Re: RE: Diagnostic Port Wiring

From: david.clement@verizon.net
Date: Fri May 28 2004 - 09:00:38 EDT


I have never had an occasion to try that procedure but that's what's in the
FSM.

Dave Clement
99 SLT+ CC 4x4

In article <c96ckm$aj5$1@bent.twistedbits.net>,
larryathey.nospam@larryathey.com (Larry L Athey) writes:
>
>
> Mine is a 99 with a 4 cylinder engine. I've tried the on/off with the
> key three times and that doesn't do anything. I can hold the odometer
> button and turn on the key, and that definitely throws the thing into
> its self test mode, but I never get an error code on the odometer. My
> check engine light has been on since I got the truck and detailed
> everything under the hood, but I never get an error code on the odometer
> after the self test.
>
> Is there some other trick that I'm missing?
>
> david.clement@verizon.net wrote:
>
> > I do not know what year your truck is but my 99 Dakota will display the
> > diagnostic codes in the LED mileage display now and my 03 PT Cruiser spits
them
> > out every time you fire up the engine (being that there is no problems with
the
> > PT it just displays "none").
> >
> > Dave Clement
> > 99 SLT+ CC 4x4
> >
> > In article <c951po$fuj$1@bent.twistedbits.net>,
> > larryathey.nospam@larryathey.com (Larry L Athey) writes:
> >
> >>
> >>I'll be honest, my only intention is to be able to listen to my pickup
> >>on a plain RS232 (serial) basis on my laptop so I can see what's going
> >>on with the diagnostic port. Once I get a grasp on it, I want to build a
> >>small in-dash or under-dash device based on a PIC processor and a small
> >>flourescent display that replaces the "check engine" idiot light with
> >>something more comprehensive. Might sound complicated to someone who
> >>isn't a programmer, but I do this kind of stuff on an almost daily
> >>basis, so it's really not that major of an undertaking for me. I would
> >>also end up making the schematic and the PIC processor source code
> >>public for others who would like to do the same thing.
> >>
> >>Josh Battles wrote:
> >>
> >>
> >>>"Larry L Athey" <larryathey.nospam@larryathey.com> wrote in message
> >>>
> >>>
> >>>>Well $150 is a little more realistic...Where did you get the
> >>>>cable/software from?
> >>>>
> >>>>I'm also curious as to where people actually find information regarding
> >>>>the pin-outs of these ports and the specifications on the proprietary
> >>>>protocol Chrysler uses.
> >>>
> >>>
> >>>Some of the pin-out information might be in the FSM... As to
> >
> > specifications
> >
> >>>of the Chrysler PCM programming, that's pretty much a mystery. There are
> >>>some companies that can reflash them, but usually everything is a pretty
> >>>closely guarded secret.
> >>>



This archive was generated by hypermail 2b29 : Tue Jun 01 2004 - 10:59:13 EDT