Communications Gateway - Home | Franklin Electric | Grid...

Communications Gateway (For Gateway firmware 2.14 and higher)

Version 5.3 14 Dec 2015

Gateway Manual Sept 2015 Page 1 of 113

Copyright

LineIQ Gateway User Manual

© CHK GridSense Pty Ltd 2011, 2012 The material presented in this manual is copyright protected by CHK GridSense Pty Ltd

2012. Any reproduction in whole or part for any purpose without the prior written consent

of CHK GridSense Pty Ltd is strictly prohibited. Information in this document is subject to

change without notice.

All trademarks are property of their respective owners.

LIMITED WARRANTY The Gateway is guaranteed to be free of mechanical and electrical defects w h e n

dispatched from our store. Provided that the Gateway has been operated within its normal

ratings as specified, it will be repaired or replaced free of charge if, within a period of

t w e l v e

(12) Months from date of our invoice to the original purchase, it is proven, upon

examination by our engineers, to be defective in material or workmanship. This warranty is

void if the unit has been tampered with, abused or if the defect is related to service not

performed by CHK GridSense Pty Ltd.

Responsibility of CHK GridSense Pty Ltd: Under this guarantee, the responsibility of CHK

GridSense Pty Ltd is limited to the repairing or replacing of any defective part provided the

instrument is returned freight paid to and from our Testing and Service office in Sydney,

NSW Amendments

AUSTRALIA / NEW ZEALAND EMC NOTES

N3207

This is a CISPR 22 Class A product. In a domestic

environment this product may cause radio interference,

which the user may need to take steps to prevent.


Contents

1 International Safety Symbols .......................................................................................... 9

2 The LineIQ and Gateway Remote Monitoring Solution ................................................. 10

3 The LIQ Gateway ......................................................................................................... 13

3.1 What’s in the box? ............................................................................................. 14

3.2 Optional Accessories ......................................................................................... 15

4 Quick Start Guide ......................................................................................................... 16

5 Gateway Overview ....................................................................................................... 18

5.1 The Gateway .....................................................................................................18

5.2 Indicators and Controls. ....................................................................................19

5.3 External Connectors ..........................................................................................20

5.4 Local RF Link .....................................................................................................20

5.5 AC Power Cable (Optional) ............................................................................... 20

5.6 AC Power Cable with large clamps leads (Optional) ........................................ 21

5.7 External Solar Panel (Optional) ..........................................................................22

5.8 AC Power Cable with tinned leads (Optional) ...................................................23

5.9 DC Power Cable (Optional) ................................................................................24

5.10 PC Data Cable (Optional) ...................................................................................25

5.11 Modem Data Cable (Optional) .......................................................................... 26

5.12 Ethernet Data Cable (Optional) ..........................................................................26

5.13 Internal Ethernet Module (Optional) ...................................................................27

5.14 Cellular Modem (Optional) .................................................................................27

5.15 Utility Radio (Optional) .......................................................................................28

5.16 Omni Directional Antenna Kit (Optional) ............................................................. 28

5.17 External High Gain Yagi Antenna Kit (Optional) .................................................28


6 Safe Use of the Gateway.............................................................................................. 29

6.1 Hazard Assessment ...........................................................................................29

6.2 Live low voltage work ........................................................................................ 30

6.3 Live high voltage work ...................................................................................... 30

6.4 Equipment safety ............................................................................................... 30

7 Configuring The Gateway Before Use .......................................................................... 31

7.1 Introduction ........................................................................................................31

7.2 Communicating with the Gateway .....................................................................31

7.3 Gateway Status .................................................................................................31

7.4 Starting LineMan ...............................................................................................34

7.5 How will the Gateway communicate? ............................................................... 35

7.6 Working with LineMan Remote ..........................................................................35

7.7 Working with a DNP3 SCADA master ................................................................35

8 Installing Your Gateway ............................................................................................... 37

8.1 Pre-installation checks ......................................................................................37

8.2 Mounting ............................................................................................................37

8.3 Post-installation checks..................................................................................... 37

9 Commissioning the Gateway ....................................................................................... 39

9.1 Step 1: Configuring the CMS devices ................................................................39

9.2 Step 2: Configuring the Gateway ...................................................................... 39

9.3 Step 3: Commissioning the Gateway .................................................................41

10 Troubleshooting .......................................................................................................... 42

10.1 Internal battery is discharged: ...........................................................................42

10.2 LineMan cannot communicate with Gateway: ...................................................42

10.3 Gateway does not communicate with external peripherals: .............................. 42


10.4 Unable to connect via LineMan-Remote: ...........................................................42

10.5 Unable to communicate with SCADA system: ................................................... 43

10.6 Gateway displays alternating red and amber LEDs after commissioning: ..........43

10.7 Gateway displays fast flashing red LED: ........................................................... 43

11 Operating Principles .................................................................................................... 44

11.1 Gateway Memory Usage .................................................................................. 44

11.2 Event Memory ...................................................................................................44

11.3 Unsolicited event data transfers ........................................................................44

11.4 Solicited event data transfers ............................................................................45

11.5 Load Log Memory .............................................................................................45

11.6 Estimated Download Times ...............................................................................47

11.7 Gateway lack of response during Health Checks ..............................................49

11.8 Real Time Clock (RTC) ....................................................................................... 51

11.9 Solar Panel Mounting Considerations ................................................................52

12 Maintenance ............................................................................................................... 56

12.1 Standby battery ................................................................................................ 56

12.2 Calibration .........................................................................................................56

12.3 Cleaning ...................................................................................................................... 56

12.4 Periodic Maintenance and Testing ....................................................................56

12.5 Operational Problems ........................................................................................56

12.6 Firmware and Software Upgrades .....................................................................57

12.7 Repairs ........................................................................................................................ 57

12.8 Customer Registration .......................................................................................57

12.9 Technical Sales and Assistance ....................................................................... 58

13 Gateway Specifications ............................................................................................... 59


14 Accessory Specifications ........................................................................................................... 61

14.1 10 W External Solar Panel .............................................................................................. 61

APPENDIX A – LINEMAN .................................................................................................................. 62

A1 Installing LineMan ................................................................................................................ 62

A2 Starting LineMan................................................................................................................. 62

APPENDIX B – LINEMAN REMOTE ................................................................................................... 65

APPENDIX C – INTERNAL ETHERNET MODULE .............................................................................. 67

C1 Introduction ......................................................................................................................... 67

C2 Installation ........................................................................................................................... 68

APPENDIX D - DNP3 COMMUNICATIONS ....................................................................................... 73

D1 Introduction ......................................................................................................................... 73

D2 Locating the DNP3 Interface Settings .................................................................................. 73

D3 Selecting the Health Check Interval ..................................................................................... 74

D4 Changing the DNP3 Interface Settings ................................................................................ 75

D5 Selecting and configuring the DNP3 RS232 Port ................................................................. 76

D6 Permanently powering the radio modem ............................................................................. 76

D7 Setting DNP3 Protocol Parameters ..................................................................................... 76

D8 Other Pertinent Parameters ................................................................................................. 81

D9 Checklist for Configuring the Interface ................................................................................ 81

APPENDIX E – RECOMMENDED DNP3 POINTS USAGE ................................................................. 82

APPENDIX F – DNP3 DEVICE PROFILE ............................................................................................ 83

F1 Device Identification .............................................................................................................. 83

F2 Link Layer ............................................................................................................................. 87

F3 Application Layer .................................................................................................................. 88

F4 Fill Out the Following Items for Outstations Only .................................................................. 90


F5 Outstation Unsolicited Response Support ............................................................................. 92

F6 Outstation Unsolicited Response Trigger Conditions ............................................................ 93

F7 Outstation Performance ........................................................................................................ 95

F8 Individual Field Outstation Parameters. ................................................................................. 95

F9 Implementation Table ........................................................................................................... 96

F10 Capabilities and Current Settings for Device Database (Outstation Only) –Point List… … . 97

F10.1 Single-Bit Binary Inputs ............................................................................................. 97

F10.2 Analog Input Points ................................................................................................... 98

APPENDIX G – Detailed DNP3 Point List ....................................................................................... 100

G1 Octet String Events ............................................................................................................ 100

G2 Single Binary Inputs ........................................................................................................... 101

G3 16 Bit Analog Inputs ........................................................................................................... 102

Appendix H – Gateway Firmware Upgrades .................................................................................... 103

Appendix I – Remote Access via TCP/IP…………….…………………………………………………… 110


Table of Figures

Figure 1: LineIQ System Overview .................................................................................................. 12

Figure 2: Gateway Isometric View .................................................................................................. 18

Figure 3: Gateway Front Panel ........................................................................................................ 19

Figure 4: Gateway Connectors ........................................................................................................ 20

Figure 5: AC Power Supply Cable .................................................................................................. 21

Figure 6: AC Power Cable with large clamps ............................................................................... 21

Figure 7: External Solar Panel ......................................................................................................... 22

Figure 8: AC power cable with tinned ends .................................................................................. 23

Figure 9: DC power cable with tinned ends .................................................................................. 24

Figure 10: PC Data Cable and Pin Out .......................................................................................... 25

Figure 11: Modem data cable and pinout...................................................................................... 26

Figure 12: Ethernet data cable ........................................................................................................ 26

Figure 13: Cellular Modem power supply connector pinout ...................................................... 28

Figure 14: Status indicators ............................................................................................................. 31

Figure 15: Status Indicator Summary ............................................................................................. 34

Figure 16: Estimated LineIQ Log Average memory usage .......................................................... 46

Figure 17: Estimated Gateway communication speeds .............................................................. 47

Figure 18: LineIQ-60 Health Check downloads times using a cellular modem ....................... 48

Figure 19: LineIQ Health Check download times using cellular model .................................... 49

Figure 20: Lack of response time during Health Check for LineIQs ......................................... 50

Figure 21: Lack of response time during Health Check for LINEIQs ........................................ 51

Figure 22: Solar panel facing the equator (Northern hemisphere mounting) ........................... 53

Figure 23: Solar panel angle measured from vertical .................................................................. 54

Figure 24: Solar panel angle measured from vertical .................................................................. 55


Figure 25: LineMan Opening Screen .............................................................................................. 62

Figure 26: LineMan Connection Screen......................................................................................... 63

Figure 27: Selecting the Communications Port from the pull down menu ............................... 63

Figure 28: LineMan Remote Connection Screen ......................................................................... 66

Figure 29: Internal Ethernet module kit .......................................................................................... 67

Figure 30: Internal Ethernet module ............................................................................................... 67

Figure 31: Gateway with cover opened .......................................................................................... 68

Figure 32: Gateway with main shield cover removed .................................................................. 69

Figure 33: Centre pair of SIL 8 pin female connectors (at bottom) ............................................ 69

Figure 34: S3 connector (bottom pair of SIL female connectors) .............................................. 70

Figure 35: Internal RJ45 connector inserted into internal Ethernet module ............................. 71

Figure 36: Internal RJ45 connector inserted into internal module (shield cover replaced) ... 71

Figure 37: External RJ45 cable connected to Data Connector ................................................ 72

Figure 38: LineMan main screen ..................................................................................................... 74

Figure 39: IFC setting window ......................................................................................................... 75

Figure 40: Verifying the COM port number .................................................................................. 103

Figure 41: Gateway Firmware Upgrader opening screen ......................................................... 104

Figure 42: Selecting the .LHX file .................................................................................................. 104

Figure 43: Gateway firmware upgrader with .LHX file selected ............................................... 105

Figure 44: Figure 44: Gateway Firmware Upgrader with COM port selected ........................ 105

Figure 45: Gateway Firmware Upgrade commencing ............................................................... 106

Figure 46: Gateway Firmware Upgrade in progress .................................................................. 107

Figure 47: Gateway Firmware Upgrade completed ................................................................... 107

Figure 48: Using LineMan to verify the firmware version number............................................ 108

Figure 49-55: Gateway Remote Access via TCP/IP...……………………………….......109-113


1 International Safety Symbols

CAUTION Symbol: See explanation in manual

This manual covers the Gateway. Other products in the LineIQ suite are described in other manuals.

GridSense places the highest emphasis on safety. Please see section “Error! Reference source not

found.” on page Error! Bookmark not defined.. Ensure that only qualified personnel use the Gateway.


2 The LineIQ and Gateway Remote Monitoring Solution The LineIQ system allows electric utilities and other owner/operators of high voltage

overhead conductor electric power transmission systems to remotely monitor and respond

to faults and load changes on the HV network, using LineIQ Conductor Mounted Sensors

(CMS) to detect and store network events (faults, momentary interruptions, outages &

restorations) as well as monitor load currents, conductor temperatures and ambient

temperatures.

LineIQ-60 devices are installed on energized lines. They are battery and solar powered for

long term and continuous monitoring. They can be configured wirelessly using a license

free low power radio (LocalLink) which can is also used to download event and load log

data and to upgrade firmware.

Local wireless configuration and data downloads are performed via the LocalLink unit and

a personal computer (PC) running the GridSense Lineman application software.

For remote connection to LIQ-60 and access to stored data records, a Gateway Pole

Attached Collator (PAC) is mounted within radio range of the LineIQ CMS. The Gateway

functions as a Remote Terminal Unit (RTU) and collates event and load log data from up to

9 LIQ-60 using the low power radio link.

The Gateway can be mains powered DC or battery/solar powered.

LIQ-60 devices transfer event data detecting an event, while load log (line current, line

temperature & ambient temperature) is collected by the Gateway from the LIQ-60 at

regular, user selected intervals, typically once a day.

Transmission of load log data from LIQ-60 to the Gateway occurs during a “health check”.

This data is then transmitted by the Gateway to the remote monitoring system (SCADA) or

is accessed on demand using LineMan Remote software as shown in Figure 1.

A system “Health Check” is initiated by the Gateway independently of events. The Gateway

initiates communications with each LIQ-60 to download all log data and health records

(battery voltage, solar charge current etc.) to the Gateway memory. This information can be

remotely accessed on demand via LineMan Remote or accessed by SCADA via DNP3.

Event records are transferred to the Gateway via unsolicited report and are automatically

transferred to SCADA. If the Gateway is not connected to SCADA, the event records can

be accessed through LineMan Remote or onsite by downloading the data loca l l y .

The Gateway communicates to external systems using either a cellular modem or a utility

radio, and includes space for these to be mounted inside the Gateway.


The LineIQ system is powered by solar trickle charged sealed lead acid batteries designed

to provide continuous and long term unsolicited remote reporting of events and historic

load data. This is achieved by minimizing local RF and remote communications through

scheduled and unsolicited reporting, as this means that the communication systems (RF

link and cellular modem or utility radio) can be powered up only when required.

Figure 1 shows how the Gateway interfaces wirelessly to Conductor Mounted Sensors

(CMS) and remotely to external systems via the Gateway RTU and various remote software

applications.


Fig

ure

1:

Lin

eIQ

Sys

tem

Ov

erv

iew


3 The LIQ Gateway Congratulations! On your purchase of a LIQ Gateway– a state of the art Remote Terminal

Unit (RTU) for use with LineIQ Conductor Mounted Sensors (CMS).

The Gateway provides an interface to LIQ-60 line mounted high voltage load and event

loggers which are used for load logging and fault detection on overhead high voltage

transmission lines.

Features of the Gateway include:

Low power license free RF communication to up to 9 LIQ-60 CMS devices within RF

range

Supports industry standard DNP3 interface for SCADA applications

Provides remote access to log and event data via:

o LineMan Remote

o Industry standard DNP3 interface

Provides gateway to data from remote locations via:

o Solicited load, line and device status queries (polls) to DNP3 SCADA master

o Unsolicited fault event, momentary outages and load log data to DNP3

SCADA master

o On demand remote download of fault events, load log data and

instantaneous line status queries via LineMan Remote software

Includes multiple communication options:

o UtilinetTM or other utility radio

o GSM Cellular (circuit or packet switched)

o CDMA Cellular (circuit or packet switched)

o 3G Cellular (circuit or packet switched)

o PSTN

o RS232 direct connect

o TCP or UDP over Ethernet

16 bit processor with 4\512 kB non-volatile memory

Real time clock with battery backup

Remote diagnostic and troubleshooting tools


Robust IP65 rated weather-proof housing with hinged lid

3.1 What’s in the box?

The Gateway is normally supplied in a ready to use kit which does not include a modem:

Part No. Description

1ALT-PACv2-1 Remote Data Concentrator excluding modem, ready for use

with LIQ-60


with LIQ-60/45/50 (916-US)


with LIQ-60


with LIQ-60 (916-US)


with LIQ-60


with LIQ-60 (916-US)

For safety reasons, use only GridSense accessories specifically designed for use with this product. The

use of any other manufacturer's equipment is NOT recommended, will void the warranty and may cause

safety hazards.


3.2 Optional Accessories

The following optional accessories are also available:

Part No. Description

AC-PAC-PC5 AC Power Supply Cable with Australian GPO plug

AC-PAC-PC5-2 AC Power Supply Cable with North American GPO plug

AC-PAC-ACVC AC Power Supply Cable with Clamps

AC-PAC-ACVT AC Power Supply Cable with tinned leads

AC-PAC-DCVT DC Power Supply Cable with tinned leads

1AAC-PAC-Solar External Solar Panel (5 W)

1AAC-PAC-Solar-10W External Solar panel (10 W)

1AAC-PAC-RC2-PC Gateway external RS232 Data Cable for direct PC connection, 3m length

1AAC-PAC-RC2-RTU Gateway external RS232 Data Cable for direct Modem/RTU connection, 3m length

1AAC-PAC-ETHMODULE Ethernet upgrade module (including Ethernet Data Cable)

AC-PAC-ETHERNET-CABLE Gateway external PAC to Ethernet connection cable, 3m length

1AAC-3GK 3G ModMax cellular modem kit for use with Gateway

1AAC-GSMK GSM/GPRS cellular modem kit for use with Gateway

1AAC-PSTNK Landline modem kit for use with Gateway

1AAC-CDMAK CDMA modem for use with Gateway

1AAC-SATK Satellite modem for use with Gateway

Utility radio - no part number as not supplied by GridSense

1AAntenna-800/900 Gateway external 3G Cellular Antenna accessory kit

1AAC-PAC-Yagi High Gain Yagi Antenna

1AAC-PAC-OMNI Omni Directional Antenna

For safety reasons, use only GridSense accessories specifically designed for use with this product. The

use of any other manufacturer's equipment is NOT recommended, will void the warranty and may cause

safety hazards.


4 Quick Start Guide The information presented in this section is a duplicate of the information presented on a

sticker inside the front lid of the Gateway.

1. If a cellular modem is to be installed, mount it to the modem mounting plate using

the two screws provided. Connect the DB15 data connector the antenna connector

and the power supply connector to the modem. The modem will need to be

preconfigured before installation.

2. If a radio modem is to be installed, mount it above the battery pack using the

mounting hardware provided. Do not remove the protective cove on the battery

pack. Connect the DB9 data connector, the antenna connector and the power

supply cable.

3. Install the RF antenna located on the inside of the lid. Screw it to the small socket

mounted on the right hand side of the enclosure. Don’t over tighten the antenna.

4. Check that all unused connectors are fitted with blanking plugs. Close the lid and

secure the latches.

5. Switch on the Gateway. The Status and Fault indicators will flash as follows:

The Fault indictor will flash red rapidly for 3 seconds

The Status indicator will flash amber rapidly for 3 seconds

The Status indicator will flash amber once every second for an

uncommissioned Gateway.

6. Mount the Gateway within 30 meters of the associated LIQ-60s with a direct line of

sight between the Gateway and the LIQ-60s. The Gateway should be oriented so

that the connectors are facing down so that it is possible to view the LED indicators

from the ground.

7. To optimize the performance of the LineIQ RF communications with the Gateway ,

the orientation of the Radio antenna’s between the Gateway and LineIQ must be

kept as parallel as possible as illustrated below:

8. Connect the cellular or radio antennas as required.

9. Connect the power supply. Your supply will be either (a) solar panel, (b) AC mains or

a (c) DC source:

a) Solar Panel - Install the solar panel so that it face towards the sun

at noon - south in the northern hemisphere and north in the


Southern hemisphere. Adjust the angle of the solar panel,

measured from the vertical, to be approximately latitude + 15o.

Connect the solar panel to the Gateway.

b) AC mains - Connect the AC supply using appropriate safety

equipment if working on live connections. The supply must be

between 55 V and 600 V AC at either 50 Hz or 60 Hz.

c) DC Source - Connect the external power cable to a 12 V 1 Amp DC

supply, and then connect this cable, observing polarity, to the

Gateway.

10. Using a LocalLink and LineMan software installed on your PC, configure the LIQ-

60and Gateway.

11. Send a commission command to activate the site.

12. Finally, verify that data is being correctly received via the remote communication

system.


5 Gateway Overview

5.1 The Gateway

An isometric view of the Gateway is shown in Figure 2 below:

Figure 2: Gateway Isometric View

The Gateway is an intelligent Remote Terminal Unit (RTU) for GridSense LIQ-60 line

mounted sensors to be efficiently and easily integrated into remote SCADA systems using

DNP3 protocol. In parallel the Gateway provides communication and data transfer to the

GridSense LineMan Remote application software.

The Gateway enables remote unsolicited fault and outage events for network reliability

applications. Detailed fault profiles for fault location analysis, modelling and scenarios, as


well as system loading information for planning, line balancing and asset utilization

applications.

5.2 Indicators and Controls

Figure 3: Gateway Front Panel

The Gateway base has four connectors AC Mains / Solar power input, Data, Radio Antenna

& Cellular Antenna, an ON/OFF switch and it also has two visual indicators.

The “Status” Indicator is an amber high intensity LED, while the “Fault” Indicator is a red

high intensity LED. The status indicators are used for fault/event annunciation and to

indicate remote connection, activities, to confirm that the Gateway is on and what mode it

is in.

The unlabeled hexagonal item in the center of the front panel is a pressure relief valve. This

valve allows the internal air pressure to equalize with the external air pressure while

maintaining the IP65 integrity of the Gateway.


5.3 External Connectors

Connector Specification

AC MAINS /

SOLAR

8 pin voltage connector – used to connect external power sources – AC mains

(55 – 600 Volts AC 50 Hz or 60 Hz), solar panel or DC source (13.8 Volts DC 1

Amp)

DATA 12 pin data connector – allows external wired connections (RS232, or Ethernet)

RADIO

ANTENNA

N type female – allows connection of an external radio antenna

CELLULAR

ANTENNA

N type female – allows connection of an external cellular antenna

Local RF

Antenna

SMA female (mounted on side of Gateway)

Figure 4: Gateway Connectors

5.4 Local RF Link

The local license free RF communication system uses low power half duplex radio links.

The minimum operating range is 30 m (100 ft.) using the small antenna mounted on the side

of the Gateway enclosure.

The operating RF frequency is at 2.4GHz with maximum power output of 4mW.

5.5 AC Power Cable (Optional)

The fused PC5 (PC5-2 in North America) Power Cable provides a means of connecting

electrical power to the Gateway. A GPO plug is available to suit local requirements.

The internal switch mode power supply operates from 60 to 600 V AC at standard supply

frequencies (50 Hz or 60 Hz). Maximum power consumption is 15 VA.


Figure 5: AC Power Supply Cable

5.6 AC Power Cable with large clamps leads (Optional)

The AC-PAC-ACVC power cable is fitted with large clamps. The clamps include integral

High Rupture Capacity (HRC) fuses which are not user replaceable.

Figure 6: AC Power Cable with large clamps

As shown in Figure 6, labels “Phase A” and “Neutral” are fitted adjacent to the two clamps.

The leads are 3 m (10 ft.) long.


5.7 External Solar Panel (Optional)

The AC-PAC-SOLAR External Solar Panel allows the Gateway to operate without access to

mains power.

Figure 7: External Solar Panel

A connection cable and mounting bracket is included with the Solar Panel.

Depending on the application, customers may wish to use their own higher capacity solar

panel. A DC power cable is available for this purpose. Contact GridSense if you are unsure

if the standard solar panel is suitable for your application.


5.8 AC Power Cable with tinned leads (Optional)

The AC-PAC-ACVT power cable has tinned ends and allows direct connection of an

external AC supply. This cable includes non-replaceable in line High Rupture Capacity

(HRC) fuses.

Figure 8: AC power cable with tinned ends


5.9 DC Power Cable (Optional)

The AC-PAC-DCVT power cable allows operation from an external regulated 13.8 Volt DC

supply, or from a large external solar panel. It is provided with tinned ends.

Figure 9: DC power cable with tinned ends


5.10 PC Data Cable (Optional)

The AC-PAC-RC2 Data cable allows connection of the Gateway to a standard 9 pin male

PC or RTU serial port.

Figure 10: PC Data Cable and Pin Out

The PC Data cable is fitted with a 9 pin female connector. 5 pins are connected – TX, RX,

CTS, RTS and GND.

For troubleshooting purposes, this cable is used to connect the Gateway to a PC running

LineMan software.


5.11 Modem Data Cable (Optional)

The AC-PAC-MODEM-CABLE allows connection of the Gateway to a standard 9 pin female

modem serial port.

Figure 11: Modem data cable and pinout

The Modem Data cable is fitted with a 9 pin male connector. 5 pins are connected - TX, RX,

CTS, RTS and GND.

This cable is used to connect the Gateway to an external modem.

5.12 Ethernet Data Cable (Optional)

Figure 12: Ethernet data cable


This Ethernet Data Cable is used to connect the Gateway directly to the internet using an

industry standard RJ45 10 base T connector, typically in a substation.

5.13 Internal Ethernet Module (Optional)

The Ethernet module provides TCP and UDP internet access, and is supplied complete

with an external Ethernet Data Cable.

If the Gateway is ordered with this accessory, it is pre-installed.

If the Internal Ethernet Module is ordered at a later date as an accessory to be installed into

an existing Gateway, refer to “APPENDIX C – INTERNAL ETHERNET MODULE” for

installation details.

Refer to section 18.2 for details on how to configure the Internal Ethernet Module.

5.14 Cellular Modem (Optional)

An internally mounted modem can be used to interface the Gateway to external systems

using commercial cellular phone systems.

If the cellular modem is ordered with the Gateway, the modem power supply loom is

supplied and connected to the modem, which is installed in the G a t e w a y .

If no cellular modem is ordered with the Gateway, the modem power supply loom is not

supplied. The required 3 pin connector is provided and is installed onto the main printed

circuit board.

Both 12V DC and 5V DC supplies are available. The pinouts for the connector areas shown

in Figure 10.


Figure 13: Cellular Modem power supply connector pinout

5.15 Utility Radio (Optional)

An internal mounting location is provided for a user supplied utility radio for interfacing the

Gateway to an external radio network.

5.16 Omni Directional Antenna Kit (Optional)

The AC-PAC-OMNI external Omni-directional antenna kit provides standard coverage for

the internally mounted cellular modem.

Note that the antenna must match the cellular frequency as dictated by the cellular modem

and cellular service provider.

5.17 External High Gain Yagi Antenna Kit (Optional)

The AC-PAC-YAGI external Yagi Antenna kit allows for reliable cellular communications in

areas of marginal coverage.

Note that the antenna must match the cellular frequency as dictated by the cellular modem

and cellular service provider.


6 Safe Use of the Gateway

The LineIQ Conductor Mounted Sensors associated with the Gateway are intended to be

used on high voltage energized lines or equipment. Personnel using equipment on

energized lines must be authorized by the relevant regulatory bodies to carry out such work

and must have appropriate training.

The information given in this document is given as a guide only. It is the user's

responsibility to ensure that correct and safe procedures are followed at the actual

worksite. GridSense offers no warranty or indemnity for accidents that may occur when

following these instructions.

6.1 Hazard Assessment

Prior to installing the Gateway, the operator must carry out a worksite, pre-job hazard

assessment to identify the safety and environmental needs. This must be done prior to

commencing work and prior to recommencing work after leaving and returning to the

worksite. As a minimum, this hazard assessment should:

Identify possible hazards and risks

Identify the safety needs of the job

Identify the correct procedures, practices and equipment for the job

Eliminate unsafe conditions and actions from the worksite

Identify the need for personal protective equipment

There should also be an on-going risk assessment during the job

Inspection before use

Prior to using a Gateway, you should check the following:

The sheaths of all cables are secured and undamaged at both ends

If you do not understand any instructions in this manual, please ask someone

to assist you.

If the Gateway and accessories are used in a manner not specified in this

manual, the protection provided by the equipment may be impaired.


Plugs and connectors are properly connected and serviceable

6.2 Live low voltage work

For the correct and safe use of this equipment, it is essential that all operating personnel

follow appropriate safety procedures.

6.3 Live high voltage work

For the correct and safe use of this equipment, it is essential that all operating personnel

follow appropriate safety procedures.

6.4 Equipment safety

The Gateway equipment should be regularly tested and maintained to make sure the

equipment and cables are in good order.

Check your relevant employer or regulatory body's rules for working with live

low voltage equipment.

Check your relevant employer or regulatory body's rules for working with live

high voltage equipment.


7 Configuring the Gateway before Use

7.1 Introduction

The Gateway is configured using LineMan software. Refer to the LineMan User Manual for

detailed instructions on how to install and use Lineman. Brief details are also provided in

APPENDIX A.

7.2 Communicating with the Gateway

Plug in the LocalLink1 to an open USB on the PC. Make sure the proper COMS port is

selected in LineMan. You are now ready to communicate with the LIQ-60 and Gateway

units.

7.3 Gateway Status

Gateway status is provided by the two LED indicators in the bottom right hand corner of

the front panel.

Figure 14: Status indicators

The main modes of operation are shown as follows:

Power On / Reboot

8 short red flashes followed by 8 short amber flashes

1 To determine the COM Port connection, access the Device Manager (Control Panel → System

→ Device Manager) and expend the selection “Ports”, the selection USB Serial Port will identify

the correct COM Port number


This sequence indicates successful initialization and start-up of the Gateway. Refer to

Section 10, “Troubleshooting,” if you do not see this sequence after the Gateway is

switched on.

For the first 5 minutes after power is applied, the red LED will flash whenever RF activity is

detected. This provides an indication of RF interference which may cause communication

errors.

Gateway requires Commissioning

Amber LED flashes once per second

This sequence indicates that the Gateway has not been commissioned.

Commissioning involves initialization of several aspects of the LineIQ site being monitored.

Many aspects of Gateway operation, including DNP3 communications, are disabled until

the Gateway is commissioned.

GridSense recommend that after physical installation has been completed, the Gateway

and associated LIQ-60units are commissioned manually on site using the LocalLink and

LineMan software.

This allows the user to verify that the commissioning process has been successfully

completed prior to leaving the site by monitoring the Status LEDs.

If a Gateway is not manually commissioned, an auto-commission will occur immediately

prior to the first scheduled health check or after one hour, whichever occurs first.

Failed Commission

Alternating Red and Amber LEDs

This sequence indicates that commissioning has failed.

Refer to Section 10 for further information.

Normal operation

Three Amber flashes repeated each minute

This indicates normal idle operation.

RF Communications in progress

Fast Flashing Amber LED


This indicates that the Gateway is communicating over the local RF link to one of the

associated LineIQ Conductor Mounted Sensors (CMS).

Local RF communication occurs:

During the commissioning process

When a periodic health check is in progress

When an event has been detected by a LineIQ CMS

When instantaneous line data has been requested by a SCADA master

When instantaneous line data has been requested by LineMan Remote software

You will not be able to communicate with the Gateway using LineMan software and the

local RF link during this time.

Please wait until the Gateway returns to normal idle operation before attempting to

communicate with it.

Outbound call in progress

Slow flashing Red LED (once per second)

This indicates that the Gateway is making an outbound call to report data or

commissioning results to SCADA

You will not be able to communicate with the Gateway using LineMan software and the

local RF link during this time.

Ethernet communications in progress

Continuous fast flickering Amber LED

This indicates that Ethernet communications are in progress.

Firmware upgrade in progress

Red and Amber LEDs permanently on

This indicates that a firmware upgrade is in progress.

Configuration Error

Fast Flashing Red LED

This indicates that there has been a configuration error.

The status indication modes are summarized in Figure 15 below:


LED Indicator Description

Amber LED

Red LED

Figure 15: Status Indicator Summary

7.4 Starting LineMan

1. Start LineMan by double clicking on the desktop icon, or selecting it from the Start

Menu.

2. If you are not familiar with LineMan or you need to install it, refer to the LineMan

User Manual or to Section 7.4.

3. From the LineMan device selection window, select the Gateway.


4. The following commands can then be used:

Status - provides details of the battery voltage, battery drain current, charging

voltage, charging current and internal temperature

Summary – provides details of serial number, firmware version, hardware

revision and other parameters

Configure – allows the Gateway to be configured

Data Download – allows data to be downloaded. This command is normally

used only with conductor mounted sensors (CMS)

Commission – allows the Gateway to be commissioned. This should only be

done after the entire site (Gateway and LineIQs) have been correctly configured

Restart – performs a warm restart (reboot) of the Gateway microprocessor, and

is equivalent to switching the power off and then on again

7.5 How will the Gateway communicate?

From the viewpoint of the Gateway, the outside world can manifest itself in three ways:

As a PC running LineMan Remote software. In this mode, the Gateway only

responds to external requests for event and load log data. In this mode, the

Gateway never initiates external event and load log data transfers

As a SCADA control system, to which the Gateway can send unsolicited event

and load log data, and which can request the Gateway to provide event and

load log data

The configuration of the Gateway depends on which of these viewpoints is to be

implemented. Please refer to the relevant section below for information on how to configure

the Gateway.

7.6 Working with LineMan Remote

LineMan Remote allows remote connection to a Gateway.

Refer to the LineMan Remote User Manual for details on how to communicate with a

Gateway using LineMan Remote.

A brief introduction to LineMan Remote is provided in APPENDIX B.

7.7 Working with a DNP3 SCADA master

The Gateway implements a versatile, industry standard DNP3 interface for seamless

integration into SCADA systems. The interface can operate:


in a fully polled mode

a report by exception (unsolicited) mode

a combination of the two above modes

Refer to APPENDIX D for a detailed description on how to configure and use the DNP3

interface.

APPENDIX E provides a quick reference to the DNP3 points implemented by GridSense in

the Gateway.

Refer to APPENDIX F for the complete DNP3 Implementation Table.

Refer to APPENDIX G for the complete DNP3 Point List.


8 Installing Your Gateway

8.1 Pre-installation checks

If AC line power is provided, verify that the supply voltage is between 60 and 600 V

AC, and capable of supplying 15 VA. Supply frequency can be either 50 Hz or 60 Hz

If using cellular communications, confirm that there is adequate coverage at the

site. If possible, ascertain the direction of the closest cellular tower

If using internet communications, verify that a working internet connection is

available

If using an external solar panel, verify that adequate sunlight is available, and

determine the direction to the sun at noon – south in the northern hemisphere and

north in the southern hemisphere

8.2 Mounting

The Gateway should be mounted within 30 m (100 ft.) of associated LIQ-60 units.

Orient the Gateway so that the connectors are towards the ground.

Mount the Gateway using 2 suitable sized screws above and below the main body, using

the attached metal mounting bracket.

The solar panel should be mounted in a sunny location so that it faces the equator (south in

the northern hemisphere and north in the southern hemisphere).

The solar panel should be mounted so that the angle between the face of the solar panel

and a horizontal plane is approximately 15 degrees more than the latitude of the location.

8.3 Post-installation checks

Once installation is complete, check that:

The Gateway is securely mounted

The solar panel is securely mounted, faces the equator and is at the correct angle

The small RF antenna is screwed securely to the socket on the side of the Gateway

All connectors are securely tightened

The waterproof cap is installed on the data port connector

All cables are secure and unlikely to move or dislodge


If used, AC power is available and is connected

If used, DC power is available and is connected with the correct polarity


9 Commissioning the Gateway After installation is complete, and before you leave the site, the Gateway and associated

LIQ-60 devices must be configured, and then the Gateway must be commissioned.

To do this, you will need a LocalLink and LineMan software.

Before commencing, make sure that the real time clock in the PC or laptop is set correctly.

GridSense recommends that 24 hour mode is used for the clock, rather than AM/PM mode.

For further information on LineMan, refer to the LineMan User Manual. APPENDIX A

provides brief details on LineMan software.

9.1 Step 1: Configuring the CMS devices

Using LineMan and the LocalLink, connect to each CMS device.

Confirm that:

The internal battery voltage exceeds 2 V

There is some solar charge current if the solar panel is illuminated

Event recording is enabled if required

Load logging is enabled if required

Line currents are as expected

Voltage sensor values are as expected

The appropriate Gateway has been assigned as a parent to the CMS

9.2 Step 2: Configuring the Gateway

Turn on the Gateway using the front panel switch.

Observe the red and amber indicators:

The red indicator should flash 8 times

The amber indicator should flash 8 times

The amber indicator should flash slowly at 1 second intervals

Using the LocalLink and LineMan, connect to the Gateway.


Confirm that:

The internal battery voltage exceeds 12 V

There is some solar charge current if the solar panel is illuminated

The appropriate LIQ-60 devices have been assigned as children to the Gateway

The health check interval has been assigned

The interface control (IFC) settings have been properly configured for the

desired Gateway application and modem or other communications interface


9.3 Step 3: Commissioning the Gateway

The final step before leaving the site is to commission the Gateway.

The Gateway will then automatically commission any associated LIQ-60 devices, and

initiate the first health check.

Subsequent health checks will occur at the specified interval, typically every 24 hours.

The GridSense recommended procedure is to:

Commission the Gateway using LineMan and a LocalLink

Observe the Gateway status indicators and confirm that the Idle state has been

reached (three amber flashes every minute)

This may take several minutes. Status indications during commissioning will include a fast

amber flash while the Gateway is communicating with LineIQs via the RF link.

If the Gateway begins to flash alternating red and amber LEDs, the commissioning process

has failed. Refer to Section 9 or further details.

GridSense recommends that correct operation of the remote communications

system is verified as part of the installation process before leaving the site


10 Troubleshooting

10.1 Internal battery is discharged:

The Gateway will not start up until the internal 12 V battery is charged. If the internal 12 V

battery is completely discharged, connect the AC or DC power and wait for at least 16

hours before turning the Gateway on.

10.2 LineMan cannot communicate with Gateway:

Ensure that the LocalLink is connected to the PC, and that the correct

communication port (RS232) is selected

Some notebook hardware RS232 ports are also incompatible with the LocalLink

Ensure that the Gateway is switched on and the internal battery is charged

10.3 Gateway does not communicate with external peripherals:

Check that the port selections and baud rates are correctly configured

Ensure that the site has been commissioned

10.4 Unable to connect via LineMan-Remote:

Check that the modem is powered on and correctly configured

Ensure that you have the correct modem phone number, including international

and area codes. If you are dialing through a PABX, make sure that you have

included the appropriate access code for an external line

Confirm that you have an analog phone line. Many PABX systems provide digital

phone lines which are incompatible with analog modems

Confirm that the internet connection is working

Verify that you have the correct IPV4 style TCP or UDP internet address and port

number


10.5 Unable to communicate with SCADA system:

Check that the Gateway SCADA port is correctly configured

Confirm that DNP3 is enabled

Ensure that the DNP3 link address is correct

10.6 Gateway displays alternating red and amber LEDs after

commissioning:

This indicates that commissioning of at least one LIQ-60 has failed.

Check that:

The list of child LIQ-60s assigned to the Gateway is correct

Each LIQ-60 is powered on and can be successfully communicated with using

Lineman

Each LIQ-60 is no further than 30 m (100 ft.) from the Gateway

10.7 Gateway displays fast flashing red LED:

This indicates that the Gateway configuration is invalid.

Re-configure the Gateway using the latest version of LineMan software

If this problem persists, please contact GridSense for assistance

system is verified as part of the installation process before leaving the site


11 Operating Principles

11.1 Gateway Memory Usage

The internal 512 kB memory of the Gateway is partitioned into 3 sections

256 kB is used for internal variables and a data scratchpad

128 kB is used for storage of event information

128 kB is used for storage of load log information

11.2 Event Memory

As events are detected by associated LineIQ CMS, the event information is transferred to

the Gateway and stored in the Gateway event memory.

A typical event, including current and voltage waveforms, requires approximately 1 kB of

memory for storage.

Event information is transferred from the Gateway event memory to an external system by

either an unsolicited (initiated by the Gateway) or a solicited (initiated remotely) request.

11.3 Unsolicited event data transfers

Unsolicited event data is sent to a SCADA control system.

There is a small delay (approximately 1 minute) between when the first event data is

detected by a LIQ-60 and when the unsolicited data transfer commences. This delay is

required to allow event data from all associated LIQ-60 to be transferred to and collated by

the Gateway.

Once an acknowledgment of successful data transfer has been received, the Gateway

event memory is cleared.

In this mode, because the event data is transferred shortly after the events occur, there is

generally no problem with the event memory filling up and event data being lost.


11.4 Solicited event data transfers

Solicited event data can be requested by LineMan Remote or a SCADA system.

As each event recorded by a LIQ-60requires approximately 1 kB of memory for storage,

about 120 individual events can be stored in the Gateway event memory.

So for a Gateway with three child LineIQ CMS, all of which are presumed to see the same

event, only 40 events can be stored.

For a system with 9 child LineIQs, approximately 12 events can be stored.

It is up to the user to ensure that event data is transferred from the Gateway before the

event memory fills up.

For a DNP3 solicited event data transfer, once an acknowledgment of successful

data transfer has been received, the Gateway event memory is cleared

For a LineMan Remote solicited event data transfer, the user has the option as to

whether to clear the event memory or not.

If the event memory is not cleared, when the event memory fills up, older events will be

overwritten by newer events

11.5 Load Log Memory

Load log (line current) data (including conductor temperature for LineIQ CMS) is

downloaded from associated LineIQs on a regular basis during a Health Check, and is

stored in the Gateway Load Log memory.

The amount of data which is downloaded depends on the number of associated LineIQ

CMS, the type of LIQ-60and on the Log Average period.

For an LIQ-60 logging line current, power factor, conductor temperature and ambient

temperature, each Log Average sample requires 48 bytes of storage in the Gateway.

With the recommended Log Average interval of 15 minutes, this is equivalent to 1.5 kB of

storage per day for each 4.5 kB per day for each LineIQ-60 CMS.

Figure 18 below shows estimated percentage memory usage for 3, 6 and 9 LIQ-60 with

Log Average rates between 2 and 60 minutes


Days to Fill Gateway Log Average Memory with

Line Tracker LIQ-60 Load Log Data

Log Average

(min)

3x LIQ-60

(days)

6x LIQ-60

(days)

3x LIQ-60

(days)

2 1.3 0.6 0.4

5 3.2 1.6 1.1

10 6.3 3.2 2.1

15 9.5 4.0 3.2

30 19.0 9.5 6.3

60 37.9 19.0 12.6

Figure 16: Estimated LineIQ Log Average memory usage

Note that with a 2 minute Log Average period, the Gateway memory capacity is exceeded

in less than 1 day with 6 or 9 associated LineIQ CMS.

If the load log data is transferred out of the Gateway at the recommended rate (once per

day as set by the Health check period), then the tables above show that except in extreme

cases of rapid sampling, the Gateway load log memory capacity is never exceeded, so that

no load log data is lost.

For solicited systems, these tables can also be used to estimate the frequency at which the

data must be downloaded from the Gateway.

For example, for a system with 6 LineIQ CMS installed and in which the Log Average

period is set to 30 minutes, it is necessary to download the load log data once a week,

since otherwise the Gateway Log Average memory will overflow after 9.5 days. The

additional 2.5 days of memory capacity would act as a reserve to allow for a download

after say 8 days, as might happen because of unforeseen circumstances such as public

holiday.


11.6 Estimated Download Times

Estimated communication speeds for the five communication systems which can be used

to transfer event and load log data from the Gateway are shown Figure 19 below:

Comms

System

Effective

Throughput Units Comments

Estimated Download Time

(mins)

Internet 115 kB/min direct wired

connection 1.1

mins to transfer event

or load log memory

Direct

RS232

85

kB/min

direct wired

connection, 19 200

Baud

1.5


or load log memory

Cellular

Modem 55 kB/min

based on 9600 baud

overall throughput 2.3


or load log memory

Utility Radio 25 kB/min based on 4800 baud

overall throughput 5.1


or load log memory

RF Link 84 kB/min based on 57600

baud connection 1.5


or load log memory

Figure 17: Estimated Gateway communication speeds

These speeds are limited either by the communication system (cellular modem or utility

radio) or by the Gateway itself (Internet or RS232). The RF link speeds are limited by the

packet system (180 byte packet length) and the half duplex communication system.

The times are shown in seconds, and do not include call set up times.

This table includes down load times for 2, 5, 10, 15, 30 & 60 minute log average periods,

Health Check periods of 1, 2, 4, and 13 & 24 hours and for 3, 6 & 9 associated LineIQ CMS.

The download time is proportional to the amount of load log data collated by and stored in

the Gateway, and this is related to the three input variables modelled in this table:

Log Average period - as this decreases, more load log data is collected by

the LineIQ CMS, and therefore the amount of load log data collated by the

Gateway between each Health Check increases.


Health Check interval – as this increases, the amount of load log data

collated by the Gateway during each Health Check interval increases.

No of associated CMS – as this increases, the amount of load log data

collated by the Gateway during each Health Check interval increases.

The shortest download times occur with the largest Log Average period, the smallest

Health Check interval and the least number of associated LineIQ CMS.

The longest download times occur with the smallest Log Average period, the longest

Health Check interval and the largest number of associated LineIQ CMS.

The user must be aware that with a small Log Average period, long Health Check interval

and large number of associated LineIQ CMS, the capacity of the Gateway load log memory

(128 kB) may be exceeded, and load log data will be lost.

Gateway Health Check download time (sec.) for LIQ-60 via Cellular Modem at 55Kb/min

Health Check

Every Hour

Health Check

Every 2 Hour

Health Check

Every 4 Hour

Health Check

Every 12 Hour

Health Check

Every 24 Hour

Log Average

(mins)

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

2 2 4 5 4 7 10 7 13 19 19 37 56 37 74 111

5 1 2 2 2 3 4 3 5 8 8 15 23 15 30 45

10 1 1 1 1 2 2 2 3 4 4 8 12 8 15 23

15 1 1 1 1 1 2 1 2 3 3 5 8 5 10 15

30 1 1 1 1 1 1 1 1 2 2 3 4 3 5 8

60 1 1 1 1 1 1 1 1 1 1 2 2 2 3 4

Figure 18: LIQ-60 Health Check downloads times using a cellular modem

In Figure 17 above, the Gateway memory capacity is almost exceeded with a 2 minute Log

Average period, a Health Check interval of 24 hours, and 9 associated LineIQ CMS.

With a different communication system, and hence a different data transfer rate, the times

shown in Figure 21 will change proportionately.

For example, if the Health Check data is transmitted using a direct wired internet

connection, the effective data transfer rate increases from 55 kB/min to 115 kB/min, so the

download times shown in Figure 21 will reduce by a factor of 2.1, giving a download time of

45 / 2.1 = 22 seconds for a Gateway monitoring 9 LineIQ CMS with Log Average period of

5 minutes and a Health Check interval of 24 hours.

Figure 19 is similar to Figure 18, but shows download times for LineIQ CMS.


Health Check download time (sec.) for LIQ-60 via Cellular Modem at 55kB/min

Health Check

Every Hour

Health Check

Every 2 Hour

Health Check

Every 4 Hour

Health Check

Every 12 Hour

Health Check

Every 24 Hour

Log Average

(mins)

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

2 7 14 20 10 20 30 20 40 59 56 112 O'flow 112 O'flow O'flow

5 4 7 10 7 14 20 10 20 30 23 46 69 46 98 138

10 4 7 10 4 7 10 7 14 20 14 27 40 23 46 69

15 4 7 10 4 7 10 4 7 10 10 20 30 17 33 50

30 4 7 10 4 7 10 4 7 10 7 14 20 10 20 30

60 4 7 10 4 7 10 4 7 10 4 7 10 7 14 20

Notes 1 Cells shaded red represent senarios where the Gateway load log memory overflows during the health check

Figure 19: LineIQ Health Check download times using cellular model

Note that because of the increased (three times) memory requirements of a LineIQ CMS

compared to a LineIQ CMS, the download times for a given configuration are three times

longer.

Note also that with a 2 minute Log Average period and a long Health Check interval, the

Gateway load log memory will overflow between Health Checks. These cases are shown in

red in Error! Reference source not found.

11.7 Gateway lack of response during Health Checks

While the Gateway is performing a health check, it is unresponsive to events generated by

associated LineIQ CMS, and to external requests (from LineMan Remote or a SCADA

system) for data. This is because the Gateway needs to talk to each associated LIQ-60 to

download the load log data from the CMS over the local radio link.

External requests will be ignored while the Health Check is in progress.

Unsolicited event data from associated LIQ-60 will be ignored. The event data will not be

lost, however, as the automatic retry system means that the CMS will repeatedly try to re-

send the event data. Once the Health Check is completed, the Gateway will respond to

these requests, and the event data will be downloaded into the Gateway.

The amount of time that the Gateway is unresponsive depends on a number of factors:

The Log Average period used in the LineIQ-60 to store load log data – the shorter

the load log interval, the more data has to be downloaded during each Health

Check.


The Health Check interval – a longer Health Check interval increases the amount of

load log data to be downloaded, leading to a commensurate increase in the

download time.

Refer to Figure 20 for a table of times during which a Gateway monitoring LineIQ LIQ-60

CMS is unresponsive to external requests.

Time in minutes during which the Gateway is unresponsive due to LIQ-60 Health Check

Activity

Health Check

Every Hour

Health Check

Every 2 Hour

Health Check

Every 4 Hour

Health Check

Every 12 Hour

Health Check

Every 24 Hour

Log Average

(mins)

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

2 1.0 1.9 2.8 1.3 2.6 3.9 2.2 4.4 6.6 5.5 10.9 16.3 10.5 21.0 31.5

5 0.6 1.2 1.8 0.8 1.5 2.3 1.1 2.3 3.4 2.6 5.1 7.7 4.6 9.1 13.6

10 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.5 2.3 1.5 3.0 4.5 2.6 5.1 7.7

15 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.5 2.3 1.1 2.3 3.4 0.9 3.7 5.5

30 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.2 1.5 0.8 1.5 2.3 1.1 2.3 3.4

60 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.2 1.2 0.6 1.2 1.8 0.8 1.5 2.3

Notes 1 Cells shaded yellow represent scenarios where the Gateway is unresponsive for more than 15 mins during each health check

Cells shaded red represent scenarios where the Gateway is unresponsive for more than 30 mins during each health check 2

Figure 20: Lack of response time during Health Check for LineIQs

GridSense recommends that Health Checks be performed only once per day (i.e. the

Health Check interval is 24 hours), and that the Log Average period be set to 15 minutes.

With these settings, a Gateway monitoring 6 LineIQ-60 CMS is unresponsive for only 3.7

minutes each day. This represents 99.7% availability.

If this site were configured for a Log Average period of 2 minutes with a Health Check every

hour, the Gateway will be unresponsive for 1.9 minutes each hour, or 45.6 minutes each

day, which represents 96.8% availability.

Refer to Figure 21 for a table of times during which a Gateway monitoring LineIQ-60 is

unresponsive to external requests.


Health Check

Every Hour

Health Check

Every 2 Hour

Health Check

Every 4 Hour

Health Check

Every 12 Hour

Health Check

Every 24 Hour

Log Average

(mins)

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

3 x

LIQ‐60

6 x

LIQ‐60

9 x

LIQ‐60

2 1.3 2.6 3.9 2.2 4.4 6.6 3.8 7.7 11.5 10.5 21.0 O'flow 20.4 O'flow O'flow

5 0.8 1.5 2.3 1.1 2.3 3.4 1.9 3.7 5.5 4.6 9.1 13.6 8.5 17.0 25.5

10 0.6 1.2 1.8 0.8 1.5 2.3 1.1 2.3 3.4 2.6 5.1 7.7 4.6 9.1 13.6

15 0.6 1.2 1.8 0.8 1.5 2.3 1.0 1.9 2.8 1.9 3.7 5.5 3.1 6.2 9.3

30 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.5 2.3 1.1 2.3 3.4 1.9 3.7 5.5

60 0.6 1.2 1.8 0.6 1.2 1.8 0.8 1.2 1.8 0.8 1.5 2.3 1.1 2.3 3.4

Notes 1 Cells shaded yellow represent senarios where the Gateway is unresponsive for more than 15 mins during each health check

Cells shaded red represent senarios where the Gateway load log memory overflows during the health check 2

Figure 21: Lack of response time during Health Check for LINEIQs

With the GridSense recommended Health Check interval of 24 hours, and the GridSense

recommended Log Average period of 15 minutes, a Gateway monitoring 6 LineIQ LIQ-60is

unresponsive for only 6.2 minutes each day. This represents 99.6% availability.

11.8 Real Time Clock (RTC)

The Gateway includes a battery backed real time clock (RTC).

During normal Gateway operation (when the Gateway is turned on), the RTC is powered

directly from the Gateway, and the RTC backup battery is not used.

The RTC backup battery is only used when the Gateway is switched off.

The estimated RTC backup battery life is 10 years.

The Real Time Clock is set during the manufacturing process.

The RTC backup battery is a lithium button cell, type CR2032, and is located on the

Gateway printed circuit board (PCB). Access to the PCB is obtained by removing the

access plate under the cellular modem.

Please contact GridSense if you need to reset the Real Time Clock or replace the RTC

backup battery.

In order to conserve internal memory and maximize transmission efficiency, and to maintain

compatibility with earlier Series 1 LIQ-60 and PACs, the RTC is not used directly. Instead, it

is used to set an internal counter which is then used to provide a date and time reference

for event and load log data.


When event and load log data is processed by LineMan or LineMan Remote software, the

counter date/time stamp values are converted to conventional date/time stamps, using the

clock of the PC on which the software is running as a reference.

For this reason, it is important that the PC date and time be set correctly on the PC before

event and load log data is downloaded from LIQ-60 and Gateways.

11.9 Solar Panel Mounting Considerations

The solar panel supplies all the energy required to operate the Gateway, and must provide

enough energy to ensure that the internal Gateway battery pack remains charged.

The solar panel converts the energy contained in sunlight directly into electrical energy.

Correct orientation of the solar panel is important, especially at high latitudes.

The amount of energy generated depends on the following factors:

The amount of incident solar energy. This energy is provided by the sun, and varies with

the time of day, the time of year, the latitude and with the amount of cloud cover.

The angle at which the incident solar energy strikes the solar panel.

The amount of shading (by nearby structures) or obstruction (e.g. by snow or dust) of the

solar panel.

The Gateway solar panel has an adjustable mount, which allows the solar panel to be

oriented for maximum energy generation.

Since the amount of incident solar energy varies with seasons (more in summer, less in

winter) it is better to orient the solar panel to maximize the solar energy in winter rather than

in summer.

The following step by step process details how to mount the solar panel correctly:

1. Determine the direction to the equator. In the northern hemisphere this is due

south, while in the southern hemisphere it is due north. Note that you must

determine the true rather than the magnetic direction, as these vary considerably.

This direction can be determined in a number of ways:

Use an atlas, a physical map or a street directory

Use an internet based geographic information system such as Google Earth

Determine the direction to the sun at 12 noon in winter (or 1pm during

daylight saving times)


Use an electronic compass such as a Global Positioning System (GPS)

receiver

Use a magnetic compass, corrected for magnetic deviation.

It is sufficient to determine the direction to the equator to within 5 degrees.

Mount the solar panel so that in plan view it points directly towards the equator

– true south in the northern hemisphere

– true north in the southern hemisphere

Figure 22 shows how the solar panel is positioned in the Northern hemisphere.

Figure 22: Solar panel facing the equator (Northern hemisphere mounting)

2. Determine the latitude. This is your position on the earth, measured in degrees.

If you are at the equator, your latitude will be 0 degrees.

If you are at the North Pole, your latitude will be 90 degrees north.

If you are at the South Pole, your latitude will be 90 degrees south.

The latitude of Sydney, NSW in Australia is approximately 35 degrees South

The latitude of Sacramento CA in the United States of America is 40 degrees

North


You can determine your latitude in a number of ways:

Use an atlas, a physical map or a street directory

Use an internet based geographic information system such as Google Earth

Use an electronic positioning system such as a Global Positioning System

(GPS) receiver

It is sufficient to determine your latitude within 5 degrees.

Use the following table to determine the angle at which to mount the solar panel. The angle

specified in Figure 23 is measured from the face of the solar panel to the vertical.

Latitude

Example Location

Winter Elevation

Angle from vertical

(degrees)

Autumn/Spring

Elevation Angle

from vertical

(degrees)

Summer Elevation

Angle from vertical

(degrees)

Average Elevation

Angle from Vertical

(degrees) 90 N North Pole no sun 10 20 15

80 N no sun 15 30 23

70 N North West Passage no sun 20 40 30

60 N Kodiak, Alaska USA 10 30 50 30

50 N Vancouver, BC Canada 20 40 60 40

40 N Sacramento, CA USA 30 50 70 50

30 N Houston, Texas USA 40 60 80 60

20 N Mexico City, Mexico 50 70 90 70

10 N Nairobi, Kenya 60 80 90 77

0 Singapore 70 80 90 80

10 S Darwin NT Australia 60 80 90 77

20 S Alice Springs NT Australia 50 70 90 70

30 S Sydney, NSW Australia 40 60 80 60

40 S Hobart, TAS Australia 30 50 70 50

50 S Invercargill New Zealand 20 40 60 40

60 S Southern Ocean 10 30 50 30

70 S Mawson Base, Antarctica no sun 20 40 30

80 S no sun 15 30 23

90 S South Pole no sun 10 20 15

Figure 23: Solar panel angle measured from vertical

The rightmost column is the average of the winter. Autumn/spring and summer columns.

Use this angle if you are not going to change the angle as the seasons change.

Figure 24 shows how the solar panel angle is measured.


Figure 24: Solar panel angle measured from vertical


12 Maintenance

12.1 Standby battery

The Gateway includes a sealed lead acid standby battery.

The performance of the standby battery will degrade if it is exposed to long periods of high

temperature and/or it is allowed to discharge excessively.

The battery life of the Gateway can be extended by following a few simple precautions as

outlined below:

Store the Gateway at ambient temperatures below 30o C

Store the Gateway with a fully charged battery. This can be achieved by energizing

the Gateway for 24 hours before storage

Recharge the battery after every three months of storage

12.2 Calibration

The Gateway does not require calibration.

12.3 Cleaning

All equipment should be cleaned with a soft, moist cloth using only a mild detergent.

12.4 Periodic Maintenance and Testing

The Gateway and accessories should be inspected on a regular basis.

12.5 Operational Problems

If you have any questions about the operation of the Gateway or associated software

(LineMan, Lineman Remote, and LineView), first look in the relevant User Manual or consult

the on-line help files included with the software.


12.6 Firmware and Software Upgrades

The Gateway is a complex instrument which utilizes embedded firmware and PC based

software (LineMan, Lineman Remote, and LineView).

GridSense occasionally releases firmware upgrades for the Gateway and new versions of

LineMan, Lineman Remote, and LineView software.

Users who have electronically registered with GridSense will be notified of firmware

upgrades and new versions of LineMan, LineMan Remote, and LineView

Updated firmware and software can be downloaded from the GridSense web site after

registering at:

http://www.gridsense.com/customer-downloads/

The customer download webpage is only accessible after customer login.

Firmware upgrades are accomplished using the Gateway Firmware Upgrade Tool.

This is a small program (Gateway_FW_Upgrade.exe) which connects to the Gateway via

either a serial port or a direct Ethernet connection.

Refer to “Appendix H – Gateway Firmware Upgrades” for detailed instructions on how to

upgrade the Gateway firmware

12.7 Repairs

The Gateway and accessories do not contain any user serviceable parts.

If the equipment is found to be faulty in any way, including blown fuses, it should be

returned to your supplier for inspection and repair.

If service is required, return the Gateway and all accessories to GridSense at the addresses

shown below.

NORTH AMERICA

GridSense Inc.

2568 Industrial Blvd, Ste. 110

West Sacramento CA 95691

USA

12.8 Customer Registration

GridSense suggest that you register as a customer on the GridSense web site:

http://www.gridsense.com/customer-downloads/


http://www.gridsense.com/gridsense-login/

Registered customers are able to download firmware and software upgrades from the

GridSense web site.

12.9 Technical Sales and Assistance

If you are experiencing any technical problems, or require any assistance with the proper

use or application of this instrument, please contact us:

NORTH AMERICA

Phone: +1 916 372 4945

Fax: +1 916 372 4948

Support: http://www.gridsense.com/product-support/

Web: http://www.gridsense.com/

http://www.gridsense.com/gridsense-login/

http://www.gridsense.com/product-support/

http://www.gridsense.com/product-support/

http://www.gridsense.com/


13 Gateway Specifications

INTERFACES

Internal Memory 512 kB non volatile

Internal Radio serial

port

RS232 via male DB9 connector

1 start bit, 8 data bits, no parity & 1 stop bit with RTS/CTS flow control

Baud rates 1200, 2400, 4800, 9600, 19200, 28800, 57600 & 115200

baud

Internal Modem serial

port

RS232 connector or PCB socket


RS232: male DB15 connector. Baud rates 1200, 2400, 4800, 9600,

14400, 19200, 28800, 33600 & 57600 baud

PCB socket: TTL logic. Baud rates 1200, 2400, 4800, 9600, 14400,

19200, 28800, 33600 & 57600 baud

External serial port

RS232 via DB9 serial data cable.


Baud rates 1200, 2400, 4800, 9600, 14400, 19200, 28800, 33600,

57600 & 115200 baud

RF Interface port Proprietary TTL level interface to RF module.

Ethernet interface

port

10/100 MHz 10-base-T

Global Positioning

System (GPS)(2)

50-channel GPS receiver with -160dBm SuperSense ® sensitivity,

active Antenna and accurate time keeping options. ® SuperSense is a

registered trademark of u-blox AG

Internal WiFi

Module(3)

IEEE 802.11 b/g (11/54MBps), Wi-Fi compliant, with support for WEP

(64 and 128 bit), and WPA (TKIP). 4MBps effective data throughput. -

71dBm to -87dBm sensitivity.

Communication

protocols DNP3 & GridSense proprietary


MECHANICAL & POWER

Display Amber and Red high intensity LEDs

Power Consumption 8 mA at 12 V DC with no active communications

AC Power 55 – 600 Volts AC 50 Hz or 60 Hz

Solar Power External 12 V 10 W solar panel

DC Power 13.8 V DC rated at 1 Amp

Backup Battery 12 V 5 Ah rechargeable sealed lead acid

Real Time Clock

Battery CR2032 3V lithium

Dimensions (l x w x d) 510 mm (20 in) x 295 mm (11 5/8 in) x 160 mm (6 5/16 in) 20 in (l) x

(w) x (d)

Weight 7.6 kg (17 lbs) Gateway only, 15kg (33 lbs) typical with accessories in

shipping case

ENVIRONMENTAL & SAFETY

Temperature -20°C to +60°C (-4°F to +130°F)

Humidity 20% to 99% RH

Protection Class AS 60529-2004 - IP65

ABSOLUTE MAXIMUM RATINGS

Supply Voltage 600 Volts

DC Power 14 Volts

Solar Panel Voltage 30 Volts


14 Accessory Specifications

14.1 10 W External Solar Panel

SPECIFICATIONS

Nominal Rating 10 W at 12 VDC

Open Circuit Voltage 21 V

Short Circuit Current 700 mA

Nominal output 16.8 V

Nominal output 600 mA

Rated output 10 W at 800 W/m2 and 47 oC

Dimensions (l x w x 421 mm (16 9/16 ins) x 269 mm (10 9/16 in) x 23 mm (7/8 in)

Weight 2 kg


APPENDIX A – LINEMAN

A1 Installing LineMan To install LineMan software, insert the CD supplied with the Gateway into a CD drive.

If the installer does not start automatically, browse to the LineIQ directory on the CD and

run the LineMan setup program.

Follow the on screen instructions to install LineMan software.

A2 Starting LineMan Start LineMan by double clicking on the desktop icon, or selecting it from the Start Menu.

Start/Programs/GridSense/LineIQ/LineMan/LineMan.exe

The splash screen shown will appear for 1 second.

The LineMan opening screen will then appear as shown below:

Figure 25: LineMan Opening Screen

In the pull down box in the Lineman connection screen, select the appropriate

Communications Port and then click on the “Connect to LineIQ” button.


Figure 26: LineMan Connection Screen

If this screen is not shown, the communications port can be selected using the pull down

menu on the right hand end of the menu bar, as shown below:

Figure 27: Selecting the Communications Port from the pull down menu

Once the correct communications port is selected use the File/Start command to initiate

communications.

LineMan will then scan for all available devices. The Gateway will appear, along with any

other nearby devices, in the device list.

Select the Gateway in the device list.

The following commands can then be used:

Status - provides details of the battery voltage, battery drain current,

charging voltage, charging current and internal temperature.


Summary – provides details of serial number, firmware version, hardware

revision and other parameters.

Configure – allows the Gateway to be configured.

Data Download – allows data to be downloaded. This command is normally

used only with conductor mounted sensors (CMS).

Commission – allows the Gateway to be commissioned. This should only be

done after the entire site (Gateway and LineIQs) have been correctly

configured.

Restart – performs a warm restart (reboot) of the Gateway microprocessor,

and is equivalent to switching the power off then on again.


APPENDIX B – LINEMAN REMOTE LineMan Remote allows remote connection to a Gateway.

In order for LineMan Remote to initiate communications with a Gateway, the Gateway must

be powered externally. This can be achieved by one of the following methods:

An external solar panel with sufficient capacity to power the Gateway and

associated modem at all times.

An external AC power supply.

In order to allow LineMan Remote to connect to a Gateway, the Gateway must be fitted

with a suitable remote communication interface.

This interface can be one of the following:

A modem connected to a standard PSTN telephone line.

A cellular modem.

A working internet connection.

Using LineMan Remote, two main functions can be performed:

Log and event data can be downloaded.

Gateway status and line current (along with line temperature if LIQ-

60devices are installed) can be monitored.


Figure 28: LineMan Remote Connection Screen

For further information on using LineMan Remote, refer to the LineMan Remote User

Manual.


APPENDIX C – INTERNAL ETHERNET MODULE

C1 Introduction The Internal Ethernet Module consists of a small printed circuit board (PCB) which is

mounted into J3 on the main Gateway PCB.

The RJ45 internal loom which is required to connect the Ethernet Module to the Data

connector on the front panel is already installed in all Gateways.

An external cable with an RJ45 connector is provided with the Internal Ethernet Module to

allow connection to a standard 10BaseT Ethernet system.

Figure 29: Internal Ethernet module kit

Figure 30: Internal Ethernet module


C2 Installation To install the internal Ethernet Module, you will need a large flat bladed screwdriver and a

small pair of side cutters.

a) Open the front cover of the Gateway.

Figure 31: Gateway with cover opened

Note that the Gateway may not look exactly the same as shown in Figure 31, as it may

have cellular and radio modems installed.

b) Remove the Main Shield Cover by undoing the two captive screws at the

bottom of the cover.

The Internal Ethernet Module is supplied in an antistatic bag. Do not remove the module from the

antistatic bag until you are ready to install it. Appropriate antistatic measures should be used during

installation.


Figure 32: Gateway with main shield cover removed

The RJ45 internal wires can be seen at the bottom left hand corner of Figure 32.

c) Locate S3, which is the center pair of white single in line (SIL) 8 pin female

connectors.

Figure 33: Centre pair of SIL 8 pin female connectors (at bottom)

d) Insert the Internal Ethernet Module into S3. Ensure that the correct

orientation is used. The RJ45 connector must be on the right.


Figure 34: S3 connector (bottom pair of SIL female connectors)

e) Remove the cable tie holding the RJ45 wiring loom on the left of the

Gateway. This is shown in Figure 32.

f) Route the RJ45 wiring loom underneath the two antenna cables, and

connect it to the Internal Ethernet Module.

g) Make sure that the Internal Ethernet Module is securely and fully located

onto J3.

h) Replace the Main Shield Cover, making sure that all cables are routed

through the appropriate glands and are not pinched by the cover in any way.

i) If necessary, secure any loose cables to the wiring loom on the left hand

side of the Gateway with cable ties.


Figure 35: Internal RJ45 connector inserted into internal Ethernet module

Figure 36: Internal RJ45 connector inserted into internal module (main shield cover replaced)

j) If necessary, secure any loose cables to the wiring loom on the left

hand side of the Gateway with cable ties.

k) Close the front cover of the Gateway.

l) Unscrew the sealing cap and connect the external Ethernet cable

to the data connector on the front panel of the Gateway.


Figure 37: External RJ45 cable connected to Data Connector

If the external Ethernet cable is ever removed, the sealing cap must be replaced to prevent

corrosion of the Data connector.


APPENDIX D - DNP3 COMMUNICATIONS

D1 Introduction Critical fault data as well as load logging data and device status information is available

through the versatile industry standard DNP3 interface.

The interface is highly configurable and should be set up to best fit your application. The

purpose of this appendix is to explain how to achieve this using LineMan software. If you

are not familiar with LineMan, consult the LineMan User Manual.

The DNP3 interface can be configured to provide both solicited and unsolicited

communications. Event and load log data, as well as status information can be accessed

via the DNP3 interface.

D2 Locating the DNP3 Interface Settings Referring to “Error! Reference source not found.” below, select the Gateway in the

LineIQ ID List window (1), then access the device configuration settings by pressing the

Device Config button (2).


Figure 38: LineMan main screen

This will open the Sensor Configuration pane, shown on the right in Figure 38.

D3 Selecting the Health Check Interval Historical data, such as load logging information, is accumulated first in the conductor

mounted sensors and only transferred to the Gateway during the periodic ‘Health Check

(3)’. Therefore such data only becomes available to the external DNP3 master device after

each health check.

The health check interval should therefore be chosen with consideration to how time-

critical the historical information is to the external system.


When choosing the health check interval the longest acceptable interval should be chosen

to limit battery drain on the LineIQs due to the power required for the short range RF

communications between the Gateway and the LineIQs during health checks.

Typically 2 hours is considered the absolute shortest acceptable health check interva l .

D4 Changing the DNP3 Interface Settings

The DNP3 interface settings are located under the Interface Control settings, which are

accessed by pressing the Communication Settings w indo w.

This will open Figure 39 as shown below.

Figure 39: IFC setting window

10


D5 Selecting and configuring the DNP3 RS232 Port This will be either the internal RS232 port intended for connection to utility radios, or the

external RS232 data port.

In area 7 above, select the desired baud rate on the appropriate port using the drop-down

menu, and select whether to implement RTS/CTS hardware flow control on the selected

port.

D6 Permanently powering the radio modem In area 8 above, if you are using the internal RS232 port and utility radio, ensure that the

radio is permanently powered on (box ticked).

D7 Setting DNP3 Protocol Parameters In the lower right of Figure 39, the following options are available:

DNP3 Unsolicited Reporting

Otherwise known as ‘Report by Exception’, this setting determines whether the Gateway

can be configured to send unsolicited reports. Note that in accordance with the DNP3

standard, all classes of unsolicited data are disabled by default and must be enabled as

required by the master device via the Enable/Disable unsolicited reporting commands. The

Gateway will send an unsolicited Null Response on start up to indicate device restart .

Things to Note:

Unsolicited data can only be enabled or disabled by class. See the GatewayDNP3

points-list in Appendix E to determine the class of each data point.

The Gateway is a DNP3 Level 1 device and does not support dynamic class

assignments.

When unsolicited reporting is enabled another selection becomes available in the

IFC Settings to configure the hardware port to which unsolicited reports are sent.

When using unsolicited reporting it is critical to configure the Link Destination

Address to that of the attached DNP3 master device.

Modem and Ethernet support are under development. Contact GridSense for further

details.

GridSense Recommended Setting: Where the master station supports unsolicited

messages from outstations, it is recommended that this feature is enabled, to

p r o v i d e


Immediate notification of new data. This will eliminate communications channel congestion

due to polling. DNP3 Static Polling (see next bullet-point) can allow for infrequent polling of

instantaneous line parameters.

DNP3 Static Polling (Do RF Status Command)

This checkbox determines the Gateway behavior when it receives a request for the value of

static data points from the DNP3 master. Since the Gateway is physically isolated from the

LineIQ devices it is monitoring, to determine the instantaneous status of a device (such as

the instantaneous line current) it must send out a request over the local RF communications.

The low-power nature of the LineIQ devices requires that this RF command be used

sparingly. It may be difficult or undesirable to re-configure the DNP3 master to only poll

these points rarely, so this checkbox is provided to enable or suppress the RF command

when a poll request is received from the DNP3 master.

To leave this box Unchecked is to configure the Gateway to return the last known value

when these static points are requested. This value will have been retrieved during the last

‘Health Check’, which occurs at a configurable interval (see more details of health check

intervals below).

Things to Note:

DNP3 requests which trigger RF commands will not receive a response from the

Gateway until after the RF communications are complete. This may take several

minutes depending on the number of LineIQs assigned to the Gateway.

GridSense Recommended Setting: When using a polling method to retrieve data from the

outstation, this checkbox should be left unchecked. Where unsolicited reporting (report by

exception) is used to retrieve outstation data, this box should be checked to allow

instantaneous line parameters to be read when desired.

DNP3 Waveform Support

Fault current and voltage waveforms are available to be retrieved through the DNP3

interface as data object 111 (Octet String Event).

Since each waveform consists of 249 Bytes and this data object 111 is not supported by

some DNP3 masters, the option is provided here to choose whether or not waveform data

is generated.


Things to Note:

Waveform data is a separate DNP3 class to the fault summary data. This allows

the DNP3 master to enable unsolicited reporting of summary data but not

waveform data, and the waveform can be retrieved if desired.

One voltage and one current waveform is stored for each LineIQ event. When

the Gateway internal memory fills up, the oldest (earliest) waveforms will be

overwritten.

When the waveform data is extracted, the extracted waveforms are cleared from

the Gateway memory.

GridSense Recommended Setting: This box should only be checked if the user expects

to use waveform data to analyze fault information. If such data is not desired the box

should be left unchecked to limit the amount of data transferred over the communications

channel.

Clock Validation Period

This is the time period in minutes between which the Gateway will set the Time

Synchronization Required IIN bit in the DNP3 application layer frame. The master should

send a time synchronization message.

Things to Note:

Setting this parameter to 0 disables periodic time synchronization requests. The

IIN bit will only be set on restart.

GridSense Recommended Setting: This parameter should be set for daily time

synchronization (every 86400 seconds) if the master station has access to an accurate time

source and the latency of the communications channel is small. In other cases the value

should be set to 0 to prevent periodic time synchronization r e q u e s t s .

Unsolicited Max Short Retries

Determines the number of times the Gateway will attempt to send unsolicited messages at

the configurable short retry interval if the master does not acknowledge the message.

Once this number of retries has expired, the Gateway will send retries indefinitely at the

configurable long retry interval.


GridSense Recommended Setting: This parameter, combined with the unsolicited short

retry delay, should be set such that the Gateway will always attempt to resend unsolicited

messages for longer than the time a master station might be expected to be unresponsive

doing other tasks. Should a master station never be expected to be unresponsive, then a

default of 3 short retries should be applied.

Link Source Address

The address of the Gateway at the DNP3 Link Layer. The Gateway will only respond to

requests sent to this address.

GridSense Recommended Setting: This parameter is entirely dependent on the

requirements that the master station places on the addresses of outstations.

Link Destination Address

The DNP3 Link Layer address to which the Gateway will send all unsolicited messages.

Things to Note:

This address is for unsolicited messages only, the Gateway will respond to any

requests with the GatewayDNP3 address in the destination field.

Responses will be addressed to the sender of the request, even if that differs

from the address configured here.

GridSense Recommended Setting: Good design practice is to set, this parameter to the

address of the master station even if unsolicited reporting is not being us ed .

App. Confirmation Timeout

The time in seconds to wait for the master to confirm a DNP3 application layer message.

Once this time elapses, the Gateway considers the message lost and aborts sending any

remaining fragments and starts the retry timer (if the message is unsolicited).

GridSense Recommended Setting: This parameter should be set to at least quadruple the

maximum expected one-way latency of the communications channel or double the

maximum expected time the master station will be unresponsive handling other tasks

(whichever is longer). If neither of these parameters is known, a default value of 30 seconds

should be adequate for the majority of installations.


Unsolicited Short Retry Delay

The time in seconds to wait before resending an unsolicited message that was not

confirmed by the master.

The number of retries sent at this interval is configurable.

Things to Note:

This delay begins at the end of the configurable application layer confirmation

timeout.

GridSense Recommended Setting: This parameter, combined with the max. number of

unsolicited short retries, should be set such that the Gateway will always attempt to resend

unsolicited messages for longer than the time a master station might be expected to be

unresponsive doing other tasks. Should a master station never be expected to be

unresponsive, then a default of 30 seconds should be applied.

Unsolicited Long Retry Delay

The time in seconds to wait before resending an unsolicited message after the configurable

number of short retry attempts has been exhausted.

The Gateway will continue to send the message at this interval indefinitely until

acknowledged by the master.

GridSense Recommended Setting: Unsolicited long retries are a fallback if the master

station has failed to respond to short retries for longer than should ever be expected under

normal circumstances. This would usually be as a result of a failure of the communications

channel or a serious problem with the DNP3 master station. In this case a recommended

retry of every hour (3600 seconds) should allow for prompt recovery once the

communications channel or master station is restored.


D8 Other Pertinent Parameters

Maximum Supported Fragment Sizes

DNP3 Link Layer Tx Frame 146 Bytes

DNP3 Application Layer Tx Fragment 300 Bytes

DNP3 Application Layer Rx Fragment 512 Bytes

DNP3 Commands During Health Check or Event Data Download

When the Gateway is occupied conducting a health check on the LineIQs or retrieving

event data, it will not respond to DNP3 requests.

If the time from receiving the request until the Gateway becomes idle exceeds 32 seconds,

the Gateway will consider the request expired and discard it without r e s p o n s e .

D9 Checklist for Configuring the Interface

1. Enable the DNP3 protocol handler by ensuring the Enable DNP3 checkbox is

checked.

2. Configure the hardware interface (7).

3. If an internal radio is being powered from the Gateway internal dedicated radio

power, ensure the checkbox Permanently Power Radio (8) is selected.

4. Configure the protocol parameters (9). These are each described earlier in this

document.

5. Close the IFC Settings dialog (10) and apply the configuration.

6. Configuration changes are not saved until the Apply Configuration button (4) is

pressed.

7. Commission the Gateway, by pressing the Commission (Remote) button (5). The

Gateway needs information it retrieves during the commissioning process to

properly respond to DNP3 requests. As a result, the protocol handler is not started

until after commissioning, even if the Enable DNP3 setting has been applied.


APPENDIX E – RECOMMENDED DNP3 POINTS USAGE

Obj Var Description Obj Var Class Description

0 000 30 2Analog Input -- 16-bit

with flagBattery Voltage -- PAC

Static Variation Recommended for

DataPAC battery health check. divided by 100



with flag

Instantaneous* Battery Voltage --

CMS G1P1

Recommended for battery health

check.divided by 100


with flag

Instantaneous* Line Voltage Indication -

- CMS G1P1

Static Variation Optional - Can be

polled infrequently for real time

indication of line voltage

times 100


with flag32 4 1

Analog Input Event -- 16-

bit with time

Most Recent Trigger Current / Event

Trigger Current -- CMS G1P1

Event Variation Recommended for

fault current magnitude.divided by 10


with flag32 4 1


bit with time

Most Recent Pre-Trigger Current / Pre-

Trigger Current --CMS G1P1


pre-event line current informationdivided by 10


with flag32 4 1


bit with time

Most Recent Pre-Trigger Current / Pre-

Trigger Current --CMS G1P1


post-event line current informationdivided by 10


with flag32 4 2


bit with time

Instantaneous* Current / Load Log

Current -- CMS G1P1

Static Variation Optional Can be

polled infrequently for instantaneous

load readings / Event Variation

Recommended for long term load

trend study.

divided by 10


with flagLineFrequency -- CMS G1P1


polled infrequently for line frequency

readings. LineTracker support

dependent

divided by 10


with flag

32 4 3


bit with time

Displacement Power Factor

(Instantaneous* / Historical) -- CMS

G1P1


polled infrequently for taking

instantaneous power factor

readings.


long term historical power factor

study. LineTracker support

dependent

divided by 1000


with flag

32 4 3


bit with time

Phase Angle (Instantaneous* /

Historical) -- CMS G1P1



instantaneous phase angle

readings.


long term historical phase angle

study.LineTracker support

dependent

divided by 10

10 00A 30 2Analog Input -- 16-bit

with flag

32 4 2


bit with time

Ambient Temperature (Instantaneous*

/ Historical) -- CMS G1P1



instantaneous ambient temperature

readings.


long term historical ambient

temperature study.LineTracker

support dependent

divided by 100

11 00B 30 2Analog Input -- 16-bit

with flag

32 4 2


bit with time

Conductor Temperature

(Instantaneous* / Historical) -- CMS

G1P1



instantaneous conductor

temperature readings.


long term historical conductor

temperature study. LineTracker

support dependent

divided by 100


0 001 1 2Binary Input -- With

Flags2 2 1

Binary Input Event -- With

absolute time

Most recent event type SI (Short

Interruption) / Event Type - SI -- CMS

G1P1


line event classification.not applicable


Flags2 2 1


absolute time

Most recent event type LI (Long

Interruption) / Event Type - LI -- CMS

G1P1




Flags2 2 1


absolute time

Most recent event type FP (on the

Fault Path) / Event Type - FP -- CMS

G1P1




Flags2 2 1


absolute time

Most recent event type PR (Power

Return) / Event Type - PR -- CMS

G1P1




Flags2 2 1


absolute time

Most recent event type Pre-Trigger

Power Status / Event Type - Pre-

Trigger Power Status -- CMS G1P1




Flags2 2 1


absolute time

Most recent event type Post-Trigger

Power Status / Event Type - Post-

Trigger Power Status -- CMS G1P1



* Note: If RF Comms are disabled (default setting) during DNP3 polling, then the returned analog reading was taken at the time of the preceeding DataPAC health check.

If RF Comms are enabled during DNP3 polling, then the returned analog reading is a "real time" value read from the CMS at the time of DNP3 polling.

Point Name

Event Variation

Point

Index

(Dec)

Note

Static Variation Event Variation

Point

Index

(Dec)

Analog points usage recommendations - LineTracker points (block is repeated for each assigned LineTracker)

Static Variation

Point

Index

(Hex)

Point Name

Static Variation / Event Variation

Point Name

Static Variation / Event VariationNote

Point

Index

(Hex)

Analog points usage recommendations - DataPAC points

Scaling

Scaling

Binary Points Usage Recommendations (block is repeated for each assigned LineTracker)

Point

Index

(Dec)

Point

Index

(Hex)

Static Variation Event Variation

Note

Scaling


APPENDIX F – DNP3 DEVICE PROFILE

F1 Device Identification

DEVICE

IDENTIFICATION Capabilities Current Value

If configurable,

list methods

Device Function: Master

Outstation

Master

Outstation

Vendor Name CHK GridSense

Device Name Gateway Device manufacturer’s

hardware version

string:

Device manufacturer’s

software version

string:

Device Profile Document

Version

Number:

0.1.3

DNP Levels Supported for: Outstations Only:

None

Level 1

Level 2

Level 3

Level 4

None

Level 1

Level 2

Level 3

Level 4

Supported Function Blocks: Self-Address Reservation

Object 0 – attribute objects

Data Sets

File Transfer

Virtual Terminal

Mapping to IEC 61850 Object

Models defined in a DNP3 XML

file

Function code 31, activate

configuration

Self-Address Reservation

Object 0 – attribute objects

Data Sets

File Transfer

Virtual Terminal


DEVICE IDENTIFICATION

Capabilities

Current Value

If configurable,

list methods

Notable Additions:

A brief description intended to

quickly identify for the reader the

most obvious features the

device supports in addition to

the Highest DNP Level

Supported. The complete list of

features is described in the

Implementation Table.

· Binary input - All Variations :

Read all points

· Analog input - All Variations :

Read all points

Methods to set Configurable

Parameters:

XML – Loaded via DNP3 File

Transfer

XML – Loaded via other

transport mechanism

Terminal – ASCII Terminal

Command Line

Software – Vendor software

named

Proprietary file loaded via

DNP3 file transfer

Proprietary file loaded via other

transport mechanism

Direct – Keypad on device front

panel

Factory – Specified when

device is ordered

Protocol – Set via DNP3 (e.g.

assign class)

Other – explain

Software – Vendor software

named: Line Man

Connections Supported: Serial (complete section

1.2)

IP Networking (complete

section 1.3)

Other, explain

Serial (complete section

1.2)

IP Networking (complete

section 1.3)

Other, explain

SERIAL CONNECTIONS Capabilities Current Value If configurable,

list methods


Port Name

Name used to reference the

communication port defined

in this section.

Electrical Interface: RS232, GSM

or GPRS, CDMA or CDMA1x.

Type of connector: 9 pin SUB-D,

male

Serial Connection

Parameters:

Asynchronous - 8 Data Bits, 1

Start Bit, 1 Stop Bit, No Parity

Other, explain

Asynchronous - 8 Data Bits, 1

Start Bit, 1 Stop Bit, No Parity

Other, explain

Baud Rate: Fixed at

Configurable, range to

Configurable, selectable from

, ,_

Configurable, other,

describe

Fixed at



1200, 2400, 4800 , 9600, 14400,

19200, 28800,33600, 57600 ,

115200,


describe

Configuration is

done by vendor

provided LineMan

software.

Hardware Flow Control

(Handshaking):

Describe hardware

signaling requirements of

the interface.

Where a transmitter or

receiver is inhibited until a

given control signal is

asserted, it is considered

to require that signal prior

to sending or receiving

characters.

Where a signal is asserted

prior to transmitting, that

signal will be maintained

active until after the end of

transmission.

Where a signal is asserted

to enable reception, any

data sent to the device

when the signal is not

active could be discarded.

None

RS-232 / V.24 / V.28 Options:

Before Tx, Asserts:

RTS

DTR

Before Rx, Asserts:

RTS

DTR

Always Asserts:

RTS

DTR

Before Tx, Requires: Asserted

De-asserted

CTS

DCD

DSR

RI

Rx Inactive

Before Rx, Requires: Asserted

Disserted

CTS

DCD

DSR

RS-232 / V.24 / V.28 Options:

Before Tx, Asserts:

RTS

DTR

Before Rx, Asserts:

RTS

DTR

Always Asserts:

RTS

DTR

Before Tx, Requires: Asserted

De-asserted

CTS

DCD

DSR

RI

Rx Inactive

Before Rx, Requires: Asserted

Disserted

CTS

DCD

DSR

Configurable by

vendor provided

software –

LineMan.


RI

Always Ignores:

CTS

DCD

DSR

RI

Other, explain

RS-422 / V.11 Options:

Requires Indication before

Rx

Asserts Control before Tx

Other, explain

RS-485 Options:

Requires Rx inactive

before Tx

Other, explain

RI

Always Ignores:

CTS

DCD

DSR

RI

Other, explain enable or

disable Hardware Flow Control

is configurable.


F2 Link Layer

LINK LAYER Capabilities Current Value If configurable,

list methods

Maximum number of octets

Transmitted in a Data Link Frame:

This number includes the CRCs. With

a length field of 255, the maximum

size would be 292.

Fixed at



, ,_


describe

Fixed at

146_

Maximum number of octets that

can be Received in a Data Link

Frame:

This number includes the CRCs. With

a length field of 255, the maximum

size would be 292. The device must

be able to receive 292 octets to be

compliant.

Fixed at



, ,_


describe

Fixed at

146_

Maximum Data Link Retries:

The number of times the device will

retransmit a frame that requests Link

Layer confirmation.

Never Retries

Fixed at



, ,_ Configurable,

other, describe

Fixed at 3.

Sends Confirmed User Data

Frames:

A list of conditions under which the

device transmits confirmed link layer

services (TEST_LINK_STATES,

RESET_LINK_STATES,

CONFIRMED_USER_DATA).

Always

Sometimes, explain

Never

Never

Data Link Layer Confirmation

Timeout:

This timeout applies to any

secondary data link message that

requires a confirm or response (link

reset, link status, user data, etc.)

None

Fixed at_ ms


ms


, , ms


describe

Variable, explain

None


F3 Application Layer

APPLICATION

LAYER Capabilities Current Value

If configurable,

list methods

Maximum number of

octets Transmitted in an

Application Layer

Fragment other than File

Transfer:

This size does not include

any transport or frame

octets.

• Masters must provide a

setting less than or equal

to 249.

• Outstations must provide

a setting less than or equal

to 2048. .

Fixed at



, ,_


describe

Fixed at _512



, ,_


describe

Maximum number of

octets Transmitted in an

Application Layer

Fragment containing File

Transfer:

Fixed at



, ,_


describe

Maximum number of

octets that can be

Received in an

Application Layer

Fragment:

This size does not include

any transport or frame

octets.

• Masters must provide a

setting greater than or

equal to 2048.

• Outstations must provide

a setting greater than or

equal to 249.

Fixed at



, ,_


describe

Fixed at 512



, ,_


describe


APPLICATION

LAYER

Capabilities

Current Value

If configurable,

list methods

Maximum Application

Layer Retries for

Request Messages:

The number of times a

Master will retransmit an

application layer request

message if a response is

not received. This

parameter must never

cause a Master to

retransmit control or time

sync messages.

Outstations should never

transmit retries.

None (required)

Fixed at_


Configurable, selectable from , ,


describe

Variable, explain

None (required)

Fixed at_



, ,


describe

Variable, explain

Timeout waiting for

Complete Application

Layer Fragment:

Timeout if all frames of a

message fragment are not

received in the specified

time. Measured from time

first frame of a fragment is

received until the last

frame is received.

None

Fixed at_ ms


ms

Configurable, selectable from , , ms


describe

Variable, explain

Configurable, range 0 to

65535 seconds

LineMan

Maximum number of

objects allowed in a

single control request

for Analog Outputs

(group 41):

Fixed at (enter 0 if

controls are not supported)



, ,_


describe

Variable, explain


F4 Fill Out the Following Items for Outstations Only

FILL OUT THE

FOLLOWING ITEMS

FOR OUTSTATIONS

ONLY

Capabilities

Current Value

If configurable,

list methods

Timeout waiting for

Application Confirm of

solicited response

message:

None

Fixed at_ ms

Configurable, range to ms

Configurable, selectable from , , ms


describe

Variable, explain

Configurable,

range 0_ to

_65535_ s

LineMan

How often is time

synchronization

required from the

master?

Never needs time

Within seconds after IIN1.4 is set

Periodically every seconds

Periodically every

86400 seconds

Device Trouble Bit

IIN1.6:

If IIN1.6 device trouble bit

is set under certain

conditions, explain the

possible causes.

Never used

Reason for

setting

Reason for setting:

Device not configured

properly.

Event Buffer Overflow

Behaviour:

Discard the oldest event

Discard the newest event

Other, explain

Discard the oldest

event

Event Buffer

Organization:

Explain how event buffers

are arranged (per Object

Group, per Class, single

buffer, etc,) and provide

their sizes


Sends Multi-Fragment

Responses:

Indicates whether an

Outstation sends multi-

fragment responses

(Masters do not send

multi-fragment requests).

Ye

s

No

Yes

No

FILL OUT THE

FOLLOWING ITEMS

FOR OUTSTATIONS

Capabilities

Current Value

If configurable,

list methods

ONLY

DNP Command Settings Assign Class preserved through a

device reset: Analog Deadbands

If data associated with Data Set Prototypes

any of these requests are Data Set Descriptors

written through the DNP

protocol but not Function Code 31 Activate Configuration

preserved through a restart of the Outstation, the Master will have to write them again anytime the Restart IIN bit is set


F5 Outstation Unsolicited Response Support

OUTSTATION UNSOLICITED

RESPONSE SUPPORT

Capabilities

Current Value

If configurable, list

methods

Supports Unsolicited Reporting:

When the unsolicited response mode

is configured “off”, the device is to

behave exactly like an equivalent

device that has no support for

unsolicited responses. If set to On, the

Outstation will send a null Unsolicited

Response after it restarts, then wait

for an Enable Unsolicited Response

command from the master before

sending additional Unsolicited

Responses containing event data.

Not Supported


On and Off

Not Supported

Configurable, selectable

from On and Off

Configurable via

SCADA master

Master Data Link Address:

The destination address of the master

device where the unsolicited

responses will be sent.

Fixed at_



, ,_


describe

Configurable, range

0 to 65535_

LineMan

Unsolicited Response Confirmation

Timeout:

This is the amount of time that the

outstation will wait for an Application

Layer confirmation back from the

master indicating that the master

received the unsolicited response

message. As a minimum, the range of

configurable values must include

times from one second to one minute.

This parameter may be the same one

that is used for normal, solicited,

application confirmation timeouts, or it

may be a separate parameter.

Fixed at_ ms


ms


, , ms


describe

Variable, explain

Configurable, range

0 to 65535_s

LineMan

OUTSTATION UNSOLICITED

RESPONSE SUPPORT

Capabilities

Current Value

If configurable, list

methods

Number of Unsolicited Retries:

This is the number of retries that an

outstation transmits in each

unsolicited response series if it does

not receive confirmation back from the

master. The configured value includes

identical and regenerated retry

messages. One of the choices must

provide for an indefinite (and

potentially infinite) number of

transmissions.

None

Fixed at

Configurable, range

to


, ,_


describe

Always infinite, never gives up

Always infinite, never

gives up


F6 Outstation Unsolicited Response Trigger Conditions

OUTSTATION

UNSOLICITED RESPONSE

TRIGGER CONDITIONS

Capabilities

Current Value

If configurable,

list methods

Number of class 1 events: Class 1 not used to trigger Unsolicited

Responses

Fixed at



, ,_


describe

Fixed at 1

Number of class 2 events: Class 2 not used to trigger Unsolicited

Responses

Fixed at



, ,_


describe

Fixed at 1

Hold time after class 1

event:

A configured value of 0

indicates that responses are

not delayed due to this

parameter.

Class 1 not used to trigger Unsolicited

Responses

Fixed at ms


ms


, ,_ ms


describe

Fixed at 0

ms

Hold time after class 2

event:




parameter.

Class 2 not used to trigger Unsolicited

Responses

Fixed at ms


ms


, ,_ ms


describe

Fixed at 0

ms


OUTSTATION

UNSOLICITED RESPONSE

TRIGGER CONDITIONS

Capabilities

Current Value

If configurable,

list methods

Hold time after event

assigned to any class:




parameter.

Class events not used to trigger

Unsolicited Responses

Fixed at ms


ms


, ,_ ms


describe

Fixed at 0

ms

Retrigger Hold Timer:

The hold-time timer may be

retriggered for each new

event detected (increased

possibly of capturing all the

changes in a single response)

or not retriggered (giving the

master a guaranteed update

time).

Hold-time timer will be retriggered for

each new event detected (may get more

changes in next response)

Hold-time timer will not be retriggered

for each new event detected (guaranteed

update time)

Hold-time timer will be

retriggered for each new

event detected (may get

more changes in next

response)

Other Unsolicited Response

Trigger Conditions:

There are two conditions that will trigger

unsolicited response.

1. Periodic Load Log

measurement timer.

(configurable through vendor

software—LineMan.)

2. Events occurred on high

voltage power line. (such as

high current, power OFF, power

return etc.)


F7 Outstation Performance

OUTSTATION

PERFORMANCE

Capabilities

Current Value

If configurable,

list methods

When does outstation set

IIN1.4?

Never

Asserted at startup until first Time

Synchronization request received

Periodically, range to

seconds

Periodically, selectable from

, ,_ seconds

Range _to seconds after

last time sync

Selectable

from , _, seconds after last

time sync

When time error may have drifted

by range _to ms

When time error may have drifted

by selectable from , ,

Asserted at startup until

first Time Synchronization

request received

Range _0_ to__65535

minutes after last time sync

Maximum Response time

(ms):

The amount of time an

Outstation will take to respond

upon receipt of a valid

request. This does not include

the message transmission

time.

Maximum time from start-up

to IIN 1.4 assertion (ms):

F8 Individual Field Outstation Parameters

INDIVIDUAL FIELD OUTSTATION

PARAMETERS

Value of Current Setting

If configurable, list methods

User-assigned location name or code string

(same as g0v245):

Configurable Through CHK GSN

LineMan.

Device Serial Number string (same as

g0v248):

Configured At Manufacture

Device Firmware Version (same as g0v242): Configured At Manufacture

Device Hardware Version (same as g0v243): Configured At Manufacture


F9 Implementation Table

The following implementation table identifies which object groups and variations, function

codes and qualifiers the device supports in both requests and responses. The Request

columns identify all requests that may be sent by a Master, or all requests that must be

parsed by an Outstation. The Response columns identify all responses that must be parsed

by a Master, or all responses that may be sent by an Outstation.

DNP OBJECT GROUP & VARIATION REQUEST

outstation must parse

RESPONSE

Outstation may issue

Notes

Group

Num

Var

Num

Description

Function

Codes

(dec)

Qualifier

Codes

(hex)

Function

Codes

(dec)

Qualifier

Codes

(hex)

1 0 Binary Input – All Variations 1 (read) 06 (no range, or

all)

07,08 (limited qty)

1 2 Binary Input – with flags 1 (read) 06 (no range, or 129 (response) 00,17,28

(index)

all) 07,08 (limited qty)

2 0 Binary Input Event – With Absolute

Time

1 (read) 06 (no range, or

all)

07,08 (limited qty)

2 2 Binary Input Event – With Absolute

Time

1 (read) 06 (no range, or

all)

07,08 (limited qty)

129 (response)

130 (unsold.resp)

00,17,28

(index)

30 0 Analog Input – Any Variation 1 (read) 06 (no range, or

all)

07,08 (limited qty

30 2 Analog Input – 16-bit with flag 1 (read) 06 (no range, or 129 (response) 00,17,28(index

)

all) 07,08 (limited qty)

32 0 Analog Input Event – Any Variation 1 (read) 06 (no range, or

all)

07,08 (limited qty)

32 4 Analog Input Event—16-bit with time 1 (read) 06 (no range, or 129 (response) 00,17,28 all)

130 (unsold.resp) (index) 07,08 (limited qty)

50 1 Time and Date 2 (write) 07

=1)

(limited qty

The implementation table must list all functionality required by the device

whether Master or Outstation as defined within the DNP3 IED Conformance

Test Procedures. Any functionality beyond the subset level 1 supported is

indicated by highlighted rows. Text shaded as 07,08 (limited qty) indicates

subset level4 and above functionality. Any Object Groups not provided by an

outstation or not processed by a Master are indicated by strikethrough (note

these Object Groups will still be parsed).


1 (read) 07 (limited, 129 (response) 07 (limited

qty=1) qty) (qty = 1)

60 1 Class Objects – Class 0 data 1 (read) 06 (no range, or

all)

60 2 Class Objects – Class 1 data 1 (read)

20 (enbl.unsol.)

06 (no range, or

all)

21 (dab. Unsold.) 07,08 (limited qty) 60 3 Class Objects – Class 2 data 1 (read)

20 (enbl.unsol.)

06 (no range, or

all)

21 (dab. Unsold.) 07,08 (limited qty) 60 4 Class Objects – Class 3 data 1 (read)

20 (enbl.unsol.)

06 (no range, or

all)

21 (dab. Unsold.) 07,08 (limited qty) 80 1 Internal Indications – Packed format 2 (write) 00 (start-stop)

Index = 7

111 249 Octet String Event Object 1 (read) 06 (no range, or 129 (response) 00,17,28 all)

130 (unsold.resp) (index) 07,08 (limited qty)

No object 13 (cold restart)

No object 23 (delay meas.)

F10 Capabilities and Current Settings for Device Database (Outstation Only) –

Point List

F10.1 Single-Bit Binary Inputs

SINGLE-BIT BINARY INPUTS

Static (Steady-State) Group

Number: 1

Event Group Number: 2

Capabilities

Current Value

If configurable,

list methods

Static Variation reported when

variation 0 requested:

Variation 1 – Single-bit Packed

format

Variation 2 – Single-bit with flag

Based on point Index (add

column to table below)

Variation 2 – Single-bit

with flag

Event Variation reported when


Variation 1 – without time

Variation 2 – with absolute time

Variation 3 – with relative time

Based on point Index (add

column to table below)

Variation 2 – with

absolute time


Point List of Single-Bit Binary Input is in APPENDIX G – Detailed DNP3 Point List

Binary input is used to report Event Type and Power ON status before and after event

triggered. The static value of Binary Input Point is the most recent recorded value. (i.e.,

most recent event type.)

F10.2 Analog Input Points

ANALOG INPUT POINTS

Static (Steady-State) Group

Number: 30


Capabilities

Current Value

If configurable

list methods

Static Variation reported when


Variation 1 – 32-bit with flag

Variation 2 – 16-bit with flag

Variation 3 – 32-bit without flag

Variation 4 – 16-bit without flag

Variation 5 – single-precision floating point

with flag

Variation 6 – double-precision floating point

with flag

Based on point Index (add column to table

below)

Variation 2 –

16-bit with flag

Event variation reported when


Variation 1 – 32-bit without time

Variation 2 – 16-bit without time

Variation 3 – 32-bit with time

Variation 4 – 16-bit with time


w/o time


w/o time


with time


with time


below)

Variation 4 –

16-bit with time

Event reporting mode:

When responding with event data

and more than one event has

occurred for a data point, an

Outstation may include all events or

only the most recent event. Only the

most recent event is typically

reported for Analog Inputs.

Only most recent

All events

All events


Analog Inputs Included in Class 0

response:

If Analog Inputs are not included in

the Class 0 response, Analog Input

Events (group 32) may not be

reported.

Alway

s

Never

Only if point is assigned to Class 1, 2, or 3


below)

Always

ANALOG INPUT POINTS Static (Steady-State) Group

Number: 30 Capabilities Current Value

If configurable

list methods


Definition of Analog Input Point

List:

List all addressable points. Points

that do not exist (for example,

because an option is not installed)

shall be omitted from the table.

Fixed, list shown in table below

Configurable(current list may be shown in

table below)

Other, explain

Fixed, list

shown in table

below

Point List of Analog Input is in APPENDIX G – Detailed DNP3 Point List.

Static Analog Input Points are mainly used to read instantaneous (or most recent

measured) status of Data-PAC and CMS installed, e.g., Static analog input on points 3, 4, 5

represent most recent recorded event trigger current.

Event Analog Input Points are mainly used to record all events data recorded since last

Event Analog Input reading, in which each point could have more than one event values

with different time stamp. (e.g., Event Analog Input on points 3, 4, 5, 6)

Gateway Manual July 2012 page 100 of 109

APPENDIX G – Detailed DNP3 Point List

G1 Octet String Events

Point Index

(Dec)

Point Index

(Hex)

Event Variation Point Name Scaling

Obj Var Class Description

0 000 111 249 1 Octet String Input -- 247 Bytes Waveform Data - Current -- CMS G1P1

(120x16bitsSamples+48bitsTimeStamp+16bits(Counter of micro seconds)+8bitsCheckSum) No Scaling

1 001 111 249 1 Octet String Input -- 247 Bytes Waveform Data - Voltage -- CMS G1P1

(120x16bitsSamples+48bitsTimeStamp+16bits(Counter of micro seconds)+8bitsCheckSum) divided by 10

2 002 111 x 1 Octet String Input -- x Bytes Reserved -- CMS G1P1

3 003 111 249 1 Octet String Input -- 247 Bytes

Waveform Data - Current -- CMS G1P2









(120x16bitsSamples+48bitsTimeStamp+8bitCheckSum) divided by 10





10 00A 111 249 1 Octet String Input -- 247 Bytes Waveform Data - Voltage -- CMS G2P1


11 00B 111 x 1 Octet String Input -- x Bytes Reserved -- CMS G2P1

12 00C 111 249 1 Octet String Input -- 247 Bytes



13 00D 111 249 1 Octet String Input -- 247 Bytes Waveform Data - Voltage -- CMS G2P2


14 00E 111 x 1 Octet String Input -- x Bytes Reserved -- CMS G2P2

15 00F 111 249 1 Octet String Input -- 247 Bytes























26 01A 111 x 1 Octet String Input -- x Bytes Reserved -- CMS G3P3

Note: Current waveform has 120 sample points, and every sample point is 16 bit signed integer value. No scaling needed. (Unit: Ampere)

Voltage waveform has 120 sample points, and every sample point is 16 bit signed integer value. To be divided by 10 to get real value. (Unit: Percentage.)

Range of real value.(-100.0%~+100.0%)

Timestamp is 48bit DNP3 time stamp which represents the time stamp of the first sample point.

249Bytes=Waveform(240Bytes)+TimeStamp(6Bytes)+Reserved(2Bytes)+CheckSum(1Byte)

(Waveform is sampled at 600HZ. 120samples will cover 200ms time duration, which corresponds to 10 cycles for 50Hz Line, and 12 cycles for 60Hz Line.)

G1 Octet Troubleshooting Points

Point Index

(Dec)

Point Index

(Hex)

Event Variation Point Name Scaling

Obj Var Class Description

166 0A6 111 4 3 Octet String Input -- 2 Bytes RF Health Check Error

16bits(lowest bit is G1P1) No Scaling

167 0A7 111 4 3 Octet String Input -- 2 Bytes Commission Error

16bits(lowest bit is G1P1) No Scaling


G2 Single Binary Inputs

Point Index

(Dec)

Point Index

(Hex) Obj Var Description Obj Var Class Description Point Name

0 000 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - Gateway Battery Alarm

1 001 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LineIQ Battery Alarm -G1P1 2 002 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - SI (short interruption) - G1P1

3 003 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LI (long interruption) - G1P1

4 004 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - FP (on the fault path) - G1P1

5 005 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - PR (power return) - G1P1

6 006 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PreTrigger Power Status -- CMS - G1P1

7 007 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PostTrigger Power Status -- CMS - G1P1

8 008 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LineIQ Battery Alarm -G1P2

9 009 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - SI (short interruption) - G1P2

10 00A 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LI (long interruption) - G1P2

11 00B 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - FP (on the fault path) - G1P2

12 00C 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - PR (power return) - G1P2

13 00D 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PreTrigger Power Status -- CMS - G1P2

14 00E 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PostTrigger Power Status -- CMS - G1P2

15 00F 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LineIQ Battery Alarm -G1P3











26 01A 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - PR (power return) - G2P1

27 01B 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PreTrigger Power Status -- CMS - G2P1

28 01C 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PostTrigger Power Status -- CMS - G2P1

29 01D 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LineIQ Battery Alarm -G2P2

30 01E 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - SI (short interruption) - G2P2

31 01F 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LI (long interruption) - G2P2











42 02A 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time PostTrigger Power Status -- CMS - G2P3

43 02B 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LineIQ Battery Alarm -G3P1

44 02C 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - SI (short interruption) - G3P1

45 02D 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - LI (long interruption) - G3P1

46 02E 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - FP (on the fault path) - G3P1

47 02F 1 2 Binary Input -- With Flags 2 2 1 Binary Input Event -- With absolute time Event Type - PR (power return) - G3P1


















G3 16 Bit Analog Inputs

Point Index

(Dec)

Point Index

(Hex)

Static Variation Event Variation Point Name

Static Variation / Event Variation SCALING


0 000 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Battery Voltage Raw value -- PAC divided by 100

1 001 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Battery Voltage Raw value -- CMS G1P1 divided by 100

2 002 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time VSensor Static / VSensor Event Profile --CMS G1P1 times 100

3 003 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / Event Trigger Current --CMS G1P1 divided by 10

4 004 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / PreTrigger Current --CMS G1P1 divided by 10

5 005 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / PostTrigger Current --CMS G1P1 divided by 10

6 006 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Load Log Current -- CMS G1P1 divided by 10

7 007 30 2 Analog Input -- 16-bit with flag

LineFrequency -- CMS G1P1 divided by 10

8 008 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Power Factor (Instantaneous / Historical) -- CMS G1P1 divided by 1000

9 009 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Phase Angle (Instantaneous / Historical) -- CMS G1P1 divided by 10

10 00A 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Ambient Temperature (Instantaneous / Historical ) -- CMS G1P1 divided by 100

11 00B 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Conductor Temperature (Instantaneous / Historical ) -- CMS G1P1 divided by 100

12 00C 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Battery Voltage Raw value -- CMS G1P2 divided by 100

13 00D 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time VSensor Static / VSensor Event Profile --CMS G1P2 times 100

14 00E 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / Event Trigger Current --CMS G1P2 divided by 10

15 00F 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PreTrigger Current --CMS G1P2 divided by 10

16 010 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PostTrigger Current --CMS G1P2 divided by 10






21 015 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Ambient Temperature (Instantaneous / Historical ) -- CMS G1P2 divided by 100

22 016 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Conductor Temperature (Instantaneous / Historical ) -- CMS G1P2 divided by 100




26 01A 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PreTrigger Current --CMS G1P3 divided by 10

27 01B 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PostTrigger Current --CMS G1P3 divided by 10

28 01C 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Load Log Current -- CMS G1P3 divided by 10

29 01D 30 2 Analog Input -- 16-bit with flag


30 01E 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Power Factor (Instantaneous / Historical) -- CMS G1P3 divided by 1000

31 01F 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Phase Angle (Instantaneous / Historical) -- CMS G1P3 divided by 10






37 025 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PreTrigger Current --CMS G2P1 divided by 10






42 02A 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Phase Angle (Instantaneous / Historical) -- CMS G2P1 divided by 10

43 02B 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Ambient Temperature (Instantaneous / Historical ) -- CMS G2P1 divided by 100

44 02C 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Conductor Temperature (Instantaneous / Historical ) -- CMS G2P1 divided by 100

45 02D 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Battery Voltage Raw value -- CMS G2P2 divided by 100

46 02E 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time VSensor Static / VSensor Event Profile --CMS G2P2 times 100

47 02F 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / Event Trigger Current --CMS G2P2 divided by 10












58 03A 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / Event Trigger Current --CMS G2P3 divided by 10

59 03B 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PreTrigger Current --CMS G2P3 divided by 10

60 03C 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PostTrigger Current --CMS G2P3 divided by 10

61 03D 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Load Log Current -- CMS G2P3 divided by 10

62 03E 30 2 Analog Input -- 16-bit with flag


63 03F 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Power Factor (Instantaneous / Historical) -- CMS G2P3 divided by 1000












74 04A 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Power Factor (Instantaneous / Historical) -- CMS G3P1 divided by 1000

75 04B 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Phase Angle (Instantaneous / Historical) -- CMS G3P1 divided by 10

76 04C 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Ambient Temperature (Instantaneous / Historical ) -- CMS G3P1 divided by 100

77 04D 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Conductor Temperature (Instantaneous / Historical ) -- CMS G3P1 divided by 100

78 04E 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Battery Voltage Raw value -- CMS G3P2 divided by 100

79 04F 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time VSensor Static / VSensor Event Profile --CMS G3P2 times 100












90 05A 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time VSensor Static / VSensor Event Profile --CMS G3P3 times 100

91 05B 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current / Event Trigger Current --CMS G3P3 divided by 10

92 05C 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PreTrigger Current --CMS G3P3 divided by 10

93 05D 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Instantaneous Current /PostTrigger Current --CMS G3P3 divided by 10

94 05E 30 2 Analog Input -- 16-bit with flag 32 4 2 Analog Input Event -- 16-bit with time Load Log Current -- CMS G3P3 divided by 10

95 05F 30 2 Analog Input -- 16-bit with flag






100 064 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved, diagnosis only. (RF health check Error)

101 065 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved, diagnosis only. (Communication Error)

102 066 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved, diagnosis only. (Modem Script Error.) Lower Word of 32bits

103 067 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved, diagnosis only. (Modem Script Error.) Higher Word of 32bits

104 068 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved (Debug One) Lower Word of 32bits

105 069 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved (Debug One) Higher Word of 32bits

106 06A 30 2 Analog Input -- 16-bit with flag 32 4 3 Analog Input Event -- 16-bit with time Reserved (Debug Two)


Point Index

(Dec)

Point Index

(Hex)

Static Variation Event Variation Point Name

Static Variation / Event Variation SCALING


172

AC 30

2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Load Direction – CMS G1P1

173 AD 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G1P1

174 AE 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G1P1

182 B6 30


183 B7 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G1P2

184 B8 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G1P2

192 C0 30


193 C1 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G1P3

194 C2 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G1P3

202 CA 30


203 CB 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G2P1

204 CC 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G2P1

212 D4 30


213 D5 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G2P2

214 D6 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G2P2

222 DE 30


223 DF 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G2P3

224 E0 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G2P3

232 E8 30


233 E9

30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G3P1

234 EA 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G3P1

242 F2 30


243 F3 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G3P2

244 F4 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G3P2

252 FC 30


253 FD 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G3P3

254 FE 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G3P3

262 106 30


263 107 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G4P1

264 108 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G4P1

272 110 30


273 111

11

30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G4P2


282 11A 30


283 11B 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G4P3

284 11C

30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G4P3

292 124 30




302

12E 30


303 12F 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Direction – CMS G5P2


312 138 30



314 13A 30 2 Analog Input -- 16-bit with flag 32 4 1 Analog Input Event -- 16-bit with time Fault Boolean – CMS G5P3

Fault Direction Returned Values (0=n/a, 1=N, 2=NE, 3=E, 4=SE, 5=S, 6=SW, 7=W, 8=NW)

Appendix H – Gateway Firmware Upgrades The Gateway Firmware Upgrade tool (Gateway _FW_Upgrade.exe) is distributed as a zip

file along with the .LHX file which contains the actual firmware upgrade.

To upgrade the Gateway firmware, you must be able to make a direct serial port

connection, or a direct Ethernet connection to the Gateway

Follow the steps below to perform the upgrade.

1. Unzip the Firmware Upgrade file and copy the Gateway _FW_Upgrade.exe

executable and the .LHX file (e.g. V043-Gateway C30TcpIpDnp3-O1.lhx ) to your

desktop.

2. Turn on the Gateway and wait for the initialization process to complete.

3. Make a direct connection to the Gateway.

If using a serial (COM) port, you will need to know the COM port number of the serial port

you are using.

If you are unsure of the COM port number, right click on the My Computer icon, and select

Manage. Then select “Device Manager” and scroll to the “Ports (COM & LPT)” entry, and

expand it.


Figure 40: Verifying the COM port number


The available COM ports and their numbers (e.g. COM5) will be shown.

If you are using an Internet connection you will need to know the IP address of the

Gateway.

4. Start the Gateway Firmware Upgrade Program by clicking on the desktop icon.

Figure 41: Gateway Firmware Upgrader opening screen

5. Using the Browse button, select and open the .LHX file.

Figure 42: Selecting the .LHX file


Figure 43: Gateway firmware upgrader with .LHX file selected

6. Enter the COM port (e.g. COM5) or the IP address, using the style shown below the

Comms input box.

Figure 44: Figure 44: Gateway Firmware Upgrader with COM port selected


7. Verify that the entries you have made are correct, and then click on Upgrade.

8. The information box will now show you the status of the upgrade. The initial screen

will say that communications have been established with the Gateway, and that the

upgrade process has commenced.

Figure 45: Gateway Firmware Upgrade commencing

9. As the upgrade proceeds, the Percentage Complete number will be updated at

10% intervals.


Figure 46: Gateway Firmware Upgrade in progress

10. When the upgrade is complete, the following screen will be displayed.

Figure 47: Gateway Firmware Upgrade completed


11. To check the Gateway status, use LineMan to connect to the Gateway via a

LocalLink, and check the Gateway summary. You will need to wait for the firmware

upgrade process to complete and for the Gateway to reboot and the Gateway

initialization process to complete before you can check the status.

Figure 48: Using LineMan to verify the firmware version number

12. Confirm that the COM Firmware Version is correct.


Appendix I – Remote Access via TCP/IP The Gateway remote access tool (RF-DataLink-Emulator.exe) is distributed as a zip file,

which contains the command line utility as well as a GUI interface.

*A null modem cable or virtual null program is need for both GridInSite as well as

DNP3/LineMan Remote applications.

**Gateway firmware version 2.15 and LineMan version 1.9.8.6 or higher is required to

connect for customers using GridInsite.

***Connecting to units setup to call into GridInSite/GServer will only be allowed to connect

within 5 minutes of the last Health Check. If the windows is missed you will have to wait till

the next health check

To access the Gateway, you must use either a virtual or hardware based null modem serial

port, and a direct TCP/IP connection to the Gateway.

Follow the steps below to perform the connection

1. Open the program by clicking on the “RF-DataLink-Emulator-UI.exe” f ilename as shown below.

Figure 49.

2. The following window will open up.


Figure 50.

3. Enter one of the null serial port addresses in to the LineMan COM Port text box.

Figure 51.

4. Next, Select LineMan LIQ60 for LineIQ products.


Figure 52.

5. In the PAC Comms textbox, enter the IP Address of the unit you wish to talk to, with the port equal to

9000

Figure 53.


6. Click Start to Begin the session.

Figure 54.

7. Open LineMan and select the other serial port that is connected to your null connection.

Figure 55.

8. If successful, the program will behave as normal.

Communications Gateway - Home | Franklin Electric | Grid...

Documents

Transcript of Communications Gateway - Home | Franklin Electric | Grid...