C200 Upgrade Tool Guide-EPDOC-X640-en-520A

Experion PKS
Release 520
&8SJUDGH7RRO*XLGH
EPDOC-X-en-520A
June 2021
Disclaimer
This document contains Honeywell proprietary information. Information contained herein is to be used
solely for the purpose submitted, and no part of this document or its contents shall be reproduced,
published, or disclosed to a third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the
implied warranties of merchantability and fitness for a purpose and makes no express warranties
except as may be stated in its written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The
information and specifications in this document are subject to change without notice.
Copyright 2021 - Honeywell International Sàrl
-2-
Contents
Chapter 1 - About this guide 7
1.1 Scope 7
1.2 Purpose 7
1.3 Revision history 8
1.4 Intended audience 8
1.5 Related documents 8
1.6 Terms and definitions 9
Chapter 2 - C200/C200E Controller to the C300 Controller 11
2.1 Introduction 11
2.1.1 Hardware upgrade 12
2.1.2 C200/C200E Controller to the C300 Controller 15

2.1.3 Scope and limitations 16
2.1.4 Understand the differences between C200/C200E and C300 17
2.1.5 Understand the differences between FIM2 and FIM4/FIM8 19

2.1.6 Hardware Software requirements 20
2.1.7 Interoperability requirements 21
2.1.8 User Privilege requirements 21
2.2 Plan the C200/C200E to C300 Upgrade 21

2.2.1 Planning considerations 21
2.2.2 Prerequisites and assumptions 23
2.2.3 Site requirements 24

2.2.4 Upgrade kits 27
2.2.5 Upgrade tool workflow 32
2.3 Install the C200 Upgrade Tool 33

2.3.1 C200 Upgrade tools 34
2.3.2 Upgrade tool user interface 35
2.4 Readiness Checks 35

2.4.1 Ensure ERDB is not fragmented 36
2.4.2 Readiness check types 36
2.4.3 Server upgrade readiness checks 37
2.4.4 CNET to FTE readiness checks 40
2.4.5 Controller upgrade readiness checks 42
2.4.6 Supervisory FIM2 readiness Checks 50
2.4.7 Generating and analyzing readiness check reports 52
-3-
2.5 Upgrade the Experion Process Network from CNET to FTE 54
2.5.1 CNET to FTE upgrade screen 54
2.5.2 Adding the FTEB module to the controller chassis 55
2.5.3 Taking a backup of ERDB 57
2.5.4 Upgrading the Experion Process Network to FTE 58
2.6 Transform Configuration (C200/C200E to C300, FIM2 to

FIM4/FIM8) 60
2.6.1 Transform option and backup ERDB 61
2.6.2 Transform C200/C200E configuration to C300 configuration 61
2.6.3 Transform Supervisory FIM2 configuration to FIM4/FIM8 configuration 72
2.6.4 Transform configuration summary report 73
2.7 Upgrade C200/C200E to C300 (Live/Off-Process) 73

2.7.1 Live upgrade 74
2.7.2 Off-Process Upgrade 87
2.8 Prepare Controller Hardware for Upgrade 94

2.8.1 Upgrade hardware using the C200/C200E to C300 hardware upgrade kit 94
2.8.2 Process to upgrade SIM 114
2.9 Post Upgrade Activities 115

2.9.1 Prerequisites 115
2.9.2 Considerations 115

2.9.3 Updating the network configuration 116
2.9.4 Loading after performing Off-Process Upgrade 117
2.9.5 Update and load Exchange blocks in peer server 117
2.10 Troubleshooting and Maintenance 118

2.10.1 Cancel CNET to FTE upgrade 118
2.10.2 Cancel controller upgrade 119
2.10.3 Remove the C200 Upgrade tool 120
2.10.4 Isolate the Console Station from the server 120

2.10.5 Alarms generated during upgrade 121
2.10.6 AB PLC2/3/5 address is not mapped for the Input and the Status file type 121
2.10.7 Device index is not in the PCDI range 122

2.10.8 PCDI activation error 122
2.10.9 Slave FTA Handling 123
2.10.10 Load firmware to C300 failure scenarios 123
2.10.11 Readiness check failure scenarios 123
2.10.12 Load FTEB Error Handling 123
2.10.13 QVCS Details 124
-4-
2.11 Appendix A Off-process upgrade without Upgrade Tool 126
2.11.2 Hardware and software requirements 127
2.11.3 C200 Upgrade tool components 128
2.12 Appendix-B Checklist for ControlNet to FTE conversion 131

2.13 Appendix C Checklist for C200 to C300 conversion (Live
Upgrade) 133
2.14 Appendix D SCADA configuration 135
Chapter 3 - C200/C200E Controller to the UOC Controller 136
3.1 Introduction 136
3.1.2 Licensing information 137
3.1.4 Understand the difference between C200/C200E and UOC 139

3.2 Plan the C200/C200E to UOC Upgrade 139

3.2.1 Topology 140
3.2.4 Security Considerations 144

3.2.5 UOC Hardware Installation 144
3.3 Install the C200 Upgrade Tool 147

3.3.1 C200 Upgrade Tool components 148
3.4 Readiness Checks 148

3.4.1 Checking for ERDB inconsistencies 148
3.4.3 Types of Readiness Checks 149
3.5 Upgrade the Experion Process Network from CNET to FTE 163

-5-
3.6 C200 Upgrade Tool Transform Configuration 169
3.6.1 Transform C200/C200E configuration to UOC configuration 170
3.7 C200 Upgrade Tool 173

3.7.2 Perform off-process upgrade 173
3.8 Prepare Controller Hardware for Upgrade 175

3.8.1 Configuring 1756 modules 175
3.8.2 Process to upgrade Serial Interface Module (SIM) 177
3.9 Post Upgrade Activities 178

3.9.2 Loading after performing off-process upgrade 178
3.9.3 To Reestablish peer connection 180
3.10 Troubleshooting and Maintenance 180

3.10.3 Remove the C200/C200E Upgrade Tool 181


3.10.9 Upgrade a non-redundant C200/C200E to redundant UOC 183

3.10.11 C200 Upgrade without IOMs configured 186
3.11 Appendix A Checklist for ControlNet to FTE conversion 187
-6-
CHAPTER
1 ABOUT THIS GUIDE
1.1 Scope
Beginning with Release R5xx, the C200/C200E to C300 Upgrade tool and the C200/C200E to UOC
Upgrade tool are merged. Both the migrations can now be performed using the C200 Upgrade tool.
This guide describes how to upgrade the following.
l C200/C200E Controller chassis modules: C200/C200E Controller, FTE Bridge, Redundancy
Module, IOLIM, SIM, FIM2 and Series A, to the Experion Series C system (including C300,
FIM4/FIM8, PGM etc.). Modules/Strategies under QVCS are also supported.
l C200/C200E Controller chassis modules: C200/C200E Controller, FTE bridge, Redundancy
Module, and Series A I/Os to Unit Operations Controller (UOC).
This document provides detailed information for planning and executing the following migrations in the
C200 Upgrade tool.
l C200/C200E Controller to the C300 Controller
l C200/C200E Controller to the UOC Controller
1.2 Purpose
C200/C200E Controller to the C300 Controller
This section is focused on the tasks related to live upgrade and Off-Process upgrade with upgrade tool;
detailed procedures for Off-Process upgrade without tool are not available as they are site-specific and
there is no formal process for the same. However, this guide includes tips for performing an Off-
Process upgrade without using the tool.
Details of three types of upgrade process:
l Live upgrade process – If your system has C200/C200E with PMIO configured then Live upgrade
process can be performed. Use the C200 Upgrade Tool to perform the upgrade. This upgrade is
possible even if Series A is available. However, Series A and its strategies will be in Inactive state
during the upgrade process.
l Off-Process upgrade with Upgrade Tool – Typically, performed when the requisite hardware is not
available but you still want to perform a C200/C200E to C300 ERDB conversion. E.g. Factory
Acceptance Test (FAT). In addition, the Off-Process upgrade will be the default option under these
conditions:
o If your C200 controller is facing a Communication Error
o If the same C200 FTEB Device index is used for C300 while performing Transform
Configuration.
o If FIM2 is configured with C200 or if it is a Supervisory FIM
-7-
Chapter 1 - About this guide
l Off-Process upgrade without Upgrade Tool - Means a manual upgrade. However “Server and
Controller Readiness Checks” can be used for checking system readiness. See Off-process
upgrade without Upgrade Tool .
C200/C200E Controller to the UOC Controller
This section describes the tasks associated with an off-process upgrade using the C200 Upgrade Tool.
The detailed procedures for an off-process upgrade without using the tool are not available as they are
site-specific and there is no formal process for the same.
1.3 Revision history
Revision Date Description

A June 2021 Initial release of the document
1.4 Intended audience

This guide is primarily intended for Honeywell field personnel working along with the end users, for
performing this upgrade. It is assumed that these personnel have technical knowledge of both
C200/C200E, C300, and UOC systems, additionally, FIM2 and FIM4/FIM8 systems for performing
C200/C200E controller to the C300 controller upgrade. QVCS knowledge will be an advantage if
strategies are in QVCS.
1.5 Related documents

Document Description
Network and Security Planning Guide Provides information about network planning.
Fault Tolerant Ethernet Overview and Provides an overview of FTE.
Implementation Guide
Fault Tolerant Ethernet Installation and Provides information about installing FTE.
Service Guide
Fault Tolerant Ethernet Status Server and Describes the installation of the FTE status display
Auxiliary Display User’s Guide and FTE status server, and the usage of the FTE
display.
Ethernet IP User's Guide Provides an overview of Ethernet IP.
UOC User's Guide Provides an overview and information about
installing and configuring UOC.
ControlEdge 900 Hardware Planning and Describes the process to set up ControlEdge 900
Installation Guide platform and install UOC.
Control Building User's Guide Describes the usage of the Control Builder for
configuring and loading the strategies.
Control Builder Parameter Reference Provides information about the parameters.
Control Builder Error Code Reference Provides information related to the errors that
appear in the Control Builder.
Control Builder Components Theory Provides information about the usage of the
function blocks in the Control Builder.
-8-
Document Description
Control Builder Components Reference Provides quick reference about the function blocks.
Server and Client Configuration Guide Provides detailed procedures for configuration of an
Experion server and client system.
PROFINET User’s Guide Provides information about the PROFINET protocol
implementation in UOC and its extent, capacity,
assembly, maintenance, and field network.
Peer Control Data Interface Implementation To configure and establish PCDI during SIM to PCDI
Guide conversion.
Rockwell recommended security practices To learn about security best practices for security
provided in Rockwell’s documentation issues with Rockwell’s components, visit Rockwell’s
website and see Rockwell’s documentation.
ControlLogix Enhanced Redundancy System Provides information about the Enhanced
Release Notes available at the Rockwell redundancy Scheme and configuration.
website
http://www.rockwellautomation.com/literature/
Ethernet/IP Network Devices User Manual Provides information about 1756-EN2TR EthernetIP
available at the Rockwell interface module and the process to configure the
website module.
ControlNet Configuration User Provides information about configuring the 17656-
Manual available at the Rockwell CN2R ControlNet Interface Module added to the
website EIP-ControlNet bridge and establishing
http://www.rockwellautomation.com/literature/ communication on the I/O ControlNet Network .
Control Firewall User's Guide Provides information about installing, configuring,
and troubleshooting the 9-port Control Firewall.
C300 Controller User's Guide Provides information about installing, configuring,
and troubleshooting the C300 Controller.
Series C Fieldbus Interface Module User's Provides information for planning, installing,
Guide configuring, operating and maintaining of Series C
Fieldbus Interface Modules (FIM4/FIM8).
Qualification and Version Control System Provides information of Qualification and Version
User's Guide Control System.
Contact Honeywell TAC or Migration COE To perform a safer and secure disposal of the C200
team hardware.
1.6 Terms and definitions

The following table lists the terms used in this document.
Term Definition
AI Analog Input
AO Analog Output
C200/C200E Controller in Process Manager Input/Output packaging
UOC Unit Operations Controller
CDA Control Data Access
CEE Control Execution Environment
CM Control Module
-9-
Term Definition
CNET ControlNet
DI Digital Input
DO Digital Output
EMDB Enterprise Model Database
ERDB Engineering Repository Database
FIM Field Interface Module
FTE Fault Tolerant Ethernet
FTEB FTE Bridge
I/O Input/Output
(Typically, refers to devices that handle Inputs and Outputs)
IOLIM Input/Output Link Interface Module
IOTA Input/Output Termination Assembly
PCDI Peer Control Data Interface
PMD Process, Machinery, and Drives
RM Redundancy Module
SAM Server Activity Manager
SESP Software Enhancement Support Program
SIM Serial Interface Module
Supervisory FIM2 C200/C200E is not present in its same or downlink chassis
WMI Windows Management Instrumentation
Series A Chassis based I/O module family supported by C200/C200E and UOC
Controllers
vUOC Virtual Unit Operations Controller
1756-EN2TR Rockwell's Ethernet/IP Interface Module
1756-RM2 Rockwell's Redundancy Module
1756-CN2R Rockwell's ControlNet Interface Module
- 10 -
CHAPTER
2 C200/C200E CONTROLLER TO THE C300

CONTROLLER
2.1 Introduction

2.1.2 C200/C200E Controller to the C300 Controller 15
2.1.4 Understand the differences between C200/C200E and C300 17

2.1.5 Understand the differences between FIM2 and FIM4/FIM8 19
2.1.6 Hardware Software requirements 20

This section provides detailed information for planning and executing the migration of your
C200/C200E controller to the C300 controller. The migration involves upgrading the hardware,
network, and software required for the existing C200 system to work with the C300 controller.
The C200/C200E Controller to C300 Controller upgrade is not supported for releases R500.1 and
R511.1.
While the C200/C200E controller and its power supply and cabling will be physically removed and
replaced with the C300 controller, the existing I/Os will remain untouched. However, you must perform
the following upgrades.
Upgrade what Using this tool

Upgrade the network from CNET to FTE using the CNET to FTE upgrade tool
Upgrade the controller and I/O modules l Server and Controller Upgrade Readiness Checks
l C200 Upgrade Tool Transform Configuration
l C200 Upgrade tool
The upgrade can be performed in one of two ways—Live and Off-Process.

l A Live upgrade enables upgrading to C300 modules while holding outputs ensuring zero
engineering effort.
l An Off-Process upgrade is one wherein a loss of view occurs during the upgrade as the C200
controller is taken down, C300 controller is mounted, powered up, and loaded again.
The readiness checks and upgrade tools are tools that enable understanding the readiness of the
system, and helps upgrading the C200/C200E to C300 when it is connected to PMIO, Series A, and
FIM.
- 11 -
Chapter 2 - C200/C200E Controller to the C300 Controller
A comprehensive set of scenarios that were earlier unsupported are now supported. For example,
earlier, when the C200 controller had a communication error (applicable only for C200 to C300
Upgrade, not Experion Process Network upgrade) or if Series A modules existed, upgrade was not
possible.
Upgrade is considered off-process if controllers are facing communication errors. The comprehensive
set of scenarios under which migration can take place and the benefits from such an upgrade is
provided in these sections, Benefits of the upgrade, and Scope and Limitations.
Beginning with R500.2, support is provided for CNET to FTE Upgrade and C200/C200E to C300
Upgrade when the C200/C200E, its IOs, FIM2 and its FF Devices and strategies are in QVCS.
Off-process upgrade
The following table describes the scope and limitations of an Off-Process process upgrade with
upgrade tool:
Hardware Supported only under these Software Tool

conditions
Supported C200/C200E with l User has chosen to Experion R5xx; C200
perform off-process 50 ms CEE Upgrade
l PM I/O modules tool
l Controller has a
l RM
Communication error
l IOLIM l You are using the
l FTEB C200/C200E FTEB
Device index
l SIM with Serial/PLC
devices l If FIM is present
l FIM2
l Series A
Supervisory FIM l Configured Experion R5xx C200
l Module has a Upgrade
Communication error tool
Not LIOM and any other AB Drive Controller I/F (1203- Toledo Weigh
supported chassis-based modules CNI) 1757- scale I/O blocks
CN2FF module
2.1.1 Hardware upgrade

The following is a representation of the cabinet and the hardware before and after the upgrade. Note
that it is not to scale and is for instructional purposes only.
- 12 -
The C200/C200E chassis is affected.

The upgrade proceeds in the following stages.
Stage Description
1 Disconnect and remove C200/C200E controller chassis from cabinet
2 Mount the controller
3 Connect power supply cables and FTE cables
4 Power on C300 and CF9
Process to upgrade C200/C200E to C300 and FIM2 to FIM4/FIM8

Upgrade C200/C200E modules to C300 and FIM2 to FIM4/FIM8 modules using one of the following
methods:
Task Live Off-Process Off-Process Upgrade Supervisory

Upgrade With Without Upgrade Tool FIM
Upgrade Tool
This method Requires shutting Requires shutting down Enables
enables upgrading down the the control system upgrading
the C200/C200E C200/C200E during the upgrade the FIM2 to
modules to C300 Controller and FIM4/FIM8
modules while FIM2 chassis for modules.
holding outputs and which the upgrade
causing minimal is planned
disruption to the
process
Check upgrade Controller Controller Yes. Run the
readiness Supervisory
FIM2 Optionally, you can do it FIM2 to
manually.
FIM4/FIM8
readiness
check
Backup ERDB Yes Yes Yes Yes
Upgrade network Yes Yes Manual Yes
– CNET to FTE
(only if existing
network is CNET)
- 13 -

Upgrade Tool
Upgrade Yes Yes Yes Yes
C200/C200E
controller
hardware to C300 Delete strategies from
hardware the C200/C200E
controller. If FIM2 exists,
delete its FF devices and
strategies.
Shutdown the
C200/C200E/FIM2
system.
Install the
C300/FIM4/FIM8
system.
Connect the I/Os to the

C300 system, and also
connect the FF devices
to FIM4/FIM8 system.
Assign and load the

strategies and devices
to C300 and
FIM4/FIM8system
Power-on and startup

the C300/FIM4/FIM8
system.
Perform Yes Yes Manual Yes
transform of
C200/C200E to
C300 upgrade
and transfer
control
Post upgrade Activate Series A Disconnect I/Os You may have to re- Disconnect
activities and its related from C200 and configure some IOMs for FF devices
strategies, if connect to C300 the strategies from FIM2
available. link and
Also disconnect FF connect to
devices from FIM2 FIM4/FIM8
link and connect to
FIM4/FIM8
Power-on
and start-
Power on and start up
the C300 and
FIM4/FIM8
FIM4/FIM8
- 14 -

Upgrade Tool
Load C300 and its Load
strategies; load strategies
strategies and and
devices to devices to
FIM4/FIM8 FIM4/FIM8
Benefits of the upgrade
Live upgrade
This upgrade enables you to benefit from the Experion Series C system by upgrading to the C300
Controller. There is no investment and planning required for additional space and cabinet if the
upgrade is performed using the hardware upgrade kit. In such a case, you can reuse the existing
C200/C200E chassis space to mount and install the C200 to C300 upgrade kit. The only investment
required for this upgrade is for procuring the hardware upgrade kit.
You may also have to procure FTEB modules if Series A is configured as a part of the existing C200
setup.
This upgrade enables upgrading to C300 modules while holding outputs ensuring zero engineering
effort.
Off-Process upgrade
This upgrade enables you to benefit from the Experion Series C system by upgrading to the C300
Controller and FIM4/FIM8 modules.
For C300 modules, there is no investment and planning required for additional space and cabinet if the
upgrade is performed using the hardware upgrade kit. In such a case, you can reuse the existing
C200/C200E chassis space to mount and install the C200 to C300 upgrade kit. The only investment is
required for this upgrade is for procuring the hardware upgrade kit.
Upgrading to FIM4/FIM8 modules ensures reduction in the overall FIM modules. However, FIM4/FIM8
modules are not available as part of upgrade kit.
This upgrade enables upgrading to C300 modules and FIM4/FIM8 ensuring reduced engineering effort.
You may also have to procure FTEB modules if Series A is configured as part of existing C200 setup.
Supervisory FIM2 modules
Upgrading to FIM4/FIM8 modules ensures reduction in the overall FIM modules. However, FIM4/FIM8
modules are not available as part of the upgrade kit.
This upgrade enables upgrading to FIM4/FIM8 ensuring reduced engineering effort.
2.1.2 C200/C200E Controller to the C300 Controller

For every C200/C200E that you want to upgrade, a C300 control solver license is required. With an
upgraded C300 license, you can load either a C200/C200E or a C300.
After you procure the license, update the license key to replace the C200/C200E control solver license
with the C300 control solver license. You cannot proceed with the C200/C200E to C300 Controller
upgrade if you do not have sufficient C300 control solver licenses.
No license is required for the C200 Upgrade tool. If SIM to PCDI upgrade is planned, then purchase the
PCDI license to use the related functions. The PCDI Master block is created based on the SIM FTAs
used, not on the SIMs configured. Purchase PCDI licenses based on the usage of SIM FTAs.
- 15 -
Control solver license options applicable for Control solver license options applicable for Off-
Live upgrade Process upgrade
TC-CSUG50|C200 TO C300 CONTROL SOLVER TC-CSUG20|C200 TO C300 CONTROL SOLVER
UPG, 50MS UPG, 20MS
TS-CSUG50|SESP C200 TO C300 CONTROL TS-CSUG20|SESP C200 TO C300 CONTROL SLVR
SLVR UPG, 50MS UPG, 20MS
TC-CSUG50|C200 TO C300 CONTROL SOLVER
UPG, 50MS
TS-CSUG50|SESP C200 TO C300 CONTROL SLVR
UPG, 50MS
The hardware model numbers are listed in the section, Upgrade kits.
2.1.3 Scope and limitations

Live upgrade
The following table describes the scope and limitations of a live upgrade.
Hardware Third-party modules/ Software Tool

interfaces
Supported C200/C200E with: ExperionPKS_R5xx C200
l PM I/O 50 ms CEE Upgrade
modules tool
l RM
l IOLIM
l FTEB
l Series A*
l SIM with
Serial/PLC
devices
Not l LIOM AB Drive Controller I/F Toledo Weigh scale
supported (1203-CNI) 1757- I/O blocks
CN2FF module
* Series A I/O modules are supported on C300 with additional hardware (offline upgrade only). For
more information, see section Understand the differences between C200/C200E and C300.
Off-process upgrade
The following table describes the scope and limitations of an Off-Process process upgrade with
upgrade tool:
- 16 -
Hardware Supported only under these Software Tool

conditions
Supported C200/C200E with l User has chosen to Experion R5xx; C200
perform off-process 50 ms CEE
l PM I/O modules Upgrade
l Controller has a tool
l RM
Communication error
l IOLIM l You are using the
l FTEB C200/C200E FTEB
Device index
l SIM with Serial/PLC
devices l If FIM is present
l FIM2
l Series A
Supervisory FIM l Configured Experion R5xx C200
l Module has a Upgrade
Communication error tool
Not LIOM and any other AB Drive Controller I/F (1203- Toledo Weigh
supported chassis-based modules CNI) 1757- scale I/O blocks
CN2FF module
2.1.4 Understand the differences between C200/C200E and C300

To know more about C300 and its functions, see the C300 specifications from the Honeywell Process
Solutions website http://www.honeywellprocess.com.
Considerations for continuing to use LIOM after upgrading to C300
C300 with Series A Chassis I/O topology with FTEB enables C300 to interface with Series A I/Os. You
can enable a tighter integration of this solution by connecting FTEB to CF9, which is mandatory.
Upgrade third-party modules/interfaces connected to C200/C200E
To continue using the Series A SIM with C300 after upgrading to C300, configure the Series A SIM to
communicate through C300 with Series A Chassis I/O topology with FTEB. Alternatively, use PCDI or
SCADA instead of Series A SIM. TCP to Serial Gateway hardware may be required for SIM with PCDI.
Additionally, to maintain any Exchange block communication through ControlNet to third-party PLCs,
you may need to retain the Series A IO chassis and a FTEB module in that chassis as a gateway for
C300 to interoperate peer-to-peer with ControlNet, DH+, or CIP Ethernet resident PLCs and AB devices
(for example, Panel View) using the Exchange Block library. In addition, modify the path in Exchange
blocks, re-configure, and reload them after the upgrade.
IOU loading differences between C200/C200E and C300
The Input/Output Unit (IOU) loading of the C300 and C200/C200E is different for some of the
Input/Output modules. The following table lists IOU loading for the C300 and C200/C200E.
Upgrading C200/C200E with Series A to C300 with FTEB enhancements leads to changes in IOU limits
as detailed in the following table.
IOU limits for C200/C200E and C300 (before and after the FTEB firmware enhancements).
Table 1 : IOU limits for C200/C200E and C300 before and after FTEB firmware enhancements
- 17 -
Controller IO C200 / C200E C300 (After FTEB

Module (Expected) Enhancements)
1 PM I/O Processor Module 1 1
For redundant IOPs, each IOP pair is counted as 1
IO unit.
1 Series C I/O Module NA 1
For redundant IOMs, each IOM pair is counted as 1
I/O unit.
1 Series A chassis-mounted I/O Module (except 1 1 (both C300 limit as well
some IOMs) as FTEB limit)
Consider C300 XU calculations when using Series A

I/O.
H Rail-mounted I/O Module 1 Not Supported
1 Serial Interface Module (SIM) per FTA 4 6* per FTA

I/O.
For SIM using both FTAs, this count is doubled to 8

and 16 IOUs, respectively.
1 Pulse Input Module (PIM) l 1 (for 64 1.5*
Unit/CPM
limit)
l 1.5 (for 24
Unit/CNI
limit)
1 Series C Fieldbus Interface Module (FIM4) NA 4
IOU count is the same for both redundant and non-
redundant configuration.
1 Series C Fieldbus Interface Module (FIM8) NA 8
1 Series C Profibus Gateway Module (PGM) NA 4
1 DHRIO Module l 1 (for 24
Unit/CNI
Limit)
l 0 (for 64
IOU limit)
- 18 -
Controller IO C200 / C200E C300 (After FTEB

Module (Expected) Enhancements)
1 (1203-CN1) AB Drive Controller 1
1 SST-PFB-CLX Profibus Module l 2 (for 64 l 4.5 (for 64 Unit/C300
Unit/CPM Limit)
Limit)
I/O. l 3.5 (for 16 Unit/FTEB
l 6 (for 24 Limit)
Unit/CNI
Limit)
1 DeviceNet Bridge Module (DNB) l 2 (for 64 l 4* (for 64 Unit/C300
Unit/CPM Limit)
Consider C300 XU calculations when using Series A Limit)
I/O. l 3.5* (for 16
l 2 (for 24 Unit/FTEB Limit)
Unit/CNI
Limit)
1 Source or Destination Device on Auxiliary (for 24 Unit/CNI
Exchange peer to peer network Limit)
* Based on theoretical calculation
2.1.5 Understand the differences between FIM2 and FIM4/FIM8

To know more about FIM4/FIM8 and its functions, see the FIM4/FIM8 specifications from the Honeywell
Process Solutions website http://www.honeywellprocess.com.
FIM specifications
Specification FIM2 FIM4 FIM8

Number of H1 networks 2 4 8
per FIM2 (Link)
FF Device limit 16 FF Devices 16 FF Devices per Link 16 FF Devices per Link (16*8 =
per Link (16*2 (16*4 = 64) cabinet) 128) useful for performing
= 32) readiness checks)
Controller support Only Only C300 Only C300
C200/C200E
Maximum Peer 5 5 5
connections per FIM
Maximum number of 21 Non 15 Redundant or Non 8 Redundant or Non redundant
FIM2(s) per Controller redundant or redundant in any in any combination
12 redundant combination
Capacity Description 1 second 1 second minimum 1 second minimum

(FIM2 cache parameter minimum
refresh rate)*
FIM2 Cache will refresh parameter values at a maximum rate of once per second. If all parameters
cannot be refreshed within one second due to bandwidth limitations, the FIM2 will allocate additional
time as needed. Actual performance will depend on the number of parameters within FIM2 Cache,
device performance, and unscheduled bandwidth available on H1 Network.
- 19 -
FIM H1 network specifications
Specification FIM2 FIM4 FIM8

Maximum Number of 16 16 16
Fieldbus Devices per H1
Network
Agents per H1 Network 50 per H1 Network 100 per H1 Network 100 per H1 Network
Maximum Number of 64 per H1 Network 128 per H1 Network, 128 per H1 Network,
VCRs (Virtual
Communication 128 per FIM2 512 per FIM4 1024 per FIM8
Relationships) per H1 See Note See Note See Note
Network
Maximum Scheduled 16 per H1 Network 16 per H1 Network 16 per H1 Network
Single-Variable
Publications per Second
per H1 Network
Unscheduled Parameter 16 per Fieldbus Device, 16 per Fieldbus Device, 16 per Fieldbus Device,
Reads per Second per
H1 Network 40 per H1 Network 40 per H1 Network 40 per H1 Network
Unscheduled Parameter 5 burst, 1 sustained per 5 burst, 1 sustained per 5 burst, 1 sustained per
Writes per Second per Fieldbus Device, 20 Fieldbus Device, 20 Fieldbus Device, 20
H1 Network burst, 5 sustained per burst, 5 sustained per burst, 5 sustained per
H1 Network H1 Network H1 Network
Available Macrocycle 250, 500 ms.; 1, 2, 4, 8, 250, 500 ms.; 1, 2, 4, 8, 250, 500 ms.; 1, 2, 4, 8,
Periods 16, and 32 sec. 16, and 32 sec. 16, and 32 sec.
Device reload or device replacement functionality requires at least one free VCR on a Fieldbus
link/segment. If a segment is configured with the maximum number of VCRs allowed (64 for the FIM2 or
128 for the FIM4), a device replacement will not be able to done without freeing a VCR on the segment
first. Freeing a VCR is typically done by deleting a CM or device from the monitoring tree. Therefore, it is
recommended that at least one VCR is kept free so that device reloads or replacement will not require a
VCR to be freed first. Control Builder will display a warning message when a segment is low on free
VCRs.
2.1.6 Hardware Software requirements

C200/C200E Controller to the C300 Controller
Live upgrade
Upgrade option Hardware Software

Option 1* Standard Series C hardware (mounted in a new Series C C200 Upgrade
cabinet) tool
Option 2* C200/C200E to C300 hardware upgrade kit C200 Upgrade
tool
- 20 -
Off-Process upgrade with Upgrade Tool
Upgrade Hardware Software

option
Option 1* Standard Series C hardware including FIM4/FIM8 (mounted in a new C200 Upgrade
Series C cabinet) tool
Option 2* C200/C200E to C300 hardware upgrade kit. C200 Upgrade
tool
FIM4/FIM8 module mounted on standard Series C cabinet
* FTEB hardware modules will be required if Series A modules exist in the system being upgraded.
Sub pan is a cabinet-less solution that comprises of a flat metal sheet that allows you to mount the
Series C components.
2.1.7 Interoperability requirements

The interoperability of the controller with respect to the Experion server version and amongst the
controllers themselves is governed by the interoperability rules of the Server Experion release. Hence,
refer to the corresponding Experion server version SCN to understand the interoperability rules.
For example, if the upgrade is taken up on a R500.2 server, then the C200 controllers can have the
latest firmware supported in R400.1 or later. If the upgrade is taken up on a R501.1 server, then the
C200 controllers can have the latest firmware supported in R310.2 or later. These interoperability rules
are provided in the R500.2 and R501.1 SCNs.
2.1.8 User Privilege requirements

To install the C200 Upgrade Tool, you must be a member of the Windows Administrator group. To
perform the upgrade you must be a member of the Local Engineers group.
2.2 Plan the C200/C200E to C300 Upgrade

2.2.4 Upgrade kits 27
There are no detailed procedures for performing an Off-Process upgrade since it is a site-specific
activity and there is no formal process for the same. However, the planning and preparatory activities
are common for both live and Off-Process upgrades.
2.2.1 Planning considerations

Planning for an upgrade involves the following high-level tasks.
- 21 -
Tasks Details
Assess your site l Identify the C200/C200E Controller modules with PM I/O, Series A, and
requirements. FIM2 that you want to upgrade.
l Series A and its strategies are inactive during the live upgrade. The
strategies that contain the Series A blocks and strategies that have
reference to Series A blocks must be reviewed. Similarly, impact of Series
A and its strategies which remain inactive on the process must be
reviewed.
l The FIM2 configuration will perform the process Off-Process. However,
the C200 Upgrade tool can be used to automate the Off-Process
upgrade.
l Determine the type of upgrade (live upgrade or Off-Process upgrade with
tool, or Off-Process upgrade without tool) depending on the type of your
controller setup and IO/ interface module (redundant or non-redundant).
l Identify if the configurations are in QVCS. For more information on
changes that will be made to upgraded configurations that are in QVCS,
see the section QVCS details.
l During the upgrade, the strategies in the other controller INITIATING peer
connections to the controller that is being upgraded need to be re-
downloaded post successful upgrade to C300 for re-establishing the
connection. Hence, there will be a disruption in these peer connections.
l Meet the prerequisites and understand the assumptions for this upgrade.
Before starting the C200 /C200E to C300 migration, make a list of the
inactive and non-loaded CMs/SCMs so that those CMs can be left in the
same state after the migration.
See the “Prerequisites and assumptions”.

Understand the If you are not familiar or have not used the Series C system earlier, it is
differences recommended to complete the following:
between
C200/C200E and
l Read the C300 Controller specifications from the Honeywell Process
C300. Solutions website http://www.honeywellprocess.com.
l Understand the Input/Output Unit (IOU) loading differences between
C200/C200E and C300. See the “IOU loading differences between
C200/C200E and C300”.
l Some I/Os supported by the C200/C200E Controller do not work with
C300. Therefore, you may need to re- configure the strategies with C300,
or procure new hardware if the I/O is not supported with C300.
C300 does not support FIM2.

Understand the If you are not familiar or have not used the Series C system earlier, it is
between FIM2 and
FIM4/FIM8
l Read the FIM4/FIM8 module specifications from the Honeywell Process
Solutions website http://www.honeywellprocess.com.
l Understand differences between FIM2 and FIM4/FIM8. See the note
“"IOU loading differences between C200/C200E and C300" on page 17
Familiarize with the The live upgrade process or Off-Process process with upgrade tool involves a
upgrade process combination of hardware and software upgrade steps to be performed.
and the tools Therefore, it is important to familiarize yourself with the process and tools
required for the before the upgrade.
same.
l Familiarize yourself with the C200/C200E to C300 hardware upgrade kit
and its contents. See the section, Upgrade kits.
l Install and get started with the C200 Upgrade tool. See the section Install
- 22 -
Tasks Details
the C200 Upgrade Tool.
l Familiarize yourself with the upgrade workflow.
Familiarize yourself See the section, “Upgrade tool workflow.
with the upgrade
workflow.
2.2.2 Prerequisites and assumptions

Before you proceed with the upgrade, understand, and meet the following prerequisites:
If there are C200/C200E peer-to-peer connections across clusters, ensure that FTEBs are mounted and
running in all the applicable controller chassis, before performing CNET to FTE upgrade.
This is needed only for systems starting on ControlNet.
Before upgrade, ensure that you verify the I/O loading from the section, “IOU loading differences
between C200/C200E and C300”.
When the C200/C200E Checkpoint is restored to the C300, function blocks such as Timer, Totalizer,
Counter, Sequence Control Module (SCM) and Recipe Control Module (RCM) are not restored with
their current run-time values. Instead, these function blocks are restored with the C200/C200E
Checkpoint value. You must ensure to plan your process and the upgrade accordingly.
If Live Upgrade is being performed on a redundant server, then the Server A should be healthy and
synchronized with Server B.
Following are the examples for the restart behavior of the blocks, based on the C300 Startup type
(COLD START/WARM START). The details of all the blocks are available in the Knowledge Builder.
l RampSoak block — The behavior is the same for Cold Start and Warm Start. Set the behavior as
follows:
o MODE to manual
o CV to NaN
o Reset internal timers
o Current profile identifier to first
o Current segment identifier to first
o RESETTIMER to On
o Apply STARTOP[ ] value at next Man to Auto transition
l Regulatory Control (REGCTL) block – If the CEE Restart option of REGCTL blocks are configured
other than FOLLOWCEE, the CEE Restart option of REGCTL blocks overrides the CEE command
selection of C300 Controller.
Behavior is always safe because it forces the ramping action to stop and wait for the involvement by the
operator.
l AuxCal block — The behavior is the same for Cold Start and Warm Start. Set the behavior as follows:
o C[X] result value is set to NaN
l On restart it starts calculating the expression result all over again.

l Totalizer block — On cold restart, it stops totalizing and on warm restart, either it stops totalizing or
continues totalizing based on the configured equation.
For more information about the Checkpoint Restore of the function blocks, see Control Building
User's Guide.
- 23 -
Applicable for Live upgrade.

Ensure that the prerequisites of C300, CF9 and FIM4/FIM8 components are verified.
For information about the prerequisites of C300 and CF9 modules, see the following
documents:
l C300 Controller User's Guide
l Control Firewall User's Guide
l Series C Fieldbus Interface Module User's Guide
Adhere to the guidelines to be followed before and after installing the C300, CF9, and FIM4/FIM8
components.
The Experion Upgrade Tool must not be in use whenever you start/use the C200 Upgrade tool.
2.2.3 Site requirements

Read and answer the following checklist before ordering Experion components for migrating
C200/C200E modules to the C300 system.
- 24 -
Task Description References, if any

Determine the Identify the modules that are configured with the controller
C200/C200E being upgraded.
Controllers, Series
A chassis, and
FIM2 that need to
be upgraded
Determine the Migrate the control system to Experion R5xx and ensure the Server Upgrade
upgrade readiness controllers are running at a release that meets the Readiness
of the control interoperability requirements. Checks.
system
Install and use the C200 Upgrade tool to perform readiness
checks on the control system. Readiness checks help in
planning the upgrade. Performing the readiness checks
helps in understanding the impact on the process and
control loops.
Performing the readiness checks using the C200 Upgrade
tool helps you to choose the right type of upgrade.
For example, as part of the readiness check, if some
unsupported modules like LIOM are identified, opt for the
Off-Process upgrade without tool. If FIM module is present
opt for Off-Process upgrade with tool.
Choose the During a live upgrade, loss of view is experienced
upgrade method temporarily. However, with the console station in place,
- Live/Off-Process there will be no loss of view across the cluster. The C200
using tool Upgrade tool is also used for the upgrade.
l Manual Off-Process upgrade with Upgrade Tool requires you to

shut down the upgrading modules and then complete the
upgrade. C200 Upgrade tool can be used. However you
need to perform the load for C300 Controller and
FIM4/FIM8, manually. In such instances, the process is
disrupted during the entire upgrade process.
Manual method involves performing upgrade without

Upgrade Tool and requires you to shut down the control
system and then complete the upgrade. In such instances,
ensure if the loss of control can be tolerated and for how
long.
Determine how Procure the hardware upgrade kit if the existing Upgrade kits.
you want to mount C200/C200E chassis space for horizontally mounting the
your Series C Series C modules must be re-used. In this case, you can
modules also reuse the existing PM I/O power supply.
Procure the standard Series C hardware if you want to go
for a standard C300 and FIM4/FIM8 setup. Ensure to
procure additional power supply and a RAM battery backup.
Procure the sub pan hardware to use a sub pan C300 and
FIM4/FIM8 hardware setup.
Determine the To reuse the existing C200/C200E chassis space for C200/C200E to
number of C200/ mounting the Series C modules, determine the number of C300 hardware
C200E to C300 C200/C200E to C300 upgrade kits that you must procure. Upgrade kit.
upgrade kits to be
procured Procure one upgrade kit per redundant controller setup.
Determine the To perform an upgrade using the standard Series C, procure Overview of the
standard Series C the same. Series C
hardware to be hardware.
procured
- 25 -

Determine the One FTEB module per controller chassis is required. If you
number of FTEB have peer-to-peer C200/C200E Controller connections,
modules and FTE install FTEB in all the peer controller chassis as well.
cables to be
procured You can plan and execute the task of adding the FTEB in
the controller chassis ahead of your upgrade activities.
If Series A is configured, procure one FTEB module per

Series A chassis.
You may have to add more FTEBs for extra racks only if the
redistribution of Series A modules makes it necessary.
Download and The C200 Upgrade tool is the starting point for a live
install the C200 upgrade. Install the tool on Server B in an Experion cluster
Upgrade tool for readiness checks and actual upgrade. Install the C200
Upgrade tool on Server A for CNET to FTE Upgrade only.
The C200 Upgrade tool is optional for an Off-Process
upgrade.
However, you can still use it to verify the readiness of your
control system before the upgrade.
The C200 Upgrade tool is internal to Honeywell. It can be
downloaded and installed only by Honeywell field
personnel.
Consider replacing It is recommended that the following rechargeable batteries
RAM batteries if are to be replaced for better performance:
they are older
than 3 years NiCad batteries: NiCad batteries that are installed in the PM
I/O standard power system to provide standby power for
the CMOS memory must be replaced after every two years
of operation.
48V Backup Battery that is the lead acid batteries provide
20 minutes of standby power to the controller and PM I/O
Power System must be replaced every 3 years.
Determine if the One of the prerequisites for an upgrade is that the Servers
Servers are must already be on FTE topology. If they are not, procure
already on FTE the necessary FTE hardware, install, and upgrade your
topology Supervisory Networks to FTE topology.
Contact Honeywell TAC on how to upgrade your Supervisory
Networks to FTE.
Determine your If the control system is not on the required Experion release
current Experion for performing the upgrade, migrate the control system to
release the required release.
Decide the plan If the third-party devices/interfaces are connected to “Considerations
for upgrading C200/C200E, you may want to read the C300 Specifications for upgrading
third-party from the Honeywell Process Solutions website: third-party
devices/interfaces modules/interfaces
connected to your http:// www.honeywellprocess.com and determine if they are
connected to
supported on C300 as well.
C200/C200E C200/C200E”.
Controller If third-party devices/interfaces are not supported on C300,
contact Honeywell TAC on how to proceed with the
upgrade.
If the third-party devices/interfaces are connected to your

C200/C200E through CNET, some of these configurations
on the CNET network are not detected by the tool. For
example, Panel View connected to your C200/C200E
- 26 -

through CNET. Using the FTEB Module as a Gateway, the
C300 can interoperate peer-to-peer with ControlNet, DH+,
or CIP Ethernet resident PLCs and AB devices (for example,
Panel View) using the Exchange Block Library in a manner
similar to the C200.
Determine how During live upgrade, controller redundancy is disabled.
long can loss of Therefore, it is important to be aware of the loss of
redundancy be redundancy and determine how long the loss can be
tolerated tolerated.
Determine the Determine the number of FIM4/FIM8 modules that you
number must procure.
FIM4/FIM8
modules to be
procured
Determine the Identify the modules and their strategies that are in QVCS See the section
modules and their QVCS details.
strategies that are
in QVCS
The time required for an upgrade is configuration-specific.
2.2.4 Upgrade kits
C200/C200E to C300 hardware upgrade kit
Upgrade kits (CC-ZHMT10 and CC-ZHR041) are available for replacing chassis-based modules such
as C200/ C200E Controller, FTE Bridge, Redundancy Module, and IOLIM, with Series C modules such
as C300 Controller and Control Firewall.
Upgrade kit model numbers
The following table lists the model numbers of each upgrade kit.
Model Number Description

CC-ZHMT10 C300 Horizontal Mounting Kit in PM Cabinet
CC-ZHR041 UHIO kit with redundant C300 and redundant CF9
This upgrade kit contains two sets of C300 Controller and 9-port Control Firewall. The following figure
displays the layout of the CC-ZHR041 upgrade kit.
- 27 -
Layout of CC-ZHR041
In this figure, 1 and 2 denote the two sets of C300 Controller and 9-port Control Firewall.
Upgrade kit part numbers and component details
Part numbers of CC-ZHMT10
The following table lists the part numbers of the CC-ZHMT10 kit.
Part Number Description Quantity

51306877-100 Backplate, Mounting, UHIO 1
51202341-102 I/O link – PM to Series C I/O link cable 1
51202984-100 Cable for C300 Memory Backup Power 2
51202347-200 24V Power cable 2
99000222-740 Screw, Mach, Pan-Head, Slotted, M5x40L, ISO-1580 5
51195195-346 Trade-in instructions for upgrade kits 1
51195168-616 Screw, Thread Forming, BLACK, M5x16 5
51108884-006 LOCK WASHER, SPLIT, M5 5
Part numbers of CC-ZHR041
The following table lists the part numbers of the CC-ZHR041 kit.
Part Number Description Quantity

51454504-175 Horizontal Backplane, Coated 1
51307206-175 Horizontal C300/CF9 IOTA, Coated 2
51405047-175 Control Firewall 9 Module 2
51405046-175 C300 Control Processor 2
- 28 -
Overview of the Series C hardware
The following table lists Series C hardware and their model numbers required for migrating the
C200/C200E to C300.
Series C Description Model Number

Component
C300 Controller A distributed process controller and I/O gateway for the CC-PCNT01
Module Experion system. Module contains printed circuit assemblies,
status indicators and a display, inside in a plastic housing.
Module mounts to its Input Output Termination Assembly
(IOTA).
C300 Controller Provides the connection point for the C300 Controller module CC-TCNT01
Input Output and all cable terminations to the controller, (FTE, IOLink,
Termination Redundancy, Battery, and Time Source cable terminations).
Assembly (IOTA) Provides 24 Vdc power distribution to the controller module.
The C300 Controller IOTA supports only one controller module.
9 Port FTE Control Provides FTE distribution to the cabinet network nodes, (other CC-PCF901
Firewall Module C300 Controllers and Series C FIMs)
9 Port Control Provides connection for the eight FTE cables from in-cabinet CC-TCF901
Firewall IOTA controllers and Series C FIMs. The 9th port provides an uplink
to the FTE supervisory network. Provides 24 Vdc power
distribution to the CF9 module.
FTE Cable STP CAT5 Cable with RJ 45 connectors for FTE connections.
2 m (6.5 ft) 51305482-102
(Y)
(Y) = Yellow coded boots
513054820202
(G) = Green coded boots (G)
5 m (16 ft) 51305482-105
(Y)
513054820205
(G)
10 m (33 ft) 51305482-110
(Y)
513054820210
(G)
20 m (65.5 ft) 51305482-120
(Y)
51305482-220
(G)
Redundancy Cable STP CAT5 Cable with RJ 45 connectors joining primary and
secondary controllers.
IOLink Cable Multidrop cable assemblies to connect the I/O modules of a xxxxxxxx-xxx
controller IOLink.
Battery Cable Multidrop twisted pair cable to connect battery power to xxxxxxxx-xxx
controllers.
IOTA Channel Aluminum channels that provide a mounting medium for the CC-MCHN01
Supports IOTA Channel.
IOTA Channel Assembly for mounting the Series C hardware IOTAs. CC-MCAR01
Channels contain power and grounding busbars are mounted
- 29 -
Series C Description Model Number

Component
onto IOTA channel supports.
Power Supply, Non- 24 Vdc, 20 A power supply. Provides non-redundant power to CC-PWRN01
redundant no Channel busbars and Series C IOTAs.
Battery Back Up
Power Supply 24 Vdc, 20 A fully redundant power supply. Provides redundant CC-PWRR01
Redundant, no power to Channel busbars and Series C IOTAs.
Battery Back Up
Power Supply, 24 Vdc, 20 A fully redundant power supply with battery backup. CC-PWRB01
Redundant with Provides redundant power to Channel busbars and Series C
Battery Back Up IOTAs.
COTS Power Supply 24 Vdc, 20 A COTS power supply. Provides redundant power to CU-PWMR20
(Meanwell) channel busbars and Series C IOTAs.
Redundant, no
Battery Back Up
COTS Power Supply 24 Vdc, 20 A COTS power supply. Provides non-redundant CU-PWMN20
(Meanwell) Non- power to channel busbars and Series C IOTAs.
redundant, no
Battery Back Up
COTS Power Supply 24 Vdc, 20 A COTS power supply. Provides redundant power to CU-PWPR20
(Phoenix Contact) channel busbars and Series C IOTAs.
Redundant, no
Battery Back Up
COTS Power Supply 24 Vdc, 20 A COTS power supply. Provides non-redundant CU-PWPN20
(Phoenix Contact) power to channel busbars and Series C IOTAs.
Non- redundant, no
Battery Back Up
Horizontal backplane (UHIO based)
The UHIO Backplane is used for powering up the Series C form factor CF9/C300 IOTAs and to maintain
the same form factor as the C200/C200E chassis. The size and component placement of the Series C
CF9/C300 IOTAs is modified to fit on to the UHIO Backplane and thereby maintain the same form factor
as the C200/ C200E chassis modules.
The Backplane supports two CF9/C300 IOTA configurations.
The following figure displays the front view of the UHIO Backplane.
- 30 -
Environmental characteristics
The following table lists the environmental characteristics and requirements for the Series C
components.
Environmental Specifications Operating Limits Transportation and Storage Limits

Ambient Temperature Range 0 to +60 °C -40 to +85 °C
Temp. Rate of Change <= 1 °C/min <= 5 °C/min
Relative Humidity 4, 5 5 to 95% (non-condensing) 5 to 95% (non-condensing)
Barometric Pressure Altitude -300 to +3000 m Any
Corrosives G3 G3
Vibration
Frequency (Hz) 0–60 0–60
Acceleration (g) 0.2 0.2
Mechanical Shock
Acceleration (g) 5 25
Duration (ms) 30 30
Operating limits define the range of operating conditions within which the system is designed to
operate. Performance characteristics are defined when operating in this state. For more information
about the operating limits, see ANSA/ISA D 51.1
Transportation and storage limits define the range of conditions to which the system may be subjected
without permanent damage to the equipment. Performance is not guaranteed in this state. For more
information about the transportation and storage limits, see ANSA/ISA D 51.1.
The maximum relative humidity specification applies up to 40 °C. Above 40 °C, the RH specification is
de-rated to 55%, to maintain constant moisture content.
- 31 -
Electrical requirements
The following table lists the electrical requirements for the Series C components.
Model Part Number Description Current (amperes at)

Number 25VDC)
CC-PCNT01 51405046-175 C300 Controller, non-redundant 0.319
Control Firewall IOM (8 port + 1 uplink)
CC-PCF901 51405047-175 0.195
CC-HCAR01 51454504-175 Horizontal Backplane PWA, coated 0
Horizontal C300/CF9 IOTA PWA,
coated
CC-HCN911 51307206-175 0
The following table lists the electrical requirements for a UHIO upgrade kit:
Kit Model Number Description Current (amperes at 25VDC)

CC-ZHR041 UHIO kit with 2 sets C300, CF9 1.028
2.2.5 Upgrade tool workflow

At a high-level, the upgrade activity can be classified into two separate high-level tasks as network
upgrade and controller upgrade. These are two different stages of your upgrade and you can always
stop at network upgrade and plan your controller upgrade for a later date.
l Network upgrade —Upgrade all the C200/C200E controllers in an Experion cluster at once.
l Controller upgrade —Upgrade one controller at a time.
Therefore, plan the network upgrade and controller upgrade as separate activities. If the C200/C200E
Controllers are already on FTE, skip the network upgrade tasks.
The following figure displays the workflow diagram for a live upgrade:
- 32 -
2.3 Install the C200 Upgrade Tool
2.3.1 C200 Upgrade tools 34

2.3.2 Upgrade tool user interface 35
- 33 -
The C200 Upgrade tool is used to perform a live upgrade in a phased manner. Both the hardware and
the software upgrade steps must be performed in a combined sequence. At each step, the tool prompts
the action to be taken and provides work around for any issues. In an Experion cluster, install and use
the C200 Upgrade tool on Server B.
To upgrade Server A process network to FTE, install the tool on Server A also. For more information,
refer to "Upgrading the Experion Process Network to FTE" on page 167.
To install the C200 Upgrade tool on Experion Server A and Server B
1. In a web browser, type the following URL:
https://honeywellprod.sharepoint.com/teams/GPOEngTools/Lists/MasterList/DispForm.aspx?ID=33
1. The Global Product Engineering Tools team room page appears.
This website is applicable only for Honeywell internal users.
2. Download the C200 Upgrade tool installer for Experion R5xx.x.zip file.
3. Copy the file to a temporary folder on the Experion server.
4. Extract the C200 Upgrade tool installer for R5xx.x.zip file in the C:\temp path.
5. After extracting the C200 Upgrade tool installer for Experion R5xx.x.zip file, right-click the
executable file setup.exe, and then click Run as Administrator. The User Account Control dialog
box is displayed.
6. Follow prompts to complete the installation.
7. After a successful installation, click Finish.
By default, the C200 Upgrade tool is installed in C:\Program Files (x86)\Honeywell\Experion

PKS\C200toC300UpgradeTool. For custom installation path, navigate to <User selected
path>\Honeywell\Experion PKS\C200toC300UpgradeTool.
2.3.1 C200 Upgrade tools

The tool consists of the following components classified based on the phases of a live upgrade. Use the
components in the order listed in the following table. In addition, these components can be invoked
individually from the Start menu.
Component Purpose
Server and Controller Upgrade To perform all the readiness checks on the C200/C200E modules
Readiness Checks before starting the upgrade tool.
CNET to FTE upgrade To upgrade the Experion Process Network from CNET to FTE.
C200 Upgrade Tool Transform To replicate the C200/C200E control strategies in C300.
Configuration
C200 Upgrade tool To switch over the control from C200/C200E to C300.
For Supervisory FIM2 upgrade process, the Off-Process upgrade with Upgrade tool task sequence will
- 34 -
be applicable. However C200/C200E will not be present in Supervisory FIM2 chassis.

Although the C200 Upgrade tool is the starting point for the upgrade activity, some tasks must be
performed manually or by using other Experion engineering tools (for example, Control Builder,
DBAdmin, and ERDB Consistency Checker (ECC)) at every stage. For example, after you run the
readiness checks, depending on the failure, you may need to complete the work around manually
and repeat the readiness checks. In addition, all the hardware upgrade tasks must be performed
manually whenever prompted.
However, for Off-Process upgrade with C200 Upgrade tool, user shall manually load the upgraded
configurations to monitoring .
2.3.2 Upgrade tool user interface

This table describes all elements available in screens of the C200 Upgrade tool.
Common Options Description

elements
Title bar The title bar is the top-most element of the C200 Upgrade tool. Displays the title
of the user interface selected.
Menu File Open Project - Use this option to open a saved project.
bar
Save Project - Use this option to perform suggested workarounds and later re-
open the project and repeat the readiness checks on failed nodes/modules.
Saved project is used only to view the saved information. If there is no major
change in the L1 and L2 configuration in the cluster, rerun the readiness checks
from the saved project. However, it is recommended to run Readiness Check
Tool each time to get the most current state of the cluster.
Save Project as - Use this option to save the saved project in a different name.
Close Project - Use this option to close the opened project.
Exit - Exits the tool.
Help Launch Help - Opens the help file.
About - Provides version details of C200 Upgrade tool.
2.4 Readiness Checks

2.4.2 Readiness check types 36
2.4.3 Server upgrade readiness checks 37

2.4.4 CNET to FTE readiness checks 40
2.4.5 Controller upgrade readiness checks 42
2.4.6 Supervisory FIM2 readiness Checks 50

Before you start readiness checks, ensure that there are no consistency issues with the ERDB. To
ensure this, use the ERDB Consistency Checker (ECC) tool and resolve any consistency issues. You
can download the tool from the Honeywell Process Solutions website
http://www.honeywellprocess.com. For more information on downloading and using the tool, see the
Experion PKS Upgrade Tool User's Guide.
- 35 -
2.4.1 Ensure ERDB is not fragmented

To ensure that the ERDB is not fragmented, perform the following:
1. Choose Start > All Programs > Honeywell > Experion PKS > Configuration Studio. The Connect
dialog box is displayed.
2. Select a listed system and then click Connect.
3. Log on to the primary server with engineer (Engr.) security permissions.
4. On the Configuration Explorer tab, click Control Strategy in the tree view.
5. In the right pane, click Administer the control strategy database under the Process Control
Strategies section.
6. If prompted for User Account Control, click Yes. The DBAdmin dialog box appears.
7. Expand the DBAdmin.
8. Expand the Server Node item, and click ERDB Admin Tasks.
9. Click Update Statistics.
10. Click Yes. The indexes are rebuilt and the statistics are updated.
2.4.2 Readiness check types

Preparing for an upgrade involves verifying upgrade readiness of server, controller and the network.
Use the C200 Upgrade tool from Server B to perform these checks.
You must complete the readiness checks before starting the upgrade. If the checks fail, complete the
work-around as indicated in the tool and repeat the readiness checks until you succeed.
Do not proceed with the upgrade until all readiness checks are completed successfully.
The four readiness checks that you can perform using the C200 Upgrade tool are listed.
Readiness Check Type Description

Server readiness To perform both server and controller readiness checks. See, Perform
checks Server readiness checks.
CNET to FTE readiness To perform only CNET to FTE readiness checks. See, Perform CNET to FTE
checks readiness checks.
C200/C200E to C300 To perform only controller readiness checks. See, Perform C200/C200E to
readiness checks C300 upgrade readiness checks.
Supervisory FIM2 To perform only Supervisory FIM2 related readiness checks. See, “"Perform
readiness Checks Supervisory FIM2 readiness checks" on page 51”.
- 36 -
Perform these readiness checks up front since they help determine the impact on your process and
control loops. In addition, they help you decide if you can perform a live or an Off-Process upgrade. For
example, if there are unsupported modules in your C200/C200E chassis system, you may need to
perform an Off-Process upgrade for the controller or for the unsupported modules only. If there are FIM2
configured in your C200/C200E chassis system, you need to perform Off-Process upgrade with the
Upgrade Tool.
2.4.3 Server upgrade readiness checks

The Server and Controller Upgrade Readiness Checks screen displays the list of readiness checks to
be performed on the selected nodes and modules.
List of Server Readiness Checks and CNET to FTE Readiness Checks
The following tables list the 5.3Server Readiness Checks and CNET to FTE readiness checks that must
be completed successfully before proceeding with the upgrade.
The checks are categorized as Blockers, Warning and Manual.
l A blocker check is a readiness check that must be completed successfully before proceeding with
the upgrade.
l In case of a Warning check, you may proceed with the upgrade but it is recommended you take
necessary action per the information provided.
l Manual check is to be performed manually.
Server readiness checks

Readiness Checks Description/Workaround
Blockers Is Server at the Upgrade the Server to the supported point release of Experion if
supported release? the Server is not already upgraded.
Is the Server connected Upgrade the servers to the FTE topology if they are not on the
to Experion Supervisory FTE topology.
Network nodes (ACE,
Server, and Flex) via
FTE?
Is Server connected via If servers are connected to the Experion Process Network
CNET on Experion through FTE, you can skip the CNET to FTE Upgrade and
Process Network? proceed with controller upgrade.
Are there any IOLIMs Ensure that IOLIMs reside in the C200/C200E chassis only.
residing in Chassis
independent of C200?
Are there any If there are any unsupported modules, disconnect the modules
unsupported and delete modules and the strategies associated with those
modules/firmware? modules. If there are any modules with unsupported firmware
versions, upgrade the firmware compatible with the necessary
Experion release.
Are there any Interface If there are any interface modules connected to the Experion
modules (such as Process Network, identify if they are supported on C300 also
LIOM) connected to and upgrade accordingly.
Experion Process
Network?
Are there any active Run DBAdmin tool from the configuration studio.
locks?
Verify that there are no active locks in ERDB, EMDB.
- 37 -

If active locks are found, clear them.
Are there any Ensure that no Controllers/RM/IOLIM with backup name is
Controllers/RM/IOLIM missing. If so, click Execute to update the backup name.
with backup name
missing?
Are there any QVCS This check lists the strategies which are in checked-out state. If
elements in checked- any strategies are found in the checked-out state, perform
out state? Check-in before proceeding with the Upgrade.
Warning Is BootP Server The BOOTP Server service must be enabled and running on one
configured properly? of the server cluster pairs.
Manual Please ensure that Ensure that the empty slot is available in the server.
required empty slot is
available
Perform server readiness checks
This section describes how to perform server readiness checks and also describes the tool's General
Information and General Data Collection screens.
1. In the Server and Controller Upgrade Readiness Checks Tool, you cannot change the readiness
checks type if you are in General Data Collection screen or Readiness Checks screen. You must close
the Server and Controller Upgrade Readiness Checks Tool and open the tool again.
2. If the Server is connected through the FTE on the Experion process network, then the readiness
check Is Server connected via CNET on Experion Process Network fails.
The Sever readiness checklist includes CNET to FTE readiness checks and C200/C200E to C300
readiness checks.
If the Server is connected through the FTE on the Experion Process Network, then the readiness check
Is Server connected via CNET on Experion Process Network fails.
To perform server readiness checks
1. Log in to the Experion server with the least privilege as Local Engineer.
2. Click Start > Honeywell Experion Tools> All Honeywell Tools. Open the C200 Upgrade Tool folder
and double-click Server and Controller Upgrade Readiness Checks to launch the tool.
3. On the Provide User Credential dialog box, type the Password and click OK. The General
Information screen appears.
4. Select Server Readiness Check from the Readiness Check Type list.
- 38 -
5. Click Next. The General Data Collection screen appears. This screen provides information about
all the configured modules in chassis.
l The left navigation pane displays the list of configured chassis in the Experion cluster. Click a
node or a chassis to view the details in the right data pane. Select check box next to each node
to selected node(s) or chassis to perform tasks on. The L1 and L2 nodes (Server B or
standalone server of local machine) are by default selected and disabled.
l All the Supervisory FIM2(s) in the Experion cluster are seen under a node SUPERVISORY_
FIM
l The data pane on the right displays system configuration information of the chassis that
contains slot number, module name, module type, firmware version.
6. Click Next. The Add Computer dialog box appears.

7. Select the primary sever from the list of servers, which have exchange peer-to-peer connections
with this cluster and then click OK.
8. The Readiness Checks screen appears. Select the applicable nodes and modules. All the
nodes/modules are selected by default.
9. In the data pane on the right, select the required readiness checks for each node/module selected
in the left navigation pane. By default, all the readiness checks are selected for each node/module.
By default, the servers and chassis readiness checks are not performed and the status for server
and chassis are Not Executed.
- 39 -
10. Click Start to perform the selected readiness checks for the selected nodes/modules. The overall
status of the readiness checks for each node is displayed in the navigation pane. You can select a
node in the navigation pane to view the status of the individual readiness check in the right pane.
11. Click the hyperlink provided for each readiness check in the Status column. The server readiness
check starts and status of each readiness check is displayed in the right pane.
Use the Filter option to sort the readiness checks based on their status — Pass, Fail, Warning,
None, Not Applicable, Not Executed.
12. You can click Generate Report and save the list of readiness checks along with their execution
status in html format.
Even if you use a filter to sort the readiness checks, while generating a report all readiness checks that
have been selected regardless of their execution status are included in the report.
2.4.4 CNET to FTE readiness checks

CNET to FTE readiness checks must be performed to assess your Experion Process Network readiness
for upgrading to FTE.
If the Servers are connected to the Experion process network through CNET, the check Are the servers
connected to the Experion process network through FTE fails.
List of CNET to FTE Readiness Checks
CNET to FTE readiness checks

Blockers Is Server at the supported release? Upgrade the Server to the
supported point release
of Experion if the Server is
not already upgraded.
Is the Server connected to Experion Supervisory Network Upgrade the servers to
nodes (ACE, Server, and Flex) via FTE? the FTE topology if they
are not on the FTE
topology.
Is Server connected via CNET on Experion Process Network? If servers are connected
- 40 -

to the Experion Process
Network through FTE, you
can skip the CNET to FTE
Upgrade and proceed
with controller upgrade.
Are there any IOLIMs residing in Chassis independent of Ensure that IOLIMs reside
C200? in the C200/C200E
chassis only.
Are there any unsupported modules/firmware? If there are any
unsupported modules,
disconnect the modules
and delete modules and
the strategies associated
with those modules. If
there are any modules
with unsupported
firmware versions,
upgrade the firmware
compatible with the
necessary Experion
release.
Are there any Interface modules (such as LIOM) connected to If there are any interface
Experion Process Network? modules connected to the
Experion Process
Network, identify if they
are supported on C300
also and upgrade
accordingly.
Are there any active locks? Run DBAdmin tool from
the configuration studio.
Verify that there are no

active locks in ERDB,
EMDB databases.
If active locks are found,

clear them.
Are there any QVCS elements in checked-out state? Ensure that there are no
elements in checked-out
state in QVCS.
Are there any Controllers/RM/IOLIM with backup name Ensure that no
missing? Controllers/RM/IOLIM
with backup name is
missing. If so, click
Execute to update the
backup name.
Warning Is BootP Server configured properly? The BOOTP Server
service must be enabled
and running on one of the
server cluster pairs.
Manual Please ensure that required empty slot is available Ensure that the empty
slot is available in the
server.
- 41 -
Perform CNET to FTE readiness checks
To perform CNET to FTE readiness checks

2. Click Start > Honeywell Experion Tools > All Honeywell Tools. Open the C200 Upgrade Tool
folder and double-click Server and Controller Upgrade Readiness Checks to launch the tool.
4. Select CNET to FTE Readiness Check from the Readiness Check Type list.
all the configured modules in chassis.
with this cluster and then click OK.
8. The Readiness Checks screen appears. Select the applicable nodes and modules. All the
nodes/modules are selected by default.
in the navigation pane on the left. By default, all the readiness checks are selected for each
node/module. The chassis readiness checks and Supervisory FIM2 readiness checks are not
performed and the status for server and chassis are Not Executed.
status of the readiness checks for each node is displayed in the node tree. You can select a node
in the Navigation pane to view the status of the individual readiness checks in the data pane.
11. Click the hyperlink provided for each readiness check in the Status column.
2.4.5 Controller upgrade readiness checks

Ensure you close the Experion Upgrade Tool before starting the C200 Upgrade tool.
- 42 -
List of C200/C200E to C300 Readiness Checks
Controller Readiness Checks Applicable only

if
Readiness Checks Description/Workaround FIM is There
present is a
Comm
Error
Blockers Is Server connected to Connect the Server to Experion Process
Experion Process Network through FTE.
Network via FTE?
Is C200 redundant? Configure the C200 Controller as redundant.
Is base period of C200 Ensure that the base period configured for
configured for value C200 is 50ms.
other than 50ms?
Are there any Delete the associated strategies from NA
unsupported Control Builder and disconnect the modules
modules/firmware? before the upgrade.
If there are any modules with unsupported
firmware versions upgrade the firmware
compatible with the necessary Experion
release.
Are there function blocks Delete the function blocks manually from the
currently loaded to the Monitoring view and unassigned from Project
C200 which are not view.
supported in C300?
Are there any strategies This check lists the strategies outside this
outside this C200 that C200 that has reference to I/Os connected to
has reference to I/Os this C200. Update the references to the I/Os
connected to this C200? connected to the C200 and reload them.
Are there any redundant Ensures that controller/RM/IOLIM have a
Controllers/RM/IOLIM default backup name. If it is missing, the
without default check executes. Click Execute to update the
secondary name? backup name.
Ensure you re-load the secondary module to
Monitoring View.
Are there any QVCS This check lists the strategies which are in
elements in checked-out checked-out state. If any strategies are found
state? in the checked-out state, perform Check-in
before proceeding with the Upgrade.
Warning Is Peer Control Data Checks for the PCDI licenses available.
Interface license
available for all SIM If the system is not licensed to use PCDI,
being upgraded? please ensure that you do not select the SIM
to PCDI conversion check box while running
the Transform Configuration tool. If you
select this, the C200 to C300 upgrade will be
interrupted at a later stage.
Are number of I/Os Ensure that the I/Os configured in the
within the Controller Controller are in the Tech and Spec Limits
Tech and Spec Limits?
Are there any strategies This check lists the strategies in other
in other Controllers Controllers containing peer connections to
- 43 -

if
initiating peer the C200 Controller been upgraded.
connections to this
C200?
Are there any strategies This check lists the strategies initiating peer
initiating peer connections from this controller.
connections from this
C200?
Are there any strategies This check lists the strategies that are peer
in other Controllers with referenced to the parameters on this C200
peer references to block.
parameters on this C200
block?
Are there any strategies Delete the references to the parameters that
with references to do not work after the upgrade.
parameters on the C200
or CEE blocks that won’t
work after the upgrade?
Are there any strategies Exchange block paths must be updated
initiating Exchange peer before the upgrade.
C200?
Are there any strategies This check list the strategies in other
in other Controllers Controllers containing the exchange peer
initiating Exchange peer connections to the C200 Controller being
connections to this upgraded. Update the Exchange block path
C200? before the upgrade in the Project side and
then the tool loads the updated strategies.
Are there any strategies This check lists the strategies assigned to the
in other Controllers (in Controllers (in other Servers) initiating
other Servers) initiating exchange peer connections to the upgrading
Exchange peer C200 Controller. Update the Exchange block
connections to this path before the upgrade in the project side
C200? and then the tool loads the updated
strategies.
If the status shows that the Experion server is
“Not connected” then this is because the
servers are in two different Experion
releases, and this check is not able to identify
the Exchange strategies. Refer to the section
“Updating and loading the Exchange blocks
in peer Server” for more information.
Ensure current and peer cluster have the
same logon credentials.
Are there any dangling Resolve such connections with the right NA
peer connections? references.
Are there any peer Delete such peer references from the
references to the Monitoring view of Control Builder and reload
secondary blocks? them after the upgrade.
Are there any In Control Builder, right-click the controller NA
ghost/inconsistent and select the Identify ERDB/ Controller
modules in the inconsistency option.
controller?
Delete the listed inconsistencies.
- 44 -

if
Is BootP Server The BOOTP Server service must be enabled
configured properly? and running on one of the server cluster
pairs.
Are there any strategies This check lists the strategies having
with references to references to parameters on the RM, FTEB,
parameters on the RM, and IOLIM blocks.
FTEB, FIM and IOLIM
blocks?
Are there any dangling Resolve such connections with the right
control connections? references.
Are there any Inactive Open the Control Builder and perform any of
strategies containing the operations before upgrade from the
Exchange blocks in this following options:
C200?
l Activate the strategies which are in
inactive state.
l Delete the strategies from the
Monitoring side.
l Reload the strategies
The following options are available if SIM and its strategies are loaded.
During the upgrade, SIM and its strategies containing SIM channels are
inactivated by default and strategies which have direct references to the
SIM Array channels are optionally inactivated. You must analyze the
impact of this on the process.
Are there any Serial This check lists the Serial Interface Modules
Interface Modules and and its corresponding strategies.
corresponding strategies
configured in this C200?
Are there any strategies This workaround is applicable only if you plan
with references to to upgrade SIM to PCDI.
parameters on Serial
Interface Module that Delete such references to the parameters
won't work after the from the Monitoring View and reload them
after the upgrade.
upgrade?
Are there any strategies This check will list strategies assigned to the YES
in this C200 initiating controller having peer communication to
peer connections to FIM2 present in the same local chassis.
FIM2 present in Local
Chassis?
Are there any strategies You need to upgrade this peer FIM2 to YES
in this C200 initiating FIM4/FIM8 and then perform load operation
peer connections to for these strategies.
FIM2 present in other
controller/Supervisory
Chassis?
Are there any strategies Delete such peer references from the Project YES
in other Controllers and Monitoring view of Control Builder.
initiating peer
connections to FIM2(s)
configured along with
this C200?
Are number of FIMs Ensure that the FIM2(s) are in the Tech and YES
within the Tech and Spec Spec Limits.
- 45 -

if
Limits?
Are there any Series A This check lists the Serial A Modules and its
Modules and corresponding strategies.
Are there any Series A This check lists the Serial A Modules which
Modules with Zero MAC are having Remote IO Chassis MAC Address
or duplicate slot as Zero and Modules with duplicate IOM Slot
address? Number.
C200?
Are there any IOLINKs This check lists the IOLINKs that has invalid
without valid I/O Link Link Number.
Number?
Is Peer Control Data If the system is not licensed to use PCDI,
Interface license ensure that you do not select the SIM to
available for all SIM PCDI conversion check box while running
being upgraded? the Transform Configuration tool. If you
select this check box, the C200 to C300
upgrade will be interrupted at a later stage.
Is C300 control solvers If you do not have enough licenses, procure
license available for all the same.
C200 being upgraded?
FIMs under QVCS. Lists all the FIM2s under the control of QVCS. YES
These FIM2 and QVCS details will be used
during FIM Consolidation in the Transform
Configuration tool.
Manual Is Serial Interface Serial devices connected to FTA with
Module is connected to Model\Part no 51191029 won't
Allen Bradley device communicate to PCDI Master.
using DF1 protocol or to
a device with TCP port
enabled?
Perform C200/C200E to C300 upgrade readiness checks
To perform C200/C200E to C300 upgrade readiness checks:

2. Click Start > Honeywell Experion Tools > All Honeywell Tools. Open the C200 Upgrade tool folder
4. Select C200/C200E to C300 Readiness Check from the Readiness Check Type list and click Next.
5. The General Data Collection screen appears with a list of configured chassis that is available in
the Experion cluster in the navigation pane on the left.
- 46 -
l L1 and L2 nodes (Server B or standalone server of local machine) are by default selected and
disabled.
l All Supervisory FIM2(s) in the Experion cluster are seen under a node SUPERVISORY_FIM.
The nodes, chassis, or modules are displayed on the left pane. Details of the selected node —
system configuration information of the chassis that contains slot number, module name,
module type, firmware version, are displayed on the right pane.
6. The Add Computer dialog box appears. Select the primary servers from other clusters, which have
exchange peer-to-peer communication with this controller, and then click Add. Based on this
selection, the readiness check populates the strategies containing the exchange peer-to-peer
communication. Click Cancel.
7. The Readiness Checks screen appears. From the navigation pane on the left, select the
server/nodes on which to run this check.
8. On the right pane, the list of checks appears. Select the check boxes next to each node to perform
tasks on the selected nodes or chassis.
- 47 -
9. By default, all controller readiness checks are selected but the server and Supervisory FIM2
readiness checks will not be applicable. Click Start to run all checks.
10. You can also choose to run one or multiple checks on a single server/node. In this case, select the
server/node from the left navigation pane and click the Run Checks button on the top in the right
pane.
11. The checks are run on the selected nodes and status for each check is displayed along with the
time stamp when it was run. The status can be one of these:
l Pass
l Warning
l Fail
l Not Applicable
l Not Executed
12. For checks that did not pass, click the hyperlink in the Status column to see a pop-up message with
detailed account of the problem in a tabular format. Additional Detail hyperlinks, when present, can
be clicked to get more information.
- 48 -
13. Click OK to close the message pop-ups.

14. Go to Control Builder and take appropriate action to remedy the cause mentioned by the readiness
Checks tool.
15. Click Run Checks again. If a checks fails, repeat steps 10 through 12 until all checks pass.
16. Click the Generate Report button on top to generate a report of the status of the checks you
performed on all/selected nodes.
You can save this report too. For more information about analyzing the reports, refer to the section
“Generating and analyzing the readiness check reports”.
- 49 -
If the controller is facing a COMM ERROR, some live data may not be available as part of readiness
checks.
If the C200 to C300 related WMI processes are not stopped properly, readiness checks do not appear.
2.4.6 Supervisory FIM2 readiness Checks

The following figure provides the details of the Supervisory readiness checks.
List of Supervisory FIM2 Readiness Checks
Supervisory FIM2 Readiness Checks

Readiness Description/work around
Checks
Blockers Is the Server Upgrade the servers to the FTE topology if they are not on the FTE
connected to topology.
Experion Process
Network via FTE?
Are there any If there are unsupported modules, disconnect the modules and
unsupported delete the modules and the strategies associated with those
modules/ modules. If there are modules with unsupported firmware versions,
firmware? upgrade the firmware compatible with the necessary Experion
release.
Are there any This check lists the strategies that have references to parameters on
strategies with the RM, FTEB and IOLIM blocks.
references to
parameters on the
RM, FTEB and
IOLIM blocks?
Are there any This check lists the strategies which are in checked-out state. If any
QVCS elements in strategies are found in the checked-out state, perform Check-in
checked-out before proceeding with the Upgrade.
state?
Warning Is the BOOTP The BOOTP Server service must be enabled and running on one of
Server configured the server cluster pairs.
properly?
- 50 -
Supervisory FIM2 Readiness Checks

List of FIM2(s), Provides the list of List of FIM2(s), Links, Devices and Strategies.
Links, Devices
and Strategies.
Are there any This check lists the strategies in other Controllers containing peer
strategies in other connections to the FIM2 been upgraded.
Controllers
initiating peer
connections to
FIM2 present in
the Chassis?
Are number of Ensure that the Supervisory FIM2(s) are in the Tech and Spec Limits.
Supervisory FIMs
within the Tech
and Spec Limits?
FIMs under QVCS. Lists all the FIM2s under the control of QVCS. These FIM2 and QVCS
details will be used during FIM Consolidation in the Transform
Configuration tool.
If the status of a readiness check is indicated as “Fail,” ensure to perform the work around and repeat
the readiness. If the status of a readiness check is indicated as “Warning,” you can perform the upgrade.
However, after upgrade you must resolve these warnings.
Since network upgrade and controller upgrade are separate activities, you can proceed with network
upgrade while there are blockers for controller upgrade. However, for a controller upgrade, completing
the network upgrade is a prerequisite.
You can proceed with the Controller upgrade if there are no blockers identified for that Controller
even if there are blockers identified for another Controller on the same network
Perform Supervisory FIM2 readiness checks
To perform supervisory FIM2 readiness checks:

1. Choose Start > All Programs > Honeywell Experion PKS > Engineering Tools > C200 Upgrade
Tool, and then right-click Server and Controller Upgrade Readiness Checks Tool.
2. The Provide User credentials dialog box appears. Type the Password and click OK.
3. The Server and Controller Upgrade Readiness Checks screen appears. Select Supervisory FIM2
Readiness Check from the Readiness Check Type list.
all the configured FIM2(s).
with this cluster and then click OK. The Readiness Checks screen appears.
- 51 -
7. Select the SUPERVISORY_FIM node. All the nodes are selected by default.
node/module. By default, the servers and chassis readiness checks are not performed and the
status for server and chassis are Not Executed.
status of the readiness checks for each node is displayed in the node tree. You can select a node
in the Navigation pane to view the status of the individual readiness checks in the data pane.
10. Click the hyperlink provided for each readiness check in the Status column. The server readiness
check starts and the status of each readiness check is displayed in the data pane.
2.4.7 Generating and analyzing readiness check reports

You can generate a report for the readiness checks performed. To generate a report, click Generate
Report on the readiness check screen. The readiness check report is used for analyzing the execution
status of the readiness checks with the details. Sample reports for Server readiness check and
Controller readiness check are illustrated. The following table describes the status for readiness
checks.
For example, consider that a peer connection exists between two CMs that are assigned to different
controllers. In this case, if you delete one of the CMs from which a peer connection has been made to
another CM, then the strategy is displayed under “Are there any dangling control connections?”
However, if the controller to which the strategy is loaded is deleted from the Monitoring view, then the
strategy is displayed under “Are there any dangling peer connections?”
Status of each readiness check
- 52 -
Status Description Guideline

Pass Indicates that the No action required.
readiness check has
passed.
Fail Indicates that the Perform the recommended work around and repeat the readiness
readiness check has check.
failed.
Aborted Indicates that the Perform the recommended workaround and repeat the check.
readiness check could
not be completed due
to some issues.
Warning Indicates that the Although warnings are not blockers for upgrade, click Details to
readiness check has analyze the problem and perform the work around. However, if
passed with warnings. you proceed with the upgrade without addressing the warnings,
you have to address the same after the upgrade is complete.
Manual Indicates that the
readiness checks have
to be manually
performed before the
upgrade.
The reports are in HTML format and can be opened using a web browser preferably, Internet Explorer.
Sample reports
- 53 -
Item Description
1 Warning
2 Warning
3 Click to view instructions for upgrading C200/C200E to C300 controllers.
2.5 Upgrade the Experion Process Network from CNET to

FTE

Before upgrading C200/C200E modules to C300 modules, the Experion Process Network (EPN) of the
Experion system must have Fault Tolerant Ethernet (FTE) network. If the EPN of the Experion system
has ControlNet (CNET) network, then the CNET to FTE Upgrade is a prerequisite to the C200 to C300
Upgrade.
After the CNET to FTE upgrade, the Experion Process Network that is Server to Controller
communication is changed from CNET to FTE. The C200 Controllers still continue to use CNET at the
I/O network level. In order to execute the CNET to FTE Upgrade, your Experion System supervisory
network must have FTE network.
For more information, refer to the Experion Network Best Practices guide. This activity involves the
following high-level tasks:
l “Adding the FTEB module to the controller chassis”
l “Taking a backup of ERDB”
l “Upgrading the Experion Process Network to FTE”
Log in to the Experion server with the least privilege as Local Engineer.
2.5.1 CNET to FTE upgrade screen

Following is the illustration of CNET to FTE upgrade screen.
CNET to FTE upgrade
The CNET to FTE screen consists of the following:
- 54 -
Task/Stage Description
Add FTEB Modules to Upgrade the Server A from CNET to FTE.
controller chassis
Backup ERDB Take a backup of ERDB using DBAdmin tool.
Upgrade server network The Experion server is upgraded from CNET to FTE network. During this
to FTE upgrade, System Repository and Experion Services (CDA and SAM) are
restarted.
An User Account Control appears when performing Network type change
(from CNET to FTE) and services restart. Please provide Administrator
credentials and click Yes.
Update ERDB system Provide the Base IP address, Subnet mask, Default gateway, Primary NTP
preferences Server, and Secondary NTP Server details.
This step not applicable from release R511.2 onwards.
Update Module Version Select the version (major or minor) and provide the mandatory comment.
This is specific to modules that are under the control of QVCS.
This task is visible only when any of the following modules are under the
control of QVCS: C200/C200E, IOLIM, RM and FIM.
Refer QVCS Details for the QVCS updates during upgrade process.
Configure FTEB Provide the FTEB name, Device Index, and slot number of FTEB. FTEB
modules and upgrade nodes in database are created and all C200/ C200E are assigned to that
controllers to FTE FTEB.
Connect Server B to At this stage, the following steps must be performed manually.
network
Connect Server B to network.
Command server synchronization from Server A.
Command failover from Server A.

Power off Server A.
Upgrade Server A from Ensure that you have upgraded Server A from CNET to FTE.
CNET to FTE
Status: Displays the status of each CNET to FTE upgrade step as follows:
l Not Executed
l In Progress
l Executed
l Failed
2.5.2 Adding the FTEB module to the controller chassis

Plan and execute this task ahead of your network upgrade activities. In addition, note that the FTEB
modules must be added in all the peer controller chassis across the cluster.
Ensure that C200/C200E and FTEB module are in the same firmware version.
Prerequisites
BootP service must be stopped and disabled on Server B and started and enabled in Server A before
adding the FTEB in the chassis.
- 55 -
Stop BOOTP service on Server B and start it on Server A
1. If multiple BootP services are running, navigate to: C:\Program Files (x86)\Honeywell\Experion
PKS\C200toC300UpgradeTool.
2. For custom installation path, navigate to: <user selected path>\Honeywell\Experion
3. Right-click Bootp_Stop_batch.cmd, and click Run As Administrator. The BOOTP service dialog
box appears. Follow on-screen instructions.
Or
4. Type services.msc in the Run dialog box. The Services dialog box appears.
Update ERDB system preferences
1. To set the base IP address, go to: C:\ Program Files (X86)\Honeywell\Experion

2. For custom installation path, navigate to <user selected path>\Honeywell\Experion
3. Right-click UpdateBaseIP_SubnetMask_Batch.cmd, with Local Engineer or Product Administrator
permissions.
4. Enter the Base IP Address and Subnet Mask Address. A confirmation message appears.
5. Click Yes. A message indicating success appears. The Base IP Address and Subnet mask are
updated in ERDB.
6. Start BOOTP service.
In addition, run the BOOTP checker tool after updating the system preferences to verify if there is only 1
BOOTP Server detected in the network.
To run this on Server A and to ensure BOOTP service is running, perform this before adding the FTEBs
in the chassis so that the FTEB gets the correct IP based on the system preferences base IP and the
device index is given to the FTEB.
Start BOOTP service on Server B and start it on Server A
1. Navigate to: C:\Program Files (x86)\Honeywell\Experion PKS\C200toC300UpgradeTool.

2. For custom installation path, navigate to: <user selected path>\Honeywell\Experion
3. Right-click BootP_Start_Batch.cmd, and click Run As Administrator. The BOOTP service dialog
Or
4. Type services.msc in the Run dialog box. The Services dialog box appears.
Add FTEB module to the redundant controller chassis
1. In the Control Builder Monitoring view, double-click the RM.

2. Click the Summary tab.
3. Click Disqualify Secondary. The synchronization of the primary and secondary chassis is disabled.
4. Power-off the secondary chassis.
- 56 -
5. Insert the FTEB module with odd Device Index using the following steps:
a. Align the module's circuit board with the top and bottom chassis guides for the available slot
location. Remember that slot numbering is zero-based and the left most slot is number "0".
b. Slide the module into the chassis, until the module's locking tabs "click" into position. The
module is fully installed when it is filled with the power supply or other installed modules.
c. Insert the FTE cables properly into the FTEB module, to pick up the base IP from the Server A.
Note down the FTEB slot number for further use during upgrade.
6. Click Enable Synchronization to initiate synchronization and allow auto-synchronization. The
synchronization of primary and secondary chassis is enabled.
7. Power on the secondary chassis.
8. In the Control Builder Monitoring view, double-click Redundancy Module > Synchronization >
Synchronize Secondary and then click OK.
9. In the Control Builder Monitoring view, click Initiate Switchover after the C200 chassis is
synchronized.
10. Power off the new secondary chassis.
11. Click Disqualify Secondary. The synchronization of primary and secondary chassis is disabled.
12. Insert the FTEB module with even Device Index using the following steps:
location. Remember that slot numbering is zero-based and the left most slot is number "0."
13. Power on the new secondary chassis. Verify that the primary chassis has odd Device Index and
secondary chassis has even Device Index.
14. Click Enable Synchronization to initiate synchronization and allow auto-synchronization.
The synchronization of primary and secondary chassis is enabled. Confirm that the Auto
Synchronization State becomes ENABLED.
Add FTEB module to a chassis that does not have an empty slot
If an empty slot for adding the FTEB module is not available:

1. Disable the synchronization of primary and secondary chassis.
2. Power off the secondary chassis.
3. Remove the modules from the chassis.
4. Remove the secondary chassis.
5. Add the new chassis, which has more slots.
6. Mount the modules in the chassis.
8. Enable the synchronization between the primary and secondary chassis.
9. Switch-over the control to secondary chassis.
10. Perform the steps listed in “"Add FTEB module to the redundant controller chassis" on the previous
page”. Refer "Add FTEB module to the redundant controller chassis" on the previous page.
2.5.3 Taking a backup of ERDB

Before you upgrade the network, take a backup of the ERDB. This helps in reverting to CNET in case of
any issues during the network upgrade.
- 57 -
2. Select a listed system and click Connect.
Strategies section.
8. Expand the Server Node item and click ERDB Admin Tasks.
9. Click Backup Database. The Select and/or Create a folder to store backup set dialog box
appears.
Create the folder C:\temp and store the backup of ERDB.
10. Click Select. A confirmation dialog box appears.
11. Click OK and acknowledge the message indicating success.
2.5.4 Upgrading the Experion Process Network to FTE

This procedure provides steps upgrade the server nodes connected to L1 controllers and IOLIMs
through ControlNet to the FTE network.
Prerequisites
l Before executing the tool, log on using local administrator privileges. This account must exist on
Server A and Server B and configured to have the same privileges.
l Power off Server B and then remove PCI Express host card from Server B.
l Remove FTE cables from Server B and then power On Server B. Ensure Server B is the primary
server before running the CNET to FTE upgrade tool.
l C200/C200E must be running with the firmware of the latest release or at least of a release
compatible with the release interoperability rules for the system version.
l Server A is the primary server.
l Stations and ACE nodes are connected to the Server on Level 2 FTE (on-line upgrade from dual
Ethernet excluded).
l Level 1 FTE cabling and switching are complete.
l CNET to FTE readiness checks are completed.
l Ensure that you upgrade Server B to FTE first before upgrading Server A to FTE.
l Ensure that Control Builder is closed.
Before starting the CNET to FTE Upgrade tool, Server B must be disconnected from the CNET and FTE
network and its status should show Primary before launching and running the CNET to FTE upgrade
tool. (Disconnect the FTE cables and the CNET cables and verify the Server status with the Start/Stop
Experion application. Additionally, since the Server B is disconnected from the network, Server B
cannot see any other nodes on the network and its status appears as Primary (only after confirmation
that the CNET to FTE upgrade tool can be launched).
- 58 -
To upgrade the Server B Experion Process Network to FTE
tool, and then right-click CNET to FTE Upgrade > Run as administrator. The Provide User
Credentials dialog box appears
You should run the tool with administrator privileges to avoid failure issues. The user account
must exist on Server A and Server B with the same privileges.
2. Type the Password and click OK. The CNET to FTE Upgrade screen appears.
3. Confirm that the FTEB modules are added to all the required controller chassis and the controllers
are synced
4. Click Proceed. The Upgrade Server B Process Network to FTE task is automatically selected.
5. Click Proceed. A message indicating that system needs to be updated for FTE network type and
service is restarted.
6. Click Yes. The tool updates the registry and restarts the SR, CDA SAM services. If the registry
update fails, change the network type from RSLinx to FTE in the following path — HKEY_local_
Machine > Software > Wow6432node > Honeywell > TPS50 > InstallInfo > Networktype. You
need to update the registry and restart the CDA and SAM services manually.
The Upgrade Server B Process Network To FTE task may appear as “Failed.”. However, you
can continue with the upgrade once the network type is changed from RSLinx to FTE
manually. The Update ERDB System Preference task is automatically selected
7. Select the Task Completed check box and click Proceed.
Configure FTEB modules and upgrade the controllers
1. Enter the name of the FTEB module in the New FTEB Name box.
2. Enter the Device Index of the FTEB module in the Device Index box.
3. Enter the slot number in which the FTEB module is inserted in the Slot Number box.
4. Click Proceed. A message appears indicating that FTEB modules are created and the controller
configuration is updated with new FTEB modules.
5. Click Yes. The Connect Server B to FTE Network option is automatically selected.
Connect Server B to FTE network
1. Follow on-screen instructions. After these tasks are completed successfully, you cannot return to
the CNET topology.
2. Select the Task Completed check box, and click Proceed. The Upgrade Server A Process Network
to FTE option is selected.
To upgrade the Server A Experion Process Network to FTE
1. Remove PCI Express host card and power on Server A.

2. Ensure FTE cables are disconnected before powering on Server A.
3. Run the UpdateServertoFTE batch file from C:\Program Files\ Honeywell\Experion\
C200toC300UpgradeTool on Server A.
4. Power-off Server A.
It is recommended to follow the right sequence before the Server A is powered on after the
upgrade from CNET to FTE upgrade tool is executed and then the Server A must be powered
off. The network cables must be connected to the Server A when Server A is powered off and
Server A must be powered on only after the network cables are connected. If the network
cables are connected after the Server A is powered on Server A becomes the preferred
Primary and the upgrade fails.
- 59 -
5. Connect the network cables, and then power on Server A.

6. Open Configuration studio from Server B and click Administer the control strategy database. The
DBAdmin tool appears.
7. Click Recover Secondary Database. The Recover Secondary Database dialog box appears.
8. Click Yes.
9. Re-enable the ERDB synchronization.
10. Synchronize the servers by performing the following procedure.
a. Log on to the Station running on Server B with Manager (mngr) privileges.
b. Choose Configure > System Hardware > Redundant Server.
c. Click the Status tab.
d. Click Synchronize.
e. In the Message Zone, click Yes to synchronize Server A with the database on Server B.
After upgrading CNET to FTE, DO NOT remove the CNI card from the C200/C200E chassis
as peer-to-peer communication to other controllers is still through CNI cards, that is, until the
C200/C200E Controller is upgraded to C300 Controller. Wait for the server synchronization
to complete.
11. Select the Task Completed check box, and then click Proceed.
Results
Server A and Server B are connected to L1 nodes through FTE.
2.6 Transform Configuration (C200/C200E to C300, FIM2 to

FIM4/FIM8)
2.6.1 Transform option and backup ERDB 61
2.6.2 Transform C200/C200E configuration to C300 configuration 61

2.6.3 Transform Supervisory FIM2 configuration to FIM4/FIM8 configuration 72
The transformation activity involves the following tasks:
1. Taking a backup of the ERDB.
2. Assigning a Device Index to C300.
3. Modifying any Exchange block communication paths.
4. Configuring SIM to PCDI.
This task should be performed only if SIM and its strategies are loaded and also if you would
want to perform SIM to PCDI Conversion.
5. Configuring Series A Modules to FTEB
This task should be performed only if Series A is available
6. Configuring FIM2 to FIM4/FIM8.
This task should be performed only if FIM2 is available. All these tasks must be performed in
the sequence mentioned
7. Transforming the C200/C200E configuration to C300 or FIM2 configuration to FIM4/FIM8.
All these tasks must be performed in the sequence mentioned.

Log in to the Experion server with the least privilege as Local Engineer
- 60 -
2.6.1 Transform option and backup ERDB

Before you upgrade the controller, take a backup of the ERDB. This helps in reverting to C200/C200E in
case of any issues during the controller upgrade.
To take a backup of the ERDB, refer to the section “"Taking a backup of ERDB" on page 167”.
The Transform Option and Backup ERDB page has the following Transform Configuration types.
l C200 to C300 – This Transform type option is chosen if the chassis has the following:
o Controller configured with PMIO and Series A only – This will lead to a Live Upgrade using
the C200 Upgrade tool.
o Controller with FIM2 – This will lead to an Off-Process upgrade using the C200 Upgrade
tool.
l Supervisory FIM2 to FIM4/FIM8 – This transform type is chosen if chassis has only FIM2 configured.
This option will lead to the Off-Process upgrade using C200 Upgrade tool.
2.6.2 Transform C200/C200E configuration to C300 configuration

This operation converts/changes C200/C200E strategies to C300. During this operation, the
C200/C200E strategies are locked and a shadow of the strategy configuration is created in C300.
If FIM2 are configured along with C200/C200E, then its related FF devices and strategies are locked
and a shadow of the configuration is created in consolidated FIM4/FIM8.
However, if you want to revert the shadow configuration, click Transform Cancel.
Prerequisites
Ensure that you have completed the C200/C200E to C300 readiness checks.
- 61 -
To transform the C200/C200E configuration to C300 configuration
1. Launch the tool (Click Start > Honeywell Experion Tools > All Honeywell Tools. Open the C200
Upgrade tool folder and double-click C200 Upgrade Tool Transform Configuration).
2. The Login Information dialog box appears. Provide User Name and Password.
3. Select Server Name, Domain Name, and click OK. The Transform Option and Backup ERDB
screen appears.
4. Backup ERDB using DBAdmin Tool now. See “"Transform option and backup ERDB" on the
previous page”. Click the Task Completed checkbox.
5. Select C200 to C300 as the Transform Option.
6. Click Next. The C200 Controller screen appears.
7. Missed readiness checks, if any, or skipped readiness check-related errors are displayed.
8. Select the C200 tag name from the drop-down list.
- 62 -
9. The IOLINK1 and IOLINK2 details are displayed. If IOLIMs are not configured, the IOLINK1 and
IOLINK2 fields appear blank. To interchange IOLINK1 and IOLINK2 connections, click Swap.
Ensure that you record the IOLINK connections, as you will be using the same details while
performing the controller hardware upgrade.
10. Type the unique, odd C300 Device Index with a value less than or equal to 509, and click Next. orIf
you want to use the C200 FTEB Index for C300, type the same here.
11. The C300 Exchange Block Path Update screen appears only if Exchange block is configured. The
Transform Type, Controller Name and Description is displayed.
12. Depending on the C200 Tag Name selected, the Description changes as follows:
l If C200/C200E configured with FIM2 is selected in the chassis, description is “Upgrade
process is Off-Process”.
l If only C200/C200E is selected, description is “Upgrade process is Live if no COMM ERROR”.
l If C200/C200E is transformed using the same FTEB Device Index, then the upgrade is
considered as Off-Process.
13. Observe that the Exchange Block Path and the Current Value of Exchange block are displayed
automatically.
- 63 -
14. You can enter the new Exchange block path in New Value. Or
a. Perform the following steps to configure the data.
l Click Export to write to a csv file. Save the .csv file.
l Open this .csv file with an editor such as Notepad and update the file with new values
and save the file. The location of the .csv file appears in the bottom of the screen.
l Click Import to read the updated .csv file and copy them to the New Value fields.
15. Click Next. In this page, all the SIMs available in C200 controller appear.
The Serial Interface Module to PCDI address update page appears only if SIM and its
strategies are configured.
16. Only if you want to perform SIM to PCDI conversion select the Convert Serial Interface Module to
PCDI address update checkbox and enter the following configuration details or jump to the next
step:
- 64 -
a. FTA Model – Select from one of the following FTA models

l MC-TSIM12 (Modbus Master)
l MU-TSIM12 (Modbus Master)
l MC-TSIM13 (Modbus Master)
l MU-TSIM13 (Modbus Master)
l MC-TSIA12 (AB DF1 Master)
l MU-TSIA12 (AB DF1 Master)
l 51191029 (Modbus Slave)
b. PCDI Master – A default PCDI name is provided. The naming convention is as follows:
l If both FTA-A and FTA-B are used, then two PCDIMASTERs are created and the name is
<SIMNAME>-A and <SIMNAME>-B.
l If only FTA-A or FTA-B is used, then the PCDI Master remains the same as the SIM
name.
c. Device Type – Select from one of the following device types:

l Single MODBUS TCP Device
l Redundant MODBUS TCP Device
l Single MODBUS TCP Bridge
l Redundant MODBUS TCP Bridge
d. Primary IP - Enter the IP address for the primary or non-redundant device.

e. Secondary IP - If you have selected a single (non-redundant) device type, you can skip this
step. If not, enter the IP address for the redundant device.
17. Click Next. The Series A Module Summary screen appears only if Series A modules are
configured.
18. Click the Assign Series A button to assign Series A modules to FTEB.
- 65 -
19. The Series A Assignment screen appears. Under Chassis and FTEB provide the following details:
l Select Chassis Type.
l FTEB Details
l Type FTEB Name
l Type Device Index
l Select Slot No
l Type Asset Name
20. Click the Create Chassis/FTEB Node button. Acknowledge the success message. The FTEB is
added to the List of FTEB and its I/Os list on the right.
- 66 -
21. Expand the remote IO chassis on the left pane to view all the I/Os. Right click the MAC address
(MACADDR) and click Assign all IOs to FTEB to assign all I/Os. You can also select individual I/Os
and assign them to FTEB.
If you are planning to assign MACADDR node to FTEB, the slots of Series A remote chassis
and FTEB chassis must match. When you are planning to assign individual Series A IOs,
available free slots per FTEB are listed. You can choose the slot and assign individual Series
A IOs.
22. The FTEB name appears under Assign Remote Chassis to FTEB. Select the FTEB and click
Assign.
23. Acknowledge the message indicating success.
- 67 -
24. Repeat the previous two steps to assign remaining modules per your requirement. Note that it is
not mandatory to assign all modules.
25. Click the OK button on the bottom right of the screen.
26. Click Next. The FIM2 Summary and Consolidation screen appears.
If FIM2 is under the control of QVCS, refer FIMs under QVCS details in Readiness Check
report. This will help in consolidation of FIM2 to FIM4/FIM8 based on the QVCS configuration.
These details can only be seen if FIM2 Module is configured and loaded.
In this page, all the FIM2(s) available in C200 Controller chassis appear:
27. To move FF devices assigned to FIM2 under FIM4/FIM8, click Consolidate. FIM2 to FIM4/FIM8
Consolidation screen appears.
- 68 -
28. You can consolidate FF devices of two FIM2s to one FIM4 or FF devices of four FIM2s to one FIM8.
29. You can create FIM4/FIM8 by providing details under Create FIM4 or FIM8 and click the Create
FIM4/FIM8 node button. The newly created FIM4/FIM8 appears in the List of FIM4/FIM8.
Details to create FIM4/FIM8:
l Select FIM type – Select FIM4 or FIM 8 respectively.
l FIM name – Enter the FIM name.
l Device Index – Enter the odd number device index.
l Asset name – Enter the asset name that exists.
- 69 -
30. To consolidate FF devices of FIM2 to FIM4/FIM8, right click on the FIM2 name (in the left pane) and
select Assign to FIM4/FIM8.
31. Under Assign to existing FIM4/FIM8 (in the middle pane), select the FIM4 or FIM8 you want to
assign to. Click Assign.
32. A confirmation message appears mentioning that the FIM2 is assigned. This ensures the FIM2 links
are assigned to FIM4/FIM8.
Until all FIM2 are not assigned, transform operation cannot be done.
Unassigned FIM4/FIM8 will not be considered for transform operation.
33. Click OK.
- 70 -
34. You will return to the FIM2 Summary and Consolidation page. Click Transform.
Wait for the transform configuration to complete. The strategy transformation takes time
depending on the database size of C200/C200E Controller and FIM2. After a shadow
configuration of C200/C200E and FIM2 is created on Project view, a successful message
appears.
In case you want to cancel the shadow configuration of C200/C200E and FIM2 created on
Project view, you can click Transform Cancel.
If any data validation errors appear, the Status bar displays an error message.
35. Click the Generate Report button to generate a report. You can save the report too.
36. Click the Close button to close the tool.
- 71 -
2.6.3 Transform Supervisory FIM2 configuration to FIM4/FIM8

configuration
This operation converts/changes FIM2 modules to FIM4/FIM8. During this operation, the FIM2 strategies
are locked and a shadow of the strategy configuration is created in FIM4/FIM8. However, if you want to
revert the shadow configuration, click Transform cancel.
This Transform configuration option is used when Chassis contains only FIM2 module.
Prerequisites
Ensure that you have completed the readiness checks.
To transform the Supervisory FIM2 configuration to FIM4/FIM8 configuration
tool > C200 Upgrade Tool Transform Configuration. The Provide User credentials dialog box
appears.
2. Type the Password. Click OK. The Transform Option and Backup ERDB screen appears. Refer
“"Transform option and backup ERDB" on page 61”.
3. Select the Supervisory FIM2 to FIM4/FIM8 from the Transform option list.
4. Take a backup of the ERDB using the DBAdmin tool.
5. Select the Task Completed check box, and then click Next. The FIM2 Summary and Consolidation
page appears. All the Supervisory FTEB and its FIM2s are seen in the List of FIM2s.
6. If FIM2 is under the control of QVCS, refer FIMs under QVCS details in Readiness Check report.
This will help in consolidation of FIM2 to FIM4/FIM8 based on the QVCS configuration.
7. You can create FIM4/FIM8 by providing details in “Create FIM4/FIM8” and click the Create
FIM4/FIM8 node button. The newly created FIM4/FIM8 appears in the List of FIM4/FIM8.
Details to create FIM4/FIM8:
l Select FIM type – Select FIM4 or FIM 8 respectively.
l FIM name – Enter the FIM name.
l Device Index – Enter the odd number device index.
l Asset name – Enter the asset name that exists.
8. You can consolidate FF devices of two FIM2s to one FIM4 or FF devices of four FIM2s to one FIM8.
To do this, on the left pane, expand the FTEB name, right click the FIM2 name and select Assign to
FIM4/FIM8.
9. Under Assign to existing FIM4/FIM8 (in the middle pane), select the FIM4 or FIM8 you want to
assign to. Click Assign.
10. A confirmation message appears mentioning that the FIM2 is assigned. This ensures the FIM2 links
are assigned to FIM4/FIM8.
11. Click OK.
12. You will return to the FIM2 Summary and Consolidation page. Click Transform.
13. Wait for the transform configuration to complete. The strategy transformation takes time depending
on the database size of Supervisory FIM2s. After a shadow configuration of FIM4/FIM8 is created
in Project view, a message indicating success appears.
14. If you want to cancel the shadow configuration of Supervisory FIM2s created in Project view, click
Transform Cancel.
- 72 -
If any data validation errors appear, the Status bar displays an error message.
15. After a successful transform, you can click Generate Report to view the Transform Configuration
Summary Report.
16. Click Close.
2.6.4 Transform configuration summary report

Title Description
Controller Provides the controller information that is, the controller name, the controller type,
Information and the device index.
Exchange Block Provides the details of the exchange block path before (Old Path) and after (New
Path) the transform configuration.
Serial Interface Provides the details of SIM to PCDI conversion.
Module – PCDI
Master
Channel Block Provides the details of the channel number of SIM mapped to the PCDI Master.
Assignment
Channel Block Provides the details of the block addresses of SIM mapped to the PCDI.
Address
Mapping
Address that Provides the details of the addresses that cannot be mapped to PCDI. Refer to the
cannot be Peer Control Data Interface Implementation Guide for more information.
mapped
Device Index Provides the information that the respective PCDI block device address is set to 1
not in PCDI by default if the Serial block DEVADDR is not in the PCDI range (1-247 or255). You
Range need to ensure to update the UNIT ID of the PCDI master and load it after the
upgrade.
PCDI Master Provides the details of the PCDI master and its slave configuration that are
Slave updated during the transform configuration.
Configuration
Series-A IO or Provides details of the Series-A I/Os or Interface Modules assigned to FTEB.
Interface
Module
assigned to
FTEB
C300 IOU Provides details of C300 IOU.
Series A Module Provides details of module count of Serial Interface, SST Profibus and DeviceNet
Count Modules per C300 and FTEB.
FIM2 to Provides information of the FIM2s consolidated to FIM4/FIM8.
FIM4/FIM8
consolidation
details
For Supervisory FIM2 option, only FIM2 to FIM4/FIM8 consolidation details will be seen in the report.
2.7 Upgrade C200/C200E to C300 (Live/Off-Process)
2.7.1 Live upgrade 74
2.7.2 Off-Process Upgrade 87
- 73 -
C200 to C300 Upgrade employs checkpoint restore and warm start. This work flow causes all function
blocks to behave like a regular controller Warm start. Assess the impact of this warm start behavior on
your process.
Whether the upgrade process is live or will be considered Off-Process depends on the conditions
explained in the following table.
Hardware Supported only under these conditions

Live C200/C200E with l C200/C200E is redundant and is live (appears in green
in Monitoring view)
l PM I/O modules
l RM
l IOLIM
l FTEB
l SIM with
Serial/PLC devices
l Series A
Off- C200/C200E with l That user chose to perform off-process
Process
l PM I/O modules l That is facing a COMM ERROR (communication error)
l RM l That uses the C200/C200E FTEB Device index
l IOLIM l If C200/C200E is configured with FIM
l FTEB
l SIM with
Serial/PLC devices
l Series A
l FIM2
Supervisory FIM l Configured
l That is facing a COMM ERROR
2.7.1 Live upgrade

This operation upgrades C200/C200E Controller along with strategies to C300 for a live controller.
Prerequisites
l C200/C200E to C300 readiness checks have been completed.
l C200/C200E Transform configuration has been completed.
Stages of the Live upgrade
The C200/C200E to C300 live upgrade proceeds in the following stages.
- 74 -
Check Indicates whether there are any blockers for C200/C200E upgrade.
C200/C200E
upgrade blocker
Transform At this stage, you need to confirm if you have completed the Transform
configuration Configuration tasks.
confirmation
Prepare controller At this stage, the following steps must be performed manually.
hardware for
Upgrade the Control Firewall firmware.
upgrade
Prepare the controller hardware for C200/C200E to C300 upgrade.
Update the FTEB firmware if Series A to FTEB assignment is performed in

Transform Configuration.
C200/C200E to Displays a list of strategies in other controller that are initiating exchange peer-
C300 upgrade to-peer connection and peer-to-peer connection with this controller. In
notification addition, you are notified with disruption of history collection.
Strategies in QVCS affected during the upgrade are available in the report
format.
If a controller is facing a COMM ERROR, all notifications received from a live
controller may not be available.
From this step, there is a Loss Of View (LOV) from the Server and the Flex
Station to the controller being upgraded and the operations to the upgrading
controller are limited to the Console Station until the upgrade to C300
completes.
Load firmware to Loads the Experion R5xx firmware to the C300 Controller. The C200 Upgrade
C300 Controller tool performs this task.
Inactivate Series A Lists Series A and its related strategy present in the selected C200 Controller.
IO/Interface
Module(s) and This operation is available only if Series A IO /Interface Module(s) and its
Strategy(s) strategies are loaded.
Rebuild Checkpoint Creates and saves C200/C200E Checkpoint.

of C200/ C200E
Controller
Prepare controller Perform the following tasks:
configuration for
upgrade Finalize the transformed configuration
Load FTEBs
Create the checkpoint for C300.
Transfer control Perform the following tasks:
from C200/ C200E
to C300 Save C200/C200E Checkpoint.
Restore Checkpoint to the secondary C300.
Transfer control from C200/C200E to C300.
Restore peer-to-peer and Exchange block connections.
Upgrade chassis A At this stage, the following steps must be performed manually.
to C300
Connect the IOLINK cables from chassis A to the secondary C300.
Power on the secondary C300.
Experion R5xx firmware is loaded to the powered on secondary C300.
Status: Displays the status of each C200/C200E to C300 upgrade step as follows:
- 75 -
l Not Executed
l In Progress
l Completed
l Failed
Perform Live Upgrade
Prerequisites
l The server is connected to Level 1 controllers and IOLIM by FTE.

l The Console Station is connected to maintain a view during upgrade.
l Transform configuration for C200/C200E to C300 is complete.
l Controller hardware upgrade is complete.
l C200/C200E is running on interoperability release.
l Control Builder is closed.
Although the loading of C300 firmware is automatically taken care of in the background, you must verify
the same in CTools before proceeding further.
and double-click C200 Upgrade Tool to launch the tool. The Provide User Credentials dialog box
appears.
2. Type the Password and click OK. The General Data Collection screen appears.
3. Select the module from the left pane and click Next.
4. The Upgrade Type Selection screen appears. Select the Upgrade Type and click OK:
a. Live: If your C200 controller is live. For a detailed list of conditions when upgrade is live, see
the section, "Scope and limitations" on page 138.
b. Off-Process: For a detailed list of conditions when upgrade is off-process, see the section,
"Scope and limitations" on page 138.
- 76 -
5. Only in case of a blocker issue, the C200 Upgrade Blocker screen appears with the relevant
blockers. Resolve the blockers and repeat from step 1.
6. Click Proceed if no upgrade blockers are detected.
7. The Transform Configuration Confirmation screen appears. Ensure that ERDB is backed up using
DBAdmin Tool and C200 configuration transformation is completed using the C200 to C300
Transform Configuration tool. Check the Task Completed option and click Proceed.
- 77 -
8. The Prepare Controller Hardware for Upgrade screen appears. At this stage, you must upgrade
controller hardware by following instructions provided in the section, "Prepare Controller Hardware
for Upgrade" on page 175 .
Ensure that only the controller with even device index is powered on and the controller with odd
device index remains powered off.
Proceeding with the remaining steps in this procedure only after you upgrade controller
hardware by following instructions provided in, Prepare Controller Hardware for Upgrade.
Before upgrading the C200/C200E to C300, ensure that auto Checkpoint Save operations are
stopped.
Control Recipe must not be running during C200/C200E to C300 upgrade. If Control
Recipe is running, Control Recipe related activities are removed from Activities Summary
page.
After upgrading the C200/C200E to C300, C200/C200E CEE related parameters in
custom displays are lost
After upgrading to C300, the following parameters configured in the C200/C200E CEE are
moved to C300 CEE.
l DAYLIGHTTIME
l TIMEZONE
l WEEKDAYFMT
l YEARFMT
Insert FTEB modules for the Series A chassis and connect to CF9.
Ensure you upgrade the FTEB firmware using Ntools. See the Fault Tolerant Ethernet Bridge
Implementation guide to launch Ntools and flash the FTEB firmware.
9. After completing the hardware upgrade tasks, return to this screen, click the Task Completed check
box and click Proceed.
- 78 -
10. The C200 to C300 Upgrade Notification screen appears. Click Proceed.
On the right pane, the following details are displayed. For example:
l List of strategies in other controllers that are initiating Exchange peer-to-peer connections with
this controller.
l List of strategies in other controllers that are initiating peer-to-peer connections with this
controller.
l Notification of the Upgrade type is mentioned.
l Option to Export the report of strategies under QVCS affected during upgrade.
11. Read the instructions on the right pane and then click Proceed.
12. The Load Firmware to C300 Controller screen appears. C200 Upgrade tool does not automatically
upgrade the CF9 firmware. Hence, you must upgrade to the latest CF9 firmware.
13. Click Load Firmware.
- 79 -
14. At this stage, you must open Ctool and ensure C300 has been flashed with the latest firmware and
is powered on. See "Upgrade the CF9 module firmware" on page 114.
15. After you have ensured C300 is running the latest firmware, select the Task Completed checkbox
and click Proceed.
- 80 -
16. The Inactivate Series A IO/Interface Module(s) and its Strategy(s) screen appears. A list of
assigned/loaded Series A and its related strategies is displayed. Note that strategies containing
Series A block/channel parameters are by default selected.
The Inactivate Serial Interface Module(s) and its Strategy(s) task is selected if Series A and its
strategies are loaded.
17. Click Export to save the list of Series A I/Os that will be inactivated.
18. Click Inactivate. After the task is completed, the status on the left pane shows Executed. If the
Inactivation fails, the list of failed inactivation strategies is listed. You must manually inactivate the
strategies and click Task Completed to proceed. Click Proceed.
- 81 -
19. The Rebuild Checkpoint of C200 Controller screen appears. Click Proceed.
20. After the checkpoint of C200 controller is rebuilt, the Prepare Controller Configuration for Upgrade
screen appears. Follow instructions given on the screen and check the I’m aware of impact and
want to proceed option and click Proceed.
- 82 -
The following operations are performed in this step:

l C300 configuration is finalized.
l QVCS configuration is updated. See QVCS Details.
l FTEB modules inserted in Series A chassis are loaded.
l A Checkpoint of C300 controller is created.
In case of issues in loading FTEBs, a message is shown prompting you to acknowledge that
you will load FTEBs post upgrade. Acknowledge this message and click Proceed.
Trends view is lost if the historization parameters are configured in the Console Station.
However, the values are displayed in the Legend. To avoid the loss of Trends view, isolate the
Console Station from the server. Perform the section “Isolating the Console Station from the
server” only if you want to view the Trend Plot in the Console Station during the upgrade as the
Current Value always appears even if the Trend Plot is not shown.
21. The Transfer Control from C200 to C300 screen appears. Click Proceed.
- 83 -
The following operations are performed as part of the Transfer control from C200 to C300 task.
l Checkpoint Save operation for the C200/C200E Controller.
l Checkpoint Restore operation on the secondary C300.
l Control is transferred from C200/C200E to C300.
l Peer-to-peer connections and Exchange block connections are restored. The following dialog
box appears
By default, Continue with latest C200 controller Checkpoint option is selected.

In the Select C300 startup type list, select the startup type and then click Continue.
For more information about the controller startup type, see Control Building User’s Guide.
At this stage of the upgrade, there is a temporary Loss Of View (LOV) from the Server and the
Flex Station to the controller being upgraded. Operations to the upgrading controller are
limited to the Console Station. History Collection is also stopped during this phase and view
from the Flex Station and Server starts after the C300 Controller upgrade is completed.
The temporary Loss of View (LOV) for the upgraded controller from the Console Station is for
about one minute. The view on the Flex Station returns in 40 seconds after the C300 startup
type is selected.
Perform the following tasks if SIM and its strategies are loaded and SIM to PCDI conversion is
performed.
Click Details to view the entire PCDI Master list that must be activated.
- 84 -
The PCDI Activation Details dialog box appears.

l The Details link appears, Click to view the entire PCDI Master list that must be activated. The
PCDI Activation Details dialog box appears.
l Click Activate.
l Select the Task Completed option, and then click Proceed.
After successfully completing the above steps, the Upgrade Chassis A to C300 task is
selected.
After the Transfer control from C200 to C300 task is complete, you cannot change the control
from C300 to C200/C200E.
22. The Upgrade Chassis A to C300 screen appears. Perform instructions given on screen and select
the Task Completed option.
23. The C300 controller with odd device index will be upgraded with the latest firmware next. The Load
Firmware button appears. Click this button.
- 85 -
24. You must now ensure the latest firmware has been flashed on the C300 controller with odd device
index and it is powered on. After confirming this, click the Task Completed option and click
Proceed. See "Upgrade the CF9 module firmware" on page 114.
25. The upgrade proceeds and after a successful upgrade, a notification appears. Click Close to close
the upgrade tool.
- 86 -
If there are any Trends and Groups configured only in Station and are not configured through the
Control Builder Server History and Server Displays tabs, these are lost after the controller upgrade
Congratulations! Your C200/C200E has been upgraded to C300. The strategies are running in C300
and the PM I/O are communicating with the C300.
Refer “QVCS Details” for the QVCS updates during upgrade process.
2.7.2 Off-Process Upgrade

This operation upgrades C200/C200E Controller along with strategies to C300 for an off-process
controller (COMM ERROR, same FTEB Device Index used, or FIM2 configured)
COMM ERROR occurs when either controller is in Project view only, or controller is in Monitoring view
but in crash state (in red color).
This upgrade is applicable to Supervisory FIM2 also.
Prerequisites
l Ensure that you have completed the C200/C200E to C300 readiness checks for upgrade with FIM,
and also the Supervisory FIM2 to FIM4/FIM8 readiness checks for upgrading Supervisory FIM2s.
l Ensure that you have completed the C200/C200E Transform configuration.
- 87 -
Stages of the Off-Process Upgrade
Check Indicates whether there are any blockers for C200/C200E and FIM2 upgrade.
C200/C200E
upgrade
blocker
configuration Configuration tasks. You also need to take ERDB backup using ERDB Admin Tool.
confirmation
Prepare At this stage, the following steps must be performed manually:
controller
Upgrade the Control Firewall firmware.
hardware for
upgrade Prepare the controller hardware for C200/C200E to C300 upgrade.
Ensure to prepare the hardware of FIM4/FIM8.
C200/C200E If C200/C200E controller is configured along with FIM2 in chassis, then this step
to C300 displays a list of strategies in the other controller that are initiating exchange for
upgrade peer-to-peer connection and peer-to-peer connection with this controller. In
notification addition, you are notified with disruption of history collection.
Strategies in QVCS affected during the upgrade are available in the report format.
If a controller is facing a COMM ERROR, all notifications received from a live

controller may not be available.
Finalize For Supervisory FIM, the transformed configuration from FIM2 to FIM4/FIM8 is
Transform finalized.
Configuration
If C200/C200E is configured along with FIM2 it results in the following:
Finalizes the transformed configuration

C200 Checkpoint will be deleted.
Perform Off-Process upgrade
and double-click C200 Upgrade Tool to launch the tool. The Provide User Credentials dialog box
appears.
3. Select the module from the left pane and click Next. You must select the controller with FIM2
configured in the same chassis, or, select the SUPERVISORY_FIM node. On selecting
SUPERVISORY_FIM node, all the Supervisory FIM2(s) are chosen for upgrade simultaneously.
- 88 -
4. The Upgrade Tool Type Selection pop-up appears. Select C300 and click OK.
5. The Upgrade Type Selection screen appears. Select the Upgrade Type and click OK:
a. Off-Process: For a detailed list of conditions when upgrade is off-process, see the section,
"Scope and limitations" on page 138.
- 89 -
6. Only in case of a blocker issue, the C200 Upgrade Blocker screen appears with the relevant
blockers. Resolve the blockers and repeat from step 1.
7. Click Proceed if no upgrade blockers are detected.
8. The Transform Configuration Confirmation screen appears. Ensure that ERDB is backed up using
DBAdmin Tool and C200 configuration transformation is completed using the C200 to C300
Transform Configuration tool. Check the Task Completed option and click Proceed.
- 90 -
9. The Prepare Controller Hardware for Upgrade screen appears. At this stage, you can upgrade
controller hardware by following instructions provided in the section, "Prepare Controller Hardware
for Upgrade" on page 175 .
You can also perform the hardware upgrade post upgrade but before loading modules in
Control Builder.
l If upgrading C200/C200E with FIM2, ensure that the C300 and FIM4/FIM8
hardware configuration is completed. Ensure the I/Os and FF devices are
connected to C300 and FIM4/FIM8.
l If upgrading C200/C200E configured with Series A, ensure that C300 and FTEB
hardware configuration is completed.
l If you are upgrading Supervisory FIM2, ensure that the FIM4/FIM8 hardware
configuration is completed, and FF devices are connected to FIM4/FIM8.
Ensure you upgrade the FTEB firmware using Ntools. See the Fault Tolerant Ethernet Bridge
Implementation guide to launch Ntools and flash the FTEB firmware.
10. After completing the hardware upgrade tasks, return to this screen, click the Task Completed check
box and click Proceed.
- 91 -
11. The C200 to C300 Upgrade Notification screen appears.
On the right pane, the following details are displayed. For example:
l List of strategies in other controllers that are initiating Exchange peer-to-peer connections with
this controller.
l List of strategies in other controllers that are initiating peer-to-peer connections with this
controller.
l Notification of the Upgrade type is mentioned.
l Option to Export the report of strategies under QVCS affected during upgrade.
l If the Controller is facing a COMM ERROR, some of the notifications available for a Live
- 92 -
Controller may not appear.

l However, the controller related notifications will not be seen while upgrading SUPERVISORY_
FIM.
12. Read the instructions on the right pane and then click Proceed.
13. The Finalize Transformed Configuration screen appears.
If FIM2 are under the control of QVCS

l Details of FIM4/FIM8 and their consolidated FIM2 which are under QVCS are seen. Both
primary and secondary modules are considered.
l You can choose FIM2 for applying QVCS details (Qualification State and Revert Label) to
FIM4/FIM8.
l By default, one FIM2 is selected. However, use the FIM2’s list box to select a different FIM2.
Read the on-screen instruction and select the I’m aware of the impact and want to proceed
option and click Proceed.
14. Based on the node selected for upgrade, the result of Finalization is as described here.
l Finalize Transformed configuration for C200/C200E.
o Deletes the C200 checkpoints, transforms C200/C200E and FIM2 configuration, if
any, to C300 and FIM4/FIM8 configuration.
o Deletes C200/C200E and FIM2 configurations from Project and Monitoring views.
o Updates QVCS configuration.
l Finalize Transform configuration for SUPERVISORY_FIM.

o Transforms all Supervisory FIM2 configurations to actual FIM4/FIM8 configuration.
o Deletes FIM2 configurations from Project and Monitoring view.
o Updates QVCS configuration.
15. The upgrade proceeds and after a successful upgrade, a notification appears. Click Close to close
the upgrade tool.
- 93 -
After completing the upgrade and configuring the hardware, load the C300 and its I/Os, FTEBs (if any),
FIM4/FIM8 and its FF devices (if any) and all related strategies manually.
Congratulations! Your C200/C200E has been upgraded to C300.
See the section, QVCS Details for details of QVCS updates that occur during the upgrade process.
2.8 Prepare Controller Hardware for Upgrade
2.8.1 Upgrade hardware using the C200/C200E to C300 hardware upgrade kit 94
2.8.2 Process to upgrade SIM 114
Complete the Check C200 Upgrade Blocker and Transform Configuration Confirmation steps, which
should indicate “Executed” provided the readiness checks and transform configuration are successful.
You cannot proceed with Preparing the Controller Hardware for Upgrade until these two
prerequisites are met.
This section details the procedures required to dismount the C200/200E hardware and mount the C300
using the C200/C200E to C300 hardware Upgrade kit.
Upgrade kit is for C300 and CF9. There is no upgrade kit for FIM4/FIM8.
2.8.1 Upgrade hardware using the C200/C200E to C300 hardware

upgrade kit
The following picture depicts the initial and final stage of the controller hardware upgrade.
- 94 -
The table lists the overall sequence of the tasks to be performed for upgrading C200/C200E Controller
chassis modules with the standard Series C hardware.
Disconnect the power and communication cables Disconnect power and communication cables.
Remove modules from the C200/C200E Controller Remove modules from the controller chassis.
chassis
Mount the Universal Hiway Input/Output mounting Mount Universal Hiway Input/Output mounting
plate plate.
Mount C300/CF9 IOTA Mount the C300/CF9 IOTA.
Mount RAM charger module Mount the RAM charger module.
Mount UHIO Backplane Mount the UHIO Backplane.
Mount the Control Firewall Mount the Control Firewall.
Mount the C300 Controller Mount the C300 Controller.
Mount 24V DC COTS power supply Mount 24V DC COTS power supply.
Connect the power cables for RAM charger module Connect the RAM charger module cables.
Connect the memory cables
Connect 24V DC power supply cables
Connect the FTE cables Connect FTE cables.
Power on C300 and CF9 Power-up C300 and CF9.
Upgrade CF9 module firmware Upgrade the CF9 module firmware.
- 95 -
Disconnect power and communication cables
Prerequisites
Ensure that ERDB is backed up.
Perform the following procedure on the Backup controller. The C200 Backup controller must contain
FTEB even device index.
To disconnect the power and communication cables
1. On the Backup controller, open the door on the power supply and flip the power switch to OFF
position.
2. Unplug the power cable (RED) from the rack-mounted power supply.
3. Unplug the redundancy cables (ORANGE) from the Redundancy Module (RM).
Remove modules from the controller chassis
Prerequisites
l Ensure that the power supply to the chassis is turned off.

l Ensure that the power and communication cables are removed.
To remove the C200/C200E chassis modules
1. Press and hold the locking tabs available on each of the modules. For example, the following
figure displays the removal of Control Processor Module (CPM) from the chassis.
2. Pull and remove the module from the chassis.
- 96 -
The modules must be removed from the cabinet in the following order.
No Description
1 Power supply
2 FTEB module
3 Control Processor
4 Redundancy Module
5 IOLIM
6 PCI Express host card
Remove C200/C200E controller chassis from cabinet
Prerequisites
Ensure that the modules are removed.

To remove the C200/C200E chassis from the cabinet
1. Loosen the screws of the chassis.
2. Remove the chassis from the cabinet. The following figure displays the chassis that is already
removed from the cabinet.
- 97 -
Mount Universal Hiway Input/Output mounting plate
To mount the Universal Hiway Input/Output mounting plate, perform the following procedure.
1. Position the mounting plate to align the screws with the appropriate holes in the cabinet.
2. Tighten screws to 3.9 Nm.
Mount the C300/CF9 IOTA
To mount the horizontal C300/CF9 IOTA, perform the following procedure.

1. Replace the four slotted screws on the UHIO Backplane with four slotted screws (99000222-740)
from the CC-ZHMT10 kit.
2. Place the Horizontal C300/CF9 IOTA on the Horizontal Backplane, as displayed in the following
figure.
- 98 -
3. Tighten the screws in the order specified in the following figure.
4. The mounting screws must be tightened to 1.3 Nm.

5. Tighten the IOTA power connection screws to 1.9 Nm in the following order.
l COM IOTA screw
l 24V IOTA screw
- 99 -
6. Install the second C300/CF9 IOTA on the right side of the Backplane. You can reuse the above
steps to install the second C300/CF9 IOTA.
Mount the RAM charger module
Prerequisites
The UHIO mounting plate is installed.

To install the RAM charger module on the UHIO mounting plate
- 100 -
1. Align the mounting holes in the RAM charger module with the screw hole locations on the right side
of the UHIO mounting plate
2. Secure the RAM charger module to the mounting plate with four screws (highlighted in the image)
and nuts (p/n# 30735043-302) from CC-ZHMT10 kit.
3. Tighten the screws to 3.9 Nm.

4. Connect the protective earth ground cable.
- 101 -
Install Mounting Plate on the Chassis
For instruction purposes, the mounting plate is shown mounted on the backplate without the cabinet.
The following figure shows mounting hole alignment according to 7-slot, 10-slot, and 13-slot rack
locations.
- 102 -
1. Position the mounting plate to align the screws with the appropriate holes in the cabinet.
- 103 -
Mount the UHIO Backplane
Prerequisites
Ensure that the UHIO mounting plate is mounted on the C200/C200E chassis backplate.
To mount the UHIO Backplane
1. Position the Backplane in the UHIO mounting plate and then align the four screws (highlighted)
with the appropriate holes in the cabinet.
- 104 -
3. For ease of installation, it is recommended that you mount the IOTA's onto the Backplane before
mounting the Backplane on the mounting plate. For more information about mounting the
C300/CF9 IOTA, see, Mount the C300/CF9 IOTA.
Mount the Control Firewall
Remove the fuse from the fuse holder to prevent CF9 from powering on by itself.
To install the Control Firewall perform the following tasks:
1. Align CF9 connector pins over the connector/slot on the IOTA labeled as Control Firewall 9 Module.
2. Carefully press down on the CF9 module until it is fully seated in the connector.
3. Use the two side screws to secure the CF9 module to the IOTA.
4. Using a #2 Phillips screwdriver, hand-tighten the plastic screw on the front of the module cover.
Ensure that you do not strip the plastic screw head.
- 105 -
5. Repeat the above steps for the second IOTA.
Mount the C300 controller
Remove the fuse from the fuse holder to prevent C300 from powering on by itself.
Prerequisites
Horizontal C300/CF9 IOTA is installed.

To install the C300 Controller on the Horizontal C300/CF9 IOTA
1. Align the mounting holes in the IOTA with the screw hole locations on the module (over the
connector labeled as C300 Control Processor).
2. Secure the controller module to the IOTA board with two screws located on each side of the plastic
cover.
- 106 -
3. Using a #2 Phillips screwdriver, hand-tighten the plastic screw on the front of the module cover.
Ensure that you do not strip the plastic screw head.
4. Repeat the above steps for the second IOTA.
- 107 -
Set FTE Device Index
1. Set the Device Index (FTE DEVICE INDEX) of the controller according to the site documentation by
turning the three rotary decimal switches located on the IOTA board.
2. Set the switches to the three-digit address ranging from 001 to 509. The leftmost switch (100) is
used for setting the hundreds digit. The middle switch (10) is used for setting the tens digit and the
rightmost switch (1) sets the ones digit.
The Device Index of all non-redundant and primary C300 Controllers must be set to an odd number
address. Similarly, the Device Index of all secondary C300 Controllers must be set to an even number
address.
The FTE DEVICE INDEX setting on the switches should match the number entered in the Main tab of
the Controller block's configuration form.
- 108 -
Mount 24 VDC COTS power supply
Prerequisites
Ensure that sufficient cabinet space is available for installing 24V DC COTS power supply.
To install the 24VDC COTS Power supply:

1. Install DIN-rail in the specified area of the cabinet.
2. Install Power supply modules on DIN-rail.
3. Install Redundancy module on DIN rail.
4. Connect power supply cables as shown below.
- 109 -
An example of Power supply assembly after installation is shown here.
- 110 -
Connect the 24 VDC power supply cables
Prerequisites
l C300 is installed on the Horizontal C300/CF9 IOTA.

l CF9 is mounted on the Horizontal C300/CF9 IOTA.
To connect the Power supply cables:

1. Connect one end (4–pin connector) of the 24VDC power supply cables (51202948-300) to the
Power connectors of the UHIO Backplane.
2. Connect second end (6–pin connector) of the 24VDC power supply cables (51202948-300) to the
J1 and J2 connectors of the RAM charger module.
3. Connect third end (open wires) of the 24VDC power supply cables (51202948-300) to the Terminal
block.
The following figure displays the connection of the 24VDC Power supply cable.
- 111 -
Connect cables
Prerequisites
l Horizontal CF9/C300 IOTA is mounted on the Backplane.

l FTE cables are available.
To connect the cables

1. Connect the FTEA port on the C300/CF9 IOTA to a port on J7 or J13 on the primary IOTA using a
yellow Ethernet patch cable.
2. Connect the FTEB port on the C300/CF9 IOTA to a port on J7 or J13 on the secondary IOTA using
a green Ethernet patch cable.
3. Connect FTE uplink cables.
4. Connect redundancy cable.
The following figure displays how the FTE cables are connected.
- 112 -
Connect the RAM charger module cables
Prerequisites
Ensure that the Horizontal C300/CF9 IOTA is installed.
To connect the memory cables:

1. Connect one end (2–pin connector) of the RAM charger module cable (51202330-300) to the P1
connector of the RAM charger module and the other end to the J12 connector of the first Horizontal
C300/CF9 IOTA.
2. Connect one end (2–pin connector) of the RAM charger module cable (51202330-300) to the P2
connector of the RAM charger module and the other end to the J12 connector of the second
Horizontal C300/CF9 IOTA.
Power-up C300 and CF9
Ensure that you have replaced the required hardware and connected the FTE cables.
Power-on the C300 controller with even device index first and ensure that it is communicating with the
system. Do not power on C300 controller with odd device index. For more information on powering-on
C300 and CF9, see C300 Controller User's Guide
Connect I/O link cables
Ensure that you connect the IOLINK cables in the same order as selected during the C200/C200E to
C300 transformation.
Prerequisites
l UHIO IOTA is mounted on the Backplane.

l CF9/C300 IOTA is mounted on the Backplane.
l I/O link cables are long enough to reach from the PM I/O card files to the Series C IOTA.
- 113 -
To connect the I/O link cables
1. Connect the PM I/O link cables to the PM I/O card files.

2. Connect the special adapter cables (51202341-102) to one end of PM I/O link cables.
3. Connect the Series C I/O link cables to the special adaptor cables.
4. Connect the Series C I/O link cable to the C300/CF9 IOTA.
Upgrade the CF9 module firmware
C200 Upgrade tool does not automatically upgrade the CF9 firmware. Hence, you must upgrade to the
latest CF9 firmware.
1. Choose Start > All Programs > Honeywell Experion PKS > Engineering Tools > Control Firewall
Update. The Control Firewall Update dialog box appears.
2. Select the firmware from the Control Firewall Configuration section, and then click Browse. The
CF9 Open File dialog box is displayed.
3. Select the latest CF9_Part1.Hex file from: C:\Program Files (x86)\Honeywell\Experion
PKS\Engineering Tools\system\FIRMWARE\CF9, and click Open.
4. If you have installed the Experion using the Custom Installation option, the Control Firewall
firmware can be located from the path %User selected software path%\Honeywell\Experion
PKS\Engineering Tools\system\FIRMWARE\CF9.
5. Click Start to upgrade the firmware. The firmware is upgraded.
6. Click Browse. The CF9 Open File dialog box is displayed.
7. Select the latest CF9_Part2.Bin file from C:\Program Files(x86)\Honeywell\Experion
PKS\Engineering Tools\system\FIRMWARE\CF9, and then click Open.
8. If you have installed the Experion using the custom installation option, the Control Firewall
firmware can be located from the path: %User selected software path%\Honeywell\Experion
PKS\Engineering Tools\system\FIRMWARE\CF9.
9. Click Start to upgrade the firmware. The firmware is upgraded.
10. Click Close.
Before upgrading the C200/C200E to C300, ensure that auto Checkpoint Save operations are stopped.
Control Recipe must not be running during C200/C200E to C300 upgrade. If Control Recipe is
running, Control Recipe related activities are removed from Activities Summary page.
After upgrading the C200/C200E to C300, C200/C200E CEE related parameters in custom
displays are lost.
After upgrading to C300, the following parameters configured in the C200/C200E CEE are moved to
C300 CEE.
l DAYLIGHTTIME
l TIMEZONE
l WEEKDAYFMT
l YEARFMT
2.8.2 Process to upgrade SIM

Prerequisites
Perform the following procedure only if SIM and its strategies are loaded.
- 114 -
1. Manually modify SIM and its related strategies to communicate with the C300 with Series A
Chassis I/O topology with FTEB, if you do not want to upgrade SIM to PCDI.
2. Check if the hardware can support Modbus TCP or is a Serial Modbus to Modbus TCP converter
required. If the hardware can support Serial Modbus to Modbus TCP converter, then you can select
one of the following:
l Qualified Modbus TCP to Serial gateway devices
l Digi One IA, Digi One IAP
l Lantronics Xpress-DR-IAP
l Connect the Ethernet cable between the device/bridge to the L2 switch.
To disconnect the device from SIM

1. Disconnect the device from the respective FTA.
2. Connect the device to the L2 switch.
3. Configure the TCP Bridge based on the device connected. For example, configure the Allen
Bradley (IAP) device or the RS232/RS485 (IA bridge) protocol-based device.
For more information about the configuration and wiring of the TCP Bridge, refer to the Original
Equipment Manufacturing (OEM) document.
2.9 Post Upgrade Activities

2.9.2 Considerations 115
2.9.3 Updating the network configuration 116
2.9.4 Loading after performing Off-Process Upgrade 117

2.9.5 Update and load Exchange blocks in peer server 117
2.9.1 Prerequisites
Completing checkpoint-related tasks
Complete the following tasks from the Control Builder.

1. Perform Upload and Update to Project with contents operations for the upgraded C300 to
synchronize the Project view ERDB and Monitoring view ERDB.
For more information about the Upload and Update to Project with contents operations, see
Control Building User’s Guide.
2. Perform a Checkpoint Save of the upgraded C300.
2.9.2 Considerations
Considerations for peer-to-peer communication from PMD controller
Note that the C200 Upgrade tool does not detect any peer-to-peer communication initiated from the
PMD Controller.
If there are peer-to-peer communications initiated from the PMD Controller to the C200/C200E, you
must reload the strategies from the PMD Builder after upgrading the associated C200/C200E.
- 115 -
Activate PCDI master and its strategies
Ensure that PCDI master is activated and its communication to the device is successful, and then
activate its strategies.
Considerations for retuning loops
After upgrading from C200/C200E to C300, re-tuning of loops is not required. However, if needed you
can re-tune the loops.
Activate Series A and its strategies
After upgrading from C200/C200E with Series A to C300 with Series A, verify that the related FTEB(s)
are loaded and then activate the Series A modules and their strategies.
Reestablishing peer connections
To reestablish peer connections that are initiating from other controllers to the controller that is
upgraded, select the strategies of other controllers initiating peer connections and download them.
2.9.3 Updating the network configuration

Prerequisites
l You have upgraded either of the following topologies:

o C200/C200E to C300.
o C200/C200E with FIM2 to C300 with FIM4/FIM8
o Supervisory FIM2 to FIM4/FIM8
l C300 must be available if upgrading from C200/C200E.

l FIM4/FIM8 must be available if upgrading FIM2.
To add FTE communities to the Network tree
1. In the Configuration Explorer in Configuration Studio, expand the System tree you are configuring
and click Devices.
2. Click the Define FTE community’s task. The FTE Definition display appears.
3. Type the FTE Community Name and click Apply. The FTE community appears in the Devices tree.
4. Select the check box for the controllers listed in the PD Tag Name column and click OK.
To add Control Firewall to the Network tree
1. In the Configuration Explorer in Configuration Studio, expand the System tree you are configuring
and click Devices.
2. Click the Add Control Firewall to the Network Tree task. The Add Control Firewall Definition tree
display appears.
3. Select the control firewall name and click Apply.
- 116 -
To load the Network tree configuration
1. In the Configuration Explorer in Configuration Studio, select the system you want to configure. The
Network tree appears underneath the system item.
2. Click the Network item in the tree.
3. Under Network Tasks, click Load Network Configuration To Servers.
4. In the Load column, select the check boxes of the servers that you want to download to the Network
tree.
5. Click OK to begin the Network tree load to the selected servers.
The C300/FIM4/FIM8 appears in the FTE Status display. The CF9 pair appears in the Configuration
Studio and in the Station System Alarm Summary display.
2.9.4 Loading after performing Off-Process Upgrade

Prerequisites
l You have upgraded either of the following topologies:

o C200/C200E with FIM2 to C300 with FIM4/FIM8
o C200/C200E to C300 with Communication Error
o C200/C200E to C300 using C200 FTEB Device Index
o Supervisory FIM2 to FIM4/FIM8
l C300 must be available while upgrading C200/C200E to C300.

l FIM4/FIM8 must be available while upgrading FIM2.
l All the configurations are seen only on the Project view in Control Builder.
l Hardware should be mounted, connected, powered on, and communicating with the system.
Perform load operations (C200/C200E to C300 with or without FIM2 to FIM4/FIM8)
Modules and its related strategies shall be loaded in following order based on their availability:
C300 Module, FTEB and Series A modules, PMIO, PCDI, FIM4/FIM8, FIM devices and Strategies.
On loading C300, if any checkpoint issue is observed, continue loading and then perform rebuild and
restore of checkpoint.
Perform load operations (Supervisory FIM2 to FIM4/FIM8)
Modules and it related strategies shall be loaded in following order based on their availability:
FIM4/FIM8, FIM2 devices and Strategies.
2.9.5 Update and load Exchange blocks in peer server

Perform this procedure after the current C200 to C300 upgrade completion.
- 117 -
To update and load the Exchange blocks in peer server
1. Log in to Control Builder of the peer Server which contains the exchange peer-to-peer connections
with the Current Server where the tool is executing.
2. Open the strategies containing the exchange peer reference.
3. Modify the exchange path in the Project side.
4. Load the strategies containing the exchange peer reference.
2.10 Troubleshooting and Maintenance

2.10.3 Remove the C200 Upgrade tool 120
2.10.4 Isolate the Console Station from the server 120
2.10.6 AB PLC2/3/5 address is not mapped for the Input and the Status file type 121

2.10.10 Load firmware to C300 failure scenarios 123

2.10.12 Load FTEB Error Handling 123
2.10.1 Cancel CNET to FTE upgrade

To cancel CNET to FTE upgrade before Server B becomes primary:
1. Click Cancel on the CNET to FTE Upgrade screen and confirm restarting the required services.
An User Account Control appears when performing the Network type change (from FTE to
CNET) and services restart. Provide the Administrator credentials and click Yes.
2. Click OK.
3. Restore the ERDB using the DBadmin tool.
4. Close the CNET to FTE Upgrade.
To cancel CNET to FTE upgrade after Server B becomes primary:
1. Click Cancel on the CNET to FTE Upgrade screen. A confirmation appears prompting you to restart
the required services and disconnect Server B from the network.
User Account Control appears when performing Network type change (from FTE to CNET) and
services restart. Provide the Administrator credentials and click Yes.
2. Disconnect the Server B from the network.
3. Reconnect the Server A with CNET hardware to the network, and then power-on the Server A.
- 118 -
4. Restore the ERDB using the Badin tool.

5. Power off the Server B.
6. Reconnect the Server B with CNET hardware to the network, and then power-on the Server B.
7. Close the CNET to FTE Upgrade tool.
2.10.2 Cancel controller upgrade

You can cancel the upgrade during the following stages:
l Before preparing the controller configuration for an upgrade.
l During transfer of control from C200/C200E to C300.
Contact Honeywell TAC on how to proceed with the upgrade before restoring the ERDB.
To cancel the upgrade before preparing the controller configuration for upgrade
1. Click Cancel on the C200/C200E to C300 upgrade screen. A confirmation message appears
prompting you to launch the C200 to C300 Transform Configuration tool.
2. Click OK.
3. Click Start > Honeywell Experion Tools> All Honeywell Tools. Open the C200 Upgrade tool folder
and double-click C200 to C300 Transform Configuration to launch the tool.
4. The Provide User credentials dialog box appears. Type the Password.
5. Click Transform Cancel. The shadow configuration of the C300 is reverted to C200/C200E.
To revert the hardware upgrade
1. Power-off the C300 and CF9s, and then remove the Horizontal Backplane and the backplate.
2. Mount back the C200/C200E secondary chassis.
3. Insert the C200/C200E chassis modules (FTE, C200, RM, IOLIMs) back into the chassis.
4. Connect the IOLINK cables back to the IOLIM in the C200/C200E secondary chassis.
5. Power-on the secondary C200/C200E chassis so that the C200/C200E controller, RM and IOLIM
start up, synchronize and the chassis redundancy is restored.
When you cancel the upgrade to C300, you need to mount the C200 chassis and Series A hardware
only if you plan to continue to use C200 Controller for an extended period of time.
To cancel the upgrade during transfer of control from C200/C200E to C300
1. Click Cancel on the C200/C200E to C300 upgrade screen.

2. Restore the ERDB using the DBAdmin tool.
3. Enable ERDB replication using the DBAdmin tool.
4. Power-off the C300 and CF9s, and then remove the horizontal backplane and the backplate.
5. Mount back the C200/C200E secondary chassis.
6. Insert the C200/C200E chassis modules (FTE, C200, RM, IOLIMs) back into the chassis.
7. Connect the IOLINK cables back to the IOLIM in the C200/C200E secondary chassis.
8. Power-on the secondary C200/C200E chassis so that the C200/C200E Controller, RM and IOLIM
start up, synchronize and the chassis redundancy is restored.
If you cancel the upgrade during transfer of control from C200/C200E to C300, then there is no point of
return that is Loss of Control (LOC) occurs.
- 119 -
2.10.3 Remove the C200 Upgrade tool

After the upgrade is complete, you may remove the C200 Upgrade tool.
1. Choose Start > Control Panel > Programs > Uninstall Programs.
2. Right-click C200ToC300Upgrade, and select Uninstall. Acknowledge the confirmation message.
3. Wait for some time. The C200 Upgrade tool is removed.
2.10.4 Isolate the Console Station from the server

The following topics describe how to the isolate the Console Station from the server.
Delete the Console Station from the server
1. In Station, choose Configure > System Hardware > Stations > Console Stations. The Console
Station Configuration Summary display appears.
2. In the Details tab, click Delete and acknowledge the message that appears.
Before deleting the Console Station, disconnect the server by either removing the both the FTE cables
or shutdown the Console Station.
To reconnect the Console Station
l Re-configure the Console Station using the Station application.
Isolating the Console Station from the server
To isolate the Console Station from the server
1. Edit the hosts file in the Console Station, and then comment the entries for the server.
2. Save the edited hosts file.
There is no need to disable DNS as the Console Station relies on hosts file entries.
3. On the Console Station, stop the following processes in the Task Manager on the Console in the
order listed.
l Ms_linkd.exe
l DbRepCli.exe
l GdaMngr.exe
l GdaNotCli.exe
Stopping the processes does not make the processes disappear, but forces them to restart/refresh.
The Console Station is disconnected from the server. However, you can still view the CDA data on the
Console Station. If you invoke a trend, you can see both the trend value and the pen. However, you
cannot view the history parameters, as the Console Station does not store history parameters. If you
leave the trend for a while, you can observe the plot lines rising up. If you refresh the trend page or
navigate to another page and then return to the trend, you can observe the following:
l The plot lines would have disappeared, and
l Re-plotting has begun from the right side of the screen.
- 120 -
To reconnect the Console Station
Re-add the entries for the server in the hosts file on the Console Station and reboot.
After a few minutes the Console Station will automatically reconnect and start reading the history
parameters from the server again.
2.10.5 Alarms generated during upgrade

The following are some of the alarms generated during upgrade:
l NDM manager intermittent cable communication error and Umax error alarms are expected.
l No tag alarms are generated in Console Station. After upgrade, you must acknowledge these
alarms.
If the quality of alarm is bad, perform the alarm regeneration:

1. Go to Station > Configure > Alarm and Event Management > Alarms > Alarm Processing tab.
2. Uncheck the Enable alarm server-wide option under Processing settings. Ensure that all alarms
are cleared.
3. Check the Enable alarm server-wide option under Processing settings. All bad quality alarms are
not seen.
During this process, all the alarms disappear from process and system alarm summary temporarily and
are regenerated. Bad quality alarms are greyed out and can be acknowledged. Perform this operation
only when it ok to not have any alarms for up to few minutes.
Perform this operation only when you want to clear the bad quality alarms.
2.10.6 AB PLC2/3/5 address is not mapped for the Input and the
Status file type
Cause
For PLC type 2/3/5, if the AUXDATA [6] parameter (specifies the datatype for AB PLC) is set to 1 (that is,
Input Type) or 2 (that is, Status Type), the SIFLAGARRCH block is used for reading these files.
In the PCDI configuration to communicate to the AB PLC, DigiONeIAP Bridge is used.
According to the DigiOneIAP manual, for reading the Input and Status type, the address range should
be 4x00251 - 4x00500 and 4x00501 - 4x00750 respectively. In PCDI, this range can be entered only for
the PCDINUMARCH block.
When upgrading SIM to PCDI, the tool does not convert SIFLAGARRCH block to PCDINUMARCH
block, hence the conversion fails for the Input and Status type. These details appear in the Transform
configuration summary report.
Solution
Manually create the PCDINUMARCH block for the SIFLAGARCH block. You may also need to add the
Type conversion block to read the values from the files as float and convert it to binary.
- 121 -
2.10.7 Device index is not in the PCDI range

Cause
The PCDI supported device index range is 1-247 and 255. If the device index entered in SIM is not in
the supported range of the PCDI.
Solution
Manually change the device index field in the Control Builder, or, if needed, you have to modify the
device index in the PLC.
Cause
If the PCDIMASTER is connected to only one device.
Solution
Enter 255 for the device index in the Control Builder and change it in the PLC.
Cause
If the PCDIMASTER is connected to multiple devices.
Solution
Map the PLC device index to PCDI range in the bridge or modify the device index of the PLC.
2.10.8 PCDI activation error

Cause
The tool has the optional feature to activate the PCDIMaster. However, activation of the PCDIMaster
fails for many reasons. For example,
l PCDI license is not available
l The TCP Bridge configuration is not correct.
l Proper wiring is not done between the TCP Bridge and the device.
l L2 Ethernet cable is not connected properly with the TCP Bridge.
Solution
Check the activation error in the Control Builder, fix the issue, and then activate it manually before
activating the strategy to communicate to the PCDI.
For details on activation failure and troubleshooting, refer to the Peer Control Data Interface
Implementation Guide.
- 122 -
2.10.9 Slave FTA Handling

Cause
PCDI always acts as a Master. If any site has Slave FTA (part no - 51191029), then SIM with this Slave
FTA configuration cannot be upgraded. The C300 controller with this PCDI cannot communicate to the
PLCs which are connected to this Slave FTA.
Solution
The C300 Controller can communicate to the device/PLC either through C300 with Series A Chassis I/O
topology with FTEB or through OPC server (SCADA configuration).
2.10.10 Load firmware to C300 failure scenarios

Cause
Following are the failure scenarios if the C300 is not upgraded to the latest firmware.
l C300 is not powered ON.
l C300 is not connected to the FTE network; hence the Server cannot communicate to the C300.
l C300 does not take the correct IP because the BOOTP services are not running, or multiple
BOOTP services are running.
Solution
Open the CTool utility, power on C300 if it not seen in CTool utility and then upgrade the C300 to the
latest firmware.
2.10.11 Readiness check failure scenarios

Cause
C200 Upgrade tool server readiness check does not execute both server and controller checks, it
remains in NE (Not Executed) state.
Solution
To resolve this issue, perform the following steps.

1. Restart the Upgrade Tool.
2. Restart the server running the readiness check.
3. Run only the server check or the controller check (one or the other, but not both together).
2.10.12 Load FTEB Error Handling

Cause
Failure scenarios for FTEB not loading during upgrade include:

l FTEB is not mounted in the expected slot of Series A chassis
- 123 -
l FTEB chassis is not powered ON.
Solution
Post upgrade, ensure FTEB is loaded and then activate Series A.
2.10.13 QVCS Details

QVCS updates while Upgrading Experion Process Network from CNET to FTE
Block types QVCS details

C200/C200E, Version: Major/Minor version will be updated for the upgraded module (based on
IOLIM, RM user selection)
and FIM
Qualification State and Label: Qualification State and Label will be moved from the
current active or working version (before upgrade) to the upgraded version. The
upgraded version will become the active or working version.
History: Choose QVCS Manager > Object History. Select Checkin from the Action
list.
l Entry for CNET to FTE upgrade is displayed for the corresponding version
created during the upgrade.
l History of previous versions of objects before upgrade are displayed.
Revert to Version in Control Builder: After performing CNET to FTE upgrade, revert
the Platform Block to a version that existed before the upgrade. A message stating
revert is not allowed will be displayed. However, if there are any version increments
after the upgrade, reverting the newer versions will not have any impact.
Revert to Label in Control Builder: After performing CNET to FTE upgrade, revert
the Platform Block Version to a Label that was applied before the upgrade. A
message stating revert is not allowed will be displayed. However, if there are any
Label version increments after the upgrade, on reverting the label on the newer
versions will not have any impact.
QVCS updates while Upgrading C200/C200E to C300 or FIM4 to FIM4/FIM8
When upgrading C200/C200E to C300, FIM2 to FIM4/FIM8, SIM to PCDI, Series A IO and Exchange
strategies, QVCS details such as Version, Qualification State, Label, Revert to Version and Label
details are updated as described here.
l Version: The strategies upgraded will be initialized to major version (1.0). For Series A, see the
section, QVCS updates while Upgrading Series A modules.
l Qualification State and Label: Qualification State and Label will be moved from the current active
or working version (before upgrade) to the version initialized (1.00) during the upgrade. This
initialized version will become the active or working version.
l Revert to Version in Control Builder: For versioning initialized objects, this scenario will not hold
good. However, for other objects, reverting versions will be successful.
l Revert to Label in Control Builder: Trying to revert to label (Label created and applied to versions
of object) before upgrade will not be allowed and a message informing that“A different object with
the same name exists in the project, cannot revert” will be displayed.
- 124 -
Workaround
1. Go to QVCS Manager > Query and select Revert Label from the Query on dropdown list.
2. Select the label to be reverted to from the Value list. Click List .
3. Select respective deleted object which appears in the list.
4. Right click on the selected object > Select Revert Labels > Select Apply/Remove > Select To
selected version > Remove label from Applied Revert Labels(for the version) .
5. Follow step 3 for all the deleted objects in the list. Ensure the label is removed for all the deleted
instances of the particular object.
6. When you try to revert to a label applied before upgrade, revert will be successful.
View History of objects under QVCS after upgrade
For History details, choose QVCS Manager > Object History and select Checkin from the Action
dropdown box. Details for each upgraded block types seen are described here.
Block type Upgraded History details

Block Type
SIM PCDI l Entry for object version created during upgrade
l History of previous versions of object before upgrade
FIM FIM4/FIM8 Entry for object version created during upgrade. In case of FIM, total
number of FIM objects consolidated to FIM4/FIM8
Control Control History of each object
Module Module
C200 C300 l Entry for object version created during upgrade
l History of previous versions of object before upgrade
QVCS updates while Upgrading Series A modules
When upgrading C200/C200E to C300 with Series A modules, QVCS details such as Version,
Qualification State, Label, Revert to Version and Label details are updated as described here.
- 125 -
Block QVCS details

types
Series A Version: Major version will be incremented for the upgraded module.
Modules
current active or working version (before upgrade) to the upgraded version. The upgraded
version will become the active or working version.
History: Choose QVCS Manager > Object History. Select Checkin from the Action list.
l Entry for C200 to C300 upgrade is displayed for the corresponding version created
during the upgrade.
Revert to Version in Control Builder: After performing C200 to C300 upgrade, revert the
Series A module to a version that existed before the upgrade. A message stating revert is
not allowed will be displayed. However, if there are any version increments after the
upgrade, reverting the newer versions will not have any impact.
Revert to Label in Control Builder: After performing C200 to C300 upgrade, revert the
Series A Module Version to a Label that was applied before the upgrade. A message
stating revert is not allowed will be displayed. However, if there are any Label version
increments after the upgrade, on reverting, the label on the newer versions will not have
any impact.
See the Qualification and Version Control System User's Guide for more information about QVCS.
2.11 Appendix A Off-process upgrade without Upgrade Tool

This section describes procedures specific to performing an Off-Process upgrade but without using the
Upgrade Tool. Note that in this method, most tasks are performed manually.

The following table describes the scope and limitations of an Off-Process upgrade without Upgrade
Tool.
- 126 -
Hardware Third- Software Tool

party
modules/
interfaces
Supported l C200/C200E l Experion_ C200/C200E
R5xx to C300
l PM I/O
(optional)
modules Upgrade tool
50 ms
RM (for readiness
l CEE
checks only)
l IOLIM
l FTEB
l SIM with
Serial/PLC
devices
l Series A I/O
modules (1.5
modules per
C300)*
Not supported FIM2 and LIOM AB Drive Toledo Weigh
Controller scale I/O
I/F (1203- blocks
CNI)
1757-
CN2FF
module
* Series A modules are supported on C300 with additional hardware. For more information, see
section Understand the differences between C200/C200E and C300.
2.11.2 Hardware and software requirements

Upgrade Hardware Software
option
Option 1 Standard Series C hardware including FIM4/FIM8 C200 Upgrade tool (optional;
(mounted in a new Series C cabinet) useful for performing readiness
checks)
Option 2 Series C hardware including FIM4/FIM8 (mounted on a C200 Upgrade tool (optional;
sub pan, and the sub pan mounted in an existing useful for performing readiness
cabinet) checks)
Option 3 C200/C200E to C300 hardware upgrade kit. C200 Upgrade tool (optional;
useful for performing readiness
FIM4/FIM8 module mounted on standard Series C
checks)
cabinet
Sub pan is a cabinet-less solution that comprises of a flat metal sheet that allows you to mount the
Series C components.
- 127 -
2.11.3 C200 Upgrade tool components

Component Purpose
Server and controller To perform all the readiness checks on the C200/C200E modules
readiness checks before starting the upgrade tool.
Readiness checks to perform Off-Process upgrade without using Upgrade

Tool
Honeywell recommends you to perform the following readiness checks manually, though the readiness
checks can be performed using the C200 Upgrade tool for an Off-Process upgrade.
Server and network readiness checks
Server and network readiness Description/work around

checks
Is the Server at the supported Upgrade the Server to the supported main release of Experion if
main release? the Server is not already upgraded.
Are the servers connected to the Move the servers to the FTE topology if they are not on the FTE
Experion supervisory network topology.
nodes (ACE, Server, and Flex)
through FTE?
Are the servers connected If your servers are connected to the Experion Process Network
through CNET on Experion through FTE, you can skip the CNET to FTE upgrade and proceed
process network? with controller upgrade.
Are there any IOLIMs residing in Ensure that IOLIMs reside in the C200/C200E chassis only.
a chassis independent of
C200/C200E?
Are there any unsupported If there are any unsupported modules then disconnect the
modules? modules and delete modules and the strategies associated with
those modules.
Are there any unsupported If there are any modules with unsupported firmware versions then
release.
Are there any interface modules If there are any interface modules connected to the Experion
(such as LIOM) connected to the process network, identify if they are supported on C300 as well
Experion process network? and upgrade accordingly.
Are there any active locks? Run DBAdmin tool from the configuration studio.
Verify that there are no active locks in ERDB, EMDB. Verify that
the active locks are cleared, if they are found.
Is the BOOTP Server configured? The BOOTP Server service must be enabled and running on one
of the server cluster pairs.
Select Primary Servers from other cluster having Exchange block
peer connection to the upgraded controller. Based on the
selection, the readiness check populates the strategies having
Exchange Peer connection.
Is an empty slot available in the Ensure that an empty slot is available in the C200/C200E chassis
C200/C200E chassis for the for the FTEB module. Otherwise, you need to install a new
FTEB module? chassis and mount the FTEB module.
- 128 -
Controller and Supervisory FIM2 readiness checks
Controller and Supervisory Description/work around

FIM2 readiness checks
Are the servers connected to Connect the Server to Experion Process Network through FTE.
the Experion process network
through FTE?
Are there any unsupported Delete the associated strategies from Control Builder and
modules? disconnect the modules before the upgrade.
Are there any unsupported If there are any modules with unsupported firmware versions then
release.
Is the C200/C200E connected Delete the strategies that contain the I/Os from the Control Builder
to I/Os other than PM I/Os/ Monitoring view and unassign them from the Project view.
Serial Interface Module?
Delete the I/Os from the Monitoring view and unassign them from
the Project view.
Are the number of I/Os within Ensure that the I/Os configured in the Controller are in the
the controller specification controller specification limits.
limits?
Are there any function blocks Delete the function blocks manually from the Monitoring view and
currently loaded to the C200/ unassign it from the Project view.
C200E which are not
supported in C300?
Are there any strategies in Remember to reload the CMs initiating peer references to
other controllers with peer parameters of the C200/C200E block after the upgrade.
references to parameters on
this C200/C200E block?
Are there any strategies with Delete such references to the parameters from the Monitoring view
references to parameters on and reload them after the upgrade.
the C200/C200E or CEE blocks
that will not work after the
upgrade?
Are there any strategies in This check lists the strategies in other Controllers containing the
other controllers initiating peer peer connections to the upgrading C200 Controller.
connections to this
C200/C200E?
Are there any interface Use FTEB phase 2 solution for Series A/SIM.
modules or Series A SIM?
For SIM, PCDI or SCADA can be used.
Are there Profibus SST Use PROFIBUS Gateway Module (PGM) instead of Profibus SST
Modules, Profibus I/Os or Module and C300 with Series A Chassis IO topology with FTEB.
Profibus Devices configured?
Are there any DeviceNet If you want to continue to use them after upgrading to C300, then
modules or DeviceNet devices use the C300 with Series A Chassis I/O Topology with FTEB, re-
configured? configure, and reload after the upgrade. The associated strategies
must be deleted from the Monitoring view of Control Builder before
the upgrade.
Are there any strategies If you want to continue to use them after upgrading to C300, then
containing Series A Modules? use the C300 with Series A Chassis I/O topology with FTEB, re-
configure, and reload after the upgrade. The associated strategies
must be deleted from the Monitoring view of Control Builder before
the upgrade.
Are there any strategies in Re-configure such peer connections to modify the path and reload
- 129 -

other controllers initiating after the upgrade.
Exchange peer connections to
this C200/C200E?
Are there any strategies in This check lists the strategies assigned to the Controllers (in other
other controllers (in other Servers) initiating exchange peer connections to the upgrading
Servers) initiating Exchange C200 Controller. Update the Exchange block path before the
peer connections to this C200/ upgrade in the Project view and then the tool loads the updated
C200E? strategies.
Are there any strategies Exchange block paths must be updated, re-configured and
initiating Exchange peer reloaded after the upgrade.
C200/C200E?
Are there any dangling peer Resolve such connections with the right references.
connections?
Are there any peer references Delete such peer references from the Monitoring view of Control
to the secondary blocks? Builder and reload them after the upgrade.
Are there any dangling control Resolve such connections with the right references.
connections?
Are there any In Control Builder, right-click the controller and select Identify
ghost/inconsistent modules in ERDB/Controller inconsistency.
the controller?
Are there any strategies with This check lists the strategies that have references to parameters
references to parameters on on the RM, FTEB and IOLIM blocks.
the RM, FTEB and IOLIM
blocks?
Are there any Inactive Open the Control Builder and perform any of the operations before
strategies containing upgrade from the following options:
Exchange blocks in this
C200/C200E? Activate the strategies which are in inactive state.
Delete the strategies from the Monitoring view.
Reload the strategies.
Do you have C300 control If you do not have enough licenses, procure the same.
solver licenses available for all
the C200/C200E being
upgraded?
Are there any Serial Interface This check will list SIM modules and corresponding strategies
Modules and corresponding which are configured in this C200/C200E Chassis configuration.
strategies configured in this
C200?
Are there any strategies with Delete such references to the parameters from the monitoring view
references to parameters on and reload them after the upgrade.
Serial Interface Module that
would not work after the
upgrade?
Is Peer Control Data Interface If you do not have enough PCDI licenses, procure the same.
license available for all SIM
being upgraded?
List of strategies in this C200 This check will list strategies assigned to controller having peer
initiating peer connections to communication to FIM2 present in the same local chassis.
FIM2 present in this Local
- 130 -

Chassis?
Are there any strategies in this You need to upgrade this peer FIM2 to FIM4/FIM8 and then
C200 initiating peer perform load operation for these strategies.
connections to FIM2 present in
other controller/Supervisory
Chassis?
Are there any strategies in Delete such peer references from the Project and Monitoring view
other Controllers initiating peer of Control Builder.
connections to FIM2(s)
configured along with this
C200?
Are the number of FIM2(s) You need to consolidate FIM2 to FIM4/FIM8 to ensure the
within the Tech and Spec FIM4/FIM8 per C300 spec is not exceeded.
Limits?
List of FIM2(s), Links, Devices This check will list strategies and devices assigned under links in
and Strategies. this FIM2.
Are there any strategies in Delete such peer references from the Project and Monitoring view
other Controllers initiating peer of Control Builder.
connections to FIM2(s) present
in this Chassis?
Are the number of Supervisory Ensure that the Supervisory FIM2(s) are in the Tech and Spec
FIM2(s) within the Tech and Limits.
Spec Limits?
2.12 Appendix-B Checklist for ControlNet to FTE conversion

This section includes the required steps to upgrade the Experion Process Network from CNET to FTE.
Task Done?
The system should be running Experion R5xx.
Supervisory network should be on FTE.
Contact Honeywell TAC if the supervisory network is not on FTE.

C200/C200E/IOLIM/SIM/FIM2, is flashed to the latest firmware Experion R5xx (or the
firmware is interoperable with the system on Experion R5xx.
FTEB modules is flashed to the latest firmware Experion R5xx (or the firmware which is
interoperable with the system on Experion R5xx.
If the secondary module names are missing in the configuration form, make sure to run the
script provided.
Ensure BootP is disabled and stopped in all the Servers.
C200 Upgrade tool is installed on Server A and Server B.
Readiness Checks are run and results are successful.
All peer-to-peer (CDA and EXCHANGE) points have been reviewed and confirmed safe to
proceed.
Log in to the Server with appropriate privileges to perform the upgrade. (For example,
administrator privileges) and run the UpdateBaseIP_SubnetMask_Batch.cmd file.
Enter the following details.
- 131 -
Task Done?
Base IP — For example, 10.144.1.0
Subnet — For example, 255.255.248.0
Double-click Redundancy Module and Disqualify the Secondary module.
Power off the secondary C200 rack.
Install FTEB with the odd device index. For example 13.
Power on the secondary rack.
Synchronize the secondary controller.
Initiate switchover.
Power off secondary rack.
Install FTEB with the even device index in the new secondary rack.
Power on the new secondary rack.
Confirm synchronization.
Close the Control Builder.
Disconnect Server B from the CNET and FTE networks and confirm the primary status.
Right-click the CNET to FTE Upgrade Tool and select the Run as administrator option.
Confirm the odd addressed device index is the primary C200.
Select the Task completed check box and click Proceed.
Confirm ERDB Backup and click Proceed.
Click Proceed to upgrade Server B to FTE and click Yes.
Enter Base IP and additional information. For example, Subnet.
Enter FTEB name, for example, FTEB31X, Device Index, for example, 13, and slot, for
example, slot 4 and then click Proceed.
Confirm status changes to Executed.
Check registry settings (HKEY_LOCAL_Machine > Software > Wow6432node > Honeywell
> TPS50 > InstallInfo > NetworkType is changed to FTE.
Open Control Builder and confirm both primary and secondary controllers, RMs and IOLs are
shown in each new FTEB. For example, FTEB31X and FTEB31XSEC
Connect Server B to FTE network.
Confirm from the Station in the System Status page that the System Repository backup is
not synchronized and stopped.
Synchronize Server B from Server A.
From Server B, open NTOOLS -e and confirm the view to FTEB’s and C200.
Manual Failover from Server A to make Server B primary and confirm view to controllers.
Shutdown Server A.
Disconnect CNET cables from Server A.
Disconnect FTE cables from Server A.
Power on Server A.
- 132 -
Task Done?
Run UpdateServertoFTE script on Server A.
Shutdown Server A.
Connect FTE network to Server A.
Power on Server A.
On ServerB, in DBAdmin, check ERDB host information and that both are running.
On Server B, in DBAdmin, recover Secondary from Primary.
Confirm if it is successful.
On Server B, in DBAdmin, check ERDB host information and that both are running. If Server A
fails, reboot Server B after enabling the ERDB replication.
Synchronize the servers.
Failover the servers and synchronize the servers.
Enable the ERDB replication.
2.13 Appendix C Checklist for C200 to C300 conversion (Live

Upgrade)
This section includes the required steps to upgrade the C200/C200E Controller to C300 Controller.
Task Done?
New server license with both C200 and C300 Control Solver must be installed on Server A
and Server B.
Switch configuration must be complete in preparation for CF9 connections.
C200/C200E/IOLIM/Series A is flashed to the latest firmware Experion R5xx (or the
firmware is interoperable with the system on Experion R5xx.
ControlNet to FTE conversion must be complete if applicable.
C200 Upgrade tool must be installed on Server B.
Take a backup of ERDB from Server B.
Open the C200 to C300 Transform Configuration tool from Server B, and ensure that the
primary server of the cluster that is upgraded is selected.
Confirm that the ERDB backup is performed, and then select the Task Completed check box
and click Next.
Clear all the Controllers and select the Controller which you need to upgrade.
Enter the odd device index. For example, 65.
Enter the following details in the C300 Exchange Block Path Update dialog box.
Enter the new Exchange block path in the New Value text box for the Exchange blocks if the
exchange blocks are available.
Enter the PCDI details if SIM is available.

Click Transform.
After the Transform is successful, you can click Generate Report to view the
Transform Configuration Summary Report.
Confirm FTE connection from C300 CF9 to the L2 switch.
- 133 -
Task Done?
Log on to the Server B with local and administrator privileges.
From Server B, right-click the executable file setup.exe, and then click Run as
Administrator.
Enter the password and follow on-screen instructions.
Verify if all the modules are correct and only module which is not configured is the CNI cards.
Verify the correct firmware versions in the CTools.
Click Next.
Verify that there are no C200 blockers detected, and then click Proceed.
Verify if the ERDB backup is previously taken and C200 to C300 transformation is complete.
Select the Task Completed check box and then click Proceed.
Power OFF the backup C200.
Disconnect IOLINK from the backup C200 and connect to the secondary C300.
Verify if the primary C300 is not powered ON.
Verify if the IOLINK is disconnected from the primary C300.
Power ON the secondary C300 only.
Verify the view of C300 in the FTE status and the device index. For example, 66.
Verify if FTEB is inserted to the Series A chassis, if Series A is available.
Click Proceed.
Click Load Firmware to flash the latest firmware to the C300 controller.
Click Proceed to rebuild checkpoints of the controller.
Select I am aware of the impact message and click Proceed.
At this point Operations are limited to the Console Station only.

Click Proceed to Transfer Control from C200 to C300.
Click Continue and verify if the latest C200 controller checkpoint is selected (optional).
In the Select C300 startup type list, select the startup type and click Continue.
Verify if the view to controller checkpoint is restored from a flex station.
Verify if the view to controller checkpoint is restored from a console station.
Click Proceed.
Power OFF the primary C200 rack.
Disconnect the primary C200 IOLINK.
Connect the primary C300 IOLINK.
Power ON the primary C300.
Verify the FTE status of the primary C300 and the device index. For example, 65.
Confirm Complete.
Open the Control Builder and in the Monitoring View, click the controller, then right click and
select Upload and Update to Project with contents.
Perform the rebuild and checkpoint save for the controller.
- 134 -
2.14 Appendix D SCADA configuration

See the following sections in the Server and Client Configuration Guide, for the high- level planning and
design topics for SCADA configuration.
l Configuring SCADA controllers — This section provides information for configuring SCADA
controllers.
l Points — This section provides an overview of the different types of points you can configure and
how they can be used.
- 135 -
CHAPTER
3 C200/C200E CONTROLLER TO THE UOC

CONTROLLER
3.1 Introduction

3.1.2 Licensing information 137
3.1.4 Understand the difference between C200/C200E and UOC 139


This section provides detailed information for planning and executing the migration from the
C200/C200E Controller to the UOC Controller. The migration involves upgrading the hardware,
network, and software required for the existing C200 system to work with the UOC controller.
The C200/C200E Controller to UOC Controller upgrade is only supported for releases R511.2 and
later.
While the C200/C200E Controller and its power supply and cabling will be physically removed and
replaced with the UOC controller, the existing Series A I/Os will remain untouched. However, by using
the C200 Upgrade Tool, you must perform the following upgrades.
Upgrade what Using this tool

Upgrade the network from CNET to FTE CNET to FTE Upgrade Tool
Upgrade the existing C200/C200E firmware to a minimum of Controller Migration Wizard /
EXP311.2-12.901 or later NTools
Upgrade Series A I/Os firmware to the latest Ntools
Upgrade the controller and I/O modules l Server and Controller Upgrade
Readiness Checks
l C200 Upgrade Tool Transform
Configuration
l C200 Upgrade Tool
The migration from C200/C200E to UOC can only be done off-process.

An off-process upgrade is the one wherein a Loss of View (LOV) and Loss of Control (LOC) occurs
during the upgrade. Hence, during the C200 upgrade, the C200 Controller must be powered off and
removed first, and then the UOC Controller is mounted, powered up, loaded, and the strategies are
loaded again.
The readiness checks and the upgrade tools enable you to understand the readiness of the system,
and helps to upgrade the C200/C200E to UOC when it is connected to Series A.
- 136 -
Chapter 3 - C200/C200E Controller to the UOC Controller
The users performing the C200 upgrade with MODBUS communication through Serial Interface Module
are provided with an option to convert their MODBUS communication through PCDI.
The users performing the C200 upgrade with Exchange communication are provided with an option to
change all the Exchange communication paths by the tool.
3.1.1 Hardware upgrade

As part of the C200/C200E to UOC upgrade, the control hardware is modified and involves the
following tasks at a high level.
1. Changing the Experion Process Network (EPN) from ControlNet to FTE topology.
This is required only if the C200/C200E Controllers are communicating to the Experion server over
ControlNet.
2. Changing the remote chassis communication interface from ControlNet to EthernetIP. This is
applicable only if the EIP Direct topology is chosen as the target UOC topology.
3. Setting up the EIP-ControlNet bridge using 1756-EN2TR, 1756-RM2 and 1756-CN2R modules.
This is applicable only if the CNET Pass-through topology is chosen as the target UOC topology.
4. Replacing the C200 Controller with UOC Controller and establishing the downlink I/O network for
the UOC Controller. The different actions to be taken during the Migration workflow will be
intimated through the C200 Upgrade Tool at the appropriate time. To save time, you can complete
the tasks like configuring the modules, laying cables and keeping the hardware ready before using
the C200 Upgrade Tool.
See section"Topology" on page 140 to know about the different target topologies supported by
UOC. Also, see the documents listed in the section "Related documents" on page 8 to
configure the ControlNet Bridge module, EthernetIP interface module, and to establish
redundancy on the EIP-ControlNet Bridge.
Before using the received ControlEdge hardware, you should first flash it to a UOC controller
using the Firmware Manager Tool.
3.1.2 Licensing information

For every C200/C200E that you want to upgrade, a UOC control solver license is required. You cannot
proceed with the C200/C200E to UOC controller upgrade if you do not have sufficient UOC control
solver licenses.
After procuring the license, update the license key to replace the C200/C200E control solver license
with the UOC control solver license.
Perform the following steps to update the license.
1. From the Configuration Studio, select the server name in the network tree.
2. From the Server Tasks group, select Change or compare license.
3. Select the license file and select OK.
4. Select Apply.
The licensing scheme of UOC is different from C200/C200E. In addition to the UOC Control Solver
license, you need to evaluate the number of I/O point license required based on the number C200
process points (one process point in C200 corresponds to one I/O point license for Analog/Digital
points). In addition to this, you need to evaluate the number of composite point license for UOC based
on the Exchange blocks configured for third-party connection. For more details, contact Honeywell TAC
team.
No license is required for the C200 Upgrade Tool.
The following table lists the model numbers applicable for the off-process upgrade.
- 137 -
Model numbers Description

EP-UPUOC1 UOC Upgrade fee for non-SESP within release
TC-SWCS90 ControlEdge UOC Process Solver
ES-ANLG50 50 Analog I/O Point Adder
ES-DISC50 50 Discrete I/O Point Adder
ES-AIO100 100 Analog I/O Point Adder
ES-DIO100 100 Discrete I/O Point Adder
ES-DEV010 10 Composite Device Adder
ES-DEV100 100 Composite Device Adder

The following table describes the scope and limitations of the upgrade.
Hardware Configuration Tool

Support C200/C200E with l User has l CNET to FTE Upgrade
ed chosen to
l RM l Server and Controller
perform off-
Upgrade Readiness
l FTEB process
Checks
l SIM with Serial/PLC devices l C200/C200
l C200 Upgrade Transform
(the support depends on the E Controller
Configuration Tool
Experion release, therefore, has a
contact Migration COE Communica l C200 Upgrade Tool
(LSS.Migration.COE@honeywel tion error*
l.com) for complete details) l C200/C200
l Series A I/Os (only specific I/Os E with 50
are supported). Contact ms CEE
Migration COE personality
(LSS.Migration.COE@honeywel
l.com) to check the support for
the specific I/Os.
l Rockwell equivalent of Series A
I/Os (contact Migration COE
(LSS.Migration.COE@honeywel
l.com) to check the support for
the specific I/Os)
l Series H I/Os (contact Migration

COE
(LSS.Migration.COE@honeywe
ll.com) to check the support for
the specific I/Os).
To be supported in upcoming
release R511.x .
Not LIOM and any other chassis-based C200/C200E Contact Migration COE
supporte modules. other than the (LSS.Migration.COE@honeywell.
d one having 50 com)
l PM I/O modules ms CEE
l IOLIM personality
l FIM2
*The C200 Upgrade Tool reports a communication error under the following conditions:
- 138 -
l Controller is in Project view only.
l Controller is in Monitoring view but in fail (crash) state (in red color).
3.1.4 Understand the difference between C200/C200E and UOC

To know more about UOC and its functions, see the ControlEdge UOC Specifications document
available on the Honeywell Process Solutions website http://www.honeywellprocess.com.
Upgrade third-party modules/interfaces connected to C200/C200E
To continue using the third-party devices connected to C200/C200E Controller through Series A SIM,
use PCDI or SCADA. TCP to Serial Gateway hardware may be required for SIM with PCDI.
Any interfacing done with third-party devices through Exchange communication on C200/C200E
Controller downlink network will have to be re-routed through the UOC uplink network. The C200
Upgrade Transform Configuration Tool provides an option to change the Exchange communication
paths during the upgrade process.
3.1.5 Interoperability requirements

In a multi C200/C200E system where there could be peer-to-peer connections across the C200
Controllers. In such cases, the C200 controller firmware should be upgraded to a minimum of
EXP311.2-12.901 to maintain the peer communication between the new UOC Controller and its peer
C200 Controller.
For more details on migration of C200/C200E controllers, contact Migration COE
([email protected]).
3.1.6 User Privilege requirements

To install the C200 Upgrade Tool, you must be a member of the Windows Administrator group. To
perform the upgrade you must be a member of the Local Engineers group.
3.2 Plan the C200/C200E to UOC Upgrade
3.2.1 Topology 140

3.2.4 Security Considerations 144
3.2.5 UOC Hardware Installation 144

There are no detailed procedures for performing an off-process upgrade without using the tool since it
is a site-specific activity and there is no formal process for the same.
Upgrading the C200/C200E to UOC involves the following readiness check.
- 139 -
Task Input and Output Tool

Data Format
To perform migration from The Input/Output Without Configuration tool change in
C200/C200E to UOC with data format is Control builder mapping.
1738AB and Truck devices. configured as byte.
To perform migration from The Input/Output With SST configuration tool change and
C200/C200E to UOC with data format is the offset changes to be modified in
Anybus devices. configured as word. Control builder mapping.
3.2.1 Topology
The C200/C200E to UOC migration supports three different topologies, EIP Direct, EIP-CNET Bridge,
and Hybrid topology.
For more details, see section "Prepare Controller Hardware for Upgrade" on page 175.
EIP Direct Topology
The following topology diagram is an example of an upgrade from a redundant C200 controller with
Series A I/Os on CNet upgraded to UOC Controller with all remote chassis communication on
EthernetIP.
EIP-CNET Bridge Topology
The following topology diagram is an example of an upgrade from a redundant C200 controller with
Series A I/Os on CNet upgraded to UOC Controller with remote chassis communicating on ControlNet
through a EIP-CNet bridge.
- 140 -
Hybrid Topology
The following topology diagram is an example of an upgrade of a redundant C200 controller with
Series A I/Os on CNet to UOC Controller with remote chassis communicating on EthernetIP as well as
one chassis residing on ControlNet segment.
- 141 -
3.2.2 Planning considerations

Planning for an upgrade involves the following high-level tasks.
Task Details
Assess your site l Identify the C200/C200E Controller with Series A I/Os that you want to
requirements upgrade.
l The C200/C200E to UOC upgrade is an off-process upgrade where there
is a LOV/LOC of the controller that is being upgraded during the upgrade
process.
l If the C200/C200E that is being upgraded has peer connections with other
controllers, those peer connections will be disrupted during the upgrade
process. The Readiness check tool helps in identifying the peer
connections.
l In a multi C200/C200E system where there could be peer-to-peer
connections across C200 Controllers. In such cases, the C200 controller
firmware should be migrated to a minimum of EXP311.2-12.901 or later to
maintain the peer communication between the new UOC Controller and its
peer C200 Controller.
l In a multi-cluster system with Exchange peer connections across the
clusters, the Exchange path in other clusters should be modified and
loaded post the controller upgrade to re-establish the exchange peer
connection. The list of strategies can be identified using the readiness
check tool.
l Meet the prerequisites and understand the assumptions for this upgrade.
Before starting the C200 /C200E to UOC migration, make a list of the
inactive and non-loaded CMs/SCMs so that those CMs can be left in the
same state after the migration.
The C200 Controller upgrade must be performed manually in all the

following conditions: -C200/C200E without I/Os configured. -C200/C200E
with peer connections with other controllers and without I/Os configured. -
C200/C200E with exchange strategies and without I/Os configured.
See section Prerequisites and assumptions.
Understand the If you are not familiar with the Unit Operations Controller and Ethernet/IP, it is
between
l See the Ethernet IP Implementation Guide to understand the different I/O
C200/C200E and
UOC network configurations supported.
l See the UOC User's Guide and UOC Specifications.
l The various Series A I/O support on UOC is being provided in a staggered
manner through multiple Experion releases. The migration project
approval process involving Migration COE will ensure that the support of
I/Os are assessed.
Familiarize with The off-process upgrade with the upgrade tool involves a combination of
the upgrade hardware and software upgrade steps to be performed. Therefore, it is
process and the important to familiarize yourself with the process and tools before the upgrade.
tools required for
l Familiarize yourself with the C200 Upgrade Tool set and its features,
the same.
restrictions and prerequisites.
l Familiarize yourself with the new Unit Operations Controller by using the
UOC User's Guide.
l Familiarize yourself with the Ethernet IP protocol and the different I/O
downlink network supported by UOC by using Ethernet IP User's Guide.
Familiarize See section “Upgrade tool workflow.
- 142 -
Task Details
yourself with the
upgrade workflow.
3.2.3 Prerequisites and assumptions

Before you proceed with the upgrade, understand, and meet the following prerequisites:
l C200/C200E to UOC upgrade is an off-process upgrade where there will be LOV/LOC.
l Using the C200 Upgrade Tool, the C200/C200E Controller can be migrated to UOC Controller that
can communicate to Series A I/Os either directly to Ethernet IP or through ControlNet Bridge
configuration. The Controller-I/O connections should match the configurations entered in the C200
Upgrade Tool.
l Since the C200 Upgrade Tool works on specific Experion releases only, you should contact
Migration COE ([email protected]) to ensure that your current Experion system
supports the C200 Upgrade Tool.
l A system with multiple C200 Controllers should upgrade their C200 firmware to a minimum of
EXP311.2-12.901 or later, in order to maintain peer-to-peer communication with newly upgraded
UOC controllers.
l If the system contains LIOM, FIM/PMIOs, then C200 cannot be migrated to UOC. If you intend to use
PGM, then you should not upgrade the C200 to UOC. In such cases, contact Migration COE for
appropriate solution.
l If the C200 Controllers have CCLs, then contact Migration COE to ensure the CCLs are supported
on UOC Controller.
To identify the CCLs present in C200, open Control Builder > CEE property page > Block Type Info
tab and scroll down the table to see the list of CCLs configured.
l Once the C200 Controller is upgraded to UOC Controller, you cannot upgrade the Series A I/O
firmware without using additional FTEB hardware. Hence, it is recommended to do any firmware
upgrade of the I/O modules prior to commencing the C200 to UOC upgrade.
The Series A I/Os that will be configured under UOC can have any version which is interoperable
with the current C200 Controller. However, it is recommended to have the I/O modules in the latest
firmware available with the Experion Server.
l The support for various Series A I/Os (both chassis and rail) with UOC are introduced in phases
through different Experion releases. To know all the Series A I/Os that are configured with C200 that
is to be upgraded, contact the Migration COE.
l Ensure that there are no checkpoint operations being performed on the server while C200 upgrade
is in progress. If there are Auto checkpoints scheduled, then disable them before proceeding with
C200 upgrade on the cluster.
l In a multi-cluster environment with Exchange communication across clusters, the Network model
has to be configured in Configuration studio to identify the Exchange blocks that are configured in
other clusters that are communicating to the Controller being upgraded.
Few more general points to be taken care:

l Ensure that the prerequisites of UOC and the Ethernet IP network are taken care by referring to the
UOC User's Guide and Ethernet IP User's Guide.
l Adhere to the guidelines to be followed before and after installing the UOC and the Ethernet IP
components.
l The Experion Upgrade Tool must not be in use when the C200 Upgrade Tool is in use .
- 143 -
3.2.4 Security Considerations

For more information about the planning and design activities of UOC and vUOC, see the Experion
Network and Security Planning Guide and UOC User's Guide.
3.2.5 UOC Hardware Installation

Information Guide to refer
UOC specifications, power requirements, mounting Unit Operations Controller Specifications
options, etc. Guide
Wiring and configuration of the I/O network for the UOC Ethernet IP User's Guide
controller
3.2.6 Site requirements

Ensure to follow all the checklist points before ordering any Experion components for migrating
C200/C200E modules to the UOC system.
- 144 -

Determine the Identify the modules that are
C200/C200E configured with the controller
Controllers and being upgraded.
Series A chassis
that need to be Identify the C200/C200E
Controller that needs to be
upgraded
migrated. Determine the UOC
downlink network type that needs
to be migrated to. For example,
the Series A I/Os can be
connected to UOC through the
EIP direct and the EIP CNET-
bridge topologies. See section
""Topology" on page 140" and the
EthernetIP User's Guide for more
details. Assess the peer
connections and possible impact
of upgrade and peer connection
disruption to the process.
Determine the order in which the
controllers need to be upgraded
in a multi-controller environment.
Determine the Migrate the control system to Server Upgrade Readiness Checks.
upgrade readiness Experion R511.2 or later and
of the control ensure the controllers are running
system at a release that meets the
interoperability requirements.
Install and use the C200 Upgrade
Tool to perform readiness checks
on the control system. Readiness
checks help in planning the
upgrade. Performing the
readiness checks helps in
understanding the impact on the
process and control loops.
Procure the Procure the hardware required for UOC User's Guide
hardware and the upgrade and determine the
determine how space to mount them and plan for Ethernet IP User's Guide
you want to mount it. See section "Licensing information" on
page 137.
Depending on the I/O network
chosen and the controller
configuration, the hardware to be
procured might include the UOC
Controller and its associated
components, Rockwell branded
interfacing modules like 1756-
EN2TR, 1756-RM2, 1756-CN2R,
network witches, cables etc.
Also remember to order for
licenses related to the upgrade.
Download and The C200 Upgrade Tool is the
install the C200 starting point for the upgrade.
Upgrade Tool Install the tool on Server B in an
Experion cluster for readiness
checks and actual upgrade. Install
the C200 Upgrade Tool on Server
A for CNET to FTE Upgrade only.
- 145 -

The C200 Upgrade Tool is
internal to Honeywell. It can be
downloaded and installed only by
Honeywell field personnel.
Determine if the One of the prerequisites for an
servers are upgrade is that the Servers must
already on FTE already be on FTE topology. If
topology they are not, procure the
necessary FTE hardware, install,
and upgrade your Supervisory
Networks to FTE topology.
Contact Honeywell TAC on how to
upgrade your Supervisory
Networks to FTE.
Determine your If the control system is not on the
current Experion required Experion release for
release performing the upgrade, migrate
the control system to the required
release.
Decide the plan If the third-party See section "Upgrade third-party
for upgrading devices/interfaces are connected modules/interfaces connected to
third-party to C200/C200E, then you may C200/C200E" on page 139.
devices/interfaces want to see the UOC
connected to your Specifications document and
C200/C200E determine if they are supported
Controller on UOC as well.
If third-party devices/interfaces
are not supported on UOC,
contact Honeywell TAC on how to
proceed with the upgrade.
Determine how During the upgrade, controller is
long can loss of not available. Therefore, it is
redundancy be important to be aware of the
tolerated LOV/LOC and determine how
long the loss can be tolerated.
Configure the Configure the 1756-EN2TR, ControlLogix Enhanced Redundancy System
1756 Modules 1756-RM2 & 1756-CN2R Release Notes
Modules and establish
Ethernet/IP Network Devices User Manual
redundancy of the EIP-ControlNet
Bridge. ControlNet Configuration User Manual
See section Configuring 1756 All these documents are available at
modules. Rockwell website
Redundancy Configuration Tool
The time required for an upgrade is configuration-specific.
3.2.7 Upgrade tool workflow

At a high-level, the upgrade activity can be classified into two separate high-level tasks as network
upgrade and controller upgrade. These are two different stages of your upgrade and you can always
stop at network upgrade and plan your controller upgrade at a later time.
- 146 -
l Network upgrade — This is for upgrading the communication between the C200/C200E Controller
and the server from ControlNet to FTE. This upgrade can be done for all the C200/C200E
Controllers in an Experion cluster at once.
l Controller upgrade — This is about upgrading the C200/C200E Controller with Series A I/Os to
UOC Controller. This upgrade must be performed for one controller at a time.
Therefore, plan the network upgrade and controller upgrade as separate activities. If the C200/C200E
Controllers are already on FTE, skip the network upgrade tasks.
The following figure displays the workflow diagram for an upgrade:
3.3 Install the C200 Upgrade Tool
3.3.1 C200 Upgrade Tool components 148

The C200 Upgrade Tool is used to perform an off-process upgrade in a phased manner. Both the
hardware and the software upgrade steps must be performed in a combined sequence. At each step,
the tool prompts the action to be taken and provides workaround for any issues. In an Experion cluster,
install and use the C200 Upgrade Tool on Server B.
To upgrade Server A process network to FTE, install the tool on Server A also. For more information,
see section "Upgrading the Experion Process Network to FTE" on page 167.
To install the C200 Upgrade Tool on Experion Server B, perform the following steps:
1. In a web browser, type the following URL:
https://honeywellprod.sharepoint.com/teams/GPOEngTools/Lists/MasterList/DispForm.aspx?ID=33
1. The Global Project Operation (GPO) Engineering Tools team room page appears.
This website is applicable only for Honeywell internal users.
- 147 -
2. Download the C200 Upgrade Tool installer for Experion R5xx.x.zip file.
3. Copy the file to a temporary folder on the Experion server.
4. Extract the C200 Upgrade Tool installer for R5xx.x.zip file in the C:\temp path.
5. Right-click the executable file Setup.exe, and then select Run as Administrator. The User Account
Control dialog box is displayed.
6. Follow user-screen prompts to complete the installation.
7. After successful installation, select Finish.
By default, the C200 Upgrade tool is installed in C:\Program Files (x86)\Honeywell\Experion

PKS\C200toC300UpgradeTool. For custom installation path, navigate to <User selected
path>\Honeywell\Experion PKS\C200toC300UpgradeTool.
3.3.1 C200 Upgrade Tool components

The C200 Upgrade Tool folder consists of four tools, classified based on the four stages of the upgrade.
Launch each tool in the same order as listed in the following table. For each stage, either double-click
the component to launch the tool or launch it directly through Start menu.
Ensure that all the instances of Control Builder are closed while using CNET to FTE Upgrade Tool,
C200 Upgrade Transform Configuration Tool, and C200 Upgrade Tool.
Tool Purpose
Server and Controller Upgrade To perform all the readiness checks on the C200/C200E modules
Readiness Checks before starting the upgrade tool.
CNET to FTE Upgrade To upgrade the Experion Process Network from CNET to FTE.
C200 Upgrade Transform To replicate the C200/C200E control strategies in UOC.

Configuration Tool
C200 Upgrade Tool To upgrade the controller from C200/C200E to UOC.
Although the C200 Upgrade Tool is the starting point for the upgrade activity, some tasks must be
performed either manually or by using other Experion engineering tools (for example, Control Builder,
DBAdmin, and ERDB Consistency Checker (ECC)) at every stage. For example, after you run the
readiness checks, depending on the failure, you may need to complete the workaround manually and
repeat the readiness checks. In addition, all the hardware upgrade tasks must be performed manually
whenever prompted. For C200/C200E to UOC, user shall manually load the upgraded configurations to
monitoring.
3.4 Readiness Checks
3.4.1 Checking for ERDB inconsistencies 148

3.4.3 Types of Readiness Checks 149
3.4.1 Checking for ERDB inconsistencies

Before you start the readiness checks, ensure that there are no consistency issues with ERDB. To
ensure this, use the ERDB Consistency Checker (ECC) tool and resolve any consistency issues.
- 148 -
You can download the tool from the Honeywell Process Solutions website
http://www.honeywellprocess.com. For more information on downloading and using the tool, see
Experion PKS Upgrade Tool User's Guide .
3.4.2 Ensure ERDB is not fragmented

To ensure that the ERDB is not fragmented, perform the following:
1. Choose Start > All Programs > Honeywell > Experion PKS > Configuration Studio.
The Connect dialog box is displayed.
2. Select a listed system and then click Connect.
Strategies section.
8. Expand the Server Node item, and click ERDB Admin Tasks.
9. Click Update Statistics.

10. Click Yes. The indexes are rebuilt and the statistics are updated.
3.4.3 Types of Readiness Checks

Preparing for an upgrade involves verifying the readiness of servers, controllers, and the network.
You must complete the readiness checks before starting the upgrade as it helps to determine the impact
on your process and control loops. If the checks fail, complete the workaround as indicated in the tool
and repeat the readiness checks until you succeed.
Use the C200 Upgrade Tool from Server B to perform these checks.
Do not proceed with the upgrade until all readiness checks are completed successfully.
Perform the following four readiness checks using the C200 Upgrade Tool:
- 149 -
Readiness Check Type Description

C200/C200E To UOC Server Readiness To perform both server and controller readiness checks.
Check
See section C200/C200E To UOC Server Readiness
Checks.
CNET to FTE readiness checks To perform only CNET to FTE readiness checks.
See section CNET to FTE readiness checks.

C200/C200E to UOC readiness checks To perform only controller readiness checks.
See section C200/C200E To UOC Readiness Checks.
The different kinds of checks are categorized as follows:
Readiness Description
Check Type
Blocker This readiness check must be completed successfully before proceeding with the
upgrade.
Warning If this check fails, then you may proceed with the upgrade but it is recommended to
fix the check before proceeding with the upgrade.
Manual This check is performed manually. It is recommended to complete these checks
successfully before proceeding with the upgrade.
The status of all the checks could be one of the following:

l Pass
l Warning
l Fail
l Not Applicable
l Not Executed
l Abort
C200/C200E To UOC Server Readiness Checks
The Server Upgrade Readiness Checks screen displays the list of readiness checks to be performed on
the selected nodes and modules. This readiness check covers both the servers and controllers.
List of Server Readiness Checks
The following tables lists the server readiness checks that must be completed successfully before
proceeding with the upgrade.

Blockers Is Server at the supported Upgrade the Server to the supported point release of
main release? Experion if the Server is not already upgraded.
Is the Server connected to Upgrade the servers to the FTE topology if they are not on
Experion Supervisory the FTE topology.
Network nodes (ACE,
Server, and Flex) via FTE?
CNET on Experion Process through FTE, you can skip the CNET to FTE Upgrade and
Network? proceed with controller upgrade.
- 150 -

Are there any unsupported If there are any unsupported modules, disconnect the
modules/firmware? modules and delete modules and the strategies associated
with those modules. If there are any modules with
unsupported firmware versions, upgrade the firmware
compatible with the necessary Experion release.
Are there any active locks? Run DBAdmin tool from the configuration studio.
Verify that there are no active locks in ERDB, EMDB.
Controllers/RM/IOLIM/FIM missing. If so, click Execute to update the backup name.
with backup name missing?
Are there any QVCS This check lists the strategies which are in checked-out
elements in checked-out state. If any strategies are found in the checked-out state,
state? perform Check-in before proceeding with the Upgrade.
Are there any redundant The secondary modules should have the default name
Controllers/RM/IOLIM syntax (For example, Secondary module name as CPM200_
without default secondary 20SEC for a Primary module with name CPM200_20)
name?
Perform server readiness checks
This section describes how to perform server and controller readiness checks and also describes the
tool's General Information and General Data Collection screens.
In the Server and Controller Upgrade Readiness Checks Tool, you cannot change the readiness
checks type if you are in General Data Collection screen or Readiness Checks screen. You must close
the Server and Controller Upgrade Readiness Checks Tool and open the tool again. If the Server is
connected through FTE on the Experion process network, then the readiness check "Is Server
connected via CNET on Experion Process Network" fails.
The Sever readiness checklist includes CNET to FTE readiness checks and C200/C200E to UOC
readiness checks.
To perform server readiness checks, do the following:
3. In the Provide User Credential dialog box, type the password and click OK.
The General Information screen appears.
4. From the Readiness Check Type list, select C200/C200E To UOC Server Readiness Check and
click Next.
- 151 -
The General Data Collection screen appears. This screen provides information about all the
configured modules in chassis.
node or a chassis to view the details in the right data pane. Select the check box next to each
node(s) or chassis to perform the tasks on. The L1 and L2 nodes (Server B or standalone
server of local machine) are selected by default and appear disabled.
l The data pane on the right displays system configuration information of the selected chassis
that contains Slot Number, Module Name, Module Type, Base Period, Application Firmware
Version, Boot Firmware Version, Module Status.
CommFail: Communication failure indicates that the tool is unable to communicate to the
module on the network. This condition could arise due to multiple reasons, such as:
l Actual module is not available on the network but available on the Project or Monitoring
side in Control Builder.
l The module is not loaded on to the Monitoring side in the Control Builder.
lThe module is available on the network, but in Power Off / Shut Down condition or has
failed to respond.
However, the off-process migration should work for the module with a Communication failure.
5. Click Next.
The Add Computer dialog box appears.
6. From the list of servers that appear, select the primary server that has exchange peer-to-peer
connections with this cluster and then click OK.
The Readiness Checks screen appears.
7. Select the applicable nodes and modules. All the nodes/modules are selected by default.
in the left navigation pane. By default, all the readiness checks are selected for each node/module.
By default, the servers and chassis readiness checks are not performed and the status for server
and chassis is Not Executed.
- 152 -
status of the readiness checks for each node is displayed in the navigation pane. You can select a
node in the navigation pane to view the status of the individual readiness check in the right pane.
To perform a readiness check, you can either run for all the nodes at once or for one or more nodes
at a time.
To run for all nodes at once, select the Start button.
To run for one or more nodes, select the node from the left navigation pane and click the Run
Checks button in the top-right pane.
Once the readiness check completes, the status bar will show the completion status, and the
Start button will appear.
10. Click the hyperlink provided for each readiness check in the Status column. A pop-up window
appears describing the result of the status. The server readiness check starts and status of each
readiness check is displayed in the right pane.
Use the Filter option to sort the readiness checks based on their status — Pass, Fail, Warning,
None, Not Applicable, Not Executed.
11. You can click Generate Report and save the list of readiness checks along with their execution
status in html format.
Even if you use a filter to sort the readiness checks, while generating a report all readiness checks that
have been selected regardless of their execution status are included in the report.
CNET to FTE readiness checks must be performed to assess your Experion Process Network readiness
for upgrading to FTE.
If the servers are connected to the Experion Process Network through CNET, then the check "Are the
servers connected to the Experion Process Network through FTE" fails.
- 153 -
List of CNET to FTE Readiness Checks

Blockers Is Server at the Upgrade the Server to the supported point release of Experion if
supported main the Server is not already upgraded.
release?
Is the Server connected Upgrade the servers to the FTE topology if they are not on the
to Experion Supervisory FTE topology.
Network nodes (ACE,
Server, and Flex) via
FTE?
CNET on Experion through FTE, you can skip the CNET to FTE Upgrade and
Process Network? proceed with controller upgrade.
Are there any IOLIMs Ensure that IOLIMs reside in the C200/C200E chassis only.
residing in Chassis
independent of C200?
Are there any If there are any unsupported modules, disconnect the modules
unsupported and delete modules and the strategies associated with those
modules/firmware? modules. If there are any modules with unsupported firmware
versions, upgrade the firmware compatible with the necessary
Experion release.
Are there any Interface If there are any interface modules connected to the Experion
modules (such as Process Network, identify if they are supported on UOC also and
LIOM) connected to upgrade accordingly.
Experion Process
Network?
Are there any active Run DBAdmin tool from the configuration studio.
locks?
Verify that there are no active locks in ERDB, EMDB databases.
Are there any QVCS Ensure that there are no elements in checked-out state in QVCS.
elements in checked-
out state?
Controllers/RM/IOLIM missing. If so, click Execute to update the backup name.
with backup name
missing?
Warning Is BootP Server The BOOTP Server service must be enabled and running on one
configured properly? of the server cluster pairs.
Manual Please ensure that Ensure that the empty slot is available in the server.
required empty slot is
available
Perform CNET to FTE readiness checks
To perform CNET to FTE readiness checks, do the following:
- 154 -
3. In the Provide User Credential dialog box, type the Password and click OK.
4. From the Readiness Check Type list, select CNET to FTE Readiness Check and click Next.
5. Click Next.
6. From the list of servers that appear, select the primary server that has exchange peer-to-peer
connections with this cluster and then click OK.
7. Select the applicable nodes and modules. All the nodes/modules are selected by default.
node/module. The chassis readiness checks and Supervisory FIM2 readiness checks are not
performed and the status for server and chassis is Not Executed.
- 155 -
9. Click Start to perform the readiness checks for the selected nodes/modules. The overall status of
the readiness checks for each node is displayed in the node tree. You can select a node in the
Navigation pane to view the status of the individual readiness checks in the data pane. While the
readiness check is in progress, the Stop button will appear next to the status bar.
10. Click the hyperlink provided for each readiness check in the Status column.
C200/C200E To UOC Readiness Checks
Ensure to close the Experion Upgrade Tool before starting the C200 Upgrade Tool.
List of C200/C200E to UOC Readiness Checks

if
Readiness Checks Description/Workaround FIM is There
present is a
Comm
Error
Blockers Is Server connected to Connect the Server to Experion Process
Experion Process Network through FTE.
Network via FTE?
Is base period of C200 Ensure that the base period configured for
configured for value C200 is 50ms.
other than 50ms?
Are there any Delete the associated strategies from Control NA
unsupported Builder and disconnect the modules before the
modules/firmware? upgrade.
If there are any modules with unsupported
firmware versions upgrade the firmware
compatible with the necessary Experion
release.
If there are Rockwell branded 1756 series IO
(as a standard equivalent to the Series A IO as
prescribed by Honeywell) in the rack, they will
be flagged as in unsupported firmware. Please
- 156 -

if
ignore this.
Are there function blocks Delete the function blocks manually from the
currently loaded to the Monitoring view and unassigned from Project
C200 that are not view.
supported in UOC?
Are there any strategies/ This check lists the strategies outside this
IO outside this C200 that C200 that has reference to I/Os connected to
has reference to this C200. Update the references to the I/Os
IO/strategies of this connected to the C200 and reload them.
C200?
Are there any redundant Ensures that controller/RM/IOLIM have a
Controllers/RM/IOLIM default backup name. If it is missing, the check
without default executes. Click Execute to update the backup
secondary name? name.
Ensure to reload the secondary module to
Monitoring View.
Are there any QVCS This check lists the strategies which are in
elements in checked-out checked-out state. If any strategies are found
state? in the checked-out state, perform Check-in
before proceeding with the Upgrade.
Are there any If your C200/C200E have LIOM, FIM, IOLIM or
unsupported modules PMIO, they cannot be migrated to UOC.
(such as Please contact Migration COE for an
LIOM/FIM/IOLIM/PMIO) appropriate solution.
present?
Warning Is Peer Control Data Checks for the PCDI licenses available.
Interface license
available for all SIM If the system is not licensed to use PCDI, then
ensure that you do not select the SIM to PCDI
being upgraded?
conversion check box while running the C200
Upgrade Transform Configuration Tool. If you
select this, the C200 to UOC upgrade will be
interrupted at a later stage.
This check is not applicable for C200 to UOC
upgrade as the UOC Controller uses
composite-point license for PCDI.
Are there any strategies This check lists the strategies in other
in other Controllers Controllers containing peer connections to the
initiating peer C200 Controller been upgraded.
connections to this
C200?
C200?
Are there any strategies This check lists the strategies that are peer
in other Controllers with referenced to the parameters on this C200
peer references to block.
parameters on this C200
block?
Are there any strategies Delete the references to the parameters that
with references to do not work after the upgrade.
- 157 -

if
parameters on the C200
or CEE blocks that won’t
work after the upgrade?
Are there any strategies Exchange block paths must be updated before
initiating Exchange peer the upgrade.
C200?
Are there any strategies This check list the strategies in other
in other Controllers Controllers containing the exchange peer
initiating Exchange peer connections to the C200 Controller being
connections to this upgraded. Update the Exchange block path
C200? before the upgrade in the Project side and
then the tool loads the updated strategies.
Are there any strategies This check lists the strategies assigned to the
in other Controllers (in Controllers (in other Servers) initiating
other Servers) initiating exchange peer connections to the upgrading
Exchange peer C200 Controller. Update the Exchange block
connections to this path before the upgrade in the project side
C200? and then the tool loads the updated strategies.
If the status shows that the Experion server is

“Not connected” then this is because the
servers are in two different Experion releases,
and this check is not able to identify the
Exchange strategies. See section “Updating
and loading the Exchange blocks in peer
Server” for more information.
Ensure current and peer cluster have the same
login credentials.
Are there any peer Delete such peer references from the
references to the Monitoring view of Control Builder and reload
secondary blocks? them after the upgrade.
Are there any In Control Builder, right-click the controller and NA
ghost/inconsistent select the Identify ERDB/ Controller
modules in the inconsistency option.
controller?
Is BootP Server The BOOTP Server service must be enabled
configured properly? and running on one of the server cluster pairs.
Are there any strategies This check lists the strategies having
with references to references to parameters on the RM, FTEB,
parameters on the RM, and IOLIM blocks.
FTEB, FIM and IOLIM
blocks?
Are there any Serial This check lists the Serial Interface Modules
Interface Modules and and its corresponding strategies.
Are there any strategies This workaround is applicable only if you plan
with references to to upgrade SIM to PCDI.
parameters on Serial
Interface Module that Delete such references to the parameters
won't work after the from the Monitoring View and reload them
after the upgrade.
upgrade?
- 158 -

if
Are there any strategies You need to upgrade this peer FIM2 to YES
in this C200 initiating FIM4/FIM8 and then perform load operation
peer connections to for these strategies.
FIM2 present in other
This check is applicable only for C300 and not
controller/Supervisory
for UOC.
Chassis?
Are there any Series A This check lists the Serial A Modules and its
Modules and corresponding strategies.
Are there any CCLs in List all the CCL bocks in the C200 controller.
C200?
Are the Series A IOs on List the Series A IOs that are not on the latest
the latest firmware? firmware.
Are the other C200s in Check if the controllers of the cluster have the
the correct firmware? correct firmware to maintain peer-to-peer
connection with UOC.
Perform C200/C200E to UOC server readiness checks
To perform C200/C200E to UOC upgrade readiness checks, do the following:

2. Click Start > Honeywell Experion Tools> All Honeywell Tools. Open the C200 Upgrade Tool folder
3. In the Provide User Credential dialog box, type the Password and click OK.
4. From the Readiness Check Type list, select C200/C200E to UOC Readiness Check and click
Next.
- 159 -
5. Click Next.
6. Select the primary server from other clusters that has exchange peer-to-peer communication with
this controller and then click Add. Based on this selection, the readiness check populates the
strategies containing the exchange peer-to-peer communication. Or, click Cancel.
7. From the left navigation pane, select the server/nodes to run the check on.
A list of checks appears on the right pane.
8. By default, all controller readiness checks are selected. Click Start to run all checks at once.
9. Select the check boxes next to each node to perform the tasks on the selected nodes or chassis.
10. You can also choose to run one or multiple checks on a single server/node. In this case, select the
server/node from the left navigation pane and click the Run Checks button on the top in the right
pane.
11. The checks are run on the selected nodes and status for each check is displayed along with the
time stamp when it was run. The status can be one of these:
l Pass
l Warning
l Fail
l Not Applicable
l Not Executed
l Abort
12. For checks that did not pass, click the hyperlink in the Status column to see a pop-up message with
detailed account of the problem in a tabular format. Additional Detail hyperlinks, when present, can
be clicked to get more information.
- 160 -
13. Click OK to close the message pop-ups.

14. Go to Control Builder and take appropriate action to remedy the cause mentioned by the readiness
Checks tool.
15. Click Run Checks again. If a checks fails, repeat steps 10 through 12 until all checks pass.
16. Click the Generate Report button on top to generate a report of the status of the checks you
performed on all/selected nodes.
You can save this report too. For more information about analyzing the reports, see the next section
"Generating and analyzing readiness check reports" on the facing page
- 161 -
ATTENTION
If the controller is facing a COMM ERROR, some live data may not be available as part of
readiness checks.
3.4.4 Generating and analyzing readiness check reports

You can generate a report for the readiness checks performed. To generate a report, click Generate
Report on the readiness check screen. The readiness check report is used for analyzing the execution
status of the readiness checks with the details. Sample reports for Server readiness check and
Controller readiness check are illustrated. The following table describes the status for readiness checks.
For example, consider that a peer connection exists between two CMs that are assigned to different
controllers. In this case, if you delete one of the CMs from which a peer connection has been made to
another CM, then the strategy is displayed under “Are there any dangling control connections?”
However, if the controller to which the strategy is loaded is deleted from the Monitoring view, then the
strategy is displayed under “Are there any dangling peer connections?”
Status Description Guideline

Pass Indicates that the No action required.
readiness check has
passed.
Fail Indicates that the Perform the recommended work around and repeat the readiness
readiness check has check.
failed.
Aborted Indicates that the Perform the recommended workaround and repeat the check.
readiness check could
not be completed due
to some issues.
Warning Indicates that the Although warnings are not blockers for upgrade, click Details to
readiness check has analyze the problem and perform the work around. However, if
passed with warnings. you proceed with the upgrade without addressing the warnings,
you must address the same after the upgrade is complete.
Manual Indicates that the
readiness checks have
to be manually
performed before the
upgrade.
- 162 -
The reports are in HTML format and can be opened using a web browser preferably, Internet Explorer.
3.5 Upgrade the Experion Process Network from CNET to

FTE


Before upgrading C200/C200E modules to UOC modules, the Experion Process Network (EPN) of the
Experion system must have Fault Tolerant Ethernet (FTE) network. If the EPN of the Experion system
has ControlNet (CNET) network, then the CNET to FTE Upgrade is a prerequisite to the C200 to UOC
Upgrade.
After the CNET to FTE upgrade, the Experion Process Network that is Server to Controller
communication is changed from CNET to FTE. The C200 Controllers still continue to use CNET at the
I/O network level. In order to execute the CNET to FTE Upgrade, your Experion System supervisory
network must have FTE network.
For more information, see Experion Network Best Practices Guide . This activity involves the following
high-level tasks:
l “Adding the FTEB module to the controller chassis”
l “Taking a backup of ERDB”
l “Upgrading the Experion Process Network to FTE”
- 163 -
ATTENTION
3.5.1 CNET to FTE upgrade screen

Following is the illustration of CNET to FTE upgrade screen.
CNET to FTE upgrade
The CNET to FTE screen consists of the following:
Add FTEB Modules to Upgrade the Server A from CNET to FTE.
controller chassis
Backup ERDB Take a backup of ERDB using DBAdmin tool.
Upgrade server network The Experion server is upgraded from CNET to FTE network. During this
to FTE upgrade, System Repository and Experion Services (CDA and SAM) are
restarted.
An User Account Control appears when performing Network type change
(from CNET to FTE) and services restart. Please provide Administrator
credentials and click Yes.
Configure FTEB Provide the FTEB name, Device Index, and slot number of FTEB. FTEB
modules and upgrade nodes in database are created and all C200/ C200E are assigned to that
controllers to FTE FTEB.
Connect Server B to At this stage, the following steps must be performed manually.
network
Connect Server B to network.
Command server synchronization from Server A.
Command switch over from Server A.
Power off Server A.

Upgrade Server A from Ensure that you have upgraded Server A from CNET to FTE.
CNET to FTE
Status: Displays the status of each CNET to FTE upgrade step as follows:
- 164 -
l Not Executed
l In Progress
l Executed
l Failed
l Abort
3.5.2 Adding the FTEB module to the controller chassis

Plan and execute this task ahead of your network upgrade activities. In addition, note that the FTEB
modules must be added in all the peer controller chassis across the cluster.
Ensure that C200/C200E and FTEB module are in the same firmware version.
Prerequisites
BootP service must be stopped and disabled on Server B and started and enabled in Server A before
adding the FTEB in the chassis.
Stop BOOTP service on Server B and start it on Server A
1. If multiple BootP services are running, navigate to: C:\Program Files (x86)\Honeywell\Experion
PKS\C200 Upgrade Tool.
2. For custom installation path, navigate to: <User selected path>\Honeywell\Experion PKS\C200
Upgrade Tool.
3. Right-click Bootp_Stop_batch.cmd, and click Run As Administrator. The BOOTP service dialog
Or
Type services.msc in the Run dialog box. The Services dialog box appears.
Update ERDB system preferences
1. To set the base IP address, go to: C:\ Program Files (X86)\Honeywell\Experion PKS\C200 Upgrade
Tool.
2. For custom installation path, navigate to <User selected path>\Honeywell\Experion PKS\C200
Upgrade Tool.
3. Right-click UpdateBaseIP_SubnetMask_Batch.cmd with Local Engineer or Product Administrator
permissions.
4. Enter the Base IP Address and Subnet Mask Address. A confirmation message appears.
5. Click Yes. A message indicating success appears. The Base IP Address and Subnet mask are
updated in ERDB.
6. Start BOOTP service.
In addition, run the BOOTP checker tool after updating the system preferences to verify if there is
only 1 BOOTP Server detected in the network.
Use the following two batch files to start or stop the BOOTP services:
l BootP_Start_Batch — To start the BOOTP service
l BootP_Stop_Batch — To stop the BOOTP service
To run this on Server A and to ensure BOOTP service is running, perform this before adding the FTEBs
in the chassis so that the FTEB gets the correct IP based on the system preferences base IP and the
device index is given to the FTEB.
- 165 -
Start BOOTP service on Server B and start it on Server A
1. Navigate to: C:\Program Files (x86)\Honeywell\Experion PKS\C200 Upgrade Tool .

2. For custom installation path, navigate to: <User selected path>\Honeywell\Experion PKS\C200
Upgrade Tool.
3. Right-click BootP_Start_Batch.cmd, and click Run As Administrator. The BOOTP service dialog
Or
Type services.msc in the Run dialog box. The Services dialog box appears.
Add FTEB module to the redundant controller chassis
1. In the Control Builder Monitoring view, double-click RM.

2. Click the Summary tab.
3. Click Disqualify Secondary. The synchronization of the primary and secondary chassis is disabled.
4. Power-off the secondary chassis.
5. Insert the FTEB module with odd Device Index using the following steps:
location. Remember that slot numbering is zero-based and the left most slot is number "0".
c. Insert the FTE cables properly into the FTEB module, to pick up the base IP from the Server A.
Note down the FTEB slot number for further use during upgrade.
6. Click Enable Synchronization to initiate synchronization and allow auto-synchronization. The
synchronization of primary and secondary chassis is enabled.
8. In the Control Builder Monitoring view, double-click Redundancy Module > Synchronization >
Synchronize Secondary and then click OK.
9. In the Control Builder Monitoring view, click Initiate Switchover after the C200 chassis is
synchronized.
10. Power off the new secondary chassis.
11. Click Disqualify Secondary. The synchronization of primary and secondary chassis is disabled.
12. Insert the FTEB module with even Device Index using the following steps:
location. Remember that slot numbering is zero-based and the left most slot is number "0."
13. Power on the new secondary chassis. Verify that the primary chassis has odd Device Index and
secondary chassis has even Device Index.
14. Click Enable Synchronization to initiate synchronization and allow auto-synchronization.
The synchronization of primary and secondary chassis is enabled. Confirm that the Auto
Synchronization State becomes ENABLED.
Add FTEB module to a chassis that does not have an empty slot
If an empty slot for adding the FTEB module is not available:
- 166 -
1. Disable the synchronization of primary and secondary chassis.

2. Power off the secondary chassis.
3. Remove the modules from the chassis.
4. Remove the secondary chassis.
5. Add the new chassis, which has more slots.
6. Mount the modules in the chassis.
8. Enable the synchronization between the primary and secondary chassis.
9. Switch-over the control to secondary chassis.
10. Perform the steps listed in the earlier section.
3.5.3 Taking a backup of ERDB

Before you upgrade the network, take a backup of the ERDB. This helps in reverting to CNET in case of
any issues during the network upgrade.
2. Select a listed system and click Connect.
Strategies section.
8. Expand the Server Node item and click ERDB Admin Tasks.
9. Click Backup Database. The Select and/or Create a folder to store backup set dialog box
appears.
Create the folder C:\temp and store the backup of ERDB
10. Click Select. A confirmation dialog box appears.
11. Click OK and acknowledge the message indicating success.
3.5.4 Upgrading the Experion Process Network to FTE

This procedure provides the steps to upgrade the server nodes connected to L1 controllers and IOLIMs
through ControlNet to the FTE network.
Prerequisites
l Before executing the tool, log on using local administrator privileges. This account must exist on
Server A and Server B and configured to have the same privileges.
l Power off Server B and then remove PCI Express host card from Server B.
l Remove FTE cables from Server B and then power On Server B. Ensure Server B is the primary
server before running the CNET to FTE upgrade tool.
l C200/C200E must be running with a minimum firmware version of EXP311.2-12.901 or later.
l Server A is the primary server.
- 167 -
l Stations and ACE nodes are connected to the Server on Level 2 FTE (on-line upgrade from dual
Ethernet excluded).
l Level 1 FTE cabling and switching are complete.
l CNET to FTE readiness checks are completed.
l Ensure that you upgrade Server B to FTE first before upgrading Server A to FTE.
l Ensure that Control Builder is closed.
Before starting the CNET to FTE Upgrade Tool, Server B must be disconnected from the CNET and FTE
network and its status should show Primary before launching and running the CNET to FTE Upgrade
Tool. (disconnect the FTE cables and the CNET cables and verify the Server status with the Start/Stop
Experion application). Additionally, since the Server B is disconnected from the network, Server B
cannot see any other nodes on the network and its status appears as Primary (only after confirmation
that the CNET to FTE Upgrade Tool can be launched).
To upgrade the Server B Experion Process Network to FTE
Tool, and then right-click CNET to FTE Upgrade > Run as administrator. The Provide User
Credentials dialog box appears.
You should run the tool with administrator privileges to avoid failure issues. The user account
must exist on Server A and Server B with the same privileges.
2. Type the Password and click OK. The CNET to FTE Upgrade screen appears.
3. Confirm that the FTEB modules are added to all the required controller chassis and the controllers
are synced.
4. Click Proceed. The Upgrade Server B Process Network to FTE task is automatically selected.
5. Click Proceed. A message indicating that system needs to be updated for FTE network type and
service is restarted.
6. Click Yes. The tool updates the registry and restarts the SR, CDA SAM services. If the registry
update fails, change the network type from RSLinx to FTE in the following path — HKEY_local_
Machine > Software > Wow6432node > Honeywell > TPS50 > InstallInfo > Networktype. You
need to update the registry and restart the CDA and SAM services manually.
The Upgrade Server B Process Network To FTE task may appear as “Failed.”. However, you
can continue with the upgrade once the network type is changed from RSLinx to FTE
manually. The Update ERDB System Preference task is automatically selected.
7. Select the Task Completed check box and click Proceed.
Configure FTEB modules and upgrade the controllers
1. Enter the name of the FTEB module in the New FTEB Name box.
2. Enter the Device Index of the FTEB module in the Device Index box.
3. Enter the slot number in which the FTEB module is inserted in the Slot Number box.
4. Click Proceed. A message appears indicating that FTEB modules are created and the controller
configuration is updated with new FTEB modules.
5. Click Yes. The Connect Server B to FTE Network option is automatically selected.
Connect Server B to FTE network
1. Follow on-screen instructions. After these tasks are completed successfully, you cannot return to
the CNET topology.
2. Select the Task Completed check box, and click Proceed. The Upgrade Server A Process Network
to FTE option is selected.
- 168 -
To upgrade the Server A Experion Process Network to FTE
1. Remove PCI Express host card and power on Server A.

2. Ensure FTE cables are disconnected before powering on Server A.
3. Run the UpdateServertoFTE batch file from C:\Program Files\ Honeywell\Experion\ C200
UpgradeTool on Server A.
4. Power-off Server A.
It is recommended to follow the right sequence before the Server A is powered on after the
upgrade from CNET to FTE upgrade tool is executed and then the Server A must be powered
off. The network cables must be connected to the Server A when Server A is powered off and
Server A must be powered on only after the network cables are connected. If the network
cables are connected after the Server A is powered on Server A becomes the preferred
Primary and the upgrade fails.
5. Connect the network cables, and then power on Server A.
6. Open Configuration Studio from Server B and click Administer the control strategy database. The
DBAdmin tool appears.
7. Click Recover Secondary Database. The Recover Secondary Database dialog box appears.
8. Click Yes.
9. Re-enable the ERDB synchronization.
10. Synchronize the servers by performing the following procedure:
a. Log on to the Station running on Server B with Manager (mngr) privileges.
b. Choose Configure > System Hardware > Redundant Server.
c. Click the Status tab.
d. Click Synchronize.
e. In the Message Zone, click Yes to synchronize Server A with the database on Server B.
After upgrading CNET to FTE, DO NOT remove the CNI card from the C200/C200E chassis as
peer-to-peer communication to other controllers is still through CNI cards, that is, until the
C200/C200E Controller is upgraded to UOC Controller. Wait for the server synchronization to
complete.
11. Select the Task Completed check box, and then click Proceed.
Results
Server A and Server B are connected to L1 nodes through FTE.
3.6 C200 Upgrade Tool Transform Configuration
3.6.1 Transform C200/C200E configuration to UOC configuration 170

The transformation activity involves the following tasks. All these tasks must be performed in the
sequence mentioned.
1. Taking a backup of the ERDB.
2. Assigning a Device Index to UOC.
3. Modifying any Exchange block communication paths.
4. Configuring SIM to PCDI.
5. Assigning Series A Modules to UOC generic adapters.
- 169 -
ATTENTION
ATTENTION
In case if you decide to cancel the C200 upgrade, the shadow configuration created by the tool
should only be cleaned using the Transform Cancel option in the C200 Upgrade Transform
Configuration Tool. See section "Cancel controller upgrade" on page 181 for more details.
3.6.1 Transform C200/C200E configuration to UOC configuration

This operation converts the C200/C200E strategies to UOC. During this operation, the C200/C200E
strategies are locked and a shadow of the strategy configuration is created in UOC.
However, if you want to revert the shadow configuration as done earlier, click Transform Cancel.
Prerequisites
l Ensure that you have completed the C200/C200E to UOC readiness checks.
l Ensure that all instances of Control Builder are closed.
To transform the C200/C200E configuration to UOC configuration
1. To launch the tool, click Start > Honeywell Experion Tools > All Honeywell Tools. Open the C200
Upgrade Tool folder and double-click C200 Upgrade Tool Transform Configuration .
2. The Login Information dialog box appears. Provide User Name and Password.
3. Select Server Name, Domain Name, and click OK. The Transform Option and Backup ERDB
screen appears.
4. In the Select Transform option: field, select C200 to UOC.

5. Select the Task Completed check box.
6. Click Next.
It could take several minutes for the C200 Control screen to appear.
The C200 Controller screen appears.
- 170 -
7. In the C200 tag name: field, select the C200 controller that you want to upgrade.
Ensure to first transform and then upgrade the selected controller before moving to the next
controller.
8. In the UOC Type: field, select UOC or VUOC, as required.
9. In the Connection Type: field, the value appears based on the selection in the UOC Type field.
10. In the UOC Primary Name: field, the name appears automatically based on the value selected in
the C200 Tag Name field.
11. In the UOC Device Index: field, enter the device index of the UOC controller. Ensure to provide the
device index, as planned. If you want to use the C200 FTEB Index for UOC, enter the same here.
If the device index of the C200/C200E Controller being upgraded is reused in the tool for the new
UOC, then post transform configuration step, the device index will be assigned as "0" in the control
builder to avoid index duplication. This will be changed to the actual value post final upgrade by
the Upgrade Tool.
12. The UOC Secondary Name field appears along with a value only if a name is selected in the C200
Tag Name field and the controller selected in the UOC Type field is redundant.
13. In the Downlink IP Address: field, enter the IP address.
14. In the Downlink IP Subnet mask: field, enter the IP address.
15. Click Next.
The UOC Exchange Block Path Update screen appears only if Exchange block is configured in
C200.
The Exchange Block Path and the Current Value of exchange block are displayed automatically.
16. To enter a new value for the Exchange Block Path in the New Value column, you can do either of
the following:
- 171 -
l Click the cell and enter the new value manually.

Or
l Perform the following steps to configure the new value:
a. Click Export to write to a csv file. Save the .csv file.
b. Open this .csv file with an editor such as Notepad and update the file with new values and
save the file. The location of the .csv file appears at the bottom of the screen.
c. Click Import to read the updated .csv file and copy them to the New Value fields.
If the new value entered is incorrect, then, see the Error column for error details.
17. Click Next. The Exchange path modification process completes.

A Series A Module Summary window appears.
18. A list of Series A I/O modules appear in the same hierarchy as configured in the Control Builder.
Click Assign Series A.
A Series A Assignment window appears.
19. In the Select Chassis Type field, select the chassis type to create a generic Ethernet IP adapter.
20. In the Name field, enter the name of the Ethernet IP adapter.
21. In the IP Address field, enter the IP address of the Ethernet IP adapter.
22. Select the Enable Extended Path Support check box, if the C200 is being upgraded to UOC with
ControlNet-EIP Bridge using Series A chassis.
To understand about the right extended path to be entered, see section "Configuring
ControlNet IOMs in the Ethernet/IP" in the Ethernet IP User's Guide. For example, 1,3 – signifies
that the ControlNet interface card is placed at slot number 3 in the chassis and can be reached
over the backplane (1).
23. Click Create GenAdapter Node.
A pop up window appears confirming the creation of GenAdapter. Click OK.
The created GenAdapter appears on the right pane under section Use of GenAdapter and its IO’s.
Repeat steps 19 to 23 to create multiple GenAdapters, as applicable.
24. There are two ways to assign I/Os to GenAdapters.
If you do not intend to change the physical location of the I/Os in the current remote I/O chassis, you
can perform the following steps:
a. Right-click the MACADDR node and select Assign all IO’s to GenAdapter.
A list of assigned GenAdapters that can be assigned with these I/Os appear under section
Assign Remote Chassis to GenAdapter.
b. From the list, select the applicable GenAdapter and click Assign.
A pop-up window confirming the assignment appears. Click OK.
Repeat steps a and b for each MACADDR node.
Or,
If you want to assign individual I/Os of the Remote I/O Chassis to specific Ethernet IP GenAdapter,
then perform the following step:
a. Right-click the IO and select Assign all selected IO to GenAdapter.
A list of assigned GenAdapters that can be assigned with these I/Os and its Available Slots
appear under section Assign IO to Chassis.
b. After all the I/Os are assigned to the correct GenAdapters as planned, click OK.
Partial assignment of I/Os to GenAdapters is not supported by the C200 Upgrade Transform
Configuration Tool.
25. Click Transform.
- 172 -
The status bar will display “Transformed successfully from C200 to shadow UOC”.
With this step, a UOC controller is created by the tool and a shadow configuration of the C200
Controller strategies and the I/Os are made on the newly created UOC.
The shadow strategies will have the original name with a standard prefix to avoid duplicate names.
26. Click Close to close the tool.
The Transform configuration can be completed (deleting the C200 and its strategies and correcting
the shadow configuration names) in the next step of the workflow using the C200 Upgrade Tool.
Go to section "C200 Upgrade Tool" below.
3.6.2 Transform configuration summary report

Title Description
Controller Information Provides the controller information that is, the controller name, the
controller type, and the device index.
Exchange Block Provides the details of the exchange block path before (old path) and
after (new path) the transform configuration.
Channel Block Provides the details of the channel number of SIM mapped to the PCDI
Assignment Master.
Channel Block Address Provides the details of the block addresses of SIM mapped to the PCDI.
Mapping
Address that cannot be Provides the details of the addresses that cannot be mapped to PCDI.
mapped See Peer Control Data Interface Implementation Guide for more
information.
Series-A IO or Interface Provides details of the Series-A I/Os or Interface Modules assigned to
Module assigned to FTEB.
FTEB
Series A Module Count Provides details of module count of Serial Interface, SST Profibus and
DeviceNet Modules per UOC and GenAdapter.
3.7 C200 Upgrade Tool

3.7.2 Perform off-process upgrade 173
The C200 Upgrade Tool is used to complete the strategy transformation and remove the C200
Controllers from the database. At the end of this step, all the strategies and I/Os that were under the
C200 Controller will be assigned to the UOC controller, and the generic adapters along with any
configuration changes required for the transformation.
3.7.1 Prerequisites
l Ensure that you have completed the C200/C200E to UOC readiness checks.
l Ensure that you have completed the C200/C200E to UOC Transform configuration.
3.7.2 Perform off-process upgrade

C200 to UOC Upgrade employs checkpoint restore and warm start. This work flow causes all function
blocks to behave like a regular controller Warm start. Assess the impact of this warm start behavior on
your process.
- 173 -
folder and double-click C200 Upgrade Tool to launch the tool. The Provide User Credentials dialog
box appears.
3. Select the module from the left pane and click Next.
4. The Upgrade Tool Type Selection pop-up appears. Select UOC and click OK.
The migration from C200/C200E to UOC can only be done off-process. Therefore, the Live option is
disabled and the off-process option is selected by default. Click OK.
The C200 Upgrade Tool window appears.
The list of each step and its status appears on the left pane, and its subsequent status and
description appears on the right pane.
Stages of the off-process upgrade
Check C200 Indicates whether there are any blockers for C200/C200E upgrade.
Upgrade Blocker
Configuration Configuration tasks. You also need to take ERDB backup using ERDB
Confirmation Admin Tool.
Prepare Controller Follow the instructions as displayed on the screen to prepare the
Hardware for hardware for upgrade.
Upgrade
C200 to UOC Read the notification carefully.

Upgrade
Notification
Finalize Displays the steps involved in Finalize Transformed Configuration and its
Transformed status.
Configuration
- 174 -
5. Select each step on the left pane, and then select the Task Completed check box on the right pane
and then click Proceed.
6. On completion of all the steps, the message “Off-Process Upgraded completed successfully” will
appear on the Finalize Transformed Configuration screen.
7. Click Close to close the window.
3.8 Prepare Controller Hardware for Upgrade
3.8.1 Configuring 1756 modules 175

3.8.2 Process to upgrade Serial Interface Module (SIM) 177
The C200 to UOC upgrade supports three kinds of topologies, EIP Direct, EIP-CNET Bridge, Hybrid
Topology. See section Topology for more details.
Though the conversion topologies illustrated in the Topology section show the I/Os connected to UOC
over a Device level Ring (DLR) Topology over the downlink, there are multiple I/O downlink topologies
supported by UOC. See EthernetIP User's Guide to understand more about the different topologies.
High Availability Seamless Redundancy (HSR) topology is not supported for connecting Series A I/Os
to UOC over the downlink.
3.8.1 Configuring 1756 modules

Prerequisites
l Installation of hardware should be as per the topology (EIP Direct, EIP-CNET Bridge, or Hybrid) as
illustrated in section Topology.
l Ensure that the Redundant Chassis module is powered on.
l Ensure that the hardware components (1756-EN2TR, 1756-CN2R and 1756-RM2) have the
firmware versions as advised in section "Enhanced Redundancy System Kit firmware" mentioned in
the ControlLogix Enhanced Redundancy System Release Notes. This document is available for
download at Rockwell website http://www.rockwellautomation.com/literature/
l Both 1756-EN2TR on the Redundant EIP-ControlNet Bridge chassis should have the same
firmware version, if the EIP-ControlNet Bridge topology is selected.
l All the 1756-CN2R should have the same firmware version.
- 175 -
l Both 1756-RM2 on the Redundant EIP-ControlNet Bridge chassis should have the same firmware
version, if the EIP-ControlNet Bridge Topology is selected.
l Have RSLinx Classic v3.90 or higher – available at Rockwell Automation download website.
l Enhanced ControLogix Redundancy Kit v20.058 kit2 or later – available at Rockwell Automation
download website.
l BOOTP/DHCP Tool – available at Rockwell Automation download website.
The EIP-ControlNet bridge uses Rockwell Modules and the Enhanced Redundancy Scheme for the
bridge. To know more about the Enhanced Redundancy Scheme and configuration, see ControlLogix
Enhanced Redundancy System Release Notes (for example, 1756-RN694-EN-P) document available
at Rockwell website http://www.rockwellautomation.com/literature/.
Configuring EN2TR module
There are three ways to set up an IP address for EN2TR.

l Using rotary dials on EN2TR to set IP address manually from 192.168.1.x (x is 1 to 254). This is the
default IP series taken by the module.
l Using Rockwell BootP/DHCP tool. Use this tool if you do not want to use the default series.
l Using RSlinx Classic
See the Ethernet/IP Network Devices User Manual (for example, ENET-UM006-EN-P) available at the
Rockwell website http://www.rockwellautomation.com/literature/ and follow the detailed procedure.
The steps at a high-level are described as follows:

1. Configure the IP address for 1756-EN2TR.
2. If using BOOTP to set IP address, disable BOOTP on device after configured.
Ensure that both ENT2R have the same IP address in redundant chassis configuration.
Configuring CN2R module
Configure the MAC address of 1756-CN2R by setting the rotary switch on the card.
Ensure that the CN2R in the redundant chassis configuration has the same MAC address.
To configure the CN2R module added to the EIP-ControlNet bridge to establish communication on the
IO ControlNet Network, see ControlNet Configuration User Manual (for example, CNET-UM001-EN-P)
available at the Rockwell website http://www.rockwellautomation.com/literature/
Configuring Bridge Redundancy
To configure the redundancy using the EIP-ControlNet bridge, see the ControlLogix Enhanced
Redundancy System Release Notes (for example, 1756-RN694-EN-P) available at Rockwell website
http://www.rockwellautomation.com/literature/.
The high-level steps to establish the sync between the bridges are:
1. Download and install RSLinx Classic and Redundancy Configuration Tool.
2. Open RSlinx Classic and configure EtherNet/IP driver to discover 1756-EN2TR.
3. Browse to 1756-EN2TR > 1756-RM2. Then, right click 1756-RM2 and select Redundancy
Configuration Tool.
4. Use this tool to establish and monitor the sync status. If the chassis are not synchronized, then
power recycle both the chassis.
- 176 -
Configuring EIP-ControlNet Bridge chassis
If the UOC Target Topology is using the EIP-ControlNet Bridge, then perform the following high-level
steps to configure the hardware:
1. Install the hardware.
l Install the UOC Hardware. See instructions in UOC User's Guide.
l Install the EIP-ControlNet Bridge components as per the planned topology.
2. Configure the 1756-EN2TR.

l See instructions in section “Configuring EN2TR module” above.
l See the EthernetIP User's Guide to plan the UOC Downlink connection for the 1756-EN2TR
Modules.
3. Connect the 1756-EN2TR modules to UOC downlink.

l See EthernetIP User's Guide to connect the 1756-EN2TR Modules to the UOC Downlink
network.
4. Connect the hardware on the ControlNet bus.

l See instructions in section “Configuring CN2R module” above to configure 1756-CN2R
Modules.
l Connect the 1756-CN2R Modules to the correct ControlNet segment as planned.
l Ensure that the ControlNet parameters of the 1756-CN2R modules are set to the same values
as that of the other CNI modules in the ControlNet segment.
l While configuring the 1756-CN2R modules, ensure to check the fiber optics check box "My
System uses Fiber Optics".
5. Reboot all the chassis including the remote chassis.

l Reboot all the chassis connected to the ControlNet segment so that the ControlNet parameters
of all the Interface modules are synchronized and there are no Keeper Faults.
6. Sync the bridges.
3.8.2 Process to upgrade Serial Interface Module (SIM)

Perform the following procedure only if SIM and its strategies are loaded.
The Modbus communication through the Serial Interface Module has to be moved to Peer Control Data
Interface (PCDI) while using the Transform Configuration as part of the upgrade process. See the Peer
Control Data Interface Implementation Guide for more details on how to configure PCDI communication.
1. Check if the hardware can support Modbus TCP or is a Serial Modbus to Modbus TCP converter
required. If the hardware can support Serial Modbus to Modbus TCP converter, then you can select
one of the following:
l Qualified Modbus TCP to Serial gateway devices
o Digi One IA, Digi One IAP
o Lantronics Xpress-DR-IAP
2. Connect the Ethernet cable between the device/bridge to the L2 switch.
To disconnect the device from SIM
1. Disconnect the device from the respective FTA.

2. Connect the device to the L2 switch.
3. Configure the TCP Bridge based on the device connected. For example, configure the Allen
Bradley (IAP) device or the RS232/RS485 (IA bridge) protocol-based device.
- 177 -
For more information about the configuration and wiring of the TCP Bridge, see the Original Equipment
Manufacturing (OEM) document.
3.9 Post Upgrade Activities
3.9.2 Loading after performing off-process upgrade 178

3.9.3 To Reestablish peer connection 180
3.9.1 Prerequisites
Activate PCDI master and its strategies
Ensure that PCDI master is activated and its communication to the device is successful, and then
activate its strategies.
3.9.2 Loading after performing off-process upgrade
Perform load operations
Post upgrade, note that the CEE name of the new UOC controller is retained as that of the C200CEE. If
you want to change the CEE name, then change it before loading the new UOC controller.
Modules and its related strategies shall be loaded in following order based on their availability:
l UOC Module
l Series A modules
The C200 Upgrade Transform Configuration Tool sets the parameter "TO Connection Type" value to
"POINT2POINT" during the transformation process. However, some of the I/O modules with specific
firmware version do not support this configuration. Thus, loading these I/O modules with an
unsupported configuration will not be unsuccessful. Hence, ensure that the I/O module configurations
are valid before loading them to ensure a successful load operation.
The following table shows the supported connection types. For more details, see Ethernet IP User's
Guide.
Model Rockwell Honeywell Connection type Comments

Equivalent Version
TC- 1756-IF8H 2.1 Multicast/Point2Point Rockwell module is not supporting
HAI081 HART. This is not in scope.
TC- 1756-OF8H 2.13 Multicast/Point2Point Rockwell module is not supporting
HAO081 HART. This is not in scope.
TC- 1756-IF6I 1.9 Multicast/Point2Point
IAH061
1756-IF8I 2.011 Multicast/Point2Point
TC- 1756-IA16 2.4 Multicast
IDA161
3.2 Multicast/Point2Point
TC- 1756-IA16I 1.6 Multicast
IDK161
2.1 Multicast
- 178 -
TC- 1756-IB16I 1.6 Multicast

IDJ161
2.1 Multicast
TC- 1756-OB16I 2.3 Multicast
ODA161
TC- 1756-OA16I 1.6 Multicast
ODK161
3.2 Multicast
TC- 1756-OB16I 2.1 Multicast
ODJ161
TC- 1756-IT6I 1.9 Multicast/Point2Point
IXL061
1756-IRT8I 2.011 Multicast/Point2Point
TC- 1756-IT6I2 1.13 Multicast/Point2Point
IXL062
TC- 1756-IR6I 1.9 Multicast/Point2Point
IXR061
TC- 1756-IB32 2.8 Multicast
IDD321
TC- 1756-OB32 2.4 Multicast
ODD321
TC- 1756-OA8D 3.2 Multicast/Point2Point
ODX081
TC- 1756-OB16D 3.2 Multicast/Point2Point
ODX161
TC- 1756-IA8D 2.5 Multicast
IDX081
TC- 1756-IB16D 2.5 Multicast
IDX161
TC- 1756-IM16I 1.6 Multicast
IDW161
2.1 Multicast
3.2 Multicast
TC- 1756-OX81 2.1 Multicast
ORC081
TC- 1756- 2.1 Multicast
ORC161 OW16IK
TC- 1794-IE8 Multicast
FIAH81
TC- 1794-OE4 Multicast
FOA041
TC- 1794-IB16 Multicast
FID161
- 179 -
TC- 1794-OB16P Multicast

FOD161
TC/TK- 1756-OF6CI 1.9 Multicast
OAH061
1756-OF8I
TC- 1.9 Multicast
MDP081
l PCDI
l Strategies
For all RAIL IO's Connection Timeout Multiplier should be *64.

On loading UOC, if any checkpoint issue is observed, continue loading and then perform rebuild and
restore of checkpoint.
3.9.3 To Reestablish peer connection

Perform this procedure after the current C200 to UOC upgrade completion.
l If there are Initiator/Responder peer connections between the C200 Controller that is being
upgraded and any other controller, then perform the following actions:
1. Select the strategies in the upgraded C200 that has peer connections with other controllers.
2. Select the strategies in other controllers that have peer connections with the C200 that is being
upgraded.
3. Load the selected strategies.
l If there are Exchange peer connections between the C200 Controller that is being upgraded and
any other controller (including those in other clusters), and if the Requester blocks are residing in
other controller, then perform the following actions:
1. Identify the Exchange connections from the Readiness check report.
2. Access the Requestor blocks in other controllers and modify the Exchange paths to the new
controller.
3. Reload the modified strategies.
3.10 Troubleshooting and Maintenance

3.10.3 Remove the C200/C200E Upgrade Tool 181

3.10.9 Upgrade a non-redundant C200/C200E to redundant UOC 183
3.10.11 C200 Upgrade without IOMs configured 186
- 180 -
3.10.1 Cancel CNET to FTE upgrade

To cancel CNET to FTE upgrade before Server B becomes primary:
1. Click Cancel on the CNET to FTE Upgrade screen and confirm restarting the required services.
An User Account Control window appears when performing the Network type change (from
FTE to CNET) and services restart. Provide the Administrator credentials and click Yes.
2. Click OK.
3. Restore the ERDB using the DBadmin tool.
4. Close the CNET to FTE Upgrade.
To cancel CNET to FTE upgrade after Server B becomes primary:
1. Click Cancel on the CNET to FTE Upgrade screen. A confirmation appears prompting you to restart
the required services and disconnect Server B from the network.
An User Account Control appears when performing Network type change (from FTE to CNET)
and services restart. Provide the Administrator credentials and click Yes.
2. Disconnect the Server B from the network.
3. Reconnect the Server A with CNET hardware to the network, and then power-on the Server A.
4. Restore the ERDB using the Badin tool.
5. Power off the Server B.
6. Reconnect the Server B with CNET hardware to the network, and then power-on the Server B.
7. Close the CNET to FTE Upgrade tool.
3.10.2 Cancel controller upgrade

Contact Honeywell TAC on how to proceed with the upgrade before restoring the ERDB.
To cancel the upgrade before preparing the controller configuration for upgrade
1. Click Cancel on the C200/C200E to UOC upgrade screen. A confirmation message appears
prompting you to launch the C200 Upgrade Transform Configuration Tool.
2. Click OK.
folder and double-click C200 Upgrade Transform Configuration Tool to launch the tool.
4. The Provide User credentials dialog box appears. Type the Password.
5. Click Transform Cancel. The shadow configuration of the UOC is reverted to C200/C200E.
3.10.3 Remove the C200/C200E Upgrade Tool

After the upgrade is complete, you may remove the C200/C200E Upgrade tool.
1. Choose Start > Control Panel > Programs > Uninstall Programs.
2. Right-click C200 Upgrade Tool, and select Uninstall. Acknowledge the confirmation message.
3. Wait for some time. The C200 to UOC Upgrade tool is removed.
3.10.4 Alarms generated during upgrade

The following are some of the alarms generated during upgrade:
- 181 -
l NDM manager intermittent cable communication error and Umax error alarms are expected.
l No tag alarms are generated in Console Station. After upgrade, you must acknowledge these
alarms.
If the quality of alarm is bad, perform the alarm regeneration:

1. Go to Station > Configure > Alarm and Event Management > Alarms > Alarm Processing tab.
2. Uncheck the Enable alarm server-wide option under Processing settings. Ensure that all alarms
are cleared.
3. Check the Enable alarm server-wide option under Processing settings. All bad quality alarms are
not seen.
l During this process, all the alarms disappear from the process and system alarm summary
temporarily, and are regenerated. Bad quality alarms are grayed out and can be
acknowledged. Perform this operation only when it is fine to not have any alarms for up to few
minutes.
l Perform this operation only when you want to clear the bad quality alarms.
3.10.5 Device index is not in the PCDI range

Cause
The PCDI supported device index range is 1-247 and 255. If the device index entered in SIM is not in
the supported range of the PCDI.
Solution
Manually change the device index field in the Control Builder, or, if needed, you have to modify the
device index in the PLC.
Cause
If the PCDIMASTER is connected to only one device.
Solution
Enter 255 for the device index in the Control Builder and change it in the PLC.
Cause
If the PCDIMASTER is connected to multiple devices.
Solution
Map the PLC device index to PCDI range in the bridge or modify the device index of the PLC.
3.10.6 PCDI activation error

Cause
The tool has the optional feature to activate the PCDIMaster. However, activation of the PCDIMaster
fails for many reasons. For example,
- 182 -
l The TCP Bridge configuration is not correct.

l Proper wiring is not done between the TCP Bridge and the device.
l L2 Ethernet cable is not connected properly with the TCP Bridge.
Solution
Check the activation error in the Control Builder, fix the issue, and then activate it manually before
activating the strategy to communicate to the PCDI.
For details on activation failure and troubleshooting, see the Peer Control Data Interface
Implementation Guide .
3.10.7 Slave FTA Handling

Cause
PCDI always acts as a Master. If any site has Slave FTA (part no - 51191029), then SIM with this Slave
FTA configuration cannot be upgraded. The controller with this PCDI cannot communicate to the PLCs
which are connected to this Slave FTA.
Solution
The controller can communicate to the device/PLC either through controller with Series A Chassis I/O
topology with FTEB or through OPC server (SCADA configuration).
3.10.8 Readiness check failure scenarios

Cause
The C200 Upgrade Tool server readiness check does not execute both server and controller checks, it
remains in NE (Not Executed) state.
Solution
To resolve this issue, perform the following steps.
1. Restart the C200 Upgrade Tool.

2. Restart the server running the readiness check.
3. Run only the server check or the controller check (one check at a time and not together).
3.10.9 Upgrade a non-redundant C200/C200E to redundant UOC

Problem: If the C200/C200E chosen for the upgrade is non-redundant, then the C200 Upgrade Tool
does not allow you to finalize the transformed configuration and complete the upgrade from non-
redundant C200 to redundant UOC.
Solution: If a shadow copy is already created for the non-redundant C200/C200E by the C200 Upgrade
Transform Configuration Tool, then first cancel the already transformed configuration and then use one
of the following two ways to upgrade the non-redundant controller.
ATTENTION
The Upgrade Tool allows:
- 183 -
l Non-redundant C200 to non-redundant UOC.

l Redundant C200 to redundant UOC.
However, non-redundant C200 to redundant UOC is not supported.
l Do the upgrade manually without using the tool.

This involves tasks like, creating a new UOC Controller and related configurations like Generic
adapters, assigning the Series A I/Os to the new UOC and modifying their configurations
accordingly, re-assigning the strategies in the C200/C200E Controller to the new UOC
Controller and loading all the components.
Or,
l Do the upgrade using the tool after converting the controller into redundant.
This involves creating a temporary redundant C200 Controller, then moving all the I/Os and
strategies of the non-redundant controllers to the redundant controller, upgrading the
redundant controller to a redundant UOC using the C200 Upgrade Tool set and then changing
the redundant UOC to a non-redundant UOC. To do all this, perform the following steps:
a. Put the running C200/C200E Controller to IDLE state from monitoring side of the Control
Builder.
b. Inactivate all the I/O modules and control modules present under the controller from
monitoring side.
c. Delete all the control modules from monitoring side of the Control Builder.
d. Delete all the I/O modules from monitoring side of the Control Builder.
e. Delete C200/C200E controller block from monitoring side of the Control Builder.
f. Delete FTEB block and other Controller chassis resident modules from monitoring side of
the Control Builder.
g. Change the device index of the old FTEB to some other value from the project side of
Control Builder.
h. Create new redundant FTEB blocks with the old device index and same configuration as
old FTEB block.
i. Create new C200/C200E blocks with the same configuration as old C200/C200E
controller block.
j. Assign all the I/O Modules from old C200/C200E controller to the new C200/C200E
controller.
k. Assign all the Control Modules from old C200/C200E controller to the new C200/C200E
controller.
l. Perform the complete upgrade for this new C200/C200E controller with the C200
Upgrade Tool set.
m. Open control builder, uncheck the “Module is redundant” option from the new UOC
primary block created by the C200 Upgrade Tool and make it a non-redundant UOC.
n. Perform manual load for the UOC block and its related I/O modules and control modules
from the project side of Control Builder.
- 184 -
3.10.10 QVCS Details

QVCS updates while upgrading Experion Process Network from CNET to FTE
Block types QVCS details

C200/C200E, Version: Major/Minor version will be updated for the upgraded module (based on
IOLIM, RM user selection)
and FIM
current active or working version (before upgrade) to the upgraded version. The
upgraded version will become the active or working version.
l Entry for CNET to FTE upgrade is displayed for the corresponding version
created during the upgrade.
Revert to Version in Control Builder: After performing CNET to FTE upgrade, revert
the Platform Block to a version that existed before the upgrade. A message stating
revert is not allowed will be displayed. However, if there are any version increments
after the upgrade, reverting the newer versions will not have any impact.
Revert to Label in Control Builder: After performing CNET to FTE upgrade, revert
the Platform Block Version to a Label that was applied before the upgrade. A
message stating revert is not allowed will be displayed. However, if there are any
Label version increments after the upgrade, on reverting the label on the newer
versions will not have any impact.
QVCS updates while upgrading C200/C200E to UOC
When upgrading C200/C200E to UOC, SIM to PCDI, Series A IO and Exchange strategies, QVCS
details such as Version, Qualification State, Label, Revert to Version and Label details are updated as
described here.
l Version: The strategies upgraded will be initialized to major version (1.0). For Series A, see the
section, QVCS updates while Upgrading Series A modules.
l Qualification State and Label: Qualification State and Label will be moved from the current active or
working version (before upgrade) to the version initialized (1.00) during the upgrade. This initialized
version will become the active or working version.
l Revert to Version in Control Builder: For versioning initialized objects, this scenario will not hold
good. However, for other objects, reverting versions will be successful.
l Revert to Label in Control Builder: Trying to revert to label (Label created and applied to versions of
object) before upgrade will not be allowed and a message informing that“A different object with the
same name exists in the project, cannot revert” will be displayed.
Workaround
1. Go to QVCS Manager > Query and select Revert Label from the Query on dropdown list.
2. Select the label to be reverted to from the Value list. Click List
3. Select respective deleted object which appears in the list.
4. Right click on the selected object > Select Revert Labels > Select Apply/Remove > Select To
selected version > Remove label from Applied Revert Labels(for the version)
5. Follow step 3 for all the deleted objects in the list. Ensure the label is removed for all the deleted
instances of the particular object.
6. When you try to revert to a label applied before upgrade, revert will be successful.
- 185 -
View History of objects under QVCS after upgrade
For History details, choose QVCS Manager > Object History and select Checkin from the Action
dropdown box. Details for each upgraded block types seen are described here.
Block types Upgraded Block Type History details

SIM PCDI Entry for object version created during upgrade
l History of previous versions of object before
upgrade
Control Module Control Module History of each object
C200 UOC l Entry for object version created during upgrade
l History of previous versions of object before
upgrade
QVCS updates while Upgrading Series A modules
When upgrading C200/C200E to UOC with Series A modules, QVCS details such as Version,
Qualification State, Label, Revert to Version and Label details are updated as described here.
Block QVCS details

types
Series A Version: Major version will be incremented for the upgraded module. Qualification State
Modules and Label: Qualification State and Label will be moved from the current active or working
version (before upgrade) to the upgraded version. The upgraded version will become the
active or working version.
l Entry for C200 to UOC upgrade is displayed for the corresponding version created
during the upgrade.
Revert to Version in Control Builder: After performing C200 to UOC upgrade, revert the
Series A module to a version that existed before the upgrade. A message stating revert is
not allowed will be displayed. However, if there are any version increments after the
upgrade, reverting the newer versions will not have any impact. Revert to Label in
Control Builder: After performing C200 to UOC upgrade, revert the Series A Module
Version to a Label that was applied before the upgrade. A message stating revert is not
allowed will be displayed. However, if there are any Label version increments after the
upgrade, on reverting, the label on the newer versions will not have any impact.
See the Qualification and Version Control System User's Guide for more information about QVCS.
3.10.11 C200 Upgrade without IOMs configured

Cause
The Control Modules fail to load post-upgrade to UOC if there are no IOMs configured under the C200
Controller.
If you perform the upgrade using the C200 Upgrade Tool, then the upgrade will be successful. But, the
loading of CM will fail.
Solution
Therefore, to recover from the load failure of the CM, you should perform the following steps:
- 186 -
1. Create a new UOC manually in the Control Builder.

2. Assign the CM of the upgraded UOC to the newly created UOC.
3. Proceed to load the Control Modules.
3.11 Appendix A Checklist for ControlNet to FTE conversion

This section includes the required steps to upgrade the Experion Process Network from CNET to FTE.
Task Done?
The system should be running Experion R511.2.
Supervisory network should be on FTE.
ATTENTION
Contact Honeywell TAC if the supervisory network is not on FTE.
C200/C200E/IOLIM/SIM, is flashed to the latest firmware Experion R511.2 (or the firmware
is interoperable with the system on Experion R511.2.
FTEB modules is flashed to the latest firmware Experion R511.2 (or the firmware which is
interoperable with the system on Experion R511.2.
If the secondary module names are missing in the configuration form, make sure to run the
script provided.
Ensure BootP is disabled and stopped in all the Servers.
C200 Upgrade Tool is installed on Server A and Server B.
Readiness Checks are run and results are successful.
All peer-to-peer (CDA and EXCHANGE) points have been reviewed and confirmed safe to
proceed.
Log in to the Server with appropriate privileges to perform the upgrade. (for example,
administrator privileges) and run the UpdateBaseIP_SubnetMask_Batch.cmd file.
Enter the following details.
Base IP — For example, 10.144.1.0
Subnet — For example, 255.255.248.0
Double-click Redundancy Module and Disqualify the Secondary module.
Power off the secondary C200 rack.
Install FTEB with the odd device index. For example, 13.
Power on the secondary rack.
Synchronize the secondary controller.
Initiate switchover.
Power off secondary rack.
Install FTEB with the even device index in the new secondary rack.
Power on the new secondary rack.
Confirm synchronization.
Disconnect Server B from the CNET and FTE networks and confirm the primary status.
Right-click the CNET to FTE Upgrade Tool and select the Run as administrator option.
- 187 -
Task Done?
Confirm the odd addressed device index is the primary C200.
Confirm ERDB Backup and click Proceed.
Click Proceed to upgrade Server B to FTE and click Yes.
Enter Base IP and additional information. For example, Subnet.
Enter FTEB name, for example, FTEB31X, Device Index, for example, 13, and slot, for
example, slot 4 and then click Proceed.
Confirm status changes to Executed.
Check registry settings (HKEY_LOCAL_Machine > Software > Wow6432node > Honeywell
> TPS50 > InstallInfo > NetworkType is changed to FTE.
Open Control Builder and confirm both primary and secondary controllers, RMs and IOLs are
shown in each new FTEB. For example, FTEB31X and FTEB31XSEC
Connect Server B to FTE network.
Confirm from the Station in the System Status page that the System Repository backup is
not synchronized and stopped.
Synchronize Server B from Server A.
From Server B, open NTOOLS -e and confirm the view to FTEB’s and C200.
Manual Failover (switch over) from Server A to make Server B primary and confirm view to
controllers.
Shutdown Server A.
Disconnect CNET cables from Server A.
Disconnect FTE cables from Server A.
Power on Server A.
Run UpdateServertoFTE script on Server A.
Shutdown Server A.
Connect FTE network to Server A.
Power on Server A.
On ServerB, in DBAdmin, check ERDB host information and that both are running.
On Server B, in DBAdmin, recover Secondary from Primary.
Confirm if it is successful.
On Server B, in DBAdmin, check ERDB host information and that both are running. If Server A
fails, reboot Server B after enabling the ERDB replication.
Synchronize the servers.
Switch over the servers and synchronize the servers.
Enable the ERDB replication.
- 188 -
NOTICES
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of
Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.

Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is a
business unit of Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of
Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Other brands or trademarks are trademarks of their respective owners.
Trademarks that appear in this document are used only to the benefit of the trademark owner, with no
intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third
party materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor.
The licenses, notices, restrictions and obligations, if any, may be found in the materials accompanying
the product, in the documents or files accompanying such third party materials, in a file named third_
party_licenses on the media containing the product.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions Support website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
[email protected]
Use this email address to provide feedback, or to report errors and omissions in the documentation. For
immediate help with a technical problem, contact HPS Technical Support through your local Customer
Contact Center, or by raising a support request on the Honeywell Process Solutions Support website.
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness that
can be exploited to reduce the operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.
To report a potential security vulnerability against any Honeywell product, please follow the instructions
at:
https://www.honeywell.com/en-us/product-security.
Support
- 189 -
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find
your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-
support-contacts/Pages/default.aspx.
Training classes
Honeywell holds technical training classes that are taught by process control systems experts. For more
information about these classes, contact your Honeywell representative, or see
http://www.automationcollege.com.
- 190 -

C200 Upgrade Tool Guide-EPDOC-X640-en-520A

Uploaded by

Copyright:

Available Formats

C200 Upgrade Tool Guide-EPDOC-X640-en-520A

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C200 Upgrade Tool Guide-EPDOC-X640-en-520A

Uploaded by

Copyright:

Available Formats

Experion PKS

2.1.2 C200/C200E Controller to the C300 Controller 15

2.1.5 Understand the differences between FIM2 and FIM4/FIM8 19

2.1.8 User Privilege requirements 21

2.2 Plan the C200/C200E to C300 Upgrade 21

2.2.3 Site requirements 24

2.3 Install the C200 Upgrade Tool 33

2.4 Readiness Checks 35

2.6 Transform Configuration (C200/C200E to C300, FIM2 to

2.7 Upgrade C200/C200E to C300 (Live/Off-Process) 73

2.8 Prepare Controller Hardware for Upgrade 94

2.9 Post Upgrade Activities 115

2.9.2 Considerations 115

2.10 Troubleshooting and Maintenance 118

2.10.4 Isolate the Console Station from the server 120

2.10.7 Device index is not in the PCDI range 122

2.12 Appendix-B Checklist for ControlNet to FTE conversion 131

3.1.4 Understand the difference between C200/C200E and UOC 139

3.2 Plan the C200/C200E to UOC Upgrade 139

3.2.4 Security Considerations 144

3.3 Install the C200 Upgrade Tool 147

3.4 Readiness Checks 148

3.5.2 Adding the FTEB module to the controller chassis 165

3.7 C200 Upgrade Tool 173

3.8 Prepare Controller Hardware for Upgrade 175

3.9 Post Upgrade Activities 178

3.10 Troubleshooting and Maintenance 180

3.10.3 Remove the C200/C200E Upgrade Tool 181

3.10.6 PCDI activation error 182

3.10.9 Upgrade a non-redundant C200/C200E to redundant UOC 183

3.10.10 QVCS Details 185

3.11 Appendix A Checklist for ControlNet to FTE conversion 187

1 ABOUT THIS GUIDE

C200/C200E Controller to the UOC Controller

1.3 Revision history

Revision Date Description

1.4 Intended audience

1.5 Related documents

1.6 Terms and definitions

2 C200/C200E CONTROLLER TO THE C300

2.1.1 Hardware upgrade 12

2.1.4 Understand the differences between C200/C200E and C300 17

2.1.6 Hardware Software requirements 20

Upgrade what Using this tool

The upgrade can be performed in one of two ways—Live and Off-Process.

Hardware Supported only under these Software Tool

2.1.1 Hardware upgrade

The C200/C200E chassis is affected.

Process to upgrade C200/C200E to C300 and FIM2 to FIM4/FIM8

Task Live Off-Process Off-Process Upgrade Supervisory

Task Live Off-Process Off-Process Upgrade Supervisory

Connect the I/Os to the

Assign and load the

Power-on and startup

Task Live Off-Process Off-Process Upgrade Supervisory

Benefits of the upgrade

Supervisory FIM2 modules

2.1.2 C200/C200E Controller to the C300 Controller

2.1.3 Scope and limitations

Hardware Third-party modules/ Software Tool