I try to implement a vendor-specific data type to configure my ESC’s. I know the structure of the message and the DSDL signature. Unfortunately, I don’t know the exact DSDL defintion of the message. As a result, I was able to implement a DSDL with the correct structure but with the wrong DSDL signature. When I try to read the message with the UAVCAN-GUI I get a CRC mismatch because the ESC uses an other DSDL signature to compute the CRC than the UAVCAN-GUI.
How can I solve this issue? Is there a possibility to pass a specific DSDL signature for the CRC computation or a directive I can use in the DSDL defintion for the compiler to output a specific DSDL signature?
I still use v0 UAVCAN and use multi frame transfer for the message. I think in v1 there’s versioning to solve this issue but for the moment I cannot update to v1.
Thank you for your help!