90 F150 5.0L EEC without a label with catch code

joker772005 · Post by **joker772005** » Fri Jul 20, 2012 12:03 am

How wud I go about obtaining my eec catch code on a 90 f150 5.0 auto?
There is not any kind of writing on it that says a ford part # or catch code.I know the eec was replaced under recall or some type of recal back in 95ish.
Mike

vristang · Post by **vristang** » Fri Jul 20, 2012 2:56 pm

Trial and error is the only way I know of...
Pull and save the .bin
Then try opening it with definitions that might work...

Hopefully there is a better way?

crakrz · Post by **crakrz** » Fri Jul 20, 2012 5:14 pm

I thought that the bins actually had that info in them. For example, if I open up my bin with hex editor, at address 27F**, or thereabouts, the strategy and bin numbers are actually listed. I don't know if this is just with our EECV 4 bank bins, or if its a common feature. Someone else, like sailorbob, may know more about it.

joker772005 · Post by **joker772005** » Fri Jul 20, 2012 5:30 pm

i went threw all the bins on eecanalyzer and cudnt find any list for my truck

joker772005 · Post by **joker772005** » Fri Jul 20, 2012 6:09 pm

i found a code inside of x9j
anybody crack that yet?

decipha · Post by **decipha** » Fri Jul 20, 2012 8:12 pm

only eec5 contains strategy

prob speed density something close to a file i posted from a 93 f150

theres an automatic disassembly thread with some details but that wont help any

gt40ford · Post by **gt40ford** » Fri Jul 20, 2012 9:20 pm

Maybe , just maybe,

Since the binary is data, could you read the existing bin and run a simple hash/checksum on that and other known binaires and find the one that matches?

joker772005 · Post by **joker772005** » Fri Jul 20, 2012 11:21 pm

gt40ford wrote:Maybe , just maybe,

Since the binary is data, could you read the existing bin and run a simple hash/checksum on that and other known binaires and find the one that matches?

gonna take me a couple years b4 im smart enuff to understand what you said

yea this is for a non maf/vaf 1 o2 map sensor

decipha · Post by **decipha** » Sat Jul 21, 2012 9:58 am

comparing checksums won't do you any good unless you just so happen to stumble across that exact binary which is very unlikely considering those ecu's aren't too well supported

now if you could compare the binary to other binarys and calculate the percentage of difference you'd then be on to something, if you could find a binary that had as much in common with that specific binary you'd be able to figure out what strategy it is

joker772005 · Post by **joker772005** » Sat May 17, 2014 2:25 pm

bringing this back up.....anybody crack it yet?

LeadHead · Post by **LeadHead** » Sat May 17, 2014 10:32 pm

No, and I doubt anyone ever will. Very, very little interest in the Gen 1 EEC-IV Speed Density F-150 stuff. The only one that really has any support is the 351 E4OD lightning computer.

jsa · Post by **jsa** » Sun May 18, 2014 3:08 am

When I use ForDiag on my eec-iv, it reports strategy and catchcode from the eec-iv.

XantheFIN · Post by **XantheFIN** » Mon May 19, 2014 1:41 pm

ForDiag uses Checksum for that.

I would use those Calibration Pointers on 2020 or 0020=56K Addresses and look which Strategy uses same pointers. Example:
08 01 00 BF CA C0 A6 C3 60 CB A8 CF C6 D4 2A D7 A4 D7

jsa · Post by **jsa** » Tue May 20, 2014 1:03 am

XantheFIN wrote:ForDiag uses Checksum for that.

When I have the GGR chip plugged in ForDiag reports CARD catchcode, rather than COSY of the eec-iv alone.

The GGR chip will have a different checksum to CARD, so does ForDiag really have the checksum and catchcode of 3rd party chips ?

XantheFIN · Post by **XantheFIN** » Tue May 20, 2014 4:07 am

jsa wrote:
XantheFIN wrote:ForDiag uses Checksum for that.
When I have the GGR chip plugged in ForDiag reports CARD catchcode, rather than COSY of the eec-iv alone.

The GGR chip will have a different checksum to CARD, so does ForDiag really have the checksum and catchcode of 3rd party chips ?

Well i did not think that. But i thought that because everytime when i update my Tune it Checksum becomes different. And some times i get that my car become 4,6l and so on. But usually i get nothing else than Checksum over there to be displayed.

Tomin · Post by **Tomin** » Wed May 21, 2014 2:55 am

Hi,

Fordiag uses, on EEC 4, a calibration ID. It is not checksum.
It is word transimtted from EEC in data stream.
Plus, fordiag has internal table with all calibration id / catch code / partnum,
so it can search rest of informations from calid then.

(I am creator of Fordiag, so it is confirmed information :-)
Tomas

sailorbob · Post by **sailorbob** » Wed May 21, 2014 1:14 pm

The calibration ID (aka CALID) was superseded by the checksum (aka ROM_TO) in the late '80's. The checksum forms a unique reference and there is another parameter (the FIXSUM) that is used to ensure the ROM_TO value is unique.

Once you change a calibration and recalculate the checksum this method of ecu identification no longer works.

Tomin · Post by **Tomin** » Wed May 21, 2014 2:53 pm

Superseded ? It works for me on all EEC IV models, so up to cca '1999 (Escort 1.6 Zetec, for example).

sailorbob · Post by **sailorbob** » Wed May 21, 2014 3:02 pm

The ecu is giving you the ROM_TO value when issuing the ROM Calibration ID in a DCL message.

BTW, nice work with your Fordiag s/w

Tomin · Post by **Tomin** » Thu May 22, 2014 6:36 am

Oh, so. Thanks for a clarification.

90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Re: 90 F150 5.0L EEC without a label with catch code

Who is online