Moteus

Latest version: v0.3.74

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

0.120230605

* Improve ADC performance across all moteus revisions

0.120230531

Resolve output drift with non-unity `motor_position.rotor_to_output_ratio`:

Previously, for some values of `motor_position.rotor_to_output_ratio`, the output position could drift over time. This would manifest as an incorrect reported position, and if under control, an incorrect controlled position. Torque and velocity control worked correctly, and still do. This was most common with irrational or non-power of two ratios, although the rate of drift varies depending upon what ratio was selected.

Improve initialization of AS5047P encoder

When using the onboard AS5047P encoder, the relative position was previously incorrectly offset from 0.0 on startup, which could result in the output position not being within +-0.5 * rotor_to_output_ratio as intended.

Support moteus-n1 r1.3 boards

0.120230323

* Make the I2C startup delay 30ms and be configurable
* moteus-n1 boards now have a default flux braking minimum voltage of 52V

0.120230315

* Improve ADC performance
* This fixes a regression for moteus-r4.11 boards in 2023-03-10
* It also generally improves the performance for moteus-n1 boards

0.120230310

* Support the moteus-n1
* Fix possible inability to flash after reconfiguring aux ports
* Improve hardware board version detection reliability

0.120230201

* Support sending and receiving arbitrary data from a UART configured on one of the auxiliary ports
* when mode 'kTunnel' is selected, then the diagnostic protocol can be used to send and receive data
* aux1 is diagnostic channel 2
* aux2 is diagnostic channel 3
* Permit I2C encoders to operate at up to 1kHz
* Report control position, velocity, and torque as well as the errors in tracking them over the register protocol as registers 0x038 through 0x03d
* Provide support for synchronizing the clock of a moteus controller with a host application.
* In the diagnostic data, report the number of times that hall sensors changed more than one bit at the same time. This is an imperfect measure of problematic hall data, but better than nothing.
* Fix register 0x006 to be reported in revolutions as it previously was and as it is still documented
* Expose the drv8353 fault flags over the register protocol as registers 0x140 and 0x141

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.