- 1. Introduction
- 2. What Is IEC 61850?
- 3. IEC 61850 Architecture in a Substation
- 4. IEC 61850 Data Modelling: Logical Devices, Logical Nodes and Data Objects
- 5. MMS Communication in GE Multilin Relays
- 6. IEC 61850 Reports: Buffered and Unbuffered Reporting
- 7. GOOSE Communication in GE Multilin Protection Applications
- 8. Practical GOOSE Application: Feeder Protection Blocking
- 9. GOOSE Network Parameters: MAC Address, APPID and VLAN
- 10. SCL Files: ICD, CID, IID and SCD
- 11. Integration of GE Multilin Relays with SICAM PAS and SCADA Systems
- 12. Time Synchronization in IEC 61850 Substations
- 13. Ethernet Network Design for GE Multilin IEC 61850 Systems
- 14. IEC 61850 Cybersecurity Considerations
- 15. Practical Engineering Example: GOOSE-Based Feeder Interlocking
- 16. Testing IEC 61850 Communication Using IEDScout and Wireshark
- 17. IEC 61850 Commissioning and Testing Checklist
- 18. Common IEC 61850 Communication Problems and Troubleshooting
- 19. Best Practices for GE Multilin IEC 61850 Engineering
- 20. Conclusion
- 21. Training on GE Multilin Protection Relays and IEC 61850 by Elec-Engg
- 22. Frequently Asked Questions
- What is the difference between MMS and GOOSE in IEC 61850?
- Can GE Multilin relays communicate using IEC 61850?
- What is the purpose of a GOOSE message?
- What is an SCD file?
- What is the difference between ICD and CID files?
- Can GE Multilin relays be integrated with Siemens SICAM PAS?
- Which software can be used to test IEC 61850 communication?
- Does IEC 61850 eliminate all hardwired connections?
1. Introduction
IEC 61850 is an international standard for communication and interoperability in electrical substations. It defines a common data model, communication services, engineering language and mechanisms for exchanging information between protection relays, bay controllers, merging units, SCADA systems and other intelligent electronic devices (IEDs).
GE Multilin protection relays are used in a wide range of power system applications, including feeder, transformer, generator, motor, line and busbar protection. Depending on the relay model, installed communication hardware, firmware version and licensed features, selected GE Multilin devices can participate in IEC 61850-based substation automation systems.
IEC 61850 integration is not simply a matter of connecting an Ethernet cable and assigning an IP address. Successful engineering requires an understanding of:
- IEC 61850 data modelling and logical nodes.
- MMS client-server communication.
- GOOSE publisher-subscriber communication.
- Datasets and report control blocks.
- SCL engineering files.
- Ethernet network design and VLAN configuration.
- Time synchronization.
- SCADA integration.
- Communication testing and troubleshooting.
This article explains how IEC 61850 can be applied to GE Multilin protection relays, with an emphasis on practical engineering, commissioning and substation automation.
Important: IEC 61850 capabilities differ between GE Multilin product families and individual models. The supported services, logical nodes, control models, redundancy options and configuration procedures must be confirmed using the documentation for the exact relay, communication hardware and firmware revision.
2. What Is IEC 61850?
IEC 61850 is more than a communication protocol. It defines a structured approach to representing substation equipment and exchanging information.
Traditional communication protocols often use manufacturer-specific registers, addresses or point lists. IEC 61850 introduces standardized logical nodes, data objects and data attributes, allowing different devices to represent common electrical functions using a consistent information model.
For example, a feeder protection relay may provide information related to:
- Phase overcurrent protection.
- Earth fault protection.
- Circuit-breaker position.
- Measured phase currents.
- Measured phase voltages.
- Protection operation.
- Alarm and supervision conditions.
- Communication and device health.
These signals can be represented using appropriate IEC 61850 logical nodes and data objects, depending on the device implementation.
The main benefits include:
- Improved interoperability between IEDs.
- Standardized data modelling.
- High-speed peer-to-peer communication through GOOSE.
- Flexible SCADA integration using MMS.
- Reduced conventional copper wiring for selected interlocking and status applications.
- More structured engineering using SCL files.
- Improved diagnostics and communication supervision.
3. IEC 61850 Architecture in a Substation
A typical digital substation architecture is divided into three functional levels.
3.1 Station Level
The station level contains systems responsible for overall substation supervision and control.
Typical equipment includes:
- SCADA servers.
- HMI workstations.
- Substation automation controllers.
- Engineering workstations.
- Gateway devices.
- Time synchronization equipment.
GE Multilin protection relays may exchange measurements, indications, alarms and control information with station-level systems through supported IEC 61850 services.
3.2 Bay Level
The bay level contains IEDs associated with individual electrical bays.
Examples include:
- Feeder protection relays.
- Transformer protection relays.
- Generator protection relays.
- Busbar protection relays.
- Circuit-breaker control units.
- Metering devices.
A GE Multilin relay installed in a feeder or transformer bay may provide protection functions and exchange information with other bay-level devices.
3.3 Process Level
The process level is associated with the primary equipment interface.
Depending on the substation architecture, it may include:
- Current transformers.
- Voltage transformers.
- Merging units.
- Circuit-breaker interfaces.
- Switchgear sensors.
- Process bus communication networks.
Not every IEC 61850 substation uses a process bus. A conventional hardwired process interface can coexist with IEC 61850 station-bus communication.
4. IEC 61850 Data Modelling: Logical Devices, Logical Nodes and Data Objects
Understanding the IEC 61850 information model is essential before configuring MMS reports or GOOSE messages.
The information model is organized hierarchically.
4.1 Physical Device
The physical IED is the actual protection relay or other intelligent device installed in the substation.
For example, a GE Multilin feeder relay is a physical IED.
4.2 Logical Device (LD)
A logical device groups related functions within an IED.
A protection relay may contain logical devices associated with protection, measurement, control and other functions. The actual structure depends on the manufacturer’s implementation.
4.3 Logical Node (LN)
A logical node represents a standardized functional element.
Examples include:
| Logical Node | General purpose |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIF | Differential protection |
| PDIS | Distance protection |
| MMXU | Measurement |
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CSWI | Switch control |
| PTRC | Protection trip conditioning |
| GGIO | Generic input/output |
| LPHD | Physical device information |
| LLN0 | Logical device common functions |
The availability and naming of logical nodes depend on the relay’s IEC 61850 conformance and implementation.
4.4 Data Objects and Data Attributes
Each logical node contains data objects, which in turn contain data attributes.
For example, a circuit-breaker logical node XCBR may contain a position data object commonly represented as Pos.
The position information can include:
- Position value.
- Data quality.
- Timestamp.
A typical IEC 61850 representation may look like:
XCBR1.Pos.stVal
The exact logical node instance and data path must be checked against the relay’s IEC 61850 model.
4.5 Why Data Modelling Matters
When integrating a GE Multilin relay with a substation automation system, the engineer must understand which signals are available and how they are represented.
For example, the SCADA engineer may require:
- Breaker open indication.
- Breaker closed indication.
- Overcurrent protection operation.
- Earth fault protection operation.
- Relay healthy indication.
- Phase current measurements.
These signals must be mapped using the data model supported by the actual device.
5. MMS Communication in GE Multilin Relays
Manufacturing Message Specification (MMS) is an application-layer communication service used in IEC 61850 for client-server communication.
In a typical substation automation system:
- The protection relay operates as an MMS server.
- The SCADA system or station controller operates as an MMS client.
- The client accesses data exposed by the server.
- The client can receive reports and, where supported and authorized, issue control commands.
MMS normally operates over TCP/IP using the IEC 61850 communication profile.
5.1 Typical MMS Applications
MMS can be used for:
- Reading measurements.
- Reading protection indications.
- Receiving alarms.
- Monitoring breaker status.
- Reading device information.
- Receiving event reports.
- Accessing supported control services.
- Monitoring communication and device health.
5.2 Client-Server Architecture
Consider a substation containing a GE Multilin feeder protection relay and a station-level SCADA server.
The relay measures current and voltage and executes its protection functions. The SCADA server communicates with the relay to obtain measurements and status information.
For example:
- The relay detects a feeder overcurrent condition.
- The protection function operates.
- The relay updates the corresponding IEC 61850 data.
- The MMS server makes the updated information available.
- The SCADA client receives the associated report, if correctly configured.
- The operator sees the alarm and event information on the HMI.
MMS reporting is particularly useful for supervisory monitoring and event collection.
6. IEC 61850 Reports: Buffered and Unbuffered Reporting
IEC 61850 provides reporting mechanisms that allow an MMS client to receive changes in selected data.
A report is normally associated with a dataset and a report control block.
6.1 Datasets
A dataset is a logical collection of data attributes.
For example, a feeder relay dataset may contain:
- Phase current measurements.
- Phase voltage measurements.
- Breaker position.
- Protection operation indications.
- Device health status.
The dataset defines which information is available for reporting.
6.2 Report Control Blocks
A Report Control Block (RCB) defines how reports are generated and delivered.
Important configuration properties can include:
- Report identifier.
- Dataset reference.
- Buffered or unbuffered reporting mode.
- Integrity period.
- General interrogation.
- Trigger options.
- Optional fields.
- Client association and reservation parameters.
The available properties and configuration mechanisms depend on the relay implementation.
6.3 Buffered Reports (BRCB)
Buffered reporting is designed to retain event information during temporary communication interruptions, subject to the device’s buffer capacity and implementation.
When communication is restored, the client may retrieve buffered reports.
This is particularly useful when event history must be preserved during short network interruptions.
6.4 Unbuffered Reports (URCB)
Unbuffered reporting provides event-driven reporting without the same event-retention behavior as buffered reporting.
If the communication connection is lost, events occurring during the interruption may not be recovered through the unbuffered report mechanism.
6.5 Practical Engineering Considerations
When configuring reports, verify:
- The correct dataset is selected.
- The report control block is supported.
- The reporting client is correctly configured.
- The integrity period is appropriate.
- Required trigger options are enabled.
- The client can establish the required association.
- The SCADA system correctly interprets quality and timestamps.
Do not assume that every GE Multilin relay exposes identical report-control features.
7. GOOSE Communication in GE Multilin Protection Applications
Generic Object Oriented Substation Event (GOOSE) is an IEC 61850 mechanism for fast peer-to-peer communication between IEDs.
Unlike MMS, which uses a client-server communication model, GOOSE uses a publisher-subscriber model.
A GOOSE publisher sends messages containing selected data values. One or more subscriber IEDs receive and process those messages.
GOOSE is commonly used for:
- Interlocking.
- Protection blocking.
- Breaker failure initiation or coordination.
- Transfer trip applications.
- Trip signal exchange.
- Breaker status exchange.
- Busbar and feeder automation.
- Other peer-to-peer automation functions.
The suitability of a particular application depends on the relay’s supported GOOSE functionality, system design and protection scheme requirements.
7.1 GOOSE Publisher
The publisher is the IED that generates and transmits the GOOSE message.
For example, a feeder relay may publish:
- Protection operated.
- Breaker closed.
- Breaker open.
- Interlocking condition.
- Device alarm.
7.2 GOOSE Subscriber
The subscriber receives the GOOSE message and uses the received information in its application logic.
For example, a second relay may subscribe to a blocking signal from another feeder relay.
7.3 GOOSE Dataset
The GOOSE dataset defines the information included in the transmitted message.
It may contain several data attributes associated with protection, control or status functions.
The dataset must be engineered consistently between publisher and subscriber.
7.4 GOOSE Control Block
The GOOSE Control Block (GoCB) defines the publication properties.
Typical parameters include:
- GoCB reference.
- Dataset reference.
- GOOSE control block enable state.
- Application identifier (APPID).
- Destination multicast MAC address.
- VLAN identifier.
- VLAN priority.
- Minimum retransmission time.
- Maximum retransmission time.
- Configuration revision.
The exact parameter names and available options depend on the device implementation and engineering tool.
7.5 GOOSE Message Transmission
GOOSE communication uses Ethernet multicast frames.
When a dataset value changes, the publisher typically transmits a new message rapidly. The transmission interval then increases according to the configured retransmission behavior until another event occurs.
This event-driven retransmission mechanism supports fast communication and allows subscribers to supervise the continued presence of messages.
GOOSE communication is not ordinary cyclic polling.
8. Practical GOOSE Application: Feeder Protection Blocking
Consider two feeders connected to the same busbar.
Feeder A and Feeder B are equipped with compatible IEC 61850 protection relays.
The protection design requires Feeder A to send a blocking signal to Feeder B under a defined operating condition.
A simplified engineering sequence is:
- Feeder A detects the condition specified by the protection design.
- The corresponding signal is mapped to a GOOSE dataset.
- Feeder A publishes the GOOSE message.
- Feeder B subscribes to the published dataset.
- The received signal is mapped to an appropriate input or logic function.
- Feeder B uses the signal in its configured protection logic.
The purpose may be to improve selectivity or coordinate protection operation.
Important protection engineering note: A GOOSE blocking scheme must be designed with a defined fail-safe response. The engineer must consider communication loss, stale data, invalid quality, publisher failure, subscriber behavior and the required protection response. A communication failure must never silently defeat the intended protection function.
9. GOOSE Network Parameters: MAC Address, APPID and VLAN
Correct Ethernet configuration is essential for reliable GOOSE communication.
9.1 Multicast MAC Address
GOOSE messages are transmitted using multicast Ethernet destination addresses.
The subscriber must be configured to recognize the intended publication.
An incorrect destination MAC address can prevent the subscriber from receiving the expected message.
9.2 Application Identifier (APPID)
The APPID helps identify the GOOSE application and distinguish message streams.
Publisher and subscriber configuration must be consistent with the engineered communication design.
9.3 VLAN Identifier
A VLAN can be used to separate GOOSE traffic from other Ethernet communication.
For example, a substation network may use:
- One VLAN for GOOSE traffic.
- Another VLAN for station-level MMS communication.
- A separate management VLAN.
The actual VLAN architecture must be designed according to the substation network requirements.
9.4 VLAN Priority
IEEE 802.1Q priority tagging can be used to prioritize selected Ethernet frames.
GOOSE traffic may be assigned a suitable priority according to the network engineering specification.
Priority tagging alone does not guarantee deterministic delivery. Switch configuration, traffic loading, network topology and end-to-end performance must also be considered.
10. SCL Files: ICD, CID, IID and SCD
Substation Configuration Language (SCL) is the engineering language defined by IEC 61850-6.
SCL files are XML-based files used to describe IED capabilities, communication configuration, substation structure and communication relationships.
Understanding SCL is essential when integrating GE Multilin relays into a multi-vendor substation automation system.
10.1 ICD File
IED Capability Description (ICD) describes the capabilities of an IED.
It typically contains information about:
- Logical devices.
- Logical nodes.
- Data objects.
- Supported communication services.
- Available datasets and control blocks, as applicable.
- Communication capabilities.
The ICD file is generally supplied or generated through the manufacturer’s engineering environment.
10.2 CID File
Configured IED Description (CID) contains the configuration intended for a particular IED.
It can include the device’s configured communication parameters and relevant IEC 61850 engineering information.
10.3 IID File
Instantiated IED Description (IID) represents an instantiated IED configuration for engineering exchange.
Its use depends on the engineering workflow and tool compatibility.
10.4 SCD File
Substation Configuration Description (SCD) describes the overall IEC 61850 substation configuration.
It can contain:
- Substation structure.
- IED descriptions.
- Communication networks.
- Communication associations.
- GOOSE publisher-subscriber relationships.
- Datasets and control blocks.
The SCD file is particularly important in multi-vendor substation engineering.
10.5 Typical SCL Engineering Workflow
A general IEC 61850 engineering workflow may include:
- Obtain the correct capability description for each IED.
- Import IED descriptions into the system engineering tool.
- Create the substation structure.
- Define communication networks.
- Configure MMS datasets and reports.
- Configure GOOSE datasets and control blocks.
- Define publisher-subscriber relationships.
- Validate the overall configuration.
- Export the appropriate configuration files.
- Import the relevant configuration into each IED using its supported engineering method.
- Verify the actual configuration and communication during commissioning.
The precise workflow depends on the engineering software used by the project and the GE Multilin relay’s supported configuration process.
11. Integration of GE Multilin Relays with SICAM PAS and SCADA Systems
GE Multilin protection relays may be integrated into substation automation systems using supported IEC 61850 services.
For example, a substation may include:
- GE Multilin feeder relays.
- GE Multilin transformer protection relays.
- Siemens SIPROTEC protection relays.
- Bay control units.
- SICAM PAS.
- SCADA and HMI workstations.
In such a system, IEC 61850 can provide a common communication framework for exchanging measurements, indications, alarms and control information.
11.1 MMS Integration
Where supported, the station automation system can act as an MMS client and communicate with the relay’s IEC 61850 server.
The engineering process normally includes:
- Confirming the relay’s IEC 61850 server capability.
- Obtaining the correct IED description.
- Importing or configuring the IED in the station automation engineering tool.
- Identifying the required logical nodes and data attributes.
- Configuring datasets and reports as required.
- Mapping the signals into the SCADA database.
- Testing the measurements, indications and alarms.
11.2 GOOSE Integration
Where both devices support the required GOOSE services, GOOSE can be used for peer-to-peer communication.
For example:
- A GE Multilin relay publishes breaker status.
- A bay controller subscribes to the status.
- The bay controller uses the received status for a defined automation function.
The engineering tool must support the required SCL workflow, and the devices must have compatible IEC 61850 implementations.
11.3 Important Integration Considerations
Before starting integration, verify:
- Supported IEC 61850 edition and conformance.
- Relay firmware and communication hardware.
- Supported logical nodes and data attributes.
- MMS reporting capabilities.
- GOOSE publisher and subscriber capabilities.
- Control models.
- SCL compatibility.
- Network requirements.
- Time synchronization.
- Cybersecurity requirements.
Never assume that two IEC 61850-compliant devices automatically support every possible communication service or data model combination.
12. Time Synchronization in IEC 61850 Substations
Accurate time synchronization is important for event analysis, sequence-of-events recording and disturbance investigation.
A substation may contain many IEDs from different manufacturers. If their clocks are not synchronized, comparing event timestamps becomes difficult.
Common time synchronization methods include:
12.1 SNTP
Simple Network Time Protocol is used for clock synchronization over an IP network.
It may be supported by selected GE Multilin devices and other substation equipment.
12.2 IRIG-B
IRIG-B is a time synchronization signal commonly used in protection and control systems.
It can provide a dedicated time reference to compatible IEDs.
12.3 PTP
Precision Time Protocol is defined by IEEE 1588.
It is used in applications requiring more precise time synchronization, particularly in appropriately engineered digital substations.
PTP support, profiles and performance depend on the device and network architecture.
12.4 Commissioning Checks
During commissioning:
- Verify the configured time source.
- Confirm the device’s time synchronization status.
- Compare relay time against the station reference.
- Check event timestamps.
- Verify time quality indications where available.
- Confirm behavior during loss and restoration of the time source.
The required accuracy depends on the application and project specification.
13. Ethernet Network Design for GE Multilin IEC 61850 Systems
IEC 61850 communication reliability depends on proper network engineering.
The Ethernet network must be designed to support the required communication services and protection applications.
Important considerations include:
- Network topology.
- Managed Ethernet switches.
- Fibre-optic connections.
- VLAN segmentation.
- Multicast traffic handling.
- Network loading.
- Redundancy.
- Port security.
- Cybersecurity.
- Time synchronization.
- Network monitoring.
13.1 Star Topology
In a star topology, IEDs connect to central Ethernet switches.
This arrangement is straightforward to implement and troubleshoot.
However, the failure of a central switch may affect several connected devices unless redundancy is provided.
13.2 Ring Topology
A ring topology connects network devices in a loop.
The actual recovery behavior depends on the redundancy protocol and network design.
A ring must be engineered and tested to ensure that recovery time meets the application’s requirements.
13.3 Redundant Network Architectures
Some IEC 61850 substations use specialized redundancy architectures.
Examples include:
- PRP – Parallel Redundancy Protocol.
- HSR – High-availability Seamless Redundancy.
These technologies are not universally supported by all GE Multilin relays. Confirm the exact relay hardware and firmware capabilities before designing a PRP or HSR architecture.
14. IEC 61850 Cybersecurity Considerations
Connecting protection relays to Ethernet networks introduces cybersecurity responsibilities.
Protection and control networks must be protected against unauthorized access, configuration changes and communication disruption.
Recommended practices include:
- Separate protection networks from business IT networks.
- Use network segmentation and appropriate firewalls.
- Restrict access to engineering workstations.
- Apply role-based access controls where supported.
- Use strong authentication and password policies.
- Disable unused communication services where practical.
- Maintain configuration backups.
- Record engineering changes.
- Monitor network access and communication events.
- Follow the applicable IEC 62351 and project cybersecurity requirements.
IEC 61850 communication does not automatically mean that all communication is encrypted or authenticated. Security mechanisms depend on the applicable standard parts, device implementation and system configuration.
15. Practical Engineering Example: GOOSE-Based Feeder Interlocking
Consider a substation with two feeder bays.
The engineering requirement is to exchange a status signal between the two protection relays to implement a defined interlocking function.
Assume:
- Feeder A has a GE Multilin relay acting as the GOOSE publisher.
- Feeder B has a compatible relay acting as the GOOSE subscriber.
- Both devices are connected to the same engineered Ethernet network.
- The interlocking logic is defined in the protection and control design.
Step 1: Identify the Signal
Determine the exact status or protection signal that must be transmitted.
For example, it may be a breaker position or an interlocking permissive.
Step 2: Confirm Data Availability
Check the IEC 61850 model of Feeder A and verify that the required signal is available for publication.
Step 3: Create the Dataset
Create or select a dataset containing the required data attribute.
Step 4: Configure the GOOSE Publisher
Configure the GOOSE control block and its communication parameters.
Step 5: Configure the Subscriber
Configure Feeder B to subscribe to the correct GOOSE message and map the received data to the intended application input.
Step 6: Verify Network Configuration
Check:
- Publisher and subscriber network connectivity.
- Multicast MAC address.
- APPID.
- VLAN ID.
- VLAN priority.
- Switch multicast handling.
- GOOSE message transmission.
Step 7: Test the Application
Operate the initiating signal under controlled test conditions and verify that Feeder B receives and processes the information correctly.
Step 8: Test Communication Failure
Disconnect or interrupt the relevant communication path under an approved test procedure.
Verify that the subscriber detects communication loss and that the protection or interlocking logic responds according to the approved design.
The example is conceptual. The actual implementation must use the logical nodes, data attributes, GOOSE capabilities and application logic supported by the selected relays.
16. Testing IEC 61850 Communication Using IEDScout and Wireshark
Communication testing is an essential part of IEC 61850 commissioning.
Two useful engineering tools are IEDScout and Wireshark.
16.1 IEDScout
IEDScout can be used in supported configurations to inspect IEC 61850 communication and interact with IED data models.
Depending on the tool version and device capabilities, engineers may use it to:
- Discover IEC 61850 servers.
- Browse logical devices.
- Inspect logical nodes.
- Read data attributes.
- Examine datasets.
- Inspect report control blocks.
- Monitor GOOSE messages.
- Test selected communication services.
IEDScout is useful for identifying whether the relay exposes the expected IEC 61850 information model.
16.2 Wireshark
Wireshark is a network protocol analyzer.
It can be used to capture and inspect Ethernet traffic, including IEC 61850-related communication.
Typical applications include:
- Inspecting GOOSE frames.
- Checking destination multicast MAC addresses.
- Verifying APPID.
- Checking VLAN tags.
- Observing retransmission behavior.
- Inspecting MMS communication.
- Identifying network communication problems.
16.3 Practical GOOSE Inspection
When testing GOOSE communication with Wireshark:
- Select the correct network interface.
- Start a packet capture.
- Generate the expected GOOSE event.
- Identify the GOOSE frames.
- Inspect the publisher information.
- Check the APPID and destination MAC.
- Verify the dataset values.
- Observe state changes and retransmission behavior.
- Confirm that the subscriber receives the expected message.
A packet capture can confirm that a message is present on the observed network segment. It does not, by itself, prove that the subscriber’s protection logic has processed the message correctly. End-to-end functional testing is still required.
17. IEC 61850 Commissioning and Testing Checklist
A structured commissioning procedure should cover both communication and protection functionality.
17.1 Device and Firmware Verification
- Confirm the exact relay model.
- Confirm hardware and communication modules.
- Verify firmware version.
- Confirm IEC 61850 capability.
- Check the applicable manufacturer’s documentation.
- Record the relay identification and configuration revision.
17.2 IP and Network Configuration
- Verify IP address.
- Verify subnet mask.
- Verify gateway where required.
- Check Ethernet link status.
- Confirm switch port configuration.
- Verify VLAN configuration.
- Check multicast handling.
17.3 MMS Testing
- Verify MMS server availability.
- Confirm client-server association.
- Browse the data model.
- Read required measurements.
- Verify datasets.
- Test report control blocks.
- Confirm event reporting.
- Verify timestamps and data quality.
- Test supported control functions under approved conditions.
17.4 GOOSE Testing
- Verify publisher configuration.
- Verify subscriber configuration.
- Check dataset consistency.
- Confirm APPID.
- Confirm multicast MAC address.
- Verify VLAN parameters.
- Confirm GOOSE transmission.
- Verify subscriber reception.
- Test data changes.
- Test communication interruption.
- Verify the configured fail-safe response.
17.5 Time Synchronization
- Verify time source.
- Confirm synchronization status.
- Compare timestamps.
- Check event sequence.
- Test loss and restoration of the time source where required.
17.6 Protection and Functional Testing
- Test the initiating protection element.
- Verify the associated GOOSE publication.
- Confirm subscriber logic operation.
- Verify output relay operation where applicable.
- Confirm breaker or interlocking response.
- Test communication failure behavior.
- Record all results.
18. Common IEC 61850 Communication Problems and Troubleshooting
Problem 1: MMS Server Cannot Be Accessed
Possible causes:
- Incorrect IP address.
- Incorrect subnet configuration.
- Ethernet connection problem.
- MMS service not enabled.
- Unsupported communication configuration.
- Firewall or network filtering.
Recommended checks:
- Verify the IP configuration.
- Check physical Ethernet connectivity.
- Confirm that the relay supports the required MMS service.
- Inspect network traffic.
- Check the client configuration.
Problem 2: SCADA Receives No Reports
Possible causes:
- Incorrect dataset reference.
- Report control block not enabled.
- Incorrect client association.
- Wrong trigger options.
- Incompatible report configuration.
Recommended checks:
- Inspect the dataset.
- Verify the report control block.
- Check the client configuration.
- Test general interrogation where supported.
- Confirm event changes at the relay.
Problem 3: GOOSE Publisher Transmits but Subscriber Does Not Operate
Possible causes:
- Incorrect multicast MAC address.
- Incorrect APPID.
- VLAN mismatch.
- Dataset mismatch.
- Subscriber mapping error.
- GOOSE subscription disabled.
- Network switch filtering multicast traffic.
Recommended checks:
- Capture the GOOSE traffic.
- Verify the publisher parameters.
- Compare the subscriber configuration.
- Check the dataset structure and configuration revision.
- Verify switch VLAN and multicast settings.
- Confirm the subscriber’s received data and quality.
Problem 4: GOOSE Communication Works Intermittently
Possible causes:
- Network congestion.
- Unstable Ethernet links.
- Incorrect switch configuration.
- Multicast filtering problems.
- Network redundancy recovery behavior.
- Excessive or poorly engineered network traffic.
Recommended checks:
- Inspect switch logs.
- Monitor packet loss.
- Check port errors.
- Review network loading.
- Verify redundancy operation.
- Capture traffic during the failure.
Problem 5: Incorrect Event Timestamps
Possible causes:
- Incorrect time source.
- SNTP configuration error.
- IRIG-B wiring or signal problem.
- PTP profile mismatch.
- Time synchronization not enabled.
- Incorrect time zone or clock configuration in the station system.
Recommended checks:
- Verify the configured time source.
- Compare relay and station clocks.
- Check synchronization status.
- Inspect event timestamps.
- Verify the time distribution architecture.
Problem 6: Incorrect Data Quality
IEC 61850 data includes quality information.
A value may be present but marked invalid, questionable or otherwise abnormal.
Possible causes include:
- Invalid measurement input.
- Communication interruption.
- Substituted data.
- Device self-supervision problem.
- Data mapping error.
Engineers should investigate the value and its quality attributes together rather than relying only on the displayed numerical value.
19. Best Practices for GE Multilin IEC 61850 Engineering
For reliable substation automation, consider the following recommendations:
- Confirm IEC 61850 support before selecting the relay.
- Use the correct firmware-specific IED description.
- Maintain consistent SCL file revisions.
- Define naming conventions for IEDs, datasets and control blocks.
- Document every GOOSE publisher-subscriber relationship.
- Separate station-bus and process-bus traffic where required by the design.
- Engineer VLANs and multicast behavior carefully.
- Verify MMS reporting before integrating the complete SCADA database.
- Test GOOSE communication end to end.
- Include communication failure testing in the commissioning plan.
- Synchronize relay clocks using an approved time source.
- Keep backups of relay settings and IEC 61850 configuration files.
- Maintain a record of firmware and configuration revisions.
- Apply appropriate cybersecurity controls.
- Never treat successful Ethernet communication as proof of correct protection operation.
20. Conclusion
IEC 61850 provides a powerful framework for integrating GE Multilin protection relays into modern substation automation systems.
MMS supports client-server communication for measurements, reports, alarms and supervisory functions. GOOSE provides peer-to-peer communication for applications such as interlocking, blocking and status exchange. SCL files provide a structured engineering approach for defining IED capabilities and system communication relationships.
However, successful implementation requires more than protocol knowledge. Engineers must understand the relay’s actual IEC 61850 data model, firmware capabilities, communication configuration, network architecture and protection application.
Practical testing with tools such as IEDScout and Wireshark, combined with end-to-end functional testing, helps identify configuration and communication problems before the system enters service.
For protection and substation automation engineers, IEC 61850 knowledge is increasingly important when working with multi-vendor substations and modern digital protection systems.
21. Training on GE Multilin Protection Relays and IEC 61850 by Elec-Engg
Elec-Engg provides practical technical training by Dr Saeed Roostaee (Electrical Engineering), focusing on power system protection, protection relay engineering, commissioning and substation automation.
The training approach emphasizes practical engineering applications rather than theoretical explanations alone.
Relevant training subjects include:
- GE Multilin protection relay architecture and configuration.
- GE Multilin feeder, transformer, motor and generator protection.
- Overcurrent and directional protection.
- Transformer and line differential protection.
- Generator and motor protection.
- EnerVista software and relay settings management.
- IEC 61850 communication and data modelling.
- MMS client-server communication.
- GOOSE publisher and subscriber configuration.
- SCL engineering and multi-vendor integration.
- IEDScout and Wireshark for communication testing.
- Protection relay testing and commissioning.
Training can be delivered through:
- Pre-recorded technical video courses.
- Structured self-paced training.
- Live online training.
- Face-to-face technical training.
- Customized in-house training for utilities, industries and engineering companies.
Explore Elec-Engg: https://elec-engg.com/
Contact for technical training and customized programs: https://elec-engg.com/contact/
22. Frequently Asked Questions
What is the difference between MMS and GOOSE in IEC 61850?
MMS uses a client-server communication model and is commonly used for SCADA data access, reporting, measurements and supervisory control. GOOSE uses a publisher-subscriber model and is commonly used for fast peer-to-peer communication between IEDs.
Can GE Multilin relays communicate using IEC 61850?
Selected GE Multilin relays support IEC 61850 communication. The available services and features depend on the exact model, communication hardware, firmware and configuration.
What is the purpose of a GOOSE message?
A GOOSE message allows one IED to transmit selected status, protection or control information to other IEDs over an Ethernet network. Typical applications include interlocking, blocking, breaker status exchange and protection coordination.
What is an SCD file?
An SCD file is a Substation Configuration Description file. It describes the IEC 61850 substation configuration, including IEDs, communication networks and relevant communication relationships.
What is the difference between ICD and CID files?
An ICD file describes the capabilities of an IED. A CID file contains the configured description intended for a particular IED. Their exact use depends on the engineering workflow and tool implementation.
Can GE Multilin relays be integrated with Siemens SICAM PAS?
Integration may be possible where the specific relay and SICAM PAS versions support compatible IEC 61850 services and data models. The IED description, communication configuration and signal mapping must be verified and tested.
Which software can be used to test IEC 61850 communication?
IEDScout can be used to inspect IEC 61850 data models and supported communication services. Wireshark can capture and analyze network traffic, including GOOSE and MMS-related packets. Additional manufacturer and system engineering tools may also be required.
Does IEC 61850 eliminate all hardwired connections?
No. IEC 61850 can replace selected communication and signal wiring, but conventional hardwired interfaces may still be required for CTs, VTs, trip circuits, critical interlocks and other applications depending on the substation design.
