NARI Engineering Software & Practical Tutorials

NARI Engineering Software & Practical Tutorials

Complete Guide to NARI Relay Engineering, Configuration, Communication, Settings Management, and Practical Applications

Table Of Contents
  1. 1. NARI Relay Engineering Software Overview
  2. 2. Relay Project Creation and Device Selection
  3. 3. Online and Offline Engineering
  4. 4. Parameter Configuration
  5. 5. Communication Setup
  6. 6. Relay Setting Download and Upload
  7. 7. Event and Fault Record Retrieval
  8. 8. Firmware and Compatibility Management
  9. 9. Practical Relay Configuration Projects
  10. 10. Troubleshooting Real Engineering Cases
  11. 11. Recommended NARI Relay Engineering Workflow
  12. 12. Practical Engineering Checklist
  13. 13. Best Practices for NARI Relay Engineering
  14. 14. Applicable IEC Standards and Technical References
  15. 15. NARI Relay Engineering and Practical Training by Elec-Engg
  16. 16. Conclusion

NARI protection relays and protection-and-control devices are used in transmission and distribution substations, power plants, industrial power systems, and other electrical installations. Correct application of these devices requires more than selecting protection functions and entering setting values. Engineers must understand the engineering software, device configuration, communication architecture, parameter management, setting-file handling, event retrieval, firmware compatibility, and commissioning procedures.

This article provides a practical engineering overview of NARI relay engineering software and the typical workflows involved in configuring, testing, and maintaining NARI protection devices.

It is intended for protection engineers, commissioning engineers, substation automation engineers, maintenance personnel, and technical specialists responsible for relay configuration and lifecycle management.

Important technical note: NARI has different protection relay families, device generations, engineering tools, and firmware versions. Software names, menus, supported functions, file formats, communication interfaces, and procedures can differ between models. The exact device manual, software release documentation, approved project specifications, and manufacturer instructions must always take priority over generic procedures described here.

1. NARI Relay Engineering Software Overview

NARI engineering software provides the tools required to configure, parameterize, communicate with, and maintain protection and control devices.

Depending on the device family, engineering tools may support some or all of the following activities:

  • Creating and managing relay engineering projects.
  • Selecting protection and control devices.
  • Configuring device hardware and application parameters.
  • Entering protection settings.
  • Configuring communication interfaces and protocols.
  • Managing binary inputs and outputs.
  • Configuring programmable logic and control functions.
  • Downloading configuration and setting files to devices.
  • Uploading or retrieving existing device configurations.
  • Monitoring device status and measurements.
  • Reading event records and disturbance records.
  • Diagnosing communication and configuration problems.
  • Managing device firmware and software compatibility.

The engineering environment is an important part of the protection system lifecycle. It connects the protection design, relay configuration, commissioning, operation, and maintenance stages.

1.1 Main engineering software functions

Engineering activityTypical purpose
Project managementOrganize substation and device engineering data
Device selectionDefine the target relay model and hardware
Parameter configurationConfigure device application parameters
Protection settingsEnter approved protection values
Communication engineeringConfigure interfaces and protocols
Logic configurationConfigure programmable logic where supported
Online monitoringInspect live device status and measurements
Download and uploadTransfer supported data between software and relay
Event retrievalRetrieve records for operational analysis
Firmware managementMaintain compatible device software versions

Not every NARI device supports every function through the same engineering tool. Engineers must identify the exact device model and software package before starting a project.

1.2 Engineering software and device documentation

Before beginning engineering work, collect the following information:

  1. Relay model and ordering information.
  2. Hardware configuration and installed modules.
  3. Firmware version.
  4. Engineering software name and release.
  5. Device communication interface.
  6. Applicable device manuals.
  7. Approved protection setting calculations.
  8. Substation communication and network design.
  9. Approved input/output and trip matrix.
  10. Project-specific configuration requirements.

A common engineering mistake is to begin configuration using software intended for a different relay generation or hardware variant. This can cause missing parameters, unsupported functions, incorrect device selection, or unsuccessful communication.

2. Relay Project Creation and Device Selection

The first stage of relay engineering is creating a project that represents the actual protection and control installation.

A well-organized engineering project makes it easier to manage settings, configuration files, communication parameters, and commissioning records.

2.1 Project structure

A typical project may represent an entire substation, a protection system, or an individual bay.

For example:

Substation project

  • Substation name and voltage levels.
  • Busbar arrangement.
  • Transformer bays.
  • Incoming and outgoing feeder bays.
  • Bus coupler and bus section bays.
  • Generator or motor bays.
  • Protection and control devices.
  • Communication network.
  • Signal and control relationships.

An example project hierarchy is:

Substation Project
│
├── 400 kV Switchyard
│   ├── Line Bay 1
│   │   ├── Line Protection Relay
│   │   └── Bay Control Device
│   │
│   └── Line Bay 2
│
├── 132 kV Switchyard
│   ├── Transformer Bay 1
│   │   ├── Transformer Protection Relay
│   │   └── Bay Control Device
│   │
│   └── Feeder Bay 1
│
└── Station Communication
    ├── Ethernet Network
    ├── Station HMI
    └── Gateway

This is an illustrative project structure rather than a mandatory NARI software hierarchy.

2.2 Creating a new project

A typical project creation workflow includes:

  1. Open the applicable NARI engineering software.
  2. Select the new-project function.
  3. Enter the project name.
  4. Define the project directory.
  5. Enter substation or application information if required.
  6. Define the relevant voltage level and bay structure.
  7. Add the required protection devices.
  8. Save the project.
  9. Create a backup before detailed configuration.

Project naming should be consistent and descriptive.

For example:

SUBSTATION_132kV_LINE_BAY_01

A revision-controlled naming convention can also be used:

SUBSTATION_LINE_BAY_01_REV02

2.3 Device selection

Correct device selection is essential because different relay models may have different:

  • Protection functions.
  • Current and voltage input arrangements.
  • Binary input and output capacities.
  • Communication interfaces.
  • Hardware options.
  • Programmable logic capabilities.
  • Firmware requirements.
  • Engineering software compatibility.

Before selecting a device, verify the complete model designation and ordering information.

2.4 Hardware configuration

The hardware configuration should reflect the physical device installed in the panel.

Typical information includes:

  • Main processor module.
  • Current measurement inputs.
  • Voltage measurement inputs.
  • Binary input modules.
  • Binary output modules.
  • Communication ports.
  • Power supply module.
  • Optional extension modules.

The engineer must compare the software configuration against the actual device hardware.

A mismatch between the project configuration and installed hardware can result in unavailable signals, incorrect I/O assignments, or failed configuration transfer.

3. Online and Offline Engineering

NARI relay engineering may involve offline configuration, online communication, or a combination of both.

Understanding the difference is important because offline engineering does not necessarily prove that the physical relay has the same configuration as the project.

3.1 Offline engineering

Offline engineering means preparing or editing the relay project without an active connection to the physical device.

Typical offline activities include:

  • Creating a new relay project.
  • Selecting the relay model.
  • Configuring protection functions.
  • Entering protection settings.
  • Preparing communication parameters.
  • Assigning binary inputs and outputs.
  • Preparing logic configuration.
  • Reviewing parameter consistency.
  • Saving engineering files.

Advantages of offline engineering

  • Configuration can be prepared before site commissioning.
  • Engineering work does not require continuous relay access.
  • Project revisions can be reviewed and approved.
  • Settings can be checked before download.
  • Configuration work can be performed without interfering with an operating installation.

Offline engineering should be the normal starting point for new installations and major configuration changes.

3.2 Online engineering

Online engineering involves establishing communication between the engineering computer and the physical relay.

Depending on the supported model and software, online functions may include:

  • Reading device identification.
  • Checking firmware and hardware information.
  • Monitoring measurements.
  • Reading active settings.
  • Retrieving event records.
  • Retrieving fault or disturbance records.
  • Reading diagnostic information.
  • Downloading approved settings or configuration.
  • Performing supported device maintenance operations.

3.3 Online and offline comparison

Before transferring configuration, compare the offline project with the actual device.

Important comparison items include:

ParameterOffline projectPhysical relay
Device modelVerifyVerify
FirmwareVerify compatibilityRead actual version
Protection settingsApproved valuesExisting values
CT ratioProject designInstalled configuration
VT ratioProject designInstalled configuration
Binary inputsProject allocationActual wiring
Binary outputsProject allocationActual wiring
CommunicationNetwork designActual device configuration

The objective is to identify differences before making changes.

3.4 Important safety consideration

Online access to a relay in service must be controlled.

A configuration download, output test, logic change, or setting modification may affect protection performance. Such operations must follow the site’s approved switching, isolation, permit-to-work, and protection management procedures.

Reading measurements and retrieving records are not equivalent to changing protection parameters.

4. Parameter Configuration

Parameter configuration defines how the relay operates within the protection and control system.

It includes general device parameters, measurement parameters, protection function parameters, communication settings, and logic-related configuration where supported.

4.1 General device parameters

Typical device parameters may include:

  • System frequency.
  • Nominal current.
  • Nominal voltage.
  • Current transformer ratio.
  • Voltage transformer ratio.
  • Phase sequence.
  • Measurement configuration.
  • Device identification.
  • Time synchronization settings.

These parameters must match the approved project design.

4.2 CT configuration

Current transformer parameters directly influence the relay’s interpretation of primary system currents.

For example, assume:

  • Primary CT rating: 800 A.
  • Secondary CT rating: 1 A.

The CT ratio is:

\[ CTR=\frac{800}{1}=800 \]

If the primary current is 400 A, the ideal secondary current is:

\[ I_s=\frac{400}{800}=0.5\text{ A} \]

The engineer must verify that the relay configuration uses the correct CT ratio and that the physical CT secondary wiring is consistent with the design.

Incorrect CT ratios can cause incorrect protection pickup values and measurement readings.

4.3 VT configuration

Voltage transformer ratios must also be configured correctly.

For example:

  • Primary voltage: 132 kV.
  • Secondary voltage: 110 V.

The ratio is:

\[ VTR=\frac{132000}{110}=1200 \]

The relay must use the correct nominal voltage and ratio according to its measurement configuration.

Engineers should also verify the VT connection type, phase assignment, and any residual voltage measurement arrangement.

4.4 Protection function configuration

Depending on the relay application, configurable protection functions may include:

ANSI functionProtection function
50Instantaneous overcurrent
51Time overcurrent
50N/51NEarth-fault overcurrent
67Directional overcurrent
67NDirectional earth fault
27Undervoltage
59Overvoltage
46Negative-sequence protection
49Thermal overload
21Distance protection
87TTransformer differential protection
87BBusbar differential protection
87GGenerator differential protection
50BFBreaker failure protection

The availability and implementation of each function depend on the exact NARI relay model.

4.5 Protection settings versus configuration parameters

It is important to distinguish between protection settings and application configuration.

Protection settings define values such as:

  • Pickup current.
  • Operating time.
  • Time multiplier.
  • Characteristic curve.
  • Differential restraint settings.
  • Distance protection reach.
  • Directional angle.
  • Voltage thresholds.

Application configuration defines how the relay uses its available functions and signals, including:

  • Enabled or disabled functions.
  • Binary input assignments.
  • Binary output assignments.
  • Logic connections.
  • Communication signals.
  • Trip matrix relationships.

Both must be checked before commissioning.

4.6 Parameter validation

Before transferring a configuration, check:

  1. Device model.
  2. Nominal current and voltage.
  3. CT and VT ratios.
  4. Protection function availability.
  5. Pickup and operating values.
  6. Setting group selection.
  7. Binary input allocation.
  8. Binary output allocation.
  9. Trip logic.
  10. Communication parameters.
  11. Configuration consistency.
  12. Revision and approval status.

5. Communication Setup

Communication configuration is a major part of modern NARI relay engineering.

A protection relay may communicate with engineering software, a bay control system, station HMI, gateway, SCADA system, or other protection devices.

The communication architecture depends on the project design and supported device capabilities.

5.1 Communication interfaces

Depending on the device, available interfaces may include:

  • Ethernet.
  • Serial communication.
  • Optical communication.
  • Front-panel engineering interfaces.
  • Rear communication ports.

The physical interface must be confirmed from the relay hardware documentation.

5.2 Ethernet configuration

Typical Ethernet parameters include:

ParameterExample
IP address192.168.10.101
Subnet mask255.255.255.0
Default gateway192.168.10.1
Device nameLINE_PROT_01
Network portAccording to design

These values are illustrative only.

The actual network settings must be assigned according to the approved substation network design.

5.3 Communication protocols

Depending on the device and project, communication protocols may include:

  • IEC 61850.
  • IEC 60870-5-103.
  • Modbus.
  • Other manufacturer-supported or project-specific protocols.

Engineers must verify the exact protocol support and implementation for the relay model.

5.4 IEC 61850 configuration

Where IEC 61850 is supported, the relay may exchange information with other IEDs and station-level systems.

Typical engineering activities include:

  • Device identification.
  • Logical device and logical node configuration.
  • Data object configuration.
  • Report control configuration.
  • GOOSE publishing.
  • GOOSE subscription.
  • Communication network assignment.
  • SCL file management.

IEC 61850 engineering may involve SCL files such as:

  • ICD — IED Capability Description.
  • CID — Configured IED Description.
  • SCD — Substation Configuration Description.
  • IID — Instantiated IED Description.

The exact supported SCL workflow depends on the device and engineering software.

5.5 GOOSE communication

GOOSE messages can be used for fast communication between protection and control devices.

Typical applications include:

  • Interlocking.
  • Breaker failure initiation.
  • Direct transfer trip.
  • Busbar protection signals.
  • Blocking signals.
  • Protection status exchange.

For GOOSE communication, engineers must verify:

  • Publisher configuration.
  • Subscriber configuration.
  • Dataset.
  • GoCB configuration.
  • Application ID.
  • VLAN settings where applicable.
  • MAC address.
  • Network connectivity.
  • Message supervision.
  • Correct signal mapping.

A GOOSE message appearing on the network does not automatically prove that the intended protection logic is operating correctly. The complete publisher-to-subscriber signal path must be tested.

6. Relay Setting Download and Upload

Downloading and uploading settings are important engineering operations.

However, engineers must understand the difference between transferring protection settings and transferring a complete device configuration.

Depending on the model and software, these may be separate operations.

6.1 Downloading settings

Downloading transfers supported setting or configuration data from the engineering project to the relay.

A typical workflow is:

  1. Open the approved engineering project.
  2. Confirm the target relay model.
  3. Verify device identity.
  4. Establish communication.
  5. Read the device’s existing configuration where supported.
  6. Compare the existing configuration with the approved project.
  7. Confirm the intended download scope.
  8. Verify the setting and configuration revision.
  9. Perform the download using the approved procedure.
  10. Confirm the transfer result.
  11. Read back and verify the relevant parameters.
  12. Record the operation in the commissioning report.

6.2 Uploading settings

Uploading retrieves supported information from the physical relay to the engineering computer.

It may be used to:

  • Recover an existing device configuration.
  • Compare actual settings with approved settings.
  • Investigate an operational problem.
  • Create a maintenance backup.
  • Review changes made during previous commissioning.

A typical workflow includes:

  1. Connect to the relay.
  2. Verify the device identity.
  3. Select the supported upload or read function.
  4. Retrieve the relevant setting or configuration data.
  5. Save the retrieved data under a controlled filename.
  6. Compare it against the approved engineering project.
  7. Record any differences.

6.3 Important difference between upload and download

OperationData directionTypical purpose
DownloadEngineering software to relayApply approved configuration
Upload/readRelay to engineering softwareRetrieve existing configuration

The exact scope of each operation depends on the engineering software.

6.4 Backup and revision control

Before changing a relay configuration, preserve the existing configuration wherever supported.

A useful file naming convention is:

SUBSTATION_BAY01_NARI_BACKUP_2026-11-21
SUBSTATION_BAY01_NARI_APPROVED_REV03
SUBSTATION_BAY01_NARI_AS_BUILT_REV04

The backup should include relevant information such as:

  • Relay model.
  • Serial number.
  • Firmware version.
  • Engineering software version.
  • Date of retrieval.
  • Engineer responsible.
  • Configuration revision.

Do not assume that a successful transfer proves that the relay has the intended final protection behavior. Functional testing and read-back verification remain necessary.

7. Event and Fault Record Retrieval

Event and fault records are essential for troubleshooting and post-fault analysis.

They help engineers understand what happened before, during, and after a disturbance.

7.1 Event records

Event records may include:

  • Protection pickup.
  • Protection operation.
  • Trip command.
  • Breaker status change.
  • Binary input activation.
  • Communication alarm.
  • Setting group change.
  • Device alarm.
  • Self-supervision event.

The exact event content and storage capacity vary by relay model.

7.2 Fault and disturbance records

Disturbance records may contain sampled current and voltage signals, binary status signals, and other information captured during a fault or abnormal operating condition.

Depending on the relay, records may be available in COMTRADE or another supported format.

COMTRADE is standardized by IEC 60255-24.

7.3 Retrieving records

A general retrieval procedure is:

  1. Establish communication with the relay.
  2. Verify the device identity and time.
  3. Open the event or disturbance record function.
  4. Review the available records.
  5. Select the required event or disturbance.
  6. Retrieve the record.
  7. Save the original file.
  8. Open the record using compatible analysis software.
  9. Compare the recorded signals with relay indications and system conditions.
  10. Prepare an engineering report.

7.4 Fault record analysis

For a feeder fault, engineers may investigate:

  • Phase current behavior.
  • Earth-fault current.
  • Voltage depression.
  • Protection pickup.
  • Directional decision.
  • Operating time.
  • Trip command.
  • Circuit breaker opening.
  • Fault clearance.

A typical event sequence could be:

TimeEvent
10:15:32.100Fault current detected
10:15:32.115Overcurrent protection pickup
10:15:32.250Protection trip command
10:15:32.310Circuit breaker opens

These values are illustrative and do not represent a specific NARI relay operating time.

7.5 Using fault records for troubleshooting

A disturbance record can help identify:

  • Incorrect protection pickup.
  • Unexpected directional operation.
  • Incorrect CT polarity.
  • VT circuit problems.
  • Incorrect trip logic.
  • Breaker operating delays.
  • Communication failures.
  • Incorrect setting group selection.

The engineer should correlate relay records with station event logs, SCADA indications, breaker records, and other relevant system evidence.

8. Firmware and Compatibility Management

Firmware management is an important part of relay lifecycle management.

Firmware updates may introduce new functions, correct software defects, improve communication compatibility, or address cybersecurity issues.

However, firmware changes must be carefully controlled.

8.1 Why firmware compatibility matters

A relay’s firmware version may determine:

  • Available protection functions.
  • Supported communication protocols.
  • Engineering software compatibility.
  • Parameter structure.
  • SCL compatibility.
  • Event record behavior.
  • Communication performance.
  • Supported hardware modules.

A project created using one software release may not be fully compatible with an older device firmware.

8.2 Compatibility checks

Before firmware-related work, verify:

  1. Exact relay model.
  2. Hardware version.
  3. Existing firmware version.
  4. Target firmware version.
  5. Required engineering software release.
  6. Manufacturer upgrade instructions.
  7. Configuration conversion requirements.
  8. Backup and recovery procedure.
  9. Project-specific approval.
  10. Required post-update testing.

8.3 Firmware upgrade procedure

A controlled firmware upgrade generally involves:

  1. Confirming the technical reason for the upgrade.
  2. Checking manufacturer release documentation.
  3. Verifying hardware and firmware compatibility.
  4. Backing up existing configuration and settings.
  5. Recording the current firmware version.
  6. Obtaining the approved firmware package.
  7. Confirming the upgrade procedure for the exact model.
  8. Performing the upgrade under an approved maintenance plan.
  9. Verifying the new firmware version.
  10. Checking device self-supervision and communication.
  11. Verifying settings and configuration.
  12. Performing required functional tests.
  13. Updating the device maintenance record.

Firmware upgrading should never be treated as a routine configuration download.

An incorrect firmware package or interrupted update can make a device unavailable or require manufacturer intervention.

8.4 Firmware and configuration backups

A complete maintenance record should preserve:

  • Original configuration.
  • Approved configuration.
  • Existing firmware version.
  • Updated firmware version.
  • Software compatibility information.
  • Upgrade date.
  • Upgrade reason.
  • Test results.
  • Responsible engineer.

9. Practical Relay Configuration Projects

Practical projects are essential for developing confidence in NARI engineering software.

The following examples illustrate typical engineering activities. They are generic workflows and must be adapted to the exact supported relay model.

Project 1: Feeder protection relay configuration

Objective: Configure a feeder protection relay for a medium-voltage or high-voltage feeder.

Typical engineering steps:

  1. Create a new project.
  2. Select the appropriate NARI feeder protection device.
  3. Verify the device hardware configuration.
  4. Configure CT and VT ratios.
  5. Enable the required protection functions.
  6. Enter approved overcurrent settings.
  7. Configure earth-fault protection.
  8. Configure directional protection if required.
  9. Assign binary inputs.
  10. Assign trip and alarm outputs.
  11. Configure communication parameters.
  12. Save the project.
  13. Download the approved configuration where authorized.
  14. Verify settings and perform functional tests.

Example protection functions

FunctionANSI number
Phase overcurrent50/51
Earth-fault overcurrent50N/51N
Directional overcurrent67
Directional earth fault67N
Undervoltage27
Breaker failure50BF

Project 2: Transformer protection relay configuration

Objective: Prepare the configuration of a transformer protection relay.

Typical engineering activities include:

  • Transformer rating configuration.
  • CT ratio configuration.
  • Transformer vector group definition.
  • Differential protection settings.
  • Bias or restraint characteristic configuration.
  • Harmonic restraint configuration where supported.
  • Restricted earth-fault protection configuration where supported.
  • Transformer overcurrent backup protection.
  • Binary input and output assignment.
  • Trip logic configuration.

Important engineering considerations

Transformer differential protection requires careful verification of:

  • Transformer vector group.
  • CT ratios.
  • CT polarity.
  • Phase compensation.
  • Differential operating characteristic.
  • Restraint settings.
  • Inrush stabilization.
  • Overexcitation restraint where applicable.

Incorrect transformer or CT data can lead to unwanted differential operation or reduced sensitivity to internal faults.

Project 3: Distance protection relay configuration

Objective: Configure a transmission line protection relay.

Typical engineering activities include:

  1. Configure nominal current and voltage.
  2. Enter line impedance data.
  3. Define line length and relevant system data.
  4. Configure distance zones.
  5. Configure zone operating times.
  6. Define directional characteristics.
  7. Configure power swing blocking if required and supported.
  8. Configure autoreclosing if included in the application.
  9. Configure teleprotection or communication-assisted schemes where applicable.
  10. Verify trip logic and breaker failure initiation.

The engineer must consider:

  • Positive-sequence impedance.
  • Zero-sequence compensation.
  • Line impedance angle.
  • Zone reach.
  • Remote infeed and outfeed.
  • Mutual coupling where relevant.
  • Load encroachment.
  • Fault resistance.
  • System stability requirements.

The actual distance protection characteristics and available functions are model-specific.

Project 4: Binary input and output configuration

Objective: Configure the relay interface with the substation control and protection circuits.

Typical binary inputs may include:

  • Circuit breaker open.
  • Circuit breaker closed.
  • Local/remote selector.
  • Protection trip circuit supervision.
  • External protection trip.
  • Isolator position.
  • Earthing switch position.
  • External blocking signal.

Typical binary outputs may include:

  • Protection trip.
  • Alarm.
  • Breaker failure initiation.
  • Protection operation indication.
  • Disturbance recorder trigger.
  • Interlocking output.

The engineer must compare the software allocation with the approved wiring diagrams and actual terminal connections.

Project 5: IEC 61850 communication configuration

Objective: Prepare IEC 61850 communication for a supported NARI IED.

Typical engineering activities include:

  1. Verify IEC 61850 support.
  2. Identify the supported SCL workflow.
  3. Prepare or import the relevant engineering files.
  4. Configure the required logical devices and nodes.
  5. Configure report control blocks.
  6. Define datasets.
  7. Configure GOOSE publishers where required.
  8. Configure GOOSE subscribers where required.
  9. Verify network settings.
  10. Check signal mapping.
  11. Test communication with the station system.
  12. Verify protection and control signal behavior.

Communication testing should include both network-level verification and application-level functional testing.

10. Troubleshooting Real Engineering Cases

Troubleshooting requires a systematic approach.

Instead of changing parameters randomly, engineers should identify the failure stage, collect evidence, and verify each part of the engineering chain.

Case 1: Engineering software cannot connect to the relay

Possible causes

  • Incorrect IP address.
  • Incorrect subnet mask.
  • Network cable problem.
  • Incorrect communication port.
  • Firewall restrictions.
  • Wrong communication settings.
  • Device not powered.
  • Unsupported software or communication driver.
  • Incorrect interface selection.

Recommended checks

  1. Confirm relay power and device status.
  2. Check the physical Ethernet or serial connection.
  3. Verify the computer’s network configuration.
  4. Confirm the relay IP address.
  5. Check whether the computer and relay are on the correct network.
  6. Check the selected communication interface.
  7. Verify the supported protocol and port.
  8. Review software diagnostic messages.
  9. Check the network switch and VLAN configuration where applicable.

Do not change the relay’s IP address without confirming the approved network design.

Case 2: Download operation fails

Possible causes

  • Wrong relay model selected.
  • Firmware incompatibility.
  • Unsupported configuration feature.
  • Communication interruption.
  • Device access restrictions.
  • Incorrect software version.
  • Configuration integrity problem.

Recommended checks

  • Verify device identification.
  • Confirm firmware compatibility.
  • Compare the project model with the physical relay.
  • Check software release information.
  • Review the transfer error message.
  • Verify the approved download scope.
  • Retry only after identifying and correcting the cause.

Case 3: Uploaded settings do not match the engineering project

Possible causes

  • Different project revision.
  • Previous engineering changes.
  • Incorrect device selected.
  • Different setting group active.
  • Some settings were not included in the transfer.
  • Different parameter interpretation or software version.

Recommended checks

  1. Retrieve the current device settings.
  2. Save the retrieved configuration separately.
  3. Compare the device and project revisions.
  4. Check active setting group selection.
  5. Identify individual differences.
  6. Confirm the approved setting file.
  7. Prepare a controlled correction plan.

Never overwrite an existing relay configuration simply because it differs from the engineering project. First establish which revision is approved and why the difference exists.

Case 4: Relay measurements are incorrect

Possible causes

  • Incorrect CT ratio.
  • Incorrect VT ratio.
  • Wrong phase sequence.
  • CT polarity error.
  • VT wiring error.
  • Incorrect measurement configuration.
  • Incorrect nominal frequency.
  • Incorrect phase assignment.

Recommended checks

  • Compare relay measurements with calibrated test equipment.
  • Verify CT and VT nameplate data.
  • Check wiring diagrams.
  • Verify secondary circuit connections.
  • Check phase sequence.
  • Confirm measurement scaling.
  • Perform injection tests as required.

Case 5: GOOSE communication is not working

Possible causes

  • Incorrect publisher configuration.
  • Incorrect subscriber configuration.
  • Dataset mismatch.
  • Wrong GoCB reference.
  • Incorrect application ID.
  • Incorrect VLAN configuration.
  • Network switch configuration issue.
  • Incorrect signal mapping.
  • Incompatible configuration files.

Recommended checks

  1. Verify that the publisher is configured correctly.
  2. Verify the subscriber configuration.
  3. Compare the relevant SCL files.
  4. Check the GOOSE control block and dataset.
  5. Verify VLAN and network settings.
  6. Use an appropriate network analysis tool if permitted.
  7. Confirm that the receiving IED recognizes the subscribed message.
  8. Test the complete application logic.

Case 6: Fault records cannot be retrieved

Possible causes

  • Communication problem.
  • Unsupported record retrieval function.
  • Incorrect software version.
  • Record storage limitation.
  • Incorrect retrieval procedure.
  • Device memory or record management issue.

Recommended checks

  • Confirm device communication.
  • Check the relay’s record menu or supported software function.
  • Verify the device manual.
  • Check record availability and storage status.
  • Retrieve records using the supported method.
  • Preserve the original record files.

Case 7: Firmware upgrade or compatibility problem

Possible causes

  • Firmware package intended for another model.
  • Hardware revision incompatibility.
  • Incorrect upgrade sequence.
  • Unsupported software release.
  • Incomplete upgrade.
  • Configuration conversion issue.

Recommended checks

  • Verify the exact relay model and hardware.
  • Check the manufacturer’s firmware release information.
  • Confirm the approved upgrade sequence.
  • Preserve all available backups.
  • Follow the device-specific recovery procedure.
  • Contact the manufacturer if the device enters an abnormal state.

Case 8: Protection settings are correct but the relay does not trip

Possible causes

  • Protection function disabled.
  • Wrong setting group active.
  • Binary output not assigned.
  • Trip logic not connected.
  • Blocking signal active.
  • Breaker trip circuit problem.
  • Incorrect binary input state.
  • Incorrect output mapping.

Recommended checks

  1. Verify the protection element pickup.
  2. Check the active setting group.
  3. Review the protection operation logic.
  4. Verify blocking and interlocking conditions.
  5. Check the trip output assignment.
  6. Test the binary output.
  7. Verify the external trip circuit.
  8. Check circuit breaker trip coil and auxiliary supply.
  9. Review event records and disturbance records.

This case demonstrates why relay configuration must be verified as a complete protection chain rather than as a collection of individual setting values.

11. Recommended NARI Relay Engineering Workflow

A consistent workflow helps reduce configuration errors and improves project traceability.

Engineering lifecycle

  1. Project preparationCollect relay models, manuals, firmware information, drawings, and approved protection calculations.
  2. Project creationCreate the engineering project and select the correct device.
  3. ConfigurationConfigure hardware, measurement parameters, protection functions, logic, and communication.
  4. Engineering verificationReview settings, signal mapping, configuration consistency, and software compatibility.
  5. Device communicationEstablish online communication and verify the actual device identity.
  6. Configuration transferBack up the existing configuration and transfer approved data using the supported procedure.
  7. Commissioning testsVerify measurements, protection functions, binary I/O, trip circuits, and communication.
  8. Final documentationRetrieve final settings, preserve backups, record firmware versions, and issue as-built documents.

12. Practical Engineering Checklist

The following checklist can be used as a starting point for NARI relay configuration and commissioning. It must be adapted to the exact device and project.

Project preparation

  • Confirm relay model and ordering information.
  • Confirm hardware configuration.
  • Confirm firmware version.
  • Confirm engineering software compatibility.
  • Obtain approved protection calculations.
  • Obtain approved wiring diagrams.
  • Obtain communication network documentation.
  • Create a controlled project backup.

Configuration

  • Select the correct relay model.
  • Configure CT and VT ratios.
  • Configure nominal frequency.
  • Enable required protection functions.
  • Enter approved protection settings.
  • Configure setting groups where applicable.
  • Assign binary inputs.
  • Assign binary outputs.
  • Verify trip logic.
  • Configure communication parameters.
  • Check configuration consistency.

Online engineering

  • Confirm physical communication.
  • Verify device identity.
  • Read actual device parameters.
  • Compare actual and approved settings.
  • Confirm transfer scope.
  • Download approved configuration if authorized.
  • Read back and verify relevant parameters.

Commissioning

  • Verify CT circuits.
  • Verify VT circuits.
  • Check current and voltage measurements.
  • Test protection functions.
  • Test binary inputs and outputs.
  • Verify trip circuit operation.
  • Test communication signals.
  • Verify GOOSE functions where applicable.
  • Retrieve event records.
  • Retrieve disturbance records where applicable.

Documentation

  • Save final engineering project.
  • Save final settings.
  • Record firmware version.
  • Record engineering software version.
  • Save test reports.
  • Record configuration changes.
  • Prepare as-built documentation.
  • Archive backups under revision control.

13. Best Practices for NARI Relay Engineering

13.1 Always verify the device model

Never assume that different NARI relays use identical engineering procedures. Confirm the exact model, hardware, and firmware before configuration.

13.2 Keep project files under revision control

Use controlled project directories and descriptive filenames. Preserve the original configuration, approved configuration, and final as-built configuration separately.

13.3 Separate approved settings from working settings

Protection setting calculations should be reviewed and approved before they are entered into the relay. Working files must not be confused with approved operational settings.

13.4 Verify before downloading

Compare the engineering project with the actual device. Check the target relay, active setting group, configuration revision, and intended transfer scope.

13.5 Read back after configuration changes

A successful download message is not sufficient evidence that all intended parameters have been applied. Read back and verify relevant settings wherever supported.

13.6 Test the complete protection chain

Protection testing should cover:

  • CT and VT measurement.
  • Protection element operation.
  • Internal logic.
  • Binary output.
  • Trip circuit.
  • Circuit breaker response.
  • Communication signals where applicable.

13.7 Preserve original fault records

Keep original event and disturbance records before performing analysis or conversion. Preserve timestamps and device identification information.

13.8 Treat firmware updates as controlled maintenance

Do not update firmware without a documented reason, verified compatibility, manufacturer instructions, backups, and an approved testing plan.

13.9 Document every engineering change

Every change should have a clear reason, responsible engineer, date, approval status, and revision reference.

14. Applicable IEC Standards and Technical References

The following standards are relevant to different aspects of protection relay engineering, testing, communication, and disturbance analysis.

StandardEngineering subject
IEC 60255 seriesMeasuring relays and protection equipment
IEC 60255-1Common requirements for measuring relays and protection equipment
IEC 60255-24COMTRADE disturbance data exchange format
IEC 61850 seriesCommunication networks and systems for power utility automation
IEC 61850-6Configuration description language for communication in electrical substations
IEC 61850-8-1Specific communication service mapping to MMS and Ethernet
IEC 61850-9-2Sampled values communication mapping
IEC 60870-5-103Communication protocol for protection equipment
IEC 60870-5-104Network access for IEC 60870-5-101
IEC 62351 seriesPower system management and associated information exchange security

The applicable standards depend on the relay functions, communication architecture, and project requirements. Their inclusion does not imply that every NARI relay supports every standard or protocol.

Primary technical references should include:

  • The specific NARI relay hardware manual.
  • The specific NARI relay application and operation manual.
  • The applicable NARI engineering software manual.
  • The firmware release notes.
  • The approved protection setting document.
  • The approved substation communication architecture.
  • The project-specific commissioning procedure.

15. NARI Relay Engineering and Practical Training by Elec-Engg

Understanding relay engineering software is an essential skill for protection, commissioning, and substation automation engineers.

However, practical engineering competence requires more than knowing where to find parameters in a software menu. Engineers must understand why each parameter is required, how it affects relay behavior, and how to verify the final configuration in the field.

Elec-Engg provides practical power system protection and substation automation education through structured online courses, recorded technical training, customized company training, and face-to-face programs.

Practical courses by Dr Saeed Roostaee / Elec-Engg focus on engineering applications and real commissioning and maintenance activities.

Relevant training subjects include:

  • Protection relay engineering and configuration.
  • Protection setting calculation and verification.
  • CT and VT circuit verification.
  • Binary input and output configuration.
  • Protection function testing.
  • Relay testing and commissioning.
  • IEC 61850 engineering.
  • GOOSE communication and troubleshooting.
  • Substation automation and SCADA.
  • Fault record retrieval and analysis.
  • Practical engineering software applications.

The objective is to help engineers develop the ability to work with protection devices systematically, understand the relationship between software configuration and physical wiring, and identify problems encountered during real projects.

Explore the technical training resources at:

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

For NARI-specific training, the exact relay model, engineering software, firmware version, and practical application should be identified before defining the training scope.

16. Conclusion

NARI relay engineering software is an important part of protection system design, configuration, commissioning, and maintenance.

A reliable engineering workflow includes project creation, correct device selection, offline configuration, online verification, parameter management, communication setup, controlled setting transfer, event and fault record retrieval, and firmware compatibility management.

The most important engineering principle is that a relay configuration must always be verified against the actual protection design and physical installation.

Correct settings alone do not guarantee correct protection operation. CT and VT circuits, binary inputs and outputs, internal logic, trip circuits, communication signals, and circuit breaker interfaces must all work together as intended.

By following a structured engineering process, maintaining revision-controlled backups, and performing systematic commissioning tests, engineers can improve the reliability, traceability, and maintainability of NARI-based protection and control systems.

Leave a Comment

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

Scroll to Top