Alarm message format
The control byte and the repeat level/status byte in the header of each message indicate the presence of alarm conditions.
Bits | Definition |
---|---|
0:3 | RF Sequence Number |
4 | LAT Delay Bit 0 |
5 | IIT |
6 | Low Battery Detected |
7 | Payload Encrypted |
Bits | Definition |
---|---|
0:3 | RF Sequence Number |
4 | Reserved |
5 | Reserved |
6 | Low Battery Detected |
7 | Payload Encrypted |
The low battery alarm is indicated by bit 6 of the control byte.
Bits | Definition |
---|---|
0 | History Overflow |
1 | Meter Alarms |
2 | Reserved |
3 | LAT Delay Bit 1 |
4 | LAT Delay Bit 0 |
5 | RF Sequence Number MSB |
6:7 | Repeat Level |
Bit 0 indicates a reading history overflow. This is the only place history overflow is reported, with the exception of the error code in reading history. It is not logged as a historical alarm.
Bit 1 indicates the presence of one of the alarm conditions. To determine the specific alarm condition(s) that are present, it is necessary to observe what is reported in the alarm message (appcode 11).
Bits | Definition (Gas device) |
---|---|
0 | History Overflow |
1 | Tilt Alarm |
2 | Reverse Flow Alarm |
3 | History Overflow |
4 | Reserved |
5 | RF Sequence Number MSB |
6:7 | Repeat Level |
Each historical alarm condition is indicated by the respective bit in the repeat level/status byte.
When an NA2W device is configured in one-way mode for operation in a legacy network, all messages are transmitted in one-way format with one exception. Once per week, the SmartPoint module transmits a single alarm message in two-way format. Sending the two-way message (with LAT window) is done to facilitate upgrading a network from one-way mode to two-way. The LAT window gives the RNI an opportunity to send a message to the SmartPoint module to transition it from one-way to two-way mode.