Antx Messenger 600, User Manual

Page: 7 / 40

7
•
An analog input exceeding a user-defined delta for a user-defined period of
time
•
A scheduled update
• System faults
•
Power on or reset
1.3.1 Alarm Notification
The RemoteIQ backend provides notification to designated personnel via:
• Text message
•
Email
• Voice
Each method allows the user to acknowledge the message received.
1.3.2 Event Codes
Every message sent by the Messenger 600 to a host-based server application is
triggered by an event. The event generates a message and the message contains an
Event Code. The Event Code uniquely identifies to the server the reason the message is
being sent. Some of the messages generated contain data, others serve as just
notification that a particular event has occurred. Protocol document “M09-PRTCLxxx”
contains a list of all event codes.
1.3.3 Positive Acknowledgement
The Messenger 600 is configured to require a message acknowledgement from the host
server providing complete end-to-end verified communication. Message
acknowledgement provides a verifiable mechanism that a message was delivered, even
during poor network conditions.
1.3.4 Store and Forward Data Queue
There are several scenarios where a message may not be deliverable – network down,
host server down, poor connectivity to name a few. In the event that a message cannot
be delivered, it is stored in memory and is continually re-sent until properly
acknowledged. This store and forward memory is non-volatile and remains intact
during power off.
1.3.5 Real-Time Clock (RTC)
The RTC is used to time stamp data records and events. All messages sent to the host
server contain a time stamp to provide a chronology of data/events to the end user. The
RTC is battery backed to provide time keeping during power off. If the RTC is
configured to be automatically set, the Messenger will set time after every power on