MiCOM IEC 61850 GOOSE Configuration: GOOSE Publisher, Subscriber, Datasets, Control Blocks and Practical Protection Applications

1. Introduction

Generic Object-Oriented Substation Event (GOOSE) messaging is one of the most important communication services defined by IEC 61850. It enables protection relays and other intelligent electronic devices (IEDs) to exchange status information, protection signals, interlocking commands and trip-related information directly over an Ethernet network.

In conventional substations, signals such as breaker failure, interlocking, blocking, permissive trip and protection initiation are commonly exchanged through copper wiring and binary inputs and outputs.

With IEC 61850 GOOSE, these signals can be transmitted between compatible IEDs using Ethernet multicast communication.

MiCOM protection relays can participate in GOOSE-based applications where the specific relay model, communication hardware, firmware and IEC 61850 implementation support the required services.

This article explains the practical engineering of GOOSE communication in MiCOM protection systems, including publishers, subscribers, datasets, GOOSE control blocks, SCL configuration and commissioning.

2. What Is GOOSE Communication?

GOOSE is an event-driven communication mechanism defined in IEC 61850-8-1.

It allows an IED to publish a dataset containing information such as:

  • Protection start signals.
  • Protection trip signals.
  • Circuit breaker status.
  • Disconnector and earthing switch positions.
  • Interlocking conditions.
  • Breaker failure initiation.
  • Blocking and permissive signals.
  • General-purpose binary indications.

GOOSE messages are transmitted directly over Ethernet using multicast communication.

Unlike MMS communication, GOOSE does not use TCP/IP or require a TCP connection between the publisher and subscriber.

GOOSE Ethernet frames use EtherType 0x88B8.

A typical GOOSE communication path is:

Protection Relay A → Ethernet Switch → Protection Relay B

Relay A publishes a GOOSE message, and Relay B receives and processes the subscribed information.

The actual protection application depends on the device’s supported IEC 61850 data model and internal logic.

3. GOOSE Publisher and Subscriber

Two important roles must be understood when engineering GOOSE communication.

3.1 GOOSE Publisher

The publisher is the IED that generates and transmits GOOSE messages.

For example, a MiCOM feeder protection relay detects an overcurrent condition and publishes a protection trip signal.

The published dataset may contain:

  • Protection start.
  • Protection trip.
  • Circuit breaker status.
  • General-purpose indications.

The publisher uses a GOOSE control block to define the transmission of the selected dataset.

3.2 GOOSE Subscriber

The subscriber is the IED that receives and processes GOOSE messages.

For example, another MiCOM relay receives a GOOSE blocking signal from the first relay.

The received information can be connected to an application function or programmable logic, depending on the relay’s implementation.

The subscriber must be configured with the correct external signal reference and communication parameters.

3.3 Publisher and Subscriber Example

Consider two feeders connected to the same busbar.

  • Feeder 1 relay detects a fault.
  • Feeder 1 relay publishes a GOOSE blocking signal.
  • Feeder 2 relay subscribes to this signal.
  • Feeder 2 relay uses the received signal in its protection logic.

Example communication architecture

       FEEDER 1                         FEEDER 2
   +----------------+               +----------------+
   | MiCOM Relay A  |               | MiCOM Relay B  |
   |                |               |                |
   | Protection     |               | Protection     |
   | Function       |               | Function       |
   |                |               |                |
   | GOOSE          |               | GOOSE          |
   | Publisher      |               | Subscriber     |
   +-------+--------+               +--------+-------+
           |                                 |
           +------------+   +----------------+
                        |   |
                 +------v---v------+
                 | Ethernet Switch |
                 +-----------------+

The exact topology and redundancy arrangement depend on the substation network design.

4. GOOSE Message Structure

A GOOSE message contains several important fields used by the receiving IED to identify, supervise and process the communication.

The main fields include:

FieldDescription
APPIDIdentifies the GOOSE application
Destination MACMulticast destination address
VLAN IDIdentifies the configured VLAN
VLAN PriorityDefines Ethernet traffic priority
gocbRefGOOSE control block reference
datSetDataset reference
goIDOptional GOOSE identifier
tTimestamp associated with the message
stNumState number
sqNumSequence number
timeAllowedToLiveMaximum expected validity interval before the next message
confRevConfiguration revision of the GOOSE control block
numDatSetEntriesNumber of dataset entries
allDataPublished dataset values

Two fields are particularly important during troubleshooting.

stNum – State Number

The state number changes when the published dataset state changes.

For example, when a protection trip signal changes from FALSE to TRUE, the publisher transmits a new state with an updated state number.

sqNum – Sequence Number

The sequence number advances as the publisher retransmits a particular state.

GOOSE retransmission allows subscribers to receive the latest state even if an individual Ethernet frame is lost.

timeAllowedToLive

This field tells the subscriber how long the currently received state may be considered valid without another expected transmission.

If the expected messages are not received within the applicable supervision interval, the subscriber can identify a communication failure.

confRev

This field represents the configuration revision associated with the GOOSE control block and its dataset configuration. It is not the relay firmware revision.

A mismatch between the expected and received configuration can indicate an engineering or interoperability problem.

5. GOOSE Dataset Engineering

A dataset defines the information transmitted by a GOOSE publisher.

It contains selected data attributes from the IED’s IEC 61850 data model.

For example, a feeder protection relay may publish:

  • Protection trip status.
  • Protection start status.
  • Circuit breaker position.
  • Breaker failure initiation.

A dataset should contain only the information required by the receiving devices and the intended application.

5.1 Dataset Members

Dataset members are selected using functional constraint data attributes (FCDA) in the SCL configuration.

An FCDA identifies the source information using parameters such as:

  • Logical device.
  • Logical node.
  • Data object.
  • Data attribute.
  • Functional constraint.

An illustrative data reference might look like:

IED_A/PROT/PTOC1.Op.general

This is an example of a logical reference, not a guaranteed reference available in every MiCOM relay.

The actual references must be taken from the device’s IEC 61850 data model.

5.2 Selecting Dataset Information

When designing a dataset, consider:

  1. Which protection or control signals must be transmitted?
  2. Which IEDs need to receive these signals?
  3. Are the selected data objects supported by the publisher?
  4. Are the data types and functional constraints compatible?
  5. Is the dataset unnecessarily large?
  6. Does the subscriber correctly map each dataset member?

A well-designed dataset improves engineering clarity and reduces unnecessary network traffic.

6. GOOSE Control Block (GoCB)

The GOOSE Control Block defines how an IED publishes a dataset.

It is commonly represented in SCL configuration through the GSEControl element.

The GOOSE control block contains parameters associated with:

  • GOOSE identifier.
  • Dataset reference.
  • Control block name.
  • Configuration revision.
  • Transmission behavior.
  • GOOSE application settings.

The control block is associated with a logical node, commonly the LLN0 logical node, depending on the implementation.

An IED may support multiple GOOSE control blocks, but the number and capabilities depend on its model and firmware.

6.1 GOOSE Control Block Example

A simplified SCL representation is:

<GSEControl
    name="gcbTrip"
    type="GOOSE"
    datSet="DS_Protection"
    appID="GCB_TRIP"
    confRev="1"/>

This example illustrates the general SCL structure. Actual configuration files contain additional information and must follow the applicable schema and device-specific requirements.

7. SCL Configuration for GOOSE Communication

IEC 61850-6 defines Substation Configuration Language (SCL), an XML-based language used to describe IED capabilities, communication settings and substation engineering.

Several SCL elements are important for GOOSE engineering.

SCL elementPurpose
DataSetDefines the published data
FCDAIdentifies individual dataset members
GSEControlDefines a GOOSE control block
GSEDefines GOOSE communication information
AddressContains communication address parameters
PDefines individual parameter values
ExtRefDescribes an external reference
InputsDescribes external input configuration
ConnectedAPAssociates an IED access point with communication configuration

7.1 DataSet

The DataSet element defines the collection of data attributes to be transmitted.

7.2 GSEControl

The GSEControl element defines the publisher’s GOOSE control block.

7.3 GSE and Address

The GSE and Address elements describe communication configuration, including relevant destination and network parameters.

Depending on the SCL version and implementation, these parameters can include:

  • MAC address.
  • APPID.
  • VLAN ID.
  • VLAN priority.

7.4 ExtRef

The ExtRef element describes an external reference used to identify information originating from another IED.

It is particularly important in engineering GOOSE subscriber relationships.

7.5 Inputs

The Inputs element can describe external input connections associated with an IED’s logical node configuration.

The exact way a relay uses these elements depends on its IEC 61850 implementation.

8. Practical Example: MiCOM Relay-to-Relay GOOSE Trip Signal

Consider a substation with two feeders.

Feeder 1 and Feeder 2 are equipped with IEC 61850-compatible MiCOM protection relays.

The objective is to transmit a protection trip signal from Relay A to Relay B using GOOSE.

Step 1: Configure the Publisher

In Relay A:

  • Identify the required protection trip signal.
  • Confirm its IEC 61850 data reference.
  • Create a dataset.
  • Add the required trip indication.
  • Create a GOOSE control block.
  • Associate the control block with the dataset.
  • Configure the required communication parameters.

Step 2: Configure the Subscriber

In Relay B:

  • Identify the required external signal.
  • Configure the GOOSE subscription using the system engineering workflow supported by the relay.
  • Map the received dataset member to the appropriate external signal.
  • Connect the signal to the required application logic.
  • Verify the expected TRUE and FALSE states.

Step 3: Configure Ethernet Communication

Check the following parameters:

  • Publisher and subscriber network connectivity.
  • GOOSE multicast destination address.
  • APPID.
  • VLAN ID.
  • VLAN priority.
  • Ethernet switch multicast handling.
  • Network redundancy, if implemented.

Step 4: Verify the Application

Inject the required test condition into Relay A.

Confirm that:

  1. Relay A detects the intended condition.
  2. The publisher changes the GOOSE dataset state.
  3. The GOOSE message is transmitted.
  4. Relay B receives the message.
  5. The subscribed signal changes correctly.
  6. The application logic responds as intended.

A received GOOSE frame alone does not prove that the protection application is operating correctly. End-to-end testing is essential.

9. GOOSE Configuration Using MiCOM Engineering Tools

MiCOM engineering workflows depend on the exact relay family and IEC 61850 implementation.

S1 Agile is used for supported MiCOM device engineering. However, system-level SCL engineering and GOOSE publisher/subscriber configuration may require a separate IEC 61850 system configuration tool.

A typical workflow includes:

  1. Identify the relay model and firmware.
  2. Confirm IEC 61850 communication capabilities.
  3. Obtain the appropriate ICD or other supported SCL description.
  4. Create or open the substation configuration project.
  5. Add the relevant IEDs.
  6. Configure IED names and access points.
  7. Define publisher datasets.
  8. Configure GOOSE control blocks.
  9. Configure subscriber external references.
  10. Allocate communication addresses.
  11. Validate the SCL configuration.
  12. Generate device-specific configuration files where supported.
  13. Transfer the configuration to the IEDs using the approved procedure.
  14. Verify communication and application behavior.

Do not assume that every MiCOM relay supports the same SCL import, export or configuration functions through S1 Agile.

Always verify the engineering workflow against the specific device documentation.

10. Ethernet Network Requirements

GOOSE communication depends on the correct Ethernet network configuration.

Incorrect switch settings or network design can prevent a subscriber from receiving GOOSE messages.

10.1 Multicast Communication

GOOSE uses Ethernet multicast communication.

The publisher sends frames to a multicast destination MAC address, and relevant network devices forward the frames to the required ports.

Switch configuration should be checked to ensure GOOSE multicast traffic reaches all intended subscribers.

10.2 VLAN Configuration

VLANs can separate protection communication from other substation network traffic.

For example:

  • VLAN 10: Protection GOOSE.
  • VLAN 20: SCADA and MMS communication.
  • VLAN 30: Engineering access.

These are illustrative values only. Actual VLAN allocation must follow the substation network design.

10.3 VLAN Priority

Protection-related GOOSE traffic can be assigned an appropriate IEEE 802.1Q priority.

The priority configuration should be coordinated with the Ethernet switch QoS policy.

10.4 Switch Configuration

Important switch parameters include:

  • VLAN membership.
  • Multicast forwarding.
  • IGMP-related behavior where relevant to the network design.
  • QoS configuration.
  • Port status.
  • Port speed and duplex.
  • Redundant network configuration.
  • Network diagnostics.

GOOSE multicast forwarding should not be treated as ordinary IP multicast forwarding without checking the switch’s Layer 2 behavior.

11. GOOSE Supervision and Communication Failure

GOOSE communication must be supervised.

The subscriber monitors the expected messages and their validity.

If communication is interrupted, the subscriber can detect that the received information is no longer being refreshed within the applicable time interval.

Possible causes include:

  • Ethernet cable failure.
  • Switch power failure.
  • Incorrect VLAN configuration.
  • Wrong multicast address.
  • Incorrect APPID.
  • Publisher configuration changes.
  • Subscriber configuration mismatch.
  • Network redundancy failure.
  • IED communication module problems.

11.1 What Happens When GOOSE Communication Fails?

The application response depends on the receiving relay’s implementation and the engineering configuration.

Possible responses include:

  • Communication failure indication.
  • Invalid quality indication.
  • Subscriber signal supervision alarm.
  • Application blocking or fallback logic.
  • A configured safe-state response.

Do not assume that all MiCOM relays automatically force a subscribed signal to FALSE when communication is lost.

The actual failure behavior must be verified in the device documentation and through testing.

12. Wireshark Analysis of MiCOM GOOSE Messages

Wireshark is a useful tool for examining GOOSE traffic during commissioning and troubleshooting.

Connect a laptop to an appropriately configured switch mirror port or network TAP.

Capture the Ethernet traffic and apply the following display filters.

Wireshark filterPurpose
gooseDisplay GOOSE packets
eth.type == 0x88b8Identify GOOSE Ethernet frames
vlan.id == 10Filter a specific VLAN
tcp.port == 102Examine MMS communication
tcp.analysis.retransmissionIdentify TCP retransmissions
tcp.flags.reset == 1Identify TCP reset packets

The TCP filters are useful for MMS diagnostics, not for GOOSE itself.

12.1 Important GOOSE Fields to Examine

When inspecting a GOOSE packet, check:

  • Source MAC address.
  • Destination MAC address.
  • APPID.
  • VLAN ID.
  • VLAN priority.
  • gocbRef.
  • datSet.
  • stNum.
  • sqNum.
  • timeAllowedToLive.
  • confRev.
  • Dataset values.

12.2 Example Analysis

Suppose Relay A publishes a trip signal.

Initially:

Trip = FALSE
stNum = 1
sqNum = 0

After a protection operation:

Trip = TRUE
stNum = 2
sqNum = 0

Subsequent retransmissions of the same state may show:

Trip = TRUE
stNum = 2
sqNum = 1

The sequence number continues advancing as the publisher retransmits the current state.

This behavior helps engineers distinguish a state change from repeated transmission of an unchanged state.

13. GOOSE Commissioning and Testing Procedure

A systematic commissioning procedure is essential before placing GOOSE-based protection applications into service.

13.1 Documentation Verification

  • Confirm the exact MiCOM relay model.
  • Check the communication hardware.
  • Verify firmware compatibility.
  • Review the MICS, PICS and PIXIT documentation where available.
  • Check the ICD and SCL files.
  • Confirm supported GOOSE services.
  • Review the approved protection logic.

13.2 Publisher Testing

  • Verify dataset members.
  • Check the GOOSE control block.
  • Confirm the APPID.
  • Check the multicast MAC address.
  • Verify VLAN configuration.
  • Trigger each published signal.
  • Confirm the expected dataset changes.

13.3 Subscriber Testing

  • Confirm the external references.
  • Verify the dataset mapping.
  • Check the received signal state.
  • Test TRUE and FALSE transitions.
  • Verify signal quality and supervision.
  • Confirm the signal reaches the intended logic.

13.4 Communication Failure Testing

Where permitted by the approved commissioning procedure:

  • Disconnect the communication link.
  • Interrupt the relevant switch path.
  • Verify the subscriber’s communication failure indication.
  • Check the configured application response.
  • Restore communication.
  • Verify recovery and correct signal state.

13.5 End-to-End Testing

The most important test is to verify the complete signal path:

Protection Input → Relay Logic → GOOSE Publisher → Ethernet Network → GOOSE Subscriber → Application Logic → Intended Output

The test must confirm the intended protection or control function, not simply successful Ethernet communication.

14. Common GOOSE Configuration Problems

ProblemPossible causeRecommended check
Subscriber does not receive GOOSENetwork or multicast issueCheck switch forwarding and packet capture
Incorrect GOOSE signalWrong dataset mappingVerify FCDA and external references
APPID mismatchIncorrect communication configurationCompare publisher and subscriber project data
VLAN mismatchIncorrect VLAN allocationCheck switch ports and SCL parameters
GOOSE configuration mismatchDifferent control block or dataset configurationVerify confRev and configuration files
Signal remains unchangedWrong source data referenceCheck publisher dataset and relay logic
Communication supervision alarmMissing or delayed messagesCheck network health and timeAllowedToLive
GOOSE works during testing but not in serviceNetwork or application integration issuePerform end-to-end testing under operating conditions

15. GOOSE Cybersecurity Considerations

GOOSE communication is important for protection and control applications, so its network must be appropriately protected.

Recommended practices include:

  • Separate protection communication from office networks.
  • Restrict engineering workstation access.
  • Use controlled access to Ethernet switches.
  • Protect SCL configuration files.
  • Maintain approved configuration backups.
  • Monitor unexpected GOOSE traffic.
  • Document all publisher and subscriber relationships.
  • Apply network segmentation and access-control policies.
  • Follow applicable IEC 62351 guidance and the organization’s cybersecurity policy.

Do not assume that GOOSE multicast traffic is encrypted or authenticated simply because it uses IEC 61850.

Security capabilities depend on the relevant standards, devices and implementation.

16. Practical Engineering Recommendations

For reliable MiCOM GOOSE engineering, follow these principles:

  1. Confirm IEC 61850 capabilities before starting the project.
  2. Use the correct ICD and device-specific documentation.
  3. Keep datasets focused on the required application.
  4. Maintain consistent IED names and data references.
  5. Document all publisher-subscriber relationships.
  6. Verify APPID, multicast address and VLAN settings.
  7. Confirm switch multicast forwarding and QoS behavior.
  8. Check GOOSE supervision and failure responses.
  9. Use Wireshark during commissioning.
  10. Test the complete protection or control application.
  11. Maintain configuration backups and revision records.
  12. Revalidate the system after any relevant dataset or control-block modification.

A successful SCL validation does not automatically prove that two devices will interoperate correctly. Device compatibility and end-to-end testing remain essential.

17. Conclusion

GOOSE communication is a fundamental part of IEC 61850-based protection and substation automation systems.

For MiCOM protection relays, correct GOOSE engineering requires more than selecting signals and connecting Ethernet cables. Engineers must understand the publisher and subscriber architecture, datasets, FCDA references, GOOSE control blocks, SCL configuration, network parameters and application logic.

A properly engineered GOOSE system can reduce conventional wiring and support fast communication between protection and control devices.

However, the final design must always be based on the exact MiCOM relay model, firmware, communication hardware and documented IEC 61850 capabilities.

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

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

Our training covers:

  • MiCOM relay configuration and engineering.
  • IEC 61850 architecture and data models.
  • GOOSE publisher and subscriber configuration.
  • MMS communication and SCADA integration.
  • ICD, CID, IID and SCD file engineering.
  • GOOSE and MMS testing.
  • Wireshark communication analysis.
  • SICAM PAS integration.
  • Practical protection and control applications.

Training is available through:

  • Pre-recorded video courses.
  • Structured self-paced training.
  • Face-to-face training.
  • Customized in-house training for companies and utilities.

Practical courses by Dr Saeed Roostaee / Elec-Engg

Website: https://elec-engg.com/

Leave a Comment

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

Scroll to Top