STATUS_NONE response - E1.20 RDM (Remote Device Management) Protocol Forums

kenypp · January 3rd, 2014

Thanks for explaining table 10-1, that was very helpful.
I had a few quick questions regarding my implementation that I'll add here rather than starting a new thread.
1. Is there a public status warning for "replace bulb"? I didn't see one in the appendix.
2. When responding to get device info, is this still RDM version 1.0? I saw it mentioned in the document even though the document is labeled 1.20.
3. When responding to an unsupported parameter request I am using nack reason unknown. When responding to a set when only get is supported I am using nack reason unsupported parameter. This is how I read it in table A-17. Is this correct?

January 3rd, 2014	#5
kenypp Junior Member Join Date: Jan 2014 Posts: 9	Thanks for explaining table 10-1, that was very helpful. I had a few quick questions regarding my implementation that I'll add here rather than starting a new thread. 1. Is there a public status warning for "replace bulb"? I didn't see one in the appendix. 2. When responding to get device info, is this still RDM version 1.0? I saw it mentioned in the document even though the document is labeled 1.20. 3. When responding to an unsupported parameter request I am using nack reason unknown. When responding to a set when only get is supported I am using nack reason unsupported parameter. This is how I read it in table A-17. Is this correct?