Status of can-j1939 integration into linux kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am currently considering to write a test port for Eclispe Titan TTCN compiler for the isobus, as I have done for the socketcan-interface (CAN, CAN_FD) before.

In the past I have tested https://github.com/kurt-vd/test-can-j1939. It work fine, but requires selfbuild kernel.

As taking this effort makes only sense if the j1939 / isobus socketcan in interface is stable and widely available I would like to know:

What is the status of the j1939 / isobus integration into the mainline kernel?

Michael
-----------------------------------------------
Background: 
This would allow encoding/sending, decoding/receiving and logging Isobus messages into almost clear text.  

Here are already found some encoders and decoders for Isobus:
https://projects.eclipse.org/projects/tools.titan/developer

An Isobus  VT message would e.g. look like the following in textual form:
{ can_j1939 := { prio := '000000'B, res := '0'B, dp := '0'B, pf := '00'O, ps := '00'O, sa := '00'O, comp := '000000'O }, can_pdu := { vt2ecu := { vtStatusReq := { vtfunction := 254, sourceAddressOfActiveWorkingSetMaster := '11'O, objectIDOfTheVisibleDataAlarmMaskOfTheActiveWorkingSet := '2233'O ("\"3"), objectIDOfTheVisibleSoftKeyMaskOfTheActiveWorkingSet := '4455'O ("DU"), vtBusyCodes := vtIsBusyExecutingACommand (2), vtFunctionCode := '66'O ("f") } } } }



[Index of Archives]     [Automotive Discussions]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [CAN Bus]

  Powered by Linux