DMX512 Topologia
DMX512 Topologia
DMX512 Topologia
The specification requires a 'terminator' to be connected to the final OUT or THRU connector of the last
slave on the daisy chain, which would otherwise be unconnected. A terminator is a stand-alone male
connector with an integral 120 Ω resistor connected across the primary data signal pair; this resistor matches
the cable's characteristic impedance. If a secondary data pair is used, a termination resistor is connected
across it as well. Although simple systems (i.e., systems having few devices and short cables) will
sometimes function normally without a terminator, the standard requires its use. Some DMX slave devices
have built-in terminators that can be manually activated with a mechanical switch or by software, or by
automatically sensing the absence of a connected cable.
A DMX512 network is called a "DMX universe".[4] Each OUT connector on a DMX512 controller can
control a single universe. A DMX512 universe is made up of 512 channels, with each channel containing a
value between 0 and 255. Each slave device in the chain can "look at" a different set of channels in order to
be controlled by the master controller. Smaller controllers may have a single OUT connector, enabling them
to control only one universe, whereas large control desks (operator consoles) may have the capacity to
control multiple universes, with an OUT connector provided for each universe. Many of the more modern
control desks instead of featuring multiple OUT connectors have a Unshielded Twisted Pair connector
(such as CAT5, CAT5e or CAT6. ) Such cables and systems can control up to 32768 universes of
DMX512[5] using the Art-Net protocol or 65536 using the sACN protocol, and the existing Ethernet in
buildings.
Physical layer
Electrical
DMX512 data is transmitted over a differential pair using EIA-485 voltage levels. DMX512 electrical
specifications are identical to those of the EIA-485-A standard, except where stated otherwise in E1.11.
DMX512 is a bus network no more than 400 metres (1,300 ft) long, with not more than 32 unit loads
(individual devices connected) on a single bus. If more than 32 unit loads need to communicate, the
network can be expanded across parallel buses using DMX splitters. Network wiring consists of a shielded
twisted pair, with a characteristic impedance of 120 ohms, with a termination resistor at the end of the cable
furthest from the controller to absorb signal reflections. DMX512 has two twisted pair data paths, although
specification currently only defines the use of one of the twisted pairs. The second pair is undefined, but
required by the electrical specification.
The E1.11 (DMX512 2004) electrical specification addresses the connection of DMX512 signal common
to earth ground. Specifically, the standard recommends that transmitter ports (DMX512 controller OUT
port) have a low impedance connection between signal common and ground; such ports are referred to as
grounded. It is further recommended that receivers have a high impedance connection between signal
common and ground; such ports are referred to as isolated.
The standard also allows for isolated transmitter ports, and non-isolated receivers. It also recommends that
systems ground the signal common at only one point, in order to avoid the formation of disruptive ground
loops.
Grounded receivers that have a hard connection between signal common and ground are permitted but their
use is strongly discouraged. Several possible grounding configurations which are commonly used with
EIA485 are specifically disallowed by E1.11.
Connectors
The original DMX512 1990 specified that where connectors are used, the data link shall use five-pin XLR
style electrical connectors (XLR-5), with female connectors used on transmitting (OUT) ports and male
connectors on receiving ports.
The use of any other XLR style connector is prohibited.
The three-pin XLR connector is commonly used for DMX512, on lighting and related control equipment,
particularly at the budget/DJ end of the market. However, using three-pin XLR connectors for DMX512 is
specifically prohibited by section 7.1.2 of the DMX512 standard. Use of the three-pin XLR in this context
firstly presents a risk of damage to the lighting equipment should an audio cable carrying 48 volt phantom
power be accidentally connected, and secondly encourages the use of cable following analogue audio
specifications for DMX, which can lead to signal degradation and unreliable operation of the DMX
network.
DMX512-A (ANSI E1.11-2008) defined the use of eight-pin modular (8P8C, or "RJ-45") connectors for
fixed installations where regular plugging and unplugging of equipment is not required.
Note: Several manufacturers used other pinouts for RJ-45 connectors prior to this inclusion in the standard.
Other form-factors of connectors are permitted on equipment where the XLR and RJ-45 would not fit or are
considered inappropriate, for example on equipment intended for permanent installation.
7.2 Equipment intended for fixed installation with internal connections to the data link
Fixed installation products with internal connections to the data link may use the 5-pin XLR
connector, but shall not use any other XLR connector. When use is made of the 5-pin XLR
connector, the requirements of 7.1 and 7.1.1 shall apply. When a non-XLR connector is used,
this Standard makes no other restriction or stipulation on connector choice. The contact (pin)
numbering on the alternate connector should match numbering for the standard 5-Pin XLR
XLR-5 pinout
1. Signal Common
2. Data 1- (Primary Data Link)
3. Data 1+ (Primary Data Link)
4. Data 2- (Optional Secondary Data Link)
5. Data 2+ (Optional Secondary Data Link)
RJ-45 pinout
1. Data 1+
2. Data 1-
3. Data 2+
4. Not Assigned
5. Not Assigned
6. Data 2-
7. Signal Common (0 V) for Data 1
8. Signal Common (0 V) for Data 2
The 8P8C modular connector pinout matches the conductor pairing scheme used by Category 5 (Cat5)
twisted pair patch cables. The avoidance of pins 4 and 5 helps to prevent equipment damage, if the cabling
is accidentally plugged into a single-line public switched telephone network phone jack.
In the early days of digital lighting control, several equipment manufacturers employed various connectors
and pinouts for their proprietary digital control signals.
The most common of these was the three-pin XLR connector (also called cannon jack in some countries).
When DMX512 was ratified, many of these manufacturers then issued firmware updates to enable the use
of DMX512 control on their existing equipment by the use of a simple adapter to and from the standard 5-
pin XLR style connector.
As the electrical specification currently only defines a purpose for a single wire pair, some equipment
manufacturers continue to use it. Such equipment is not compliant with the DMX standard, but may be
sufficiently compatible for operation using simple adapters.
Note: There is a risk of equipment damage if 3-pin XLR audio and DMX signals are plugged into each
other.
XLR-3 pinout
Data 1+ and - are often swapped over. The most commonly encountered pinout is given first:
1. Ground
2. Data 1- or 1+ (Primary Data Link)
3. Data 1+ or 1- (Primary Data Link)
Color Kinetics has their own version of the RJ-45 connector for DMX,[6] which predates the 2008 official
inclusion in the DMX512 standard. The pinout specifically for Color Kinetics LED lighting products is:
1. Data 1-
2. Data 1+
3. Shield
4. Optional
5. Optional
6. Optional
7. Optional
8. Optional
Cabling
The standard cables used in DMX512 networks employ XLR5 connectors,
with a male connector on one end and a female connector on the other end.
The cable's male connector attaches to the transmitting, female jack (OUT),
and its female connector attaches to the receiving, male jack (IN).
Cabling for DMX512 was removed from the ANSI E1.11 standard and a
separate cabling standards project was started in 2003.[7] Two cabling
standards have been developed, one for portable DMX512 cables (ANSI
E1.27-1 – 2006) and one for permanent installations (draft standard BSR
E1.27-2). This resolved issues arising from the differences in requirements
for cables used in touring shows versus those used for permanent
infrastructure.[8]
The electrical characteristics of DMX512 cable are specified in terms of Cable built to the DMX512A
impedance and capacitance, although there are often mechanical and other specification
considerations that must be considered as well. Cable types that are
appropriate for DMX512 usage will have a nominal characteristic
impedance of 120 ohms. Cat5 cable, commonly used for networking and telecommunications, has been
tested by ESTA for use with DMX512A. Also, cables designed for EIA485 typically meet the DMX512
electrical specifications. Conversely, microphone and line level audio cables lack the requisite electrical
characteristics and thus are not suitable for DMX512 cabling. The significantly lower impedance and higher
capacitance of these cables distort the DMX512 digital waveforms, which in turn can cause irregular
operation or intermittent errors that are difficult to identify and correct.[9]
Protocol
At the data link layer, a DMX512 controller transmits asynchronous
serial data at 250 kbit/s. The data format is fixed at one start bit,
eight data bits (least significant first[10]), two stop bits and no parity.
Break condition
Mark-After-Break
Slot 0, containing the one-byte Start Code DMX512 signal on an oscilloscope,
annotated to show measured timing
Up to 512 slots of channel data, each containing one
byte
The start of a packet is signified by a break followed by a "mark" (a logical one), known as the "Mark After
Break" (MAB). The break, which signals the end of one packet and the start of another, causes receivers to
start reception and also serves as a frame (position reference) for data bytes within the packet. Framed data
bytes are known as slots. Following the break, up to 513 slots are sent.
The first slot is reserved for a "Start Code" that specifies the type of data in the packet. A start code of 0x00
(hexadecimal zero) is the standard value used for all DMX512 compatible devices, which includes most
lighting fixtures and dimmers. Other start codes are used for Text packets (0x17), System Information
Packets (0xCF), for the RDM extension to DMX (0xCC), and various proprietary systems. ESTA
maintains a database of alternate start codes.[11]
All slots following the start code contain control settings for slave devices. A slot's position within the
packet determines the device and function to be controlled while its data value specifies the control set
point.
Timing
DMX512 timing parameters may vary over a wide range. The original authors specified the standard this
way to provide the greatest design flexibility. Because of this, however, it was difficult to design receivers
that operated over the entire timing range. As a result of this difficulty, the timing specification of the
original 1986 standard was changed in 1990. Specifically, the MAB, which was originally fixed at 4 μs,
was changed to 8 μs, minimum. The E1.11 (2004) standard relaxed the transmitter and receiver timing
specifications. This relaxed the timing requirements for systems using controllers built to DMX512-A
(E1.11); however, a significant number of legacy devices still employ transmit timing near the minimum end
of the range.
Transmitted 92 12
Receiver recognize 88 8
Maximum times are not specified because as long as a packet is sent at least once per second, the BREAK,
MAB, inter-slot time, and the mark between the last slot of the packet and the break (MBB) can be as long
as desired.
A maximum-sized packet, which has 512 channels (slots following the start code), takes approximately 23
ms to send, corresponding to a maximum refresh rate of about 44 Hz. For higher refresh rates, packets
having fewer than 512 channels can be sent.
The standard does not specify the minimum number of slots that can be sent in a packet. However, it does
require that packets be transmitted so that the leading edges of any two sequential BREAKs must be
separated by at least 1204 μs, and receivers must be able to handle packets with break-to-break times as
short as 1196 μs.[12] The minimum break-to-break transmit time can be achieved by sending packets that
contain at least 24 slots (by adding extra padding bytes, if necessary) or by stretching parameters such as the
BREAK, MAB, Interslot, or Interpacket times.[13]
Most data is sent with the default Null Start Code of 00h. Quoting from the standard:
A NULL START Code identifies subsequent data slots as a block of un-typed sequential 8-
bit information.
Packets identified by a NULL START Code are the default packets sent on DMX512
networks. Earlier versions of this standard assumed that only dimmer class data would be sent
using NULL START Code packets. In practice NULL START Code packets have been used
by a wide variety of devices; this version recognizes this fact.
Each NULL START Code packet contains no formal data or addressing structure. The
device using data from the packet must know the position of that data within the packet.
Dimmer packs or racks use a group of slots to determine the levels for their dimmers. Typically a dimmer
has a starting address that represents the lowest numbered dimmer in that pack, and the addressing increases
from there to the highest numbered dimmer. As an example, for two packs of six dimmers each, the first
pack would start at address 1 and the second pack at address 7. Each slot in the DMX512 packet
corresponds to one dimmer.
8-bit v. 16-bit
DMX does not mandate a method of 16-bit encoding for Null Start Code packets; however, many
parameters of moving lights make use of encoding larger than 8 bit numbers. To control these parameters
more accurately, some fixtures use two channels for parameters that require greater accuracy. The first of the
two channels controls the coarse (256 steps for the whole range of movement) and the second the fine (256
steps for each coarse step), this gives a 16-bit value range of 65536 steps, permitting much greater accuracy
for any 16-bit controlled parameter such as Pan or Tilt.
DMX in practice
DMX512's popularity is partly due to its robustness. The cable can be abused without any loss of function
in ways that would render Ethernet or other high speed data cables useless, although cable faults can
occasionally lead to intermittent problems such as random triggering. Unexpected fixture behavior is caused
by addressing errors, cable faults, incorrect data from the controller, or multiple DMX sources inadvertently
applied to a single chain of fixtures.
In the 1986 and 1990 standards the use of the second data pair is not
defined other than as an ‘optional second data link’. Both unidirectional and
bidirectional use were envisioned. Other proprietary uses have been
implemented for these pins. Schemes that use voltage outside of the range
allowed by EIA485 are disallowed. Guidance on allowed usage can be
found in Annex B of E1.11. Current standard practice is to leave the
secondary data link pins unused.
Connectors
DMX512-A uses a single pair of conductors, so can be connected using the The Singapore Flyer uses
cheaper 3-pin XLR connectors. Some manufacturers made units with three- wireless DMX to control the
pin XLR connectors, because of their lower cost. However, as 3-pin XLRs lighting on the pods and
are commonly used for connecting microphones and sound mixing rim.[14]
consoles, there is a risk of wrongly connecting DMX512 equipment to
microphones and other sound equipment. The +48 volt phantom power
emitted by mixing consoles could damage DMX512 equipment if connected to it. The DMX512 signals
emitted by lighting desks can damage microphones and other sound equipment if connected to it. As a
result, the best practice is to use only 5-pin XLRs for DMX512 signals, to avoid risk of confusion with
connectors used for sound signals.
Termination
The DMX512 signal lines require a single 120 Ohm termination resistor to be fitted at the extreme end of
the signal cable.
Some of the more common symptoms of improper termination are flashing, uncontrollable or incorrect light
operation, or other undesired random special effects.
Some equipment has automatic termination, others a physical switch, while the remainder requires a
physical terminator (e.g. male XLR-5 plug fitted with a resistor) to be installed by the user.
It is important for users to check whether their devices have automatic or switched termination, as otherwise
they may end up with the DMX line being terminated multiple times or not at all when they believed it to be
correct.
Additionally, terminating the DMX line often exposes physical cable faults - for example, if the "Data −"
wire is broken, an unterminated DMX run may partially work, while fitting the terminator immediately
exposes the problem.
Wireless operation
Recently, wireless DMX512 adapters have become popular, especially in architectural lighting installations
where cable lengths can be prohibitively long. Such networks typically employ a wireless transmitter at the
controller, with strategically placed receivers near the fixtures to convert the wireless signal back to
conventional DMX512 wired network signals or wireless receivers built into the individual fixtures.
Although wireless DMX512 networks can function over distances exceeding 3,000 feet (910 m) under
ideal conditions, most wireless DMX512 links are limited to a maximum distance of 1,000–1,500 feet
(300–460 m) to ensure reliable operation. The first commercially marketed wireless DMX512 system was
based on frequency-hopping spread spectrum (FHSS) technology using commercial wireless modems.[15]
Other later-generation systems still used frequency-hopping spread spectrum (FHSS) technology, but at
higher bandwidth. FHSS systems tend to disturb other types of wireless communication systems such as
WiFi/WLAN. This has been solved in newer wireless DMX systems by using adaptive frequency hopping,
a technique to detect and avoid surrounding wireless systems, to avoid transmitting on occupied
frequencies.[16]
Multiple incompatible wireless protocols currently exist. While DMX-over-Ethernet protocols such as
E1.31 - Streaming ACN can be used to send DMX data over WiFi, this is not generally recommended due
to the highly variable latency of WiFi.
Development
Many alternatives to DMX512 have been proposed to address limitations such as the maximum slot count
of 512 per universe, the unidirectional signal, and the lack of inherent error detection. The 2004 DMX512-
A revision added a System Information Packet (SIP). This packet can be interleaved with Null packets. One
feature of SIPs is they allow checksums to be sent for DMX Null data. However, SIPs have rarely been
implemented.
E1.11-2004, a revision of DMX512-A, also lays the foundation for Remote Device Management (RDM)
protocol through the definition of Enhanced Functionality. RDM allows for diagnostic feedback from
fixtures to the controller by extending the DMX512 standard to encompass bidirectional communication
between the lighting controller and lighting fixtures. RDM was approved by ANSI in 2006 as ANSI E1.20
and is gaining interest.
An Ethernet-based protocol can distribute multiple DMX universes through a single cable from a control
location to breakout boxes closer to fixtures. These boxes then output the conventional DMX512 signal.
ANSI E1.31—2009[8] Entertainment Technology—Lightweight streaming protocol for transport of
DMX512 using ACN, published May 4, 2009, and Art-Net are two free-to-use protocols used to achieve
this.
See also
Architecture for Control Networks (ANSI E1.31/sACN/Streaming ACN)
Art-Net
Lighting control console
Lighting control system
RDM (Remote Device Management)
References
1. United States Institute for Theatre Technology -- Resources > Standards > DMX512 >
DMX512 FAQ -- http://www.usitt.org/Resources/Standards2/DMX512/DMX512FAQ#a12
Archived (https://web.archive.org/web/20111020092102/http://www.usitt.org/Resources/Stan
dards2/DMX512/DMX512FAQ) 2011-10-20 at the Wayback Machine -- ...DMX512 is not an
appropriate control protocol for hazardous applications...
2. "ESTA Technical Standards Program, published documents" (https://tsp.esta.org/tsp/docume
nts/published_docs.php). tsp.esta.org. Retrieved 18 January 2024.
3. "United States Institute for Theatre Technology DMX512 FAQ" (https://archive.today/201304
16024656/http://www.usitt.org/content.asp?contentid=373). usitt.org. Archived from the
original (http://www.usitt.org/content.asp?contentid=373) on 16 April 2013. Retrieved
19 March 2018.
4. Bennette, Adam (2006). Recommended Practice for DMX512. PLASA. ISBN 978-0-
9557035-2-2.
5. "Introduction and Terminology" (https://art-net.org.uk/structure/the-technology/). Art-Net.
Retrieved 2020-04-12.
6. "Archived copy" (http://www.dl.colorkinetics.com/files/web/support/pro/wiring/RJ45_TO_RJ4
5.pdf) (PDF). Archived (https://web.archive.org/web/20160417220016/http://www.dl.colorkine
tics.com/files/web/support/pro/wiring/RJ45_TO_RJ45.pdf) (PDF) from the original on 2016-
04-17. Retrieved 2016-06-28.
7. "Archived copy" (https://web.archive.org/web/20120330153032/http://tsp.plasa.org/tsp/worki
ng_groups/CP/docs/CPmin07-2003w.pdf) (PDF). Archived from the original (http://tsp.plasa.
org/tsp/working_groups/CP/docs/CPmin07-2003w.pdf) (PDF) on 2012-03-30. Retrieved
2011-08-11.
8. "PLASA Technical Standards Program" (https://web.archive.org/web/20160101165635/http://
tsp.plasa.org/tsp/documents/published_docs.php). plasa.org. Archived from the original (htt
p://tsp.plasa.org/tsp/documents/published_docs.php) on 1 January 2016. Retrieved
19 March 2018.
9. Cadena, Richard (2009-10-31). "Troubleshooting DMX 512" (http://stage-directions.com/curr
ent-issue/55-light-on-the-subject/1949-troubleshooting-dmx-512.html%5C). Stage
Directions. Archived (https://web.archive.org/web/20190524190630/http://stage-directions.co
m/current-issue/55-light-on-the-subject/1949-troubleshooting-dmx-512.html) from the original
on 2019-05-24. Retrieved 2019-05-24.
10. Luna, Oscar; Torres, Daniel (2002–2009). DMX512 Protocol Implementation Using
MC9S08GT60 8-Bit MCU (Application Note 3315) (https://www.nxp.com/docs/en/application
-note/AN3315.pdf) (PDF). Freescale Semiconductor. Archived (https://web.archive.org/web/2
0170830235842/http://cache.freescale.com/files/microcontrollers/doc/app_note/AN3315.pdf)
(PDF) from the original on 2017-08-30.
11. "TSP - Working Groups - About, Camera Cranes, Control Protocols, Electrical Power, Event
Safety, Floors, Fog & Smoke, Followspot Position, Photometrics, Rigging, Stage Lifts" (http://
tsp.esta.org/tsp/working_groups/CP/DMXAlternateCodes.php). tsp.esta.org. Archived (http
s://web.archive.org/web/20170528115853/http://tsp.esta.org/tsp/working_groups/CP/DMXAlt
ernateCodes.php) from the original on 28 May 2017. Retrieved 19 March 2018.
12. ESTA (2004). American National Standard E1.11 – 2004 (https://tsp.esta.org/tsp/documents/
docs/E1-11.pdf) (PDF). Entertainment Services and Technology Association. p. 19.
13. "Ujjal's DMX512 Pages....The DMX512 Packet" (https://web.archive.org/web/201709231818
53/http://www.dmx512-online.com/packt.html). www.dmx512-online.com. Archived from the
original (http://www.dmx512-online.com/packt.html) on 2017-09-23. Retrieved 19 March
2018.
14. Evans, Jim (2008-09-23). "W-DMX on the Singapore Flyer" (https://www.lsionline.com/news/
w-dmx-on-the-singapore-flyer--pm2a8k). LSi Online. Archived (https://web.archive.org/web/2
0190524154438/https://www.lsionline.com/news/w-dmx-on-the-singapore-flyer--pm2a8k)
from the original on 2019-05-24. Retrieved 2019-05-24.
15. "DMX512 WITH OUT WIRES!" (http://www.goddarddesign.com/wspread.html).
www.goddarddesign.com. Archived (https://web.archive.org/web/20170406025044/http://ww
w.goddarddesign.com/wspread.html) from the original on 6 April 2017. Retrieved 19 March
2018.
16. "FAQ - LumenRadio" (https://www.lumenradio.com/faq/). lumenradio.com. Archived (https://w
eb.archive.org/web/20170108031257/https://www.lumenradio.com/faq/) from the original on
8 January 2017. Retrieved 19 March 2018.
External links
Technical Standards Program (https://tsp.esta.org/tsp/) from ESTA
USITT (http://www.usitt.org/)
OpenDMX.net (http://opendmx.net/)
Open Lighting Project (http://www.openlighting.org/)