1.16
SEL-2701 Ethernet Processor Instruction Manual Date Code 20020501
Introduction
UCA2
slave device then reports a description containing the details of each available
standard, extended, or custom brick.
Self-description operates similarly to autoconfiguration of an SEL-2030 port
communicating with an SEL IED. The master automatically collects
information from the IED on what data are available and how to collect that
data. Only a very small amount of user configuration is necessary for the
master to begin collecting data.
GOMSFE also utilizes a high-level organizational structure with logical
devices and domains. Both logical devices and domains contain GOMSFE
bricks. All UCA2 devices have at least one logical device and can include
either more logical devices or domains. For a detailed example of GOMSFE
models for a relay connected to an SEL-2030, see Appendix C: GOMSFE
Model Example.
The SEL-2701 contains all of the information necessary to collect data from
the host and populate GOMSFE models. All SEL hosts with an SEL-2701 will
have a Logical Device 0 (labeled LN0) that contains at least the DI and
GLOBE bricks. There will also be at least 1 domain and as many as 18
domains for the host and any devices connected to the host. Devices connected
to the host are called virtual devices. For SEL hosts and SEL relays connected
to SEL hosts, the SEL-2701 automatically finds data in the host and populates
the GOMSFE models.
In devices that are the primary source of information available for GOMSFE
models like the SEL-400 series relays, there is a single domain that contains
the DID and GLOBE bricks as well as several other bricks with measurement,
status, and control for the host. In devices that collect data from other IEDs
such as the SEL-2030, there are virtual domains for the connected devices.
The SEL-2030 can collect data from SEL IEDs and from non-SEL IEDs
including protective relays, meters, PLCs (programmable logic controllers),
and transformer monitors. The SEL-2701 populates models using data
collected from the attached IEDs using the rules shown in Appendix B: UCA2
GOMSFE Models.
GOOSE
GOOSE is part of the GOMSFE brick GLOBE. UCA2 IEDs use GOOSE
messages for event-driven peer-to-peer communication and control. Each
UCA2 device sends a GOOSE message when an internal data-change event
occurs. A data-change event occurs when a monitored point changes state, for
example, from one to zero or from zero to one. Event-driven messages limit
network traffic and improve response speed by sending messages only when
data-change events occur. This is a significant improvement over polling
mechanisms that burden the network when no new data values are available.
In addition to the event-driven messages, UCA2 devices send GOOSE
messages at a default rate of once every minute. Devices that receive GOOSE
messages use the default rate messages to track the status of GOOSE senders
and collect initial values when joining the network.
Each GOOSE message contains a text ID name of the GOOSE sender and a
special Ethernet multicast destination address. UCA2 devices use the Ethernet
multicast destination addresses to filter incoming GOOSE messages. Each
device accepts and processes only messages containing information it is
configured to use.
To Next Page
Loading...
