Tinymovr Versions Save

What's Changed

Features

• External Sensor support (1) (prerelease) by @yconst in https://github.com/tinymovr/Tinymovr/pull/338

• Make heartbeat optional (reset upon restart)

• Configurable sensor rate by @yconst in https://github.com/tinymovr/Tinymovr/pull/341

• Enable adaptive updates in studio app by @yconst in https://github.com/tinymovr/Tinymovr/pull/339

• Use checkboxes for bool values in Studio by @yconst in https://github.com/tinymovr/Tinymovr/pull/333

• Add raw sensor angle reporting https://github.com/tinymovr/Tinymovr/commit/8e86d265495c1eb60a407cc706b481cbbca5fd7f

• Demote schedule reentrance error to warning by @yconst in https://github.com/tinymovr/Tinymovr/pull/340

Docs

Add transform documentation and calibration instructions https://github.com/tinymovr/Tinymovr/commit/1a43b346acc795ba479188f7b2d30c7015fb2168

• Add M5.2 pinouts by @yconst in https://github.com/tinymovr/Tinymovr/pull/325
• Add pdf and epub builds https://github.com/tinymovr/Tinymovr/commit/fefef8e3cc662896a3190e7d94c1db571f125e6b

Bug fixes

• Make the scheduler state volatile by @eufrizz in https://github.com/tinymovr/Tinymovr/pull/327
• Fix protocol hash incompatibility in the latest release by @yconst in https://github.com/tinymovr/Tinymovr/pull/326
• Fix length of returned version string https://github.com/tinymovr/Tinymovr/commit/997d2604ea2539d281429472db7594413f50fd7f
• Restore DWT counter. https://github.com/tinymovr/Tinymovr/commit/7bed2fecd78c1941f803b098fe9fa11803a06414

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.6.5...2.0.0a1

Documentation for this release

Notes

(1) 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

What's Changed

• Docs/change theme by @yconst in https://github.com/tinymovr/Tinymovr/pull/319
• add m5.2 board version by @yconst in https://github.com/tinymovr/Tinymovr/pull/320
• Update CAN ID docs by @yconst in https://github.com/tinymovr/Tinymovr/pull/321
• Extended CAN ID hash by @yconst in https://github.com/tinymovr/Tinymovr/pull/322
• update bootloader
• add version info to DFU mode
• improve function safety in DFU mode
• update DFU script
• add optional protocol hash check to every message in ext arbitration id
• fix trimmed version string
• improve DFU tests

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.6.4...1.6.5

Notes

• 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 1.6.7 with this firmware release.

What's Changed

• Improve angle sensor docs by @yconst in https://github.com/tinymovr/Tinymovr/pull/290
• Misc fixes in docs by @yconst in https://github.com/tinymovr/Tinymovr/pull/291
• Ensure copied directory name in docs by @yconst in https://github.com/tinymovr/Tinymovr/pull/292
• Calibration Fixes by @yconst in https://github.com/tinymovr/Tinymovr/pull/293
• Studio GUI timer improvements and bug fixes by @yconst in https://github.com/tinymovr/Tinymovr/pull/295
• Add bus, channel and bitrate arguments to DFU util by @yconst in https://github.com/tinymovr/Tinymovr/pull/297

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.6.0...1.6.2

Notes

• This release offers the option to upgrade the Tinymovr bootloader, along with the firmware, to support CAN bus DFU, but for existing boards this is only possible using JLink with the VSCode environment.
• As such there are two methods for flashing:
  1. 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.
  2. 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 1.6.2 with this firmware release.

What's Changed

• New CAN-based DFU mode by @yconst in https://github.com/tinymovr/Tinymovr/pull/279

• DFU validation and recovery mode by @yconst in https://github.com/tinymovr/Tinymovr/pull/287

• Add dialog for inputting function arguments by @yconst in https://github.com/tinymovr/Tinymovr/pull/284

• Add remote JLink debug server flash/debug VSCode action by @yconst in https://github.com/tinymovr/Tinymovr/pull/273

• User and technical documentation and devtools improvements by @yconst in https://github.com/tinymovr/Tinymovr/pull/274

• Add models for all new hardware by @yconst in https://github.com/tinymovr/Tinymovr/pull/270

• Update servo kit models and drawings by @yconst in https://github.com/tinymovr/Tinymovr/pull/281

• Add M5 gimbal motor bracket model by @yconst in https://github.com/tinymovr/Tinymovr/pull/275

• Improve docs for firmware upgrade, add DFU using CAN by @yconst in https://github.com/tinymovr/Tinymovr/pull/285

• Docs hotfixes by @yconst in https://github.com/tinymovr/Tinymovr/pull/283

• Version 1.6.0 by @yconst in https://github.com/tinymovr/Tinymovr/pull/286

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.5.0...1.6.0

Notes

• This release offers the option to upgrade the Tinymovr bootloader, along with the firmware, to support CAN bus DFU, but for existing boards this is only possible using JLink with the VSCode environment.
• As such there are two methods for flashing:
  1. 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.
  2. Via JLink & VSCode: This method enables comprehensive upgrade of both bootloader and firmware, but it requires specialized hardware (JLink) and hardware connections. After downloading the correct "release" firmware according to your board revision (R3.x, R5.x or M5.x), follow the instructions in our documentation.
• Please use Tinymovr Studio 1.6.0 with this firmware release.

What's Changed

• Sensorless homing by @yconst in https://github.com/tinymovr/Tinymovr/pull/259
• Cleanup legacy Eclipse files by @yconst in https://github.com/tinymovr/Tinymovr/pull/261
• Add uart port warning by @yconst in https://github.com/tinymovr/Tinymovr/pull/263
• Add M5 hardware info by @yconst in https://github.com/tinymovr/Tinymovr/pull/264
• Fix bandwidth value for encoder observer and current control by @yconst in https://github.com/tinymovr/Tinymovr/pull/265
• Support for Tinymovr R5.2 by @yconst in https://github.com/tinymovr/Tinymovr/pull/267
• Update hardware diagrams by @yconst in https://github.com/tinymovr/Tinymovr/pull/268

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.4.0...1.5.0

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5.x or M5.x).
• Do not download the "z_testbed_fw.bin" file. This is for internal testing purposes.
• Follow the bootloader flashing instructions in the documentation.
• Please use Tinymovr Studio 1.5.0 with this firmware release.

This is the second official release of our Next-Gen firmware! 🎉

Changes:

• [feat] Add full support for time-limited trajectory planner
• [feat] Suggest course of action if firmware and studio are incompatible
• [feat] Migrate to pyside6
• [feat] Add placeholder to tree view if no devices found
• [bug] Fix issue with pyside compatibility on Apple silicon
• [bug] Improve Studio stability and device discovery
• [bug] Fix some functions of type void returning a can frame when remotely called
• [bug] Better management of Studio package resources through manifest.
• [docs] Revise and clarify various sections.

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.2.5...1.4.0

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5.x or M5.x).
• Do not download the "z_testbed_fw.bin" file. This is for internal testing purposes.
• Follow the bootloader flashing instructions in the documentation.
• Please use Tinymovr Studio 1.4.0 with this firmware release.

This is the first official release of our Next-Gen firmware! 🎉 We've put a lot of effort into this, and we hope you enjoy it!

Warning

There are compatibility issues with Tinymovr Studio 1.x.x GUI on Apple ARM. We are actively working to resolve these issues. Users of Apple ARM-based systems are advised to either use the 1.x.x CLI version, or delay upgrading till these issues are resolved.

Changes:

Too many to mention in detail really, but here are the highlights:

• [feat] Complete rewrite of the comms layer using Avlos
• [feat] Add support for the upcoming M5 board
• [feat] Add Studio GUI app
• [feat] Add flux braking
• [feat] Improve main loop efficiency
• [bug] Fix ADC gain values
• [devtools] Revise launch configurations
• [devtools] No longer necessary to patch the JLinkDevices.xml file with the PAC additions, in order for JLinkGDBServer to work properly.
• [docs] Rewrite and revision of major documentation areas.

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5.x or M5.x).
• Do not download the "z_testbed_fw.bin" file. This is for internal testing purposes.
• Follow the bootloader flashing instructions in the documentation.
• Please use Tinymovr Studio 1.2.8 with this firmware release.

This is the second pre-release of the next-gen v1.x firmware series. It is a pre-release of beta quality, and bugs are present for sure. Do not use on production systems.

Documentation is currently being updated here

What's Changed

• [bug] Fix error in the scaling of ADC values
• [feat] Import/export of board configuration in Studio CLI and GUI
• [refactor] Refactor Studio GUI for greater efficiency and readability
• [bug] Reload nodes on change of critical remote attributes
• [perf] Improve node management in Studio GUI

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/1.1.1.dev2...1.2.3.dev1

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• This release uses a version compatibility check between firmware and studio. You will need to have compatible firmware and studio versions.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5 or M5).
• Follow the bootloader flashing instructions in the documentation.
• This firmware release is compatible with Tinymovr studio v1.2.3.dev1. Please clone this repo and use pip install -e ., to install the development installation of Tinymovr Studio.

This is the first pre-release of the next-gen v1.x firmware series. It is a pre-release of beta quality, and bugs are present for sure. Do not use on production systems.

Documentation is currently being updated here

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• This release uses a version compatibility check between firmware and studio. You will need to have compatible firmware and studio versions.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, R5 or M5).
• Follow the bootloader flashing instructions in the documentation.
• This firmware release is compatible with Tinymovr studio v1.1.1.dev2. Please clone this repo and use pip install -e . for now for a development installation of Tinymovr Studio.

Changes:

• [bug] Improve Hall effect sensor calibration (thanks @eufrizz !)
• [feat] Add velocity ramping (thanks @eufrizz !)
• [devtools] Revise launch configurations
• [docs] Improved Hall effect sensor documentation
• [docs] Add Servokit R5 STEP and STL models

Full Changelog: https://github.com/tinymovr/Tinymovr/compare/fw-v0.8.16...fw-v0.8.17

Notes

• When flashing this release with the ActiveFlashLight app, please select the Full Erase option, next to Auto Program, otherwise a verification error may occur.
• This release uses a version compatibility check between firmware and studio. You will need to have compatible firmware and studio versions. If incompatible versions are detected you will be informed during discovery. If you are absolutely sure about what you're doing, use the --no-version-check flag.
• There are several versions of this firmware. Download the correct one according to your board revision (R3.2, R3.3, or R5).
• Do not download the "z_testbed_fw.bin" file. This is for internal testing purposes.
• Follow the bootloader flashing instructions in the documentation.
• This firmware release is compatible with Tinymovr studio v0.3.17.

This is the last feature release of the 0.8.x line. From now on, this line will only accept hotfixes.We are gradually transitioning to the next-gen 1.x Tinymovr firmware/software, and all new features are added there, in the develop branch.