View Connected Instruments
To view all instruments currently connected to a specific Lager Box, run:Example Output:
Automatic Net Creation
When an instrument is plugged into a Lager Box, Lager automatically creates a default Net for each function the instrument supports.- A simple, single-function device like a power supply will create one
SupplyNet. - A multi-function device like a LabJack T7 DAQ will create several Nets: one for
GPIO, one forADC, one forDAC, and (if configured) one each forI2CandSPI. - An I2C/SPI adapter like a Total Phase Aardvark will create both an
I2CNet and anSPINet, since the adapter supports both protocols.
Modify or Assign Nets Using the TUI
For instruments that support multiple channels (e.g. LabJack, PicoScope), you can assign new Nets using the interactive TUI (text user interface). You can also re-name existing Nets. To launch the Net TUI, run:Within the TUI, you can:
- Add new Nets
- Rename existing Nets
- Delete unused Nets
RS-232 Instruments (Manual Assignment)
Some instruments have no USB control port and connect through a USB-serial adapter — for example, a Rigol DP711 power supply on its RS-232 port. The Lager Box sees only the adapter cable, so it can’t tell what instrument is behind it, and nothing appears automatically. Tell the box what the cable is connected to, once per cable:lager nets tui) via the
Assign Device button: pick the cable, pick the instrument, and name the
net in the same flow — done.
After assignment, the instrument shows up in lager instruments and in the
TUI like any auto-detected device, and nets can be added for it normally. The
assignment is stored on the box and survives reboots and replugs.
See the nets assign reference for
port-pinned assignments, baud-rate overrides, and removal.
Debug Nets
For debug instruments (e.g., Segger J-Link, ST-Link), you must specify the target MCU when creating the net. This is easily done through the TUI, as it will prompt you to input the MCU type.Important: The MCU type must match a valid target device supported by your debug probe. If the MCU type is not recognized, the debugger will not function correctly.
Next Steps
With your instruments configured, start controlling them:- Interacting With Nets — Send commands to your instruments via CLI or Python

