Landis Gyr Technology ER1R1S6 5252 Ampy Module User Manual 14 0210 Exhibit Cover
Landis+Gyr Technology, Inc. 5252 Ampy Module 14 0210 Exhibit Cover
Manual
Certification Exhibit FCC ID: R7PER1R1S6 FCC Rule Part: 15.247 ACS Project Number: 14-0210 Manufacturer: Landis+Gyr Technology, Inc. Model: 5252 Comm Module Manual 5015 B.U. Bowman Drive Buford, GA 30518 USA Voice: 770-831-8048 Fax: 770-831-8598 Draft 7.30.14 Gridstream RF Enhanced Series IV AMPY 5252B Endpoint User Guide Publication: 98-1745 Rev AA LANDIS+GYR CONFIDENTIAL INFORMATION Draft 7.30.14 Limitation on Warranties and Liability Information in this document is subject to change without notice. This manual or any part of it thereof may not be reproduced in any form unless permitted by contract or by written permission of Landis+Gyr. In no event will Landis+Gyr be liable for any incidental, indirect, special, or consequential damages (including lost profits) arising out of or relating to this publication or the information contained in it, even if Landis+Gyr has been advised, knew, or should have known of the possibility of such damages. © 2014 Landis+Gyr, Inc. All Rights Reserved Gridstream RF Enhanced Series IV AMPY 5252B Endpoint User Guide Publication: 98-1745 Rev AA Revision History Modification Date 07/30/2014 Revision AA Description Pending © 2014 Landis+Gyr • All rights reserved. Author Kim Utesch Draft 7.30.14 Table of Contents Chapter 1: Endpoint Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Enhanced Series IV AMPY 5252B Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Endpoint Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Features and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Communicating via Meter to Endpoint Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Auto-Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Retrieving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Demand Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Power Outage/Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Supporting Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Downloading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Encrypting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Configuration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Theory of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 FCC Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 FCC Class B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 RF Exposure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 2: Command Center Deployment/Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Auto Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Endpoint Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Meter Manufacturer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Import Installation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Import Information File CSV Format requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Tracking and Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Deployment Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 RF Installation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Endpoint Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Packet Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Alarm Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Meter Configuration Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Add Meters to a Meter Configuration Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Chapter 3: Using Endpoint Testing Manager (ETM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 How To Use ETM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Access to Endpoint Test Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting Up Access to the Command Center Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Adding a New Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Selecting an alternate existing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Modify an existing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 User Guide 98-1745 Rev AA Table of Contents Draft 7.30.14 Landis+Gyr Delete an existing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 Add additional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 After Login: Setup Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Certificate Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Request MAT Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 ETM Sign In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Using the Bar-code Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Navigating the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Configuring a New Gridstream IWR Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Meter Shop Best Practices Use Case - Proper IWR Configuration . . . . . . . . . . . . . . . . . . . . 37 Authentication Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Connecting to a Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Connection Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Baud Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Connecting to an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Head End Radio Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Device Test Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 High Speed (115200 bps) Enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Multiple Meter Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Enabling Multiple Meter Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Editing Multiple Meter Test Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Firmware Download Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Battery End Point Firmware Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Module Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Optical Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Reporting Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Demand Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Enabling Demand Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Demand Reset Lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Performing a Demand Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Command Scheduler Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Event Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Command Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Universal Event Log Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Service Limiting Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Service Limiting Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Read Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Service Limiting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Create a Service Limiting Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Send an existing Service Limiting Program to an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . 66 Groups Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Chapter 4: Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Enhanced Series IV AMPY 5252B Specs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 98-1745 Rev AA User Guide Draft 7.30.14 Endpoint Overview Enhanced Series IV AMPY 5252B Endpoint Figure 1 - 1. Gridstream RF Enhanced Series IV AMPY 5252B Meter and Module Endpoint Usage The Gridstream RF Enhanced Series IV AMPY 5252B endpoint will be used for commercial and industrial metering applications. The communication module requires professional installation by qualified personnel. User Guide 98-1745 Rev AA Chapter 1 - Endpoint Overview Draft 7.30.14 Landis+Gyr Required Software To work with the endpoint, you need one of the following software tools: • Command Center version 6.2 or later. • RadioShop version x.x or later. • Endpoint Testing Manager version x.x or later. Labels The endpoint includes the following label. Figure 1 - 2. Label Identification 1. LAN ID: XXXXXXXX NOTE: The LAN ID is a unique identifier for each endpoint. It always displays in hex. Landis+Gyr provides the LAN address. You cannot change the LAN ID of a radio. 2. Model: 5252 COMM Module 3. Meter FCC ID: U3R-5252-01 TYPE - 5252B 4. Module FCC ID: R7PER1R1S6 Features and Functions Using the AMPY 5252B Meter with the Gridstream RF Enhanced Communication Module, you can: • Integrate the endpoint into the 240V, Form 25 AMPY 5252B meter. • Communicate via serial connection between the endpoint and the meter through the meter's provided interface. • Support all levels of meter passwords. • Download radio firmware. Communicating via Meter to Endpoint Connection The serial connection is a 26-pin header that contains: 98-1745 Rev AA User Guide Draft 7.30.14 Landis+Gyr Chapter 1 - Endpoint Overview • Full duplex serial connection. The baud rate is 9600, 8 bits, 1 stop bit, no hardware handshaking. • Power fail indication signal from the meter that tells the endpoint to disconnect from drawing power from the meter. • DC power line which supplies power to the module from the meter. Auto-Registration Endpoint firmware version 9.04 or later and module Device Control Word (DCW) x.xx or later is required for auto-registration. After the meter/endpoint is installed in the field it will automatically register with the Head End System. No special tools are needed during installation as the normal Utility meter swap process can be utilized. The meter automatically sends in the registration information containing items on how the meter/ communication module is configured so the host can properly interpret the incoming data. Some of the items contained in this are as follows: • Default Gridstream RF Collector destination • Reporting interval for Register Data • Reporting interval for Interval Data • Meter's AMR-level security password • Time Synchronization parameters • GMT offset • Periodic Register Data reporting • Periodic LP Data reporting • Meter configuration information Once this information has been sent the meter/communication module starts collecting and sending based on the default configuration loaded during manufacturing. Retrieving Data The communication module performs data retrieval from the meter on request (ORR) or autonomously (periodically reported). Availability of the following features depends on meter configuration. On Request Reads (ORR) available with this communication module are: • Register Data which includes consumption, demand and TOU values • Load Profile or Interval Data • Revenue Integrity Services which includes instantaneous measurements related to line voltage, current and phase angle Availability of the following features depends on meter configuration. Options for periodically reported data with this module include: • User Guide Register Data & Status Flags which includes consumption, demand, TOU values and meter status. 98-1745 Rev AA Chapter 1 - Endpoint Overview • Draft 7.30.14 Landis+Gyr Load Profile or Interval Data & Status Flags (Standard Tables 64 & 3) which includes interval data and meter status. Demand Reset When Command Center delivers a Demand Reset command, the communication module passes the command to the meter, which performs the Demand Reset on the meter. The meter/communication module then passes the previous demand data captured by the meter to Command Center for processing. Time Synchronization Time synchronization is the process of keeping the meter time synchronized with the Gridstream RF network time within a configurable limit. The communication module automatically keeps its time synchronized with the Gridstream RF network via periodic background process. The communication module reads the meter date/clock table periodically, determined by its configuration. If the time drift between the meter and communication module exceeds the configured threshold, it sends a time synchronization alert message to Command Center. Command Center schedules a time change event for the meter and sends it to the communication module. The time of the change is determined such that the meter’s data integrity is maintained. At the scheduled time, the communication module executes the standard procedure to change date/time on the meter. Power Outage/Restoration When an outage occurs, the meter uses an early power failure signal to alert the communication module to disconnect from the meter's power immediately. The communication module saves critical module data to non-volatile memory and creates and sends a power outage message. This message includes the following information: • LAN ID • Outage time • Reboot count. The communication module sends the message, then assists with routing other packets until the back-up energy source can no longer keep the radio alive. The time that this energy source is available varies with several factors, including amount of data packets being routed, environmental conditions and age of meter/communication module. Generally, a hold-up time of ~120 seconds is typical. At restoration, the communication module first acquires network connectivity. With network communications restored, the communication module sends a power restoration message that includes details such as: • LAN ID • Outage time • Restoration time • Reboot count. The communications module stores a history of up to the last five power outage and restoration event pairs. Command Center can request this data. 98-1745 Rev AA User Guide Draft 7.30.14 Landis+Gyr Chapter 1 - Endpoint Overview Supporting Passwords The meter/communication module supports passwords provided by the utility. See publication 981055 Gridstream 2-way Endpoint Testing Manager User Guide for information regarding loading password into module. Downloading Firmware Communications module firmware can be upgraded via Command Center or ETM. Encrypting Data The Gridstream RF Network currently supports use of one encryption key per network. If you enable the Gridstream RF Enhanced with encryption, Command Center must have a matching encryption key. Configuration Tables The Gridstream RF Endpoint Configuration structure passes the data to configure the endpoint. It is used for both C&I and Residential applications. This table is currently 55 bytes long. It contains information necessary to configure several services on the endpoint, such as firmware reads, autonomous data return configuration. The endpoint receives the packet, and using the data, configures its own operation. The host maintains a record of the endpoint’s configuration. User Guide Item Other Packet Contents Identifies which elements in this packet are set. Elements that are not set are ignored. There still must be a place in the packet for it, though. Config Byte 1 Not Used Config Byte 2 Not Used Config Byte 3 Not Used Config Byte 4 Not Used Config Byte 5 Not Used Reporting Interval LP In Minutes. Pump Period Register In Minutes. Pump Period RIS In minutes. The period for the RIS/Vector/Voltage data pump. Pump Period Status In minutes. The period for the Device Status (SO3, typically) data pump Pump Period Snap Read Snap Reads will be delivered at a pseudo-random time, which will occur in the first X hours of each day. X is the value that is provided here. It will default to 2. The process is: this value, which is in hours, will be converted to minutes. The LAN ID will be mod-ed with this minute value, and the result will be the minute of the day that the self read is transmitted. User ID 2 byte User ID used while running ANSI Logon Service 98-1745 Rev AA Chapter 1 - Endpoint Overview Draft 7.30.14 Landis+Gyr Item Other Logon User 10 byte User Name that is used while running the ANSI Logon Service Security Password The full 20 bytes are required. Sustained Outage Duration Defines the number of seconds after which an outage will be classified as sustained. If less than this amount, the outage is momentary. A value of zero will cause all outages to be considered "sustained". Max Meter Time Drift The number of seconds that the meter clock can drift from the radio clock, after which an alarm is triggered. Meter Time Read Period The number of seconds that the meter clock can drift from the radio clock, after which an alarm is triggered. GMT Offset The GMT Offset in 15 minute increments. Signed. Theory of Operation The Gridstream RF Enhanced Series IV AMPY 5252B module is an electric endpoint with 900MHz Gridstream communications on a single PCB. This product will be integrated into the Ampy 5252 meter. The following figure shows the high-level block diagram of the module. Each functional block is described in the following sections. Figure 1 - 3. Block Diagram FCC Compliance FCC Class B This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: 10 98-1745 Rev AA User Guide Draft 7.30.14 Landis+Gyr Chapter 1 - Endpoint Overview 1. This device may not cause harmful interference, and 2. This device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the Instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: • Reorient or relocate the receiving antenna. • Increase the separation between the equipment and receiver. • Consult Landis+Gyr or an experienced radio technician for help WARNING: Changes or modifications to this device not expressly approved by Landis+Gyr could void the user’s authority to operate the equipment. RF Exposure This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20 cm between the radiator and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. User Guide 98-1745 Rev AA 11 Draft 7.30.14 Draft 7.30.14 Command Center Deployment/Configuration Deployment Auto Registration Landis+Gyr RF radio is Plug & Play; meters equipped with Landis+Gyr endpoints arrive from the factory in operational mode, ready to be installed at a service location. Along with the meters, a Meter Manufacturer File is provided to the utility. This file contains meter number/serial number combinations; the file must be uploaded into Command Center prior to installation of endpoints in the field. A meter installer installs the endpoint at the service location. Once installed, the endpoint will begin the following auto-registration process: 1. The endpoint listens for RF traffic and evaluates its neighbors, searching for the best possible path to the collector. The best path is the one with the fewest hops to the Collector and through an endpoint with the highest Receive Signal Strength Indicator (RSSI) (RSSI is the receive signal strength from the node. It is a rough indicator of how strong the signal is from the radio). 2. Having identified the best path, the endpoint will transmit the following two packets: • RF Registration Packet: The RF Registration Packet identifies for the Collector the return path to the endpoint. This is achieved by each intermediary endpoint adding its LAN address to the endpoint’s RF Registration Packet as it travels to the Collector. Once the RF Registration Packet is received, the endpoint will transition to Discovered in Command Center. The RF Registration will continue to be sent until the SetWAN command is received from Command Center. • Init Push: The Init Push packet contains configuration information about the meter, that allows Command Center to understand the configuration of the meter. The Init Push is transmitted until the SetWAN command is received from Command Center. 3. Once the RF Registration Packet and Init Push are received, Command Center will validate the configuration and, if validated, begin accepting readings from the endpoint. The endpoint will remain in Discovered status until the SetWAN command is received by the endpoint. 4. The SetWAN command is issued to the endpoint when Command Center receives latitude and longitude information AND the endpoint’s closest neighbor has a WAN address. The SetWAN command provides the endpoint with its WAN address. The WAN address is the radio’s physical location (Latitude and Longitude) expressed in degree, minutes and seconds. The SetWAN command achieves two way communication with the endpoint. The SetWAN tells the endpoint that we have received your configuration information and it is OK to stop sending it in. User Guide 98-1745 Rev AA 13 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr NOTE: If Installation Data is received before an Init Push has been received, the installation record will be stored awaiting the Init Push from the device. Endpoint Status Endpoints will move from one status to another during the deployment process. The following are various endpoint statuses: • Installed. Endpoints in the Installed status have been deployed in the field, but Command Center has not received the RF Registration packet. • Discovered. Endpoints in the Discovered status have transmitted an RF Registration Packet. The RF Registration Packet identifies for the Collector the return path to the endpoint. This is achieved by each intermediary endpoint adding its LAN address to the endpoint’s RF Registration Packet as it travels to the Collector. • Normal. Endpoints in the Normal status have transmitted an Init Push packet containing configuration information AND have acknowledged a SetWAN command from Command Center. The SetWAN command provides the endpoint with its WAN address. The WAN address is the radio’s physical location (Latitude and Longitude) expressed in degree, minutes and seconds. • Lost. Endpoints in the Lost status have reported an outage event. When the endpoint loses power, it will transmit a “Power Outage Event” to Command Center. Once power has been restored, the endpoint transmits a “Power Restore Event”. The endpoint will then transition back to Normal status. • Configure. Endpoints in the Configure status are endpoints that have been recently added to a new configuration group and have not yet confirmed the receipt of configuration commands. • Failed. Endpoints and/or meters in the Failed status have failed a re-configuration attempt or have failed a work flow process. Work flow processing will determine if configuration changes such as time zone updates, reconfiguring of endpoints, meter change programs have been successful. Endpoints must be manually removed from the Failed status, generally by attempting the work process again. • Archive. Endpoints in Archive status are no longer in use within the Mesh System, for example, damaged endpoints. Endpoints must be manually entered into Archive status. • Inventory. Endpoints in Inventory status have not yet been deployed in the field. These may be recently purchased meters or meters that have been removed from the field and are awaiting redeployment. Meter Manufacturer Data The Meter Manufacturer Data screen allows the user to import an XML or CSV file supplied by the meter manufacturer so the utility does not have to key in meters and endpoints by hand. 1. Click Operations > Import > Meter Manufacturer Data to display the Import Meter Manufacturer Data screen. 14 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 1. Import Meter Manufacturer Data 2. Click the Browse button to navigate to, and select, a file that was sent by the meter manufacturer. 3. Click the Save button to import the file into the database. The Meter Manufacturer Data Import (Upload Complete) window will appear displaying the Error Summary (if applicable) and Successful Entries. Figure 2 - 2. Upload Complete Window NOTE: Any entries under Error Summary will be red text. The usual reason for an entry under Errors is that the endpoint already exists in the system. If file parsing errors or other file-related errors occur, contact the meter manufacturer that supplied the file. 4. Successful entries will be added to inventory and will be displayed on the dashboard as Inventory status. Import Installation File Meter deployment details can be imported by use of an Installation File provided by the installer. Following is the procedure for importing the installation file. 1. Click Operations > Import > Import Installation File to display the Import Installation File screen. User Guide 98-1745 Rev AA 15 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 3. Import Installation File Screen 2. Enter the Path to the file. ...or... 3. Click the Browse button to navigate to, and select, a file containing the endpoint information. 4. Click OK to upload the file. The information imported via the Installation File: Table 2-1. Installation File Fields Data Format Format/Description User ID* AlphaNum (30) Login assigned by the utility for the installer. Utility may elect to use “1” for System usage. Installation Date* Date MM/DD/YYYY 12/26/2009 Actual date the meter was installed. This date is used in various Command Center reports to track deployment statistics. Installation Time* Time HHMM AM/PM 11:12 AM Actual time the meter was installed. This date is used in various Command Center Reports to track deployment statistics. Change Out meter number AlphaNum (20) The meter being replaced with a new meter. Meter change out information is displayed in the notes section of the endpoint information screen. Change Out meter kWh AlphaNum (20) The kWh reading on the meter being replaced Meter change out kWh information is displayed in the notes section of the endpoint information screen. Variable Character. Installed Meter Number* AlphaNum (20) Meter number of the new meter being installed. This meter must exist in Command Center prior to importing the Import Installation File. Must parse to Decimal format. Installed Endpoint Serial Number* Decimal (9) The serial number of the new meter being installed. Note: Endpoint serial numbers must be converted from Hex to Decimal. Installed Meter kWh Decimal (9) Initial reading of the new meter. Service Latitude Decimal (12,8) GPS latitude. * Indicates a required field. 16 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Table 2-1. Installation File Fields (Continued) Data Format Format/Description Service Longitude Decimal (12,8) GPS longitude. Service Location AlphaNum (100) Meter service location. Service Time Zone See formatting below. The service time zone may be entered to specify the correct time zone for the service location. * Indicates a required field. Import Information File CSV Format requirements CAUTION: Required fields are UserID, Installed Date, InstalledTime, InstalledMeterNo, and InstalledEndpointSN. If these fields are not populated, the file will not be processed. Service Location is required if the Latitude and Longitude fields are populated. Command Center will ignore the latitude and longitude values if Service Location is not provided. The Import Installation File window provides a CSV template link. Click this link to view the format requirements for the file. This template can be saved to a network location or local machine and provided to the installer. The Installation file must be of the following format: • The first line must be a header. • A comma is required to separate each item even if no data exists. • A Service location is required if the service latitude and longitude are provided. Time Zone In order to report reading time correctly, the endpoint must be programmed with the appropriate time zone; this is achieved by sending commands to the endpoint that indicates the time zone in which the endpoint is installed and whether Daylight Savings Time (DST) is observed in the given time zone. The Installation File should include the endpoint time zone. Clicking the Time Zone List link will open a document that displays a list of valid time zone designations by country. Figure 2 - 4. Time Zones User Guide 98-1745 Rev AA 17 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Tracking and Deployment Deployment Status Deployment Status enables users to monitor the find process when endpoints are being deployed on a system. 1. Click Network > Deployment Status to display the Deployment Status Report screen. Figure 2 - 5. RF Deployment Status Screen 2. Choose the Selection Criteria: A. All ...or... B. Collector. Select the desired collector from the drop-down menu. 3. Select a Date Range: A. Start Date. Click the calendar icon, and then click on the desired start date. B. End Date. Click the calendar icon and then click the desired end date. 4. Click the OK button to display the RF Deployment Status Report. Figure 2 - 6. RF Deployment Status Report The RF Deployment Status Report displays a graph representing 14 days of installation statistics and a chart. Time periods longer than 14 days may be selected, but will not be presented on the graph due 18 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr to space limitations. By clicking on a specific date, each endpoint registering that day displays installation, registered, normal and reading status for this date. Information on the report is updated as the information is received by Command Center on a rolling seven day basis. Installation information is populated from the RF Installation File Import process. Registered and Normal status updates are based on receipt of the two registration requests from the endpoints. Readings are based on the first reading received from the endpoint. Average deployment time is based on the time it takes to go from installed to normal. 5. Click on the Date link to display the Gridstream Meters Deployed By Day report. Figure 2 - 7. RF Meters Deployed by Day RF Installation Status The RF Installation Status Report is intended to be used by utilities during mass deployment. It can be used as an installation tool to determine how many meters have been installed over a specified time frame and of those meters how many have been discovered, how many have moved to normal status, how many are sending readings, and how many have sent readings in the past 24 hours. Following is the procedure for viewing the RF Installation Status report: 1. From Command Center, select Network > RF Installation Status. The RF Installation Status window will open. Figure 2 - 8. RF Installation Status 2. Selection Criteria. Select All to view results for all collectors in the system ...or... Select the desired collector from the drop down box to view results for only that collector. 3. Date Range. Enter a Start Date and End Date. Select the Calendar icon to view a calendar and make date selections if needed. 4. Click OK. The RF Installation Status report will be displayed, shown in Figure 2 - 9. User Guide 98-1745 Rev AA 19 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 9. RF Installation Status Report The following information is displayed in the report: • Day. This number will increment for each day the used has selected to display. • Date. This will display the dates selected in generation of the report. Click the date link to view a list of all meters deployed on the selected date. • Daily Installed. This will display the number of endpoints installed for that particular day. The daily installed data is imported into Command Center via the Installation File. • Discovered. Of the total number of meters installed on the summary date, the total number of those that have transitioned into a Discovered state and the percentage (Discovered meters/Installed meters). • Normal. Of the number of meters installed on the summary date, the total of those meters that have transitioned to a normal state at that point in time and the percentage (Normal meters/Installed meters). • Readings. Of the total number of meters installed on that day, the number of those meters that have sent in a billable reading packet, and the percentage (meters that have sent a billable reading packet/total meters installed on that day). • Readings past 24 Hours. Of the meters that were installed on that day, the total number of meters that sent in a billable readings packet in the last 24 hours (from the point the report was generated) and the percentage (meters that sent in a billable readings packet in the last 24 hours/total meters installed on that day). • Cumulative installed. The total number of meters that have been installed up to that date. • Normal. The total cumulative number of meters that have transitioned to Normal status up to that date. The color-coded bar graph displays the following deployment information: 20 • Cumulative number of meters installed for each date (Grey). • Current number of meters that have transitioned to Normal status (Green). 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr • Number of installed meters that have sent in a billable reading in the last 24 hours (Blue). Endpoint Configuration Packet Definitions Creating a packet definition is necessary to reconfigure the packet payload of an endpoint. Packet definitions can contain several different user-configurable data elements. NOTE: RF endpoints allow a user to return up to 6 registers. However, the more registers returned, the greater the strain on the network. 1. Click Setup > Packet Definitions > RF Residential The Packet Definitions screen will be displayed. Figure 2 - 10. Packet Definitions Screen 2. In the Packet Definitions screen click the New button to display the Packet Definition window. User Guide 98-1745 Rev AA 21 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 11. The Packet Definition Window 3. Enter a name in the Packet Name field. The name should be unique to the organization. 4. Click the Edit Description link to enter any desired notes for the packet definition. If any notes were entered, click the OK button to save them. 5. Select a Packet Type from the drop-down. • On Demand. Used for RF Endpoints. • Daily Packet Type. Used for PLC Endpoints 6. Select the Meter Type from the drop-down. 7. Select the desired data options from the Available Data Options window on the left side of the screen. To view a description of each available data option, click once on the data element. A description of the data element will be displayed in the yellow shaded box in the lower-center area of the screen. NOTE: The available data options vary depending on the type of endpoint. 8. Click the right pointing arrow to move the data option to the Selected Data window. As you select data options, monitor the Packet Capacity gauge on the right of the screen. Each selection will add to the percentage total. If your selections exceed 100 percent, a message will be displayed when you click the Save button indicating that packet capacity must be 100% or less and can contain six or fewer data items. You can remove selections from the Selected Data window by clicking to highlight the selection and then click the left pointing arrow to remove the selection. 9. After selecting all of the desired data options, click the Save button to save the new packet definition. 22 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Alarm Definitions Alarm Definitions determine what type of response the given Events will trigger, including Dashboard Alerts and Email Alerts. Alarm Definitions must be created prior to Meter Configuration Groups in order to be programmed to a module. 1. Click Setup > Alarm Definitions and select the appropriate endpoint type to display the Alarm Definitions screen. Figure 2 - 12. Alarm Definitions screen 2. Click the New button to display the Alarm Definition screen. Figure 2 - 13. Alarm Definition screen 3. Enter an Alarm Definition name in the Name field. 4. Choose the desired setting for each event. See below for setting descriptions. Available Settings Result Disabled Log Only Advisory Alarm Logged in module Available via request Event is: Included in next Transmitted immediately Flagged on Dashboard Included in E-mail Alerts NOTE: The default Alarm Definition settings represent the recommendation of Landis+Gyr. 5. Click the Save button. An Alarm Definition can only be edited if it is not already part of an existing Configuration Group. User Guide 98-1745 Rev AA 23 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Meter Configuration Groups A Configuration Group is a type of Command Addressing Group. A meter can be a member of only one configuration group. All members of a configuration group must be assigned the same configuration settings. Configuration groups are used to drive group-based reconfigurations for multiple endpoints. Each endpoint type is manufactured with a default configuration group. The data transmitted by an RF module, how frequently the data is sent, and how the module responds to conditions in the field, is dictated by the endpoint’s Configuration Group. An RF Endpoint configuration consists of the following: • Packet Definitions that are built for various data elements to be captured by the endpoint. • Alarm Definitions that establish the priority associated with events that occur in the RF endpoints. • RF Network Settings that establish the outage wait and time synchronization settings. • A schedule that includes the commands and packet definitions, along with time settings and frequency settings associated with data transmission, that are stored in the endpoint. NOTE: During the Auto-registration process, the module transmits an Init Push packet which indicates its configuration. This enables Command Center to associate the endpoint with the appropriate configuration group. If the configuration transmitted does not match an existing configuration in Command Center, a new configuration group may be auto-generated to which the endpoint will be assigned. For this process to occur, the Auto Generate Meter Configuration Groups setting must be enabled in System Settings. 1. Click Setup > Groups > Meter Configuration Groups and select the endpoint type. The Configuration Group screen will be displayed. Figure 2 - 14. Configuration Groups Window If you wish to view the details of an existing configuration group, perform the following steps. A. In the Configuration Group window click the View Meters icon for the Configuration Group you want to view to display the Group Summary window. 24 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 15. Group Summary Window The group membership list window displays the following categories: • Status. Status is the current status of the meter. • Total Meters. Displays the total number of meters in each status. B. Click any of the meter number links to view the Endpoint Properties window for the selected meter. 2. In the Configuration Groups window click the New button to display the Configuration Group Properties window. Figure 2 - 16. Configuration Group Properties Window 3. Enter a Group Name. The name must be unique within the organization. 4. Enter any desired Group Notes. 5. To set up Scheduled Commands use the following steps: A. Select the desired packet definition from the Command drop-down. B. Select the Time at which the reading will be taken from the meter. Adjust the time by clicking on either the hours, minutes, or AM/PM and then using the up or down arrow. C. Select the Frequency with which the reading will be taken from the meter. If either Every n minutes or Every n hours is selected, an additional field, N, will be displayed. Figure 2 - 17. Frequency Interval User Guide 98-1745 Rev AA 25 Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration • Landis+Gyr Select the desired interval from the Frequency drop-down. D. Click the Schedule Command icon to add the command to the Scheduled Commands list. Figure 2 - 18. Scheduled Commands E. (Gridstream endpoints only) Select the Delayed check-box for a command. 6. Repeat step 5 for any additional commands. 7. Select the Endpoint Transmit Interval from the drop-down. This setting determines how often the endpoint will transfer its readings to Command Center. 8. Select the appropriate RF Network Settings from the drop-down. Outage Wait Value* LG RF Commercial Configuration A LG AU Residential Network Configuration A RF Residential Configuration A Hunt RFS Gas Configuration Hunt RFS S4 Configuration A Default RF Collector Configuration Parameter Hunt RFS Residential Configuration A Table 2-2. RF Network Settings Parameters 30 Tamper Threshold** 10 30 10 Time Synchronization (X, Y)† 1,1 20, 60 20, 60 20, 60 20, 360 20, 60 20, 1 *Outage Wait Value The length of time (in seconds) that an endpoint will wait during a power outage situation before sending an outage notification to Command Center. **Tamper Threshold The number of reverse pulses of -kWh an endpoint must see within an interval before triggering a "Tamper Alert". †Time Synchronization The number of seconds that the meter time may drift before an automated time synchronization must be performed (X), or an alert must be generated and sent to Command Center (Y). 9. Select an RF Alarm Definition from the drop-down. 10. Click the Save button to save the new configuration group. Add Meters to a Meter Configuration Group Adding meters to a configuration group initiates the configuration process. 1. Click Setup > Groups > Meter Configuration Groups and select the endpoint type. The Configuration Group screen will be displayed. 26 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 2 - Command Center Deployment/Configuration Landis+Gyr Figure 2 - 19. Configuration Group Window 2. Click the Add Meters icon for the Configuration Group to which you want to add meters in order to display the Add Meters to Group window. Figure 2 - 20. Add Meters to Group Window 3. Click the Meter(s) radio button and enter individual meter numbers separated by spaces, commas, or semi-colons. ...or... 4. Click the Meter File radio button and then the Browse button to browse for a .csv file containing all the necessary meter numbers. 5. Click the Add button and then the Exit button to save the additions. After clicking the Add button, the user will receive feedback on how many meter numbers were successfully and/or unsuccessfully added. The reason for an unsuccessful message is that the meter number does not exist. User Guide NOTE: If a meter is already in a configuration group, the meter will be removed from the original and added to the new configuration group. 98-1745 Rev AA 27 Draft 7.30.14 Draft 7.30.14 Using Endpoint Testing Manager (ETM) How To Use ETM Endpoint Testing Manager (ETM) software provides the user with the ability to verify accurate module-to-meter, meter-to-module, module-to-network, and network-to-module communications. This chapter provides detailed instructions for navigating the software. Access to Endpoint Test Manager With the release of Command Center 5.0, ETM users must be authenticated into Command Center prior to accessing the ETM application and communicating with devices in the network. The designated Security Administrator for the utility is responsible for configuring the connection to the Command Center server, and for providing log in credentials (including user names and passwords) for those who will require access to the software. Setting Up Access to the Command Center Server Before launching the ETM software, a link to the Command Center server must be created. Follow the steps below to create the link to the Command Center server. • Launch ETM software. The ETM Sign in screen will open. On an initial launch of ETM, the ETM user must be authenticated with the Command Center server. The Command Center server connection places an authentication token on the user’s computer. This token is valid for a time specified by the Command Center Administrator. On succeeding launches, the Server Name field may display Offline, and may display Offline during future logins. Users may login to ETM without Command Center server connection, as long as their authentication token is valid. Figure 3 - 1. Endpoint Testing Manager - Sign In User Guide 98-1745 Rev AA 29 Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) • Landis+Gyr If this launch of ETM is not connected to a server, click the Select a new server link. The Server List will appear. Figure 3 - 2. Server List • Click the name of the desired server in the Server column to highlight it. • Click Select. The Server List window will close and the selected server will be displayed on the ETM log in screen. Adding a New Server Click Add on the Server List. The New Server window will open. Figure 3 - 3. Endpoint Testing Manager - New Server • Server Nickname: Enter a user-defined name for this server. • Server Location: Enter the physical location of the server. • Server FQDN: Enter the fully qualified domain name for the server. (see example in the New Server display). • Make this my default Authentication Server. Enable this setting to connect to this server each time this instance of ETM starts. • Click Submit to add the new server. Selecting an alternate existing server An ETM instance may have multiple servers associated to it. When ETM is first started, the server that has been selected by default will be displayed on the log in screen. The user may choose a different server, if necessary. 30 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr Following is the procedure for selecting an alternate server: From the ETM log-in screen, select the Select a new server link. The Server List window will appear. • Click the name of the desired server in the Server column. • Click Select. The Server List window will close and if ETM can connect to that server, the selected server will be displayed on the ETM login screen. Modify an existing server If it is necessary to make modifications to an existing server, this task may be performed in the Server List window, shown previously in Figure 3 - 2. From the ETM log-in screen, click the Select a new server link. In the Server List window, click the name of the server to be modified. • Select the Modify button. The New Server window will open. • Make desired changes. • Click Save to apply changes. • Click Close to close the Server List window and return to the ETM login screen. Delete an existing server If it is necessary to delete an existing server, this task may be performed in the Server List window. In the Server List window, click the name of the server to be deleted. • Select the Delete button. The selected server will be removed from the Server List. • Click Close to close the Server List window and return to the ETM login screen. Add additional servers If it is necessary to add additional servers, this task may be performed in the Server List window. In the Server List window, click the Add button. The New Server window will open. User Guide • Server Nickname: Enter a user-defined name for this server. • Server Location: Enter the physical location of the server. • Server FQDN: Enter the fully qualified domain name for the server. (see example in the New Server display) • Make this my default Authentication Server. Enable this setting to connect to this server each time this instance of ETM starts. • Click Submit to add the new server. • Click Close to close the Server List window and return to the ETM login screen. 98-1745 Rev AA 31 Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr After Login: Setup Cautions NOTE: When ETM is first launched, view the Connection tab. Click the checkboxes for both Display Scrolling Status and Enable Test Reports, and then click Save Settings. Until changed, these settings will remain the default each time the ETM application opens. CAUTION: Upon launch, ETM will attempt connection to the computer’s first available serial port. If an Integrated WAN Radio (IWR) is not connected to that serial port, ETM will time out. After ETM times out, click the Connection tab to select the serial port connected to the IWR. Certificate Attributes The current status of the Mobile Admin Tool (MAT) Certificate can be viewed in the Security display. Figure 3 - 4. Security Menu Options From the menu options, select Security > MAT Certificate Attributes. The Token Attributes displays the current status of the MAT Certificate received from Command Center. Figure 3 - 5. Token Attributes 32 • NetWork ID. The Network ID is the utility’s unique Network Identifier. (For endpoints with v6.x firmware, this parameter cannot be changed in ETM) • Token Sequence Number. The Certificate Sequence number uniquely identifies the certificate issued for the MAT session. • Lan Address Block. The LAN Address Block displays the set of LAN Addresses that the MAT has been provided to use to communicate with endpoints. LAN Address block consists of 16 addresses, and are provided each time a certificate is requested from Command Center. • Token Expiration Time Stamp. Indicates the date and time that the MAT certificate will expire. The default value is 1440 minutes (one day) and is established in Command Center Organization Information settings. 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr • Keep Alive. This value specifies the amount of time that a session between a MAT and an endpoint can be inactive before the endpoint closes the session. The default value is 15 minutes. • User Priority. The user priority field allows a user of a higher or equal priority to preempt an existing MAT Certificate. Users with a lower priority cannot gain access if a higher priority is engaged with the endpoint device. This also provides a method for the system to lockout a rogue user if a problem is detected on the endpoint. • Signature Expiration Time Stamp. This indicates the signature expiration for the MAT Certificate. It is set to three times the MAT Certificate expiration interval by default. This allows the MAT user to attempt to access an endpoint using the certificate and get a response back from the MAT rather than no response for a reasonable period of time before the certificate expires. A signed certificate is only required when endpoints are in ECC mode. Request MAT Certificate In the event that a MAT Certificate is reaching its expiration time, a new MAT Certificate may be requested from Command Center by selecting the MAT Certificate option from the Security submenu. From the Menu options, select Security > Request MAT Certificate. The Log-in window will open. Figure 3 - 6. ETM Login screen User Guide • User Name: Enter utility-provided user name. • Password: Enter utility-provided password. • Server Name: The Server name field will display the server to which ETM will connect by default. • Click OK. If the user is successfully authenticated by Command Center, and the user has the proper privileges (Access and Certificate Authorization), Command Center will issue a MAT Certificate consistent with the level of security that the utility is using. NOTE: If a user’s session is nearing expiration, the user may also log out of ETM and log back in to get a new Certificate. If the ETM either has no Certificate, or the current MAT Certificate expiration is less than 50% of the original time interval, the MAT requests a new MAT Certificate. 98-1745 Rev AA 33 Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr ETM Sign In The ETM user and the ETM tool must 1) be known to and 2) authenticated by Command Center. The user must have been provided privileges and user credentials in order to access the ETM software. If the user has not been provided with credentials, the user must contact the utility-designated Security Administrator. The process of authenticating with Command Center provides the user with a Mobile Admin Tool (MAT) Certificate. The MAT Certificate confirms and certifies ETM’s identity to the endpoints. CAUTION: ETM login has two modes: one with and one without server access (off-line). In off-line environments, ETM users must go on-line and successfully authenticate themselves to Command Center once every seven days. Below is the procedure for logging into ETM: Launch ETM. The Login to ETM screen will open. Figure 3 - 7. Endpoint Test Manager - Sign In • User Name: Enter utility provided your User Name. • Password: Enter utility provided password • Server Name: The Server name field will display the server to which ETM will connect by default. If needed, click the Select a new server link to connect to a different server, as described above. • Click OK. If the user is properly authenticated by Command Center and the user has the proper privileges (Access and Certificate Authorization), Command Center will issue a MAT Certificate consistent with the level of security the utility is using. If the user name and/or password is not authenticated, a warning dialog box will appear. The user may attempt to log in a total of five times with incorrect credentials before being locked out of the system. The Security Administrator will need to clear the locked out status via Command Center. 34 98-1745 Rev AA User Guide Landis+Gyr Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Figure 3 - 8. Login Validation Even though the user may have certificate privileges, this message indicates that certificate server is not properly set up. (Possible reasons include: the server might be down or the signing utility might not be set up). If the user clicks OK, ETM will launch and they will be able to communicate to meters that are not in ECC mode. Figure 3 - 9. Login Validation The authentication process provides the user with the required MAT Certificate. The length of time that the MAT certificate is valid is configured by the utility in the Organization Information settings, with the default being 1440 minutes. CAUTION: If a MAT Certificate is nearing expiration, the user may log out of ETM and log back in to get a new Certificate. If the ETM instance either has no Certificate, or the current MAT Certificate expiration is less than 50% of the original time interval, the MAT requests a new MAT Certificate. Using the Bar-code Scanner Please read the following information before using the barcode scanner to scan meter information. WARNING: The bar-code scanner contains a laser light. Do not stare directly into the beam. NOTE: Ensure that the bar-code scanner beam covers the length of the bar-code. The figure below illustrates the proper method for scanning a bar-code. User Guide 98-1745 Rev AA 35 Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr Figure 3 - 10. Using the Bar-code Scanner Navigating the Software ETM is an easy-to-use software application that allows you to perform specific configuration, verification, and testing procedures. The application is comprised of an upper menu bar, the tabs listed below, and a Security Status line at the bottom of the display that describes the server connection and displays the connected endpoint’s security status. • Connection • Head End Radio • Device Test • Firmware Download • Module • Reporting • Command Scheduler • HAN (ONLY appears when a compatible endpoint is connected) • Universal Event Log • Service Limiting (ONLY appears when a compatible endpoint is connected) • Groups • RF Gas/Water (ONLY appears when the appropriate key is added to the Settings.XML file) • Collector (ONLY appears when ETM is connected to a Collector) Use the upper menu bar for exiting ETM, File > Exit, or to display or request Security details (as specified in the following section). Table 3-1. Upper Menu Bar Security Details Field Description MAT Certificate Attributes Displays details about the Mobile Admin Tool certificate received from Command Center. Request MAT Certificate Sends a request to Command Center for a Mobile Admin Tool Certificate. Login permissions will vary access to this feature. ETM can also be configured to display an Activity Log at the bottom of each screen that allows the user to view communication activities between the tool and the endpoint. Configuring a New Gridstream IWR Radio These parameters can be set via the Head End Radio tab. To configure a new Gridstream IWR radio: 1. Connect the IWR to the PC 36 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr 2. Select the Head End Radio tab 3. Click the Modify button 4. Change the radio's Network ID to match the utility-specified Network ID (for endpoints with firmware version v6.x and higher, this parameter is managed by Command Center and cannot be changed by ETM) 5. Disable the router bit 6. Disable the timekeeper bit 7. Enable the head-end bit 8. Enable the operational bit 9. Set the baud rate to 38400 10. Enter the Latitude and Longitude in the LPP Address field 11. Click Apply to save changes. NOTE: If only the CRC and baud rate are to be changed, a new Gridstream IWR can be configured using ETM’s Head-end management. Command Center is used to manage the CRC for endpoints with firmware v6.x and higher. Meter Shop Best Practices Use Case - Proper IWR Configuration This procedure describes proper configuration for IWR radios being used by any technician where the radio is on a production network. Do not: • Set up your IWR as a router. This will only slow down process actions as the IWR will be busy routing packets unnecessarily. On a production network this will interfere with the local mesh when the radio is turned off. • Set up your IWR as a head-end. This will cause significant problems with the production mesh network. • Set up your IWR set as a timekeeper. This is will pass the time of your computer to other network devices. Using RadioShop, confirm the following settings. User Guide NOTE: For information on RadioShop see RadioShop® Getting Started Guide, Landis+Gyr publication 98-1054. • Control Byte 1 - 69 is correct for a mobile IWR. The best way to change Control byte 1 is by setting WAN address under configure. As you change from a Mobile IWR to Fixed IWR CB1 changes from 69 > 49. • Control byte 2 should be HEX 48. • Control byte 3 should be HEX 50. CAUTION: Control byte 3 is important. It prevents your radio from advertising a path to the Collector and from trying to register with Command Center every time it is powered on or reset. 98-1745 Rev AA 37 Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr • Control byte 4 should be HEX 69. • Control Byte 4 with RF Filter enabled and wide mode enabled should be HEX 29. • Control Byte 4 with RF Filter disabled and wide mode enabled should be HEX 28. • Max LAN Nodes could be set to 28 or 86 depending on your environment. If you are on a deployed Normal meter network, 28 would be the best setting. If you are working in a LARGE meter shop environment handling meter returns, sample testing, and First Article Testing Max LAN Nodes value 56 (hex 86) would be best. NOTE: Series IV radios appear in Command Center by default. Authentication Server Connection If the current instance of ETM is not connected to the Authentication Server, ETM will display Work Offline in the status bar. Figure 3 - 11. Login Validation Connecting to a Collector On the Connection tab, click the Collector Settings button to add a Collector. The Collector List dialog box will appear. Figure 3 - 12. Collector List Dialog 1. When adding a Collector to the Collector List, click the Add button. The Collector dialog will appear. Figure 3 - 13. Collector Dialog 2. Type a unique name into the Collector Name field. 38 98-1745 Rev AA User Guide Draft 7.30.14 Chapter 3 - Using Endpoint Testing Manager (ETM) Landis+Gyr 3. Type the Collector IP address into the IP Address field with the numbers between the periods. 4. Click the OK button to add the Collector. The added Collector will appear in the Host: drop down box, located on the Connection tab. 5. To connect to the Collector, click Use Collector from the drop-down box. 6. In the Host: drop down box, highlight the name of the Collector you would like to connect to. 7. Click Connect. When the connection is successful, the Collector tab will appear in the tab group, ETM will navigate to the Device Test tab, and your radio will be set to field mode. Use the Disconnect button on the Connection tab to break communications with the Collector and return to standard head-end radio communications using the COM port. Connection Tab The Connection tab allows the user to view and change the connection information for the radio or Collector connected to the meter being tested. The table below describes the fields on the Connection tab. Table 3-2. Connection Tab Field Description Connection Settings- Use COM1 - at dropdown arrow This button allows the user to Connect or Disconnect, contains a drop down menu that allow the user to choose a COM port or Collector to interface with your radio, and contains another drop down menu (Figure 3 - 14.) to select connection speed for the COM port. The available baud rates are: 9,600 19,200 38,400 (default) 115,200 (for Series IV IWRs) RadioShop can identify the COM port and baud rate of the radio you are using. - Use Collector drop-down arrow choose Host drop-down arrow This button provides for Connect or Disconnect, selecting the Collector to connect with, and uses a drop-down menu to list collectors available to host the connected module. When ETM is connected to a Collector, a tab labeled “Collector” appears. Host Allows testing meters in the field by displaying available collectors in the drop down box. Collector Settings
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : Yes XMP Toolkit : Adobe XMP Core 5.4-c005 78.147326, 2012/08/23-13:03:03 Producer : ScanSoft PDF Create! 7 Creator Tool : Microsoft Word - 14-0210 - Exhibit Cover.doc Create Date : 2014:07:31 09:51:44-04:00 Modify Date : 2014:08:01 11:18:41-04:00 Metadata Date : 2014:08:01 11:18:41-04:00 Format : application/pdf Title : Microsoft Word - 14-0210 - Exhibit Cover.doc Creator : courtney.mcgann Document ID : uuid:4850de75-3d5b-472f-a1d2-5507a999f89e Instance ID : uuid:ee5d1b53-b90a-4f19-9ccb-c5adc32be8d1 Page Count : 70 Author : courtney.mcgannEXIF Metadata provided by EXIF.tools