[Thunderbird6]

Why didn't I think of doing a Google search years ago for this.. sheeesh duh.

A whole forum on EEC IV - wow. great.

I have an EEC IV in a street rod. THe motor is an 89 mustang 302 with MAF (hot wire anemometer)

I rewired pretty much everything and dumped all the EGR / emissions crap. The motor had work and I raised to compression to about 10:1, roller rockers, gapless rings, flowed and ported, yada yada

The MAF sits about 3 feet further away from the inlet manifold. I had to use a piece of plastic PVC black pipe to connect it to the flexible rubber inlet hose. It has run well but would still like to get into the code.

Just so happens I am a software developer and work with low level languages and ASM. I was very interested to read this thread:

viewtopic.php?f=8&t=19542

Anyone have Andy's email. Loved TVRs but didnt know they had EEC mkIV in them. Is that the Rover controller also?

Obviously a lot of reading to do here. I need to figure out how to d/l binaries with a laptop for one.

I have a custom fuel system and custom stainless exhaust with the exhaust gas sensors in place. Running in Highway Spark mode for fuel economy on longer journeys was an important part of the concept.

I'm interested in the megasquirt solutions but not sure what that will buy me. Im more interested in looking at the code. Will ford every release the source?

[cgrey8]

Welcome.
Check out eecanalyzer.net for downloads of Binary Editor, EEC Analyzer, def files, and binary tune files. There's a lot of reading in the FAQ and some tuning-related tech docs as well. But before you even think of trying to look at and decipher assembly, you really need to understand the non-programming aspect of tuning first. Understand your EEC's strategy, what adjustments are available, the common lingo and programming concepts, and then once you got all that under your best, only then would the code even begin to make sense. If all you are after is tuning, you don't need to know a think about programming or code. But I can get how as a software guy, you'd think that would be the easiest place for you to start. I'm here to say, as a firmware developer myself, resist that thinking. That's not where you should start.

Anyway, welcome and I hope you find the info and people here useful to you.

[jsa]

Anyone have Andy's email.

You can PM him on here but he has been quiet for a while, hopefully all's well.

Thread on another forum if disassembly interest you.
http://www.efidynotuning.com/forum/view ... =30&t=1042

As Chris said disassembly is not necessary if your catch code strategy is available already.