# The rig sheet and its sensor readings

- **MCP resource:** rdmbench://help/rig-sheet
- **Version:** 0.12.0
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Needs:** An Enttec DMX USB Pro with its DMX/RDM firmware (major version 2), or, on a rig, an Art-Net 4 node with RDM on at its ports
- **Price:** Free

The **rig sheet** is one spreadsheet row for every unit on the line, or
on every universe of a rig. It is for the paperwork around the
bench: the patch for a production office, or what went out and what came
back on a rental return. Beside it goes the **sensor sheet**, one row for
every sensor reading, so units of a model can be compared with each
other.

For a quick look, on the built-in simulator, watch
[What came back, and in what shape? Read the whole rig into one sheet.](https://youtu.be/J6TcB1pyt8g)

To see every column step by step, on the built-in simulator, and what a
green row does not say about the patch, watch
[How to read a whole DMX rig into one spreadsheet, step by step](https://youtu.be/9M8MIfn0wtg)

## Making one

**On macOS:**

Choose **Fixture → Read Every Unit for Rig Sheet…**. It takes a fresh
report of every unit, on every universe of a rig at once, and then
opens the sheet. That includes the units you have left alone: this is
you asking by hand, and it does not change which units are chosen. On a
big rig it takes a while. The status bar counts the units read, and
**Stop** opens the sheet with the reports taken so far.

**Fixture → Export Rig Sheet…** (⇧⌘E) opens the sheet over the reports
already taken this session, without reading anything. A unit with no
report is named under the table, not left out.

The sheet opens in a window of its own, so the sidebar and each unit's
report stay usable beside it. A report you take while it is open is
read into it at once. Disconnecting closes it.

**Save…** (⌘S) writes the sheet, then the sensor sheet beside it with
`-sensors` on the end of its name: `rig-2026-11-01.csv` and
`rig-2026-11-01-sensors.csv`.

**On Windows, Linux:**

Choose **Fixture → Repair → Export rig sheet…** for the sheet over the reports
taken this session. A unit with no report is named under the table, not
left out. The sensor sheet comes from the command line, below.

From the command line:

```
rdmbench-cli scan --all --csv -o rig.csv
```

writes `rig.csv` and `rig-sensors.csv`. On a rig, every universe goes in one
sheet. Without `-o`, the rig sheet goes to the
screen, and `--sensors` puts the sensor sheet there instead.

## The readings are idle

The bench drives nothing to take these readings: each unit is read as it
was at the time. They are good for comparing units with each other, such
as one unit whose sensor reads 0 where three of the same model read 24.
They do not say how a unit behaves while it is working. For that, run a
[load test](/help/load/) on the unit.

## The rig sheet's columns

One row per unit, in DMX address order, a universe at a time on a rig.

- `uid`, `manufacturer`, `model`, `label`: who the unit is. The label is
  usually its position on the truss.
- `dmx_address`, `footprint`, `personality`, `personality_name`: how it
  is patched.
- `firmware`
- `device_hours`, `lamp_hours`, `lamp_strikes`, `power_cycles`: the
  unit's counters. Where its model file knows the unit keeps a lifetime
  count that cannot be reset, as a MAC Aura does, the lifetime count is
  used, and `notes` says the counter was reset.
- `sub_devices`: how many modules a rack or multi-head unit reports.
- `rollup`: `ok`, `warning` or `error`, the report's verdict.
- `scanned_at`: when that unit was read.
- `notes`: why the unit is not green, in one sentence, or why it has no
  data at all.
- `universe`: the universe as a console numbers it, empty on a widget's
  line.
- `serial`: the serial printed on the unit. `(blank)` means the unit
  answered with nothing printable. An empty cell means it gave no serial.
- `sensors`, `sensors_out`: how many sensors the unit reports, and how
  many read outside their normal range.

A unit that was found but gave no report still gets a row, with its
columns empty and the reason in `notes`.

**A unit that has just started** can read 0 on every sensor for its
first seconds. When every one of a unit's sensors reads 0 at once,
`notes` says it may still have been starting. Those sensors are not
counted in `sensors_out`, and its counters stand in for any lifetime
figures. Read it again once it has run a minute. A unit with a single
sensor reading 0 is not treated this way: that is a reading worth
looking at.

## The sensor sheet's columns

One row per reading:

- `uid`, `universe`, `label`: whose reading it is.
- `sensor`: the sensor's name, in the maker's words.
- `type`: what it measures, such as `temperature`. `unit`: what it is
  measured in, such as `°C`.
- `value`, `lowest`, `highest`: the reading, and the lowest and highest
  recorded, where they are kept.
- `normal_min`, `normal_max`: the range given as normal, where there is
  one.
- `read_at`: when it was read.
- `number`: the sensor's number, which tells apart two sensors with the
  same name.
- `sub_device`: the module, for a rack. Empty otherwise.

Where a sensor's own description cannot be true, such as a voltage
measured in °C, `type`, `unit` and the limits are left empty and
`value` is the number that was sent. It can still be compared with the
same sensor on others of the model.

Sort on `value` with the sheet filtered to one sensor, and the odd one
out is at the top or the bottom. A pivot table puts them side by side.

In both sheets, text that a spreadsheet would run as a formula, such as
a label starting with `=`, gets a leading `'` so it shows as text.
