RDM-Compliance Testing
The RDM compliance test runs a structured set of checks against a device under test and reports whether its RDM implementation behaves as it should. It is the feature that most often justifies reaching for a KLSTR.rdm instead of a fixture's built in RDM bridge.
The tester lives in the settings of a nano that is connected to KLSTR.ctrl as an
RDM controller, so it needs both special builds in place: sniffer.klstr.nano on the
nano and the usbNano build of KLSTR.ctrl on the PC. The compliance test is not
present in the standard build at all.
Before you start
You need a working KLSTR.rdm, which means both earlier pages in this section are done and both special builds are in place:
You also need the device under test cabled to the nano over DMX, and reachable over RDM.
Conduct the test
Open the settings of the connected nano
With the nano connected as an RDM controller, open its settings.
Open the RDM compliance test
The RDM compliance test feature is in the settings. Open it to reach the compliance page.
Work through the three stages
The compliance page runs in three stages. Follow them in order against your device under test.
- TODO: name and describe stage 1, and state what a pass looks like.
- TODO: name and describe stage 2, and state what a pass looks like.
- TODO: name and describe stage 3, and state what a pass looks like.
/images/klstr-rdm/compliance-step-1.png,
/images/klstr-rdm/compliance-step-2.png,
/images/klstr-rdm/compliance-step-3.png.Troubleshooting
| Symptom | Most likely cause |
|---|---|
| No compliance test in the settings | Wrong KLSTR.ctrl build. The usbNano build is required |
| The nano is connected but no device under test is found | The DUT is not reachable over RDM. Check the DMX cabling and terminate the line |
| Settings do not open as an RDM controller | The nano is connected as a plain device, not promoted. Recheck the firmware page |
Related
- Firmware Update over RDM explains the RDM transport and the manufacturer specific PID family at the protocol level.