f650man-a5
f650man-a5
Instruction Manual
Firmware version: 9.1x
EnerVista F650 Setup version: 9.1x
GE publication code: 1601-0800-A5
LISTED
*1601-0800-A5*
© 2025 GE VERNOVA Multilin. All rights reserved.
GE VERNOVA Multilin F650 Digital Bay Controller instruction manual for revision 1601-
0800-A5.
F650 Digital Bay Controller, EnerVista, and EnerVista 650 family Setup are registered
trademarks of GE VERNOVA Multilin.
The contents of this manual are the property of GE VERNOVA Multilin.
This documentation is furnished on license and may not be reproduced in whole or in part
without the permission of GE VERNOVA Multilin.
Disclaimer
It is the responsibility of the user to verify and validate the suitability of all GE
VERNOVA Grid Automation products. This equipment must be used within its design
limits. The proper application including the configuration and setting of this product to
suit the power system assets is the responsibility of the user, who is also required to
ensure that all local or regional safety guidelines are adhered to. Incorrect application
of this product could risk damage to property/the environment, personal injuries or
fatalities and shall be the sole responsibility of the person/entity applying and
qualifying the product for use.
The content of this document has been developed to provide guidance to properly
install, configure and maintain this product for its intended applications. This guidance
is not intended to cover every possible contingency that may arise during
commissioning, operation, service, or maintenance activities. Should you encounter
any circumstances not clearly addressed in this document, please contact your local
GE service site.
The information contained in this document is subject to change without notice.
Table of Contents
8 SECURITY 8.1 Security level for firmware versions prior to 9.00.......................... 8-1
8.1.1 Adding users............................................................................................................................. 8-1
8.1.2 Changing passwords............................................................................................................ 8-2
8.1.3 Enabling security .................................................................................................................... 8-2
8.1.4 Logging into EnerVista 650 Setup .................................................................................. 8-3
8.2 Security level for firmware versions 9.00 and higher ................... 8-4
8.2.1 Cybersecurity Overview ...................................................................................................... 8-4
8.2.2 Settings ....................................................................................................................................... 8-5
8.2.4 Authentication Methods ..................................................................................................8-15
8.2.5 Secure communication ....................................................................................................8-17
8.2.6 Other Features......................................................................................................................8-19
8.2.7 Product Hardening .............................................................................................................8-22
8.2.8 Security Logging - Syslog ................................................................................................8-25
8.2.9 LOST PASSWORD ..................................................................................................................8-26
GETTING STARTED
Indicates a hazardous situation which, if not avoided, will result in death or serious injury.
DANGER
Indicates a hazardous situation which, if not avoided, could result in death or serious injury.
WARNING
Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.
CAUTION
Indicates practices not related to personal injury.
NOTICE
Ensure that all connections to the product are correct so as to avoid accidental risk of shock
WARNING and/or fire, for example such as can arise from high voltage connected to low voltage terminals.
Follow the requirements of this manual, including adequate wiring size and type, terminal torque settings,
voltage, current magnitudes applied, and adequate isolation/clearance in external wiring from high to low
voltage circuits.
Use the device only for its intended purpose and application.
Ensure that all ground paths are uncompromised for safety purposes during device operation and service.
Ensure that the control power applied to the device, the AC current, and voltage input match the ratings
specified on the relay nameplate. Do not apply current or voltage in excess of the specified limits.
Only qualified personnel are to operate the device. Such personnel must be thoroughly familiar with all
safety cautions and warnings in this manual and with applicable country, regional, utility, and plant safety
regulations.
Hazardous voltages can exist in the power supply and at the device connection to current transformers,
voltage transformers, control, and test circuit terminals. Make sure all sources of such voltages are isolated
prior to attempting work on the device.
Hazardous voltages can exist when opening the secondary circuits of live current transformers. Make sure
that current transformer secondary circuits are shorted out before making or removing any connection to
the current transformer (CT) input terminals of the device.
For tests with secondary test equipment, ensure that no other sources of voltages or currents are
connected to such equipment and that trip and close commands to the circuit breakers or other switching
apparatus are isolated, unless this is required by the test procedure and is specified by appropriate utility/
plant procedure.
When the device is used to control primary equipment, such as circuit breakers, isolators, and other
switching apparatus, all control circuits from the device to the primary equipment must be isolated while
personnel are working on or around this primary equipment to prevent any inadvertent command from this
device.
Uses an external disconnect to isolate the mains voltage supply.
LED transmitters are classified as IEC 60825-1 Accessible Emission Limit (AEL) Class 1M. Class 1M
WARNING devices are considered safe to the unaided eye. Do not view directly with optical instruments.
This product is rated to Class A emissions levels and is to be used in Utility, Substation
NOTICE Industrial environments. Not to be used near electronic devices rated for Class B levels.
The modular design of the relay allows for the withdrawal and insertion of the communication module.
Figure 1-2: Module withdrawal/insertion shows the location of communication modules on the rear part of the relay.
Qualified personnel must carry out the insertion or extraction of the communication boards only after disconnecting
the relay auxiliary voltage and ensuring that all the rear terminals are potential free.
Communication boards are installed on the rear of the unit, with upper port reserved for the asynchronous
communications board and CAN bus, and the lower port for the ETHERNET board. (The Ethernet module can be
withdrawn or inserted only in models with Rear Ethernet Communication Board 2: "B", "C", "D" or "E". For the
remaining options, Ethernet communications are included in the main CPU).
Before performing any of these actions, control power must be removed from the relay and all the rear terminals
must be potential free. A grounded anti static wristband must be used when manipulating the module in order to
avoid electrostatic discharges that may cause damage to the electronic components.
WITHDRAWAL: Loosen the small screws that keep the faceplate in place and extract the module.
INSERTION: Insert the module and press it firmly in the case, until it is completely fixed. After this, bolt the
faceplate screws and replace the control power. Check that the relay is fully operative.
GE VERNOVA Multilin will not be responsible for any damage to the relay, connected equipment or
personnel whenever these safety rules are not followed.
GE VERNOVA Multilin will not be responsible for any damage of the relay, connected equipment or
personnel whenever these safety rules are not followed.
Please ensure that you received the following items with your relay:
• Mounting screws for fixing the relay to a cabinet
• GE EnerVista™ DVD (includes the EnerVista 650 Setup software and manuals in PDF format)
• Wiring diagram.
• Certificate of Compliance
For product information, instruction manual updates, and the latest software updates, please visit the GE VERNOVA
Multilin Home Page: https://www.gevernova.com/grid-solutions/multilin
Note: If there is any physical damage detected on the relay, or any of the contents listed are missing, please
contact GE VERNOVA Grid Solutions immediately:
The information provided herein is not intended to cover all the details of the variations
CAUTION of the equipment, nor does it take into account the circumstances that may be present in
your installation, operating or maintenance activities.
Should you wish to receive additional information, or for any particular problem that cannot be solved by referring to
the information contained herein, please contact GE VERNOVA, Grid Solutions.
Before communicating with the F650 through the front USB port, ensure that the computer's power supply is
grounded. When using a laptop, it is recommended that the power supply be disconnected. In many cases the laptop
may not be correctly grounded either due to the power supply or to the connector cables used.
GE VERNOVA Multilin will not be responsible for any damage to the relay or connected equipment when
this basic safety rule is not followed.
CAUTION
• Failure to practice safe working procedures is likely to damage the equipment, cause severe injury and/
or death.
• The use of appropriate safety gloves, safety glasses and protective clothing are recommended during
equipment installation, maintenance and service of the equipment.
• All procedures must be strictly adhered to.
• Failure to observe and follow the instructions provided in the equipment manual(s) could cause
irreversible damage to the equipment and could lead to property damage, personal injury and/or death.
• Before attempting to use the equipment, it is important that all danger and caution indicators are
reviewed.
• If the equipment is used in a manner not specified by the manufacturer or functions abnormally, proceed
with caution. Otherwise, the protection provided by the equipment may be impaired and can result in
Impaired operation and injury.
• Beware of potential hazards, wear personal protective equipment and carefully inspect the work area for
tools and objects that may have been left inside the equipment.
• Caution: Hazardous voltages can cause shock, burns or death.
• Test/Installation/Service personnel must be familiar with general device test practices, safety
precautions and follow standard ESD precautions to avoid personal injury or equipment damage.
• Before performing visual inspections, tests, or periodic maintenance on this device or associated
circuits, isolate or disconnect all hazardous live circuits and sources of electric power.
• Failure to shut equipment power off prior to removing the power connections could expose you to
dangerous voltages causing injury or death.
• All recommended equipment that should be grounded must have a reliable and uncompromised
grounding path for safety purposes, protection against electromagnetic interference and proper device
operation.
• Equipment grounds should be bonded together and connected to the facility's main ground system for
primary power.
• Keep all ground leads as short as possible.
• At all times, equipment ground terminal must be grounded during device operation.
• While the equipment manual may suggest several safety and reliability steps, safety precautions must
be used in conjunction with the safety codes in force at your location.
• LED transmitters are classified as IEC 60825-1 Accessible Emission Limit (AEL) Class 1M. Class 1M
devices are considered safe to the unaided eye. Do not view directly with optical instruments.
• It is the responsibility of the user to check the equipment ratings and installation instructions prior to
commissioning, service.
• Use a lift system with side rails/bucket to reduce a fall hazard as opposed to other means when
installing or servicing.
• In addition to the safety precautions mentioned all electrical connections made must respect the
applicable local jurisdiction electrical code.
• Before working on CTs, they must be short circuited.
• Do not remove the voltage terminal blocks or disconnect the voltage input wires when the voltage
phases are live. The voltage inputs must be de-energized prior to any servicing.
!
instructions. Failure to take or avoid a specified action can result in loss of data or
physical damage.
AVERTISSEMENT: Se réferer à la documentation pour l'entretien et l'utilisation.
L'absence ou èviter de prender des mesures spècifiques peut entraîner des pertes
de données ou même causer des dommages physiques.
WARNING! Dangerous voltage constituting a risk of electric shock is present
within the unit. Failure to take or avoid a specified action can result in physical
harm to the user.
AVERTISSEMENT! Tensions dangereuses comportant un risque de choc électrique
sont presents dans l'equipement. L'absence ou èviter de prender des mesures
spècifiques peut causer des dommages physiques à l'utilisateur.
CAUTION: Class 1M Laser (IEC 60825-1 Safety of laser products)
DO NOT VIEW DIRECTLY WITH OPTICAL INSTRUMENTS.
AVERTISSEMENT: Laser de classe 1M (IEC60825-1) ÉVITER DE REGARDER
DIRECTEMENT LE DISPOSITIF QUI ÉMET LE LASER OPTIQUE.
CAUTION: Hot surface.
AVERTISSEMENT: Surface chaude.
Note: Read all instructions included in package before using your product. Additional safety information
Product Safety Supplement document available at : https://www.gevernova.com/grid-solutions/productsafety/
1.2 Overview
The other module provides Ethernet communications (ETH Port), using 10/100BaseTX (self-negotiable speed) or
100BaseFX connectors, depending on the selected model. The most complete models include a double redundant
100BaseFX fiber optic port. Redundancy is provided at the physical level, for options D and E; the unit incorporates
internally duplicated and independent controllers for extended system reliability and accessibility.
For options C and D you must select the active physical media, by means of an internal selector inside the module.
The factory configuration for this selection is the 10/100BaseTX port. For firmware versions 7.00 and above, the
following options are available:
Finally, internal communication with input and output modules is performed via an internal CAN Bus, independent of
the one used for remote CAN Bus I/Os. This provides increased communication speed, and acknowledgment of
modules, abnormalities, etc. As this is a serial port supporting a communications protocol, it provides immunity
against external or internal disturbances.
ETHERNET COMMUNICATIONS
CAN
REMOTE
ETH1 Redundancy I/O
(Optional)
SERIAL
MAIN PROCESSOR COM 1
DIGITAL SUPERVISION
ETH2 ETH3
COMMUNICATION
CONTROL I/O I/O
PROTECTION
CAN I/O
INTERNAL
SERIAL MULTIPLEXED
SERIAL COM 2
DSP COM H
MEASUREMENT
PROCESSOR
ANALOG
SERIAL
INPUTS COM2
COM H
CURENT AC
AND FRONT
VOLTAGE AC HMI HUMAN MACHINE INTERFACE SERIAL
PORT
1.3.2 Installation
After ensuring the minimum requirements for using EnerVista 650 Setup are met (see previous section), obtain the
software from the GE EnerVista DVD, or download from: https://www.gevernova.com/grid-solutions/multilin/ as
follows:
1. Insert the GE EnerVista DVD into the DVD drive of your computer.
2. Click Install Now and follow the installation instructions to install the complimentary EnerVista software.
3. When installation is complete, start the EnerVista Launchpad application.
4. Click IED Setup in the Launch Pad window.
5. Click Add Product and select the “F650 Bay Controller” relay from the Install Software window as shown below. Select
the “Web” option to ensure the most recent software release, or select “CD” if you do not have a web connection, then
click Add Now to list software items for the F650.
6. EnerVista Launchpad obtains the installation program from the Web or CD. Once the download is complete, double-
click the installation program to install the EnerVista 650 Setup software.
7. Follow the on-screen instructions to install the EnerVista 650 Setup software. When the Welcome window appears,
click Next to continue with the installation.
8. When the Choose Destination Location window is displayed, change the installation directory id needed by clicking
Change… and typing in the complete path name including the new directory name. Click Next to continue with the
installation.
9. The default program group containing the application is added to as shown in the Selected Program Folder window.
Click Next to begin the installation process, and all the necessary program files are copied into the selected directory.
10. To complete the installation, select the desired language for startup.
11. Click Finish to end the installation. The F650 device has been added to the list of installed IEDs in the EnerVista
Launchpad window, as shown below.
1.4.4 Maintenance
To avoid deterioration of electrolytic capacitors, power up units that are stored in a de-energized
NOTICE state once per year, for one hour continuously.
1.4.5 Storage
Store the unit indoors in a cool, dry place. If possible, store in the original packaging. Follow the storage temperature
range outlined in the Specifications.
To avoid deterioration of electrolytic capacitors, power up units that are stored in a de-energized
NOTICE state once per year, for one hour continuously.
1.4.6 Repairs
The firmware and software can be upgraded without return of the device to the factory.
For issues not solved by troubleshooting, the process to return the device to the factory for repair is as follows:
• Contact a GE Grid Solutions Technical Support Center. Contact information is found in the first chapter.
• Obtain a Return Materials Authorization (RMA) number from the Technical Support Center.
• Verify that the RMA and Commercial Invoice received have the correct information.
• Tightly pack the unit in a box with bubble wrap, foam material, or Styrofoam inserts or packaging
peanuts to cushion the item(s). You may also use double boxing whereby you place the box in a larger
box that contains at least 5 cm of cushioning material.
• Ship the unit by courier or freight forwarder, along with the Commercial Invoice and RMA, to the factory.
• Fax a copy of the shipping information to the GE Grid Solutions service department. Customers are
responsible for shipping costs to the factory, regardless of whether the unit is under warranty.
Use the detailed return procedure outlined at
https://www.gevernova.com/grid-solutions/multilin/support/ret_proc.htm
The current warranty and return information are outlined at
https://www.gevernova.com/grid-solutions/multilin/warranty.htm
1.4.7 Disposal
The F650 is intended to be part of defective large-scale stationary industrial tools and large-scale fixed installations.
This product cannot be disposed of as unsorted municipal waste in the European Union. For proper recycling return
this product to your supplier or a designated collection point. For more information go to www.recyclethis.info.
PRODUCT DESCRIPTION
Another option provides two 100BaseFX fiber optic ports for redundancy. The Ethernet port supports IEC 61850,
Modbus®/TCP, DNP 3.0 and TFTP protocols, and allows access to the relay via any standard web browser. The IEC
60870-5-104 protocol is supported on the Ethernet port. The Ethernet port also supports the Parallel Redundancy
Protocol (PRP) and High-availability Seamless Redundancy (HSR) of IEC 62439-3 (clause 4 (PRP) and clause 5
(HSR)) for firmware version 7.00 and so on.
Rear port COM1 can be set to support IEC60870-5-103 protocol
The F650 IEDs use flash memory technology which allows field upgrading as new features are added:
User Programmable Keys (up to 5) Fault Locator and Fault report (up to Logic Equations (PLC Editor)
10 records)
Easy menu management Oscillography (up to 20 records) Operations (up to 24)
Configurable One-Line Diagram (Graphic Snapshot Events (up to 1023)** Web Server Application
model only)
Phasor Diagram (available in EnerVista 650
Setup)
** Maximum number of events can vary depend on firmware version. See details in section 2.5.3.3
SPECIAL MODELS MOD001 (Abbreviation "+M1"): have 6A output contacts instead of 16A.
Notes:
(*) For firmware version 7.00 or above, Port E is only intended for maintenance purposes.
(1) Order code option F4 requires option G4 or G5. Order code option F5 requires option G5.
For example: F1G5 is a valid selection and F5G1 is an invalid selection.
(2) Display options with language selection:
Graphic display: available for English, French, Spanish and Chinese languages. For Chinese and Russian only IEC symbols
option is available (N in order code).
Basic display: available for all languages
For applications requiring a high number of inputs and outputs, F650 units can be connected to a CIO module
(Remote CAN bus I/O module) for using up to 2 additional boards.
F650 units allow monitoring and configuring these I/O boards as if they were internal boards, located on slots F and
G. In this case, slots are labeled as H and J.
The required information to completely define a CIO Module is shown on Table 2–2:.
(1) The digit selected for option J must be equal or higher than the digit selected for option H for models including boards 4 and 5.
CIOH1J5**: is a valid selection
CIOH5J1**: is an invalid selection
2.5.1 Protection
Phase and Ground protection functions use currents measured through CT inputs for performing internal
calculations, while the Neutral protection functions use the current calculated from three phase currents.
The sensitive ground protection functions are usually used for applications where the neutral is completely isolated.
These functions use current measured though the sensitive ground current input. This CT has a sensitivity 10 time
higher than standard CT inputs (Connected to 1A and 5A CT) and its current withstand is lower.
UNDERFREQUENCY (81U)
Pickup Level: ...............................................................................20.00 to 65.00 Hz in steps of 0.01 Hz
Dropout Level:............................................................................pickup + 0.03 Hz
Level Accuracy: .........................................................................±0.05 Hz of the reading from 30 to 80 Hz
Trip Delay: ....................................................................................0.00 to 900.00 s in steps of 0.01 s
Reset Delay: ................................................................................0.00 to 900.00 s in steps of 0.01 s
Minimum Voltage Threshold:..............................................10 to 300 V in steps of 1 V
Time Delay Accuracy:.............................................................0 to 7 cycles
Operate Time:.............................................................................typically 10 cycles at 0.1 Hz/s change
Snapshot Events: ......................................................................selectable by setting
OVERFREQUENCY (81O)
Pickup Level: ...............................................................................20.00 to 65.00 Hz in steps of 0.01 Hz
Dropout Level:............................................................................pickup - 0.03 Hz
Level Accuracy: .........................................................................±0.05 Hz of the reading from 30.00 to 80.00 Hz
Trip Delay: ....................................................................................0.00 to 900.00 s in steps of 0.01 s
Reset Delay: ................................................................................0.00 to 900.00 s in steps of 0.01 s
Minimum Voltage Threshold:..............................................10 to 300 V in steps of 1 V
Time Delay Accuracy:.............................................................0 to 7 cycles
Operate Time:.............................................................................typically 10 cycles at 0.1 Hz/s change
Snapshot Events: ......................................................................selectable by setting
2.5.2 Control
AUTORECLOSE (79)
Schemes: ......................................................................................three-pole tripping schemes
Number of Shots:......................................................................up to 4 reclose attempts before lockout
Dead Time:...................................................................................independent dead time setting before each shot
adjustable between 0.00 and 900.00 s in steps of 0.01 s.
Reclaim Time: .............................................................................0.00 and 900.00 s in steps of 0.01 s
Condition Permission:.............................................................selectable by setting
Hold Time: ....................................................................................0.00 and 900.00 s in steps of 0.01 s
Reset Time: ..................................................................................0.00 and 900.00 s in steps of 0.01 s
Snapshot Events: ......................................................................selectable by setting
Protection settings can be modified after each shot through PLC programming (block signals are available after each shot).
SYNCHROCHECK (25)
Dead/live Level for Line and Bus:......................................0.00 to 300.00 in steps of 0.01 V
Maximum Voltage Difference:............................................2.00 to 300.00 V in steps of 0.01 V
Maximum Angle Difference:................................................2.0º to 80.0º in steps of 0.1º
Maximum Frequency Slip:....................................................10 to 5000 mHz in steps of 10 mHz
Synchronism Time: ..................................................................0.01 to 1.00 s in steps of 0.01 s
Angle Accuracy: ........................................................................3º
Dead Source Function: ..........................................................None
(DL-DB) Dead Line - Dead Bus
(LL-DB) Live Line-Dead Bus
(DL-LB) Dead Line – Live Bus
Snapshot Events: ......................................................................selectable by setting
FUSE FAILURE
Algorithm based on positive sequence of voltage and current
Activation by V2/V1 ratio
PULSE COUNTERS
Number of Pulse Counters Available:............................. up to 8
Multiplier Factor: ...................................................................... 0.000 to 65000.000 in steps of 0.001
Overload Factor:....................................................................... 0 to 10000000 in steps of 1
Board Origin: .............................................................................. all available input/output boards in the device. See order code (F, G, H, J)
Input Origin:................................................................................ up to 32 (depending on board selection type)
ANALOG COMPARATORS
Analog Input: ..............................................................................any analog value in the device
Analog Maximum Threshold Value:.................................-100000.000 to 100000.000 in steps of 0.001
Analog Minimum Threshold Value: ..................................-100000.000 to 100000.000 in steps of 0.001
Analog Delay: .............................................................................0.00 to 900.00 in steps of 0.01
Analog Hysteresis: ...................................................................0.0 to 50.0 in steps of 0.1
Analog Direction (for activation inside or outside the
deadband: .............................................................................. IN or OUT
LOAD ENCROACHMENT
Responds to: ...............................................................................positive sequence quantities
Minimum Voltage: ....................................................................0.00 to 300.00 V in steps of 0.01 V
Reach (sec.Ω): ...........................................................................0.02 to 250.00 Ω in steps of 0.01 Ω
Impedance Accuracy: ............................................................±3%
Angle: .............................................................................................5 to 50º in steps of 1º
Angle Accuracy: ........................................................................±3%
Pickup Delay: ..............................................................................0.000 to 65.535 s in steps of 0.001
Reset Delay: ................................................................................0.000 to 65.535 s in steps of 0.001
Time Accuracy: ..........................................................................±3.5% or ±60 ms, whichever is greater
Operate Time:.............................................................................< 60 ms at 50 Hz, typically
Snapshot Events: ......................................................................selectable by setting
BREAKER SETTINGS
Number of Switchgear:..........................................................1 to 16 (selection of switchgear for breaker control)
Maximum KI2t: ...........................................................................0.00 to 9999.99 (kA)2s in steps of 0.01 (kA)2s
KI2t Integration Time: .............................................................0.03 to 0.25 s in steps of 0.01
Maximum Openings:...............................................................0 to 9999 in steps of 1
Maximum Openings in One Hour: ....................................1 to 60 in steps of 1
Snapshot Events: ......................................................................selectable by setting
BREAKER MAINTENANCE
KI2t Breaker Counters for Phases A, B, C:......................0.00 to 9999.99 (kA)2s in steps of 0.01 (kA)2s
Breaker Opening Counters: .................................................0 to 9999 in steps of 1
Breaker Closing Counters:....................................................0 to 9999 in steps of 1
SWITCHGEAR
Switchgear: .................................................................................1 to 16 (configurable in Relay Configuration)
Snapshot Events: ......................................................................selectable by setting (for each switchgear, in System Setup)
DIGITAL COUNTERS
Function: ...................................................................................... Disabled, Enabled
Name:............................................................................................ any 12 alphanumeric characters
Preset: ........................................................................................... -2147483648, 0, +2147483647
Compare: ..................................................................................... -2147483648, 0, +2147483647
2.5.3 Monitoring
OSCILLOGRAPHY
Maximum Records: ................................................................. up to 20 oscillography records
Sampling Rate:.......................................................................... programmable to 4, 8, 16, 32, or 64 samples per power cycle
Capacity per record:............................................................... (27592 samples)/(number of oscillos x number of samples/cycle)
Maximum Records: ................................................................. up to 20 oscillography records
Trigger Position:........................................................................ 5% to 95% of total length
Trigger:.......................................................................................... programmable via PLC
Data: .............................................................................................. 5 current channels and 4 voltage channels up to 16 digital channels programmable
through PLC
Data Storage:............................................................................. non-volatile (flash) memory without battery
Format: ......................................................................................... International Standard COMTRADE ASCII - IEEE C37.111-1999
Automatic Overwrite:............................................................. selectable by setting (oscillography records can be concatenated)
Snapshot Events: ..................................................................... selectable by setting
FAULT LOCATOR
Method: ........................................................................................ single-ended
Positive Sequence Module: ................................................. 0.01 to 250.00 Ohm in steps of 0.01 Ohms
Positive Sequence Angle: ..................................................... 25 to 90º in steps of 1º
Zero Sequence Module: ........................................................ 0.01 to 750.00 Ω in steps of 0.01 Ω
Zero Sequence Angle:............................................................ 25 to 90º in steps of 1º
Line Length: ................................................................................ 0.0 to 2000.0 in steps of 0.1 miles or km (as per line length setting)
Accuracy:..................................................................................... 5% (typically)
Show Fault on HMI:................................................................. selectable by setting
Snapshot Events: ..................................................................... selectable by setting
Maximum Records: ................................................................. up to 10 fault report records
Data: .............................................................................................. Fault date and time, pre-fault currents and voltages, fault currents and voltages, fault
type, distance to the fault (fault location), line parameters, recloser and breaker status
information.
Data Storage:............................................................................. In non-volatile (flash) memory without battery available through communications In
volatile (RAM) memory available through HMI (if selectable by setting)
Format: ......................................................................................... text in ASCII format
SNAPSHOT EVENTS
Capacity*:.....................................................................................1023 scrolling events
Time-tag: ......................................................................................1 ms using an internal clock of 100 μs
Timing Accuracy: ......................................................................1 ms (using IRIG-B synchronization)
Triggers: ........................................................................................any element pickup, dropout, or operation
digital input/output change of state
virtual inputs and control events
Data Storage: .............................................................................non-volatile (flash) memory without battery
*Note: For firmware 7.20, up to 511 snapshot events are available. For firmware below 7.20, up to 479 snapshot events are available.
CONTROL EVENTS
Capacity:.......................................................................................128 events programmable through PLC
Time-tag: ......................................................................................1 ms plus one PLC cycle using an internal clock of 100 μs. For digital inputs,
the debounce time of these digital inputs must be added.
Timing Accuracy: ......................................................................1 ms (with IRIG-B synchronization input)
Trigger: ..........................................................................................Any digital signal programmable through the PLC
Alarm:.............................................................................................Control events can be displayed as an alarm on the alarms panel. Information is
always available through Communications for all models and in the HMI for models
with a graphical display (M in order code).
Data Storage: .............................................................................non-volatile (flash) memory without battery
Control events are also displayed in the snapshot events recording
DEMAND
Channels:......................................................................................9
Parameters:.................................................................................Ia (kA RMS), Ib (kA RMS), Ic (kA RMS), Ig (kA RMS), Isg (kA RMS), I2 (kA), P (MW), Q (MVAr)
and S (MVA)
Current and Power Method:................................................Thermal Exponential, Block Interval, Rolling Demand
Measurements:..........................................................................Each channel shows the present and maximum measured value, with date and time
for the maximum recorded value.
Samples: .......................................................................................5, 10, 15, 20, 30, 60 minutes
Accuracy:......................................................................................±2%
Trigger Input: ..............................................................................selectable by setting (operation mode selection for the block interval calculation
method)
Snapshot Events: ......................................................................selectable by setting
DATA LOGGER
Number of Channels:..............................................................1 to 16
Parameters:.................................................................................any available analog actual value
Samples: .......................................................................................1 second, 1, 5, 10, 15, 20, 30, 60 minutes
Storage Capacity:.....................................................................fixed, 32768 measurements
2.5.4 User-programmable
PLC LOGIC
Programming language: ...................................................... The logical configuration is performed using graphical functions based on the IEC
61131-3 standard.
Lines of code*:........................................................................... 640 lines of code or 15360 bytes, whichever is greater (for versions < 7.00)
1000 total equations or 15360 bytes, whichever is greater (for versions >= 7.00)
(*) Note: Reserved Modbus memory space of PLC equations in text format is up to 15360 bytes. This space is shared with
information configured in EnerVista at Setpoint > Relay Configuration. According to this, the number of PLC equations can be
limited by values configured on that section.
Supported operations:........................................................... NOT, XOR, OR (2 to 8 inputs), AND (2 to 8 inputs), NOR (2 to 8 inputs),
NAND (2 to 8 inputs), Latch (Reset Dominant), Edge Detectors, Timers.
2 inputs default gates, from 3 to 8 inputs provided in library format.
Starting in version 7.20, analog operators are also available.
Libraries:....................................................................................... Logical gates fully programmable by user. Used to create user-programmable logic to
be distributed as a single object.
Inputs: ........................................................................................... any logical variable, contact or virtual input
Number of Timers:................................................................... 8 maximum in each logic scheme (provided in library format)
FLEXCURVES
Number: ....................................................................................... 4 (A through D)
Reset Points:............................................................................... 40 (0 through 1 of pickup)
Operate Point: ........................................................................... 80 (0 through 20 of pickup)
Time Delay: ................................................................................. 0 to 65535 ms in steps of 1 ms
Saturation Level: ...................................................................... 20 x the pickup level
USER-PROGRAMMABLE LEDS
Number: ....................................................................................... 15 configurable LEDs plus the Ready non-configurable LED
Programmability: ..................................................................... any logical variable, contact, or virtual input
Reset Mode:................................................................................ self-reset or latched.
The first 5 LEDs (red) are latched by hardware, usually configured for trip signals.
The following 10 LEDs (yellow and green) are self-reset but can be latched through PLC
configuration.
Reset Signal:............................................................................... The LEDs can be reset by hardware, pressing the front “esc” key for more than 3
seconds or using the LED reset signal through PLC configuration.
USER-DEFINABLE DISPLAYS
Number of Configurable Displays:................................... 1: one line diagram fully configurable. In graphical displays only
Number of Fixed Displays:................................................... 6: Metering (selectable between Primary and Secondary values), Snapshot Events (all
and new), Alarms, Inputs and Outputs screen with test functionality for inputs and
outputs. (In graphical displays only.)
Number of Selectable Displays:........................................ 2: Logotype, Metering, or both in scrolling mode can be selected as the default screen
in text display for all models (basic and mimic). The metering screen contains current
and voltages for phases and ground in primary or secondary values.
2.5.5 Metering
CURRENT
Accuracy (at nominal frequency):.....................................±0.5% of the reading ± 10 mA from 0.05 to 10.00 A (for phases and ground)
±1.5% of the reading ± 1 mA from 0.005 to 5 A (for sensitive ground)
±1.5% of the reading for higher values
% of Load-to-trip Accuracy:................................................±0.5% of full-scale
VOLTAGE
Accuracy:......................................................................................±1% of reading from 10 to 208 V
FREQUENCY
Accuracy:......................................................................................+/- 0.03Hz
From 30 to 80 Hz
Note: Voltage input must be above 10 V to start measuring frequency
ANGLE
Accuracy:......................................................................................±3º
2.5.6 Inputs
AC CURRENT INPUTS
CT Ratio:........................................................................................1.0 to 6000.0 in steps of 0.1
Rated Currents:..........................................................................Appropriate for 1 or 5 A. F650 has universal range for CT (valid for 1 or 5 A to only one
terminal).
Relay Burden: .............................................................................< 8 mVA at 1 A
< 200 mVA at 5 A VA
Input Impedance: .....................................................................< 8 mOhm
Current Withstand: ..................................................................Continuous at 20 A
1 s at 500 A for phases and ground
1 s at 50 A for sensitive ground
AC VOLTAGE INPUTS
VT Ratio: ....................................................................................... 1.0 to 6000.0 in steps of 0.1
Rated Voltage:........................................................................... 275 Vac
Metering Range: ....................................................................... From 2 to 275 Vac
Relay Burden:............................................................................. 0.05 VA at 120 Vac (50 or 60 Hz)
Voltage Withstand: ................................................................. Continuous at 275 V to neutral
1 min/hr at 420 to neutral
VAC inputs do not need varistors, as the impulse test is applied to 100% of the transformers
CONTACT INPUTS
Input Activation Threshold: ................................................. 10 to 230 Vdc in steps of 1 V (selectable by setting)
Impedance:................................................................................. > 100 kΩ
Maximum Error:........................................................................ ±10% setting or ± 5 V
Load for Voltage Supervision Inputs: ............................. 2 mA + V/100 kΩ
Voltage Threshold for Voltage Supervision Inputs:.. < 10 V (fixed)
Debounce Time:........................................................................ 1 to 50 ms in steps of 1 ms
Recognition Time: .................................................................... 2 ms (typical)
Timing Resolution: ................................................................... 1 ms
For Activation Voltage Threshold and Debounce Time there is a single setting for all inputs in the same group (all inputs sharing
the same common).
Input Type and Delay Input Time are not grouped; there is a different setting for each input.
Input Type: .................................................................................. positive-edge/negative-edge/positive/negative
Delay Input Time: ..................................................................... 0 to 60000 ms in steps of 1 ms (input signal time delay)
ANALOG INPUTS
Input Impedance: .................................................................... 116Ω
Current Input (mADC):............................................................ 0 to -1; 0 to +1; -1 to +1; 0 to 5; 0 to 10; 0 to 20; 4 to 20 (programmable)
Conversion Range: .................................................................. -1 to +20 mA
Accuracy:..................................................................................... ±0.2% of full scale
Type:............................................................................................... passive
IRIG-B INPUT
Amplitude Modulation:.......................................................... DC SHIFT = demodulated input (no carrier)
Input Voltage: ............................................................................ TTL
Input Burden: ............................................................................. 1.5 mA
Input Impedance: .................................................................... 3.3 kΩ
Minimum Input Voltage: ....................................................... 2.4 V
Maximum Input Voltage:...................................................... ± 24 V
Formats: ....................................................................................... B000 (*) B001, B002 and B003 (*
(*) Signal combinations recognized in accordance with IRIG Standard 200-95
Isolation:....................................................................................... 2 kV
2.5.8 Outputs
OUTPUTS
Single Contact Carry continuous: .....................................16 A
Make and Carry for 1 s: .........................................................60 A
Break at L/R of 40 ms:............................................................0.3 A DC max. at 125 Vdc
0.25 A DC max. at 250 Vdc
Operate Time:.............................................................................< 8 ms
Contact Material: ......................................................................silver alloy
Output Logic Type, Output Type and Pulse Output Time are selectable by setting for each output
Output Logic Type:...................................................................positive/negative
Output Type: ...............................................................................normal/pulse/latch (selectable by setting for each output)
Pulse Output Time:...................................................................0 to 60000 ms in steps of 1 ms (applicable only to signals sent as pulse type)
Separate operate and reset signals can be configured by any digital signal programmable through the PLC
Contact Outputs (F31-F33, F34-F36) for board type
2 (supervision) in slot F:.....................................................The current seal-in circuit is used for verifying the current condition in a circuit during
the time that the tripping contact remains closed. If the current in the tripping circuit is
maintained over 500 mA, the function is sealed independently of the status of the
function that caused the trip.
2.5.10 Communications
FRONT PORT:
Front port: COM2
Type: RS232/USB
Baud Rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600 and 115200 baud
Default Baud Rate: 19200 baud
Protocols: ModBus® RTU/DNP 3.0
Typical Distance: 3m
Isolation: 2 kV
ASYNCHRONOUS REAR PORTS:
None or two rear ports (depending on model): COM1, COM2 (rear COM2 multiplexed with front port)
Type (depending on model):
Model F None
Model A Redundant RS485
Model X Redundant RS485 + fiber CAN for inputs/outputs module
Model P Redundant 1mm-plastic F.O.
Model Y Redundant 1mm-plastic F.O. + fiber CAN for inputs/outputs module
Model G Redundant multimode glass F.O.
Model Z Redundant multimode glass F.O. + fiber CAN for inputs/outputs module
Model C Cable CAN port for I/O module
Model M Cable CAN port for I/O module (cable) + RS485 (ModBus RTU)
Optic Features for ST Connector Devices: Wave length: 1300nm
Fiber type: multimode 62.5/125 μm or 50/125 μm
Baud Rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600 and 115200 baud
Default Baud Rate: 19200 baud
Protocols: ModBus® RTU/DNP 3.0/IEC103
Typical Distance: 1200 m for cooper cable, 1000 m for glass fiber and 50 m for plastic fiber
Isolation: 2 kV
CAN PORT:
Rear Port: CAN port in models C, M, X, Y, Z for asynchronous rear ports
Type: Multimode glass F.O. port with ST connectors
Fiber Wavelength: 820 nm
Fiber Type: multimode 62.5/125 μm or 50/125 μm
Maximum Recommended Length: 300 m for cooper cable and glass fiber
Isolation: 2 kV
ETHERNET PORT:
Rear port:
For models B, C, D, E: ETH_1/ ETH_2
For models G, H, J, K, L, M: ETH_E/ ETH_A/ ETH_B
Type (depending on model):
Model B: 10/100BaseTX self-negotiable
Model C: 10/100BaseTX + 100Base FX
Model D: 10/100BaseTX + redundant 100BaseFX (Physical media redundancy)
Model E: Redundant 10/100BaseTX self-negotiable ports
Model G: 1588, 10/100 Base TX* + 100 Base TX
Model H: 1588, 10/100 Base TX* + 100 Base FX
Model J: PRP, 1588, 10/100 Base TX* + Redundant 100 Base FX
Model K: PRP, HSR, RSTP, 1588, 10/100 Base TX* + Redundant 100 Base FX
Model L: PRP, 1588, 10/100 Base TX* + Redundant 100 Base TX
Model M: PRP, HSR, RSTP, 1588, 10/100 Base TX* + Redundant 100 Base TX
(*) Note: This Ethernet port (ETH_E) is intended only for maintenance purposes.
2.5.11 Optical
Wave length: 1300 nm
Connector types: ST package style
Fiber type: multimode 62.5/125 μm or 50/125 μm
Transmitter characteristics
Parameter Min. Typ. Max. Unit Reference
Output Optical Power BOL -19 -14 dBm avg. Note 1
62.5/125 μm, NA = 0.275 Fiber EOL -20
Output Optical Power BOL -22.5 -14 dBm avg. Note 1
50/125 μm, NA = 0.275 Fiber EOL -23.5
Output Optical Power at -45 dBm avg. Note 2
Logic “0” State
Receiver characteristics
Parameter Min. Typ. Max. Unit Reference
Input Optical Power -33.9 -31 dBm avg. Note 3
Minimum at Window Edge
Input Optical Power -35.2 -31.8 dBm avg. Note 4
Minimum at Eye Center
Input Optical Power Maximum -14 dBm avg. Note 3
Notes:
1. These optical power values are measured with the following conditions:
The Beginning of Live (BOL) to the End of Life (EOL) optical power degradation is typically 1.5 dB per industry
convention for long wavelength LEDs. The actual degradation observed in Agilent’s 1300nm LED products is <1 dB, as
specified in this data sheet.
Over the specified operating voltage and temperature ranges.
With HALT Line State, (12.5 MHz square-wave), input signal.
At the end of one meter of noted optical fiber with cladding modes removed.
The average power value can be converted to a peak power value by adding 3 dB. Higher output optical power
transmitters are available on special request.
2. The transmitter provides compliance with the need for Transmit_Disable commands from the FDDI SMT layer by
providing an Output Optical Power level of <-45 dBm average in response to a logic “0” input. This specification
applies to either 62.5/125 μm or 50/125 μm fiber cables.
3. This specification is intended to indicate the performance of the receiver section of the transceiver when Input Optical
Power signal characteristics are present per the following definitions. The Input Optical Power dynamic range from the
minimum level (with a window time-width) to the maximum level is the range over which the receiver is guaranteed to
provide output data with a Bit Error Ratio (BER) better than or equal to 2.5e-10.
At the Beginning of Life (BOL).
Over the specified operating temperature and voltage ranges.
4. All conditions for Note 3 apply except that the measurement is made at the center of the symbol with no window
time-width.
2.5.12 Environmental
Operating Temperature: .......................................................- 10°C to + 60°C
Storage Temperature:............................................................- 40°C to + 85°C
Humidity (non-condensing): ................................................95%
Altitude: .........................................................................................up to 2000 m
Class of Equipment:.................................................................I
Equipment Mobility:.................................................................fixed
Overvoltage Category:...........................................................III
Pollution Degree: ......................................................................2
F650 has been designed to comply with the highest existing requirements. More specifically, UNIPEDE
recommendations for high voltage substations are followed, even if for most applications such high classes are not
required.
The relay complies with ANSI C37.90 standards, and has been designed to comply with international standards.
2.5.15 Approvals
EAC
The EAC Technical Regulations (TR) for Machines and Equipment apply to the Customs Union (CU) of the Russian
Federation, Belarus, and Kazakhstan
Item Description
Country of origin Spain
Date of manufacture See label on the F650 unit
Declaration of Conformity and/or Certificate of Conformity Available on request
5('81'$17
32:(5 32:(5
6833/< 6833/<
$ &
%
& $
&20
56 $
$ 9$
%$&.83 %
*1'
92/7$*(,13876
5($'< %$&.835($'<
&$1 &20
$ 9$ 32:(5 32:(5
56 $
$ 9% %
7;
),%(5
$ 9% 5;
7;
&20
$ 9& ),%(5
5;
7;
$ 9& *(0XOWLOLQ
&20
),%(5
5;
% ,$ 7;
)
&$1
),%(5
5;
% ,$
'LJLWDO%D\&RQWUROOHU *1'
&20
% ,% $
56
&855(17,13876
%
% ,%
*1'
&$1
&$%/( &$1/
% ,&
&$1+
% ,&
(7+(51(7 (7+(51(7
873 5-
% ,* 7;
);67
5;
% ,* 873 5-
7;
% ,6* );67
5;
% ,6* (7+(1* 873 5-
,5,*%
$ 9; +
%869
+
$ 9;
56 )5217
23(1'(/7$97&211(&7,21
$ &
%
& $
*5281',1*
% 6&5(:
$ 9$
6/27*
92/7$*(,13876
$ 9$
%2$5'7<3( %2$5'7<3( %2$5'7<3( %2$5'7<3(
$ 9% * && * && * 6+,(/' *
* && 2 * && *
$ 9% *
$,
* && * && * *
86(5&21),*85$%/(,13876
$,
&21),*85$%/(2873876
$,
* && 2 * && * *
* && * && * *
$,
* &20021 2 * &20021 * *
* &20021 * &20021 * *
$,
* && 2 * && * *
* && * && * *
$,
* && 2 * && * *
*5281'$75(/$</2&$7,21 * && * && * *
$,
127&7 37/2&$7,21 * && 2 * && * *
* && * && * *
$,
* && 2 * && * *
237,21$/(/(0(176
* && * && * 6+,(/' *
6/27)
%2$5'7<3( %2$5'7<3( %2$5'7<3( %2$5'7<3( %2$5'7<3( %2$5'7<3(
) && ) &2,/ ) 2 ) && ) 6+,(/' )
9
&2,/
$,
&21),*85$%/(2873876
&21),*85$%/(2873876
2
) && ) && ) ) && ) )
$1$/2*,13876
$,
) && ) && 2 ) 2 ) && ) )
) && ) && ) ) && ) )
$,
) &20021 ) &20021 2 ) 2 ) &20021 ) )
) &20021 ) &20021 ) ) &20021 ) )
$,
) && ) && 2 ) 2 ) && ) )
) && ) && ) ) && ) )
$,
) && ) && 2 ) ,6(16 ) && ) )
) && ) && ) ) && ) )
2 $,
) && ) &2,/ 2 ) ) && ) )
9
&2,/
) && ) D ) ,6(16 ) && ) )
$,
) && ) &2,/ 2 ) ) && ) )
9 2
) && ) E ) ) && ) 6+,(/' )
F2 - 52/a F20
F3 + COIL 1 F21
52/b SUPERVISION O2 27/59 PICKUP
V
52/a SUPERVISION
COIL 2
Chapter 3: Hardware
HARDWARE
SCREEN
Keypad
LEDs
RS
RS232 Local/
23
322
2 Remote
USB
Control power supplied to the relay must be connected to the matching power supply
NOTICE range of the relay. If the voltage is applied to the wrong terminals, damage can occur.
The F650 relay contains electrolytic capacitors. These capacitors are well known to be
NOTICE subject to deterioration over time if voltage is not applied periodically. Deterioration can
be avoided by powering the relays up once a year.
In the case of a redundant power supply the two modules work in parallel continuously, distributing 50% of the load
on each, thus ensuring greater reliability and an instantaneous load transfer from a failed power supply to the
backup, without loss of time or module reset.
A contact relay connected to the low voltage side of the power supply monitors this voltage. The three contact
terminals, normally open, common, and normally closed, are available at the external connector terminals. The
contact monitors the power supply integrity and it is not controlled by the main microprocessor. In order to monitor
whether the unit is ready to protect (READY), an auxiliary output contacts in the unit should be programmed. This
“fly-back” type power supply provides high efficiency, stability and reliability and is available in two ranges, Hi and
Low, in order to optimize efficiency and general performance, including the capability to tolerate auxiliary voltage
interruptions (dips).
Oversized components highly resistant to temperature are used. For example, all capacitors are specified to stand
up to 105ºC, transformer components are specially designed to stand up to 180ºC, the MOSFET transistor has very
low resistance, supports high voltage and is refrigerated by an oversized heat sink. This allows temperatures over
the 60ºC shown in the Technical Characteristics section, and prolonged overloads such as those occurring at
batteries in deep charge mode (much higher than +15% voltage shown in the Technical Characteristics section).
High capacitance capacitors are also used, providing high tolerance to prolonged dips, 100ms, even in the most
unfavorable consumption conditions. This allows the relay to continue operating normally without undesired resets
leaving protection features offline.
3.3.1 Mounting
The unit is designed for semi-flush mounting. The relay is secured to the panel with the 4 M6 screws provided with
the unit. The front keypad, display, and communications port are easily access on the front of the unit. The wiring is
at the rear of the unit. Drilling dimensions are shown on Figure 3-3: Cutout and drilling dimensions
Note: For version 7.00 and above, only the serial card can be removed
The transformer module housing the VTs and CTs is already connected to a female
WARNING connector screwed to the case that incorporates shorting bars in the current inputs, so
that it can be extracted without the need to short-circuit the currents externally. It is very
important, for safety reasons, not to change or switch the terminals for CTs and VTs.
A grounded antistatic wristband must be used when manipulating the module in order to avoid electrostatic
discharges that may cause damage to the electronic components
Special care is required when disconnecting CT wire leads from the terminal block.
WARNING A high voltage potential can occur if a wire is disconnected while a CT is energized.
CT isolation or de-energization is required prior to CT terminal wire removal.
3.4 Wiring
3.4.1 External connections
F650 units can have different options for the F module:
Option 1: Board with 16 digital inputs and 8 outputs.
Option 2: Board with 8 digital inputs, 4 circuit supervision inputs, 6 conventional outputs, and two current
sensing outputs
Option 4: Board with 32 digital inputs.
Option 5: Board with 16 digital inputs and 8 analog inputs.
For slot G there are five different options:
Option 0: No board
Option 1: Board with 16 digital inputs and 8 outputs.
Option 2: Board with 8 digital inputs, 4 circuit supervision inputs, 6 conventional outputs, and two current
sensing outputs
Option 4: Board with 32 digital inputs.
Option 5: Board with 16 digital inputs and 8 analog inputs.
The number selected for slot G must be equal or higher than the number selected for option F for models including
boards 4 and 5.
In order to implement these schemes, it is not necessary to perform any setting in the
NOTICE unit. Internal functions are always operative. A detailed description of trip circuit
supervision is included in chapter 5 in this manual.
In models C and D (options for versions prior to 7.00), the 10/100BaseTx port is selected by an internal switch. This
switch must be configured as shown in the figure 3-8 in order to select between fiber or cable.
Title
Working Area
Safety instructions must be followed before connecting the computer to the relay. Safety
NOTICE instructions are detailed in section 1.1.3 Safety instructions. Connect the relay ground terminal
and the communicating computer to a good grounding. Otherwise, communication may not be
viable, or even, in worst cases, the relay and/or the computer can result damaged by
overvoltages.
When working online, ensure that all relay communication parameters, such as baud rate, slave ModBus address,
etc., match the computer settings before connected to the relay.
YES
Is it necessary to
program
additional logic?
Is the relay
completely
configured?
YES
Store in the computer the Logic configuration files (*.pep, *.aut, *.lib) as
well as the *.650 for further logic changes.
Description Settings and Configuration Section Header for Logic Graphical edition User
project container. Logic programmable
equations (Virtual logic objects
Outputs) in FDB
format.
Created by EnerVista 650 Setup Logic Logic configuration Logic configuration
configuration graphic editor (PLC graphic editor
graphic editor Editor) (PLC Editor)
(PLC Editor)
Contents Relay configuration file containing all elements PLC project file PLC Project file Library file to be
Settings, input/output and LEDs configuration, containing the containing all the included as an
graphic display configuration, etc. necessary drawings used by object in a PLC
Equations corresponding to the logic created and information the logic, required project. Logic
compiled in the PLC Editor relative to the by 650 relay based packages that can
relay model, logic on IEC 61131-3 be stored into
libraries included standard. libraries and be
in the project Functional block distributed in
(*.lib), graphic file diagram (FDB). different PLC
name (*.aut), etc. projects.
How to save EnerVista 650 Setup: PLC Editor: PLC Editor: PLC Editor:
File > Save * File > Save File > Save Project File > Save Library
Project
How to open EnerVista 650 Setup: PLC Editor: PLC Editor: PLC Editor:
File>Open * File > Open File > Open Project File > Library >
Project New Library
How to Connect with the relay (Communications > Connect with the relay (Communications > Computer)
transfer to Computer) Launch Logic equations Editor (Setpoint > Logic
relay Open the created file (File > Open *) Configuration)
Send to relay from the menu: File > Send info to Open the created PLC project (File > Open Project)
relay Compile the project (Run > Compile)
Note that texts used in the configuration of inputs, Now the logic (virtual outputs) can be sent directly to relay
outputs, etc. are not sent to the relay. The only texts (Run > Send Equations to Relay). Texts of virtual outputs
sent to relay are operations, events, and LEDs. are not stored in the relay, only in the logic configuration
files to be edited.
When using element libraries (both pre-existing in File Library > Open Library or created by the user in File Library
> New Library), the program creates and manages the corresponding files (*.lib) in a folder named FDB (Functional
Block Diagram). These files are used for PLC project compilation. The element library files must be stored with the
other logic configuration files that build the PLC project (*.pep, *.aut, *.lib).
Besides sending configuration information to the relay (Settings & configuration in *.650 format), storing the
complete set of *.650, *.pep, *.aut and *.lib files inside the relay is recommended (Communication > Upload info
files to relay). This ensures that logic configuration files are available in future for logic modifications. Even if these
files are not used by the relay, they are required to connect to the relay and analyze its configuration. The EnerVista
650 Setup software program manages the logic configuration files globally, so that when the *.pep file is uploaded to
the relay, the associated *.aut and *.lib files are also stored.
File storage inside the relay Communication > Upload info files to relay through Ethernet
(RECOMMENDED)
Retrieval of files stored in the relay Communication > Download info files from relay through Ethernet
(RECOMMENDED)
YES
Is it necessary to
program
additional logic?
NO Compile (“Run>Compile”)
and save logic file (*.pep) and drawing design
(*.aut) in Logic Configuration tool (“File>Save
Project”)
Is the relay
completely
configured?
YES
Store in the relay the Logic configuration files (*.pep, *.aut, *.lib) as well as the
*.650 for further logic changes. (“Communication>Upload info files to relay”)
Table 4-2: Types of files generated by EnerVista 650 Setup software, online
Logic Configuration Files (*.pep, *.aut, *.lib)
Settings & Configuration File *.650
*.pep *.aut *.lib
Description Settings and Configuration Section Header for Logic Graphical edition User programmable
project container. Logic logic objects
equations (Virtual
Outputs) in FDB
format.
Created by EnerVista 650 Setup Logic Logic Logic configuration
configuration configuration graphic editor (PLC
graphic editor graphic editor Editor)
(PLC Editor) (PLC Editor)
Contents Relay configuration file containing all elements, PLC project file PLC Project file Library file to be
settings, input/output and LEDs configuration, containing the containing all the included as an
graphic display configuration, etc. necessary drawings used by object in a PLC
Equations corresponding to the logic created and information the logic, required project. Logic
compiled in the PLC Editor relative to the by 650 relay packages that can
relay model, logic based on IEC be stored into
libraries included 61131-3 standard. libraries and be
in the project Functional block distributed in
(*.lib), graphic file diagram (FDB). different PLC
name (*.aut), etc. projects.
How to Connect with the relay (Communications > Connect with the relay (Communications > Computer)
transfer to Computer)
relay Send settings and configuration from file Launch 650 Logic equations editor (Setpoint > Logic
Configuration)
Open the created PLC project (File > Open Project)
Compile the project (Run > Compile)
Now the logic (virtual outputs) can be sent directly to relay
(Run > Send Equations to Relay). Texts of virtual outputs
are not stored in the relay, only in the logic configuration
files to be edited.
REMINDER:
Logic programming support files (*.pep, *.aut, *.lib) CANNOT be retrieved directly from the relay.
NO
NO
Save the PLC project New converted *.650 file is Save the *650
(File > Save Project) created and stored in the configuration file.
selected path. (File > Save)
Figure 4-5: Offline mode file management (firmware v7.70 and above))
Do not try to communicate with the relay during the start-up process. Doing so may
WARNING cause loss of the configuration file (*.650), leading to unexpected behavior.
Communication can be established safely once relay has fully started-up. The relay has
completed its start-up process when Menus are accessible from the HMI.
NO
Select PLC project (*.pep, *.qut,
NO *.lib) that matches equations
NO configured in the relay.
Modify settings and relay
configuration, and send to
the relay.
Does selected PLC
project match logic configuration
The PLC project is compiled YES compiled and running in the
and sent to the relay. The relay?
Is the relay PLC editor closes.
Is additional logic
completely NO
required?
configured? NO
NO
Go to Run > Save
YES Configuration File.
Do you want to send
equations to the relay?
The PLC project is sent to the
relay and the new equations
start to run.
NO
Figure 4-6: Online mode file management (firmware v7.70 and above)
The View > Language submenu allows the user to change the default language for the
NOTICE EnerVista 650 Setup program. This feature is only enabled when the relay is not communicating
and no file has been opened.
Table 4-3: EnerVista 650 Setup menu structure
IEC 61850
File Setpoint Actual Operations(*) Communication Security View Help
CONFIGURATOR
New (**) Product Setup Front Fixed Computer Login user Traces Instruction
Panel commands Manual
Open (**) System Setup Status Modem (*) Change ModBus GE Multilin
Password Memory on the web
Map
Save (**) Protection Metering Troubleshooti User Language About
Elements ng (*) Manageme s (**) EnerVista
nt 650 Setup
Save As (**) Control Inputs/ Calibration (*)
Elements Outputs
Close (**) Inputs/ Records Upgrade
Outputs (*) Relay (*)
Quick
Settings
Config File Relay
(* 650) Configuration
Converter
Compare to
settings file
Properties (**) Logic Upgrade 650
Configuration Web Server
Procome Update
Configuration Magnetic
Module
IEC103
Configuration
Get info from Clock (*) Upload info
relay (*) files to relay
Send info to Download
relay (*) info files from
relay
Print Setup (**)
Print Preview
(**)
Print (**)
Print to file
PLC Checksum
Calculation
Settings
Checksum
Calculation
Order Code
Exit
4.1.6.1 New
Use the File > New menu option to create a new default settings file while working offline.
To access this menu, there must be no communication between the Enervista 650 Setup program and the relay
(offline mode).
1. Select File > New.
EnerVista 650 Setup opens a pop-up window with a list of all files available for different models/firmware versions.
– Relay Selection: Select a 650 family relay (F650, R650, C650, W650 or G650).
– Redundancy Selection (firmware v7.00 and above only): Select to include files for F650/C650 relays with Rear
Ethernet Communications 2 Board options J, K, L and M.
– Models and Firmware Selection: Click to select one of the different models and firmware versions available.
2. Once you have selected a file, click OK and wait until the file has finished loading.
3. A message indicates when the new *650 file has been created. Click OK to access the new file in offline mode.
4.1.6.2 Open
Use the File > Open menu option to open an existing settings file while working offline.
To access this menu, there must be no communication between the Enervista 650 Setup program and the relay
(offline mode).
Open a *.650 configuration file for firmware versions 7.70 and above:
Enervista 650 Setup version 8.10 or above is required.
1. Navigate to File > Open and select a file to open.
– If the file is a firmware v7.70 or higher file, or has already been converted, proceed to edit the settings and
configuration.
– If the file has logic configuration that has not yet been updated for firmware v 7.70 and higher, continue to follow
these steps.
2. The following message is shown:
Depending on the *.650 file and selected PLC project files, one of the following messages may be displayed:
Message Meaning
Warning: Opening a file with firmware version x.xx while editing a The version of the *.650 configuration file and version of the PLC
file with firmware version y.yy project (*.pep, *.aut,*.lib) do not match.
Logic might be modified. Continue anyway?
Some PLC project variables may not be supported by the *.650
configuration file.
Compiled equations are different from the ones stored. Do you Logic equations compiled in the *.650 configuration file do not
want to overwrite the stored equations? match equations in the selected PLC project (*.pep, *.aut,*.lib).
Select Yes, and logic configuration from the selected PLC project
(*.pep, *.aut,*.lib) will be compiled and saved into *.650
configuration file.
Select No, and the original logic will remain in the *.650
configuration file.
File conversion failure. You must select an existing or a new PLC This message indicates that the conversion process is
project to continue with file conversion. unsuccessful because a PLC project has not been selected.
5. Upon successful file conversion, the newly converted *.650 file is saved.
4.1.6.3 Save/Save as
The Save as and Close file options are used to save the *.650 file into the computer and to close the current file. To
work in offline mode for settings and configuration editing, a new *.650 file can be opened without closing the
previous file.
To access this menu, there must be no communication between the Enervista 650 Setup program and the relay
(offline mode).
During settings and configuration edits, saving your file regularly is recommended. Unsaved changes will be lost
when the file is closed.
4.1.6.4 Close
In addition to closing the working file, the File > Close option is used to clear all data in the EnerVista 650 Setup
program, enabling the Language, Upgrade firmware version, and Upgrade Operating system menu options.
Use the File > Close menu option to close a settings file while working offline.
To access this menu, there must be no communication between the Enervista 650 Setup program and the relay
(offline mode).
If File > Close is selected during *.650 configuration process, without first saving the file (File > Save), the following
warning message is shown:
Click OK to open the File > Save/Save as window, or Cancel to close without saving.
Source Model
Destination Model
• If the source (*.650) configuration file contains Logic configuration, a PLC project (*.pep, *.aut, *.lib) must be selected
for insertion into the converted (*.650) configuration file.:
The selected PLC project file is checked against the (*.650) configuration file to ensure they match. If the files do not
match, the following message pops-up:
Select Yes, and the equations available on selected PLC project (*.pep, *.aut, *.lib) will be compiled and stored into
(*.650) configuration file. New equations will overwrite the equations existing in (*.650) configuration file
Select No, and the following message will display to indicate that file conversion process has failed.
To convert the *,650 file, a new PLC project (*.pep, *.aut, *.lib) must be selected for insertion into the converted
(*.650) configuration file.
Note: If the PLC editor is closed before selecting, compiling and storing a PLC project, the file conversion process
will not be successful.
CASE 2: If the setting groups option is enabled (Setpoint > Control Elements > Setting group) in the source file,
conversion to the destination file is as follows:
• Settings of different elements (Phase TOC High 1, 2 and 3) that belong to different setting groups in the source file are
copied into elements that belong to first group of first three setting groups in the destination file
• Protection elements in the other groups/setting groups are configured with default values in the destination file.
SG1 SG2 SG3 SG4 SG5 SG6
Phase TOC High G1 G2 G3 G1 G2 G3 G1 G2 G3 G1 G2 G3 G1 G2 G3 G1 G2 G3
Reset INSTANTANEOUS
Voltage DISABLED
Restraint
Snapshot ENABLED
Events
4.1.6.6 Properties
When this option is selected, the program displays the relay model information, firmware version, etc. of the file
being edited, as shown:
Print setup
Option to configure the printer options and settings.
Print preview
Option to preview the whole settings and configuration file (*.650) in paper format to be printed as shown:
Print
Option to print the relay configuration using the PC default (active) printer on port COMx or LPT. This option is active
only in offline mode and in file edition (not in online mode while connected to the relay).
Setpoint
Product Setup Communications settings for all protocols and physical mediums. ModBus user map
definition, fault report, oscillography, data logger demand settings and Time Settings.
System Setup General Settings, Flex Curves Definition, Breaker settings, maintenance, switchgear
snapshot events management and Miscellaneous Settings.
Protection Elements Phase, Neutral, Ground, Sensitive Ground and Negative Sequence Current Settings.
Voltage Elements settings and Power Settings management.
Control Elements Setting groups, under- and over-frequency settings, synchrocheck, autoreclose,
breaker failure, VT fuse failure, broken conductor, locked rotor settings management,
Pulse Counters, Analog comparators, Frequency Rate of Change, Load
encroachment, max number of starts, Digital Counters, Cold Load Pickup and PLC
Timer Masks
Inputs/Outputs Contact I/O settings for all boards available in device, Remote Comms Force Outputs
and Virtual inputs.
Quick Settings Menu that encompass the most important settings to configure the device such as;
Current and Voltage sensing or current protection element.
Relay Configuration Configuration of Outputs, LEDs, Operations, Protection Elements, Oscillography,
Control Events, Control Elements, Switchgear, Inputs, Virtual Inputs, Operations and
HMI. Whole relay configuration with internal relay signals or user-definable ones as
logic (virtual outputs).
Logic Configuration Logic configuration graphic editor (PLC Editor). It is a PLC Project file editor that
contains all the internal drawings used to make the logic (virtual outputs) based on
IEC 61131-3 standard. Functional block diagram (FDB).
Procome Procome Configuration tool. Only available for Procome models (5) when
Configuration communicating through Ethernet with EnerVista 650 Setup
IEC103 Configuration IEC103 settings for available IEC103 models (3) when communicating through
Ethernet with Enervista 650 Setup
Clock (*) Relay synchronization to computer clock or to user-definable date and time. Online
mode only.
(*) indicates online only, (**) indicates offline only
Product Setup
Communication Serial Ports, Network (Ethernet), ModBus Protocol, DNP Slave, IEC 870-5-104, SNTP
Settings settings and procome (if available on model selection), PTP1588 and Routing (for
firmware version 7.00 and higher)
ModBus User Map ModBus user map definition. The ModBus user map is formed by 256 records,
selectable from the complete relay ModBus map.
Fault Report Fault report settings. Possibility to show fault reports on HMI screen.
Oscillography Oscillography settings (trigger position, samples per cycle, etc.). The trigger and digital
channels (up to 16) must be configured in Setpoint > Relay configuration.
Data Logger Data logger configuration
Demand Demand settings. The demand trigger and demand reset signals must be configured
in Setpoint > Relay configuration
Time Settings Time settings.
Communication
Settings
Serial Ports Baud rate and parity for COM1 and COM2 serial communication ports.
Network (Ethernet) Ethernet communication parameters for ETH_1/ETH2 or ETH_E/ETH_A/ETH_B
(Depending on model) (IP Address, Netmask, Gateway IP)
NOTE: The ModBus Slave address used by Ethernet ports is the one set for
COM2.EnerVista 650 Setup software allows programming two different Ethernet
addresses, but the first IP has always to be set as the second IP Address is an
Alias.
ModBus Protocol ModBus Slave Addresses for serial and Ethernet communication and the ModBus
port number used for ModBus TCP/IP
DNP3 Slave Physical port, Slave Address for DNP, IP Addresses for Masters, TCP/UDP Port,
Unsolicited Response parameters, Analog scale factors and deadbands, message
fragment size, Binary input block.Available for standard and IEC61850 models.
IEC 870-5-104 TCP Port, Common Addr of ASDU, Cyclic Meter Period and, Synchronization
Event settings.Available for standard and IEC61850 models.
SNTP (*) Synchronization over Ethernet settings
PROCOME Comm port and slave number for procome protocol. Only available for
procome models (5).
PTP 1588 Precision Time Protocol 1588 settings. (Available on fw version 7.00 or higher)
Routing A default route and a maximum number of 6 static routes may be configured. The
default route is used as the last choice, if no other route towards a given
destination is found.This option is only available for version 7.00 and higher.
(*) indicates online only, (**) indicates offline only
System Setup
General Settings This screen describes and enables the settings of the power system where the relay
operates. Some of these settings are used only for metering values presentation
purposes; however, some of them apply directly to the sampling and analog-digital
conversion process (rated frequency setting). Therefore, these settings need to be
adjusted to fit the system settings.
Flex Curves Flex Curves – Programmable user curves: The relay incorporates 4 user curves
called Flex Curve A, B, C and D. The points for these curves are defined by the user in
Setpoint > System Setup > Flex Curves > Edit Curve menu in EnerVista 650 Setup.
User defined flex curves can be selected as an operation curve in all the time
overcurrent functions in the relay.
Breaker Breaker Configuration
Switchgear Configuration of snapshot events for each switchgear (enable or disable)
Miscellaneous This screen contains settings related with relay working mode. Out of service setting,
Settings Local/Remote mode and Active language mode are options listed below.
(*) indicates online only, (**) indicates offline only
Breaker settings Breaker settings, maintenance and switchgear selection of the device configured as breaker in the F650.
The selected switchgear is used in recloser, breaker failure and synchronism functions. The settings are
Number of Switchgear, Maximum KI2t, KI2t Integ. Time, Maximum Openings, Max.Openings 1 hour and
Snapshot Events.
Breaker maintenance These settings correspond to the initialization of (KI)2t counters, and the counting of number of openings
and closings of the switchgear configured as breaker. These Counters allow the breaker Maintenance.
They are used to cumulate the breaker aging produced by a trip or a breaker opening. In order to
incorporate the breaker historic, in case of existing breakers, the system allows assigning an initial value
to accumulated amperes, and to the number of opening and closing operations.
Firmware version 7.50 and above also include Frequency and Miscellaneous menus in the Protection Element
section.
Frequency
Underfrequency Underfrequency unit (81U).
Overfrequency Overfrequency unit (81O).
Frequency Rate of Frequency rate of change function (81R).
Change
Miscellaneous
Broken Conductor Broken or fallen conductor detection function (I2/I1). Grouped element. Ratio
between the negative sequence current, I2, and the positive sequence current I1.
In normal and balanced load situations, this ratio is zero, while in severe load fault
conditions, an unbalance is produced and this ratio is increased.
Locked Rotor Locked rotor detection function (48).
Load Encroachment Load Encroachment function.
Table 4-8: Control elements menu, firmware version 7.50 and above
Control
Elements
Setting Group F650 incorporate a flexible grouping capability for protection units can be used in
either single setting group (default mode- All units that belong to Active group,
configured in Setpoint > Control > Setting Group, can operate simultaneously ) or up to
six setting groups (in this mode, all protection elements, that are available when
setting group function is disabled, will be available in each individual setting group (Up
to maximum of 6). Only one of setting group will be active at a given time). Units
grouped under Protection elements section will be the units affected by changing of
setting group.
Synchrocheck Synchronism check unit (25). Single element.
Autoreclose Recloser (79). Single element.
Breaker Failure Breaker failure (50BF). Single element.
VT Fuse Failure Fuse Failure (VTFF). Single element.
Pulse Counters Pulse counters function. 8 counters provided.
Analog Comparators Analog comparator function. 20 analog comparators provided.
Max. Number of Maximum Number of Starts (66). Single element.
Starts
Digital Counters Up to 8 Digital Counters
Cold Load Pickup Cold Load Pickup Function. Single element. Available for firmware version 7.00 and
above.
PLC Timer Masks Configuration of masks that can be assigned to PLC timers
60 CTS Failure Current transformer failure function
2nd HRMC Inhibit Second harmonic inhibit
Relay
Configuration
Outputs Configuration of contact output operate and reset signals for all boards.
LEDs 15 LEDs fully configurable from any logical variable, contact or virtual input. First 5
LEDs are latched by hardware, the rest are self-reset but can be latched through PLC
configuration. For firmware version 7.20 and higher, all 15 LEDs can be latched by
setting. From the LED configuration screen, it is possible to print the vertical LED label
for the relay.
Operations Configurable operations up to 24. Operation texts, interlocks, final states, frontal keys,
time outs and masters.
Protection Elements This tab allows assigning operands (logic signals) as inputs to different protection
elements. To block, reset, initiate the different protection elements inputs.
Control Elements This tab allows assigning operands (logic signals) as inputs to different control
elements.
Oscillography Trigger and up to 16 digital channels to be included in oscillography records, are
programmable from any logical variable, contact or virtual input. Text configuration is
only for offline mode.
NOTE: This screen is used for the configuration of digital channels and oscillography
trigger. The rest of parameters, such as function enabling/disabling, sampling rate,
number of oscillography files, etc. must be set on the Setpoint > Product Setup >
Oscillography menu.
Control Events Up to 128 user programmable events from any logical variable, contact or virtual input.
Possibility to display the event as an alarm on the alarms panel. Control events are
also displayed in the snapshot events recording. 1 ms time tagging.
A control event is a logic signal associated with an operand or combination of
operands, that allows following the status of that signal.
Switchgear Up to 16 configurable switchgear elements. A switchgear element can be a breaker, a
line selector switch, a grounding selector switch, a busbar selector switch, etc. This
screen allows configuration of type of contacts, opening and closing time, contact
assignation and text for events related to switchgear. There are 64 pre-established
events for switchgear, which correspond to opening, closing, Error01 and Error11 of
the 16 programmable switchgear elements.
Remote outputs Up to 32 DNA bits and 64 user St bits to be transmitted to remote devices over CAN
using GSSE messages
Inputs Text configuration for offline mode file management for all the contact inputs available
in device.
Virtual Inputs Text configuration for offline mode file management. 32 latched and 32 self reset
virtual inputs.
MMI (HMI-Human Screen one line diagram configuration. This menu shows a canvas to draw a
Machine Interface) simplified one-line diagram of a bay in a feeder, line, transformer, etc. The menu
includes a library for power elements, metering elements, text and drawings. See an
example on the next page.
The following figures show an example of the default factory configuration for F650:
Actual
Front Panel The relay front LED status is shown on this menu.
Status Protection and control status signals for all available protection functions in device.
Metering All metering values available in device. Primary and secondary values, frequency and
phasor diagram provided.
Inputs/Outputs All input and output status provided. For contact inputs and contact outputs as well as
virtual input and virtual output signals.
Records Only enabled in online mode, retrieval of all the available records in device. Snapshot
events, control events, oscillography and fault reports.
4.1.8.2 Status
The following menu includes all the available protection status in the device. Location of different menus can vary
depending firmware version.
status
Operation Bits Up to 24 elements. OPERATION BIT XX is (0) when the configured time out for the
operation XX expires or when success conditions are met. And it is (1) if operation XX
is executed and interlocks are fulfilled.
Breaker Breaker status (open, closed or undefined). The rest of the status signals
corresponding to the switchgear XX configured as breaker are in the Status >
Switchgear Status > Switchgear XX menu.
Protection Status of all the protection units in the device.
Control Elements Status of all the control units available in the device.
Protection Summary This screen shows a complete list of all protection and control elements in the relay,
showing their status (enabled or not).
Snapshots Events Summary of the snapshot events status (enabled or disabled) for protection, control,
summary inputs and outputs boards and switchgear.
ModBus User Map Up to 256 elements. Value in SIGNED INT 16 BIT format of the reading for the
selected address configured in Setpoint > Product Setup > ModBus User Map
Switchgear Status Up to 16 blocks of switchgear status signals for the 16 configurable devices. Status
signals such as inputs for A and B contacts, status for A and B, open and close status,
error 00 and error 11, open init and close init, fail to open and fail to close signals.
Calibration Internal states for calibration. Factory calibration and calibration error signals.
FlexCurves Flex curve status for A, B, C and D user curves. (0) if it is not configured, (1) if it is
configured. To configure a flex curve go to Setpoint > System Setup > Flex Curves
menu.
System Info This screen can monitor the system parameters and the internal status of the Relay
operating system. Not enabled by default, password required
Records Status Information related to the different records stored in the Relay, such as: Fault reports,
control events, oscillography, data logger, demand, energy, and breaker maintenance.
SNTP-IRIG_B & Information related to synchronization via IRIG_B, SNTP or PTP1588.
PTP 1588
Versions Information related to the different firmware versions and hardware revisions.
Redundancy Information related to the status of the frames sent through PRP and HSR. Also
information related to the status of RSTP port.
Thermal Model Protection status signals for thermal model. Reset, alarm and operation signals for
phases and for unit, besides the thermal image values in percentage for all phases
and units.
Voltage Protection status signals (pickups and operations) for all voltage functions,
undervoltage, overvoltage, neutral overvoltage, negative sequence overvoltage and
auxiliary under and over voltage.
Power Protection status signals (pickups and operations) for forward, directional and
wattmetric ground fault (high and low) power units, and power factor status. Power
values for 32N High and Low functions (in watts).
Table 4-10: Control elements, actual values menu, firmware versions below 7.50
Control
Elements
Frequency Status signals (pickups and operations) for under, overfrequency and frequency rate
of change units.
Synchrocheck Status signals for synchrocheck function (25).
Autoreclose Status signals for autoreclose function (79). Close signal, recloser status (ready,
lockout, etc.), block signals after each shot.
Breaker Failure Status signals for breaker failure function (50BF).
VT Fuse Failure Fuse failure detection signal.
Broken Conductor Status signals (pickups and operations) for broken conductor (I2/I1).
Setting Groups Status signals (activations and blocks) for the relay setting group change. By default
the "setting group" setting is disabled and all the grouped elements can be enabled at
the same time.
Locked Rotor Status signals (pickups and operations) for locked rotor units.
Pulse Counters Status signals for pulse counters units.
Analog Comparator Status signals for analog comparator units.
Load Encroachment Status signals (pickups and operations) for load encroachment units.
Max. Number of Status signal for number of starts operations
Starts
Digital Counters Status signals for the Digital Counter units.
Cold Load Pickup Status signals for the Cold Load Pickup Function.
Table 4-11: Control elements, actual values menu, firmware version 7.50 and above
Control
Elements
Frequency Status signals (pickups and operations) for under, overfrequency and frequency rate of
change units.
Synchrocheck Status signals for synchrocheck function (25).
Autoreclose Status signals for autoreclose function (79). Close signal, recloser status (ready,
lockout, etc.), block signals after each shot.
Breaker Failure Status signals for breaker failure function (50BF).
VT Fuse Failure Fuse failure detection signal.
Broken Conductor Status signals (pickups and operations) for broken conductor (I2/I1).
Setting Groups Status signals (activations and blocks) for the relay setting group change. By default the
Setting Groups setting is disabled and all the grouped elements can be enabled at the
same time.
Locked Rotor Status signals (pickups and operations) for locked rotor units.
Pulse Counters Status signals for pulse counters units.
Analog Comparator Status signals for analog comparator units.
Load Encroachment Status signals (pickups and operations) for load encroachment units.
Max. Number of Status signal for number of starts operations
Starts
Digital Counters Status signals for the Digital Counter units.
Cold Load Pickup Status signals for the Cold Load Pickup Function.
60CTS Failure Status signals of Current transformer failure Function
2nd HRMC Inhibit Status signals of Second Harmonic Inhibit Function
4.1.8.3 Metering
The Metering menu includes all the measurements available in the device. Primary and secondary values, and also
the data related to the recording functions in the relay
metering
Primary Values Primary values measurements for currents, voltages, power, energy and demand
Secondary Values Secondary values measurements for currents, voltages and power.
Phasor Diagram Current, voltage and sequence components.
Frequency Line and Bus frequencies.
inputs/outputs
Contact Inputs Status of digital inputs in the Relay for each board according to the relay model.
Contact Output Status of digital outputs in the Relay for each board according to the relay model.
Status
Contact Outputs Status (activated or not) of the variables used to operate a contact output. To
Operates configure these signals go to Setpoint > Relay Configuration > Outputs menu.
Contact Outputs Status (activated or not) of the variables used to reset a contact output. To configure
Resets these signals go to Setpoint > Relay Configuration > Outputs menu. This output
reset Command is only effective if latch is selected for Output Type setting on the I/O
board, thus the contact output has been configured to emulate function 86 (latching
relay).
IO Board Status Status of I/O boards. This status provides if the hardware it is OK (boards matching
relay model, correctly inserted in their tracks, in good state and communicating
through the internal CAN bus).
Virtual Inputs Status of Virtual inputs latched (32) and self-reset (32).
Virtual Outputs Status of virtual outputs (configured in PLC Editor). Up to 512.
Remote Outputs States of remote outputs for IEC61850 models.
Remote Inputs Status of remote device and remote inputs for IEC61850 models.
Analog Inputs (*) Measurements coming from analog inputs (DCMA)
Virtual Output Status of Virtual Output Latched (configured in PLC Editor). Up to 16.
Latched
Virtual output Status of Virtual Output Analogues configured in PLC Editor). Up to 49 float values
Analogue and 49 integer values can be used.
(*) indicates online only, (**) indicates offline only
Records (*)
Event recorder (*) Retrieval and visualization of snapshot event (all and new), control events and alarm
panel. By serial or Ethernet (ModBus RTU or TCP/IP)
Waveform capture (*) Retrieval of oscillography files, by Ethernet.
Fault Report (*) Retrieval and visualization of fault report files, by Ethernet.
Data logger (*) Retrieval and visualization of data logger files. Only by Ethernet.
operations
Operation 1 (*) Entry to first operation (with its corresponding text)
... ...
Operation 24 (*) Entry to 24th operation (with its corresponding text)
(*) indicates online only, (**) indicates offline only
Communication
Computer Menu to start communication with the relay.
Modem (**) Configure the unit for remote communications via modem, using a telephone line.
This is only available if the relay is not communicating and if modem has been
selected under Communication > Computer control type.
Troubleshooting (*) Read/write to ModBus addresses, for verifying communications and access to
different positions in the ModBus memory map. Only available if the communication
has already been established.
Calibration (*) Retrieve the unit calibration settings and storing them in a file (with extension *.cal).
For reading or storing the calibration settings in the relay go to Communications >
Calibration > Get or Set calibration settings and select the intended calibration file.
The calibration retrieval process must be performed before updating the operating
system. When the firmware and bootcode are updated, all the data in the relay is
deleted, including the factory calibration settings. When only the firmware is updated
(for versions higher than 1.50), the calibration settings are automatically saved in the
relay.
Upgrade relay (**) Upgrade firmware version (Ethernet connection): Update the relay firmware through
Ethernet communication. Firmware is related to the relay internal program, designed
by GE Multilin, which performs the protection and control functions, and which is run
by the relay main microprocessor.
Upgrade 650 web Upgrade 650 web server (Ethernet connection): Go to Communications > Upgrade
server 650 web server. The relay web server application can be updated to further versions
(if available) using this menu without modifying the relay operating system.
Upload info files to Upload info files to relay (Ethernet connection): This functionality is used to store
relay setting files (*.650) inside the relay, as well as auxiliary files used by the
programmable logic graphical editor (*.pep, *.aut, *.lib).
Download info files Download info files from relay (Ethernet connection): This functionality is used for
from relay retrieving the files (*.650 and *.pep, *.aut, *.lib) that have been previously stored in the
relay flash memory.
(*) indicates online only, (**) indicates offline only
For firmware versions below 7.00, check that the firmware version that is going to be
NOTICE updated matches the operating system version of the relay before updating firmware.
If not, update the operating system before proceeding to update the firmware. Other
combinations of firmware and operating system different from the listed in section 5
will not be operative.
For previous version than 7.00 the operating system version is available in the
logotype main screen in HMI; it is the number between brackets in the first line, e.g.
F650 1.70 (2.35). The operating system version is 2.35
*.650 files contain protection, control settings, relay configuration and compiled logic equations.
NOTICE This file can be retrieved from the relay, using the File > Get info from relay option in EnerVista
650 Setup (through serial or Ethernet communication). File > Send info to relay option stores
this *.650 file in the relay.
*.pep, *.aut and *.lib files contain the logic configuration projects necessary to modify the logic
(virtual outputs) in the relay. These files can be stored in the relay, using the Communication >
Upload info files to relay option in EnerVista 650 Setup (through Ethernet communication).
They can be retrieved using Communication > Download info files to relay option in
EnerVista 650 Setup program (Ethernet communication). Take into account that the *.pep, *.aut
and library files are necessary to modify the PLC logic (virtual outputs). Without these files
setting and configuration can be modified but not logic equations (virtual outputs). It is advisable
to use the Communication > Upload info files to relay option to store these logic
configuration files into the relay.
*.pep, *.aut and *.lib files contain the logic configuration projects necessary to modify the logic
(virtual outputs) in the relay. These files can be stored in the relay, using the Communication >
Upload info files to relay option in EnerVista 650 Setup (through Ethernet communication).
They can be retrieved using Communication > Download info files to relay option in
EnerVista 650 Setup program (Ethernet communication). Take into account that the *.pep, *.aut
and library files are necessary to modify the PLC logic (virtual outputs). Without these files
setting and configuration can be modified but not logic equations (virtual outputs). It is advisable
to use the Communication > Upload info files to relay option to store these logic
configuration files into the relay.
security
Login User (*) Log on menu for EnerVista 650 Setup. Enabled after security control has been
enabled in user management menu.
Change Password (*) Menu to change passwords and establish password recovering questions.
User Management (*) User management dialog box.
View
Traces (*) ModBus communication traces between the EnerVista 650 Setup and the relay.
ModBus Memory Complete ModBus memory map description.
map
Languages (**) Option to change the EnerVista 650 Setup default language. Only available if the relay
is not communicating and no file (*650) is open.
(*) indicates online only, (**) indicates offline only
Help
Instruction Manual Instructions manual in the language selected in View > Languages.
GE Mulitlin on the GE Multilin web page link.
Web
About EnerVista 650 Release version and date of the EnerVista 650 Setup program.
Setup
HMI Interface
FRONT PORT
Figure 4-19: HMI interface, available for firmware versions 7.00 and below
4.2.1 Display
F650 units are available with two different options for the front display. The first option is an alphanumerical display
of 4 lines with 20 characters each, and the second option is a graphical display of 16 lines with 40 characters each
(128x240 pixels).
The boot code and firmware versions can be seen in the relay text main screen, this screen is the default screen in
the text menu for all models: After the text “F650“, appears the relay firmware version (7.00 in the example), and
between brackets the boot program version (7.00 in the example), followed by “General Electric”, the relay model
and the default front port (COM2) communication parameters.
4.2.3 Pushbuttons
The front panel provides:
Push buttons: keypad (5 user programmable plus ESC/ESCAPE non configurable), shuttle key or keypad for easy
navigation, command pushbutton to select operations mode.
RS232/USB port: intended for connection to a portable PC.
I
This button can be used for closing the user-programmable switchgear. It is fully
programmable by the user.
O This button can be used for closing the user-programmable switchgear. It is fully
programmable by the user.
*
User programmable.
F1
User programmable.
F2 User programmable.
(ESC) Escape key. When pressed for more than 3 seconds, it tests all LEDs and
ESC
resets the trip LEDs.
Rotary knob or Shuttle Key (it can be both rotated and pressed): Used for selecting
menus, sub menus, settings and for confirmation. Press or rotate the shuttle key to
enter the text main menu from the text standby screen.
Figure 4-22: Keypad and shuttle key description, basic display models (not enhanced)
8VHGIRUFORVLQJWKHXVHUSURJUDPPDEOH
VZLWFKJHDU,WLVIXOO\SURJUDPPDEOH
F3 / *. User programmable.
Press the command button to switch from local to remote operations mode and vice versa. OFF status (operation
inhibited for maintenance and safety) can be reach pressing the commands pushbutton during several seconds
(local-remote-off sequence).
The local-remote-off sequence can be also available through communications (see chapter 5.8), with a configurable
signal that can be set in the Setpoint > Relay Configuration > Control Elements screen.
4.2.6.1 Navigation
Text menu is available for all models, this is the main menu for visualizing actual values, metering, changing settings,
etc. through the HMI. In models with graphical display besides this text main menu there are several screens
providing more performance for control purposes.
Press (or rotate left or right) the enter/shuttle key to enter the main menu, starting from the standby screen (default
main screen). The default main screen can be accessed pressing ESC key until it appears. In all the navigation
press the enter/shuttle key to select the desired header display (top-level menu). Each press of the enter/shuttle key
advances through the main heading pages as illustrated below. To return to previous menus press the ESC key. To
move inside the top-level menu without changing to other low levels, rotate the shuttle key left to move up and right
to move down (or use up/down keys).
When rotating the shuttle key (or up/down keys) the selected menu is marked by a single scroll bar character. The
mark (>) in the right part of any menu means that contains more than one level.
Figure 4-25: Text menu navigation Shows an example of main menu navigation:
Calibration
FlexCurves
System Info
Records Status > Fault Reports
Control Events
Oscillography
Data logger
Demand
Energy
Breaker Maintenance
SNTP-IRIG_B-PTP
Versions
Redundancy
Metering >
Primary Values > Current
Voltage
Power
Energy
Demand
Frequency
Inputs/Outputs
>
Contact Inputs > Board F/ Board G/ Board H/ Board J
Cont. Output St. > Board F/ Board G/ Board H/ Board J
Cont. Output Op. > Board F/ Board G/ Board H/ Board J
Cont. Output Rs. > Board F/ Board G/ Board H/ Board J
IO Board Status
Virtual Inputs > Virtual Inp.Latched
Virtual Inp.SR
Virtual Outputs
Remote Outputs (for DNA
IEC61850 models only) > User St
GOOSE Dig Outputs
Remote Inputs for Remote Input
IEC61850 models only)> Remote Devices
GOOSE Dig Inputs
GOOSE Analog Inputs
To enter this menu press the shuttle key or enter key when the option Actual Values is selected in main menu. A
secondary level is displayed with different sub levels as shown on . Pressing Up/down keys or rotating the shuttle
key, (left for moving up and right for moving down) select the next level to be displayed, press the enter/shuttle key
again to enter in next level and press ESC key to return to previous level if desired. This navigation is performed the
same for all the menus in Actual Values. Once the last sub level is reached, move up and down to visualize the
actual values selected.
One example of data screen for actual values is shown in Figure 4-26: Actual values screen data.
First Line: Header of last level in actual values (Phase Current in the example)
Second Line: Data identifier (in the example PH IOC1 HIGH A, is the pickup signal for the first instantaneous
overcurrent function level high for phase A).
Third line: Status of the displayed actual value.
Fourth Line:Relative position in the menu (it is the first value of 114)
Phase Current
PH IOC1 HIGH A PKP
OFF
(1/114)
Press enter/shuttle key from the default main screen and enter in the main
text menu.
Move the shuttle key or press up-down keys until a single scroll bar
character (o) appears in the left part of Snapshot event header.
Select the snapshot event to display using the up/down keys or shuttle key
(left and right to move up and down inside the recorded snapshot events).
Once selected the snapshot event, identifier, status, date and time are
displayed.
In the second line St: is showing the status and the relative snapshot index
from the whole recorded number. Third and fourth lines are used to display
the time and date of the snapshot event.
Pressing the enter/shuttle key the metering screen for the snapshot event is
displayed.
To exit from this screen press the ESC key and return to the snapshot
events menu.
Figure 4-27: Snapshot event navigation HMI
If there is more than one fault record press the up-down keys or rotate the
shuttle key and select the desired record to be displayed.
First screen with general fault information: Fault report #number, fault type,
distance and date and time.
Second screen with metering data for that fault record. All this data is a
summary from the fault report file that can be retrieved via EnerVista 650 Setup
software.
MAIN SETTINGS MENU FIRST LEVEL SECOND LEVEL THIRD LEVEL MAIN SETTINGS MENU
Protection Element >
Setting Group X >
Phase Current >
Phase TOC High > Phase TOC High 1..3
Phase TOC Low > Phase TOC Low 1..3
Phase IOC High > Phase IOC High 1..3
Phase IOC Low > Phase IOC Low 1..3
Phase Directional > Phase Directional 1..3
Thermal Model > Thermal Model 1..3
Neutral Current >
Frequency >
Underfrequency > Underfrequency 1..6
Overfrequency > Overfrequency 1..6
Fq Rate of Change > Fq Rate of Change 1..3
Miscellaneous >
Broken Conductor > Broken Conductor 1..3
Locked Rotor > Locked Rotor 1..3
Load Encroachment > Load Encroachment 1..3
Control Elements >
Setting Group
Synchrocheck
Autoreclose
Breaker Failure
VT Fuse Failure.
Max. Num of starts
Select the menu Change settings and press the enter/shuttle key to enter in the
next sub levels.
If there is more than one sub levels, select the next sub level by pressing the
up-down keys or rotating and pressing the enter/shuttle key until the last level is
reached.
Pressing the enter/shuttle key, value appears between brackets and can be
modified pressing the up-down keys or rotating the shuttle key. Pressing again
the enter/shuttle key, the new value is accepted.
Once all settings inside the group have been modified, go to the last screen
pressing the down key or rotating the shuttle key and press Enter. At this
moment of time, the new settings is active in the relay.
Once this sequence is completed, these values remain stored in the relay, and the display once again shows the
date at the bottom of the text screen.
Figure 4-30: Change date & time in HMI
4.2.6.9 Commands
Commands are configured using EnerVista 650 Setup, and they can be executed using the pushbuttons on the relay
front.
Use the EnerVista 650 Setup software to configure up to 24 commands with a descriptive text. When executing the
operations from the relay front panel, the operation description is displayed.
Example of commands (operations) executions via HMI
Press the enter/shuttle key when Commands is selected in the display (o).
All the previously configured commands are displayed. Press up-down keys or
rotate the shuttle key to move through the available commands. Press ESC to
return to previous level.
When the message Push Enter for Confirmation appears, press the enter/
shuttle key to confirm.
Once the command has been performed or the time out has expired the
Command completed message is shown on the display.
4.2.6.10 Passwords
The F650 units incorporate independent passwords for protection and control, in order to prevent unauthorized
keypad and display access to the relay.
Settings Password:
This password restricts access to settings changes in the relay protection elements.
Commands Password:
This password restricts access to executing operation commands through the keypad and display.
If the Commands Password is activated, when the user tries to execute an operation, the relay requests this
password. When using single-line diagrams for graphical display models, all objects are not operational until the
password is entered, either by logging in to Login Pwd Commands, or by entering the password in the Commands
menu.
Relay settings view, measures, and other monitored information are not password-protected, and can be accessed
by all users.
The password menu is located at the Password option in the relay text menu. This menu includes the following
options:
“Login Pwd Settings”
“Logout Pwd Settings”
“Change Pwd Settings”
“Login Pwd Commands”
“Logout Pwd Commands”
“Change Pwd Commands”
“Forgot Password?”
Among the available options in this menu, there are three types of functionality:
Login: For entering the password, either for settings or commands, and enable access to settings
or commands. Once entering the password the relay is no longer password protected, and
access is enabled to settings modification or commands execution.
Logout: Once the necessary setting changes or operation commands have been executed, the
user can log out, so that the relay is password protected again.
Change: Setting or modifying the desired password.
Forgot Password: Retrieves the encrypted password, so that it can be recovered if the user loses or forgets it.
Passwords are restricted for Settings change and Commands execution. To password-protect the relay, it is first
necessary to set the desired password, using the corresponding Change Pwd... menu. The default password is
0000. This password provides access to the whole relay functionality.
Once a new password has been set, the user must log in to access the protected functionality; otherwise, the relay
requests the password when trying to change settings or execute commands. Once the password is entered the
relay is unprotected (as if the user had logged in), and remains so for 15 minutes of inactivity or until the user logs
out.
Password range
The valid range for F650 passwords is a number from 0000 to 9999.
The default password is 0000, which provides access to the whole relay functionality. This is the default option for
enabling relay use without using passwords.
Logotype
This option selects as main screen the relay logotype including the firmware and boot code versions, the relay model
and the communication parameters for local port COM2.
Press up-down keys or rotate the shuttle key to select the desired language
and press enter to store the selection in the relay
Once the new language has been selected it is necessary to reboot the relay in
order to start working with the new language in the device.
Freq = 0.00 Hz
The bottom of the display shows a legend that indicates the possible selections that can be made from this screen.
Esc: Menu. Enter: Next. : Select.
This legend means that there are a total of events stored in the relay, and that the cursor is located on event number
1. The information shown on this screen for each event is as follows:
"Hour:Minute:Second:Millisecond" "Event text" "Event status (ON/OFF)"
Esc: Prev.
Pressing the ESC key, the user returns to the previous screen (Metering screen)
Intro: Menu.
Pressing the enter/shuttle key, the user accesses the Events menu that offers the following options at the bottom of
the screen:
nextprevreloaddetailsAt
To access the different options in the snapshot events graphic menu the user must move the cursor from up to down
or from left to right. The selected option is displayed in upper case and between brackets. To access the selected
option, the user must press again the enter/shuttle key.
<NEXT>
The user accesses the next available graphic screen (Events – New)
<PREV>
This option returns to the general events graphic menu (All Events)
<RELOAD>
This option updates all events stored in the relay and returns to the general events screen.
<DETAILS>
The Details screen provides access to metering values, and date and time related with the event.
The top of the screen displays a legend with the event text, followed by the date and time, the event status (ON or OFF),
and the event index number related to the complete list of events in the relay, for example (1/479). The rest of
information provided by the Details screen corresponds to the relay measures in the moment of the event. Metering
values provided in the events are secondary, and voltage values correspond to phase-to-ground voltage.
Ready LED ON
Date: 07/Nov/2004 St:ON
Time: 16:11:08.035 (1/479)
Intro: Meters.
To access the metering values in the moment of the event, the user must press the enter/shuttle key. A new metering
screen is displayed, containing the primary metering values in the snapshot event, such as:
Once inside the Metering screen, a new legend is shown for each event (Intro or ESC: Prev. U-D (L-R: Scroll); press ESC
or the shuttle key to return to the Event Details screen, and press the up-down key or rotate the shuttle key to access
all the metering values contained in the metering screen of the selected event.
ESC: Prev.
If the user presses the ESC key from the event detail screen, the system returns to the all events screen.
: Scroll.
Pressing the up-down key or rotating the shuttle key left (L) or right (R) moves among all the events contained in the all
events screen, allowing a preview of the details for each of them.
<AT>
When this option is selected, the system marks the event where the cursor is located. A relative time stamp is
performed, in such a way that the selected event, marked with an asterisk (*) between the time and the event name is
set with a relative time of 00:00:00:000 on the top line of the event screen, together with its relative index, and the rest
of events in the screen shows a date/time that relates to the marked event. This operation mode allows a quick
inspection of the relative time passed between several events, which is very useful for analyzing events in the field.
The corresponding legend to this relative event-marking screen is as follows:
Esc: Out At.Enter: Tag event.
Esc: Out At.
The relative event marking is eliminated and the system returns to the general events screen.
Enter: Tag event.
If the user places the cursor on a different event by pressing the up-down key or rotating the shuttle key left or
right, pressing the enter/shuttle key changes the relative mark to that new event.
First line shows the relative and total number of alarms existing in that screen. The relative number refers to the
alarm on which the cursor is located, and the total number refers to the total amount of alarms available. The second
line on this screen shows an index that indicates the number of the configured control event that corresponds to the
displayed alarm, followed by the alarm text configured in the Control Events menu inside the Relay Configuration
option (Setpoint > Relay Configuration > Control Events).
IO Card.
Type: 2, Nº IN 8, Nº OUT 8
>F<
G
H
J
0 CC1 8 Va COIL1
1 CC2 9 Vb COIL1
2 CC3 10 Va COIL2
3 CC4 11 Vb COIL2
4 CC5 12 Isense1
5 CC6 13 Isense1
6 CC7 14 SUP21
7 CC8 15 SUP22
Esc: Prev.
Returns to the general I/O screen
Enter: Menu.
Provides access to the I/O menu (next, view, test input, test output).
: Chg Card
Pressing the up-down key or Moving the shuttle key to the left or right provides access to the status of inputs/
outputs for the different boards available in the relay.
<TEST INPUT>
This option allows testing the input activation (in emulation mode). The displayed screen is similar to the viewing
screen, but in this case the user can operate the different relay inputs.
This screen shows the Input name lit up, showing that this is an Input emulation mode.
The first relay input appears blinking and between brackets; the user can select a different input by pressing up-down
key or rotating the enter/shuttle key. When the shuttle key is pressed, the selected input is activated. Navigation
through this screen is indicated by the following legend:
Esc: Exit Text. Enter: Chg Input.
<TEST OUTPUT>
This option allows testing the output activation in emulation mode. The displayed screen is similar to the viewing
screen, but in this case the user can operate the different relay contact outputs to test the wiring.
This screen shows the Output name lit up, showing that this is an output emulation mode.
The first relay output appears blinking and between brackets; the user can select a different output by pressing the
up-down key or rotating the shuttle key. When the enter/shuttle key is pressed, the selected output is activated.
Navigation through this screen is indicated by the following legend:
Esc: Exit Text. Enter: Chg Output.
Esc: Exit Text.
The ESC option returns to the general I/O board menu.
Enter: Chg Output.
Pressing the enter/shuttle key on the blinking output, this output is activated in emulation mode.
Note: Output emulation can be executed through the TEST OUTPUT tool on the graphic display, and also
through communications using EnerVista 650 Setup software for all F650 models.
: Chg Card
Pressing the up-down key or rotating the shuttle key allows to change the selected I/O board in the main I/O screen.
Unlike the case of Snapshot events, in this screen the highest index corresponds to the most recent event. The
information provided is the control event index, the text that has been associated with the event when configured, its
status, active (ON) or inactive (OFF), and its date and time.
4.3.4 Alarms
The alarms screen provides access to alarms configured in the relay. As in the case of snapshot events and control
events, this screen allows only to view the alarms, but not to acknowledge them.
4.3.5 Oscillography
The oscillography screen allows obtaining from the relay available oscillography records in that moment.
This screen includes two windows. The first window shows oscillography records available in the relay, identified by
an index, being the highest index the most recent record (oscillography record No 6 in the example below).
Chapter 5: Setpoints
SETPOINTS
5.1 Overview
5.1.1 Setpoint main menu
Table 5-1: Setpoint main menu in EnerVista 650 Setup software:
Product Setup
Communication settings
Serial Ports
Network (Ethernet)
ModBus Protocol
DNP3 Slave (Available for standard and
IEC61850 models, not available for IEC
870-5-103 models)
IEC 870-5-104 (Available for standard and
IEC61850 models, not available for IEC
870-5-103 models)
SNTP
Procome (Available for Procome models
only)
IEC 870-5-103 (Available for IEC 870-5-
103 models only)
PTP 1588 (Available from V7.00)
Routing (Available from V7.00)
ModBus User Map
Fault Report
Oscillography
Data Logger
Demand
Time Settings
System Setup
General settings
Flex Curves
Breaker
Breaker Settings
Breaker Maintenance
Switchgear
Miscellaneous Settings
Protection Elements
Phase Current
Phase TOC High
Phase TOC Low
Phase IOC High
Phase IOC Low
Phase Directional
Thermal Model
Neutral Current
Neutral TOC
Neutral IOC
Neutral Directional
Ground Current
Ground TOC
Ground IOC
Ground Directional
Sensitive Ground Current.
Sensitive Ground TOC
Sensitive Ground IOC
Isolated Ground IOC
Sensitive Ground Directional
Negative Sequence Current
Negative Sequence TOC
voltage Elements
Phase UV
Phase OV
Neutral OV High
Neutral OV Low
Negative Sequence OV
Auxiliary OV
Auxiliary UV
Power
Forward Power
Directional Power
Watt Gnd Flt High
Watt Gnd Flt Low
Control Elements
Setting Group
Underfrequency
Overfrequency
Synchrocheck
Autoreclose
Breaker Failure.
VT Fuse Failure.
Broken Conductor
Locked Rotor
Pulse Counters
Analog Comparator
Frequency rate of change
Load Encroachment
Max. Number of Starts
Digital Counters
Cold Load Pickup
Input/Outputs
Contact I/O
Board F
Board G
Board H
Board J
Force Outputs.
Remote Comms (Available for IEC61850
models only).
Virtual Inputs
For firmware versions 7.00 or higher; the Network settings are the Ethernet communication parameters for Port A,
Port B and Port E. Depending on the order code, up to three different Ethernet addresses can be used, The ModBus
Slave address used by Ethernet ports is the one set for COM2.
Table 5-3: Network settings for firmware version 7.00 and above
PRODUCT SETUP > COMMUNICATION SETTINGS > NETWORK (ETHERNET) NETWORK (ETHERNET)A
> NETWORK (ETHERNET)B > NETWORK (ETHERNET) E > REDUNDANCY
Name Default Value Step Range User Value
IP Address Oct1 0 N/A [0 : 255]
IP Address Oct2 0 N/A [0 : 255]
IP Address Oct3 0 N/A [0 : 255]
IP Address Oct4 0 N/A [0 : 255]
Netmask Oct1 0 N/A [0 : 255]
Netmask Oct2 0 N/A [0 : 255]
Netmask Oct3 0 N/A [0 : 255]
Netmask Oct4 0 N/A [0 : 255]
IP ADDRESS: This setting sets the ports IPv4 address in standard IPV4 format. Note that this setting is only valid on
port B if port A’s REDUNDANCY is set to INDEPENDENT.
NETMASK: This setting sets the ports IPv4 subnet mask in standard IPV4 format. Note that this setting is only valid
on port B if port A’s REDUNDANCY is set to INDEPENDENT.
PRODUCT SETUP > COMMUNICATION SETTINGS > NETWORK (ETHERNET) > REDUNDANCY
Name Default Value Step Range
REDUNDANCY MODE INDEPENDENT N/A [INDEPENDENT; LLA; PRP; HSR; RSTP;
DAISY_CHAIN]
LLA Priority DISABLED N/A [ENABLED; DISABLED]
LLA Timeout 5000 N/A [0 : 600000]
RSTP BRIDGE PRIORITY 32768 N/A [0 : 61440]
RSTP PORT A PRIORITY 128 N/A [0 : 240]
RSTP PORT A PATHCOST 200000 N/A [0 : 2000000]
RSTP PORT B PRIORITY 128 N/A [0 : 240]
RSTP PORT B PATHCOST 200000 N/A [0 : 2000000]
REDUNDANCY MODE: This setting is available only if the hardware has multiple ports. The setting determines if ports A
and B operate in redundant or independent mode. Different options are listed below:
-Independent: In non-redundant mode, port A and B operate independently with their own MAC, IP address,
mask and gateway.
NOTE: When using more than one Ethernet port, each port must be configured to belong to a different network,
otherwise communications becomes unpredictable.
NOTE 2: When non-redundant mode is selected, MAC address assigned to port A is the same as MAC address
assigned to port E but increased in one unit and MAC address assigned to port B is the same as MAC address
assigned to port A but increased in one unit.
E.g (MAC_portE: 00AFF40A24DA, MAC_portA:00AFF40A24DB, MAC_portB: 00AFF40A24DC)
-LLA (Link Loss) operation: The operation of ports A and B are as follows:
Ports A and B use port A’s MAC and IP address settings while port B is in standby mode in that it does not
actively communicate on the Ethernet network but monitors its link.
-PRP (Parallel Redundancy Protocol): ports A and B use the same MAC (physical device) address and
combine information at the link layer. It is intended to only be used if the two ports are connected to separate
parallel LAN’s. In this mode of operation both ports cannot be connected to the same LAN. The receiving
devices process the first frame received and discard the duplicate through a link redundancy entity (LRE) or
similar service that operates below layer 2. Aside from LRE, PRP uses conventional Ethernet hardware but both
ports must know they are in PRP. Both ports of PRP devices operate with the same Internet Protocol (IP)
addresses for traffic that uses IP Management protocols such as Address Resolution Protocol (ARP).
-HSR (High-availability Seamless Redundancy): ports A and B use the same MAC (physical device) address
and combine information at the link layer. It is intended to work in a ring topology. In this mode of operation port
A is connected to the other device’s port B, and port B is connected to other device´s port A provided that ring
topology is respected. The receiving devices process the first frame received and discard the duplicate through
a link redundancy entity (LRE) or similar service that operates below layer 2. Aside from LRE, HSR uses
conventional Ethernet hardware but both ports must know they are in HSR. Both ports of HSR devices operate
with the same Internet Protocol (IP) addresses for traffic that uses IP Management protocols such as Address
Resolution Protocol (ARP).
-RSTP (Rapid Spanning Tree Protocol): ports A and B use the same MAC (physical device) address and can
operate with different network topologies. The device operates only with one IP address through these 2 ports
-Daisy Chain: ports A and B use the same MAC (physical device) address and operate by chaining one device
with the next one. Note that it is important not to create a loop in this topology. Both ends of the chain can be
connected to different networks. The device operates only with one IP address through these 2 ports.
NOTE 3: When LLA/PRP/HSR or PRR mode is selected, MAC addresses assigned to port A and B are the same
between them and a consecutive value of MAC address assigned to port E.
E.g (MAC_portE: 00AFF40A24DA, MAC_portA:00AFF40A24DB, MAC_portB: 00AFF40A24DB)
NOTE 4: When LLA/PRP/HSP/RSTP or DAISY CHAIN mode is selected, the IP configured at
Product Setup > Communication Settings > Network (Ethernet) > Network (Ethernet) A is the one used by both
ports (A and B) to communicate in these modes.
LLA PRIORITY: If this setting is set to enabled, the port A has the priority. If PORTA’s LLA detects a problem with
the link, communications is switched to Port B. Port B is, in effect, acting as a redundant or backup link to the
network for port A.
LLA TIMEOUT: This setting is active only when the LLA PRIORITY is set to ENABLED. When the link on primary
port is detected again after it fails, there is LLA TIMEOUT (ms) monitoring time for the health of the network. During
this time, the secondary port remains active. If primary network is healthy for more than LLA TIMEOUT value, the
switch over to primary port is automatic.
RSTP BRIDGE PRIORITY: Specifies the switch (bridge) priority value. This value is used along with the switch MAC
address to determine which switch in the network is the root device. Lower values mean higher priority. The value
ranges from 0 to 65535, with a default of 32768.
RSTP PORTA PRIORITY: This is to determine which ports are used for forwarding. Lower the number means higher
priority. Value ranges from 0 to 255. Default is 128.
RSTP PORTA PATHCOST: This is the assigned port cost value used for the switch to determine the forwarding
points. Values range from 1 to 2000000. The lower the value, the lower the cost and hence the preferred route.
RSTP PORTB PRIORITY: This is to determine which ports are used for forwarding. Lower the number means higher
priority. Value ranges from 0 to 255. Default is 128.
RSTP PORTB PATHCOST: This is the assigned port cost value used for the switch to determine the forwarding
points. Values range from 1 to 2000000. The lower the value, the lower the cost and hence the preferred route.
For this setting change to take effect, a reboot is required.
5.2.1.6 SNTP
The F650 supports the Simple Network Time Protocol specified in RFC-2030. With SNTP, the F650 can obtain the
clock time over an Ethernet network. The F650 acts as an SNTP client to receive time values from an SNTP/NTP
server, usually a dedicated product using a GPS receiver to provide an accurate time. Three different modes of
SNTP operation are supported. These modes are unicast, broadcast and anycast.
If SNTP functionality is enabled at the same time as an IRIG-B source is connected to the F650, the IRIG-B signal
provides the time value to the F650 clock for as long as a valid signal is present. If the IRIG-B signal is removed, the
time obtained from the SNTP server is used.
To use SNTP in unicast mode, Server IP Oct1...4 must be set to the SNTP/NTP server IP address. Once this
address is set and the Function setting is “UNICAST”, the F650 attempts to obtain time values from the SNTP/NTP
server. Since many time values are obtained and averaged, it generally takes forty seconds until the F650 clock is
synchronized with the SNTP/NTP server. It may take up to one minute for the F650 to signal an SNTP FAIL state if
the server is offline.
To use SNTP in broadcast mode, set the Function setting to “BROADCAST”. The F650 then listens to SNTP
messages sent to the “all ones” broadcast address for the subnet. The F650 waits up to eighteen minutes (>1024
seconds) without receiving an SNTP broadcast message before signalling an SNTP FAIL state.
To use SNTP in anycast mode, set the Function setting to “ANYCAST”. Anycast mode is designed for use with a set
of cooperating servers whose addresses are not known beforehand by the client. The F650 sends a request to a
multicast group address assigned by IANA for NTP protocol. This address is 224.0.1.1 and a group of SNTP/NTP
servers listens to it. Upon receiving a request each server sends a unicast response to the SNTP/NTP client. The
F650 relay binds to the first unicast message received from any server. Then it continues operating with SNTP/NTP
server in unicast mode. Any further responses from other SNTP/NTP servers are ignored. In unicast mode of
operation the chosen time server can go offline, in that case it takes about one minute for the F650 to signal an
SNTP FAIL state and to switch again to anycast mode to try to find another time server. In anycast mode the F650
tries to send multicast messages up to five minutes before signalling an SNTP FAIL state.
The F650 relay does not support the multicast mode of SNTP functionality.
For firmware version 7.20 or above, F650 shall accept time synchronization from up to two different SNTP servers. In
order to define number of SNTP servers to be used, different settings for each SNTP server must be configured in
the F650. SNTP1 or/and SNTP2 tab settings shall be configured.
If only one SNTP server is used to synchronize the relay, SNTP1 tab settings shall be filled with its corresponding
settings. If two SNTP servers are used, SNTP1 and SNTP2 tab shall be filled as follow:
"SNTP1 tab shall contain settings of main SNTP server.
"SNTP2 tab shall contain settings of back-up SNTP server.
If two SNTP servers are configured, F650 operation mode is described as follows:
When NONE is selected in the comm port setting the protocol is not enabled. The com1 selection enables Procome
for the com1 (remote) serial port.
Slave Number:is the Procome slave number.
Baud rate and parity for COM1 must be set in the Setpoint > Communications > Serial Ports menu.
DNP protocol is available for standard and IEC61850 models but it is not available IEC 60870-5-103 models.
If COMM Port is set to NONE, IEC 870-5-103 communication protocol is not available.
If the user sets a value different from 0 in the Synchronization Timeout setting, when this timer expires without
receiving a synchronization message, the Invalid bit is set in the time stamp of a time-tagged message.
PTP FUNCTION
While this port setting is selected to disabled, PTP is disabled on this port. The relay does not generate or listen to
PTP messages on this port.
In unusual cases where the length of the link is different in different directions, this setting should be set to the
number of nanoseconds the Ethernet propagation delay to the relay is longer than the mean of path propagation
delays to and from the relay. For instance, if it is known say from the physical length of the fibers and the propagation
speed in the fibers that the delay from the relay to the Ethernet switch it is connected to is 9 000 ns and the that the
delay from the switch to the relay is 11 000 ns, then the mean delay is 10 000 ns, and the path delay asymmetry is
+1 000 ns.
PTP VLAN ID
This setting selects the value of the ID field in the 802.1Q VLAN tag in request messages issued by the relay’s peer
delay mechanism. It is provided in compliance with PP. As these messages have a destination address that
indicates they are not to be bridged, their VLAN ID serves no function, and so may be left at its default value.
Depending on the characteristics of the device to which the relay is directly linked, VLAN ID may have no effect.
This setting applies to all of the relay’s PTP capable ports.
PTP EPOCH
This setting sets the reference point from which time is measured.
5.2.1.10 Routing
A default route and a maximum number of 6 static routes may be configured. The default route is used as the last
choice, if no other route towards a given destination is found.
The redundancy communications comes with the capability of setting a number of static routes and one default route, which
is used instead of default gateway.
Default RT GWY:
This setting sets the gateway of the default route to be used by IP traffic sent from the relay, if no other route towards a
given IP destination is found.
Note that this setting is only valid on port B if port REDUNDANCY is set to INDEPENDENT.
Static RTX IP: This setting sets the destination IPv4 route.
Static RTX MASK: This setting sets the IP mask associated with the route.
Static RTX GWY: This setting sets the gateway to reach the destination IP route.
Important Notes:
1. Host routes are not supported at present.
2. The route mask has IPv4 mask format. In binary this should be a set of contiguous bits of 1 from left to right,
followed by one or more contiguous bits of 0.
3. The route destination and mask must match.
• This can be verified by checking that RtDestination & RtMask == RtDestination
• Example of good configuration: RtDestination= 10.1.1.0; Rt Mask= 255.255.255.0
• Example of bad configuration: RtDestination = 10.1.1.1; Rt Mask= 255.255.255.0
4) The route destination must not be a connected network.
5) The route gateway must be on a connected network. This rule applies to the gateway address of the default route as
well.
Function permission (Function): Enabling this setting allows to create a fault report
when the FAULT REPORT TRIGG is activated.
Positive sequence impedance module (Pos Seq Module): Value, in ohms, of the line positive sequence
impedance module.
Positive sequence impedance Angle (Pos Seq Angle): Value, in degrees, of the line positive sequence
angle.
Zero sequence impedance module (Zero Seq Module): Value, in ohms, of the line zero sequence
impedance module.
Zero sequence impedance Angle (Zero Seq Angle): Value, in degrees, of the line zero sequence angle.
Line Length: The metering element can be kilometers or miles.
Show Fault On HMI: This setting enables or disables the option to display
faults on the Relay HMI.
WARNING
If only two phase CTs are connected to the relay, several protection elements are affected and could
experience unexpected behaviors. Also several measurements are affected and accuracy will not be met.
Proper behavior of all protection elements and measurements accuracy cannot be guaranteed if any of
these settings is selected: CTA+CTB, CTA+CTC, CTB+CTC.
States associated with the fault report (Actual > Status > fRecords Status > Fault Reports), are shown on Table
5-7: Fault report states
Table 5-7: Fault report states
FAULT REPORT STATES
FAULT REPORT TRIGG
CLEAR FAULT REPORTS
FAULT DATE
FAULT TYPE
FAULT LOCATION
FAULT REPORT TRIGG: The activation of this state initiates the calculation of the fault location and the
generation of the corresponding report.
CLEAR FAULT REPORTS: The activation of this state produces the removal of all faults stored in the relay.
Additionally, all active faults on the HMI display are acknowledged. This signal is
programmed at “Setpoint > Relay Configuration > Protection Elements”.
FAULT DATE: Date and time of the last fault.
FAULT TYPE: Type of the last fault produced (3PHASE, AG, BG, CG, AB, ABG, BC, BCG, CA, CAG,
NAF). NAF indicates that the type of fault has not been calculated.
FAULT LOCATION: Calculated distance to the last fault (the metering element is the same used for setting
the line length).
FAULT REPORT NUMBER: Number of the fault report file saved in the relay’s non-volatile memory, associated
with the last fault produced.
The 16 digital channels and the oscillography trigger signal are programmable using the EnerVista 650 Setup
software at Setpoint > Relay configuration > Oscillography. Each digital channel can be associated with a single
status or to a logic status. In this last case, the logic must be configured using the PLC Editor tool, at Setpoint >
Logic Configuration inside EnerVista 650 Setup. The oscillography trigger signal can be a single status or a
configured logic. The relay’s default configuration associates the oscillography trigger to Virtual Output 83, which
corresponds to the logic associated with the general trip of protection elements.
Function Permission (Function):Enabling this setting allows to create an oscillography record when the
“TRIGGER OSCILLO” signal is activated.
Trigger Position: This setting defines the prefault data (in percentage) stored every time a new
oscillo is produced.
Samples/Cycle: This setting defines the number of samples per cycle stored in each oscillography
record.
The overall maximum samples capacity is allocated for 27594 samples. The size of each oscillography file depends
on the configured number of oscillographies and is evenly distributed based on the maximum samples value using
these formulas:
After a change in oscillography settings all oscillography files stored on the flash memory are
NOTICE erased.
EXAMPLE
For a Max. Number Osc. of 4, each record stores 27594 / 4 = 6898 samples per stored oscillo.
If we set the Samples /Cycle setpoint to 64 samples per cycle, each record stores up to 6898 / 64 = 107.78 signal
cycles. This value expressed in terms of time is:
For 50 Hz: 204.79 cycles x 20 ms/cycle = 4095.8 ms.
For 60 Hz: 204.79 cycles x 16.67 ms/cycle = 3413 ms.
OSCILLOGRAPHY STATES
OSC DIG CHANNEL 1
OSC DIG CHANNEL 2
OSC DIG CHANNEL 3
OSC DIG CHANNEL 4
OSC DIG CHANNEL 5
OSC DIG CHANNEL 6
OSC DIG CHANNEL 7
OSC DIG CHANNEL 8
OSC DIG CHANNEL 9
OSC DIG CHANNEL 10
OSC DIG CHANNEL 11
OSC DIG CHANNEL 12
OSC DIG CHANNEL 13
OSC DIG CHANNEL 14
OSC DIG CHANNEL 15
OSC DIG CHANNEL 16
OSCILLO TRIGGER
NUMBER OF TRIGGERS
CYCLES PER RECORD
AVAILABLE RECORDS
OSC DIGITAL CHANNEL XX: These states are configured at “Setpoint > Relay configuration >
Oscillography”. Each of these states can be associated with a protection state or
to a virtual output. Each oscillography record reflects the changes experienced by
this state during the record.
OSCILLO TRIGGER: The activation of this state produces the oscillography record capture. Each
record uses a percentage of its capacity to store prefault information. This
percentage is selected in the Trigger Position setting, and the rest of the record’s
capacity stores post-fault information.
NUMBER OF TRIGGERS: This is the number of the most recent oscillography record stored in the relay. The
record is stored in COMTRADE format. The range is 0 to 999.
CYCLES PER RECORD: This state displays the number of cycles that are stored in each oscillography
record. Although the number of cycles can be a decimal number, the record
represents only the integer part.
AVAILABLE RECORDS: The range is 0 to 20.
Data Logger analog channels X Data Logger Chnl X None N/A [1 to 16]
OLDEST SAMPLE TIME: The Date/time of the oldest state with 6 characters. This is the time that
corresponds to the oldest sample. This value remains constant until the available
memory capacity is exceeded. Afterwards, this value changes according to the
sampling rate (Data Logger Rate).
NEWEST SAMPLE TIME: The Date/time of the newest state with 6 characters. This is the time when the
most recent sample was taken. This value is updated according to the sample
rate selected.
If no channel has been selected, these settings do not change.
DATA LOGGER CHANNELS: This state shows the number of channels selected.
DATA LOGGER DAYS: This state shows the number of days that can be stored. It depends on the Data
Logger Rate setting, and on the number of channels selected.
File Retrieval
Data logger files can be retrieved using the EnerVista 650 Setup software, or the web server at “http:\\relay IP
address”.
For obtaining the data logger files using the EnerVista 650 Setup software, the user must access “Actual > Records
> Data Logger”. The top of the window shows the date when the oldest sample was taken, and then the date when
the newest sample was taken.
This screen shows the measurements stored for the different channels through the time.
Clicking on the “Download” button, all the information contained in the file can be read.
Clicking on the “Save” button, the data logger files (*.DAT, *.CFG) are retrieved in COMTRADE format, and saved by
default in the folder “...\EnerVista 650 Setup\files\osc”, using “DLGxxx.DAT”, “DLGxxx.CFG” names, where xxx is the
corresponding record number.
For firmware versions below 7.70, datalogger record retrieval uses Ethernet communications ports (ftp, tftp). For
firmware versions 7.70 or above, datalogger record retrieval uses serial (ModBus RTU) or Ethernet (tftp)
communication ports
File Format
Data logger information is made of two text files: configuration file (datalogger.cfg), and data file (datalogger.dat).
*Note: The step depends on the selected “Primary Meter Units” in System Setup > General Settings (A_V; KA_KV)
Different integration methods can be selected to calculate current and power values.
Calculated demand values are as follows:
Table 5-9: Demand calculated values
DEMAND CALCULATED VALUES
DEMAND IA DEMAND IG DEMAND W
DEMAND IA MAX DEMAND IG MAX DEMAND W MAX
DEMAND IA DATE DEMAND IG DATE DEMAND W DATE
DEMAND IB DEMAND ISG DEMAND VAR PWR
DEMAND IB MAX DEMAND ISG MAX DEMAND VAR MAX
DEMAND IB DATE DEMAND ISG DATE DEMAND VAR DATE
DEMAND IC DEMAND I2 DEMAND VA PWR
DEMAND IC MAX DEMAND I2 MAX DEMAND VA MAX
DEMAND IC DATE DEMAND I2 DATE DEMAND VA DATE
DEMAND W MIN DEMAND VAR MIN DEMAND VA MIN
The relay measures current demanded on each phase, ground and sensitive ground, negative sequence and three-
phase demand for real, reactive and apparent power. Current and Power methods can be chosen separately.
Settings are provided to disable certain measuring techniques. These techniques are used by many utilities for
statistical or control purposes.
d (t ) =D(1 − e−Kt )
Where:
D Input signal (constant).
d(t) Demand value after applying the input value during time t (in minutes)
Figure 5-1: Response to different demand methods shows the behavior of the demand, depending on the Selected
setting for demand calculation.
1,2
0,8
0,6
Input 0,4
0,2
0
0 5 10 15 20 25 30
-0,2
Time (minutes)
1,2
0,8
Demand %
0,6
0,4
0,2
0
0 5 10 15 20 25 30
-0,2
Time (minutes)
1,2
0,8
Demand %
0,6
0,4
0,2
0
0 5 10 15 20 25 30
-0,2
Time (minutes)
Block interval
1,2
0,8
Demand %
0,6
0,4
0,2
0
0 5 10 15 20 25 3
-0,2
Time (minutes)
Rolling demand
*Note: The step depends on the selected “Primary Meter Units” in System Setup > General Settings (A_V; KA_KV)
Demand measurements for power values are as follows (Y being the power considered in each case):
DEMAND Y This is the demanded value every minute or every integration period, depending on
the selected settings
DEMAND Y MAX Demand maximeter; it stores the maximum demand value until a demand reset is
issued.
DEMAND Y MIN Demand minimeter; it stores the minimum demand value until a demand reset is
issued.
DEMAND Y DATE Date of the maximum demand value.
The maximum or minimum demanded values are stored in non-volatile memory. These are not cleared when the
relay is turned off. When the relay is turned on again, the values are updated.
States associated with the demand (“Actual > Status > Records Status > Demand”) are the following:
Besides the previously considered demand measures, two states are used for demand control:
DEMAND TRIGGER INPBit type state, Programmable at “Setpoint > Relay Configuration > Protection
Elements” in the EnerVista 650 Setup software. This signal is used by the Block Interval
demand method.
DEMAND RESET INP Bit type state, programmable at “Setpoint > Relay Configuration > Protection
Elements” in the EnerVista 650 Setup software. When this bit is activated, the demand
measures are reset. All stored values are reset to zero (for demand dates, this value
represents January 1st, 2000).
When there is no SNTP protocol enabled, IRIG-B protocol is not set to UTC Time or IEEE1588 synchronization, the
TIME SETTINGS are not used in the Real Time Clock but are still used to calculate the UTC Time (i.e., for the
IEC61850 protocol), but its behavior is not assumed correct in several critical hour changes because of Daylight
Savings Time getting effective. In these configuration cases, it is recommended to disable Daylight Savings Time.
IRIG-B FUNCTION:
Setting for enable or disable the IRIG-B protocol
The F650 is capable of receiving a time reference from several time sources in addition to its own internal clock for
the purpose of time stamping events, transient recorders and other occurrences within the relay. The accuracy of the
time stamp is based on the time reference that is used. The F650 supports an internal clock, SNTP, IRIG-B and 1588
as potential time references.
Regarding the PTP, F650 acts as an ordinary clock, with only Sync and Pdelay_Req messages.
Note:
Synchronization by IEC103, DNP, Modbus and IEC104 is not going to be issued if there is a synch source from IRIG-B,
SNTP or PTP.
This section shows the settings related to the system setup definition.
The system rated voltage is used as reference by the voltage restraint in the phase timed overcurrent element.
The Frequency reference marks the voltage channel to which the system Frequency is measured.
The auxiliary voltage setting can be selected between VN and VX.
VN means that all elements using neutral voltage take the value directly from the fourth voltage input.
VX means that all elements using neutral voltage take the value calculated from phase voltages.
o Voltage:
• Auxiliary OV (59X)
• Voltage Unbalance (60V)
• Phase UV (27)
• Neutral OV High (59NH)
• Neutral OV Low (59NL)
• Neg Seq OV (47)
• Auxiliary UV (27X)
• Phase OV (59)
o Power:
• Forward Power (32FP)
• Directional Power (32DIR)
• Watt Gnd Flt Low (32NL)
• Watt Gnd Flt High (32NH)
o Frequency:
• Underfrequency (81U)
• Overfrequency (81O)
• Frequency Rate of Change (81df/dt)
o Misc:
• Broken Conductor (I1I2)
• Load Encroachment
• Rotor Blocked (48)
• Setting Groups
• Recloser (79)
• Oscillography
• Synchrocheck (25)
• Fault Locator
• Max. number of starts (66)
• Fuse Failure (VTFF)
• Data Logger
• Comparator
• Switchgear
• Breaker
When the Out of Service status goes to ON, or the setting has been changed to Enabled, the ready LED changes to
red. Be careful if the ready LED is linked to an output, because the output will not change its state. To set an output
to the ready state, see the factory default Logic & Configuration. Take notice that VO_000 is set to the output instead
of VO_099
SETTING: LOGIC:
START Relay Out Relay Out
Disabled Disabled
Of Service Of Service
Enabled Enabled
Ready
LED OFF
Definitions
The value is defined as:
• OFF: The operator is able to change the operations from local to remote or OFF.
• ON: The operator is not able to change the operations from local to remote or OFF.
Settings
The unit is set by the HMI and by 650PC software as it is shown in the following figure.
The definition of the curve points can be introduced directly in the Flex Curve settings menu. Alternatively they can
be created using the graphical tool provided by clicking Edit Curve in the Flex curves menu in EnerVista 650 Setup.
In the user curve edit screen (see Figure 5-2: FlexCurves edition), a base curve can be selected, from the Standard
Curves menu. This curve is used as a template to create the user curve. Once the standard curve is viewed, it is
possible to make the user curve (operate, reset or both) reconcile the standard curve, using the Flex curve > set
flex curve from the standard curve, and then modifying any of the points by editing in the table the corresponding
value.
The user can also view a different curve model to the one the FlexCurve has been adapted to, and compare both
models to adopt the most appropriate values in each case. If once the user curve has been configured, the user
wants to store the information, the “Flex Curve > Exit with Data” menu must be selected. If the results are not to be
saved, the Exit without Data option must be selected. Now, calculated points must be saved in the Flex Curve using
the “Store” option.
(KI)2t integration time (KI)2t Integ. Time 0.03 0.01s [0.03 : 0.25]
Maximum number of openings Maximum Openings 9999 1 [0 : 9999]
Maximum Openings in one hour Max.Openings 1 hour 40 1 [1 : 60]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED –
ENABLED]
The interrupted current limit setting, fixes the Maximum breaker capacity (this value is set depending on the
information provided by the breaker manufacturer); the relay incorporates a (KI)2t counter for each phase, when a
breaker opening occurs, the counter increases its value (in primary values). If the flowing current is lower than the
rated current, the relay takes the rated current value for its calculations. When the accumulated counter for each
phase reaches or exceeds the set value, the corresponding alarm signal is activated.
The purpose of this function is to provide closer information of the current status of the breaker’s internal contacts.
This is, in order to ensure appropriate breaker maintenance, and to decrease the risk of damage when the breaker
has suffered severe operations during a long time. Once the breaker has been operated, and the preventive
maintenance is in place, the accumulated I2t values and the number of operations are reset to zero.
(KI)2t Counter Phase C (KI)2t BKR Ph C Cnt 0.00 0.01 (KA)2 s [0.00 : 9999.99]
Openings counter BKR Openings Cnt 0 1 [0 : 9999]
Closings counter BKR Closings Cnt 0 1 [0 : 9999]
In this group of settings, the start values of the breaker Counters can be set.
These Counters allow the breaker Maintenance. They are used to accumulate the breaker aging produced by a trip
or a breaker opening. In order to incorporate the breaker’s history, in case of used breakers, the system allows
assigning an initial value to accumulated amperes, and to the number of opening and closing operations.
To supervise breaker aging, S(KI)2t accumulated values are calculated and stored for each phase in each opening.
If the rated current is not exceeded, as in the case of a manual opening command, without fault current, the relay
uses the rated current instead of the measured value.
(KI)2t value is accumulated and maintained in independent Counters for each phase. Counters can be accessed
through the local HMI as well as through the EnerVista 650 Setup software. The element incorporates a setting to
select the integration time ((KI)2t Integ. Time).
The signals associated with the opened or closed status of the breaker can be monitored at Actual > Status >
Breaker
Table 5-16: Breaker status
BREAKER STATUS DESCRIPTION
BREAKER OPEN Breaker in open position.
BREAKER CLOSED Breaker in close position
BREAKER UNDEFINED Breaker undefined
The signals associated with breaker maintenance can be monitored at Actual > Status > Records Status >
Breaker Maintenance, and they are as follows:
Table 5-17: Breaker maintenance status
BREAKER MAINTENANCE DESCRIPTION
2
(KI) t PHASE A ALARM This signal activates when the set value for phase A is exceeded.
(KI)2t PHASE B ALARM This signal activates when the set value for phase B is exceeded.
(KI)2t PHASE C ALARM This signal activates when the set value for phase C is exceeded.
BKR OPENINGS ALARM Relay total Number of Openings alarm
BKR OPEN 1 HOUR ALRM Relay total Number of Openings in one hour alarm
RESET (KI)2t COUNTERS (KI)2t Counters reset signal. This signal is configured at Setpoint > Relay Configuration >
Protection Elements, and it is used for resetting the (KI)2t counter through the corresponding
signal, command, digital input, etc.
RESET BKR COUNTERS Reset signal for the Opening and Closing Counters. This signal is configured at Setpoint > Relay
Configuration > Protection Elements, and it is used for resetting the breaker Opening and
closing counters.
BREAKER OPENINGS Number of Breaker openings
BREAKER CLOSINGS Number of Breaker closings
(KI)2t PHASE A Accumulated (KI)2t value for phase A ((KI)2t Counter for Phase A)
(KI)2t PHASE B Accumulated (KI)2t value for phase B ((KI)2t Counter for Phase B)
(KI)2t PHASE C Accumulated (KI)2t value for phase C ((KI)2t Counter for Phase C)
BKR OPENING TIME Maximum breaker Opening time. This signal is configured at Setpoint > Relay Configuration >
Switchgear in the number of switchgear corresponding to the breaker selection
BKR CLOSING TIME Maximum breaker Closing time. This signal is configured at Setpoint > Relay Configuration >
Switchgear in the number of switchgear corresponding to the breaker selection
BKR OPEN TIMING Exact time in opening the breaker
CURRENT ELEMENTS
Instantaneous overcurrent:
3 x PHASE IOC HIGH (50PH)
3 x PHASE IOC LOW (50PL)
3 x NEUTRAL IOC (50N)
3 x GROUND IOC (50G)
3 x SENSITIVE GROUND IOC (50SG)
3 x ISOLATED GROUND IOC (50IG)
Time delayed overcurrent:
3 x PHASE TOC HIGH (51PH)
3 x PHASE TOC LOW (51PL)
3 x NEUTRAL TOC (51N)
3 x GROUND TOC (51G)
3 x SENSITIVE GROUND TOC (51SG)
Negative sequence overcurrent:
3 x NEGATIVE SEQUENCE TOC (46P)
Thermal image:
3 x THERMAL MODEL (49P)
DIRECTIONAL ELEMENTS
3 x PHASE DIR (67P)
3 x NEUTRAL DIR (67N)
3 x GROUND DIR (67G)
3 x SENSITIVE GROUND DIR (67SG)
VOLTAGE ELEMENTS
Phase under/overvoltage
3 x PHASE UV (27P)
3 x PHASE OV (59P)
Zero sequence overvoltage
3 x NEUTRAL OV HIGH (59NH)
3 x NEUTRAL OV LOW (59NL)
Additional auxiliary under/overvoltage (for VX selection in auxiliary voltage)
3 x AUXILIARY OV (59X)
3 x AUXILIARY UV (27X)
Negative sequence overvoltage:
3 x NEGATIVE SEQUENCE OV (47P)
POWER
3 x FORWARD POWER (32FP)
3 x DIRECTIONAL POWER (32)
Note *1: For firmware version 7.20 or above, three extra underfrequency and overfrequency elements have been
added which gives a total of 6 underfrequency and 6 overfrequency elements.
F650 elements incorporate a flexible grouping capability for protection ELEMENTS. This means that protection
elements can be used in either one of the following modes:
The settings used for setting table management are located in Setpoint > Control Elements > Setting Group:
These activation signals for the different setting groups are configured using EnerVista 650 Setup at Setpoint >
Relay Configuration > Control Elements as shown in the figure. For firmware prior to 7.00, these signal are
located at Setpoint > Relay Configuration > Protection Elements
The example above uses three digital inputs to perform the table selection, but it is possible to use any other logic
signal in the relay.
In case of using digital inputs, the user can select the setting table activating these digital inputs (which can come
from the PLC, or from a different relay, or from an auxiliary switch, for adaptive protection). This selection of the
active group has priority over the setting. If several signals are active at the same time, the highest one is taken as
valid. For example, if selection signals for both groups 1 and 2 are active, the active table is number 2.
The time used in the table change is one PLC logic scan cycle (5 ms typical), allowing a fast adaptation to system
changes.
Another type of signals are block signals. These are internal relay signals that indicate which groups are active, and
which are blocked. For example, if the setting group function is enabled and setting group 1 has been set as active,
block signals from setting groups 2 and 3 are active, and the block signal that corresponds to group 1 is inactive
because that group is enabled.
Block signals are as follows:
GROUP 1 BLOCKED
GROUP 2 BLOCKED
GROUP 3 BLOCKED
All signals corresponding to setting Groups, both the activation and the block signals, are located in the Actual >
Status > Control Elements > Setting Groups menu.
CURRENT ELEMENTS
Instantaneous overcurrent:
3 x PHASE IOC HIGH (50PH)
3 x PHASE IOC LOW (50PL)
3 x NEUTRAL IOC (50N)
3 x GROUND IOC (50G)
DIRECTIONAL ELEMENTS
3 x PHASE DIR (67P)
3 x NEUTRAL DIR (67N)
3 x GROUND DIR (67G)
3 x SENSITIVE GROUND DIR (67SG)
VOLTAGE ELEMENTS
Phase under/overvoltage
3 x PHASE UV (27P)
3 x PHASE OV (59P)
Zero sequence overvoltage
3 x NEUTRAL OV HIGH (59NH)
3 x NEUTRAL OV LOW (59NL)
Additional auxiliary under/overvoltage (for VX selection in auxiliary voltage)
3 x AUXILIARY OV (59X)
3 x AUXILIARY UV (27X)
Negative sequence overvoltage:
3 x NEGATIVE SEQUENCE OV (47P)
POWER
3 x FORWARD POWER (32FP)
3 x DIRECTIONAL POWER (32)
3 x WATT GND FLT HIGH (32NH)
3 x WATT GND FLT LOW (32NL)
FREQUENCY ELEMENTS
6 x OVERFREQUENCY (81O)
6 x UNDERFREQUENCY (81U)
3 x FREQUENCY RATE OF CHANGE (81 df/dt)
MISCELLANEOUS
3 x BROKEN CONDUCTOR
3 x LOCKED ROTOR
3 x LOAD ENCROACHMENT
The F650 elements incorporate also the following control elements. These control elements are not affected by setting groups
and they are available in EnerVista 650 Setup at Setpoints > Control Elements
1 x SETTINGS GROUP
1 x SYNCHROCHECK(25)
1 x AUTORECLOSE (79)
1 x BREAKER FAILURE (50BF)
1 x VT FUSE FAILURE (VTFF)
8 x PULSE COUNTERS
8 x DIGITAL COUNTERS
20 x ANALOG COMPARATORS
1x MAX. NUMBERS OF STARTS
1 x COLD LOAD PICKUP
16 x PLC TIMER MASK
1x 60 CTS FAILURE
1x 2ND HRMC INHIBIT
As in previous firmware versions, F650 elements incorporate a flexible grouping capability for elements grouped in
protection elements section. However, two different working modes have been implemented for firmware version
7.5X and above
This means that protection elements can be used in either one of the following modes:
SETTING GROUP 1 SETTING GROUP 2 SETTING GROUP 3 SETTING GROUP 4 SETTING GROUP 5 SETTING GROUP 6
3x50PH 3x50PH 3x50PH 3x50PH 3x50PH 3x50PH
3x50PL 3x50PL 3x50PL 3x50PL 3x50PL 3x50PL
3x50N 3x50N 3x50N 3x50N 3x50N 3x50N
3x50G 3x50G 3x50G 3x50G 3x50G 3x50G
3x50SG 3x50SG 3x50SG 3x50SG 3x50SG 3x50SG
When this setting is DISABLED, the relay is working in single setting group mode. All protection elements that belong
to the group selected in the active groups setting are available and working at the same time if required.
If this setting is ENABLED, the relay is working in multiple setting groups mode. In this mode, all protection elements
of different setting groups are available to be activated. However, only protection elements of the Active Group
selected are real active ones. In this case, selection of active setting group can be modified through logic signals.
Active group: Possible values are 1, 2, 3, 4, 5 or 6.
This setting indicates which setting group is active by default. Default configuration value is 1.
• When this function is disabled, the Active Group value indicates which setting group of protection elements is
available, e.g if Active Group is GROUP 1, all protection elements under setting group 1 in SetPoint >
Protection Elements are available.
• When this function is enabled, the Active Group value indicates the active setting group when no group is
selected as the active one.
Snapshot events: Possible values are: [DISABLED – ENABLED]
If this setting is ENABLED, Snapshot events related to change of setting groups are reported.
Regarding changing between setting groups when working in multiple setting groups mode, the Relay incorporates
several signals associated with the Protection elements grouping in tables.
First, signals that indicate the group activation:
GROUP 1 ACT ON: This signal produces the activation of setting group 1
GROUP 2 ACT ON: This signal produces the activation of setting group 2
GROUP 3 ACT ON: This signal produces the activation of setting group 3
GROUP 4 ACT ON: This signal produces the activation of setting group 4
GROUP 5 ACT ON: This signal produces the activation of setting group 5
GROUP 6 ACT ON: This signal produces the activation of setting group 6
The instantaneous mode provides that, when the current value falls below the reset level, energy is immediately
reset to 0. This mode is used for coordinating with static devices, which behave in a similar way. In the Linear mode,
energy is reduced at a speed associated with the reset times curve (showed in the curve tables), trying to simulate
the behavior of electromechanical relays.
Where:
t = Operation time in seconds
Dial = multiplier setting
I = Input current
Itap = Current pickup value
A, B, p = constants defined by the standard
TRESET = reset time in seconds
tr = characteristic constant.
Table 5-21: Constants for IEEE curves
IEEE Curve Shape Name A B p tr
IEEE Extremely Inverse IEEE Ext Inv 28.2 0.1217 2.0000 29.1
IEEE Very Inverse IEEE Very Inv 19.61 0.491 2.0000 21.6
IEEE Inverse IEEE Mod Inv 0.0515 0.1140 0.0200 4.85
8.0 129.432 56.221 23.538 14.387 10.465 8.410 7.196 6.418 5.889 5.513
10.0 161.790 70.277 29.423 17.983 13.081 10.513 8.995 8.023 7.361 6.891
IEEE Inverse
0.5 3.220 1.902 1.216 0.973 0.844 0.763 0.706 0.663 0.630 0.603
1.0 6.439 3.803 2.432 1.946 1.688 1.526 1.412 1.327 1.260 1.207
2.0 12.878 7.606 4.864 3.892 3.377 3.051 2.823 2.653 2.521 2.414
4.0 25.756 15.213 9.729 7.783 6.753 6.102 5.647 5.307 5.041 4.827
6.0 38.634 22.819 14.593 11.675 10.130 9.153 8.470 7.960 7.562 7.241
8.0 51.512 30.426 19.458 15.567 13.507 12.204 11.294 10.614 10.083 9.654
10.0 64.390 38.032 24.322 19.458 16.883 15.255 14.117 13.267 12.604 12.068
Where:
t = Operation time in seconds
Dial = multiplying factor
I = Input current
Itap = Current pickup value
K, E = constants defined by the standard
TRESET = reset time in seconds (assuming 100% of power capacity and that the reset is activated)
tr = characteristic constant.
Where:
t = Operation time in seconds
Dial = multiplier setting
I = Input current
Itap = Current pickup value
A, B, C, D, E = predefined constants
TRESET = reset time in seconds
tr = characteristic constant.
0.5 0.578 0.375 0.266 0.221 0.196 0.180 0.168 0.160 0.154 0.148
1.0 1.155 0.749 0.532 0.443 0.392 0.360 0.337 0.320 0.307 0.297
2.0 2.310 1.499 1.064 0.885 0.784 0.719 0.674 0.640 0.614 0.594
4.0 4.621 2.997 2.128 1.770 1.569 1.439 1.348 1.280 1.229 1.188
6.0 6.931 4.496 3.192 2.656 2.353 2.158 2.022 1.921 1.843 1.781
8.0 9.242 5.995 4.256 3.541 3.138 2.878 2.695 2.561 2.457 2.375
10.0 11.552 7.494 5.320 4.426 3.922 3.597 3.369 3.201 3.072 2.969
where:
T = Operation time (in seconds).
Dial = Multiplying factor
I = Input current
Ipickup = Current pickup setting
A, B, C, D, E = Constants
Treset = Reset time (in seconds) assuming a 100% of power capacity and that the reset is activated
Tr = Characteristic constant
where:
t = Operation time in seconds
Dial = multiplier setting
I = Input current
Itap = Current pickup value
TRESET = reset time in seconds
Table 5-29: Tripping time in seconds for I2t curves
Dial Current (I/Itap)
1.5 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0
0.01 0.444 0.250 0.111 0.063 0.040 0.028 0.020 0.016 0.012 0.010
0.10 4.444 2.500 1.111 0.625 0.400 0.278 0.204 0.156 0.123 0.100
1.00 44.444 25.000 11.111 6.250 4.000 2.778 2.041 1.563 1.235 1.000
10.00 444.444 250.000 111.111 62.500 40.000 27.778 20.408 15.625 12.346 10.000
100.00 4444.444 2500.000 1111.111 625.000 400.000 277.778 204.082 156.250 123.457 100.000
600.00 26666.66 15000.00 6666.667 3750.000 2400.000 1666.667 1224.490 937.500 740.741 600.000
7 0
where:
T = Operation time (in seconds).
TDM = Multiplying factor
I = Input current
Ipickup = Pickup current
Treset = Reset time (in seconds) assuming a 100% of power capacity and that the reset is activated
The two first columns (40 points) correspond to the RESET curve. The other 4 columns, with 80 points in total,
correspond to the OPERATE curve. The reset characteristic values are between 0 and 0.98, and the operation
values are between 1.03 and 20.
The final curve is created by means of a linear interpolation from the points defined by the user. This is a separate
process for the RESET and the OPERATE curve.
The definition of these points is performed in a separate module from the relay, using a configuration program
included in the EnerVista 650 Setup, which incorporates a graphical environment for viewing the curve, thus making
it easy for the user to create it. This module can be accessed from the “Edit Curve” option in the FlexCurve menu, at
Setpoint > System Setup > Flex Curves.
The phase overcurrent element (51P) operates in a time period that depends on the applied current and on the set
curve. Possible outputs for the protection element logic are the pickup and tripping signals independent for each
phase, and the general element pickup and tripping signals.
Function: This setting allows enabling or disabling the corresponding directional element.
Input: The phase current input may be selected as fundamental phasor magnitude or total
waveform RMS magnitude as required by the application.
Pickup Level: This setting allows selecting the current level for the Phase Time Overcurrent element to
operate. The PICKUP setting of the element can be dynamically reduced by a VOLTAGE
RESTRAINT feature. In order to avoid undesired trips, pickup will occur at 1.03 times the
set value.
Curve: This setting allows to select the curve that want to be use to operate this element. If the
element Curve is set as Definite Time, then the TD Multiplier setting is used to define both
the Operation time and, in case of selecting Linear reset, the Reset time of the element.
TD Multiplier: This setting allows the curve to be shifted up or down on the time-current characteristic
curve. This allows configuration of the relay depending on network selectivity
Reset: The element reset can be selected between Instantaneous and Linear (timed according to
the corresponding equation).
Voltage Restraint: As mention above, the pickup current magnitude can be dynamically reduced depending
on the existing voltage value. This is done using the Voltage Restraint setting. The pickup
current level is proportional to the phase-to-phase voltage measured according to a
coefficient shown on Figure 5–5:.This is accomplished via the multipliers (Mvr)
corresponding to the phase-phase voltages of the voltage restraint characteristic curve; the
pickup level is calculated as ‘Mvr’ times the ‘Pickup’ setting. In the figure, Vpp is the phase-
to-phase voltage, and VT Nominal is the rated voltage set under General settings (refer to
section 5.3.1)
Snapshot Events: The snapshot event setting enables or disables the snapshot event generation for the
phase directional elements.
Phase time delayed overcurrent element is an independent Protection element that provides block and Operation
signals for each phase. Block signal status can be monitored through the relay HMI or using EnerVista 650 Setup at
Actual > Status > Protection > Protection Block and Operation Signal status at Actual > Status > Protection >
Phase Current
The element incorporates independent block inputs for each phase. Block signals indicate blocked elements by an
external block input. When a particular signal is activated, the element is blocked. These inputs can be configured
using EnerVista 650 setup at Setpoint > Relay Configuration > Protection elements
Table 5-32: Block signal for the phase time delayed overcurrent element
When the element is blocked, the tripping time counter is reset to 0. This feature allows the use of this input to
instantaneously reset the protection element timing
The following diagram shows the logic scheme followed by high range and low range time overcurrent elements (51PH and
51PL) in the following figure.
SETPOINT > PROTECTION ELEMENTS > SETPOINT GROUP X > Phase Current >
> Phase IOC High > Phase IOC High 1 > Phase IOC High 2 > Phase IOC High 3
> Phase IOC Low > Phase IOC Low 1 > Phase IOC Low 2 > Phase IOC Low 3
Setting Description Name Default Value Step Range
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Input type Input PHASOR(DFT) N/A [PHASOR – RMS]
Pickup level Pickup Level 30.00 0.01 A [0.05 : 160.00]
Trip time Trip Delay 0.00 0.01 s [0.00 : 900.00]
Reset time Reset Delay 0.00 0.01 s [0.00 : 900.00]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
The snapshot event setting enables or disables the snapshot event generation for these elements.
The following figure shows the logic scheme diagram for high range and low range Instantaneous overcurrent
elements (50PH, 50PL).
SETPOINT > PROTECTION ELEMENT > SETTING GROUP X > SETPOINT GROUP X > Phase Current > Phase Directional >
Phase Directional 1 > Phase Directional 2 > Phase Directional 3
Setting Description Name Default Value Step Range
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Maximum Torque Angle MTA 45º 1 Deg [-90 : +90]
Operation Direction Direction FORWARD N/A [FORWARD – REVERSE]
Block logic Block Logic PERMISSION N/A [BLOCK – PERMISSION]
Polarization voltage threshold Pol V Threshold 40 1V [0 : 300]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Voltage Memory Time Voltage Memory 0,00 s [0,00: 3,00]
time
Function: This setting allows enabling or disabling the corresponding directional element.
MTA: The MTA setting corresponds to the Torque angle, which is the rotation applied to
phase-to-phase crossed voltage.
Direction: This setting allows selecting the area for the directional element to operate, either
forward or reverse.
Block Logic: This setting allows selecting either permission or block, depending on the logic to
be applied upon expiration of voltage memory.
Polarization Voltage Threshold:This is the minimum voltage considered for the direction calculation. Under this
setting, memory voltage is used.
Snapshot Events: The snapshot event setting enables or disables the snapshot event generation for
the phase directional elements.
Voltage Memory Time: This is the time voltage memory is considered as valid and used for direction
calculation when polarization voltage collapses.
Phase directional element is an independent Protection element that provides block and Operation signals for each
phase. These signals can be monitored both through the relay HMI or using EnerVista 650 Setup at “Actual >
Status > Protection > Phase Current”
Table 5-33: Block and operation signals for the phase directional element
BLOCK AND OPERATION FOR 67P
PHASE DIR1 BLOCK A
PHASE DIR1 A OP
PHASE DIR1 BLOCK B
PHASE DIR1 B OP
PHASE DIR1 BLOCK C
PHASE DIR1 C OP
PHASE DIR2 BLOCK A
PHASE DIR2 A OP
PHASE DIR2 BLOCK B
PHASE DIR2 B OP
PHASE DIR2 BLOCK C
PHASE DIR2 C OP
PHASE DIR3 BLOCK A
PHASE DIR3 A OP
PHASE DIR3 BLOCK B
PHASE DIR3 B OP
PHASE DIR3 BLOCK C
PHASE DIR3 C OP
Signals provided by the directional element are, block and operation signals. Signals used to block overcurrent
elements are configured at Setpoint > Relay Configuration > Protection Elements.
Operation signals are active when operation and polarization magnitudes meet conditions given by the settings.
Block signals indicate blocked elements by an external block input or by polarization voltage loss after voltage
memorize time elapses. Using the “Block logic” setting, the user can select how the directional element responds in
case of a block. When the “Block” option is selected, the operational signal is not activated in a block condition.
When the “Permission” option is selected, the operation signal is activated in a block condition.
Figure 5-8: Overcurrent elements block configuration by the directional element shows the default configuration for
the phase overcurrent block input. When the “Block logic” setting is set as “Block”, this input is active in case of a
block in the directional element, avoiding any phase overcurrent trip.
When the “Block logic” setting is set as “Permission”, the phase overcurrent element is enabled to trip as the block
input is not active in case of polarization voltage memory expiration.
Directional elements can also be blocked with signals coming from other relays, PLCs, or through signals configured
in the relay PLC Editor (Logic configuration tool). The signal used in that case is PHASE DIR BLK INP. Figure 5-9:
Directional element block configuration by input shows an example of the default block configuration of directional
elements by digital input. There is one block signal per input for each setting group.
The following figure shows the logic scheme for the phase directional element.
Where,
t is the heating/cooling time constant.
I’ is the ratio current/pickup
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
The following figure shows the logic scheme for the neutral Instantaneous overcurrent element.
The Neutral directional element is an independent Protection element that provides Block and Operation signals.
These signals can be monitored both through the relay HMI or using EnerVista 650 Setup at “Actual > Status >
Protection > Neutral Current”
67N Block (NEUTRAL DIR BLOCK): It indicates that the element is blocked by digital input or because the Operation
magnitude (In current), or the Polarization magnitude (Vn voltage and/or Ip current) level is too low.
67N Operation (NEUTRAL DIR OP): It indicates that the directional element is giving permission, that the angle
relations between the operation magnitude and the polarization magnitude are met, according to the set conditions,
or in case of having selected Permission in the Block Logic setting, it indicates that the element allows operation
under block conditions.
Table 5-39: Signals for the neutral directional element
NEUTRAL DIRECTIONAL
NEUTRAL DIR1 BLOCK
NEUTRAL DIR1 OP
NEUTRAL DIR2 BLOCK
NEUTRAL DIR2 OP
NEUTRAL DIR3 BLOCK
NEUTRAL DIR3 OP
shows the operation of the zero sequence polarization, 3V0, in case of an AG fault. In this case, the polarization
magnitude 3V0 can be calculated from the three phase voltage values, or measured through the fourth voltage input
(Vx). In this last case, the voltage transformer must be wye connected, and the Auxiliary Voltage setting in General
settings must be configured as VX. The operation magnitude In, is calculated from the phase currents.
When Ip Polarization is selected, the Polarization magnitude is Ip, this current value measured at the fifth current
input (terminals B11-B12). This polarization current usually comes from a CT measuring the current flow from the
ground to the neutral of the neutral fault current source, which is usually a transformer. The direction is considered to
be Forward when the neutral current In is inside a ±90º arc at both sides of the polarization current. In any other
case, the direction is Reverse. If the polarization current is lower than 5 mA, the element output takes the value of
the Block Logic setting. See Figure 5-13: Voltage polarization.
Figure 5-13: Voltage polarization shows the Operation of the directional element for a Phase A to Ground fault,
where the Phase A current grows in magnitude and is delayed with respect to its voltage by an angle similar to the
protected line. Va voltage decreases or can even disappear if the fault is close and the fault resistance is very low.
-3V0
Fault Ia In
Cone 5º Maximum
-45º torque angle
IA
Forward
Vc Vb
3V0 = Va +Vb+Vc
To perform a directional comparison by current, the polarization magnitude used is the current measured at the relay
Ip input, terminals B11-B12, with input or “positive” in B11. This current is taken from the source (transformer or
generator) neutral grounding.
Direction is considered to be forward when the phase shift between both magnitudes is lower than 85º. If the angle is
higher than 85º, the fault is considered to be reverse.
The following table shows the element’s output signals management (block and permission) depending on the
polarization type setting.
Configuration of the required signals for blocking the neutral overcurrent elements from the signals provided by the
neutral directional elements is performed at Setpoint > Relay Configuration > Protection Elements using the
inverted operation signals to block the trip, as shown in the following example:
How to block neutral time overcurrent elements with neutral directional functions:
NEUTRAL TOC1 BLOCK = NOT (NEUTRAL DIR1 OP)
NEUTRAL TOC2 BLOCK = NOT (NEUTRAL DIR2 OP)
NEUTRAL TOC3 BLOCK = NOT (NEUTRAL DIR3 OP)
To block neutral instantaneous elements:
NEUTRAL IOC1 BLOCK = NOT (NEUTRAL DIR1 OP)
NEUTRAL IOC2 BLOCK = NOT (NEUTRAL DIR2 OP)
NEUTRAL IOC3 BLOCK = NOT (NEUTRAL DIR3 OP)
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
Operation of the Ground directional element 67G is similar to the operation of the neutral directional element 67N
(refer to section 5.4.4.3 Neutral directional element (67N)), with the exception that the operation magnitude here is
the ground current Ig (67G), measured from the input terminals B9-B10 instead of the Neutral current, In (67N),
calculated from the phase currents.
Polarization magnitudes can be, as in the case of 67N, Polarization voltage (3Vo), either calculated from the phase
voltages or measured from terminals A11-A12, or polarization current (Ip), measured from the fifth input transformer
terminals, Isg, terminals B11-B12.
The following table shows the used magnitudes in each of the Polarization possibilities:
The following table shows the management of the element output signals (block and permission) depending on the
Polarization Type setting.
The configuration of the signals required for blocking the Ground overcurrent elements from the signals provided by
the Ground directional element is made at Setpoint > Relay Configuration > Protection Elements using inverted
operation signals to block the trip.
For example, to block the ground time delayed elements:
GROUND TOC1 BLOCK = NOT (GROUND DIR1 OP)
GROUND TOC2 BLOCK = NOT (GROUND DIR2 OP)
GROUND TOC3 BLOCK = NOT (GROUND DIR3 OP)
To block the Ground Instantaneous elements:
GROUND IOC1 BLOCK = NOT (GROUND DIR1 OP)
GROUND IOC2 BLOCK = NOT (GROUND DIR2 OP)
GROUND IOC3 BLOCK = NOT (GROUND DIR3 OP)
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
Vn=3V0
Operation Area
Vh
Vl
Il Ih In=3I0
Figure 5-14: Operations characteristics, element 50IG
The relay settings for the Isolated Ground IOC elements are as follows:
Function: This setting determines whether the element is operative and can generate
pickup and trip events, which can be configured to close outputs, light up LEDs
or trigger oscillography.
Vh, VL, Ih, IL: Vn and In values that define the points in the operative area.
Operation time (Delay): This is the selectable period between the element pickup and trip, with a range
from 0 to 900 seconds in steps of 0,01 seconds.
Deviation time to Instantaneous (Time to inst): Time after the trip during which the elements become
instantaneous. It must be set to zero if the functionality is not required.
Snapshot Events: The snapshot event setting enables or disables the snapshot event generation
for this element.
OPERATION PRINCIPLES:
Operation of the isolated Ground element is based on the detection of a current that exceeds the setting, with neutral
voltage supervision (3V0). This allows very sensitive setting of the element, with a very low current level, ensuring
that small angle or ratio errors in the current transformers do not cause the relay to operate, as the neutral voltage
verified is higher than the one set.
Values for Ih, IL, Vh and VL, which define the relay operation area, are configurable. H magnitudes must be higher
than L magnitudes. The 50IG element can be supervised by directional element 67SG.
Using the relay input magnitudes In and Vn, if the point defined by (In, Vn) is inside the operation area and if the
directional element (if directional supervision is set) allows it, the element picks up and the set delay time starts
counting down. If a directional block appears during the countdown, the element is reset. After the set time the
element trips. Once tripped, the relay cannot be blocked by the directional element, and the trip remains while the
fault exists.
After the trip, the deviation time to instantaneous starts to run, so that all pickups produced during this time produce
an Instantaneous trip. This means that, if after a trip the breaker is reclosed and the fault persists or reappears, the
trip is instantaneous. If the user doesn’t want to use this function, then the Deviation Time to Instantaneous (Time
to inst) setting must be set to zero seconds. Once the time has expired, the element returns to its normal operation.
Sensitive ground directional element is an independent Protection element that provides block and Operation
signals. These signals can be monitored both through the relay HMI or using EnerVista 650 Setup at Actual >
Status > Protection > Sensitive Ground Current
67SG Block (SENS GND DIR1 BLOCK): It indicates that the element is blocked by digital input or because the
Operation magnitude (In current), or the Polarization magnitude (Vn voltage and/or Ip current) level is too low.
67SG Operation (SENS GND DIR1 OP): It indicates that the directional element is giving permission, the operation
magnitude and the polarization magnitude conditions are met, or in case of having selected Permission in the Block
Logic setting, it indicates that the element allows operation under block conditions.
Table 5-52: Sensitive ground directional signals
SENS GND DIRECTIONAL
SENS GND DIR1 BLOCK
SENS GND DIR1 OP
SENS GND DIR2 BLOCK
SENS GND DIR2 OP
SENS GND DIR3 BLOCK
SENS GND DIR3 OP
Configuration of the required signals for blocking the sensitive ground overcurrent elements from the signals
provided by the sensitive ground directional elements is performed at Setpoint > Relay Configuration > Protection
Elements. This is done using the inverted operation signals to block the trip, as shown in the following example:
For example, to block sensitive Ground time overcurrent elements, use the following signals:
SENS GND TOC1 BLOCK = NOT (SENS GND DIR1 OP)
SENS GND TOC2 BLOCK = NOT (SENS GND DIR2 OP)
SENS GND TOC3 BLOCK = NOT (SENS GND DIR3 OP)
To block Ground instantaneous elements:
SENS GND IOC1 BLOCK = NOT (SENS GND DIR1 OP)
SENS GND IOC2 BLOCK = NOT (SENS GND DIR2 OP)
SENS GND IOC3 BLOCK = NOT (SENS GND DIR3 OP)
To block isolated Ground elements:
ISOLATED GND1 BLK = NOT (SENS GND DIR1 OP)
ISOLATED GND2 BLK = NOT (SENS GND DIR2 OP)
ISOLATED GND3 BLK = NOT (SENS GND DIR3 OP)
The snapshot event setting enables or disables the snapshot event generation for this element.
Snapshot Events: The snapshot event setting enables or disables the snapshot event generation for
this element.
Notice that the neutral overvoltage element is not be available if a DELTA Connection is set in the Phase VT
Connection setting in General settings, and the fourth voltage transformer input is set to the busbar voltage for the
synchronism element (Vx in Auxiliary Voltage setting). This is because with this combination of settings it is not
possible to calculate the zero sequence component from the phase-to-phase voltage magnitudes.
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
The snapshot event setting enables or disables the snapshot event generation for this element.
P- P+
0
The snapshot event setting enables or disables the snapshot event generation for this element.
The F650 includes three 32FP elements. Each elements incorporates two stages, the first stage, less critical, is
intended to produce an alarm, the second stage is used for trip. Both levels are set in primary values, for instance:
if in general settings we set CT_RATIO to a value of 100, and the same value for PT_RATIO, the base power is: 100
x 100 = 10000 W
The block time allows blocking the element operation during a set time after the coupling breaker closure. For this
purpose it is necessary to connect the breaker bay using a 52B type contact. The purpose of this setting is to avoid
spurious trips caused by overloads after the breaker closure.
Power calculations depending on the VT connection:
1- WYE VT connection, or only one transformer in phase-to-ground connection:
Element description
The Directional Power element responds to three-phase active power measured from the feeder associated with the
F650. This element can be selected to operate according to the power threshold adjusted in the corresponding
setting. This element is ideal for reverse power applications (F32 REV) or forward power (F32 FWD), depending on
the selected setting. The relay measures the three-phase power for wye or delta connections.
The element has an adjustable characteristic angle and minimum operating power as shown in the Directional Power
Characteristic diagram. The element responds to the following condition:
P cos(j) + Q sin (j) > SMIN
where: P and Q are active and reactive powers as measured per the F650 convention, j is the angle set at the 32
setting (DIR POWER ANGLE) in degrees in steps of 0.01º, and SMIN is the minimum operating power.
The element has two independent (as to the pickup and delay settings) elements. Both elements can be used for
alarm and trip, and they can be set separately to provide a mixed power protection.
The Directional Power Characteristic is shown in the following diagram.
By making the characteristic angle adjustable from 0º to 360º in steps of 0.01º, a variety of operating characteristics
can be achieved as presented in the figures below. For example, for an angle of 0º, the element would operate as a
32 Forward Power element, while if setting an RCA angle of 180º, the element would operate as a 32 Reverse
Power element. For angles of 90º and 270º, the case would be similar but with reactive power.
Figures (a, b, c, d, e, f) below shows settings for different power applications.
The following table shows the SMIN and angle values that must be used for some typical applications:
Table 5-61: Directional power element
SMIN (Stage Tap) ANGLE (RCA) ELEMENT
>0 0º Forward Active Power
<0 0º Reverse Low Forward Active Power
>0 180º Reverse Forward Active Power
<0 180º Low Forward Active Power
By adding 90º to the angles shown on figures a, b, c and d, the represented elements would be similar but with
Reactive Power instead of Active Power.
Any other angle would provide a mixed Protection Between Active and Reactive power.
A different angle selection for Stage 1 and Stage 2 can provide in a single element, a Reactive and Active power
limitation. For example, using the following values:
Dir Power Angle 1(RCA) 0º
Stage 1 Tap 0
Dir Power Angle 2(RCA) 90º
Stage 2 Tap 0
We would obtain a mixed Protection Between figure (d) and figure (e).
Settings
Table 5-62: 32 element settings
SETPOINT > PROTECTION ELEMENT > SETTING GROUP X > Power > Directional Power >
Directional Power 1 > Directional Power 2 > Directional Power 3
Setting Description Name Default Value Step Range
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Block from offline Blk Time After Close 0.00 0.01 s [0.00 : 900.00]
Directional Angle for stage 1 (RCA1) Dir Power Angle 1 0.00 1 Deg [0.00 : 359.99]
Pickup level for stage 1 Stage 1 Tap 10.00 0.01MW [-10000.00 : 10000.00]
Trip time for stage 1 Stage 1 Time 60.00 0.01 s [0.00 : 900.00]
Directional Angle for stage 2 (RCA2) Dir Power Angle 2 0.00 1 Deg [0.00 : 359.99]
Pickup level for stage 2 Stage 2 Tap 20.00 0.01MW [-10000.00 : 10000.00]
Trip time for stage 2 Stage 2 Time 60.00 0.01 s [0.00 : 900.00]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
The snapshot event setting enables or disables the snapshot event generation for this element.
Function: Enables or disables the directional element.
Blk Time After Close: In seconds. This settings allow to block the element 32 during the time specified
in the setting after the breaker switches from OPEN to CLOSED.
Dir Power Angle (1-2) (RCA): This setting specifies the relay characteristic angle (RCA) for the directional
power element. This setting provides ability to respond to the function in any
direction defined (active forward power, active low forward power, etc.)
Stage (1 - 2) Tap: This setting specifies the minimum Operation three-phase power for the Stage 1 (2) element. The
power value defined in this setting is the minimum distance between the source and the directional power
characteristic. This value can be positive or negative. The value of this setting is defined in total MW (primary) – the
CT and VT value is considered in the calculations.
NOTE:
Even if the element defined in this setting is MW, this does not necessarily mean that the resulting value and the
RCA setting are in MW. For example:
RCA: 30 º SMIN: 100 MW.
If we assume that there is only active power. The element operation would be produced for a value of:
P = 100 / cos (30) = 115,7 MW.
If there was only reactive power:
Q = 100/sin (30) = 200,0 MVar.
(In this case the real Operation elements are Mvar, even if SMIN is expressed in MW.)
Stage 1 (2)Time: This setting specifies the delay for Stage 1 of the element. For reverse power or direct power
applications, usually Stage 1 is used for alarm functions, while Stage 2 is used for tripping functions.
Snapshot Events: This setting enables or disables the generation of events. All states in this function are affected
by this setting.
Status
Statuses defined for this Function are as follows:
DIR PWR1 (2, 3) BLOCK: Writing status, operates by level. When this status is activated externally (via
PLC), the directional power element is blocked. This status affects both elements
in the protection element (stage 1 and 2).
Activation of this status produces the event: DIR PWR1 (2, 3) BLK ON.
Deactivation produces the event: DIR PWR1 (2, 3) BLK OFF.
DIR PWR1 (2, 3) STG1 (2) OP: This is activated when the element that corresponds to stage 1/2 is activated.
Events generated by this element are:
DIR PWR1 (2, 3) STG1 (2) OP ON
DIR PWR1 (2, 3) STG1 (2) OP OFF
DIR PWR1 (2, 3) STG1 (2) PKP: Activation of this status indicates that the power value has exceeded the threshold
indicated by the Stage 1/2 element. Events generated by this element are:
DIR PWR1 (2, 3) STG1 (2) PKP ON
DIR PWR1 (2, 3) STG1 (2) PKP OFF
DIR PWR1 (2, 3) STG PKP: This status is a logic OR between the DIR PWR STG1 PKP and DIR PWR STG2
PKP statuses. Activation of this status indicates that the power value has
exceeded the threshold indicated by any of the Stage 1/2 elements. Events
generated by this element are:
DIR PWR1 (2, 3) STG PKP ON
DIR PWR1 (2, 3) STG PKP OFF
DIR PWR1 (2, 3) STG OP: This status is a logic OR between the DIR PWR STG1 OP and DIR PWR STG2
OP statuses. This is activated when the element that corresponds to stage 1/2 is
activated. Events generated by this element are:
DIR PWR1 (2, 3) STG OP ON
DIR PWR1 (2, 3) STG OP OFF
Element settings
SETPOINT > PROTECTION ELEMENT > SETTING GROUP X > POWER >
WATT GND FLT HIGH 1 > WATT GND FLT HIGH 2 > WATT GND FLT HIGH 3
WATT GND FLT LOW 1 > WATT GND FLT LOW 2 > WATT GND FLT LOW 3
Setting Description Name Default Value Step Range
Function permission Function DISABLED N/A [DISABLED-ENABLED]
Supervision minimum voltage Voltage Pickup Level 2.00 0.01 V [2.00 : 70.00]
Source of operating current. Current selection IN N/A [IN-IG]
Pickup Level for Overcurrent OC Pickup Level 0.005 0.001A [0.005 : 0.400]
Pickup Delay for Overcurrent OC Pickup Delay 0.20 0.01 s [0.00 : 600.00]
Pickup Level for operating Power Power Pickup 0.01 0.01 W [0.01 : 4.50]
Max torque angle MTA 0 1 Deg [0 : 360]
Pickup Delay for Operating Power Power Pickup Delay 0.20 0.01 s [0.00 : 600.00]
Curve shape Curve DEFINITE TIME N/A [DEFINITE TIME - INVERSE TIME -
USER CURVE A - USER CURVE B
- USER CURVE C - USER CURVE
D]
Multiplier Multiplier 1.00 0.01 s [0.02 : 2.00]
Snapshot event generation Snapshot Event DISABLED N/A [DISABLED-ENABLED]
Current selection: The element responds to the neutral (3 times zero-sequence) current, either calculated
internally (IN) from the phase currents, or supplied externally (IG) via the ground CT
input. This setting allows selecting the source of the operating current.
OC Pickup Level: This setting specifies the current supervision level for the measurement of the zero-
sequence power.
OC Pickup Delay: This setting specifies delay for the overcurrent portion of this element. The delay applies
to the 32N1(2 3) HIGH(LOW) OC PKP operand driven from the overcurrent condition.
Power Pickup: This setting specifies the operating point of the element.
MTA: This setting adjusts the maximum torque angle of the element.
Power Pickup Delay: This setting defines a definite time delay before the inverse time characteristic is activated. If
the curve selection is set as “Definite Time”, the element would operate after this security time delay.
Curve: This setting allows choosing one of three methods to delay operate signal once all conditions
are met to discriminate fault direction:
Definite time: Fixed time delay defined by the POWER PICKUP DELAY setting
Inverse time: Inverse time characteristics delay defined by:
S PKP
t = m • -------------
S OP
where m is a multiplier defined by the MULTIPLIER setting, SPKP is the pickup setting
and SOP is the operating power at the time.
FlexCurve A,B,C,D: any time characteristics programmed by the user with
FlexCurves.
Snapshot Events: The snapshot event setting enables or disables the snapshot event generation for the
wattmetric ground fault elements.
Element description
The operating power is calculated as:
S_op= real(Vn(In 1ÐMTA)*)
where: * stands for complex conjugate. By varying the MTA angle one can make the element to respond to forward
or reverse direction in inductive, resistive, or capacitive networks as shown in the figure below.
Vn – neutral voltage (3 times V_0): either calculated (VX as auxiliary voltage setting) or supplied from the Auxiliary
voltage channel (VN as auxiliary voltage setting)
In – neutral current (3 times I_0): either calculated (IN as current selection setting) or supplied from the ground
current channel (IG as current selection setting)
The following figure shows the logic scheme diagram for high range and low range wattmetric ground fault elements
(32NH, 32NL).
Status
Statuses defined for this Function are as follows:
32N1 (2, 3) HIGH (LOW) BLOCK:Writing status, operates by level. When this status is activated externally (via PLC), the
wattmetric ground fault element is blocked.
The activation produces the event: 32N1 (2, 3) HIGH (LOW) BLOCK ON.
Deactivation produces the event: 32N1 (2, 3) HIGH (LOW) BLOCK OFF.
32N1 (2, 3) HIGH (LOW) OC PKP: The activation of this status indicates that the current value has exceeded the
threshold indicated and pickup delay has expired. Events generated by this element
are:
32N1 (2, 3) HIGH (LOW) OC PKP ON
32N1 (2, 3) HIGH (LOW) OC PKP OFF
32N1 (2, 3) HIGH (LOW) PKP:Activation of this status indicates that the current, voltage and power value has exceeded
the threshold indicated and power pickup delay has expired.
Events generated by this element are:
32N1 (2, 3) HIGH (LOW) PKP ON
32N1 (2, 3) HIGH (LOW) PKP OFF
32N1 (2, 3) HIGH (LOW) OP: This is activated when the element is activated. Events generated by this element are:
32N1 (2, 3) HIGH (LOW) OP ON
32N1 (2, 3) HIGH (LOW) OP OFF
** For firmware below 7.20 version, only the first three overfrequency elements is available.
The snapshot event setting enables or disables the snapshot event generation for this element.
Frequency elements operate with the system frequency, this frequency is measured in the voltage channel set for
the frequency reference, in the Frequency Reference setting inside Setpoint > System Setup >General Settings.
SETPOINT > Protection Elements > Setting Group X > FREQUENCY RATE OF CHANGE
FREQUENCY RATE OF CHANGE 1 > FREQUENCY RATE OF CHANGE 2 > FREQUENCY RATE OF CHANGE 3
Setting Description Name Default Value Step Range
Function Permission Function DISABLED N/A [DISABLED – ENABLED]
Direction of the frequency change Freq. rate trend INCREASING N/A [INCREASING - DECREASING
- BI-DIRECTIONAL]
Operation Value in Hz/s Freq. rate pickup 0.50 0.01 Hz/s [0.10 : 10.00]
Minimum required voltage in % Freq. rate OV supv 40.00 0.01% [0.00 : 110.00]
nominal voltage
Minimum Frequency Threshold Freq. rate min 45.00 0.01 Hz [20.00 : 80.00]
Maximum Frequency Threshold Freq. rate max 65.00 0.01 Hz [20.00 : 80.00]
Frequency rate Trip Delay Freq. rate delay 0.00 0.01 s [0.00 : 60.00]
Rate of Change Function: This setting allows enabling or disabling the frequency rate of change element.
Freq rate trend: This setting allows to configure the element in order to answer to increasing,
decreasing or both directions frequency changes.
Freq. Rate Pickup: This setting defines the value to operate the element. If Direction is set as
"Increasing", element operates when df/dt > Pickup Level, if set as "Decreasing"
when -df/dt > Pickup Level, if set as both when |df/dt| > Pickup Level.
Freq. Rate OV supv: This setting defines the minimum required voltage. Under this level, the frequency
rate of change element is blocked. This is the percentage of the nominal voltage
(adjust in general settings). Voltage used as reference is line voltage (see
frequency reference setting in general settings).
Freq rate Min: This setting defines the minimum frequency required in this unit to be enabled.
For any value under this level the element is disabled.
Freq rate Max: This setting defines the maximum frequency allowed in this unit to be enabled.
For any value above this level the element is disabled.
Freq rate Delay: Time that the element must remain picked up before it operates.
Snapshot events: The snapshot event setting enables or disables the snapshot event generation for
this element.
The frequency rate of change actual values can be viewed at Actual> Status > Control Elements > Frequency:
Table 5-65: Frequency rate of change status
FREQUENCY RATE OF CHANGE STATUS
FREQ RATE1 PKP
FREQ RATE1 OP
FREQ RATE2 PKP
FREQ RATE2 OP
FREQ RATE3 PKP
FREQ RATE3 OP
The block signals for the frequency rate of change element can be viewed at: Actual> Status > Protection >
Protection Blocks:
SETPOINT > PROTECTION ELEMENTS > SETTING GROUP X > MISCELLANEOUS > BROKEN CONDUCTOR
Setting Description Name Default Value Step Range
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Tap Level in percentage of I2/I1 Tap 20.0 0.1% [20.0 : 100.0]
Trip Time Trip Delay 60.00 0.01 s [0.00 : 900.00]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Current Inhibition Level setting Operation Threshold 0.005 0.001 A [0.000 : 1.000]
This way, when the function is enabled and the unbalance is produced over the set percentage, the element picks
up. If unbalance conditions are maintained during a period longer than the set time delay, the element trips.
In order to avoid trips or pickups with very weak loads there is a current level threshold to inhibit the operation of
the element when the three phase currents are below a fixed level.
Note: The I2/I1 current inhibition level for the different firmware versions is as follows:
The Operation Threshold level has been included to allow the user selecting the current inhibition level suitable for a
particular application, in order to avoid operation of the element when the relay is not connected to the line or in case
the relay has previously operated correctly and has been disconnected from the line, as in this case the operation
condition is met but the relay should not trip.
The operation threshold operation is as follows:
The Broken conductor element is fully operational if at least one of the phase currents is higher than the setting. This
condition assumes that the relay is connected to the line.
If the element is on trip or pickup condition, the element is reset if the three phase currents are below the operation
threshold level. This condition assumes that the relay is not connected to the line and therefore the relay should not
trip.
Due to the response time of this function, if the set time delay is 0s, a trip can occur in situations where, for example,
one of the currents is stopped before the rest, as these currents would produce a negative sequence current
calculation. Therefore, to avoid this kind of undesired trips, it is strongly recommended to establish a minimum time
delay setting, such as 100 ms, or higher depending on the expected normal unbalances in the network. This is to
differentiate these situations from broken conductor situations.
The block signals for the locked rotor element can be configured at: Setpoint > Relay Configuration > Protection
Elements
Table 5-69: Locked rotor blocks
LOCKED ROTOR BLOCKS
LOCKED ROTOR1 BLK
LOCKED ROTOR2 BLK
LOCKED ROTOR3 BLK
Note:
The element works with primary values.
The element picks up if at least one of the three phase currents is above the adjusted level. The operation value is
the higher of the three.
The reset level is 97% to 98% of the pickup level.
The load encroachment element responds to the positive-sequence voltage and current and applies a characteristic
shown in the figure below.
Reach: This setting specifies the impedance reach of the element as shown in the load
encroachment characteristic diagram. This settings should be entered in secondary
ohms and be calculated as the positive-sequence impedance seen by the relay under
maximum load conditions.
Angle: This setting specifies the size of the blocking region as shown on the Load
Encroachment Characteristic diagram and applies to the positive sequence impedance.
Pickup Delay: This setting specifies the delay for the trip of Load Encroachment element. After this time
expires the signal Load Encroachment Operate is asserted.
Reset Delay: This setting specifies the time that the signal Pickup and operate are asserted after trip
conditions have been removed.
Snapshot events: The snapshot event setting enables or disables the snapshot event generation for this
element.
The Load Encroachment actual values can be viewed at Actual> Status > Control Elements > Load
Encroachment
The block signals for the Load Encroachment element can be viewed at: Actual> Status > Protection > Protection
Blocks:
Table 5-71: Load encroachment blocks
Setting Group
Synchrocheck (25)
Autoreclose (79)
Breaker Failure (50BF)
VT Fuse Failure
Pulse Counters
Digital Counters
Analog Comparators
Max Number of starts
Cold Load Pickup
PLC Timer mask
60 CTS Failure
2nd Harmonic Inhibit
Note: for all control elements related to the breaker, it must be considered that all operations are performed
considering the status of the switchgear configured as breaker. In Setpoint > Relay Configuration > Switchgear
up to 16 switchgear elements can be configured to operate and be monitored, but only one of them can be
configured as a breaker, for monitoring, number of openings and closings counters, (KI)2t.
The snapshot event setting enables or disables the snapshot event generation for this element.
For more detailed information go to section 5.4.1 Available settings and setting groups
WARNING
When testing this function do not forget that the relay must detect an open breaker to operate.
The synchronism element is used for monitoring the connection of two parts of the circuit by the close of a breaker.
This element verifies that voltages (V1 and V2) at both sides of the breaker are within the magnitude, angle and
frequency limits set by the user. V1 and V2 are the line and busbar voltage values measured by the relay.
Synchronism check (25) is defined as the comparison of the voltage difference of two circuits with different sources
to be either linked through an impedance element (transmission line, feeder, etc.), or connected through parallel
circuits of defined impedance (Figure 5-23: Synchronism check element) The voltage comparison between both
sides of a breaker is performed before closing the breaker, in order to minimize internal damage that can occur due
to the voltage difference, both in magnitude and angle. This is extremely important in steam generating plants, where
reclosing output lines with angle differences can lead to severe damage to the turbine axis.
Vs
52s 52r Vr
ZParallel
Figure 5-23: Synchronism check element
The difference in voltage level and phase angle in a given moment is the result of the existing load between remote
sources connected through parallel circuits (load flux), as well as a consequence of the impedance of those
elements connecting them (even if there is no load flux in parallel circuits, or because sources to be connected are
completely independent and isolated from one another).
In interconnected systems, the angle difference between both ends of an open breaker is usually negligible, as its
sources are remotely connected through other elements (equivalent or parallel circuits). However, in isolated circuits
as in the case of an independent generator, the difference in angle, voltage levels and relative slip of voltage phasors
can be very important. It may happen that the relative slip of voltage values is very low or null so that they are rarely
in phase. Luckily, due to the changing conditions of a power system (connection-disconnection of loads, sources,
and new inductive-capacitive elements) the relative slip between phasors is not null and they can be synchronized.
In the first case, even if we must take into consideration the length of the line whose ends (sources) are connected
for determining the angle difference between them, this is not enough to fix the synchronism conditions before
closing the breaker. Experience tells us that the window of angle difference between voltage phasors must be fixed
to a value of 15º-20º.
Setpoint > System Setup > General settings > Auxiliary Voltage setting must be set to Vx, in order to monitor
auxiliary voltage instead of Vn (neutral voltage, coming from an open delta connection).
5.5.2.2 Application
Even if the application range of the F650 is quite wide and the element can be used in distribution lines at any
voltage level, it must be taken into account that it is a three-pole tripping relay, designed for managing a single
breaker. This is why F650 is not suitable for one and a half breaker configurations, or ring configurations where a
transmission line or feeder has two breakers.
5.5.2.3 Settings
There is only one synchrocheck element in the F650.
the maximum angle difference. This means that if the product of the frequency slip multiplied by the
breaker closing time covers an angle greater than two times the maximum angle, closing is not
allowed. For further information see 5.5.4.5.
Closing permission logic settings:
In case that the voltage at one or both ends of the breaker is null, the synchronism element cannot establish the
necessary parameters to give closing conditions, and therefore it does not issue synchronism permission. For those
situations where the user wants to enable the closing permission in a condition of loss of one or both voltages at both
ends of the breaker, F650 elements incorporate closing permission logics for the cases of: dead line-dead bus, live
line-dead bus and dead line-live bus.
Dead line- Dead Bus Function permission (DL-DB Function): Enabling this Function allows issuing
a Closing permission signal in dead line and dead bus Condition (without voltage at both sides of the
breaker).
Live line- Dead Bus Function permission (LL-DB Function): Enabling this Function allows to issue
a Closing permission signal in live line and dead bus Condition (without voltage at the sides of the
breaker that corresponds to the busbar voltage)
Dead line- Live Bus Function permission (DL-LB Function): Enabling this Function allows issuing
a Closing permission signal in live line and dead bus Condition (without voltage at the sides of the
breaker that corresponds to the line voltage).
Snapshot event: The snapshot event setting enables or disables the snapshot event generation for this element.
SYNCROCHECK BLK INP: Block signal for the synchrocheck element, configurable at Setpoint > Relay
Configuration > Control Elements
SYNCROCHECK OP: Closing permission signal in live line-live bus conditions with open breaker.
SYNCHK CLOSE PERM: General Closing permission of the Synchronism element. It contemplates all
possible situations, live line-live bus conditions, and the closing permission logics
(dead line-dead bus, live line- dead bus, dead line-live bus). Note: in case the
Function is disabled, the Closing permission signal is activated in order not to
interfere with possible logics where it is included. If the synchronism element is
enabled, this signal is only activated in the closing conditions established by
setting.
SYNCROCHECK COND OP: Closing permission according to permission logics (DL-DB, LL-DB, DL-LB).
Voltage and frequency values for the line and busbar can be obtained, both in primary and secondary values at:
Actual> Metering > Primary Values > Voltage
VBB Primary (KV) Busbar voltage in primary values
VL Primary (KV) Line voltage in primary values
Actual> Metering > Secondary Values > Voltage
Line Voltage (V) Line voltage in secondary values
Bus Voltage (V) Busbar voltage in secondary values
5.5.2.5 Algorithm
F650 elements perform the synchronism check by basically establishing and comparing three parameters:
Module difference of voltage phasors DV (V)
Phase angle of voltage phasors Dj (º)
Frequency slip between two phasors S (Hz)
These parameters are continuously determined and managed once that element 25 has been enabled by
setting, and in open breaker conditions. It is necessary to consider that all calculations are made once the open
breaker condition is detected; if the breaker is closed or undefined, the synchronism element does not issue a
closing permission signal, even when closing conditions are met.
If voltage on one side of the breaker to be closed is null, the synchronism element cannot establish the synchronism
check, and therefore it does not issue synchronism permission. For these cases, usual in breaker maintenance
situations, or in new installations where voltage might not be present, but the breaker operation needs to be verified,
F650 elements incorporate closing permission logics for situations of:
Dead Line – Dead Bus (DL-DB)
Live Line – Dead Bus (LL-DB)
Dead Line – Live Bus (DL-LB)
In order to establish the closing permission signal, the first parameter used by the algorithm is the difference in
magnitude between line and bus voltages, and afterwards, the angle difference and frequency slip are verified.
Voltage Difference DV
Comparing the voltage values for line voltage (V1) and busbar voltage (V2) at both sides of the breaker, the relay
can determine the synchronism situation of the element (see Table 5-75: Synchronism conditions).
Being:
V1 line voltage
V2 bus voltage
VL Minimum acceptable voltage by setting to establish synchronism conditions (dead line and bus levels).
VH Appropriate voltage to establish synchronism conditions, configured by setting (live line and bus levels).
Table 5-75: Synchronism conditions shows the different synchrocheck and closing logic situations, that can be
produced depending on the line and busbar voltage levels.
Live Line – Live Bus (Synchronism check): Only in case number (2), with live line and live bus, the element starts
evaluating the line and busbar voltage comparison with respect to the setting
DVset established by setting (Max Volt Difference). In this case, if the voltage
difference is lower than DVset, the synchronism check element (25) verifies the
angle difference Dj adjusted by setting (Max Angle Difference).
Dead Line – Dead Bus (DL - DB): Case number (3) does not allow the synchronism function, but it does allow DL-
DB operation logic, if this logic is enabled by setting (DL-DB Function).
Dead Line – Live Bus (DL - LB): Case number (6) does not allow the synchronism function, but it does allow DL-
LB Operation logic, if this logic is enabled by setting (DL-LB Function)
Live Line – Dead Bus (LL - DB): Case number (7) does not allow the synchronism function, but it does allow LL-
DB operation logic, if this logic is enabled by setting (LL-DB Function)
Case numbers (1), (4) and (5) are not considered neither for synchronism check purposes, nor for closing logic.
set
actua
VH
VL
V1 V2
In the live-live bus condition, once the voltage difference has been successfully verified in magnitude, the relative
frequency slip between phasors is calculated. From the information obtained from the relay, the algorithm knows the
slip (mHz) of both phasors, and it takes as reference (VRef) the lowest frequency phasor. The behaviour of the
algorithm depends on the slip frequency and the breaker close time as follows:
1. If the relative slip, Δf, is equal or lower than 20 mHz, the algorithm gives permission to close as soon as the
angle difference is slower than the Δϕset (Max Angle Difference), because at such a low speed, the hold time for
getting an “in-phase” closing permission would be too long.
2. If the relative slip is higher than 20 mHz, the element performs an anticipative algorithm, determining the right
moment to give the closing command to the breaker, so that the breaker closes when the line and busbar
voltages are in phase. When the difference between voltage values equals “two times” the set angle as
maximum angle difference (ΔV = ΔVset), the anticipative algorithm starts running and uses the set breaker
closing time to establish the initiation of permission, so that it is executed in the moment when both voltage
phasors are completely in phase, thus minimizing the voltage difference in the breaker chamber to negligible
values. The main benefit is that after a considerable number of breaker operations, damage to internal
connection elements, as well as to the chamber isolating element is drastically reduced, ensuring a longer life for
the breaker, and reducing costly maintenance operations.
3. If the product of frequency slip and breaker closing time is higher than Max Angle difference and lower than two
times this setting, as an in phase close is not possible, the algorithm ensures that the difference between
voltages in the real closing moment is not higher than the set value (Max Volt Difference).
4. If this product is beyond two times Max Angle difference, closing operation is not allowed.
The Closing process using anticipative algorithm is described on the following figure:
VRef V’s V
1 1
VRef
V’s
V
AR LEVEL BLOCK: This signal is configured to block the autoreclose by level; when the block signal
disappears, the recloser goes to Lockout status before returning to either the READY
status, or the corresponding status in the reclosing cycle.
AR PULSE BLOCK: This signal is configured to block the autoreclose by pulse; a pulse moves the autoreclose
to BLOCK status. The autoreclose block is active until an unblock signal is received.
AR PULSE UNBLOCK: This signal is configured as autoreclose unblock by pulse; this pulse is required to bring the
recloser out of the block status. The autoreclose goes to Lockout after a block situation.
AR INITIATE: This signal indicates the autoreclose initiation. Usually, the factory default configuration sets
this signal as a combination of the general trip signal (Virtual Output 83), and an external
input configured as AR Initiate.
AR CONDS INPUT: This signal configures the conditions that are to be met before executing a breaker close
command. These conditions are verified once the configured Dead Time has expired, and
they are only considered if the Cond. Permission setting is enabled. Otherwise, these
conditions wouldn’t have any effect. In the default factory configuration, the conditions input
is associated with the synchronism check element close permission.
AR BLOCK BY LEVEL Autoreclose blocked by level. See AR block signals configuration (AR LEVEL BLOCK)
AR BLOCK BY PULSE Autoreclose blocked by pulse. See AR block signals configuration (AR PULSE BLOCK)
AR STATUS Autoreclose status (see Table 5-77: 79 internal status)
AR LOCKOUT MODE Autoreclose lockout mode (see Table 5-77: 79 internal status)
AR BLOCK MODE Autoreclose block mode (see Table 5-77: 79 internal status)
From READY status, a reclose initiation sets the cycle counter to 1 and a reclosing sequence is initiated which
produce breaker close commands, unless any abnormality is produced that makes the autoreclose go to
LOCKOUT status.
The reclosing sequence consists on the following steps:
Wait until the breaker is open, if the waiting exceeds the Fail to Open Time setting, the autoreclose goes to
LOCKOUT by failure of opening status (AR LCK BY FAIL OPEN).
Once the breaker is open, it waits for the time set in the Dead Time N setting, N being the number of the cycles
in progress. If during this waiting the breaker is closed or reclose initiation conditions are given, the recloser
goes to LOCKOUT status by anomaly (AR LCK BY ANOMALY).
Once the Dead Time has expired, in case the Conditions Permission setting is disabled, a closing command
would be produced. If the conditions permission setting is enabled, the system waits for the conditions fixed in
the conditions input (AR CONDS INPUT) configured at Setpoint > Relay Configuration > Protection
Elements; if the waiting period for the reclosing conditions signal activation exceeds the Hold Time, the
autoreclose goes to Lockout status by conditions (AR LCK BY CONDS).
The autoreclose gives a Closing command and waits for the breaker to close. If the Fail to Close Time setting is
exceeded, the autoreclose goes to lockout by failure to close (AR LCK BY FAIL CLOSE).
At this point, the diagram indicates that a reclosing cycle has been reached, and so the cycle counter is increased. In
this time, the period set in Reset Time starts to count. If during the set element reset time there is no autoreclose
initiation, the cycle counter resets to its initial value (1), and the autoreclose returns to the standby status (READY).
If during the Reset Time setting period, there is a new autoreclose initiation, the Reclose In Progress sequence
starts again. If this reclose is produced after the last configured cycle in the Maximum Number of Shots setting, the
autorecloser goes to Lockout by maximum number of shots (AR LCK BY SHOTS).
AR LOCKOUT
This is a safety status, scheme lockout blocks all phases of the reclosing cycle, preventing automatic reclosure.
From the out of service (AR DISABLE) and BLOCK statuses, the autoreclose stays in LOCKOUT prior to going
to READY.
From the RECLOSE IN PROGRESS status, the recloser goes to LOCKOUT status if any of the anomalies
described above occur.
To go from the LOCKOUT status to READY it is necessary that the breaker is closed and stays closed for preset
time in Reclaim Time setting.
AR BLOCK
The BLOCK status is similar to the LOCKOUT status, as it guarantees that if the autoreclose is in Block, no
breaker close command is produced, but the difference between them is that this Block status is reached by an
external action. The autoreclose block can be configured by pulse or level signals. This configuration must be
selected at Setpoint > Relay Configuration > Protection Elements
When the autoreclose block signal is deactivated, either by a level change in the set signal (in case of block by
level) or by an Unblock pulse (in case of block by pulse), the block status is abandoned and the autoreclose
returns to the Lockout status.
Configurable signals to block the autorecloser are described in section 5.5.3.2 Autoreclose inputs.
Figure 5-29: Reclose initiation and block signals configuration example shows an example of the autoreclose
initiation and protection element block signals after the different trips. The autoreclose initiate signal is configured to
the relay general trip that corresponds to virtual output 83 configured in the logic configuration tool, and a physical
contact to generate an external autoreclose initiation.
In the example shown on the figure, the 50PH element block signal is configured as a combination of block by digital
input, block by non-trip permission of the directional element, and finally the element remains blocked during the
reclosing cycle. This means that only the first trip can be executed by the phase instantaneous overcurrent element;
after the first reclose trip, the element remains blocked until the end of the cycle.
Signals relative to breaker failure provided by the relay can be viewed at Actual> Status > Control Elements >
Breaker Failure, and they are as follows:
Table 5-79: Breaker failure status
BREAKER FAILURE STATUS
BKR FAIL INITIATE
BKR FAIL NO CURRENT
BKR FAIL SUPERVISION
BKR FAIL HISET
BKR FAIL LOWSET
INTERNAL ARC
BKR FAIL 2nd STEP
BKR FAIL INITIATE External signal for breaker failure initiation. (Configurable at settings> Relay
Configuration > Protection Elements).
BKR FAIL NO CURRENT Signal for breaker failure without current
BKR FAIL SUPERVISION Signal for supervision level breaker failure (retrip)
BKR FAIL HISET Signal for high-level breaker failure
BKR FAIL LOWSET Signal for low-level breaker failure
INTERNAL ARC Signal for internal arc
BKR FAIL 2nd STEP Signal for Second level breaker failure (high and low)
The following figure shows the logic scheme for the breaker failure element:
HI
HI
HI
LO
LO
LO
The internal arc element inside the breaker failure element is independent from the external breaker failure signal;
this element is used to detect arcing produced with an open breaker; if a higher current that the set level is detected
during a period that is longer than the set delay for the element (Internal Arc Delay), and the breaker is open, the
corresponding internal arc signal is issued (INTERNAL ARC).
The fuse failure element has only two settings, one to enable or disable the element and the other to enable or
disable the snapshot event generation.
The fuse failure signal provided by the element (VT FUSE FAILURE) can be monitored at Actual> Status > Control
Elements >VT Fuse Failure
CntPulses Board Origin: Board selection for the pulse counter input.
CntPulses Input Origin: Index of the input select in the board origin.
The signals related to the 8 pulse counters can be viewed at Actual> Status > Control Elements > Pulse
Counters and they are as follows:
Table 5-80: Pulse counters status
The F650 includes eight different pulse counters in which the value shown is the result of the number of activation of
the input configured for that counter multiplied plus the CntPulses Factor set for that pulse. For each pulse counter
there are two magnitudes available, the actual value and the frozen value.
The freeze and unfreeze and reset operations are similar to the energy management, the signals used for that
purpose are the same for both energy and pulse counters.
By default, all the values are unfreeze, updating the values in a continuous mode. After a freeze operation the freeze
value stops updating and the actual value is being updated. If a freeze operation is set again, the actual value is
copied to the freeze one, which remains frozen again.
To unfreeze all the values it is necessary to perform an unfreeze operation.
If a reset operation is set, all the values, actual and frozen ones goes to zero.
All the operations (freeze, unfreeze and reset) are performed over all the energy counters (both energy and pulse
counters). It is not possible to set them to a particular counter.
The analog level value is by default in a reset state, when the value meets the comparison (inside or outside the
comparison band) the "Analog Level X" signal is activated if the analog value remains active the time set in the
analog delay setting. When the activation conditions are not met the "Analog Level X" value goes to the reset state.
An analog change must remain active at least 40 ms to be considered, plus the analog time setting. Besides the
snapshot event data has a 20 ms accuracy.
For F650 with firmware version below 7.XX, the special model F650 MOD003 relay incorporates a maximum number
of starts function (66) to prevent operators from jogging the motor (multiple starts and stops performed in rapid
succession). For F650 with firmware version 7.XX this element is included in standard models (No special model
(MOD) is required)
A motor start is assumed to be occurring when the F650 measures the transition of the motor current from below 5%
of FLA to some value above 7% of FLA. Breaker status can also be used to detect motor starts. At this point, one of
the Starts/Hour timers is loaded with 60 minutes. Even unsuccessful start attempts are logged as starts for this
feature. Once the motor is stopped, the number of starts within the past hour is compared to the number of starts
allowable. If the two numbers are the same, a block occurs. If a block occurs, the lockout time is equal to the longest
time elapsed since a start within the past hour, subtracted from one hour.
The time to Restart feature may be used to ensure that a certain amount of time passes between stopping a motor
and restarting that motor. This timer feature may be very useful for some process applications or motor
considerations. If a motor is on a down-hole pump, after the motor stops, the liquid may fall back down the pipe and
spin the rotor backwards. It would be very undesirable to start the motor at this time. In another scenario, a motor
may be driving a very high inertia load. Once the supply to the motor is disconnected, the rotor may continue to turn
for a long period of time as it decelerates. The motor has now become a generator and applying supply voltage out
of phase may result in catastrophic failure.
The Restart Block feature is strictly a timer. The F650 does not sense rotor rotation.
Snapshot events: The snapshot event setting enables or disables the snapshot event generation for this element.
This unit operates only if the motor is stopped, in order to avoid a new start. The unit never operate while the motor
is running.
The maximum number of starts actual values can be viewed at Actual > Status > Control Elements >Max.
Number of Starts:
The block signals for the frequency rate of change element can be viewed at: Actual > Status > Protection >
Protection Blocks:
Note: All the counters are stored in a RAM memory, therefore when the relay is powered off and powered, on all
timers and counters are set to a zero value.
Settings
Relay configuration
To the correct operation of each counter, there are several PLC status variables in EnerVista 650 Setup at
Setpoint> Relay Configuration>Control Elements section that should be configured properly. Each one of the 8
digital counters has its own PLC statuses and they are identical:
DIGCNT X BLOCK: Blocks the functionality of the specified counter. If a counter’s DIGCNT X BLOCK is set to
1, all the counter’s values remain unaltered and no counter commands are processed.
When the counter’s DigCnt X Function is set to Enabled and the DIGCNT X BLOCK is set
to 0, then the counter starts running and accepting counter commands.
DIGCNT X UP: Counter command. When this element changes from 0 to 1, the value of the specified
counter is incremented by 1. If the current counter value is 2,147,483,647 and is
incremented, the updated value is set to -2,147,483,648.
DIGCNT X DOWN: Counter command. When this element changes from 0 to 1, the value of the specified
counter is decremented by 1. If the current counter value is -2,147,483,648 and is
decremented, the updated value is set to 2,147,483,647.
DIGCNT X SETPRESET: Counter command. This element defines the behavior of the specified counter’s Reset
and the Freeze/Reset commands or when counter is set from Disabled to Enabled:
• If set to 0, all commands with a Reset involved or when counter is Enabled set the initial counter value to 0
• If set to 1, all commands with a Reset involved or when counter is Enabled set the initial counter value to the one
specified in the setting DigCnt # Preset.
DIGCNT X RESET: Counter command. It sends a Reset command to the specified counter.
DIGCNT X FREEZERESET: Counter command. It copies the current counter value to the DIGCNT X
FROZENVALUE actual value and the current date to the DIGCNT X
FROZENDATE actual value. Then a Reset command is sent to the specified
counter.
DIGCNT X FREEZECOUNT: Counter command. It copies the current counter value to the DIGCNT X
FROZENVALUE actual value and the current date to the DIGCNT X
FROZENDATE actual value. Then the specified counter value DIGCNT X VALUE
is set to 0 or to the DigCnt X Preset setting value.
Periodically the counter current Value and Frozen Value and Date are saved to non-volatile memory to keep them
safe from an unexpected energy loss.
Note: Digital Counters only appear in the Actual Values menu option in HMI, in the Control Elements level.
Specifications – Control
Function This setting allows enabling and disabling the CTS function.
3I0 Current PKP: This setting defines the level of neutral current, above which CT failure would pick
up. Refer to the CT Failure logic diagram for more detail.
3V0 Voltage Inhibit This setting defines the level of neutral voltage (3V0) above which the CT failure
detection is inhibited.
GND Current Inhibit This setting defines the level of ground current above which CT failure detection is
inhibited.
SGND Current Inhibit This setting defines the level of sensitive ground current above which CT failure
detection is inhibited.
TIME DELAY This setting defines the time for CT failure to operate.
Care must be taken when configuring the delay for an IOC or TOC element that is being supervised by CT
Supervision Failure function. The delay time in the IOC function should be set to a value 10 ms greater than CT
Supervision Failure delay timer
Second harmonic Inhibit actual values are available in EnerVista 650 setup at
Actual Values>Control Elements> 2nd HRMC Inhibit
Blocks of 2nd harmonic inhibit can be configured in EnerVista 650 Setup at Setpoint> Relay Configuration>
Protection Elements. The status of this signal can be viewed at: Actual> Status > Protection > Protection Blocks.
The following picture shows the logic scheme for the 2nd Harmonic Inhibit function:
5.6 Inputs/outputs
5.6.1 Input/output placement
TERMINALS 1 2 4 5
V
2 CC2 52/a CC2 CC2
3 CC3 COIL 1 CC3 CC3
V
4 CC4 52/b CC4 CC4
5 CC5 CC1 CC5 CC5
6 CC6 CC2 CC6 CC6
7 CC7 CC3 CC7 CC7
8 CC8 CC4 CC8 CC8
9 COMMON 1/8 COMMON 1/4 COMMON 1/8 COMMON 1/8
10 COMMON 9/16 COMMON 5/8 COMMON 9/16 COMMON 9/16
11 CC9 CC5 CC9 CC9
12 CC10 CC6 CC10 CC10
13 CC11 CC7 CC11 CC11
14 CC12 CC8 CC12 CC12
15 CC13 COIL 2 CC13 CC13
V
32 CC28
O7 AI 7
33 CC29
O7
34 I SENS CC30
AI 8
I
35 CC31
O8 O8
36 CC32 SHIELD 5/8
For versions previous to 7.00, the snapshot event setting enables or disables the snapshot event generation for this
element. It is mandatory to enable this setting in order the input/output values to be refreshed in IEC61850 protocol.
Being:
X F, G, H or J, the I/O board name, depending on the Relay model.
F and G are internal Relay boards, and H and J are additional boards available in CIO modules (remote Bus CAN I/
O module).
For the I/O board selection in the relay model, associated digits to each board type are as follows:
Table 5-84: I/O board type
Associated Digit EnerVista 650 Setup Board Settings Board Type
0 NONE None
1 16 INP+ 8OUT Mixed
2 8 INP +8 OUT +SUPV Supervision
4 32 INP 32 digital inputs
5 16 INP + 8 ANA 8 Analog Inputs + 16 digital inputs
5.6.3 Inputs
The operation logic for supervision signals (board type 2) is detailed in section 5.6.5 Circuit supervision and contact
seal-in circuits in this manual.
5.6.4 Outputs
Figure 5-36: Output logic typesshows the types of signals associated with the different output configuration types.
Activated or deactivated status of those variables used internally to operate a contact output.
Actual > Inputs/Outputs > Contact Output Resets
These are the logic signals associated with the contact output reset, which produce the reset of those signals
previously configured as Latched. Configuration for the contact output reset signal is set at Setpoint > Relay
Configuration > Outputs > Contact Output Reset.
Actual > Inputs/Outputs >I/O Board Status
These signals are associated with the different I/O boards. There are internal signals that provide information about
the status of these boards, indicating whether there is any anomaly in the board, or whether the board is not
available in the relay according to the relay model.
Circuit Supervision:
F650 elements can include supervision boards (type 2), either in their internal slot F, or in an additional CIO module
connected to the element via a CAN bus (slots H and J). This type of board includes 4 voltage detectors for
implementing tripping or opening circuit supervision control logics.
Contact Seal-in:
The current seal-in circuit is used for verifying the current condition in a circuit during the time that the tripping
contact remains closed. If the current in the tripping circuit is maintained over 500 mA, the function is sealed
independently of the status of the function that caused the trip.
This current seal-in function in tripping circuits is mainly used in applications where auxiliary contacts 52/a (in charge
of cutting the current in the tripping circuit) are very slow. This may cause that, once the function that produced the
trip is reset, the relay contact opens before the breaker auxiliary 52/a, even if the time delay of the first has expired.
By using this function, we prevent the relay contact from cutting the current (basically inductive and high) from the
tripping circuit, which can cause damage to the element, as these currents exceed the nominal breaking
characteristics.
The circuit and the current threshold of the function are as follows:
500 mA min
In order to implement these schemes, it is not necessary to set any setting in the element. Internal functions are
always operative and provide the following logic operands:
A continuity failure is detected in a circuit when both voltage detectors (Va and Vb) detect lack of voltage during more
than 500 ms. This function is not influenced by the breaker status.
These operands can be associated with internal signals (virtual outputs), LEDs or element outputs, to issue alarm
signals or to block elements, for example for blocking the Breaker close if an anomaly is detected in the trip circuit.
Available schemes are as follows:
1. Without supervision
2. With current supervision (with seal-in)
3. With simple voltage supervision
4. With double voltage supervision
5. With current and simple voltage supervision (with seal-in)
6. With current and double voltage supervision (with seal-in)
7. With current and double voltage supervision (with seal-in) and serial resistor in voltage monitors.
The following subsections describe the different types of connection to create each supervision scheme in an easy
way. As the supervision circuits are identical, only the first group connection examples are described, being also
applicable to the second group.
In order to assure a high isolation level between groups, the digital inputs for supervision have been located in a
symmetrical basis. That is to optimize the isolation between groups that can be connected to different batteries, and
therefore requiring a greater distance between circuits.
this indication can be used to produce a latching of the output relay, so that it remains closed while the circulating
current is over 200 mA. To use the seal-in feature in the relay it is not necessary to configure any setting. It works,
we only must program the corresponding Circuit latching setting wiring the external circuit to terminals F34 and F36.
With this scheme, in the case of a failure to open from the breaker auxiliary contact, the F650 output relay does not
open the tripping coil current, as in this case the contact may be damaged, as it is prepared for opening currents
around 0.35 A at 125 Vdc. This latching or memory function is only guaranteed while the element is powered.
Figure 5-40: Supervision application with auxiliary contact 52a and a resistor (A6631F3)
Table 5-88: Supervision with 52/a
INTERNAL STATE V 52/a SUPERVISION
52 open ON OK
52 closed ON OK
TRIP OFF OK if t < 0.5 s
TRIP with 52 open OFF OK if t < 0.5 s
There is a possibility to monitor the trip circuit and trip coil continuity. This can be done by monitoring Vdc through the
output contact when this is open.
In this table, ON means that the voltage detector V52/a is active, detecting a voltage.
In the first case shown on the table, with closed breaker, voltage is detected by V 52/a sensor, and this means that
there is continuity in the supervised circuit.
As shown on Figure 5-40: Supervision application with auxiliary contact 52a and a resistor (A6631F3), when the
relay is not tripped, trip contact F35-F36 remains open. If the breaker is closed, its auxiliary contact 52a is closed.
Therefore, a little current is flowing, about 2 mA, through terminals F15 and F16 through the voltage detector circuit,
which flows through 52/a and the tripping coil 52TC (TC = tripping coil). Current only circulates when there is
continuity in the whole circuit, so the complete circuit is monitored, and not only the trip coil. This circuit includes
auxiliary 52/a as well as the whole wiring between the battery and the relay tripping terminals, and between these
and the breaker tripping circuit.
For the second case shown on the table, open breaker, its auxiliary contact 52/a remains open, and current cannot
flow through it for detecting continuity. In order to correctly monitor the circuit, a resistor must be used, not included
in the protection, connected in parallel. The value of resistance is selected so that the V 52/a input circuit minimum
detection current flows, but not as high as to activate the breaker-tripping coil. The figure shows the following
equation:
Where:
Vmin Is the minimum voltage, in Volts, expected in the battery (e.g. 80% of Vn)
R Resistance, in kilo ohms.
2 2 mA of approximate current flowing through input V 52/a
As shown in the second case in the table, with an open breaker, as current flows through R if there is continuity in the
WHOLE tripping circuit, voltage is detected in input V 52/a.
This works correctly in steady state. However, if the breaker trips, while it is opening, the V 52/a input signal can be
deactivated without this meaning that the circuit is not correct. This is due to the fact that the tripping relay, terminals
F35-F36, short circuits input V 52/a temporarily.
Therefore, if there is a trip signal, it is permitted that no signal is detected during a period of 1s to allow the breaker to
open, and reopen the tripping relay F35-F36.
Figure 5-41: Trip circuit and trip coil supervision, auxiliary contact 52/a (closed breaker only) (A6631F5) shows the
possibility of monitoring the circuit only when the breaker is closed. In this case resistance R is not used, but it must
be observed in the element logic that the corresponding signal CONT IP_F_CC16 (SUP_COIL2) is activated
showing a failure when the breaker is open. Therefore it is required to supervise the continuity failure signaling by the
breaker status information.
Figure 5-41: Trip circuit and trip coil supervision, auxiliary contact 52/a (closed breaker only) (A6631F5)
Figure 5-42: Supervision application with auxiliary contacts 52a and 52b (A6631F4)
Table 5-90: Supervision algorithm with double voltage supervision scheme
Status of Involved Elements Inputs to 650 Decision
CIRCUIT OUTPUT BREAKER STATUS OPERAND OPERAND OPERAND
STATUS STATUS CONT IP_X_CC11 CONT IP_X_CC12 CONT IP_X_CC16
(F35-F36) (Va_COIL2) (Vb_COIL2) (SUP_COIL2)
V 52/a (F15-F16) V 52/b (F17-F18)
There is a possibility to monitor the trip circuit continuity not only via its auxiliary contact 52/a, but also with auxiliary
contact 52/b. This avoids the need to install a resistance in parallel with auxiliary 52/a. The correct connection is
shown on Figure 5-42: Supervision application with auxiliary contacts 52a and 52b (A6631F4)
The circuit works in a similar way to the one described in the previous section, but it uses both supervision inputs
F15-F16 and F17-F18.
The advantage in this case is that circuit supervision with 52 open is more complete, as input V 52/b is used through
contact 52/b, (that is closed when the breaker is open).
We must point out that in this scheme, the tripping contact, shown in the example as the F650 trip relay, can be the
one in the relay (terminals F35 and F36), or be provided by another protection or by the parallel of several
protections. This provides high flexibility in the use of this circuit.
The battery voltage can also be monitored, by using one of the standard digital inputs.
5.6.5.7 With double voltage supervision and serial resistor in voltage monitors
Figure 5-43: Supervision application, auxiliary contacts 52a and 52b and series resistor in F15-F16shows the
supervision scheme with an external resistor.
An external series resistor is used with the 52a voltage monitor to prevent CB tripping with a short-circuited voltage
monitor. With CB open, 52/a is open and 52/b is closed. A shorted 52/a voltage monitor does not cause a trip
because 52/b voltage monitor is current limited to 2mA. With a shorted 52/b voltage monitor, no false trip is
performed because 52/a is in series limiting current to 2mA.
Figure 5-43: Supervision application, auxiliary contacts 52a and 52b and series resistor in F15-F16
Hardware and software is provided to receive signals from external transducers and convert these signals into a
digital format for use as required. The relay accepts inputs in the range of –1 to +20 mA DC, suitable for use with the
most common transducer output ranges; all inputs are assumed to be linear over the complete range.
The Input Range setting specifies the mA DC range of the transducer connected to the input channel.
• Range: -1 to 0, 0 to 1, -1 to 1, 0 to 5, 0 to 10, 0 to 20, 4 to 20.
The Min and Max Value settings are used to program the span of the transducer in primary units.
• Min Value: -9999.99 to 9999.99
• Max Value: -9999.99 to 9999.99
Text assignment for virtual input is made at Setpoint > Relay Configuration > Virtual Inputs. It should be taken
into account that the text assigned for virtual inputs in the relay configuration screen are only for file management,
they are not sent to the relay.
These virtual output latched may be reset by a PLC setting as it is shown in the following figure
5.8 Testing
5.8.1 Force IO–input testing
The input testing can only be performed in relay with graphical display, see the human interfaces section in this
manual for more detailed information.
5.9.1 Outputs
Configuration of contact output operates and reset signals for all boards available in the device:
To configure any output it is necessary to select the output to be configured, clicking on the checkbox in the select
column and choose the logic operand in the source column. Simple logics can be performed on this screen, using
the “or” and “not” columns, for more complex logics go to the logic configuration tool to create the virtual outputs and
afterwards select it in the source column.
The different options available in this screen are the following:
• Select checkbox enables each output. The output must be enabled before modifying any other setting on that
output
• Name setting for defining identification for the output. Note: nor the Output name, nor the Input name, nor the
Virtual Input name is recorded into the relay.
• Source setting for defining a function, logic, remote input, digital input, etc. that activates the contact.
• OR checkbox for configuring the output operation by activation of any of the indicated signals. The element
performs an OR of the signals, and its output produces operation.
• NOT checkbox for inverting or not the configured logic.
5.9.2 LEDs
F650 has 15 LEDs fully configurable from any logical variable, contact or virtual input. For firmware version below
7.20, the first five are latched by hardware, the rest are self reset but can be latched through PLC Configuration. For
firmware version 7.20 or higher, all these LEDs can be individually configured as latched or self-reset. This new
setting is accessible from Setpoint > Relay Configuration > LED.
This window displays all relay LEDs with the following setting options for each one:
• Select checkbox enables each LED. The LED must be enabled before modifying any other setting on that LED
• Name setting for defining identification for the LED
• Source setting defines which function; logic, remote input, digital input, etc. activates the LED.
• OR checkbox for configuring the LED operation by activation of any of the indicated signals. The element
performs an OR of the signals, and its output produces operation.
• NOT checkbox for inverting or not the configured logic.
• For firmware version 7.20 or higher, latched checkboxes are available for configuring the LEDs. If it is selected,
LED shall work as latched, if it is deselected, LED shall work as self-reset.
From the LED configuration screen, it is possible to print the vertical LED label for the relay. For this purpose, click
the printer icon. The label obtained is similar to the default factory label, with black background and the LED texts in
white. This label can replace the original one under the black plastic cover. The label is also provided in word format
and can be modified by the user (e.g. different color marking)
5.9.3 Operations
This menu option shows the settings for the 24 control operations that can be programmed, as follows:
• Select checkbox enables the desired operation.
• Command Text setting defines the command name.
• Interlocks Type setting defines the desired interlock type (An interlock is a condition that must be fulfilled for an
operation to be performed). The possible options are Logic or None. If the LOGIC option is selected, the
program enables a new window for creating the logic. If the NONE option is selected, then the following setting
(Interlocks) is irrelevant.
• Interlocks setting define the desired interlocks. This setting is enabled selecting the “logic” option in “Interlock
type”. In the “Interlock logic” screen we can set the interlock logic, as shown on Figure 5-48: Operations and
interlocks
The settings on this screen allow creating a logic configuration with up to 3 AND gates and 1 OR gate for each of
the 24 operations available in the relay. These settings are:
Select – Enables/disables the selection for the interlock input
Source – Selects a function, digital input, logic, etc. for defining each input of each AND gate.
NOT – Logic inverter
• Final State Type setting: defines whether the operation requires (in addition to the interlock logic) any other
conditions to determine a “success condition”. If so, we must select LOGIC. Otherwise, we must select NONE.
• Final State setting: defines the success condition of a programmed operation, if the previous setting (Final
State type) was set as LOGIC.
• Front Key setting: defines the front pushbutton from which the operation can be executed.
• Contact Input setting: defines whether the operation can be executed by digital input. It defines the digital input
to be used for this purpose.
• Virtual Output setting: defines whether the operation can be executed from a virtual output previously defined
at the logic configuration tool (PLC logic).
• Time Out setting: defines the period during which the operation command remains activated waiting for a
success condition. If the success signal is received before this period expires, the command signal is removed
and the timer reset. If the success condition is not received within this period of time, the operation is considered
to be finished.
Operations Logic
Without interlock
logic
Condition 1
Interlocking
Condition n
Condition 1
Condition 1
Interlocking
Condition n
Keyboard
Push button Operation
Digital input
Condition 1
Success
Condition n
Finally, configure a contact output to be activated with the programmed Operation (Operation1).
This is done under Setpoint > Relay Configuration > Output, selecting an output and choosing the internal signal
OPERATION BIT 1, which corresponds to the bit that is activated when the related operation is executed.
5.9.6 Oscillography
This menu is used for selecting the digital channels to be included in oscillography records, and the oscillo trigger
signal. As for the above-described settings, the trigger selection can be any of the signals provided by the relay or a
logic combination of these.
settings are described below:
• Select checkbox enables or disables a digital channel and the oscillography trigger.
• Name setting defines the name of the digital channel to be included in oscillography records.
• Source setting defines the source or signal to be recorded in that specific channel, which can be selected
among all the operands available in the signals menu.
• NOT checkbox inverts the enabled digital channel signal.
• OR checkbox to select a group of operands instead of a single one. The relay performs an OR of the signals,
and its output produces operation.
NOTE This screen is used for the configuration of digital channels and oscillography trigger. The rest of
parameters, such as function enabling/disabling, sampling rate, number of oscillography files, etc. must be
set on the Setpoint > Product Setup > Oscillography menu.
ACTIVE status is shown on the display (relay HMI), showing an ON label on the right of the alarm. The PC shows the
alarm text in red.
ACKNOWLEDGED: Operation acknowledgment can be performed from three independent channels: MMI-COM2
(local), COM1 (remote) and ETH_1/ETH2 or ETH_E/ETH_A/ETH_B (Ethernet). Inactive alarms disappear from the
HMI when being acknowledged.
HMI: Acknowledged status is shown on the HMI with a selection mark on the right of the ON label.
EnerVista 650 Setup: the acknowledged status is shown by a check mark to the left of the Operation name.
5.9.8 Switchgear
This menu is used for defining the SWITCHGEAR elements to be controlled by the relay. A switchgear element can
be a breaker, a line selector switch, a grounding selector switch, a busbar selector switch, etc. It is possible to define
up to 16 switchgear elements. The settings are as follows:
• Select checkbox: enables or disables the control of a new switchgear element
• Contacts setting: allows selecting which type of contact is used for monitoring the status (open/closed) of the
element. The selection can be: 52a (contact type A, showing the same status as the represented element), 52b
(opposite status to the represented element), 52a+52b (both types of contacts are used), NONE (no status
monitoring).
• Opening Time setting: defines the maximum opening time of an element. It is used for issuing an opening time
failure signal if the element opening is not produced within this time.
• Closing Time setting: defines the maximum closing time of an element. It is used for issuing a closing time
failure signal if the element closing is not produced within this time.
• Contact A checkbox: allows selecting which operand or combination of operands activate the type A contact
status. Usually it is an input contact wired to type A contact of the element (Breaker/selector switch). This
column and the next two columns are only active if the selected contact type in the Contacts column is 52a or
52a+52b.
• OR checkbox: selects a group of operands instead of a single one. The relay performs and OR of the signals,
and its output produces operation.
• NOT checkbox inverts the status of the signal selected in column Contact A.
• Contact B checkbox: allows selecting which operand or combination of operands activates the type B contact
status. Usually it is an input contact wired to type B contact of the element (Breaker/selector switch). This
column and the next two columns are only active if the selected contact type in the Contacts column is 52b or
52a+52b.
•OR checkbox selects a group of operands instead of a single one. The relay performs OR of the signals, and its
output produces operation.
•NOT checkbox inverts the status of the signal selected in column Contact B.
• Open text setting: allows associating a text to the control event associated with the element opening.
• Close text setting: allows associating a text to the control event associated with the element closing.
• Error 00 text setting: in case of using double contact for the switchgear element status (52a+52b), this setting
allows to associate a text to the Error00 internal status, this means, when both contacts are inactive during a
period longer than the associated with the opening or closing Operation, depending on which Operation is being
performed.
• Error 11 text setting: in case of using double contact for the switchgear element status (52a+52b), this setting
allows to associate a text to the Error11 internal status, this means, when both contacts are active during a
period longer than the associated with the opening or closing Operation, depending on which Operation is being
performed.
• ALARM setting: enables the issue of an alarm in the event of a close, open, 00-type, 11-type error. If it is
configured as an alarm.
• Opening init setting: this setting selects which operand or combination of operands indicate the initiation of an
opening operation, in order to allow the follow up of the operation and generate the corresponding alarms if the
operation is not successful. The operation bit signal used to launch the opening init must be configured in the
operations tab inside relay configuration.
• Closing init setting: this setting selects which operand or combination of operands indicate the initiation of a
closing operation, in order to allow the follow up of the operation and generate the corresponding alarms if the
operation is not successful. The operation bit signal used to launch the closing init must be configured in the
operations tab inside relay configuration.
• Block Open: allow selecting which operand or combination of operands activates the opening blocks for the
switchgears (XSWI$ST$BlkOpn and XSWI$ST$BlkCls) for operating in 61850.
• Block Close settings: allow selecting which operand or combination of operands activates the closing blocks
for the switchgears (XSWI$ST$BlkOpn and XSWI$ST$BlkCls) for operating in 61850.
On the left side of the window all the available elements to be programmed on the HMI are displayed. Their meaning
is detailed on the right.
Table 5-94: Active configurable symbols in online diagram for graphical HMI
ACTIVE SYMBOLS
ICONS IN SCREEN DESCRIPTION
SWITCHGEAR SYMBOLS STANDARD AND IEC 1082-1 SWITCHGEAR SYMBOLS
STANDARD SWITCHGEAR SYMBOLS M and C selection for graphic display option in the order code
Switchgear elements: breaker (square) and selector switch (rhombus), in
vertical and horizontal positions.
It is necessary to associate the figure to its corresponding switchgear
number. The figure is shown filled if the element is closed, and blank if the
element is open. The symbol on the right represents an unpluggable
breaker. In this case it is necessary to indicate which operands show
whether the element is plugged or unplugged. The figure shows also
graphically these two statuses.
IEC SWITCHGEAR SYMBOLS N and D selection for graphic display option in the order code
Breakers and breaker trucks in vertical and horizontal positions.
The first fourth symbols are breakers in vertical and horizontal positions
for left and right options. The last fourth symbols are breaker trucks or
unpluggable breakers. When the device is connected two arrows can be
seen, if the device is not connected only one arrow is displayed. When
the device it is inserted the device can be seen and when it is not inserted
only a blank space is displayed
ACTIVE SYMBOLS
Icons On Screen Description
DATE AND TIME SYMBOL
Display the date and time provided by the device in the HMI.
OPERATIONS SYMBOL
Configure and execute operations on the graphic display.
This symbol can only be selected once the operations have been
configured in the Operations screen of the Relay Configuration menu.
To select an Operation, click the element and then the display. A window
opens to select the operation and the tab order. Once selected, a red
border square is shown. Place this square on the object to operate. When
the object is selected on the screen to execute this operation, the object
on which it is located blinks. It is possible to place several operations on
the same object, for example to open and close the breaker object.
Configure and execute operations with the front keys "I" and "O" on the
graphic display over an object selected.
To select the object, click the element and then the display. A window
opens to select the required operations "I" and "O" and the tab order.
Once selected, a blue border square is shown. Place this square on the
object to operate. When the object is selected on the screen to execute
these operations, the object on which it is located blinks. Press key "I" or
"O" to execute the configured operations.
Configure and execute operations with the front keys "I", "O" and "*" on
the graphic display over an object selected.
To select the object, click the element and then the display. A window
opens to select the required operations "I", "O" and "*" and the tab order.
Once selected, a green border square is shown. Place this square on the
object to operate. When the object is selected on the screen to execute
these operations, the object on which it is located blinks. Press key "I",
"O" or "*" to execute the configured operations.
After executing this kind of operation, information about the result of the
operation is displayed on the HMI.
Configure and execute virtual inputs with the front keys "I" and "O" on the
graphic display over an object selected.
To select the object, click the element and then the display. A window
opens to select the required virtual operations "I" and "O" and the tab
order. Once selected, a white border square is shown. Place this square
on the object to operate. When the object is selected on the screen to
execute this virtual inputs, the object on which it is located blinks. Press
key "I" or "O" to set the configured virtual inputs.
Two and three winding voltage transformers Only for N model (IEC selection)
representation.
Symbol for vertical capacitor banks. Only for N model (IEC selection).
Symbol for open delta and delta connection Both M and N selection
For the extended graphic symbols, extraction device must be set to 52a+52b switchgear device.
EXTENDED
GRAPHIC AND TEXT EDITION SYMBOLS
ICONS IN SCREEN DESCRIPTION AVAILABILITY
Breaker Only for N model (IEC selection)
Different Text properties (Bold/Vertical/Reverse Video) Only for N model (IEC selection)
5.10.1.1 Description
As already mentioned in the introduction, this tool uses FBD mode of IEC 61131-3 standard. For this purpose we
have defined a series of basic operations with illustrations below.
The basic operations available in the PLC Editor are located in the tool bar of the application and are as follows:
Table 5-97: PLC editor basic operation in F650
PLC EDITOR BASIC OPERATION
ICONS IN DESCRIPTION
SCREEN
INPUT TO LOGIC: Selection of the digital input to the logic. (All available internal status can be used as logic
inputs **)
OUTPUT FROM LOGIC: Virtual output built with internal logic. (Up to 512)
LIBRARY: Possibility to build blocks of logic in a simple graphic object. OR and AND from 3 to 8 inputs are
provided as libraries.
AND of two digital inputs.
ONS: signal to pulse an logic input to a signal of one scan cycle length.
TIMER: timer signal with set, reset and mask for timing.
Flip-Flop D: signal that maintains the actual value frozen during a PLC cycle
For firmware 7.20 or above, analog operands are available. It is possible to use these operands with analog or digital
values.
The basic operations available in PLC Editor are located in the tool bar of the application and are as follows:
**NOTE1: For firmware version 7.20 or above, two new inputs have been added; PLC_BOOL_ON and
PLC_BOOL_OFF. These two inputs are set always to PLC_BOOL_ON =1 and PLC_BOOL_OFF =0 and their values
are not accessible via protocol and cannot be modified.
Example of logic signals in F650 logic configuration:
Table 5-98: Logic signals in F650
LOGIC SIGNALS EXAMPLES
SIGNAL DESCRIPTION TIME DIAGRAM
SET When the input
signal is set to 1
1
the output signal
remain fixed to 1 0
until a reset signal
is received.
1
0
RESET When the input
signal is reset to 1
1
the output signal
remain fixed to 0. 0
1
ut
0
ONS The input signal is
pulsed. The width 1
of the output pulse
is the same as that 0
of the PLC cycle
1
ut
0
TIMER With selectable
time (MASK), one 1
SET input and one SET input
RESET input 0
1
RESET input
0
1
Output
0
T(ms) T1 T2 T1+T2=T
Digital Variables:
1. If Latched Virtual input 1 =0 & Latched
Virtual input 2 =0 then Virtual output is
set to 0
2. If Latched Virtual input 1 =1 & Latched
Virtual input 2 =1 then Virtual output is
set to 0
3. If Latched Virtual input 1 =1 & Latched
Virtual input 2 =0 then Virtual output is
set to 1
4 If Latched Virtual input 1 =0 & Latched
Virtual input 2 =1 then Virtual output is
set to 0
EQUAL TO Analog Variables:
4. If Vb Angle > Vc Angle then Virtual
output is set to 0
5. If Vb Angle = Vc Angle then Virtual
output is set to 1
6. If Vb Angle < Vc Angle then Virtual
output is set to 0
Digital Variables:
5. If Latched Virtual input 1 =0 & Latched
Virtual input 2 =0 then Virtual output is
set to 1
6. If Latched Virtual input 1 =1 & Latched
Virtual input 2 =1 then Virtual output is
set to 1
7. If Latched Virtual input 1 =1 & Latched
Virtual input 2 =0 then Virtual output is
set to 0
8. If Latched Virtual input 1 =0 & Latched
Virtual input 2 =1 then Virtual output is
set to 0
MULTIPLIER Result of multiplication of both inputs is
stored into variable assigned to Multiplier
output
DAT OPERATION
COMPILATION
PLC
EQUATIONS
PLC
A single equation is composed of one or more inputs, one or more operations, and one output. The order of
equations is determined by the relative position of their outputs.
In the following example is shown the order of compilation for equations determined by their relative position in the
configuration file:
In this case, equation A is the first to be executed. However, in the second case, the first equation to be executed
would be B, as its output is before the Equation A output.
File menu
The FILE menu includes the following options:
New Project: Create a new project that includes the logic configuration files.
Open Project: Open an existing project.
Close Project: Close the currently open project.
Import***: Obtain the PLC project information (*.pep, *.aut, *.lib files) from another *.650 file
(firmware version 7.70 or above) to insert in the open *.650 file.
Export***: Extract the PLC project information (*.pep, *.aut, *.lib files) from the open *.650
configuration file, and save it to the local PC.
Get Project from Relay**: Retrieve a previously saved project from the relay.
Save Project / Save Project as**: Save the open project.
Save Automatic Function &
Save Automatic Function As**: Save the file of the active project.
Library: Give access to the library sub-menus, where new libraries can be created and
existing libraries can be modified and saved.
Print: Print the active configuration file.
Preview: Preview of the document before printing.
Exit: Close all open projects and exit the application.
***Option only available for firmware v7.70 or above.
** Option only available for firmware below v7.70.
Project menu
The Project menu includes the following options:
Project Explorer: Display a tree structure showing all files contained in the project.
Insert library: Insert a library in the active automatic function.
Edit menu
The Edit menu includes the following options:
Undo: Undo the last modification in the active function.
Redo: Repeat the last modification.
Cut: Cut one or more logic operations.
Copy: Copy one or more logic operations.
Paste: Paste one or more logic operations.
Find: Search for a logic operation in the project.
Copy as Bitmap: Copy the active automatic function to the clipboard in picture format.
View Clipboard: Launch the clipboard viewer application.
Run menu
The RUN menu includes the following options:
Configuration: Not valid in the current application (for analog operations still not available).
Compile: Compile the configuration functions to generate the equations that are interpreted
by the 650 PLC.
Save Configuration file***: Save compiled equations into *.650 configuration file
***Option only available for firmware v7.70 or above.
View menu
The VIEW menu includes the following options:
Log: Display the status name and time stamp of the digital statuses configured in
the PLC logic (still not available).
Equations: Display the equations resulting from the compilation.
Grid: Show or hide the form grid where the configuration functions are developed. It
also aligns the different objects to the grid.
Zoom: Allow selection of the percentage of zoom in the application.
Rectangle Zoom (Zoom rectangular): Allow zooming the selected rectangle.
These libraries are saved in the LIB folder in order to be used in further projects
Digital signals:
To configure a new signal, set the Procome ID selected for that signal, select the digital signal, and then click Add to
add the new signal to the status list of signals configured in the Procome configuration file. To remove an existing
signal from the status list, select the signal and click Remove. To save the data in the configuration file, click Save;
all data is stored in the "f650procome.cfg" file.
Analog Measurements
In the measurements configuration screen, for each measurement selected the configuration signals are:
• Procome ID: the identification number for each measurement
• Identifier: the measurement selected to be sent in the Procome slave answer
• Factor: the multiplier factor to be applied to the relay measurement to make the final measurement calculation to
be sent to the master
• Offset: an offset factor to be applied to the relay measurement to make the final measurement calculation to be
sent to the master
The Factor and offset parameters allow the user to perform different scaling in the relay measurements. The final
measurement sent to the Procome master is: a*x+b, where x is the relay measurement, a is the multiplier factor and
b is the offset.
Counters
The counters (pulse counters and energy counters) have the same management as the measurements, this is
Procome ID, Identifier, Factor and offset configuration for each of them.
Operations
This operations configuration screen allow the user to configure the Procome number that identifies the command in
the Procome protocol and the "operation bit number" that the slave when the command has DCO_ON and the
operation to be executed when the command is DCO_OFF. The user can set the same operation for DCO_ON and
DCO_OFF or a different one for each status if desired.
The user must select:
• Procome ID (IEC): which is the identification number for each operation
• Type: type 1 for operation bits.
• Operation ON: DCO_ON operation bit selection
• Operation OFF: DCO_OFF operation bit selection
Counters Operations
The counter operations screen is a dedicated configuration screen for the counter (pulse and energy) operations to
freeze, unfreeze and reset.
These operations must be set in the "Setpoint > Relay configuration > Operations" and "Setpoint > Relay
configuration > Protection Elements" in FREEZE ENERGY CNT, UNFREEZE ENERGY CNT and RESET ENERGY
CNT.
For example if the ENERGY RESET operation is the 6th one in the operations screen, it must be configured to the
"ENERGY RESET CNT" input in the protection elements screen. To configure this operation to be launched through
Procome see the example below. This configuration screen has the same management as the operations one.
Digital states:
All the digital states that F650 supports are available in order to be mapped using the EnerVista 650 Setup program.
All the mapped information is sent as a response to a general interrogation.
In the interoperability table, the states that the standard propose have been selected with the suitable information
number. Some of them must be generated in the firmware code as an OR operation. This information is mapped by
default, but the user can delete them if desired. For the other states, you can assign the Information Number
<1..255> and the Function Type <0..255>, but the Identification Type 1 (Time-tagged message) is fixed.
• To configure a new mapping of a digital state, set the Function Type and the Information number. Then select
Digital Status from the first combo box in the Status frame for mapping a single digital state, and the digital
state to be sent to the IEC103 master from the second combo box. You can configure a logic OR operation of
digital states selecting Logic in the first combo box and clicking Press for Logic. In the next screen, choose the
digital status combination to be sent to the IEC103 master and click Save.
Finally click Add and the configured data is added to the Status List.
• To remove an existing signal from the status list, select the signal then click Remove. The signal is removed
from the status list.
• In the same way, to change a configured signal from the status list, select the signal, make the changes, and
then click Update. The signal is updated in the status list
• To save the data in the configuration file, click Save and all the data is stored in the corresponding "*.cfg" file.
Measurands
The standard proposes some analog points supported by the F650 with compatible information number that has
been included in the previous profile.
For the other measurands, it would be possible to use the 650 EnerVista Setup to select the desired point and assign
the Identification Type (3 or 9), Function Type <0..255>, and Information Number <1..255>.
If the user selects Identification Type 3 (ASDU 3) only four measurands are available for the configuration, but if
Identification Type 9 (ASDU 9) is selected, up to nine measurands can be sent in the IEC103 slave answer. For each
measurand, all metering values that F650 supports, are available in order to be mapped.
In the measurands configuration screen, with each selected measurement, a Factor and an Offset must be
configured. The Factor is a multiplier factor and the Offset is an offset factor to be applied to the relay measurement
to make the final measurement calculation to be sent to the master The factor and offset parameters allow the user
to perform different scaling in the relay measurements. The final measurement sent to the IEC103 master is:
"a*x+b", where "x" is the relay measurement, "a" is the multiplier factor and "b" is the offset.
The measurands are sent to the primary station as a response to a class 2 request. There is a Timeout configurable
with increments of 100 ms, between 0 and 60 min, in order to configure the interval desired.
Click Add and the configured data is added to the Measurands List. The processes of removing, updating and
saving are done in the same way as for digital states.
Commands
All configurable commands and virtual inputs self-reset are available in order to be mapped using the EnerVista 650
Setup program. It would be possible to choose the desired command for the ON state and the same or different
command for the OFF state.
You can select the Information Number <1..255> and the Function Type <0..255>, but the Identification Type 20
(General Commands) is fixed and it is used to send a command to the slave station.
Clicking the Add button the configured data is added to the Operations List. The processes of removing, updating
and saving are done in the same way as for digital states and for measurands.
ACTUAL VALUES
6.1.1 LEDs
Operation of the relay front LEDs is shown on the following figure (Actual > Front Panel > LEDs) by the lighting of
the associated LED in the appropriate color. The Ready LED is green when the relay is in service. LEDs 1 to 5 light
up in red when active, LEDs 6 to 10 light up in orange, and the last 5 LEDs light up in green.
The first five LEDs are latched by hardware and can
only be reset by a LEDs RESET Command, either pressing the “esc” key on the Front of the Relay, or by
Communications using the appropriate signal. The rest of LEDs are not latched, but can be latched by logic.
Table 6-1: Front panel LEDs
LEDS
READY LED
LED 1
LED 2
LED 3
LED 4
LED 5
LED 6
LED 7
LED 8
LED 9
LED 10
LED 11
LED 12
LED 13
LED 14
LED 15
LOCAL OPERATION MODE
OPERATIONS BLOCKED
ST HMI BACKLIGHT
6.2 Status
6.2.1 Operation bits status
(Actual > Status > Operation bits)
OPERATION BIT 1...24 These 24 bits are the outputs of each possible Operation modules, programmed in menu
Setpoint > Relay Configuration > Operations. The light up LED indicates their status 1
(activation)
OPERATION BITS
OPERATION BIT 1
OPERATION BIT 2
…
OPERATION BIT 24
BREAKER STATUS
BREAKER OPEN
BREAKER CLOSED
BREAKER UNDEFINED
BREAKER OPEN: Open breaker status. In the switchgear selected as breaker, besides providing the usual
switchgear contact status, the system provides also the open breaker, closed breaker, and
undefined breaker states.
BREAKER CLOSED: Breaker closed.
BREAKER UNDEFINED: If there are two digital inputs configured for breaker contacts 52/a and 52/b, this status is
present when both inputs are at 0 or at 1. This status can be caused by a wiring failure,
failure of auxiliary elements, etc.
SENSITIVE GROUND IOC SENSITIVE GROUND TOC ISOLATED GROUND ACTUAL SENSITIVE GROUND DIRECTIONAL
ACTUAL VALUES ACTUAL VALUES VALUES ACTUAL VALUES
SENS GND IOC1 PKP SENS GND TOC1 PKP ISOLATED GND1 PKP SENS GND DIR1 BLOCK
SENS GND IOC1 OP SENS GND TOC1 OP ISOLATED GND1 OP SENS GND DIR1 OP
SENS GND IOC2 PKP SENS GND TOC2 PKP ISOLATED GND2 PKP SENS GND DIR2 BLOCK
SENS GND IOC2 OP SENS GND TOC2 OP ISOLATED GND2 OP SENS GND DIR2 OP
SENS GND IOC3 PKP SENS GND TOC3 PKP ISOLATED GND3 PKP SENS GND DIR3 BLOCK
SENS GND IOC3 OP SENS GND TOC3 OP ISOLATED GND3 OP SENS GND DIR3 OP
6.2.3.8 Voltage
This screen shows the activation of all voltage elements available in the F650. It can be accessed from the menu:
Actual > Status > Protection > Voltage, and it includes the following signaling LEDs.
The values shown are:
Pickup and operation signals for phase to ground and phase-to-phase undervoltage elements and the three-phase
signal for pickup and operation for the undervoltage element.
Pickup and operation for negative sequence overvoltage element.
Pickup and operation signals for phase-to-phase overvoltage elements and the three-phase signal for pickup and
operation for the overvoltage element.
Pickup and operation for neutral overvoltage elements (High and low).
Pickup and operation for auxiliary undervoltage and overvoltage elements.
Table 6-9: Voltage actual values
6.2.3.9 Power
Forward Power and directional power elements
These functions may have several applications, for example, small generating plants connected to the power
system, to limit the supplied power and not to exceed its rated capacity.
If programmed conditions for any of the three elements are met, the corresponding LEDs lights up.
This screen shows the activation of all power elements available in the F650. It can be accessed from the menu:
Actual > Status > Protection > Power, and it includes the following signaling LEDs.
Table 6-10: Power actual values
Forward Power Actual Values Directional Power Actual Values Wattmetric Ground Fault Actual Values
FWD PWR1 STG1 PKP DIR PWR1 STG1 PKP 32N1 HIGH PKP
FWD PWR1 STG1 OP DIR PWR1 STG1 OP 32N1 HIGH OC PKP
FWD PWR1 STG2 PKP DIR PWR1 STG2 PKP 32N1 HIGH OP
FWD PWR1 STG2 OP DIR PWR1 STG2 OP 32N2 HIGH PKP
FWD PWR2 STG1 PKP DIR PWR1 STG PKP 32N2 HIGH OC PKP
FWD PWR2 STG1 OP DIR PWR1 STG OP 32N2 HIGH OP
FWD PWR2 STG2 PKP DIR PWR2 STG1 PKP 32N3 HIGH PKP
FWD PWR2 STG2 OP DIR PWR2 STG1 OP 32N3 HIGH OC PKP
FWD PWR3 STG1 PKP DIR PWR2 STG2 PKP 32N3 HIGH OP
FWD PWR3 STG1 OP DIR PWR2 STG2 OP 32N1 LOW PKP
FWD PWR3 STG2 PKP DIR PWR2 STG PKP 32N1 LOW OC PKP
FWD PWR3 STG2 OP DIR PWR2 STG OP 32N1 LOW OP
DIR PWR3 STG1 PKP 32N2 LOW PKP
DIR PWR3 STG1 OP 32N2 LOW OC PKP
DIR PWR3 STG2 PKP 32N2 LOW OP
DIR PWR3 STG2 OP 32N3 LOW PKP
DIR PWR3 STG PKP 32N3 LOW OC PKP
DIR PWR3 STG OP 32N3 LOW OP
Wattmetric Ground Fault Power
Measurement Actual Values
32N1 HIGH POWER
32N2 HIGH POWER
32N3 HIGH POWER
32N1 LOW POWER
32N2 LOW POWER
32N3 LOW POWER
6.2.4.1 Frequency
F650 units incorporate three overfrequency and three underfrequency units. For each of them there are two
magnitudes pickup and trip (operation).
Frequency elements are often used in generating plants, as well as in the connection of substations to the main
system. Frequency monitoring is the base for synchronous machines protection application, with a couple of setting
levels, as well as for the development of automatic shedding functions and underfrequency reset.
This screen shows the activation of all frequency elements available in the F650. It can be accessed from the menu:
Actual> Status > Control Elements >Frequency, and it includes the following signaling LEDs.
Table 6-11: Frequency actual values
OVERFREQUENCY ACTUAL VALUES UNDERFREQUENCY ACTUAL VALUES
OVERFREQ1 PKP UNDERFREQ1 PKP
OVERFREQ1 OP UNDERFREQ1 OP
OVERFREQ2 PKP UNDERFREQ2 PKP
OVERFREQ2 OP UNDERFREQ2 OP
OVERFREQ3 PKP UNDERFREQ3 PKP
OVERFREQ3 OP UNDERFREQ3 OP
OVERFREQ4 PKP UNDERFREQ4 PKP
OVERFREQ4 OP UNDERFREQ4 OP
OVERFREQ5 PKP UNDERFREQ5 PKP
OVERFREQ5 OP UNDERFREQ5 OP
OVERFREQ6 PKP UNDERFREQ6 PKP
OVERFREQ6 OP UNDERFREQ6 OP
FREQUENCY RATE OF CHANGE ACTUAL
VALUES
FREQ RATE1 PKP
FREQ RATE1 OP
FREQ RATE2 PKP
FREQ RATE2 OP
FREQ RATE3 PKP
FREQ RATE3 OP
6.2.4.2 Synchrocheck
This screen can be accessed at Actual> Status > Control Elements > Synchrocheck, and it includes the following
signaling LEDs for the synchronism check function:
Table 6-12: Synchrocheck actual values
SYNCHROCHECK ACTUAL VALUES
Synchrocheck BLK INP
Synchrocheck OP
SYNCHK CLOSE PERM
Synchrocheck COND OP
DL-DB OPERATION
DL-LB OPERATION
LL-DB OPERATION
SLIP CONDITION
BUS FREQ > LINE FREQ
BUS FREQ < LINE FREQ
VOLTAGE DIFFERENCE
FREQUENCY DIFFERENCE
Synchrocheck BLK INP: Block signal for the synchrocheck unit, configurable at Setpoint > Relay
Configuration > Protection Elements
Synchrocheck OP: Closing permission signal in live line-live bus conditions with open breaker.
SYNCHK CLOSE PERM: General Closing permission of the Synchronism unit. It contemplates all possible
situations, live line-live bus conditions, and the closing permission logics (dead
line-dead bus, live line- dead bus, dead line-live bus). Note: in case the Function
is disabled, the Closing permission signal is activated in order not to interfere with
possible logics where it is included. If the synchronism unit is enabled, this signal
only activates under the closing conditions established by setting.
Synchrocheck COND OP: Closing permission according to permission logics (DL-DB, LL-DB, DL-LB).
DL-DB OPERATION: Closing permission in dead line – dead bus condition.
DL-LB OPERATION: Closing permission in dead line – live bus condition.
LL-DB OPERATION: Closing permission in live line – dead bus condition.
SLIP CONDITION: Internal signal indicating frequency slip between the line voltage and bus voltage
phasors.
BUS FREQ > LINE FREQ: Busbar Frequency higher than line frequency
BUS FREQ < LINE FREQ: Busbar Frequency lower than line frequency
VOLTAGE DIFFERENCE: Voltage difference between the line and the busbar in volts (secondary values),
only available if the Synchrocheck element is enabled.
FREQ. DIFFERENCE: Frequency difference between the line and the busbar in Hz, only available if the
Synchrocheck element is enabled.
6.2.4.3 Autoreclose
This screen can be accessed at Actual> Status > Control Elements > Autoreclose, and it includes the following
signaling LEDs for the Autoreclose function:
Table 6-13: Autoreclose actual values
AUTORECLOSE INPUTS
AR LEVEL BLOCK
AR PULSE BLOCK
AR PULSE UNBLOCK
AR INITIATE
AR CONDS INPUT
AUTORECLOSE INTERNAL STATUS
AR CLOSE BREAKER
AR OUT OF SERVICE
AR READY
AR LOCKOUT
AR BLOCK
AR RCL IN PROGRESS
AR LCK BY ANOMALY
AR LCK BY FAIL OPEN
AR LCK BY FAIL CLOSE
AR LCK BY USER
AR LCK BY CONDS
AR LCK BY TRIPS
AR LCK BY SHOTS
AR BLK AFTER 1 SHOT
AR BLK AFTER 2 SHOT
AR BLK AFTER 3 SHOT
AR BLK AFTER 4 SHOT
AR BLOCK BY LEVEL
AR BLOCK BY PULSE
AR STATUS
AR LOCKOUT MODE
AR BLOCK MODE
AUTORECST_61850
The AUTORECLOSE INPUTS are signal configurable by the user at Setpoint > Relay Configuration > Protection
Elements to:
AR LEVEL BLOCK: programmable signal to block the autoreclose unit by level
AR PULSE BLOCK: programmable signal to block the autoreclose unit by pulse
AR PULSE UNBLOCK: programmable signal to unblock the autoreclose unit by pulse
AR INITIATE: programmable signal to initiate the autoreclose.
AR CONDS INPUT: programmable signal to set the conditions to be met before executing a breaker close.
The AUTORECLOSE INTERNAL STATUS are internal signals provided by the autoreclose unit:
AR CLOSE BREAKER: Breaker close command given by the autoreclose
AR OUT OF SERVICE: Autoreclose out of service (Disabled)
AR READY: Autoreclose in service
AR LOCKOUT: Autoreclose in lockout status (finished cycled-definite trip)
AR BLOCK: Autoreclose blocked (by input, logic, others, etc).
AR RCL IN PROGRESS: Cycle in course (autoreclose in progress).
AR LCK BY ANOMALY: Autoreclose in “Lockout” by anomaly.
AR LCK BY FAIL OPEN: Autoreclose in “Lockout” by a failure in opening the breaker.
AR LCK BY FAIL CLOSE: Autoreclose in “Lockout” by a failure in closing the breaker.
AR LCK BY USER: Autoreclose in “Lockout” by manual close.
AR LCK BY CONDS: Autoreclose in “Lockout” by conditions. See input conditions configuration.
AR LCK BY TRIPS: Autoreclose in “Lockout” by maximum number of trips.
AR LCK BY SHOTS: Autoreclose in “Lockout” at the end of cycle – Definite trip.
AR BLK AFTER 1 SHOT: Signal sent by the autoreclose after the 1st shot.
AR BLK AFTER 2 SHOT: Signal sent by the autoreclose after the 2nd shot.
AR BLK AFTER 3 SHOT: Signal sent by the autoreclose after the 3rd shot.
AR BLK AFTER 4 SHOT: Signal sent by the autoreclose after the 4th shot.
AR BLOCK BY LEVEL: Autoreclose blocked by level. See AR block signals configuration
AR BLOCK BY PULSE: Autoreclose blocked by pulse. See AR block signals configuration
AR STATUS: Autoreclose status (in service – out of service)
AR LOCKOUT MODE: Relay “Lockout” status.
AR BLOCK MODE: Relay “Block” status
AutoRecSt_61850: Autorecloser status sent in IEC 61850. This value represent whether or not the auto reclosing is
ready, in progress or successful. It is an enumerate type whose values are defined in IEC 61850-7-4 Edition 2.0
standard and it is available
BKR FAIL INITIATE External signal for breaker failure initiation. (configurable at Settings> Relay
Configuration > Protection Elements).
BKR FAIL NO CURRENT Signal for breaker failure without current
DIGCNT 8 VALUE
DIGCNT 1 FROZENVALUE
DIGCNT 2 FROZENVALUE
DIGCNT 3 FROZENVALUE
DIGCNT 4 FROZENVALUE
DIGCNT 5 FROZENVALUE
DIGCNT 6 FROZENVALUE
DIGCNT 7 FROZENVALUE
DIGCNT 8 FROZENVALUE
DIGCNT 1 FROZENDATE
DIGCNT 2 FROZENDATE
DIGCNT 3 FROZENDATE
DIGCNT 4 FROZENDATE
DIGCNT 5 FROZENDATE
DIGCNT 6 FROZENDATE
DIGCNT 7 FROZENDATE
DIGCNT 8 FROZENDATE
For each of the 8 digital counters, there exist independent and identical groups of actual values:
• DIGCNT # HI [OFF: ON]: If this bit is activated, the counter value DIGCNT # VALUE is greater than the setting DigCNt
#Compare value.
• DIGCNT # EQ [OFF: ON]: If this bit is activated, the counter value DIGCNT # VALUE is equal than the setting DigCNt
#Compare value.
• DIGCNT # LO [OFF: ON]: If this bit is activated, the counter value DIGCNT # VALUE is lower than the setting DigCNt
#Compare value.
(These 3 previous states are mutually exclusive: only one can be ON at the same time. If the counter is Disabled, the 3 of
them are OFF.)
• DIGCNT # VALUE [-2,147,483,648 : 2,147,483,647]: The specified counter current value.
• DIGCNT # FROZENVALUE [-2,147,483,648 : 2,147,483,647]: The specified counter last captured (frozen) value.
• DIGCNT # FROZENDATE [Valid date]: The specified counter last captured (frozen) date.
60CTS Inhibit
CT Failure PKP
CT Failure OP
SWITCH X A INPUT The LED lights up when the input associated with switchgear Contact A is activated.
SWITCH X B INPUT The LED lights up when the input associated with switchgear Contact B is activated.
SWITCH X A STATUS Status associated with Switchgear contact A. It is activated once the time required for
the Switchgear module to acknowledge contact A has expired.
SWITCH X B STATUS Status associated with Switchgear contact B. It is activated once the time required for
the Switchgear module to acknowledge contact B has expired.
SWITCH X OPEN Lights up when the associated switchgear is open
SWITCH X CLOSED Lights up when the associated switchgear is closed
SWITCH X 00_ERROR Output that represents the Switchgear status 00, considered as abnormal.
SWITCH X 11_ERROR Output that represents the Switchgear status 11, considered as abnormal.
SWITCH X OPEN INIT Programmable input that indicates the initiation of the Opening Operation for the
considered switchgear.
SWITCH X CLOSE INIT Programmable input that indicates the initiation of the closing Operation for the
considered switchgear.
SWGR X FAIL TO OPEN Output that represents a failure to open, from the associated external device (opening
time exceeded)
SWGR X FAIL TO CLOSE Output that represents a failure to close from the associated external device (closing
time exceeded)
SWITCH X OPEN
SWITCH X
CLOSED
Switchgear logic
module SWITCH X
00_ERROR
SWITCH X
11_ERROR
FACTORY CALIBRATION: This value is active when the relay calibration settings are the default values (no
calibration).
CALIBRATION ERROR: Error shown when there is a problem in the calibration settings (wrong values).
CALIBRATION DATE: This value is showing date when relay was calibrated.
6.2.10 FlexCurves
This screen can be accessed at Actual> Status > Flex Curves, and it includes the internal flex curves status.
If the LED associated with the FlexCurve status is lit up, this indicates that the user curve has been configured with
new values (not default values).
Table 6-30: FlexCurve status
FLEX CURVES STATUS
FLEXCURVE A STATUS
FLEXCURVE B STATUS
FLEXCURVE C STATUS
FLEXCURVE D STATUS
Form firmware version prior to 7.00, System Info pop-up window shows general system information as described in
the table below:
Table 6-31: System info for firmware versions below 7.00
SYSTEM INFO
E2PROM STATUS
DSP COMM ERROR
MAGNETIC MODULE ERROR
Green Zone
Yellow Zone
Orange Zone
Red Zone
Kswapd Time
mtd2 Time
mtd2 Time
CPU Rtai
CPU Linux
Total RAM
Used DRAM
Free RAM
Shared RAM
Buffer RAM
Chached RAM
Green Counter
Yellow Counter
Orange Counter
Red Counter
Up Time
DSP Counter
ICD Status
MAC Address
Serial Number
Manufacturer date
• E2PROM status: LED associated lights in green if E2PROM is configured and working properly
• DSP comm error: LED associated lights in green if communication error between DSP and main processor.
• Magnetic module error: LED associated lights in green if communication error between DSP and magnetic module.
• Green/Yellow/Orange/Red Zones and Counters:
These 4 counters are referred to the total amount of free RAM available in the device. The
usual state should be Green zone and the rest of indicators means that the device can
have or stop some task just in case that they would need to prioritize the protection task.
• Kswapd Time: It should take value always to 0
• Mtd2 Time: Time accessing to this partition with Linux OS
• Mtd3 Time: Time accessing to this partition with Application
• CPU Rtai: Percentage corresponding to protection tasks execution
• CPU Linux: Percentage corresponding to rest of Linux tasks execution
• Total RAM: Total RAM in the device
• Used DRAM: Used RAM in the device
• Free RAM: Available RAM in the device
• Chached RAM: Memory reserved for the Linux OS
• Up Time: Second from the last power-up
• DSP Counter: It shows that DSP is running
• ICD Status: Information about status of ICD file stored in the F650. For detailed information go to
Chapter 7, section 7.3.2.2 IEC 61850 CONFIGURATOR FEATURES FOR CONFIGURATION
• MAC address: MAC address assigned to Ethernet ports, Eth_1 and Eth_2.
• Serial number: Serial number of the relay that is communicating with EnerVista 650 Setup.
• Manufacturing date: Date when the relay, connected to EnerVista 650 Setup, was assembled.
Table 6-32: System info for firmware versions 7.00 and above
SYSTEM INFO
E2PROM STATUS
DSP COMM ERROR
MAGNETIC MODULE ERROR
PLC ERROR
NET CONF ERROR
ORDER CODE ERROR
Total RAM
Used DRAM
Free RAM
Up Time
DSP Counter
CPU Usage
ICD Status
ICD Status NOTVAL
DSP Status
FLASH Usage
KINETICS Usage
CPU Max Usage
Temp Current Value
Temp Max Value
Temp Min Value
Scan Cycle Average
Scan Cycle Rate
PLC Checksum
Settings Checksum
MAC Address
Serial Number
Manufacturer date
• E2PROM Status: LED associated lights in green if E2PROM is configured and working properly
• DSP COMM ERROR: LED associated lights in green if communication error between DSP and main
processor.
• Magnetic module error: LED associated lights in green if communication error between DSP and magnetic
module.
• Plc error: PLC equations sent to the relay have an error or are incorrect.
• Net conf error: Network configuration is incorrect
• Order code error: Order code and hardware configuration do not match
• Total RAM: Total RAM in the device
• Used DRAM: Used RAM in the device
• Free RAM: Available RAM in the device
• UpTime: DSP heartbeat
• DSP Counter: Percentage of CPU in use
• CPU Usage: Percentage of CPU in use
• ICD Status: Information about status of ICD file stored in the F650. For detailed information go to
Chapter 7, section 7.3.2.2 IEC 61850 CONFIGURATOR FEATURES FOR CONFIGURATION
• ICD Status NotVal: Information about validation of new ICD after being sent into the relay. For detailed
information go to Chapter 7, section 7.3.2.2 IEC 61850 CONFIGURATOR FEATURES FOR
CONFIGURATION
• Dsp Status: Internal status of the DSP
• Flash Usage: FLASH memory in use
• KINETIS Status: Kinetis working mode
• CPU MAX Usage: Maximum measured CPU usage
• Temp Current Value: Current temperature of CPU. This value is displayed in Celsius units.
• Temp Max Value: Maximum temperature reached by CPU during operating mode. This value is reset
This value is taken into account from last reboot.
• Temp Min Value: Maximum temperature reached by CPU after last reboot.
• Scan Cycle Average: Mean time in nanoseconds that takes a Scan cycle to run
• Scan Cycle Rate: Every milliseconds a Scan cycle is run
• PLC Checksum: Value of CRC of PLC equations. This value is read from the relay.
• Settings checksum: Value of CRC of relay settings. This value is read from the relay.
• MAC address: MAC address assigned to Ethernet port, Eth_E.
• Serial number: Serial number of the relay that is communicating with EnerVista 650 Setup.
• Manufacturing date: Date when the relay, connected to EnerVista 650 Setup, was assembled.
• PreFault values: Prefault values for all the current and voltage units (Modulus (mod), Angle (deg))
• PostFault values: Postfault values for all the current and voltage units (Modulus (mod), Angle (deg))
• R Primary/R Secondary: Primary/Secondary Fault Resistance; this value represents the resistance in primary/
secondary values of the portion of the affected line until the defect.
• Secondary fault resistance: Resistance of Positive sequence x distance / Line Length;
• X Primary/X Secondary: Primary/Secondary Fault Reactance. This value represents the reactance in primary/
secondary values of the portion of the affected line until the defect.
• Secondary fault reactance: Reactance of Positive sequence x distance / Line Length;
• Fault resistance: This value provides the estimated ground fault resistance in primary values of the fault
seen by the F650 by neglecting the resistance of the affected portion of the line.
• Fault report trigg: This signal indicates whether the signal that initiates the calculation of the distance to
the fault has been activated.
• Clear fault reports: This signal indicates the reset of fault reports.
• Fault date: Date and time of the last fault produced in the relay. In format (Day/Month/year
Hour:minutes:seconds.milliseconds)
• Fault type: Type of the last fault produced in the Relay (phase to ground, phase to phase, three-
phase, etc).
• Fault location: Location of the last fault produced in the relay.
• Fault report number: Number of fault reports
6.2.12.3 Oscillography
Actual> Status > Records Status > Oscillography
The following figure shows the status of the different digital channels that can be programmed to be included in
oscillography records. When the signal associated with a specific channel is active, its LED lights up on this screen.
This screen also shows the oscillography trigger status, active or inactive, by lighting up that channel.
Table 6-35: Oscillography status
OSCILLOGRAPHY
OSC DIG CHANNEL 1
OSC DIG CHANNEL 2
OSC DIG CHANNEL 3
OSC DIG CHANNEL 4
OSC DIG CHANNEL 5
OSC DIG CHANNEL 6
OSC DIG CHANNEL 7
OSC DIG CHANNEL 8
OSC DIG CHANNEL 9
OSC DIG CHANNEL 10
OSC DIG CHANNEL 11
OSC DIG CHANNEL 12
OSC DIG CHANNEL 13
OSC DIG CHANNEL 14
OSC DIG CHANNEL 15
OSC DIG CHANNEL 16
OSCILLO TRIGGER
NUMBER OF TRIGGERS
CYCLES PER RECORD
AVAILABLE RECORDS
Values for these last 3 fields are reset every time the oscillography settings are modified.
OLDEST SAMPLE TIME: Date and time of the oldest value stored in the data logger.
NEWEST SAMPLE TIME: Date and time of the most recent value stored in the data logger
DATA LOGGER CHANNELS: Number of channels configured in the data logger
DATA LOGGER DAYS: Time in days during which, samples are stored without overwriting them.
6.2.12.5 Demand
Actual> Status > Records Status > Demand
Table 6-37: Demand status
DEMAND
DEMAND TRIGGER INP
DEMAND RESET INP
DEMAND TRIGGER INP: Signal used for triggering the demand in the case of Rolling demand.
DEMAND RESET INP: Signal to reset the demand.
These signals can be configured at Setpoint > Relay Configuration > Protection Elements
6.2.12.6 Energy
Freeze/Unfreeze/reset Energy:These signals correspond to the relay energy counters statuses of freeze, unfreeze
and reset.
Actual> Status > Records Status > Energy
Table 6-38: Energy status
ENERGY
FREEZE ENERGY CNT
UNFREEZE ENERGY CNT
RESET ENERGY CNT
FREEZE ENERGY CNT: Signal used to freeze the energy counters for measurement purposes.
UNFREEZE ENERGY CNT: Signal used to unfreeze the energy counters.
RESET ENERGY CNT: Signal to reset the energy measurements and set the values to zero.
These signals can be configured at Setpoint > Relay Configuration > Protection Elements
The breaker maintenance inputs are signals that can be configured at Setpoint > Relay Configuration > Protection
Elements:
RESET KI2t COUNTERS Signal to reset and set to zero all the KI2t counters (for all phases)
RESET BKR COUNTERS Signal to reset and set to zero all the breaker counters (number of openings and
closings and alarms)
KI2t PHASE A ALARM Alarm signal for maximum breaking capacity in phase A exceeded
KI2t PHASE B ALARM Alarm signal for maximum breaking capacity in phase B exceeded
KI2t PHASE C ALARM Alarm signal for maximum breaking capacity in phase C exceeded
BKR OPENINGS ALARM Alarm related to the maximum number of breaker openings
BKR OPEN 1 HOUR ALARMAlarm related to the maximum number of breaker openings in one hour
BREAKER OPENINGS Counter of the total number of openings performed by the breaker
BREAKER CLOSINGS Counter of the total number of closings performed by the breaker
KI2t PHASE A kI2t phase A counter (total accumulative breaking level – phase A)
KI2t PHASE B kI2t phase B counter (total accumulative breaking level – phase B)
KI2t PHASE C kI2t phase C counter (total accumulative breaking level – phase C)
BKR OPENING TIME Time to set a failure in opening the breaker.
BKR CLOSING TIME Time to set a failure in closing the breaker.
BKR OPEN TIMING Exact time in opening the breaker
BKR CLOSE TIMING Exact time in closing the breaker
Breaker opening and closing time signals are configured at Setpoint > Relay Configuration > Switchgear for the
related switchgear device.
This screen shows the IRIG-B and PRP status. It includes the following signaling LEDs showing the FAILURE of the
SNTP and IRIG-B and other statuses are provided.
SNTP - IRIGB - PTP1588 STATUS
SNTP FAILURE
IRIG-B FAILURE
RTC Sync Source
GrandMaster-ID LOW
GrandMaster-ID HIGH
PTP ACCURACY
The RTC Sync Source actual value is the time synchronizing source the relay is using at present. Possible sources
are: Port A PTP Clock, Port B PTP Clock, IRIG B, SNTP and None.
Grandmaster ID is the grandmaster Identity code being received from the present PTP grandmaster if any. When
the relay is not using any PTP grandmaster, this actual value is zero. The grandmaster Identity code is specified by
PTP to be globally unique, so one can always know which clock is grandmaster in a system with multiple
grandmaster-capable clocks.
PTP Accuracy is the estimated maximum time error at present in the Real Time Clock (RTC), considering the
quality information embedded in the received time signal, how long the relay has had to lock to the time source, and
in the case of time signal interruptions, the length of the interruption. The value 999,999,999 indicates that the
magnitude of the estimated error is one second or more, or that the error cannot be estimated.
Note:
The F650 does not support the end-to-end delay mechanism, so it is not unexpected that changing the device to
which the F650 is connected to this mode would cause the (NoPDelay) message. When PTP source clock is having
"End to End clock delay” configured, and if F650 is receiving PTP packets from this clock F650 is getting
synchronized and status is showing Synch'd (No Pdelay). Note that the relay does not allow manual overwriting of its
RTC time if PTP is functional.
6.2.14 Versions
This screen can be accessed at Actual > Status > Versions. It shows the current versions and dates of the different
applications.
VERSIONS
HMI Version
DISPLAY TYPE
Boot Version
Boot Date
Kinetis Boot Version
Kinetis Boot Date
Kinetis Loader Ver
Kinetis Loader Date
Kinetis App Version
Kinetis App Date
DSP Version
DSP Date
Firmware Date
FPGA Version
RM PRP HSR Version
RM RSTP Version
RM LLA Version
RM Bypass Version
CPU Revision
DISPLAY TYPE: Relay’s display model (refers to order code, basic or graphic)
1. Basic display
2. Graphic display
3. Chinese Basic
4. Chinese Graphic (IEC symbols)
Boot Version: Boot version
RM PRP HSR Version: Current version of the PRP_HSR bitstream running in the redundancy module FPGA.
RM RSTP Version: Current version of the RSTP-Daisy Chain bitstream running in the redundancy module FPGA.
RM LLA Version: Current version of the LLA bitstream running in the redundancy module FPGA.
RM Bypass Version: Current version of the Bypass bitstream running in the redundancy module FPGA.
CPU Revision: CPU hardware version:
• Redundant Fiber Optic: 0
• Redundant Cooper Cable: 1
• Single Fiber Optic: 2
• Single Cooper Cable: 3
6.2.15 Redundancy
Actual > Status > Redundancy: This screen shows the port A and B statuses related to PRP, HSR and RSTP
protocols.
REDUNDANCY
PRP_HSR A tx
PRP_HSR B tx
PRP_HSR A err
PRP_HSR B err
RSTP PortA State
RSTP PortB State
• PRP_HSR A TX: This is the number of the transmitted messages over port A when PRP or HSR option is
enabled.
• PRP_HSR B TX: This is the number of the transmitted messages over port B when PRP or HSR option is
enabled.
• PRP_HSR A ERR: This value shows the number of messages received over port A with wrong LAN ID.
• PRP_HSR B ERR: This value shows the number of messages received over port B with wrong LAN ID.
• RSTP PortA State: This is the state of RSTP for port A (Discarding, Learning & Forwarding)
• RSTP PortB State: This is the state of RSTP for port B (Discarding, Learning & Forwarding)
6.3 Metering
6.3.1 Primary values
6.3.1.1 Current
Actual> Metering > Primary Values > Current
Description UNITS
CT Ratio N/A
CT Ratio Ig N/A
CT Ratio Isg N/A
Ia Angle Deg
Ib Angle Deg
Ic Angle Deg
In Angle Deg
Ig Angle Deg
Isg Angle Deg
Phasor Ia Primary KA
Phasor Ib Primary KA
Phasor Ic Primary KA
Phasor Ig Primary KA
Phasor Isg Primary KA
Phasor In Primary KA
RMS Ia Primary KA
RMS Ib Primary KA
RMS Ic Primary KA
RMS Ig Primary KA
RMS Isg Primary KA
I0 Primary KA
I1 Primary KA
I2 Primary KA
% Load to trip N/A
6.3.1.2 Voltage
Actual > Metering > Primary Values > Voltage
DESCRIPTION UNITS
PT Ratio N/A
Va Angle Deg
Vb Angle Deg
Vc Angle Deg
Vn Angle Deg
Vx Angle Deg
Vab Angle Deg
Vbc Angle Deg
Vca Angle Deg
V0 Primary KV
V1 Primary KV
V2 Primary KV
Vab Primary KV
Vbc Primary KV
Vca Primary KV
Va Primary KV
Vb Primary KV
Vc Primary KV
Vn Primary KV
Vx Primary KV
VBB Primary KV
VL Primary KV
6.3.1.3 Power
Actual > Metering > Primary Values > Power
DESCRIPTION UNITS
Phase A Real Pwr MW
Phase A Reactive Pwr MVAr
Phase A Apparent Pwr MVA
Phase B Real Pwr MW
Phase B Reactive Pwr MVAr
Phase B Apparent Pwr MVA
Phase C Real Pwr MW
Phase C Reactive Pwr MVAr
Phase C Apparent Pwr MVA
3 Phase Real Pwr MW
3 Phase Reactive Pwr MVAr
3 Phase Apparent Pwr MVA
6.3.1.4 Energy
Actual> Metering > Primary Values > Energy
Energy is only given in three phase primary values
DESCRIPTION UNITS
Positive MWatthour MWh
Negative MWatthour MWh
Positive MVarhour MVArh
Negative MVarhour MVArh
Pos Mwatthour Cnt MWh
Neg Mwatthour Cnt MWh
Pos MVarhour Cnt MVArh
Neg MVarhour Cnt MVArh
When the energy counters reach the value (2ˆ 31)/1000 (approximately 2147483 MVArh and MWh) all the values are
set to zero and starts counting again.
6.3.1.5 Demand
Actual > Metering > Primary Values > Demand
Demand is only given in primary values
6.3.2.1 Current
Actual> Metering > Secondary Values > Current
DESCRIPTION UNITS
Phasor Ia A
RMS Ia A
Phasor Ib A
RMS Ib A
Phasor Ic A
RMS Ic A
Phasor In A
Phasor Ig A
RMS Ig A
Phasor Isg A
RMS Isg A
Zero seq I0 A
Positive Seq I1 A
Negative Seq I2 A
6.3.2.2 Voltage
Actual > Metering > Secondary Values > Voltage
DESCRIPTION UNITS
Phasor Vab V
Phasor Vbc V
Phasor Vca V
Phasor Van V
Phasor Vbn V
Phasor Vcn V
Phasor Vn V
Positive Seq V1 V
Negative Seq V2 V
Zero Seq V0 V
Phasor Vx V
Nominal Voltage V
Line Voltage V
Bus Voltage V
6.3.2.3 Power
Actual> Metering > Secondary Values > Power
DESCRIPTION UNITS
Phase A Apparent Pwr VA
Phase B Apparent Pwr VA
Phase C Apparent Pwr VA
Phase A Real Pwr W
Phase B Real Pwr W
Phase C Real Pwr W
Phase A Reactive Pwr VARS
Phase B Reactive Pwr VARS
Phase C Reactive Pwr VARS
3 Phase Apparent Pwr VA
3 Phase Real Pwr W
3 Phase Reactive Pwr VARS
Phase A Power Factor N/A
Phase B Power Factor N/A
Phase C Power Factor N/A
3 Phase Power Factor N/A
NOTE: If voltage inputs are configured in Delta connection and the auxiliary voltage input is set as Vx, measurements of
single phase power value cannot be duly calculated, and therefore, its value is zero. For the three-phase power value, the
system uses the ARON method, or two-wattmeters method.
6.3.4 Frequency
Actual > Metering > Frequency
DESCRIPTION UNITS
Line Frequency Hz
Bus Frequency Hz
df/dt Hz/s
CONT OP_X_02
CONT OP_X_03
CONT OP_X_04
CONT OP_X_05
CONT OP_X_06
CONT OP_X_07
CONT OP_X_08
BOARD X STATUS
NOTE: Both in the outputs menu as in the rest of menus available in “Actual”, the user can view several screens at
the same time to facilitate analysis.
These screens are available for all boards incorporated in the relay model, which can be F, G, H, and/or J.
This screen shows the activated or deactivated status of those variables used internally to operate a contact output.
Signals shown on this screen are configured in the Outputs screen inside the Setpoint > Relay Configuration
menu, either directly by selecting the signals provided by the relay, or selecting a signal provided by the logic
configured at Setpoint > Logic Configuration.
These logic signals (Contact Output Operates), when being transformed by the outputs logic configured at Setpoint
> Inputs/Outputs >Contact I/O > Board X become Contact Output signals. This output logic can be POSITIVE,
NEGATIVE, pulse, latched, etc.
Operation example of output contacts:
The last LED in this screen, labeled Board Status, indicates the general board status.
This output reset Command is only be effective if latch has been selected for Output Type on the I/O board, thus
the contact output has been configured to emulate function 86 (latching relay).
Configuration for the contact output reset signal is set at Setpoint > Relay Configuration > Outputs > Contact
Output Reset.
For all I/O board screens described above, the last LED provides this same information individually.
Actual > Inputs/Outputs > Remote Outputs > Remote GOOSE Dig Outputs
This screen provides the status of the 32 Remote GOOSE Digital Outputs.
Table 6-43: Remote GOOSE digital output status
REMOTE GOOSE DIG OUTPUTS STATUS
Rem GOOSE Dig Out 1
Rem GOOSE Dig Out 2
Rem GOOSE Dig Out 3
...
Rem GOOSE Dig Out 32
Actual > Inputs/Outputs > Remote Outputs > Remote GOOSE Digital Inputs
This screen provides the status of the 32 Remote GOOSE Digital Inputs.
Actual > Inputs/Outputs > Remote Outputs > Remote GOOSE Analog Inputs
This screen provides the values of the 16 Remote GOOSE Analog Inputs. Eight of them are float type and the other eight are
integer type.
6.4.12 RIOs
Actual > Inputs/Outputs > RIOs
This screen provides the values of virtual output analogues, integer and float values
6.5 Records
6.5.1 Event recorder
Note that any settings change in the oscillography removes all the information stored up to that moment.
When selecting one of the records, a new screen details the following information:
• Date
• Time
• Pre-fault current and voltage in primary values
• Fault current and voltage in primary values
• Fault type
• Distance to the fault
The operation of this screen is similar to that of the previous oscillography screen, being in this case the number of
fault reports a fixed number (10), instead of variable and setting-selected like as in the previous case.
Once a fault report is selected, its heading description is displayed, showing pre-fault information, fault information
and the distance to the fault. This file can be downloaded to the computer in a CSV format file.
Note that any settings change in the fault report remove all information stored up to that moment. Fault report
retrieval is described in section 5.2.3.2 Fault report retrieval.
This chapter outlines the IEC 61850 communications protocol. The IEC 61850 protocol applies when ordered with
the product. (Check the order code to determine whether IEC 61850 is included with your product).
The relay provides 32 "DNA" bit pairs that represent the state of two pre-defined events and 64 "UserSt" bit pairs,
which are status bits representing user-definable events.
GSSE service can be configured using the EnerVista 650 Setup program in the menu Setpoint > Input/Outputs >
Remote Comms.
Remote Comms must be set to "GSSE" to enable GSSE configuration.
650 ID represents the IEC 61850 GSSE application ID name string sent as part of each GSSE message. This string
identifies the GSSE message to the receiving device.
Hold time is used to calculate the interval, if a change-of-state has not occurred, that the device waits to send GSSE
message.
Remote Device (1 to 32) is used to select specific remote devices by entering the exact identification (ID) assigned
to these devices. A maximum of 32 devices can be configured for receiving GSSE messages.
Bit Pair (1 to 32) is used to assign the data from the GSSE message to remote inputs.
The 10 parts of the standard IEC 61850 are as listed in the following tables:
1.1.2 Configuration
Part 6: Configuration Description Language For Communication In Electrical
Substations Related To IEDs
1.1.3 Testing
Part 10: Conformance Testing
These documents can be obtained from the IEC (http://www.iec.ch). It is strongly recommended that all those involved with
any IEC 61850 implementation obtain this document set.
Glossary Part 2
Conformance testing
Part 10
Parts 3, 4, and 5 of the standard start by identifying the general and specific functional requirements for
communications in a substation. These requirements are then used as forcing functions to aid in the identification of
the services and data models needed, application protocol required, and the underlying transport, network, data link,
and physical layers that meet the overall requirements.
The major architectural construct that 61850 adopts is that of "abstracting" the definition of the data items and the
services, that is, creating data items/objects and services that are independent of any underlying protocols. The
abstract definitions then allow "mapping" of the data objects and services to any other protocol that can meet the
data and service requirements.
The definition of the abstract services is found in part 7.2 of the standard and the abstraction of the data objects
(referred to as Logical Nodes) is found in part 7.4.
In as much as many of the data objects are made up of common pieces (such as Status, Control, Measurement,
Substitution), the concept of "Common Data Classes" or "CDC" was developed which defined common building
blocks for creating the larger data objects. The CDC elements are defined in part 7.3.
Given the data and services abstract definitions, the final step was one of "mapping" the abstract services into an
actual protocol. Section 8.1 defines the mapping of the abstract data object and services onto the Manufacturing
Messaging Specification - MMS2 and sections 9.1 and 9.2 define the mapping of the Sample Measured Values
(unidirectional point-to-point and bi-directional multipoint accordingly) onto an Ethernet data frame. The 9.2
document defines what has become known as the Process Bus.
From a system perspective, there is a significant amount of configuration that is required in order to put all the pieces
together and have them work. In order to facilitate this process and to eliminate much of the human error component,
an XML based Substation Configuration Language (SCL) was defined in part 6. It allows the formal description of the
relations between the substation automation system and the substation. At the application level, the substation
topology itself and the relation of the substation structure to the SAS functions (logical nodes) configured on the IEDs
can be described. Each device must provide an SCL file that describes the configuration of itself.
Finally, part 10 defines a testing methodology in order to determine "conformance" with the numerous protocol
definitions and constraints defined in the standard.
Application layer
Presentation layer A Profile
Session layer
Transport layer
Network layer
T Profile
Data link layer
Physical layer
A and T profiles can be combined in various ways to form different types of services and information items that can
be exchanged. The services specified in Part 7-2 of the IEC61850 standard are mapped onto four different
combinations of the profiles. These four combinations are used for
• Client/server services,
• GOOSE/GSE management services,
• GSSE services,
• Time synchronization,
• Services for measured value sampling.
For F650 relays whose order code contains Rear Ethernet Communication Board 2 "G", "H", "J", "K", "L" or "M" and
Communication protocol "6", product protocol and model implementation conformance statements are described in
the following sections:
IEC 61850 Edition 2:
• 7.3.7.3.2 PICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 "H", "G", "K", "J","L",
"M" and IEC 61850 Edition 2 on page 7–25 (PICS for 650 family of relays v1_4 firm7_20)
• 7.3.7.3.5 MICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G", "K",
"J", "L", "M" and IEC 61850 Edition 2 on page 7–66 MICS for 650 family of relays v1_01 firm7_20
• 7.3.7.3.8 TICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G", "K",
"J", "L", "M" and IEC 61850 Edition 2 on page 7–180 (TICS for 650 family of relays v1_0 firm7_20)
• 7.3.7.3.11 PIXIT for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G",
"K", "J", "L", "M" and IEC 61850 Edition 2 on page 7–193 (PIXIT for 650 family of relays v1_6 firm7_20)
IEC 61850 Edition 1:
• 7.3.7.3.3 PICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G", "K",
"J", "L", "M" and IEC 61850 Edition 1 on page 7–37 (PICS For F650 relay V1_6 firm7_52)
• 7.3.7.3.6 MICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G", "K",
"J", "L", "M" and IEC 61850 Edition 1 on page 7–128 (MICS For F650 relay V1_10 firm7_52)
• 7.3.7.3.9 TICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G", "K",
"J", "L", "M" and IEC 61850 Edition 1 on page 7–183 (TICS For F650 relay V3_04 firm7_52)
• 7.3.7.3.12 PIXIT for 650 family of relays whose order code has Rear Ethernet Communication Board 2 option "H", "G",
"K", "J", "L", "M" and IEC 61850 Edition 1 on page 7–202 (PIXIT For F650 relay V1_10 firm7_52)
7.3.7.3.1 PICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
"B", "C", "D", "E"
Reference documentation: PICS for 650 family rev1_7 firm3_60.
This document describes the:
• ACSI Conformance Statement
• PICS (“Protocol Implementation Conformance Statement”) for 650 family of relays.
1 ACSI Conformance Statement
The following ACSI conformance statements shall be used to provide an overview and details about a device
claiming conformance with ACSI to specify the communication features mapped to an SCSM:
S14 CreateDataSet TP - N
S15 DeleteDataSet TP - N
S16 GetDataSetDirectory TP - Y
GSSE-CONTROL-BLOCK
S40 SendGSSEMessage MC - Y
S41 GetGsReference TP - N
S42 GetGSSEElementNumber TP - N
S43 GetGsCBValues TP - Y
S44 SetGsCBValues TP - Y
The tables refer to part 7 of the standard and the corresponding information must be contained in the PICS.
2.1 Notation
For the following clauses, these definitions apply:
• Y: The item is implemented.
• N: The item is not implemented.
• x: excluded. The implementation shall not implement this item.
• i: out-of-scope. The implementation of the item is not within the scope of this standard.
• F/S: Functional Standard. Should be applied.
• Base: Shall be applied in any application claiming conformance to this standard.
Refer to the services of Part 7 to see whether these profiles are supported. No distinction is made between A- and T-
Profiles there because the definition only refers to the application.
2.3 MMS conformance
The following conformance statements are conditional upon the support of the client/server A-Profile (e.g. A1 see
profile description in Clause 6) being declared.
Except where present, MMS conformance shall be in accordance with ISO/ISP 14226-2.
2.3.1 MMS Initiate conformance
2.3.1.1 MMS InitiateRequest general parameters
Client-CR Server-CR
InitiateRequest Realized Value/range Realized Value/range
InitiateRequest
localDetailCalling Y
proposedMaxServOutstandingCalling Y
ProposedMaxServOustandingCalled Y
InitRequestDetail Y
InitiateRequestDetail
proposedVersionNumber Y
proposedParameterCBB Y
servicesSupportedCalling Y
additionalSupportedCalling N
additionalCbbSupportedCalling N
privilegeClassIdentityCalling N
2.3.1.2 MMS InitiateResponse general parameters
Client-CR Server-CR
InitiateRequest Realized Value/range Realized Value/range
InitiateResponse
localDetailCalled Y
negotiatedMaxServOutstandingCalling Y 1
negotiatedMaxServOustandingCalled Y 3
initResponseDetail Y
InitiateResponseDetail Y
negotiatedVersionNumber Y
negotiatedParameterCBB Y
servicesSupportedCalled Y
additionalSupportedCalled N
additionalCbbSupportedCalled N
privilegeClassIdentityCalled N
Client-CR Server-CR
MMS service supported CBB
Realized Value/range Realized Value/range
status Y
getNameList Y
identify Y
rename N
read Y
write Y
getVariableAccessAttributes Y
defineNamedVariable N
defineScatteredAccess N
getScatteredAccessAttributes N
deleteVariableAccess N
defineNamedVariableList N
getNamedVariableListAttributes Y
deleteNamedVariableList N
defineNamedType N
getNamedTypeAttributes N
deleteNamedType N
Input N
Output N
takeControl N
relinquishControl N
defineSemaphore N
deleteSemaphore N
reportPoolSemaphoreStatus N
reportSemaphoreStatus N
initiateDownloadSequence N
downloadSegment N
terminateDownloadSequence N
initiateUploadSequence N
uploadSegment N
terminateUploadSequence N
requestDomainDownload N
requestDomainUpload N
loadDomainContent N
storeDomainContent N
deleteDomain N
getDomainAttributes Y
createProgramInvocation N
deleteProgramInvocation N
Start N
Stop N
Resume N
Reset N
Kill N
getProgramInvocationAttributes N
obtainFile N
defineEventCondition N
Client-CR Server-CR
MMS service supported CBB (cont.)
Realized Value/range Realized Value/range
deleteEventCondition N
getEventConditionAttributes N
reportEventConditionStatus N
alterEventConditionMonitoring N
triggerEvent N
defineEventAction N
deleteEventAction N
alterEventEnrollment N
reportEventEnrollmentStatus N
getEventEnrollmentAttributes N
acknowledgeEventNotification N
getAlarmSummary N
getAlarmEnrollmentSummary N
readJournal N
writeJournal N
initializeJournal N
reportJournalStatus N
createJournal N
deleteJournal N
FileOpen Y
FileRead Y
FileClose Y
fileRename N
fileDelete N
fileDirectory Y
unsolicitedStatus N
informationReport Y
eventNotification N
attachToEventCondition N
attachToSemaphore N
Conclude Y
Cancel Y
getDataExchangeAttributes N
exchangeData N
defineAccessControlList N
getAccessControlListAttributes N
reportAccessControlledObjects N
deleteAccessControlList N
alterAccessControl N
reconfigureProgramInvocation N
Client-CR Server-CR
MMS parameter CBB
Realized Value/range Realized Value/range
STR1 Y
STR2 Y
VNAM Y
VALT Y
VADR N
VSCA N
TPY N
VLIS Y
REAL N
CEI N
NEST Y 7
ACO N
SEM N
CSR N
CSNC N
CSPLC N
CSPI N
Client-CR Server-CR
GetNameList
Realized Value/range Realized Value/range
Request
ObjectClass Y
ObjectScope Y
DomainName Y
ContinueAfter Y
Response+
List Of Identifier Y
MoreFollows Y
Response–
Error Type Y
NOTE Object class ‘vmd' (formerly VMDSpecific in MMS V1.0) shall not appear. If a request contains this ObjectClass, an MMS
Reject shall be issued.
2.3.5 Variable access conformance statement
2.3.5.1 Supporting productions
2.3.5.1.1 AlternateAccessSelection conformance statement
Client-CR Server-CR
AlternateAccessSelection Realized Value/range Realized Value/range
accessSelection Y
component Y
index N
indexRange N
allElements N
alternateAccess Y
selectAccess Y
component Y
index N
indexRange N
allElements N
Client-CR Server-CR
VariableAccessSpecification Realized Value/range Realized Value/range
listOfVariable Y
variableSpecification Y
alternateAccess Y
variableListName Y
Client-CR Server-CR
VariableSpecification
Realized Value/range Realized Value/range
name Y
address N
variableDescription N
scatteredAccessDescription N
invalidated N
Client-CR Server-CR
Read
Realized Value/range Realized Value/range
Request
specificationWithResult Y
variableAccessSpecification Y
Response
variableAccessSpecification Y
listOfAccessResult Y
Client-CR Server-CR
Write
Realized Value/range Realized Value/range
Request
variableAccessSpecification Y
listOfData Y
Response
failure Y
success Y
Client-CR Server-CR
InformationReport
Realized Value/range Realized Value/range
Request
variableAccessSpecification Y
listOfAccessResult Y
Client-CR Server-CR
GetVariableAccessAttributes
Realized Value/range Realized Value/range
Request
name Y
address N
Response
mmsDeletable Y
address N
typeSpecification Y
Client-CR Server-CR
GetNamedVariableListAttributes realized Value/range realized Value/range
Request
ObjectName Y
Response
mmsDeletable Y
listOfVariable Y
variableSpecification Y
alternateAccess Y
Client-CR Server-CR
FileDirectory
Realized Value/range Realized Value/range
Request
filespecification Y
continueAfter Y
Response+
listOfDirectoryEntry Y
MoreFollows Y
Client-CR Server-CR
FileOpen
Realized Value/range Realized Value/range
Request
filename Y
initialPosition Y
Response+
frsmID Y
fileAttributes Y
Client-CR Server-CR
FileRead
Realized Value/range Realized Value/range
Request
FrsmID Y
Response+
FileData Y
moreFollows Y
Client-CR Server-CR
FileClose
Realized Value/range Realized Value/range
Request
FrsmID Y
Response+ Y
7.3.7.3.2 PICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
"H", "G", "K", "J","L", "M" and IEC 61850 Edition 2
Reference documentation: PICS for 650 family of relays v1_4 firm7_20.
This document describes the:
• ACSI Conformance Statement
• PICS ("Protocol Implementation Conformance Statement") for 650 family of relays.
The following ACSI conformance statements shall be used to provide an overview and details about a device
claiming conformance with ACSI to specify the communication features mapped to an SCSM:
The statements specify the communication features mapped to IEC 61850-8-1 First Edition and/or Edition 2.
1.1 Notation
The basic conformance statement is defined in Table 7-2: Basic conformance statement
Table 7-2: Basic conformance statement
SCSMs supported
M1 Logical device - Y
M2 Logical node - Y
M3 Data - Y
M4 Data set - Y
M5 Substitution
M6 Setting group control - Y
Reporting
M7 Buffered report control - Y
M7-1 sequence-number - Y
M7-2 report-time-stamp - Y
M7-3 reason-for-inclusion - Y
M7-4 data-set-name - Y
M7-5 data-reference - Y
M7-6 buffer-overflow - Y
M7-7 entryID - Y
M7-8 BufTm - Y
M7-9 IntgPd - Y
M7-10 GI - Y
M7-11 conf-revision - Y
M8 Unbuffered report control - Y
M8-1 sequence-number - Y
M8-2 report-time-stamp - Y
M8-3 reason-for-inclusion - Y
M8-4 data-set-name - Y
M8-5 data-reference - Y
M8-6 BufTm - Y
M8-7 IntgPd - Y
M8-8 GI - Y
M8-9 conf-revision - Y
Logging
M9 Log control -
M9-1 IntgPd -
M10 Log -
M11 Control - Y
M17 File Transfer Y
M12 GOOSE Y
M13 GSSE Deprecated
If SVC (B41/B42) is supported
M16 Time Y Y
Y = service is supported
N or empty = service is not supported
Application association
S2 1,2 Associate TP Y
S3 1,2 Abort TP Y
S4 1,2 Release TP Y
Logical device
S5 1,2 GetLogicalDeviceDirectory TP Y
Logical node
S6 1,2 GetLogicalNodeDirectory TP Y
S7 1,2 GetAllDataValues TP Y
Data
S8 1,2 GetDataValues TP Y
S9 1,2 SetDataValues TP Y
S10 1,2 GetDataDirectory TP Y
S11 1,2 GetDataDefinition TP Y
Data set
S12 1,2 GetDataSetValues TP Y
S13 1,2 SetDataSetValues TP N
S14 1,2 CreateDataSet TP N
S15 1,2 DeleteDataSet TP N
S16 1,2 GetDataSetDirectory TP Y
Substitution
S17 1 SetDataValues TP N Ed1 only
Reporting
Buffered report control block (BRCB)
S24 1,2 Report TP Y
S24-1 1,2 data-change (dchg) Y
S24-2 1,2 quality-change (qchg) Y
S24-3 1,2 data-update (dupd) N
S25 1,2 GetBRCBValues TP Y
S26 1,2 SetBRCBValues TP Y
Unbuffered report control block (URCB)
S27 1,2 Report TP Y
S27-1 1,2 data-change (dchg) Y
S27-2 1,2 quality-change (qchg) Y
S27-3 1,2 data-update (dupd) N
S28 1,2 GetURCBValues TP Y
S29 1,2 SetURCBValues TP Y
Logging
Log control
S30 1,2 GetLCBValues TP N
S31 1,2 SetLCBValues TP N
Log
S32 1,2 QueryLogByTime TP N
S33 1,2 QueryLogAfter TP N
S34 1,2 GetLogStatusValues TP N
Control
S51 1,2 Select TP Y SBO Normal Security
S52 1,2 SelectWithValue TP Y SBO Enhanced Security
S53 1,2 Cancel TP Y
File transfer
S57 1,2 GetFile TP Y
S58 1,2 SetFile TP N
S59 1,2 DeleteFile TP N
S60 1,2 GetFileAttributeValues TP Y
S61 1,2 GetServerDirectory (FILE) TP Y
Time
T1 1,2 Time resolution of internal clock - 2ms nearest negative power of 2 in seconds
T2 2 Time accuracy of internal clock - TL (ms) (low accuracy), T3 < 7) (only Ed2)
1,2 - T0 (ms) (<= 10 ms), 7 <= T3 < 9)
1,2 - T1 (µs) (<= 1 ms), 10 <= T3 < 13
1,2 - T2 (µs) (<= 100 µS), 13 <= T3 < 15
1,2 - T3 (µs) (<= 25 µS), 15 <= T3 < 18
1,2 - T4 (µs) (<= 4 µS), 18 <= T3 < 20
1,2 - Y T5 (µs) (<= 1 µS), T3 >= 20)
T3 1,2 Supported TimeStamp resolution - 1ms nearest negative power of 2 in seconds
2.1 Notation
For the following clauses, these definitions apply:
• Y: The item is implemented.
• N: The item is not implemented.
• x: excluded. The implementation shall not implement this item.
• i: out-of-scope. The implementation of the item is not within the scope of this standard.
• F/S: Functional Standard. Should be applied.
• Base: Shall be applied in any application claiming conformance to this standard.
Refer to the services of Part 7 to see whether these profiles are supported. No distinction is made between A- and T-
Profiles there because the definition only refers to the application.
2.3 MMS conformance
The following conformance statements are conditional upon the support of the client/server A-Profile (e.g. A1 see
profile description in Clause 6) being declared.
Except where present, MMS conformance shall be in accordance with ISO/ISP 14226-2.
2.3.1 MMS Initiate conformance
2.3.1.1 MMS InitiateRequest general parameters
Client-CR Server-CR
InitiateRequest Realized Value/range Realized Value/range
InitiateRequest
localDetailCalling Y
proposedMaxServOutstandingCalling Y
ProposedMaxServOustandingCalled Y
InitRequestDetail Y
InitiateRequestDetail
proposedVersionNumber Y
proposedParameterCBB Y
servicesSupportedCalling Y
additionalSupportedCalling N
additionalCbbSupportedCalling N
privilegeClassIdentityCalling N
Client-CR Server-CR
InitiateRequest Realized Value/range Realized Value/range
InitiateResponse
localDetailCalled Y
negotiatedMaxServOutstandingCalling Y 1
negotiatedMaxServOustandingCalled Y 3
initResponseDetail Y
InitiateResponseDetail Y
negotiatedVersionNumber Y
negotiatedParameterCBB Y
servicesSupportedCalled Y
additionalSupportedCalled N
additionalCbbSupportedCalled N
privilegeClassIdentityCalled N
Client-CR Server-CR
MMS service supported CBB
Realized Value/range Realized Value/range
status Y
getNameList Y
identify Y
rename N
read Y
write Y
getVariableAccessAttributes Y
defineNamedVariable N
defineScatteredAccess N
getScatteredAccessAttributes N
deleteVariableAccess N
defineNamedVariableList N
getNamedVariableListAttributes Y
deleteNamedVariableList N
defineNamedType N
getNamedTypeAttributes N
deleteNamedType N
Input N
Output N
takeControl N
relinquishControl N
defineSemaphore N
deleteSemaphore N
reportPoolSemaphoreStatus N
reportSemaphoreStatus N
initiateDownloadSequence N
downloadSegment N
terminateDownloadSequence N
initiateUploadSequence N
uploadSegment N
terminateUploadSequence N
requestDomainDownload N
requestDomainUpload N
loadDomainContent N
storeDomainContent N
deleteDomain N
getDomainAttributes Y
createProgramInvocation N
deleteProgramInvocation N
Start N
Stop N
Resume N
Reset N
Kill N
getProgramInvocationAttributes N
obtainFile N
defineEventCondition N
deleteEventCondition N
getEventConditionAttributes N
reportEventConditionStatus N
alterEventConditionMonitoring N
triggerEvent N
defineEventAction N
deleteEventAction N
alterEventEnrollment N
reportEventEnrollmentStatus N
getEventEnrollmentAttributes N
acknowledgeEventNotification N
getAlarmSummary N
getAlarmEnrollmentSummary N
readJournal N
writeJournal N
initializeJournal N
reportJournalStatus N
createJournal N
deleteJournal N
FileOpen Y
FileRead Y
FileClose Y
fileRename N
fileDelete N
fileDirectory Y
unsolicitedStatus N
informationReport Y
eventNotification N
attachToEventCondition N
attachToSemaphore N
Conclude Y
Cancel Y
getDataExchangeAttributes N
exchangeData N
defineAccessControlList N
getAccessControlListAttributes N
reportAccessControlledObjects N
deleteAccessControlList N
alterAccessControl N
reconfigureProgramInvocation N
Client-CR Server-CR
MMS parameter CBB
Realized Value/range Realized Value/range
STR1 Y
STR2 Y
VNAM Y
VALT Y
VADR N
VSCA N
TPY N
VLIS Y
REAL N
CEI N
NEST Y 7
ACO N
SEM N
CSR N
CSNC N
CSPLC N
CSPI N
2.3.4 GetNameList conformance statement
Client-CR Server-CR
GetNameList
Realized Value/range Realized Value/range
Request
ObjectClass Y
ObjectScope Y
DomainName Y
ContinueAfter Y
Response+
List Of Identifier Y
MoreFollows Y
Response–
Error Type Y
NOTE Object class ‘vmd' (formerly VMDSpecific in MMS V1.0) shall not appear. If a request contains this ObjectClass, an MMS
Reject shall be issued.
Client-CR Server-CR
AlternateAccessSelection Realized Value/range Realized Value/range
accessSelection Y
component Y
index N
indexRange N
allElements N
alternateAccess Y
selectAccess Y
component Y
index N
indexRange N
allElements N
Client-CR Server-CR
VariableAccessSpecification Realized Value/range Realized Value/range
listOfVariable Y
variableSpecification Y
alternateAccess Y
variableListName Y
Client-CR Server-CR
VariableSpecification
Realized Value/range Realized Value/range
name Y
address N
variableDescription N
scatteredAccessDescription N
invalidated N
Client-CR Server-CR
Read
Realized Value/range Realized Value/range
Request
specificationWithResult Y
variableAccessSpecification Y
Response
variableAccessSpecification Y
listOfAccessResult Y
Client-CR Server-CR
Write
Realized Value/range Realized Value/range
Request
variableAccessSpecification Y
listOfData Y
Response
failure Y
success Y
Client-CR Server-CR
InformationReport
Realized Value/range Realized Value/range
Request
variableAccessSpecification Y
listOfAccessResult Y
Client-CR Server-CR
GetVariableAccessAttributes
Realized Value/range Realized Value/range
Request
name Y
address N
Response
mmsDeletable Y
address N
typeSpecification Y
Client-CR Server-CR
GetNamedVariableListAttributes Realized Value/range Realized Value/range
Request
ObjectName Y
Response
mmsDeletable Y
listOfVariable Y
variableSpecification Y
alternateAccess Y
Client-CR Server-CR
FileDirectory
Realized Value/range Realized Value/range
Request
filespecification Y
continueAfter Y
Response+
listOfDirectoryEntry Y
MoreFollows Y
Client-CR Server-CR
FileOpen
Realized Value/range Realized Value/range
Request
filename Y
initialPosition Y
Response+
frsmID Y
fileAttributes Y
Client-CR Server-CR
FileRead
Realized Value/range Realized Value/range
Request
FrsmID Y
Response+
FileData Y
moreFollows Y
Client-CR Server-CR
FileClose
Realized Value/range Realized Value/range
Request
FrsmID Y
Response+ Y
7.3.7.3.3 PICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 1
Reference documentation: PICS For F650 relay V1_6 firm7_52.
This document describes the:
• ACSI Conformance Statement
• PICS ("Protocol Implementation Conformance Statement") for 650 family of relays.
1 General
The following ACSI conformance statements are used to provide an overview and details about F650 bay controller,
with firmware 7.52:
• ACSI BASIC conformance statement.
• ACSI MODELS conformance statement.
• ACSI SERVICE conformance statement.
The statements specify the communication features mapped to IEC 61850-8-1 First Edition and/or Edition 2.
SCSMs supported
M1 Logical device Y
M2 Logical node Y
M3 Data Y
M4 Data set Y
M5 Substitution
M6 Setting group control Y
Reporting
M7 Buffered report control Y
M7-1 sequence-number Y
M7-2 report-time-stamp Y
M7-3 reason-for-inclusion Y
M7-4 data-set-name Y
M7-5 data-reference Y
M7-6 buffer-overflow Y
M7-7 entryID Y
M7-8 BufTm Y
M7-9 IntgPd Y
M7-10 GI Y
M7-11 conf-revision Y
M8 Unbuffered report control Y
M8-1 sequence-number Y
M8-2 report-time-stamp Y
M8-3 reason-for-inclusion Y
M8-4 data-set-name Y
M8-5 data-reference Y
M8-6 BufTm Y
M8-7 IntgPd Y
M8-8 GI Y
M8-9 conf-revision Y
Logging
M9 Log control
M9-1 IntgPd
M10 Log
M11 Control Y
M17 File Transfer Y
M18 Application association Y
M19 GOOSE Control Block Y
M20 Sampled Value Control Block
If GSE (B31/32) is supported
M12 GOOSE Y
M13 GSSE Deprecated
If SVC (B41/B42) is supported
M16 Time Y Y
Y = service is supported
N or empty = service is not supported
Application association
S2 1,2 Associate TP Y
S3 1,2 Abort TP Y
S4 1,2 Release TP Y
Logical device
S5 1,2 GetLogicalDeviceDirectory TP Y
Logical node
S6 1,2 GetLogicalNodeDirectory TP Y
S7 1,2 GetAllDataValues TP Y
Data
S8 1,2 GetDataValues TP Y
S9 1,2 SetDataValues TP Y
S10 1,2 GetDataDirectory TP Y
S11 1,2 GetDataDefinition TP Y
Data set
S12 1,2 GetDataSetValues TP Y
S13 1,2 SetDataSetValues TP N
S14 1,2 CreateDataSet TP N
S15 1,2 DeleteDataSet TP N
S16 1,2 GetDataSetDirectory TP Y
Substitution
S17 1 SetDataValues TP N Ed1 only
Reporting
Buffered report control block (BRCB)
S24 1,2 Report TP Y
S24-1 1,2 data-change (dchg) Y
S24-2 1,2 quality-change (qchg) Y
S24-3 1,2 data-update (dupd) N
S25 1,2 GetBRCBValues TP Y
S26 1,2 SetBRCBValues TP Y
Unbuffered report control block (URCB)
S27 1,2 Report TP Y
S27-1 1,2 data-change (dchg) Y
S27-2 1,2 quality-change (qchg) Y
Logging
Log control
S30 1,2 GetLCBValues TP N
S31 1,2 SetLCBValues TP N
Log
S32 1,2 QueryLogByTime TP N
S33 1,2 QueryLogAfter TP N
S34 1,2 GetLogStatusValues TP N
Control
S51 1,2 Select TP Y SBO Normal Security
S52 1,2 SelectWithValue TP Y SBO Enhanced Security
S53 1,2 Cancel TP Y
S54 1,2 Operate TP Y
S55 1,2 CommandTermination TP Y
S56 1,2 TimeActivatedOperate TP N
File transfer
S57 1,2 GetFile TP Y
S58 1,2 SetFile TP N
S59 1,2 DeleteFile TP N
S60 1,2 GetFileAttributeValues TP Y
S61 1,2 GetServerDirectory (FILE) TP Y
Time
T1 1,2 Time resolution of internal clock - 2ms nearest negative power of 2 in seconds
T2 2 Time accuracy of internal clock - TL (ms) (low accuracy), T3 < 7) (only Ed2)
1,2 - T0 (ms) (<= 10 ms), 7 <= T3 < 10)
7.3.7.3.4 MICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "B", "C", "D", "E" and IEC 61850 Edition 1
Reference documentation: MICS for 650 family rev1.4 firm3_60.
This document describes the:
• Logical Nodes List
• Logical Nodes and Extensions
• Enum types implementation
1 Logical Nodes List
The following table contains the list of logical nodes implemented in the device with firmware version lower than 7.00:
LPHD class
Attribute Name Attribute Type Explanation M/O/E Notes
LPHD Physical device information M
Data
Common Logical Node Information
PhyNam DPL Physical device name plate M
PhyHealth INS Physical device health M
Proxy SPS Indicates if this LN is a proxy M
LLN0 class
Attribute Name Attribute Explanation M/O/E Notes
Type
LLN0 Logical node zero
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Loc SPS Local operation for complete logical device O
Optmh INS Operation time M
GsCB (ACSI class GSSE control block)
GsCB GsCB
GoCB (ACSI class GOOSE control block)
GoCB GoCB
SGCB (ACSI class Setting Group control block)
SGCB SGCB
GsCB class
Attribute Name Attribute Type FC Notes
GsEna BOOLEAN GS Enable (TRUE), disable (FALSE)
GsID VISIBLE STRING65 GS
DNALabels[1..n] VISIBLE STRING65 GS Labels of DNA bit pairs
UserSTLabels[1..n] VISIBLE STRING65 GS Label of ST bit pairs
LSentData [1..n] GSSEData GS Derived from GSSE message
GoCB class
Attribute Name Attribute Type FC Notes
GoEna BOOLEAN GO Enable (TRUE), disable (FALSE)
SGCB class
Attribute Name Attribute Type FC Notes
NumOfSG INT8U SP Total number of settings group available in the logical
device. Fixed as 3
ActSG INT8U SP Setting group whose values are used by a logical node
to performing its function. Values: 1, 2 or 3
EditSG INT8U SP Setting group whose values can be set. Values: 1, 2 or 3
CnfEdit BOOLEAN SP
LActTm Timestamp SP
PIOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start O IOC PKP
Op ACT Operate M IOC OP
Blk ACT Blk E IOC BLK
Settings
StrVal ASG Start value M Pickup Level (0,05 – 160)
OpDlTmms ING Operate Delay Time E Trip Delay (0-900000)
Units in milliseconds
InMagTyp ING Input Type E (Phasor or RMS)
RsDlTmms ING Reset Delay E Reset Delay (0-900000)
Units in milliseconds
PIOCEna SPG Function IOC enable E Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.2.1.2 ndPIOC
This logical node class is used for neutral instantaneous overcurrent and has 3 instances inside the device.
PIOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start O IOC PKP
Op ACT Operate M IOC OP
Blk ACT Blk E IOC BLK
Settings
StrVal ASG Start value M Pickup Level (0,05 – 160)
OpDlTmms ING Operate Delay Time E Trip Delay (0-900000)
Units in milliseconds
RsDlTmms ING Reset Delay E Reset Delay (0-900000)
Units in milliseconds
PIOCEna SPG Function IOC enable E Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.2.1.3 gndPIOC/hsePIOC
This logical node class is used for ground instantaneous and sensitive ground instantaneous overcurrent. There are
6 instances of this logical node inside the device.
PIOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start O IOC PKP
Op ACT Operate M IOC OP
Blk ACT Blk E IOC BLK
Settings
StrVal ASG Start value M Pickup Level (0,05 – 160)*
OpDlTmms ING Operate Delay Time E Trip Delay (0-900000)
Units in milliseconds
InMagTyp ING Input Type E (Phasor or RMS)
RsDlTmms ING Reset Delay E Reset Delay (0-900000)
Units in milliseconds
PIOCEna SPG Function IOC enable E Function
PTOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOC PKP
Op ACT Operate M TOC OP
Blk ACT Block E TOC BLK
Settings
TmACrv CURVE Operating curve type M Curve
StrVal ASG Start value O Pickup Level (0,05 - 160)
TmMult ASG Time dial multiplier O TD Multiplier (0 – 900)
RsMod ING Reset Mode E Reset (instantaneous, lineal)
InMagTyp ING Input Type E Input (Phasor, RMS)
VolRst SPG Voltage Restraint E (enable, Disable)
PTOCEna SPG Function TOC enable E Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.2.2.2 ndPTOC
This logical node class is used for neutral time overcurrent and has 3 instances inside the device.
PTOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOC PKP
Op ACT Operate M TOC OP
Blk ACT Block E TOC BLK
Settings
TmACrv CURVE Operating curve type M Curve
StrVal ASG Start value O Pickup Level (0,05 - 160)
TmMult ASG Time dial multiplier O TD Multiplier (0 – 900)
RsMod ING Reset Mode E Reset (instantaneous, lineal)
PTOC class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start O TOC PKP
Op ACT Operate M TOC OP
Blk ACT Block O TOC BLK
Settings
TmACrv CURVE Operating curve type O Curve
StrVal ASG Start value O Pickup Level (0,05 – 160)
TmMult ASG Time dial multiplier O TD Multiplier (0 – 900)
RsMod ING Reset Mode O Reset (instantaneous, lineal)
InMagTyp ING Input Type O Input (Phasor, RMS)
PTOCEna SPG Function TOC enable O Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
PTOF class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOF OverFrequency
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOF PKP
Op ACD Operate M TOF OP
Blk ACT Block E TOF BLK
Settings
StrVal ASG Start value (frequency) O Pickup Level (20-65)
BlkVal ASG Voltage Block Value O Minimum Voltage (10-300)
PTOV class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOV PKP
Op ACT Operate O TOV OP
Blk ACT Block E TOV BLK
Settings
StrVal ASG Start Value O Pickup Level (3 – 300)
OpDlTmms ING Operate Delay Time O Trip Delay (0 – 900000)
Units in milliseconds
RsDlTmms ING Reset Delay Time O Reset Delay (0 – 900000)
Units in milliseconds
PhLogic ING Logic Mode E Logic (Any, two, all phases)
PTOVEna SPG Function TOV enable E Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.2.4.2 auxPTOV
This logical node class is used for auxiliary overvoltage and has 3 instances inside the device.
PTOV class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOV PKP
Op ACT Operate O TOV OP
PTOV class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TOV PKP
Op ACT Operate O TOV OP
Blk ACT Block E TOV BLK
Settings
StrVal ASG Start Value O Pickup Level (3 – 300)
OpDlTmms ING Operate Delay Time O Trip Delay (0 – 900000)
Units in milliseconds
RsDlTmms ING Reset Delay Time O Reset Delay (0 – 900000)
Units in milliseconds
PTOVEna SPG Function TOV enable E Function
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
PTUV class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
2.2.5.2 AuxPTUV
This logical node class is used for auxiliary undervoltage and has 3 instances inside the device.
PTUV class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TUV PKP
Op ACT Operate M TUV OP
Blk ACT Block E TUV BLK
Settings
TmVCrv CURVE_2 Operating curve type O Curve (definitive, inverse)
StrVal ASG Start value O Pickup Level (3 – 300)
TmMult ASG Time dial multiplier O Delay (0 – 900)
PTUVEna SPG Function TUV enable E Function
Notes:
TmVCrv object uses Enum type setCharact_2 (See the Enum types implementation section).
ACT includes origin attribute in ST, this is implemented according to Tissue 68.
PTUF class
Attribute Attribute Explanation M/O/E Notes
Name Type
PTUF UnderFrequency
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Str ACD Start M TUF PKP
Op ACD Operate M TUF OP
Blk ACT Block E TUF BLK
Settings
StrVal ASG Start value (frequency) O Pickup Level (20-65)
BlkVal ASG Voltage Block Value O Minimum Voltage (10-300)
OpDlTmms ING Operate Delay Time O Trip Delay (0-900000)
Units in milliseconds
RsDlTmms ING Reset Delay Time O Reset Delay (0-900000)
Units in milliseconds
PTUFEna SPG Function TUF enable E Function (Enable, Disable)
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.3 Logical Nodes for protection related functions. LN Group: R
2.3.1 RDIR (Directional element)
2.3.1.1 phsRDIR
This logical node class is used for phase directional elements and has 3 instances inside the device.
RDIR class
Attribute Attribute Explanation M/O/E Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Dir ACD Direction M Fixed to unknown value
Op ACT Operate O Phase Dir OP
Blk ACT Block O Phase Dir Block
BlkIn ACT Phase Dir Blk Inp O Phase Dir Blk Inp
Settings
ChrAng ASG Characteristic Angle O (-90, 90) MTA
BlkValV ASG Minimum operating current O (0, 300) Pol V Threshold
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.3.1.2 ndRDIR
This logical node class is used for neutral directional elements and has 3 instances inside the device.
RDIR class
Attribute Attribute Explanation M/O/E Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Dir ACD Direction M Fixed to unknown value
Op ACT Operate E Neutral Dir OP
Blk ACT Block E Neutral Dir Block
BlkIn ACT Neutral Dir Blk Inp E Neutral Dir Blk Inp
Settings
ChrAng ASG Characteristic Angle O (-90, 90) MTA
BlkValV ASG Minimum operating current O (0, 300) Pol V Threshold
PolOpMod ING Direction E (Reverse, Forward)
BlkMod ING Block Logical E (Permission, Blocked)
RDIREna SPG Function Permission E (Enable, Disable)
PolQty ING Polarization O (VO,IP,VO+IP,VO*IP)
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.3.1.3 gndRDIR
This logical node class is used for ground directional elements and has 3 instances inside the device.
RDIR class
Attribute Attribute Explanation M/O/E Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Dir ACD Direction M Fixed to unknown value
Op ACT Operate E Ground Dir OP
Blk ACT Block E Ground Dir Block
BlkIn ACT Ground Dir Blk Inp E Ground Dir Blk Inp
Settings
This logical node class is used for sensitive ground directional elements and has 3 instances inside the device.
RDIR class
Attribute Attribute Explanation M/O/E Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status Information
Dir ACD Direction M Fixed to unknown value
Op ACT Operate E Sens Gnd Dir OP
Blk ACT Block E Sens Gnd Dir Block
BlkIn ACT Sens Gnd Dir Blk Inp E Sens Gnd Dir Blk Inp
Settings
ChrAng ASG Characteristic Angle O (-90, 90) MTA
BlkValV ASG Minimum operating current O (0, 300) Pol V Threshold
PolOpMod ING Direction E (Reverse, Forward)
BlkMod ING Block Logical E (Permission, Blocked)
RDIREna SPG Function Permission E (Enable, Disable)
Note: ACT includes origin attribute in ST, this is implemented according to Tissue 68.
RREC class
Attribute Attribute Explanation M/O/E Notes
Name Type
RREC Autoreclosing
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
Status Information
Op ACT Operate M AR Close Breaker
AutoRecSt INS Auto Reclosing status M AR Status
Notes:
AutoRecSt object includes extra enum values specified by Tissue 3 and Tissue 133 (See the Enum types
implementation section).
ACT includes origin attribute in ST, this is implemented according to Tissue 68.
2.4 Logical Nodes for control. LN Group: C
2.4.1 CSWI (Switch controller)
CSWI class
Attribute Attribute Explanation M/O/E Notes
Name Type
CSWI Switch controller
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Controls
Pos DPC Switch position M Switch open, close, undefined
In the F650 there are up to 16 configurable switchgears. Currently sixteen XSWI and sixteen CSWI are implemented
and mapped to the first sixteen switchgears in F650. XSWI and CSWI Logical Nodes can be seen as paired objects
in F650 as one pair of XSWI and CSWI map to the same switchgear. XSWI1 and CSWI1 map to Switchgear1,
XSWI2 and CSWI2 map to Switchgear2, etc. The difference between XSWI and CSWI in F650 is that control
commands cannot be sent directly via XSWI LN. Control commands have to be sent via CSWI LN.
In CSWI LN for "Pos" controllable attribute all possible control models are applicable:
• “direct-control-with-normal-security”
• “SBO-control-with-normal-security”
• “direct-control-with-enhanced-security”
• “SBO-control-with-enhanced-security”
The sboTimeout attribute for Pos is configurable in a range from 500 ms to 60 seconds.
The sboClass attribute for Pos can only have value "0" (operate-once).
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status information
BoardSt SPS Board Status E Board Status.
True:
board present and working correctly
False:
board not present
board present and board model
mismatch
board present and hardware failure
Ind1 SPS General Indication (binary input) O Contact Input 1
Ind2 SPS General Indication (binary input) O Contact Input 2
2.5.1.2 vinGGIO
This logical node class is used is used to map the latched and self reset virtual Inputs.
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Controls
DPCSO1 geDPC Double point controllable status O Latched Virtual Input 1, 2
output
DPCSO2 geDPC Double point controllable status O Latched Virtual Input 3, 4
output
.. .. .. .. ..
DPCSO16 geDPC Double point controllable status O Latched Virtual Input 31, 32
output
SPCSO1 SPC Single point controllable status O Latched Virtual Input 1
output
SPCSO2 SPC Single point controllable status O Latched Virtual Input 2
output
.. .. .. .. ..
SPCSO32 SPC Single point controllable status O Latched Virtual Input 32
output
SPCSO33 SPC Single point controllable status O Self reset Virtual Input 1
output
SPCSO34 SPC Single point controllable status O Self reset Virtual Input 2
output
.. .. .. .. ..
SPCSO64 SPC Single point controllable status O Self reset Virtual Input 32
output
Note:
Double control points operate on pairs of Virtual Inputs in a manner that one Virtual Input of the pair is set to “1” and
the other Virtual Input of the pair is set to "0".
For all controllable attributes in this logical node only "direct-control-with-normal-security" model of control is
applicable.
2.5.1.3 eveGGIO
This logical node class is used to map data from the list of any all internal digital states (PLC control events).
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS General Indication (binary O Control Event 1
input)
Ind2 SPS General Indication (binary O Control Event 2
input)
......... .......... ............... .......... ..............
Ind128 SPS General Indication (binary O Control Event 128
input)
Ind129 SPS General Indication (binary O Switchgear 1 event 1
input)
Ind130 SPS General Indication (binary O Switchgear 1 event 2
input)
Ind131 SPS General Indication (binary O Switchgear 1 event 3
input)
Ind132 SPS General Indication (binary O Switchgear 1 event 4
input)
Ind133 SPS General Indication (binary O Switchgear 2 event 1
input)
......... .......... ............... .......... ..............
Ind192 SPS General Indication (binary O Switchgear 16 event 4
input)
2.5.1.4 geRemoteInputsGGIO
This logical node class is used to map data from incoming GOOSE messages.
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS General Indication (binary O Remote Digital Input 1
input)
Ind2 SPS General Indication (binary O Remote Digital Input 2
input)
......... .......... ............... .......... ..............
2.5.1.5 geRemoteOutputsGGIO
This logical node class is used to map PLC digital states for outgoing GOOSE messages.
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS General Indication (binary O Remote Digital Output 1
input)
Ind2 SPS General Indication (binary O Remote Digital Output 2
input)
......... .......... ............... .......... ..............
Ind31 SPS General Indication (binary O Remote Digital Output 31
input)
Ind32 SPS General Indication (binary O Remote Digital Output 32
input)
Note: In 650 relays data from all logical nodes can be sent through outgoing GOOSE messages. Apart from that,
logical node rouGGIO gives the ability to send through GOOSE digital states that are results of PLC logic equations.
Mapping and configuration of rouGGIO states should be done with EnerVista 650 software.
MMTR class
Attribute Attribute Explanation M/O/E Notes
Name Type
MMTR Metering
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Measured values
SupWh BCR Mapped to generic pulse counter O Pulse Counter 1
SupVArh BCR Mapped to generic pulse counter O Pulse Counter 2
DmdWh BCR Mapped to generic pulse counter O Pulse Counter 3
DmdVArh BCR Mapped to generic pulse counter O Pulse Counter 4
CntPsWh MV Positive Wat Counter O
CntNgWh MV Negative Wat Counter O
CntPsVArh MV Positive VAR Counter O
CntNgVArh MV Negative VAR Counter O
MMXU class
Attribute Attribute Explanation M/O/E Notes
Name Type
MMXU Measurement
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Measured values
TotW MV Total active power (P) O Phase Real Pwr
TotVAr MV Total reactive power (Q) O Ph Reactive Pwr
TotVA MV Total apparent power (S) O Ph Apparent Pwr
TotPF MV Average power factor (PF) O 3 Ph Power Factor
Hz MV Frequency O Frequency
PPV DEL Phase to phase voltages (VL1L2,...) O Phase-to-Phase Primary
Voltages
PhV WYE Phase to ground voltages (VL1ER, ...) O Phase Primary Voltages
A WYE Phase currents (IL1, ...) O Phasor Primary
AuxV CMV Auxiliary Voltage E Vx Primary
BusHz MV Bus Frequency E Bus Frequency
MSQI class
Attribute Attribute Explanation M/O/E Notes
Name Type
MSQI Sequence and imbalance
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Measured values
SeqA SEQ Positive, Negative and Zero Sequence C
Current
SeqV SEQ Positive, Negative and Zero Sequence C
Voltage
XCBR class
Attribute Attribute Explanation M/O/E Notes
Name Type
XCBR Circuit breaker
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M Number of Switchgear
Loc SPS Local operation M Local / Remote
OpCnt INS Operation counter M Breaker openings
Controls
Pos geDPC Switch position M Breaker open, close, und
BlkOpn SPC Block opening M Status-only
BlkCls SPC Block closing M Status-only
Metered Values
SumSwARs BCR Sum of Switched Amperes O Maximum KI2t value of any of
the phases
Status information
CBOpCap INS Circuit breaker operating capability M Fixed value = 5
Settings
ThAlSwA ASG Threshold Alarm of Switched Amps E Maximum KI2t
SumSwATmms ASG Sum of sw. Amps integration time E KI2t Integ. Time
ExNumTr ASG Excessive number of trips E Maximum Openings
ExNumTr1hr ASG Excessive number of trips in 1 hour E Max. Openings 1 hour
In the F650 there are up to 16 configurable switchgears. Currently sixteen XSWI and sixteen CSWI are implemented
and mapped to first sixteen switchgears in F650. XSWI and CSWI Logical Nodes can be seen as paired objects in
F650 as one pair of XSWI and CSWI map to the same switchgear. XSWI1 and CSWI1 map to Switchgear1, XSWI2
and CSWI2 map to Switchgear2, etc. The difference between XSWI and CSWI in F650 is that control commands
cannot be sent directly via XSWI LN. Control commands have to be sent via CSWI LN.
In F650 relay the Circuit Breaker (XCBR1 Logical Node) by default is mapped to first switchgear (exactly like XSWI1
and CSWI1 LNs). However it is possible to map the Circuit Breaker to any of the 16 switchgears of F650 relay. It can
be done by modification of the following setting: Setpoint > System Setup > Breaker Settings > Number of
Switchgear.
In XCBR LN for "Pos" controllable attribute all possible control models are applicable:
• "direct-control-with-normal-security"
• "SBO-control-with-normal-security"
• "direct-control-with-enhanced-security"
• "SBO-control-with-enhanced-security"
The sboTimeout attribute for Pos is configurable in a range from 500 ms to 60 seconds.
The sboClass attribute for Pos can only have value "0" (operate-once).
XSWI class
Attribute Attribute Explanation M/O/E Notes
Name Type
XSWI Circuit switch
Data
Common Logical Node Information
Mod INC Mode M Status-only
Beh INS Behavior M
Health INS Health M
NamPlt LPL Name plate M
Loc SPS Local operation M Local / Remote
EEHealth INS External equipment health O
OpCnt INS Operation counter M Breaker openings
Controls
Pos geDPC Switch position M Status-only
BlkOpn SPC Block opening M Status-only
BlkCls SPC Block closing M Status-only
Status information
SwTyp INS Switch Type M Fixed value = 2 (Disconnecter)
SwOpCap INS Switch operating capability M Fixed value = 5
In the F650 there are up to 16 configurable switchgears. Currently sixteen XSWI and sixteen CSWI are implemented
and mapped to the first sixteen switchgears in F650. XSWI and CSWI Logical Nodes can be seen as paired objects
in F650 as one pair of XSWI and CSWI map to the same switchgear. XSWI1 and CSWI1 map to Switchgear1,
XSWI2 and CSWI2 map to Switchgear2, etc. The difference between XSWI and CSWI in F650 is that control
commands cannot be sent directly via XSWI LN. Control commands have to be sent via CSWI LN.
"Pos" attribute is not controllable in XSWI it has ctlModel = Status-only. In order to control the switch mapped to
given XSWI the corresponding CSWI LN should be used.
3.2 setCharact_2
3.3 PolQty
3.4 AutoRecSt
3.5 InMagTyp
3.6 RsMod
3.7 PolOpMod
3.8 InMod
3.9 PhLogic
3.10 MaxNumShot
7.3.7.3.5 MICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 2
Reference documentation: MICS for 650 family rev 1.05 firm 7_72.
This document describes the:
• Logical Nodes List
• Logical Nodes and Extensions
• Enum types implementation
RSYN (Synchrocheck)**
C: Logical Nodes for control
CILO (Interlocking)
CSWI (Switch controller)
G: Logical Nodes for generic references
GGIO (Generic process I/O)
M: Logical Nodes for metering and measurement
MMTR (Metering)
MMXU (Measurement)
MSQI (Sequence and imbalance)
X: Logical Nodes for switchgear
XCBR (Circuit breaker)
XSWI (Circuit switch)
S: Logical Nodes for supervision and monitoring
SCBR (Circuit breaker supervision)
Nodes with ** in the table above have been included from firmware version 7.50
Notation:
ØM: Data is mandatory in the IEC-61850-7-4.
ØO: Data is optional in the IEC-61850-7-4 and is used in the device.
ØE: Data is an extension to the IEC-61850-7-4.
2.1 System Logical Nodes. LN Group: L
LPHD class
Attribute Attr. Explanation M/O Notes
Name Type
LPHD Physical device information M
Data
Common Logical Node Information
PhyNam geDPL Physical device name plate M
PhyHealth geHealthENS Physical device health M
Proxy geSPS Indicates if this LN is a proxy M
2.1.2.1 LLN0 (geLLN0) Logical node zero --> one instance in Protection LDevice
LLN0 class
Attribute Attr. Explanation M/O Notes
Name Type
LLN0 Logical node zero
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL_1 Name plate M
Loc geSPS Local control behavior O
2.1.2.2 LLN0 (geLLN0_LocSta) Logical node zero --> one instance in Control LDevice
LLN0 class
Attribute Attr. Explanation M/O Notes
Name Type
LLN0 Logical node zero
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL_1 Name plate M
Loc geSPS Local control behavior O
OpTmh geINS Operation time O
lLocSta geSPC_2 Switching authority at station level O
GoCB (ACSI class Goose Control Block)
GoCB GoCB
2.1.3 LCCH (geLCCH) --> physical channel status: one instance in Control LDevice
LCCH class
Attribute Attr. Explanation M/O Notes
Name Type
LCCH Logical node zero
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
ChLiv geSPS Physical channel status M
RedChLiv geSPS Physical channel status of redundant channel O
GoCB class
Attribute Name Attribute Type FC Notes
GoEna BOOLEAN GO Enable (TRUE), disable (FALSE)
GoID VISIBLE STRING65 GO
DatSet Object Reference GO
ConfRev INT32U GO
NdsCom BOOLEAN GO
DstAddress PHYCOMADDR GO
2.1.5 LGOS (LGOS) --> GOOSE subscription information: 24 instances in Control LDevice
For firmware version 7.00 or higher, this LN Logical is used for monitoring GOOSE messages, diagnosing the
subscription state of a GOOSE message and has 24 instances inside the device
LGOS class
Attribute Attr. Explanation M/O Notes
Name Type
LGOS GOOSE subscription
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
St geSPS Status of the subscription M
LastStNum geINS Last state number received O
ConfRevNum geINS Expected conf. revision num. O
Settings
GoCBRef geORG Ref. to the subscribed GOOSE control block O
2.1.6 LTMS (geLTMS) --> Time synchronization: one instance in Control LDevice
LTMS class
Attribute Attr. Explanation M/O Notes
Name Type
LTMS Time master supervision
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
TmSrc geVSS Current time source M
SGCB class
Attribute Name Attribute Type FC Notes
NumOfSG INT8U SE/SG Total number of settings groups available in the LDevice.
Fixed at 6.
ActSG NT8U SE/SG Setting group whose values are used by a logical node to
perform its function.
EditSG NT8U SE/SG Setting group whose values can be set.
CnfEdit BOOLEAN SE/SG
LactTm TimeStamp SE/SG
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.2.1.2 phsPIOC_2
This logical node class is used for phase instantaneous overcurrent when setting group option is enabled and has 2
instances inside the device. This logical node class is available only for firmware version below 7.50.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str PhsACD Start O IOC PKP
Op PhsACT Operate M IOC OP
Blk SPS Block O
Settings
PIOCEna SPG_2 Function O
InMagTyp ING_0_2 Input O
StrVal FloatASG_2 Pickup level O
OpDlTmms ING_8_2 Trip delay O
RsDlTmms ING_8_2 Reset delay O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.1.3 ndPIOC
This logical node class is used for neutral instantaneous overcurrent and has 3 instances inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str NeutACD Start O IOC PKP
Op NeutACT Operate M IOC OP
Blk SPS Block O
Settings
PIOCEna SPG Function O
StrVal FloatASG Pickup level O
OpDlTmms ING_8 Trip delay O
RsDlTmms ING_8 Reset delay O
SnpshtEvEna SPG Snapshot events enabled O
2.2.1.4 ndPIOC_2
This logical node class is used for neutral instantaneous overcurrent if setting group option is enable and has 1
instance inside the device. This logical node class is available only for firmware version below 7.50
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str NeutACD Start O IOC PKP
Op NeutACT Operate M IOC OP
Blk SPS Block O
Settings
PIOCEna SPG_2 Function O
StrVal FloatASG_2 Pickup level O
OpDlTmms ING_8_2 Trip delay O
RsDlTmms ING_8_2 Reset delay O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.1.5 gndPIOC/hsePIOC
This logical node class is used for ground instantaneous and sensitive ground instantaneous overcurrent. There are
6
instances (3 for ground and 3 for sensitive ground instantaneous overcurrent) of this logical node inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geNeutACD Start O IOC PKP
Op geNeutACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG Function O
InMagTyp geING_0 Input O
StrVal geFloatASG Pickup level O
OpDlTmms geING_8 Trip delay O
RsDlTmms geING_8 Reset delay O
SnpshtEvEna geSPG Snapshot events enabled O
2.2.1.5 gndPIOC_2
This logical node class is used for ground instantaneous and sensitive ground instantaneous overcurrent when
setting group option is enable. There are 2 instances (1 for ground and 1 for sensitive ground instantaneous
overcurrent) of this logical node inside the device. This logical node class is available only for firmware version below
7.50.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG_2 Function O
VhStr geIntASG_2 Vh level O
VlStr geIntASG_2 Vl level O
IhStr geFloatASG_1_2 Ih level O
IlStr geFloatASG_1_2 Il level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.2.1.7 BknCndPIOC
This logical node class is used for broken conductor function and has 3 instances inside the device. This node have
been included for firmware versions 7.50 or above.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
BlkCurrent geFloatASG_1_2 Operation Threshold O
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG Function O
InMagTyp geING_0 Input O
StrVal geFloatASG Pickup level O
TmACrv geCURVE Curve O
VolRst geSPG Voltage Restraint O
TmMult geFloatASG TD Multiplier O
RsMod geING_0 Reset O
SnpshtEvEna geSPG Snapshot events enabled O
2.2.2.2 phsPTOC_2
This logical node class is used for phase time overcurrent when setting group option is enabled and has 2 instances
inside the device. This logical node class is available only for firmware version below 7.50
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
2.2.2.3 ndPTOC
This logical node class is used for neutral time overcurrent and has 3 instances inside the device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geNeutACD Start O TOC PKP
Op geNeutACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG Function O
StrVal geFloatASG Pickup level O
TmACrv geCURVE Curve O
TmMult geFloatASG TD Multiplier O
RsMod geING_0 Reset O
SnpshtEvEna geSPG Snapshot events enabled O
2.2.2.4 ndPTOC_2
This logical node class is used for neutral time overcurrent when setting group option is enable and has 1 instances
inside the device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geNeutACD Start O TOC PKP
Op geNeutACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.2.2.5 gndPTOC
This logical node class is used for ground time overcurrent and sensitive ground time overcurrent. There are 6
instances inside of this logical node inside the device. 3 for ground and 3 for sensitive ground time overcurrent.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str PhsACD Start M TOC PKP
Op PhsACT Operate M TOC OP
Blk SPS Block O TOC BLK
Settings
PTOCEna SPG Function O
InMagTyp ING_0 Input O
StrVal FloatASG Pickup level O
TmACrv CURVE Curve O
TmMult geFloatASG TD Multiplier O
RsMod geING_0 Reset O
SnpshtEvEna geSPG Snapshot events enabled O
2.2.2.6 gndPTOC_2
This logical node class is used for ground time overcurrent and sensitive ground time overcurrent when setting group
option is enable. There are 2 instances inside of this logical node inside the device, 1 for ground and 1 for sensitive
ground time overcurrent. This logical node class is available only for firmware version below 7.50
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str PhsACD Start M TOC PKP
Op PhsACT Operate M TOC OP
Blk SPS Block O TOC BLK
Settings
PTOCEna SPG_2 Function O
InMagTyp ING_0_2 Input O
StrVal FloatASG_2 Pickup level O
TmACrv CURVE_3 Curve O
TmMult FloatASG_2 TD Multiplier O
RsMod ING_0_2 Reset O
2.2.2.7 hsePTOC
This logical node class is used for sensitive ground time overcurrent function and has 3 instances inside the device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.2.2.8 NgSeqPTOC
This logical node class is used for negative sequence time overcurrent function and has 3 instances inside the
device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
SnpshtEvEna geSPG_2 Snapshot events enabled O
This logical node class is used for overfrequency and has 3 instances for firmware version below 7.20 and 6
instances for firmware version 7.20 or above inside the device.
PTOF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTOF Overfrequency
Data
Common Logical Node Information
Mod ENC Mode M Status-only
Beh ENS Behavior M
Health ENS Health M
NamPlt LPL Name Plate M
Status information
Str ACD Start M TOF PKP
Op ACT Operate M TOF OP
Blk SPS Block O TOF BLK
BlkV SPS Blocked because of voltage O
Settings
StrVal ASG Start value (frequency) O
BlkVal ASG Voltage block value O
OpDlTmms ING Operate delay time O
RsDlTmms ING Reset delay time O
PTOFEna SPG Function TOF enable O
SnpshtEvEna SPG Snapshot events enabled O
FreqSource SPG Frequency source O Firmware version 7.20 or above
2.2.3.2 PTOF_2
This logical node class is used for overfrequency when setting group option is anable and has 1 instances inside the
device.
PTOF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTOF Overfrequency
Data
Common Logical Node Information
Mod ENC Mode M Status-only
Beh ENS Behavior M
Health ENS Health M
NamPlt LPL Name Plate M
Status information
Str ACD Start M TOF PKP
Op ACT Operate M TOF OP
Blk SPS Block O TOF BLK
BlkV SPS Blocked because of voltage O
Settings
StrVal ASG Start value (frequency) O
BlkVal ASG Voltage block value O
OpDlTmms ING Operate delay time O
RsDlTmms ING Reset delay time O
PTOFEna SPG Function TOF enable O
SnpshtEvEna SPG Snapshot events enabled O
FreqSource SPG Frequency source O Firmware version 7.20 or above
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str PhsACD Start M TOV PKP
Op PhsACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG Function O
StrVal IntASG Start value O
OpDlTmms ING_8 Operate delay time O
RsDlTmms ING_8 Reset delay time O
PhLogic ING_0 Logic O
SnpshtEvEna SPG Snapshot events enabled O
2.2.4.2 phsPTOV_2
This logical node class is used for phase overvoltage when setting group option is enabled and has 1 instance inside
the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str PhsACD Start M TOV PKP
Op PhsACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG_2 Function O
StrVal IntASG_3 Start value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
PhLogic ING_0_2 Logic O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.4.3 auxPTOV
This logical node class is used for auxiliary overvoltage and has 3 instances inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TOV PKP
Op GeneralACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG_2 Function O
StrVal IntASG_3 Start value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.4.4 auxPTOV_2
This logical node class is used for auxiliary overvoltage when setting group option is enabled and has 1 instance
inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TOV PKP
Op GeneralACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG_2 Function O
StrVal IntASG_3 Start value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.4.5 neuPTOV
This logical node class is used for neutral overvoltage and has 6 instances inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TOV PKP
Op GeneralACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG Function O
StrVal IntASG Start value O
OpDlTmms ING_8 Operate delay time O
RsDlTmms ING_8 Reset delay time O
SnpshtEvEna SPG Snapshot events enabled O
2.2.4.6 neuPTOV_2
This logical node class is used for neutral overvoltage when setting group option is enabled and has 2 instances
inside the device. This logical node class is available only for firmware version below 7.50.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TOV PKP
Op GeneralACT Operate M TOV OP
Blk SPS Block O TOV BLK
Settings
PTOVEna SPG_2 Function O
StrVal IntASG_3 Start value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.4.7 NgSeqPTOV
This logical node class is used for neutral sequence overvoltage and has 3 instances inside the device. This logical
node class has been included from firmware version 7.50.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TOV PKP
Op geGeneralACT Operate M TOV OP
Blk geSPS Block O TOV BLK
Settings
PTOVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
SnpshtEvEna geSPG_2 Snapshot events enabled O
PTRC class
Attribute Attr. Explanation M/O Notes
Name Type
PTRC Trip bus
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Op geGeneralACT Operate M
This logical node class is used for phase undervoltage and has 3 instances inside the device.
PTUV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
2.2.6.2 phsPTUV_2
This logical node class is used for phase undervoltage when setting group option is enabled and has 1 instances
inside the device.
PTUV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TUV PKP
Op GeneralACT Operate M TUV OP
Blk SPS Block O TUV BLK
StrPhGn PhsACD_1 Pickup Phase-Ground O
OpPhGn PhsACT_1 Operate Phase-Ground O
StrPhPh PhsACD_1 Pickup Phase-Phase O
OpPhPh PhsACT_1 Operate Phase-Phase O
Settings
PTUVEna SPG_2 Function O
InMod ING_0_2 Mode O
StrVal IntASG_3 Start value O
TmVCrv CURVE_4 Operating curve type O
TmMult FloatASG_2 Time dial multiplier O
DeaLinVal IntASG_3 Minimum Voltage O
PhLogic ING_0_2 Logic O
BkrMon SPG_2 Supervised by 52 O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.2.6.3 AuxPTUV
This logical node class is used for auxiliary undervoltage and has 3 instances inside the device.
PTUV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Str GeneralACD Start M TUV PKP
Op GeneralACT Operate M TUV OP
Blk SPS Block O TUV BLK
Settings
PTUVEna SPG Function O
StrVal IntASG Start value O
TmVCrv CURVE_2 Operating curve type O
TmMult FloatASG Time dial multiplier O
SnpshtEvEna SPG Snapshot events enabled O
2.2.6.3 AuxPTUV_2
This logical node class is used for auxiliary undervoltage when setting group is enabled and has 1 instances inside
the device.
PTUV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TUV PKP
Op geGeneralACT Operate M TUV OP
Blk geSPS Block O TUV BLK
Settings
PTUVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
TmVCrv geCURVE_4 Operating curve type O
TmMult geFloatASG_2 Time dial multiplier O
SnpshtEvEna geSPG_2 Snapshot events enabled O
PTUF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTUF Underfrequency
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name Plate M
Status information
Str GeneralACD Start M TUF PKP
Op GeneralACT Operate M TUF OP
Blk SPS Block O TUF BLK
BlkV SPS Blocked because of voltage O
Settings
StrVal FloatASG_2 Start value (frequency) O
BlkVal IntASG_3 Voltage block value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
PTUFEna SPG_2 Function TUF enable E
SnpshtEvEna SPG_2 Snapshot events enabled E
FreqSource SPG_2 Frequency source E
2.2.7.2 PTUF_2
This logical node class is used for phase underfrequency when setting group option is enabled and has 1 instance
inside the device.
PTUF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTUF Underfrequency
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name Plate M
Status information
Str GeneralACD Start M TUF PKP
Op GeneralACT Operate M TUF OP
Blk SPS Block O TUF BLK
BlkV SPS Blocked because of voltage O
Settings
StrVal FloatASG_2 Start value (frequency) O
BlkVal IntASG_3 Voltage block value O
OpDlTmms ING_8_2 Operate delay time O
RsDlTmms ING_8_2 Reset delay time O
PTUFEna SPG_2 Function TUF enable E
SnpshtEvEna SPG_2 Snapshot events enabled E
FreqSource SPG_2 Frequency source E
PTTR class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTTR Thermal overload
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name Plate M
Status information
Str ACD Start M Thermal PKP
Op PhsACT Operate M Thermal OP
Blk SPS Block O Thermal BLK
AlmThm SPS Thermal alarm O
AlmThmPhA SPS_1 Thermal alarm phase A O
AlmThmPhB SPS_1 Thermal alarm phase B O
AlmThmPhC SPS_1 Thermal alarm phase C O
Settings
PTTREna SPG_2 Thermal overload enable O
ConsTmmHeat FloatASG_1_2 Heat time constant O
ConsTmmCool FloatASG_1_2 Cool time constant O
StrVal FloatASG_2 Pickup level O
AlmVal FloatASG_2 Alarm level O
SnpshtEvEna SPG_2 Snapshot events enabled O
PDOP class
Attribute Attr. Explanation M/O Notes
Name Type
PDOP Overpower
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS Block O
S1Str gePhsACD_2 Start O Stage 1 PKP
S1Op gePhsACT_1 Operate O Stage 1 OP
S2Str gePhsACD_2 Start O Stage 2 PKP
S2Op gePhsACT_1 Operate O Stage 2 OP
Settings
PDOPEna geSPG_2 Function O
BlkCloseTmms geING_0_2 Blk time after close O
S1DirPwrAng geFloatASG_1_2 Dir Power Angle 1 O
S1StrVal geFloatASG_1_2 Stage 1 Tap O
S1OpDlTmms geING_0_2 Stage 1 Time O
S2DirPwrAng geFloatASG_1_2 Dir Power Angle 2 O
S2StrVal geFloatASG_1_2 Stage 2 Tap O
S2OpDlTmms geING_0_2 Stage 2 Time O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.2.9.3 WattPDOP
This logical node class shall be used to model the wattmeter ground overpower function and has six instances inside
the device.
PDOP class
Attribute Attr. Explanation M/O Notes
Name Type
PDOP Overpower
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS Block O
SupStr gePhsACD_2 Start O
Settings
PDOPEna geSPG_2 Function O
OVStrVal geFloatASG_1_2 Voltage Pickup Level O
InMagTyp geING_0_2 Current Selection O
PFRC class
Attribute Attr. Explanation M/O Notes
Name Type
PFRC Frequency Rate of Change
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS Block O
Settings
PFRCEna geSPG_2 Function O
Trend geING_0_2 Freq Rate Trend O
StrVal geFloatASG_2 Freq Rate Pickup O
BlkVal geFloatASG_2 Freq Rate Min Volt O
BlkMinFreq geFloatASG_1_2 Freq Rate Min Freq O
BlkMaxFreq geFloatASG_1_2 Freq Rate Max Freq O
OpDlTmms geING_8_2 Freq Rate Delay O
SnpshtEvEna geSPG_2 Snapshot events O
PDIS class
Attribute Attr. Explanation M/O Notes
Name Type
PDIS Distance
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS Block O
Settings
PDISEna geSPG_2 Function O
MinVoltage geFloatASG_1_2 Freq Rate Trend O
RisLod geFloatASG_2 Freq Rate Pickup O
AngLod geFloatASG_2 Freq Rate Min Volt O
OpDlTmms geING_8_2 Operation Delay O
RsDlTmms geING_8_2 Reset Delay O
SnpshtEvEna geSPG_2 Snapshot events O
PRTR class
Attribute Attr. Explanation M/O Notes
Name Type
PRTR Rotor Protection
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M
Op geGeneralACT Operate M
Blk geSPS Block O
Settings
PRTREna geSPG_2 Function O
InMagTyp geING_0_2 Input O
LodCurrent geFloatASG_1_2 Full Load Current O
strVal geFloatASG_2 Pickup Level O
OpDlTmms geING_8_2 Operation Delay O
RsDlTmms geING_8_2 Reset Delay O
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir PhsACD Direction M
Op PhsACT Operate O
Blk SPS Block O
BlkIn GeneralACT_1 Block Input O
Settings
RDIREna SPG Function O
ChrAng FloatASG Characteristic angle O
PolOpMod ING_0 Direction O
BlkMod ING_0 Block Logic O
BlkValV IntASG Minimum operating current O
VMemTms FloatASG Voltage Memory Time O
SnpshtEvEna SPG Snapshot events enabled O
2.3.1.2 phsRDIR_2
This logical node class is used for phase directional elements when setting group option is enabled and
has 1 instance inside the device.
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir PhsACD Direction M
Op PhsACT Operate O
Blk SPS Block O
BlkIn GeneralACT_1 Block Input O
Settings
RDIREna SPG_2 Function O
ChrAng FloatASG_2 Characteristic angle O
PolOpMod ING_0_2 Direction O
BlkMod ING_0_2 Block Logic O
BlkValV IntASG_3 Minimum operating current O
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir NeutACD Direction M
Op NeutACT Operate O
Blk SPS Block O
BlkIn NeutACT_1 Block Input O
Settings
RDIREna SPG Function O
ChrAng FloatASG Characteristic angle O
PolOpMod ING_0 Direction O
PolQty ENG Polarizing quantity O
BlkMod ING_0 Block Logic O
BlkValV IntASG Minimum operating current O
SnpshtEvEna SPG Snapshot events enabled O
2.3.1.4 ndRDIR_2
This logical node class is used for neutral directional elements when setting group option is enable and has 1
instance inside the device.
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir NeutACD Direction M
Op NeutACT Operate O
Blk SPS Block O
BlkIn NeutACT_1 Block Input O
Settings
RDIREna SPG_2 Function O
ChrAng FloatASG_2 Characteristic angle O
PolOpMod ING_0_2 Direction O
PolQty ENG_2 Polarizing quantity O
BlkMod ING_0_2 Block Logic O
BlkValV IntASG_3 Minimum operating current O
SnpshtEvEna SPG_2 Snapshot events enabled O
2.3.1.5 gndRDIR
This logical node class is used for ground directional elements and has 3 instances inside the device
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir NeutACD Direction M
Op NeutACT Operate O
Blk SPS Block O
BlkIn NeutACT_1 Block Input O
Settings
RDIREna SPG Function O
ChrAng FloatASG Characteristic angle O
PolOpMod ING_0 Direction O
PolQty ENG Polarizing quantity O
BlkMod ING_0 Block Logic O
BlkValV IntASG Minimum operating current O
SnpshtEvEna SPG Snapshot events enabled O
2.3.1.6 gndRDIR_2
This logical node class is used for ground directional elements when setting group option is enabled and has 1
instance inside the device
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir NeutACD Direction M
Op NeutACT Operate O
Blk SPS Block O
BlkIn NeutACT_1 Block Input O
Settings
RDIREna SPG_2 Function O
ChrAng FloatASG_2 Characteristic angle O
PolOpMod ING_0_2 Direction O
PolQty ENG_2 Polarizing quantity O
BlkMod ING_0_2 Block Logic O
BlkValV IntASG_3 Minimum operating current O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.3.1.7 hseRDIR
This logical node class is used for sensitive ground directional elements and has 3 instances inside the device.
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir GeneralACD Direction M
Op GeneralACT Operate O
Blk SPS Block O
BlkIn GeneralACT_1 Block Input O
Settings
RDIREna SPG Function O
ChrAng FloatASG Characteristic angle O
PolOpMod ING_0 Direction O
BlkMod ING_0 Block Logic O
BlkValV IntASG Minimum operating current O
SnpshtEvEna SPG Snapshot events enabled O
2.3.1.8 hseRDIR_2
This logical node class is used for sensitive ground directional elements when setting group option is enabled and
has 1 instance inside the device. This logical node class is available only for firmware version below 7.50.
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
Dir GeneralACD Direction M
Op GeneralACT Operate O
Blk SPS Block O
BlkIn GeneralACT_1 Block Input O
Settings
RDIREna SPG_2 Function O
ChrAng FloatASG_2 Characteristic angle O
PolOpMod ING_0_2 Direction O
BlkMod ING_0_2 Block Logic O
BlkValV IntASG_3 Minimum operating current O
SnpshtEvEna SPG_2 Snapshot events enabled O
RREC class
Attribute Attr. Explanation M/O Notes
Name Type
RREC Autoreclosing Element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
OpCls GeneralACT Direction M
AutoRecSt AutoRecStENS Operate M
AutoRecLo INS_1 Block O
AutoRecBlk INS_1 Block Input O
RecCyc INS Actual Reclose Cycle O
Settings
RRECEna SPG Function O
MaxNumShot ING_0 Max. Number Shots O
Rec1Tmms1 ING_8 Dead Time 1 O
Rec1Tmms2 ING_8 Dead Time 2 O
Rec1Tmms3 ING_8 Dead Time 3 O
Rec1Tmms4 ING_8 Dead Time 4 O
RclTmms ING_8 Reclaim time
CondEna SPG Cond. Permission
HoldTmms FloatASG_1 Hold Time
RsTmms FloatASG_1 Reset Time
For firmware versions 7.00 or higher, this logical node class is used for breaker failure and has 1 instance inside the
device.
RREC class
Attribute Attr. Explanation M/O Notes
Name Type
RBRF Breaker failure element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
OpEx GeneralACT Direction M
RFLO class
Attribute Attr. Explanation M/O Notes
Name Type
RFLO Fault locator element
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
FltRprtTrg SPS_1 Fault Report Trigger O
ClrFltRprts SPS_1 Clear fault reports O
FltZ FloatCMV Fault impedance M
FltDiskm FloatMV_3 Fault distance in km O
RPriFlt FloatMV_2 Primary Fault Resistance O
XPriFlt FloatMV_2 Primary Fault Reactance O
RSeFlt FloatMV_2 Secondary Fault Resistance O
XSeFlt FloatMV_2 Secondary Fault Reactance O
RFault FloatMV_2 Fault Resistance O
FltTyp INS_1 Fault type O
FltRprtNum INS_1 Fault report number O
PreFltIaMod FloatMV_2 Prefault Ia module O
PreFltIaAng FloatMV_2 Prefault Ia angle O
PreFltIbMod FloatMV_2 O
PreFltIbAng FloatMV_2 O
PreFltIcMod FloatMV_2 O
PreFltIcAng FloatMV_2 O
PreFltIgMod FloatMV_2 O
PreFltIgAng FloatMV_2 O
PreFltIsgMod FloatMV_2 O
PreFltIsgAng FloatMV_2 O
PreFltVabMod FloatMV_2 O
PreFltVabAng FloatMV_2 O
PreFltVbcMod FloatMV_2 O
PreFltVbcAng FloatMV_2 O
PreFltVcaMod FloatMV_2 O
PreFltVcaAng FloatMV_2 O
PstFltIaMod FloatMV_2 Postfault Ia module O
PstFltIaAng FloatMV_2 Postfault Ia angle O
PstFltIbMod FloatMV_2 O
PstFltIbAng FloatMV_2 O
PstFltIcMod FloatMV_2 O
PstFltIcAng FloatMV_2 O
PstFltIgMod FloatMV_2 O
PstFltIgAng FloatMV_2 O
PstFltIsgMod FloatMV_2 O
PstFltIsgAng FloatMV_2 O
PstFltVabMod FloatMV_2 O
PstFltVabAng FloatMV_2 O
PstFltVbcMod FloatMV_2 O
PstFltVbcAng FloatMV_2 O
PstFltVcaMod FloatMV_2 O
PstFltVcaAng FloatMV_2 O
Settings
RBDR class
Attribute Name Attribute type Explanation M/O/C/E Notes
RBDR Disturbance recorder channel binary
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name Plate M
Status information
ChTrg SPS Channel triggered M
DigCh01 SPS_1 O
… … … …
DigChn16 SPS_1 O
RDRE class
Attribute Name Attribute type Explanation M/O/C/E Notes
RDRE Disturbance recorder channel binary
Data
Common Logical Node Information
Mod ENC Mode M Status-only
Beh ENS Behavior M
Health ENS Health M
NamPlt LPL Name Plate M
Status information
RcdMade SPS Recording made M
FltNum INS Fault number M
OscTrg SPS Oscillo trigger E
CycRcd INS Cycles per record E
RcdNum INS Available records E
Controls
RcdTrg geSPC_1 Trigger Recorder M
Settings
RDREEna SPG Oscillography function enable E
RSYN class
Attribute Attr. Explanation M/O Notes
Name Type
RSYN Synchronism-check
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status Information
Blk geSPS Block signal O
SynOp geSPS_1 Closing permission signal O
Rel geSPS Release M
SynCondOp geSPS_1 Closing perm. according to logic O
DLDBOp geSPS_1 Closing perm. in DLDB condition O
DLLBOp geSPS_1 Closing perm. in DLLB condition O
LLDBOp geSPS_1 Closing perm. in LLDB condition O
HzInd geSPS Frequency difference indicator O
BusHzHiLinHz geSPS_1 Busbar frequency > line frequency O
BusHzLoLinHz geSPS_1 Busbar frequency < line frequency O
Measured values
DifVClc geFloatMV Calculated difference in voltage O
DifHzClc geFloatMV Calculated difference in frequency O
DifAngClc geFloatMV Calculated difference in angle O
Settings
RSYNEna geSPG Function O
DeaBusVal geFloatASG Dead bus value O
LivBusVal geFloatASG Live bus value O
DeaLinVal geFloatASG Dead line value O
LivLinVal geFloatASG Live line value O
DifV geFloatASG Difference voltage O
DifAng geFloatASG Difference angle O
DifHz geIntASG Difference frequency O
TotTmms geING_8 Total time of synch. process O
DLDBEna geSPG Dead line - dead bus permission O
LLDBEna geSPG Live line - dead bus permission O
DLLBEna geSPG Dead line - live bus permission O
SnpshtEvEna geSPG Snapshot events enabled O
CILO class
Attribute Attr. Explanation M/O Notes
Name Type
CILO Switch controller
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status Information
EnaOpn SPS Enable Open M
EnaCls SPS Enable Close M
CSWI class
Attribute Name Attribute Type Explanation M/O/E Notes
CSWI Switch controller
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Controls
Pos DPC_3 Switch position M Switch open, close, undefined
Status Information
Loc SPS Local control behavior O Local/Remote
For firmware version 7.20 or above
In the F650 there are up to 16 configurable switchgears. Currently sixteen XSWI and sixteen CSWI are implemented
and mapped to all switchgears in F650. XSWI and CSWI Logical Nodes can be seen as paired objects in F650 as
one pair of XSWI and CSWI map to the same switchgear. XSWI1 and CSWI1 map to Switchgear1, XSWI2 and
CSWI2 map to Switchgear2, etc. The difference between XSWI and CSWI in F650 is that control commands cannot
be sent directly via XSWI LN. Control commands have to be sent via CSWI LN.
• In CSWI LN for "Pos" controllable attribute all possible control models are applicable:
• "direct-control-with-normal-security"
• "SBO-control-with-normal-security"
• "direct-control-with-enhanced-security"
• "SBO-control-with-enhanced-security"
The sboTimeout attribute for Pos is configurable in a range from 500 ms to 60 seconds.
The sboClass attribute for Pos can only have value "0" (operate-once).
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status information
BoardSt SPS_1 Board status O
Ind1 SPS Status contact input 1 O
Ind2 SPS Status contact input 2 O
.. .. .. ..
Ind32 SPS Status contact input 32 O
Ind33 SPS Status contact output 1 O
.. .. ..
Ind48 SPS Status contact output 16 O
Measured and metered values
AnIn1 FloatMV Analog input 1 O
AnIn2 FloatMV Analog input 2 O
.. .. ..
AnIn8 FloatMV Analog input 8 O
Settings
VThrldA IntASG_1 Voltage threshold A O
VThrldB IntASG_1 Voltage threshold B O
VThrldC IntASG_1 Voltage threshold C O
VThrldD IntASG_1 Voltage threshold D O
DbceTmmsA ING_0 Debounce time A O
DbceTmmsB ING_0 Debounce time B O
DbceTmmsC ING_0 Debounce time C O
DbceTmmsD ING_0 Debounce time D O
InTyp01 ING_0 Type input 1 O
InTyp02 ING_0 Type input 2 O
.. .. .. ..
InTyp32 ING_0 Type input 32 O
DlInTmms01 ING_0 Delay time input 1 O
DlInTmms02 ING_0 Delay time input 2 O
.. .. .. ..
DlInTmms32 ING_0 Delay time input 32 O
OutLogic01 ING_0 Logic output 1 O
OutLogic02 ING_0 Logic output 2 O
.. .. .. ..
OutLogic16 ING_0 Logic output 16 O
OutTyp01 ING_0 Type output 1 O
OutTyp02 ING_0 Type output 2 O
.. .. ..
OutTyp16 ING_0 Type output 16 O
PlsOutTmms01 ING_0 Pulse time output 1 O
PlsOutTmms02 ING_0 Pulse time output 2 O
.. .. ..
PlsOutTmms16 ING_0 Pulse time output 16 O
2.5.1.2 vinGGIO
This logical node class is used is used to map the latched and self reset virtual Inputs.
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModENC Mode M Status-only
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Controls
DPCSO01 geDPC Double point controllable status O Latched Virtual Input 1, 2
output
DPCSO02 geDPC Double point controllable status O Latched Virtual Input 3, 4
output
.. .. .. .. ..
DPCSO16 geDPC Double point controllable status O Latched Virtual Input 31, 32
output
SPCSO01 SPC Single point controllable status output O Latched Virtual Input 1
SPCSO02 SPC Single point controllable status output O Latched Virtual Input 2
.. .. .. .. ..
SPCSO32 SPC Single point controllable status output O Latched Virtual Input 32
SPCSO33 SPC Single point controllable status output O Self reset Virtual Input 1
SPCSO34 SPC Single point controllable status output O Self reset Virtual Input 2
.. .. .. .. ..
SPCSO64 SPC Single point controllable status output O Self reset Virtual Input 32
Note:
Double control points operate on pairs of Virtual Inputs in a manner that one Virtual Input of the pair is set to "1" and
the other Virtual Input of the pair is set to "0".
For all controllable attributes in this logical node only "direct-control-with-normal-security" model of control is
applicable
2.5.1.3 eveGGIO
This logical node class is used to map data from the list of any all internal digital states (PLC control events).
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod ModENC Mode M Status-only
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS General Indication (binary O Control Event 1
input)
Ind2 SPS General Indication (binary O Control Event 2
input)
......... .......... ............... .......... ..............
Ind128 SPS General Indication (binary O Control Event 128
input)
Ind129 SPS General Indication (binary O Switchgear 1 event 1
input)
Ind130 SPS General Indication (binary O Switchgear 1 event 2
input)
Ind131 SPS General Indication (binary O Switchgear 1 event 3
input)
Ind132 SPS General Indication (binary O Switchgear 1 event 4
input)
Ind133 SPS General Indication (binary O Switchgear 2 event 1
input)
......... .......... ............... .......... ..............
Ind192 SPS General Indication (binary O Switchgear 16 event 4
input)
2.5.1.4 geRemoteInputsGGIO
This logical node class is used to map data from incoming GOOSE messages.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS Remote digital input 1 O
Ind2 SPS Remote digital input 2 O
.. .. .. ..
Ind64 SPS Remote digital input 32 O
2.5.1.5 geRemoteOutputsGGIO
This logical node class is used to map PLC digital states for outgoing GOOSE messages.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Status information
Ind1 SPS Remote digital output 1 O
Ind2 SPS Remote digital output 2 O
.. .. .. ..
Ind32 SPS Remote digital output 32 O
Note: In 650 relays data from all logical nodes can be sent through outgoing GOOSE messages. Apart from that,
logical node rouGGIO gives the ability to send through GOOSE digital states that are results of PLC logic equations.
Mapping and configuration of rouGGIO states should be done with EnerVista 650 software.
2.5.1.6 dcntGGIO:
For versions 7.00 or higher, this logical node is used for modeling the eight digital counters of F650 relay.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status information
AnOutInt1 geIntMV_2 Virtual Output Analogue Int32 1 O
.. .. .. ..
AnOutInt50 geIntMV_2 Virtual Output Analogue Int32 50 O
AnOutF1 geFloatMV_5 Virtual Output Analogue Flt32 1 O
.. .. ..
AnOutF50 geFloatMV_5 Virtual Output Analogue Flt32 50 O
MMTR class
Attribute Attr. Explanation M/O Notes
Name Type
MMTR Measurement
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Measured values
SupWh BCR Pulse Counter 1/Real energy supply O
SupVArh BCR Pulse Counter 2/Reactive energy supply O
DmdWh BCR Pulse Counter 3/Real energy demand O
DmdVArh BCR Pulse Counter 4/Reactive energy demand O
CntPsWh FloatMV_1 Positive Wat Counter O
CntNgWh FloatMV_1 Negative Wat Counter O
CntPsVArh FloatMV_1 Positive VAR Counter O
CntNgVArh FloatMV_1 Negative VAR Counter O
MMXU class
Attribute Attr. Explanation M/O Notes
Name Type
MMXU Measurement
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Measured values
TotW FloatMV Total active power (P) O
TotVAr FloatMV Total reactive power (Q) O
TotVA FloatMV Total apparent power (S) O
TotPF FloatMV Average power factor (PF) O
Hz FloatMV Line Frequency O
PPV FloatDEL Phase to phase voltages (VL1L2,...) O
PhV FloatPhsWYE Phase to ground voltages (VL1ER, ...) O
A FloatWYE Phase currents (IL1, ...) O
AuxV FloatCMV_1 Auxiliary Phase Voltage O
BusHz FloatMV_1 Bus Frequency O
MaxDmdTotW geFloatMV_1 Demand W Max O
MinDmdTotW geFloatMV_1 Demand W Min O
MaxDmdTotVAr geFloatMV_1 Demand VAr Max O
MinDmdTotVAr geFloatMV_1 Demand VAr Min O
MaxDmdTotVA geFloatMV_1 Demand VA Max O
MinDmdTotVA geFloatMV_1 Demand VA Min O
2.6.3 MSQI (Sequence and imbalance) - MSQI (geMSQI) --> sequence and imbalance analogues values: 1
instance in Control LDevice
MSQI class
Attribute Attr. Explanation M/O Notes
Name Type
MSQI Measurement
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Measured values
SeqA FloatSEQ O
SeqV FloatSEQ O
XCBR class
Attribute Attr. Explanation M/O Notes
Name Type
XCBR Circuit breaker
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Descriptions
EEName geDPL External equipment name plate M
Status information
Loc SPS Local operation M Local / Remote
OpCnt INS Operation counter M Breaker openings
SumSwARs O
CBOpCap CBOpCapENS Circuit breaker operating O
capability
Controls
Pos DPC_1 Switch position M Breaker open, close
BlkOpn SPC_1 Block opening M Virtual output
BlkClr SPC_1 Block closing M Virtual output
Settings
ThAlSwA FloatASG_1 Maximum KI2t O
SumSwATmms FloatASG_1 KI2t Integ. Time O
ExNumTr IntASG_1 Maximum Openings O
ExNumTr1hr IntASG_1 Max.Openings 1 hour O
In the F650 there are up to 16 configurable switchgears. Currently sixteen XSWI and sixteen CSWI are implemented
and mapped to all switchgears in F650. XSWI and CSWI Logical Nodes can be seen as paired objects in F650 as
one pair of XSWI and CSWI map to the same switchgear. XSWI1 and CSWI1 map to Switchgear1, XSWI2 and
CSWI2 map to Switchgear2, etc. The difference between XSWI and CSWI in F650 is that control commands cannot
be sent directly via XSWI LN. Control commands have to be sent via CSWI LN.
In F650 relay the Circuit Breaker (XCBR1 Logical Node) by default is mapped to first switchgear (exactly like XSWI1
and CSWI1 LNs). However it is possible to map the Circuit Breaker to any of the 16 switchgears of F650 relay. It can
be done by modification of the following setting: Setpoint > System Setup > Breaker Settings > Number of
Switchgear.
In XCBR LN for "Pos" controllable attribute all possible control models are applicable:
• "direct-control-with-normal-security"
• "SBO-control-with-normal-security"
• "direct-control-with-enhanced-security"
• "SBO-control-with-enhanced-security"
The sboTimeout attribute for Pos is configurable in a range from 500 ms to 60 seconds.
The sboClass attribute for Pos can only have value "0" (operate-once).
XCBR class
Attribute Attr. Explanation M/O Notes
Name Type
XSWI Circuit switch
Data
Common Logical Node Information
Mod ModENC Mode M
Beh BehENS Behavior M
Health HealthENS Health M
NamPlt LPL Name plate M
Descriptions
EEName geDPL External equipment name plate M
Status information
Loc SPS Local operation M Local / Remote
EEHealth EEHealthENS Ext. equipment health O
OpCnt INS Operation counter M Breaker openings
Controls
Pos DPC_3 Switch position M Breaker open, close
BlkOpn SPC_1 Block opening M Virtual output
BlkCls SPC_1 Block closing M Virtual output
SwTyp SwTypENS Switch type M
SwOpCap SwOpCapENS Switch operating capability
SCBR class
Attribute Attr. Explanation M/O Notes
Name Type
d Vstring255 DC O
geINS_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Status
stVal Boolean ST dchg M
q BVstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
DataAttribute
Control And Status
general Boolean ST dchg M
neut Boolean ST dchg O
q Bvstring13 ST qchg M
t Utctime ST M
originSrc Struct ST O
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geGeneralACT
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
general Boolean ST dchg M
q Bvstring13 ST qchg M
t Utctime ST M
originSrc Struct ST O
Configuration, Description And Extension
d Vstring255 DC O
geGeneralACT_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
general Boolean ST dchg M
q Bvstring13 ST qchg M
t Utctime ST M
originSrc Struct ST O
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
zeroDb INT32U CF O
rangeC RangeConfig CF O
hhLim FloatAnalogueValue
f
FLOAT32 GC_1
hlim
f FloatAnalogueValue
lLim FLOAT32 GC_1
f FloatAnalogueValue
llLim FLOAT32 GC_1
f
FloatAnalogueValue
min
f FLOAT32 GC_1
max FloatAnalogueValue
f FLOAT32 GC_1
limDb FloatAnalogueValue
FLOAT32 GC_1
INT32U
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geFloatMV_2
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
mag FloatAnalogueValue MX dchg M
f FLOAT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geFloatMV_3
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
mag FloatAnalogueValue MX dchg M
f FLOAT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
d Vstring255 DC O
geIntMV
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
instMag IntAnalogueValue MX ------ O
i INT32 GC_1
mag IntAnalogueValue MX dchg M
i INT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
db INT32U CF O
d Vstring255 DC O
geIntMV_1
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
instMag IntAnalogueValue MX ------ O
i INT32 GC_1
mag IntAnalogueValue MX dchg M
i INT32 GC_1
range ENUMERATED(Byte) MX dchg O
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
db INT32U CF O
zeroDb INT32U CF O
rangeC RangeConfig CF O
hhLim IntAnalogueValue
i
INT32U GC_1
hlim
i IntAnalogueValue
lLim UINT32 GC_1
i IntAnalogueValue
llLim INT32U GC_1
i
IntAnalogueValue
min
i INT32U GC_1
max IntAnalogueValue
i INT32U GC_1
limDb IntAnalogueValue
INT32U GC_1
INT32U
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
zeroDb INT32U CF O
rangeC RangeConfig CF O
rangeAngC RangeConfig CF O
d Vstring255 DC O
geFloatCMV_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Measured Attributes
instCVal FloatVector MX ------ O
mag FloatAnalogueValue
f FLOAT32
cVal FloatVector MX dchg M
mag FloatAnalogueValue
f FLOAT32
range ENUMERATED(Byte) MX dchg O
rangeAng ENUMERATED(Byte) MX dchg O
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit Byte M
Multiplier Byte O
db INT32U CF O
dbAng INT32U CF O
zeroDb INT32U CF O
rangeC RangeConfig CF O
rangeAngC RangeConfig CF O
d Vstring255 DC O
dataNs Vstring255 EX M
3.2.3 Phase to ground related measured values of a three phase system (WYE)
WYE class
geFloatPhsWYE
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsA CMV_0 GC_1
phsB CMV_0 GC_1
phsC CMV_0 GC_1
neut CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
geFloatWYE
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsA CMV_0 GC_1
phsB CMV_0 GC_1
phsC CMV_0 GC_1
neut CMV_0 GC_1
net CMV_0 GC_1
res CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
3.2.4 Phase to phase related measured values of a three phase system (DEL)
DEL class (Phase to phase related measured values of a three phase system)
geFloatDEL
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsAB CMV_0 GC_1
phsBC CMV_0 GC_1
phsCA CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
SPC class
geSPC
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal Boolean ST FALSE | TRUE AC_ST
q Quality ST AC_ST
t TimeStamp ST AC_ST
Oper ctlVal Boolean CO AC_CO_M
origin Originator CO AC_CO_M
orCat ENUMERATED M
orIdent OCTECT64 M
ctlNum INT8U CO M
T Btime6 CO M
Test Boolean CO M
Check ENUMERATED CO M
Configuration, Description And Extension
ctlModel ENUMERATED CF ctlModel M
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
geSPC_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal Boolean ST FALSE | TRUE AC_ST
Q Quality ST AC_ST
t TimeStamp ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF ctlModel_1 M
d Vstring255 DC O
ctlModel ENUMERATED CF M
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
geDPC_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
Oper ctlVal Boolean CO AC_CO_M
origin Originator CO,ST AC_CO_M
orCat ENUMERATED M
orIdent OCTECT64 M
ctlNum INT8U CO,ST M
T Btime6 CO M
Test Boolean CO M
Check ENUMERATED CO M
Cancel
SBO
SBOw
stVal CODE ENUM ST dchg intermediate-state | off | on | bad- M
state
q BVstring13 ST qchg AC_ST
t Utctime ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF M
sboTimeout INT32U CF AC_CO_O
sboClass ENUMERATED CF AC_CO_O
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
geDPC_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal CODE ENUM ST dchg intermediate-state | off | on | bad- M
state
q BVstring13 ST qchg AC_ST
t Utctime ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF M
d Vstring255 DC O
SPG class
geSPG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SP AC_NSG_M
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX O
geSPG_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SG AC_SG_M
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX O
ING class
geING_0
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SP AC_NSG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
dataNs Vstring255 EX O
geING_0_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SG AC_SG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
dataNs Vstring255 EX O
geING_8
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SP AC_NSG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
geING_8_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SG AC_SG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
ENG class
geENG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Enumerated SP PolQty AC_NSG_M
Configuration, Description And Extension
d Vstring255 DC O
geENG_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Enumerated SG PolQty AC_SG_M
Configuration, Description And Extension
d Vstring255 DC O
ORG class
geORG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setSrcRef ObjectReference SP Object reference M
Configuration, Description And Extension
d Vstring255 DC O
ASG class
geIntASG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SP AC_NSG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
geIntASG_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SP AC_NSG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
dataNs Vstring255 EX O
geIntASG_3
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SG AC_SG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
geFloatASG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag FloatAnalogueValue SP AC_NSG_M
f FLOAT32 GC_1
7.3.7.3.6 MICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 1
Reference documentation: MICS For F650 relay V1_4 firm7_52.
This model implementation conformance statement is applicable for F650 Bay Controller, with firmware 7.52.
This MICS document specifies the modeling extensions compared to IEC 61850 edition 1. For the exact details on
the standardized model please compare the ICD substation configuration file: “<F650_6SG_v752_Ed1.icd>”, version
<1.0>.
This document describes the:
• Logical Nodes List
• Logical Nodes and Extensions
• Enum types implementation
LPHD class
Attribute Attr. Explanation M/O Notes
Name Type
LPHD Physical device information M
Data
Common Logical Node Information
PhyNam geDPL Physical device name plate M
PhyHealth geHealthINS Physical device health M
Proxy geSPS Indicates if this LN is a proxy M
LLN0 class
Attribute Attr. Explanation M/O Notes
Name Type
LLN0 Logical node zero
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL_1 Name plate M
Loc geSPS Local control behavior O
OpTmh geINS Operation time O
GoCB (ACSI class GOOSE control block)
GoCB GoCB
LLN0 class
Attribute Attr. Explanation M/O Notes
Name Type
LLN0 Logical node zero
Data
Common Logical Node Information
GoCB class
Attribute Name Attribute Type FC Notes
GoEna BOOLEAN GO Enable (TRUE), disable (FALSE)
GoID VISIBLE STRINGS GO
DatSet Object Reference GO
ConfRev INT32U GO
NdsCom BOOLEAN GO
DstAddress PHYCOMADDR GO
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS_1 Block O
Settings
PIOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
EventEna geSPG_2 Snapshot events enabled O
2.2.1.2 geNdPIOC_2
This logical node class is used for neutral instantaneous overcurrent and has 3 instances inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geNeutACD Start O IOC PKP
Op geNeutACT Operate M IOC OP
Blk geSPS_1 Block O
Settings
PIOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
EventEna geSPG_2 Snapshot events enabled O
2.2.1.3 geGndPIOC_2
This logical node class is used for ground instantaneous overcurrent (3 instances) and sensitive ground
instantaneous overcurrent (3 instances). There are 6 instances this logical node inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS_1 Block O
Settings
PIOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
EventEna geSPG_2 Snapshot events enabled O
2.2.1.4 IsoGndPIOC_2
This logical node class is used for Isolated sensitive ground instantaneous overcurrent. There are 3 instances this
logical node inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS_1 Block O
Settings
PIOCEna geSPG_2 Function O
VhStr geIntASG_2 Vh level O
VIStr geIntASG_2 VI level O
IhStr geFloatASG_1_2 Ih level O
IIStr geFloatASG_1_2 II level O
OpDlTmms geING_8_2 Trip delay O
RsDlTmms geING_8_2 Reset delay O
EventEna geSPG_2 Snapshot events enabled O
2.2.1.5 geBknCndPIOC_2
This logical node class is used for broken conductor instantaneous overcurrent. There are 3 instances this logical
node inside the device.
PIOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Instantaneous overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O IOC PKP
Op gePhsACT Operate M IOC OP
Blk geSPS Block O
Settings
PIOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
OpDlTmms geING_8_2 Trip delay O
BlkCurrent geFloatASG_1_2 Operation Threshold O
EventEna geSPG_2 Snapshot events enabled O
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS_1 Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
TmACrv geCURVE_3 Curve O
StrVal geFloatASG_2 Pickup level O
VolRst geSPG_2 Voltage Restraint O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
EventEna geSPG_2 Snapshot events enabled O
2.2.2.2 geNdPTOC_2
This logical node class is used for neutral time overcurrent and has 3 instances inside the device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geNeutACD Start O TOC PKP
Op geNeutACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
TmACrv geCURVE_3 Curve O
StrVal geFloatASG_2 Pickup level O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
EventEna geSPG_2 Snapshot events enabled O
2.2.2.3 geGndPTOC_2
This logical node class is used for ground time overcurrent (3 instances) and for sensitive ground time overcurrent (3
instances). There are 6 instances inside of this logical node inside the device
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PTOC Time overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
InMagTyp geING_0_2 Input O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
EventEna geSPG_2 Snapshot events enabled O
2.2.2.4 geNgSeqPTOC_2
This logical node class is used for negative sequence time overcurrent function and has 3 instances inside the
device.
PTOC class
Attribute Attr. Explanation M/O Notes
Name Type
PIOC Time overcurrent
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start O TOC PKP
Op gePhsACT Operate M TOC OP
Blk geSPS Block O TOC BLK
Settings
PTOCEna geSPG_2 Function O
StrVal geFloatASG_2 Pickup level O
TmACrv geCURVE_3 Curve O
TmMult geFloatASG_2 TD Multiplier O
RsMod geING_0_2 Reset O
EventEna geSPG_2 Snapshot events enabled O
PTOF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTOF Overfrequency
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name Plate M
Status information
Str geGeneralACD Start M TOF PKP
Op geGeneralACT Operate M TOF OP
Blk geSPS_1 Block O TOF BLK
Settings
PTOFEna geSPG_2 Function E
StrVal geFloatASG_2 Start value (frequency) O
BlkVal geIntASG_3 Voltage block value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
FreqSource geSPG_2 Frequency source E
EventEna geSPG_2 Snapshot events enabled E
PTOF class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTUF Underfrequency
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name Plate M
Status information
Str geGeneralACD Start M TU PKP
Op geGeneralACT Operate M TUF OP
Blk geSPS_1 Block O TUF BLK
Settings
PTUFEna geSPG_2 Function E
StrVal geFloatASG_2 Start value (frequency) O
BlkVal geIntASG_3 Voltage block value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
FreqSource geSPG_2 Frequency source E
EventEna geSPG_2 Snapshot events enabled E
2.2.5 PTUV
2.2.5.1 gePhsPTUV_2
This logical node class is used for phase undervoltage and has 3 instances inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TUV PKP
Op geGeneralACT Operate M TUV OP
Blk geSPS_1 Block O TUV BLK
StrPhGn gePhsACD_1 Pickup Phase-Ground O
OpPhGn gePhsACT_1 Operate Phase-Ground O
StrPhPh gePhsACD_1 Pickup Phase-Phase O
OpPhPh gePhsACT_1 Operate Phase-Phase O
Settings
PTUVEna geSPG_2 Function O
InMod geING_0_2 Mode O
TmVCrv geCURVE_4 Operating Curve Type O
StrVal geIntASG_3 Start value O
TmMult geFloatASG_2 Time dial multiplier O
DeaLinVal geIntASG_3 Minimum Voltage O
PhLogic geING_0_2 Logic O
BkrMon geSPG_2 Supervised by 52 O
EventEna geSPG_2 Snapshot events enabled O
2.2.5.2 geAuxPTUV_2
This logical node class is used for auxiliary undervoltage and has 3 instances inside the device.
PTUV class
Attribute Attr. Explanation M/O Notes
Name Type
PTUV Undervoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TUV PKP
Op geGeneralACT Operate M TUV OP
Blk geSPS_1 Block O TUV BLK
Settings
PTUVEna geSPG_2 Function O
TmVCrv geCURVE_4 Operating Curve Type O
StrVal geIntASG_3 Start value O
TmMult geFloatASG_2 Time dial multiplier O
EventEna geSPG_2 Snapshot events enabled O
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M TOV PKP
Op gePhsACT Operate M TOV OP
Blk geSPS Block O TOV BLK
Settings
PTOVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
PhLogic geING_0_2 Logic O
EventEna geSPG_2 Snapshot events enabled O
2.2.6.2 geAuxPTOV_2
This logical node class is used for auxiliary overvoltage and has 3 instances inside the device
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TOV PKP
Op geGeneralACT Operate M TOV OP
Blk geSPS_1 Block O TOV BLK
Settings
PTOVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
EventEna geSPG_2 Snapshot events enabled O
2.2.6.3 geNeutPTOV_2
This logical node class is used for neutral overvoltage and has 6 instances inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TOV PKP
Op geGeneralACT Operate M TOV OP
Blk geSPS_1 Block O TOV BLK
Settings
PTOVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
EventEna geSPG_2 Snapshot events enabled O
2.2.6.4 geNgSeqPTOV_2
This logical node class is used for negative sequence overvoltage and has 3 instances inside the device.
PTOV class
Attribute Attr. Explanation M/O Notes
Name Type
PTOV Overvoltage
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str geGeneralACD Start M TOV PKP
Op geGeneralACT Operate M TOV OP
Blk geSPS Block O TOV BLK
Settings
PTOVEna geSPG_2 Function O
StrVal geIntASG_3 Start value O
OpDlTmms geING_8_2 Operate delay time O
RsDlTmms geING_8_2 Reset delay time O
EventEna geSPG_2 Snapshot events enabled O
2.2.7.2 geDirPDOP_2
This logical node class shall be used to model the directional overpower function and has 3 instances inside the
device.
PDOP class
Attribute Attr. Explanation M/O Notes
Name Type
PDOP Overpower
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS_1 Block O
S1Str gePhsACD_2 Start O Stage 1 PKP
S1Op gePhsACT_1 Operate O Stage 1 OP
S2Str gePhsACD_2 Start O Stage 2 PKP
S2Op gePhsACT_1 Operate O Stage 2 OP
Settings
PDOPEna geSPG_2 Function O
BlkClsTms geING_0_2 Blk time after close O
S1DirPwAng geFloatASG_1_2 Dir Power Angle 1 O
S1StrVal geFloatASG_1_2 Stage 1 Tap O
S1OpDlTmms geING_0_2 Stage 1 Time O
S2DirPwAng geFloatASG_1_2 Dir Power Angle 2 O
2.2.7.3 geWattPDOP_2
This logical node class shall be used to model the wattmeter ground overpower function and has 6 instances inside
the device.
PDOP class
Attribute Attr. Explanation M/O Notes
Name Type
PDOP Overpower
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS_1 Block O
SupStr gePhsACD_2 Start O
Settings
PDOPEna geSPG_2 Function O
OVStrVal geFloatASG_1_2 Voltage Pickup Level O
InMagTyp geING_0_2 Current Selection O
OCStrVal geFloatASG_1_2 OC Pickup level O
OCStrDlTms geING_0_2 OC Pickup Delay O
PWStrVal geFloatASG_1_2 Power Pickup O
ChrAng geFloatASG_2 MTA O
PWStrDlTms geING_0_2 Power Pickup Delay O
Curve geING_0_2 Curve O
MltTmms geING_0_2 Multiplier O
EventEna geSPG_2 Snapshot events enabled O
PDIS class
Attribute Attr. Explanation M/O Notes
Name Type
PDIS Distance
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Str gePhsACD Start M
Op gePhsACT Operate M
Blk geSPS_1 Block O
Settings
PDISEna geSPG_2 Function O
MinVoltage geFloatASG_1_2 Freq Rate Trend O
RisLod geFloatASG_2 Freq Rate Pickup O
AngLod geFloatASG_2 Freq Rate Min Volt O
OpDlTmms geING_8_2 Operation Delay O
RsDlTmms geING_8_2 Reset Delay O
EventEna geSPG_2 Snapshot events O
PTTR class
Attribute Name Attribute type Explanation M/O/C/E Notes
PTTR Thermal overload
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name Plate M
Status information
Str geGeneralACD Start M
Op gePhsACT Operate M
Blk geSPS_1 Block O
AlmThm geGeneralACT Thermal alarm O
AlmThmPhA geSPS_1 Thermal alarm phase A E
AlmThmPhB geSPS_1 Thermal alarm phase B E
AlmThmPhC geSPS_1 Thermal alarm phase C E
Settings
PTTREna geSPG_2 Function E
ConsTmHeat geFloatASG_1_2 Heat time constant E
ConsTmCool geFloatASG_1_2 Cool time constant E
StrVal geFloatASG_2 Pickup level O
AlmVal geFloatASG_2 Alarm level O
EventEna geSPG_2 Snapshot events enabled E
PTRC class
Attribute Attr. Explanation M/O Notes
Name Type
PTRC Trip bus
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Op geGeneralACT Operate M
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Dir gePhsACD Direction M
Op gePhsACT Operate O
Blk geSPS_1 Block O
BlkIn geGeneralACT_1 Block Input O
Settings
RDIREna geSPG_2 Function O
ChrAng geFloatASG_2 Characteristic angle O
PolOpMod geING_0_2 Direction O
BlkMod geING_0_2 Block Logic O
BlkValV geIntASG_3 Minimum operating current O
VMemTms geFloatASG_1_2 Voltage Memory Time O
EventEna geSPG_2 Snapshot events enabled O
2.3.1.2 geNdRDIR_2
This logical node class is used for neutral directional elements and has 3 instances inside the device.
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Dir geNeutACD Direction M
Op geNeutACT Operate O
Blk geSPS_1 Block O
BlkIn geNeutACT_1 Block Input O
Settings
RDIREna geSPG_2 Function O
ChrAng geFloatASG_2 Characteristic angle O
PolOpMod geING_0_2 Direction O
BlkMod geING_0_2 Block Logic O
BlkValV geIntASG_3 Minimum operating current O
PolQty geING_9 Polarizing quantity O
SnpshtEvEna geSPG_2 Snapshot events enabled O
2.3.1.3 geGndRDIR_2
This logical node class is used for ground directional elements (3 instances) and for sensitive ground directional (3
instances).
RDIR class
Attribute Attr. Explanation M/O Notes
Name Type
RDIR Directional Element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Dir geNeutACD Direction M
Op geNeutACT Operate O
Blk geSPS_1 Block O
BlkIn geNeutACT_1 Block Input O
Settings
RDIREna geSPG_2 Function O
ChrAng geFloatASG_2 Characteristic angle O
PolOpMod geING_0_2 Direction O
BlkMod geING_0_2 Block Logic O
BlkValV geIntASG_3 Minimum operating current O
PolQty geING_9 Polarizing quantity O
EventEna geSPG_2 Snapshot events enabled O
RREC class
Attribute Attr. Explanation M/O Notes
Name Type
RREC Autoreclosing Element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
Op geGeneralACT M
OpCls geGeneralACT Direction M
AutoRecSt geAutoRecStENS Operate M
AutoRecLo geINS_1 Block O
AutoRecBlk geINS_1 Block Input O
Settings
RRECEna geSPG Function O
MaxNumShot geING_0 Max. Number Shots O
Rec1Tmms1 geING_8 Dead Time 1 O
Rec1Tmms2 geING_8 Dead Time 2 O
Rec1Tmms3 geING_8 Dead Time 3 O
Rec1Tmms4 geING_8 Dead Time 4 O
RclTmms geING_8 Reclaim time
CondEna geSPG Cond. Permission
HoldTmms geFloatASG_1 Hold Time
RsTmms geFloatASG_1 Reset Time
RREC class
Attribute Attr. Explanation M/O Notes
Name Type
RBRF Breaker failure element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
OpEx geGeneralACT Direction M
RFLO class
Attribute Attr. Explanation M/O Notes
Name Type
RFLO Fault locator element
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
FltRprtTrg geSPS_1 Fault Report Trigger O
ClrFltRprts geSPS_1 Clear fault reports O
FltZ geFloatCMV Fault impedance M
FltDiskm geFloatMV_3 Fault distance in km O
RPriFlt geFloatMV_2 Primary Fault Resistance O
XPriFlt geFloatMV_2 Primary Fault Reactance O
RSeFlt geFloatMV_2 Secondary Fault Resistance O
XSeFlt geFloatMV_2 Secondary Fault Reactance O
RFault geFloatMV_2 Fault Resistance O
FltTyp geINS_1 Fault type O
FltRprtNum geINS_1 Fault report number O
PreFlaMod geFloatMV_2 Prefault Ia module O
PreFlaAng geFloatMV_2 Prefault Ia angle O
PreFlbMod geFloatMV_2 O
PreFlbAng geFloatMV_2 O
PreFlcMod geFloatMV_2 O
PreFlcAng geFloatMV_2 O
PreFlgMod geFloatMV_2 O
PreFlgAng geFloatMV_2 O
PreFlsgMod geFloatMV_2 O
PreFlsgAng geFloatMV_2 O
PreFVabMod geFloatMV_2 O
PreFVabAng geFloatMV_2 O
PreFVbcMod geFloatMV_2 O
PreFVbcAng geFloatMV_2 O
PreFVcaMod geFloatMV_2 O
PreFVcaAng geFloatMV_2 O
PstFlaMod geFloatMV_2 Postfault Ia module O
PstFlaAng geFloatMV_2 Postfault Ia angle O
PstFlbMod geFloatMV_2 O
PstFlbAng geFloatMV_2 O
PstFlcMod geFloatMV_2 O
PstFlcAng geFloatMV_2 O
PstFlgMod geFloatMV_2 O
PstFlgAng geFloatMV_2 O
PstFlsgMod geFloatMV_2 O
PstFltIsgAng geFloatMV_2 O
PstFVabMod geFloatMV_2 O
PstFVabAng geFloatMV_2 O
PstFVbcMod geFloatMV_2 O
PstFVbcAng geFloatMV_2 O
PstFVcaMod geFloatMV_2 O
PstFVcaAng geFloatMV_2 O
Settings
RSYN class
Attribute Attr. Explanation M/O Notes
Name Type
RSYN Synchronism-check
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status Information
SynBlkIn geSPS_1 Block signal O
SynOp geSPS_1 Closing permission signal O
Rel geSPS Release M
SynCondOp geSPS_1 Closing perm. according to logic O
DLDBOp geSPS_1 Closing perm. in DLDB condition O
DLLBOp geSPS_1 Closing perm. in DLLB condition O
LLDBOp geSPS_1 Closing perm. in LLDB condition O
HzInd geSPS Frequency difference indicator O
BusHzHiLinHz geSPS_1 Busbar frequency > line frequency O
BusHzLoLinHz geSPS_1 Busbar frequency < line frequency O
Measured values
DifVClc geFloatMV Calculated difference in voltage O
DifHzClc geFloatMV Calculated difference in frequency O
Settings
RSYNEna geSPG Function O
DeaBusVal geFloatASG Dead bus value O
LivBusVal geFloatASG Live bus value O
DeaLinVal geFloatASG Dead line value O
LivLinVal geFloatASG Live line value O
DifV geFloatASG Difference voltage O
DifAng geFloatASG Difference angle O
DifHz geIntASG Difference frequency O
TotTmms geING_8 Total time of synch. process O
DLDBEna geSPG Dead line - dead bus permission O
LLDBEna geSPG Live line - dead bus permission O
DLLBEna geSPG Dead line - live bus permission O
EventEna geSPG Snapshot events enabled O
RDRE class
Attribute Name Attribute type Explanation M/O/C/E Notes
RDRE Disturbance recorder
Data
Common Logical Node Information
Mod geModINC Mode M Status-only
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name Plate M
Status information
RcdMade geSPS Recording made M
FltNum geINS Fault number M
CycRcd geINS_1 Cycles per record E
RcdNum geINS_1 Available records E
Settings
RDREEna geSPG Oscillography function enable E
TrgPos geINS_0 Trigger position E
SmpCyc geINS_10 Samples per cycle E
MaxNumRcd geINS_8 Maximum number of records O
RcdMod geINS_11 Recorder operation mode O
EventEna geSPG Snapshot events enabled E
RBDR class
Attribute Name Attribute type Explanation M/O/C/E Notes
RBDR Disturbance recorder channel binary
Data
Common Logical Node Information
Mod geModINC Mode M Status-only
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name Plate M
Status information
ChTrg geSPS Channel triggered M
FltNum geINS Fault Number M
DigCh01 geSPS_01 O
… … … …
DigCh16 geSPS_01 O
CSWI class
Attribute Name Attribute Type Explanation M/O/E Notes
CSWI Switch controller
Data
Common Logical Node Information
Mod geModINC Mode M Status-only
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Controls
Loc geSPS Local operation O Local/Remote
Pos geDPC_1 Switch position M Switch open, close, undefined
CILO class
Attribute Attr. Explanation M/O Notes
Name Type
CILO Switch controller
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status information
EnaOpn geSPS Enable Open M
EnaCls geSPS Enable Close
2.5.1.2 geVirtualGGIO
This logical node class is used is used to map the latched and self reset virtual Inputs.
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModINC Mode M Status-only
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Controls
DPCSO01 geSPC Virtual input 1 O
DPCSO01 geSPC Virtual input 2 O
.. .. .. ..
DPCSO64 geSPC Virtual input 32 O
2.5.1.3 geEventsGGIO
This logical node class is used to map data from the list of any all internal digital states (PLC control events).
GGIO class
Attribute Attribute Explanation M/O/E Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModINC Mode M Status-only
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status information
Ind1 geSPS Control Event 1 O
Ind2 SPS Control Event 2 O Control Event 2
......... .......... ............... .......... ..............
Ind192 SPS Control Event 32 O Control Event 32
2.5.1.4 geRemoteInputsGGIO
This logical node class is used to map data from incoming GOOSE messages.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status information
Ind1 geSPS Remote digital input 1 O
Ind2 geSPS Remote digital input 2 O
.. .. .. ..
Ind64 geSPS Remote digital input 32 O
AnIn1 geFloatMV Remote float input 1 O
AnIn2 geFloatMV Remote float input 2 O
.. .. .. ..
AnIn8 geFloatMV Remote float input 8 O
AnIn9 geIntMV_1 Remote integer input 1 O
AnIn10 geIntMV_1 Remote integer input 2 O
.. .. .. ..
AnIn16 geIntMV_1 Remote integer input 8 O
Settings
OscTmms geING_0 Oscillation time remote inputs O
NumChgs geING_0 Number of transient changes O
2.5.1.5 geRemoteOutputsGGIO
This logical node class is used to map PLC digital states for outgoing GOOSE messages.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status information
Ind1 geSPS Remote digital output 1 O
Ind2 geSPS Remote digital output 2 O
.. .. .. ..
Ind32 SgePS Remote digital output 32 O
2.5.1.6 geDigitalCountersGGIO
This logical node is used for modeling the eight digital counters of F650 relay.
GGIO class
Attribute Attr. Explanation M/O Notes
Name Type
GGIO Generic process I/O
Data
Common Logical Node Information
Mod geModENC Mode M
Beh geBehENS Behavior M
Health geHealthENS Health M
NamPlt geLPL Name plate M
Status information
Cnt1 geBCR_2 Digital counter 1 O
.. .. .. ..
Cnt8 geBCR_2 Digital counter 8 O
CntBlk1 geSPS_1 Digital counter 1 block O
.. .. ..
CntBlk8 geSPS_1 Digital counter 8 block O
CntHi1 geSPS_1 Digital counter 1 high O
.. .. ..
CntHi8 geSPS_1 Digital counter 8 high O
CntEq1 geSPS_1 Digital counter 1 equal O
.. .. ..
CntEq8 geSPS_1 Digital counter 8 equal O
CntLo1 geSPS_1 Digital counter 1 low O
.. .. ..
CntLo8 geSPS_1 Digital counter 8 low O
CntUp1 geSPS_1 Digital counter 1 up O
.. .. ..
CntUp8 geSPS_1 Digital counter 8 up O
CntDwn1 geSPS_1 Digital counter 1 down O
.. .. ..
CntDwn8 geSPS_1 Digital counter 8 down O
CntSetPre1 geSPS_1 Digital counter 1 set preset O
.. .. ..
CntSetPre8 geSPS_1 Digital counter 8 set preset O
CntRst1 geSPS_1 Digital counter 1 reset O
.. .. ..
CntRst8 geSPS_1 Digital counter 8 reset O
CntFrzRst1 geSPS_1 Digital counter 1 FreezeReset O
.. .. ..
CntFrzRst8 geSPS_1 Digital counter 8 FreezeReset O
CntFrzCnt1 geSPS_1 Digital counter 1 FreezeCount O
.. .. ..
CntFrzCnt8 geSPS_1 Digital counter 8 FreezeCount O
MMXU class
Attribute Attr. Explanation M/O Notes
Name Type
MMXU Measurement
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Measured values
TotW geFloatMV Total active power (P) O
TotVAr geFloatMV Total reactive power (Q) O
TotVA geFloatMV Total apparent power (S) O
TotPF geFloatMV Average power factor (PF) O
Hz geFloatMV Line Frequency O
PPV geFloatDEL Phase to phase voltages (VL1L2,...) O
PhV geFloatPhsWYE Phase to ground voltages (VL1ER, ...) O
A geFloatWYE Phase currents (IL1, ...) O
AuxV geFloatCMV_1 Auxiliary Phase Voltage O
BusHz geFloatMV_1
MSQI class
Attribute Attr. Explanation M/O Notes
Name Type
MSQI Measurement
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Measured values
SeqA geFloatSEQ O
SeqV geFloatSEQ O
MMTR class
Attribute Attr. Explanation M/O Notes
Name Type
MMTR Measurement
Data
Common Logical Node Information
Mod geModINC Mode M
XCBR class
Attribute Attr. Explanation M/O Notes
Name Type
XCBR Circuit breaker
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status information
Loc geSPS Local operation M Local / Remote
OpCnt geINS Operation counter M Breaker openings
SumSwARs O
CBOpCap geCBOpCapENS Cicruit breaker operating O
capability
Controls
Pos geDPC_1 Switch position M Breaker open, close
BlkOpn geSPC_1 Block opening M Virtual output
BlkClr geSPC_1 Block closing M Virtual output
Settings
ThAlSwA geFloatASG_1 Maximum KI2t O
SumSwATmms geFloatASG_1 KI2t Integ. Time O
ExNumTr geIntASG_1 Maximum Openings O
ExNumTr1hr geIntASG_1 Max.Openings 1 hour O
XCBR class
Attribute Attr. Explanation M/O Notes
Name Type
XSWI Circuit switch
Data
Common Logical Node Information
Mod geModINC Mode M
Beh geBehINS Behavior M
Health geHealthINS Health M
NamPlt geLPL Name plate M
Status information
Loc geSPS Local operation M Local / Remote
EEHealth geEEHealthENS Ext. equipment health O
OpCnt geINS Operation counter M Breaker openings
Controls
Pos geDPC_2 Switch position M Breaker open, close
BlkOpn geSPC_1 Block opening M Virtual output
BlkClr geSPC_1 Block closing M Virtual output
SwTyp geSwTypENS Switch type M
SwOpCap geSwOpCapENS Switch operating capability
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
q BVstring13 ST qchg M
t Utctime ST M
CONFIGURATION, DESCRIPTION AND EXTENSION
d Vstring255 DC O
geEEHealthINS (EEHealth)
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Status
stVal INT32 ST dchg Ok,Warning,Alarm M
q BVstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
geCBOpCapINS (CBOpCap)
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Status
stVal Enumerated ST dchg None,Open,Close-Open,… M
q BVstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
geSwOpCapINS (SwOpCap)
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Status
stVal Enumerated ST dchg None,Open,Close,… M
q BVstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
geSwTypINS (SwTyp)
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Status
stVal Enumerated ST dchg Load Break, Disconnector,… M
q BVstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
d Vstring255 DC O
geNeutACD_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
general Boolean ST Dchg M
dirGeneral Enumerated (Byte) ST Dchg unknown | forward | backward | both M
q Bvstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geGeneralACD
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
general Boolean ST Dchg M
dirGeneral Enumerated (Byte) ST Dchg unknown | forward | backward | both M
q Bvstring13 ST qchg M
t Utctime ST M
Configuration, Description And Extension
d Vstring255 DC O
Measured Attributes
instMag FloatAnalogueValue MX ------ O
f FLOAT32 GC_1
mag FloatAnalogueValue MX dchg M
f FLOAT32 GC_1
range ENUMERATED(Byte) MX dchg O
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
db INT32U CF O
zeroDb INT32U CF O
rangeC RangeConfig CF O
hhLim FloatAnalogueValue
f
FLOAT32 GC_1
hlim
f FloatAnalogueValue
lLim FLOAT32 GC_1
f FloatAnalogueValue
llLim FLOAT32 GC_1
f
FloatAnalogueValue
min
f FLOAT32 GC_1
max FloatAnalogueValue
f FLOAT32 GC_1
limDb FloatAnalogueValue
FLOAT32 GC_1
INT32U
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geFloatMV_2
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
mag FloatAnalogueValue MX dchg M
f FLOAT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
geFloatMV_3
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
mag FloatAnalogueValue MX dchg M
f FLOAT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
d Vstring255 DC O
geIntMV
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
instMag IntAnalogueValue MX ------ O
i INT32 GC_1
mag IntAnalogueValue MX dchg M
i INT32 GC_1
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
db INT32U CF O
d Vstring255 DC O
geIntMV_1
Attribute Name Attribute Type FC TrgOp Value/Value Range M/O/C
DataAttribute
Measured Attributes
instMag IntAnalogueValue MX ------ O
i INT32 GC_1
mag IntAnalogueValue MX dchg M
i INT32 GC_1
range ENUMERATED(Byte) MX dchg O
q BVstring13 MX qchg M
t Utctime MX M
Configuration, Description And Extension
units Unit CF O
SIUnit ENUMERATED(Byte) M
Multiplier ENUMERATED(Byte) O
db INT32U CF O
zeroDb INT32U CF O
rangeC RangeConfig CF O
hhLim IntAnalogueValue
i
INT32U GC_1
hlim
i IntAnalogueValue
lLim UINT32 GC_1
i IntAnalogueValue
llLim INT32U GC_1
i
IntAnalogueValue
min
i INT32U GC_1
max IntAnalogueValue
i INT32U GC_1
limDb IntAnalogueValue
INT32U GC_1
INT32U
d Vstring255 DC O
dataNs Vstring255 EX AC_DLN_M
3.2.3 Phase to ground related measured values of a three phase system (WYE)
WYE class
geFloatPhsWYE
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsA CMV_0 GC_1
phsB CMV_0 GC_1
phsC CMV_0 GC_1
neut CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
geFloatWYE
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsA CMV_0 GC_1
phsB CMV_0 GC_1
phsC CMV_0 GC_1
neut CMV_0 GC_1
net CMV_0 GC_1
res CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
3.2.4 Phase to phase related measured values of a three phase system (DEL)
DEL class (Phase to phase related measured values of a three phase system)
geFloatDEL
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
phsAB CMV_0 GC_1
phsBC CMV_0 GC_1
phsCA CMV_0 GC_1
Configuration, Description And Extension
d Vstring255 DC O
SPC class
geSPC
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal Boolean ST FALSE | TRUE AC_ST
q Quality ST AC_ST
t TimeStamp ST AC_ST
Oper ctlVal Boolean CO AC_CO_M
origin Originator CO AC_CO_M
orCat ENUMERATED M
orIdent OCTECT64 M
ctlNum INT8U CO M
T Btime6 CO M
Test Boolean CO M
Check ENUMERATED CO M
Configuration, Description And Extension
ctlModel ENUMERATED CF ctlModel M
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
cdcNs Vstring255 EX
cdcName Vstring255 EX
geSPC_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal Boolean ST FALSE | TRUE AC_ST
Q Quality ST AC_ST
t TimeStamp ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF ctlModel_1 M
d Vstring255 DC O
t Utctime ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF M
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
cdcNs Vstring255 EX
cdcName Vstring255 EX
geDPC_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
Oper ctlVal Boolean CO AC_CO_M
origin Originator CO,ST AC_CO_M
orCat ENUMERATED M
orIdent OCTECT64 M
ctlNum INT8U CO,ST M
T Btime6 CO M
Test Boolean CO M
Check ENUMERATED CO M
Cancel
SBO
SBOw
stVal CODE ENUM ST dchg intermediate-state | off | on | bad- M
state
q BVstring13 ST qchg AC_ST
t Utctime ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF M
sboTimeout INT32U CF AC_CO_O
sboClass ENUMERATED CF AC_CO_O
operTimeout INT32U CF AC_CO_O
d Vstring255 DC O
cdcNs Vstring255 EX
cdcName Vstring255 EX
geDPC_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Control And Status
stVal CODE ENUM ST dchg intermediate-state | off | on | bad- M
state
q BVstring13 ST qchg AC_ST
t Utctime ST AC_ST
Configuration, Description And Extension
ctlModel ENUMERATED CF M
d Vstring255 DC O
SPG class
geSPG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SP AC_NSG_M
configuration, description and extension
d Vstring255 DC O
dataNs Vstring255 EX O
geSPG_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SG AC_SG_M
Configuration, Description And Extension
d Vstring255 DC O
dataNs Vstring255 EX O
ING class
geING_0
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SP AC_NSG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
dataNs Vstring255 EX O
geING_0_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Boolean SG AC_SG_M
Configuration, Description And Extension
minVal INT32 CF O
maxVal INT32 CF O
stepSize INT32 CF O
d Vstring255 DC O
dataNs Vstring255 EX O
geING_8
ENG class
geENG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Enumerated SP PolQty AC_NSG_M
Configuration, Description And Extension
d Vstring255 DC O
geENG_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setVal Enumerated SG PolQty AC_SG_M
Configuration, Description And Extension
d Vstring255 DC O
ORG class
geORG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setSrcRef ObjectReference SP Object reference M
Configuration, Description And Extension
d Vstring255 DC O
ASG class
geIntASG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SP AC_NSG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
geIntASG_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SP AC_NSG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
dataNs Vstring255 EX O
geIntASG_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SG AC_NSG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
dataNs Vstring255 EX O
geIntASG_3
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag IntAnalogueValue SG AC_SG_M
i INT32 GC_1
Configuration, Description And Extension
units Unit CF
minVal IntAnalogueValue CF O
i INT32 GC_1
maxVal IntAnalogueValue CF O
i INT32 GC_1
stepSize IntAnalogueValue CF O
i INT32 GC_1
d Vstring255 DC O
geFloatASG
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag FloatAnalogueValue SP AC_NSG_M
f FLOAT32 GC_1
Configuration, Description And Extension
Units Unit CF
minVal FloatAnalogueValue CF O
f FLOAT32 GC_1
maxVal FloatAnalogueValue CF O
f FLOAT32 GC_1
stepSize FloatAnalogueValue CF O
f FLOAT32 GC_1
d Vstring255 DC O
geFloatASG_1
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag FloatAnalogueValue SP AC_NSG_M
f FLOAT32 GC_1
Configuration, Description And Extension
Units Unit CF
minVal FloatAnalogueValue CF O
f FLOAT32 GC_1
maxVal FloatAnalogueValue CF O
f FLOAT32 GC_1
stepSize FloatAnalogueValue CF O
f FLOAT32 GC_1
d Vstring255 DC O
dataNs Vstring255 EX O
geFloatASG_1_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag FloatAnalogueValue SG AC_NSG_M
f FLOAT32 GC_1
Configuration, Description And Extension
Units Unit CF
minVal FloatAnalogueValue CF O
f FLOAT32 GC_1
maxVal FloatAnalogueValue CF O
f FLOAT32 GC_1
stepSize FloatAnalogueValue CF O
f FLOAT32 GC_1
d Vstring255 DC O
dataNs Vstring255 EX O
geFloatASG_2
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setMag FloatAnalogueValue SG AC_SG_M
f FLOAT32 GC_1
Configuration, Description And Extension
Units Unit CF
minVal FloatAnalogueValue CF O
f FLOAT32 GC_1
maxVal FloatAnalogueValue CF O
f FLOAT32 GC_1
stepSize FloatAnalogueValue CF O
f FLOAT32 GC_1
d Vstring255 DC O
geCURVE_3
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setCharact ENUMERATED SG O
d Vstring255 DC O
geCURVE_4
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setCharact ENUMERATED SG O
d Vstring255 DC O
4. Enum Types
4.2 New Enum Types
4.2.1 setCharact_2
4.2.2 SamplesCycle
2 16 samples/cycle
3 8 samples/cycle
4 4 samples/cycle
7.3.7.3.7 TICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "B", "C", "D", "E" and IEC 61850 Edition 1
Reference documentation: TICS for 650 family of relays v1_7 firm3_60.
This document describes the:
• Introduction
• TICS Template
1 Introduction
This document provides a template for the tissues conformance statement (TICS). According to the UCA QAP the TICS is
required to perform a conformance test and is referenced on the final certificate.
In this TICS template only tissues with a “green” status are considered since they become mandatory and thus must be
included in the UCA Device conformance test procedures.
“Green” Tissues listed in this document represent the current status of all Tissues for a date of the document creation.
As for some of the remaining tissues, they are not yet included in the test procedures, either because they are just a
recommendation or optional within the IEC 61850 documents, or because their respective proposals are not defined in
such detail to be implemented or tested, or because they are simply not applicable, just editorial, with no change for
implementation and testing.
The supported (“Sup”) column indicates:
• Y: yes, the tissue is implemented in the device.
• N: no, the tissue is not implemented in the device.
• N/A: not applicable, the tissue is not applicable for the device.
2 TICS Template
130 N/A
157 N/A
169 N/A
170 N/A
176 N/A
186 Y Technically it would be possible to include Control Block’s attributes as
Data Set members, however Data Sets in this device are fixed and it is
not possible to modify them.
197 N/A
201 N/A
211 N/A
245 N/A
IEC 61850 Part 7-2
29 N/A
30 N/A
31 N/A
32 N/A
33 N/A
34 N/A
35 Y
36 N/A
37 N/A
38 N/A
39 N/A
40 N/A
41 Y
42 N/A
43 N/A
44 N/A
45 N/A
47 N/A
48 N/A
50 N/A
51 N/A
52 N/A
53 N
137 N/A
142 N
IEC 61850 Part 7-3
28 N/A No CDC APC present in Data Model.
54 N/A
55 N/A
56 N/A
57 N/A
58 N/A
59 N/A
60 N/A
61 N/A
62 N/A
63 N/A
64 N/A
65 N/A
7.3.7.3.8 TICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 2
1 Introduction
This document provides a template for the tissues conformance statement (TICS). According to the UCA QAP the
TICS is required to perform a conformance test and is referenced on the final certificate.
In this TICS template only tissues with a "green" status are considered since they become mandatory and thus must
be included in the UCA Device conformance test procedures.
"Green" Tissues listed in this document represent the current status of all Tissues for a date of the document
creation. As for some of the remaining tissues, they are not yet included in the test procedures, either because they
are just a recommendation or optional within the IEC 61850 documents, or because their respective proposals are
not defined in such detail to be implemented or tested, or because they are simply not applicable, just editorial, with
no change for implementation and testing.
The supported ("Sup") column indicates:
• Y: yes, the tissue is implemented in the device.
• N: no, the tissue is not implemented in the device.
• N/A: not applicable, the tissue is not applicable for the device.
2 TICS Template
7.3.7.3.9 TICS for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 1
During the October 2006 meeting IEC TC57 working group 10 decided that:
• green Tissues with the category "IntOp" are mandatory for IEC 61850 edition 1
• Tissues with the category "Ed.2" Tissues should not be implemented.
The table below gives an overview of the implemented IntOp Tissues.
7.3.7.3.10 PIXIT for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "B", "C", "D", "E" and IEC 61850 Edition 1
Reference documentation: PIXIT for 650 family of relays v1_5 firm3_60.
This document describes the:
• PIXIT for Association Model
• PIXIT for Server model
• PIXIT for Dataset model
• PIXIT for Reporting model
• PIXIT for Generic substation events model
• PIXIT for Control model
• PIXIT for Time and time synchronisation model
• PIXIT for File transfer model
This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface
in 650 family of relays
Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10.
Contents of this document: Each chapter specifies the PIXIT for each applicable ACSI service model as structured in
IEC 61850-10.
Description Value/Clarification
Maximum number of clients that can set-up an 5
association simultaneously
Lost connection detection time range (default range of 20 seconds
TCP_KEEPALIVE is 1 – 20 seconds)
Is authentication supported N
What association parameters are necessary for Only local selectors are checked:
successful association Y Transport selector (00 01)
Y Session selector (00 01)
Y Presentation selector (00 00 00 01)
N AP Title
N AE Qualifier
What is the maximum and minimum MMS PDU size Max MMS PDU size: 256000
There is no established minimum MMS PDU size, however
recommended MMS PDU size is at least 32000.
What is the typical startup time after a power supply 210 SECONDS
interrupt
Description Value/Clarification
Which analogue value (MX) quality bits are supported Validity:
(can be set by server) Y Good
N Invalid
N Reserved
N Questionable
N Overflow
N OutofRange
N BadReference
N Oscillatory
N Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
N Substituted
N Test
N OperatorBlocked
Which status value (ST) quality bits are supported (can be Validity:
set by server) Y Good
N Invalid
N Reserved
N Questionable
N BadReference
N Oscillatory
N Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
N Substituted
N Test
N OperatorBlocked
What is the maximum number of data values in one MMS PDU SIZE / 4
GetDataValues request
What is the maximum number of data values in one MMS PDU SIZE / 4
SetDataValues request
Additional Items:
Behavior of stepSize attribute checks When a client attempts to write value of setVal (CDC ING)
or setMag (CDC ASG), which is not a multiple of stepSize
attribute of the associated CF, then the device truncates
the value to the nearest stepSize not greater than the
value intended to be written.
Description Value/Clarification
What is the maximum number of data elements in one Data sets cannot be created via MMS services.
data set Data sets can be created via ICD/CID file and maximum
number of elements in one data set is 64. The exception
to that is the predefined data set “eveGGIO1$ST” which
contains 192 elements.
How many persistent data sets can be created by one or Data sets cannot be created via MMS services.
more clients Data sets can be created via ICD/CID file and maximum
number of all persistent data sets in F650 relay is 20.
How many non-persistent data sets can be created by 0
one or more clients
Description Value/Clarification
The supported trigger conditions are: Y integrity
Y data change
N quality change
N data update
Y general interrogation
The supported optional fields are: Y sequence-number
Y report-time-stamp
Y reason-for-inclusion
Y data-set-name
Y data-reference
Y buffer-overflow
Y entryID
Y conf-rev
Y segmentation
Can the server send segmented reports? Y
Mechanism on second internal data change notification Send report immediately
of the same analogue data value within buffer period
(Compare IEC 61850-7-2 $14.2.2.9)
Multi client URCB approach (compare IEC 61850-7-2 Option b) of IEC 61850-7-2 $14.2.1 is implemented
$14.2.1) which means that each client has it's own set of URCB's.
What is the format of EntryID Signed 32 bit integer.
What is the buffer size for each BRCB or how many Buffer size = 50000 bytes.
reports can be buffered
Pre-configured RCB attributes that cannot be changed DatSet attributes are always fixed
online when RptEna = FALSE
Additional Items:
BufTm=0 behavior When BufTm=0 multiple data can be placed in one
report if changes of these data have been detected at
the same time, it means during the same scan period.
The scan period for analogues is 500 milliseconds.
Integrity period Configurable >= 500 milliseconds
EntryID EntryID is incremented only if the EntryID bit is set in
OptFlds.
A valid EntryID that can be written by a client should be
equal or smaller than the EntryID in BRCB. This is
because the client should only request retransmission
of reports that had already been sent.
GI reports Can be triggered independently from the GI bit in
TrgOps
Behavior at buffer overflow When buffer overflow occurs all reports generated after
buffer overflow has the BufOvfl flag set.
To stop sending reports with the BufOvfl flag, the client
should disable BRCB and clear the BufOvfl flag by
setting PurgeBuf=TRUE.
Sending of already buffered reports after enabling BRCB All reports that have been already buffered, after setting
the RptEna=TRUE are sent in chronological order, e.g.
the oldest reports are sent first.
Multi client access to BRCB It is possible to access and configure the same BRCB
from different clients, however, it is recommended that
each BRCB be accessed and configured by only one
client.
Note the following restriction: The first client to enable a
BRCB establishes the “minimum MMS PDU size”
required for this BRCB. This BRCB can then be enabled
by any client which has the MMS PDU size at least as big
as the established “minimum MMS PDU size” for that
BRCB.
This restriction is required since the initial use may have
left buffered reports in the BRCB. The “minimum MMS
PDU size” was used for segmentation of the reports. If a
client enable the BRCB with a smaller “minimum MMS
PDU size”, the reports stored in a buffer cannot be sent
to this client due to their larger size.
GSSE
Description Value/Clarification
What elements of a subscribed GSSE header are checked N source MAC address
to decide the message is valid and the allData values are Y destination MAC address
accepted? If yes, describe the conditions. For example: Y timeAllowedtoLive
Destination MAC address = as multicast Y SendingIED
SendingIED = valid reference, not NULL Nt
timeAllowedtoLive > 0 N stNum
numDatSetEntries = matches with number of datSet N sqNum
members & allData members Y numDatSetEntries
What is the behavior when one subscribed GSSE A single “missing” GSSE message is ignored.
message isn’t received or syntactically incorrect (missing
GSSE)?
What is the behavior when one subscribed GSSE It signals this GSSE as “offline”.
message exceeds the previous time Allowed to Live (TAL)?
What is the behavior when a subscribed GSSE message is Sequence number is ignored.
out-of-order?
What is the behavior when a subscribed GSSE message is Sequence number is ignored.
duplicated?
Description Value/Clarification
Supported control modes: Y status-only
Y direct-with-normal-security
Y sbo-with-normal-security
Y direct-with-enhanced-security
Y sbo-with-enhanced-security
Description Value/Clarification
What quality bits are supported N LeapSecondsKnown
Y ClockFailure
Y ClockNotSynchronized
What is the behavior when the time synchronization Internal clock is used.
signal/messages are lost
When is the quality bit "Clock failure" set? It is set when SNTP packet with LI field (Leap Indicator)
with both bits set to ON is received.
When is the quality bit "Clock not synchronised” set? It is set when the communication is lost with the time
server. The timeout for setting this bit is 1 minute for
unicast mode, 5 minutes for anycast mode and up to 18
minutes for broadcast mode.
After startup the device has not set this quality bit even if
the time server is not present or not working. The bit is set
when the corresponding timeout elapses.
Description Value/Clarification
What is structure of files and directories? The main directory for files is “/LD/XXXLD/” where XXXLD
is the Logical Device name.
COMTRADE files are located in “/LD/XXXLD/COMTRADE/”
directory. All other files are in “/LD/XXXLD/” directory.
The device retrieves the content and/or definition of files
when the client’s request contains the filename with full
path or only the filename without path. Relative paths like
"/XXXLD/file1" or "COMTRADE/file1" are not allowed and
are returned by the server with error code “file-non-
existing".
7.3.7.3.11 PIXIT for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 2
This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface
in 650 family of relays.
Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10.
Contents of this document: Each chapter specifies the PIXIT for each applicable ACSI service model as structured in
IEC 61850-10.
Description Value/Clarification
Maximum number of clients that can set-up an association 5
simultaneously
TCP_KEEPALIVE value. The recommended range is between 1 and 5 seconds but if no application message is
20s detected within the As3 value, the device
closes the connection.
Lost connection detection time 120 seconds (Configurable)
Authentication is not supported yet
What association parameters are necessary for successful Y Transport selector
association? Y Session selector
Y Presentation selector
N AP Title
N AE Qualifier
If association parameters are necessary for association, describe Transport selector 0001
the correct values e.g. Session selector 0001
Presentation selector 00000001
AP Title N/A
AE Qualifier N/A
What is the maximum and minimum MMS PDU size? Max MMS PDU size 120000
Min MMS PDU size 32000.
What is the maximum start up time after a power supply interrupt?90 seconds
Description Value/Clarification
Which analogue value (MX) quality bits are supported (can be set by Validity:
server)? Y Good
Y Invalid
N Reserved
Y Questionable
N Overflow
Y OutofRange
Y BadReference
N Oscillatory
Y Failure
N OldData
N Inconsistent
N Inaccurate
Source:
N Process
N Substituted
N Test
N OperatorBlocked
Which status value (ST) quality bits are supported (can be set by Validity:
server)? Y Good
Y Invalid
N Reserved
Y Questionable
N BadReference
Y Oscillatory
Y Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
Y Substituted
Y Test
N OperatorBlocked
What is the maximum number of data object references in one Deprecated
GetDataValues request?
What is the maximum number of data object references in one Deprecated
SetDataValues request?
Which Mode values are supported 1 Y On
N [On-]Blocked
N Test
N Test/Blocked
N Off
1. IEC 61850-6:2009 clause 9.5.6 states that if only a subrange of the enumeration value set is
supported, this shall be indicated within an ICD file by an enumeration type, where the
unsupported values are missing
Description Value/Clarification
What is the maximum number of data elements in one data set? 576
(compare ICD setting)
How many persistent data sets can be created by one or more Not Supported
clients?
(this number includes predefined datasets)
How many non-persistent data sets can be created by one or more Not Supported
clients?
Description Value/Clarification
Are substituted values stored in volatile memory? Not Supported
Description Value/Clarification
What is the number of supported setting groups for each logical 3 groups for “PRO” logical device 3
device?
What is the effect of when and how the non-volatile storage is The server saves to non-volatile storage 25
updated? seconds after confirmation.
(compare IEC 61850-8-1 $16.2.4)
Can multiple clients edit the same setting group No
What happens if the association is lost while editing a setting Lost Permission and EditSG = 0
group?
Is EditSG value 0 allowed Yes
When ResvTms is not present how long is an edit setting group While EditSG > 0
locked?
Description Value/Clarification
The supported trigger conditions are: Y integrity
(compare PICS) Y data change
Y quality change
N data update
Y general interrogation
The supported optional fields are: Y sequence-number
Y report-time-stamp
Y reason-for-inclusion
Y data-set-name
Y data-reference
Y buffer-overflow
Y entryID
Y conf-rev
Y segmentation
Can the server send segmented reports? Y
Mechanism on second internal data change notification of the Send report immediately
same analogue data value within buffer period
(Compare IEC 61850-7-2 $14.2.2.9)
Multi client URCB approach Each URCB is visible to all clients
(compare IEC 61850-7-2:2003 $14.2.1)
Description Value/Clarification
What is the default value of LogEna? Not supported
(Compare IEC 61850-8-1 $17.3.3.2.1, the default value should be
FALSE)
What is the format of EntryID? Deprecated
Are there are multiple Log Control Blocks that specify the Not supported
Journaling of the same MMS NamedVariable and TrgOps and the
Event Condition?
(Compare IEC 61850-8-1 $17.3.3.3.2)
Pre-configured LCB attributes that cannot be changed online: Not supported
Description Value/Clarification
Can the test (Ed1) / simulation (Ed2) flag in the published GOOSE N
be set?
What is the behavior when the GOOSE publish configuration is DUT keeps GoEna=F.
incorrect? Configuration tool does not allow wrong
configuration to be uploaded into device
e.g. empty dataset.
Published FCD supported common data classes are: SPS, INS, ENS, ACT, ACD, MV, CMV, SAV, WYE,
DEL, SEQ, INC, ENC, SPC, DPC, INC, ENC. (Only
the elements with FC=ST or MX are published).
What is the slow retransmission time? Configured by SCL or GoCB MaxTime
Is it fixed or configurable?
What is the fastest retransmission time? MinTime = 5 ms
Is it fixed or configurable? Fixed
Can the GOOSE publish be turned on / off by using Y
SetGoCBValues(GoEna)?
What is the initial GOOSE sqNum after restart? sqNum = 1
Can the GOOSE data set contain:
- structured data objects (FCD) Y
- timestamp data attributes Y (timestamp attributes are not supported)
How is the retransmission curve after a change? sqNum = 0 New change
sqNum = 1 -> 5ms later with TAL = 1000
sqNum = 2 -> 10ms later with TAL = 1000
sqNum = 3 -> 15ms later with TAL = 4000
sqNum = 4 -> 1000ms later with TAL = Update
time* multiplied by 4
sqNum = 5 -> Update time* later with TAL =
Update time* multiplied by 4
sqNum = 6-> Update time* later with TAL =
Update time* multiplied by 4
sqNum = 7 ……..
………...
………….
*Update time is configured in the ICT
Description Value/Clarification
What elements of a subscribed GOOSE header are checked to Y destination MAC address
decide the message is valid and the allData values are accepted? Y APPID
If yes, describe the conditions. N gocbRef
Notes: Y timeAllowedtoLive
- The VLAN tag may be removed by a ethernet switch and will not N datSet
be checked. Y goID
- The simulation flag will always be checked (Ed2) Nt
- The ndsCom shall always be checked (Ed2) N stNum
N sqNum
Y simulation / test
N confRev
Y ndsCom
Y numDatSetEntries
When is a subscribed GOOSE marked as lost? Message does not arrive after TAL
(TAL = time allowed to live value from the last received GOOSE
message)
What is the behavior when one or more subscribed GOOSE Message is ignored, but when the next correct
messages isn’t received or syntactically incorrect (missing message is received, it proceeds as normal.
GOOSE)
What is the behavior when a subscribed GOOSE message is out- Message proceeds.
of-order?
What is the behavior when a subscribed GOOSE message is Message is ignored.
duplicated?
Does the device subscribe to GOOSE messages with and without Y
the VLAN tag?
Can the GOOSE data set contain:
- structured data objects (FCD) Y
- timestamp data attributes N
Subscribed FCD supported common data classes are: DUT can receive all kinds of data but only
digitals can be mapped.
Are subscribed GOOSE with test=T (Ed1) / simulation=T (Ed2) N
accepted in test/simulation mode?
What is the behavior when a subscribed GOOSE message with The message is ignored. The mechanism
TAL = 0 is received by the subscriber? applies where the new GOOSE message is not
received within a TAL.
What is the behavior when a subscribed GOOSE message hasn’t The message is ignored. The mechanism
the expected data structure? applies where the new GOOSE message is not
received within a TAL.
Description Value/Clarification
What control models are supported? Deprecated
(compare PICS)
Is the control model fixed, configurable and/or dynamic? Configurable & Dynamic
Is TimeActivatedOperate supported? Deprecated
(compare PICS or SCL)
Is “operate-many” supported? Deprecated
(compare sboClass)
Will the DUT activate the control output when the test attribute is set in N
the SelectWithValue and/or Operate request?
(when N test procedure Ctl2 is applicable)
What are the conditions for the time (T) attribute in the SelectWithValue Deprecated
and/or Operate request?
Is pulse configuration supported? Deprecated
(compare pulseConfig)
What is the behavior of the DUT when the check conditions are set? N synchrocheck
N interlock-check
DUT ignores the check value and always
performs the check
Does the IED accept a select/operate on the same control object from N DOns
two different clients at the same time? N SBOns
N DOes
N SBOes
Does the IED accept a Select/SelectWithValue from the same client N SBOns
when the control object is already selected (Tissue #334)? N SBOes
Is the internal validation for SBOes performed during the SelectWithValue and Operate
SelectWithValue and/or Operate step?
Can a control operation be blocked by Mod=Off or [On-]Blocked? Deprecated
(Compare PIXIT-Sr5)
Does the IED support local/remote operation? Y (Only for XCBR)
Does the IED send an InformationReport with LastApplError as part of N SBOns
the Operate response for control with normal security? N DOns
How to force a “parameter-change-in-execution”? N/A SBOns
N/A SBOes
Description Value/Clarification
What time quality bits are supported (may be set by the IED) Y LeapSecondsKnown
N ClockFailure
Y ClockNotSynchronized.
Describe the behavior when the time server(s) ceases to On one time server: An event is generated
respond? On all time servers: An event is generated
What is the time server lost detection time 60 seconds
How long does it take to take over the new time from time 2 seconds
server?
When is the time quality bit “ClockFailure” set? Never
When is the time quality bit “Clock not Synchronized” set? 60 seconds after the time server(s) ceases to
respond.
Is the timestamp of a binary event adjusted to the configured Deprecated
scan cycle?
Does the device support time zone and daylight saving? Y
Which attributes of the SNTP response packet are validated? Y Leap indicator not equal to 3
Y Mode is equal to SERVER
N OriginateTimestamp is equal to value sent by
the SNTP client as Transmit Timestamp
Y RX/TX timestamp fields are checked for
reasonableness
Y SNTP version 3 and/or 4
N other (describe)
Do the COMTRADE files have local time or UTC time and is this Local
configurable? N
Description Value/Clarification
What is structure of files and directories?
Where are the COMTRADE files stored? /COMTRADE
Are comtrade files zipped and what files are included in each
zip file? N
Directory names are separated from the file name by: “/”
The maximum file name size including path? 255 chars
(recommended 64 chars)
Are directory/file name case sensitive? Y
Maximum file size for SetFile?
Is the requested file path included in the MMS fileDirectory Y
respond file name?
Is the wild char supported MMS fileDirectory request? N
Can two clients get a file at the same time? Y same file
Y different files
Which files can be deleted?
Description Value/Clarification
Which ACSI services are tracked by LTRK.GenTrk? N/A
7.3.7.3.12 PIXIT for 650 family of relays whose order code has Rear Ethernet Communication Board 2
option "H", "G", "K", "J", "L", "M" and IEC 61850 Edition 1
Reference documentation: PIXIT For F650 relay V1_10 firm7_52.
This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface
in:
F650 Bay Controller with firmware version 7.52
Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10.
The PIXIT entries contain information which is not available in the PICS, MICS, TICS documents or SCL file.
Each table specifies the PIXIT for applicable ACSI service model as structured in IEC 61850-10. The "Ed" column
indicates if the entry is applicable for IEC 61850 Edition 1 and/or Edition 2.
ID Ed Description Value/Clarification
As1 1 Maximum number of clients that can set-up an association 5
simultaneously?
As2 1, 2 TCP_KEEPALIVE value: 5 seconds but if no application message is
The recommended range is between 1 and 20s detected within the As3 value, the device
closes the connection.
As3 1, 2 Lost connection detection time: 120 seconds (Configurable)
As4 - Authentication is not supported yet.
As5 1, 2 What association parameters are necessary for successful Y Transport selector
association? Y Session selector
Y Presentation selector
N AP Title
N AE Qualifier
As6 1, 2 If association parameters are necessary for association, the Transport selector 0001
correct values are: Session selector 0001
Presentation selector 00000001
As7 1, 2 What is the maximum and minimum MMS PDU size? Max MMS PDU size120000
Min MMS PDU size7000.
As8 1, 2 What is the maximum start up time after a power supply interrupt?90 seconds
ID Ed Description Value/Clarification
Sr1 1, 2 Which analogue value (MX) quality bits are supported (can be set by Validity:
server)? Y Good
Y Invalid
N Reserved
Y Questionable
N Overflow
Y OutofRange
Y BadReference
N Oscillatory
Y Failure
N OldData
N Inconsistent
N Inaccurate
Source:
N Process
N Substituted
N Test
N OperatorBlocked
Sr2 1, 2 Which status value (ST) quality bits are supported (can be set by Validity:
server)? Y Good,
Y Invalid
N Reserved
Y Questionable
N BadReference
Y Oscillatory
Y Failure
N OldData
N Inconsistent
N Inaccurate
Source:
Y Process
Y Substituted
Y Test
N OperatorBlocked
Sr3 - What is the maximum number of data object references in one Deprecated
GetDataValues request?
Sr4 - What is the maximum number of data object references in one Deprecated
SetDataValues request?
Sr5 1 Which Mode values are supported? 1 Y On
N [On-]Blocked
N Test
N Test/Blocked
N Off
1. IEC 61850-6:2009 clause 9.5.6 states that if only a subrange of the enumeration value set is supported, this shall
be indicated within an ICD file by an enumeration type, where the unsupported values are missing
ID Ed Description Value/Clarification
Ds1 1 What is the maximum number of data elements in one data set? 576
(compare ICD setting)
Ds2 1 How many persistent data sets can be created by one or more Not Supported
clients?
(this number includes predefined datasets)
Ds3 1 How many non-persistent data sets can be created by one or more Not Supported
clients?
ID Ed Description Value/Clarification
Sb1 1 Are substituted values stored in volatile memory? Not Supported
ID Ed Description Value/Clarification
Sg1 What is the number of supported setting groups for each logical 6 groups for “PRO” logical device 3
device?
Sg2 What is the effect of when and how the non-volatile storage is The server saves to non-volatile storage 25
updated? seconds after confirmation.
(compare IEC 61850-8-1 $16.2.4)
Sg3 Can multiple clients edit the same setting group? N
Sg4 What happens if the association is lost while editing a setting Lost Permission and EditSG = 0
group?
Sg5 Is EditSG value 0 allowed? Y
Sg6 When ResvTms is not present, how long is an edit setting group While EditSG > 0
locked?
ID Ed Description Value/Clarification
Rp1 1 The supported trigger conditions are: Y Integrity
(compare PICS) Y Data change
Y Quality change
N Data update
Y General interrogation
Rp2 1 The supported optional fields are: Y Sequence-number
Y Report-time-stamp
Y Reason-for-inclusion
Y Data-set-name
Y Data-reference
Y Buffer-overflow
Y EntryID
Y Conf-rev
Y Segmentation
Rp3 1, 2 Can the server send segmented reports Y
Rp4 1, 2 Mechanism on second internal data change notification of the Send report immediately
same analogue data value within buffer period:
(Compare IEC 61850-7-2 $14.2.2.9)
Rp5 1 Multi client URCB approach: Each URCB is visible to all clients
(compare IEC 61850-7-2:2003 $14.2.1)
ID Ed Description Value/Clarification
Lg1 1, 2 What is the default value of LogEna Not Supported
(Compare IEC 61850-8-1 $17.3.3.2.1, the default value should be
FALSE)
Lg2 - What is the format of EntryID Deprecated
Lg3 1, 2 Are there are multiple Log Control Blocks that specify the Not Supported
Journaling of the same MMS NamedVariable and TrgOps and the
Event Condition
(Compare IEC 61850-8-1 $17.3.3.3.2)
Lg4 1 Pre-configured LCB attributes that cannot be changed online Not Supported
ID Ed Description Value/Clarification
Gp1 1, 2 Can the test (Ed1)/simulation (Ed2) flag in the published GOOSE be N
set?
Gp2 1 What is the behavior when the GOOSE publish configuration is DUT keeps GoEna=F.
incorrect? Configuration tool does not allow wrong
configuration to be uploaded into device
e.g. empty dataset.
Gp3 1, 2 Published FCD supported common data classes are: SPS, INS, ENS, ACT, ACD, MV, CMV, SAV, WYE,
DEL, SEQ, INC, ENC, SPC, DPC, INC, ENC. (Only
the elements with FC=ST or MX are published.)
Gp4 1, 2 What is the slow retransmission time? Configured by SCL or GoCB MaxTime
Is it fixed or configurable?
Gp5 1, 2 What is the fastest retransmission time? MinTime = 5 ms
Is it fixed or configurable? Fixed
Gp6 - Can the GOOSE publish be turned on/off by using Y
SetGoCBValues(GoEna)?
Gp7 1, 2 What is the initial GOOSE sqNum after restart? sqNum = 1
Gp8 1 Can the GOOSE data set contain:
- structured data objects (FCD) Y
- timestamp data attributes Y (timestamp attributes are not supported)
Gp9 How is the retransmission curve after a change? sqNum = 0 New change
sqNum = 1 -> 5ms later with TAL = 1000
sqNum = 2 -> 10ms later with TAL = 1000
sqNum = 3 -> 15ms later with TAL = 4000
sqNum = 4 -> 1000ms later with TAL = Update
time* multipled by 4
sqNum = 5 -> Update time* later with TAL =
Update time* multipled by 4
sqNum = 6-> Update time* later with TAL =
Update time* multipled by 4
sqNum = 7 ……..
………...
………….
*Update time is configured in the ICT
ID Ed Description Value/Clarification
Gs1 1, 2 What elements of a subscribed GOOSE header are checked to Y Destination MAC address
decide the message is valid and the allData values are accepted? Y APPID
If yes, describe the conditions. N gocbRef
Notes: Y timeAllowedtoLive
- The VLAN tag may be removed by a ethernet switch and shall N datSet
not be checked Y goID
- The simulation flag shall always be checked (Ed2) Nt
- The ndsCom shall always be checked (Ed2) N stNum
N sqNum
Y simulation/test
N confRev
Y ndsCom
Y numDatSetEntries
Gs2 1, 2 When is a subscribed GOOSE marked as lost? Message does not arrive after TAL.
(TAL = time allowed to live value from the last received GOOSE
message)
Gs3 1, 2 What is the behavior when one or more subscribed GOOSE Message is ignored, but when the next correct
messages isn’t received or syntactically incorrect (missing message is received, it proceeds as normal.
GOOSE)?
Gs4 1, 2 What is the behavior when a subscribed GOOSE message is out Message proceeds.
of order?
Gs5 1, 2 What is the behavior when a subscribed GOOSE message is Message is ignored.
duplicated?
Gs6 1 Does the device subscribe to GOOSE messages with and without Y
the VLAN tag?
Gs7 1 Can the GOOSE data set contain:
- structured data objects (FCD) Y
- timestamp data attributes N
Gs8 1, 2 Subscribed FCD supported common data classes are: DUT can receive all kinds of data but only
digitals can be mapped.
Gs9 1, 2 Are subscribed GOOSE with test=T (Ed1)/simulation=T (Ed2) N
accepted in test/simulation mode?
Gs10 2 What is the behavior when a subscribed GOOSE message with The message is ignored. The mechanism
TAL = 0 is received by the subscriber? applies where the new GOOSE message is not
received within a TAL.
Gs11 2 What is the behavior when a subscribed GOOSE message doesn’t The message is ignored. The mechanism
have the expected data structure? applies where the new GOOSE message is not
received within a TAL.
ID Ed Description Value/Clarification
Ct1 - What control models are supported? Deprecated
(compare PICS)
Ct2 1, 2 Is the control model fixed, configurable and/or dynamic? Configurable and Dynamic
Ct3 - Is TimeActivatedOperate supported? Deprecated
(compare PICS or SCL)
Ct4 - Is “operate-many” supported? Deprecated
(compare sboClass)
Ct5 1 Will the DUT activate the control output when the test attribute is set in N
the SelectWithValue and/or Operate request?
(when N test procedure Ctl2 is applicable)
Ct6 - What are the conditions for the time (T) attribute in the SelectWithValue Deprecated
and/or Operate request?
Ct7 - Is pulse configuration supported? Deprecated
(compare pulseConfig)
Ct8 1, 2 What is the behavior of the DUT when the check conditions are set? N synchrocheck
N interlock-check
DUT ignores the check value and always
perform the check
Is this behavior fixed, configurable or online changeable?
Ct9 1, 2 Which additional cause diagnosis are supported? Y Unknown
Y Not-supported
Y Blocked-by-switching-hierarchy
N Select-failed
Y Invalid-position
Y Position-reached
N Step-limit
N Blocked-by-Mode
N Blocked-by-process
N Blocked-by-interlocking
N Blocked-by-synchrocheck
Y Command-already-in-execution
N Blocked-by-health
N 1-of-n-control
N Abortion-by-cancel
Y Time-limit-over
N Abortion-by-trip
Y Object-not-selected
Edition 1 specific values:
N Parameter-change-in-execution
Edition 2 specific values:
Y Object-already-selected
N No-access-authority
N Ended-with-overshoot
N Abortion-due-to-deviation
N Abortion-by-communication-loss
N Blocked-by-command
N None
Y Inconsistent-parameters
Y Locked-by-other-client
N Parameter-change-in-execution
Ct10 1, 2 How to force a “test-not-ok” response with SelectWithValue request? Device in local mode
Ct11 1, 2 How to force a “test-not-ok” response with Select request?
Ct12 1, 2 How to force a “test-not-ok” response with Operate request? DOns: Sending T=1
SBOns: Sending T=1
DOes: Sending T=1
SBOes: Sending T=1
ID Ed Description Value/Clarification
Tm1 1, 2 What time quality bits are supported (may be set by the IED) Y LeapSecondsKnown
N ClockFailure
Y ClockNotSynchronized.
Tm2 1, 2 Describe the behavior when the time server(s) ceases to On one time server: An event is generated
respond. On all time servers: An event is generated
What is the time server lost detection time? 180 seconds
Tm3 1, 2 How long does it take to take over the new time from the time 2 seconds
server?
Tm4 1, 2 When is the time quality bit “ClockFailure” set? Never
Tm5 1, 2 When is the time quality bit “Clock not Synchronized” set? 60 seconds after the time server(s) ceases to
respond.
Tm6 - Is the timestamp of a binary event adjusted to the configured Deprecated
scan cycle?
Tm7 1 Does the device support time zone and daylight saving? Y
Tm8 1, 2 Which attributes of the SNTP response packet are validated? Y Leap indicator not equal to 3
Y Mode is equal to SERVER
N OriginateTimestamp is equal to value sent by
the SNTP client as Transmit Timestamp
Y RX/TX timestamp fields are checked for
reasonableness
Y SNTP version 3 and/or 4
N Other (describe)
Tm9 1, 2 Do the COMTRADE files have local time or UTC time? Local
Is this configurable? N
ID Ed Description Value/Clarification
Ft1 1 What is structure of files and directories? /COMTRADE
Where are the COMTRADE files stored?
Are comtrade files zipped? N
What files are included in each zip file?
Ft2 1, 2 Directory names are separated from the file name by: “/”
Ft3 1 The maximum file name size including path: 255 chars
(recommended 64 chars)
Ft4 1, 2 Are directory/file name case sensitive? Case sensitive
Ft5 1, 2 Maximum file size for SetFile? N/A
Ft6 1 Is the requested file path included in the MMS fileDirectory Y
response file name?
Ft7 1 Is the wild char supported MMS fileDirectory request? No
Ft8 1, 2 Is it allowed that two clients get a file at the same time? Y same file
Y different files
Ft9 1, 2 Which files can be deleted? N/A
ID Ed Description Value/Clarification
Tr1 2 Which ACSI services are tracked by LTRK.GenTrk? N/A
Note: The saving process is updated in ICD FILE STATUS in System Info and it is recommended that the relay is not rebooted
until the process finishes (OK WITHOUT DAIS or OK), otherwise the last value of “LocSta” could be lost.
7.4.2 GOOSES
650 relays support transmission and reception of configurable IEC 61850 Generic Object Oriented Substation Event
(GOOSE). If GOOSE communications need to be enabled, Remote comms setting must be set to GOOSE in
EnerVista 650 Setup at Setpoint > Input/Output > Remote Comms.
Configurable GOOSE is recommended for implementations that require GOOSE data transfer between 650 relays
and devices from other manufacturers.
Report control block configuration settings are modified from IEC61850 configurator writing directly in a CID file.
There is no Modbus register assigned to those. The datasets for reports are fully configurable with CDCs from any
Logical Node. The Description field in the LN is fixed text and it cannot be updated from the Modbus settings
By default,
• if Unbuffered report is selected, 5 Unbuffered Report Control Blocks are created. This figure can be modified from 1 to
5.
• If Buffered report is selected, 1 Unbuffered Report Control Block is created. This figure can be modified from 1 to 5.
In Actual > Inputs/Outputs > Remote Inputs > Remote GOOSE Digital Inputs:
Rem GOOSE Dig Inp X - Provides status of Remote Goose Digital input X that relay is subscribed to. The green
LED lights up if Remote GOOSE Digital Input was set to 1 last time it was received and it turns off if the last Remote
GOOSE Digital Input was set to 0.
There is a maximum of 32 Remote GOOSE Digital Inputs that the relay can be subscribed to.
In Actual > Inputs/Outputs > Remote Inputs > Remote Inputs:
Remote Input X - Provides status of Remote input X that relay is subscribed to. The green LED lights up if Remote
Input was set to 1 last time it was received and it turns off if the last Remote Input was set to 0
There is a maximum of 32 Remote Inputs that relay can be subscribed to. These remote inputs are digital signals.
In Actual > Inputs/Outputs > Remote Inputs > Remote GOOSE Analog Inputs:
Rem GOOSE Ana Inp X- This is the last analog value received in the Remote GOOSE Analog Input configured.
The relay can be subscribed to up to maximum of 8 different float remote GOOSE analog values and 8 different
integer remote GOOSE analog values.
In Actual > Inputs/Outputs > Remote Outputs > Remote GOOSE Digital Outputs:
Rem GOOSE Dig Out X - Provides status of Remote Goose Digital outputs that are configured to be transmitted by
the relay. The green LED lights up if Remote GOOSE Digital Output is set to 1 and it turns off if Remote GOOSE
Digital Output is set to 0
ICD Edition:
This field shows which IEC 61850 Edition if CID that relays is working with. For F650. See 7.1 IEC 61850 Overview
on page 7–1.
1. WATCH OUT! If the ICD status is "MODIFIED" or "IN PROGRESS" it is not advisable to switch off the
NOTICE unit because the latest settings will not be stored in the unit.
2. In the case that ERROR SG CID is displayed in the ICD Status, ensure that the managed CID has
Setting Group enabled if the Setting Groups function is enabled, or ensure that the managed CID has
Setting Group disabled if the Setting Groups function is disabled.
For firmware versions 7.20 and 7.21:
– default_F650SG_v7XX.cid: CID file with setting group option enabled
– default_F650_v7XX.cid: CID file with setting group option disabled
For firmware versions below 7.20 or above 7.21:
– default_F650_v7XX.cid: CID file with setting group option disabled/enabled
3. Take into in account that if ERROR HEADER CID value is displayed in the ICD STATUS or ICD STATUS
NOT VAL section in Actual Values > Status > System info, the relay cannot communicate using
IEC 61850 until this discrepancy is resolved. CID version and firmware version must match for a fully
functional relay.
Offline Operation Mode: When user is not communicating with 650 Family relay, IEC 61850 Configurator tool can
be used to work offline mode. In this case, if IEC 61850 Configurator menu is clicked at the menu toolbar in
EnerVista, the following windows prompts to allow selection of the IED version to be configured.
Online Operation Mode: When communicating with an F650 using the EnerVista 650 Setup software, the
IEC61850 Configurator tool allows access to the CID/IEC of the connected device, or to send a previously
configured file.
expect information in intAddr field in line with the 650 Edition 2 CID default template (version 7.71 or above) provided with
EnerVista 650 8.12 or above.
Tools Menu: (CID conversion tools)
A CID file converter menu option is available in the IEC 61850 Configurator menu: Tools > ConvertCIDFiles. The
CID file converter enables CID file conversion, allowing for conversion of CID files in parallel with relay firmware
updates. The main parts of the CID file that are maintained are the configurable fields at the Communication and IED
levels, the public and private Settings, Datasets, Report Control Blocks, GOOSE Transmission Control Blocks and
GOOSE Reception.
To convert a CID file, follow these steps:
1. In the IEC61850 Configurator, select Tool > ConvertCIDFiles.
4. The CID file Converter fills in the firmware version of the selected CID file under Source Version. Select the new
firmware version for the CID file under Destination Version.
Note: For successful conversion, the default CID file templates installed with the EnerVista 650 Setup must be in the
installed folder location with their original names, as shown.
displayed, followed by a message confirming the name and location of the converted file.
For all scenarios, after opening the file all ICD data is displayed in the tree on the left and the user can start
configuring the IEC 61850 protocol in 650 devices.
To determine whether the relay is working with CID Edition 1 or Edition 2, check EnerVista > Actual Values >
System Info for firmware versions above 7.60.
After retrieving the CID file it can be saved on the local PC by clicking the Open button and selecting the received
file. All ICD data is displayed in the tree on the left, and the IEC 61850 protocol is ready to configure.
If the user is already communicating with the 650 device using the Modbus/TCP option in the Communication
menu the send files options are performed over the IP Address selected on the Communication menu.
If the user is working in offline mode using the Open IEC 61850/CID file from disk option, when the "end IEC 61850
file to device option is selected, the program shall pop up a window to introduce the IP Address.
These pop-up menus also appear the Send IEC 61850 file to device option is selected after retrieving the files
using the Receive IEC 61850 file from device.
Exit
When Exit is selected, the program prompts to save the configuration to disk or send it to the relay.
• IP, IP-SUBNET, IP-GATEWAY: The parameters are the configured ETH_A IP details configured in the device through
EnerVista: Setpoints > Product Setup > Communications > Network
• OSI-AP-Title, OSI-AE-Qualifier, OSI-PSEL, OSI-SSEL, OSI-TSEL: The parameters must be configured according to the IEC
61850 standard
• GOOSE-port: Three different options are available in this dropbox depending which port wants to be selected for
GOOSE transmission (ETHA-ETHB-Both) the user to change the GOOSE port number for GOOSE communication.
• MMS-Port: The range of the setting is 1 to 65535, in steps of 1. The setting allows the user to change the TCP port
number for MMS connections.
• MMS- Connection-Timeout: The setting is useful for detecting "fail" IEC 61850 connections. The timer must be
application specific for IEC 61850. If there is no data traffic on an established connection for more than this setting
time, the connection is disconnected from the server
Server Configuration
• IED NAME: Up to 64 alphanumeric characters. The IED Name represents the MMS domain name (IEC 61850 logical
device) where all IEC/MMS logical nodes are located. Valid characters for these values are upper and lowercase
letters, numbers, and the underscore (_) character, and the first character in the string must be a letter. This conforms
to the IEC 61850 standard. Default value is "GEDevice"
• UseDoiDai:
– If this setting is set to false: the relay works only with the settings located in the relay's memory and the changes
performed on the ICD in settings related with the protection and control functions are only stored on the ICD file
but not updated in the relay.
– If this setting is set to true, you are selecting the ICD file settings to prevail over the relay settings. This means that
after changing settings in the ICD and powering the relay off and on the unit works with the settings included in
the ICD.
All setting changes performed through the HMI or EnerVista 650 Setup are automatically updated over the ICD file,
likewise if there is any change in the ICD file these changes are updated in the relay settings. The relay starts working
with the new ICD file after sending the file to the unit and powering the relay off and on.
• Power Max and Min Automatic Calculation *:
– If set to True, Max and Min values used for Power reporting are automatically calculated based on the CT Ratio
and VT Ratio setpoints.
– If set to False, Max and Min values used for Power reporting are configurable in the Settings / Max and Min tab.
*This setting is only available for Firmware version 7.70 and above.
• PRO functional IdName: ID name of logical device where all protection logical nodes are available. The logical device
name is used to identify the IEC 61850 logical device that exists within the F650 and this name is composed of two
parts: the IED NAME and the PRO/CON functional IdName. Default name for PRO functional IdName is PRO
• CON functional IdName: ID name of logical device where all control logical nodes are available. Default name for CON
functional IdName is CON
Settings
Four different levels are available under setting section:
• Deadbands
• Commands
• Timeouts
• Oscillation
• Max and Min
DEADBANDS
The equations to calculate minimum (min) and maximum (max) values in the MMXU nodes of F650 are as follows:
Note: When max/min values are configurable, setting these values below accuracy levels
could result in unpredictable behavior.
Note: When max/min values are configurable, setting these values below accuracy levels
could result in unpredictable behavior.
In addition to the MMXU logical node, MSQI and Remote Input GGIO (default name rinGGIO1)
also have attributes that are analogue values and contain db parameters to establish
deadbands.
For firmware version below 7.00, deadbands are available in ICD/CID tab.
WARNING: If deadbands are configured to allow measurement oscillation reporting below accuracy level, relay
could present with some unexpected behaviors.
*Max and min values for Power reporting are only available when the Power Max and Min Automatic Calculation
setting is set to false (See Server Configuration on page 7–228)
COMMANDS
In the F650 relay IEC 61850 controllable data exist in logical nodes vinGGIO, XCBR and CSWI:
• vinGGIO maps to Virtual Inputs of F650.
• XCBR represents the circuit breaker.
• CSWI logical nodes represent switchgear of F650 relay.
OSCILLATION
There are two settings used for the detection of the digital inputs of I/O boards and rinGGIO LN oscillation,
OscTmms and NumChgs.
·OscTmms: time between two changes in the same direction (from 0 to 1 or from 1 to 0) to consider that a signal is
oscillating. There are four settings for each GGIO (OscTmmsA, OscTmmsB, OscTmmsC and OscTmmsD), one for
each group of inputs, and one in rinGGIO logical node.
·NumChgs: number of changes that have to be produced in an oscillatory signal to be consider as invalid and not to
continue sending changes of the signal, sending the value of the signal when it was consider as oscillatory.
DataSet
Two different sections will be differentiated under this section:
• Summary
• DataSetXX
SUMMARY
In this screen, user can find a list with information about where a configured DataSetXX has been used (Report and/
or GOOSE).
If a DataSetXX is shared by more than one Report/GOOSE, all elements will be listed in DataSetXX Parameter field,
separated by commas.
DataSetXX MemberX: After the DataSet name is defined, members can be added by dragging and dropping elements
from the complete data model of the IED displayed below to the Data Set.
There is a counter in the right-up corner of configuration area where users can visualize how many basic attributes
have been added to a DataSetXX. This counter will increase automatically when basic attributes are dragged and
dropped.
For example id CON.MMXU1.MX.A.net.cVal is dragged and dropped into DataSet, counter will be increased to two
as there are two basic attributes in it (CON.MMXU1.MX.A.net.cVal.mag and CON.MMXU1.MX.A.net.cVal .ang)
Reports
The 650 family relay supports both IEC 61850 buffered and unbuffered reporting. The device has configurable
reports, which include user-defined Data Sets and Report Control Blocks. Reporting is based on Data Sets, which
are collections of Data that can be included in Reports. The Report Control Block is a group of parameters which
permit IEC 61850 customization of the reports being sent by the IEC 61850 server. For example, the IntgPd
parameter of the Report Control Block contains the value in milliseconds of the interval between Integrity Reports
sent by IEC 61850 servers.
A 650 family relay can have up to 20 different reports and up to 20 different Data Sets linked (only one DataSet can
be linked to one Report). In the reports, each Dataset can be configured with a maximum of 576 Dataset Members.
All settings/datasets assigned to different reports can configured as described in this section. Up to 20 different
reports can be configured.
ReportX Name:
The first character in the value of this attribute must be a letter (upper or lower case). The rest of the characters must
be a number, a letter (upper or lower case) or a "_". The maximum number of characters allowed in IEC61850
Configurator is 30 and IEC61850 MMS Library adds two more characters indicating the number of the instance of the
RCB depending on the number of IEC61850 clients configured
ReportX RptID:
The attribute RptID is the client-specified report identifier of the RCB that has caused the generation of the report.
ReportX DatSet:
This dropbox lists only DataSets configured in DataSet section with less than 576 DataSet Members. Select the
Dataset that is going to be assigned to Report X,
ReportX ConfRev:
It represents the configuration revision number of the control block
ReportX OptFlds:
Different options for report triggers are listed in this dropbox list. One or more options the report triggers are shown in
the Supported Triggers list:
– Data-Change
– Quality-Change
– Integrity
– General Interrogation
ReportX BufTm:
This setting is only considered if ReportX Buffer setting is set to true. In case of an event that causes a report the server
will wait for BufTm ms for other events. All data that is to be reported because of events in this time span is sent in a
single report. If connection with client is lost, events will be logged during BufTm and they will be sent when client
connects again.
ReportX IntgPd
Only working if general interrogation is configured in trigger options. The integrity period specifies an interval in ms for
the periodic sending of integrity reports.
ReportX Buffered:
The standard distinguishes between two types of reporting: buffered reporting and unbuffered reporting. With
buffered reporting reports are buffered by the server in case a connection to the client is interrupted. This way reports
can be sent after the client has connected again. Buffered reporting is configured through buffered report control
blocks (BRCB). Unbuffered reporting is configured through unbuffered report control blocks (URCB).
If it set to true, report will be configured as buffered report control block (BRCB). If set to false, report will be configured
as unbuffered report control block (URCB)
ReportX Max Clients:
Number of clients that can be connected to a report control block. Up to 5 different clients can be configured
GOOSE
TxGOOSE
In this section, configure four different transmission GOOSE: TXGOOSEX.
2. A pop-up window allows selection of the CID file to import, with transmission GOOSES previously configured.
4. If any imported transmission GOOSE needs to be deleted, updated, moved up/down or the header needs to be edited,
right-click on the imported GOOSE in the IED panel list
Up to 32 Remote Inputs and 32 Goose Digital Inputs can be configured in a reception goose (RXGOOSE). The
configuration section shows a list with 64 different rows. The first 32 values are shown on the Remote Goose Digital
Inputs screen and the remaining 32 values are on the Remote Inputs screen.
In order to replace an Analog Input, first remove the existing Analog Input.
• For firmware version below 7.50: 3 setting group for F650 relay
• For firmware version 7.50 or above: 6 setting group for F650 relay
Each setting data contained in those Logical Nodes has a type derived from one of the following common data
classes defined in the standard IEC 61850-7-3: ING, SPG, ASG and CURVE. The setting data attributes of these
common data classes have functional constraints SG (setting group) and SE (setting group editable) when the
setting group function is enabled and SP (setpoint) when it is not.
When the setting group function is enabled the F650 relay has the following instances of the Logical Nodes
mentioned before:
PIOC
• Phase instantaneous overcurrent: SGphHiPIOC1 and SGphLoPIOC1*/ phHiPIOC1 and phLoPIOC1
• Neutral instantaneous overcurrent: SGndPIOC1*/ ndPIOC1
• Ground instantaneous overcurrent: SGgndPIOC1*/ gndPIOC1
• Sensitive ground instantaneous overcurrent: SGhsePIOC1*/ hsePIOC1
• Isolated ground instantaneous overcurrent: IsoGndPIOC**
• Broken conductor: BknCndPIOC**
PTOC
• Phase time overcurrent: SGphHiPTOC1 and SGphLoPTOC1*/ phHiPTOC1 and phLoPTOC1
• Neutral time overcurrent: SGndPTOC1*/ ndPTOC1
• Ground time overcurrent: SGgndPTOC1*/ gndPTOC1
• Sensitive ground time overcurrent: SGhsePTOC1*/ hsePTOC1
• Sensitive ground time overcurrent: hsePTOC**
• Negative sequence time overcurrent: NgSeqPTOC**
PTOF
• Overfrequency: SGPTOF1*/ PTOF1
PTOV
• Phase overvoltage: SGphsPTOV1*/ phsPTOV1
• Auxiliary overvoltage: SGauxPTOV1*/ auxPTOV1
• Neutral overvoltage: SGneuHiPTOV1 and SGneuLoPTOV1*/ neuHiPTOV1 and neuLoPTOV1
PTUV
• Phase undervoltage: SGphsPTUV1*/ phsPTUV1
• Auxiliary undervoltage: SGauxPTUV1*/ auxPTUV1
PTUF
• Underfrequency: SGPTUF1*/ PTUF1
RDIR
• Phase directional element: SGphsRDIR1*/ phsRDIR1
• Neutral directional element: SGndRDIR1*/ ndRDIR1
• Ground directional element: SGgndRDIR1*/ gndRDIR1
• Sensitive ground directional element: SGhseRDIR1*/ hseRDIR1
PDOP
• Forward overpower: FwdPDOP **
• Directional overpower: DirPDOP**
• Wattmeter ground overpower: WattPDOP**
PFRC
• Frequency rate of change: PFRC**
PDIS
• Load encroachment: LodEncPDIS**
PRTR
• Locked Rotor: LockedPRTR**
*These logical nodes model the corresponding protection function for setting groups in firmware version from 7.20 to
below 7.50
**These functions have been included from firmware version 7.50.
If “Use Setting Group” is set to true for firmware version from 7.20 to below 7.50, the new instances of the Logical
Nodes are accessible with the IEC 61850 Configurator as is shown in the following figure.
The next figure is a capture of an MMS browser where SGCB class attributes are shown and configured, setting
ActSG with the value 1 that corresponds with the first setting group in the F650 relay and EditSG with the value 2 that
corresponds with the second setting group.
As it is shown in the figure, the values of the settings of the setting group indicated with the ActSg are the ones with
the FC = SG in Logical Node SGphHiPTOC1, therefore the ones used by the high level of Phase Time Overcurrent
protection function in the relay.
On the other hand, as it is shown in the figure, the values of the settings of the setting group indicated with the EditSg
are the ones with the FC = SE in Logical Node SGphHiPTOC1.
As it is shown in the figure, the values of the settings of the setting group indicated with the ActSg are the ones with
the FC = SG in Logical Nodes phPTOC1, phPTOC2 and phPTOC3. Therefore the ones used by the high level of
Phase Time Overcurrent protection function in the relay.
On the other hand, as it is shown in the figure, the values of the settings of the setting group indicated with the EditSg
are the ones with the FC = SE in Logical Nodes phPTOC1, phPTOC2 and phPTOC3.
Chapter 8: Security
SECURITY
New users can only be added by users that have Administrator Access (or Admin Rights). The Enable Security
check box located in the Security > User Management window must be enabled.
Remember: (In order to add new users and assign user rights)
• must be logged in with Administrator Permission
and Enable Security check box must be enabled
NOTE: Only Administrators have access to the User Management dialog box.
Following is a list of all of the User Rights Options available to be granted to users, and their functions.
By default, Administrator and Service users are created with "password" as default password.
Security Control is enabled by checking the ENABLE SECURITY check box. The first time the enable security
option is selected it is necessary to close and reopen the EnerVista 650 Setup software to start working under
security management.
The bulk of the Cyber Security implementation consists of RBAC Cybersecurity mode, Centralized Authentication,
Remote Logging and System Hardening.
The relay’s cyber-security functionality shall be implemented to meet the NERC-CIPv6 and IEEE 1686 requirements.
And it is planned to offer Cyber security function in two flavors as ordering options:
· Basic Cyber Security
· Advanced Cyber Security
The main features for each of the CyberSecurity order option will be as follows:
Basic Cyber Security: The relay with Basic security option will support the following:
1. Device / Local Authentication
b. RBAC: 4 fixed roles: Administrator, Engineer, Operator & Viewer
c. Password complexity = Disabled by default (minimum password length: 4)
d. Default Password: “ChangeMe1#”
e. Flag for Failed authentication, User lockout for configurable period
f. Encrypted communication over ethernet
g. Inactivity Timeout
h. Security event storage on IED
i. Secure firmware download
j. Hardening
1)Enable / Disable communication ports
2)Enable / Disable protocols
8.2.2 Settings
8.2.2.1 Basic Security
The device’s Basic Security relay supports 4 fixed roles: Administrator, Engineer, Operator, Viewer.
Settings available under this path are divided in two main groups:
· Security Config
· Security Password
Setpoint > Product Setup > Security > Security Config
Setting Description Name Default Step Range
Value
This setting allows a user to login with a
Security Login Viewer N/A [Viewer-Administrator-Engineer-Operator]
specific role
This setting logs out the current user and
Security Logout No N/A [Yes - No]
logs it in as Viewer
This feature allows to bypass security -
Bypass Access DISABLED N/A [DISABLED – Local - HMI]
user authentication
This setting allows user to configure
password adhere to complexity rules or PW Complexity DISABLED N/A [DISABLED – ENABLED]
regarlar 4-20 characters password.
Access Lockout Acc Lockout 3 min [0 : 99]
Access Lockout Time is the duration in
Acc Lockout Time 3 min [0 : 9999]
minutes for lockout
Access Timeout HMI Acc Timeout HMI 5 min [2 : 999]
Access Timeout Other Acc Timeout Othr 5 min [2 : 999]
Require Password for Reset Key Req PW Reset Key ENABLED N/A [DISABLED – ENABLED]
Req PW D/T
Require Password for Date/Time change ENABLED N/A [DISABLED – ENABLED]
Change
Require Password for control Req PW Ctrl ENABLED N/A [DISABLED – ENABLED]
Bypass PW Rem
Bypass Password for remote control DISABLED N/A [DISABLED – ENABLED]
Ctrl
Req PW Setting
Require Password for Setting Group ENABLED N/A [DISABLED – ENABLED]
Group
Security Login: This setting allows a user to login with a specific role.
1) Whenever a new role is logged in, the user is prompted with a
display to enter password.
2) If the user enters the wrong password, "Authentication Failed!" message is
displayed.
3) If the maximum failed authentications occur an "Account Blocked!" message
is displayed.
4) The "Viewer" is the default choice and it does not require a password.
5) If the authentication is successful, EnerVista 650 Setup will show in
the status bar the logged user name.
Secrity Logout: This setting logs out the current user and logs it in as Viewer. If the user is
already a Viewer, this setting does nothing. When logging out, a switch to
Viewer role is performed.
Bypass Access: The "Bypass Access" feature allows to bypass security - user authentication.
Once this setting is other than "Disabled", then user gets Administrator access
rights on the configured interface. For example, if user configures it as "Local"
then no user authentication is needed for accessing the device over USB or
HMI.
Other possible option for 650 is to bypass authentication for "HMI" - where
user can view & modify all the settings, view actual values or execute
commands.
The use of this feature should be restricted only in commissioning phase
or when it is considered safe.
PW Complexity: When "PW complexity" is set to "Enabled", it allows user to configure password
strings which adhere to complexity rules defined in Password complexity
chapter. When the setting is configured as "Disabled" then user can change the
password to any string with minimum length of 4 characters maximum length of
20 characters.
For basic security IED, Password complexity is set to "Disabled" by default.
Acc Lockout: Access lockout is the number of failed authentications (default is 3 and
maximum is 99) before the device blocks subsequent authentication attempts
for the lockout period. A value of 0 shall mean Lockout is disabled.
Acc Lockout Time: Access lockout time is the duration in minutes for lockout. After configured
times of failed authentication, particular role gets locked-out for configured "Acc
Lockout Time". After this period, user will be allowed to login again for that role.
Acc Timeout HMI: If user is logged in through HMI then he can be inactive for the period
configured as "Acc Timeout HMI" before getting auto-logged out.
Acc Timeout Othr: Access Timeout Other is the time authorized user can be inactive, before
automatically getting logged out. This timeout shall apply to all users & roles,
independent of the communication channel (serial, Ethernet or USB) but not for
HMI users.
Req PW Reset Key: This setting is only available to the Administrator. It is used for the purpose of
bypassing security. If this setting is enabled and an alarm or trip occurs on the
relay, the Reset button is not available to the Viewer.
Req PW D/T Change: The date/time can be set by any role, if this setting is disabled. If this setting is
enabled the date/time can only be set by the Administrator and Engineer.
Req PW Ctrl: If this setting is disabled, Operator controls do not require a password. If this
setting is enabled, the password for users with access privilege is required.
Bypass PW Rem Ctrl: This setting is only applicable to Basic cybersecurity order code, it is disabled
by default. If it is enabled, then no password is required for the remote controls.
Req PW Setting Group: This setting is only applicable to Basic cybersecurity order code, it is
disabled by default. If it is enabled, then no password is required for the setting
groups.
Operator Pswd
f. If a user connected to the device as other than Administrator role, tries to select Change Passwords
option, then HMI as well as EnerVista 650 Setup will allow changing password for the user’s own account.
If a non-admin user tries to change other account password, then HMI as well as EnerVista 650 Setup will prohibit it.
The password rules validation shall be done only when password complexity is set to enabled. When the complexity
is enabled and user tries to modify the password, then it Will be nice to show password complexity rules. Once user
tries to save new password, make sure that the string adheres to all the password complexity rules. If any of the rule
is not met, then proper error message needs to be shown to user regarding which rule/s is/are not met.
8.2.2.2
8.2.2.3 Advanced security
In addition to Basic Security, Advanced security offers Server authentication & authorization, syslog capability,
Configurable user credentials.
8.2.2.3.1 Syslog:
Support for SysLog is only required in product variants supporting advanced security order-code.
The device shall support 2 Syslog servers for redundancy. The product shall always attempt to send security
events to the primary & Secondary SysLog server. The product shall communicate with the external SysLog servers
using UDP/IP .
PW Complexity: When "PW complexity" is set to "Enabled", it allows user to configure password
strings which adhere to complexity rules defined in Password complexity
chapter. When the setting is configured as "Disabled" then user can change the
password to any string with minimum length of 8 characters and maximum
length of 20 characters. For advanced security IED, Password complexity is set
to "Enabled" by default.
For advanced security relay, user can configure upto 10 configurable user accounts. As part of this, he can configure
a username (length can be upto 20 ASCII char), Password for the username (max length can be 20 ASCII char) &
assign a device supported user role (range : Administrator, Engineer, Operator, Viewer).
In advanced security option, “Administrator” is eligible to configure various accounts and is eligible to modify
passwords for all available accounts. Non-Admin user should be able to modify their own account password.
It is recommended to have more than one “Administrator” account.
R: Read
RW: Read/Write
X: No access
Non-Security settings RW RW R R
PLC RW RW R R
Output Simulation RW RW X X
IEC61850 settings RW RW R R
Commands
Date change RW RW X X
BKR related RW RW RW X
Clear records RW RW X X
File operations
Config File read R R R R
RBAC microservice is in charge of session management. Every login attempt will connect to the microservice and it
will allow or deny the login of the user.
In Basic Security, default connection is done as Viewer, without password requirement.
Once logged as Viewer, the user can change the role and login as Administrator, Operator or Engineer.
In Basic Security, once logged out from major roles, the connection comes back to Viewer role.
In case of Advanced Security, a username and password will be required. If the login is successful, the access level
will correspond to the role defined to this user.
The user cannot change its own role. So, in case of more rights needed, another different user with the
corresponding role should be logged in.
The maximum number of concurrent sessions is only one for all roles, except of Viewer role, which has the limit of 5
sessions.
There is a session timeout adjustable by settings. This timeout means that open sessions are automatically closed
if they remain inactive till the timer elapses. This inactivity timer defines the period that IED waits in idleness before a
logged in user will be automatically logged out.
There is a lockout period adjustable by settings. For each account, when a maximum number of failed login
attempts is reached, it is locked during the specified period. It doesn’t matter the interface the login comes from. The
account will be unlocked at the first successful login passed the lockout period.
If the Authentication Method setting is changed, the logged in user will be forced to logout.
The EnerVista 650 Setup shall check if the login was successful as follow:
8.2.4.2 Bypass
In Bypass mode, IED does not provide security, any user can login IED to access. IED does not validate user and
password. The bypass security feature provides an easier access, with no authentication and encryption for those
special situations when this is considered safe. Only the Administrator, can enable this feature
There are three modes for authentication bypass:
1)Disable – Will disable Bypass completely
2)HMI: will bypass authentication for front panel
3)Local: will bypass authentication for
·Front USB
·Serial Port (RS 485)
Only Administrator can change other user’s passwords. All device users can change their own passwords. For
password reset/recovery procedure the Administrator role will be required.
Viewer access level has no password associated in Basic Security.
In Advanced Security relay, all users need to enter username as well as password to get access privileges.
The default password for both Basic Security and Advanced Security relay is “ChangeMe1#”
IED will first try the server 1 up to the configured number of retries leaving request timeout between each request. If
after this point it still don’t have a valid answer from server 1, it switches to server 2 and repeats for up to the number
of configured retries again. If it maxes out on retries on the second server, it gives up entirely on Server
Authentication and fallback to device authentication (Only if Authentication Method Server and Device is selected). A
"RADIUS Server unavailable" security event is also logged under this condition.
IED will authenticate and authorize RADIUS users using the following authentication stack:
- Primary Radius if enabled (stop on invalid credential failure, continue all other failures)
- Secondary Radius if enabled (stop on invalid credential failure, continue all other failures)
The RADIUS implementation supports the following authentication protocols:
- PEAPv0 with inner authentication method MS-CHAPv2 (To support Microsoft NPS server)
- EAP-TTLS with inner authentication method PAP (To support RSA AM)
- PAP (unsecured, to support any RADIUS server)
When using PEAPv0 or EAP-TTLS-PAP the RADIUS implementation shall use CA certificate to establish the TLS
connection.
The EAP-TTLS RADIUS implementations are not required to support Client certificate authentication.
The RADIUS implementation will query the Role ID vendor attribute and establish the logged in user security context
with that role.
In case of Server Authentication mode but if the RADIUS server is not operational, IED will try Device Authentication.
Engineer: This role has almost same rights as “Administrator”, except security settings modification as well as some of the
commands & FW upload is not allowed.
Operator: The operator has access to read all settings as well as actual values. This role is also entitled to execute
commands and can also close or open breakers.
Viewer: Has read only access to all the device settings. This role will allow multiple concurrent access. This role will have no
download access to any files on the device.
At a time, only single non-Viewer user can connect to the device. Up-to 5 number of Viewers can connect to device
at given time.
8.2.5.2.1 Ensuring non-viewer user may always login
It is mandatory that one Modbus connection is always reserved for Administrator or non-Viewer user. This is to make
sure; a user can take immediate action/ give command when there is need.
The following will be implemented -
1)Only maximum of 4 Viewer/Observer connections are allowed.
2)Maximum 1 non-viewer connection
8.2.5.3 Modbus/SSH
The SSH server reside in the IED. It securely encrypts the Modbus commands and data between the EnerVista 650
Setup and itself using port forwarding. SSH 2.0 is supported.
The port forwarding feature is available only on TCP/IP frames. UDP is not supported. The SSH server on the
product runs on port 22.
The SSH server has a timeout for authentication and disconnect if the authentication has not been accepted within
the timeout period.
8.2.5.4 SFTP
The SFTP commands will be limited for a given period of time to avoid DOS attacks and also implement role based
access to the file. FW will validate the file before processing it.
User with “Administrator” role can configure this setting. Once the setting is configured to other than “Disabled”,
IED will allow communication with 3rd party SCADA application in plain text MODBUS over port 502. Also, for
configuration change, the relay IED shall register a security even to, show target message & alarm to indicate user.
When “MODBUS TCP” is configured to “Enabled”: then legitimate user can read or write over plain MODBUS
using port 502 on successful authentication.
When “MODBUS TCP” is configured to “Disabled”: the port 502 will be closed.
NOTE1: EnerVista 650 Setup configuration tool will always communicate with IED over SSH using port22.
Authent Failure X X When any authentication attenpt is failed, the event will
get recorded
Clear Transient X X
Clear transient records command was issued.
Pri RADIUS Active X The operand will get asserted when "Primary RADIUS
server" is being utilized by relay for remote
authentication
Prim RADIUS Unavailable X X The event will get generated by the relay when
configured Primary RADIUS server is not available or
not reachable for authentication
Sec RADIUS Active X The operand will get asserted when "Secondary
RADIUS server" is being utilized by relay for remote
authentication
Sec RADIUS Unavailable X X The event will get generated by the relay when
configured Secondary RADIUS server is not available
or not reachable for authentication
Prim Syslog Active ** X The operand will get asserted when the relay is
sending out syslog messages to syslog server
configured as "Primary Syslog server"
Prim Syslog Unavailable The event will get logged when the relay detects
X X
** unavailability of syslog server configured as "Primary
server"
Sec Syslog Active ** X The operand will get asserted when the relay is
sending out syslog messages to syslog server
configured as "Secondary Syslog server"
Sec Syslog Unavailable ** X X The event will get logged when the relay detects
unavailability of syslog server configured as secondary
server
Syslog Unavailable ** X The operand will get asserted when the relay detects
unavailability of any of the syslog server
BYPASS ACCESS ACTIVATED Critical (1) Bypass access has been activated
BYPASS ACCESS
Critical (1) Bypass access has been deactivated
DEACTIVATED
PRIM_SYSLOG_UNREACHABL SYSLOG server is unreachable. Origin: SYSLOG server IP
Critical (2)
E address and port number
SYSLOG server is unreachable. Origin: SYSLOG server IP
SEC_SYSLOG_UNREACHABLE Critical (2)
address and port number
MODBUS TCP Enabled Warning (4) Port 502 has been opened for Read/Write
Security_Events.CSV file stores security events information. A total of minimum 1024 events are stored in a circular
buffer in non-volatile memory. Once the file reaches its max limit, oldest event Will get over-written by newest
security event.
FORMAT: Following information Will be supported & stored in events file for each event: Event Number, Data/Time,
Username, IP Address, Role, Activity value
The timestamp is the UTC time.
This file will be stored on IED & will be accessible from EnerVista 650 Setup for user with “Administrator” role. For
Basic security, this is the only file to give security audit information to user. And this file will be useful for advanced
security user if in case syslog is not configured or non-functional due to some issue.
Serial Protocols (only supports one protocol on serial ports) can be disabled by disabling the serial port.
According to the product hardening requirement these are the settings needed:
Enable/Disable physical ports:
Product Setup > Function This existing setting it Enum value: 1: Enabled
Communication is used to disable/
0: Disabled
settings > enable the Ethernet
Network(Ethernet) > port E 1: Enabled
Ethernet E
Product Setup > Communication Function This existing Enum value: 0: Disabled
settings > SNTP > SNTP Client 1 setting it is used
0: Disabled
to disable/enable
the SNTP 1: Unicast
protocol Client 1 2: Broadcast
3: Anycast
Product Setup > Communication Function This existing Enum value: 0: Disabled
settings > SNTP > SNTP Client 2 setting it is used
0: Disabled
to disable/enable
the SNTP 1: Unicast
protocol Client 2 2: Broadcast
3: Anycast
Product Setup > Communication PTP This existing Enum value: 0: Disabled
settings >PTP-1588 Function setting it is used
0: Disabled
to disable/enable
the PTP protocol 1: Enabled
Product Setup > Communication Function This existing Enum value: 0: Disabled
settings >Web Sever setting it is used
0: Disabled
to disable/enable
the Web Server 1: Enabled
Product Setup > Communication Function This existing Enum value: 1: Enabled
settings >IEC61850 MMS setting it is used
0: Disabled
to disable/enable
the IEC61850 1: Enabled
MMS Server
Product Setup > Communication Function This existing Enum value: 1: Enabled
settings >SFTP/SSH setting it is used
0: Disabled
to disable/enable
the SFTP/SSH 1: Enabled
protocol
Product Setup > Time Settings IRIG-B This existing Enum value: 0: Disabled
Function setting it is used
0: Disabled
to disable/enable
the IRIG-B 1: Enabled
Product Setup > Communication Function This existing Enum value: 0: Disabled
settings >TFTP setting it is used
0: Disabled
to disable/enable
the TFTP 1: Enabled
protocol
Product Setup > Security >Server Config RADIUS Primary Radius 0 to 255 0
IP Prm IP
Octect1
If both IP’s are
0.0.0.0 the radius
will be disabled
RADIUS 0 to 255 0
IP Prm
Octect2
RADIUS 0 to 255 0
IP Prm
Octect3
RADIUS 0 to 255 0
IP Prm
Octect4
RADIUS 0 to 255 0
IP Sec
Octect1
RADIUS 0 to 255 0
IP Sec
Octect2
RADIUS 0 to 255 0
IP Sec
Octect3
RADIUS 0 to 255 0
IP Sec
Octect4
Product Setup > Security >Syslog IP Prim If IP is 0.0.0.0 the 0 to 255 0
Octet1 syslog will be
disabled
IP Prim 0 to 255 0
Octet2
IP Prim 0 to 255 0
Octet3
IP Prim 0 to 255 0
Octet4
IP Sec 0 to 255 0
Octet1
IP Sec 0 to 255 0
Octet2
IP Sec 0 to 255 0
Octet3
IP Sec 0 to 255 0
Octet4
2 syslog servers are supported in the configuration for redundancy. The IED will try each in sequence until one
respond
This section explains how to upgrade the F650 boot code and firmware for version below 7.00.
BEFORE PERFORMING THE UPGRADE PROCEDURE CHECK THAT BOOT AND FIRMWARE VERSION
NOTICE MATCH.
The boot code and firmware versions can be seen in the relay main screen: The relay firmware version appears after
the text “F650“(5.70 in Figure 9-1: Main screen) with the boot program version (6.00 in Figure 9-1: Main screen)
followed by “GENERAL ELECTRIC”, the relay model and the default front RS232/USB port communication
parameters.
NOTICE
A STEP LIST SUMMARY that allows the user to control the upgrading process is included at the end of this
section. It is necessary to read paragraphs 1 to 4 of chapter 9 of manual GEK-106310 before accomplishing the
F650 UPGRADE PROCEDURE.
Be aware that boot program and firmware upgrades erase all data contained in the relay, thus it is advisable to
save all data, oscillography, events, settings and configuration files before proceeding.
For upgrading firmware versions lower than 3.20 or upgrading bootware, be aware to calibrate the unit offset, after
upgrading it, in Communication > Calibration > Offset Calibration. No analog currents nor analog voltages
must be injected in the unit during this process.
2. Relay IP Address - An IP address must be assigned to the relay in the Ethernet parameters via HMI at
Product Setup > Communication > Ethernet > Ethernet1 menu, or via EnerVista 650 Setup software at
Setpoint > Product Setup > Communication Settings > Network (Ethernet) 1 as shown in the table below:
3. PC IP Address - In case the boot code has been previously updated to the relay (section 9.2), the IP address
and other parameters already assigned in the process are:
IP Address:192.168.37.177
Netmask:255.255.255.0
Gateway:192.168.37.10
IP Address:192.168.37.xxx
Netmask:255.255.255.0
Gateway:192.168.37.10 (if desired)
Where XXX is a number between 0 and 255 that is not assigned to any other device to avoid collisions.
• According to the model number of the relay, to enable the 10/100 BASE TX-CABLE option in the relay communication
board, a specific jumper in this board must be changed. See detailed instructions in paragraph 3.4.3 of Instruction
Manual GEK-106310AE.
• IP address, netmask, gateway are correct and match the parameters used in the computer to perform the procedure.
See table 9.1 (on this chapter) of Manual GEK-106310AE COMMUNICATION PARAMETERS.
Boot code upgrade is performed using EnerVista 650 Setup, and the most recent version of EnerVista 650 setup
software should be used. It is required that no active communication is currently established between the program
and the relay, and that no configuration files are open.
During the boot code upgrading process, all the data stored in the relay is lost. Save all calibration, settings,
oscillography, etc. from the relay before starting the upgrade.
If calibration files were saved click Yes, otherwise click No to cancel the upgrade process and save first the
calibration files according to section 4.1.11.
10. Parameters already set in step 5 are operative during serial communications. If they have not been previously
set a pop up window prompts for the serial COM port to be used during upgrading.
11. During the upgrade, the system shows the following message indicating the procedure to be followed.
If you click Yes, the next window allows you to choose the Network adapter for your Ethernet connection to the relay.
12. After selecting the Network adapter, a window to choose a temporary IP address is shown. It is advisable to set
the same IP address that is going to be used later in the relay for Ethernet connection.
13. After entering the temporary IP Address, the next new window requires the bootware file retrieved from
https://www.gevernova.com/grid-solutions and previously stored someplace in the PC.
15. Then the program shows a message requiring switch OFF and ON the relay while the progress bar is in course,
to start the upgrading process.
16. It is important to switch the Relay OFF and ON again during the time shown by the progress bar; in case this
time expires, the program offers the option to continue with the process or to postpone, verify the correct RS232
connections and try again later. Notice that the serial COM PORT used in the boot upgrade procedure is the one
selected in step 4 above.
If the relay gets stuck during the upgrading process after switching OFF and ON the relay, giving error message
shown, it is due to no serial communication via the front RS232 port. Check the serial cable and serial settings
connection. At this point the relay will not be upgraded.
After switching it OFF and ON it will continue working with the former firmware and bootware versions.
17. After switching the relay OFF and ON, if the serial communication between EnerVista 650 Setup and the relay is
correct the program shows the following message:
18. Click Yes to start the process, beginning with the relay flash memory deletion.
At this point all the information stored in the relay is lost. Until now, no important change has been made to the relay,
the boot memory upgrading process has just been prepared.
This process can take several minutes, during which a progress bar is displayed.
This error may be due to no communication via the Ethernet port. At this point serial communications work properly,
the relay flash memory has been erased, and the upgrade procedure must be completed to start working with the
unit. If the procedure is not completed, the HMI shows the message "OS Loading..." and the relay does not start up.
In this case refer to step 4 above
If all points from step 4 are correct but the problem persists:
Disable and Enable the Ethernet connection while the files are being sent (during the “Sending file...” message -
previous figure). To do this, in Windows OS go to Startup > Control Panel > Network Connection > Local Network,
right-click and select Disable. Now the Local Network status Icon is shown as Disabled. In the same screen right-click
Local Network, select Enable, and wait until Enabled status is shown.
20. Once the memory has been erased and the files upgraded in the relay, the parameters for the Ethernet
communications must be set. The requested values are the IP address and the gateway.
These values should match the LAN structure where the relay will be connected.
The relay IP address should have the first three octets corresponding with the gateway and the last octet must be a
free IP address reserved to the relay to avoid possible collisions with other devices.
The gateway must be the one used in the LAN structure connecting the relay
21. After assigning the Ethernet parameters, the upgrade of the boot code is complete and successful.
22. A window is displayed with the message: Setting Default IP address, followed by:
After boot code upgrade, the equipment firmware must also be upgraded.
9.1.3.1 Introduction
1. Save relay settings and configuration to a file before proceeding, as they will be lost during upgrade.
2. Save calibration settings to a file for firmware revisions lower than 1.50, before upgrading the F650 to a new
firmware version.
3. For firmware revision higher than 1.50 when only upgrading the firmware (no bootware upgrade), the calibration
files are not modified and do not need to be saved.
4. Special care should be taken when the boot code has been previously upgraded: all data (including calibration
settings) is lost.
5. In case of errors during the firmware upgrade process, repeat the entire process as many times as necessary.
This is possible thanks to an independent boot memory (bootcode).
6. A pure firmware upgrade process should use the EnerVista 650 Setup software and Ethernet connection (Port
ETH_1 or ETH2) via a Cross-Over RJ45 Ethernet cable.
2. Select Device FW Upgrade FW version <7.00 and click [...]. to browse for the new firmware file.
3. Once the new firmware file has been selected, click Upgrade to continue.
4. Fill in the device IP address, serial number, and order code as needed. (The order code is not required for
firmware versions below 1.70).
5. If the relay is not an enhanced model or one with control functionality, click Upgrade Firmware to continue the
process (see the following figure).
At this point, proceeding with the upgrade erases all data stored in the equipment, including the calibration settings in
firmware versions below 1.50. It is necessary to save all settings to a file now if you have not already done so.
Click Yes to continue. A message is displayed indicating that a local network reboot is necessary (see following figure).
Proceed as follows:
• In the Windows Control Panel (Start > Control Panel), navigate to Network Connection > Local Network. Right-click
and select Disable. Confirm that the Local Network status is now Disabled. Restart the local network in the same
screen (right-click and select Enable). Wait until the local network status is Enabled before continuing.
• Click Upgrade Firmware to continue the process (as shown).
6. When upgrading models with Enhanced protection or control functionality (see model selection), the upgrade
program requires a password to continue (as shown).
For a model with specialized functionality and a password requirement, contact GE Multilin.
7. Once the upgrade parameters have been entered, click OK. When communication has been established, the
program shows a message requesting a reboot of the 650 (turn the relay off and then back on) to continue with
the upgrade process.
8. Once the relay has been rebooted, you are prompted to select the new firmware upgrade file (update.txt).
The upgrade files, including update.txt, can be obtained online (https://www.gevernova.com/grid-solutions) or from
the Technical Service Dept. at any GE Multilin facility. Save the files in a directory in the root drive or the PC desktop.
Extract any zipped files.
Browse to the "update.txt" file and click Open.
During the upgrade process, the program displays the files that are being upgraded.
12. When the file transfer is finished, a message is displayed indicating that it is necessary to wait before resetting
the unit, in order to start working with the new firmware version in the relay (figure below).
13. When the whole process has finished a message is displayed asking to switch the F650 on and off (figure
below).
14. Click OK (Aceptar). At this point, the firmware upgrade is finished and the relay can be powered OFF and ON to
check that the firmware has been upgraded properly.
When upgrading the firmware the entire settings and relay configuration are reset to factory default values.
Then the User is committed to download the settings, configuration and logic files to the relay in order to get
it fully operative.
Calibration settings and configuration must be reloaded to the relay the relay.
To recover and download the different files to the relay go to EnerVista 650 Setup and at the top menu bar choose:
• Communication > Calibration > Set Calibration Files: to restore calibration settings, if necessary.
• File > Config File (*.650) Converter: to convert the setting and configuration file *.650 for the relay (if it was in a
previous version format).
• File > Send Info to Relay: to send the new settings and configuration file to the unit.
(*) The boot code upgrade must be performed using a crossed copper cable (RJ45) connected to the PC. It is not
necessary to modify the internal fiber/cable switch, as the upgrade is carried out at 10 Mb/s, and thus there is no
cable/fiber conflict.This does not apply to the firmware upgrade, which can be performed either with the Ethernet
fiber connection, or with the cable connection.
Note: See chapter 13 F650 TROUBLESHOOTING GUIDE if there is any problem during the upgrade process.
This section explains how to upgrade the F650 firmware code for version V7.00 or higher.
It is mandatory to maintain version compatibility between firmware and boot code in the upgrade procedure,
otherwise the relay will not start after upgrading.
BEFORE PERFORMING THE UPGRADE PROCEDURE CHECK THAT BOOT AND FIRMWARE VERSION
MATCH.
2. Relay IP Address - It must be assigned a IP address to the relay in the Ethernet parameters via HMI at
Product Setup > Communication > Ethernet > Ethernet E, A or B menu or via EnerVista 650 Setup at Setpoint >
Product Setup > Communication Settings > Network (Ethernet) E, A or B as shown in the Table below.
Table 9-2: Ethernet parameters
The IP address and other parameters already assigned in the process are:
IP Address:192.168.37.177
Netmask:255.255.255.0
Gateway:192.168.37.10
Note: To assure that the configuration is correctly setup it is possible to perform a ping command from the PC.
IP Address:192.168.37.xxx
Netmask:255.255.255.0
Where XXX is a number between 0 and 255 that is not assigned to any other device to avoid collisions.
9.2.2.1 Introduction
1. The relay settings and configuration will be lost, so it is advisable to save them to a file.
2. In case of error during the firmware upgrading process, the user can repeat the whole process as many times as
necessary.
3. Firmware upgrading process should be done using the EnerVista 650 Setup software and Ethernet connection
(Port ETH_E, A or B) via Cross-Over RJ45 Ethernet cable or Fiber Optic cable (depending on order code
option).
Note that ETH_A and ETH_B ports cannot be used if PRP configuration is selected.
1. Once the communication with the relay through Ethernet connection has been verified, enter the EnerVista 650
Setup program, select Communication and the Upgrade Relay option on the top menu bar.
2. Select Device Upgrade FW&Boot>=7.00 and click […] to browse for the file. The appropriate *.SFD file should
be obtained from https://www.gevernova.com/grid-solutions or from The Technical Service Dept. at any GE
Multilin facility. The file must be saved in the root drive or in the desktop of the PC. Choose the corresponding
firmware file for upgrading the device.
3. Enter communication parameters for the relay being upgraded and click Upgrade.
4. If the IP address is correctly set, then the message "*.SFD Sending file" is displayed. A sending file status bar
shows the progress of the upgrade.
5. If the file is not sent successfully, the following message box is displayed.
7. When the flashing upgrade process finishes, a message is displayed requesting a relay reboot.
Calibration settings and configuration must be loaded to the relay once the upgrade process has finished.
To recover and download the different files to the relay use EnerVista 650 Setup and at the top menu bar choose:
• Communication > Calibration > Set Calibration Files: to restore in the relay the calibration settings if necessary.
• File > Config File (*.650) Converter: to convert the setting and configuration file *.650 for the relay (if it was in a
previous version format).
• File > Send Info to Relay: to send the new settings and configuration file to the unit.
1. To reach the window where the password is requested, the user must be communicating with the relay (ONLINE
MODE). On the File menu the following submenu is available (for firmware versions above 7.00):
2. Click Order Code on the menu and the following window is displayed:
3. This window only allows changing the last digit, which refers to supported communications protocols options.
Click Send:
4. The users must contact GE Multilin and provide the following parameters in their order:
– Unit serial number
– Current model option (before memory upgrade)
– Desired model option (after memory upgrade)
– Unit MAC address (available in the identification label)
5. Once the password is obtained, enter it when prompted.Tthe following messages appear if the password is
correct.:
6. After the successful operation, the SEND button is disabled. It is not allowed to make another change from here,
so it can be seen what changes have been made. The new order code appears on the status bar.
NOTICE
1. See chapter 13 F650 trouble shooting guide, if there is any problem during the upgrading process.
2. For the relay firmware upgraded to version 9.00 or higher, it can not be downgraded back to the versions below
9.00.
COMMISSIONING
Verify that the relay has not suffered any damage during transportation, and that all screws are correctly fixed, and
all relay terminal boards are in good condition.
Verify that the information shown on the relay front plate corresponds to the data shown on the display, and to the
requested relay model.
Display information:
Firmware version
GENERAL ELECTRIC
F650XXXXXXXXX Model
19200N81 MODBUS:254
The Relay Out Of Service setting is configured in Setpoint > System Setup > Miscellaneous. The unit also has an
Out of Service status that is configured in Relay configuration > Protection elements. When active, these states
stop all changes to PLC equations and functions, including changes to the input/output boards, so if there is a
change in any input or output the unit will not show this change until it has returned to ready mode. For example if an
output is closed and the unit goes to the Out of Service state, the output is kept closed even if the state that closed
it changes and would otherwise open the output. When the unit goes out of the Out of Service state, the output is
then opened.
When the Out of Service status goes to ON, or the setting has been changed to Enabled, the ready LED also
changes to red. Be careful if ready LED is linked to an output, because the output will not change its state. To set
outputs to ready state see factory default Logic & Configuration in the detailed manual. Take notice that, in the
default configuration, the general setting out of service is enabled, so it is necessary to change to disabled to start
working with the unit
The following figure shows the flow chart of these states
The ammeters and chronometers used for testing the pickup current and relay operation time must be calibrated and
their accuracy must be better than the relay’s. The power supply used in the tests must remain stable, mainly in the
levels near the operation thresholds.
It is important to point out that the accuracy with which the test is performed depends on the network and on the
instruments used. Functional tests performed with unsuitable power supply network and instruments are useful to
check that the relay operates properly and therefore its operating characteristics are verified in an approximate
manner. However, if the relay would be calibrated in these conditions, its operational characteristics would be
outside the tolerance range values.
The following sections detail the list of tests for verifying the complete relay functionality.
10.5 Indicators
Feed the relay and verify that when commanding a LED reset operation, all LED indicators light up and they are
turned off when pressing the ESC key for more than 3 seconds.
Feed the relay with the minimum and maximum voltage. For each voltage value, verify that the alarm relay is
activated when there is voltage, and it is deactivated when there is no feed. If the power supply source incorporates
AC feed, this test is also performed for VAC.
If the relay incorporates a redundant power supply, these tests shall be performed on both power supplies.
Voltage values to be applied are the ones indicated below according to the relay model:
10.7 Communications
Verify that available communication ports allow communication with the relay.
Ports to be checked are as follows:
Front:RS232
Rear:2 x RS485, 2 x Fiber Optic - Serial, 2 x Fiber Optic - Ethernet, 1 x RJ45 - Ethernet.
A computer with EnerVista 650 Setup software and an appropriate connector must be used.
10.8.1 Voltages
Apply the following voltage and frequency values to the relay:
Verify that the relay measures the values with an error of ±1% of the applied value from 10V to 208V.
Verify that the relay measures the values with an error lower than ±0.5% of the test value or ± 10 mA, whichever is
greater, for phases and ground.
Verify that the relay measures the values with an error lower than ±1.5% of the test value or ± 1 mA, whichever is
greater, for sensitive ground (SG).
Percent of Load-to-Trip
The relevant actual values displays are shown below:
Actual > Metering > Primary Values > Current > % of Load-to-trip
Note Percent of load-to-trip is calculated from the phase with the highest current reading. It is the ratio of this current
to the lowest pickup setting among the phase time and instantaneous overcurrent protection features. If all of these
features are disabled, the value displayed is “0”.
- Inject current of various values into Phase A.
- Verify that percent load-to-trip is calculated as the correct
percentage of the most sensitive operational Phase Overcurrent
element and displayed.
- Repeat for phases B and C.
With the indicated voltage and current values, verify that the power measure corresponds to expected values
indicated in the following table:
Maximum admissible error is ± 1% of the test value for P and Q, and 0.02 for cosj.
10.8.4 Frequency
Frequency measure on channel VII (terminals A7-A8):
Apply 50 Vac at 50 Hz on channel VII. Maximum admissible error:± 10 mHz.
Apply 50 Vac at 60 Hz on channel VII. Maximum admissible error: ± 12 mHz.
Results:
Test settings for mixed board (type 1:16 inputs and 8 outputs):
The inputs test is completed by groups of 8 inputs, as this type of board has 2 groups of 8 inputs with the same
common. For the first 8 inputs, the voltage threshold setting is determined by Voltage Threshold A. For the next 8
inputs, the setting is Voltage Threshold B. Inputs (or contact converters, CC1 – CC16) must also be set to
POSITIVE.
Test settings for mixed board (type 2: 8 digital inputs, 4 blocks for supervision and 8 outputs):
The inputs test is completed by groups of 4 inputs, as this type of board has 2 groups of 4 inputs with the same
common. For the first 4 inputs, the voltage threshold setting is determined by Voltage Threshold A. For the next 4
inputs, the setting is Voltage Threshold B. Inputs (or contact converters, CC1 – CC8) must also be set to POSITIVE.
If the relay incorporates more input modules, these tests must also be applied to them.
Coil 2:
Apply 19 Vdc to both 52/a (terminals F15-F16) and 52/b (terminals F17-F18)”Coil 2” circuit supervision inputs and verify
that they are activated.
Apply -19 Vdc to both 52/a (terminals F15-F16) and 52/b (terminals F17-F18)”Coil 2” circuit supervision inputs and
verify that they are activated.
Remove voltage from both inputs and verify that it takes them 500 ms to change state (deactivate).
Make circulate a current of 500 mA through the contact in series with the sensing terminal.
Send an opening command and verify that the contact does not open.
Interrupt current and check that the contact is released.
500
I
Repeat the test for the other latched contact (F34-F36).
Phase Connections
Current
IA B1-B2
IB B3-B4
IC B5-B6
IG B9-B10
ISG B11-B12
Voltage
VI A5-A6
VII A7-A8
VIII A9-A10
VX A11-A12
50PH/67P IA 2A 0º VIII 60 V 0º NO
60 V 180º YES
IB 2A 0º VI 60 V 0º NO
60 V 180º YES
IC 2A 0º VII 60 V 0º NO
60 V 180º YES
IB 0A 0º VII 0V 0º
IC 0A 0º VIII 0V 0º
VIII 0º
VIII 0V 0º
PHASE UV (27P)
Function ENABLED
Mode PHASE-GROUND
Pickup Level 50 V
Curve DEFINITE TIME
Delay 2.00 sec
Minimum Voltage 30 V
Logic ANY PHASE
Supervised by 52 DISABLED
Apply voltage as indicated on the table over the undervoltage setting level and verify that the relay does not trip.
Decrease voltage level gradually and verify that the relay trips for the set voltage (with an admissible error of 5%).
AUXILIARY UV (27X)
Function ENABLED
Pickup Level 50 V
Curve DEFINITE TIME
Delay 2.00 sec
Apply voltage as indicated on the table over the undervoltage setting level and verify that the relay does not trip.
Decrease voltage level gradually and verify that the relay trips for the set voltage (with an admissible error of 5%).
Element Phase Pickup Level Trip Delay Applied Voltage (V) Tripping time (s)
(volts) (seconds) Expected Admissible
59P VII 120 2 114 NO TRIP NA
132 2 [1.9–2.1]
132 2 [1.9 – 2.1]
GENERAL SETTINGS
Auxiliary Voltage VX
AUXILIARY OV (59P)
Function ENABLED
Pickup Level 120 V
Trip Delay 2.00
Reset Delay 0.00
Logic ANY PHASE
Apply voltage as indicated on the table under the overvoltage setting level and verify that the relay does not trip.
Verify that the relay trips for the set voltage (with an admissible error of 5%).
Element Input Pickup Level Trip Delay Applied Voltage (V) Tripping time (s)
(volts) (seconds) Expected Admissible
59X VX 120 2 114 NO TRIP NA
132 2 [1.9–2.1]
132 2 [1.9 – 2.1]
GENERAL SETTINGS
Auxiliary Voltage VN
Apply voltage as indicated on the table under the overvoltage setting level and verify that the relay does not trip.
Verify that the relay trips for the set voltage (with an admissible error of 5%).
Elements Input Pickup Level Trip Delay Applied Voltage (V) Tripping time (s)
(volts) (seconds) Expected Admissible
59NH/59NL VX 120 2 114 NO TRIP NA
132 2 [1.9–2.1]
132 2 [1.9 – 2.1]
This element can also be tested by applying only phase voltages. For this purpose, it is necessary to set Auxiliary
Voltage = VX. In this condition, Vn voltage is calculated as a sum of the phase voltages.
Apply voltage as indicated on the table under the overvoltage setting level and verify that the relay does not trip.
Verify that the relay trips for the set voltage (with an admissible error of 5%).
NOTE: All angles mentioned on the tables are delay angles, where a balanced ABC system would be composed by:
VI 65 0º
VII 65 120º
VIII 65 240º
GENERAL SETTINGS
Nominal Frequency 50 Hz
ELEMENT SETTINGS
FREQUENCY (81) 81U 81O
Function ENABLED ENABLED
Pickup Level 47.50 Hz 52.50 Hz
Trip Delay 2.00 sec 2.00 sec
Reset Delay 0.00 sec 0.00 sec
Minimum Voltage 30 V 30 V
Apply voltage as indicated on the table, modifying frequency from the maximum threshold (48 Hz) to the minimum
(46 Hz) for 81U, and from the minimum (52 Hz) to the maximum (54 Hz) for 81O, in steps of 10 mHz.
Verify that the relay trips at the set frequency in the corresponding element with an error of 3% ó ±50 mHz.
Apply a voltage that is lower than the “Minimum Voltage” setting, with a frequency under (81U) or over (81O) the
setting, and verify that the relay does not trip.
Elements Phase Pickup Level (Hz) Trip Delay Applied Voltage Frequency Tripping Time (s)
(seconds) (V) Thresholds Expected Admissible
81U VII 47.5 2 80 48 Hz No trip NA
46 Hz 2 [1.9 -2.1]
25 46 Hz No trip NA
81 O VII 52.5 2 80 52 Hz No trip NA
54 Hz 2 [1.9 –2.1]
25 54 Hz No trip NA
Set the relay to trip by 50PH, and configure the signals necessary to test the 79 element:
Configure one output as AR RECLOSE
Configure the AR INITIATE signal with the 50PH trip
Configure the AR LEVEL BLOCK signal with a digital input
Configure the AR CONDS INPUT with the digital signal desired
50PH Settings
Function ENABLED
Input RMS
Pickup Level 3A
Trip Delay 0.00 s
Reset Delay 0.00 s
Reclosing Cycle
Nº shot Expected time Admissible time
1 2.1 sec [1.8 – 2.3]
2 4.1 sec [3.8 – 4.3]
3 6.1 sec [5.8 – 6.3]
4 8.1 sec [7.8 – 8.3]
Rated Current (A) Applied Current (A) Times of set tap Operation time (s)
4.0 2 48.5 - 53.6
5 10.0 5 7.06 - 7.80
20.0 10 1.77 - 1.95
After each measuring, the thermal element must be reset to zero in order to start the next test at a zero thermal
status condition.
Repeat the test selecting a time constant t1 of 60 minutes. Verify that the operation time is within the range described
on the following table:
Rated Current (A) Applied Current (A) Times of set tap Operation time (s)
4.0 2 960 - 1072
5 10.0 5 141 - 156
20.0 10 35.4 - 39
After each measuring, the thermal element must be reset to zero in order to start the next test at a zero thermal
status condition.
APPLICATION EXAMPLES
Click ON key.
Ethernet LAN (10/100 Base T rear port of the relay)
In the Laptop choose My PC-Control Panel-Network-Protocols-Protocol TCP/IP-Advance and set in IP Address screen
the following:
IP Address 192.168.37.126
Netmask 255.255.255.0
Sequence
Action Setting Action
---- IP Address OCT 1 Set to 192
Move rotating knob clockwise IP Address OCT 2 Set to 168
Move rotating knob clockwise IP Address OCT 3 Set to 37
Move rotating knob clockwise IP Address OCT 4 Set to 125
Move rotating knob clockwise Netmask OCT 2 Set to 255
Move rotating knob clockwise Netmask OCT 3 Set to 255
Move rotating knob clockwise Netmask OCT 4 Set to 0
Move rotating knob clockwise Netway IP OCT 1 Leave default setting without any change
Move rotating knob clockwise Netway IP OCT 2 Leave default setting without any change
Move rotating knob clockwise Netway IP OCT 3 Leave default setting without any change
Move rotating knob clockwise Netway IP OCT 4 Leave default setting without any change
Move rotating knob clockwise Press INTRO Press enter to validate settings
Under
SETPOINT PROTECTION ELEMENTS PHASE CURRENT PHASE TOC HIGH PHASE TOC HIGH 1
Name Value
Function Enabled
Input Phasor DFT
Pickup Level 5.0 A
Curve IEC Curve A
TD Multiplier 0.1
Reset Instantaneous
Voltage Restraint Disabled
Under
SETPOINT CONTROL ELEMENTS INPUTS/OUTPUTS BOARD F
Name Value
Output Logic_00_00 Positive
Output Type_00_00 Latch
Under
SETPOINT RELAY CONFIGURATION OUTPUTS
Select Name Source OR
Contact Output Operate 00 (Board F) C Output Oper_00_00 Press for Logic
Phase TOC A Op
Phase TOC B Op
Phase TOC C Op
Contact Output Reset 00 (Board F) C Output Reset_00_00 Operation bit 000
Under
SETPOINT RELAY CONFIGURATION LEDS
Select Name Source
Led 5 C Output Op 00 C Output_00_00
Under
SETPOINT RELAY CONFIGURATION OPERATIONS
Select Operation 0
Command Text Reset C Output 00
Interlock Type None
Interlocks ---
Final State Type None
Final States ---
Frontal Key F1
Contact Input None
Virtual Output None
Time Out 500 (default)
MMI ---
Com1 ---
Com 2 ---
ETH-Master 1 ---
ETH Master 2 ---
ETH Master 3 ---
ETH Master 4 ---
Under
SETPOINT RELAY CONFIGURATION OSCILLOGRAPHY
Select Name Source
Digital Channel 1 C Output Op_00_00 C Output Oper_00_00
Digital Channel 2 C Output_00_00 C Output_00_00
11.1.4 Test
Apply 7.5 A in phase A (terminals B1-B2) until contact 00 on Board F operates (terminals F19-F21 should be and remain
closed), and LED 5 should be lit. Check that operating time is in the order of 1.7 seconds.
Remove current from terminals B1-B2
Press pushbutton F1 and check that contact 00 on Board F has been open.
Check that LED 5 in the front of the relay has been turned off.
Repeat the process for phase B (terminals B3-B4) and for phase C (terminals B5-B6)
Under Actual Waveform Capture menu retrieve the last oscillography recording stored, open it using GE_OSC program
and check that the two digital signals as well as the current signal were kept.
11.2.1 Description
The purpose of this exercise is to introduce the F650 User about the way to set a protection scheme including:
Trip operation of a phase time overcurrent protection.
Two reclosing shots with successful fault clearing.
Synchronism check action to verify two ends voltage conditions previous to perform each reclosing action.
Name Value
Number of Switchgear 1
Under
SETPOINT INPUTS/OUTPUTS CONTACT I/O BOARD F
Name Value
Output Logic_00_00 Positive
Voltage Threshold B_00 80V
Debounce Time B_00 10 ms
Input Type_00_00 (CC1) Positive
Delay Input Time_00_00 (CC1) 0 ms
Output Type_00_00 Normal
Pulse Output Time_00_00 500 ms
Under
SETPOINT RELAY CONFIGURATION PROTECTION ELEMENTS
Select Source OR
AR Initiate Press for Logic
Phase TOC A Op
Phase TOC B Op
Phase TOC C Op
AR Conds Input Sync Close Perm
Name Value
Function Enabled
Max. Number of shots 2
Dead Time 1 2.0s
Dead Time 2 4.0s
Dead Time 3 ---
Dead Time 4 ---
Reclaim Time 0.05s
Condition Permission Enabled
Hold Time 0.1s
Reset Time 1.9s
Name Value
Function Enabled
Dead Bus Level 10V
Live Bus Level 50V
Dead Line Level 10V
Live Line Level 50V
Max. Volt Difference 10
Max. Angle Difference 10º
Max. Freq. Difference 20mHz
Breaker Closing Time 0.07s
DL-DB Function Disabled
LL-DB Function Disabled
DL-LB Function Disabled
The holding time for reclosing conditions can be very low since the processor internal time to check them is
instantaneously if they are present at this moment. Depending in the application reclosing conditions might come later
especially when commands are sent from dispatching center. If does then this timing must be set properly.
The F650 trip contact over-travel is the time the contact remains closed for some definite time to assure the tripping action
of the breaker, specially in CB’s with large tripping times (bulk or other CB’s). This time delay has been set in group
SETPOINT CONTROL ELEMENTS INPUTS/OUTPUTS BOARD F
To test the reclosing scheme one current and two voltages signals equipment with phase and frequency shifting capability
must be used. The current source must be switched OFF and ON in the time ranges described in the scheme
11.3.2 Procedure
Set the following values:
Under
SETPOINT CONTROL ELEMENTS Þ INPUTS/OUTPUTS BOARD F
Name Value
Output Logic_00_00 Positive
Output Type_00_00 Latch
Pulse Output Time 10000ms *
* This setting is non-relevant since it applies only when “pulse” type is chosen
Under
SETPOINT RELAY CONFIGURATION OUTPUTS
Under
SETPOINT RELAY CONFIGURATION LEDS
Under
SETPOINT RELAY CONFIGURATION OPERATIONS
Select Operation 0
Command Text Close C_Output_00_00
Interlock Type None
Interlocks ---
Final State Type None
Final States ---
Frontal Key F2
Contact Input None
Virtual Output None
Time Out 500 (default)
MMI ---
Com1 ---
Com 2 ---
ETH-Master 1 ---
ETH Master 2 ---
ETH Master 3 ---
ETH Master 4 ---
Select Operation 1
Command Text Reset C_Output_00_00
Interlock Type None
Interlocks ---
Final State Type None
Final States ---
Frontal Key F1
Contact Input None
Virtual Output None
Time Out 500 (default)
MMI ---
Com1 ---
Com 2 ---
ETH-Master 1 ---
ETH Master 2 ---
ETH Master 3 ---
ETH Master 4 ---
11.3.3 Test
In the main front screen press F2 key.
A message showing “Press Enter to Confirm Key ®F2¬” is displayed.
Press Enter.
Check that contact_00_00 (board F) has been closed.
Check that the front LED 14th is lit.
In the main front screen press F1 key.
A message showing “Press Enter to Confirm Key ®F1¬” is displayed.
Press Enter.
Check that contact_00_00 (board F) has been opened.
Check that the front LED 14th has been switched off
12.1 Communications
Q1. Does the F650 support DNP and ModBus over the Ethernet port?
A1. F650 units support both protocols over both the asynchronous serial ports and the Ethernet LAN synchronous port
using TCP/IP and UDP/IP layers over the Ethernet.
Q7. How many different communication Ethernet sessions can be opened through the LAN port?
A7. ModBus TCP/IP:4 sockets
DNP TCP/IP:3 sessions (from version 1.72 on)
Q8. May I use the cooper 10/100 BaseTX connection included in the basic model with all protocols?
A8. Yes, it may be used with all protocols. In noisy substation environments and/or long distances, it is recommended to
use fiber optic options due to much better EMC performance and immunity. For fiber optic models, it is necessary to
adjust an internal jumper to use the copper port.
Q9. Remote I/O CAN bus. Does it support DeviceNet protocol?
A9. No it does not support DeviceNet.
Q13. How do I connect with fiber 10-BASE-FL UR relays with 100-BASE-FX F650 relays?
A13. Take into account that an UR is never connected directly to a F650 (neither two UR nor two F650 with each other)
but they are always connected through a hub or switch. The hub or switch where the URs are connected must be
10-BASE-FL and the hub or switch for the F650 must be 100-BASE-FX.
Q14. How do I connect with cable 10_BASE-T UR relays with 10/100-BASE-TX F650 relays?
A14. The answer to this question is as described before but also in this case there is an advantage added, because the
hub 10-BASE-TX port is able to understand a 10-BASE-T port. This means that a hub 10-BASE-T port may be
connected to an UR or a F650, and a hub 10/100-BASE-TX port may be connected either to an UR or F650.
Q15. What happens with fiber optic connectors compatibility, because the hub that I have has a different connector to the
one of the F650, although both are 100-BASE-FX?
A15. Just buy fiber cables with the appropriate male connectors. For the UR and F650 side we need the same
connectors, ST type, for the hub side, the correspondent ones. And in what concerns to the fiber type, it is used the
same for 10 as for 100, it is the 50/125 or 62.5/125 multimode, this last one allows longer distances.
Q17. Why do we have 10/100 compatibility for cable but not for fiber?
A17. The cable has some advantages that the fiber does not have, and it is that the signal attenuation in short and
medium distances, is worthless and this is truth for low and high frequency signals. By the contrary, the light in one
fiber optic is highly attenuated, being much worse in case of high frequencies than in the low ones. The 10-BASE-FL
fiber transmission is performed in a wavelength of 850nm, what allows a less expensive electronic than the 1300 nm
used in 100-BASE-FX fiber transmission. Using, in both cases, the same glass multimode fiber type, the attenuation
to 1300 nm is lower than the 850 nm ones, this way the greater attenuation of the 100 Mbits is compensated. There
is another fiber standard, the 100-BASE-SX, which uses 850 nm to 100 Mbits, being compatible with the 10-BASE-
FL one, although it sacrifices the maximum distance to 300 m. Nowadays, this standard has not had success among
Ethernet equipment manufacturers and suppliers.
12.2 Protection
Q1. Does the F650 support IRIG-B signals? Which type and accuracy? How many units may be connected to the same
source?
A1. Yes, the F650 includes an IRIG-B input for all models, including the basic ones.
It uses DC level format B. Formats used are B0000, B0002 and B0003.
Actual accuracy is 1 millisecond. Internal sampling rate allows true 1 ms accuracy time tagging.
The input burden is very low. The maximum number of units that may be connected to a generator depends on its
output driving capability. Up to 60 units have been successfully connected with equipments commonly used in the
market.
Q2. Does the equipment work with dry inputs in both AC and DC?
A2. The equipment works only with DC inputs.
Inputs should be driven with externally generated DC current. No special 48 Vdc or other outputs are included in the
equipment to drive these inputs; therefore, contacts connected to the equipment should be connected to a DC
source.
Q3. Is it oscillography programmable?
A3. Yes, the sampling rate is programmable (4, 8, 16, 32 or 64 samples per input). The depth depends on the sampling
rate.
Q5. In my installation, several digital inputs become active when I energize the transformer. How can I reduce sensitivity?
A5. By selecting debounce time and/or voltage threshold, the relay may adapt its sensitivity to different applications.
Select the maximum voltage threshold and debounce time (recommended 15 ms) to minimize AC coupling effects.
A1. Get/Send are used for settings and configuration storage that although both are in a unique file, are sent separately
in two times. Upload/Download are used for project or PLC files group storage. These files are the
setting_configuration file source. To operate, the F650 does not need the source files; the Upload/Download tool is
destined to serve as historic file.
It is easier to read the LCD display because it has been designed for horizontal positions.
Compatibility between text display (4x20 characters) and LCD display (16x40 characters or 128x240 pixels).
Refresh speed is better in horizontal than vertical format.
Q6. Is it possible to have a remote HMI installed in the front of the panel with the rest of the relay in the rear side?
A6. Not in the present version.
Q8. May I force inputs and outputs to ease commissioning and testing?
A8. Yes.
Q10. How can I disable/enable beep sound HMI keypad in models with Enhanced HMI?
A10. To disable: Press ESC push-button more than 3 seconds and then press ENTER push-button while keeping ESC
push button pressed.
To enable: Press ESC push-button more than 3 seconds. After this time, press the ENTER push-button and then Up/
down key while keeping ESC push-button pressed.
Q11. Why do appear strange texts on the display when switching on the relay?
A11. You have pressed any button and the HMI has entered test mode.
The display messages are updated after a few minutes, once the relay has completed the starting sequence.
Q2. I set an output contact as "Latched". If I do not set a "reset" condition, will it reset from the "ESC" key?
A2. No, you have to configure the contact output reset signal (in Setpoint > Relay Configuration > Outputs).
The ESC key only reset the LED indicators.
F650 units have been designed and verified using the most advanced and reliable equipment. Mounting and
testing automation ensure a high consistency of the final product. Before sending a unit back to the factory,
we strongly suggest you follow the recommendations below. These actions may solve the problem, and if
not they will help define the problem for quicker repair.
To send a unit back to the factory for repair, use the appropriate RETURN MATERIAL AUTHORIZATION process,
and follow the shipping instructions provided by our Service Department, especially in the case of international
shipments. This will lead to a faster and more efficient solution to your problem.
Category Symptom Possible cause Recommended action
Protection The relay does not -Function not permitted -Set the function permission to
trip ENABLED
- The unit is not set to ready - Verify that the general setting is set
to disable and the out of service
state is not active
General When feeding the -Insufficient power supply -Verify the voltage level using a
unit, no indicator is lit multimeter in the power supply
up terminals, and check that it is within
the model range
-Incorrect baud rate, port, address, -Test other ports, other baud rates,
etc. etc. Make sure that the
communication parameters in the
computer match the ones in the
relay.
General After Updating the Check that the bootware version -If there is an incompatibility
firmware the relay match with the firmware version between boot and firmware version,
does not start up and update to the corresponding boot
always shows the and after that update the firmware
message “Os version
Loading…”.
-If the boot and firmware versions
are correct, perform the firmware
update procedure again.
Communication EnerVista 650 Setup Bad communication in TFTP using Disable and Enable the Ethernet
does not retrieve osc, Windows 2000 connection on Control Panel inside
fault reports and Data Windows 2000. Try again to retrieve
Logger files files from relay
Firmware and bootware upgrade
Bootware The relay gets stuck - The relay does not communicate To perform the bootware upgrading
during the upgrading via the front RS232 port process it is necessary to connect
process after the unit thought the front RS232
switching off and on port. check:
the relay, giving the • Serial cable correct (straight
following error through) and undamaged.
message: “ERROR • Settings selection in EnerVista 650
Setting relay in Setup: Communication > Computer
configuration mode. Settings”:
Retry? o Com port selected must be
the one that is being used to
perform this procedure
o Parity set to NONE
o Baud rate set to 19200
o Control type: No control type
o Modbus slave number: any
Note: if the bootware upgrade
procedure got stuck at this point
the relay will not be upgraded.
After reboot the relay will
continue working with the former
firmware and bootware versions.
Firmware It is not possible to - IEC 61850 upgrade from standard • To upgrade from a standard model
upgrade models models is password protected. to a 6 model, ask the factory for an
without IEC 61850 to upgrade package, depending on the
models with IEC hardware the existing unit has. If it is
61850 automatically hardware 00 a hardware and
firmware change is required
(password protected), if it is
hardware 01 or above only a
firmware change is required
(password protected).
Firmware During the upgrading - Communication problems during • EnerVista 650 Setup program
process for models the upgrade procedure. does not ask for a password if the
with IEC 61850 -The procedure has been not relay model is IEC61850 and the
sometimes it ask for performed in a continuous way. procedure is completed.
password and • If during the process there is any
sometimes not. problem and it has to be restarted,
this second time the program will
ask to confirm the IEC password.
• If the EnerVista 650 Setup
program is closed and started again
during the bootware and firmware
upgrade process, the program will
ask to confirm the IEC password.
Firmware Password for - Model change • The password is tied to the model,
IEC61850 incorrect - Incorrect mac or serial number MAC Address and serial number, so
a change in any of these requires a
password change.
• If the model has been modified to
add or replace any boards or
communication protocol, the IEC
61850 passwords needs to be
updated (contact the factory).
EnerVista 650 Setup InstallShield Setup A previous installation of any Delete (or rename) the 0701 folder
Initialization Error product using InstallShield for located in "C:\Program
6001 installation may have corrupted Files\Common
some of the InstallShield files used Files\InstallShield\Professional\Run
in the EnerVista 650 Setup Time\" and retry installation
installation
LOGIC OPERANDS
Note: It is advisable to use the critical alarms to raise an event or to light a warning LED for maintenance purposes.
See the example below, the Board X Status depends on the relay model.
... ...
MODBUS PROTOCOL
B.1 Introduction
This section describes the MODBUS memory map and how to read and write data from and to the F650 relay using
MODBUS protocol. The MODBUS protocol is an industrial communications protocol based on a master/slave
architecture (RTU-Serial) or a client/server architecture (TCP/IP). Refer to http://www.modbus.org/ for more
information about this protocol.
A generic memory map has been created, compatible between versions, with all possible items that an F650 may
have, independent of type or configuration to prevent an existing integration from being affected by version changes.
This memory map describes each item including the data type, length, memory position, object version, etc.
Moreover, the memory map groups the different objects into subgroups, such as status and settings groups.
Each object has a unique memory position for the whole family. Only after reading the objects of a particular relay
model, it is possible to elaborate its own MODBUS memory map. This map is only valid for that particular relay and
memory version. From one version to another the memory positions of existing objects remain fixed, and new
objects are assigned new addresses, which again remain the same for following versions.
View the Memory Map using EnerVista 650 Setup software, menu:
View > MODBUS Memory map
The implemented protocol is standard MODBUS, so any SCADA or PLC can easily communicate with F650 units.
The F650 unit always works as a slave/server, and thus never initiates communication; it is always the master/client
(EnerVista 650 Software or PLC, i.e.) that initiates communication.
Only two MODBUS codes are implemented in all firmware versions:
Starting from firmware version 7.50 and above, two custom MODBUS functions have also been implemented:
• Read function 66 (42h)
• Write function 67 (43h)
The two new custom function codes allow the master/server to read/write settings of protection functions affected by
the setting groups. If these MODBUS function codes are used, the master/server has access to read/write protection
element settings that belong to any setting group. In contrast, if read function 3 or Write function 4 is used, only
protection elements settings in the active setting group can be accessed/modified.
MODBUS FORMAT
CLIENT ADDRESS 1 byte Each device in a communications bus must have a unique address to prevent
[A] two units from responding at the same time to the same request. All relay ports
use this address, which can be programmed to any value between 1 and 254.
When the master transmits a string with the slave address 0, this indicates that it
is a Broadcast. Every slave in the communication bus performs the requested
action, but none of them responds to the master. Broadcast is only accepted for
writing since no unit responds.
FUNCTION CODE 1 byte This is one of the function codes supported by the equipment. The generic
[B] function codes are 3 and 4 for reading and 16 for writing. Special read function
66 and write function 67 are available only for firmware version 7.50 or above.
When the slave responds with an exception to any of these strings, it places to 1
the most important bit of the corresponding function. For example, an exception
to function 3 is indicated with an 83 as function code, and an exception to
function 16 or 0x10 in hexadecimal, is indicated with a 0x90.
SETTING GROUP 1byte This part of string format only applies to read function 66 and write function 67
SELECTED (fw 7.50 or above).This byte indicates the setting group being read or written.
[B1] Values should are as follow:
0 [Decimal] Setting Group 1
1 [Decimal] Setting Group 2
…
5 [Decimal] Setting Group 6
DATA N bytes This section includes a variable number of bytes, depending on the function
[C] code. It may include: addresses, data length, settings, commands or exception
codes sent by the client.
CRC 2 bytes Two-byte control code. ModBus/RTU includes a 16-bit CRC in each string for
[D] error detection. If the slave detects a string with errors, based on an incorrect
CRC, it neither performs an action, nor responds to the master. The CRC order is
LSB-MSB.
TIME OUT Required time to A string is finished when nothing is received during a period of 3.5 bytes, with the
transmit 3.5 Bytes actual time varying depending on baud rate:
15 ms at 2400 bps
2 ms at 19200 bps
300 μs at 115200 bps
etc.
Reading function 3 or 4:
01 04 01 09 00 01 XX XX
01 42 00 01 09 00 01 XX XX
OK Response
Reading function 3 or 4:
01 42 02 00 08 XX XX
Bytes...Data ..........
Error Response
R
e
ading function 3 or 4:
01 C2 03 XX XX
01 10 00 87 00 02 04 00 0A 01 02 XX XX
01 43 00 09 C1 00 01 02 00 03 XX XX
OK Response
01 43 09 C1 00 01 XX XX
Data Addr…....Regs .....
Error Response
Error code...........
01 C3 03 XX XX
43 67 Setting Group Writing of values This function allows the master to write any setting that belongs to any setting
Write affected by group, active or not, in one or more consecutive relay addresses. Registers
setting are always 16-bits long, with the most important byte first. The maximum
number of registers that can be written in a single package is 125, equivalent
to 250 bytes.
01 ILLEGAL FUNCTION Slave does not support the function code received.
02 ILLEGAL DATA ADDRESS Master is using an incorrect address.
03 ILLEGAL DATA VALUE Slave has detected an invalid value.
04 ILLEGAL RESPONSE Response to the master’s request exceeds the maximum size for that function code.
LENGTH
05 ACKNOWLEDGE Generic acknowledgment.
06 SLAVE DEVICE BUSY Slave is busy and cannot perform the requested operation.
07 NEGATIVE ACKNOWLEDGE Negative acknowledgment.
F7 1 Characters without sign. As it needs to be sent in a register, i.e. in two bytes, the character goes below.
Example: ‘β’ = 0x00E1
F8 1 Characters with sign As it needs to be sent in a register, i.e. in two bytes, the character goes below.
Example: ‘A’ = 0x0041
F9 16 String. Chain of characters with a fixed length (32 bytes). The end of the string is marked with “\0”.
Example: “ABC” = 0x41x42x43x00....
F10 1 This is a 16-bit integer without sign. Each value that can be taken by this integer has a correspondence in the
database Auxiliary Table. In this table we can find the corresponding chain, which must be shown for each
value. In memory, only an integer value is received.
Example: 0, 1Correspond to CLOSE, OPEN
F11 3 Milliseconds passed since January/1/2000 at 00:00:00.000.
F12 1 Unsigned int 16 bit (enumerated), example: In MODBUS address Ox0EBE is the FAULT TYPE
0=GROUND
1=PHASE
2=3 PH
3=AG
4=ABG
5=AB
6=BG
7=BCG
8=BC
9=CG
10=CAG
11=CA
12=NAF
2nd step:
[0xFE 0x03 0xFF 0x00 0x00 0x7D 0xA1 0xF0] --------> RELAY
The relay responds with “SLAVE DEVICE BUSY”:
PC <--------- 0xFE 0x83 0x06 0xF1 0x02]
The request is repeated:
[0xFE 0x03 0xFF 0x00 0x00 0x7D 0xA1 0xF0] --------> RELAY
Now the relay sends the events format:
[A] Position within file (Unsigned 32 bits)
[B] Block size (Unsigned 16 bits)
PC --------- [0xFE 0x03 0xFA 0x00 0x00 0x00 0x00 0x00 0xF4 0x46 0x4F 0x52 0x4D 0x41
.............[A].............. .....[B]...... F O R M A
0x54 0x2C 0x45 0x56 0x45 0x4E 0x54 0x5F 0x46 0x36 0x35 0x30 0x5F 0x56 0x30
T , E V E N T _ F 6 5 0 _ V 0
0x30 0x2C 0x45 0x76 0x65 0x6E 0x74 0x20 0x4E 0x75 0x6D 0x2C 0x44 0x61 0x74
0 , E v e n t N u m , D a t
0x65 0x2F 0x54 0x69 0x6D 0x65 0x3C 0x48 0x65 0x78 0x3E 0x2C 0x43 0x61 0x75
e / T i m e . . . etc . . .
0x73 0x65 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x49 0x61 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x49
0x62 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x49 0x63 0x2C 0x4C 0x69 0x6E 0x65 0x20 0x46 0x72 0x65 0x71
0x75 0x65 0x6E 0x63 0x79 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x49 0x67 0x2C 0x50 0x68 0x61 0x73 0x6F
0x72 0x20 0x49 0x73 0x67 0x2C 0x5A 0x65 0x72 0x6F 0x20 0x73 0x65 0x71 0x20 0x49 0x30 0x2C 0x50 0x6F 0x73
0x69 0x74 0x69 0x76 0x65 0x20 0x53 0x65 0x71 0x20 0x49 0x31 0x2C 0x4E 0x65 0x67 0x61 0x74 0x69 0x76 0x65
0x20 0x53 0x65 0x71 0x20 0x49 0x32 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x56 0x61 0x6E 0x2C 0x50 0x68
0x61 0x73 0x6F 0x72 0x20 0x56 0x62 0x6E 0x2C 0x50 0x68 0x61 0x73 0x6F 0x72 0x20 0x56 0x63 0x6E 0x2C 0x50
0x6F 0x73 0x69 0x74 0x69 0x76 0x65 0x20 0x53 0x65 0x71 0x20 0x56 0x31 0x2C 0x4E 0x65 0x67 0x61 0x74 0x69
0x76 0x65 0x20 0x53 0x65 0x71 0x20 0x56 0x32 0x2C 0x5A 0x65 0x72 0x6F 0x20 0x53 0x65 0x71 0x20 0x56 0x30
0x2C 0x33 0x20 0x50 0x68 0x4C 0xF3]
[0xFE 0x03 0xFF 0x00 0x00 0x7D 0xA1 0xF0] ---------> RELAY
PC <--------- [0xFE 0x03 0xFA 0x00 0x00 0x00 0xF4 0x00 0xF4 0x61 0x73 0x65 0x20 0x50 0x6F
0x77 0x65 0x72 0x20 0x46 0x61 0x63 0x74 0x6F 0x72 0x0D 0x0A
CR LF (here the format ends)
0x45 0x56 0x45 0x4E 0x54 0x5F 0x46 0x36 0x35 0x30 0x5F 0x56 0x30 0x30 0x2C 0x35 0x36 0x35
E V E N T _ F 6 5 0 _ V 0 0 , 5 6 5
0 x37 0x2C 0x30 0x30 0x30 0x30 0x30 0x30 0x31 0x36 0x66 0x63 0x39 0x38 0x66
7 , 0 0 0 0 0 0 1 6 f 3 9 8 f
0x34 0x33 0x39 0x2C 0x4C 0x6F 0x63 0x61 0x6C 0x20 0x6D 0x6F 0x64 0x65 0x2C
4 3 9 , l o c a l m o d e ,
0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30
....
0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30
0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30
0x2E 0x30 0x30 0x32 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x32 0x2C 0x30 0x2E 0x30
0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x31 0x2E 0x30 0x30 0x30
0x0D 0x0A
CR LF (a line ends)
0x45 0x56 0x45 0x4E 0x54 0x5F 0x46 0x36 0x35 0x30 0x5F 0x56 0x30 0x30 0x2C 0x35 0x36 0x35 0x38 0x2C
0x30 0x30 0x30 0x30 0x30 0x30 0x31 0x36 0x66 0x63 0x39 0x38 0x66 0x34 0x33 0x39 0x2C 0x28 0x31 0x29 0x56
0x69 0x72 0x74 0x75 0x61 0x6C 0x20 0x4F 0x75 0x74 0x38 0x39 0x36 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30
0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x34
0x24]
[0xFE 0x03 0xFF 0x00 0x00 0x7D 0xA1 0xF0] ---------> RELAY
PC <---------[0xFE 0x03 0xFA 0x00 0x00 0x01 0xE8 0x00 0x47 0x30 0x0047 => last string
0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30
0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x32 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30
0x2E 0x30 0x30 0x32 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30
0x30 0x30 0x2C 0x31 0x2E 0x30 0x30 0x30 0x0D 0x0A
CR LF (a line ends)
0x00 0x00 0x30 0x0D 0x0A 0x45 0x56 0x45 0x4E 0x54 0x5F 0x46 0x36 0x35 0x30 0x5F 0x56 0x30 0x30 0x2C 0x33
0x30 0x39 0x38 0x2C 0x30 0x30 0x30 0x30 0x30 0x30 0x31 0x36 0x65 0x62 0x61 0x33 0x33 0x62 0x62 0x38 0x2C
0x43 0x6F 0x6E 0x74 0x61 0x63 0x74 0x20 0x4F 0x75 0x74 0x70 0x75 0x74 0x5F 0x30 0x30 0x5F 0x30 0x30 0x20
0x4F 0x4E 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x31
0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30
0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30
0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x32 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x30 0x2E 0x30 0x30 0x30
0x2C 0x30 0x2E 0x30 0x30 0x31 0x2C 0x30 0x2E 0x30 0x30 0x30 0x2C 0x31 0x2E 0x30 0x30 0x30 0x0D 0x0A
0x45 0x56 0x45 0x4E 0x54 0x5F 0x46 0x36 0x35 0x30 0xDB 0xB4]
B.4.4 Operations
To execute an operation, write the bit corresponding to that operation. For this purpose, there are two memory
records with bits representing operations. These records are 0xAFFE and 0xAFFF.
Each operation is assigned one bit in the register:
Operation 1: bit 0 ‘0xaffe’
Operation 2: bit 1‘0xaffe’
...
Operation 16: bit 15‘0xaffe’
Operation 17: bit 0‘0xafff’
...
Operation 24: bit 7‘0xafff’
The register format is Big Endian; this means that the first byte arriving is the one with more weight. Operations
commands are affected depending on the physical communication channel they use: serial port, ethernet ports, mmi,
etc.
Refer to section 4.2.3.2 Command push button on page 4–73.
The operations channels are:
0 - MMI
1 - OPER REMOTE
2 - COM 1- COMMUNICATION
3 - COM 2- COMMUNICATION
4 - RED 1- COMMUNICATION
5 - RED 2- COMMUNICATION
6 - RED 3- COMMUNICATION
7 - RED 4- COMMUNICATION
2 Write:
[0xFE 0x10 0xFF 0x20 0x00 0x05 0x0A 0x00 0x00 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x0000 0x03
0xAE 0x8D] ---------> RELAY
PC <--------- [0xFE 0x10 0xFF 0x20 0x00 0x05 0x25 0xDB]
3 Close:
[0xFE 0x10 0xFE 0x28 0x00 0x03 0x06 0x4F 0x55 0x54 0x50 0x55 0x54 0x29 0xA8] ---------> RELAY
PC <--------- [0xFE 0x10 0xFE 0x28 0x00 0x03 0x25 0xE7]
Internally the events buffer is a circular FIFO of 255 events. The addresses for managing this FIFO are:
- 0x03FF: Number of the next event
- 0xFCFF: Access to the oldest event
- 0xFD00 to 0xFDFF: Access to any stored event (circular queue)
The address 0x03FF stores the number of the next event. For example, if the number 7677 is stored, the last event
stored is number 7676. This value is initially 0, and it is increases from 0 to 2^12 + 1 carry bit as events are
generated.
The carry bit indicates whether the F650 has been started, since when the relay starts, whether due to lack of power
supply or a configuration change, the carry bit is set to 0. When events are generated, the event number is increased
up to a maximum value of 0x1FFF; in the next event the number is 0x1000, thus the carry bit is always 1, until the
F650 is restarted. This is shown in the following figure:
The 0xFCFF address is useful when reading all the available events in the F650, as is done following a master start
up.
WARNING! Unlike a standard ModBus address, these addresses consist of 14 bytes each one, instead of the 2
used in ModBus. This way, each event, which has a structure of 14 bytes, is contained in one address, as shown on
the table below:
0xFD00 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte
............
0xFDFF 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte 1byte
For example, the events buffer could contain the following information:
ALL EVENTS
When reading all events, there are two possible approaches:
First option: start from the oldest event, in address 0xFCFF, and read the events 15 by 15. The initial request frame
sent to the relay is as follows:
Within this frame the buffer pointer is set to the oldest event, or number 7421 in the example. 15 events are returned,
ending with number 7435.
In order to read the following 15 events, numbered from 7436 to 7450, calculate the initial address and send another
request frame:
Hex(7436)= 0x1D0C
0x1D0C AND 0x00FF= 0xOC
0xFD00+0x0C= 0xFD0C: initial address
[0xFE 0x03 0xFD 0x0C 0x00 0x69 0x60 0x44] ---------> RELAY
Either continue until the relay responds with a 0 event, or stop at the last recorded event by reading the number of
the next upcoming event from address 0x03FF and comparing against the last event read.
Second option: read the circular event queue directly, from address 0xFD00 to 0xFDFF, and then rearrange the
retrieved events by event number.
Once all events have been read, subsequent queries should only request new events.
NEW EVENTS
The 0x03FF address contains the number of the next event to be written. Based on this, the number of events
recorded since the last query can be determined.For example, if the relay indicates that the next event to be
generated is number 7677 and events up to number 7674 have already been read, there are two new events. A
frame must be sent to read the two new events, 7675 and 7676, and the corresponding 28 bytes.
Hex(7675)=0x1DFB
0x1DFB AND 0xFF=0xFB
0xFD00+0xFB=0xFDFB: reading address (*)
[0xFE 0x03 0xFD 0xFB 0x00 0x0E 0x90 0x5C] ---------> RELAY
SERIAL COMUNICATION
EnerVista 650 Setup –e event number "File name" –com port: baud_rate relay_number
E.g.: EnerVista 650 Setup –e 6 “C:\GE Power Management\EnerVista 650 Setup\files\Events\eventos.txt” –com
1:19200 254
ETHERNET COMMUNICATION
EnerVista 650 Setup –e event number "File name" –ip “IP address”: port relay_number
E.g.: EnerVista 650 Setup –e 6 “C:\GE Power Management\EnerVista 650 Setup\files\Events \eventos.txt” –ip
192.168.37.240:502 254
The created file format looks as follows:
#Event Number, Event Id,Event Text,Event Data Time,Event Value(0,1)#
6,1,Local,09-Sep-2003 17:42:40.782,1
7,1,Local,09-Sep-2003 17:42:43.236,0
8,2,Remote,09-Sep-2003 17:42:43.236,1
To obtain an instantaneous snapshot of all events and alarms states, do the following:
1. Read the head of events FIFO (0x03FF).
2. Read the addresses above.
3. Finally, read the head again to confirm that it has not changed. If it had changed, restart the procedure.
NOTE: The message must request the address and the quantity of bytes indicated in each zone. If another quantity
is needed, it will not respond with the requested data.
A record index area (addresses 0x3384 to 0x3483), containing 256 statuses and/or setting record addresses.
A record area (addresses 0xF330 to 0xF42F), containing the values for addresses indicated in the index area.
Data records that are separated in the rest of the memory map can be remapped to an address of an adjacent record
in the User Map area. For programming the map this way, addresses for the required records must be written in the
index area. This avoids the need for several reading operations, thus improving data transmission yield.
For instance, if Contact Outputs from Board F (address 0x008B) and Board G (address 0x00B0) values are required,
these addresses must be mapped as follows:
In address 0x3384, write 0x008B.
In address 0x3385 XXX write 0x00B0.
The reading of records 0xF330 and 0xF331, applying the corresponding bit masks, provides the required information
about the two boards Contact Outputs.
NOTE: Only single data can be set in the map, i.e. data that are in the memory map and can be read. This feature is
not valid for events, waveform records, etc. that are not located in a map address.
Time synchronization is made by a reading message over 0xfff0 address, either with the address of a single relay, if
a writing confirmation is desired, or in broadcast, to synchronize several relays simultaneously.
Date/time format is stored in 4 MODBUS registers (8 bytes, Big Endian format), which indicates elapsed milliseconds
from the 1st of January 2000 at 00:00:00.000.
Reading example:
[0xFE 0x03 0xFF 0xF0 0x00 0x04 0x60 0x21] ---------> RELAY
PC <---------- [0xFE 0x03 0x08 0x00 0x00 0x00 0x17 0x05 0xFA 0xD5 0xBA 0x2D 0x1D]
Synchronism example:
[0xFE 0x10 0xFF 0xF0 0x00 0x04 0x08 0x00 0x00 0x00 0x17 0x9B 0x53 0x3F 0x60 0xA4 0x2B] ---------> RELAY
PC <---------- [0xFE 0x10 0xFF 0xF0 0x00 0x04 0xE5 0xE2]
NOTE: As the relay is internally a modular system, it is possible that the response of some processes is slower than
what is expected by the external program, considering the message as missed and sending again another request. If
so, there will be 2 queued messages and therefore, 2 message responses. For this reason, response message
‘ACK’ must be verified with its request, and special attention must be paid to setting confirmation writings, especially
with reference to time-out. EnerVista 650 Setup software is recommended to do the configuration modifications, as
this software takes into account all these details.
The screen displays the group settings, and on the left side bottom the relay read request is shown:
<0001><06/18/03 12:14:15>[0xFE 0x03 0x21 0x8A 0x00 0x16 0xFB 0xDD]
On the right the settings response is shown:
0001><06/18/03 12:14:15>[0xFE 0x03 0x2C 0x3F 0x80 0x00 0x00 0x3F 0x80 0x00 0x00 0x3F 0x80 0x00 0x00
0x3F 0x80 0x00 0x00 0x00 0x00 0x42 0xC8 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01
0x00 0xFE 0x00 0xFE 0x00 0x06 0x00 0x06 0x00 0x00 0x01 0xF6 0xAC 0xB5]
This way, any request or mechanism to obtain information from the relay can be viewed string by string.
There is another tool for tracing the relay memory: in the EnerVista 650 Setup menu: Communication >
Troubleshooting, any read of any address can be requested, and the PC forms the request string together with the
check-sum register.
{
const UCHAR hi[] = {
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,
0X0,0Xc1,0X81,0X40,0X0,0Xc1,0X81,0X40,0X1,0Xc0,
0X80,0X41,0X1,0Xc0,0X80,0X41,0X0,0Xc1,0X81,0X40,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X0,0Xc1,
0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,0X80,0X41,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X0,0Xc1,
0X81,0X40,0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X0,0Xc1,0X81,0X40,
0X1,0Xc0,0X80,0X41,0X1,0Xc0,0X80,0X41,0X0,0Xc1,
0X81,0X40,0X1,0Xc0,0X80,0X41,0X0,0Xc1,0X81,0X40,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X0,0Xc1,0X81,0X40,
0X1,0Xc0,0X80,0X41,0X0,0Xc1,0X81,0X40,0X1,0Xc0,
0X80,0X41,0X1,0Xc0,0X80,0X41,0X0,0Xc1,0X81,0X40,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,
0X0,0Xc1,0X81,0X40,0X0,0Xc1,0X81,0X40,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,
0X1,0Xc0,0X80,0X41,0X0,0Xc1,0X81,0X40,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40,0X0,0Xc1,0X81,0X40,
0X1,0Xc0,0X80,0X41,0X1,0Xc0,0X80,0X41,0X0,0Xc1,
0X81,0X40,0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,
0X0,0Xc1,0X81,0X40,0X1,0Xc0,0X80,0X41,0X1,0Xc0,
0X80,0X41,0X0,0Xc1,0X81,0X40};
UCHAR chi;
UCHAR clo;
USHORT ui;
chi = 0xff;
clo = 0xff;
while(us--)
{ ui = chi ^ *p++;
chi = clo ^ hi[ui];
clo = lo[ui];
}
ui = chi;
ui = ui << 8;
ui = ui | clo; // Big-Endian format
return(ui);
}
If it is Little-Endian format the returned bytes must be interchanged: each unsigned 16 bit type's bytes need to be
swapped.
The Memory map can be obtained from EnerVista 650 Setup software, menu:
View > ModBus Memory map
ADDRESS BIT NAME FORMAT STEP MODE LENGTH MISCELLANEOUS
Estado CPU - CPU Status
0x0003 0x010 TIMER STATUS F001 R 1
0
0x0003 0x020 E2PROM STATUS F001 R 1
0
Salidas Virtuales (512 elementos) - Virtual Outputs
0x0005 0x040 VIRTUAL OUTPUT 000 F001 R 1
0
0x0005 0x080 VIRTUAL OUTPUT 001 F001 R 1
0
... ... ... ... ... ... ... ...
0x0025 0x020 VIRTUAL OUTPUT 511 F001 R 1
0
Salidas virtuales analógicas- Virtual Output Analog
0x07D0 INT32_000 F005 1.000 R 2
0x07D2 INT32_001 F005 1.000 R 2
0x07D4 INT32_002 F005 1.000 R 2
0x07D6 INT32_003 F005 1.000 R 2
0x07D8 INT32_004 F005 1.000 R 2
0x07DA INT32_005 F005 1.000 R 2
0x07DC INT32_006 F005 1.000 R 2
0x07DE INT32_007 F005 1.000 R 2
0x07E0 INT32_008 F005 1.000 R 2
0x07E2 INT32_009 F005 1.000 R 2
0x07E4 INT32_010 F005 1.000 R 2
0x07E6 INT32_011 F005 1.000 R 2
0x07E8 INT32_012 F005 1.000 R 2
0x07EA INT32_013 F005 1.000 R 2
0x07EC INT32_014 F005 1.000 R 2
0x07EE INT32_015 F005 1.000 R 2
0x07F0 INT32_016 F005 1.000 R 2
0x07F2 INT32_017 F005 1.000 R 2
0x07F4 INT32_018 F005 1.000 R 2
0x07F6 INT32_019 F005 1.000 R 2
0x07F8 INT32_020 F005 1.000 R 2
0x07FA INT32_021 F005 1.000 R 2
0x07FC INT32_022 F005 1.000 R 2
0x07FE INT32_023 F005 1.000 R 2
0x0800 INT32_024 F005 1.000 R 2
Estado Señales Reposición de Salidas Tarjeta F (16 elementos) - Board F: Contact Output Resets
0x008A 0x100 CONT OP RESET_F_1 F001 R 1
0
Estado Salidas Tarjeta F (16 elementos) - Board F: Contact Outputs -physical status-
0x008B 0x100 CONT OP_F_01 F001 R 1
0
0x008B 0x200 CONT OP_F_02 F001 R 1
0
... ... ... ... ... ... ... ...
0x008C 0x080 CONT OP_F_16 F001 R 1
0
Estado Tarjeta F - Board F Status
1. Physical Port: The F650 supports the Distributed Network Protocol (DNP) version 3.0. The F650 can be
used as a DNP slave device connected up to three DNP masters (usually RTUs or SCADA master stations).
The Physical Port setting is used to select the communications port assigned to the DNP protocol for a
specific logical DNP slave device of F650. When this setting is set to NETWORK, the DNP protocol can be
used over either TCP/IP or UDP/IP.
2. Address: This setting is the DNP slave address. This number identifies the F650 on a DNP communications
link. Each logical DNP slave should be assigned a unique address.
3-22. IP Addr Client x Oct x: this setting is one of four octets of an IP address. The F650 relay can respond to a
maximum of 5 specific DNP masters (not in the same time). To set the IP address of DNP master it is
necessary to set four octets (e.g. to set the IP address of the first DNP master to 192.168.48.125, you should
set IP Addr Client1 Oct1 = 192, IP Addr Client1 Oct2 = 168, IP Addr Client1 Oct3 = 48, IP Addr Client1
Oct4 = 125).
23. TCP/UDP Port: TCP/UDP port number for the case of DNP3 communication being performed through the
Ethernet.
24. Unsol Resp Function: ENABLED, if unsolicited responses are allowed, and DISABLED otherwise.
25. Unsol Resp TimeOut: sets the time the F650 waits for a DNP master to confirm an unsolicited response.
26. Unsol Resp Max Ret: This setting determines the number of times the F650 retransmits an unsolicited
response without receiving a confirmation from the master. Once this limit has been exceeded, the
unsolicited response is sent at a larger interval. This interval is called the unsolicited offline interval and is
fixed at 10 minutes.
27. Unsol Resp Dest Adr: This setting is DNP address to which all unsolicited responses are sent. The IP
address to which unsolicited responses are sent is determined by the F650 from either the current DNP TCP
connection or the most recent UDP message.
28-32. Scale Factor: These settings are numbers used to scale Analog Input point values. These settings group the
F650 Analog Input data into types: current, voltage, power, energy, and other. Each setting represents the
scale factor for all Analog Input points of that type. For example, if the Voltage Scale Factor is set to a value
of 1000, all DNP Analog Input points that are voltages are returned with the values 1000 times smaller (e.g. a
value 72000 V on the F650 is returned as 72). These settings are useful when Analog Input values must be
adjusted to fit within certain ranges in DNP masters. Note that a scale factor of 0.1 is equivalent to a multiplier
of 10 (i.e. the value is 10 times larger).
33-37. Deadband: These settings are the values used by the F650 to determine when to trigger unsolicited
responses containing Analog Input data. These settings group the F650 Analog Input data into types: current,
voltage, power, energy, and other. Each setting represents the default deadband value for all Analog Input
points of that type. For example, in order to trigger unsolicited responses from the F650 when any current
values change by 15 A, the Current Deadband setting should be set to 15. Note that these settings are the
default values of the deadbands. DNP object 34 points can be used to change deadband values, from the
default, for each individual DNP Analog Input point. Whenever power is removed and re-applied to the F650,
the default deadbands are in effect.
38. Msg Fragment Size: This setting determines the size, in bytes, at which message fragmentation occurs.
Large fragment sizes allow for more efficient throughput; smaller fragment sizes cause more application layer
confirmations to be necessary which can provide for more robust data transfer over noisy communication
channels
39-48. Binary Input Block x: These settings allow customization and change of the size of DNP Binary Inputs point
list. The default Binary Inputs point list contains 160 points representing binary states that are configured
using Setpoint > Relay Configuration in the EnerVista 650 Setup program. These 160 binary states are
grouped in 10 blocks of 16 points each. There are 128 bits (8 blocks of 16) called Control Events and 32 bits
(2 blocks of 16) corresponding to the states of 16 switchgears available in F650 relay. If not all of the 160
points are required in the DNP master, a custom Binary Inputs point list can be created by selecting up to 10
blocks of 16 points. Each block represents 16 Binary Input points. Block 1 represents Binary Input points 0-
15, block 2 represents Binary Input points 16- 31, block 3 represents Binary Input points 32-47, etc. The
minimum number of Binary Input points that can be selected is 16 (1 block). If all of the Binary Input Block x
settings are set to “NOT USED”, the default list of 160 points is in effect. The F650 forms the Binary Inputs
points list from the Binary Input Block x settings up to the first occurrence of a setting value “NOT USED”.
Permitted values for these settings are: NOT USED, CTL EVENTS 1-16, CTL EVENTS 17-32, CTL EVENTS
33-48, CTL EVENTS 49-64, CTL EVENTS 65-80, CTL EVENTS 81-96, CTL EVENTS 97-112, CTL EVENTS
113-128, SWITCHGEAR 1-8, SWITCHGEAR 9-16,BOARD F 1-16,BOARD F 17-32, BOARD G 1-16,
BOARD G 17-32,BOARD H 1-16, BOARD H 17-32, BOARD J 1-16,BOARD J 17-32.
49-81. Default analog Map: This setting allows selection between predefined Analog Input Points or choosing
preferred Analog Input Points (from 50 to 81).
82. DNP Time Sync IIN Period: This setting has a range of between 1 and 10080 minutes in steps of 1 minute
and the default value is “1440 min”. It determines how often the Need Time Internal Indication (IIN) bit is set
by the F650 relay. Changing this time allows the DNP master to send time synchronization commands more
or less often, as required.
Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the
complete list is described in the attached table):
Binary Inputs (Object 1)
Binary Inputs Changes (Object 2)
Binary Outputs (Object 10)
Binary Counters (Object 20)
Frozen Counters (21)
Binary Counters Change (Object 22)
Frozen Counter Change (23)
Analog Inputs (Object 30)
Analog Input Changes (Object 32)
Analog Deadbands (Object 34)
Maximum Data Link String Size (octets): Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted: Configurable up to 2048
Received: 292 Received: 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
None None
Fixed at 2 Configurable
Configurable
Requires Data Link Layer Confirmation:
Never
Always
Sometimes
Configurable
Reports Binary Input Change Events when no Reports time-tagged Binary Input Change Events when
specific variation requested: no specific variation requested:
Never Never
Only time-tagged Binary Input Change With Time
Only non-time-tagged Binary Input Change With Relative Time
Configurable Configurable (attach explanation)
Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:
Never Never
Configurable When Device Restarts
Only certain objects When Status Flag Change
Sometimes (attach explanation)
ENABLE/DISABLE unsolicited Function codes No other options permitted
supported
Explanation of ‘Sometimes’: It will be disabled for
RS-485 applications, since there is no collision
avoidance mechanism. For ethernet communication
it will be available and it can be disabled or enabled
with the proper function code.
Default CounterObject/Variation: Counters Roll Over at:
No Counters Reported No Counters Reported
Configurable (attach explanation) Configurable (attach explanation)
Default Object: 20. 16 Bits
Default Variation: 1 32 Bits
Point-by-point list attached Other Value: ______
Point-by-point list attached
Sends Multi-Fragment Responses:
Yes
No
The following table shows objects, variations, function codes and qualifiers supported by F650 units, both in requests
and responses for DNP3 protocol. For static (non-change-event) objects, requests sent with qualifiers 00, 01, 06, 07
or 08, are responded to with qualifiers 00 or 01. Static object requests sent with qualifiers 17 or 28 are responded to
with qualifiers 17 or 28. For change-event objects, qualifiers 17 or 28 are always responded.
Text in bold and italic indicates functionality higher than DNP3 implementation level 2.
Note 1: A default variation refers to the variation responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.
Note 2: For static (non-change-event) objects, qualifiers 17 or 28 are only responded when a request is sent with qualifiers 17 or 28,
respectively. Otherwise, static object requests sent with qualifiers 00, 01, 06, 07, or 08, are responded to with qualifiers 00 or 01 (for
change-event objects, qualifiers 17 or 28 are always responded).
Note 3: Cold restarts are implemented the same as warm restarts – The F650 is not restarted, but the DNP process is restarted.
Note 1: A default variation refers to the variation responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.
Note 2: For static (non-change-event) objects, qualifiers 17 or 28 are only responded when a request is sent with qualifiers 17 or 28,
respectively. Otherwise, static object requests sent with qualifiers 00, 01, 06, 07, or 08, are responded to with qualifiers 00 or 01 (for
change-event objects, qualifiers 17 or 28 are always responded).
Note 3: Cold restarts are implemented the same as warm restarts – The F650 is not restarted, but the DNP process is restarted.
In the example presented in this chapter the F650 relay has 48 Binary Input points, as shown in the table below.
Digital Counter values are represented as 32-bit integers. The DNP 3.0 protocol defines counters to be unsigned
integers. Care should be taken when interpreting negative counter values.
BINARY COUNTERS
FROZEN COUNTERS
The deadbands for all Analog Input points are in the same units as the Analog Input quantity. For example, an
Analog Input quantity measured in volts has a corresponding deadband in units of volts. This is in conformance with
DNP Technical Bulletin 9809-001 Analog Input Reporting Deadband. The scale factors apply also to deadbands. For
example if Current Scale Factor is set to 0.001, and it is desired that a specific Analog Input point (that is of type
current) trigger an event when its value changes by 1 kA, then the deadband for this point should be set to 1000.
Relay settings are available to set default deadband values according to data type. Deadbands for individual Analog
Input Points can be set using DNP Object 34.
The “Fault Type” is represented by enumeration value. The table below shows values with DNP3 setting “Other
Scale Factor = 1".
ENUM VALUE FAULT TYPE
0 GROUND
1 PHASE
2 TRIPH
3 AG
4 ABG
5 AB
6 BG
7 BCG
8 BC
9 CG
10 CAG
11 CA
12 NAF
If the DNP3 setting “Other Scale Factor” has a value different from “1” then “Enum Value” is scaled by the adjusted
factor. For example if “Other Scale Factor = 0.001", then the value corresponding to “TRIPH” fault type is 2000.
NAF indicates that the type of fault has not been calculated.
D.1 Introduction
The F650 implements functionality of an IEC 60870-5-104 server. The devices responds to client requests or can
send spontaneous transmissions. F650 implementation of 60870-5-104 provides analog metering and states.
The IEC 60870-5-104 communications protocol is supported on Ethernet ports A and B only.
ASDU is the information unit used for data transmission. An ASDU may have data inside or not. The ASDU is
encapsulated in another package of the link layer. ASDU address takes up 2 bytes.
Communication frames can be control or data frames. Control strings do not have ASDU inside.
A frame is consisting of 3 parts. (2 of them are not always present):
Link data + [ASDU header+ [ASDU data]]
The data between brackets can be omitted.
In IEC104 communication is made by TCP/IP protocols. Actually, it is a TCP communication. The default port is the
2404.
The F650 is listening as a server and supports up to two different IEC60870-5-104 masters simultaneously.
Spontaneous Transmission:
Information objects may be transmitted without a specific request from the IEC 60870-5-104 master.
The data that can be sent spontaneously are:
Clock synchronization
F650 supports clock synchronization from IEC 60870-5-104 master.
If IRIG-B, PTP-1588 or SNTP is being used for time synchronization, the IEC 60870-5-104 clock synchronization
command does not set the F650 real time clock.
Command transmission
F650 is allowed to accept single commands and double commands.
Function: Enable or disable the protocol operation for the first IEC 60870-5-104
connection.
TCP Port: Listening TCP port in the relay. Default value is 2404.
Common Addr of ASDU: Address in the ASDU header. Default value is 255.
Cyclic Meter Period: Number of seconds for cyclical data sending, 0 means no spontaneous
meterings.
Synchronization event: Period of time (in minutes) for which timestamps are considered valid
after receiving a clock synchronization command.
IEC104 NET1 CLI1 OCTET1 to 4: These four octets define the IP address of the first client that is accepted
in the first connection. The F650 relay can respond to a maximum of 2
IEC 60870-5-104 masters (not at the same time) in this connection.
EC104 NET1 CLI2 OCTET1 to 4: These four octets define the IP address of the second client that is
accepted in the first connection. The F650 relay can respond to a
maximum of 2 IEC 60870-5-104 masters (not at the same time) in this
connection.
Function 2: Enable or disable the protocol operation for the second connection.
TCP Port 2: Listening TCP port in the relay. Default value is 2404.
Common Addr of ASDU2: Address in the ASDU header. Default value is 255.
IEC104 NET2 CLI1 OCTET1 to 4: These four octets define the IP address of the first client that is accepted
in the second connection. The F650 relay can respond to a maximum of
2 IEC 60870-5-104 masters (not at the same time) in this connection.
IEC104 NET2 CLI2 OCTET1 to 4: These four octets define the IP address of the second client that is
accepted in the second connection. The F650 relay can respond to a
maximum of 2 IEC 60870-5-104 masters (not at the same time) in this
connection.
IEC104 SCALE CURRENT, VOLTAGE,
POWER, ENERGY, OTHER: These settings are numbers used to scale Analog Input point values.
These settings group the F650 Analog Input data into types: current,
voltage, power, energy, and other. Each setting represents the scale
factor for all Analog Input points of that type. For example, if the IEC104
SCALE VOLTAGE is set to a value of 1000, all IEC104 Analog Input
points that are voltages are returned with the values 1000 times smaller
(e.g. a value 72000 V on the F650 is returned as 72). These settings are
useful when Analog Input values must be adjusted to fit within certain
ranges in IEC 60870-5-104 masters. Note that a scale factor of 0.1 is
equivalent to a multiplier of 10 (i.e. the value is 10 times larger).
IEC104 IOA BINARIES: Starting Information Object Address for Single Points.
IEC104 IOA DOUBLE POINTS: Starting Information Object Address for Double Points.
IEC104 IOA ANALOGS: Starting Information Object Address for Analog Inputs.
IEC104 IOA COUNTERS: Starting Information Object Address for Counters.
IEC104 IOA COMMANDS: Starting Information Object Address for Single or Double Commands.
IEC104 IOA ANALOG PARAMETERS: Starting Information Object Address for Parameter of measured value.
Each
Measured value has a Parameter of measured value associated with its
threshold.
The F650 relay has a custom Binary Inputs points list, called User Map; it is common for any protocol. In the case of
IEC 104 Protocol, those points are GROUP1 and GROUP2.
The IEC 104 User Map can be configured using the EnerVista 650 Setup software in Setpoint > Relay
Configuration > Control Events.
The User Map contains 128 Binary Inputs. To each point of the User Map, assign any of the binary states of the F650
relay. It is also possible to combine those states using OR and NOT functions. These states are: contact inputs and
outputs, virtual outputs, protection element states, PLC states, etc. The User Map always has a size of 128 Binary
Inputs. Points in the User Map that are not configured have a zero value in the answer.
It is possible to implement more complex logic than simple OR and NOT using the PLC Editor tool in EnerVista 650
Setup in the menu Setpoint > Logic Configuration. These complex signals (Virtual Outputs) can be assigned to
the binary points in the Control Events configuration for the IEC 104 user map.
Groups of Data
The data is organized into groups in order to provide values when the controlling station requests them by a general
or group interrogation.
Group 5 and 6 are set by the120 Analog Inputs, short floating-point (M_ME_NC_1).
Group 7 is set by the 120 Parameter of measured value, short floating-point (P_ME_NC_1).
These 256 Single Points, 16 Double points and 120 Measured Values are also sent as a response to a General
Interrogation.
The 20 Integrated Totals (M_IT_NA_1) has its own Counter Group and it is sent as a response to a General Request
Counter.
Group 1 Status
POINT DESCRIPTION
M_SP_NA_1
1000-1063 CONTROL EVENTS 1-64
Group 2 Status
POINT DESCRIPTION
M_SP_NA_1
1064-1127 CONTROL EVENTS 65-128
Group 3 Status
POINT DESCRIPTION
M_DP_NA_1
1500-1515 SWITCHGEAR EVENTS
Group 4 Status
POINT DESCRIPTION
M_SP_NA_1
1128-1255 BOARD F 1-32, G 1-32, H 1-32, J 1-32
Group 6 Metering
POINT DESCRIPTION
M_ME_NC_1
2060 Fault 1 Prefault Phase AB Voltage Angle
2061 Fault 1 Prefault Phase BC Voltage Magnitude
2062 Fault 1 Prefault Phase BC Voltage Angle
2063 Fault 1 Prefault Phase CA Voltage Magnitude
2064 Fault 1 Prefault Phase CA Voltage Angle
2065 Fault 1 Postfault Phase A Current Magnitude
2066 Fault 1 Postfault Phase A Current Angle
2067 Fault 1 Postfault Phase B Current Magnitude
2068 Fault 1 Postfault Phase B Current Angle
2069 Fault 1 Postfault Phase C Current Magnitude
2070 Fault 1 Postfault Phase C Current Angle
2071 Fault 1 Postfault Phase AB Voltage Magnitude
2072 Fault 1 Postfault Phase AB Voltage Angle
2073 Fault 1 Postfault Phase BC Voltage Magnitude
2074 Fault 1 Postfault Phase BC Voltage Angle
2075 Fault 1 Postfault Phase CA Voltage Magnitude
2076 Fault 1 Postfault Phase CA Voltage Angle
2077 Fault 1 Type
2078 Fault 1 Location
2079 Fault 1 Prefault Ground Current Magnitude
2080 Fault 1 Prefault Ground Current Angle
2081 Fault 1 Prefault Sensitive Ground Current Magnitude
2082 Fault 1 Prefault Sensitive Ground Current Angle
2083 Fault 1 Postfault Ground Current Magnitude
2084 Fault 1 Postfault Ground Current Angle
2085 Fault 1 Postfault Sensitive Ground Current Magnitude
2086 Fault 1 Postfault Sensitive Ground Current Angle
2087 % of Load to Trip
2088 Board F – Analog 1
2089 Board F – Analog 2
2090 Board F – Analog 3
2091 Board F – Analog 4
2092 Board F – Analog 5
2093 Board F – Analog 6
2094 Board F – Analog 7
2095 Board F – Analog 8
2096 Board G – Analog 1
2097 Board G – Analog 2
2098 Board G – Analog 3
2099 Board G – Analog 4
2100 Board G – Analog 5
2101 Board G – Analog 6
2102 Board G – Analog 7
2103 Board G – Analog 8
2104 Board H – Analog 1
2105 Board H – Analog 2
2106 Board H – Analog 3
Group 6 Metering
2107 Board H – Analog 4
2108 Board H – Analog 5
2109 Board H – Analog 6
2110 Board H – Analog 7
2111 Board H – Analog 8
2112 Board J – Analog 1
2113 Board J – Analog 2
2114 Board J – Analog 3
2115 Board J – Analog 4
2116 Board J – Analog 5
2117 Board J – Analog 6
2118 Board J – Analog 7
2119 Board J – Analog 8
Group 7 Deadband
POINT DESCRIPTION
P_ME_NC_1
5000-5119 Analog Input Deadbands 2000-2119
Integrated Totals
POINT DESCRIPTION
M_IT_NA_1
4000-4007 Pulse Counter 1-8
4008-4015 Digital Counters 1-8
4016-4019 Energy Counters
Commands
POINT DESCRIPTION COMMAND MODE
3000 Operation 1 (ON) + Operation 2(OFF) Select and Execute Double Command
--- --- ---
3005 Operation 11 (ON) + Operation 12(OFF) Select and Execute Double Command
3006 Operation 13 (ON) + Operation 14(OFF) Direct Double Command
--- --- ---
3011 Operation 23 (ON) + Operation 24(OFF) Direct Double Command
3012 Virtual Self Reset 1 (ON) + Virtual Self Reset 2(OFF) Direct Double Command
--- --- ---
3027 Virtual Self Reset 31 (ON) + Virtual Self Reset 32(OFF) Direct Double Command
3028-3059 Virtual Latched 1-32 Direct Single Command
There are 24 available operation in F650 device; they must be configured using EnerVista 650 Setup in Setting
The possible selection (blank, X, R, or B) is specified for each specific clause or parameter.
A black check box indicates that the option cannot be selected in this companion standard.
System or device
System definition
Network configuration
(network-specific parameter, all configurations that are used are to be marked "X")
Physical layer
(network-specific parameter, all interfaces and data rates that are used are to be marked "X")
Link layer
(network-specific parameter, all options that are used are to be marked “X”. Specify the maximum frame length. If a
non-standard assignment of class 2 messages is implemented for unbalanced transmission, indicate the Type ID
and COT of all messages assigned to class 2.)
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.
Frame length
When using an unbalanced link layer, the following ASDU types are returned in class 2 messages (low
priority) with the indicated causes of transmission:
Note: (In response to a class 2 poll, a controlled station may respond with class 1 data when there is no
class 2 data available).
Application layer
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively in this companion
standard.
(system-specific parameter, all configurations that are used are to be marked "X")
Cause of transmission
(system-specific parameter, all configurations that are used are to be marked "X")
Length of APDU
(system-specific parameter, specify the maximum length of the APDU per system)
The maximum length of APDU for both directions is 253. It is a fixed system parameter.
In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is permitted.
Either the ASDUs of the set <45> – <51> or of the set <58> – <64> are used.
(station-specific parameter, mark each Type ID "X" if it is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions).
File transfer
(station-specific parameter, mark each Type ID "X" if it is only used in the standard direction, "R" if only
used in the reverse direction, and "B" if used in both directions).
to to
36 41
<1> M_SP_NA_1 X X
<2> M_SP_TA_1
<3> M_DP_NA_1 X X
<4> M_DP_TA_1
<5> M_ST_NA_1
<6> M_ST_TA_1
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1
<10> M_ME_TA_1
<11> M_ME_NB_1
<12> M_ME_TB_1
<13> M_ME_NC_1 X X X
<14> M_ME_TC_1
<15> M_IT_NA_1 X
<16> M_IT_TA_1
<17> M_EP_TA_1
<18> M_EP_TB_1
<19> M_EP_TC_1
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X
<31> M_DP_TB_1
<32> M_ST_TB_1
<33> M_BO_TB_1
<34> M_ME_TD_1
<35> M_ME_TE_1
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X
<38> M_EP_TD_1
<39> M_EP_TE_1
<40> M_EP_TF_1
<45> C_SC_NA_1 X X X X X
<46> C_DC_NA_1 X X X X X
<47> C_RC_NA_1
<48> C_SE_NA_1
<49> C_SE_NB_1
<50> C_SE_NC_1
<51> C_BO_NA_1
<58> C_SC_TA_1 X X X X X
<59> C_DC_TA_1 X X X X X
<60> C_RC_TA_1
Type identification Cause of transmission
1 2 3 4 5 6 7 8 9 10 11 12 13 20 37 44 45 46 47
to to
36 41
<61> C_SE_TA_1
<62> C_SE_TB_1
<63> C_SE_TC_1
<64> C_BO_TA_1
<70> M_EI_NA_1* X
<100> C_IC_NA_1 X X X X X
<101> C_CI_NA_1 X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X
<104> C_TS_NA_1
<105> C_RP_NA_1 X X
<106> C_CD_NA_1
<107> C_TS_TA_1
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1 X X X
<113> P_AC_NA_1
<120> F_FR_NA_1
<121> F_SR_NA_1
<122> F_SC_NA_1
<123> F_LS_NA_1
<124> F_AF_NA_1
<125> F_SG_NA_1
<126> F_DR_TA_1*
<127> F_SC_NB_1*
* Blank or X only
Station initialization
(station-specific parameter, mark "X" if function is used)
X Remote initialization
Read procedure
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions)
X Read procedure
Spontaneous transmission
(station-specific parameter, mark “X” if function is only used in the standard direction, "R" if only used in
the reverse direction, and “B” if used in both directions)
X Spontaneous transmission
(station-specific parameter, mark each information type "X" where both a Type ID without time and corresponding
Type ID with time are issued in response to a single spontaneous change of a monitored object)
The following type identifications may be transmitted in succession caused by a single status change of an
information object. The particular information object addresses for which double transmission is enabled are
defined in a project-specific list.
Station interrogation
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions).
Clock synchronization
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions).
X Spontaneous transmission
Command transmission
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions).
X No additional definition
X Persistent output
X Supervision of maximum delay in command direction of commands and set point commands
X Counter read
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the reverse
direction, and “B” if used in both directions).
X Threshold value
Smoothing factor
Parameter activation
(object-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions).
Test procedure
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions).
Test procedure
File transfer
(station-specific parameter, mark “X” if function is used).
File transfer in monitor direction
Transparent file
Transparent file
Background scan
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in
the reverse direction, and "B" if used in both directions).
Background scan
(station-specific parameter, mark "X" if function is only used in the standard direction, "R" if only used in the
reverse direction, and "B" if used in both directions).
Maximum number of outstanding I format APDUs k and latest acknowledge APDUs (w)
Portnumber
Redundant connections
RFC 2200 is an official Internet Standard which describes the state of standardization of protocols used in
the Internet as determined by the Internet Architecture Board (IAB). It offers a broad spectrum of actual
standards used in the Internet. The suitable selection of documents from RFC 2200 defined in this standard
for a given projects has to be chosen by the user of this standard.
X Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200:
PROCOME PROTOCOL
Procome is an communication protocol focused on control operations. Commands to read data as status,
measurements, events and counters have been implemented together with commands to perform operations and
synchronization.
This procome implementation has a subset of the basic application functions, asdus and services of the whole
procome profile. The protection functionality for procome has not been implemented.
Procome Settings:
When value NONE is selected in the COMM Port setting the protocol is not enabled. The COM1 selection enables
PROCOME for the COM1 (remote) serial port.
Slave Number:is the PROCOME slave number.
Baud rate and parity for COM1 must be set in Setpoint > Communications > Serial Ports.
Procome Configuration:
The procome data configuration is performed through the Setpoint > Procome Configuration tool when
communicating via Ethernet with the device. The procome configuration file can be retrieved and sent to the relay
easily. The relay must be switched off and on to start working with the new procome configuration set by the user.
The relay by default has no procome configuration. For more information about procome configuration see 5.13 IEC
60870-5-103 configuration.
1. PHYSICAL LAYER
Electrical interface
X EIA RS-485
Optical interface
X Glass fiber
X Plastic fiber
Transmission speed
X 9600 bits/s
X 19200 bits/s
2. LINK LAYER
There are no choices for the link layer.
3. APPLICATION LAYER
Transmission mode for application data
Mode 1 (least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively in this companion
standard.
Common address of ASDU
X One COMMON ADDRESS OF ASDU (identical with station address)
X <3> Reset CU
X <4> Start/restart
X <5> Power on
<26> Characteristic 4
<78> Zone 1
<79> Zone 2
<80> Zone 3
<81> Zone 4
<82> Zone 5
<83> Zone 6
Disturbance data
Generic services
Private data
Miscellaneous
Measurand Max. MVAL = times rated value
1,2 or 2,4
Current L1 X
Current L2 X
Current L3 X
Voltage L1-E X
Voltage L2-E X
Voltage L3-E X
Active power P X
Reactive power Q X
Frequency f X
Voltage L1-L2 X
Data is transferred to the primary or control station (master) using the "data acquisition by polling" principle.
Cyclically, the master requests class 2 data to the secondary station (slave). When slave has class 1 data (high
priority) pending, the ACD control bit is set to 1 demanding the master to request for that data. Periodically, the
master can send a General Interrogation in order to update the complete database.
The measurands are sent to the primary station as a response to a class 2 request. There is a setting (0-60 min) in
order to configure the desired interval, where 0 means transmission as fast as possible.
2. Type identification
The implemented Type Identification values are listed below:
TYPE IDENTIFICATION UI8[1..8] <1..255>
<1..31> := definitions of this companion standard (compatible range)
<32..255>:= for special use (private range)
3. Function Type
FUNCTION TYPE UI8 [1..8] <0..255>
The F650 device is identified at the protocol level as "overcurrent protection", so the Function Type <160> is used for
all the digital and analogue points proposed by the standard and mapped in this profile. For the other data supported
by the device, the number can be set from the private range.
4. Information Number
INFORMATION NUMBER := UI8 [1..8] <0..255>
REDUNDANCY PROTOCOL
Industrial real-time Ethernets typically demand much higher availability and uninterrupted operation than office
Ethernet solutions can provide. Even a short loss of connectivity can result in loss of functionality, as for example in
some automation, vehicular, power generation, and power distribution systems.
To recover from a network failure, different standard redundancy schemes are applied such as Parallel Redundancy
Protocol (PRP), High-availability Seamless Redundancy (HSR) and others.
The basic concept of both protocols, PRP and HSR, is to send practically identical frames over different paths and
discard one of the copies in reception, at best. If an error occurs or one of the paths is down, the frame traveling
through that path does not reach the destination, but its copy does.
If the node to be attached to a redundant network has not the capability to do it (e.g. has only one port), it can be
connected through a Redundancy Box (RedBox). This type of node allows single attached nodes connect
transparently to a redundant network. An example can be seen in Figures 1.
PRP operates on two independent networks. Each frame is replicated on the sending node and transmitted over
both networks. The receiving node processes the frame arriving first and discards the subsequent copy. The PRP
layer is responsible for this replicate/discard function and hides the two networks from the upper layers. This scheme
works without explicit reconfiguration and switchover and therefore does not show a period of unavailability.
Figure G-1: Example of PRP with two LANs (LAN A and LAN B)
The two LANs, named LAN_A and LAN_B, are identical in protocol at the MAC level, but they can differ in
performance and topology. Transmission delays can also be different. The LANs have no direct connection among
them and they are assumed to be fail independent.
In some applications, only availability-critical nodes need a double attachment, while others do not. In order to meet
the specific requirements, PRP defines different kinds of end nodes.
• The Dual Attached Node (DAN) is connected to both LANs.
• Uncritical nodes can be attached to only one LAN and are therefore called Single Attached Nodes (SAN). SANs
that need to communicate with each other are on the same LAN.
• The Redundancy Box (RedBox) is used when a single interface node has to be attached to both networks. Such
a node can communicate with all other nodes. Since a node behind a RedBox appears for other nodes like a
DAN, it is called Virtual DANs (VDAN). The RedBox itself is a DAN and acts as a proxy on behalf of its
VDANs. The RedBox has its own IP address for management purposes
Similarly to PRP, HSR is based in the duplication of every frame sent, but in a ring topology. Each copy of the frame
is injected in a different direction of the ring. If any of the links between nodes is down, all nodes are still reachable.
This topology forces every node in the net to be HSR aware because they have to forward every message until it
reaches its destination. With that purpose, the redundancy information is located at the beginning of the frame
allowing a faster forwarding, see next figure.
Definitions:
• PRP – Parallel Redundancy Protocol - redundancy protocol for high availability in substation automation
networks based on IEC 62439-3 Clause 4 and applicable to networks based on Ethernet technology (ISO/IEC
8802-3).
• OSI - Open Systems Interconnection - model defined by the International Organization for Standardization (ISO)
for standardizing the functions of a communication system in terms of abstraction layers. Similar
communication functions are grouped into logical layers. A layer serves the layer above it and is served by the
layer below it. There are 7 layers: physical, data link, network, transport, session, presentation, application.
• DANP – Doubly Attached Node running PRP – a node that has two ports which operate in parallel and are
attached to the upper layers of the OSI communications stack through a Link Redundancy Entity module.
• DANH – Doubly Attached Node with HSR protocol.
• LRE - Link Redundancy Entity – module operating at the link layer of the OSI stack and responsible for handling
duplicates and managing redundancy.
• SAN – Singly Attached Node – regular nodes with non-redundant network adapters
• RedBox – device attaching singly attached nodes (SANs) to a redundant network.
• RCT – Redundancy Check Trailer – PRP trailer added to frames and consisting of the following fields:
– 16-bit sequence number (SeqNr);
– 4-bit LAN identifier (LanId);
– 12 bit frame size (LSDUsize)
– 16-bit suffix (PRPsuffix).
G.1.1 PRP
PRP defines a redundancy protocol for high availability in substation automation networks. It is applicable to
networks based on Ethernet technology (ISO/IEC 8802-3).
PRP is designed to provide seamless recovery in case of a single failure in the network, by using a combination of
LAN duplication and frame duplication technique. Identical frames are sent on two completely independent networks
that connect source and destination, see next figure.
Under normal circumstances both frames reach their destination and one of them is sent up the OSI stack to the
destination application, while the second one is discarded. If an error occurs in one of the networks and traffic is
prevented from flowing on that path, connectivity is still be provided through the other network to ensure continuous
communication. However, care must be taken when designing the two LANs, so that no single point of failure (such
as a common power supply) is encountered, as such scenarios can bring down both LANs simultaneously.
PRP uses specialized nodes called doubly attached nodes (DANPs) for handling the duplicated frames. DANPs
devices have an additional module at the link layer level, called the Link Redundancy Entity (LRE). LRE is
responsible for duplicating frames and adding the specific PRP trailer when sending the frames out on the LAN, as
well as making decisions on received frames as to which one is sent up the OSI stack to the application layer and
which one is discarded. In essence LRE is responsible for making PRP transparent to the higher layers of the stack.
There is a second type of specialized device used in PRP networks, called RedBox, with the role of connecting
Single Attached Nodes (SANs) to a redundant network.
F650 relays implement only the DANP functionality. The RedBox functionality is not implemented.
The original standard IEC 62439-3 (2010) was amended to align PRP with the High availability Seamless
Redundancy (HSR) protocol. To achieve this, the original PRP was modified at the cost of losing compatibility with
the PRP 2010 version. The revised standard IEC 62439-3 (2012) is commonly referred to as PRP-1, while the
original standard is PRP-0. The F650 relays support only PRP-1.
PRP can be enabled in configuration through a setting available on the network configuration menu (Product Setup?
Communication Settings? Network (Ethernet), REDUNDANCY, which already has the capability of enabling Failover
redundancy. When REDUNDANCY is set to PRP, the ports dedicated for PRP operate in redundant mode.
The rights associated with configuring PRP follow the security requirements for network configuration.
PRP management through SNMP MIB is not supported, as F650 doesn’t currently support SNMP for configuration.
Settings and actual values are only available through the front panel and through EnerVista.
The PRP solution to implement must ensure that performance requirements stated in IEC 61850-5 Clause 13 are
still met. It is specified under Clause 13 (Message performance requirements) that messages of type 1A must meet
the performance class P2/3, which is 3ms (See 3.7.1.1).
G.1.2 HSR
HSR defines a redundancy protocol for high availability in substation automation networks, based on PRP principles,
provides the property of zero recovery time, typically used in ring topology but applicable to any topology.
In the F650 relay, HSR is implemented in devices with communication option number K (for Fiber; 100 Base Fx) and
M (for cooper; Base 100 Tx). A frame is sent over both ports. A destination should receive, in the fault-free state, two
identical frames within a certain time skew, forward the first frame to the application and discard the second frame
when (and if) it comes. A sequence number is used to recognize such duplicates.
In contrast to PRP (IEC 62439-3- Clause 4), with which it shares the operating principle, HSR nodes are arranged
into a ring, which allows the network to operate without dedicated switches, since every node is able to forward
frames from port to port. HSR originally meant "High-availability Seamless Ring", but HSR is not limited to a simple
ring topology.
Redundant connections to other HSR rings and to PRP networks are possible.
• Topology changes in STP must be passed to the root bridge before they can be propagated to the network.
Topology changes in RSTP can be originated from and acted upon by any designated switch (bridge), leading
to more rapid propagation of address information
• STP recognizes one state - blocking for ports that should not forward any data or information. RSTP explicitly
recognizes two states or blocking roles - alternate and backup port including them in computations of when to
learn and forward and when to block
• STP relays configuration messages received on the root port going out of its designated ports. If an STP switch
(bridge) fails to receive a message from its neighbor it cannot be sure where along the path to the root a failure
occurred. RSTP switches (bridges) generate their own configuration messages, even if they fail to receive one
from the root bridge. This leads to quicker failure detection
• RSTP offers edge port recognition, allowing ports at the edge of the network to forward frames immediately after
activation while at the same time protecting them against loops
• An improvement in RSTP allows configuration messages to age more quickly preventing them from “going
around in circles” in the event of a loop RSTP has three states. They are discarding, learning and forwarding.
The discarding state is entered when the port is first taken into service. The port does not learn addresses in this
state and does not participate in frame transfer. The port looks for STP traffic in order to determine its role in the
network. When it is determined that the port plays an active part in the network, the state changes to learning. The
learning state is entered when the port is preparing to play an active member of the network. The port learns
addresses in this state but does not participate in frame transfer. In a network of RSTP switches (bridges) the time
spent in this state is usually quite short. RSTP switches (bridges) operating in STP compatibility mode spend
between 6 to 40 seconds in this state. After 'learning' the bridge places the port in the forwarding state. While in this
state the port both learn addresses and participates in frame transfer while in this state. The result of these
enhanced states is that the IEEE 802.1d version of spanning tree (STP) can take a fairly long time to resolve all the
possible paths and to select the most efficient path through the network. The IEEE 802.1w Rapid reconfiguration of
Spanning Tree significantly reduces the amount of time it takes to establish the network path. The result is reduced
network downtime and improved network robustness. In addition to faster network reconfiguration, RSTP also
implements greater ranges for port path costs to accommodate the higher connection speeds that are being
implemented.
Proper implementations of RSTP (by switch vendors) is designed to be compatible with IEEE 802.1d STP. GE
recommends that you employ RSTP or STP in your network.
Ports A and B use port A’s MAC and IP address settings while port B is in standby mode in that it does not actively
communicate on the Ethernet network but monitors its link.
PICKUPS
104
PH TOC1 HIGH PKP 40
105 319
VO_053_51P_PKP
PH TOC2 HIGH PKP inOR1 OR6 outOR1
106 inOR2
PH TOC3 HIGH PKP
316 inOR3
318 inOR6
PH TOC3 LOW PKP
101
39
PH IOC1 HIGH PKP 11
VO_051_50PH_PKP
102 inOR1 OR3 outOR1
PH IOC2 HIGH PKP
inOR2
103
PH IOC3 HIGH PKP inOR3
98 38
PH IOC1 LOW PKP 10
VO_050_50PL_PKP
99 inOR1 OR3 outOR1
PH IOC2 LOW PKP
100 inOR2
95 37
GROUND TOC1 PKP 1
VO_049_51G_PKP
96 inOR1 OR3 outOR1
GROUND TOC2 PKP
inOR2
97
GROUND TOC3 PKP inOR3
92
GROUND IOC1 PKP 36
0
VO_048_50G_PKP
93 inOR1 OR3 outOR1
GROUND IOC2 PKP
inOR2
94
GROUND IOC3 PKP inOR3
220 219
VO 049 51G PKP OR 221
VO_049_51G_PKP OR 221
222 VO_009_GR OUND_OVERCURRENT_PKP
VO_048_50G_PKP
191 195
SENS GND TOC1 PKP 187
VO_003_51SG_PKP
192 inOR1 OR3 outOR1
SENS GND TOC2 PKP
inOR2
193
SENS GND TOC3 PKP inOR3
188
194
SENS GND IOC 1 PKP 186
VO_002_50SG_PKP
189 inOR1 OR3 outOR1
SENS GND IOC 2 PKP
inOR2
190
SENS GND IOC 3 PKP inOR3
173
ISOLATED GND1 PKP 172
171
VO_043_50IG_PKP
OVERCURRENT 174 inOR1 OR3 outOR1
PICKUPS ISOLATED GND2 PKP
175 inOR2
231 inOR2
VO_009_GR OUND_OVERCURR ENT_PKP
228
232 inOR3
VO_011_ALL_OVERCURRENT_PKP
VO_010_SENSITIVE_GROUND_PKP inOR4
233
VO_006_I2_TOC_PKP inOR5
309 inOR6
VO_001_THERMAL_ALARM
86
34
PH ASE UV1 PKP 2
VO_045_27P_PKP
87 inOR1 OR3 outOR1
PH ASE UV2 PKP
inOR2
88
PHASE UV3 PKP inOR3
89
35
PH ASE OV1 PKP 3
VO_046_59P_PKP
90 inOR1 OR3 outOR1
PH ASE OV2 PKP
inOR2
91
PH ASE OV3 PKP inOR3
235
NEUTRAL OV1 HIGH PKP 254
234
VO_012_59NH_PKP
236 inOR1 OR3 outOR1
NEUTRAL OV2 HIGH PKP
237 inOR2
NEUTRAL OV3 HIGH PKP
inOR3
238
NEUTRAL OV1 LOW PKP 255
250
VO_013_59NL_PKP
239 inOR1 OR3 outOR1
NEUTRAL OV2 LOW PKP
inOR2
240
NEUTRAL OV3 LOW PKP inOR3
241
256
AUXILIARY UV1 PKP 252
VO_014_27X_PKP
242 inOR1 OR3 outOR1
VOLTAGE AUXILIARY UV2 PKP
260 InOR3
VO_012_59NH_PKP
261 InOR4
VO_013_59NL_PKP InOR5
263
InOR6
VO_015_59X_PKP
264 InOR7
VO_016_V2_OV_PKP
107
OVERFREQ1 PKP 41
108 515
VO_054_81O_PKP
OVERFREQ2 PKP inOR1 OR6 outOR1
109
inOR2
OVERFREQ3 PKP
513 inOR3
110
42
UNDERFREQ1 PKP 516
VO_055_81U_PKP
111 inOR1 OR6 outOR1
UNDERFREQ2 PKP
inOR2
112
FREQUENCY UNDERFREQ3 PKP inOR3
PICKUPS 514
inOR4
UNDERFREQ4 PKP
519
inOR5
UNDERFREQ5 PKP
520 inOR6
UNDERFREQ6 PKP
406 409
405
FREQ RATE1 PKP VO_052_81DF-DT PKP
407 inOR1 OR3 outOR1
FREQ RATE2 PKP
408 inOR2
FREQ RATE3 PKP
inOR3
411 45
410
VO_052_81DF-DT PKP VO_056_ALL_FREQUENCY_PKP
43 inOR1 OR3 outOR1
VO_054_81O_PKP
44 inOR2
VO_055_81U_PKP
inOR3
270
BROKEN CONDUCT1 PKP 273
269
VO_018_BROKEN_CONDUCTOR_PKP
271 inOR1 OR3 outOR1
BROKEN
BROKEN CONDUCT2 PKP
CONDUCTOR inOR2
272
BROKEN CONDUCT3 PKP inOR3
343
343
FWD PW R1 STG1 PKP 349
344 342
VO_023_FORWARD_POWER_PKP
FWD PW R1 STG2 PKP inOR1 OR6 outOR1
345
inOR2
FWD PW R2 STG1 PKP
FORW ARD inOR3
346
POWER
FWD PW R2 STG2 PKP inOR4
347
FWD PW R3 STG1 PKP inOR5
348 inOR6
FWD PW R3 STG2 PKP
386
366
DIR PW R1 STG PKP 369
VO_025_DIRECTIONAL_POWER_PKP
DIRECTIONAL 367 inOR1 OR3 outOR1
POWER DIR PW R2 STG PKP
368 inOR2
DIR PW R3 STG PKP
inOR3
440 447
439
32N1 HIGH PKP VO_092_32N_HIGH_PKP
441 inOR1 OR3 outOR1
32N2 HIGH PKP
442 inOR2
WATTIMETRIC 32N3 HIGH PKP
GROUND 443 inOR3 448
FAULT PKP 446
32N1 LOW PKP VO_093_32N_LOW_PKP
444 inOR1 OR3 outOR1
32N2 LOW PKP
445 inOR2
32N3 LOW PKP
inOR3
370 373
464
VO_023_FORWARD_POWER_PKP VO_026_POWER_PKP
371 inOR1 OR4 outOR1
VO_025_DIRECTIONAL_POWER_PKP
POWER 462 inOR2
VO_092_32N_HIGH_PKP
463 inOR3
VO_093_32N_LOW_PKP
inOR4
389 392
388
LOCKED ROTOR1 PKP VO_029_LOCKED_ROTOR_PKP
390 inOR1 OR3 outOR1
LOCKED
ROTOR LOCKED ROTOR2 PKP
391 inOR2
LOCKED ROTOR3 PKP
inOR3
414 417
413
LOAD LOAD ENCR1 PKP VO_031_LOAD_ENCROACHMENT_PKP
415 inOR1 OR3 outOR1
ENCROACHMENT LOAD ENCR2 PKP
PICKUP 416 inOR2
LOAD ENCR3 PKP
inOR3
274 85
419
VO_011_ALL_OVERCURRENT_PKP VO_085_GENERAL_PKP
275 InOR1 OR7 OutO R1
VO_017_ALL_VOLTAGE_PKP
276 InOR2
VO_056_ALL_FREQUENC Y_PKP
277 InOR3
GENERAL VO_018_BROKEN_CONDUCTOR_PKP
PICKUP 374 InOR4
VO_026_POWER_PKP
400 InOR5
VO_029_LOCKED_ROTOR_PKP
418 InOR6
VO_031_LOAD_ENCROACHMENT_PKP
InOR7
TRIPS
113
PH TOC1 HIGH OP 46
114 312
VO_057_51P_TRIP
PH TOC2 HIGH OP inOR1 OR6 outOR1
115
inOR2
PH TOC3 HIGH OP
313 inOR3
315 inOR6
PH TOC3 LOW OP
116
PH IOC1 HIGH OP 47
12
VO_058_50PH_TRIP
117 inOR1 OR3 outOR1
PH IOC2 HIGH OP
inOR2
118
PH IOC3 HIGH OP inOR3
119
48
PH IOC1 LOW OP 29
VO_059_50PL_TRIP
120 inOR1 OR3 outOR1
PH IOC2 LOW OP
inOR2
121
PH IOC3 LOW OP inOR3
125
50
THERMAL1 OP 13
VO_062_THERMAL_TRIP
126 inOR1 OR3 outOR1
THERMAL2 OP
inOR2
127
OVERCURRENT
THERMAL3 OP inOR3
TRIPS
280
279
VO_057_51P_TRIP 307
VO_019_PHASE_OVERCURRENT_TRIP
281 inOR1 OR3 outOR1
VO_058_50PH_TRIP
inOR2
282
VO_059_50PL_TRIP inOR3
131
52
NEUTRAL TOC1 OP 8
VO_065_51N_TRIP
133 inOR1 OR3 outOR1
NEUTRAL TOC2 OP
inOR2
132
NEUTRAL TOC3 OP inOR3
128
51
NEUTRAL IOC1 OP 7
VO_064_50N_TRIP
129 inOR1 OR3 outOR1
NEUTRAL IOC2 OP
inOR2
130
NEUTRAL IOC3 OP inOR3
54 9
VO_064_50N_TRIP OR 53
55 VO_066_NEUTRAL_OVERCURRENT_TRIP
VO_065_51N_TRIP
137
GROUND TOC1 OP 56
14
VO_067_51G_TRIP
138 inOR1 OR3 outOR1
GROUND TOC2 OP
139 inOR2
134
57
GROUND IOC1 OP 15
VO_068_50G_TRIP
135 inOR1 OR3 outOR1
GROUND IOC2 OP
inOR2
136
GROUND IOC3 OP inOR3
59 16
VO_067_51G_TRIP OR 58
60 VO_069_GROUND_OVERCURRENT_TR IP
VO_068_50G_TRIP
143
SENS GND TOC1 OP 61
18
VO_070_51SG_TRIP
144 inOR1 OR3 outOR1
SENS GND TOC2 OP
inOR2
145
SENS GND TOC3 OP inOR3
140
62
SENS GND IOC 1 OP 17
VO_071_50SG_TRIP
141 inOR1 OR3 outOR1
SENS GND IOC2 OP
inOR2
142
SENS GND IOC 3 OP inOR3
177
180
ISOLATED GND1 OP 176
VO_044_50IG_TRIP
178 inOR1 OR3 outOR1
OVERCURRENT ISOLATED GND2 OP
inOR2
TRIPS 179
ISOLATED GND3 OP inOR3
64
63
VO_070_51SG_TRIP 170
VO_072_SENSITIVE_GROUND_TRIP
65 inOR1 OR3 outOR1
VO_071_50SG_TRIP
inOR2
181
VO_044_50IG_TRIP inOR3
122
49
NEG SEQ TOC1 OP 4
VO_061_I2_TOC_TRIP
123 inOR1 OR3 outOR1
NEG SEQ TOC2 OP
inOR2
124
NEG SEQ TOC3 OP inOR3
284
VO_019_PHASE_OVERCURRENT_TRIP
285 310
VO_066_NEUTRAL_OVERCURRENT_TRIP
inOR1 OR6 outOR1
286
inOR2
VO_069_GROUND_OVERCURR ENT_TRIP
287 inOR3
VO_072_SENSITIVE_GROUND_TRIP
inOR4
288
283
VO_061_I2_TOC_TRIP inOR5
VO_020_ALL_OVERCURRENT_TRIP
311
inOR6
VO_062_THERMAL_TRIP
146
66
PHASE UV1 OP 5
VO_073_27P_TRIP
147 inOR1 OR3 outOR1
PHASE UV2 OP
148 inOR2
VO_075_59NH_TRIP InOR4
76
InOR5 72
VO_076_59NL_TRIP
VO_079_ALL_VOLTAGE_TRIP
77 InOR6
VO_077_59X_TRIP
InOR7
294
VO_021_V2_OV_TRIP
164
OVERFREQ1 OP
165 508 79
OVERFREQ2 OP inOR1 OR6 outOR1 VO_080_81O_TRIP
166 inOR2
OVERFREQ3 OP
505 inOR3
OVERFREQ4 OP
inOR4
506
OVERFREQ5 OP inOR5
507
inOR6
OVERFREQ6 OP
167
UNDERFREQ1 OP
512 80
168
inOR1 OR6 outOR1 VO_081_81U_TRIP
UNDERFREQ2 OP
169 inOR2
UNDERFREQ3 OP
FREQUENCY inOR3
TRIPS 509
UNDERFREQ4 OP inOR4
510
UNDERFREQ5 OP inOR5
511 inOR6
UNDERFREQ6 OP
UNDERFREQ6 OP
425 428
423
FREQ RATE1 OP VO_060_81DF-DT OP
426 inOR1 OR3 outOR1
FREQ RATE2 OP
427 inOR2
FREQ RATE3 OP
inOR3
82 81
424
VO_080_81O_TRIP VO_082_ALL_FREQUENCY_TRIP
83 inOR1 OR3 outOR1
VO_081_81U_TRIP
429 inOR2
VO_060_81DF-DT OP
inOR3
298
BROKEN CONDUCT1 OP 301
297
VO_022_BROKEN_CONDUCTOR_TRIP
299 inOR1 OR3 outOR1
BROKEN
CONDUCTOR BROKEN CONDUCT2 OP
inOR2
300
BROKEN CONDUCT3 OP inOR3
353
FWD PW R1 STG1 OP 359
354 352
VO_024_FORWARD_POWER_TRIP
FWD PW R1 STG2 OP inOR1 OR6 outOR1
355 inOR2
FWD PW R2 STG1 OP
FORW ARD inOR3
356
POWER
FWD PW R2 STG2 OP inOR4
357
inOR5
FWD PW R3 STG1 OP
358 inOR6
FWD PW R3 STG2 OP
376
380
DIR PW R1 STG OP 379
VO_027_DIRECTIONAL_POWER_TRIP
377 inOR1 OR3 outOR1
DIRECTIONAL
DIR PW R2 STG OP
POWER inOR2
378
DIR PW R3 STG OP inOR3
467 470
466
32N1 HIGH OP VO_096_32N_HIGH_TRIP
468 inOR1 OR3 outOR1
32N2 HIGH OP
469 inOR2
32N3 HIGH OP
WATTIMETRIC inOR3
GROUND
476 472
FAULT 471
32N1 LOW OP VO_097_32N_LOW_TRIP
477 inOR1 OR3 outOR1
32N2 LOW OP
478 inOR2
32N3 LOW OP
inOR3
382 384
475
VO_024_FORWARD_POWER_TRIP VO_028_POWER _TRIP
383 inOR1 OR4 outOR1
VO_027_DIRECTIONAL_POWER_TRIP
POWER 473 inOR2
VO_096_32N_HIGH_TRIP
474 inOR3
VO_097_32N_LOW_TRIP
inOR4
395 398
394
LOCKED ROTOR1 OP VO_030_LOCKED_ROTOR_TRIP
396 inOR1 OR3 outOR1
LOCKED
ROTOR LOCKED ROTOR2 OP
397 inOR2
LOCKED ROTOR3 OP
inOR3
431 435
434
LOAD VO_032_LOAD_ENCROACHMENT_TRIP
LOAD 432 ENCR1 OP inOR1 OR3 outOR1
ENCROACHMENT LOAD ENCR2 OP
TRIP 433 inOR2
LOAD ENCR3 OP
inOR3
302 84
436
VO_020_ALL_OVERCURRENT_TRIP VO_083_GENERAL_TRIP
304 InOR1 OR7 OutO R1
VO_079_ALL_VOLTAGE_TRIP
305 InOR2
VO_082_ALL_FREQUENC Y_TRIP
303 InOR3
GENERAL
VO_022_BROKEN_CONDUCTOR_TRIP
TRIP
TRIP 385
385 InOR4
InOR4
VO_028_POWER_TRIP
399 InOR5
VO_030_LOCKED_ROTOR_TRIP
437 InOR6
VO_032_LOAD_ENCROACHMENT_TRIP
InOR7
InOR4
BOARD STATUS ALARM
491 InOR5
(CRITICAL TO OPERATION)
NOT
488
BOARD F STATUS
522
ORDERCODE ERROR
498
VO_000_PROTECTION_ALAR M
DELAY
494 497
VO_098_ALARM T_Input Timer(Pkp-Dpt) T_Output
495
T_Pi ckup
503
10000
VO_099_PROT_ALARM
496 T_Dropout
0
**For firmware versions 7.00 or higher; the Network settings are the ethernet communication parameters are as follow
**For firmware versions 7.00 or higher; on the Network settings are also located the settings for Redundancy.
User
Setting Description Name Default Value Step Range
Value
Function permission REDUNDANCY INDEPENDE N/A [INDEPENDENT; LLA;
MODE NT PRP; HSR; RSTP;
DAISY_CHAIN]
Establish priority for Port A LLA Priority DISABLED N/A [ENABLED; DISABLED]
Switch over time from port B to port A LLA Timeout 5000 N/A [0 : 600000]
Switch (bridge) priority value RSTP BRIDGE 32768 N/A [0 : 61440]
PRIORITY
determine which ports are used for RSTP PORT A 128 N/A [0 : 240]
forwarding PRIORITY
assigned port cost value used for the RSTP PORT A 200000 N/A [0 : 2000000]
switch PATHCOST
Determine which ports are used for RSTP PORT B 128 N/A [0 : 240]
forwarding PRIORITY
Assigned port cost value used for the RSTP PORT B 200000 N/A [0 : 2000000]
switch PATHCOST
1st Octect of IP address of DNP master 2 IP Addr Client2 Oct1 0 N/A [0 : 255]
2nd Octect of IP address of DNP master 2 IP Addr Client2 Oct2 0 N/A [0 : 255]
3nd Octect of IP address of DNP master 2 IP Addr Client2 Oct3 0 N/A [0 : 255]
4th Octect of IP address of DNP master 2 IP Addr Client2 Oct4 0 N/A [0 : 255]
1st Octect of IP address of DNP master 3 IP Addr Client3 Oct1 0 N/A [0 : 255]
2nd Octect of IP address of DNP master 3 IP Addr Client3 Oct2 0 N/A [0 : 255]
3nd Octect of IP address of DNP master 3 IP Addr Client3 Oct3 0 N/A [0 : 255]
4th Octect of IP address of DNP master 3 IP Addr Client3 Oct4 0 N/A [0 : 255]
1st Octect of IP address of DNP master 4 IP Addr Client4 Oct1 0 N/A [0 : 255]
2nd Octect of IP address of DNP master 4 IP Addr Client4 Oct2 0 N/A [0 : 255]
3nd Octect of IP address of DNP master 4 IP Addr Client4 Oct3 0 N/A [0 : 255]
4th Octect of IP address of DNP master 4 IP Addr Client4 Oct4 0 N/A [0 : 255]
1st Octect of IP address of DNP master 4 IP Addr Client5 Oct1 0 N/A [0 : 255]
2nd Octect of IP address of DNP master 4 IP Addr Client5 Oct2 0 N/A [0 : 255]
3nd Octect of IP address of DNP master 4 IP Addr Client5 Oct3 0 N/A [0 : 255]
4th Octect of IP address of DNP master 4 IP Addr Client5 Oct4 0 N/A [0 : 255]
TCP/UDP port number for DNP over TCP/UDP Port 20000 N/A [0 : 65535]
Ethernet
Unsolicited responses permission Unsol Resp Function DISABLED N/A [DISABLED – ENABLED]
Time out to confirm an unsolicited Unsol Resp TimeOut 5 1s [0 : 60]
response
Number of retransmissions of an unsol Unsol Resp Max Ret 10 N/A [0 : 255]
resp w/o confirmation
Address to which all unsolicited Unsol Resp Dest Adr 200 N/A [0 : 65519]
responses are sent
Scale for currents Current Scale Factor 1 N/A [0.00001-0.0001-0.001-
0.01-0.1-1-10-100-1000]
Scale for voltages Voltage Scale Factor 1 N/A [0.00001-0.0001-0.001-
0.01-0.1-1-10-100-1000]
Product Setup > Communication Settings > DNP3 Slave (CONT.)
DNP3 Slave 1 > DNP3 Slave 2 > DNP3 Slave 3
User
Setting Description Name Default Value Step Range
Value
Scale for power Power Scale Factor 1 N/A [0.00001-0.0001-0.001-
0.01-0.1-1-10-100-1000]
Scale for energy Energy Scale Factor 1 N/A [0.00001-0.0001-0.001-
0.01-0.1-1-10-100-1000]
Other Scale factor Other Scale Factor 1 N/A [0.00001-0.0001-0.001-
0.01-0.1-1-10-100-1000]
Default deadband for Current Analog Current Deadband 30000 N/A [0 : 65535]
Input points to trigger unsolicited
responses
Default deadband for Voltage Analog Voltage Deadband 30000 N/A [0 : 65535]
Input points to trigger unsolicited
responses
Default deadband for Power Analog Input Power Deadband 30000 N/A [0 : 65535]
points to trigger unsolicited responses
Default deadband for Energy Analog Energy Deadband 30000 N/A [0 : 65535]
Input points to trigger unsolicited
responses
Default deadband for Other Analog Input Other Deadband 30000 N/A [0 : 65535]
points to trigger unsolicited responses
Size (in bytes) for message fragmentation Msg Fragment Size 240 1 byte [30 : 2048]
DNP Analog Input Points point list Analog Input Point 22 End of list N/A
DNP Analog Input Points point list Analog Input Point 23 End of list N/A
DNP Analog Input Points point list Analog Input Point 24 End of list N/A
DNP Analog Input Points point list Analog Input Point 25 End of list N/A
DNP Analog Input Points point list Analog Input Point 26 End of list N/A
DNP Analog Input Points point list Analog Input Point 27 End of list N/A
DNP Analog Input Points point list Analog Input Point 28 End of list N/A
DNP Analog Input Points point list Analog Input Point 29 End of list N/A
DNP Analog Input Points point list Analog Input Point 30 End of list N/A
DNP Analog Input Points point list Analog Input Point 31 End of list N/A
DNP Notes
Note 1: Scale Factor Note that a scale factor of 0.1 is equivalent to a multiplier of 10 (i.e. the value is 10
[NOT USED, CTL EVENTS 1-16, CTL EVENTS 17-32, CTL EVENTS 33-48,CTL
Note 2: Binary Input Block Selection: EVENTS 49-64, CTL EVENTS 65-80, CTL EVENTS 81-96, CTL EVENTS 97-112,
sets the gateway to reach the destination Static RT3 GWY 0 1 [0 : 255]
IP route Oct3
sets the gateway to reach the destination Static RT3 GWY 0 1 [0 : 255]
IP route Oct4
sets the destination IPv4 route Static RT4 IP Oct1 0 1 [0 : 255]
sets the destination IPv4 route Static RT4 IP Oct2 0 1 [0 : 255]
sets the destination IPv4 route Static RT4 IP Oct3 0 1 [0 : 255]
sets the destination IPv4 route Static RT4 IP Oct4 0 1 [0 : 255]
sets the IP mask associated with the Static RT4 Mask 0 1 [0 : 255]
route Oct1
sets the IP mask associated with the Static RT4 Mask 0 1 [0 : 255]
route Oct2
sets the IP mask associated with the Static RT4 Mask 0 1 [0 : 255]
route Oct3
sets the IP mask associated with the Static RT4 Mask 0 1 [0 : 255]
route Oct4
sets the gateway to reach the destination Static RT4 GWY 0 1 [0 : 255]
IP route Oct1
sets the gateway to reach the destination Static RT4 GWY 0 1 [0 : 255]
IP route Oct2
sets the gateway to reach the destination Static RT4 GWY 0 1 [0 : 255]
IP route Oct3
sets the gateway to reach the destination Static RT4 GWY 0 1 [0 : 255]
IP route Oct4
sets the destination IPv4 route Static RT5 IP Oct1 0 1 [0 : 255]
sets the destination IPv4 route Static RT5 IP Oct2 0 1 [0 : 255]
sets the destination IPv4 route Static RT5 IP Oct3 0 1 [0 : 255]
sets the destination IPv4 route Static RT5 IP Oct4 0 1 [0 : 255]
sets the IP mask associated with the Static RT5 Mask 0 1 [0 : 255]
route Oct1
sets the IP mask associated with the Static RT5 Mask 0 1 [0 : 255]
route Oct2
sets the IP mask associated with the Static RT5 Mask 0 1 [0 : 255]
route Oct3
sets the IP mask associated with the Static RT5 Mask 0 1 [0 : 255]
route Oct4
sets the gateway to reach the destination Static RT5 GWY 0 1 [0 : 255]
IP route Oct1
sets the gateway to reach the destination Static RT5 GWY 0 1 [0 : 255]
IP route Oct2
sets the gateway to reach the destination Static RT5 GWY 0 1 [0 : 255]
IP route Oct3
sets the gateway to reach the destination Static RT5 GWY 0 1 [0 : 255]
IP route Oct4
sets the destination IPv4 route Static RT6 IP Oct1 0 1 [0 : 255]
sets the destination IPv4 route Static RT6 IP Oct2 0 1 [0 : 255]
sets the destination IPv4 route Static RT6 IP Oct3 0 1 [0 : 255]
sets the destination IPv4 route Static RT6 IP Oct4 0 1 [0 : 255]
sets the IP mask associated with the Static RT6 Mask 0 1 [0 : 255]
route Oct1
sets the IP mask associated with the Static RT6 Mask 0 1 [0 : 255]
route Oct2
sets the IP mask associated with the Static RT6 Mask 0 1 [0 : 255]
route Oct3
sets the IP mask associated with the Static RT6 Mask 0 1 [0 : 255]
route Oct4
sets the gateway to reach the destination Static RT6 GWY 0 1 [0 : 255]
IP route Oct1
sets the gateway to reach the destination Static RT6 GWY 0 1 [0 : 255]
IP route Oct2
sets the gateway to reach the destination Static RT6 GWY 0 1 [0 : 255]
IP route Oct3
sets the gateway to reach the destination Static RT6 GWY 0 1 [0 : 255]
IP route Oct4
SETPOINT > Product Setup > Modbus User Map
User
Setting Description Name Default Value Step Range
Value
Address 00 for Modbus user map Address 00 0 N/A [0000 : FFFF]
Address 01 for Modbus user map Address 01 0 N/A [0000 : FFFF]
... ... ...
Address 254 for Modbus user map Address 254 0 N/A [0000 : FFFF]
Address 255 for Modbus user map Address 255 0 N/A [0000 : FFFF]
Setpoint > Protection Elements > Phase Current > Phase Directional >
Phase Directional 1> Phase Directional 2 > Phase Directional 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Maximum Torque Angle MTA 45 1 Deg [-90 : +90]
Operation Direction Direction FORWARD N/A [FORWARD – REVERSE]
Block logic Block Logic PERMISSION N/A [BLOCK – PERMISSION]
Polarization voltage threshold Pol V Threshold 40 1V [0 : 300]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Voltage Memory Voltage Memory 0,00 s 0,01 s [0,00 : 3,00]
Setpoint > Protection Elements > Phase Current > Thermal Model >
Thermal Model 1 > Thermal Model 2 > Thermal Model 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Heating constant Heat Time Constant 6.0 0.1 min [3.0 : 600.0]
Cooling constant Cool Time Constant 2.00 0.01 times [1.00 : 6.00]
Heat Time
Ct.
Pickup level Pickup Level 1.00 0.01 A [0.05 : 160.00]
Alarm level Alarm Level 80.0 0.10% [1.0 : 110.0]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Neutral Current > Neutral TOC
Neutral TOC 1> Neutral TOC 2 > Neutral TOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Neutral Current > Neutral IOC
Neutral IOC 1 > Neutral IOC 2 > Neutral IOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Pickup level Pickup Level 30.00 0.01 A [0.05 : 160.00]
Trip time Trip Delay 0.00 0.01 s [0.00 : 900.00]
Reset time Reset Delay 0.00 0.01 s [0.00 : 900.00]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Neutral Current > Neutral Directional >
Neutral Directional 1 > Neutral Directional 2 > Neutral Directional 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Maximum Torque Angle MTA -45 1 Deg [-90 : +90]
Operation Direction Direction FORWARD N/A [FORWARD – REVERSE]
Polarization type Polarization VO N/A [V0 – IP – V0+IP – V0*IP ]
Block logic type Block Logic PERMISSION N/A [BLOCK – PERMISSION]
Polarization voltage threshold Pol V Threshold 10 1V [0 : 300]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Ground Current > Ground TOC
Ground TOC 1 > Ground TOC 2 > Ground TOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Input type Input PHASOR(DF N/A [PHASOR – RMS]
T)
Pickup level Pickup Level 1.00 0.01 A [0.05 : 160.00]
Curve shape Curve IEEE Ext Inv N/A [See list of curves]
Time Dial TD Multiplier 1.00 0.01 s [0.00 : 900.00]
Reset type Reset INSTANTANE N/A [INSTANTANEOUS –
OUS LINEAR]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Ground Current > Ground IOC
Ground IOC 1 > Ground IOC 2 > Ground IOC 3
User
Setting Description Name Default Value Step Range
Value
Setpoint > Protection Elements > Ground Current > Ground Directional >
Ground Directional 1 > Ground Directional 2 > Ground Directional 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Maximum Torque Angle MTA -45 1 Deg [-90 : +90]
Operation Direction Direction FORWARD N/A [FORWARD – REVERSE]
Polarization type Polarization VO N/A [V0 – IP – V0+IP – V0*IP ]
Block logic type Block Logic PERMISSION N/A [BLOCK – PERMISSION]
Polarization voltage threshold Pol V Threshold 10 1V [0 : 300]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Sensitive Ground Current > Sensitive Ground TOC
Sensitive Ground TOC 1 > Sensitive Ground TOC 2 > Sensitive Ground TOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Input type Input PHASOR(DF N/A [PHASOR – RMS]
T)
Pickup level Pickup Level 0.050 0.001 A [0.005 : 16.000]
Curve shape Curve IEEE Ext Inv N/A [See list of curves]
Time Dial TD Multiplier 1.00 0.01 s [0.00 : 900.00]
Reset type Reset INSTANTANE N/A [INSTANTANEOUS –
OUS LINEAR]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Sensitive Ground Current > Sensitive Ground IOC
Sensitive Ground IOC 1 > Sensitive Ground IOC 2 > Sensitive Ground IOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Input type Input PHASOR(DF N/A [PHASOR – RMS]
T)
Pickup level Pickup Level 0.100 0.001 A [0.005 : 16.000]
Trip time Trip Delay 0.00 0.01 s [0.00 : 900.00]
Reset time Reset Delay 0.00 0.01 s [0.00 : 900.00]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Sensitive Ground Current > Isolated Ground IOC
Isolated Ground IOC 1 > Isolated Ground IOC 2 > Isolated Ground IOC 3
User
Setting Description Name Default Value Step Range
Value
Function Permission Function DISABLED N/A [DISABLED – ENABLED]
High Voltage level Vh Level 20 1V [2 : 70]
Low Current level Il LEVEL 0.005 0.001 A [0.005 : 0.400]
Low Voltage level Vl LEVEL 2 1V [2 : 70]
High Current level Ih LEVEL 0.025 0.001 A [0.005 : 0.400]
Operation time Delay 0.00 0.01 s [0.00 : 900.00]
Deviation time to instantaneous Time to inst 0.00 0.01 s [0.00 : 900.00]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Sensitive Ground Current > Sensitive Ground Directional >
Sensitive Ground Directional 1 > Sensitive Ground Directional 2 > Sensitive Ground Directional 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Maximum Torque Angle MTA -45 1 Deg [-90 : +90]
Operation Direction Direction FORWARD N/A [FORWARD – REVERSE]
Block logic type Block Logic PERMISSION N/A [BLOCK – PERMISSION]
Polarization voltage threshold Pol V Threshold 10 1V [0 : 300]
Snapshot event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Negative Sequence Current > Negative Sequence TOC >
Negative Sequence TOC 1 > Negative Sequence TOC 2 > Negative Sequence TOC 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Pickup level Pickup Level 1.00 0.01 A [0.05 : 160.00]
Curve shape Curve IEEE Ext Inv N/A [See list of curves]
Time Dial TD Multiplier 1.00 0.01 s [0.00 : 900.00]
Reset type Reset INSTANTANE N/A [INSTANTANEOUS –
OUS LINEAR]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Voltage Elements > Phase UV >
Phase UV 1 > Phase UV 2 > Phase UV 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Input mode Mode PHASE- N/A [PHASE-PHASE,
PHASE PHASE-GROUND]
Pickup Level Pickup Level 10 1V [3 : 300]
Curve shape Curve DEFINITE N/A [DEFINITE TIME –
TIME INVERSE TIME]
Time Dial Delay 10.00 0.01 s [0.00 : 900.00]
Minimum Voltage Threshold Minimum Voltage 5 1V [0 : 300]
Operation logic Logic ANY PHASE N/A [ANY PHASE – TWO
PHASES – ALL PHASES]
Supervision by breaker status Supervised by 52 DISABLED N/A [DISABLED – ENABLED]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > Voltage Elements > Phase OV >
Phase OV 1 > Phase OV 2 > Phase OV 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Pickup Level Pickup Level 10 1V [3 : 300]
Trip time Trip Delay 10.00 0.01 s [0.00 : 900.00]
Reset time Reset Delay 0.00 0.01 s [0.00 : 900.00]
Operation logic Logic ANY PHASE N/A [ANY PHASE – TWO
PHASES – ALL PHASES]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Setpoint > Protection Elements > voltage elements > Negative Sequence OV >
Negative Sequence OV 1 > Negative Sequence OV 2 > Negative Sequence OV 3
User
Setting Description Name Default Value Step Range
Value
Function permission Function DISABLED N/A [DISABLED – ENABLED]
Pickup Level Pickup Level 10 1V [3 : 300]
Trip time Trip Delay 10.00 0.01 s [0.00 : 900.00]
Reset time Reset Delay 0.00 0.01 s [0.00 : 900.00]
Snapshot Event generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
[INCREASING -
Direction of the frequency change Freq. Rate Trend INCREASING N/A DECREASING - BI-
DIRECTIONAL]
Operation Value in Hz/s Freq. Rate Pickup 0.50 0.01 Hz/s [0.10 : 10.00]
Minimum required voltage in % nominal
Freq. Rate OV Supv 40.00 0.01% [0.00 : 110.00]
voltage
Minimum Frequency Threshold Freq. Rate Min 45.00 0.01 Hz [20.00 : 80.00]
Maximum Frequency Threshold Freq. Rate Max 65.00 0.01 Hz [20.00 : 80.00]
Frequency rate Trip Delay Freq. Rate Delay 0.00 0.01 s [0.00 : 60.00]
Snapshot Events Generation Snapshot Events ENABLED N/A [DISABLED – ENABLED]
Is the name used for the different outputs in I/O boards, 8 outputs available for any of
0Z
the two types of board (01,…., 08)
SOURCE COLUMN
This column allows the user to select the simple or complex (OR signal/virtual output) operand that activates the
selected elements for configuration of the relay.
If more than one operand is selected, the relay performs an OR gate to activate the selected element.
Appendix J: Miscellaneous
MISCELLANEOUS
J.1 Warranty
For products shipped as of 1 October 2013, GE VERNOVA warrants most of its GE VERNOVA manufactured
products for 10 years. For warranty details including any limitations and disclaimers, see our Terms and Conditions
at:
https://www.gevernova.com/grid-solutions/multilin/warranty.htm
For products shipped before 1 October 2013, the standard 24-month warranty applies.
0.1REVISION HISTORY
MANUAL P/N RELEASE DATE
GEK-106310-AF June 2017
GEK-106310-AG November 2017
GEK-106310-AH April 2018
1601-0800-A1 November 2020
1601-0800-A2 March 2021
1601-0800-A3 October 2022
1601-0800-A4 April 2024
1601-0800-A5 February 2025