Skip to content

RDM Proxy

What “RDM Proxy” Means

An external RDM controller can send RDM to a DMX input port on an ELC Node8GBx. The NodeGBx system will then communicate with RDM devices on multiple DMX outputs on multiple nodes.

Why this is useful

It allows you to connect an external RDM control system (example given: ROBE RoboSpot) to one DMX input, and then reach RDM-controlled devices that are physically connected to different node outputs, without running lots of extra DMX cables.

Supported Hardware & Firmware Requirements

To use this RDM Proxy functionality, firmware requirements depend on the product:

  • Node8GBx: firmware 1.28 or higher — DMX in and out
  • SwitchGBx and slave: firmware 1.28 or higher — DMX out only
  • ShowstoreGBx: firmware 1.15 or higher — DMX out only
  • Node 8S/Gb, Node 6x, Node 3, Buddy: firmware 2.50 or higher — DMX out only

Practical takeaway: The DMX input that receives RDM must be on a Node8GBx (because it is listed as DMX in/out). The other listed devices participate as output-only ports.

Functional Limits (Sizing Rules)

One Node8GBx input port can proxy:

  • A maximum of 8 output ports (across any number of nodes)
  • A maximum of 16 RDM devices controlled by proxy on one DMX input

Design implications

  • If you have more than 8 output ports that need RDM proxying, split across additional proxy inputs (e.g., another Node8GBx input port / node).
  • If you have more than 16 RDM devices to control, also split across additional proxy inputs.

Core Setup Principle

Universe matching (Primary universe)

A DMX input will automatically detect up to 8 DMX ports on the network with the same Primary universe.

What this means in practice - Your proxy “domain” is defined by the Primary universe setting. - Put the ports you want to be proxied into the same Primary universe as the Node8GBx input.

Discovery trigger (how proxying starts)

RDM discovery on the input—started by an external RDM controller—automatically triggers RDM discovery on the output ports.

After discovery, the system proxies all communication between:

  • the external RDM controller, and
  • the discovered devices (on the selected output ports).

Step-by-Step: Typical Deployment Workflow

Step 1 — Verify firmware and roles

  1. Ensure the Node8GBx that will receive the external controller is on firmware ≥ 1.28 and is used for DMX input.
  2. Ensure all participating output devices meet their minimum firmware (SwitchGBx, ShowstoreGBx, Node 8S/Gb, Node6x, Node3, Buddy).

Step 2 — Plan your proxy “domain”

  1. Choose which up to 8 output ports will be included.
  2. Confirm the total number of RDM fixtures in that group is ≤ 16.

Step 3 — Align Primary universe

Configure the Node8GBx input and the target output ports so they share the same Primary universe.

Step 4 — Connect the external RDM controller

Connect the external controller to the DMX input on the Node8GBx.

Step 5 — Start RDM discovery from the controller

Initiate RDM discovery on your external RDM controller. This will:

  • discover on the input, and
  • automatically trigger discovery on the output ports,
  • then begin proxying traffic.

Diagnostics & Maintenance

Each DMX input port has RDM diagnostics and control available in the RDM menu.

The RDM menu:

  • shows an overview of connected ports and discovered devices, and
  • lets the user force a full discovery on all or one of the connected output ports.
  • If devices are missing or changed, run a full discovery from the RDM menu (all ports), or target only the affected port.

Example Use Case (from the application note)

You can connect a system like ROBE RoboSpot to a DMX input, linking controlled spots/cameras across multiple different node outputs, without needing lots of extra DMX cabling.

Quick Reference (Cheat Sheet)

Requirements

  • Proxy input must be on Node8GBx (firmware ≥ 1.28)
  • Output-capable devices must meet their minimum firmware levels

Limits per Node8GBx input port

  • ≤ 8 output ports
  • ≤ 16 RDM devices

Setup rule

  • Output ports must share the same Primary universe as the input

How it starts

  • External controller starts discovery on the input → output discovery runs automatically → proxy traffic flows

Diagnostics

  • Use the RDM menu for overview + force discovery per port or all ports