Tinymovr

Latest version: v2.3.2

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

Scan your dependencies

Page 1 of 3

2.3.1

What's Changed
* Make the scheduler state volatile by eufrizz in https://github.com/tinymovr/Tinymovr/pull/327
* Use checkboxes for bool values in Studio by yconst in https://github.com/tinymovr/Tinymovr/pull/333
* External Sensor support (prerelease) by yconst in https://github.com/tinymovr/Tinymovr/pull/338
* Enable adaptive updates in studio app by yconst in https://github.com/tinymovr/Tinymovr/pull/339
* Demote schedule reentrance error to warning by yconst in https://github.com/tinymovr/Tinymovr/pull/340
* Configurable sensor rate by yconst in https://github.com/tinymovr/Tinymovr/pull/341
* Fix manifest and tests by yconst in https://github.com/tinymovr/Tinymovr/pull/344
* GUI improvements by yconst in https://github.com/tinymovr/Tinymovr/pull/346
* Improve AMT22 reliability by yconst in https://github.com/tinymovr/Tinymovr/pull/348
* Refactor CAN bus infrastructure in Studio by yconst in https://github.com/tinymovr/Tinymovr/pull/350
* Add GUI console by yconst in https://github.com/tinymovr/Tinymovr/pull/347
* Studio/fix logging by yconst in https://github.com/tinymovr/Tinymovr/pull/352
* Add update rate and time window adjustments by yconst in https://github.com/tinymovr/Tinymovr/pull/353
* Improve error reporting for pole pair calibration by yconst in https://github.com/tinymovr/Tinymovr/pull/354
* Use shared ram for dfu setting by yconst in https://github.com/tinymovr/Tinymovr/pull/355
* Fix can initialization/setup by yconst in https://github.com/tinymovr/Tinymovr/pull/356
* Add motor resistance and inductance limitations table by yconst in https://github.com/tinymovr/Tinymovr/pull/357
* Fix transform derivation by yconst in https://github.com/tinymovr/Tinymovr/pull/358
* Use wildcards in manifest by yconst in https://github.com/tinymovr/Tinymovr/pull/359
* add flag for forcing device flashing by yconst in https://github.com/tinymovr/Tinymovr/pull/360
* add test cases by yconst in https://github.com/tinymovr/Tinymovr/pull/361
* Docs/add ma7xx figure by yconst in https://github.com/tinymovr/Tinymovr/pull/362
* Validate data written to nvm by yconst in https://github.com/tinymovr/Tinymovr/pull/363
* Pre CL checks by yconst in https://github.com/tinymovr/Tinymovr/pull/364
* Abnormal calibration voltage check by yconst in https://github.com/tinymovr/Tinymovr/pull/365
* Support for Tinymovr R53 by yconst in https://github.com/tinymovr/Tinymovr/pull/366


**Full Changelog**: https://github.com/tinymovr/Tinymovr/compare/1.6.7...2.3.1


[Documentation for this release](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.3.1](https://pypi.org/project/tinymovr/2.3.1/) with this firmware release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

2.3.0a1

What's Changed
* Pre Closed Loop checks by yconst in https://github.com/tinymovr/Tinymovr/pull/364
* Abnormal calibration voltage check by yconst in https://github.com/tinymovr/Tinymovr/pull/365


**Full Changelog**: https://github.com/tinymovr/Tinymovr/compare/2.2.3a1...2.3.0a1

[Documentation for this release](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.3.0a1](https://pypi.org/project/tinymovr/2.3.0a1/) with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

2.2.3a1

What's Changed

* add flag for forcing device flashing by yconst in https://github.com/tinymovr/Tinymovr/pull/360
* add nvm test case by yconst in https://github.com/tinymovr/Tinymovr/pull/361
* Docs/add ma7xx figure by yconst in https://github.com/tinymovr/Tinymovr/pull/362
* Validate data written to nvm by yconst in https://github.com/tinymovr/Tinymovr/pull/363


**Full Changelog**: https://github.com/tinymovr/Tinymovr/compare/2.2.2a1...2.2.3a1

[Documentation for this release](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.2.3a1](https://pypi.org/project/tinymovr/2.2.3a1/) with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

2.2.1a1

What's Changed
* Refactor CAN bus infrastructure in Studio by yconst in https://github.com/tinymovr/Tinymovr/pull/350
* (feat) Add GUI console by yconst in https://github.com/tinymovr/Tinymovr/pull/347
* (bug) Studio/fix logging by yconst in https://github.com/tinymovr/Tinymovr/pull/352
* (feat) Add update rate and time window adjustments by yconst in https://github.com/tinymovr/Tinymovr/pull/353
* (feat) Improve error reporting for pole pair calibration by yconst in https://github.com/tinymovr/Tinymovr/pull/354
* (bug) Use shared ram for dfu setting by yconst in https://github.com/tinymovr/Tinymovr/pull/355
* (bug) Fix can initialization/setup by yconst in https://github.com/tinymovr/Tinymovr/pull/356
* (docs) Add motor resistance and inductance limitations table by yconst in https://github.com/tinymovr/Tinymovr/pull/357
* (bug) Fix transform derivation by yconst in https://github.com/tinymovr/Tinymovr/pull/358

**Full Changelog**: https://github.com/tinymovr/Tinymovr/compare/2.0.1a1...2.2.1a1

[Documentation for this release](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.0.0a2](https://pypi.org/project/tinymovr/2.0.0a2/) with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

2.0.1a1

What's Changed
* GUI improvements by yconst in https://github.com/tinymovr/Tinymovr/pull/346
* Improve AMT22 reliability by yconst in https://github.com/tinymovr/Tinymovr/pull/348


**Full Changelog**: https://github.com/tinymovr/Tinymovr/compare/2.0.0a2...2.0.1a1

[Documentation for this release](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.0.0a2](https://pypi.org/project/tinymovr/2.0.0a2/) with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

2.0.0a1

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](https://tinymovr.readthedocs.io/en/develop/)

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](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 2.0.0a2](https://pypi.org/project/tinymovr/2.0.0a2/) with this firmware pre-release.
- Documentation for this release is available on Readthedocs in the [develop branch](https://tinymovr.readthedocs.io/en/develop/)

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.