Alright now I have some time let me kick off the discussion, and yes MarkCL, by the time we've finished this discussion I will justify my view that the other ECU's are not capable of producing the same HP with the same reliability as Motec
Over the years there have been a few attempts to stop 3S-GTE from failing. However all of these attempts have been solutions for problems that weren’t properly defined. If you don’t know what’s going wrong how can you fix it? This strategy brought about several urban myths about the 3S-GTE, like “you need a Supra fuel pump”, or even “a dual feed fuel rail is the answer”. An answer to what I ask? To the best of my knowledge nobody has ever put a fuel pressure & flow sensor on and logged the data, either before or after these mods. If they had then I doubt these “fixes” would have been done or attained the legendary status that they have. Simple data logging would have shown that there was/was not a fuel supply or pressure problem, and if these mods fixed it. No, they relied on the old “it hasn’t blown so I must’ve fixed it” adage, to which I say “fixed what?” and “Don’t you mean it hasn’t blown
yet?”. These mods don’t solve the problem, and there a plenty of people who’ve done them that still blow their motors.
So what next? Well if you’re the typical MR2 enthusiast you find a new miracle cure (Evans Coolant) and invent the problem it solves (micro boiling), of course you provide no data (or you provide data that proves nothing about what you claim to be the problem) and everyone jumps on the bandwagon, cursing the naysayers and hyping up the benefits of this new wonder cure to all that will listen. I must admit to a quiet chuckle when the chief proponent of this particular snake oil blew his motor
What you really need to do is find out why the 3S-GTE is blowing up, and before anyone shouts the D word, I don’t mean the method of failure (that’s pretty obvious), but what causes the detonation to occur in the first place. That is why you need data-logging, along with the tools and skills to set it up and interpret the data. This is where the aftermarket ECU shines, not only can you log he data, but you can change settings and see what effect these changes have.
So now we have identified one of the important features that is required lets have a look at what is on offer from the ECU’s. I’ll stick to comparing the Motec M400/600 (with notes where the M800/880 differs), Haltech E11 & Autronic SM2 but if you have any other ECU’s you’d like to compare please post their features. I apologise if I make any mistakes in the specs for the Autronic/Haltech as I’m not as familiar with them as the Motec, and can only rely on what I can read in their manuals/ find in the software.
Motec - Optional 512kb (M800 = 1mb, M880 =4mb) onboard logging for up to 64 channels at one time (from about 300 possible), logging rate variable for each channel at 1,2,5,10,20,50,100, or 200hz. Remote telemetry option, All ECU channels can be logged at 20Hz using a CAN compatible logger e.g. ADL. Has very good interpreter software for viewing the data, also supports CSV export.
Haltech - 448kb onboard, up to 10 channels from a possible 81, all channels logged at either 1,10 or 200hz, can be RPM activated. Also supports unlimited logging to PC for up to 20 channels (from a possible 60), at 10hz, software only supports viewing in 2 minute chunks very limited graphing abilities, files are CSV.
Autronic - hard to find data about the onboard system, from a search on the net it appears to have only 32kb onboard, 16 channels (out of 44) @50hz enough for about 30secs of 8 channels, no wonder they don’t mention it anywhere. PC logging for 76(?) channels at .2,.5,1,2,5,10,20hz (limited by transmission speed), remote telemetry option. Log viewing software is IMO not very user friendly and has poor interpretation facilities, although it does have XY plots which on the Motec requires the advanced logging option or export to an external graphing solution e.g. Excel.
IMHO Motec is the clear winner in the Datalogging stakes, with the only black mark being no direct PC logging, which IME is not required and this limitation can be overcome if required (I wrote a program to download the log from the ECU every 10 minutes)
That’s enough for a start, any comments?