The MegaSquirt Project has experienced explosive growth other the years, with hundreds of new MS installations occurring every week - a phenomenal success! MegaSquirt has been successfully used in all aspects of Internal Combustion engine applications including R&D, Industry, Race, and Research. The MS project has transformed itself from a simple R&D project into a full-featured mature engine control system. To reflect this the support structure has also changed to meet the needs of MegaSquirt Users.
Moving forward, the R&D forums for MegaSquirt project are in a read-only mode - no new forum posts are accepted.
However the forums will remain available for view, they still contain a wealth of information on how MegaSquirt works, how it is installed and used. Feel free to search the forums for information, facts, and overview.While the R&D forum traffic has slowed in recent years, this is not at all a reflection of Megasquirt users, which continue to grow year after year. What has changed is that the method of MegaSquirt support today has rapidly moved to Facebook, this is where the vast majority of interaction is happening now. For those not on Facebook the msextra forums is another place for product support. Finally, for product selection assistance, all of the MegaSquirt vendors are there to help you select a system, along with all of the required pieces to make it complete.
I have a Rover SD1 originally fitted with Lucas injection. My car has now an MS2 V3, EDIS ignition and a Tech Edge wideband O2 unit.
I'm making up a 'plug and play' MS (for SDI Club members) inside the original Lucas ECU case which will be fuel only - really just because the original ECUs are getting tired and expensive to fix. So it only needs to match the performance of the original when working properly (if they ever did ). A V2.2 should fit the bill nicely. (UK cars have no cat. or lambda sensor)
I've made a prototype, and would like to map it correctly for a standard engine - but to use my car for this would mean a lot of work changing it back to standard. So does anyone make a board that could be adapted to piggyback the MS1 to my MS2 which would then be used for ignition only? Or any tips on attempting such a thing? So I could use my own car to map it?
Dave P, London UK.
Rover V-8
MSII V3
EDIS
Tech Edge Wideband
I am not completely sure if it is what your after as it almost sounds like you want to just "swap processors" without opening the case... If so, I think you have a little more work cut out for you. Keep in mind that 12v feed into the MS2 can not be connected in the same spot on the MS1.
That's interesting - never seen that before. However, the cost to me in the UK becomes $60 instead of $20 because they insist on using stupidly expensive couriers. FFS, it's only a small bare PCB with low value and could be sent letter post.
Dave P, London UK.
Rover V-8
MSII V3
EDIS
Tech Edge Wideband
So I am dealing with a simular project in a few ways. Not to go into that here, but I have done simular now, and in the past.
So for these Lucas ECU replacements ALL you want is fuel control? I would suggjest a little bit of ectra effort and brainstorming making it a simple extra step up to full ignition control too. That is where ALL the power is at anyways. But your base issue?
The simplest solution I can see is to just remove the MS2 processor for now, and pop in an MS1. You should only have minimal work to do so. As the .msq's are not backwards compatable, you will have to either export the vex tables (also possibly not backwards compatable) for ignition, or screenshot and then redoe them. I have done this dozens of times to make new tunes from incompatable platforms. The quickest way is to use two computers side by side. I have always done this with MegaTune and usign review mode. A thumbdrive can quickly export and import VEX files between them. At worse it takes 1-2hrs. No fancy hardware needed.
You could get fancy though and swap out your 40 pin socket for a ZIF. With the MS2, you will need one that does not have a flip up lever arm. A low profile one or something. Still it is easy enough to pop processors out and I would not use a ZIP long term in the automotive vibration enviroment.
When done tuning, you would have a file capable of both fuel and spark. Fueling is fairly forgiving though while spark, not so much. And you can quickly remove all the spark portions from the tune files if you so choose.
Anyways a solution not requiring any additional hardware expendature (beyone a processor and possibly a ZIF). I do not know your current setup, but some additional effort and though may need to go into even a simple processor swap. I have always taken the extra time to make my installs multi platform and ECU compatable. But that is not the norm I guess.