Other Parts Discussed in Thread: HALCOGEN,
Tool/software:
Hello,
We are experiencing issues while implementing the FlexWire protocol over a CAN interface to communicate with our driver. Below is a detailed description of the problem:
Context:
We have successfully implemented the FlexWire protocol and connected it via a serial interface (SCI) from a Hercules TMS570LC43. Through this method, we send a synchronization byte (sync), the device address (dev addr), register address (reg addr), and a calculated CRC. Using this serial interface, we are able to control the drivers without any issues.
Issue with CAN Protocol:
When we attempt to perform the same communication using the CAN protocol, we encounter issues. We have configured the CAN bus parameters using Halcogen, including the ID, frequency, and other relevant settings. On the CAN bus (CAN_H and CAN_L), we can observe the messages with the configured parameters as expected. The data bytes include the synchronization byte, device address, register address, and the calculated CRC, just like with the serial interface. However, the drivers do not respond to these messages when communicated over the CAN bus.
We would like to know the correct procedure for utilizing the CAN interface with the FlexWire protocol. Specifically, are there additional considerations or configurations required for the CAN protocol that differ from the serial implementation? Could there be any timing, message framing, or data interpretation issues specific to the CAN interface that we might be overlooking?
Any guidance on how to properly implement the FlexWire protocol over the CAN interface to ensure successful communication with the drivers would be greatly appreciated.
Thank you for your support.