4.9
Date Code 20020501 SEL-2701 Ethernet Processor Instruction Manual
SEL-2030 Host
Data Access
to force RB1 to a controlled state if the SEL-2701 no longer considers
the GOOSE monitor active.
The first 32 incoming GOOSE bits form the DNA portion of the GOOSE
message. Bit 33 is the first User ST bit in the incoming GOOSE
message. Incoming GOOSE messages contain bit pairs that indicate
status changes. If the bit pair is 10, it indicates a state change to on
and 17:CCIN2 will be set. If the bit pair is 01, it indicates a state change
to off and 17:CCIN2 will be cleared.
CTRLB1 and CTRLB2 appear inside the SEL-2030 as 17:CCIN1 and
17:CCIN2, respectively. The SRB1 and CRB1 settings for Port 3 set or
clear RB1 based on the incoming message data.
When 17:CCIN1 is on, the SEL-2701 considers data from GOOSE
Monitor 1 invalid. The !17:CCIN1 term in the SRB1 and CRB1 settings
prevents setting or clearing RB1 if the incoming data are invalid. In
the SRB1 setting, the 17:CCIN1 term forces RB1 on when incoming data
are invalid.
If the 17:CCIN1 term resides in the CRB1 setting as shown below, RB1 is
automatically cleared any time the incoming GOOSE message data
are invalid.
SRB1 = 17:CCIN2 * !17:CCIN1
CRB1 = !17:CCIN2 * !17:CCIN1 + 17:CCIN1
If there is no 17:CCIN1 term in SRB1 or CRB1, RB1 will not change state
when the incoming data are invalid.
The SEL-2701 polls the SEL-2030 control bits (CCOUT1–CCOUT32) every
100 ms. You must design your logic so that control bits remain in any new
state for at least 100 ms or the SEL-2701 may not recognize the new state. For
example, if CCOUT1 changes from a logical 0 to a logical 1 and back to
logical 0 in less than 100 ms, the SEL-2701 may not recognize the changes
and not send outgoing GOOSE messages. If CCOUT1 remains in the new
state for more than 100 ms, the SEL-2701 will recognize the change and send
corresponding GOOSE messages. This behavior only affects control bits that
you configure with control equations that include remote bits, breaker bits,
other control bits, and intermediate logic bits. Data in the User and Data
regions are updated at 500 ms or slower and are not affected.
GOMSFE
GOMSFE is a system that contains both standard ways (bricks) to organize
and represent data as well as rules for vendor-specific extensions. On a UCA2
network, the SEL-2701 appears as a single Logical Device. The SEL-2030
Logical Device contains one Virtual Device for each connected IED. Each
Virtual Device contains standard and extended GOMSFE model bricks to
convey available data. The available data and bricks vary based on the
connected IEDs. You can observe available data by browsing the UCA2
interface with an MMS browser.
The model description in Appendix B: UCA2 GOMSFE Models provides rules
for the population of GOMSFE models. SEL-2701 data are based on labels in
the SEL-2030. This process is automatic for SEL relays.
For SEL relays, the SEL-2701 populates models based on data collected by
the SEL-2030. To populate models with SEL relay data, use the following
steps:
Step 1. Configure the SEL-2030 port connected to the relay for SEL
protocol and perform an autoconfiguration.
Step 2. Use the GOMSFE tables to determine what SEL-2030 data
collection (e.g., 20HISTORY) is necessary for the GOMSFE
bricks you want to use.