We’ve been trying to communicate with the ODrive via CAN with a CAN Bus Analyser.
We’ve been unable to communicate from the Analyser to the ODrive. We see data being transferred with an oscilloscope, but we think the ODrive is not interpreting it correctly, or better, that what we send is encoded in the wrong way to accomodate for ODrive’s specific protocol.
In the figure above, for reference, we are setting the CAN address of the ODrive (3), and telling the analyser to send a message of 1 byte length containing the message to be received by the ODrive.
This is likely not how the ODrive expects it, but I don’t see how else we should generate the message.
We have a similar problem receiving the heartbeat (which we do receive), where the address of the incoming information is thought to be 0x21 rather than 0x03.
Is there something wrong with how we are approaching the communication? Like using the wrong protocol? If so, are there other known tools we could use to test the ODrive from either our PC or from other devices?
As far as we understand, all existing CAN-enabled devices use the same protocol, and they would not match with ODrive’s SimpleCAN.
Thanks in advance