RDM Basics
Remote Device Management over DMX512 Networks (RDM) has been developed by
PLASA as a communications and control protocol to allow devices to be remotely
managed via existing DMX512 wiring, and is basically a variation on DMX512. Further,
the protocol is defined to allow existing (“legacy”) DMX devices to be connected and
operate on the same link as RDM devices and operate normally. This can occur
because the RDM data signals are “mixed in” with conventional DMX data signals, and
while conventional legacy DMX devices cannot respond to or communicate via the
RDM data, they will continue to respond to the DMX portion of the data, while
(hopefully) ignoring the RDM portion (more on the “hopefully” later). The other big
difference between DMX and RDM is that DMX is a simplex or “one way” protocol, while
RDM is a half-duplex or “two way” protocol. DMX data always flows from the controller
to the controlled devices, while RDM can flow back, and forth.
A full length DMX512 packet includes 513 data bytes. For conventional DMX
communication, the first byte should consist of all 0s, while the remaining 512 bytes
contain the data intended to control the 512 DMX devices connected to the link. That
first byte has been referred to variously as the Start Code, Null Byte, 0 Byte, etc. RDM
data looks very much the same as DMX data, except that the packet length can vary
with each communication, the longest packet is 257 bytes, and the first byte contains
different data than all 0s. The data in that first byte identifies the packet as an RDM
rater than DMX packet.
An RDM system consists of a controller and one or more responders. These units will
normally be operating as a conventional DMX network. When RDM control activity is
needed, the controller will issue a special RDM data command to alert any connected
RDM devices, and then may issue any of a variety of other RDM commands to trigger
actions or responses in the connected responders (dimmers, fog machines, whatever).
As mentioned above, the RDM data is mixed in with conventional DMX data and, in
theory should be invisible to conventional DMX devices on the link.
An RDM session must begin with RDM Discovery, during which the controller identifies
and builds a list of all the connected RDM responders connected to its data link. Once
the controller has discovered all of the connected responders, they can be monitored,
adjusted, configured and generally managed individually over the RDM data link.
During normal RDM operations, the Discovery process is periodically repeated so that
added, removed, or failed devices can be identified and the controller’s list can be
updated.
Page 7
The ISL and Linear curves are optimized for incandescent loads, and the
LED curve is optimized for LEDs.
LED TV/Film Mode:
Five options for LED (mode
three
by default).
LED Smoothing:
Six different delay times to make LED dim at different
rates; 5ms, 10ms, 50ms, 100ms, 200ms
,
and 400ms (100ms smoothing by
default).
Misc. Settings
Bump
Enable
:
Enables or Disables Bump Buttons
.
Data
Hold
T-Out:
Adjust how long the last valid DMX level is held if DMX
is lost, from
five
minutes–120 Minutes, plus infinity
.
Panel Lock Out-
Locks the user interface. (Unlock by pressing L+R
buttons at the same time.)
Backlight T-Out:
Allows adjustment of the Backlight automatic shutoff
time-out from Always off, through 1-240 seconds on, to
a
lways on
.
Input Status:
Displays input status as DMX OK or DMX No Data
.
Firmware:
Displays firmware version.
Restore Defaults:
Restores factory defaults as DMX start
one
, ISL
Curve on all,
ten
sec. backlight time-out,
five
min. DMX data loss time-out
.
