Free forever·no account, no tracking, no third-party requests ·open data, free API
showstack / protocols / rdmnet

RDMnet

Also called E1.33, RDM over IP.

Carries RDM messages over IP, with brokers routing between controllers and devices instead of every controller polling every wire. It also defines LLRP, a multicast side channel for finding and fixing devices whose IP settings are wrong.

Device managementOpenESTAReported

Stewarded by ESTA (Entertainment Services and Technology Association).

Management Housekeeping, no deadline

Discovery, monitoring, configuration, backups, updates. Useful, and none of it has a deadline of its own.

What kills it. Nothing kills it. That is the problem: with no deadline it has no manners, and it will happily starve everything that does have one. Putting it on a show VLAN is the commonest self-inflicted wound in the industry.

Why this one, and not what the category suggests. The same job over IP, and the same reasoning.

Ports

udp/5569 LLRP discovery and configuration (multicast)
IANA registers 5569/udp as rdmnet-device and 5569/tcp as rdmnet-ctrl to PLASA for E1.33. Broker connections do not use a fixed port; brokers advertise their listening port over DNS-SD.

Multicast

What goes wrong

Nothing works without a broker. With no broker running in the scope, controllers and devices sit there discovered and unable to exchange a single message. Some products embed a broker, most do not.
Discovery is DNS-SD, normally over mDNS, which does not cross a subnet boundary without a reflector or a unicast DNS-SD server. That is the usual reason a device on another VLAN never appears in the list.
Scope is a text string and it defaults to "default". A device left on the wrong scope is invisible to the controller even though it is on the right network and answers a ping.
LLRP is the recovery path, not the working path. It is multicast and deliberately limited in what it can do, so never design a routine control workflow around it.
Dynamic UIDs are allocated by the broker in the 8000h-FFFFh manufacturer ID range and are not stable across sessions. Never key a patch, a preset or a show file off one.
A gateway presents its downstream DMX responders as endpoints, but the wire behind it is still RS-485 RDM. A slow or marginal DMX leg gates the whole conversation regardless of how fast the network is.
TCP connections to the broker are health-checked with heartbeats. A network that drops idle flows, or a firewall with a short state timeout, will make devices appear and disappear on a cycle.

What speaks RDMnet (1)

ProductDirectionNotes
Wireshark
Wireshark Foundation
in RDMnet dissector added in Wireshark 3.4.0 (commit 'Added RDMnet protocol', March 2020).

Open source implementations

Typical use

Sources

Understand the mechanism
Something wrong, or missing?

Every entry here is maintained by people who run shows.

Edit this entry on GitHub — one file, editable in your browser, and your handle goes on it permanently.

Work at ESTA (Entertainment Services and Technology Association)? Confirm or correct this entry — it is free, it stays free, and nothing about it is for sale.