Correctly handling ACK_OVERFLOW - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · September 6th, 2010

Thinking about this a bit more, it's not clear if STATUS_MESSAGES should ever use ACK_OVERFLOW in the first place. Multiple status responses are packed into a single packet. But, STATUS_MESSAGES has its own queuing mechanism, so if you have more status conditions to report than will fit into a single response, you can use that queuing mechanism to get the additional statuses.

Again, a controller should probably handle both, but I'd argue a responder shouldn't generate ACK_OVERFLOWs for STATUS_MESSAGES responses.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ACK_TIMER Handling	ericthegeek	RDM General Implementation Discussion	8	January 20th, 2011 08:15 PM
Command Class / Parameter ID mismatch handling	dangeross	RDM Interpretation Questions	2	April 16th, 2009 01:39 PM

September 6th, 2010	#7
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Thinking about this a bit more, it's not clear if STATUS_MESSAGES should ever use ACK_OVERFLOW in the first place. Multiple status responses are packed into a single packet. But, STATUS_MESSAGES has its own queuing mechanism, so if you have more status conditions to report than will fit into a single response, you can use that queuing mechanism to get the additional statuses. Again, a controller should probably handle both, but I'd argue a responder shouldn't generate ACK_OVERFLOWs for STATUS_MESSAGES responses.