IEC 61850 GOOSE Testing in MiCOM Relays: Practical Testing, Troubleshooting, Wireshark Analysis and Commissioning Procedures

1. Introduction

GOOSE (Generic Object Oriented Substation Event) is one of the most important communication services in IEC 61850-based substation automation systems. It enables fast exchange of status information, protection signals, interlocking commands and other event-based information between intelligent electronic devices (IEDs).

In substations using MiCOM protection relays, GOOSE communication can reduce the need for conventional hardwired connections between devices. It can be used for applications such as:

  • Circuit breaker interlocking
  • Protection trip signaling
  • Breaker failure initiation and transfer
  • Busbar protection signaling
  • Transformer protection intertripping
  • Feeder protection blocking
  • Auto-reclosing coordination
  • Breaker status exchange
  • Load shedding and automation

However, configuring a GOOSE message does not automatically guarantee that the complete application will operate correctly.

Engineers must test the publisher, Ethernet network, subscriber, signal mapping, relay logic and final application response.

This article explains how to test IEC 61850 GOOSE communication in supported MiCOM relays, including practical commissioning procedures, Wireshark analysis, troubleshooting and functional verification.

Important: GOOSE capabilities and engineering procedures vary between MiCOM models, hardware versions and firmware. Always confirm the applicable services, data model and testing procedures in the relay’s technical documentation.

2. Understanding GOOSE Communication

GOOSE is an IEC 61850 communication service designed for fast event-based information exchange between IEDs.

Unlike MMS, which uses a client-server communication model over TCP/IP, GOOSE uses Ethernet multicast messages.

A GOOSE publisher transmits information to the network, and one or more subscribers receive and process the published information.

GOOSE publisher and subscriber architecture

MiCOM Relay 1

Publisher

Protection trip / breaker status

Ethernet multicast GOOSE

Substation Ethernet Network

Switches · VLAN · Multicast forwarding

MiCOM Relay 2

Subscriber

Interlocking logic

Bay Controller

Subscriber

Status monitoring

Conceptual example. Actual publisher and subscriber roles depend on device capabilities and project design.

One GOOSE publisher can communicate with multiple subscribers, provided that the network and receiving devices are configured accordingly.

3. GOOSE Message Structure and Important Parameters

To test GOOSE communication effectively, engineers should understand the main fields and parameters included in a GOOSE message.

Important fields include:

ParameterDescription
GoCB referenceIdentifies the GOOSE control block
Dataset referenceIdentifies the published dataset
GoIDGOOSE identifier
AppIDApplication identifier
MAC addressEthernet destination multicast address
VLAN IDVLAN identifier, if configured
VLAN priorityEthernet priority, if configured
ConfRevGOOSE configuration revision
stNumState number
sqNumSequence number
timeAllowedToLiveExpected maximum time before the next message
datSetDataset reference
goIDGOOSE identifier
allDataPublished data values

Some field names are case-sensitive in the protocol representation. The table includes both commonly discussed fields and their protocol-style names.

3.1 State number (stNum)

The state number changes when the published dataset state changes.

For example, if a feeder protection relay publishes a breaker position and the breaker changes from closed to open, the publisher’s GOOSE state information is updated.

The state number helps the subscriber recognize a new state.

3.2 Sequence number (sqNum)

The sequence number changes as GOOSE messages are retransmitted within a particular state.

It helps distinguish successive transmissions of the same state.

3.3 Time allowed to live

The timeAllowedToLive field indicates the maximum expected time before the next message is due.

The subscriber can use this information for communication supervision.

If messages stop arriving within the expected time, the subscriber can detect a communication interruption and apply its configured failure behavior.

3.4 Configuration revision (ConfRev)

ConfRev identifies the configuration revision associated with the GOOSE control block and its dataset.

When relevant configuration changes are made, the revision must be handled consistently between publisher and subscriber.

It is not the relay firmware revision.

4. GOOSE Testing: What Must Be Verified?

A complete GOOSE test should cover several layers.

Testing layerWhat to verify
PublisherGOOSE messages are transmitted
NetworkEthernet multicast traffic reaches the required ports
SubscriberMessages are received and recognized
Data mappingCorrect data attributes are assigned
Application logicReceived information operates the intended logic
OutputThe correct physical or logical response occurs
SupervisionCommunication failure is detected and handled correctly

It is important to separate communication testing from application testing.

For example, Wireshark may confirm that a GOOSE message is being transmitted, but it cannot by itself confirm that the receiving MiCOM relay has mapped the signal correctly into its protection or control logic.

5. Practical Example: GOOSE Protection Trip Between Two MiCOM Relays

Consider a substation with two feeder bays.

  • MiCOM Relay 1 provides feeder protection.
  • MiCOM Relay 2 receives a protection trip signal.
  • The trip signal is transmitted through GOOSE.
  • The receiving relay uses the signal in its configured application logic.

The purpose of the test is to verify the complete communication chain.

Example protection trip signal path

MiCOM Relay 1

Protection function operates

Trip signal changes state

GOOSE publisher

Dataset and control block

Ethernet network

Multicast message transmission

MiCOM Relay 2

GOOSE subscriber and input mapping

Configured application response

Interlocking, blocking or trip logic as designed

The test should verify each stage separately before performing an end-to-end functional test.

6. Step 1 – Review the GOOSE Configuration Before Testing

Before starting the commissioning test, review the approved engineering configuration.

Check the following:

Publisher information

  • Publisher IED name
  • Logical device
  • Logical node
  • GOOSE control block
  • Dataset reference
  • Published data attributes
  • AppID
  • Destination multicast MAC address
  • VLAN ID and priority, where used
  • ConfRev

Subscriber information

  • Subscriber IED name
  • Publisher reference
  • Dataset reference
  • External references
  • Signal mapping
  • Application logic
  • Communication supervision settings

Network information

  • Switch port configuration
  • VLAN configuration
  • Multicast forwarding
  • Network redundancy arrangement, where applicable
  • Port mirroring or network tap availability for packet capture

Compare the configuration of the publisher and subscriber against the approved SCD and device-specific configuration files.

Do not assume that the latest SCD file is necessarily the configuration currently loaded into the relay.

7. Step 2 – Check the Publisher Relay

The first practical test is to confirm that the publishing MiCOM relay is transmitting GOOSE messages.

Check:

  1. Relay communication interface is operational.
  2. Correct GOOSE configuration is active.
  3. Required dataset is configured.
  4. GOOSE control block is enabled.
  5. Publisher communication parameters are correct.
  6. No relevant communication or configuration alarm is active.

Where supported, use the relay’s diagnostic or communication monitoring functions to inspect the GOOSE status.

The available diagnostic information depends on the model and firmware.

A relay can have a correctly configured GOOSE dataset but still fail to transmit because of an incorrect control block configuration, disabled service or communication interface problem.

8. Step 3 – Check GOOSE Communication Using Wireshark

Wireshark is one of the most useful tools for IEC 61850 GOOSE troubleshooting.

It allows engineers to inspect the actual Ethernet frames transmitted by the publisher.

8.1 Configure the packet capture

Connect the engineering workstation to a suitable network observation point.

Possible methods include:

  • Managed switch port mirroring
  • Network TAP
  • Approved monitoring port
  • Direct connection in a controlled test arrangement

A normal connection to an arbitrary switch port may not show multicast traffic exchanged between other switch ports.

8.2 Apply the GOOSE display filter

Use the following Wireshark display filter:

goose

GOOSE messages use Ethernet EtherType 0x88B8.

An alternative filter is:

eth.type == 0x88b8

The filter should display the GOOSE packets visible to the capture interface.

8.3 Inspect the packet details

Check the following fields:

FieldWhat to verify
Source MACExpected publisher interface
Destination MACConfigured multicast address
VLAN IDExpected VLAN, if used
AppIDCorrect application identifier
GoCB referenceCorrect control block
Dataset referenceExpected dataset
ConfRevConsistent with approved configuration
stNumChanges when dataset state changes
sqNumAdvances during retransmissions
allDataContains expected published values

The exact packet details depend on the message and the protocol decoder.

9. Step 4 – Test GOOSE State Changes

After confirming that GOOSE messages are being transmitted, test whether the published information changes correctly when the source signal changes.

For example, consider a dataset containing:

  • Circuit breaker position
  • Protection trip indication
  • Protection start indication

The engineer should arrange an approved test condition that causes the relevant signal to change.

A simplified expected sequence is:

Test conditionExpected publisher behavior
Normal stateGOOSE message contains normal values
Protection startRelevant data attribute changes
Protection tripTrip indication changes
Breaker opensBreaker position changes
Return to normalRelevant values return according to the application design

Observe the message in Wireshark.

When the published dataset changes, the state number should reflect the new state according to the GOOSE protocol behavior.

Do not rely on the packet count alone. Verify the actual data values.

10. Step 5 – Check GOOSE Retransmission Behavior

GOOSE uses a retransmission mechanism.

When a state change occurs, the publisher sends the updated message and retransmits it at progressively increasing intervals until the steady-state transmission interval is reached.

This is important because subscribers must be able to detect communication interruptions.

During testing, inspect:

  • Time intervals between successive messages
  • State number changes
  • Sequence number progression
  • timeAllowedToLive
  • Behavior after a new event
  • Steady-state retransmission behavior

Do not assume that every MiCOM relay uses identical retransmission timing. Verify the expected behavior against the applicable configuration and device documentation.

What should the engineer observe?

During a state change, the publisher generally transmits the new state promptly and retransmits it more frequently at first.

As time passes without another state change, the retransmission interval increases toward the configured steady-state interval.

The subscriber uses the incoming message and supervision information to monitor communication.

11. Step 6 – Test the GOOSE Subscriber

After verifying the publisher, test the receiving MiCOM relay.

The subscriber test should confirm:

  • Correct publisher identification
  • Correct dataset reference
  • Correct external reference
  • Correct data type
  • Correct signal polarity or state interpretation
  • Correct application input mapping
  • Correct response of the configured logic

Example: Breaker status subscription

A receiving relay subscribes to the circuit breaker position from another IED.

The engineer should verify:

  1. The publisher sends the breaker position.
  2. The message reaches the subscriber’s network interface.
  3. The subscriber recognizes the message.
  4. The external reference is mapped correctly.
  5. The internal application receives the expected status.
  6. The relevant logic responds correctly.

Where the relay offers diagnostic indications for GOOSE reception, use them as supporting evidence.

The actual application should also be verified through the approved commissioning test procedure.

12. Step 7 – Perform End-to-End GOOSE Functional Testing

End-to-end testing verifies the entire application rather than only the communication packets.

Consider a protection trip transfer application.

The test should cover:

  1. Initiating condition at the publisher.
  2. Protection or logic signal operation.
  3. Publisher dataset update.
  4. GOOSE message transmission.
  5. Network delivery.
  6. Subscriber reception.
  7. External signal mapping.
  8. Subscriber logic response.
  9. Intended final output or application action.

The engineer should record the result of every stage.

For protection-critical applications, use approved test procedures, appropriate test equipment and safe isolation arrangements. Do not initiate actual breaker operations unless specifically authorized by the commissioning plan.

13. Step 8 – Test GOOSE Communication Failure and Recovery

GOOSE communication supervision is essential for applications that depend on receiving timely information from another IED.

A commissioning test should include controlled communication failure and recovery scenarios where permitted by the project test plan.

Possible test conditions include:

  • Disconnecting the publisher’s communication link
  • Blocking the relevant multicast traffic in a controlled test environment
  • Interrupting the network path
  • Restoring the communication connection
  • Restarting an IED under an approved test procedure

Observe the subscriber’s behavior.

Check:

  • Whether a communication failure is detected
  • Whether the expected alarm or diagnostic indication appears
  • Whether the application enters the intended failure state
  • Whether the communication status recovers correctly
  • Whether the application returns to normal as designed

The correct failure response must be defined by the protection and automation design. A communication failure should not be assumed to produce a universal trip or blocking action.

14. Step 9 – Troubleshoot Common GOOSE Problems

The following table summarizes common problems encountered during MiCOM GOOSE commissioning.

ProblemPossible causeRecommended investigation
No GOOSE packet visiblePublisher not transmitting or wrong capture pointCheck publisher and switch mirroring
GOOSE packet visible but subscriber does not respondIncorrect subscriber configurationCheck ExtRef and application mapping
Wrong signal valueIncorrect dataset or data mappingInspect allData and source reference
Subscriber communication alarmMissing or delayed messagesCheck network and publisher supervision
Incorrect VLANSwitch and IED settings inconsistentVerify VLAN configuration
GOOSE messages not forwardedMulticast filtering or switch configurationCheck switch multicast handling
Configuration mismatchPublisher and subscriber project versions differCompare SCD and loaded configurations
Wrong publisher identifiedIncorrect MAC, AppID or referencesCompare message with approved design
Signal remains in an unexpected stateApplication mapping or failure handling issueInspect subscriber logic and quality/status
Intermittent communicationNetwork congestion, link faults or topology problemsCheck switch logs and packet capture

14.1 GOOSE messages are not visible in Wireshark

Possible causes include:

  • Incorrect capture interface
  • Switch port mirroring not configured
  • Incorrect port mirroring source or destination
  • Publisher not transmitting
  • VLAN filtering
  • Network path problem

First verify that the capture point can actually observe the publisher’s traffic.

14.2 GOOSE is visible but the subscriber does not operate

This is a common commissioning problem.

The publisher may be transmitting correctly, but the receiving relay may not recognize or use the message.

Check:

  • Publisher IED reference
  • Dataset reference
  • GOOSE control block
  • AppID
  • Multicast MAC address
  • ConfRev
  • External references
  • Subscriber configuration
  • Application logic mapping

Also check whether the subscriber’s supported implementation accepts the data types and configuration being published.

14.3 ConfRev mismatch

A difference in the expected configuration revision can indicate that publisher and subscriber configurations are not aligned.

Check the approved SCD file and the actual configurations loaded into both devices.

Do not simply change the revision value to clear an alarm without understanding the underlying configuration difference.

14.4 Incorrect GOOSE signal polarity

A signal may be received but interpreted incorrectly by the application.

For example, the engineering design may define a particular Boolean value as breaker closed, while the receiving logic uses the opposite interpretation.

Check the data model, signal definition and application mapping.

15. Practical GOOSE Test Cases for MiCOM Relays

The following examples can be used as a starting point when developing a project-specific commissioning test plan.

Test caseTest objectiveExpected result
GOOSE publisher testVerify message transmissionCorrect GOOSE message visible
Dataset testVerify published valuesExpected data attributes present
State change testVerify event updateNew state reflected in message
Retransmission testVerify message retransmissionExpected sequence and timing behavior
Subscriber testVerify message receptionSubscriber recognizes the message
Signal mapping testVerify external referenceCorrect internal signal changes
Application testVerify protection/control logicIntended logic response
Communication failure testVerify supervisionFailure detected and handled as designed
Recovery testVerify restorationCommunication and application recover as designed
Network testVerify Ethernet forwardingRequired multicast traffic reaches the subscriber

For each test, record:

  • Test identification
  • Date and test engineer
  • Publisher IED
  • Subscriber IED
  • Dataset and GOOSE control block
  • Test condition
  • Expected result
  • Actual result
  • Evidence, such as packet captures
  • Pass/fail status
  • Corrective actions

16. GOOSE Testing Versus Conventional Hardwired Testing

GOOSE communication can replace selected hardwired signal connections, but it does not eliminate the need for engineering and functional verification.

ItemHardwired signalingGOOSE signaling
Signal transmissionCopper wiringEthernet multicast
Signal mappingTerminals and wiring diagramsDatasets and external references
InterconnectionPhysical wiringCommunication network
TroubleshootingWiring and electrical measurementsNetwork capture and IED diagnostics
ExpansionAdditional wiring may be requiredEngineering and network changes
Failure modesCable and contact faultsNetwork and communication faults
TestingElectrical and functional testsCommunication and functional tests

The selection between hardwired and GOOSE signaling should be based on the protection philosophy, availability requirements, network architecture, engineering standards and project specifications.

For critical protection functions, the design must explicitly address communication failure behavior and the required dependability and security.

17. GOOSE Testing and Cybersecurity Considerations

GOOSE communication is an important part of substation operational technology.

It should be included in the substation cybersecurity design.

Recommended considerations include:

  • Restrict physical access to network equipment.
  • Use network segmentation.
  • Configure VLANs according to the approved design.
  • Restrict unauthorized engineering access.
  • Control changes to SCL files and IED configurations.
  • Maintain approved configuration backups.
  • Monitor network switches and communication health.
  • Follow the organization’s IEC 62351 and cybersecurity requirements where applicable.

GOOSE traffic should not be treated as trusted simply because it is exchanged inside a substation network.

Configuration management and controlled engineering access are important for maintaining the integrity of protection and automation communication.

18. Practical GOOSE Commissioning Checklist

Use the following checklist when testing supported MiCOM GOOSE applications.

Before testing

  • Confirm publisher and subscriber models.
  • Check IEC 61850 capabilities.
  • Review the approved SCD.
  • Confirm the correct configuration is loaded.
  • Check dataset and GOOSE control block references.
  • Verify multicast MAC address.
  • Verify AppID.
  • Verify VLAN configuration.
  • Check ConfRev.
  • Confirm the network observation point.

Publisher testing

  • Confirm GOOSE transmission.
  • Check dataset values.
  • Verify state changes.
  • Inspect retransmission behavior.
  • Record packet capture evidence.

Subscriber testing

  • Confirm message reception.
  • Verify external references.
  • Check signal mapping.
  • Verify application logic.
  • Test the intended output or response.

Failure and recovery testing

  • Test communication interruption under an approved procedure.
  • Verify supervision and alarms.
  • Verify configured failure behavior.
  • Restore communication.
  • Confirm normal operation.

Documentation

  • Save Wireshark captures.
  • Record test results.
  • Document configuration changes.
  • Archive final approved configuration files.

19. Conclusion

GOOSE testing is an essential part of IEC 61850 commissioning in substations using MiCOM protection relays.

A successful test must verify more than the presence of Ethernet packets. It must confirm that the publisher transmits the correct information, the network delivers the messages, the subscriber recognizes them, the signals are mapped correctly and the intended protection or automation application operates as designed.

Wireshark, IED diagnostics, system configuration files and functional test equipment all contribute to a complete commissioning process.

By following a structured approach, engineers can identify communication problems more efficiently and improve the reliability of IEC 61850-based protection and substation automation systems.

20. Practical MiCOM and IEC 61850 Training by Elec-Engg

Elec-Engg provides practical training in power system protection, MiCOM relays and substation automation.

Our training covers:

  • MiCOM protection relay engineering
  • IEC 61850 architecture and data modeling
  • MMS communication and reporting
  • GOOSE publisher and subscriber configuration
  • GOOSE datasets and control blocks
  • SCL, ICD, CID and SCD files
  • GOOSE testing and commissioning
  • Wireshark packet analysis
  • IEC 61850 troubleshooting
  • Practical protection and automation applications

Training is available through video courses, structured self-paced training, face-to-face sessions and customized in-house programs.

Visit Elec-Engg to explore practical courses by Dr Saeed Roostaee in power system protection and substation automation.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top