Plesty K10CR1 Device
Plesty device for the Thorlabs K10CR1 motorized 360° cage rotation stage, driven over USB serial with the binary APT protocol (no Kinesis/.NET runtime required, works on Windows and Linux).
Device constants (unit scaling, software limits, stage defaults, runtime
defaults) live in plesty/k10cr1/config.yaml; the parameter set is defined in
plesty/k10cr1/schema_param.json.
Installation
git clone https://gitlab.com/plesty/hub/devices/thorlab/plesty-k10cr1.git
cd plesty-k10cr1
uv sync
Run As TCP Server
Windows only: the controller's custom FTDI product id is claimed by no driver
macOS can load, and no rig here has bound it on Linux. The simulator (--mock)
runs anywhere. See the docs for the detail.
Connect the stage via USB. The server opens the stage named by the first of
these that is set: the controller's serial number from the unit's label
(DEVICE_SERIAL or --serial, e.g. 55001327), the serial port
(DEVICE_PORT or --port, e.g. COM3), or else the one controller carrying
Thorlabs' USB id 0403:FAF0 (DEVICE_VID_PID or --vid-pid). On a host with
several stages, give each server its serial number: it stays valid when a
replug moves the COM name, and with two controllers and neither set the server
refuses rather than guess. Then:
uv run python -m plesty.k10cr1 --tcp-port 5555
Pass --mock to serve the in-memory APT motor simulator instead of real
hardware.
Run pytest
All tests run against the simulator; set DEVICE_PORT in .env to also run
the real-device test.
uv run pytest
Metadata
Release files for plesty-k10cr1 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plesty_k10cr1-0.4.0.tar.gz | 154.7 kB | Without provenance | Details for plesty_k10cr1-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plesty_k10cr1-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for plesty_k10cr1-0.4.0-py3-none-any.whl |
Total release size: 184.1 kB
Release files / plesty_k10cr1-0.4.0.tar.gz
| Download URL | plesty_k10cr1-0.4.0.tar.gz |
|---|---|
| Size | 154.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e3eb254ef070ae2222a158d802d2a933a86519330e8c3946a95449caf788482
|
|
BLAKE2b-256 checksum How to use checksums |
82c28d603dad95af9228d0c79b1b200b6a99bff2a8c239707ad76a57c7a8ceef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / plesty_k10cr1-0.4.0-py3-none-any.whl
| Download URL | plesty_k10cr1-0.4.0-py3-none-any.whl |
|---|---|
| Size | 29.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22c6d18128b8a8558770b489a90427739551da00f0e15238f0af3dc2bfca075c
|
|
BLAKE2b-256 checksum How to use checksums |
a0aaaa8238c8c2015d5ca5fea502b64e3acab9289aae12a640216a142ecc1ca8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for plesty-k10cr1 0.4.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.