When using the XCP function of the Labview ECUMC tool, the CANFD reply cannot be parsed normally

[WhyNT]

If the parameter read is greater than 8 bytes, an error will be reported (in fact, the ECU has replied normally). When it is less than or equal to 8 bytes, everything is normal. Switching to CANApe can read and write normally。The above picture is the bus message I monitored with PCAN。

[WhyNT]

I have been troubled by this problem for a long time. Is there a bug in the underlying interaction function of XCP? Setting MAX DLC does not work.

[ZYOng]

Since you can communicate with Vector CANape but not NI-XNET, I suspect it is a baud rate sample timing issue.

By default, NI-XNET uses 87.5% of the sample point on most baud rates and Vector devices use 75%. Try using a custom baud rate with a 75% sample point in How Can I Use XCP on CAN FD at ECUMC Toolkit?

How Can I Set Custom Baud Rates on NI-XNET Devices?

[TroyK]

Are you sure that your XCP configuration is using the CAN-Transport-Layer_V1-2-0 which supports CAN-FD and therefore DLC > 8? 

[WhyNT]

Thank you for your reply! However, I’m not sure how to determine whether the CAN-Transport-Layer_V1-2-0 is being used. Could you please guide me on how to check this configuration?

[WhyNT]

Thank you for your reply. There is no problem with communication. DAQ and single-point Characteristics can be read normally. It is just that the two-dimensional Characteristics (when the total number of bytes is greater than 😎 cannot be parsed normally by the XCP toolkit after reply.