Controller event buffer overflow message

When a controller is disconnected from the server, the controller buffer starts collecting the controller’s events. When the buffer is full, it transfers the oldest events in a secondary buffer (50 to 100 bytes) that always contain 50 events. When the communication is restored, the system then starts sending messages to the Desktop Message List to indicate that the buffer is full and that events are being deleted from the buffer.

• The controller will delete messages in FIFO order (First In, First Out). The oldest message will therefore be deleted first.
• When the controller is reconnected to the server, the controller events will be sent to the Message list all at once, in the following order: events in the controller’s secondary event buffer; a single Event Buffer Overflow will display, followed by the list of events generated while the controller was disconnected from the server.