Open Source RoboticsRobots, software & learning

Tinymovr public v3.0 source snapshot

Software

Historical public motor-control firmware and Studio client sources; current v3.1+ binaries come from a private codebase. [1] [3]

Installation & first result →Official websiteGetting started

For
Motor-control developers evaluating a historical source reference [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

The public Tinymovr repository is a motor-control firmware and client-source reference with an important version boundary. Its selected README says active development moved to a private repository, public source reflects v3.0.0 and releases from v3.1 onward are proprietary binaries. This entry covers the inspectable public snapshot, not an assertion that the latest Tinymovr firmware or Studio remains open source. [1]

Is this for you?

Known limitations
  • README says active development moved private and public code reflects v3.0.0; v3.1+ binaries are proprietary.
  • Firmware directory MIT declaration conflicts with controller.c GPLv3 header; preserve the differing notices rather than declare one clean license.
  • Hardware folder contains models/drawings, not an independently validated complete PCB-manufacturing release.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] [7] [8] · Editorial assessment

What you need

Dependencies
  • Matching controller hardware and historical firmware/client version must be established
  • A current pip tinymovr install is not automatically the inspected public source

[1] [2] [3] [4] [5] [6] [7] [8]

Installation & first result

Open the upstream getting-started guide [1]

  • Inspect the pinned public firmware and Studio sources and their notices before selecting matching hardware or a client; do not equate latest PyPI/release binaries with this snapshot.
  • Preserve exact source/dependency/model versions and evaluate the selected workflow before connecting physical hardware or reusing data.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] [7] [8] · Editorial assessment

Installation

Inspect the pinned public firmware and Studio sources and their notices before selecting matching hardware or a client; do not equate latest PyPI/release binaries with this snapshot.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [2] [3] [4] [5] [6] [7] [8] · Editorial assessment

Hardware, models & data

Inputs and outputs

Motor-control/client source and CAN-facing configurations; no hardware interface or current binary deployment verified.

Editorial scope assessment from the cited implementation/documentation; no execution or compatibility test.

[1] [3] · Editorial assessment

Project notes

A current install is not a source match

The Studio Python README identifies its own code as the v3.0.0 state while directing users to a current PyPI distribution. Thus installing the latest tinymovr package does not establish that you are running the client source inspected here. Before connecting a controller, identify the hardware revision and intended firmware/client pair, and distinguish a source build from a binary release. We have not established a tested compatible combination. [1] [8]

The firmware tree includes actual controller implementation, not just packaged firmware binaries. Inspect its control code and the corresponding Studio interfaces before attempting changes. The hardware README separately describes models and drawings for controller boards, accessories and actuators; it does not make those geometry files an independently validated complete board-manufacturing release. [3] [4] [7]

This review selects revision 945e34a52bcdf8a5c1528ee0ddd2dc23fb4356f7. The inspected controller path is firmware/src/controller/controller.c; the Python client source is under studio/Python. The documented client installation requires Python 3. This identifies an inspection route, not a tested hardware/firmware/client combination or a recommendation to substitute a current package. [3] [4] [8]

Preserve the differing notices

The root license and overall Studio declaration are GPLv3. The README and firmware/hardware directory licenses declare MIT for their respective scopes, while the inspected controller.c header states GPLv3. Preserve these differing declarations instead of assigning one clean license to every source file or to later private releases. Review the intended files and upstream clarification before redistribution. [1] [2] [3] [5] [6]

No firmware compilation, flashing, CAN connection, current binary inspection, motor tuning or physical controller test was performed. Current stock, complete build cost and vendor support were not evaluated.

What we checked

Source research only. Selected implementation/model text, repository tree and license declarations were inspected. No upstream compilation, dependency installation, simulator, network/USB/device integration, data collection, benchmark or physical robot test was performed. Source files are linked rather than redistributed; external services and paid products are not endorsed.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
945e34a

Source files and licenses

Distinct robot-facing library contribution with actual implementation/model content and a bounded documented next step. Review covers source artifacts, not operational performance or a complete tested deployment.

LayerAvailability / license
softwareavailable · GPL-3.0 overall; MIT per-directory declarations; differing GPL firmware-file header
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]
documentationavailable · GPL-3.0 overall; MIT per-directory declarations; differing GPL firmware-file header
Declaration for the scoped source implementation/documentation; dependencies, external services, model/data assets and inherited file-specific terms require separate checks. No blanket redistribution or operational clearance. [1] [2] [3]

This profile is scoped to source implementation/model descriptions and an initial inspection workflow; no physical manufacturing design, pretrained checkpoint or dataset is selected for redistribution or tested deployment.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history