RDMBench

Fixtures

What RDMBench's public fixture library knows about particular brands and models, from the fixtures themselves, their manuals and units on the bench, each with its source.

Library version
20261005.1
Brands
3
Models profiled
1
Version
0.2.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)
Price
Free

These pages are rdmbench-pids, the public fixture library RDMBench ships with and keeps up to date, as a page per brand and per model. The library holds what a fixture on the bench cannot say about itself.

What it holds

  • Manufacturer parameters, per brand. Makers add parameters of their own to RDM (PIDs 0x8000 to 0xFFDF), and many fixtures list them in SUPPORTED_PARAMETERS but will not describe them. A brand’s table names them, so a report shows a word instead of a number in hex. Its wanted list is the ones fixtures list and refuse to describe that no table names yet.
  • Profiles, per model. What a model says about itself over RDM, captured from one unit: every DMX personality, every sensor’s definition and the parameters it lists. On top of that, what the wire cannot show: what the model is known to get wrong (its quirks), what each channel does where the fixture reports no slot table of its own, and which channels a load test must hold at a level of their own.

On the bench, the fixture’s own answers always win. Makers reuse parameter numbers across product generations, and a profile is true of the firmware it was captured from.

Where it comes from

Every table and profile names its source, specifically enough to check: a maker’s manual with its revision and page, a fixture’s own answers with the model and firmware, or a run on the bench with its date and method. These pages quote each source as the library gives it. A quirk is an observation someone can repeat, not an opinion, and not a statement by the manufacturer.

Nothing in the library comes from the Open Lighting Project’s PID data, which carries no licence grant.

Adding to it

RDMBench captures a profile from a unit on the bench: Fixture → Contribute Fixture Profile… in the app, or rdmbench-cli export-profile --share. Either reads every personality and leaves out the unit’s UID, and the app opens a prefilled pull request. A parameter the library does not know is proposed from the report’s banner (see The PID library). Fixture onboarding, planned, is the paid way to have a model profiled.

Brands