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

este_ · March 2nd, 2014

One of the the most obvious occurrences of this situation seems be the LOCK_PIN command. In this case, however, the standard (E1-37) makes it clear and says, "For devices that protect against the RDM Controller retrieving the current PIN code, any GET_COMMAND messages shall send a NACK with a NACK Reason of NR_UNSUPPORTED_COMMAND_CLASS".

The same should apply for all the examples above.

Note: Even if you do not support GET_LOCK_PIN, the OLA responders tests try a "GetLockPinWithData" and claim a

"Response: RDMResponse:, Get NACK Unsupported command class, PID: 0x0640"
as
"Failed: expected one of:
CC: Get, PID 0x0640, NACK Format Error
CC: Get, PID 0x0640, ACK, fieds [], values {}"

This may be misleading. You simply cannot generate any answer when you don't support that PID or command class.
It reminds me of the question:
"Which part of 'NO' don't you understand?"

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Switch to Hybrid Mode Threaded Mode

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

March 2nd, 2014	#4
este_ Junior Member Join Date: Jan 2010 Location: Germany Posts: 24	One of the the most obvious occurrences of this situation seems be the LOCK_PIN command. In this case, however, the standard (E1-37) makes it clear and says, "For devices that protect against the RDM Controller retrieving the current PIN code, any GET_COMMAND messages shall send a NACK with a NACK Reason of NR_UNSUPPORTED_COMMAND_CLASS". The same should apply for all the examples above. Note: Even if you do not support GET_LOCK_PIN, the OLA responders tests try a "GetLockPinWithData" and claim a "Response: RDMResponse:, Get NACK Unsupported command class, PID: 0x0640" as "Failed: expected one of: CC: Get, PID 0x0640, NACK Format Error CC: Get, PID 0x0640, ACK, fieds [], values {}" This may be misleading. You simply cannot generate any answer when you don't support that PID or command class. It reminds me of the question: "Which part of 'NO' don't you understand?"