Skip to content
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

UDS or OBDII protocol #30

Open
Daparrag opened this issue Sep 1, 2021 · 3 comments
Open

UDS or OBDII protocol #30

Daparrag opened this issue Sep 1, 2021 · 3 comments

Comments

@Daparrag
Copy link

Daparrag commented Sep 1, 2021

Hi All

Hope you are doing well and congrats for supporting automotive protocols.

My question is the following:

There is a clear difference between what is UDS and OBDII protocols as is pointed in the following article https://incardoc.com/en-us/article/the-difference-between-uds-and-obd-protocols/

If I am not wrong your implementation only support OBD messages. is this true?
if so how can I send standard UDS messages? do you have any example?
if not how can adapt your implementation for that? there is a easy way to do it.

hope you can respond soon.

Cheers,

@Satnet
Copy link

Satnet commented Sep 5, 2021

I'm wondering the same!

@zdf0145
Copy link

zdf0145 commented Oct 15, 2021

I have the same problem, I cannot find the UDS service in the project, for example: 0x19 read DTC Information

@Daparrag
Copy link
Author

This library is more OBDll library than UDS. If you want to have standard UDS, as I presume you do, you will end up modifying the source code to add the functionality you need.

The isotp library is great however is quite limited. I recommend you to make a look of the isotp module implemented on Linux. Isotp will package your UDS frame and send it over can.

If you think about it, you don't really need this lib for UDS. You can instead get some ideas and implement by yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants