- Introduction
- 1. What Is GOOSE Communication?
- 2. How GOOSE Communication Works in MiCOM Relays
- 3. GOOSE Communication Architecture
- 4. GOOSE Message Structure
- 5. GOOSE Dataset Configuration in MiCOM Relays
- 6. GOOSE Control Block Configuration
- 7. GOOSE Communication Between Two MiCOM Relays
- 8. GOOSE Applications in MiCOM Protection Systems
- 9. GOOSE Communication and Programmable Scheme Logic (PSL)
- 10. GOOSE Communication Performance
- 11. GOOSE Communication Supervision
- 12. Testing GOOSE Communication Using Wireshark
- 13. GOOSE Testing and Commissioning Procedure
- 14. Common GOOSE Communication Problems in MiCOM Relays
- 15. GOOSE vs Conventional Hardwired Signals
- 16. Cybersecurity Considerations for GOOSE Networks
- 17. Conclusion
- IEC 61850 and MiCOM Relay Training by Elec-Engg
Introduction
GOOSE (Generic Object Oriented Substation Event) is one of the most important communication services defined by IEC 61850. It enables fast, reliable and event-driven communication between Intelligent Electronic Devices (IEDs) in electrical substations.
In conventional protection and control systems, signals such as breaker status, protection trips, blocking signals and interlocking commands are exchanged through copper wiring between protection relays and control devices.
IEC 61850 GOOSE provides an alternative by allowing these signals to be exchanged through Ethernet communication.
MiCOM protection relays equipped with IEC 61850 GOOSE functionality can publish and subscribe to information exchanged with other compatible IEDs.
This technology is particularly useful in applications involving feeder protection, transformer protection, busbar protection, circuit breaker interlocking, breaker failure protection and substation automation.
This article explains GOOSE communication principles, publisher and subscriber architecture, configuration concepts, datasets, engineering parameters, practical applications and commissioning procedures for MiCOM protection relays.
1. What Is GOOSE Communication?
GOOSE is an event-based communication mechanism defined in IEC 61850-8-1.
It provides fast peer-to-peer communication between IEDs over Ethernet networks.
Unlike conventional MMS client-server communication, GOOSE does not require a client to continuously request information from a server.
Instead, a publishing IED transmits a predefined dataset to the network. Other IEDs configured as subscribers receive and process the information.
For example:
- MiCOM Relay 1 detects a feeder protection operation.
- Relay 1 publishes a GOOSE message.
- The Ethernet network distributes the message.
- MiCOM Relay 2 receives the message.
- Relay 2 uses the received signal in its programmable logic.
This mechanism can replace selected hardwired connections between protection and control devices.
2. How GOOSE Communication Works in MiCOM Relays
GOOSE communication is based on a publisher-subscriber architecture.
There are two principal roles.
2.1 GOOSE Publisher
The publisher is the IED responsible for transmitting information to the Ethernet network.
A MiCOM protection relay can publish signals such as:
- Protection trip.
- Overcurrent start.
- Earth fault operation.
- Circuit breaker status.
- Breaker failure initiation.
- Interlocking status.
- Programmable logic outputs.
The published information is organized into a dataset.
2.2 GOOSE Subscriber
The subscriber is the IED configured to receive and process GOOSE messages.
A MiCOM relay can subscribe to information published by another IED.
Examples include:
- Receiving a breaker position signal.
- Receiving a busbar protection trip.
- Receiving an interlocking signal.
- Receiving a blocking signal.
- Receiving a transfer trip command.
The received information can be assigned to available internal signals or virtual inputs and used in the relay’s programmable logic, subject to the product implementation.
3. GOOSE Communication Architecture
A typical MiCOM GOOSE network includes several protection relays connected to industrial Ethernet switches.
For example, consider a substation containing:
- MiCOM P143 feeder protection relay.
- MiCOM P643 transformer protection relay.
- MiCOM P546 line differential protection relay.
- Ethernet communication switches.
The relays can exchange information through GOOSE messages.
A transformer protection relay can publish a trip signal, which can be received by other IEDs for coordinated protection and control actions.
The actual protection scheme must be engineered with suitable redundancy, supervision and failure handling.
4. GOOSE Message Structure
A GOOSE message contains several important parameters that identify the publisher, dataset and communication state.
The main parameters include:
| Parameter | Description |
|---|---|
| gocbRef | GOOSE Control Block reference |
| datSet | Dataset reference |
| goID | GOOSE identifier |
| t | Message timestamp |
| stNum | State number |
| sqNum | Sequence number |
| timeAllowedToLive | Maximum expected interval before timeout |
| confRev | Dataset configuration revision |
| ndsCom | Needs commissioning indication |
| numDatSetEntries | Number of dataset entries |
| allData | Published dataset values |
These parameters help subscriber IEDs identify the message, evaluate its state and supervise communication.
4.1 State Number – stNum
The state number changes when the published dataset undergoes a state change.
For example, when a breaker position changes from open to closed, the publisher transmits a new state with an updated state number.
4.2 Sequence Number – sqNum
The sequence number identifies successive transmissions associated with the same state.
When a GOOSE event occurs, the publisher typically retransmits the message several times at decreasing intervals before returning to its normal heartbeat transmission interval.
4.3 Time Allowed to Live
This parameter defines the maximum time a subscriber should wait before considering the received GOOSE information stale.
If no valid message is received within the configured supervision interval, the subscriber can declare a communication timeout.
The resulting application behavior depends on the subscriber implementation and engineering configuration.
5. GOOSE Dataset Configuration in MiCOM Relays
A dataset is a collection of data attributes that the publisher transmits through GOOSE.
For example, a feeder relay may publish the following information:
| Dataset member | Description |
|---|---|
| Overcurrent Start | Overcurrent protection pickup |
| Overcurrent Trip | Overcurrent protection operation |
| Earth Fault Trip | Earth fault protection operation |
| Breaker Open | Circuit breaker open status |
| Breaker Closed | Circuit breaker closed status |
| Relay Healthy | Device health indication |
The dataset must be compatible with the GOOSE publisher configuration and the receiving subscriber.
Engineers should verify:
- Data object references.
- Data attribute types.
- Dataset membership.
- Number of dataset entries.
- Configuration revision.
- Publisher and subscriber compatibility.
Not every signal available internally in a MiCOM relay is necessarily available for GOOSE publication.
6. GOOSE Control Block Configuration
The GOOSE Control Block (GoCB) defines the communication parameters used by the publisher.
Important configuration parameters include:
- GoCB reference.
- GOOSE identifier.
- Dataset reference.
- Configuration revision.
- Destination multicast MAC address.
- VLAN identifier.
- VLAN priority.
- Minimum transmission interval.
- Maximum transmission interval.
- Time allowed to live.
The configuration must be consistent with the communication requirements of the project.
For example, VLAN configuration should be coordinated with the Ethernet switch configuration.
Incorrect VLAN assignment or multicast filtering can prevent a subscriber from receiving the intended GOOSE messages.
7. GOOSE Communication Between Two MiCOM Relays
Consider a practical application involving two MiCOM P143 feeder protection relays.
The objective is to transmit an overcurrent protection trip signal from Relay 1 to Relay 2.
Publisher Configuration
Relay 1 acts as the GOOSE publisher.
The engineer selects the required protection signal and includes it in the appropriate dataset.
For example:
- Overcurrent protection trip.
- Earth fault trip.
- Breaker status.
The GOOSE Control Block is configured to publish the dataset.
Subscriber Configuration
Relay 2 acts as the GOOSE subscriber.
The engineer configures Relay 2 to receive the required GOOSE message from Relay 1.
The received signal is mapped to an available internal input or virtual input.
Programmable Scheme Logic
The received GOOSE signal can then be connected to the required Programmable Scheme Logic (PSL).
For example:
GOOSE Received Signal
|
v
Virtual Input
|
v
PSL Logic
|
v
Control / Protection
Function
The exact signal mapping and logic implementation depend on the MiCOM model and firmware.
8. GOOSE Applications in MiCOM Protection Systems
GOOSE communication supports many protection and automation applications.
8.1 Circuit Breaker Interlocking
GOOSE can exchange breaker position and interlocking information between IEDs.
For example, a bus coupler closing command may be permitted only when the required feeder and busbar conditions are satisfied.
The MiCOM relay receives the required status information and processes the interlocking logic.
8.2 Busbar Protection Signaling
In a substation with multiple feeder bays, GOOSE can exchange protection-related signals between feeder relays and busbar protection equipment.
Applications include:
- Feeder status exchange.
- Blocking signals.
- Trip signals.
- Breaker failure information.
The actual busbar protection algorithm and trip logic must be designed according to the dedicated protection system requirements.
8.3 Breaker Failure Protection
GOOSE can transmit breaker failure initiation or associated protection signals between IEDs.
For example, when a feeder protection relay issues a trip command but the breaker fails to interrupt the fault, the required breaker failure information can be exchanged with other protection devices.
8.4 Transformer Protection Intertripping
A MiCOM P643 transformer protection relay can participate in a GOOSE-based intertripping scheme where supported.
A transformer differential protection operation can initiate the appropriate trip actions through configured communication signals.
The scheme must include independent consideration of communication failure and the required backup protection.
8.5 Automatic Changeover Schemes
GOOSE can also be used to exchange breaker and supply status information in automatic bus transfer applications.
The automation logic can use the received signals to determine whether a transfer operation is permitted.
9. GOOSE Communication and Programmable Scheme Logic (PSL)
Programmable Scheme Logic is particularly important in MiCOM relays.
PSL allows engineers to create application-specific logic by combining internal protection signals, binary inputs, virtual inputs, timers and logic gates.
GOOSE communication can extend this capability by allowing information from external IEDs to participate in the logic.
For example:
External GOOSE Signal
|
v
Virtual Input
|
v
AND Gate <----- Local Breaker Status
|
v
Timer Logic
|
v
Programmable Output
This allows engineers to design advanced protection and control schemes without requiring a separate hardwired signal for every function.
However, the PSL execution time, signal processing behavior and communication latency must be considered when designing protection-critical applications.
10. GOOSE Communication Performance
GOOSE is designed for fast communication in substation automation systems.
Its performance depends on:
- Ethernet network architecture.
- Switch processing time.
- Network loading.
- Number of network hops.
- IED processing time.
- GOOSE retransmission settings.
- Network configuration.
- Traffic prioritization.
GOOSE messages use Ethernet multicast and can be assigned VLAN priority to support traffic handling.
For time-critical applications, engineers should assess the complete end-to-end communication performance rather than relying only on the protocol’s theoretical capabilities.
IEC 61850 performance requirements are application-dependent and should be evaluated against the applicable IEC 61850-5 performance classes.
11. GOOSE Communication Supervision
GOOSE subscribers monitor incoming messages to determine whether communication is operating correctly.
Important supervision parameters include:
- Source identification.
- Dataset consistency.
- Configuration revision.
- State number.
- Sequence number.
- Time allowed to live.
- Message reception status.
If a valid GOOSE message is not received within the expected supervision period, the subscriber may indicate a communication failure.
Engineers must carefully define what happens when the communication fails.
For example:
- Should the virtual input return to a predefined state?
- Should an alarm be generated?
- Should the protection function be blocked?
- Should the system transfer to a hardwired backup?
- Should the associated protection function remain enabled?
These decisions must be made according to the protection philosophy and safety requirements of the application.
12. Testing GOOSE Communication Using Wireshark
Wireshark is a useful tool for analyzing GOOSE communication during commissioning.
GOOSE uses Ethernet EtherType:
0x88B8
A useful Wireshark display filter is:
goose
Engineers can inspect:
- Source MAC address.
- Destination multicast MAC address.
- VLAN information.
- GOOSE identifier.
- Dataset reference.
- State number.
- Sequence number.
- Time allowed to live.
- Published data values.
This is particularly useful when diagnosing incorrect publisher configuration, missing subscriber messages and network filtering problems.
13. GOOSE Testing and Commissioning Procedure
A practical GOOSE commissioning procedure should include the following stages.
Stage 1 – Configuration verification
- Verify publisher configuration.
- Verify subscriber configuration.
- Check dataset membership.
- Confirm the GOOSE Control Block.
- Verify multicast MAC addresses.
- Check VLAN and priority settings.
Stage 2 – Network verification
- Check Ethernet connectivity.
- Verify switch configuration.
- Check multicast forwarding.
- Inspect VLAN configuration.
- Confirm communication between IEDs.
Stage 3 – Publisher testing
- Activate the selected source signal.
- Observe GOOSE transmission.
- Verify the published data values.
- Check state and sequence numbers.
Stage 4 – Subscriber testing
- Verify reception of the GOOSE message.
- Confirm the received signal mapping.
- Check the virtual input status.
- Verify signal processing in PSL.
Stage 5 – Functional testing
- Test the complete application logic.
- Verify output behavior.
- Check interlocking conditions.
- Test communication failure behavior.
- Restore the system to its normal operating condition.
All tests involving trip and control signals should be performed under an approved commissioning procedure with suitable isolation and safety precautions.
14. Common GOOSE Communication Problems in MiCOM Relays
| Problem | Possible reason |
|---|---|
| No GOOSE messages transmitted | Publisher not enabled or incorrect configuration |
| Subscriber does not receive messages | Incorrect multicast address or VLAN |
| GOOSE signal remains inactive | Incorrect dataset member or signal mapping |
| Configuration mismatch | Incorrect ConfRev |
| Communication timeout | Network interruption or incorrect supervision |
| Incorrect signal behavior | Wrong data type or polarity |
| Intermittent GOOSE communication | Network congestion or switch configuration |
| GOOSE works in one direction only | Missing reverse-direction configuration |
An important point is that GOOSE communication is directional at the application level.
If two MiCOM relays need to exchange signals in both directions, each direction must be configured appropriately.
15. GOOSE vs Conventional Hardwired Signals
| Feature | Conventional wiring | IEC 61850 GOOSE |
|---|---|---|
| Signal transmission | Copper wiring | Ethernet |
| Physical connections | Dedicated signal wiring | Shared communication network |
| Signal flexibility | Requires wiring changes | Configuration-based |
| Diagnostics | Circuit-level checks | Network and IED diagnostics |
| Multi-IED communication | Requires additional wiring | Supports multiple subscribers |
| Engineering | Wiring diagrams and terminal connections | Datasets and communication configuration |
| Failure considerations | Open circuit and wiring faults | Network and communication failures |
GOOSE does not eliminate the need for conventional wiring in every application. Critical trip circuits, backup arrangements and other functions may still require dedicated hardwired connections according to the project design and applicable standards.
16. Cybersecurity Considerations for GOOSE Networks
GOOSE communication must be protected against unauthorized access and unintended network traffic.
Important engineering measures include:
- Network segmentation.
- VLAN configuration.
- Managed switch security.
- Restricting physical network access.
- Port security where appropriate.
- Controlled engineering access.
- Network traffic monitoring.
- Configuration backup and change management.
- Appropriate IEC 62351 security measures where supported.
Since GOOSE operates directly over Ethernet, network design and access control are important parts of the overall protection system security architecture.
17. Conclusion
IEC 61850 GOOSE communication provides MiCOM protection relays with powerful peer-to-peer communication capabilities.
It enables protection and control information to be exchanged between IEDs without requiring a dedicated hardwired connection for every signal.
Through GOOSE publisher and subscriber configuration, engineers can implement advanced applications such as breaker interlocking, protection signaling, intertripping, breaker failure signaling and automatic changeover schemes.
A successful implementation requires more than enabling GOOSE communication. Engineers must understand datasets, GOOSE Control Blocks, multicast addressing, VLAN configuration, signal mapping, PSL logic, communication supervision and functional testing.
Practical knowledge of these concepts is essential for commissioning and maintaining IEC 61850-based MiCOM protection systems.
IEC 61850 and MiCOM Relay Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM protection relays and substation automation.
Our training programs cover:
- MiCOM protection relay configuration.
- IEC 61850 MMS and GOOSE communication.
- GOOSE publisher and subscriber engineering.
- Dataset and Control Block configuration.
- SCL file engineering.
- GOOSE-based interlocking and protection schemes.
- MiCOM PSL programming.
- IEC 61850 testing using Wireshark.
- Integration with SICAM PAS and SCADA systems.
Training is available through online courses, structured self-paced programs, face-to-face sessions and customized in-house training.
Website: https://elec-engg.com/
