RDM discover driving against dmx input (wrong cabling) - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · January 26th, 2011

There are several RDM hubs that do jabber detection. This would solve the problem that you are describing. It works by looking for activity on the line during the 176us turnaround period.

After an RDM request (DUB or Normal request), there is a 176 microsecond period before the response can start. If there is any activity on the line during that time there may be a jabbering device.

In the case of a hub, it can cut off the port that has the jabbering device for a few seconds. On a console, you could warn the user.

January 26th, 2011	#5
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	There are several RDM hubs that do jabber detection. This would solve the problem that you are describing. It works by looking for activity on the line during the 176us turnaround period. After an RDM request (DUB or Normal request), there is a 176 microsecond period before the response can start. If there is any activity on the line during that time there may be a jabbering device. In the case of a hub, it can cut off the port that has the jabbering device for a few seconds. On a console, you could warn the user.