ODrive Versions Save

[0.4.0] - 2018-06-10

Added

• Encoder can now go forever in velocity/torque mode due to using circular encoder space.
• Protocol supports function return values
• bake Git-derived firmware version into firmware binary. The firmware version is exposed through the fw_version_[...] properties.
• make write_otp command to burn the board version onto the ODrive's one-time programmable memory. If you have an ODrive v3.4 or older, you should run this once for a better firmware update user experience in the future. Run the command without any options for more details. Once set, the board version is exposed through the hw_version_[...] properties.
• infrastructure to publish the python tools to PyPi. See tools/setup.py for details.
• Automated test script run_tests.py
• System stats (e.g. stack usage) are exposed under <odrv>.system_stats

Changed

• DFU script updates
  • Verify the flash after writing
  • Automatically download firmware from GitHub releases if no file is provided
  • Retain configuration during firmware updates
• Refactor python tools
  • The scripts explore_odrive.py, liveplotter.py, drv_status.py and rate_test.py have been merged into one single odrivetool script. Running this script without any arguments provides the shell that explore_odrive.py used to provide.
  • The command line options of odrivetool have changed compared to the original explore_odrive.py. See odrivetool --help for more details.
  • odrivetool (previously explore_odrive.py) now supports controlling multiple ODrives concurrently (odrv0, odrv1, ...)
  • No need to restart the odrivetool shell when devices get disconnected and reconnected
  • ODrive accesses from within python tools are now thread-safe. That means you can read from the same remote property from multiple threads concurrently.
  • The liveplotter (odrivetool liveplotter, formerly liveplotter.py) does no longer steal focus and closes as expected
  • Add commands odrivetool backup-config and odrivetool restore-config
  • (experimental: start liveplotter from odrivetool shell by typing start_liveplotter(lambda: odrv0.motor0.encoder.encoder_state))
• Set thread priority of USB pump thread above protocol thread
• GPIO3 not sensitive to edges by default
• The device now appears as a composite device on USB. One subdevice is still a CDC device (virtual COM port), the other subdevice is a vendor specific class. This should resolve several issues that were caused by conflicting kernel drivers or OS services.
• Add WinUSB descriptors. This will tell Windows >= 8 to automatically load winusb.sys for the ODrive (only for the vendor specific subdevice). This makes it possible to use the ODrive from userspace via WinUSB with zero configuration. The Python tool currently still uses libusb so Zadig is still required.
• Add a configuration to enable the ASCII protocol on USB at runtime. This will only enable the ASCII protocol on the USB CDC subdevice, not the vendor specific subdevice so the python tools will still be able to talk to the ODrive.

Fixed

• Enums now transported with correct underlying type on native protocol
• USB issue where the device would stop responding when the host script would quit abruptly or reset the device during operation

[0.3.6] - 2018-03-26

Added

• Storing of configuration parameters to Non Volatile Memory
• USB Bootloader
• make erase_config to erase the configuration with an STLink (the configuration can also be erased from within explore_odrive.py, using my_odrive.erase_configuration())
• Travis-CI builds firmware for all board versions and deploys the binaries when a tag is pushed to master

Changed

• The build is now configured using the tup.config file instead of editing source files. Make sure you set your board version correctly. See here for details.
• The toplevel directory for tup is now Firmware. If you used tup before, go to Firmware and run rm -rd ../.tup; rm -rd build/*; make.
• Update CubeMX generated STM platform code to version 1.19.0
• Remove UUID_0, UUID_1 and UUID_2 from USB protocol. Use serial_number instead.
• Freertos memory pool (task stacks, etc) now uses Core Coupled Memory.

Fixed

• malloc now fails if we run out of memory (before it would always succeed even if we are out of ram...)

Known Issues

• The README says you should run (lsusb -d 1209:0d32 -v; lsusb -d 0483:df11 -v) | grep iSerial to find your ODrive's serial number. However with this release's firmware you need to run (lsusb -d 1209:0d33 -v; lsusb -d 0483:df11 -v) | grep iSerial instead (that is 0d33 instead of 0d32).

[0.3.5] - 2018-03-04

Added

• Reporting error if your encoder CPR is incorrect
• Ability to start anticogging calibration over USB protocol
• Reporting of DRV status/control registers and fault codes
• DRV status read script
• Microsecond delay function
• Travis-CI

Changed

• Build system is now tup instead of make. Please check the Readme for installation instructions.

[0.3.4] - 2018-02-13

Fixed

• Broken way to check for python 2. Python 2 not supported yet.

[0.3.3] - 2018-02-12

Added

• Liveplotter script
• Automatic recovery of USB halt/stall condition

Changed

• Modified python code to be Python 2 compatible

Fixed

• USB CSC (USB serial) now reports a sensible baud rate

[0.3.2] - 2018-02-02

Added

• Gimbal motor mode
• Encoder index pulse support
• resistance_calib_max_voltage parameter

[0.3.1] - 2018-01-18

Added

• UUID Endpoint
• Reporting of correct ODrive version on USB descriptor
• Getting started instructions for VSCode

Changed

• USB Product ID to 0x0D32, as it is the only Pid we were allocated on pid.codes
• Recommended method to debug firmware from VSCode now uses Cortex-Debug extension instead of native-debug.
• Refactor IDE instructions into separate files

Fixed

• Bug where the remote function calls from Python to the ODrive were not working properly.

[0.3] - 2017-12-18

Added

• New binary communication protocol
  • This is a much richer and more efficient binary protocol than the old human-readable protocol.
  • The old protocol is still available (but will be depricated eventually). You must manually chose to fall back on this protocol if you wish to still use it.
• Support for C++
• Demo scripts for getting started with commanding ODrive from python
• Protection from user setting current_lim higher than is measurable
• Current sense shunt values for HW v3.4
• Check DRV chip fault line

Changed

• Shunt resistance values for v3.3 and earlier to include extra resistance of PCB
• Default HW revision to v3.4
• Refactoring of control code:
  • Lifted top layer of low_level.c into Axis.cpp

Fixed

• Incorrect TIM14 interrupt mapping on board v3.2 caused hard-fault
• USB communication deadlock
• EXTI handler redefiniton in V3.2

Changed

• GPIO communication mode now defaults to NONE
• Resistance/inductance measurement now saved dispite errors, to allow debugging

• UART communication
• Setting to select UART or Step/dir on GIPIO 1,2
• Basic Anti-cogging