GE Multilin G650 Manual page 82

Generator protection & control system
Hide thumbs Also See for Multilin G650:
Table of Contents

Advertisement

4 HUMAN INTERFACES. SETTINGS & ACTUAL VALUES 4.1 ENERVISTA 650 SETUP SOFTWARE INTERFACE
Table 4–1: TYPES OF FILES GENERATED BY ENERVISTA 650 SETUP SOFTWARE OPERATION MODE OFF-LINE:
SETTINGS & CONFIGURATION FILE *.650
Description
Protection Settings and Configuration Section
Created by
EnerVista 650 Setup
Relay configuration file containing all protection
elements Settings, input/output and LEDs configuration,
Contents
graphic display configuration, etc.
Equations corresponding to the logic created and
compiled in the PLC Editor
EnerVista 650 Setup:
How to save
"File>Save *"
EnerVista 650 Setup:
How to open
"File>Open *"
Connect with the relay
("Communications>Computer")
How to
Open the created file ("File>Open *")
transfer to
Send to relay from the menu: "File>Send info to relay"
relay
Note that texts used in the configuration of inputs,
outputs, etc. are not sent to the relay. The only texts
sent to relay are operations, events, and LEDs.
In case of using element libraries (either existing ("File Library>Open Library") or created by the user ("File Library>New
Library"), the program will create and manage the corresponding files (*.lib) in a folder named FDB (Functional Block
Diagram). These files are used for the PLC project compilation. It is necessary to store them with the other logic
configuration files that built the PLC project (*.pep, *.aut, *.lib).
Besides sending basic information to the relay (Settings + configuration) in *.650 format, it is recommended to store *.650,
*.pep, *.aut and *.lib files inside the relay ("Communication>Upload info files to relay"), to ensure that logic configuration
files will be available in the future for further logic modifications; either if these files are not used by the relay, they are
required for connecting to a relay and analyzing its configuration. The program manages the logic configuration files
globally, so that when the user selects to save file *.pep in the relay, the associated *.aut and *.lib files are also stored.
File storage inside the relay
(RECOMMENDED)
Retrieval of files stored in the relay
(RECOMMENDED)
GEK-113285A
"Communication > Upload info files to relay" through Ethernet
"Communication > Download info files from relay" through Ethernet
G650 Generator Protection & Control System
LOGIC CONFIGURATION FILES (*.PEP, *AUT, *.LIB)
*.PEP
*.AUT
Graphical edition
container. Logic
Header for Logic
equations (Virtual
project
Outputs) in FDB
format.
Logic configuration
Logic configuration
graphic editor (PLC
graphic editor (PLC
Editor)
Editor)
PLC project file
PLC Project file
containing the
containing all the
necessary
drawings used by
information relative
the logic, required by
to the relay model,
650 relay based on
logic libraries
IEC 61131-3
included in the
standard. Functional
project (*.lib),
block diagram
graphic file name
(FDB).
(*.aut), etc.
PLC Editor:
PLC Editor:
"File>Save
"File>Save
Project"
Project"
PLC Editor:
PLC Editor:
"File>Open
"File>Open
Project"
Project"
Connect with the relay ("Communications>Computer")
Launch 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.
*.LIB
User programmable
logic objects
Logic configuration
graphic editor (PLC
Editor)
Library file to be
included as an
object in a PLC
project. Logic
packages that can
4
be stored into
libraries and be
distributed in
different PLC
projects.
PLC Editor:
"File>Save
Library"
PLC Editor:
"File>Library>New
Library"
4-7

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents