GET_STATUS_MESSAGES for fault reporting - E1.20 RDM (Remote Device Management) Protocol Forums

dj41354 · December 18th, 2015

from ANSI E1.20-2010 Section 6 Message Structure:
sub-section 6.2.8 Message Count:
"The message count field is used by a responder to indicate that additional data is now available for collection by a controller. This data (which might be unrelated to the current message transaction) should be collected by the controller using the GET:QUEUED_MESSAGE command."

This paragraph certainly makes it sound like the Message Count field is used by QUEUED_MESSAGE, not STATUS_MESSAGES... so I guess I'm still unclear on this..

Questions:
1) Is it ok to implement STATUS_MESSAGES and not implement QUEUED_MESSAGE?
(you said in your 4th response to me above: "You have to include Queued Messages, whether you include status messages in the count is up to you."
2) If Message Count is not used with my implementation of STATUS_MESSAGES, how does the controller know to ask for device status?.. does the controller just do this occasionally on it's own?

Thanks for you help with this..

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
RDM and simple status reporting	Jim Acker	RDM General Implementation Discussion	2	February 23rd, 2012 01:24 PM
Simple dimmer error reporting	Milton Davis	RDM General Implementation Discussion	3	November 7th, 2008 11:15 AM
COMMS_STATUS Error reporting	prwatE120	RDM Interpretation Questions	0	January 20th, 2007 07:07 AM

December 18th, 2015	#3
dj41354 Member Join Date: Nov 2015 Posts: 33	from ANSI E1.20-2010 Section 6 Message Structure: sub-section 6.2.8 Message Count: "The message count field is used by a responder to indicate that additional data is now available for collection by a controller. This data (which might be unrelated to the current message transaction) should be collected by the controller using the GET:QUEUED_MESSAGE command." This paragraph certainly makes it sound like the Message Count field is used by QUEUED_MESSAGE, not STATUS_MESSAGES... so I guess I'm still unclear on this.. Questions: 1) Is it ok to implement STATUS_MESSAGES and not implement QUEUED_MESSAGE? (you said in your 4th response to me above: "You have to include Queued Messages, whether you include status messages in the count is up to you." 2) If Message Count is not used with my implementation of STATUS_MESSAGES, how does the controller know to ask for device status?.. does the controller just do this occasionally on it's own? Thanks for you help with this..