Easergy P5

Easergy P5
User Manual
Communication
Version: P5/EN M/11A

05/2019
www.schneider-electric.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and
furnished for informational use only. No part of this guide may be reproduced or
transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), for any purpose, without the prior written permission of
Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as
is" basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
Table of Contents
Safety information and password protection ..........................................5
Introduction ..................................................................................................6
Presentation...............................................................................................6
Protocols Used and Data Exchanged .....................................................6
Architecture ...............................................................................................8
Serial Network Architecture ...................................................................8
Ethernet Network Architectures..............................................................8
Communication Ports................................................................................12
Ethernet Communication Slot ..............................................................12
Serial communication Slot ...................................................................15
Port Hardening Configuration...............................................................16
Communication Protocols........................................................................17
IEC 61850 Communication........................................................................17
Presentation .......................................................................................17
Configuration of IEC 61850 Communication..........................................18
Configuration of GOOSE Communication .............................................33
GOOSE Performance .........................................................................36
Conformance Statements ....................................................................36
DNP3 ......................................................................................................37
Presentation .......................................................................................37
Function Description ...........................................................................37
Data Configuration ..............................................................................48
Data Model of DNP3 ...........................................................................51
IEC 60870-5-101 ......................................................................................53
Presentation .......................................................................................53
IEC 60870-5-101 Configuration............................................................54
Data Model of IEC 60870-5-101 ...........................................................61
IEC 60870-5-103 ......................................................................................63
Presentation .......................................................................................63
IEC 60870-5-103 Configuration............................................................64
Data Model of IEC 60870-5-103 ...........................................................70
Modbus ...................................................................................................72
Presentation .......................................................................................72
Function Description ...........................................................................72
Events ...............................................................................................76
Clock Synchronisation.........................................................................77
Scaling...............................................................................................77
Data Model of Modbus ........................................................................80
Ethernet/IP............................................................................................. 119
Presentation ..................................................................................... 119
Function Description ......................................................................... 122
Ethernet/IP Main Configuration .......................................................... 126
Data Point Configuration ................................................................... 129
Generating an EDS File with eSetup Easergy Pro ............................... 130
Data Model of Ethernet/IP.................................................................. 131
Redundancy Protocols............................................................................ 160
Parallel Redundancy Protocol (PRP) .................................................. 160
High-availability Seamless Redundancy (HSR) ................................... 165
P5/EN M/11A 3
Rapid Spanning Tree Protocol (RSTP) ............................................... 169
Generic Functions for All Redundant Ethernet Modules ....................... 170
Secure Communication with the eSetup Easergy Pro via the Ethernet
Interface ................................................................................................ 171
Network Time Protocol (NTP) ............................................................... 172
A1 Definitions .......................................................................................... 173
Abbreviation........................................................................................... 173
4 P5/EN M/11A
Safety information and password protection
Safety information and password protection

Important information
Read these instructions carefully and look at the equipment to become familiar
with the device before trying to install, operate, service or maintain it. The
following special messages may appear throughout this manual or on the
equipment to warn of potential hazards or to call attention to information that
clarifies or simplifies a procedure.
The addition of this symbol to a "Danger" or "Warning" safety label indicates that an
electrical hazard exists which will result in personal injury if the instructions are not
followed.
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury or
death.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will
result in death or serious injury.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can
result in death or serious injury.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can
result in minor or moderate injury, or equipment damage.
Failure to follow these instructions can result in injury or equipment
damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions can result in equipment damage.
User qualification
Electrical equipment should be installed, operated, serviced, and maintained only
by trained and 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,
installation, and operation of electrical equipment and has received safety training
to recognize and avoid the hazards involved.
Use the password protection feature in order to protect untrained person
interacting with the Easergy P5 protection relay.
P5/EN M/11A 5
Introduction
Introduction
Presentation
The Easergy P5 protection relays have been designed for easy data exchange
and integration in any system architecture with serial links (daisy chain) or
Ethernet.
Protocols Used and Data Exchanged

The protocols for exchange of data are as follows:
• IEC 61850
• Modbus
• DNP3
• IEC 60870-5-101
• IEC 60870-5-103
• Ethernet/IP
The data exchanged is as follows:
Port Ethernet
Protocol IEC 61850 EtherNet/IP sFTP DNP3 Modbus GetSet
Real time data
Measurement ✓ ✓ ✓ ✓ ✓
Alarms and
✓ ✓ ✓ ✓ ✓
status
Controls ✓ ✓ ✓ ✓ ✓
Time-stamped
✓ ✓ ✓ ✓ ✓
events
Logged data
Disturbance
✓
records
Sequence of
✓
event record files
Device management
Setting group
change ✓ ✓ ✓ ✓ ✓
Settings ✓ ✓ ✓
6 P5/EN M/11A
Introduction
Port Serial
Protocol DNP3 Modbus IEC IEC
60870–5–103 60870–5–101
Real time data
Measurement ✓ ✓ ✓ ✓
Alarms and
✓ ✓ ✓ ✓
status
Controls ✓ ✓ ✓ ✓
Time-stamped
✓ ✓ ✓ ✓
events
Logged data
Disturbance
✓
records
Sequence of
event record files
Device management
Setting group
change ✓ ✓ ✓ ✓
Settings ✓
P5/EN M/11A 7
Introduction
Architecture
Serial Network Architecture
This architecture allows the connection of HMI/SCADA to a set of Easergy P5
protection relays using a multi-drop serial communication link with master-slave
communication.
SCADA
Termination
module
Serial
link
F0198
Ethernet Network Architectures

This architecture allows the connection of a set of Easergy P5 protection relays
directly on an Ethernet network.
NOTE: It is possible to mix on the same Ethernet network the IEC 61850
protocol with any one of the 3 other protocols.
This allows to use the Generic Object-Oriented Substation Event (GOOSE)✧
messages between relays together with another protocol for communication to
Supervisory Control and Data Acquisition (SCADA)✧.
It is also possible to connect Easergy P5 protection relays to two different control
systems, using the same Ethernet communication port and IEC 61850 protocol for
one of them and any available protocol for the other one.
Easergy P5 protection relays handle the IEC 61850 station bus, in compliance
with standards IEC 61850-6, 7-1, 7-2, 7-3, 7-4 and 8-1 Edition 1 or Edition 2,
according to configuration.
Other supporting protocols:
• Secured File Transfer Protocol (sFTP)✧ for file transfer
• Simple Network Management Protocol (SNMP)✧ for network management
• Simple Network Time Protocol (SNTP)✧ for time synchronization
• Secured Hypertext Transfer Protocol (HTTPS)✧ for Web HMI
• GetSet is an ASCII protocol used by eSetup Easergy Pro
8 P5/EN M/11A
Introduction
SCADA
Ethernet
switch
Ethernet
switch
Ethernet
switch
F0199
Connections
The Easergy P5 protection relays can be connected to an Ethernet switch using:
• 10/100BASE-T copper wire (radial connection).
• 100BASE-FX multi-mode fiber optic (radial or ring connection).
To optimize system performance, Schneider Electric recommends:
• to build a fault-tolerant communications backbone by implementing a fiber-
optic ring
• to use IEC 61850 compatible managed switches
• to use VLANs for prioritized messages
• to configure meaningful destination MAC address and APPID to enable
network filtering
• to minimize the content of GOOSE datasets
P5/EN M/11A 9
Introduction
Parallel Redundancy Protocol (PRP)

The principle of Parallel Redundancy Protocol (PRP) is to transmit frames in
parallel on two independent network infrastructures: A and B.
The receiving device is in charge of discarding the second (redundant) frame once
it is received.
PRP features a 0 ms recovery time in case of a communication failure, but this
quality is achieved at the cost of a double communication network.
SCADA
Network A Network B
F0200
High-Availability Seamless Redundancy (HSR)

High-availability Seamless Redundancy (HSR) is typically used in ring
architectures.
Frames are transmitted on the ring on both directions and the receiving device
discards the redundant frames.
HSR provide a 0 ms recovery time and is a cheaper alternative compared to PRP.
SCADA
SCADA
F0201
10 P5/EN M/11A
Introduction
Rapid Spanning Tree Protocol (RSTP)

The principle of Rapid Spanning Tree Protocol (RSTP) is to virtually switch off all
links that are not necessary at a given time, changing the meshed topology into a
tree topology.
The main advantage of RSTP is that it is widespread, and works on any network
topology. On the other hand, RSTP may take a considerable time to reconfigure
the network in case of a network failure, which may exceed the requirements of
automations.
SCADA
Ethernet Ethernet
switch switch
Ethernet Ethernet
switch switch
F0415
P5/EN M/11A 11
Introduction
Communication Ports
Ethernet Communication Slot
The Ethernet communication slot can accommodate one of the following options:
• Dual port copper (RJ45) Ethernet module with RSTP redundancy
management.
• Dual port fibre / fiber optic (multimode glass fibre / fiber) Ethernet module with
RSTP redundancy management.
• Dual port fibre / fiber optic (multimode glass fibre / fiber) Ethernet module with
PRP/HSR advanced redundancy management (this option is a double width
module which spans over the serial slot space and is therefore not compatible
with the use of a serial communication module).
Ethernet Port Configuration

The parameters for the port can be set from the front panel, using
COMMUNICATION menu of eSetup Easergy Pro or Web HMI. Different protocols
(Ethernet Protocol 1 and Ethernet Protocol 2) can be used simultaneously - both
protocols use the same IP address and MAC address (but different IP port
number).
12 P5/EN M/11A
Introduction
Table 1 - Ethernet protocol 1 configuration
Parameter Value Description Note
Ethernet port protocol None Select the protocol of the Ethernet port Set
ModBusTcps
DNP3
IEC-61850
EthernetIP
IP port for protocol 1 Set the IP port number of the protocol 1 Set
Set protocol default – Default IP port number can be set Set

IP port Default
ModBusTcps default IP port: 502
DNP3 default IP port: 20000
IEC-61850 default IP port: 102
EthernetIP default IP port: 44818
Message counter Number of messages since the device has Clear

restarted or since last clearing
Error counter Number of protocol interruptions since Clear

device has restarted or since last clearing
Timeout counter Number of timeout interruptions since Clear

device has restarted or since last clearing
IP Select IP1 Choose the Ethernet module to be used 1 Set
IP3
Set = An editable parameter (password needed)

Clear = A resetable parameter (password needed)
1. IP1 means choose the Ethernet module to be used on Slot M; IP3 means choose the Ethernet module to be used on Slot L.
P5/EN M/11A 13
Introduction
Table 2 - Ethernet port configuration
MAC Address Display the MAC address
IP Address n.n.n.n IP address Set

NetMask n.n.n.n Net mask Set
Gateway n.n.n.n Gateway IP address Set
Eth. Port 1 status Link on / Display the connection of Ethernet Port 1
Link off
Eth. Port 2 status Link on / Display the connection of Ethernet Port 2 Set
Link off
Enable HTTPS server Yes / No If this option is enabled, HTTP server can be Set
used
IP select IP1 Choose the Ethernet module to be used by Set
HTTP server 2
IP3
NTP server n.n.n.n Network time protocol server Set
NTP server (backup) n.n.n.n Network time protocol server to be used if Set
NTP server does not respond
IP select IP1 Choose the Ethernet module to be used by Set

NTP server 2
IP3
TCP keepalive interval 0 - 20 s TCP keepalive interval in second Set3
When Ethernet module with PRP/HSR is selected, additional parameters are

shown.
Table 3 - Ethernet port configuration (PRP/HSR)
FPGA version Display the FPGA version of the Ethernet

module
Get mode Display the used protocol
Mode Switch PRP / HSR Switch the protocol to be used Set
2. IP1 means choose the Ethernet module to be used on Slot M; IP3 means choose the Ethernet module to be used on Slot L.
3. Keepalive: The Keepalive parameter sets the time between two keepalive packets in seconds which are sent from the IED. The setting
range for this parameter is between zero (0) and 20 seconds; with the exception that zero (0) means actually 120 seconds (2 minutes).A
keep alive’s packet purpose is for the eSetup Easergy Pro to send a probe packet to a connected client for checking the status of the
TCP-connection when no other packet is being sent, e.g. client does not poll data from the IED. If the keepalive packet is not
acknowledged, the IED will close the TCP connection. Connection must be restarted by the client side.
14 P5/EN M/11A
Introduction
Serial communication Slot

The Serial communication slot can accommodate one of the following options:
• RS485 (two and four wires) serial communication module, with integrated tap
and RJ45 connection.
• Fibre optic serial communication module.
Serial Port Configuration

The parameters for the remote port can be set from the front panel, using
COMMUNICATION menu of eSetup Easergy Pro or Web HMI.
Only one serial port can be used and one serial communication protocol can be
selected.
Table 4 - Serial port configuration
Remote port protocol None Select the protocol of the serial port Set
ModBusSlv
IEC-103
DNP3
IEC-101
Message counter Number of messages since the device has Clear
Error counter Number of errors that have been received Clear

since device has restarted or since last
clearing
Timeout counter Number of timeouts since device has Clear

Set = An editable parameter (password needed)

Clear = A resetable parameter (password needed)
NOTE: Only the Modbus slave protocol can be configured on both remote port
and Ethernet port.
P5/EN M/11A 15
Introduction
Port Hardening Configuration

It is possible to disable a communication port – either via the front panel, using
COMMUNICATION menu of eSetup Easergy Pro or Web HMI with the correct
access rights.
This allows the user to take control of the physical ports limiting the exposure of
ports to only those that are needed.
Figure 1 - Port hardening configuration (various from communication

modules used)
When the ports or the protocols on Ethernet module are disabled or enabled, a
reboot is needed.
16 P5/EN M/11A
Communication Protocols
IEC 61850 Communication
Presentation
IEC 61850 is a standard for communication networks and systems of power utility
automation. Easergy P5 protection relays, used as a server, can be connected to
an IEC 61850 station bus according to Edition 1 and Edition 2 of:
• IEC 61850-6
• IEC 61850-7-1 to 7-4
• IEC 61850-8-1
Based on the Ethernet protocol, the IEC 61850 communication standard helps to
ensure:
• High communication speeds and versatile communication architectures
• Interoperability between manufacturers
Easergy P5 protection relays provide a built-in solution for demanding IEC 61850
applications:
• IEC 61850 logical nodes and configurable data sets to fit the needs of the
Edge control system/SCADA system
• Peer-to peer communication capabilities on Easergy P5 protection relays
using GOOSE messages to enhance the protection and control system
without the need of additional wiring
• Up to 8 simultaneous IEC 61850 client-server associations
The IEC 61850 protocol can be used to read/write static data from the Easergy P5
protection relays, to receive events, to send controls, and to receive/send GOOSE
messages to other relays.
The IEC 61850 server interface is capable of:
• Configurable pre-defined data sets
• Dynamic data sets created by clients, which can be assigned to buffered and
unbuffered Report Control Blocks
• Reporting function with buffered and unbuffered Report Control Blocks
• Supported control models:
◦ Status only
◦ Direct with normal security
◦ Direct with enhanced security
◦ Select before operation with normal security
◦ Select before operation with enhanced security
• Supported horizontal communication with GOOSE
◦ Configurable GOOSE publisher data sets
◦ Configurable filters for GOOSE subscriber inputs (i.e. MAC Address,
APPID....)
• Sending and receiving analogue or binary values over GOOSE
P5/EN M/11A 17
Configuration of IEC 61850 Communication

Configuration Tools
The Easergy P5 protection relays IEC 61850 solution can be configured with:
• eSetup Easergy Pro used as a setting and operating software to help ensure
straightforward configuration and to send IEC 61850 configuration to the
Easergy P5 protection relays
• CET850 software used as configuration tool to adapt the communication
profile of the Easergy P5 protection relays for the precise needs of the system
Configuration Files
The IEC 61850 configuration process uses and generates several types of
System Configuration description Language (SCL)✧ files:
• ICD - IED (Intelligent Electronic Device✧) Capability Description✧
An ICD file exists for each type of Easergy P5 protection relay; a selection is
introduced here. It describes the data model and communication services
available in the referred-to Easergy P5 device model.
ICD files are provided in a library together with the CET850 configuration tool,
and are used as template models in the configuration process.
The ICD files can be gotten from the ICD folder under eSetup EasergyPro or
by the “Export ICD/SCL file” command by eSetup EasergyPro.
• IID - Instantiated IED Description✧
The IID file describes the project-specific configuration of a single IED in a
system.
It is used as an exchange file between the CET850 configuration tool and
other IEC 61850 system configuration tools to exchange the configuration
data of a single IED instantiated specifically for a project.
• CID - Configured IED Description✧
For every configured Easergy P5 protection relays there is a CID file which
describes the IEC 61850 configuration of the device.
A CID file is created by the IED configuration tools. The CID file is then loaded
into the device to configure it.
• SCD - System Configuration Description✧
An SCD file contains the configuration data for the IEC 61850 system
including the communication configuration settings for all related IEC 61850
devices.
18 P5/EN M/11A
eSetup Easergy Pro for IEC 61850 Configuration

The Easergy P5 protection relays setting and operating software, eSetup Easergy
Pro, is used to create and send IEC 61850 configuration to the Easergy P5
protection relay.
eSetup Easergy Pro is used to:
1. Get the information from Easergy P5 protection relays connected to the IEC
61850 network. This can be done automatically by the eSetup Easergy Pro
polling the network to find connected devices (with IP address and port
number).
2. Import a CID file into eSetup Easergy Pro (see eSetup Easergy Pro user
manual).
3. Provide the content of the CID file into Easergy P5 protection relays with
eSetup Easergy Pro.
3 1
IEC 61850 Main Configuration

The IEC 61850 protocol is activated by setting it as the port protocol for an
Ethernet port on the device. This setting can be found by navigating to the
COMMUNICATION menu and Protocol configuration view in the eSetup Easergy
Pro or Web HMI. The edition of IEC 61850 and control model of object 1-6 can be
configured via IEC 61850 main configuration view in the eSetup Easergy Pro or
Web HMI. Number of active connections and IP addresses of client 1-8 can be
monitored.
P5/EN M/11A 19
Table 5 - IEC 61850 main configuration
Parameter Description Note
Edition IEC 61850 standard edition to be used (1 or 2), Edition 2 is the Set
default.
Check upper Defines whether the address parameters of the protocol layers Set
address above TCP/IP (APID etc) are checked or not during the
IEC 61850 connection establishing procedure.
Control model Selects the control model to be used with the controllable Set
Objects.
• Status Only (StatusOnly)
• Direct with normal security (DirNorSec)
• Select before operation with normal security
(SBONorSec)
• Direct with enhanced security (DirEnhSec)
• Select before operation with enhanced security
(SBOEnhSec)
Size of array Number of elements in the arrays used to transfer the Set
harmonics.
Active connections The number of active connections.
Client x The IP addresses of the clients.
20 P5/EN M/11A
IEC 61850 Measurement Configuration

The IEC 61850 measurement configuration of deadband values (primary values)
and unit multiplier settings can be found by navigating to the COMMUNICATION
menu and IEC 61850 measurement configuration view in the eSetup Easergy Pro
or Web HMI.
P5/EN M/11A 21
Table 6 - IEC 61850 measurement configuration
Parameter 4 Description Note
Energy Deadband of the measurements. Set

...
Counters
Integration time Deadband integration time. Set
Unit multiplier Set the unit multiplier of deadband values. Set
There are two variants of the deadband calculation: absolute deadband and
integrated deadband. To select absolute deadbanding, set the integration time to
zero.
NOTE: Too small values may cause unnecessary traffic.
A short example: If the Current I deadband value is set to 5 A, and the Integration
time set to 0 (absolute deadband), the change condition will be satisfied when the
value changes more than 5 A from the previously reported value. If, on the other
hand, the Integration time is set to 1, the change condition will be satisfied for
instance, if the signal value changes more than 1 A from the previously reported
value and remains as such for five seconds.
In case there are several changes during the time period set (report buffer time >
0), the integration time is not considered and the analogue value of the pending
previous event is overwritten. The behavior can refer to Conformance Statements,
page 36 in this doc. Mechanism on second internal data change notification of the
same analogue data value within buffer period (see IEC 61840-7-2 Ed.1 §14.2.2.9
and IEC 61850-7-2 Ed.2 §17.2.2.9 respectively): Replace analogue value in
pending report.
IEC 61850 BRCB Configuration

The 8 BRCB lost reports count can be configured by navigating to the
COMMUNICATION menu and IEC 61850 BRCB configuration view in the eSetup
Easergy Pro or Web HMI.
Table 7 - IEC 61850 BRCB configuration
BRCBx Lost Number of reports that were overwritten before sending. It is Set
reports count separate for each BRCB.
4. These parameters can be set for each individual measurement.
22 P5/EN M/11A
IEC 61850 Datasets

The information of IEC 61850 datasets can be found by navigating to the
COMMUNICATION menu and IEC 61850 datasets view in the eSetup Easergy
Pro or Web HMI.
Table 8 - IEC 61850 datasets
Parameter Description
Name Name of the dataset

Type Type of the dataset (BuiltIn / Persist / NonPers)
IEC 61850 Variable The data that included in the dataset

FC Functional constraint of the data
IEC 61850 Generic Events

These generic events can be configured via navigating to the COMMUNICATION
menu and IEC 61850 generic events view in the eSetup Easergy Pro or Web HMI.
This provides means to map any events (i.e. protection trip, digital input change,
port hardening change, ...) of the relay to maximum 8 indication data objects of the
P5EVTGGIO1 logical node of the IEC 61850 interface. The status of the indication
data object will be determined by ON and OFF events set for the corresponding
index.
Table 9 - IEC 61850 generic events
Ind idx Index of the LN P5EVTGGIO1 indication
ON event channel Channel number of the ON event Set

ON event code Event code of state ON Set
OFF event channel Channel number of the OFF event Set
OFF event code Event code of state OFF Set
P5/EN M/11A 23
The above screenshot features an example, where the status of Virtual Input 1
(event channel 69) is mapped to the generic events table. If the value of Virtual
Input 1 is changed, then the value stored in the IEC 61850 address
P5EVTGGIO1.Ind1stVal will indicate the current value of Virtual Input 1.
If only an “ON event” is defined for an indication then the transition to OFF state is
generated automatically after reporting the ON state (momentary ON state). And
the same applies if only an “OFF event” is defined for an indication (momentary
OFF state).
GOOSE Configuration
The publisher configuration GoCB 1-4 and subscriber configuration can be found
by navigating to the COMMUNICATION menu and GOOSE configuration view in
the eSetup Easergy Pro or Web HMI.
Table 10 - GOOSE configuration
Publisher configuration GCB x
Enable Enable/disable the publishing of data defined by GCB x. Set
Name of selected Display the name of the dataset associated to the GCB x. Set
Dataset
Needs A flag which can be used to indicate that some change has Set
Commissioning been done in the configuration and a new commissioning is
needed.
DI for simulation Select the digital input for simulation mode. When this DI is Set
mode TRUE, the GOOSE message is in simulation mode.
Simulation mode Indicates the test (Ed1) / simulation (Ed2) parameter value in Set
GOOSE publish message
No: normal operation
Yes: test / simulation mode
Fixed length Disable/enable sending the GOOSE messages in flexible or Set
GOOSE fixed format (fixed length is a feature defined by Edition 2).
Subscriber configuration
Min supervision time Minimum timeout for indicating invalid status of GOOSE Set
Network Inputs due to no incoming GOOSE messages
(exceeded supervision time or time allowed to live from the last
GOOSE message, whichever is greater).
24 P5/EN M/11A
GOOSE Subscriber: Data Points

The GOOSE subscriber 128 binary data and 8 analog data can be monitored by
navigating to the COMMUNICATION menu and GOOSE Subscriber: data points
view in the eSetup Easergy Pro or Web HMI.
Table 11 - GOOSE Subscriber: data points
GOOSE NI Global Error Global error status of GOOSE NI /ANI

NI Index of GOOSE Network Input for the received GOOSE data point
(can be binary or analog). Binary NIs can be used as inputs for the
user-defined logic blocks or as control inputs in the other functions of
the relay (e.g. the output matrix). Analogue NIs (Virtual Analog
Inputs) can be used as coupling in programmable stages.
Value Data value received in the GOOSE data packet
Status Status of the GOOSE data (NO DATA / OLD / OK)
VAI Unit Unit of the incoming analogue data
P5/EN M/11A 25
CET850 for IEC 61850 Configuration

IEC 61850 configuration software CET850 is used to create, display, modify or
optimize an IEC 61850 configuration.
.cid
.iid
.icd
1 1 1
template library
5
1
CET850
.scd
.icd 2
3
6 2 2
2 4
eSetup
.icd .cid Easergy Pro
.iid
user customized ICD
The CET850 can be used to:

1. Create an IEC 61850 configuration using an ICD, IID or CID file as an input.
2. Edit an existing CID, SCD, IID or user-customized ICD file to modify its
contents by :
• Adding or removing Easergy P5 protection relays
• Displaying the configuration
• Modifying communication parameter values
• Optimizing configuration by creating or modifying Datasets and Report
Control Blocks
• Configuring or optimizing the GOOSE communication by creating or
modifying the GOOSE messages production and subscription
3. Generate user-customized ICD file using Easergy P5 protection relays IED
template from the factory ICD library.
4. Generate a CID file for storing the configuration of one device which can then
be imported to the Easergy P5 protection relays using eSetup Easergy Pro.
5. Generate SCD file for storing the configuration of an IEC 61850 system which
can then be used by other IEC 61850 configuration tools.
6. Generate an IID file for storing the specific configuration of an instantiated
IED which can then be used by other IEC 61850 system configuration tools.
Graphical SCL Editor

CET850 is a graphical tool that enables to browse an SCL file using a tree view
that displays the content of the file in a hierarchical format.
26 P5/EN M/11A
Tree View
The following main sections are displayed in the tree view:
• Header and History
The Header section identifies the SCL configuration file and its version.
• Communication
This section contains the definition of all sub-networks defined in the IEC
61850 system, with the list of the connected IEDs. Both Client/Server and
Peer-to-Peer communication access points are displayed.
• List of IEDs
This section contains the definition of all IEDs defined in the IEC 61850
system. Each IED is displayed with all its contents:
◦ Logical Devices (LD) ✧
◦ Logical Nodes (LN) ✧
◦ Datasets (DS) ✧
◦ Report Control Blocks (RCB) ✧
◦ GOOSE Control Blocks (GoCB) ✧
◦ Subscription
Property View
When an item is selected in the tree view, the property view displays details of the
selected item. You can activate editing operations from the tool bar and contextual
menu. There are also specific dialogue interfaces to guide you.
Device Configuration
Adding and removing a device in an IEC 61850 system consists of making the
change in the associated SCD file.
Adding an IED
CET850 enables the addition of an IED to an IEC 61850 system using its ICD
description file, or the addition of a device already defined by a CID file. As pecific
dialog interface requests a name for the IED and then its description. The
description is provided from an ICD file, a CID file or from an IID file.
Procedure:
• Create a new SCL file for a substation system (e.g. My Substation.scd).
• From the tree view, select the SCL root element
• In the menu bar or in the contextual menu, click Add > IED
• Set the IED Identification and optionally the Address parameters according to
the following descriptions
• Click OK to validate the operation
IED Identification:
• ICD/CID file:
Select IEC 61850 description of the IED to add by an ICD, a CID. User can
select a device from library or other device with ICD file.
• IED name:
Assign a name to the IED. The name of the IED is unique in the IEC 61850
system. Its length is restricted to a maximum of 64 characters, and consists of
alphanumeric and underscore (_) characters, beginning with a letter.
• IED description:
This is a free ASCII string where the user can write comments about the
device.
P5/EN M/11A 27
Address:
Address parameters are set to connect to the IED in the communication network.
Connecting the IED can be done at this stage or later using the Add > Connected
Access Point menu.
Removing an IED
An IED can be removed from an SCD file. This function is available when an IED
is selected in the tree view. After confirming that the IED is to be deleted, the tree
view and the content of the SCD file are updated.
Connecting Device in IEC 61850
An IEC 61850 IED uses an Access Point (AP)✧ to communicate. This AP is
connected to a subnetwork. CET850 provides the following set of functions to
manage the communication architecture of an IEC 61850 System:
• Adding or removing a Subnet to the system
• Adding or removing an Access Point on a Subnet
28 P5/EN M/11A
IED Configuration
The configuration of an IED described in an ICD, CID or SCD file can be modified
so that its communication profile and behavior are adjusted to the needs of the
system. Refer to the CET850 user manual for more information.
Create, modify or delete Dataset
With the Easergy P5 protection relay, a dataset is a collection of references to
Data Attributes (DA) grouped together to increase communication efficiency for
reports and GOOSE messages.
Datasets can be modified by the user and new Datasets can be added, depending
on the capabilities of the IED.
CET850 provides an easy way to create or edit a Dataset inside LLN0. When
creating a Dataset, CET850 prompts user for its name and description. A specific
dialog interface allows the user to select which data is to be added to, or removed
from the Dataset.
The available data that can be selected is displayed in a hierarchical tree with
collapse and expand facilities, from their host Logical Node up to their final
attributes. Individual and multiple selections are possible.
After completing the definition of the Dataset in the dialog interface, the changes
to the Dataset are reflected in the current SCL file and the CET850 display is
updated: A newly created Dataset is displayed in the tree view and a deleted
Dataset is removed from the tree view. The content of the Dataset is updated in
the property view.
Modify Report Control Block (RCB)

Easergy P5 protection relays provide both 8 buffered and 8 unbuffered RCBs
inside LLN0.
CET850 provides a specific dialog interface for creating or modifying a Report
Control Block. When creating an RCB, CET850 prompts user for the name and
description of the RCB. A specific dialog interface allows the user to select the
Dataset to be associated with the RCB and to define all settings concerning the
way the report is generated.
The most common trigger options to define an RCB are:
• Data Change : the Report is triggered by changes to the data
• Quality Change: the Report is triggered by quality changes
• Integrity: the Report is triggered periodically, according to an Integrity period
specified
P5/EN M/11A 29
Modify GOOSE Control Block (GoCB)

The GOOSE message service is an efficient real-time communication service for
peer-to-peer exchanges between IEDs.
A GOOSE Control Block (GoCB) manages how information referenced in a
Dataset is transmitted in a GOOSE message. A GoCB can only be created inside
the Logical Node 0 (LLN0).
By default, each Easergy P5 protection relay provides up to 4 GoCB, which need
to be defined in the LLN0.
CET850 provides a specific dialog interface for modifying a GOOSE Control
Block. A specific dialog interface allows the user to select the Dataset whose
referenced information shall be transmitted as a GOOSE message. Then, the user
needs to enter the settings for publishing the GOOSE message.
This includes:
• Multicast address the GOOSE message transmitted to
• Time for the first retransmission of the GOOSE message (the fastest
retransmission is after 6 ms)
• Maximum retransmission interval (heartbeat cycle time)
After completing the definition of the GoCB in the dialog interface, the changes to
the GoCB are reflected in the current SCL file and the CET850 display is updated:
A newly created GoCB is displayed in the tree view and a deleted GoCB is
removed from the tree view. The GoCB settings are displayed in the property view.
30 P5/EN M/11A
Subscribe to GOOSE messages and assign GOOSE inputs

The capability of the Easergy P5 protection relay to receive GOOSE messages is
defined in the ICD file. If GOOSE messages are to be subscribed to, a GOOSE
Receive element is defined at the beginning of the IED section, in the tree view
displayed by CET850.
Editing the GOOSE Receive element allows the user to:
• Select the GOOSE messages and the data to which the IED subscribed
• Assign the subscribed data to Easergy P5 protection relays GOOSE inputs
CET850 provides a specific dialog interface to edit the GOOSE Receive. The
dialog is organized in two parts:
• GOOSE message and data subscription
• GOOSE Inputs assignment
Refer to Configuration at Subscriber Side, page 34 for detailed configuration.
Generating, Editing, Validating an SCL file

Generating CID files
When an SCD file is open, CET850 can generate the CID file of a specific IED or
all the CID files for all IEDs defined in the SCD file.
Generating a CID file is available when an IED is selected from the tree view and if
this IED is connected to a subnet. A specific dialog interface box asks the user to
enter the location and the name of the output CID file. By default, the name of the
CID file is based on the name of the IED.
Generating all CID files is available if the SCD file includes at least one IED that is
connected to a subnet. A specific dialog interface box asks the user to enter the
location of the output CID files. The name of each CID file is based on the name of
the IED.
Editing a CID file
CET850 allows the editing of an existing CID file. This CID file is an advanced
configuration file generated during a previous use of CET850, or a standard
configuration file generated by eSetup Easergy Pro.
P5/EN M/11A 31
Validating an SCL file

The validate function includes two kinds of verification:
• Verification of the structure and content of the SCL file
The System Configuration description Language is based on Extensible
Markup Language (XML)✧. The structure and the content of an SCL file is
fully specified by the IEC 61850 standard using an XML Schema (XSD files).
CET850 is delivered with the set of XSD files defined by the IEC 61850
standard. Using the XercesTM parser, CET850 checks the validity of SCL
files against the IEC 61850 XML Schema.
• Verification of the consistency of the GOOSE communication.
The following checks are made:
◦ The Dataset defined for a GOOSE messages meets a specific size
constraint.
◦ The data sent by a publishing IED is consistent with the data expected and
subscribed by the subscribing IED.
CET850 provides two ways to validate an SCL file:
• Schema validation
• Validation at file saving
Automatic validation is enabled or disabled using a specific option in the CET850
User Preferences.
32 P5/EN M/11A
Configuration of GOOSE Communication

To configure the GOOSE communication, the following software are used:
• CET850 software to configure GOOSE communication in the IEC 61850
system
• eSetup Easergy Pro software to assign GOOSE Inputs to Easergy P5
protection relays control and monitoring functions for the precise needs of the
system
Configuration at GOOSE Publisher Side

Configuring GOOSE communication involves first configuring the publisher that
sends the messages and then the subscriber that receives the message. The
GOOSE communication configuration is saved in an SCD file.
Procedure
Configure a GOOSE Control Block to define the publishing of the Dataset as a
GOOSE message on the communication network.
There are no specific output variables for GOOSE communication and any data
produced by Easergy P5 protection relays maybe put into a Dataset to be sent via
a GOOSE message. Nevertheless, only data from the following types are relevant
for GOOSE communication between Easergy P5 protection relays devices: Single
Point Status (SPS) and Double Point Status (DPS).
Any Dataset may be attached to a GOOSE Control Block provided its size is
compatible with the size of one Ethernet frame. When creating a Dataset, CET850
calculates the size of the Dataset and informs the user if it is GOOSE compatible
or not. When creating a GOOSE Control Block, CET850 allows the selection of
GOOSE compatible Datasets only.
P5/EN M/11A 33
Configuration at Subscriber Side
Procedure
1. Select from the published GOOSE messages which Data Attributes (DAs)✧,
page 173 / Data Objects (DOs)✧, page 173 the device shall subscribe to.
2. Assign subscribed DAs/DOs to GOOSE Inputs.
The Easergy P5 protection relay provides 128 GOOSE inputs and 8 analogue
inputs that can be used by control logic functions.
Assignment table
The subscribed DAs are assigned to Easergy P5 protection relays GOOSE inputs
in an assignment table. The assignment table gives in rows the list of all the
subscribed DAs and in column the list of the Easergy P5 protection relays GOOSE
inputs to which the DAs can be assigned/de-assigned. Assignment/de-assignment
is done by selecting the appropriate cells in the table. Several DAs can be
assigned to the same GOOSE input. In this case, Easergy P5 protection relays
apply a wired-OR logic operation to these DAs.
34 P5/EN M/11A
GOOSE Matrix
All Easergy P5 protection relays GOOSE inputs NI 1-128 can be mapped to NI or
Vitual inputs VI 1-20 in COMMUNICATION menu and GOOSE matrix view in
eSetup Easergy Pro or Web HMI.
P5/EN M/11A 35
GOOSE Performance
According to IEC 61850-5 and IEC 61850-10 Edition 2, the GOOSE Performance
of Easergy P5 protection relays is compliant with Class P2 (< 10 ms). For more
information, visit www.schneider-electric.com.
Conformance Statements
This chapter lists the standardized documents stating the conformity with IEC
61850 Edition 1 and Edition 2. It does not describe the standard itself, but only the
choices that have been made in the Easergy P5 protection relays implementation
of the standard, in terms of services, modeling, exceptions, extensions and
adaptations.
The conformance statement is made up of the following documents:
• Protocol Implementation Conformance Statement (PICS)✧:
Describes choices made in protocol implementation.
• Model Implementation Conformance Statement (MICS)✧:
Describes how the information model is implemented.
• Protocol Implementation Extra Information for Testing (PIXIT)✧:
Gives any additional implementation specific information not found in the
previous standardized documents. Despite the name, this information is
useful for operation of the devices.
• Tissues Conformance Statement (TICS)✧:
Describes which Technical Issues (TISSUES) are considered in the device
implementation.
36 P5/EN M/11A
DNP3
Presentation
DNP3 communication enables Easergy P5 protection relay units to be connected
to a supervisor or other device featuring a DNP3 communication channel.
Communication is based on the master/slave principle:
• Easergy P5 protection relay is always a slave device.
• The master is the supervisor, which is another device.
The DNP3 protocol specifies the coding of data and the rules for exchanging this
data between a slave device and a master device (supervision and control device
or RTU). DNP3 is an open (non-proprietary) protocol, which can be implemented
by any communicating device without any restrictions.
The DNP3 protocol was developed from the basic standards prepared by IEC
Technical Committee 57 (Power systems management and associated
communications).
DNP3 was chosen by IEEE Task Force C.2 as the IEEE Recommendation for
communication between RTUs and IEDs.
For more information on the Intelligent Electronic Device protocol can be obtained
from the DNP3 User Group (www.dnp.org).
The following data types from the DNP3 protocol are supported:
• Binary input
• Binary input change
• Double-bit input
• Binary output
• Analog input
• Counter
Easergy P5 protection relays also support the division of data into classes.
Function Description
Transmission Mode
Easergy P5 protection relays can communicate using DNP, in two transmission
modes:
• Serial port mode
• TCP/IP mode
The maximum number of clients for DNP3 is 1. The client and master can be
connected by either:
• a serial port connection
• a TCP connection via an Ethernet port
The Easergy P5 protection relays can only support one transmission mode at a
time.
Status Polling
Easergy P5 protection relays allow the polling of current status values on master
request with class 0.
The contents of binary input for polling, group number and variation number are
configurable.
The function code for polling is 1 [READ].
P5/EN M/11A 37
Status Reporting
Easergy P5 protection relays allow the reporting of data change events which are
derived from:
• Polled value status change
• Control command status change
The status to be reported is configurable.
The event class can be configured as class 1, class 2 or class 3.
Status report entries are stored in a circular buffer with access provided to the
most recent ones.
It is possible for a master to query the availability of status reports, in order that the
master can determine whether it is necessary to read the available status reports
from the slave.
Easergy P5 protection relays may be configured to support unsolicited responses.
Measurement Polling
Easergy P5 protection relays support the polling of static measurement values on
master request with class 0.
The list of measurement values for polling, group number and variation number
are configurable.
The function code for polling is 1[READ].
The data type of each measurement value is configurable.
Measurement Event Polling (Reporting)

Easergy P5 protection relays support the polling of measurements event values
on master request.
The list of measurement event values for polling is configurable.
The data type of each measurement event value is configurable.
The deadband values for managing measurement events reported by Easergy P5
protection relays are configurable.
Remote Control
Easergy P5 protection relays support both remote control command requests and
polling command status requests from a master.
Remote control command requests can be used with data types: binary output.
The remote control commands supported are listed below:
• Select
• Operate
• Direct operate
• Direct operate with no ACK
Both DC (Direct Control) and SBO (Select Before Operate) control models are
supported. The DNP3 checks whether the point to be controlled has been
configured only. DNP3 doesn't check whether the value is correct or not.
Easergy P5 protections relays implement an SBO timeout of 60s.
Easergy P5 protection relays send response frame to client according to the real
control command response.
38 P5/EN M/11A
Counter Management
Easergy P5 protection relays support the polling of counter values on master
request.
The list of the counter values for polling is configurable.
General Interrogation
The general interrogation functions for Easergy P5 protection relays mean to poll
class 0 data for DNP3 master.
When Easergy P5 protection relays receive the general interrogation command
from DNP3 master, the Easergy P5 protection relays report all the point’s static
data values (except for the point’s class is not assigned to one of the four classes)
in one frame or multi-frame.
Generally, the group number 60 and variation number 1 is used for general
interrogation for all profiles.
Time Synchronisation
The time of Easergy P5 protection relays corresponds to Universal Coordinated
Time (UTC).
Easergy P5 protection relays support time synchronization command requests
and the polling of current date & time information from a DNP3 master.
It's possible for master to verify the correctness of system time.
The function code for actioning the time synchronization command is 2 [WRITE].
The function code for polling the current date & time information is 1 [READ].
The time synchronization procedure for TCP and serial is different.
Easergy P5 protection relays do not retry time synchronization messages at either
the Application or Data Link layers for these application layer function codes.
• DELAY_MEASURE request from master and corresponding response
• (RESPONSE function code) from outstation.
• WRITE requests from master with an Absolute Time object, group 50,
variation 1.
When Easergy P5 protection relays detect that the time synchronization request
has not been received within the configured timeout, the IIN1.4 [NEED_TIME] bit
is set in the response message. The master must send the time synchronization
request after receiving a response with this bit set.
Application Identifier
The application identifier uses the function code 16[INITIALIZE_APPL], 17
[START_APPL], 18[STOP_APPL].
When Easergy P5 protection relays receive a request related with application
identifier, nothing internally is performed.
Cold Restart and Warm Restart

When an Easergy P5 relay receives a cold or warm restart request, it immediately
triggers the cold/warm restart sequence. A response frame containing the Delay
Time DNP3 object, with a value of 10 seconds is generated. The response
indicates the time when the relay will become available again. Hence during this
period the Easergy P5 relay does not respond to requests from the DNP3 client.
P5/EN M/11A 39
Device Profile Document

The following tables show the device profile of a DNP3 slave.
DNP 3.0
Vendor Name: Schneider Electric
Device Name: Easergy P5 Protection Relay
Highest DNP Level Supported: Device Function:
For Requests: Level 2 Master
For Responses: Level 2 ✓ Slave
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the
complete list is described in the DNP Implementation table):
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted: 2048
Received: 292 Received: 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None None
Fixed ✓ Configurable
✓ Configurable from 0 to 255
Requires Data Link Layer Confirmation:

Never
Always
Sometimes
✓ Configurable with confirmation type selector, default NO ACK
Requires Application Layer Confirmation:

Never
Always
Sometimes
✓ When reporting Event Data (Slave devices only)
✓ When sending multi-fragment responses (Slave devices only)
Sometimes
✓ Configurable as: “Only when reporting event data”, or “When reporting event data
or multi-fragment messages.”
Timeouts while waiting for:
Data Link Confirm: None Fixed at Variable ✓ Configurable
Complete Appl. Fragment: ✓ None Fixed at Variable Configurable
Application Confirm: None Fixed at Variable ✓ Configurable
Complete Appl. Response: ✓ None Fixed at Variable Configurable
40 P5/EN M/11A
DNP 3.0
Vendor Name: Schneider Electric
Device Name: Easergy P5 Protection Relay
Sends/Executes Control Operations:
WRITE Binary Outputs ✓ Never Always Sometimes Configurable
SELECT/OPERATE Never ✓ Always Sometimes Configurable
DIRECT OPERATE Never ✓ Always Sometimes Configurable
DIRECT OPERATE – NO ACK Never ✓ Always Sometimes Configurable
Count > 1 ✓ Never Always Sometimes Configurable

Pulse On Never ✓ Always Sometimes Configurable
Pulse Off Never ✓ Always Sometimes Configurable
Latch On Never ✓ Always Sometimes Configurable
Latch Off Never ✓ Always Sometimes Configurable
Queue ✓ Never Never Sometimes Configurable

Clear Queue ✓ Never Never Sometimes Configurable
Reports Binary Input Change Events when no specific Reports time-tagged Binary Input Change Events when no
variation requested: specific variation requested:
Never Never
Only time-tagged ✓ Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
✓ Configurable to send one or the other Configurable
Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:
Never ✓ Never
✓ Configuration When Device Restarts
Only certain Objects When Status Flags Change
Sometimes
✓ ENABLE/DISABLE UNSOLICITED
No other options are permitted.
Function codes supported
Default Counter Object/Variation: Counters Roll Over at:
No Counters Reported No Counters Reported
Configurable Configurable
✓ Default Object: 20 ✓ 16 Bits, but roll-over bits not used
✓ Default Variation : 1 32 Bits
Point-by-point list attached Other Value:____
Point-by-point list attached
Sends Multi-Fragment Responses:
✓ Yes
No
Configuration
P5/EN M/11A 41
Implementation Table
REQUEST RESPONSE
DNP OBJECT GROUP & VARIATION (Master may issue (Master parses
Outstation parses) Outstation may issue)
Function Qualifier Function Qualifier
Group Var
Description Codes Codes Codes Codes
Num Num
(dec) (hex) (dec) (dec)
00, 01 (start-stop)
1 0 Binary Input – Any Variation 1 (read)
06 (no range, or all)
00, 01 (start-stop)
1 1 Binary Input – Packed format 1 (read) 129 (response) 00, 01, 17,28
00, 01 (start-stop)
1 2 Binary Input – With flags 1 (read) 129 (response) 00, 01, 17,28
2 0 Binary Input Event – Any Variation 1 (read)
07, 08 (limited qty)
06 (no range, or all) 129 (response)
2 1 Binary Input Event – Without time 1 (read) 17, 28 (index)
07, 08 (limited qty) 130 (unsol. resp)
2 2 Binary Input Event – With absolute time 1 (read) 17, 28 (index)
3 0 Double-bit Binary Input – Any Variation 1 (read) 00, 01, 06
3 1 Double-bit Binary Input – Packed format 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
3 2 Double-bit Binary Input – With flags 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
4 0 Double-bit Binary Input – Any Variation 1 (read) 00, 01, 06
Double-bit Binary Input Event 06 (no range, or all) 129 (response)

4 1 1 (read) 17, 28 (index)
– Without time 07, 08 (limited qty) 130 (unsol. resp)
Double-bit Binary Input Event 06 (no range, or all) 129 (response)
4 2 1 (read) 17, 28 (index)
– With absolute time 07, 08 (limited qty) 130 (unsol. resp)
10 0 Binary Output – Any Variation 1 (read) 00, 01, 06
10 2 Binary Output – Output status with flags 00, 01, 06 129 (response) 00, 01, 17, 28
3 (select)
Binary Command 4 (operate)
12 1 00, 01, 17, 28 129 (response) 00, 01, 17, 28
– Control relay output block (CROB) 5 (direct op)
6 (dir. op, no ack)
20 0 Counter – Any Variation 1 (read) 00, 01, 06
20 1 Counter – 32-bit with flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
20 2 Counter – 16-bit with flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
20 5 Counter – 32-bit without flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
20 6 Counter – 16-bit without flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
42 P5/EN M/11A
REQUEST RESPONSE
DNP OBJECT GROUP & VARIATION (Master may issue (Master parses
Outstation parses) Outstation may issue)
Function Qualifier Function Qualifier
Group Var
Description Codes Codes Codes Codes
Num Num
(dec) (hex) (dec) (dec)
30 0 Analog Input – Any Variation 1 (read) 06 (no range,or all)
30 1 Analog Input – 32-bit with flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
30 2 Analog Input – 16-bit with flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
30 3 Analog Input – 32-bit without flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
30 4 Analog Input – 16-bit without flag 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
30 5 Analog Input – Short float 1 (read) 00, 01, 06 129 (response) 00, 01, 17, 28
32 0 Analog Input Event – Any Variation 1 (read)
32 1 Analog Input Event – 32-bit without time 1 (read) 17, 28 (index)
32 2 Analog Input Event – 16-bit without time 1 (read) 17, 28 (index)
32 3 Analog Input Event – 32-bit with time 1 (read) 17, 28 (index)
32 4 Analog Input Event – 16-bit with time 1 (read) 17, 28 (index)
6, 7, 8 129 (response)
32 5 Short Float Ana. Change Ev. without Time 1 17, 28 (index)
130 (unsol. resp)
50 0 Time and Date 1 (read) 06, 07, 08 129 (response) 17, 28
1 (read) 06, 07, 08 129 (response) 17, 28
50 1 Time and Date – Absolute time
2 (write) 07, 08 129 (response)
07 (limited qty)
52 2 Time Delay – Fine 23 07 129 (response)
(qty = 1)
60 0 Class Objects – Class 0, 1, 2, 3 1 (read) 06
60 1 Class Objects – Class 0 data 1 (read) 06 (no range,or all)
60 2 Class Objects – Class 1 data 1 (read) 06 (no range, or all)
00 (start-stop)
80 1 Internal Indications – Packed format 2 (write) 129
index=7
90 1 Application Identifier 16, 17, 18 0 129

No Object (function code only) 13 (cold restart)
No Object (function code only) 14 (warm restart)
P5/EN M/11A 43
Supported Function Codes

The table below is the application layer function codes that DNP3 slave supported.
Code Function Description Supported

Transfer function codes
Message fragment confirmation
0 Confirm Yes
No response
Request objects from outstation
1 Read Yes
Response with requested objects
Store specified objects to outstation
2 Write Yes
Respond with status of operation
Control function codes
Select output point of outstation
3 Select Yes
Respond with status of control point
Set output that has previously selected
4 Operate Yes
Set output directly
5 Direct operate Yes
Set output directly
6 Direct operate Yes
No response
Freeze function codes
Copy specified objects to freeze buffer
7 Immediate freeze No
Copy specified objects to freeze buffer
8 Immediate freeze No
No respond
Copy specified objects to freeze buffer and clear objects
9 Freeze and clear No
Freeze and clear Copy specified objects to freeze buffer and clear objects
10 No
-NO ACK No respond
Copy specified objects to freeze buffer at specified time
11 Freeze with time No
Freeze with time Copy specified objects to freeze buffer at specified time
12 No
-NO ACK No respond
44 P5/EN M/11A
Code Function Description Supported

Application control function codes
Perform desired reset sequence
13 Cold restart Yes
Respond with a time object
Perform desired partial reset operation
14 Warm restart Yes
Respond with a time object
Ready the specified application to run
16 Initialize application No
Start the specified application to run
17 Start application Yes
Stop the specified application to run
18 Stop application Yes
Configuration function codes
Save configuration
19 Save configuration No
Enable unsolicited messages
20 Enable unsolicited messages Yes
Disable unsolicited messages
21 Disable unsolicited messages Yes
Assign specified objects to a class
22 Assign class No
Time synchronization function codes
23 Delay measurement Perform propagation delay measurement Yes
24 Record current time For LAN networks only No
File transfer
25 Open file No
26 Close file No
27 Delete file No
28 get file information No
29 Authenticate file No
30 Abort file No
31 Activate configuration No
Response function codes

0 Confirm Message fragment confirmation Yes
129 Response Response to request message Yes
130 Unsolicited message Spontaneous message without request Yes
P5/EN M/11A 45
Configuration Parameters
Parameter Value Description

1200, 4800, 9600,
Bit rate 19200, 38400, The communication speed, bits per second.
57600, 115200 bps
Parity None, Even, Odd The type of parity bit used.
Wire number 2, 4 The wires number for serial port.
Poll line False, True Polarized line.
Specifies the amount of time (calculated by bits)

Frame Gap 10…500
to determine that a frame has been completed.
Slave unit 1…65519 The address of the device (slave address).
Master unit 1…65534 The address of the master.
Linklayer 0 ms Link layer confirmation disabled.
Confirmation Timeout 1…65535 ms Timeout for link layer confirmation.
Linklayer Retry Count 1…255 Link layer retries if Link layer confirmation is enabled.
Appl.layer
0…65535 ms Timeout for application layer confirmation.
Confirmation Timeout
Confirmation requested for application layer messages containing
Appl.layer EvOnly
event information only.
Confirmation Mode All Confirmation requested for all application layer messages.
Double-Bit Input If double-bit inputs are not supported by the master, setting this to
No, Yes
Support No will disable them.
0 Clock synchronisation is requested only at startup.

ClockSync Mode
1…64000 s Interval for clock synchronisation request.
Integer variation carries values with same precision as float variation.
Float precision No
(i.e. voltage 230.4 V as integer: 2304, as float: 2304.0)
Float variation has bigger precision than integer variation.
enable flag Yes
(i.e. voltage 230.4V as integer: 230, as float: 230.4)
Deadband Disabled No deadband, no AI events generated.
calculation method Fixed An Event is generated when the AI value change exceeds given deadband.
Integrated Integrating deadband used.
Deadband Integrating time setting used when the Deadband calculation

1…200 s
method is Integrated.
integrating time
Unsolicited resp. Disabled Unsolicited responses not in use.
Unsolicited response enabled, empty UR sent first, waiting for Enable
mode +Empty&Ena
UR from master.
Unsolicited response enabled, empty UR sent first, not waiting
+Empty
for master Enable UR before proceeding.
Enabled Unsolicited response enabled, starts sending UR’s directly.
46 P5/EN M/11A

Unsolicited resp.
0…200 s Unsolicited responses are delayed by this amount of seconds from first event.
event delay
Unsolocited resp.
Unsolicited responses are delayed until this many events are available.
1…10
event count Used together with previous parameter.
Unsolicited resp. max

1…100 Maximum number of events in one unsolicited response.
event cnt
Collision avoidance
No, Yes Collision avoidance off/on.
enable flag
Collision avoidance
1…200 s Delay setting used in next parameter.
fixed delay
Collision avoidance Number of bus access slots available for random bus access.
1…255 If the line is busy, the slave waits for: fixed delay + random (slots),
slots number after the bus becomes idle before accessing the bus.
1: Single-bit packed.
Default Variation BI 1, 2
2: Single-bit with flag.
Default Variation BI 1: Without time.
1, 2
event 2: With absolute time.
Default Variation BO 2 2: Binary output status.
1: Without flag.
Default Variation DBI 1, 2
2: With flag.
Default Variation DBI 1: Without time.
1, 2
event 2: With absolute time.
1: 32-bit with flag.
Default Variation 3: Not supported.

1…6
Counter 4: Not supported.
5. 32-bit without flag.
6: 16-bit without flag.
Default Variation AI 1…5 3. 32-bit without flag.
4: 16-bit without flag.
5: Single precision, floating point without time.
1: 32-bit without time.
2: 16-bit without time.
Default Variation AI
1…5 3: 32-bit with time.
event
4: 16-bit with time.
5: Single precision, floating point without time.
P5/EN M/11A 47
Data Configuration
In Easergy P5 protection relays, data is mapped to five different categories:
• Binary Inputs (BI)
• Double-Bit Inputs (DBI)
• Analog Inputs (AI)
• Counters (CNTRS)
• Binary Outputs (BO)
The configuration of these is described in the following subsections.
Binary Inputs
Binary inputs are found in the DNP3: data points – BI view of COMMUNICATION
menu in eSetup Easergy Pro or Web HMI.
Table 12 - DNP3 DATA POINTS – BI
Index The index of the data item in the list.
Class Which class the data point belongs to. (Class 1, 2 or 3).
UR Controls whether changes in the value of the data point generates

unsolicited responses or not.
Item The data point.
48 P5/EN M/11A
Double-Bit Inputs
DNP3: data points – DBI view of COMMUNICATION menu contains the
configuration of Double-Bit Inputs.
The configuration of these points is analogous to that of Binary Inputs, see DNP3
DATA POINTS – BI, page 48.
Analog Inputs
Analog inputs are configured in the DNP3: data points – AI view of
COMMUNICATION menu.
Table 13 - DNP3 DATA POINTS – AI.
Index The index of the data item in the list.
Class Which class the data point belongs to. (Class 1, 2 or 3).
UR Controls whether changes in the value of the data point generates

unsolicited responses or not.
Deadband The amount of change in value needed before a change is registered. The
range of this setting is 1…4200000000.
Item The data point.
P5/EN M/11A 49
Counters
The configuration of counters is found in the DNP3: data points – CNTRS view of
COMMUNICATION menu.
Binary Outputs
Binary outputs are found in the DNP3: data points – BO view of
COMMUNICATION menu.
The structure of this configuration table is simple: only an index for the data items
(data points) and an Item field, which determines which data point if found at the
corresponding index. The data points are edited by clicking on an element in the
Item column and selecting the desired output.
50 P5/EN M/11A
Data Model of DNP3

The default Binary Inputs, Double-Bit Inputs, Analog Inputs, Counts and Binary
Outputs of Easergy P5 protection relays pre-configured in DNP3 can be found in
following tables.
Binary Inputs
Default Index Default Item

Class
0 1 DI1
1 1 DI2
2 1 DI3
3 1 DI4
4 1 SGrp1
5 1 SGrp2
6 1 SGrp3
7 1 SGrp4
8 1 Logic1
9 1 Logic2
10 1 Logic3
11 1 Logic4
12 1 Logic5
13 1 Logic6
14 1 VI1
15 1 VI2
16 1 VI3
17 1 VI4
18 1 VI5
19 1 VI6
Double-Bit Inputs
Default Index Default Item

Class
0 1 Object1
1 1 Object2
2 1 Object3
3 1 Object4
4 1 Object5
5 1 Object6
6 1 Object7
7 1 Object8
P5/EN M/11A 51
Analog Inputs
Default Default Dead- Item

Index Class band
0 2 1 PS1Value
1 2 1 PS2Value
2 2 1 PS3Value
3 2 1 PS4Value
4 2 1 PS5Value
5 2 1 PS6Value
6 2 1 PS7Value
7 2 1 PS8Value
Counters
Default Default Item
Index Class
0 2 DI1
1 2 DI2
2 2 DI3
3 2 DI4
Binary Outputs
Default Index Item

0 Obj1OC
1 Obj1Un
2 Obj2OC
3 Obj2Un
4 Obj3OC
5 Obj3Un
6 Obj4OC
7 Obj4Un
8 Obj5OC
9 Obj5Un
10 Obj6OC
11 Obj6Un
12 Obj7OC
13 Obj7Un
14 Obj8OC
15 Obj8Un
52 P5/EN M/11A
IEC 60870-5-101
Presentation
IEC 60870-5-101 is an accompanying standard for the standards in the IEC
60870-5 series. It defines communication between protection devices and the
various devices in a control system (supervisor or RTU) in a substation.
Easergy P5 protection relays using IEC 60870-5-101 work as controlled outstation
(slave) units in unbalanced mode. Supported application functions include:
• Process data transmission
• Event transmission
• Command transmission
• General interrogation
• Clock synchronization
• Transmission of integrated totals
• Acquisition of transmission delay
The IEC 60870-5-101 communication in Easergy P5 protection relays is only
command and event driven. Therefore only Class 1 data will be reported. Class 2
will not be used.
Class 1 data is handled in the following priority order:
• Command responses
• Events (binary events, analog events, counter value change events)
The event buffer size of IEC 60870-5-101 is 250.
• General Interrogation data
Chronology between events and requested data will be always maintained. For
lists of default data mappings in Easergy P5 protection relays, refer to Data Model
of IEC 60870-5-101, page 61.
P5/EN M/11A 53
IEC 60870-5-101 Configuration

This section explains how to configure Easergy P5 protection relays to use the
IEC 60870-5-101 protocol.
General Configuration
The IEC 60870-5-101 protocol is activated by setting it as the port protocol for a
serial port on the device. This setting can be found by navigating to the
COMMUNICATION menu and Protocol configuration view in the eSetup Easergy
Pro or Web HMI.
The IEC 60870-5-101 protocol is activated on the Remote port as follows:
NOTE: Setting a protocol to any port requires a reboot of the device for the
changes to take effect. eSetup Easergy Pro will prompt for a reboot.
Once the protocol has been activated, it can be configured. This is done with
eSetup Easergy Pro in the IEC 60870-5-101 main config view. All values shown
are defaults.
54 P5/EN M/11A
Table 14 - IEC 60870-5-101 main configuration
Bit rate 1200, 2400, 4800, 9600, 19200, Communication speed

38400, 57600, 115200 bps
Parity None, Even, Odd Parity used for serial

communication
WireNum 2, 4 Number of wire connection
PolLine False, True Polarity of the wire connection
FrameGap 10...500 Specifies the amount of time

(calculated by bits) to use to
determine that a frame has been
completed
Link layer address 1 byte: 1…254 Device address

2 bytes: 1…65534
Link layer address size 1 or 2 bytes Size of the device address
ASDU address 1 byte: 1…254 Address of data segment on the

2 bytes: 1…65534 same device address
ASDU address size 1 or 2 bytes Size of the ASDU
IO address size 2 or 3 bytes Size of Information Object

address
Cause of transmission 1 byte Size of the code for the reason
size why a message is sent
Time tag format Short, Full Determines the time tag format:
3-octet time tag of 7- octet time
tag
Measurements format Scaled, Normalised, Float Determines the data format for
measurements, float, normalised
or scaled values
Deadband enable flag On, Off Enabling of deadband
measurements and event
generation
Deadband cycle 100...10000 ms The interval of deadband

calculations
P5/EN M/11A 55
Data Configuration
Data and commands are mapped to six different tables: Single point information
(SPI), Double point information (DPI), Analog inputs (AI), Analog events (AE),
Integrated totals (IT) and Commands (CMD). The settings for these categories are
described in the following subsections.
Single and Double Point Information

Single point information (SPI) objects are one-bit data items (range 0…1). Double
point information objects are two-bit data items (range 0…3). Default SPI and DPI
mapping are shown in figures below.
A description of the column elements for SPI and DPI objects is given in the table.
NOTE: Information object address (Index) 1 is reserved for an SPI object:

Class 1 buffer overflow indication (BOV1).
Table 15 - SPI and DPI mapping table
Index Information object address
GI Determines whether the object is included in response to General

Interrogation request message (Enabled/Disabled)
Event Determines whether change events for the object are put into Class 1 buffer
(Enabled/Disabled)
Item The data item which is configured on the row (for instance, DI1)
56 P5/EN M/11A
Analog Inputs
Analog inputs are measurement values that are float, scaled or normalised.
Scaling is done according to the scaling settings found under the list item
MODBUS&IEC101 specific scalings in eSetup Easergy Pro or Web HMI (it applies
to IEC 60870-5-101 if the protocol is configured to use scaled values). When using
float for measurement values, no scalling is needed.
NOTE: Measurement values have no time tags when read upon request.
Change events (based on deadband supervision) are sent with time tags with
cause of transmission spontaneous in Class 1. The time tag format is
determined by the interface configuration (general time tag format selection
parameter).
Table 16 - AI mapping table
GI Determines whether the object is included in response to General

Interrogation request message (Enabled/Disabled)
Event Determines whether change events for the object are put into Class 1 buffer
(Enabled/Disabled)
Deadband Deadband value for change supervision and change event generation (valid
only if Event is Enabled).
Max Maximum value for defining the value range as –Max…+Max. This range is
transformed to the range -1…+1 if the protocol measurement format is set
to “Normalized”
Item The data item which is configured on the row
P5/EN M/11A 57
Analog Events
These analog values are fault event and are sent with time tags. The values are
float, normalised or scaled measured values. A part of the default data mapping is
shown in following figure.
Table 17 - AE mapping table
Event Determines whether change events for the object are put into Class 1
buffer (Enabled/Disabled)
58 P5/EN M/11A
Integrated Totals
Integrated totals are energy and pulse counter values. the following figure is a part
of the mapping table in eSetup Easergy Pro.
Table 18 - Integrated totals mapping table
CI Determines whether the object is included in responses to Counter

Counter Interrogation messages (Enabled/Disabled)
Interrogation
Command Items
The commands are divided into two categories: Select Before Operate and Direct
Operate.
Table 19 - Description of command items
P5/EN M/11A 59
Scaling
Measured values that transferred as signed integers of 16 bits are in the range: –
215 ··· 215 – 1 = – 32768 ··· 32767. Thus values that exceed this range are scaled
in order to be successfully sent over an IEC 101 data link.
The scaling is determined by the float value of corresponding specific scalings. It
is common to use scaling factors with base ten (0.100,1.000,10.000, 100.000…).
In such cases, only the decimals are removed from the original measurements
and such values are easy to read and rescale to actual values on the client side
after transmission. Different settings for scaling can be used for the power-, power
factor-, tan phi-, voltage- and frequency scaling. These settings for scaling can be
set by navigating to the Modbus & IEC101 specific scalings view in the
COMMUNICATION menu in eSetup Easergy Pro or Web HMI.
A short example: The frequency is internally (in the Easergy P5 protection relays)
stored as an integer value which also holds three decimal places, that is, 50.000
Hz is represented as 50000. This is a value too large to be represented with 16
bits (signed integer). However, frequency is multipled by default scaled value 0.1,
enabling it to be sent over the data line.
Thus, the value on the receiving side (the scaled value) will be:
valueScaled = k ⋅ valueInternal = 0.1 ⋅ 50000 = 5000
NOTE: It is highly recommended to scale values so that they are kept in the
interval 0 –32768 to avoid overflow.
Normalization
When using normalization for measured values, the normalized value is calculated
using the Max parameter, which determines the range for the data (– Max … +
Max).
An example: The frequency is internally (in the Easergy P5 protection relays)
Hz is represented as 50000. If normalization is activated and the Max value set to
100000, the value sent over the data link will (in the ideal case) be:
value Normalized= valueInternal/Max = 50000/100000 = 0.5
Currently, however, the scaling is also performed before normalization. This
means that the scaling is always active.
The equation will therefore be: valueNormalized =valueScaled/Max = 0.1 x 50000/
100000 = 0.05
Also, due to the fact that normalised values are represented with 16 bit floating
point values, the accuracy will not always be this exact.
Float
When using Float for measured values, no scaling will be used. An example:
50.000 Hz is represented as 50, just use the raw value to transfer.
60 P5/EN M/11A
Data Model of IEC 60870-5-101

The default Single Point Information, Double Point Information, Analog Inputs,
Analog Events, Intergrated Totals and Command of Easergy P5 protection relays
pre-configured in IEC 60870-5-101 can be found in following tables.
Default Single and Double Point Information

Table 20 - Single Point Information
Default Index Item

2 DI1
3 DI2
4 DI3
5 DI4
6 SGrp1
7 SGrp2
8 SGrp3
9 SGrp4
10 Logic1
11 Logic2
12 Logic3
13 Logic4
14 Logic5
15 Logic6
Table 21 - Double Point Information
Default Index Item

4097 Object1
4098 Object2
4099 Object3
4100 Object4
4101 Object5
4102 Object6
4103 Object7
4104 Object8
Analog Inputs
Default Index Deadband Max Item

16385 1.000 1000 PS1Value
16386 1.000 1000 PS2Value
16387 1.000 1000 PS3Value
16388 1.000 1000 PS4Value
16389 1.000 1000 PS5Value
16390 1.000 1000 PS6Value
16391 1.000 1000 PS7Value
16392 1.000 1000 PS8Value
P5/EN M/11A 61
Analog Events
Default Index Item

18433 PS1Value
18434 PS2Value
18435 PS3Value
18436 PS4Value
18437 PS5Value
18438 PS6Value
18439 PS7Value
18440 PS8Value
Integrated Totals
Default Index Item

20481 DI1
20482 DI2
20483 DI3
20484 DI4
Default Command
Table 22 - SBO table
Default Item
34817 Object1
34818 Object2
34819 Object3
34820 Object4
34821 Object5
34822 Object6
Table 23 - DO table
Default Index Item

32769 SGrp1
32770 SGrp2
32771 SGrp3
32772 SGrp4
32773 Object1
32774 Object2
32775 Object3
32776 Object4
32777 Object5
32778 Object6
62 P5/EN M/11A
IEC 60870-5-103
Presentation
IEC 60870-5-103 is an accompanying standard for the standards in the
IEC 60870-5 series. It defines communication between protection devices and the
various devices in a control system (supervisor or RTU) in a substation.
The unbalanced transmission mode of the protocol is used, and the device
functions as a secondary station (slave) in the communication. Data is transferred
to the primary system using the "data acquisition by polling" principle.
The Easergy P5 protection relay supports the following IEC 61870-5-103
application functions:
• Data acquisition by polling
• General initialization
• Station initialization
• General interrogation
• Clock synchronization
• Command transmission
• Transmission of disturbance data
The following ASDU (Application Service Data Unit)✧ types are used in
communication from the Easergy P5 protection relays:
• ASDU 1: Time tagged message
• ASDU 3: Measurands I
• ASDU 4: Time-tagged measurands with relative time
• ASDU 5: Identification message
• ASDU 6: Time synchronization
• ASDU 8: Termination of general interrogation
• ASDU 9: Measurands II
Easergy P5 protection relays accept:
• ASDU 6: Time synchronization
• ASDU 7: Initiation of general interrogation
• ASDU 20: General command
The ASDUs from 23 to 31 are used for disturbance record file transmission.
The data in a message frame is identified by:
• Type identification
• Function type (TYP)
• Information number (INF)
For more information on the IEC 60870-5-103 protocol, visit www.iec.ch.
P5/EN M/11A 63
IEC 60870-5-103 Configuration

This section explains how to configure Easergy P5 protection relays to use the
IEC 60870-5-103 protocol.
General Configuration
The IEC 60870-5-103 protocol is activated by setting it as the port protocol for a
serial port on the device. This setting can be found by navigating to the
COMMUNICATION menu and Protocol configuration view in the
eSetup Easergy Pro or Web HMI. IEC 60870-5-103 protocol is activated on the
Remote port.
NOTE: Setting a protocol to any port will require a reboot of the device for the
changes to take effect. eSetup Easergy Pro will prompt for a reboot.
Once the protocol has been activated, it can be configured. This is done with
eSetup Easergy Pro in the IEC 60870-5-103 main config view. All values shown
are defaults.
64 P5/EN M/11A
Table 24 - IEC 60870-5-103 main configuration
IEC-103 slave number 1...254 A unique address within the

system setup
IEC-103 bit rate 1200, 2400, 4800, 9600, 19200, Communication speed
38400, 57600, 115200 bps
WireNum 2, 4 Number of wire connection
PolLine False, True Polarity of the wire connection
FrameGap 10...500 Specifies the amount of time

completed
Meas sending interval 200…10000 ms Minimum measurement response

interval
ASDU6 response time Sync (the time in the slave’s ASDU 6 response time mode
mode response = the master’s time)
Sync + Proc (the time in the
slave’s response = the master’s
time + internal processing time
(standard)), Msg (the time in the
slave’s response = the slave’s
time at the moment when the
clock sync message arrived)
Msg + Proc(the time in the
slave’s response = the slave’s
time at the moment when the
clock sync message arrived +
internal processing time)
Include Start/Restart- On, Off

PowerOn
Table 25 - IEC 60870-5-103 disturbance recorder parameter
Enable record info msg On, Off Enable record information

messages
Record samples in msg 1...25 Record samples in one message
Record reading timeout 10…10000 s Record reading timeout
Fault number of active (not editable) The fault number of the current
record record. This is a number which is
given by Easergy P5 protection
relays, incrementally and is what
identifies faults.
Tags read position (not editable) Tags are indications of change in
the value of digital data. The
current tag read position shows
which such item is being read.
Active channel (not editable) “Channel” refers to the channels

in Easergy P5 protection relays
Disturbance recorder, which can
be found in the DISTURBANCE
RECORDER view in eSetup
Easergy Pro. The active channel
indicates which channel is being
read.
Channel read position (not editable) A channel contains sampled
analog values. The current read
position indicates which of these
entries in the active channel is
being read.
P5/EN M/11A 65
Data Configuration
The data points available through the IEC 60870-5-103 protocol interface in
Easergy P5 protection relays can be configured in the IEC 60870-5-103: Data
config view. It is divided into two categories, Digital data points (1-bit values) and
Analog data points.
Digital Data
The parameters, by which digital data points are defined, are explained below. In
order to change the value of an existing data item, click on the row. This brings up
an item configuration window, in which the parameters can be set. Pressing Save
in the window will save the item set, pressing Remove will remove the item from
the list and pressing Cancel will close the popup window without making any
changes to the digital item configuration.
In order to add new items to the list, press the ADD Item row furthest down in the
list. Doing so will add a new item at the end of the list. New items will be set to
Digital Input 1 by default. The new item is configured as explained in the previous
paragraph.
Table 26 - Description of digital data configuration
Index Index of the data item in the list

FUN Function type
INF Information number
GI Item included in General Interrogation (Enabled/Disabled) and data

acquisition by polling
EVENT Events enabled for change of item value (Enabled/Disabled)
CONTROL Item value can be set by command (Enabled/Disabled)
Item The data item which is configured on the row (for instance, Digital
Input 1)
NOTE: Changes will not take effect if they are not explicitly written to the
device using the Write changes to device button in eSetup Easergy Pro. This
will require a reboot.
66 P5/EN M/11A
Analog Data
The parameters, by which analog data points are defined, are explained below. In
order to change the value of an existing data item, click on the row. This brings up
an item configuration window, in which the parameters can be set. Pressing Save
in the window will save the item set, pressing Remove will remove the item from
the list and pressing Cancel will close the popup window without making any
changes to the analog item configuration.
In order to add new items to the list, press the ADD Item row furthest down in the
list. Doing so will add a new item at the end of the list. The new item is configured
as explained in the previous paragraph.
Table 27 - Description of analog data configuration
Index Index of the data item in the list

FUN Function type
INF Information number
ASDU Application service data unit to be used to send the data item:
ASDU 3.1: analog data 1 value
ASDU 4: analog data floating point value
ASDU 9: analog data 9 value
NOTE: Changes will not take effect if they are not explicitly written to the
device using the Write changes to device button in eSetup Easergy Pro. This
will require a reboot.
P5/EN M/11A 67
Measurement Data
Analog measurements are transferred in two different formats, as integers and as
floating point values. The value format depends on the application message type,
ASDU. The following ASDU types are available for measurement values:
Table 28 - ASDU types for measurement values
ASDU Number of measurements in one message Format
3.1 1 Integrer
3.2 2
3.3 4
3.4 2
3.9 9
4 1 Float
Integer Value Scaling

Integer value scaling ASDU 3 measurements are transferred in 12 bit + sign
integer format. The raw 12 bit values (-4096 … +4095) are relative to 2.4 x
nominal values. Following table shows the scaling for different measurements.
The values of scaling settings can be found in the SCALING view in eSetup
Easergy Pro.
Table 29 - Integer scaling values
Type Measurement Scaling
Current IL1 ... IL3 2.4 × IN

loCalc
Residual current Ir 2.4 × IrN
Irvs 2.4 × IrvsN
Voltage VL1...VL3 2.4 × UN
U12...U13
Residual voltage Ur 2.4 × UrN
Power P, Q, S 2.4 × IN × UN × √3
Other DI counters 1:1

PF, Cos Phi 2.4:1
An example:
The device transfers Line 1 current, IL1 with ASDU 3.1.
The scaling setting is as follows: CT primary = 500 A.
The measured value M = 321.
Thus, the value sent, B = M ×(4096/(2.4×500))= 321 ×(4096/(2.4×500))= 1095
The protocol master receives the value: B = 1095
OVF (Overflow bit in frame): No
Valid: Yes
This value is converted back to the measured value:
M = B ×((2.4 × 500)/4096) = 1095 × ((2.4 × 500)/4096) = 320.8 ≈ 321
68 P5/EN M/11A
An example:
The device transfers Line 1 current, IL1 with ASDU 3.1.
The scaling setting is as follows: CT primary = 500 A.
The measured value M = 1321.
Thus, the value sent, B = M × (4096/(2.4 × 500))= 1321 × (4096/(2.4 × 500)) =
4509, is too large a value to fit into twelve bits. Thus, the value is sent as B = 4095
(the largest value that can be sent with twelve bits) and the OVF (Overflow flag)
set.
The protocol master receives the value: B = 4095
OVF (Overflow bit in frame): Yes
Valid: Yes
This value is converted back to the measured value: M ≥ 2.4 × 500 M ≥ 1200
Floating Point Values

Values transferred in ASDU 4 need not be scaled. Most of the measurements are
sent as primary scaled values, but some values can be sent as per unit (PU)
values. This setting can be changed via the local panel on the Easergy P5
protection relays.
Measurement Format
Fault current I> PU or A
Fault current I>> PU or A
Fault current I>>> PU or A
Fault reactance Ω
Exported energy MWh
Exported reactive energy Mvarh
P5/EN M/11A 69
Data Model of IEC 60870-5-103

The default digital and analog data of Easergy P5 protection relays preconfigured
in IEC 60870-5-103 can be found in following tables.
Default Digital Configuration
Defaut Index FUN INF Item

000 55 161 CB Open_DI1
001 55 162 CB Open_DI2
002 55 163 Digital input 3
003 55 164 External trip_DI4
004 55 181 Object1 state
012 160 20 Logic output 1 on
022 160 130 Virtual input 1
032 160 140 CBF1 Trip On
033 160 141 CBF2 Trip On
034 55 23 Setting group 1
70 P5/EN M/11A
Defaut Index FUN INF Item

038 160 103 Prg1 start
039 160 105 Prg1 trip
040 160 98 Prg2 start
041 160 100 Prg2 trip
042 160 99 Prg3 start
043 160 101 Prg3 trip
044 160 180 Prg4 start
045 160 181 Prg4 trip
046 160 69 Prg5 start
047 160 70 Prg5 trip
048 160 71 Prg6 start
049 160 19 Prg6 trip
Default Analog Configuration
Default Index FUN INF ASDU Item

050 160 65 4 Frequency
P5/EN M/11A 71
Modbus
Presentation
The Modbus interface is a master/slave protocol defined by the Modbus
organization.
For more information on the Modbus protocol, visit www.modbus.org.
It is used to exchange information between a master and one or more slave units,
identified by a number. It implements request-reply dialog, where requests are
always initiated by the master. Modbus exists in ASCII and binary (RTU mode)
formats. Data is exchanged in the form of 16-bit words (also called registers) or
simply bits. Each piece of information (bit or register) has a 16-bit address.
Modbus is a data-transmission protocol in charge of communication using serial
link or Ethernet links.
Modbus TCP/IP offers the same functionality as Modbus over a serial link, as well
as compatibility with multi-master architectures.
The Easergy P5 protection relay is considered in Modbus communication as a
slave only. The maximum number of Modbus slaves in the device is 2.
The Modbus slave can communicate with masters using either of two
transmission modes:
• Serial mode
• TCP/IP mode
The Modbus slave can communicate with the master through the serial port and
Ethernet port at the same time.
The Modbus slave supports the following functions and services:
• Binary Status
• Measurement Values
• Remote Control
• Time Synchronization
• Event Record
• Diagnostics
Modbus Protocol Data Unit
Every Modbus request or response frame includes a Modbus PDU (protocol data
unit) made up of 2 fields.
• Function code (1 byte): indicates the type of request (1 to 127)
• Data (0 to n bytes): depends on the function code
The function codes in the reply and in the request are identical.
Function Codes
Table 30 - Modbus function codes
Function Codes Address Space
03 Read Holding Registers (16 bits)
04 Read Input Registers (16 bits)
06 Write single register (16 bits)
07 Read Exception Status (16 bits)
08 Diagnostic
11 Get Comm Event Counter (16 bits)
72 P5/EN M/11A
Table 30 - Modbus function codes (Continued)
Function Codes Address Space
16 Write multiple registers (16 bits)
23 Read/Write multiple registers (16 bits)
43 Read Device Identification (16 bits)
The following exception codes are supported:

• 01: Unknown function code
• 02: Incorrect address
• 03: Incorrect data
• 04: Not ready (cannot process request)
• 07: Not acknowledged (remote reading and setting)
Modbus Serial Link Frames
All the frames exchanged have the same structure, made up of 3 parts:
• Slave address (1 byte): from 1 to 247 (0 for broadcasting)
• Modbus PDU: as previously described
• Check (2 bytes): CRC16 used to check frame integrity
The slave addresses in the reply and in the request are identical.
The maximum size of a frame is 256 bytes.
Synchronization of Exchanges
Any character that is received after a silence of more than 3.5 characters is
considered as the beginning of a new frame. A minimum silence of 3.5 characters
is always observed between two frames.
A slave disregards all frames:
• Received with a physical error for 1 or more characters (format error, parity
error, etc.)
• With an incorrect CRC16 result
• For which it is not the recipient.
The slave addresses in the reply and in the request are identical.
The maximum size of a frame is 256 bytes.
Broadcasting
The master can also address all slaves using the conventional address 0. This
type of exchange is called broadcasting. Slaves do not respond to broadcast
messages. As a result, only messages that do not require the transmission of data
by the slaves can be broadcast.
Response time
The communication coupler response time (Tr) is less than 15 ms, including a 3-
character silence (approximately 3 ms at 9600 bauds).
This time is given with the following parameters:
• 9600 bauds
• Format: 8 bits, odd parity, 1 stop bit
P5/EN M/11A 73
Modbus Serial RTU Mode Configuration

The Modbus RTU protocol is activated by selecting the 'ModBusSlv' option for the
'Remote port protocol' of the Easergy P5 protection relay serial port. This setting
can be found by navigating to the Protocol configuration view in the
COMMUNICATION menu in eSetup Easergy Pro. The following figures show how
to enable the Modbus protocol on the Remote port of an Easergy P5 protection
relay.
The protocol can also be enabled via the front panel or Web HMI.
Once the protocol has been activated, it can be configured. This is done in the
MODBUS main configuration view of the COMMUNICATION menu. In the
Modbus main configuration view, the Modbus Slave Address (or number), the bit
rate, the parity of the connection, the wire number and polling line can be set. The
frame gap is fixed.
Figure 2 - Modbus main configuration
Table 31 - Modbus main configuration
Slave number 1...247 The Modbus slave address.

ModBus bit rate 1200, 2400, 4800, 9600, The communication speed, bits
19200, 38400, 57600, 115200 per second.
bps
Parity None, Even, Odd The type of parity bit used.
WireNum 2, 4 The number of wire connection.
PolLine False, True The polarity of the wire connection.
FrameGap Specifies the amount of time

completed. For modbus RTU this
value is fixed at 38 bits.
NOTE: The parity and bit rate are set to the same value on all devices
connected to the same data link.
74 P5/EN M/11A
Modbus TCP Mode Configuration

Modbus TCP (or Modbus TCP/IP) is simply the Modbus RTU protocol with a TCP
interface that runs on Ethernet. TCP/IP refers to the Transmission Control
Protocol and Internet Protocol which provide the transmission medium for Modbus
TCP/IP messaging. In practice, Modbus TCP embeds a standard Modbus data
frame into a TCP frame.
One advantage over serial Modbus (RTU or ASCII) is that the number of nodes is
not limited to 247 on one data link, since the addressing of nodes is done with the
Internet Protocol. Furthermore, several devices can be connected to one IP
address, provided the appropriate equipment is used (some Modbus TCP-to-
Modbus RTU bridge). These devices are differentiated from each other with a Unit
Identifier, in the TCP frame, which corresponds to the Slave ID. The range of the
Unit Identifier is also 1-247. In Easergy P5 protection relays the Modbus Slave ID
corresponds to the Unit Identifier when Modbus TCP is used, see Modbus main
configuration, page 74.
The Modbus TCP protocol is activated by first configuring the Ethernet port
settings. First, the IP address, Subnet mask and Gateway are set, and require a
static IP address to be configured. This is considered before connecting a relay to
an existing network, so that no conflicts emerge.
Once these settings have been configured, one of the Ethernet port protocol
selections can be set to “ModBusTCPs” (Modbus TCP, slave).
Before the protocol is activated, a device reboot is required.
NOTE: There are two TCP port instances “Ethernet Protocol 1” and “Ethernet
Protocol 2”, that is, two independent sockets for two different protocols. The
default TCP IP port for Modbus TCP is 502.
P5/EN M/11A 75
Data access, such as reading and writing to holding registers, event reading, clock
synchronisation and scaling work, with the addition that clock synchronisation also
can be done by using SNTP (Simple Network Time Protocol). This requires a NTP
server, the address of which is set in the Protocol configuration view in eSetup
Easergy Pro or Web HMI.
Events
The event buffer of Easergy P5 protection relays can be read via the Modbus
Protocol. This is done by reading one event at a time, from holding registers
2101…2105. The event registers contain the latest event, and are cleared when
they are read. The registers are then updated to contain the following event from
the event buffer. A description of the registers is shown in the table.
Table 32 - Description of Events in holding registers.
Holding Register Content
2101 Event code

2102 Event timestamp
Bits 15-6 = milliseconds
Bits 5-0 = seconds
Upper byte = minute
Lower byte = hour

Upper byte = day
Lower byte = month
2105 Event timestamp, year
76 P5/EN M/11A
Clock Synchronisation
The internal clock of Easergy P5 protection relays can be synchronised via the
Modbus protocol. Note this is not a native feature of the Modbus protocol.
Therefore, this is an Easergy P5 protection relay specific feature. The accuracy of
the clock synchronisation is in the scale of a few hundred milliseconds.
The clock can be synchronised either completely (all fields: seconds, minutes,
hours, days, month and year) or by synchronising only the minutes, which in turn
will set the seconds and milliseconds to zero.
An example of how minute synchronisation can be done: when the reference clock
(the clock which is assumed to be correct) is exactly seven minutes past (any
hour), a minute synchronisation is performed. The result will be that the internal
clock of the Easergy P5 protection relays will be set to HH:07:00.000 (“Hours:
Minutes:Seconds.Milliseconds”) “HH” will not be changed.
These two ways of synchronising the clock are denoted “Set RTC”, where “RTC”
stands for “Real-Time Clock” and “Synchronise Minutes” in the data map. The
holding register address of the minute synchronisation is 2502.
The holding registers allocated to the Set RTC synchronisation are:
Table 33 - Description of holding registers allocated to Set RTC

synchronisation
Holding Register Content
2504 Lower byte: seconds, milliseconds will be zero
2505 Upper byte: minutes

Lower byte: hours
2506 Upper byte: day

Lower byte: month
2507 Year
Scaling
Since the Modbus registers are 16 bits in size, they can directly represent 2^16 =
65535 different values, which might not be enough to describe the values of some
physical quantity such as voltage or power. Thus, values transmitted over a
Modbus data link are scaled to account for this.
The scaling is determined by the float value of the corresponding specific scalings.
After multiplication by a scaling value, only the decimals are removed from the
original measurements, and such values are easy to read and rescale to actual
values on the client side after transmission.
These settings for scaling can be set by navigating to the Modbus&IEC101
specific scalings view in the COMMUNICATION menu in eSetup Easergy Pro or
Web HMI.
A short example: The frequency is internally (in the Easergy P5 protection relays)
Hz is represented as 50000. This is a value too large to be represented with 16
bits (signed integer). However, frequency is multipled by default scaled value 0.1,
enabling it to be sent over Modbus.
Thus, the value on the receiving side (the Modbus value) will be:
valueModbus = k ⋅ valueInternal = 0.1 ⋅ 50000 = 5000
P5/EN M/11A 77
Scaling can be checked in eSetup Easergy Pro by viewing the Scaling column for
each register in the Modbus slave: xxx items in the COMMUNICATION menu.
NOTE: It is highly recommended to scale values so that they are kept in the
interval 0 –32000 to avoid overflow.
The Modbus scaling address can be found in the Modbus specific scalings view in
the COMMUNICATION menu in eSetup Easergy Pro or Web HMI.
78 P5/EN M/11A
The following table shows the different values of Voltage scaling, and the values to
be filled in the frame. When the client reads a 2 register value for voltage scaling, it
needs to combine these 2 values together and convert them to a float 32 value.
For example, when voltage scaling value is 0.001, the values 0x126f and 0x3A83
will be merged to 4 bytes value 0x3A83126F.
Table 34 - Voltage scaling values
Voltage scaling IEEE 754 / Float32 Value in address Value in address

10007 10008
1.0000 0x3F800000 0x0000 0x3F80
0.0010 0x3A83126F 0x126F 0x3A83
1000.0000 0x447A0000 0x0000 0x447A
500.0000 0x43FA0000 0x0000 0x43FA
P5/EN M/11A 79
Data Model of Modbus
Scalings
Function Setting for

Address Name Read Write Data Type Scalling P5U20 P5V20 P5F30 P5M30
Code Scalling
1001 CT primary ■ 3 UInt32 1A=1 ■ ■ ■
1002 CT secondary ■ 3 UInt16 1A=1 ■ ■ ■
Rated ext. LPCT/VT

1003 primary ■ 3 float32 1.00 A = 100 scaling ■ ■
current In
LPCT rated
1004 primary ■ 3 UInt32 1A=1 ■ ■
current
0.25=0, 1.25=1, 0.5=2,
Extended 2.5=3, 1=4, 5, 1.33=6,
1005 primary ■ 3 UInt8 6.65=7, 2=8, 10=9, 3.2=10, ■ ■
current factor 16=11, 4=12, 20=13, 6.3=
14, 31.5=15, 25=16
Earth/ground
1006 CT primary ■ 3 UInt32 1A=1 ■
Earth/ground
1007 CT secondary ■ 3 float32 1.0 A = 10 ■
Io CSH
1008 primary ■ 3 UInt32 1A=1 ■ ■
Io CSH
1009 secondary ■ 3 float32 1.0 A = 10 ■ ■
1010 Io CSH input ■ 3 float32 1.0 A = 10 ■ ■
Very sensitive
1011 Earth/ground ■ 3 UInt32 1A=1 ■
CT primary
Very sensitive
1012 Earth/ground ■ 3 float32 1.0 A = 10 ■
CT secondary
VT
1013 VT primary ■ 3 UInt32 1000 V = 1000 primary ■ ■ ■
scaling
Rated ext.
LPCT/VT
1014 primary ■ 3 float32 1.00 V = 100 ■ ■
scaling
voltage Un
LPVT rated
LPCT/VT
1015 primary ■ 3 UInt32 ■ ■
scaling
voltage 1000 V = 1000
1016 VT secondary ■ 3 UInt16 1V=1 ■ ■ ■
VTy
1017 secondary ■ 3 UInt16 1V=1
VT
1018 VTo primary ■ 3 UInt32 1000 V = 1000 primary ■ ■ ■
scaling
VTo
VTo secon-
1019 secondary ■ 3 float32 1.000 V = 100 dary ■ ■ ■
scaling
0.25=0, 0.3=1, 0.4=2, 0.5=

Extended
3, 0.6=4, 0.7=5, 0.8=6, 0.9=
1020 primary ■ 3 UInt8 ■ ■
7, 1=8, 1.1=9, 1.2=10, 1.3=
voltage factor
11, 1.4=12, 1.5=13
Phase 1-2-3=0, 1-3-2=1

1021 ■ 3 UInt8 ■ ■ ■ ■
Rotation
2LL+Uo=0, 3LN=1, 1LL
Voltage +Uo/LLy=2, 2LL/LLy=3, LL/
1022 measurement ■ 3 UInt8 LLy/LLz=4, 1LL=5, 1LN=6, ■ ■ ■
mode 3LL=8, 3LN/LNy=9, 3LN/
80 P5/EN M/11A

Code Scalling
LLy=10, 2LL+Uo/LNy=11,
2LL+Uo+LLy=12, 3LN+Uo=
13, LL+Uo/y/z=14, LN+Uo/
y/z=15, LL/LLy=16, 3LN/
2LNy=17
Nominal
1023 frequency ■ 3 UInt32 50 Hz = 50 ■ ■ ■ ■
Power Outgoing=0, Incoming=1

1024 ■ 3 UInt8 ■ ■
direction
P5/EN M/11A 81
Read and Command

Code Scalling
2001 Alive indicator ■ 3 UInt16 1=1 ■ ■ ■ ■
Digital Inputs
2006 ■ 3 UInt32 1=1 ■ ■ ■ ■
01...16
Digital Inputs
2007 ■ 3 UInt16 1=1 ■ ■ ■ ■
17...32
Digital Inputs
2008 ■ 3 UInt32 1=1 ■ ■ ■
33...40
2042 Object1 state ■ 3 UInt8 Open=0, Close=1, Undef=2 ■ ■ ■
2051 Output relays ■ 3 UInt32 1=1 ■ ■ ■
Run hours/
2057 ■ 3 UInt16 1=1 ■ ■ ■
10^0
Run hours/
2058 ■ 3 UInt16 1=1 ■ ■ ■
10^4
Engine
2059 running (in ■ ■ 3, 6 UInt16 1s=1 ■ ■ ■
seconds)
2060 Start counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■
2101 Events ■ 3 UInt16 1=1 ■ ■ ■ ■
Normal=0, Test=1, Test

2301 IED Mode ■ 3 UInt16 ■ ■ ■ ■
Block=2
Remote/Local REMOTE=0, LOCAL=1
2302 ■ 3 UInt8 ■ ■ ■
State
2490 Reread event ■ 3 UInt16 1=1 ■ ■ ■ ■
Release 3, 6
2501 ■ ■ UInt8 Release=1 ■ ■ ■ ■
latches
Synchronize 3, 6
2502 ■ ■ UInt8 1=1 ■ ■ ■ ■
minutes
2504 Set RTC ■ 6 UInt16 1=1 ■ ■ ■ ■
Open select
2508 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object1
Close select
2509 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object1
Execute
2510 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object1
MaxCtrl-
Max ctrl pulse
Pulse-
2511 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object1
scaling
Open select
2512 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object2
Close select
2513 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object2
Execute
2514 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object2
82 P5/EN M/11A

Code Scalling
MaxCtrl-
Max ctrl pulse
Pulse-
2515 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object2
scaling
Cancel
2516 selected ■ 6 UInt8 1=1 ■ ■ ■ ■
operation
Open select
2517 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object3
Close select
2518 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object3
Execute
2519 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object3
MaxCtrl-
Max ctrl pulse
Pulse-
2520 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object3
scaling
Open select
2521 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object4
Close select
2522 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object4
Execute
2523 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object4
MaxCtrl-
Max ctrl pulse
Pulse-
2524 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object4
scaling
Open select
2525 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object5
Close select
2526 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object5
Execute
2527 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object5
MaxCtrl-
Max ctrl pulse
Pulse-
2528 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object5
scaling
Open select
2529 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object6
Close select
2530 ■ ■ 3, 6 UInt8 1=1 ■ ■ ■ ■
Object6
Execute
2531 operation ■ 6 UInt8 1=1 ■ ■ ■ ■
Object6
MaxCtrl-
Max ctrl pulse
Pulse-
2532 length of ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Length
Object6
scaling
SetGrp
2534 common ■ ■ 3, 6 UInt8 1=0, 2=1, 3=2, 4=3 ■ ■ ■ ■
change
Clear min/ 3, 6
2536 ■ ■ UInt8 Clear=1 ■ ■ ■ ■
max/demand
P5/EN M/11A 83
Measurement
Code Scalling
Pos.
3001 sequence I1 ■ 3 UInt32 1A=1 ■ ■ ■
Negative
3002 sequence I2 ■ 3 UInt32 1A=1 ■ ■ ■
Current ratio
3003 ■ 3 float32 1.0 % = 10 ■ ■ ■
I2/I1
Current phase
3004 ■ 3 UInt8 ??=0, OK=1, Reverse=2 ■ ■ ■
sequence
Phase current
3005 ■ 3 float32 1.0 % = 10 ■ ■ ■
THD
Phase current
3006 ■ 3 float32 1.0 % = 10 ■ ■ ■
IL1 THD
Phase current
3007 ■ 3 float32 1.0 % = 10 ■ ■ ■
IL2 THD
Phase current
3008 ■ 3 float32 1.0 % = 10 ■ ■ ■
IL3 THD
Phase current
3009 ■ 3 UInt32 1A=1 ■ ■ ■
IL
Min. of IL1 IL2
3010 ■ 3 Int32 1A=1 ■ ■ ■
IL3
Max. of IL1
3011 ■ 3 Int32 1A=1 ■ ■ ■
IL2 IL3
Phase current
3012 ■ 3 UInt32 1A=1 ■ ■ ■
ILRMS
Phase current
3015 ■ 3 UInt32 1A=1 ■ ■ ■
IL1RMS
Phase current
3016 ■ 3 UInt32 1A=1 ■ ■ ■
IL2RMS
Phase current
3017 ■ 3 UInt32 1A=1 ■ ■ ■
IL3RMS
Ambient
3019 ■ 3, 6 Int16 ■ ■
temperature 1 °C = 1
Phase current
3020 ■ 3 UInt32 1A=1 ■ ■ ■
IL1da demand
Phase current
3021 ■ 3 UInt32 1A=1 ■ ■ ■
IL2da demand
Phase current
3022 ■ 3 UInt32 1A=1 ■ ■ ■
IL3da demand
Pos. Voltage
3031 sequence U1 ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Negative Voltage
3032 sequence U2 ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
3033 Voltage U2/U1 ■ 3 float32 1.0 % = 10 ■ ■ ■
Voltage phase
3034 ■ 3 UInt8 ??=0, OK=1, Reverse=2 ■ ■ ■
sequence
3035 Voltage THD ■ 3 float32 1.0 % = 10 ■ ■ ■
Line-to-neutral
3036 ■ 3 float32 1.0 % = 10 ■ ■ ■
VL1 THD
Line-to-neutral
3037 ■ 3 float32 1.0 % = 10 ■ ■ ■
VL2 THD
Line-to-neutral
3038 ■ 3 float32 1.0 % = 10 ■ ■ ■
VL3 THD
Average Line- Voltage
3039 Line voltage ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Min of Line- Voltage

3040 Line voltages ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
84 P5/EN M/11A

Code Scalling
Max of Line- Voltage

3041 Line voltages ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Average Line-
Voltage
3042 to-neutral ■ 3 UInt32 1000 V = 1000 ■ ■ ■
scaling
voltage
Min. of Line-
Voltage
3043 to-neutral ■ 3 UInt32 1000 V = 1000 ■ ■ ■
scaling
voltages
Max. of Line-
Voltage
3044 to-neutral ■ 3 UInt32 1000 V = 1000 ■ ■ ■
scaling
voltages
RMS voltage Voltage

3045 ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
mean
Line-to-neutral Voltage
3048 voltage ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
VL1RMS
VL2RMS
VL3RMS
PF and
3058 ■ 3 float32 1.00 = 100 cos ■ ■
Cosφ scaling
Tanφ
3059 Tanφ ■ 3 float32 1.000 = 1000 scaling ■ ■
3060 Power angle ■ 3 Int16 1°=1 ■ ■
RMS active Power

3061 power ■ 3 Int32 1000 kW = 1000 scaling ■ ■
RMS reactive Power

3062 power ■ 3 Int32 1000 kVAr = 1000 scaling ■ ■
RMS apparent Power

3063 power ■ 3 Int32 1000 kVA = 1000 scaling ■ ■
Active power Power

3066 ■ 3 Int32 1000 kW = 1000 scaling ■ ■
demand
Reactive Power
demand
Apparent Power
demand
PF and
Power factor cos
3069 ■ 3 float32 1.00 = 100 ■ ■
demand scaling
RMS active Power

3071 power ■ 3 Int32 1000 kW = 1000 scaling ■ ■
demand
RMS reactive Power
demand
RMS apparent Power
demand
Phase L1 Power
3081 active power ■ 3 Int32 1000 kW = 1000 scaling ■ ■
Phase L2 Power
Phase L3 Power
P5/EN M/11A 85

Code Scalling
Phase L1 Power
3084 reactive power ■ 3 Int32 1000 kVAr = 1000 scaling ■ ■
Phase L2 Power
Phase L3 Power
Phase L1
Power
3087 apparent ■ 3 Int32 1000 kVA = 1000 ■ ■
scaling
power
Phase L2
Power
3088 apparent ■ 3 Int32 1000 kVA = 1000 ■ ■
scaling
power
Phase L3
Power
3089 apparent ■ 3 Int32 1000 kVA = 1000 ■ ■
scaling
power
PF and
3090 Cosφ of phase ■ 3 float32 1.00 = 100 cos ■ ■
L1 scaling
PF and
L2 scaling
PF and
L3 scaling
Frequen-
3101 Frequency fy ■ 3 float32 ■ ■
50.000 Hz = 5000 cy scaling
Line-line Voltage
3102 voltage U12y ■ 3 float32 scaling ■ ■
1000 V = 1000
Phase angle
3103 ■ 3 float32 ■ ■
difference 1°=1
Frequen-
3111 Frequency fz ■ 3 float32 ■ ■
50.000 Hz = 5000 cy scaling
Line-line Voltage
3112 voltage U12z ■ 3 float32 scaling ■ ■
1000 V = 1000
Phase angle
3113 ■ 3 float32 ■ ■
difference 1°=1
Pos.
3151 sequence I'1 ■ 3 float32 ■ ■
1A=1
Negative
3152 sequence I'2 ■ 3 float32 ■ ■
1A=1
3207 Calculated Io ■ 3 float32 1.00 A = 100 Io scaling ■ ■ ■
Io CSH IoCSH
3208 residual ■ 3 float32 scaling ■ ■ ■
current 1.00 A = 100
Phase current
3209 ■ 3 UInt32 1A=1 ■ ■ ■
IL1
Phase current
3210 ■ 3 UInt32 1A=1 ■ ■ ■
IL2
Phase current
3211 ■ 3 UInt32 1A=1 ■ ■ ■
IL3
Io residual Io scaling
3212 ■ 3 float32 1.00 A = 100 ■ ■
current
Io' residual Io' scaling
3213 ■ 3 float32 1.000 A = 1000 ■ ■
current
Line-line Voltage
3214 voltage U12 ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Line-line Voltage
86 P5/EN M/11A

Code Scalling
Line-line Voltage
3217 voltage VL1 ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Residual
3220 voltage ■ 3 float32 1.0 % = 10 ■ ■ ■
Frequen-
3221 Frequency ■ 3 float32 50.000 Hz = 5000 ■ ■ ■ ■
cy scaling
Power
3222 Active power ■ 3 Int32 1000 kW = 1000 ■ ■
scaling
Reactive Power
Apparent Power
PF and
3225 Power factor ■ 3 float32 1.00 = 100 cos ■ ■
scaling
3226 Energy Eexp ■ 3 UInt16 1=1 ■ ■
3227 Eexp/10^4 ■ 3 UInt16 10^4 = 1 ■ ■
3228 Eexp/10^8 ■ 3 UInt16 10^8 = 1 ■ ■
3229 Energy EqExp ■ 3 UInt16 1=1 ■ ■
3230 EqExp/10^4 ■ 3 UInt16 10^4 = 1 ■ ■
3231 EqExp/10^8 ■ 3 UInt16 10^8 = 1 ■ ■
3232 Energy Eimp ■ 3 UInt16 1=1 ■ ■
3233 Eimp/10^4 ■ 3 UInt16 10^4 = 1 ■ ■
3234 Eimp/10^8 ■ 3 UInt16 10^8 = 1 ■ ■
3235 Energy EqImp ■ 3 UInt16 1=1 ■ ■
3236 EqImp/10^4 ■ 3 UInt16 10^4 = 1 ■ ■
3237 EqImp/10^8 ■ 3 UInt16 10^8 = 1 ■ ■
Tanφ
3238 Tanφ ■ 3 float32 1.000 = 1000 scaling ■ ■
Phase current
3239 ■ 3 UInt32 1A=1 ■ ■ ■
IL
Average Line- Voltage
3240 Line voltage ■ 3 UInt32 1000 V = 1000 scaling ■ ■ ■
Average Line-
Voltage
3241 to-neutral ■ 3 UInt32 1000 V = 1000 ■ ■ ■
scaling
voltage
Harmonics of
3256 ■ 3 UInt32 1%=1 ■ ■ ■
IL1
Harmonics of
3276 ■ 3 UInt32 1%=1 ■ ■ ■
IL2
Harmonics of
3296 ■ 3 UInt32 1%=1 ■ ■ ■
IL3
Harmonics of
3316 ■ 3 UInt32 1%=1 ■ ■ ■
VL1
Harmonics of
3336 ■ 3 UInt32 1%=1 ■ ■ ■
VL2
P5/EN M/11A 87

Code Scalling
Harmonics of
3356 ■ 3 UInt32 1%=1 ■ ■ ■
VL3
3381 Temperature 1 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
Temperature
3390 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
10
Temperature
3391 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
11
Temperature
3392 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
12
Temperature
3393 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
13
Temperature
3394 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
14
Temperature
3395 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
15
Temperature
3396 ■ 3 Int16 1 °C = 1 / 1F = 1 ■ ■ ■ ■
16
Fault
Last fault 3, 6 value
3410 ■ ■ float32 1.00 xIn = 100 ■ ■ ■
current scaling
Fault
Fault current value
3411 ■ 3 float32 1.00 xIn = 100 ■ ■ ■
I> scaling
Fault
Fault current value
3412 ■ 3 float32 1.00 xIn = 100 ■ ■ ■
I>> scaling
Fault
Fault current value
3413 ■ 3 float32 1.00 xIn = 100 ■ ■ ■
I>>> scaling
Fault
3415 ■ 3 float32 1.00 ohm = 100 ■
reactance
OK=0, NegX=1, BigX=2,
LongFlt=3, NoDI=4,
Algorithm NoPreFlt=5, NoPostFlt=6,
3416 ■ 3 UInt8 ■
condition ShrtFlt=7, PreUns=8,
FltUns=9, PostUns=10,
Blocked=11, Off=12
Fault
Last fault Io 1.00 pu = 100 value
3430 ■ 3 float32 ■ ■ ■
current scaling
Fault
Fault current 1.00 pu = 100 value
3431 ■ 3 float32 ■ ■ ■
Io> scaling
Fault
3432 ■ 3 float32 ■ ■ ■
Io>> scaling
Fault
3433 ■ 3 float32 ■ ■ ■
Io>>> scaling
88 P5/EN M/11A

Code Scalling
Fault
3434 ■ 3 float32 ■ ■ ■
Io>>>> scaling
Fault
3435 ■ 3 float32 ■ ■ ■
Io>>>>> scaling
Fault
3436 Last fault Ioφ> ■ 3 float32 1.00 pu = 100 value ■ ■
current scaling
Fault
Fault current
3437 ■ 3 float32 1.00 pu = 100 value ■ ■
Ioφ>
scaling
Fault
Fault current
3438 ■ 3 float32 1.00 pu = 100 value ■ ■
Ioφ>>
scaling
Fault
Fault current
3439 ■ 3 float32 1.00 pu = 100 value ■ ■
Ioφ>>>
scaling
Fault
Fault current value
3440 ■ 3 float32 1.00 xIn = 100 ■ ■ ■
SOTF scaling
Fault
Fault voltage value
3441 ■ 3 float32 1.0 % = 10 ■ ■ ■
Uo> scaling
Fault
Fault voltage value
3442 ■ 3 float32 1.0 % = 10 ■ ■ ■
Uo>> scaling
Fault
Fault voltage value
3443 ■ 3 float32 1.0 % = 10 ■ ■ ■
Uo>>> scaling
Fault
Fault current value
3444 ■ 3 float32 ■ ■
Io'> 1.000 pu = 1000 scaling
Fault
Fault current value
3445 ■ 3 float32 ■ ■
Io'>> 1.000 pu = 1000 scaling
Fault
Fault current value
3446 ■ 3 float32 ■ ■
Io'>>> 1.000 pu = 1000 scaling
Fault
Fault value value
3447 ■ 3 float32 ■ ■
IoUo> scaling
1000 %Pno = 1000
Fault
3448 Fault value ■ 3 float32 value ■ ■
IoUo>> 1000 %Pno = 1000 scaling
Fault
Fault current value
3449 ■ 3 float32 1.00 xIn = 100 ■ ■ ■
I2> scaling
Cold load
3452 ■ 3 UInt8 Start=1, Timeout=2 ■ ■ ■
pickup
Inrush Start=1, Timeout=2

3453 ■ 3 UInt8 ■ ■ ■
detection
Fault
Fault value df/ value
3454 ■ 3 float32 1.00 Hz/s = 100 ■ ■
dt> scaling
Fault
Fault value df/ value
3455 ■ 3 float32 1.00 Hz/s = 100 ■ ■
dt>> scaling
P5/EN M/11A 89
Statistics and Virtual Input/Output

Code Scalling
3501 DI1 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3502 DI2 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3503 DI3 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3504 DI4 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3505 DI5 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3506 DI6 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3507 DI7 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3508 DI8 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3509 DI9 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3510 DI10 counter ■ ■ 3, 6 UInt16 1=1 ■ ■ ■ ■
3511 DI11 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3512 DI12 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3513 DI13 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3514 DI14 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3515 DI15 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3516 DI16 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3517 DI17 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3518 DI18 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3519 DI19 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3520 DI20 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3521 DI21 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3522 DI22 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3523 DI23 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3524 DI24 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3525 DI25 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3526 DI26 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3527 DI27 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3528 DI28 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3529 DI29 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3530 DI30 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3531 DI31 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
3532 DI32 counter ■ ■ 3, 6 UInt16 1=1 ■ ■
Shot1 start 3, 6
3571 ■ ■ UInt16 1=1 ■ ■
counter
Shot2 start 3, 6
3572 ■ ■ UInt16 1=1 ■ ■
counter
Shot3 start 3, 6
3573 ■ ■ UInt16 1=1 ■ ■
counter
Shot4 start 3, 6
3574 ■ ■ UInt16 1=1 ■ ■
counter
Shot5 start 3, 6
3575 ■ ■ UInt16 1=1 ■ ■
counter
AR start 3, 6
3576 ■ ■ UInt16 1=1 ■ ■
counter
90 P5/EN M/11A

Code Scalling
3577 AR fail counter ■ ■ 3, 6 UInt16 1=1 ■ ■
AR shot 1, 2, 3, 4, 5, END=6
3578 ■ 3 UInt8 ■ ■
number
Critical AR
3579 req. ■ 3 UInt16 1=1 ■ ■
Recloser
3580 ■ 3 UInt16 1=1 ■ ■
locked
Recloser
3581 running ■ 3 UInt16 1=1 ■ ■
3582 Final trip ■ 3 UInt16 1=1 ■ ■
Auto-Recloser
3583 ■ 3 UInt16 1=1 ■ ■
on
3611 Motor starting ■ 3 1=1 ■
3612 Motor running ■ 3 1=1 ■
Voltage
3613 ■ 3 UInt8 Low=0, ok=1 ■ ■ ■
interrupt
OK=0, Low=1, High=2,

3614 Voltage status ■ 3 UInt8 Low/High=3, (OK)=4, (Low) ■ ■ ■
=5, (High)=6, (Low)/High=7
3615 Timer 1 status ■ ■ 3, 6 UInt8 0=1, 1=2 ■ ■ ■ ■
CBWear
3619 ■ 3 UInt8 1=1 ■ ■ ■ ■
Alarm 1
CBWear
3620 ■ 3 UInt8 1=1 ■ ■ ■ ■
Alarm 2
Logic output
3621 ■ 3 UInt8 1=1 ■ ■ ■ ■
states 1...8
Logic output
3622 ■ 3 UInt8 1=1 ■ ■ ■ ■
states 9...16
Logic output
3623 ■ 3 UInt8 1=1 ■ ■ ■ ■
states 17...20
Virtual outputs
3626 ■ 3 UInt8 1=1 ■ ■ ■ ■
1...10
Virtual outputs
3627 ■ 3 UInt8 1=1 ■ ■ ■ ■
11...20
3631 Sync1 request ■ 3 UInt8 1=1 ■ ■
3632 Sync1 OK ■ 3 UInt8 1=1 ■ ■
3633 Bypass ■ ■ 3, 6 UInt8 1=1 ■ ■
3634 Sync1 fail ■ 3 UInt8 1=1 ■ ■
3657 Virtual input 1 ■ ■ 3, 6 UInt8 0, 1 ■ ■ ■ ■
P5/EN M/11A 91

Code Scalling
Virtual input 3, 6 0, 1
3666 ■ ■ UInt8 ■ ■ ■ ■
10
3667 ■ ■ UInt8 ■ ■ ■ ■
11
3668 ■ ■ UInt8 ■ ■ ■ ■
12
3669 ■ ■ UInt8 ■ ■ ■ ■
13
3670 ■ ■ UInt8 ■ ■ ■ ■
14
3671 ■ ■ UInt8 ■ ■ ■ ■
15
3672 ■ ■ UInt8 ■ ■ ■ ■
16
3673 ■ ■ UInt8 ■ ■ ■ ■
17
3674 ■ ■ UInt8 ■ ■ ■ ■
18
3675 ■ ■ UInt8 ■ ■ ■ ■
19
3676 ■ ■ UInt8 ■ ■ ■ ■
20
92 P5/EN M/11A
Minimum and Maximum Value

Writ- Function Setting for
Address Name Read Data Type Scalling P5U20 P5V20 P5F30 P5M30
e Code Scalling
Minimum Frequen-
4001 ■ ■ 3, 6 float32 50.000 Hz = 5000 ■ ■ ■ ■
frequency cy scaling
Minimum Power
4002 ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
active power scaling
Minimum Power
4003 ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
react. power scaling
Minimum
Power
4004 apparent ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
scaling
power
PF and
Min power 3, 6 cos
4005 ■ ■ float32 1.000 = 1000 ■ ■
factor scaling
4006 Minimum of Io ■ ■ 3, 6 float32 1.0 % = 10 Io scaling ■ ■ ■
Iovs
4007 Minimum of Io' ■ ■ 3, 6 float32 1.0 % = 10 ■ ■ ■
scaling
Demand
Power
4008 Minimum ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
scaling
active power
Demand
Power
4009 minimum ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
scaling
reactive power
Demand
Minimum Power
4010 ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
apparent scaling
power
Demand PF and
4011 minimum ■ ■ 3, 6 float32 1.000 = 1000 cos ■ ■
power factor scaling
RMS Demand
Power
4012 mini active ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
scaling
power
RMS Demand
Power
4013 min reactive ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
scaling
power
RMS Demand
Power
4014 mini apparent ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
scaling
power
Minimum of 3, 6
4015 ■ ■ UInt32 1A=1 ■ ■ ■
IL1
Minimum of 3, 6
4016 ■ ■ UInt32 1A=1 ■ ■ ■
IL2
Minimum of 3, 6
4017 ■ ■ UInt32 1A=1 ■ ■ ■
IL3
RMS minimum 3, 6
4018 ■ ■ UInt32 1A=1 ■ ■ ■
of IL1
RMS minimum 3, 6
4019 ■ ■ UInt32 1A=1 ■ ■ ■
of IL2
RMS minimum 3, 6
4020 ■ ■ UInt32 1A=1 ■ ■ ■
of IL3
Demand
4021 Minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL1
Demand
4022 Minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL2
Demand
4023 Minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL3
P5/EN M/11A 93

e Code Scalling
RMS Demand
4024 minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL1
RMS Demand
4025 minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL2
RMS Demand
4026 minimum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL3
Minimum of Io IoCSH
4027 ■ ■ 3, 6 float32 1.0 pu = 10 ■ ■ ■
CSH scaling
Minimum of Voltage
4028 ■ ■ 3, 6 float32 1.0 % = 10 ■ ■ ■
Uo scaling
Minimum of Voltage
4030 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U12 scaling
Minimum of Voltage
4031 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U23 scaling
Minimum of Voltage
4032 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U31 scaling
Minimum VL1 Voltage

4033 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS voltage scaling
Minimum VL2 Voltage

4034 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS voltage scaling
Minimum VL3 Voltage

4035 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS voltage scaling
Maximum Frequen-
4101 ■ ■ 3, 6 float32 50.000 Hz = 5000 ■ ■ ■ ■
frequency cy scaling
Maximum Power
4102 ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
active power scaling
Maximum Power
4103 ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
react. power scaling
Maximum
Power
4104 apparent ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
scaling
power
PF and
Max power 3, 6 cos
4105 ■ ■ float32 1.000 = 1000 ■ ■
factor scaling
4106 Maximum of Io ■ ■ 3, 6 float32 1.0 % = 10 Io scaling ■ ■ ■
Maximum of Iovs
4107 ■ ■ 3, 6 float32 1.0 % = 10 ■ ■ ■
Io' scaling
Demand
Power
4108 Maximum ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
scaling
active power
Demand
Power
4109 maximum ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
scaling
reactive power
Demand
Maximum Power
4110 ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
apparent scaling
power
Demand PF and
4111 maximum ■ ■ 3, 6 float32 1.000 = 1000 cos ■ ■
power factor scaling
RMS Demand
Power
4112 Max active ■ ■ 3, 6 Int32 1000 kW = 1000 ■ ■
scaling
power
RMS Demand
Power
4113 max reactive ■ ■ 3, 6 Int32 1000 kVAr = 1000 ■ ■
scaling
power
94 P5/EN M/11A

e Code Scalling
RMS Demand
Power
4114 Max apparent ■ ■ 3, 6 Int32 1000 kVA = 1000 ■ ■
scaling
power
Maximum of 3, 6
4115 ■ ■ UInt32 1A=1 ■ ■ ■
IL1
Maximum of 3, 6
4116 ■ ■ UInt32 1A=1 ■ ■ ■
IL2
Maximum of 3, 6
4117 ■ ■ UInt32 1A=1 ■ ■ ■
IL3
RMS
4118 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL1
RMS
4119 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL2
RMS
4120 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL3
Demand
4121 Maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL1
Demand
4122 Maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL2
Demand
4123 Maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL3
RMS Demand
4124 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL1
RMS Demand
4125 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL2
RMS Demand
4126 maximum of ■ ■ 3, 6 UInt32 1A=1 ■ ■ ■
IL3
Maximum of Io IoCSH
4127 ■ ■ 3, 6 float32 1.0 pu = 10 ■ ■ ■
CSH scaling
Maximum of Voltage
4128 ■ ■ 3, 6 float32 1.0 % = 10 ■ ■ ■
Uo scaling
Maximum of Voltage
4130 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U12 scaling
Maximum of Voltage
4131 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U23 scaling
Maximum of Voltage
4132 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
U31 scaling
Maximum VL1 Voltage

4133 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS Voltage scaling
Maximum VL2 Voltage

4134 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS Voltage scaling
Maximum VL3 Voltage

4135 ■ ■ 3, 6 UInt32 1000 V = 1000 ■ ■ ■
RMS Voltage scaling
4299 Arc Io state ■ 3 UInt8 1=1 ■ ■
4300 Arc I state ■ 3 UInt8 1=1 ■ ■
Clear I/O units'

4301 ■ ■ 3, 6 Clear=1
registers
Release all 3, 6
4302 ■ ■ UInt8 Release=1 ■ ■
latches
P5/EN M/11A 95

e Code Scalling
4303 Arc Stages ■ 3 UInt8 1=1 ■ ■
Activated arc
4304 ■ 3 UInt16 1=1 ■ ■
sensors
96 P5/EN M/11A
Settings

e Code Scalling
ARC setting items:
I>int. pick-up 3, 6
5001 ■ ■ float32 1.00 xIn = 100 ■ ■
value
Io>int. pick-up 3, 6
5002 ■ ■ float32 1.00 xIn = 100 ■ ■
value
Arc stage 1 3, 6 Off=0, On=1
5003 ■ ■ UInt8 ■ ■
enabled
5004 ■ ■ UInt8 ■ ■
enabled
5005 ■ ■ UInt8 ■ ■
enabled
5006 ■ ■ UInt8 ■ ■
enabled
5007 ■ ■ UInt8 ■ ■
enabled
5008 ■ ■ UInt8 ■ ■
enabled
5009 ■ ■ UInt8 ■ ■
enabled
5010 ■ ■ UInt8 ■ ■
enabled
5011 Stage 1 Mode ■ ■ 3, 6 UInt8 Light=0, LightAndI=1 ■ ■
Trip 1 delay
5019 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 2 delay
5020 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 3 delay
5021 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 4 delay
5022 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 5 delay
5023 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 6 delay
5024 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 7 delay
5025 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Trip 8 delay
5026 ■ ■ 3, 6 UInt8 1=1 ■ ■
[x1ms]
Min. hold time

5027 ■ ■ 3, 6 UInt32 1=1 ■ ■
[x1ms]
Min. hold
5028 ■ ■ 3, 6 UInt32 1=1 ■ ■
time2 [x1ms]
Min. hold
5029 ■ ■ 3, 6 UInt32 1=1 ■ ■
time3 [x1ms]
P5/EN M/11A 97

e Code Scalling
Min. hold
5030 ■ ■ 3, 6 UInt32 1=1 ■ ■
time4 [x1ms]
Min. hold
5031 ■ ■ 3, 6 UInt32 1=1 ■ ■
time5 [x1ms]
Min. hold
5032 ■ ■ 3, 6 UInt32 1=1 ■ ■
time6 [x1ms]
Min. hold
5033 ■ ■ 3, 6 UInt32 1=1 ■ ■
time7 [x1ms]
Min. hold
5034 ■ ■ 3, 6 UInt32 1=1 ■ ■
time8 [x1ms]
ColdLoad/Inrush setting:
Enable for 3, 6 Off=0, On=1

5101 ■ ■ UInt8 ■ ■ ■
CLP/Inrush
5102 Idle current ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■ ■
5103 Pickup current ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■ ■
CLPU
CLPU dead 3, 6 dead time
5104 ■ ■ float32 ■ ■ ■
time scaling
1.00 s = 100
5105 Maximum time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
Pickup for 2nd 3, 6

5106 ■ ■ UInt32 ■ ■ ■
harmonic 1%=1
Cold load
5107 pickup event ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
on
Cold load
5108 pickup event ■ ■ 3, 6 UInt8 ■ ■ ■
off Off=0, On=1
Inrush event 3, 6
5109 ■ ■ UInt8 Off=0, On=1 ■ ■ ■
on
Inrush event 3, 6
5110 ■ ■ UInt8 Off=0, On=1 ■ ■ ■
off
CLPU event 3, 6
5111 ■ ■ UInt8 Off=0, On=1 ■ ■ ■
enabled
CLPU event 3, 6
5112 ■ ■ UInt8 Off=0, On=1 ■ ■ ■
disabled
OverCurrent I> setting:
5151 Enable for I> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
5152 Pick-up value ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■ ■
DT=0, IEC=1, IEEE=2,

Delay curve
5156 ■ ■ 3, 6 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
UInt8 Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

Delay type 3, 6 LTI=4, LTEI=5, LTVI=6, MI=
5160 ■ ■ ■ ■ ■
7, STI=8, STEI=9, RI=10,
UInt8 RXIDG=11
Operation
5164 ■ ■ 3, 6 ■ ■ ■
delay float32 1.00 s = 100
Inv. time 3, 6
5168 ■ ■ ■ ■ ■
coefficient float32 1.00 = 100
5172 Reset time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
Inrush status 3, 6
5176 ■ ■ Off=0, On=1 ■ ■ ■
for I> UInt8
5180 SOL use by I> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
SOL
5184 Operation ■ ■ 3, 6 ■ ■ ■
98 P5/EN M/11A

e Code Scalling
SOL Inv. time 3, 6

5188 ■ ■ ■ ■ ■
CLP status for 3, 6
5192 ■ ■ Off=0, On=1 ■ ■ ■
I> UInt8
CLP Pick-up 3, 6
5196 ■ ■ ■ ■ ■
value float32 1.00 xIn = 100
CLP
5200 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
5204 ■ ■ ■ ■ ■
Include 3, 6
5208 ■ ■ Off=0, On=1 ■ ■ ■
harmonics UInt8
OverCurrent I>> setting:
5251 Enable for I>> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■

Delay curve
5256 ■ ■ 3, 7 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
DT=0, NI=1, VI=2, EI=3,

5260 ■ ■ ■ ■ ■
7, STI=8, STEI=9, RI=10,
UInt8 RXIDG=11
Operation
5264 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
5268 ■ ■ ■ ■ ■
Inrush status 3, 6 Off=0, On=1
5272 ■ ■ ■ ■ ■
for I>> UInt8
SOL use by 3, 6 Off=0, On=1
5276 ■ ■ ■ ■ ■
I>> UInt8
SOL
5280 Operation ■ ■ 3, 6 ■ ■ ■
SOL Inv. time 3, 6
5284 ■ ■ ■ ■ ■
CLP status for 3, 6 Off=0,On=1
5288 ■ ■ ■ ■ ■
I>> UInt8
CLP Pick-up 3, 6
5292 ■ ■ float32 1.00 xIn = 100 ■ ■ ■
value
CLP
5296 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
5300 ■ ■ ■ ■ ■
Include 3, 6
5304 ■ ■ Off=0, On=1 ■ ■ ■
harmonics UInt8
OverCurrent I>>> setting:

5351 ■ ■ UInt8 ■ ■ ■
I>>>
Operation
5356 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inrush status 3, 6
5360 ■ ■ Off=0, On=1 ■ ■ ■
for I>>> UInt8
SOL use by 3, 6
5364 ■ ■ Off=0, On=1 ■ ■ ■
I>>> UInt8
P5/EN M/11A 99

e Code Scalling
SOL
5368 Operation ■ ■ 3, 6 ■ ■ ■
CLP status for 3, 6
5372 ■ ■ Off=0, On=1 ■ ■ ■
I>>> UInt8
CLP Pick-up 3, 6
5376 ■ ■ ■ ■ ■
CLP
5380 Operation ■ ■ 3, 6 ■ ■ ■
SOTF setting:

5401 ■ ■ UInt8 ■ ■ ■
SOTF
Dead line
5403 detection ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
SOTF active 3, 6
5404 ■ ■ float32 1.00 s = 100 ■ ■ ■
Timer
DI1=1, DI2=2, ..., DI19=19,
DI20=20, Arc1=25, Arc2=
26, BI=27, VI1=29, VI2=30,
VI3=31, VI4=32, DO1(B)
=33, DO2(B)=34, DO3(B)
=35, Watchdog=36, SF=37,
SF=38, ..., SF=40, SF=41,
BO=42, DO1(C)=43, DO2
(C)=44, DO3(C)=45, DO4
(C)=46, LedAl=49, LedTr=
50, LedA=51, LedB=52,
LedC=53, LedDR=54,
VO1=55, VO2=56, ...,
VO5=59, VO6=60, DI21=
Dead line 65, DI22=66, ..., DI39=83,
5405 ■ ■ 3, 6 UInt16 ■ ■ ■
detection input DI40=84, F1=85, F2=86, ...,
F6=90, F7=91, DO1(D)=97,
DO2(D)=98, DO3(D)=99,
SF=100, DO1(E)=101,
DO2(E)=102, NI1=129,
NI2=130, ..., NI63=191,
NI64=192, POC1=193,
POC2=194, ..., POC15=
207, POC16=208, VI5=
225, VI6=226, ..., VI19=
239, VI20=240, VO7=257,
VO8=258, ..., VO19=269,
VO20=270, NI65=289,
NI66=290, ..., NI127=351,
NI128=352
Iφ> setting
5411 Enable for Iφ> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
5412 Pick-up value ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■
Direction 3, 6 Dir+Backup=0, Undir=1,

5416 ■ ■ UInt8 ■ ■
mode Dir=2
5420 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■

Delay curve
5424 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

5428 ■ ■ UInt8 ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
5432 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inv. time 3, 6
5436 ■ ■ float32 1.00 = 100 ■ ■
coefficient
100 P5/EN M/11A


e Code Scalling
5440 Reset time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
Inrush_Stat
5444 ■ ■ 3, 6 ■ ■
for Iφ> UInt8 Off=0, On=1
SOL_Stat for
5448 ■ ■ 3, 6 ■ ■
Iφ> UInt8 Off=0, On=1
SOL
5452 Operation ■ ■ 3, 6 ■ ■
SOL Inv. time 3, 6
5456 ■ ■ ■ ■
CLP_Stat for
5460 ■ ■ 3, 6 ■ ■
Iφ> UInt8 Off=0, On=1
CLP Pick-up 3, 6
5464 ■ ■ ■ ■
CLP
5468 Operation ■ ■ 3, 6 ■ ■
CLP Inv. time 3, 6
5472 ■ ■ ■ ■
Iφ> > setting
Enable for
5481 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Iφ>>
Direction 3, 6 Dir+Backup=0,Undir=1,
5486 ■ ■ UInt8 ■ ■
mode Dir=2
5490 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■

Delay curve
5494 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

5498 ■ ■ UInt8 ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
5502 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inv. time 3, 6
5506 ■ ■ float32 1.00 = 100 ■ ■
coefficient
Inrush_Stat
5514 ■ ■ 3, 6 ■ ■
for Iφ>> UInt8 Off=0, On=1
SOL_Stat for
5518 ■ ■ 3, 6 ■ ■
Iφ>> UInt8 Off=0, On=1
SOL
5522 Operation ■ ■ 3, 6 ■ ■
SOL Inv. time 3, 6
5526 ■ ■ ■ ■
CLP_Stat for
5530 ■ ■ 3, 6 ■ ■
Iφ>> UInt8 Off=0, On=1
CLP Pick-up 3, 6
5534 ■ ■ ■ ■
CLP
5538 Operation ■ ■ 3, 6 ■ ■
CLP Inv. time 3, 6
5542 ■ ■ ■ ■
P5/EN M/11A 101


e Code Scalling
Iφ> >> setting:
Enable for
5551 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Iφ>>>

5556 ■ ■ UInt8 ■ ■
mode Dir=2
5560 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■
Operation
5564 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inrush_Stat
5568 ■ ■ 3, 6 ■ ■
for Iφ>>> UInt8 Off=0, On=1
SOL_Stat for
5572 ■ ■ 3, 6 ■ ■
Iφ>>> UInt8 Off=0, On=1
SOL
5576 Operation ■ ■ 3, 6 ■ ■
CLP_Stat for
5580 ■ ■ 3, 6 ■ ■
Iφ>>> UInt8 Off=0,On=1
CLP Pick-up 3, 6
5584 ■ ■ ■ ■
CLP
5588 Operation ■ ■ 3, 6 ■ ■
Iφ> >>> setting:
Enable for
5601 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Iφ>>>>

5606 ■ ■ UInt8 ■ ■
mode Dir=2
5610 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■
Operation
5614 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inrush_Stat
5618 ■ ■ 3, 6 ■ ■
for Iφ>>>> UInt8 Off=0, On=1
SOL_Stat for
5622 ■ ■ 3, 6 ■ ■
Iφ>>>> UInt8 Off=0, On=1
SOL
5626 Operation ■ ■ 3, 6 ■ ■
CLP_Stat for
5630 ■ ■ 3, 6 ■ ■
Iφ>>>> UInt8 Off=0, On=1
CLP Pick-up 3, 6
5634 ■ ■ ■ ■
CLP
5638 Operation ■ ■ 3, 6 ■ ■
P< setting:
5651 Enable for P< ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
5652 Pick-up value ■ ■ 3, 6 float32 1.0 %Sn = 10 ■ ■
Operation
5656 ■ ■ 3, 6 float32 1.0 s = 10 ■ ■
delay
P<< setting:

5701 ■ ■ UInt8 ■ ■
P<<
102 P5/EN M/11A


e Code Scalling
5702 Pick-up value ■ ■ 3, 6 Int32 1 %Sn = 1 ■ ■
Operation
5706 ■ ■ 3, 6 float32 1.0 s = 10 ■ ■
delay
I< setting:
5751 Enable for I< ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
5752 Pick-up value ■ ■ 3, 6 UInt32 1 %In = 1 ■ ■
Operation
5756 ■ ■ 3, 6 float32 1.0 s = 10 ■ ■
delay
I2>I1 setting:
Enable for I2/ 3, 6 Off=0, On=1

5801 ■ ■ UInt8 ■ ■ ■
I1>
Pick-up value 3, 6
5802 ■ ■ UInt32 1%=1 ■ ■ ■
K2
Operation
5806 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
I2> setting:
5901 Enable for I2> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■

Delay curve
5906 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

5910 ■ ■ UInt8 ■ ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
5914 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
5918 ■ ■ float32 1.00 = 100 ■ ■ ■
coefficient
Ist> setting:
5951 Enable for Ist> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
5952 Delay type ■ ■ 3, 6 float32 DT=0, INV=1 ■ ■
Motor start 3, 6
5953 ■ ■ float32 ■ ■
time 1.0 s = 10
Ilr> setting:
6001 Enable for Ilr> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
6002 Pick-up value ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
6003 Delay type ■ ■ 3, 6 UInt8 DT=0, INV=1 ■ ■
Operation
6004 ■ ■ 3, 6 float32 1.0 s = 10 ■ ■
delay
N> setting:
6051 Enable for N> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Max motor Hot 3, 6

6052 ■ ■ UInt32 1=1 ■ ■
starts/hour
Max motor
6053 cold starts/ ■ ■ 3, 6 UInt32 1=1 ■ ■
hour
Min time
6054 between ■ ■ 3, 6 float32 1.0 min = 10 ■ ■
motor starts
Motor T> setting:

6101 ■ ■ UInt8 ■ ■
Motor 49M>
P5/EN M/11A 103


e Code Scalling
Basic current
6102 ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■
setting
6106 Factor k ■ ■ 3, 6 float32 1.00 = 100 ■ ■
Heating time 3, 6
6110 ■ ■ float32 1.0 min = 10 ■ ■
constant
Time constant
6114 for motor ■ ■ 3, 6 float32 1.0 min = 10 ■ ■
starting
Cooling time 3, 6
6118 ■ ■ float32 1.0 min = 10 ■ ■
constant
Unbalance 3, 6
6130 ■ ■ float32 1.0 = 10 ■ ■
factor
Thermal alarm 3, 6
6134 ■ ■ UInt32 1%=1 ■ ■
value
Reserve time 3, 6
6138 ■ ■ float32 1.0 min = 10 ■ ■
thermal alarm
Temperature 3, 6 Current=0, Ambient=1
6142 ■ ■ UInt8 ■ ■
based mode
Nominal
6146 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
ambient temp
Max object
6150 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Alarm
6154 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Min ambient
6158 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Default
6162 ambient ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Feeder T> setting:

6201 ■ ■ UInt8 ■ ■
feeder 49F>
Basic current
6202 ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■
setting
6206 Factor k ■ ■ 3, 6 float32 1.00 = 100 ■ ■
Heating time 3, 6
6210 ■ ■ float32 1.0 min = 10 ■ ■
constant
Thermal alarm 3, 6
6214 ■ ■ UInt32 1%=1 ■ ■
value
Reserve time 3, 6
6218 ■ ■ float32 1.0 min = 10 ■ ■
thermal alarm
Temperature 3, 6 Current=0, Ambient=1
6222 ■ ■ UInt8 ■ ■
based mode
Nominal
6226 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
ambient temp
Max object
6230 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Alarm
6234 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Min ambient
6238 ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Default
6242 ambient ■ ■ 3, 6 Int16 1 °C = 1 ■ ■
temperature
Io> setting:
6261 Enable for Io> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
104 P5/EN M/11A


e Code Scalling
6262 Pick-up value ■ ■ 3, 6 float32 1.000 pu = 1000 ■ ■ ■

Delay curve
6266 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

6270 ■ ■ UInt8 ■ ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
6274 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
6278 ■ ■ float32 1.00 = 100 ■ ■ ■
coefficient
Network
6282 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush status 3, 6
6291 ■ ■ Off=0, On=1 ■ ■ ■
for Io> UInt8
SOL use for 3, 6
6295 ■ ■ Off=0, On=1 ■ ■ ■
Io> UInt8
SOL
6299 Operation ■ ■ 3, 6 ■ ■ ■
SOL Inv. time 3, 6
6303 ■ ■ ■ ■ ■
CLP_Stat for 3, 6
6307 ■ ■ Off=0, On=1 ■ ■ ■
Io> UInt8
CLP Pick-up 3, 6
6311 ■ ■ ■ ■ ■
CLP
6315 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
6319 ■ ■ ■ ■ ■
Io>> setting:

6331 ■ ■ UInt8 ■ ■ ■
Io>>

Delay curve
6336 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

6340 ■ ■ UInt8 ■ ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
6344 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
6348 ■ ■ float32 ■ ■ ■
coefficient 1.00 = 100
Network
6352 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush status 3, 6
6356 ■ ■ Off=0, On=1 ■ ■ ■
for Io>> UInt8
SOL use for 3, 6
6360 ■ ■ Off=0, On=1 ■ ■ ■
Io>> UInt8
SOL
6364 Operation ■ ■ 3, 6 ■ ■ ■
SOL Inv. time 3, 6
6368 ■ ■ ■ ■ ■
P5/EN M/11A 105


e Code Scalling
CLP_Stat for 3, 6
6372 ■ ■ Off=0, On=1 ■ ■ ■
Io>> UInt8
CLP Pick-up 3, 6
6376 ■ ■ ■ ■ ■
CLP
6380 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
6384 ■ ■ ■ ■ ■
Io>>> setting:

6401 ■ ■ UInt8 ■ ■ ■
Io>>>
Operation
6406 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Network
6410 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush status 3, 6
6414 ■ ■ Off=0, On=1 ■ ■ ■
for Io>>> UInt8
SOL use for 3, 6
6418 ■ ■ Off=0, On=1 ■ ■ ■
Io>>> UInt8
SOL
6422 Operation ■ ■ 3, 6 ■ ■ ■
CLP_Stat for 3, 6
6426 ■ ■ Off=0, On=1 ■ ■ ■
Io>>> UInt8
CLP Pick-up 3, 6
6430 ■ ■ ■ ■ ■
CLP
6434 Operation ■ ■ 3, 6 ■ ■ ■
Io>>>> setting:

6451 ■ ■ UInt8 ■ ■ ■
Io>>>>
Operation
6456 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Network
6460 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush status 3, 6
6464 ■ ■ Off=0, On=1 ■ ■ ■
for Io>>>> UInt8
SOL use for 3, 6
6468 ■ ■ Off=0, On=1 ■ ■ ■
Io>>>> UInt8
SOL
6472 Operation ■ ■ 3, 6 ■ ■ ■
CLP_Stat for 3, 6
6476 ■ ■ Off=0, On=1 ■ ■ ■
Io>>>> UInt8
CLP Pick-up 3, 6
6480 ■ ■ ■ ■ ■
CLP
6484 Operation ■ ■ 3, 6 ■ ■ ■
Io>>>>> setting:

6501 ■ ■ UInt8 ■ ■ ■
Io>>>>>
106 P5/EN M/11A


e Code Scalling
Operation
6506 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Ioφ> setting:
Enable for
6551 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Ioφ>
Direction 3, 6 ResCap=0, Sector=1,

6552 ■ ■ UInt8 ■ ■
mode Undir=2
Res=0, Cap=1, DI1=2,
DI2=3, ..., DI19=20, DI20=
Char ctrl. in 21, Arc1=26, Arc2=27, BI=
6556 ■ ■ 3, 6 UInt8 28, VI1=30, VI2=31, VI3= ■ ■
ResCap mode
32, VI4=33, DI21=66,
DI22=67, ..., DI31=76,
DI32=77
6560 Pick-up value ■ ■ 3, 6 float32 1.000 pu = 1000 ■ ■
Uo setting for
6564 ■ ■ 3, 6 Int32 1.0 % = 10 ■ ■
Ioφ> stage
6568 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■
Pick up sector 3, 6
6572 ■ ■ Int16 ■ ■
size 1 ±° = 1
Delay curve
6576 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

6580 ■ ■ UInt8 ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
6584 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inv. time 3, 6
6588 ■ ■ float32 1.00 = 100 ■ ■
coefficient
Ioφ> > setting:
Enable for
6601 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Ioφ>>

6602 ■ ■ UInt8 ■ ■
mode Undir=2
DI2=3, ..., DI19=20, DI20=
6606 ■ ■ 3, 6 UInt8 28, VI1=30, VI2=31, VI3= ■ ■
ResCap mode
32, VI4=33, DI21=66,
DI22=67, ..., DI31=76,
DI32=77
Uo setting for
6614 ■ ■ 3, 6 Int32 1.0 % = 10 ■ ■
Ioφ>> stage
6618 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■
Pick up sector 3, 6
6622 ■ ■ Int16 ■ ■
size 1 ±° = 1
Delay curve
6626 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

6630 ■ ■ UInt8 ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
P5/EN M/11A 107


e Code Scalling
Operation
6634 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inv. time 3, 6
6638 ■ ■ float32 1.00 = 100 ■ ■
coefficient
Ioφ>>> setting:
Enable for
6651 ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Ioφ>>>

6652 ■ ■ UInt8 ■ ■
mode Undir=2
DI2=3, ..., DI19=20, DI20=
6656 ■ ■ 3, 6 UInt8 28, VI1=30, VI2=31, VI3= ■ ■
ResCap mode
32, VI4=33, DI21=66,
DI22=67, ..., DI31=76,
DI32=77
Uo setting for
6664 ■ ■ 3, 6 Int32 1.0 % = 10 ■ ■
Ioφ>>> stage
6668 Angle offset ■ ■ 3, 6 Int16 1°=1 ■ ■
Pick up sector 3, 6
6672 ■ ■ Int16 ■ ■
size 1 ±° = 1
Delay curve
6676 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

6680 ■ ■ UInt8 ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
6684 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Inv. time 3, 6
6688 ■ ■ float32 1.00 = 100 ■ ■
coefficient
IoWatt> setting:

6701 ■ ■ UInt8 ■ ■
IoUo>
Direction 3, 6 Forward=0, Reverse=1
6702 ■ ■ UInt8 ■ ■
mode
DI1=1, DI2=2, ..., DI19=19,
DI20=20, Arc1=25, Arc2=
3, 6 26, BI=27, VI1=29, VI2=30,
6706 Inhibit ctrl. ■ ■ UInt8 ■ ■
VI3=31, VI4=32, DI21=65,
DI22=66, ..., DI31=75,
DI32=76
DI1=1, DI2=2, ..., DI19=19,
DI20=20, Arc1=25, Arc2=
Timer instant 26, BI=27, VI1=29, VI2=30,
6710 ■ ■ 3, 6 ■ ■
delay ctrl. VI3=31, VI4=32, DI21=65,
DI22=66, ..., DI31=75,
UInt8 DI32=76
Pick-up
6714 ■ ■ 3, 6 float32 value ■ ■
Pick-up value 1.0 %Pno = 10 scaling
6718 Uo setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
Pick up sector 3, 6
6722 ■ ■ Int16 ■ ■
size 1 ±° = 1
Operation
6726 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
6730 SOL Mode ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
108 P5/EN M/11A


e Code Scalling
SOL
6734 Operation ■ ■ 3, 6 float32 ■ ■
delay 1.00 s = 100
None=0, Voltage=1, Time=
6738 Memory Mode ■ ■ 3, 6 UInt8 ■ ■
2, Both=3
6742 Uo setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
6746 Memory time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
IoWatt>> setting:

6751 ■ ■ UInt8 ■ ■
IoUo>>
6752 ■ ■ UInt8 ■ ■
mode
DI1=1, DI2=2, ..., DI19=19,
DI20=20, Arc1=25, Arc2=
3, 6 26, BI=27, VI1=29, VI2=30,
6756 Inhibit ctrl. ■ ■ UInt8 ■ ■
VI3=31, VI4=32, DI21=65,
DI22=66, ..., DI31=75,
DI32=76
DI1=1, DI2=2, ..., DI19=19,
DI20=20, Arc1=25, Arc2=
Timer instant 26, BI=27, VI1=29, VI2=30,
6760 ■ ■ 3, 6 UInt8 ■ ■
delay ctrl. VI3=31, VI4=32, DI21=65,
DI22=66, ..., DI31=75,
DI32=76
Pick-up
6764 ■ ■ 3, 6 float32 value ■ ■
Pick-up value 1.0 %Pno = 10 scaling
6768 Uo setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
Pick up sector 3, 6
6772 ■ ■ Int16 1 ±° = 1 ■ ■
size
Operation
6776 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
6780 SOL Mode ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
SOL
6784 Operation ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
None=0, Voltage=1, Time=

6788 Memory Mode ■ ■ 3, 6 UInt8 ■ ■
2, Both=3
6792 Uo setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
6796 Memory time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
U> setting:
6801 Enable for U> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
6802 Pick-up value ■ ■ 3, 6 Int32 1 %Un = 1 ■ ■ ■
Operation
6806 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
6811 Hysteresis ■ ■ 3, 6 float32 1.0 % = 10 ■ ■ ■
U>> setting:

6851 ■ ■ UInt8 ■ ■ ■
U>>
Operation
6856 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
P5/EN M/11A 109


e Code Scalling
U>>> setting:

6901 ■ ■ UInt8 ■ ■ ■
U>>>
Operation
6906 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
U< setting:
6951 Enable for U< ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
Operation
6956 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
U<< setting:

■ ■ UInt8 ■ ■ ■
7001 U<<
Operation
■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
7006 delay
U<<< setting:

7051 ■ ■ UInt8 ■ ■ ■
U<<<
Operation
7056 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
U1< setting:

7101 ■ ■ UInt8 ■ ■
U1<
7102 Pick-up value ■ ■ 3, 6 Int32 1 %Vn = 1 ■ ■
Operation
7106 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Low voltage
7110 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■
blocking
U1<< setting:

7151 ■ ■ UInt8 ■ ■
U1<<
7152 Pick-up value ■ ■ 3, 6 Int32 1 %Vn = 1 ■ ■
Operation
7156 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Low voltage
7160 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■
blocking
Uo> setting:

7201 ■ ■ UInt8 ■ ■ ■
Uo>
7202 Pick-up value ■ ■ 3, 6 Int32 1%=1 ■ ■ ■
110 P5/EN M/11A


e Code Scalling
Operation
7206 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Uo>> setting:

7251 ■ ■ UInt8 ■ ■ ■
Uo>>
7252 Pick-up value ■ ■ 3, 6 Int32 1%=1 ■ ■ ■
Operation
7256 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Uo>>> setting:

7301 ■ ■ UInt8 ■ ■ ■
Uo>>>
7302 Pick-up value ■ ■ 3, 6 Int32 1%=1 ■ ■ ■
Operation
7306 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
fX setting:
7351 Enable for fX ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
7352 Pick-up value ■ ■ 3, 6 float32 50.00 Hz = 5000 ■ ■ ■
Operation
7356 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Low voltage
7360 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■ ■
blocking
fXX setting:
7401 Enable for fXX ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
Operation
7406 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Low voltage
7410 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■ ■
blocking
f< setting:
7451 Enable for f< ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
Operation
7456 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Low voltage
7460 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■ ■
blocking
f<< setting:
7501 Enable for f<< ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
Operation
7506 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Low voltage
7510 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■ ■
blocking
CBFail setting:

7551 ■ ■ UInt8 ■ ■ ■ ■
CBF
Enable CBF 3, 6 Off=0, On=1
7552 ■ ■ UInt8 ■ ■ ■ ■
timer1
Timer1
7553 Operation ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Delay
P5/EN M/11A 111


e Code Scalling
Enable CBF 3, 6 Off=0, On=1

7554 ■ ■ UInt8 ■ ■ ■ ■
timer2
Timer 2
7555 Operation ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■ ■
Delay
Noncurrent
3, 6 I<Only=0, PoleDead=1,
7556 CBF reset ■ ■ UInt8 ■ ■ ■ ■
ProtRst=2
mode
Ext. CBF reset 3, 6 I<Only=0, PoleDead=1,
7557 ■ ■ UInt8 ■ ■ ■ ■
mode ProtRst=2
7558 I< current set ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■ ■
7559 Io< current set ■ ■ 3, 6 float32 1.000 pu = 1000 ■ ■ ■
Io'< current 3, 6 1.000 pu = 1000

7560 ■ ■ float32 ■ ■ ■
set
Ih2> setting:

7601 ■ ■ UInt8 ■ ■ ■
Ih2>
7602 Pick-up value ■ ■ 3, 6 UInt32 1%=1 ■ ■ ■
Operation
7603 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Ih5> setting:

7651 ■ ■ UInt8 ■ ■ ■
Ih5>
7652 Pick-up value ■ ■ 3, 6 UInt32 1%=1 ■ ■ ■
Operation
7653 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
CT setting:

7701 ■ ■ UInt8 ■ ■ ■
CTS
CTS Operate 3, 6
7702 ■ ■ UInt8 3I only=0, I0&U0=1, Both=2 ■ ■ ■
mode
CTS output 3, 6 DI1=1, DI2=2, ..., DI39=39,
7703 ■ ■ UInt16 ■ ■ ■
reset DI40=40
Operation
7704 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Residual 3, 6
7721 ■ ■ float32 1.00 xIn = 100 ■ ■
current>
Residual
7722 ■ ■ 3, 6 Int32 1 %Un = 1 ■ ■
voltage<
VT setting:

7751 ■ ■ UInt8 ■ ■ ■
VTS
7752 U2> setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
7753 I2< setting ■ ■ 3, 6 float32 1.0 % = 10 ■ ■
Operate
Operation
7754 ■ ■ 3, 6 float32 1.00 s = 100 delay ■ ■
delay
scaling
VTS output 3, 6 DI1=1, DI2=2, ..., DI39=39,

■ ■ UInt16 ■ ■
7755 reset DI40=40
DI for MCB DI1=1, DI2=2, ..., DI39=39,
■ ■ 3, 6 UInt16 ■ ■
7756 position DI40=40
Iovs> setting:
7761 Enable for Io'> ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■ ■
112 P5/EN M/11A


e Code Scalling

Delay curve
7766 ■ ■ 3, 6 UInt8 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
Prg2=6, Prg3=7
DT=0, NI=1, VI=2, EI=3,

7770 ■ ■ UInt8 ■ ■ ■
7, STI=8, STEI=9, RI=10,
RXIDG=11
Operation
7774 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
7778 ■ ■ float32 1.00 = 100 ■ ■ ■
coefficient
Network
7782 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush_Stat 3, 6
7791 ■ ■ Off=0, On=1 ■ ■ ■
for Io'> UInt8
SOL_Stat for 3, 6
7795 ■ ■ Off=0, On=1 ■ ■ ■
Io'> UInt8
SOL
7799 Operation ■ ■ 3, 6 ■ ■ ■
SOL Inv. time 3, 6
7803 ■ ■ ■ ■ ■
CLP_Stat for 3, 6
7807 ■ ■ Off=0, On=1 ■ ■ ■
Io'> UInt8
CLP Pick-up 3, 6
7811 ■ ■ ■ ■ ■
CLP
7815 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
7819 ■ ■ ■ ■ ■
Iovs>> setting:

7831 ■ ■ UInt8 ■ ■ ■
Io'>>

Delay curve
7836 ■ ■ 3, 6 IEEE2=3, RI=4, Prg1=5, ■ ■ ■
family
DT=0, NI=1, VI=2, EI=3,

7840 ■ ■ ■ ■ ■
7, STI=8, STEI=9, RI=10,
UInt8 RXIDG=11
Operation
7844 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Inv. time 3, 6
7848 ■ ■ float32 1.00 = 100 ■ ■ ■
coefficient
Network
7852 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush_Stat 3, 6
7856 ■ ■ Off=0, On=1 ■ ■ ■
for Io'>> UInt8
SOL_Stat for 3, 6
7860 ■ ■ Off=0, On=1 ■ ■ ■
Io'>> UInt8
SOL
7864 Operation ■ ■ 3, 6 ■ ■ ■
SOL Inv. time 3, 6
7868 ■ ■ ■ ■ ■
P5/EN M/11A 113


e Code Scalling
CLP_Stat for 3, 6
7872 ■ ■ Off=0, On=1 ■ ■ ■
Io'>> UInt8
CLP Pick-up 3, 6
7876 ■ ■ ■ ■ ■
CLP
7880 Operation ■ ■ 3, 6 ■ ■ ■
CLP Inv. time 3, 6
7884 ■ ■ ■ ■ ■
Iovs>>> setting:

7901 ■ ■ UInt8 ■ ■ ■
Io'>>>
Operation
7906 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
delay
Network
7910 ■ ■ 3, 6 UInt8 Res=0, Cap=1 ■ ■ ■
grounding
Inrush_Stat 3, 6
7914 ■ ■ Off=0, On=1 ■ ■ ■
for Io'>>> UInt8
SOL_Stat for 3, 6
7918 ■ ■ Off=0, On=1 ■ ■ ■
Io'>>> UInt8
SOL
7922 Operation ■ ■ 3, 6 ■ ■ ■
CLP_Stat for 3, 6
7926 ■ ■ Off=0, On=1 ■ ■ ■
Io'>>> UInt8
CLP Pick-up 3, 6
7930 ■ ■ ■ ■ ■
CLP
7934 Operation ■ ■ 3, 6 ■ ■ ■
Uc> setting:

7951 ■ ■ UInt8 ■ ■
Uc>
7952 Pick-up value ■ ■ 3, 6 float32 1.00 xUcLN = 100 ■ ■
Operation
7956 ■ ■ 3, 6 float32 1.0 s = 10 ■ ■
delay
df/dt> setting:
Enable for df/ 3, 6 Off=0, On=1

8001 ■ ■ UInt8 ■ ■
dt>
Direction of Negative=0, Positive=1,
8002 ■ ■ 3, 6 UInt8 ■ ■
change Either=2
8006 Pick-up value ■ ■ 3, 6 float32 1.0 Hz/s = 10 ■ ■
Operation
8010 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
Low voltage
8014 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■
blocking
df/dt>> setting:
Enable for df/ 3, 6 Off=0, On=1

8051 ■ ■ UInt8 ■ ■
dt>>
Direction of Negative=0, Positive=1,
8052 ■ ■ 3, 6 UInt8 ■ ■
change Either=2
8056 Pick-up value ■ ■ 3, 6 float32 1.0 Hz/s = 10 ■ ■
Operation
8060 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■
delay
114 P5/EN M/11A


e Code Scalling
Low voltage
8064 ■ ■ 3, 6 UInt32 1 %Un = 1 ■ ■
blocking
IoInt> setting:

8101 ■ ■ UInt8 ■
IoInt>
8102 ■ ■ UInt8 ■
mode
8106 Uo pick-up ■ ■ 3, 6 Int32 1%=1 ■
Operation
8110 ■ ■ 3, 6 float32 1.00 s = 100 ■
delay
Min number of
8114 ■ ■ 3, 6 UInt8 1=1 ■
peaks
8118 Reset delay ■ ■ 3, 6 float32 1.00 s = 100 ■
Intermittent 3, 6
8122 ■ ■ float32 1.00 s = 100 ■
time
Feeder Fault Locator setting:
8152 Pick-up value ■ ■ 3, 6 float32 1.00 xIn = 100 ■
DI1=1, DI2=2, ..., DI19=19,

DI20=20, Arc1=25, Arc2=
26, BI=27, VI1=29, VI2=30,
VI3=31, VI4=32, DO1(B)
=33, DO2(B)=34, DO3(B)
SF=38, SF=39, SF=40,
SF=41, BO=42, DO1(C)
=43, DO2(C)=44, DO3(C)
=45, DO4(C)=46, LedAl=
49, LedTr=50, LedA=51,
LedB=52, LedC=53,
LedDR=54, VO1=55, VO2=
56, ..., VO5=59, VO6=60,
Triggering DI21=65, DI22=66, ...,
8153 ■ ■ 3, 6 UInt16 ■
digital input DI39=83, DI40=84, F1=85,
F2=86, ..., F6=90, F7=91,
DO1(D)=97, DO2(D)=98,
DO3(D)=99, SF=100, DO1
(E)=101, DO2(E)=102,
NI1=129, NI2=130, ...,
NI63=191, NI64=192,
POC1=193, POC2=194, ...,
POC15=207, POC16=208,
VI5=225, VI6=226, ...,
VI19=239, VI20=240,
VO7=257, VO8=258, ...,
VO19=269, VO20=270,
NI65=289, NI66=290, ...,
NI127=351, NI128=352
Line 3, 6
8154 ■ ■ float32 1.000 ohm = 1000 ■
reactance/unit
Earth/ground 3, 6
8155 ■ ■ float32 1.000 = 1000 ■
factor
Earth/ground
8156 ■ ■ 3, 6 Int16 ■
factor angle 1°=1
Event
8157 ■ ■ 3, 6 UInt8 Off=0, On=1 ■
enabling
8158 Uavg limit ■ ■ 3, 6 float32 1.0 %Un = 10 ■
8159 Io limit ■ ■ 3, 6 float32 1.00 xIn = 100 ■
8160 DI timeout ■ ■ 3, 6 float32 1.00 s = 100 ■
Release 3, 6
8161 ■ ■ float32 1.00 s = 100 ■
timeout
Synchro-check 1 setting

8201 ■ ■ UInt8 ■ ■ ■
SYNC1
P5/EN M/11A 115


e Code Scalling
Object 1=1, Object 2=2,

8202 CB object 1 ■ ■ 3, 6 UInt8 Object 3=3, Object 4=4, ■ ■ ■
Object 5=5, Object 6=6
Object 1=1, Object 2=2,

8203 CB object 2 ■ ■ 3, 6 UInt8 Object 3=3, Object 4=4, ■ ■ ■
Object 5=5, Object 6=6
DI1=1, DI2=2, ..., DI19=19,

DI20=20, Arc1=25, Arc2=
26, BI=27, VI1=29, VI2=30,
VI3=31, VI4=32, DO1(B)
=33, DO2(B)=34, DO3(B)
SF=38, SF=39, SF=40,
SF=41, BO=42, DO1(C)
=43, DO2(C)=44, DO3(C)
=45, DO4(C)=46, LedAl=
49, LedTr=50, LedA=51,
LedB=52, LedC=53,
LedDR=54, VO1=55, VO2=
56, ..., VO5=59, VO6=60,
Input for
DI21=65, DI22=66, ...,
8204 selecting ■ ■ 3, 6 UInt16 ■ ■ ■
DI39=83, DI40=84, F1=85,
Object2
F2=86, ..., F6=90, F7=91,
DO1(D)=97, DO2(D)=98,
DO3(D)=99, SF=100, DO1
(E)=101, DO2(E)=102,
NI1=129, NI2=130, ...,
NI63=191, NI64=192,
POC1=193, POC2=194, ...,
POC15=207, POC16=208,
VI5=225, VI6=226, ...,
VI19=239, VI20=240,
VO7=257, VO8=258, ...,
VO19=269, VO20=270,
NI65=289, NI66=290, ...,
NI127=351, NI128=352
Inhibit closing 3, 6 Off=0, On=1

8205 ■ ■ UInt8 ■ ■ ■
unselected CB
8206 Sync mode ■ ■ 3, 6 UInt8 Off=0, Async=1, Sync=2 ■ ■ ■
DD=1, DL=2, LD=3, DD/

Voltage check 3, 6
8207 ■ ■ UInt8 DL=4, DD/LD=5, DL/LD=6, ■ ■ ■
mode
DD/DL/LD=7
8208 CB close time ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
52B=1, 52A=2, DI1=3,

Extrip=4, DI5=5, DI6=6, ...,
DI19=19, DI20=20, Arc1=
8209 Bypass DI ■ ■ 3, 6 UInt16 25, Arc2=26, BI=27, VI1= ■ ■ ■
29, VI2=30, VI3=31, VI4=
32, DI21=65, DI22=66, ...,
DI31=75, DI32=76
8210 Bypass ■ ■ 3, 6 UInt8 1=1 ■ ■ ■
Ok pulse
8211 ■ ■ 3, 6 Int16 1 ms = 1 ■ ■ ■
length
Udead limit
8212 ■ ■ 3, 6 Int32 1 %Un = 1 ■ ■ ■
setting
Ulive limit
8216 ■ ■ 3, 6 Int32 1 %Un = 1 ■ ■ ■
setting
Frequency 3, 6
8220 ■ ■ float32 50.00 Hz = 5000 ■ ■ ■
difference
Voltage 3, 6
8224 ■ ■ Int32 1 %Un = 1 ■ ■ ■
difference
Phase angle 3, 6
8228 ■ ■ UInt16 1°=1 ■ ■ ■
difference
Request 3, 6
8232 ■ ■ float32 1.0 s = 10 ■ ■ ■
timeout
CB Wear setting
116 P5/EN M/11A


e Code Scalling

8251 ■ ■ UInt8 ■ ■ ■
CBwear
8252 Alarm level ■ ■ 3, 6 float32 1.00 kA = 100 ■ ■ ■
Limit for
Limit for oper. 3, 6 oper.left
8254 ■ ■ UInt32 1000 = 1000 ■ ■ ■
left scaling
8256 Current points ■ ■ 3, 6 float32 1.00 kA = 100 ■ ■ ■
Limit for oper. Limit for

8264 left of Break ■ ■ 3, 6 UInt32 1000 = 1000 oper.left ■ ■ ■
cur scaling
'Alarm 1 On' 3, 6 Off=0, On=1

8272 ■ ■ UInt8 ■ ■ ■
event
'Alarm 1 Off' 3, 6 Off=0, On=1
8273 ■ ■ UInt8 ■ ■ ■
event
8274 ■ ■ UInt8 ■ ■ ■
event
8274 ■ ■ UInt8 ■ ■ ■
event
Motor status setting
8301 Motor status ■ ■ 3, 6 UInt8 Off=0, On=1 ■ ■
Nom motor 3, 6
8302 ■ ■ float32 1.00 xIn = 100 ■ ■
start current
Motor start
8303 detection ■ ■ 3, 6 float32 1.00 xIn = 100 ■ ■
current
CB position
3, 6 CBPos=0, Current=1,
8304 detection ■ ■ UInt8 ■ ■
CBPos&Cur=2
mode
SOL setting
Enable for 3, 6 off=0, On=1

8351 ■ ■ UInt8 ■ ■ ■
SOL
SOL signal 3, 6 1=0, 2=1
8352 ■ ■ UInt8 ■ ■ ■
number
CB Trip
8353 ■ ■ 3, 6 float32 1.00 s = 100 ■ ■ ■
Clearing time
P5/EN M/11A 117

Specific Scalings
Data
Address Name Read Write Type P5U20 P5V20 P5F30 P5M30
10001-10002 Power scaling ■ float32 ■ ■
10003-10004 PF and cos scaling ■ float32 ■ ■
10005-10006 Tanφ scaling ■ float32 ■ ■
10007-10008 Voltage scaling ■ float32 ■ ■ ■
10009-10010 VT primary scaling ■ float32 ■ ■ ■
10011-10012 Frequency scaling ■ float32 ■ ■ ■ ■
10013-10014 VTo secondary scaling ■ float32 ■ ■ ■
10015-10016 Io scaling ■ float32 ■ ■ ■
10017-10018 Io' scaling ■ float32 ■ ■ ■
10019-10020 CLPU dead time scaling ■ float32 ■ ■ ■
10021-10022 Limit for oper.left scaling ■ float32 ■ ■ ■
10023-10024 Operate delay scaling ■ float32 ■ ■
10025-10026 Pick-up value scaling ■ float32 ■ ■
10027-10028 Fault value scaling ■ float32 ■ ■ ■ ■
10029-10030 MaxCtrlPulseLength scaling ■ float32 ■ ■ ■ ■
10031-10032 LPCT/VT scaling ■ float32 ■ ■
10033-10034 IoCSH scaling ■ float32 ■ ■ ■ ■
118 P5/EN M/11A

Ethernet/IP
Presentation
The Easergy P5 protection relays support communication using Ethernet/IP
protocol which is a part of Common Industrial Protocol (CIP)✧ family. Ethernet/IP
protocol is available with the optional inbuilt Ethernet port. The protocol can be
used to read / write data from the Easergy P5 protection relays using request /
response communication or via cyclic messages transporting data assigned to
assemblies (data sets).
Messaging
Ethernet/IP supports two modes of messaging, unconnected and connected
messaging.
• Unconnected messaging refers to peer-to-peer communication, where
opening and closing of connections is allowed via unconnected messaging.
This is handled by the UnConnected Message Manager (UCMM)✧.
Messages are sent over TCP/IP.
• Connected messaging, on the other hand, is dedicated to a particular
purpose, such as frequent explicit message transactions or real-time I/O data
transfers. Connection resources are reserved and configured using
communication services available via the UCMM. Messages are sent over
TCIP/IP and User Datagram Protocol (UDP)✧.
Ethernet/IP specifies a special encapsulation protocol to carry CIP messages over
TCP/IP and UDP.
There are two types of connections, explicit and implicit.
• Explicit connections refer to request-response connections which are general
purpose connections. Explicit connections use TCP/IP and use either
unconnected messaging via UCMM (one-time request/response) or Class 3
connections (cyclic request /response).
• In implicit connections, only application data is contained within the
messages. Implicit data may be polled, cyclic or Change of State (COS)✧
messages. Implicit connections are either point-to-point (unicast) or one-to-
many (multicast) connections. Implicit connections use UDP/IP.
Devices
There are two classes of devices in a CIP network, adapters and scanners.
• Adapters are targets of real-time I/O data connection. Adapters cannot send
or receive real-time data unless requested to do so by a scanner device.
Adapters can exchange data using explicit messages with any class of
devices but cannot originate a connection.
• Scanners are originators of I/O data connection requests and originators or
targets of explicit connection requests.
P5/EN M/11A 119

Objects
Figure 3 - CIP object model
Objects in CIP (and thereby Ethernet/IP) are defined by:

• A description – a description of an object being specified.
• A class code (Class ID) – hexadecimal identifier assigned to each CIP object
• Attributes – data elements associated with the object.
• Common services – list of the common services defined for the object.
• Object-specific Services – the full specifications of any services unique to the
object
• Connections – connections supported by the object.
• Behaviour – the relationship between attribute values and services.
The CIP also includes an Object Library, which is a set of standardized objects
that covers protocol objects such as the Identity Object, Assembly Object, etc. as
well as Application Objects. The Object Library covers basic automation blocks
and some more complex devices, including Digital Input, Digital Output, etc.
Table 35 - CIP object description.
Object Description
Connection The CIP Communication Object manages and provides the runtime
Object exchange of messages.
Message The Message Router Object provides a messaging connection point

Router through which a Client may address a service to any object class or
instance residing in the physical device. It routes explicit messages over
requested paths.
Assembly The Assembly Object binds attributes of multiple objects, which in allows
Object data to or from each of these objects to be sent or received over a single
connection (like a data set).
Assembly objects can be used to group input data (producing instance of
an Assembly Object – information transmitted to the network) or output
data (consuming instance of an Assembly Object – information received
from the network).
I/O connections are established between Assembly Object instances of
the devices – between inputs and outputs.
Assembly object instances are accessible via explicit messaging.
Identity Provides device identification and general information about the device,
Object such as vendor identifier, product code, name, status, etc.
The Identity Object shall be present in all CIP products.
Application Objects are based on the standard objects from the Object Library if
possible, if not, vendors can define their own, private (vendor specific) Application
Objects. CIP specifies the Class ID ranges for that purpose.
120 P5/EN M/11A

Table 36 - CIP Class ID ranges.
Range Meaning Quantity

(hexadecimal)
0x00…0x63 Open 100
0x64…0xC7 Vendor specific 100
0xC8…0xEF Reserved by CIP for future use 40
0xF0…0x2FF Open 528
0x300…0x4FF Vendor specific 512
0x500…0xFFFF Reserved by CIP for future use 64256
Device Profile
The series of application objects for Easergy P5 is known as the device profile. A
large number of profiles for many device types have been defined. An example of
a device profile is shown in Device profile, page 122.
Ethernet/IP Main Features

Ethernet/IP main features:
• Static data model:
◦ 2 standard objects (Overload and Control Supervisor)
◦ 2 private objects (one for digital data and one for analog data)
◦ 4 configuration objects for configuration of protection functions
• Two configurable assemblies (one producing and one consuming) with the
maximum capacity of 128 bytes. Each configuration is described in an
Electronic Data Sheet (EDS) file. Each EDS file that can be fed to any client
supporting EDS files and can be generated at any time, all changes to
Ethernet/IP configuration or to assemblies’ content require generating of the
new EDS file, see Generating an EDS File with eSetup Easergy Pro, page
130.
• Three types of communications are supported:
◦ UCMM (one time request / response)
◦ Class 3 connection (cyclic request / response)
◦ Class 1 connection (cyclic IO messages containing assemblies’ data)
P5/EN M/11A 121

Ethernet/IP protocol is available on Easergy P5 protection relays with an optional
embedded Ethernet card. Easergy P5 protection relays with the Ethernet/IP
protocol selected on the Ethernet port serves as an adapter which means that it is
not able to initiate communication with other devices on the network.
Objects and Messaging

The Ethernet/IP implementation on Easergy P5 protection relays supports all
required standard objects with their required attributes. There is also a total of 10
application objects from which 8 are private. A list of Easergy P5 device objects
and their classes is shown in the table below.
Table 37 - Device profile
Class Object Object Category
0x01 Identity Protocol Standard
0x02 Message Router
0x04 Assembly
0x06 Connection Manager
0xF5 TCP/IP Interface

0xF6 Ethernet Link
0x29 Control Supervisor Application
0x2C Overload
0x64 Digital Private
(vendor specific)
0x65 Analog
0x66 StgProtCurrent
0x67 StgProtEF
0x68 StgProtOther
0x69 StgGeneral
0x70 Analog2
0x71 Special
The Ethernet/IP implementation in Easergy P5 protection relays supports three

types of communication:
• Unconnected Explicit Requests and Responses – used mainly for
establishing explicit and I/O connections, but can also be used for one time
requests to attributes of data model objects.
• Explicit Messaging (Class 3) connections – these are strictly point-to-point
connections used to cyclically query the adapter for some data or to cyclically
write data to the adapter. Transmitted using TCP.
• I/O Messaging (Class 1) connections – can be point-to-point or multicast.
Used for very frequent exchange of process data. Easergy P5 protection
relays support only cyclic I/O connections. Transmitted using UDP.
Connection limits:
• For Class 3 connections – a maximum of six connections at the same time.
• For Class 1 connections – only one connection at the same time.
122 P5/EN M/11A

Supported Services
Table 38 - Supported services for objects
Class Object Object Category
Get Set
0x01 Identity GAA, GAS –
0x02 Message Router – –
0x04 Assembly GAS SAS
0x06 Connection Manager – –
0xF5 TCP/IP Interface GAA, GAS –
0xF6 Ethernet Link GAA, GAS –
0x29 Control Supervisor GAS SAS
0x2C Overload GAS SAS

0x64 Digital GAS SAS
0x65 Analog GAS SAS
0x66 StgProtCurrent GAS SAS
0x67 StgProtEF GAS SAS
0x68 StgProtOther GAS SAS
0x69 StgGeneral GAS SAS
0x70 Analog2 GAS SAS
0x71 Special GAS SAS
Easergy P5 protection relays support following services for objects:

• GAA = Get Attribute All
• GAS = Get Attribute Single
• SAS = Set Attribute Single
GAS service is available for all attributes with the GET or GET (to access) | SET
(to modify) access type and the SAS service is available for all attributes with the
GET | SET or SET access type.
A list of Easergy P5 device services for objects is shown in the above table.
I/O Messaging Assemblies

Ethernet/IP implementation on Easergy P5 protection relays includes a total of two
producing assemblies (Tx, Target → Originator) and two consuming assemblies
(Rx, Target → Originator); see table below.
Table 39 - Available assemblies
Instance no. Type Description
2 Producing Static Basic Output Image
50 Consuming Static Basic Image
100 Producing Configurable Output Image (dynamic)
150 Consuming Configurable Input Image (dynamic)
Additionally, a zero-length configuration assembly with instance number “199” is

available.
Assemblies have to be configured during the device setup. Configuring
assemblies involve selecting the producing and consuming instances to be used.
P5/EN M/11A 123

If dynamic assemblies (instance numbers 100 & 150) are used it is also needed to
configure the contents of both assemblies. By default both assemblies are
configured with one byte of data each. By default producing assembly is
configured with “Control Supervisor Object” / “Faulted attribute” and consuming
assembly with “Control Supervisor Object” / “FaultRst”.
I/O connections with Easergy P5 protection relays are opened with the Requested
Packet Interval (RPI) no less than 50 ms and not greater than 5 s. The default
Value is 100 ms.
Events
Easergy P5 protection relay events are available under the following attributes of
Digital Object (0x64)
• Attribute 118 – Event Code (bits 0-5: code, bits 6-15: channel)
• Attribute 119 – Event Milliseconds And Seconds (bits 0-5: seconds, bits 6-15:
milliseconds)
• Attribute 120 – Event Min And Hour (bits 0-7: hour, bits 8-15: minutes)
• Attribute 121 – Event Day And Month (bits 0-7: month, bits 8-15: day)
• Attribute 122 – Event Year
Events are read starting from the oldest one in the Event Buffer of the Easergy P5
protection relay. Events are read sequentially, the next event is read when the
previous one is acknowledged. Acknowledgement is done by setting attribute 123
of the Digital Object (0x64) – Event Ack. When all events have been read and the
event buffer is thus empty, the attributes will contain zero-data (zeroes). This zero-
data will automatically be replaced with the data of a new event when one is
registered.
Reading of events is the same for all communication types. The Easergy P5
protection relay sends the oldest available event. The next oldest event will be
read only after setting the Event Ack parameter (the one previously read is not
available any more) or after the event buffer has been cleared and a new event is
generated later on.
Fault Codes
The table below contains a translation of Easergy P5 protection relay stages to
Ethernet/IP Fault Codes.
Table 40 - Ethernet/IP fault code
Ethernet/IP Description Protection stage ANSI

fault code
20 CURRENT TRIP Overcurrent I> 50/51
Overcurrent I>>
Overcurrent I>>>
21 THERMAL OVERLOAD Thermal Overload T> 49
26 PHASE UNBALANCE Unbalance I2> 46
27 GROUND FAULT Earth Fault Io> 50N/51N
Earth Fault Io>>
Earth Fault Io>>>
Earth Fault Io>>>>
29 UNDERLOAD Under Current Stage I< 37
31 STALL Motor Startup Supervision Ist> 48
51 UNDERVOLTAGE U< 27
U<<
U<<<
52 OVERVOLTAGE U> 59
U>>
U>>>
54 PHASE REVERSAL Unbalance I2>> 47
124 P5/EN M/11A

Table 40 - Ethernet/IP fault code (Continued)
Ethernet/IP Description Protection stage ANSI

fault code
55 FREQUENCY f< 81L
f<< 81
f><
f>><<
73 START/HOURS Motor Restart Inhibition N> 66
EXCEED
P5/EN M/11A 125

Ethernet/IP Main Configuration

The configuration of the Ethernet/IP settings is done in the Ethernet/IP main
configuration view of the COMMUNICATION menu in eSetup Easergy Pro or Web
HMI.
Ethernet/IP main configuration parameters:
Table 41 - Description of the Ethernet/IP main configuration parameters
General
Multicast IP Multicast IP address used for sending IO
Address messages
Multicast TTL 1–100 Time to live of the IO messages sent to

multicast address
Vendor ID 1–65535 Identification of Schneider Electric
Device Type 0–65535 Indication of general type of product
Product Code 1-65535 Identification of a particular product of an

individual vendor
Major Revision 1–127 Major revision of the item the Identity
Object represents
Minor Revision 1–255 Minor revision of the item the Identity

Object represents
Serial Number 0-4294967295 Serial number of device

Product Name 32 chars Human readable identification
Auto/Manual Manual Include Run/Idle Header parameters are

Header Detection Auto used to define whether Run/Idle Header
(default) is used. Run/Idle Headers are detected
automatically
I/O assembly 2+50, Instance numbers of producing and

instances in use (default) consuming assemblies being used
100+150
Producing
Producing 1–1278 Instance number of producing assembly

instance number (not directly editable) 5
Include Run/Idle On/Off Include or exclude Run/Idle Header in an

Header outgoing IO messages
(Producing)
Producing [bytes] The size of the producing assembly (not

Instance Size directly editable) 6
Consuming
Consuming 1–1278 Instance number of consuming assembly

Instance
Include Run/Idle On/Off Expect presence or absence of Run/Idle
Header Header in an incoming IO messages
(Consuming)
Consuming [bytes] The size of the consuming assembly (not

Configuration
Configuration 1–1279 Instance number of configuration instance

Instance
Configuration [bytes] The size of the consuming assembly (not
5. Automatically updated according to the value of “I/O assembly instances in use” parameter.
6. Automatically updated as the assemblies are configured.
126 P5/EN M/11A

Multicast IP
Multicast IP address is a parameter used by the device to send EtherNet/IP
multicast packets, if requested to do so by the scanner. Multicast IP is a valid
Class D IP address. In device there is only one possible I/O connection at a time
and therefore only single Multicast IP is used.
Multicast IP parameter is ignored when scanner requested T → O (target-to-
originator, i.e. adapter to scanner) communication to be point-to-point. The default
value of this parameter is 239.0.0.1.
Multicast TTL
Multicast TTL value is used for the IP header Time-to-live field when sending
EtherNet/IP multicast packets. This value is ignored for the unicast packets and
TTL as configured for the TCP/IP stack is used instead.
The default value of this parameter is 1 (the number of network hops over which
the multicast packet is propagated – datagrams limited to the local subnet).
Auto/Manual Header Detection

When this parameter is set to “Manual”, user needs to define manually the
presence of Run/Idle header in the I/O messaging. This is done by configuring
parameters “Include Run/Idle Header” for more information, see Include Run/Idle
Header (Producing), page 127 and Include Run/Idle Header (Consuming), page
127.
When “Auto” is selected, Easergy P5 protection relays automatically detect
whether Run/Idle header is used in the I/O messaging. The default value of this
parameter is “Auto”.
I/O Assembly Instances in Use

Selection of producing and consuming instances to be used. The values of
producing and consuming assemblies are available in the EDS file (see
Generating an EDS File with eSetup Easergy Pro, page 130) and are used by the
configuration tool as a reference path during I/O connection opening.
Every change to this parameter requires restarting the device and generation of a
new EDS file.
Include Run/Idle Header (Producing)

An I/O connection can be established with or without the Run/Idle Header in the
Target → Originator direction (adapter to scanner). Including Run/Idle Header in
the producing assembly adds additional 4 bytes to the beginning of the data part
of an I/O message. Run bit is always set in the outgoing messages if Easergy P5
protection relays are configured to send I/O messages with the Run/Idle Header.
Information about whether the Run/Idle Header is included in the outgoing
messages is available in the EDS file and can be used by the eSetup Easergy Pro
to properly establish communication.
Every change to this parameter requires generation of a new EDS file.
The default value of this parameter is “Off”.
Include Run/Idle Header (Consuming)

An I/O connection can be established with or without the Run/Idle Header in the
Target ← Originator direction (scanner to adapter). Setting this value to “On”
inform the eSetup Easergy Pro that Easergy P5 protection relays expect the
consuming assembly to contain additional 4 bytes of data. If the Run/Idle Header
is included and the Run bit is set in the incoming I/O messages then Easergy P5
protection relays process received data, and if the Run bit is cleared then P5
device ignores received data. If the Run/Idle Header is not included in the
P5/EN M/11A 127

incoming I/O messages then the received data is always processed. Information
about whether the Run/Idle Header is expected in the incoming I/O messages is
available in the EDS file and can be used by the eSetup Easergy Pro to properly
establish communication.
Every change to this parameter requires generation of a new EDS file. The default
value of this parameter is “On”.
NOTE:
Changing of both "Include Run/Idle Header" parameters while the I/O
connection is running is not allowed by Easergy P5 protection relays.
128 P5/EN M/11A

Data Point Configuration

Available data items, that is, the contents of the Producing Assembly and the
Consuming Assembly can be viewed / configured in the following eSetup Easergy
Pro menus:
• EtherNet/IP I/O 2+50 (static)
• EtherNet/IP I/O 100+150 (dynamic)
Assembly 2+50 is static, meaning user cannot make changes to the contents of
assembly. Assembly 100+150 is dynamic, meaning user can select data items to
the assembly by clicking on a row and selecting a desired data point. An example
of this is shown in figure below.
Figure 4 - Configuration of the Ethernet/IP Producing Assembly.
Table 42 - Description of Assembly configuration table contents
Attribute Description
Name Type and name of the data item
Length Length of the data item in bytes
Scaling The scaling used for the data item
Offset The offset of the data item in the assembly
NOTE: Making changes to the assemblies will require a device reboot for the
changes to take effect.
A list of the set of available data items in Ethernet/IP, see Data Model of
Ethernet/IP, page 131.
P5/EN M/11A 129

Generating an EDS File with eSetup Easergy Pro

Changes to main configuration parameters or the configuration of assemblies
requires a new EDS file to be generated (once all changes are made and the
device is about to be used in the network).
An EDS file can be generated with eSetup Easergy Pro or Web HMI in the
COMMUNICATION menu. Selecting the option “Export EthernetIP EDS file...” will
generate the EDS file and bring up a file browser window asking where to save the
generated file. After clicking Save the generated EDS file will be stored at the
selected location.
Figure 5 - Creating an EDS file
130 P5/EN M/11A

Data Model of Ethernet/IP

Cont. Data-
Class Name Length Read Write P5U20 P5V20 P5F30 P5M30
mode Type
0x71 Special#001/1 byte padding 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x71 Special#002/2 bytes padding 2 ■ ■ 1 UInt16 ■ ■ ■ ■
0x29 Control Supervisor#003/Run1 1 ■ ■ 1 UInt8 ■ ■ ■ ■
Control Supervisor#010/
0x29 1 ■ 1 UInt8 ■ ■ ■ ■
Faulted
0x29 Warning 1 ■ 1 UInt8 ■ ■ ■ ■
0x29 1 ■ 1 UInt8 ■ ■ ■ ■
FaultRst
0x29 1 ■ 1 UInt8 ■ ■ ■ ■
FaultCode
0x29 1 ■ 1 UInt8 ■ ■ ■ ■
WarnCode
0x29 CycleCount 4 ■ ■ 1 UInt32 ■ ■ ■ ■
0x2C Overload#005/AvgCurrent 4 ■ 1 float32 ■ ■ ■ ■
0x2C Overload#006/%PhImbal 1 ■ 1 UInt8 ■ ■ ■ ■
0x2C Overload#007/%Thermal 1 ■ 1 UInt8 ■ ■ ■ ■
0x2C Overload#008/CurrentL1 4 ■ 1 float32 ■ ■ ■ ■
0x2C Overload#011/GroundCurrent 4 ■ 1 float32 ■ ■ ■ ■
0x64 Digital#001/Digital inputs 4 ■ 1 UInt32 ■ ■ ■ ■
0x64 Digital#002/Output relays 4 ■ 1 UInt32 ■ ■ ■ ■
0x64 Digital#003/Alive indicator 2 ■ 1 UInt16 ■ ■ ■ ■
0x64 Digital#004/Events 4 ■ 1 UInt32 ■ ■ ■ ■
Digital#005/Remote/Local
0x64 1 ■ ■ 1 UInt8 ■ ■ ■ ■
State
Digital#006/Cancel selected
0x64 operation 1 ■ 1 UInt8 ■ ■ ■ ■
Digital#007/OM_MB_
0x64 1 ■ ■ 1 UInt8 ■ ■ ■ ■
ResetLatches
Digital#008/Synchronize
0x64 1 ■ ■ 1 UInt8 ■ ■ ■ ■
minutes
0x64 Digital#009/Object1 state 1 ■ 1 UInt8 ■ ■ ■ ■
Digital#017/Open select
0x64 Object1 1 ■ ■ 1 UInt8 ■ ■ ■ ■
Digital#018/Close select
0x64 Object1 1 ■ ■ 1 UInt8 ■ ■ ■ ■
Digital#019/Execute operation
0x64 Object1 1 ■ 1 UInt8 ■ ■ ■ ■
P5/EN M/11A 131

Cont. Data-
mode Type
Digital#020/Max ctrl pulse

0x64 length of Object1 4 ■ ■ 1 float32 ■ ■ ■ ■
0x64 Object2 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object2 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object2 1 ■ 1 UInt8 ■ ■ ■ ■

0x64 Object3 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object3 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object3 1 ■ 1 UInt8 ■ ■ ■ ■

0x64 Object4 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object4 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object4 1 ■ 1 UInt8 ■ ■ ■ ■

0x64 Object5 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object5 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object5 1 ■ 1 UInt8 ■ ■ ■ ■

0x64 Object6 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object6 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Object6 1 ■ 1 UInt8 ■ ■ ■ ■

0x64 Digital#041/DirectO1O 1 ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#042/DirectO1C 1 ■ 1 UInt8 ■ ■ ■ ■
132 P5/EN M/11A

Cont. Data-
mode Type
0x64 Digital#053/Pos. sequence I1 4 ■ 1 UInt32 ■ ■ ■
Digital#054/Negative
0x64 sequence I2 4 ■ 1 UInt32 ■ ■ ■
0x64 Digital#055/Current ratio I2/I1 4 ■ 1 float32 ■ ■ ■
Digital#056/Current phase
0x64 sequence 1 ■ 1 UInt8 ■ ■ ■
0x64 Digital#057/Pos. sequence U1 4 ■ 1 UInt32 ■ ■ ■
Digital#058/Negative
0x64 sequence U2 4 ■ 1 UInt32 ■ ■ ■
0x64 Digital#059/Voltage U2/U1 4 ■ 1 float32 ■ ■ ■
Digital#060/Voltage phase
0x64 sequence 1 ■ 1 UInt8 ■ ■ ■
0x64 Digital#061/Voltage interrupt 1 ■ 1 UInt8 ■ ■ ■
0x64 Digital#062/Voltage status 1 ■ 1 UInt8 ■ ■ ■
Digital#063/Clear min/max/
0x64 1 ■ ■ 1 UInt8 ■ ■ ■ ■
demand
Digital#068/Shot1 start
0x64 2 ■ ■ 1 UInt16 ■ ■
counter
0x64 2 ■ ■ 1 UInt16 ■ ■
counter
0x64 2 ■ ■ 1 UInt16 ■ ■
counter
0x64 2 ■ ■ 1 UInt16 ■ ■
counter
0x64 2 ■ ■ 1 UInt16 ■ ■
counter
0x64 Digital#073/AR start counter 2 ■ ■ 1 UInt16 ■ ■
0x64 Digital#074/AR fail counter 2 ■ ■ 1 UInt16 ■ ■
0x64 Digital#075/AR shot number 1 ■ 1 UInt8 ■ ■
0x64 Digital#076/Critical AR req. 2 ■ 1 UInt16 ■ ■
0x64 Digital#077/Recloser locked 2 ■ 1 UInt16 ■ ■
0x64 Digital#078/Recloser running 2 ■ 1 UInt16 ■ ■
0x64 Digital#079/Final trip 2 ■ 1 UInt16 ■ ■
0x64 Digital#080/Auto-Recloser on 2 ■ 1 UInt16 ■ ■
0x64 Digital#081/Timer 1 status 1 ■ ■ 1 UInt8 ■ ■ ■ ■
Digital#085/Logic output
0x64 1 ■ 1 UInt8 ■ ■ ■ ■
states 1...8
0x64 1 ■ 1 UInt8 ■ ■ ■ ■
states 9...16
0x64 1 ■ 1 UInt8 ■ ■ ■ ■
states 17...20
0x64 Digital#088/Stage start state 1 ■ 1 UInt8 ■ ■ ■ ■
P5/EN M/11A 133

Cont. Data-
mode Type
0x64 Digital#089/Stage trip state 1 ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#090/N> alarm 1 ■ 1 UInt8 ■ ■
Digital#091/Motor start
0x64 1 ■ 1 UInt8 ■ ■
disabled
0x64 Digital#092/Motor starting 1 ■ 1 UInt8 ■ ■
0x64 Digital#093/Motor running 1 ■ 1 UInt8 ■ ■
0x64 Digital#094/CBWear Alarm 1 1 ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#095/CBWear Alarm 2 1 ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#096/Alarm L1..L3 1 ■ 1 UInt8 ■ ■ ■
0x64 Digital#097/Fault L1..L3 1 ■ 1 UInt8 ■ ■ ■
Digital#098/SetGrp common
0x64 change 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#099/Sync1 request 1 ■ 1 UInt8 ■ ■
0x64 Digital#100/Sync1 OK 1 ■ 1 UInt8 ■ ■
0x64 Digital#101/Bypass 1 ■ ■ 1 UInt8 ■ ■
0x64 Digital#102/Sync1 fail 1 ■ 1 UInt8 ■ ■
0x64 Digital#109/Virtual outputs 2 ■ 1 UInt16 ■ ■ ■ ■
Digital#114/Engine running
0x64 4 ■ ■ 1 UInt32 ■ ■ ■ ■
hours
Digital#115/Engine running (in
0x64 seconds) 2 ■ ■ 1 UInt16 ■ ■ ■ ■
0x64 Digital#116/Start counter 2 ■ ■ 1 UInt16 ■ ■ ■ ■
0x64 Digital#117/Reset diagnostics 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#118/Event Code 2 ■ 1 UInt16 ■ ■ ■ ■
Digital#119/Event Millisec And

0x64 2 ■ 1 UInt16 ■ ■ ■ ■
Sec
Digital#120/Event Min And
0x64 2 ■ 1 UInt16 ■ ■ ■ ■
Hour
Digital#121/Event Day And
0x64 2 ■ 1 UInt16 ■ ■ ■ ■
Month
0x64 Digital#122/Event Year 2 ■ 1 UInt16 ■ ■ ■ ■
0x64 Digital#123/Event Ack 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#124/Device status 1 ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#125/DI1 counter 2 ■ ■ 1 UInt16 ■ ■ ■ ■
0x64 Digital#135/DI11 counter 2 ■ ■ 1 UInt16 ■ ■
134 P5/EN M/11A

Cont. Data-
mode Type
0x64 Digital#199/Virtual input 1 1 ■ ■ 1 UInt8 ■ ■ ■ ■
0x64 Digital#219/Virtual output 1 1 ■ ■ 1 UInt8 ■ ■ ■ ■
P5/EN M/11A 135

Cont. Data-
mode Type
0x65 Analog#001/Phase current IL1 4 ■ 1 UInt32 ■ ■ ■
0x65 Analog#004/Frequency 4 ■ 1 float32 ■ ■ ■ ■
Analog#005/Io residual
0x65 4 ■ 1 float32 ■ ■
current
Analog#006/Io' residual
0x65 4 ■ 1 float32 ■ ■
current
0x65 Analog#007/Residual voltage 4 ■ 1 float32 ■ ■ ■
0x65 Analog#008/Active power 4 ■ 1 Int32 ■ ■
0x65 Analog#009/Reactive power 4 ■ 1 Int32 ■ ■
0x65 Analog#010/Apparent power 4 ■ 1 Int32 ■ ■
Analog#011/Line-to-line
0x65 voltage U12 4 ■ 1 UInt32 ■ ■ ■
0x65 voltage U23 4 ■ 1 UInt32 ■ ■ ■
0x65 voltage U31 4 ■ 1 UInt32 ■ ■ ■
0x65 Analog#014/Exported energy 4 ■ ■ 1 float32 ■ ■
0x65 Analog#015/Imported energy 4 ■ ■ 1 float32 ■ ■
Analog#016/Exp. reactive
0x65 energy 4 ■ ■ 1 float32 ■ ■
Analog#017/Imp. reactive
0x65 energy 4 ■ ■ 1 float32 ■ ■
0x65 Analog#018/Power factor 4 ■ 1 float32 ■ ■
Analog#019/Line-to-neutral
0x65 voltage VL1 4 ■ 1 UInt32 ■ ■ ■
136 P5/EN M/11A

Cont. Data-
mode Type
0x65 Analog#022/Tanφ 4 ■ 1 float32 ■ ■
0x65 Analog#023/Phase current IL 4 ■ 1 UInt32 ■ ■ ■
Analog#024/Average Line-to-
0x65 line voltage 4 ■ 1 UInt32 ■ ■ ■
Analog#025/Average Line-to-
0x65 neutral voltage 4 ■ 1 UInt32 ■ ■ ■
Analog#026/Phase current
0x65 4 ■ 1 float32 ■ ■ ■
THD
Analog#027/Phase current IL1
0x65 4 ■ 1 float32 ■ ■ ■
THD
0x65 4 ■ 1 float32 ■ ■ ■
THD
0x65 4 ■ 1 float32 ■ ■ ■
THD
Analog#030/HARMONICS of
0x65 4 ■ 1 UInt32 ■ ■ ■
IL1
0x65 4 ■ 1 UInt32 ■ ■ ■
IL2
0x65 4 ■ 1 UInt32 ■ ■ ■
IL3
Analog#033/Min. of IL1 IL2
0x65 4 ■ 1 Int32 ■ ■ ■
IL3
Analog#034/Max. of IL1 IL2
0x65 4 ■ 1 Int32 ■ ■ ■
IL3
0x65 4 ■ 1 UInt32 ■ ■ ■
ILRMS
0x65 4 ■ 1 UInt32 ■ ■ ■
IL1RMS
0x65 4 ■ 1 UInt32 ■ ■ ■
IL2RMS
0x65 4 ■ 1 UInt32 ■ ■ ■
IL3RMS
0x65 Analog#039/Temperature rise 4 ■ 1 float32 ■ ■
Analog#040/Ambient
0x65 temperature 2 ■ ■ 1 Int16 ■ ■
0x65 4 ■ 1 UInt32 ■ ■ ■
IL1da demand
0x65 4 ■ 1 UInt32 ■ ■ ■
IL2da demand
0x65 4 ■ 1 UInt32 ■ ■ ■
IL3da demand
0x65 Analog#044/IoCalc demand 4 ■ 1 float32 ■ ■ ■
0x65 Analog#045/Io demand 4 ■ 1 float32 ■ ■
0x65 Analog#046/Io' demand 4 ■ 1 float32 ■ ■
0x65 Analog#047/Voltage THD 4 ■ 1 float32 ■ ■ ■
0x65 4 ■ 1 float32 ■ ■ ■
VL1 THD
0x65 4 ■ 1 float32 ■ ■ ■
VL2 THD
0x65 4 ■ 1 float32 ■ ■ ■
VL3 THD
P5/EN M/11A 137

Cont. Data-
mode Type
Analog#051/Harmonics of
0x65 4 ■ 1 UInt32 ■ ■ ■
VL1
0x65 4 ■ 1 UInt32 ■ ■ ■
VL2
0x65 4 ■ 1 UInt32 ■ ■ ■
VL3
Analog#054/Min of Line-to-
0x65 line voltages 4 ■ 1 UInt32 ■ ■ ■
Analog#055/Max of Line-to-
Analog#056/Min. of Line-to-
0x65 neutral voltages 4 ■ 1 UInt32 ■ ■ ■
Analog#057/Max. of Line-to-
Analog#058/RMS voltage
0x65 4 ■ 1 UInt32 ■ ■ ■
mean
0x65 voltage VL1RMS 4 ■ 1 UInt32 ■ ■ ■
0x65 4 ■ 1 UInt32 ■ ■ ■
U12demand
0x65 4 ■ 1 UInt32 ■ ■ ■
U23demand
0x65 4 ■ 1 UInt32 ■ ■ ■
U31demand
0x65 4 ■ 1 UInt32 ■ ■ ■
VL1demand
0x65 4 ■ 1 UInt32 ■ ■ ■
VL2demand
0x65 4 ■ 1 UInt32 ■ ■ ■
VL3demand
0x65 Analog#068/Cosφ 4 ■ 1 float32 ■ ■
Analog#069/Cosφ of phase
0x65 4 ■ 1 float32 ■ ■
L1
0x65 4 ■ 1 float32 ■ ■
L2
0x65 4 ■ 1 float32 ■ ■
L3
0x65 Analog#072/Power angle 2 ■ 1 Int16 ■ ■
Analog#073/Phase L1 active
0x65 power 4 ■ 1 Int32 ■ ■
0x65 power 4 ■ 1 Int32 ■ ■
0x65 power 4 ■ 1 Int32 ■ ■
Analog#076/Phase L1
0x65 reactive power 4 ■ 1 Int32 ■ ■
Analog#077/Phase L2
Analog#078/Phase L3
Analog#079/Phase L1
0x65 apparent power 4 ■ 1 Int32 ■ ■
138 P5/EN M/11A

Cont. Data-
mode Type
Analog#080/Phase L2
Analog#081/Phase L3
Analog#082/RMS active
0x65 power 4 ■ 1 Int32 ■ ■
Analog#083/RMS reactive
0x65 power 4 ■ 1 Int32 ■ ■
Analog#084/RMS apparent
0x65 power 4 ■ 1 Int32 ■ ■
Analog#085/Active power
0x65 4 ■ 1 Int32 ■ ■
demand
Analog#086/Reactive power
0x65 4 ■ 1 Int32 ■ ■
demand
Analog#087/Apparent power
0x65 4 ■ 1 Int32 ■ ■
demand
Analog#088/Power factor
0x65 4 ■ 1 float32 ■ ■
demand
Analog#089/RMS active
0x65 power demand 4 ■ 1 Int32 ■ ■
Analog#090/RMS reactive
Analog#091/RMS apparent
0x65 Analog#092/Calculated Io 4 ■ 1 float32 ■ ■ ■
0x65 Analog#093/Fault current of I> 4 ■ 1 float32 ■ ■ ■
Analog#094/Fault current of
0x65 4 ■ 1 float32 ■ ■ ■
I>>
Analog#095/Fault current of
0x65 4 ■ 1 float32 ■ ■ ■
I>>>
0x65 Analog#096/Fault reactance 4 ■ 1 float32 ■
Analog#102/Minimum
0x65 frequency 4 ■ ■ 1 float32 ■ ■ ■ ■
Analog#103/Minimum active
0x65 power 4 ■ ■ 1 Int32 ■ ■
Analog#104/Minimum react.
0x65 power 4 ■ ■ 1 Int32 ■ ■
Analog#105/Minimum
0x65 apparent power 4 ■ ■ 1 Int32 ■ ■
0x65 Analog#106/Min power factor 4 ■ ■ 1 float32 ■ ■
0x65 Analog#107/Minimum of Io 4 ■ ■ 1 float32 ■ ■ ■
0x65 Analog#108/Minimum of Io' 4 ■ ■ 1 float32 ■ ■ ■
Analog#109/Demand
0x65 minimum active power 4 ■ ■ 1 Int32 ■ ■
Analog#110/Demand
0x65 minimum reactive power 4 ■ ■ 1 Int32 ■ ■
Analog#111/Demand
0x65 minimum apparent power 4 ■ ■ 1 Int32 ■ ■
Analog#112/Demand
0x65 minimum power factor 4 ■ ■ 1 float32 ■ ■
Analog#113/RMS Demand
0x65 mini active power 4 ■ ■ 1 Int32 ■ ■
0x65 min reactive power 4 ■ ■ 1 Int32 ■ ■
P5/EN M/11A 139

Cont. Data-
mode Type
0x65 mini apparent power 4 ■ ■ 1 Int32 ■ ■
0x65 Analog#116/Minimum of IL1 4 ■ ■ 1 UInt32 ■ ■ ■
Analog#119/RMS minimum of
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
IL1
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
IL2
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
IL3
Analog#122/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Minimum of IL1
Analog#123/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Minimum of IL2
Analog#124/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Minimum of IL3
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
minimum of IL1
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
minimum of IL2
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
minimum of IL3
0x65 Analog#128/Minimum of U12 4 ■ ■ 1 UInt32 ■ ■ ■
Analog#131/Maximum
0x65 frequency 4 ■ ■ 1 float32 ■ ■ ■ ■
Analog#132/Maximum active
0x65 power 4 ■ ■ 1 Int32 ■ ■
Analog#133/Maximum react.
0x65 power 4 ■ ■ 1 Int32 ■ ■
Analog#134/Maximum
0x65 apparent power 4 ■ ■ 1 Int32 ■ ■
0x65 Analog#135/Max power factor 4 ■ ■ 1 float32 ■ ■
0x65 Analog#136/Maximum of Io 4 ■ ■ 1 float32 ■ ■ ■
0x65 Analog#137/Maximum of Io' 4 ■ ■ 1 float32 ■ ■ ■
Analog#138/Demand
0x65 Maximum active power 4 ■ ■ 1 Int32 ■ ■
Analog#139/Demand
0x65 maximum reactive power 4 ■ ■ 1 Int32 ■ ■
Analog#140/Demand
0x65 Maximum apparent power 4 ■ ■ 1 Int32 ■ ■
Analog#141/Demand
0x65 maximum power factor 4 ■ ■ 1 float32 ■ ■
0x65 max active power 4 ■ ■ 1 Int32 ■ ■
0x65 max reactive power 4 ■ ■ 1 Int32 ■ ■
0x65 max apparent power 4 ■ ■ 1 Int32 ■ ■
0x65 Analog#145/Maximum of IL1 4 ■ ■ 1 UInt32 ■ ■ ■
140 P5/EN M/11A

Cont. Data-
mode Type
Analog#148/RMS maximum
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
of IL1
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
of IL2
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
of IL3
Analog#151/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Maximum of IL1
Analog#152/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Maximum of IL2
Analog#153/Demand
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
Maximum of IL3
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
maximum of IL1
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
maximum of IL2
0x65 4 ■ ■ 1 UInt32 ■ ■ ■
maximum of IL3
0x65 Analog#157/Maximum of U12 4 ■ ■ 1 UInt32 ■ ■ ■
0x65 Analog#252/IED Mode 2 ■ 1 UInt16 ■ ■ ■ ■
StgProtCurrent#001/Enable
0x66 1 ■ ■ 0 UInt8 ■ ■ ■
for I>
0x66 StgProtCurrent#002/Group 1 ■ 0 UInt8 ■ ■ ■
StgProtCurrent#003/Pick-up
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
StgProtCurrent#005/Delay
0x66 curve family 1 ■ ■ 0 UInt8 ■ ■ ■
0x66 curve family 1 ■ ■ 0 UInt8 ■ ■ ■
0x66 type 1 ■ ■ 0 UInt8 ■ ■ ■
0x66 type 1 ■ ■ 0 UInt8 ■ ■ ■
StgProtCurrent#009/Inv. time
0x66 4 ■ ■ 0 float32 ■ ■ ■
coefficient
0x66 4 ■ ■ 0 float32 ■ ■ ■
coefficient
StgProtCurrent#011/Include
0x66 1 ■ ■ 0 UInt8 ■ ■ ■
harmonics
StgProtCurrent#012/Constant
0x66 4 ■ ■ 0 float32 ■ ■ ■
A
0x66 4 ■ ■ 0 float32 ■ ■ ■
B
0x66 4 ■ ■ 0 float32 ■ ■ ■
C
0x66 4 ■ ■ 0 float32 ■ ■ ■
D
0x66 4 ■ ■ 0 float32 ■ ■ ■
E
P5/EN M/11A 141

Cont. Data-
mode Type
0x66 1 ■ ■ 0 UInt8 ■ ■ ■
for I>>
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
StgProtCurrent#021/
0x66 Operation delay 4 ■ ■ 0 float32 ■ ■ ■
StgProtCurrent#022/
0x66 1 ■ ■ 0 UInt8 ■ ■ ■
for I>>>
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■ ■
value
StgProtCurrent#027/
StgProtCurrent#028/
0x66 for Iφ> 1 ■ ■ 0 UInt8 ■ ■
0x66 StgProtCurrent#030/Group 1 ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■
value
StgProtCurrent#033/Direction
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
StgProtCurrent#035/Angle
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 curve family 1 ■ ■ 0 UInt8 ■ ■
0x66 type 1 ■ ■ 0 UInt8 ■ ■
0x66 type 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
coefficient
0x66 4 ■ ■ 0 float32 ■ ■
coefficient
0x66 4 ■ ■ 0 float32 ■ ■
A
0x66 4 ■ ■ 0 float32 ■ ■
B
0x66 4 ■ ■ 0 float32 ■ ■
C
142 P5/EN M/11A

Cont. Data-
mode Type
0x66 4 ■ ■ 0 float32 ■ ■
D
0x66 4 ■ ■ 0 float32 ■ ■
E
0x66 for Iφ>> 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 type 1 ■ ■ 0 UInt8 ■ ■
0x66 type 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
coefficient
0x66 4 ■ ■ 0 float32 ■ ■
coefficient
0x66 4 ■ ■ 0 float32 ■ ■
A
0x66 4 ■ ■ 0 float32 ■ ■
B
0x66 4 ■ ■ 0 float32 ■ ■
C
0x66 4 ■ ■ 0 float32 ■ ■
D
0x66 4 ■ ■ 0 float32 ■ ■
E
0x66 for Iφ>>> 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 2 ■ ■ 0 Int16 ■ ■
offset
P5/EN M/11A 143

Cont. Data-
mode Type
StgProtCurrent#075/
0x66 Operation delay 4 ■ ■ 0 float32 ■ ■
StgProtCurrent#076/
0x66 for Iφ>>>> 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 4 ■ ■ 0 float32 ■ ■
value
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 1 ■ ■ 0 UInt8 ■ ■
mode
0x66 2 ■ ■ 0 Int16 ■ ■
offset
0x66 2 ■ ■ 0 Int16 ■ ■
offset
StgProtCurrent#085/
StgProtCurrent#086/
0x66 1 ■ ■ 0 UInt8 ■ ■ ■
for I2/I1>
0x66 4 ■ ■ 0 UInt32 ■ ■ ■
value K2
0x66 4 ■ ■ 0 UInt32 ■ ■ ■
value K2
StgProtCurrent#093/
StgProtCurrent#094/
0x66 1 ■ ■ 0 UInt8 ■ ■
for Ist>
StgProtCurrent#097/Motor
0x66 4 ■ ■ 0 float32 ■
start detection current
StgProtCurrent#098/Nom
0x66 4 ■ ■ 0 float32 ■ ■
motor start current
0x66 type 1 ■ ■ 0 UInt8 ■ ■
0x66 4 ■ ■ 0 float32 ■ ■
start time
0x66 1 ■ ■ 0 UInt8 ■ ■
for N>
StgProtCurrent#102/Max
0x66 4 ■ ■ 0 UInt32 ■ ■
motor starts/hour
StgProtCurrent#103/Min time
0x66 4 ■ ■ 0 float32 ■ ■
between motor starts
StgProtCurrent#104/Alarm on
0x66 1 ■ ■ 0 UInt8 ■ ■
event
StgProtCurrent#105/Alarm off
0x66 1 ■ ■ 0 UInt8 ■ ■
event
0x66 1 ■ ■ 0 UInt8 ■ ■
start disabled
144 P5/EN M/11A

Cont. Data-
mode Type
0x66 1 ■ ■ 0 UInt8 ■ ■
start enabled
0x66 1 ■ ■ 0 UInt8 ■ ■
for I<
0x66 4 ■ ■ 0 UInt32 ■ ■
value
0x66 4 ■ ■ 0 UInt32 ■ ■
value
StgProtCurrent#112/
StgProtCurrent#113/
0x67 StgProtEF#001/Enable for Io> 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 StgProtEF#002/Group 1 ■ 0 UInt8 ■ ■ ■
0x67 StgProtEF#003/Pick-up value 4 ■ ■ 0 float32 ■ ■ ■
StgProtEF#005/Delay curve
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 StgProtEF#007/Delay type 1 ■ ■ 0 UInt8 ■ ■ ■
StgProtEF#009/Operation
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#012/Constant A 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#013/Constant B 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#014/Constant C 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#015/Constant D 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#016/Constant E 4 ■ ■ 0 float32 ■ ■ ■
StgProtEF#017/Enable for
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Io>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 Ioφ> 1 ■ ■ 0 UInt8 ■ ■
0x67 StgProtEF#024/Group 1 ■ 0 UInt8 ■ ■
StgProtEF#025/Direction
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
StgProtEF#027/Char ctrl. in
0x67 ResCap mode 1 ■ ■ 0 UInt8 ■ ■
P5/EN M/11A 145

Cont. Data-
mode Type
0x67 StgProtEF#029/Pick-up value 4 ■ ■ 0 float32 ■ ■
StgProtEF#031/Uo setting for

0x67 Ioφ> stage 4 ■ ■ 0 Int32 ■ ■

0x67 Ioφ> stage 4 ■ ■ 0 Int32 ■ ■
0x67 StgProtEF#033/Angle offset 2 ■ ■ 0 Int16 ■ ■
StgProtEF#035/Pick up sector
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 StgProtEF#039/Delay type 1 ■ ■ 0 UInt8 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 StgProtEF#043/Constant A 4 ■ ■ 0 float32 ■ ■
0x67 StgProtEF#044/Constant B 4 ■ ■ 0 float32 ■ ■
0x67 StgProtEF#045/Constant C 4 ■ ■ 0 float32 ■ ■
0x67 StgProtEF#046/Constant D 4 ■ ■ 0 float32 ■ ■
0x67 StgProtEF#047/Constant E 4 ■ ■ 0 float32 ■ ■
0x67 Ioφ>> 1 ■ ■ 0 UInt8 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
0x67 1 ■ ■ 0 UInt8 ■ ■
mode

0x67 Ioφ>> stage 4 ■ ■ 0 Int32 ■ ■

0x67 Ioφ>> stage 4 ■ ■ 0 Int32 ■ ■
0x67 2 ■ ■ 0 Int16 ■ ■
size
146 P5/EN M/11A

Cont. Data-
mode Type
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Io>>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
StgProtEF#079/
0x67 Compensation mode 1 ■ ■ 0 UInt8 ■ ■
StgProtEF#080/
0x67 Compensation current 4 ■ ■ 0 float32 ■ ■
StgProtEF#081/Save
0x67 1 ■ ■ 0 UInt8 ■ ■
unbalance current
StgProtEF#082/'Saving unbal'
0x67 1 ■ ■ 0 UInt8 ■ ■
event
StgProtEF#083/'Unbal saved'
0x67 1 ■ ■ 0 UInt8 ■ ■
event
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Io>>>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
StgProtEF#090/
0x67 Compensation mode 1 ■ ■ 0 UInt8 ■ ■
StgProtEF#091/
0x67 Compensation current 4 ■ ■ 0 float32 ■ ■
StgProtEF#092/Save
0x67 1 ■ ■ 0 UInt8 ■ ■
unbalance current
P5/EN M/11A 147

Cont. Data-
mode Type
StgProtEF#093/Max allowed
0x67 2 ■ ■ 0 UInt16 ■ ■
faults
StgProtEF#094/Clear location
0x67 1 ■ ■ 0 UInt8 ■ ■
counters
StgProtEF#095/'Saving unbal'
0x67 1 ■ ■ 0 UInt8 ■ ■
event
StgProtEF#096/'Unbal saved'
0x67 1 ■ ■ 0 UInt8 ■ ■
event
0x67 1 ■ ■ 0 UInt8 ■
IoInt>
0x67 StgProtEF#098/Group 1 ■ 0 UInt8 ■
0x67 StgProtEF#099/Uo pick-up 4 ■ ■ 0 Int32 ■
0x67 StgProtEF#100/Uo pick-up 4 ■ ■ 0 Int32 ■
0x67 delay 4 ■ ■ 0 float32 ■
0x67 delay 4 ■ ■ 0 float32 ■
StgProtEF#103/Intermittent
0x67 4 ■ ■ 0 float32 ■
time
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Uo>
0x67 StgProtEF#106/Pick-up value 4 ■ ■ 0 Int32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Uo>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Io>>>>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 Ioφ>>> 1 ■ ■ 0 UInt8 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
148 P5/EN M/11A

Cont. Data-
mode Type
0x67 1 ■ ■ 0 UInt8 ■ ■
mode

0x67 Ioφ>>> stage 4 ■ ■ 0 Int32 ■ ■

0x67 Ioφ>>> stage 4 ■ ■ 0 Int32 ■ ■
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■
Uo>>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■ ■
Io'>
0x67 StgProtEF#160/Group 1 ■ 0 UInt8 ■ ■ ■ ■
0x67 StgProtEF#161/Pick-up value 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■ ■
P5/EN M/11A 149

Cont. Data-
mode Type
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 StgProtEF#165/Delay type 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 StgProtEF#166/Delay type 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#169/Io' input 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 StgProtEF#171/Constant A 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#172/Constant B 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#173/Constant C 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#174/Constant D 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#175/Constant E 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■ ■
Io'>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#182/Io input 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■ ■ ■
Io'>>>
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x67 StgProtEF#189/Io input 1 ■ ■ 0 UInt8 ■ ■ ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
IoUo>
0x67 StgProtEF#194/Io input 1 ■ ■ 0 UInt8 ■ ■
0x67 StgProtEF#195/Reset time 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
150 P5/EN M/11A

Cont. Data-
mode Type
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 2 ■ ■ 0 Int16 ■ ■
size
StgProtEF#202/Timer instant
0x67 delay ctrl. 1 ■ ■ 0 UInt8 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
IoUo>>
0x67 StgProtEF#207/Io input 1 ■ ■ 0 UInt8 ■ ■
0x67 StgProtEF#208/Reset time 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
0x67 1 ■ ■ 0 UInt8 ■ ■
mode
0x67 2 ■ ■ 0 Int16 ■ ■
size
0x67 2 ■ ■ 0 Int16 ■ ■
size
StgProtEF#215/Timer instant
0x67 delay ctrl. 1 ■ ■ 0 UInt8 ■ ■
0x67 StgProtEF#216/Enable for I2> 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 family 1 ■ ■ 0 UInt8 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 delay 4 ■ ■ 0 float32 ■ ■ ■
0x67 StgProtEF#229/Arc I state 1 ■ 0 UInt8 ■ ■
0x67 StgProtEF#230/Arc Io state 1 ■ 0 UInt8 ■ ■
0x67 StgProtEF#231/Arc stage 1 1 ■ 0 UInt8 ■ ■
P5/EN M/11A 151

Cont. Data-
mode Type
StgProtEF#239/Temperature
0x67 2 ■ 0 Int16 ■ ■ ■ ■
1
0x67 2 ■ 0 Int16 ■ ■ ■ ■
2
0x67 2 ■ 0 Int16 ■ ■ ■ ■
3
0x67 2 ■ 0 Int16 ■ ■ ■ ■
4
0x67 2 ■ 0 Int16 ■ ■ ■ ■
5
0x67 2 ■ 0 Int16 ■ ■ ■ ■
6
0x67 2 ■ 0 Int16 ■ ■ ■ ■
7
0x67 2 ■ 0 Int16 ■ ■ ■ ■
8
0x67 2 ■ 0 Int16 ■ ■ ■ ■
9
0x67 2 ■ 0 Int16 ■ ■ ■ ■
10
0x67 2 ■ 0 Int16 ■ ■ ■ ■
11
0x67 2 ■ 0 Int16 ■ ■ ■ ■
12
0x67 2 ■ 0 Int16 ■ ■ ■ ■
13
0x67 2 ■ 0 Int16 ■ ■ ■ ■
14
0x67 2 ■ 0 Int16 ■ ■ ■ ■
15
0x67 2 ■ 0 Int16 ■ ■ ■ ■
16
StgProtOther#001/Enable for
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U>
0x68 StgProtOther#002/Group 1 ■ 0 UInt8 ■ ■ ■
StgProtOther#003/Pick-up
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
StgProtOther#005/Operation
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 StgProtOther#007/Reset time 4 ■ ■ 0 float32 ■ ■ ■
0x68 StgProtOther#008/Hysteresis 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U>>
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
152 P5/EN M/11A

Cont. Data-
mode Type
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U>>>
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U<
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
StgProtOther#029/Low
0x68 voltage blocking 4 ■ 0 Int32 ■ ■ ■
0x68 StgProtOther#031/Reset time 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U<<
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
U<<<
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
P5/EN M/11A 153

Cont. Data-
mode Type
0x68 4 ■ ■ 0 Int32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
fX
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 voltage blocking 4 ■ ■ 0 UInt32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
fXX
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
f<
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
f<<
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
154 P5/EN M/11A

Cont. Data-
mode Type
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■
df/dt>
0x68 StgProtOther#080/Group 1 ■ 0 UInt8 ■ ■
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
StgProtOther#085/Minimum
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■
P<
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■
P<<
0x68 4 ■ ■ 0 Int32 ■ ■
value
0x68 4 ■ ■ 0 Int32 ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■
feeder 49F>
StgProtOther#101/Maximum
0x68 4 ■ ■ 0 float32 ■ ■
continuous current
StgProtOther#102/Alarm
0x68 setting 4 ■ ■ 0 UInt32 ■ ■
StgProtOther#103/Time
0x68 2 ■ ■ 0 UInt16 ■ ■
constant tau
P5/EN M/11A 155

Cont. Data-
mode Type
StgProtOther#104/Rel.
0x68 cooling time constant 4 ■ 0 float32 ■ ■
StgProtOther#105/Max
0x68 4 ■ 0 UInt32 ■ ■
overload at +40°C
StgProtOther#106/Max
0x68 4 ■ 0 UInt32 ■ ■
overload at +70°C
StgProtOther#107/Ambient
0x68 temperature 2 ■ 0 Int16 ■ ■
StgProtOther#108/Ambient
0x68 temp. sensor 1 ■ 0 UInt8 ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■ ■
CBF
StgProtOther#110/Monitored
0x68 Trip relay 1 ■ ■ 0 UInt8 ■ ■ ■ ■
StgProtOther#111/Timer1
0x68 Operation Delay 4 ■ ■ 0 float32 ■ ■ ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■ ■
SOTF
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■ ■
value
StgProtOther#115/Cold load
0x68 pickup 1 ■ 0 UInt8 ■ ■ ■
StgProtOther#116/Inrush
0x68 1 ■ 0 UInt8 ■ ■ ■
detection
0x68 1 ■ ■ 0 UInt8 ■ ■
df/dt>>
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 4 ■ ■ 0 float32 ■ ■
value
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 delay 4 ■ ■ 0 float32 ■ ■
0x68 1 ■ ■ 0 UInt8 ■ ■
Motor 49M>
0x69 StgGeneral#001/CT primary 4 ■ ■ 0 UInt32 ■ ■ ■
StgGeneral#002/CT
0x69 secondary 2 ■ 0 UInt16 ■ ■ ■
StgGeneral#003/Nominal
0x69 input 2 ■ 0 UInt16 ■ ■ ■
StgGeneral#004/earth/
0x69 ground/ground CT primary 4 ■ ■ 0 UInt32 ■ ■ ■ ■
StgGeneral#005/earth/
0x69 ground/ground CT secondary 4 ■ 0 float32 ■ ■ ■ ■
StgGeneral#006/Nominal Io1
0x69 input 4 ■ 0 float32 ■ ■ ■ ■
156 P5/EN M/11A

Cont. Data-
mode Type
StgGeneral#007/Very
0x69 sensitive earth/ground CT 4 ■ ■ 0 UInt32 ■ ■ ■ ■
primary
StgGeneral#008/Very
0x69 sensitive earth/ground CT 4 ■ 0 float32 ■ ■ ■ ■
secondary
StgGeneral#009/Nominal Io2
0x69 input 4 ■ 0 float32 ■ ■ ■ ■
0x69 StgGeneral#010/VT primary 4 ■ ■ 0 UInt32 ■ ■ ■
StgGeneral#011/VT
0x69 secondary 2 ■ ■ 0 UInt16 ■ ■ ■
StgGeneral#012/VTo
0x69 secondary 4 ■ ■ 0 float32 ■ ■ ■
StgGeneral#013/Motor
0x69 4 ■ ■ 0 float32 ■
nominal current
StgGeneral#021/Delay CT
0x69 supervision 2 ■ ■ 0 UInt16 ■ ■ ■
StgGeneral#022/VT
0x69 supervisor 2 ■ ■ 0 UInt16 ■ ■ ■
0x70 Analog2#001/Frequency 4 ■ 1 float32 ■ ■ ■ ■
0x70 Analog2#002/Active power 4 ■ 1 Int32 ■ ■
0x70 Analog2#003/Reactive power 4 ■ 1 Int32 ■ ■
0x70 Analog2#004/Apparent power 4 ■ 1 Int32 ■ ■
Analog2#005/Line-to-line
0x70 voltage U12 4 ■ 1 UInt32 ■ ■ ■
0x70 voltage U23 4 ■ 1 UInt32 ■ ■ ■
0x70 voltage U31 4 ■ 1 UInt32 ■ ■ ■
0x70 Analog2#008/Power factor 4 ■ 1 float32 ■ ■
Analog2#009/Line-to-neutral
0x70 Analog2#012/Tanφ 4 ■ 1 float32 ■ ■
Analog2#013/Average Line-
0x70 to-line voltage 4 ■ 1 UInt32 ■ ■ ■
Analog2#014/Average Line-
0x70 to-neutral voltage 4 ■ 1 UInt32 ■ ■ ■
Analog2#015/Pos. sequence
0x70 4 ■ 1 UInt32 ■ ■ ■
U1
Analog2#016/Negative
0x70 sequence U2 4 ■ 1 UInt32 ■ ■ ■
Analog2#017/Min of Line-to-
Analog2#018/Max of Line-to-
Analog2#019/Min. of Line-to-
Analog2#020/Max. of Line-to-
P5/EN M/11A 157

Cont. Data-
mode Type
Analog2#021/RMS voltage
0x70 4 ■ 1 UInt32 ■ ■ ■
mean
0x70 4 ■ 1 UInt32 ■ ■ ■
U12demand
0x70 4 ■ 1 UInt32 ■ ■ ■
U23demand
0x70 4 ■ 1 UInt32 ■ ■ ■
U31demand
0x70 4 ■ 1 UInt32 ■ ■ ■
VL1demand
0x70 4 ■ 1 UInt32 ■ ■ ■
VL2demand
0x70 4 ■ 1 UInt32 ■ ■ ■
VL3demand
0x70 Analog2#031/Cosφ 4 ■ 1 float32 ■ ■
Analog2#032/Cosφ of phase
0x70 4 ■ 1 float32 ■ ■
L1
0x70 4 ■ 1 float32 ■ ■
L2
0x70 4 ■ 1 float32 ■ ■
L3
Analog2#035/Phase L1 active
0x70 power 4 ■ 1 Int32 ■ ■
0x70 power 4 ■ 1 Int32 ■ ■
0x70 power 4 ■ 1 Int32 ■ ■
Analog2#038/Phase L1
Analog2#044/RMS active
0x70 power 4 ■ 1 Int32 ■ ■
Analog2#045/RMS reactive
0x70 power 4 ■ 1 Int32 ■ ■
Analog2#046/RMS apparent
0x70 power 4 ■ 1 Int32 ■ ■
Analog2#047/Active power
0x70 4 ■ 1 Int32 ■ ■
demand
Analog2#048/Reactive power
0x70 4 ■ 1 Int32 ■ ■
demand
Analog2#049/Apparent power
0x70 4 ■ 1 Int32 ■ ■
demand
158 P5/EN M/11A

Cont. Data-
mode Type
Analog2#050/Power factor
0x70 4 ■ 1 float32 ■ ■
demand
Analog2#051/RMS active
Analog2#052/RMS reactive
Analog2#053/RMS apparent
Analog2#054/Estimated time
0x70 to trip 4 ■ 1 UInt32 ■ ■
Analog2#055/Phase current
0x70 4 ■ 1 UInt32 ■ ■ ■
IL1
0x70 4 ■ 1 UInt32 ■ ■ ■
IL2
0x70 4 ■ 1 UInt32 ■ ■ ■
IL3
Analog2#058/Pos. sequence
0x70 4 ■ 1 UInt32 ■ ■ ■
I1
Analog2#059/Negative
0x70 sequence I2 4 ■ 1 UInt32 ■ ■ ■
Analog2#060/Current ratio I2/

0x70 4 ■ 1 float32 ■ ■ ■
I1
0x70 Analog2#061/Voltage U2/U1 4 ■ 1 float32 ■ ■ ■
Analog2#063/Estimated time
0x70 to trip 4 ■ 1 UInt32 ■ ■
P5/EN M/11A 159

Redundancy Protocols
There are three redundancy protocols available as options of Ethernet
communication in Easergy P5 protection relays:
• PRP (Parallel Redundancy Protocol)
• HSR (High-availability Seamless Redundancy)
• RSTP (Rapid Spanning Tree Protocol)
Parallel Redundancy Protocol (PRP)
Introduction
The Parallel Redundancy Protocol used in the Easergy P5 protection relays is
defined in Clause 4 of the IEC 62439-3 standard. The PRP is a “redundancy in the
devices” method that provides bumpless switchover in case of network failure or
reintegration. Furthermore, it provides the shortest Ethernet network
reconfiguration time as network reconfiguration is seamless.
The Easergy P5 protection relay uses two independent Ethernet ports that
operate in parallel on two independent networks. Each message is replicated and
sent over both networks. The first network node that receives a message will
process it, all later instances of the received message will be discarded. These
details of replicating and discarding messages are controlled by the low-level PRP
layer of the network architecture, so that the two networks are hidden from the
higher level layers. Thus, PRP-based networks provide a high degree of
robustness and resilience.
Essentially, a PRP network consists of a pair of similar Local Area Networks
(LANs)✧ which can be any topology (tree, ring or mesh). An example of a PRP
network is shown in PRP Redundancy Network, page 161.
The key features of a PRP redundancy network include:
• Each of the two LANs can have one or more “Single Attached Nodes” (SANs)
✧. These are normally non-significant devices that are attached only to a
single network. SANs can communicate with each other, but only if they are
attached to the same LAN.
• Matched pairs of devices have an interface to each LAN, hence they are
called “Dual Attached Nodes” (DANs)✧. DANs having the PRP implemented
are called “DANs with PRP implemented” (DANP)✧.
• To make the network messages (also known as “frames”) be transferred
correctly to each device in both LANs, each DANP has to be configured with
the same Media Access Control (MAC)✧ code and Internet Protocol (IP)
address for both of its ports. As a result, TCP/IP traffic will automatically
communicate with both of the paired devices, so it will be unaware of any
layer 2 redundancy or frame duplication issues.
• A Redundancy Box is used when a single interface node has to be connected
to both LANs. The RedBox can communicate with all other nodes. So far as
other nodes are concerned, the RedBox behaves like a DAN, so a RedBox is
also called a “Virtual DAN” (VDAN)✧. The RedBox has its own unique IP
address.
• The Easergy P5 protection relays have to be connected to the redundant
Ethernet network as a Double Attached Node (DAN) using PRP (DAN using
PRP is known as DANP).
• The redundant Ethernet interface can be made using an optical fibre
connection with an LC connector type (Ethernet card dependent).
• The management of the PRP redundancy is transparent to the application
data provided via the Ethernet interface.
• Disconnection of one of the LANs to the device does not cause any
degradation to the application data over the Ethernet interface.
160 P5/EN M/11A

• Each supervision frame includes a sequence number as defined in the

IEC 62439-3 specification. This is incremented for each supervision message
and the value starts from zero following a system restart.
• Received frames to provide supervision of the redundant network are not
processed by Easergy P5 protection relays.
Figure 6 - PRP Redundancy Network
Power LAN A
SAN SAN Supply
(A1) (A2) DANP LAN B
(D2)
Redundancy Box
(RedBox) SAN
(B2)
DANP
VDAN (D1) SAN Power
(B1) Supply
VDAN
VDAN
REBz2232A
Structure of a DANP
Figure 7 - Communication between two DANPs
Easergy P5 protection relays working in PRP mode work as a DANP each within
the overall network topology. Each DANP has two ports that operate in parallel.
They are attached to the upper layers of the communications stack through the
Link Redundancy Entity (LRE)✧.
The LRE has two main tasks:
• Handling message frames
• Management of redundancy
When an upper layer sends a frame to the LRE, the LRE replicates the frame and
sends it through both its ports at nearly the same time. The two frames move
through the two LANs with slightly different delays, ideally arriving at the
destination node within a small time window.
When receiving frames, the LRE forwards the first frame it received to its upper
layers and then discards the duplicate.
As both DANP nodes have the same MAC and IP addresses, this makes
redundancy transparent to the upper layers. This allows the Address Resolution
Protocol (ARP)✧ to work in the same way as with a SAN. Accordingly, to the
upper layers of a DANP, the LRE layer shows the same interface as the network
adapter of a non-redundant adapter.
P5/EN M/11A 161

To manage redundancy, the LRE:

• Adds a 32-bit Redundancy Check Tag (RCT)✧ to each frame it sends
• Removes the RCT from each frame it receives
Communication between SANs and DANs

A SAN can be connected to any LAN and can communicate with any other SAN
on the same LAN or any DAN. However, a SAN which connected to one LAN can
not communicate directly to a SAN which is connected to the other LAN.
A DAN is connected to both LANs and can communicate with any Redundancy
Box (RedBox) or any other DANs or any SANs on either network. For
communication purposes, a DAN “views” a SAN connected through a RedBox as
a VDAN.
When a SAN generates a basic frame, it sends the frame only onto the LAN to
which it is connected.
Originating at the SAN, a typical frame contains these parameters:
• dest_addr: Destination Address
• src_addr: Source Address
• type: Type
• data
• fcs: Frame Check Sequence (i.e. extra checksum characters added to allow
error detection and correction)
The frame from the SAN is then received by the DAN; which sends the frame to its
upper layers, which act accordingly.
When a DAN generates a frame, it needs to send the frame onto both of the LANs
to which it is connected. When it does this, it extends the frame by adding the 32-
bit Redundancy Control Trailer (RCT) into the frame.
The RCT consists of these parameters:
• 16-bit Sequence Number
• 4-bit LAN identifier, 1010 (0xA) for LAN_A and 1011 (0xB) for LAN_B
• 12-bit frame size
• PRP suffix
Accordingly, originating at the DAN, a typical frame then contains these
parameters:
• type: Type
• lsdu: Link Service Data Unit
• Padding: if needed
• RCT data:
◦ 16-bit sequence number
◦ 4-bit LAN identifier
◦ 12-bit frame size
◦ 16-bit PRP suffix (0x88FB)
• fcs: Frame Check Sequence
162 P5/EN M/11A

Figure 8 - Frames without and with RCT and padding.
Basic Frame dest_addr src_addr type FCS
Frame extended by an RCT

dest_addr src_addr type LSDU SeqNr LANId Size FCS
(Redundancy Control Trailer)
Frame extended by an RCT

dest_addr src_addr type LSDU padding SeqNr LANId Size FCS
plus padding
The key points about these differing frame structures is that:

• SANs implement no redundancy features, so they generate basic frames
which SANs and DANs can understand.
• SANs can still understand the frames that come from DANs, as SANs ignore
the RCT components in frames which come from DANs (a SAN cannot
distinguish the RCT from the IEEE802.3 padding).
• If a DAN receives a frame which does not include the RCT component, it
sends a single copy of the frame to its upper layers.
• If a DAN receives a frame which does include the RCT component, it does not
send a duplicate copy of the frame to its upper layers.
• If a DANP cannot identify that the remote Node is a DAN, it inserts no RCT.
Main Characteristics
• One VLAN tag supported
• 128 publishers supported per receiver
• Up to 100Mbit/s full duplex Ethernet
• Dynamic frame memory allocation (pager manager)
• Configurable duplicate detection
• Wishborne interface for configuration and status registers
• CPU port interface — Ethernet or Wishbone
• Support for link-local protocols - CPU may send to specific ports only - CPU
knows receive port
• Configurable frame memory and queue length
• Duplicate detection with configurable size and aging time
• MAC address filtering (8 filter masks for interlink, 6 for CPU)
• Support for interfaces with or without Ethernet preamble
According to the IEC/IEEE 8802-3, the Maximum Transmission Unit (MTU)✧
(Ethernet maximum packet size) is:
• 1518 bytes without VLAN and without PRP
• 1522 bytes with VLAN and without PRP
• 1524 bytes without VLAN and with PRP
• 1528 bytes with VLAN and with PRP
NOTE: Check that the LAN switches setting for the MTU is at least 1528
bytes.
P5/EN M/11A 163

PRP Parameters
The redundant Ethernet standard (IEC 62439-3) defines several parameters for
the PRP protocol; these being fixed according to the table below:
Table 43 - PRP parameter values
Supervision Frame 01-15-4E-00-01-00 Target MAC Address for multicast supervision

Multicast Address frame.
Life Check Interval 2 s +/- 100 ms Period between transmission of supervision frames.
PRP Mode Duplicate This is normal PRP mode, Duplicate address will
Discard not be supported.
Entry Forget Time 400 ms Duration that the received message Sequence
number will be held to discard a duplicate message.
Node Reboot 500 ms Duration following reboot for which no PRP frames
Interval will be transmitted.
164 P5/EN M/11A

High-availability Seamless Redundancy (HSR)
Introduction
The High-availability Seamless Redundancy Protocol used in the Easergy P5
protection relays is defined in Clause 5 of the IEC 62439-3 standard.
The HSR is a “redundancy in the devices” method that provides seamless
switchover and recovery in case of a single communication failure or reintegration.
HSR Ethernet redundancy method is independent of any industrial Ethernet
protocol and typically used in a ring topology.
Easergy P5 protection relays provide two redundant Ethernet ports using HSR.
The redundant Ethernet interface can be made using an optical fibre connection
with an LC connector type. The management of the HSR redundancy is
transparent to the application data provided via the Ethernet interface.
Disconnection of one of the Nodes to the device does not cause any degradation
to the application data over the Ethernet interface.
Easergy P5 protection relays support SNMP.
An example of a HSR network is shown in HSR Redundancy Network, page 165.
The key features of a HSR redundancy network include:
• Nodes within the ring are restricted to be HSR-capable bridging nodes, thus
avoiding the use of dedicated bridges.
• Singly Attached Nodes (SANs) such as laptops or printers cannot be attached
directly to the ring, but need attachment through a RedBox.
• A simple HSR network consists of doubly attached bridging nodes, each
having two ports, interconnected by full-duplex links.
• A source DANH (Double Attached Node with HSR implemented) sends a
frame passed from its upper layers, prefixes it by an HSR tag to identify frame
duplicates and sends the frame over each port.
• A destination DANH receives, in the fault-free state, two identical frames from
each port within a certain interval, if it is a multicast frame, it instantaneously
forwards it on the ring, removes the HSR tag of the first frame before passing
it to its upper layers and discards any duplicate.
In particular, the node will not forward a frame that it injected into the ring. A
destination node of a unicast frame does not forward a frame for which it is
the only destination, except for testing.
• Easergy P5 protection relays have to be connected to the redundant Ethernet
network as a Double Attached Node (DAN) using HSR (DANH).
Figure 9 - HSR Redundancy Network
Structure of a DAN
Easergy P5 protection relays working in HSR Mode work as a DAN within the
overall network topology. Each DAN has two ports that operate in parallel. The two
HSR ports A and B and the device port C are connected by the Link Redundancy
Entity (LRE), which includes a switching matrix allowing to forward frames from
one port to the other. The switching matrix allows cut-through bridging. The LRE
P5/EN M/11A 165

presents to the higher layers the same interface as a standard Ethernet

transceiver would do.
Figure 10 - Communication between two DANs (in HSR)
DAN node is operable in HSR-tagged forwarding mode, the DAN inserts the HSR
tag on behalf of its host and forwards the ring traffic, except for frames sent by the
node itself. Duplicate frames and frames where the node is the unicast destination
are not forwarded.
Structure of a RedBox
The RedBox has a LRE that performs the duties of the HSR protocol, in particular:
• forwards the frames received from one HSR port to the other HSR port,
unless the frame receives frames addressed to its own upper protocols
• prefixes the frames sent by its own upper layers with the corresponding HSR
tag before sending two copies over its HSR ports
The switching logic is incorporated into the RedBox, so interlink becomes an
internal connection.
A simple RedBox is present in every node, since the LRE makes a transition to a
single non-HSR host. In addition, it is usual to have more than one host in a node,
since a port for maintenance often exists.
A node does not send over a port a frame that is a duplicate of a frame previously
sent over that port in that same direction.
For the purpose of Duplicate Discard, a frame is identified by:
• source MAC address
• sequence number
The Duplicate Discard method forgets an entry identified by <Source MAC
Address><Sequence number> after a time EntryForgetTime.
Communication between SANs, DANs and RedBoxs

Singly Attached Nodes, for instance maintenance laptops or printers cannot be
inserted directly into the ring since they have only one port and cannot interpret
the HSR tag in the frames. SANs communicate with ring devices through a
RedBox that acts as a proxy for the SANs attached to it.
A source DANH sends a frame passed from its upper layers, and prefixes it by an
HSR tag to identify frame duplicates and sends the frame over both ports. Each
supervision frame includes a sequence number as defined in the IEC 62439- 3
specification. This is incremented for each supervision message and the value
starts from zero following a system restart.
A destination DANH receives, in the fault-free state, two identical frames from
each port within a certain interval, if it is a multicast frame, it instantaneously
166 P5/EN M/11A

forwards it on the ring, removes the HSR tag of the first frame before passing it to
its upper layers (“D”- frame) and discards any duplicate.
A typical frame contains these parameters:
• type: Type
• data
• fcs: Frame Check Sequence (i.e. extra checksum characters added to allow
error detection and correction)
HSR frames are identified uniquely by their HSR tag.
The HSR tag consists of these parameters: The Redundancy Control Trailer
(RCT) consists of following parameters:
• 16-bit Ethertype (HSR_EtherType = 0x892F)
• 4-bit path identifier (PathId), 0000 for both HSR nodes A and B, and 0010-
1111 for one of 7 PRP networks (A/B)
• 12-bit frame size (LSDUsize)
• 16-bit Sequence Number (SeqNr)
Accordingly, a typical HSR frame then contains these parameters:
• HSR tag data
• type: Type
• payload: Payload
• Padding: if needed
• fcs: Frame Check Sequence
Figure 11 - HSR frame without VLAN tag.
Figure 12 - HSR frame with VLAN tag.
The key points about these differing frame structures is that:

• Unlike PRP, SANs cannot be attached directly to such a duplicated network
unless they are able to interpret the HSR tag.
• In particular, the node will not forward a frame that it injected into the ring.
• A destination node of a unicast frame does not forward a frame for which it is
the only destination, except for testing.
P5/EN M/11A 167

• DANH receiving from an HSR port, if this frame is not HSR-tagged and is a
link local traffic, consume the frame and will not be forward it.
• DANH receiving from an HSR port, if this frame is HSR-tagged and this node
is not a destination, it will not pass the frame to the link layer interface.
• A node accepts an HSR tagged frame also if the LanId does not correspond
to the PathId and if the LSDUsize does not match the frame size.
Main Characteristics
• One VLAN tag supported
• Up to 128 devices supported
• Up to 100Mbit/s full duplex Ethernet
• Dynamic frame memory allocation (page manager)
• Configurable duplicate detection
• Wishbone interface for configuration and status registers
• CPU port interface - Wishbone
• Support for link-local protocols - CPU may send to specific ports only - CPU
knows receive port
• Configurable frame memory and queue length
• Duplicate detection with configurable size and aging time
• MAC address filtering (8 filter masks for interlink port, 6 for CPU port)
Limitations:
• Number of devices on a same ring at 100 Mbit/s:
Each hop (devices or RedBox) not only carries its own messages but also all
the other devices messages thus the bandwidth used is proportional to the
number of device. The maximum number of hops is around 20 when the
GOOSE messages are highly used or 40 if the number and importance of
GOOSE messages is not high.
• When Precision Time Protocol, according IEEE1588/IEC 61588 standard, is
used:
As the GPS receiver inaccuracy is 200 ns and as each hop (devices or
RedBox) can add a 50 ns inaccuracy, the maximum number of hops is 16 if 1
μs accuracy is required (PMU application or Process Bus).
HSR Parameters
The redundant Ethernet standard (IEC 62439-3) defines several parameters for
the HSR protocol; these being fixed according to the table below:
Table 44 - HSR parameter values
Supervision Frame 01-15-4E-00-01-00 Target MAC Address for multicast supervision

Multicast Address frame
Life Check Interval 2 s +/- 100 ms Period between transmission of supervision frames
HSR Mode Duplicate Discard This is normal HSR mode, Duplicate address will
not be supported.
Entry Forget Time 400 ms Duration that the received message Sequence
number will be held to discard a duplicate message.
Node Reboot 500 ms Duration following reboot for which no PRP frames
Interval will be transmitted.
MulticastFilterSize 8 Interlink & 6 Nios Number of multicast addresses to be filtered
CPU
168 P5/EN M/11A

Rapid Spanning Tree Protocol (RSTP)
Introduction
RSTP is a standard used to quickly reconnect a network failure by finding an
alternative path, allowing loop-free network topology.
Figure 13 - A redundant Ethernet star or ring circuit
Switch 1 Switch 2 Switch 1 Switch 2
Easergy P5 1 Easergy P5 2 Easergy P5 1 Easergy P5 2
Ring connection managed by RSTP

Star connection with redundant ports
blocking function on upper switches and
managed by RSTP blocking function.
IEDs interconnected directly.
Although RSTP can recover network failures quickly, the recovery time depends
on the number of devices and the topology. The recovery time also depends on
the time taken by the devices to determine the root bridge and compute the port
roles (discarding, learning, forwarding). The devices do this by exchanging Bridge
Protocol Data Units (BPDUs) containing information about bridge devices and root
path costs. See the IEEE 802.1w standard for further information.
The RSTP solution is based on open standards. It is therefore compatible with
other manufacturers’ IEDs that use the RSTP protocol. The RSTP recovery time is
typically 300 ms but it increases with the network size. Due to this recovery times
it is not recommended to use RSTP in automation systems where a high
availability of GOOSE is essential.
Easergy P5 protection relays provide two redundant Ethernet ports using RSTP.
The redundant Ethernet interface can be made using RJ45 or optical fibre
connections of LC connector type. The management of the RSTP is transparent to
the application data provided via the Ethernet interface. One of the missed node
connections to the device does not cause any degradation to the application data
over the Ethernet interface.
RSTP Parameters
Table 45 - RSTP parameter values
Parameter Default Range Description

Value
Enable for RSTP Yes Yes, No Enable/disable the use of RSTP protocol on the
Ethernet port.
(RSTP on Slot L can be enabled or disabled,
while RSTP on Slot M is always enabled.)
Bridge priority 32768 0...65535 Parameter used to define the RSTP root device
(step is for the network. If priorities of two or more
4096) devices are equal then the device with lowest
MAC address is chosen as a root.
Hello Time 2s 1...10 s Setting defines how often RSTP frames (Hello
BPDU) are sent.
Forward Delay 15 s 4...30 s Time needed for the port to change its state
from blocking to forwarding.
Max Age 20 s 6...40 s The maximum age of the information

transmitted by the Bridge when it is the Root
Bridge.
Port1 Path Cost 200000 1...200000 Port Cost is related to transfer speed. This is
determined according to RSTP specification.
Port1 Priority 128 0...255 When both Ethernet ports are set connected to
the same network segment – in such a case the
P5/EN M/11A 169

Table 45 - RSTP parameter values (Continued)
Parameter Default Range Description

Value
port with worse priority (higher value) is disabled
as a backup path for that segment.
Port2 Path Cost 200000 1...200000 Port Cost is related to transfer speed. This is
determined according to RSTP specification.
Port2 Priority 128 0...255 When both Ethernet ports are set connected to
the same network segment – in such a case the
port with worse priority (higher value) is disabled
as a backup path for that segment.
The parameters for the RSTP protocol can be configured via:

• front panel
• Protocol configuration view of COMMUNICATION menu of
eSetup Easergy Pro or Web HMI
Generic Functions for All Redundant Ethernet Modules

• Ethernet 100Base Fx/Tx
The fiber optic ports are full duplex 100 Mbps LC connectors.
• Forwarding
The devices from the families Easergy P5 protection relays support store and
forward mode. The switch forwards messages with known addresses to the
appropriate port. The messages with unknown addresses, the broadcast
messages and the multicast messages are forwarded out to all ports except
the source port. Switches will not forward error packets, 802.3x pause frames
or local packets.
NOTE: Forwarding is active when HSR or RSTP protocol is selected.
• Priority Tagging
802.1p priority tagging is enabled on all ports.
170 P5/EN M/11A

Secure Communication with the eSetup Easergy Pro via the

Ethernet Interface
NOTE: The communication will be done using port 22. Ensure this port is left
unblocked on the network.
When Easergy P5 protection relays and eSetup Easergy Pro are connected via
the Ethernet interface, they will communicate securely using SSH (Secure Shell).
The benefits of secure communication are:
• Help in the prevention of unwanted eavesdropping between eSetup Easergy
Pro and the Easergy P5 protection relays.
• Help in the prevention of modification of data between eSetup Easergy Pro
and the Easergy P5 protection relays.
• Ensure integrity of data.
• Help to prevent replay of data at a later date.
P5/EN M/11A 171

Network Time Protocol (NTP)
Network Time Protocol (NTP)

Network Time Protocol is supported by the Easergy P5 protection relay and the
Redundant Ethernet switch. NTP is used to synchronize the clocks of computer
systems over packet-switched, variable-latency data networks. A jitter buffer is
used to reduce the effects of variable latency introduced by queuing in packet
switched networks, helping to ensure a continuous data stream over the network.
The Easergy P5 protection relays receive the synchronization from the NTP
server. This is done using the IP address of the NTP server entered into the
Easergy P5 protection relays from the eSetup Easergy Pro or Web HMI.
172 P5/EN M/11A

A1 Definitions
A1 Definitions
Abbreviation
AP Access Point
ARP Address Resolution Protocol
ASDU Application Service Data Unit
CID The Configured IED Description (file) is a file used to have communication between
an IED configuration tool to an IED. It can be considered as an SCD file stripped
down to what the concerned IED need to know and contains a mandatory
communication section of the addressed IED.
CIP Common Industrial Protocol
COS Change of State
DA Data Attribute
DAN Double Attached Nodes
DANP Double Attached Nodes implementing PRP
DO Data Object
DS Dateset
GoCB GOOSE Control Block
GOOSE Generic Object-Oriented Substation Event
HTTPS Secured Hypertext Transfer Protocol (HTTPS) is an extension of the Hypertext

Transfer Protocol (HTTP) to help to secure communication over a computer network.
ICD The IED Capability Description (file) completely defines the capabilities of an IED.
This file needs to be supplied by each manufacturer to make the complete system
configuration. The file contains a single IED section, an optional communication
section and an optional substation part which denotes the physical entities
corresponding to the IED.
IED Intelligent Electronic Device – This is a term used to describe microprocessor-based

controllers of power system equipment. Common types of IEDs include protective
relaying devices, load tap changer controllers, circuit breaker controllers, capacitor
bank switches, recloser controllers, voltage regulators, etc.
IID The Instantiated IED Description (file) defines the configuration of one IED for a
project and is used as data exchange format from the IED configurator to the system
configurator. This file contains only the data for the IED being configured: one IED
section, the communication section with the IED's communication parameters, the
IED's data type templates, and, optionally, a substation section with the binding of
functions (LNodes) to the single line diagram.
LAN Local Area Network

LD Logical Device
LN Logical Node
LRE Link Redundancy Entity
MAC Media Access Control

MICS Model Implementation Conformance Statement describes how the information model
is implemented.
MTU Maximum Transmission Unit

PICS Protocol Implementation Conformance Statement describes choices made in
protocol implementation.
PIXIT Protocol Implementation Extra Information for Testing gives any additional
implementation specific information not found in the previous standardized
documents.
RCB Report Control Block
RCT Redundancy Check Tag
RedBox Redundancy Box
SAN Singly Attached Node
P5/EN M/11A 173

A1 Definitions
SCADA Supervisory Control and Data Acquisition
SCD The System (or Substation) Configuration Description is the file describing the
complete power utility automation system details. It contains substation,
communication, IED and Data type template sections. An SSD file and different ICD
files contribute in making an SCD file.
SCL The System Configuration description Language is the language and representation
format specified by IEC 61850 for the configuration of electrical substation devices.
This includes representation of modeled data and communication services specified
by IEC 61850-7-X standard documents. The complete SCL representation and its
details are specified in IEC 61850-6 standard document. It includes data
representation for substation device entities; its associated functions represented as
logical nodes, communication systems and capabilities. The complete representation
of data as SCL enhances the different devices of a substation to exchange the SCL
files and to have a complete interoperability.
sFTP Secured File Transfer Protocol (sFTP) is a network protocol that provides file access,
file transfer, and file management over any reliable data stream.
SNMP Simple Network Management Protocol (SNMP) is an "Internetstandard protocol for

managing devices on IP networks.
SNTP Simple Network Time Protocol (SNTP) is a less complex implementation of NTP,
using the same protocol but without requiring the storage of state over extended
periods of time.
SSH Secure Shell (SSH) is a cryptographic network protocol for operating network
services securely over network communication.
TICS Tissues Conformance Statement describes how the device behaves regarding
identified technica lissues.
UCMM UnConnected Message Manager
UDP User Datagram Protocol
VDAN Virtual Double Attached Nodes

XML Extensible Markup Language
174 P5/EN M/11A

Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison
France
www.schneider-electric.com
As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.
© 2019 – Schneider Electric. All rights reserved.

P5/EN M/11A

Easergy P5 - Communication - P5 - EN M - 11A - 2019 - 05

Uploaded by

Copyright:

Available Formats

Easergy P5 - Communication - P5 - EN M - 11A - 2019 - 05

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Easergy P5 - Communication - P5 - EN M - 11A - 2019 - 05

Uploaded by

Copyright:

Available Formats

Version: P5/EN M/11A

Safety information and password protection

Protocols Used and Data Exchanged

Ethernet Network Architectures

Parallel Redundancy Protocol (PRP)

High-Availability Seamless Redundancy (HSR)

Rapid Spanning Tree Protocol (RSTP)

Ethernet Port Configuration

Table 1 - Ethernet protocol 1 configuration

Parameter Value Description Note

Set protocol default – Default IP port number can be set Set

DNP3 default IP port: 20000

IEC-61850 default IP port: 102

EthernetIP default IP port: 44818

Message counter Number of messages since the device has Clear

Error counter Number of protocol interruptions since Clear

Timeout counter Number of timeout interruptions since Clear

IP Select IP1 Choose the Ethernet module to be used 1 Set

Set = An editable parameter (password needed)

Table 2 - Ethernet port configuration

Parameter Value Description Note

MAC Address Display the MAC address

IP Address n.n.n.n IP address Set

Gateway n.n.n.n Gateway IP address Set

Eth. Port 1 status Link on / Display the connection of Ethernet Port 1

IP select IP1 Choose the Ethernet module to be used by Set

When Ethernet module with PRP/HSR is selected, additional parameters are

Table 3 - Ethernet port configuration (PRP/HSR)

Parameter Value Description Note

FPGA version Display the FPGA version of the Ethernet

Mode Switch PRP / HSR Switch the protocol to be used Set

Serial communication Slot

Serial Port Configuration

Table 4 - Serial port configuration

Parameter Value Description Note

Error counter Number of errors that have been received Clear

Timeout counter Number of timeouts since device has Clear

Set = An editable parameter (password needed)

Port Hardening Configuration

Figure 1 - Port hardening configuration (various from communication

Configuration of IEC 61850 Communication

eSetup Easergy Pro for IEC 61850 Configuration

IEC 61850 Main Configuration

Table 5 - IEC 61850 main configuration

Parameter Description Note

IEC 61850 Measurement Configuration

Table 6 - IEC 61850 measurement configuration

Parameter 4 Description Note

Energy Deadband of the measurements. Set

Unit multiplier Set the unit multiplier of deadband values. Set

IEC 61850 BRCB Configuration

Table 7 - IEC 61850 BRCB configuration

Parameter Description Note

4. These parameters can be set for each individual measurement.

IEC 61850 Datasets

Table 8 - IEC 61850 datasets

Name Name of the dataset

IEC 61850 Variable The data that included in the dataset