10-15-2019 01:27 PM - edited 10-15-2019 01:36 PM
I am trying to connect to a DoIP compliant DUT using the "UDS Diagnostic Comander.vi" example. However I get an undefined error -8305 after I try to activate routing. Get entities.vi returns the correct IP and VIN of the DUT I am connected to but it fails at activate routing. I am running ADCS 18.5.0f3. See the Block diagram screenshot below.
Does anyone have experience running with DoIP in LabVIEW, or know why I might get this error?
How would I do a loopback test in DoIP like with CAN to verify the functionality of the examples in LabVIEW.
Current modified example to add source and target address and IP of DUT
Solved! Go to Solution.
10-16-2019 06:33 AM
The error code -8305 means that the “Routing Activation Response” that the “UDS Diagnostic Commander.vi” received from the ECU is not correct.
To ensure a valid response, you could do the following:
You could also debug the protocol trace using Wireshark with the help of ‘doip’ filter or post the traces here.
Further, to verify the functionality of DoIP in LabVIEW, you could run one of the examples (say “UDS Read ECU Identification.vi”) against ”ADCS Demo ECU CAN Ethernet.vi”. Make sure that the Transport Protocol chosen on the front panel of these VIs is ‘Diagnostics on IP’.
10-20-2019 10:29 AM
The Wireshark DoIP protocol trace was extremely helpful! Turns out there was a bug in the ECU.
Thanks