Code Scanners and Testers
Logistics Pro
Joined: Aug 2014
Posts: 3,566
Likes: 852
OBD1 was basically from 1980-1995, then OBD2 from 1996 onward.
Primarily driven by California emission regulations in 1991.
For scan tools, your looking at a very small window for OBD1, about 5 years where manufacturers could create something.
New for OBD1, no, not in production. There is also ForDiag, but last time I looked not for sale any longer. Definitely a good one.
And for the hobbyist and DIYer, there are a couple of opensource projects:
- AVR https://github.com/mercury64/ford-eec-iv-diagnostic
- Arduino https://github.com/mercury64/eec-iv-reader-arduino
- Atmega https://github.com/mercury64/eeciv
Primarily driven by California emission regulations in 1991.
For scan tools, your looking at a very small window for OBD1, about 5 years where manufacturers could create something.
New for OBD1, no, not in production. There is also ForDiag, but last time I looked not for sale any longer. Definitely a good one.
And for the hobbyist and DIYer, there are a couple of opensource projects:
- AVR https://github.com/mercury64/ford-eec-iv-diagnostic
- Arduino https://github.com/mercury64/eec-iv-reader-arduino
- Atmega https://github.com/mercury64/eeciv
Logistics Pro
Joined: Aug 2014
Posts: 3,566
Likes: 852
DCL supports both standard UART and CART (Custom Asynchronous Receiver/Transmitter) modes.
Maximum data rate is 19,200 baud, depending on the ECU.
There are approximately 40 different parameters that can be read, including RPM, ECT, MAP, FUELPW, etc.
Thread
Thread Starter
Forum
Replies
Last Post
ChRoNo16
1987 - 1996 F150 & Larger F-Series Trucks
4
May 30, 2016 08:17 PM
Big_Man_Brad
1987 - 1996 F150 & Larger F-Series Trucks
11
Mar 4, 2008 06:17 PM
