Anybody already found some J1939 code?
I am working on my little hobby project to fool a trucks' speed limiter and
I would really appreciate it if anybody could give some help to start up with a
LPC2129. I do have pretty much knowledge of SAE J1939, but my knowledge about
embedded programming is not (yet) enough.
Regards,
Andr
The Neterlands
>
>
>Does anyone know of any J1939 stacks that can be used with the Philips
>LPC2xxx uC's. I've Googled around a bit but have not found
anything
>yet...
>
>Thanks!
>
Re: J1939 stacks for the LPC2xxx's?
Started by ●January 6, 2006
Reply by ●January 6, 20062006-01-06
This is more like a job for a 6 pin PIC10 than a 32bit ARM part. You
really don't need to get into the intricacies of internal
communications, this is total overkill. The simplest way is to mess with
the singal from the (normally) gear box directly. However this will be
a) breaking the law, b) voiding any warranty, and c) potentially life
threatening to other road users, so I would strongly recommend it be
something you NOT try. If I were to do this personally, say for the sake
of racing said truck, in legitimate competition, I would intercept the
speed signal coming from the gear box and output my own 'scaled' signal.
In most cases you can leave this alone until you approach the limit. In
most ECU's I've seen (these were mainly cars, not trucks) the speed
signal was not used for engine management, except to limit the vehicle
speed, so by altering it you should not alter performance of the ECU or
vehicle in any other way. This also means you can interfere with the
signla just before the programmed limit is reached. The micro will
monitor this, and as the limit is approached it will take over the and
generate its own speed signal for the ECU, and maintain this below the
limit. The downside to this is inaccurate speedometer, odometer, and any
fuel/trip type computers. I would either see if these circuits are
separately serviced by the singla, and, if so, only interfere with the
feed to the ECU for speed limiting, or I would pass the true signal to a
display which could then show the actual roadspeed vs the 'modified' one.
That's of course if I ever got into truck racing. Which is unlikely.
Cheers
Al
andrebesselsen@andr... wrote:
>Anybody already found some J1939 code?
>
>I am working on my little hobby project to fool a trucks' speed limiter and I would really appreciate it if anybody could give some help to start up with a LPC2129. I do have pretty much knowledge of SAE J1939, but my knowledge about embedded programming is not (yet) enough.
>
>Regards,
>
>Andr
>
>The Neterlands >
>>
>>
>>Does anyone know of any J1939 stacks that can be used with the Philips
>>LPC2xxx uC's. I've Googled around a bit but have not found anything
>>yet...
>>
>>Thanks!
>>
>>
>>
>>
>>
>>
>>
> >
>Yahoo! Groups Links >
>
really don't need to get into the intricacies of internal
communications, this is total overkill. The simplest way is to mess with
the singal from the (normally) gear box directly. However this will be
a) breaking the law, b) voiding any warranty, and c) potentially life
threatening to other road users, so I would strongly recommend it be
something you NOT try. If I were to do this personally, say for the sake
of racing said truck, in legitimate competition, I would intercept the
speed signal coming from the gear box and output my own 'scaled' signal.
In most cases you can leave this alone until you approach the limit. In
most ECU's I've seen (these were mainly cars, not trucks) the speed
signal was not used for engine management, except to limit the vehicle
speed, so by altering it you should not alter performance of the ECU or
vehicle in any other way. This also means you can interfere with the
signla just before the programmed limit is reached. The micro will
monitor this, and as the limit is approached it will take over the and
generate its own speed signal for the ECU, and maintain this below the
limit. The downside to this is inaccurate speedometer, odometer, and any
fuel/trip type computers. I would either see if these circuits are
separately serviced by the singla, and, if so, only interfere with the
feed to the ECU for speed limiting, or I would pass the true signal to a
display which could then show the actual roadspeed vs the 'modified' one.
That's of course if I ever got into truck racing. Which is unlikely.
Cheers
Al
andrebesselsen@andr... wrote:
>Anybody already found some J1939 code?
>
>I am working on my little hobby project to fool a trucks' speed limiter and I would really appreciate it if anybody could give some help to start up with a LPC2129. I do have pretty much knowledge of SAE J1939, but my knowledge about embedded programming is not (yet) enough.
>
>Regards,
>
>Andr
>
>The Neterlands >
>>
>>
>>Does anyone know of any J1939 stacks that can be used with the Philips
>>LPC2xxx uC's. I've Googled around a bit but have not found anything
>>yet...
>>
>>Thanks!
>>
>>
>>
>>
>>
>>
>>
> >
>Yahoo! Groups Links >
>
Reply by ●January 6, 20062006-01-06
> Do you know anything about J1850 (OBDII)?
What do you need to know? I've done keyword protocol.
Randy
www.newmicros.com
What do you need to know? I've done keyword protocol.
Randy
www.newmicros.com
Reply by ●January 6, 20062006-01-06
> -----Original Message-----
> From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> Of Randy M. Dumse
> Sent: Friday, January 06, 2006 3:37 PM
> To: lpc2000@lpc2...
> Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>
> > Do you know anything about J1850 (OBDII)?
>
> What do you need to know? I've done keyword protocol.
>
> Randy
> www.newmicros.com
I'm a "me too" on this topic :)
Is there any documentation out there on how to get info from an OBDII port?
I had a OBDII scanner hooked up to a Ford truck at one time and was able to
figure out a few commands like oil temp, tran temp, ... It would be nice if
there was a document that covered all of the commands. I've Googled quite a
bit on the subject and have come up with nothing.
Thanks for any info you could give out!!! Greg Deuerling
> -----Original Message-----
> From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> Of Randy M. Dumse
> Sent: Friday, January 06, 2006 3:37 PM
> To: lpc2000@lpc2...
> Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>
> > Do you know anything about J1850 (OBDII)?
>
> What do you need to know? I've done keyword protocol.
>
> Randy
> www.newmicros.com > Yahoo! Groups Links >
Reply by ●January 6, 20062006-01-06
This gleaned from agoogle for J1850 COMMANDS. tHE 808 MENTIONED IS A
gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
maybe this will be of some help.
Cheers
Al
>
>Bruce
>The fault code 22 you saw was TPS voltage too low.
>My manual says that this code is set if TPS voltage falls below 0.15V
>
>Here is a list of all 808 Fault codes.
>
>12 System Functioning OK
>13 Oxygen sensor Open Circuit
>14 CTS low ( <0.7V)
>15 CTS High (>4.65)
>21 TPS High (>2.5V and MAP <60kPa fot 2 secs)
>22 TPS Low (<0.15V)
>23 MAT High (>4.9V)
>24 VSS Error
>25 MAT Low (<0.3V)
>33 MAP High
>34 MAP Low
>41 No Refrence Pulse
>42 EST Failure
>43 Knock Sensor open or shorted
>44 Oxygen sensor low (<0.25V, >20Sec)
>45 Oxygen sensor high (>0.45V, >20Sec)
>51 MEMCAL Error
>55 A to D error (>5.5V)
>
>Hope that this helps
>Cheers
>Matt
Greg Deuerling wrote:
>>-----Original Message-----
>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>Of Randy M. Dumse
>>Sent: Friday, January 06, 2006 3:37 PM
>>To: lpc2000@lpc2...
>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>
>>
>>
>>>Do you know anything about J1850 (OBDII)?
>>>
>>>
>>What do you need to know? I've done keyword protocol.
>>
>>Randy
>>www.newmicros.com
>>
>>
>
>I'm a "me too" on this topic :)
>
>Is there any documentation out there on how to get info from an OBDII port?
>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
>figure out a few commands like oil temp, tran temp, ... It would be nice if
>there was a document that covered all of the commands. I've Googled quite a
>bit on the subject and have come up with nothing.
>
>Thanks for any info you could give out!!! >Greg Deuerling >
>>-----Original Message-----
>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>Of Randy M. Dumse
>>Sent: Friday, January 06, 2006 3:37 PM
>>To: lpc2000@lpc2...
>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>
>>
>>
>>>Do you know anything about J1850 (OBDII)?
>>>
>>>
>>What do you need to know? I've done keyword protocol.
>>
>>Randy
>>www.newmicros.com
>>
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
> >
>Yahoo! Groups Links >
>
gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
maybe this will be of some help.
Cheers
Al
>
>Bruce
>The fault code 22 you saw was TPS voltage too low.
>My manual says that this code is set if TPS voltage falls below 0.15V
>
>Here is a list of all 808 Fault codes.
>
>12 System Functioning OK
>13 Oxygen sensor Open Circuit
>14 CTS low ( <0.7V)
>15 CTS High (>4.65)
>21 TPS High (>2.5V and MAP <60kPa fot 2 secs)
>22 TPS Low (<0.15V)
>23 MAT High (>4.9V)
>24 VSS Error
>25 MAT Low (<0.3V)
>33 MAP High
>34 MAP Low
>41 No Refrence Pulse
>42 EST Failure
>43 Knock Sensor open or shorted
>44 Oxygen sensor low (<0.25V, >20Sec)
>45 Oxygen sensor high (>0.45V, >20Sec)
>51 MEMCAL Error
>55 A to D error (>5.5V)
>
>Hope that this helps
>Cheers
>Matt
Greg Deuerling wrote:
>>-----Original Message-----
>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>Of Randy M. Dumse
>>Sent: Friday, January 06, 2006 3:37 PM
>>To: lpc2000@lpc2...
>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>
>>
>>
>>>Do you know anything about J1850 (OBDII)?
>>>
>>>
>>What do you need to know? I've done keyword protocol.
>>
>>Randy
>>www.newmicros.com
>>
>>
>
>I'm a "me too" on this topic :)
>
>Is there any documentation out there on how to get info from an OBDII port?
>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
>figure out a few commands like oil temp, tran temp, ... It would be nice if
>there was a document that covered all of the commands. I've Googled quite a
>bit on the subject and have come up with nothing.
>
>Thanks for any info you could give out!!! >Greg Deuerling >
>>-----Original Message-----
>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>Of Randy M. Dumse
>>Sent: Friday, January 06, 2006 3:37 PM
>>To: lpc2000@lpc2...
>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>
>>
>>
>>>Do you know anything about J1850 (OBDII)?
>>>
>>>
>>What do you need to know? I've done keyword protocol.
>>
>>Randy
>>www.newmicros.com
>>
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
> >
>Yahoo! Groups Links >
>
Reply by ●January 6, 20062006-01-06
For a more complete listing I came across this for Jeep using search
string "J1850 MESSAGES". This got loads more hits than other efforts.
http://www.stu-offroad.com/engine/scancodes.htm
Cheers
Al
Onestone wrote:
>This gleaned from agoogle for J1850 COMMANDS. tHE 808 MENTIONED IS A
>gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
>
>maybe this will be of some help.
>
>Cheers
>
>Al >
>>Bruce
>>The fault code 22 you saw was TPS voltage too low.
>>My manual says that this code is set if TPS voltage falls below 0.15V
>>
>>Here is a list of all 808 Fault codes.
>>
>>12 System Functioning OK
>>13 Oxygen sensor Open Circuit
>>14 CTS low ( <0.7V)
>>15 CTS High (>4.65)
>>21 TPS High (>2.5V and MAP <60kPa fot 2 secs)
>>22 TPS Low (<0.15V)
>>23 MAT High (>4.9V)
>>24 VSS Error
>>25 MAT Low (<0.3V)
>>33 MAP High
>>34 MAP Low
>>41 No Refrence Pulse
>>42 EST Failure
>>43 Knock Sensor open or shorted
>>44 Oxygen sensor low (<0.25V, >20Sec)
>>45 Oxygen sensor high (>0.45V, >20Sec)
>>51 MEMCAL Error
>>55 A to D error (>5.5V)
>>
>>Hope that this helps
>>Cheers
>>Matt
>>
> >
>Greg Deuerling wrote: >
>>>-----Original Message-----
>>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>>Of Randy M. Dumse
>>>Sent: Friday, January 06, 2006 3:37 PM
>>>To: lpc2000@lpc2...
>>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>>
>>>
>>>
>>>
>>>
>>>>Do you know anything about J1850 (OBDII)?
>>>>
>>>>
>>>>
>>>>
>>>What do you need to know? I've done keyword protocol.
>>>
>>>Randy
>>>www.newmicros.com
>>>
>>>
>>>
>>>
>>I'm a "me too" on this topic :)
>>
>>Is there any documentation out there on how to get info from an OBDII port?
>>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
>>figure out a few commands like oil temp, tran temp, ... It would be nice if
>>there was a document that covered all of the commands. I've Googled quite a
>>bit on the subject and have come up with nothing.
>>
>>Thanks for any info you could give out!!!
>>
>>
>>Greg Deuerling
>>
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>>Of Randy M. Dumse
>>>Sent: Friday, January 06, 2006 3:37 PM
>>>To: lpc2000@lpc2...
>>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>>
>>>
>>>
>>>
>>>
>>>>Do you know anything about J1850 (OBDII)?
>>>>
>>>>
>>>>
>>>>
>>>What do you need to know? I've done keyword protocol.
>>>
>>>Randy
>>>www.newmicros.com
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
> >
>
>Yahoo! Groups Links >
>
string "J1850 MESSAGES". This got loads more hits than other efforts.
http://www.stu-offroad.com/engine/scancodes.htm
Cheers
Al
Onestone wrote:
>This gleaned from agoogle for J1850 COMMANDS. tHE 808 MENTIONED IS A
>gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
>
>maybe this will be of some help.
>
>Cheers
>
>Al >
>>Bruce
>>The fault code 22 you saw was TPS voltage too low.
>>My manual says that this code is set if TPS voltage falls below 0.15V
>>
>>Here is a list of all 808 Fault codes.
>>
>>12 System Functioning OK
>>13 Oxygen sensor Open Circuit
>>14 CTS low ( <0.7V)
>>15 CTS High (>4.65)
>>21 TPS High (>2.5V and MAP <60kPa fot 2 secs)
>>22 TPS Low (<0.15V)
>>23 MAT High (>4.9V)
>>24 VSS Error
>>25 MAT Low (<0.3V)
>>33 MAP High
>>34 MAP Low
>>41 No Refrence Pulse
>>42 EST Failure
>>43 Knock Sensor open or shorted
>>44 Oxygen sensor low (<0.25V, >20Sec)
>>45 Oxygen sensor high (>0.45V, >20Sec)
>>51 MEMCAL Error
>>55 A to D error (>5.5V)
>>
>>Hope that this helps
>>Cheers
>>Matt
>>
> >
>Greg Deuerling wrote: >
>>>-----Original Message-----
>>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>>Of Randy M. Dumse
>>>Sent: Friday, January 06, 2006 3:37 PM
>>>To: lpc2000@lpc2...
>>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>>
>>>
>>>
>>>
>>>
>>>>Do you know anything about J1850 (OBDII)?
>>>>
>>>>
>>>>
>>>>
>>>What do you need to know? I've done keyword protocol.
>>>
>>>Randy
>>>www.newmicros.com
>>>
>>>
>>>
>>>
>>I'm a "me too" on this topic :)
>>
>>Is there any documentation out there on how to get info from an OBDII port?
>>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
>>figure out a few commands like oil temp, tran temp, ... It would be nice if
>>there was a document that covered all of the commands. I've Googled quite a
>>bit on the subject and have come up with nothing.
>>
>>Thanks for any info you could give out!!!
>>
>>
>>Greg Deuerling
>>
>>
>>
>>
>>
>>>-----Original Message-----
>>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
>>>Of Randy M. Dumse
>>>Sent: Friday, January 06, 2006 3:37 PM
>>>To: lpc2000@lpc2...
>>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>>>
>>>
>>>
>>>
>>>
>>>>Do you know anything about J1850 (OBDII)?
>>>>
>>>>
>>>>
>>>>
>>>What do you need to know? I've done keyword protocol.
>>>
>>>Randy
>>>www.newmicros.com
>>>
>>>
>>>
>>>
>>>
>>>Yahoo! Groups Links
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>Yahoo! Groups Links
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
> >
>
>Yahoo! Groups Links >
>
Reply by ●January 6, 20062006-01-06
> -----Original Message-----
> From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> Of Onestone
> Sent: Friday, January 06, 2006 4:03 PM
> To: lpc2000@lpc2...
> Subject: Re: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
>
> This gleaned from agoogle for J1850 COMMANDS. tHE 808 MENTIONED IS A
> gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
>
> maybe this will be of some help.
Thanks for the reply,
I've found tons of OBDII diagnostic code info but nothing on how to get the
code.
From my fiddling around with an OBDII scanner and a laptop with a USB CAN
interface OBDII is command driven protocol. If I want the transmission
temperature I have to send a CAN packet with a certain ID, then the engine
controller sends the response back in a different CAN packet.
I was able to get the scanner to just read trans temp and nothing else. I
then saw two CAN packets on the OBDII bus. I was then able to determine
which packet was the actual command and which packet was the response by
using my laptop to send a command. With the scanners help I was able to
figure out which bytes in the packet was the tran temp data and what math I
had to do to get the actual temperature.
So I guess in short, what I need are the commands that get the codes. I've
found enough info to figure out the codes.
Thanks again!
Greg Deuerling
Reply by ●January 6, 20062006-01-06
That's the thing, I don't think there is any free information out
there. You have to pay $$$ to get the docs. What did you manage to find
out? Raw commands? If I knew how to build a simple bus monitor that could
monitor the traffic (probably not difficult) then I could probably reverse
engineer something (as I'm sure most of you could as well).
In any case, I too am looking for info. Elm Electronics has a good
interface chip, but it's $$$ as well.
-- Sean
At 04:49 PM 1/6/2006, you wrote:
> > -----Original Message-----
> > From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> > Of Randy M. Dumse
> > Sent: Friday, January 06, 2006 3:37 PM
> > To: lpc2000@lpc2...
> > Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
> >
> > > Do you know anything about J1850 (OBDII)?
> >
> > What do you need to know? I've done keyword protocol.
> >
> > Randy
> > www.newmicros.com
>
>I'm a "me too" on this topic :)
>
>Is there any documentation out there on how to get info from an OBDII port?
>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
>figure out a few commands like oil temp, tran temp, ... It would be nice if
>there was a document that covered all of the commands. I've Googled quite a
>bit on the subject and have come up with nothing.
>
>Thanks for any info you could give out!!! >Greg Deuerling
Reply by ●January 6, 20062006-01-06
It's not the scancodes themselves we're looking for, but the command
interface to the car computer. Thanks though.
-- Sean
At 05:12 PM 1/6/2006, you wrote:
>For a more complete listing I came across this for Jeep using search
>string "J1850 MESSAGES". This got loads more hits than other efforts.
>
><http://www.stu-offroad.com/engine/scancodes.htm" target="_blank" rel="nofollow">http://www.stu-offroad.com/engine/scancodes.htm>http://www.stu-offroad.com/engine/scancodes.htm
>
>Cheers
>
>Al
>
>Onestone wrote:
>
> >This gleaned from agoogle for J1850 COMMANDS. tHE 808 MENTIONED IS A
> >gENERAL mOTORS hOLDEN (aUSTRALIAN) vehicle.
> >
> >maybe this will be of some help.
> >
> >Cheers
> >
> >Al
> >
> >>Bruce
> >>The fault code 22 you saw was TPS voltage too low.
> >>My manual says that this code is set if TPS voltage falls below 0.15V
> >>
> >>Here is a list of all 808 Fault codes.
> >>
> >>12 System Functioning OK
> >>13 Oxygen sensor Open Circuit
> >>14 CTS low ( <0.7V)
> >>15 CTS High (>4.65)
> >>21 TPS High (>2.5V and MAP <60kPa fot 2 secs)
> >>22 TPS Low (<0.15V)
> >>23 MAT High (>4.9V)
> >>24 VSS Error
> >>25 MAT Low (<0.3V)
> >>33 MAP High
> >>34 MAP Low
> >>41 No Refrence Pulse
> >>42 EST Failure
> >>43 Knock Sensor open or shorted
> >>44 Oxygen sensor low (<0.25V, >20Sec)
> >>45 Oxygen sensor high (>0.45V, >20Sec)
> >>51 MEMCAL Error
> >>55 A to D error (>5.5V)
> >>
> >>Hope that this helps
> >>Cheers
> >>Matt
> >
> >Greg Deuerling wrote:
> >
> >>>-----Original Message-----
> >>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> >>>Of Randy M. Dumse
> >>>Sent: Friday, January 06, 2006 3:37 PM
> >>>To: lpc2000@lpc2...
> >>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
> >>>
> >>>>Do you know anything about J1850 (OBDII)?
> >>>>
> >>>What do you need to know? I've done keyword protocol.
> >>>
> >>>Randy
> >>>www.newmicros.com
> >>>
> >>I'm a "me too" on this topic :)
> >>
> >>Is there any documentation out there on how to get info from an OBDII port?
> >>I had a OBDII scanner hooked up to a Ford truck at one time and was able to
> >>figure out a few commands like oil temp, tran temp, ... It would be
> nice if
> >>there was a document that covered all of the commands. I've Googled
> quite a
> >>bit on the subject and have come up with nothing.
> >>
> >>Thanks for any info you could give out!!!
> >>
> >>
> >>Greg Deuerling
> >>
> >>>-----Original Message-----
> >>>From: lpc2000@lpc2... [mailto:lpc2000@lpc2...] On Behalf
> >>>Of Randy M. Dumse
> >>>Sent: Friday, January 06, 2006 3:37 PM
> >>>To: lpc2000@lpc2...
> >>>Subject: RE: [lpc2000] Re: J1939 stacks for the LPC2xxx's?
> >>>
> >>>>Do you know anything about J1850 (OBDII)?
> >>>>
> >>>What do you need to know? I've done keyword protocol.
> >>>
> >>>Randy
> >>>www.newmicros.com
Reply by ●January 6, 20062006-01-06
> That's the thing, I don't think there is any free
> information out
> there. You have to pay $$$ to get the docs.
I would have said the same thing.
But wouldn't you know it, Wikipedia to the rescue. A good start
anyway. Think the book I had was SAE 2012.
http://en.wikipedia.org/wiki/OBD-II
Randy
www.newmicros.com
> information out
> there. You have to pay $$$ to get the docs.
I would have said the same thing.
But wouldn't you know it, Wikipedia to the rescue. A good start
anyway. Think the book I had was SAE 2012.
http://en.wikipedia.org/wiki/OBD-II
Randy
www.newmicros.com
