Closed jlgreene2 closed 3 years ago
Nothing to worry about, "controller.vel_setpoint" has been changed to "controller.input_vel" for the latest firmware. Update pushed. Thanks!
Well, after one last change in odrive_utils.cpp, I was able to at least get the wheels spinning. So I'll take that as progress.
int calibrateAxis1(odrive_endpoint *endpoint, Json::Value odrive_json)
{
float fval;
uint8_t u32val; <---- I had to change this to a uint32_t datatype
bool bval;
I guess I'll spend the day today getting my differential drive code working properly now. Thanks so much for the help!
I wrote a very basic Python class to accept cmd_vel messages and translate them into odrive_ctrl messages. Upon initialization, the class sends CMD_AXIS_CLOSED_LOOP commands to both axis0, and axis1, without errors. But when I start processing cmd_vel messages, I attempt to send CMD_AXIS_SET_VELOCITY_DUAL commands, and get the following errors:
I added some logging into the odrive.cpp source, to print the values in the odrive_ctrl messages before being submitted to the motor controller.
Here's the source for my Python class. Is there something in the process of setting things up that I have missed?