(Instro)ductions

Hey everyone, I’m John - one of the maintainers of instro!

Who are we?

Test engineers, hardware enthusiasts, and Nominal employees building a world-class hardware and instrumentation library in Python. For forty years, T&M tooling has meant silos and vendor lock-in. We think a community-driven, open-source effort in Python can be the rising tide that lifts all hardware-adjacent ships.

What is instro?

An open-source instrumentation library. Every company has a homegrown version of this… Someone in QC writes scripts for the bench power supply, a test engineer grinds on multimeter support before a big qual campaign, and a few short years later it’s a Frankenstein “framework” nobody owns or documents. Instro is that library built once, in the open, properly typed, tested, documented, community-maintained.

What makes it different?

Instro is a Hardware Abstraction Layer (HAL), you write test logic against abstract instrument types (InstroDAQ, InstroDMM, InstroPSU, etc), then pick the driver for whatever’s actually on your bench. Could be a Rigol DP800 on system one, a Keysight E36100 on system two. Swapping vendors is a one-line change, not a refactor. When it’s time to capture data, Publishers stream measurements to a file or wherever else they need to go.

Engineers like you deserve top-of-the-line tools. We’re going to make them real.

John

2 Likes