- 1. Introduction
- 2. Understanding the MiCOM IEC 61850 Communication Architecture
- 3. First-Level Ethernet Troubleshooting
- 4. Troubleshooting MMS Communication
- 5. Troubleshooting IEC 61850 GOOSE Communication
- 6. Common GOOSE Communication Problems
- 7. Wireshark for MiCOM IEC 61850 Troubleshooting
- 8. VLAN and Multicast Troubleshooting
- 9. IEC 61850 Redundancy Troubleshooting
- 10. Troubleshooting Time Synchronization
- 11. SCL Configuration Problems
- 12. Practical Troubleshooting Example: MiCOM Relay and SICAM PAS
- 13. Common MiCOM IEC 61850 Troubleshooting Cases
- 14. Advanced Network Diagnostics
- 15. Practical Commissioning Procedure
- 16. Practical Troubleshooting Checklist
- 17. Conclusion
- 18. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
Reliable communication is essential for modern substation automation systems. MiCOM protection relays use communication interfaces to exchange information with station controllers, SCADA systems, engineering workstations and other intelligent electronic devices (IEDs).
IEC 61850 provides standardized communication services, including MMS and GOOSE, but successful implementation depends on correct relay configuration, Ethernet network design, communication settings and system integration.
During commissioning and operation, engineers may encounter problems such as:
- MiCOM relay not accessible through Ethernet.
- MMS association failure.
- Missing SCADA indications.
- GOOSE messages not received by subscribers.
- Incorrect dataset configuration.
- Communication interruptions.
- Incorrect IED names or references.
- VLAN and multicast problems.
- Incorrect network redundancy configuration.
- Time synchronization problems.
- Unexpected communication delays.
This article provides a practical troubleshooting approach for MiCOM IEC 61850 systems, including Ethernet diagnostics, MMS analysis, GOOSE monitoring, Wireshark and commissioning procedures.
Important: Communication capabilities differ between MiCOM models, order codes, communication hardware and firmware versions. Verify the exact implementation using the relevant technical manuals, MICS, PICS, PIXIT, ICD files and release notes.
2. Understanding the MiCOM IEC 61850 Communication Architecture
A typical IEC 61850 substation network includes protection relays, bay controllers, station controllers, SCADA servers and engineering workstations.
A MiCOM relay may communicate with other devices through several services.
| Communication service | Main application |
|---|---|
| MMS | SCADA monitoring and control |
| GOOSE | Fast peer-to-peer communication |
| Sampled Values | Process bus measurement exchange, where supported |
| SNTP | Time synchronization |
| PTP | Precision time synchronization, where supported |
| File services | Access to supported device files |
The most common troubleshooting tasks involve MMS and GOOSE.
2.1 MMS communication
MMS is used for client-server communication.
Typical applications include:
- Reading relay measurements.
- Monitoring protection indications.
- Receiving reports.
- Accessing the IEC 61850 data model.
- Sending supported control commands.
MMS commonly operates over TCP port 102.
2.2 GOOSE communication
GOOSE is used for fast peer-to-peer communication between IEDs.
Typical applications include:
- Breaker interlocking.
- Protection trip signals.
- Breaker failure initiation.
- Busbar protection signals.
- Transfer trip applications.
- Blocking and permissive signals.
GOOSE uses Ethernet multicast and EtherType 0x88B8. It does not use TCP/IP.
This distinction is important because MMS and GOOSE require different troubleshooting methods.
3. First-Level Ethernet Troubleshooting
Before investigating IEC 61850 application services, engineers should confirm that the physical and network layers are operating correctly.
3.1 Check physical Ethernet connectivity
Inspect:
- Ethernet cable connections.
- Switch port status.
- Relay communication port LEDs.
- Switch power supply.
- Fiber-optic connections, where applicable.
- SFP compatibility.
- Link speed and duplex settings.
- Port errors and packet counters.
A physical link problem can prevent all higher-level communication services from operating.
3.2 Check IP configuration
For MMS communication, verify the following parameters:
- Relay IP address.
- Subnet mask.
- Default gateway, if required.
- Station controller IP address.
- VLAN assignment.
- Routing configuration, where applicable.
Example network:
| Device | IP address |
|---|---|
| MiCOM Feeder 1 | 192.168.10.11 |
| MiCOM Feeder 2 | 192.168.10.12 |
| SICAM PAS | 192.168.10.100 |
| Engineering PC | 192.168.10.200 |
These addresses are illustrative only.
3.3 Ping test
A ping test can help determine whether two devices have basic IP connectivity.
Example Windows command:
ping 192.168.10.11
If the relay responds, basic IP connectivity exists between the test computer and relay.
However, a successful ping does not prove that MMS or GOOSE is working.
Likewise, a failed ping does not always prove that the relay is unreachable. ICMP may be blocked by network policy or device configuration.
3.4 Check ARP resolution
The Address Resolution Protocol maps an IPv4 address to a MAC address on a local network.
Example:
arp -a
Engineers can use this command to inspect whether the relay’s IP address is associated with the expected MAC address.
Unexpected or changing MAC addresses may indicate duplicate IP addressing, incorrect network connections or other network problems.
4. Troubleshooting MMS Communication
MMS is commonly used for communication between a MiCOM relay and a station controller.
A basic troubleshooting sequence should start with the TCP connection and continue to the MMS association and application services.
4.1 Check TCP port 102
MMS commonly uses TCP port 102.
In Windows PowerShell:
Test-NetConnection 192.168.10.11 -Port 102
A successful test indicates that the TCP connection can be established to the specified port.
It does not prove that the MMS association or IEC 61850 data exchange will work.
4.2 Check MMS association
If TCP connectivity is available but the SCADA client cannot communicate with the relay, investigate:
- Client configuration.
- Server configuration.
- IED identification.
- Access restrictions.
- Supported MMS services.
- IEC 61850 edition compatibility.
- Relay communication settings.
- Client association handling.
4.3 Check data model access
After establishing an association, the SCADA client should be able to access the supported data model.
Check:
- Logical device names.
- Logical node names.
- Data object references.
- Data attribute references.
- Functional constraints.
- Data types.
- Access permissions.
A common engineering error is using an incorrect object reference based on another relay model or a generic IEC 61850 example.
The actual MiCOM data model must be checked.
4.4 Common MMS problems
| Problem | Possible cause |
|---|---|
| TCP connection fails | Incorrect IP, blocked port or unavailable service |
| MMS association rejected | Client/server configuration mismatch |
| Data model browsing fails | Unsupported service or incorrect client configuration |
| Some data points are missing | Objects not implemented or not enabled |
| Reports are not received | Dataset or RCB configuration issue |
| Control commands are rejected | Control model or authority problem |
| Communication stops intermittently | Network interruption or association management problem |
5. Troubleshooting IEC 61850 GOOSE Communication
GOOSE communication requires particular attention because it is Ethernet multicast traffic.
A GOOSE publisher transmits information, and one or more subscribers receive and process it.
5.1 GOOSE publisher
The publisher is the IED that transmits a GOOSE message.
It normally uses a configured GOOSE Control Block and dataset.
The transmitted information may include:
- Protection trip status.
- Breaker position.
- Interlocking signals.
- Blocking signals.
- Permissive signals.
5.2 GOOSE subscriber
The subscriber receives GOOSE messages and uses selected data attributes within its configured application.
A subscriber must be correctly configured to receive and interpret the intended publisher’s information.
5.3 Important GOOSE parameters
When troubleshooting, examine:
| Parameter | Purpose |
|---|---|
| Destination MAC address | Identifies the multicast destination |
| APPID | Identifies the GOOSE application association |
| VLAN ID | Identifies the configured VLAN |
| VLAN priority | Provides traffic priority information |
| Dataset | Defines transmitted data |
| GoCB reference | Identifies the GOOSE Control Block |
ConfRev | Configuration revision |
stNum | State number |
sqNum | Sequence number |
timeAllowedToLive | Supervision interval information |
5.4 Understanding stNum and sqNum
These two parameters are especially useful during troubleshooting.
stNum – State number
The state number changes when the GOOSE dataset state changes.
For example, when a protection trip signal changes from FALSE to TRUE, the publisher transmits a new state.
sqNum – Sequence number
The sequence number advances as the publisher retransmits messages associated with the current state.
GOOSE messages are retransmitted according to the publisher’s retransmission strategy.
timeAllowedToLive
This parameter indicates the maximum expected time before the next message should arrive under the current transmission behavior.
Subscribers use it to supervise communication freshness.
5.5 Understanding ConfRev
ConfRev identifies the configuration revision associated with the GOOSE Control Block and dataset configuration.
It is not the relay firmware revision.
If the publisher’s dataset configuration changes, the associated configuration revision may also change.
The publisher and subscriber configuration must remain consistent.
6. Common GOOSE Communication Problems
6.1 Subscriber does not receive GOOSE messages
Possible causes include:
- Incorrect destination MAC address.
- Incorrect APPID.
- VLAN mismatch.
- Incorrect publisher configuration.
- Incorrect subscriber configuration.
- Multicast filtering.
- Switch configuration problem.
- Incorrect network port connection.
6.2 GOOSE messages are visible in Wireshark but the subscriber does not operate
Possible causes include:
- Incorrect dataset mapping.
- Incorrect external reference.
- Incompatible data type.
- Incorrect configuration revision.
- Subscriber configuration mismatch.
- Signal quality or test-mode handling.
- Application logic not configured correctly.
Seeing a GOOSE packet in Wireshark does not prove that the subscriber has accepted the information.
6.3 GOOSE communication supervision alarm
A subscriber may indicate a communication problem if expected GOOSE messages are not received within the configured supervision interval.
Investigate:
- Publisher status.
- Ethernet network.
- VLAN configuration.
- Multicast delivery.
- GOOSE transmission behavior.
- Subscriber configuration.
- Network interruption.
6.4 GOOSE message is received but signal remains incorrect
Check:
- Dataset member order.
- Data attribute references.
- Signal polarity.
- Data types.
- Subscriber mapping.
- Application logic.
- Quality and test information.
Incorrect dataset engineering can result in a valid Ethernet packet carrying information that is interpreted incorrectly by the receiving application.
7. Wireshark for MiCOM IEC 61850 Troubleshooting
Wireshark is one of the most useful tools for analyzing IEC 61850 communication.
It allows engineers to inspect network packets and investigate communication problems.
7.1 Capturing network traffic
A practical procedure is:
- Install Wireshark on an engineering workstation.
- Connect the workstation to the relevant network.
- Select the correct network interface.
- Start packet capture.
- Generate the required communication activity.
- Apply suitable display filters.
- Inspect the decoded packets.
For switched Ethernet networks, the monitoring workstation may need a configured switch mirror port (SPAN) to observe traffic between other devices.
Without appropriate traffic visibility, a capture may show only packets addressed to the workstation.
7.2 Useful Wireshark filters
| Display filter | Purpose |
|---|---|
goose | Display decoded GOOSE packets |
eth.type == 0x88b8 | Display GOOSE EtherType traffic |
tcp.port == 102 | Display MMS-related TCP traffic |
tcp.analysis.retransmission | Identify TCP retransmissions |
tcp.flags.reset == 1 | Identify TCP reset packets |
ip.addr == 192.168.10.11 | Display traffic involving a specific relay |
arp | Display ARP packets |
icmp | Display ICMP traffic |
7.3 Analyze GOOSE packets
When examining a GOOSE packet, check:
- Source MAC address.
- Destination MAC address.
- APPID.
- VLAN information.
- GoCB reference.
- Dataset reference.
- Configuration revision.
- State number.
- Sequence number.
- Time allowed to live.
- Dataset values.
Compare these parameters with the approved engineering configuration.
7.4 Analyze MMS packets
For MMS troubleshooting, check:
- TCP connection establishment.
- Port 102 communication.
- MMS association requests.
- Association responses.
- Data access requests.
- Report transmission.
- Control requests.
- Communication errors.
The Wireshark protocol decoder and packet details available depend on the capture and installed version.
8. VLAN and Multicast Troubleshooting
VLAN configuration is important for organizing IEC 61850 substation networks.
GOOSE traffic may use VLAN tagging and priority settings according to the system design.
8.1 VLAN mismatch
A publisher may transmit GOOSE messages on one VLAN while the subscriber is connected to a different VLAN.
As a result, the subscriber may not receive the expected messages.
Check:
- Switch access port configuration.
- Trunk port configuration.
- VLAN membership.
- VLAN tagging.
- VLAN ID.
- VLAN priority.
8.2 Multicast filtering
GOOSE uses Ethernet multicast.
Switch features such as multicast filtering and traffic-control policies can affect delivery.
Engineers should check:
- Multicast forwarding configuration.
- Port membership.
- Filtering rules.
- Traffic policing.
- Network topology.
IGMP snooping is designed primarily for IP multicast. GOOSE is not IP multicast, so engineers should not assume that ordinary IGMP configuration alone guarantees correct GOOSE forwarding.
8.3 Network load
High network utilization can affect communication performance.
Investigate:
- Port utilization.
- Broadcast and multicast traffic.
- Packet drops.
- Interface errors.
- Switch CPU load.
- Incorrect network loops.
- Unnecessary traffic.
Protection-related communication networks should be engineered according to the required performance and availability specifications.
9. IEC 61850 Redundancy Troubleshooting
Some substation networks use redundancy technologies to improve communication availability.
Common IEC 62439-3 redundancy protocols include:
- PRP – Parallel Redundancy Protocol.
- HSR – High-availability Seamless Redundancy.
Support for PRP or HSR depends on the device, communication hardware and network architecture.
9.1 PRP
PRP uses two independent LANs.
A compatible device sends duplicate frames over both networks.
The receiving device can accept the first valid frame and discard the duplicate.
When correctly implemented, PRP can provide seamless recovery from a single network failure.
9.2 HSR
HSR uses a ring-based architecture in which frames are transmitted in both directions around the ring.
Compatible nodes process duplicate frames according to the protocol.
9.3 Common redundancy problems
| Problem | Possible cause |
|---|---|
| One LAN unavailable | Cable or switch failure |
| Duplicate frame handling problem | Redundancy configuration mismatch |
| Device not communicating | Incompatible redundancy implementation |
| Unexpected packet loss | Network topology or device configuration |
| Communication alarm | Redundancy supervision problem |
Do not assume that a MiCOM relay supports PRP or HSR merely because it has two Ethernet ports. Verify the actual hardware and protocol support.
10. Troubleshooting Time Synchronization
Time synchronization problems can affect event analysis and sequence-of-events accuracy.
Possible synchronization methods include:
- SNTP.
- PTP.
- IRIG-B.
The available methods depend on the relay and system design.
10.1 Common problems
- Incorrect time server address.
- Time server unreachable.
- Incorrect network routing.
- Unsupported synchronization mode.
- Incorrect PTP profile.
- Time source failure.
- Incorrect time zone handling.
- Device clock not synchronized.
10.2 Practical checks
Verify:
- The configured time source.
- Network connectivity to the time server.
- Relay synchronization status.
- Station controller time.
- SCADA timestamp handling.
- Time-quality information.
- Event chronology across devices.
A relay can continue communicating through MMS while its clock is not synchronized. Communication health and time synchronization health must therefore be checked separately.
11. SCL Configuration Problems
SCL files are important in IEC 61850 engineering.
The main file types include:
| File | Full name |
|---|---|
| ICD | IED Capability Description |
| CID | Configured IED Description |
| IID | Instantiated IED Description |
| SCD | Substation Configuration Description |
| SSD | System Specification Description |
11.1 Common SCL problems
- Incorrect IED name.
- Incorrect communication address.
- Incorrect dataset reference.
- Incorrect GOOSE Control Block reference.
- Incorrect external reference.
- Unsupported SCL edition.
- Incompatible schema.
- Incorrect communication configuration.
- Configuration differences between engineering tools.
11.2 Incorrect IED name
IED names are important for system-level references.
If the relay’s configured IED name differs from the name expected by the station engineering configuration, communication and data mapping may fail.
11.3 Incorrect GOOSE subscription
A subscriber’s external reference configuration must correspond to the intended publisher’s information.
Check:
- Publisher IED name.
- Logical device.
- Logical node.
- Data object.
- Data attribute.
- Dataset member.
- Communication parameters.
11.4 SCL compatibility
Not all IEC 61850 engineering tools support identical SCL features or versions.
A file that is syntactically valid XML is not necessarily fully compatible with a particular MiCOM relay or engineering application.
Verify the supported SCL edition and tool interoperability before downloading configurations to a live device.
12. Practical Troubleshooting Example: MiCOM Relay and SICAM PAS
Consider a substation where MiCOM feeder relays communicate with Siemens SICAM PAS.
The operator reports that Feeder 1 measurements are visible, but breaker status and protection alarms are not updating.
A structured investigation is required.
Step 1: Check physical connection
Inspect the relay’s Ethernet link and the relevant switch port.
Confirm that there are no physical link alarms.
Step 2: Check IP connectivity
Ping the relay from the engineering workstation.
Confirm that the configured IP address is correct.
Step 3: Check MMS connection
Test TCP port 102.
Verify that SICAM PAS can establish the MMS association.
Step 4: Browse the data model
Check whether the breaker status and protection indications exist in the actual relay data model.
Step 5: Check point mapping
Compare the SCADA references with the actual logical device, logical node, data object and data attribute references.
Step 6: Check reporting
Verify the datasets and Report Control Blocks.
Check whether the required points are included and whether the appropriate report triggers are configured.
Step 7: Capture network traffic
Use Wireshark to confirm whether the relay is transmitting the expected MMS reports.
Step 8: Compare relay and SCADA information
Check the relay’s local indications and event records against the SCADA database.
This process helps isolate whether the problem is related to the relay, communication network, IEC 61850 configuration or SCADA engineering.
13. Common MiCOM IEC 61850 Troubleshooting Cases
| No. | Problem | Main investigation |
|---|---|---|
| 1 | Relay cannot be pinged | Ethernet and IP configuration |
| 2 | TCP port 102 unavailable | MMS service and network restrictions |
| 3 | MMS association rejected | Client/server configuration |
| 4 | Data model cannot be browsed | Supported services and object references |
| 5 | Measurements missing | Data mapping and reporting |
| 6 | Protection indications not updated | Dataset and report configuration |
| 7 | GOOSE not received | VLAN, multicast and publisher settings |
| 8 | GOOSE received but no operation | Subscriber mapping and application logic |
| 9 | GOOSE supervision alarm | Publisher availability and message timing |
| 10 | Wrong GOOSE signal | Dataset mapping and signal interpretation |
| 11 | SCADA values are stale | Reporting and communication supervision |
| 12 | Incorrect event timestamps | Time synchronization |
| 13 | Remote control rejected | Control model and interlocking |
| 14 | Communication interruption | Switches, cables and network loading |
| 15 | Redundancy failure | PRP/HSR compatibility and configuration |
14. Advanced Network Diagnostics
For larger substation automation systems, basic ping and Wireshark analysis may not be sufficient.
Additional diagnostics may include:
14.1 Switch diagnostics
Check:
- Interface counters.
- CRC errors.
- Dropped frames.
- Port utilization.
- Link transitions.
- Multicast forwarding.
- VLAN membership.
- MAC address tables.
- Redundancy status.
14.2 Network monitoring
Network monitoring tools can help identify:
- Unexpected traffic.
- Network interruptions.
- High utilization.
- Port failures.
- Device availability.
- Configuration changes.
14.3 Comparing publisher and subscriber configurations
For GOOSE applications, compare the publisher and subscriber configurations.
Verify:
- Dataset definition.
- Dataset member order.
- Data types.
- GOOSE Control Block.
- Destination MAC address.
- APPID.
- VLAN settings.
- Configuration revision.
- External references.
14.4 Configuration backups
Before modifying a live protection system:
- Back up relay configurations.
- Save relevant SCL files.
- Record communication settings.
- Document switch configurations.
- Record firmware versions.
- Maintain approved configuration copies.
Configuration changes should follow the project’s management-of-change procedure.
15. Practical Commissioning Procedure
A systematic commissioning process helps prevent communication problems after energization.
Phase 1: Documentation review
- Confirm relay models and firmware.
- Obtain applicable technical manuals.
- Review ICD and SCL files.
- Review network architecture.
- Confirm IP addressing.
- Review SCADA point lists.
- Review GOOSE signal lists.
Phase 2: Physical network checks
- Inspect Ethernet cabling.
- Verify switch ports.
- Check fiber connections.
- Confirm VLAN configuration.
- Verify network redundancy, where applicable.
Phase 3: MMS testing
- Test IP connectivity.
- Test TCP port 102.
- Establish MMS association.
- Browse the data model.
- Read selected values.
- Test reporting.
- Test supported control services.
Phase 4: GOOSE testing
- Identify publishers.
- Identify subscribers.
- Verify datasets.
- Check MAC addresses and APPIDs.
- Verify VLAN settings.
- Capture GOOSE messages.
- Test signal changes.
- Verify subscriber response.
- Check supervision alarms.
Phase 5: Time synchronization
- Verify the time source.
- Check relay synchronization.
- Compare device clocks.
- Verify SCADA timestamps.
- Check event chronology.
Phase 6: Final integration
- Verify SCADA indications.
- Verify measurements.
- Verify quality handling.
- Verify alarms and events.
- Test communication recovery.
- Save approved configuration backups.
- Prepare commissioning reports.
16. Practical Troubleshooting Checklist
Physical and network layer
- Ethernet link is available.
- Correct cable and fiber connections.
- Correct IP configuration.
- No duplicate IP addresses.
- Switch ports are operational.
- VLAN configuration is correct.
- No unexpected packet loss.
MMS
- TCP port 102 is reachable.
- MMS association is successful.
- Correct IED identification.
- Data model browsing works.
- Required values are accessible.
- Reports are received.
- Controls work where supported.
GOOSE
- Publisher configuration verified.
- Subscriber configuration verified.
- Dataset references are correct.
- Destination MAC address is correct.
- APPID is correct.
- VLAN settings are correct.
ConfRevis consistent.- GOOSE messages are visible.
- Subscriber responds correctly.
- Supervision is healthy.
Time and redundancy
- Time synchronization is healthy.
- Event timestamps are correct.
- Network redundancy is verified where applicable.
- Recovery behavior has been tested.
Final documentation
- Relay configuration backed up.
- SCL files archived.
- Network settings documented.
- Test results recorded.
- Approved configuration versions identified.
17. Conclusion
Effective IEC 61850 troubleshooting requires a structured understanding of the communication layers and the functions implemented by the protection relay.
For MiCOM systems, engineers should investigate physical Ethernet connectivity, IP configuration, MMS associations, GOOSE multicast communication, SCL engineering, time synchronization and SCADA integration separately.
The most important troubleshooting principle is to identify exactly where communication or application processing fails rather than changing relay settings without evidence.
Using network diagnostics, Wireshark, engineering documentation and systematic commissioning procedures can significantly reduce troubleshooting time and improve substation automation reliability.
18. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training topics include:
- MiCOM relay configuration and engineering.
- IEC 61850 fundamentals.
- MMS communication and reporting.
- GOOSE configuration and troubleshooting.
- SCL engineering.
- Wireshark packet analysis.
- Ethernet network diagnostics.
- SICAM PAS integration.
- Time synchronization.
- Practical relay testing and commissioning.
Training formats include video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Website: https://elec-engg.com/
