Hello,
We are exploring PCAN-UDS example.
When testDiagnosticSessionControl [from PCAN-UDS\Samples\C++\06_client_all_request ] is executed, the ECU is able to receive the request and send the response (Please refer the PCAN view snapshot).
But the status = UDS_WaitForService_2013(channel, &request, &response, &confirmation); ends up with PUDS_STATUS_SERVICE_TIMEOUT_RESPONSE".
Could you please help us to identify the short comings, if any, and what the corrective actions we need to take to get the response on the example code.
Thank you in advance
UDS_WaitForService_2013 returns PUDS_STATUS_SERVICE_TIMEOUT_RESPONSE , while PCAN View displays response
UDS_WaitForService_2013 returns PUDS_STATUS_SERVICE_TIMEOUT_RESPONSE , while PCAN View displays response
- Attachments
-
- error_snap.PNG (23.46 KiB) Viewed 1897 times
-
- Software Development
- Posts: 305
- Joined: Mon 9. Sep 2013, 12:21
Re: UDS_WaitForService_2013 returns PUDS_STATUS_SERVICE_TIMEOUT_RESPONSE , while PCAN View displays response
Hello,
The CAN IDs you are using to communicate with your ECU (0x59A and 0x5A2) are not standard ones and therefore are not configured by default in the API.
You need to configure mappings in order to successfully transmit and receive responses (note that without those mappings the API is only able to transmit single frame request as it is the case in your screenshot).
You can find an example of UDS_AddMapping_2013 in example "07_read_write_uds" and in the user manual §3.8.6.
The CAN IDs you are using to communicate with your ECU (0x59A and 0x5A2) are not standard ones and therefore are not configured by default in the API.
You need to configure mappings in order to successfully transmit and receive responses (note that without those mappings the API is only able to transmit single frame request as it is the case in your screenshot).
You can find an example of UDS_AddMapping_2013 in example "07_read_write_uds" and in the user manual §3.8.6.
Best regards,
Fabrice
Fabrice