0% found this document useful (0 votes)
14 views444 pages

Metercat User Guide

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views444 pages

Metercat User Guide

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 444

Metercat

User manual

Release 6.4

TM42-3060G
Trademarks
ALPHA, ALPHA Plus, REX, REX2, REXUniversal, EnergyAxis, IP AxisLink, CallistoUX, and Metercat are trademarks and/or registered trademarks of Elster. All other product
names may be trademarks and/or registered trademarks of their respective owners.
CONTENTS

Welcome to Metercat .......................................................................................1


What would you like to do? .....................................................................1
Work with programs and components ............................................1
Work with my connections ...............................................................1
Work with functions and tasks ........................................................1
Configure my version of Metercat ...................................................1
Getting started ..................................................................................................3
Logging into Metercat ..............................................................................3
I can't log in to Metercat ..................................................................3
Configuring Metercat for the first time ...................................................3
User environment .............................................................................5
Managing users and groups ............................................................................7
Account Information ................................................................................7
General tab .......................................................................................7
Details tab.........................................................................................8
Notes tab ..........................................................................................8
Meter Access Level tab ....................................................................8
User management ...................................................................................8
Group Information....................................................................................9
General tab .................................................................................... 10
Privileges tab ................................................................................. 10
Membership tab ............................................................................ 12
Viewsets tab................................................................................... 12
Functions tab ................................................................................. 12
Programs tab ................................................................................. 12
Meter Access Level tab ................................................................. 12
User Information ................................................................................... 13
General tab .................................................................................... 13
Details tab...................................................................................... 13
Notes tab ....................................................................................... 13
System configuration ............................................................................ 14
User Password Requirements ...................................................... 14
Network Storage ............................................................................ 14
Event Viewer.......................................................................................... 15
Viewing only Metercat events in the Event Viewer ...................... 15
Contents ii

Viewing Metercat event details .................................................... 16


About the CEF ................................................................................ 16
Components and programs .......................................................................... 19
Components .......................................................................................... 19
About components ........................................................................ 19
New Component ............................................................................ 20
New Component as Copy .............................................................. 20
Open and edit components .......................................................... 21
Save Component ........................................................................... 22
Export/Import Component ............................................................ 24
Delete Component ........................................................................ 26
Available components ................................................................... 27
Component descriptions ............................................................... 28
Programs ............................................................................................. 148
About programs ........................................................................... 148
New Program ............................................................................... 150
New Program as Copy ................................................................. 152
Using the Program Editor ............................................................ 152
Properties component ................................................................. 155
Export/Import Program ............................................................... 158
Save a program ........................................................................... 160
Delete Program ............................................................................ 160
Troubleshooting program/component imports ......................... 161
Functions and tasks .................................................................................... 165
About functions ................................................................................... 165
What is a function? ..................................................................... 165
How do I create a function? ........................................................ 165
What happens when a function is performed? ......................... 165
Function Management ....................................................................... 166
Function Builder .................................................................................. 166
Building or editing function ......................................................... 167
Controlling access to a function ................................................. 168
Performing a function.................................................................. 168
About Metercat's sample functions ............................................ 168
List of available tasks.................................................................. 168
Executing functions ............................................................................ 168
Sample functions ................................................................................ 169
Available tasks .................................................................................... 170
Task descriptions ................................................................................ 173
Activate C12.22 WAN Factory Key ............................................. 173
Activate LAN Factory Key ............................................................ 173
Contents iii

Billing Read .................................................................................. 174


Billing Reset ................................................................................. 176
Change Demand Overload .......................................................... 177
Change Demand Thresholds ...................................................... 177
Change Display Units for Primary Instrumentation ................... 178
Change DLMS Password ............................................................. 179
Change KYZ Output ..................................................................... 179
Change Modem Init String .......................................................... 180
Change Optical Test Source ........................................................ 181
Change Out Gatekeeper.............................................................. 182
Change Passwords ...................................................................... 183
Change Pulse Divisor .................................................................. 184
Change Seed Set ......................................................................... 185
Change Time ................................................................................ 186
Change Utility ID .......................................................................... 190
Clear Battery Log ......................................................................... 190
Clear Data .................................................................................... 191
Clear Event Log ............................................................................ 192
Clear Outage Data ....................................................................... 192
Clear PQM Data ........................................................................... 193
Clear Read without Power Data .................................................. 194
Clear Status Flags ....................................................................... 194
Clear Temperature Status Flags ................................................. 195
Configure Special Option Board ................................................. 196
Confirm Factory Unrestricted Seed ............................................ 196
Connect Service ........................................................................... 197
Demand Reset ............................................................................. 198
Diagnostic Read .......................................................................... 198
Disable/Enable Node Communication ....................................... 202
Disable Optical Port ..................................................................... 203
Disconnect Service ...................................................................... 203
Edit PQM Thresholds ................................................................... 204
Edit Service Test .......................................................................... 205
Enable Optical Port ...................................................................... 206
Fast Demand Test ....................................................................... 207
Meter Identification Info.............................................................. 207
Ping LAN node ............................................................................. 208
Poll Instrumentation .................................................................... 209
PQ Inspector ................................................................................ 209
Program ....................................................................................... 210
Register Edit ................................................................................ 217
Contents iv

Replace Configuration ................................................................. 218


Replace Loss Compensation ...................................................... 220
Replace PQM ............................................................................... 221
Replace Program ......................................................................... 222
Replace Rates and Dates ........................................................... 225
Replace Remote .......................................................................... 226
Set DA I/O relays ......................................................................... 226
Set Interposing Control Relay ..................................................... 228
Set Interrupter Control Relay ...................................................... 228
Set LAN Radio Test Mode ........................................................... 229
Test Mode Off .............................................................................. 230
Test Mode On .............................................................................. 231
Turn Loss Compensation Off ...................................................... 232
Turn Loss Compensation On ....................................................... 233
Turn PQM or TRueQ ON/OFF ...................................................... 233
Unlock Service ............................................................................. 234
Update Option Board Identification ............................................ 235
Export Endpoint Execution Request .................................................. 235
Completing the Export Endpoint Request Wizard ...................... 236
Views and viewsets ..................................................................................... 239
About viewsets .................................................................................... 239
What is a viewset? ....................................................................... 239
How do I create or edit a viewset? ............................................. 239
Viewset Management ......................................................................... 239
Viewset Builder ................................................................................... 239
Building or editing viewsets ........................................................ 240
Controlling access to a viewset .................................................. 240
Performing a read ........................................................................ 241
About Metercat's sample viewsets ............................................. 241
List of available views ................................................................. 241
Sample viewsets ................................................................................. 241
Available views .................................................................................... 243
View descriptions ................................................................................ 246
Billing views ................................................................................. 246
EOI/Midnight Snapshot view ...................................................... 247
Event log data view ..................................................................... 248
History log data view ................................................................... 249
Instrumentation view................................................................... 249
Interval data view ........................................................................ 251
PQM/Sag Log Data view ............................................................. 256
PQM/Sag status view .................................................................. 256
Contents v

REX view only items ..................................................................... 258


Security event log view ................................................................ 259
Special option board view ........................................................... 260
Status view .................................................................................. 260
Temperature monitoring view ..................................................... 285
Reports and stored readings ...................................................................... 287
Reports ................................................................................................ 287
Stored Readings Management .......................................................... 287
Opening stored readings ............................................................. 288
Exporting stored readings ........................................................... 288
Importing stored readings ........................................................... 293
Delete a stored reading .............................................................. 293
Configuring Metercat ................................................................................... 295
Update network storage ..................................................................... 295
Update programs from network storage ........................................... 295
Server Synchronization Options ......................................................... 295
About communications encryption ............................................. 295
Downloading a certificate from the server ................................. 297
Setting the synchronization options in Metercat ....................... 297
Synchronizing with the server ..................................................... 298
Meter Passwords Management ......................................................... 298
About the Meter Passwords Management dialog box............... 299
About password sets ................................................................... 299
ANSI C12.19 password sets ....................................................... 300
REX meter password sets ........................................................... 301
ALPHA Plus password sets .......................................................... 301
REXUniversal seed sets .............................................................. 301
Connections ........................................................................................ 302
About reading devices ................................................................. 302
Machine Settings ......................................................................... 302
Edit New Connection ................................................................... 303
Connection bars .......................................................................... 307
Phone Book.................................................................................. 311
System Preferences ............................................................................ 313
Preference descriptions ..................................................................... 314
Meters Supported........................................................................ 314
Site ID Labels ............................................................................... 314
Holidays........................................................................................ 315
Dates and Rates Options ............................................................ 315
Programming Options ................................................................. 315
Time Difference Options ............................................................. 317
Contents vi

Stored Readings .......................................................................... 317


Application notes ......................................................................................... 319
A3 ALPHA meter codes ....................................................................... 319
Error codes................................................................................... 319
Warning codes ............................................................................. 322
System service error codes ......................................................... 324
Events reported in Metercat ....................................................... 326
Warnings reported in Metercat ................................................... 327
Errors reported in Metercat ........................................................ 328
A3 ALPHA meter special display items .............................................. 329
A3 ALPHA meter with W-WIC special display items ................... 329
A1800 ALPHA meter codes ................................................................ 330
Error codes................................................................................... 330
Warning codes ............................................................................. 332
System service test error codes ................................................. 335
Events reported in Metercat ....................................................... 337
Warnings reported in Metercat ................................................... 337
Errors reported in Metercat ........................................................ 338
About Alpha Keys ................................................................................ 339
A3 ALPHA meter .......................................................................... 339
A1800 ALPHA meter ................................................................... 340
About AlphaPlus software .................................................................. 340
Troubleshooting AlphaPlus serial port conflicts ........................ 341
About DLMS passwords ...................................................................... 342
About security mode ........................................................................... 343
A3 ALPHA/A1800 ALPHA meters and IP AxisLink devices ........ 343
REXUniversal meters ................................................................... 343
About Special Dates ........................................................................... 343
Typical operation ......................................................................... 344
Compatible EER export operation .............................................. 344
About the register multiplier ............................................................... 345
Changing ANSI C12.19 passwords .................................................... 346
EA_NIC programming notes ............................................................... 347
A3 ALPHA meter with EA_NIC ..................................................... 347
A1800 ALPHA meter with EA_NIC .............................................. 349
Estimated load profiling days (A3 ALPHA) ......................................... 350
Estimated load profiling days (A1800 ALPHA) .................................. 351
Fast pulse ............................................................................................ 351
Fixed width pulse ................................................................................ 352
Four quadrant metering ..................................................................... 352
Keyboard shortcut guidelines ............................................................ 352
Contents vii

Viewing assigned shortcuts ........................................................ 353


Meter types ......................................................................................... 353
A3 ALPHA meters......................................................................... 353
A3 ALPHA metered energy and demand quantities .................. 356
A1800 ALPHA meters .................................................................. 357
REXUniversal meters ................................................................... 358
Metercat event IDs ............................................................................. 359
Security events ............................................................................ 359
Operational events ...................................................................... 368
Program types ..................................................................................... 369
Relay wiring diagrams......................................................................... 369
A3 ALPHA meter relays................................................................ 369
A1800 ALPHA meter relays......................................................... 371
REX2 meter codes .............................................................................. 372
Error codes................................................................................... 372
Status codes ................................................................................ 373
Events recorded in Metercat ...................................................... 376
Warnings recorded in Metercat .................................................. 376
Errors reported in Metercat ........................................................ 376
REXUniversal meter codes ................................................................. 377
Error codes................................................................................... 377
Status codes ................................................................................ 377
Metrology events recorded in Metercat ..................................... 381
Metrology warnings recorded in Metercat ................................. 381
Metrology errors reported in Metercat ....................................... 382
Comms warnings reported in Metercat ...................................... 382
Comms errors reported in Metercat ........................................... 383
REXUniversal meter special display items ........................................ 383
REXUniversal meter for the EnergyAxis mesh network special
display item .................................................................................. 383
REXUniversal meter with W-WIC special display item ............... 384
Standard pulse .................................................................................... 385
Transformer and line loss compensation .......................................... 386
About transformer and line loss compensation ........................ 386
Calculating the percent correction values for configuring the
meter ............................................................................................ 387
Line loss calculations .................................................................. 390
Calculation example .................................................................... 393
Inputs ........................................................................................... 394
Calculations ................................................................................. 394
Internal meter calculations ......................................................... 397
Note regarding two-element meters:.......................................... 399
Contents viii

Meter outputs affected by compensation .................................. 399


Testing a meter with compensation ........................................... 400
User ID assignments ........................................................................... 400
Legal notices ................................................................................................ 403
Trademarks ......................................................................................... 403
Copyright ............................................................................................. 403
Generated ........................................................................................... 403
Glossary ....................................................................................................... 405
Welcome to Metercat

Metercat, the meter configuration and analysis tool, is a software


application developed to program and read Elster's A3 ALPHA
meters, A1800 ALPHA meters, and IP AxisLink routers. Metercat also
performs various tasks on Elster's REX meters, REX2 meters, gREX
meters, and REXUniversal meters. Metercat runs on Microsoft
Windows operating systems.

What would you like to do?


Additional topics are listed in the Contents tab or Index tab of the
Help window. You may also search for keywords in the Search tab.

WORK WITH PROGRAMS AND COMPONENTS


1 Create a program from scratch or based on an existing program
2 Import or export a program
3 Create a component from scratch or based on an existing
component

WORK WITH MY CONNECTIONS


1 Connect to a meter or device locally using an optical probe
2 Set up my computer for a new connection
3 Create, edit, or delete entries in the Phone Book

WORK WITH FUNCTIONS AND TASKS


1 Perform a function or task
2 Create, edit, or delete a function or task

CONFIGURE MY VERSION OF METERCAT


1 Set or remove an expiry time for user passwords
2 Configure which meters and devices are supported

1
Getting started

Logging into Metercat


Note: If this is the first time you are starting your copy of
Metercat, you must log in as the Administrator and configure
Metercat's security settings.
Metercat supports two system configurations, which is determined at
the time of the initial setup.
 single user system
You must sign in as Administrator using the administrator
password.
 multiple user system
You must sign in typing your user name and password assigned
to you by the Metercat administrator. If you belong to more than
one group, select the group name for this session of Metercat.

I CAN'T LOG IN TO METERCAT


 User names in Metercat are case insensitive; however,
passwords are case sensitive. Check to make sure CAPS LOCK is
off.
 If you are using a multiple user system and cannot log in, contact
your Metercat administrator to have your password reset.
 If you are using a single user system, the administrator's
password is not recoverable. You must uninstall and then
reinstall Metercat to use Metercat on your computer.

See also
 Configuring Metercat for the first time
 User Management
 User Information

For more information


See the Metercat installation manual (TM42-3050) for information
on installing or uninstalling Metercat and its components.

Configuring Metercat for the first time

3
Getting started

Metercat uses enhanced security for storage of user IDs, user


passwords, and device passwords. When you start Metercat for the
first time, a warning box is displayed indicating that the Metercat
administrator must set up the security policy.
 If you are able to complete the security settings at this time, click
OK and continue with this procedure.
 If you are unable to complete the security settings at this time,
click Cancel. You will be presented with this warning dialog box
each time you start Metercat until you complete the security
settings.

Note: Once the user environment and user password


requirements have been configured, they may not be able to be
changed in the existing version of Metercat. See "user
environment" in the table below for more information.
To set the security settings:
1 From the Welcome to Metercat dialog box, type the password for
the Administrator account to log in to Metercat. Metercat only
allows for the administrator to log in for the first time.
2 From the System Configuration dialog box, configure the user
environment, user password requirements, and network settings
as appropriate for your installation.
Item Description
You can specify whether the version
of Metercat on this computer is a
Simple Single User environment or a
Multiple Users and Groups
User environment environment. If you choose single
user first, you may change to multiple
user mode later. Once you choose
multiple user mode, however, you
cannot alter the user environment.
You can specify a minimum password
length, which must be at least 6
alphanumeric characters and no
more than 50.
You can specify whether the
password requires at least one of the
allowed special characters.
You can specify how long passwords
User password requirements
can be used before they must be
changed, from 0 to 365 days. If you
set a value of 0, user passwords will
never expire.
You can change the password expiry
time by selecting Tools > System
Configuration from the Metercat
menu.
You can specify a network location for
the storage of Metercat files and
Network storage location
whether or not the meter programs
update form the network location

4
TM42-3060

when the user logs in.


The network storage location can be
modified later by selecting Tools >
System Configuration from the
Metercat menu.

3 Click OK to complete the initial setup. The User Information


dialog box for the Metercat administrator will be displayed.
4 In the Log On Password text box, type a new password for the
Administrator account. This password must meet the password
requirements you just set up.
Elster recommends that you retype your password.
5 In the Confirm text box, retype the new password.

Note: The Metercat administrator password is not recoverable. If


the password is forgotten or lost, the administrator will be locked
out. You must uninstall and then reinstall Metercat to reactivate
the administrator.

USER ENVIRONMENT

SIMPLE SINGLE USER


In a single user environment, there is one user—the Administrator.
The single user has unrestricted privileges to Metercat functions,
tasks, components, and programs.
In a Simple Single User environment, the logon password is not
recoverable. If the password is forgotten or lost, the user will be
locked out. You must install and then reinstall Metercat to reactivate
the single user account.

MULTIPLE USERS AND GROUPS


In a multiple user environment, Metercat supports multiple users and
groups. Each user has their own unique ID (per computer) and
password. The Metercat administrator can control various levels of
access based on group rights. For example, one group may have read
only access while another group may have billing read with demand
reset access. Some users may also be in the Administrator group,
giving the user administrator privileges within Metercat. Users may
also be assigned to more than one group. If a user is a member of
more than one group, they must select which group to use for their
session of Metercat when they log in.

See also
 System Configuration
 User Management

5
Managing users and
groups

Account Information
Tools > Account Information
You can view or change information regarding your Metercat account
as well as change your log on password using the Account
Information window.
The Account Information window contains the following tabs:
General, Details, Notes, and Meter Access Level.

Note: The Notes tab is only available for users with administrator
privileges. The Meter Access Level tab is only available in simple
single user mode. For multiple users mode, the Meter Access
Level is controlled by a Metercat administrator using the User
Information window.

GENERAL TAB
The General tab displays the following information:
 Meter Programmer's Identifier: Your unique ID number, which
may be a number from 2 to 9999. If you are in single user mode,
you can change the programmer ID. If you are in multiple user
mode, your programmer ID is set by the Metercat administrator
using the User Information window, and you cannot change it
unless you have administrator privileges. For more information
on the User ID, see User ID assignments.
 Log On Name: Your Metercat user name. If you are in single user
mode, the user name is always Administrator. If you are in
multiple user mode, your user name is assigned by the Metercat
administrator using the User Information window.
 Log On Password: In both single user and multiple user modes,
you can change your password by typing in a new password in
the Log On Password text box. The new password must meet the
password requirements as specified by the Metercat
administrator.
 Confirm: The password must be typed a second time to confirm.
 Meter Groups: In single user mode, the Administrator user is
always in the Administrators group. In multiple user mode, the

7
Managing users and groups

Member Groups box indicates all the groups associated with


your user name, as assigned by the Metercat administrator.

DETAILS TAB
You can view or edit the information associated with the user name
in the Details tab.

NOTES TAB
If you are in multiple user mode, the Notes tab is only viewable by
users in the administrators group. Administrator users can use the
text box to record information such as creation date, date of changes
to group associations, or information about the active status.

METER ACCESS LEVEL TAB


The Meter Access Level tab is only available from the Account
Information window in single user mode.
You can specify the password sets and the access level that are
accessible to you. The access level determines which of the three
passwords in the password set is used when you attempt meter
communication.
The password set and meter access level only apply to meter and
device communication. Neither password sets nor meter access level
affect Metercat privileges.
To learn more about meter passwords, password sets, and how
Metercat handles them, see Meter Passwords Management.

User management
Tools > User Management
Within Metercat, user privileges are controlled by the groups they are
assigned to. For example, users of one group may be limited to read-
only functions while users of another group may be allowed to
perform billing reads with demand reset capability. Some users may
be assigned to the administrator group, giving them identical access
to Metercat as the Administrator user account has. Users may be
assigned to more than one group. When a user has more than one
group, they must select which group privileges to use when they log
into Metercat.
From the User Management window, you can create users and
groups, edit users and groups, and determine which users and
groups are active or inactive. You can also set group privileges using
the User Management window.
 To view the members of a particular group, click on the name in
the Groups box. The Users box will display only those members
associated to the selected group.

8
TM42-3060

 To create a user, click New User. The User Information window is


displayed.
 To create a groups, click New Group. The Group Information
window is displayed.
 To edit a group, click on the group name in the Groups box and
then click Edit. The Group Information window is displayed.
 To edit a user, click on the user name in the Users box and then
click Edit. The User Information window is displayed.
 To delete a group or user, click on the name in the appropriate
box and then click Delete. You will be prompted to confirm
deleting the user information. Instead of deleting a user, Elster
recommends setting the user status to inactive. Inactive users
cannot log in or use Metercat; however, their meter
programmer's ID will still be unique and unassignable to new
users, making it possible to associate past actions to a specific
user account even if the account is inactive. Once an account is
deleted, the meter programmer's ID may be re-used.

Note: You can also edit a group or user by double-click on their


name. Additional shortcuts include right-clicking a group name or
user name.

To make group or user inactive:


1 Double-click on the group name or the user name you want to
make inactive. Either the Group Information window or the User
Information window will display.
2 From the General tab, uncheck the Active check box and then
click OK.

To make the user or group active again in the future, edit the user or
group and check the Active check box.

See also
 Logging into Metercat
 User Information
 Group Information
 User ID assignments

Group Information
Tools > User Management > New Group
Tools > User Management > Edit

Note: You must have the appropriate privileges to access User


Management. If you do not have the appropriate privileges, the
command is not available.

9
Managing users and groups

You create a new or edit the selected Metercat group, group


membership, privileges, and meter access levels from the Group
Information window. If you are in a group that has authorization
privileges (for example, Authorize Functions), you can authorize the
items using the Group Information window.
The Group Information window has the tabs: General, Privileges,
Membership, Viewsets, Functions, Programs, and Meter Access
Level.

Note: You will only see the tabs to which you have privileges. For
example, if you have Authorize Viewsets privileges, you will see
the Viewsets tab. If you do not have Administer Groups and
Users privileges, for example, you will not see the Privileges tab.

GENERAL TAB
The Group tab allows you to create or edit the groups general
information.
1 Active: If the group is active, then all the users in the group may
log into Metercat. If the group is inactive, users in the group will
not be able to log in or use Metercat.
2 Group Name: The group name is required. It may be any
combination of alphanumeric characters.
3 Description: The group description is optional.
4 Notes: The group notes are optional.

PRIVILEGES TAB
The Privileges tab allows you to set the level of access and control
the members of the group have.
Item Allows group members to
Create, edit, or delete groups and
Administer Groups and Users
users (see User Management)
Create, edit, or delete meter and
Manage Meter Passwords device password sets (see Meter
Passwords Management)
Synchronize Metercat with the head-
end system (see Server
Synchronization Options). Users in
groups with this privilege can also
communicate with network-enabled
meters. Communication is both
Cleartext with Authentication or
Allow Server Synchronization
Ciphertext with Authentication,
depending on the meter's
configuration. To communicate with
the network-enabled meters, users
must also have View Phone Book
Entries enabled as well as have
access to at least one function.
Edit and set system preferences
Edit System Preferences
based on the computer running

10
TM42-3060

Metercat and other options (see


System Preferences)
Authorize specific functions to
Authorize Functions members of other groups using the
Functions tab.
Edit existing functions (see Function
Create/Edit Functions Management) or create new
functions (see Function Builder)
View all existing functions using
Function Management. Users can
View Functions perform functions that they have
access to as specified in the Viewset
tab.
Generate and export an endpoint
execution request (EER) XML file
containing data and instructions that
Export Endpoint Execution Requests a programming client needs to
configure an Elster meter or device
(see Export Endpoint Execution
Request)
Authorize specific viewsets to
Authorize Viewsets members of other groups using the
Viewsets tab.
Edit existing viewsets (see Viewset
Create/Edit Viewsets Management) or create new viewsets
(see Viewset Builder)
Authorize specific meter programs to
Authorize Meter Programs
members of other groups
Create new meter programs and
components or edit existing programs
Create/Edit Meter Programs
and components (see Creating
programs)
View all existing meter programs and
components. Users can only load the
View Meter Programs
programs they are authorized to as
specified in the Programs tab.
Delete existing meter programs or
Delete Meter Programs
components
Export existing meter programs as
.ped files (see Export/Import
Export Meter Programs Program) or export existing
components as .pcd files (see
Export/Import Component)
Import .ped files as meter programs
(see Export/Import Program) or
Import Meter Programs import .pcd files as meter
components (see Export/Import
Component)
Edit existing phone book entries or
Create/Edit Phone Book Entries create new phone book entries (see
Phone Book)
View all existing entries in the Phone
Book. Users can also, depending on
View Phone Book Entries the meter configuration,
communicate with meters in the
Phone Book. See Phone Book for

11
Managing users and groups

more information. If communicating


with an Energy-Axis enabled meter,
the user must also be in a group that
has Allow Server Synchronization
privileges.
Delete Metercat stored reading (.msr)
Delete Stored Readings files (see Stored Readings
Management)
Export existing Metercat stored
Export Stored Readings readings as an .msr file (see Stored
Readings Management)
Import .msr files as a Metercat stored
Import Stored Readings reading (see Stored Readings
Management)
Start Alpha Keys software (see the
Alpha Keys user manual for more
Launch Alpha Keys
information on using Alpha Keys
software)

MEMBERSHIP TAB
You can specify which users are associated with the group. You can
add or remove multiple users by holding down either the CTRL key
(selects multiple users) or the SHIFT key (selects a range of users).
To learn how to create new users, see User Information.

VIEWSETS TAB
You can specify which viewsets are accessible to users of a group. If
you have the Authorize Viewsets privilege, you can enable viewsets
for users of other groups. To learn more about viewsets, see Viewset
Management.

FUNCTIONS TAB
You can specify which functions are accessible to users of a group. If
you have the Authorize Functions privilege, you can enable functions
for users of other groups.
To add or authorize a group, move the selected function from the
Available Functions list to the Enabled Functions list.
To remove access to a particular function, move the selected
function from the Enabled Functions list o the Available Functions
list.
To learn more about functions, see Function Management.

PROGRAMS TAB
You can specify which programs are accessible to users of a group. If
you have the Authorize Programs privilege, you can enable programs
for users of other groups. To learn more about meter programs, see
Creating programs.

METER ACCESS LEVEL TAB

12
TM42-3060

You can specify the password sets and the access level that are
accessible to users of a group. The access level determines which of
the three passwords in the password set is used when users in the
group attempt meter communication.
The password set and meter access level only apply to meter and
device communication. Neither password sets nor meter access level
affect Metercat privileges. For example, a group that has the
unrestricted password will only have privileges within Metercat
granted specifically to them.
To learn more about meter passwords, password sets, and how
Metercat handles them, see Meter Passwords Management.

User Information
Tools > User Management > New User
Tools > User Management > Edit
You create or edit Metercat user names and association information
from the User Information window. The User Information window has
the following tabs: General, Details, and Notes. The Notes tab is only
viewable by users in the administrators group.

GENERAL TAB
The General tab defines a user's logon name, password, and group
associations. If a user needs to have their password reset, an
administrator can change the user's password using this tab.
 Active: If the check box is checked, the user account is active. If
the check box is cleared, the user account is inactive. Inactive
users cannot log in or use Metercat.
 Meter Programmer's Identifier: You can change the meter
programmer's ID to be any unique number from 3 to 9999
(meter programmer ID 2 is always reserved for the Metercat
administrator). The meter programmer ID is stored in the meter
when the meter is programmed by the user.
 Log On Name: This is the name the user must type in the login
window when starting Metercat. The log on name may be any
combination any alphanumeric characters.
 Log On Password: The new or updated password must meet the
password requirements as set by the Metercat administrator.
 Confirm: The password must be typed a second time to confirm.
 Available Groups: A list of all the available groups.
 Member Groups: A list of the groups the user belongs to.

DETAILS TAB

13
Managing users and groups

All of the information in the Details tab is optional. The full name
entered in the Details tab is full name displayed in the User
Management window.

NOTES TAB
The Notes tab is only viewable by users in the administrators group.
Administrator users can use the text box to record information such
as creation date, date of changes to group associations, or
information about the active status.

See also
 Group Information
 User Management

System configuration
Tools > System Configuration

Note: If this is your first time configuring Metercat, see


Configuring Metercat for the first time. After the initial
configuration, the User Environment settings and the User
Password Requirements, with the exception of the expiry time,
cannot be changed after the initial configuration.
After the initial setup, you can only change the password expiry time
and the network storage options.

USER PASSWORD REQUIREMENTS


The maximum number of days before users' passwords must be
change may be set from 0 to 365 days, where 0 means that the
users' passwords will not expire.

NETWORK STORAGE
Metercat allows meter programs to be stored as master files on a
network server or folder. This will allow for a centralized location for
meter programs that different computers can access. To copy meter
programs to the network location for others to have access to, users
must have the Export Meter Programs privilege and select Tools >
Update Network Storage. To manually update meter programs from
the network, users must select Tools > Update Programs from
Network Storage.
The network location can be specified using the … button or by typing
the path (including UNC path names) in the text box.
When Metercat updates local programs from a network storage
location, the following conditions apply:
 local user privileges for existing programs are not changed
 when retrieving a new program from the network, local user
access privileges are for the Administrator group only

14
TM42-3060

 password sets are imported with master programs


If imported password sets are changed, Metercat lists the names
of the changed sets. If new password sets are imported,
Metercat lists the names of the new password sets.
 Metercat reports changed components after updating from the
master program

When Automatically update programs from Network Storage after


log on is checked, Metercat will automatically update programs from
the network storage location (provided the user has sufficient
privileges for importing meter programs).

Event Viewer
Note: This topic covers the Microsoft Event Viewer (specifically,
for Microsoft Windows 7) and how it relates to Metercat. See the
Microsoft help and documentation for more information on using
the Event Viewer.

VIEWING ONLY METERCAT EVENTS IN THE EVENT


VIEWER
To view the Event Viewer, click the Windows Start button and type
Event Viewer in the Search program and files text box. Click on
Event Viewer when it is displayed in the list of available programs.
This procedure will display only Metercat-related events logged at any
time regardless of the event level, event ID, task category, keyword,
user, or computer.
1 On the left side, expand the Windows Logs folder and click on
Application.

15
Managing users and groups

2 From the Actions panel on the right, click Filter Current Log. The
Filter Current Log is displayed.
3 On the Filter tab, from the Event sources drop list, select
Metercat.
4 Be sure the remainder of the dialog box has the following options
selected and then click OK:
Item Setting
Logged Any time
Event level Clear all check boxes
Event logs Application
Includes/Excludes Event IDs <All Event IDs>
Task category Blank
Keywords Blank
User <All Users>
Computer(s) <All Computers>

VIEWING METERCAT EVENT DETAILS


To view the details of the Metercat event, click on the desired event
in the list of events.
 You can copy the event details as text or save the select event
from the Actions menu.
 You can open the selected event in a separate dialog box by
double-clicking the event.
Metercat generated events are recorded using the Common Event
Format (CEF) specification. The CEF formatted log details are
captured in the Description field of the log entry.

ABOUT THE CEF


Metercat uses the Event Viewer to log security and operational
events using the CEF format. This allows Metercat administrators to
monitor activities of users as well as help diagnose issues reported
by the user.
The CEF description has two parts: the header and the extension.
 The CEF header has a fixed number of fields describing the
general nature of the event. Each field is separated by a pipe
character (|)
 The CEF extension provides additional information about the
specific event, and the information can vary based on the type of
event.

For a description of all the events that Metercat can report, see
Metercat event IDs.

CEF HEADER
The following is an example of a Metercat event's CEF header:

16
TM42-3060

CEF:0|Elster|Metercat|6.1.0|SecurityServiceOrMechanism(9)|Auth
enticationSuccess(799)|Information(6)|
 Version of the CEF log format: CEF:0 indicates that this is the
first version of the CEF log format
 Device vendor: Elster
 Device product: Metercat
 Device version: 6.1.0
 Signature ID: General category of the event. In this example, it is
SecurityServiceOrMechanism(9).
 Name attribute: The probable cause of the event. Each signature
ID has a specified list of possible name attributes.
 Severity: The severity of the event. Metercat typically uses
Information(6) or Warning(7) as the severity level. For description
of the severity levels, see the Event Viewer online help.

CEF EXTENSION
The CEF extension has two parts: the standard extension attributes
and custom extension attributes. The extension attributes are
dependent on the specific event and not all events may have all
fields.

Standard extension attributes


 externalID: a sequentially incrementing number assigned to each
event
 deviceExternalID: The reporting device's GUID(global unique
identifier. The PC's GUID is assigned at the time of the Windows
OS installation. It is stored in the Registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Crypto
graphy\MachineGuid).
 suid and suser: The source GUID and source user name who
attempted to perform the action. The suid and suser information
are read from the Metercat database.
 dst: The intended destination of the attempted action. This field
is used to indicate the destination meter's IP address (when
relevant).
 duid: The destination GUID of the user who is the intended
recipient of the action or the device manufacturer serial number
of the intended meter.
 duser: The destination user name or the meter family and serial
number of the intended meter.
 reason: The text string created by Metercat describing the event
 cat: The category of the event as set by Metercat. The category
helps filter the list of events. Metercat uses securityAudit(1) as
the category for all security and operational events.

17
Managing users and groups

 msg: The task message created by Metercat in event of a task


failure.
 rt, start, or stop: The receipt time of the event. Alternatively,
some tasks may have a start time and a stop time logged
instead of rt. All times are recorded in UTC (GMT). No time zone
or DST offset is applied to UTC.
 outcome: Metercat will record whether the task had a success or
if it failed.

Custom extension attributes


 cs1Label and cs1:
o For configuration change events, cs1 is used to capture the
values before the event.
o The value is captured with the name: value syntax. Multiple
values are separated by a semicolon (;).
 cs2Label and cs2:
o For configuration change events, cs2 is used to capture the
values after the event.
o For task execution events, cs2 is used to capture the values
of the task parameters (if any) at runtime.
o The value is captured with the name: value syntax. Multiple
values are separated by a semicolon (;).
 cs3Label and cs3:
o Set as eventId. This is the description label for the custom
extension.
o The event ID is set according to the event code number.

18
Components and
programs

Components
ABOUT COMPONENTS

WHAT IS A COMPONENT?
Components define meter operation and gather the parameters
regarding a specific area of meter behavior. For example, you can
create a component for relay output handling or another component
that defines the meter's log entries.
Components can vary depending on meter family, meter type, and
timekeeping capability. When you create components, you will
specify the dependencies. This will be important when you create
programs using existing components. For example, if you create a
Demand component for a demand-only meter, Metercat will not allow
you to use the component in a TOU meter. Some components may be
compatible with different meter families. When creating such a
component, Metercat will display a dialog box asking if you want to
maintain compatibility. If you select to maintain compatibility, you
can use the same component in programs for different meter
families.

HOW DO I CREATE COMPONENTS?


There are different ways to create components:
 create a component from the start (File > New> Component)
 create a component by copying an existing component (File >
New > Component as Copy)

The list of available component types in Metercat. View the topic for
each component for more information.

HOW DO I EDIT COMPONENTS?


To edit an existing component, you open it (File > Open >
Component) and then make your edits. When you are finished
making changes, save the component (File > Save).

HOW DO I DELETE COMPONENTS?

19
Components and programs

To delete a component, select File > Delete > Component.

NEW COMPONENT

Note: Metercat controls access to components based on your


group privileges for programming. You must have create program
privileges to create components.
To create a component from the start
1 Select File > New > Component. The New Component dialog box
is displayed.
2 Select the appropriate meter from the Meter Family drop list.
3 Select the component you want to create from the list and then
click Open. The selected component will be displayed in a new
window. See Available components for a listing of components
and for links to the help topic for the individual components.

See also
 See New Component as Copy for information on creating a
component based on an existing component.
 See Save Component for information on saving a component
after you finish editing it.

NEW COMPONENT AS COPY


File > New > Component as Copy

Note: Metercat controls access to components based on your


group privileges for programming. You must have create program
privileges to create components.
You can create a component by copying an existing component. This
can be useful if you already have an existing component that you
want to make changes to, but you don't want to risk making changes
to the existing component.
When the New Component as Copy dialog box is displayed, it will
show all the existing components. The dialog box has several options
to help you sort and narrow the list:
 Meter Family drop list: Narrows the list by showing the existing
components that are compatible with the selected meter family.
 Components of Type drop list: Narrows the list by showing only
existing components of the type selected. See Available
components for information on component types.
 List button and Details button: Toggle between how much
information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

20
TM42-3060

To create a component by copying an existing component:


1 Select File > New > Component as Copy. The New Component
as Copy dialog box is displayed.
2 Select the component that you want to copy. The Source
Component Name text box displays the name of the selected
component you want to copy.
3 If you want to see which programs use the selected component,
click More. Using the mouse, you can click on the horizontal rule
and drag it to control how much of the programs you are viewing.
To hide this list, click Less.
4 In the New Component Name text box, type the new name for
the component.
5 Click Open. Metercat creates a component based on the source
component and displays the new component in the component
editor.
See Available components for a listing of components and for links to
the help topic for the individual components.

See also
 See New Component for information on creating a component
from the start.
 See Save Component for information on saving a component
after you finish editing it.

OPEN AND EDIT COMPONENTS


File > Open > Component

Note: Metercat controls access to components based on your


group privileges for programming. You must have view program
privileges to view components, and you must have create/edit
program privileges to edit components.
You can edit an existing component by opening it and making your
desired changes. If you make changes to the component and save it,
you may affect any program that includes it. For more information,
see Save Component. When the Open Component dialog box is
displayed, it will show all the existing components. The dialog box has
several options to help you sort and narrow the list:
 Meter Family drop list: Narrows the list by showing the existing
components that are compatible with the selected meter family.
 Components of Type drop list: Narrows the list by showing only
existing components of the type selected. See Available
components for information on component types.

21
Components and programs

 List button and Details button: Toggle between how much


information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

To open a component:
1 Select File > Open > Component. The Open Component dialog
box is displayed.
2 Select the component you want to open. The Component Name
text box displays the name of the selected component as
confirmation.
3 Click Open. Metercat opens the selected component in the
Component editor.
See Available components for a listing of components and for links to
the help topic for the individual components.

To close the component:


 Select File > Close.
If you made changes, you will be prompted to save the
component (see Save Component). If you want to discard any
changes, click No.

SAVE COMPONENT
File > Save

Note: Metercat controls access to components based on your


group privileges for programming. You must have create program
privileges to save components.
When saving a component, Metercat distinguishes between
components that are not used in existing programs from components
that are.
 If you are saving a component that is not used in an existing
program (for example, saving a component that you created from
the start), then Metercat will present a simplified Save
Component As dialog box.
 If you are changing a component that is used in existing
program, saving the component will update it in all the programs
that contain it. Metercat will present a Save Component As
dialog box that identifies the affected programs.

SAVING A COMPONENT THAT IS NOT USED BY EXISTING


PROGRAMS

22
TM42-3060

When you have finished with component and want to save it, select
File > Save. The Save Component As dialog box is displayed. When
the Save Component As dialog box is displayed, it will show all the
existing components. The dialog box has several options to help you
sort and narrow the list:
 Meter Family drop list: Identifies existing components that are
compatible with the selected meter family. Because you selected
the meter family when creating the component, this option is
grayed out and cannot be changed when saving it.
 Components of Type drop list: Identifies existing components of
the type selected. Because you selected the component type
when creating the component, this option is grayed out and
cannot be changed when saving it.
 List button and Details button: Toggle between how much
information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

To save the component, type a name in the Component Name text


box and click Save.

SAVING A COMPONENT THAT IS USED BY EXISTING


PROGRAMS
When you have finished with a component and want to save it, select
File > Save. When the Save Component As dialog box is displayed, it
will show all the existing components. The dialog box has several
options to help you sort and narrow the list:
 Meter Family drop list: Identifies existing components that are
compatible with the selected meter family. Because you selected
the meter family when creating the component, this option is
grayed out and cannot be changed when saving it.
 Components of Type drop list: Identifies existing components of
the type selected. Because you selected the component type
when creating the component, this option is grayed out and
cannot be changed when saving it.
 List button and Details button: Toggle between how much
information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

23
Components and programs

If Metercat determines that the component is used by an existing


program, the dialog box will open with the extended view. The Save
Component As dialog box will list the programs that use the selected
component in the lower portion of the dialog box. If you do not see
the extended view, click More. When you finish saving the
component, the component will be automatically updated in all listed
programs.
 To update the component in the existing programs, click Save.
 To save the component without affecting any existing programs,
change the name of the component in the Component Name
text box and then click Save.

EXPORT/IMPORT COMPONENT
Tools > Export/Import Components

Note: To export or import components, you must have the


appropriate export meter programs or import meter programs
privileges.
Metercat provides a means to transfer components by exporting
them from one installed version of Metercat and importing them into
another installed version.

EXPORT A COMPONENT
The Export/Import Component window allows you to sort the list of
available programs in your Metercat installation, select the specific
component, and then export the component as a .pcd or .xml file.
The file can then be transferred to another Metercat installation and
then imported as a component. The Export/Import Component
window has options to help sort and narrow the list:
 Meters and Types drop list: Narrows the list of components
based on meter family and meter type.
 Components of type drop list: Narrows the list of components
based on their type (for example, display only Special Dates
components).
 List button and Details button: Toggle between how much
information is displayed. When viewing the component as a list,
you see only the component names. When viewing the
components by details, you see the component name, meter
types, the date it was created, who created it, when it was last
modified, and other unique information.

To export a component:
1 Click on the component you want to export. To confirm your
selection, the Component Name text box will display the name
of the program.

24
TM42-3060

2 If you want to see the programs that use the component that will
be exported, click More. Click Less to hide the information.
3 When you are ready to export the program, click Export. The
Save Exported Component As dialog box is displayed.
4 Navigate to the desired location and change the file name if you
want. The Save as Type drop list allows you to choose .pcd or
.xml as the extension.
5 Click Save to complete the export.

IMPORT A COMPONENT
The Export/Import Program window allows you to import a Metercat
program file. You can import a program from either a .ped or .xml file.

About importing programs


 You are allowed to import components created in earlier versions
of Metercat into later versions of Metercat.
 Components will be updated during an import.
Since a program is a set of components, it is possible that the
component you are important may have a component name that
already exists. The component that is being imported will replace
an existing component with the same name in the destination
version of Metercat. This will affect all other programs in the
destination version of Metercat that uses the component. You
will be prompted during the import process if there are
component conflicts, and you will be able to cancel the
procedure, and no data will be affected.

To import a component:
1 Click Import. The Select PCD file to Import dialog box is
displayed.
2 If necessary, change the format from the drop list from .pcd to
.xml.
3 Navigate to the location that has the file to be imported and
select it. The File Name text box displays the name of the file to
confirm your selection.
4 Click Open.
As a shortcut, you can double-click on the .pcd file from Windows
to start the import process. Metercat will warn you if there are
any component conflicts.
5 If there are component conflicts, Metercat will display a dialog
box warning you which components will be updated during the
import. Review the list carefully.
6 Click OK to complete the import; click Cancel to end the
procedure without affect data.

25
Components and programs

7 When you finish, click Close. Metercat will generate an Import


Component Activities report when the import is either completed
or canceled.

ABOUT FILE TYPES


The .pcd file is an XML document. The extension .pcd is associated
with Metercat, making it easy to import the program by simply
double-clicking on it. You can save the file with an .xml extension,
and the file will then open using the default XML editor on your
computer. It doesn't matter which file extension you use, you can
import the program as either a .pcd or an .xml file.

Note: Do not edit the .pcd or .xml file manually. Manually editing
a Metercat component file may result in an invalid meter
program, which may affect meter operation or billing data.

DELETE COMPONENT
File > Delete > Component

Note: Metercat controls access to components based on your


group privileges for programming. You must have create/edit
program privileges to delete components.
Because Metercat does not allow you to delete components that are
used in existing programs, you must change the programs so they
don't use the component you want to delete. See About programs for
information about editing programs.
When the Delete Component dialog box is displayed, it will show all
the existing components. The dialog box has several options to help
you sort and narrow the list:
 Meter Family drop list: Narrows the list by showing the existing
components that are compatible with the selected meter family.
 Components of Type drop list: Narrows the list by showing only
existing components of the type selected. See Available
components for information on component types.
 List button and Details button: Toggle between how much
information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

The Delete Component dialog box also has a list of Programs using
the selected component. If the selected component is used in
existing programs, the program information will be displayed
informing you of which programs will need to be edited. The
horizontal rule above this list can be clicked and drag to reveal as
much of the list box as you need.

26
TM42-3060

To delete a component:
1 Select File > Delete > Component. The Delete Component
dialog box is displayed.
2 From the list of components, select the component you want to
delete. The Component Name text box will display the selected
component as confirmation of your selection.
3 Click Delete. Metercat will prompt you to confirm your deletion.

Note: If the Delete button is grayed out, then the selected


component is used in at least one existing program. You must
change all of the programs so they don't use the component you
want to delete.
4 Click Yes to delete the component.

See also
 See About programs for information on creating, editing, saving,
and deleting programs.

AVAILABLE COMPONENTS
Click on the component name to learn more.

Note: The Properties component is only available from within a


program, and you can only configure it by using the Program
Editor.
A1800
Component type A3 ALPHA IP AxisLink REXUniversal
ALPHA
ACL (Access
Control List)

Binary IO •
Constants • • •
Demand • • •
Demand Limiting •
Display •
DNP •
Event Log
Configuration
• •
Event Notifications •
Instrumentation
Profiling
• • •
Load Profile • •
Logs • •
Loss
Compensation
• •
Metering • • •
Network •
PQM/TRueQ • •

27
Components and programs

Rates • • • •
Relay Options • •
Remote • •
Service Test • •
Special Dates • • • •
Special Features • •
Special Option
Board
• •
Voltage Monitoring •
WAN Configuration •

COMPONENT DESCRIPTIONS

ACL (ACCESS CONTROL LIST) COMPONENT


The ACL component allows you to specify which IP addresses and
which MAC addresses can be accepted by the IP AxisLink router
when a client attempts to communicate using the WAN port. MAC
filtering may be enabled, but it only applies to a local subnet
attached to the device. Typically, all communication traffic will come
from a gateway or modem, and there would only be a single MAC
address to configure.
For more information, see the IP AxisLink router installation and
administration guide (TM42-4002).
 To control which IP addresses can access the IP AxisLink router,
check the Enable Source Checking box under the IP-ACL for
WAN section.
 To control which MAC addresses can access the IP AxisLink
router, check the Enable Source Checking box under the MAC-
ACL for WAN section.

If you enable source checking, you can collapse or expand section by


toggling the button to the left of each section label.

BINARY IO COMPONENT
The binary IO component allows you to configure the 4 discrete
binary inputs and the 2 discrete binary outputs on the IP AxisLink
router. See the IP AxisLink router installation and administration
manual (TM42-4002) for more information. You can configure the
input debounce period as well as the output assignments. The
parameters for each output varies depending on wither you are
selecting C12.19 or DNP as the assignment.
 Input debounce period (ms): you can enter a range from 0 to 80
ms, with 40 ms being the default.
 Output assignment 1/Output assignment 2: You can select
either C12.19 (default) or DNP.

C12.19

28
TM42-3060

If you select C12.19 for output 1 or output 2, you must also specify
the control mode.
 If you select Level as the control mode, then no other
parameters are required.
 If you select either Pulse High or Pulse Low as the control mode,
then you must pulse time from a range of 10 ms to 2550 ms.

DNP
If you select DNP for output 1 or output 2, then no other parameters
are required.

CONSTANTS COMPONENT
The Constants component allows you to program the values Metercat
will write into the meter for calculating adjusted Ke, adjusted Kh, and
Kd.

A3 ALPHA/A1800 ALPHA meter constants


The Constants component is valid for all meter types and program
types.

Metering application

You must select either Primary Metering or Secondary Metering as


the metering application
Primary metering: The meter converts the measured energy and
demand quantities to primary units using the current transformer
ratio and voltage transformer ratio. Metered quantities reflect energy
and demand on the primary side of the instrument transformers.
While Metercat allows you to enter and store the register multiplier,
the register multiplier value is not used for storing or displaying
energy and demand values. A3 ALPHA and A1800 ALPHA meters
always use the adjusted Ke for energy calculations.

Secondary metering: The meter does not use the CTR or VTR to
adjust the metered quantities. The metered quantities reflect the
energy and demand on the secondary side of the instrument
transformers even if the VTR and CTR are programmed into the
meter.

Transformer factor

You can specify the current transformer ratio and the voltage
transformer ratio by typing a value of 1.00 to 9999.99 in the
respective boxes. Metercat will display the transformer factor (CTR ×
VTR) automatically.

29
Components and programs

Register multiplier

You can select the register multiplier from the drop list. If you require
a different value, you can type it directly into the box.
Adjusted Kh, Ke, Kd
Metercat displays "undefined" in the text boxes. To view the meter's
programmed adjusted values, read the meter and select the
Constants view.

REXUniversal meter constants


The REXUniversal meter only supports secondary metering. Even
though the meter doesn't use current transformer ratio or voltage
transformer ratio to adjust the metered quantities, you can still
program them into the meter. You can type a value between 1.00 to
9999.99 in the respective boxes.

DEMAND COMPONENT
The Demand component allows you to configure the demand
operation within the meter. The parameters vary depending on the
program type (whether the meter is a demand-only meter or a TOU
meter).

A3 ALPHA/A1800 ALPHA meter demand

Exponential response

If checked, the meter emulates thermal demand. The meter


calculates demand based on a logarithmic scale that emulates
thermal demand meters. The thermal demand constants (t c) vary
depending on the operational mode of the meter:
 Normal mode = 15 minutes
 Test mode = 1 minute

After tc minutes of application of the constant load, the demand


indication will be 90% of its final value. After 2 × tc minutes, the
demand will be 99% of the final value. After 3 × tc minutes, the
demand will be at 99.9% of the final value.

Interval and subinterval lengths

To configure the meter for rolling demand, you must specify two
parameters:
 The Interval length is specified in minutes and may be any value
that is evenly divisible into 60.
 The Subinterval length is also specified in minutes and may be
any value that is evenly divisible into the interval length.

30
TM42-3060

The demand is calculated at the end of each subinterval, resulting in


an overlapping demand interval (or a "rolling" demand). For example,
you can configure a 15-minute demand interval and a 5-minute
subinterval. In this case, the demand is calculated every 5 minutes
based on the 3 previous 5-minute subintervals.
If you set the same length for both the interval and subinterval, the
meter is configured for "block demand."

Test interval and test subinterval

The meter supports a test mode, which displays test readings without
affecting the present energy usage and billing data values. Test
mode has its own independent interval and subinterval lengths,
which can be shorter to reduce demand test time. It will not interfere
with billing data. Like the demand interval and demand subinterval,
you must specify two parameters:
 The Test Interval length is specified in minutes and may be any
value that is evenly divisible into 60.
 The Test Subinterval length is also specified in minutes and may
be any value that is evenly divisible into the interval length.

For information on test mode, see the meter technical manual.


Typically, test mode is described in chapter 3, "Operating
instructions," and other chapters.

Overload

You can specify a threshold (in kilo units for the metered quantities)
that will trigger an overload indication. Overload is generally intended
to inform a utility when an installation is requiring more power than
the service equipment was originally designed to handle. When this
threshold is exceeded, the meter can display a warning on the LCD,
activate a relay, or make an alarm call.
The Overload value can be within the range of 0.0000 to
999999.9999, where 0.0000 disables overload monitoring.
For single rate demand program types, anytime the overload
threshold is exceeded, an overload indication is triggered.
If you are using a time of use program type, you can also specify a
threshold by rate. If the demand exceeds the threshold while in the
rate, the meter will trigger an overload indication. You need to plan
the general overload threshold and the per rate threshold carefully to
avoid potentially undesired results. For example, if you have a higher
rate threshold than general threshold, the general threshold will
always trigger an overload indication regardless of the meter's
current rate.

See also

31
Components and programs

The Metering component allows you to enable or disable both


overload and demand limiting capabilities using a single toggle.

Threshold

You can specify a threshold (in kilo units for the metered quantities)
that will trigger load control relay. The load control relay closes when
the demand exceeds this threshold, and it will remain closed for the
duration of the interval. The relay will open after the demand remains
below this threshold for one full interval.
The Threshold value can be within the range of 0.0000 to
999999.9999, where 0.0000 disables the load control capability.

See also
The Metering component allows you to enable or disable both
overload and demand limiting capabilities using a single toggle.

Demand Forgiveness Time

Demand forgiveness is the time during which demand is neither


calculated nor stored after a power restoration. Using Metercat, you
can specify the number of minutes that demand is not calculated or
stored (from zero to 255 minutes).
If you are using a single rate demand program type, then any power
outage will result in the demand forgiveness time being applied. If
you are using a TOU program type, you can also specify the number
of minutes a power outage must last to quality for demand
forgiveness (from zero to 15 minutes).

Cumulative Demand Type

Maximum demand is the highest demand value that occurs in a


billing period. The demand for each interval is calculated and
compared to an earlier maximum demand value. If the new interval
exceeds the earlier maximum demand, then the new demand is
stored as the maximum demand. In addition to the maximum
demand, the meter also stores either a cumulative demand (at reset)
or a continuous cumulative demand.
At reset: Using the cumulative maximum demand, a demand reset
adds the current maximum demand value to the cumulative
maximum demand. Since the cumulative demand is not reset to
zero, unauthorized demand resets do not cause a loss of the
maximum demand data. To determine the maximum demand for a
billing period after a demand reset, subtract the previous cumulative
demand from the current cumulative demand.
Continuous: Continuous cumulative maximum demand works
similarly to cumulative maximum demand. Continuous cumulative
maximum demand, however, is always equal to the sum of the
previous billing period continuous cumulative demand and the
current maximum demand.

32
TM42-3060

REXUniversal meter demand

Demand Mode

Rolling demand (or sliding demand) is defined by two parameters:


the demand interval and the subinterval length.
 The Interval length is specified in minutes and may be any value
that is evenly divisible into 60.
 The Subinterval length is also specified in minutes and may be
any value that is evenly divisible into the interval length.

The demand is calculated at the end of each subinterval, resulting in


an overlapping demand interval (or a "rolling" demand). For example,
you can configure a 15-minute demand interval and a 5-minute
subinterval. In this case, the demand is calculated every 5 minutes
based on the 3 previous 5-minute subintervals.
Block demand is a special case of rolling demand in which the
subinterval is always the same length as the interval.

Demand Forgiveness Time

Demand forgiveness is the time during which demand is neither


calculated nor stored after a power restoration. Using Metercat, you
can specify the number of minutes that demand is not calculated or
stored (from zero to 255 minutes).

DEMAND LIMITING COMPONENT


If the REXUniversal meter is equipped with an optional internal
service control switch, the meter can be programmed to open the
service control switch to disconnect power when the demand
threshold is exceeded. When the switch is opened, it will remain
open until the end of the next demand subinterval and stay open for
an additional time (as defined by the time penalty).

Example: The demand threshold is set to 2 kW (2000 W). At


about 8 minutes into the interval, the demand threshold is
exceeded, causing in the service control switch to open. The
switch will remain open until the end of the subinterval plus the
time specified by the penalty (in this case 10 minutes).

33
Components and programs

Additionally, you can also control the demand limiting operations to


specific tiers as well as how many times demand limiting operations
can be performed.
Item Description
Specify the threshold for the demand quantity (in
units) that, if met or exceeded, will cause the
service control switch to open. Source 1 and Source
2 are configured in the REXUniversal meter's
Metering component.
You can type the quantity directly into the text box.
Clicking the up or down arrows will adjust the
Demand Thresholds
quantity by 1000 units (for example, if you type
(units)
1500, clicking the up arrow will increment to 2500;
if you type 1500, clicking the down arrow will
decrement to 500).
To inhibit the demand limiting operation, type an
impossibly high value, such as 999999. Note:
Typing a value of zero will always result in a
demand limiting operation.
You can specify which tiers the demand limiting
operating can occur. For example, you can
Demand Limiting Tiers
configure the meter to only perform demand
limiting operations in Tier A and Tier C.
The time (in minutes) the switch will remain closed
Demand Limiting Time after the end of the meter's subinterval. If you
Penalty specify a time of zero, the switch will close
immediately at the end of the next demand interval.
In addition to the time penalty, you can specify a
maximum time (in seconds) that the meter will
delay closing the switch. The meter will close the
switch at a randomized time between 0 and the
Demand Limiting max delay time you specify.
Maximum Delay You can type the quantity directly into the text box.
Clicking the up or down arrows will adjust the
quantity by 5 seconds.
The range for the maximum delay is 0 to 1275
seconds.
You can specify the number of a demand limiting
operation can be performed within the demand
Demand Limiting
limit lockout period. If the number of demand
Lockout Count
limiting operations is met or exceeded during a
lockout period, the service control switch will be

34
TM42-3060

permanently opened. To close a permanently


opened switch requires a command to be sent by
the head-end system or by Metercat (see Connect
Service).
The meter can be figured to restrict the number of
Demand Limiting demand limiting operations in a period (specified in
Lockout Period hours). Select the demand limiting lockout period
from the hours listed in the drop box.

DISPLAY COMPONENT
The Display component allows you to configure the display items on
the REXUniversal meter's LCD. You can control how long the items
remain on the display, the format of demand quantities, and the
format of energy quantities.

Display settings
Item Description
Controls how long each item is lit on the display. You can set
On Time
the display time to be between 1 second and 15 seconds.
(seconds)
The default is 2 seconds.
Specifies the format of the meter's demand quantities. You
Number of
can choose between a 5-digit format (###.##) or a 6-digit
Demand Digits
format (###.###). The default is 6 digits.
Specifies the format of the meter's energy quantities. You
Number of
can choose to display 4 digits, 5 digits, or 6 digits. The
Energy Digits
default is 6 digits.
Show Total When checked, the meter will light the Total indicator when
("TOT") the quantity displayed on the LCD is a total energy value.
Annunicator The default is checked.

Display items
You can specify the number of items in the meter's display table and
which quantities the meter will display. When the meter is operating
normally, the meter will scroll through all the programmed display
items in sequence before beginning the cycle again with the first item
specified. Normally, the first items is the LCD test which turns on all
the display segments. The LCD test provides a quick way to
determine of the LCD is functioning properly.
The number of items can be within the range of 1 to 70 items. As you
specify the number of items, Metercat will automatically add or
remove the appropriate number drop boxes for the display items.

Note: Instantaneous quantities always display the most currently


retrieved values and do not update during the time the item is
displayed on the LCD.
The following items can be selected to be displayed on the LCD:
 LCD test
 Error codes

35
Components and programs

 Status 1 codes
 Status 2 codes
 Status 3 codes
 Switch/relay status
 Current time and tier
 Summation 1 total data
 Summation 1 Tier A data
 Summation 1 Tier B data
 Summation 1 Tier C data
 Summation 1 Tier D data
 Summation 2 total data
 Summation 2 Tier A data
 Summation 2 Tier B data
 Summation 2 Tier C data
 Summation 2 Tier D data
 Summation 3 total data
 Summation 4 total data
 Demand 1 total data
 Demand 1 Tier A data
 Demand 1 Tier B data
 Demand 1 Tier C data
 Demand 1 Tier D data
 Demand 2 total data
 Demand 2 Tier A data
 Demand 2 Tier B data
 Demand 2 Tier C data
 Demand 2 Tier D data
 Current date
 Instantaneous RMS voltage - Phase A
 Instantaneous RMS current - Phase A
 Instantaneous kW - Phase A
 Instantaneous kVAR - Phase A
 Instantaneous kVA - Phase A
 Instantaneous RMS voltage - Phase C
 Instantaneous RMS current - Phase C

36
TM42-3060

 Instantaneous kW - Phase C
 Instantaneous kVAR - Phase C
 Instantaneous kVA - Phase C
 Meter firmware version.revision
 Comm. controller firmware version.revision
 ZigBee firmware version.revision
 Option board 1 firmware version.revision
 Option board 2 firmware version.revision
The REXUniversal meter supports special display items. For example,
if an option board needs to display data, it can use a special display
item to display it on the meter's LCD. The meter supports up to 8
special display items. See REXUniversal meter special display items
for more information.

DNP COMPONENT
The DNP component allows you to configure the DNP slave running in
the IP AxisLink router.

Note: Detailed information on configuring the IP AxisLink router


for a slave DA device is located in the IP AxisLink router
installation and administration manual (TM42-4002). If you do
not have a copy of the manual, contact your Elster
representative to request one.

EVENT LOG CONFIGURATION COMPONENT


You can use this component to configure which events are recorded
in either the IP AxisLink device or the REXUniversal meter. Because
each meter family has different capabilities, you must select the
desired meter family when creating an event log configuration from
the start.

IP AxisLink device event log


Using the Event Log Configuration component, you can specify which
of the following events will be recorded in the device's event log:
 Device power up
 Device power down
 Time changed (old time)
 Time changed (new time)
 Digital input 1 transitioned high
 Digital input 1 transitioned low
 Digital input 2 transitioned high
 Digital input 2 transitioned low
 Digital input 3 transitioned high

37
Components and programs

 Digital input 3 transitioned low


 Digital input 4 transitioned high
 Digital input 4 transitioned low
 Digital output 1 driven high
 Digital output 1 driven low
 Digital output 2 driven high
 Digital output 2 driven low

REXUniversal meter event log


The Event Log Configuration component allows you to specify and
configure the events that the REXUniversal meter will record in its
event log when the event is detected.

REXUniversal connectivity

Select the type of network the REXUniversal meter is a part of:


 Select Third-Party Network if your REXUniversal meter is part of
a network that connects to a WAN-enabled device using a
protocol other than C12.22
 Select C12.22 WAN Connected if your REXUniversal meter is
part of a network that uses the C12.22 protocol for WAN-enabled
devices
 Select EnergyAxis LAN Connected if your REXUniversal meter is
part of the EnergyAxis 900 MHz mesh network
 Select SynergyNet IP Connected if your REXUniversal meter is
part of the IPv6 900 MHz mesh network

Depending on the connectivity you select, different panels may be


displayed or removed.

Thresholds configuration

Connectivity: All

Item Description
If the meter detects the specified value or
Reverse energy threshold greater number of received energy pulses in a
(Kh count) demand interval, the meter will indicate a
reverse energy event. The default 100 pulses.
The number of attempts to access the meter or
execute a task with insufficient or invalid
Security access threshold password that will indicate a tamper attempt
detected. The security access threshold
monitors both the optical port as well as radio.
Enable warning The warning temperature threshold is the
temperature exceeded temperature (in degrees Celsius) at which the
threshold meter will set the warning temperature

38
TM42-3060

exceeded status flag. By default, the warning


temperature threshold is not enabled. To enable
the threshold, check this box. Once checked,
you can set the warning temperature threshold.
Warning temperature
threshold (C)
NoteIf the service
disconnect temperature is
also enabled, the warning
The meter's temperature, in degrees Celsius
temperature threshold
from +15 °C to +126 °C (default = 50 °C), that
must be lower than the
will set the warning temperature exceeded
disconnect temperature
status flag.
threshold. Metercat will not
allow you to save the
component if the warning
temperature value is set
incorrectly.
The service disconnect temperature threshold is
the temperature (in degrees Celsius) at which
the meter will set the service disconnect
temperature exceeded status flag and will open
Enable service disconnect
the service control switch. By default, the
temperature threshold
service disconnect temperature threshold is not
enabled. To enable the threshold, check this
box. Once checked, you can set the service
disconnect temperature threshold.
Service disconnect
temperature threshold (C)
NoteIf the warning
temperature is also
enabled, the service
The meter's temperature, in degrees Celsius
disconnect temperature
from +16 °C to +127 °C (default = 85 °C), that
threshold must be higher
will set the service disconnect temperature
than the warning
exceeded status flag and will open the service
temperature threshold.
control switch.
Metercat will not allow you
to save the component if
the service disconnect
temperature value is set
incorrectly.

DC current detection

Connectivity: All

The meter can be programmed to check for the presence of DC


current.
Item Description
You can enable or disable the meter's DC
Mode
current detection.
For each phase, the current must be above this
Low current threshold (% of
threshold (a percentage of the Class amps) for
Class amps)
the meter to indicate a DC current event.

39
Components and programs

For each phase, if the minimum per phase


current is exceeded, the meter computes the
ratio of the second harmonic current to the total
2nd harmonic current current and compares the result to this
threshold (% total current) threshold. If this threshold is met or exceeded, a
DC current event is indicated.

To prevent the monitor from creating a false


alarm from legitimate second harmonic current
sources, the recommended qualification time is
Qualification time 15 minutes. The range between 1 minute and
255 minutes. If a power failure occurs once the
timer has started, the timer is reset at the power
failure.

Magnetic tamper detection

Connectivity: All

The meter performs a per phase periodic check for magnetic tamper.
Item Description
You can specify the operating mode for the
meter's magnetic tamper detection:

Disabled: the meter does not check for


magnetic tamper.
Mode
Enabled for Q2 and Q4: the meter checks for
magnetic tamper on the 2nd and 4th quadrant.
Enabled for Q4 only: the meter only checks for
magnetic tamper on the 4th quadrant.

For each phase, the current must be above this


Low current threshold (% of threshold (a percentage of the Class amps) for
Class amps) the meter to indicate a magnetic tamper
detection event.
For each phase, if the minimum per phase
current is exceeded and the power factor is
leading, the meter compares the per phase
Power factor threshold
power factor to this threshold. If the calculated
value is less than or equal to the threshold,
magnetic tampering is detected.
The test must fail for a period exceeding this
timer. The recommended qualification time is
15 minutes. The range between 1 minute and
Qualification time
255 minutes. If a power failure occurs once the
timer has started, the timer is reset at the power
failure.

Outage notification configuration

Connectivity: EnergyAxis LAN connected; SynergyNet IPv6 connected

40
TM42-3060

Note: The outage notification delay only controls how long the meter
will delay broadcast of the outage notification message. The outage
notification time does not affect the momentary outage time (see
Voltage Monitoring component).
Item Description
By default, the REXUniversal meter will send an
outage notification broadcast message over the
Enable outage notification
900 MHz mesh network. To disable outage
notification, clear the check box.
If outage notification is enabled, you can specify
how many seconds the meter will wait before
sending the broadcast message. If power is
restored during this delay period, the meter will
not send the outage message.
Outage notification delay
You may select 0, 30, 60, or 120 as the length
(s)
of the delay time in seconds. If you select 0, the
meter will immediately broadcast an outage
notification message after every outage
regardless of the duration. The default time is
120 seconds.
By default, the REXUniversal meter will send a
Enable restoration power restoration broadcast message over the
notification 900 MHz mesh network. To disable restoration
notification, clear this check box.
If restoration notification is enabled, the meter
may be configured to delay for a number of
seconds before transmitting the restoration
Restoration notification message. This delay can allow for recloser
delay (s) operation.
You may select 32, 128, or 320 as the length of
the delay time in seconds. The default time is
32 seconds.

Metrology Events logged

Connectivity: All

The meter supports 1 event log for the metrology processor events. If
you select which events are recorded, they are recorded in the
metrology event log. If an item is checked, it will be recorded in the
metrology event log if it is detected. If an item is unchecked, it will
not be recorded if it is detected. The REXUniversal supports the
recording of the following events. For some of the items (as indicated
in the list below), the thresholds are set in the Event Log
Configuration component.
If the meter is network connected, you can select which conditions
may also place a call-in (see "Call-in Hosts and Events" below). For an
event to place a call-in, it must be selected as an event to be logged.
 Primary power down
 Primary power up

41
Components and programs

 Time change (old time)


 Time change (new time)
 Reset list points
 Event log cleared
 Demand reset occurred
 Season change
 Test mode started
 Test mode stopped
 Nonvolatile memory failure detected
 Clock error detected
 Measurement error detected
 Tilt detected
 Reverse energy detected
o The reverse energy threshold is set in the Thresholds
Configuration panel
 Enter tier override
 Exit tier override
 Remote flash fail
 Metrology firmware changed
 Communications firmware changed
 ZigBee firmware changed
 Option 1 firmware changed
 Option 2 firmware changed
 Configuration table write
 Seed changed
 EnergyAxis LAN encryption key changed
 Optical port lockout
 Disconnect switch opened
 Disconnect switch closed
 Load side voltage present
 Load side voltage not present
 Meter configuration changed
 Configuration error detected
 Table access warning
 Authentication service failure
 Voltage monitoring: Phase A minimum voltage

42
TM42-3060

 Voltage monitoring: Phase C minimum voltage


 Voltage monitoring: Phase A maximum voltage
 Voltage monitoring: Phase C maximum voltage
 Voltage monitoring: Phase A normal voltage
 Voltage monitoring: Phase C normal voltage
 Coincidental values: Phase A voltage
 Coincidental values: Phase C voltage
 Coincidental values: Phase A demand
 Coincidental values: Phase C demand
 DC current detected
o The parameters for DC current detection are set in the DC
Current Detection panel
 Magnetic tamper detected
o The parameters for magnetic tamper detection are set in the
Magnetic Tamper Detection panel
 End of calendar detected
 Warning temperature exceeded
o The temperature threshold is set in the Thresholds
Configuration panel
o Note: The meter will not log exceeding the threshold if you
disable the warning temperature in the Thresholds
Configuration panel.
 Power fail data save error
 Table CRC error
 Service disconnect temperature exceeded
o The temperature threshold is set in the Thresholds
Configuration panel
o Note: The meter will not log exceeding the threshold if you
disable the service disconnect temperature in the
Thresholds Configuration panel.
 WIC firmware upgrade failed
 Communications firmware upgrade failed

Communication (COMMS) events

Connectivity: C12.22 WAN; EnergyAxis LAN; SynergyNet IPv6

The meter supports 2 COMMS event logs for the communications


events.

43
Components and programs

 If you are using C12.22 WAN or EnergyAxis LAN connectivity,


using the drop menu, you can select the following for each
possible event
o Log A: the event will be recorded in Log A when it is detected
o Log B: the event will be recorded in Log B when it is
detected
o Disabled: the event will not be recorded when it is detected
 If you are using SynergyNet IPv6 connectivity, check the box for
each item you wan to record. Clear the box for each item you do
not want recorded.
For C12.22 WAN connected devices, you can also select which
conditions may also place a call-in (see "Call-in Hosts and Events"
below). For an event to place a call-in, it must be selected as an
event to be logged. For SynergyNet IPv6 connected devices, you can
also select which conditions can send an event-based notification
(see "High Priority Notification Events" below).
The REXUniversal supports the recording (and possible call in
notification) of the following communications events:
 reset list pointers
 event log cleared
 nonvolatile memory failure detected
 configuration table write
 EnergyAxis LAN encryption key changed
 meter configuration changed
 configuration error detected
 table access warning
 authentication service failure
 power fail data save error
 table CRC error
 900 MHz radio enabled
 900 MHz radio disabled
 C12.22 key reverted to factory
 C12.22 key activation failure
 C12.22 key distribution failure

Call-in hosts and events

Connectivity: C12.22 WAN

The REXUniversal meters supports placing call ins to an exception


host. The meter can report up to 64 events. If the REXUniversal
connectivity is set to Third-Party, then the meter cannot place call ins.

44
TM42-3060

Item Description
Check the box to enable call-in messages
Enable call-in messages to the exception host. Clear the box to
disable call-in messages.

Exception host
Item Description
AP Title Enter the AP title for the host.
IP address Enter the IP address for the host.
Enter the network port for the
Exception port
host.
Specify how many times the meter
will attempt to reach the host
Max number of tries before failing. You may specify
between 0 (the meter will not
retry) to 255.
Specify how long the meter will
wait (in minutes) before
Retries delay (min) attempting another call in. You
may specify a time between 0
minutes and 65,535 minutes.
The exclusion period is the
specified time (in minutes) that
the meter ignores subsequent or
repeated events after the first
Exclusion period (min) event is detected. Once the
exclusion period expires, any event
will start a new exclusion period.
You may specify a time between 0
minutes and 65,535 minutes.

Primary power down advanced options


If you selected primary power down as one of the metrology events
that are logged, there are advanced settings you can configure if you
need to make adjustments to the network load. These settings
should be changed in consultation with your Elster support
representative.
Parameter Description
Initial reply time (sec) Default: 5; Range: 0 to 255
Incremental reply time (sec) Default: 15; Range: 0 to 255
Number of retries Default: 3; Range 0 to 255
Random backoff factor (sec) Default: 2; Range: 0 to 255

Select the events to be sent to this host


You can select up to 64 event types that can be sent to the host. You
can specify any combination of metrology events and
communications events. As you specify the number of items,
Metercat will automatically add or remove the appropriate number of
drop boxes for the event types.
Notes:

45
Components and programs

 The selected event types must also be selected as a logged


event; otherwise, Metercat will not allow you to save the
component.
 If you want to report primary power events (for example, primary
power down or primary power down), you must select both
primary power events. Metercat will not allow you to save the
component if you attempt to report only one type of primary
power event.

High priority notification events

Connectivity: SynergyNet IPv6


Using Metercat, you define what metrology and COMMS events are
high priority.
Whether or not a high priority event triggers a notification message is
configured within Connexo NetSense. If high priority events are
configured to trigger a message, then this panel determines which
events are high priority.
Metercat presents a set that is a combination of the metrology
events and the COMMS events. You can select up to 64 items from
this combined list as high priority. Using the text box, specify the
number of events to be sent. For an event to be high priority, it must
be selected in metrology events and COMMS events above and then
selected as a high priority event here. Metercat will not allow you to
save the component if you attempt to select an event for notification
that is not also selected for being logged.

See also
SynergyNet notification

EVENT NOTIFICATIONS COMPONENT


The IP AxisLink router supports event notifications over the WAN
connection. In the Exception Port box, enter the port used for
notifications. The range is 0 to 65535, with the default of 1153.
You can specify the number of exception hosts, from 0 to 4, in the
Number of Exception Hosts box. For each exception host you
specify, Metercat will display the configuration options for each.
Item Description
AP Title Specify the AP title for the host.
IP Address Type the IP address for the host.
The range can be between 0 and
Max number of retries
255; the default is 3.
The range can be between 0 and
Retry delay (minutes)
65535; the default is 1.

46
TM42-3060

The range can be between 0 and


Exclusion period
65535; the default is 0.
Each host can support up to 16 event
Number of exception types to report types; for each host, specify the
number of exception types to report.
For each exception type selected
above, select the event from the list
of events. Notification is available for
the following events. In addition, the
router's gatekeeper module can
report the following events.

IP AxisLink router gatekeeper module


events:

 MFG meter event call


 LANOB diagnostic
 LANOB immediate call
 LANOB status call
 LANOB scheduled call
 LANOB power restoration
 LANOB power outage

IP AxisLink router notification events:

 No event
Exception event
 Device power down (requires
backup power supply)
 Device power up (requires
backup power supply)
 Time changed (old time)
 Time changed (new time)
 Procedure invoked
 Configuration changed
 Event log cleared
 Daylight Saving Time on
 Daylight Saving Time off
 Pending table activation
 Pending table clear
 Configuration error detected
 ROM failure detected
 Nonvolatile memory failure
detected

47
Components and programs

 Clock error detected


 Security log entry made
 Clock change by C12.19
 Clock change by DNP3.0
 Clock change by SNTP
 Clock change by web
 Device reboot occurred
 Device firmware updated
 Diagnostic test event
 Primary power down (requires
backup power supply)
 Primary power up (requires
backup power supply)
 EEPROM memory initialized
 Nonvolatile memory initialized
 Digital input 1 transitioned high
 Digital input 1 transitioned low
 Digital input 2 transitioned high
 Digital input 2 transitioned low
 Digital input 3 transitioned high
 Digital input 3 transitioned low
 Digital input 4 transitioned high
 Digital input 4 transitioned low
 Digital output 1 driven high
 Digital output 1 driven low
 Digital output 2 driven high
 Digital output 2 driven low

INSTRUMENTATION PROFILING COMPONENT


The Instrumentation Profiling component allows you to configure the
meter's instrumentation profiling capability. Each meter family has
different capabilities, as described in this topic.

A3 ALPHA meter instrumentation profiling

48
TM42-3060

The A3 ALPHA meter can record two sets, and each set can record up
to 16 channels. Each channel can be configured to record the
instrumentation profiling using any one of the following algorithms:
Item Description
The meter samples the selected quantity over the
Minimum instrumentation interval. The minimum value of all
the samples is recorded.
The meter samples the selected quantity over the
Maximum instrumentation interval. The maximum value of all
the samples is recorded.
The meter samples the selected quantity over the
Average instrumentation interval. The average value of all
the samples is recorded.
The meter samples the selected quantity over the
End instrumentation interval. The last value of all the
samples is recorded.

Each set of instrumentation profiling has its own, separate interval


length that is configured independently from the demand interval
length. The length of the instrumentation profiling interval must
adhere to the following rules:
 the length must be between 1 minute and 60 minutes
 the time must be evenly divisible into 60 minutes
Metercat allows you to only select the Interval Length that meets
these criteria.

Instrumentation profiling quantities:

 frequency
 per phase current
 per phase voltage
 per phase watts
 per phase VA
 per phase voltage angle with respect to Phase A voltage
 per phase fundamental (1st harmonic) current magnitude
 per phase fundamental (1st harmonic) voltage magnitude
 per phase 2nd harmonic current magnitude
 per phase 2nd harmonic voltage magnitude
 per phase voltage percent THD
 per phase current percent THD
 per phase harmonic current (sum of 2nd through 15th)
 system watts
 system VA (arithmetic)

49
Components and programs

 per phase PF
 system PF (arithmetic)
 per phase PF angle
 system PF angel (arithmetic)
 per phase current angle with respect to phase A voltage
 per phase VARs (vectorial)
 system VARs (vectorial)
 system VA (vectorial)
 system VAR (arithmetic)
 system PF (vectorial)
 system PF angle (vectorial)
 per phase 2nd harmonic voltage percent
 per phase TDD

A1800 ALPHA meter instrumentation profiling


The A1800 ALPHA meter can record two sets of instrumentation
profiling, and each set can record up to 16 channels. Each channel
can be configured to record the instrumentation profiling using any
one of the following algorithms:
Item Description
The meter samples the selected quantity over the
Minimum instrumentation interval. The minimum value of all
the samples is recorded.
The meter samples the selected quantity over the
Maximum instrumentation interval. The maximum value of all
the samples is recorded.
The meter samples the selected quantity over the
Average instrumentation interval. The average value of all
the samples is recorded.
The meter samples the selected quantity over the
End instrumentation interval. The last value of all the
samples is recorded.

Each set of instrumentation profiling has its own, separate interval


length that is configured independently from the demand interval
length. The length of the instrumentation profiling interval must
adhere to the following rules:
 the length must be between 1 minute and 60 minutes
 the time must be evenly divisible into 60 minutes
Metercat allows you to only select the Interval Length that meets
these criteria.

Instrumentation profiling quantities

50
TM42-3060

In meters with instrumentation profiling (designated with an N suffix),


the meter has two sets of instrumentation profiling. Each set can
record up to 16 channels of sources listed below. Also,
instrumentation profiling can use the sources for the A1800 ALPHA
meter's interval data record for more extensive profiling recording
(see Metering component for the A1800 ALPHA meter's interval data
quantities).
 frequency
 per phase current
 per phase voltage
 per phase watts
 per phase VA
 per phase voltage angle with respect to Line 1 voltage
 per phase fundamental (1st harmonic) current magnitude
 per phase fundamental (1st harmonic) voltage magnitude
 per phase 2nd harmonic current magnitude
 per phase 2nd harmonic voltage magnitude
 per phase voltage percent THD
 per phase current percent THD
 per phase harmonic current (sum of 2nd through 15th)
 per phase current angle with respect to Line 1 voltage
 per phase vars (vectorial)
 per phase 2nd harmonic voltage percent
 per phase TDD
 per phase PF
 per phase PF angle
 system watts
 system VA (arithmetic)
 system PF (arithmetic)
 system PF angle (arithmetic)
 system vars (vectorial)
 system VA (vectorial)
 system vars (arithmetic)
 system PF (vectorial)
 system PF angle (vectorial)

REXUniversal instrumentation profiling


The REXUniversal meter can record 1 set of up to 4 channels of
instrumentation profiling data. Each channel can be configured to

51
Components and programs

record the instrumentation profiling using any one of the following


algorithms:
Item Description
The meter samples the selected quantity over the
Minimum instrumentation interval. The minimum value of all
the samples is recorded.
The meter samples the selected quantity over the
Maximum instrumentation interval. The maximum value of all
the samples is recorded.
The meter samples the selected quantity over the
Average instrumentation interval. The average value of all
the samples is recorded.
The meter samples the selected quantity over the
Snapshot instrumentation interval. The last value of all the
samples is recorded.

Instrumentation profiling has its own, separate interval length that is


configured independently from the demand interval length. The
length of the instrumentation profiling interval must be 5 minutes, 15
minutes, 30 minutes, or 60 minutes.

Instrumentation profiling quantities

As you specify the number of channels, Metercat will automatically


add or remove the appropriate number drop boxes for the quantity
and algorithm.
The REXUniversal meter supports voltage profiling.

Note: Only REXUniversal Form 12S meters have a Phase C. If


Phase C voltage is programmed into a non-12S meter, the meter
will report a value of zero for the channel in the Instrumentation
Profiling view.

LOAD PROFILE COMPONENT


This component allows you to configure the load profiling capability
of the A3 ALPHA meter or REXUniversal meter..

Note: Load profiling is only available on timekeeping meters with


the load profiling capability enabled. A3D meters do not support
load profiling.

A3 ALPHA meter load profiling

Meter Type
When you create a load profile component, you must first specify the
meter type you want to create this component for. You must select
from the following options:
 D/T for A3TL meters
 K for A3KL meters
 Q for A3QL meters

52
TM42-3060

 R for A3RL meters

Each meter type supports different metered quantities. See A3


ALPHA meter types for an overview of meter types.

Days of storage
Using Metercat, you can select Maximize to configure the meter to
log the maximum number of days possible. This will be determined
by the meter based on available memory when the program is
written. The function completion report will indicate the actual
number of days the meter will record. Alternatively, you can specify
the number of days manually from zero (which disables load
profiling in the meter) to 999. See Estimated load profiling days for a
discussion on how many days the meter may be capable of recording
based on different parameters.
All A3 ALPHA meters are equipped with EEPROM. The main board
storage may be 64 KB or 128 KB. A small portion of EEPROM is
permanently reserved (called "reserved memory") by the meter to
store the main billing and configuration information. The reminder of
the memory, called "shared memory," is used to store the following
logs and data sets:
 event log
 history log
 self reads
 PQM log
 voltage sag log
 load profiling
 instrumentation profiling

All of the logs and data sets share the meter's memory. The sizes of
each may vary to allow more room for a different log or data set. For
example, self reads can store less data so that load profiling can
store more data. If more memory is required, an optional extended
memory option board can be used to provide up to 1 MB of space for
shared memory.

Interval length
Load profiling has its own, separate interval length that is
configured independently from the demand interval length. You can
select the number of minutes for the load profiling interval from the
drop list, which are all the minutes that can be evenly divisible into
an hour.

Pulse Divisor
You can specify a pulse divisor value in the range of 1 (default) to
255.

53
Components and programs

Each load profiling interval can store up to 32,767 pulses before


overflowing. By default, the meter counts one pulse per Ke. A pulse
divisor is used to scale down the number of pulses stored in each
load profiling interval. This allows recording of data that may
otherwise exceed the maximum number of pulses that can be stored
in each load profiling interval.

Quantities to Record
The A3 ALPHA meter is capable of recording up to 8 channels of
information, depending on its meter type (see the following table).
Data is stored as pulse counts proportional to energy accumulated
during the load profiling interval.
 A3TL meters can record up to 2 quantities of information
 A3KL, A3QL, and A3RL meters can record up to 8 quantities of
information

As you select a quantity to record, Metercat will automatically enable


the next drop list.

Quantity A3TL A3KL A3QL A3RL


kWh delivered • • • •
kWh received • • • •
kWh sum • • • •
kWh net • • • •
kVAh delivered • •
kVAh received • •
kVAh sum • •
kVAh net •
kVAh Q1 •
kVAh Q2 •
kVAh Q3 •
kVAh Q4 •
kQh delivered •
kQh received •
kQh sum •
kVARh delivered •
kVARh received •
kVARh sum •
kVARh net •
kVARh Q1 •
kVARh Q2 •
kVARh Q3 •
kVARh Q4 •
kVARh (Q1 + Q4) • •
kVARh (Q2 + Q3) • •
kVARh (Q1 - Q4) •

54
TM42-3060

kVARh (Q2 - Q3) •


kVARh (Q3 - Q2) •

REXUniversal meter load profiling


The REXUniversal supports up to 4 channels of load profiling. The
channel sources are the same as the summations (configured in the
Metering component). The first summation quantity is used for the
first channel of load profiling; the second summation quantity is used
for the second channel of load profiling; and so on. To disable load
profile, set the number of channels to 0.
The interval length can be 5, 15 (default), 30, or 60 minutes.
You can configure a pulse divisor between 1 and 255. The same
pulse divisor is used for all channels of load profile.

LOGS COMPONENT
Meters are equipped with EEPROM. A small portion of this main
board memory is permanently reserved (called "reserved memory")
by the meter to store the main billing and configuration information.
The remainder of the memory (called "shared memory") is used to
store the logs and data sets. The Logs component allows you to
configure most of the meter's logs and data sets (with the exception
of load profiling/interval data).
 event log
 history log
 self reads
 load profiling (A3 ALPHA)/interval data (A1800 ALPHA meter)
 instrumentation profiling
 PQM log (A3 ALPHA)/TRueQ log (A1800 ALPHA)
 voltage sag log
All of the logs and data sets share the meter's memory. The sizes of
each log or data set can be configured to allow more room for a
different log or data set. For example, self reads can be configured to
store less data so that the instrumentation profiling can store more
data.

A3 ALPHA meter logs

Logs configuration

The Logs component allows you to configure the following logs and
data sets recorded by the meter:
Log/data set Number of entries

55
Components and programs

Event log zero to 255; default = 50


History log zero to 255; default = 50
Sag log
* requires meters with
zero to 255; default = 50
the Q suffix in the meter
type
PQM log
* requires meters with
40 to 255; default = 40
the Q suffix in the meter
type
Self reads zero to 15; default = 5

Beginning with A3 ALPHA meter firmware version 5.0, the meter's


event log can also record when the meter's temperature exceeds a
threshold as well as display the F4 400000 warning code on the
LCD. Also beginning with meter firmware version 5.0, the meter's
event log can also record a momentary outage based on a user
configurable time. See the Event Configuration section of this topic to
enable or disable the events that can be recorded in the event log.
Item Description
Temperature Threshold The meter's temperature, in degrees Celsius, from
(C) +50 °C to +127 °C; default = 85 °C.
The threshold time in seconds to differentiate a
momentary outage from a sustained outage. If the
outage falls below or is equal to the threshold, it is
Momentary outage time a momentary outage. If the outage exceeds the
threshold threshold, it is a sustained outage.
The threshold time may be within a range of 1
second to 65,535 seconds; the default is 60
seconds.

Phase outage configuration

Beginning with A3 ALPHA meter firmware version 4.4, the meter's log
can record power loss and power restoration on a per phase basis.
Item Description
The qualification time (in seconds) that the phase
must have lost power before the event will be
Phase Loss Time (s) recorded in the event log. The range can be
between 0 seconds (where every phase loss is
logged) to 545 seconds.
The qualification time (in seconds) that the phase
must have had power restored before the event will
Phase Restoration Time
be recorded in the event log. The range can be
(s)
between 0 seconds (where every phase restoration
is logged) to 545 seconds.

Event configuration

The Event Configuration panel allows you to decide which events are
actually recorded in the event log. If an item is checked, it will be
recorded in the event log if the event is detected; if an item is
unchecked, it will not be recorded if it is detected. Different firmware

56
TM42-3060

versions of the A3 ALPHA meter support different recording of


events, as shown in the following table.
FW
FW FW
1.x FW
Event 5.0 & 6.0 &
to 4.4
later later
4.3
Primary power up • • • •
Primary power down • • • •
Time changed (old time) • • • •
Time changed (new time) • • • •
End device programmed • • • •
History log cleared • •
Event log cleared • • • •
Demand reset occurred • • • •
Self read occurred • • • •
Season change • •
Rate change • •
Pending table activated • •
Test mode started • • • •
Test mode stopped • • • •
End device reprogrammed • •
Configuration error detected • •
RAM failure detected • •
Nonvolatile memory failure detected • •
Clock error detected • •
Measurement error detected • •
Tamper attempt detected • •
Reverse rotation detected • •
Tier override entered • • • •
Tier override exited • • • •
External event 0 signalled • • • •
External event 1 signalled • • • •
External event 2 signalled • • • •
External event 3 signalled • • • •
Phase A voltage not active • • •
Phase A voltage active • • •
Phase B voltage not active • • •
Phase B voltage active • • •
Phase C voltage not active • • •
Phase C voltage active • • •
Remote flash failed • • •
Metrology firmware changed • •
DA I/O binary input 1 activated • • •
DA I/O binary input 2 activated • • •
DA I/O binary input 3 activated • • •
DA I/O binary input 4 activated • • •
DA I/O binary output contact K1 closed • • •

57
Components and programs

DA I/O binary output contact K2 closed • • •


DA I/O binary output contact K1 opened • • •
DA I/O binary output contact K2 opened • • •
Unauthorized requests • •
End device reprogram error • •
Optical port disabled • •
Optical port enabled • •
Temperature threshold exceeded • •
Disconnect switch opened optically
(Service control switch open optically)

Disconnect switch closed optically
(Service control switch closed optically)

Disconnect switch opened remotely
(Service control switch opened remotely)

Disconnect switch closed remotely
(Service control switch closed remotely)

Optical access successful (noteIf selected,
the meter will record an event in the event
log for every optical port attempt that is •
successful (even those that are authorized
by the utility).)
Optical access failure (noteIf selected, the
meter will record an event in the event log
for every optical port attempt that fails •
(even those that are authorized by the
utility).)
Phase A reverse polarity detected begin •
Phase A reverse polarity detected end •
Phase B reverse polarity detected begin •
Phase B reverse polarity detected end •
Phase C reverse polarity detected begin •
Phase C reverse polarity detected end •

See also
See Estimated load profiling days for a discussion on how many days
the meter may be capable of recording based on different
parameters.

A1800 ALPHA meter logs

Logs configuration

The Logs component allows you to configure the following logs and
data sets recorded by the meter:
Log/data set Number of entries
Event log zero to 255; default = 50
History log zero to 255; default = 50
Sag log zero to 255; default = 50
TRueQ/PQM log 40 to 255; default = 40

58
TM42-3060

Self reads zero to 35; default = 5

Event log contents

The Event Configuration panel allows you to decide which events are
actually recorded in the event log. If an item is checked, it will be
recorded in the event log if the it is detected; if an item is unchecked,
it will not be recorded if it is detected.
 Demand reset
 Power fail (the time before and after the event)
 Time change (the time before the time change and after the time
change)
 Test mode (the time the test mode started and the time the test
mode stopped)
 Phase outage
o Phase loss time: The qualification time (in seconds) that the
phase must have lost power before the event will be
recorded in the event log. The range can be between 0
seconds (where every phase loss is logged) to 545 seconds.
o Phase restoration time: The qualification time (in seconds)
that the phase must have had power restored before the
event will be recorded in the event log. The range can be
between 0 seconds (where every phase restoration is
logged) to 545 seconds.
 Terminal cover removal detection
o Terminal cover tamper exclusion: The time (in minutes) that
the terminal cover can be removed before the event is
logged in the event log. The range can be between zero and
255 minutes. A time of zero means any removal will be
flagged as an event.
 Main cover opening detection
o Main cover tamper exclusion: The time (in minutes) that the
main cover can be removed before the event is logged in the
event log. The range can be between zero and 255 minutes.
A time of zero means any removal will be flagged as an
event.

See also
See Estimated load profiling days for a discussion on how many days
the meter may be capable of recording based on different
parameters.

LOSS COMPENSATION COMPONENT


Using the Loss Compensation component, you can configure the
meter to actively adjust the energy registration to account for any
losses in a transformer. For example, it may be desirable to measure
the energy usage on the low voltage side of a distribution

59
Components and programs

transformer that serves an industrial customer even though the end-


point customer actually owns the transformer and is responsible for
any transformer losses. In this case, the utility billing point is actually
the high voltage side of the transformer. Using loss compensation,
the meter on the low voltage side of the transformer can actively
adjust the energy registration to account for the losses in the
transformer.
See About transformer and line loss compensation for more
information.
To control loss compensation within the meter:
 Check the Turn Loss Compensation On box to enable loss
compensation within the meter based on the parameters set in
the component.
 Clear the Turn Loss Compensation On box to disable loss
compensation within the meter.

You can also turn loss compensation on or turn it off by using the
appropriate tasks. This allows you to enable or disable loss
compensation without reprogramming the meter.
You can program loss compensation into a meter that does not have
the loss compensation key enabled. The meter will store the
compensation values for future use. Once the loss compensation key
has been enabled through AlphaKeys software, the meter will
automatically start the loss compensation algorithms based on the
stored values.

General configuration
Regardless of whether you are compensating for power transformer
or line loss compensation (or both), you must have the following
information entered into the component for the calculation to be
correct:
Item Description
 Enable: Configures the
meter to maintain loss
compensation when the
meter enters test mode.
 Disable: Configures the
meter to automatically turn
off loss compensation
Loss compensation in test when the meter enters test
mode mode. Loss compensation
will automatically resume
once the meter exits test
mode.
See Testing a meter with
compensation for more
information.
Calculation of loss
Meter applied to
compensation parameters

60
TM42-3060

depends on the meter location


with respect to the
transformer. The rated voltage
and rated current used in
calculations must represent
the values on the same side of
the transformer as the meter
is located.

 Primary side: the meter is


located on the primary side
of the transformer. Rated
voltage and rated current
used in calculations must
be primary values.
 Secondary side: the meter
is located on the secondary
side of the transformer.
Rated voltage and rated
current used in
calculations must be
secondary values.
 Add losses: adds the
compensation values to
the registration data
 Subtract losses: subtracts
Registration the compensation values
from the registration data
See Internal meter
calculations for more
information.
Select the application for the
service location.

Application  4WY (3-element)


 3WD (2-element)
 4WY (2½-element)
 Open 3WD (2 element)
Type the instrument
transformer's CT primary
ampere value and the CT
secondary ampere value in the
Instrum transformer primary
appropriate text boxes, and
current (A)
Metercat will automatically
Instrum transformer secondary
compute the CT ratio. For
current (A)
correct calculation of loss
CT ratio
compensation, Metercat
requires both the primary and
secondary ampere values of
the CT ratio.
Instrum transformer primary Type the voltage transformer's
voltage (V) VT primary volt value and the
Instrum transformer secondary VT secondary volt value in the
voltage (V) appropriate text boxes, and
VT ratio Metercat will automatically

61
Components and programs

compute the VT ratio. For


correct calculation of loss
compensation, Metercat
requires both the primary and
secondary volt values of the VT
ratio.
Type the power transformer's
Primary L-L Voltage (Power primary line-to-line voltage (Vpri
transformer) L-L) obtained from the power
transformer manufacturer.
Type the power transformer's
secondary line-to-line voltage
Secondary L-L Voltage (Power
(Vsec L-L) obtained from the
transformer)
power transformer
manufacturer.
Type the rated kVA (KVArated)
kVA (Power transformer) value obtained from the power
transformer manufacturer.

Transformer losses configuration


You can use Metercat to configure the meter to compensate for
transformer losses or line losses or both.
 To compensate for power transformer losses, check the
Compensate for Transformer Losses box to enable.
 To disable power transformer compensation, clear the
Compensate for Transformer Losses box.
Item Description
The percentage of the kVA
used in the loss compensation
calculation. The default is
Contract %
100.0, meaning that 100% of
the kVA will be used in the
calculation.
Select the following:

 3-phase transformer
 bank of three 1-phase
Transformer type If there is a bank of three
1-phase transformers,
you will need the test
data for all three.
For each transformer, enter
the LWCu value as stated on
Full load watts loss (copper)
the power transformer test
report.
For each transformer, enter
the LWFe value as stated on
No load watts loss (iron)
the power transformer test
report.
For each transformer, enter
% excitation
the percent excitation current

62
TM42-3060

(%EXC) of the power


transformer.
For each transformer, enter
% impedance the percent impedance (%Z) of
the power transformer.

Line losses configuration


You can use Metercat to configure the meter to compensate for
transformer losses or line losses or both.
 To compensate for power transformer losses, check the
Compensate for Line Losses box to enable.
 To disable power transformer compensation, clear the
Compensate for Line Losses box.

The form will automatically display the different required values


necessary to the calculations depending on the reactance calculation
method selected.
Item Description
Select the nominal line
frequency:
Frequency
 60 Hz
 50 Hz
Select the conductor
resistance (Ra):
Resistance units
 Ohms/1000 feet (Ω/1000
feet)
 Ohms/mile (Ω/mile)
Select one of the following:

 None
 Geometric mean radius
Reactance calculation method (GMR) of the phase
conductors (in feet)
 Inductive reactance (Xa) of
the conductor at 1 foot
spacing
If you are using Xa for the
reactance calculation method,
select the units:
Xa units
 Ohms/1000 feet (Ω/1000
feet)
 Ohms/mile (Ω/mile)

If using GMR

For each conductor, enter the following:

63
Components and programs

Item Description
Line length (L) (units
Line length (feet) compatible with conductor
resistance)
Conductor resistance (Ra)
Resistance
(Ω/mile or Ω/1000 feet)
Distance between phases A The distance between phase A
and B (feet) and phase B (Dab) in feet.
Distance between phases B The distance between phase B
and C (feet) and phase C (Dbc) in feet.
Distance between phases C The distance between phase C
and A (feet) and phase A (Dca) in feet.
The geometric mean radius of
Geometric mean radius (GMR)
the phase conductors (feet)

If using Xa

For each conductor, enter the following:


Item Description
Line length (L) (units
Line length (feet) compatible with conductor
resistance)
Conductor resistance (Ra)
Resistance
(Ω/mile or Ω/1000 feet)
Distance between phases A The distance between phase A
and B (feet) and phase B (Dab) in feet.
Distance between phases B The distance between phase B
and C (feet) and phase C (Dbc) in feet.
Distance between phases C The distance between phase C
and A (feet) and phase A (Dca) in feet.
Inductive reactance of the
conductor at 1-foot
Inductive reactance (Xa) spacing (Ω/mile or Ω/1000
feet)

Calculated losses
After you have d entering all the information, Metercat will perform
the calculations based on the formulas presented in transformer and
line loss compensation section. You can also follow an example of
line loss compensation calculations. The information in this panel is
presented for your informational use.
Item Description
Transformer
Metercat performs the calculation for
Full load watts
LWCu and displays the result.
Metercat performs the calculation for
No load watts
LWFe and displays the result.
Metercat performs the calculation for
Full load VARs
LVCu and displays the result.
Metercat performs the calculation for
No load VARs
LVFe and displays the result.
Line

64
TM42-3060

Metercat performs the calculation for


Full load watts
LiWTOT and displays the result.
Metercat performs the calculation for
Full load VARs
LiVTOT and displays the result.
Total
Metercat adds the transformer LWCu
and line LWCu and displays the sum.
Full load watts
If there is no compensating for line
losses, the line LWCu is 0.
Metercat displays the LWFe value
No load watts that is being used in the configuration
values.
Metercat adds the transformer LVCu
and the line LVCu and displays the
Full load VARs
sum. If there is no compensating for
line losses, the line LVCu is 0.
Metercat displays the LVFe value that
No load VARs is being used in the configuration
values.

Configuration values
Metercat will perform the calculations based on the formulas
presented in transformer and line loss compensation section. When
this component is written to the meter and loss compensation is
turned on, the meter will compensate for transformer and line losses
based on the values displayed in this panel.
Item Description
Iron watts correction % The value of %LWFe.
Copper watts correction % The value of %LWCu
Iron VARs correction % The value of %LVFe
Cooper VARs correction % The value of %LVCu
Meter current (A) The meter current in amperes.
Meter voltage (V) The meter voltage in volts.

METERING COMPONENT

Metering component
The Metering component allows you to configure the following meter
capabilities:
 A3 ALPHA metering component: the metered
quantities and the display items
 A1800 ALPHA metering component: the metered
quantities, the display items, and interval data
configuration (load profiling)
 REX2 meter view: the metered quantities (when
viewing Quantities in viewset)
 REXUniversal metering component: the metered
quantities
Because each meter family has different capabilities, you must
select the meter family first when creating a Metering component
from the start. You may also be prompted to select the meter type.

65
Components and programs

Note: When creating an A3 ALPHA or A1800 ALPHA component


using the New Component dialog box or opening a component
using the Open Component dialog box, the Metering component
contains both the Quantities and Display. If you are using the
Program Editor, Metercat presents the Quantities and Display as
separate components; however, Quantities and Display are
always controlled by the same Metering component.

A3 ALPHA metering component

A3 ALPHA metering component

The metering component for the A3 ALPHA meter has the following
main tabs:
 Quantities tab
 Display tab

When you create a metering component, you must first specify the
meter type you want to create this component for. You must select
from the following options:
 D/T for A3T meters
 K for A3K meters
 Q for A3Q meters
 R for A3R meters
Each meter type supports different metered quantities. See A3
ALPHA meter types for a brief overview of meter types, or see the A3
ALPHA meter technical manual for more information.
You will then be specified to select the program type. Select either
single rate demand or TOU as appropriate for your desired
configuration.

Quantities tab

Metered quantities
The meter supports the recording of up to 1 or 2 quantities, based on
meter type. If the advanced four-quadrant metering option is enabled
in the meter and the Configure for the advanced metering option
is checked, the meter can support up to 6 quantities.

Note: If you attempt to configure a meter with a component it


cannot support (for example, you are attempting to write 6
quantities to a meter that does not have advanced four quadrant
metering), the Program task will fail.
You can also enable or disable load control & overload thresholds (as
a single toggle) per metered quantity. If Apply Load Control &
Overload Thresholds is enabled, the meter will use the thresholds
defined in the Demand component to respond to a demand overload
or activate a load control relay.

66
TM42-3060

Power factor
The A3K and A3R meters can calculate the average power factor.
Average power factor is calculated by the meter using the following
values since the last demand reset:
 kWh
 kVARh or kVAh
Method 1 Method 2
if using kWh and kVAh: if using kWh and kVARh:

The average power factor is calculated every second. The values


used in this calculation will be set to zero at a demand reset, and the
average power factor will be set 1.000.
Coincident
The A3 ALPHA meter is capable of recording the coincident demand
or coincident power factor, depending on meter type. Coincident
demand refers to a demand value that occurs at the same time as
another demand reaches its peak value.

Example: A utility wants to record the kVAR demand at the time


of a maximum kW. This requires that kVAR be stored and
reported during the same interval as the maximum kW demand.
Coincident power factor refers to the average power factor since the
last demand reset that occurs at the same time as a demand value
reaches its peak value.

Example: A utility wants to record the average power (since the


last demand reset) at the time of a maximum kVAR demand. This
requires the power factor be stored and reported during the
same interval as the maximum kVAR demand.
Method 1 Method 2
if using kWh and kVAh: if using kWh and kVARh:

Coincident demand values are available on A3K, A3R, and A3Q


meter types. Coincident power factor values are only available on
A3K and A3R meter types. The number of supported coincident
values that may be captured by the meter depends on whether or not
the advanced four quadrant metering option is present.
Meter type Total coincident values
A3D or A3T None
A3K, A3Q,* A3R 2
A3KA, A3QA,* A3RA 4

67
Components and programs

*A3Q meters can be programmed to trigger the recording of coincident


demand, but A3Q meters do not support coincident power factor measurement.

Display tab

Display options include the hold time, the sequence of the display
quantities for each display list, and how the quantities are displayed.

Control tab
Hold time: You can configure how long each item is lit on the meter's
LCD. The range can be between 1 second and 15 seconds, with the
default being 6 seconds.
If the quantity being displayed requires fewer digits than what it is
configured for, you can check the Show leading zeros on metered
quantities to pad the quantity with leading zeros (the default is
unchecked).
Formatting options
Determines how many digits to display to the right
of the decimal point, from 0 to 4.

Decimal location
For demand values, the default is 2.
For energy values, the default is 0.

Determines how many total digits to display, from 3


to 6.

For demand values, the default is 5.


Display digits For energy values, the default is 5.

Note: If you are expecting negative values (for


example, you are metering net or received
quantities), Elster recommends that you set the
display digits to 5 or fewer.
You can select the unit of measure on the display.
You can select kilo units, mega units, or unity.
Note: If you select either mega or unity, the
Display units
power/energy units identifer will not be lit. Instead,
you must identify the value using the quantity
identifier.

68
TM42-3060

Display labels
You can choose whether or not the display identifiers are lit on the display for
each display list. If checked (the default for all display lists), the display
identifiers are lit for their appropriate quantity. If unchecked, the display
identifiers are inhibited.

Display previous billing data


A quantity will be displayed as 0 until a demand
Always (default) reset occurs. After a demand reset, the previous
billing data value will be displayed.
The previous billing data value will only be
Only if present
displayed after a demand reset.

Display previous season data


A quantity will be displayed as 0 until a demand
reset at the season change occurs. After the
Always (default)
demand reset, the previous billing data value will
be displayed.
The previous billing data value will only be
Only if present
displayed after the season change demand reset.

Date format
A date value will be displayed in the DD-MM-YY
Day-Month-Year
format. For example, November 1, 2013, will be
(default)
displayed as 01.11.13.
A date value will be displayed in a MM-DD-YY
Month-Day-Year format. For example, November 1, 2013, will be
displayed as 11.01.13.
A date value will be displayed in a YY-MM-DD
Year-Month-Day format. For example, November 1, 2013 will be
displayed as 13.11.01.
Warnings tab
Warning codes are automatically inserted as the last item in the
normal display list and the alternate display list. The meter can be
configured so that one or more warning codes will lock the display
with an error code (Er3 300000). You can also specify which warning
codes can lock the display with an error code and which cannot. If
the condition causing the warning clears, the error code will also
clear.
To enable all warning codes to lock as an error, check the Lock all
warnings on the display using defined warning codes (the default
is unchecked). If the option is unchecked, you can select the
individual warning codes that can lock as an error in the panel below.
To enable the warning that reverse energy is detected, you must
check to enable Display warning if reverse power flow detected.
If this option is unchecked (default), then the meter will inhibit the
display of F1 000100, indicating reverse energy flow is detected.
Any or all of the following warning codes can be selected to lock on
the display as an error code (Er3 300000):

69
Components and programs

 Demand overload warning (F1 100000)


 Potential indicator warning (F1 010000)
 Reverse energy warning* (F1 000100)
 Improper meter operation warning (F1 000010)
 Low battery warning (F1 000001)
 End of calendar warning (F2 200000)
 PQM test warning (F2 020000)
 Line frequency warning (F2 002000)
 Demand threshold exceeded warning (F2 000200)
 Service current test failure warning (F2 000002)
*The Display warning if reverse power flow detected must be
checked for this code to appear as a warning or to be able to
lock the warning as an error.
Normal tab / Alternate tab / Test tab
The Normal tab, Alternate tab, and Test tab allow you to configure
which items will display on the LCD in the order specified for the
corresponding display lists (normal display list, alternate display list,
and test display list). The A3 ALPHA meter can display up to 6
characters at a time. Certain display items can exceed the 6-
character limit. To display these items on the LCD, you must include
all of the multiple display items as part of the display list.
For example, the meter ID can be up to 20 characters. To show all 20
characters on the LCD, you must select the following items in order:
 Meter ID:1
o displays the first 2 digits
 Meter ID:2
o displays the next 6 digits
 Meter ID:3
o displays the next 6 digits
 Meter ID:4
o displays the last 6 digits
With the meter ID, it is also possible to select to display only the last
9 digits of the meter ID. In this instance, the first 3 digits will be
displayed in the quantity identifier region; and the last 6 digits will be
displayed in the main display quantity region.
Displayable items
To help you sort and select the display items, you can drag 'n drop
one or more of the column header buttons to the gray are above the
list.
Category Items

70
TM42-3060

Current billing Per metered quantity measurements (including


Cumulative, Maximum, Maximum Date, and
Maximum Time) of the present interval for the
following:
 Total
 Rate A
 Rate B
 Rate C
 Rate D
EnergyAxis  EnergyAxis utility ID
 ILC/ILN errors
 ILC/ILN status
 ILC number of nodes
 ILC number of repeaters
 LAN ID:1
 LAN ID:2
 LAN registration information
Identification  Account:1
 Account:2
 Account:3
 Account:4
 Meter ID:1
 Meter ID:2
 Meter ID:3
 Meter ID:4
 Complete LCD test
 Custom display string 1
 Custom display string 2
 DSP code
 DSP revision
 Firmware product
 Firmware revision
 Firmware version
 Hardware revision
 Hardware version
 Meter family
 Meter ID: last 9 characters
 Meter programmer ID
Instrumentation  Line frequency
 Per phase of the following:
 2nd harmonic current
 2nd harmonic voltage
 2nd harmonic voltage %
 PF
 PF angle
 TDD
 current
 current % THD
 current angle
 fundamental current
 fundamental voltage
 harmonic current
 kVA

71
Components and programs

 kVAR
 kW
 voltage
 voltage % THD
 voltage angle
 Service current test
 Service voltage test
 System PF (arithmetic)
 System PF (vectorial)
 System PF angle (arithmetic)
 System PF angle (vectorial)
 System service type
 System kVA (arithmetic)
 System kVA (vectorial)
 System kVAR (arithmetic)
 System kVAR (vectorial)
 System kW
Meter configuration  CT ratio
 Demand interval - normal mode
 Demand interval - test mode
 Demand overload value
 External multiplier
 Meter adjusted Kh
 Meter factory Kh
 Program ID
 Pulse ratio
 Transformer factor
 VT ratio
 Wh per pulse (Kh)
Previous billing Per metered quantity measurements of the
previous billing period (including Cumulative,
Maximum, Maximum Date, and Maximum Time) for
the following:
Total
Rate A
Rate B
Rate C
Rate D
Present Interval
Previous Interval

Previous season Per metered quantity measurements of the


previous season (including Cumulative, Maximum,
Maximum Date, and Maximum Time) for the
following:
 Total
 Rate A
 Rate B
 Rate C
 Rate D
 Present Interval
 Previous Interval

72
TM42-3060

Self read Per metered quantity measurements


(including Cumulative, Maximum,
Maximum Date, and Maximum Time) for
the self read for the following:
 Total
 Rate A
 Rate B
 Rate C
 Rate D
Status  Comm session count (port 1)
 Comm session count (port 2/optical)
 Date of last pending table activation
 Days since input pulse
 Days since reset
 Demand reset date
 Demand resets (all)
 Demand resets (manual)
 Effective Date for Rates/Special Dates
 End power out date
 End power out time
 Errors? (Yes/No)
 Initial remote baud port 1
 Initial remote baud port 2
 Last Elster configuration change date
 Number of write sessions (port 1)
 Number of write sessions (port 2/optical)
 Outage log
 Power outage count
 Present day of week
 Present date
 Present season
 Present time
 Program change date - port 1
 Program change date - port 2/optical
 Pulse count VARh delivered
 Pulse count VARh received
 Pulse count Wh delivered
 Pulse count Wh received
 Self read date
 Special display item 1
 Special display item 2
 Special display item 3
 Special display item 4
 Special display item 5
 Start power out date
 Start power out time
 PQM Status (On/Off)
 Time left interval
 Transformer loss comp status
 Warnings? (Yes/No)

A1800 ALPHA metering component

73
Components and programs

About the A1800 ALPHA metering component

The metering component for the A1800 ALPHA meter has the
following main tabs:
 Quantities tab
 Display tab
 Interval data configuration tab

When you create a metering component, you must first specify the
meter type you want to create this component for. You must reactive
metering (R) for the A1800 ALPHA meter.
See the A1800 ALPHA meter types for a brief overview of metered
quantities, or see the technical manual for more information.
You will then be specified to select the program type. Select either
single rate demand or TOU as appropriate for your desired
configuration.

Quantities tab

Summations and Power factors / Demands


To configure the meter to record summations and power factors for a
desired quantity, drag the desired quantities from the Summations,
Power Factors, and Coincidents list drop it in the Summations and
Power Factors box.
 The possible quantities are listed in the top list box
 The possible power factors are listed in the bottom list box
The base meter supports up to 3 summation and power factor
quantities and 2 demand quantities. If the Configure for Advanced
Metering option is checked, then the meter supports up to 8
summation and power factor quantities and up to 6 demand
quantities.
The Demands box is automatically populated based on the selected
summation quantities in the order they are listed in the Summation
and Power Factors box. You can drag a summation and power factor
quantity up or down to control its order in the list. You can also
enable or disable load control & overload thresholds (as a single
toggle) per metered quantity. If Apply Load Control & Overload
Thresholds is enabled, the meter will use the thresholds defined in
the Demand component to respond to a demand overload or activate
a load control relay.
Coincidents
The number of coincident values that may be captured depends on
the state of the 4-quadrant metering.
 A1800 ALPHA meters without 4-quadrant metering record up to
2 coincident values
 A1800 ALPHA meters with 4-quadrant metering record up to 4
coincident value

74
TM42-3060

To configure the coincidents, you must drag the desired quantity to


the coincident list.
 Drag the desired demand value (from the Demands box) to the
desired position in the Coincident Demand column to specify
the demand quantity to be recorded.
 Drag the desired power factor value (from the Summations and
Power Factor box) to the desired position in the Coincident
Demand column to specify the power factor quantity to be
recorded.
 Drag the desired trigger event to the desired position in the At
the time of a maximum column to specify when the coincident
demand or power factor is recorded.

Display tab

Display options include the hold time, the sequence of the display
quantities for each display list, and how the quantities are displayed.

Control tab
Hold time: You can configure how long each item is lit on the meter's
LCD. The range can be between 1 second and 15 seconds, with the
default being 6 seconds.
If the quantity being displayed requires fewer digits than what it is
configured for, you can check the Show leading zeros on metered
quantities to pad the quantity with leading zeros (the default is
unchecked).
Formatting options
Determines how many digits to display to the right
of the decimal point, from 0 to 6.

Decimal location
For demand values, the default is 2.
For energy values, the default is 0.

Determines how many total digits to display, from 3


to 8.
Display digits
For demand values, the default is 5.

75
Components and programs

For energy values, the default is 5.

Note: If you are expecting negative values (for


example, you are metering net or received
quantities), Elster recommends that you set the
display digits to 7 or fewer.
You can select the unit of measure on the display.
Display units
You can select kilo units, mega units, or unity.

Display labels
You can choose whether or not the display identifiers are lit on the display for
each display list. If checked (the default for all display lists), the display
identifiers are lit for their appropriate quantity. If unchecked, the display
identifiers are inhibited.

Read Without Power


The meter may be ordered with the Read without Power feature. When the
feature is available and activated, the meter can do the following:

display the LCD test


scroll through the normal and alternate display lists (error and warning codes
are handled as appropriate)
perform a billing read or diagnostic read through the optical port
manually perform a demand reset

The Read without power time out can be between 0 and 255 minutes (default
is 0, which also disables Read without Power).
For more information on Read without Power, see the A1800 ALPHA meter
technical manual.

Display previous billing data


A quantity will be displayed as 0 until a demand
Always (default) reset occurs. After a demand reset, the previous
billing data value will be displayed.
The previous billing data value will only be
Only if present
displayed after a demand reset.

Display previous season data


A quantity will be displayed as 0 until a demand
reset at the season change occurs. After the
Always (default)
demand reset, the previous billing data value will
be displayed.
The previous billing data value will only be
Only if present
displayed after the season change demand reset.

Date format
A date value will be displayed in the DD-MM-YY
Day-Month-Year
format. For example, November 1, 2013, will be
(default)
displayed as 01.11.13.
A date value will be displayed in a MM-DD-YY
Month-Day-Year format. For example, November 1, 2013, will be
displayed as 11.01.13.

76
TM42-3060

A date value will be displayed in a YY-MM-DD


Year-Month-Day format. For example, November 1, 2013 will be
displayed as 13.11.01.

Self read annunciator numbering


The meter supports up to 12 self reads, typically
Annual one for each month. The number of the annunciator
corresponds to the number of the month.
The meter supports up to 35 self reads, numbered
in sequential order. The higher the number, the
Rolling
older the self read is (that is, a self read numbered
35 will be older than a self read numbered 20).

Check the Configure ALL instrumentation quantities as primary to


display all instrumentation quantities transformer ratios (that is,
voltage quantities are multiplied by the voltage transformer ratio;
current quantities are multiplied by the current transformer ratio, and
power quantities are multiplied by the transformer factor). The
default is unchecked.
You can also configure the meter to display between 0 and the 35
self reads on the LCD by specifying the number in the Number of
self reads to loop through box. The default is 0.
Warnings tab
Warning codes are automatically inserted as the last item in the
normal display list and the alternate display list. The meter can be
configured so that one or more warning codes will lock the display
with an error code (Er3 300000). You can also specify which warning
codes can lock the display with an error code and which cannot. If
the condition causing the warning clears, the error code will also
clear.
To enable all warning codes to lock as an error, check the Lock all
warnings on the display using defined warning codes (the default
is unchecked). If the option is unchecked, you can select the
individual warning codes that can lock as an error in the panel below.
To enable the warning that reverse energy is detected, you must
check to enable Display warning if reverse power flow detected.
If this option is unchecked (default), then the meter will inhibit the
display of F1 000100, indicating reverse energy flow is detected.
Any or all of the following warning codes can be selected to lock on
the display as an error code (Er3 300000):
 Demand overload warning (W1 100000)
 Potential indicator warning (W1 010000)
 Reverse energy warning* (W1 000100)
 Improper meter operation warning (W1 000010)
 Low battery warning (W1 000001)
 End of calendar warning (W2 200000)
 TRueQ test warning (W2 020000)

77
Components and programs

 Line frequency warning (W2 002000)


 Demand threshold exceeded warning (W2 000200)
 Service current test failure warning (W2 000002)
*The Display warning if reverse power flow detected must be
checked for this code to appear as a warning or to be able to
lock the warning as an error.
Normal tab / Alternate tab / Test tab
The Normal tab, Alternate tab, and Test tab allow you to configure
which items will display on the LCD in the order specified for the
corresponding display lists (normal display list, alternate display list,
and test display list). The A1800 ALPHA meter can display up to 8
characters at a time. Certain display items can exceed the 8-
character limit. To display these items on the LCD, you must include
all of the multiple display items as part of the display list.
For example, the meter ID can be up to 20 characters. To show all 20
characters on the LCD, you must select the following items in order:
 Meter ID:1
o Displays the first 4 characters
 Meter ID:2
o Displays the next 8 characters
 Meter ID:3
o Displays the last 8 characters
Displayable items
To help you sort and select the display items, you can drag 'n drop
one or more of the column header buttons to the gray are above the
list.
Category Items
Current billing Per metered quantity measurements of the prevent
interval (including Cumulative, Maximum, Maximum
Date, and Maximum Time) for the following:

 Total
 Rate A
 Rate B
 Rate C
 Rate D
EnergyAxis  EnergyAxis utility ID
 ILC/ILN errors
 ILC/ILN status
 ILC number of nodes
 ILC number of repeaters
 LAN ID:1
 LAN ID:2
 LAN registration information
Identification  Account:1
 Account:2

78
TM42-3060

 Account:3
 Meter ID:1
 Meter ID:2
 Meter ID:3
 Complete LCD test
 Custom display string 1
 Custom display string 2
 DSP code
 DSP revision
 Firmware product
 Firmware revision
 Firmware version
 Hardware revision
 Hardware version
 Meter family
 Meter programmer ID
Instrumentation  Line frequency
 Per phase of the following:
 2nd harmonic current
 2nd harmonic voltage
 2nd harmonic voltage %
 PF
 PF angle
 TDD
 current
 current % THD
 current angle
 fundamental current
 fundamental voltage
 harmonic current
 kVA
 kVAR
 kW
 voltage
 voltage % THD
 voltage angle
 Service current test
 Service voltage test
 System PF (arithmetic)
 System PF (vectorial)
 System PF angle (arithmetic)
 System PF angle (vectorial)
 System service type
 System kVA (arithmetic)
 System kVA (vectorial)
 System kVAR (arithmetic)
 System kVAR (vectorial)
 System kW
Meter configuration  CT ratio
 Demand interval - normal mode
 Demand interval - test mode
 Demand overload value

79
Components and programs

 External multiplier
 Meter adjusted Kh
 Meter factory Kh
 Program ID
 Pulse ratio
 Transformer factor
 VT ratio
 Wh per pulse (Kh)
Previous billing Per metered quantity measurements of the
previous billing period (including Cumulative,
Maximum, Maximum Date, and Maximum Time) for
the following:

 Total
 Rate A
 Rate B
 Rate C
 Rate D
 Present Interval
 Previous Interval
Previous season Per metered quantity measurements of the
previous season (including Cumulative, Maximum,
Maximum Date, and Maximum Time) for the
following:

 Total
 Rate A
 Rate B
 Rate C
 Rate D
 Present Interval
 Previous Interval
Self read Per metered quantity measurements (including
Cumulative, Maximum, Maximum Date, and
Maximum Time) for the self read for the following:

 Total
 Rate A
 Rate B
 Rate C
 Rate D
Status  Comm session count (port 1)
 Comm session count (port 2/optical)
 Date of last pending table activation
 Days since input pulse
 Days since reset
 Demand reset date
 Demand resets (all)
 Demand resets (manual)
 Effective Date for Rates/Special Dates
 End power out date
 End power out time
 Initial remote baud port 1

80
TM42-3060

 Initial remote baud port 2


 Last Elster configuration change date
 Number of write sessions (port 1)
 Number of write sessions (port 2/optical)
 Outage log
 Power outage count
 Present day of week
 Present date
 Present season
 Present time
 Program change date - port 1
 Program change date - port 2/optical
 Pulse count VARh delivered
 Pulse count VARh received
 Pulse count Wh delivered
 Pulse count Wh received
 Self read date
 Special display item 1
 Special display item 2
 Special display item 3
 Special display item 4
 Special display item 5
 Start power out date
 Start power out time
 TRueQ Status (On/Off)
 Time left interval
 Transformer loss comp status

Interval data configuration tab

Interval data mode


You can configure how the meter stores data in load profiling.
 Pulses: Data stored in load profiling is stored as pulses of the
metered quantity.
 Engineering units: Data for each interval is converted to
engineering units (for example: kWh, kvarh, etc.) before it is
stored in load profiling; the value is reset with each interval.
 Cumulative engineering units: Data is converted to engineering
units before it is stored in load profiling; the value is not reset
with each interval. Instead, it is a cumulative number from zero
to the maximum value capable of being stored in the meter.

Note: Storing data as engineering units or cumulative


engineering units takes considerably more space than storing
the data as pulses.
Days of storage
Using Metercat, you can select Maximize to configure the meter to
log the maximum number of days possible. This will be determined
by the meter based on available memory when the program is
written. The function completion report will indicate the actual

81
Components and programs

number of days the meter will record. Alternatively, you can specify
the number of days manually from zero (which disables load
profiling in the meter) to 999. See Estimated load profiling days for a
discussion on how many days the meter may be capable of recording
based on different parameters.
All A1800 ALPHA meters are equipped with EEPROM. The main
board storage is 256 KB. A small portion of EEPROM is permanently
reserved (called "reserved memory") by the meter to store the main
billing and configuration information. The reminder of the memory,
called "shared memory," is used to store the following logs and data
sets:
 event log
 history log
 self reads
 TRueQ log
 voltage sag log
 interval data (load profiling)
 instrumentation profiling

All of the logs and data sets share the meter's memory. The sizes of
each may vary to allow more room for a different log or data set. For
example, self reads can store less data so that load profiling can
store more data. If more memory is required, an optional extended
memory option board can be used to provide up to 1 MB of space for
shared memory.
Interval length
Load profiling has its own, separate interval length that is
configured independently from the demand interval length. You can
select the number of minutes for the load profiling interval from the
drop list, which are all the minutes that can be evenly divisible into
an hour.
Pulse divisor
You can specify a pulse divisor value in the range of 1 (default) to
255.
Each load profiling interval can store up to 32,767 pulses before
overflowing. By default, the meter counts one pulse per Ke. A pulse
divisor is used to scale down the number of pulses stored in each
load profiling interval. This allows recording of data that may
otherwise exceed the maximum number of pulses that can be stored
in each load profiling interval.
Quantities to record
As you select a quantity to record, Metercat will automatically enable
the next drop list. The A1800 ALPHA meter is capable of recording up
to 8 channels of information from the following sources:
 kVAh delivered (Q1 + Q4)

82
TM42-3060

 kVAh Q1
 kVAh Q2
 kVAh Q3
 kVAh Q4
 kVAh received (Q2 + Q3)
 kVAh sum
 kvarh (Q1 - Q4)
 kvarh (Q1 + Q4)
 kvarh (Q2 - Q3)
 kvarh (Q2 + Q3)
 kvarh (Q3 - Q2)
 kvarh delivered (Q1 + Q2)
 kvarh net
 kvarh Q1
 kvarh Q2
 kvarh Q3
 kvarh Q4
 kvarh received (Q3 + Q4)
 kvarh sum
 kWh devlivered
 kWh net
 kWh received
 kWh sum

REX2 metered quantities


The REX2 meter supports up to 2 energy quantities and 1 demand
quantity. The Quantities view identifies the energy and demand
quantities in a read-only form. See About viewsets for more
information.

REXUniversal metering component

Summation quantity and demand quantity

See Meter types for a listing of the available energy and demand
quantities supported by the REXUniversal meter.
In the Decade 2 standard tables, the meter supports total and 4-tier
data for two summations and two demand.
 The resolution for summations is 1 Wh
 The resolution for demands is 1 W

83
Components and programs

Demand data include a time stamp for each total and TOU maximum
demand value.
In additional, the meter records the total summation values (non-
TOU) for two additional sources.

NETWORK COMPONENT
The IP AxisLink router requires configuration of the following items:
 Ethernet WAN
 DTLS and tunnel parameters to connect to the IP AxisLink Secure
Tunnel Server
 HTTP settings for the router's Web interface
 Serial Edge interface (if you are connecting the router serially to
a DA device)
 Clock source
A DTLS tunnel is required if the router will support Edge DA devices
(Ethernet, serial, or I/O)
See the IP AxisLink router installation and administration manual
(TM42-4002) for more information. Contact your Elster
representative to request TM42-4002 if you do not have a copy.

PQM COMPONENT (TRUEQ)

Note: Depending on the language selection used for Metercat,


the TRueQ may be referred to PQM. The language setting is
controlled by Help > Language. As a standard, the Metercat
documentation will use the English (IEC) designation TRueQ,
which is also consistent with the A1800 ALPHA technical
manual. While the A1800 ALPHA meter supports the default
PQM tests, the A1800 ALPHA meter offers additional tests as
part of its tamper restraint and quality monitoring.
See the following documents for more information:
 The A3 ALPHA meter technical manual for information regarding
PQM. PQM is primarily described in chapter 4, "Meter Tools."
 The A1800 ALPHA meter technical manual for information
regarding TRueQ. TRueQ is primarily described in chapter 4,
"Meter Tools."
Item Description
See "PQM test status" below for
PQM ON
information.
Each PQM set contains a series of
different power quality and tampering
tests. From the drop list, select the
PQM Set PQM set you want to write to the
meter. For more information about
the tests in each set, see "A3 ALPHA
meter PQM tests and test sets" or

84
TM42-3060

"A1800 ALPHA meter TRueQ tests


and test sets" as appropriate.
Factory code indicating which tests
are configured as a test set from
Set version tests supported by the meter. One
PQM configuration can have many
test sets with different set versions.
Factory code indicating the version of
PQM version PQM test configuration supported by
the meter.

A3 ALPHA meter PQM tests and test sets


PQM tests do not interfere with any meter functions related to energy
measurement. These test run separately from the metering
functions. The following table shows the tests available. See the topic
for each particular test for more information about each test.
The A3 ALPHA meter supports the following PQM test sets:
 Default Elster PQM test set
 IEEE Voltage Imbalance test set, which requires A3 ALPHA meter
firmware version 4.0 or later
 Tamper detect test set, which requires A3 ALPHA meter firmware
version 5.0 or later

Tamper
Default IEEE Test name
detect
Test 1 Low voltage phase A test
Test 2 Low voltage phase B test
Test 3 Low voltage phase C test
Test 4 High voltage phase A test
Test 5 High voltage phase B test
Test 6 High voltage phase C test
Test
Test 1 Service voltage test
1
Test
Test 2 Low voltage test
2
Test
Test 3 High voltage test
3
Test
Test 4 Reverse power test and power factor test
4
Test
Test 5 Low current test
5
Test
Test 6 Power factor test
6
Test
Test 7 Test 7 Second harmonic current test
7
Test
Test 8 % total harmonic distortion current test
8
Test
Test 9 % total harmonic distortion voltage test
9
Test Test
Voltage imbalance test
10 10

85
Components and programs

Test Test
Current imbalance test
11 11
Test Test
Total demand distortion
12 12
Test
IEEE voltage imbalance
13
Test 8 Magnetic detection test (leading PF angle)
Test 9 Magnetic detection test (PF angle differences)

A1800 ALPHA meter TRueQ tests and test sets


TRueQ tests do not interfere with any meter functions related to
energy measurement. These test run separately from the metering
functions. The following table shows the tests available. See the topic
for each particular test for more information about each test.
The A1800 ALPHA meter supports the following TRueQ test sets:
 Default Elster TRueQ test set
 Enhanced TRueQ test set
 IEEE voltage imbalance test set
 EN 50160 TRueQ test set, which requires A1800 ALPHA meter
firmware version 4.0 or later

EN Tamper
Default Enhanced IEEE Test name
50160 detect

Test 1 Voltage interruptions test


Rapid voltage changes
Test 2
test
Test 3 Frequency changes 1
Test 4 Frequency changes 2
Test
Test 1 Test 1 Test 5 Service voltage test
1
Test
Test 2 Test 2 Low voltage test
2
Test
Test 3 Test 3 High voltage test
3
Test Reverse power test and
Test 4 Test 4
4 power factor test
Test
Test 5 Test 5 Low current test
5
Test
Test 6 Test 6 Power factor
6
Test Second harmonic current
Test 7 Test 7 Test 7
7 test
Test % total harmonic
Test 8 Test 8 Test 6
8 distortion current test
Test % total harmonic
Test 9 Test 9 Test 7
9 distortion voltage test

86
TM42-3060

Test Test
Test 10 Voltage imbalance
10 10
Test Test
Test 11 Current imbalance
11 11
Test Test
Test 12 Total demand distortion
12 12
Test 13 Test 1 Low voltage (Line 1)
Test 14 Test 2 Low voltage (Line 2)
Test 15 Test 3 Low voltage (Line 3)
Test 16 Test 4 High voltage (Line 1)
Test 17 Test 5 High voltage (Line 2)
Test 18 Test 6 High voltage (Line 3)
Low voltage and current
Test 19
present (Line 1)
Low voltage and current
Test 20
present (Line 2)
Low voltage and current
Test 21
present (Line 3)
Test 22 Current missing (Line 1)
Test 23 Current missing (Line 2)
Test 24 Current missing (Line 3)
Test
IEEE voltage imbalance
13
Magnetic detection test
Test 8
(leading PF angle)
Magnetic detection test
Test 9
(PF angle differences)

Voltage sags
A momentary sag in voltage can reset process control equipment and
computer systems. The momentary voltage sag monitor watches for
decreases in voltage that last for a measured number of cycles. This
monitor can detect any voltage decrease that falls below its
programmed threshold for as few as 2 line cycles. You can use
Metercat to define the threshold and duration.
The voltage sag threshold is defined as a percentage of the lowest
nominal per phase voltage and recommended to be in the range of
60% to 99.9%. A sag is defined as a drop in the phase voltage below
the threshold for a duration greater than the sag minimum time and
less than the sag maximum time. If the condition exceeds the
maximum sag tag, it will not be considered a sag event. The sag time
can be configured to a resolution of approximately 8 milliseconds.
The minimum range can be from approximately 32 milliseconds to
approximately 2 seconds. The maximum time range can be a time up
to approximately 546 seconds.

Note: Because of meter resolution and data formatting, Metercat


adjusts (either up or down) the values entered for minimum and

87
Components and programs

maximum duration to the meter's resolution and data formatting.


For example, if you enter 35 milliseconds for a duration,
Metercat will round the value to 33 milliseconds. When you read
a meter, the threshold values may be slightly different than the
values you programmed.
The meter's potential indicators on the LCD will blink if the voltage is
below the sag level threshold. Each phase voltage has a voltage sag
counter and time associated with it. Each counter can accumulate up
to 65,535 before rolling over to zero. Each cumulative timer can
record time for 414 days. The counter and timer for each phase are
maintained in the meter's memory, and these values are reported
and reset through Metercat.

For more information


See the technical manual for your meter for more information on
voltage sag. Typically, the information is found in Chapter 4, "Meter
tools."

PQM test status


The following table shows the status of the PQM tests taking the
PQM Alpha Key, PQM component programming, and the Turn PQM
ON/OFF task.
PQM
Turn PQM
component:
PQM Alpha Key ON/OFF task Result
PQM ON check
parameter
box
Specified PQM
On
checked (PQM is tests will run
on) Specified PQM
Off
tests will not run
Enabled
Specified PQM
On
unchecked (PQM tests will run
is off) Specified PQM
Off
tests will not run
Specified PQM
On
tests will not run
checked
Specified PQM
Off
tests will not run
Disabled
Specified PQM
On
tests will not run
unchecked
Specified PQM
Off
tests will not run

Note: The PQM component can be configured in a meter


regardless of the status of the PQM Alpha Key. If the status of
the PQM Alpha Key is disabled, the PQM tests will not run.

See also

88
TM42-3060

 See Replace PQM for information on replacing the PQM


component with new values for both PQM/TRueQ and voltage
sag.
 See Edit PQM Thresholds for information on editing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Turn PQM or TRueQ ON/OFF for information on turning
PQM/TRueQ on or off without reprogramming or changing
values.
 See Clear PQM Data for information on clearing the PQM
information and the voltage sag information.

PQM TEST DESCRIPTIONS

Current imbalance test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula:

Variable: Minimum current threshold: 0.00% to 100.00% of Class


amps/Imax; Imbalance threshold: 0.00% to 100.00%
Default value: Minimum current threshold: 1.25% of Class
amps/Imax; Imbalance threshold: 5.00%
Configuration based on: Minimum high current threshold and
imbalance threshold
Description:
This test checks for an imbalance between per phase currents. To
qualify as a failure, both of the following must exist:
 The highest per phase current must be greater than the
minimum current threshold
 The ratio between the lowest per phase current to the highest
(low/high) must be less than the imbalance threshold
The minimum current threshold is defined as a percentage of Class
amps/Imax, and the imbalance threshold is a percentage.
Stored value: None

Current missing (Line 1)


Supported devices: A1800 ALPHA
Test sets: Enhanced

89
Components and programs

Formula:
(VL1 or VL2 or VL3) ≥ specified voltage threshold and
IL1 < specified current threshold and
(IL2 or IL3) ≥ specified current threshold
Variable:
 5.0 % to 100.0 % of nominal for Line 1 voltage threshold
 5.0 % to 100.0 % of nominal for Line 2 voltage threshold
 5.0 % to 100.0 % of nominal for Line 3 voltage threshold
 0.0003 A to 1000.0000 A for Line 1 current threshold
 0.0010 A to 1000.0000 A for Line 2 current threshold
 0.0010 A to 1000.0000 A for Line 3 current threshold

Default value:
 60.0 % of nominal for Line 1 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 0.0015 A for Line 1 current threshold
 0.0750 A for Line 2 current threshold
 0.0750 A for Line 3 current threshold

Configuration based on: Specified thresholds for voltage and current


Description:
This test checks voltage and current on all phases to help detect
possible theft or CT problems on Line 1. This test fails if the following
conditions are present:
 Voltage is present on any phase, and
 Current is at or above a specified threshold on Line 2 or Line 3,
and
 Current is below a specified threshold on Line 1

Stored value: Line 1 current

Current missing (Line 2)


Supported devices: A1800 ALPHA
Test sets: Enhanced

Formula:
(VL1 or VL2 or VL3) ≥ specified voltage threshold and

90
TM42-3060

IL2 < specified current threshold and


(IL1 or IL3) ≥ specified current threshold
Variable:
 5.0 % to 100.0 % of nominal for Line 1 voltage threshold
 5.0 % to 100.0 % of nominal for Line 2 voltage threshold
 5.0 % to 100.0 % of nominal for Line 3 voltage threshold
 0.0010 A to 1000.0000 A for Line 1 current threshold
 0.0003 A to 1000.0000 A for Line 2 current threshold
 0.0010 A to 1000.0000 A for Line 3 current threshold

Default value:
 60.0 % of nominal for Line 1 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 0.0750 A for Line 1 current threshold
 0.0015 A for Line 2 current threshold
 0.0750 A for Line 3 current threshold

Configuration based on: Specified thresholds for voltage and current


Description:
This test checks voltage and current on all phases to help detect
possible theft or CT problems on Line 2. This test fails if the following
conditions are present:
 Voltage is present on any phase, and
 Current is at or above a specified threshold on Line 1 or Line 3,
and
 Current is below a specified threshold on Line 2

Stored value: Line 2 current

Current missing (Line 3)


Supported devices: A1800 ALPHA
Test sets: Enhanced

Formula:
(VL1 or VL2 or VL3) ≥ specified voltage threshold and
IL3 < specified current threshold and
(IL2 or IL3) ≥ specified current threshold

91
Components and programs

Variable:
 5.0 % to 100.0 % of nominal for Line 1 voltage threshold
 5.0 % to 100.0 % of nominal for Line 2 voltage threshold
 5.0 % to 100.0 % of nominal for Line 3 voltage threshold
 0.0010 A to 1000.0000 A for Line 1 current threshold
 0.0010 A to 1000.0000 A for Line 2 current threshold
 0.0003 A to 1000.0000 A for Line 3 current threshold

Default value:
 60.0 % of nominal for Line 1 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 60.0 % of nominal for Line 2 voltage threshold
 0.0750 A for Line 1 current threshold
 0.0750 A for Line 2 current threshold
 0.0015 A for Line 3 current threshold

Configuration based on: Specified thresholds for voltage and current


Description:
This test checks voltage and current on all phases to help detect
possible theft or CT problems on Line 3. This test fails if the following
conditions are present:
 Voltage is present on any phase, and
 Current is at or above a specified threshold on Line 2 or Line 3,
and
 Current is below a specified threshold on Line 3

Stored value: Line 3 current

Frequency changes 1
Supported devices: A1800 ALPHA
Test sets: EN 5160

Formula:
system frequency < specified low frequency threshold or
system frequency > specified high frequency threshold
Variable: Low frequency threshold: 85.00% to 99.99% of the nominal
system frequency; High frequency threshold: 100.01% to 115.00% of
the nominal system frequency

92
TM42-3060

Default value: Low frequency threshold: 99.00%; high frequency


threshold: 101.00%
Configuration based on: Specified thresholds for both low frequency
and high frequency
Description:
This test checks the frequency for values that are out of range. The
frequency must be within a specified range of the system frequency.
The test fails if the frequency is out of the specified range.
Stored value: Frequency value at the time the event is detected

Frequency changes 2
Supported devices: A1800 ALPHA
Test sets: EN 5160

Formula:
system frequency < specified low frequency threshold or
system frequency > specified high frequency threshold
Variable: Low frequency threshold: 85.00% to 99.99% of the nominal
system frequency; High frequency threshold: 100.01% to 115.00% of
the nominal system frequency
Default value: Low frequency threshold: 94.00%; high frequency
threshold: 104.00%
Configuration based on: Specified thresholds for both low frequency
and high frequency
Description:
This test checks the frequency for values that are out of range. The
frequency must be within a specified range of the system frequency.
The test fails if the frequency is out of the specified range.
Stored value: Frequency value at the time the event is detected

High voltage test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula: (VL1 or VL2 or VL3) ≥ specified high voltage threshold


Variable: 100.1% to 200.0%
Default value: 106.0%
Configuration based on: A specified high voltage threshold
Description:
This test checks the per phase voltages for values that exceed a
specified limit. The threshold values can be set at a value higher or

93
Components and programs

lower than the limits selected for the service voltage test. This allows
a more thorough study of the voltage changes.
The threshold is defined as a percentage of the expected per phase
nominal value. The percentage for each phase can be individually
defined. The test fails if any of the phase voltages exceeds the
threshold.
Stored value: Phase A/Line 1 voltage (even if any other phase causes
the test to fail)

High voltage (Phase A/Line 1)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

Formula: VL1 ≥ specified high voltage threshold


Variable: 100.1% to 200.0% of nominal
Default value: 115.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase A/Line 1 values that exceed a specified limit.
The threshold is defined as a percentage of the expected Phase
A/Line 1 nominal voltage. The test fails if Phase A/Line 1 voltage
exceeds the voltage threshold.
Stored value: Phase A/Line 1 voltage

High voltage (Phase B/Line 2)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

Formula: VL2 ≥ specified high voltage threshold


Variable: 100.1% to 200.0% of nominal
Default value: 115.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase B/Line 2 values that exceed a specified limit.
The threshold is defined as a percentage of the expected Phase
B/Line 2 nominal voltage. The test fails if Phase B/Line 2 voltage
exceeds the voltage threshold.
Stored value: Phase B/Line 2 voltage

High voltage (Phase C/Line 3)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

94
TM42-3060

Formula: VL3 ≥ specified high voltage threshold


Variable: 100.1% to 200.0% of nominal
Default value: 115.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase C/Line 3 values that exceed a specified limit.
The threshold is defined as a percentage of the expected Phase
C/Line 3 nominal voltage. The test fails if Phase C/Line 3 voltage
exceeds the voltage threshold.
Stored value: Phase C/Line 3 voltage

IEEE voltage imbalance test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (IEEE); A1800 ALPHA (IEEE)

Formula:

Variable: 0.00% to 100.00%


Default value: 5.00%
Configuration based on: IEEE voltage imbalance threshold
Description:
This voltage imbalance calculation is defined in IEEE-1159-2009 and
is defined as the ratio of the magnitude of the negative sequence
voltage component to the magnitude of the positive sequence
voltage component, expressed in a percentage. The test fails if the
imbalance threshold value exceeds the specified voltage. IEEE
voltage imbalance may only be calculated in polyphase meters in
which all three line-to-line voltages are available to the voltage
sensing terminals.
These include 3-phase, 4-wire wye and 3-phase, 4-wire delta services
on 3-element meters and 3-phase, 3-wire delta services on 2-
element meters.

95
Components and programs

Stored value: None

Low current test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula: (IL1 or IL2 or IL3) < specified low current threshold


Variable: Based on service current test thresholds
Default value: Based on service current test thresholds
Configuration based on: Service current test thresholds
Description:
This test checks the per phase currents for values that fall below a
specified limit. This test will check for erroneous operation or failure
of a current transformer and can detect signs of meter tampering. If
all phase currents fall below the zero current threshold, then no
warning or indication will be provided. A warning will be issued when
one or more phase currents fall below the threshold value for the
qualification time while the remaining phase currents stay above the
limits.
This threshold is defined as a percentage of the meter Class ampere
rating (Imax) from the system service current test definition. This
percentage is applied on a per phase basis. The thresholds are
defined by the service current test configuration.
Stored value: None

Low voltage test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula: (VL1 or VL2 or VL3) < specified low voltage threshold


Variable: 0% to 99.9%
Default value: 94.0%
Configuration based on: A specified low voltage threshold
Description:
This test checks the per phase voltages for values that fall below a
specified limit. Each phase threshold can be set individually and can
be set at a value higher or lower than the limits selected for the
service voltage test. This allows a more thorough study of the voltage
changes.
The threshold is defined as a percentage of the expected per phase
nominal voltage (recommended to be in the range of 60.0% to
99.9%). The percentage for each phase can be individually defined.
The test fails if any phase voltage exceeds the threshold.

96
TM42-3060

Stored value: Phase A/Line 1 voltage (even if any other phase causes
the test to fail)

Low voltage & current present (Line 1)


Supported devices: A1800 ALPHA
Test sets: Enhanced

Formula:
VL1 < specified low voltage threshold and
IL1 ≥ specified high current threshold
Variable: 0.0% to 99.9% of nominal Line 1 voltage; 0.0003 to
1000.0000 amperes for Line 1 current
Default value: 78.0% for low voltage threshold; 0.0015 amperes for
high current threshold
Configuration based on: Specified thresholds for voltage and current
Description:
This test checks voltage and current on Line 1 to detect possible
theft or VT problems on Line 1. This test fails if the following
conditions are present:
 Current on Line 1 is greater than a specified current threshold,
and
 Voltage on Line 1 is less than a specified voltage threshold

Stored value: Line 1 voltage

Low voltage & current present (Line 2)


Supported devices: A1800 ALPHA
Test sets: Enhanced

Formula:
VL2 < specified low voltage threshold and
IL2 ≥ specified high current threshold
Variable: 0.0% to 99.9% of nominal Line 2 voltage; 0.0003 to
1000.0000 amperes for Line 2 current
Default value: 78.0% for low voltage threshold; 0.0015 amperes for
high current threshold
Configuration based on: Specified thresholds for voltage and current
Description:
This test checks voltage and current on Line 2 to detect possible
theft or VT problems on Line 2. This test fails if the following
conditions are present:

97
Components and programs

 Current on Line 2 is greater than a specified current threshold,


and
 Voltage on Line 2 is less than a specified voltage threshold

Stored value: Line 2 voltage

Low voltage & current present (Line 3)


Supported devices: A1800 ALPHA
Test sets: Enhanced

Formula:
VL3 < specified low voltage threshold and
IL3 ≥ specified high current threshold
Variable: 0.0% to 99.9% of nominal Line 3 voltage; 0.0003 to
1000.0000 amperes for Line 3 current
Default value: 78.0% for low voltage threshold; 0.0015 amperes for
high current threshold
Configuration based on: Specified thresholds for voltage and current
Description:
This test checks voltage and current on Line 3 to detect possible
theft or VT problems on Line 3. This test fails if the following
conditions are present:
 Current on Line 3 is greater than a specified current threshold,
and
 Voltage on Line 3 is less than a specified voltage threshold

Stored value: Line 3 voltage

Low voltage (Phase A/Line 1)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

Formula: VL1 < specified low voltage threshold


Variable: 0.0% to 99.9% of nominal
Default value: 60.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase A/Line 1 voltage for values that fall below a
specified limit. The threshold is defined as a percentage of the
expected Phase A/Line 1 nominal voltage. The test fails if Phase
A/Line 1 voltage falls below the voltage threshold.

98
TM42-3060

Stored value: Phase A/Line 1 voltage

Low voltage (Phase B/Line 2)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

Formula: VL2 < specified low voltage threshold


Variable: 0.0% to 99.9% of nominal
Default value: 60.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase B/Line 2 voltage for values that fall below a
specified limit. The threshold is defined as a percentage of the
expected Phase B/Line 2 nominal voltage. The test fails if Phase
B/Line 2 voltage falls below the voltage threshold.
Stored value: Phase B/Line 2 voltage

Low voltage (Phase C/Line 3)


Supported devices: A3 ALPHA, A1800 ALPHA
Test sets: Tamper detect (A3 ALPHA); Enhanced (A1800 ALPHA)

Formula: VL3 < specified low voltage threshold


Variable: 0.0% to 99.9% of nominal
Default value: 60.0% of nominal
Configuration based on: A specified voltage threshold
Description:
This test checks Phase C/Line 3 voltage for values that fall below a
specified limit. The threshold is defined as a percentage of the
expected Phase C/Line 3 nominal voltage. The test fails if Phase
C/Line 3 voltage falls below the voltage threshold.
Stored value: Phase C/Line 3 voltage

Magnetic detection (leading PF angle)


Supported devices: A3 ALPHA
Test sets: Tamper detection

Formula:
If [ (Wa > 0 and Ia > Minimum test phase current and Phase A normalized PF angle <
specified normalized power factor angle threshold) or
(Wb > 0 and Ib > Minimum test phase current and Phase B normalized PF angle <
specified normalized power factor angle threshold) or

99
Components and programs

(Wc > 0 and Ic > Minimum test phase current and Phase C normalized PF angle <
specified normalized power factor angle threshold)
Variable: 90.0 degrees to -90.0 degrees (leading or negative angles
are expected, but lagging or positive angles are allowed for special
conditions*)
Default value: -15 degrees (that is, 15 degrees leading)
Configuration based on: Specified normalized PF angle threshold
(configured in the Service Test component)
Description:
Each phase is tested individually, and if any phase fails, the test will
fail. Once any phase is failing, then all phases must be passing for
the PQM test failure to be over.
Each phase is initially checked to insure that real energy (Wh) is in
the Delivered direction. If it is, then the rms current for that phase is
checked to ensure that it is greater than a user defined minimum
test phase current threshold (as a percentage of Class Amps, and
defined in the Service Test component). If it is, then the normalized
power factor angle is tested to see if it is more leading than the
normalized power factor angle threshold (negative values are leading
so less than means more leading).
Normalization of a power factor angle subtracts the nominal per
phase power factor angle (which may vary depending on the service
type and phase rotation) from the actual per phase power factor
angle. This allows a single threshold angle to be used for comparison
purposes on all phases, and all service types and rotations.
Stored value: The normalized power factor phase angle for the first
phase that files the test

*The specified normalized power factor angle threshold is expected


to be leading (negative), but lagging (positive) angles are allowed for
special conditions where actual loads are expected to be significantly
lagging. The test will still fail if an actual normalized PF angle is less
(more leading) than the specified normalized power factor angle
threshold, even if the angle and the threshold are both lagging
(positive) angles. But the user should beware that use of lagging
angles would generally be a source of false failures.
To prevent the monitor from creating a false alarm from legitimate
leading PF phase angles, the recommended qualification time is 15
minutes.
Note: When a magnet begins to saturate a current sensor core, it
causes a leading phase shift in the output of the current sensor.
Most loads are unity to lagging, so a leading power factor phase
angle is unusual. This test looks for that shift at some (typically)
leading phase angle to detect the possible presence of a magnet
tamper condition. If however, there are legitimate leading power
factor load conditions, the test should either be disabled or have the
threshold set to a more leading value.

100
TM42-3060

Example 1
For a 3-element 4wire wye service, with PF phase angles of:
 Phase A = 12°
 Phase B = 340° = -20°
 Phase C =16°
All normal PF angles are 0 degrees, so normalized PF angles are:
 Phase A = 12° – 0° = 12°
 Phase B = -20° – 0° = -20°
 Phase C = 16° – 0° = 16°
Only the normalized Phase B angle is less than the -15° threshold,
so this will fail because of Phase B.
Example 2
For a 3-element 4-wire delta service with CBA phase rotation, with PF
phase angles of:
 Phase A = 342° = -18°
 Phase B = 10°
 Phase C =16°
The normal PF angles under polyphase unity PF conditions for
Phases A, B and C respectively are 330°, 30° and 0°. So normalized
PF angles are:
 Phase A = 342° – 330° = 12°
 Phase B = 10 - 30° = -20°
 Phase C = 16° – 0° = 16°
Only the normalized Phase B angle is less than the -15° threshold,
so this will fail because of Phase B.

Magnetic detection (PF angle differences)


Supported devices: A3 ALPHA
Test sets: Tamper detect

Formula: If [ (Maximum qualified normalized phase PF angle -


minimum qualified normalized phase PF angle) > specified PF angle
differences ]
Variable: 0 degrees to 180 degrees
Default value: 20 degrees
Configuration based on: Specialized normalized PF angle differences
threshold (configured in the Service Test component)
Description:
All qualified normalized phase PF phase angles are checked to find a
maximum value, and a minimum value. If the difference between

101
Components and programs

the maximum minus the minimum is greater than a user specified


normalized PF phase angle difference threshold, then the test fails.
To be a qualified phase PF phase angle, the real energy (Wh) flow for
that phase must be in the delivered direction. If it is, then the rms
current for that phase is checked to insure that it is greater than a
user defined minimum test phase current threshold (as a percentage
of Class Amps, and defined in the service current threshold settings).
If it is, then the angle is considered qualified, and the normalized
power factor angle is tested to see if it is the maximum or minimum
normalized phase PF angle.
Normalization of a power factor angle subtracts the nominal per
phase power factor angle (which may vary depending on the service
type and phase rotation) from the actual per phase power factor
angle. This allows the different per phase power factor angles for all
different service types and rotations to be treated in a similar
manner with respect to each other.
To prevent the monitor from creating a false alarm from legitimate PF
phase angle differences, the recommended qualification time is 15
minutes.
Note: When a magnet begins to saturate a current sensor core, it
causes a leading phase shift in the output of the current sensor.
Most loads are unity to lagging, so a leading power factor phase
angle is unusual. However, if the load is significantly lagging then the
tampering may not cause the current signal to go far enough leading
to fail the previous test. But magnet location is very important in the
saturation of CT cores, so if the magnet is close to one current
sensor then that current sensor may be greatly affected, but an
adjacent current sensor may not be affected much or any. So this
test assumes that the polyphase loading on all phases is roughly
equivalent (amount of phase shift on each phase), and so it looks for
a difference in the normalized PF angle for each phase and checks to
see if one is significantly different from another, which may indicate
the possible presence of a magnet tamper condition. If however,
there are legitimate reasons for significantly different phase loadings
(different power factor load conditions), the test should either be
disabled, or have the threshold set to a larger difference value.
Stored value: The normalized power factor phase angle difference
(always a positive value)
Example 1
For a 3-element 4wire wye service, with PF phase angles of:
 Phase A = 12°
 Phase B = 340° = -20°
 Phase C =16°
All normal PF angles are 0 degrees, so normalized PF angles are:
 Phase A = 12° – 0° = 12°
 Phase B = -20° – 0° = -20°
 Phase C = 16° – 0° = 16°

102
TM42-3060

Minimum Normalized PF Angle is -20°. Maximum Normalized PF


Angle is 16°. Difference is 16° - -20° = 36° which is greater than
the 20° threshold, so this test will fail.
Example 2
For a 3-element 4-wire Delta service with CBA phase rotation, with PF
phase angles of:
 Phase A = 342° = -18°
 Phase B = 10°
 Phase C =16°
The normal PF angles under polyphase unity PF conditions for
Phases A, B and C respectively are 330°, 30° and 0°. So normalized
PF angles are:
 Phase A = 342° – 330° = 12°
 Phase B = 10 - 30° = -20°
 Phase C = 16° – 0° = 16°
Minimum normalized PF angle is -20°, maximum normalized PF
angle is 16°. Difference is 16° - -20°= 36°, which is greater than
the 20° threshold, so this test will fail.

% total harmonic distortion current test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (all)

Formula: (IL1 or IL2 or IL3)% THD current ≥ specified THD


current threshold
Variable: 0.0% to 99.9% of the fundamental current
Default value: 30.0% of the fundamental current (per phase)
Configuration based on: A specified THD percentage
Description:
As the load on electrical systems becomes more saturated with
electronic control devices (such as computers and communications
systems), there is a growing concern with the harmonics that these
devices can contribute to the electrical system. Total harmonic
distortion (THD), expressed as a percentage of the fundamental, is a
measurement of the power quality of the circuit under these
conditions.
The THD current test measures the per phase THD current and can
alert the utility to conditions that may be harmful or dangerous to the
system or other equipment. The threshold is defined as a percentage
of the fundamental. The test fails if any phase exceeds the threshold.

Note: When there is no current on a phase, the THD result may


generate an artificially large value since the calculation involves
dividing by the fundamental current (which is or is approaching

103
Components and programs

zero). Use of total demand distortion gives a better indication of


the actual magnitude of current distortion.
Stored value: Phase A/Line 1 THD (even if any other phase causes
the test to fail)

% total harmonic distortion voltage test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (all)

Formula: (VL1 or VL2 or VL3)% THD voltage ≥ specified THD


voltage threshold
Variable: 0.0% to 99.9% of the fundamental voltage
Default value: 30.0% of the fundamental threshold (per phase)
Configuration based on: A specified THD percentage
Description:
As the load on electrical systems becomes more saturated with
electronic control devices (such as computers and communications
systems), there is a growing concern with the harmonics that these
devices can contribute to the electrical system. Total harmonic
distortion (THD), expressed as a percentage of the fundamental, is a
measurement of the power quality of the circuit under these
conditions.
The THD voltage test measures the per phase THD voltage and can
alert the utility to conditions that may be harmful or dangerous to the
system or other equipment. The threshold is defined as a percentage
of the fundamental. The test fails if any phase exceeds the threshold.

Note: When a phase voltage is missing, the THD can be


artificially large since the calculation involves dividing by the
fundamental voltage (which is or is approaching zero). However,
If a phase voltage is lost, other PQM/TRueQ failures will also be
incurred.
Stored value: Phase A/Line 1 THD voltage (even if any other phase
causes the test to fail)

Power factor test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula:
If lagging PF, then (PFL1 or PFL2 or PFL3) < specified lagging
PF threshold or
If leading PF, then (PFL1 or PFL2 or PFL3) < specified leading
PF threshold

104
TM42-3060

Variable: 0.00 to 1.00 for the minimum lagging power factor with
ABC/L1-L2-L3 rotation (per phase); 0.00 to 1.00 for the minimum
leading power factor with ABC/L1-L2-L3 rotation (per phase)
Default value: 0.20 for the minimum lagging power factor with
ABC/L1-L2-L3 rotation (per phase); 0.20 for the minimum leading
power factor with ABC/L1-L2-L3 rotation (per phase)
Configuration based on: Specified threshold for leading and lagging
power factors
Description:
This test checks the power factor for any deviation beyond the
programmed threshold. This monitor may be used alone to monitor
rate-based conditions in conjunction with the reverse power test and
PF monitor to provide a more thorough analysis of power factor
fluctuations.
The leading and lagging thresholds are individually defined for each
phase. These settings may be different than those defined in the
service current configuration.
Per phase leading and lagging threshold values are defined
specifically for ABC/L1-L2-L3 phase rotation. If the locked service
has CBA/L3-L2-L1 rotation, then the per phase leading and lagging
thresholds are reversed (that is, the same threshold value for Line 1
minimum leading power factor with L1-L2-L3 rotation is also used as
the Line 1 lagging power factor with L3-L2-L1 rotation). Also, if the
Irms value for a given phase is less than the zero current threshold,
then no power factor failure will be reported, regardless of the
calculated power factor value (to eliminate false failures).
Stored value: None

Rapid voltage changes test


Supported devices: A1800 ALPHA
Test sets: EN 5160

Formula:
(VL1 or VL2 or VL3) < specified low voltage threshold or
(VL1 or VL2 or VL3) > specified high voltage threshold
Variable: Low voltage threshold: 80.0% to 99.9% of the nominal
service voltage; high voltage threshold: 100.1% to 120.0% of the
nominal service voltage
Default value: Low voltage threshold: 95.0%; high voltage threshold:
105.0%
Configuration based on: Specified low voltage threshold and
specified high voltage threshold
Description:

105
Components and programs

This test checks the line voltages for values that are out of range.
The line voltages must be within a specified range of the expected
nominal service voltage. The test fails if any line voltage is out of the
specified range.
Stored value: Line 1 voltage

Reverse power test and power factor test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula:
(WL1 or WL2 or WL3) < 0 or
If lagging PF, then (PFL1 or PFL2 or PFL3) < specified lagging
PF threshold or
If leading PF, then (PFL1 or PFL2 or PFL3) < specified leading
PF threshold
Variable: Based on service current test thresholds
Default value: Based on service current test thresholds
Configuration based on: Service current test thresholds
Description:
This test recognizes any condition where the current transformer may
be wired incorrectly or where tampering may have occurred. The
power factor (PF) threshold in this test is typically set to a very low
value to detect only abnormal conditions.
The PF thresholds are defined with the system service current test
definition. Using the service current test definition permits
independent PF settings to be set for each service type. Each service
type can have individual leading and lagging thresholds for each
phase.
Per phase leading and lagging PF threshold values are defined in the
system service current test specifically for ABC/L1-L2-L3 phase
rotation. This permits independent PF thresholds for each service
type. If the locked service has CBA/L3-L2-L1 phase rotation, then the
per phase leading and lagging thresholds are reversed (that is, the
same threshold for Phase A/Line 1 minimum leading PF with
ABC/L1-L2-L3 rotation is also used as the Phase A/Line 1 minimum
lagging PF for CBA/L3-L2-L1 rotation).
Also, if the Irms value for a given phase is less than zero current
threshold, then no power factor or reverse energy failure will be
detected from that phase (to eliminate false failures).
Stored value: None

Second harmonic current


Supported devices: A3 ALPHA; A1800 ALPHA

106
TM42-3060

Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula: (IL1 or IL2 or IL3)% 2nd harmonic current ≥ specified


% 2nd harmonic current threshold
Variable: 0.00% to 100.00%
Default value: Transformer rated: 2.50% of Class amperes/ Imax
(per phase); self-contained/direct-connect: 1.25% of Class
amperes/Imax (per phase)
Configuration based on: A specified current threshold
Description:
This test checks for the presence of second harmonic current. The
second harmonic current may be created by equipment on the line or
may indicate the presence of DC on the system. The threshold is
defined as the percentage of the 2nd harmonic AC amperes with
respect to the meter Class amps/Imax. The test fails if any phase
exceeds the threshold.
To prevent the monitor from creating a false alarm from legitimate
second harmonic current sources, the recommended qualification
time is 15 minutes.
Stored value: Phase A/Line 1 second harmonic magnitude (even if
any other phase causes the test to fail)

Service voltage test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (all)

Formula: (VL1 or VL2 or VL3) < specified low voltage threshold


Variable: Based on service voltage thresholds
Default value: Based on service voltage thresholds
Configuration based on: System service voltage test thresholds
Description:
This test continually monitors the service voltage. Voltage
fluctuations outside the programmed limits are detected and can
indicate the following:
 improper voltage transformer operation
 inappropriate transformer tap settings
 equipment failure
All voltage magnitudes and phase angles must fall within the
thresholds for locked service. The thresholds are defined by the
service voltage configuration. Programming the service voltage as a
PQM test allows it to continually run and create a log of the results.
Stored value: None

107
Components and programs

Total demand distortion test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula: (IL1 or IL2 or IL3)% TDD ≥ specified TDD threshold


Variable: 0.00% to 100.00% of Class amps/Imax (per phase)
Default value: 10.00% of Class amps/Imax
Configuration based on: Specified TDD threshold
Description:
The test checks the per phase total demand distortion (TDD) and
makes sure that the TDD is less than the threshold. TDD measures
the harmonic current distortion on each phase as a percentage of
the maximum demand load current (Class amps/Imax). Total
demand distortion gives an indication of the absolute amount of
distortion seen by a meter rather than the relative indication given by
total harmonic distortion.
Stored value: Phase A/Line 1 % TDD (even if any other phase causes
the test to fail)

Voltage imbalance test


Supported devices: A3 ALPHA; A1800 ALPHA
Test sets: A3 ALPHA (all); A1800 ALPHA (Default, Enhanced, IEEE)

Formula:

Variable: Minimum voltage threshold: 0.00% to 100.00% of the


nominal; Imbalance threshold: 0.00% to 100.00%
Default value: Minimum voltage threshold: 80.00% of the nominal;
Imbalance threshold: 90.00%
Configuration based on: Minimum high voltage threshold and
imbalance threshold
Description:
This test checks for an imbalance between phase voltages. The test
first measures and normalizes each per phase voltage. The voltages
are normalized to account for different per phase nominal voltages
as specified by the locked service. To qualify as a failure, both the
following conditions must exist:
 The highest normalized per phase voltage must be greater than
the minimum voltage threshold

108
TM42-3060

 The ratio of the lowest normalized per phase voltage to the


highest (low/high) must be less than the imbalance threshold

This calculation methodology does not meet the IEEE 1159


definition; however, this calculation methodology does allow a valid
calculation to be performed on any polyphase service even with
single phase voltage excitation which is not possible using the IEEE
1159 definition.
The minimum voltage threshold is defined as a percentage of the
nominal voltage, and the imbalance threshold is a percentage.
Stored value: None

Voltage interruptions test


Supported devices: A1800 ALPHA
Test sets: EN 5160

Formula: (VL1 or VL2 or VL3) < specified low voltage threshold


Variable: 1.0% to 90.0% of the nominal service voltage
Default value: 1.0% of the nominal service voltage
Configuration based on: Specified low voltage threshold
Description:
This test checks the line voltages for values that drop below a
specified limit. The threshold is defined as a percentage of the
expected nominal service voltage. The test fails if all line voltages
drops below the threshold.
Stored value: Line 1 voltage

RATES COMPONENT
Using the Rates component, you can set the day types and switch
times.
 Day types: assign the type to each day of the week (weekday,
weekend, or holiday)
 Switch times: assign the switch times for the rates that the meter
supports.
A The A3 ALPHA meter, IP AxisLink device, and REXUniversal meter
support up to 80 switch times
B The A1800 ALPHA meter supports up to 132 switch times

A3 ALPHA, A1800 ALPHA, and IP AxisLink Rates components are


always compatible with each other. The REXUniversal meter has
different capabilities than the remaining meter families. When you
create a Rates component from the start (that is, by selecting File >
New > Component) for the A3 ALPHA, A1800 ALPHA, or IP AxisLink

109
Components and programs

device, Metercat will ask if you want to maintain compatibility


between all the meter families.
 If you select Yes, then you can use the component in any
program regardless of the meter family. To maintain
compatibility across all meter families, certain parameters
become unavailable.
 If you select No, then you must the Rates component in the A3
ALPHA, A1800 ALPHA, and IP AxisLink devices. The Rates
component created will not be compatible with the REXUniversal
meter.

Note: The REXUniversal meter Rates component, which is a


subset of the A3 ALPHA/A1800 ALPHA/IP AxisLink component, is
always compatible with the rest of the meter families.

Switch times
Switch times are the times that the meter will change from one rate
(or tier) to another. Using the Switch Times tab, you can configure the
time a new rate starts, and whether the new rate is energy or
demand (or both). You can define rates by season as well. For
example, you can configure that during the summer, a new weekday
rate (Rate D) starts at 07:00. You can also configure that during the
winter, a new weekday rate (Rate D) starts at 08:00.
 Seasons are defined in your System Preferences (Dates and
Rates Options).
 Day Types are defined in the Rates Component in the Day Types
tab (see below in this topic).
When configuring the rates for a REXUniversal meter, there will be
limitations to the options as noted in the table below. If the
component maintains compatibility between all meter families, then
the A3 ALPHA/A1800 ALPHA/IP AxisLink components will follow
these REXUniversal meter restrictions.
Item Description
When this item is in a checked state,
it indicates that the component is
compatible across all devices. When
this item is in an unchecked state,
you must check the meter family to
Component maintains compatibility
make sure you are configuring the
between A3 ALPHA, A1800 ALPHA, IP
correct Rates component for your
AxisLink, and REXUniversal meter
desired program.
families
If the check box is not present, then
the component was created by
specifying a REXUniversal meter
component, which is compatible with
all meter families.
REXUniversal meter: supports 4
seasons. If you define more than 4
Number of seasons seasons in the Dates and Rates
Options, then the REXUniversal meter
uses the first 4 listed seasons.

110
TM42-3060

All other meter families: If you define


more than 4 seasons in the Dates
and Rates Options, select how many
seasons to use when defining the
rates. For example, if your utility has
8 seasons, then select 8 in the drop
list.
Default rate
[Note 1]For A3 ALPHA meters up to
version 3.0, the meter is programmed
at the factory to use Rate C as the
If real time is lost in the meter, then
default rate. This cannot be changed.
upon power restoration, the meter will
use the default rate until such time
[Note 2]If you execute a Replace
that the meter regains real time and
Rates and Dates task with an
has the correct rate.
effective date that is in the future,
If so configured, the default rate
and you are changing the default
begins at midnight (see next item).
rate, the switch time default rate is
REXUniversal meter: the default rate
changed. However, the power fail
must be Rate C.
default rate is not changed.
All other meter families: select the
The default rate used after an
rate you want to use for the default
extended power fail can only be
rate.
changed by reprogramming the
meter or by executing a Replace
Rates and Dates task that is effective
immediately.
If checked, the meter will
automatically switch to the
programmed default rate at midnight
for all day types and all seasons.
Automatic midnight switches will use
16 switch times.
The Dates and Rates Options can
control whether or not midnight
switches are generated for all rates
Automatically generate midnight
components. If the Dates and Rates
switches
option is configured, then the option
in the Rates component may be both
checked and grayed out.
REXUniversal meter: the REXUniversal
meter always uses a midnight switch.
All other meter families: if available,
check the box to automatically
generate midnight switches in this
particular component.

When you add a switch time, you must specify the following
information:
 Season: You can configure a rate's start time by Day Type for a
particular season. In the Season column, select the effective
season for the new rate.
 Day Type: You can configure on what day type (weekday,
weekend, holiday, or special) that the rate's start time will start
on.

111
Components and programs

 Start Time: Enter the time that the rate will start, using 24-hour
notion. If you set a time that doesn't end on the hour (for
example, 14:00), then the minute-boundary must end in 0 or 5.
For example: you can specify times such as 14:05, 14:10,
14:15, 14:20, 14:25, etc.
 Switch Type: You can configure which kind of rate the new rate
is for. You can select a demand only rate, an energy only rate, or
an energy and demand rate. Note: the REXUniversal meter
supports only an energy and demand rate.

Note: You create a switch time at midnight (00:00) that uses a


non-default rate. At midnight, a specified rate will be used,
overriding the default rate.

Day types
Using the Day Types tab, you can specify how each day of the week
(Sunday, Monday, Tuesday, etc.,) is treated as well as how a holiday
is treated. Each day can be specified to be a weekend, a weekday, a
holiday, or a special day type.
You must also specify each day type for each of the seasons you are
creating. Seasons are controlled by the Dates and Rates Options as
well as the Number of Seasons box in the Switch Times tab.
By default, Metercat specifies the following for each season:
 Sunday and Saturday are specified as Weekend day types.
 Monday, Tuesday, Wednesday, Thursday, and Friday are
specified as Weekday day types.
 Holiday is specified as a Holiday day type.

RELAY OPTIONS COMPONENT


Using the Relay Options component, you can configure how the A3
ALPHA meter and the A1800 ALPHA meter relay outputs.
 The A3 ALPHA meter supports the installation of option boards,
and option boards can include relay outputs. The meter supports
up to 6 relays, depending on the communications options being
used. See Relay wiring diagrams and the A3 ALPHA meter
technical manual for more information.
 The A1830 ALPHA meter and higher supports 4 relays. See Relay
wiring diagrams and the A1800 ALPHA meter technical manual
for more information.
Your meter may be equipped with special relay operation. For
example, your A3 ALPHA meter may have the DA I/O option board
installed or your A1800 ALPHA meter may have an interposing relay.
Use the Special Relay tab to configure relays other than Relays A, B,
C, D, E, or F.

Relay A through Relay F

112
TM42-3060

Relay drivers

All relay outputs are fully programmable using Metercat. Sources for
relay outputs are listed below, with the labels used in the technical
manuals listed in parentheses.
Relay source Relay output specification
Disabled None
A3 ALPHA meter: For each Ke
transition of the selected basic
metered quantity, the relay will do
either of the following: toggle (that is,
turn on and off) or pulse for a specific
KYZ output length of time
(Energy pulse) A1800 ALPHA meter: For each pulse
of the selected basic metered
quantity, the relay will do either of the
following: toggle (that is, turn on and
off) or pulse for a specific length of
time
The relay closes when the demand
exceeds the specific demand
threshold (configured in the Demand
Demand threshold component), and it remains closed for
(Load control) the duration of the interval. The relay
will open after the demand remains
below the threshold for one full
interval.
The relay closes for 5 seconds after
End of interval
the end of each interval or
(EOI indication)
subinterval.
The relay closes while demand
forgiveness (configured in the
Cold load pickup
Demand component) is in effect. The
(Demand forgiveness)
relay opens after the demand
forgiveness time has expired.
PQM failure indication
Relay closes as long as the specified
(A3 ALPHA: PQM tests failure; A1800
PQM/TRueQ tests continue to fail.
ALPHA: TRueQ tests failure)
Alarm indication The relay closes as long as the
(Specific errors, warnings, and meter specific errors, warnings, or events
events) persist.
Rate indication
(A3 ALPHA: TOU switches to a specific The relay closes for the duration of
rate; A1800 ALPHA: TOU switches to the specific rate/tariff.
a specific tariff)

Special relays
If your meter program is not using a special relay, select Disabled.

Interrupter control relay

If your A3 ALPHA meter is equipped with the interrupter control


board, you can configure the relay operation by selecting Interrupter
Control Relay from the Special Relay drop list.

113
Components and programs

Output options
The number of minutes the meter will
delay between receiving the signal to
change the state of the relay and
Cold load pickup period (minutes) when the relay state is actually
changed. The range can be between
0 (default; the state is changed
immediately) and 30 minutes.
If checked (default is not checked),
the meter will wait a randomized time
Randomize cold load pickup period between 0 and the cold load pickup
period before changing the state of
the relay.
You can choose the interrupter
control board's default relay state:

Connected
Disconnected
Default relay state Current state

If you are using the interrupter control


board in an EnergyAxis-enabled A3
ALPHA meter application, Elster
recommends that the default state =
current.

Enable inputs
Depending on the interrupter control
board supports up to 2 binary inputs.
Input 1 To enable the binary input, check the
Input 2 Input 1 or Input 2 box (or both). The
interrupter control board disregards
inputs 3 and 4.

DA I/O option board

If your A3 ALPHA meter is equipped with the DA I/O option board, you
can configure the relay operation by selecting DA I/O from the
Special Relay drop list. The DA I/O supports 2 relay outputs and up
to 4 binary inputs.
Output options
Relay 1 can be configured to operate
in an open/close mode (fully
open/fully closed) or as a pulse
mode.
Relay 1
If you specify open/close mode, Relay
1 can support a cold load pickup
period.

114
TM42-3060

If you specify pulse mode, you can


specify the width of the pulse in
milliseconds.

Relay 2 can be configured to operate


in an open/close mode (fully
open/fully closed) or as a pulse
mode.

If you specify open/close mode, Relay


Relay 2
2 does not support a cold load pickup
period.
If you specify pulse mode, you can
specify the width of the pulse in
milliseconds.

The number of minutes the meter will


delay between receiving the signal to
change the state of the relay and
Cold load pickup period (minutes) when the relay state is actually
changed. The range can be between
0 (default; the state is changed
immediately) and 30 minutes.
If checked (default is not checked),
the meter will wait a randomized time
Randomize cold load pickup period between 0 and the cold load pickup
period before changing the state of
the relay.
You can choose the interrupter
control board's default relay state:

Connected
Disconnected
Default relay state Current state

If you are using the interrupter control


board in an EnergyAxis-enabled A3
ALPHA meter application, Elster
recommends that the default state =
current.

Enable inputs
The DA I/O option board supports up
Input 1 to 4 binary inputs. If you are
Input 2 configuring the DA I/O option board
Input 3 for use in an AGI RLC polyphase
Input 4 interrupter, the DA I/O option board
supports only 2 binary inputs.

Interposing relay

If you are using an A1800 ALPHA meter with interposing relay


support, select Interposing Control Relay from the Special Relay
drop list.

115
Components and programs

Beginning with Series 200 of the A1800 ALPHA meter, the meter
supports the use of an interposing relay. By using an interposing
relay, the A1800 ALPHA meter can remotely control a ccontactor that
the meter would otherwise be unable to control directly.
Controlling an interposing relay requires configuring the meter's relay
component using Metercat version 3.2.1 or later. When enabled for
interposing relays, the functions of Relay C and Relay D are
overridden of their previous settings, and Relay C and Relay D will
only serve to control the interposing relay.
Relay C, when activated, supplies a pulse that will connect the
interposing relay. Relay D, when activated, supplies a pulse that will
disconnect the interposing relay.

For more information:


See the A1800 ALPHA meter technical manual for more information
on the operation of the interposing relay.

Global KYZ relay settings


When a relay is used to echo energy pulses for a basic metered
quantity, each pulse is equal to a specific amount of energy. Using
Metercat, there are two methods of specifying the weight of each
pulse.
It is possible to inhibit KYZ pulse outputs when the meter is in test
mode by checking the Inhibit KYZ outputs during Test Mode option.
By default, this option is unchecked.

KYZ divisor

Program the energy pulse divisor with an integer value between 1


and 999.
A3 ALPHA meter A1800 ALPHA meter
Before configuring the weight of the
energy pulse, first determine the desired
secondary value per pulse. If you are using
instrument transformers, the secondary
value can be determined as follows:

All energy outputs must be an integer


multiple of the meter nameplate Ke. If the energy pulse divisor is not an integer,
then the exact desired output is not
possible.

If the energy pulse divisor is not an


integer, then the exact desired output is
not possible.

116
TM42-3060

For transformer rated meters, the pulse


Example 1: The desired relay value is 1 constant is 40,000 pulses per kWh
Wh/pulse, and the meter nameplate Ke = Example: the desired relay constant is 1000
0.05 Wh/pulse. pulses per 1 kWh and the pulse constant is
40,000 pulses per 1 kWh:

In the KYZ Divisor text box, type 20.


In the KYZ Divisor text box, type 40.
Example 2: The desired relay value is 1
Wh/pulse, and the meter nameplate Ke = For direct connect rated meters, the pulse
0075 Wh/pulse. constant is 4000 pulses per kWh
Example: the desired relay constant is 1000
pulses per 1 kWh and the pulse constant is
4000 pulses per 1 kWh:

In the KYZ Divisor text box, type either 13


(yielding 13 × 0.075 Wh = 0.975
Wh/pulse) or 14 (yielding 14 × 0.075 = In the KYZ Divisor text box, type 4.
1.05 Wh/pulse)

KYZ value

The KYZ Value must be enabled using Tools > System Preferences >
Programming Options. If the KYZ value is not enabled, then the KYZ
Value option is not available using Metercat.

Note: the KYZ Value method is supported in A3 ALPHA meters


beginning with meter firmware version 3.01.
Using the KYZ Value box, it is possible to specify the energy pulse
value with a value between 0.000001 kWh and 100.000000 to
represent the amount of energy per pulse (in kilo units). For example,
to have one energy pulse value represent 2 Wh (0.002 kWh), you
would specify a KYZ Value of 0.002.

Note: The KYZ Value method may result in a pulse rate that will
be irregular over a short period but will be accurate over a longer
period. Elster recommends that the KYZ Value method should
not be used when verifying meter accuracy.

KYZ relay activation type

You can specify whether the relay is a toggle or whether it is a pulse.


If you select pulse, you can also specify the width of the pulse in
milliseconds.

117
Components and programs

REMOTE COMPONENT
The Remote component allows you to configure the communication
ports of the A3 ALPHA or A1800 ALPHA meter when equipped with
remote communications.

A3 ALPHA meter option boards


The meter supports up to 2 option boards. The following table details
the various ports and line sharing settings. Position 1 refers to the
option board connected to the main meter board. Position 2 refers to
the option board installed on top of the option board in Position 1. An
option board's physical location does not necessarily correspond to
the logical COM port number. For example, an ITM2 option board
may be in Position 2 but be logically connected to Remote Port 1.
Certain option boards also require additional configuration in the
Special Option Board component, and they are as follows:
 ACB option board 1.2 & 1.3; ACB option board version 3.7 (DNP)
 Ethernet WIC version 2.x; version 3.x; version 4.x
 Itron 50ESS ERT
 Wireless WIC (CDMA) versions 1.0 - 1.2; version 1.4; version 2.0
 Wireless WIC (CDMA/GSM) version 3.x

Communication Option board position Remote component Enable line


type Position 1 Position 2 Port 1 Port 2 sharing?
Internal
Internal None Disabled No
ITM3 option modem
telephone
board Internal
modem (ITM3) Relays Disabled No
modem

118
TM42-3060

RS-485 Internal
(modem modem
Disabled Yes
sharing (Device
unit) ID = 1)
No (noteA3
ALPHA meter
can
RS-485 or Internal
communicate
RS-232 modem Direct
simultaneously
(external (Device connect
on port 1 (over
device) ID = 1)
ITM3) and port
2 (over RS-
232/435))
Direct
Gatekeeper Internal connect
Yes
module modem (bps =
9600)
Internal Modem
Internal
telephone interface ITM2 Disabled No
modem
modem (ITM2) board
Direct
None (bps Disabled No
Advanced =28800)
communication ACB 2.x Direct Direct
board (ACB 2.x) Gatekeeper connect connect
No
module (bps = (bps =
28800) 9600)
External
modem
None Disabled No
(bps =
ACB 2.x with 28800)
ACB 2.x
alarm reporting External Direct
Gatekeeper modem connect
No
module (bps = (bps =
28800) 9600)
Direct
connect
None Disabled No
(bps
Ethernet WIC =28800)
E-WIC
(E-WIC) Direct Direct
Gatekeeper connect connect
No
module (bps = (bps =
28800) 9600)
Direct
connect
None Disabled No
(bps
=28800)
WIC (serial) WIC (serial)
Direct Direct
Gatekeeper connect connect
No
module (bps = (bps =
28800) 9600)
Direct
connect
Wireless WIC W-WIC None Disabled No
(bps =
9600)

119
Components and programs

Direct Direct
Gatekeeper connect connect
No
module (bps = (bps =
9600) 9600)
Direct
Gatekeeper Direct connect
RS-232 RS-232 No
module connect (bps =
9600)
Additional Direct
option connect
EA_NIC Disabled No
board is (bps =
installed 9600)
EA_NIC No
Direct
additional
connect
option EA_NIC Disabled No
(bps =
boards
9600)
installed
MSU support External
for meters RS-232 or modem
None Disabled N/A
(note) RS-485 (device
ID = 1)
Meters
connected
over RS-485
to external
modem;
master
Direct
meter with RS-485 None
connect
Disabled N/A
RS-485
connected to
an external
modem;
slave meters
with RS-485

A3 ALPHA meters with third party option boards


Enable line
Installed option Remote port 1 Remote port 2
sharing?
Itron 50ESS ERT
Requires
configuration in Direct connect
Disabled No
the Special (bps = 9600)
Option Board
component
Direct connect
SmartSynch Disabled No
(bps = 9600)
Direct connect
AMRON M5 CIB Disabled No
(bps = 9600)

120
TM42-3060

Aclara TWACS Direct connect


Disabled No
UMT-C-A3 (bps = 9600)
Sensus FlexNet Direct connect
Disabled No
RF (bps = 9600)
SilverSprings Direct connect
Disabled No
Network (bps = 9600)
Ladis+Gyr Direct connect
Disabled No
Gridstream (bps = 9600)

A1800 ALPHA meter port options


The following port assignments are recommended combinations for
the A1800 ALPHA meter Remote component:
Port 1 Port 2
Disabled Disabled
Disabled
Direct connect Direct connect
External modem
Disabled
Internal modem Direct connect
External modem
Disabled
External modem Direct connect
External modem

While Metercat will allow the following port assignments, Elster does
not recommend using the following because they may result in
unexpected results:
Port 1 Port 2
Direct connect
Disabled Internal modem
External modem
Direct connect Internal modem
External modem Internal modem

If configuring the A1800 ALPHA meter as a node within the


EnergyAxis System:
Installed Remote port Remote port Enable line
Meter
option 1 2 sharing?
Direct
nA1810 EA_NIC connect (bps Disabled N/A
= 9600)
Direct Direct
nA1830 EA_NIC connect (bps connect (bps N/A
= 9600) = 9600)

Configuring the Remote component


To help with configuring the Remote component, Metercat provides
sample components that you can use as a basis for creating your
own components (see New Component as Copy):

121
Components and programs

 Sample 50ESS Remote component: an example of configuring


an A3 ALPHA meter with an Itron 50ESS ERT option board
 Sample ICM Remote component: an example of configuring an
A3 ALPHA meter with the internal cellular modem option board
 Sample LAN collector Remote component: an example of
configuring an A3 ALPHA meter with the ITM3 option board and
the EA_Gatekeeper module
 Sample Remote component: an example of configuring the A3
ALPHA or A1800 ALPHA meter with the ITM3 option board

Note: If you do not see the sample components listed, they are
available on the Metercat installation disc.

Direct connections

When configuring a port for direct connect, the following parameters


are available:
Item Description
You can select the following
protocols:

 ANSI
 DLMS and ANSI
 DLMS
 DCPM
Protocol
The A3 ALPHA meter supports only
the ANSI protocol.
The A1800 ALPHA meter supports all
the listed protocols. Be sure that the
protocol is compatible with the meter
firmware version. See the A1800
ALPHA meter technical manual
(TM42-2410) for more information.
If checked, the meter will only allow
the selected port to be used for
reading the meter. This restriction
applies even if the connecting device
or system has a valid meter
Port permits read services only
password.
If cleared, the meter will allow the
selected port to be used for reading
and configuring the meter, provided
correct meter passwords are used.
You can select bit rate speeds of 300
bps to 28,800 bps. The tables listed
Bit rate in the sections above contain the
recommended bit rate speeds for
your communication solution.

If you click Advanced, the following options are displayed:

122
TM42-3060

Item Description
The turnaround delay is the minimum
length of time between the last byte
of data received and the ACK
character is transmitted by the meter.
Turnaround delay
This parameter is typically needed for
half-duplex media (radio frequency).
The delay can be in a range of 0.0 to
25.0 seconds (default = 0.0).
C12.21 communications has a typical
response timeout of 4 seconds. By
checking this box, the response
Enable large timeouts
timeout increases to a total of 15
seconds.
The default is unchecked.

Modem connections

The A3 ALPHA and A1800 ALPHA meters have many different


parameters that can support both internal modem and external
modem communications, including call origination window times, line
sharing capabilities, off-hook and intrusion detection, and alarm
calling.
See the Elster model product guide (PG42-1006) for detailed
information on configuring the modem connection parameters using
the ANSI protocol.

Note: Outage call support is only supported in the meter if the


ITM3 option board is installed and the meter is configured to
support outage reporting.
The A1800 ALPHA meter supports the DL/T 645 protocol for modem
communications. The A1800 ALPHA meter must support the Virtual
Option Board (also referred to as the DCPM). See the A1800 ALPHA
meter technical manual (TM42-2410F or later) for information
regarding the DL/T 645 protocol using the Virtual Option Board.
To configure the Remote component to support DL/T645:
Select DCPM as the Port 1 or Port 2 protocol. The DCPM tab is
displayed.
In the DCPM Protocol drop box, select DLT 645 Version 1.x.
Complete the DCPM tab with the appropriate values for your desired
parameters.

SERVICE TEST COMPONENT


The Service Test component allows you to configure the service test
parameters for the A3 ALPHA and A1800 ALPHA meters. Service
tests can be performed to determine the validity of the electrical
service that is being metered. The service tests consist of the service
voltage test and the service current test.

123
Components and programs

About the system service voltage test


For the service voltage test, the meter measures each phase voltage
and phase voltage angle and attempts to match the measurements
to a stored list of valid services.
 If the service voltage test is successful, the validated service
shown on the meter's LCD and the meter will continue to the
next display item in the display list sequence.
 If the service voltage test fails, a warning is set. The LCD will
display a service voltage test error (see A3 ALPHA meter codes or
A1800 ALPHA meter codes).
The following conditions can cause the service voltage test to fail:
 phase voltage angles not within the ±15° of the expected
service phase angles
 phase voltage magnitudes not within the tolerance of the
nominal service configured into the meter using Metercat

About the system service current test


The service current test validates the system currents.
 If the service current test is successful, SYS PASS is shown on
the meter LCD and the meter will continue to the next display
item in the display list sequence.
 If the service current test fails, a warning is set. The LCD will
display a service current test error (see A3 ALPHA meter codes or
A1800 ALPHA meter codes).
The following conditions can cause the service current test to fail:
 current remains on one phase while no current is on any other
phase
 current on any single phase is below the programmed low
current limit
 current on any phase is greater than the programmed absolute
maximum
 current is negative on any phase (reverse power)
 power factor on any phase is less than the limit set for leading or
lagging power factor
If all phases are below the absolute minimum current threshold, the
low and missing current failure will not be reported. It is assumed
that this is a valid, noload condition. The exception to this
assumption is for a 1-element meter. In this case, the low and zero
current warnings will display if the condition exists.

Using Metercat to configure the Service Test component


The basic settings are the default settings for the service voltage test
and service current test and will be applied to all services. Using the
Advanced Settings tab, you can specify different parameters for the
desired configurations and services.

124
TM42-3060

Basic settings panel

Service test mode Description


When selected, the meter will attempt to lock the
service automatically once the service is
determined to be valid. Both the voltage magnitude
and the phase angle of the service are compared to
a table of valid relationships stored within meter
memory. The meter accepts the service that most
closely matches one of the stored values in the
meter.
The meter periodically checks the service. Under
certain conditions (for example, the meter moved to
a new service), the smart autolocked service may
lock on a different service. The service voltage test
Smart autolock will be performed and the service may be changed
in response to the following:

power up
exit of test mode
after data-altering communication session

If a new, valid service is detected, the meter locks


on the new service. If a valid service cannot be
detected, the meter will remain locked on the last
known valid service and display an error code (see
A3 ALPHA meter codes or A1800 ALPHA meter
codes).
When selected, the meter will detect and evaluate
the service in the same manner as the smart
autolock. The identified service will be displayed on
the LCD; however, the RESET button must be
Manual pressed to lock the detected service.
Once manually locked, the service will never
automatically unlock. The service must be unlocked
before moving the meter to a new service. The new
service can then be detected and manually locked.
The service is not locked. The meter will not
perform system service tests. PQM/TRueQ tests are
None
also disabled because PQM/TRueQ tests require a
valid locked service.

Rotation test Description


Both The meter will accept either phase rotation as valid.
ABC only The meter will only accept ABC (or L1-L2-L3)
(also L1-L2-L3 rotation) rotation as valid rotation.
CBA only The meter will only accept CBA (or L3-L2-L1)
(also L3-L2-L1 rotation) rotation as a valid rotation.

Check the Run current test after powerup voltage test to have the
meter automatically perform a service current test after a service
voltage test following a power restoration. The default is checked.

125
Components and programs

Phase indicator
Description
threshold
If the voltage for a phase drops below the threshold
(defined as a percentage of the nominal voltage),
Percent of nominal
then the corresponding potential indicator on the
meter's LCD will blink.

Default current test


Description
thresholds
If the current drops below this threshold, the meter
rounds the current to zero. The threshold is a
Zero current
percentage of the meter Class. The range is
between 0.00% and 39.99% (default = 0.05%).
If the meter detects current on a phase that
exceeds this threshold, the meter will trigger the
service current test to fail and display an error on
the LCD (see "System service error codes" in A3
Over current
ALPHA meter codes or A1800 ALPHA meter codes).
The threshold is a percentage of the meter Class.
The range is between 100.00% and 199.95%
(default = 110.00%).
If the meter detects a phase drop below the per
phase low current threshold, the meter will trigger
the service current test to fail and display an error
on the LCD (see "System service error codes" in A3
ALPHA meter codes or A1800 ALPHA meter codes).
The threshold is a percentage of the meter Class
amps.
Low current
If all phases are below the minimum current
threshold, the low and missing current failures will
not be reported. Instead, it is assumed that this is a
valid, no-load condition (except for single phase
meters).
The per phase range is between 0.00% to 39.99%
(default = 0.10% per phase).
Min lagging PF (ABC
order)
noteIf CBA rotation, the
minimum lagging and
minimum leading The minimum lagging power factor threshold below
thresholds are which a lagging power factor will cause a low power
reversed. That is, the factor service current test failure (see "System
min lagging PF value is service error codes" in A3 ALPHA meter codes or
used as the threshold A1800 ALPHA meter codes).
for leading PF.
Likewise, min leading
PF value is used as the
threshold for lagging.
Min leading PF (ABC
order) The minimum leading power factor threshold below
noteIf CBA rotation, the which a lagging power factor will cause a low power
minimum lagging and factor service current test failure (see "System
minimum leading service error codes" in A3 ALPHA meter codes or
thresholds are A1800 ALPHA meter codes).
reversed. That is, the

126
TM42-3060

min lagging PF value is


used as the threshold
for leading PF.
Likewise, min leading
PF value is used as the
threshold for lagging.

Default magnetic
detection test Description
thresholds
The threshold used in the Magnetic detection
Nominal power factor (leading PF angle) PQM test to indicate possible
angle threshold tampering. The range is between -90 to 90 (default
= -15).
The threshold used in the Magnetic detection (PF
Nominal power factor
angle differences) PQM test to indicate possible
angle difference
tampering. The range is between 0 and 180
threshold
degrees (default = 20 degrees).
The minimum phase current required for the
Minimum test phase
Magnetic detection (leading PF angle) PQM test to
current
be performed.

Advanced settings panel

Using the Advanced Settings tab, you can configure thresholds,


warnings, and recognized nominal voltages for each meter service.
You can specify up to 10 services for each configuration.
 For 1-element meters
o 1 EL single phase
 For 2-element meters
o 2 EL single phase
o 2 EL 3-phase single phase
o 2 EL 3-wire delta
o 2 EL 3-wire wye (network)
o 2 EL 4-wire delta
o 2 EL dual single phase "star"
 For 2½-element meters
o 2½ EL 4-wire wye
o 2½ EL single phase
 For 3-element meters
o 3 EL 4-wire wye
o 3 EL 4-wire delta
o 3 EL single phase

127
Components and programs

o 3 EL 4-wire delta high leg on Phase A


o 3 EL 4-wire delta high leg on Phase B
 For portable meters
o 3 EL 4-wire wye
o 3 EL 4-wire delta
o 3 EL single phase
o 3 EL 4-wire delta high leg on Phase A
o 3 EL 4-wire delta high leg on Phase B
o 2 EL single phase
o 2 EL 3-phase single phase
o 2 EL 3-wire delta
o 2 EL 3-wire wye (network)
o 2 EL 4-wire delta
o 2 EL 4-wire delta high leg on Phase A
o 1 EL single phase
To specify or change the available services for each configuration:
Select the desired configuration in the Meter Configuration panel.
In the list of services, click in a cell in the Service column. Metercat
will display a drop list indicator.
Click on the drop list indicator and select the desired service. You
may also select None to not configure the voltage or current
parameters for the service.
Voltages tab
Item Description
Phase voltage Indicates the expected per phase value based on
percentage the selected service
Indicates the expected voltage phase angles
Voltage phase angles (assuming ABC rotation) based on the selected
service
For each service, you can specify up to 5 nominal
Recognized nominal service voltage values. The range for each nominal
service voltage service voltage may be between 0 and 6553.5
volts.

Currents tab / Thresholds


For each service, you can specify whether to use the default
thresholds (as configured in the Basic Settings panel) or to use
different thresholds for the service. Clear the Use Default Current
Thresholds or the Use Default Magnetic Test Thresholds (as
appropriate) and enter the desired values.
Currents tab / Warnings
For each service, you can specify whether the service triggers a
warning for each of the listed events. The warnings can be configured

128
TM42-3060

on a per phase basis for each desired service type. The default is
checked.

SPECIAL DATES COMPONENT


Special dates are the collection of dates that use different switch
times than be normally used or dates that special events occur.
Special dates address the following items:
 holidays
 season changes
 start of DST
 end of DST
Special dates can be recurring (have a predictable, repeatable
pattern) or nonrecurring (have no predictable, repeating pattern).
A3 ALPHA, A1800 ALPHA, and IP AxisLink Special Dates components
are always compatible with each other. The REXUniversal meter has
different capabilities than the remaining meter families. When you
create a Special Dates component from the start (that is, by selecting
File > New > Component), Metercat will ask if you want to maintain
compatibility between A3 ALPHA, A1800 ALPHA, IP AxisLink, and
REXUniversal meter families.
 If you select Yes, then you can use the component in any
program regardless of the meter family. To maintain
compatibility across all meter families, certain parameters
become unavailable.
 If you select No, then you must the REXUniversal meter's Special
Dates component can only be used in REXUniversal meter
programs. A3 ALPHA, A1800 ALPHA, and IP AxisLink Special
Dates components remain compatible with each other.

Global Options
Items in the following table that are shaded in blue are those that are
not compatible with the REXUniversal meter. If the component
maintains compatibility between all meter families, then the shaded
items are not available.
Item Description
When this item is in a checked state,
it indicates that the component is
Component maintains compatibility compatible across all devices. When
between A3 ALPHA, A1800 ALPHA, IP this item is in an unchecked state,
AxisLink, and REXUniversal meter you must check the meter family to
families make sure you are configuring the
correct Special Dates component for
your desired program.
If checked, the meter will perform a
demand reset automatically at every
Perform Demand Reset on every
season change. You do not have to
Season Change
select a demand reset for any season
change event in the Recurring Dates

129
Components and programs

tab because the demand reset will


occur automatically. By default,
demand resets occur on midnight
(00:00) on the date that the reset is
scheduled.
If checked, the meter will require that
Enforce a maximum number of days the specified number of days must
between demand resets have elapsed before the next demand
reset can be performed.
If checked, the meter will trigger an
end of calendar event in the meter
End of calendar warning number of when the meter calendar is about to
days before the end of nonrecurring expire. You can specify up to 999
dates days before the last nonrecurring
date defined in the Nonrecurring Date
tab.
Beginning with A1800 ALPHA meter
firmware version 4.0, users can
Demand reset time specify a different time (using 24-
hour time) for the A1800 ALPHA
meter to perform the demand reset.
This option is relevant for customers
who using over-the-air configuration
of REXUniversal meters as well as A3
ALPHA meters beginning with
firmware version 5.0. The OTA
configuration uses the Metercat
Endpoint Execution Request (EER)
file. To maintain compatibility with
Programming compatible with EER Metercat's EER file, this option must
export be checked to prevent a nonrecurring
dates mismatch between the Special
Dates component and the actual
meter configuration.
Otherwise, this option is
recommended to remain unchecked.
See About Special Dates for more
information about special dates and
the EER file.

Recurring special dates configuration


Add a recurring special date, click on the Recurring Dates tab (if
necessary) and click Add. The Recurring Date Configuration dialog
box will be displayed.
 If you selected an A3 ALPHA, A1800 ALPHA, or IP AxisLink
Special Dates component, and you are not maintaining
compatibility with REXUniversal meters, then Table 1 shows you
the available options for recurring dates configuration.
 If you selected to maintain compatibility with REXUniversal
meters, then Table 2 shows you the available options for
recurring dates configuration.
 If you selected a REXUniversal Special Dates component, and
you are not maintaining compatibility with the remaining meter

130
TM42-3060

families, then Table 3 shows you the available options for


recurring dates configuration.
The A3 ALPHA, A1800 ALPHA, and IP AxisLink devices can support up
to 35 recurring date entries. The REXUniversal meter can support up
to 20 recurring date entries. See About Special Dates for more
information about the meter handling of special dates.

Table 1. A3 ALPHA, A1800 ALPHA, IP AxisLink (no compatibility with REXUniversal)

Item Description
Check this box if you are creating a
calendar event (specifying a recurring
holiday, a season change, or a Daylight
Saving Time change). Leave this box
unchecked if you want to perform a self
read or demand reset that is not related
to a calendar event.

Season change choices are determined


by your System Preferences (Dates and
Calendar action
Rates Options).
Metercat does not check to ensure the
events for these entries do not conflict.
For example, Metercat allows DST Start
and DST End dates to occur
simultaneously. Also, Metercat does not
check to see if DST events are paired
(that is, each DST Start has a
corresponding DST End).

Check this box to perform a self read at


midnight (00:00) on the date of the
recurring event.
Note: If Special Features component is
Self Read
set to always perform a self read on a
demand reset, then a self read will always
be performed regardless of the state of
this check box.
Check this box to perform a demand reset
on the date of the recurring event.
Typically, the time of the demand reset is
midnight (00:00); however, A1800 ALPHA
Demand reset
meters with firmware version 4.0 or later
can specify a different time for the
demand reset, as specified in the Global
Options panel.
You can specify that the event occurs
monthly or every specific month. For
Recurring Options example, you can specify that the event
occurs the 1st day of each month or you
can specify that it occurs every March 15.
Always on this date
The event will occur on the date specified.
regardless of day of week

131
Components and programs

You can schedule the event to occur on a


specific day of week on or after specified
On the first _______ on or
date. For example, you can specify an
after this date
event to occur on the first Monday on or
after September 1.
You can specify exceptions to the event if
the event falls on a weekend day. For
example, if July 1 is on a Sunday, you can
postpone the event to Monday. You can
select the following exception handling:

If Sunday - postpone to Monday


(Example: Sunday, July 1 will be
postponed to Monday, July 2)
If Sunday - advance to Friday (Example:
Sunday, July 1 will be advanced to Friday,
June 29)
If Saturday - postpone to Monday
(Example: Saturday, November 11 will be
postponed to Monday, November 13)
If Saturday - advance to Friday
(Example: Saturday, November 11 will be
advanced to Friday, November 10)
Special rules
If Sunday or Saturday - postpone to
Monday (Example: an event scheduled on
Saturday, November 11 or on Sunday,
November 12 will be postponed to
Monday, November 13)
If Sunday or Saturday - advance to
Friday (Example: an event scheduled on
Saturday November 11 or on Sunday,
November 12 will be advanced to Friday,
November 10)
If Sun - postpone to Mon; if Sat -
advance to Fri (Example: an event
scheduled on Sunday, November 11 will
be postponed to Monday, November 12;
an event scheduled for Saturday,
November 10 will be advanced to Friday,
November 9)

If you select an event to occur weekly, you


Every week can select the day of week for the event
to occur.
You can specify an event to occur every
set number of days (from every 1 day to
Every ___ days, starting _______
every 63 days) beginning on a specific
date.

Table 2. Compatibility across all meter families

Item Description

132
TM42-3060

Check this box if you are creating a


calendar event (specifying a recurring
holiday, a season change, or a Daylight
Saving Time change). Leave this box
unchecked if you want to perform a self
read or demand reset that is not related
to a calendar event.

Season change choices are determined


by your System Preferences (Dates and
Calendar action
Rates Options).
Metercat does not check to ensure the
events for these entries do not conflict.
For example, Metercat allows DST Start
and DST End dates to occur
simultaneously. Also, Metercat does not
check to see if DST events are paired
(that is, each DST Start has a
corresponding DST End).

Check this box to perform a self read at


Self Read midnight (00:00) on the date of the
recurring event.
You can specify that the event occurs
monthly or every specific month. For
Recurring Options example, you can specify that the event
occurs the 1st day of each month or you
can specify that it occurs every March 15.
Always on this date
The event will occur on the date specified.
regardless of day of week
You can schedule the event to occur on a
specific day of week on or after specified
On the first _______ on or
date. For example, you can specify an
after this date
event to occur on the first Monday on or
after September 1.
You can specify exceptions to the event if
the event falls on a weekend day. For
example, if July 1 is on a Sunday, you can
postpone the event to Monday. You can
select the following exception handling:

If Sunday or Saturday - postpone to


Monday (Example: an event scheduled on
Saturday, November 11 or on Sunday,
Special rules November 12 will be postponed to
Monday, November 13)
If Sunday or Saturday - advance to
Friday (Example: an event scheduled on
Saturday November 11 or on Sunday,
November 12 will be advanced to Friday,
November 10)
If Sun - postpone to Mon; if Sat -
advance to Fri (Example: an event
scheduled on Sunday, November 11 will
be postponed to Monday, November 12;

133
Components and programs

an event scheduled for Saturday,


November 10 will be advanced to Friday,
November 9)

You can specify an event to occur every


set number of days (from every 1 day to
Every ___ days, starting _______
every 63 days) beginning on a specific
date.

Table 3. REXUniversal (no compatibility with A3 ALPHA, A1800 ALPHA, or IP AxisLink)

Item Description
Check this box if you are creating a
calendar event (specifying a recurring
holiday, a season change, or a Daylight
Saving Time change). Leave this box
unchecked if you want to perform a self
read or demand reset that is not related
to a calendar event.

Season change choices are determined


by your System Preferences (Dates and
Calendar action
Rates Options).
Metercat does not check to ensure the
events for these entries do not conflict.
For example, Metercat allows DST Start
and DST End dates to occur
simultaneously. Also, Metercat does not
check to see if DST events are paired
(that is, each DST Start has a
corresponding DST End).

Check this box to perform a self read at


Self Read midnight (00:00) on the date of the
recurring event.
You can specify that the event occurs
monthly or every specific month. For
Recurring Options example, you can specify that the event
occurs the 1st day of each month or you
can specify that it occurs every March 15.
Always on this date
The event will occur on the date specified.
regardless of day of week
On the first _______ on or
after this date
You can schedule the event to occur on a
On the second _______ on or
specific day of week on or after specified
after this date
date. For example, you can specify an
On the third _______ on or
event to occur on the fourth Thursday on
after this date
or after November 1.
On the fourth _______ on or
after this date
You can specify exceptions to the event if
Special rules the event falls on a weekend day. For
example, if July 1 is on a Sunday, you can

134
TM42-3060

postpone the event to Monday. You can


select the following exception handling:

If Sunday or Saturday - postpone to


Monday (Example: an event scheduled on
Saturday, November 11 or on Sunday,
November 12 will be postponed to
Monday, November 13)
If Sunday or Saturday - advance to
Friday (Example: an event scheduled on
Saturday November 11 or on Sunday,
November 12 will be advanced to Friday,
November 10)
If Sun - postpone to Mon; if Sat -
advance to Fri (Example: an event
scheduled on Sunday, November 11 will
be postponed to Monday, November 12;
an event scheduled for Saturday,
November 10 will be advanced to Friday,
November 9)

You can specify an event to occur every


set number of days (from every 1 day to
Every ___ days, starting _______
every 63 days) beginning on a specific
date.

Nonrecurring special dates configuration


A nonrecurring special date is a date that does not have a repeatable
pattern. Metercat can automatically add nonrecurring dates for
Easter (Good Friday, Easter, and the Monday following Easter) using
the System Preferences (see Holidays).
 If you select an A3 ALPHA, A1800 ALPHA, or IP AxisLink Special
Dates component, and you are not maintaining compatibility with
REXUniversal meters, then you can schedule a demand reset to
occur on a nonrecurring event.
 If you select to maintain compatibility across all meter families,
or if you select a REXUniversal only special date, then you cannot
schedule a demand reset to occur on a nonrecurring event.
The A3 ALPHA, A1800 ALPHA, and IP AxisLink devices can support up
to 255 nonrecurrent date entries. The REXUniversal can support up
to 5 nonrecurring date entries. See About Special Dates for more
information about the meter handling of special dates.
If you click on the Summary button, the Nonrecurring Dates tab will
show you the following items:
 The programming date (see About Special Dates for a discussion
on the effect of the programming date on the special dates
handling)
 How many of the meter's nonrecurring date slots you have filled

135
Components and programs

 Based on the entries in the Nonrecurring Dates tab, when the


calendar will expire
Item Description
Select the date for the nonrecurring event. The event will occur on
Date the date specified, and it cannot have any special rules (for
example, there is no support for "If Sunday - postpone to Monday").
Check this box if you are creating a calendar event (specifying a
recurring holiday, a season change, or a Daylight Saving Time
change). Leave this box unchecked if you want to perform a self
read or demand reset that is not related to a calendar event.

Season change choices are determined by your System


Calendar Preferences (Dates and Rates Options).
action Metercat does not check to ensure the events for these
entries do not conflict. For example, Metercat allows
DST Start and DST End dates to occur simultaneously.
Also, Metercat does not check to see if DST events are
paired (that is, each DST Start has a corresponding DST
End).
Check this box to perform a self read at midnight (00:00) on the
date of the recurring event.
Self
Note: If Special Features component is set to always perform a self
Read
read on a demand reset, then a self read will always be performed
regardless of the state of this check box.
Check this box to perform a demand reset on the date of the
recurring event. Typically, the time of the demand reset is midnight
(00:00); however, A1800 ALPHA meters with firmware version 4.0
Demand or later can specify a different time for the demand reset, as
reset specified in the Global Options panel.
The REXUniversal meter (including Special Dates components that
are compatible with the REXUniversal meter) does not support a
nonrecurring event performing of a demand reset.

SPECIAL FEATURES COMPONENT

Demand reset lockout


After a demand reset (regardless of the method of the demand
reset), you can program the A3 ALPHA/A1800 ALPHA meter to ignore
subsequent demand reset commands (regardless of the method) for
a specified time (in minutes). This prevents accidental or unintended
resets. You can specify a time from zero (there is no demand reset
lockout) to 255 minutes.
If a power failure occurs during the lockout period, the lockout is
released upon power restoration.

Perform a self read on every demand reset


If checked, the A3 ALPHA/A1800 ALPHA meter will always perform a
self read on every demand reset (regardless of the method of the
reset).

136
TM42-3060

Note: Using the Special Dates component, you can configure the
meter to perform a self read and/or a demand reset based on a
calendar entry. If you configure the meter to perform a self read
on every demand reset using the Special Features component,
the meter will always perform a self read regardless of the
configuration in the Special Dates component.

SPECIAL OPTION BOARD COMPONENT


The A3 ALPHA meter supports a variety of communication option
boards. You use the Special Option Board component to configure
the parameters necessary for proper operation. The Special Option
Board component supports the following option boards. Click on the
name of the option board to see the help topic for configuring the
board.
 ACB version 1.2 & 1.3
 ACB version 3.7 (DNP)
 Ethernet WIC version 2.x
 Ethernet WIC version 3.x
 Ethernet WIC version 4.x
 Itron 50ESS ERT
o See the A3 ALPHA meter with Itron 50ESS ERT product guide
(PG42-1002) and the Custom applications for the Itron
50ESS ERT product guide (PG42-1004) for more information
 Wireless WIC (CDMA) version 1.0 - 1.2
 Wireless WIC (CDMA) version 1.4
 Wireless WIC (CDMA) version 2.0
 Wireless WIC (CDMA/GSM) version 3.0

To configure the option board, select the board from the Special
Option Board Format drop list.
In the process of configuring the component, if you select a different
option board from the list, Metercat will ask if you want to migrate
the compatible items from the old component to the new component.
Select Yes or No as desired.

A3 ALPHA meter with W-WIC


Before you configure the parameters in the Special Option Board
component, perform a diagnostic read, making sure that the Special
Option Board view is included in the viewset. Make a note of the
WIC's firmware version and revision for later use.
If you received the PED file used to program your meter with W-WIC,
you must import the PED file before editing the Special Option Board
component.
Item Description

137
Components and programs

Select the Wireless WIC firmware


version & revision from the drop list.
Special option board format This should match the W-WIC
firmware version & revision obtained
from the diagnostic read.
W-WIC firmware version 3.0 supports
both CDMA and GSM cellular
communication. If you select GSM,
WIC type
additional parameters are displayed.
See the following section for more
information.
WAN Configuration
Along with the network-assigned IP
adddress, this is the port number the
C12.22 meter port number head-end system will use to
communicate with the W-WIC. The
default port number is 1153.
The time (in seconds) that the W-WIC
will wait before terminating a socket
Connection activity time (secs) connection if the connection
becomes idle. The default is 255
seconds.
This parameter is internal to the A3
ALPHA meter. This parameter should
Channel traffic timeout (secs)
be changed only after consulting your
Elster support representative.
Host access control list
To enable access control list
support, check the Enable
Source Checking box.
You can then specify which IP
addresses and their subnet
masks can be accepted by the
Enable source checking WIC when a client attempts to
communicate using the WAN
port. You can specify up to 8
allowed hosts.
To disable ACL support, clear
the Enable Source Checking
box.
Exception notification configuration
To enable exception
notifications, check the Enable
notifications box.
Note: For an event to generate
Enable notifications
a WAN notification, the event
must also be configured for
event logging in the Logs
component.
Enter the port used for
Exception port
notifications. The range is 0 to

138
TM42-3060

65535, with the default of


1153.
You can specify up to 4
exception hosts. For each
Number of exception hosts exception host you specified,
Metercat will display the
configuration options for each.
AP title Specify the AP title for the host.
Type the IP address for the
IP address
host.
The range can be between 0
Max number of retries
and 255; the default is 3.
The range can be between 0
Retry delay (min)
and 65535. The default is 1.
The range can be between 0
Exclusion period (min)
and 65535. The default is 0.
Each host can support up to 16
event types; for each host,
Number of exception types to report
specify the number of
exception types to report.
For each exception type you
specified, select the event from
the list of events. Notification is
available for the following
events.
A3 ALPHA meter notification
events:
 No event
 Primary power up
 Primary power down
 Time change (old time)
 Time change (new time)
Exception event
 End device programmed
 History log cleared
 Event log cleared
 Demand reset occurred
 Self read occurred
 Season change
 Rate change
 Pending table activated
 Test mode started
 Test mode stopped

139
Components and programs

 End device reprogrammed


 Configuration error detected
 RAM failure detected
 Nonvolatile memory failure
detected
 Clock error detected
 Tamper attempt detected
 Reverse rotation detected
 Tier override entered
 Tier override exited
 External event 0 signaled
 External event 1 signaled
 External event 2 signaled
 External event 3 signaled
 Phase A voltage not active
(meter firmware version 4.4 and
later)
 Phase A voltage active (meter
firmware version 4.4 and later)
 Phase B voltage not active
(meter firmware version 4.4 and
later)
 Phase B voltage active (meter
firmware version 4.4 and later)
 Phase C voltage not active
(meter firmware version 4.4 and
later)
 Phase C voltage active (meter
firmware version 4.4 and later)
 Remote flash failed
 Unauthorized requests
 End device reprogram error
 Optical port disabled
 Optical port enabled
 Temperature threshold
exceeded
 MFG meter event call
 WIC security log entry made
 WIC flash download complete

140
TM42-3060

Meter-based gatekeeper
notification events:
 LANOB command queue call
 LANOB key coordination call
 LANOB diagnostic
 LANOB data read complete
 LANOB profile schedule 1
complete
 LANOB profile schedule 2
complete
 LANOB outage read complete
 LANOB voltage call
 LANOB immediate call
 LANOB scheduled call
 LANOB power outage

DA I/O option board notification


events:
 DA I/O binary input 1 activated
(note 1)
 DA I/O binary input 1 not
activated (note 1)
 DA I/O binary input 2 activated
(note 1)
 DA I/O binary input 2 not
activated (note 1)
 DA I/O binary input 3 activated
(note 1)
 DA I/O binary input 3 not
activated (note 1)
 DA I/O binary input 4 activated
(note 1)
 DA I/O binary input 4 not
activated (note 1)
 DA I/O binary output contact K1
closed (note 1)
 DA I/O binary output contact K2
closed (note 1)
 DA I/O binary output contact K1
opened (note 1)

141
Components and programs

 DA I/O binary output contact K2


opened (note 1)
Check-in calls configuration
If you enable check-in calls, you
enable special communications
Enable check-in calls (noteTo that the WIC broadcasts to the
configure a gatekeeper or A3 ALPHA check-in host. The purpose of
meter for a last gasp outage the check-in call is to provide
notification, you must enable and routine network information to
configure check-in calls) the host that can be used to
diagnose and analyze WAN
communication.
These are advanced settings
Call-in delay (sec) you can configure if you need
Initial reply time (sec) to make adjustments to the
Incremental reply time (sec) network load. Changes to these
Number of retries settings should be made in
Random backoff factor (sec) consultation with your Elster
support representative.
You can select check-in calls
for current time recordPresent
meter time and date, cell signal
strengthCellular signal strength
as measured by the W-WIC, cell
signal bit error rate recordType
your expanding text here., cell
tower info record, temperature
recordTemperature (° C) inside
the meter, voltage recordDC
voltage as measured on the
main W-WIC power supply rail,
current recordType your
expanding text here. (mA),
Check-in parameters
event record. For each check-in
host (primary, secondary, and
last resort), you must specify
the AP title, IP address, port
number, and C12.22 security
mode.
0 = Power down (WIC notifies
the head-end system of last
gasp outage)
1 = Power up (WIC notifies the
head-end system of power
restoration)
2 = Temperature, transition
normal to restricted modes)

142
TM42-3060

3 = Temperature, in restricted
mode
4 = Temperature, transition
power off to restricted mode
5 = Temperature, transition
restricted to normal mode
6 = Network connection
achieved

Configure GSM parameters

If you are using GSM cellular communications (for example, AT&T or


T-Mobile), you must select GSM as the WIC type. Once GSM is
selected, you must enter the GSM configuration information as
supplied by your carrier. Metercat supports up to 3 alternate access
points (if used by your carrier) as well as the primary access point.

A3 ALPHA meter with E-WIC (ANSI C12.22 protocol)


Option boards: Ethernet WIC version 3.x; Ethernet WIC version 4.x
Before you configure the parameters in the Special Option Board
component, perform a diagnostic read, making sure that the Special
Option Board view is included in the viewset. Make a note of the
WIC's firmware version and revision for later use.
If you received the PED file used to program your meter with E-WIC,
you must import the PED file before editing the Special Option Board
component.
Item Description
Select the Ethernet WIC firmware
version & revision from the drop list.
Special option board format This should match the E-WIC firmware
version & revision obtained from the
diagnostic read.
The drop list displays Ethernet, which
WIC type
is the only supported type.
Network port parameters
The drop list displays C12.22, which
Protocol
is the only supported protocol.
C12.22 protocol parameters
Elster head-end systems require E-
WIC devices to use static IP
addresses. This check box should
remain cleared for meters intended to
be used within Elster systems.
Obtain an IP address using DHCP If you do select to use DHCP, check
the box. You must also specify the
length of the requested DHCP lease
time (in seconds). The default time (in
seconds) is 3600; the range is from
300 to 31536000.
Type the static IP address
IP address
assigned to the WIC. In most

143
Components and programs

cases where the E-WIC


connects to a modem or radio,
a private IP address is required.
Type a valid subnet mask. If the
mask is 255.255.255.0, the
incoming IP address must
equal the first 3 IP address
octets with the fourth octet
having any value for a range of
valid IP addresses. The mask
Subnet mask
algorithm works as follows: if
the mask and inbound IP
address = Mask & Allowed Host
IP Address (where & is a
bitwise AND operation), then
the inbound IP address is
allowed.
Type the default gateway IP
Default gateway IP address for outbound
messages.
The default port number is
1153. Port 1153 is registered
with the IANA for ANSI C12.22
traffic and is therefore the
recommended value. Other
C12.22 meter port number
port numbers may be used;
however, the use of different
port numbers are not compliant
with the ANSI C12.22
standards.
The E-WIC will terminate a
C12.22 connection if the
connection is idle longer than
this time (specified in seconds).
Connection activity time (secs) The connection activity timer is
reset to this value whenever
activity occurs on the
established connection. The
default time is 255 seconds.
This parameter is related to
inter-device communication.
The default value of 40
Channel traffic timeout (secs) seconds should only be
changed if you are instructed
by Elster support personnel to
do so.
Host access control list

144
TM42-3060

To enable access control list


support, check the Enable
Source Checking box. You can
then specify which IP
addresses and their subnet
masks can be accepted by the
Enable source checking WIC when a client attempts to
communicate using the WAN
port. You can specify up to 8
allowed hosts.
To disable ACL support, clear
the Enable Source Checking
box.
Exception notification configuration
To enable exception
notifications, check the Enable
notifications box.
Note: For an event to generate
Enable notifications
a WAN notification, the event
must also be configured for
event logging in the Logs
component.
Enter the port used for
notifications. The range is 0 to
Exception port
65535, with the default of
1153.
You can specify up to 4
exception hosts. For each
Number of exception hosts exception host you specified,
Metercat will display the
configuration options for each.
AP title Specify the AP title for the host.
Type the IP address for the
IP address
host.
The range can be between 0
Max number of retries
and 255; the default is 3.
The range can be between 0
Retry delay (min)
and 65535. The default is 1.
The range can be between 0
Exclusion period (min)
and 65535. The default is 0.
Each host can support up to 16
event types; for each host,
Number of exception types to report
specify the number of
exception types to report.
For each exception type you
Exception event specified, select the event from
the list of events. Notification is

145
Components and programs

available for the following


events.
A3 ALPHA meter notification
events:
 No event
 Primary power up
 Primary power down
 Time change (old time)
 Time change (new time)
 End device programmed
 History log cleared
 Event log cleared
 Demand reset occurred
 Self read occurred
 Season change
 Rate change
 Pending table activated
 Test mode started
 Test mode stopped
 End device reprogrammed
 Configuration error detected
 RAM failure detected
 Nonvolatile memory failure
detected
 Clock error detected
 Tamper attempt detected
 Reverse rotation detected
 Tier override entered
 Tier override exited
 External event 0 signaled
 External event 1 signaled
 External event 2 signaled
 External event 3 signaled
 Phase A voltage not active
(meter firmware version 4.4 and
later)

146
TM42-3060

 Phase A voltage active (meter


firmware version 4.4 and later)
 Phase B voltage not active
(meter firmware version 4.4 and
later)
 Phase B voltage active (meter
firmware version 4.4 and later)
 Phase C voltage not active
(meter firmware version 4.4 and
later)
 Phase C voltage active (meter
firmware version 4.4 and later)
 Remote flash failed
 Unauthorized requests
 End device reprogram error
 Optical port disabled
 Optical port enabled
 Temperature threshold
exceeded
 MFG meter event call
 WIC security log entry made
 WIC flash download complete

Meter-based gatekeeper
notification events:
 LANOB command queue call
 LANOB key coordination call
 LANOB diagnostic
 LANOB data read complete
 LANOB profile schedule 1
complete
 LANOB profile schedule 2
complete
 LANOB outage read complete
 LANOB voltage call
 LANOB immediate call
 LANOB scheduled call
 LANOB power outage

147
Components and programs

DA I/O option board notification


events:
 DA I/O binary input 1 activated
(note 1)
 DA I/O binary input 1 not
activated (note 1)
 DA I/O binary input 2 activated
(note 1)
 DA I/O binary input 2 not
activated (note 1)
 DA I/O binary input 3 activated
(note 1)
 DA I/O binary input 3 not
activated (note 1)
 DA I/O binary input 4 activated
(note 1)
 DA I/O binary input 4 not
activated (note 1)
 DA I/O binary output contact K1
closed (note 1)
 DA I/O binary output contact K2
closed (note 1)
 DA I/O binary output contact K1
opened (note 1)
 DA I/O binary output contact K2
opened (note 1)

A3 ALPHA meter with E-WIC (ANSI C12.21 protocol)


Option boards: Ethernet WIC version 2.x; ACB version 1.2; ACB
version 1.3
Before you configure the parameters in the Special Option Board
component, perform a diagnostic read, making sure that the Special
Option Board view is included in the viewset. Make a note of the
WIC's firmware version and revision for later use.
If you received the PED file used to program your meter with E-WIC,
you must import the PED file before editing the Special Option Board
component.
Item Description
Select the Ethernet WIC firmware
version & revision from the drop list.
Special option board format This should match the E-WIC firmware
version & revision obtained from the
diagnostic read.
ACB port parameters

148
TM42-3060

Select C12.21 from the drop list. The


Protocol Modbus, DNP 3.0, and DL/T 645
protocols are not supported.
The default value is 19200.
Note: This parameter is not
Port baud
used in ANSI C12.21
communication.
The default value is None. Note: This
Parity parameter is not used in ANSI C12.21
communication.
The default value is 8 bits. Note: This
Data bits parameter is not used in ANSI C12.21
communication.
The default value is 1 bit. Note: This
Stop bits parameter is not used in ANSI C12.21
communication.
Common protocol parameters
The default value is 0; range 0 to
Identity number
255.
The default value is 128; range 0 to
Maximum number of packets
255.
The default value is 256; range 64 to
1024. The maximum bytes per
Maximum bytes per packet
packet should match the packet size
in the Phone Book.
This parameter is related to inter-
device communication. The default
Channel Traffic Timeout (secs) value of 10 seconds should only be
changed if you are instructed by
Elster support personnel to do so.
Intercharacter timeout (secs) The default value is 1.
Packet response timeout (secs) 3
Maximum number of retries 3
C12.21 specific parameters
Elster head-end systems require E-
WIC devices to use static IP
addresses. This check box should
remain cleared for meters intended to
be used within Elster systems.
Obtain an IP address using DHCP If you do select to use DHCP, check
the box. You must also specify the
length of the requested DHCP lease
time (in seconds). The default time (in
seconds) is 3600; the range is from
300 to 31536000.
Type the static IP address assigned to
the WIC. In most cases where the E-
IP address
WIC connects to a modem or radio, a
private IP address is required.
Subnet mask Type a valid subnet mask.
Type the default gateway IP
Default gateway IP address for outbound
messages.

149
Components and programs

The default value is 1000; range 0 to


C12.21 port number
65,535.
The default value is 23; range 0 to
Telnet port 65,535. The E-WIC does not currently
support Telnet.
Enter one or more client IP addresses
Client IP address
(1 to 8 addresses).
The default is to enable ILC routing.
Enable ILC routing
The box should be checked.
The default value is 100; range 0 to
Transmit accumulate time (msec)
2550 in increments of 10.
The default value is 255; range 0 to
Connection activity time
255.

VOLTAGE MONITORING COMPONENT


The REXUniversal meter includes voltage monitoring. The meter will
indicate when voltages exceed the configurable thresholds for a time
greater than a configurable duration.

Minimum voltage parameters


You can specify the voltage parameters will result in the minimum
voltage event when the voltage drops below the threshold for a time
greater than or equal to the minimum voltage duration.
Item Description
The range is between 0 and 255 seconds
(default = 1 second). If a qualification time of 0
Qualification time
is defined, then any voltage that drops below
(seconds)
the threshold results in a minimum voltage
event.
The minimum voltage threshold as a percentage
Threshold (% nominal) of the meter's nominal voltage. The range is
from 75.0% to 99.9%, with a default of 90.0%.

Maximum voltage parameters


You can specify the voltage parameters will result in the maximum
voltage event when the voltage exceeds the threshold for a time
greater than or equal to the maximum voltage duration.
Item Description
The range is between 0 and 255 seconds
Qualification time (default = 1 second). If a qualification time of 0
(seconds) is defined, then any voltage that exceeds the
threshold results in a maximum voltage event.
The maximum voltage threshold as a
percentage of the meter's nominal voltage. The
Threshold (% nominal)
range is from 101.0% to 120.0%, with a default
of 110.0%.

Phase indicators
Each phase indicator on the LCD corresponds to a phase voltage
present on the meter's connections. If the phase indicator is on, then

150
TM42-3060

the corresponding voltage is present. If an indicator is blinking, then


the corresponding voltage is either missing or below the defined
threshold. Although Phase A voltage must be above the power fail
threshold for the meter to function, the meter may still operate even
if Phase A voltage is below the phase indicator threshold. In this
circumstance, the phase A indicator will blink.

Note: The Phase C indicator is only used on Form 12S meters. It


is always off for the remaining meter forms.
The threshold is defined as a percentage of the meter's nominal
voltage. The range is from 0.0% to 100.0%, with a default of 80.0%.

Momentary outage time


You can specify the boundary between what constitutes a
momentary outage and a sustained outage. Outages less than or
equal to this time are counted as momentary outages. Outages that
exceed this time are counted as sustained outages. If the momentary
outage time is defined as 0, then all outages are counted as
sustained outages.

Note: This parameter does not affect whether or when an outage


or restoration messages are generated (see Event Log
Configuration component).
The momentary outage time is defined in seconds, from 0 to 510
seconds. Metercat may round a value if the desired time is not
compatible with the meter.

WAN CONFIGURATION COMPONENT


You can use the WAN Configuration component to set the
parameters for the REXUniversal meter's WAN connection using the
Elster Wireless WIC (W-WIC) option board.

Configure GSM parameters


 If you are using GSM cellular communications (for example,
AT&T or T-Mobile), you must check the Confiure GSM
parameters box and specify the access point name (APN)
information as supplied by your carrier. You must specify the
primary APN, user name, and password. The WAN Configuration
component also supports up to 3 alternate APN sets (if used by
your carrier).
 If you are using GSM communications and the APN information
has not yet been received from your carrier, you may leave the
Configure GSM parameters box unchecked. When the APN
information is received, you must edit the component to include
the APN information. After you update the APN information, you
must replace the WAN configuration component in the meter.

151
Components and programs

 If you are using CDMA cellular communications (for example,


Verizon or Kore), the Configure GSM parameters box is to
remain unchecked.

Access control lists (ACL)


To enable access control list support, check the Enable Source IP
Checking box. You can then specify which IP addresses and their
subnet masks can be accepted by the WIC when a client attempts to
communicate using the WAN port. You can specify up to 8 allowed
hosts.
To disable ACL support, clear the Enable Source IP Checking box.

Check-in messages
If you enable check-in messages, you can enable a special
communication that the REXUniversal broadcasts to the check-in
host. The purpose of the check-in message is to provide routine
network information to the host that can be use diagnose and
analyze WAN communication. By default, the check-in message
includes the following data items:
 time
 cell signal strength
 cell signal bit error rate
 cell tower info
Parameter Description
By default, check-in messages are not
enabled. To enable check-in calls to
Enable check-in messages the host, check this box. Once
checked, the remaining parameters
will be displayed.
How long the WIC will wait before
sending another check-in message.
Check-in period (min) The default period is 60 minutes. You
may specify a period between 1
minute and 1440 minutes.

Check-in host

Parameter Description
AP title The AP title of the check-in host.
The numeric IP address of the check-
IP address
in host.
The port that the check-in host will
Port number
monitor for check-in messages.

Check-in advanced options

There are also advanced settings you can configure if you need to
make adjustments to the network load. These settings should be
made in consultation with your Elster support representative.

152
TM42-3060

Parameter Description
Initial reply time (sec) Default: 5; Range: 0 to 255
Incremental reply time (sec) Default: 15; Range 0 to 255
Number of retries Default: 3; Range 0 to 255
Random backoff factor (sec) Default 2: Range 0 to 255

You can also disable the data items included in the check-in
message by clearing their checkboxes.

Programs
ABOUT PROGRAMS

WHAT IS A PROGRAM?
A program controls how a specific meter or device operates, such as
which options are enabled (for example, PQM, relays, or
instrumentation profiling), length of intervals (for example, demand
and load profiling), and configuration of logs (for example, event log,
history log, and self reads).
Within Metercat, a program is a set of components. For example, a
program may have a Constants component (which defines things
such as whether the meter is using secondary metering or primary
metering, the CT and VT ratios, or adjusted Kh, Ke, or Kd values), a
Rates component (which defines the switch times and day types),
and a Special Option Board component (which defines how certain
option boards installed in the meter or device operate). It is possible
for a program to have unique components defined; however, it is also
possible for a single component to be used in multiple programs. For
example, your Rates component may be used in many different
programs. To assist you in creating programs, Metercat has sample
programs and sample components defined. As you edit the programs
(and components) to suit your utility's needs, you can save them for
later use in other programs, as necessary.
Every program has its own unique number (based on meter family
and meter type) called the Program ID. The program ID is stored in
the meter for future retrieval and reference. You may also add a
description and notes to each program, making it easier for you to
find and work with each program.

HOW DO I CREATE A PROGRAM?


There are several different ways to create a program.
 You can create a program from the start using the New Program
Wizard (File > New > Program). The New Program Wizard will
present a series of steps that will guide you through the process
to create a program.
 You can create a program by copying an existing program (File >
New > Program as Copy). You must assign a new, unique
program ID, but all other configurations will be copied from the

153
Components and programs

existing program. You can then make changes to the new


program as necessary.
 You can import an existing program from another computer
(Tools > Export/Import Program). You may have to make
changes during the import if there are conflicts, such as the
program ID of the imported program is already in use.

HOW DO I EDIT A PROGRAM?


To make changes to an existing program, you open it (File > Open >
Program) and make your edits. When you finish, save it (File > Save)

HOW DO I ADD OR REMOVE A COMPONENT FROM A


PROGRAM?
To add a component to an existing program, open it (File > Open >
Program). Select the Properties tab and then the Program Options
tab. Check to select the components you want to add or clear the
component you want to delete. When you finish, save it (File > Save).

HOW DO I SAVE A PROGRAM


Saving a program involves saving its components. See Save a
program for more information.

HOW DO I PROGRAM A METER?


Once you are ready to program your device, you must create a
function using the Program task or Replace Program task (as
necessary) and the execute the function.

HOW DO I DELETE A PROGRAM?


To delete a program, select File > Delete > Program.

NEW PROGRAM
File > New > Program

Note: You must have create program privileges to create a


program.
The New Program Wizard steps you through the process of creating a
program. To start the New Program Wizard, select File > New >
Program.
Item Description
Metercat lists the supported meter
families. If the meter family is not
listed, enable it by selecting the
Meter family Meters Supported tab in System
Preferences.
See Meter types to learn more about
meter families and meter types.
Meter type Metercat lists the supported meter
(A3 ALPHA/A1800 ALPHA only) types. If the meter type is not listed,

154
TM42-3060

enable it by selecting the Meters


Supported tab in System Preferences.
See Meter types to learn more about
meter families and meter types.
You must select whether the program
is for a single-rate demand or a time
Program type
of use application.
(A3 ALPHA/A1800 ALPHA only)
See About program types to learn
more about program types.
Select a unique ID in the New
Program ID number box. You can
scroll through the list of available
program numbers or type a number. If
you cannot type the number, then the
program ID is already in use. You
must enter a new value.
Note: The program ID must be unique
by both meter family and meter type.
For example, a program for an A3
ALPHA meter/A3R meter type can use
the same program ID as a
REXUniversal program. Likewise, a
program for an A3 ALPHA meter/A3T
Program ID number can use the same program ID as an
A3 ALPHA meter/A3K program.

If you click Next, you will be


presented with choices as to which
component types and components to
use in the program.
If you choose Finish, Metercat will
create a program using new, default
components.

You can use the Program Editor to


add or remove components after a
program has been created.
You can select the options you want
to include. The list is dependent on
your meter family, meter type, and
program type.

If you click Next, you will be


presented with more options to
select.
Options to include If you click Finish, Metercat will
create the program using new,
default components.

Use the Program Editor to add or


remove components after a program
has been created. See Available
components for the available
component types by meter family.

155
Components and programs

For the component types presented in


the window, you can choose the
following:

create new components for each


select the desired component by
selecting it from the drop list

New or existing components Use the Program Editor to add or


remove components after a program
has been created. See Available
components for the available
component types by meter family.
When you click Finish, Metercat will
create a program based on the
parameters you entered in the New
Program Wizard.

NEW PROGRAM AS COPY


File > New > Program as Copy

Note: You must have create program privileges to create a


program.
You can create a program by copying an existing program. This can
be useful if you already having an existing program that you want to
make changes to, but you don't want to risk making changes to the
existing program.
When the New Program as Copy dialog box is displayed, it will show
all the existing programs.
 List button and Details button: Toggle between how much
information is displayed. When viewing the programs as a list,
you see only the name of the program. When viewing the
programs by details, you see the program name, program type,
and other unique information.

To create a program by copying an existing program:


1 Select File > New > Program as Copy. The New Program
as Copy dialog box is displayed.
2 Select the program you want to copy. The Source Program Name
text box displays the name of the selected program you want to
copy.
3 If you want to see the components that make up the selected
program, click More. When you finish and want to close the list of
components, click Less.
4 Select a unique ID in the New Program ID number box. You can
scroll through the list of available program numbers or type a

156
TM42-3060

number. If you cannot type the number, then the program ID is


already in use. You must enter a new value.

Note: The program ID must be unique by both meter family and


meter type. For example, a program for an A3 ALPHA meter/A3R
meter type can use the same program ID as a REXUniversal
program. Likewise, a program for an A3 ALPHA meter/A3T can
use the same program ID as an A3 ALPHA meter/A3K program.
5 Click Open. Metercat creates a program based on the source
program and displays the new program in the Program Editor.

USING THE PROGRAM EDITOR

INTRODUCTION
Within Metercat, a program is a set of components that control the
operation and functionality of a meter or device. Using the Program
Editor, you can define additional properties to the program using the
Properties component. The Properties component is unique to a
program, and it must be edited within the Program Editor. Below is a
sample of the Program Editor window as viewed using the tree mode.

Metercat supports two viewing modes: tab view and tree view.
Tree view:

157
Components and programs

Tab view

To change views, open Metercat's document window control (that is,


the Program Editor window). The control window options are
displayed.

To use the tree view, click to enable Enable tree view option (a
check mark is displayed). To use the tab view, click to deselect
Enable tree view (check mark clears). If you do not see the
command, be sure you are in the Program Editor window and not the
Metercat application window.

EDITING COMPONENTS WITHIN THE PROGRAM EDITOR


You can edit and create components from within the Program Editor.
Select the component type from the tab view or tree view, and
Metercat will display the associated component for use within the
program. The following figure shows the demand component for use
within the sample A3R program.

158
TM42-3060

To edit the component


You can make changes to the component, changing any or all of its
parameters. See Available components for more information.
When you have finished making your changes, select File > Save to
save the component. See the section "Saving a component used by
an existing program" in the Save Component topic.

Note: When saving a component from the Program Editor, the


Save Component As dialog box contains a Skip button. Skipping
a component save is the same as clicking Cancel: Metercat will
not save the changes. Instead, you will return to the component.

To create a component
You can create a new component from within the Program Editor.
Select <new> from the drop list. Metercat will open a new
component. See Available components for a completing listing of
components.

When you have finished making your component, select File > Save
to save the component. See the section "Saving a component that is
not used by an existing program" in the Save Component topic.

CLOSING THE PROGRAM EDITOR


To close the Program Editor, select File > Close or double-click on
the Program Editor control.
If you have made changes to any components, the Save Program
Confirmation dialog box will be displayed. You are prompted to save
the changes or discard them.
 Click Yes to save the changes.

PROPERTIES COMPONENT

159
Components and programs

The Properties component allows you to set the parameters for


Metercat programs. The Properties component is different from all
other components because it can only be configured in the Program
Editor.

A3 ALPHA AND A1800 ALPHA PROGRAM PROPERTIES


Item Description
The Program ID Number box identifies
the unique program ID. Within
Metercat, program IDs are unique by
Program ID number meter family and meter type. The
Program ID is determined when the
program is created. It cannot be
edited once it has been set.
You can enter a brief description of
the program (up to 30 characters) to
Program description help you identify the program when
you see it listed in Metercat dialog
boxes.
From the drop list, select the
password set to be written to the
Password set
meter. See Meter Passwords
Management for more information.
Metercat provides 2 custom display
strings that can be used by the utility.
For example, you can identify the
Custom Display String
meter's read cycle. See the Metering
component for information on how to
add items to the meter display.
The effective date is not used by
Effective date Metercat. To specify a future effective
(timekeeping meters only) date, use the Replace Rates and
Dates task.
You can enter a detailed description
or notes about the program (up to
2000 characters). Program notes are
Program notes not stored in or used by the meter;
however, the program notes will be
included in a Program Report for
reference.
Certain components can be added or
removed from a program without
Program Options tab
having to create an entirely new
program.
The tab displays the number of days
of storage for common meter memory
configurations. For more information
Memory Allocation tab on how the meter memory is
allocated, see the estimated load
profiling days for the A3 ALPHA meter
or the A1800 ALPHA meter.
You can control with user groups can
Access Control tab use or have access to the program.
You can also control which programs

160
TM42-3060

specific users can use by setting their


privileges in Group Information.

IP AXISLINK PROGRAM PROPERTIES


Item Description
The Program ID Number box identifies
the unique program ID. Within
Metercat, program IDs are unique by
Program ID number meter family and meter type. The
Program ID is determined when the
program is created. It cannot be
edited once it has been set.
You can enter a brief description of
the program (up to 30 characters) to
Program description help you identify the program when
you see it listed in Metercat dialog
boxes.
From the drop list, select the
password set to be written to the
Password set
meter. See Meter Passwords
Management for more information.
You can enter a detailed description
or notes about the program (up to
2000 characters). Program notes are
Program notes not stored in or used by the meter;
however, the program notes will be
included in a Program Report for
reference.
Certain components can be added or
removed from a program without
Program Options tab
having to create an entirely new
program.
You can control with user groups can
use or have access to the program.
Access Control tab You can also control which programs
specific users can use by setting their
privileges in Group Information.

REXUNIVERSAL PROGRAM PROPERTIES


Item Description
The Program ID Number box identifies
the unique program ID. Within
Metercat, program IDs are unique by
Program ID number meter family and meter type. The
Program ID is determined when the
program is created. It cannot be
edited once it has been set.
You can enter a brief description of
the program (up to 30 characters) to
Program description help you identify the program when
you see it listed in Metercat dialog
boxes.

161
Components and programs

From the drop list, select the seed set


to be written to the meter. See Meter
Seed set
Passwords Management for more
information.
Metercat provides 2 custom display
strings that can be used by the utility.
For example, you can identify the
Custom Display String
meter's read cycle. See the Metering
component for information on how to
add items to the meter display.
You can enter a detailed description
or notes about the program (up to
2000 characters). Program notes are
Program notes not stored in or used by the meter;
however, the program notes will be
included in a Program Report for
reference.
Certain components can be added or
removed from a program without
Program Options tab
having to create an entirely new
program.
The tab displays the number of days
Memory Allocation tab of storage for common meter memory
configurations.
You can control with user groups can
use or have access to the program.
Access Control tab You can also control which programs
specific users can use by setting their
privileges in Group Information.

EXPORT/IMPORT PROGRAM
Tools > Export/Import Programs

Note: To export or import programs, you must have the


appropriate export meter programs or import meter programs
privileges.
Metercat provides a means to transfer programs by exporting them
from one installed version of Metercat and importing them into
another installed version. When importing a program, there are some
important aspects to consider in regards to your password sets and
components, as discussed in "Import a program" below.

EXPORT A PROGRAM
The Export/Import Program window allows you to sort the list of
available programs in your Metercat installation, select the specific
program, and then export the program as a .ped or .xml file. The file
can then be transferred to another Metercat installation and then
imported as a program. The Export/Import Program window has
options to help sort and narrow the list:
 Meters and Types drop list: Narrows the list of programs based
on meter family and meter type.

162
TM42-3060

 List button and Details button: Toggle between how much


information is displayed. When viewing the programs as a list,
you see only the meter type, program ID, and program
description. When viewing the programs by details, you see the
program name, program type, the date it was created, who
created it, when it was last modified, and other unique
information.

To export a program:
1 Click on the program you want to export. To confirm your
selection, the Program Name text box will display the name of
the program.
2 If you want to see the components making up the program that
will be exported, click More. Click Less to hide the information.
3 When you are ready to export the program, click Export. The
Save Exported Program As dialog box is displayed.
4 Navigate to the desired location and change the file name if you
want. The Save as Type drop list allows you to choose .ped or
.xml as the extension.
5 Click Save to complete the export.

IMPORT A PROGRAM
The Export/Import Program window allows you to import a Metercat
program file. You can import a program from either a .ped or .xml file.

About importing programs


 Beginning with Metercat 3.0, the program formatting changed.
You cannot export a program created using Metercat 3.0 or later
and then important it into a version of Metercat earlier than 3.0.
 You are allowed to import programs created in earlier versions of
Metercat into later versions of Metercat.
 Password sets will be updated during an import.
If the password sets being imported is different from the
password sets in the destination, then the imported password
sets will be the ones used. This may cause communication errors
with meters or devices, depending on the group's password set
and the password history depth setting. See Meter Passwords
Management for more information.
 Components will be updated during an import.
Since a program is a set of components, it is possible that the
program you are important may have a component name that
already exists. The component that is being imported will replace
an existing component with the same name in the destination
version of Metercat. This will affect all other programs in the
destination version of Metercat that uses the component. You

163
Components and programs

will be prompted during the import process if there are


component conflicts, and you will be able to cancel the
procedure, and no data will be affected.

To import a program:
1 Click Import. The Select PED file to Import dialog box is
displayed.
2 If necessary, change the format from the drop list from .ped to
.xml.

3 Navigate to the location that has the file to be imported and


select it. The File Name text box displays the name of the file to
confirm your selection.
4 Click Open.
As a shortcut, you can double-click on the .ped file from Windows
to start the import process. Metercat will warn you if there are
any component conflicts.
5 If there are component conflicts, Metercat will display a dialog
box warning you which components will be updated during the
import. Review the list carefully.
6 Click OK to complete the import; click Cancel to end the
procedure without affect data.
7 When you finish, click Close. Metercat will generate an Import
Program Activities report when the import is either completed or
canceled.

ABOUT FILE TYPES


The .ped file is an XML document. The extension .ped is associated
with Metercat, making it easy to import the program by simply
double-clicking on it. You can save the file with an .xml extension,
and the file will then open using the default XML editor on your
computer. It doesn't matter which file extension you use, you can
import the program as either a .ped or an .xml file.

Note: Do not edit the .ped or .xml file manually. Manually editing
a Metercat program file may result in an invalid meter program,
which may affect meter operation or billing data.

See also:
 Troubleshooting program imports

SAVE A PROGRAM

164
TM42-3060

File > Save


While working within the Program Editor, you can save the program.
Depending on which components have been changed, Metercat will
handle the save command different:
 If only Properties component is changed, Metercat will save the
changes to the component without any user confirmation.
o It is important to note that the saved changes are saved
within the existing program. There is no "Save As" feature at
this point that allows you to save a copy of the program.
o Use the New Program as Copy command to create program
based on an existing program.
 If any of the remaining components were edited using the
Program Editor but have not yet been saved, Metercat will
prompt you to save them.
o Pressing Skip forces Metercat to continue to the next
component that needs to be saved.
o Pressing Skip does not discard the changes. The changes
are kept until you close the Program Editor.
o Pressing Skip when closing the Program Editor, the changes
are discarded.

DELETE PROGRAM
File > Delete > Program

Note: To delete a program, you must have create/edit program


privileges.
When you delete a program, you delete Properties component as well
as the references to the remaining components within the program.
The remaining components are not affected or changed when
deleting the program. Metercat will prompt you to confirm the
program deletion.
The Delete Program dialog box has several options to help you sort
and narrow the list:
 Meters and Types drop list: Narrows the list by showing the
existing programs based on meter family and meter type.
 List button and Details button: Toggle between how much
information is displayed. When viewing the components as a list,
you see only the name of the component. When viewing the
components by details, you see the component name,
component type, compatible meter families, meter type, and
other unique information.

To delete the program:

165
Components and programs

1 From the list of programs, select the program you want to delete.
The Program Name text box displays the name of the selected
program.
2 If you want to view the components that make up the program,
click More to view the components that make up the program.
Click Less to hide the components.
3 Click Delete. Metercat will prompt you to confirm your deletion.
4 Click Yes. Metercat will delete the program.

TROUBLESHOOTING PROGRAM/COMPONENT IMPORTS


Importing a program or component may result in a warning or have
unintended results for several different reasons.

RENUMBERING A PROGRAM
If a program import fails because of a special duplicate program ID
situation, Metercat will prompt you to renumber your existing
program and retry the import. You must have create/edit meter
program privileges as well as delete meter program privileges. If you
must make edits to a function, you must also have create/edit
function privileges.
Follow these steps:
1 Create a New Program as Copy, selecting the program whose
number you want to change.
2 Enter a new program ID, click Open, and then save the copied
program.
3 If any functions include a program task that references the old
number, you must edit those functions to reference the new
program ID (see Function Management).
4 Make sure that all the appropriate groups have access to the
new program (see Group Information).
5 Delete the old copy of the program. This frees up the program ID,
and you can retry the import.

RENAMING A COMPONENT
If a program import fails because of a special duplicate component
name situation, Metercat will prompt you to rename your existing
component and retry the import. You must have create/edit meter
program privileges as well as delete meter program privileges. If you
must make edits to a function, you must also have create/edit
function privileges.
Follow these steps:
1 Create a New Component as Copy, selecting the component
whose name you want to change.
2 Click on More to display the programs using the selected
components. Make note of the programs that use this
component.

166
TM42-3060

3 Type a new component name in the New Component Name text


box, click Open, and then save the copied component.
4 If any programs include component, edit the programs to
reference the new component name (see ).
5 If any functions include a task that references the old component
name, you must edit the functions to reference the new
component name (see Function Management).
6 Delete the old copy of the component. This frees up the
component name, and you can retry the import.

RENAMING A PASSWORD SET


If program import fails because of a special duplicate password set
situation, Metercat will prompt you to rename your existing password
set and then retry the import. You must have the manage meter
passwords privilege. If you must change any meter programs or
group access, you must have the appropriate privileges.
Follow these steps:
1 Select Tools > Meter Password Management.
2 Select the name of the password set that is the duplicate.
3 Enter a new password set name that will not conflict with an
existing password set and click OK.
4 Edit any programs or groups that reference the old password set
name to reflect the new password set name, as necessary.
5 Retry the import.

WARNING MESSAGE ABOUT SYSTEM PREFERENCES


If you import a program from another Metercat installation that uses
different system preferences (for example, the power up display list,
KYZ value method, or adjusted Kh value), you will see a warning.
Metercat will always use the setting that is on the destination
computer even when the program being imported has a different
setting. To keep the setting of the imported program, you must
change your system preferences accordingly.

OTHER IMPORTING ERRORS


If you experience errors while importing a program or component, the
import will be unsuccessful. These errors are usually the result of one
of the following conditions:
 corrupt files
 editing the .ped, .pcd, or .xml file outside of Metercat
 importing a later Metercat release .ped, .pcd, or .xml file into an
earlier Metercat release

To correct the problem, re-export the program or component from the


original Metercat installation and attempt to re-import the program or
component into a compatible Metercat installation.

167
Functions and tasks

About functions
WHAT IS A FUNCTION?
A function is a set of tasks that can be performed on a meter.
Typically, a function will have just one task (such as, perform a
diagnostic read), although it is possible to have a multiple tasks
within a single function. For example, you can create a single
function that will connect service and then perform a demand reset.
When you have more than one task in a function, the tasks are
performed in the order they were defined in the function.
Many tasks also have parameters will get programmed into the
meter or specify what information the task needs to perform.
Parameters can be set when the function is created, or they may be
specified when the function is being performed. If a particular task is
used in different functions, the task parameters can be different in
each function.

HOW DO I CREATE A FUNCTION?


Functions are created and managed from Function Management.
Metercat includes sample functions, which you can edit as
appropriate for your requirements. You can also create your own
functions using Function Builder.
The tasks are set by Metercat, and you cannot create your own tasks.

WHAT HAPPENS WHEN A FUNCTION IS PERFORMED?


To perform a function, you must have a way to connect to the meter
(see Machine Settings to set up new connections to your computer),
establish the connection with the meter (see Connection bars for
more information), and then execute the function.
You must have the correct privileges and the appropriate password
access level to execute the function, which are set by your group (see
Group Information). If a function contains more than one task and
you do not have appropriate password access level to perform all the
tasks, the function will perform up until the point it fails, and then it
will stop. For example, you have defined a function to perform a
diagnostic read (which requires read only access) followed by a
demand reset (which requires billing access). If you password access
level is read only, the diagnostic read will be performed; however, the
demand reset will fail. If the task order were reversed (for example,
you defined the function to perform a demand reset and then a

169
Functions and tasks

diagnostic read), the demand reset will fail and the function will stop.
In the latter example, the diagnostic read will not be performed.

Function Management
Tools > Function Management

Note: You must have the appropriate function privileges to view,


create, edit, or delete functions.
From the Function Management window, you can view and manage
existing functions as well as create new ones.

You can perform the following actions from the Function


Management window:
 Scroll through the list of available functions, select and view the
included tasks for the selected function as well as the keyboard
shortcut (if any).
 Click New to create a function using the Function Builder.
 Click Edit or double-click on the function name to edit the
selected function using the Function Builder.
 Click Export to save the selected function as a Metercat
Function Request (.mfr) file.
 Click Delete to delete the selected function.

See also
 Executing functions for information on performing a function

Function Builder
Tools > Function Management > New
Tools > Function Management > Edit

170
TM42-3060

Note: You must have the appropriate function privileges to view,


create, edit, or delete functions. If you do not have the
appropriate privileges, the Tools > Function Management
command will not be available.
Function Builder allows you to create a function or to edit an existing
function (using the Function Definition tab). If you are using
Metercat in a multi-user system, you can also select which Metercat
groups will be able to execute the function (using the Access Control
tab).

BUILDING OR EDITING FUNCTION


You must type in a name for the function in the Function Name text
box.

Note: Choosing a function name is important. When you execute


a function, you will select the function from a list. Because some
functions may include meter family specific tasks (for example,
there are separate billing read tasks for different meter families),
the name of the function should reflect such situations to make
it easier for you to identify the function later.
To include a task in a function, you must move a selected task from
the Available Tasks column to the Included Tasks column by either
using the Add button or by dragging the task from column to column.
If you want to remove one task from the function, you can click
Remove or drag it back to the Available Tasks column. If you click
All, all the tasks in the Included Tasks column will be moved back to
the Available Tasks column.
Typically, a function will include only one task. However, if you are
building a task that includes more than one task, they are performed
in the order in which they appear in Included Tasks. You can control
their order using the Up and Down buttons.
Some tasks have parameters that must be specified for the
command to be completed. If you are adding a task to a function and
the task requires parameters, Metercat will automatically display its
configuration dialog box. If you are editing a task, you can view or

171
Functions and tasks

edit the parameters by clicking Parameters. If the button is grayed


out, then the task has no configuration settings that can be changed
in Function Builder (however, some tasks may have configuration
parameters that can only be set at run time).
You can also create a keyboard shortcut for use when you are
executing the function. Once a connection has been made to the
device, and provided the function can be performed with the
selected connection type, you can press the keyboard shortcut to
execute the function.
There are some key sequences that are reserved and cannot be used
as a keyboard shortcut; other combinations may override Metercat
default keyboard shortcuts. See the Keyboard shortcut guidelines for
more information. To view a list of assigned keyboard shortcuts, see
Help > Function Shortcuts.

CONTROLLING ACCESS TO A FUNCTION


If you are using Metercat in a multi-user environment, you must
specify which Metercat groups will have access to the function. You
can assign group privileges using the Access Control tab. Groups
listed in the Disallowed Group list will not have access to the
function; groups listed in the Enabled Groups list will have access to
the function.
Group access to functions can also be controlled by using the
Function tab in Group Information.
If you are in a group that has authorization privileges, you can enable
another group to have access using the Function tab in Group
Information.

PERFORMING A FUNCTION
See Executing functions for information on performing functions on a
meter or device.

ABOUT METERCAT'S SAMPLE FUNCTIONS


See Sample functions for more information.

LIST OF AVAILABLE TASKS


See Available tasks for a complete listing of the available tasks.

Executing functions
When you execute a function, Metercat will perform the tasks
specified by the function to the connected meter or device. For
example, if you execute a demand reset function that contains a
demand reset task, Metercat will send the command to the
connected meter to reset the demand. If you do not have a
connection method already defined, you must create one first (see
Machine Settings).

172
TM42-3060

After the connection has been established, select the desired


function from the Function drop list and then click Go. Metercat will
begin the communication process, identify the meter, and perform
the function's tasks in the order they specified in the function. A
dialog box may be displayed for you to enter any run time settings
that are required for the task to be completed. After a function is
complete, a function completion report will be generated. The
function completion report will indicate the status of the function
(whether it succeeded or failed) as well as additional information.
If a function is repeatable, the Repeat button will be enabled. Some
functions can be repeated without re-entering parameters; others
may have optional re-entering of parameters; and some require re-
entering parameters. See Available tasks for a list of tasks that can
be included in a function and if the task is repeatable. See the
description for each task for any limitations on the repeat capability.

Sample functions
Metercat includes a set of sample functions. You may edit the
functions as appropriate for your requirements. You may also use
them as reference to build your own functions. The following table
lists the sample functions along with any notes about their use.
Function name Description
Billing Read task (A3 ALPHA/A1800 ALPHA) with
the following parameters:
Storage Mode: Append
Reading Filename ID: Meter ID
Interval Data (Load Profile): All
Interval Data (Instrumentation): All
Billing Read with Reset
History Log; Event Log; PQM Log; Self Read Data: All
for each log or data set
Harmonic Content Data: None
Collector/Node Data: Status
Perform Demand Reset: checked
Create PROFILE HHF: not checked
Change Demand Change Demand Overload task; parameters
Overload entered at run time
Change Demand Change Demand Thresholds task; parameters
Threshold entered at run time
Change Passwords task (A3 ALPHA/A1800
Change Higher
ALPHA/IP AxisLink) with the Unrestricted & Billing
Passwords
option checked
Change KYZ Output task; parameters entered at
Change KYZ Divisor
run time
Change Modem Init Change Modem Init String task; parameters
String entered at run time
Change Passwords task (A3 ALPHA/A1800
Change Read Only
ALPHA/IP AxisLink) with the Read Only option
Password
checked

173
Functions and tasks

Change Remote Replace Remote task (A3 ALPHA/A1800 ALPHA);


Definition parameters entered at run time
Change Time task (A3 ALPHA/A1800 ALPHA) based
Change Time on local PC time at run time; time zone set to Do
Not Change.
Clear Battery Log Clear Battery Log task
Clear Event Flags Clear Event Flags task (A3 ALPHA/A1800 ALPHA)
Clear Event Log Clear Event Log task (A3 ALPHA/A1800 ALPHA)
Clear Values & Statuses Clear Data (A3 ALPHA/A1800 ALPHA)
Configure Special Option Board task (A3
Configure Special
ALPHA/A1800 ALPHA); parameters entered at run
Option Board
time
Diagnostic Read task (A3 ALPHA/A1800 ALPHA)
with the following parameters:
Storage Mode: Replace
Reading Filename ID: Account
Interval Data (Load Profile): Number of Days = 1
Diagnostic Read Interval Data (Instrumentation): Number of Days =
1
History Log; Event Log; PQM Log; Self Read Data: All
for each log or data set
Harmonic Content Data: None
Collector/Node Data: Status
Edit Service Test task (A3 ALPHA/A1800 ALPHA);
Edit Service Test
parameters entered at run time
Program Program task (A3 ALPHA/A1800 ALPHA)
Register Edit Register Edit task (A3 ALPHA/A1800 ALPHA)
Reset Demand Demand Reset task (A3 ALPHA/A1800 ALPHA)
Turn OFF Test Mode Test Mode Off task (A3 ALPHA/A1800 ALPHA)
Turn ON Test Mode Test Mode On task (A3 ALPHA/A1800 ALPHA)
Unlock Service Unlock Service task (A3 ALPHA/A1800 ALPHA)

Available tasks
The following table identifies all the tasks that are available for this
version of Metercat. Some tasks may have additional requirements
(for example, a meter may be required to have a specific version of
firmware). Click on each task name to find out more information
about each task, including any additional requirements. Tasks
marked with a plus sign (+) are repeatable. Some tasks can be
repeated without re-entering parameters; others may have optional
re-entering of parameters; and some require re-entering parameters.
See the description for a task for more information.

Note: For tasks and functions, "REX" refers to the original REX
meter, REX2 meter, and gREX meter. Where only specific meters
within the REX family are supported, the help topic for the task
will indicate the specific meter.
REX
A3 A1800 meters IP
REXUniversal
Task ALPHA ALPHA (REX, AxisLink
meter
meter meter REX2, router
gREX)

174
TM42-3060

Activate C12.22
WAN Factory • • • •
Key
Activate LAN
Factory Key
• • •
Billing Read + + +
Billing Reset •
Change
Demand + +
Overload
Change
Demand + +
Threshold(s)
Change Display
Units for
Primary

Instrumentation
Change DLMS
Password

Change KYZ
Output
+ +
Change Modem
Init String
+ +
Change Optical
Test Source
• •
Change Out
Gatekeeper
+ +
Change
Passwords
+ + + +
Change Pulse
Divisor
+ +
Change Seed
Set
+
Change Time + + + + +
Change Utility
ID
• • • • •
Clear Battery
Log
+ +
Clear Data + + + + +
Clear Event Log + + + +
Clear Outage
Data

Clear PQM Data + +
Clear Read
Without Power •
Data
Clear Status
Flags
+ + + +
Clear
Temperature + +
Status Flags
Configure
Special Option + +
Board

175
Functions and tasks

Confirm Factory
Unrestricted •
Seed
Connect Service • • •
Demand Reset + + + +
Diagnostic Read + + + + +
Disable Node
Communication
• •
Disable Optical
Port
• •
Disconnect
Service
• • •
Edit PQM
Thresholds
• •
Edit Service
Test
• •
Enable Node
Communication
• •
Enable Optical
Port
• •
Fast Demand
Test

Meter Health
Report
+
Meter
Identification +
Info
Ping LAN Node •
Poll
Instrumentation

PQ Inspector • •
Program + + + +
Register Edit • •
Replace
Configuration
• •
Replace Loss
Compensation
+ +
Replace PQM + +
Replace
Program
+ +
Replace Rates
and Dates
+ + •
Replace
Remote
+ +
Set DA I/O
Relays
+
Set Interposing
Control Relay

Set Interrupter
Control Relay

Set LAN Radio
Test Mode
• • •
Test Mode Off + + + +
Test Mode On + + + +

176
TM42-3060

Turn Loss
Compensation + +
Off
Turn Loss
Compensation + +
On
Turn PQM or
TRueQ On/Off
+ +
Unlock Service + +
Update Option
Board • •
Identification
WAN Ping Test • •

Task descriptions
ACTIVATE C12.22 WAN FACTORY KEY
Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA, REXUniversal, IP
AxisLink

Note: This task may only be executed using the meter's optical
port or the IP AxisLink router's local Mini-B USB port.
In the event that the headend system loses the key to a device,
communications from the headend to the device will no longer be
possible. Using Metercat and local communication (either optical port
or Mini-B USB port), it is possible to promote the WIC factory key to a
pending state.
To promote the factory key, add this task to a function. Once the
function is executed, Metercat will identify the connected device. If
the device has a WIC, Metercat will promote the factory key to a
pending state. The factory key will become active after a WAN
communication (which is encrypted with the factory key) is
successfully processed by the meter.

ACTIVATE LAN FACTORY KEY


Minimum password level: Unrestricted for A3 ALPHA & A1800 ALPHA
meters; Optical for REX2 meters
Supported devices: A3 ALPHA & A1800 ALPHA meters with EA_NIC;
REX2 meters

Note: A3 ALPHA & A1800 ALPHA meters must have firmware


version 4.0 or later; REX2 meters must have firmware version
3.0 or later.
In the event that the LAN key is lost, device communication within
the EA_LAN will no longer be possible. Using Metercat and local
communication (optical port), it is possible to promote the LAN
factory key to a pending state.

177
Functions and tasks

A3 ALPHA AND A1800 ALPHA METERS


To promote the LAN factory key in these meters, add this task to a
function. The function will identify the connected meter. If the meter
has an EA_NIC, Metercat will promote the factory key to a pending
state. The factory key will become active after a LAN communication
(encrypted with the factory key) is successfully processed by the
meter.

REX2 METERS
By adding this task to a function, the function will reset the LAN key
back to the factory key that was originally programmed into the
meter.

BILLING READ
Minimum password level: Billing
Supported devices: A3 ALPHA, A1800 ALPHA, REXUniversal
Repeatable without re-entering parameters
This task performs a billing read of the connected meter. When you
create a function that includes the Billing Read task, the Billing Read
Task Configuration dialog box will be automatically displayed. If you
are editing a function that includes the task, click Parameters to
display the configuration dialog box.
In addition to performing a billing read, the task will also clear meter
statuses. Depending on your system preferences, a successful billing
read may also adjust the meter's time.
You can configure the storage mode in one of the following ways:
 Store the billing read as a Metercat Stored Reading (.msr) file in
the Metercat\Readings\Billing folder
 Only display the read in the selected viewset

Note: If you experience problems when reading a meter, make


sure you have access to Metercat's \Config, \Readings, and
\Reports folders and subfolders. Contact your Metercat
administrator for more assistance.

A3 ALPHA/A1800 ALPHA BILLING READ TASK


CONFIGURATION PARAMETERS
Item Description
None: No stored reading file is
created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
Storage Mode created with each read. No data is
overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.

178
TM42-3060

See Stored Readings Management


for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how many days worth of
load profiling data will be read.
None: No load profiling data will be
read.
All: All load profiling data will be read.
Unread: Only load profiling data that
is marked as "unread" will be read.
Unread with Update: Only load
Interval Data (Load Profile)
profiling data that is marked as
"unread" will be read; the unread
marker will be updated to indicate
that the load profiling data up to that
point has been read.
Number of Days: Reads load profiling
data for the specified number of days;
may be between 1 and 999 days.
Determines how many days worth of
instrumentation data will be read.
None: No instrumentation data will be
read.
All: All instrumentation data will be
read.
Unread: Only instrumentation data
that is marked as "unread" will be
read.
Interval Data (Instrumentation) Unread with Update: Only
instrumentation data that is marked
as "unread" will be read; the unread
marker will be updated to indicate
that the instrumentation data up to
that point has been read.
Number of Days: Reads
instrumentation data for the specified
number of days; may be between 1
and 999 days.
History Log
Event Log Determines how much of the log or
PQM Logs data set will be read. You may select
Self Read Data None or All.
Harmonic Content Data
Determines how much of the
gatekeeper data or node data will be
read. You may select Status or All.
Gatekeeper/Node Data
The selection is only applicable to
meters that have either the
gatekeeper module or the EA_NIC.
If checked, the meter will perform a
Perform Demand Rest
demand reset after a successful

179
Functions and tasks

billing read. If clear, no demand reset


will be performed.
Creates an MV-90 HHF file and stores
it in the \Metercat\Readings\HHF
folder. See Stored Readings
Management for more information.
Create PROFILE HHF
Creating a profile HHF also requires
that the storage mode be set to either
Append or Replace. You must also be
reading load profiling data.

REXUNIVERSAL BILLING READ TASK CONFIGURATION


PARAMETERS
Item Description
None: No stored reading file is
created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
created with each read. No data is
Storage Mode overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.
See Stored Readings Management
for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how many days worth of
load profiling data will be read.
Interval Data (Load Profile) None: No load profiling data will be
read.
All: All load profiling data will be read.
Determines how many days worth of
instrumentation data will be read.
None: No instrumentation data will be
Interval Data (Instrumentation)
read.
All: All instrumentation data will be
read.
Determines how much of the log will
Event Log
be read. You may select None or All.
Determines how much of the data set
Self Read Data will be read. You may select None or
All.
If checked, the meter will perform a
demand reset after a successful
Perform Demand Rest
billing read. If clear, no demand reset
will be performed.

180
TM42-3060

BILLING RESET
Minimum password level: Optical
Supported devices: REX2 meters with firmware versions 3.0 or later

Note: This command can only be performed using the optical


port connection.
This task will perform a demand reset in the connected REX2 meter
and increment the demand reset count. This will also notify the HAN
devices associated with the meter of the demand reset.
When the function completes, Metercat will generate a Billing Reset
Completion Report, indicating the status of the task (whether it was
successful or failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CHANGE DEMAND OVERLOAD


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings

Note: The register multiplier, demand overload, and demand


threshold values cannot all be set to their maximum value. If you
set them to their maximum value, executing any of the following
tasks will fail: Program, Change Demand Overload, Change
Demand Threshold(s). For example: If you set the register
multiplier to 1000000.0 and you attempt to change the demand
overload value to 999999.9999, the attempt will fail.
Initially, the overload value is set during meter configuration using
the Demand component. This task will change the demand overload
value after it has been written to the meter.
The demand overload range may be between 0.0000 and
999999.9999 kilo units. A value of 0.0000 inhibits the demand
overload warnings in the meter.
When you create a function that includes the Change Demand
Overload task, the Change Overload Task Configuration dialog box
will be displayed automatically. If you are editing a function that
includes the task, click on Parameters. If you check the Prompt for
Override at Run Time, you will be prompted to manually enter a
value when the function is performed. If the Prompt at Run Time is
unchecked, Metercat will automatically program the specified value
when the function was created.

Note

181
Functions and tasks

The demand overload is different from demand threshold, and both


serve a specific purpose.

CHANGE DEMAND THRESHOLDS


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
Initially, demand threshold values are set during meter configuration
using the Demand component. This task will change the demand
threshold value after it has been written to the meter.
 If you are changing the demand threshold for a single rate
(demand-only meter) meter, type the new value in the Single
Rate Demand Thresholds (kilo units) text box. The range may
be between 0.0000 to 999999.9999 kilo units, where 0.0000 is
the default value.
 If you are changing the demand threshold for a multi-rate (TOU
meter) meter, type the new values for the demand threshold for
each rate in the Multi-Rate Demand Thresholds (kilo units)
panel. The range may be between 0.0000 to 999999.9999 kilo
units per rate, where 0.0000 per rate is the default value.
When you create a function that includes the Change Demand
Thresholds task, the Change Thresholds Task Configuration dialog
box will be displayed automatically. If you are editing a function that
includes the Change Demand Thresholds task, click on Parameters.
If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
created. For multi-rate meters, this can be configured individually for
each rate.

Note
The demand threshold is different from demand overload, and both
serve a specific purpose.

CHANGE DISPLAY UNITS FOR PRIMARY


INSTRUMENTATION
Minimum password level: Unrestricted
Supported devices: A1800 ALPHA meter that are configured to
display all instrumentation quantities as primary

Note: Changing the display units for primary instrumentation


using this task can result in an overflow on the meter display.
Carefully consider the use of this task to your specific primary
metering application.

182
TM42-3060

This task will change the meter display behavior in the following
manner:
 For all current and voltage instrumentation sources, the
measuring units are changed from kilounits (the configuration
written to the meter when programming) to unity. However, the
number of displayed digits remains in the format of xxx.xxx.
 For all power instrumentation sources, the measuring units are
changed from megaunits (the configuration written to the meter
when programming) to kilounits. However, the number of
displayed digits remains in the format of xxxx.xxx.
The display units are changed when the task is executed. If the meter
is later reprogrammed (that is, the Program task is executed), the
reprogramming will revert the display to its previous state. You must
execute this function again to change the display units for primary
instrumentation.

See also
 Metering component for the A1800 ALPHA meter > Display tab >
Control sub tab for information on configuring instrumentation
quantities as primary.
 Function Builder for information on creating a function.
 Function Management for information on editing an existing
function.

CHANGE DLMS PASSWORD


Minimum password level: Unrestricted
Supported devices: A1800 ALPHA meters with firmware version 2.1
or later
This task will change the Level 1 DLMS password that is stored in the
meter. When the function is executed, Metercat will display the
Change DLMS Password run time dialog box. Type the new password
in the DLMS Password text box. The new password may be up to 20
hexadecimal characters.

For more information


See About DLMS passwords for information on how Metercat
handles DLMS passwords.

CHANGE KYZ OUTPUT


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
When a relay is used to echo energy pulses for a basic metered
quantity, each pulse is equal to a specific amount of energy. For all

183
Functions and tasks

firmware versions of the A3 ALPHA meter and the A1800 ALPHA


meter, you can program the KYZ divisor with an integer. All A1800
ALPHA meter firmware versions and A3 ALPHA meters beginning with
firmware version 3.01 support two methods for specifying the
amount of energy: the KYZ divisor and the KYZ value.
This task will change the KYZ Divisor or, if supported and configured,
the KYZ Value presently stored in the meter. When you create a
function that includes the Change KYZ Output task, the Change KYZ
Output Task Configuration dialog box will be displayed automatically.
If you are editing a function that includes the task, click on
Parameters.
If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
created.

CHANGING THE KYZ DIVISOR


To change KYZ divisor, type an integer from 1 to 999.

CHANGING THE KYZ VALUE


To change the KYZ value, type a KYZ value or select the KYZ value in
the drop list. If you are typing the value, the range may be between
0.000001 and 100.000000 kilo units. If you are selecting the value,
the options are determined by what was configured in Programming
Options.

See also
The KYZ divisor and the KYZ value are set during meter configuration
using the Relay Options component.

For more information


See your meter's technical manual to understand how to set the KYZ
divisor and/or the KYZ value. Typically, the relay outputs are
described in Chapter 5, "Outputs." The manuals refer to the KYZ
divisor as "energy pulse divisor" and KYZ value as "energy pulse
value."

CHANGE MODEM INIT STRING


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
The modem initialization string is the list of commands that the
meter sends to the internal or external telephone modem to prepare
it for a connection. The modem init string typically sets things like the

184
TM42-3060

communication speed, error correction, compression, and various


timeout values.
This task will change the modem init string presently stored in the
meter. When you create a function that includes the Change Modem
Init String task, the Change Modem Init String Configuration dialog
box will be displayed automatically. If you are editing a function that
includes the task, click on Parameters.
If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
created.
In the Port Number drop list, select the port number for the modem
whose init string you want to change. In the Modem Initialization
String text box, type the new modem init string you want to the meter
to use. The modem init string can be up to 32 ASCII characters long.

See also
The modem init string is set during meter configuration using the
Remote component.

For more information


See the documentation that came with your modem to determine
what the init string is best suited for your requirements.

CHANGE OPTICAL TEST SOURCE

FOR A3 ALPHA AND A1800 ALPHA METERS


Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA meters
The A3 ALPHA meter contains an LED on the face of the meter. The
LED emits a pulse output that can be used to test the meter accuracy
in the shop or in the field without breaking the meter seal or
removing it from service. Beginning with Metercat software version
6.1.1. or later, you can configure the optical pulse source for normal
mode, alternate mode, and test mode.
This task will change the optical source presently stored in the meter.
When the function is executed, Metercat displays the Change
Optical Test Source dialog box at run time. The dialog box displays
the original optical port pulse sources read from the meter as well as
present the valid options for the new source. Valid options are
determined by the quantities available for each meter type.
The dialog box also displays the pulse frequency. The meters support
the following frequencies:
 standard pulses

185
Functions and tasks

 fast pulses
To complete this function, select the desired value in the Pulse
Source drop list for each meter mode (normal, test, and alternate).
For each meter mode, you can select the desired Pulse Frequency
from the drop list. The dialog box will update the energy per pulse of
the optical port LED.

For more information


See chapter 5 of your meter's technical manual for more information
on optical pulse outputs.

FOR REX2 AND REXUNIVERSAL METERS


Minimum password level: Optical for REX2 meters; Unrestricted for
REXUniversal meters
Supported devices: REX2 meters with firmware version 3.0 or later;
REXUniversal meters
The REX2 meter and REXUniversal meter contains an LED on the
face of the meter. The LED emits a pulse output that can be used to
test the meter accuracy in the shop or in the field without breaking
the meter seal or removing it from service. Typically, the source for
the LED pulse output is the meter's first energy quantity.
This task will change the optical test source presently stored in the
meter. When the function is executed, Metercat displays the Change
Optical Test Source dialog box at run time. The dialog box displays
the original optical port test pulse source as well as the valid options
for the new source. Valid options for the new source are the meter's
programmed first energy source or the meter's programmed
alternate energy source. The Kh of the optical pulse output depends
on the meter form.
To complete the function, select the desired source in the New
Source for Optical Port Test Pulses panel and click OK. If you
select Do Not Change, the optical port test pulse source will not be
changed from the listed original source.
For REX2 meters, the first energy source and alternate energy source
are configured at the time of ordering. For REXUniversal meters, the
primary and alternate energy sources can be configured in Metering
component.

For more information


See your meter's technical manual for more information the first
energy source, alternate energy source, and optical port test sources.

CHANGE OUT GATEKEEPER


Minimum password level: Unrestricted
Supported devices: Gatekeeper modules (A3 ALPHA; IP AxisLink)

186
TM42-3060

Note: Before performing this task, make sure you have read all
the data (including all gatekeeper and node data) form the old
gatekeeper before changing to a new gatekeeper. Make sure the
new gatekeeper's Remote component is configured for proper
gatekeeper operation.
This task will unregister all devices from the gatekeeper in
preparation for changing to a new gatekeeper.
When this task is executed on the old gatekeeper, the Change Out
Gatekeeper dialog box is displayed. Type the LAN ID (a 10-digit
number located on the nameplate) and then click OK. When the
function is completed, Metercat will generate a completion report
indicating the status of the task (whether it succeeded or failed).
The new gatekeeper will initiate a node scan to register devices.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CHANGE PASSWORDS
Minimum password level: Unrestricted for A3 ALPHA, A1800 ALPHA,
IP AxisLink; Optical for REX, REX2, and gREX
Supported devices: A3 ALPHA, A1800 ALPHA, IP AxisLink, REX, REX2,
and gREX
This task will change the specified passwords used in a connected
meter.

Note: Changing the meter password is a task that must be


handled carefully. Failing to manage a password change properly
can result in losing the ability to interact with the meter. See
Changing ANSI C12.19 passwords for more information on
changing passwords correctly.

A3 ALPHA, A1800 ALPHA, IP AXISLINK PASSWORDS


The Change Password task allows you to change the unrestricted
password, the billing password, or the read only password in a
device.
Password A3 ALPHA, A1800 ALPHA
IP AxisLink allowed activity
level allowed activity
Used only in Metercat. Allows
The meter can only be read.
the device to only be read. No
Read only No alteration of data or
alteration of data or
programming is allowed.
programming is allowed.
The meter can be read. Some Used by EA_MS. Allows
Billing basic data-altering activity access to the device's web
related to billing functions is interface.

187
Functions and tasks

allowed. Demand reset can


be performed.
The meter can be read. Full Used by EA_MS and Metercat.
Unrestricted programming of the meter is Allows full access to the
allowed. device.

The Metercat help will identify the minimum password level is


required to perform certain tasks or other operations in a device.
When you create a function that includes the Change Password task,
the Change Passwords Task Configuration dialog box will be
displayed automatically. If you are editing a function that includes the
Change Passwords task, click Parameters to display the Change
Password Task Configuration dialog box. Select the password levels
you want to change.

If you are changing the read only password


If you change the your group's read only password using Meter
Passwords Management, the Change Passwords run time dialog box
will display the "new" read only password by default. When you click
OK, the "new" read only password will be written to the meter.
If you manually type a different password in the run time dialog, the
password set in your group's password set will not be changed. It is
up to you to update the read only password in your group's password
set, if needed. Failure to update your group's assigned read only
password may result in communication failure at a later time.

If you are changing the billing & unrestricted passwords


You must change your group's billing and unrestricted password
using Meter Passwords Management. Changing the billing &
unrestricted passwords do not have a run time dialog box because
Metercat will always write your group's most current password set
passwords directly to the meter.

Note: If you are changing both the billing & unrestricted


passwords as well as the read only password in a single task,
you will see the Change Passwords run time dialog when
changing the read only password.

About EnergyAxis-enabled devices


If the meter has a gatekeeper module or a NIC board installed, the
passwords in the option boards will be updated to match those being
written to the meter.

REX, REX2, GREX PASSWORDS


The Change Passwords task allows you to change the optical
password used by the meter. You must connect to the meter using
an optical probe to complete this task.
You must change your group's optical password using Meter
Passwords Management. When the Change Password task is
executed, the Change Password Task Configuration dialog box will be

188
TM42-3060

displayed. Select the desired password set from the drop list and
click OK. Metercat will write the "new" password as determined by
the password set into the meter.

See also
See Meter Passwords Management for information on setting
passwords.

CHANGE PULSE DIVISOR


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA

Note: You can only change the pulse divisor on a TOU meter. If
you attempt to change the pulse divisor on a demand-only meter,
you will receive an error indicating the meter type does not
support this feature.
Load profiling can store up to 32,767 pulses before overflowing. By
default, the meter counts one pulse per Ke. A pulse divisor is used to
scale down the number of pulses stored in each load profiling
interval. This allows recording of data that may otherwise exceed the
maximum number of pulses that can be stored in each load profiling
interval.
This task will change the pulse divisor. When you create a function
that includes the Change Pulse Divisor task, the Change Pulse
Divisor Task dialog box will be displayed automatically. If you are
editing a function that includes the task, click on Parameters.
If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
created.

CHANGING THE PULSE DIVISOR


To change pulse divisor, type an integer from 1 to 255.

See also
The pulse divisor is set during meter configuration using the Load
Profile component.

CHANGE SEED SET


Minimum password level: Unrestricted
Supported devices: REXUniversal
Repeatable without re-entering parameters

189
Functions and tasks

Note: Changing the meter seed sets is a task that must be


handled carefully. Failing to manage a seed set change properly
can result in losing the ability to interact with the meter. See
Meter Passwords Management for more information on how
seed sets are handled by various devices.
This task will change the specified seed set used in a REXUniversal
meter to the current seed set as defined in Meter Passwords
Management. The Change Seed Set task can be executed on a
connected meter or exported using the Export Endpoint Execution
Request.
When the Change Seed Set is executed, the REXU Change Seed Set
dialog box will be displayed. You must confirm the task's change to
the seed set to the current seed set. When the function is completed,
Metercat will generate a completion report indicating the status of
the task (whether it succeeded or failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CHANGE TIME
Minimum password level: Billing
Supported devices: A3 ALPHA/A1800 ALPHA; REX2; REXUniversal; IP
AxisLink
Repeatable without re-entering settings
This task will set the meter's time based on your local PC's time, and
it is adjusted by any change of the time zone.
When you create a function that includes the Change Time task, the
Change Time Task Configuration dialog box is displayed
automatically. If you are editing a function that includes the task,
click Parameters to display the Change Time Task Configuration
dialog box.
If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
created.
When the function is executed, Metercat will change the meter's time
to the local PC time, adjusted by the specified time zone in the
Change Time Task configuration. Metercat does not allow a time
change that results in a change of the date (that is, time changes
cannot cross a midnight boundary). If you attempt to perform a
function that results in a date change, the function will fail and
generate an error message.

190
TM42-3060

A3 ALPHA METER AND A1800 ALPHA METER TIME


CHANGES
When changing the meter time, the meter processes the time change
task differently depending on whether you are changing time forward
or changing time backward.
If you are changing time forward:
 The meter will perform any calendar-based events that should
have occurred. If the calendar-based event is a DST time change
and the meter is configured to support DST, the meter will still
schedule the DST event (if the "new" time is before the DST
change) or perform the DST change (if the "new" time is after the
DST change).

Example: If you change time from 00:15 to 01:15 on the day of a


DST event, the meter will still perform the DST event at 02:00. If
you change time from 00:15 to 03:15 on the day of a DST event,
the meter will be in DST after the time change is complete.
 If a TOU rate change was scheduled to occur during the time
affected by the change, the meter will switch to the TOU rate of
the "new" time. Example: If the rate changes from Rate C to Rate
A at 22:00 and the time change crosses the 22:00 boundary, the
meter will be in Rate A after the time change is complete.
 The meter will not necessarily end the load profiling block. If the
"new" time is within the same block, the status of the intervals
affected by the time change are set to invalid, and the meter will
continue profiling. The time stamp of the block will reflect the
"new" time.
 If the time change crosses a load profiling block boundary (by
one or more blocks), the status of the remaining intervals of the
current block are set to invalid. The time stamp of the current
block reflects the "old" time. Then, the meter creates a new block
with the time stamp of the block reflecting the "new" time.

If you are changing time backward:


 The meter will not perform any calendar-based events. If the
calendar-based event is a DST time change and the meter is
configured to support DST, the meter will not revert to standard
time.

Example: If you change time from 03:15 to 00:15 on the day of a


DST event, the meter will still be in DST at 00:15. As time moves
forward, the meter will still be in DST after the 02:00 boundary
has been crossed.
 The meter will be in the correct scheduled TOU rate for the
adjusted time. Example: If the rate changes from Rate C to Rate
A at 22:00 and the time change crosses the 22:00 boundary, the
meter will be in Rate C after the time change is complete.

191
Functions and tasks

 The meter will end the current interval block. The time stamp of
the block will indicate the "old" time. The status of the remaining
intervals of the block affected by the time change will be set to
invalid. The meter will then start a new profiling block. The time
stamp of the first block will indicate the "new" time.

The Time Zone Entry Option has the following options:


 No Default: Requires the user to specify the time zone setting
when the function is performed.
 Do Not Change: Performing the function will not change the time
zone presently set in the meter.
 System Setting: Sets the meter's time zone to the local
computer's time zone, provided the change of time zone doesn't
cross a midnight boundary.
 Time zones: The list of selectable time zones comes from your
local PC's Windows Registry. Time zones are listed based on their
offset from UTC. If the time zone you are programming into the
meter is different than the local computer's time zone, Metercat
will change the time to be correct for the selected time zone,
provided the time change doesn't cross a midnight boundary.

Example: If it is 13:30 UTC-5 on the local computer, but you


specify the meter's time zone to be UTC-6, Metercat will program
a time of 12:30 UTC-6 into the meter. If you were to specify a
time zone that would result in crossing a midnight boundary,
however, the function will fail and report an error.

Notes about time zones and DST


The Windows Registry contains the DST configuration information:
the DST time (in the US, 2:00 a.m.) and the DST amount (in the US,
60 minutes). The Change Time task sets these parameters in the
meter based on the selected time zone. The DST status is controlled
by the meter firmware based on the DST configruation information
and the DST Start/End actions (if any) configured in the Special
Dates component.
If the meter's selected time zone does not observe DST, the presence
of a DST Start or DST End in the Special Dates component will not
affect the meter's time (because the meter's DST amount would be 0
minutes). However, it is good practice to not program DST Start or
DST End actions in the Special Dates component if the meter has
been programmed with a time zone that doesn't observe DST.

REX2 METER TIME CHANGES


The REX2 meter is designed to have its time and date set by the
EA_LAN 900 MHz network. Elster recommends that the Change
Times task be executed only on REX2 meters that are not connected
to the EnergyAxis network.
The Change Time task will configure the meter's date and time to the
local time of the connected computer. For the REX2 meter, Metercat

192
TM42-3060

will not allow you to select the time zone; the time zone will always be
configured to the local time zone of the connected computer.
Once the REX2 meter rejoins the EnergyAxis network, the EA_LAN
900 MHz network will automatically reconfigure the meter to the
network date and time.

REXUNIVERSAL METER TIME CHANGES


When changing the meter time, the meter handles the time change
differently depending on the situation.
If a time change, whether forward or backward, results in the meter
remaining in its current interval, the meter handles the current
interval record normally.
If a forward time change crosses one interval boundary:
 If a TOU tier change was scheduled to occur during the time
affected by the change, the meter will switch to the TOU rate of
the "new" time. Example: if the rate changes from Tier C to Tier A
at 14:00 and the time change crosses the 14:00 boundary, the
meter will be in Tier A after the time change is complete.
 The meter will end the current interval record and indicate that a
time change occurred. The time stamp of the record will indicate
the "old" time.
 The meter will start a new interval record. The time stamp of the
record will indicate the "new" time.

If a forward time change crosses more than one interval boundary:


 If a TOU tier change was scheduled to occur during the time
affected by the change, the meter will switch to the TOU rate of
the "new" time. Example: if the rate changes from Tier C to Tier A
at 14:00 and the time change crosses the 14:00 boundary, the
meter will be in Tier A after the time change is complete.
 The meter will end the current interval record and indicate that a
time change occurred. The time stamp of the record will indicate
the "old" time.
 The meter will start a new interval record. The time stamp of the
record will indicate the "new" time.
 The meter will log the time change event, indicating the "old"
date/time and the "new" date/time.

If a backward time change crosses one or more interval boundaries:


 If a TOU tier change was scheduled to occur during the time
affected by the change, the meter will switch to the TOU rate of
the "new" time. Example: if the rate changes from Tier C to Tier A
at 14:00 and the time change crosses the 14:00 boundary, the
meter will be in Tier C after the time change is complete.

193
Functions and tasks

 The meter will end the current interval record and indicate that a
time change occurred. The time stamp of the record will indicate
the "old" time.
 The meter will start a new interval record. The time stamp of the
record will indicate the "new" time.
 The meter will log the time change event, indicating the "old"
date/time and the "new" date/time.

Notes about the REXUniversal meter and real time


The meter uses a capacitor to maintain real time across a power
failure. If the capacitor is depleted, real time is lost. When the meter
is re-energized after real time is lost (that is, the meter is maintaining
relative time), then the Change Time task will set both the real date
and the real time based on the local computer's date and time
(adjusted to any change of the time zone).
If the meter has real time, the Change Task will only set the time
even if the date does not match the local computer's date.

Notes about DST and time zones


The REXUniversal meter uses its own calendar to determine the
correct DST status. The Change Time task cannot affect the DST
status. Any attempt to set a DST status that conflicts with the meter
calendar will result in an error.

CHANGE UTILITY ID
Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA meters with EA_NIC
firmware version 5.0 or later; gatekeepers with firmware version 7.0
and later; REX2 meters with firmware version 4.0 and later;
EnergyAxis-enabled REXUniversal meters; IP AxisLink (IPGKR)
The utility ID is the same for all meters that are part of the same
network. Typically, there is only one utility ID per utility. However, it is
possible to support additional alternate utility IDs. Alternate utility IDs
allow for a utility to maintain a separate network, which can be used
for testing purposes, for example. Changing a utility ID does not
change any of the stored data within the meter. It is important to
perform a Clear Data task and reprogram the meter as appropriate
when changing the utility ID.
This task will change the utility ID used by the device. When the
function is executed, the Change Utility ID task is displayed. Select
the desired utility ID from the drop list and then click OK. When the
function is completed, Metercat will generate a completion report
indicating the status of the task (whether it succeeded or failed) and
the new utility ID.

See also:
 Function Builder for information on creating a function

194
TM42-3060

 Function Management for information on editing an existing


function

CLEAR BATTERY LOG


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
This task will clear the battery outage time (see the Security tab in
the Status view). When the function is completed, Metercat will
generate a completion report indicating the status of the task
(whether it succeeded or failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CLEAR DATA
Minimum password level: Unrestricted for A3 ALPHA, A1800 ALPHA,
IP AxisLink, and REXUniversal; Optical for REX
Supported devices: A3 ALPHA, A1800 ALPHA, IP AxisLink, REX, and
REXUniversal
Repeatable without re-entering settings
This task will clear billing, other measuring data, statuses, logs, and
data sets but preserve the meter's configuration. Typically, a function
with the clear data task is executed in the meter shop before
deploying the meter in the field. Certain error codes or warning codes
may be reset using a clear data task.
When the function is executed, Metercat will display a warning dialog
box at run time, prompting the user to confirm the task or to cancel
it. When the function is completed, Metercat will generate a
completion report indicating the status of the task (whether it
succeeded or failed) and the values that were cleared. Depending on
the meter and its present state, the following list is a sample of the
types of information that is cleared from the meter:
 clears current and previous data
 clears rate switch points and rate overrides (tier switch points
and tier overrides)
 clears interval data (load profiling and instrumentation)
 clears event log
 clears event flags
 clears self reads

195
Functions and tasks

 clears data stored in the gatekeeper module or EA_NIC option


boards
 clears power fail data save area
 clears power failure and power restoration data
 closes the service control switch (if installed)

Note: Typically, the Clear Data task will not clear the battery log.
See Clear Battery Log for more information.

See also
There are additional tasks that will clear specific types of information
and won't clear all the data that the Clear Data task performs. Check
Available tasks or the individual help topics below to see which of the
following tasks are available for your meter:
 Clear Battery Log
 Clear Event Flags
 Clear Event Log
 Clear PQM Data
 Clear Read without Power Data

For more information


See the technical manual for your meter for specific information
regarding what actions are taken when a clear data function is
executed. Your technical manual may refer to the Clear Data task
using terms such as "clear billing data" or "clear values and status."

CLEAR EVENT LOG


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA, IP AxisLink,
REXUniversal
Repeatable without re-entering settings
This task will clear events that stored in the device's event log. When
the function is completed, Metercat will generate a completion report
indicating the status of the task (whether it succeeded or failed) as
well as which values were cleared.
To clear both status flags and the event log, create a function that
includes the Clear Status Flags task as well as this task.

See also:
 Function Builder for information on creating a function

196
TM42-3060

 Function Management for information on editing an existing


function

CLEAR OUTAGE DATA


Minimum password level: Unrestricted
Supported devices: A3 ALPHA meter firmware version 5.0 and later
This task will clear the following values located in the Security tab of
the Status view:
 Sustained power outages count
 Sustained power outage time
 Momentary power outages count
When the function is executed, Metercat will prompt you to confirm
the task. When the function is completed, Metercat will generate a
completion report indicating the status of the task (whether it
succeeded or failed) as well as which values were cleared.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CLEAR PQM DATA


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings

Note: Depending on the language selection used for Metercat,


the TRueQ may be referred to PQM. The language setting is
controlled by Help > Language. As a standard, the Metercat
documentation will use the English (IEC) designation TRueQ,
which is also consistent with the A1800 ALPHA technical
manual. While the A1800 ALPHA meter supports the default
PQM tests, the A1800 ALPHA meter offers additional tests as
part of its tamper restraint and quality monitoring.
By adding this task to a function, the function will clear one or both of
the following:
 the PQM log and PQM status (counter and timer)
 the voltage sag log and voltage sag log status (counter and
timer)

When you create a function that includes the Clear PQM Data task,
the Clear PQM Data Task dialog box will be displayed automatically. If
you are editing a function that includes the task, click on
Parameters. When the function is executed, the PQM and/or voltage
sag log information will be cleared from the meter.

197
Functions and tasks

See also
 See PQM component for more information about PQM/TRueQ
tests and test sets.
 See Replace PQM for information on replacing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Edit PQM Thresholds for information on editing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Turn PQM or TRueQ ON/OFF for information on turning
PQM/TRueQ on or off without reprogramming or changing
values.

For more information


See your A3 ALPHA meter technical manual for more information
regarding PQM. Typically, PQM data is described in Chapter 4, "Meter
Tools." In the A1800 ALPHA meter, PQM is referred to as TRueQ and
is typically described in Chapter 4, "Meter Tools." TRueQ offers
additional tests to the PQM test set; however, TRueQ tests are
configured in the PQM component.

CLEAR READ WITHOUT POWER DATA


Minimum password level: Unrestricted
Supported devices: A1800 ALPHA (firmware version 3.0 or later)
Beginning with firmware version 3.0, the A1800 ALPHA meter may be
equipped with the ability to be read when AC power is not present at
the meter installation. When replacing the special Read without
Power battery, you will need to clear the Read without Power data
adding a Clear Read without Power Data task to a function. When the
function is executed, it will clear the following values (see Read
without Power tab of the Status view):
 Total Active Time
 Total Use Count

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information


See the A1800 ALPHA meter technical manual for more information
on the Read without Power feature.

198
TM42-3060

CLEAR STATUS FLAGS


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA, REX, REXUniversal
Repeatable without re-entering settings
This task will clear the events that are displayed in the Conditions tab
of the Status view. When the function is completed, Metercat will
generate a completion report indicating the status of the task
(whether it succeeded or failed).
To clear both status flags and the event log, create a function that
also includes the Clear Event Log task as well as this task.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CLEAR TEMPERATURE STATUS FLAGS


Minimum password level: Unrestricted
Supported devices: REX2 meter with firmware version 4.5 or later;
REXUniversal meter with firmware version 3.1 or later
Meters can be set with the following high temperature related
thresholds:
 a warning temperature thresholds that, when exceeded, will set
a status flag
 a service disconnect temperature threshold that, when
exceeded, will set a status flag and open the service control
switch
This task will clear the two temperature-related status flags. When
the function is executed, Metercat will display the Clear Temperature
Status Flags dialog box. You can select which temperature related
statuses to clear. You can select which statuses to clear; however, if
the warning status is selected, then the service disconnect status
must also be selected.
If you attempt to clear the temperature status while the current
meter temperature exceeds the thresholds, the task will fail.
When the function is complete, Metercat will generate a completion
report indicating the status of the task (whether it succeeded or
failed).

See also:
 Temperature monitoring view for displaying the REX2 warning
temperature threshold and the service disconnect temperature
threshold

199
Functions and tasks

 Event Log component for configuring the warning temperature


threshold and the service disconnect temperature threshold in
the REXUniversal meter
 Status view Conditions tab for displaying the internal meter
temperature and any status flags
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CONFIGURE SPECIAL OPTION BOARD


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings

Note: You can use this task to reset the EA_Gatekeeper's ACL
that have been set using EA_MS. To clear ACLs in a gatekeeper,
first disable the Enable Source Checking option and then
reprogram the gatekeeper.
This task will write a new Special Option Board component to the
connected meter.
When the function is executed, the Configure Special Option Board
Task dialog box will be displayed, which will allow you to select the
"new" Special Option Board component you want to write to the
meter. Select the new component from the drop list, and then click
OK. If you are programming a meter with an ACB option board
component, you will be prompted for additional parameters at run
time.
When the function is completed, Metercat will generate a completion
report indicating the status of the task (whether it succeeded or
failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

CONFIRM FACTORY UNRESTRICTED SEED


Minimum password level: Unrestricted
Supported devices: REXUniversal

Note: This task may only be executed using the meter's optical
port or the IP AxisLink router's local Mini-B USB port.
In the event that Metercat loses the seeds to a REXUniversal meter,
all communications from Metercat to the meter will no longer be
possible. Using EA_MS, it is possible to remotely promote the factory
unrestricted seed to a pending state. Once the meter's factory

200
TM42-3060

unrestricted seed has been promoted to a pending state, by adding


this task to a function, Metercat will confirm the factory unrestricted
seed. If task is successful, Metercat can reseed the meter.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information:


See the EA_MS user guide (TM42-3110) for more information on
WAN communication recovery.

CONNECT SERVICE
Minimum password level: Unrestricted for A3 ALPHA and
REXUniversal; Optical for REX meters
Supported devices: A3 ALPHA firmware version 4.3 and later;
REXUniversal; REX/REX2/gREX
Repeatable without re-entering settings

Note: Elster meters with the service control switch check the
voltage status on the load side before attempting to close the
switch. If load side voltage is present, the meter will not close the
switch, but it will instead notify the utility that load side voltage is
present.
Meters can be equipped with an optional service control switch that
enables the utility to disconnect the electrical service (by opening the
switch) or to reconnect the electrical service (by closing the switch).
This task will close the service control switch to restore the service.
When the function is executed, a warning dialog box will be
displayed. To complete the function, you must confirm or cancel the
command. When the function is completed, Metercat will generate a
completion report indicating the status of the task (whether it
succeeded or failed).
REX2 meters with firmware version 4.5 or later also check the
internal meter temperature. Before closing the service control switch,
the meter checks to see if the service disconnect temperature
threshold status flag is set. If the flag is set, you must clear the
status for the switch to close using the Clear Status Flags task or the
Clear Temperature Status Flags task.

See also:
 Disconnect Service
 Function Builder for information on creating a function

201
Functions and tasks

 Function Management for information on editing an existing


function

For more information:


 See the Polyphase Service Control for the A3 ALPHA meter
product guide (PG42-1026) for more information regarding the
service control switch for the A3 ALPHA meter.
 See the REX meter with Service Control Switch product guide
(PG42-1007) for more information regarding the service control
switch for the original REX meter.
 For all other meters (REXUniversal, REX2, and gREX), see the
meter's technical manual for more information.

DEMAND RESET
Minimum password level: Billing for A3 ALPHA, A1800 ALPHA,
REXUniversal; Optical for REX
Supported devices: A3 ALPHA, A1800 ALPHA, REX, REXUniversal
Repeatable without re-entering settings
This task will process a demand reset in the meter. Typical actions,
which can vary depending on meter family, include copying current
billing data to the demand reset data area, incrementing the demand
reset count, clearing appropriate status/event flags, and starting a
new demand interval.
When the function is executed, the demand in the meter will be reset
immediately.
The demand reset will be recorded as an event in the meter's event
log.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information


The technical manual should list the actions your meter performs
when a demand reset command is issued. Typically, this information
is described in Chapter 3, "Operating instructions." Your meter's
technical manual will also typically describe in Chapter 6 which error
codes, status codes, or warning codes (as appropriate for your
meter) are cleared on a demand reset.

DIAGNOSTIC READ
Minimum password level: Read only

202
TM42-3060

Supported devices: A3 ALPHA, A1800 ALPHA, IP AxisLink, REX,


REXUniversal
Repeatable without re-entering settings

Note: The diagnostic read is the only read that the A1800 ALPHA
meter the optional Read without Power feature when the feature
is activated (that is, there is no power at the meter site). See the
section below for more information.

Note: If you experience problems when reading a meter, make


sure you have access to Metercat's \Config, \Readings, and
\Reports folders and subfolders. Contact your Metercat
administrator for more assistance.
The diagnostic read obtains information from the requested meter
without the possibility of altering the data within the meter,
performing a demand reset, or updating any of the log/data set
unread markers. A diagnostic read will not clear statuses or change
the time. This makes the diagnostic read useful when
troubleshooting any issue with the device. Depending on your
storage mode, the diagnostic read file will be stored as a Metercat
Stored Reading (.msr) file in the Metercat\Readings\Diagnostic
folder or only displayable in the selected viewset.
When you create a function that includes the Diagnostic Read task,
the Diagnostic Read Task Configuration dialog box will be displayed
automatically. If you are editing a function that includes the
Diagnostic Read task, click on Parameters. When the function is
executed, the read is performed. Metercat will generate a function
completion report and display the information in the selected
viewset.

A3 ALPHA AND A1800 ALPHA DIAGNOSTIC TASK


CONFIGURATION PARAMETERS
Item Description
None: No stored reading file is
created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
created with each read. No data is
Storage Mode overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.
See Stored Readings Management
for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how many days worth of
Interval Data (Load Profile)
load profiling data will be read.

203
Functions and tasks

None: No load profiling data will be


read.
All: All load profiling data will be read.
Unread: Only load profiling data that
is marked as "unread" will be read.
Number of Days: Reads load profiling
data for the specified number of days;
may be between 1 and 999 days.
Determines how many days worth of
instrumentation data will be read.
None: No instrumentation data will be
read.
All: All instrumentation data will be
read.
Interval Data (Instrumentation) Unread: Only instrumentation data
that is marked as "unread" will be
read.
Number of Days: Reads
instrumentation data for the specified
number of days; may be between 1
and 999 days.
History Log
Event Log Determines how much of the log or
PQM Logs data set will be read. You may select
Self Read Data None or All.
Harmonic Content Data
Determines how much of the
gatekeeper data or node data will be
Gatekeeper/Node Data
read. You may select Status or All.
(only A3 ALPHA meters with
The selection is only applicable to
gatekeeper module or EA_NIC)
meters that have either the
gatekeeper module or the EA_NIC.

ABOUT A1800 ALPHA METERS WITH OPTIONAL READ


WITHOUT POWER
For A1800 ALPHA meters with the optional Read without Power
feature, the meter may be read when AC electrical service is not
present at the meter. You can only perform a diagnostic read when
reading the A1800 ALPHA meter in the Read without Power mode.
Any other task will fail. Also, if additional tasks are included in the
function, the diagnostic read may or may not occur, depending on
the order of the diagnostic read in the function.
Instrumentation data will not be read nor will it be displayed in the
corresponding view.
Because the extended memory option board (if installed) is not
powered by the Read without Power battery, data stored in extended
memory will not be read.

IP AXISLINK DIAGNOSTIC TASK CONFIGURATION


PARAMETERS
Item Description

204
TM42-3060

None: No stored reading file is


created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
created with each read. No data is
Storage Mode overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.
See Stored Readings Management
for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how much of the event
Event Log log will be read. You may select None
or All.
Determines how much of the
gatekeeper data or node data will be
read. You may select Status or All.
Gatekeeper/Node Data
The selection is only applicable to
devices that have either the
gatekeeper module or the EA_NIC.

REX DIAGNOSTIC TASK CONFIGURATION PARAMETERS


Item Description
None: No stored reading file is
created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
created with each read. No data is
Storage Mode overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.
See Stored Readings Management
for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how much interval data
Interval Data (Pulses) (pulses) is read. You may select None
or All.

REXUNIVERSAL DIAGNOSTIC TASK CONFIGURATION


PARAMETERS

205
Functions and tasks

Item Description
None: No stored reading file is
created; data is only displayed in the
selected viewset.
Append: A new stored reading file is
created with each read. No data is
Storage Mode overwritten.
Replace: A new stored reading file
overwrites the most recent stored
reading file for the same meter.
See Stored Readings Management
for more information.
Determines how the stored reading
file gets its name. The default is by
Account; however, you may also use
Reading Filename ID
the Meter ID. See System Preferences
for more information on setting the ID
labels.
Determines how many days worth of
load profiling data will be read.
None: No load profiling data will be
read.
All: All load profiling data will be read.
Interval Data (Load Profile)
Unread: Only load profiling data that
is marked as "unread" will be read.
Number of Days: Reads load profiling
data for the specified number of days;
may be between 1 and 999 days.
Determines how many days worth of
instrumentation data will be read.
None: No instrumentation data will be
read.
All: All instrumentation data will be
read.
Interval Data (Instrumentation) Unread: Only instrumentation data
that is marked as "unread" will be
read.
Number of Days: Reads
instrumentation data for the specified
number of days; may be between 1
and 999 days.
Event Log Determines how much of the log or
data set will be read. You may select
Self Read Data
None or All.

Note: The REXUniversal meter also supports the Poll


Instrumentation task that allows you to view the instrumentation
data on a continuous or step basis.

See also
About reading devices

For more information

206
TM42-3060

See the A1800 ALPHA meter technical manual for more information
regarding the optional Read without Power feature.

DISABLE/ENABLE NODE COMMUNICATION


Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA meters with EA_NIC
firmware versions 4.x or 5.0

Note: This task is to be performed if you are attempting to


program a meter with the EA_NIC firmware versions 4.x or 5.0
and you are experiencing repeated communication errors.
If you are experiencing repeated communication errors when
programming a meter with EA_NIC firmware versions 4.x or 5.0,
define a function with the following tasks in the order specified:
1 Disable Node Communication
2 Program
3 Enable Node Communication

DISABLE OPTICAL PORT


Minimum password level: Unrestricted
Supported devices: A3 ALPHA meter firmware version 5.0 or later;
REXUniversal
The meter supports a lockable optical port. This task will lock the
optical port.
Once the optical port is locked, any communication with the meter
will result in an error code indicating the port is locked. When the
function is executed, a warning dialog box will be displayed. To
complete this function, you must confirm or cancel the command.
When the function is completed, Metercat will generate a completion
report indicating the status of the task (whether it succeeded or
failed).
For information on enabling the optical port, see the Enable Optical
Port task.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information:

207
Functions and tasks

See the REXUniversal meter technical manual for information


regarding the lockable optical port.

DISCONNECT SERVICE
Minimum password level: Unrestricted for A3 ALPHA and
REXUniversal; Optical for REX meters
Supported devices: A3 ALPHA firmware version 4.3 and later;
REXUniversal; REX/REX2/gREX
Repeatable without re-entering settings
Meters can be equipped with an optional service control switch that
enables the utility to disconnect the electrical service (by opening the
switch) or to reconnect the electrical service (by closing the switch).
This task will open the service control switch to disconnect the
service. When the function is executed, a warning dialog box will be
displayed. To complete the function, you must confirm or cancel the
command. When the function is completed, Metercat will generate a
completion report indicating the status of the task (whether it
succeeded or failed).

See also
 Connect Service
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information


 See the Polyphase Service Control for the A3 ALPHA meter
product guide (PG42-1026) for more information regarding the
service control switch for the A3 ALPHA meter.
 See the REX meter with Service Control Switch product guide
(PG42-1007) for more information regarding the service control
switch for the original REX meter.
 For all other meters (REXUniversal, REX2, and gREX), see the
meter's technical manual for more information.

EDIT PQM THRESHOLDS


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA

Note: Depending on the language selection used for Metercat,


the TRueQ may be referred to as PQM. The language setting is
controlled by Help > Language. As a standard, the Metercat
documentation will use the English (IEC) designation TRueQ,
which is also consistent with the A1800 ALPHA technical
manual. While the A1800 ALPHA meter supports the default

208
TM42-3060

PQM tests, the A1800 ALPHA meter offers additional tests as


part of its tamper restraint and quality monitoring.
You can make changes to the settings for one or more of the PQM
tests of the connected meter. When you create a function using the
Edit PQM Thresholds task, the Edit PQM Thresholds dialog box will be
displayed automatically. If you are editing a function that already
includes the task, click Parameters to display the Edit PQM
Thresholds dialog box. You must specify whether or not to clear PQM
and sag logs and statuses.
When the task is executed, Metercat will display the Edit PQM
Thresholds window at run time, where you can make edits to the
existing PQM set that is already programmed in the meter. You can
also turn PQM on by checking the PQM ON check box or turn PQM off
by clearing the PQM ON check box. See PQM component for more
information on PQM tests and test sets.

Note: To change sets existing within the meter, you must either
reprogram the meter with a new PQM component or use the
Replace PQM task.

WHAT IS THE DIFFERENCE BETWEEN CLEAR, REPLACE,


AND EDIT?
When you clear the PQM data, you are not changing any of the
configuration settings for the PQM component. You are simply
"zeroing out" the data. Replacing the PQM component allows you to
replace all the PQM configuration settings for all the PQM tests at
once. Editing the PQM thresholds allows you to make specific
changes to specific PQM tests to the set already programmed for the
connected meter.

See also
 See PQM component for more information about PQM/TRueQ
tests and test sets.
 See Replace PQM for information on replacing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Turn PQM or TRueQ ON/OFF for information on turning
PQM/TRueQ on or off without reprogramming or changing
values.
 See Clear PQM Data for information on clearing the PQM/TRueQ
information and the voltage sag information.

EDIT SERVICE TEST


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA meters

Note: The Edit Service Test works different depending on


whether your meter is locked on a service or is unlocked.

209
Functions and tasks

IF THE METER IS LOCKED ON A SERVICE


This task will allow you to view the basic service voltage test
parameters and service current test parameters in a meter, edit
them, and then write them back to the meter. When the task is
executed, the Edit Service Test dialog box is displayed, showing the
parameters as they exist in the meter. You can edit the parameters
as needed. Click OK to update the parameters back to the meter.
See the help topic for the Service Test component for more
information on the parameters.

Note: The Edit Service Task only allows you to edit the basic
parameters. If you need to update the advanced parameters, you
must reprogram the meter with a new Service Test component.

IF THE METER IS UNLOCKED


The meter must be locked on a service to edit the service test. If this
task is executed on a meter with an unlocked service, the Edit
Service Test dialog will prompt you to lock the service. You may
select smart auto lock or manual lock. See your meter's technical
manual for information on locking the service (typically located in
Chapter 4, "Meter tools"). After you have locked the service, you may
attempt to execute the Edit Service Test task again.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

ENABLE OPTICAL PORT


Minimum password level: Unrestricted
Supported devices: A3 ALPHA meter firmware version 5.0 or later;
REXUniversal

Note: To enable the optical port once it has been locked, you
must follow the procedure for unlocking the optical port. A3
ALPHA meters require pressing the RESET and ALT buttons
simultaneously to unlock the optical port; REXUniversal meters
require a program key.
The meter supports a lockable optical port. If the optical port is
disabled, any communication with the meter will result in an error
code indicating the port is locked.
This task will enable the optical port after you have followed the
procedure to unlock the optical port. When the function is executed,
you can select to enable the optical port on a permanent basis or a
temporary basis. If you select to temporarily enable the optical port,
the optical port will lock itself once the time expires. The time is
specified in minutes, and it can be between 1 and 65,534 minutes.

210
TM42-3060

When the function is completed, Metercat will generate a completion


report indicating the status of the task (whether it succeeded or
failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information


See the meter technical manual for information regarding the
lockable optical port.

FAST DEMAND TEST


Minimum password level: Unrestricted
Supported devices: REXUniversal meter

Note: A fast demand test will result in clearing the demand


register data as well as performing a demand rest.
The REXUniversal meter supports the fast demand test that uses a
fixed, one minute (approximate) block demand interval for meters
that are Measurement Canada sealed for demand. This task will start
the fast demand test. When the function is executed, a warning
dialog box will be displayed. To complete the function, you must
confirm or cancel the command. When the function is completed,
Metercat will generate a completion report indicating the status of
the task (whether it succeeded or failed).
To perform a fast demand test:
1 Apply a test load to the meter.
2 Execute a function with the fast demand test task. A warning box
will be displayed indicating that a fast demand is about to be
performed that the test will take a few minutes.
The demand registers are cleared at the beginning of a fast
demand test. Any demand data contained in the demand
registers will be lost once the fast demand test has started.
3 Confirm the dialog box and wait approximately one minute for the
fast demand test to complete.
Normal demand calculations will not restart until power is cycled
at the meter, a demand reset task is performed, or a clear data
task is performed. By design, the Fast Demand Test will
automatically perform a demand reset as the test is completed
to restart normal demand calculations.

See also:
 Function Builder for information on creating a function

211
Functions and tasks

 Function Management for information on editing an existing


function

For more information:


See the REXUniversal meter technical manual for more information
on the fast demand test capability.

METER HEALTH REPORT


Minimum password level: Optical
Supported devices: REX2 meters
Repeatable without re-entering parameters
Using the Meter Health Report task, you can perform a meter fitness
test using the meter's optical port to help determine whether the
meter should be removed from service.
To run a meter fitness test, add this task to a function. When you
create a function that includes the Meter Health Report task, the
Meter Health Report dialog box will be automatically displayed. If you
are editing a function that includes the task, click Parameters to
display the configuration dialog box. You can set the testing defaults
and optimal firmware versions to suit your business needs.
When the function is complete, Metercat will generate a report
displaying the results of the fitness test.
Item Description
If enabled, the task will force
the meter display on the LCD
test for an extended time (over
30 seconds). This will allow
you to visually confirm the
meter display segments lit
correctly.

Once the display test is


complete, Metercat will prompt
Verify LCD appearance you to confirm the LCD
segments turned on correctly.

 If the LCD segments turned


on correctly, check the box
to indicate the display test
was successful.
 If the LCD segments did
not, then make sure the
check box is clear.
If the meter has a service
control switch installed, check
Test service disconnect
the box to test the opening
operations
and closing of the service
control switch.

212
TM42-3060

Pinging of a gatekeeper is an
advanced test that should only
be performed in consultation
Ping using a gatekeeper
with your Honeywell Elster
electricity meter support
member.
The meter may routinely
reinitialize the radio as part of
its normal operation. The task
will read the number of times
the meter has reinitialized the
Acceptable number of radio
radio. If the number of radio
resets
resets exceeds the number
specified here (between 0 and
100), the task will report the
radio resets as a potential
health issue.
There may be a difference
between the meter's rated
voltage (for example, 120 V)
and the actual voltage
measured by the meter (for
example, 118.9 V). You can
Acceptable percent of
specify the tolerance between
difference rated vs measured
the rated and measured
voltage
voltage as a percent (integers
from 0 to 200). If the
difference is beyond the
threshold, the task will report
the difference as a potential
health issue.
The task will read the meter's
outage count. If the number of
Number of outages considered outages exceeds the number
excessive specified here, the task will
report the outages as a
potential meter health issue.
This task will read the
metrology firmware version
and revision. If the firmware is
Optimal metrology firmware
earlier than this optimal value,
version.revision
the task will report the
firmware version information is
below the optimal level.
This task will read the radio
firmware version and revision.
If the firmware is earlier than
Optimal radio firmware
this optimal value, the task will
version.revision
report the firmware version
information is below the
optimal level.

METER IDENTIFICATION INFO

213
Functions and tasks

Minimum password level: Optical


Supported devices: REX, REX2, gREX
Repeatable without re-entering parameters

Note: This task can only be executed when connected to the


meter using its optical port.
This task will read the connected meter's information and display the
results an HTML report. The following will be included in the report:
 LAN ID
 LAN utility ID
 Factory serial number
 Customer serial number
 Meter firmware information (version and revision)
 Meter firmware SSPEC
 Radio firmware information (version and revision)
 Radio firmware SSPEC
 Manufacturer order number
 Manufacturer style number
 Meter options (indicates whether the options are enabled or
disabled)
 Meter time
 Metered quantity
 Demand interval
 Load profiling interval
 Load profiling divisor
 Load side voltage present? (Yes/No)
 Demand reset scheduled? (Yes/No)
 Disconnect relay open (Yes/No)
 Program ID

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

PING LAN NODE


Minimum password level: Unrestricted

214
TM42-3060

Supported devices: EnergyAxis-enabled A3 ALPHA


This task will ping another EnergyAxis-enabled meter and then
display the results. To complete the task, you will need the target
device's utility ID and LAN ID.
When this task is executed, the Ping Node Task dialog box will be
display. To ping the other EnergyAxis-enabled meter, you must type
the appropriate utility ID and LAN ID in the text boxes and click OK.
When the function is completed, Metercat will display the Ping LAN
Node completion report, which will indicate the status of the task
(whether it succeeded or failed). If the task was successful, the
completion report will also list the utility ID, LAN ID, and the RSSI of
the target meter.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

POLL INSTRUMENTATION
Minimum password level: Read only
Supported devices: REXUniversal
This task will read the meter's present register data and display the
instrumentation data on a continuous or step basis. When the
function is executed, Metercat will display the Instrumentation Polling
run time dialog box. The Poll Instrumentation task can only read the
register data and it cannot make changes to it.
To start the polling, click one of the following buttons:
 Click Run to poll the instrumentation data on a continuous basis.
As the information is read from the meter, the data in the
Instrumentation Polling dialog box will be updated.
 Click Step Read to poll the instrumentation data and display the
information in the Instrumentation Polling dialog box. The Step
Read button must be clicked for the information to be updated.
 Click Close to stop the polling and close the dialog box.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function
 The Billing Read and Diagnostic Read tasks read the present
register data and display the instrumentation data in the
Instrumentation view.

PQ INSPECTOR

215
Functions and tasks

Minimum password level: Unrestricted


Supported devices: A3 ALPHA, A1800 ALPHA
This task will read the meter and display the following information:
 phasor diagram
 power relationship diagram
 harmonic content diagram

When the task is executed, the PQI dialog box is displayed. You can
select to read the harmonics and view a graph of the channel
readings by checking the Read Harmonics box. When you click OK,
the PQ Inspector run time dialog box is displayed.
To start the display of the information, click one of the following
buttons:
 Click Run to refresh the data on a continuous basis. As the
information is read from the meter, the PQ Inspector data will be
updated.
 Click Step Read to manually refresh the data and display the it.
The Step Read button must be clicked for the information to be
updated.
 Click Close to stop the polling and close the dialog box.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function
 The Billing Read and Diagnostic Read tasks read the phasor,
power relationship, and harmonic content data and display the
data in the Instrumentation view.

PROGRAM
Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA; IP AxisLink;
REXUniversal
Repeatable with optional re-entering settings
After you have created a program for the meter or device, you use
the Program task to send a selected program to the meter or device.
When you create a function that includes the Program task, the
Program Task Configuration dialog box will be displayed
automatically. If you are editing a function that includes the task,
click on Parameters.

216
TM42-3060

If you check the Prompt for Override at Run Time, you will be
prompted to manually enter a value when the function is performed.
If the Prompt for Override at Run Time is unchecked, Metercat will
automatically program the specified value when the function was
configured.

A3 ALPHA/A1800 ALPHA PROGRAMS


Successfully programming an A3 ALPHA/A1800 ALPHA meter
accomplishes the following:
 downloads the specified program
 downloads new passwords
 resets previously calculated data to zero
 clears previous status information
 resets the programmed date in the meter to the current date
(except for A3D meters)
 for A3 ALPHA meters with EA_NIC: clears data stored in the
EA_NIC option board
The program task does not clear any data stored in any
connected gatekeeper module.
 for A3 ALPHA meters with the DA I/O option board (which
requires meter firmware version 4.4 or later): the program task
will enable DA I/O relay events when the task is executed

Note: If the selected program contains a special option board


component, the WIC will be configured with the DA I/O relay
events. To configure DA I/O relay events without programming
the meter, see Configure Special Option Board.
Item Description
<No Default>: No program is selected at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must select the program
when the function is executed.
Program If you select a program at the time the function is
created, this becomes the default program when this
particular function is executed, with the ability to
change the program at runtime if the Prompt box is
checked.
The default label for this quantity is Account; however,
this can be controlled by ID #1 Options in Site ID
Labels. You can set the following options:
<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
Account
when the function is executed.
<Factory Serial Num>: Uses the connected meter's
factory serial number as the value. This cannot be
changed, even at run time.
<Utility Serial Num>: Uses the connected meter's
utility serial number as the value. This cannot be

217
Functions and tasks

changed, even at run time.


If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected meter.
The default label for this quantity is Meter ID; however,
this can be controlled by ID #2 Options in Site ID
Labels. You can set the following options:
<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
when the function is executed.
<Factory Serial Num>: Uses the connected meter's
factory serial number as the value. This cannot be
Meter ID changed, even at run time.
<Utility Serial Num>: Uses the connected meter's
utility serial number as the value. This cannot be
changed, even at run time.
<Use Mask>: Prompts the user at the time the function
is executed to enter the appropriate masked value (see
Site ID Labels)
If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected meter.
No Default: Requires the user to specify the time zone
setting when the function is performed.
Do Not Change: Performing the function will not
change the time zone presently set in the meter.
System Setting: Sets the meter's time zone to the local
computer's time zone, provided the change of time
zone doesn't cross a midnight boundary.
Time zones: The list of selectable time zones comes
from your local PC's Windows Registry. Time zones are
listed based on their offset from UTC. If the time zone
you are programming into the meter is different than
the local computer's time zone, Metercat will change
the time to be correct for the selected time zone,
provided the time change doesn't cross a midnight
boundary.
Example: If it is 13:30 UTC-5 on the local computer, but
Time Zone you specify the meter's time zone to be UTC-6, Metercat
will program a time of 12:30 UTC-6 into the meter. If
you were to specify a time zone that would result in
crossing a midnight boundary, however, the function
will fail and report an error.
Notes about time zones and DST
The Windows Registry contains the DST configuration
information: the DST time (in the US, 2:00 a.m.) and the
DST amount (in the US, 60 minutes). The Program task
sets these parameters in the meter based on the
selected time zone. The DST status is controlled by the
meter firmware based on the DST configuration
information and the DST Start/End actions (if any)
configured in the Special Dates component.
If the meter's selected time zone does not observe DST,
the presence of a DST Start or DST End in the Special
Dates component will not affect the meter's time

218
TM42-3060

(because the meter's DST amount would be 0 minutes).


However, it is good practice to not program DST Start or
DST End actions in the Special Dates component if the
meter has been programmed with a time zone that
doesn't observe DST.
<Program Value>: Uses the parameter as specified
when the Constants component was configured.
Primary: the meter internally converts the measured
energy and demand quantities to primary units using
the voltage transformer ratio and current transformer
ratio. The metered quantities reflect energy and
Metering demand on the primary side of the instrument
Application transformers.
Secondary: the meter does not use the voltage
transformer ratio or the current transformer ratio to
adjust metered quantities. The metered quantities
reflect energy and demand on the secondary side of the
instrument transformers even if the voltage and current
ratios are programmed in the meter.
<Program Value>: If checked, uses the parameters as
specified when the Constants component was
configured.
CT / VT Otherwise, type a value in the range of 1.00 to 9999.99
in the respective boxes for the current transformer ratio
and voltage transformer ratio. Metercat will display the
transformer factor automatically.
<Program Value>: If checked, uses the parameters as
specified when the Constants component was
configured.
Otherwise, you must specify the register multiplier from
Register multiplier the Register Multiplier drop list. See About the register
multiplier for more information.
If you are using adjusted Kh in Programming Options,
Metercat will require that you enter the adjusted Kh
regardless of your settings for this parameter.
The programmable value that the meter will use to
display a demand overload warning or trigger an alarm
indication relay (if the meter is configured for such
actions).
<Program Value>: If checked, uses the parameters as
Overload (kilo units)
specified when the Demand component was
configured.
Otherwise, you must specify the overload in the kilo
units for the overload value. The value can be between
0.0000 and 999999.0000.
<Program Value>: If checked, uses the parameters as
specified when the Relay Options component was
configured.
KYZ Output
Otherwise, you must specify either the KYZ Divisor or
the KYZ Value, depending the settings as configured in
Programming Options.
<Do Not Change>: Does not change the parameters set
in the Service Test component already written in the
Service Test meter.
<No Default>: No value is specified at the time the
function was configured. The Prompt check box is

219
Functions and tasks

required, and the user must specify the value when the
function is executed.
<Program Value>: Uses the selected program's
contains a Service Test component if it is present in the
program.
Otherwise, you can select a specific service test
component to be written to the meter from the drop list.
<Do Not Change>: Does not change the parameters set
in the PQM component already written in the meter.
<No Default>: No value is specified at the time the
function was configured. The Prompt check box is
required, and the user must specify the value when the
PQM function is executed.
<Program Value>: Uses the selected program's
contains a PQM component if it is present in the
program.
Otherwise, you can select a specific PQM component to
be written to the meter from the drop list.
<Program Value>: Uses the selected program's
contains a Instrumentation Profiling component if it is
present in the program.
Instrumentation <Disable>: Disables instrumentation profiling in the
profiling meter.
Otherwise, you may select a specific Instrumentation
Profiling component to be written to the meter from the
drop list.
<Disable>: Disables remote communications in the
meter.
<Do Not Change>: Does not change the parameters set
in the Remote component already written in the meter.
<No Default>: No value is specified at the time the
function was configured. The Prompt check box is
Remote required, and the user must specify the value when the
function is executed.
<Program Value>: Uses the selected program's
contains a Remote component if it is present in the
program.
Otherwise, you can select a specific Remote component
to be written to the meter from the drop list.
Port 1/Port 2 If checked when the meter will be using a modem
Device ID Always sharing unit, the port of the connected meter will be set
Master as the master.

IP AXISLINK PROGRAMS
You must be connected to the IP AxisLink router using either the
WAN connection or the local Mini-B USB port to execute this task.
Executing the Program task will clear all data (status, event logs,
billing, interval data, etc.) in the device. Executing the Program task
will also reset the programmed date in the device to the current date
(based on local PC time).
Item Description
<No Default>: No program is selected at the time the
Program function was created. The Prompt for Override at Run
Time is required, and the user must select the program

220
TM42-3060

when the function is executed.


If you select a program at the time the function is
created, this becomes the default program when this
particular function is executed, with the ability to
change the program at runtime if the Prompt box is
checked.
The default label for this quantity is Account; however,
this can be controlled by ID #1 Options in Site ID
Labels. You can set the following options:
<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
when the function is executed.
<Factory Serial Num>: Uses the connected device's
Account
factory serial number as the value. This cannot be
changed, even at run time.
<Utility Serial Num>: Uses the connected device's
utility serial number as the value. This cannot be
changed, even at run time.
If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected device.
The default label for this quantity is Meter ID; however,
this can be controlled by ID #2 Options in Site ID
Labels. You can set the following options:
<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
when the function is executed.
<Factory Serial Num>: Uses the connected device's
factory serial number as the value. This cannot be
Meter ID changed, even at run time.
<Utility Serial Num>: Uses the connected device's
utility serial number as the value. This cannot be
changed, even at run time.
<Use Mask>: Prompts the user at the time the function
is executed to enter the appropriate masked value (see
Site ID Labels)
If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected device.
No Default: Requires the user to specify the time zone
setting when the function is performed.
Do Not Change: Performing the function will not
change the time zone presently set in the device.
System Setting: Sets the device's time zone to the local
computer's time zone, provided the change of time
zone doesn't cross a midnight boundary.
Time Zone Time zones: The list of selectable time zones comes
from your local PC's Windows Registry. Time zones are
listed based on their offset from UTC. If the time zone
you are programming into the meter is different than
the local computer's time zone, Metercat will change
the time to be correct for the selected time zone,
provided the time change doesn't cross a midnight
boundary.

221
Functions and tasks

Example: If it is 13:30 UTC-5 on the local computer, but


you specify the device's time zone to be UTC-6,
Metercat will program a time of 12:30 UTC-6 into the
device. If you were to specify a time zone that would
result in crossing a midnight boundary, however, the
function will fail and report an error.
Notes about time zones and DST
The Windows Registry contains the DST configuration
information: the DST time (in the US, 2:00 a.m.) and the
DST amount (in the US, 60 minutes). The Program task
sets these parameters in the device based on the
selected time zone. The DST status is controlled by the
device firmware based on the DST configuration
information and the DST Start/End actions (if any)
configured in the Special Dates component.
If the device's selected time zone does not observe
DST, the presence of a DST Start or DST End in the
Special Dates component will not affect the meter's
time (because the meter's DST amount would be 0
minutes). However, it is good practice to not program
DST Start or DST End actions in the Special Dates
component if the device has been programmed with a
time zone that doesn't observe DST.

REXUNIVERSAL METER PROGRAMS


Executing the Program task will clear all data (status, event logs,
billing, interval data, etc.) in the meter.
Item Description
<No Default>: No program is selected at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must select the program
when the function is executed.
Program If you select a program at the time the function is
created, this becomes the default program when this
particular function is executed, with the ability to
change the program at runtime if the Prompt box is
checked.
The default label for this quantity is Account; however,
this can be controlled by ID #1 Options in Site ID
Labels. You can set the following options:
<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
when the function is executed.
<Factory Serial Num>: Uses the connected meter's
Account
factory serial number as the value. This cannot be
changed, even at run time.
<Utility Serial Num>: Uses the connected meter's
utility serial number as the value. This cannot be
changed, even at run time.
If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected meter.
The default label for this quantity is Meter ID; however,
Meter ID
this can be controlled by ID #2 Options in Site ID

222
TM42-3060

Labels. You can set the following options:


<No Default>: No value is specified at the time the
function was created. The Prompt for Override at Run
Time is required, and the user must specify the value
when the function is executed.
<Factory Serial Num>: Uses the connected meter's
factory serial number as the value. This cannot be
changed, even at run time.
<Utility Serial Num>: Uses the connected meter's
utility serial number as the value. This cannot be
changed, even at run time.
<Use Mask>: Prompts the user at the time the function
is executed to enter the appropriate masked value (see
Site ID Labels)
If you specify any other valueYou can specify up to 20
alphanumeric or special characters, the value will be
programmed into the connected meter.
No Default: Requires the user to specify the time zone
setting when the function is performed.
Do Not Change: Performing the function will not
change the time zone presently set in the meter.
System Setting: Sets the meter's time zone to the local
computer's time zone, provided the change of time
zone doesn't cross a midnight boundary.
Time zones: The list of selectable time zones comes
from your local PC's Windows Registry. Time zones are
listed based on their offset from UTC. If the time zone
you are programming into the meter is different than
the local computer's time zone, Metercat will change
the time to be correct for the selected time zone,
provided the time change doesn't cross a midnight
boundary.
Example: If it is 13:30 UTC-5 on the local computer, but
Time Zone
you specify the meter's time zone to be UTC-6, Metercat
will program a time of 12:30 UTC-6 into the meter. If
you were to specify a time zone that would result in
crossing a midnight boundary, however, the function
will fail and report an error.
Notes about the REXUniversal and time
The meter uses a capacitor to maintain real time across
a power failure. If the capacitor is depleted, real time is
lost. When the meter is re-energized after real time is
lost (that is, the meter is maintaining relative time),
then the Program task will set both the real date and
the real time based on the local computer's date and
time (adjusted to any change of the time zone). The
meter will then update its programmed date and time
based on the date and time information from its head-
end system.

REGISTER EDIT
Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA

223
Functions and tasks

Note: Beginning with A1800 ALPHA meter firmware 4.0, the


A1800 ALPHA meter can be factory configured to prevent the
reset of energy registers. When the energy registers are locked,
the Register Edit task will fail and display a message that the
meter's tariff data is locked.
This task will allow you to read the connected meter's current billing
data, edit it, and then write it back to the meter. When the task is
executed, the Data Edit flag is set (see Security tab in the Status
view). The Data Edit flag can only be reset by reprogramming the
meter.

The Register Edit task allows you to edit any or all of the following
values. The register multiplier is not applied to the displayed billing
data.
 Site ID labels: ID #1 (typically, Account) and ID #2 (typically,
Meter ID). See Site ID Labels for information on ID #1 and ID #2.
 Energy per the metered quantity (demand only) or energy per
metered quantity by rate/tariff
 Maximum demand (demand only) or maximum demand by
rate/tariff
 Cumulative demand (demand only) or cumulative demand by
rate/tariff and the total

Note: When editing the total cumulative demand, the total must
be equal to or greater than the cumulative demand for all
rates/tariffs.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

REPLACE CONFIGURATION
Minimum password level: Unrestricted
Supported devices: A3 ALPHA meter firmware version 5.0 or later;
REXUniversal
This task will allow you to replace one or more components within the
A3 ALPHA meter or the REXUniversal meter.

A3 ALPHA METERS
When you create a function that includes the Replace Configuration
task, the Replace Configuration dialog box will be displayed
automatically. If you are editing a function that includes the task,
click on Parameters to display the dialog box.
The Replace Configuration task allows you to replace the following
components within the A3 ALPHA meter:

224
TM42-3060

 Load profile
 Instrumentation profiling
 Special dates
 Rates

Keep the following items in mind when completing this dialog box:
 Check the Update in Endpoint box to replace the component in
the A3 ALPHA meter. If the Update in Endpoint box is not
checked, the component will not update when the task is
executed.
 Check the Prompt box to allow the user to change the selected
parameter when the task is executed. If the Prompt box is left
unchecked, the task will execute with the parameters specified
at task configuration.
 Check the Perform a Self Read box to have the meter perform a
self read before the component are changed.
 Check the Perform a Demand Reset box to have the meter
perform a demand reset before the components are changed.

Notes
 To replace the component when the task is executed, the Update
in Endpoint box must be checked. Check the Prompt box if you
want to have an opportunity to update the component when the
task is executed.

REXUNIVERSAL METERS
By adding the Replace Configuration task to a function, the function
will allow you to replace one or more components within the
REXUniversal meter.
When you create a function that includes the Replace Configuration
task, the Replace Configuration dialog box will be displayed
automatically. If you are editing a function that includes the task,
click on Parameters to display the dialog box.
Using the Replace Configuration task, you can replace the following
components within the REXUniversal meter:
 Constants
 Demand
 Demand limiting
 Display
 Event log configuration
 Instrumentation profiling
 Load profile
 Metering

225
Functions and tasks

 Rates
 Special dates
 Voltage monitoring
 WAN configuration (available for meters with WIC option boards
present)

Keep the following items in mind when completing this dialog box:
 If you want to replace one or more components that already exist
in a program, you can select the program name in the Program
drop list. This will populate the remaining component lists.
 Check the Update in Endpoint box to replace the component in
the REXUniversal meter. If the Update in Endpoint box is not
checked, the component will not update when the task is
executed.
 Check the Prompt for Override at Run Time (or Prompt) box to
allow the user to change the selected parameter when the task
is executed. If the Prompt box is left unchecked, the task will
execute with the parameters specified at task configuration.
 Check the Perform a Self Read box to have the meter perform a
self read before the component are changed.

Note: The REXUniversal with the WIC option board does not
support performing a self read while replacing the configuration.
 Check the Perform a Demand Reset box to have the meter
perform a demand reset before the components are changed.

Notes
 Selecting the program does not reprogram the meter. The
Program drop list is simply a quick way of populating the list of
components if you choose to use it.
 To replace the component when the task is executed, the Update
in Endpoint box must be checked. Check the Prompt box if you
want to have an opportunity to update the component when the
task is executed.

EXECUTING THE REPLACE CONFIGURATION TASK


For both A3 ALPHA meters and REXUniversal meters, you can
execute the Replace Configuration task when Metercat is connected
to a meter (see Executing functions). You can also export the Replace
Configuration using the Endpoint Execution Request (see Export
Endpoint Execution Request).

REPLACE LOSS COMPENSATION


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings

226
TM42-3060

This task will update the Loss Compensation component without


reprogramming the meter.
When you create a function that includes the Replace Loss
Compensation task, the Replace Loss Compensation dialog box will
be displayed. If you are editing a function that includes the task, click
on Parameters to display the dialog box.
When you execute a function that includes this task, the Replace
Loss Compensation runtime dialog will be displayed. Depending on
how the task was configured, you can either confirm the new loss
compensation or change it.
Item Description
Select the new loss
compensation component you
want listed as the default
option. This will be the default
component that will display at
the runtime dialog box.
Component
No Default: If you select <No
Default> as the option, the
user will be required to
manually select the loss
compensation at the runtime
dialog box.
If checked, the user will have
the option to change the loss
compensation at runtime.
Prompt for Override at
If unchecked, the user cannot
Runtime
change the default loss
compensation component in
the runtime dialog box.

REPLACE PQM
Minimum password level: Unrestricted
Supported devices: A3 ALPHA; A1800 ALPHA
Repeatable without re-entering settings

Note: Depending on the language selection used for Metercat,


the TRueQ may be referred to PQM. The language setting is
controlled by Help > Language. As a standard, the Metercat
documentation will use the English (IEC) designation TRueQ,
which is also consistent with the A1800 ALPHA technical
manual. While the A1800 ALPHA meter supports the default
PQM tests, the A1800 ALPHA meter offers additional tests as
part of its tamper restraint and quality monitoring.
This task will allow you to replace the entire PQM component without
reprogramming the meter.
When you create a function that includes the Replace PQM task, the
Replace PQM dialog box will be displayed automatically. If you are
editing a function that includes the task, click on Parameters to

227
Functions and tasks

display the dialog box. When creating or editing a function with the
Replace PQM task, you can choose clear the PQM log, sag log,
counters, and timers.
When you execute a function that includes the Replace PQM task,
the Replace PQM runtime dialog box will be displayed. From the
runtime dialog box, you can select the PQM component you want
written to the meter. The option to clear PQM log, sag log, counters,
and timers cannot be set at runtime.

WHAT IS THE DIFFERENCE BETWEEN CLEAR, REPLACE,


AND EDIT?
When you clear the PQM data, you are not changing any of the
configuration settings for the PQM component. You are simply
"zeroing out" the data. Replacing the PQM component allows you to
replace all the PQM configuration settings for all the PQM tests at
once. Editing the PQM thresholds allows you to make specific
changes to specific PQM tests to the set already programmed for the
connected meter.

See also
 See PQM component for more information about PQM/TRueQ
tests and test sets.
 See Edit PQM Thresholds for information on editing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Turn PQM or TRueQ ON/OFF for information on turning
PQM/TRueQ on or off without reprogramming or changing
values.
 See Clear PQM Data for information on clearing the
PQM/TRueQ information and the voltage sag information.

REPLACE PROGRAM
Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings

Note: To preserve billing data, Elster recommends that you


perform a Billing Read before replacing the program.
This task will update the most program components in the connected
meter. If the "old" program contains any log components, the "new"
program will change the meter's logs and will clear self reads and
profile data (both pulse and instrumentation). Depending on the time
adjustment criteria (see Time Difference Options), the time in the
meter may be synchronized.
When you create a function that includes the Replace Program task,
the Replace Program dialog box will be displayed automatically. If you

228
TM42-3060

are editing a function that includes the task, click on Parameters to


display the dialog box.
If you check the Prompt box for a selection, the Replace Program
dialog box will be displayed when the task is executed so you can
make changes to that selection at runtime. If the Prompt box is left
unchecked, the task will write the parameters when the function was
configured.
Item Description
Program Select the "new" program from the drop list.
Determines when the program is replaced. If the date
specified is current or earlier, the new program is effective
Effective Date
immediately. If the date is in the future, the new program
will be effective beginning on the specified date.
When checked, will perform a self read at the time the task
is effective. That is, if the task is updated immediately, the
Perform a Self
self read will occur immediately; if the task is updated in the
Read
future, the self read will occur when the task is updated in
the future.
When checked, will perform a demand reset at the time the
task is effective. That is, if the task is updated immediately,
Perform
the demand reset will occur immediately; if the task is
Demand Reset
updated in the future, the demand reset will occur when the
task is updated in the future.

ABOUT USING THE REPLACE PROGRAM TASK


When replacing a program using this task, the task compares the
meter's existing components with the desired incoming components
to validate whether the program can be replaced.
 Some incoming component values must match the existing
component values.
 Some components can be replaced entirely and without
restrictions.
 Some components are not replaced and no match is required.

Also, the Replace Program task can specify an effective date, which
can be in the future.

Replace Replace
Component Description
immediately? future?
The incoming
component must
Constants No No
match the existing
component.
The incoming
Metering
component must
component - No No
match the existing
Quantities
component.

229
Functions and tasks

Immediately,
replaced entirely.
For future
replacement, all
except Display
labels
Metering (annunciators),
Yes,
component - Yes Display warning if
partially
Display reverse power
flow is detected,
and Lock all
warnings on
display using
defined warning
codes.
The following
parameters can be
replaced entirely:

 Rate A
threshold, Rate
B threshold,
Rate C
threshold, Rate
D threshold
 Demand
Yes,
Demand Yes, partially forgiveness
partially
time
 Demand
forgiveness
outage time
For all other
parameters, the
incoming values
must match the
existing
parameters.
Load profiling data
is cleared when the
Load profile Yes No
component is
replaced.
Instrumentation
profiling data is
Instrumentation
Yes No cleared when the
profiling
component is
replaced.
The KYZ divisor
Relay options Yes, partially No and KYZ value are
not replaced.
Rates Yes Yes Replaced entirely.
Special dates Yes Yes Replaced entirely.
The following logs
Logs Yes No have their data
cleared when the

230
TM42-3060

component is
replaced:

 Event log
 Load profiling
 Instrumentation
profiling
 Self reads
Special
Yes No Replaced entirely.
features
The custom display
Program strings 1 and 2 can
Yes, partially No
properties be replaced
entirely.

The following components are not replaced in the meter and no


match is required:
 service test
 PQM/TRueQ
 remote
 special option board
 loss compensation

REPLACE RATES AND DATES


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA, IP AxisLink
Repeatable without re-entering parameters (A3 ALPHA and A1800
ALPHA only)

Note: For A3 ALPHA meters firmware version 5.0 and later, use
the Replace Configuration task.
This task will update the Rates component, Special Dates
component, or both, without reprogramming the meter. The
replacement can be effective immediately or scheduled to occur at a
later date.
When you create a function that includes the Replace Rates and
Dates task, the Replace Rates and Dates dialog box will be displayed
automatically. If you are editing a function that includes the task,
click on Parameters to display the dialog box. If the Allow Override
box is checked, then the dialog box will be displayed when the task is
executed. Otherwise, if the Allow Override box is not checked, the
task will execute with the parameters set when the function was last
edited.
Item Description

231
Functions and tasks

If checked, the Replace Rates and Dates dialog box will be


Allow Override displayed at task execution. If clear, the parameters defined
in task will be used when the function is executed.
Determines when the updated components are updated. If
the date specified is current or earlier, the updated
Effective Date components are effective immediately. If the date is in the
future, the components will be effective beginning on the
specified date.
Select the new Rate component that you want to write into
Rates the target meter. If you select Do Not Change, the task will
not modify the Rates component in the target meter.
Select the new Special Dates component that you want to
write into the target meter. If you select Do Not Change, the
Special Dates
task will not modify the Special Dates component in the
target meter.
When checked, will perform a self read at the time the task
is effective. That is, if the task is updated immediately, the
Perform a Self
self read will occur immediately; if the task is updated in the
Read
future, the self read will occur when the task is updated in
the future.
When checked, will perform a demand reset at the time the
task is effective. That is, if the task is updated immediately,
Perform
the demand reset will occur immediately; if the task is
Demand Reset
updated in the future, the demand reset will occur when the
task is updated in the future.

See also
 The rates are set during meter configuration using the Rates
component.
 Special dates are set during meter configuration using the
Special Dates component.

REPLACE REMOTE
Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering parameters

Note: If the Replace Remote task is executed on a meter with the


gatekeeper module installed, the gatekeeper's bit rate will be
changed to reflect the modem settings in the new remote
component. The task completion report will indicate whether the
gatekeeper's bit rate was changed.
This task will replace the Remote component in the connected meter
without having to reprogram it.
When the task is executed, the Replace Remote Run Time Overrides
dialog box will be displayed, which allows you to change parameters
when the task is executed or to specify parameters which can only be

232
TM42-3060

done when the task is executed (such as entering the DLMS


password).
See Remote component for more information.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

SET DA I/O RELAYS


Minimum password level: Unrestricted
Supported devices: A3 ALPHA meters with firmware version 4.0 or
later
Repeatable without re-entering parameters

Note: The DA I/O relay option board must be installed and be


programmed for DA I/O operation in the Relay Options
component for its operation.
This task will perform the selected action on the control relays at the
specified time. The specified actions depend on the relay, as the
following indicates.

FOR RELAY 1:
 Do not change
The state of the control relay does not change
 Connect after cold load pickup period
Connects after a specified time (as indicated by the Actual Cold
Load Pickup Period text box) after relay activation
 Connect now
Connects the relay immediately
 Disconnect now
Disconnects the relay immediately
 Pulse now
Sends a pulse of a specified width (see Relay Options
component for the DA I/O pulse width specification)

FOR RELAY 2:
 Do not change
The state of the control relay does not change
 Connect now
Connects the relay immediately

233
Functions and tasks

 Disconnect now
Disconnects the relay immediately
 Pulse now
Sends a pulse of a specified width (see Relay Options
component for the DA I/O pulse width specification)

When the function is completed, Metercat will generate a completion


report indicating the status of the task (whether it succeeded or
failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

SET INTERPOSING CONTROL RELAY


Minimum password level: Unrestricted
Supported devices: A1800 ALPHA meters firmware version 4.0 or
later

Note: The meter must be configured for interposing control. See


the topic for Relay Options component for more information.
This task will perform the selected action on the interposing control
relay. Selected actions include the following:
 Do not change
The state of the control relay does not change
 Connect now
Relay C is pulsed that connects the interposing relay
 Arm the interposing relay for connect
Activation of Relay C is delayed until the * button is pressed by
the user
 Disconnect now
Relay D is pulsed that disconnects the interposing relay
 Clear armed for connect state
Cancels the armed state
When the function is completed, Metercat will generate a completion
report indicating the status of the task (whether it succeeded or
failed).

See also:
 Function Builder for information on creating a function

234
TM42-3060

 Function Management for information on editing an existing


function

For more information


See the A1800 ALPHA meter technical manual (TM42-2410F or
later) for information regarding the interposing relay. Typically, the
relay outputs are described in Chapter 5.

SET INTERRUPTER CONTROL RELAY


Minimum password level: Unrestricted
Supported devices: A3 ALPHA meters firmware version 4.0 or later

Note: The meter must have the interrupter control relay option
board installed and be programmed in the Relay Options
component for its operation.
This task will perform the selected action on the control relay at the
specified time. Selected actions include the following:
 Do not change
The state of the control relay does not change
 Clear scheduled connect and disconnect events
Cancels all scheduled connect and disconnect events
 Connect after cold load pickup period
Connects after a specified time (as indicated by the Actual Cold
Load Pickup Period text box) after relay activation
 Connect now
Connects the relay immediately
 Disconnect now
Disconnects the relay immediately
 Connect and disconnect once at specified time
Performs a single connect or a single disconnect at the specified
date and time
 Connect and disconnect daily at specified time
Performs a daily connect and disconnect at the specified date
and time
When the function is completed, Metercat will generate a completion
report indicating the status of the task (whether it succeeded or
failed).

See also:

235
Functions and tasks

 Function Builder for information on creating a function


 Function Management for information on editing an existing
function

SET LAN RADIO TEST MODE


Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA with EA_NIC firmware
version 5.0 and later; REX2
It is possible to put the device's LAN radio into test mode, which
forces the radio to send out packets. While in radio test mode, the
radio transmits at the specified duty cycle to allow for metrology
testing under realistic field conditions. While in radio test mode, the
meter ignores all incoming network traffic.
This task will force the device to enter radio test mode. When the
function is executed, Metercat will display the Set LAN Radio Test
Mode run time dialog box. You must specify the duty cycle by
selecting the percentage in the drop list.
To exit radio test mode, perform a function with the Clear Data task
or simply cycle the meter power.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

TEST MODE OFF


Minimum password level: Unrestricted for A3 ALPHA/A1800 ALPHA
and REXUniversal; Optical for REX2
Supported devices: A3 ALPHA/A1800 ALPHA; REX2 firmware version
4.4 or later; REXUniversal
Repeatable without re-entering settings

Note: You must be connected to the meter using the optical port.
This function is disabled for direct, TCP/IP, or modem
connections.
This task will cause the meter to exit the test mode and return to
normal operating mode when the function is executed.

A3 ALPHA AND A1800 ALPHA METER EXITING TEST


MODE
The status of the meter (including billing data, profiling data, errors,
and warnings) before the meter entered test mode is preserved.
Load profiling is suspended during test mode.
When the meter exits test mode, the status of the meter is restored
to its previous state. Readings taken during test mode are discarded,

236
TM42-3060

and the present energy usage and billing data values are restored.
The interval status indicates the meter entered test mode. The meter
starts a new load profiling block.

REX2 AND REXUNIVERSAL METER EXITING TEST MODE


Energy summation registers, demand registers, and interval data do
not accumulate during test mode. From a register perspective, test
mode is the same as if there is no load applied to the meter.

See also:
 Test Mode On
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

For more information:


See technical manual for more information on your meter's behavior
and operating during and after exiting test mode.

TEST MODE ON
Minimum password level: Unrestricted for A3 ALPHA/A1800 ALPHA
and REXUniversal; Optical for REX2
Supported devices: A3 ALPHA/A1800 ALPHA; REX2 meters with
firmware version 4.4 or later; REXUniversal
Repeatable with required re-entering settings

Note: You must be connected to the meter using the optical port.
This function is disabled for direct, TCP/IP, or modem
connections.
This task will allow the meter to enter the test mode. When the
function is executed, the Test Mode On dialog box will be displayed
automatically. Depending on the meter family meter type (where
appropriate), and form factor, the information presented in the Test
Mode On dialog box will be different.

A3 ALPHA AND A1800 ALPHA METER TEST MODE


The status of the meter (including billing data, profiling data, errors,
and warnings) before the meter entered test mode is preserved.
Load profiling is suspended during test mode.
When the meter exits test mode, the status of the meter will be
restored to its previous state. Readings taken during test mode will
be discarded, and the present energy usage and billing data values
will be restored. The interval status will indicate the meter entered
test mode. The meter will start a new load profiling block.
Item Description

237
Functions and tasks

Based on meter type and the


measured quantities, you can specify
which quantity will be the basis of the
optical port pulsesA pulse is defined
from rising edge to rising edge.. The
Pulse Selection default pulse rate for the meter in
normal mode is the fixed width pulse.
In alternate and test modes, you can
select a standard pulse (equal to 1
Kh of the measured quantity) or a
fast pulse (equal to 2 Ke quantity).
The default is that the meter will exit
the test mode after 3 test intervals.
You may specify the auto-exit interval
Auto-exit after to be a number between 1 and 255
intervals. The test mode interval
length is set in the Demand
Component.
Metercat displays the energy value of
each pulseThe pulse is defined as
one rising edge to rising edge. based
Energy per pulse of the test LED
on the pulse selection, form factor,
and any adjusted values (as set in the
Constants Component).

See also:
 See Test Mode Off to learn more about meter operation when
exiting test mode.

For more information:


See the technical manual for your meter for a description of the
meter operation in test mode (typically, in Chapter 3) as well as the
operation of the optical port in test mode (typically, Chapter 5).

REX2 AND REXUNIVERSAL METER TEST MODE


The REX2 meter and REXUniversal meter test mode enables you to
perform metering accuracy tests in the field without the data
accumulating into billing registers. In the test mode, the output is not
changed from normal mode. When entering test mode, energy
summation registers, demand registers, and interval data do not
accumulate. From a register perspective, test mode is the same as if
there is no load applied to the meter.
When Test Mode On dialog box is displayed, you must specify the
length of the test mode in minutes, from 1 (default) to 255. At the
end of the time, the meter will automatically exit test mode and
resume normal operation.

See also:

238
TM42-3060

 See Test Mode Off to learn


more about the meter's operation
when exiting test mode.

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

TURN LOSS COMPENSATION OFF


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
This task turns the meter's transformer and line loss compensation
feature off without re-programming the meter with a new loss
compensation component.
The task is the equivalent of unchecking the Turn Loss
Compensation On check box to disable loss compensation in the
Loss Compensation component.

See also:
 Turn Loss Compensation On

TURN LOSS COMPENSATION ON


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A1800 ALPHA
Repeatable without re-entering settings
This task turns the meter's transformer and line loss compensation
feature on without re-programming the meter with a new loss
compensation component.
The task is the equivalent of checking the Turn Loss Compensation
On check box to enable loss compensation in the Loss
Compensation component.

See also:
 Turn Loss Compensation Off

TURN PQM OR TRUEQ ON/OFF


Minimum password level: Unrestricted
Supported devices: A3 ALPHA, A180 ALPHA
Repeatable without re-entering settings

239
Functions and tasks

Note: Depending on the language selection used for Metercat,


the TRueQ may be referred to PQM. The language setting is
controlled by Help > Language. As a standard, the Metercat
documentation will use the English (IEC) designation TRueQ,
which is also consistent with the A1800 ALPHA technical
manual. While the A1800 ALPHA meter supports the default
PQM tests, the A1800 ALPHA meter offers additional tests as
part of its tamper restraint and quality monitoring.
This task can turn the meter's PQM/TRueQ testing on or off without
re-programming the meter with a new PQM component. The task is
the equivalent of checking or unchecking the PQM On check box of
the PQM component. When the Turn PQM ON/OFF task is executed,
Metecat will display the Turn PQM ON/OFF Task run time dialog box.
 When using the Turn PQM ON/OFF task to turn the tests off, you
prevent any PQM/TRueQ tests from being executed regardless of
the individual test settings specified in the PQM component.
 When using this task to turn the tests on, you allow the
configured PQM/TRueQ tests to run (based on the configuration
programmed in the PQM component). When the function is
completed, Metercat will generate a completion report indicating
the status of the task (whether it succeeded or failed).

See also
 See PQM component for more information about PQM/TRueQ
tests and test sets.
 See Replace PQM for information on replacing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Edit PQM Thresholds for information on editing the PQM
component with new values for both PQM/TRueQ and voltage
sag.
 See Clear PQM Data for information on clearing the PQM/TRueQ
information and the voltage sag information.

For more information


See your A3 ALPHA meter technical manual for more information
regarding PQM. Typically, PQM data is described in Chapter 4, "Meter
Tools." In the A1800 ALPHA meter, PQM is referred to as TRueQ and
is typically described in Chapter 4, "Meter Tools." TRueQ offers
additional tests to the PQM test set; however, TRueQ tests are
configured in the PQM component.

UNLOCK SERVICE
Minimum password level: Unrestricted
Supported devices: A3 ALPHA/A1800 ALPHA
The A3 ALPHA meter and A1800 ALPHA meter can determine its
service (for example, 3-phase, 240 volt, 4-wire wye, ABC rotation)

240
TM42-3060

and lock the service in its memory. The locked service is used as the
basis for future system service tests, PQM tests (A3 ALPHA) or TRueQ
tests (A1800 ALPHA). The meter can lock a valid service using the
smart autolock or manual lock method. By adding this task to a
function, the function will unlock the meter's locked service when the
function is executed.
How the meter responds to the Unlock Service task depends on how
the service was locked.

SMART AUTOLOCK
Once the service is unlocked, the meter's service voltage test will be
performed. If the meter detects a new, valid service, the meter will
automatically lock on the new service. If a valid service cannot be
detected, the meter will remain locked on the last known valid
service and display an error code on the LCD.

MANUAL LOCK
Once a meter is manually locked, it can only be unlocked by using
Metercat's Unlock Service task. Once you install the meter at a new
service, the service will have to be manually locked.

UNLOCKED METER
If the meter is not programmed to lock on a valid service or is already
unlocked, then this command does not affect the meter.

For more information


The technical manual for your meter will offer information regarding
the service voltage test, locking the service, and unlocking the
service. Typically, this information is in Chapter 4, "Meter tools."

UPDATE OPTION BOARD IDENTIFICATION


Minimum password level: Unrestricted
Supported devices: EnergyAxis-enabled A3 ALPHA/A1800 ALPHA
meters (gatekeepers and nodes)

Note: You only need to execute this task if the EnergyAxis-


enabled device does not display the EnergyAxis Option tab in the
Status view.
This task will trigger the update of the option board identification
information in the EnergyAxis-enabled A3 ALPHA or A1800 ALPHA
meter. You should execute this function if the meter incorrectly
reports that no gatekeeper module or EA_NIC option board is
installed in the meter. You should also execute this function if the
EnergyAxis Option tab is not displayed in the Status view for
EnergyAxis-enabled meters.

See also:

241
Functions and tasks

 Function Builder for information on creating a function


 Function Management for information on editing an existing
function

WAN PING TEST


Minimum password level: Unrestricted
Supported devices: A3 ALPHA with E-WIC, A1800 ALPHA with E-WIC
This task will attempt to ping the head-end server. To complete this
task, you will need the head-end server's IP address. For example, if
the head-end server cannot receive the messages from a WAN-
enabled meter, this task will determine if the meter can at least
reach the server address.
When the task is executed, the WAN Ping Test dialog box will be
displayed. To ping the head-end server, you must type in the server's
IP address and click OK. When the function is completed, Metercat
will display the WAN Ping Test completion report, which will indicate
the status of the task (whether it succeeded or failed).

See also:
 Function Builder for information on creating a function
 Function Management for information on editing an existing
function

Export Endpoint Execution Request


Tools > Export Endpoint Execution Request
Beginning with release 5.0, Metercat supports an export format
known as the endpoint execution request (EER). It contains the data
and instructions that a head-end system needs to configure an A3
ALPHA meter (requires meter firmware version 5.0 or later) or a
REXUniversal meter that is an endpoint in the AMI system.
Within Metercat, a component contains the parameters that are
necessary to configure the endpoint. For example, the Display
component contains the parameters necessary to configure the
meter's LCD. A configuration is a set of one or more components. The
typical steps in configuring an endpoint over-the-air (OTA) is as
follows:
Using Metercat:
1 Create the desired components that you want to export. The
Replace Configuration task topic describes which components
can be updated for the different meters.
2 Create a function that contains the Replace Configuration task
and configure the parameters as appropriate. Give the function a
name you will recognize when completing the EER Wizard.

242
TM42-3060

3 Export the components to an EER using the Tools > Export


Endpoint Execution Request and complete the EER Wizard (see
below).
Once you have the EER, from within your head-end system:
1 Import the EER file.
2 Parse the EER and execute the instructions to configure the
endpoint.

COMPLETING THE EXPORT ENDPOINT REQUEST WIZARD


The following table describes the Export Endpoint Request Wizard,
assuming Next is clicked for each screen.
Step Description
You can select A3 ALPHA if you are
Select the device family for which you creating an EER for an A3 ALPHA
want to create the Export Execution meter or REXUniversal if you are
Request. creating an EER for the REXUniversal
meter.
Because the A3 ALPHA meter uses a
meter type-specific load profile, you
must specify the meter type as an
Specify the options for endpoint
A3T, A3K, A3Q, or A3R. You can also
device (A3 ALPHA meter only)
select Any, which removes support for
the load profile component for this
EER file creation.
From the drop list, select the function
you want to export. Metercat will
Select a function to export display only those functions that
contain the Replace Configuration
task.
Select a folder and file name for the Specify the folder and file name you
EER file want for the generated EER file.
Metercat will display the Replace
Configuration runtime dialog box.
Depending on how the function was
Replace Configuration runtime dialog
created, you can either confirm the
box
options or update them (if Prompt is
checked when the function was
created).
Metercat creates and displays the
completion report and generates the
Function completion report EER file. You can pass the EER file to
the head-end system for configuring
the endpoint.

243
Views and viewsets

About viewsets
WHAT IS A VIEWSET?
Metercat uses views to organize the data that is obtained from
reading devices. For example, you can select the Current Billing view
to see the meter's current billing data. A viewset contains one or
more views.

HOW DO I CREATE OR EDIT A VIEWSET?


Viewsets are created and managed from Viewset Management.
Metercat includes sample viewsets, which you can edit as
appropriate for your requirements. You can also create or edit your
own viewsets (including the display sort order) using Viewset Builder.
The views are set by Metercat, and you cannot create your own view.

Viewset Management
Tools > Viewset Management

Note: You must have the appropriate privileges to view, create,


edit, or delete viewsets.
You can perform the following actions from the Viewset Management
window:
 Scroll through the list of available viewsets, select and display
the included views for the selected viewset.
 Click New to create a viewset using the Viewset Builder.
 Click Edit or double-click on the viewset name to edit the
selected viewset using the Viewset Builder.
 Click Delete to delete the selected view.

Viewset Builder
Tools > Viewset Management > New
Tools > Viewset Management > Edit

Note: You must have the appropriate privileges to view, create,


edit, or delete viewsets. If you do not have the appropriate

245
Views and viewsets

privileges, the Tools > Viewset Management command will not


be available.
Viewset Builder allows you to create a viewset or to edit an existing
viewset (using the Viewset Definition tab). If you are using Metercat
in a multi-user system, you can also select which Metercat groups
will be able to use the viewset (using the Access Control tab).

BUILDING OR EDITING VIEWSETS


You must type in a name for the viewset in the Viewset Name text
box.
To include a view in a viewset, you must move a selected view from
the Available Views column to the Included Views column by either
using the Add button or by dragging the task from column to column.
If you want to remove one view from the viewset, you can click
Remove or drag it back to the Available Views column. If you click
All, all the views in the Included Views column will be moved back to
the Available Views column.
If you are building a viewset that includes more than one view, they
are presented in the order they appear in Included Views. You can
control their order using the Up and Down buttons. You can also
quickly alphabetize the Included Views list by clicking the A to Z
button.

CONTROLLING ACCESS TO A VIEWSET


If you are using Metercat in a multi-user environment, you must
specify which Metercat groups will have access to the viewset. You
can assign group privileges using the Access Control tab. Groups
listed in the Disallowed Group list will not have access to the viewset;
groups listed in the Enabled Groups list will have access to the
viewset.
Group access to viewsets can also be controlled by using the
Viewsets tab in Group Information.
If you are in a group that has authorization privileges, you can enable
another group to have access using the Viewsets tab in Group
Information.

246
TM42-3060

PERFORMING A READ
See About reading devices for information on performing reads on
connected meters or devices.

ABOUT METERCAT'S SAMPLE VIEWSETS


See Sample viewsets for more information.

LIST OF AVAILABLE VIEWS


See Available views for a complete listing of the available views.

Sample viewsets
Metercat includes a set of sample viewsets. You may edit the
viewsets as appropriate for your requirements. You may also use
them as reference to build your own functions. The following table
lists the sample viewsets along with any notes about their use.
Viewset Included views
Status
Event Log Data
Security Event Log Data
Day Types
Switch Times
Special Dates
Logs Configuration
IP AxisLink Diagnostic Event Notifications
Binary IO
Network
ACL
DNP
Day Types Pending
Switch Times Pending
Special Dates Pending
Status
Day Types
Switch Times
Special Dates
Logs Configuration
IP AxisLink Program Relay Options
Configuration Remote
Event Notifications
Binary IO
Network
ACL
DNP
Status
Current Billing
Previous Billing
Previous Season
Long Diagnostic
Self Reads
Instrumentation
Event Log Data
History Log Data

247
Views and viewsets

Interval Data (Load Profile)


Interval Data (Instrumentation)
EOI/Midnight Snapshot
Constants
Demand
Quantities
Interval Data Configuration (A3 ALPHA; A1800
ALPHA)
Instrumentation Profiling Config
Display
Special Features
Service Test
Day Types
Switch Times
Special Dates
Logs Configuration
Relay Options
Special Relay Status
Remote
Special Option Board
Demand Pending
Display Pending
Day Types Pending
Switch Times Pending
PQM
PQM/Sag Status
PQM/Sag Log Data
Status
Constants
Current Billing
Previous Billing
Meter Data
Previous Season
Self Reads
Interval Data (Load Profile)
Event Log Data
Status
Constants
Quantities
Interval Data Configuration
Display
Demand
Special Features
Program Configuration
Service Test
Day Types
Switch Times
Special Dates
Logs Configuration
Relay Options
Remote
Status
Current Billing
Previous Billing
REX Data Event Log Data
Interval Data (Load Profile)
Demand
Quantities

248
TM42-3060

Interval Data Configuration


Display
Status
Current Billing
Previous Billing
Previous Season
Self Reads
Event Log Data
Interval Data (Load Profile)
Interval Data (Instrumentation)
Instrumentation
Constants
REXUniversal Long
Demand
Diagnostic
Demand Limiting
Display
Quantities
Interval Data Configuration
Instrumentation Profiling Configuration
Voltage Monitoring
Day Types
Switch Times
Special Dates
Logs Configuration
Status
Constants
Demand
Demand Limiting
Display
Quantities
REXUniversal Program
Interval Data Configuration
Configuration
Instrumentation Profiling
Voltage Monitoring
Switch Times
Day Types
Special Dates
Logs Configuration
Status
Current Billing
Short Diagnostic Quantities
Interval Data (Load Profiling)
Event Log Data

Available views
The following table identifies all the views that are available for this
version of Metercat. Depending on various factors, including meter
family, meter type, and meter configuration, not all views may have
data.
 Example: A3D meters do not support load profiling. If you include
the load profiling view in a read of the A3D meter, Metercat will
display "Function not supported by meter type."
 Example: A3R meters do support previous season. If you include
the previous season view in a read the A3R meter before the first

249
Views and viewsets

season change occurred, Metercat will display "No data


available."
 Example: REXUniversal meters do not support power quality
monitoring. If you include the PQM view in a read of the
REXUniversal meter, Metercat will display "Function not
supported by meter type."
Some features display their data in read only windows of their
associated component. For example, the Service Test view displays
its data in a read only version of the Service Test component. In the
following table, views that use read only component windows are
indicated by blue shading (REX meter items indicated by an * are
described in the REX view only items topic). Other features use
unique windows to display their data.
REX
A3 A1800 meters IP
REXUniversal
View ALPHA ALPHA (REX, AxisLink
meter
meter meter REX2, router
gREX)
ACL •
Binary IO •
Constants • • •
Current billing (see
Note 1)
• • • •
Day types • • • •
Day types pending
(see Note 2)
• • •
Demand • • * •
Demand pending
(see Note 2)
• •
Demand limiting •
Display (see Note 3) • • * •
Display pending (see
Note 2)
• •
DNP •
EOI/midnight
snapshot

Event log data • • • • •
Event notifications •
History log data • •
Instrumentation • • • •
Instrumentation
profiling • • •
configuration
Interval data/load
profiling (see Note 4)
• • • •
Interval
data/instrumentation • • •
profiling (see Note 4)
Interval data
configuration (see • • * •
Note 5)

250
TM42-3060

Logs configuration • • • •
Network •
PQM • •
PQM/Sag log data • •
PQM/Sag status • •
Previous billing (see
Note 1)
• • • •
Previous season (see
Note 1)
• • •
Quantities (see Note
6)
• • • •
Relay options • •
Remote • •
Security event log •
Self reads (see Note
1)
• • • •
Service test • •
Special dates • • • •
Special dates
pending (see Note 2)
• • •
Special features • •
Special option board • •
Special relay status
(see Note 7)
• •
Status • • • • •
Switch times • • • •
Switch times pending
(see Note 2)
• • •
SynergyNet
notification

Temperature
monitoring

Voltage monitoring •
WAN configuration •

Notes:
1 All billing views (current, previous billing, previous season, and
self reads) are discussed in a single Billing views topic.
2 Pending views will add Perform a self read, Perform a demand
reset, and Effective date fields to the component view. These
fields are also read only.
3 For A3 ALPHA/A1800 ALPHA meters, the display configuration is
contained in the Metering component. For the REXUniversal
meter, the display configuration is contained Display component.
For the REX meter, the display configuration is contained in the
REX view only items view.
4 All interval data reporting (load profiling and instrumentation
profiling) are discussed in a single Interval data view topic.
5 A3 ALPHA/REXUniversal meter load profiling configuration is
contained in the Load Profile component; A1800 ALPHA meter

251
Views and viewsets

load profiling configuration is contained in the Metering


component. For the REX meter, the interval data configuration is
contained in the REX view only items view.
6 The quantities configuration is contained in the Metering
component.
7 The special relay status view displays just the Special Relay Tab
of the Relay Options component.

View descriptions
BILLING VIEWS

CURRENT BILLING VIEW


The Current Billing view displays the billing data for the current
period (at the time of the reading).
Item Description
Indicates the date and time that the
Date/time of billing read
billing or diagnostic read occurred.
If supported by the meter, indicates
Temperature the meter temperature (in degrees
Celsius) at the time of the reading
Indicates the total energy and the
Total maximum demand for each metered
quantity
Indicates the value for the configured
metered quantities as well as the
Rates
values for maximum demand for each
rate/tier
For meters with timekeeping ability,
Date and time indicates the date and time the
metered quantity was recorded.

See also
Additional information about the current meter information can be
found in the Status view.

PREVIOUS BILLING VIEW


The Previous Billing view displays the billing data for the previous
billing period.
Item Description
The date and time of the demand
Date/time of last demand reset
reset
Indicates the season the meter was
Season in when the demand reset occurred
that started the new billing period
If supported by the meter, indicates
Temperature the meter temperature at the time of
the demand reset

252
TM42-3060

Indicates the total energy and the


Total
maximum demand
Indicates the value for the configured
metered quantities as well as the
Rates
values for maximum demand for each
rate/tier
For meters with timekeeping ability,
Date and time indicates the date and time the
metered quantity was recorded.

PREVIOUS SEASON VIEW


The Previous Season view displays the billing data for the previous
season.
Item Description
The date and time of the season
Date/time of last season change
change
Indicates the season the meter was
Season in when the demand reset occurred
that started the new season
Indicates the total energy and the
Total
maximum demand
Indicates the value for the configured
metered quantities as well as the
Rates
values for maximum demand for each
rate/tier
For meters with timekeeping ability,
Date and time indicates the date and time the
metered quantity was recorded.

SELF READ TABS


Metercat displays a Self Read tab for each self read the meter has
recorded. The most current self read is listed first.
Item Description
Indicates the date and time the self
Date/time of self read
read occurred
If supported by the meter, the season
Season the meter was in when the self read
occurred
If supported by the meter, the meter
Temperature temperature (in degrees Celsius) at
the time the self read occurred
Indicates the value for the configured
metered quantities as well as the
Rates
values for maximum demand for each
rate/tier
Indicates the total energy and the
Total
maximum demand
For meters with timekeeping ability,
Date and time indicates the date and time the
metered quantity was recorded.

EOI/MIDNIGHT SNAPSHOT VIEW

253
Views and viewsets

Beginning with A3 ALPHA meter firmware version 5.0, the


EOI/Midnight Snapshot view displays the snapshots of the meter
total summations (as configured in the Metering component) taken
in the following cases:
 the end of the last load profile interval
 the last midnight crossing
If the midnight crossing has not occurred after the meter was
programmed, the view will display "No midnight snapshot available."
If the first interval has not ended since the meter was programmed,
the view will display "No data available."

See also:
For the REXUniversal meter, the EOI/Midnight Snapshot is contained
in the load profiling view (see Interval data view).

EVENT LOG DATA VIEW


The event log displays a sequential list of all the meter events, the
date & time of their occurrence, and other information:
Item Description
The sequence number of the event in the log.
The event log will wrap after the maximum
number of events has been recorded.
Note: For the REXUniversal meters: the
sequence number includes which log the
Seq number
event was recorded in. The REXUniversal
supports 1 metrology log and 2
communications logs. See the Event Log
Configuration component topic for more
information.
The date and time of the event. If the meter
does not have or loses real time, then the
data will be displayed differently.

For A3D meters: the Date/Time column is


removed. Only a sequential listing of events is
provided.
For timekeeping A3 ALPHA/A1800 ALPHA &
Date/time REXUniversal: relative dates begin with 01-
Jan-00 until the real date is acquired. Relative
time, beginning with 00:00, is used until the
meter acquires real time.
For REX/REX2/gREX meters: relative dates
are masked out with an * until the real date is
acquired. Relative time, beginning with 00:00,
is used until the meter acquires real time.

Indicates the type of event that is being


Event
recorded.
Indicates the Metercat user ID (see User ID
User ID
assignments for more information).

254
TM42-3060

If used, indicates data associated with the


Event argument
event. For example: voltage or energy value.

Notes:
 For the REXUniversal meter & IP AxisLink device, see Event Log
Configuration component for a listing of the configurable events
that can be recorded.
 For the A3 ALPHA/A1800 ALPHA meter, see Logs component for
a listing of the configurable events that can be recorded.
 For the REX/REX2/gREX meter, the configurable events are set
by EA_MS or at factory programming.

HISTORY LOG DATA VIEW


The history log can be used to store table information and procedure
IDs for configuration-altering writes to the meter. Demand only
meters store a sequential listing of records. TOU meters also record
the date and time. The meter records this information as an audit
trail, maintaining a history of programming changes made to the
meter. After the maximum number of entries has been stored, the
meter will begin overwriting the oldest entries or will prevent any
further changes until the history log has been read, depending on the
meter configuration.
Recording of events in the history log is configured in the Logs
component.

INSTRUMENTATION VIEW

A3 ALPHA/A1800 ALPHA METER INSTRUMENTATION


VIEW
The instrumentation view displays the phasor diagram, power
relationship, and harmonic content from the meter.

Phasor diagram
The phasor diagram tab displays the following data read from the
meter.

Note: The data is not updated in real time. To view the data in
real time, use the PQ Inspector task.
 Voltage
 Voltage phase angle
 Current
 Current phase angle
 Power factor
 Power factor angle
 kW

255
Views and viewsets

 kVAR
 Line frequency
 phasor diagram

Power relationship
If the connected meter has power quality monitoring and it is turned
on (see PQM component), then the instrumentation view will display
the power relationship data:

Note: The data is not updated in real time. To view the data in
real time, use the PQ Inspector task.
 Voltage
 Current
 Power factor angle
 kW
 kVA
In addition, the tab also displays total system power measurements
for the following:
 kW
 kVAR
 kVA
 Power factor
The power relationship diagram displays the power vector for each
phase and for the system (total) in a 4-quadrant graph.

Harmonic content
If the connected meter has power quality monitoring and it is turned
on (see PQM component), then the instrumentation view will display
the harmonic content data and graph:

Note: The data is not updated in real time. To view the data in
real time, use the PQ Inspector task.
 harmonic content (% of the fundamental) of voltage and current
up to the 15th harmonic
 a bar chart (% vs. harmonic) of the values measured
 per phase measures of the rms of voltage and current
 per phase measures of the total harmonic distortion (THD)
values of voltage and current

REX2 METER INSTRUMENTATION VIEW


Beginning with REX2 meter firmware version 5.4, the meter can
measure, display on the LCD, and report the instantaneous system
power factor and the instantaneous RMS current using Metercat. The

256
TM42-3060

instrumentation view displays the following information obtained


from the connected meter:
 Phase A current
 Phase C current (Form 12S meters only)
 Phase A voltage
 Phase C voltage (Form 12S meters only)
 System power factor

If the meter firmware version is earlier than version 5.4, the


instrumentation view will display "no data available."

REXUNIVERSAL METER INSTRUMENTATION VIEW


The instrumentation view displays the following information obtained
from the connected meter:
 Demand 1 & 2
 Per phase current and voltage
 Per phase watt/VAR/VA
 System (total) watts/VAR/VA

INTERVAL DATA VIEW


Interval data views contain the following navigation items:
 There is a separate tab for each data set (for example, pulse
data, EOI/midnight snapshots, or instrumentation profiling sets).
 The navigation arrows perform the following actions:
o Up arrow (): Collapse all days. Displays only the dates for
the interval data in the meter reading. Clicking on one date
shows the meter interval data collected on that date.
o Down arrow (): Expand all days. Displays the interval data
for every date contained in the meter readings. You must
click this button to have all interval data appear on a report
(File > New > Report).
o Left arrow (): Hide status columns. Hides the status
information column (that is, only the date and data
information is displayed).
o Right arrow (): Show status columns. Shows the status
information column in addition to the date and data
information.
 The time listed in interval data is based on the time as reported
by the meter.

A3 ALPHA METER INTERVAL DATA

257
Views and viewsets

Interval data uses two types of statuses: interval and channel (for
each specific interval). With the exception of the current interval
status, all status values are set by the meter.
 Dst - Daylight Saving Time (Summer Time) is in effect during the
interval
 Pwr - Power Failure or power restoration occurred during the
interval
 ClkF - meter clock was changed forward to a new time during the
interval
 ClkB - meter clock was changed backward to a new time during
the interval
 Cur - the interval is the current interval
More than one channel status may occur in an interval; however, due
to ANSI C12.19 limitations, only one value will be displayed
according to the priorities, from highest to lowest:
 Test - interval contains test mode data. The meter entered or
exited test mode during the marked interval.
 Overflow - Channel overflow. The data accumulated during the
interval exceeded the data format chosen for the interval.
 Skipped - Skipped interval. There was no data available for the
channel during the interval.
 Long - Long interval. The interval length was longer than its
configured length.
 Partial - Partial interval. The interval length was shorter than its
configured length.
 Blank - No event occurred that required flagging of the interval.

Load profiling
This view displays the meter's load profiling interval data by date and
interval stop time for all recorded channels.
To view the pulse count based on its divisor, check the Display
scaled pulse count box.

Instrumentation profiling
In meters with instrumentation profiling (designated with the N suffix
in the meter type), the meter has two sets of instrumentation
profiling. Each set can record up to 16 channels as configured in the
Instrumentation profiling component.

A1800 ALPHA METER INTERVAL DATA


Interval data uses two types of statuses: interval and channel (for
each specific interval). With the exception of the current interval
status, all status values are set by the meter.
 Dst - Daylight Saving Time (Summer Time) is in effect during the
interval

258
TM42-3060

 Pwr - Power Failure or power restoration occurred during the


interval
 ClkF - meter clock was changed forward to a new time during the
interval
 ClkB - meter clock was changed backward to a new time during
the interval
 Cur - the interval is the current interval
More than one channel status may occur in an interval; however, due
to ANSI C12.19 limitations, only one value will be displayed
according to the priorities, from highest to lowest:
 Test - interval contains test mode data. The meter entered or
exited test mode during the marked interval.
 Overflow - Channel overflow. The data accumulated during the
interval exceeded the data format chosen for the interval.
 Skipped - Skipped interval. There was no data available for the
channel during the interval.
 Long - Long interval. The interval length was longer than its
configured length.
 Partial - Partial interval. The interval length was shorter than its
configured length.
 Blank - No event occurred that required flagging of the interval.

Load profiling
This view displays the meter's load profiling interval data by date and
interval stop time for all recorded channels. The view also indicates
the interval data mode (configured in the A1800 ALPHA meter's
Metering component) as either pulses, engineering units, or
cumulative engineering units.
To view the pulse count based on its divisor (configured in the A1800
ALPHA meter's Metering component), check the Display scaled
pulse count box.

Instrumentation profiling
For A1800 ALPHA meters with instrumentation profiling capabilities,
the meter has two sets of instrumentation profiling. Each set can
record up to 16 channels as configured in the Instrumentation
profiling component.

REX/REX2 METERS
For REX and REX2 meters, interval data is configured at the time of
ordering. For more information, see the meter technical manual for
your meter.

REX meter interval data


The REX meter supports load profiling for either up to 104 records
(REX firmware versions 1.0 and 2.0) or up to 480 records (REX

259
Views and viewsets

firmware version 3.0). The load profiling record can be scaled by a


pulse divisor and with a status flag to indicate if a power failure or
time change occurred during the interval. For more information, see
the REX meter technical manual TM42-2210B).

REX2 meter interval data


Depending on the meter firmware version, the REX2 meter is capable
of recording one or, beginning with meter firmware version 4.0, two
sets of interval data. Each set contains 1 or 2 channels of
information, depending on how the meter is programmed. Each set
has its own, separate interval length that is configured
independently. With two sets, it is possible to use set 1 to record
interval data and to use set 2 as an instrumentation profile log. It is
also possible to program the meter to use set 1 and set 2 to record
4-quadrant energy values.

Note: If the metered quantity is a net quantity, the quantity's


delivered pulses are stored in the interval data records.
 set 1
o The source for the first channel is the first energy source
o if configured for 2 channels, the source for the second
channel is the second energy source
 set 2 (requires meter firmware version 4.0 or later)
o The source for the first channel is either a valid energy
source or an instrumentation quantity
o The source for the second channel is either a valid energy
source or an instrumentation quantity
When storing energy quantities, an interval data record stores the Kh
pulses of the selected metered quantity (scaled by the pulse divisor)
per channel with status flags to indicate the following events if they
occur in the interval: power failure, power restoration, or time
change.
In addition, REX2 meters, beginning with meter firmware version 3.0,
can be programmed to record only specific events and their
associated time stamps. When programmed to record only events,
the REX2 meter excludes billing-related data.

Instrumentation quantities

When configured for 2 sets of interval data (which requires meter


firmware version 4.0 or later), the second set, containing 1 or 2
channels, can be programmed to record either energy values or
instrumentation quantities. When programming to record
instrumentation quantities, instrumentation is based on the per
phase voltage with a resolution of 32 line cycles. Each channel can
be configured to record instrumentation data in any one of the
following ways:
 Minimum: the meter samples the voltage over the interval, and
the minimum value is recorded.

260
TM42-3060

 Maximum: the meter samples the voltage over the interval, and
the maximum value is recorded.
 Average: the meter samples the voltage over the interval, and
the average value is recorded.
 Snapshot: the meter samples the voltage at the end of an
interval, and the last available voltage is recorded.

EOI/midnight snapshots

Beginning with the REX2 meter firmware version 5.0, REX2 meter
interval data will include the snapshots of the meter total
summations taken in the following cases:
 the end of the last interval profiling interval
 the last midnight crossing
If the midnight crossing has not occurred after the meter was
programmed, the view will display "No midnight snapshot available."
If the first interval has not ended since the meter was programmed,
the view will display "No data available." If the metered quantity is an
instrumentation or net quantity, the view will display "n/a," indicating
the value is not available.

REXUNIVERSAL METER INTERVAL DATA


Interval data can indicate the following:
 power fail: a power failure occurred during the interval
 long: interval data may contain data for a duration longer than
the interval length due to one of the following:
o a backward time change of more than 5 seconds that did
not cross an interval boundary. Backward time changes that
cross the current interval boundary create status records
which report the time change event.
o data accumulated for the reported interval occurred while
the meter was keeping relative time. The interval is not
guaranteed to be aligned to a real time clock boundary and
may be equivalent to a long interval.
 Time changed: the time changed in the interval.
 Configuration changed: the number of channels recorded by the
meter changed.

Data
This view displays the meter's load profiling interval data by date and
interval stop time for all recorded channels.
To view the pulse count based on its divisor, check the Display
scaled pulse count box.

EOI/midnight snapshot

261
Views and viewsets

The EOI/Midnight Snapshot view displays the snapshots of the meter


total summations (as configured in the Metering component) taken
in the following cases:
 the end of the last load profile interval
 the last midnight crossing
If the midnight crossing has not occurred after the meter was
programmed, the view will display "No midnight snapshot available."
If the first interval has not ended since the meter was programmed,
the view will display "No data available."

PQM/SAG LOG DATA VIEW


The PQM/Sag Log Data view displays the log data for PQM tests (as
defined in the PQM component) as well as for voltage sag events for
the current billing period.

PQM LOG TAB


The PQM log tab displays the following information:
Item Description
Indicates the order that the PQM test
Seq. no.
failure occurred in.
Indicates the date and time the PQM
test exceeded the set thresholds and
the qualification time.
Date/time
The date/time indicated here may be
(timekeeping meters only)
different than PQM/Sag Status view
because the qualification time is not
a factor in the PQM/Sag Status view.
Test no. Indicates the PQM test number.
Test name Indicates the name of the PQM test.
Indicates whether the specific event
was one of the following:

Status Start - testing exceeds test thresholds


and qualification time
Stop - test falls within test thresholds

Some tests store data when a PQM


test fails. See the PQM component
topic for a listing of each PQM test by
Optional value
meter family and test set. See the
topic for each particular test for more
information about each test.

SAG LOG TAB


The Sag log tab displays the following information:
Item Description
Indicates the order that the sag
Seq. no.
events occurred in.

262
TM42-3060

Date/time Indicates the date and time the sag


(timekeeping meters only) event occurred.
Event Indicates the details of the sag event.

PQM/SAG STATUS VIEW


The PQM/Sag Status view displays the status data for PQM test and
voltage sags for the current billing period.
See the PQM Component for information about PQM, sag, and a
listing of the different PQM tests and test sets supported by each
meter.

PQM STATUS TAB


The PQM Status tab displays the following information:
Item Description
Test no. Indicates the test number
Test name Indicates the test name
Indicates the total number of times
Cumulative count
the specific PQM test failed
Indicates the total amount of time
that the specific PQM test failed
Cumulative failure time
(does not include an event that is in
progress)
This item only applies to test
thresholds. Qualification times are
not a factor. Indicates one of the
following:

For both demand only and TOU


meters: No if the test is currently
within the defined thresholds.
For demand only meters: Yes (test
thresholds are currently exceeded)
In progress
For TOU meters: the date/time the
specific test thresholds were first
exceeded.

Because the qualification time is not


a factor, the date/time indicated here
may be different than PQM/Sag Log
Data view. The PQM/Sag Log Data
view does take qualification time into
consideration.

SAG STATUS TAB


The Sag Status tab displays the following information:

Item Description

263
Views and viewsets

Indicates the total number of


Cumulative voltage sag count times there was a qualifying
sag event for each phase
Indicates the total time (in
Cumulative voltage sag
seconds) there was a qualifying
duration (sec)
sag for each phase
Indicates the total number of
Events with duration less than
times there was a sag event
minimum sag time
that lasted less than the
(NoteRequires meter firmware
configured minimum sag
version 3.0 or later)
duration
Indicates the total number of
Events with duration greater
times there was a sag event
than maximum sag time
that lasted longer than the
(NoteRequires meter firmware
configured maximum sag
version 3.0 or later)
duration

REX VIEW ONLY ITEMS

DEMAND VIEW
Item Description
Displays the length of the
demand interval programmed
in the meter. The demand
Interval (minutes)
interval length is specified in
minutes and may be 5, 15, 30,
or 60.
Displays the length of the
demand subinterval
programmed in the meter. The
subinterval length is specified
Subinterval (minutes)
in minutes. If the subinterval
length is equal to the interval
length, then the meter is using
block demand.
Displays the demand threshold
value in kilo units programmed
in the meter. When demand
exceeds this value, the meter
Threshold (kilo units) will issue an exception
message, set the demand
threshold exceeded status,
and perform demand limiting
(if enabled).
Displays the demand forgives
time programmed in the
Demand forgiveness time meter. The demand
(minutes) forgiveness time is specified in
minutes. Demand forgiveness
is the time demand is not

264
TM42-3060

calculated or stored after a


restoration from an outage.

DISPLAY VIEW
The Display view identifies the display list items programmed in the
meter. It also lists the hold time (the number of seconds the item will
display on the LCD) and the index (the order of the display items).

INTERVAL DATA CONFIGURATION VIEW


Item Description
Displays the length of the
interval data record (in
minutes) programmed in the
Interval length meter. Interval data has a
separate, independent length
from the demand interval
length.
Displays the interval data
pulse divisor programmed in
the meter. Each interval data
record can store 4095 pulses
before overflowing. A pulse
divisor can be used to scale
Pulse divisor down the number of pulses Kh
pulses recorded in each
record.
For example, if the Kh value is
1.0 and the divisor is set to
10, then each pulse count
represents 10 Wh/VAh/VARh.
Displays the billing quantities
the REX meter is measuring.
Quantities to record The primary energy quantity is
listed first, and the alternate
quantity is listed second.

SECURITY EVENT LOG VIEW


The Security event log view displays the security events recorded by
the IP AxisLink device.
Column Description
Indicates the order that the security
Seq number
event occurred in.
Indicates the device date & time taht
Date/time
the event occurred.
User ID Indicates the user ID assignment
Indicates the specified event (see
Event code
Event codes below)
Indicates that the operation was
Status successful (0) or that the operation
failed (1)

265
Views and viewsets

Indicates the source of the event:

0 = local port (USB)


1 = WAN port (wired/wireless)
Source code 2 = Edge port
3 = LAN device
4 = Self operation
5 = Web page

Indicates the intended destination:

0 = AGI
Destination code 1 = LANOB
2 = WWAN
3 = Tunnel

For event codes 1, 3, 4, 5:

Host device IP address


Host device port

For event code 11:


Event data 1 and 2
Table ID

For event code 12:

Page ID

EVENT CODES
Event code Description
0 Security configuration change
MSG rec'd does not meet security
1
requirements
2 MSG re'd not unique
Failed to authenticate/decrypt rec'd
3
MSG
4 Promotion of pending seed to activate
5 Copy of active seed to pending
6 Re-seed action occurred
7 Set factory seed action
8 Activate factory seed action
9 Access control list was modified
10 Program flash update occurred
11 Table write operation occurred
12 POST request from web interface
13 Web access authentication failure

SPECIAL OPTION BOARD VIEW

266
TM42-3060

This view displays the meter's special option board's configuration


information, including manufacturer-specific information.

STATUS VIEW
The status view displays manufacturing, diagnostic, and other status-
related information.

A3 ALPHA METER STATUS

General tab
The General tab displays details such as the meter's manufacturer,
the meter type, hardware/firmware version information, option
boards and option board firmware, and the Alpha Key status.
Item Description
Identifies the meter manufacture. EE
Manufacturer represents Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.
The style number of the meter at the
time of manufacture. This style
Original style number number will not reflect any hardware
or Alpha Key changes made to the
device after it was manufactured.
The amount of memory in KB
available for the meter's shared
Main EEPROM memory memory (see Load Profile component
for more information on the A3 ALPHA
meter's shared memory).
The amount of extended memory (in
Extended memory KB) provided by an option board (if
present)
Identifies how the reading was
Reading reason obtained (for example: manual =
using an optical probe)
Identifies the hardware version and
Hardware version
revision of the meter.
Identifies the firmware version and
Firmware version
revision.
Additional manufacturer information
Firmware S-Spec
that identifies the meter family.
DSP version The meter engine revision code.
Factory code indicating the version
SM version and revision of the measurement
sources.
Factory code indicating the version
PQM version and revision of the PQM
configuration.
Indicates the option boards that may
Option boards be present in the meter along with
manufacturing information for each.
Indicates the status of the Alpha
Alpha Keys Keys:

267
Views and viewsets

Enabled: the functionality has been


unlocked and is accessible
Disabled: this function must be
purchased and unlocked before it can
be accessible

The date and time the meter was


Date of last key change most recently upgraded using Alpha
Keys.
Displays comments entered by the
Reader notes reader during the execution of the
reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.

Item Description
Typically, this will be the Meter
ID. The label is defined in Site
ID #2 ID Labels, and the value is
written to the meter when it is
programmed.
Typically, this will be the
Account. The label is defined in
ID #1 Site ID Labels, and the value is
written to the meter when it is
programmed.
Utility-specified identifier
configured in the meter at the
time of manufacture; if no
Utility serial number special requests were made at
the time of manufacture, this
number will also be the
manufacturer serial number.
The remote device ID for each
communication port. A 1
indicates the port has a
dedicated communications
Port 1 and Port 2 device ID
link; any other value is used in
applications where multiple
devices share a common
communications link.
The program number (specified
Program at the time the Metercat
program is created).

268
TM42-3060

The user ID of the person who


Programmer wrote the program to the
meter.
Indicates whether the meter is
Program function demand-only meter or a TOU
meter.
User-defined display items set
Custom display strings 1 and 2
in the Properties component.
Identifies the factory set
UDT configuration configuration values for the
user defined table.
Version of ANSI C12.19 (Utility
C12.19 Rev industry end device data
tables) supported by the meter.

Conditions tab
The Conditions tab displays the meter's conditions at the time the
reading was obtained (for example: any events, warnings, or errors
were recorded).

Item Description
The operating mode of the
meter (normal, alternate, test);
see Chapter 3 of the meter
Mode
technical manual for
information on the operating
mode.
Indicates the service of the
meter and whether or not the
service is locked; see Chapter
Service
4 of the meter technical
manual for information on
service and locking.
Indicates the line frequency;
Line frequency the meter supports a nominal
50 Hz or 60 Hz ± 2%
The average time (in seconds)
it takes to make a complete
Avg. PQM update
loop through the PQM tests
configured in the meter.
The average time (in seconds)
Avg. present value update it takes the meter to update its
list of present value quantities.

269
Views and viewsets

Indicates whether or not the


meter display is locked by a
warning (see the Display
Display locked by warning
subcomponent, Warnings tab
in the Metering component for
more information).
Indicates whether or not the
Modem initialized modem has been initialized for
remote communication.
IP avg. samples/interval (per
set)
See A3 ALPHA meter codes for
Events a listing of events that can be
reported by Metercat.
See A3 ALPHA meter codes for
Warnings a listing of warnings that can
be reported by Metercat.
See A3 ALPHA meter codes for
Errors a listing of errors that can be
reported by Metercat.
Indicates components and
Pending replacements modules that are scheduled to
be replaced in the future.

Security tab
The Security tab displays the following information, which can be
useful in determining if there has been any unusual activity that may
indicate tampering with the meter:
Item Description
For each port, Metercat reports the
date and time of the last table write,
Port 1 & Port 2 (Optical) status the number of invalid password
information attempts, and the number of
communication sessions with a write
to the meter.
The date and time of the most recent
Date of last programming
meter programming.
Indicates whether or not the meter's
register data using the Register Edit
Data edited
task. This value can only be cleared
by reprogramming the meter.
The total number of demand resets
Total number of resets
regardless of method.
Indicates the method of demand
Last reset trigger reset:

270
TM42-3060

None: no reset occurred


Button press: manual demand reset
by pressing the RESET button
Communication: a demand reset
occurred as a result of a
communication procedure
Calendar: a demand reset was
triggered by a meter calendar entry

The number of days (midnight


Days since last reset crossings) that have occurred since
the most recent demand reset.
The date and time of the most recent
Date of last reset
demand reset regardless of method.
The number of days (midnight
Days since last pulse crossings) since the last energy pulse
was detected.
The date and time of the most recent
Last outage start
start of a power failure.
The date and time of the most recent
Last outage end
power restoration.
The length of time the meter has
Battery usage time
used the TOU battery.
The number of outages that exceeded
the threshold and are considered a
Sustained power outages count
sustained outage (configured in the
Logs component).
The length of time of sustained power
Sustained power outage time
outages.
The number of outages that are less
than or equal to the threshold and
Momentary power outages count
are considered momentary outages
(configured in the Logs component).

Time tab
The Time tab identifies the date and time of the reading.

Item Description
The date and time the reading
Date/Time of reading was captured (based on the PC
clock).
The meter date and time
Meter date/time
(based on the meter clock).
The day of the week based on
Day of week
the meter clock.
Whether or not the meter was
Holiday
in a holiday rate/tier.
Whether or not the meter is in
DST status
Daylight Saving Time.

271
Views and viewsets

The current energy rate/tier of


Rate (energy) the meter at the time of the
reading.
The current demand rate/tier
Rate (demand) of the meter at the time of the
reading.
The current season of the
Season meter at the time of the
reading.
The "old" time of the meter
Meter time when time change
when it received the time
requested
change request.
The "new" time of the meter
Meter time after time change
after it processed the time
requested
change request
Indicates whether the meter is
using the line frequency or the
Clock source
crystal oscillator to maintain its
internal clock.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.

Item Description
Ke Identifies the factory Ke
Kh Identifies the factory Kh
Identifies the factory pulses to
P/R
equivalent disk revolution
Identifies the manufacturer's
Serial no.
serial number
Indicates if the meter has
Configuration errors detected any configuration
errors
Indicates if the meter has
CRC errors
detected any CRC errors

EnergyAxis Options tab


The EnergyAxis Options tab displays information about EnergyAxis-
enabled A3 ALPHA meters.

272
TM42-3060

Note: If the EnergyAxis Options tab is not displayed, execute a


function that contains the Update Option Board Identification
task.

A3 ALPHA meter as an EnergyAxis node

Item Description
Identifies the hardware version
Hardware version
of the EA_NIC option board.
Identifies the firmware version
Firmware version and revision of the EA_NIC
option board.
Additional manufacturing
Firmware S-Spec information for the EA_NIC
option board.
For meters as endpoints within
LAN node type the EnergyAxis network, this
will be RF Node.
The unique communications ID
LAN ID
within the network.
All meters within the same
Utility ID EnergyAxis network use the
same utility ID
The amount of memory the
Used shared memory EA_NIC has used (strictly for
network activity)
The amount of memory
Available shared memory available to the EA_NIC for its
network activity
For a listing of possible errors
detected by the EA_NIC, see
Errors the A3 ALPHA meter with
EA_NIC product guide (PG42-
1017).

A3 ALPHA meter as an EnergyAxis gatekeeper

Item Description
Identifies the hardware version
Hardware version
of the EA_Gatekeper module.

273
Views and viewsets

Identifies the firmware version


Firmware version and revision of the
EA_Gatekeper module.
Additional manufacturing
Firmware S-Spec information for the
EA_Gatekeper module.
For meters as gatekeepers
LAN node type within the EnergyAxis network,
this will be RF Collector.
The unique communications ID
LAN ID
within the network.
All meters within the same
Utility ID EnergyAxis network use the
same utility ID
The amount of memory the
Used shared memory EA_NIC has used (strictly for
network activity)
The amount of memory
Available shared memory available to the EA_NIC for its
network activity
For a listing of possible errors
detected by the gatekeeper
Errors module, see the
EA_Gatekeeper product guide
(PG42-1023).
The number of
nodes/endpoints that have
Registered nodes
registered with the gatekeeper
module.
The number of devices acting
Repeaters as repeaters that are registered
with the gatekeeper module.
List of those events that can
occur in the LAN. All possible
events are listed with their start
Event list and stop time (if applicable):
Meter read: the last date/time
that the gatekeeper read its
registered meters.

274
TM42-3060

Profile read: the last date/time


the gatekeeper read profiling
data from its registered meters.
time broadcast: the last
date/time the gatekeeper
broadcasted its time signal to
the LAN.
Node scan: the last date/time
the gatekeeper performed a
full node scan, which is at start
up and on a scheduled basis.
Partial node scan: the last
date/time the gatekeeper
performed a partial node scan,
which is handled when the
gatekeeper receives a node
scan request.
Brute force node read: the last
date/time of a brute force node
rad, which is performed every
hour and looks for meters with
read times older than a certain
value and forces a read from
those devices.
Clear all nodes status: the last
date/time the Clear All Nodes
Status was executed by the
head-end system (resets total
read attempts and total read
successes from a node).

A1800 ALPHA METER

General tab
The General tab displays details such as the meter's manufacturer,
the meter type, hardware/firmware version information, option
boards and option board firmware, and the Alpha Key status.

Item Description
Identifies the meter
manufacture. EE represents
Manufacturer
Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.

275
Views and viewsets

The style number of the meter


at the time of manufacture.
This style number will not
Original style number reflect any hardware or Alpha
Key changes made to the
device after it was
manufactured.
The amount of memory in KB
available for the meter's shared
memory (see Metering
Main EEPROM memory component for more
information on the A1800
ALPHA meter's shared
memory).
The amount of extended
Extended memory memory (in KB) provided by an
option board (if present)
Identifies how the reading was
Reading reason obtained (for example: manual
= using an optical probe)
Identifies the hardware version
Hardware version
and revision of the meter.
Identifies the firmware version
Firmware version
and revision.
Additional manufacturer
Firmware S-Spec information that identifies the
meter family.
The meter engine revision
DSP version
code.
Factory code indicating the
SM version version and revision of the
measurement sources.
Factory code indicating the
PQM version version and revision of the
PQM configuration.
Indicates the option boards
that may be present in the
Option boards meter along with
manufacturing information for
each.
Indicates the status of the
Alpha Keys
Alpha Keys:

276
TM42-3060

Enabled: the functionality has


been unlocked and is
accessible
Disabled: this function must be
purchased and unlocked
before it can be accessible
The date and time the meter
Date of last key change was most recently upgraded
using Alpha Keys.
Displays comments entered by
Reader notes the reader during the execution
of the reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.

Item Description
Typically, this will be the Meter
ID. The label is defined in Site
ID #2 ID Labels, and the value is
written to the meter when it is
programmed.
Typically, this will be the
Account. The label is defined in
ID #1 Site ID Labels, and the value is
written to the meter when it is
programmed.
Utility-specified identifier
configured in the meter at the
time of manufacture; if no
Utility serial number special requests were made at
the time of manufacture, this
number will also be the
manufacturer serial number.
The remote device ID for each
communication port. A 1
indicates the port has a
dedicated communications
Port 1 and Port 2 device ID
link; any other value is used in
applications where multiple
devices share a common
communications link.

277
Views and viewsets

The program number (specified


Program at the time the Metercat
program is created).
The user ID of the person who
Programmer wrote the program to the
meter.
Indicates whether the meter is
Program function demand-only meter or a TOU
meter.
User-defined display items set
Custom display strings 1 and 2
in the Properties component.
Identifies the factory set
UDT configuration configuration values for the
user defined table.
Version of ANSI C12.19 (Utility
C12.19 Rev industry end device data
tables) supported by the meter.
Identifies the physical address
DLMS physical address of the meter for use with the
DLMS protocol.

Conditions tab
The Conditions tab displays the meter's conditions at the time the
reading was obtained (for example: any events, warnings, or errors
were recorded).

Item Description
The operating mode of the
meter (normal, alternate, test);
see Chapter 3 of the meter
Mode
technical manual for
information on the operating
mode.
Indicates the service of the
meter and whether or not the
service is locked; see Chapter
Service
4 of the meter technical
manual for information on
service and locking.
Indicates the line frequency;
Line frequency the meter supports a nominal
50 Hz or 60 Hz ± 2%

278
TM42-3060

The average time (in seconds)


it takes to make a complete
Avg. PQM update
loop through the PQM/TRueQ
tests configured in the meter.
The average time (in seconds)
Avg. present value update it takes the meter to update its
list of present value quantities.
Indicates whether or not the
meter display is locked by a
warning (see the Display
Display locked by warning
subcomponent, Warnings tab
in the Metering component for
more information).
Indicates whether or not the
Modem initialized modem has been initialized for
remote communication.
IP avg. samples/interval (per
set)
See A1800 ALPHA meter codes
Events for a listing of events that can
be reported by Metercat.
See A1800 ALPHA meter codes
Warnings for a listing of warnings that
can be reported by Metercat.
See A1800 ALPHA meter codes
Errors for a listing of errors that can
be reported by Metercat.
Indicates components and
Pending replacements modules that are scheduled to
be replaced in the future.

Security tab
The Security tab displays the following information, which can be
useful in determining if there has been any unusual activity that may
indicate tampering with the meter:

Item Description
For each port, Metercat reports
Port 1 & Port 2 (Optical) status the date and time of the last
information table write, the number of
invalid password attempts, and
the number of communication

279
Views and viewsets

sessions with a write to the


meter.
The date and time of the most
Date of last programming
recent meter programming.
Indicates whether or not the
meter's register data using the
Data edited Register Edit task. This value
can only be cleared by
reprogramming the meter.
The total number of demand
Total number of resets
resets regardless of method.
Indicates the method of
demand reset:
None: no reset occurred
Button press: manual demand
reset by pressing the RESET
button
Last reset trigger
Communication: a demand
reset occurred as a result of a
communication procedure
Calendar: a demand reset was
triggered by a meter calendar
entry
The number of days (midnight
crossings) that have occurred
Days since last reset
since the most recent demand
reset.
The date and time of the most
Date of last reset recent demand reset
regardless of method.
The number of days (midnight
Days since last pulse crossings) since the last energy
pulse was detected.
The date and time of the most
Last outage start
recent start of a power failure.
The date and time of the most
Last outage end
recent power restoration.
The length of time the meter
Battery usage time
has used the TOU battery.

Time tab

280
TM42-3060

The Time tab identifies the date and time of the reading.

Item Description
The date and time the reading
Date/Time of reading was captured (based on the PC
clock).
The meter date and time
Meter date/time
(based on the meter clock).
The day of the week based on
Day of week
the meter clock.
Whether or not the meter was
Holiday
in a holiday rate/tier.
Whether or not the meter is in
DST status
Daylight Saving Time.
The current energy rate/tier of
Rate (energy) the meter at the time of the
reading.
The current demand rate/tier
Rate (demand) of the meter at the time of the
reading.
The current season of the
Season meter at the time of the
reading.
The "old" time of the meter
Meter time when time change
when it received the time
requested
change request.
The "new" time of the meter
Meter time after time change
after it processed the time
requested
change request
Indicates whether the meter is
using the line frequency or the
Clock source
crystal oscillator to maintain its
internal clock.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.

Item Description
Ke Identifies the factory Ke

281
Views and viewsets

Kh Identifies the factory Kh


Identifies the factory pulses to
P/R
equivalent disk revolution
Identifies the manufacturer's
Serial no.
serial number
Indicates if the meter has
Configuration errors detected any configuration
errors
Indicates if the meter has
CRC errors
detected any CRC errors

EnergyAxis options tab


The EnergyAxis Options tab displays information about EnergyAxis-
enabled A1800 ALPHA meters.

Note: If the EnergyAxis Options tab is not displayed, execute a


function that contains the Update Option Board Identification
task.

A1800 ALPHA meter as an EnergyAxis node

Item Description
Identifies the hardware version
Hardware version
of the EA_NIC option board.
Identifies the firmware version
Firmware version and revision of the EA_NIC
option board.
Additional manufacturing
Firmware S-Spec information for the EA_NIC
option board.
For meters as endpoints within
LAN node type the EnergyAxis network, this
will be RF Node.
The unique communications ID
LAN ID
within the network.
All meters within the same
Utility ID EnergyAxis network use the
same utility ID
The amount of memory the
Used shared memory EA_NIC has used (strictly for
network activity)

282
TM42-3060

The amount of memory


Available shared memory available to the EA_NIC for its
network activity
For a listing of possible errors
detected by the EA_NIC, see
Errors
the EA_NIC product guide
(PG42-1017).

Read without Power tab


The Read without Power tab displays the following information about
the meter's Read without Power feature:
Item Description
Identifies the state of Read without
Status
Power at the time of the reading
Identifies the state of the Read
Battery status
without Power battery
Identifies the voltage level of the
Battery voltage
Read without Power battery
Indicates how long the meter had
Total active time
Read without Power activated
Identifies how many times the Read
Total use count
without Power feature was activated

REX METER

General tab
The General tab displays details such as the meter's manufacturer,
the meter type, hardware/firmware version information, option
boards and option board firmware, and the Alpha Key status.
Item Description
Identifies the meter manufacture. EE
Manufacturer represents Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.
The style number of the meter at the
time of manufacture. This style
Original style number number will not reflect any hardware
or Alpha Key changes made to the
device after it was manufactured.
Identifies how the reading was
Reading reason obtained (for example: manual =
using an optical probe)
Identifies the hardware version and
Hardware version
revision of the meter.
Identifies the firmware version and
Firmware version
revision.
Additional manufacturer information
Firmware S-Spec
that identifies the meter family.

283
Views and viewsets

Displays comments entered by the


Reader notes reader during the execution of the
reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.

Item Description
Typically, this will be the Meter
ID. The label is defined in Site
ID #2 ID Labels, and the value is
written to the meter when it is
programmed.
Typically, this will be the
Account. The label is defined in
ID #1 Site ID Labels, and the value is
written to the meter when it is
programmed.
Manufacturer-configured
Manufacturing order number number identifying the order
information.
Program The program number.
User-defined display items set
Custom display strings 1 and 2
in the Properties component.

Conditions tab
The Conditions tab displays the meter's conditions at the time the
reading was obtained (for example: any events, warnings, or errors
were recorded).

Item Description
The operating mode of the
meter (normal, alternate, test);
see Chapter 3 of the meter
Mode
technical manual for
information on the operating
mode.
The following items can be
reported:
Status flag
Demand threshold exceeded
since last demand reset

284
TM42-3060

Meter is scheduled to perform


a demand reset at the next
midnight crossing
See the REX technical manual
Warnings
for a list of warnings.
The following items can be
reported:
ROM checksum error
Power fail data save error
Errors
General configuration error
Table CRC error
Improper meter engine
operation error

Security tab
The Security tab displays the following information, which can be
useful in determining if there has been any unusual activity that may
indicate tampering with the meter:

Item Description
Indicates the number of invalid
Invalid passwords password attempts over the meter's
optical port.
The total number of demand resets
Total number of resets
(regardless of method).
The total number of all power failures
Number of power outages
at the meter.

Time tab
The Time tab identifies the date and time of the reading.

Item Description
The date and time the reading
Date/Time of reading was captured (based on the PC
clock).
The meter date and time
Meter date/time
(based on the meter clock).
The day of the week based on
Day of week
the meter clock.
Whether or not the meter is in
DST status
Daylight Saving Time.

285
Views and viewsets

The current rate/tier of the


Rate meter at the time of the
reading.
The current season of the
Season meter at the time of the
reading.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.

Item Description
Ke Identifies the factory Ke
Kh Identifies the factory Kh

EnergyAxis Options tab


The EnergyAxis Options tab displays the following information about
the meter's EnergyAxis capabilities:
Item Description
Radio firmware version The radio firmware version/revision
Additional manufacturer information
Radio Firmware S-Spec
for the radio firmware
The unique communications ID for
LAN ID
the meter
All meters within the same EnergyAxis
Utility ID
network use the same utility ID
The LAN ID of the gatekeeper the
Collector ID
meter is registered to.

REX2 METER

General tab

Item Description
Identifies the meter
manufacture. EE represents
Manufacturer
Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.
The style number of the meter
at the time of manufacture.
Original style number This style number will not
reflect any hardware or Alpha
Key changes made to the

286
TM42-3060

device after it was


manufactured.
Identifies how the reading was
Reading reason obtained (for example: manual
= using an optical probe)
Identifies the hardware version
Hardware version
and revision of the meter.
Identifies the firmware version
Firmware version
and revision.
Additional manufacturer
Firmware S-Spec information that identifies the
meter family.
Amount of memory (in KB)
EEPROM size
available for use by the meter.
Displays comments entered by
Reader notes the reader during the execution
of the reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.

Item Description
Typically, this will be the Meter
ID. The label is defined in Site
ID #2 ID Labels, and the value is
written to the meter when it is
programmed.
Typically, this will be the
Account. The label is defined in
ID #1 Site ID Labels, and the value is
written to the meter when it is
programmed.
Manufacturer-configured
Manufacturing order number number identifying the order
information.
Program The program number.
User-defined display items set
Custom display strings 1 and 2
in the Properties component.

287
Views and viewsets

The status of the service


control switch.
Installed: the service control
Service Disconnect Switch
switch is present.
Not Installed: the service
control switch is not present.

Conditions tab
The Conditions tab displays the meter's conditions at the time the
reading was obtained (for example: any events, warnings, or errors
were recorded).

Item Description
The operating mode of the
meter (normal, alternate, test);
see Chapter 3 of the meter
Mode
technical manual for
information on the operating
mode.
The internal meter temperature
Temperature
in degrees Celsius.
See REX2 meter codes for a list
Status flag
of status codes.
See REX2 meter codes for a list
of status codes that can be
Warnings
used to indicate a warning
situation.
See REX2 meter codes for a list
Errors
of error codes.

Security tab
The Security tab displays the following information, which can be
useful in determining if there has been any unusual activity that may
indicate tampering with the meter:

Item Description
Indicates the number of invalid
Invalid passwords password attempts over the
meter's optical port.
The total number of demand
Total number of resets
resets (regardless of method).

288
TM42-3060

The total number of all power


Number of power outages
failures at the meter.
The total length of time for all
Power outage time
power failures.

Time tab
The Time tab identifies the date and time of the reading.

Item Description
The date and time the reading
Date/Time of reading was captured (based on the PC
clock).
The meter date and time
Meter date/time
(based on the meter clock).
The day of the week based on
Day of week
the meter clock.
Whether or not the meter is in
DST status
Daylight Saving Time.
The current rate/tier of the
Rate meter at the time of the
reading.
The current season of the
Season meter at the time of the
reading.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.

Item Description
Ke Identifies the factory Ke
Kh Identifies the factory Kh

EnergyAxis Options tab


The EnergyAxis Options tab displays the following information about
the meter's EnergyAxis capabilities:
Item Description
Radio firmware version The radio firmware version/revision
Additional manufacturer information
Radio Firmware S-Spec
for the radio firmware
The unique communications ID for
LAN ID
the meter

289
Views and viewsets

All meters within the same EnergyAxis


Utility ID
network use the same utility ID
The LAN ID of the gatekeeper the
Collector ID
meter is registered to.

REXUNIVERSAL METER
The REXUniversal meter has 3 computational processors (that is,
microcontrollers).
 The metrology processor: responsible for all electricity metering
calculations, maintains metrology configuration parameters,
maintains data storage in either internal memory or EEPROM,
manages local communications using the optical port interface
 The communications processor: supports multiple remote
communication interfaces (specifically a 900 MHz transceiver to
support communications to an AMI network), option board
interface, and an interface to the ZigBee processor
 The ZigBee processor: responsible for communications to home
area network (HAN) devices
Metercat can display status information for both the metrology
processor and the communications (comms) processor.
If the REXUniversal meter is connected to an EnergyAxis network, the
EnergyAxis Options tab is displayed. If the REXUniversal meter is
connected to the SynergyNet network, the SynergyNet tab is
displayed.

General tab
Item Description
Identifies the meter manufacture. EE
Manufacturer represents Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.
The style number of the meter at the
time of manufacture. This style
Original style number number will not reflect any hardware
or Alpha Key changes made to the
device after it was manufactured.
Indicates the compatible network for
Network
the REXUniversal meter.
Identifies how the reading was
Reading reason obtained (for example: manual =
using an optical probe)
Identifies the hardware version and
Hardware version
revision of the meter.
Identifies the firmware version and
Firmware version
revision.
Additional manufacturer information
Firmware S-Spec
that identifies the meter family.
Amount of memory (in KB) available
EEPROM size
for use by the meter.
Indicates the firmware versions of the
Product versions
communication controllers.

290
TM42-3060

Indicates the firmware versions of any


Additional COMM options additional option boards or
communication controllers.
Displays comments entered by the
Reader notes reader during the execution of the
reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.
Item Description
Typically, this will be the Meter ID. The
label is defined in Site ID Labels, and
ID #2
the value is written to the meter when
it is programmed.
Typically, this will be the Account. The
label is defined in Site ID Labels, and
ID #1
the value is written to the meter when
it is programmed.
Utility-specified identifier configured
in the meter at the time of
manufacture; if no special requests
Utility serial number
were made at the time of
manufacture, this number will also be
the manufacturer serial number.
The program number (specified at the
Program time the Metercat program is
created).
The user ID of the person who wrote
Programmer
the program to the meter.
Indicates whether the meter is
Program function
demand-only meter or a TOU meter.
User-defined display items set in the
Custom display strings 1 and 2
Properties component.
Version of ANSI C12.19 (Utility
C12.19 Rev industry end device data tables)
supported by the meter.
Indicates the status of the service
Service Disconnect Switch
control switch in the meter.

Conditions tab
The Conditions tab displays the conditions at the time the reading
was obtained as well as any events, warnings, or errors that were
recorded.
Item Description
Mode The operating mode of the meter.
The temperature of the meter (in
Temperature
degrees Celsius)
See REXUniversal meter codes for a
Metrology Events list of metrology processor events
that can be recorded by Metercat.

291
Views and viewsets

See REXUniversal meter codes for a


Metrology Warnings list of metrology processor warnings
that can be recorded by Metercat.
See REXUniversal meter codes for a
Metrology Errors list of metrology processor errors that
can be recorded by Metercat.
See REXUniversal meter codes for a
list of communications processor
Comms Warnings
warnings that can be recorded by
Metercat.
See REXUniversal meter codes for a
Comms Errors list of metrology processor errors that
can be recorded by Metercat.

Security tab
The Security tab displays the following information, which can be
useful in determining if there has been any unusual activity that may
indicate tampering with the meter.
The REXUniversal meter has three separate ports:
 optical
 remote
 LAN
The metrology processor can use the optical port and remote port;
the communications processor can use all three ports. When a
communication session is initiated, the session must indicate the
target processor, which is responsible for validating the
communication. A failed session will then be counted based only on
the intended target processor. For example:
 Metrology port optical authentication failure count = 1
 Comms port optical authentication failure count = 1
In the above example, there were 2 separate attempts to access the
REXUniversal meter using the optical port. One attempt was targeting
the metrology processor while the other attempt was targeting the
communications processor.
Item Description
The number of communication
attempts that failed because
Authentication failures
the user supplied an incorrect
seed.
The number of functions that
failed because the user had
insufficient privileges (for
Authorization failures
example, a user with read-only
access attempts to perform a
demand reset).

The remaining items apply to the overall meter.


Item Description

292
TM42-3060

The total number of demand resets,


Total number of demand resets
regardless of method.
The time and date of the most recent
Date of last demand reset
demand reset, regardless of method.
The time and date of the most recent
Date of last programming
meter programming.
The time and date of the most recent
Last table write
writing to a meter table.
The number of demand limiting
Demand limits in current window operations in the current demand
limiting lockout period.
The total number of demand limiting
Total number of demand limits
operations.
Indicates if the meter protects
metrological parameters from
unauthorized changes. If the
metrology is protected, then changing
Metrology protected
metrological parameters requires the
program key. If the metrology is not
protected, then the key is not
required to change the parameters.
Typically, the security state should be
listed as idle. The security state may
Comms security state be requested from your Metercat
technical support personnel in
troubleshooting an issue.
The number of power failures that
last less than or equal to the
Number of momentary outages momentary outage time threshold
(defined in the Voltage Monitoring
component).
The number of power failures that
last longer than the momentary
Number of sustained outages
outage threshold time (defined in the
Voltage Monitoring component).
The total length of time of all
Cumulative power outage time
sustained outages.
The total number of service control
Total disconnect operations
switch operations.
Indicates whether or not the meter
has detected magnetic tampering (as
Magnetic tamper detection
defined in the Event Log
Configuration component).
Indicates whether or not the meter
DC detection has detected DC (as defined in the
Event Log Configuration component).

Time tab
The Time tab identifies the date and time of the reading.
Item Description
The date and time the reading was
Date/Time of reading
captured (based on the PC clock).
The meter date and time (based on
Meter date/time
the meter clock).

293
Views and viewsets

The day of the week based on the


Day of week
meter clock.
Whether or not the meter was in a
Holiday
holiday rate/tier.
Whether or not the meter is in
DST status
Daylight Saving Time.
The current rate/tier of the meter at
Rate
the time of the reading.
The current season of the meter at
Season
the time of the reading.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.
Item Description
Ke Identifies the factory Ke
Kh Identifies the factory Kh
Identifies the manufacturer's serial
Serial no.
number
Indicates if the meter has detected
Configuration errors
any configuration errors
Indicates if the meter has detected
CRC errors
any CRC errors

EnergyAxis
The EnergyAxis Options tab displays the following information about
the meter's EnergyAxis network capabilities:
Item Description
The version/revision of the
Communications firmware
communications processor
version
firmware
Additional manufacturer
Communications S-SPEC information for the
communications processor
The unique communications ID
LAN ID for the meter within the utility
ID
All meters within the same
Utility ID EnergyAxis network use the
same utility ID
The LAN ID of the gatekeeper
Gatekeeper ID
that the meter is registered to

SynergyNet
The SynergyNet tab displays the following information about the
meter's IPv6 network capabilities:
Item Description
The network date and time as
Network time of when the reading was
captured

294
TM42-3060

AP title The AP title of the meter


The MAC address of the meter;
MAC address
set at the time of manufacture
The MAC layer status; the
MAC status status will be Unjoined,
Joining, or Joined
If the MAC status is
MAC join priority Joining or Joined, the hop
count from the root
If the MAC status is
Joining or Joined, the ID
MAC PAN ID
of the Personal Area
Network
If the MAC status is
Joining or Joined, the
MAC short address short MAC address
received during the
process of joining
The RPL joined status;
Network status - Joined the status will be Yes or
No
The status of the meter
acting as a network
Network status - Router
router and is forwarding
messages
The status of the meter
Network status - Accepting
messages
accepting messages that
are addressed to it
If RPL-joined, the current
Destination Advertisement
Current DTSN Trigger Sequence Number, set
by the node and used to
maintain downward roots
If RPL-joined, the global IPv6
address of the meter
Global IPv6 address
Note: this address will change
if the meter switches routers
If RPL-joined, the IPv6 address
and ID of the edge router
DODAG ID
exposed toward the RPL
network
If RPL-joined, the rank of the
meter's position relative to
other meters with respect to
Current rank the DODAG root (router). The
higher the rank, the further
down the path to the DODAG
root.
Should be identical to the
Current advertised rank current rank. The advertised
rank may be different during

295
Views and viewsets

parent transitions, when the


device cannot confirm
connectivity to the router, or
for battery powered devices.
A unique identifier within a
RPL instance ID
network
The version associated with
DODAG version
the RPL DODAG ID
The number of neighboring
RPL neighbors number
meters seen by a meter
The global IPv6 address
Preferred parent IPv6 address of the preferred parent
node
The rank of the parent
toward the edge router.
Preferred parent rank This will be a lower
number than the meter's
current rank.
The global IPv6 address
of the backup parent (if
there is one); if there is
Backup parent IPv6 address
no backup parent, then
the address is displayed
as 0:0:0:0:0:0:0:0
If there is a backup
Backup parent rank parent, the rank of the
backup parent
If any errors are displayed,
Errors contact your Elster support
representative

IP AXISLINK DEVICES

General tab
Item Description
Identifies the meter manufacture. EE
Manufacturer represents Elster Solutions (formerly,
Elster Electricity).
Model Identifies the basic meter type.
The style number of the meter at the
time of manufacture. This style
Original style number number will not reflect any hardware
or Alpha Key changes made to the
device after it was manufactured.
Identifies how the reading was
Reading reason obtained (for example: manual =
using an optical probe)
Identifies the hardware version and
Hardware version
revision of the meter.
Identifies the firmware version and
Firmware version
revision.

296
TM42-3060

Additional manufacturer information


Firmware S-Spec
that identifies the meter family.
Indicates the firmware versions of any
Option boards
installed option boards.
Indicates the status of options
available for the IP AxisLink device:

Options
Enabled: the functionality available
Disabled: this function is not available

Displays comments entered by the


Reader notes reader during the execution of the
reading task (if any)

Identification tab
The Identification tab displays the meter serial number, account
number, program ID, and other such information.

Item Description
Typically, this will be the Meter
ID. The label is defined in Site
ID #2 ID Labels, and the value is
written to the device when it is
programmed.
Typically, this will be the
Account. The label is defined in
ID #1 Site ID Labels, and the value is
written to the device when it is
programmed.
Utility-specified identifier
configured in the device at the
time of manufacture; if no
Utility serial number special requests were made at
the time of manufacture, this
number will also be the
manufacturer serial number.
The program number (specified
Program at the time the Metercat
program is created).
The user ID of the person who
Programmer wrote the program to the
device.
Indicates whether or not the
Calendar loaded
device has a calendar.

297
Views and viewsets

Version of ANSI C12.19 (Utility


industry end device data
C12.19 Rev
tables) supported by the
device.

Conditions tab
The Conditions tab displays the device's conditions at the time the
reading was obtained (for example: any events, warnings, or errors
were recorded).
Item Description
See IP AxisLink device codes for a list
Events of events that can be recorded by
Metercat.
See IP AxisLink device codes for a list
Warnings of warnings that can be recorded by
Metercat.
See IP AxisLink device codes for a list
Errors of errors that can be recorded by
Metercat.
Metercat reports the communication
status of the following:

Wireless WAN
LAN module
Local interface
Local DNP3.0 slave
Serial DA device
Tunnel manager
C12.22 slave
Web server
Edge DHCP srever
Communication status SNTP client

For each item, the status can be one


of the following:

Shutdown
Initializing
Task starting
Running
Disabled
Faulted
Shutting down

If future replacements are


programmed, Metercat displays the
Pending replacement
module to be replaced and its
effective date.

Security tab

298
TM42-3060

The Security tab displays the following information, which can be


useful in determining if there has been any unusual activity that may
indicate tampering with the meter:

Item Description
For each device, Metercat
reports the total number of
Host and Edge LAN devices packets sent, the number of
packets received, and the
packets lost.
The date and time of the most
Last outage start
recent start of a power failure.
The date and time of the most
Last outage end
recent power restoration.
The time and date of the most
Date of last programming
recent device programming.

Time tab
The Time tab identifies the date and time of the reading.
Item Description
The date and time the reading was
Date/Time of reading
captured (based on the PC clock).
The device date and time (based on
Device date/time
the device clock).
The day of the week based on the
Day of week
meter clock.
Whether or not the meter was in a
Holiday
holiday rate/tier.
Whether or not the meter is in
DST status
Daylight Saving Time.
The current rate/tier of the meter at
Rate
the time of the reading.

Factory codes tab


The Factory Codes tab identifies the factory defaults and
configuration stored in the meter. The factory codes cannot be
edited.
Item Description
Identifies the manufacturer's serial
Serial no.
number
Indicates if the meter has detected
Configuration errors
any configuration errors
Indicates if the meter has detected
CRC errors
any CRC errors

SYNERGYNET NOTIFICATION

299
Views and viewsets

The notification configuration parameters for REXUniversal meters


are programmed using Connexo NetSense. Using Metercat, you can
read the configuration parameters using the SynergyNet Notification
view.
If the meter does not support the SynergyNet connection, Metercat
will display "No data available." If the meter does support the
SynergyNet configuration, Metercat will display the following:
Item Description
Indicates the status of the IPv6 push
Enabled
notification
Server AP title Displays information about the server
Server IP address receiving the IPv6 push notification
Server port messages.

The meter can be support up to 20 configuration entries. For each


entry programmed into the meter, Metercat will display the following:
Item Description
Indicates what kind of data is
being communicated. The
available data types are as
follows:

 Register data
 Demand reset data
 Season change data
 Self read data
 Load profiling (interval data
set 1)
 Instrumentation profiling
Data type (interval data set 2)
 Metrology event log
(periodic trigger)
 COMMS event log (periodic
trigger)
 Metrology high priority
events (event trigger)
 COMMS high priority
events (event trigger)
 Outage/restoration
 Present register data
 Push statistics
 Gas/water
Indicates which of the triggers
is being used:

 Periodic: pushes the


Publishing trigger message on a regular basis
(as set by the seconds past
midnight & period settings)
 Event: pushes the message
if the event occurs in the

300
TM42-3060

meter (for example,


demand reset)
When the publishing trigger is
set to periodic, this parameter
Start time offset (seconds past indicates how many seconds
midnight) after midnight the meter will
wait before pushing the first
message.
When the publishing trigger is
set to periodic, this parameter
indicates how many seconds
after the first message before
publishing additional
Period (seconds)
messages.
If the start time offset is set to
0 and the period is set to 0,
then the message is published
daily at midnight.
If the publishing trigger is set
to event, this parameter
indicates how many seconds
the meter will wait before
resending the message. The
Retry timeout (seconds)
meter will attempt to resend a
message until it receives an
acknowledgement or it
reaches the maximum number
of retry attempts.
Indicates the priority level of
the message. The higher the
Priority
number, the greater the
priority.
Indicates the maximum length
of time (in seconds) the meter
will delay before sending a
Randomization factor
message (including retries).
(seconds)
The actual time is a
randomized time up to this
parameter.
Indicates whether or not the
message includes status
Include status
information so the head-end
system can validate the data.
If the push trigger is event, the
meter should require an
acknowledgement (ACK) for
the message. If an ACK is not
ACK required
received, then the meter will
retry the message until it is
successful or when the
number of retries expires.
The meter stores the
communications statistics for
Statistics
each configuration entry since
the last power restoration or

301
Views and viewsets

configuration change of an
entry.
The date and time the
Last sent
message was last sent.
The data and time the meter
Last ACK timeout received an ACK for the
message.
The number of times a
message reached the
Number of failures maximum number of retries
because the message never
received an ACK.
The number of retries the
message has remaining to
Retries left
receive an ACK or it will
counted as a failure.

TEMPERATURE MONITORING VIEW


Beginning with REX2 meter firmware version 4.5, the meter can
monitor the internal temperature and set status flags based on the
high temperature thresholds. The temperature monitoring view
displays the high temperature (in degrees Celsius) thresholds
configured in the REX2 meter. The REX2 meter supports two
temperature thresholds:
 warning threshold: the temperature at which the meter will set
the warning temperature threshold exceeded status flag (see
REX2 meter codes)
 service disconnect threshold: the temperature at which the
meter will set the service disconnect temperature threshold
exceeded status flag and will open the service control switch
(see REX2 meter codes)
You can clear the temperature related status flags by using the Clear
Status Flags task or the Clear Temperature Status Flags task.

302
Reports and stored
readings

Reports
File > New > Report
Metercat supports the creation of HTML-based reports. Many reports
are created automatically when Metercat completes an operation,
such as the following:
 Function completion report
 Program completion report
 Import completion report
These reports will indicate the status of the operation (such as
whether it succeeded or failed) as well as additional information
(such as which components were changed, what values in the meter
affected, or what caused the operation to fail).
Other views can be created manually, such as the following:
 Viewset report: generates a report that contains the load
profiling and/or instrumentation data. You create the report
while the viewset is open by selecting File > New > Report.
Metercat will present different options for you to select as to
what information the report will contain.
 Program report: after you have created a program or imported a
program, you can generate the detailed information contained in
the program. You can create the report while viewing a program
in the Program Editor and selecting File > New > Report.
 Component report: after you have created a component, you can
generate the detailed information contained in the component.
You create the report while viewing a component in the
Component Editor and selecting File > New > Report.

While viewing the report, you can save it or print it by right-clicking


and selecting the desired operation from the menu. You can open a
saved report from within Metercat or from any web browser.

Stored Readings Management


Tools > Stored Readings Management

303
Reports and stored readings

Note: You must have sufficient group privileges to manage


stored readings.
Metercat allows you to selectively store billing readings and
diagnostic readings. The Stored Readings Management dialog box
allows you to open a reading, perform an import/export operation, or
delete a reading.

OPENING STORED READINGS


You can open a stored reading simply by double-clicking the desired
MSR file located on your PC. Metercat will open (a logon may be
required) and display the Stored Readings Management dialog box.
Select the desired viewset and then click Open. Metercat will display
the information based on the defined views.
You can also select Tools > Stored Readings Management to
display the dialog box. Use the Viewset to select the desired viewset.
When opening the reading, Metercat will display the information
based on the defined views. To help you sort and select the display
items, you can drag 'n drop one or more of the column header
buttons to the gray are above the list.

EXPORTING STORED READINGS


Metercat supports a variety of export options. You may export a
stored reading into one of the following file formats:
 Metercat stored reading file: This is used to store readings to
another location so you can import them into another installation
of Metercat
 Profile HHF for MV-90: This is used to convert the file into an MV-
90 software compatible format
 Interval data as ASCII: This is used to create a plain text file of
the load profiling data so you can import it into a spreadsheet
program for further analysis
 Instrumentation profiling set 1/set 2 as ASCII: This is used to
create a plain text file of the instrumentation data (per set) so
you can import it into a spreadsheet program for further analysis

EXPORT AS METERCAT STORED READING


To export a stored reading as a Metercat stored reading file:
From the Stored Readings Management dialog box, select one or
more readings you want to export.
Click Export and select as Metercat Stored Readings File from the
pop up menu. The Export MSR File dialog box will be displayed.
If you select more than one file to export, the dialog box will be
displayed individually for each file you selected.
Navigate to the location where you want to exported files saved to.
You can accept the default name or change it as necessary.
Click Save.

304
TM42-3060

EXPORT AS PROFILE HHF FOR MV-90


REX2 meters beginning with firmware version 4.0 support 2 sets of
interval data with at least 2 channels per set. When exporting REX2
meter files with two sets of interval data, each set is exported to a
separate HHF file. For A1800 ALPHA meters beginning with firmware
version 1.8, the HHF will be saved in the standard file format if the
load profiling data is in engineering units.
You can also create HHF files automatically when performing a Billing
Read task.
To export a stored reading as an HHF:
From the Stored Readings Management dialog box, select one or
more readings you want to export.
Click Export and select as Profile HHF for MV-90 from the pop up
menu. The Export MSR File dialog box will be displayed. If you
select more than one file to export, the dialog box will be
displayed individually for each file you selected.
Navigate to the location where you want to exported files saved to.
You can accept the default name or change it as necessary.
Click Save.

INTERVAL DATA AS ASCII


REX2 meters beginning with firmware version 4.0 support 2 sets of
interval data with at least 2 channels per set. When exporting REX2
meter files with two sets of interval data, each set is exported to a
separate ASCII file.
Where the time in the meter has changed (regardless of method),
missing intervals are exported as zeros and duplicate intervals are
exported by adding the duplicate values together.

Note: All times are exported in standard time (that is, Daylight
Saving Time is not taken into consideration). Times indicate the
time of the end of the interval.
To export a stored reading as an ASCII file:
From the Stored Readings Management dialog box, select one or
more readings you want to export.
Click Export and select as Interval data as ASCII from the pop up
menu. The Interval Data ASCII-Export Options dialog box is
displayed.
Complete the dialog box as necessary and then click Export. It may
take several minutes for the file to convert to ASCII.

Item Description
All IDs: no restrictions to the report

Restrict data by ID Account: restricts the report to only


those readings from the specified site
ID #1 (typically, account ID)

305
Reports and stored readings

Meter ID: restricts the report to only


those readings from the specified site
ID #2 (typically, meter ID)

Select beginning date for meter data


reporting appearing in the file. The
Start date/time range is between 00:00 and 23:59. A
blank date specifies all data prior to
the stop date will be reported.
Select end date for meter data
reporting appearing in the file. The
range is between 00:00 and 23:59. A
blank date specifies all data after to
the start date will be reported.
Stop date/time
Note: 00:00 is the start of the next
day. For example, you use a 1-minute
interval, and you want to capture the
interval from 31-Dec 23:59 to 24:00,
you must then specify 01-Jan 00:00.
Select the formats used within the file
(such as MM/DD/YY; DD/MM/YY, or
Output date format
YY/MM/DD). The default is your PC
date format.
Specify the location and file name for
Output file
the generated file.
Select the structure of the file:

Interval per row: each row contains


complete information for one interval
period.
Day per row: each row contains
Output format information for one complete day for
a single channel of data.
Day per column: each column
contains information for one
complete day for a single channel of
data.

Specifies what units to use for the


output data:

Demand: computed from the meter


pulse data based on the settings
within the meter and the report (unity
or kilo)
Energy: computed from the meter
Output units
pulse data based on the settings
within the meter and the report (unity
or kilo)
Pulses: shows the raw pulses from
the meter (disregards any
transformer factor or external
multipliers)

306
TM42-3060

Pulse data matches pulse data shown


in a reading with the appropriate
pulse divisor applied.
Select the delimiter to separate the
Field delimiter data in the fields in the file. You can
select a comma, a space, or a tab.
Determines whether or not the
transformer factor is applied to the
Use transformer factor
energy or demand values from the A3
ALPHA/A1800 ALPHA meter.
Determines whether or not the
register multiplier is applied to the
Use register multiplier
energy or demand values from the A3
ALPHA/A1800 ALPHA meter.
Determines whether or not the pulse
divisor is applied to the pulse count
value. When this is selected, the
Use pulse divisor
ASCII reports contain the pulse count
scaled by the divisor (as it is stored in
the meter).
Determines whether channel labels
are included in the export file:
Interval per row: a header is added in
the same format as for
instrumentation profiling
Include channel labels Day per row: a channel label is added
after a channel number for each
channel
Day per column: a row with channel
labels is added next to a row with
channel numbers
Determines whether the ASCII report
Include header contains a header that specifies the
type and unit of reported quantity.
Saves the options you have selected
into a parameter file for future re-use.
The options are saved to a text file
Save options with a CFG extension sored in the
\Config folder by default. The CFG file
can be shared with other installations
of Metercat.
Load options Loads previously saved options

INSTRUMENTATION PROFILING SET 1/SET 2 AS ASCII


Where the time in the meter has changed (regardless of method),
missing intervals are exported as zeros and duplicate intervals are
exported by adding the duplicate values together. For quantities
using either average or end, the most recent duplicate interval will be
exported; for quantities using maximum (or minimum) , the duplicate
interval with the maximum (or minimum) will be exported.

Note: All times are exported in standard time (that is, Daylight
Saving Time is not taken into consideration). Times indicate the
time of the end of the interval.
To export a stored reading as an ASCII file:

307
Reports and stored readings

From the Stored Readings Management dialog box, select one or


more readings you want to export.
Click Export and select as Instrumentation profiling set 1/set 2
data as ASCII from the pop up menu. The Instrumentation
Profiling Export Options dialog box is displayed.
Complete the dialog box as necessary and then click Export. It may
take several minutes for the file to convert to ASCII.

Item Description
All IDs: no restrictions to the report

Account: restricts the report to only


those readings from the specified site
Restrict data by ID ID #1 (typically, account ID)
Meter ID: restricts the report to only
those readings from the specified site
ID #2 (typically, meter ID)

Select beginning date for meter data


reporting appearing in the file. The
Start date/time range is between 00:00 and 23:59. A
blank date specifies all data prior to
the stop date will be reported.
Select end date for meter data
reporting appearing in the file. The
range is between 00:00 and 23:59. A
blank date specifies all data after to
the start date will be reported.
Stop date/time
Note: 00:00 is the start of the next
day. For example, you use a 1-minute
interval, and you want to capture the
interval from 31-Dec 23:59 to 24:00,
you must then specify 01-Jan 00:00.
Select the formats used within the file
(such as MM/DD/YY; DD/MM/YY, or
Output date format
YY/MM/DD). The default is your PC
date format.
Specify the location and file name for
Output file
the generated file.
Select the structure of the file:

Interval per row: each row contains


Output format
complete information for one interval
period.

Select the delimiter to separate the


Field delimiter data in the fields in the file. You can
select a comma, a space, or a tab.
Used to specify the identifier used in
the export file, either site ID #1
Output ID
(typically Account ID) or site ID #2
(typically meter ID).

308
TM42-3060

Metercat multiplies the


instrumentation data by the
Convert to primary (as applicable) appropriate CT or VT value depending
on the unit of measure before
exporting the data.
Saves the options you have selected
into a parameter file for future re-use.
The options are saved to a text file
Save options with a CFG extension sored in the
\Config folder by default. The CFG file
can be shared with other installations
of Metercat.
Load options Loads previously saved options.

IMPORTING STORED READINGS


You can import one or more Metercat stored readings using the
Stored Readings Management dialog box.
1 Click Import. The Select Metercat Stored Readings to import
dialog box is displayed.
2 Navigate to the location of the reading files you want to import.
You can select one or more reading files at the same time.
3 Click Open. Metercat imports the selected files.
Newly imported stored readings appear in bold temporarily until you
close the Stored Readings Management dialog box.

DELETE A STORED READING


From the Stored Readings Management dialog box, select the stored
reading you want to delete and then click Delete. Metercat will
prompt to confirm the deletion.

309
Configuring Metercat

Update network storage


Tools > Update Network Storage
In Metercat releases prior to 3.2, the administrators group had the
privilege of executing this command. After Metercat 3.2, any user
with Export Meter Programs privilege has access to this command.
When this command is selected, Metercat will update the master
programs stored on the network (as specified in System
configuration) based on the programs contained in this installation of
Metercat.
When the command is completed, Metercat will display a completion
report, which will indicate the status of the command (such as the
export was successful or if the network program was already up-to-
date).

Update programs from network storage


Tools > Update Programs from Network Storage
In Metercat releases prior to 3.2, the administrators group had the
privilege of executing this command. After Metercat 3.2, any user
with Import Meter Programs privilege has access to this command.
When this command is selected, Metercat updates the local
Metercat program files based on the network location (defined in
System configuration). After the files are updated, Metercat will
generate a report indicating the status of the command (whether it
succeeded or failed).

Server Synchronization Options


Note: You must have the Allow server synchronization privilege to
administer and perform server synchronization.

ABOUT COMMUNICATIONS ENCRYPTION


C12.22 WAN communication packet is encrypted using a WAN
encryption key (or WAN key) which must be known by both the client
(for example, Metercat, the EnergyAxis Management System) and the
endpoint (for example, a A3 ALPHA meter with a W-WIC option
board). Similarly, a LAN communication packet is encrypted using a
LAN encryption key (or LAN key), which must also be shared between

311
Configuring Metercat

devices communicating over the LAN (for example, an EnergyAxis


gatekeeper and EA-enabled meters).
Each meter has a unique LAN key or WAN key. These unique keys are
generated using the following strings:
 a utility specific WAN seed or LAN seed that is common to all
meters with the same utility ID
 the meter's manufacturing serial number (which is meter
specific)
WAN keys are generated internally by the client and by the meter
and, to ensure security, they keys are never exchanged.
When Elster manufactures C12.22-enabled devices, a factory WAN
seed and/or a factory LAN seed is configured. The combination of
factory WAN seed and the device serial number creates the factory
WAN key. The combination of factory LAN seed and the device serial
number creates the factory LAN key. To change the WAN (or LAN) key
in a population of meters, the server sends new WAN (or LAN) seeds
to all meters that share the same utility ID. As a result, changing the
seed in a meter results in a changed key.
Occasionally, a utility may lose the seed. The only way to
communicate with a device is to use Metercat to reset the meter's
WAN (or LAN) seed back to the factory value (see Activate C12.22
WAN Factory Key and Activate LAN Factory Key). To ensure that
Metercat can communicate with the ANSI C12.22 devices, you must
synchronize Metercat with the server. Synchronization downloads the
seed data to Metercat.
Servers with SOAP-compliant Web Services interface allows for
clients (Metercat, for example) to retrieve WAN seed data stored in
the server. The downloaded WAN seed data consists of the following:
 a list detailing every active WAN seed value, WAN seed ID, utility
ID set
 For each WAN seed set, a list of meters that use the set in terms
of ANSI C12.22 AP Title, IP address, etc.
The WAN seed value is needed by a client to communicate with ANSI
C12.22-capable meters using Ciphertext with Authentication.
Communication between the client and the server occurs using a
secure encryption channel.
When Metercat communicates with the server, two layers of security
are used:
 Authentication using standard certificate verification and
exchange of an established session key. At the Web Services
level, the server must authorize the client. The client includes the
authorization credentials (user name/password) in the Web
Services request. The server then verifies the credentials, and if
valid, grants the client access to the Web Services interface for
retrieving WAN seeds.

312
TM42-3060

 Secure communications proceeds and all data (that is, the Web
Services request and response) are encrypted using the session
key. Metercat stores the WAN seeds in an encrypted database.
Before Metercat can be synchronized, an administrator must perform
the following actions:
 download a certificate from the server
 setting synchronization options in Metercat

DOWNLOADING A CERTIFICATE FROM THE SERVER


Contact the server administrator for information on obtaining the SSL
certificate from the server. Be sure to note the location of the
certificate so you can point to the certificate later.

SETTING THE SYNCHRONIZATION OPTIONS IN METERCAT


Metercat can support synchronization with one or more servers. You
can separately synchronize each server and access the related
meters independently.
To configure Metercat to synchronize with a server:
1 Select Tools > Server Synchronization > Edit Options. The
Server Synchronization Options dialog box is displayed.
2 If necessary, click Add to add a new server.
3 Complete the server information:
Item Description
Type the name of the server. This will
be the name of the server you will see
when requesting a synchronization.
Once you complete the form for a
Server name server and click OK (or click Add to
create a new server), you cannot
change the name. The server
information must be deleted and then
re-created to change the name.
Type the address to reach the server.
You can specify a domain name or IP
address. Be sure to indicate protocol
(for example: https://) and port
Server address (name or IP)
number (for example:
192.168.1.1:8590).
Note: the IP address in the example is
for illustrative purposes only.
The user name to be used to connect
to the server. Contact the server
Server user account
administrator if assistance is
required.
The password required to connect to
the server. Contact the server
Server password
administrator if assistance is
required.

313
Configuring Metercat

Click Load/Reload Certificate and


Server SSL certificate navigate to the location of the stored
SSL certificate.
If you are connecting to an EnergyAxis
Management Server (EA_MS), you
should leave this box unchecked. If
OEM Server
you are connecting to a different
head-end system that is not EA_MS,
you should check this box.
If this option is checked, Metercat will
prompt the user to synchronize with
Prompt for synchronization at system the server each time Metercat starts.
startup If this option is left unchecked, then
the user must manually initiate a
server synchronization.

4 Repeat steps 2 and 3 for each server you want to add.

You can also edit the server information (except the name) or delete
the server information entirely using the Server Synchronization
Options dialog box.

SYNCHRONIZING WITH THE SERVER


To synchronize Metercat with a server, select Server
Synchronization and then select the name of the server from the
cascading menu. Synchronization can take several minutes
depending on the number of meters and devices handled by the
server.
For each meter/device imported, Metercat imports the following:
 communication information into the Phone Book
 passwords and seed sets (see Meter Passwords Management)

See About reading devices for information on the various methods to


connect to meters and devices.

Meter Passwords Management


Tools > Meter Passwords Management
To manage passwords, you must have the Manage Meter Passwords
privilege.

Note: The tabs available to you depend on the meter families


supported by your installation of Metercat. For example, if the
REXUniversal meter family is not supported in your installation of
Metercat, you will not see the REXUniversal tab.
Password management requires careful planning and careful
handling. For example, if you are changing passwords, do not create
a new password set. Instead, edit an existing set. When attempting
to connect with a meter, be sure the history depth is sufficient so
that Metercat can attempt to communicate with a meter using

314
TM42-3060

previous valid passwords. See "About password sets" for more


information on password levels and password history.
While the REXUniversal uses seeds rather than passwords, the
management of seed sets is the same as management of
passwords, otherwise, connection to the meter may be lost.

ABOUT THE METER PASSWORDS MANAGEMENT DIALOG


BOX
For specific information about each supported password or seed
type, see the sections below in this topic.
Dialog box button Description
When clicked, Metercat will create a
New
new password set or seed set.
When clicked, Metercat will delete the
password set or seed set from the
Delete
dialog box (see About password sets
below for more information).
When clicked, Metercat will apply the
Apply changes made to the dialog box
without closing it.
When clicked, Metercat will display
History the revision history of the selected
password set or seed set.

To edit a name of a password set or seed set, or to edit the password


or seed value, click in the desired text box and type as appropriate.

Note: Password retry options are described in the "About


password sets" in this topic.

ABOUT PASSWORD SETS


A password set consists of the passwords required for each level
(typically, an unrestricted password, a billing read password, and a
read-only password). The Meter Passwords Management dialog box
allows you to determine the passwords for each level.
When you create or change a password, a new record is added to the
Metercat database. This record becomes part of the password
history and includes the date/time stamp and the logon name of the
user that created or changed the password set. For security reasons,
Metercat does not delete the password set from the Metercat
database; instead, the password set is removed from the dialog box.

PASSWORD LEVELS
Elster meters and devices typically use three levels of access that
determine how the user supplying the password can interact with the
meter.
 Read only passwords allow only reading of the meter without the
ability to execute a function or write any table or parameter to
the meter.

315
Configuring Metercat

 Billing read passwords allow reading the meter, synchronize the


meter time, and perform a demand reset.
 Unrestricted passwords allow reading the meter and writing
programs and parameters to the meter.
Passwords should be unique for each level within a password set.
Elster meters compare the password being transmitted with its
programmed passwords in sequence from lowest to highest. So, if
the read only password and the unrestricted password are identical,
the meter will only grant read only access because it is the lowest
password level.
The Meter Access Level tab in Group Information determines which
password sets a group has access to as well as what password level
a group can use.

PASSWORD RETRY OPTIONS


If the current password fails to establish communications with a
meter, Metercat has two options to use to attempt to resolve the
situation: password history depth and all zeros.

Password history depth


Password history depth sets the number of previous sets Metercat
will use to attempt to communicate with a meter. If the current
version of the password set fails to establish connection, Metercat
will automatically attempt to use previous versions of the password
set to a level established by the password history depth.
For example, if the Password History Depth is set to 0, Metercat will
only use the current password set. If the history depth is set to 2 (the
default), Metercat will attempt to use the current password set plus
the two previous versions of the set. When setting the depth, be sure
to set it to a level that is sufficient for your password history. This will
help ensure that a user can still interact with a meter that may be
use the password set that is older than what is currently in use.
Metercat does not attempt to use password sets other than the
password set assigned to the user's group (see Group Information).

Try all zeros after other attempts fail


The default Metercat password for devices is twenty zeros. By
checking this box, Metercat will use all zeros to attempt to establish
communication if all other attempts fail.

ANSI C12.19 PASSWORD SETS


Elster's A3 ALPHA and A1800 ALPHA meters support the ANSI
C12.18 security service over the optical port. A separate 20-
character password is used for each password access level. Elster
programs a meter with a password set specified in the customer
program. The characters can be case-sensitive letters, numbers, and
special symbols.

316
TM42-3060

For TCP/IP (C12.21) connections, the meters support the C12.21


authentication service. Per the C12.21 standard, this services uses
an 8-byte encryption key when initiating remote communication. A
separate encryption key exists for each password access level. For
convenience, when configuring a meter, Metercat sets each
encryption key used for each remote access password level equal to
the first 8 characters of the 20-character optical password. To ensure
that the remote keys are unique, Elster recommends that each
password level starts out with 8 unique characters to make them
different from each other.
For TCP/IP connections using C12.22, the communication mode can
be Cleartext with Authentication or Ciphertext with Authentication,
according to the standard. In Cleartext with Authentication, the
authentication is guaranteed by a message authentication code
(MAC) that is appended to every packet and is encrypted with a key
that is derived from the meter password, depending on the desired
access. In Ciphertext with Authentication, the communication is
encrypted with a WAN key that is separate form the meter password
(see Server Synchronization Options for details).
For the IP AxisLink device, the billing level password is only used for
web browser access.

REX METER PASSWORD SETS


Elster's REX and REX2 meters support an 8-digit (numeric only)
password. This password allows you to execute various tasks on a
connected REX/REX2 meter. See Available tasks for a list of tasks
supported by the REX/REX2 meter.

ALPHA PLUS PASSWORD SETS


Metercat manages ALPHA Plus meter passwords for use in Alpha
Keys software. These passwords must be up to 8 digits (numeric
only).
Alpha Keys uses only the unrestricted meter password for
communicating with an ALPHA Plus meter and uses the unrestricted
password for a meter programmed with a non-zero device ID.

REXUNIVERSAL SEED SETS


Instead of passwords, the REXUniversal meter stores three seeds
(one for each authentication level). The seeds are used to derive
corresponding keys which the meter uses in the C12.21
authentication service. This derivation is performed by the meter,
and it is guaranteed to have a unique key for each meter.
The seeds are generated by Metercat and programmed in the meter
using the Change Seed Set task.
When creating a seed set, Metercat will automatically generate a
random value. If desired, users can enter their own values, but
Metercat will require that each seed set have three unique seed
values.

317
Configuring Metercat

See also:
 Change Passwords for meters that use password sets
 Change Seed Set for meters that use seed sets
 Changing ANSI C12.19 passwords for a step-by-step procedure
for changing passwords

Connections
ABOUT READING DEVICES
Reading a device requires the following steps. You must have
sufficient group privileges to execute functions or manage
connections.
 You execute a function that includes a read task (typically, a
Billing Read or a Diagnostic Read). See About functions to learn
more about creating and editing functions and tasks.
 Use a defined connection to the device. See Machine Settings to
learn more about adding or editing connections.
 Establish a connection with the device and perform a function
with a read task included. See Connection bars to learn more
about connecting to a device and reading it.

MACHINE SETTINGS
Tools > Machine Settings
The Machine Settings allows you to view and manage your
computer's connection settings. You can:
 Add a connection
 View and edit a connection
 Delete a connection
 Configure the AlphaPlus software directory
Metercat supports the following connection types:
 optical probe
 modem
 direct connect
 TCP/IP (C12.21)
 TCP/IP (C12.22)
To communicate with a meter using a particular connection method,
you must add a connection specifying the correct settings. See Edit
New Connection for information on adding or editing a connection.
The following table describes the columns and buttons that appear in
the dialog box:
Item Description

318
TM42-3060

Identifies name of the existing


Connection name
connection.
Identifies the type of connection (that
Connection type is, optical probe, modem, direct
connect, etc.)
Identifies the COM port used for the
current connection (note: TCP/IP
Serial port
connections do not require a COM
port).
Opens a pop-up menu where you can
New select a new connection type (see
Edit New Connection).
Opens the currently selected
Edit connection and enables you to make
changes to it.
Deletes the currently selected
Delete
connection and removes it from use.
Must be completed if you want to
launch AlphaPlus software from
Path to AlphaPlus
within Metercat (see About AlphaPlus
software).

EDIT NEW CONNECTION


Tools > Machine Settings > New… (displays popup)
Tools > Machine Settings then edit a defined connection
When creating a connection or editing a defined connection, the
parameters vary depending on the connection type.

Note: Advanced fields are for troubleshooting communications


and should only be set with the help of Elster customer support.
Advanced settings are specific to the channel (probe, modem,
direct connect, etc.) or the protocol.
After you create a connection, Metercat will create a menu entry
under the Connections menu, using the name you create. When you
select the connection from the Connections menu, Metercat will
display a connections bar (see Connection bars).

OPTICAL PROBE CONNECTION


Item Description
The name you want to use for
the connection. For example, if
you are using more than one
type of optical probe, and their
Name
settings are different, you will
want to distinguish one optical
probe connection from the
other.

319
Configuring Metercat

You can use the drop menu to


Port [noteCOM ports are select COM1 to COM4. If you
specified in your PC's Device need a COM port with a higher
Manager. Contact your value, you can type the value
computer support personnel if in. For example, if your optical
you need assistance.] probe is on COM6, you can type
COM6.
Check the boxes as appropriate
for your optical probe. The
Elster UNICOM probe will
communicate using either of
Battery control DTR high the following settings:
Battery control RTS high both DTR high and RTS high
are disabled
either DTR high is checked or
RTS high are checked (but not
both)

For the protocol you are using, complete the tabs as appropriate.
When specifying a connection speed, you should always set the
connection speed to a value higher than or equal to the maximum bit
rate for the device. This will ensure reliable communications.

Item ANSI C12.18 REX REX C12.21


Select a value
from 300 bps
N/A for the N/A for the
Speed (bps) to 14400 bps
REX meter REX meter
from the drop
list.
Default is
Default is
1024. You
192. You can
can specify a
specify a
value in
value in
common
common
increments by
N/A for the increments by
Packet size using the up
REX meter using the up
or down
or down
arrows. You
arrows or type
can also a
a value
value
between 64
between 64
and 192.
and 8192.
Default is 3. Default is 3. Default is 3.
Packet retries You can You can You can
specify a specify a specify a

320
TM42-3060

value (in value (in value (in


single single single
increments) increments) increments)
by using the by using the by using the
arrows or type arrows or type arrows or type
a value a value a value
between 1 between 1 between 1
and 20. and 20. and 20.

MODEM CONNECTION
Item Description
The name you want to use for the
connection. For example, if you are
using more than one type of modem,
Name
and their settings are different, you
will want to distinguish one modem
connection from the other.
You can use the drop menu to select
Port [noteCOM ports are specified in COM1 to COM4. If you need a COM
your PC's Device Manager. Contact port with a higher value, you can type
your computer support personnel if the value in. For example, if your
you need assistance.] modem is on COM6, you can type
COM6.
Type the modem initialization string
for your modem. Metercat uses the
default AT&FE0Q0V1&C1&D2;
Modem init string
however, the documentation supplied
with your modem may specify a
different init string.
Select ATDT if you are using a touch
Dialing string tone line (the default) or ATDP if you
are using a pulse line (rare).
If the modem is to receive calls from
meters, specify how many rings the
modem waits before answering. The
Auto Answer String
default is ATS0=1 for 1 ring. If you
specify ATS0=0, the modem will not
answer meter calls.
Specifies the duration (in seconds) of
allowed inactivity between dialed
digits. if the limit is exceeded, the
Dialing timeout (sec)
dialing will terminate. The range is
between 10 and 255, with a default
of 60.
When specifying a connection speed,
you should always set the connection
speed to a value higher than or equal
Speed (bps) to the maximum bit rate for the
device. This will ensure reliable
communications. Select the
communication rate from a value

321
Configuring Metercat

between 300 bps to 14400 bps from


the drop list. The default is 9600.
Default is 1024. You can specify a
value in common increments by using
Packet size
the up or down arrows. You can also a
value between 64 and 8192.
Default is 3. You can specify a value
(in single increments) by using the
Packet retries
arrows or type a value between 1 and
20.

DIRECT CONNECT CONNECTION


Item Description
The name you want to use for
the connection. For example, if
you are using more than one
Name type of direct connection, and
their settings are different, you
will want to distinguish one
connection from the other.
You can use the drop menu to
Port [noteCOM ports are
select COM1 to COM4. If you
specified in your PC's Device
need a COM port with a higher
Manager. Contact your
value, you can type the value
computer support personnel if
in. For example, for COM6, you
you need assistance.]
can type COM6.
When specifying a connection
speed, you should always set
the connection speed to a
value higher than or equal to
the maximum bit rate for the
Speed (bps) device. This will ensure reliable
communications. Select the
communication rate from a
value between 300 bps to
14400 bps from the drop list.
The default is 9600.
Default is 1024. You can
specify a value in common
Packet size increments by using the up or
down arrows. You can also a
value between 64 and 8192.
Packet retries Default is 3. You can specify a
value (in single increments) by

322
TM42-3060

using the arrows or type a


value between 1 and 20.

TCP/IP

Note: This is for TCP/IP (C12.21). See TCP/IP (C12.22) for


information on creating an ANSI C12.22 connection.

Item Description
The name you want to use for
the connection. For example, if
you are using more than one
Name type of C12.21, and their
settings are different, you will
want to distinguish one C12.21
from the other.
If you are using Metercat to
execute a diagnostic read when
receiving a call over TCP/IP
(see Connection bars), then
Auto Answer Port
specify the port number
Metercat should monitor. The
range is between 0 and 65535
with a default of 1153.
Default is 1024. You can
specify a value in common
Packet size increments by using the up or
down arrows. You can also a
value between 64 and 8192.
Default is 3. You can specify a
value (in single increments) by
Packet retries
using the arrows or type a
value between 1 and 20.

TCP/IP (C12.22)

Note: This is for TCP/IP (C12.22). See TCP/IP for information on


creating an ANSI C12.21 connection.

Item Description
The name you want to use for
the connection. For example, if
Name you are using more than one
type of C12.22, and their
settings are different, you will

323
Configuring Metercat

want to distinguish one C12.22


from the other.
The PPP connection name is
not required if you are
manually launching the PPP
connection. If the PPP
connection name is specified,
Metercat will automatically
launch the PPP connection
PPP connection name when executing a function for
the IP AxisLink device. The PPP
connection will be closed
automatically when the
function is complete. For more
information, see the IP AxisLink
router installation and
administration guide.
This is automatically assigned
Calling AP title (host) by Metercat and should not be
changed.

CONNECTION BARS
After you create a connection (see Machine Settings), Metercat will
create a menu entry under the Connections menu, using the name
specified when the connection was created. When you select the
connection from the Connections menu, Metercat will display a
connections bar. This topic will describe the bars created for the
following connection types:
 optical probe
 modem
 direct connect
 TCP/IP (both C12.21 and C12.22)
Depending on the connections you have created, not all bars may be
available.

OPTICAL PROBE CONNECTION BAR

To communicate with a meter using the optical probe:


1 Connect the PC to the meter using the optical probe.
2 If necessary, display the optical probe connection bar from the
Connections menu.

324
TM42-3060

3 Select the desired function from the function list.


4 If you are performing a reading, select the desired viewset from
the viewset list.
5 Click Go. Metercat will attempt to establish a connection to the
meter and execute the desired function. The status will update in
the connection status area of the bar. Metercat will generate a
completion report indicating the status of the function (whether
it succeeded or failed) as well as additional information.
6 If the function is repeatable, you can click the Repeat button to
repeat the function (see Available tasks for a list of repeatable
functions).

MODEM CONNECTION BAR

To communicate with a meter using a modem:


1 If necessary, display the modem connection bar from the
Connections menu.
2 Select the desired function from the function list.
3 If you are performing a reading, select the desired viewset from
the viewset list.
4 Click Dial to display the dialing list and select the phone book
entry to dial.
5 Click Go. Metercat will attempt to establish a connection to the
meter and execute the desired function. The dialing log text box
shows the connection progress, and the connection status area
of the bar will indicate the overall status of the function.
Metercat will generate a completion report indicating the status
of the function (whether it succeeded or failed) as well as
additional information.
6 If the function is repeatable, you can click the Repeat button to
repeat the function (see Available tasks for a list of repeatable
functions).

Auto answer mode


If you check Answer mode, Metercat will switch to auto answer mode.
When Metercat receives a call-in from a meter, Metercat can be
configured to execute a diagnostic read task. The data received from
the read task will be stored in a Metercat stored reading (.msr) file,
and the file name is logged in the call-in log file. A call-in log file is
created for each answering session (located in the
\Readings\Incoming calls folder). A session starts when Metercat
answers the first call from a meter and ends when the Answer mode
box is unchecked.

Note: If the call-in is a result of a power outage, Metercat will not


execute a function.

325
Configuring Metercat

When Metercat receives a call from a meter, a record is added to the


call-in log (Call-in Log.html). The call-in log records the following
information for each logged call:
 call date and time of the computer receiving the call
 identification data of the meter that originated the call
 the reason for the call (billing, alarm, power restoration, outage)
 any function that was executed as a result of the call
 function completion report
 name of the MSR file generated

DIRECT CONNECT CONNECTION BAR

To communicate with a meter using a direct connection:


1 If necessary, display the direct connect connection bar from the
Connections menu.
2 Select the desired function from the function list.
3 If you are performing a reading, select the desired viewset from
the viewset list.
4 Specify the device ID. For a single meter, you can specify 0
(default). If you are using a multiple meter connection, use the
correct ID for the meter.
5 Click Go. Metercat will attempt to establish a connection to the
meter and execute the desired function. The status will update in
the connection status area of the bar. Metercat will generate a
completion report indicating the status of the function (whether
it succeeded or failed) as well as additional information.
6 If the function is repeatable, you can click the Repeat button to
repeat the function (see Available tasks for a list of repeatable
functions).

Auto answer mode


If you check Answer mode, Metercat will switch to auto answer mode.
When Metercat receives a call-in from a meter, Metercat can be
configured to execute a diagnostic read task. The data received from
the read task will be stored in a Metercat stored reading (.msr) file,
and the file name is logged in the call-in log file. A call-in log file is
created for each answering session (located in the
\Readings\Incoming calls folder). A session starts when Metercat
answers the first call from a meter and ends when the Answer mode
box is unchecked.

Note: If the call-in is a result of a power outage, Metercat will not


execute a function.

326
TM42-3060

When Metercat receives a call from a meter, a record is added to the


call-in log (Call-in Log.html). The call-in log records the following
information for each logged call:
 call date and time of the computer receiving the call
 identification data of the meter that originated the call
 the reason for the call (billing, alarm, power restoration, outage)
 any function that was executed as a result of the call
 function completion report
 name of the MSR file generated

TCP/IP CONNECTION BAR

To communicate with a meter using TCP/IP:


1 If necessary, display the TCP/IP connection bar from the
Connections menu.
2 Select the desired function from the function list.
3 If you are performing a reading, select the desired viewset from
the viewset list.
4 Click Address to display the dialing list and select the phone book
entry to connect to.
5 Click Go. Metercat will attempt to establish a connection to the
meter and execute the desired function. The dialing log text box
shows the connection progress, and the connection status area
of the bar will indicate the overall status of the function.
Metercat will generate a completion report indicating the status
of the function (whether it succeeded or failed) as well as
additional information.
6 If the function is repeatable, you can click the Repeat button to
repeat the function (see Available tasks for a list of repeatable
functions).

Auto answer mode

Note: Auto answer mode is only available on TCP/IP connections


that use C12.21.
If you check Answer mode, Metercat will switch to auto answer mode.
When Metercat receives a call-in from a meter, Metercat can be
configured to execute a diagnostic read task. The data received from
the read task will be stored in a Metercat stored reading (.msr) file,
and the file name is logged in the call-in log file. A call-in log file is
created for each answering session (located in the
\Readings\Incoming calls folder). A session starts when Metercat
answers the first call from a meter and ends when the Answer mode
box is unchecked.

327
Configuring Metercat

Note: If the call-in is a result of a power outage, Metercat will not


execute a function.
When Metercat receives a call from a meter, a record is added to the
call-in log (Call-in Log.html). The call-in log records the following
information for each logged call:
 call date and time of the computer receiving the call
 identification data of the meter that originated the call
 the reason for the call (billing, alarm, power restoration, outage)
 any function that was executed as a result of the call
 function completion report
 name of the MSR file generated

PHONE BOOK
Tools > Phone Book
The Phone Book opens in a dialog box. To help you sort and select
the display items, you can click on a column heading to sort, or drag
'n drop one or more of the column header buttons to the gray are
above the list to group the entries.
The following table describes the various fields and buttons of the
Phone Book dialog box:
Item Description
Creates a phone book entry (referred
New
to as an "installation")
Edit Edits the selected phone book entry
Deletes the selected phone book
Delete
entry
Generates an HTML report of the
Create report
phone book contents

ADDING OR EDITING A PHONE BOOK ENTRY


If you are creating a phone book entry from the start, click the New
button and a pop-up menu is displayed. Select the connection type
and complete the Edit New Installation dialog box as appropriate
for your connection type. The connection types are as follows:
 Modem
 TCP/IP (that is, C12.21)
 TCP/IP C12.22
 UDP C12.22
If you are editing an existing phone book entry, select the entry and
click the Edit button and complete the Edit Installation dialog box
as appropriate for the connection type.

Modem entry
Item Description

328
TM42-3060

Type a name for the phone book entry


Name
(up to 30 characters)
If checked, you must enter the device
Multiple meter installation
ID at communications time.
To permit sorting by group, select a
Group group or type in a new group if
desired. This field is optional.
Phone number Type the phone number to call.
Modem init string These values are taken from the
Dialing string connection type. If you need to make
Dialing timeout (sec) an exception to a specific value for
this entry, check the box and enter
Speed (bps)
the different value.
Default is 1024. You can specify a
value in common increments by using
Packet size
the up or down arrows. You can also a
value between 64 and 8192.
Default is 3. You can specify a value
(in single increments) by using the
Packet retries
arrows or type a value between 1 and
20.

TCP/IP entry
This is for a TCP/IP connection using C12.21. See the TCP/IP
(C12.22) for information on creating a phone book entry for a C12.22
device.
Item Description
Type a name for the phone book entry
Name
(up to 30 characters)
If checked, you must enter the device
Multiple meter installation
ID at communications time.
To permit sorting by group, select a
Group group or type in a new group if
desired. This field is optional.
Type the IP numeric address or IP
IP Address/Name
name.
Type the port number to use for the
IP Port device. The range is between 0 and
65535.
Default is 1024. You can specify a
value in common increments by using
Packet size
the up or down arrows. You can also a
value between 64 and 8192.
Default is 3. You can specify a value
(in single increments) by using the
Packet retries
arrows or type a value between 1 and
20.

TCP/IP (C12.22) entry


This is for a TCP/IP connection using C12.22. See the TCP/IP for
information on creating a phone book entry for a C12.21 device.
Item Description

329
Configuring Metercat

Type a name for the phone book entry


Name
(up to 30 characters)
To permit sorting by group, select a
Group group or type in a new group if
desired. This field is optional.
Type the IP numeric address or IP
IP Address/Name
name.
Type the port number to use for the
IP Port device. The range is between 0 and
65535.
If displayed, you can use the drop list
to change the connection's security
mode from Cleartext with
Security mode
authentication to Ciphertext with
authentication. See About security
mode for more information.
Type the AP title for the meter or
device. The meter AP title is
Called AP title (meter)
contained in the activation file sent by
Elster when the meter is shipped.

If you are configuring to connect to an A3 ALPHA meter with W-WIC,


you must complete the Advanced section of the entry.
If necessary, click on the bottom Advanced button (that is, the
Advanced button in the C12.22 panel).
Press the [Insert] key, and from the Parameter name drop list, select
Response timeout.
In the Parameter value, type 180.
Press the [Insert] key, and from the Parameter name drop list, select
SessionIdleTimeout.
In the Parameter value, type 180.
Click OK.

UDP C12.22 entry


This is for a SynergyNet IPv6 connection.
Item Description
Type a name for the phone
Name book entry (up to 30
characters)
To permit sorting by group,
select a group or type in a new
Group
group if desired. This field is
optional.
Type the IP numeric address or
IP Address/Name
IP name.
Type the port number to use
IP Port for the device. The range is
between 0 and 65535.
Type the AP title for the meter
Called AP title (meter) or device. The meter AP title is
contained in the activation file

330
TM42-3060

sent by Elster when the meter


is shipped.

System Preferences
Tools > System Preferences

Note: By default, System Preferences is included at the time


Metercat is installed. Depending on how the administrator
installed Metercat and your user privileges, you may not have
access to this command.
Using System Preferences, you can set the following options:
 supported meter types for an installation of Metercat
 site ID labels used to identify values used in reports & by the
computer
 dates for Good Friday, Easter Sunday, and the Monday following
Easter (Gregorian calendar) holidays for the next 20 years
 number and names of seasons
 programming of the KYZ output, Kh values, and meter clock
source
 time difference handling
 location of stored readings

Preference descriptions
METERS SUPPORTED
Tools > System Preferences > Meters Supported tab
When Metercat is installed, the administrator selected the meter
families for this installation. To add meter families, you must modify
your installation of Metercat using the Windows Programs and
Features control panel.
Using the Meters Supported tab, you can select which meter types
are enabled or disabled for your installation of Metercat. For
example, if the administrator selected to install the A1800 ALPHA
meter family, you can use the Meters Supported tab to disable the
A1800 ALPHA meter types D, T, and K (because Elster only supports
the A1800 ALPHA meter type R).

SITE ID LABELS

331
Configuring Metercat

Tools > System Preferences > Site ID Labels tab


You can set labels used to identify values used in reports and used
by the computer. These values are then used during the following:
 setting stored readings options
 configuring the Billing Read task
 configuring the Diagnostic Read task
 configuring the Program task
Additionally, Site ID #2 allows masking of the ID value to restrict
editing to certain allowed characters in the string. This feature is
used by the Program task.
 ID #1 supports up to 20 characters for the label. The default
label is Account:.
 ID #2 supports up to 20 characters for the label, a default value,
and a mask.
o The default label is Meter ID:.
o The default value is 00000000000000000000 (20 zeroes)
o The default mask is YYYYYYYYYYYYYYYYYYYY (20 Ys)

For the mask, use the following to control the allowed characters:
 N to specify non-editable character
 Y to specify an editable character (alphanumeric)
 D to specify a numeric character (0 to 9)

HOLIDAYS
Tools > System Preferences > Holidays tab
You can have Metercat automatically generate dates for Easter
(Gregorian calendar) for the next 20 years each time you create a
new Special Dates component. Metercat can generate dates for
Easter (that is, Easter Sunday), Good Friday (the Friday before Easter
Sunday), and the Monday following Easter (Easter Monday).

DATES AND RATES OPTIONS


Tools > System Preferences > Dates and Rates Options tab
Metercat allows you to specify the number and names of the seasons
used in your installation of Metercat. The settings in this tab are used
in the following components:
 Special Dates component
 Rates component

332
TM42-3060

NUMBER OF SEASONS
The A3 ALPHA meter and A1800 ALPHA meter supports up to 12
seasons. You can specify whether or not to limit the meter to 4
seasons or allow the programmer to specify up to 12 seasons in the
Rates component.

SEASON NAMES
By default, Metercat defines Season 1 to be Winter; Season 2 to be
Spring; Season 3 to be Summer; and Season 4 to be Fall. You can
change the names of any season (1 through 12) by clicking in the
season and typing a new name. The new name must be unique (per
Metercat installation) for each.

MIDNIGHT SWITCHES
By checking the Automatically generate midnight switches for all
Rates components, you can force Metercat to always switch to the
default rate/tier at midnight. The option will take affect on all newly
created Rates components. The default is checked, and this will
cause the meter to always switch to the default rate/tier at every
midnight crossing by generating an entry in the switch times table. If
the option is unchecked, then the meter will not automatically switch
to the default rate/tier at midnight.

PROGRAMMING OPTIONS
Tools > System Preferences > Programming Options
Metercat allows you to control programming options for meter
programs created in this installation of Metercat. The options
supported are as follows:
 specifying the KYZ output method
 specifying the adjusted Kh value
 setting the meter clock source
 controlling the power up display sequence

KYZ OUTPUT
A3 ALPHA meters (beginning with firmware version 3.01) and all
A1800 ALPHA meters support a specified KYZ value instead of a
pulse divisor. it is possible to specify the energy pulse value with a
value between 0.000001 kWh and 100.000000 to represent the
amount of energy per pulse (in kilo units). The KYZ output is
supported in the Relay Options component.
To use the KYZ value method, check the Use KYZ value method box.
If the box is unchecked (default), then this installation of Metercat
will use a KYZ divisor.

333
Configuring Metercat

If you are using the KYZ value method, you can create the values that
appear in the Global KYZ Relay Settings panel in the Relay Options
component. To add a value to the list of options:
1 Click Add. Metercat will add a row to the Choice List for KYZ
Value (kilo units) table.
2 Click in the newly created row, and type a value. For example, to
specify a value of 2 kWh, type 0.002.
3 Press ENTER.
You can also edit a value by clicking in the row and typing a new
value.

ADJUSTED KH VALUES
If you are using adjusted Kh values, check the Use adjusted Kh
values to configure meter constants box to specify the meter's
adjusted Kh.
To add a value to the list of options:
1 Click Add. Metercat will add a row to the Choice List for
Adjusted Kh Value table.
2 Click in the newly created row, and type a value.
3 Press ENTER.
You can also edit a value by clicking in the row and typing a new
value.

METER CLOCK SOURCE


The meter can use the power line frequency (either 50 Hz or 60 Hz)
or the internal crystal oscillator to be the primary time base. If the
line frequency of the isolated power system is considered too
unstable for use as a clock frequency, select internal oscillator. The
default is line frequency.

POWER UP DISPLAY LIST


If the Show One Cycle of Alternate Display List at Power Up is
checked (default), the meter will scroll one time through the alternate
display list upon power up. The alternate display list is configured in
the Metering component. If this option is unchecked, then the meter
will enter the normal display list upon power application.

TIME DIFFERENCE OPTIONS


Tools > System Preferences > Time Difference Options tab
You may configure Metercat so that a time difference test is
performed each time Metercat communicates with a meter during a
billing read or a diagnostic read. This test determines how close the
meter's internal timekeeping matches the clock on the computer
running Metercat.

334
TM42-3060

 No time error checking: Metercat will not perform a time


difference check. This is the default.
 If time difference exceeds (hh:mm): Metercat will perform a
time difference check. You can specify a minimum time that the
meter must be different than the PC clock before Metercat will
adjust the time. A time of 00:00 means that Metercat will always
handle a time error based on the defined criteria.

TIME ADJUSTMENT CRITERIA


You can specify how Metercat will handle a meter time error:
 Never adjust meter time: Metercat will not adjust the meter
time. This is the default.
 Always adjust meter time: Metercat will always adjust the
meter time to match the computer time (see the Change Time
topic for a discussion on how meter's handle time changes).
 Adjust meter time if difference is in range: Metercat will only
adjust the time if the error is in the specified range (in hh:mm)
between 00:00 and 99:59. If the error is outside the specified
range, Metercat will not adjust the time.

STORED READINGS
Tools > System Preferences > Stored Readings
When performing a billing read or a diagnostic read, you can specify
the file name ID to be either the site ID #1 (the default is Account) or
site ID #2 (the default is Meter ID). See Site ID Labels for information
on site IDs. When importing a stored reading, you must select which
ID to use by specifying the option in this Stored Readings tab.
To require Metercat to send a stored reading to the Windows Recycle
Bin, check the box. Otherwise, Metercat will delete the file
permanently.

335
Application notes

A3 ALPHA meter codes


Error codes indicate conditions that may be affecting billing data. It is
not recommended to operate the A3 ALPHA meter for an extended
time when it is displaying an error code.
Warning codes indicate conditions that may be of concern but do not
affect the integrity of billing data.

ERROR CODES
Error codes of the same group are displayed in combination (Er1
001010, for example), indicating that more than one error condition
has been detected. If errors exist in more than one group, the meter
will continually cycle through the different groups. Any problems must
be corrected before normal operation can continue. In some cases,
the meter may need to be reprogrammed or returned to the factory
for repair or replacement.

ER1 000001: CARRYOVER ERROR


This code indicates a failure of a RAM checksum test on data stored
in the meter’s volatile RAM during a power outage. When a loss of
line voltage occurs, the meter’s RAM is maintained by the super
capacitor and an optional battery. If both of these fail, the data
stored in RAM is lost. Billing data is stored in nonvolatile memory and
will still be available. The push buttons and communications ports
will function normally.
The conditions that cause a carryover error will also always cause
loss of time (see “Er3 030000: Clock error” below). A carryover error
affects only the clock on meters that do not use the extended
memory option. If extended memory is used, all load profiling and
instrumentation profiling data (which is stored in extended memory)
would be lost as the result of a carryover area.
The meter battery may need to be replaced, and the error will need to
be reset through Metercat. If the error code is still shown after using
Metercat, the meter must be returned to the factory for repair or
replacement.
Since shipping can take several days, this error will likely be seen on
time-keeping meters shipped without a battery.

Note: This error is automatically disabled on demand-only


meters.

337
Application notes

ER1 000010: CRYSTAL OSCILLATOR ERROR


This codes indicates a problem with the crystal oscillator. The A3
ALPHA meter must be returned to the factory for repair or
replacement.

ER1 000100: TABLE CRC ERROR


This code indicates a possible error in the A3 ALPHA meter’s
programming. This code might appear if a communications
interruption occurs during meter programming. Depending on which
area of the meter is affected, billing data may not be reliably
accumulated while this error condition exists. The push buttons and
optical port will continue to function normally.
Reprogramming the meter with Metercat may correct the problem. If
the error code is displayed after reprogramming, the A3 ALPHA meter
should be returned to the factory for repair or replacement.

ER1 001000: INTERNAL COMMUNICATION ERROR


This code indicates the meter had an internal communication error.
The A3 ALPHA meter must be returned to the factory for repair or
replacement.

ER1 010000: EEPROM ACCESS ERROR


This code indicates the meter had a problem accessing its
nonvolatile EEPROM. The A3 ALPHA meter should be returned to the
factory for repair or replacement.

ER1 100000: GENERAL CONFIGURATION ERROR


This code indicates a problem with the meter’s configuration or
program. The meter can usually be reprogrammed using Metercat to
correct the errors.

ER2 000002: SECURITY CONFIGURATION ERROR


This code indicates an error is present in the meter’s security
configuration. Contact Elster if this error is displayed on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A3 ALPHA
meter’s security protection.

ER2 000020: PASSWORD TABLE CRC ERROR


This code indicates a CRC error is present in the meter’s ANSI
C12.19 password configuration table. Contact Elster if this error is
displayed on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A3 ALPHA
meter’s security protection.

ER2 000200: ENCRYPTION KEY TABLE CRC ERROR

338
TM42-3060

This code indicates a CRC error is present in the meter’s ANSI


C12.19 encryption key configuration table. Encryption keys are used
for secure access to the meter’s data and configuration through the
remote communication port. Contact Elster if this error is displayed
on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A3 ALPHA
meter’s security protection.

ER2 020000: ROM FAIL ERROR


This code indicates an incomplete attempt to flash the meter
firmware. This code will exist on the meter if Elster firmware flash
software did not complete the upgrade process. All meter
functionality is halted until this error is resolved. Use Elster firmware
flash software to attempt repair. If this fails, the meter must be
returned to the factory for repair or replacement.

ER2 200000: POWER FAIL DATA SAVE ERROR


This code indicates that the data saved in the nonvolatile EEPROM
during a power fail may be invalid. This error will be displayed when
power is restored to the meter, and a self check has discovered an
error with the EEPROM data. The A3 ALPHA meter must be returned
to the factory for repair or replacement.

ER3 030000: CLOCK ERROR


This code indicates an error with the meter’s time-keeping ability.
The error can be a result of either of the following situations:
 When a carryover error occurs (see “Er1 000001: Carryover
error” abvove), reference to real time is lost. The meter battery
may need to be replaced, and the error will need to be reset
through Metercat. If the error code is still present, the meter
must be returned to the factory for repair or replacement.
 When an A3D meter is upgraded to a timekeeping capable meter
(that is, an A3T, A3K, A3R, or A3Q meter) and the time has not
yet been set. Using Metercat, program the meter time to the
correct time.
TOU features cannot be performed when time is lost. Billing data
accumulated after this error occurs is stored in the default rate.
 For meters with firmware less than 3.0, the default rate is Rate
A.
 For meters with firmware 3.0 or higher, the default rate is
configured by the user using Metercat.
Previously accumulated data is stored in nonvolatile memory and will
still be available.

Note: This error is automatically disabled on demand-only


meters.

339
Application notes

ER3 300000: DISPLAY LOCKED BY WARNING


This code indicates that one or more warning codes (see “Warning
codes” below) has locked the display. The A3 ALPHA meter can be
programmed to lock the display if a warning condition is present. The
Metering component (Display tab) is used to select the individual
warnings that will cause this error code to display. If the condition
causing the warning clears, the error code will also clear.

WARNING CODES
Warning codes of the same group are displayed in combination (for
example, F2 202000), indicating that one or more warning
conditions are present. If warnings exist in more than one group, the
meter displays each group at the end of the display sequence before
returning to the first item.

F1 000001: LOW BATTERY WARNING


This warning code indicates a low battery voltage or missing battery.
A3 ALPHA meters having a realtime clock require a battery to
maintain date and time over an extended power outage.
The meter should be de-energized and the battery should be
replaced. Once the new battery has been installed and the meter is
energized, the code is automatically cleared.
For meters configured for demand-only operation, this warning code
is automatically disabled.

F1 000010: IMPROPER METER ENGINE OPERATION


WARNING
This code indicates that the meter engine program may be corrupt or
is not executing correctly. This warning condition is typically triggered
when the microcontroller reinitializes the meter engine. An unstable
or noisy electrical environment at the A3 ALPHA meter installation
can interfere with this operation.
If the meter engine is successfully reinitialized, then the warning
code will be automatically cleared from the LCD. If the code
continues to be displayed on the LCD, the A3 ALPHA meter should be
returned to the factory for repair or replacement.

F1 000100: REVERSE ENERGY FLOW WARNING


This warning code indicates that reverse energy flow has been
detected equivalent to twice the Kh in a single demand interval since
the last demand reset. It may be an indication of tampering with the
A3 ALPHA meter installation. If reverse energy flow is expected, then
this warning code can be disabled. If the service being metered is not
expected to return energy to the utility, further investigation is
required. In some cases, it may be necessary to return the A3 ALPHA
meter to the factory for repair or replacement.
The code is cleared by these methods:
 performing a demand reset

340
TM42-3060

 issuing the clear values and status function


See fields 3 & 4 of the A3 ALPHA meter style numbers for a listing of
the Kh by meter form.

F1 010000: POTENTIAL INDICATOR WARNING


This code indicates that one or more of the phase potentials are
missing or below the defined phase indicator threshold. This code
will display at the same time as one or more of the potential
indicators blink.
The code is automatically cleared when the phase potential returns a
value within the programmed thresholds.

F1 100000: DEMAND OVERLOAD WARNING


This code indicates that the demand value exceeded the
programmed overload value since the last demand reset. It is
generally intended to inform a utility when the installation is requiring
more power than the service equipment was originally designed to
handle.
If the demand overload value has been set lower than appropriate
for the installation, the A3 ALPHA meter may be reprogrammed with
a higher threshold value.
The code is cleared by these methods:
 performing a demand reset
 issuing the clear values and status function

F2 000002: SERVICE CURRENT TEST FAILURE WARNING


This code indicates that the most recently performed service current
test has failed. See Service Test component for more information.
The code is cleared by these methods:
 the service current test is performed again and the test does not
fail
 issuing the clear values and status function

F2 000200: DEMAND THRESHOLD EXCEEDED WARNING


This code indicates that the demand has exceeded one of the
programmed demand thresholds. This warning follows the state of
any relay programmed for demand threshold operation. It is set once
the demand threshold has been exceeded and only cleared after one
complete demand interval during which the threshold is not
exceeded.

F2 002000: LINE FREQUENCY WARNING


If a meter is configured to use the line frequency instead of the
crystal oscillator as the time base (see Programming Options), this
code indicates that the line frequency is off by ±5 % of its

341
Application notes

programmed setting. When this condition occurs, the meter switches


timekeeping to the crystal oscillator.
The code will be automatically cleared once the line frequency
returns to within 5 % of the nominal frequency. This warning will
never appear on meters configured for constant timekeeping
operation from the internal crystal.

F2 020000: PQM TEST FAILURE WARNING


This code indicates that one or more PQM tests have detected a
value outside the programmed thresholds. Use the meter system
instrumentation displays or Metercat to gain additional information
on the specific PQM test causing the problem.
The code will be automatically cleared once PQM conditions return to
a value within the programmed thresholds.

F2 200000: END OF CALENDAR WARNING


This code indicates that the meter calendar has expired or is about
to expire. The date at which this code appears is configurable using
the Special Dates component. Write a new calendar to the meter.
The code will be automatically cleared once a new calendar has been
written in the meter.

F4 400000: TEMPERATURE THRESHOLD EXCEEDED


This code indicates that the meter's temperature has exceeded the
programmed temperature value (see the A3 ALPHA meter's "Logs
configuration" in Logs component).
The code will be automatically cleared once the meter's temperature
returns to below the programmed value.

SYSTEM SERVICE ERROR CODES


When SEr is displayed on the LCD, the display quantity is a numeric
code representing a system service error. This indicates there is a
service problem detected by the A3 ALPHA meter. The following
tables identify the service voltage error codes and the service current
error codes.

Error code SEr


Voltage phase
Error condition A B C
Low nominal
1 0 0 0 0 0
voltage on Phase A
Low nominal
0 1 0 0 0 0
voltage on Phase B

342
TM42-3060

Low nominal
0 0 1 0 0 0
voltage on Phase C
High nominal
2 0 0 0 0 0
voltage on Phase A
High nominal
0 2 0 0 0 0
voltage on Phase B
High nominal
0 0 2 0 0 0
voltage on Phase C
Unrecognized
5 5 5 0 0 0
service
Bad phase angle
8 0 0 0 0 0
on Phase A
Bad phase angle
0 8 0 0 0 0
on Phase B
Bad phase angle
0 0 8 0 0 0
on Phase C
Low voltage & bad
phase angle on 9 0 0 0 0 0
Phase A
Low voltage & bad
phase angle on 0 9 0 0 0 0
Phase B
Low voltage & bad
phase angle on 0 0 9 0 0 0
Phase C
High voltage & bad
phase angle on A 0 0 0 0 0
Phase A
High voltage & bad
phase angle on 0 A 0 0 0 0
Phase B
High voltage & bad
phase angle on 0 0 A 0 0 0
Phase C

Error code SEr


Current
phase
Error condition A B C

343
Application notes

Missing Phase A
current
0 0 0 1 0 0
Missing Phase B
current
0 0 0 0 1 0
Missing Phase C
current
0 0 0 0 0 1
Low Phase A current 0 0 0 2 0 0
Low Phase B current 0 0 0 0 2 0
Low Phase C current 0 0 0 0 0 2
Missing and low
current on Phase A
0 0 0 3 0 0
Missing and low
current on Phase B
0 0 0 0 3 0
Missing and low
current on Phase C
0 0 0 0 0 3
Low PF on Phase A 0 0 0 4 0 0
Low PF on Phase B 0 0 0 0 4 0
Low PF on Phase C 0 0 0 0 0 4
Reverse power on
Phase A
0 0 0 5 0 0
Reverse power on
Phase B
0 0 0 0 5 0
Reverse power on
Phase C
0 0 0 0 0 5
Low PF & low current
on Phase A
0 0 0 6 0 0
Low PF & low current
on Phase B
0 0 0 0 6 0
Low PF & low current
on Phase C
0 0 0 0 0 6
Reverse power & low
current on Phase A
0 0 0 7 0 0
Reverse power & low
current on Phase B
0 0 0 0 7 0
Reverse power & low
current on Phase C
0 0 0 0 0 7
Excess current on
Phase A current
0 0 0 8 0 0
Excess current on
Phase B current
0 0 0 0 8 0
Excess current on
Phase C current
0 0 0 0 0 8
Excess current & low
PF on Phase A
0 0 0 C 0 0
Excess current & low
PF on Phase B
0 0 0 0 C 0
Excess current & low
PF on Phase C
0 0 0 0 0 C
Excess current &
reverse power on 0 0 0 d 0 0
Phase A
Excess current &
reverse power on 0 0 0 0 d 0
Phase B

344
TM42-3060

Excess current &


reverse power on 0 0 0 0 0 d
Phase C

EVENTS REPORTED IN METERCAT


The following table details those events that Metercat reports in the
Conditions tab of the Status view.
Event Description
Calendar-initiated demand reset
Calendar demand reset
occurred.
Season change occurred Season change occurred.
Self read occurred Self read occurred.
Pending table activated A pending table was activated.
Time change A time change occurred in the meter.
A demand reset occurred by a manual
Button press demand reset
press of the RESET button.
The event log reached its maximum
Event log wrap value, and the meter will begin
overwriting the oldest entries.
Indicates that load profiling is
Pulse profiling wrap
within 2 days of overflowing.
Indicates that the
corresponding instrumentation
Profile 1/Profile 2 wrap
profiling is within 2 days of
overflowing.
See the description for F2
Demand threshold exceeded 000200 in the "Warning
Codes" section above.
Indicates that the history log
History log wrap has exceeded the maximum
number of entries.
Indicates that the sag log has
Sag log wrap exceeded the maximum
number of entries.
Indicates that the current TOU
Rate override rate is being overridden by the
alternate TOU rate schedule.
Indicates that the PQM log has
PQM log wrap exceeded its maximum number
of entries.
Indicates the meter has been
Button press test mode activation placed into test mode since the
occurred last Clear Status Flags or Clear
Data task occurred.

WARNINGS REPORTED IN METERCAT


The following table explains the warnings that Metercat reports in the
Conditions tab of the Status view. If a warning code is displayed on

345
Application notes

the LCD, see the description of the code in the "Warning Codes"
section above.
Warning Warning code on LCD Description
Low battery F1 000001
Improper meter engine
F1 000010
operation
Reverse energy flow F1 000100
Potential indicator F1 010000
Demand overload F1 100000
Service current test
F2 000002
failure
Line frequency F2 002000
PQM test failure F2 020000
End of calendar F2 200000
Indicates that an item
Bad display item in the display list is
invalid. Contact Elster.
The outage reporting
battery used by the
modem needs to be
Low outage battery
replaced. Replace the
battery and perform a
demand reset.
The ITM3 is expected
Modem not
but the meter can no
communicating with
longer communicate
meter
with it. Contact Elster.
The ITM3 has reported
Outage modem
a checksum error.
configuration
Contact Elster.
The ITM3 has reported
Outage modem internal
a self test error. Contact
test failure
Elster.
Indicates possible
tampering of the meter
because a specified
Possible tamper number of invalid
passwords used to
access the meter has
been used.
Indicates possible
Possible tariff data
corruption of billing
corruption
data.
Indicates the service
voltage test was unable
Service voltage test to find a valid service or
failure the measured service
does not match the
locked service.
For Canadian meters,
program mode was
Write protect override
entered and metrology
changes were possible.

346
TM42-3060

The meter's extended


XMB not
memory is expected but
communicating with
not detected by the
meter
meter.
Indicates that the
Service disconnect meter's internal
switch is opened polyphase service
control switch is open.

ERRORS REPORTED IN METERCAT


The following table explains the errors that Metercat reports in the
Conditions tab of the Status view. See the description of each code in
the "Error Codes" section above.
Error Error code on LCD
Carryover Er1 000001
Crystal oscillator Er1 000010
Table CRC Er1 000100
Interval communication (I2C) Er1 001000
EEPROM access Er1 010000
General configuration Er1 100000
Security configuration Er2 000002
ROM failure Er2 020000
Security CRC Er2 000020
Security CRC Er2 000200
Security configuration Er2 000002
Power fail data save Er2 200000
Clock Er3 030000
Display locked by warning condition Er3 300000

A3 ALPHA meter special display items


The A3 ALPHA meter supports special display items. For example, if
an option board needs to display data, it can use a special display
item to display it on the meter's LCD. The meter supports up to 5
special display items. See Display tab for more information.

A3 ALPHA METER WITH W-WIC SPECIAL DISPLAY ITEMS

WIRELESS STATUS
The A3 ALPHA meter with W-WIC uses special display item 1 to
display the wireless status.

347
Application notes

Item Description
Unique, user-assigned numeric
Quantity identifier identifier for the quantity being
displayed.
The status of the W-WIC radio.
0 = reset
1 = Off
2 = Initialization
3 = RSSI wait
W-WIC status code 4 = Get device ID
5 = Tower registration wait
7 = Over the air service
provisioning (OTASP)
8 = Bearer
9 = Connected
The RSSI value (which is
preceded by r) may vary
between 0 and 31, with 31
indicating the best possible
signal strength. An RSSI value
RSSI signal strength
greater than 10 is considered
adequate for wireless
communication. An RSSI value
of 99 inciates an unknown or
non-detectable signal.

A3 ALPHA meter style numbers


Note: Not all style combinations are valid. Style numbers are
subject to change without notice.
Contact your Elster representative for the most current product
information. Your Elster representative is also able to assist you in
ordering the A3 ALPHA meter.

348
TM42-3060

FIELDS 1 & 2: A3 ALPHA METER (CPS POWER SUPPLY)


All A3 ALPHA meters with the CPS power supply begin with the
characters ZD.

FIELDS 3 & 4: SERVICE, FORM, AND CLASS


The following table shows the commonly available ANSI compatible
configurations for S-base (socket connected) and A-base (bottom
connected) meters according to the type of service being metered.

Type of Test Style


Form Class Elements Kh
service amps number
2-wire, 30 200 1 7.2 ZDA3xxxxxxx
1S single
phase 50 320 1 12 ZDA4xxxxxxx
3-wire, 30 200 1 7.2 ZDC3xxxxxxx
2S single
phase 50 320 1 12 ZDC4xxxxxxx
2- or 3-
wire,
3S
single
2.5 20 1 0.6 ZDA2xxxxxxx
phase
3-wire,
4S single 2.5 20 1 0.6 ZDC2xxxxxxx
phase
3- or 4-
wire
35S
delta,
(note
4-wire
2.5 20 2 1.2 ZD22xxxxxxx
1)
wye;
network
3- or 4-
wire
35A
delta;
(note
4-wire
2.5 20 2 1.2 ZD2Bxxxxxxx
1)
wye;
network
3-wire 30 200 2 14.4 ZD53xxxxxxx
12S delta;
network 50 320 2 24 ZD54xxxxxxx

349
Application notes

3-wire
13A delta; 30 100 2 14.4 ZD2Cxxxxxxx
network
36S
4-wire
(note
wye
2.5 20 2½ 1.8 ZD82xxxxxxx
2)
36A
4-wire
(note
wye
2.5 20 2½ 1.8 ZD8Bxxxxxxx
2)
4-wire
9S
wye; 4-
(note
wire
2.5 20 3 1.8 ZD32xxxxxxx
3)
delta
4-wire
10S
wye; 4-
(note
wire
2.5 20 3 1.8 ZD42xxxxxxx
4)
delta
4-wire
10A
wye; 4-
(note
wire
2.5 20 3 1.8 ZD4Bxxxxxxx
3)
delta
16S
4-wire 30 200 3 21.6 ZD33xxxxxxx
wye; 4-
(note
5)
wire 50 320 3 36 ZD34xxxxxxx
delta
4-wire
16A
wye; 4-
(note
wire
30 100 3 21.6 ZD3Cxxxxxxx
5)
delta

Notes:
1 Form 35S replaces Form 5 circuit applications. Because the
voltage elements share a common point of reference on one
side, the form cannot be used with phase shifting transformers
or totalize separate single phase services.
2 Form 36 replaces Form 6 circuit applications. Because the
voltage elements share a common point of reference on one
side, the form cannot be used with phase shifting transformers.
3 Form 9S replaces Form 8S, and Form 10A replaces Form 8A.
4 Form 10S is actually a Form 9S with jumpers across the three
common (neutral) connections of the voltage circuit. This meter
style provides a means of replacing a Form 10S without requiring
changes to socket wiring. This Form should not be used with
phase shifting transformers.
5 Form 16S replaces Form 14S and 15S while Form 16A replaces
Form 14A and 15A circuit applications.

FIELD 5: MAIN BOARD OPTIONS


All styles listed are 120 V to 480 V
 0 = 64 KB main board memory
 1 = 128 KB main board memory

350
TM42-3060

 4 = 64 KB main board memory, AnyPhase power supply


 5 = 128 KB main board memory, AnyPhase power supply

FIELD 6: RELAY & EXTENDED MEMORY OPTION BOARDS


 0 = None
 1 = 1 × 120 V solid state relay to KYZ blades or KYZ terminal
 2 = 1 × 120 V solid state relay to KYZ relay or cable
 3 = 2 relays to cable
 4 = 4 relays to cable
 6 = 6 relays to cable
 8 = DA I/O option board (2 outputs; 4 inputs)
 9 = DA I/O option board (1 output; 2 inputs)
For use with the A3 ALPHA meter and the AGI RLC interrupter
 B = 1 MB extended memory; 1 relay to KYZ blades or KYZ
terminal
 D = 1 MB extended memory; 2 relays to cable
 E = 1 MB extended memory; 4 relays to cable
 G = 1 MB extended memory; 6 relays to cable

FIELDS 7 & 8: COMMUNICATION OPTIONS


 00 = No communication
 A0 = External modem ready
 E0 = RS-232 option board
 F0 = RS-485 option board
 T1 = RS-232 option board with DNP protocol
 T6 = Ethernet with ANSI C12.21 protocol
 W2 = CDMA Wireless WIC (W-WIC), internal antenna, Verizon
 W3 = CDMA W-WIC, external antenna, Verizon
 P0 = EnergyAxis EA_NIC, internal antenna
 P1 = EnergyAxis EA_NIC, external antenna ready
 P8 = EnergyAxis EA_NIC, internal antenna, outage reporting
 P9 = EnergyAxis EA_NIC, external antenna, outage reporting
 Q4 = EnergyAxis gatekeeper module, RS-232, internal antenna
 Q5 = EnergyAxis gatekeeper module, RS-232, external antenna
ready
 Q6 = EnergyAxis gatekeeper module, Ethernet, internal antenna
 Q7 = EnergyAxis gatekeeper module, Ethernet, external antenna
ready

351
Application notes

 W0 = EnergyAxis gatekeeper module, CDMA W-WIC, internal


antenna, Verizon
 W1 = EnergyAxis gatekeeper module, CDMA W-WIC, external
antenna, Verizon
 W9 = EnergyAxis gatekeeper module, CDMA W-WIC, external
antenna with extender collar, Verizon
 L3 = Aclara TWACS UMT-C-A3 (self contained meters)
 L4 = Aclara TWACS UMT-C-A3 (transformer rated)
 NA = Itron SmartSynch GPRS, internal antenna, AT&T
 NB = Itron SmartSynch GPRS, external antenna, AT&T
 NC = Itron SmartSynch GPRS, internal antenna, Rogers
 ND = Itron SmartSynch GPRS, external antenna, Rogers
 NE = Itron SmartSynch GPRS, internal antenna, T-Mobile
 L7 = Landis+Gyr CellNet Utilinet
 LA = Sensus FlexNet FLXA2D
 LL = Silver Spring Networks NIC 310, internal antenna
 LM = Silver Spring Networks, NIC 310, internal antenna, ZigBee
 LN = Silver Spring Networks, NIC 410, internal antenna
 LP = Silver Spring Networks, NIC 410, internal antenna, ZigBee

FIELD 9: MISCELLANEOUS OPTIONS


 0 = Standard meter cover
 K = Keylock meter cover (noteSee PG42-1039 for more
information.)

FIELDS 10 & 11: METER TYPE


See Meter types for an explanation of the quantities available.
 00 = A3D
 01 = A3DQ
 80 = A3T
 81 = A3TQ
 82 = A3TL
 83 = A3TLQ
 84 = A3TLN
 85 = A3TLNQ
 A0 = A3K

352
TM42-3060

 A1 = A3KQ
 A2 = A3KL
 A3 = A3KLQ
 A4 = A3KLN
 A5 = A3KLNQ
 A6 = A3KA
 A7 = A3KAQ
 A8 = A3KAL
 A9 = A3KALQ
 AA = A3KALN
 AB = A3KALNQ
 L0 = A3R
 L1 = A3RQ
 L2 = A3RC
 L3 = A3RCQ
 L4 = A3RL
 L5 = A3RLQ
 L6 = A3RLC
 L7 = A3RLCQ
 L8 = A3RLN
 L9 = A3RLNQ
 LA = A3RLNC
 LB = A3RLNCQ
 LC = A3RA
 LD = A3RAQ
 LE = A3RAC
 LF = A3RACQ
 LG = A3RAL
 LH = A3RALQ
 LJ = A3RALC
 LK = A3RALCQ
 LL = A3RALN
 LM = A3RALNQ
 LN = A3RALNC
 LP = A3RALNCQ

353
Application notes

 F0 = A3Q
 F1 = A3QQ
 FC = A3QC
 FD = A3QCQ
 F2 = F3QL
 F3 = A3QLQ
 FE = A3QLC
 FF = A3QLCQ
 F4 = A3QLN
 F5 = A3QLNQ
 FG = A3QLNC
 FH = A3QLNCQ
 F6 = A3QA
 F7 = A3QAQ
 FJ = A3QAC
 FK = A3QACQ
 F8 = A3QAL
 F9 = A3QALQ
 FL = A3QALC
 FM = A3QALCQ
 FA = A3QALN
 FB = A3QALNQ
 FN = A3QALNC
 FP = A3QALNCQ

A1800 ALPHA meter codes


Error codes indicate conditions that may be affecting billing data. It is
not recommended to operate the A1800 ALPHA meter for an
extended time when it is displaying an error code.
Warning codes indicate conditions that may be of concern but do not
affect the integrity of billing data.

ERROR CODES
Error codes of the same group are displayed in combination (E1
001010, for example), indicating that more than one error condition
has been detected. If errors exist in more than one group, the meter
will continually cycle through the different groups. Any problems must

354
TM42-3060

be corrected before normal operation can continue. In some cases,


the meter may need to be reprogrammed or returned to the factory
for repair or replacement.

E1 000001: CARRYOVER ERROR


This code indicates a failure of a RAM checksum test on data stored
in the meter’s volatile RAM during a power outage. When a loss of
line voltage occurs, the meter’s RAM is maintained by the super
capacitor and the TOU battery. If both of these fail, the data stored in
RAM is lost. Billing data is stored in nonvolatile EEPROM and will still
be available. The push buttons and communications ports will
function normally.
Since shipping can take several days, this error will likely be seen on
meters shipped without a connected battery.
The meter battery may need to be replaced, and the error will need to
be reset through Metercat. If the error code is still shown after using
Metercat, the meter must be returned to the factory for repair or
replacement.

E1 000010: CRYSTAL OSCILLATOR ERROR


This codes indicates a problem with the crystal oscillator. The A1800
ALPHA meter must be returned to the factory for repair or
replacement.

E1 000100: TABLE CRC ERROR


This code indicates a possible error in the A1800 ALPHA meter’s
programming. This code might appear if a communications
interruption occurs during meter programming. Depending on which
area of the meter is affected, billing data may not be reliably
accumulated while this error condition exists. The push buttons and
optical port will continue to function normally.
Reprogramming the meter with Metercat may correct the problem. If
the error code is displayed after reprogramming, the A1800 ALPHA
meter should be returned to the factory for repair or replacement.

E1 001000: INTERNAL COMMUNICATION ERROR


This code indicates the meter had an internal communication error.
The A1800 ALPHA meter must be returned to the factory for repair or
replacement.

E1 010000: EEPROM ACCESS ERROR


This code indicates the meter had a problem accessing its
nonvolatile EEPROM. The A1800 ALPHA meter should be returned to
the factory for repair or replacement.

E1 100000: GENERAL CONFIGURATION ERROR

355
Application notes

This code indicates a problem with the meter’s configuration or


program. The meter can usually be reprogrammed using Metercat to
correct the errors.

E2 000002: SECURITY CONFIGURATION ERROR


This code indicates an error is present in the meter’s security
configuration. Contact Elster if this error is displayed on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A1800 ALPHA
meter’s security protection.

E2 000020: PASSWORD TABLE CRC ERROR


This code indicates a CRC error is present in the meter’s ANSI
C12.21 password configuration table. Contact Elster if this error is
displayed on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A1800 ALPHA
meter’s security protection.

E2 000200: ENCRYPTION KEY TABLE CRC ERROR


This code indicates a CRC error is present in the meter’s ANSI
C12.19 encryption key configuration table. Encryption keys are used
for secure access to the meter’s data and configuration through the
remote communication port. Contact Elster if this error is displayed
on the LCD.

Note: If this error occurs, the meter is vulnerable to tampering.


Prompt correction of the error will maximize the A1800 ALPHA
meter’s security protection.

E2 020000: ROM FAIL ERROR


This code indicates an incomplete attempt to flash the meter
firmware. This code will exist on the meter if Elster firmware flash
software did not complete the upgrade process. All meter
functionality is halted until this error is resolved. Use Elster firmware
flash software to attempt repair. If this fails, the meter must be
returned to the factory for repair or replacement.

E2 200000: POWER FAIL DATA SAVE ERROR


This code indicates that the data saved in the nonvolatile EEPROM
during a power fail may be invalid. This error will be displayed when
power is restored to the meter, and a self check has discovered an
error with the EEPROM data. The A1800 ALPHA meter must be
returned to the factory for repair or replacement.

E3 030000: CLOCK ERROR


This code indicates an error with the meter’s timekeeping ability.
When a carryover error occurs (see “E1 000001: Carryover error”

356
TM42-3060

above), reference to real time is lost. The meter battery may need to
be replaced, and the error will need to be reset through Metercat. If
the error code is still present, the meter must be returned to the
factory for repair or replacement.
TOU features cannot be performed when time is lost. Previously
accumulated data is stored in nonvolatile EEPROM and will still be
available.

E3 300000: DISPLAY LOCKED BY WARNING


This code indicates that one or more warning codes (see “Warning
codes” below) has locked the display. The A1800 ALPHA meter can
be programmed to lock the display if a warning condition is present.
Metercat is used to select the individual warnings that will cause this
error code to display. If the condition causing the warning clears, the
error code will also clear.

WARNING CODES
Warning codes of the same group are displayed in combination (for
example, W2 202000), indicating that one or more warning
conditions are present. If warnings exist in more than one group, the
meter displays each group at the end of the display sequence before
returning to the first item.

W1 000001: LOW BATTERY WARNING


This warning code indicates a low battery voltage or missing battery.
A1800 ALPHA meters having realtime TOU functionality require a
battery to maintain date and time over an extended power outage.
For timekeeping configurations, the meter should be de-energized
and the battery should be replaced. Once the new battery has been
installed and the meter is energized, the code is automatically
cleared.
In addition, the low battery indicator will display on the LCD.

W1 000010: IMPROPER METER ENGINE OPERATION


WARNING
This code indicates that the meter engine program may be corrupt or
is not executing correctly. This warning condition is typically triggered
when the microcontroller reinitializes the meter engine. An unstable
or noisy electrical environment at the A1800 ALPHA meter
installation can interfere with this operation.
If the meter engine is successfully reinitialized, then the warning
code will be automatically cleared from the LCD. If the code
continues to be displayed on the LCD, the A1800 ALPHA meter
should be returned to the factory for repair or replacement.

W1 000100: REVERSE ENERGY FLOW WARNING


This warning code indicates that reverse energy flow has been
detected equivalent to twice the Kh since the last reset. It may be an

357
Application notes

indication of tampering with the A1800 ALPHA meter installation. If


reverse energy flow is expected, then this warning code can be
disabled in the Metering component (Display subcomponent >
Warning tab). If the service being metered is not expected to return
energy to the utility, further investigation is required. In some cases,
it may be necessary to return the A1800 ALPHA meter to the factory
for repair or replacement.
The code is cleared by these methods:
 performing a demand reset
 issuing the clear data command through Metercat

W1 001000: INTERPOSING RELAY DISCONNECTED


This warning code indicates that the interposing relay is in a
disconnected state.
This code is cleared automatically when the state of the interposing
relay is connected.

W1 010000: POTENTIAL INDICATOR WARNING


This code indicates that one or more of the phase potentials are
missing or below the defined threshold for voltage sag detection. This
code will display at the same time as one or more of the potential
indicators blink.
The code is automatically cleared when the phase potential returns a
value within the programmed thresholds.

W1 100000: DEMAND OVERLOAD WARNING


This code indicates that the demand value exceeded the
programmed overload value. It is generally intended to inform a utility
when the installation is requiring more power than the service
equipment was originally designed to handle.
If the demand overload value has been set lower than appropriate
for the installation, the A1800 ALPHA meter may be reprogrammed
with a higher threshold value.
The code is cleared by these methods:
 performing a demand reset
 issuing the clear data command through Metercat

W2 000002: SERVICE CURRENT TEST FAILURE WARNING


This code indicates that the most recently performed service current
test has failed.
The code is cleared by these methods:
 the service current test is performed again and the test does not
fail
 issuing the clear data command through Metercat

358
TM42-3060

W2 000200: DEMAND THRESHOLD EXCEEDED WARNING


This code indicates that the demand has exceeded one of the
programmed demand thresholds. This warning follows the state of
any relay programmed for demand threshold operation. It is set once
the demand threshold has been exceeded and only cleared after one
complete demand interval during which the threshold is not
exceeded.

W2 002000: LINE FREQUENCY WARNING


If a meter is configured to use the line frequency instead of the
crystal oscillator as the time base, this code indicates that the line
frequency is off by ±5 % of its programmed setting. When this
condition occurs, the meter switches timekeeping to the crystal
oscillator.
The code will be automatically cleared once the line frequency
returns to within 5 % of the nominal frequency. This warning will
never appear on meters configured for constant timekeeping
operation from the internal crystal.

W2 020000: TRUEQ TEST FAILURE WARNING


This code indicates that one or more TRueQ tests have detected a
value outside the programmed thresholds. Use the meter system
instrumentation displays or Metercat to gain additional information
on the specific TRueQ test causing the problem.
The code will be automatically cleared once TRueQ conditions return
to a value within the programmed thresholds.

W2 200000: END OF CALENDAR WARNING


This code indicates that the meter calendar has expired or is about
to expire. The date at which this code appears is configurable using
the Special Dates component. Program a new calendar using
Metercat.
The code is cleared by these methods:
 performing a demand reset
 issuing the clear data command through Metercat
 write a new calendar to the meter

W3 000003: READ WITHOUT POWER BATTERY


DISCHARGED
This code indicates that the Read without Power battery, which is
used only to enable the Read without Power mode during an outage,
failed the meter’s most recent self test. The Read without Power
battery fails if the meter self test detects that the battery’s voltage is
below the minimum threshold or the battery has exceeded its
maximum lifetime usage time. The meter will not enter Read without
Power mode if this warning is displayed. Contact Elster if this warning
appears on the display.

359
Application notes

W3 000030: READ WITHOUT POWER MODE ACTIVE


This code indicates that the meter is operating in the Read without
Power mode. The meter has limited functionality while in this mode.
This code is cleared automatically when the meter exits the Read
without Power mode.

SYSTEM SERVICE TEST ERROR CODES


When SEr is displayed on the LCD, the display quantity is a numeric
code representing a system service error. This indicates there is a
service problem detected by the A1800 ALPHA meter. The following
tables identify the service voltage error codes and the service current
error codes.
Error code SEr
Voltage phase
Error condition L1 L2 L3
Low nominal voltage
1 0 0 0 0 0
on line 1
Low nominal voltage
0 1 0 0 0 0
on line 2
Low nominal voltage
0 0 1 0 0 0
on line 3
High nominal voltage
2 0 0 0 0 0
on line 1
High nominal voltage
0 2 0 0 0 0
on line 2
High nominal voltage
0 0 2 0 0 0
on line 3
Unrecognized service 5 5 5 0 0 0
Bad phase angle on
8 0 0 0 0 0
line 1
Bad phase angle on
0 8 0 0 0 0
line 2
Bad phase angle on
0 0 8 0 0 0
line 3
Low voltage & bad
9 0 0 0 0 0
phase angle on line 1
Low voltage & bad
0 9 0 0 0 0
phase angle on line 2
Low voltage & bad
0 0 9 0 0 0
phase angle on line 3
High voltage & bad
A 0 0 0 0 0
phase angle on line 1
High voltage & bad
0 A 0 0 0 0
phase angle on line 2
High voltage & bad
0 0 A 0 0 0
phase angle on line 3

Error code SEr


Current
phase
Error condition L1 L2 L3
Missing line 1 current 0 0 0 1 0 0

360
TM42-3060

Missing line 2 current 0 0 0 0 1 0


Missing line 3 current 0 0 0 0 0 1
Low line 1 current 0 0 0 2 0 0
Low line 2 current 0 0 0 0 2 0
Low line 3 current 0 0 0 0 0 2
Missing and low
0 0 0 3 0 0
current on line 1
Missing and low
0 0 0 0 3 0
current on line 2
Missing and low
0 0 0 0 0 3
current on line 3
Low PF on line 1 0 0 0 4 0 0
Low PF on line 2 0 0 0 0 4 0
Low PF on line 3 0 0 0 0 0 4
Reverse power on line
0 0 0 5 0 0
1
Reverse power on line
0 0 0 0 5 0
2
Reverse power on line
0 0 0 0 0 5
3
Low PF & low current
0 0 0 6 0 0
on line 1
Low PF & low current
0 0 0 0 6 0
on line 2
Low PF & low current
0 0 0 0 0 6
on line 3
Reverse power & low
0 0 0 7 0 0
current on line 1
Reverse power & low
0 0 0 0 7 0
current on line 2
Reverse power & low
0 0 0 0 0 7
current on line 3
Excess current on line
0 0 0 8 0 0
1 current
Excess current on line
0 0 0 0 8 0
2 current
Excess current on line
0 0 0 0 0 8
3 current
Excess current & low
0 0 0 C 0 0
PF on line 1
Excess current & low
0 0 0 0 C 0
PF on line 2
Excess current & low
0 0 0 0 0 C
PF on line 3
Excess current &
reverse power on line 0 0 0 d 0 0
1
Excess current &
reverse power on line 0 0 0 0 d 0
2
Excess current &
reverse power on line 0 0 0 0 0 d
3

EVENTS REPORTED IN METERCAT

361
Application notes

The following table details those events that Metercat reports in the
Conditions tab of the Status view.
Event Description
Calendar-initiated demand reset
Calendar demand reset
occurred.
Season change occurred Season change occurred.
Self read occurred Self read occurred.
Pending table activated A pending table was activated.
Time change A time change occurred in the meter.
A demand reset occurred by a manual
Button press demand reset
press of the RESET button.
The event log reached its maximum
Event log wrap value, and the meter will begin
overwriting the oldest entries.
Indicates that load profiling is
Pulse profiling wrap
within 2 days of overflowing.
Indicates that the
corresponding instrumentation
Profile 1/Profile 2 wrap
profiling is within 2 days of
overflowing.
See the description for W2
Demand threshold exceeded 000200 in the "Warning
Codes" section above.
Indicates that the history log
History log wrap has exceeded the maximum
number of entries.
Indicates that the sag log has
Sag log wrap exceeded the maximum
number of entries.
Indicates that the current TOU
Rate override rate is being overridden by the
alternate TOU rate schedule.
Indicates that the PQM log has
PQM log wrap exceeded its maximum number
of entries.
Indicates the meter has been
Button press test mode activation placed into test mode since the
occurred last Clear Status Flags or Clear
Data task occurred.

WARNINGS REPORTED IN METERCAT


Warning Warning code on LCD Description
Low battery W1 000001
Improper meter engine
W1 000010
operation
Reverse energy flow W1 000100
Potential indicator W1 010000
Demand overload W1 100000

362
TM42-3060

Service current test


W2 000002
failure
Line frequency W2 002000
PQM test failure W2 020000
End of calendar W2 200000
Indicates that an item
Bad display item in the display list is
invalid. Contact Elster.
The outage reporting
battery used by the
modem needs to be
Low outage battery
replaced. Replace the
battery and perform a
demand reset.
The ITM3 is expected
Modem not
but the meter can no
communicating with
longer communicate
meter
with it. Contact Elster.
The ITM3 has reported
Outage modem
a checksum error.
configuration
Contact Elster.
The ITM3 has reported
Outage modem internal
a self test error. Contact
test failure
Elster.
Indicates possible
tampering of the meter
because a specified
Possible tamper number of invalid
passwords used to
access the meter has
been used.
Indicates possible
Possible tariff data
corruption of billing
corruption
data.
Indicates the service
voltage test was unable
Service voltage test to find a valid service or
failure the measured service
does not match the
locked service.
For meters with
program protection,
Write protect override program protection was
exited and metrology
changes were possible.
The meter's extended
XMB not
memory is expected but
communicating with
not detected by the
meter
meter.
Indicates that the
Service disconnect meter's internal
switch is opened polyphase service
control switch is open.

ERRORS REPORTED IN METERCAT

363
Application notes

The following table explains the errors that Metercat reports in the
Conditions tab of the Status view. See the description of each code in
the "Error Codes" section above.
Error Error code on LCD
Carryover Er1 000001
Crystal oscillator Er1 000010
Table CRC Er1 000100
Interval communication (I2C) Er1 001000
EEPROM access Er1 010000
General configuration Er1 100000
Security configuration Er2 000002
ROM failure Er2 020000
Security CRC Er2 000020
Security CRC Er2 000200
Security configuration Er2 000002
Power fail data save Er2 200000
Clock Er3 030000
Display locked by warning condition Er3 300000

About Alpha Keys


Metercat allows you to open an installed version of Alpha Keys
software using your Metercat logon password. Alpha Keys software is
shipped on the Metercat installation disc.
To start Alpha Keys
1 Connect a Hard Key III with Soft Keys available to your
computer's USB port.
2 Connect a meter to your computer using an optical probe.
3 Select Tools > Launch Alpha Keys. The Alpha Keys main window
is displayed.
4 Click Start.

A3 ALPHA METER
Alpha Keys software and hardware allows A3 ALPHA meters to be
upgraded so they provide additional functionality. Upgrading with
Alpha Keys means that the meter does not have to be returned to the
factory and new meters do not have to be purchased to gain
functionality.
The following table shows the type of upgrades that can be
performed using Alpha Keys:
Current meter type Can be upgraded to
A3T
A3D A3K
A3R
A3K
A3T
A3R
A3K A3R
A3R A3K

364
TM42-3060

The following table lists the additional functionalities that can be


added to the meter using Alpha Keys:

Additional function Can be added to


A3D
A3T
Power quality monitoring (Q suffix) A3Q
A3K
A3R
A3T
A3Q
Load profiling (L suffix)
A3K
A3R
A3Q
Instrumentation profiling (N suffix)
A3R
Transformer and line loss A3Q
compensation (C suffix) A3R
A3Q
Advanced four quadrant metering (A
A3K
suffix)
A3R

A1800 ALPHA METER


Alpha Keys software and hardware allows A1800 ALPHA meters to
be upgraded so they provide additional functionality. Upgrading with
Alpha Keys means that the meter does not have to be returned to the
factory and new meters do not have to be purchased to gain
functionality.
The following features can be added to the meter by using Alpha
Keys:
 load profiling
 instrumentation profiling
 transformer and line loss compensation (noteContact Elster for
availability)
 4-quadrant metering
 DLMS/COSEM protocol support (noteContact Elster for
availability)

See also:
 Meter types

About AlphaPlus software


Tools > Launch AlphaPlus
Elster's original ALPHA, ALPHA Plus, and the AIN ALPHA meters can
be read and programmed using the AlphaPlus software. Metercat
allows you to open an installed version of AlphaPlus software in a
command line window using your Metercat log on.
Before you can start AlphaPlus software:

365
Application notes

 for releases prior to 1.30, you must edit the APLUS.BAT file
located in the \APLUS folder on your computer and edit the
APMENU line to read APMENU %1
 you must set the path to AlphaPlus

To configure the path to Elster's AlphaPlus software:


1 Select Tools > Machine Settings. The Machine Settings dialog
box is displayed.
2 Click Browse. The Select folder with APLUS.BAT dialog box is
displayed.
3 Navigate to the folder location where AlphaPlus is installed (for
example, C:\APLUS\).
4 Select APLUS.BAT and then click Open. You will return to the
Machine Settings dialog box.
5 Click Close.

TROUBLESHOOTING ALPHAPLUS SERIAL PORT


CONFLICTS
AlphaPlus software release 1.3 introduces changes to how the serial
communications port is accessed (Aplus.dll). These changes improve
communication reliability for computers using current versions of
Windows software.
However, not all AlphaPlus support applications have been changed;
therefore, when an application that uses the DOS port access uses a
given port, this port will be locked from use by any application using
the Windows port access (that is, Aplus.dll) and the port will not be
unlocked until the DOS window is closed. Other DOS applications
started in this same DOS window that use DOS port access may be
able to access the port.
The table below shows the different AlphaPlus applications and
which port access method each uses.
Application name Comm port access Notes
Port can be shared with
Metercat, applications using
Aplus.dll, and other Windows
applications. Exception:
Other applications will not be
AlphaPlus 1.30 Windows (Aplus.dll)
able to access the
communication port when
AlphaPlus is displaying the To
Proceed, press ENTER
prompt.
Thresholds and PQ Inspector
use DOS direct port access.
Thresholds 1.30 DOS
Once either of these
applications accesses the

366
TM42-3060

port, the DOS window will


lock the port and only
applications using DOS direct
port access running in the
same window can access the
port. The DOS window must
be closed to release the port.
Port can be shared with
Metercat, applications
using Aplus.dll, and
other Windows
applications. Exception:
Other applications will
not be able to access
the communication port
when AlphaPlus is
displaying the To
Proceed, press ENTER
prompt.
An early version of Loss
Compensation 1.30
Loss Compensation uses the Aplus.dll,
Windows (Aplus.dll)
1.30 however the port
sharing is not consistent
with AlphaPlus or ALPHA
Keys. The port is not
shareable while Loss
Compensation is active,
but it does not require
the user to close the
DOS window to free the
port. An improved
version of Loss
Compensation (dated
01/10/2004) offers
similar port sharing to
AlphaPlus.
Thresholds and PQ
Inspector use DOS
direct port access. Once
either of these
applications accesses
PQ Inspector 1.22 DOS the port, the DOS
window will lock the port
and only applications
using DOS direct port
access running in the
same window can

367
Application notes

access the port. The


DOS window must be
closed to release the
port.

About DLMS passwords


Beginning with meter firmware version 2.0, A1800 ALPHA meters
support DLMS. When a program contains a Remote component that
uses the DLMS protocol, Metercat will prompt for handling Level 1
DLMS password. Metercat will display a runtime dialog box that
allows the user to enter the Level 1 DLMS password. While Metercat
will write the password to the meter, Metercat will not store or
maintain the DLMS password. Users themselves are responsible for
maintaining the password.
The password can be set in a variety of ways:
 At the time of ordering
In this situation, the DLMS password will be written to the meter
at the time of manufacturing.
 If DLMS is being used and no password has ever been
programmed into the meter
In this situation, Metercat will prompt for the initial password to
be stored in the meter using a runtime dialog box. Metercat will
not store or maintain the password. Users themselves are
responsible for maintaining a record of the password.
 Changing an existing DLMS password
In this situation, you must execute a function using the Change
DLMS Password task. Metercat will prompt for a new DLMS
password, which will be written to the meter. Metercat will not
store or maintain the password. Users themselves are
responsible for maintaining a record of the password.

About security mode


The security mode determines how Metercat connects to the C12.22-
enabled device; that is, whether to use cleartext with authentication
or ciphertext with authentication. The security mode depends on the
meter family and how the Phone Book entry is created and
maintained. Phone Book entries can be created manually (see Phone
Book) or created automatically when synchronizing with the server
(see Server Synchronization Options).

A3 ALPHA/A1800 ALPHA METERS AND IP AXISLINK


DEVICES

368
TM42-3060

Supported Phone Book


Minimum security mode Notes
entry
When you manually
create the Phone Book
entry, you can only
connect to this meter
Manual
using Cleartext. The
Security Mode drop list
will not be displayed in
the Phone Book entry.
Cleartext with
When the Phone Book
authentication
is synchronized with the
server, you can connect
to this meter using
Synced either Cleartext or
Ciphertext using the
Security Mode drop list
in the Phone Book
entry.
You can only connect to
the meter using
Ciphertext with Ciphertext. The Security
Synced
authentication Mode drop list is not
displayed in the Phone
Book entry.

REXUNIVERSAL METERS
Supported Phone Book
Minimum security mode Notes
entry
You can only connect to
the meter using
Ciphertext with Ciphertext. The Security
Manual
authentication Mode drop list is not
displayed in the Phone
Book entry.

About Special Dates


Metercat handles the nonrecurring dates differently depending on
the state of the Programming compatible with EER export option.
When programming meters with special dates, it is important to
understand the differences in the operation.

TYPICAL OPERATION
Under typical operation, the compatible with EER option is
unchecked, and Metercat will write the nonrecurring dates in the
traditional fashion. Metercat will write only the nonrecurring dates
that are scheduled to occur in the future as determined by the date
of the actual programming up to the meter's maximum number of
entries. A3 ALPHA meter can store up to 255 nonrecurring entries;
the REXUniversal meter can store up to 5 nonrecurring entries.

369
Application notes

Example: You created a special dates component on January 5,


2010, that includes nonrecurring entries for Good Friday, Easter, and
Easter Monday for the next 20 years. The EER compatibility option
remains unchecked. On February 18, 2015, you program a
REXUniversal meter over the optical port with this special dates
component. Metercat will write only the nonrecurring dates that are
scheduled to occur in the future based on the date of programming.
In this situation, the meter calendar will expire on March 27, 2016.

COMPATIBLE EER EXPORT OPERATION


To prevent a mismatch between the special dates configuration and
the actual meter programming, the compatible EER export option will
always write the maximum number of entries beginning with the first
entry listed in the component. The A3 ALPHA meter can store up to
255 nonrecurring entries, and the REXUniversal meter can store up
to 5 nonrecurring entries.
Example: You created a special dates component on January 5,
2010, that includes nonrecurring entries for Good Friday, Easter, and
Easter Monday for the next 20 years. You enabled the programming
to be compatible with the EER export file. On February 18, 2015, you
program a REXUniversal meter over-the-air using an EER file. The
endpoint execution request will write the maximum number of entries
beginning with the first entry listed in the component. In this
situation, the meter calendar expired on April 24, 2011.

370
TM42-3060

To avoid programming an expired calendar, you must create a new


special dates component and make sure the first five nonrecurring
entries are appropriate for your needs.

About the register multiplier


The register multiplier is referred to as the external display multiplier
in the meter technical manuals. It may also be referred to as the
register constant, dial constant, reading multiplier, or the external
multiplier.
The register multiplier should be used when the transformer factor
(current transformer ratio × voltage transformer ratio) is larger than
can be stored in the meter. When programmed for a register
multiplier, the quantities read from the meter's LCD or register must
be manually multiplied by the register multiplier to yield the proper
readings.
The register multiplier value indicates the number of decimal places
that the meter uses to adjust its adjusted Ke value to obtain a
calculated value that can be stored in the meter without losing
significant digits. Since this value is multiplied by the reading to yield
a scaled reading, Metercat must divide the factory Ke by this value to
produce a reading that eventually will be scaled externally. The
register multiplier may be applied to the Factory Ke whether the
metering application is either primary or secondary.

Changing ANSI C12.19 passwords


Changing passwords is a complex process. If performed incorrectly, it
is possible to lock yourself out of the meter. By handling the
password changes correctly, you can avoid the having to return the
meter to the factory to have the passwords reset.

371
Application notes

1 Determine the password set currently used in the meter. If the


password set does not exist, create one and set all three
passwords to the values that are stored in the meter.
To do this, go to Tools > Meter Password Management > ANSI
C12.19 (see topic for help) and note the name of the password
set that is currently in the meter.
2 Make sure that you have access to the password set and that
you have unrestricted access to the meter.
This varies based on whether you have a single user or multiple
user configuration for Metercat. If you are using a single user
configuration of Metercat, select Tools > Account Information >
Meter Access Level (see topic for help). If you are using multiple
user configuration, select Tools > User Management > (user
group) > Edit (see topic for help). Then, go to the Meter Access
Level tab.
Be sure that the password set for ANSI C12.19 is the same as
the password set noted in Step 1.
Make sure that the access level for meter communication is set
to unrestricted.
3 Edit the password set and update the passwords for all three
levels (read only, billing, and unrestricted). Also, set the
password history depth to 2.
To do this, go to Tools > Meter Password Management > ANSI
C12.19 and edit the password set identified in step 1 (see topic
for help). When you finish, click Apply.
4 Verify that the passwords have been changed correctly by
checking the history level.
To do this, click History to display the password history. The new
passwords that you will write to the meter should be at the top,
and the passwords presently stored in the meter should be
below.
5 Create a new function that includes the Change Passwords -
A3/A1800/IPAL task. Configure the task so that it replaces all
passwords by enabling Change Passwords > Unrestricted and
Billing.
To do this, go to Tools > Function Management > New (see
topic for help).
6 Open an optical connection and execute the change password
function created in Step 5 (see topic for help). Make sure
Metercat successfully completes the function.
7 Securely archive the new values of the passwords outside of
Metercat.
This will serve as a backup in case the Metercat database is ever
lost or corrupt. If the unrestricted meter password is ever lost or
unrecoverable, the meter must be returned to the factory for
reset.

372
TM42-3060

EA_NIC programming notes


To have the meter function properly as a node within the EnergyAxis
System, it is important that the meter is programmed correctly using
Metercat. Be sure to understand the following restrictions.

A3 ALPHA METER WITH EA_NIC


Component Description
For A3D and A3T meters: the option
board will return the first energy
quantity and the first demand
quantity configured in the meter.
For all other meter types: the option
Metering (Quantities tab)
board will return the first 2 energy
quantities and first 2 demand
quantities configured in the meter. It
will also return the first 2 coincident
demands configured in the meter.
When operating as a network element
within EnergyAxis, the following items
(located in the EnergyAxis Items
category) are available for display:

Metering (Display tab) ILC/ILN errors


ILC/ILN status
EnergyAxis utility ID
LAN ID 1 and LAN ID 2
LAN registration information

Quantities to record: The option board


will return data for the first 4 energy
channels (noteRequires EA_NIC
firmware version 5.6 or later and
EA_MS 8.0 or later. For firmware
versions prior to 5.6, the EA_NIC only
returns the first 2 energy channels
configured in the meter.) configured
in the meter. The option board
generates a configuration error if any
of the first 4 energy channels are
configured to profile a net quantity
Load Profile (noteFor EA_NIC firmware versions
5.6 or later, the EA_NIC will return
interval data for all channels.
However, if one of the channels is a
net quantity, the load profiling data
will be flagged with a configuration
error. For EA_NIC firmware versions
earlier than 5.6, the EA_NIC will not
return any data if the meter is
configured for a net quantity. Instead,
the EA_NIC will only generate a
configuration error.).
Interval length: The interval length

373
Application notes

can be 5, 6, 10, 12, 15, 30, or 60


minutes. Selecting any other interval
length will return interval data but
with an unknown interval length
reported to EA_MS.
Quantity: For each set, the option
board will return data for the first 6
channels configured in the meter.
Interval length: The interval length
Instrumentation Profiling can be 5, 6, 10, 12, 15, 30, or 60
minutes. Selecting any other interval
length will return interval data but
with an unknown interval length
reported to EA_MS.
Interval (minutes): For all meter types,
Elster recommends that you select
15, 30, or 60 minutes. Selecting any
other value can prevent the actual
demand interval length from being
Demand reported in the data. That is, the
actual data will be reported without
specifying the demand interval
length. If any other demand interval is
required, contact Elster for more
information.
Beginning with EA_NIC version 6.0,
demand reset dates are always
controlled by the meter calendar.
Using the system, a demand reset
date may be assigned to the meter
and communicated from EA_MS to
Special Dates the gatekeeper to the EA_NIC. When
the system assigned demand reset
date is successfully communicated to
the NIC, the NIC updates the meter's
calendar to replace the existing
demand reset dates with the system-
assigned recurring date.
A3 ALPHA meters with the EA_NIC
can support the relay option board or
the extended memory option board
(note). Configuration for port 1 and
port 2 usage for meters is as follows:
If an additional option board is not
Remote
used: Port 1 set to Direct Connect at
9600 bps and Port 2 set to Disabled.
If an additional option board is
present: Port 1 set to Disabled and
Port 2 set to Direct Connect at 9600
bps.

A1800 ALPHA METER WITH EA_NIC


Component Description
The option board will return the first 2
Metering (Quantities tab)
energy quantities and first 2 demand

374
TM42-3060

quantities configured in the meter. It


will also return the first 2 coincident
demands configured in the meter.
When operating as a network element
within EnergyAxis, the following items
(located in the EnergyAxis Items
category) are available for display:

Metering (Display tab) ILC/ILN errors


ILC/ILN status
EnergyAxis utility ID
LAN ID 1 and LAN ID 2
LAN registration information

Interval data mode: The meter must


be configured to record pulses and
not engineering units.
Quantities to record: The option board
will return data for the first 4 energy
channels (noteRequires EA_NIC
firmware version 5.6 or later and
EA_MS 8.0 or later. For firmware
versions prior to 5.6, the EA_NIC only
returns the first 2 energy channels
configured in the meter.) configured
in the meter. The option board
generates a configuration error if any
of the first 4 energy channels are
configured to profile a net quantity
(noteFor EA_NIC firmware versions
Metering (Interval Data Configuration
5.6 or later, the EA_NIC will return
tab)
interval data for all channels.
However, if one of the channels is a
net quantity, the load profiling data
will be flagged with a configuration
error. For EA_NIC firmware versions
earlier than 5.6, the EA_NIC will not
return any data if the meter is
configured for a net quantity. Instead,
the EA_NIC will only generate a
configuration error.).
Interval length: The interval length
can be 5, 6, 10, 12, 15, 30, or 60
minutes. Selecting any other interval
length will return interval data but
with an unknown interval length
reported to EA_MS.
Quantity: For each set, the option
board will return data for the first 6
channels configured in the meter.
Interval length: The interval length
Instrumentation Profiling can be 5, 6, 10, 12, 15, 30, or 60
minutes. Selecting any other interval
length will return interval data but
with an unknown interval length
reported to EA_MS.

375
Application notes

Interval (minutes): For all meter types,


Elster recommends that you select
15, 30, or 60 minutes. Selecting any
other value can prevent the actual
demand interval length from being
Demand reported in the data. That is, the
actual data will be reported without
specifying the demand interval
length. If any other demand interval is
required, contact Elster for more
information.
Beginning with EA_NIC version 6.0,
demand reset dates are always
controlled by the meter calendar.
Using the system, a demand reset
date may be assigned to the meter
and communicated from EA_MS to
Special Dates the gatekeeper to the EA_NIC. When
the system assigned demand reset
date is successfully communicated to
the NIC, the NIC updates the meter's
calendar to replace the existing
demand reset dates with the system-
assigned recurring date.
For n1810 meters: Port 1 set to
Direct Connect at 9600 bps and Port
2 set to Disabled.
For n1830 meters: Port 1 set to
Remote
Direct Connect at 9600 bps and Port
2 set to Direct Connect at an
appropriate rate for the serial RS-232
or RS-485 connectivity.

Estimated load profiling days (A3 ALPHA)


The following table shows the estimated number of days of load
profiling storage available. These values are estimated based on A3
ALPHA meter firmware version 6.x. Other variables, such as firmware
version and meter programming, may affect the storage capabilities.
Data for this table is based on the following settings:
 load profile interval is set to 15 minutes
 no instrumentation profiling

The first number (min) shows the estimated number of days of load
profiling assuming all other logs and self reads record their maximum
number of entries. The second number (max) shows the estimated
number of days of load profiling assuming all other logs and data
sets record their minimum number of entries.
1 2 3 4 5 6 7 8
chann chann chann chann chann chann chann chann
el els els els els els els els

376
TM42-3060

Min:
Min: Min: Min: Min: Min: Min: Min:
47
89 36 26 22 18 16 14
days
64 days days days days days days days
Max:
KB Max: Max: Max: Max: Max: Max: Max:
68
127 52 38 32 26 23 20
days
days days days days days days days
Min: Min: Min: Min: Min: Min: Min: Min:
288 153 117 86 73 60 53 46
12
days days days days days days days days
8
Max: Max: Max: Max: Max: Max: Max: Max:
KB
326 174 132 98 83 68 60 52
days days days days days days days days
Min: Min: Min: Min: Min: Min: Min: Min:
683 364 278 205 174 142 127 109
25
days days days days min days days days
6
Max: Max: Max: Max: Max: Max: Max: Max:
KB
721 385 293 216 184 150 134 115
days days days days days days days days
1 3177 1696 1294 954 812 664 592 509
MB days days days days days days days days

Estimated load profiling days (A1800 ALPHA)


The following table shows the estimated number of days of load
profiling storage available. These values are estimates and may vary
depending on the firmware and programming used in the meter.
Data for this table is based on the following settings:
 load profile interval is set to 15 minutes
 no instrumentation profiling
 the meter is programmed for 6 metered quantities, 2 average
power factors, and 4 coincident values

The first number (min) shows the estimated number of days of load
profiling assuming all other logs and self reads record their maximum
number of entries. The second number (max) shows the estimated
number of days of load profiling assuming all other logs and data
sets record their minimum number of entries.
2 3 4 5 6 7 8
1
chann chann chann chann chann chann chann
channel
els els els els els els els
Min: Min: Min: Min: Min: Min: Min: Min:
594da 317 242 178 151 124 110 95
25 ys days days days days days days days
6
KB Max: Max: Max: Max: Max: Max: Max: Max:
714 381 291 214 182 149 133 114
days days days days days days days days
1 3177 1696 1294 954 812 664 592 509
M
B days days days days days days days days

377
Application notes

Fast pulse
A fast pulse is a pulse with a width of 1 Ke.

Fixed width pulse


A pulse with a width of 2 milliseconds.

Four quadrant metering

Keyboard shortcut guidelines


Metercat allows you to configure keyboard shortcuts for functions.
Valid combinations may be either a single key press (for example,
[F2]) or a combination of key presses (for example, [CTRL] + [F2] or

378
TM42-3060

[CTRL] + [SHIFT] + [F2]). To avoid overriding default Metercat


shortcuts, use care when selecting the shortcut combination. The
following table describes the various keyboard sequences and their
usage as a keyboard shortcut for functions.
Key sequence Description
Reserved. Used as the Metercat
[ALT] + [C]
Cancel button shortcut.
Reserved. Used for the standard
[CTRL] + [C], [CTRL] + [X], [CTRL] + [V] copy, cut, and paste commands
within Windows.
Reserved. Used to delete the
[Delete], [SHIFT] + [Delete] currently assigned shortcut key
sequence.
Allowed; however, using [F1] will
[F1] override the ability to use Metercat's
context-sensitive keyboard shortcut
Reserved. Used for the Repeat
[F9]
command within Metercat.
Allowed; however, using the [ALT] +
character combination may override
[ALT] + character
Metercat's menu and dialog button
shortcuts.
Metercat assigns defined connections
to an [ALT] + number shortcut (for
example, the optical probe
[ALT] + number connection may be [ALT] + [1]). You
may use an [ALT] + number shortcut
if it is not already assigned to a
connection shortcut.
[ALT] + [SHIFT] + character; [ALT] +
Allowed
[SHIFT] + number
Provided the sequence is not
[CTRL] + character
reserved, allowed.
[CTRL] + number; [CTRL] + [SHIFT] +
Allowed
character; [CTRL] + [SHIFT] + number

VIEWING ASSIGNED SHORTCUTS


Prior to Metercat 6.1, selecting Help > Function Shortcuts
generated an HTML report that displayed the keyboard shortcuts
along with the functions the shortcuts performed. Users had to save
or print the HTML report to preserve the information.
Beginning with Metercat 6.1, selecting Help > Function Shortcuts
displays the functions along with their assigned shortcuts directly on
the Metercat background. Because keyboard shortcuts may or may
not be valid for your selected connection type, Metercat will
automatically update the list of valid keyboard shortcuts when you
change connection types.
The shortcut display will remain on the background (even if you quit
and restart Metercat) until you select Help > Function Shortcuts to
turn off the display.

Meter types

379
Application notes

Meter types vary by meter family.

A3 ALPHA METERS
Different A3 ALPHA meter types have different capabilities. The
following table identifies the base meter types (that is, without any
features or capabilities that can be added to extend the base meter
type functionality).
Type Measures and calculates
A3D Watthours (Wh) and maximum demand (kW)
A3T Wh and W on a time-of-use (TOU) basis
Wh and W on a TOU basis
Volt-ampere-hours (VAh) and VA on a TOU basis
A3K VAh is measured and calculated arithmetically
Volt-ampere-reactive-hours (VARh) and VAR on a
TOU basis
Wh and W on a TOU basis
VAh and VA on a TOU basis
A3R VAh is measured by vectorial calculation using Wh
and VARh on a continuous integration basis
VARh and VAR on a TOU basis
Wh and W on a TOU basis
A3Q
Q-hours (Qh) and Q on a TOU basis

Additional functionality can be added to the base type either at the


time of ordering or later through the use of Alpha Keys hardware and
software. The additional features are identified by one or more
suffixes added to the base meter type:
Suffix Description of function
A Advanced four quadrant metering (6 quantities)
L Load profiling (LP)
N Instrumentation profiling (IP)
C Transformer and line loss compensation (LC)
Q Power quality monitoring (PQM)

The rest of this section identifies the specific quantities and


capabilities for each meter type.

Note: See the section "A3 ALPHA metered energy and demand
quantities" for the available metered quantities by type.

A3D METER CONFIGURATION OPTIONS


For the A3D meter, the following base meter and additional
functionalities are available:
Meter type kWh PQM Quantities
A3D • 1
A3DQ • • 1

A3T METER CONFIGURATION OPTIONS

380
TM42-3060

For the A3T meter, the following base meter and additional
functionalities are available:
Meter
kWh TOU LP IP PQM Quantities
type
A3T • • 1
A3TQ • • • 1
A3TL • • • 1
A3TLQ • • • • 1
A3TLN • • • • 1
A3TLNQ • • • • • 1

A3K METER CONFIGURATION OPTIONS


For the A3K meter, the following base meter and additional
functionalities are available:
Meter
kWh kVARh kVAh TOU LP IP PQM Quantities
type
A3K • • • • 2
A3KQ • • • • • 2
A3KL • • • • • 2
A3LQ • • • • • • 2
A3KLN • • • • • • 2
A3KLNQ • • • • • • • 2
A3KA • • • • 6
A3KAQ • • • • • 6
A3KAL • • • • • 6
A3KALQ • • • • • • 6
A3KALN • • • • • • 6
A3KALNQ • • • • • • • 6

A3Q METER CONFIGURATION OPTIONS


For the A3Q meter, the following base meter and additional
functionalities are available:
Type kWh kQh TOU LP IP LC PQM Quantities
A3Q • • • 2
A3QQ • • • • 2
A3QC • • • • 2
A3QCQ • • • • • 2
A3QL • • • • 2
A3QLQ • • • • • 2
A3QLC • • • • • 2
A3QLCQ • • • • • • 2
A3QLN • • • • • 2
A3QLNQ • • • • • • 2
A3QLNC • • • • • • 2
A3QLNCQ • • • • • • • 2
A3QA • • • 6

381
Application notes

A3QAQ • • • • 6
A3QAC • • • • 6
A3QACQ • • • • • 6
A3QAL • • • • 6
A3QALQ • • • • • 6
A3QALC • • • • • 6
A3QALCQ • • • • • • 6
A3QALN • • • • • 6
A3QALNQ • • • • • • 6
A3QALNC • • • • • • 6
A3QALNCQ • • • • • • • 6

A3R METER CONFIGURATION OPTIONS


For the A3R meter, the following base meter and additional
functionalities are available:
Type kWh kVARh kVAh TOU LP IP LC PQM Quantities
A3R • • • • 2
A3RQ • • • • • 2
A3RC • • • • • 2
A3RCQ • • • • • • 2
A3RL • • • • • 2
A3RLQ • • • • • • 2
A3RLC • • • • • • 2
A3RLCQ • • • • • • • 2
A3RLN • • • • • • 2
A3RLNQ • • • • • • • 2
A3RLNC • • • • • • • 2
A3RLNCQ • • • • • • • • 2
A3RA • • • • 6
A3RAQ • • • • • 6
A3RAC • • • • • 6
A3RACQ • • • • • • 6
A3RAL • • • • • 6
A3RALQ • • • • • • 6
A3RALC • • • • • • 6
A3RALCQ • • • • • • • 6
A3RALN • • • • • • 6
A3RALNQ • • • • • • • 6
A3RALNC • • • • • • • 6
A3RALNCQ • • • • • • • • 6

A3 ALPHA METERED ENERGY AND DEMAND QUANTITIES


The A3 ALPHA meter technical manual identifies the metered
quantities for each meter type. Basic metered quantities (indicated
by blue shading) can be selected as a source for relay and optical
port pulse outputs. The remaining metered quantities are calculated
from 2 or more basic metered quantities.

382
TM42-3060

Metered
quantity
A3D/A3T A3K A3R A3Q
kWh
delivered
• • • •
kWh
received
• • • •
kWh sum • • • •
kWh net • • • •
kVAh
delivered
• •
kVAh
received
• •
kVAh sum • •
kVAh net •
kVAh Q1 •
kVAh Q2 •
kVAh Q3 •
kVAh Q4 •
kQh
delivered

kQh
received

kQh sum •
kVARh
delivered

kVARh
received

kVARh
sum

kVARh
net

kVARh Q1 •
kVARh Q2 •
kVARh Q3 •
kVARh Q4 •
kVARh
(Q1 + Q4)
• •
kVARh
(Q2 + Q3)
• •

A1800 ALPHA METERS


When creating a program or component for the A1800 ALPHA, you
must select the reactive meter type using time of use as the program
type.
The A1800 ALPHA meter supports the following quantities for both
energy and demand. Basic metered quantities (indicated by blue
shading) can be selected as a source for relay outputs.
 kVAh delivered (Q1 + Q4)

383
Application notes

 kVAh Q1
 kVAh Q2
 kVAh Q3
 kVAh Q4
 kVAh received (Q2 + Q3)
 kVAh sum (delivered + received)
 kvarh (Q1 - Q4)
 kvarh (Q1 + Q4)
 kvarh (Q2 - Q3)
 kvarh (Q2 + Q3)
 kvarh (Q3 - Q2)
 kvarh delivered (Q1 + Q2)
 kvarh net
 kvarh Q1
 kvarh Q2
 kvarh Q3
 kvarh Q4
 kvarh received (Q3 + Q4)
 kvarh sum (delivered + received)
 kWh delivered
 kWh net
 kWh received
 kWh sum

REXUNIVERSAL METERS
The REXUniversal meter reports register data using standard tables
defined by Decade 2 of C12.19 (standard tables 20, 21, 22, 23, 24,
25 and 26). The metered quantities (that is, sources that can be
selected for summation (energy) and demand registers are as
follows:
 kWh delivered
 kWh received
 kWh sum (delivered + received)
 kWh net (delivered - received)
 kVARh delivered (Q1 + Q2)
 kVARh received (Q3 + Q4)
 kVARh sum (delivered + received)

384
TM42-3060

 kVARh net (delivered - received)


 kVAh delivered

 kVAh received

Metercat event IDs


In the event log, the cs3Label is set to eventID, and the value of cs3
of the event ID. For example, the cs3label and cs3 value for a user
logoff would be as follows:
 cs3label=eventID
 cs3=101
For more information on the Event Viewer, see the Event Viewer
topic.

SECURITY EVENTS

EVENT ID = 100
Event: User login success
Signature ID: securityServiceOrMechanism(9)
Name: authenticationSuccess(799)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: computer's GUID
suid and suser: user's GUID and user name
reason: user login
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success

Event: User login failure


Signature ID: securityServiceOrMechanism(9)
Name: authenticationFailure(750)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: computer's GUID
suid and suser: user's GUID and user name
reason: user login

385
Application notes

cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: failed

EVENT ID = 101
Event: User logoff
Signature ID: securityServiceOrMechanism(9)
Name: authenticationSuccess(799)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: computer's GUID
suid and suser: user's GUID and user name
reason: user logoff
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed

EVENT ID = 102
Event: Create new user
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: new user's GUID and user name
suid and suser: user's GUID and user name who created the new
user
reason: create new user
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed

EVENT ID = 103
Event: Change user
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: destination user's GUID and user name

386
TM42-3060

suid and suser: source user's GUID and user name


reason: edit user
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

EVENT ID = 104
Event: Delete user
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: destination user's GUID and user name
suid and suser: source user's GUID and user name
reason: edit user
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed

EVENT ID = 105
Event: Create new user group
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: new group's GUID and group name
suid and suser: source user's GUID and user name
reason: create new user group
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed

EVENT ID = 106
Event: Change user group
Signature ID: operational(7)
Name: configurationDataChange(692)

387
Application notes

Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: destination group's GUID and group name
suid and suser: source user's GUID and user name
reason: edit user group
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

EVENT ID = 107
Event: Delete user group
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid and duser: destination group's GUID and group name
suid and suser: source user's GUID and user name
reason: delete user group
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed

EVENT ID = 108
Event: Create new server (OEM or EAMS) config
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of new server
dpt = port address of new server
dhost = new server name
suid and suser: source user's GUID and user name
reason: create EA_MS configuration
cat: securityAudit(1)
rt = date and time stamp (UTC)

388
TM42-3060

outcome: success or failed

EVENT ID = 109
Event: Change server (OEM or EAMS) config
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination server
dpt = port address of destination server
dhost = destination server name
suid and suser: source user's GUID and user name
reason: edit EA_MS configuration
cat: securityAudit(1)
rt = date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

EVENT ID = 110
Event: Delete server (OEM or EAMS) config
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination server
dpt = port address of destination server
dhost = destination server name
suid and suser: source user's GUID and user name
reason: delete EA_MS configuration
cat: securityAudit(1)
rt = date and time stamp (UTC)
outcome: success or failed

EVENT ID= 111


Event: perform server (OEM or EAMS) synchronization
Signature ID: operational(7)
Name: configurationDataChange(692)

389
Application notes

Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination server
dpt = port address of destination server
dhost = destination server name
suid and suser: source user's GUID and user name
reason: EA_MS synchronization
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

EVENT ID= 112


Event: change system configuration
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination machine's GUID
suid and suser: source user's GUID and user name
reason: edit system config
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

EVENT ID= 113


Event: create new meter password set
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination machine's GUID
suid and suser: source user's GUID and user name
reason: create meter password
cat: securityAudit(1)

390
TM42-3060

rt: date and time stamp (UTC)


outcome: success or failed
cs2Label and cs2: modified or added values

EVENT ID= 114


Event: change meter password set
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination machine's GUID
suid and suser: source user's GUID and user name
reason: edit meter password <password level>
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

EVENT ID= 115


Event: delete meter password set
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination machine's GUID
suid and suser: source user's GUID and user name
reason: delete meter password
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: success or failed
cs1Label and cs1: original or removed values

EVENT ID= 116


Event: execute task on C12.22 encrypted channel
Signature ID: operational(7)
Name: unspecifiedReason(2048)
Severity: Information(6)

391
Application notes

deviceExternalID: reporting computer's GUID


dst: IP address of destination meter
duid: destination meter serial number
suid and suser: source user's GUID and user name
reason: execute task <task name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed
cs1Label and cs1: original or removed values
cs2Label and cs2: modified or added values

Note: executing tasks on an encrypted C12.22 channel will also


generate operational event log records.

EVENT ID= 117


Event: security failure in ANSI C12.xx communication
Signature ID: operational(7)
Name: unspecifiedReason(2048)
Severity: Warning(7)
deviceExternalID: reporting computer's GUID
dst: IP address of destination meter
duid: destination meter serial number
suid and suser: source user's GUID and user name
reason: security failure in ANSI C12.xx communication <exception
message>
cat: securityAudit(1)
rt: date and time stamp (UTC)
outcome: failed

EVENT ID = 120
Event: export meter program
Signature ID: operational(7)
Name: serviceStateChange(699)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination computer's GUID

392
TM42-3060

suid and suser: source user's GUID and user name


reason: export meter program <name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

EVENT ID = 121
Event: import meter program
Signature ID: operational(7)
Name: serviceStateChange(699)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
duid: destination computer's GUID
suid and suser: source user's GUID and user name
reason: import meter program <name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

EVENT ID = 122
Event: execution of Activate Factory WAN Key Task
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination meter
duid: destination meter serial number
suid and suser: source user's GUID and user name
reason: activate factory wan key task over <protocol name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

Note: activating the WAN key will also generate its related
operational event log record.

393
Application notes

EVENT ID = 123
Event: execution of Activate Factory LAN Key Task
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination meter
duid: destination meter serial number
suid and suser: source user's GUID and user name
reason: activate factory lan key task over <protocol name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

Note: activating the LAN key will also generate its related
operational event log record.

EVENT ID = 124
Event: execution of Change Password task
Signature ID: operational(7)
Name: configurationDataChange(692)
Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination meter
duid: destination meter serial number
suid and suser: source user's GUID and user name
reason: change password task over <protocol name>
cat: securityAudit(1)
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed

OPERATIONAL EVENTS

EVENT ID = 500
Event: execution of Activate Factory WAN Key Task
Signature ID: operational(7)
Name: serviceStateChange(699)

394
TM42-3060

Severity: Information(6)
deviceExternalID: reporting computer's GUID
dst: IP address of destination meter
duid: destination meter serial number
dserv: meter family and type, if applicable (A3R, REXUniversal, REX2,
etc.)
suid and suser: source user's GUID and user name
reason: execute task <task name>
cat: securityAudit(1)
msg: in case of error, the message of the error
start: date and time stamp (UTC) when the event began
stop: date and time stamp (UTC) when the event ended
outcome: success or failed
cs2Label and cs2: the task runtime parameters (if any)

Note: executing tasks on an encrypted C12.22 channel or


activating the LAN or WAN key will also generate their related
security event log record.

Program types
The A3 ALPHA meter supports both demand-only metering and TOU
metering. The A1800 ALPHA meter only supports TOU metering.
If you are prompted to select a program type, select from the
following options:
 If you are creating a program or component for a demand-only
meter, select Single Rate Demand (No Timekeeping).
 If you are creating a program or component for a TOU meter,
select Time Of Use.

Relay wiring diagrams


A3 ALPHA METER RELAYS
The output relays can switch up to 120 VAC or 200 VDC at up to 100
mA. The KYZ1 relay can be terminated to three, small voltage blades
in 13-terminal socket applications (or to a specific terminal in A-base
meters). For more information, see Appendix D of the A3 ALPHA
meter technical manual.

COLOR CODING FOR 1 OR 2 RELAYS WITH 6 OUTPUT


LEADS

395
Application notes

COLOR CODING FOR 4 RELAYS WITH 8 OUTPUT LEADS

COLOR CODING FOR 4 RELAYS WITH 9 OUTPUT LEADS

COLOR CODING FOR 6 RELAYS WITH 12 OUTPUT LEADS

396
TM42-3060

A1800 ALPHA METER RELAYS


The output relays on the main circuit board can switch up to 125 VAC
or 180 VDC at up to 70 mA. See Appendix D of the A1800 ALPHA
meter technical manual.

A1800 ALPHA METER WITH RS-232 AS SECOND


COMMUNICATION PORT

397
Application notes

A1800 ALPHA METER WITH RS-485 AS SECOND


COMMUNICATION PORT

REX2 meter codes


The REX2 meter technical manual identifies the error and status
codes for the REX2 meter.

ERROR CODES
Error codes indicate a problem exists with the meter that may affect
billing data. Elster does not recommend operating the REX2 meter
when it is displaying an error code.

E10000: POWER FAIL DATA SAVE ERROR


This code indicates that the data saved in nonvolatile EEPROM
during a power fail may be invalid. This error will be displayed when
power is restored to the meter and then a self check has detected an
error with the EEPROM data after a power fail data save. The REX2
meter should be returned to the factory for repair or replacement.

E01000: CONFIGURATION ERROR


This code indicates a problem with the meter's configuration. If the
error continues after reprogramming, the meter should be returned
to the factory for repair or replacement.

398
TM42-3060

E00100: TABLE CRC ERROR


This code indicates a possible error in the REX2 meter's
programming. Depending on which area of the meter is affected,
billing data may not be reliably accumulated while this error condition
exists. The REX2 meter should be returned to the factory for repair or
replacement.

E00010: EEPROM WRITE ERROR


This code indicates that the meter had a problem storing meter data
in nonvolatile EEPROM. The REX2 meter should be returned to the
factory for repair or replacement.

E00001: IMPROPER METER ENGINE OR RADIO


MICROPROCESSOR OPERATION ERROR
This code indicates that the meter engine program or radio
microprocessor may be corrupt or is not executing correctly. If this
code is displayed on the LCD, the REX2 meter should be returned to
the factory for repair or replacement.

STATUS CODES
Unlike error codes, status codes do not indicate a problem with the
REX2 meter. However, some status conditions may be caused by
possible tampering with the meter. When such a status condition is
present, the LCD will also display the tamper detect indicator on the
LCD.

F10000: NO LOAD SIDE VOLTAGE WHEN SERVICE


CONTROL SWITCH IS CLOSED
This code indicates that there is no load side voltage present when
the service control switch is supposedly closed. The code can
indicate a malfunction with the service control switch. If this code is
displaye, contact Elster.

F01000: DEMAND THRESHOLD EXCEEDED


This code indicates that the demand has exceeded the programmed
threshold. It is displayed once the demand threshold has been
exceeded and is cleared by a demand reset, clear status, or clear
data command.

F00100: LOAD SIDE VOLTAGE PRESENT WHEN SERVICE


CONTROL SWITCH IS OPEN
This code indicates load side voltage present when the service
control switch is open. This code can indicate one of the following
conditions exist:
 a malfunction occurred in the service control switch
 the load side is receiving voltage from a different source (for
example, a gas powered generator)

399
Application notes

This code may be the result of meter tampering; therefore, the


tamper detect indicator on the LCD is lit while the condition is
present. If this status code is displayed, follow your utility's
procedures for restoring power when there is a possibility of power
being supplied to the load side by a different source.

F00010: DEMAND RESET SCHEDULED


This code indicates that the meter has been scheduled to perform a
demand reset at the next midnight crossing. This code is displayed
when it receives a command to perform a demand reset from the
network. This code remains on the display until the next midnight
crossing (the time the meter performs the demand reset).

F00001: SERVICE CONTROL SWITCH OPEN


This code requires meter firmware version 3.0 and later. This code
indicates that the service control switch is open because either the
meter received a command or the demand threshold is exceeded.
This code is displayed when the switch is open, and it is cleared
when the switch is closed. The meter also displays the status of the
service control switch using the service control switch indicators on
the LCD.

F20000: VOLTAGE ABOVE MAXIMUM THRESHOLD


This code indicates that the meter has detected a voltage that
exceeds a programmable maximum voltage threshold for a duration
greater than or equal to a programmable maximum voltage time.
This code is cleared by a demand reset, clear data, or clear status
command. Also, once this code has been reported by the gatekeeper
and read by the head-end system, the head-end system can instruct
the gatekeeper to issue a clear status command at its next
communication with the meter (usually, the next meter read).

F02000: VOLTAGE BELOW MINIMUM THRESHOLD


This code indicates that the meter has detected a voltage that drops
below the minimum voltage threshold for a duration greater than or
equal to a programmable minimum voltage time.
This code is cleared by a demand reset, clear data, or clear status
command. Also, once this code has been reported by the gatekeeper
and read by the head-end system, the head-end system can instruct
the gatekeeper to issue a clear status command at its next
communication with the meter (usually, the next meter read).

F00200: DEMAND LIMITING OPERATIONS EXCEEDED


This code indicates that the meter has exceeded the programmable
threshold for demand limiting operations within a specific time.
When the demand limiting operation threshold is exceeded, the
meter opens the service control switch to disconnect power to the
consumer. The service control switch will remain open until it is

400
TM42-3060

closed by the utility using a command sent over the network or


through the optical port.
This code is cleared when the service control switch is closed by the
utility (remotely or optically) or when the meter receives a clear data
command.

F00020: TILT WARNING


This code indicates that the meter detected a tilt condition in
conjunction with a power outage. The tamper detect indicator on the
LCD is lit when this condition is flagged.
This code is cleared by a demand reset, clear status, clear billing
data, or clear data command.

F30000: TOU SCHEDULE OUT-OF-DATE


This code indicates that the TOU schedule stored in the REX2 meter
is out-of-date. When the gatekeeper detects this status code, the
gatekeeper will re-send the current TOU schedule to the REX2 meter.
This code is cleared automatically when the meter receives a valid
TOU schedule.

F03000: EVENT LOG UPDATED


This code indicates that a new event has been posted to the event
log that has not yet been read by the gatekeeper. When an event
occurs, it can be logged in the event log. The meter will send an
exception message to the gatekeeper to report the new event log
entry, but the status code is displayed on the meter LCD until the
gatekeeper reads the meter’s event log.
This code is cleared when the gatekeeper reads the event log.

F00300: REVERSE ENERGY WARNING


This code indicates that reverse energy flow has been detected that
is equal to or greater than the programmed reverse energy threshold.
If reverse energy flow is expected, then this warning can be disabled.
If the service being metered is not expected to return energy to the
utility, further investigation may be required. The tamper detect
indicator on the LCD is lit while this condition is present.
This code is cleared by a demand reset, clear status, clear billing
data, or clear data command.

F00030: INVALID ACCESS WARNING


This code indicates possible tampering with the meter because a
specified number of invalid optical passwords or invalid LAN
encryption keys were received by the meter. The meter has separate
counters for the optical port and the radio: if either count exceeds
the threshold, the flag is set.
This code is cleared by a demand reset, clear status, clear billing
data, or clear data command.

401
Application notes

F00003: CONFIGURATION TABLE WRITE WARNING


This code indicates that a specified meter configuration table within
the meter has been written, indicating possible tampering with the
meter programming. The tamper detect indicator on the LCD is lit
when this event occurs.
This code is cleared by a demand reset, clear status, clear billing
data, or clear data command.

EVENTS RECORDED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 an exception exists that will be reported to the gatekeeper
 no load side voltage detected when service control switch is
closed
 demand threshold exceeded
 latched copy of load side voltage present when service control
switch is open
 load side voltage present when service control switch is open
 demand reset scheduled
 service control switch is open
 phase A or phase C is below the minimum phase voltage
threshold
 a voltage monitoring minimum or maximum event has occurred
 service control switch is open because of a demand limit lockout
 the load control relay is open

WARNINGS RECORDED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 a tilt event occurred
 reverse energy detected
 invalid access occurred
 configuration table write occurred
 TOU schedule out of date
 warning temperature threshold exceeded
 service disconnect temperature threshold exceeded

ERRORS REPORTED IN METERCAT


Metercat is capable of reporting the following errors:
 radio operation error

402
TM42-3060

 radio configuration error


 power fail data save error
 configuration error in the meter tables
 meter table CRC error
 EEPROM write error
 meter engine error

REXUniversal meter codes


ERROR CODES
Error codes indicate a problem exists with the meter that may affect
billing data. Elster does not recommend operating the REXUniversal
meter when it is displaying an error code.

E10000: POWER FAIL DATA SAVE ERROR


This code indicates that the data saved in nonvolatile EEPROM
during a power fail may be invalid. This error will be displayed when
power is returned to the meter and then a self check has detected an
error with the EEPROM data after a power fail data save. The meter
should be returned to the factory for repair or replacement.

E01000: CONFIGURATION ERROR


This code indicates a problem with the meter’s configuration. If the
error continues after reprogramming, the meter should be returned
to the factory for repair or replacement.

E00100: TABLE CRC ERROR


This code indicates a possible error in the meter’s programming.
Depending on which area of the meter is affected, billing data may
not be reliably accumulated while this error condition exists. The
meter should be returned to the factory for repair or replacement.

E00010: EEPROM WRITE ERROR


This code indicates that the meter had a problem storing meter data
in nonvolatile EEPROM. The meter should be returned to the factory
for repair or replacement.

E00001: IMPROPER METER ENGINE OPERATION ERROR


This code indicates that the meter engine program may be corrupt or
is not executing correctly. If this code is displayed, the meter should
be returned to the factory for repair or replacement.

STATUS CODES
The REXUniversal meter displays status codes as an indication of the
operational status of the meter. Unlike error codes, status codes do
not indicate a problem with the meter. However, some status

403
Application notes

conditions may be caused by possible tampering with the meter.


When such a status condition is present, the LCD will also display the
tamper detect indicator on the LCD.

F00001: SERVICE CONTROL SWITCH OPEN


This code indicates that the service control switch is open. The
service control switch can be opened when either of the following
occurs:
 The meter has received a command to disconnect the
service
 The meter is configured to open the switch when the
demand threshold is exceeded
 The meter is configured to open the service control
switch based on:
o the TOU schedule
o the active tier (that is, the current rate) is one that the meter
is configured to open the switch for
This code is displayed when the switch is opened, and it is cleared
with the switch is closed. The meter also displays the status of the
service control switch on the LCD using the service control switch
indicators.

F00100: LOAD SIDE VOLTAGE PRESENT WHEN SERVICE


CONTROL SWITCH IS OPEN
This code indicates that there is load side voltage present when the
service control switch is open. This code typically indicates that
voltage applied to the load side of the meter is from a different
source (for example, a gas-powered generator).
This code may be the result of meter tampering; therefore, the
tamper detect indicator on the LCD is lit while the condition is
present. The meter also records the status flag in the register data.
The service control switch cannot be closed when load side voltage is
present. Follow your utility’s procedures for investigating an account
when there is a possibility of power being supplied to the load side by
a different source.
The code remains on the LCD for as long as the condition exists.
When the load side voltage is removed, the code is cleared from the
display.

F01000: DEMAND THRESHOLD EXCEEDED


This code indicates that the demand has exceeded the programmed
demand threshold. It is displayed once the demand threshold has
been exceeded and is cleared by a demand reset, clear status, or
clear data command.

404
TM42-3060

F10000: NO LOAD SIDE VOLTAGE WHEN SERVICE


CONTROL SWITCH IS CLOSED
This code indicates that there is no load side voltage present when
the service control switch is supposedly closed. This code can
indicate a malfunction with the service control switch. If this code is
displayed, contact Elster.

F00020: TILT WARNING


This code indicates that the meter detected a tilt condition in
conjunction with a power outage. The tamper detect indicator on the
LCD is lit when this condition is flagged.
This code is cleared by a demand reset, a clear status, or a clear
data command.

F00200: DEMAND LIMITING OPERATIONS EXCEEDED


This code indicates that the meter has exceeded the programmable
threshold for demand limiting operations within a specific time. The
service control switch is opened due to the demand limiting
operations. When the demand limiting operation threshold is
exceeded, the meter does not automatically close the service control
switch. The service control switch will remain open until it is closed
by the utility using a command sent over the network or through the
optical port.
This code is cleared when the service control switch is closed by the
utility (remotely or optically) or when the meter receives a clear data
command.

F02000: VOLTAGE BELOW MINIMUM THRESHOLD


This code indicates that the meter has detected a voltage that is
below the minimum voltage threshold for a duration greater than or
equal to a programmable minimum voltage qualification time.
This code is cleared when voltage returns to a value that is above the
minimum voltage threshold.

F20000: VOLTAGE ABOVE MAXIMUM THRESHOLD


This code indicates that the meter has detected a voltage that
exceeds a programmable maximum voltage threshold for a duration
greater than or equal to a programmable maximum voltage
qualification time.
This code is cleared when the voltage returns to a value below the
maximum voltage threshold.

F00003: CONFIGURATION TABLE WRITE WARNING

405
Application notes

This code indicates that a meter configuration table has been


written, indicating possible tampering with the meter programming.
The tamper detect indicator on the LCD is lit when this event occurs.
This code is cleared by a clear status or clear data command.

F00030: INVALID ACCESS WARNING


This code indicates possible tampering with the meter because one
of the following conditions has occurred:
 The number of log on attempts with an invalid security key has
exceeded the configurable Security Access Threshold (see the
Event Log Configuration component). The meter has separate
counters for the optical port interface and the AMI interface. If
either count exceeds the threshold, an event is indicated. In
Metercat, it is identified as Authenticate Access Warning Status
Flag in the Status view (Conditions tab).
 The number of table or task access attempts with insufficient
permission levels has exceeded the configurable Security
Access Threshold (see the Event Log Configuration component).
The meter has separate counters for the optical port interface
and the AMI interface. If either count exceeds the threshold, an
event is indicated. In Metercat, it is identified as Table Access
Warning Status Flag in the Status view (Conditions tab).
 This code is cleared by a demand reset, clear status, or clear
data command.

F00300: REVERSE ENERGY WARNING


This code indicates that the amount of reverse energy flow has
exceeded the programmed reverse energy threshold. If reverse
energy is expected, this warning can be disabled. If the service being
metered is not expected to return energy to the utility, further
investigation may be required.
The tamper detect indicator on the LCD is lit while this condition is
present.
This code is cleared by a demand reset, a clear status, or a clear
data command.

F03000: TEMPERATURE THRESHOLD EXCEEDED


This code indicates that the meter’s internal temperature has
exceeded the programmable threshold. The threshold is configured
in the Event Log Configuration component.
This code is cleared by a clear status or clear data command.

406
TM42-3060

F30000: END OF CALENDAR WARNING


This code indicates that the meter calendar has expired or is about
to expire. The date at which this code appears is configurable using
Metercat. Write a new calendar to the meter.
The code will be automatically cleared once a new calendar has been
written in the meter.

METROLOGY EVENTS RECORDED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 End device needs programming
 End device configuration error
 End device self check error
 End device RAM failure
 End device ROM failure
 End device nonvolatile memory failure
 End device clock error
 End device measurement element error
 End device low battery
 End device low loss potential
 End device demand overload
 End device power failure
 End device tamper detect
 End device reverse rotation

METROLOGY WARNINGS RECORDED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 Service control switch open
 Optical port lockout
 Load side voltage present
 Demand threshold exceeded
 No voltage (service control switch closed)
 Latched load side voltage present
 Spare flag
 Tilt warning
 Demand limit lockout
 Voltage monitoring minimum event

407
Application notes

 Voltage monitoring maximum event


 Phase A low potential
 Phase C low potential
 Invalid time change, interval data lost
 Configuration table write warning
 Excessive unauthorized table access attempts
 Date invalid
 End of calendar
 Excessive authentication failures
 Warning temperature exceeded
 Metrology protected
 Service disconnect temperature exceeded
 Tier override active
 Radio configuration table written
 Radio LAN access warning
 Exception present
 Flash transfer pending
 External operation pending
 In home device table data available

METROLOGY ERRORS REPORTED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 Table CRC error
 Registered memory error
 Radio operation error
 Radio CRC error
 Radio registered memory error
 Radio EEPROM error
 Radio flash error

COMMS WARNINGS REPORTED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 Configuration table written
 Excessive unauthorized table access attempts

408
TM42-3060

COMMS ERRORS REPORTED IN METERCAT


Metercat is capable of reporting that the following events have
occurred:
 Registered memory error detected
 Configuration error
 Table CRC error

REXUniversal meter special display items


The REXUniversal meter supports special display items. If an option
board needs to display data, it can use a special display item to
display it on the meter's LCD. The meter supports up to 8 special
display items. You can specify which special items to display using
the Display component.

REXUNIVERSAL METER FOR THE ENERGYAXIS MESH


NETWORK SPECIAL DISPLAY ITEM

NETWORK REGISTRATION STATUS


The REXUniversal meter for use within the EnergyAxis mesh network
uses special display item 5 to display the connection status to the
EnergyAxis network. The following figure shows an example of a
meter that is currently registered to a gatekeeper.

Item Description
 If the meter is registered to
a gatekeeper, the number
of communication hops
between the REXUniversal
meter and the gatekeeper.
Hop level In the above example, "4"
indicates that the
REXUniversal meter
communicates with the
gatekeeper through 3 other
meters.

409
Application notes

 If the meter is not


registered, the hop level is
replaced with a dash (see
the following example).
 If the meter is registered,
the last 4 digits (decimal
format) of the gatekeeper's
Gatekeeper ID LAN ID.
 If the meter is not
registered, the gatekeeper
ID is replaced with dashes.
 If the meter is registered to
a gatekeeper, the radio
status indicator is lit.
Radio status indicator
 If the meter is not
registered, the radio status
indicator is turned off.

The following figure shows the network registration status for a meter
that is not currently registered to a gatekeeper.

REXUNIVERSAL METER WITH W-WIC SPECIAL DISPLAY


ITEM

WIRELESS CONNECTION STATUS


The REXUniversal meter with W-WIC uses special display item 5 to
display the wireless connection status.

410
TM42-3060

Item Description
To uniquely indicate the wireless
W-WIC indicator connection status in the display list,
the value starts with the character C.
The modem status uses 2 characters
to indicate the status of the modem.
0 = inactive
1 = power on
2 = configure
3 = detect signal*
4 = register*
5 = back off*
6 = attach*
7 = attach wait*
8 = activate*
Modem status
9 = activate wait*
10 = connect*
11 = connected
12 = disconnect
13 = disconnected
14 = detach
15 = power off
16 = reset
17 = test mode
18 = OTASP*
* Radio status indicator = blinking
The character r comes before the
RSSI indicator
RSSI value.
The RSSI value may vary between 0
RSSI value and 31, with 31 indicating the best
possible signal strength.
 If the indicator is off, the modem
is not connected to the cell phone
network.
 If the indicator is blinking, the
modem is attempting to connect
Radio status indicator
to the cell phone network.
 If the indicator is on (solid), the
modem is connected to the cell
phone network (modem status =
11).

REXUNIVERSAL METER WITH SYNERGYNET NETWORK


SPECIAL DISPLAY ITEM
The REXUniversal meter for use within the SynergyNet network uses
special display item 5 to display the connection status. The following
figure shows an example of the display indicating the number of hops
to its SynergyNet router.

411
Application notes

Standard pulse
A standard pulse is a pulse with a width of ½ Kh.

Transformer and line loss compensation


ABOUT TRANSFORMER AND LINE LOSS COMPENSATION

WHAT IS LOSS COMPENSATION?


The Handbook for Electricity Metering defines loss compensation as
follows:
A means for correcting the reading of a meter when
the metering point and the point of service are
physically separated resulting in measurable losses
including I2R losses in conductors and transformers,
and iron-core losses. These losses may be added to,
or subtracted from the meter registration.
[Edison Electric Institute, Handbook for Electricity
Metering, 10th edition, Washington, DC: Edison
Electric Institute, 2002, p.16]

For example, it may be desirable to measure the energy usage on the


low voltage side of a distribution transformer that serves an
industrial customer even though the end-point customer actually
owns the transformer and is responsible for any transformer losses.
In this case, the utility billing point is actually the high voltage side of
the transformer. Using loss compensation, the meter on the low
voltage side of the transformer can actively adjust the energy
registration to account for the losses in the transformer.
The loss compensation functionality is available only on the following
meter configurations:
 A3 ALPHA meters that have the loss compensation key enabled

412
TM42-3060

o Form 35S
o Form 35A
o Form 9S
o Form 10A
o Form 36S
o Form 36A
o 2-element FT case
o 2-½ element FT case
o 3-element FT case
 A1800 ALPHA CT-connected meters that have the loss
compensation key enabled
o 2-element
o 3-element

Next: Calculating the percent correction values for


configuring the meter

CALCULATING THE PERCENT CORRECTION VALUES FOR


CONFIGURING THE METER
To configure the loss compensation feature of a meter, you must use
these values. These values are site specific and must be uniquely
determined for each loss compensation application.
Parameter Description
Iron watts correction
%LWFe
percentage
Copper watts correction
%LWCu
percentage
Iron VARs correction
%LVFe
percentage
Copper VARs correction
%LVCu
percentage
Meter current when power
Meter current transformer is operating at
maximum rating
Meter voltage when power
Meter voltage transformer is operating at
rated voltage

These values must be calculated on the basis of the power


transformer test report and, if the line losses are to be included, the
characteristics of the primary/secondary conductors at the specific
site in question. The transformer and line loss compensation topics
address these calculations.
Calculations of loss compensation parameters is dependent on the
location of the meter with respect to the power transformer. The
rated voltage and rated current used in the calculations must

413
Application notes

represent the values on the same side of the power transformer as


the meter is located.
 If the meter is located on the secondary side of the power
transformer, then the rated voltage and rated current used in the
calculations must be secondary values.
 If the meter is located on the primary side of the power
transformer, then the rated voltage and rated current used in the
calculations must be primary values.

GATHER DATA NECESSARY FOR CALCULATION OF LOSS


COMPENSATION PARAMETERS
The following information is necessary to calculate the loss
compensation configuration parameters.
Parameter Description
Rated kVA of power
KVArated
transformer
Primary line-to-line voltage of
Vpri L-L
the power transformer
Secondary line-to-line voltage
Vsec L-L
of power transformer
Full load watts of power
LWCu transformer (copper or winding
losses)
No load watts of power
LWFe transformer (iron or core
losses)
Percent excitation current of
%EXC
the power transformer
Percent impedance of the
%Z
power transformer
Current transformer ratio for
CTR instrumentation transformers
supplying current to the meter
Voltage transformer ratio for
VTR instrumentation transformers
supplying voltage to the meter
Number of meter elements
Elements (use 3 for all 2½ element
meters)

There may be one 3-phase transformer or a bank of three single


phase transformers. If there are three single phase transformers
then test data is needed for all three.

CALCULATE THE METER CONFIGURATION PARAMETERS

Step 1
Calculate the following quantities.
Parameter Description
Per phase VA rating of power
VAphase
transformer

414
TM42-3060

Rated secondary voltage of


Vsec rated
power transformer
Rated secondary current of
Isec rated
power transformer
Rated primary voltage of power
Vpri rated
transformer
Rated primary current of power
Ipri rated
transformer
No load watt loss of power
LWFe
transformer (loss wat iron)
Full load watt loss of power
LWCu
transformer (loss watt copper)
No load VA loss of power
LVAFe
transformer (Loss VA iron)
Full load VA loss of power
LVACu
transformer (loss VA copper)
No load VAR loss of power
LVFe
transformer (loss VAR iron)
Full load VAR loss of power
LVCu
transformer (loss VAR copper)

Item Equation
If bank of 3 transformers:

VAphase If one 3-phase transformer:

For 2-element, 3-wire delta applications:

Vsec rated For 3- (and 2½-) element, 4-wire wye

applications:
For 2-element, 3-wire delta applications:

Vpri rated For 3- (and 2½-) element, 4 wire wye

applications:

Isec rated
All applications:

Ipri rated
All applications:

Note: For a bank of three single phase transformers the below


calculations should be performed independently for each
transformer and then summed to obtain the total losses.
Parameter Equation
Take directly from power transformer test
LWFe
report

415
Application notes

Take directly from power transformer test


LWCu
report

LVAFe

LVACu

LVFe
LVCu

Step 2
If it is desired to compensate for line losses then calculate the Full
Load Watt Line Loss and the Full Load VAR Line Loss values (see
next section for details on line loss calculation).
Parameter Description
Total full load watt line loss
LiWTOT (line loss watt)
Total full load VAR line loss
LiVTOT
(line loss VAR)

Step 3
Calculate the Per Element % Correction Factors, the Meter Voltage,
and the Meter Current. These are the values that must be entered
into the loss compensation software to configure the meter properly.
 If the meter is on the primary side of the power transformer, then
Vrated = Vpri rated and Irated = Ipri rated
 If the meter is on the secondary side of the power transformer,
then Vrated = Vsec rated and Irated = Isec rated

Parameter Equation

%LWFe

%LWCu

%LVFe

%LVCu

Meter current

Meter voltage

416
TM42-3060

Previous: About transformer and line loss compensation


Next: Line loss calculations

LINE LOSS CALCULATIONS


Compensation for line losses may include primary losses, secondary
losses, or both depending on the application.

INPUT DATA NECESSARY TO CALCULATE LINE LOSSES


The following information is necessary to calculate the line losses.

Item Description
f Frequency
n Number of conductors
line length (units compatible
L
with conductor resistance)
Conductor resistance (Ω/mile
Ra or Ω/1000 feet or Ω/meter or
Ω/kilometer)
GMR (noteEither GMR or Xa is
required, but not both. The Geometric mean radius of the
available information phase conductors (ft or
determines which is used in meters)
the calculations.)
Xa (noteEither GMR or Xa is
Inductive reactance of the
required, but not both. The
conductor at 1 ft spacing
available information
(Ω/mile or Ω/1000 feet or
determines which is used in
Ω/meter or Ω/kilometer)
the calculations.)

Step 1
Calculate line resistance and line reactance
The equations below should be applied individually to the primary
and secondary conductors.
Item Description
RL Line resistance (Ω)
XL Line reactance (Ω)
Geometric mean distance
Deq between phase conductors (in
feet or meters)
Distance between phase A
Dab (Line 1) and phase B (Line 2)
(in feet or meters)
Distance between phase B
Dbc (Line 2) and phase C (Line 3)
(in feet or meters)
Distance between phase C
Dca (Line 3) and phase A (Line 1)
(in feet or meters)

417
Application notes

Item Equation
RL

Calculating the reactive component of the impedance is not as


straight forward as the resistance calculation, and the calculation
depends on the wiring configuration. The most common
configuration is one where the wires are unbundled and the spacing
between wires is uniform. Other types of wiring, such as bundled
conductors, will not be discussed in this document. Two equations
can be used to calculate line reactance. The choice of which
equation to use is based on the whether GMR or Xa is available.
Item Equation
If using GMR:

XL
If using Xa:

where:

step 2
Calculate the line losses
Item Description
Total full load line loss (line
LiWTOT
loss watt)
Total full load line loss (line
LiVTOT
loss VAR)
Primary line-to-line voltage of
Vpri L-L
power transformer
Secondary line-to-line voltage
Vsec L-L
of power transformer
Rated secondary current of
Isec rated
power transformer
Rated primary current of power
Ipri rated
transformer

Note: Vpri L-L, Vsec L-L, Ipri rated, and Isec rated are the same values as
used in Calculating the percent correction values for configuring
the meter.

When compensating for both transformer and line loss:


Item Equation
LiWsec

418
TM42-3060

LiVsec
LiWpri
LiVpri
LiWTOT
LiVTOT

Note: In the special case that you are compensating only for line
loss (no transformer losses), then the values for Ipri rated and Isec
rated must be directly specified by the user. Typically, these two
values will be inversely proportional to the rated secondary and
primary voltages of the power transformer. That is:

Step 3
Determine the compensation approach:
 If you are compensating for both transformer and line losses,
return to step 3 in Calculating the percent correction values for
configuring the meter, using the above calculated line losses to
help calculate the %LWCU and %LVCu values.
 If you are compensating only for line losses, use the following
equations to calculate the per element % correction factors, the
meter voltage, and the meter current.

 If the meter is on the primary side of the power transformer, Irated


= Ipri rated.
 If the meter is on the secondary side of the power transformer,
Irated = Isec rated.
 Vrated is the nominal voltage seen on the high side of the
instrument transformer supplying voltage to the meter.
Item Equation
%LWFe 0

%LWCu

%LVFe 0

%LVCu

Meter current

Meter voltage

419
Application notes

Previous: Calculating the percent correction values for


configuring the meter
Next: Calculation example

CALCULATION EXAMPLE
The following example can be used as a guideline. This is based on
the sample transformer data for loss compensation shown in chapter
10 of the Handbook for Electricity Metering (10th edition).
[Edison Electric Institute, Handbook for Electricity
Metering, 10th edition, Washington, DC: Edison
Electric Institute, 2002, Chapter 10, "Special
Metering," pp. 249 - 88]

Application notes:
 The application is a bank of three single-phase power
transformers.
 The metering occurs on the low (secondary) side of a power
trans-former, and losses will be added to the measured energy.
 There is a delta connection on the secondary of the power
transformer and thus a 2-element meter will be used to measure
the service.
 Losses are being compensated for the power transformer only
(no line losses).

INPUTS
Power
transf
ormer
data
(from Phase Phase Phase
transf A (Line B (Line C (Line
ormer 1) 2) 3)
manuf
acture
r)

KVArated 3333 3333 3333


11500 11500 11500
Vpri L-L
0 0 0
Vsec L-L 2520 2520 2520
LWFe 9650 9690 9340
LWCu 18935 18400 18692
%EXC 1.00 1.06 0.91

420
TM42-3060

%Z 8.16 8.03 8.12

Instrument
transformer
data Value

Item

CTR

VTR

Meter data
 Elements = 2

CALCULATIONS
Because the metering is on the secondary side of the power
transformer, all references to rated voltage and rated current refer to
the secondary rated values.
Item Equation

VAphase

Vrated

Irated

Meter voltage

Meter current

PHASE A. CALCULATIONS
Item Equation
LWFe 9650
LWCu 18935

LVAFe

421
Application notes

LVACu

LVFe

LVCu

PHASE B. CALCULATIONS
Item Equation
LWFe 9690
LWCu 18400

LVAFe

LVACu

LVFe

LVCu

PHASE C. CALCULATIONS
Item Equation
LWFe 9340
LWCu 18692

LVAFe

LVACu

422
TM42-3060

LVFe

LVCu

CALCULATIONS FROM ALL PHASES


Item Equation
LWFe 9650 + 9690 + 9340 = 28680
LWCu 18935 + 18400 + 18692 = 56027
LVFe 31902 + 33975 + 28856 = 94734
LVCu 271313 + 267007 + 269993 = 808313

Per the stated assumptions, there is no compensating for line losses:


 LiWTOT = 0
 LiVTOT = 0

PER ELEMENT PERCENT CORRECTION FACTORS


Item Equation

%LWFe

%LWCu

%LVFe

%LVCu

Meter current

423
Application notes

Meter voltage

SUMMARY OF CALCULATED VALUES


Item Value
Registration Add losses
Iron watts correction
0.2484
percentage
Copper watts correction
0.4853
percentage
Iron VARs correction
0.8205
percentage
Copper VARs correction
7.0009
percentage
Meter current 3.82
Meter voltage 126

Previous: Line loss calculations


Next: Internal meter calculations

INTERNAL METER CALCULATIONS


To understand the loss compensation calculations, it is first
necessary to understand a little bit about how the A3 ALPHA meter
engine operates. Internal to the meter engine Vrms and Irms are
measured independently on each phase every two line cycles. These
values are used to perform the normal energy calculations on each
phase every two line cycles. The individual phase measurements are
then summed. This drives an internal accumulator in the meter
engine that generates a pulse to the microcontroller when a
threshold level is reached. The threshold level at which a pulse is
generated is known as the meter Ke (energy per pulse). There are
separate calculations, separate accumulators and separate Ke
pulses generated for each measured energy quantity (for example,
kWh-delivered, kVARh-delivered).
When loss compensation is turned on, additional calculations are
performed. Every two line cycles on each phase, the Vrms and Irms
values used in the normal energy calculations are also used to
calculate a watt compensation value and a VAR compensation value.
The following equations indicate the compensation terms that are
calculated and applied to the normal energy measurements every
two line cycles.
For a 3-element meter, watts and VARs are compensated every two
line cycles according to the following equations:
Compensation Equation

424
TM42-3060

Watt

VAR

For a 2-element meter, watts and VARs are compensated every two
line cycles according to the following equations:
Compensation Equation

Watt

VAR

where:

Item Description
R Per element resistance
G Per element conductance
X Per element reactance
B Per element susceptance
Ix meas Per phase rms current
Vx meas Per phase rms voltage

Elster calculates R, G, X, and B using the following formulas and then


programs these vales into the meter:

Item Equation

The compensation terms will be either positive or negative depending


on whether losses are configured to be added or subtracted from the
energy measurements. So, the key difference on meters with loss
compensation is that every two line cycles on each phase, the
calculated Watt compensation value is summed with the normal
Watthour energy calculations. Similarly, the VAR compensation term
is summed per phase every two line cycles with the normal VARhour
energy calculations. From that point everything is essentially the
same (individual phases are then summed to drive an accumulator).

NOTE REGARDING TWO-ELEMENT METERS:

425
Application notes

Two-element ALPHA meters are unique in that they create an


artificial internal reference that is used to measure the phase
voltages. In the special case that phase C experiences a loss of
voltage while the meter remains powered (either from phase A or
from an auxiliary supply) the internal meter engine will still measure
a phase C voltage equal to one-half of the phase A voltage. In
applications where loss compensation is not applied this has no
impact on the measurement of energy because no power will be
drawn by the load on phase C. That is, phase C current equals zero
and so the net energy measured on phase C is accurately calculated
as zero. However, in the special case of a meter that is compensating
for transformer losses, the no-load compensation terms are based
solely on the measured voltage on each phase (see above formulas).
Therefore, on 2-element ALPHA meters with loss compensation
enabled, if phase C voltage is lost while the meter remains powered,
the no load compensation terms for phase C will be in error because
they will be calculated based on one-half the phase A voltage.

Previous: Calculation example


Next: Meter outputs affected by compensation

METER OUTPUTS AFFECTED BY COMPENSATION


When loss compensation is enabled, all of the following collected
data use the compensated values:
 all register billing data
 all pulse profile data
 all KYZ pulse outputs
 all test pulses (both in the LCD and on the LED)
Compensation does not affect instrumentation values or the meter
features that use instrumentation values. Regardless of the status of
loss compensation, all instrumentation values reflect the actual
measured values as seen at the meter terminals. For example, per
phase voltage values are not affected (whether displayed on the LCD
or reported in meter support software). Likewise PQM/TRueQ
functions and instrumentation profiling values are not affected when
compensation is active.

TESTING A METER WITH COMPENSATION


The LEDs on the meters always reflect the current measurement
algorithm in the meter engine. That is, if compensation is turned on
then the LEDs will indicate compensated energy. If compensation is
turned off then the LEDs will indicate uncompensated energy.
Because the LED always reflects the state of the compensation it
reduces the chance that a meter with active compensation is
accidentally installed unknowingly.

426
TM42-3060

It is possible to configure the meter to automatically turn off


compensation whenever the meter enters test mode. This may or
may not be desired depending on utility testing practices.
The Metercat also permits the loss compensation to be manually
turned off and turned on without altering the loss compensation
parameters configured in the meter.
Utilities may desire to calculate the expected test results of a
compensated meter and then test the meter with active
compensation to verify that the expected results are obtained.

Previous: Internal meter calculations

User ID assignments
For event log and history log entries, Metercat uses the following
user IDs to indicate who or what initiated the action. The User IDs are
based on the ANSI C12.18, C12.21, and C12.22 protocols.
User ID Name Notes
End device (meter)
0 Reserved
initiated the event
For example, a button
1 Manual operation
press
Reserved and always
Metercat administrator
2 associated with the
account
Metercat administrator
3 to 9999 (with Can be set in Account
exceptions as noted Metercat user ID Information or in User
below) management
Avoid using as a
33 Sensus Metercat user ID to
avoid an overlap
Avoid using as a
900 ILN1 option board Metercat user ID to
avoid an overlap
EnergyAxis
10000 Management System
(EA_MS)
For EACOMMS
REXUniversal comms
20100 internally generated
processor
events
Any REXUniversal
meter event generated
20101 EA_LAN from the EA_LAN (900
MHz local area
network)
Events generated on
20102 Cellular connection the meter from a
cellular connection
Events added to the
event log by the
20103 Wireless WIC
REXUniversal meter
Wireless WIC

427
Application notes

Events generated by
20104 ZigBee processor the meter's ZigBee
processor
For example, a
25000 EA_Tools
gatekeeper upgrade
Assigned by Elster.
Typically, it will be an
Elster option board or
57344 to 65535 Option boards an option board
developed by a third
party in an agreement
with Elster.
Elster ACB or WIC
57344
option board
Elster Lighting
58000
Intelligence module
60000 Itron 50ESS ERT
60100 Amron option board
60200 Sensus option board
Silver Spring Networks
60300
option board
Landis+Gyr option
60400
board
61000 Metrum option board
Nertec/Trilliant option
62000
board
Itron/SmartSynch
63000
option board
64044 Aclara option board
EKA Systems option
65000
board

428
Legal notices

Trademarks
Metercat, AlphaPlus, ALPHA, ALPHA Plus, REX, REX2, REXUniversal,
IP AxisLink, EnergyAxis are trademarks and/or registered trademarks
of Elster.
All other product names may be trademarks and/or registered
trademarks of their respective owners.

Copyright
No part of this software or documentation may be reproduced,
transmitted, processed, or recorded by any means or form, electronic
mechanical, photographic, translated to another language, or be
released to any third party without the express written consent of
Elster.
© 2016 by Elster. All rights reserved.

Generated
Last generated & updated: 07 September 2016 at 09:45

429
Glossary

A
adjusted Kh: Also called watt-hour constant. This Kh value can be changed and programmed
using Metercat.

C
current transformer ratio: CTR. The ratio of the primary current to the secondary current of a
current transformer. Example: 400 A to 5 A would have a CTR of 80.

D
demand overload: The demand overload can be used to inform a utility when an installation
is requiring more power than the service equipment was originally designed to
handle.
demand threshold: The present value of demand which, when reached, initiates a relay
closure or other programmed action.
demand-only meter: An A3D meter or any other meter type that has been programmed as a
demand meter. See also TOU meter.

E
EA_NIC: EnergyAxis network interface card
EEPROM: Electrically erasable programmable read only memory. Nonvolitale storage.
EEPROM retains all stored data even when power is removed from the circuit.

F
factory Ke: This Ke value is set at the factory. It cannot be changed.
factory Kh: This Kh value is set at the factory. It cannot be changed.

H
HAN: home area network
hexadecimal: A base-16 numbering system, supporting the characters 0 to 9 and A to F.

431
Glossary

K
Ke: The smallest discrete amount of energy available within the meter. It is the value of a
single pulse used between the meter engine and the microcontroller.
Kh: A meter constant representing the watthours per output pulse on the optical port.
Historically, Kh represents the energy equivalent to one revolution of an
electromechical meter (called the P/R). Kh = P/R × Ke.
kilo units: The measured quantity in kilo units. For example, if the meter is programmed for
VA demand, then kilo units would be kVA. If the meter is programmed for VAR energy,
then the value would be kVARh.

M
meter family: The main product line of Elster's meters or devices. Examples of meter families
include: A3 ALPHA meter, A1800 ALPHA meter, REX2 meter, REXUniversal meter, IP
AxisLink router. A meter family may have many different meter types.
meter type: Different meters within a meter family may have different capabilities, for
example, some meter types may measure demand only, while other meter types may
measure real/alternate energy quantities on a time of use basis.

R
register multiplier: Called external display multiplier in the meter technical manuals. Used
when the transformer ratio is larger than can be stored in the meter. When using a
register multiplier, display quantities read form the meter LCD must be manually
multiplied by this value to yield proper readings.
rms: root mean square

T
TOU meter: An A3T, A3K, A3R, A3Q, or A1800 ALPHA meter that is programmed to record
energy usage and demand on a time of use basis. See also demand-only meter.
transformer factor: The combined factor of the current transformer ratio multiplied by the
voltage transformer ratio.

U
UDP: User Datagram Protocol. UDP is suitable when communications does not require a
handshake or delivery verification.
UNC path names: Universal Naming Convention. For example: \\server\folder\file.txt
user defined table: Offers specific data retrieval options for meters. User defined table
configuration may be requested at the time of purchase, adn the specific
configuration is then programmed at the factory. A head-end system or other device

432
TM42-3060

can then be configured to retrieve the user defined table information from the meter
instead of individual table reads to reduce total communication time.
utility ID: The utility ID is the same for all devices within the same network.

V
voltage transformer ratio: VTR. The ratio of primary voltage to secondary voltage of a
transformer. Example: 12000 V to 120 V would have a VTR of 100.

W
WIC: WAN interface card

433
Elster Solutions © 2016 by Elster. All rights reserved.
208 S Rogers Lane Information herein is subject to change without
Raleigh, NC 27610-2144 notice. Product specifications cited may change.
T +1 800 257 9754 (US sales) Contact your Elster representative for the most
T +1 800 338 5251 (US support) current product information.
T +1 905 634 4895 (Canada) Produced in the United States.
www.elster.com

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy