View Single Post
Old March 2nd, 2014   #4
este_
Junior Member
 
Join Date: Jan 2010
Location: Germany
Posts: 24
Default

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?"
este_ is offline   Reply With Quote