samuelsadok
samuelsadok
I haven't seen this on original hardware before so it might be caused by an unstable STM32 voltage supply. I think you can add `-c 'flash verify_image $(FIRMWARE)' \` after...
Can you give a brief description about your use case for this CAN message? In particular, is it necessary to change this variable at runtime (while the machine is in...
The mechanical brake engages automatically when going to IDLE state. Would it be viable for you to use a state change to IDLE instead of calling `mechanical_brake.engage()`?
Thanks for the suggestions. I think these are some good inputs on possible homing use cases. I think from an implementation perspective the key is to decouple a bunch of...
Thanks for bringing this up. We put a fix in our next-generation firmware for this. With this fix, when you increase the velocity limit, the setpoint doesn't jump up anymore...
The string variant is the correct one. However the Fibre protocol currently does not support string properties. Therefore fixing this would either be fairly hacky or non-trivial.
Well `odrive.dump_serial_nr(odrv0)` would be equivalent to `hex(odrv0.serial_number)`. But yeah it's not a huge priority at the moment.
Were you trying with firmware v0.5.4 or with the latest `devel`? I believe on `devel` this issue should already be fixed as we added back the `AXIS_ERROR_MOTOR_FAILED` flag.
Ok you can try with v0.5.5 then which got released just now
I don't think it's quick/easy enough for us to work on it in this context.