Changing DMX512 footprint - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · January 7th, 2025

Is this a multi-port "patching" splitter that allows each downstream port to have a different block of Null Startcode slots sent to it? For example, port 1 could be configured to take 100 slots of data starting from input slot 251, and it will retransmit it starting at slot 1?

The standard PIDs generally assume that universes are an inseparable block of data, so there aren't PIDs defined to slice universes in to multiple segments. RDMnet and E1.37 have the concept of a "Composite Universe", but managing composite universes is outside the scope of the standard.

It may be best to implement this with Manufacturer-specific PIDs.

I assume there will be other devices attached to the downstream ports? Will those devices only use NSC DMX, or will they also support RDM?

I would not recommend using Start Address for this, because some controllers will not allow you to patch fixtures on top of each other.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to handle DMX Footprint overrun	RobbG	RDM General Implementation Discussion	3	May 8th, 2017 08:42 AM
RDM and DMX512 will soon be retired!	Milton Davis	RDM General Implementation Discussion	1	June 10th, 2013 07:56 PM
DMX Addressing when Footprint is Zero	Mark_C	RDM General Implementation Discussion	8	January 17th, 2010 10:47 AM
Welcome to the DMX512 Discussion Forum	sblair	DMX512 Discussion	0	May 31st, 2006 11:10 PM

January 7th, 2025	#4
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Is this a multi-port "patching" splitter that allows each downstream port to have a different block of Null Startcode slots sent to it? For example, port 1 could be configured to take 100 slots of data starting from input slot 251, and it will retransmit it starting at slot 1? The standard PIDs generally assume that universes are an inseparable block of data, so there aren't PIDs defined to slice universes in to multiple segments. RDMnet and E1.37 have the concept of a "Composite Universe", but managing composite universes is outside the scope of the standard. It may be best to implement this with Manufacturer-specific PIDs. I assume there will be other devices attached to the downstream ports? Will those devices only use NSC DMX, or will they also support RDM? I would not recommend using Start Address for this, because some controllers will not allow you to patch fixtures on top of each other.