-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Act as server and parse python-can messages #211
Comments
Hi Let me know if I can help, you have some doc reading to do first I believe :) |
@pylessard thank you - but which one project you're talking about? :D Can you please point me some example or code line to get familiar with? I think you're talking about python-isotp. |
I have 2 projects, the other one is called python-can-isotp. Which implements the isotp protocol as per above comment. |
@pylessard sorry for asking stupid questions, but as I understand I need to implement custom |
Don't hack it. Isotp headers are not always 1 byte. You need a custom rxfn/txfn if you have specialized hardware. If you use python-can, the work is already done. See this example : https://udsoncan.readthedocs.io/en/latest/udsoncan/examples.html#using-uds-over-python-can |
@pylessard Thank you mate :* Probably have all what I need. Have a nice evening. |
Hey,
I'm trying to act as a server-side with udsoncan but I'm facing some issues related to parsing.
I'm receiving can message with data:
arbitration_id [DLC] DATA, where 03 - is msg length, 22 - service, d1 00 is content and 00 00 00 00 is padding.
When I try to use:
Request.from_payload()
it cannot parse because the service is on the second position, not the first. I can of course use data[1:] to pass this failure, but then I'm trying to do a response like:What I'm sending is:
What I'm expecting to send is:
I'm not very familiar with can, but the lacking parts in the payload are length (03) and service (d1 00)
What I did do wrong?
The text was updated successfully, but these errors were encountered: