EFIDynoTuning Forum

I read my friends EEC IV computer in his 1993 F150. It has a 351 with an e4OD trans. 4X4. I can not find a tear tag number anywhere. the hardware is hard to make out, but looks like EFI-SD48. SAD disassembles it fine but I do not see any copy right info in the lst file. I tried using the xdf and adx files listed for the EFI-SD4x but data still looks like all jibberish. Any ideas how I can find the tear tag other than on the pcm or truck? Looks to be a reman pcm in the truck.

copyright info isnt in eec iv

nah no way to find it, you can only match it to a known one to figure out what it is

If the bin/hardware supports DCL, and the checksum and fixsum is still the oem values, then ForDiag will output the catchcode for most EEC-IV boxes but not all.

The parts numbers printed on the PCB inside the box may give a couple more hints.

No info block in EEC-IV, as decipha said.

It has the older style dcl connector. Not an OBD style connector. I have the BIN readout from the pcm. I'll post it up. I should be able to just use A1C Bin and retune if need be, correct? Is datalogging enabled in the posted A1C bin file?

On a side question, he should be able to get any EFI-SD48 hardware code pcm and it should run the truck fine as long as we put a chip or quarterhorse in it with the proper tune, correct? Also, is the A1C strategy posted for a 4x4 E4Od 351w Truck, or will I have to make some major changes to it to make it work? Thanks again for all the help. His truck has been doing random stuff with the trans and drivability lately and we were looking into it and found some corrosion and some questionable repairs inside, so we were thinking it may possibly need a new PCM, and it seems they are getting pretty hard to find for a 351w E4OD truck. I was originally just planning on putting the quarterhorse in it with a stock file and hoping to log it while it was acting up, but looks like there is not an ADX or XDF available for his specific file.

DCLHP looks to be enabled in the bin and the external interrupt also, but for whatever reason I can't get your bin too talk on the DCL capable hardware I have here. So none the wiser on catch code. If your hardware code is the same as A1C then you can run A1C on your hardware. A1C will need to support the same functionality as your bin does, so it may/not work out depending on similarity/difference.

Ok. I guess I will try and download A1C and give it a shot. Hopefully it is pretty close. Not knowing the exact tear tag info on this pcm, I guess anything is a shot in the dark. I think that A1C is about the same hardware code from what I see on this forum.

I have these as a possibility.

that houston named file posted is a revision to the S0M cal its the same strategy

Weird that all I get is gibberish when I use the XDF posted, or maybe it’s me doing something wrong?