-
Notifications
You must be signed in to change notification settings - Fork 717
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
Cannot send zero length j1939 messages. #564
Comments
@xile273 , good point. Thx! |
Hello, |
i'll be very happy if there are more hackers in the stack :) |
I did get it to work, see xile273/linux@3bf3fa0. |
Nice, you can test it at least with vcan and following test scripts: https://github.com/linux-can/can-tests/tree/master/j1939 For example you can run: ./j1939_ac_1m_local0.sh vcan0 vcan0 |
They all seem to work on vcan as well as mcp2518fd |
ok, can you please prepare the patches and send them upstream? |
Should we put [email protected] on Cc? |
yes, good point |
Ok will do so in the next days! |
Sorry, I was very busy the last weeks, finally sent a patch. |
Also I just want to add that the examples are not really correct, I misread the standard. DM11 and DM55 are not sent directly just as requests. Thats why their data length is specified is zero. |
Hello,
sorry to bother you again regarding the J1939 implementation.
It seems it is impossible to send J1939 messages with data length 0.
Unfortunately the J1939 standard requires the transmission of such messages,
for example J1939-73 DM11 (5.7.11.3) or DM55 (5.7.55).
Receiving such messages is possible though.
Thank you for your help!
The text was updated successfully, but these errors were encountered: