Refreshing of paramters need Queued Messages? - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · May 25th, 2010

> In the case with DMX_START_ADDRESS it wont
> make any difference for the controller, hence you
> could go with either SET_RESPONSE or
> GET_RESPONSE.

I'd argue that it does make a difference. If you queue up a SET_RESPONSE DMX_START_ADDRESS when the DMX address is changed, then the controller only knows that the DMX address was set. It then has to issue a GET DMX_START_ADDRESS or GET_DEVICE_INFO to find out what the new address is.

If you queue a GET_RESPONSE DMX_START_ADDRESS, the queued message contains the new address and the controller does not need to do any followup work to find out what the new address is.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ACK_TIMER, QUEUED Messages	berntd	RDM Interpretation Questions	1	November 12th, 2008 10:02 PM
get queued messages as a ping?	sondericker	RDM Interpretation Questions	2	January 20th, 2007 09:11 PM

May 25th, 2010	#30
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	> In the case with DMX_START_ADDRESS it wont > make any difference for the controller, hence you > could go with either SET_RESPONSE or > GET_RESPONSE. I'd argue that it does make a difference. If you queue up a SET_RESPONSE DMX_START_ADDRESS when the DMX address is changed, then the controller only knows that the DMX address was set. It then has to issue a GET DMX_START_ADDRESS or GET_DEVICE_INFO to find out what the new address is. If you queue a GET_RESPONSE DMX_START_ADDRESS, the queued message contains the new address and the controller does not need to do any followup work to find out what the new address is.