- Introduction
- 1. Understanding the IEC 61850 Testing Structure
- 2. IEC 61850 Testing Tools for MiCOM Relays
- 3. Physical and Ethernet Communication Testing
- 4. MMS Communication Testing
- 5. GOOSE Communication Testing
- 6. Sampled Values Testing
- 7. Testing IEC 61850 Logical Nodes and Data Objects
- 8. Testing Reports and Datasets
- 9. Testing Control Services
- 10. SCL File Validation and Configuration Testing
- 11. Wireshark Filters for IEC 61850 Troubleshooting
- 12. Common IEC 61850 Problems in MiCOM Relays
- Problem 1 – Ping is successful but MMS communication fails
- Problem 2 – GOOSE messages are visible but the subscriber does not operate
- Problem 3 – SCADA receives measurements but not events
- Problem 4 – Incorrect IEC 61850 point mapping
- Problem 5 – Communication interruptions
- Problem 6 – Incorrect timestamps
- 13. Practical Testing Example: MiCOM Feeder Relay and SCADA
- 14. Practical Testing Example: MiCOM GOOSE Interlocking
- 15. Testing Communication Redundancy
- 16. IEC 61850 Commissioning Checklist for MiCOM Relays
- 17. Recommended Troubleshooting Workflow
- 18. Conclusion
- Practical MiCOM and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Introduction
IEC 61850 communication testing is an essential part of protection relay commissioning, substation automation engineering and maintenance.
Modern MiCOM protection relays can communicate with SCADA systems, other protection devices, bay controllers and engineering workstations through IEC 61850 communication services.
However, establishing an Ethernet connection does not necessarily mean that the complete IEC 61850 application is operating correctly.
Engineers must verify the communication architecture, data models, reports, GOOSE messages, control operations, configuration files and protection signal interfaces.
Depending on the exact relay model and implementation, testing may involve:
- MMS client-server communication.
- GOOSE publishing and subscription.
- Sampled Values, where supported.
- Logical nodes and data objects.
- Reporting and datasets.
- Control services.
- SCL configuration.
- Ethernet network communication.
- Time synchronization.
- Communication failure and recovery.
This article provides a practical approach to testing and troubleshooting IEC 61850 in MiCOM protection systems.
Important: IEC 61850 capabilities differ between MiCOM models, hardware versions and firmware releases. MMS or GOOSE support does not automatically imply Sampled Values, PRP or HSR support. Always verify the exact device documentation before preparing a test procedure.
1. Understanding the IEC 61850 Testing Structure
IEC 61850 testing should be divided into different engineering levels.
A communication test at one level does not prove that all other levels are correct.
For example, successfully pinging a MiCOM relay does not prove that MMS reporting or GOOSE protection communication is working.
A complete testing structure includes:
| Testing level | Main objective |
|---|---|
| Physical layer | Verify Ethernet connections and link status |
| Network layer | Verify IP addressing and routing, where applicable |
| Communication services | Test MMS, GOOSE and SV, where supported |
| Data model | Verify logical nodes and data objects |
| Configuration | Check SCL files and communication parameters |
| Application | Verify protection and control signal behavior |
| System integration | Confirm SCADA and IED interoperability |
| Failure testing | Verify alarms, supervision and recovery |
2. IEC 61850 Testing Tools for MiCOM Relays
Several tools may be required during IEC 61850 testing.
The exact tools depend on the MiCOM relay family and the communication services being tested.
2.1 MiCOM S1 Agile
S1 Agile is an engineering environment used with supported MiCOM devices.
Depending on the relay and software version, it can be used for tasks such as:
- Relay configuration.
- Parameter setting.
- Device communication.
- Configuration management.
- Reading device information.
- Accessing supported communication settings.
Do not assume that every S1 Agile version supports every IEC 61850 engineering function or complete substation SCL engineering.
2.2 Wireshark
Wireshark is a packet analysis tool used to inspect Ethernet communication.
It is particularly useful for investigating:
- GOOSE messages.
- MMS communication.
- Sampled Values.
- VLAN tags.
- Multicast traffic.
- TCP connections.
- Communication interruptions.
2.3 IEC 61850 System Configuration Tools
System configuration tools are used to engineer the substation communication architecture and manage SCL files.
Depending on the project, they may be used to:
- Import ICD files.
- Create an SCD file.
- Configure datasets.
- Define GOOSE control blocks.
- Map external references.
- Configure communication parameters.
- Validate system configuration.
The system configuration tool and the relay engineering software may have different responsibilities.
2.4 Protection Testing Equipment
Protection testing equipment, such as suitable Omicron CMC configurations and Test Universe applications, can be used to verify protection functions and associated signal interfaces.
For process bus testing, the equipment must support the required digital communication workflow and device profile.
3. Physical and Ethernet Communication Testing
Before testing IEC 61850 services, verify the physical communication infrastructure.
Step 1 – Check Ethernet connections
Inspect:
- Ethernet cable connections.
- RJ45 or fibre-optic interfaces.
- Switch ports.
- Link indicators.
- Fibre transmit and receive connections.
- Communication module status.
Step 2 – Verify IP configuration
Check the relay’s configured:
- IP address.
- Subnet mask.
- Default gateway, where required.
- Ethernet interface.
- VLAN configuration, where applicable.
Example:
| Parameter | Illustrative value |
|---|---|
| Relay IP | 192.168.10.21 |
| Subnet mask | 255.255.255.0 |
| Gateway | 192.168.10.1 |
| Engineering PC | 192.168.10.100 |
These are example values only.
Step 3 – Test basic connectivity
From the engineering workstation, use:
ping 192.168.10.21
A successful response confirms basic IP reachability under the tested conditions.
However, it does not prove that IEC 61850 communication services are configured correctly.
Step 4 – Check the switch
Verify:
- Port status.
- VLAN membership.
- MAC address learning.
- Multicast forwarding.
- Port errors.
- Network loading.
- Link speed and duplex settings.
4. MMS Communication Testing
MMS is used for client-server communication between IEC 61850 clients and IED servers.
A SCADA system, gateway or engineering application may act as an MMS client, while the MiCOM relay acts as an MMS server.
4.1 Verify TCP communication
MMS commonly operates over TCP port 102.
A useful Wireshark filter is:
tcp.port == 102
Check:
- TCP connection establishment.
- Connection resets.
- Retransmissions.
- Communication interruptions.
- MMS association attempts.
4.2 Verify MMS association
The client must establish an association with the relay.
Check whether:
- The relay accepts the connection.
- The client can establish the required association.
- The server exposes the expected data model.
- Communication remains stable.
An open TCP connection alone does not prove successful MMS association.
4.3 Verify data-model access
Test access to selected logical devices, logical nodes and data objects.
For example, depending on the relay’s implemented data model, you may need to read:
- Protection operation indications.
- Phase current measurements.
- Voltage measurements.
- Circuit-breaker status.
- Relay health information.
- Alarms and events.
The actual references must be obtained from the device’s supported data model.
4.4 Verify reporting
Test the configured report control blocks.
Important parameters include:
- Report control block reference.
- Dataset reference.
- Buffered or unbuffered reporting.
- Trigger options.
- Integrity period.
- General interrogation behavior.
- Client association and report reception.
4.5 Test MMS controls
Where supported and configured, test the required control services.
Possible control models include:
- Direct control.
- Select Before Operate (SBO).
- Enhanced security control models.
Check the exact model supported by the relay and the project control philosophy.
Control testing must be performed under an approved procedure with the breaker or test interface in a safe condition.
5. GOOSE Communication Testing
GOOSE is used for fast event-driven communication between IEDs.
Typical applications include:
- Interlocking.
- Protection blocking.
- Trip signals.
- Breaker failure initiation.
- Circuit-breaker status.
- Transfer trip.
- Other protection and control signals.
5.1 Verify the GOOSE publisher
Check:
- IED name.
- gocbRef.
- Dataset reference.
- APPID.
- Multicast MAC address.
- VLAN ID.
- VLAN priority.
- confRev.
- Dataset values.
5.2 Verify the GOOSE subscriber
Check:
- Publisher reference.
- External references.
- Dataset mapping.
- Input signal assignment.
- Subscription status.
- Communication supervision.
5.3 Monitor GOOSE messages
Use Wireshark:
goose
Or filter using the GOOSE EtherType:
eth.type == 0x88b8
5.4 Understand stNum and sqNum
Two important GOOSE fields are:
stNum: changes when the state of the published dataset changes.sqNum: advances as retransmissions of the current state are sent.
When a dataset value changes, engineers should observe the expected state transition and subsequent retransmission behavior.
5.5 Test the complete signal path
For example, if a feeder relay publishes a trip signal to another IED:
- Initiate the test condition.
- Verify the publisher dataset changes.
- Observe the GOOSE message.
- Verify subscriber reception.
- Check the mapped binary input or internal signal.
- Verify the intended application response.
- Restore the initial condition.
A GOOSE packet visible in Wireshark does not prove that the subscriber has correctly processed the signal.
6. Sampled Values Testing
Sampled Values testing is relevant only when the MiCOM relay and associated equipment support the required SV implementation.
An IEC 61850-enabled relay does not necessarily support SV reception.
For a process bus application, the following items should be verified:
- Merging Unit compatibility.
- SV stream identification.
- APPID.
- Dataset.
- Sampling profile.
- Sample counter.
- Multicast address.
- VLAN configuration.
- Synchronization.
- Measurement scaling.
Useful Wireshark filter
sv
Sample counter testing
The sample counter helps engineers identify sequence behavior.
Investigate:
- Missing samples.
- Repeated samples.
- Unexpected counter changes.
- Communication interruptions.
- Synchronization problems.
Measurement verification
Compare the values received by the protection IED against the expected test values.
Verify:
- Current magnitude.
- Voltage magnitude.
- Phase sequence.
- Polarity.
- Scaling.
- Measurement quality.
Do not rely exclusively on packet capture. Confirm the actual measurement values processed by the protection device.
7. Testing IEC 61850 Logical Nodes and Data Objects
The IEC 61850 data model organizes information using logical devices, logical nodes, data objects and data attributes.
Testing must confirm that the required data references are correctly implemented.
Common logical node examples include:
| Logical node | Typical purpose |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIF | Differential protection |
| PDIS | Distance protection |
| PTRC | Protection trip conditioning |
| XCBR | Circuit-breaker information |
| XSWI | Switch or disconnector information |
| CSWI | Switch control |
| MMXU | Measurement information |
| GGIO | Generic input/output information |
| LPHD | Physical device information |
| LLN0 | Logical device common functions |
The presence of a logical node in the IEC 61850 standard does not mean that every MiCOM relay implements it.
Practical data-model test
For each required point:
- Identify the logical device.
- Identify the logical node.
- Identify the data object.
- Identify the functional constraint.
- Check the data attribute.
- Read the value through the client.
- Compare it with the actual relay condition.
- Verify quality and timestamp information where applicable.
For example, a circuit-breaker position indication may be represented using an XCBR logical node, but the exact reference depends on the relay’s implemented data model.
8. Testing Reports and Datasets
Reports are important for transferring information from protection relays to SCADA systems.
A report can contain selected data objects and attributes from an IEC 61850 dataset.
Main report types
URCB – Unbuffered Report Control Block
Unbuffered reporting is generally intended for connected clients and does not provide the same persistent event buffering behavior as buffered reporting.
BRCB – Buffered Report Control Block
Buffered reporting can retain report information during certain client communication interruptions, subject to the implementation and buffer capacity.
Reporting test procedure
- Identify the required dataset.
- Verify the report control block.
- Check the client configuration.
- Establish the required association.
- Enable reporting.
- Change a selected data point.
- Verify report reception.
- Test general interrogation where supported.
- Test communication interruption.
- Verify recovery and buffered event behavior, where applicable.
Common reporting problems
| Problem | Possible cause |
|---|---|
| No reports received | Reporting disabled or incorrect dataset |
| Incorrect data points | Dataset mapping error |
| Reports stop after reconnection | Client or report reservation issue |
| Events are missing | Trigger configuration or buffer limitation |
| Incorrect timestamps | Time synchronization or timestamp mapping |
| Client cannot enable report | Unsupported service or configuration mismatch |
9. Testing Control Services
IEC 61850 supports different control models.
The actual control model depends on the device implementation and engineering configuration.
Direct control
The client sends a control request directly, where permitted.
Select Before Operate
The client first selects the object and then sends the operate request.
The control model may include additional security and command termination behavior.
Practical breaker control test
Under an approved commissioning procedure:
- Verify the circuit-breaker control object.
- Confirm the control model.
- Check the interlocking conditions.
- Verify the client’s access.
- Perform the select operation if required.
- Perform the operate command.
- Verify the breaker response.
- Check the position indication.
- Verify event reporting.
Control testing must never bypass required electrical or mechanical interlocking.
10. SCL File Validation and Configuration Testing
SCL files are important for IEC 61850 system engineering.
The main file types include:
| File | Meaning |
|---|---|
| ICD | IED Capability Description |
| CID | Configured IED Description |
| IID | Instantiated IED Description |
| SCD | Substation Configuration Description |
| SSD | System Specification Description |
Testing should verify that the system configuration matches the actual device configuration.
Important checks
- Correct IED names.
- Correct logical devices.
- Correct logical nodes.
- Correct datasets.
- Correct report control blocks.
- Correct GOOSE control blocks.
- Correct external references.
- Correct multicast addresses.
- Correct APPIDs.
- Correct VLAN parameters.
- Consistent configuration revisions.
A successful XML schema validation does not prove that two devices are interoperable.
The final configuration must also be checked against the manufacturer’s implementation and tested with the actual equipment.
11. Wireshark Filters for IEC 61850 Troubleshooting
Wireshark is one of the most useful tools for investigating communication problems.
The following filters are useful during MiCOM IEC 61850 testing.
| Purpose | Display filter |
|---|---|
| GOOSE traffic | goose |
| GOOSE EtherType | eth.type == 0x88b8 |
| Sampled Values | sv |
| MMS TCP port | tcp.port == 102 |
| VLAN traffic | vlan |
| TCP retransmissions | tcp.analysis.retransmission |
| TCP resets | tcp.flags.reset == 1 |
| ARP traffic | arp |
| ICMP traffic | icmp |
Practical GOOSE analysis
When investigating GOOSE communication, inspect:
- Source MAC address.
- Destination multicast MAC address.
- APPID.
- gocbRef.
- Dataset reference.
- confRev.
- stNum.
- sqNum.
- timeAllowedToLive.
- Dataset values.
Practical MMS analysis
When investigating MMS communication, inspect:
- TCP connection establishment.
- TCP retransmissions.
- Connection resets.
- MMS association requests.
- Association responses.
- Read and write services.
- Reports.
- Control requests and responses.
Practical SV analysis
When investigating Sampled Values, inspect:
- APPID.
- svID.
- Sample counter.
- Multicast destination.
- Dataset.
- VLAN tagging.
- Synchronization-related information.
Capture location and network topology are important. A capture on one interface may not show all traffic transmitted across redundant networks.
12. Common IEC 61850 Problems in MiCOM Relays
Problem 1 – Ping is successful but MMS communication fails
Possible causes:
- Incorrect client configuration.
- Unsupported MMS service.
- Association configuration issue.
- Incorrect application settings.
- Firewall or network filtering.
Recommended checks:
- Confirm TCP port 102 communication.
- Inspect MMS association attempts.
- Check client and relay configuration.
- Verify supported services.
Problem 2 – GOOSE messages are visible but the subscriber does not operate
Possible causes:
- Incorrect GOOSE subscription.
- Wrong external reference.
- Dataset mismatch.
- Incorrect input mapping.
- confRev mismatch.
- VLAN or multicast configuration problem.
Recommended checks:
- Compare publisher and subscriber configuration.
- Verify the correct dataset.
- Check the subscriber diagnostic status.
- Confirm internal signal mapping.
- Test the complete application.
Problem 3 – SCADA receives measurements but not events
Possible causes:
- Incorrect dataset.
- Report control block not enabled.
- Incorrect trigger options.
- Client configuration mismatch.
- Reporting or buffering limitations.
Recommended checks:
- Verify the report dataset.
- Check report control block configuration.
- Confirm client association.
- Test data changes and event reporting.
Problem 4 – Incorrect IEC 61850 point mapping
Possible causes:
- Incorrect logical node reference.
- Wrong data object.
- Incorrect functional constraint.
- Different data model between firmware versions.
- Engineering configuration mismatch.
Recommended checks:
- Compare the relay’s actual data model.
- Verify SCL configuration.
- Read the data point directly.
- Compare it with the physical relay condition.
Problem 5 – Communication interruptions
Possible causes:
- Switch or cable problems.
- Multicast flooding.
- Incorrect VLAN configuration.
- Network congestion.
- Power supply problems.
- Redundancy configuration errors.
Recommended checks:
- Check switch diagnostics.
- Analyze packet captures.
- Verify network loading.
- Inspect cable and fibre connections.
- Test redundant paths individually.
Problem 6 – Incorrect timestamps
Possible causes:
- Time synchronization failure.
- Incorrect time source.
- Time-zone interpretation.
- Incorrect timestamp mapping.
- Device configuration differences.
Recommended checks:
- Verify the configured time source.
- Check synchronization status.
- Compare device and SCADA timestamps.
- Verify UTC handling and display configuration.
13. Practical Testing Example: MiCOM Feeder Relay and SCADA
Consider a feeder protection relay connected to a station SCADA system through IEC 61850 MMS.
The objective is to verify the communication and point mapping.
Step 1 – Establish network communication
Check the relay IP address and verify network connectivity.
Step 2 – Establish MMS association
Connect the SCADA client and verify successful association.
Step 3 – Read measurements
Read selected current and voltage measurements.
Compare them with the relay display or an approved test source.
Step 4 – Test protection indications
Simulate a protection operation under an approved test procedure.
Verify the corresponding IEC 61850 data point.
Step 5 – Test reporting
Verify that the relevant report is transmitted to SCADA when the data changes.
Step 6 – Test breaker indications
Operate the breaker status test interface or use an approved simulation method.
Confirm that the SCADA point changes correctly.
Step 7 – Test controls
Where enabled, test the approved remote control procedure.
Verify interlocking, command response and feedback.
Step 8 – Record results
Document:
- Relay model and firmware.
- IP address.
- Tested logical node references.
- Report configuration.
- Control model.
- Communication status.
- Test results.
- Outstanding issues.
14. Practical Testing Example: MiCOM GOOSE Interlocking
Consider two feeder relays exchanging interlocking signals.
The objective is to prevent an operation when the required interlocking condition is not satisfied.
Step 1 – Identify the signal
Define the interlocking signal and its intended function.
Step 2 – Configure the publisher
Configure the required GOOSE dataset and control block.
Step 3 – Configure the subscriber
Map the incoming GOOSE signal to the correct internal input.
Step 4 – Verify communication
Use Wireshark to confirm that the expected GOOSE message is transmitted.
Step 5 – Verify the signal
Change the publisher signal and confirm that the subscriber receives the correct value.
Step 6 – Verify the interlocking application
Test the complete logic under controlled conditions.
Step 7 – Test communication failure
Interrupt the communication using an approved procedure.
Verify the configured supervision alarm and the intended fail-safe behavior.
The expected response must be defined by the protection and interlocking philosophy. It should not be assumed that every communication failure must produce the same blocking or permissive response.
15. Testing Communication Redundancy
Where the MiCOM relay and network architecture support PRP or HSR, redundancy testing should be included in commissioning.
PRP testing
- Verify LAN A.
- Verify LAN B.
- Confirm normal communication.
- Simulate LAN A failure.
- Verify communication through LAN B.
- Restore LAN A.
- Repeat for LAN B.
HSR testing
- Verify the ring topology.
- Check normal communication.
- Simulate a single ring-link failure.
- Verify communication through the remaining path.
- Restore the connection.
- Confirm normal ring operation.
The test should verify GOOSE and MMS behavior, and SV behavior where supported.
PRP or HSR should not be assumed to preserve every application-level session under all possible failure conditions.
16. IEC 61850 Commissioning Checklist for MiCOM Relays
General configuration
- Confirm relay model and firmware.
- Check IEC 61850 capability.
- Verify IP configuration.
- Check Ethernet connectivity.
- Review SCL files.
- Confirm logical node references.
- Save configuration backups.
MMS
- Verify TCP communication.
- Confirm MMS association.
- Read selected data points.
- Verify measurement scaling.
- Test reports.
- Test general interrogation where supported.
- Test controls where enabled.
GOOSE
- Verify publisher configuration.
- Verify subscriber configuration.
- Check dataset.
- Confirm APPID and multicast address.
- Check VLAN configuration.
- Verify stNum and sqNum behavior.
- Test signal mapping.
- Test communication supervision.
Sampled Values, where supported
- Verify SV capability.
- Confirm sampling profile.
- Check APPID and svID.
- Verify sample counter.
- Check measurement scaling.
- Confirm synchronization.
- Test loss-of-SV response.
Network and redundancy
- Check switch configuration.
- Verify VLANs.
- Check multicast forwarding.
- Test network redundancy where applicable.
- Verify communication recovery.
- Save network configuration.
Documentation
- Record test results.
- Save packet captures where required.
- Record device firmware.
- Save final SCL files.
- Document outstanding issues.
- Prepare commissioning report.
17. Recommended Troubleshooting Workflow
When an IEC 61850 problem occurs, engineers should follow a structured approach instead of changing multiple settings simultaneously.
A practical troubleshooting sequence is:
- Identify the affected communication service.
- Confirm the relay model and supported capability.
- Check physical Ethernet connections.
- Verify IP and VLAN configuration.
- Capture network traffic.
- Inspect the relevant MMS, GOOSE or SV messages.
- Compare device and SCL configuration.
- Verify data-model references.
- Check application signal mapping.
- Test the complete protection or control function.
- Record the root cause and corrective action.
Avoid changing relay settings, SCL configuration and switch parameters simultaneously. Make controlled changes and repeat the relevant tests after each modification.
18. Conclusion
IEC 61850 testing in MiCOM protection relays requires a systematic approach that covers communication, configuration and application behavior.
MMS testing verifies client-server communication, data access, reporting and controls. GOOSE testing verifies fast event and status communication between IEDs. Sampled Values testing verifies digital measurement transmission where the installed equipment supports it.
Wireshark, S1 Agile, system configuration tools and suitable protection test equipment can help engineers identify communication problems and verify the complete protection application.
The most important commissioning principle is that communication must be tested end to end. A successful ping, an open TCP connection or a visible GOOSE packet is not sufficient proof of correct protection operation.
A reliable IEC 61850 installation requires correct device compatibility, accurate SCL engineering, proper network configuration, verified signal mapping and documented failure testing.
Practical MiCOM and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training subjects include:
- MiCOM relay configuration and testing.
- IEC 61850 MMS communication.
- GOOSE publisher and subscriber engineering.
- Sampled Values and process bus fundamentals.
- SCL configuration and system integration.
- Wireshark packet analysis.
- SCADA integration and reporting.
- Ethernet network troubleshooting.
- Omicron CMC and Test Universe applications.
- Protection testing and commissioning.
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Visit Elec-Engg for practical power system protection and substation automation training.
