Modern digital substations rely on fast, standardized communication between protection relays and supervisory systems. This guide explains IEC 61850 communication between MiCOM relay and SCADA, covering network setup, IP configuration, SCL files (ICD/CID), and real-time data exchange using MMS and GOOSE. Whether you are integrating Schneider Electric MiCOM P141, P143, or other MiCOM models, this step-by-step tutorial will help you build a reliable substation automation network.
What Is IEC 61850?
IEC 61850 is an international communication standard for substation automation systems. It replaces vendor-specific protocols with a unified, object-oriented data model and Ethernet-based communication.
Key Features of IEC 61850
- High-speed communication using Ethernet
- Standardized data models for protection and control
- MMS (Manufacturing Message Specification) for client/server communication
- GOOSE (Generic Object Oriented Substation Event) for fast event messaging
- SCL files (ICD, CID, SCD) for system engineering and configuration
IEC 61850 enables seamless communication between MiCOM relays and SCADA systems regardless of manufacturer.
Why Use IEC 61850 with MiCOM Relays?
Schneider Electric’s MiCOM protection relays are widely used in transmission, distribution, and industrial substations. With IEC 61850 support, they provide:
- Real-time status and measurements to SCADA
- Fast protection signaling via GOOSE
- Interoperability with any IEC 61850-compliant IED
- Reduced wiring using Ethernet networks
- Centralized monitoring and control
This makes IEC 61850 communication between MiCOM relay and SCADA ideal for modern digital substations.
MiCOM Relay Models Supporting IEC 61850
Most modern MiCOM relays support IEC 61850, including:
- MiCOM P141 / P143 – Feeder protection
- MiCOM P127 / P122 – Metering and control
- MiCOM P445 / P437 – Distance protection
- MiCOM C264 / P40 Agile series
Ensure your relay firmware supports IEC 61850 before configuration.
System Requirements
Before starting, confirm the following:
Hardware
- MiCOM relay with Ethernet port
- Managed Ethernet switch (substation-grade preferred)
- SCADA server or HMI workstation
Software
- Schneider S1 Studio / Energy Studio (for MiCOM configuration)
- IEC 61850-compatible SCADA software
- Network configuration access
Network & IP Configuration
A stable network is the foundation of IEC 61850 communication.
Step 1: Physical Connection
Connect the MiCOM relay’s Ethernet port to the substation switch using a CAT-6 cable.
Step 2: Assign IP Address to MiCOM Relay
Using S1 Studio / Energy Studio:
- Connect your PC to the relay.
- Open the relay configuration file.
- Navigate to Communication → Ethernet Settings.
- Set:
- IP Address: e.g.,
192.168.1.10 - Subnet Mask:
255.255.255.0 - Gateway: (if required by your network)
- IP Address: e.g.,
- Write settings to the relay and reboot.
📌 Tip: Ensure the SCADA system is on the same subnet.
Understanding SCL Files: ICD, CID, and SCD
IEC 61850 uses Substation Configuration Language (SCL) files to define communication.
🔹 ICD (IED Capability Description)
- Provided by the manufacturer
- Describes relay capabilities and data models
🔹 CID (Configured IED Description)
- Device-specific configuration
- Created after engineering the relay
- Loaded into the MiCOM relay
🔹 SCD (Substation Configuration Description)
- Contains full substation architecture
- Used when multiple IEDs are integrated
Creating the CID File in S1 Studio / Energy Studio
Step 3: Export ICD File
- Open your MiCOM project in S1 Studio.
- Go to IEC 61850 Configuration.
- Export the ICD file.
Step 4: Engineering in SCADA or IEC 61850 Tool
- Import the ICD file into your SCADA or system configurator.
- Map required data points:
- Measurements (Voltage, Current, Power)
- Status (Breaker Open/Close)
- Alarms and protection trips
- Generate the CID file.
Step 5: Upload CID to MiCOM Relay
- Return to S1 Studio.
- Import the generated CID file.
- Download it to the relay.
- Restart the relay to apply settings.
SCADA Integration Using MMS
MMS is used for standard client/server communication between MiCOM relays and SCADA.
Step 6: Configure SCADA Tags
In your SCADA software:
- Add a new IEC 61850 device.
- Enter the MiCOM relay IP address.
- Browse available data objects from the relay.
- Map:
- Analog values (V, I, P, Q, Frequency)
- Digital signals (Trip, Alarm, Breaker status)
- Save and activate communication.
Once complete, your SCADA should start receiving real-time data from the MiCOM relay.
GOOSE Messaging for Fast Protection
GOOSE (Generic Object Oriented Substation Event) is used for high-speed peer-to-peer communication.
Typical GOOSE Applications
- Interlocking between relays
- Busbar protection schemes
- Transfer trip signals
- Breaker failure logic
Step 7: Configure GOOSE
- In S1 Studio, enable GOOSE Publishing.
- Select signals to publish (Trip, Start, Status).
- Assign:
- VLAN ID (if used)
- GOOSE ID
- In receiving devices or SCADA, subscribe to the GOOSE message.
GOOSE messages operate in milliseconds, making them ideal for protection coordination.
Testing IEC 61850 Communication
Step 8: Communication Verification
✔ Ping Test
From SCADA or engineering PC:
ping 192.168.1.10
Confirms basic network connectivity.
✔ MMS Status
Check in SCADA:
- Device should appear Online
- Data values should update in real time
✔ GOOSE Monitoring
Use:
- S1 Studio GOOSE diagnostics
- Network analyzer (Wireshark) for GOOSE frames
Common Problems & Troubleshooting
❌ No Communication
- Verify IP address and subnet
- Check Ethernet cable and switch port
- Confirm IEC 61850 service is enabled
❌ SCADA Not Reading Data
- CID file not properly loaded
- Data mapping mismatch
- Wrong logical node or dataset
❌ GOOSE Not Working
- VLAN mismatch
- GOOSE ID incorrect
- Network switch not supporting multicast
Best Practices for Reliable IEC 61850 Networks
- Use managed industrial Ethernet switches
- Enable VLANs for GOOSE traffic
- Keep relay firmware updated
- Maintain proper network documentation
- Use standardized naming conventions for datasets
Conclusion
Implementing IEC 61850 communication between MiCOM relay and SCADA enables fast, secure, and interoperable substation automation. By correctly assigning IP addresses, engineering SCL files, configuring MMS and GOOSE, and validating communication, you can integrate Schneider Electric MiCOM relays seamlessly into any modern SCADA system.
This setup not only improves operational visibility but also enhances protection performance and system reliability—making IEC 61850 the backbone of future-ready digital substations.






![Voltage Sag vs Interruption: Causes, Impact, and Fixes A plant can lose a production line from a blink of power, even when the lights come back almost at once. If you've seen a VFD trip, a contactor drop out, or a PLC reset after a split-second dip, you've seen power quality turn into a production problem. The issue is often not a full outage. It's a short voltage event that sensitive equipment can't ride through. Start with the basics, and the failure starts to make sense. What voltage sag and interruption mean A voltage sag is a short drop in RMS voltage below normal, usually to 10% to 90% of rated voltage, for 0.5 cycles up to 1 minute. In a 415 V system, a brief drop to 280 V or 250 V is a sag, not a blackout. Duration matters. If voltage stays low for more than a minute, that is usually undervoltage, not sag. A sag arrives fast, recovers fast, and can still stop a machine. This quick comparison makes the difference easier to see: EventWhat happensTypical durationVoltage sagVoltage drops but does not go to zero0.5 cycles to 1 minuteVoltage interruptionVoltage is zero or near zeroLess than 1 minuteUndervoltageVoltage stays below normal for longerMore than 1 minute An interruption is more severe because supply is lost completely, or almost completely, for less than a minute. If it clears in a few seconds after auto-reclosing, it is a momentary interruption. If it stays off beyond a minute, it becomes a sustained interruption. Why these events happen The most common cause is a fault on the power system. That could be a single line-to-ground fault, line-to-line fault, double line-to-ground fault, or a three-phase fault. When fault current rises, voltage drops across the network until protection clears the problem. If the fault is on your feeder, you may see a sag first and then an interruption when the breaker opens. If the fault is on another feeder from the same substation, your breaker may never trip, but your plant can still see a bus voltage dip. That is why equipment can trip even when "our feeder never opened." Large motor starting is another frequent cause. An induction motor can draw five to seven times full-load current during start. In a weak system, or where the motor is large compared with the transformer, that inrush can create a temporary sag. Transformer energization, capacitor switching, welding loads, arc furnaces, and sudden heavy loading can do the same. Why a tiny dip can stop a large machine > The main motor may ride through a sag, but the control power often won't. Older plants had more electromechanical loads, and many of them tolerated short dips. Modern plants rely on PLCs, VFDs, servo drives, electronic power supplies, sensors, relays, and SCADA. Those devices make automation possible, but many are more sensitive to voltage dips than the motor they control. Massive steel control panels and heavy machinery dominate the floor as overhead lights cast a chaotic, flickering glow. Sharp shadows and sparks suggest a sudden surge in the facility power grid. [https://user-images.rightblogger.com/ai/f382171e-d1b1-4320-b7eb-289d9b53ee27/industrial-factory-power-instability-93e17dc7.jpg] A short sag may not stop a spinning motor because inertia keeps it moving. Still, the contactor coil can drop out, the VFD can detect undervoltage, and the PLC power supply can reset. Once the control chain breaks, the process stops. In process plants, that can mean lost batches, reset time, scrap, labor loss, and delayed delivery. Magnitude and duration both matter. Some equipment can tolerate 80% voltage for five cycles, but not 40% for the same time. That is why ride-through curves matter, and why event recording matters too. Good monitoring tools, such as monitoring power quality with PME 2024 R2 [https://www.interestingautomation.com/schneider-pme-2024-r2/], help capture minimum voltage, duration, and affected phases. Practical ways to reduce voltage sag problems The most cost-effective fix starts with the weak point. If a 200 kW machine trips because a 230 V PLC supply resets, you usually do not need to protect the whole machine. You need to protect the control power. * Specify ride-through performance when buying critical PLCs, drives, relays, and controls. * Add a small UPS, DC backup, or capacitor ride-through module for control power. * Use a voltage sag compensator or dynamic voltage restorer for sensitive process loads. * Apply online UPS systems where transfer time cannot be tolerated. * Consider motor-generator or flywheel systems where short interruptions happen often. * Use static transfer switches only when the two sources are truly independent. Source quality matters too. Utilities reduce events with better protection coordination, faster fault clearing, line maintenance, tree trimming, and feeder automation. On the plant side, grid automation and fault visibility also help, which is why tools for using Easergy T300 for fault detection [https://www.interestingautomation.com/brief-explain-easergy-t300-features-benefits-and-complete-guide/] are relevant in systems that need faster disturbance response. Final thoughts A blink in voltage can do more damage to production than a short outage, because the failure often happens inside the control system before anyone sees a breaker trip. That is the core lesson behind voltage sag and interruption studies. The best fix is rarely the biggest one. Find what actually trips, measure how deep and how long the event lasts, and protect the most sensitive part first. A brief dip should not turn into hours of downtime.](https://www.interestingautomation.com/wp-content/uploads/2026/05/Voltage-Sag-vs-Interruption-Causes-Impact-and-Fixes-150x150.jpg)


