proces-rm011_-en-p
proces-rm011_-en-p
Original Instructions
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are
required to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may
be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from
the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous
environment, which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 1
Introduction PlantPAx DCS and IEC 61850. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Required Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Controller Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 2
Configure the Gateway Module Set Up the Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Mapping the Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 3
Integrate IEC 61850 into a Studio Gateway Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5000 Project Import the Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Create Your Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 4
Bulletin 857 Motor/Feeder Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Protection Object InOut Structure for Bulletin 857 from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
InOut Structure for Bulletin 857 from Library Download . . . . 35
Output Structure for Bulletin 857 Relay . . . . . . . . . . . . . . . . . . . . 35
Remote Bit Control Value Structure for Bulletin 857. . . . . . . . . 35
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . . 36
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . . 40
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . . 43
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 5
Bulletin 865 Transformer Object Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
InOut Structure for Bulletin 865 from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
InOut Structure for Bulletin 865 from Library Download . . . . 51
Output Structure for Bulletin 865 Relay . . . . . . . . . . . . . . . . . . . . 51
Remote Bit Control Value Structure for Bulletin 865. . . . . . . . . 51
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . . 52
Chapter 6
SEL 700G Object Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
InOut Structure for SEL700G from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
InOut Structure for SEL700G from Library Download . . . . . . . 67
Remote Bit Control Value Structure for
SEL700G_TripSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . . 68
Associate Controller Tags to ProSoft Add-On Instruction . . . . 68
Configure Trip Source Add-On Instruction . . . . . . . . . . . . . . . . . 71
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . . 73
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . . 77
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Automatic-Synchronization Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Chapter 7
SEL 710 Object Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
InOut Structure for SEL710 from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
InOut Structure for SEL710 from Library Download. . . . . . . . . 91
Remote Bit Control Value Structure for
SEL710_TripSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . . 92
Associate Controller Tags to ProSoft Add-On Instruction . . . . 92
Configure Trip Source Add-On Instruction . . . . . . . . . . . . . . . . . 95
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . . 97
Complete these steps to create a parameter file within your
FactoryTalk® View SE project file. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . 100
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 8
SEL 751A Object Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
InOut Structure for SEL751A from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
InOut Structure for SEL751A from Library Download . . . . . . 111
Remote Bit Control Value Structure for
SEL751A_TripSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . 112
Associate Controller Tags to ProSoft Add-On Instruction . . . 112
Configure Trip Source Add-On Instruction . . . . . . . . . . . . . . . . 114
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . 116
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . 119
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Chapter 9
SEL 787 Object Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
InOut Structure for SEL751A from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
InOut Structure for SEL787 from Library Download. . . . . . . . 129
Remote Bit Control Value Structure for
SEL787_TripSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . 130
Associate Controller Tags to ProSoft Add-On Instruction . . . 130
Configure Trip Source Add-On Instruction . . . . . . . . . . . . . . . . 133
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . 135
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . 138
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Chapter 10
ABB EMAX2 Using EtherNet/IP Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Object InOut Structure for EtherNet/IP ABB EMAX2 from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
InOut Structure for EtherNet/IP ABB EMAX2 from
Library Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Adding a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . 149
Associate Controller Tags to ProSoft Add-On Instruction . . . 149
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Creating a New Parameter File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . 153
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Chapter 11
ABB EMAX2 Using IEC 61850 Controller Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Object InOut Structure for IEC 61850 ABB EMAX2 from
ProSoft Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
InOut Structure for IEC 61850 ABB EMAX2 from
Library Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Remote Command Structure for IEC 61850 ABB
EMAX2_TripSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Mapping InOut Tags to Add-On Instructions . . . . . . . . . . . . . . . . . . 163
Associate Controller Tags to ProSoft Add-On Instruction . . . 163
Using Visualization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Creating a FactoryTalk View SE Parameter File . . . . . . . . . . . . . 167
Linking Parameter Files to an HMI Display. . . . . . . . . . . . . . . . . 170
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Operator Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Engineering Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Help Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
The files that are required to configure the electrical protection devices can be
downloaded from the Product Compatibility and Download Center (PCDC)
at http://compatibility.rockwellautomation.com/Pages/home.aspx.
Operator Engineering
Workstations Workstations
Domain
Stratix 5400 Controller
Stratix 5410
NTP
Layers 4 and 5
Stratix 5700
Layer 2
PTP
VLAN Segmentation
Management (300)
Native - Trunk (301)
Supervisory Network
MCC I/O Network (502)
Process I/O Network (503)
RTU I/O Network (504)
Intelligent Electrical Protection Devices IEC61850 Network (505)
Additional Resources
Introduction
PlantPAx DCS and IEC 61850 The PlantPAx® Distributed Control System architecture provides for the
integration of electrical protection devices via the IEC 61850 standard and the
EtherNet/IP network. The IEC 61850 standard defines a communication
interface that monitors and controls electrical distribution systems with one
common platform regardless of manufacturer. Substation equipment has
evolved from electromechanical to microprocessor- based relays that allow for
communication to industrial control systems.
Time Synchronization
NTP
PTP
VLAN Segmentation
PTP Management (300)
Native - Trunk (301)
Supervisory Network
MCC I/O Network (502)
Process I/O Network (503)
RTU I/O Network (504)
IEC61850 Network (505)
The devices that are shown in Figure 1 include products from Rockwell
Automation, as well as Encompass™ partners, such as Schweitzer Engineering
Labs (SEL) and ProSoft Technology. Faceplates in this manual are also
representative of ABB products.
As the dashed lines show in Figure 2 each physical device shares data across the
network. The data flow is defined by communication and mapping portions of
the IEC 61850 standard.
The gateway organizes the IEC 61850 data from the devices, and
communicates with a controller on an EtherNet/IP network. The ProSoft
gateway configuration software creates Add-On Instructions that decode the
field device power data within the controller.
In addition to the Add-On Instructions, graphic files in this manual link the
devices to an HMI interface. Faceplates for each device present information,
including diagnostics, to operators, engineers, or maintenance personnel.
Required Files The controller and visualization files are required to create instruction sets for
programming logic. This logic is as a supplement to the instruction set
provided natively in the ControlLogix® firmware.
Controller Files
The module Add-On Instruction files are included in the following table
Table 1 - Module Add-On Instruction Files
Module Type Device Name Process Library Add-On Configuration File Description Firmware
Instruction
Power Relays SEL 751A SEL751ATripSource.l5x (RA-LIB) SEL751A.CID Feeder protection relay with arc flash R418 and above
detection
SEL 710/710d5 SEL710TripSource.l5x (RA-LIB) SEL710.CID Motor protection relay 710-5 standard and above
SEL 700G SEL700GTripSource.l5x (RA-LIB) SEL700G.CID Generator protection relay R107 and above
SEL 787 SEL787TripSource.l5x (RA-LIB) SEL787.CID Transformer protection relay R209 and above
AB857 AB857TripSource.l5x (RA-LIB)AB857.CID Feeder protection relay Revisions12.001 and later
AB865 AB865TripSource.l5x (RA-LIB) AB865.CID Generator protection relay Revisions12.001 and later
Circuit Breakers ABB EMAX2 E/IP EMAXEIPTripSource.l5x Ekip2_07_12+key.eds Power circuit breaker with 2.08 and above
communication via EtherNet/IP
ABB EMAX2 IEC 61850 EMAX61850TripSource.l5x (RA-LIB) ABB EMAX2.CID Power circuit breaker with 2.10 and above
communication via IEC 61850
Visualization Files
The display files (.gfx file type) in Table 3 are the displays that you see at
runtime.
Table 2 - Display Files
FactoryTalk View SE Software FactoryTalk View ME Software Description
(RA-SEL) SEL_751A-faceplate (RA-SEL-ME) SEL_751A-faceplate Faceplate for the feeder protection relay with arc flash detection
(RA-SEL) SEL 710d5-faceplate (RA-SEL-ME) SEL 710d5-faceplate Faceplate for the motor protection relay
(RA-SEL) SEL 700G-faceplate (RA-SEL-ME) SEL 700G-faceplate Faceplate for the transformer protection relay
(RA-SEL) SEL 787-faceplate (RA-SEL-ME) SEL 787-faceplate Faceplate for the generator protection relay
(RA-AB) AB 857 61850-faceplate (RA-AB-ME) AB 857 61850-faceplate Faceplate for the feeder protection relay
(RA-AB) AB 865 61850-faceplate (RA-AB-ME) AB 865 61850-faceplate Faceplate for the generator protection relay
(RA-ABB)ABB EMAX2 E/IP-faceplate (RA-SEL-ABB)ABB EMAX2 E/IP-faceplate Faceplate for the power circuit breaker with communication via EtherNet/IP
(RA-ABB) ABB EMAX2 IEC 61850-faceplate (RA-SEL-ABB) ABB EMAX2 IEC 61850-faceplate Faceplate for the power circuit breaker with communication via IEC 61850
IMPORTANT This manual assumes that you are using the IEC 61850 CID files that are
provided on the PCDC. If your application requires additional parameters,
use your manufacturer's configuration software to modify the PCDC CID files
for parameters. Do not delete any content from pre-established reports that
are labeled measurands, alarms, or PB and target status indicators. Deletion
of these reports has an adverse effect on the faceplates.
IMPORTANT Use ProSoft firmware revision 2.01 or later when you integrate the
PlantPAx® objects for electrical protection.
Set Up the Communication The following steps configure a gateway module within the
ProSoft PLX8x-EIP-61850 Configuration Manager. If you do not already have
this software, you can download it from the ProSoft Technology website
(www.prosoft-technology.com).
2. Assign the IP address to the ProSoft Module for the IEC 61850
Network and EtherNet/IP network.
Verify the correct subnet mask and default gateway for each network. If
the 2-port module is being used, the IEC 61850 and EtherNet/IP ports
must be assigned on separate subnets. Also, verify that you select the
correct port for the EtherNet/IP and IEC 61850 services.
3. Click OK.
8. To open the IEC 61850 Tag Mapping Tool, double-click the newly
created block.
9. Expand the LLN0 folder, and then expand the Reports folder.
10. Drag Measurands (Buffered Report 1), Alarms (Buffered Report 2), and
status indicators (Buffered Report 3) to the canvas on the right.
IMPORTANT For each additional report, drag reports into the canvas to move the data to a
controller.
11. For SEL devices, expand the Control folder and RBGGIO1 folder.
12. Expand SPCSO1 through SPCSO8.
13. Expand Oper and select ctlVal. Drag these values to the canvas in
addition to any other commands required for your application.
14. For ABB Devices, expand LD0, CS2I1, and Pos folders.
15. Expand Oper and Cancel folders. Drag these values to the canvas in
addition to any other commands required for your application.
17. Repeat steps 3…9 for every gateway module being added to the system.
IMPORTANT The faceplates and three pre-defined buffered reports for the devices use the
data in Table 5.
IMPORTANT These conditions apply only when you use the CID files from PCDC and the
files are not modified.
1. Once you have added all devices within the system, double-click the
EtherNet/IP block in the configuration manager canvas. This action
opens the EtherNet/IP Mapping Window.
6. Right-click the ProSoft module in the canvas and select Download From
PC to Device.
11. Right-click the ProSoft Module Block and select Export AOI Files.
TIP For a full list of the device tags that are included, see
IEC61850_IED_Tags.xlsx under the tools folder of the download.
Notes:
This section describes how to connect the ProSoft gateway module to the
Rockwell Automation® Studio 5000® environment. This module provides the
communication link between the PlantPAx® system and the IEC 61850
devices.
Topic Page
Gateway Integration 25
Import the Add-On Instructions 28
Create Your Routine 30
Gateway Integration If you have a project with a controller already configured, make sure that the
project path is set to the correct controller. For the purposes of this document, we
refer to this path as the target application.
The ProSoft gateway that is created in Chapter 2 must be added into the project
I/O configuration.
IMPORTANT The following procedure uses the gateway that you configured in Chapter 2.
Make sure that the Slot positions of the controller and the Ethernet
module are correct.
3. Right-click Ethernet and choose New Module.
IMPORTANT Verify that the gateway IP address is an exact match with the IP
address that you assigned to the module ports in step 2 of
Chapter 2.
7. Click OK.
8. Right-click CIP Bus and choose New Module.
9. Click the Comm Format pull-down arrow and select the Comm Format
(Data-SINT).
10. In the Connection Parameters box, type the values exactly as shown in
the following Module Properties Report dialog box.
Your CIP connection for the bridge is now in the I/O Configuration
tree.
12. Repeat steps 8…11 for each module that you are configuring with CIP
connections.
Import the Add-On You have successfully configured the ProSoft gateway within your Studio 5000
project. The following steps define how to import the IEC 61850 data via the
Instructions Add-On Instruction that was exported in Chapter 2.
4. Click OK.
5. Repeat steps 1…4 for each device Add-On Instruction that was created
by the ProSoft gateway.
For this example, we have four devices that require the use of four
Add-On Instructions and nine CIP connections.
Create Your Routine The following steps define how to use the ProSoft gateway Add-On
Instructions to create a Studio 5000 project that can be downloaded to a
controller.
6. Inside the top of the function block, double-click the tag name and type a
new name.
7. Click Enter.
8. Right-click the new tag name and choose New <new tag name> (New
IED700G_01 in this example).
By default the New Tag dialog box includes the tag name, data type, and
external access (Read/Write)
9. Type an optional description and select a scope from the pull-down
menu. Controller scope is selected in our example.
10. Click Create.
11. Repeat steps 5…9 for each function block required.
You have successfully configured the ProSoft gateway module in your Studio
5000 project.
The Bulletin 857 Relay is a combined motor and feeder protection relay that is
used for various tasks. These tasks include highly selective protection of
rotating machines, line feeders, cable feeders, capacitor banks, reactors,
transformers, and bus bars.
This instruction monitors one 857 relay. Alarms are provided when the
physical device experiences a protection-related trip. The instruction also
provides capabilities for locking, opening, and closing the breaker.
Faceplate
Add-On Instruction
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Table 7 shows the InOut parameters that are available from the Rockwell
Automation Library of Electrical Protection Devices Folder in the PCDC.
These external tags must be of the data type shown. These tags are
representative of the tags that are required for each 857 relay.
Table 7 - Bulletin 857 Device
Name Data Type Description
[DeviceName]_AOI [DeviceName]857_AOI Add-On Instruction tag. Matches naming from ProSoft
Configuration Manager.
Connection_Input0 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output0 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
Connection_Input1 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output1 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
[DeviceName]857 [DeviceName]857 Device data that is collected from the CIP connections and
organized into understandable tags. This data type changes to
match each device tag in the ProSoft Gateway.
These parameters are used to link the Add-On Instruction to the HMI. These
tags are representative of the tags that are required for each 857relay. These
parameters are a subset of the full variable list available from the device.
The CID files that are provided with the download provide you with these
measurement values from the physical device already selected and ready to load
into the ProSoft gateway. This selection verifies that all variables that are
needed for correct HMI operation are present.
For a full list of the relay variables included, see List_Of_Variables.xls under
the tools folder of the download.
Remote Bit Control Value parameters are used to link the Add-On Instruction
to configurable input points in the device. Each bit is configurable through the
device vendor software. Table 8 has the recommended uses for each bit.
Table 8 - Remote Bit Control - Bulletin 857
Name Description
VI1GGIO137_CO_SPCSO_ctlVal Enable/Disable
Mapping InOut Tags to Add- Each 857 relay requires two Add-On Instructions to monitor and visualize the
On Instructions relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
Instruction is downloaded from the Rockwell Automation Library of
Electronic Protection Devices from the PCDC.
5. Repeat this process for Connection Input and Output that are included
with your Add-On Instructions.
This tag has the same name as the Add-On Instruction and the device as
configured in the ProSoft Gateway.
7. Type in a name for this tag. In this example, the name is “Feeder”.
8. Right-click on the new tag name and select New <tag name>.
11. Click the question mark next to each Ref_Tgt#Txt and enter a string
tag. These tags are intended to match the status indicators on the front
panel of the device.
12. Once you type the tag name, if the tag is not already configured in the
controller, you have to right-click and create a tag.
13. Click the question mark next to Bulletin 857TripAlarm and select or
create the digital alarm tag to be used.
This tag is used for alarming through the HMI FactoryTalk® Alarm and
Event Server.
14. Click the question mark next to Bulletin 857TripText and select or
create the tag to be used.
This tag is used for alarm message through the HMI FactoryTalk Alarm
and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1= under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
6. Expand the folders and select the tag that was created for the device
TripSource Add-On Instruction. Click OK.
You can see the parameter file in the list in the Application Window.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project. For this
example, we are adding a button.
3. In the Button Properties, set the release action of the button as shown in
the following image.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The Bulletin 857_TripSource faceplate consists of six tabs and each tab consists
of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
Lock/Unlock
Faceplate Status
Indicators
Close Breaker
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 9 - Operator Tab Description
Function Action
Click to lock or unlock device. Function locks the device from accepting commands.
Click to reset the device. The status of the device is indicated on the faceplate.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
The Allen-Bradley® 865 is a differential protection relay that is used for various
tasks. These tasks include selective differential protection of substation
transmission lines, medium voltage overhead and cable feeders, rotating
machines, transformer feeders, capacitor banks, generators, reactors and bus
bars. The relay is used in power system distribution substations, power plants,
industrial power systems, and marine and offshore installations.
This instruction monitors one 865 relay. Alarms are provided when the
physical device experiences a protection-related trip. The instruction also
provides capabilities for opening and closing the breaker. It is also possible to
switch between the two available breakers.
Faceplate
Add-On Instruction
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Table 11 shows the InOut parameters that are available from the Rockwell
Automation Library of Electrical Protection Devices Folder in the PCDC.
These external tags must be of the data type shown. These tags are
representative of the tags that are required for each 865 relay.
Table 11 - Bulletin 865 Device
Name Data Type Description
[DeviceName]_AOI [DeviceName]_AOI Add-On Instruction tag. Matches naming from ProSoft
Configuration Manager.
Connection_Input0 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output0 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
Connection_Input1 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output1 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
[DeviceName]865 [DeviceName]865 Device Data that is collected from the CIP connections and
organized into understandable tags. This data type changes to
match each device tag in the ProSoft Gateway.
These parameters are used to link the Add-On Instruction to the HMI. These
tags are representative of the tags that are required for each 865 relay. These
parameters are a subset of the full variable list available from the device.
The CID files that are provided with the download provide you with these
measurement values from the physical device already selected and ready to load
into the ProSoft gateway. This selection verifies that all variables that are
needed for correct HMI operation are present.
For a full list of the relay variables included, see List_Of_Variables.xls under
the tools folder of the download
Remote Bit Control Value parameters are used to link the Add-On Instruction
to configurable input points in the device. Each bit is configurable through the
device vendor software. Table 12 has the recommended uses for each bit.
Table 12 - Remote Bit Control - Bulletin 865 Device
Name Description
VI1GGIO137_CO_SPCSO_ctlVal Breaker Select
Mapping InOut Tags to Add- Each 865 relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation Library of
Electronic Protection Devices from the PCDC.
4. Repeat this process for Connection Input and Output that are included
with your Add-On Instructions.
5. Click the question mark next to the final tag. This tag has the same
name as the Add-On Instruction and the device as configured in the
ProSoft Gateway.
6. Type in a name for this tag. In this example, the name is “Transformer”.
7. Right-click on the new tag name and select New <tag name>.
10. Click the question mark next to each Ref_Tgt#Txt and enter a string
tag. These tags are intended to match the status indicators on the front
panel of the device.
11. Once you type the tag name, if the tag is not already configured in the
controller, you have to right-click and create a tag.
12. Click the question mark next to Bulletin 865TripAlarm and select or
create the digital alarm tag to be used.
This tag is used for alarming through the HMI FactoryTalk® Alarm and
Event Server.
13. Click the question mark next to Bulletin 865TripText and select or
create the tag to be used.
This tag is used for alarm message through the HMI FactoryTalk Alarm
and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1= under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
6. Expand the folders and select the tag that was created for the device
TripSource Add-On Instruction. Click OK.
9. You can see the parameter file in the list in the Application Window.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project. For this
example, we are adding a button.
3. In the Button Properties, set the release action of the button as shown in
the following image.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The Bulletin 865_TripSource faceplate consists of six tabs and each tab consists
of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
Breaker Select
Faceplate Status
Indicators
Close Breaker
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 13 - Operator Tab Description
Function Action
Click to reset the device. The status of the device is indicated on the faceplate.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
Topic Page
Controller Code 66
Mapping InOut Tags to Add-On Instructions 68
Using Visualization Files 73
Faceplates 79
The following instruction monitors one SEL700G relay. Alarms are provided
when the device experiences a protection-related trip. The instruction also
provides capabilities for locking, opening, and closing the breaker.
Synchronization control of the device is also permitted through the instruction.
Add-On Instruction Faceplate
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Remote Bit Control Value parameters are used to link the Add-On Instruction
to configurable input points in the physical device. Each bit is configurable via
the vendor software of each device. Table 16 has recommended uses for each
bit.
Table 16 - Remote Bit Control - SEL700G Relay
Name Description
CON_RBGGIO1_CO_SPCSO01_Oper_ctlVal Lock/Unlock
CON_RBGGIO1_CO_SPCSO02_Oper_ctlVal Target Reset
CON_RBGGIO1_CO_SPCSO03_Oper_ctlVal Breaker Close
CON_RBGGIO1_CO_SPCSO04_Oper_ctlVal Breaker Open
CON_RBGGIO1_CO_SPCSO05_Oper_ctlVal AUX
CON_RBGGIO1_CO_SPCSO06_Oper_ctlVal Enable SYNC
CON_RBGGIO1_CO_SPCSO07_Oper_ctlVal Frequency SYNC
CON_RBGGIO1_CO_SPCSO08_Oper_ctlVal Voltage SYNC
IMPORTANT The bits shown in Table 16 are dependent on the use of the IEC 61850 CID
files and your gateway is configured as described in Chapter 2. The IEC 61850
CID files are provided on the PCDC. If your application requires additional
parameters, use your manufacturer's configuration software to modify the
PCDC CID files.
Mapping InOut Tags to Add- Each SEL700G relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation® Library of
Electronic Protection Devices from the PCDC.
Complete these steps to map the ProSoft instruction to Studio 5000 tags.
5. Repeat this process for each connection input and output that are
included with your Add-On Instructions.
6. Click the question mark next to the final tag. Enter a clear engineering
name to this tag that represents your device within your Studio 5000
project. In this example, the name is “Generator”.
7. Right-click on the new tag name and select New “<tag name>”.
Now that the SEL700G Add-On Instruction has been configured, you must
configure the SEL700G trip source Add-On Instruction for alarming.
2. Click the question mark next to each Ref_Tgt#Txt and enter a string tag.
These tags are intended to match the status indicators on the front panel
of the device.
3. Once you type the tag name, if needed, right-click and create a tag if that
the tag is not already configured in the controller.
This tag is used for alarming through the HMI FactoryTalk® Alarm and
Event Server.
This tag is used for the alarm message through the HMI FactoryTalk®
Alarm and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1= under the comment box. Then double-click to the right of the
= to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
6. Expand the folders and select the tag that was created for the SEL700G
TripSource Add-On Instruction. Click OK.
You can see the parameter file in the list in the Application Window.
Now that the SEL700G controller tags are linked to the parameter file, you
must add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The SEL700G
faceplate consists of three tabs and each tab consists of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E F G H
• A - Operator
• B - Sync
• C - Engineering
• D - Diagnostics
• E - X-side Diagnostics
• F - Y-side Diagnostics
• G - Help
• H - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
Lock/Unlock
AUX input
Faceplate Status
Indicators Close Breaker
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 17 - Operator Tab Description
Function Action
To issue the commands to the device, unlock the device. If the device is locked, you can only
monitor data from the device.
Click to reset the device. The status of the device is indicated on the faceplate.
Click to toggle the AUX input to the device. This input is configurable in the device vendor
software. This button provides a configurable interface to provide a user chosen command.
Automatic-Synchronization Tab
Sync Status
The following table shows the functions that are included on the Operator tab.
Table 18 - SYNC Tab Description
Function Action
Click to initiate Auto-Sync.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Readout of the X-side measurement values from the SEL-700G. This readout
displays fundamental metering data that is associated with the X-side of the
generator.
Readout of the Y-side measurement values from the SEL-700G. This readout
displays fundamental metering data that is associated with the Y-side of the
generator.
Readout of the temperatures from the 12 RTD inputs that are available in the
SEL-700G.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device. The
first tab shows general diagnostics for the entire generator. There are separate
tabs for the X-Side and Y-Side conditions.
Help Tab
The following instruction monitors one SEL710 relay. Alarms are provided
when the device experiences a protection-related trip. The instruction also
provides capabilities for starting and stopping the motor and two auxiliary
inputs.
Add-On Instruction Faceplate
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Mapping InOut Tags to Add- Each SEL710 relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation® Library of
Electronic Protection Devices from the PCDC.
Complete these steps to map the ProSoft instruction to Studio 5000® tags.
4. Click the down arrow on the drop box and expand the
ProSoft_Gateway:0:O. Select the ProSoft_Gateway:0:O.Data and
double-click to choose it.
5. Repeat this process for each Connection Input and Output that are
included with your Add-On Instructions.
6. Click the question mark next to the final tag. Enter a clear engineering
name to this tag that represents your device within your Studio 5000
project. In our example “Motor”.
7. Right-click on the new tag name and select New “<tag name>”.
Now that the SEL710 Add-On Instruction has been configured, you must
configure the SEL710 trip source Add-On Instruction for alarming.
2. Next click the question mark next to each Ref_Tgt#Txt and enter a
string tag. These tags are intended to match the status indicators on the
front panel of the device.
3. Once you type the tag name, if the tag is not already configured in the
controller, you have to right-click and create a tag.
This tag is used for alarming through the HMI FactoryTalk® Alarm and
Event Server.
This tag is used for alarm message through the HMI FactoryTalk Alarm
and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
Complete these steps to create a parameter file within your FactoryTalk® View
SE project file.
2. Type #1= under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Then click OK.
6. Expand the folders and select the tag that was created for the SEL710
TripSource Add-On Instruction. Click OK
7. Click the save icon and name the parameter file. Click OK when you are
finished.
You can see the parameter file in the list in the Application Window.
Now that the SEL710 controller tags are linked to the parameter file, you must
add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
3. In the Button Properties, set the release action of the button as shown in
the following image.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The SEL710
faceplate consists of three tabs and each tab consists of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
AUX1 Input
AUX2 Input
Faceplate Status
Indicators Motor Start
Motor Stop
The following table shows the functions that are included on the Operator tab.
Table 22 - Operator Tab Description
Function Action
Click to reset the device. The status of the device is indicated on the faceplate.
Click to toggle the AUX input to the device. This input is configurable in the device vendor
software.
Click to toggle the AUX input to the device. This input is configurable in the device vendor
software.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Readout of the temperatures from the12 RTD inputs that are available in the
SEL-710.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
Notes:
The Schweitzer Engineering Labs 751A is a feeder protection relay with arc
flash protection. This device is used to protect an electrical bus from
conditions of over current, over voltage, under voltage, and so on. The device
also provides multiple fundamental metering data including, voltage, current,
frequency, and power. When retrofitted with RTD capability, the SEL 751A
can also provide various temperature measurements at locations on the
electrical bus.
Topic Page
Controller Code 110
Mapping InOut Tags to Add-On Instructions 112
Using Visualization Files 116
Faceplates 121
This instruction monitors one SEL751A relay. Alarms are provided when the
device experiences a protection-related trip. The instruction also provides
capabilities for locking, opening, and closing the breaker.
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Table 24 shows the InOut parameters that are available from the Rockwell
Automation® Library of Electrical Protection Devices Folder in the PCDC.
These external tags must be of the data type shown.
Table 24 - SEL751A_TripSource
Name Data Type Description
[DeviceName]_Relay_Name <Defined by device Device data from the Add-On Instruction. This data type
AOI> changes to match each device tag in the ProSoft
Gateway.
Ref_Tgt3Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt4Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt5Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt6Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt7Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software
Ref_Tgt8Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
[DeviceName]TripAlarm ALARM_DIGITAL Digital Alarm tag
[DeviceName]TripText STRING Alarm text to be displayed when active.
Mapping InOut Tags to Add- Each SEL751A relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation Library of
Electronic Protection Devices from the PCDC.
5. Repeat this process for each Connection Input and Output that are
included with your Add-On Instructions.
6. Click the question mark next to the final tag. Type a tag name that
represents your physical device within your Studio 5000 project. In this
example, the name is “Feeder”.
7. Right-click the new tag name and select New “<tag name>”.
Now that the SEL751A Add-On Instruction has been configured, you must
configure the SEL751A trip source Add-On Instruction for alarming.
2. Next click the question mark next to each Ref_Tgt#Txt and enter a
string tag. These tags are intended to match the status indicators on the
front panel of the device.
3. Once you type the tag name, if the tag is not already configured in the
controller, you have to right-click and create a tag.
This tag is used for alarming through the HMI FactoryTalk® Alarm and
Event Server.
This tag is used for alarm message through the HMI FactoryTalk Alarm
and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1= under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
6. Expand the folders and select the tag that was created for the SEL751A
TripSource Add-On Instruction. Click OK.
You can see the parameter file in the list in the Application Window.
Now that the SEL751A controller tags are linked to the parameter file, you
must add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The SEL751A
faceplate consists of three tabs and each tab consists of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
AUX Input
Lock/Unlock
Faceplate Status
Indicators Close Breaker
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 26 - Operator Tab Description
Function Action
Click to lock or unlock device. Function locks the device from accepting commands.
Click to reset the device. The status of the device is indicated on the faceplate.
Click to toggle the AUX input to the device. This input is configurable in the device vendor
software.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Readout of the temperatures from the 12 RTD inputs that are available in the
SEL-751A.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
Notes:
This instruction monitors one SEL787 relay. Alarms are provided when the
device experiences a protection-related trip. The instruction also provides
capabilities for locking, opening, and closing the breaker. It is also possible to
switch between the two available breakers.
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Table 28 shows the InOut parameters that are available from the Rockwell
Automation® Library of Electrical Protection Devices Folder in the PCDC.
These external tags must be of the data type shown.
Table 28 - SEL787 TripSource
Name Data Type Description
[DeviceName]_Relay_Name <Defined by device Device data from the Add-On Instruction. This data type
AOI> changes to match each device tag in the ProSoft
Gateway.
Ref_Tgt3Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt4Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt5Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt6Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
Ref_Tgt7Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software
Ref_Tgt8Txt STRING Alarm description for device front plate status
indicators. This is configurable through device vendor
software.
[DeviceName]TripAlarm ALARM_DIGITAL Digital Alarm tag
[DeviceName]TripText STRING Alarm text to be displayed when active.
Remote Bit Control Value parameters are used to link the Add-On Instruction
to configurable input points in the physical device. Each bit is configurable via
the vendor software of each device. Table 29 has recommended uses for each
bit.
Name Description
CON_RBGGIO1_CO_SPCSO01_Oper_ctlVal Lock/Unlock
CON_RBGGIO1_CO_SPCSO02_Oper_ctlVal Target Reset
CON_RBGGIO1_CO_SPCSO03_Oper_ctlVal Breaker Close
CON_RBGGIO1_CO_SPCSO04_Oper_ctlVal Breaker Open
CON_RBGGIO1_CO_SPCSO05_Oper_ctlVal Breaker Select
CON_RBGGIO1_CO_SPCSO06_Oper_ctlVal User Programmable
CON_RBGGIO1_CO_SPCSO07_Oper_ctlVal User Programmable
CON_RBGGIO1_CO_SPCSO08_Oper_ctlVal User Programmable
Mapping InOut Tags to Add- Each SEL787 relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation Library of
Electronic Protection Devices from the PCDC.
5. Repeat this process for each Connection Input and Output that are
included with your Add-On Instructions.
6. Click the question mark next to the final tag. Enter a clear engineering
name to this tag that represents your device within your Studio 5000®
project. In this example “Transformer”.
7. Right-click the new tag name and select New “<tag name>”.
Now that the SEL787 Add-On Instruction has been configured, you must
configure the SEL787 trip source Add-On Instruction for alarming.
1. Click the question mark next to SEL787_Relay_Name and select the tag
that was created in step 8.
2. Next click the question mark next to each Ref_Tgt#Txt and enter a
string tag. These tags are intended to match the status indicators on the
front panel of the device. Once you type the tag name, if the tag is not
already configured in the controller, you have to right-click and create a
tag.
This tag is used for alarm message through the HMI FactoryTalk Alarm
and Event Server.
Fully Configured Add-On Instruction
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1= under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
6. Expand the folders and select the tag that was created for the device
TripSource Add-On Instruction. Click OK.
You can see the parameter file in the list in the Application Window.
Now that the SEL787 controller tags are linked to the parameter file, you must
add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The SEL787
faceplate consists of three tabs and each tab consists of one or more pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device.
Trip Reset
Lock/Unlock
Breaker Select
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 29 - Operator Tab Description
Function Action
Click to lock or unlock device. Function locks the device from accepting commands.
Click to reset the device. The status of the device is indicated on the faceplate.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the device.
Diagnostic Tab
The diagnostic tab shows which alarms are active from the device.
Help Tab
The ABB EMAX2 is a power/air circuit breaker that has been configured with
an electronic trip unit. This device can communicate on various industrial and
electrical distribution networks including, EtherNet/IP, and IEC 61850. The
device can be controlled via remote command with proper credentials.
Additionally, the device also provides multiple fundamental metering data
including, voltage, current, frequency, power, and more.
Topic Page
Controller Code 146
Mapping InOut Tags to Add-On Instructions 149
Using Visualization Files 150
Faceplates 155
This instruction monitors one ABB EMAX2 breaker communication via the
EtherNet/IP ABB. Alarms are provided when the device experiences a
protection-related trip. The instruction also provides capabilities for opening,
and closing the breaker.
Add-On Instruction Faceplate
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
Table 31 shows the InOut parameters that are available from the Rockwell
Automation® Library of Electrical Protection Devices Folder in the PCDC.
These external tags must be of the data type shown.
Table 31 - EMAX2 TripSource
Name Data Type Description
EMAX2CB _0526:002B_0101_82C511B0:I:0 Device Input Data Structure
EMAX2CB _0526:002B_0101_82C511B0:O:0 Device Output Data Structure
Adding a Device
3. Select the ABB Ekip COM EtherNet/IP module from the module list
and click Create.
4. Enter the name and IP address for the ABB EMAX2 circuit breaker.
Click OK.
5. Now you can see the circuit breaker in your project tree and tags in the
controller tags.
Mapping InOut Tags to Add- Each EMAX2 relay requires two Add-On Instructions to monitor and visualize the
relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation® Library of
Electronic Protection Devices from the PCDC.
Using Visualization Files The ABB EMAX2 EtherNet/IP breaker visualization in FactoryTalk® View is
accomplished with the use of parameter files. These files link the device
controller tags to the faceplate tag placeholders. Each device requires a
parameter file to be created.
You can see the parameter file in the list in the Application Window.
Now that the EMAX2 controller tags are linked to the parameter file, you must
add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The ABB
EMAX2 faceplate consists of three tabs and each tab consists of one or more
pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device when it is in Operator mode.
Activate Wink
Close Breaker
Faceplate Status
Indicators
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 32 - Operator Tab Description
Function Action
Wink is an ABB diagnostic function that allows for blinking of status indicator to locate which
device you're communicating with. Activate the diagnostic wink function of the circuit breaker.
This activation allows for discovery of the breaker.
Click to close the circuit breaker.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Engineering Page
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
Notes:
The ABB EMAX2 power circuit breaker provides a user the benefits of a
power circuit breaker that is combined with the intelligence of a device. The
ABB EMAX2 contains an electronic trip unit that can communicate with
upstream control systems via a number of protocols and standards. When
equipping the ABB EMAX2 with IEC 61850 communications, you can
configure various MMS and GOOSE communications that allow SCADA/
monitoring communications in addition to high speed interlocking. This
chapter discusses how to integrate the EMAX2 that communicates via IEC
61850 for SCADA purposes to the PlantPAx® system.
Topic Page
Controller Code 162
Mapping InOut Tags to Add-On Instructions 163
Using Visualization Files 167
Faceplates 172
This instruction monitors one ABB EMAX2 breaker communication via the
EtherNet/IP ABB. Alarms are provided when the device experiences a
protection-related trip. The instruction also provides capabilities for opening,
and closing the breaker.
Add-On Instruction Faceplate
Controller Code Two Add-On Instructions represent each physical device. You must configure
the InOut parameters of each Add-On Instruction per physical device.
InOut Structure for IEC 61850 ABB EMAX2 from ProSoft Add-On
Instruction
InOut parameters are used to link the Add-On Instruction to external tags that
contain necessary data for the instruction to operate. These external tags must
be of the data type shown.
Name Data Type Description
CircuitBreaker <Defined by device AOI> Device data from the device Add-On
Instruction. This data type changes to match
each device tag in the ProSoft Gateway.
InOut Structure for IEC 61850 ABB EMAX2 from Library Download
InOut parameters are used to link the Add-On Instruction to external tags that
contain necessary data for the instruction to operate. These external tags must
be of the data type shown. These tags are representative of the tags that are
required for each IEC 61850ABB EMAX2 that is configured in your system.
Name Data Type Description
[DeviceName]_AOI [DeviceName]_AOI Add-On Instruction tag. Matches naming from ProSoft
Configuration Manager.
Connection_Input0 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output0 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
Connection_Input1 SINT[500] CIP Connection Input data. The number of these parameters
vary depending on system sizing.
Connection_Output1 SINT[496] CIP Connection Output data. The number of these parameters
vary depending on system sizing.
[DeviceName] [DeviceName] Device data that is collected from the CIP connections and
organized into understandable tags. This data type changes to
match each device tag in the ProSoft Gateway.
Remote Bit Control Value parameters are used to link the Add-On Instruction
to configurable input points in the physical device. Each bit is configurable via
the vendor software of each device. The following table has recommended uses
for each bit.
Control Bit Function
PlantPAxEMAX2LD0_CSWI1_CO_Pos_Oper_ctlVal Issue Open/ Command via Toggle
PlantPAxEMAX2LD0_CSWI1_CO_Pos_Cancel_ctlVal Issue Command Canceled
Mapping InOut Tags to Add- Each 61850 EMAX2 relay requires two Add-On Instructions to monitor and visualize
the relay. The ProSoft Software instruction is created in Chapter 2. The Add-On
On Instructions Instruction is downloaded from the Rockwell Automation® Library of
Electronic Protection Devices from the PCDC.
Complete these steps to map the ProSoft instruction to Studio 5000® tags.
5. Repeat this process for Connection Input and Output that are included
with your Add-On Instructions.
6. Click the question mark next to the final tag. This tag has the same
name as the Add-On Instruction and the device as configured in the
ProSoft Gateway. Type in a name for this tag. In this example, the name
is Circuitbreaker.
7. Right-click on the new tag name and select New “<tag name>”.
Using Visualization Files The IEC 61850 object visualization in FactoryTalk® View is accomplished with
the use of parameter files. These files link the device controller tags to the
faceplate tag placeholders. Each physical device requires a parameter file to be
created.
2. Type #1=:: under the comment box. Then double-click to the right of
the = to open the Tag Browser dialog box.
3. Expand the folders and select the tag that was created for the device
Relay Name. Click OK.
You can see the parameter file in the list in the Application Window.
Now that the 61850 EMAX2 controller tags are linked to the parameter file,
you must add components to the display that the operator sees.
If you already have a display that was created with the device objects,
simply expand the Display tree and double-click the display name to
open it.
2. Add the objects to the display that you need for your project.
The button, when clicked, displays the faceplate and links the associated
parameter file.
4. Save and type a name for the display.
5. Click OK.
Faceplates The faceplates for each physical device are contained in the Accessory File that
is part of the Rockwell Automation Library of Process Objects. The 61850
EMAX2 faceplate consists of three tabs and each tab consists of one or more
pages.
The Operator tab is displayed when the faceplate is initially opened. Click the
appropriate icon at the top of the faceplate to access a specific tab.
A B C D E
• A - Operator
• B - Engineering
• C - Diagnostics
• D - Help
• E - Exit
Operator Tab
The Faceplate initially opens to the Operator tab, sometimes called the Home
tab. From here, an operator can monitor the device status and manually operate
the device when it is in Operator mode.
Close Breaker
Open Breaker
The following table shows the functions that are included on the Operator tab.
Table 33 - Operator Tab Description
Function Action
Click to control AUX input.
Engineering Tab
The engineering tab allows the operator to see the measurement values from
the physical device.
Engineering Page
Diagnostic Tab
The diagnostic tab shows which alarms are active from the physical device.
Help Tab
Glossary For definitions of terms not listed here, refer to the Allen-Bradley Industrial
Automation Glossary, publication AG-7.1.
Add-On Instruction Add-On Instructions are reusable code objects that contain encapsulated logic
that can streamline the implementation of your system. The objects let you
create your own instruction set for programming logic as a supplement to the
instruction set provided natively in the ControlLogix® firmware. An Add-On
Instruction is defined once in each controller project, and can be instantiated
multiple times in your application code as needed.
address conflict detection (ACD) Allows a device to detect if another device is using its IP address. This ACD is
not to be confused with the .acd file extension, which is associated with the
RSLogix 5000 software tool. The .acd file stores a programming project.
Address Resolution Protocol (ARP) A broadcast message that asks who has this IP address; enables a network to
learn and adapt to changes.
alarm event A push notification from the alarm object to the alarm subscriber indicating a
change in alarm state.
alarm management The processes and practices for determining, documenting, designing,
operating, monitoring, and maintaining alarm systems.
alarm object The alarm system element that owns the alarm; it is responsible to identify an
alarm, managing the state, and generating an alarm event.
alarm priority An attribute of In-Alarm event that informs you of the salience of the event.
alarm system The collection of hardware and software that detects an alarm state,
communicates the indication of that state to the operator, and records changes
in the alarm state.
application objects These objects define how device data is represented and accessed.
application server (AppServ) The application server (AppServ) is a server in addition to the Process
Automation System Server (PASS) that is typically a FactoryTalk® Directory
client of the PASS. Examples are AppServ-Batch for a FactoryTalk Batch
application or AppServ-History for an Historian application.
automatic device configuration A Studio 5000 software feature that supports the automatic download of
(ADC) configuration data into a Logix controller. The download establishes an
EtherNet/IP network connection to a device.
automatic device replacement (ADR) A Studio 5000 software feature that automatically commissions the original
node address, and downloads the original configured device parameters into
the new device.
CIP connection Transfers data from an application that runs on one end node (transmitter) to
an application that runs on another end node (receiver); uses explicit or
implicit message types; connected message types are used to transfer data;
connected message type can use implicit or explicit messages; unconnected
messages are used temporarily and only use explicit messages.
CIP sync Time synchronization service for CIP. Synchronizes clocks across devices on
the network; a single time master with multiple slaves.
control strategy A control strategy is a system footprint to show the complexity of the
following:
• Data servers
• Information storage
• Operator interface (graphics, faceplates)
• Control code (sequence, procedure, phases)
• I/O
Configured IED Description (CID) An XML file that defines all information that can be communicated from the
Intelligent Electronic Device (IED).
Converged Plant-wide Ethernet An architecture that provides standard network services to application
(CPwE) devices and equipment in an Industrial Automation and Control System
(IACS) application; integrates the devices and equipment into the wider
enterprise.
critical system attribute (CSA) A critical system attribute (CSA) is a customer-facing characteristic that
defines or identifies whether the system is performing as expected. CSAs are
specific, visible indicators of overall system performance and usability.
CSAs have specified parameters that must be maintained and that set the base
operational requirements for the system. These parameters determine pass or
fail (follow up) of a system test. For example, screen paint time < 2 seconds and
screen refresh < 1 second.
There are many other attributes associated with system elements such as
controller loading, computer loading, and network settings that must be
configured properly to maintain system CSAs.
datastore Represents a storage location for virtual machine files. A storage location can
be a virtual machine file system volume, a local file system path, or a directory
on Network Attached Storage.
Device Level Ring (DLR) A single, fault-tolerant network for interconnection of automatic devices;
Layer 2 protocol.
display object A display object is a functional group of display elements with animations.
distributed control system (DCS) A specially designed control system for complex and large applications in
industrial processes wherein the control elements of the system are distributed
geographically throughout the plant. In a DCS, a hierarchy of controllers is
connected by communication networks for command and monitoring.
Domain Name System (DNS) A name resolution protocol that enables identification of devices by name
instead of IP address.
Electronic data sheet (EDS) An ASCII text file that describes the features of an EtherNet/IP device and is
used by software tools for device and network configuration.
engineering workstation (EWS) The engineering workstation (EWS) provides system configuration,
development, and maintenance functions of the PlantPAx system. The EWS
contains development software, including FactoryTalk View SE Studio and
Studio 5000 Logix Designer.
ESXi hypervisor Also called a ‘bare metal’ hypervisor, this virtual software is on top of the
resources of a host server when the server does not have an operating system
installed.
FactoryTalk directory software FactoryTalk Directory software defines were system data is stored for access.
FactoryTalk Directory software provides a common address book of factory
resources that are shared among FactoryTalk-enabled products.
FactoryTalk services platform The FactoryTalk Services Platform (FTSP) is a service-oriented architecture
(see SOA) that delivers value through FactoryTalk-enabled products. This
platform reduces the customer learning curve and project engineering time
through commonality and reuse. For example, activation, FactoryTalk
Directory, security, diagnostics, audit, live data, and alarms and events.
full-duplex mode A data transmission mode that is deterministic, collision-free, and can transmit
and receive at the same time.
function block diagram A graphical language for programmable logic controller design that describes
the function between input variables and output variables.
Generic Object Oriented Substation A control strategy to remotely collect and control devices in a distributed
Event (GOOSE) system.
global object An object that is created once and can be referenced multiple times on multiple
displays in an application.
historical data Historical data is data that is used for the long term analysis of past operation.
hypervisor A program that lets multiple operating systems share resources from a single
hardware host; also called a virtual machine manager. The hypervisor manages
the host processor and resources, allocating what is needed to each virtual
machine to make sure they cannot negatively impact each other.
hypervisor client A program that lets you remotely connect to a host server with a hypervisor
from any workstation. From the hypervisor client, you can create, deploy, copy,
and edit your virtual machines. When a hypervisor client connects to a
implicit connection Time critical in nature. For example, I/O and produced/consumed tags.
Integrated Architecture (IA) Integrated Architecture (IA) is the identifying name of Rockwell Automation
group of products that use Rockwell Automation core-enabling technologies.
The PlantPAx® system is a defined set of IA products configured in a prescribed
way to provide optimal performance as a distributed control system.
Internet Group Management A protocol that manages the membership of IP multicast groups.
Protocol (IGMP)
linear topology End user devices are daisy-chained together; limited number of nodes
are supported.
Network Address Translation (NAT) A service that translates one IP address to another IP address via a
NAT-configured switch. NAT makes it possible for devices that share a single
IP address on a private subnet to be segmented into multiple identical private
subnets while maintaining unique identities on the public subnet.
old computer name The term ‘old computer name’ is used to refer to the computer name of the
virtual machine prior to your changes. This could be the factory default
computer name of the virtual machines or a computer name set by your
organization. Once the computer name is changed, the previous computer
name becomes the old computer name.
operator workstation (OWS) The operator workstation (OWS) provides the graphical view and interface
into the process. The workstation is a client of either a PASS or AppServ-HMI.
PlantPAx Distributed Control The PlantPAx system has all the core capabilities expected in a world-class
System distributed control system (DCS). The system is built on a standards-based
architecture by using Integrated Architecture® components that enable
Process Automation System Server The Process Automation System Server (PASS) is the core PlantPAx system
(PASS) server allowing central administration throughout the PlantPAx system. The
PASS is a required component.
server Software component that serves data to an application (for example, data
server). Typically, server software components are installed on server-class
computers.
star topology End user devices are connected to each other via a switch.
subnet mask Determines which of the 32 bits of the IP address are part of the network ID
and which are part of the unique node identification.
Supervisory Control and Data A control strategy to remotely collect and control devices in a distributed
Acquisition (SCADA) system.
system infrastructure System infrastructure is the commercial off-the-shelf hardware and software
required to enable system elements to work together as a system. For example,
network switches, computers, and so forth.
system server A system server expands the scope of a system by providing support for
additional system capacity or optional system functions. For example, the
Process Automation System Server (PASS) is a required component for all
centralized and distributed process systems. The PASS provides central name
resolution and system-wide, FactoryTalk services. The PASS provides the
capability to distribute information to the OWS and add to optional
application servers to increase the scope of the process system.
User -defined Data Type (UDT) Tag types that you create once and reuse in multiple tag templates, multiple
times.
virtual LAN (VLAN) A display object is a functional group of display elements with animations.
Notes:
A output structure 35
remote bit control value structure 35
ABB EMAX2 with EtherNet/IP 145 faceplates 45
controller code 146 engineering tab 47
adding a device 147 help tab 48
InOut structure 146 operator tab 46
input structure 146 mapping InOut tags to add-on instructions
faceplates 36
diagnostic tab 158 using visualization files 40
engineering tab 157 visualization file 40
help tab 159 link to a display 43
operator tab 156 Bulletin 865 49
using visualization files 150 controller code 50
ABB EMAX2 with IEC 61850 161 output structure 51
controller code 162 remote bit control value structure 51
Add-On Instructions 163 faceplates 61
InOut structure 162 diagnostic tab 63
remote command structure 163 engineering tab 63
faceplates 172 help tab 64
diagnostic tab 175 operator tab 62
engineering tab 174 mapping InOut tags to add-on-instructions
help tab 176 52
operator tab 173 using visualization files 56
using visualization files 167 visualization file 56
additional resources 8
Add-On Instruction
definition 177 C
address conflict detection characterization
definition 177 definition 178
address resolution protocol CIP
definition 177 connection
ADR definition 178
definition 178 definition 178
alarm sync
definition 177 definition 178
event client
definition 177 definition 178
management common industrial protocol
definition 177 definition 178
object connected enterprise 9
definition 177 control
priority
definition 177 strategy
definition 178
system
controller
definition 177
application files 11
controller files 11
server
definition 177 Converged Plant-wide Ethernet
application objects definition 179
definition 177 CPwE
AppServ definition 179
definition 177 critical
architecture system attribute
definition 177 definition 179
automatic device configuration
definition 178 D
datastore
B definition 179
Bulletin 857 DCS
controller code 34 definition 179
InOut structure 34, 50
F L
FactoryTalk linear topology
directory software definition 181
definition 180
services platform
definition 180 N
files
NAT
controller 11
flowchart definition 181
Network Address Translation
definition 180
full-duplex mode definition 181
definition 180
function block diagram O
definition 180
old computer name
definition 181
G OPC
gateway definition 181
definition 180
S T
SEL700G 65 TCP/IP
faceplates definition 183
auto-sync tab 81
diagnostic tab 85
engineering tab 82 U
help tab 88
operator tab 80 UDT
x-side diagnostic tab 86 definition 183
y-side diagnostic tab 87 user-defined tag
mapping InOut tags to add-on instructions definition 183
92
using visualization files 73
SEL710 89 V
controller code 90 virtual LAN
output structure 91 definition 183
remote bit 91 virtual machine
faceplates 102
diagnostic tab 106 definition 183
engineering tab 104 visualization files 11
help tab 107 display files 12
operator tab 103 global object files 11
using visualization files 97 HMI tags 12
SEL751A 109 VLAN
controller code 110 definition 183
InOut structure for SEL751A from Li- VM
brary Download 111 definition 183
InOut structure for SEL751A from Pro-
Soft Gateway 66, 90, 110, 128
remote bit 111 W
faceplates 121 workstation
diagnostic tab 124
engineering tab 123 definition 183
help tab 125
operator tab 122
using visualization files 116
link to display 119
SEL787 127
controller code 128
remote bit 129
faceplates 140
diagnostic tab 47, 143
engineering tab 142
help tab 144
Notes:
Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, User https://rockwellautomation.custhelp.com/
Forums, and Product Notification Updates.
Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page
Find the Direct Dial Code for your product. Use the code to
Direct Dial Codes route your call directly to a technical support engineer. http://www.rockwellautomation.com/global/support/direct-dial.page
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf.
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.
Allen-Bradley, ControlLogix, FactoryTalk, FactorTalk View SE, FactoryTalk View Studio, PlantPAx, Rockwell Software, Rockwell Automation, and Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400