-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Adding parameter to Communication Control Service(0x28) #216
Comments
If there is a feature missing, I can implement. |
I reviewed the doc. This parameter has been introduced in the 2013 version of the standard. My initial version of this lib was based on the 2006 version, I never noticed this was added and nobody asked for it. |
I have started the work here : https://github.com/pylessard/python-udsoncan/tree/add_node_id_number_to_comm_control It's untested |
I see. You will have enough bits, the parameter is 16 bits I don't think there is best practices for adding a session. Or I'm not aware of any. Just pick a number |
As I said adding a session is not relative to this topic. I want to prepare the base for future projects. That why I want to create separate OEM specific sessions. |
Implementation is complete. |
Hi, good news, thank you
cheers |
Added support for nodeIdentificationNumber in communicationControl service (2013,2020) Fixes #216
Available in release 1.23.0 |
Hi,
First of all its not a issue, this is a question about modifying udsoncan library.
As I see you haven't add the "nodeIdentificationNumber" parameter for Communication Control service. I need this parameter for my project. Before forking and diving into library I wanted suggestions from you. Ofc I can do it in a manual way but I want to save some time. If I'm successful, you can be sure I'll open a PR
Best regards.
The text was updated successfully, but these errors were encountered: