i am trying to get my motor (335kv 10 pole) to run in sensorless mode. The motor stops rotating after a few revolutions. The motor should spin with constant velocity.
axis1
axis: Error(s):
AXIS_ERROR_MOTOR_FAILED
motor: Error(s):
MOTOR_ERROR_CURRENT_LIMIT_VIOLATION
fet_thermistor: no error
motor_thermistor: no error
encoder: no error
controller: no error
Hi togther,
i have still the same error. I put the current limit to 20A ( and don´t overwrite it later). 100 Hz is no problem and sounds good (1.3 A!). At 120 Hz the motor switch off immediately. After switsching off the USB connection is lost.
The following error occurs after replugging:
In [53]: dump_errors(odrv0)
axis0
axis: Error(s):
AXIS_ERROR_MOTOR_FAILED
motor: Error(s):
MOTOR_ERROR_CURRENT_LIMIT_VIOLATION
fet_thermistor: no error
motor_thermistor: no error
encoder: no error
controller: no error
Is ther a speed limit for sensorless mode?
Are there other current limit?
more data running at 50 Hz:
In [14]: odrv0.axis0.requested_state = AXIS_STATE_MOTOR_CALIBRATION
In [15]: odrv0.axis0.controller.input_vel = 50
In [16]: odrv0.axis0.requested_state = AXIS_STATE_SENSORLESS_CONTROL
The motor should be good to about 600hz electrical. At 120hz mechanical * 5 pole pairs, you’re at exactly 600Hz electrical, oddly enough. That is the limit that we expect from ODrive v3.
If I use the samples posted above I can get the motor spinning, but the speed appears independant of odrv0.axis0.controller.input_vel = 0 - stopped
odrv0.axis0.controller.input_vel = 10 - runs
odrv0.axis0.controller.input_vel = 20 - runs as 10
odrv0.axis0.controller.input_vel = 200 - runs as 10
odrv0.axis0.controller.input_vel = 3000 - runs as 10
(using a J-drone motor that I think has 3 poles, 850KV - 3.6 board and the latest firmware)
It’s because we only have two current shunts and the 3rd phase is calculated. Unfortunately we can only sample the shunts during certain phases of motor commutation, which means there is a bit of a “dead band” where we can only measure one shunt and not both. This has pretty significant effects on the drive’s ability to compensate. v4 will not have this problem