STATUS_MESSAGES

[sblair]

Bernt,

I would strongly suggest implementing Queued_Messages. It really is one of the most useful messages there is as most of the controllers do a good job at supporting it I've found.

You can choose to only report Error conditions and not Warning type conditions if you choose. The standard does require the STATUS_GET_LAST_MESSAGE though to handle a case where the packet doesn't get through successfully:

The responder shall maintain reported status information until it has been successfully delivered to the controller. Status is considered successfully delivered when the responder receives a Status Type Requested other than STATUS_GET_LAST_MESSAGE.

[berntd]

Originally Posted by sblair

Bernt,

I would strongly suggest implementing Queued_Messages. It really is one of the most useful messages there is as most of the controllers do a good job at supporting it I've found.

Hello
In relation to queued messages...

Is it implied that a controller will leave the device alone if it receives and ACK_TIMER?

In other words, is there a way to tell a controller not to send any more commands for a certain period because the poor device is really busy saving stuff to eprom etc?

Kind regards
Bernt