Professional Documents
Culture Documents
Content:
1. Introduction 4
1.1 Document Scope 4
1.2 Related Documentation 6
1.3 Equipment and Software Needed for the Firmware Update Procedure 6
2. The Firmware Update Procedure in Brief 7
3. Prepare the Update Computer 8
3.1 Connectivity Package Settings in the Update Manager 8
3.2 The PCM600 Project with the IEDs to Be Updated 8
3.3 Local Area Connection Settings 13
4. Safety Information and Site Preparation 14
4.1 Personal Safety 14
4.2 Minimize the Risk to Unintentionally Trip a Circuit Breaker 14
4.3 The Auxiliary Power Supply Must Be Uninterruptible 14
5. Read the IED Configuration 15
5.1 General 15
5.2 Common Read from the IED to PCM600 15
6. Update the IED Firmware 18
6.1 Before Starting 18
6.2 Updating the Firmware Using the IED’s Front Port 18
7. Restore the IED Configuration 23
7.1 The Technical Key in the IED Has to Match with PCM600 23
7.2 Common Write to IED with Lock Parameters Included and R/L in Remote 24
7.3 Some Special Parameters to Check, and Restore if Needed 27
7.4 Restart the IED 27
8. Clear the Local HMI’s Lifecycle Handling Indication 28
8.1 General Information 28
8.2 Collect the IED Composition Data to PCM600 28
9. Verify Procedure Successfulness and Restore IED Connections 30
9.1 Verify the Firmware Version 30
9.2 Check the Appearance of the SLD on the LHMI 30
9.3 Comparison of Present Parameter Values to Pre-update Values 31
9.4 Verify the Communication between IED and Control System 32
10. Check the IED’s Date and Time, and Adjust if Necessary 33
11. Finally 33
- How to Export a PCM600 Project to a PCMP File 34
- IED Users and Passwords 35
B.1 If IED Passwords Are in Use 35
B.2 How to Restore IED Users and Passwords 36
- How to Prepare Your PC for Communication with the IED 39
C.1 How to Set the IP Addresses of Your PC’s Network Interface 39
C.2 Create a Desktop Shortcut to the Local Area Connection Settings 42
C.3 Firewall Settings 44
C.4 Considerations about Using the Front Port versus the Rear Port 44
- PC Related Troubleshooting 45
D.1 The Ping-Command 45
D.2 Resetting Your Computer’s Address Resolution Table 45
- Installation of the Lifecycle Services Tool (LCT) 47
E.1 PCM600 version 2.10 47
E.2 PCM600 versions before 2.10 48
- How to find out the Original Version of PCM600 and ConnPack 51
- How to Correct a Pixel Shift in the LHMI’s SLD 53
- Check List Template 56
1. Introduction
1.1 Document Scope
This document is a guideline how to update the firmware of 615 series IEC Intelligent Electronic
Devices (IED). The main content is an example update procedure, illustrated with screenshots. The
screenshots are mainly based on one of the versions, but the same procedure can be followed also with
the other IED versions mentioned in this document’s scope. This is the tested procedure, which does
not require the protection relay to have any optional communication ports – the front port is used in all
steps. Conditional and alternative steps are indicated with indentation.
The instructions in this document assume, that the protection relay is installed in a switchgear or panel.
In case you are unfamiliar with the update procedure, we recommend that you read this document in
its entirety, before you start.
Note:
• There is a separate document for product version 3.0 (XD), because the procedure is different.
• In case of updating line differential protection RED615, both line ends need to be updated at
the same time. The line differential protection resumes normal operation when both protection
relays have been updated.
To verify that this firmware update applies to your protection relay version, ensure that the second
character and the last two characters of the order code on the label on top of the local human-machine
interface (LHMI) match the corresponding characters of the order code in the table below:
To identify the Order code and the current firmware revision via the LHMI, navigate to Information \
Product Identifiers, and note the parameters Order code and SW version:
Example of Order code and current firmware revision (SW version) of a 615 series IED
To verify that this firmware update applies to your protection relay version, ensure that the second
character and the last two characters of the order code on the label on top of the local human-machine
interface (LHMI) match the corresponding characters of the order code in the table below:
To verify that this firmware update applies to your feeder automation IED version, ensure that the
second character and the last two characters of the order code on the label on top of the local human-
machine interface (LHMI) match the corresponding characters of the order code in the table below:
xBxxxxxxxxxxxxxx1F for product version 1.1, SW version 1.1
xBxxxxxxxxxxxxxx1G for product version 2.0, SW version 2.0
On the LHMI, you find the Order code and SW version in the same way as described for the
protection relays.
1.3 Equipment and Software Needed for the Firmware Update Procedure
• The latest version of the existing PCM600 project, the project either as such or as a PCMP-
file. See Appendix A for information how to export a PCM600 project to a PCMP-file.
• A Windows computer with the latest PCM600 version, with the latest available hotfix.
o PCM600 needs to be installed with the option “I accept to take ABB’s Lifecycle Service
Tool into use” enabled. See Appendix E.
• The firmware update file (.BIN) and the latest available connectivity package for the IED
types you intend to update.
• An Ethernet cable with RJ45 connectors.
Verification
Verify that the Read, Update and Write have been successful.
Ch. 9
i
It might be tempting to just create a new PCM600 project, build a plant structure for the IEDs to be
updated, and simply “Read from IED …”. However, be aware that for cyber security reasons, in
some scenarios some information (e.g. some of the passwords) is excluded from the Common Read. It
is therefore strongly recommended to always use (a copy of) the latest version of the existing PCM600
project.
• In case you already have the latest version of the PCM600 project on your laptop, you can use
that. Before you continue, take a full backup of the project by exporting it to a PCMP-file, as
described in Appendix A.
• In other case, you must create a copy of the PCM600 project by importing a PCMP-file, which
has been exported from the latest version of the PCM600 project. See Appendix A and the
sub-chapter below.
i
When you import a PCMP-file from an older PCM600 version, the PCM600 project version will be
converted, and it cannot be converted back. It is therefore recommended to keep the PCMP-file, and/or
any other backup(s) of the original PCM600 project.
3.2.1 How to Import the PCMP-file and Convert the PCM600 Project to the Latest
PCM600 Version
Start the latest PCM600 version and Select File \ Open/Manage Project...
Select the file that has been exported from the original PCM600 version. Click Open:
• In case the PCM600 project has not existed on this computer before, there will be only one
instance of the project, as in the screenshot above.
• In case the project was imported to the same computer (and to the same PCMSERVER) as the
original PCM600 project, PCM600 will add an incremental suffix “(n)” – for example “(2)” –
to the name of the imported project.
Start the conversion of the imported project by selecting it and click the Open Project button.
i
In case the project you are opening was created by the same
PCM600-version as you are using, there will naturally not be any
conversion. In such case, skip the next three screens and continue at
“PCM600 opens the project”.
!
Note that the protection functions will be out of use from start of the update until the configurations
and settings have been written back and committed in the IED, and the IED has resumed normal
operational status.
!
Concerning line differential protection with a pair of RED615, note that the protection communication
requires that both REDs have the same firmware version. This means that the line differential
protection will not resume operation before also the second RED has been updated.
!
The firmware update will set the IED configuration and settings to factory default (concerns at least
SW versions 4.0 and 4.1), which means that the protection relay will in most cases trip if the update is
done while the switchbay is in normal operation.
Note that in addition to the local CB, other CBs might be tripped via the Circuit Breaker Failure
Protection (CBFP) function. Note that in some cases the CBFP trip is implemented with GOOSE
communication.
!
The IED will restart several times during the procedure, and will thereby de-energize all its output
relays, including the Internal Relay Fault (IRF) contact. Depending on how the switchgear has been
designed, the de-energization of an output relay may cause a tripping of the local CB and/or some
other CB(s).
The IED under work must be isolated from such protection schemes for the whole duration of the
update process. It is under the responsibility of the plant’s authorized operation personnel to make
an evaluation of the situation within the installation, plan and carry out the necessary actions to
avoid possible unwanted incidents.
After the IED update process has been successfully carried out, the installation shall be returned
to its original status. It is under the plant’s authorized operation personnel to remove any
temporary connections and to resume and confirm the installation’s full operational status.
!
The firmware update will set some of the configurations and settings to factory default. It is therefore
important to Read from IED first (with the Common Read/Write Tool), to produce an up-to-date and
full back up of the IED application and settings.
i
The Read from IED does not include the Web HMI mode parameter.
On the LHMI, navigate to Configuration\HMI and note down the status of the Web HMI mode
parameter:
If the laptop has been recently connected to the front port of some
other IED, it is sometimes necessary to refresh the laptop’s IP
configuration and address resolution table. See Appendix C and
Appendix D.
The following picture shows how to set PCM600 to communicate via the front port of the selected
IED. Right click on the IED in the Plant Structure and select the desired Communication Port from
the context menu. The port selection is IED specific.
If this is the first time you are doing the firmware update procedure, use the front port.
i
For experienced users, the rear port may have advantages. The full detail about rear port usage
is beyond the scope of this document. When you have fully mastered the procedure via the
front port, in case you want to learn about the rear port alternatives, you can start by reading
Appendix C.4.
In PCM600, ensure that you have selected the intended IED and communication port, and that the
communication check mark is green.
Via the front port, the Common Read from IED typically takes 4–8 minutes. A successful Common
Read is indicated with the word “Success” in the Comment column of the Common Read/Write tool:
i
During the firmware update, until the original settings have been restored to the IED, the IED’s rear
communication port will have the factory default IP address 192.168.2.10. Thus, unless the IED’s rear
port has been disconnected from the network, there will be a duplicate IP in case 192.168.2.10 is in
use by some other device on the network.
Tip
It is a good idea to verify also before the update those same IED functions, which you are going to
verify after the update, and make a note if something is out of use. For example, if after the update
there is no time synchronization, it will be a relief to know that there was no time synchronization
before the firmware update either.
Start the Firmware Update Tool by right clicking on the IED and select Update IED:
Note the 4th character of the order code; you will need it when selecting which update file to use.
i
The Common Read done earlier in this guideline serves the purpose of an up-to-date backup of the
IED configuration.
!
“redundant Ethernet network” refers to Parallel Redundant communication Protocol (PRP) or High-
availability Seamless Redundancy (HSR). The IED must be disconnected from any of these before
proceeding.
When the conditions in the dialog are fulfilled, click the Next-button.
Select the bin-file according to IED version, type, and the 4th character of the order code, which shall
correspond to the character after “Config_” in the file name (“L” in this example).
Via the front port, the firmware update typically takes 5 – 30 minutes, depending on the update
content.
!
Although some IED versions may preserve a large part of its configuration and settings through the
firmware update, some parameters are set to default. It is therefore necessary to follow the steps in this
chapter, in order to make sure that all configurations and settings are restored. In cases where correct
settings are already present, the corresponding screens below will be slightly different.
7.1 The Technical Key in the IED Has to Match with PCM600
i
The technical key in the IED must match with the corresponding Technical Key in
PCM600, before you can write anything else from PCM600 to the IED.
In the Set Technical Key dialog, first click the radio button
“Technical Key in PCM600” and next click the “OK”-button:
7.2 Common Write to IED with Lock Parameters Included and R/L in Remote
7.2.1 Enable “Write locked parameters to IED”
Before you write the configuration to the IED, you need to activate the “Write locked parameters to
IED” option in the Common Read/Write tool.
In case the Common Read/Write-tool is not visible, you have
to make it visible first, for example by starting a write (see
the second next screen clip) and then cancel it by answering
“No” to the question “Are you sure you want to start write
operation for IED?”
In the Common Read/Write-tool’s toolbar, select Write locked parameters to IED:
Note that the lock setting will return to the “Do not write locked parameters to IED” state, when you
exit the Common Read/Write tool or PCM600.
i
Writing via the front port is straightforward; simply follow the steps depicted in this
guideline.
In case you consider using the rear port for this step, the IED’s rear port IP address,
Subnet Mask and Default Gateway must match with PCM600 first. After these
settings have been changed and stored, an IED restart is required in order to activate
them.
If possible, have the LHMI’s R/L-key in the Remote (R) position during the write to IED. Note down
the R/L-keys original position if you must change it.
i
In most cases, everything is written successfully regardless of the R/L-key’s position. But in some
case, generic control points (SPCGGIO, SPCGAPC) might be an exception, because they might have
been configured to observe the R/L-key’s position. This means that they cannot be set remotely even
from PCM600 unless the R/L-key is in the remote position. If you cannot set the R/L-key to the
remote position, after completion of the write please investigate if there are any skipped parameters in
the Common Read/Write tool’s Report.
With the lock icon in the unlocked state, select Write to IED:
Or
Via the front port, the Common Write to IED typically takes 3–6 minutes. A successful Common
Write is indicated with the word “Success” in the Comment column of the Common Read/Write tool:
i
The Common Write to IED does not include the Web HMI mode parameter. It is therefore necessary
that you manually ensure that it has the same value that it had before the firmware update.
On the LHMI, navigate to Configuration\HMI and check/set the Web HMI mode parameter
back to the value that you noted before starting the firmware update.
In case you change the parameter value, store it before rebooting the IED. (After you have
changed the parameter value by pressing the Enter-button, press the left arrow key repeatedly
until the Commit settings?-dialog appears. Select Yes and press the Enter-button. This
same principle applies to any parameter value that you change via the LHMI.)
i
A Software reset is enough for a full IED restart, there is no need to cycle the IED’s auxiliary power.
!
It is better to use Software reset instead of cycling the IED’s auxiliary power with the Miniature
Circuit Breaker (MCB), because it is possible that also some other devices are supplied by the same
MCB.
!
Do not force a restart if the LHMI icon is showing a flashing “S”, because the flashing “S” means that
the IED is storing parameters:
If a restart is forced in this situation, any parameters changes that have not yet been stored, will be lost.
i
After the Firmware Update, the IED is aware that its composition has been changed. Until the changed
composition data has been read to PCM600, and unless the “Clear Lifecycle Handling indication on
Local HMI after update” checkbox was shown and ticked in the Firmware Update dialog, the IED may
occasionally show the following Lifecycle Service Tool (LCT) reminder screen on the LHMI:
i
Note that the required tool, Lifecycle Service tool (LCT), is available in PCM600 only if the related
option was chosen during PCM600 installation. See Appendix E for additional information.
Right-click on the IED in the Plant Structure, select Lifecycle Handling \ Collect IED Composition
Data:
It is optional whether to include the “Configuration File” and “Disturbance Recordings”. Please feel
free to uncheck them:
In case the Site identifiers are empty, PCM600 will show a Warning
dialog:
i
Despite the Warning dialog, it is optional whether to fill in the Site
identifiers or not. It is enough that you acknowledge the Warning-
dialog by clicking its OK button.
After successful IED composition data collection, the IED knows that the data has been collected, and
does not show the LCT reminder screen on the LHMI anymore.
Note
Until you have completed comparing the present parameter values to the pre-update values, keep
unchecking the “Copy IED values to PC value field”, each time before you read. This in order to
preserve the values that were read before the firmware update.
Then, each time you have read some parameters, the information cloud will indicate which IED values
have changed:
• Warning and Internal Fault must be either “All ok”, or same as before the update:
10. Check the IED’s Date and Time, and Adjust if Necessary
In case the IED does not have automatic time synchronization, you will have to adjust date and time
manually. Check the IED’s date and time by selecting Configuration \ Time \ System Time, check
that Date and Time are correct and adjust if necessary:
i
When writing the lock parameters during the Write to IED…, also the time that had been read to
PCM600 during the Common Read earlier, was written back to the IED. The outdated date and time
will however be automatically overwritten by the correct date and time, in case there is automatic time
synchronization.
11. Finally
When you do not need communication between the IED’s front port and PCM600 anymore, it is
recommended to set the IED for rear port communication in PCM600. (Select Communication Port \
Rear port in PCM’s Plant Structure.) The idea is to leave all IEDs in PCM600‘s plant structure set for
rear port communication with individual IP addresses, and have only the IED undergoing updating
work set for front port communication with fixed IP (192.168.0.254). Thereby you reduce the risk to
exchange data with the wrong IED by a human mistake.
In case you have changed the position of any buttons on the LHMI, for example the R/L-key, set them
back to their original positions.
Select the folder where you want to save the file, click Save:
i
In case Remote override = “False” in the IED, then in PCM600’s Object Properties Is Authentication
Disabled has to be “False”, Is Password used has to be “True”, and Password has to be the same as
the IED’s Remote administrator password .
Because you have imported and converted the original PCM600 project, the Object Properties will
already match to the IED parameters, and normally you should not need to change them.
• Note that in case passwords are in use, as indicated by the Login screen and Authentication
settings depicted above, you may have to restore them by a separate procedure after the firmware
update. In most cases, the passwords are however retained unchanged by the IED throughout the
firmware update. You find information about how to restore IED Users and Passwords in
Appendix B.2.
i
For cyber security reason, the remote passwords (Remote viewer, Remote operator, Remote engineer,
Remote administrator) cannot be read from the IED to PCM600, they can only be written. This means
that it is important to use the original PCM600 project (or a copy created e.g. by importing a PCMP
file), when writing the user management settings to IED.
i
In case Remote override = “False” in the IED, then in PCM’s Object Properties Is Authentication
Disabled must be “False”, and Is Password used must be “True”:
In case IED Users and Passwords are different from default, you must write also them to the IED.
Check the parameter value of Remote override:
• If Remote override = “True”, it means that remote passwords are not in use, and
then you do not need to write the User Management Settings to the IED.
• If Remote override = “False”, it means that remote passwords are in use, and then
you must write the User Management Settings to the IED:
Select IED Users from the IED’s context menu:
In case Remote override = “False” in PCM600 (PC Value), but “True” in the
IED, you must unlock and write the parameter from PCM600:
i
Any possibly assigned local passwords might be overwritten by the firmware update, and
they are not included in the Write to IED. If local passwords have been assigned (Local
override = “False” in the IED), they will have to be verified/restored manually by a person
who knows them. The person, who originally set the local passwords, will know how to
set them again by using Configuration\Authorization on the LHMI:
i
The front port of the 615 series has DHCP, which means that the IED allocates an IP address
automatically to the laptop, as soon as it is connected to the front port. A successful automatic address
allocation by the IED to a laptop can look e.g. like this (Windows 7):
You may have to refresh the IP configuration, when you have moved the Ethernet cable from the front
port of some other IED to the front port of the IED you will be working on. (Windows’ automatic
refresh cycle is approximately 10 minutes.) You can do the refresh e.g. by Disabling/Enabling your
laptops Network Interface, or by using command prompt commands like Arp and Ping (described in
Appendix D).
In some cases however, the automatic IP configuration might still be unsuccessful, and you may have
to configure the IP address(s) manually.
!
Take a note of the original communication settings before changing them.
In case the PC/laptop is borrowed from some other environment, for example an office network, it
might be vitally important to set the settings back to original before returning the laptop to its original
environment.
i
On most computers, it is possible to set the Network Interface Controller to use several IP addresses
simultaneously, which might be convenient if you are going to swap frequently between IED front
port and rear port communication.
C.1.2 Example NIC Settings (Windows 7) for Communication with the IED’s
Front Port and Rear Port
OR
• 192.168.0.10 is for communication with the IED’s front port, which has always the same
(fixed) IP address 192.168.0.254.
• 192.168.240.112 / 255.255.192.0 is an example of a custom IP address and mask allocated for
the laptop by the possessor of the IED network. It is intended for communication via the
IED’s rear port when it is using a custom address (which could be e.g. 192.168.220.34.)
• 192.168.2.9 is an example of an IP address that could be used for communication via the
IED’s rear port during situations when it is using the factory default address, which is
192.168.2.10.
i
Some computers, for example those with external NIC via USB, may not always support usage of
several IP addresses simultaneously. In case you notice that addresses you have added via the
advanced TCP/IP settings do not work, you must delete them and use only one IP address per each
NIC. In this case, you must keep changing the IP address always when needed.
OR
C.2.1 How to Use the Shortcut to Disable/Enable the Local Area Connection
Example screen clip (Windows 7) how to disable and re-enable the Local Area Connection, by using
the desktop shortcut:
On some computers, the Enable/Disable doesn’t work reliably. In such case, first click the Open file
location, to use the context menu of the NIC itself.
C.4 Considerations about Using the Front Port versus the Rear Port
The steps illustrated in the Firmware Update Guideline are using exclusively the IED’s front port. One
reason is that not all IED variants have a rear communication port, but they do have a front port. In
addition, in some cases accessing the IED’s rear side must be avoided in order to maintain personal
safety. For example, if the user does not have competence how to work safely near live electrical parts,
and/or depending on the switchgear construction.
However, when the IED has a rear Ethernet communication port, and the safety conditions allows its
usage, using the rear port for Common Read and Write has several advantages. Not only is the rear
port faster than the front port. In addition, connecting the laptop to the rear port serves as a reminder to
disconnect the IED from the station communication bus (Ethernet) during the update procedure. (In
some cases, it is necessary to disconnect the IED from the station communication bus in order to avoid
a duplicate IP address allocation, and/or disturbance to redundant communication Ethernet protocols.)
Thirdly, having each IED in PCM’s plant structure set for rear port communication, each with its
individual IP address, reduces the risk to exchange data with the wrong IED by a human mistake.
Fourthly, by alternating front port usage (firmware update) with rear port usage (Common
Read/Write), you avoid the need to reset manually the front port’s address resolution table. You can
get some basic information about rear port usage by reading from the beginning of Appendix C, but
please note that this document scope does not cover all possibilities and details. The 615 Series
Engineering Manual is suggested for further reading. Even after having gained comprehensive
knowledge about how to use the rear port, use it only when it can be accessed safely.
- PC Related Troubleshooting
D.1 The Ping-Command
The ping-command might be helpful when troubleshooting communication problems between the
laptop and the IED. For example, sometimes it happens that PCM600 is slow in discovering that
communication with the IED is possible. The ping-command is usually faster.
The ping-command is used from the command prompt:
Example of successful ping-command from the laptop to the (rear port) custom IP address of an IED:
In case the response is that “The requested operation requires elevation”, it means that the command
prompt has to be started with the “run as administrator” option:
To check the result of the Arp –d * command, use Arp –a before and after the Arp –d * command:
In the screen clip below, when we ping 192.168.0.254, it is added again to the address resolution table,
now with the “Physical Address” of the second IED:
Alternatively, if the installed PCM600 version is 2.5 … 2.9, you may use the
“Programs and Features” of the Windows operating system to restart the
installation wizard.
Select “Modify”:
Tick “I accept to take ABB’s Lifecycle Service Tool into use”, and click the Next-button:
After the installation, the Lifecycle Service Tool (LCT) is configured to send its collected data
automatically to ABB’s global support database, with the following default settings:
If you prefer that the collected composition data shall not be sent to ABB’s support database, locate
the “ABB Lifecycle Service Tool” button on the computer’s taskbar, right click on the button, and
select “Options”:
i
The list of connpacks contains not only the connpacks tied to the IEDs in the PCM600 project, it
contains all the connpacks that were defined in the Update Manager to be used with the PCM600
version from which the project was exported.
Example of a PCM600 project, the related settings in the Update Manager, and the resulting
ProjectDataServer%versions.ini file:
i
If the PCM600 project has been made with new enough product versions, PCM600’s Open/Manage
Projects’ Show Project Information is able to show specifically which Connectivity Package versions
has been used by the project:
This can be adjusted by correcting the truck indications by one pixel in the GDE. Note that the change
is best done by adjusting the “X Position” value rather than trying to drag the symbol. Here is an
example, how to do the adjustment:
• Increment the X Position value of the uppermost truck indication by one. (From “69” to “70” in the
example below):
• Save:
The information in this document is subject to change without notice and shall not be construed as a commitment
by ABB Oy. ABB Oy assumes no responsibility for any errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature
or kind arising from the use of this document, nor shall ABB Oy be liable for incidental or consequential damages
arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB Oy,
and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and may be used, copied, or
disclosed only in accordance with the terms of such license.
Trademarks
ABB is a registered trademark of ABB Group. All other brand or product names mentioned in this document
may be trademarks or registered trademarks of their respective holders.
Contact information
www.abb.com/mediumvoltage
www.abb.com/substationautomation