# Fine in one mode, not in others

- **MCP resource:** rdmbench://help/mode-sweep
- **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

Some faults only show in one personality (mode): a status message that
only appears in the extended mode, a channel that does nothing in the
16-bit mode, a sensor that only moves under load in one of them. A mode
sweep finds them. It runs the same check in each mode you pick, shows
the modes side by side, and then puts the unit back in its own mode
and at its own address.

What differs between the columns is the finding. A fault in one mode
only is that mode or its firmware, not the cable or the lamp, and
saves readdressing a rig to chase it.

## In the app

Select the fixture and choose **Fixture → Sweep Modes…** *(macOS)* / **Fixture → Measure → Sweep modes…** *(Windows, Linux)*, or
right-click the unit in the sidebar *(macOS)* / the fixture list *(Windows, Linux)*. Pick the check:

- **Report**: the report in each mode, and nothing else.
- **Under Load**: the report, then the fixture lit and its sensors read
  in each mode, as a [load test](/help/load/) does. **The fixture
  goes bright and hot in each mode.** Each mode is held for 30 seconds
  unless you choose otherwise. Each mode starts warmer than the one
  before it, so a temperature that only differs in the later modes may
  be the earlier mode's heat, not the mode itself. Sweep that mode on
  its own, from cold, to be sure.
- **Walk by Eye**: the report, then each mode's channels walked one at
  a time, as [Walk Channels](/help/channel-walk/) does. Mark each
  channel, then click **Next Mode**. **End Sweep** stops early.

Under Load and Walk by Eye light the fixture, so they are offered only
on a connection that can send DMX: the widget, or a universe of an
Art-Net rig that nothing else is driving
([Send DMX](/help/send-dmx/) says how a node is checked).

Then tick the modes to run. Every mode the unit lists is ticked to
start, with its channel count. A mode whose channels would run past 512
at the unit's address is skipped and nothing is sent, and the sheet *(macOS)* / dialog *(Windows, Linux)*
says so before you start.

**Sweep** sets each mode and reads it back, takes the report again, and
runs the check. **Stop** finishes the mode it is in. Either way, the
unit goes back to the mode and address it was in before the results
appear. If it can't be put back, the results say so first, with the
mode it was in. Set it back with **Fixture → Change Address and Mode…** *(macOS)* / **Fixture → Change address and mode…** *(Windows, Linux)* or from the unit's menu.

A console patched to the unit sees the wrong mode while the sweep runs.
The sweep is unavailable while levels are held with Send DMX, during a
load test, during a channel walk and while the unit is being monitored.
Each of those is placed by the unit's mode.

## Reading the results

One column per mode: its channel count, the report's verdict and how
many lines are above OK, and the check's own result. The channel count
is the one the mode describes. Where the unit reports a different number
for itself in that mode, that number is shown under it, and the
disagreement is one line under **What differs** with the modes it showed
in (see [Footprint disagrees with the mode](/help/address-mode/#footprint-disagrees-with-the-mode)).
Under **What differs** is each line of the report, sensor or channel
that showed in some modes and not the others, with the modes it showed
in. A mode that was skipped, failed or not reached says why below.

The sweep is filed under the unit, and its
[repair sheet](/help/repair-sheet/) lists what differed. Loads
and walks run inside a sweep are part of the sweep, not filed on their
own.

## If RDMBench quits during a sweep

The next launch lists the sweep under **Interrupted Work**, with the
mode it left the unit in and the mode and address it came from. Click
**Put Back** to set the unit back once its line is open. See
[Interrupted work](/help/interrupted/).

## From the command line

`rdmbench-cli sweep` runs the report in every mode of the first fixture
found, or of the UID given after it, and prints the modes side by side.
`--mode 1 --mode 3` picks the modes. `--check load` lights the fixture
in each mode for `--seconds` (30 by default). `--check walk` walks each
mode's channels at the keyboard. Ctrl-C stops after the mode it is in
and still puts the unit back. `rdmbench-cli recover` lists a sweep a
killed run left behind, and `restore` puts its unit back.

## From an AI assistant

An assistant connected to the bench can run a sweep with the report or
the load check, never a walk. It asks you before changing anything, and
puts the unit back before it answers. It is not offered on an Art-Net
rig for now; run the sweep yourself there.
