> I'm a "me too" on this topic :)
Start with SAE http://www.sae.org/servlets/index
We had a large standards book from them (iirc) that described
all the protocols, the key codes, and what code meant what. As I
recall it was like $200. I sent it back at the end of the
project, so I'm asking my customer for details, perhaps an ISBN.
There are a number of interfaces, I think one is VPW, PWM and
ISO9141 Iso 14230 (Keyword 2000, or KWP, the one I used)
Yes, look at http://obddiagnostics.com/ . We bought one of those
scan tools and it worked nicely for looking at the traffic. They
even have a schematic of their hardware. More information in
their programmers guide.
We also used
http://www.intrepidcs.com/neoVI/networkProtocols.htm to look at
the CAN bus traffic. They mention J1939 compatibiliity, but I
didn't use it.
Randy
www.newmicros.com
Re: J1939 stacks for the LPC2xxx's?
Started by ●January 6, 2006
Reply by ●January 6, 20062006-01-06
Reply by ●January 6, 20062006-01-06
Hi Andr
> >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.
I designed a suite of RV-C based products. RV-C is a thin layer on top of
J1939. I evaluated the LPC2129 but required J1939 support would not fit.
You can fit a much stripped version of J1939 on the LPC2129.
The commercial offerings for J1939 stacks run from $5kUS to $18kUS+.
Quality varies widely. Microchip has a J1939 implementation (cough...hack)
for zero cost. I would avoid this unless implementing a proprietary closed
loop system that doesn't involve life safety. I would never trust my life
on random free code.
Regards,
Joel Winarske Independent Electronics, Inc.
Joel Winarske
Systems Architect
joelw@joel...
2248 Morlan Drive
Napa, CA 94558
tel: (707) 320-4271
fax: (408) 516-5978
Timezone: GMT -08:00
> >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.
I designed a suite of RV-C based products. RV-C is a thin layer on top of
J1939. I evaluated the LPC2129 but required J1939 support would not fit.
You can fit a much stripped version of J1939 on the LPC2129.
The commercial offerings for J1939 stacks run from $5kUS to $18kUS+.
Quality varies widely. Microchip has a J1939 implementation (cough...hack)
for zero cost. I would avoid this unless implementing a proprietary closed
loop system that doesn't involve life safety. I would never trust my life
on random free code.
Regards,
Joel Winarske Independent Electronics, Inc.
Joel Winarske
Systems Architect
joelw@joel...
2248 Morlan Drive
Napa, CA 94558
tel: (707) 320-4271
fax: (408) 516-5978
Timezone: GMT -08:00
Reply by ●January 6, 20062006-01-06
Do you know anything about J1850 (OBDII)?
-- Sean
At 07:44 AM 1/6/2006, you 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,
>
>Andrbr /> >
>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!
-- Sean
At 07:44 AM 1/6/2006, you 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,
>
>Andrbr /> >
>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!
Reply by ●January 7, 20062006-01-07
http://www.okisemi.com/datadocs/doc-eng/msm6636_ug.pdf
This describes a part that is used to implement the protocol, I haven't
looked at it in any depth, but it may help.
Al
Sean wrote:
>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
>>
> >
>
>Yahoo! Groups Links >
>
This describes a part that is used to implement the protocol, I haven't
looked at it in any depth, but it may help.
Al
Sean wrote:
>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
>>
> >
>
>Yahoo! Groups Links >
>
Reply by ●January 7, 20062006-01-07
Odd comment. I doubt that they consider their code to be Random. Other
Microchip implementations have been reliably functional, if not always
awe inspiring. Their USB, TCP/IP stuff etc is solidly boring. I would
rather trust this than some $18k package that may very well have been
brewed up by a hobbyist. just because it's a commercial offering doesn't
mean it's reliable, I mean look at windows, the PSP, etc etc.
Al
Joel Winarske wrote:
>Hi Andr >
>>>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.
>>
>>
>
>I designed a suite of RV-C based products. RV-C is a thin layer on top of
>J1939. I evaluated the LPC2129 but required J1939 support would not fit.
>You can fit a much stripped version of J1939 on the LPC2129.
>
>The commercial offerings for J1939 stacks run from $5kUS to $18kUS+.
>Quality varies widely. Microchip has a J1939 implementation (cough...hack)
>for zero cost. I would avoid this unless implementing a proprietary closed
>loop system that doesn't involve life safety. I would never trust my life
>on random free code.
>
>Regards,
>Joel Winarske >Independent Electronics, Inc.
>Joel Winarske
>Systems Architect
>joelw@joel...
>2248 Morlan Drive
>Napa, CA 94558
>tel: (707) 320-4271
>fax: (408) 516-5978
>Timezone: GMT -08:00 >
>Yahoo! Groups Links >
>
Microchip implementations have been reliably functional, if not always
awe inspiring. Their USB, TCP/IP stuff etc is solidly boring. I would
rather trust this than some $18k package that may very well have been
brewed up by a hobbyist. just because it's a commercial offering doesn't
mean it's reliable, I mean look at windows, the PSP, etc etc.
Al
Joel Winarske wrote:
>Hi Andr >
>>>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.
>>
>>
>
>I designed a suite of RV-C based products. RV-C is a thin layer on top of
>J1939. I evaluated the LPC2129 but required J1939 support would not fit.
>You can fit a much stripped version of J1939 on the LPC2129.
>
>The commercial offerings for J1939 stacks run from $5kUS to $18kUS+.
>Quality varies widely. Microchip has a J1939 implementation (cough...hack)
>for zero cost. I would avoid this unless implementing a proprietary closed
>loop system that doesn't involve life safety. I would never trust my life
>on random free code.
>
>Regards,
>Joel Winarske >Independent Electronics, Inc.
>Joel Winarske
>Systems Architect
>joelw@joel...
>2248 Morlan Drive
>Napa, CA 94558
>tel: (707) 320-4271
>fax: (408) 516-5978
>Timezone: GMT -08:00 >
>Yahoo! Groups Links >
>
Reply by ●January 7, 20062006-01-07
> Odd comment. I doubt that they consider their code to be Random.
Other
> Microchip implementations have been reliably functional, if not always
> awe inspiring. Their USB, TCP/IP stuff etc is solidly boring. I would
> rather trust this than some $18k package that may very well have been
> brewed up by a hobbyist. just because it's a commercial offering doesn't
> mean it's reliable, I mean look at windows, the PSP, etc etc.
Not odd at all. It's a hack in light of requiring a J1939 compliant device.
Perhaps more a marketing push to show they have something for the Automotive
sector. The Microchip CANopen stack is better.
The ~18k package is from CAN-Vector. http://www.vector-cantech.com/
In the automotive sector they are the leader at what they do. The majority
of other vendors are integrators who are selling their not-so refined or
tested code base from past projects. Joel
> Microchip implementations have been reliably functional, if not always
> awe inspiring. Their USB, TCP/IP stuff etc is solidly boring. I would
> rather trust this than some $18k package that may very well have been
> brewed up by a hobbyist. just because it's a commercial offering doesn't
> mean it's reliable, I mean look at windows, the PSP, etc etc.
Not odd at all. It's a hack in light of requiring a J1939 compliant device.
Perhaps more a marketing push to show they have something for the Automotive
sector. The Microchip CANopen stack is better.
The ~18k package is from CAN-Vector. http://www.vector-cantech.com/
In the automotive sector they are the leader at what they do. The majority
of other vendors are integrators who are selling their not-so refined or
tested code base from past projects. Joel
