03-09-2021 02:47 AM - edited 03-09-2021 02:49 AM
Hello
I wonder whether XNET supports conversion between signal and frame of CAN FD .
We know that payload length maximum is 64 in CANFD database but XNET conversion is 8 .
Hope your help sincerely.
03-11-2021 05:49 AM
Is there a way to configure payload length?
03-27-2023 07:31 AM
Hey, guys, have you solved this problem? How did you solve it? I am currently experiencing the same problem and reporting the same error
03-27-2023 09:11 AM
This question is best to be posted at Automotive and Embedded Networks board.
The shipping example is still good to be used with the CAN FD, as long as all the signals have a size smaller than a byte. Otherwise, you would need to use the byte array for the conversion. Make sure that your frames have the I/O mode of CAN FD. A cluster of CAN FD can have both CAN 2.0 and CAN FD frames. Using CAN and CAN FD in same NI-XNET Interface
03-28-2023 05:04 AM
"I used the. dbc file in the zip file, but it still couldn't be parsed. The error message still prompted me that it exceeded 8 bytes."
The way I tried it was: I used the xml file in the zip file, and I used XNET to convert it to a. dbc file. Then, I only retained one frame of data inside, and deleted the other data. Then, I saved the retained frame of data as' test32byte. dbc '. "Then I will import this frame as my dbc file into the project for parsing. There are no errors reported in the 'Signal to Frame CAN' step, but an error exceeding 8 bytes is still reported in the 'Frame CAN to Signal' step'. I don't quite understand the difference between this and the paradigm. Or where is my problem.
03-28-2023 09:06 AM
Kindly please upload the database file and the VI you used, this would help to save our time to try reproducing your issue from scratch. Uploading only images requires us to guess what you are trying to do.
Using the DBC exported from the XML and then reimported, running in the same VI I uploaded, no issue was found.
03-28-2023 09:29 AM
Thank you very much for your answer. Just after replying to you, I tried again to check my program and data, and finally let me find the cause of the error. The reason for the error lies in: I defined the data uploaded by. CANFD as 64 bytes, as I stated in my previous reply that my. DBC is 32 bytes, so later I guess it was caused by this. So I redefined. dbc as 64 bytes and successfully parsed it. Finally, thank you for your answers and assistance, and send my most sincere gratitude.