Quantum IEC61850 NHA31369 07/2015 Quantum … Quantum IEC61850 NHA31369 07/2015 Quantum IEC61850 140 NOP 850 00 Installation and Configuration Guide 07/2015 2 NHA31369 07/2015 The

NH

A31

369.

00

www.schneider-electric.com

Quantum IEC61850

NHA31369 07/2015

Quantum IEC61850140 NOP 850 00Installation and Configuration Guide

07/2015

2 NHA31369 07/2015

The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.

No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric.

All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.

When devices are used for applications with technical safety requirements, the relevant instructions must be followed.

Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results.

Failure to observe this information can result in injury or equipment damage.

© 2015 Schneider Electric. All rights reserved.

NHA31369 07/2015 3

Table of Contents

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7About the Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1 Characteristics of the 140 NOP 850 00 Module . . . . . . 15140 NOP 850 00 Module Description . . . . . . . . . . . . . . . . . . . . . . . . . 16Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Communication Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 2 Installing the 140 NOP 850 00 Module . . . . . . . . . . . . . 27Mounting a 140 NOP 850 00 Module on the Backplane . . . . . . . . . . . 27

Chapter 3 Configuring the 140 NOP 850 00 Module . . . . . . . . . . . 293.1 Creating a Project in Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Creating a Project in Unity Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Configuring the Module Name and Starting Memory Location . . . . . . 35

3.2 Introducing the IEC61850 Configuration Settings . . . . . . . . . . . . . . . . 37Selecting the IEC61850 Edition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Using the Modicon IEC61850 Configuration Tool . . . . . . . . . . . . . . . . 39General Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.3 Configuring IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Assigning Roles and IP Addresses to Ethernet Ports . . . . . . . . . . . . . 47

3.4 Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Configuring the Rapid Spanning Tree Protocol . . . . . . . . . . . . . . . . . . 52Configuring Time Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Configuring the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Configuring QoS Ethernet Packet Tagging . . . . . . . . . . . . . . . . . . . . . 58Configuring Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.5 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.6 Uploading and Downloading Configuration Settings . . . . . . . . . . . . . . 62Uploading and Downloading Configuration Settings . . . . . . . . . . . . . . 62

Chapter 4 Configuring the IEC61850 Server . . . . . . . . . . . . . . . . . 65Working with Server Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 66Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Instantiating Data Objects and Data Attributes . . . . . . . . . . . . . . . . . . 81Working with Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4 NHA31369 07/2015

Configuring Report Control Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Publishing GOOSE Control Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Working with ERT Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Subscribing to GOOSE Control Blocks from External References . . . 99

Chapter 5 Configuring the IEC61850 Client . . . . . . . . . . . . . . . . . 103Client Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Chapter 6 Working with IEC61850 Data Objects. . . . . . . . . . . . . . 107Mapping Data Attributes to PLC Memory. . . . . . . . . . . . . . . . . . . . . . . 108Working with IEC61850 Data Objects . . . . . . . . . . . . . . . . . . . . . . . . . 115PLC State Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118IEC61850 Memory Arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119DDT Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Chapter 7 Elementary Function and Elementary Functio n Block for the 140 NOP 850 00 . . . . . . . . . . . . . . . . . . . . . . . . . 133NOP850_EVTS Elementary Function Block for the 140 NOP 850 00 . 134T850_TO_T870 and T870_TO_T850 Elementary Functions for the 140 NOP 850 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Chapter 8 Explicit Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Configuring Explicit Messaging Using MBP_MSTR. . . . . . . . . . . . . . . 142Modbus TCP Explicit Messaging Function Codes . . . . . . . . . . . . . . . . 144Configuring the Control Parameter for Modbus TCP Explicit Messaging 145

Chapter 9 Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153LED Indicators on the 140 NOP 850 00 Module . . . . . . . . . . . . . . . . . 154Modbus Diagnostic Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Modbus Diagnostic Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167IEC61850 Diagnostic Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Hot Standby Switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 10 Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173140 NOP 850 00 Firmware Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 11 Protocol Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 177Statement of Protocol Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Appendix A Detected Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 181

TCP/IP Ethernet Detected Error Codes . . . . . . . . . . . . . . . . . . . . . . . . 182Modbus TCP Explicit Messaging Detected Error Codes . . . . . . . . . . . 183IEC61850 Explicit Messaging Detected Error Codes. . . . . . . . . . . . . . 184

NHA31369 07/2015 5

Appendix B Supported Data Model Items . . . . . . . . . . . . . . . . . . . . . 187Logical Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Common Data Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

6 NHA31369 07/2015

NHA31369 07/2015 7

Safety Information

Important Information

NOTICE

Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install, operate, or maintain it. The following special messages may appear throughout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.

8 NHA31369 07/2015

PLEASE NOTE

Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.

A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and its installation, and has received safety training to recognize and avoid the hazards involved.

BEFORE YOU BEGIN

Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective point-of-operation guarding on a machine can result in serious injury to the operator of that machine.

This automation equipment and related software is used to control a variety of industrial processes. The type or model of automation equipment suitable for each application will vary depending on factors such as the control function required, degree of protection required, production methods, unusual conditions, government regulations, etc. In some applications, more than one processor may be required, as when backup redundancy is needed.

Only you, the user, machine builder or system integrator can be aware of all the conditions and factors present during setup, operation, and maintenance of the machine and, therefore, can determine the automation equipment and the related safeties and interlocks which can be properly used. When selecting automation and control equipment and related software for a particular application, you should refer to the applicable local and national standards and regulations. The National Safety Council’s Accident Prevention Manual (nationally recognized in the United States of America) also provides much useful information.

In some applications, such as packaging machinery, additional operator protection such as point-of-operation guarding must be provided. This is necessary if the operator’s hands and other parts of the body are free to enter the pinch points or other hazardous areas and serious injury can occur. Software products alone cannot protect an operator from injury. For this reason the software cannot be substituted for or take the place of point-of-operation protection.

WARNINGUNGUARDED EQUIPMENT

� Do not use this software and related automation equipment on equipment which does not have point-of-operation protection.

� Do not reach into machinery during operation.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

NHA31369 07/2015 9

Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation protection have been installed and are operational before placing the equipment into service. All interlocks and safeties related to point-of-operation protection must be coordinated with the related automation equipment and software programming.

NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation protection is outside the scope of the Function Block Library, System User Guide, or other implementation referenced in this documentation.

START-UP AND TEST

Before using electrical control and automation equipment for regular operation after installation, the system should be given a start-up test by qualified personnel to verify correct operation of the equipment. It is important that arrangements for such a check be made and that enough time is allowed to perform complete and satisfactory testing.

Follow all start-up tests recommended in the equipment documentation. Store all equipment documentation for future references.

Software testing must be done in both simulated and real environments.

Verify that the completed system is free from all short circuits and temporary grounds that are not installed according to local regulations (according to the National Electrical Code in the U.S.A, for instance). If high-potential voltage testing is necessary, follow recommendations in equipment documentation to prevent accidental equipment damage.

Before energizing equipment:� Remove tools, meters, and debris from equipment.� Close the equipment enclosure door.� Remove all temporary grounds from incoming power lines.� Perform all start-up tests recommended by the manufacturer.

CAUTIONEQUIPMENT OPERATION HAZARD

� Verify that all installation and set up procedures have been completed.� Before operational tests are performed, remove all blocks or other temporary holding means

used for shipment from all component devices.� Remove tools, meters, and debris from equipment.

Failure to follow these instructions can result in injury or equipment damage.

10 NHA31369 07/2015

OPERATION AND ADJUSTMENTS

The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English version prevails):� Regardless of the care exercised in the design and manufacture of equipment or in the selection

and ratings of components, there are hazards that can be encountered if such equipment is improperly operated.

� It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe operation. Always use the manufacturer’s instructions as a guide for functional adjustments. Personnel who have access to these adjustments should be familiar with the equipment manufacturer’s instructions and the machinery used with the electrical equipment.

� Only those operational adjustments actually required by the operator should be accessible to the operator. Access to other controls should be restricted to prevent unauthorized changes in operating characteristics.

NHA31369 07/2015 11

About the Book

At a Glance

Document Scope

This guide describes the Quantum 140 NOP 850 00 module. The main purpose of this module is to connect to intelligent electronic devices (IEDs) and supervision control software that utilize the IEC61850 standard. The module enables PlantStruxure controllers to be easily integrated into IEC61850 environment.

NOTE: Any specific configuration settings contained in this guide are for instructional purposes only. The settings required for your specific application will differ from any examples presented in this guide.

This document is intended for users with knowledge of both:� The IEC61850 protocol, parts 6, 7-2, 7-3, 7-4, and 7-410.� Unity Pro configuration software, which is the engineering tool for the Quantum platform and the

140 NOP 850 00 module.

Validity Note

This document is valid for the Quantum 140 NOP 850 00 module when used with Unity Pro 10.0 or later.

The technical characteristics for devices described in this document also appear online. To access this information online:

The characteristics that are presented in this manual should be the same as those characteristics that appear online. In line with our policy of constant improvement, we may revise content over time to improve clarity and accuracy. If you see a difference between the manual and online information, use the online information as your reference.

Step Action

1 Contact your local Schneider Electric sales representative to obtain the website URL.

2 If more than one reference appears on the website, click on the reference that interests you.

3 Depending on the size of your screen, you may need to scroll down to locate the data sheet.

4 To save or print a data sheet as a .PDF file, click Download Product data sheet .

12 NHA31369 07/2015

Related Documents

Title of Documentation Reference Number

Quantum EIO Control Network Installation and Configuration Guide S1A48993 (English), S1A48994 (French), S1A48995 (German), S1A48997 (Italian), S1A48998 (Spanish), S1A48999 (Chinese)

Quantum EIO System Planning Guide S1A48959 (English), S1A48961 (French), S1A48962 (German), S1A48964 (Italian), S1A48965 (Spanish), S1A48966 (Chinese)

Quantum EIO Remote I/O Modules Installation and Configuration Guide

S1A48978 (English), S1A48981 (French), S1A48982 (German), S1A48983 (Italian), S1A48984 (Spanish), S1A48985 (Chinese)

Quantum EIO Distributed I/O Network Installation and Configuration Guide

S1A48986 (English), S1A48987 (French), S1A48988 (German), S1A48990 (Italian), S1A48991 (Spanish), S1A48992 (Chinese)

Modicon Quantum Change Configuration on the Fly User Guide S1A48967 (English), S1A48968 (French), S1A48969 (German), S1A48970 (Italian), S1A48972 (Spanish), S1A48976 (Chinese)

Modicon Quantum Hot Standby System User Manual 35010533 (English), 35010534 (French), 35010535 (German), 35010536 (Spanish), 35013993 (Italian), 35012188 (Chinese)

NHA31369 07/2015 13

Modicon M340/X80 BMX NRP 020• Fiber Optic Repeater Module User Guide

EIO0000001108 (English), EIO0000001109 (French), EIO0000001110 (German), EIO0000001111 (Spanish), EIO0000001112 (Italian), EIO0000001113 (Chinese)

Modicon M340/X80 with Unity Pro Analog Input/Output Modules User Manual

35011978 (English), 35011979 (German), 35011980 (French), 35011981 (Spanish), 35011982 (Italian), 35011983 (Chinese)

Modicon M340/X80 with Unity Pro Discrete Input/Output Modules User Manual


Modicon M340/X80 with Unity Pro BMX EHC 0200 Counting Module User Manual


Unity Pro Program Languages and Structure Reference Manual 35006144 (English), 35006145 (French), 35006146 (German), 35006147 (Spanish), 35013361 (Italian), 35013362 (Chinese)

Unity Pro Operating Modes 33003101 (English), 33003102 (French), 33003103 (German), 33003104 (Spanish), 33003696 (Italian), 33003697 (Chinese)

Quantum with Unity Pro Hardware Reference Manual 35010529 (English), 35010530 (French), 35010531 (German), 35010532 (Spanish), 35013975 (Italian), 35012184 (Chinese)


14 NHA31369 07/2015

You can download these technical publications and other technical information from our website at http://www.schneider-electric.com/ww/en/download/

Unity Pro Installation Manual 35014792 (English), 35014793 (French), 35014794 (German), 35014795 (Spanish), 35014796 (Italian), 35012191 (Chinese)


NHA31369 07/2015 15

Quantum IEC61850

140 NOP 850 00 Module Characteristics

NHA31369 07/2015

Characteristics of the 140 NOP 850 00 Module

Chapter 1Characteristics of the 140 NOP 850 00 Module

Introduction

This chapter describes the 140 NOP 850 00 module linking IEC61850 and Ethernet networks in a Quantum system.

This chapter includes physical characteristics, port descriptions, and agency specifications for the 140 NOP 850 00 module.

What Is in This Chapter?

This chapter contains the following topics:

Topic Page

140 NOP 850 00 Module Description 16

Module Specifications 19

Communication Specifications 21


16 NHA31369 07/2015

140 NOP 850 00 Module Description

Introduction

The 140 NOP 850 00 module is installed on the local rack of a Quantum system. The module provides interfaces for IEC61850 communication.

Functionality

The main purpose of the 140 NOP 850 00 module is to provide connection with IEC61850 IED devices as well as device management software that utilizes the IEC61850 standard.

The 140 NOP 850 00 module is mounted on the local rack and supports communication as:� IEC61850 server� IEC61850 client� Modbus TCP server� Modbus TCP client� GOOSE publisher� GOOSE subscriber

The 140 NOP 850 00 module also provides high network availability by supporting the RSTP protocol, router, and the Quantum Hot Standby functionality.

The maximum number of 140 NOP 850 00 modules that can be mounted on a local rack is determined by your choice of CPU. The maximum numbers of communication modules – including 140 NOP 850 00 modules – supported by Quantum CPUs are as follows:

NOTE: � The 140 NOP 850 00 transmits explicit messages over the backplane. To enhance

communication performance, set the Maximum Unity data exchanged by PLC Scan setting to its highest value.

CPU Maximum Number of Communication Modules

CPU Maximum Number of Communication Modules

140 CPU 651 50 6 140 CPU 671 60 6

140 CPU 651 60 6 140 CPU 672 60 6

140 CPU 652 60 6 140 CPU 672 61 6

140 CPU 658 60 6 140 CPU 678 61 6

140 CPU 670 60 6 – –

NOTE: All CPUs require the use of firmware version 3.30, or higher.


NHA31369 07/2015 17

External Features

140 NOP 850 00:

1 LED display2 Service port (ETH 1)3 Ethernet port (ETH 2)4 Ethernet port (ETH 3)5 Ethernet port (ETH 4)

NOTE: To help prevent dust from entering the unused Ethernet ports on this module, cover the port with the stopper:


18 NHA31369 07/2015

External Ports

The 140 NOP 850 00 module has 4 external Ethernet ports, which support up to three IP addresses that can be configured in the Communication Settings → IP Setting tab.

Port Description

ETH 1 (Service port)

The ETH 1 service port allows the diagnosis of Ethernet ports and provides access to external tools and devices (Unity Pro, ConneXium Network Manager, HMI, etc.). The port supports these modes:� port mirroring: In this mode, data traffic from one or more of the 3 external ports – plus

the internal port – is copied to this port. This allows a connected tool to monitor and analyze the port traffic.

� access port (default): In this mode, diagnostic information is provided via Modbus explicit messages (see page 141) or via SNMP (see page 56).

� extended network: This mode supports a dedicated network for the 140 NOP 850 00 module.

NOTE: � If the device, which is connected to the ETH 1 service port, is configured for a speed

that exceeds 100 Mbps, the Ethernet link may not be established between the device and the module through the ETH 1 service port.

� In port mirroring mode, the ETH 1 service port acts like a read-only port. That is, you cannot access devices (ping, connect to Unity Pro, etc.) through the ETH_1 service port.

To configure this port, refer to the Configuring the Service/Extend Port topic (see page 47).

ETH 2 The ETH 2 port provides supports the following modes:� access port (default): In this mode, diagnostic information is provided via Modbus

explicit messages (see page 141) or via SNMP (see page 56).� extended network: This mode supports a dedicated network for the 140 NOP 850 00

module.

ETH 3 and ETH 4

These 2 copper ports provide:� connections for IEC61850 communications and other Ethernet services� star, loop, or mesh topology� support for RSTP


NHA31369 07/2015 19

Module Specifications

Product Certification

The 140 NOP 850 00 module meets these standards:

140 NOP 850 00 module conforms to these product certification and marine classification authorities:

The electrical isolation within a 140 NOP 850 00 system modules complies with the 1500 Vac/2250 Vdc 60s from IEEE 802.3 2008.

UL (UL61010)

CSA (CSA22.2 no. 142)

RCM

Hazardous locations (Cl1 div 2)

IEC61000-4-16

EMI EN 55011

CE

EN 61131-1

IEC 61131-2 (zone B and zone C, except surges on AC: zone B only)

Key Certification Body Country

ABS American Bureau of Shipping United States

BV Bureau Veritas France

DNV Det Norske Veritas Norway

GL Germanischer Lloyd Germany

LR Lloyd’s Register United Kingdom

RINA Registro Italiano Navale Italy


20 NHA31369 07/2015

Environmental Requirements

NOTE: The 140 NOP 850 00 is also available in a coated version.

Parameter Reference Specification

protection EN 61131-2 IP20

IEC 60527

protection class EN 61131-2 protection class 1

over voltage class EN 61131-2 category II

operating temperature IEC 60068-2-1 0 ... 60° C

Ab&Ad (cold)

IEC 60068-2-2

Bb&Bd (cold)

storage temperature IEC 60068-2-1 -40 ... 85° C

Ab&Ad (cold)

IEC 60068-2-2

Bb&Bd (cold)

sinusoidal vibration IEC 60068-2-6fC � .5 ... 8.4 Hz at 3.5 mm constant amplitude� 8.4 ... 150 Hz at 1g constant acceleration� 10 cycles at sweep rate of 1 oct/min

EN 61131-2

operating shock IEC 60068-2-27Ea 15 g peak, 11 ms, half-sine wave, 3 shocks in each direction (+ and -) for each of the 3 principle axes

altitude – 0 ... 5000 m maximum during operation. For altitudes > 2000 m, reduce the operating temperature by 6° C for each additional 1000 m.

free fall, random (packaged)

EN 61131-2 5 random drops from 1 m onto flat surfaces

IEC 60068-2-32

test ed., method 1

free fall, flat drop (unpackaged)

EN 61131-2 � 2 random drops from 1 m onto flat surfaces� 5 drops from 0.1 m onto flat surfacesIEC 60068-2-32

test ed., method 1

free fall, angled (unpackaged)

EN 61131-2 5 drops from 0.1 m onto each corner

IEC 60068-2-31

relative humidity (operating)

IEC 60068-2-78Ca 93% (+/- 2%, noncondensing) at 60° C

relative humidity (nonoperating)

IEC 60068 93% (+/- 2%, noncondensing) at 60° C


NHA31369 07/2015 21

Communication Specifications

Introduction

The following specifications describe both the IEC61850 communication and the explicit messaging capacities of the 140 NOP 850 00 module.

Data In versus Data Out

The terms data in and data out, as used in this topic, refer to the flow of data from the point of view 140 NOP 850 00 IED, and vary depending on the role of the device as client or server.� Data In: the 140 NOP 850 00 receives a data update from its connected devices, then

synchronizes data with the CPU:� As server: the 140 NOP 850 00 receives a command from a control object, or from a buffered

report, unbuffered report, or GOOSE.� As client: the 140 NOP 850 00 receives a report/GOOSE response to a previous read

request.

� Data Out: the 140 NOP 850 00 receives a data update from the CPU, then propagates the data among its connected devices:� As server: the 140 NOP 850 00 sends a buffered report, unbuffered report, or GOOSE.� As client: the 140 NOP 850 00 issues a control object command, or a buffered report,

unbuffered report, or GOOSE.

IEC61850 Messaging Specifications

The 140 NOP 850 00 module presents the following IEC61850 messaging features:

Feature Capacity

Client

Polling period per IED 1000 ms (default; configurable)

Maximum number of data attributes 100001 data attributes

Maximum number of concurrent IED connections 16 connections (provided the maximum of 10000 data attributes is not reached)

Maximum number of words for data in flow variables 20002, 3, 5 words

Maximum number of words for data out flow variables 20003, 4 words

1. The maximum number of data attributes includes the sum of client and server data attributes.2. The maximum number of input words includes the sum of client and server input words.3. The maximum number of variables depends on the data types included in the application (see page 23), because the lengths of different data types varies. 4. The maximum number of output words includes the sum of client and server output words.5. Module memory contains the most current (real-time) value for data in flow.


22 NHA31369 07/2015

NOTE: IEC61850 communications are given a higher priority than Modbus TCP communications.

Explicit Messaging Specifications

The 140 NOP 850 00 module presents the following Modbus TCP explicit messaging features:

Server

Maximum number of concurrent client connections 16 connections

Maximum number of data sets 100 data sets

Maximum number of data attributes per data set 256 data attributes per data set

Maximum number of data attributes 100001 data attributes

Maximum number of virtual logical devices within an IED 16 logical devices

Maximum number of report control blocks within an IED 64 total buffered plus unbuffered report control block instances

Maximum number of instances of a single buffered control block

8 (serving 8 clients)

Maximum buffer size of each buffered control block 16k bytes

Maximum number of control blocks for GOOSE publishing 4 control blocks

Maximum number of inputs in a GOOSE data set 256 inputs (provided the length of the message does not exceed one Ethernet frame)

Maximum number of words for data in flow variables 20002, 3 words

Maximum number of words for data out flow variables 20003, 4 words

Feature Capacity

1. The maximum number of data attributes includes the sum of client and server data attributes.2. The maximum number of input words includes the sum of client and server input words.3. The maximum number of variables depends on the data types included in the application (see page 23), because the lengths of different data types varies. 4. The maximum number of output words includes the sum of client and server output words.5. Module memory contains the most current (real-time) value for data in flow.

Feature Capacity

Client

maximum number of simultaneous connections 16 connections

maximum number of concurrent requests 16 requests

Server

maximum number of requests that can be transferred to the CPU per scan

12 requests

maximum number of simultaneous connections 16 connections


NHA31369 07/2015 23

Comparing Standard Data Types: Unity Pro and IEC618 50 Data Types

The following list presents IEC61850 standard data types and the comparable data type used by Unity Pro:

Maximum message size

read 250 bytes (125 words) excluding header

write 240 bytes (120 words) excluding header

Maximum Explicit I/O memory allocation size

Maximum number of allocated words 4000 (less memory allocated to implicit data in flow and out flow variables)

Feature Capacity

Unity Pro Standard Comparable IEC61850 Standard

Data Type Data Type Support by

Server Client

WORD BITSTRING (see page 24) √ √

BOOL1 BOOLEAN √ √

WORD CODED ENUM (see page 25) √ √

WORD Dbpos √ √

WORD ENUMERATED √ √

INT INT8 √ √

BYTE INT8U √ √

INT INT16 √ √

UINT INT16U √ √

DINT INT32 √ √

UDINT INT32U √ √

Timestamp TIME850FORMAT (see page 140)

√ √

1. In Unity Pro, a BOOL occupies one BYTE.


24 NHA31369 07/2015

BITSTRING

IEC61850 supports trigger, option, and quality report elements in BITSTRING format. Unity Pro maps BITSTRING to the WORD data type. In each of the following structures, Bit0 is the most significant bit.

Trigger option of report structure: The following bits indicate the stated trigger value when equal to 1:

Option field of report structure: The following bits indicate the stated option value when equal to 1:

Quality element structure: The following bits indicate the stated quality value when equal to 1:

Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7

Reserved Data-change

Quality-change

Data-update

Integrity General-interrogation

0 0

MSB Bit0 Bit1 Bit2 Bit3 Bit4 Bit5 Bit6 Bit7

Reserved Sequence-number

Report-timestamp

Reason for inclusion

Data-set-name

Data-reference

Buffer-overflow

EntryID

LSB Bit8 Bit9 Bit10 Bit11 Bit12 Bit13 Bit14 Bit15

Conf-revision

Segmen-tation

– – – – – –


Validity:00 = good01 = invalid10 = reserved11 = questionable

Overflow Out-of-range

Bad-reference

Oscillatory

Detected failure

Old-data


Inconsis-tent

Inaccurate

Source:0 = process1 = substituted

Test Operator-blocked

– – –


NHA31369 07/2015 25

CODED ENUM

Dbpos (double position) definition from IEC61850-8-1:

Custom Data Types

The 140 NOP 850 00 module also provides the following custom data types, which are used to support module DDTs:� IEDERTBUF (see page 135)� IEDEVTM (see page 136)� IEDEVTQ (see page 137)� IEDRPT (see page 135)� TIME850FORMAT (see page 140)� TIME870FORMAT (see page 140)

Refer to the presentation of each custom data type elsewhere in this document for a description of its structure.


– – – – – – – –


00 = intermediate state01 = Off10 = On11 = Bad state

– – – – – –


26 NHA31369 07/2015

NHA31369 07/2015 27

Quantum IEC61850

Installing the 140 NOP 850 00 Module

NHA31369 07/2015


Chapter 2Installing the 140 NOP 850 00 Module

Mounting a 140 NOP 850 00 Module on the Backplane

Introduction

Use these instructions to mount a 140 NOP 850 00 module onto a Quantum local rack.

Grounding Considerations

Do not apply power to a Quantum rack until connections are made at both ends of the Ethernet cable. For example, connect the cable to both the 140 NOP 850 00 and another device or ConneXium dual-ring switch DRS before you turn on the power.

Refer to the Quantum EIO System Planning Guide for details on dual-ring switches (DRSs).

DANGERELECTRICAL SHOCK HAZARD

� Switch off the power supply to the automation controller stations at both ends of the connection before inserting or removing an Ethernet cable.

� Use suitable insulation equipment when inserting or removing all or part of this equipment.

Failure to follow these instructions will result in death or serious injury.


28 NHA31369 07/2015

Mounting a Module

Replacing a Module

You can replace a 140 NOP 850 00 module at any time using another 140 NOP 850 00 module. The replacement module obtains its operating parameters over the backplane connection from the CPU. The transfer occurs immediately at the next cycle to the device.

The operating parameters that the CPU sends to a replacement module do not include any parameter values that were edited in the original module using explicit messaging SET commands.

Step Action

1 Hold the module at an angle and mount it on the 2 hooks near the top of the backplane. The figure shows the correct way to hold the module:

2 Swing the module down so the connector engages the backplane connector.

3 Use a Phillips-head screw driver to tighten the screw at the bottom of the module from 2 to 4 in-lbs or from .22 through .45 N•m of torque.

NHA31369 07/2015 29

Quantum IEC61850

Configuring the 140 NOP 850 00 Module

NHA31369 07/2015


Chapter 3Configuring the 140 NOP 850 00 Module

Introduction

This chapter shows you how to use Unity Pro programming software, including the Modicon IEC61850 Configuration Tool, to select and configure the 140 NOP 850 00 module on the local rack.

NOTE: The instructions presented in this chapter may include specific choices made for a sample project. Your Unity Pro project may include different choices that are appropriate for your specific configuration.


This chapter contains the following sections:

Section Topic Page

3.1 Creating a Project in Unity Pro 30

3.2 Introducing the IEC61850 Configuration Settings 37

3.3 Configuring IP Addresses 47

3.4 Ethernet Services 51

3.5 Security 60

3.6 Uploading and Downloading Configuration Settings 62


30 NHA31369 07/2015

Creating a Project in Unity Pro

Section 3.1Creating a Project in Unity Pro

Overview

This section shows you how to add modules — including the 140 NOP 850 00 module — to your project, using Unity Pro.

NOTE: For detailed information about how to use Unity Pro, refer to the online help and documentation DVD that come with Unity Pro.

What Is in This Section?

This section contains the following topics:

Topic Page

Creating a Project in Unity Pro 31

Configuring the Module Name and Starting Memory Location 35


NHA31369 07/2015 31

Creating a Project in Unity Pro

Introduction

You may have already created a project in Unity Pro and installed a power supply. If so, jump to the instructions for Adding a 140 NOP 850 00 Module (see page 34). If not, the following pages show you how to create a new Unity Pro project and add the following components:� A CPU� A power supply� A 140 NOP 850 00 module

NOTE: Design your network so that IEC61850 GOOSE transmissions and Quantum Ethernet remote I/O transmissions are not carried by the same media.

Creating and Saving a New Unity Pro Project

The following steps describe the creation of a project:

Step Action

1 Open Unity Pro.

2 In the Unity Pro main menu, select File → New....The New Project window opens displaying a list of Schneider Electric controller types.


32 NHA31369 07/2015

3 In the New Project window, expand the Quantum node and select both a CPU and a rack. In this example, a 140 CPU 670 60 controller (which supports Hot Standby) and a 10 slot rack are selected:

4 Click OK. Unity Pro displays the Project Browser .

5 To save the project, select File → Save. The Save As dialog opens.

6 In the Save As dialog, do the following:1. Enter a File name which is the name of your Unity Pro project. 2. Select the .STU or .STA extension in the Save As field.3. Click Save.

NOTE: If you do not save the project as an .STU or .STA file type, Unity Pro does not save the 140 NOP 850 00 IEC61850 configuration.

Step Action


NHA31369 07/2015 33

Adding a Power Supply to the New Unity Pro Project

The next step is to add a power supply to your Unity Pro project:

Step Action

7 In the Project Browser , double-click Local Bus . Unity Pro displays both the:� Local Bus window with the selected CPU in the second position, and� Hardware catalog displaying the Local Bus tab, below:

8 In the Hardware catalog , under the Supply node, select then drag a power supply (in this example, a 140 CPS 111 00) to the slot 1 position in the rack.


34 NHA31369 07/2015

Adding a 140 NOP 850 00 Module to the New Unity Pro Pr oject

The next task is to add a 140 NOP 850 00 module to your project. To do this, you first need to download and install the Modicon IEC61850 Configuration Tool:

Next, you need to open the Configuration tab for the 140 NOP 850 00 module, where you can:� Configure the Module name and %MW Start Address settings.� Launch the Modicon IEC61850 Configuration Tool, where you can configure IEC61850 settings

for the 140 NOP 850 00 module.

9 In the File menu, select Save, to save your edits.

NOTE: Schneider Electric recommends that you periodically save your changes as you make edits.

Step Action

Step Action

10 Contact your Schneider Electric sales agent to obtain the installation files for the Modicon IEC61850 Configuration Tool.

11 Insert the installation CD into your PC, then navigate to and double-click Setup.exe . The Modicon IEC61850 Configuration Tool installation wizard starts-up.

12 Follow the wizard instructions to install the Modicon IEC61850 Configuration Tool. This process adds the 140 NOP 850 00 to the Hardware Catalog .

13 In the Hardware catalog , under the Communication node, drag a 140 NOP 850 00 module to an open slot in the rack — in this example, slot 4:

14 In the File menu, select Save to save your edits.


NHA31369 07/2015 35

Configuring the Module Name and Starting Memory Loc ation

Overview

Use the Configuration tab of the 140 NOP 850 00 module properties window to configure the:

� module name� starting %MW memory address for storage of data items

The following steps present one example of how to configure the module name and starting memory address. Your own project configuration may differ.

Setting the Starting Memory Address and Naming the Module

The Properties window opens when you double-click the left mouse button on the image of the 140 NOP 850 00 module in either the Local Bus window or the Project Browser .

Use the Configuration tab to edit the 140 NOP 850 00 module name and starting memory address:

To input the above settings, take the following steps:

Step Action

1 Right click the 140 NOP 850 00 module, then select Open Module in the context menu.

2 Select the Configuration tab.

3 Enter a Module name : an ASCII string up to a maximum of 10 characters.

NOTE: The beginning character cannot be an Arabic numeral.


36 NHA31369 07/2015

NOTE: The %MW real used size field is read-only. After module configuration is complete, Unity Pro allocates memory addresses for the module’s data items; then enters the allocated amount of memory into the %MW real used size field.

The maximum size of all 140 NOP 850 00 module memory items is 4000 words. The actual size is determined by the specific module configuration. For maximum allocations of:� Implicit (I/O) messaging data refer to IEC 61850 Messaging Specifications (see page 21).� explicit messaging data refer to Explicit Messaging Specifications (see page 141).

Refer to the topic Working with IEC 61850 Data Objects (see page 115) for information about the data items automatically created by Unity Pro, when you click Update application .

4 Enter a %MW Start Address : an integer value from 1 to the maximal %MW address, which depends upon the memory capacity of the CPU.

5 Select Validate in the main menu. A message opens informing you that the module name cannot be edited after validation.

6 Click OK to close the message. The Module name becomes read-only.

Step Action


NHA31369 07/2015 37

Introducing the IEC61850 Configuration Settings

Section 3.2Introducing the IEC61850 Configuration Settings

Introduction

This section introduces the IEC61850 configuration settings.



Topic Page

Selecting the IEC61850 Edition 38

Using the Modicon IEC61850 Configuration Tool 39

General Window 43


38 NHA31369 07/2015

Selecting the IEC61850 Edition

Overview

After configuring the module name and starting memory address settings for the module, you need to create an IEC61850 project, then select the IEC61850 protocol supported by your 140 NOP 850 00 module.

Selecting the IEC61850 Edition

To select the edition of IEC61850 supported by your module, follow these steps:

NOTE: When Unity Pro displays IEC61850 configuration settings, it presents one of the following collections of module data:� For a new IEC61850 project, the General window displays default settings.� For a project created using a pre-existing IEC61850 project file, the General window displays

the saved configuration settings.

Step Action

1 In the Configuration tab, click the IEDCT Configuration button.The Modicon IEC 61850 Configuration Tool opens, displaying the Create Project dialog.

NOTE: Only one instance of the Modicon IEC 61850 Configuration Tool can be open at a time.

2 In the Create Project dialog, select either:� Create New Project or� Open Project

3 If you selected Open Project :1. Click the ellipsis button to open the Open dialog.2. Navigate to and select an existing project (.prj) file.3. Click Open .

The Open dialog closes, and the selected project and path are displayed in the Create Project dialog.

4. Click OK.

NOTE: � Because the saved project file already contains an edition selection setting, the

IEC61850 Edition Selection dialog (described below) does not appear. Instead, the General window opens.

� If the previously saved IEC61850 configuration cannot be found, the tool asks you to navigate to and select the IEC61850 configuration file to open. If you do not select a saved configuration, you need to create and configure a new project.

4 If you selected Create Project , the IEC61850 Edition Selection dialog opens.

5 Select the edition, or version, of the IEC61850 protocol that applies to your module:� Edition 1.0� Edition 2.0

NOTE: Schneider Electric recommends that you use the 140 NOP 850 00 module only in IEC61850 networks where all devices support the same edition of the IEC61850 protocol.

6 Click OK.The General window opens.


NHA31369 07/2015 39

Using the Modicon IEC61850 Configuration Tool

Introduction

The IEC61850 configuration interface in Unity Pro is the exclusive tool for configuring IEC61850-based properties of the 140 NOP 850 00 module.

Use the Modicon IEC61850 Configuration Tool to perform the following tasks:� Configure the 140 NOP 850 00 module as an IEC61850 server or client� Configure the IP address settings for the module� Configure Ethernet services for the module, including:

� RSTP� SNMP� SNTP� Baud rates for the Ethernet ports

Workbench

The workbench is the parent window of the IEC61850 interface. It presents:� The toolbar� One or more configuration windows, each on its own tab

The workbench:


40 NHA31369 07/2015

Toolbar

The Modicon IEC61850 Configuration Tool presents a toolbar with the following functions:

Saving and Backing Up your IEC61850 Project

When you identify a project backup folder, a copy of the project file is saved to the specified location each time you click Save in the IEC61850 configuration tool.

To specify a project folder, follow these steps:

Icon / Name Description

SaveSaves edits made to configuration settings.

NOTE: If you have configured a project backup folder, a copy of the IEC61850 configuration is saved to that location.

ValidatePerforms a validation check of the configuration.

NOTE: If one or more configuration errors are detected, a message opens describing one of the detected errors. Click this button after each configuration error is fixed, until the message indicates no detected errors.

Undo Reverses the previous edit.

Redo Repeats a text edit that was reversed via the Undo command.

CutRemoves and saves selected text.

CopyCopies selected text.

PasteInserts text that was cut or copied.

Full ScreenToggles the size of the Modicon IEC61850 Configuration Tool: normal size or full screen.

Step Action

1

In the upper left corner of the Modicon IEC61850 Configuration Tool, click on the icon. The Application Preferences page opens.

2 Click Backup .

3 Click the ellipsis button (...) to open Browse For Folder window.

4 Navigate to and select the folder where you want to store project backup files, then click OK.

3 Close the Application Preferences page.


NHA31369 07/2015 41

Breadcrumb Navigation

A breadcrumb navigation bar sits at the top of each tab, and describes the path to the displayed page, starting with the General window:

Click a breadcrumb item to move to that window.

You can also click a breadcrumb item to display a context menu containing the available child windows. For example, right-click on the black arrow in the IEC61850 Server breadcrumb item to display the following menu:

Click the name of a child window to open it.


42 NHA31369 07/2015

Exiting the Modicon IEC61850 Configuration Tool

When you close the Modicon IEC61850 Configuration Tool and Unity Pro, it continues to run in the background on your PC.

To exit the Modicon IEC61850 Configuration Tool, follow these steps:

Step Action

1 Click the close button (with the red “x”) at the upper right corner of the Modicon IEC61850 Configuration Tool.

2 In the Confirm dialog, indicate if you want to save data before closing (Yes or No).

3 On your PC task bar, click the Show hidden icons button. The list includes an icon for the Modicon IEC61850 Configuration Tool:

4 Right-click on the Modicon IEC61850 Configuration Tool icon, and select Exit .

5 In the Confirm dialog, select Yes, indicating you wish to exit the application.


NHA31369 07/2015 43

General Window

Introduction

After you select an IEC61850 edition, the General window opens when you start up the Modicon IEC61850 Configuration Tool:


44 NHA31369 07/2015

Use the General window to:� Edit module information� Select the Ethernet port used for GOOSE publication� Configure and view the size and starting memory location for the module.� Enable and disable the embedded IEC61850 server � Enable and disable the embedded IEC61850 client� Open the following windows where you can continue to configure 140 NOP 850 00 module

functions:� Communication settings� I/O mapping� Server settings� Client settings

Editing Module Information

Use the Module Information section to edit the name of the module, and to view settings that describe the module commercial reference and protocol edition.

The Module Information section presents the following settings and commands:

Setting Description

Module Name A read-only string of ASCII characters. This value is entered in the module Configuration tab when the module is added to the Unity Pro project. (see page 35)

NOTE: Unity Pro uses this setting as the base string for naming module variables.

IEC61850 Edition A previously selected (see page 38), read-only description of the edition of the IEC61850 protocol supported by the 140 NOP 850 00 module

Reference The read-only commercial reference, or product name, for the 140 NOP 850 00 module.

PDU Size The size of the manufacturing message specification (MMS) protocol data unit (PDU), from 4K bytes to 64K bytes. Default = 16K bytes.

Communication Settings (see page 47) button

Opens the Communication Settings window, which consists of the following tabs:� IP Setting , where you can assign roles and IP addresses to the four Ethernet ports

of the module.� RSTP, where you can enter settings to configure the embedded Ethernet switch to

be part of a redundant, loop-free logical Ethernet network. � SNTP, where you can configure the internal clock of the module to synchronize with

a network time server.� SNMP, where you can configure the SNMP client service in the module that allows

access to module diagnostic and management information. � Security , where you can restrict access to the module via TCP port 502.� Switch , where you can set baud rates for the four Ethernet ports.


NHA31369 07/2015 45

Selecting GOOSE Publication Port

Use the Goose Publish area to specify the Ethernet port or ports used to transmit GOOSE control blocks.

The Goose Publish area presents the following settings:

Viewing Module Memory Location and Size

The Module Memory area displays the size and starting location of memory space reserved for:� input items� output items� explicit items

NOTE: The Modicon IEC61850 Configuration Tool automatically calculates the memory space allowed to each group of items, based on your I/O Mapping (see page 108) configuration. The beginning memory position is the position you specified (see page 35) as the %MW Start Address setting in the Configuration tab of the Properties window.

The Module Memory section presents the following settings:

Setting Description

Ethernet Port Select the port used for GOOSE publication:� Eth Port 3&4 (default)� Eth Port 1� Eth Port 2

NOTE: � If the port you select shares an IP address with other ports, GOOSE

transmissions are published over all ports that share the IP address.� GOOSE publication occurs if the Ethernet cable to the selected port is

connected or disconnected. GOOSE diagnostic codes (see page 169) are unaffected by the cable being connected or disconnected to the port.

Auto Enable Indicate if a GOOSE transmission is sent on start-up or re-start:� Selected = a GOOSE transmission is sent.� De-selected = a GOOSE transmission is not sent.

Setting Description

Input Index (%MW) The starting address offset for input data.

Input Size The number of 16-bit words dedicated to input data.

Output Index (%MW) The starting address offset for output data.

Output Size The number of 16-bit words dedicated to output data.

Explicit Index (%MW) The starting address offset for explicit messaging data.

Explicit Size The number of 16-bit words dedicated to explicit messaging data.

I/O Mapping button Opens the I/O Mapping window, where you can map server and client data attributes to module memory addresses.


46 NHA31369 07/2015

Enabling and Disabling the IEC61850 Server

Use the controls in the Server Function section to enable and disable the IEC61850 server.

The Server Function section presents the following settings:

NOTE: Enabling the server does not complete the server configuration. After enabling the server, click the IEC61850 Server Settings button to open the IEC61650 Server window, where you can complete the server configuration.

Enabling and Disabling the IEC61850 Client

Use the controls in the Client Function section to enable and disable the IEC61850 client.

The Client Function section presents the following settings:

Setting Description

Enable IEC61850 Server Select this to enable the IEC61850 server; de-select it to disable the server. This setting is de-selected by default.

NOTE: � When this setting is Selected: the IEC61850 Server Settings button is

enabled.� If you enable and configure the IEC61850 server; and then disable the

server, your server configuration settings are saved. The saved server settings are re-applied when you later select this setting and enable the server.

IEC61850 Server Settings button

Opens the Client Settings window, where you can complete the configuration of client settings.

NOTE: This button is enabled only when Enable IEC61850 Client is selected.

Setting Description

Enable IEC61850 Client Select this to enable the IEC61850 client; de-select it to disable the client. This setting is de-selected by default.

NOTE: When this setting is:� Selected: the IEC61850 Client Settings button is enabled.� De-selected: all previously configured client configuration settings for this

module are permanently deleted.

IEC61850 Client Settings button

Opens the Client Settings window, where you can complete the configuration of client settings.

NOTE: This button is enabled only when Enable IEC61850 Client is selected.


NHA31369 07/2015 47

Configuring IP Addresses

Section 3.3Configuring IP Addresses

Assigning Roles and IP Addresses to Ethernet Ports

Introduction

Use the Communication Settings → IP Setting tab to assign roles and IP address settings to the four ports of the 140 NOP 850 00 module:

After changing any IP address setting in this tab, click Apply to confirm and retain your edits before clicking on another Communication Settings tab. Alternatively, you can click Cancel to delete your edits on the current tab and restore the previous setting.


48 NHA31369 07/2015

Port Roles

The 140 NOP 850 00 module includes four Ethernet ports and supports three different IP interfaces. These ports can be configured as the following port types:

The module includes an internal router that handles and forwards packets among the three IP interfaces.

Ethernet Frames

The 140 NOP 850 00 module supports the Ethernet II frame type. The module supports the IEEE 802.3 frame type only for RSTP.

Type Description Available

Port 1 (ETH 1)

Port 2 (ETH 2)

Ports 3/4 (ETH 3/4)

Access Port Diagnostic information is available via explicit messaging (Modbus) or via SNMP.

NOTE: A port set to Access Port type uses the IP address of the network that is set for Ports 3/4.

√ √ –

Extended Network You can extend the device network by adding another network to this port.

√ √ –

Port Mirroring You can connect to this port via a PC and use packet sniffing software to analyze the traffic traveling through one or more of the other module ports.

√ – –

Dedicated Network Ports

Ports 3 and 4 (ETH 3 and ETH 4) share a single IP address and are dedicated connections.

NOTE: Ports 3 and 4 (ETH 3 and ETH 4) support RSTP (see page 52).

– – √

√ The port type is available for this port.– The port type is not available for this port.


NHA31369 07/2015 49

Assigning IP Address Settings

All IP addresses settings need to be manually assigned in this window as part of module configuration.

The IP Setting tab presents separate configuration areas for Port 1 , Port 2 , and Port 3/4 . To configure each port, enter values for the following settings:

NOTE: � If the IP address for a port is not configured, the 140 NOP 850 00 modules automatically assign

that port a MAC address-based IP address (see page 50).� If the IP address for a port is not valid – for example, a malformed or duplicate IP address – the

module LEDs indicate the invalid IP address status.

Setting Description

Type Select the role to assign to the port. Selections include:� Port 1:

� Access Port� Extended Network� Port Mirroring

� Port 2:� Access Port� Extended Network

� Port 3/4: Not applicable. (The role for these ports is fixed as dedicated control network ports.)

IP A 32-bit IP address assigned to the port, including both network and host components.

Sub-Network Mask A 32-bit value used to mask the network portion of the IP address and reveal the host address.

Default Gateway For Port 3/4, the IP address of the router that is the access point to a remote network.

NOTE: 0.0.0.0 is a valid setting.


50 NHA31369 07/2015

Configuring Port Mirroring

You can configure Port 1 (ETH 1) to serve as a mirroring port. A copy of Ethernet packets traveling through other selected ports is sent to Port 1 , where you can use a packet sniffer to monitor and analyze network traffic.

When port mirroring is enabled, Port 1 becomes a read-only port. There is no access to network devices via this port while port mirroring remains enabled.

To configure Port 1 (ETH 1) for port mirroring, follow these steps:

Determining Port Default IP Addresses

If one or more Ethernet ports on the 140 NOP 850 00 module are not manually assigned an I P address, the module automatically assigns default IP addresses that are based on the MAC address, as follows:� Port 1 (ETH 1): 169.254.30.xxx� Port 2 (ETH 2): 169.254.20.xxx� Port 3/4 (ETH 3/4): 169.254.10.xxx

In each case, ‘xxx’ represents the sixth octet of the module MAC address. However, if the sixth octet of the module MAC address is 0xff or 0x00, ‘xxx’ is reset to 0xfe (254) to avoid the generation of an invalid IP address.

NOTE: Both the IEC61850 server and client are disabled while the module is using a default IP address.

Step Action

1 In the Port 1 area, select Port Mirroring as the port Type .The check boxes at the bottom of the Port 1 area are enabled.

2 Select the ports whose traffic is mirrored and sent to Port 1 :

Enable Internal Port Select this to send a copy of traffic passing through the internal port (between the module internal router and the module CPU) to Port 1 .

Enable ETH2 Select this to send a copy of traffic passing through Port 2 (ETH 2) to Port 1 .



3 Click Apply to confirm your edits.

4 Click Save to save your edits.


NHA31369 07/2015 51

Ethernet Services

Section 3.4Ethernet Services

Overview

This section describes the Ethernet services supported by the 140 NOP 850 00 module.



Topic Page

Configuring the Rapid Spanning Tree Protocol 52

Configuring Time Synchronization 53

Configuring the SNMP Agent 56

Configuring QoS Ethernet Packet Tagging 58

Configuring Data Rates 59


52 NHA31369 07/2015

Configuring the Rapid Spanning Tree Protocol

Introducing RSTP

Ethernet ports 3 and 4, located on the front of the 140 NOP 850 00 module, support the Rapid Spanning Tree Protocol (RSTP). RSTP is an OSI layer 2 protocol defined by IEEE 802.1D 2004. RSTP performs 2 services:� It creates a loop-free logical network path for Ethernet devices that are part of a topology that

includes redundant physical paths. � It automatically restores network communication — by activating redundant links — in the event

the network experiences an interruption of service.NOTE: RSTP can take up to 50 ms to restore network communication in case of a service interruption. During this time, Ethernet packets may be dropped.

RSTP software, operating simultaneously in all network switches, obtains information from each switch, which enables the software to create a hierarchical logical network topology. RSTP is a flexible protocol that can be implemented on many physical topologies, including ring, mesh, or a combination of ring and mesh.

Use the RSTP tab of the Communication Settings window to configure RSTP for the embedded Ethernet switch in the 140 NOP 850 00 module. After you make your selection, click Apply to preserve your edit.

NOTE: RSTP can be implemented only when all network switches are configured to support RSTP.

Configuring RSTP Settings

The following setting can be viewed and edited in the Communication Settings → RSTP tab:

Setting Description

RSTP Operational State: Bridge Priority

Select one of the following RSTP roles for the module:� Root (0)� Backup Root (4096)� Participant (32768) (default)

NOTE: Network switches running RSTP software periodically exchange information about themselves using special packets called Bridge Protocol Data Units (BPDUs), which act as a heartbeat. The Bridge Priority value is contained in the BPDU and establishes the relative position of the switch in the RSTP hierarchy.


NHA31369 07/2015 53

Configuring Time Synchronization

Introduction

The simple network time protocol (SNTP) synchronizes the clock in the 140 NOP 850 00 module to that of the network time server. The synchronized value is used to update the clock in the PLC. Typical time service configurations utilize redundant servers and diverse network paths to achieve high accuracy and reliability.

Use the time service for:� Event recording (sequence events)� Event synchronization (trigger simultaneous events)

Time Synchronization Service Features

Features of the time synchronization service include:� Periodic time correction obtained from the reference-standard time server.� Automatic switch-over to a backup time server if communication with the primary time server is

interrupted.� Availability of a function block for application programs that can read the accurate clock, and let

project events or variables be time stamped.� An estimated time stamping accuracy of:

� 1 ms for the 140 NOP 850 00 module� 5 ms for 140 CPU 651 •0 and later CPUs� 10 ms for other CPUs

� Configurable local time zone, including daylight savings time

NOTE: Broadcast frames for clock synchronization are not supported.

Time Synchronization Process

The 140 NOP 850 00 module contains an SNTP client, which provides time synchronization:

Sequence Action Result

1 An SNTP client requests a time synchronization signal from an SNTP server. (The request is sent over an Ethernet network.)

The SNTP server responds with a signal.

2 The SNTP client stores the time. –

3 The SNTP client sends a message to the controller’s clock system counter.

The controller updates its internal clock.

4 Use the R_NTPC function block in either MAST, FAST, or interrupt sections to read the clock from the PLC application.

–


54 NHA31369 07/2015

On an Ethernet network, all controllers should be synchronized with the same SNTP server.

When the 140 NOP 850 00 module is synchronized to the CPU clock via the SNTP service, the 140 NOP 850 00 module can achieve accuracy to within 1 ms.

Power Up

To establish the accurate Ethernet system network time, the system performs the following at power-up:� Requires the 140 NOP 850 00 module to restart� Uses the 140 NOP 850 00 module to obtain the time from the SNTP server� Requires a predefined interval until time is accurate; your configuration determines how long

before time is accurate� May require several updates to achieve peak accuracy

After the accurate time is received, the service sets the status in the associated time service register.

The time service clock value starts at 0 until fully updated from the 140 NOP 850 00 module.

Stop or Run PLC

� Stop and run have no effect on the accuracy of the clock.� Stop and run have no effect on the update of the clock.� A transition from one operating mode to another has no effect on the accuracy of the Ethernet

system network time.

Download Application

The status clock value associated with the time service register in the CPU is re-initialized after an application is downloaded or after an SNTP server swap.

There will be two polling periods before the time is accurate.

Model Starting date

Modicon Quantum with Unity Pro January 1st 1970 00:00:00.00


NHA31369 07/2015 55

Time Synchronization Configuration Settings

The Communication Settings → SNTP tab presents the following configuration settings:

When you finish editing time synchronization configuration settings, click Apply to preserve your edits.

Setting Action

NTP Server Configuration:

Primary NTP Server IP Address

The IP address for the primary SNTP server.

Secondary NTP Server IP Address

The IP address for the back-up SNTP server.

Polling Period The polling period is the time (in seconds) between updates from the SNTP server. To obtain optimal accuracy (and if your network allows), reduce the polling period to a small value. The default is 5 seconds.Valid values include:� minimum = 1 s� maximum = 120 s

Time Zone:

Time Zone Select the desired time zone from the drop-down list. The default value is your current system time zone (as found in Windows). You can also select Custom Time Zone .

Time Zone Offset If you selected Custom Time Zone , enter a value in the range of (24 hours * 60 minutes - 1) [1-minute step].

Daylight Saving:

Automatically adjust clock for daylight saving change

If this setting is:� De-selected : In the Start Daylight Saving and End Daylight Saving fields,

enter the month, day of week, and occurrence range from the respective drop-down lists. De-selected is the default.

� Selected : The 140 NOP 850 00 module automatically corrects the local time to account for daylight saving time. The Start Daylight Saving and End Daylight Saving fields are disabled because their times are automatically changed in the spring and fall every year.

Start Daylight Saving If automatic daylight savings adjustment is disabled, select values for:� Month : January to December� Day of Week : Sunday to Saturday� Occurrence : 1 to 5

End Daylight Saving If automatic daylight savings adjustment is disabled, selection values for:� Month : January to December� Day of Week : Sunday to Saturday� Occurrence : 1 to 5

CPU Time Update:

Update CPU time with this module

� Selected : The 140 NOP 850 00 module performs updates of the CPU clock.� De-selected : The module does not perform this task (default).


56 NHA31369 07/2015

Configuring the SNMP Agent

Description

The 140 NOP 850 00 module includes an SNMP v1 agent. An SNMP agent is a software component running on the 140 NOP 850 00 module that allows access to the module diagnostic and management information via the SNMP service.

SNMP browsers, network management software, and other tools typically use SNMP to access this data. In addition, the SNMP agent can be configured with the IP address of up to 2 devices — typically PCs running network management software — to be the target of event driven trap messages. These trap messages inform the management device of events such as cold start and unauthorized access.

Use the Communication Settings → SNMP tab to:� Configure the SNMP agent in the 140 NOP 850 00 module.� Download a copy of the Schneider Electric Private MIB to your PC.

NOTE: The SNMP service is enabled and disabled in the Communication Settings → Security tab.

The SNMP agent can connect to and communicate with up to 2 SNMP managers as part of an SNMP service. The diagnostic information provided by the SNMP service includes:� Standard SNMP MIB 2 � VLAN Bridge-MIB � Private MIB � TCP/IP � Port 502 messaging� Switching

Viewing and Configuring SNMP Properties

The following settings can be viewed and edited in the Communication Settings → SNMP tab:

Setting Description

IP Address Managers:

IP Address Manager 1 The IP address of the first SNMP manager to which the SNMP agent sends notices of traps.

IP Address Manager 2 The IP address of the second SNMP manager to which the SNMP agent sends notices of traps.

Agent:

Location The device location (32 characters maximum)

Contact Information describing the person to contact for device maintenance (32 characters maximum)

SNMP Manager If this is:� Selected : the Location and Contact information are editable in this tab� De-selected : Location and Contact settings are not editable in this tab


NHA31369 07/2015 57

When you finish editing SNMP property settings, click Apply to preserve your edits.

NOTE: The sysName SNMP parameter is not editable or visible in the Modicon IEC61850 Configuration Tool. By default, sysName is set to 140 NOP 850 00.

Downloading and Saving the Schneider Private MIB

The Schneider Private MIB is used together with the SNMP agent to manage system components. To download a copy of the Schneider Private MIB, follow these steps:

Community Names:

Get Password required by the SNMP agent before executing read commands from an SNMP manager. Default = Public .

Set Password required by the SNMP agent before executing write commands from an SNMP manager. Default = Public

Trap Password an SNMP manager requires from the SNMP agent before the manager accepts trap notices from the agent. Default = Public

Security:

Enable Authentication Failure Trap

If this is Selected , the SNMP agent sends a trap notice to the SNMP manager if an unauthorized manager sends a Get or Set command to the agent. Default = De-selected .

Properties:

Schneider Private MIB button Click this button to download and save a copy of the Schneider Private MIB file (see page 57).

Setting Description

Step Action

1 In the Communication Settings → SNMP tab, click the Schneider Private MIB button.The Save As dialog opens, displaying the file name “SchneiderTFE.mib”.

2 Navigate to the location where you want to store the file, then click Save.


58 NHA31369 07/2015

Configuring QoS Ethernet Packet Tagging

Description

The 140 NOP 850 00 module provides fixed priority packet tagging for Ethernet transmissions. No configuration is required for this service.

The module supports the OSI layer 3 Quality of Service (QoS) standard defined in RFC-2475. The module adds a differentiated services code point (DSCP) tag to each Ethernet packet it transmits, indicating the priority of that packet.

Type of Traffic Settings

QoS automatically prioritizes Ethernet packet streams based on the type of traffic in that stream. The 140 NOP 850 00 module recognizes the traffic types described below:

To implement QoS settings in your Ethernet network:� Use network switches that support QoS.� Consistently apply DSCP values to network devices and switches that support DSCP.� Confirm that switches apply a consistent set of rules for sorting DSCP tags, when transmitting

and receiving Ethernet packets.

Traffic type Prioritization value (default)

DSCP Value for Network Time Protocol Messages 59

DSCP Value for IEC 61850 Messages 43

DSCP Value for Explicit Messages 27


NHA31369 07/2015 59

Configuring Data Rates

Introduction

The embedded switch in the 140 NOP 850 00 module includes four Ethernet ports. Use the Communication Settings → Switch tab to specify the data rate and duplex setting for each port, or you let each port auto-negotiate these settings with the connected device.

Configuring Baud Rate Settings

You can select one of the following baud rate settings for each of the four Ethernet ports on the module:

After you finish editing baud rate settings, click Apply to preserve your edits.

Port Available settings

ETH1 Select one of the following settings:� 100 Mbits/sec Full duplex� 100 Mbits/sec Half duplex� Auto 10/100 Mbits/sec (default)

ETH2

ETH3 Select one of the following settings:� 1000 Mbits/sec Full duplex� 1000 Mbits/sec Half duplex� 100 Mbits/sec Full duplex� 100 Mbits/sec Half duplex� 10 Mbits/sec Full duplex� 10 Mbits/sec Half duplex� Auto 10/100/100 Mbits/sec (default)

ETH4


60 NHA31369 07/2015

Security

Section 3.5Security

Access Control

Restricting Access to the 140 NOP 850 00 Module

Using the Modicon IEC61850 Configuration Tool, you can open Communication Settings → Security tab and restrict access to the module by:� Disabling the module FTP service � Disabling the module SNMP service � Specifying the Ethernet devices that may make TCP port 502 connections with the module

Enabling and Disabling the FTP and SNMP Services

The 140 NOP 850 00 module uses the FTP service to support firmware upgrades, and uses the SNMP service to provide access to diagnostic information for the module.

You can enable and disable these services using the Modicon IEC61850 Configuration Tool in the Access Control tab of the Communication Settings window:� Select Enable FTP to enable the FTP service. De-select it to disable the service.� Select Enable SNMP to enable the SNMP service. De-select it to disable the service.

When you finish editing FTP and SNMP services, click Apply to preserve your edits.

Both services are disabled by default.

If the FTP service has been enabled in Unity Pro using the Modicon IEC61850 Configuration Tool, it can also be enabled or disabled at run time using an MBP_MSTR block (see page 142) with operation code FFF0 (hex).

Configuring Access Control

You can also use the Security tab of the Communication Settings window to specify the Ethernet devices that may make TCP port 502 connections with the module, in its role as either a Modbus TCP server. When you select Access Control , you need to add the IP addresses of the devices that may open a connection with the module.

When you enable access control, consider adding the following devices to the list of Authorized Addresses so that they may communicate with the module:� Any client device that may send a request to the 140 NOP 850 00 module, in its role as either

Modbus TCP server� Your own maintenance PC so that you can communicate with the PLC via Unity Pro to configure

and diagnose your application� Any target device to which the 140 NOP 850 00 module may send a Modbus TCP explicit

message


NHA31369 07/2015 61

NOTE: You do not need to list the IP address of a target device to which the 140 NOP 850 00 module may send an IEC61850 message.

Adding and Removing Devices in the Authorized Addre ss List

To add a device to the Authorized Addresses list:

To remove a device from the Authorized Addresses list, select its IP address in the list, then click the – button. The selected IP address is removed.

Step Description

1 In the Access Control area, select Access Control .

2 In the Authorized Address area, click the + button.A new row appears in the list, displaying a placeholder IP address.

3 Double-click the placeholder IP address.The IP address field becomes editable.

4 In the new IP address field, type the IP address of the device that is authorized to access the 140 NOP 850 00 module, then press Enter .

5 Repeat steps 2 through 4, above, for each additional device for which you want to grant access to the 140 NOP 850 00 module.

NOTE: You can add a specific IP address only once. Duplicate IP addresses are not allowed.

6 When you finish making access control edits, click Apply to preserve your edits.


62 NHA31369 07/2015

Uploading and Downloading Configuration Settings

Section 3.6Uploading and Downloading Configuration Settings

Uploading and Downloading Configuration Settings

Introduction

When you finish entering configuration settings for the 140 NOP 850 00 module, you need to perform the following tasks:� Update the application� Build the project� Transfer the built project to the CPU

After the built application is transferred to the CPU, the CPU transfers configuration settings to the 140 NOP 850 00 module.

NOTE: Configuration settings do not take effect until they are successfully downloaded from your PC to the CPU, and from the CPU to the 140 NOP 850 00 module.

Updating the Configuration

After you input configuration settings for the 140 NOP 850 00 module, update the configuration as follows:

Clicking Update application button creates variables that display the following information and commands for your Unity Pro project:� The status of the IEC61850 server and client.� The IEC61850 data model mapped into PLC memory.

Compiling the Project

To compile the updated project, in Unity Pro select either Build → Build Changes or Build → Rebuild All Project . Check the Output window to confirm the process succeeded.

Step Action

1 Close the Modicon IEC61850 Configuration Tool. The Confirm dialog opens.

2 Click Yes to save your edits. The Confirm dialog closes. In the Configuration tab of the 140 NOP 850 00 module Properties window, the Update application button is enabled.

3 Click the Update application button.


NHA31369 07/2015 63

Downloading the Application Program

After the application has been compiled, connect Unity Pro to the CPU (PLC → Connect ), then download the application to the CPU (PLC → Transfer Project to PLC .

To transfer the compiled application program from Unity Pro to the CPU, follow these steps:

On next power-up, the 140 NOP 850 00 module compares the application in the CPU against the one stored in the module.� If the applications are different – or if there is no application program in the module, the CPU

downloads the application program to the 140 NOP 850 00 module. The module stores the new application program in its non-volatile memory and loads it on start-up.

� If the applications are the same, the module loads the application program stored in its non-volatile memory.

Uploading the Application Program

To transfer the current application program from the CPU to Unity Pro, follow these steps:

NOTE: Uploading the application program does not also upload the IEC61850 settings of the 140 NOP 850 00 module. To apply IEC61850 settings, you need to have saved these settings in a .prj file during a previous configuration. For instructions on how to apply saved IEC61850 settings, refer to the topic Selecting the IEC 61850 Edition (see page 38).

Archiving the Application Program

To archive the application in Unity Pro, do one of the following:� Select File → Save As , then save the file as an .STU file type.� After building the project (Build → Build Changes/Rebuild All Project ), select File → Save

Archive... then save the file as an .STA file type.

NOTE: Saving your application as an .STA or .STU file type saves the entire Unity Pro project, including the IEC61850 project file. If you export the application as a .ZEF file type, the IEC61850 project file is not saved.

Step Action

1 Connect Unity Pro to the CPU: Select PLC → Connect .

2 Stop CPU operations if the CPU is executing an earlier version of the application: Select PLC → Stop .

3 Download the application to the CPU: Select (PLC → Transfer Project to PLC .

Step Action

1 Connect Unity Pro to the CPU: Select PLC → Connect .

2 Stop CPU operations if the CPU is executing an earlier version of the application: Select PLC → Stop .

3 Upload the application to the CPU: Select (PLC → Transfer Project from PLC .


64 NHA31369 07/2015

NHA31369 07/2015 65

Quantum IEC61850

IEC61850 Server

NHA31369 07/2015

Configuring the IEC61850 Server

Chapter 4Configuring the IEC61850 Server

Introduction

This chapter shows you how to configure the module as an IEC61850 server.

Before configuring server properties, you need to enable the IEC61850 server function in the General (see page 43) window. After you enable the IEC61850 server function, click the IEC61850 Server Settings button to open the Server Settings window.



Topic Page

Working with Server Configurations 66

Data Model 72

Instantiating Data Objects and Data Attributes 81

Working with Data Sets 84

Configuring Report Control Blocks 87

Publishing GOOSE Control Blocks 92

Working with ERT Data Sets 96

Subscribing to GOOSE Control Blocks from External References 99

IEC61850 Server

66 NHA31369 07/2015

Working with Server Configurations

Introduction

Use the IEC61850 Server window to perform the following functions for the 140 NOP 850 00 module:� View and edit server information, including:

� IP address

� Create a new IEC61850 server that is:� An empty IED server� Based on an external Schneider Electric ICD or CID file� Based on an external Schneider Electric SCD file

� Delete an IEC61850 server� Export an IEC61850 server file to:

� a CID/ICD file, or� an Excel spreadsheet file

� Open one of the following windows, where you can configure server functions:� Data Model (see page 72)� Application Settings (see page 81)� Data Set (see page 84)� Report Control (see page 87)� GOOSE Control (see page 92)� External Reference (see page 99)� ERT Data Set (see page 96)

IEC61850 Server

NHA31369 07/2015 67

Before configuring server properties, you need to enable the IEC61850 server function in the General (see page 43) window. After you enable the IEC61850 server function, click the IEC61850 Server Settings button to open the IEC61850 Server window.

IEC61850 Server

68 NHA31369 07/2015

Viewing Server Information

When a server is created, the Server Information area displays the following server settings:

NOTE: Before you create a new IEC61850 server, the Server Information settings are empty and disabled. After you create a new server instance, these settings display their default values.

Creating an Empty IED Server

To create a new empty IED server, follow these steps:

Setting Description

IED Name The read-only server name. By default, it is the same as the Module Name in the General window (see page 44).

Description The configurable description of the server. By default, it displays the description provided by the ICD template.

IP Select an IP address for the IEC61850 server. IEC61850 clients use this IP address to access the server.

NOTE: The list can contain up to 3 IP addresses. IP addresses are added to the list in the Communication Settings window.

Step Action

1 When the IEC61850 Server window opens, the Create IED Server dialog opens, presenting three selections:� Create an empty IED server� Select an external Schneider Electric ICD / CID file� Select an external Schneider Electric SCD file

NOTE: If you cancel the Create IEC61850 Server window, you need to click the Create IEC61850

Server button to re-open it.

2 Select Create an empty IED server . The OK button is enabled.

3 Click OK.The Input IED Name dialog opens.

4 In the Input IED Name dialog, accept the default name or enter a new name for this IED.

5 Click OK.The new server is created.

6 Save the new server.

NOTE: A new empty IED server contains no predefined functions. You need to create all the functions your new IED server requires.

IEC61850 Server

NHA31369 07/2015 69

Creating a New Server from an External Schneider El ectric ICD / CID File

You can create a new server instance from an ICD or CID file that was previously created and saved using the Modicon IEC61850 Configuration Tool. To create a new server from an external ICD or CID file, follow these steps:

Step Action




2 In the Create IED Server dialog, select Select an external ICD / CID file . The file path box and browse button are enabled.

3 Click the browse button beneath your selection.The Open dialog opens.

4 In the files of type list, select the type of file you want to select:� ICD file (*.icd)� CID file (*.cid)

5 Navigate to and select an ICD or CID file, then click Open .The dialog closes, and the name of the selected file appears in the path box.

6 Click OK. The Input IED Name dialog opens.

7 In the Input IED Name dialog, accept the default name or enter a new name for this IED.



IEC61850 Server

70 NHA31369 07/2015

Creating a New Server from an External Schneider El ectric SCD File

The Modicon IEC61850 Configuration Tool can create a new server from an IED file contained in an external SCD file. To create a new server from an external SCD file, follow these steps:

Deleting an Existing Server

You can delete the IEC61850 server instance that is currently displayed in IEC61850 Server window. To delete the server, follow these steps:

Step Action




2 In the Create IED Server dialog, select Select an external SCD file . The file path box and browse button are enabled.

3 Click the browse button beneath your selection.The Open dialog opens.

4 Confirm that in the files of type list, SCD file (*scd) is selected.

5 Navigate to and select the appropriate SCD file, then click Open .The dialog closes:� The name of the selected SCD file appears in the path box.� The Select IED to Import list is populated with IEDs associated with the selected SCD file.

6 In the Select IED to Import list, select the appropriate IED file, then click OK.The Input IED Name dialog opens.

7 In the Input IED Name dialog, accept the default name for this IED.

NOTE: Schneider Electric recommends you do not change the default IED name.



Step Action

1 Open the server you want to display in the IEC61850 Server window.

2Click the Delete this server configuration button .The Confirm dialog opens and asks if you are sure you want to delete the server.

3 In the Confirm dialog, click Yes.

The server is deleted, and the Create IEC61850 Server button is enabled.

4 Save your edits.

IEC61850 Server

NHA31369 07/2015 71

Exporting the Server to a CID or ICD File

You can export the IEC61850 server instance that is currently displayed in IEC61850 Server window, as a CID file. To export a server, follow these steps:

Exporting the Server to an Excel Spreadsheet File

You can export the configured IEC61850 server that is currently displayed in IEC61850 Server window, as an Excel 97-2003 spreadsheet file. To export a server, follow these steps:

The exported Excel spreadsheet file populates the following fields with configured server data:� Reference: the path and name of the data item.� BasicType: the data type of the item.� FC: The functional constraint value of the data item.� DO/DA: The type of item: data object (DO) or data attribute (DA).� Initial Value: The initialized value assigned to the data item.

All other fields in the spreadsheet are not populated.

Opening Additional Server Property Windows

To continue configuring properties for the IEC61850 server open in the IEC61850 Server window, click one of the following:� Data Model (see page 72)� Application Settings (see page 81)� Data Set (see page 84)� Report Control (see page 87)� GOOSE Control (see page 92)� ERT Data Set (see page 96)

Step Action

1 Click the Export toolbar button .The Save As dialog opens.

2 In the Save As dialog:� Navigate to the location where you want to save the exported file.� Select a file type: CID or ICD (or IID for Edition 2.0).� Click Save.

Step Action

1 Click the Export to Excel button.The Save As dialog opens.

2 In the Save As dialog:� Navigate to the location where you want to save the exported file.� Click Save.

IEC61850 Server

72 NHA31369 07/2015

Data Model

Introduction

Use the Data Model window to view, add, remove, and edit the IEC61850 data model for the 140 NOP 850 00 module IED.

The Data Model window displays:� A data model navigator (on the left), which you can use to move through the data model and

select individual data items.� A data model editor, which you can use to view, add, remove, and edit the data items associated

with the item selected in the data model navigator.

NOTE: The Modicon IEC61850 Configuration Tool supports flexible data modelling. You can manage name space assignments in the application to meet your application needs. The Modicon IEC61850 Configuration Tool does not manage name space designations by default.

The data model editor presents a different interface, depending on the item selected in the data model navigator. In the data model editor, you can add and remove optional data items. Mandatory data items are automatically added by default, and cannot be removed.

1 Data model navigator2 Data path display

IEC61850 Server

NHA31369 07/2015 73

3 Data model editor4 Module IED5 Logical devices6 Logical nodes7 Data objects8 Data attributes

Expand the navigation tree control and select a data item to display its related data items in the data editor:

Working with Logical Devices

A module IED can include up to 16 logical devices. The System logical devices node is mandatory. It is included by default and cannot be removed.

Each logical device includes the following parameters:� Instance :

The name of the logical device, up to 16 characters long.� Description :

The editable description for a logical device.

To add a logical device, follow these steps

To remove an optional logical device, select it in the data model editor, then right-click and select Delete . When the item disappears from the list, click Save.

In the data model navigator, select a... ...to display the following items in the data model editor...

Module IED Logical devices

Logical device Logical nodes

Logical node Data objects

Data object Sub data objects and data attributes

Step Action

1 In the data model navigator, select the module IED.The data model editor displays a list of logical devices.

2 Click Add .The Input Logical Device Instance Name dialog opens.

3 Enter a logical device name of up to 16 ASCII characters.

4 Click OK.The dialog closes, and the new logical device is added to the data model editor.

5 (Optional) In the data model editor, type in a Description for the new logical device, then click Enter .

6 Save your edits.

IEC61850 Server

74 NHA31369 07/2015

Working with Logical Nodes

When a logical device is selected in the data model navigator, the data model editor looks like this:

1 Data model navigator2 Data path display3 Logical node table4 Logical node group selector5 Logical node class list

The logical node table displays a list of logical nodes for the selected logical device. LLN0 is mandatory for each logical device; LPHD is mandatory for each system logical device. They are included by default and cannot be removed. Refer to the appendix for a list of logical nodes (see page 188) supported by the 140 NOP 850 00 module IED.

Each logical node includes the following parameters:� Name:

The read-only name of the logical node.� Prefix :

An optional prefix to the logical node, for ASCII “x” characters long. It is editable only when a new logical node is instantiated; thereafter it is read-only.

� LnClass : The read-only name of the logical node class.

� Instance : A read-only sequential number automatically assigned to a new logical node, “y” characters long. When more than one instance of a logical node class is added, this value increments by a value of 1.NOTE: The combined length of the Prefix plus Instance (x + y) cannot exceed 12 characters.

� Type :An editable value of up to 64 ASCII characters that defines data objects inside a logical node. The logical node type is derived from and extends a logical node class.NOTE: The logical node type name starts with the concatenation of “SE_” and the Class setting as the Type prefix.

IEC61850 Server

NHA31369 07/2015 75

For example, a logical node type of class ARIS begins with “SE_ARIS_”.� If you input text that matches this naming convention, (for example, "SE_ARIS_12345") the

Modicon IEC61850 Configuration Tool uses the input text as the Type setting.� If you input text that does not match this naming convention, the Modicon IEC61850

Configuration Tool adds the expected prefix to your input text. (for example, if you input the text "V001”, the value is edited to "SE_ARIS_V001".

� Description :An editable text field you can use to describe the logical node.

To add a logical node, follow these steps

To remove an optional logical node, select it in the logical node table, then right-click and select Delete . When the item disappears from the list, click Save.

Step Action

1 In the data model navigator, select a logical device.The data model editor displays a logical node table, a logical node group selector, and a logical node class list.

2 In the logical node group selector, select a logical node alphabetical group. The logical node class list displays items for the selected group.

3 Drag an item from the logical node class list to the logical node table.The Add Logical Node dialog opens.

4 In the Add Logical Node dialog, accept the default Prefix setting, or enter a new value.In the Add Logical Node dialog:� Accept the default Prefix (SE), or enter a value.

NOTE: if you enter a different prefix value, it will be added to the Name string. However the Type value will be the concatenation of the prefix “SE” and the LnClass value.

� Enter a Type value.

LnClass and Instance values are automatically generated.

5 (Click OK.The new logical node is added to the table.

6 Save your edits.

IEC61850 Server

76 NHA31369 07/2015

Working with Data Objects

When a logical node is selected in the data model navigator, the data model editor looks like this:

1 Data model navigator2 Data path display3 Data object table4 Data object list

The data object table displays a list of data objects for the selected logical node. The collection of available data objects for each logical node is pre-defined by the IEC61850 protocol. Mandatory data objects are included by default and cannot be individually removed.

NOTE: Mandatory data objects for an optional logical node can be removed only by removing the optional logical node.

Each data object includes the following parameters:� Name:

The name of the data object. It is:� Read-only for default data objects.� Editable for extended data objects.

NOTE: For data objects that can be added to a logical node more than once, the name includes a numerical instance suffix. For example, Ind1 represents the first instance of the Ind data object of the GGIO logical node.

� Common Data Class (CDC) : The read-only IEC61850 protocol-specified group to which the data object belongs.NOTE: Refer to the appendix for a list of CDCs (see page 196) supported by the 140 NOP 850 00 module IED.

� Mandatory : A read-only indicator that, when selected, indicates the data object is required for the logical node and cannot be removed.

IEC61850 Server

NHA31369 07/2015 77

� Type Name :An editable value that defines data objects inside a logical node. The logical node type is derived from and extends a common data class.NOTE: The logical node type name starts with the concatenation of “SE_” and the Class setting as the Type prefix.

For example, a type name of the common data class SPS begins with “SE_SPS_”.� If you input text that matches this naming convention, (for example, "SE_SPS_12345") the

Modicon IEC61850 Configuration Tool uses the input text as the Type Name setting.� If you input text that does not match this naming convention, the Modicon IEC61850

Configuration Tool adds the expected prefix to your input text. (for example, if you input the text "V001”, the value is edited to "SE_SPIS_V001".

There are two ways to add a data object:� Add an optional data object.� Extend a data object for the editing logical node.

NOTE: When you add a data object to a logical node, the data object is added not only to the logical node instance, but to the underlying structure of the logical node object itself. Therefore, if a logical node can be added to a logical device more than once (for example, LDevice → MSTA) every instance of that logical node contains the newly added data object.

To add a new data object, follow these steps:

Step Action

1 In the data model navigator, select a logical node.The data model editor displays a data object table and a data object list.

2 Drag an item from the data object list to the data object table.The Edit Data Object dialog opens.

3 In the Edit Data Object dialog, enter or select a Type . The text you enter or select is concatenated with the prefix “SE” and the CDC value to form the Type Name .

4 Clock OK to close the dialog. The new data object appears in the data object table.

NOTE: If the data object can be added to the table:� Only once, it is removed from the data object list.� More than once, the data object remains in the list and a numerical instance suffix is added

to the data object name in the table.

5 Save your edits.

IEC61850 Server

78 NHA31369 07/2015

To add a new extension object, follow these steps:

To remove an optional data object, select it in the data object table, then right-click and select Delete . When the item disappears from the list, click Save.

Working with Data Attributes

When a data object is selected in the data model navigator, the data model editor looks like this:

1 Data model navigator2 Data path display3 Data object table4 Data attribute list

Step Action1 In the data model navigator, select a logical node.

The data model editor displays a data object table and a data object list.2 Click Add Extension Object .

The Edit Data Object dialog opens.3 In the Edit Data Object dialog:

� Enter a Name of the new data object, up to ten ASCII characters. NOTE: The first character of the value must be a capital letter.

� Select a Common Data Class value.� Enter or select a Type . The text you enter or select is concatenated with the prefix “SE” and

the CDC value to form the Type Name .4 Clock OK to close the dialog. The new data object appears in the data object table.5 Save your edits.

IEC61850 Server

NHA31369 07/2015 79

The data attribute table displays a list of data attributes for the selected data object. The collection of available data attributes for each data object is pre-defined by the IEC61850 protocol. Mandatory data attributes are included by default and cannot be individually removed.

NOTE: A logical device can support up to 10000 data attributes.

Each data attribute includes the following parameters:� Name:

The read-only name of the data attribute.� BasicType :

The read-only IEC61850 protocol-specified data type for the data attribute. � Mandatory :

A read-only indicator that, when selected, indicates the data attribute is required for the data object and cannot be removed.

� FC: The functional constraint group of the data attribute.� Type : An text string describing the data attribute. If the BasicType is:

� A pre-determined, non-editable value, the Type setting is not displayed.� A variable type, specified at the time of creation, the value is displayed.

NOTE: When you add a data attribute to a data object, the data attribute is added not only to the data object instance, but also to the underlying structure of the data object. Therefore, if a data object can be added to a logical node more than once (for example, LDevice → MSTA → Beh → stVal) ) every instance of that data object contains the newly added data attribute.

To add a data attribute, follow these steps

To remove an optional data attribute, select it in the data attribute table, then right-click and select Delete . When the item disappears from the list, click Save.

Step Action

1 In the data model navigator, select a data object.The data model editor displays a data attribute table and a data attribute list.

2 Drag an item from the data attribute list to the data attribute table.The data attribute is added to the table.

NOTE: If the data object can be added to the table:� Only once, it is removed from the data object list.� More than once, the data object remains in the list and a numerical instance suffix is added

to the data object name in the table.

3 For some data attributes the Select Type of Data Attribute dialog opens:� For some attributes of the Stuct BasicType , you need to specify the attribute type. For

example, for LDevice → ARCO → TapChg → SBO) you need to indicate if the attribute supports activation time.

� For some attributes of the Enum BasicType , you need to select from a list of existing Type values. For example: LDevice → SEMSTA1 → Beh → stVal) .

In these cases, select a Type value, and click OK.

4 After the new data attribute appears in the data attribute table, Save your edits.

IEC61850 Server

80 NHA31369 07/2015

Working with a Data Object that includes Sub Data O bjects

The structure of some data objects includes sub data objects (for example, LDevice → MHAI → HPhV). When you add a data object that includes sub data objects, the data model editor displays both a data object editor and a data attribute editor. You can use these editors to add and remove optional data sub objects and data attributes for this kind of data object.

Both the data object editor (see page 76) and the data attribute editor (see page 78) work in the same manner as described above.

IEC61850 Server

NHA31369 07/2015 81

Instantiating Data Objects and Data Attributes

Introduction

Use the Application Settings window to:� Display IEC61850 server data objects and data attributes.� Instantiate data attributes and data objects by assigning an initial value to data attributes.

Before you can use the Application Settings window, you need to first enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module; then create a new server instance (see page 66) for the module.

1 Data table2 Data Object Filter

IEC61850 Server

82 NHA31369 07/2015

NOTE: � Assigning an initial value to a data attribute instantiates both that attribute and the associated

data object. An instantiated data attribute is indicated by the DAI object designation; an instantiated data object is indicated by the DOI object designation (or SDI for sub data objects).

� Attributes with a value set to an empty string are not instantiated by the application. If values for all data attributes of a data object are set to an empty string, the application does not instantiate the data object.

� For data attributes of the functional constraint CF, the initial value remains constant after the configuration is instantiated. For data attributes of other function constraint items, the initialized value is the default value if not included in I/O mapping; otherwise, the functional constraint item is not instantiated.

� For data out flow variables, an assigned initial value takes effect only if a variable is not mapped to PLC memory. If a variable is mapped to PLC memory, its value comes from PLC memory.

Adding Data Objects and Data Attributes

The Application Settings window presents a Data Object Filter and a data table. Use the Data Object Filter to select data objects and data attributes of the IEC61850 server, then drag them onto the data table. The data table displays the data objects and data attributes you add to it in the following nested order:

LDevice → LNode → Data Object → Data Attribute

To add data objects and data attributes to the data table, follow these steps:

Step Action

1 In the Data Object Filter , select a logical device in the LDevice list.The contents of the LNode filter presents logical nodes of the selected logical device.

2 In the LNode list, select a logical node.The contents of the FC list presents functional constraint items of for the selected logical node.

3 In the FC list, select a functional constraint item.The Data Object Filter displays the data objects and nested data attributes associated with the selected functional constraint item.

4 Do one of the following:� Drag a data object or data attribute in the Data Object Filter and drop it onto the data table to

add it to the list.� Click the Add All button to add all of the displayed data objects and data attributes to the list.

5 (Optional) Type in a text Description for each data object added to the list.

6 Repeat steps 1...5 for each data object or data attribute you want to add to the data table.

7 Save your edits to preserve the structure of the data table you created.

IEC61850 Server

NHA31369 07/2015 83

Instantiating Data Attributes and Data Objects

Assigning an initial value to a data attribute instantiates both that attribute and the associated data object. To edit the initial value of a data attribute, follow these steps:

Removing Data Attributes and Data Objects from the Data Table

To remove a data attribute from the data table, select the data attribute, then either:� Click the right mouse button and select Delete , or� Click the Delete key.

If you delete all attributes of a data object, that data object is removed from the data table.

Step Action

1 In the data table, expand the LDevice , LNode , and data object rows until the associated Data Attribute Instance items are visible.

2 In the Initial Value column, enter or select a value for the data attribute.

3 Repeat steps 1 and 2 for each data attribute you want to instantiate.

4 Save your edits.

IEC61850 Server

84 NHA31369 07/2015

Working with Data Sets

Introduction

A data set is a collection of data attributes that can originate with many different logical devices and logical nodes. Data sets can provide an efficient method of viewing and transferring data. The IEC61850 server can include up to 100 data sets, and up to 256 basic type data attributes.

Use the Data Set window to: � Create a new data set.� View the list of existing data sets. � Edit the contents of a new or existing data set by adding data attributes to, or removing data

attributes from the data set collection.� Remove a data set from the IEC61850 server.

Before you can use the Data Set window, you need to first enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module; then create a new server instance (see page 66) for the module.

After you create a data set, you can add it to GOOSE control blocks (see page 92) and also to Report control blocks (see page 87).

1 Data set list2 Data Set description3 FCD/FCDA table4 Data Object Filter

IEC61850 Server

NHA31369 07/2015 85

NOTE: Schneider Electric recommends that:� When you add a stVal or cVal attribute, also add its companion q (quality) data attribute. The q

attribute contains valuable data information for your application.� You do not add a t attribute to a GOOSE data set. To do so is not an efficient use of control block

space.

Creating a Data Set

To create a new data set, follow these steps:

Step Action

1 In the General → IEC61850 Server → Data Model window, create the data model for your module.

2 In the General → IEC61850 Server → Data Set window, in the Data Set list, click the + button.A new data set appears in the data set list, with the default name ‘NewDatasetn’ (where n represents the sequential number of the data set).

3 Do one of the following:� Accept the default data set name.� Double click the default name, then type a new name and press Enter .

4 In the Description area, do one of the following:� Accept the default data set description, which is the reference path to the data set; or� Type in a different description.

5 In the Data Object Filter , use the filtering lists to navigate to the data attribute you want to add to the data set. Make filtering selections for:� LDevice : Select an IEC61850 server logical device.� LNode : Select a logical node associated with the selected logical device.� FC: Select a functional constraint.

The data attribute list – located below the filtering lists – presents the data attributes that satisfy the selected filtering criteria.

6 Add data attributes to the data set in one of the following ways:� Drag a data object node from the data attribute list and drop it on the FCDA table.

NOTE: When you add a data object, all of its data attributes are also added, even though they are not visible in the list.

� Drag a single data attribute from the data attribute list and drop it on the FCDA table. Only the selected data attribute is added to the data set.

The FCDA table displays the data set in nested groups, as follows: LDevice → LNode → Data Object → Data Attribute

7 Repeat steps 3 and 4, above, until all data attributes are added to the data set.

8 Save your edits.

IEC61850 Server

86 NHA31369 07/2015

Editing an Existing Data Set

To edit an existing data set, follow these steps:

Viewing Data Set Contents

To display the data attributes assigned to a data set, select the data set in the Data Set list. The data attributes appear in the FCDA/FDC table.

Removing a Data Set from the IEC61850 Server

To remove a data set from the IEC61850 Server, follow these steps:

Step Action

1 In the Data Set list, select an existing data set.The data attributes of the selected data set appear in the data set list.

2 To add data attributes, follow steps 3 to 5 in Creating a Data Set (see page 85) (above).

3 To remove data attributes, select one or more data attributes in the FCDA table, right click, then select Delete from the context menu.

4 Save your edits.

Step Action

1 In the Data Set list, select an existing data set.The data attributes of the selected data set appear in the data set list.

2 Click the – button.The data set is removed from the list.

3 Save your edits.

IEC61850 Server

NHA31369 07/2015 87

Configuring Report Control Blocks

Introduction

Use report control blocks to transmit the information contained in data sets. Configure each report control block to specify how the IEC61850 server that resides in the 140 NOP 850 00 module transmits event data to IEC61850 clients.

There are two kinds of report control blocks:� Buffered (BRCB): Internal events (triggered by data-change and quality-change) cause either:

� the immediate transmission of a report, or� the buffering of a report (within practical limitations) for later transmission.

A report is buffered so that data object values are not lost due to transport flow control constraints or a connection interruption. A buffered report control block provides sequence-of-events (SOE) functionality.The buffer size of a buffered report control block is fixed at 16 bytes for each report control block instance.

� Unbuffered (URCB): Internal events (triggered by data-change and quality-change) cause the immediate transmission of a report on a "best effort" basis. If no association exists, or if the transport data flow is not fast enough to support the transmission, report data may be lost.

The IEC61850 server in the 140 NOP 850 00 module supports:� Up to 64 buffered or unbuffered report control block instances within a single IED.� Up to 8 instances of a single buffered control block, which can be transmitted to 8 clients, upon

the occurrence of possibly different triggering conditions.

Before you can use the Report Control Block window, you first need to:� Enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module.� Create a new server instance (see page 66) for the module.� Create a data set incorporating data attributes from this 140 NOP 850 00 module (see page 85)

or from an ERT module (see page 96).

NOTE: The 140 NOP 850 00 Ethernet module stores report control blocks in the LDevice System, at the LNode LLN0.

IEC61850 Server

88 NHA31369 07/2015

1 Report Control list2 Report Control settings

IEC61850 Server

NHA31369 07/2015 89

Report Control Settings

Every report control block presents the following configuration settings:

Setting Description

Identification area:

Buffered Do one of the following:� Select this to enable buffering for this report control block.� De-select this to disable buffering.

This setting is disabled by default.

Description The editable description of the report control block, from 0...50 characters long.

Data Set Select the data set to include in the report control block.

Report Id A string value, 0...129 characters long, used as the source identifier in report control block transmissions.

Configuration Revision The read-only revision number for the report control block. The initial value is 10000.

NOTE: This setting is increased in increments of 10000 each time one of the following changes occurs:� The identity of the data set associated with this control block

changes.� Content of the associated data set changes.

Parameters area:

Buffer Time (ms) The time interval in milliseconds for the buffering of internal notifications caused by data-change (dchg) or quality-change (qchg) by the BRCB for inclusion into a single report.

Integrity Period Enter a value, in milliseconds, to periodically force the transmission of all values in the data set. Using this setting synchronizes data values in all clients that receive the transmission.

Indexed Do one of the following:� Select this to enable indexing of this report control block.� De-select this to disable indexing.

This setting is enabled by default.

NOTE: � The Indexed setting applies only to Edition 2.0 of the IEC61850

protocol. It does not apply to Edition 1.0.� The module supports up to 8 instances of indexed report control

blocks.

Index Number Select an index number for the report control block.

Trigger Conditions area:

Data-change Select this to transmit a report upon a change in value for an item in the data set.

IEC61850 Server

90 NHA31369 07/2015

Quality-change Select this to transmit a report upon a change in quality for any item in the data set.

Period Select this to transmit a report of all data set values upon expiration of the Integrity Period .

NOTE: Schneider Electric recommends that you do not use the integrity reporting function in a Hot Standby system, because the standby 140 NOP 850 00 module does not generate this report.

General-interrogation Select this to transmit a report, in response to a request from a client, containing values for all data items in the data set.

NOTE: � All buffered events are transmitted before the general-interrogation

report is transmitted.� If the IEC61850 server receives a request for a general

interrogation report while executing a previous general interrogation request, execution of the current request stops. The server instead begins to execute the new general interrogation request.

Report Content area:

Sequence-number Select this to include an auto-generated transmission sequence number to the report control block transmission. This lets the client determine if all transmissions have been received.

Report-timestamp Select this to include a time stamp in the report control block transmission.

Reason for inclusion The reason for sending this report, for example:� data change� data quality change� general interrogation� periodic transmission

Dataset name Select this to include the configured data set name in the report control block transmission.

Data reference The name of the data set referenced in the report.

Buffer overflow Select either:� Yes: to enable the buffer overflow. (default)� No: to disable it.

Enabled only if Buffered is selected.

Entry Id Report entry identifier. Entry Id(0) is reserved for the client. If the client sets Entry Id to (0), the server reports all historic events in its buffer.Enabled only if Buffered is selected.

Configuration revision Select this to include the Configuration Revision setting of the report control block in the transmission.

Setting Description

IEC61850 Server

NHA31369 07/2015 91

Creating a New Report Control Block

To create a new report control block, follow these steps:

Editing an Existing Report Control Block

To edit an existing report control block, follow these steps:

Removing a Report Control Block

To remove a report control block from the IEC61850 Server, follow these steps:

Step Action

1 In the Report Control list, click the + button.A new report control block appears in list, with the default name report_n (where n represents the sequential number of the control block).

2 Enter values for the Identification , Parameters , Trigger Conditions and Report Content settings. Refer to the description of Report Control Settings (above).

NOTE: To enter a setting value, click Enter or move your cursor and click outside the setting input field.

3 Save your edits.

Step Action

1 In the Report Control list, select an existing control block.The settings for the selected report control block appear in the Identification , Parameters , Trigger Conditions and Report Content areas.

2 Enter values for the Identification , Parameters , Trigger Conditions and Report Content settings. Refer to the section Report Control Settings (above).


3 Save your edits.

Step Action

1 In the Report Control list, select an existing control block.The settings for the selected report control block appear in the Identification , Parameters , Trigger Conditions and Report Content areas.

2 Click the – button.The control block is removed from the list.

3 Save your edits.

IEC61850 Server

92 NHA31369 07/2015

Publishing GOOSE Control Blocks

Introduction

The 140 NOP 850 00 Ethernet module can publish module event data via GOOSE control blocks. Each control block references a data set with data attributes that can describe module status and value information. The module sends GOOSE control blocks in the form of multicast transmissions over a VLAN. Other devices that subscribe to the VLAN receive the transmitted data.

Use the GOOSE Control Block window to:� Create a new GOOSE control block.� View the list of existing GOOSE control blocks.� Edit the contents of a new or existing GOOSE control block.� Remove a GOOSE control block from the IEC61850 server.

Before you can use the GOOSE Control Block window, you first need to:� Enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module.� Create a new server instance (see page 66) for the module.� Create the data set (see page 85) you want to add to, and be published by, a GOOSE control

block.

NOTE: The 140 NOP 850 00 Ethernet module stores GOOSE control blocks in the LDevice System, at the LNode LLN0.

IEC61850 Server

NHA31369 07/2015 93

1 GOOSE Control list 2 GOOSE Control settings

GOOSE Control Settings

NOTE: When publishing GOOSE transmissions:� You can use the GooseSimulation element of the MODULE_STATE (see page 122) DDT to

publish either normal (0) or simulated (1) GOOSE transmissions.� The relative diagnostic information of each GOOSE transmission is collected in a dedicated

DDT instance.

IEC61850 Server

94 NHA31369 07/2015

Every GOOSE control block includes the following settings:

Setting Description

Parameters area:

Configuration Revision The read-only revision number for the GOOSE control block. The initial value is 10000.

NOTE: This setting is increased in increments of 10000 each time one of the following changes occurs:� The identity of the data set associated with this control block changes.� Content of the associated data set changes.

Description The editable description of the GOOSE control block, up to 50 characters long.

GOOSE ID An editable string value, from 1...128 characters long, used as the source identifier in GOOSE message transmissions. The default value is the reference path of this GOOSE control block, in the form of: IED name / logical device name / logical node name.GoID

Data Set Select the data set (see page 84) to include in the GOOSE control block.

NOTE: Data set size cannot exceed 1496 bytes.

Publishing area:

MAC Address1 Enter the multicast address for GOOSE filtering. Valid values include:01-0C-CD-01-00-01 ... 01-0C-CD-01-01-FF

VLAN ID1 Enter the VLAN ID for the GOOSE control block. A 3-character value that can include 0...9, and A...F. GOOSE subscribers use this to filter received messages based on VLAN identity. Default = 000.

NOTE: A setting of 000 indicates no VLAN ID is required. Switching equipment drops the VLAN tag when VLAN ID is set to 000.

APP ID1 Enter the APP ID for the GOOSE control block. A 4-character value that can include 0...9, and A...F. GOOSE subscribers use this to filter received messages based on the application configuration. Default = 0.

VLAN Priority1 Select the priority, 0...7, to be applied to VLAN transmissions of the GOOSE control block. Ethernet switches that manage the VLAN use this value to prioritize messages in their packet transmission queues.

Min. Time (ms)1 Enter the minimum time, from 20...1000 ms, between VLAN transmissions containing this GOOSE control block. Min. Time needs to be less than Max. Time.

Max. Time (ms)1 Enter the maximum time, from 20...1000 ms, between VLAN transmissions containing this GOOSE control block. Max. Time needs to be greater than Min. Time.

1. This setting is enabled only if GOOSE Publishing is selected. Otherwise, it is disabled and contains no value.

IEC61850 Server

NHA31369 07/2015 95

Creating a New GOOSE Control Block

To create a new GOOSE control block, follow these steps:

Editing an Existing GOOSE Control Block

To edit an existing GOOSE control block, follow these steps:

Removing a GOOSE Control Block

To remove a GOOSE control block from the IEC61850 Server follow these steps:

Step Action

1 In the GOOSE Control list, click the + button.A new GOOSE control block appears in list, with the default name goosectrln (where n represents the sequential number of the control block).

2 Enter values for the Parameters and Publishing settings. Refer to the section GOOSE Control Settings (see page 93) (above).


3 Save the new GOOSE control block.

Step Action

1 In the GOOSE Control list, select an existing control block.The settings for the selected GOOSE control block appear in the Parameters and Publishing areas.

2 Enter values for the Parameters and Publishing settings. Refer to the section GOOSE Control Settings (see page 93) (above).


3 Save your edits.

Step Action

1 In the GOOSE Control list, select an existing control block.The settings for the selected GOOSE control block appear in the Parameters and Publishing areas.

2 Click the – button.The control block is removed from the list.

3 Save your edits.

IEC61850 Server

96 NHA31369 07/2015

Working with ERT Data Sets

Introduction

You can use the Modicon IEC61850 Configuration Tool to create a data set in the IEC61850 server of the 140 NOP 850 00 module that links to data produced by an ERT module. After the ERT data set is created, you can use it to populate the data fields of a report control block.

Use the ERT Data Set window to:� View the list of existing ERT data sets.� Create a new ERT data set.� Edit the contents of a new or existing ERT data set by:

� Adding data attributes to, or removing data attributes from the data set collection.� Assigning an Event Id value to each data attribute in the collection.

� Remove an ERT data set from the IEC61850 server.

Before you can use the ERT Data Set window, you need to:� Enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module; then� Create a new server instance (see page 66) for the module

The ERT Data Set window:

1 Data Set list2 ERT Data Set description3 FCDA table4 Data Object Filter

IEC61850 Server

NHA31369 07/2015 97

Creating an ERT Data Set

To create a new ERT data set, follow these steps:

After you map data attributes to PLC variables, two DDT instances are automatically created in your application:� An IED_RPT DDT to manage diagnostic report information (see page 135).� An IED_EVT DDT to identify the channel the PLC uses to transmit event information

(see page 136).

Step Action

1 In the Data Set list, click the + button.A new data set appears in the data set list, with the default name ‘dataset_n’ (where n represents the sequential number of the data set).

2 Do one of the following:� Accept the default data set name.� Double click the default name, then type a new name and press Enter .

3 In the Description area, do one of the following:� Accept the default data set description, which is the reference path to the data set; or� Type in a different description.

4 In the Data Object Filter , use the filtering lists to navigate to the data attribute you want to add to the data set. Make filtering selections for:� LDevice : Select an IEC61850 server logical device.� LNode : Select a logical node associated with the selected logical device.� FC: Select a functional constraint.

The data attribute list – located below the filtering lists – presents the data attributes that satisfy the selected filtering criteria.

5 To add data attributes to the data set, Drag a data object node from the data attribute list and drop it on the FCDA table.The FCDA table displays the data set in nested groups, as follows: LDevice → LNode → Data Object → Data Attribute

6 Input an Event Id for the data attribute you added to the data set.

NOTE: � For a Quantum ERT, Event Id is the channel number (1...32).� For Mx80 ERT, the Event Id is the channel number (0...15).� For an Mx80 CRA, the Event ID is generated by Unity Pro.

7 Repeat steps 3, 4 and 5 until all data attributes are added to the data set.

8 Save your edits.

IEC61850 Server

98 NHA31369 07/2015

Editing an Existing ERT Data Set

To edit an existing ERT data set, follow these steps:

Viewing Data Set Contents

To display the data references assigned to an ERT data set, select the ERT data set in the Data Set list. The data attributes appear in the FCDA table.

Removing a Data Set from the IEC61850 Server

To remove a data set from the IEC61850 Server, follow these steps:

Step Action

1 In the Data Set list, select an existing ERT data set.The data references of the selected data set appear in the FCDA table.

2 To add data references, follow steps 3 to 5 in Creating an ERT Data Set (above).

3 To remove data references, select one or more data reference items in the FCDA table, right click, then select Delete from the context menu.

4 Save your edits.

Step Action

1 Confirm that the data set you want to remove has not been added to the data model (see page 72).

2 In the Data Set list, select an existing ERT data set.The data references of the selected data set appear in the FCDA table.

3 Click the – button.The ERT data set is removed from the list.

4 Save your edits.

IEC61850 Server

NHA31369 07/2015 99

Subscribing to GOOSE Control Blocks from External R eferences

Introduction

You can configure the IEC61850 server in the 140 NOP 850 00 module to subscribe to GOOSE published by external IEDs.

The method of subscribing to remote GOOSE data is different for the IEC61850 client and server:� For the IEC61850 server, use the External Reference window to map the data attributes of a

remote IED to the data attributes of the local IED. The data attributes of the local IED are updated with changes when the server receives the GOOSE published by remote IED.

� For the IEC61850 client, use the Control Block tab of the I/O Mapping window to subscribe to GOOSE data configured in a remote IED. You need to map the related data attributes in I/O mapping so that you can locate the data attributes that are updated after receiving data.

In the External Reference window, the 140 NOP 850 00 module adds the data attributes (DAs) subscribed from the external IED to PLC memory, then updates the values of the subscribed DAs as they change. The 140 NOP 850 00 module performs this update when operating in either normal or simulation mode.

For GOOSE subscriptions in simulation mode, it is possible to control LPHD.sim.stVal to receive or reject GOOSE data attribute for the server. Note that the client does not support simulation mode and will ignore all GOOSE that are marked as simulation.

When the 140 NOP 850 00 module receives a GOOSE update, the relative diagnostic information is collected with dedicated DDT instances of IED_GOOSE.

LGOS is not supported automatically when subscribing to GOOSE, but it is possible to manage LGOS in your PLC application using GOOSE diagnostic information.

Use the External Reference window to:� Create mapping items that associate data attributes of the local 140 NOP 850 00 module to

data attributes contained in GOOSE messages published by an external module.� Edit mapping items you previously created. � Remove mapping items you previously created.

Before you can use the External Reference window, you first need to:� Enable the IEC61850 server (see page 46) resident in the 140 NOP 850 00 module.� Create a new server instance (see page 66) for the module.

IEC61850 Server

100 NHA31369 07/2015

1 External GOOSE data reference 2 Import SCD / ICD button 3 Delete remote IED button4 Mapping table 5 Target drop area for the creation of a new mapping item6 Internal Data Objects filter (for the 140 NOP 850 00 module)7 External mapped data item8 Internal mapped data item

Mapping Internal Data Attributes to GOOSE External References

Follow these steps to map the internal data attributes (that you want to receive and store external data) to the external data attributes in a GOOSE transmission:

Step Action

1 In the External panel, click the Import SCD / CID button.The Importing external IED dialog appears.

2 In the Importing external IED dialog, click the ellipsis button.The Open dialog displays.

3 In the Open dialog, navigate to and select an SCD or CID file; then click Open .

4 In the Select IED to Import list, select the IED that publishes the data you want to import, and click OK.

NOTE: Because all imported IEDs are managed in the same space, each imported IED needs to have a unique name. The software will not import IEDs with same name as previously imported IED.

5 In the GOOSE list, select the control block that contains the data you want to import.The external reference list – located below the External filtering selections – presents the external references that satisfy the selected filtering criteria.

IEC61850 Server

NHA31369 07/2015 101

Editing Mapping Items

After a mapping item is created – by adding both an internal data attribute and an external reference – you can edit the item by replacing the internal data attribute.

To edit the internal data attribute, follow these steps:

Deleting a Mapping Item

To delete an item from the mapping list, select the item in Mapping panel, then click the right mouse button, and select Delete .

6 In the External panel, select a data attribute from the external references list, then drag it to the area marked Drag external data object here to create mapping . A row is added to the Mapping table, and the data attribute you added appears on the left side of the newly added mapping item. the right box of the data item in the Mapping table to which you want the external reference mapped.Repeat this step as many times as there are mapping items to populate.

7 In the Internal data panel, use the filtering lists to select the data attribute you want to add to PLC memory. Filtering items include:� IED: The read-only name of the module.� LDevice : Select an IEC61850 server logical device.� LNode : Select a logical node associated with the selected logical device.� FC: Select a functional constraint.

The data attribute list – located below the filtering selections – presents the data attributes that satisfy the selected filtering criteria.

8 Use your cursor to select a data attribute in the Internal Data Objects data attribute list, and drag it to the right box of the data item in the Mapping table to which you want the internal data item mapped.

NOTE: When you select an internal data attribute, it needs to be of the same data type as the data item to which it is mapped. If you attempt to map data items of different types, a message box opens indicating the attempted mapping is not permitted.

Repeat this step as many times as there are mapping items to populate.

9 When you finish adding mapping items, Save your edits.

Step Action

Step Action

1 In the Internal Data Objects filter, navigate to the data attribute you want to add.

2 Select the replacement internal data item, and drag it to the right box of a mapping item. The new internal data item overwrites the old one.

IEC61850 Server

102 NHA31369 07/2015

NHA31369 07/2015 103

Quantum IEC61850

IEC61850 Client

NHA31369 07/2015

Configuring the IEC61850 Client

Chapter 5Configuring the IEC61850 Client

Client Settings

Introduction

Use the IEC61850 Client window to import IEDs into, and delete IEDs from, your project. After you add an IED to your project, you can:� View basic information (including the IP address) and the data structure describing the IED.� Use the I/O Mapping window to map data objects and data attributes from the IED server to

PLC memory addresses.

To use the IEC61850 Client window, you need to enable the IEC61850 client (see page 46) resident in the 140 NOP 850 00 module.

NOTE: The IEC61850 Client can include up to 10000 data attributes.

IEC61850 Client

104 NHA31369 07/2015

Importing an IED

To import an IED into your project, follow these steps:

Displaying IED Information

After importing an IED, you can use the IEC61850 Client window to view basic information and the data structure of the IED.

Basic information for the imported IED server includes the following read-only settings:

Step Action

1 In the IEC61850 Client window, click the Import IEDs button . The Import IED dialog opens.

2 In the Select CID/SCD file area, do the following:1. Click the browse button. An Open dialog opens.2. Navigate to and select the CID or SCD file that contains the IEDs you want to add.3. Click OK to close the dialog.

The Select IED to Import list populates.

3 Select one or more IEDs from the Select IED to Import list.

4 Click OK to close the Import IED dialog. Each selected IED is displayed in its own tile in the IEC61850 Client window, with the IED name appearing in the tile header.

5 Save your edits.

Setting Description

Polling Cycle (ms) The configurable frequency for updating IED data. Default = 1000 ms.

Originator Category The basis for changing values and IEC61850 control services:� Bay Control: Control operation issued from an operator using a client located

at bay level.� Station Control: Control operation issued from an operator using a client

located at station level.� Remote Control: Control operation from a remote operator outside the

substation (for example network control center).� Automatic Bay: Control operation issued from an automatic function at bay

level.� Automatic Station: Control operation issued from an automatic function at

station level.� Automatic Remote: Control operation issued from a automatic function outside

of the substation.� Maintenance: Control operation issued from a maintenance/service tool.� Process: Status change occurred without control action (for example external

trip of a circuit breaker or detected failure inside the breaker).

Originator Identification The configurable address of the originator that caused a change of a controllable value. If NULL, the originator of a particular action is not known or is not reported.

IEC61850 Client

NHA31369 07/2015 105

NOTE: � If the Polling Cycle in memory is zero, the polling cycle configured for the IED is used as the

default.� When the Polling Cycle setting is less than the actual polling period during execution, the

140 NOP 850 00 module continues to poll using the real execution time.

Deleting IEDs

To delete an IED that has previously been imported into the IEC61850 client, follow these steps:

IP A read-only 32-bit IP address assigned to the server in the imported IED, including both network and host components.

SubnetMask A read-only 32-bit value used to mask the network portion of the IP address and reveal the IED server host address.

Gateway The read-only IP address of the router that is the access point to a remote network.

Description A read-only description of the IED.

Setting Description

Step Action

1 Click the Delete IED button located in the upper right corner of each IED tile,The Confirm dialog opens asking you if you are sure you want to delete the IED.

2 Click Yes. The IED is removed from the collection.

3 Save your edits.

IEC61850 Client

106 NHA31369 07/2015

NHA31369 07/2015 107

Quantum IEC61850

I/O Mapping

NHA31369 07/2015

Working with IEC61850 Data Objects

Chapter 6Working with IEC61850 Data Objects

Overview

This chapter shows you how to map data attributes to PLC memory using the I/O Mapping window; then shows you how to use the new data objects in your program logic.



Topic Page

Mapping Data Attributes to PLC Memory 108

Working with IEC61850 Data Objects 115

PLC State Management 118

IEC61850 Memory Arrangement 119

DDT Data Structures 120

I/O Mapping

108 NHA31369 07/2015

Mapping Data Attributes to PLC Memory

Introduction

You can use the I/O Mapping window to link IEC61850 client and IEC61850 server data items to memory locations in the PLC. You can access data items by navigating through the IEC61850 protocol data structure:

IED → LDevice → LNode → Functional Constraint (FC)

The I/O Mapping window supports the following functional constraints:

There are three groups of data items:� System items contain the operating status of a module. System data items – for both the client

and server – are automatically mapped to the PLC. You cannot add items to, or delete items from, the system data table is fixed.

� Parameter items can originate with either the client or the server. No parameters are mapped to the PLC by default. You can add both client and server data objects and data attributes to the mapping table.

� Control block items contain data provided by the following control blocks and services:� Unbuffered report control blocks (RP)� Buffered report control blocks (BR)� GOOSE control blocks (GO)� Process control service command (CO)� Polling group service

NOTE: Polling group service data items are not displayed by the Modicon IEC61850 Configuration Tool. Instead, they are included in the data structure created by Unity Pro when you click the Update application button in the Configuration tab of the 140 NOP 850 00 module Properties window.

FC Server Client Description

BR – √ Buffered report control block

CF √ √ Configuration value

CO √ √ Process control service command or status

DC – – Description attribute

GO – √ GOOSE report control block

MX √ √ Process measurement value

RP – √ Unbuffered report control block

SP √ √ Process set point to support reading of status

ST √ √ Process status value

√ The FC is supported.– The FC is not supported.

I/O Mapping

NHA31369 07/2015 109

Viewing System Data Items

To view system data items, follow these steps:

The System tab for the IEC61850 client:

1 Client / Server selector buttons2 Data items selector tabs3 Data Object / Data Attribute Filter4 Mapping table

Step Action

1 In the I/O Mapping window, select either:� Server to display data items for the IEC61850 server; or � Client to display data items for the IEC61850 client.

2 Click the System tab.The mapping table displays system data items for the module in its role as server or client.

I/O Mapping

110 NHA31369 07/2015

Adding Parameter Data Items

The Parameters tab for the IEC61850 client:

1 Client / Server selector buttons 2 Data items selector tabs3 Data Object / Data Attribute Filter4 Mapping table

I/O Mapping

NHA31369 07/2015 111

To add parameter data items, follow these steps:

When you finish configuring the 140 NOP 850 00 module, close the Modicon IEC61850 Configuration Tool, then click Update application in the Configuration tab of the module Properties window. Unity Pro creates DDT variables for each data attribute (see page 115) and displays each new DDT variable in the Unity Pro Data Editor .

Step Action

1 In the I/O Mapping window, select either:� Server to display data items for the IEC61850 server; or � Client to display data items for the IEC61850 client.

2 Click the Parameters tab.The Data Object Filter presents data objects associated with the selected tab.

3 In the Data Object Filter , make the following selections:1. In the IED list, select an IED.

NOTE: If you selected Server in step 1, the server IED is pre-selected.

2. In the LDevice list, select a device. 3. In the LNode list, select the logical node object that contains the data object (attributes) you

want to map to an address in the PLC.4. In the FC list, select the functional constraint for the data attributes you want to map to an

address in the PLC.

The Data Object Filter displays the associated data objects and data attributes.

4 Select a data object or data attribute in the Data Object Filter , and then drag it to the mapping table in the Parameters tab. If you selected a:� Data object: the data object and all its associated data attributes are added to the table.� Data attribute: only the selected data attribute is added to the table.

NOTE: The data object order of data mapping depends on the structure defined in the data model (see page 72).

5 If you selected Client in step 1, expand the mapping table to display each data attribute, then edit the Polling Group setting for the attribute. Settings include:� Not Poll: Indicates client can update data via control block (default)� Group-1� Group-2� Group-3� Group-4� Group-5

6 Repeat steps 2...5 for each data object or data attribute you want to add to map to a located memory address in the PLC.

7 Save your edits.

I/O Mapping

112 NHA31369 07/2015

Adding Control Block and Service Data Items

To add data attributes from remote IEDs to the 140 NOP 850 00 module in its role as IEC61850 client, follow these steps:

Step Action

1 In the I/O Mapping window, click Client . The Data Object Filter presents the IEDs associated with the module in its role as IEC61850 client.

2 In the I/O Mapping window, click Control Block . The Data Object Filter presents data objects associated with the selected tab.

3 In the Data Object Filter , drill down to the data attributes you want to add, by making the following selections:1. Select an IED.2. Select an LDevice object. 3. Select an LNode object.4. Select an FC object. Depending on the specific IED content, you can select:

� BR: Buffered report control block� RP: Unbuffered report control block� CO: Process control value service� GO: GOOSE control block

The Data Object Filter displays the associated data objects and data attributes.

4 Select a item in the Data Object Filter , and then drag it to the mapping table in the selected tab.

5 Repeat steps 2...4 for each data item you want to add to map to a located memory address in the PLC.

6 Save your edits.

I/O Mapping

NHA31369 07/2015 113

A sample mapping table of the Control Block tab for the IEC61850 client:

1 Unbuffered report control block (RP)2 Buffered report control block (BR)3 GOOSE report control block (GO)4 Process control value service block (CO)

Each block you add displays the following columns:� Element :

The name of the control block, up to thirteen ASCII characters. If the original name exceeds the maximum length, a dialog asks you to edit and shorten this value.

� Variable :The concatenation of the Element value and the %MW address.

I/O Mapping

114 NHA31369 07/2015

� Type :The type of mapping item: a control block or elementary variable.

� %MW Address :The %MW address of the mapped item in the PLC.

� IED:The name of the IED to which the mapped item belongs.

� Reference Path :The IEC61850 protocol reference path to the control block or data object.

� Array :A check mark indicates this element is an array.

� Length :For array elements, the number of items in the array.

When you finish configuring the 140 NOP 850 00 module, close the Modicon IEC61850 Configuration Tool, then click Update application in the Configuration tab of the module Properties window. Unity Pro creates DDT variables for each data attribute (see page 115) and displays each new DDT variable in the Unity Pro Data Editor .

Removing Data Attributes from the Mapping Table

To remove one or more data attributes from a mapping table, follow these steps:

Step Action

1 In the mapping table, select an item you want to delete.

2 Click the right mouse button to open a context menu.

3 Click Delete to remove the selected data items from the mapping table.

4 Repeat steps 1...3 for each item you want to delete.

5 Save your edits.

I/O Mapping

NHA31369 07/2015 115

Working with IEC61850 Data Objects

Introduction

After you select data items in the I/O Mapping window, click Update application . Unity Pro creates the following data objects for each 140 NOP 850 00 module in your project:� A DDT located variable structure for each IEC61850 data attribute added in the I/O Mapping

window that references DDT located variables, which can include:� {Module_name}_CLIENT_STATE� {Module_name}_MODULE_STATE� {Module_name}_SERVER_STATE

� A Device DDT unlocated variable structure that follows the IEC61850 data model:Module → IED → LD → LN → DO → <SDO> → DA

Each DDT located variable is assigned a %MW address and stores the value of a data attribute.

The Device DDT structure includes an unlocated variable for each data attribute, which references a located variable in the DDT structure.

NOTE: Although each new located variable has an assigned %MW address, Schneider Electric recommends that you do not use located variables in your program logic to access data values directly. The name assigned to each located variable is intended only to be unique, and may not provide a clear description of the path to the data attribute. Thus, the identity of a located variable may be difficult to identify in program logic. Instead, it is recommended that you use the Device DDT variables to access variable data and structure.

You can access the data stored in located variables using the dot addressing notation of the IEC61850 data model, for example: “Module.IED.LDevice.LNode.DO.DA”.

I/O Mapping

116 NHA31369 07/2015

Working with Device DDT Variables

Use the newly created Device DDT variables to access project data. An example of a new Device DDT instance presenting the module data structure appears below:

As depicted above, the Type column displays values as follows: � The top-most node displays the module name.� Intermediate nodes display the module name plus a unique hash number.� Leaf (or end) nodes are of the Reference data type, and point to the located variable identified

in the Value column.

Because of the ease of navigating the module data structure, Schneider Electric recommends that you use the Device DDT variables in program logic to indirectly access data values.

I/O Mapping

NHA31369 07/2015 117

Working with Located Variables

Unity Pro creates a located variable for each data attribute mapped in the I/O Mapping window. Click the Variables tab of the Data Editor to view the located address of each variable:

The IEC61850 data model and Unity Pro support different collections of data types (see page 23). When Unity Pro creates new located variables from IEC61850 data attributes, it assigns each new variable a data type supported by Unity Pro.

NOTE: As noted above, although each new located variable has an assigned %MW address, Schneider Electric recommends that you do not use located variables in your program logic to access data values directly. Instead, it is recommended that you use the Device DDT variables to access module data.

I/O Mapping

118 NHA31369 07/2015

PLC State Management

IEC61850 Server

When the PLC stops, the quality of each data object is set as Invalid. In this case, the 140 NOP 850 00 module continues to detect events, but rejects client requests with the Add Cause detected error code (see page 125) of 1 (not-supported) for DOns or SBOns objects.

IEC61850 Client

When the PLC stops or starts, the 140 NOP 850 00 module updates data to the CPU and continues to send control commands to the remote IED, when triggered.

IEC61850 Roles and Functions

Depending on the state of the PLC, the following polling functions are supported:

IEC61850Role/Function

PLC State

Run Stop

Server:

� Buffered and unbuffered reporting X X

� GOOSE X X

� Control commands X –

Client:

� Buffered and unbuffered reporting X X

� GOOSE X X

� Control commands X X

X: Supported–: Not supported

I/O Mapping

NHA31369 07/2015 119

IEC61850 Memory Arrangement

Introduction

The 140 NOP 850 00 module includes two kinds of memory to access:� implicit memory� explicit memory

In the implicit in and out memory area, the first sixteen %MW words are reserved by the module, and are beyond the scope of the DDT.

Implicit Data In

Monitor points, diagnostic information and special information are saved in this area:

Implicit Data Out

The data out buffer:

Explicit Data In

Monitor points, diagnostic information and special information are saved in this area:

Explicit Data Out

This area supports control points or report/GOOSE operations:

Role Implicit In Direction Number of %MW Words Comment

Server <IED>_SERVER_STATE 20 + ReportDiag IED -> CPU, synch with PLC cycle

Client <IED>_CLIENT_STATE 20 IED -> CPU, synch with PLC cycle


Server MODULE_STATE 20 CPU -> IED, synch with PLC cycle

Monitor points 1980 CPU -> IED, synch with PLC cycle


Server Control points 2000 IED -> CPU, 2000 for server only

Client Monitor points (status) 2000 IED -> CPU, 2000 for client only


Client Control points and control block (Report CB, GOOSE CB, Poll Control)

1000 CPU -> IED

I/O Mapping

120 NHA31369 07/2015

DDT Data Structures

Introduction

If you enable the IEC61850 server, enable the client, and create one or more report and GOOSE control blocks, Unity Pro adds the following DDT data structures to your project:� Server state� Client state� Module state� Buffered report control blocks� Unbuffered report control blocks� GOOSE control blocks� Control objects� Polling control block

Server State

The {Module_name}_SERVER_STATE DDT presents diagnostic information for the IEC61850 server in the module, the name of which is the prefix of the DDT:

Element Type Description

Active BOOL Server status:� 0 = disabled� 1 = enabled

Health BOOL Server health:� 0 = not operational� 1 = operational

ProtoEd BYTE IEC61850 protocol edition:� 0x10 = 1.0� 0x20 = 2.0

ActiveConn BYTE Number of established server connections: 0...16.

Variable_Rd UDINT Count of read variable requests received by the server.

Variable_Rd_Err UDINT Count of rejected MMS read variable requests.

Variable_Wrt UDINT Count of write variable requests received by the server.

Variable_Wrt_Err UDINT Count of rejected MMS write variable requests.

Reports_Tx UDINT Count of information report messages sent by the server.

Goose_Tx UDINT Count of GOOSE messages transmitted by the server.

Goose_Rx UDINT Count of GOOSE messages received by the server.

Goose_Err UDINT Count of invalid GOOSE messages received by the server.

1. The RptEntity element consists of a number of reports of the IED_RPT data type, each of which is 2 WORDS long.

I/O Mapping

NHA31369 07/2015 121

Client State

The {Module_name}_CLIENT_STATE DDT presents diagnostic information for the IEC61850 client in the module, the name of which is the prefix of the DDT:

ErrorCode DWORD Low word:� 0x0001: invalid configuration� 0x0002: stack init error detected� 0x0004: config init error detected� 0x0010...0x00F0: BP comm error detected� 0x0100: DB binding error detected� 0x1000...0xF000: Report error detected

High word:� 0x1000: Clock not synchronized� 0x2000: Default IP

RptEntity IED_RPT[x] (see page 135)

Report diagnostic information

GooseEntity IED_GOOSE[x] (see page 123)



1. The RptEntity element consists of a number of reports of the IED_RPT data type, each of which is 2 WORDS long.


Active BOOL Client status:� 0 = disabled� 1 = enabled

Health BOOL Client health:� 0 = not operational� 1 = operational

ProtoEd BYTE IEC61850 protocol edition:� 0x10 = 1.0� 0x20 = 2.0

ActiveConn BYTE Number of established server connections: 0...16.

IED_Health UDINT IED connection status:� 0 = disconnected� 1 = connected

NOTE: Each bit represents one IED in the same order as the sequence of IEDs in the SCL file.

Variable_Rd UDINT Count of read variable requests received by the client.

Variable_Rd_Err UDINT Count of rejected MMS read variable requests.

Variable_Wrt UDINT Count of write variable requests received by the client.

Variable_Wrt_Err UDINT Count of rejected MMS write variable requests.

I/O Mapping

122 NHA31369 07/2015

Module State

The {Module_name}_MODULE_STATE DDT presents diagnostic information for the IEC61850 module, the name of which is the prefix of the DDT:

Reports_Rx UDINT Count of information report messages received by the client.

Goose_Rx UDINT Count of GOOSE messages received by the client.

Goose_Err UDINT Count of invalid GOOSE messages received by the client.

ErrorCode DWORD Low word:� 0x0001: invalid configuration� 0x0002: stack init error detected� 0x0004: config init error detected� 0x0100: DB binding error detected� 0x1000: Report ID mismatch detected

High word:� 0x0001...0x00FF: Configuration inconsistent (index of IED in SCL)� 0x1000: Clock not synchronized� 0x2000: Default IP

GooseEntity IED_GOOSE[x] (see page123)




CurEntryID WORD[5] Current entry ID (read-only)

LastEntryID WORD[5] Last entry ID (read-only)

ScanCount DWORD The counter of I/O data scan (read-only)

NOTE: The 140 NOP 850 00 module I/O data scan for reports and GOOSE is not synchronized with the PLC SCAN. ScanCount indicates if the I/O scan is finished. You can use ScanCount to determine if the report/GOOSE data change is detected by module or if a report/GOOSE transmission was lost.

Reserve WORD[4] <Reserved>

ConnectControl DWORD Control register for all connections with remote IED. One bit represents one IED:� 0 = Auto-connect� 1 = Stop connect

ModuleSimulation WORD � 0 = Normal mode� 1 = Simulation mode

Reserve WORD <Reserved for alignment>

I/O Mapping

NHA31369 07/2015 123

GOOSE Diagnostics

The {Module_name}_IED_GOOSE DDT presents GOOSE control block diagnostic information for the IEC61850 module, the name of which is the prefix of the DDT:


Service BYTE � 0 = Publish� 1 = GOOSE subscribe for server� 2 = GOOSE subscribe for client

Status BOOL � True = active� False = not active

NdsCom BOOL The Need Commission attribute has a value of TRUE if the GoCB requires further configuration when:� The attribute DataSet has a value of NULL� The number or size of values being conveyed by the elements in

the DatSet referenced data-set exceeds constraint determined by the SCSM or the implementation.

Simulation BOOL A value of True indicates Sim messages are received and accepted.

LastStNum UDINT The last state number received.

LastSqNum UDINT The last sequence number received.

LastError UINT The last detected error:� 1: MAC not consist with configuration.� 2: AppID not consist with configuration.� 3: GOOSE data set not consist with configuration.� 4: initAddr is missing.� 5: GOOSE not received after Time to Alive expired.� 6: stNum is out of order.� 7: sqNum out of order.� 8: GOOSE ConfRev not consistent with configuration.� 9: Decoding GOOSE data error detected.� 10: Other unknown detected errors.� 11: NdsCom = True� 12: Go Ref is incorrect

Reserve UINT <Reserved>

I/O Mapping

124 NHA31369 07/2015

Buffered Report Control Block

The data structure of the buffered report {Report_name}_REPORT_BRCB of the client function:

Element Type Trigger Definition

Cmd BYTE Dchg Trigger: effective on change

Option BYTE - Option: operation selection. Values include:� 1: set RptEna� 2: set BufTms� 3: set IntgPd� 4: set ResvTms� 5: set TrgOps� 6: set OptFlds� 8: set EntryID� 9: set RptID

NOTE: Execute option value 9 once before enabling the report control block in the server, to receive report information.

� 10: set DataSetNOTE: For set RptID and set DataSet commands, the source is the SCL file, and cannot be set dynamically in PLC memory.

� 11: set GI� 12: set Purge buffer� 101: get RptEna� 102: get BufTms� 103: get IntgPd� 104: get ResvTms� 105: get TrgOps� 106: get OptFlds� 108: get EntryID� 120: get ConfRev � 121: get SgNum

Index BYTE - Buffer index number: 1...99

AutoEna BYTE - How is report enabled?� 0 = Enable on demand� 1 = Auto enable

NOTE: Auto-enable is recommended so the report is enabled in case of Hot Standby switchover.

I/O Mapping

NHA31369 07/2015 125

AddCause Detected Error Codes

The following is a list of report and control object detected AddCause error codes:

Attribute DWORD - Common area for read/write of attribute, depending on the selected Option:� BufTms DWORD� IntgPd DWORD� ResvTms DWORD� ConfRev DWORD� TrgOps low WORD of attribute� OptFlds low WORD of attribute� SgNum low WORD of attribute� RptEna low WORD (bit 0) of attribute� GI low WORD (bit 0) of attribute� PurgeBuf low WORD (bit 0) of attribute

Entry_ID WORD[4] - Entry ID reported in the last response.

NOTE: Supported only by buffered report control blocks (BRCB).

RptStatus WORD - � low byte: index of report control block (1...99)� high byte:

� bit 0 = ConfRev change� bit 1 = buffer overflow

Status WORD - Status of command execution:� low byte: same as command trigger� high byte:

� bits 6..7: 1 = OK; 2 = Error detected� bits 0...5: Detected Error Code (see page 125)


Code Short Description Explanation of IEC61850-7-2

1 Not-supported Not-supported

2 Blocked-by-switching-hierarchy Not successful, because one of the downstream Loc switches like in CSWI has the value TRUE.

3 Select-failed Canceled due to an unsuccessful selection (select service).

4 Invalid-position Control action is aborted due to invalid switch position (Pos in XCBR or XSWI).

5 Position-reached Switch is already in the intended position (Pos in XCBR or XSWI).

6 Parameter-change-in-execution Control action is blocked due to running parameter change.

7 Step-limit Control action is blocked because tap changer has reached the limit EndPosR or EndPosL in YLTC).

I/O Mapping

126 NHA31369 07/2015

8 Blocked-by-Mode Control action is blocked because the LN (CSWI or XCBR/XSWI)is in a mode (Mod) which doesn t allow any switching.

9 Blocked-by-process Control action is blocked due to some external event at process level that prevents a successful operation for example blocking indication (EEHealth in XCBR or XSWI).

10 Blocked-by-interlocking Control action is blocked due to interlocking of switching devices (in CILO attribute EnaOpn.stVal= FALSE or EnaCls.stVal= FALSE .

11 Blocked-by-synchrocheck Control action with synchrocheck is aborted due to exceed of time limit and missing synchronism condition.

12 Command-already-in-execution Control select or cancel service is rejected because control action is already running.

13 Blocked-by-health Control action is blocked due to some internal event that prevents a successful operation (Health).

14 1-of-n-control Control action is blocked because another control action in a domain (for example substation) is already running (in any XCBR or XSWI of that domain the DPC.stSeld= TRUE).

15 Abortion-by-cancel Control action is aborted due to cancel service.

16 Time-limit-over Control action is terminated due to exceed of some time limit.

17 Abortion-by-trip Control action is aborted due to a trip (PTRC with ACT.general = TRUE).

18 Object-not-selected Control action is rejected because control object was not selected.

19 Object-already-selected Select action is not executed because the addressed object is already selected.

20 No-access-authority Control action is blocked due to lack of access authority.

21 Ended-with-overshoot Control action executed but the end position has overshoot.

22 Abortion-due-to-deviation Control action is aborted due to deviation between the command value and the measured value.

23 Abortion-by-communication-loss Control action is aborted due to the loss of connection with the client that issued the control.

24 Blocked-by-command Control action is blocked due to the data attribute CmdBlk.stVal is TRUE.

25 None Command not successful due to Unknown causes.

26 Inconsistent-parameters The parameters between successive control services are not consistent for example the ctlNum of Select and Operate service are different.

27 Locked-by-other-client Another client has already reserved the object.

60 Auto-enable did not succeed –

61 Disconnected from remote IED –

62 Polling did not succeed –

63 Input parameter error detected –

Code Short Description Explanation of IEC61850-7-2

I/O Mapping

NHA31369 07/2015 127

Unbuffered Report Control Block

The data structure of the unbufferred report {Report_name}_REPORT_URCB of the client function:



Option BYTE - Option: operation selection. Values include:� 1: set RptEna� 2: set BufTms� 3: set IntgPd� 5: set TrgOps� 6: set OptFlds� 7: set ResvUrcb� 8: set EntryID� 9: set RptID� 10: set DataSet

NOTE: For set RptID and set DataSet commands, the source is the SCL file, and cannot be set dynamically in PLC memory.

� 11: set GI� 101: get RptEna� 102: get BufTms� 103: get IntgPd� 105: get TrgOps� 106: get OptFlds� 107: get ResvUrcb� 108: get EntryID� 111: get GI� 120: get ConfRev � 121: get SgNum

Index BYTE - Buffer index number: 1...99

AutoEna BYTE - How is report enabled?� 0 = Enable on demand� 1 = Auto enable

NOTE: Auto-enable is recommended so the report is enabled in case of Hot Standby switchover.

Attribute DWORD - Common area for read/write of attribute, depending on the selected Option:� BufTms DWORD� IntgPd DWORD� ConfRev DWORD� TrgOps low WORD of attribute� OptFlds low WORD of attribute� SgNum low WORD of attribute� RptEna low WORD (bit 0) of attribute� UrcbResv low WORD (bit 0) of attribute

I/O Mapping

128 NHA31369 07/2015

GOOSE Control Block

The data structure of the {Module_name}_GOOSE_CB DDT:

SBO Control Object

The data structure of the {Module_name}_CO_OPER_SBO (select before operate) control object DDT:

RptStatus WORD - � low byte: index of report control block (1...99)� high byte:

� bit 0 = ConfRev change






Option BYTE - Option: operation selection:� 0 = GOOSE disable� 1 = GOOSE enable







NOTE: It is recommended that you check the status of the previous command before sending another command. This way you can avoid the situation where multiple commands are pending, while only one command can be exected.

I/O Mapping

NHA31369 07/2015 129

SBOw, Cancel, and Oper Control Objects

The SBOw, Cancel, and Oper control objects each present five alternative structures, depending on the data type: BOOLEAN, INT8, INT32, ENUM, or ANA. The naming convention for each control object is {Module name}_MW{%MW address}. An example of each DDT structure follows for the OPER control object:

The data structure of the {Module_name}_CO_OPER_BOOL and {Module_name}_CO_OPER_BOOL_T control object DDTs:

The data structure of the {Module_name}_CO_OPER_INT8 and {Module_name}_CO_OPER_INT8_T control object DDTs:



Check BYTE - Synchrocheck:� Bit 0: perform synchrocheck:

� 0 = no synchrocheck� 1 = perform synchrocheck

� Bit 1 = check for interlocking condition:� 0 = no check� 1 = check

� Bit 2: test

CtVal BYTE - Bit 0: ctlVal; value to control

Resv BYTE - Reserved for alignment.

OptTime TIME_850 _FORMAT

- Specify one time to delay execution.

NOTE: Applies only to {Module_name}_CO_OPER_BOOL_T.








� Bit 2: test

I/O Mapping

130 NHA31369 07/2015

The data structure of the {Module_name}_CO_OPER_INT32 and {Module_name}_CO_OPER_INT32_T control object DDTs:

CtVal INT - Value to control

Resv BYTE - Reserved for alignment.



NOTE: Applies only to {Module_name}_CO_OPER_INT8_T.


� bits 6...7: 1 = OK; 2 = Error detected� bits 0...5: Detected Error Code (see page 125)






� Bit 2: test

CtVal DINT - Value to control



NOTE: Applies only to {Module_name}_CO_OPER_INT32_T.




I/O Mapping

NHA31369 07/2015 131

The data structure of the {Module_name}_CO_OPER_ENUM and {Module_name}_CO_OPER_ENUM_T control object DDTs:

The data structure of the {Module_name}_CO_OPER_ANA and {Module_name}_CO_OPER_ANA_T control object DDTs:


Cmd BYTE TBD Trigger: effective on change




� Bit 2: test

CtVal DINT - Value to control



NOTE: Applies only to {Module_name}_CO_OPER_ENUM_T.




Cmd BYTE TBD Trigger: effective on change




CtVal_i DINT - Value to control

CtVal_f REAL - Value to control



NOTE: Applies only to {Module_name}_CO_OPER_ANA_T.



I/O Mapping

132 NHA31369 07/2015

Polling Service

The data structure of the {Module_name}_POLLING_CTRL object DDT:

NOTE: When the 140 NOP 850 00 module restarts and re-connects with the server, it automatically reads and re-initializes all I/O mapping data.



Option BYTE - Option for polling control for each IED server; each bit represents one IED:� Bit 0:

� 0 = stop polling� 1 = start polling

� Bit 2...6: <Reserved>� Bit 7:

� 0 = Auto start polling periodically� 1 Execute only once

NOTE: Bit 7 takes effect on start polling and stop polling.

Period WORD - Period to trigger command in milliseconds. Range from 500...65535 ms. If less than 500 ms, the default period from the Modicon IEC61850 Configuration Tool is applied.

Status STATUS - Status of command execution. When auto-polling is enabled, the status is updated. Status values include:� OK: when client receives all requested polling data.� Fail: when the client receives a negative response or

a time out.� Error: when the polling data includes a data object with

mismatched data. In this case, polling skips over the mismatched data object, and proceeds to the next data object in the polling request.

NHA31369 07/2015 133

Quantum IEC61850

EF and EFB for the 140 NOP 850 00

NHA31369 07/2015

Elementary Function and Elementary Function Block for the 140 NOP 850 00

Chapter 7Elementary Function and Elementary Function Block f or the 140 NOP 850 00

Overview

Unity Pro introduces the following new elementary functions (EF) and elementary function block (EFB) to support the 140 NOP 850 00 module:� NOP850_EVTS� T850_TO_T870� T870_TO_T850



Topic Page

NOP850_EVTS Elementary Function Block for the 140 NOP 850 00 134

T850_TO_T870 and T870_TO_T850 Elementary Functions for the 140 NOP 850 00 139


134 NHA31369 07/2015

NOP850_EVTS Elementary Function Block for the 140 NO P 850 00

Introduction

Use the NOP850_EVTS elementary function block (EFB) to:� Manage and synchronize the transfer of external events from an ERT or CRA into the memory

of the 140 NOP 850 00 module.� Manage the transfer external events between a PLC and the 140 NOP 850 00.

Representation in FBD

Input Parameters

Input parameter Type Description

ENABLE BOOL Start transferring.

ERT BYTE ERT type:� 0 = Quantum� 1 = Mx80

NOTE: When ERT type is:� Quantum: the time stamp is local time (UTC+TimeZone).

The module converts local time into UTC and includes it in ERT reports. The time zone is set in the SNTP configuration window of the Modicon IEC61850 Configuration Tool.

� Mx80: the time stamp is UTC time. No configuration is necessary.

EVT Either:� IED_EVT_M

(see page 136), or� IED_EVT_Q

(see page 137)

Event description, including value, quality, time stamp and ID. Type depends upon the platform, either Mx80 or Quantum.

RPT IED RPT (see page 135)

Report information.

TIMEOUT INT Time threshold in 100 ms for triggering an event. A value greater than 0.


NHA31369 07/2015 135

Output Parameters

Data Type Structure - IED_RPT

IED_RPT

Data Type Structure - IED_ERT_BUF

IED_ERT_BUF

Output parameter Type Description

DONE BOOL A value of 1 (true) indicates the function block completed successfully.

ACTIVE BOOL A value of 1 (true) indicates execution of the function block is in progress.

ERROR BOOL A value of 1 (true) indicates the function block detects an execution error.

STATUS INT Identifies the detected error:� 1 = Input parameter is not valid.� 2 = <Reserved>� 3 = Time format is not valid.

NOTE: Only dates after January 01, 2000 are valid.

� 4 = Time out occurrence (default 10 s)� 5 = Parameter change during runtime

RPT_BUFF IED ERT BUF (see page 135)

Raw buffer containing event time stamp entities.


Status WORD Report status:� Bits 0...7: Report enabled/disabled. Each bit represents one report instance:

� 0 = disabled� 1 = enabled

� Bits 8...15: Buffer overflow:� 0 = No buffer overflow� 1 = Overflow

DaChgCnt WORD A counter value that increments each time a report is generated.


NewTS BYTE Time stamp of the new event.

EvtSrc BYTE Event source:� 0 = Quantum� 1 = Mx80

EventEntity WORD[6] Event entity, which can be either:� IED_EVT_M (see page 136) or� IED_EVT_Q (see page 137)


136 NHA31369 07/2015

Data Type Structure - IED_EVT_M

IED_EVT_M: This structure describes the format of events used by Mx80 devices using the IEC61850 format:


Rese1 BYTE <Reserved>

Value BYTE Input value.

EventID WORD An event identifier, either:� The channel number; or� A user-defined value.

SecondSince Epoch

DWORD The interval, in seconds, from 1970-01-01 00:00:00 UTC to the present.

FracOfSec_L WORD The fraction of the current second when the value element, above, has been determined. The fraction of second is calculated as:(SUM from i = 0 to 23 of bi*2**–(i+1) s).

FracOfSec_H BYTE

TimeQuality BYTE TimeQuality describes provides information regarding the sending IED, and consists of the following attributes:

Bits Attribute Type Description

0...4 Time Accuracy

CODED ENUM

The accuracy class of the time source. Only the value of 10 = 1 ms is supported.

5 Clock Not Synchronized

BOOL When set to 1, this indicates the time source of the sending IED is not synchronized with external UTC time.

6 Clock Failure BOOL When set to 1, this indicates the time source of the sending IED is unreliable.

7 Leap Seconds Known

BOOL When set to 1, this indicates that SecondSinceEpoch value includes all leap year seconds. When set to 0, this indicates leap seconds are not included and seconds are calculated from the current date assuming a constant day length of 86400 s.


NHA31369 07/2015 137

Data Structure - IED_EVT_Q

IED_EVT_Q: This structure describes the format of events used by Quantum devices using the IEC61850 format:

Quantum ERT FBD Example



Value BYTE Input value.

EventID WORD An event identifier, either:� The channel number; or� A user-defined value.


Month BYTE Month: 0...12

Year BYTE Year: 00...99 (indicating 2000 to 2099)

Ms_Lsb BYTE Time in milliseconds: 0...59999 (least significant byte).

Ms_Msb BYTE Time in milliseconds: 0...59999 (most significant byte).

Min BYTE Invalid time/minutes: 0...59

Hour BYTE Summer time/hours: 0...23

Day BYTE Weekday.Day of the month: 1...31


138 NHA31369 07/2015

Mx80 CRA FBD Example


NHA31369 07/2015 139

T850_TO_T870 and T870_TO_T850 Elementary Functions for the 140 NOP 850 00

Introduction

The 140 NOP 850 00 module is a device that sends and receives data timestamped according to the IEC60870 protocol. Some Quantum ERT devices send and receive data timestamped according to the IEC 61870 protocol.

To enable data transfer between devices that support different timestamp structures, you can use the following elementary functions in your program logic:� T850_TO_T870: This EF takes IEC61850 timestamped data (for example, data generated by

the 140 NOP 850 00 module) and converts it to the more easily readable IEC 60870 format.� T870_TO_T850: This EF takes IEC 60870 timestamped data generated by a Quantum ERT

device and converts it to the IEC61850 format where it can be used by the 140 NOP 850 00 module.

T850_TO_T870 Representation in FBD

The following graphic depicts the T850_TO_T870 function:

T850_TO_T870 Parameters:

T870_TO_T850 Representation in FBD

The following graphic depicts the T870_TO_T850 function:

Parameter Type Description

Input parameters:

IN TIME_850_FORMAT The IEC61850 timestamp format.

Output parameters:

OUT TIME_870_FORMAT The IEC 60870 timestamp format.


140 NHA31369 07/2015

T870_TO_T850 Parameters:

Data Type Structure - TIME_850_FORMAT

Data Type Structure - TIME_870_FORMAT

Parameter Type Description

Input parameters:

IN TIME_870_FORMAT The IEC 60870 timestamp format.

Output parameters:

OUT TIME_850_FORMAT The IEC61850 timestamp format.


Seconds DWORD Seconds since 01-01-1970.

NOTE: Only dates after January 01, 2000 are valid.

Ms_Quality DWORD Milliseconds in IEC61850 format in low three bytes; highest byte manages quality.


ms WORD From 0...59999 ms

min BYTE Numerical minute reference: 0...59. The highest bit indicates time validity:� 0 = valid time� 1 = invalid time

hour BYTE Numerical hour reference: 0...23

NOTE: SU (summertime) is not supported.

day BYTE Numerical day reference: 1...31.

NOTE: Day of week is not supported.

mon BYTE Numerical month reference: 1...12.

year BYTE Numerical year reference: 0...99.

reserved BYTE <Reserved>

NHA31369 07/2015 141

Quantum IEC61850

Explicit Messaging

NHA31369 07/2015

Explicit Messaging

Chapter 8Explicit Messaging

Overview

This chapter explains the 140 NOP 850 00 module and its use of explicit messaging for request-and-reply communications for non-real-time information (for example, configuration and diagnostic data). A network node that receives a TCP/IP-encapsulated explicit message processes the message and generates a response.

NOTE: � A single Unity Pro application can contain more than 16 explicit messaging blocks, but only 16

explicit messaging blocks can be active at the same time.� The 140 NOP 850 00 module can process 2 MBP_MSTR blocks per MAST cycle. Therefore, it

will take at least 8 MAST cycles to process all requests in 16 MBP_MSTR blocks.� The 140 NOP 850 00 module processes MBP_MSTR blocks to reach data on the control

network only.

NOTE: If you receive a detected error message — stating that the 140 NOP 850 00 module does not have a link (has no cable), MSTR functionality may not be available. If this happens, check that your cables are connected properly.

This chapter describes how to use Unity Pro function block logic to send explicit messages.



Topic Page

Configuring Explicit Messaging Using MBP_MSTR 142

Modbus TCP Explicit Messaging Function Codes 144

Configuring the Control Parameter for Modbus TCP Explicit Messaging 145

Explicit Messaging

142 NHA31369 07/2015

Configuring Explicit Messaging Using MBP_MSTR

Overview

You can use the MBP_MSTR function block to configure Modbus TCP connected and unconnected explicit messages.

The operation begins when the input to the EN pin is turned ON. The operation ends if the ABORT pin is turned ON, or if the EN pin is turned OFF.

The CONTROL and DATABUF output parameters define the operation.

NOTE: Refer to the topic Configuring the Control Parameter for Modbus TCP (see page 145) for instructions on how to configure these parameters for each protocol.

The ACTIVE output turns ON during operation; the ERROR output turns ON if the operation aborts without success; the SUCCESS output turns ON at the successful completion of the operation.

EN and ENO can be configured as additional parameters.

Representation in FBD

Input Parameters

Parameter Data type Description

ENABLE BOOL When ON, the explicit message operation (specified in the first element of the CONTROL pin) is executing.

ABORT BOOL When ON, the operation is aborted.

Explicit Messaging

NHA31369 07/2015 143

Output Parameters

Parameter Data type Description

ACTIVE BOOL ON when the operation is active. OFF at all other times.

ERROR BOOL ON when the operation is aborted without success.OFF before operation, during operation, and if operation succeeds.

SUCCESS BOOL ON when the operation concludes successfully.OFF before operation, during operation, and if operation does not conclude successfully.

CONTROL1 WORD This parameter contains the control block. The first element contains a code describing the operation to be performed. The content of the control block depends on the operation. The structure of the control block depends on the protocol, in this case Modbus TCP).Note: Assign this parameter to a located variable.

DATABUF1 WORD This parameter contains the data buffer. For operations that:� provide data — e.g., a write operation — this parameter is the data

source� receive data — e.g., a read operation — this parameter is the data

destination

Note: Assign this parameter to a located variable.

1. Refer to the topic Configuring the Control Block for Modbus TCP for instructions on how to configure these parameters for the Modbus TCP communication protocol.

Explicit Messaging

144 NHA31369 07/2015

Modbus TCP Explicit Messaging Function Codes

Overview

Every Modbus TCP explicit message performs a function. Each function is associated with a code (or number). You need to identify the explicit messaging function by its name, decimal number, or hexadecimal number.

You can execute Modbus TCP explicit messages using a Unity Pro MBP_MSTR function block.

Services

The function codes supported by Unity Pro using the MBP_MSTR function block include the following:

Function code Sub-code Description

Hex Dec Hex Dec

0x01 1 – – Write data

0x02 2 – – Read data

0x03 3 – – Get local statistics

0x04 4 – – Clear local statistics

0x07 7 – – Get remote statistics

0x0A 10 – – Reset module

0x17 23 – – Read/write data

0xFFF0 65520 – – Enable / disable FTP service

Explicit Messaging

NHA31369 07/2015 145

Configuring the Control Parameter for Modbus TCP Ex plicit Messaging

Overview

The CONTROL and DATABUF output parameters define the operation performed by the MBP_MSTR (see page 142) function block. For the Modbus TCP protocol, both the structure and the content of the CONTROL output parameter vary, depending upon the function code (see page 144).

The structure of the CONTROL parameter is described, below, for each supported function code.

Refer to the Quantum EIO System Planning Guide for an example of an MSTR block created in a Unity Pro application to read the ports of a dual-ring switch (DRS) to diagnose a sub-ring break.

Control Parameter Routing Register

The CONTROL[5] routing register specifies the source and destination node addresses for network data transfer, and consists of the following 2 bytes:� Most Significant Byte (MSB): contains the source node address, for example, the slot number

of the 140 NOP 850 00� Least Significant Byte (LSB): contains the destination node address — a value representing

either a direct or a bridge address. The LSB is required for devices that are reached through a bridge, for example, an Ethernet to Modbus bridge or an Ethernet to Modbus Plus bridge. The values of the LSB are as follows:� If no bridge is used: LSB is set to zero(0).� If a bridge is used: LSB contains the Modbus Plus on Ethernet Transporter (MET) mapping

index value. This value, also known as the Unit ID, indicates the device to which the message is directed.

The CONTROL[5] routing register:

When the 140 NOP 850 00 module acts as a server, the LSB indicates the destination of a message received by the module:� Messages with an LSB value from 0 to 254 are forwarded to and processed by the CPU� Messages with an LSB value of 255 are retained and processed by the 140 NOP 850 00

module

NOTE: Use Unit ID 255 when requesting diagnostic data from the 140 NOP 850 00 module.

Explicit Messaging

146 NHA31369 07/2015

Write Data

The control parameter consists of 9 contiguous words, as described below:

Read Data


Register Function Description

CONTROL[1] Operation 1 = write data

CONTROL[2] Detected error status

Holds the event code (see page 181) (read-only)

CONTROL[3] Data buffer length Number of addresses sent to the slave

CONTROL[4] Starting register Start address of the slave to which the data is written, in 16-bit words

CONTROL[5] Routing register High byte = Ethernet communication module slot

Low byte = MBP on Ethernet transporter (MET) mapping index

CONTROL[6] 1 IP address Byte 4 of the IP address (MSB)

CONTROL[7] 1 Byte 3 of the IP address


CONTROL[9] 1 Byte 1 of the IP address (LSB)

1. For example, the control parameter handles the IP address 192.168.1.7 in the following order: Byte 4 = 192, Byte 3 = 168, Byte 2 = 1, Byte 1 = 7.


CONTROL[1] Operation 2 = read data

CONTROL[2] Detected error status Holds the event code (see page 181) (read-only)

CONTROL[3] Data buffer length Number of addresses to be read from the slave

CONTROL[4] Starting register Determines the %MW starting register in the slave from which the data is read. For example: 1 = %MW1, 49 = %MW49)








Explicit Messaging

NHA31369 07/2015 147

Get Local Statistics


Module Response: A TCP/IP Ethernet module responds to the Get Local Statistics command with the following information:


CONTROL[1] Operation 3 = read local statistics



CONTROL[3] Data buffer length Number of addresses to be read from local statistics (0...37)

CONTROL[4] Starting register First address from which the statistics table is read (Reg1=0)



CONTROL[6] (not used) —

CONTROL[7]

CONTROL[8]

CONTROL[9]

Word Description

00...02 MAC Address

03 Board Status — this word contains the following bits:

Bit 15 0 = Link LED off; 1 = Link LED ON

Bit 3 Reserved

Bits 14...13 Reserved Bit 2 0 = half duplex; 1 = full duplex

Bit 12 0 = 10 Mbit; 1 = 100 Mbit Bit 1 0 = not configured; 1 = configured

Bits 11...9 Reserved Bit 0 0 = PLC not running; 1 = PLC or NOC running

Bits 8...4 Module Type — this bit presents the following values:

� 0 = NOE 2x1� 1 = ENT� 2 = M1E� 3 = NOE 771 00� 4 = ETY� 5 = CIP� 6 = (reserved)� 7 = 140 CPU 651 x0� 8 = 140 CRP 312 00� 9 = (reserved)� 10 = 140 NOE 771 10

� 11 = 140 NOE 771 01� 12 = 140 NOE 771 11� 13 = (reserved)� 14 = 140 NOC 78• 00� 15...16 = (reserved)� 17 = M340 CPU� 18 = M340 NOE� 19 = BMX NOC 0401� 20 = TSX ETC 101� 21 = 140 NOC 771 01� 22 = 140 NOP 850 00

04 and 05 Number of receiver interrupts

Explicit Messaging

148 NHA31369 07/2015

Clear Local Statistics


06 and 07 Number of transmitter interrupts

08 and 09 Transmit_timeout detected error count

10 and 11 Collision_detect error count

12 and 13 Missed packets

14 and 15 (reserved)

16 and 17 Number of times driver has restarted

18 and 19 Receive framing detected error

20 and 21 Receiver overflow detected error

22 and 23 Receive CRC detected error

24 and 25 Receive buffer detected error

26 and 27 Transmit buffer detected error

28 and 29 Transmit silo underflow

30 and 31 Late collision

32 and 33 Lost carrier

34 and 35 Number of retries

36 and 37 IP address

Word Description


CONTROL[1] Operation 4 = clear local statistics








CONTROL[7]

CONTROL[8]

CONTROL[9]

Explicit Messaging

NHA31369 07/2015 149

Get Remote Statistics


Clear Remote Statistics



CONTROL[1] Operation 7 = get remote statistics



CONTROL[3] Data buffer length Number of addresses to be read from the statistics data field (0...37)

CONTROL[4] Starting register First address from which the node statistics table is read









CONTROL[1] Operation 8 = clear remote statistics












Explicit Messaging

150 NHA31369 07/2015

Reset Module


Read/Write Data



CONTROL[1] Operation 10 = reset module








CONTROL[7]

CONTROL[8]

CONTROL[9]


CONTROL[1] Operation 23 = read / write data



CONTROL[3] Data buffer length Number of addresses sent to the slave

CONTROL[4] Starting register Determines the %MW starting register in the slave to which the data will be written. For example: 1 = %MW1, 49 = %MW49)







CONTROL[10] Data buffer length Number of addresses to be read from the slave

CONTROL[11] Starting register Determines the %MW starting register in the slave from which the data is read. For example: 1 = %MW1, 49 = %MW49)


Explicit Messaging

NHA31369 07/2015 151

Enable/Disable FTP Services

When FTP has been enabled using Unity Pro configuration tools (see page 60), an MSTR block can be used to change the enabled state of the service while the application is running. The MSTR block cannot change the state of the FTP service if the service was disabled using one of the configuration tools.


FTP service state changes made by MSTR with operation code FFF0 (hex) are overridden by the configured value when the module is power-cycled or reset and when a new application is downloaded to the module.


CONTROL[1] Operation FFF0 (hex) 65520 (dec) = enable / disable FTP


Holds the event code (read-only). Codes returned include:0x000 (Success): MSTR block with operational code 0xFFF0 was called and the enabled state of FTP was changed.0x5068 (Busy): MSTR block with operational code 0xFFF0 was called within 2 seconds of the previous call (regardless of return code from previous call).0x4001 (Same state): MSTR block with operational code 0xFFF0 was called to change the enabled state of FTP to the states they were already in.0x2004 (Invalid data): MSTR block with operational code 0xFFF0 was called and the data in the control block did not match the specifications. 0x5069 (Disabled): If the FTP service was already disabled via the Unity Pro interface when the MSTR block with operational code 0xFFF0 was called to change the state of the disabled service.

CONTROL[3] Set this register to 1.

CONTROL[4]

CONTROL[5] Module slot number and destination ID

High byte = Module slot number communication module slot

Low byte = Destination ID

CONTROL[6] Request mode Bit 0 (LSB) = 1: Enable FTPBit 0 (LSB) = 0: Disable FTP

CONTROL[7] Set this register to 0.

CONTROL[8]

CONTROL[9]

Explicit Messaging

152 NHA31369 07/2015

Here are some examples:

State Configured By Unity Pro

Action attempted using MSTR with operation code FFF0 (hex)

Result

Disabled Any MSTR returns detected error code 0x5069 (service was already disabled by configuration)

Enabled Disable MSTR returns code 0x000 (success). � Another MSTR block action enables the service

--OR--� The module is reset or power-cycled

--OR--� A new application is downloaded with the service disabled

by configuration

Enable MSTR returns detected error code 0x4001 (same state). No change made.

NHA31369 07/2015 153

Quantum IEC61850

Diagnostics

NHA31369 07/2015

Diagnostics

Chapter 9Diagnostics

Overview

This chapter describes the diagnostics for the 140 NOP 850 00 module.



Topic Page

LED Indicators on the 140 NOP 850 00 Module 154

Modbus Diagnostic Codes 157

Modbus Diagnostic Codes 167

IEC61850 Diagnostic Codes 169

Hot Standby Switchover 171

Diagnostics

154 NHA31369 07/2015

LED Indicators on the 140 NOP 850 00 Module

Display

These LEDs are on the front of the 140 NOP 850 00 module:

LED Display Panel Indicators

Use the LEDs in display panel to diagnose module conditions, as follows:

DescriptionActive 4 Ready Mod Status Net Status Net Status 1 Net Status 2

Green Green Green Red Green Red Green Red Green RedGeneral Component

not operating— Off Off On — — — — — —

Invalid configuration

— Off Off Flash — — — — — —

Not configured

— — Flash Off — — — — — —

Configured — Blink On Off on/flash

Off on/flash

Off on/flash

Off

no/default module MAC

— Blink 2 Off Flash Off Off Off Off Off Off

no/default port MAC

— Blink 2 Off Flash Off Off Off Off Off Off

Diagnostics

NHA31369 07/2015 155

– Not affected. The LED continues to operate as other conditions dictate.1 RDY blinks for a duplicate IP on any network, and the individual NS LEDs indicate the network

with the duplicate IP.2 RDY blinks for a default IP on any network.3 RDY blinks 5 if any network is configured to be used, but no Ethernet link is connected to it. For

example, the router is enabled but ETH 2 does not have a cable connected to it.4 ACT remains ON after the module has completed its power-up sequence and has an active

connection to the CPU.

Power-up Sequence 5(On

0.25 sec. Off

0.25 sec)

6(On

0.25 sec. Off

0.25 sec)

1(Green on 0.25 sec. Green off.

Red on 0.25 sec; Red off.

Green on)



Green on)



Green on)



Green on)

61850 protocol

No connections or all connections closed

— On On Off Flash Off Flash Off Flash Off

Connected — On On Off On Off On Off On Off

IP status No Ethernet links

— Blink 3 — — Off On Off On Off On

Duplicate IP1 — Blink 4 — — Off On Off On Off On

Waiting for IP

— Blink 5 On Off Off Off Off Off Off Off

Default IP

address2— Blink 6 On Off Off Off Off Off Off Off

Configured IP address assigned



— Blink 7 On Off Off Off Off On Off Off

Routing Service

Duplicate IP1 — Blink 4 On Off On Off Flash Off Off On

Waiting for

IP3— Blink 5 On Off Off Off On Off Off Off

Default IP2 — Blink 6 On Off Off Off Off Off Off Off

Receive or assign IP



— Blink 7 On Off Off Off Off Off Off Off

DescriptionActive 4 Ready Mod Status Net Status Net Status 1 Net Status 2

Green Green Green Red Green Red Green Red Green Red

Diagnostics

156 NHA31369 07/2015

Ethernet Port LED Indicators

Use the Ethernet port LEDs to diagnose the status of the respective Ethernet port:

Name Color Status Description

LINK (ETH 1 and ETH 2) Green On 100 Mbit/s link detected

Yellow On 10 Mbit/s link detected

— Off No detected link

LINK (ETH 3 and ETH 4) Green On 1000 Mbit/s link detected

Yellow On 10 Mbps or 100 Mbps link detected

— Off No detected link

ACT Green Blinking Active Ethernet link (transmit or receive detected)

— Off Inactive Ethernet link

Diagnostics

NHA31369 07/2015 157

Modbus Diagnostic Codes

Supported Diagnostic Codes

Modbus function code 3 provides access to a variety of diagnostic functions, including basic network diagnostics, Ethernet port diagnostics, and Modbus port 502 diagnostics.

To access the function code 3 diagnostics from the local device, set the unit ID to 255.

The following modules support these Modbus diagnostic codes.� Quantum remote I/O head module (140 CRP 312 00)� Quantum distributed I/O head module (140 NOC 780 00)� Quantum control head module (140 NOC 781 00)� Quantum remote I/O adapter module (140 CRA 312 00)� M340 remote I/O adapter module (BMX CRA 312 00)� Quantum IEC 61850 module (140 NOP 850 00)

Modbus Function Code 3: Basic Network Diagnostics

Basic network diagnostics start at address 40001(decimal) as described in the following table.

Starting Address (Decimal)

Length (Words)

Register Byte Order Comments

MS BYTE LS BYTE

40001 2 MS Byte 00 Byte 01 Basic network diagnostic validity

Byte 02 LS Byte

40003 1 MS Byte LS Byte 03 Communication global status

40004 1 MS Byte LS Byte Supported communication services

40005 1 MS Byte LS Byte Status of communication services

40006 2 IP 1 IP 2 IP address (IP1.IP2.IP3.IP4)

IP 3 IP 4

40008 2 SM 1 SM 2 Subnet mask (SM1.SM2.SM3.SM4)

SM 3 SM 4

40010 2 GW 1 GW 2 Default gateway (GW1.GW2.GW3.GW4)

GW 3 GW 4

40012 3 MAC 1 MAC 2 MAC address (MAC1:MAC2:MAC3:MAC4:MAC5:MAC6.

MAC 3 MAC 4

MAC 5 MAC 6

40015 3 MS Byte 00 01 Ether frame format capability / configuration / operational

02 03

04 LS Byte 05

Diagnostics

158 NHA31369 07/2015

Example: Reading Basic Network Diagnostics with Mod bus Function Code 3

Here is an example of how to read registers 40018 and 40019, the Ethernet receive frames OK count registers. The request contains 7 bytes. The starting address, shown as a hex value in byte 2 below, is calculated as follows:

40018 – 40001 = 17 dec = (11 hex)

40018 2 C00 C01 Ethernet receive frames OK

C02 C03

40020 2 C00 C01 Ethernet transmit frames OK

C02 C03

40022 1 MS Byte LS Byte Number of open client connections

40023 1 MS Byte LS Byte Number of open server connections

40024 2 C00 C01 Number of Modbus detected error messages sent

C02 C03

40026 2 C00 C01 Number of Modbus messages sent

C02 C03

40028 2 C00 C01 Number of Modbus messages received

C02 C03

40030 8 Char 1 Char 2 Device name

Char 3 Char 4

Char 5 Char 6

Char 7 Char 8

Char 9 Char 10

Char 11 Char 12

Char 13 Char 14

Char 15 Char 16

40038 2 MS Byte 00 Byte 01 IP assignment mode capability / operational

Byte 02 LS Byte 03


Length (Words)


MS BYTE LS BYTE

Diagnostics

NHA31369 07/2015 159

The number of registers to be diagnosed (2 hex) is shown in byte 4:

The normal response is returned in 8 bytes. In this example, the expected response is 14229 hex; this value is shown in bytes 2 through 5 of the response:

For more information on Modbus function code 3 and other function codes, refer to the Modicon Modbus Protocol Reference Guide (PI-MBUS-300).

Byte Number Value

0 Function code = 03 (hex)

1 Starting Address Hi = 00 (hex)

2 Starting Address Low = 11 (hex)

3 No. of Registers Hi = 00 (hex)

4 No. of Registers Low = 2 (hex)

5 CRC high byte (inserted by the Modbus sending application)

6 CRC low byte (inserted by the Modbus sending application)

Byte Number Value

0 Function code = 03 (hex)

1 Byte count = 4 (hex)

2 1st register data, high byte = 00 (hex)

3 1st register data, low byte = 01 (01 hex)

4 2nd register data, high byte = 42 (hex)

5 2nd register data, low byte = 29 (hex)

6 CRC high byte

7 CRC low byte

Byte Number Value

0 Original function code + 80 hex (= 83 hex)

1 Detected error code

2 CRC high byte

3 CRC low byte

Diagnostics

160 NHA31369 07/2015

Modbus Function Code 3: Ethernet Internal Port Diag nostic Data

Internal port diagnostics start at address 40040 (decimal) as described in the following table.


Length (Words)


MS BYTE LS BYTE

40040 1 MS Byte LS Byte Internal port Diagnostics Data Validity

40041 1 MS Byte LS Byte Internal port Logical/Physical Port Number

40042 1 MS Byte LS Byte Internal port Ethernet Control Capability

40043 1 MS Byte LS Byte Internal port Link Speed Capability

40044 1 MS Byte LS Byte Internal port Ethernet Control Configuration

40045 1 MS Byte LS Byte Internal port Link Speed Configuration

40046 1 MS Byte LS Byte Internal port Ethernet Control Operational

40047 1 MS Byte LS Byte Internal port Link Speed Operational

40048 3 MAC 1 MAC 2 MAC Address (MAC1:MAC2:MAC3:MAC4:MAC5:MAC6)

MAC 3 MAC 4

MAC 5 MAC 6

40051 2 MSB C00 C01 Internal port Media Counters Data Validity

C02 LSB C03

40053 2 MSB C00 C01 Internal port Num Frames Transmitted OK

C02 LSB C03

40055 2 MSB C00 C01 Internal port Num Frames Received OK

C02 LSB C03

40057 2 MSB C00 C01 Internal port Num Ether Collisions

C02 LSB C03

40059 2 MSB C00 C01 Internal port Carrier Sense Errors detected

C02 LSB C03

40061 2 MSB C00 C01 Internal port Num Ether Excessive Collisions

C02 LSB C03

40063 2 MSB C00 C01 Internal port CRC Errors detected

C02 LSB C03

40065 2 MSB C00 C01 Internal port FCS Errors detected

C02 LSB C03

40067 2 MSB C00 C01 Internal port Alignment Errors detected

C02 LSB C03

40069 2 MSB C00 C01 Internal port Num Internal MAC Tx Errors detected

C02 LSB C03

Diagnostics

NHA31369 07/2015 161

40071 2 MSB C00 C01 Internal port Late Collisions

C02 LSB C03

40073 2 MSB C00 C01 Internal port Num Internal MAC Rx Errors detected

C02 LSB C03

40075 2 MSB C00 C01 Internal port Multiple Collisions

C02 LSB C03

40077 2 MSB C00 C01 Internal port Single Collisions

C02 LSB C03

40079 2 MSB C00 C01 Internal port Deferred Transmissions

C02 LSB C03

40081 2 MSB C00 C01 Internal port Frames Too Long

C02 LSB C03

40083 2 MSB C00 C01 Internal port Frames Too Short

C02 LSB C03

40085 2 MSB C00 C01 Internal port SQE Test Error detected

C02 LSB C03

40087 1 MS Byte LS Byte Internal port Interface Label Length

40088 32 IL char64 IL char63 Internal port Interface Label characters

40089 IL char62 IL char61

... ... ...



40120 1 MS Byte LS Byte Internal port Interface Counters Diagnostic Validity

40121 2 MSB C00 C01 Internal port Num Octets Received

C02 LSB C03

40123 2 MSB C00 C01 Internal port Num Unicast Packets Received

C02 LSB C03

40125 2 MSB C00 C01 Internal port Num Non Unicast Packets Received

C02 LSB C03

40127 2 MSB C00 C01 Internal port Num Inbound Packets Discarded

C02 LSB C03

40129 2 MSB C00 C01 Internal port Num Inbound Packets Error detected

C02 LSB C03


Length (Words)


MS BYTE LS BYTE

Diagnostics

162 NHA31369 07/2015

Modbus Function Code 3: Ethernet Port 1 Diagnostic Data

Port 1 diagnostics start at address 40143 (decimal). As described in the following table, port 1 diagnostic data fields are the same as for the internal port, with the appropriate starting address offset.


Port 2 diagnostics start at address 40246 (decimal). As described in the following table, port 2 diagnostic data fields are the same as for the internal port and port 1, with the appropriate starting address offset.

401331 2 MSB C00 C01 Internal port Num Inbound Packets Unknown

C02 LSB C03

40133 2 MSB C00 C01 Internal port Num Octets Sent

C02 LSB C03

40135 2 MSB C00 C01 Internal port Num Unicast Packets Sent

C02 LSB C03

40137 2 MSB C00 C01 Internal port Num Non Unicast Packets Sent

C02 LSB C03

40139 2 MSB C00 C01 Internal port Num Outbound Packets Discarded

C02 LSB C03

40141 2 MSB C00 C01 Internal port Num Outbound Packets Error detected

C02 LSB C03


Length (Words)


MS BYTE LS BYTE

Starting Address

Length Register Byte Order Comments

MS BYTE LS BYTE

40143 1 MS Byte LS Byte Port 1 Port Diagnostics Data Validity

... ... ... ... ...

40244 2 MSB C00 C01 Port 1 Num Outbound Packets Error detected

C02 LSB C02

Starting Address


MS BYTE LS BYTE


... ... ... ... ...


C02 LSB C02

Diagnostics

NHA31369 07/2015 163


Port 3 diagnostics start at address 40349 (decimal). As described in the following table, port 3 diagnostic data fields are the same as for the internal port and ports 1 and 2, with the appropriate starting address offset.


Port 4 diagnostics start at address 40452 (decimal).As described in the following table, port 4 diagnostic data fields are the same as for the internal port and ports 1-3, with the appropriate starting address offset.

Ethernet Port Not Present

If an Ethernet port is not physically present on the device, the relevant Modbus registers will return data = 0.

Starting Address


MS BYTE LS BYTE


... ... ... ... ...


C02 LSB C03

Starting Address


MS BYTE LS BYTE


... ... ... ... ...


C02 LSB C03

Diagnostics

164 NHA31369 07/2015

Modbus Function Code 3: Modbus TCP Port 502 Diagnos tic Data

Modbus TCP port 502 diagnostics start at address 40555 (decimal) as described in the following table.

Starting Address


MS BYTE LS BYTE

40555 2 MS Byte 00 Byte 01 Modbus TCP/Port 502 Diagnostic Data ValidityByte 02 LS Byte 03

40557 1 MS Byte LS Byte Port 502 Status

40558 1 MS Byte LS Byte Num Open Connections

40559 2 MSB C00 C01 Num MB Messages Sent

C02 LSB C03

40561 2 MSB C00 C01 Num MB Messages Received

C02 LSB C03

40563 1 MS Byte LS Byte Num MB Open Client Connections

40564 1 MS Byte LS Byte Num MB Open Server Connections

40565 1 MS Byte LS Byte Max Num Connections

40566 1 MS Byte LS Byte Max Num Client Connections

40567 1 MS Byte LS Byte Max Num Server Connections

40568 2 MSB C00 C01 Num MB Detected Error Messages Sent

C02 LSB C03

40570 1 MS Byte LS Byte Num Open Priority Connections

40571 1 MS Byte LS Byte Max Num Priority Connections

40572 1 MS Byte LS Byte Num Entries in Unauthorized Table

40573 2 MSB - IP1 IP2 Remote IP Address 1 Connection 1

IP3 LSB - IP4

40575 1 MS Byte LS Byte Num Attempts to Open Unauthorized Connection 1


IP3 LSB - IP4


... ... ... ... ...


IP3 LSB - IP4



IP3 LSB - IP4


Diagnostics

NHA31369 07/2015 165

Modbus Function Code 3: Modbus TCP Port 502 Connecti on Table Data

Modbus TCP port 502 connection table data starts at address 40669 (decimal) as described in the following table.

Starting Address


MS BYTE LS BYTE

40669 1 MS Byte LS Byte Connection Table Validity

40670 1 MS Byte LS Byte Number of Entries

40671 1 MS Byte LS Byte Starting Entry Index

40672 1 MS Byte LS Byte Connection 1 Index Connection 1

40673 2 IP1 IP2 Connection 1 Remote IP Address

IP3 IP4

40675 1 MS Byte LS Byte Connection 1 Remote Port Number

40676 1 MS Byte LS Byte Connection 1 Local Port Number

40677 1 MS Byte LS Byte Num MB Messages Sent on Connection 1

40678 1 MS Byte LS Byte Num MB Messages Received on Connection 1

40679 1 MS Byte LS Byte Num MB Detected Error Messages Sent on Connection 1

40680 1 MS Byte LS Byte Connection 2 Index Connection 2


IP3 IP4






... ... ... ... ...

Diagnostics

166 NHA31369 07/2015

41168 1 MS Byte LS Byte Connection 63 Index Connection 63*


IP3 IP4






41176 1 MS Byte LS Byte Connection 64 Index Connection 64*


IP3 IP4






*140 CRA 312 10 and BMX CRA 312 •0 RIO adapter modules support a maximum of 8 connections.

Starting Address


MS BYTE LS BYTE

Diagnostics

NHA31369 07/2015 167

Modbus Diagnostic Codes

SNTP and QoS Diagnostic Codes

The 140 NOP 850 00 module also supports the following diagnostic codes.

Modbus SNTP Diagnostic Codes

SNTP diagnostic codes begin at 41219 (decimal) as described in the following table:

Address MS Byte LS Byte Modbus Type Comments

41219 MSW - MSB MSW - LSB UDINT Enabled/disabled

Offset + 01 LSW - MSB LSW - LSB

Offset + 02 MSW - MSB MSW - LSB UDINT Primary NTP Server IP Address


Offset + 04 MSW - MSB MSW - LSB UDINT Secondary NTP Server IP Address


Offset + 06 Unused LS Byte USINT Polling Period

Offset + 07 Unused LS Byte USINT Daylight Saving Auto Adjustment

Offset + 08 Unused LS Byte USINT Update CPU with Module Time

Offset + 09 Unused LS Byte USINT Reserved

Offset + 10 MSW - MSB MSW - LSB UDINT Time Zone


Offset + 12 MS Byte LS Byte INT Time Zone Offset

Offset + 13 Unused Unused USINT Reserved

Offset + 14 Unused Unused USINT Reserved

Offset + 15 Unused LS Byte USINT Daylight Saving Start Date - Month

Offset + 16 Unused LS Byte USINT Daylight Saving Start Date - week # day of week

Offset + 17 Unused LS Byte USINT Daylight Saving End Date - Month

Offset + 18 Unused LS Byte USINT Daylight Saving End Date - week # day of week

Offset + 19 MSW - MSB MSW - LSB UDINT Network Time Service Status


Offset + 21 MSW - MSB MSW - LSB UDINT Link to NTP Server Status


Offset + 23 MSW - MSB MSW - LSB UDINT Current NTP Server IP Address


Diagnostics

168 NHA31369 07/2015

Modbus QoS Diagnostic Codes

QoS diagnostic codes begin at 41261 (decimal) as described in the following table

Offset + 25 MSW - MSB MSW - LSB UDINT NTP Server Type


Offset + 27 MSW - MSB MSW - LSB UDINT NTP Server Time Quality


Offset + 29 MSW - MSB MSW - LSB UDINT Number of NTP Requests Sent


Offset + 31 MSW - MSB MSW - LSB UDINT Number of Communication Errors


Offset + 33 MSW - MSB MSW - LSB UDINT Number of NTP Reponses Received


Offset + 35 MS Byte LS Byte UINT Last Error

Offset + 36 MSW - MSB MSW - LSB UDINT Current Time


Offset + 38 MS Byte LS Byte UINT Current Date

Offset + 39 MSW - MSB MSW - LSB UDINT Daylight Savings Status


Offset + 41 MSW - MSB MSW - LSB UINT Time Since Last Update



Address MS Byte LS Byte CIP Type Comments

41261 MS Byte LS Byte UINT 802.1Q Tag enable / disable

Offset + 01 MS Byte LS Byte UINT Reserved for DSCP PTP Event

Offset + 02 MS Byte LS Byte UINT Reserved for DSCP PTP General

Offset + 03 MS Byte LS Byte UINT Reserved for DSCP EIP Urgent

Offset + 04 MS Byte LS Byte UINT Reserved for DSCP EIP Scheduled

Offset + 05 MS Byte LS Byte UINT Reserved for DSCP EIP High

Offset + 06 MS Byte LS Byte UINT Reserved for DSCP EIP Low

Offset + 07 MS Byte LS Byte UINT Reserved for DSCP EIP Explicit

Offset + 08 MS Byte LS Byte UINT Reserved for DSCP Modbus IO Scanner (same as DSCP EIP High)

Offset + 09 MS Byte LS Byte UINT DSCP Modbus Client/Server (same EIP Explicit)

Offset + 10 MS Byte LS Byte UINT DSCP SNTP

Offset + 11 MS Byte LS Byte UINT DSCP IEC61850_Client

Diagnostics

NHA31369 07/2015 169

IEC61850 Diagnostic Codes

Introduction

The 140 NOP 850 00 module supports IEC61850 server, server report, and client diagnostic codes.

Server Diagnostic Codes


42201 Active Health WORD � Active: 1 indicates configured� Health: 1 indicates service is

operational

42201+ 1 ProtoEd ActiveConn WORD � ProtoEd :IEC61850 Edition version� ActiveConn:Number of connection

established with this server

42201+ 2 MSW - MSB MSW - LSB UDINT A counter that increments each time the server receives a read variable request.LSW - MSB LSW - LSB

42201+ 4 MSW - MSB MSW - LSB UDINT Number of rejected MMS read variable requestsLSW - MSB LSW - LSB

42201+ 6 MSW - MSB MSW - LSB UDINT A counter that increments each time the server receives a write variable request.LSW - MSB LSW - LSB

42201+ 8 MSW - MSB MSW - LSB UDINT Number of rejected MMS write variable requestsLSW - MSB LSW - LSB

42201+ 10 MSW - MSB MSW - LSB UDINT A counter that increments each time the server sends an information report message.

LSW - MSB LSW - LSB

42201+ 12 MSW - MSB MSW - LSB UDINT A counter that increments each time the server sends a GOOSE.LSW - MSB LSW - LSB

42201+ 14 MSW - MSB MSW - LSB UDINT A counter that increments each time the server receives a GOOSE.LSW - MSB LSW - LSB

42201+ 16 MSW - MSB MSW - LSB UDINT A counter that increments each time the server receives an invalid GOOSE.LSW - MSB LSW - LSB

42201+ 18 MSW - MSB MSW - LSB DWORD Detected error code

LSW - MSB LSW - LSB

Diagnostics

170 NHA31369 07/2015

Server Report Diagnostic Codes

Client Diagnostic Codes


42221 Enabled Overflow WORD � Enabled: 1 indicates configured� Overflow: 1 indicates service is operational

42221+ 1 MSB LSB WORD Counter for data exchange for one report-1

... ... ... ... ...

... ... ... ... ...

42221 Enabled Overflow WORD � Enabled: 1 indicates configured� Overflow: 1 indicates service is operational

42221+ 63 MSB LSB WORD Counter for data exchange for one report – 64


42349 Active Health WORD � Active: 1 indicates configured� Health: 1 means service is operational

42349+ 1 ProtoEd ActiveConn WORD � ProtoEd :IEC61850 Edition version� ActiveConn:Number of connections

established with this server

42349+ 2 MSW - MSB MSW - LSB UDINT IED connection status

LSW - MSB LSW - LSB

42349+ 4 MSW - MSB MSW - LSB UDINT A counter that increments each time the client receives a read variable.LSW - MSB LSW - LSB

42349+ 6 MSW - MSB MSW - LSB UDINT Number of rejected MMS read variable requestsLSW - MSB LSW - LSB

42349+ 8 MSW - MSB MSW - LSB UDINT A counter that increments each time the client sends a write variable requestLSW - MSB LSW - LSB

42349+ 10 MSW - MSB MSW - LSB UDINT Number of rejected MMS write variable requestsLSW - MSB LSW - LSB

42349+ 12 MSW - MSB MSW - LSB UDINT A counter that increments each time the client receives an information report message.LSW - MSB LSW - LSB

42349+ 14 MSW - MSB MSW - LSB UDINT A counter that increments each time the client receives a goose.LSW - MSB LSW - LSB

42349+ 16 MSW - MSB MSW - LSB UDINT A counter that increments each time the client receives an invalid goose.LSW - MSB LSW - LSB

42349+ 18 MSW - MSB MSW - LSB DWORD Detected error code

LSW - MSB LSW - LSB

Diagnostics

NHA31369 07/2015 171

Hot Standby Switchover

Overview

The 140 NOP 850 00 module supports the Quantum Hot Standby function. In a Quantum Hot Standby system, the primary and standby PLCs continuously exchange data – including the state RAM – of the two 140 NOP 850 00 modules. This data is located in located (%MW) memory.

NOTE: When you configure the Hot Standby function of the Quantum CPU (in the Configuration → Hot Standby tab)), confirm that the State RAM → Non-Transfer Area does not include the %MW location of 140 NOP 850 00 module data.

IEC61850 Server Functions in a Quantum Hot Standby System

SCADA:

In a Quantum Hot Standby system, the primary PLC performs SCADA functions in the same manner as a standalone PLC. The standby PLC does not communicate with SCADA, but does monitor PLC memory each scan and generates reports.

On switchover, the primary PLC closes the connection with SCADA; the standby PLC starts to listen for and accept new connection requests from SCADA. The former standby PLC – now the primary – first applies the data values received from the former primary to its local database, and then begins to perform SCADA functions after a SCADA connection is established.

Report Functions:

On every PLC cycle, the two 140 NOP 850 00 modules synchronize the buffered report Entry ID value. After switchover, SCADA needs to explicitly set the Entry ID to the 140 NOP 850 00 module in the new primary PLC so that the module can continue to send buffered reports.

The Integrity Period setting is disabled for buffered and unbuffered reports in a Hot Standby system, because the 140 NOP 850 00 module in the standby PLC cannot generate periodic reports.

GOOSE:

Only the 140 NOP 850 00 module in the primary PLC can publish GOOSE transmissions.

The 140 NOP 850 00 modules in both the primary and standby PLCs receive GOOSE data from the remote IED. However, the data received by the standby PLC is not added to memory, but is only added to the local database.

On switchover, the 140 NOP 850 00 module in the standby PLC takes over the task of sending GOOSE. However, the stNum and sqNum fields are not synchronized.

Diagnostics

172 NHA31369 07/2015

IEC61850 Client Functions in a Quantum Hot Standby System

Connection with Remote IED:

Only the 140 NOP 850 00 module in the primary PLC communicates with the remote IED; the 140 NOP 850 00 module in the standby PLC does not establish a connection with remote IED.

The 140 NOP 850 00 modules in both the primary and standby PLCs synchronize data out values from PLC memory to the local database. However, because the standby PLC doesn’t send output data to the remote IED, the remote IED receives output data only from the 140 NOP 850 00 module in the primary PLC.

GOOSE:

The 140 NOP 850 00 modules in both the primary and standby PLCs receive GOOSE data from the remote IED. However, the data received by the standby PLC is not added to memory, but is only added to the local database.

Report Functions:

It is recommended to automatically enable the report function for buffered and unbuffered report control blocks by setting the AutoEna field to 1 (auto enable). After switchover, the 140 NOP 850 00 module sets the Entry ID to the remote IED and automatically enables the report when establishing a connection with the remote IED.

Switchover:

On switchover, the 140 NOP 850 00 module in the primary PLC closes the connection with remote IED; the 140 NOP 850 00 module in the former standby – now the primary – PLC begins to communicate with remote IED.

If the execution of a report control block/GOOSE command, polling command, or control operation is interrupted by a switchover, the high byte of the Status element for that object returns a detected error bit. It is recommended to add an error handling procedure to your program logic that will manage this detected error by re-sending the command.

140 NOP 850 00 IP Address Recovery Time

Use the following formula to determine the 140 NOP 850 00 module IP address recovery time in a Quantum Hot Standby system:

500 ms (IP address swapping) + connection establishment time (3 s)

NOTE: The maximum swap time may increase if the end device does not respond in a timely manner.

NOTE: During the swap, there may be disruption in communication between the 140 NOP 850 00 module and the end device. Confirm that the application can tolerate this communication disruption.

NHA31369 07/2015 173

Quantum IEC61850

Firmware Upgrade

NHA31369 07/2015

Firmware Upgrade

Chapter 10Firmware Upgrade

140 NOP 850 00 Firmware Upgrade

OS

Use the Unity Pro OS Loader to upgrade the firmware on the 140 NOP 850 00 Ethernet communication module. OS Loader was installed on your PC when you installed Unity Pro. (The minimum required version of OS Loader is V7.0. The compatible version is included with your copy of Unity Pro.)

A complete firmware upgrade includes the installation of these discrete files:� Kernel� Exec

The kernel and exec files are installed independently. Therefore, perform the firmware upgrade process two times (once for each file).

The name of the firmware file indicates the upgrade type (kernel or exec). Examples:� Kernel file name: 140 NOP 850 00 KERN.bin� Exec file name: 140 NOP 850 00.bin

NOTE: These instructions assume that you are familiar with Unity Pro. For more information about the OS Loader, refer to the OS Loader screens topic in the Unity Pro OS Loader User Manual (35006156).

Upgrade Procedure

Follow these steps to upgrade either the firmware kernel or the firmware exec.

NOTE: � Before performing the firmware upgrade procedure, check whether the module’s FTP service is

enabled, and if it is not, enable it. (see page 60)� Schneider Electric recommends that you update the kernel before you upgrade the exec. Both

firmware upgrade files are installed in the same manner. The only difference is the name of the file you select.

� Interruption to power or communications during the firmware upgrade process can disrupt the upgrade. If that happens, restart the module. The module firmware will return to its original version.

Firmware Upgrade

174 NHA31369 07/2015

The upgrade process takes approximately 2 minutes:� 1 minute for firmware upgrade� 1 minute to restart

NOTE: During the firmware upgrade, the communications with the 140 NOP 850 00 module are interrupted. After the hold up time expires, the modules return to their fallback state.

Step Action Comment

1 Connect the PC that is running the Unity Pro OS Loader directly to one of the module ports.

Available ports:� ETH 1 or ETH 2 when configured as an

extended network (see page 48) port� DRS port that is configured for a

distributed I/O cloud

2 Launch OS Loader. Start → Programs → Schneider Electric → SoCollaborative → OS Loader .

3 Click Next to continue. Go directly to the first installation step.

4 Select the FTP communication driver and press Next to continue.

The next screen displays a list of devices discovered by OS Loader. It also displays the FTP address for each discovered device.

5 In the Target Address area, type the FTP Address of the 140 NOP 850 00 module that is the target of the upgrade.

—

6 Click Next to continue. Perform these tasks at the next installation screen:a Select Download OS to device .b Click the Browse button to navigate to and select

the desired firmware upgrade file.

—

7 Click Next . Perform these tasks at the next installation screen:a Compare the selected firmware File against the

firmware already loaded in the Device .b Confirm that the Hardware ID for both the file and

the device are the same

—

8 Click Next . On the summary page, click Download . The OS Loader displays the progress of the FTP session. The download is complete when it displays the word SUCCESS.

9 Click Close . The firmware download is finished.

Firmware Upgrade

NHA31369 07/2015 175

Hot Standby

Use these steps to upgrade the 140 NOP 850 00 firmware in Hot Standby configurations:

Step Action

1 Use the preceding instructions to upgrade the firmware for the 140 NOP 850 00 in the standby rack.

NOTE: During the firmware upgrade, the communications with the 140 NOP 850 00 module in the primary rack are not interrupted.

2 When the firmware on the 140 NOP 850 00 in the standby rack is upgraded, perform a manual switch-over that gives the newly upgraded standby rack the role of primary rack.

Firmware Upgrade

176 NHA31369 07/2015

NHA31369 07/2015 177

Quantum IEC61850

Protocol Conformance

NHA31369 07/2015


Chapter 11Protocol Conformance

Statement of Protocol Conformance

Conformance

The 140 NOP 850 00 module complies with Edition .1.0 or 2.0 of the IEC61850 communication protocol. Schneider Electric recommends using the module only in a network in which all devices support the same edition of the protocol.

The 140 NOP 850 00 was tested against and conforms to the following standards:� PICS - Protocol Implementation Conformance Statement � PIXIT - Protocol Implementation Conformance Extra Information for Testing� TICS - Technical Issue Conformance Statement


178 NHA31369 07/2015

NHA31369 07/2015 179

Quantum IEC61850

NHA31369 07/2015

Appendices

What Is in This Appendix?

The appendix contains the following chapters:

Chapter Chapter Name Page

A Detected Error Codes 181

B Supported Data Model Items 187

180 NHA31369 07/2015

NHA31369 07/2015 181

Quantum IEC61850

Detected Error Codes

NHA31369 07/2015


Appendix ADetected Error Codes

Overview

This chapter contains a list of codes that describe the status of Ethernet communication module messages.



Topic Page

TCP/IP Ethernet Detected Error Codes 182

Modbus TCP Explicit Messaging Detected Error Codes 183

IEC61850 Explicit Messaging Detected Error Codes 184


182 NHA31369 07/2015

TCP/IP Ethernet Detected Error Codes

TCP/IP Ethernet Detected Error Codes

An event in an MBP_MSTR routine via TCP/IP Ethernet may produce one of the following codes in the MBP_MSTR control block.

TCP/IP Ethernet Hexadecimal Detected Error Codes

TCP/IP Ethernet hexadecimal detected error codes include:

Code (hexadecimal) Meaning

16#1001 Abort by user

16#2001 An operation type that is not supported has been specified in the control block

16#2002 One or more control block parameters were modified while the MSTR element was active (this only applies to operations which require several cycles for completion). Control block parameters my only be modified in inactive MSTR components.

16#2003 Invalid value in the length field of the control block

16#2004 Invalid value in the offset field of the control block

16#2005 Invalid value in the length and offset fields of the control block

16#2006 Unauthorized data field on slave

16#2007 Invalid slot number in the configuration routing registerExample : 253 for 140 CRP 312 00 slot number

16#2008 Unauthorized network routing path on slave

16#200E The control block is not assigned, or parts of the control block are located outside of the %MW (4x) range.

16#200F The space allocated for the CIP response is too small.

16#3000 Generic Modbus exception response

16#3001 Slave does not support requested operation

16#3002 Non-existing slave registers were requested

16#3003 An unauthorized data value was requested

16#3005 Slave has accepted a lengthy program command

16#3006 Function cannot currently be carried out: lengthy command running

16#3007 Slave has rejected lengthy program command

16#4001 Inconsistent response by Modbus slave

16#F001 Module is resetting

16#F002 Component not fully initialized


NHA31369 07/2015 183

Modbus TCP Explicit Messaging Detected Error Codes

Modbus TCP Detected Error Codes

An event in an MBP_MSTR routine via Modbus TCP may produce one of the following detected error codes in the MBP_MSTR control block.

Modbus TCP Hexadecimal Detected Error Codes

Modbus TCP hexadecimal detected error codes include:

Code (hexadecimal) Meaning

16#5101 No resources

16#5102 Bad IP address

16#5103 Transaction timed out

16#5104 Concurrent connections or transactions limit reached

16#5105 Remote address not allowed

16#5106 No route to host

16#5107 Remote host is down

16#5108 Connection reset by peer

16#5109 Network is down

16#5301 � No resources available— or —

� Module not ready or initializing

16#510A Connection refused

16#510B Connection timed out


184 NHA31369 07/2015

IEC61850 Explicit Messaging Detected Error Codes

Introduction

If an MBP_MSTR function block does not execute an explicit message, Unity Pro displays a hexidecimal detected error code.

Refer to the topic TCP/IP Ethernet detected error codes (see page 182) for a description of those codes.

IEC61850 Detected Error Codes

IEC61850 hexadecimal detected error codes include:

Code (hexadecimal) Description

16#800D Timeout on the explicit message request

16#8015 Either:� Nor resources to handle the message, or� Internal event: no buffer available, no link available, impossible to send to the

TCP task

16#8018 Either:� Another explicit message for this device is in progress, or� TCP connection or encapsulation session in progress

16#8030 Timeout on the Forward_Open request

Note : The following 16#81xx events are Forward_Open response detected error codes that originate at the remote target and are received via the CIP connection.

16#8100 Connection in use or duplicate Forward_Open

16#8103 Transport class and trigger combination not supported

16#8106 Ownership conflict

16#8107 Target connection not found

16#8108 Invalid network connection parameter

16#8109 Invalid connection size

16#8110 Target for connection not configured

16#8111 RPI not supported

16#8113 Out of connections

16#8114 Vendor ID or product code mismatch

16#8115 Product type mismatch

16#8116 Revision mismatch

16#8117 Invalid produced or consumed application path

16#8118 Invalid or inconsistent configuration application path

16#8119 Non-Listen Only connection not opened

16#811A Target object out of connections

16#811B RPI is smaller than the production inhibit time

16#8123 Connection timed out


NHA31369 07/2015 185

16#8124 Unconnected request timed out

16#8125 Parameter event in unconnected request and service

16#8126 Message too large for unconnected_send service

16#8127 Unconnected acknowledge without reply

16#8131 No buffer memory available

16#8132 Network bandwidth not available for data

16#8133 No consumed connection ID filter available

16#8134 Not configured to send scheduled priority data

16#8135 Schedule signature mismatch

16#8136 Schedule signature validation not possible

16#8141 Port not available

16#8142 Link address not valid

16#8145 Invalid segment in connection path

16#8146 Event in Forward_Close service connection path

16#8147 Scheduling not specified

16#8148 Link address to self invalid

16#8149 Secondary resources unavailable

16#814A Rack connection already established

16#814B Module connection already established

16#814C Miscellaneous

16#814D Redundant connection mismatch

16#814E No more user-configurable link consumer resources: the configured number of resources for a producing application has reached the limit

16#814F No more user-configurable link consumer resources: there are no consumers configured for a producing application to use

16#8160 Vendor specific

16#8170 No target application data available

16#8171 No originator application data available

16#8173 Not configured for off-subnet multicast

16#81A0 Event in data assignment

16#81B0 Optional object state event

16#81C0 Optional device state event

Note : All 16#82xx events are register session response detected error codes.

16#8200 Target device does not have sufficient resources

16#8208 Target device does not recognize message encapsulation header

16#820F Reserved or unknown event from target

Code (hexadecimal) Description


186 NHA31369 07/2015

NHA31369 07/2015 187

Quantum IEC61850

Supported Data Model Items

NHA31369 07/2015


Appendix BSupported Data Model Items

Overview

This chapter describes the items supported by the 140 NOP 850 00 data model.



Topic Page

Logical Nodes 188

Common Data Classes 196


188 NHA31369 07/2015

Logical Nodes

Overview

The 140 NOP 850 00 module supports the logical nodes (LNs) appearing in the following groups.

Group L: System Logical Nodes

Group A: Automatic Control Logical Nodes

Group C: Control Logical Nodes

Name Description

LLN0 Logical node zero

LPHDLN Physical device information

LCCH Physical communication channel supervision

LGOS GOOSE subscription

LTIM Time management

LTMS Time master supervision

Name Description

ACTM Control mode selection

AJCL Joint control

ANCR Neutral current regulator

APSF PSS 4B filter function

APSS PSS control, common information

APST PSS 2A/B filter function

ARCO Reactive power control

ARIS Resistor control

ATCC Automatic tap changer

AVCO Voltage control

Name Description

CALH Alarm handling

CCGR Cooling group

CILO Interlocking

CPOW Point-on-wave switching

CSWI Switch controller

CSYN Synchronizer controller


NHA31369 07/2015 189

Group F: Functional Block Logical Nodes

Group G: Generic Reference Logical Nodes

Group H: Hydropower Specific Logical Nodes

Name Description

FCNT Counter

FCSD Curve shape description

FFIL Generic filter

FHBT Functional heartbeat

FLIM Control function output

FPID PID regulator

FRMP Ramp function

FSCH Scheduler

FSPT Set-point control

FXOT Action at over threshold

FXPS Functional priority status

FXUT Action at under threshold

Name Description

GAPC Generic automatic process control

GGIO Generic process I/O

GSAL Generic security application

Name Description

HBRG Turbine – generator shaft bearing

HCOM Combinator

HDAM Hydropower dam

HDFL Deflector control

HDLS Dam leakage supervision

HEBR Electrical brake

HGOV Governor control mode

HGPI Gate position indicator

HGTE Dam gate

HITG Intake gate

HJCL Joint control


190 NHA31369 07/2015

Group I: Interfacing and Archiving Logical Nodes

HLKG Leakage supervision

HLVL Water level indicator

HMBR Mechanical brake

HNDL Needle control

HNHD Water net head data

HOTP Dam over-topping protection

HRES Hydropower / water reservoir

HSEQ Hydropower unit sequencer

HSPD Speed monitoring

HSST Surge shaft

HTGV Guide vanes (wicket gate)

HTRB Runner blades

HTRK Trash rack

HTUR Turbine

HUNT Hydropower unit

HVLV Valve (butterfly valve, ball valve)

HWCL Water control

Name Description

Name Description

IARC Archiving

IFIR Fire detection and alarm

IHMI Human machine interface

IHND Hand interface

ISAF Safety alarm function

ITCI Telecontrol interface

ITMI Telemonitoring interface

ITPC Teleprotection communication


NHA31369 07/2015 191

Group K: Mechanical and Non-Electric Primary Equipm ent Logical Nodes

Group M: Metering and Measurement Logical Nodes

Group P: Protection Function Logical Nodes

Name Description

KFAN Fan

KFIL Filter

KPMP Pump

KTNK Tank

KVLV Valve control

KHTR Heater, cubicle heater

Name Description

MENV Environmental information

MFLK Flicker measurement name

MHAI Harmonics or interharmonics

MHAN Non-phase-related harmonics or interharmonics

MHYD Hydrological information

MMDC DC measurement

MMET Meteorological information

MMTN Metering single phase

MMTR Metering 3 phase

MMXN Non-phase-related measurement

MMXU Measurement

MSQI Sequence and imbalance

MSTA Metering statistics

Name Description

PDIF Differential

PDIR Direction comparison

PDIS Distance

PDOP Directional overpower

PDUP Directional underpower

PFRC Rate of change of frequency

PHAR Harmonic restraint


192 NHA31369 07/2015

Group Q: Power Quality Logical Nodes

PHIZ Ground detector

PIOC Instantaneous overcurrent

PMRI Motor restart inhibition

PMSS Motor starting time supervision

POPF Over power factor

PPAM Phase angle measuring

PRTR Rotor protection

PSCH Protection scheme

PSDE Sensitive directional earthfault

PTEF Transient earth fault

PTHF Thyristor protection

PTOC Time overcurrent

PTOF Overfrequency

PTOV Overvoltage

PTRC Protection trip conditioning

PTTR Thermal overload

PTUC Undercurrent

PTUF Underfrequency

PTUV Undervoltage

PUPF Underpower factor

PVOC Voltage controlled time

PVPH Volts per Hz

PZSU Zero speed or underspeed

Name Description

Name Description

QFVR Frequency variation

QITR Current transient

QIUB Current unbalance variation

QVTR Voltage transient

QVUB Voltage unbalance variation

QVVR Voltage variation


NHA31369 07/2015 193

Group R: Protection Related function Logical Nodes

Group S: Supervision and Monitoring Logical Nodes

Name Description

RBRF Breaker failure

RDIR Directional element

RFBC Field breaker configuration

RFLO Fault locator

RMXU Differential measurements

RPSB Power swing detection/blocking

RREC Autoreclosing

RSYN Synchronism-check

Name Description

SARC Monitoring and diagnostics for arcs

SCBR Circuit breaker supervision

SFLW Supervision of media flow

SIMG Insulation medium supervision (gas)

SIML Insulation medium supervision (liquid)

SLTC Tap changer supervision

SLVL Supervision of media level

SOPM Supervision of operating mechanism

SPDC Monitoring and diagnostics for partial discharges

SPOS Supervision of the position of a device

SPRS Supervision media pressure

SPTR Power transformer supervision

SSWI Circuit switch supervision

STMP Temperature supervision

SVBR Vibration supervision


194 NHA31369 07/2015

Group T: Instrument Transformer and Sensor Logical Nodes

Group X: Switchgear Logical Nodes

Group Y: Power Transformers Logical Nodes

Name Description

TANG Angle

TAXD Axial displacement

TCTR Current transformer

TDST Distance

TFLW Liquid flow

TFRQ Frequency

TGSN Generic sensor

THUM Humidity

TLVL Media level

TMGF Magnetic field

TMVM Movement sensor

TPOS Position indicator

TPRS Pressure sensor

TRTN Rotation transmitter

TSND Sound pressure sensor

TTMP Temperature sensor

TTNS Mechanical tension / stress

TVBR Vibration sensor

TVTR Voltage transformer

TWPH Water acidity

Name Description

XCBR Circuit breaker

XFFL Switching control for field flashing

XSWI Circuit switch

Name Description

YEFN Earth fault neutralizer (Petersen coil)

YLTC Tap changer

YPSH Power shunt

YPTR Power transformer


NHA31369 07/2015 195

Group Z: Further Power System Equipment Logical Nod es

Name Description

ZAXN Auxiliary network

ZBAT Battery

ZBSH Bushing

ZCAB Power cable

ZCAP Capacitor bank

ZCON Converter

ZGEN Generator

ZGIL Gas insulated line

ZLIN Power overhead line

ZMOT Motor

ZREA Reactor

ZRES Resistor

ZRRC Rotating reactive component

ZSAR Surge arrestor

ZSCR Semi-conductor controlled rectifier

ZSMC Synchronous machine

ZTCF Thyristor controlled frequency converter

ZTCR Thyristor controlled reactive component


196 NHA31369 07/2015

Common Data Classes

CDCs

The 140 NOP 850 00 module supports the following common data classes (CDCs):

CDC Description Information Type

ACD Directional protection activation information Status information

ACT Protection activation information Status information

APC Controllable analogue process value Controls information

ASG Analog setting Analog settings

BAC Binary controlled analog process value Controls information

BCR Binary counter reading Status information

BSC Binary controlled step position information Controls information

CMV Complex measured value Measurment information

CSD Curve shape description Descriptive information

CSG Curve shape setting Analog settings

CURVE Setting curve Analog settings

DEL Phase to phase related measured values of a three-phase system Measurment information

DPC Controllable double point Controls information

DPL Device name plate Descriptive information

DPS Double point status Status information

ENC Controllable enumerated status Controls information

ENG Enumerated status setting Status settings

ENS Enumerated status Status information

HDEL Harmonic value for DEL Measurment information

HMV Harmonic value Measurment information

HST Histogram Status information

HWYE Harmonic value for WYE Measurment information

INC Controllable integer status Controls information

ING Integer status setting Status settings

INS Integer status Status information

ISC Integer controlled step position information Controls information

LPL Logical node name plate Descriptive information

MV Measured value Measurment information

ORG Object reference setting Status settings

RST Operational restriction Hydro-specific information


NHA31369 07/2015 197

SAV Sampled value Measurment information

SEC Security violation counting Status information

SEQ Sequence Measurment information

SPC Controllable single point Controls information

SPG Single point setting Status settings

SPS Single point status Status information

TAG Maintenance and operational tag Hydro-specific information

TSG Time setting group Status settings

VSG Visible string setting Status settings

WYE Phase to ground/neutral related measured values of a three-phase system

Measurment information

CDC Description Information Type


198 NHA31369 07/2015

NHA31369 07/2015 199

Quantum IEC61850

Glossary

NHA31369 07/2015

Glossary

CCID

configured IED description: The SCL file that describes the communication-related part of an instantiated IED within a project. The communication section contains the address of the IED. The substation section related to this IED may be present and, if so, contains project-specific assigned name values.

DDAI

instantiated data attribute: A single data attribute that has been assigned an initial value by the Modicon IEC61850 Configuration Tool, thereby instantiating both the data attribute and its parent data object (DO).

data setA collection of data attributes that can be viewed and transmitted together. Although data sets are related to logical nodes, the member data attributes can originate in different logical nodes and logical devices. Data sets are used to define data collections that form the basis for reporting and logging using buffered report control blocks, unbuffered report control blocks, and GOOSE control blocks.

DOIinstantiated data object: A single data object with one or more data attributes (DAs) that have been assigned an initial value by the Modicon IEC61850 Configuration Tool.

DRS(dual-ring switch) A ConneXium extended managed switch with one of several possible predefined configurations downloaded to it so that it can participate in a Quantum EIO network. A DRS provides 2 RSTP-enabled ring connections, one for the main ring and one for a sub-ring. It also manages QoS, which provides a predictable level of performance for both remote I/O and distributed I/O traffic on the same I/O network.

DRSs require a firmware version 6.0 or later.

EERT

encoder, receiver, transmitter: ERT is a wireless protocol used to automatically read – and transmit data from – utility meters over a short range so utility personnel need not physically enter a premises and manually take readings from each meter.

Glossary

200 NHA31369 07/2015

explicit messagingTCP/IP-based messaging for Modbus TCP . It is used for point-to-point, client/server messages that include both data (typically unscheduled information between a client and a server) and routing information.

FFTP

(file transfer protocol) A protocol that copies a file from one host to another over a TCP/IP-based network, such as the internet. FTP uses a client-server architecture as well as separate control and data connections between the client and server.

GGOOSE

generic object-oriented substation event: A control model defined by the IEC61850 protocol that provides a mechanism for the transfer of event data relating to module status and value settings. GOOSE is a sub-set of the GSE model. As implemented in the 140 NOP 850 00 module, GOOSE is used to publish and subscribe to event data in the form of VLAN transmissions.

HHot Standby

A high-availability control system with a second (standby) PLC that maintains up-to-date system status. If the primary PLC becomes inoperable, the standby PLC takes control of the system.

IICD

IED capability description: A mandatory SCL file used to exchange data from the IED configurator to the system configurator. This file describes the functional and engineering capabilities of an IED type. It contains exactly one IED section for the IED type whose capabilities are described. The IED name shall be TEMPLATE.

IEDintelligent electronic device: An IEC61850 protocol compliant, microprocessor based industrial device incorporating one or more processors with the capability of receiving or sending data/controls from or to an external source (for example, electronic multifunction meters, digital relays, controllers).

Glossary

NHA31369 07/2015 201

IIDinstantiated IED description: An SCL file that contains the configuration data for a single IED in an application. This file must contain the instantiated device description, communication settings, and data type templates. The file may optionally contain a description of LNs bound to the substation object.

LLD

logical device: A collection of a group of functions. Each function is defined as a logical node. A physical device can include one or more LDs. The IEC61850 server includes a root LD named System.

LNlogical node: A specific function of a logical device (LD), defined by a collection of data objects (DOs).

MMAST

A master processor task that is run through its programming software. The MAST task has 2 sections:� IN: Inputs are copied to the IN section before execution of the MAST task.� OUT: Outputs are copied to the OUT section after execution of the MAST task.

MIB(management information base) A virtual database used for managing the objects in a communications network. See SNMP.

PPLC

programmable logic controller. The PLC is the brain of an industrial manufacturing process. It automates a process as opposed to relay control systems. PLCs are computers suited to survive the harsh conditions of the industrial environment.

RRSTP

(rapid spanning tree protocol) A protocol that allows a network design to include spare (redundant) links to provide automatic backup paths if an active link stops working, without the need for loops or manual enabling/disabling of backup links.

Glossary

202 NHA31369 07/2015

SSCD

substation configuration description file: An SCL file containing a detailed description of an entire substation design. It must include sections describing the substation, communication, IED, and data type template. A single SCD file comprises multiple SSD and ICD files.

SNMP(simple network management protocol) Protocol used in network management systems to monitor network-attached devices for events. The protocol is part of the internet protocol suite (IP) as defined by the internet engineering task force (IETF), which consists of network management guidelines, including an application layer protocol, a database schema, and a set of data objects.

SNTP(simple network time protocol) See NTP.

NHA31369 07/2015 203

Quantum IEC61850

Index

NHA31369 07/2015

Index

Symbols{Module_name}_CLIENT_STATE, 121{Module_name}_MODULE_STATE, 122{Module_name}_SERVER_STATE, 120{Module_name}IED_GOOSE, 123

0-9140 CRA 312 00

Modbus diagnostic codes, 157140 CRP 312 00

Modbus diagnostic codes, 157140 NOC 780 00

Modbus diagnostic codes, 157140 NOC 781 00

Modbus diagnostic codes, 157140 NOP 850 00

Modbus diagnostic codes, 157specifications, 19

Aaccess control, 60

Bbaud rate, 59BMX CRA 312 00

Modbus diagnostic codes, 157BMX CRA 312 10

Modbus diagnostic codes, 157breadcrumb navigation, 41

Cclear local statistics, 148clear remote statistics, 149CO_OPER_ANA, 131CO_OPER_BOOL, 129CO_OPER_ENUM, 131

CO_OPER_INT32, 130CO_OPER_INT8, 129CO_OPER_SBO, 128common data classes, 196

Ddata attributes

instantiating, 81data model, 72data objects

instantiating, 81data rate, 59data set

create, 84DDT

{Module_name}_CLIENT_STATE, 121{Module_name}_MODULE_STATE, 122{Module_name}_SERVER_STATE, 120{Module_name}IED_GOOSE, 123CO_OPER_ANA, 131CO_OPER_BOOL, 129CO_OPER_ENUM, 131CO_OPER_INT32, 130CO_OPER_INT8, 129CO_OPER_SBO, 128GOOSE_CB, 128POLLING_CTRL, 132REPORT_CB, 124, 127

detected error codesexplicit messaging, 184MBP_MSTR, 184Modbus TCP, 183TCP/IP, 182

diagnostics, 153Modbus codes, 157, 167

duplexfull, 59half, 59

Index

204 NHA31369 07/2015

Eelementary function

T850_TO_T870, 139T870_TO_T850, 139

elementary function blockNOP850_EVTS, 134

ERT data setsconfiguring, 96

Ethernetsupported frame type, 48

Ethernet port roles, 48explicit messaging, 141

MBP_MSTR, 142Modbus TCP, 145Modbus TCP function codes, 144

explicit messaging detected error codes, 184

Ffirmware

upgrade, 173firmware upgrade, 173frame type

Ethernet II, 48FTP

enabling, 60FTP service

enable/disable, 151

GGeneral window, 43get local statistics, 147get remote statistics, 149GOOSE

publication port, 45GOOSE control blocks

publishing, 92subscribing, 99

GOOSE_CB, 128

HHot Standby

switchover, 171

II/O mapping, 108IEC 61850

edition, 38IEC 61850 client

diagnostic codes, 170enable/disable, 46import IEDs, 103

IEC 61850 servercreate, 66delete, 66enable/disable, 46export, 66

IEDimporting, 103

installation, 27IP address

assigning, 49default, 50

LLEDs, 154

Ethernet ports, 156module, 154network, 154

logical nodes, 188

MMBP_MSTR, 142, 145MBP_MSTR detected error codes, 184memory

explicit data in, 119explicit data out, 119implicit data in, 119implicit data out, 119

memory address, 35Modbus TCP detected error codes, 183

Index

NHA31369 07/2015 205

module description, 16module name, 35

NNOP850_EVTS, 134

PPDU size, 44POLLING_CTRL, 132port mirroring, 50port roles, 48protocols

conformance, 177

QQoS, 58

Rread data, 146read/write data, 150replacing, 28report control blocks

configuring, 87REPORT_CB, 124, 127reset module, 150RSTP, 52

Ssecurity, 60SNMP

enabling, 60SNMP agent, 56SNTP, 53specifications

140 NOP 850 00, 19communication, 21

state management, 118

TT850_TO_T870, 139T870_TO_T850, 139TCP/IP detected error codes, 182toolbar, 40

UUnity Pro

archive application, 63creating project, 31download application, 62upload application, 63

upgradefirmware, 173

Vvariables

located, 117unlocated, 116

Wworkbench, 39write data, 146