Thread: STATUS_MESSAGES
View Single Post
Old October 19th, 2009   #3
ericthegeek
Task Group Member
 
Join Date: Aug 2008
Posts: 375
Default

> Should I implement this pid?

It's a nice way to deliver messages from the responder without the controller having to know what to ask for.

> I do not support queueed messages

Status messages do no require you to support queued messages.

>Would I have to support everything in table A-4
> or can I just do error messages somehow?

You don't have to support all of the status types. If you only want to support errors, then you simply send the error message for Error, Warning, and Advisory.

> What about STATUS_GET_LAST_MESSAGE ?
> Do I have to support it?

Effectively yes, you have to support it. If you don't support GET_LAST_MESSAGE, there's no way for the controller to re-get a status message packet that gets lost or corrupted. If you don't have GET_LAST_MESSAGE, and your "Dimmer on Fire" status message gets dropped, the error will be lost forever.
ericthegeek is offline   Reply With Quote