Sensor Defintion/Support Parameters - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · February 14th, 2014

The STATUS_MESSAGES data format described in E1.20-2010 section 10.3.2 is enclosed in the general packet format described in section 6.2. That enclosing packet has the responder's UID included.

Status messages (and queued messages) are more of an advanced feature for RDM. They are not required for basic operation. In fact, many simple responders don't implement status messages at all. Rather than focusing on Status Messages right away, you may want to get the rest of your responder working, then go back and add status message support once you have that foundation to build on.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
QUEUED_MESSAGE - must controllers support this?	berntd	RDM General Implementation Discussion	4	December 11th, 2024 08:53 AM
Sensor type and Sensor unit for No of Phases question	berntd	RDM General Implementation Discussion	1	October 1st, 2009 10:04 PM
Sensor type and Sensor unit for DMX rate question	berntd	RDM General Implementation Discussion	3	October 1st, 2009 12:41 AM
DMX/RDM support in new SBC	tracyu	RDM Marketplace Discussion	0	June 2nd, 2008 05:57 PM

February 14th, 2014	#16
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	The STATUS_MESSAGES data format described in E1.20-2010 section 10.3.2 is enclosed in the general packet format described in section 6.2. That enclosing packet has the responder's UID included. Status messages (and queued messages) are more of an advanced feature for RDM. They are not required for basic operation. In fact, many simple responders don't implement status messages at all. Rather than focusing on Status Messages right away, you may want to get the rest of your responder working, then go back and add status message support once you have that foundation to build on.