User's Guide
Table Of Contents
- Table of Contents
- 1 - Introduction
- 2 - Safety Guidelines
- 3 - Regulatory Guidelines
- 4 - Product Specifications
- 5 - Features
- 6 - Inside the Meter
- 7 - Inspecting the Site for Anomalies
- 8 - Installing the Meter
- 9 - Testing NIC Communications in the Field
- 10 - Updates and Repairs
- Index
72 A c l a r a R F E l e c t r i c I - 2 1 0 + c U s e r G u i d e
Configuration Management
Meter Modes
The I-210+c meter can operate in one of three modes. This effectively turns the
I-210+c into three different meters. These modes determine what features are
operational in the meter. The modes are formally known as:
• Demand only
• Demand / LP
• TOU
Users should know that the “demand only” works best for a once-a-month reading
of demand in a non-AMI environment. Demand-only meters do not keep time.
They are unable to provide a date/timestamp for the demand maximum. The meter
hardware will provide a date/time value of 0 which represents midnight of January
1st, 1970. Demand-only meters will supply this timestamp for all meter events and
voltage events. However, certain alarms originate within the NIC. The last-gasp
message, the power-restored message, and the demand reset response message
(indicating a demand reset event) will all have a demand reset date and time
supplied by the NIC.
Customers that want a proper demand maximum date and time associated with
demand values should configure their meters to operate as demand / LP or TOU
meters.
Diagnostics
Cautions
A high temperature threshold of 70-75 degrees centigrade may be used. The
MeterMate setting should not exceed 75 °C.
Events
The Event Log should only capture the items of interest to the utility.
The Self Read Event (21) will occur daily and should probably not be included in
the list of reported items.
The Table Read Event (07) will occur every 5 minutes and will prove to be a
nuisance alarm if it is enabled. This could have the effect of drowning out more
important alarms that the utility cares about.
If Demand Reset is enabled as a logged event, the headend will receive alarms
twice - one by the NIC when it performs the action, and one by the meter’s event
log. If Demand Reset is not logged by the meter, the user must rely on demand
data (reported daily) to determine if a demand reset has occurred (perhaps locally
by a HandHeld MeterMate). The present max, previous max, and demand reset
counts can all be monitored for the changes that result from the demand reset
action.