2.2.1a1

What's Changed

• Refactor CAN bus infrastructure in Studio by @yconst in #350
• (feat) Add GUI console by @yconst in #347
• (bug) Studio/fix logging by @yconst in #352
• (feat) Add update rate and time window adjustments by @yconst in #353
• (feat) Improve error reporting for pole pair calibration by @yconst in #354
• (bug) Use shared ram for dfu setting by @yconst in #355
• (bug) Fix can initialization/setup by @yconst in #356
• (docs) Add motor resistance and inductance limitations table by @yconst in #357
• (bug) Fix transform derivation by @yconst in #358

Full Changelog: 2.0.1a1...2.2.1a1

Documentation for this release

Notes

External sensor support works for the M series boards only. The upcoming Tinymovr R5.3 will also support external sensors.

• There are three methods for flashing:

1. Via Tinymovr DFU: After downloading the correct "upgrade" firmware according to your board revision (R3.x, R5.x or M5.x), connect your device to CAN bus as usual and follow the instructions in our documentation. This is available to boards with fw 1.6.0 or later, featuring the new bootloader.
2. Via ActiveFlashLight: After downloading the correct "upgrade" firmware according to your board revision (R3.x, R5.x or M5.x), connect your device to ActiveFlashLight and follow the instructions in our documentation, selecting the Full Erase option, next to Auto Program. This method is applicable to boards with the old bootloader.
3. Via JLink & VSCode: This method enables comprehensive upgrade of both bootloader and firmware, but it requires specialized hardware (JLink) and hardware connections. Follow the instructions in our documentation, observing correct hardware revision, and choosing the Release target.

• Please use Tinymovr Studio 2.0.0a2 with this firmware pre-release.
• Documentation for this release is available on Readthedocs in the develop branch