BGX701-075-R03
Premier 211 User Manual
Page 27 of 56
a) Meter time set
b) Over the Air (OTA) firmware change- In this case two snapshots are taken, one before and the other
after the firmware change.
The meter stores ten (10) audit snapshots on a FIFO basis.
4.2.5.4
Current snapshot
The meter will record the current value of its energy registers which is sent to the HES on receipt of a current
snapshot request.
4.3
Metrology LEDs
Two calibration LEDs are provided on the meter main face plate. They flash in direct proportion to the rate of
energy consumption, as determined by the meter pulse weight. By default, one LED flashes to indicate Active
import (total) NET energy consumption at 5000 impulse/kWh and the second LED flashes to indicate the
consumption values of the configured energy type at 5000 impulse/kWh or kVArh.
4.4
Time keeping
The Premier 211 clock maintains time in hours, minutes, and seconds format.
All data logging (e.g. load survey data, events data, maximum demands and snapshots) take place using the
standard time whereas displayed date and time use local time (i.e. standard time + DST offset). The tariff rate
register switching operation can be configured to use standard or local time. Scheduled billing dates always use
standard time.
When the meter’s time is invalid for any reasons an RTC failure event is logged and an alert is sent to the HES
(if configured). The following activities that rely on meter time for their correct operation are affected or
suspended:
•
Rate Register switching (the meter continues with the last active rate price)
•
Maximum demand updates
•
Scheduled billing actions
•
Delayed or scheduled meter configurations
•
DST activation or deactivation
•
Load survey operation
•
Events logging will be as per the meter’s current time
•
The date and time on the meter display will appear as ‘--------‘
•
Midnight snapshots will be taken with standard time
•
Standing charges
The following two methods can be used to adjust a meter’s invalid time:
1. Time setting from the HES (Head-end-system)
2. Time synchronisation from the communication module
In order to distinguish time, set events between time synchronisation from the communication module and time
setting from HES, the issuer ID in the case of time synchronisation is logged as ‘0’ which is the same as at
manufacturing.
