Hi,
We’re currently debugging an issue with the ODrive Pro CAN interface. The ODrive connections are identical to a previous project we’ve used with a Pro (albeit with slightly older firmware). CAN ground is connected to DC- and the bus appears to be terminated correctly. The bus speed is 500kbit/s. Compare to our previous project the bus is slightly longer at around 30m, as opposed to the previous 24m.
We’re receiving the ODrive heartbeat messages (and all other cyclic messages) on the CAN bus but the ODrive does not respond to any messages we send it (e.g. Set_Input_Pos or TxSdo and RxSdo). As we’re receiving the cyclic messages without any problems, we’re assuming that it isn’t a problem with the physical configuration of the CAN bus. n_rx remains at zero during the time period where we send the ODrive messages.
The ODrive firmware version is 0.6.11, which is slightly newer than the firmware version we used previously (0.6.10). Are there any new ODrive configuration settings that need to be set in order for the ODrive to respond to CAN commands? Are there any recommended debug steps?