ECU address during SvcReadDataByIdentifier

A free API for the communication with control devices according to UDS (ISO 14229-1)
Post Reply
KiranGS
Posts: 6
Joined: Thu 25. Jul 2019, 12:05

ECU address during SvcReadDataByIdentifier

Post by KiranGS » Thu 25. Jul 2019, 12:41

Hello,
In my C# program,
After proper initialization of UDS, and AppMapping - Tester CANID: 0x18DA2AF1, and ECU: 0x18DAF12A
While using SvcReadDataByIdentifier(), I could able to send the request, But I receive NO_MESSAGE response.
Test.png
Test.png (122.72 KiB) Viewed 3782 times
Using PCAN-View, both request and response are OK
PCAN-View Request : 0x18DA2AF1 - 03 22 F1 86
ECU Response : 0x18DAF12A - 04 62 F1 86 01

I could see that my C# Tester sends an additional byte in the beginning of the data. and the response is Negative response.
Tester Request : 0x18DA2AF1 - 01 03 22 F1 86 55 55 55
ECU Response : 0x18DAF12A - 03 7F 03 11
test2.png
test2.png (12.53 KiB) Viewed 3782 times
Please let me know, why SvcReadDataByIdentifier() is causing this additional byte sent.
Waiting for your earliest feedback.

Thanks & Regards,
Kiran

KiranGS
Posts: 6
Joined: Thu 25. Jul 2019, 12:05

Re: ECU address during SvcReadDataByIdentifier

Post by KiranGS » Thu 25. Jul 2019, 12:44

Note : If I change the ECU address to 0x2A, then the additional byte sent from my C# Tester is 2A 22 F1 86, and i get the same negative response 03 7F 03 11

K.Wagner
Software Development
Software Development
Posts: 1080
Joined: Wed 22. Sep 2010, 13:36

Re: ECU address during SvcReadDataByIdentifier

Post by K.Wagner » Thu 25. Jul 2019, 13:08

Hello,

you are using an extended protocol (15765-2 29Bits Extended). Using this protocol, the first byte of the message contains N_TA. Try using normal addressing instead.
Best regards,
Keneth

KiranGS
Posts: 6
Joined: Thu 25. Jul 2019, 12:05

Re: ECU address during SvcReadDataByIdentifier

Post by KiranGS » Thu 25. Jul 2019, 14:09

Sorry, Now I tried using NORMAL diagnostics, Now it is working.

Post Reply