Support a given PID with a GET but not a SET - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · February 26th, 2014

Scott is correct, you can return NR_UNSUPPORTED_CC if you support GET but not SET.

However, in the specific example you give, it's really not a good idea. If you only have a single identify mode, there's no reason to declare support for the IDENTIFY_MODE PID. Just leave it out of your responder altogether.

This question come up more often in the context of PIDs such as DEVICE_HOURS where the GET gives you information about the responder, but there are reasons you want to prevent the user from sending a SET.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ACT_TIMER to Set messages	nic123	RDM Interpretation Questions	3	April 18th, 2014 12:01 PM
DMX_BLOCK_ADDRESS (Set)	hamish	RDM Interpretation Questions	7	June 26th, 2013 02:53 AM
Sub-device response to SET/GET DMX512 start address	p_richart	RDM Interpretation Questions	2	September 29th, 2006 09:27 AM

February 26th, 2014	#3
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Scott is correct, you can return NR_UNSUPPORTED_CC if you support GET but not SET. However, in the specific example you give, it's really not a good idea. If you only have a single identify mode, there's no reason to declare support for the IDENTIFY_MODE PID. Just leave it out of your responder altogether. This question come up more often in the context of PIDs such as DEVICE_HOURS where the GET gives you information about the responder, but there are reasons you want to prevent the user from sending a SET.