UDS Protocol Settings in LabVIEW using NI USB 8473

[Vikram_M]

Hi,  I have been recently introduced to this protocol for diagnostics on ECU.

What I want to do :-

I want to read the broadcasted messages from ECU using the program called "UDS Diagnostic Demo" that is available within Example set provided under help section in LabVIEW.

What I know:-

I can communicate with ECU just fine with the NI-CAN VIs and same hardware (NIUSB 8473) that I used initially to monitor the CAN messages.

What I want to know:-

1. I am not sure about the parameters that I would have to put in under Protocol Settings section if I am using UDS protocol?
2. What are Transmit and Recieve IDs, are these some standard values or ECU specific?
3. For ISO TP Normal and UDS mode selected - I learned I do not need to worry about Channel ID and Transmit/ Recieve Address Extensions but do I care about Periodic CAN ID ?

 Also while reading this forum I came across a topic where it was mentioned to use Transmit and REcieve ID as 7E8 and 7E0 respectively. I tried that as well but no luck.

Using values as specified in the screenshot I am able to run the VI and it does not give any errors but it does not give me any ECU respinses either.

Any help will be highly appreciated.

Thanks,

Vicky

[fromm8]

Hi Vicky

Did you review the Automotive Diagnostic Command Set User Manual? or you already reviewed it and you are looking for something else?

Regards

Frank R.

[Vikram_M]

Hi Frank,
Yes i already went through the user manual. I didnt get the answers i was looking for.
But meanwhile i have been able to use transmit id and receive id of 7E0 and 7E8 respectively bit with examples of OBD protocol. But when i try to use the same with UDS VIs it gives me error.

Now my question is do i have to have key and seed before i can query ecu using service IDs?

Vicky

[fromm8]

Hi Vicky

I would like to get on this deeper. Could you point me to the discussion forum that mentioned the ID 7E0 and 7E8 and could you tell me the error code or message please?

Regards

Frank R.

[Vikram_M · Accepted solution]

Hi Frank,

I am back with the solution. I was successful in reading ECU information such as part number, serial number, other engine parameters such as temperature, pressures, battery voltage and so on and on.

When using the LabVIEW example VIs for UDS protocol you dont need any of the fields set under protocol settings for open diagnostic.vi except Transmit and Receive ID. (Transport Protocol set to ISP TP- Normal)

After further reading on different ECU. I found out that Transmit ID - 7E0 and Receive ID - 7E8 are aone of the most common IDs to communicate with most ECUs from major manufacturers such as Delphi.

As far as service ID goes you can find standard IDs based on UDS protocol here. For propreitery IDs you need help from manufacturer or Integrators.

http://www.neweagle.net/support/wiki/index.php?title=Unified_Diagnostic_Services

Let me know if you have any questions.

Thanks,

Vicky

[fromm8]

Hi Vicky

Good to hear, and thanks for the feedback. Coud you mark that comment as the answer?

Regards

Frank R.

[Brzhou]

So the UDS is just using CAN BUS+labview(XNET) to read and write info to MCU ?

And base on the UDS format to phase the data, then know the status of the car/sensors ?

Thanks.