# RDMBench

Read a fixture over its DMX cable, not through its menu one setting at a time.

> A desktop app that reads DMX/RDM lighting fixtures over their own cable, in the shop or at the show: identity, faults, sensors against their limits, and configuration, as far as each fixture reports them, with the complaint the unit came in with answered first. Plug a fixture into an Enttec DMX USB Pro on the bench, or read a live rig through its Art-Net nodes. A wrong mode or address is often the whole fault, and the reading comes before any part is swapped.

## At a glance

- **Version:** 0.12.0
- **Released:** 2026-11-09
- **Runs on:** macOS 15 Sequoia or later, Apple silicon or Intel
- **Other platforms:** Windows and Linux are planned and not started
- **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
- **Download:** https://www.rdmbench.com/download/macos
- **AI assistants:** A built-in MCP server that runs on the bench computer, for Claude, Cursor, VS Code and Claude Code

![RDMBench's report on a simulated Martin MAC Aura: rated OK, five sensors inside their normal ranges, DMX address 1 in the 25-channel Standard personality, and the complaint 'Wrong colors' answered with: nothing the fixture reports explains it; compare the personality with the desk's patch.](https://www.rdmbench.com/images/app/report-light.webp)

*The report, on the built-in simulator.*

## One unit, before and after

A MAC Aura comes in for wrong colors. It shows no error, on its display
or anywhere else.

**Without the bench,** its menu is read a setting at a time, nothing
there looks wrong, and boards are swapped until the colors come right
or the parts run out.

**On the bench,** *Wrong colors* is picked under **Came in for** and the
unit is read once. The report answers the complaint first: nothing the
fixture reports explains wrong colors, and the usual cause is a desk
patched for a different mode, so compare the personality and its
channel count with the desk's patch. The report shows both, and with
the fixture's GDTF file, the name the desk gives that mode
([Find a fixture's desk mode](/help/desk-mode/)). When the patch is the
fault, no board was ever the problem.

The report above is this case on the built-in simulator, not a
customer's unit.

## What it changes on a fixture

- **A report only reads.** It asks the fixture questions and changes
  nothing on it.
- **A load test ends output by itself:** when its time is up, when it
  is stopped, when the fixture stops answering, and when RDMBench
  quits. If it cannot, the report says so
  ([Load test a fixture](/help/load/)).
- **A mode sweep puts the unit back** in the mode and at the address it
  was in before its results appear, and says so first if it cannot.
- **A restore never replaces a file.** It shows what it would do before
  writing anything, adds back what is missing, and keeps this bench's
  copy of anything that differs; the settings it would change are
  listed, each with its value now and after
  ([Back up the bench](/help/backup/)).

## In the shop or at the show

**In the shop,** plug the fixture into an [Enttec DMX USB Pro](https://www.enttec.com/product/dmx-usb-interfaces/dmx-usb-pro-professional-1u-usb-to-dmx512-converter/) and read it
on the bench, one unit at a time.

**At the show,** the fixtures are already on Art-Net nodes. Plug the
computer into the lighting network and the app reads every universe the
nodes report, each with its own line report: who is missing since the
last look, and what is wrong between units. The same report then opens
on any one fixture ([Connect](/help/connect/)).

## What a report holds

The report reads the fixture over RDM (ANSI E1.20) and puts the answer
to the tech's question first.

- **Came in for.** The customer's complaint, picked from a list, and
  then the lines of the report that explain it, or a plain "nothing
  the fixture reports explains this; look at the line".
- **Status.** One green, yellow or red rollup, from the fixture's own
  status messages and its sensors against their limits.
- **Sensors.** Temperatures, voltages and the rest, flagged near or at
  their limits.
- **Configuration.** DMX address and personality, what each channel of
  that personality does, and, with the fixture's GDTF file, what a
  lighting desk calls that mode. A wrong mode or address is often the
  whole fault.

## Beyond the report

- **Monitor.** Keeps asking, and draws each sensor's trend against its
  normal range, for the fault that needs time to show.
- **Load test.** Lights the fixture, reads its sensors while it works,
  and ends output by itself, for the fan that never speeds up or the
  module that draws no current.
- **Channel walk.** Puts each channel up in turn while you watch, for
  what only shows in the beam: a sticking color wheel, a dead emitter.
  You mark each one pass or fail.
- **Behavior check.** Asks whether the fixture follows the RDM standard
  at all, for the line that misbehaves while every report looks fine.
- **Standards.** File one unit's settings as the standard for its model
  and firmware, and set the rest of the fleet to match.

## What it remembers

Every report is kept on the bench computer, under the unit it came
from. Two reports of the same unit can be compared, and a unit's
history read back when it returns.

- **The repair sheet.** When the work is done, one page for the
  customer: what they said was wrong, what the bench found and did, the
  channels checked by eye and the load tests run, and how the unit
  leaves. Print it or save it as a PDF.
- **Backups.** The whole bench in one file, by hand or on a schedule.
  Restoring adds back what is missing and never replaces a file.

## Where to go next

- [Download](/download/): the newest build, and how updates work.
- [Requirements](/requirements/): the Mac, the widget's firmware, the
  terminator, and what a rig's nodes need.
- [Assistants](/assistants/): connecting Claude, Cursor, VS Code or
  Claude Code to the bench.
- [Why RDMBench](/why/): what it does that other tools don't, and what
  it is not.
- [Videos](https://www.youtube.com/@RDMBench): the app at work, on the simulator, in
  short videos.

## What it is not

- Not a handheld tester. It runs on a computer at the bench or the desk; a pocket RDM tester is the tool for the truss.
- Not show control or rig patching. It works on a live rig, but it is built for one fixture at a time, read in depth.
- Not a maker's own service tool. For Martin fixtures, use Martin's own tools: Companion Desktop on Windows, or Companion Mobile on iOS and Android. They know Martin's status codes, private parameters and firmware better than any cross-brand tool.
- Not a meter. It reads only what a fixture reports over RDM. A fixture that reports no sensors, or ignores what it should answer, gives the report less to go on; the report lists a required answer that never came, and the behavior check says how far to trust what did.
- Not a hosted service. Reports are kept on the bench computer, and the MCP server runs there too.
