Tinymovr

Latest version: v2.3.2

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

Scan your dependencies

Page 2 of 3

1.6.5

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](https://tinymovr.readthedocs.io/en/latest/upgrade/upgrade.html#upgrade-using-dfu-and-can-bus). 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](https://tinymovr.readthedocs.io/en/latest/upgrade/upgrade.html#upgrade-using-activeflashlight), 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](https://tinymovr.readthedocs.io/en/latest/develop/guide.html#flashing-and-debugging), observing correct hardware revision, and choosing the Release target.
- Please use [Tinymovr Studio 1.6.7](https://pypi.org/project/tinymovr/1.6.7/) with this firmware release.

1.6.2

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](https://tinymovr.readthedocs.io/en/latest/upgrade/upgrade.html#upgrade-using-activeflashlight), 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](https://tinymovr.readthedocs.io/en/latest/develop/guide.html#flashing-and-debugging), observing correct hardware revision, and choosing the Release target.
- Please use [Tinymovr Studio 1.6.2](https://pypi.org/project/tinymovr/1.6.0/) with this firmware release.

1.6.0

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](https://tinymovr.readthedocs.io/en/latest/upgrade/upgrade.html#upgrade-using-activeflashlight), 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](https://tinymovr.readthedocs.io/en/latest/develop/guide.html#flashing-and-debugging).
- Please use [Tinymovr Studio 1.6.0](https://pypi.org/project/tinymovr/1.6.0/) with this firmware release.

1.5.0

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](https://tinymovr.readthedocs.io/en/latest/studio/usage.html#upgrading-firmware) in the documentation.
- Please use [Tinymovr Studio 1.5.0](https://pypi.org/project/tinymovr/1.5.0/) with this firmware release.

1.4.0

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](https://tinymovr.readthedocs.io/en/latest/studio/usage.html#upgrading-firmware) in the documentation.
- Please use [Tinymovr Studio 1.4.0](https://pypi.org/project/tinymovr/1.4.0/) with this firmware release.

1.2.5

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](https://github.com/tinymovr/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](https://tinymovr.readthedocs.io/en/latest/studio/usage.html#upgrading-firmware) in the documentation.
- Please use [Tinymovr Studio 1.2.8](https://pypi.org/project/tinymovr/1.2.8/) with this firmware release.

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.