I'm hoping that the program code remains largely unchanged, just the maps/tables/scalars etc are tweaked between revisions/catch codes. this will make the job much easier to begin with - ie. firs tI have to identify WHAT bytes can be changed, then I have to figure out what each BYTE does.

Initially I want to be able to say, get an XR dump, and stick it on a stock ECU and have it work (cheap performance, get a mild cam and XR dump), or I'm sure a lot of people would be interested in getting a cop version.

Then I'll start with small mods. I've got a stock EL I6 Auto (6DBD) and a cop version (6DNB), so the differences are - essentially...
- no speed limit
- diff shift points

Once I find those ( and figure out how to change them in a meaningful way!) I'd like to get an XR dump, and figure out the timing/fuel changes.

Yes, as everyone has said it's going to be a BIG project. But that's why I'm posting here, hopefully I'll get the encouragement (and sometimes support) needed to keep interested and progressing.

Now like waggin/micky was alluding to, disassembling the program code to enable support for hipo setups WILL be a long way off. And I guess will be difficult as I don't have a garage full of various cars to test on.

Yeah that was what I was initially thinking but as you will find out, Ford changes a large number (if not all) memory addresses between catch codes which makes it impossible to do. This is why when you order a chiptorque you need to specify the catch code, if it is wrong the EEC won't recognise the chip. Obviously this is done to stop people from 'cracking' these EECs because there is no way to compare different EECs which would make finding things like spark and fuel tables quite easy.

Get a manual ECU, and you can get an auto to manual conversion happening!

I am interested, OM me when you have got it sussed and i will be in

when you can do an - EF I6 man SA (South African)

i'll be the first one to knock your door down looking for one.

the SA ones had s**t loads more power then the aussie ones

If you look around the twEECer forums and the other home-built EEC tuner kits, you'll find little tools like the ECU dissasemblers. Theyre not 100% accurate, but theyre pretty good.

If your into Computer assembler then there is a good chance that will make more sense to you. The Ford Roms are not something you can just compare easilly. XR9UTE/Pete knows a lot more about the ford roms.

Nigel

Is that the hardware that Craig Moates sells? I am pretty interested in checking that out myself.

Looks like an F2 J3, F2A Adapter, and an 'Ostrich', is that right?

Very interesting that on the "Boothware" page, they offer building custom definition files for unsupported EEC codes for $US150.

Good luck with it

yep it is the moates.net gear. I got a BURN1 instead of the ostritch. If I get good at this, I'll fork out for an ostrich and be able to do dyno/highway tuning.

Update:
Finally got my F2E adapter (so now I can read EECs). And got my first two dumps. Good news is there's only about 5000 bytes difference between them (out of 256000, but the first half appears unused), and I'm hoping I can rule out most of them quickly.


EL I6 Auto vs EL I6 Auto Police
Very similar code releases = me.

Now to find time.

That'd be easy, as long as someone can send me a SA ecu I can dump it, and burn chips with it easy. Copying EECs I can do now, tuning them is another matter.

Found the speed limit byte. Turns out the cop ECUs are limited to 210.

But you can't just copy one EEC binary and burn it on a chip to use in another EEC, unless by luck that EEC had the same memory locations.

Aren't all the ECU's the same barring the Eprom data?

No that would make it easy. Each series of EECs (catch codes) usually run different memory locations. This means chips have to be programed for that EEC, and thats why you have to specify your EECs catch code when you order a chiptorque or other chips.

I'd love to know what Ford was using to create/edit the programs for these ECU's.. I'm surprised an ex/current Ford employee who works on the EEC's hasn't leaked out either the name of, or the actual software

Lots of other things have walked from Ford!

From my HUGE sample size of EECs (two), I can 100% safely concur that they are all the same.

So far the two I've tried will swap quite happily. I've decompiled the the code from both and the decode EXACTLY the same. Only a few of teh data tables are different.

Overnight I weeded that down to only 104 bytes difference between a stock EL I6 Auto EEC, and a police spec EL I6 Auto EEC.

Here is where I ask for more bins to play with. Anyone in Canberra got spare EECs lying around I can dump, and I'll be up for the Bathurst cruise, so bring your EEC with you!