PEAK-System Forum

As far as I understand, you want to apply a use case which goes against the standard, and this is indeed not possible.
- For UDS requests where data fit in a single frame, UDS_Svc functions will adapt the dlc to the real data length.
- Otherwise the UDS_Svc functions will use the configured can_tx ...

The problem of using your proposal of building my own uds_message is that I'm not only using a single frame. Most of the frames are Consecutive Frames specially when I'm using the "UDS_SvcWriteDataByIdentifier_2013".
I write data more than 64 bytes which are sent in multi Consecutive frame.

So, you ...

I think the problem is not in the DLC itself but in the CAN frame itself.
I noticed that its a Standard CAN frame which starts with the DLC and then followed by the data like the one in ( [02] 10 03 )
But I was expecting the CAN FD frame which starts with ( [00 02] 10 03 )

I need to know why the ...

Thank you for quick reply.
And yes can_data_padding is enabled.

I tried to set the (PUDS_PARAMETER_CAN_TX_DL) with 15 but the result still the same and I can't send the FD frame which starts with (00) as in the expected request above.
Is there any idea where the problem is ?

Hello,
I have a problem with CAN FD while requesting any UDS Service like (SvcDiagnosticSessionControl_2013).
I set the value of DLC (can_tx_dlc) in (uds_msgconfig request_config) with 15. But when I checked the value of DLC in (uds_msg out_msg_request.msg.can_info.dlc) after sending the service I ...