GE Multilin
M60 Motor Protection System
5-257
5 SETTINGS
5.8 INPUTS AND OUTPUTS
5
VIRTUAL OUTPUT 1 ID:
"Trip"
VIRTUAL OUTPUT 1 EVENTS:
"Disabled"
5.8.5 REMOTE DEVICES
a) REMOTE INPUTS/OUTPUTS OVERVIEW
Remote inputs and outputs provide a means of exchanging digital state information between Ethernet-networked devices.
The IEC 61850 GSSE (Generic Substation State Event) and GOOSE (Generic Object Oriented Substation Event) stan-
dards are used.
The sharing of digital point state information between GSSE/GOOSE equipped relays is essentially an extension to Flex-
Logic, allowing distributed FlexLogic by making operands available to/from devices on a common communications net-
work. In addition to digital point states, GSSE/GOOSE messages identify the originator of the message and provide other
information required by the communication specification. All devices listen to network messages and capture data only from
messages that have originated in selected devices.
IEC 61850 GSSE messages are compatible with UCA GOOSE messages and contain a fixed set of digital points. IEC
61850 GOOSE messages can, in general, contain any configurable data items. When used by the remote input/output fea-
ture, IEC 61850 GOOSE messages contain the same data as GSSE messages.
Both GSSE and GOOSE messages are designed to be short, reliable, and high priority. GOOSE messages have additional
advantages over GSSE messages due to their support of VLAN (virtual LAN) and Ethernet priority tagging functionality.
The GSSE message structure contains space for 128 bit pairs representing digital point state information. The IEC 61850
specification provides 32 “DNA” bit pairs that represent the state of two pre-defined events and 30 user-defined events. All
remaining bit pairs are “UserSt” bit pairs, which are status bits representing user-definable events. The M60 implementation
provides 32 of the 96 available UserSt bit pairs.
The IEC 61850 specification includes features that are used to cope with the loss of communication between transmitting
and receiving devices. Each transmitting device will send a GSSE/GOOSE message upon a successful power-up, when
the state of any included point changes, or after a specified interval (the
default update
time) if a change-of-state has not
occurred. The transmitting device also sends a ‘hold time’ which is set greater than four times the programmed default time
required by the receiving device.
Receiving devices are constantly monitoring the communications network for messages they require, as recognized by the
identification of the originating device carried in the message. Messages received from remote devices include the mes-
sage
time allowed to live
. The receiving relay sets a timer assigned to the originating device to this time interval, and if it
has not received another message from this device at time-out, the remote device is declared to be non-communicating, so
it will use the programmed default state for all points from that specific remote device. If a message is received from a
remote device before the
time allowed to live
expires, all points for that device are updated to the states contained in the
message and the hold timer is restarted. The status of a remote device, where “Offline” indicates non-communicating, can
be displayed.
The remote input/output facility provides for 32 remote inputs and 64 remote outputs.
b) LOCAL DEVICES: ID OF DEVICE FOR TRANSMITTING GSSE MESSAGES
In a M60 relay, the device ID that represents the IEC 61850 GOOSE application ID (GoID) name string sent as part of each
GOOSE message is programmed in the
SETTINGS
PRODUCT SETUP
COMMUNICATIONS
IEC 61850 PROTOCOL
GSSE/GOOSE CONFIGURATION
TRANSMISSION
FIXED GOOSE
GOOSE ID
setting.
Likewise, the device ID that represents the IEC 61850 GSSE application ID name string sent as part of each GSSE mes-
sage is programmed in the
SETTINGS
PRODUCT SETUP
COMMUNICATIONS
IEC 61850 PROTOCOL
GSSE/GOOSE
CONFIGURATION
TRANSMISSION
GSSE
GSSE ID
setting.
In M60 releases previous to 5.0x, these name strings were represented by the
RELAY NAME
setting.
Summary of Contents for M60 UR Series
Page 10: ...x M60 Motor Protection System GE Multilin TABLE OF CONTENTS ...
Page 128: ...4 30 M60 Motor Protection System GE Multilin 4 3 FACEPLATE INTERFACE 4 HUMAN INTERFACES 4 ...
Page 410: ...5 282 M60 Motor Protection System GE Multilin 5 10 TESTING 5 SETTINGS 5 ...
Page 440: ...6 30 M60 Motor Protection System GE Multilin 6 5 PRODUCT INFORMATION 6 ACTUAL VALUES 6 ...
Page 452: ...7 12 M60 Motor Protection System GE Multilin 7 2 TARGETS 7 COMMANDS AND TARGETS 7 ...
Page 462: ...9 8 M60 Motor Protection System GE Multilin 9 2 BATTERIES 9 MAINTENANCE 9 ...
Page 474: ...A 12 M60 Motor Protection System GE Multilin A 1 PARAMETER LISTS APPENDIX A A ...
Page 584: ...B 110 M60 Motor Protection System GE Multilin B 4 MEMORY MAPPING APPENDIX B B ...
Page 614: ...C 30 M60 Motor Protection System GE Multilin C 7 LOGICAL NODES APPENDIX C C ...
Page 630: ...E 10 M60 Motor Protection System GE Multilin E 1 IEC 60870 5 104 PROTOCOL APPENDIX E E ...
Page 642: ...F 12 M60 Motor Protection System GE Multilin F 2 DNP POINT LISTS APPENDIX F F ...
Page 644: ...G 2 M60 Motor Protection System GE Multilin G 1 RADIUS SERVER CONFIGURATION APPENDIX G G ...
Page 652: ...H 8 M60 Motor Protection System GE Multilin H 3 WARRANTY APPENDIX H H ...
Page 662: ...x M60 Motor Protection System GE Multilin INDEX ...