IEC 61850 in SEL Relays: GOOSE, MMS, Sampled Values and Configuration

IEC 61850 in SEL Protection Relays: Complete Guide to MMS, GOOSE, Sampled Values, SCL Configuration and Testing

Table Of Contents
  1. 1. Introduction to IEC 61850 in SEL relays
  2. 2. SEL relays supporting IEC 61850
  3. 3. IEC 61850 communication architecture
  4. 4. MMS communication in SEL relays
  5. 5. GOOSE communication in SEL relays
  6. 6. Sampled Values (SV) in SEL relays
  7. 7. IEC 61850 logical nodes in SEL relays
  8. 8. IEC 61850 SCL files: ICD, IID, SCD and CID
  9. 9. acSELerator Architect: IEC 61850 engineering software for SEL relays
  10. 10. Step-by-step IEC 61850 configuration for SEL relays
  11. 11. Practical GOOSE configuration example: Feeder trip to bay controller
  12. 12. PRP, HSR and network redundancy in SEL IEC 61850 systems
  13. 13. PTP time synchronization in SEL relays
  14. 14. IEC 61850 testing and commissioning of SEL relays
  15. 15. Using Wireshark for IEC 61850 troubleshooting
  16. 16. Cybersecurity considerations for IEC 61850 SEL relays
  17. 17. Common IEC 61850 engineering mistakes in SEL relays
  18. 18. SEL IEC 61850 training: Practical engineering topics
  19. 19. Frequently asked questions about IEC 61850 in SEL relays
  20. 20. Official SEL references and technical documentation

1. Introduction to IEC 61850 in SEL relays

IEC 61850 is an international standard for communication networks and systems used in electrical substations. It defines a common data model, communication services and engineering processes that allow protection relays, bay controllers, merging units, SCADA systems and other intelligent electronic devices (IEDs) to exchange information.

Schweitzer Engineering Laboratories (SEL) provides a wide range of protection relays and substation automation products supporting IEC 61850.

Examples include:

  • SEL-751 Feeder Protection Relay.
  • SEL-451 Protection, Automation and Bay Control System.
  • SEL-421 Transmission Protection System.
  • SEL-411L Line Differential Protection System.
  • SEL-487B Bus Differential and Breaker Failure Relay.
  • SEL-787 Transformer Protection Relay.
  • SEL-700G Generator Protection Relay.
  • SEL-710-5 Motor Protection Relay.

Depending on the product and installed options, these relays can support different IEC 61850 services, including:

  • MMS (Manufacturing Message Specification).
  • GOOSE (Generic Object-Oriented Substation Event).
  • Sampled Values (SV).
  • Substation Configuration Language (SCL).
  • Ethernet-based communication.
  • Precision Time Protocol (PTP).
  • PRP and other network redundancy arrangements.

IEC 61850 allows engineers to reduce conventional hardwired connections, exchange protection signals between IEDs and integrate protection devices into modern digital substations.

However, IEC 61850 is much more than an Ethernet communication protocol. It also defines how information is represented, named, configured and exchanged between devices.

2. SEL relays supporting IEC 61850

SEL has implemented IEC 61850 across multiple protection and automation product families.

The following table gives examples of SEL products with IEC 61850 capabilities. The exact services, editions and options must be checked against each product’s documentation.

SEL relayMain applicationIEC 61850 considerations
SEL-751Feeder protectionIEC 61850 Edition 2.1 option
SEL-451Feeder protection and bay controlIEC 61850 Edition 2.1 option
SEL-421Transmission line protectionCheck exact model and communication options
SEL-411LLine differential and distance protectionCheck model-specific IEC 61850 and digital secondary options
SEL-487BBus differential protectionIEC 61850 and digital process-bus options depend on model
SEL-787-2/-3/-4Transformer protectionIEC 61850 Edition 2 support
SEL-700GGenerator protectionIEC 61850 options depend on configuration
SEL-710-5Motor protectionIEC 61850 options depend on configuration

Important engineering note: An SEL relay supporting MMS does not automatically mean it supports GOOSE or Sampled Values. Always check the model-specific Protocol Implementation Conformance Statement (PICS), Model Implementation Conformance Statement (MICS), PIXIT and data sheet.

3. IEC 61850 communication architecture

IEC 61850 communication in a substation is commonly divided into two main levels:

  1. Station bus.
  2. Process bus.

These two communication levels have different purposes.

3.1 Station bus

The station bus connects protection relays, bay control units, station controllers, gateways, HMIs and engineering workstations.

Typical station-bus communication includes:

  • MMS reporting.
  • GOOSE messaging.
  • Remote monitoring.
  • Remote control.
  • Interlocking signals.
  • Protection status exchange.
  • Measurement acquisition.

For example, an SEL-751 feeder protection relay can communicate with a station-level SCADA system using MMS reporting, subject to its installed IEC 61850 option.

An SEL-451 bay controller can exchange breaker status, measurements and control information with the station automation system.

3.2 Process bus

The process bus connects protection and control IEDs with merging units and other equipment close to the primary plant.

It can replace conventional analog copper wiring for current and voltage signals.

Typical process-bus communication includes:

  • Sampled Values (SV).
  • GOOSE messages.
  • Precision Time Protocol (PTP).

For example, a merging unit can acquire current and voltage signals from CTs and VTs and publish digital Sampled Values over an Ethernet network.

A protection relay subscribes to these values and uses them to perform its protection calculations.

Process-bus engineering requires careful attention to network architecture, time synchronization, redundancy, testing and cybersecurity.

4. MMS communication in SEL relays

MMS stands for Manufacturing Message Specification.

It is an application-layer communication protocol used by IEC 61850 for exchanging information between IEDs and client systems.

MMS is commonly used for communication between protection relays and:

  • SCADA systems.
  • Station controllers.
  • HMI systems.
  • Substation gateways.
  • Engineering and monitoring systems.

4.1 How MMS works

Consider an SEL-751 feeder protection relay connected to a station Ethernet network.

The relay acts as an IEC 61850 server, while a SCADA system or station controller acts as an MMS client.

The client can access supported information from the relay, such as:

  • Phase current measurements.
  • Voltage measurements.
  • Frequency.
  • Active and reactive power.
  • Circuit-breaker status.
  • Protection element pickup.
  • Trip indications.
  • Alarm information.
  • Device health information.

The client can also receive event-driven information through report control blocks.

4.2 MMS reporting

IEC 61850 reporting allows an IED to transmit selected information to an external client.

Rather than continuously polling every measurement, the client can subscribe to reports and receive updates when configured conditions occur.

For example, an SEL feeder relay may report:

  • Breaker opening.
  • Breaker closing.
  • Protection pickup.
  • Protection trip.
  • Communication alarm.
  • Change in measured current.
  • Device failure indication.

The actual information available depends on the relay’s IEC 61850 data model and configured datasets.

4.3 Buffered and unbuffered reports

IEC 61850 supports different report-control arrangements.

Buffered Report Control Block (BRCB)

Buffered reporting stores events so that they can be transmitted when the client reconnects, subject to buffer capacity and configuration.

This is useful when event preservation is important.

Unbuffered Report Control Block (URCB)

Unbuffered reporting transmits events while the client is connected. Events occurring during communication interruption may not be available after reconnection.

The engineer should select the appropriate reporting method according to the SCADA design and event-retention requirements.

4.4 MMS communication example

Consider a feeder protection relay connected to a station controller.

When the relay detects a feeder fault:

  1. The protection element operates.
  2. The relay issues the configured trip command.
  3. The relay updates its internal protection and breaker status information.
  4. The IEC 61850 reporting function detects the configured data change.
  5. The relay sends the corresponding report to the MMS client.
  6. The station HMI displays the feeder trip indication.

This provides a standardized alternative to many individual hardwired status signals.

5. GOOSE communication in SEL relays

GOOSE stands for Generic Object-Oriented Substation Event.

It is one of the most important IEC 61850 services for protection and control applications.

GOOSE allows IEDs to exchange fast event-based information directly over an Ethernet network.

Unlike conventional MMS client-server communication, GOOSE uses publisher-subscriber communication.

One IED publishes information, and one or more subscribing IEDs receive and use that information.

5.1 GOOSE operating principle

Consider two SEL protection relays:

  • SEL-751: Feeder protection.
  • SEL-451: Bay control and protection.

Suppose the SEL-751 detects a feeder trip condition.

It can publish a GOOSE message containing the relevant trip status.

The SEL-451 subscribes to the message and uses the received information in its configured control logic.

The sequence is:

  1. The SEL-751 detects the fault.
  2. The protection element operates.
  3. The relay changes the relevant internal logic status.
  4. The GOOSE publisher transmits the updated information.
  5. The SEL-451 receives the GOOSE message.
  6. The subscribed data are mapped into the receiving relay’s logic.
  7. The receiving relay executes the configured control or interlocking function.

This arrangement can reduce the need for conventional copper wiring between IEDs.

5.2 Typical GOOSE applications

GOOSE messaging is widely used for:

  • Circuit-breaker interlocking.
  • Breaker failure initiation.
  • Busbar protection signals.
  • Direct transfer trip.
  • Protection blocking.
  • Protection permissive signals.
  • Trip and close commands.
  • Breaker status exchange.
  • Transformer protection interlocking.
  • Load shedding.
  • Transfer schemes.

5.3 GOOSE publisher and subscriber

In an IEC 61850 engineering project, each GOOSE communication relationship requires publisher and subscriber configuration.

Publisher

The publisher IED defines the information to be transmitted.

The engineer configures:

  • Dataset.
  • GOOSE Control Block (GoCB).
  • Destination multicast MAC address.
  • APPID.
  • VLAN ID.
  • VLAN priority.
  • Transmission behavior.

Subscriber

The subscriber IED receives the published information.

The engineer configures:

  • Publisher identification.
  • Expected GOOSE dataset.
  • Data mapping.
  • Subscribed signals.
  • Application logic.
  • Communication failure handling.

The subscriber must recognize the publisher’s GOOSE message and map the received data into the appropriate internal logic variables.

5.4 GOOSE retransmission

GOOSE uses a retransmission mechanism to improve the probability that subscribers receive important state changes.

When an event occurs, the publisher initially transmits messages at short intervals.

The retransmission interval then increases until the normal steady-state retransmission interval is reached.

This means that a GOOSE message is not simply transmitted once.

Repeated transmission also allows subscribers to monitor the communication stream and detect missing or abnormal messages.

5.5 GOOSE communication supervision

GOOSE communication must be supervised.

Engineers should consider:

  • Communication timeout.
  • Dataset integrity.
  • Publisher identification.
  • Test and simulation flags.
  • Quality information.
  • Network redundancy.
  • Subscriber behavior following communication failure.

A protection or interlocking scheme must have a defined response when a subscribed GOOSE signal becomes invalid or unavailable.

For example, a GOOSE-based breaker failure scheme should not assume that a communication failure is equivalent to a healthy breaker status.

The failure response must be designed explicitly.

6. Sampled Values (SV) in SEL relays

Sampled Values are digital representations of analog current and voltage measurements.

They are defined by IEC 61850-9-2 and related standards, including IEC 61869-9.

In a conventional substation, current and voltage signals are transferred from CTs and VTs to protection relays through copper wiring.

In a digital substation using process bus, merging units convert these analog measurements into digital Sampled Values.

Protection relays receive the data over Ethernet and use them for protection calculations.

6.1 What is a merging unit?

A merging unit (MU) is a device that receives analog signals from CTs and VTs and converts them into digital measurement streams.

Typical merging-unit functions include:

  • Current acquisition.
  • Voltage acquisition.
  • Analog-to-digital conversion.
  • Sampled Values publication.
  • Time synchronization.
  • GOOSE communication.
  • Breaker status acquisition, where supported.

SEL provides merging-unit and intelligent merging-unit solutions for digital substations.

6.2 Sampled Values operating principle

Consider a digital feeder protection system.

The system includes:

  • Current transformers.
  • Voltage transformers.
  • SEL merging unit.
  • Ethernet process-bus network.
  • SEL protection relay.

The operating sequence is:

  1. CTs and VTs provide analog signals.
  2. The merging unit receives the analog signals.
  3. The merging unit samples the signals.
  4. Digital Sampled Values are published over Ethernet.
  5. The protection relay subscribes to the appropriate SV stream.
  6. The relay processes the current and voltage measurements.
  7. Protection elements perform their calculations.
  8. The relay issues a trip command when required.

This architecture can significantly reduce copper wiring between the primary equipment and protection panels.

6.3 SV publisher and subscriber

In a process-bus application:

  • The merging unit usually acts as an SV publisher.
  • The protection relay acts as an SV subscriber.

The publisher transmits digital measurements, and the subscriber processes the received values.

The configuration must define the correct SV stream, dataset, sample rate, synchronization requirements and subscriber mapping.

6.4 SV and GOOSE comparison

FeatureGOOSESampled Values
Main purposeFast event and status exchangeDigital analog measurements
Typical dataTrip, breaker status, interlockingCurrent and voltage samples
Communication modelPublisher-subscriberPublisher-subscriber
Main applicationStation bus and process busProcess bus
ExampleBreaker failure initiationThree-phase current measurements

6.5 SV communication and time synchronization

Sampled Values applications depend on accurate and consistent sampling.

Time synchronization is therefore an essential part of process-bus engineering.

PTP, defined by IEEE 1588 and relevant IEC profiles, is commonly used for time synchronization in digital substations.

The engineering design must specify the supported PTP profile, grandmaster arrangement, network architecture and failure behavior.

7. IEC 61850 logical nodes in SEL relays

Logical nodes are a fundamental part of the IEC 61850 data model.

Instead of defining information using proprietary relay-specific addresses, IEC 61850 organizes information into standardized logical devices, logical nodes, data objects and data attributes.

A logical node represents a specific function or information category.

Examples include:

Logical nodeGeneral function
PTOCTime-overcurrent protection
PIOCInstantaneous overcurrent protection
PDIFDifferential protection
PDISDistance protection
PDOPDirectional overcurrent protection
MMXUMeasurement and metering
XCBRCircuit-breaker information
CSWISwitch control
CILOInterlocking
RBRFBreaker failure
GGIOGeneric process input/output
LPHDPhysical device information
LLN0Logical device common information

The exact logical nodes available depend on the relay model and IEC 61850 implementation.

7.1 Example: Overcurrent protection logical node

Consider an SEL-751 feeder protection relay.

Its overcurrent protection information may be represented through appropriate protection logical nodes, such as PTOC or PIOC.

These nodes can contain information associated with:

  • Protection operation.
  • Pickup status.
  • Start status.
  • Trip status.
  • Mode and quality information.

The exact data objects and attributes must be checked in the model-specific IEC 61850 data model.

7.2 Example: Circuit-breaker logical node

The XCBR logical node represents circuit-breaker information.

It can provide information such as:

  • Breaker position.
  • Breaker operating state.
  • Breaker-related status information.

The CSWI logical node is associated with switch control.

CILO can be used for interlocking information.

These logical nodes allow a station-level system to use a standardized representation of switching equipment.

7.3 Logical nodes and datasets

Logical nodes contain data objects and attributes.

Engineers select the required information and group it into datasets.

These datasets are then used by communication services such as MMS reporting and GOOSE messaging.

For example, a feeder trip dataset might contain:

  • Feeder protection trip status.
  • Circuit-breaker position.
  • Protection alarm.
  • Device health information.

The dataset is then associated with the appropriate communication control block.

8. IEC 61850 SCL files: ICD, IID, SCD and CID

SCL stands for Substation Configuration Language.

It is an XML-based engineering language used to describe IEC 61850 substation communication systems.

SCL files are important because they provide standardized information about IED capabilities, communication configuration and the overall substation architecture.

The main SCL file types include:

FileFull nameMain purpose
ICDIED Capability DescriptionDescribes an IED’s communication capabilities
IIDInstantiated IED DescriptionDescribes an instantiated IED configuration
SCDSubstation Configuration DescriptionDescribes the overall substation configuration
CIDConfigured IED DescriptionContains the configuration intended for a particular IED

8.1 ICD file

The ICD file describes the communication capabilities of an IED.

It can contain information about:

  • IED name and type.
  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.
  • Communication services.
  • GOOSE capabilities.
  • MMS capabilities.
  • Sampled Values capabilities, where supported.

For example, an SEL relay’s ICD file can be imported into an IEC 61850 engineering tool to represent the relay’s available communication model.

8.2 IID file

The IID file represents an instantiated IED description.

It can be used to exchange information about an individual IED configuration within the engineering process.

8.3 SCD file

The SCD file represents the overall substation communication configuration.

It can contain information about multiple IEDs, their communication relationships and the substation network architecture.

For example, an SCD file may describe:

  • SEL-751 feeder relays.
  • SEL-451 bay controllers.
  • Merging units.
  • Station controllers.
  • GOOSE publisher-subscriber relationships.
  • MMS reporting configurations.
  • Ethernet communication networks.

8.4 CID file

The CID file is the configured description intended for an individual IED.

It contains the relevant communication configuration that is loaded into the device.

The exact workflow for importing, editing, exporting and downloading these files depends on the engineering software and the IED’s implementation.

9. acSELerator Architect: IEC 61850 engineering software for SEL relays

SEL provides acSELerator Architect SEL-5032 for IEC 61850 system configuration and documentation.

Architect is a key engineering tool for projects involving SEL protection relays and other IEC 61850-compatible devices.

It is designed to configure and document communication arrangements involving:

  • MMS.
  • GOOSE.
  • Sampled Values.
  • SCL files.
  • Station-bus networks.
  • Process-bus networks.

Architect can import and export SCL files from different IEC 61850 editions, including Edition 1, Edition 2 and Edition 2.1, subject to the supported functionality.

9.1 Main functions of acSELerator Architect

The software supports activities such as:

  • Creating IEC 61850 projects.
  • Importing IED capability files.
  • Adding SEL and third-party IEDs.
  • Configuring GOOSE messages.
  • Configuring Sampled Values.
  • Configuring MMS datasets and reports.
  • Mapping subscribed signals.
  • Editing supported IED server models.
  • Generating configured IED descriptions.
  • Validating SCL configurations.
  • Documenting communication relationships.

9.2 IED palette

Architect provides an IED palette to help engineers add devices to an IEC 61850 project.

The engineer can add the required SEL relays and other supported devices.

For example, a project may contain:

  • SEL-751 feeder protection relays.
  • SEL-451 bay controllers.
  • SEL-487B bus differential relays.
  • SEL merging units.
  • Third-party protection relays.

The exact device models available depend on the installed ICD package and supported device descriptions.

9.3 Server model configuration

Architect provides facilities to view and edit supported IED server models.

The server model includes:

  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.

This is important because the engineer must understand the available information before creating datasets and communication relationships.

9.4 Architect and QuickSet: What is the difference?

These two software applications have different primary purposes.

SoftwareMain purpose
acSELerator QuickSet SEL-5030Relay protection settings and programmable logic
acSELerator Architect SEL-5032IEC 61850 communication configuration and documentation

QuickSet is primarily used to configure protection functions, settings and control logic.

Architect is used to engineer IEC 61850 communication arrangements.

They work together in SEL engineering workflows, but they should not be treated as interchangeable tools.

10. Step-by-step IEC 61850 configuration for SEL relays

The following is a general engineering workflow for an SEL-based IEC 61850 station-bus project.

The exact procedure depends on the relay model, firmware and project engineering tool.

Step 1 – Identify the relay model and communication option

Before starting, confirm:

  • SEL relay model.
  • Firmware revision.
  • IEC 61850 edition.
  • Communication hardware.
  • MMS support.
  • GOOSE support.
  • Sampled Values support, if required.
  • Network redundancy capability.

Do not assume that every SEL relay supports the same communication functions.

Step 2 – Obtain the appropriate ICD file

Download the correct ICD file for the relay model and supported firmware.

The ICD file should match the intended relay configuration as closely as possible.

Step 3 – Create an IEC 61850 project

Open acSELerator Architect and create a new engineering project.

Define the substation and communication structure.

Step 4 – Import the SEL relay ICD file

Import the required ICD file into Architect.

Verify:

  • IED name.
  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Communication capabilities.

Step 5 – Configure IED names and network information

Define the IED identification and required communication parameters.

Typical information includes:

  • IED name.
  • IP address.
  • Subnet mask.
  • Gateway, where required.
  • Ethernet port assignments.
  • VLAN information.
  • Network redundancy settings.

IP addressing and Ethernet network planning should be coordinated with the station communication design.

Step 6 – Configure MMS datasets and reports

Select the required data objects and attributes.

Create the datasets required for SCADA monitoring and reporting.

Configure the appropriate report control blocks.

For example, a feeder protection relay may require datasets for:

  • Measurements.
  • Breaker status.
  • Protection status.
  • Alarms.
  • Device health.

Step 7 – Configure GOOSE publishers

For each GOOSE publisher, define:

  • Dataset.
  • GOOSE Control Block.
  • APPID.
  • Multicast MAC address.
  • VLAN ID.
  • VLAN priority.
  • Transmission parameters.

Ensure that the GOOSE configuration follows the project communication design.

Step 8 – Configure GOOSE subscribers

Identify the IEDs that need to receive the GOOSE information.

Configure the subscriptions and map the received data to the relevant logic variables.

For example, a bay controller may subscribe to a feeder protection trip signal.

Step 9 – Validate the configuration

Use the available validation features to check the SCL configuration.

Review:

  • Dataset definitions.
  • GOOSE publisher information.
  • Subscriber relationships.
  • Communication parameters.
  • IED naming.
  • Address assignments.
  • Logical-node references.

Step 10 – Generate and download the CID file

Generate the appropriate configured IED description for the SEL relay.

Download the communication configuration according to the device-specific procedure.

Step 11 – Verify the actual configuration

Retrieve or inspect the configuration from the relay where supported.

Compare the installed configuration with the approved engineering files.

Step 12 – Perform communication testing

Verify MMS reporting, GOOSE publishing and subscribing, and Sampled Values communication where applicable.

The final configuration should be backed up and included in the project documentation.

11. Practical GOOSE configuration example: Feeder trip to bay controller

Consider a substation containing:

  • IED 1: SEL-751 feeder protection relay.
  • IED 2: SEL-451 bay controller.
  • IED 3: Station-level SCADA system.

The objective is to transmit the feeder trip status from the SEL-751 to the SEL-451 using GOOSE.

Engineering concept

The SEL-751 acts as the GOOSE publisher.

The SEL-451 acts as the GOOSE subscriber.

The SCADA system receives the relevant status through its configured communication arrangement, such as MMS reporting.

Configuration sequence

1. Identify the feeder trip signal

Select the appropriate protection trip indication in the SEL-751 IEC 61850 server model.

2. Create a GOOSE dataset

Add the required feeder trip status and any additional signals needed by the receiving device.

3. Configure the GOOSE Control Block

Define the publisher parameters, including APPID, multicast address and VLAN settings.

4. Configure the subscriber

Import or reference the publisher configuration and configure the SEL-451 to subscribe to the required dataset.

5. Map the received signal

Map the subscribed feeder trip status into the appropriate receiving relay logic.

6. Test the communication

Operate the feeder protection element under controlled test conditions.

Verify that the SEL-751 publishes the correct GOOSE status and the SEL-451 receives and processes the signal.

7. Verify the application logic

Confirm that the receiving relay performs only the intended action.

The receiving logic should also define what happens if the GOOSE communication becomes invalid or unavailable.

12. PRP, HSR and network redundancy in SEL IEC 61850 systems

Communication availability is important in digital substations.

A communication failure can affect protection signals, SCADA monitoring and control operations.

IEC 62439-3 defines redundancy protocols including:

  • PRP – Parallel Redundancy Protocol.
  • HSR – High-availability Seamless Redundancy.

12.1 PRP

PRP uses two independent Ethernet networks, commonly called LAN A and LAN B.

A PRP-capable device transmits duplicate frames through both networks.

The receiving device accepts the first valid frame and discards the duplicate.

This provides seamless communication recovery for supported devices under the defined failure conditions.

A typical PRP arrangement includes:

  • Two independent Ethernet networks.
  • PRP-capable IEDs.
  • Redundant switches.
  • Separate communication paths.
  • Network monitoring.

12.2 HSR

HSR uses a ring-based architecture in which frames circulate through the network in both directions.

Devices receive duplicate frames through the two directions and process the first valid copy.

HSR can provide seamless redundancy in suitable network designs.

12.3 Engineering considerations

Before implementing PRP or HSR, check:

  • Relay support.
  • Ethernet port configuration.
  • Switch compatibility.
  • Network topology.
  • VLAN configuration.
  • Multicast behavior.
  • Network loading.
  • Failure monitoring.

Not every SEL relay supports both PRP and HSR. Verify the specific model and ordered communication option.

13. PTP time synchronization in SEL relays

Precision Time Protocol (PTP) is used to synchronize time between devices connected to an Ethernet network.

PTP is defined in IEEE 1588 and includes profiles used for power-system applications.

Time synchronization is important for:

  • Event recording.
  • Sequence of Events (SOE).
  • Disturbance analysis.
  • Synchrophasor applications.
  • Sampled Values.
  • Digital substation coordination.

A typical PTP arrangement includes:

  • Grandmaster clock.
  • Ethernet network.
  • Boundary or transparent clocks, where applicable.
  • SEL protection relays.
  • Merging units.

The engineer must select a compatible PTP profile and confirm the device’s time-synchronization capabilities.

PTP should not be confused with SNTP or IRIG-B. These methods have different characteristics and accuracy requirements.

14. IEC 61850 testing and commissioning of SEL relays

A successful IEC 61850 configuration does not automatically mean the communication scheme is fully tested.

Testing should cover both the protocol communication and the protection application.

14.1 Initial checks

Before testing, verify:

  • Correct relay model.
  • Firmware revision.
  • IEC 61850 edition.
  • Installed communication option.
  • Correct ICD file.
  • Approved SCD and CID files.
  • IP address and network settings.
  • VLAN configuration.
  • Network redundancy arrangement.
  • Time synchronization.

14.2 MMS testing

Verify that the SCADA or station controller can establish communication with the SEL relay.

Check:

  • Server connection.
  • Logical device access.
  • Logical node access.
  • Dataset configuration.
  • Report control blocks.
  • Measurement values.
  • Breaker status.
  • Protection indications.
  • Event reporting.

Also test report behavior following a communication interruption and reconnection.

14.3 GOOSE testing

GOOSE testing should verify both the transmitted data and the receiving application.

Check:

  • Publisher configuration.
  • Subscriber configuration.
  • Dataset.
  • APPID.
  • Multicast MAC address.
  • VLAN ID and priority.
  • Data quality.
  • Test and simulation behavior.
  • Communication supervision.
  • Receiving logic.

A suitable Ethernet monitoring tool, such as Wireshark, can help inspect GOOSE packets and identify communication problems.

14.4 Sampled Values testing

For process-bus applications, verify:

  • Correct merging-unit configuration.
  • Correct SV stream.
  • Sample rate.
  • Dataset.
  • Synchronization status.
  • Subscriber mapping.
  • Measurement scaling.
  • Phase identification.
  • Loss-of-SV response.

The protection relay must correctly interpret the incoming digital measurements.

14.5 Time synchronization testing

Verify that the IED receives the expected time source.

Check:

  • PTP grandmaster identification.
  • PTP profile.
  • Synchronization status.
  • Time accuracy indicators.
  • Holdover behavior.
  • Time quality.

14.6 Network redundancy testing

For PRP or HSR installations, simulate the relevant network failures under an approved test procedure.

Verify that communication remains available according to the designed redundancy arrangement.

Also confirm that network faults and redundancy alarms are correctly reported.

14.7 Complete protection scheme testing

Finally, test the complete protection and control sequence.

For example:

  1. Inject a fault into the SEL protection relay.
  2. Verify protection pickup and trip.
  3. Verify GOOSE publication.
  4. Verify subscriber reception.
  5. Verify the receiving IED logic.
  6. Verify the breaker trip circuit.
  7. Verify MMS reporting to SCADA.
  8. Verify event records and timestamps.

This is especially important for GOOSE-based interlocking and trip schemes.

15. Using Wireshark for IEC 61850 troubleshooting

Wireshark is a useful network analysis tool for engineers working with IEC 61850.

It can help identify communication problems by inspecting Ethernet traffic.

Common traffic types include:

CommunicationTypical Ethernet identification
GOOSEEtherType 0x88B8
Sampled ValuesEtherType 0x88BA
MMSTCP port 102
PTPDepends on PTP transport and profile

Typical Wireshark troubleshooting activities

Engineers can use Wireshark to:

  • Identify GOOSE publisher messages.
  • Check APPID and destination MAC address.
  • Inspect VLAN tags.
  • Verify GOOSE retransmission.
  • Identify Sampled Values streams.
  • Examine PTP traffic.
  • Diagnose missing or unexpected packets.
  • Investigate network interruptions.
  • Check whether the expected publisher is transmitting.

For MMS, engineers can inspect the communication session and identify connection or reporting problems.

Important: Capturing a packet does not prove that the receiving protection relay has correctly processed the information. Always combine network analysis with IED diagnostics and functional testing.

16. Cybersecurity considerations for IEC 61850 SEL relays

Digital substations introduce additional cybersecurity considerations.

Protection and automation networks must be designed to prevent unauthorized access and minimize the impact of network security incidents.

Important engineering considerations include:

  • Network segmentation.
  • Controlled access to engineering ports.
  • Secure user authentication.
  • Role-based access.
  • Firewall configuration.
  • Switch port security.
  • VLAN separation.
  • Secure remote access.
  • Firmware management.
  • Configuration backups.
  • Event and security monitoring.

IEC 62351 provides security-related standards for power-system communication protocols, including relevant IEC 61850 security considerations.

However, cybersecurity capabilities vary between devices and firmware versions.

Do not assume that an SEL relay supports every IEC 62351 security feature. Verify the specific device documentation and security advisories.

17. Common IEC 61850 engineering mistakes in SEL relays

The following problems are frequently encountered during IEC 61850 engineering and commissioning.

1. Using the wrong ICD file

An ICD file that does not match the relay model or firmware can lead to incorrect communication configuration.

2. Confusing MMS with GOOSE

MMS is commonly used for client-server communication and reporting.

GOOSE is used for fast publisher-subscriber event communication.

They serve different purposes.

3. Assuming all SEL relays support Sampled Values

Sampled Values support is model- and hardware-dependent.

Check the exact relay specifications before designing a process-bus application.

4. Incorrect GOOSE multicast configuration

An incorrect multicast MAC address, APPID or VLAN configuration can prevent the subscriber from receiving the intended message.

5. Incorrect dataset mapping

The publisher and subscriber must agree on the intended data structure and mapping.

6. Ignoring communication quality

A GOOSE signal should not be considered valid merely because a packet is visible on the network.

The subscriber must evaluate the relevant quality, state and supervision information.

7. Incorrect PTP configuration

Different PTP profiles and grandmaster configurations can create synchronization problems.

8. Inadequate network design

GOOSE and SV traffic require suitable Ethernet network engineering.

Bandwidth, multicast management, VLANs, redundancy and network recovery must be considered.

9. Failing to test communication loss

A complete test plan must include the behavior of the protection and control logic when communication becomes unavailable.

10. Confusing Architect and QuickSet

Architect is primarily used for IEC 61850 communication engineering.

QuickSet is primarily used for protection settings and programmable logic.

Both may be required in an SEL project.

18. SEL IEC 61850 training: Practical engineering topics

Engineers who work with SEL relays should understand both the IEC 61850 standard and the manufacturer’s implementation.

A practical training programme should include:

  • Introduction to IEC 61850 architecture.
  • MMS communication.
  • GOOSE publisher and subscriber configuration.
  • Logical devices and logical nodes.
  • Datasets and report control blocks.
  • ICD, IID, SCD and CID files.
  • acSELerator Architect.
  • acSELerator QuickSet.
  • GOOSE testing and troubleshooting.
  • Wireshark packet analysis.
  • Sampled Values and merging units.
  • PRP and HSR network redundancy.
  • PTP time synchronization.
  • IEC 61850 testing and commissioning.
  • Integration of SEL relays with SCADA and station automation systems.

At Elec-Engg, practical training is available for engineers working with power system protection, SEL relays and substation automation.

Online training can be arranged according to the required subjects and participants’ experience. Customized training is also available for companies and engineering teams.

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

For training information, contact Dr. Saeed Roostaee / Elec-Engg.

19. Frequently asked questions about IEC 61850 in SEL relays

What is IEC 61850 in SEL relays?

IEC 61850 is a standardized communication and data-model framework that allows compatible SEL relays to exchange protection, control, measurement and status information with other IEDs and substation systems.

Which SEL software is used for IEC 61850 configuration?

SEL acSELerator Architect SEL-5032 is used for IEC 61850 system configuration and documentation. acSELerator QuickSet SEL-5030 is used for relay protection settings and programmable logic.

What is the difference between MMS and GOOSE in SEL relays?

MMS is commonly used for client-server communication, reporting and supervisory monitoring. GOOSE provides fast publisher-subscriber communication for protection and control signals.

Can SEL relays communicate using GOOSE?

Yes, a number of SEL protection and automation relays support GOOSE. Availability depends on the model, firmware and installed communication option.

Can SEL relays use Sampled Values?

Yes, selected SEL devices support Sampled Values for process-bus applications. Check the specific relay and merging-unit documentation before designing the system.

What is an ICD file in an SEL relay project?

An ICD file describes the IEC 61850 communication capabilities of an IED, including its supported logical devices, logical nodes and communication services.

What is the difference between ICD and CID?

ICD describes the IED’s capabilities. CID contains the configured communication description intended for a particular IED.

What is the purpose of acSELerator Architect?

Architect is SEL’s IEC 61850 engineering tool. It supports SCL-based configuration and documentation of MMS, GOOSE and Sampled Values communication.

Can GOOSE replace hardwired signals?

GOOSE can replace many conventional hardwired signals in appropriately engineered applications. However, the protection design must consider communication availability, supervision, testing, cybersecurity and applicable requirements.

Does every SEL relay support IEC 61850 Edition 2.1?

No. IEC 61850 edition and service support depend on the individual relay model, firmware and ordered communication options.

Can Wireshark be used to troubleshoot SEL IEC 61850 communication?

Yes. Wireshark can inspect GOOSE, Sampled Values, PTP and MMS-related Ethernet traffic and help identify network communication problems.

Is IEC 61850 only used for SCADA communication?

No. IEC 61850 supports station-bus and process-bus applications, including SCADA reporting, protection interlocking, breaker control, GOOSE messaging and Sampled Values.

20. Official SEL references and technical documentation

For further technical information, consult the official SEL product pages and documentation.

  1. SEL-5032 acSELerator Architect Software – IEC 61850 engineering and SCL configuration.
  2. SEL-5032 Software Support and Downloads – Architect software and ICD packages.
  3. SEL Digital Secondary Systems – Digital substation and process-bus solutions.
  4. SEL Sampled Values Process Bus Solutions – Merging units, SV and process-bus communication.
  5. SEL-751 Feeder Protection Relay – Feeder protection and IEC 61850 capabilities.
  6. SEL-451 Protection and Bay Control System – Bay control and IEC 61850 integration.
  7. SEL-787-2/-3/-4 Transformer Protection Relay – Product manuals and IEC 61850 conformance documents.

Final engineering recommendation: Before starting an IEC 61850 project, obtain the correct relay manual, ICD file, PICS/MICS, PIXIT and firmware-specific documentation. Verify the supported communication services and test the complete protection application, not just Ethernet connectivity.


Leave a Comment

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

Scroll to Top