- 1. Introduction
- 2. What Is S1 Agile?
- 3. MiCOM Relays and IEC 61850 Compatibility
- 4. Preparing the Engineering Environment
- 5. Connecting S1 Agile to a MiCOM Relay
- 6. Communication Parameters
- 7. Understanding the IEC 61850 Data Model
- 8. Functional Constraints and Data Attributes
- 9. SCL Files and MiCOM Device Descriptions
- 10. MMS Reporting Configuration
- 11. GOOSE Engineering
- 12. Integrating MiCOM Relays with SICAM PAS
- 13. Practical Example: MiCOM Feeder Relay Engineering
- 14. Wireshark Analysis
- 15. Common Problems and Troubleshooting
- 16. Engineering Best Practices
- 17. Conclusion
- 18. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
S1 Agile is an engineering software environment used for configuring and managing supported Schneider Electric MiCOM protection relays. Depending on the relay family, model, firmware and installed communication options, it can be used to access protection settings, device configuration, communication parameters and other engineering functions.
For engineers working with IEC 61850-based substations, understanding the relationship between MiCOM relay configuration and IEC 61850 communication is essential.
A MiCOM relay may perform its protection functions correctly while still having communication problems with a substation automation system. Incorrect communication settings, mismatched device descriptions, unavailable data objects or improperly configured reporting can prevent successful integration with SCADA.
This article explains the practical engineering considerations when working with IEC 61850-enabled MiCOM relays using S1 Agile.
Topics include:
- S1 Agile and MiCOM relay engineering
- Supported relay families and IEC 61850 capabilities
- Connecting to a MiCOM relay
- Communication parameter configuration
- IP address and Ethernet settings
- IEC 61850 data models
- Logical devices and logical nodes
- SCL and ICD files
- MMS communication
- GOOSE engineering considerations
- Integration with SICAM PAS and other SCADA systems
- Testing and troubleshooting
Important: S1 Agile functions vary according to the relay model, software release and device firmware. Not every MiCOM relay supports IEC 61850, and not every IEC 61850 engineering function is available through S1 Agile. Always consult the relevant device manual and software documentation.
2. What Is S1 Agile?
S1 Agile is an engineering tool for supported MiCOM protection and control devices.
It provides an environment for engineers to work with compatible relays during:
- Protection setting configuration
- Device parameterization
- Configuration management
- Communication setup
- Device maintenance
- Engineering and commissioning
The exact functions depend on the selected relay and its supported software package.
S1 Agile should not be confused with a complete IEC 61850 substation system configurator. Device configuration and system-level IEC 61850 engineering are related activities, but they are not necessarily performed in the same software.
2.1 S1 Agile and IEC 61850 Engineering
In an IEC 61850 project, several engineering activities may be required:
| Engineering activity | Typical purpose |
|---|---|
| Relay configuration | Configure the protection device |
| Communication setup | Configure network and protocol parameters |
| Data model verification | Identify supported logical nodes and data objects |
| SCL engineering | Describe and coordinate IED configuration |
| GOOSE engineering | Configure publisher and subscriber relationships |
| SCADA integration | Map data into the automation system |
| Commissioning | Verify communication and application behaviour |
S1 Agile may support some of these activities for a particular MiCOM device. Other activities may require separate system-level engineering tools.
3. MiCOM Relays and IEC 61850 Compatibility
MiCOM is a broad family of protection and control relays. Different models have different hardware platforms, communication options and protocol capabilities.
Examples of MiCOM families used in protection applications include:
| MiCOM family | Typical application |
|---|---|
| P12x | Overcurrent and earth fault protection |
| P14x | Feeder management and protection |
| P44x | Distance protection |
| P54x | Line differential protection |
| P63x | Transformer differential protection |
| P64x | Transformer protection |
| P74x | Busbar protection |
These are application examples, not a statement that every model or version in each family supports IEC 61850.
Before starting an IEC 61850 project, verify:
- Exact relay model.
- Full order code.
- Communication hardware.
- Firmware version.
- Supported IEC 61850 edition.
- Supported communication services.
- Available logical nodes and data objects.
- Supported SCL file types and engineering workflow.
The relevant documentation may include:
- MICS – Model Implementation Conformance Statement
- PICS – Protocol Implementation Conformance Statement
- PIXIT – Protocol Implementation eXtra Information for Testing
- ICD – IED Capability Description
- Device manuals
- Firmware release notes
These documents are important because two relays from the same product family may not offer identical IEC 61850 functionality.
4. Preparing the Engineering Environment
Before connecting to a relay, prepare the engineering workstation and collect the necessary device information.
4.1 Engineering Preparation
Check the following:
- S1 Agile installation and software version
- Supported device package
- MiCOM relay model
- Relay firmware
- Communication interface
- Required connection cable or Ethernet connection
- Relay configuration backup
- Protection setting files
- Device communication documentation
Always use a software version compatible with the selected relay.
4.2 Backup Before Modification
Before changing an existing relay configuration:
- Identify the relay and its installed firmware.
- Connect using the approved engineering method.
- Read or retrieve the existing configuration where supported.
- Save the original settings and configuration files.
- Record the current communication parameters.
- Obtain authorization before modifying the operational device.
A backup is particularly important when working on an in-service protection system.
5. Connecting S1 Agile to a MiCOM Relay
The connection method depends on the relay hardware and supported communication interfaces.
Possible connection methods include:
- Front communication port
- Rear Ethernet port
- Rear serial communication port
- Engineering communication network
Not every relay supports every connection method.
5.1 Front Port Connection
For devices that support front-port engineering access:
- Connect the workstation using the appropriate cable.
- Confirm the physical connection.
- Open the relevant device project or configuration.
- Select the correct communication method.
- Establish communication.
- Read the device information.
- Confirm that the connected relay matches the intended device.
5.2 Rear Ethernet Connection
For Ethernet-connected devices:
- Check the relay Ethernet interface.
- Confirm its configured IP address.
- Configure the workstation network interface.
- Check subnet compatibility.
- Verify network connectivity.
- Select the appropriate communication method.
- Establish the engineering connection.
A successful ping confirms basic IP connectivity only. It does not prove that the required engineering or IEC 61850 services are available.
6. Communication Parameters
Communication parameters must be configured according to the network design and relay capabilities.
Typical Ethernet parameters include:
| Parameter | Example |
|---|---|
| Relay IP address | 192.168.10.21 |
| Subnet mask | 255.255.255.0 |
| Gateway | 192.168.10.1 |
| Engineering workstation | 192.168.10.100 |
| MMS TCP port | 102 |
These are illustrative values and must be replaced with the project’s approved network settings.
6.1 IP Address Configuration
Each relay must have a unique IP address within the relevant network.
For example:
| Device | IP address |
|---|---|
| SICAM PAS | 192.168.10.10 |
| MiCOM Feeder Relay 1 | 192.168.10.21 |
| MiCOM Feeder Relay 2 | 192.168.10.22 |
| MiCOM Transformer Relay | 192.168.10.23 |
| Engineering Workstation | 192.168.10.100 |
The engineer should also check:
- Subnet mask
- Default gateway
- VLAN assignment
- Switch port configuration
- Routing
- Firewall rules
- Network redundancy requirements
6.2 MMS Communication
IEC 61850 MMS normally operates over TCP port 102.
In a typical SCADA architecture:
- MiCOM relay acts as the MMS server.
- SICAM PAS or another compatible automation system acts as the MMS client.
The client establishes an association and accesses the supported data model and services.
However, communication parameters and service availability must be confirmed for the specific device.
7. Understanding the IEC 61850 Data Model
One of the most important parts of MiCOM IEC 61850 engineering is understanding how relay information is represented.
IEC 61850 uses a structured data model.
IED
|
+-- Logical Device
|
+-- Logical Node
|
+-- Data Object
|
+-- Data Attribute
For example:
MiCOM IED
|
+-- Logical Device
|
+-- MMXU
| |
| +-- Current
| +-- Voltage
| +-- Power
|
+-- PTOC
| |
| +-- Protection information
|
+-- XCBR
|
+-- Circuit breaker information
The diagram illustrates typical IEC 61850 concepts. Actual logical devices, logical nodes and data objects depend on the relay implementation.
7.1 Common Logical Nodes
| Logical Node | Function |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| MMXU | Measurements |
| XCBR | Circuit breaker |
| XSWI | Switch or disconnector |
| CSWI | Switching control |
| PTRC | Protection trip conditioning |
| RREC | Automatic reclosing |
| GGIO | General-purpose input/output |
A logical node may contain several data objects, each with specific attributes and functional constraints.
Do not assume that every listed logical node is implemented in every MiCOM relay.
8. Functional Constraints and Data Attributes
IEC 61850 data attributes are associated with functional constraints.
Common examples include:
| Functional constraint | Meaning |
|---|---|
| ST | Status information |
| MX | Measurements |
| CO | Control |
| SP | Setpoint |
| CF | Configuration |
| DC | Description |
| RP | Unbuffered reporting |
| BR | Buffered reporting |
For example:
- A circuit breaker position is generally status information.
- A current measurement is generally measurement information.
- A supported switching command uses a control object.
The correct functional constraint is important when configuring data references and client access.
8.1 Quality and Timestamp
IEC 61850 data may include:
stVal– Status valueq– Qualityt– Timestamp
Quality indicates the condition of the data, while the timestamp identifies the associated time.
SCADA integration should preserve and correctly interpret these attributes where they are provided.
9. SCL Files and MiCOM Device Descriptions
SCL is the XML-based Substation Configuration Language defined by IEC 61850-6.
The main file types include:
| File | Description |
|---|---|
| ICD | IED Capability Description |
| CID | Configured IED Description |
| IID | Instantiated IED Description |
| SCD | Substation Configuration Description |
| SSD | System Specification Description |
9.1 ICD File
An ICD file describes the capabilities of an IED.
It may contain information about:
- IED identification
- Access points
- Logical devices
- Logical nodes
- Data objects
- Communication capabilities
- Report control blocks
- GOOSE control blocks, where supported
The exact content depends on the device implementation.
9.2 CID File
A CID file describes a configured IED instance.
It can include project-specific configuration information such as:
- IED name
- Communication parameters
- Configured datasets
- Report control blocks
- GOOSE configuration, where applicable
9.3 S1 Agile and SCL Workflow
The availability of SCL import, export and configuration functions depends on the particular MiCOM device and software version.
A typical engineering process may involve:
- Obtaining the correct device description.
- Reviewing the IED data model.
- Performing system-level engineering in a compatible configurator.
- Generating the applicable configured device description.
- Applying the supported configuration to the relay using the documented workflow.
- Verifying the resulting device configuration.
Do not assume that S1 Agile can directly perform every SCL system-engineering operation.
10. MMS Reporting Configuration
MMS reporting allows a MiCOM relay to send selected information to an IEC 61850 client.
The reporting configuration involves:
- Dataset
- Report Control Block
- Trigger options
- Integrity period
- General interrogation
- Buffering behaviour
10.1 Dataset
A dataset is a collection of selected data attributes.
For example, a feeder dataset may contain:
- Circuit breaker position
- Phase current
- Earth fault current
- Protection trip indication
- Relay alarm
- Device health information
The dataset must contain data objects actually supported by the selected relay.
10.2 Report Control Blocks
Two common report types are:
URCB – Unbuffered Report Control Block
Unbuffered reporting does not provide the persistent event buffering associated with BRCB.
BRCB – Buffered Report Control Block
Buffered reporting can retain events during communication interruptions, subject to the available buffer and implementation.
10.3 Reporting Checks
During engineering and commissioning, verify:
- Dataset availability.
- Report control block configuration.
- Client association.
- Report enabling.
- Trigger conditions.
- Integrity reporting.
- Quality and timestamp information.
- Behaviour after communication interruption.
The exact reporting options depend on the MiCOM implementation.
11. GOOSE Engineering
GOOSE is used for fast peer-to-peer communication between compatible IEDs.
Typical applications include:
- Interlocking
- Protection blocking
- Breaker failure signals
- Trip transfer
- Busbar protection signals
- Permissive protection schemes
GOOSE messages use Ethernet multicast communication and are not carried over TCP/IP.
11.1 Publisher and Subscriber
A typical GOOSE arrangement is:
MiCOM Relay A
GOOSE Publisher
|
|
Ethernet Network
|
|
MiCOM Relay B
GOOSE Subscriber
The publisher transmits a dataset through a GOOSE control block. The subscriber receives the message and uses configured external references to associate the received information with its application.
11.2 Important GOOSE Parameters
| Parameter | Function |
|---|---|
| APPID | Application identifier |
| MAC address | Multicast destination |
| VLAN ID | VLAN identification |
| VLAN priority | Ethernet priority |
| Dataset | Published data attributes |
| GoCB | GOOSE control block |
stNum | State number |
sqNum | Sequence number |
confRev | Configuration revision |
The configuration revision relates to the GOOSE configuration, not the relay firmware version.
11.3 SCL-Based GOOSE Engineering
GOOSE engineering normally involves system-level configuration.
The engineer must coordinate:
- Publisher IED
- Subscriber IED
- Dataset
- GOOSE control block
- External references
- Communication parameters
- VLAN and multicast configuration
The supported workflow depends on the relay and system configurator.
11.4 GOOSE Testing
During commissioning:
- Confirm the publisher configuration.
- Confirm the subscriber configuration.
- Verify the Ethernet network.
- Capture GOOSE messages using Wireshark.
- Check APPID and multicast address.
- Verify
stNumandsqNum. - Test the actual subscriber application.
- Verify recovery after communication interruption.
A packet capture showing GOOSE messages does not prove that the subscriber logic is correctly configured.
12. Integrating MiCOM Relays with SICAM PAS
SICAM PAS can act as an IEC 61850 client for supported MiCOM relay servers.
A typical integration process includes:
- Prepare the network.
- Obtain the relay device description.
- Configure the system-level IED representation.
- Identify the required data objects.
- Configure MMS communication.
- Configure datasets and reports.
- Map indications and measurements.
- Configure supported control functions.
- Test the complete SCADA application.
12.1 Example Data Mapping
| SCADA point | Possible IEC 61850 source |
|---|---|
| Feeder current | MMXU measurement |
| Feeder voltage | MMXU measurement |
| Overcurrent trip | Relevant protection logical node |
| Earth fault trip | Relevant protection logical node |
| Breaker position | XCBR |
| Relay alarm | Supported device status or alarm object |
| Frequency | MMXU measurement |
These are functional examples, not universal MiCOM data references.
Always obtain the exact object references from the relay’s documentation and configured data model.
13. Practical Example: MiCOM Feeder Relay Engineering
Consider a MiCOM feeder protection relay connected to a substation Ethernet network.
The required functions are:
- Overcurrent protection
- Earth fault protection
- Circuit breaker status
- Phase current measurement
- Frequency measurement
- Protection trip indications
- MMS communication with SICAM PAS
Step 1: Identify the Device
Record:
- Relay model
- Order code
- Firmware
- Communication hardware
- IEC 61850 capability
- S1 Agile version
Step 2: Establish Engineering Access
Connect to the relay using a supported interface.
Read the existing configuration where supported and save a backup.
Step 3: Verify Communication Parameters
Check:
- IP address
- Subnet mask
- Gateway
- Ethernet interface
- Network connection
Step 4: Review the Data Model
Identify the supported logical devices and logical nodes.
Find the data references for the required measurements, status indications and alarms.
Step 5: Prepare the SCL Configuration
Obtain the applicable ICD or other supported device description.
Perform system-level engineering using a compatible tool where required.
Step 6: Configure SCADA Integration
Configure the SICAM PAS client with the appropriate device information, data mapping and reporting configuration.
Step 7: Test Communication
Check MMS association, data access and report reception.
Step 8: Test the Application
Verify measurements, protection indications, breaker status and alarms against the actual relay behaviour.
14. Wireshark Analysis
Wireshark is a valuable tool for troubleshooting IEC 61850 communication.
Useful display filters include:
| Filter | Application |
|---|---|
tcp.port == 102 | MMS communication |
goose | GOOSE protocol |
eth.type == 0x88b8 | GOOSE Ethernet frames |
tcp.analysis.retransmission | TCP retransmissions |
tcp.flags.reset == 1 | TCP reset packets |
14.1 MMS Analysis
For MMS communication, examine:
- TCP connection establishment
- MMS association
- Read requests
- Read responses
- Reports
- Control requests
- Connection termination
14.2 GOOSE Analysis
For GOOSE communication, examine:
- Source MAC address
- Destination multicast address
- APPID
- VLAN ID
stNumsqNumtimeAllowedToLiveconfRev
Wireshark can identify protocol and network problems, but the final application test must be performed at the IED level.
15. Common Problems and Troubleshooting
| Problem | Possible reason | Recommended action |
|---|---|---|
| S1 Agile cannot connect | Incorrect interface or communication settings | Check connection method and device support |
| Device not recognized | Incorrect software package | Check S1 Agile version and device support |
| Relay IP unreachable | Network configuration error | Check IP, subnet and switch |
| MMS association fails | Client/server configuration mismatch | Check services and device parameters |
| Data objects missing | Incorrect data model assumptions | Verify ICD and device documentation |
| Reports not received | Report configuration issue | Check datasets and report control blocks |
| GOOSE not received | Incorrect publisher/subscriber configuration | Check SCL and Ethernet settings |
| Measurements incorrect | Scaling or unit mismatch | Check data attributes and engineering units |
| Timestamps inconsistent | Time synchronization issue | Check the configured time source |
| Control command rejected | Interlocking or control model mismatch | Check control configuration and operating conditions |
| Configuration cannot be applied | Device or firmware incompatibility | Check the documented configuration workflow |
16. Engineering Best Practices
For reliable IEC 61850 engineering with MiCOM relays:
- Confirm exact model and firmware compatibility.
- Use the correct S1 Agile version.
- Save the original relay configuration.
- Verify communication hardware and network settings.
- Use the actual device data model.
- Obtain the correct ICD or other applicable SCL description.
- Separate device engineering from system-level SCL engineering.
- Configure reporting according to the required SCADA application.
- Verify GOOSE publisher and subscriber relationships.
- Test data quality and timestamps.
- Confirm control behaviour and interlocking.
- Maintain configuration backups and commissioning records.
17. Conclusion
S1 Agile is an important engineering tool for supported MiCOM protection relays. However, successful IEC 61850 integration requires a broader understanding of device capabilities, communication settings, data models and system-level configuration.
Engineers must distinguish between configuring an individual protection relay and engineering the complete IEC 61850 substation system.
The most important practical skills include identifying the correct data references, understanding MMS reporting, configuring supported GOOSE applications, integrating the relay with SICAM PAS or another SCADA platform, and testing the complete communication chain.
A structured engineering approach helps reduce commissioning time and prevents communication and configuration problems in operational substations.
18. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training for protection, control and substation automation engineers.
Relevant training subjects include:
- MiCOM protection relay configuration
- S1 Agile engineering
- IEC 61850 architecture
- MMS communication
- GOOSE configuration and testing
- Logical nodes and data objects
- ICD, CID and SCD files
- SICAM PAS integration
- Wireshark communication analysis
- Protection relay testing and commissioning
Training is available through 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/
