Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Difference between revisions of "J1939"

From eLinux.org
Jump to: navigation, search
Line 2: Line 2:
 
= SAE J1939 in Linux =
 
= SAE J1939 in Linux =
 
== overview ==
 
== overview ==
 +
See also on [http://en.wikipedia.org/wiki/J1939 Wikipedia].
 +
 
SAE J1939 defines a higher layer protocol on CAN. It implements a more
 
SAE J1939 defines a higher layer protocol on CAN. It implements a more
 
sophisticated addressing scheme and extends the maximum packet size above
 
sophisticated addressing scheme and extends the maximum packet size above

Revision as of 14:48, 13 March 2013

SAE J1939 in Linux

overview

See also on Wikipedia.

SAE J1939 defines a higher layer protocol on CAN. It implements a more sophisticated addressing scheme and extends the maximum packet size above 8 bytes. Several derived specifications exists, which differ from the original j1939 on the application level, like MilCAN, NMEA2000 and especially ISO-11783 (ISOBUS). This last one specifies the so-called ETP (Extended Transport Protocol) which is has been included in this implementation. This inclusion results in a maximum packet size of ((2^24)-1)*7 bytes

Specifications

  • SAE J1939-21 : data link layer
  • SAE J1939-81 : network management
  • ISO 11783-6  : Virtual Terminal (Extended Transport Protocol)

Sources

Support for SAE J1939 in Linux consists of 3 parts:

You probably want all 3 components to get a J1939 linux node working.

The final goal is to have these source trees mainlined.

Howto

todo...