This document describes:
- The effect that various exceptions and events have on reads in BEACON
- Exceptions and events that can result in estimated reads.
The following table lists the exceptions and events that can cause missed or suppressed reads.
| Exception/Event | Description |
| Endpoint Tamper | An exception triggered by a break in communication between an endpoint and an encoder. Typically occurs when the wire between the register and endpoint has been cut or disconnected.
Clears after connection is re-established. RTR encoders connected to ORION CE/ME/SE endpoints require reprogramming to clear the tamper. BEACON uses the last valid read, ignores reads post tamper as invalid. |
| Encoder Communication Error | Triggered when BEACON receives data from an encoder but a reading cannot be obtained. This indicates a communication error between the encoder and endpoint. The condition automatically clears when a new reading is obtained. Endpoints affected:
BEACON uses the last valid read, and treats any reads that occur post-error as invalid. |
| Endpoint Skipped | Triggered when a read was skipped. Possible causes include Firmware updates and gateway outages. Could result in reads being estimated. |
| Mobile Reading Missed | Set when a mobile reader gets within range of a reading location and no read is collected.
Endpoints affected:
BEACON displays and exports the last read, timestamped when it was collected. |
| Endpoint Forced Transmission | This flag indicates network transmission has been forced from a GALAXY TR3 endpoint.
Affects the read cadence. BEACON exports and displays the last valid read, timestamped when it was collected. |
| Meter Empty Pipe | Triggered when the meter senses there is not enough water in the pipe, preventing accurate reads from being obtained by E-Series meters and Mag meters.
BEACON displays and exports that last valid read. |
| Encoder Removed | This alarm is triggered when an HR-E LCD has been removed. No read can be obtained without the encoder being attached to the meter.
BEACON displays and exports the last valid read. |
| Endpoint Programmed | A flag set when HR-E LCD encoder parameters have been changed. Possible parameters that can be changed are: Meter Type, Meter Model/Size, Unit of Measure, Billing Units, Digits from Encoder, Rate of Flow Units and Rate of Flow Time.
BEACON displays and exports the last valid read. |
| Meter/Encoder End of Life | This alarm is activated after 19 years on HR-E LCD encoders and after 19 years and 6 months for E-Series meters.
BEACON displays and exports the last valid read. |
| Endpoint Temperature | This alarm indicates an HR-E LCD encoder or an E-Series meter is approaching the limit of its rated operating temperature.
BEACON displays and exports the last valid read. BEACON displays and exports the last valid read. |
| Meter Exceeding Max Flow | An alarm triggered when flow exceeds the maximum flow of the meter.
BEACON displays and exports the last valid read. |
| Meter Sensor Error | This alarm is triggered when there is a problem with the sensor on an E-Series meter that prevents readings from being properly obtained.
BEACON displays and exports the last valid read, timestamped when it was collected. |
| Encoder Magnetic Tamper | This alarm is triggered when there is a problem with the sensor on an E-Series meter that prevents readings from being properly obtained.
BEACON displays and exports the last valid read, timestamped when it was collected. |
Exceptions and Estimated Reads
When an endpoint is unable to communicate with BEACON, it continues to try to communicate until it succeeds.
Because ORION Cellular LTE endpoints store up to 42 days of quarter-hourly read data, missed reads are usually backfilled after the endpoint reestablishes communication with BEACON.
GALAXY endpoints record reads between call-in periods, but do not store them for more than 24 hours. In other words, GALAXY TR2 endpoints collect and send a single read every six hours. GALAXY TR3 endpoints collect hourly reads and send them every six hours. If communication gaps occur that last longer than 24 hours, when communication is reestablished, BEACON estimates reads by calculating flow using the previous and latest valid read and dividing the total evenly across the gap.
When communication gaps occur and an exception or an event causes the system to treat reads as being not valid, BEACON estimates reads. It does that by calculating the total flow between valid reads and dividing the total evenly across the gap.
Do estimated reads ever get converted to actual reads? No. BEACON only estimates reads when it detects corrupt or missing data that cannot be recreated.
For more on estimated reads, see Estimated Reads, Endpoints and Data Backfill.
The following table lists exceptions and events that can cause estimated reads.
| Exception/Event | Description |
| Endpoint Tampers | Tampers occur when the connection between the endpoint and encoder register is broken. Cut or disconnected wires that link an endpoint to an encoder register are frequent causes. Reads are suppressed when a tamper is present.
When the tamper clears and the system detects a valid read, it will fill in the gap between the previous and current valid reads with estimated reads. |
| Encoder Communication Errors | These types of errors can result in corrupted data. As a result, reads are suppressed.
When the endpoint and encoder are able to communicate successfully again, the system fills in the gap between the previous and current valid reads with estimated reads. |
| Gateway outages | Another condition that can potentially corrupt data and result in suppressed reads.
When gateway communication is reestablished and a valid read is detected, the system fills the gap between the previous and current valid read with estimated reads. |
| Firmware updates | While uncommon, updating endpoint firmware can result in corrupt data and suppressed reads.
The system fills the gap between valid reads with estimated reads. |
