/serial/`
(or `.../port/`) 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 moving the cable to a
different port breaks the assignment.
**Removing an assignment:**
```bash theme={null}
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 re-assigning a cable to a different instrument (or switching 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.
```bash theme={null}
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` - Lagerbox name or IP
* `--yes` - Skip confirmation prompt
**Example:**
```bash theme={null}
# 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.**
```bash theme={null}
lager nets delete-all [OPTIONS]
```
**Options:**
* `--box TEXT` - Lagerbox name or IP
* `--yes` - Skip confirmation prompt
**Example:**
```bash theme={null}
# 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.
```bash theme={null}
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` - Lagerbox name or IP
**Example:**
```bash theme={null}
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.
```bash theme={null}
lager nets tui [OPTIONS]
```
**Options:**
* `--box TEXT` - Lagerbox name or IP
**Example:**
```bash theme={null}
lager nets tui --box my-lager-box
```
**TUI Features:**
* Browse all connected instruments and their channels
* Create new nets with guided prompts
* Pick custom LabJack pins when adding i2c/spi nets — a pin dialog opens with
the defaults preselected (I2C: SDA=FIO4/SCL=FIO5; SPI: CS=FIO0/SCK=FIO1/
MOSI=FIO2/MISO=FIO3); any DIO pin can be chosen per signal, CS can be set to
none for 3-pin SPI, and pins already used by saved nets show a warning
* Assign custom serial devices (RS-232 instruments) to their USB cables — the
interactive twin of [`assign`](#assign), including the optional
create-the-net step (`--as-net`)
* Delete existing nets
* View net details and instrument information
* Keyboard navigation
### `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:
1. **The probe's USB VID** on the net's `address` field (J-Link → `jlink`; ST-Link, FTDI, CMSIS-DAP, etc. → `openocd`).
2. **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.
```bash theme={null}
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` - Lagerbox name or IP
**Example:**
```bash theme={null}
# 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.
```bash theme={null}
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` - Lagerbox name or IP
**Example:**
```bash theme={null}
# 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 so interactive use tells you which backend's script you're looking at without polluting redirects.
```bash theme={null}
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` - Lagerbox name or IP
**Example:**
```bash theme={null}
# 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`.
```bash theme={null}
lager nets show NAME [OPTIONS]
```
**Arguments:**
* `NAME` - Name of the net
**Options:**
* `--json` - Output as raw JSON
* `--box TEXT` - Lagerbox name or IP
**Example:**
```bash theme={null}
lager nets show battery1 --box my-lager-box
lager nets show battery1 --json --box my-lager-box
```
### `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](/source/reference/mcp/overview). At least one of `--purpose`,
`--notes`, or `--tag` (or `--clear-tags`) must be provided.
```bash theme={null}
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
* `--box TEXT` - Lagerbox name or IP
**Example:**
```bash theme={null}
# 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
# 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`](#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 |
| `dac` | Analog output | LabJack T7 |
| `gpio` | Digital I/O | LabJack T7, MCC USB-202 |
| `i2c` | I2C bus | LabJack T7, Aardvark |
| `spi` | SPI bus | LabJack T7, Aardvark |
| `scope` | Oscilloscope | Rigol MSO5000, PicoScope |
| `uart` | Serial port | Prolific USB, SiLabs CP210x |
| `usb` | USB port control | Acroname hub, YKUSH |
| `camera` | 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) and applies it automatically during connect, flash, erase, and reset operations.
```bash theme={null}
# 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:
```bash theme={null}
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:
```json theme={null}
{
"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
```bash theme={null}
# 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 0 USB::470026574 --box my-lager-box
lager nets add spi_flash spi 0 USB::2238595116 --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 ` 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 and Aardvark 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