Overview
This document outlines the instruments currently supported by the Lager platform. All supported devices can be controlled locally or remotely through thelager CLI and integrated directly into automated hardware
testing workflows and CI/CD systems.
Lager transforms traditional bench equipment into programmable
infrastructure for embedded engineering teams.
If you use equipment not listed here, custom integration support
is available.
1. Power Control
Lager provides automated control of bench power equipment for deterministic hardware testing, fault injection, and CI-driven validation.Power Supplies
* RS-232 only — connects through a USB-serial adapter and requires a one-time
manual assignment with
lager nets assign. The DP711 also
requires a null-modem (crossover) cable between the supply and the
RS232-to-USB adapter. Both ends are wired as DTE, so a straight-through
connection will not communicate. See
RS-232 Instruments.
** Detected over USB (f4ec:1410). Over LAN it is not detected: create its net
with lager nets add-batch,
"instrument": "Siglent_SPD1168X" and a TCPIP::<ip>::INSTR address. It has no
OVP/OCP, so lager supply --ovp/--ocp and clear-ovp/clear-ocp return an
error. Its measured values update about every 0.35 s, so wait that long after a
setpoint change before reading them. The SPD1305X has the same USB ID, so it is listed as
Siglent_SPD1168X. The driver reads the real model from the instrument.
The drivers also support the Rigol DP712 and the Keysight E36311A. Neither is in the
auto-detected list.
Turning protection off. On a Rigol DP700, a Rigol DP800 and a Keysight E36200, Lager
can turn OVP and OCP off. On a Keysight E36300, a Keithley 2281S, a Siglent SPD1000X and an
EA, a request to turn protection off returns an error. A net with a max_voltage safety
limit keeps OVP on, and a net with max_current keeps OCP on.
Enables:
- Automated voltage/current control
- Power sequencing
- Brownout and glitch testing
- CI-integrated hardware validation
Battery Simulators
Enables:
- Programmable battery emulation
- Charge/discharge profile simulation
- Low-voltage testing
Electronic Loads
Enables:
- Load step testing
- Current sink validation
- Automated power integrity testing
2. Measurement & Analysis
Lager integrates measurement equipment into programmable test workflows, enabling automated signal inspection and power analysis.Oscilloscopes & Logic Analyzers
The box reads a PicoScope’s channel count, voltage ranges, bandwidth, memory
depth and ADC resolution from the unit when it opens it. It does not assume them
from the model, so scopes within a supported series work without configuration.
To see what the box detected, type
capabilities in the console of the web UI,
or call capabilities() from Python. The 8-channel 4824 works as a four-channel
scope, on channels A to D.
Net creation takes its channel list from the same detection. Plug the scope in,
with the box running, before you add its nets. If the box’s scope service does not
have the unit open, a PicoScope shows only two channels.
Enables:
- Automated waveform capture
- Trigger-based signal validation
- Digital + analog correlation
- Continuous streaming with a live web view at
http://<box>:9000/scope(a Rigol needs a live view paired withlager nets set-capture) - Measurements computed on the box from the capture (PicoScope) or queried over SCPI (Rigol)
lager scope cursor time and cursor volts) are
PicoScope only.
Power Measurement
Enables:
- Current consumption profiling
- Energy and charge integration
- Power statistics (mean/min/max/std)
- Power regression testing
Multimeters
A LAN meter is not found by the USB scan; add its net with
lager nets add-batch, naming the instrument
Siglent_SDM3065X and a TCPIP::<ip>::INSTR address.
Enables:
- DC/AC voltage and current, 2- and 4-wire resistance, continuity, diode, frequency, period, capacitance and temperature readings
- Fixed range and integration time (NPLC) per reading
- Precision rail and leakage checks in CI
Temperature Monitoring
Enables:
- Thermal monitoring during hardware tests
- Environmental validation
- Long-duration soak testing
3. Embedded Interfaces
Lager supports programmable hardware interface control for automated communication testing and validation.Multi-Protocol Adapters
LabJack T7
Control Commands:lager i2c, lager spi, lager adc,
lager dac, lager gpi, lager gpo
Interfaces:
- I2C (1 bus)
- SPI (1 bus)
- 14 ADC channels
- 2 DAC channels
- 23 GPIO pins
LabJack U3
Control Commands:lager i2c, lager spi, lager adc,
lager dac, lager gpi, lager gpo
Interfaces:
- I2C (1 bus, needs external pull-up resistors)
- SPI (1 bus)
- 16 ADC channels
- 2 DAC channels (0.04 V to 4.95 V)
- 16 GPIO pins
- The U3 uses the LabJack Exodriver and LabJackPython, not LJM. A T7 and a U3 can share one Lager Box.
FIO0-FIO3are not GPIO pins. Lager treats every U3 as a U3-HV, where those four pins are fixed high-voltage analog inputs.AIN4-AIN15share pins withFIO4-FIO7andEIO0-EIO7. A read sets the analog or digital mode of the pin.- The DAC has no readback. A read returns the last value that the box set.
- SPI and I2C need U3 hardware version 1.21 or later. A transfer is at most 50 bytes, and the clock rate is approximate.
- The U3 has no MIO pins. Its EIO and CIO lines are on the DB15 connector.
- A U3 reports no serial number, so its address names the USB port that it is plugged into, for example
USB0::0x0CD5::0x0003::port-1-1.3::INSTR. Two U3 units on one Lager Box therefore have different addresses, and each can have nets. - A U3 net stays with the USB port. If you move the U3 to a different port, add its nets again. A net from an earlier release has an empty serial field and opens the first U3 that the box finds.
Total Phase Aardvark
Control Commands:lager i2c, lager spi, lager gpi,
lager gpo
Interfaces:
- I2C (1 bus)
- SPI (1 bus)
- 6 GPIO pins (
SCL,SDA,MISO,SCK,MOSI,SS)
FTDI FT232H
Control Commands:lager i2c, lager spi, lager gpi,
lager gpo
Interfaces:
- I2C (1 bus)
- SPI (1 bus)
- 12 GPIO pins
FTDI FT2232H
Control Commands:lager i2c, lager spi, lager gpi,
lager gpo, lager uart, lager debug
Interfaces:
- I2C and SPI
- 12 GPIO pins (
4-15) - UART
- Two channels (A and B). Pick the channel of a net with
lager nets add --interface
FTDI FT4232H
Control Commands:lager i2c, lager spi, lager gpi,
lager gpo, lager uart, lager debug
Interfaces:
- I2C and SPI on channels A and B only
- 8 GPIO pins (
0-7) on each of the four channels - UART on each channel
Measurement Computing USB-202
Control Commands:lager adc, lager dac, lager gpi,
lager gpo
Interfaces:
- 8 ADC channels
- 2 DAC channels
- 8 GPIO pins
- Automated peripheral communication testing
- Sensor validation
- Protocol-level fault injection
- Hardware-in-the-loop simulation
4. Debug & Flashing
Lager supports industry-standard ARM debug probes, all driven through the samelager debug command so probe choice is transparent to your
scripts and CI pipelines.
Capabilities:
- Flash firmware
- Erase device
- Reset target
- Launch GDB server
- Memory read/write
- OpenOCD-backed probes auto-select an interface configuration from
the USB VID/PID for the chips listed above. The FT4232H is supported
but has no safe default, because quad-MPSSE boards have too many wiring
variants. You must pass an
openocd_configthat points at the right interface cfg for your board. The same escape hatch covers non-standard FT232H/FT2232H wiring and any probe not in the table (e.g. Black Magic Probe, Glasgow Interface Explorer). - Multi-channel FTDIs (FT2232H, FT4232H) expose each MPSSE channel as
a separate debug net. The channel is an
@A/@B/@C/@Dsuffix on the device field, so a single chip can drive multiple targets independently. Channels C and D on the FT4232H have no MPSSE engine. They carrygpioanduartnets, but notdebug,i2corspinets. Pick the channel of agpio,i2corspinet withlager nets add --interface. See the nets reference for the channel-suffix syntax. - Lager selects the target chip configuration from the device name for the STM32, nRF5x, RP2040/RP2350, ATSAM, LPC, i.MX RT500, and ESP32 families. A custom OpenOCD target config drives anything else, including the i.MX RT10xx and RT11xx (#850).
- A SEGGER probe with a USB product ID not in the table is still detected,
as
J-Link.
5. Connectivity & Control
USB Power Switching
Which Plugable dock ports actually switch power
A Plugable dock enumerates as two cascaded 4-port hubs with identical descriptors. Both advertise per-port power switching (wHubCharacteristics=0x00a9, PortPwrCtrlMask=0xff), so the descriptor cannot
tell them apart. Only the topology can:
Lager exposes only the user tier. The four lager ports are therefore the four
external Type-A sockets. On the validated model, three are on the rear and one is
on the front. The dock’s own network adapter can never be switched off by accident.
Which lager port number is which physical socket is not defined. Nothing ties
USB hub port order to the order of connectors on a case, and the order can differ
between models. Determine it once, empirically. Move a device that enumerates
through each socket in turn. Any USB stick or debug probe will do. Read back which
port it lands on:
SuperSpeed docks are untested. A dock linked over USB 3 enumerates as two
virtual hubs, and VBUS drops only when power is cleared on both halves. Lager
implements that pairing, but no SuperSpeed-linked dock was available to
validate it. A topology that it cannot pair unambiguously is refused rather than
half-switched. The validated configuration is a USB 2.0 link.
lager usb <net> recover re-asserts power
on every port of that dock. If that cannot reach the hub, unbinding and
rebinding the kernel hub driver re-powers every port and re-enumerates the
children. That must be run on the box host, not in the container, which
mounts /sys read-only — replace the path with your hub’s:
- Automated USB device cycling
- Remote power reset of DUTs
- CI-controlled peripheral management
Serial / UART Adapters
Enables:
- Automated log capture
- Bootloader interaction
- Serial-based test automation
Wireless
Enables:
- Wireless device testing
- Remote connectivity validation
- Automated provisioning tests
Network Routers
Enables:
- Interface and Wi-Fi fault injection
- Network-resilience testing
- Inspection of wireless clients and DHCP leases
Hardware Security Modules
Enables:
- Key generation and signing on the bench
- Device provisioning with keys that do not leave the HSM
- Factory reset of a test HSM between runs
6. Vision & Automation
Cameras
Any USB video class (UVC) camera works withlager webcam, including a box’s built-in camera.
A model not in this table is listed as UVC_Camera, with its product name under it in
lager instruments. HDMI capture cards are UVC too, but are listed for a scope’s live view
rather than as cameras.
Enables:
- Visual DUT inspection
- Automated visual verification
Robotic Automation
Capabilities:
- Position read/write
- Homing
- Motor enable/disable
- Acceleration configuration
- Automated physical interaction with hardware
- Button press automation
- Mechanical test workflows
Custom Instrument Support
Lager’s modular architecture allows new instruments to be integrated quickly through backend extensions. If you use equipment not listed in this document, please contact us to discuss integration support.Contact
Lager Data GitHub GitHub IssuesFootnotes
-
The YKUSH3’s GPIO pins 1-3 are
gpionets. Not yet verified on hardware: the pins’ voltage level, and whether a written level is held. Check both with a meter before wiring a pin to a device. Lager never enables the hub’s “GPIO control” mode (ykushcmd ykush3 --gpio enable). That mode hands the USB ports to the GPIO pins. If it is on,lager usbreports that a port did not switch. The hub’s switchable 5V output is not controlled by Lager. ↩ -
Unlike the Acroname and Yepkit hubs, Plugable ships no SDK. Control
uses the standard USB hub class per-port power switching (PPPS), so support
depends on the individual hub genuinely implementing it. Matched by VID:PID
2230:5411, which Plugable reuses across its RTS5411 dock line; validated on a UD-CAM. Only the four external Type-A sockets switch VBUS — see below. Requires the udev rule for vendor2230(shipped in99-instrument.rules); without it libusb cannot open the hub and every operation fails with a permission error. ↩

