NARI IEC 61850 Engineering

NARI IEC 61850 Engineering: Complete Guide to Communication Architecture, Logical Nodes, MMS, GOOSE, SCL Configuration, Testing and Commissioning

Table Of Contents
  1. 1. NARI Relays and IEC 61850 Architecture
  2. 2. IEC 61850 Logical Nodes in NARI IEDs
  3. 3. NARI IEC 61850 Data Models and Signals
  4. 4. MMS Client-Server Communication
  5. 5. GOOSE Messaging and Protection Interlocking
  6. 6. GOOSE Publisher and Subscriber Configuration
  7. 7. IEC 61850 Report Control Blocks (RCB)
  8. 8. Buffered and Unbuffered Reporting
  9. 9. ICD, CID, SCD and IID Files
  10. 10. SCL Engineering and Configuration Workflow
  11. 11. IEC 61850 Communication Troubleshooting
  12. 12. GOOSE Testing with IEDScout and Wireshark
  13. 13. IEC 61850 Testing and Commissioning of NARI IEDs
  14. 14. Practical NARI IEC 61850 Engineering Example: Complete Feeder Bay Integration
  15. 15. Best Practices for NARI IEC 61850 Engineering
  16. 16. IEC 61850 Standards and Technical References
  17. 17. NARI IEC 61850 Engineering Training by Elec-Engg
  18. 18. Conclusion

NARI IEC 61850 Engineering is an essential part of modern digital substation protection, control, monitoring and automation systems. NARI protection relays and substation automation equipment support IEC 61850-based communication architectures that enable protection IEDs, bay control units, station-level systems and SCADA platforms to exchange information through standardized data models and communication services.

IEC 61850 provides a common framework for integrating protection and control equipment from different manufacturers. Instead of relying exclusively on conventional hardwired signals, digital substations can use Ethernet-based communication, GOOSE messaging, MMS client-server services and standardized Substation Configuration Language (SCL) files.

NARI has a broad IEC 61850-capable protection and automation portfolio, including PCS-series protection devices, bay control units and communication equipment. However, the exact IEC 61850 services, logical nodes, data models, supported functions and engineering capabilities depend on the individual device model, hardware configuration and firmware version.

This comprehensive article explains the engineering principles and practical implementation of IEC 61850 in NARI-based protection and substation automation projects. It covers the complete workflow, from understanding the communication architecture and configuring logical nodes to engineering GOOSE messages, configuring MMS reports, managing SCL files, testing communication and commissioning NARI IEDs.

1. NARI Relays and IEC 61850 Architecture

1.1 Introduction to IEC 61850

IEC 61850 is an international standard for communication networks and systems used in electrical substations.

It defines standardized approaches for:

  • Data modeling and naming.
  • Protection and control information exchange.
  • Ethernet-based communication.
  • GOOSE messaging.
  • MMS client-server communication.
  • Reporting and event notification.
  • Time synchronization.
  • Engineering and configuration using SCL files.
  • System integration and interoperability.

In conventional substations, protection relays communicate with other equipment through copper control cables, binary inputs, binary outputs and conventional communication protocols.

IEC 61850 introduces a structured communication environment in which protection and control functions can exchange information through standardized services.

For example, a NARI feeder protection relay can publish a trip-related GOOSE message that is received by a bay control unit or another protection IED, provided that the devices support the required communication services and have been configured correctly.

1.2 Typical NARI IEC 61850 Architecture

A typical NARI-based digital substation can be divided into three main levels.

Process Level

This level includes primary equipment and the associated interface devices:

  • Current transformers (CTs).
  • Voltage transformers (VTs).
  • Circuit breakers.
  • Disconnectors.
  • Earthing switches.
  • Merging units, where applicable.
  • Process-level interface equipment.

Bay Level

The bay level contains protection and control IEDs responsible for individual feeders, transformers, busbars, generators and transmission lines.

Typical equipment may include:

  • NARI feeder protection relays.
  • NARI line differential protection relays.
  • NARI transformer protection relays.
  • NARI generator protection relays.
  • NARI bay control units.
  • Other protection and control IEDs.

Station Level

The station level includes equipment responsible for substation-wide monitoring, control and supervision:

  • SCADA systems.
  • Station HMI.
  • Engineering workstation.
  • Gateway equipment.
  • Station-level communication servers.
  • Time synchronization systems.
  • Event and disturbance record management systems.

1.3 Communication Architecture

IEC 61850 uses different communication services for different engineering purposes.

Communication serviceMain application
MMSClient-server communication
GOOSEFast event and protection signal exchange
Sampled Values (SV)Transmission of sampled current and voltage values
ReportingTransmission of events and measurements
Time synchronizationSynchronization of IED clocks
SCLEngineering and configuration data exchange

Not every NARI device supports every service. In particular, Sampled Values and process-bus capabilities must be checked against the specific IED and its firmware documentation.

1.4 Station Bus and Process Bus

Station Bus

The station bus is primarily used for communication between bay-level IEDs and station-level systems.

Typical applications include:

  • MMS communication with SCADA.
  • GOOSE-based interlocking.
  • Protection status exchange.
  • Circuit breaker status communication.
  • Remote control.
  • Event and alarm reporting.

Process Bus

The process bus connects protection and control IEDs with process-level equipment and interfaces.

Typical applications include:

  • Sampled Values transmission.
  • GOOSE-based control signals.
  • Merging unit communication.
  • Process-level status exchange.

A process bus implementation requires compatible equipment, network architecture and appropriate IEC 61850 service support.

2. IEC 61850 Logical Nodes in NARI IEDs

2.1 What Are Logical Nodes?

Logical Nodes (LNs) are standardized functional building blocks defined by IEC 61850.

Each logical node represents a specific function or information category within an IED.

For example:

  • XCBR represents circuit breaker information.
  • XSWI represents switchgear information.
  • PTOC represents time-overcurrent protection.
  • PDIS represents distance protection.
  • MMXU represents measurement functions.
  • GGIO represents generic input/output information.

Instead of using arbitrary manufacturer-specific signal names, IEC 61850 organizes information into standardized logical nodes and data objects.

This improves interoperability between protection relays, control devices and SCADA systems.

2.2 Important Logical Nodes Used in Protection Applications

Logical NodeDescriptionTypical application
LPHDPhysical device informationIED hardware status
LLN0Logical device common nodeCommon device functions
XCBRCircuit breakerBreaker status and control
XSWISwitch or disconnectorSwitchgear status
PTOCTime overcurrentFeeder protection
PIOCInstantaneous overcurrentHigh-set overcurrent
PTOVOvervoltageVoltage protection
PTUVUndervoltageVoltage protection
PDISDistance protectionTransmission line protection
PDIFDifferential protectionLine or transformer differential
PTEFEarth fault protectionEarth fault applications
MMXUMeasurementCurrent, voltage and power
MMTRMeteringEnergy measurements
GGIOGeneric I/OBinary and analog signals
CSWISwitch controllerCircuit breaker control
CILOInterlockingSwitching interlocks
RRECAutoreclosingAutomatic reclosing
PTRCProtection trip conditioningTrip signal processing
RSYNSynchronism checkSynchronizing supervision
CALHAlarm handlingAlarm information
RDREDisturbance recordingDisturbance recording functions

The availability and implementation of these logical nodes must be confirmed using the specific NARI IED’s IEC 61850 conformance documentation and SCL files.

2.3 Example: Feeder Protection Logical Nodes

A typical feeder protection IED may contain logical nodes associated with:

  • Overcurrent protection.
  • Earth fault protection.
  • Directional overcurrent.
  • Voltage supervision.
  • Circuit breaker control.
  • Measurement.
  • Protection trip.
  • Disturbance recording.

A simplified logical structure could look like:

IED1
 |
 +-- LD0
      |
      +-- LLN0
      |
      +-- LPHD1
      |
      +-- PTOC1
      |
      +-- PIOC1
      |
      +-- PTEF1
      |
      +-- XCBR1
      |
      +-- CSWI1
      |
      +-- PTRC1
      |
      +-- MMXU1
      |
      +-- GGIO1

This is an illustrative IEC 61850 structure, not a guaranteed logical-node list for a particular NARI relay.

2.4 Logical Node Data Objects

Each logical node contains data objects representing specific information.

For example, the XCBR logical node may contain information associated with:

  • Circuit breaker position.
  • Operating capability.
  • Breaker operating mode.
  • Breaker health.
  • Breaker-related measurements.

A circuit breaker position can be represented using the data object:

XCBR1.Pos.stVal

Here:

  • XCBR1 identifies the logical node instance.
  • Pos identifies the position data object.
  • stVal identifies the status value.

The actual data attribute and functional constraint must be verified against the device’s data model.

3. NARI IEC 61850 Data Models and Signals

3.1 Understanding the IEC 61850 Data Model

IEC 61850 defines a hierarchical data structure.

The basic hierarchy is:

IED
 |
 +-- Access Point
      |
      +-- Logical Device
           |
           +-- Logical Node
                |
                +-- Data Object
                     |
                     +-- Data Attribute

For example:

NARI_FEEDER_01
 |
 +-- LD0
      |
      +-- PTOC1
      |    |
      |    +-- Str
      |    +-- Op
      |    +-- StrVal
      |
      +-- XCBR1
      |    |
      |    +-- Pos
      |
      +-- MMXU1
           |
           +-- A
           +-- PhV
           +-- Hz

3.2 Data Attributes

IEC 61850 data attributes describe the actual values associated with data objects.

Common examples include:

AttributeMeaning
stValStatus value
qQuality
tTimestamp
magMagnitude
instMagInstantaneous magnitude
setMagSetting magnitude
ctlValControl value
operOperate command

For example, a measurement can be represented using a magnitude and quality attribute.

MMXU1.A.phsA.cVal.mag.f

This is an illustrative reference to a phase-current measurement value.

3.3 Quality and Timestamp

Two important IEC 61850 attributes are quality and timestamp.

Quality (q)

Quality indicates whether a data value is valid and suitable for use.

Possible quality indications include:

  • Good.
  • Invalid.
  • Questionable.
  • Old data.
  • Test.
  • Operator blocked.
  • Failure.

Timestamp (t)

The timestamp identifies when a particular event or value was generated.

Correct timestamp handling is important for:

  • Event sequence analysis.
  • Protection disturbance investigation.
  • SOE monitoring.
  • Fault reconstruction.
  • Substation automation.

3.4 Signal Mapping

In a practical NARI engineering project, internal relay signals must be mapped to IEC 61850 data objects.

For example:

Internal relay signalIEC 61850 representation
Phase overcurrent startPTOC.Str
Phase overcurrent tripPTOC.Op
Breaker openXCBR.Pos
Breaker failureProtection or generic status data object
Phase currentMMXU.A
Busbar voltageMMXU.PhV
Relay healthyLPHD.PhyHealth or device-specific status

The actual mapping depends on the NARI relay’s implementation.

3.5 Why Signal Mapping Is Important

Incorrect signal mapping can cause serious operational problems.

Examples include:

  • A breaker open signal being interpreted as breaker closed.
  • Incorrect protection trip indication.
  • Missing alarm signals.
  • Incorrect measurement scaling.
  • Wrong quality interpretation.
  • Incorrect GOOSE subscriber assignment.

Therefore, signal mapping should be verified during engineering and commissioning.

4. MMS Client-Server Communication

4.1 What Is MMS?

Manufacturing Message Specification (MMS) is an application-layer communication protocol used by IEC 61850 for client-server communication.

In a typical substation architecture:

  • NARI IEDs operate as MMS servers.
  • SCADA systems operate as MMS clients.
  • Engineering workstations can act as MMS clients.
  • Gateway devices can retrieve data from multiple IEDs.

MMS allows clients to access standardized data objects, retrieve measurements, receive reports and perform supported control operations.

4.2 Typical MMS Applications

MMS communication is commonly used for:

  • Reading measurements.
  • Reading protection status.
  • Retrieving breaker position.
  • Monitoring relay health.
  • Receiving alarms.
  • Receiving sequence-of-events information.
  • Reading settings, where supported.
  • Executing control operations, where authorized and supported.

4.3 MMS Communication Architecture

              Station SCADA
                   |
                   |
              MMS Client
                   |
             Ethernet Network
                   |
        +----------+----------+
        |          |          |
      NARI       NARI       NARI
      IED 1      IED 2      IED 3
        |          |          |
      Feeder    Transformer   Line
      Relay       Relay      Relay

Each IED exposes its IEC 61850 data model through the MMS server.

4.4 MMS Communication Parameters

Typical engineering parameters include:

  • IED IP address.
  • Subnet mask.
  • Default gateway.
  • Ethernet interface.
  • TCP port.
  • MMS server configuration.
  • Logical device names.
  • Logical node structure.
  • Association settings.
  • Access permissions.
  • Reporting configuration.

The standard MMS transport commonly uses TCP port 102, although project architecture and device implementation should be checked.

4.5 MMS Troubleshooting

When MMS communication fails, the following checks are recommended:

  1. Verify the IED IP address.
  2. Check the subnet and gateway configuration.
  3. Verify Ethernet connectivity.
  4. Check network VLAN configuration.
  5. Check firewall rules.
  6. Confirm that the MMS server is enabled.
  7. Verify the logical device name.
  8. Check client association settings.
  9. Verify report configuration.
  10. Inspect network traffic using Wireshark.

Common symptoms include:

SymptomPossible cause
IED unreachableIP or physical network problem
MMS association failureClient/server configuration
No measurementsIncorrect data model or access configuration
Reports not receivedRCB configuration
Intermittent communicationNetwork congestion or redundancy issue
Control command rejectedControl model or permission problem

5. GOOSE Messaging and Protection Interlocking

5.1 What Is GOOSE?

Generic Object Oriented Substation Event (GOOSE) is an IEC 61850 communication service designed for fast event-based communication between IEDs.

GOOSE messages are transmitted over Ethernet using multicast communication.

Unlike conventional MMS client-server communication, GOOSE does not require a client to continuously poll the server for updated information.

Instead, an IED publishes a message when relevant information changes and retransmits it according to the GOOSE retransmission mechanism.

5.2 Typical GOOSE Applications

GOOSE is used for:

  • Circuit breaker trip signals.
  • Protection interlocking.
  • Breaker failure initiation.
  • Busbar protection signals.
  • Transfer trip.
  • Blocking signals.
  • Protection start signals.
  • Disconnector status.
  • Breaker position.
  • Automatic switching logic.

5.3 Example: GOOSE-Based Protection Interlocking

Consider two adjacent feeder bays in a substation.

A protection IED in Bay 1 must receive the breaker or disconnector status from Bay 2 to determine whether a switching operation is permitted.

Using conventional wiring, these signals would require dedicated copper cables.

With GOOSE, the status information can be transmitted through the Ethernet network.

Simplified signal flow:

       NARI IED - Bay 2
              |
       Disconnector Status
              |
        GOOSE Publisher
              |
        Ethernet Network
              |
        GOOSE Subscriber
              |
       NARI IED - Bay 1
              |
       Interlocking Logic
              |
       Switching Permission

5.4 GOOSE Performance

GOOSE is designed for time-critical communication.

Its performance depends on:

  • Network architecture.
  • Switch performance.
  • Network traffic.
  • IED processing.
  • GOOSE configuration.
  • Network redundancy.
  • Application requirements.

For protection applications, the complete end-to-end performance must be validated against the applicable project requirements and IEC 61850 performance classes.

5.5 GOOSE Message Structure

A GOOSE message contains important information such as:

ParameterDescription
gocbRefGOOSE control block reference
datSetDataset reference
goIDGOOSE identifier
goCBNameGOOSE control block name
confRevConfiguration revision
stNumState number
sqNumSequence number
timeAllowedToLiveMaximum expected message interval
testTest indication
ndsComNeeds commissioning indication
numDatSetEntriesNumber of dataset entries
allDataPublished dataset values

These parameters are useful when configuring and troubleshooting GOOSE communication.

6. GOOSE Publisher and Subscriber Configuration

6.1 GOOSE Publisher

A GOOSE publisher is the IED that generates and transmits GOOSE messages.

For example, a NARI protection relay can publish:

  • Protection trip.
  • Protection start.
  • Circuit breaker position.
  • Interlocking status.
  • Breaker failure status.

The signals are organized into a dataset and associated with a GOOSE control block.

6.2 GOOSE Subscriber

A GOOSE subscriber receives messages published by another IED.

The receiving IED uses the received information in its internal application logic.

For example:

  • A feeder protection relay publishes a trip signal.
  • A neighboring bay controller subscribes to the message.
  • The bay controller receives the status.
  • The received information is processed by the configured logic.

6.3 GOOSE Configuration Workflow

A typical configuration process includes:

  1. Identify the publishing IED.
  2. Identify the subscribing IED.
  3. Select the required signals.
  4. Create the publisher dataset.
  5. Configure the GOOSE control block.
  6. Define the multicast communication parameters.
  7. Configure the subscriber mapping.
  8. Assign the received signals to application logic.
  9. Generate or update the SCL configuration.
  10. Download or implement the configuration.
  11. Test the communication.

6.4 Example GOOSE Signal Mapping

PublisherPublished signalSubscriberApplication
Feeder IED 1Protection tripBay controller 1Trip indication
Feeder IED 1Breaker positionFeeder IED 2Interlocking
Transformer IEDTransformer tripBusbar IEDProtection coordination
Busbar IEDBusbar tripFeeder IEDsCircuit breaker tripping
Feeder IED 2Breaker failureBusbar IEDBackup protection

This is an example of possible system engineering, not a statement that every NARI relay supports all listed publisher and subscriber functions.

6.5 Important GOOSE Configuration Parameters

The following parameters should be checked during engineering:

  • MAC destination address.
  • APPID.
  • VLAN ID.
  • VLAN priority.
  • Dataset reference.
  • GOOSE control block reference.
  • Configuration revision.
  • Publisher IED identity.
  • Subscriber mapping.
  • Test and commissioning status.

Incorrect configuration can result in a subscriber failing to recognize or process the published GOOSE message.

7. IEC 61850 Report Control Blocks (RCB)

7.1 What Is a Report Control Block?

A Report Control Block (RCB) defines how an IEC 61850 server sends data and events to an MMS client.

For example, a SCADA system may require information about:

  • Circuit breaker status.
  • Protection trip.
  • Protection start.
  • Current measurements.
  • Voltage measurements.
  • Relay alarms.
  • Communication status.

Instead of continuously reading every data object, the SCADA client can receive reports from the IED.

7.2 Report Control Block Types

IEC 61850 defines two major report control block types:

  • Buffered Report Control Block (BRCB).
  • Unbuffered Report Control Block (URCB).

Each provides different reporting behavior.

7.3 Important RCB Parameters

ParameterDescription
RptIDReport identifier
DatSetDataset reference
ConfRevDataset configuration revision
OptFldsOptional report fields
BufTmBuffer time
TrgOpsTrigger options
IntgPdIntegrity period
GIGeneral interrogation
RptEnaReport enable
ResvReservation, where applicable

7.4 Report Trigger Options

Typical report trigger conditions include:

  • Data change.
  • Quality change.
  • Data update.
  • Integrity period.
  • General interrogation.

For example, when a NARI IED detects a protection trip, the associated status can trigger a report to the SCADA system if the data object is included in the reporting dataset and the relevant trigger options are configured.

8. Buffered and Unbuffered Reporting

8.1 Buffered Reporting

Buffered reporting uses a buffer to retain report information when the client is disconnected, subject to the IED’s supported buffering capacity and configuration.

When the connection is restored, the client can retrieve buffered events.

This is especially useful for substations where event information must be preserved during temporary communication interruptions.

Typical applications include:

  • Protection trips.
  • Breaker operations.
  • Switching events.
  • Alarm changes.
  • Important status transitions.

8.2 Unbuffered Reporting

Unbuffered reporting does not provide the same store-and-forward event retention behavior.

If the client is disconnected, reports generated during that period may be lost.

Typical applications include:

  • Noncritical monitoring.
  • Periodic measurements.
  • Information where historical event retention is not essential.

8.3 Comparison

FeatureBRCBURCB
Event bufferingYesNo
Disconnection handlingRetains buffered reportsReports may be lost
Event recoverySupported within buffer limitsGenerally unavailable
Suitable for SOEYesLess suitable
Typical applicationImportant eventsRoutine monitoring

8.4 Practical Engineering Recommendation

For critical protection and switching events, buffered reporting is generally preferable when supported by the NARI IED and the station-level system.

The buffer capacity, reservation behavior and recovery mechanism should be checked during project engineering.

9. ICD, CID, SCD and IID Files

9.1 Introduction to SCL

Substation Configuration Language (SCL) is an XML-based engineering language defined by IEC 61850-6.

It is used to describe IED capabilities, communication configuration, substation structure and system-level engineering information.

SCL allows engineering tools from different manufacturers to exchange configuration information.

9.2 Main SCL File Types

ICD — IED Capability Description

The ICD file describes the capabilities of an IED.

It can contain:

  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.
  • Communication capabilities.
  • Supported services.
  • Data type templates.

A NARI ICD file can be used as an input to system engineering, subject to the capabilities of the specific device and its engineering tool.

CID — Configured IED Description

The CID file contains the configuration intended for a particular IED.

It may include:

  • IED identification.
  • Logical device structure.
  • Communication parameters.
  • GOOSE configuration.
  • Datasets.
  • Report control blocks.

It is commonly used when transferring an engineered configuration to an IED.

SCD — Substation Configuration Description

The SCD file describes the overall substation IEC 61850 configuration.

It can include:

  • Substation topology.
  • All participating IEDs.
  • Communication networks.
  • Datasets.
  • GOOSE control blocks.
  • Report configurations.
  • Communication connections.

The SCD file is especially important in multi-vendor substation engineering.

IID — Instantiated IED Description

The IID file represents the instantiated configuration information for an IED, as used in engineering workflows that support this exchange format.

Its exact use depends on the engineering process and toolchain.

9.3 Comparison of SCL Files

FileMain purpose
ICDDescribes IED capabilities
CIDContains configured IED information
SCDDescribes complete substation configuration
IIDDescribes instantiated IED configuration

9.4 Practical Example

Suppose a substation contains:

  • Two NARI feeder protection IEDs.
  • One NARI transformer protection IED.
  • One NARI bay control unit.
  • One SCADA gateway.

The engineering workflow may be:

  1. Obtain the ICD files for each IED.
  2. Import the files into the system engineering tool.
  3. Create the substation structure.
  4. Define the IED communication parameters.
  5. Configure datasets.
  6. Configure GOOSE communication.
  7. Configure MMS reporting.
  8. Generate the SCD file.
  9. Export the appropriate configured IED files.
  10. Download configurations to the devices.
  11. Perform system-level validation.

Fundamentals IEC 61850 — Data Model, Logical Nodes, and the SCL World: The SCL Engineering Workflow Explained — SSD, ICD, SCD, and CID

10. SCL Engineering and Configuration Workflow

10.1 Project Preparation

Before starting IEC 61850 engineering, collect the following information:

  • NARI IED model numbers.
  • Firmware versions.
  • IEC 61850 capability documentation.
  • ICD files.
  • Device IP addresses.
  • Network topology.
  • Required protection signals.
  • GOOSE communication requirements.
  • SCADA communication requirements.
  • Control and interlocking philosophy.

It is important to use the correct ICD file for the actual hardware and firmware version.

10.2 Creating the Substation Structure

The first engineering step is defining the substation structure.

For example:

Substation
 |
 +-- Voltage Level 132 kV
      |
      +-- Line Bay 1
      |    |
      |    +-- NARI Line Protection
      |    +-- NARI Bay Control Unit
      |
      +-- Transformer Bay 1
      |    |
      |    +-- NARI Transformer Protection
      |
      +-- Feeder Bay 1
           |
           +-- NARI Feeder Protection

The actual structure should reflect the project’s single-line diagram and functional design.

10.3 Importing IED Capability Files

Import the ICD files into the engineering environment.

Check:

  • IED name.
  • Logical device structure.
  • Logical nodes.
  • Data objects.
  • Data types.
  • Communication capabilities.
  • GOOSE support.
  • Reporting support.
  • Control model support.

If the file is outdated or incompatible with the actual relay firmware, engineering errors may occur.

10.4 Communication Configuration

Assign the network parameters to each IED.

ParameterExample
IED 1 IP192.168.10.11
IED 2 IP192.168.10.12
IED 3 IP192.168.10.13
Subnet mask255.255.255.0
Gateway192.168.10.1

These addresses are illustrative only.

The actual network plan must be approved by the project network engineering team.

10.5 Dataset Engineering

Datasets define which data objects are included in communication services.

For example, a feeder IED dataset may contain:

  • Protection trip.
  • Protection start.
  • Circuit breaker position.
  • Current measurement.
  • Voltage measurement.
  • Relay health status.

Different datasets may be created for GOOSE publishing and MMS reporting.

10.6 GOOSE Engineering

Define:

  • Publisher IED.
  • Subscriber IED.
  • GOOSE dataset.
  • GOOSE control block.
  • Destination multicast address.
  • APPID.
  • VLAN configuration.
  • Subscriber signal mapping.

Then validate the configuration using the engineering tool and available IED diagnostics.

10.7 Report Engineering

Define the MMS reporting datasets and RCBs.

Configure:

  • Report identifiers.
  • Buffered or unbuffered reporting.
  • Trigger conditions.
  • Integrity periods.
  • Optional fields.
  • Client access.

10.8 Configuration Validation

Before downloading configurations, perform:

  • SCL syntax validation.
  • IED model validation.
  • Communication consistency checks.
  • GOOSE publisher/subscriber checks.
  • Dataset verification.
  • Report configuration checks.
  • IP address conflict checks.
  • Configuration revision checks.

10.9 Configuration Download

Download the appropriate configuration to each IED using the manufacturer’s supported engineering procedure.

Always maintain a backup of the previous working configuration.

After downloading, verify:

  • IED communication.
  • Correct logical device structure.
  • GOOSE publication.
  • GOOSE subscription.
  • MMS reporting.
  • Protection and control application behavior.

11. IEC 61850 Communication Troubleshooting

11.1 Common Communication Problems

IEC 61850 communication problems can occur at different levels:

  • Physical Ethernet layer.
  • IP network layer.
  • TCP transport layer.
  • MMS application layer.
  • GOOSE communication layer.
  • SCL configuration layer.
  • Protection application logic.

Troubleshooting should identify the layer responsible for the failure rather than immediately changing the IED configuration.

11.2 Ethernet Communication Checks

Check:

  1. Ethernet cable condition.
  2. Switch port status.
  3. Link speed and duplex.
  4. IED network interface.
  5. VLAN configuration.
  6. Network redundancy.
  7. IP addressing.
  8. Network switch diagnostics.

11.3 MMS Troubleshooting

Typical problems include:

  • MMS server unavailable.
  • Association rejected.
  • Wrong logical device reference.
  • Report not enabled.
  • Client cannot access a data object.
  • Incorrect report dataset.
  • Unsupported control model.

Useful diagnostic tools include network packet analysis and the IED’s own communication diagnostics.

11.4 GOOSE Troubleshooting

Common GOOSE problems include:

  • Incorrect multicast MAC address.
  • Wrong APPID.
  • Incorrect VLAN ID.
  • Wrong dataset reference.
  • Incorrect configuration revision.
  • Subscriber mapping mismatch.
  • GOOSE publisher disabled.
  • Network switch filtering.
  • Incorrect subscriber application logic.

11.5 Practical Troubleshooting Table

ProblemPossible causeRecommended action
No GOOSE messagePublisher disabledCheck GOOSE control block
GOOSE received but not processedSubscriber mapping incorrectVerify signal mapping
Wrong GOOSE valueDataset errorVerify dataset entries
GOOSE quality invalidSource data quality issueInspect source IED
MMS connection unavailableNetwork or server issueCheck IP and MMS server
No SCADA eventsRCB configuration issueVerify reporting settings
Incorrect timestampsTime synchronization issueCheck NTP or PTP configuration
Intermittent communicationNetwork issueInspect switches and redundancy
Configuration rejectedIncompatible SCL fileCheck model and firmware compatibility

11.6 Network Redundancy

Digital substations may use redundant Ethernet network architectures to improve communication availability.

Common approaches include:

  • PRP (Parallel Redundancy Protocol).
  • HSR (High-availability Seamless Redundancy).

PRP and HSR are defined in IEC 62439-3.

Whether these architectures are supported depends on the specific NARI IED, communication interface and network design.

12. GOOSE Testing with IEDScout and Wireshark

Practical testing is essential to verify that the IEC 61850 communication configuration works correctly.

Two useful engineering tools are IEDScout and Wireshark.

IEDScout – Logiciel polyvalent pour les équipements CEI 61850 – OMICRON

12.1 Testing with IEDScout

IEDScout is an IEC 61850 engineering and diagnostic tool used to explore IED data models and inspect supported communication services.

Depending on the tool version and device capabilities, it can be used to:

  • Connect to an IEC 61850 server.
  • Browse logical devices.
  • Explore logical nodes.
  • Read data objects.
  • Monitor measurements.
  • Inspect quality and timestamp information.
  • Examine reporting services.
  • Inspect GOOSE-related information.
  • Support commissioning and troubleshooting.

12.2 MMS Testing Procedure

A practical MMS testing procedure:

  1. Connect the engineering computer to the station network.
  2. Configure the computer’s IP address.
  3. Open IEDScout.
  4. Enter the NARI IED IP address.
  5. Establish an MMS association.
  6. Browse the logical devices.
  7. Open the required logical nodes.
  8. Read measurements.
  9. Check protection status.
  10. Verify quality and timestamps.

For example, browse:

LD0
 |
 +-- MMXU1
 |    |
 |    +-- A
 |    +-- PhV
 |    +-- Hz
 |
 +-- XCBR1
 |    |
 |    +-- Pos
 |
 +-- PTOC1
      |
      +-- Str
      +-- Op

The actual logical node names and structure depend on the NARI device.

12.3 GOOSE Testing with IEDScout

The objective is to verify that the publisher and subscriber exchange the expected information.

Testing should include:

  • Publisher identification.
  • Dataset verification.
  • GOOSE control block status.
  • Subscriber detection.
  • Signal value.
  • Quality.
  • State number.
  • Sequence number.
  • Communication supervision.

Where supported, controlled test signals can be used to verify the complete signal path.

12.4 GOOSE Testing with Wireshark

Wireshark is a network protocol analyzer that can capture and decode IEC 61850 communication traffic.

It is especially useful for analyzing:

  • GOOSE packets.
  • MMS packets.
  • Ethernet multicast traffic.
  • VLAN tagging.
  • Communication timing.
  • Packet loss.
  • Retransmission behavior.

A typical Wireshark display filter is:

goose

For MMS traffic:

tcp.port == 102

For VLAN-tagged traffic, the following filter may be useful:

vlan

Filter availability and decoded fields depend on the Wireshark version and packet capture environment.

12.5 GOOSE Packet Analysis

When analyzing a GOOSE packet, check:

FieldEngineering purpose
Source MACIdentifies publisher interface
Destination MACVerifies multicast destination
VLAN IDChecks network segmentation
APPIDIdentifies GOOSE application
gocbRefIdentifies control block
datSetIdentifies dataset
stNumIndicates state changes
sqNumIndicates retransmission sequence
confRevVerifies configuration revision
timeAllowedToLiveCommunication supervision

12.6 Practical GOOSE Test Example

Consider a NARI feeder relay publishing a protection trip signal to a bay control unit.

The test sequence is:

  1. Verify the publisher configuration.
  2. Confirm that the trip signal belongs to the correct dataset.
  3. Capture the GOOSE message using Wireshark.
  4. Verify the destination multicast MAC.
  5. Check APPID and VLAN.
  6. Confirm the dataset values.
  7. Initiate a controlled protection test.
  8. Observe the GOOSE state change.
  9. Verify that the subscriber receives the signal.
  10. Confirm that the expected application logic responds.

Protection trip outputs should be isolated or managed under an approved test procedure to prevent unintended breaker operation.

13. IEC 61850 Testing and Commissioning of NARI IEDs

13.1 Introduction

IEC 61850 commissioning verifies the complete communication and application behavior of the substation system.

Testing should not be limited to checking whether an IED responds to a ping command or whether an MMS connection is established.

The commissioning process must verify that the intended protection, control and monitoring signals are correctly exchanged between devices.

13.2 Pre-Commissioning Checks

Before testing, verify:

  • Correct NARI relay model.
  • Correct firmware version.
  • Correct configuration file.
  • Correct IP addressing.
  • Correct network topology.
  • Correct IED identification.
  • Correct logical node configuration.
  • Correct GOOSE datasets.
  • Correct MMS datasets.
  • Correct report control blocks.
  • Correct time synchronization.
  • Correct protection settings.

13.3 MMS Commissioning Tests

TestExpected result
IED connectivityIED reachable
MMS associationClient connected
Logical device browsingCorrect structure displayed
Measurement readingCorrect values
Breaker statusCorrect position
Protection statusCorrect indications
ReportingEvents received
General interrogationRequired data retrieved
Control operationCorrect response, where supported

13.4 GOOSE Commissioning Tests

TestExpected result
Publisher configurationCorrect dataset and control block
Subscriber configurationCorrect source mapping
Multicast addressCorrect destination
APPIDCorrect application identification
VLANCorrect network configuration
Normal statusCorrect signal value
Status changeCorrect message update
Subscriber responseCorrect application behavior
Communication interruptionCorrect supervision and fail-safe response

13.5 Protection and Interlocking Tests

For protection applications, testing should verify the complete chain:

Protection Function
        |
        v
Internal Protection Signal
        |
        v
GOOSE Publisher
        |
        v
Ethernet Network
        |
        v
GOOSE Subscriber
        |
        v
Application Logic
        |
        v
Trip / Blocking / Interlocking
        |
        v
Expected System Response

For example, when a feeder protection relay detects an overcurrent condition, the engineer should verify:

  1. Protection element pickup.
  2. Protection trip logic.
  3. GOOSE publisher activation.
  4. Correct transmitted signal.
  5. GOOSE subscriber reception.
  6. Correct receiving logic.
  7. Expected trip or interlocking response.
  8. Event recording and timestamps.

13.6 Time Synchronization Testing

Accurate time synchronization is essential for event analysis.

IEC 61850 substations may use:

  • SNTP.
  • NTP.
  • PTP (IEEE 1588).

The actual supported protocol depends on the device.

Commissioning should verify:

  • Time source availability.
  • Synchronization status.
  • Clock offset.
  • Timestamp accuracy.
  • Event sequence consistency.

13.7 Final Commissioning Documentation

The commissioning team should prepare:

  • IED configuration records.
  • SCL files.
  • IP address schedule.
  • GOOSE signal matrix.
  • MMS signal list.
  • Protection signal mapping.
  • Communication test results.
  • Wireshark packet captures, where appropriate.
  • Time synchronization test results.
  • Final approved configuration backups.
  • Outstanding issue list.

14. Practical NARI IEC 61850 Engineering Example: Complete Feeder Bay Integration

Consider a 132 kV feeder bay containing:

  • One NARI feeder protection IED.
  • One NARI bay control unit.
  • One circuit breaker.
  • One disconnector.
  • One earthing switch.
  • One station SCADA system.

The objective is to implement IEC 61850 communication for protection status, breaker monitoring, interlocking and SCADA supervision.

14.1 System Requirements

The following signals are required:

SignalCommunication
Feeder protection tripGOOSE / MMS
Protection startGOOSE / MMS
Breaker positionGOOSE / MMS
Disconnector positionGOOSE / MMS
Earthing switch positionGOOSE / MMS
Feeder currentMMS reporting
Feeder voltageMMS reporting
Relay healthMMS reporting
Breaker controlMMS, if supported
Interlocking statusGOOSE / application logic

14.2 GOOSE Configuration

The feeder protection IED publishes the protection trip signal.

The bay control unit subscribes to the signal.

The bay control unit may also publish breaker and disconnector status for use by other IEDs.

14.3 MMS Configuration

The station SCADA system connects to both IEDs using MMS.

It retrieves:

  • Protection status.
  • Breaker position.
  • Disconnector position.
  • Current measurements.
  • Voltage measurements.
  • Alarm information.

14.4 Testing

The commissioning engineer performs:

  1. MMS connection test.
  2. Logical node verification.
  3. Measurement verification.
  4. Report testing.
  5. GOOSE publisher testing.
  6. GOOSE subscriber testing.
  7. Interlocking tests.
  8. Breaker status verification.
  9. Control testing, where supported.
  10. Final documentation.

The result is a digitally integrated feeder bay in which protection, control and station monitoring systems exchange standardized IEC 61850 information.

15. Best Practices for NARI IEC 61850 Engineering

Successful IEC 61850 engineering requires careful coordination between protection engineers, automation engineers and communication network specialists.

The following practices are recommended.

15.1 Use Correct IED Capability Files

Always use ICD files that match the actual device model and firmware.

Do not assume that all NARI PCS-series devices share identical logical nodes and communication capabilities.

15.2 Maintain Consistent Naming

Use consistent naming conventions for:

  • IEDs.
  • Logical devices.
  • Logical nodes.
  • Datasets.
  • GOOSE control blocks.
  • Report control blocks.
  • Communication networks.

15.3 Maintain a GOOSE Signal Matrix

A GOOSE matrix should clearly identify:

  • Publisher.
  • Subscriber.
  • Signal name.
  • Data reference.
  • Dataset.
  • APPID.
  • VLAN ID.
  • Expected signal behavior.
  • Application destination.

15.4 Verify Every GOOSE Signal

Do not assume that a configured GOOSE subscription is working correctly.

Verify the actual transmitted packet, received value and final application response.

15.5 Use Buffered Reporting for Critical Events

Where supported, buffered reporting should be considered for important protection and switching events.

15.6 Keep Configuration Backups

Maintain controlled backups of:

  • Original ICD files.
  • Final SCD files.
  • CID files.
  • Relay settings.
  • Communication configuration.
  • Firmware information.
  • Test reports.

15.7 Coordinate Protection and Communication Engineering

Protection engineers must understand the purpose and behavior of the signals being exchanged.

Communication engineers must understand the requirements for:

  • Protection trip.
  • Blocking.
  • Interlocking.
  • Breaker failure.
  • Protection start.
  • Communication failure.

IEC 61850 engineering is not simply a network configuration task. It is an integrated protection, control and communication engineering activity.

16. IEC 61850 Standards and Technical References

The following standards are important references for NARI IEC 61850 engineering.

StandardSubject
IEC 61850-3General requirements
IEC 61850-4System and project management
IEC 61850-5Communication requirements for functions and device models
IEC 61850-6Substation Configuration Language
IEC 61850-7-1Basic communication structure
IEC 61850-7-2Abstract communication service interface
IEC 61850-7-3Common data classes
IEC 61850-7-4Compatible logical node classes and data object classes
IEC 61850-8-1MMS and Ethernet mapping
IEC 61850-9-2Sampled Values mapping
IEC 61850-10Conformance testing
IEC 62351Power system communication security
IEC 62439-3PRP and HSR network redundancy

Engineers should refer to the applicable editions of these standards and the relevant NARI product manuals when preparing project-specific configurations.

17. NARI IEC 61850 Engineering Training by Elec-Engg

Understanding IEC 61850 requires more than learning the definitions of MMS, GOOSE, logical nodes and SCL files.

Protection and substation automation engineers must be able to configure communication, understand the IEC 61850 data model, investigate communication problems and verify the complete signal exchange between protection and control devices.

Elec-Engg provides practical training in power system protection, protection relay engineering and substation automation, with an emphasis on real engineering applications.

Training by Dr Saeed Roostaee / Elec-Engg can help engineers develop practical knowledge in the following areas:

  • IEC 61850 communication architecture.
  • Logical nodes and data objects.
  • IEC 61850 data models.
  • MMS client-server communication.
  • GOOSE publisher and subscriber configuration.
  • GOOSE-based protection interlocking.
  • Report Control Blocks.
  • Buffered and unbuffered reporting.
  • ICD, CID, SCD and IID files.
  • SCL engineering workflow.
  • GOOSE communication analysis.
  • IEDScout and Wireshark.
  • IEC 61850 testing and commissioning.
  • Protection and control signal mapping.

Training can be delivered through structured online courses, video-based learning, live online sessions and customized face-to-face or in-house programs, depending on the training requirements.

For NARI-specific projects, the practical exercises should be based on the actual NARI relay models, available engineering software, firmware versions, ICD files and project configuration.

Explore technical training and engineering resources:

  • Elec-Engg — Power System Protection and Substation Automation
  • Substation Automation Training
  • Structured Self-Paced Training
  • Pre-Recorded Video Training

For customized NARI IEC 61850 training, engineers and organizations can contact Elec-Engg through the website.

18. Conclusion

IEC 61850 is a fundamental technology in modern digital substations, providing standardized communication between protection relays, bay control units, station-level systems and SCADA platforms.

For NARI-based protection and automation projects, successful implementation requires a clear understanding of logical nodes, data objects, MMS communication, GOOSE messaging, report control blocks and SCL engineering.

The most important practical activities include:

  1. Understanding the NARI IED communication architecture.
  2. Verifying the supported IEC 61850 data model.
  3. Mapping protection and control signals.
  4. Configuring MMS communication.
  5. Engineering GOOSE publisher and subscriber relationships.
  6. Configuring reporting services.
  7. Managing ICD, CID and SCD files.
  8. Testing communication with IEDScout and Wireshark.
  9. Verifying protection and interlocking behavior.
  10. Completing systematic IEC 61850 commissioning.

Engineers who understand both protection principles and IEC 61850 communication can design, integrate, test and troubleshoot modern digital substations more effectively.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top