When to use Queued Msg VS Status Msg

[sblair]

Mark,

Simply put there are two different lists of messages. The queued message list is for the device to report back a setting change of a PID. For example, if someone changes a setting such as DMX Address from the device's menu then it can use a queued message to report back to the controller the change in DMX Address.

Status Messages are for reporting back warnings or errors such as over temp information, a lamp reaching the end of it's life, or a failure of some kind.

The controller has the ability to retrieve Status Messages using the GET: QUEUED_MESSAGES from the device by indicating what level of status type it wants back (ERROR, WARNING, INFO, etc). The status message is only returned in this case if there are no queued messages to be reported.

If a controller ONLY wants to get status messages and not other queued message PID's then it can use the GET: STATUS_MESSAGES to retrieve them.

QUEUED_MESSAGES is not required to be implemented in a device (although VERY useful and encouraged). When it is not implemented, then GET: STATUS_MESSAGES is the only way for the device to report the information.

Hope that sheds some light.

Where are you located at? We have another RDM Plugfest happening Dallas in about 2 weeks and it would be a good chance for you to test with a wide range of devices and get all your questions answered by members of the Task Group in person.