mirror of
https://github.com/odriverobotics/ODrive.git
synced 2026-02-05 22:52:02 +08:00
Update changelog
This commit is contained in:
13
CHANGELOG.md
13
CHANGELOG.md
@@ -3,15 +3,16 @@
|
||||
|
||||
### Fixed
|
||||
|
||||
* Fixed race condition in homing sequence that was causing strange behaviour
|
||||
* When using a load encoder, CAN will report the correct position and velocity
|
||||
* When using a load encoder, homing will reset the correct linear position
|
||||
* Implemented CAN controller message, which was previously defined but not actually implemented
|
||||
* Get Vbus Voltage message updated to match ODrive Pro's CANSimple implementation
|
||||
* Fixed race condition in homing sequence that was causing strange behaviour. Fixes [#634](https://github.com/odriverobotics/ODrive/issues/634)]
|
||||
* When using a load encoder, CAN will report the correct position and velocity.
|
||||
* When using a load encoder, homing will reset the correct linear position. Fixes [#651](https://github.com/odriverobotics/ODrive/issues/651)
|
||||
* Implemented CAN controller error message, which was previously defined but not actually implemented.
|
||||
* Get Vbus Voltage message updated to match ODrive Pro's CANSimple implementation.
|
||||
* vel_setpoint and torque_setpoint will be clamped to vel_limit and the active torque limit. Fixes [#647](https://github.com/odriverobotics/ODrive/issues/647)
|
||||
|
||||
### Added
|
||||
|
||||
* Added public `controller.get_anticogging_value(uint32)` fibre function to index into the the cogging map
|
||||
* Added public `controller.get_anticogging_value(uint32)` fibre function to index into the the cogging map. Fixes [#690](https://github.com/odriverobotics/ODrive/issues/690)
|
||||
* Added Get ADC Voltage message to CAN (0x1C). Send the desired GPIO number in byte 1, and the ODrive will respond with the ADC voltage from that pin (if previously configured for analog)
|
||||
* Added CAN heartbeat message flags for motor, controller, and encoder error. If flag is true, fetch the corresponding error with the respective message.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user