Jon, my experience with pre OBD-II mopars is the two digit code will reflect an
issue with a particular circuit to further narrow it to the multiple
possibilities requires the use of other diagnotic tools (multi-meter or
dedicated sensor testor) and the FSM. Hooking up to a read out tool will not
provide further refinement. The factory DRB tool besides reading the code has
the capability to activate outputs of the computer such as activating an
solenoid. Also, the exact definition of the pre OBD-II code changed from year
to year so the 37 code example for one year may deal with the temperature
sensor and another year the troque covertor.
The early OBD-II systems (my 97 Avenger for example) had the two digit key
on/off output, which could be further refined to an OBD-II code with a OBD-II
scan tool. An example was my check engine light came on on the Avenger, the key
on/off routine told me it was an O2 sensor. When I plugged it into my OBD-II
scan tool I got a code for the rear bank upstream sensor.
Dave Clement
99 SLT+ CC 4x4
In article <dabta6$mv0$1@bent.twistedbits.net>, jon@dakota-truck.net writes:
>
>
> menefreghista <usriflecal30_m1@yahoo.com> wrote:
>
> : 95 5.2L throws these....12, 22, 37 and 55. I am aware
> : of what they are by using the trouble decoder on the
> : dml home page. 12 and 55 are nothing, but I have a
> : check engine light on. I have replaced the ECT sensor
> : on the block. Next step????
>
>
> Unfortunately the key on-off method can only narrow it down
> so far. As you no doubt noticed when you ran the trouble codes
> on the DML page, 22 could be 2 things, and 37 could be 6
> different things. As the next step I would recommend narrowing
> that down to find out exactly what the computer is complaning
> about. I know that many auto parts stores, such as Autozone
> will read your trouble codes for free, but unfortunately I'm
> not sure if they can only do OBD-II or if they have the ability
> to check the earlier vehicles. It would be worth stopping
> in or calling to check, anyway. Worst case scenario would be
> you would have to stop at a dealer (or an independent garage with
> the proper equipment) to have them read your codes. Unless you
> are on very good terms with them though, that's probably going to
> cost you some money. Anyway, that's what I recommend - find
> someone who can pull the exact trouble codes and you'll be on
> much better footing to decide what to do next.
>
>
> --
> -Jon-
>
> .-- Jon Steiger ---- jon@dakota-truck.net or jon@jonsteiger.com --.
> | 1970 Barracuda - 1990 Dakota 'vert - 1992 Ram 4x4 - 1996 Dakota |
> | 1996 Intruder 1400 - 1996 Kolb FireFly - 2001 Ram QC 3500 CTD |
> `------------------------------------ http://www.jonsteiger.com --'
This archive was generated by hypermail 2b29 : Mon Aug 01 2005 - 10:56:27 EDT