- 1. Introduction
- 2. Understanding MMS Communication in IEC 61850
- 3. MMS Versus GOOSE
- 4. Understanding the IEC 61850 Data Model Used by MMS
- 5. Step 1 – Prepare the MMS Communication Environment
- 6. Step 2 – Verify the MMS Server in the MiCOM Relay
- 7. Step 3 – Establish an MMS Association
- 8. Step 4 – Discover the IEC 61850 Server Data Model
- 9. Step 5 – Test MMS Read Services
- 10. Step 6 – Test MMS Measurement Values
- 11. Step 7 – Configure and Test MMS Datasets
- 12. Step 8 – Test MMS Reporting
- 13. Step 9 – Test General Interrogation
- 14. Step 10 – Test MMS Control Services
- 15. Step 11 – Analyze MMS Communication Using Wireshark
- 16. Step 12 – Common MMS Communication Problems
- 17. MMS Testing Versus GOOSE Testing
- 18. Practical MMS Commissioning Checklist
- 19. Conclusion
- 20. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
MMS (Manufacturing Message Specification) is one of the principal communication services used in IEC 61850-based substation automation systems. It enables communication between protection relays, bay controllers, SCADA systems, gateways and engineering workstations.
In substations equipped with MiCOM protection relays, MMS is commonly used for:
- Reading protection and measurement information
- Monitoring circuit breaker status
- Receiving alarms and events
- Retrieving disturbance and fault-related information where supported
- Receiving buffered and unbuffered reports
- Executing supported remote control operations
- Monitoring IED health and communication status
Unlike GOOSE, which provides fast event-based communication over Ethernet multicast, MMS uses a client-server communication model.
A station-level SCADA system or gateway normally acts as the MMS client, while the MiCOM relay acts as the IEC 61850 server.
This article explains how to test MMS communication in supported MiCOM relays, including connection establishment, data access, reporting, controls, Wireshark analysis and practical commissioning procedures.
Note: The exact MMS services, data model, reporting features and control capabilities depend on the MiCOM relay model, communication hardware, firmware and IEC 61850 implementation. Always check the applicable technical documentation.
2. Understanding MMS Communication in IEC 61850
MMS is an application-layer communication protocol used by IEC 61850 for client-server information exchange.
The IEC 61850 server inside a protection relay exposes its data model to clients.
The client can access supported information through standardized services.
A typical arrangement includes:
- MiCOM protection relay acting as an IEC 61850 server
- SCADA or station gateway acting as an MMS client
- Ethernet communication network
- Engineering workstation for configuration and testing
Typical MMS client-server architecture
MiCOM Protection Relay
IEC 61850 Server
Logical devices · Logical nodes · Data objects
MMS over TCP/IP
TCP port 102 (standard MMS mapping)
Substation Ethernet Network
IP connectivity · Switches · Network security
SCADA / Station Gateway
IEC 61850 Client
Data access · Reports · Controls
The client establishes communication with the server and accesses the information exposed by the relay.
3. MMS Versus GOOSE
MMS and GOOSE are both important IEC 61850 communication services, but they serve different purposes.
| Feature | MMS | GOOSE |
|---|---|---|
| Communication model | Client-server | Publisher-subscriber |
| Transport | TCP/IP | Ethernet multicast |
| Standard port | TCP 102 | EtherType 0x88B8 |
| Main application | Monitoring, reporting and controls | Fast event-based signaling |
| Communication initiation | Client establishes association | Publisher transmits messages |
| Typical use | SCADA integration | Interlocking and protection signaling |
| Data access | Read and supported services | Published datasets |
| Event handling | Reporting services | Event-driven message updates |
For example, a MiCOM feeder relay may use MMS to send breaker status and protection alarms to SCADA, while GOOSE is used to transmit a blocking signal to another protection relay.
Both services can operate simultaneously over the substation Ethernet network.
4. Understanding the IEC 61850 Data Model Used by MMS
Before testing MMS, engineers must understand how the relay’s information is organized.
IEC 61850 uses a hierarchical data model.
IEC 61850 data model
IED
MiCOM protection relay
Logical Device (LD)
Protection / measurement / control
Logical Node (LN)
PTOC · PDIS · PTRC · XCBR · MMXU
Data Object (DO)
Op · Pos · A · PhV
Data Attribute (DA)
stVal · q · t · mag · units
For example, a circuit breaker position may be represented using the XCBR logical node and its Pos data object.
The data object can contain attributes such as:
stVal– status valueq– qualityt– timestamp
The exact data reference depends on the relay’s IEC 61850 data model.
4.1 Functional constraints
Functional constraints define the purpose of data attributes.
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 |
When troubleshooting MMS data access, it is important to identify the correct functional constraint.
A data attribute may exist in the relay’s model but not be available through the particular service or access method being tested.
5. Step 1 – Prepare the MMS Communication Environment
Before testing MMS communication, confirm the network and device configuration.
Check the following:
- MiCOM relay IP address
- SCADA or engineering workstation IP address
- Subnet mask
- Gateway, where applicable
- Ethernet connection
- Relay IEC 61850 server configuration
- Client communication configuration
- Firewall and network access rules
Example network configuration
| Device | IP address |
|---|---|
| MiCOM Feeder Relay 1 | 192.168.10.11 |
| MiCOM Feeder Relay 2 | 192.168.10.12 |
| Station Gateway | 192.168.10.100 |
| Engineering Workstation | 192.168.10.200 |
These are illustrative addresses only.
The actual network addressing must follow the approved substation design.
Check basic connectivity
From the engineering workstation, test the relay’s IP connectivity using the operating system’s network diagnostic tools.
For example:
ping 192.168.10.11
A successful ping confirms basic IP reachability, but it does not prove that the MMS server is operational.
The engineer must also verify the TCP connection and IEC 61850 services.
6. Step 2 – Verify the MMS Server in the MiCOM Relay
The MiCOM relay must have its IEC 61850 server communication correctly configured.
Depending on the product, the relevant configuration may include:
- IEC 61850 communication enablement
- Network interface configuration
- Server access parameters
- IED name
- Logical device configuration
- Supported data model
- Reporting configuration
- Control model configuration
Check the relay’s communication status and available diagnostics.
If the relay supports communication monitoring, inspect relevant indications and diagnostic records.
The server must be active and accessible before an MMS client can establish a connection.
7. Step 3 – Establish an MMS Association
An MMS client must establish communication with the IEC 61850 server.
The process generally involves several stages:
- Establish IP connectivity.
- Establish a TCP connection to the MMS service.
- Establish the required lower-layer communication associations.
- Exchange application-level association information.
- Establish the MMS association.
- Access the IEC 61850 server model.
MMS over the IEC 61850 standard mapping commonly uses TCP port 102.
Wireshark filter for MMS communication
Use the following display filter:
tcp.port == 102
This allows the engineer to inspect traffic associated with the standard MMS TCP port.
Check:
- TCP connection establishment
- TCP connection termination
- Connection resets
- Retransmissions
- Unexpected disconnections
- Application association traffic, where decoded
A TCP connection alone does not confirm a successful MMS association. The application-level communication must also be established.
8. Step 4 – Discover the IEC 61850 Server Data Model
After communication is established, the client needs to identify the server’s available information.
IEC 61850 provides services for discovering the server model.
Depending on the client and server implementation, these include:
- Server directory
- Logical device directory
- Logical node directory
- Data object directory
- Data attribute directory
- Data set directory
- Report control block directory
For example, an IEC 61850 client may discover that a MiCOM relay contains logical nodes associated with:
- Protection
- Measurement
- Circuit breaker control
- Device health
- Generic indications
The available model should be compared with the applicable MICS and ICD documentation.
A common troubleshooting mistake is assuming that every logical node described in the IEC 61850 standard must be available in every MiCOM relay.
The actual implementation must be verified.
9. Step 5 – Test MMS Read Services
Reading information is one of the most common MMS applications.
A client can read supported data attributes from the relay’s IEC 61850 server.
Typical information includes:
- Circuit breaker position
- Protection start indications
- Protection trip indications
- Current measurements
- Voltage measurements
- Frequency
- Alarm information
- Device health
Example: Reading circuit breaker position
The client accesses the circuit breaker logical node and reads the relevant position data object.
A simplified conceptual reference might look like:
IED_NAMELD0/XCBR1.Pos.stVal
This is an illustrative IEC 61850-style reference, not a guaranteed MiCOM data reference.
The actual logical device name, logical node instance and data object structure must be obtained from the relay’s data model.
Verify the quality attribute
When reading status information, engineers should not inspect only the status value.
The quality attribute q is also important.
It can indicate whether the information is valid, questionable, invalid or affected by other quality conditions.
The timestamp t may also be relevant when assessing the freshness of the information.
For reliable SCADA integration, status, quality and timestamp behavior should be considered together.
10. Step 6 – Test MMS Measurement Values
MiCOM relays may expose measurements through logical nodes such as MMXU, depending on the model and implementation.
Typical measurements include:
- Phase currents
- Phase voltages
- Active power
- Reactive power
- Apparent power
- Frequency
- Power factor
For example, a current measurement may be represented through a measurement logical node and an appropriate data object.
A measurement commonly includes:
- Magnitude
- Quality
- Timestamp
- Unit and scaling information, where provided
Measurement verification
Compare the values reported by MMS against:
- Relay front-panel measurements.
- Engineering software measurements.
- Secondary injection test values.
- Expected primary or secondary quantities after considering CT and VT ratios.
A mismatch may result from incorrect scaling, incorrect data mapping, CT/VT configuration or a misunderstanding of the measurement reference.
Do not assume that the MMS value is always displayed in the same units as the relay’s front panel.
11. Step 7 – Configure and Test MMS Datasets
A dataset is a collection of IEC 61850 data references.
Datasets are commonly used by report control blocks to define which information is sent to a client.
For example, a feeder relay dataset may include:
| Information | Example logical node |
|---|---|
| Overcurrent start | PTOC |
| Earth fault indication | Supported protection LN |
| Protection trip | PTRC |
| Circuit breaker position | XCBR |
| Current measurement | MMXU |
| Relay health | Device-specific data model |
The engineer should check:
- Dataset name
- Dataset members
- Valid data references
- Functional constraints
- Supported reporting services
- Client compatibility
When a client reads a dataset, verify that the returned values correspond to the intended data attributes.
12. Step 8 – Test MMS Reporting
Reporting is one of the most important MMS functions in substation SCADA integration.
Instead of continuously polling every data point, the client can receive reports when configured conditions occur.
IEC 61850 provides two important types of report control blocks.
12.1 URCB – Unbuffered Report Control Block
An unbuffered report control block is used to send reports while the client is connected and reporting is enabled.
It does not provide the same persistent event buffering behavior as a BRCB.
If the client disconnects, events occurring during the interruption may not be available later through that unbuffered reporting mechanism.
12.2 BRCB – Buffered Report Control Block
A buffered report control block supports buffering of reports according to the server’s implementation.
This can help preserve event information during temporary communication interruptions.
When the client reconnects, it may retrieve buffered information according to the configured reporting and buffer behavior.
12.3 Important report control parameters
| Parameter | Purpose |
|---|---|
| RptID | Report identifier |
| DatSet | Associated dataset |
| BufTm | Buffer time |
| TrgOps | Trigger options |
| IntgPd | Integrity period |
| OptFlds | Optional report fields |
| RptEna | Report enable state |
| Resv | Reservation behavior, where supported |
The exact set of supported parameters depends on the relay and its IEC 61850 implementation.
12.4 Report trigger options
Reporting may be triggered by different conditions, including:
- Data change
- Quality change
- Data update
- Integrity period
- General interrogation
A practical SCADA test should verify that the required triggers operate correctly.
12.5 Practical reporting test
Consider a feeder relay connected to a station-level SCADA system.
The engineer wants to receive circuit breaker position changes and protection trip indications.
The test procedure is:
- Confirm the required dataset.
- Verify the report control block.
- Establish the MMS association.
- Enable reporting from the client.
- Change the relevant signal under an approved test condition.
- Confirm that the report is received.
- Check the reported data value.
- Check quality and timestamp information.
- Verify the report identifier and dataset.
- Repeat for the required events.
13. Step 9 – Test General Interrogation
General interrogation (GI) is used to request the current values of the relevant data associated with reporting.
It is useful when the client establishes communication or needs to synchronize its process image with the server.
For example, after a SCADA gateway reconnects to a MiCOM relay, it may perform general interrogation to obtain the current breaker position and protection status.
The test should verify:
- GI request is accepted.
- Expected data is returned.
- Current values are correct.
- Quality information is available as expected.
- No required points are missing.
The exact GI support and behavior must be checked against the server and client implementation.
14. Step 10 – Test MMS Control Services
IEC 61850 supports different control models for operating controllable objects.
A MiCOM relay may expose supported control objects for functions such as:
- Circuit breaker operation
- Disconnector operation
- Other configured switching functions
The control model must be checked for the specific object and relay.
Common control models include:
| Control model | General description |
|---|---|
| Status-only | Object is monitored but not controlled through that control service |
| Direct control with normal security | Direct operation using the configured control procedure |
| SBO with normal security | Select Before Operate with normal security |
| Direct control with enhanced security | Direct operation with enhanced security |
| SBO with enhanced security | Select Before Operate with enhanced security |
The actual supported models and command behavior depend on the implementation.
14.1 Direct control
With direct control, the client issues the control operation according to the configured control model.
14.2 Select Before Operate (SBO)
With Select Before Operate, the client first selects the object and then issues the operate command.
This can help reduce the risk of unintended operations.
Enhanced-security control models include additional checks and status handling compared with normal-security models.
14.3 Practical control test
For a breaker control application, verify:
- Correct control object reference.
- Correct control model.
- Client permission and authorization.
- Select operation, if required.
- Operate command.
- Command termination and response.
- Breaker position feedback.
- Indication of failed or rejected commands.
Safety note: Do not perform live breaker operations without an approved switching program, authorization, operational coordination and the required safety precautions. Commissioning tests should use an approved test arrangement.
15. Step 11 – Analyze MMS Communication Using Wireshark
Wireshark can help engineers diagnose communication problems between the MiCOM relay and the MMS client.
Useful display filters include:
MMS TCP traffic
tcp.port == 102
TCP connection resets
tcp.flags.reset == 1
TCP retransmissions
tcp.analysis.retransmission
Depending on the Wireshark version and enabled protocol dissectors, MMS-related protocol layers may be displayed in decoded form.
The engineer can investigate:
- TCP connection establishment
- MMS association attempts
- Client requests
- Server responses
- Reporting traffic
- Connection interruptions
- Retransmissions and resets
Not every packet capture will contain fully decoded MMS application information. This can depend on the protocol mapping, capture completeness and decoder support.
16. Step 12 – Common MMS Communication Problems
| Problem | Possible cause | Recommended check |
|---|---|---|
| No connection to relay | IP or network problem | Check IP configuration and connectivity |
| TCP connection failure | Port blocked or server unavailable | Check TCP port 102 and server status |
| MMS association rejected | Application configuration mismatch | Review association and client settings |
| Data object not found | Incorrect data reference | Check MICS and server model |
| Read request fails | Unsupported service or access restriction | Check implementation and permissions |
| Measurement incorrect | Scaling or mapping issue | Compare with relay and test values |
| Reports not received | RCB or client configuration problem | Check dataset, RCB and enable state |
| Buffered events missing | Buffer or reservation behavior | Check BRCB configuration and client handling |
| Control command rejected | Wrong control model or authorization | Check object configuration and access |
| Intermittent communication | Network or server instability | Inspect packet captures and diagnostics |
16.1 MMS association failure
If the client cannot establish an MMS association, investigate the problem in stages:
- Confirm the relay is powered and operational.
- Check the Ethernet link.
- Verify the IP address.
- Check TCP port 102 connectivity.
- Confirm that the IEC 61850 server is enabled.
- Review client configuration.
- Check any security or access restrictions.
- Examine the packet capture.
This approach helps separate network problems from application-level configuration problems.
16.2 Data object not available
A data object may be unavailable because:
- It is not implemented by the relay.
- The logical device name is incorrect.
- The logical node instance is different.
- The data object reference is incorrect.
- The required functional constraint is wrong.
- The requested service is not supported.
Always use the actual device data model rather than assuming a standard logical node or object is implemented.
16.3 Reporting does not work
If the relay responds to MMS read requests but does not send reports, check:
- Report control block configuration
- Dataset membership
- Report enable state
- Trigger options
- Client association
- Client reservation, where relevant
- Buffer behavior
- Supported report features
The fact that data can be read does not prove that reporting is configured correctly.
17. MMS Testing Versus GOOSE Testing
Both MMS and GOOSE should be included in IEC 61850 commissioning, but their testing procedures are different.
| Test activity | MMS | GOOSE |
|---|---|---|
| Basic network test | IP and TCP connectivity | Ethernet multicast delivery |
| Communication setup | Client-server association | Publisher transmission and subscriber reception |
| Data verification | Read data attributes | Inspect published dataset |
| Event verification | Reports | GOOSE state changes |
| Control verification | Supported control services | Application mapping and logic |
| Packet capture | TCP port 102 | EtherType 0x88B8 |
| Main troubleshooting focus | Association, services, datasets and reports | Multicast, VLAN, mapping and supervision |
An IEC 61850 commissioning plan should cover both services where they are used in the project.
18. Practical MMS Commissioning Checklist
Device and network preparation
- Confirm MiCOM model and firmware.
- Check the applicable IEC 61850 documentation.
- Verify relay IP address.
- Verify client IP address.
- Confirm Ethernet connectivity.
- Confirm MMS server availability.
- Check TCP port 102 connectivity.
Data model testing
- Establish MMS association.
- Discover server directory.
- Discover logical devices.
- Discover logical nodes.
- Verify data object references.
- Test data attribute reads.
- Verify quality and timestamp.
Reporting testing
- Verify datasets.
- Verify report control blocks.
- Test URCB where used.
- Test BRCB where used.
- Verify trigger options.
- Test general interrogation.
- Test event reporting.
- Test recovery after communication interruption.
Control testing
- Verify controllable object references.
- Confirm supported control model.
- Check authorization.
- Test selection and operation where applicable.
- Verify command response.
- Confirm actual feedback.
Documentation
- Save packet captures.
- Record test results.
- Document communication parameters.
- Record any configuration changes.
- Archive approved SCL files and relay configurations.
19. Conclusion
MMS testing is essential for verifying IEC 61850 client-server communication between MiCOM protection relays and station-level systems.
A complete MMS commissioning process should verify basic network connectivity, association establishment, server data model discovery, data access, measurement values, reporting, general interrogation and supported control services.
Wireshark provides useful evidence of network-level communication, while IEC 61850 client tools and relay diagnostics help verify the actual application services.
The most important principle is to test the complete communication function rather than relying only on a successful TCP connection or a successful data read.
By following a structured procedure, engineers can identify configuration errors, improve SCADA integration and ensure that the IEC 61850 communication functions operate according to the project requirements.
20. 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 protection relay engineering
- IEC 61850 architecture and data modeling
- MMS client-server communication
- IEC 61850 data access and reporting
- Buffered and unbuffered report control blocks
- General interrogation
- IEC 61850 control models
- GOOSE publishing and subscription
- SCL, ICD, CID and SCD files
- 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.
