Overview
This repository contains the code used to interface with an OpenMotion sensor module and OpenMotion Console. The sensor module runs the code contained in the motion-sensor-fw repository on an STM32H7 processor. The programs here communicates with the modules over a USB serial connection.
A library called omotion is imported in many of the python scripts listed here to aid communication with the Sensor Module.
Getting started
- Install requirements.txt (
pip install -r requirements.txt) - Install libusb for your system requires libusb to be installed, for windows install the dll to c:\windows\system32, download the correct dll from github libusb Releases
- Plug in your aggregator module. Please wait 10 seconds for it to boot up before continuing.
- Run
python multicam_setup.py- this will flash each camera sensor one by one. Alternatively, you may flash just a single camera sensor by usisingpython flash_camera.py 1- this will flash just camera 1 - Run
python monitor.py 1- this will flash the camera with a few parameters (test modes, exposure times, gain settings, etc), start the camera streaming, start the frame sync generating, and then put the cameras into streaming mode. It will then recieve the histogram data for the defined number of seconds then close down. Modify the parameters at the top of this file if you want to adjust the gain, exposure time, etc. Change the number in the command line arguments to change the camera you'd like to interrogate. Cameras are numbered 1-8 and correspond to J1-J8 on the aggregator board.
from repo root rebuild and install
python -m pip install --upgrade build twine python -m build # creates wheel + sdist under dist/ python -m pip install --force-reinstall dist/openmotion_pylib-1.3.3-py3-none-any.whl
quick runtime check (on Windows box with your device bound to WinUSB/libusbK)
python -c "import usb, omotion.usb_backend as ub; print(ub.get_libusb1_backend())"
Release files for openmotion-pylib 1.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openmotion_pylib-1.4.5.tar.gz | 28.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openmotion_pylib-1.4.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.1 MB
Release files / openmotion_pylib-1.4.5.tar.gz
| Download URL | openmotion_pylib-1.4.5.tar.gz |
|---|---|
| Size | 28.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c89a17f2893d5339e995eee9b9993ae6e7dd65ec328b5ed7c5e98df2b9ec53c9
|
|
BLAKE2b-256 checksum How to use checksums |
a1b6eab4f2cf43785c1f7d8fb5c4b041c37a2d5b522b1ee53b7f913e0754eb92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency logRelease files / openmotion_pylib-1.4.5-py3-none-any.whl
| Download URL | openmotion_pylib-1.4.5-py3-none-any.whl |
|---|---|
| Size | 6.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dce2f29bcec095a0c44b2bdbbb75e6cd20b0494853158aa10e74c6465cc4d33e
|
|
BLAKE2b-256 checksum How to use checksums |
68537663651ecc63ee154c6b948c536758b0acd5593253713f5c07f271e68443
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.
Transparency log