That's pretty ambitious! As I see it, the only hangup that I could think of
is being able to establish successful communications with the PCM. I'm sure
that you'd be able to reverse engineer whatever piece of software that you
could find that communicates successfully already. Are you a programmer or
EE?
-- - Josh Lowered 2000 Dakota CC 3.9L www.geocities.com/lenny187/dakota.html www.omg-stfu.com"Larry L Athey" <larryathey.nospam@larryathey.com> wrote in message news:c951po$fuj$1@bent.twistedbits.net... > > 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