SET_COMMAND_RESPONSE TIMER_ACK - E1.20 RDM (Remote Device Management) Protocol Forums

majid · November 2nd, 2018

I progressed to "Fail = 0" and "Warning = 0" on OLA Responder Tester

my device supports GET_DEVICE_HOURS, but not SET_DEVICE_HOURS

at first I ignored SET_DEVICE_HOURS command,
and OLA warned me to response with NR_WRITE_PROTECTED or NR_UNSUPPORTED_COMMAND_CLASS

also table A-17 says : "NR_UNSUPPORTED_COMMAND_CLASS may be used where GET allowed and SET not supported"

when I NR_UNSUPPORTED_COMMAND_CLASS , OLA advisory says: "returned unsupported command classs"

when I NR_WRITE_PROTECTED , OLA advisory says: "was write protected, try changing the lock mode if enabled"

my question is how can I pass this advisory messages ?

November 2nd, 2018	#17
majid Member Join Date: Oct 2017 Location: Turkiye Posts: 38	I progressed to "Fail = 0" and "Warning = 0" on OLA Responder Tester my device supports GET_DEVICE_HOURS, but not SET_DEVICE_HOURS at first I ignored SET_DEVICE_HOURS command, and OLA warned me to response with NR_WRITE_PROTECTED or NR_UNSUPPORTED_COMMAND_CLASS also table A-17 says : "NR_UNSUPPORTED_COMMAND_CLASS may be used where GET allowed and SET not supported" when I NR_UNSUPPORTED_COMMAND_CLASS , OLA advisory says: "returned unsupported command classs" when I NR_WRITE_PROTECTED , OLA advisory says: "was write protected, try changing the lock mode if enabled" my question is how can I pass this advisory messages ?