Iec 61850 Protocol; Uplc-Ii™ With Iec 61850 - Ametek UPLC-II System Manual

UPlC-ii™ System manual

7.5 IEC 61850 Protocol

7.5.1 UPLC-II™ with IEC 61850
IEC 61850 is the industry's standard for peer to peer
communications within a substation. Data is trans-
mitted over an Ethernet network in the substation,
eliminating much of the wiring between devices
that has historically been used to interconnect them.
The UPLC-II™ is used as a pilot channel with
transmission line relaying and major equipment
breaker protection. Since IEC 61850 protocol
allows for interconnecting the devices within the
substation without the usual wiring, this eliminates
the labor and cost associated with physical wiring.
Since a template may be created for all the different
devices, and copied for each project, this also elim-
inates the human factor in wiring errors from panel
to panel.
It is not a point-to-point system but a multicast sys-
tem whereby a message is generated by the UPLC-
II™ to which the other devices in the substation
subscribe. A new message is sent when there is a
change to one of the data items and is repetitiously
sent at increasing intervals until another data
change occurs. Likewise, the devices and elements
the UPLC-II™ has been programmed to subscribe
to will produce these messages and the UPLC-II™
will respond accordingly. These messages can be a
variety of functions, such as:
Permission to trip or a block input for pilot
relaying
Request to initiate a checkback test function
Alarm output
Measured value such as transmitted power out
or received level.
Some specifics to be aware of:
1. The LNodeType id is "ZPLC" and the
InClass is "ZPLC".
2. The user will need to assign:
• UPLC-II™ IEC name (the generic
name the subscribing unit may use to
identify the subscribed device)
• Choose to enable the digital and/or ana-
log GOOSE:
Page 7–8
• MAC address (the destination address
for the UPLC™ GOOSE message)
• APPID
• VLAN Priority
• GSE Control appID
These will need to be correct for the UPLC-II™ to
subscribe to other devices to properly detect and
process the information.
Figure 7–6 shows the GOOSE definitions page.
The .cid file will need to be uploaded to the UPLC-
II™. This is temporarily created manually. It must
be named "api_uplc.cid". AMETEK will assist any
customer with their configuration.
The UPLC-II™ uses the "private subscription" sec-
tion of the standard, since there are not standard
object definitions at this time. A sample file is avail-
able from your local AMETEK sales representative.
What's available?
Settings:
ChannelType
RelayingFunction
TransmitterFrequency
ReceiverFrequency
ONOFFBandwidth
FSKTransmitterBandwidth
FSKReceiverBandwidth
FSKTransmitterShift
FSKReceiverShift
TransmitterHighPower
TransmitterLowPower
GOOSE Outputs and Alarms:
The outputs are divided into "high speed" and
"slow speed" GOOSE messaging. The outputs that
are direct protective functions are interpreted and
transmitted immediately (less than 1 ms) while
those that are not direct protective functions are
transmitted after a time period of approximately 5