Nets

Nets are the core abstraction in Lager for representing physical test points, signals, or buses on your device under test. Each net maps a friendly name to a specific instrument channel.

Syntax

lager nets [OPTIONS] [COMMAND]

Global Options

Option	Description
`--box TEXT`	Lager Box name or IP address
`--help`	Show help message and exit

Commands

Command	Description
(none)	List all saved nets (default)
`delete`	Delete a specific net by name and type
`delete-all`	Delete all saved nets (dangerous)
`rename`	Rename an existing net
`add`	Add a new net
`add-all`	Auto-create all available nets from connected instruments
`add-batch`	Create multiple nets from a JSON file
`assign`	Assign a USB-serial cable to an RS-232 instrument the box can’t auto-detect
`show`	Show full details of a saved net, including metadata
`state`	Show the live hardware state of every saved net
`describe`	Set metadata on a saved net (purpose, notes, tags) for agent-assisted testing
`tui`	Launch interactive Net Manager TUI
`set-script`	Attach a J-Link script or OpenOCD `.cfg`/`.tcl` to a debug net (backend auto-detected)
`remove-script`	Remove the debug script (J-Link or OpenOCD) attached to a debug net
`show-script`	Display the debug script attached to a debug net

Command Reference

List Nets (Default)

List all saved nets on a Lager Box. This is the default behavior when no subcommand is provided.

lager nets --box my-lager-box

The output groups the nets by instrument. Each group starts with the instrument name and its address. The nets of the group follow as a tree. Output Columns:

Column	Description
`Name`	User-friendly net identifier
`Net Type`	Role/type of net (power-supply, debug, adc, gpio, i2c, spi, etc.)
`Channel`	Specific channel on the instrument
`Script`	`yes` when a J-Link script is attached
`OpenOCD`	`yes` when an OpenOCD config is attached
`Purpose`	The `purpose` text set with `describe`, cut to fit the column

The Script, OpenOCD and Purpose columns appear only when at least one net has a value for them. Run lager nets show NAME to see the full purpose text. Example Output:

    Name      Net Type      Channel
========================================
LabJack T7 [USB0::0x0CD5::0x0007::::INSTR]
├── adc1      adc           AIN0
└── gpio1     gpio          FIO0

Rigol DP811 [USB0::0x1AB1::0x0E11::DP8B123456::INSTR]
└── supply1   power-supply  1

SiLabs CP210x [USB0::0x10C4::0xEA60::0001::INSTR]
└── uart1     uart          /dev/ttyUSB0

`add`

Create a new net by specifying its name, type, channel, and instrument address.

lager nets add NAME ROLE CHANNEL ADDRESS [OPTIONS]

Arguments:

NAME - Unique name for the net (e.g., supply1, debug_main)
ROLE - Type of net: power-supply, battery, solar, debug, adc, dac, gpio, scope, logic, eload, uart, usb, webcam, arm, watt-meter, energy-analyzer, thermocouple, i2c, spi. The legacy tokens supply and batt are accepted as input aliases and normalized to power-supply / battery — saved nets always carry the canonical role.
CHANNEL - Channel identifier, as lager instruments lists it (e.g., 1, AIN0, FIO0, I2C0, STM32F4)
ADDRESS - VISA address or device path, as lager instruments lists it (e.g., USB0::0x0CD5::0x0007::::INSTR)

Options:

--box TEXT - Lager Box name or IP
--jlink-script FILE - J-Link script file for debug nets (stored on box)
--openocd-config FILE - OpenOCD .cfg/.tcl file for debug nets (stored on box)
--sda PIN / --scl PIN - Custom LabJack pins for i2c nets
--cs PIN / --sck PIN / --mosi PIN / --miso PIN - Custom LabJack pins for spi nets
--interface A|B|C|D - FTDI channel for a gpio, i2c or spi net on an FT2232H or FT4232H. The default is A. See Multi-channel FTDI debug adapters below.

Pin values accept LabJack DIO names or raw DIO numbers. The two LabJack families accept different pins:

Instrument	Pin names	DIO numbers
LabJack T7	`FIO0`-`FIO7`, `EIO0`-`EIO7`, `CIO0`-`CIO3`, `MIO0`-`MIO2`	`0`-`22`
LabJack U3	`FIO4`-`FIO7`, `EIO0`-`EIO7`, `CIO0`-`CIO3`	`4`-`19`

A U3 has no MIO pins. Its FIO0-FIO3 are fixed analog inputs, so Lager refuses them for gpio, i2c and spi nets. The EIO and CIO lines of a U3 are on its DB15 connector. When pin options are given, the CHANNEL argument is ignored — pass custom. If a chosen pin overlaps another saved LabJack net, a warning is printed but the net is still created. --cs is optional: omit it for 3-pin SPI with manual chip select. Examples:

# Create a power supply net
lager nets add supply1 power-supply 1 TCPIP::192.168.1.100::INSTR --box my-lager-box

# Create a debug net for STM32
lager nets add debug1 debug STM32F407VG USB::001::002 --box my-lager-box

# Create a debug net with J-Link script
lager nets add debug1 debug STM32F407VG USB::001::002 --jlink-script ./my_device.JLinkScript --box my-lager-box

# Create an ADC net on a LabJack T7
lager nets add temp_sensor adc AIN0 USB0::0x0CD5::0x0007::::INSTR --box my-lager-box

# Create an I2C net on a LabJack T7 (default pins: SDA=FIO4, SCL=FIO5)
lager nets add i2c_bus i2c FIO4-FIO5 USB0::0x0CD5::0x0007::::INSTR --box my-lager-box

# Create an I2C net on a LabJack T7 with custom pins
lager nets add i2c_bus i2c custom USB0::0x0CD5::0x0007::::INSTR --sda EIO0 --scl EIO1 --box my-lager-box

# Create an I2C net on a LabJack U3 (default pins: SDA=FIO6, SCL=FIO7)
lager nets add u3_i2c i2c FIO6-FIO7 USB0::0x0CD5::0x0003::::INSTR --box my-lager-box

# Create an I2C net on Aardvark
lager nets add i2c_aardvark i2c I2C0 USB0::0x0403::0xE0D0::2238595116::INSTR --box my-lager-box

# Create an SPI net on a LabJack T7 (default pins: CS=FIO0, SCK=FIO1, MOSI=FIO2, MISO=FIO3)
lager nets add spi_bus spi FIO0-FIO3 USB0::0x0CD5::0x0007::::INSTR --box my-lager-box

# Create an SPI net on a LabJack T7 with custom pins
lager nets add spi_flash spi custom USB0::0x0CD5::0x0007::::INSTR --cs FIO6 --sck FIO7 --mosi EIO0 --miso EIO1 --box my-lager-box

# Custom-pin SPI without chip select (3-pin SPI, manual CS via gpio)
lager nets add spi_flash spi custom USB0::0x0CD5::0x0007::::INSTR --sck FIO7 --mosi EIO0 --miso EIO1 --box my-lager-box

# Create an SPI net on a LabJack U3 (default pins: CS=FIO4, SCK=FIO5, MISO=FIO6, MOSI=FIO7)
lager nets add u3_spi spi FIO4-FIO7 USB0::0x0CD5::0x0003::::INSTR --box my-lager-box

# Create an SPI net on Aardvark
lager nets add spi_aardvark spi SPI0 USB0::0x0403::0xE0D0::2238595116::INSTR --box my-lager-box

# Create a UART net
lager nets add serial1 uart 0 /dev/ttyUSB0 --box my-lager-box

The --jlink-script option is only applicable for debug nets. If used with other net types, a warning is printed and the option is ignored.

Validation Rules:

Net names must be globally unique across all types
The (role, instrument, channel, address) tuple must match a connected instrument
The channel must be one that the box offers for that role. Run lager instruments to see the list.
The address must identify one device. See Two devices of the same model below.
Channel binding follows the per-instrument rules described in Channel & Role Constraints below

When the channel is not valid, add prints the valid channels for the role and exits with code 1:

The channel 'FIO0' is not valid for role 'gpio' on the instrument at USB0::0x0CD5::0x0003::::INSTR.
Valid gpio channels for LabJack_U3: FIO4, FIO5, FIO6, FIO7, EIO0, EIO1, EIO2, EIO3, EIO4, EIO5, EIO6, EIO7, CIO0, CIO1, CIO2, CIO3
FIO0-FIO3 on a LabJack U3 are fixed high-voltage analog inputs and are never digital I/O. Read them with an adc net on AIN0-AIN3, the same physical pins.

The last line appears only for a U3 gpio, i2c or spi net on FIO0-FIO3.

The box holds the channel list. A newer CLI against an older Lager Box validates against the older list. Run lager update to get the current list.

Channel & Role Constraints

Different instrument families bind nets to channels differently. Lager classifies every supported instrument into one of three categories and enforces the rules consistently across add, add-all, and the TUI.

1. Multi-channel instruments

Instruments with physically independent outputs / inputs. Each channel is its own circuit and can host its own net.

Instrument	Channels	Notes
`Rigol_DP811` / `DP821` / `DP831` / `DP832`	`1`, `2`, `3`	One `power-supply` net per output
`KEYSIGHT_E36233A`	`1`, `2`	Dual-output supply
`KEYSIGHT_E36313A` / `E36312A`	`1`, `2`, `3`	Triple-output supply
`LabJack_T7`	`AIN0`–`AIN13`, `FIO0`–`FIO7`, `DAC0`–`DAC1`, etc.	One net per pin
`LabJack_U3`	`AIN0`–`AIN15`, `DAC0`–`DAC1`; `gpio` on `FIO4`–`FIO7`, `EIO0`–`EIO7`, `CIO0`–`CIO3`; `spi` on `FIO4-FIO7`; `i2c` on `FIO6-FIO7`	`FIO0`–`FIO3` are fixed high-voltage analog inputs — read them with an `adc` net on `AIN0`–`AIN3`, never as `gpio`, `spi` or `i2c`. Lager treats every U3 as a U3-HV, so a U3-LV also loses these four digital lines. The `spi` and `i2c` spans overlap; one net of each is fine
`Rigol_MSO5204`	`scope` on `1`–`4`; `logic` on `1`	One `scope` net per analog channel, and one `logic` net
`Aardvark`	`SPI0`, `I2C0`, GPIO pins	Mixed-mode multi-channel
`MCC_USB-202`	`CH0`–`CH7`, `DIO0`–`DIO7`, `DAC0`–`DAC1`	One net per channel
`Phidget`	`0`–`3`	One `thermocouple` net per channel
`Acroname_8Port` / `4Port`, `YKUSH_Hub`	Port indices	One `usb` net per port

Rule: at most one net per (instrument, address, role, channel) tuple. Two nets that share (instrument, address, role) but differ in channel are fine — that’s exactly what multi-channel is for.

2. Single-channel, multi-mode instruments

Instruments with one physical channel that can run in one of several modes but not multiple modes at once. The role tells the box which firmware mode to flip the chip into. Lager treats two groups of these chips differently. Single-output instruments (one net per role, with a notice):

Instrument	Roles	What happens with a second role
`Keithley_2281S`	`battery` and `power-supply`	One output: battery-simulator firmware OR power-supply firmware
`EA_PSB_10080_60`	`solar` and `power-supply`	One output: solar-array simulator OR straight supply
`EA_PSB_10060_60`	`solar` and `power-supply`	Same as above

Rule: you can save one net for each role on the same chip. When the chip already has a net, add prints this notice and saves the second net:

Keithley_2281S at <ADDRESS> already has a battery net. This instrument is a single output that fills one role at a time — the driver switches its mode automatically when you drive the other net, ending whatever the previous mode was doing. Add the second net only if you intend to use both roles.

Each command on a net switches the instrument into the mode of that net. The switch stops the work of the other mode. add-all does not pick a role for a chip with no saved net: it skips the chip with a warning. The TUI does not let you select both roles of one chip in one batch. Mode-exclusive chips (one net in total):

Instrument	Allowed roles	Why exclusive
`FTDI_FT232H`	`spi` or `i2c` or `gpio` or `debug` or `uart`	One channel hardware-multiplexed between MPSSE (libftdi) and async-serial (`ftdi_sio`) modes

Rule: at most one net per (instrument, address). Once any role is saved on the chip, every other role disappears from the add list of add-all and the TUI. To switch modes, delete the existing net first. These chips are tracked in _SINGLE_CHANNEL_INST (Keithley, EA) and _MODE_EXCLUSIVE_INST (FTDI_FT232H) in cli/commands/box/nets.py and cli/commands/box/net_tui.py.

3. Single-role debug probes

Standalone debugger boxes — one probe drives one target MCU.

Instrument	Backend	Role
`J-Link` / `J-Link_Plus` / `Flasher_ARM` / `J-Link_Flasher_Pro`	J-Link (SEGGER)	`debug`
`STLink_v2` / `v2_1` / `v3` / `v3_Mini` / `v3_2VCP`	OpenOCD	`debug`
`RP2040_Picoprobe`	OpenOCD (CMSIS-DAP)	`debug`
`Atmel_EDBG`	OpenOCD (CMSIS-DAP)	`debug`
`DAPLink`	OpenOCD (CMSIS-DAP)	`debug`

Rule: at most one debug net per (instrument, address).

4. Multi-channel FTDI debug adapters

FT2232H (2 channels: A, B) and FT4232H (4 channels: A, B, C, D) physically expose multiple USB interfaces. Channels A and B have an MPSSE engine; on the FT4232H, C and D do not. That matters per net type, not per chip. debug, spi and i2c are MPSSE protocols, so they are limited to A and B. gpio runs as asynchronous bitbang, needs no MPSSE, and works on all four. The user picks an interface per net. Debug nets encode the channel in the device field:

# Channel A (interface 0) — by far the most common
lager nets add debug_a debug STM32F4x@A USB0::0x0403::0x6010::ABCDEF::INSTR

# Channel B (interface 1) — second target on the same FT2232H
lager nets add debug_b debug NRF52840_XXAA@B USB0::0x0403::0x6010::ABCDEF::INSTR

Equivalent forms: @A/@0, @B/@1, @C/@2, @D/@3. Devices without an @ suffix default to the interface OpenOCD’s interface config picks (typically channel A). GPIO, I2C and SPI nets take the channel from --interface when you add the net:

# I2C on channel B of an FT4232H
lager nets add sensors i2c I2C0 USB0::0x0403::0x6011::ABCDEF::INSTR --interface B

# A reset line on channel C, which has no MPSSE engine
lager nets add reset_line gpio 5 USB0::0x0403::0x6011::ABCDEF::INSTR --interface C

lager nets add stores the channel as params.interface on the net record. A net with no interface uses channel A, the only channel of an FT232H. The Net-Manager TUI does not ask for a channel, so it adds these nets on channel A. lager nets add refuses a channel that the part does not have for the net type, and it names the channels that work. An i2c or spi net cannot use channel C or D, because those channels have no MPSSE engine. A gpio net can use any channel of the part. The box drivers apply the same rules to a net record that you edit by hand, and they accept A-D or 0-3. UART nets distinguish channels by their tty path. The USB scanner enumerates every /dev/ttyUSB<N> bound to the chip’s USB serial. Each one shows up as a separate add-list entry, so on an FT4232H you will see up to four UART options. Rule: the channel is part of a net’s identity. A debug net is unique per (instrument, address, channel-suffix). A gpio, i2c or spi net is unique per (role, instrument, pin, address, interface). So a single FT2232H can host:

one debug net on @A
one debug net on @B
one uart net on a /dev/ttyUSB<N> belonging to whichever channels you didn’t claim for MPSSE
gpio, i2c and spi nets on each channel that --interface names. The same pin number can carry one net on each channel.

The user is responsible for not double-booking a channel (e.g. debug@A and a spi net on interface A); the box doesn’t validate that today.

Quick decision table

You want to add a second net on the same chip	Allowed?
`power-supply` on `Rigol_DP811` CH1 + `power-supply` on Rigol_DP811 CH2	Yes
`battery` on `Keithley_2281S` + `power-supply` on the same Keithley	Yes, with a notice — the nets share one output
`solar` on `EA_PSB_10080_60` + `power-supply` on the same EA	Yes, with a notice — the nets share one output
`spi` on `FTDI_FT232H` + `uart` on the same FT232H	No — pick one
`spi` on `LabJack_U3` + `i2c` on the same U3	Yes — the default spans share `FIO6` and `FIO7`
`debug@A` on `FTDI_FT2232H` + `uart` on a different interface of the same FT2232H	Yes
Two `debug@A` nets on the same `FTDI_FT2232H`	No — same channel
Two `debug` nets on the same J-Link	No — single-target probe

Two devices of the same model

Lager decides whether it can create a net from the device address, not from the model. An address that includes a unique serial number names one device. Two devices of that model on one Lager Box both work. For example, two 8-port Acroname hubs give sixteen usb nets. A LabJack T7 and a LabJack U3 report no serial number, so their addresses have an empty serial field. Two T7 units, or two U3 units, on one Lager Box report the same address. A net cannot say which device it means, so Lager refuses it:

Error: LabJack_T7 at USB0::0x0CD5::0x0007::::INSTR: more than one device reports this address, so a net could not say which one it means. This model exposes no unique serial number. Use only one at a time, or drive them from separate boxes.

add exits with code 1. add-all and the TUI skip those devices with the same message. lager instruments hides them and prints the message. One T7 and one U3 on the same Lager Box work, because their addresses differ.

`add-all`

Automatically create nets for all available channels on all connected instruments. This is useful for quickly setting up a new Lager Box.

lager nets add-all [OPTIONS]

Options:

--box TEXT - Lager Box name or IP
--yes - Skip confirmation prompt

Example:

# Preview what nets would be created
lager nets add-all --box my-lager-box

# Create all nets without prompting
lager nets add-all --box my-lager-box --yes

Output:

Found 7 nets that can be created:
  - supply1 (power-supply) on Rigol_DP811 channel 1
  - adc1 (adc) on LabJack_T7 channel AIN0
  - adc2 (adc) on LabJack_T7 channel AIN1
  - gpio1 (gpio) on LabJack_T7 channel FIO0
  - i2c1 (i2c) on LabJack_T7 channel FIO4-FIO5
  - spi1 (spi) on LabJack_T7 channel FIO0-FIO3
  - debug1 (debug) on J-Link channel STM32F4

Create all 7 nets on box <BOX_IP>? [y/N]:

Before the list, add-all prints a warning for each device that it skips. It skips two devices of one model that report the same address. It also skips a single-output or mode-exclusive chip with no saved net. That chip offers more than one role, and add-all does not choose one for you.

`add-batch`

Create multiple nets from a JSON file for efficient bulk setup.

lager nets add-batch JSON_FILE [OPTIONS]

Arguments:

JSON_FILE - Path to JSON file containing net definitions

Options:

--box TEXT - Lager Box name or IP

JSON Format:

[
  {
    "name": "supply1",
    "role": "power-supply",
    "channel": "1",
    "address": "USB0::0x1AB1::0x0E11::DP8B123456::INSTR"
  },
  {
    "name": "i2c_bus",
    "role": "i2c",
    "channel": "FIO4-FIO5",
    "address": "USB0::0x0CD5::0x0007::::INSTR"
  },
  {
    "name": "spi_bus",
    "role": "spi",
    "channel": "SPI0",
    "address": "USB0::0x0403::0xE0D0::2238595116::INSTR"
  }
]

Each record needs name, role, channel and address. An optional instrument key names the instrument. When it is absent, the command looks up the instrument from the address. An optional params object sets what the lager nets add options set:

sda_pin and scl_pin for a LabJack i2c net, or cs_pin, clk_pin, mosi_pin and miso_pin for a LabJack spi net. Each value is a pin name or a DIO number. Name the instrument in the record, because the pins depend on the model.
interface (A-D) for an FTDI FT2232H or FT4232H net.

The command checks these values as lager nets add checks its options. It refuses any other key in a record or in params. To give a debug net a script, add the net first, then use set-script.

{
  "name": "sensor_bus",
  "role": "i2c",
  "channel": "custom",
  "address": "USB0::0x0CD5::0x0007::::INSTR",
  "instrument": "LabJack_T7",
  "params": {"sda_pin": "EIO0", "scl_pin": "EIO1"}
}

Validation: Before it saves anything, the command checks each record for these problems:

A key that the command does not read, or a bad params value
A role that the instrument does not support
An address that more than one present device reports
A channel that the box does not offer for the role

It lists every record that fails, prints No nets were saved., and exits with code 1:

Net 2 ('i2c_bus'): channel '0' is not valid for role 'i2c' on LabJack_T7. Valid: FIO4-FIO5
No nets were saved.

The command does not check the channel of two kinds of record:

A record whose address is not in the current instrument scan, for example an instrument that is not connected
A uart record, because its channels are per-device tty paths

A record with no instrument whose address is not in the scan also skips the role check. Example:

lager nets add-batch nets.json --box my-lager-box

`assign`

Assign a USB-serial cable to a known instrument the box cannot auto-detect. Some instruments have no USB control port. You reach such an instrument over RS-232 through a generic USB-serial adapter — a Rigol DP711 power supply behind a Prolific cable, for example. The box sees only the adapter (a uart device), not the instrument behind it. assign records “this cable is the DP711’s serial line” on the box. From then on, the scanner reports the instrument itself. It appears in lager instruments and in the TUI, and you can create nets for it with lager nets add like any auto-detected device. Assign once per cable; the assignment is stored on the box and survives reboots and replugs. Creating nets stays the normal, repeatable step.

lager nets assign --list [OPTIONS]                       # discover
lager nets assign DEVICE --serial|--port [OPTIONS]       # assign
lager nets assign --remove --serial|--port [OPTIONS]     # unassign

Options:

Option	Description
`--list`	List assignable devices, current assignments, and unassigned USB-serial cables
`--serial TEXT`	USB serial number of the cable (durable; the assignment follows the cable across ports)
`--port TEXT`	USB port path (sysfs name, e.g. `1-1.2`); pins the assignment to a physical box port — for cables without a usable serial number
`--baud INTEGER`	Baud-rate override; must match the instrument’s front-panel setting (DP711 factory default: 9600)
`--remove`	Remove the assignment matching `--serial`/`--port`
`--as-net [NAME]`	Also create a net for the instrument right away (name defaults to the device name)
`--box TEXT`	Lager Box name or IP

End-to-end example (Rigol DP711):

# 1. Plug the instrument's USB-serial cable into the box, then find it:
lager nets assign --list --box my-lager-box
#   Unassigned USB-serial cables:
#     serial 00000006  port 1-1.2  [067b:23a3]  /dev/ttyUSB0

# 2. Assign the cable — and create a supply net in the same step:
lager nets assign Rigol_DP711 --serial 00000006 --as-net main_supply --box my-lager-box

# 3. Drive it like any other supply net:
lager supply main_supply voltage 3.3 --box my-lager-box

Without --as-net, the command prints the exact lager nets add invocation for the new instrument:

lager nets add <name> power-supply 1 'serial://067b:23a3/serial/00000006'

How it works:

The cable must be plugged in to assign it — its USB identity (vendor/product ID) is captured from the live device.
Nets for assigned instruments use a durable serial://<vid>:<pid>/serial/<s> (or .../port/<p>) address instead of a /dev/ttyUSB* path, so they survive tty renumbering, reboots, and port moves.
While a cable is assigned, it is no longer offered as a generic UART device — the serial line belongs to the instrument.

Some cheap USB-serial clones share one serial number (or have none). If assign reports multiple matching cables, pin the assignment to a physical box port with --port instead. The trade-off is that if you move the cable to a different port, the assignment breaks.

Removing an assignment:

lager nets assign --remove --serial 00000006 --box my-lager-box

The cable is offered as a generic UART device again. Nets live and die with their assignment: any saved nets bound to the assignment’s serial:// address are deleted automatically and reported in the output. The same cascade applies when you re-assign a cable to a different instrument, and when you switch its identity from --serial to --port. Only a baud-only re-assign keeps the existing nets. Currently assignable devices: Rigol DP711 (single-channel RS-232 power supply). Run lager nets assign --list to see the catalog your box supports.

`delete`

Delete a specific net by its name and type.

lager nets delete NAME NET_TYPE [OPTIONS]

Arguments:

NAME - Name of the net to delete
NET_TYPE - Type of the net (supply, debug, adc, i2c, spi, etc.)

Options:

--box TEXT - Lager Box name or IP
--yes - Skip confirmation prompt

Example:

# Delete a supply net (with confirmation)
lager nets delete supply1 supply --box my-lager-box

# Delete without confirmation
lager nets delete temp_sensor adc --box my-lager-box --yes

# Delete an I2C net
lager nets delete i2c_bus i2c --box my-lager-box --yes

`delete-all`

Delete all saved nets on a Lager Box. This is a dangerous operation.

lager nets delete-all [OPTIONS]

Options:

--box TEXT - Lager Box name or IP
--yes - Skip confirmation prompt

Example:

# Delete all nets (requires confirmation)
lager nets delete-all --box my-lager-box

# Delete all nets without prompting
lager nets delete-all --box my-lager-box --yes

`rename`

Rename an existing net.

lager nets rename NAME NEW_NAME [OPTIONS]

Arguments:

NAME - Current name of the net
NEW_NAME - New name for the net (must be unique)

Options:

--box TEXT - Lager Box name or IP

Example:

lager nets rename supply1 main_power --box my-lager-box

`tui`

Launch an interactive terminal-based UI for managing nets. The TUI provides a visual interface for viewing, creating, and deleting nets.

lager nets tui [OPTIONS]

Options:

--box TEXT - Lager Box name or IP

Example:

lager nets tui --box my-lager-box

TUI Features:

Browse all connected instruments and their channels
Create new nets with guided prompts (+ Add Nets)
Read warnings and notices on the Add screen. They appear together in one block, and the Dismiss button hides the block.
Pick custom pins for a LabJack T7 or U3 i2c or spi net. The pencil button on the row opens one editor for the net name and the pins. The pin dialog also opens when you add the net, unless you already set the pins. The dialog shows the current pins, and offers only the pins that the model can use. You can set CS to none for 3-pin SPI. If you choose the defaults again, the net gets the default channel back. A pin already used by a saved net shows a warning
Rename a new net with the pencil button on its row
Assign custom serial devices (RS-232 instruments) to their USB cables with Assign Device — the interactive twin of assign, including the optional create-the-net step (--as-net)
Select a saved net to Rename, Edit Details or Delete it. Edit Details sets Purpose, Notes and Tags. It changes only those three fields and keeps the rest of the net record.
Delete every saved net with Delete All Nets
Keyboard navigation (q or Ctrl+C quits)

Model	Default I2C pins	Default SPI pins	Pins the dialog offers
LabJack T7	SDA=FIO4, SCL=FIO5	CS=FIO0, SCK=FIO1, MOSI=FIO2, MISO=FIO3	Every DIO pin
LabJack U3	SDA=FIO6, SCL=FIO7	CS=FIO4, SCK=FIO5, MOSI=FIO7, MISO=FIO6	`FIO4`-`FIO7`, `EIO0`-`EIO7`, `CIO0`-`CIO3`

`set-script`

Attach a debug script — either a JLinkScript or an OpenOCD .cfg/.tcl — to an existing debug net. The file is stored on the box and used automatically during connect, flash, erase, and reset operations. The backend (J-Link vs. OpenOCD) is auto-detected from two signals:

The probe’s USB VID on the net’s address field (J-Link → jlink; ST-Link, FTDI, CMSIS-DAP, etc. → openocd).
The file — extension first (.JLinkScript → jlink; .cfg/.tcl/.ocd → openocd), with a content sniff as a tie-breaker for extensionless files or stdin.

If the two signals disagree, set-script refuses with a clear error and asks you to pick one via --backend. A debug net only carries one script at a time. If the other field is already set, set-script clears it and prints a yellow notice on stderr so nothing disappears silently.

lager nets set-script NAME SCRIPT_PATH [OPTIONS]

Arguments:

NAME - Name of the debug net
SCRIPT_PATH - Path to the script file, or - to read from stdin

Options:

--backend [jlink|openocd] - Force a specific backend instead of auto-detecting (required if the probe and file disagree)
--box TEXT - Lager Box name or IP

Example:

# Attach a J-Link script to a J-Link net (auto-detected)
lager nets set-script debug1 ./custom_connect.JLinkScript --box my-lager-box

# Attach an OpenOCD config to an FTDI/ST-Link/CMSIS-DAP net (auto-detected)
lager nets set-script debug1 ./probe.cfg --box my-lager-box

# Read the script from stdin
cat probe.cfg | lager nets set-script debug1 - --box my-lager-box

# Force a specific backend when the file or probe is ambiguous
lager nets set-script debug1 ./generic_script --backend openocd --box my-lager-box

`remove-script`

Remove the debug script (J-Link or OpenOCD) attached to a debug net.

lager nets remove-script NAME [OPTIONS]

Arguments:

NAME - Name of the debug net

Options:

--backend [jlink|openocd] - Only remove the named backend’s script (default: remove whichever is set)
--box TEXT - Lager Box name or IP

Example:

# Remove whichever script is attached
lager nets remove-script debug1 --box my-lager-box

# Only remove the J-Link script (leave any OpenOCD config in place)
lager nets remove-script debug1 --backend jlink --box my-lager-box

`show-script`

Display the contents of the debug script attached to a debug net. The script content is written to stdout, so > out.cfg works. A one-line summary like # OpenOCD config, 1247 bytes is written to stderr. That tells you which backend’s script you see, and it does not pollute a redirect.

lager nets show-script NAME [OPTIONS]

Arguments:

NAME - Name of the debug net

Options:

--backend [jlink|openocd] - Only show the named backend’s script (default: show whichever is set)
--box TEXT - Lager Box name or IP

Example:

# Display the attached script (J-Link or OpenOCD)
lager nets show-script debug1 --box my-lager-box

# Save to a local file (the stderr banner doesn't end up in the file)
lager nets show-script debug1 --box my-lager-box > script.txt

`show`

Display all fields of a saved net, including user-provided metadata (purpose, notes, tags) set with describe.

lager nets show NAME [OPTIONS]

Arguments:

NAME - Name of the net

Options:

--json - Output as raw JSON
--box TEXT - Lager Box name or IP

Example:

lager nets show battery1 --box my-lager-box
lager nets show battery1 --json --box my-lager-box

`state`

Show the live hardware state of every saved net. The box reads each instrument and returns a short summary for each net. The output is the grouped table of lager nets, with a State column after Channel.

lager nets state [OPTIONS]

Options:

--box TEXT - Lager Box name or IP
--json - Output as raw JSON

Example:

lager nets state --box my-lager-box
lager nets state --json --box my-lager-box

Example Output:

    Name      Net Type      Channel       State
=============================================================
Acroname 8Port [USB0::0x24FF::0x0013::EBFB0000::INSTR]
├── usb1      usb           0             –
└── usb2      usb           1             –

LabJack T7 [USB0::0x0CD5::0x0007::::INSTR]
├── adc1      adc           AIN0          1.2345V
└── gpio1     gpio          FIO0          HIGH (1)

Rigol DP811 [USB0::0x1AB1::0x0E11::DP8B123456::INSTR]
└── supply1   power-supply  1             CH1/on/3.30V/0.120A

SiLabs CP210x [USB0::0x10C4::0xEA60::0001::INSTR]
└── uart1     uart          /dev/ttyUSB0  –

Nets reporting no state:
    usb1, usb2: unreadable: <error from the hub driver>
    -> the hub is not on the USB bus at all -- unplugged, or its upstream port is off.

State values:

Net type	State	Example
`power-supply`	Channel, output, voltage, current	`CH1/on/3.30V/0.120A`
`battery`	Channel, output, terminal voltage, current, state of charge	`CH1/on/3.70V/0.100A/50%`
`usb`	Port power	`enabled`, `disabled`
`gpio`	Level	`HIGH (1)`, `LOW (0)`
`adc`, `dac`	Voltage	`1.2345V`
`thermocouple`	Temperature	`25.0°C`
`eload`	Mode, input, voltage, current	`<mode>/on/5.00V/1.000A`
`webcam`	Stream	`stopped`, `streaming <url>`
`watt-meter`	Current, voltage, power over 0.1 s	`0.1200A/3.300V/0.3960W`
`energy-analyzer`	Mean current, voltage, power over 0.5 s	`0.1200A/3.300V/0.3960W`
`arm`	Position	`X0.0/Y250.0/Z0.0`
`debug`	GDB server	`connected/jlink`, `connected/openocd`, `disconnected`
`solar`	Irradiance	`irr:<value>`
`router`	Uptime	`up/<uptime>`
`i2c`	Addresses that answer a bus scan	`0x48,0x76`, `no devices`

Net types with no probe, such as uart, spi, scope and logic, show –. How the box reads the nets:

The box groups the nets by instrument and reads up to eight instruments at the same time.
All instruments share one budget of 8 seconds. When the budget ends, every net that did not answer reports deadline.
The box reads USB hubs one after another. It does not read a hub that has less than 1 second of budget left, and the nets of that hub report hub-skipped.
A read takes the same instrument locks as a running test, so the command can wait for a test.
The box reads an i2c net with a full bus scan.
On a LabJack T7, one batch reads all gpio, adc and dac nets, and a gpio read does not change the pin direction.
On a LabJack U3, a gpio or adc read sets the pin to digital or analog mode. A U3 dac net shows – until the box sets a value.

Nets reporting no state: Below the table, the command explains each – that has a reason. It groups the nets by reason. A net type with no probe is normal, so the footnote does not list it.

Reason	Meaning
`deadline`	The shared budget ended before the instrument answered. This alone does not mean that the instrument is slow.
`unreadable: <detail>`	The box tried to read the instrument and got no value. The detail names the error.

A usb net can also carry a code. When all nets in a group have the same code, the footnote adds one remedy line:

Code	Remedy line
`hub-unreachable`	The hub is on the USB bus but does not answer. Check its power and upstream cable. A restart of the box services does not help.
`hub-absent`	The hub is not on the USB bus. It is unplugged, or its upstream port is off.
`hub-serial-mismatch`	Hubs are on the bus, but none has the serial that the net names. Check the address of the net.
`hub-skipped`	The box did not read the hub, because slower instruments used the budget first. The hub can be fine. A read of that hub alone answers.
`hub-open-failed`	No remedy line. The reason names the failure.

JSON output: --json prints an array with one object for each saved net. Each object holds all stored fields of the net, plus these fields:

Field	Description
`live_state`	The state string, or `null`
`live_state_reason`	Why the state is `null`, including `no probe for role`. Present only when the box sent a reason.
`live_state_reason_code`	The code of a `usb` net. Present only when the box sent a code.

A box without this endpoint prints a note to update it. The table still prints, with – in every State cell.

`describe`

Set metadata on a saved net so AI agents (and humans) understand what the net does on the DUT. Introduced in lager 0.24.0; the fields feed agent-assisted testing via the MCP server. At least one of --purpose, --notes, --tag, --dut-connection or --test-hint (or one of the --clear-* flags) must be provided. A Lager Box on 0.46.0 or later serves these fields over HTTP, so a connected control plane can sync them. dut_connection and test_hints need a box on 0.50.0 or later.

lager nets describe NAME [OPTIONS]

Arguments:

NAME - Name of the net

Options:

-p, --purpose TEXT - One sentence: what this net does on the DUT
-n, --notes TEXT - Optional notes (gotchas, jumper positions, scope probe points)
-t, --tag TEXT - Tag for categorisation/matching (repeatable)
--clear-tags - Remove all existing tags before adding new ones
--dut-connection TEXT - Where the net lands on the DUT: connector, pin or test point (e.g. "J3 pin 4")
--test-hint TEXT - One-line advice for a test author (repeatable)
--clear-test-hints - Remove all existing test hints before adding new ones
--box TEXT - Lager Box name or IP

Example:

# Describe a net's purpose and add tags
lager nets describe battery1 \
  --purpose "Main battery rail powering the MCU" \
  --tag power --tag critical \
  --box my-lager-box

# Say where the net lands on the DUT and leave a hint for the test author
lager nets describe battery1 \
  --dut-connection "J1 pin 2 (VBAT)" \
  --test-hint "ramp from 3.0 V; the DUT browns out below 2.8 V" \
  --box my-lager-box

# Replace the existing tags
lager nets describe battery1 --clear-tags --tag power --box my-lager-box

# View what was set
lager nets show battery1 --box my-lager-box

Net Types Reference

Net Type	Description	Typical Instruments
`power-supply` (alias `supply`)	Power supply output	Rigol DP800, Rigol DP711 (via `assign`), Keithley 2200/2280, Keysight E36200
`battery` (alias `batt`)	Battery simulator	Keithley 2281S
`solar`	Solar simulator	EA PSI/EL series
`eload`	Electronic load	Rigol DL3021
`debug`	Debug probe	J-Link, CMSIS-DAP, ST-Link
`adc`	Analog input	LabJack T7, LabJack U3
`dac`	Analog output	LabJack T7, LabJack U3
`gpio`	Digital I/O	LabJack T7, LabJack U3 (`FIO4` and up), MCC USB-202
`i2c`	I2C bus	LabJack T7, LabJack U3, Aardvark, FTDI FT232H / FT2232H / FT4232H
`spi`	SPI bus	LabJack T7, LabJack U3, Aardvark, FTDI FT232H / FT2232H / FT4232H
`scope`	Oscilloscope	Rigol MSO5000, PicoScope
`logic`	Logic analyzer channel	Rigol MSO5204
`uart`	Serial port	Prolific USB, SiLabs CP210x
`usb`	USB port control	Acroname hub, YKUSH, Plugable dock
`webcam`	Video capture	Logitech BRIO
`arm`	Robot arm	Rotrics Dexarm
`watt-meter`	Power measurement	Yocto Watt
`thermocouple`	Temperature sensor	Phidget thermocouples

Debug Script Workflow

Both J-Link and OpenOCD debug probes can carry a custom script for handling reset sequences, clock initialization, board-specific signal pinning, or other device-specific behavior. Lager stores one script per debug net — either a JLinkScript or an OpenOCD .cfg/.tcl, never both. It applies that script automatically during connect, flash, erase, and reset operations.

# Attach a J-Link script to a J-Link probe (auto-detected from .JLinkScript extension)
lager nets set-script debug1 ./my_device.JLinkScript --box my-lager-box

# Attach an OpenOCD config to an FTDI / ST-Link / CMSIS-DAP probe (auto-detected)
lager nets set-script debug1 ./probe.cfg --box my-lager-box

# Verify what's attached (stderr says which backend, stdout has the content)
lager nets show-script debug1 --box my-lager-box

# Scripts are used automatically for all debug operations:
lager debug debug1 flash --hex firmware.hex --box my-lager-box
lager debug debug1 gdbserver --box my-lager-box

# Remove the script when no longer needed
lager nets remove-script debug1 --box my-lager-box

You can also attach a script at net creation time:

lager nets add debug1 debug STM32F407VG USB::001::002 \
  --jlink-script ./my_device.JLinkScript --box my-lager-box

lager nets add debug2 debug d2763 USB::003::004 \
  --openocd-config ./probe.cfg --box my-lager-box

You can also configure J-Link scripts per-project in the local .lager config file:

{
  "DEBUG": {
    "debug1": "./scripts/my_device.JLinkScript"
  }
}

When both a net-level script (via set-script) and a project-level script (via .lager config) exist, the project-level script takes priority.

Examples

# List all nets
lager nets --box my-lager-box

# Create a new power supply net
lager nets add vdd_main power-supply 1 TCPIP::192.168.1.100::INSTR --box my-lager-box

# Create I2C and SPI bus nets
lager nets add i2c_sensors i2c FIO4-FIO5 USB0::0x0CD5::0x0007::::INSTR --box my-lager-box
lager nets add spi_flash spi SPI0 USB0::0x0403::0xE0D0::2238595116::INSTR --box my-lager-box

# Show the live state of every net
lager nets state --box my-lager-box

# Auto-create all available nets
lager nets add-all --box my-lager-box --yes

# Delete a specific net
lager nets delete old_supply supply --box my-lager-box --yes

# Rename a net
lager nets rename supply1 main_power --box my-lager-box

# Launch interactive manager
lager nets tui --box my-lager-box

# Bulk create from JSON file
lager nets add-batch testbed-nets.json --box my-lager-box

# Manage debug-probe scripts (J-Link or OpenOCD, auto-detected)
lager nets set-script debug1 ./custom_init.JLinkScript --box my-lager-box
lager nets set-script debug2 ./probe.cfg --box my-lager-box
lager nets show-script debug1 --box my-lager-box
lager nets remove-script debug1 --box my-lager-box

Notes

Net names are globally unique regardless of type
Use lager instruments --box <lager-box> to see available instruments and channels
The TUI provides the easiest way to set up nets for the first time
Use add-all to quickly configure a new Lager Box with sensible defaults
I2C and SPI nets are supported on LabJack T7, LabJack U3, Aardvark, and FTDI FT232H, FT2232H and FT4232H adapters
Debug scripts (both J-Link and OpenOCD) are base64-encoded for storage and decoded automatically during debug operations
A debug net carries at most one script (jlink_script or openocd_config); set-script enforces this by clearing the other field when present

Lager Box Management

Configuration

Power & Simulation

Measurement

I/O & Communication

Development

Utilities

Syntax

Global Options

Commands

Command Reference

List Nets (Default)

`add`

Channel & Role Constraints

1. Multi-channel instruments

2. Single-channel, multi-mode instruments

3. Single-role debug probes

4. Multi-channel FTDI debug adapters

Quick decision table

Two devices of the same model

`add-all`

`add-batch`

`assign`

`delete`

`delete-all`

`rename`

`tui`

`set-script`

`remove-script`

`show-script`

`show`

`state`

`describe`

Net Types Reference

Debug Script Workflow

Examples

Notes

​Syntax

​Global Options

​Commands

​Command Reference

​List Nets (Default)

​add

​Channel & Role Constraints

​1. Multi-channel instruments

​2. Single-channel, multi-mode instruments

​3. Single-role debug probes

​4. Multi-channel FTDI debug adapters

​Quick decision table

​Two devices of the same model

​add-all

​add-batch

​assign

​delete

​delete-all

​rename

​tui

​set-script

​remove-script

​show-script

​show

​state

​describe

​Net Types Reference

​Debug Script Workflow

​Examples

​Notes

Syntax

Global Options

Commands

Command Reference

List Nets (Default)

`add`

Channel & Role Constraints

1. Multi-channel instruments

2. Single-channel, multi-mode instruments

3. Single-role debug probes

4. Multi-channel FTDI debug adapters

Quick decision table

Two devices of the same model

`add-all`

`add-batch`

`assign`

`delete`

`delete-all`

`rename`

`tui`

`set-script`

`remove-script`

`show-script`

`show`

`state`

`describe`

Net Types Reference

Debug Script Workflow

Examples

Notes