-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAN J1939 Support #30724
Comments
@jukkar @alexanderwachter requesting for comments and feedback. |
That is the way to go if you want support socket interface for this protocol. Your plan looks ok to me. |
@Navin-Sankar don't forget that you are not allowed to copy any code from the Linux kernel (GPL licensed) to the Zephyr repository. Only Apache licensed or compatible code is allowed. |
@Navin-Sankar do you have some news about you work on J1939 ? I may be interested to use it too. |
@Navin-Sankar Any work done on this yet that you can share? |
No progress here. We can reopen if there is progress on this issue |
Is your feature request related to a problem? Please describe.
SAE J1939 is the vehicle bus recommended practice used for communication
and diagnostics among vehicle components. Originating in the car and
heavy-duty truck industry in the United States, it is now widely used in
other parts of the world.
J1939, ISO 11783 and NMEA 2000 all share the same high level protocol.
SAE J1939 can be considered the replacement for the older SAE J1708 and
SAE J1587 specifications.
Describe the solution you'd like
In linux there is separate implementation for SAE J1939 protocol (net/can/j1939/).
Likewise I try to add j1939 protocol support in zephyr by creating sockets_j1939.c file in subsys/net/lib/sockets directory to handle the socket type: SOCK_DGRAM and protocol: CAN_J1939
The text was updated successfully, but these errors were encountered: