ODrive
ODrive copied to clipboard
odriverobotics
High performance motor control
I'm trying to make a steering wheel using MMOS or EMC type controllers, they all output a PWM signal: PWM+- or PWM+ DIR or PWM one wire 0-50-100 , but...
**Describe the bug** `odrv0.serial_number` is an int whereas in `discover_any(serial_number)` the serial number is expected as a hex string. I think this should be coherent. Somewhere there should be a...
**Due to the current way homing is implemented through the min_endstop, issues #634 and #625 arose.** Industrial motion controllers often offer double-layer endstop switches in which the first endstop pressed...
**Describe the bug** Some enums (e.g. Motor::Error) have values that are too large for the underlying type. All values above 2^32 are replaced with 0 (e.g. `Motor::Error::NONE`) For Motor::Error, this...
**Describe the bug** In the latest "release candiate" firmware (e.g. v0.5.2 release #562) , Requesting the axis motor error does not respond with a number, but a string "lu" instead....
This adds a new axis state `AXIS_STATE_BRAKE` that is the same as closed loop control with forced velocity control & zero velocity input. The main purpose of this new state...
**Describe the bug** - Homing does not reset the loaded encoder position - CAN interface reads position estimate from "own" encoder **To Reproduce** - Use secondary encoder input with an...
**Describe the bug** Quoting `Firmware/odrive-interface.yaml`, `INPUT_MODE_VEL_RAMP` "Ramps a velocity command from the current value to the target value", not the actual velocity. This can cause sudden velocity jumps, as shown...
**Describe the bug** I have setup an odrive with firmware v0.5.3 and configured following the docs instructions. I enabled min endstop for the axis and set it to search home...
Suggestion to force this in firmware by modifying brake timings rather than a control element in series with the braking resistor.