Python library for talking to test instrumentation (power supplies, multimeters, electronic loads, DAQs, oscilloscopes, PLCs) from a unified, typed API.
Quickstart
Talk to a simulated PSU. No hardware required.
# Terminal 1: start the in-process SCPI sim server:
python -m instro.psu.scpi_sim_server
# Terminal 2: run this:
from instro.psu import InstroPSU
from instro.psu.drivers import SimulatedPSU
with InstroPSU(
name="my-psu",
driver=SimulatedPSU("TCPIP0::127.0.0.1::5025::SOCKET"),
num_channels=2,
) as psu:
psu.set_voltage(3.3, channel=1)
psu.output_enable(True, channel=1)
print(psu.get_voltage(channel=1))
That's the flow. Construct, open(), configure, measure, close(). When you want to capture the data, attach a publisher to stream it to a file, a custom destination, or Nominal. For the full walkthrough (including the background polling daemon and publishers), see the official documentation.
Installation
pip install instro
Requires Python 3.10 to 3.14.
To work on instro itself, clone and install with uv:
git clone https://github.com/nominal-io/instro.git
cd instro
uv sync --extra all
This creates a virtual environment with the core library, all optional vendor drivers, and dev dependencies.
Run with uv run python your_script.py or activate via source .venv/bin/activate (Unix) / .venv\Scripts\activate (Windows).
For the full toolchain needed to run just check and just test (including the native Rust/CMake/LLVM dependencies their Rust recipes require), see Prerequisites in the contributing guide.
Optional Extras
Instro drivers that require a separate vendor sdk installation ship as separate packages so the heavy dependencies stay optional, and community-contributed drivers ship in their own package. Install only what you need:
| Extra | Pulls in |
Package |
|---|---|---|
instro[nidaq] |
NI-DAQmx (Linux + Windows) |  |
instro[labjack] |
LabJack LJM |  |
instro[mccdaq] |
MCC UL (Windows-only) |  |
instro[aardvark] |
Total Phase Aardvark (I2C) |  |
instro[ethernetip] |
EtherNet/IP support for Allen-Bradley PLCs |  |
instro[contrib] |
Community-contributed hardware drivers |  |
instro[unstable] |
In-development features whose API isn't settled |  |
instro[all] |
Everything above | — |
Pass the extra package name in brackets to pip install:
pip install "instro[labjack]"
pip install "instro[nidaq,contrib]"
Supported devices
| Category | Class | Vendors |
|---|---|---|
| Power Supply | InstroPSU |
B&K Precision (9115, 914X), Keysight (E36100-series), Rigol (DP800-series), Siglent (SPD3303), TDK Lambda (Genesys), simulated |
| Multimeter | InstroDMM |
Agilent 34401A, Keysight 34461A, Keithley 2400, Keithley 2750 (unstable), simulated |
| Arbitrary Waveform Generator | InstroAWG |
Keysight (33521B, unstable), Rigol (DG1022Z, unstable) |
| Electronic Load | InstroELoad |
B&K Precision (85xxB-series) |
| Oscilloscope | InstroScope |
Keysight (1200X-series), Tektronix (2-series), Siglent (SDS1000X-E) |
| Flow Controller | InstroFlowController |
Alicat MC-series |
| DAQ | InstroDAQ |
Keysight 34980A, NI-DAQmx, LabJack T-series, MCC USB-series |
| I2C | I2CInterface |
Total Phase Aardvark |
| Modbus | ModbusDevice |
Any Modbus TCP / RTU device |
| EtherNet/IP | EtherNetIPDevice |
Allen-Bradley / CompactLogix-class PLCs |
Don't see your vendor? Drivers we can't test directly land in instro-contrib.
Install them with instro[contrib]. See CONTRIBUTING.md for the verification expectations.
Contributing
- Humans: see
CONTRIBUTING.mdfor development setup, PR conventions, and where different kinds of contributions belong in the workspace. - AI coding tools (Claude Code, Cursor, Codex, Copilot Workspace, …): see
AGENTS.mdfor codebase landmarks, conventions, and common workflows. The repo ships reusable skills and subagents for both Claude Code (.claude/) and Codex CLI (.agents/,.codex/). The existing skills areadd-instrument-driverwhich scaffolds a new vendor driver from a programming manual/API, andvalidate-driver-hardwarewhich smoke-tests an authored driver against the real instrument and self-corrects it. See Repo skills and subagents.
License
Apache License 2.0. Third-party dependency notices and proprietary vendor runtime requirements are documented in NOTICE.
1 maintainer
Metadata
1 maintainer
Release files for instro 1.13.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 | |
|---|---|---|---|
| instro-1.13.0.tar.gz | 8.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| instro-1.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.1 MB
Release files / instro-1.13.0.tar.gz
| Download URL | instro-1.13.0.tar.gz |
|---|---|
| Size | 8.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4104d78d07452593eaaba1b716d190ddde21268b9b0250125dac881fef840e88
|
|
BLAKE2b-256 checksum How to use checksums |
f580ac9f087e3b499bb928dcce9bffc27f07ab407dad4ca247007fdb817af292
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 24, 2026.
Transparency logRelease files / instro-1.13.0-py3-none-any.whl
| Download URL | instro-1.13.0-py3-none-any.whl |
|---|---|
| Size | 163.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07edbf193c9811e1b1edd8b173b0caa50cbc664824aa69e8b1c70e664333e832
|
|
BLAKE2b-256 checksum How to use checksums |
5be31ee6d9d2d9b8a3f32f7ba258ba09ec8e21670369cbdf8a076c28377feeb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 24, 2026.
Transparency log
