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
32 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
Supported Messages
The headend will offer a mapping configuration in which phasor names may be
attributed to phasor numbers. The Phasor Name attributed to each Phasor Number
is configurable at the headend for a number of reasons:
1. The reference meter(s) may be placed on any phase. The system must be
configured to accommodate their location.
2. The utility may not wish to make the distinction between a phasor and its
inversion, e.g., AB and BA.
3. The utility may not wish to use the letters ABC but XYZ or some other
naming convention.
It is expected that multiple surveys will be required before sufficient data has been
collected to render a result. With surveys issued once a day, it may take several
days of data collection before sufficient data is available. As deployments roll out,
one may also find that an inadequate number of meters have been deployed, or that
sufficient DCU infrastructure has not been deployed. A full analysis will likely
have to wait for a full deployment to occur, however, it is still possible to test the
system in a small-scale setting or in the lab.
If one or more meters appears to not converge to a solution for the phase
connection, there may be an underlying issue that is preventing it. The possible
causes include:
• Incorrect headend or DCU configuration: The headend must have a traffic
class selected to send the phase detect beacon (resource "/pd") as a low
reliability message. It must only be transmitted one time by the DCU. The
high reliability traffic class will cause the DCU to repeat the message. This
will create multiple messages with the same beacon ID. Most (but not all)
duplicate transmissions will be rejected by the endoint population. The end
result will be disagreement in the data as to what the correct measurement is
for every phase being measured, and poor results from the analyzer.
• Poor power quality at the service location: Poor power quality can disrupt all
sorts of devices including the phase detect function in the meter. Customers
may note that numerous other electronic devices misbehave. Locations with
poor power quality will likely have high counts of momentary interruptions.
Leading causes of poor power quality include:
• failed components on the distribution network
• high impedance faults
• noisy loads
p10 -B
p11 AB
Table 5.2
Example Phasor Name to Number Mapping
Phasor Number Phasor Name