- 1. Introduction
- 2. Understanding Logical-Node Mapping
- 3. PTOC – Time Overcurrent Protection
- 4. PIOC – Instantaneous Overcurrent Protection
- 5. PDIS – Distance Protection
- 6. PDIF – Differential Protection
- 7. PTRC – Protection Trip Conditioning
- 8. MMXU – Electrical Measurements
- 9. XCBR – Circuit Breaker
- 10. CSWI – Switching Control
- 11. RREC – Automatic Reclosing
- 12. GGIO – Generic Process I/O
- 13. Practical Logical-Node Mapping Table
- 14. Practical Example: MiCOM Feeder Relay SCADA Mapping
- 15. Logical-Node Mapping for Different MiCOM Applications
- 16. Testing Logical Nodes During Commissioning
- 17. Common Logical-Node Mapping Mistakes
- 18. Conclusion
- 19. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
IEC 61850 logical nodes provide a standardized way to represent protection, control, measurement and monitoring functions inside Intelligent Electronic Devices (IEDs).
For engineers working with MiCOM protection relays, understanding logical-node mapping is essential for integrating protection functions with SCADA systems, configuring MMS reporting, engineering GOOSE communication and performing IEC 61850 commissioning.
A MiCOM relay may contain several protection functions, such as:
- Phase overcurrent protection
- Earth fault protection
- Instantaneous overcurrent protection
- Distance protection
- Line differential protection
- Transformer differential protection
- Circuit breaker control
- Automatic reclosing
- Electrical measurements
IEC 61850 represents these functions using standardized logical-node classes.
This article explains the most relevant logical nodes used in protection applications and how engineers can identify and map them in MiCOM relays.
The main logical nodes covered are:
- PTOC – Time Overcurrent Protection
- PIOC – Instantaneous Overcurrent Protection
- PDIS – Distance Protection
- PDIF – Differential Protection
- PTRC – Protection Trip Conditioning
- MMXU – Measurement
- XCBR – Circuit Breaker
- CSWI – Switching Control
- RREC – Automatic Reclosing
- GGIO – Generic Input/Output
Important: These are standard logical-node classes and typical application examples. The actual implementation, instances, data objects and attributes vary according to MiCOM model, firmware and IEC 61850 configuration. Never assume that every listed logical node is present in every relay.
2. Understanding Logical-Node Mapping
A logical node represents a standardized functional element in an IEC 61850 data model.
For example, a feeder protection relay may use:
| Protection or equipment function | Typical logical node |
|---|---|
| Time overcurrent protection | PTOC |
| Instantaneous overcurrent protection | PIOC |
| Distance protection | PDIS |
| Differential protection | PDIF |
| Protection trip conditioning | PTRC |
| Electrical measurements | MMXU |
| Circuit breaker | XCBR |
| Switching control | CSWI |
| Automatic reclosing | RREC |
| General-purpose signals | GGIO |
The logical node is not necessarily identical to the physical protection function implemented in the relay.
For example, a relay may have several overcurrent stages, but the way those stages are represented in its IEC 61850 data model depends on the manufacturer’s implementation.
The engineer must therefore understand both:
- The protection function inside the relay.
- The IEC 61850 representation of that function.
3. PTOC – Time Overcurrent Protection
Protection logical node
PTOC represents time overcurrent protection.
It is relevant to feeder protection applications where phase or earth fault current is monitored against configured protection characteristics.
Typical applications include:
- Phase overcurrent protection
- Earth fault overcurrent protection
- Definite-time overcurrent protection
- Inverse-time overcurrent protection
- Backup overcurrent protection
3.1 Typical PTOC Information
Depending on the implementation, PTOC may provide information relating to:
- Protection start
- Protection operation
- Protection settings
- Pickup values
- Time-delay settings
- Directional characteristics, where applicable
Common data-object names include:
| Data object | General meaning |
|---|---|
| Str | Start information |
| Op | Operation information |
| StrVal | Start value |
| OpDlTm | Operation delay time |
| StrValA | Start value for phase A, where implemented |
These are examples of standard data-object concepts, not a guaranteed list for a particular MiCOM relay.
3.2 Practical Example: MiCOM Feeder Protection
Consider a feeder protected by a MiCOM relay with phase overcurrent protection.
The relay detects a phase fault and the overcurrent function starts.
A typical functional sequence is:
Phase Fault
|
v
Current Measurement
|
v
Overcurrent Protection
|
v
PTOC Start
|
v
PTOC Operation
|
v
Trip Conditioning
The associated IEC 61850 information may be mapped into SICAM PAS to provide:
- Overcurrent start indication
- Overcurrent trip indication
- Protection event information
The exact object references must be obtained from the relay’s data model.
4. PIOC – Instantaneous Overcurrent Protection
Protection logical node
PIOC represents instantaneous overcurrent protection.
It is commonly associated with high-set or instantaneous overcurrent stages.
Typical applications include:
- High-set phase overcurrent protection
- Instantaneous earth fault protection
- Fast fault clearance
- Short-circuit protection
4.1 PTOC and PIOC Differences
| Feature | PTOC | PIOC |
|---|---|---|
| General function | Time overcurrent | Instantaneous overcurrent |
| Time characteristic | May include a time delay or inverse characteristic | Represents instantaneous protection behaviour |
| Typical application | Feeder overcurrent | High-set short-circuit protection |
| IEC 61850 class | PTOC | PIOC |
The distinction between the two logical nodes is important when mapping protection indications.
4.2 Practical Example
A feeder relay may have:
- Low-set overcurrent stage
- High-set overcurrent stage
- Earth fault stage
- High-set earth fault stage
The relay’s IEC 61850 data model may represent these functions using separate logical-node instances or another implementation-specific arrangement.
Do not assume that every stage has a separate logical node. Check the device documentation and online data model.
5. PDIS – Distance Protection
Protection logical node
PDIS represents distance protection.
It is particularly relevant to MiCOM distance relays used for transmission and sub-transmission line protection.
Typical applications include:
- Phase-to-phase fault protection
- Phase-to-earth fault protection
- Zone 1 protection
- Zone 2 protection
- Zone 3 protection
- Directional distance protection
- Backup distance protection
5.1 Distance Protection Information
Depending on the relay implementation, distance protection information may include:
- Protection start
- Zone operation
- Protection trip
- Directional information
- Fault-loop information
- Protection settings
5.2 Practical Example: MiCOM P44x
Consider a MiCOM P44x distance protection relay.
The relay detects a line fault and determines the apparent impedance.
Depending on the measured impedance and configured zone characteristics, a protection zone may operate.
A simplified functional representation is:
Line Fault
|
v
Voltage and Current Measurement
|
v
Impedance Calculation
|
v
Distance Protection
|
v
PDIS Information
|
v
Protection Trip Logic
The IEC 61850 data model may expose distance protection information through PDIS and associated protection logical nodes.
The actual zone representation and available data objects must be verified for the selected P44x model and firmware.
5.3 SCADA Mapping
A control centre may require indications such as:
- Distance protection start
- Zone 1 operation
- Zone 2 operation
- Zone 3 operation
- Distance trip
The engineer must identify the corresponding implemented references rather than assume that every zone has a standard, separately exposed data object.
6. PDIF – Differential Protection
Protection logical node
PDIF represents differential protection.
It is relevant to protection schemes where currents entering and leaving a protected zone are compared.
Typical applications include:
- Transformer differential protection
- Line differential protection
- Other differential protection applications supported by the IED
6.1 Differential Protection Information
Depending on the relay, the data model may include information relating to:
- Differential protection start
- Differential protection operation
- Differential current
- Restraint current
- Differential protection status
- Protection blocking
Not all these quantities are necessarily represented through PDIF in every implementation.
6.2 Practical Example: Transformer Differential Protection
Consider a transformer protected by a MiCOM differential relay.
The relay compares the compensated currents from the transformer sides.
Under normal load or external fault conditions, the differential protection remains stable.
For an internal fault, the differential protection may operate.
Transformer Side 1 Current
|
v
Current Compensation
|
|
v
Differential Relay
^
|
Current Compensation
^
|
Transformer Side 2 Current
|
v
Differential Protection
|
v
PDIF
|
v
Trip Conditioning
6.3 SCADA Information
Typical SCADA requirements may include:
- Differential protection start
- Differential protection trip
- Transformer differential alarm
- Protection blocked indication
The precise logical-node mapping depends on the relay’s data model.
7. PTRC – Protection Trip Conditioning
Protection logical node
PTRC represents protection trip conditioning.
It is important because several protection functions may contribute to the final trip decision.
For example:
- Overcurrent protection
- Earth fault protection
- Distance protection
- Differential protection
- Breaker failure protection
PTRC provides a standardized representation of protection trip conditioning information.
7.1 Protection Trip Architecture
A simplified example:
PTOC
|
PDIS
|
PDIF
|
v
PTRC
|
v
Circuit Breaker Trip
This is a conceptual protection architecture. Actual internal logic and signal routing depend on the relay application and configuration.
7.2 Why PTRC Is Important
It helps distinguish between an individual protection function operating and the overall trip conditioning function.
For example:
- PTOC may indicate that overcurrent protection has operated.
- PDIS may indicate that distance protection has operated.
- PTRC may represent the associated protection trip conditioning.
This distinction is useful for SCADA mapping, event analysis and commissioning.
8. MMXU – Electrical Measurements
Measurement logical node
MMXU represents electrical measurement information.
It is one of the most important logical nodes for SCADA integration.
Typical measurements include:
- Phase currents
- Phase voltages
- Active power
- Reactive power
- Apparent power
- Frequency
- Power factor
8.1 Common MMXU Data Objects
| Data object | General meaning |
|---|---|
| A | Current |
| PhV | Phase voltage |
| PPV | Phase-to-phase voltage |
| W | Active power |
| VAr | Reactive power |
| VA | Apparent power |
| Hz | Frequency |
| PF | Power factor |
These are common IEC 61850 data-object names. Their availability depends on the actual MiCOM implementation.
8.2 Example: Current Measurement Mapping
A conceptual measurement reference may be structured as:
IED
|
+-- Logical Device
|
+-- MMXU1
|
+-- A
|
+-- phsA
+-- phsB
+-- phsC
The measurement attributes may include a magnitude, quality and timestamp.
8.3 Measurement Verification
During commissioning, compare:
- Relay front-panel measurement
- IEC 61850 client reading
- SICAM PAS value
- SCADA display value
Check engineering units, scaling, data quality and timestamps.
9. XCBR – Circuit Breaker
Switchgear logical node
XCBR represents circuit breaker information.
It is particularly important for substation control and monitoring.
Typical information includes:
- Breaker position
- Breaker operating status
- Breaker-related supervision information
- Supported circuit breaker control information
9.1 Circuit Breaker Position
A circuit breaker may have the following states:
- Open
- Closed
- Intermediate or indeterminate
- Bad-state or invalid information
IEC 61850 double-point status representation may be used for position information, depending on the implementation.
The engineer must correctly interpret the status encoding and quality.
9.2 Breaker Control
XCBR is associated with circuit breaker information and control-related data.
Switching control is commonly represented through CSWI.
A simplified relationship is:
CSWI
Switching Control
|
v
XCBR
Circuit Breaker
|
v
Position Feedback
The exact control architecture depends on the IED implementation.
10. CSWI – Switching Control
CSWI represents switching control functionality.
It is relevant to control operations such as:
- Circuit breaker opening
- Circuit breaker closing
- Switching device operation
A control application may use direct control or Select Before Operate, depending on the supported IEC 61850 control model.
10.1 Example Control Sequence
SCADA Operator
|
v
SICAM PAS
|
v
CSWI
|
v
Interlocking
|
v
XCBR
|
v
Circuit Breaker
|
v
Position Feedback
This is a simplified functional illustration. Actual interlocking and control logic must be verified in the relay configuration.
10.2 Important Control Checks
Before enabling remote control, verify:
- Local/remote selection
- Interlocking conditions
- Control model
- Command termination
- Circuit breaker feedback
- Operational authorization
- Applicable switching procedures
11. RREC – Automatic Reclosing
RREC represents automatic reclosing functionality.
It is relevant to overhead line protection applications where automatic reclosing is used.
Typical functions include:
- Reclosing initiation
- Reclosing sequence
- Dead time
- Reclaim time
- Reclosing status
- Reclosing lockout
11.1 Practical Example
Consider a feeder with an automatic reclosing function.
After a protection trip, the relay may initiate an automatic reclosing sequence according to the configured protection logic.
A simplified sequence is:
Protection Trip
|
v
Reclosing Initiation
|
v
Dead Time
|
v
Circuit Breaker Close Command
|
v
Breaker Status Verification
|
v
Reclaim or Lockout
The actual sequence depends on the relay configuration and the protection scheme.
RREC may expose relevant automatic reclosing information to SCADA, depending on the implementation.
12. GGIO – Generic Process I/O
GGIO represents general-purpose input/output information.
It can be used to model signals that do not fit naturally into more specific standardized logical-node classes.
Examples may include:
- General alarms
- External binary inputs
- Auxiliary signals
- User-defined status indications
- Selected process information
12.1 Practical Example
A MiCOM relay may have an auxiliary input assigned to an external alarm.
Where supported, this signal may be represented through a suitable generic I/O logical node.
The engineer should check the actual mapping and data-object structure rather than assuming all binary inputs appear under GGIO.
13. Practical Logical-Node Mapping Table
The following table provides a useful starting point for MiCOM IEC 61850 engineering.
| Application | Logical node | Typical information |
|---|---|---|
| Time overcurrent | PTOC | Start and operation |
| Instantaneous overcurrent | PIOC | Start and operation |
| Distance protection | PDIS | Distance protection status |
| Differential protection | PDIF | Differential protection information |
| Protection trip | PTRC | Trip conditioning information |
| Measurements | MMXU | Current, voltage and power |
| Circuit breaker | XCBR | Breaker status |
| Switching control | CSWI | Switching commands |
| Automatic reclosing | RREC | Reclosing status |
| General I/O | GGIO | Auxiliary signals |
| Device information | LPHD | Physical device information |
| Common logical-device information | LLN0 | Logical device common functions |
This table is intended as an engineering reference. It does not represent a universal data model for all MiCOM devices.
14. Practical Example: MiCOM Feeder Relay SCADA Mapping
Consider a MiCOM feeder relay connected to SICAM PAS.
The control centre requires:
- Feeder phase current.
- Feeder voltage.
- Circuit breaker position.
- Overcurrent start.
- Overcurrent trip.
- Earth fault trip.
- Automatic reclosing status.
- Relay alarm.
A practical mapping worksheet could look like this:
| SCADA point | Logical node | Data object | Required verification |
|---|---|---|---|
| Phase current | MMXU | A | Scaling and quality |
| Feeder voltage | MMXU | PhV or PPV | Unit and phase mapping |
| Breaker position | XCBR | Pos | State interpretation |
| Overcurrent start | PTOC | Str | Start indication |
| Overcurrent operation | PTOC | Op | Operation indication |
| Earth fault trip | Applicable protection LN | Device-specific | Exact mapping |
| Reclosing status | RREC | Device-specific | Reclosing implementation |
| Relay alarm | Device status or GGIO | Device-specific | Alarm mapping |
14.1 Engineering Workflow
- Identify the relay model and firmware.
- Obtain its MICS, PICS, PIXIT and applicable SCL files.
- Identify the available logical devices.
- Review the logical nodes.
- Locate the required data objects.
- Confirm data attributes and functional constraints.
- Prepare the SCADA point list.
- Configure MMS reporting where supported.
- Test each signal against the actual relay.
- Record the final data references.
15. Logical-Node Mapping for Different MiCOM Applications
Different protection applications require different combinations of logical nodes.
15.1 Feeder Protection
Typical logical-node classes may include:
- PTOC
- PIOC
- MMXU
- XCBR
- CSWI
- PTRC
- GGIO
15.2 Distance Protection
Typical logical-node classes may include:
- PDIS
- PTOC
- PIOC
- PTRC
- RREC
- MMXU
- XCBR
- CSWI
15.3 Transformer Protection
Typical logical-node classes may include:
- PDIF
- PTOC
- PIOC
- PTRC
- MMXU
- XCBR
- CSWI
- GGIO
15.4 Line Differential Protection
Typical logical-node classes may include:
- PDIF
- PTOC
- PIOC
- PTRC
- MMXU
- XCBR
- CSWI
These lists are functional examples, not confirmed inventories for every MiCOM relay. Actual logical-node support and data representation must be established from the relevant device documentation.
16. Testing Logical Nodes During Commissioning
Logical-node mapping should be verified through actual device communication and functional testing.
16.1 Data Model Discovery
Use a compatible IEC 61850 client or engineering tool to:
- Establish communication with the relay.
- Discover logical devices.
- Identify logical nodes.
- Read available data objects.
- Check supported attributes.
- Verify data types and functional constraints.
16.2 Protection Function Testing
For a feeder protection relay:
- Apply the appropriate secondary injection test.
- Verify overcurrent pickup.
- Check the PTOC start information, where implemented.
- Verify protection operation.
- Check the corresponding operation indication.
- Verify trip conditioning information.
- Confirm the circuit breaker status.
- Check event timestamps and quality.
16.3 SCADA Verification
Confirm that SICAM PAS receives the correct values and indications.
Check that:
- Measurements are correctly scaled.
- Protection indications are correctly described.
- Circuit breaker position is interpreted correctly.
- Alarm priorities are appropriate.
- Quality information is handled.
- Event timestamps are consistent.
17. Common Logical-Node Mapping Mistakes
| Mistake | Consequence | Recommended action |
|---|---|---|
| Assuming every MiCOM relay has the same LNs | Missing data points | Verify the exact device model |
| Confusing protection start and trip | Incorrect SCADA alarms | Map separate functional states |
| Using the wrong LN instance | Data access failure | Check the actual reference |
| Mapping measurements as status values | Incorrect data type | Verify CDC and FC |
| Ignoring quality | Invalid values appear valid | Map quality correctly |
| Ignoring timestamps | Incorrect event sequence | Preserve time information |
| Assuming XCBR and CSWI are interchangeable | Incorrect control engineering | Understand their separate roles |
| Assuming all protection stages have separate LNs | Incorrect point mapping | Review the manufacturer’s implementation |
18. Conclusion
IEC 61850 logical nodes provide a standardized structure for representing protection, measurement and switching functions in MiCOM relays.
Understanding PTOC, PIOC, PDIS, PDIF, PTRC, MMXU, XCBR, CSWI, RREC and GGIO helps engineers identify the information required for SCADA integration, protection monitoring, reporting and control.
However, standard logical-node definitions do not guarantee identical implementation across different MiCOM relays.
For successful engineering, always verify the actual logical devices, logical-node instances, data objects, attributes and functional constraints using the relay documentation and online data model.
This approach provides a reliable foundation for IEC 61850 configuration, testing and commissioning.
19. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM relays and substation automation.
Relevant training topics include:
- MiCOM protection relay engineering
- IEC 61850 architecture
- Logical nodes and data objects
- Protection function mapping
- MMS communication and reporting
- GOOSE configuration and testing
- ICD, CID and SCD files
- SICAM PAS integration
- Wireshark communication analysis
- Protection 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/
