PEAK-System Forum

Hello,

I think you took an example that doesn't really match your need:
- based on your description, you only need to do UDS communication,
- the ISOTP part is for transport and is managed by the PCAN-UDS API.
You should draft your code application with sample 02_client_request_ecu_reset_USDT ...

Hello,

Thank you for your feedback. I'll follow the information regarding the support of 'presume-ack' property in the PCAN netdriver driver to our development team.
We'll update this thread when more information is available.

As said before you are describing 2 different things:
- ISOTP the segmented transport protocol (ISO-15765)
- and UDS the diagnostic communication protocol (ISO-14229)
It is unclear whether the frames you are mentioning refers to a segmented UDS request or a segmented UDS response..

Here is what I ...

An ECU should always respond (either positively or negatively) to a UDS request.
If it is positive, response must include (Service_ID + 0x40) in the UDS PCI bytes, this is defined in UDS standard (ISO-14229).
Please keep in mind that explanation of UDS standards is out of scope of our support.

I ...

Your request is sent : size is 0x0C, so it fits in 2 frames "10 0C 2E ..." and "21 ...".
As your trace doesn't show anything else, please check if the ECU is actually responding to your request. If not, then the API is consistent: you have an error code "timeout response" (PUDS_STATUS_SERVICE ...

Hello,

Be careful with your nai.protocol configuration, you're using:
config.nai.protocol = uds_msgprotocol.PUDS_MSGPROTOCOL_ISO_15765_2_29B_NORMAL;
this mode indeed requires a mapping, but due to the CAN IDs you are using it should be best to use 29B_FIXED_NORMAL which does not require mapping ...

CAN IDs 0x18DAxxyy are reserved and standardized for ISOTP FIXED NORMAL addressing.
You can check "§4.3 UDS and ISO-TP Network Addressing Information" page 771 for more information.

You don't need to configure mappings with this configuration, but this means that your node address is either 0x01 or ...

Thank you for your feedback, the initial request is closed.

Regarding your second issue, please update the corresponding thread and send a photo of the adapter showing the serial number to our support email address, to see which hardware you are using.

Hello,

It seems you are confusing UDS addresses and CAN IDs:
- A UDS address is defined during network design and may not be visible in the UDS exchanges. It is an 8-bit value.
- That is why the UDS on CAN standards define mappings which associates Network Address Information with a CAN ID.
ISO ...

Hello,

If you're requesting the status of a channel that is not available (anymore) then this error message is consistent.

To check which channels are available you should use parameter PCAN_ATTACHED_CHANNELS with CAN_GetValue function: it will get information about all existing PCAN channels on a ...