- Introduction
- 1. What Is Firmware in a MiCOM Protection Relay?
- 2. Why Do MiCOM Relays Need Firmware Updates?
- 3. MiCOM Relay Families and Firmware Compatibility
- 4. Identifying the Installed Firmware Version
- 5. Understanding Firmware Release Information
- 6. Preparing for a MiCOM Firmware Upgrade
- 7. General MiCOM Firmware Upgrade Workflow
- 8. Firmware Upgrade and Protection Settings
- 9. Firmware Upgrade and IEC 61850 Compatibility
- 10. Post-Upgrade Testing
- 11. Testing IEC 61850 Communication with Wireshark
- 12. Common Problems During MiCOM Firmware Upgrades
- Problem 1: Firmware package rejected
- Problem 2: Engineering software cannot identify the relay
- Problem 3: Configuration is different after upgrading
- Problem 4: MMS communication fails after upgrading
- Problem 5: GOOSE messages are no longer received
- Problem 6: Relay does not start normally after upgrading
- 13. Firmware Rollback and Recovery Planning
- 14. Practical Example: Firmware Upgrade of a MiCOM P443 Distance Relay
- 15. Best Practices for Firmware Management
- 16. MiCOM Firmware Upgrade and Commissioning Checklist
- 17. Training on MiCOM Protection Relays and Commissioning
- Conclusion
Introduction
Firmware management is an important part of maintaining MiCOM protection relays throughout their operational lifecycle. Firmware determines how a relay executes its protection functions, processes measurements, communicates with other devices, and implements supported engineering features.
For protection and commissioning engineers, a firmware upgrade is not simply a software installation. It is a controlled engineering activity that can affect protection functionality, communication services, IEC 61850 data models, configuration compatibility, and operational availability.
An incorrectly selected firmware package or an improperly executed upgrade can result in configuration problems, communication failures, unexpected device behavior, or the need to restore the relay.
This article explains how to identify MiCOM firmware versions, select compatible packages, prepare for upgrades, manage risks, and perform post-upgrade verification.
The procedures described are general engineering principles. The exact upgrade method must always follow the manufacturer’s instructions for the specific MiCOM model, hardware revision, and firmware release.
1. What Is Firmware in a MiCOM Protection Relay?
Firmware is the embedded software installed inside a protection relay.
It controls the relay’s internal operation and provides the software implementation of its supported functions.
Depending on the relay model, firmware may include:
- Protection algorithms.
- Measurement processing.
- Fault detection and recording.
- Binary input processing.
- Binary output operation.
- Programmable logic execution.
- Communication protocols.
- IEC 61850 services.
- Event and disturbance recording.
- Device diagnostics.
- User interface functions.
- Security and access-control features.
Firmware is therefore directly related to both protection performance and substation automation functionality.
For example, a MiCOM feeder protection relay may use firmware to implement overcurrent protection, earth-fault protection, breaker monitoring, event recording, and IEC 61850 communication.
The available features depend on the particular relay implementation.
2. Why Do MiCOM Relays Need Firmware Updates?
Manufacturers may release firmware updates to correct problems, improve device operation, introduce new features, or maintain compatibility with engineering tools and communication systems.
Typical reasons for firmware updates include the following.
2.1 Correction of software defects
A firmware release may correct identified problems in earlier versions.
Examples may include:
- Incorrect operation under a particular operating condition.
- Communication interruptions.
- Event-recording issues.
- Device restart problems.
- Incorrect handling of certain input signals.
- Problems affecting a specific protection function.
The actual corrections must be checked in the relevant release notes.
2.2 New protection features
Some firmware releases may introduce additional protection functions or improvements to existing functions.
Examples can include enhancements to:
- Overcurrent protection.
- Earth-fault protection.
- Directional protection.
- Distance protection.
- Transformer differential protection.
- Breaker failure protection.
- Monitoring and supervision.
Not every firmware update introduces new protection functions, and the availability of a function also depends on the relay’s order code and licensed or hardware-supported features.
2.3 IEC 61850 improvements
Firmware changes may also affect IEC 61850 communication.
Possible changes include:
- Additional supported data objects.
- Improvements to MMS communication.
- Changes to report behavior.
- GOOSE communication corrections.
- Improvements to communication diagnostics.
- Additional supported services.
- Changes to the device’s IEC 61850 data model.
Engineers should compare the relevant IEC 61850 documentation before and after an upgrade.
A new firmware version does not automatically mean that every IEC 61850 feature defined in the standard is supported.
2.4 Engineering software compatibility
An engineering software release may support particular firmware versions or device packages.
A project created with one software release may not be directly compatible with another device firmware version.
Before an upgrade, check the compatibility requirements between:
- Relay firmware.
- Engineering software.
- Device support packages.
- Configuration files.
- Communication modules.
- SCL descriptions.
3. MiCOM Relay Families and Firmware Compatibility
MiCOM is a broad product family covering several protection applications.
Examples include:
| Relay family or model | Typical application |
|---|---|
| MiCOM P123 | Feeder protection |
| MiCOM P127 | Feeder protection |
| MiCOM P139 | Feeder protection and control |
| MiCOM P141/P142/P143 | Feeder protection |
| MiCOM P220/P225 | Motor protection |
| MiCOM P343 | Generator protection |
| MiCOM P443 | Distance protection |
| MiCOM P546 | Line differential protection |
| MiCOM P643 | Transformer protection |
These examples represent different product generations and applications. They should not be treated as sharing a common firmware package or upgrade procedure.
Even within one model family, differences may exist in:
- Hardware platform.
- Order code.
- CPU or processor hardware.
- Communication module.
- Firmware release.
- Installed options.
- Engineering software support.
Important: Never select a firmware package based only on the relay’s front-panel model designation. Verify the exact device identification and manufacturer compatibility documentation.
4. Identifying the Installed Firmware Version
Before planning an upgrade, identify the firmware currently installed in the relay.
The available identification method depends on the MiCOM model.
Common approaches include:
- Checking the relay’s front-panel menus.
- Reading device information through the supported engineering software.
- Using an approved communication connection.
- Consulting device identification or maintenance records.
Record the following information:
| Information | Purpose |
|---|---|
| Relay model | Identifies the product family |
| Complete order code | Identifies the hardware and feature configuration |
| Serial number | Identifies the individual device |
| Firmware version | Identifies the installed embedded software |
| Hardware revision | Helps establish compatibility |
| Communication option | Identifies installed communication capability |
| Engineering software version | Helps confirm project compatibility |
A useful practice is to include this information in the relay’s maintenance record and configuration backup.
5. Understanding Firmware Release Information
Firmware packages are normally associated with a particular product and release.
Before installing a package, engineers should understand the information supplied by the manufacturer.
Important items include:
5.1 Firmware release number
The release number identifies the firmware version.
Do not assume that a higher-looking version number is automatically suitable for every device.
5.2 Release notes
Release notes describe the changes introduced by a firmware release.
They may include:
- New functions.
- Corrected defects.
- Known limitations.
- Upgrade instructions.
- Compatibility requirements.
- Restrictions or special considerations.
Release notes should be reviewed before any upgrade.
5.3 Hardware compatibility
Some firmware releases may be limited to particular hardware revisions or device variants.
The package must be suitable for the actual relay.
5.4 Upgrade path
Some devices may support direct upgrades between particular versions, while others may require intermediate steps or a specific procedure.
Never assume that any earlier version can be upgraded directly to the latest available release.
5.5 Configuration compatibility
A firmware update may affect the way configuration data is interpreted or stored.
Check whether:
- Existing settings are retained.
- Configuration conversion is required.
- New parameters are introduced.
- Existing parameters are modified or deprecated.
- IEC 61850 configuration needs to be regenerated.
- Engineering software must be updated.
6. Preparing for a MiCOM Firmware Upgrade
Preparation is one of the most important stages of a firmware upgrade.
A relay operating in a live substation may be responsible for protecting an important feeder, transformer, generator, or transmission line.
An upgrade must therefore be planned with the responsible protection and operations teams.
6.1 Obtain operational approval
Before beginning the work:
- Obtain the required maintenance authorization.
- Confirm the protection system’s operational status.
- Agree on the outage or maintenance window.
- Identify any required temporary protection arrangements.
- Coordinate with the control room.
- Confirm the responsible personnel.
Do not upgrade an in-service protection relay without an approved operational procedure.
6.2 Back up the existing configuration
Create a complete available backup before upgrading.
Depending on the relay, this may include:
- Engineering project.
- Protection settings.
- Programmable logic.
- Binary input/output assignments.
- Communication parameters.
- IEC 61850 configuration.
- SCL files.
- Relevant event and disturbance records.
Where possible, retrieve the actual configuration from the device and compare it with the approved project.
A saved engineering project is not necessarily proof that the relay currently contains the same configuration.
6.3 Record the original firmware version
Document the installed firmware version before beginning.
This information is important if troubleshooting or recovery becomes necessary.
6.4 Verify the firmware package
Confirm that the selected firmware package is approved for:
- Exact relay model.
- Complete order code.
- Hardware revision.
- Communication options.
- Current firmware version.
- Intended upgrade path.
Use the official manufacturer-provided package and instructions.
6.5 Prepare the engineering computer
Check:
- Compatible engineering software.
- Required device support packages.
- Supported operating environment.
- Communication drivers.
- Correct connection interface.
- Stable power supply.
- Availability of the required upgrade files.
Avoid unnecessary software changes during the upgrade activity.
7. General MiCOM Firmware Upgrade Workflow
The following is a general engineering sequence. It is not a universal menu-by-menu procedure.
The exact method varies by relay model and firmware release.
Step 1: Establish communication
Connect to the relay using a manufacturer-supported communication interface.
Verify that the relay can be identified correctly.
Do not proceed if the engineering software identifies a different device or reports an unexpected hardware configuration.
Step 2: Confirm the existing configuration
Retrieve the current configuration where supported.
Compare it with the approved project and investigate any differences.
Step 3: Verify the firmware package
Check the firmware package name, version, target device, and compatibility requirements.
Do not rename or modify firmware files unless the manufacturer specifically instructs you to do so.
Step 4: Review upgrade instructions
Read the applicable manufacturer documentation.
Check whether the upgrade requires:
- A particular starting firmware version.
- An intermediate upgrade.
- A specific engineering software release.
- Special device preparation.
- A defined restart or recovery procedure.
Step 5: Perform the upgrade
Follow the device-specific manufacturer procedure.
Maintain a stable power supply and communication connection as required by the instructions.
Do not interrupt the upgrade process unless the manufacturer explicitly directs you to do so.
Step 6: Verify the resulting firmware
After the upgrade, identify the firmware version again.
Confirm that the expected version is installed.
Step 7: Verify configuration
Check the relay configuration against the approved backup.
Investigate any missing, modified, or newly introduced parameters.
Step 8: Perform functional and communication tests
Carry out the required tests before returning the relay to service.
The test scope must reflect the protection functions and communication services used in the actual installation.
8. Firmware Upgrade and Protection Settings
One of the most important considerations is the relationship between firmware and protection settings.
An upgrade may preserve existing settings, but engineers must not assume this without checking the manufacturer’s documentation.
After an upgrade, verify important protection parameters such as:
- CT primary and secondary ratings.
- VT ratios.
- Rated frequency.
- Phase overcurrent settings.
- Earth-fault settings.
- Directional protection settings.
- Distance protection zones.
- Transformer differential settings.
- Restricted earth-fault settings.
- Generator protection settings.
- Breaker failure settings.
- Thermal protection parameters.
- Trip logic.
- Output assignments.
The exact list depends on the relay application.
Where settings are represented differently between firmware releases, review the applicable conversion or migration procedure.
A numerical comparison alone may not be sufficient if the meaning, scaling, or behavior of a parameter has changed.
9. Firmware Upgrade and IEC 61850 Compatibility
Firmware management becomes particularly important when MiCOM relays are integrated into IEC 61850 substations.
An upgrade may affect the device’s communication behavior or its IEC 61850 data model.
9.1 Logical nodes and data objects
Check whether the updated firmware changes the available logical nodes, data objects, or data attributes.
For example, a protection relay may provide logical nodes associated with:
- Overcurrent protection.
- Earth-fault protection.
- Distance protection.
- Protection trip.
- Circuit-breaker status.
- Measurements.
- Device health.
Examples of IEC 61850 logical node classes include PTOC, PIOC, PDIS, PTRC, XCBR, and MMXU.
Their actual availability and implementation must be confirmed for the particular MiCOM relay.
9.2 MMS communication
MMS provides client-server communication between an IEC 61850 IED and a client such as a SCADA gateway.
After a firmware upgrade, verify:
- MMS connection establishment.
- Logical device browsing.
- Logical node references.
- Data object access.
- Report control blocks.
- Dataset configuration.
- Quality attributes.
- Timestamps.
- Control services, where used.
MMS over TCP commonly uses port 102, but the existence of a TCP connection does not prove correct IEC 61850 application-level operation.
9.3 GOOSE communication
GOOSE is commonly used for fast peer-to-peer communication between IEDs.
After an upgrade, verify:
- GOOSE publisher configuration.
- Dataset membership.
- GOOSE control block.
- Multicast address.
- APPID.
- VLAN parameters.
- Subscriber external references.
- Configuration revision.
- Actual received signal behavior.
GOOSE uses Ethernet multicast communication and is not carried over TCP/IP.
A GOOSE configuration that worked before an upgrade should still be tested after the upgrade.
9.4 SCL file compatibility
Review the applicable ICD, CID, IID, and SCD files.
A new firmware release may require an updated device capability description or a revised IEC 61850 engineering configuration.
If the relay data model changes, the station-level engineering project may also need modification.
Do not assume that an old SCL file is automatically suitable for a new firmware version.
10. Post-Upgrade Testing
Post-upgrade testing is essential before returning the relay to operational service.
The scope should be defined by the protection design, manufacturer instructions, maintenance procedure, and actual firmware changes.
10.1 Device health checks
Check:
- Relay startup.
- Self-supervision status.
- Device alarms.
- Hardware diagnostics.
- Communication status.
- Front-panel operation.
- Event and disturbance recording.
Investigate any unexpected warning or alarm.
10.2 Protection function verification
Verify the protection functions required by the application.
Depending on the relay, this may include:
- Phase overcurrent.
- Earth-fault protection.
- Directional overcurrent.
- Distance protection.
- Differential protection.
- Restricted earth fault.
- Breaker failure.
- Thermal overload.
- Generator protection.
Use an approved test plan and suitable secondary injection equipment.
Where required, use an Omicron CMC test set with the appropriate Test Universe modules or another approved relay-testing system.
10.3 Binary input and output checks
Verify the binary inputs and outputs used by the protection and control scheme.
Check:
- External trip inputs.
- Blocking inputs.
- Breaker position indications.
- Trip outputs.
- Alarm outputs.
- Close circuit signals, where applicable.
- Interlocking signals.
10.4 Disturbance recording and event checks
Confirm that the required recording and event functions operate correctly.
Where applicable, verify:
- Event generation.
- Time information.
- Fault records.
- Oscillography.
- Record retrieval.
10.5 Communication testing
Test every communication service used by the installation.
For IEC 61850 systems, this may include MMS reporting, controls, GOOSE messaging, and sampled values where supported and implemented.
Do not limit the test to checking whether the relay appears online in the network.
11. Testing IEC 61850 Communication with Wireshark
Wireshark can help engineers inspect network traffic before and after a firmware upgrade.
It is especially useful when investigating communication changes.
11.1 MMS traffic
A useful display filter is:
tcp.port == 102
This helps identify traffic using the standard MMS TCP port.
Check whether the communication is established and whether the expected traffic is exchanged.
11.2 GOOSE traffic
Useful filters include:
goose
and:
eth.type == 0x88b8
Inspect relevant packet information, including:
- APPID.
- VLAN ID.
- Destination MAC address.
stNum.sqNum.timeAllowedToLive.ConfRev.
The state number and sequence number have different meanings:
stNumchanges when the published dataset state changes.sqNumadvances as retransmissions are sent for the current state.timeAllowedToLiveindicates the expected supervision interval.ConfRevidentifies the applicable GOOSE configuration revision, not the firmware version.
11.3 TCP communication problems
For diagnosing TCP-level problems, useful filters include:
tcp.analysis.retransmission
tcp.flags.reset == 1
These can help identify retransmissions and connection resets.
However, packet analysis should be combined with device diagnostics and application-level testing.
12. Common Problems During MiCOM Firmware Upgrades
Problem 1: Firmware package rejected
Possible causes:
- Incorrect device model.
- Incompatible order code.
- Unsupported hardware revision.
- Incorrect starting firmware version.
- Wrong firmware package.
Recommended actions:
- Confirm the relay identification.
- Check the firmware package information.
- Review the upgrade path.
- Consult the manufacturer documentation.
Do not attempt to bypass device compatibility checks.
Problem 2: Engineering software cannot identify the relay
Possible causes:
- Incorrect communication interface.
- Missing drivers.
- Unsupported engineering software.
- Device communication problem.
- Incorrect device support package.
Recommended actions:
- Check the physical connection.
- Verify the communication settings.
- Confirm software compatibility.
- Use the appropriate manufacturer-supported interface.
Problem 3: Configuration is different after upgrading
Possible causes:
- Configuration conversion.
- New firmware parameters.
- Modified parameter behavior.
- Unsupported configuration items.
- Incomplete restoration.
Recommended actions:
- Compare the current configuration with the approved backup.
- Review the release notes.
- Check parameter definitions.
- Verify the settings with an independent reviewer.
Problem 4: MMS communication fails after upgrading
Possible causes:
- Changed communication settings.
- Incorrect IP configuration.
- IEC 61850 service configuration problem.
- Client configuration mismatch.
- Network or security restrictions.
Recommended actions:
- Verify network connectivity.
- Check the relay’s IP parameters.
- Confirm MMS service availability.
- Review the data model.
- Inspect traffic with Wireshark.
- Test the communication from the actual SCADA client.
Problem 5: GOOSE messages are no longer received
Possible causes:
- Changed GOOSE configuration.
- Incorrect subscriber mapping.
- Dataset mismatch.
- Multicast or VLAN problem.
- Configuration revision mismatch.
- Different device capability or firmware implementation.
Recommended actions:
- Check publisher and subscriber engineering.
- Compare the relevant SCL files.
- Inspect GOOSE packets.
- Verify subscriber processing.
- Perform end-to-end functional testing.
Problem 6: Relay does not start normally after upgrading
Possible causes may include:
- Interrupted upgrade.
- Incompatible firmware.
- Hardware-related problem.
- Incorrect recovery procedure.
Recommended actions:
- Follow the manufacturer’s recovery instructions.
- Do not repeatedly interrupt or restart the device without guidance.
- Contact the manufacturer’s technical support when required.
- Use an approved replacement or recovery plan if the relay cannot be restored.
13. Firmware Rollback and Recovery Planning
Engineers sometimes assume that firmware upgrades can always be reversed.
This is not necessarily true.
The ability to downgrade depends on the relay model, firmware release, hardware platform, and manufacturer’s supported procedure.
Before an upgrade, establish:
- Whether downgrade is supported.
- Which previous firmware versions are permitted.
- Whether configuration conversion is reversible.
- Whether a recovery package is required.
- Whether the device can be recovered through an approved service interface.
- What to do if the upgrade is interrupted.
A firmware backup should not be confused with a configuration backup. Saving the relay settings does not necessarily provide a way to restore its previous firmware.
If rollback is required, follow the manufacturer’s instructions rather than attempting an unapproved downgrade.
14. Practical Example: Firmware Upgrade of a MiCOM P443 Distance Relay
Consider a MiCOM P443 distance protection relay installed on a transmission line.
The relay provides distance protection, breaker failure protection, event recording, and IEC 61850 communication with the substation automation system.
An approved maintenance plan requires a firmware upgrade.
Before the upgrade
The engineering team:
- Records the relay model and order code.
- Records the serial number and firmware version.
- Retrieves the available device configuration.
- Saves the protection settings.
- Archives the relevant IEC 61850 configuration files.
- Reviews the firmware release notes.
- Confirms the upgrade path.
- Obtains operational approval.
During the upgrade
The team follows the manufacturer-approved upgrade procedure.
The communication connection and device power supply are maintained as required by the instructions.
After the upgrade
The team verifies:
- Firmware version.
- Device startup.
- Self-supervision.
- Distance protection settings.
- Zone configuration.
- Breaker failure settings.
- Binary input/output assignments.
- Event recording.
- MMS communication.
- GOOSE communication, if used.
- SCADA indications.
Secondary injection tests are then carried out according to the approved test plan.
The relay is returned to service only after the required checks and approvals have been completed.
This example illustrates the importance of treating firmware upgrades as controlled protection-system maintenance.
15. Best Practices for Firmware Management
For substations with multiple MiCOM relays, a structured firmware-management process is recommended.
- Maintain a firmware register for all protection relays.
- Record exact model and order code information.
- Record hardware and firmware versions.
- Keep manufacturer release notes with the project documentation.
- Verify firmware compatibility before every upgrade.
- Maintain an approved configuration backup.
- Keep the original firmware information available.
- Use only manufacturer-approved packages.
- Obtain operational approval before upgrading.
- Follow the specified upgrade path.
- Verify protection settings after upgrading.
- Test binary inputs and outputs.
- Test IEC 61850 MMS and GOOSE where applicable.
- Review the SCL configuration after relevant changes.
- Document test results and final firmware versions.
- Maintain a recovery plan.
16. MiCOM Firmware Upgrade and Commissioning Checklist
Before the upgrade
- Exact relay model identified.
- Complete order code recorded.
- Serial number recorded.
- Hardware revision checked.
- Existing firmware version recorded.
- Configuration backup completed.
- Protection settings saved.
- IEC 61850 files archived where applicable.
- Release notes reviewed.
- Firmware compatibility confirmed.
- Upgrade path confirmed.
- Operational approval obtained.
During the upgrade
- Manufacturer procedure followed.
- Correct firmware package used.
- Required power supply maintained.
- Communication maintained as required.
- Upgrade completion confirmed.
After the upgrade
- New firmware version verified.
- Relay startup checked.
- Self-supervision checked.
- Protection settings reviewed.
- Binary inputs and outputs checked.
- Protection functions tested as required.
- Event and disturbance recording checked.
- MMS communication verified.
- GOOSE communication verified where applicable.
- SCADA indications checked.
- Final project saved.
- Maintenance records updated.
- Return-to-service approval obtained.
17. Training on MiCOM Protection Relays and Commissioning
Firmware management is only one part of professional protection relay engineering.
Engineers also need practical knowledge of relay configuration, protection settings, testing, communication, and commissioning.
Elec-Engg provides practical training covering:
- MiCOM protection relay families.
- S1 Agile engineering.
- Protection settings and coordination.
- Distance and line protection.
- Transformer and generator protection.
- IEC 61850 MMS and GOOSE.
- SCL configuration and system integration.
- Omicron CMC and relay testing.
- Troubleshooting and commissioning procedures.
Training is available through video courses, structured self-paced training, face-to-face courses, and customized in-house programs.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Visit Elec-Engg for more information about protection and substation automation training.
Conclusion
Firmware management is an essential part of maintaining reliable MiCOM protection systems. Before upgrading a relay, engineers must identify the exact device, verify firmware compatibility, back up the existing configuration, review manufacturer release notes, and follow the approved upgrade procedure.
After upgrading, protection functions, settings, device health, communication services, and IEC 61850 integration must be verified.
The most important principle is that a firmware upgrade should never be considered complete simply because the relay displays a new firmware version. The relay must also demonstrate correct operation under the requirements of the protection and substation automation design.
