- 1. Introduction
- 2. Understanding the IEC 61850 Engineering Architecture
- 3. Step 1 – Identify the MiCOM Relay and Its IEC 61850 Capabilities
- 4. Step 2 – Prepare the IEC 61850 Engineering Environment
- 5. Step 3 – Obtain and Import the Correct ICD File
- 6. Step 4 – Configure IED Names, Logical Devices and Logical Nodes
- 7. Step 5 – Configure the IEC 61850 Communication Network
- 8. Step 6 – Configure IEC 61850 Datasets
- 9. Step 7 – Configure MMS Reporting
- 10. Step 8 – Configure GOOSE Publishing
- 11. Step 9 – Configure GOOSE Subscription
- 12. Step 10 – Configure GOOSE Network Parameters
- 13. Step 11 – Verify IEC 61850 Communication Using Wireshark
- 14. Step 12 – Test IEC 61850 Functions During Commissioning
- 15. Common IEC 61850 Configuration Problems in MiCOM Relays
- 16. Practical IEC 61850 Engineering Checklist
- 17. Conclusion
- 18. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
Configuring IEC 61850 communication in MiCOM protection relays is an important part of modern substation automation engineering. Protection engineers and commissioning engineers must understand how to configure the relay’s IEC 61850 data model, establish communication with station-level systems, exchange information through GOOSE messages and verify the complete communication chain.
IEC 61850 provides a standardized communication architecture for intelligent electronic devices (IEDs). It allows protection relays, bay control units, SCADA systems and other substation devices to exchange information using standardized data models and communication services.
MiCOM protection relays can support different IEC 61850 functions depending on their model, hardware, communication options and firmware. The engineering procedure is therefore not identical for every MiCOM relay.
This article explains the main engineering stages involved in configuring IEC 61850 communication in supported MiCOM relays, from initial device identification to MMS reporting, GOOSE configuration, testing and commissioning.
The focus is on practical engineering rather than simply describing the IEC 61850 standard.
2. Understanding the IEC 61850 Engineering Architecture
Before configuring a MiCOM relay, it is important to understand the relationship between the protection device, engineering tools, communication network and station-level system.
A typical IEC 61850 substation may include:
- MiCOM feeder protection relays
- MiCOM distance protection relays
- MiCOM transformer protection relays
- Bay control units
- Station-level SCADA or gateway systems
- Engineering workstations
- Ethernet switches
- Time synchronization equipment
The communication architecture commonly involves two important services.
MMS (Manufacturing Message Specification): Used for client-server communication, including data access, reporting and supported control services.
GOOSE (Generic Object Oriented Substation Event): Used for fast event-based communication between IEDs, particularly for interlocking, trip signals and other automation applications.
Typical IEC 61850 architecture
Station-level system
SCADA / SICAM PAS / IEC 61850 gateway
MMS communication
Substation Ethernet network
Managed switches · VLANs · Network redundancy where designed
MMS and GOOSE communication
MiCOM Relay 1
Feeder protection
MiCOM Relay 2
Feeder protection
Conceptual architecture. Actual network topology and services depend on the project and device capabilities.
3. Step 1 – Identify the MiCOM Relay and Its IEC 61850 Capabilities
The first engineering task is to identify the exact relay and confirm its communication capabilities.
Do not start configuration by assuming that all MiCOM relays support the same IEC 61850 services.
Check the following information:
| Parameter | What to verify |
|---|---|
| Relay model | Exact MiCOM model and product variant |
| Hardware | Order code and communication hardware |
| Firmware | Installed firmware version |
| IEC 61850 edition | Edition supported by the relay |
| MMS | Supported client-server services |
| GOOSE | Publishing and subscription capabilities |
| Data model | Available logical devices and logical nodes |
| Reporting | Supported report control block features |
| Controls | Supported control models and operations |
| Time synchronization | Supported synchronization methods |
The relevant technical documents may include:
- Product technical manual
- Communication protocol manual
- IEC 61850 PICS
- IEC 61850 MICS
- IEC 61850 PIXIT
- Applicable ICD file
- Firmware release notes
The PICS describes protocol implementation conformance, the MICS describes the implemented IEC 61850 data model, and the PIXIT provides additional implementation-specific information.
These documents are particularly useful when preparing a project specification or checking whether a required function is supported.
4. Step 2 – Prepare the IEC 61850 Engineering Environment
IEC 61850 engineering can involve more than one software application.
For MiCOM relays, engineers should distinguish between relay-specific engineering and system-level IEC 61850 configuration.
4.1 MiCOM S1 Agile
MiCOM S1 Agile is an engineering environment used for supported MiCOM protection products.
Depending on the relay model and software version, it can be used for activities such as:
- Relay settings configuration
- Device communication
- Programmable scheme configuration
- Disturbance and event retrieval
- Device management
- Supported communication configuration
The exact IEC 61850 functions available in S1 Agile must be checked against the particular relay and software release.
4.2 IEC 61850 System Configuration Tool
A system configuration tool is used to manage the overall substation IEC 61850 configuration.
Depending on the application, it may support:
- ICD file import
- IED instantiation
- SCL file editing
- SCD project management
- Dataset configuration
- MMS report control configuration
- GOOSE publisher configuration
- GOOSE subscriber mapping
- Communication network configuration
- SCL validation and export
Some MiCOM integration projects require a separate system configuration tool in addition to the relay-specific software.
4.3 Network analysis tools
Tools such as Wireshark can help engineers verify the actual network traffic.
They are useful for checking:
- MMS communication
- GOOSE messages
- Ethernet multicast traffic
- VLAN tags
- Source and destination MAC addresses
- Communication interruptions
- GOOSE retransmission behavior
A configuration file alone cannot prove that the network is operating correctly. Network-level verification is an essential part of commissioning.
5. Step 3 – Obtain and Import the Correct ICD File
The ICD file describes the declared IEC 61850 capabilities of an IED.
For a MiCOM relay, obtain the ICD file that corresponds to the applicable device implementation.
Before importing the file, check:
- Relay model compatibility.
- Firmware compatibility.
- IEC 61850 edition.
- SCL schema version.
- Available logical devices.
- Supported logical nodes.
- Supported communication services.
After importing the ICD into a compatible system configuration tool, the IED can be instantiated in the substation project.
The imported model provides the starting point for configuring the device’s communication and application representation.
Important: An ICD file is not necessarily the final device configuration. It describes declared capabilities and may need to be configured and instantiated for the actual project.
6. Step 4 – Configure IED Names, Logical Devices and Logical Nodes
Every IED in an IEC 61850 project must have a unique name.
For example, a substation may use the following naming arrangement:
| IED name | Description |
|---|---|
| FEEDER_01 | Feeder 1 protection |
| FEEDER_02 | Feeder 2 protection |
| TRANSFORMER_01 | Transformer protection |
| BUSBAR_01 | Busbar protection |
| STATION_GW | Station gateway |
These are illustrative project names. Actual naming must follow the project’s engineering conventions and device requirements.
6.1 Logical devices
A logical device groups related logical nodes within an IED.
For example, a feeder protection relay may have logical devices representing protection, control and measurement functions, depending on its implementation.
6.2 Logical nodes
Logical nodes represent standardized functions and information.
Some commonly encountered logical node classes include:
| Logical node | Function |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| PTRC | Protection trip conditioning |
| RREC | Auto-reclosing |
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CSWI | Switch controller |
| MMXU | Measurement |
| GGIO | Generic process I/O |
The exact logical nodes and data objects available in a MiCOM relay must be checked in its MICS and ICD documentation.
7. Step 5 – Configure the IEC 61850 Communication Network
Communication parameters must be planned before connecting the relay to the substation Ethernet network.
Typical parameters include:
- IP address
- Subnet mask
- Default gateway, where applicable
- Communication interface
- Network port
- VLAN settings, where applicable
- Redundancy parameters, where supported
Example IP addressing plan
Consider a substation with two MiCOM feeder relays and a station gateway.
| Device | IP address | Subnet mask |
|---|---|---|
| FEEDER_01 | 192.168.10.11 | 255.255.255.0 |
| FEEDER_02 | 192.168.10.12 | 255.255.255.0 |
| STATION_GW | 192.168.10.100 | 255.255.255.0 |
| ENG_WS | 192.168.10.200 | 255.255.255.0 |
These addresses are examples only.
The engineer must ensure that addresses are unique and consistent with the approved substation network design.
7.1 MMS communication port
MMS over ISO-on-TCP commonly uses TCP port 102.
For an IEC 61850 client to communicate with the relay, verify:
- Relay IP address
- Client IP address
- Network routing
- Ethernet connectivity
- TCP port availability
- IEC 61850 server configuration
- Firewall and switch policies
A successful ping does not prove that MMS communication is working. It confirms only basic IP connectivity.
8. Step 6 – Configure IEC 61850 Datasets
A dataset is a collection of data references that can be used by IEC 61850 services.
Datasets are particularly important for:
- MMS reporting
- GOOSE communication
The engineer must select the data required by the application.
Example: Feeder protection dataset
A feeder relay may need to communicate the following information to the station-level system:
| Signal | Example logical node | Application |
|---|---|---|
| Phase overcurrent start | PTOC | Protection indication |
| Earth fault start | PTOC or supported earth-fault LN | Protection indication |
| Protection trip | PTRC | Trip indication |
| Circuit breaker position | XCBR | Status monitoring |
| Phase current | MMXU | Measurement |
| Relay alarm | Device-specific data model | Alarm monitoring |
The exact data references depend on the relay implementation.
Dataset configuration considerations
When configuring datasets:
- Select only the necessary data.
- Verify the functional constraint of each data attribute.
- Check that all references exist in the IED data model.
- Confirm that the dataset is supported by the relevant control block.
- Keep protection-critical GOOSE datasets focused and appropriately sized.
- Document the dataset content.
A common engineering mistake is to select a signal based only on its displayed name without checking its complete IEC 61850 data reference.
9. Step 7 – Configure MMS Reporting
MMS reporting allows an IEC 61850 client to receive information from an IED.
The station-level SCADA system may use reporting to monitor:
- Protection starts and trips
- Circuit breaker status
- Measurements
- Alarms
- Device health
- Events and disturbances, where supported
9.1 Unbuffered Report Control Block (URCB)
An unbuffered report control block is used for reporting without the persistent event buffering associated with a buffered report control block.
If the client is disconnected, events may not be retained for later delivery in the same way as buffered reporting.
9.2 Buffered Report Control Block (BRCB)
A buffered report control block supports buffering of report information according to the device’s implementation.
This can be important when the communication connection between the relay and the client is interrupted.
When the connection is restored, buffered reports can be retrieved according to the supported reporting behavior and configuration.
9.3 Typical reporting parameters
| Parameter | Description |
|---|---|
| Report ID | Identifier of the report |
| Dataset | Data collection associated with the report |
| Buffered | Defines buffered reporting behavior |
| TrgOps | Trigger options |
| IntgPd | Integrity period |
| BufTm | Buffer time |
| OptFields | Optional report fields |
| RptEnabled | Report enable status |
The available parameters and their exact behavior depend on the relay’s IEC 61850 implementation.
Practical example
A station SCADA system needs to receive the feeder circuit breaker position and protection trip indications.
The engineer:
- Identifies the relevant data objects.
- Creates a dataset.
- Configures a report control block.
- Selects appropriate trigger options.
- Configures the IEC 61850 client.
- Tests report reception and event updates.
The engineer should test both normal status changes and abnormal communication conditions.
10. Step 8 – Configure GOOSE Publishing
GOOSE communication is used for fast exchange of event information between IEDs.
A MiCOM relay may publish information such as:
- Protection trip
- Circuit breaker status
- Protection start
- Interlocking signals
- Blocking signals
- Breaker failure-related signals, where supported
The exact signals available for publishing depend on the relay’s data model and configuration.
10.1 Create a GOOSE dataset
The engineer selects the data attributes required for the GOOSE application.
For example, a feeder relay may publish:
- Protection trip indication
- Circuit breaker position
- Protection start indication
The dataset is then associated with a GOOSE control block.
10.2 Configure the GOOSE control block
The GOOSE control block defines the publishing configuration.
Important parameters include:
| Parameter | Purpose |
|---|---|
| GoCB reference | Identifies the GOOSE control block |
| Dataset | Identifies the published data collection |
| AppID | Identifies the GOOSE application |
| MAC address | Destination multicast address |
| VLAN ID | VLAN identifier, where used |
| VLAN priority | Ethernet priority, where used |
| ConfRev | Configuration revision |
| MinTime | Minimum retransmission interval |
| MaxTime | Maximum retransmission interval |
The actual parameter names and configuration options depend on the engineering tool and device implementation.
10.3 GOOSE retransmission behavior
GOOSE messages are transmitted using a retransmission mechanism.
When a data change occurs, the publisher sends the updated message and typically retransmits it at progressively increasing intervals until the steady-state transmission interval is reached.
This mechanism helps subscribers detect communication interruptions.
The subscriber can use the timeAllowedToLive information to supervise the expected arrival of the next message.
The exact behavior and timing depend on the IEC 61850 configuration and device implementation.
11. Step 9 – Configure GOOSE Subscription
Configuring a publisher is only one part of the process. The receiving IED must also be configured to subscribe to the relevant information.
Consider a practical example involving two feeder relays.
- Feeder Relay 1 publishes its circuit breaker position.
- Feeder Relay 2 subscribes to the published status.
- Feeder Relay 2 uses the received signal in its interlocking logic.
The engineering process includes:
- Identify the publisher IED.
- Identify the published dataset.
- Select the required data attribute.
- Create the external reference in the subscriber configuration.
- Map the incoming information to the supported application input.
- Configure the relay logic.
- Check the GOOSE subscription status.
- Test the complete application.
Understanding ExtRef
An external reference identifies information originating outside the subscribing IED.
It can include information identifying the source IED, logical device, logical node, data object and relevant data attribute.
A correctly configured external reference is essential for mapping incoming GOOSE information into the subscriber’s application.
However, the exact configuration and application mapping process varies between manufacturers and relay families.
12. Step 10 – Configure GOOSE Network Parameters
GOOSE communication operates directly over Ethernet using multicast frames.
It does not use TCP/IP in the same way as MMS communication.
The engineer must coordinate the relay’s communication settings with the Ethernet switch configuration.
Important parameters include:
- Destination multicast MAC address
- VLAN ID
- VLAN priority
- Ethernet port configuration
- Multicast filtering
- Network redundancy design, where applicable
GOOSE network troubleshooting
If a subscriber does not receive a GOOSE message, check:
- Is the publisher transmitting?
- Is the correct multicast MAC address configured?
- Is the subscriber configured for the correct publisher?
- Is the VLAN configuration consistent?
- Are the Ethernet switches forwarding the multicast traffic?
- Is the dataset configuration consistent?
- Is the configuration revision correct?
- Is the external reference mapped correctly?
A Wireshark capture can help distinguish a publisher problem from a network or subscriber problem.
13. Step 11 – Verify IEC 61850 Communication Using Wireshark
Wireshark is a useful tool for troubleshooting IEC 61850 communication.
Two important traffic types can be inspected.
13.1 MMS traffic
MMS communication commonly uses TCP port 102.
A useful Wireshark display filter is:
tcp.port == 102
This helps identify MMS-related network traffic.
The engineer can inspect connection establishment, data exchange and communication interruptions.
13.2 GOOSE traffic
GOOSE uses Ethernet EtherType 0x88B8.
A useful Wireshark display filter is:
goose
The engineer can inspect:
- Source MAC address
- Destination multicast MAC address
- VLAN information
- AppID
- Dataset reference
- GoCB reference
- Configuration revision
- State number (
stNum) - Sequence number (
sqNum) - Time allowed to live
The stNum generally changes when the published state changes, while sqNum changes as messages are retransmitted within that state.
Wireshark is particularly useful for checking whether the publisher is transmitting the expected dataset and whether the network is forwarding the messages.
14. Step 12 – Test IEC 61850 Functions During Commissioning
IEC 61850 commissioning should include both communication tests and application-level tests.
14.1 MMS testing
Verify:
- IEC 61850 server availability
- Client-server association
- Data object access
- Dataset access
- Report control block operation
- Event reporting
- Control operations, where required and permitted
14.2 GOOSE testing
Verify:
- Publisher operation
- Subscriber reception
- Correct data mapping
- State changes
- Retransmission behavior
- Communication supervision
- Application response
14.3 Protection and automation testing
For protection-related GOOSE applications, verify the complete signal chain.
For example, a protection trip signal may involve:
- Protection function operation.
- Internal trip logic.
- GOOSE dataset update.
- GOOSE transmission.
- Subscriber reception.
- Application logic.
- Output operation, if designed.
Testing must be conducted under approved commissioning procedures, with appropriate isolation and safety precautions.
A successful GOOSE packet capture does not prove that the protection application will operate correctly.
15. Common IEC 61850 Configuration Problems in MiCOM Relays
| Problem | Possible reason | Recommended action |
|---|---|---|
| Relay not visible to client | Incorrect IP configuration | Check IP address and network |
| MMS association failure | Server or client configuration issue | Check server availability and client settings |
| Data object unavailable | Incorrect data reference | Check MICS and ICD |
| Report not received | Incorrect dataset or RCB | Check report configuration |
| GOOSE not transmitted | Publisher configuration issue | Check GoCB and dataset |
| GOOSE not received | Network or subscriber issue | Check multicast, VLAN and ExtRef |
| Wrong GOOSE signal | Incorrect data mapping | Verify source and destination references |
| Configuration mismatch | Inconsistent project files | Compare device and system configurations |
| GOOSE supervision alarm | Messages not received within expected time | Check network and publisher |
| SCL import failure | Edition or schema incompatibility | Check tool and device support |
16. Practical IEC 61850 Engineering Checklist
Before completing a MiCOM IEC 61850 engineering project, verify the following:
Device identification
- Correct MiCOM model identified.
- Firmware version confirmed.
- IEC 61850 capabilities checked.
- Correct ICD file obtained.
System engineering
- IED names assigned.
- Logical devices and logical nodes checked.
- Datasets configured.
- MMS report control blocks configured.
- GOOSE control blocks configured.
- External references configured.
- SCL files validated.
Network configuration
- IP addresses checked.
- Network connectivity verified.
- GOOSE multicast addressing checked.
- VLAN configuration checked.
- Ethernet switch configuration verified.
Commissioning
- MMS communication tested.
- Reporting tested.
- GOOSE publishing tested.
- GOOSE subscription tested.
- Application logic tested.
- Communication failure behavior checked.
- Final configuration archived.
17. Conclusion
IEC 61850 engineering in MiCOM protection relays requires coordination between relay configuration, system-level engineering and network commissioning.
The main engineering activities include identifying the relay’s IEC 61850 capabilities, importing the appropriate ICD file, configuring logical nodes and datasets, establishing MMS reporting, configuring GOOSE publishing and subscription, and testing the communication network.
Engineers must understand that configuring IEC 61850 is not simply enabling an Ethernet port. The complete process involves data modeling, communication engineering, application logic and functional verification.
By following a structured engineering procedure, protection and substation automation engineers can improve the reliability and maintainability of multi-vendor IEC 61850 systems.
18. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM protection relays and substation automation.
Our training covers:
- MiCOM relay configuration and engineering
- IEC 61850 fundamentals and architecture
- MMS communication and reporting
- GOOSE publishing and subscription
- Logical nodes and data objects
- Datasets and report control blocks
- ICD, CID, IID and SCD files
- SCL engineering and system integration
- Wireshark-based communication analysis
- IEC 61850 testing and commissioning
Training is available through video courses, structured self-paced training, face-to-face sessions and customized in-house programs.
Visit Elec-Engg to explore practical courses by Dr Saeed Roostaee in power system protection and substation automation.
