Errors and Sub Device All Call - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · July 18th, 2013

My interpretation has been that SUB_DEVICE_ALL_CALL should only effect Sub-Devices and not change the root at all.

In the case where someone sends a broadcast request to SUB_DEVICE_ALL_CALL, only responders that have sub-devices should act on the request.

How the respond gets a bit dicey when you have a mixed collection of sub-devices. Lets say you send a SET DMX_START_ADDRESS to a responder that has 2 sub-devices, but only one of the sub-devices supports the DMX_START_ADDRESS PID. Both "NACK Unknown PID" and "ACK" would be appropriate.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
errors when testing discovery	redwind	RDM General Implementation Discussion	1	July 20th, 2011 12:05 PM
Call for RDM Gear for display at LDI Connectivity Booth and Sessions	sblair	RDM General Implementation Discussion	0	August 31st, 2010 03:05 PM

July 18th, 2013	#2
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	My interpretation has been that SUB_DEVICE_ALL_CALL should only effect Sub-Devices and not change the root at all. In the case where someone sends a broadcast request to SUB_DEVICE_ALL_CALL, only responders that have sub-devices should act on the request. How the respond gets a bit dicey when you have a mixed collection of sub-devices. Lets say you send a SET DMX_START_ADDRESS to a responder that has 2 sub-devices, but only one of the sub-devices supports the DMX_START_ADDRESS PID. Both "NACK Unknown PID" and "ACK" would be appropriate.