If anyone here wants data info from Ford 4.0 liter v6 and I6 engines with the EEC IV, I can help. If your building a MegaSquirt kit, its propably a good shoe in to reduce a lot of extra work. Down here, Australian EFI Fords ran EEC IV and EEC V computers since about 1986, but weren't ODB2 compliant. The US import Explorer was fully ODB2 compliant, and ran the same kind of gearbox as the later 2008- date 5-speed auto Falcons and Territories. So a long term plan for me has been to get all the Aussie 4.1 and 4.0 systems patched into the US Cologne V6 Explorer/Mustang emissions certified systmes rather than constantly mucking about with the real headaches of Ford Australias often patchy and hard to lock down EEC IV and V transitions. Also there has been a desire to eliminate the need to buy a Ford Australia specific T5 or Borg Waner/BTR/Ion or ZF automatic gearbox.
What I've found is that I'm currently able to use two of the sixty sensor inputs to download vehicle distance and rear wheel bump at 50 foot intervals!
I cant do any binary code dumps as yet, but can log most of the SOHC v-six parameters visually at 50 feet intervals using this screen
http://www.fordscorpio.co.uk/images/image10.gif
Since my 3.3 and 4.1 log head EFI units use US Ford Explorer gearboxes and odb2 compliant EEC IV computers, I've got to download fuel air ratios, pulse width, tps settings, MAP and total advance settings so I can get an EECIV calibration for Crossflow and Log head EFI engines under varing loads. I'm able to produce a part load Road Warrior Dyno System settings from about 2500 miles of existing surveyed road in my Explorer. Its 4.0 V6 and 3.3/4.0/4.1 I6 engine capable, crossflow, log head, 2v, sohc or dohc.
Its just that my 98 Explorers EEC IV computer has a 32 bit memory with heaps of room to data log. Im curently using two 16 bit data loggers for my road roughness, and as a cost saving going forward for my business, I would like to use more of the functionality in Fords EEC system.
I'm using an ODB 2 plug in to read data from my 4 liter Explorer (from Alex Pepper at http://www.obd-2.com/) , and I'm just stunned at how much info I can get out of a Ford on board computer. I spent 8 grand on two Campbell Scientific CR1000x computers only to find that the EEC unit can probably due the same for the price of a junked Explorer.
What I've found is that I'm currently able to use two of the sixty sensor inputs to download vehicle distance and rear wheel bump at 50 foot intervals!
I cant do any binary code dumps as yet, but can log most of the SOHC v-six parameters visually at 50 feet intervals using this screen
http://www.fordscorpio.co.uk/images/image10.gif
Since my 3.3 and 4.1 log head EFI units use US Ford Explorer gearboxes and odb2 compliant EEC IV computers, I've got to download fuel air ratios, pulse width, tps settings, MAP and total advance settings so I can get an EECIV calibration for Crossflow and Log head EFI engines under varing loads. I'm able to produce a part load Road Warrior Dyno System settings from about 2500 miles of existing surveyed road in my Explorer. Its 4.0 V6 and 3.3/4.0/4.1 I6 engine capable, crossflow, log head, 2v, sohc or dohc.
Its just that my 98 Explorers EEC IV computer has a 32 bit memory with heaps of room to data log. Im curently using two 16 bit data loggers for my road roughness, and as a cost saving going forward for my business, I would like to use more of the functionality in Fords EEC system.
I'm using an ODB 2 plug in to read data from my 4 liter Explorer (from Alex Pepper at http://www.obd-2.com/) , and I'm just stunned at how much info I can get out of a Ford on board computer. I spent 8 grand on two Campbell Scientific CR1000x computers only to find that the EEC unit can probably due the same for the price of a junked Explorer.