Skip to content

Lab Equipment Controller v1.0.0

Choose a tag to compare

View all tags
@EECSB EECSB released this 11 Aug 17:50
· 7 commits to master since this release
v1.0.0
0f24c5c

First release. A Windows desktop app for discovering and controlling lab instruments
(oscilloscopes, generators, multimeters, power supplies, loads, spectrum analyzers) over
Ethernet using SCPI — it scans your bench subnet, opens a console per instrument, and
drives one or several of them from scripts, with every command it offers transcribed from
the vendor's own programming guide.

Downloads

File What it is
LabEquipmentController-v1.0.0-setup.exe Installer, 4 MB — installs per-user (no admin prompt), adds a Start Menu shortcut and an uninstaller. Needs the .NET 10 Desktop Runtime, and offers to download it for you if it isn't there.
LabEquipmentController-v1.0.0-win-x64.zip Portable build, 47 MB — unzip anywhere and run LabEquipmentController.exe. Self-contained: no .NET install needed, nothing written outside its folder.

Same app either way. The installer is small because its copy leans on a .NET runtime you
install once; the zip is large because it carries one.

Requirements

  • Windows 10 or later, x64
  • For the installer only: the .NET 10 Desktop Runtime
    (x64) — setup checks for it and offers the download. An older .NET runtime does not
    substitute for it.
  • Instruments reachable over the LAN (raw-socket SCPI, typically port 5025, or VXI-11) —
    see the README
    if your bench lives behind a VM
  • No administrator rights needed

🔒 Security warning on launch

These builds are not code-signed, so Windows SmartScreen shows an "unknown publisher"
warning the first time you download or run them. That's a reputation check, not a sign
anything is wrong. To get through it:

  • Download: choose Keep / Keep anyway if the browser flags it.
  • Launch: on the blue "Windows protected your PC" dialog, click More info → Run anyway.

Verify your download (SHA-256)

LabEquipmentController-v1.0.0-setup.exe      B6B6336F3CB24C8D0D783455111AA4AE52E3DA5CC0ED8021824420347F9E0807
LabEquipmentController-v1.0.0-win-x64.zip    4B8C2582E7FD4A88543BA6C342A44F739A5C5471BE2137A692D7D36798BB0353

Get-FileHash .\LabEquipmentController-v1.0.0-setup.exe -Algorithm SHA256

If the hash matches, the file is byte-for-byte the published build.

What's in it

  • Network scan — sweeps the selected interface's subnet (or an IP range) on one or
    more SCPI ports and identifies responders via *IDN?; results export to CSV
  • Consoles — a command console per instrument, as tabs or detached windows, with
    history recall and instrument-aware quick-command buttons
  • Curated command catalogs — 23,174 commands across 35 instrument families,
    transcribed from vendor programming guides (never invented — the repo's one rule),
    browsable and searchable in the Command Library; 518 entries carry a bench-verified tick
  • Scripting — a small line-oriented language with REPEAT/DELAY/PRINT, per-family
    examples, a colouring editor with catalog completion
  • Multi-instrument scripts — DEVICE/WITH bind several instruments into one
    interleaved measurement, recording into a table with a live plot
  • Capture — scope waveforms (per-vendor scaling handled), instrument screenshots, and
    a live multimeter readout
  • AI, optional and off by default — datasheet extraction and script drafting against
    your own API key (Gemini / Anthropic / OpenAI-compatible), with drafts checked against
    the catalogs; keys stored under Windows DPAPI

How the pieces fit is documented in
docs/ARCHITECTURE.md;
confirming catalog entries on your own instrument is
docs/VERIFYING-COMMANDS.md.

⚠️ Warning

Scripts and quick commands drive real equipment — some commands source voltage, sink
current, or enable outputs. Check what is wired to your bench before running a sweep, and
read the warning lines the bundled examples carry. Use at your own risk.

Assets 4
Loading