Sub Device required PIDs - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · May 1st, 2012

Scott, you and I are talking about something different.

On the root device, the standard says that the list of PIDs returned by GET SUPPORTED_PARAMETERS does not include the mandatory PIDs. For example, the list returned by the root device should not include SOFTWARE_VERSION_LABEL since SOFTWARE_VERSION_LABEL is required. This, a controller would normally not expect to see SOFTWARE_VERSION_LABEL in the list of supported parameters.

But, the same rule does not apply to sub-devices. When you send a GET SUPPORTED_PARAMETERS to a sub-device, the list of PIDs should include SOFTWARE_VERSION_LABEL. Thus, when getting the PID list from a sub-device, a controller can expect to see PIDs included in the list that would never be returned by a properly implemented root device.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Required handling of sequences of RDM broadcast cmds	eldoMS	RDM Timing Discussion	9	August 23rd, 2011 09:40 AM
Is there a minimum required PID list for sub-devices?	p_richart	RDM Interpretation Questions	4	November 7th, 2008 01:04 PM

May 1st, 2012	#11
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Scott, you and I are talking about something different. On the root device, the standard says that the list of PIDs returned by GET SUPPORTED_PARAMETERS does not include the mandatory PIDs. For example, the list returned by the root device should not include SOFTWARE_VERSION_LABEL since SOFTWARE_VERSION_LABEL is required. This, a controller would normally not expect to see SOFTWARE_VERSION_LABEL in the list of supported parameters. But, the same rule does not apply to sub-devices. When you send a GET SUPPORTED_PARAMETERS to a sub-device, the list of PIDs should include SOFTWARE_VERSION_LABEL. Thus, when getting the PID list from a sub-device, a controller can expect to see PIDs included in the list that would never be returned by a properly implemented root device.