R310.2 Support Software Change Notice

Experion
Release R310.2
Experion Support Software
Change Notice
EP310165002B
R310.2
February 2011
Notices and Trademarks
Copyright 2010 by Honeywell International Inc.

Release R310.2 February 2011
While this information is presented in good faith and believed to be accurate, Honeywell disclaims
the implied warranties of merchantability and fitness for a particular purpose and makes no
express warranties except as may be stated in its written agreement with and for its customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The
information and specifications in this document are subject to change without notice.
Honeywell, PlantScape, Experion, and TotalPlant are registered trademarks of Honeywell
International Inc.
Other brand or product names are trademarks of their respective owners.
Honeywell Process Solutions

1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA
1-800 822-7673
ii Experion Support Software Change Notice R310.2

Honeywell February 2011
Support and Other Contacts
United States and Canada

Contact: Honeywell Solution Support Center
Phone: 1-800-822-7673
Calls are answered by dispatcher between 6:00 am and 4:00 pm
Mountain Standard Time. Emergency calls outside normal working hours
are received by an answering service and returned within one hour.
Fascimile: 1-973-455-5000
Mail: Honeywell TAC, MS L17
1860 W. Garden Lane
Phoenix, AZ, 85027 USA
Europe, Middle East, and Africa (EMEA)

Contact: Honeywell TAC-EMEA
Phone: +32-2-728-2345
Fascimile: +32-2-728-2696
Mail: TAC-BE02
Hermes Plaza
Hermeslaan, 1H
B-1831 Diegem, Belgium
Pacific
Contact: Honeywell Global TAC – Pacific
Phone: 1300-364-822 (toll free within Australia)
+61-8-9362-9559 (outside Australia)
Fascimile: +61-8-9362-9564
Mail: Honeywell Limited Australia
5 Kitchener Way
Burswood 6100, Western Australia
Email: GTAC@honeywell.com
India
Contact: Honeywell Global TAC – India
Phone: +91-20- 6603-9400
Fascimile: +91-20- 6603-9800
Mail: Honeywell Automation India Ltd
56 and 57, Hadapsar Industrial Estate
Hadapsar, Pune –411 013, India
Email: Global-TAC-India@honeywell.com
Korea
R310.2 Experion Support Software Change Notice iii
February 2011 Honeywell
Contact: Honeywell Global TAC – Korea

Phone: +82-2-799-6317
Fascimile: +82-2-792-9015
Mail: Honeywell Co., Ltd
4F, Sangam IT Tower
1590, DMC Sangam-dong, Mapo-gu
Seoul, 121-836, Korea
Email: Global-TAC-Korea@honeywell.com
People’s Republic of China

Contact: Honeywell Global TAC – China
Phone: +86- 21-2219-6888
800-820-0237
400-820-0386
Mail: Honeywell (China) Co., Ltd
33/F, Tower A, City Center, 100 Zunyi Rd.
Shanghai 200051, People’s Republic of China
Email: Global-TAC-China@honeywell.com
Singapore
Contact: Honeywell Global TAC – South East Asia
Phone: +65-6580-3500
Fascimile: +65-6580-3501
+65-6445-3033
Mail: Honeywell Private Limited
Honeywell Building
17, Changi Business Park Central 1
Singapore 486073
Email: GTAC-SEA@honeywell.com
Taiwan
Contact: Honeywell Global TAC – Taiwan
Phone: +886-7-536-2567
Fascimile: +886-7-536-2039
Mail: Honeywell Taiwan Ltd.
17F-1, No. 260, Jhongshan 2nd Road.
Cianjhen District
Kaohsiung, Taiwan, ROC
Email: Global-TAC-Taiwan@honeywell.com
Japan
Contact: Honeywell Global TAC – Japan
Phone: +81-3-6730-7160
Fascimile: +81-3-6730-7228
iv Experion Support Software Change Notice R310.2

Mail: Honeywell Japan Inc.

New Pier Takeshiba, South Tower Building,
20th Floor, 1-16-1 Kaigan, Minato-ku,
Tokyo 105-0022, Japan
Email: Global-TAC-JapanJA25@honeywell.com
Elsewhere
Call your nearest Honeywell office.
World Wide Web

Honeywell Solution Support Online:
http://www.honeywell.com/ps
Training Classes
Honeywell Automation College:
http://www.automationcollege.com
R310.2 Experion Support Software Change Notice v

Symbol Definitions
Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.
Symbol Definition
ATTENTION: Identifies information that requires special

consideration.
TIP: Identifies advice or hints for the user, often in terms of

performing a task.
REFERENCE - INTERNAL: Identifies an additional source of

information within the bookset.
CAUTION Indicates a situation which, if not avoided, may result in equipment

or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.
CAUTION: Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.
WARNING: Indicates a potentially hazardous situation which, if not

avoided, could result in serious injury or death.
WARNING symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.
vi Experion Support Software Change Notice R310.2

Contents
1. ABOUT R310.2 SUPPORT SOFTWARE.....................................13

1.1 Review the latest information ...................................................................... 13
Checking for updates on online Support ..............................................................................13
1.2 Applicability of R310.2 Support Software................................................... 14
Other support information.....................................................................................................14
1.3 Contents of this Update................................................................................ 14
2. INSTALLING SUPPORT SOFTWARE.........................................15

2.1 Preparing for Installation.............................................................................. 15
Installation scenarios............................................................................................................15
Installation order...................................................................................................................15
Verifying the version of Experion installed on the node........................................................16
Loss of view during installation of Support Software ............................................................16
Backing up all nodes ............................................................................................................16
Special considerations when migrating Flex nodes..............................................................16
Virus Scanning and Protection .............................................................................................17
EBR Client and Logger Services..........................................................................................17
2.2 Server, e-Server and ESVT Installation....................................................... 17
2.3 Console Station, Flex Station, and EST installation.................................. 21
2.4 e-Server Premium Access Client Installation............................................. 23
2.5 ACE/ACE-T Installation................................................................................. 24
2.6 SIM-C200, Remote Engineering and Station Server Installation.............. 27
2.7 EMB servers and EMB clients Tools Update Installation ......................... 29
2.8 Considerations for installing LCNP4E driver on all T-Nodes (1-DCC3CT)30
2.9 About Migrating Controllers ........................................................................ 30
2.10 Reapplying software patches on Servers ............................................... 30
About the patch number .......................................................................................................31
3. REMOVING SUPPORT SOFTWARE...........................................33

3.1 Removing patches ........................................................................................ 33
3.2 Server, e-Server, and ESVT Tools Update Removal.................................. 33
R310.2 Experion Support Software Change Notice vii

Contents
3.3 Console Station, EST, EMB Servers, EMB Clients, ACE, SIM-C200, Remote
Engineering and Station Server Tools Update Removal......................................36
4. DOCUMENTATION UPDATES/ADDITIONAL INFORMATION .. 37

4.1 NIC Replacement ...........................................................................................37
NIC configuration rules........................................................................................................ 37
NIC configuration tasks ....................................................................................................... 38
4.2 Support for new functions ............................................................................39
DSA Inter-Release support ................................................................................................. 39
Digital Video Manager Support............................................................................................ 39
Experion PHD Tag synchronization support........................................................................ 39
Third party terminal server support...................................................................................... 39
4.3 Changes in functions ....................................................................................40
Change of recommended OPC channel connect time ........................................................ 40
Change of behaviour for SCADA bitwise parameters.......................................................... 40
Changes to Read Only Alphanumeric events in R310 ........................................................ 40
Change of behaviour when Multi-Window Station reconnects ............................................ 41
4.4 Other updates ................................................................................................42
Summary display view migration ......................................................................................... 42
Header file for Network API client application ..................................................................... 42
Configurating Station onto the exception list of Windows Data Execution Prevention......... 42
4.5 OPC Integrator updates ................................................................................42
Ordering Rules .................................................................................................................... 43
OPC Integrator local transport enabler................................................................................ 43
5. SPECIAL CONSIDERATIONS .................................................... 45

5.1 OEM Embedded OS (EXPPlus R311.5) for EPKS R3xx and TPS R4xx
releases (CR 891)......................................................................................................45
5.2 New platform hardware .................................................................................46
5.3 Disabling server NIC adapters while online causes abnormal operation46
5.4 Considerations for EXPPlus installation – Client/Server Initialization
Media R311.5 .............................................................................................................48
Taking a backup of configuration files ................................................................................. 48
5.5 Consideration for floppy drive usage with New Dell Hardware (T310, T610,
R710, and T5500) ......................................................................................................49
5.6 Considerations for using Dell Reinstallation Operating System (OS) Media
50
viii Experion Support Software Change Notice R310.2

Contents
Considerations for using Windows Server 2003 SP1 Media for loading Experion R301.1.002
.............................................................................................................................................50
Considerations for using Dell Windows Re-installation Operating System (OS) Media .......50
Dell Reinstallation Operating System (OS) Media Compatibility Matrix ...............................50
5.7 Consideration for loading Common Component type software from the
support media (PAR 1-8CP051) .............................................................................. 52
6. KNOWN ISSUES..........................................................................53
6.1 Server ............................................................................................................. 53
Eng-EM Engineering ............................................................................................................53
Installation and Migration .....................................................................................................53
6.2 Console Station ............................................................................................. 53
Console Station....................................................................................................................53
6.3 Client .............................................................................................................. 54
Quick Builder........................................................................................................................54
Station ..................................................................................................................................54
6.4 Knowledge Builder........................................................................................ 55
7. SPECIAL CONSIDERATIONS FOR SYSTEMS WITH PROCESS

POINTS .................................................................................................57
7.1 Phase and Goto Behavior in R300.1 ........................................................... 57
About Goto behavior ............................................................................................................57
Default configurations for parameters on the Phase Settings tab ........................................57
Default RCM Projection and Propagation settings ...............................................................58
Parameter Id error when using the Table View Goto dialog .................................................58
Going away from an active Phase block ..............................................................................58
Going to an inactive Phase block .........................................................................................58
RCM reaches Phase block whose underlying SCM is already Running ..............................59
7.2 Control Functions ......................................................................................... 59
621 IO-LIOM ........................................................................................................................59
C300 Controller ....................................................................................................................60
CDA-Embedded ...................................................................................................................60
CF-Control Function .............................................................................................................61
CK-Control Kernel ................................................................................................................61
Control Firewall 9Port...........................................................................................................64
I/O-Chassis-Series A............................................................................................................64
I/O-Profibus ..........................................................................................................................64
I/O-Series C .........................................................................................................................65
OPM-Controller Migration.....................................................................................................65
R310.2 Experion Support Software Change Notice ix

Contents
7.3 Engineering Tools .........................................................................................68

Checkpoint .......................................................................................................................... 68
Knowledge Builder Contents ............................................................................................... 73
Control Builder..................................................................................................................... 73
Control Builder-Browser ...................................................................................................... 86
Control Builder-Point Picker ................................................................................................ 87
CTools................................................................................................................................. 87
Enterprise Model Builder ..................................................................................................... 88
Fieldbus Library Manager.................................................................................................... 88
Installation-Engineering Tools ............................................................................................. 89
Installation-Experion Station TPS........................................................................................ 90
IXP-Import Export................................................................................................................ 90
LCNP4................................................................................................................................. 92
Ntools .................................................................................................................................. 93
OPM-Migration Readiness Tool .......................................................................................... 93
OPM-On Process Migration ................................................................................................ 93
QVCS .................................................................................................................................. 94
Search engine ..................................................................................................................... 95
SIM-C300 ............................................................................................................................ 96
Table View .......................................................................................................................... 96
7.4 Operational.....................................................................................................97
CDA-Control Data Access ................................................................................................... 97
Detail Displays................................................................................................................... 100
Experion Station-Gus Display............................................................................................ 101
GLC-Generic Comm Layer................................................................................................ 102
Honeywell Communications Interface ............................................................................... 102
OPC Gateway ................................................................................................................... 103
Redirection Manager ......................................................................................................... 103
7.5 Advanced Control........................................................................................104
System Management ........................................................................................................ 104
7.6 Miscellaneous ..............................................................................................104
Network-CNI...................................................................................................................... 104
RSLinx............................................................................................................................... 104
SE-Sys Engr...................................................................................................................... 105
Third Party Components ................................................................................................... 105
8. PROBLEMS RESOLVED IN THIS UPDATE............................. 107

8.1 Control Functions........................................................................................107
C300 Controller ................................................................................................................. 107
CF-Control Function .......................................................................................................... 107
CK-Control Kernel ............................................................................................................. 108
Control Firewall 9Port........................................................................................................ 108
Fieldbus Interface Module ................................................................................................. 108
x Experion Support Software Change Notice R310.2

Contents
Fieldbus Interface Module-Series C ...................................................................................108

I/O-Serial Interface .............................................................................................................108
I/O-Series C .......................................................................................................................109
ModBus TCP Infrastructure................................................................................................109
Network-FTE Bridge...........................................................................................................109
OPM-Controller Migration...................................................................................................110
Redundancy-RM ................................................................................................................110
SCM-Sequential Control Module........................................................................................110
UCF-Unit Control Function .................................................................................................111
8.2 Engineering Tools ....................................................................................... 112
CEE Database ...................................................................................................................112
Checkpoint .........................................................................................................................112
Control Builder ...................................................................................................................113
Control Builder-Browser .....................................................................................................116
Control Builder-CAB...........................................................................................................116
CTools................................................................................................................................116
DDManager........................................................................................................................116
Enterprise Model Builder ....................................................................................................116
Installation-Engineering Tools ............................................................................................116
IXP-Import Export...............................................................................................................117
ModBus TCP Network support and Equipment..................................................................117
OPM-Migration Readiness Tool .........................................................................................117
OPM-On Process Migration ...............................................................................................117
QVCS .................................................................................................................................118
SIM-C300 ...........................................................................................................................118
SIM-FFD.............................................................................................................................118
Table View .........................................................................................................................118
8.3 Operational Functions ................................................................................ 119
CDA-Control Data Access..................................................................................................119
Detail Displays ...................................................................................................................119
GCL-Generic Comm Layer.................................................................................................123
OPC Gateway ....................................................................................................................123
8.4 Supervisory Control Functions ................................................................. 124
CAB-Runtime .....................................................................................................................124
Network-CNI.......................................................................................................................124
8.5 Server ........................................................................................................... 124
Batch Reporting .................................................................................................................124
Display Subsystem.............................................................................................................124
GDA Points ........................................................................................................................125
History Subsystem .............................................................................................................125
Internationalization Infrastructure .......................................................................................125
License Management .........................................................................................................126
Notification Management....................................................................................................126
Notification Presentation ....................................................................................................126
R310.2 Experion Support Software Change Notice xi

Contents
OPC Alarm/Event Client .................................................................................................... 126

OPC Data Client (Flexible) ................................................................................................ 126
OPC HDA Server .............................................................................................................. 126
Operator Security .............................................................................................................. 127
PHD Tag Sync................................................................................................................... 127
Point/Group displays and faceplates ................................................................................. 127
Reports.............................................................................................................................. 127
Scanning ........................................................................................................................... 127
8.6 Console Station ...........................................................................................128
Console Station ................................................................................................................. 128
8.7 Client .............................................................................................................128
HMIWeb Display Builder ................................................................................................... 128
Quick Builder ..................................................................................................................... 128
Station ............................................................................................................................... 129
9. APPENDIX................................................................................. 131
9.1 Honeywell Software Components and Revisions ....................................131
Checking software versions and revisions ........................................................................ 131
Experion PKS Software Components for Systems with Process Points............................ 131
Experion PKS Server/Client Software Revisions............................................................... 134
Experion Common Components Software Revisions........................................................ 135
Honeywell Application Software Revisions........................................................................ 136
9.2 Other third-party software components....................................................137
External, Third Party Qualified Software Components ...................................................... 140
9.3 Microsoft Security Information and Qualified Anti-Virus Packages ......142
For latest information......................................................................................................... 142
Qualified Anti-Virus Packages ........................................................................................... 142
9.4 Component Revisions for Optional SCADA Interfaces ...........................143
9.5 Firmware Revision File Reference .............................................................144
9.6 Hardware/Firmware Components ..............................................................151
About firmware revisions ................................................................................................... 151
Series C I/O Hardware/Firmware Components ................................................................. 151
Controller Hardware/Firmware Components ..................................................................... 154
Communication Hardware/Firmware Components............................................................ 154
I/O hardware/firmware components .................................................................................. 156
Series H Din Rail I/S Hardware/Firmware Components .................................................... 159
Fiber Optic Communication Components.......................................................................... 159
Series A DIN Rail Hardware/Firmware Components......................................................... 161
PM I/O Hardware/Firmware Components ......................................................................... 162
xii Experion Support Software Change Notice R310.2

1. About R310.2 Support Software
1.1 Review the latest information
Checking for updates on online Support
This Software Change Notice contains information for all users of the Experion Software
Support media revision R310.2.
Before installing any software, check the Online Support site at
http://hpsweb.honeywell.com for further software or documentation updates including
updates to this SCN. If you are a new user, you can register for access to the Online
Support site at the URL.
To check the Honeywell Online Support site:

1. In your web browser application, type the following URL:
http://hpsweb.honeywell.com/Cultures/en-US/Support/default.htm
2. Click “Login to My Account”.
3. Type your user name and password, and then click Login.
4. Click System Products in the “Support” links section.
5. Click the Experion Platform link.
6. Click any subsystem link under “Experion Platform” to see the latest Product Documentation,
Notifications and Software Downloads for that subsystem or:
7. Under “Download Links”, click:
All Software Downloads link to check for software updates
All Notifications link to check for notification updates
Those not able to access the "Honeywell Online Support" can obtain the updates by
contacting their Regional Technical Assistance Center.
R310.2 Experion Support Software Change Notice 13

1. About R310.2 Support Software
1.2. Applicability of R310.2 Support Software
1.2 Applicability of R310.2 Support Software

This update applies to the following:
 Experion Server
 Experion Console Station
 Experion Flex Station/Experion Console Extension Station
 Experion Station TPS (EST)
 Experion Server TPS (ESVT)
 EMB Server (R310.2 tools update only)
 EMB client (R310.2 tools update only)
 EHG R310.2 SM 2 is applicable to EHG Nodes
 e-Server
 ACE
 SIM Cx00
 Remote Engineering and Station Server
Other support information
 Field Device Manager has not yet been qualified for the Experion R310 release.
 McAfee 8.5 Patch 5 has been certified with R310.2
1.3 Contents of this Update

This update contains the following software.
 R310.2 Server/Client Update Rev H.
 R310.2 Tools/Controller Update Rev 3
 R310.2 CAB Update
 R310.2 Common Components Update
 Microsoft Windows Installer Hotfix
ATTENTION
The R310.2 Controller Patch 1 must be installed before any of the C200 and
C300 controllers are updated to R310.2. This patch can be retrieved from
OLS. Installation details are included in the accompanying SCN.
14 Experion Support Software Change Notice R310.2

2. Installing Support Software
2.1 Preparing for Installation
Installation scenarios
The following table describes the possible installation scenarios for the R310.2 support
software and identifies sources for additional information.
Scenario For further information
Factory installation Follow the instructions in the Experion Software

Clean installation Installation User’s Guide for Experion R310.2
Migration from R2xx or R301.x Follow the instructions in the Experion R310.2
release to R310.x Migration User's Guide
Update from R310.1 to R310.2 Follow the instructions in this section.

Note: Honeywell only supports an off-process
update for this scenario.
Installation order
Update nodes in the following order:
Order of Nodes
migration
1 Server, e-Server, ESVT
2 Console Station, Flex Station, EST
3 e-Server premium access client
4 ACE
5 SIM-C200, Remote Engineering and Station Server
6 EMB servers and EMB clients
7 C200/C300 controller nodes

2.1. Preparing for Installation
Verifying the version of Experion installed on the node

Use this procedure to verify the node being updated has Experion R310.1 installed on it. If it
does not, you will need to follow the instructions in the Experion Software Installation User’s
Guide for Experion R310.2 or the Experion R310.2 Migration User's Guide.
Step Action
To verify Experion version for EMB Server and EMB client:

1 Choose Start > Control Panel > Add/Remove Programs.
2 Select Enterprise Model Builder and then Click here for support information.
3 Verify that the Enterprise Model Builder with product version is 310.1.65.0.
To verify Experion version for all other nodes:

4 Navigate to
C:\Program Files\Honeywell\Experion PKS\ProductVersion.txt
5 Right-click ProductVersion.txt and choose Open With > Notepad.
6 If the line “Experion PKS R310.1.06.0 Media Revision 5(or higher),
installed…” is present, your system is at the correct version to apply this
update.
If it is not, this update cannot be applied to your system. Contact your local
Honeywell TAC for assistance.
Loss of view during installation of Support Software

Since Honeywell only supports an off-process installation of the R310.2 Support Software,
you will experience a complete loss of view during the R310.2 installation.
Backing up all nodes
Honeywell recommends that you backup your system before installing the Experion Support
Software R310.2.
Special considerations when migrating Flex nodes
Be aware that when migrating Flex (and CE) stations that are running Windows XP any
installed Experion GUS packages (GUS Display Builder, GUS Display Runtime) must be
removed from the node before starting the migration, and reinstalled manually after migration
has completed.

2.2. Server, e-Server and ESVT Installation
Virus Scanning and Protection

Virus Scanning / Protection should be DISABLED before any updates are applied / installed.
After all updates are completed, virus scanning and protection must be RE-ENABLED.
EBR Client and Logger Services
Both the Symantec LiveState Recovery service and the DVM Logger service, if present,
should be DISABLED prior to applying updates. After updates are complete these services
must be RE-ENABLED.
2.2 Server, e-Server and ESVT Installation

To install R310.2 support software update on a redundant server system, do the following:
• Install the software following the procedure below on ServerB first.
• Repeat the procedure to install the software on ServerA.
For a non-redundant server follow this procedure once, ignoring the extra steps for redundant
servers.
Step Action
1 Log on to the server using an account with membership in the local
administrators group and the Honeywell administrators group.
Preparing a redundant server (go to step 6 if there is no redundant server)

2 Synchronize the ERDB, EMDB, and servers.
3 Check for Active Locks in ERDB and EMDB, if applicable.
From Configuration Studio:
 Check for Active Locks in ERDB, by selecting "Administer Control
Strategy Database" while connected to the Server.
 Check for Active Locks in EMDB, by selecting "Administer System
Database" while connected to the System.
If any Active Locks exist:
 Use Clear Active Locks option in the Database Administration tool.
4 Backup the ERDB and EMDB.
5 Upload controller (ACE, C200, C300).
Updating server nodes

6 Create an image of the node to return to if the update is not successful.
7 Close all running applications.

Step Action
8 Shut down Experion services:
 Using the Experion PKS Server Start/Stop program, change the Server
State to “Database Unloaded” in Full mode.
 Once the state has changed to Database Unloaded, close the Start/Stop
Program.
9 Shut down system management:
 Choose Start > Run and then type stopsmservices and then click OK.
 A Command window appears while the System Management services are
set to disabled and then stopped. System Management services are stopped
when the Command window closes.
10 Shut down Engineering tools:
 Using the Engineering Tools Services Control Panel, select Stop All
including SQL and click OK.
 The services will be stopped and the Control Panel will exit when it has
finished.
11 Install the support software:
 Insert the R310.2 Support Software DVD in DVD drive or if installation is
from network then map the location where Support media is located to
network drive.
 Using Windows Explorer, browse the contents of the DVD and double-
click the SupportSetup.exe. The Update Installation(s) screen
appears.
 Click Next.
12 a) From the Installation Confirmation screen appears.

 Click Install to begin the installation. The installation begins.
 Follow the instructions on the Installation screen to observe if there are
any errors. After the installation is completed, the Installation
Complete screen appears.
 Click Finish.

Step Action
Verifying the updates are successful

13 Verify the Tools update was successful:
 Using notepad, open the C:\Program Files\Honeywell\Experion
PKS\ProductVersion.txt file.
 Verify the following line is present:
 Experion PKS Tools Update R310.2 Installed - (310.1.06.34), DAY
MM/DD/YYYY, HH:MM:SS AM/PM.
 If the line is present, the update was successful.
14 Verify the CAB update was successful:

 Using notepad, open the C:\Install\Inst_R310_2_CAB.log file.
 R310_2_CAB Installation successfully completed
15 Verify the Server/Client update was successful:

PKS\Server\Setup\Software Update Log.txt file.
 Experion PKS Server-Station R310.2 (EXPS_SC_310.2-32.0)(RevM)
installed on DAY MM/DD/YYYY, HH:MM:SS
16 Verify the Common Component update was successful:

 Using notepad, open the C:\Install\CC_Wrapper_Patches.log file.
 Verify the file does not contain any "Error" messages.
 If no error messages are present, the update was successful.
 If error messages are present, contact your Honeywell TAC for support.

Step Action
Restarting the Server

17 Restart the Server.
 If the computer had FTE installed, after the restart the computer must be
logged into to finish updating the FTE Driver. Click “Yes” to the prompt “The
FTE Driver has been updated. You must Restart your computer for the
updates to take effect. Do you want to reboot now?”
19 Start Station.
20 Rebuild checkpoint and save manual checkpoint. For all controllers
Note: May have to be done after server migration and again after controller
migration.
Updating redundant Servers (skip steps 21-25 for non-redundant server)

21 From Configuration Studio, enable Replication for ERDB and EMDB, if
applicable.
Note: This step must be done from ServerB
22 Synchronize the Servers.
23 Force Server failover.
25 Repeat the steps in this table for the redundant server

2.3. Console Station, Flex Station, and EST installation
2.3 Console Station, Flex Station, and EST installation

Use this procedure to update clients and Flex Stations.
Step Action
1 Log on to the system using an Administrator account.
network drive.
click the SupportSetup.exe. The Update Installation(s) screen
appears.
 Click Next.
4 b) When the Installation Confirmation screen appears.

any errors. After the installation is completed, the Installation
Complete screen appears.
 Click Finish.

MM/DD/YYYY, HH:MM:SS AM/PM


2.3. Console Station, Flex Station, and EST installation
Step Action
 Using notepad, open the Log.txt file.
 For Console Stations and ESTs the file is located in C:\Program
Files\Honeywell\Experion PKS\Server\Setup\Software Update.
 For Flex Stations, the file is located in C:\Program
Files\Honeywell\Experion PKS\Client\Setup\Software Update.

9 Restart the system.

 If the computer had FTE installed, after the restart the computer must be

2.4. e-Server Premium Access Client Installation
2.4 e-Server Premium Access Client Installation

Step Action
1 Ensure that the e-Server that is associated with the e-Server premium access
client is already updated.
2 Log on to the system using an Administrator account.
3 Choose Start > Control Panel > Add/Remove Programs and remove the
following programs:
 HMIWeb Browser Runtime.
 Experion PKS Server Client Components.
4 Start Internet Explorer and browse to the eServer Premium Access home
page. For example, browse to http://servername/eServer.
5 Click the appropriate link to install the premium access components.
6 Click the appropriate link to install the server-client components.

2.5. ACE/ACE-T Installation
2.5 ACE/ACE-T Installation

Step Action
Preparing the node

1 In the Control Builder, perform an Upload for the ACE FB from the
Monitoring view.
This ensures that the monitoring ERDB contains the recent information like
tuning constants.
2 Change the ACE CEESTATE to “IDLE”.
3 Shutdown the ACE from Control Builder.
Updating the node

network drive.
click the SupportSetup.exe. The Update Installation(s) screen appears.
 Click Next.
5 From the Installation Confirmation screen:
any errors. After the installation is completed, the Installation Complete
screen appears.
 Click Finish.

MM/DD/YYYY, HH:MM:SS AM/PM

Step Action


10 Restart the node.

If the computer had FTE installed, after the restart the computer must be
Restoring the node

11 Load the ACE and CEE from the Monitoring view in the Control Builder. This
makes the ACE's IMAGEVER parameter accessible for the Checkpoint
Rebuild in the next step.
Do not reload the child tagged blocks (CMs) under the ACE-CEE.

Step Action
12 Rebuild the checkpoint for ACE.
This operation ensures that ACE's latest.cp checkpoint file matches with the
updated ACE.exe that was installed as part of the Support Software update
(steps 4 to 8).
This operation also updates the checkpoint file with the new firmware files.
Checkpoint Rebuild always makes the latest.cp checkpoint file incomplete.
Checkpoint Rebuild is similar to Reload from Monitoring view. However, the
Rebuild operation updates only the checkpoint file. It does not update the
information in the controller.
13 Perform a Checkpoint Restore for ACE using the ACE's latest
cp checkpoint file.
The latest.cp is restored as "Incomplete" as it does not have the runtime
information such as the CM execution states. All blocks are restored, with all
CMs/SCMs being made inactive. This is acceptable as you have not yet
performed a Checkpoint Save after rebuilding the checkpoint.
Do not perform a Checkpoint Save yet.
14 Correct or understand any errors that are observed during the Checkpoint
Restore operation.
15 COLDSTART the ACE-CEE.
16 After the ACE is successfully started, and the CMs/SCMs are made active,
perform a Checkpoint Save.
This ensures that the ACE's latest.cp is enriched with the necessary runtime
information and the correct execution states of the CMs/SCMs.

2.6. SIM-C200, Remote Engineering and Station Server Installation
2.6 SIM-C200, Remote Engineering and Station Server

Installation
Step Action
1 Close all running applications and restart the system.
Updating the node

network drive.
click the SupportSetup.exe. The Update Installation(s) screen appears.
 Click Next.
3 From the Installation Confirmation screen:
any errors. After the installation is completed, the Installation Complete
screen appears.
 Click Finish.

Experion PKS Tools Update R310.2 Installed - (310.1.06.34), DAY
MM/DD/YYYY, HH:MM:SS AM/PM.

R310_2_CAB Installation successfully completed.

2.6. SIM-C200, Remote Engineering and Station Server Installation
Step Action
Experion PKS Server-Station R310.2 (EXPS_SC_310.2-32.0)(RevM)



2.7. EMB servers and EMB clients Tools Update Installation
2.7 EMB servers and EMB clients Tools Update Installation

Step Action
1 Insert the R310.2 Support Software DVD in DVD drive.
2 Using Windows Explorer, browse the contents of the DVD and double-click
the Setup.exe in the R310.2_Tools_Update_Rev2 folder.
The Welcome to Experion PKS Engineering Tools R310.2 Update
screen appears.
Note: If any of files to be installed are missing, an error message is
displayed. Click No to abort the installation and report the issue to your local
Honeywell TAC.
3 If all files for installation are available, the installation begins and the status
dialog box is displayed.
4 After the installation is completed, the Installation Complete screen
appears. Click Finish.
5 Verify that the Tools Update R310.2 is installed by clicking Start> Control
Panel and then Add/Remove Programs and making sure the R310.2 Tools
Update entry is present.
6 To verify the installation, perform the following:
Verify if Tools Update installation by examining the contents of file C:\Program
Files\Honeywell\Experion PKS\ProductVersion.txt.
If the line Experion PKS Tools Update R310.2 Installed - ( 310.1.06.34), DAY
MM/DD/YYYY, HH:MM:SS AM/PM is present then the update is successfully
installed.
If the installation is not successful, contact your Honeywell TAC for support.

2.8. Considerations for installing LCNP4E driver on all T-Nodes (1-DCC3CT)
2.8 Considerations for installing LCNP4E driver on all T-

Nodes (1-DCC3CT)
ATTENTION
After completing the Experion installation on all T-Nodes, you must refer to
R311.5 EXPPlus Software Change Notice (SCN) for installing LCNP4E on T-
Nodes.
 For instructions on installing the LCNP4E using EXPPlus media, refer to
the R311.5 EXPPlus Software Change Notice (SCN).
 For instructions on installing the LCNP4E without EXPPlus media, refer to
the R311.5 EXPPlus Software Change Notice (SCN).
2.9 About Migrating Controllers

 For updating firmware, refer to the Control Hardware and I/O Module Firmware Upgrade Guide
in Knowledge Builder for firmware upgrading instructions. Failure to follow these firmware upgrading
instructions could render modules as unusable.
 For the CF-9 modules, refer to Experion Control Firewall Users Guide in Knowledge Builder for
upgrade instructions.
 For the current firmware version information, see Section 9.5, "Firmware Revision File Reference"
in the appendix of this document.
2.10 Reapplying software patches on Servers

You may have applied patches for specific Server issues. Some of these patches may not be
included in R310.2.
Use the following list to determine if you need to reapply any of the updates that are not
included in R310.2 If you have applied a patch with a patch number greater than the number
for the respective release level you may need to obtain and reapply a newer version of the
update that is compatible with Experion Server/Client R310.2 release.
Release Level migrating from Patch Number
R21X Release
R211.1 775 or above
R211.1.S01 650 or above
R30X Release

2.10. Reapplying software patches on Servers
R301.1.002 383 or above
R301.1.002.S01 670 or above
About the patch number

The patch number is embedded in the name of the patch file.
ISRxxxxx.PatchNumber.PKS.301.zip.
ISRxxxxx = The ISR number that this update is generated from
PatchNumber= The patch number.
Example: ISR62899.515.PKS.301.zip
ISRxxxxx = ISR62899
PatchNumber = 515
Refer also to the patch install log, for the history of patches applied on the node. The default
location of this log file is:
For Server/ESVT/Console Station: C:\Program Files\Honeywell\Experion
PKS\Server\Setup\Software Update log.txt.
For Flex Station/EST: C:\Program Files\Honeywell\Experion PKS\Client\Setup\Software
Update log.txt.

2.10. Reapplying software patches on Servers

3. Removing Support Software
3.1 Removing patches
Patch Removal Instructions
Server-Client Update Patches are removed during Experion Software

Remove/Upgrade. No manual steps are needed to
Common Components Update remove this patch.
CAB Update Remove by double clicking the exe

C:\install\remove_r310_2_cab.exe.
3.2 Server, e-Server, and ESVT Tools Update Removal

To remove R310.2 tools update on a redundant server system, do the following:
 Remove the tools following the procedure below on ServerB first.
 Repeat the procedure to remove the tools on ServerA.
To remove the R310.2 tools update on a non-redundant server, follow this procedure
once, ignoring the extra steps for redundant servers.
Step Action
2 Verify that the R310.2 tools update is installed on your system by running
Notepad and opening the file C:\Program Files\Honeywell\Experion PKS\
ProductVersion.txt.
If the line Experion PKS Tools Update R310.2 Installed - (310.1.06.34), DAY
MM/DD/YYYY, HH:MM:SS AM/PM is present, R310.2 is installed.
Preparing a redundant server (go to step 6 if there is no redundant server)

3 Synchronize the ERDB, EMDB, and servers.
4 Check for Active Locks in ERDB and EMDB, if applicable.
From Configuration Studio:
 Check for Active Locks in ERDB, by selecting "Administer Control
Strategy Database" while connected to the Server.
 Check for Active Locks in EMDB, by selecting "Administer System
Database" while connected to the System.

3.2. Server, e-Server, and ESVT Tools Update Removal
Step Action
If any Active Locks exist:
 Use Clear Active Locks option in the Database Administration tool.
5 Backup the ERDB and EMDB.
Removing from server nodes

7 Shut down Experion services:
 Using the Experion PKS Server Start/Stop program, change the Server
State to “Database Unloaded” in Full mode.
 Once the state has changed to Database Unloaded, close the Start/Stop
Program.
8 Shut down system management:
 Choose Start > Run and then type stopsmservices and then click OK.
 A Command window appears while the System Management services are
set to disabled and then stopped. System Management services are stopped
when the Command window closes.
9 Shut down Engineering tools:
 Using the Engineering Tools Services Control Panel, select Stop All
including SQL and click OK.
 The services will be stopped and the Control Panel will exit when it has
finished.
10 Remove the support software:
 Using Windows Explorer, browse to the c:\install folder and double-click
the Remove_R310.2_Engineering_Tools_Update_32.exe.
 Click Continue on the Welcome to Experion PKS R310.2 Uninstaller
dialog box to proceed with the R310.2 tools update removal operation.
Note: If any of the files to be restored are missing from the system, then
a message box “Some files needed for restoration are missing...” is
displayed. Click No to abort the removal and then report this issue to
your local TAC.
The status dialog box is displayed while the software is being removed.
 Click OK to finish the R310.2 tools update removal.

3.2. Server, e-Server, and ESVT Tools Update Removal
Step Action
11 Verify the Tools removal was successful:
 Verify the following line is present: Experion PKS Tools Update
R310.2 Removed.
If the line is present, the update was successful.
Restarting the Server

12 Restart the Server.
14 Start Station.
15 Rebuild checkpoint and save manual checkpoint. For all controllers
Note: May have to be done after server migration and again after controller
migration.
Updating redundant Servers (skip steps 16-19 for non-redundant servers)

16 From Configuration Studio, enable Replication for ERDB and EMDB, if
applicable.
Note: This step must be done from ServerB.
18 Force Server failover.

3.3. Console Station, EST, EMB Servers, EMB Clients, ACE, SIM-C200, Remote Engineering and
Station Server Tools Update Removal
3.3 Console Station, EST, EMB Servers, EMB Clients,

ACE, SIM-C200, Remote Engineering and Station Server
Tools Update Removal
Step Action
1 Verify that the R310.2 tools update is installed on your system by running
Notepad and opening the file C:\Program Files\Honeywell\Experion PKS\
ProductVersion.txt..
If the line Experion PKS R310.2 Installed - (310.1.06.34)... is present, R310.2 is
installed.
For EMB servers and EMB clients:
Verify that the Tools Update R310.2 is installed by choosing Start> Control
Panel and then Add/Remove Programs to see if the entry R310.2 Tools
Update is present.
3 Using Windows Explorer, browse to C:\Install folder and double-click
Remove_R310.2_Engineering_Tools_Update_34.exe and then close the
Windows Explorer.
4 Click Continue on the Welcome to Experion PKS R310.2 Un-Installation
dialog box to proceed with the R310.2 tools update removal operation.
Note: If any of the files to be restored are missing from the system, then a
message box “Some files needed for restoration are missing...” is displayed.
Click No to abort the removal and then report this issue to your local TAC.
5 Click OK to finish the R310.2 tools update removal.
6 Verify that the update is removed from your system by running Notepad and
opening the file C:\Program Files\Honeywell\Experion PKS\ ProductVersion.txt. If
the line Experion PKS R310.2 Removed - (310.1.06.34) is present, R310.2 is
removed successfully.
For EMB servers and EMB clients:
Verify that the Tools Update R310.2 is removed by choosing Start> Control
Panel and then Add/Remove Programs and ensure the R310.2 Tools Update
entry is not present.
7 Restart the node.

4. Documentation Updates/Additional Information
This section contains updated information not included in the standard documentation.
4.1 NIC Replacement

The dual Broadcom onboard NICs replace the Intel Dual NICs for FTE on the Honeywell
platforms based on Dell servers (PE2900 and PE2950). This qualification is complete. The
Broadcom onboard NIC/NICs can be used for other (non-FTE) network connections on all of
the supported servers (SC1430, PE2900, and PE2950).
NIC configuration rules
These rules are applicable for Honeywell platforms based on the PE2900, PE2950, SC1430,
T610, and R710 Servers only.
Honeywell Configurations that include FTE General Ethernet

Platforms Configurations:
Honeywell  Broadcom onboard NICs are enabled  1 or 2 NICs = Enable

platforms based from factory. onboard Broadcom NIC(s).
on PE2900,  If FTE on PE2900 or PE2950 then  3 NICs = Enable onboard
PE2950, and either onboard Broadcom NICs or PCI-X Broadcom NIC(s) plus add PCI-
SC1430 Servers Intel Pro 100/1000 Dual NIC card is used. If X based Intel single NIC card.
FTE on SC1430 then PCI-X Intel Pro
100/1000 Dual NIC card is used.
Honeywell  Broadcom dual embedded GB NICs are  1 or 2 NICs = onboard

platforms based enabled without PXE in System BIOS from Broadcom NIC(s) are enabled
on T610 and factory. without PXE.
R710 Servers  For FTE only configuration, onboard  3 NICs = onboard
NICs are used. Broadcom NICs plus a PCIe
 For FTE, EHG, and Card Single NIC based Intel Single NIC card.
PCIe Server for EHG configuration,  4 NICs = onboard
Broadcom onboard NICs for FTE are used. Broadcom NICs plus a PCIe NIC
Card PCIE dual port STP.

4.1. NIC Replacement
NIC configuration tasks

The following chart defines actions to be taken for each configuration.
Honeywell FTE Only FTE Only No FTE, but 1 No FTE, 3 No FTE, 4

platforms based (SC1430) (PE2900, or 2 Ethernet Ethernet Ethernet
on SC1430, PE2950, T610, ports ports ports (T610,
PE2900, PE2950, R710 ) R710)
T610, R710
PCI-X Intel Pro Install None None None Not

100/1000 Dual applicable
NIC
Broadcom Dual Disable Enable two Enable two Enable Enable two
Onboard NIC (through NICs (through NICs (through two NICs NICs
BIOS BIOS settings) BIOS (through (through
settings) settings) BIOS BIOS
settings) settings)
PCI-X Single NIC None None None Install Not

Board applicable
PCI-e Single NIC Not None None Install None

Board applicable

4.2. Support for new functions
4.2 Support for new functions

DSA Inter-Release support
DSA Inter-Release is supported for the following:
 Experion PKS R211.1
 Experion PKS R301.1
 Enterprise Building Integrator R310.2
Digital Video Manager Support
Digital Video Manager R200.2 supports this release of Experion.
Experion PHD Tag synchronization support
Changes made to range, units and Description for TPS point parameters through Native
Window are automatically detected and synchronized with PHD.
Third party terminal server support
The CISCO 2610 and Stallion Easy II terminal servers are no longer supported. The
replacement for these terminal servers is the Systech terminal server: models RCS 6108 (8
ports), and RCS 3282 (2 ports).

4.3. Changes in functions
4.3 Changes in functions

Change of recommended OPC channel connect time
In Experion R310.2 it is recommended that the minimum OPC channel connect timeout be set
to 20 seconds rather than 10 seconds. With the introduction of Windows 2003 SP1 and
Windows XP SP2 it has been found that initial OPC channel connection to third party OPC
Servers can take longer due to Windows security changes in these releases. The change is to
prevent the OPC channel connection from timing out. The connect timeout change is made via
the OPC Client channel main properties page for each OPC channel in Quick Builder. After
making the change the channel will need to be downloaded to Experion.
Change of behaviour for SCADA bitwise parameters
Prior to the R310 release, SCADA bitwise parameters were returned as type VT_BOOL
through the Experion OPC DA Server on the process server itself and as VT_I2 via the
Experion OPC DA Server on a DSA connected EAS (Experion Application Server). The
software has been corrected so that the Experion OPC DA Server will return VT_I2 in both
cases. Refer to the Configuration Guide for more details.
Changes to Read Only Alphanumeric events in R310
The order in which the OnMouseDown and OnActivate events fire to a parent element has
changed in R310. The following table describes the events that occur when clicking on a read
only alphanumeric. Note that only events for Read Only Alphanumeric have been changed.
Events order for Read Only Alphanumeric
Pre R310 Behavior R310 Behavior
Alpha | OnMouseDown Alpha | OnMouseDown

Page | OnMouseDown Alpha | OnActivate
Alpha | OnActivate Page | OnActivate
Page | OnActivate Page | OnMouseDown
Page | OnBlur Page | Onblur
Alpha | OnFocus Alpha | OnFocus
Alpha | OnMouseUp Alpha | OnMouseUp
Page | OnMouseUp Page | OnMouseUp
Alpha | OnClick Alpha | OnClick
Page | OnClick Page | OnClick
The events order for Data Entry Enabled Alphanumeric remains the same as described in
the table below.

4.3. Changes in functions
Events order for Data Entry Enabled Alphanumeric
Alpha | OnMouseDown
Page | OnMouseDown
Alpha | OnActivate
Page | OnActivate
Page | OnBlur
Alpha | OnFocus
Alpha | OnMouseUp
Page | OnMouseUp
Alpha | OnClick
Page | OnClick
This change only affects custom displays/shapes that write scripts for, parent elements, to
handle the onmousedown and onactivate events. A parent element is any element that contains
the alphanumeric. Typically this is the page element or a group element.
Change of behaviour when Multi-Window Station reconnects
From R310, when a multi-window Station reconnects, it will bring up the Experion Start Up
page instead of showing the previous page it was showing in its last connection. This does not
affect a failover scenario.

4.4. Other updates
4.4 Other updates

Summary display view migration
Custom views for the alarm, event, message, alert, SOE summaries and the system status
display are not migrated when upgrading from a release prior to Experion R30x or when an
operating system change/reinstall is performed. After migrating to Experion R310.2, custom
views will need to be recreated for these scenarios.
Header file for Network API client application
If you encounter an error where “mzero.h” header file is missing during compiling the C/C++
Network API client application, you can manually copy it:
From:
C:\Program Files\Honeywell\Experion PKS\Server\include\src.
To:
C:\Program Files\Honeywell\Experion PKS\Client\NetworkAPI\include\src.
Configurating Station onto the exception list of Windows Data Execution Prevention
Honeywell recommends that the Windows Data Execution Prevention (DEP) exception list be
configured to include Station. This prevents nuisance dialogs and, in some cases, prevents
Station from terminating unexpectedly.
Step Action
1 Choose Start > Run and then type sysdm.cpl, and then click OK.
2 From the Advanced tab, under Performance, click Settings.
3 Verify the following option is selected:
Turn on DEP for all programs and services except those I select
3 Click Add… and browse to the following folder:
\Program Files\Honeywell\Experion PKS\Client\Station
4 Select the following two files:
 Station.exe
 HSCStationWindow.exe
Click OK twice to exit.
4.5 OPC Integrator updates

OPC Integrator is a robust, easily configurable and efficient means of transferring data
between OPC Data Access Servers. It acts as an OPC data client to two OPC data servers to
facilitate the transfer of data between them.
4.5. OPC Integrator updates
Ordering Rules
OPC Integrator is sold on a per Server Application Instance or SAI basis. An SAI is defined as
an OPC Data Access Server Application whose data is being subscribed to by OPC Integrator
on a given machine. This OPC Data Access Server may be on the same or different physical
machine as the Experion Server. If the same OPC Data Access Server resides on two different
physical machines and OPC Integrator is subscribing to data on both machines, this would be
classified as two SAIs.
If multiple transfer groups are connecting to the same physical machine and OPC Data Access
Server, then this is classified as only one SAI.
OPC Integrator local transport enabler
Enabled with all Experion Servers is a free OPC Integrator SAI to the Experion OPC Data
Access Server on the local machine. This free SAI Instance appears on the Experion license as
“OPC Integrator local transport enabler”. This OPC Integrator SAI allows for the
transportation of data on the local Experion OPC Data Access server i.e. where the source and
destination of an OPC Integrator transfer group uses the Experion OPC Data Access Server
progID with an IP address of the local host. All other OPC Integrator connections, other than
the one just mentioned are licensed. In R30x, the Experion OPC Data Access Server does not
need to be licensed for the OPC Integrator local transport enabler to operate. This is a change
from R210 when at least one Experion OPC Data Access Server connection was required in
order for the OPC Integrator local transport enabler to operate.
Example 1
In this example, no licensed OPC Integrator connections would be required because the OPC
Integrator Local Transport Enabler, which is supplied with all Experion Systems, would be
used.
Transfer Group Source Prog ID Source IP Dest Prog ID Dest IP
Transfer Group A Experion Local host Experion Local host

4.5. OPC Integrator updates
Example 2
In this example there would be a total of three Server Application Instances:
 Vendor A running on Local host
 Vendor A running on 192.168.0.1
 Vendor B running on 192.168.0.1
Transfer Group Source Prog ID Source IP Dest Prog ID Dest IP
Transfer Group A Vendor A Local host Vendor A 192.168.0.1
Transfer Group B Vendor A Local host Vendor B 192.168.0.1

5. Special Considerations
5.1 OEM Embedded OS (EXPPlus R311.5) for EPKS R3xx
and TPS R4xx releases (CR 891)
Honeywell has an OEM agreement with Microsoft for supplying Windows Operating
System media for Experion PKS and TPS releases. With EXPPlus R311.5, new
Operating System media is released by Honeywell for Operating System (OS)
installation.
The EXPPlus R311.5 contains the following new components.
 Support for new DELL platforms.
 Windows Operating System Media supplied by Honeywell Process Solutions (HPS)
(also known as HPS Re-installation OS media).
 Support for installation of LCNP4e drivers on new DELL Platforms.

5.2. New platform hardware
ATTENTION
 During clean installation of R310.2 or during migration to R310.2, you
must select R310.2 in the EPC tool.
 In R311.5 EXPPlus media, the Activation tab is replaced with a new tab –
Licensing in the EPCTool.
 The Licensing tab is provided with the option to select whether the Dell
platform has Honeywell embedded COA.
Refer to R311.5 EXPPlus Media Software Change Notice for more details.
5.2 New platform hardware

With R310.2, the following new hardware platforms are supported:
 Dell PowerEdge T105 Server
 Dell PowerEdge R710 Server
 Dell Precision Workstation T3400
Note: These hardware platforms do not support floppy drives. For more information
about the floppy drives, refer to 5.5 Consideration for floppy drive usage with New Dell
Hardware (T310, T610, R710, and T5500) .
5.3 Disabling server NIC adapters while online causes

abnormal operation
Scenario:
Disabling the yellow NIC adapter on the Experion server while running on
control can have undesired effects. The yellow adapter IP address is the one
used by the Experion applications. The FTE driver cannot pass the
application information when the adapter is disabled. The result is a dual
primary situation. This situation can cause loss of view while the servers are
in this mode.
Recovery:
If the yellow adapter is accidentally disabled the following is the recovery
procedure. Refer to section 5.2 of the FTE Installation and Service Guide in
the Knowledge Builder if these steps are not familiar.

5.3. Disabling server NIC adapters while online causes abnormal operation
1. Open the FTE properties page and note down the device index.
2. Clear the yellow and green check boxes. Click OK.
3. If a popup prompts restart, click Cancel. Enable the yellow adapter in
the Adapter properties.
4. Open the FTE properties page. Check the yellow and green boxes.
5. Set the device index to the value that you noted down in step 1.
6. Click OK. The server recovers at this point.
There must be one primary and one secondary server.
Other FTE nodes are subject to the same warning, but it only affects them.
They can be recovered with the same procedure if the yellow adapter is
accidentally disabled.

5.4. Considerations for EXPPlus installation – Client/Server Initialization Media R311.5
5.4 Considerations for EXPPlus installation –

Client/Server Initialization Media R311.5
ATTENTION
 If you have a T5500 workstation (BIOS A02 or lower versions) or R710
Server, change the BIOS settings before installing the new EXPPlus
media R311.5.
Refer to the R311.5 EXPPlus Media Software Change Notice (SCN) for more
information on the change required in BIOS settings.
Taking a backup of configuration files

To backup configuration files from the EPCTool to the new Dell platforms (T5500,
T610, and R710), connect the USB flash drive before booting workstation or servers
from EXPPlus media. The system prompts you to select USB flash drive when you want
to save the configuration files.
For more details about the EXPPlus installation procedure, refer to Experion Software
Installation User’s Guide.

5.5. Consideration for floppy drive usage with New Dell Hardware (T310, T610, R710, and T5500)
5.5 Consideration for floppy drive usage with New Dell

Hardware (T310, T610, R710, and T5500)
Error Indication Recovery Workaround
During migration from Experion releases None To backup configuration files:

R301.X to R310.X the migration c) Select Do not use floppy
application prompts you to select “floppy check box, when you are prompted
drive” in an Experion system. However to take backup of configuration files
the new Dell platforms do not have a during migration.
floppy drive.
d) Use the USB flash drive to
save the configuration files.
To restore configuration files:
a) Do not select Get
information from floppy
check box when you are
prompted to restore
configuration files during
migration.
b) Connect the USB flash drive
and restore the configuration files
from the USB flash drive.
During the final stage of migration from None Click OK when the error message
Experion releases R301.X to R310.X appears and continue the
and vice-versa, the On Process migration.
Migration wizard displays an error
message as “Error 9 (Subscript out of
range) in procedure DeleteRegistryFile
of Class Module Phase3”.
Configuration files cannot be saved c) Connect USB flash drive

using the EPCTool as floppy drive is not before booting from the
supported on the new Dell platforms. EXPPlus Media.
d) Save the configuration files on
the USB flash drive.

5.6. Considerations for using Dell Reinstallation Operating System (OS) Media
5.6 Considerations for using Dell Reinstallation

Operating System (OS) Media
Considerations for using Windows Server 2003 SP1 Media for loading Experion
R301.1.002
Dell PowerEdge R710 and T610 servers are received already loaded with Windows
Server 2003 SP2. For migrations to Experion R301.1.002, the server must be loaded with
Windows Server 2003 Service Pack 1. Hence, the affected server must be initialized and
reloaded to bring it down to that service pack level.
Considerations for using Dell Windows Re-installation Operating System (OS)
Media
Some of the Dell Windows XP and Server 2003 Re-installation OS Media setup stops
during the EXPPlus installation. This occurs due to changes made in these disks. Refer to
the R311.5 EXPPlus media Software Change Notice for the list of affected media part
numbers and workaround if you are using any of the Media mentioned.
Dell Reinstallation Operating System (OS) Media Compatibility Matrix
ATTENTION
Before using any reinstallation media from Dell, refer to Consideration for
using Dell Reinstallation Operating System section for issues and
workaround with the new platforms.
Note: Dell Media part numbers can be found on the bottom of the Operating System (OS)
disk label, preceded by P/N.
Dell Dell Platform Dell Media Part Number

Reinstallation
Media R301.1.002 R301.2 and Other Experion
R310.2 and TPS release
nodes
Dell Windows All qualified Dell R0329 R0329 R0329

Server 2003 servers except on new Note: Note: Service Note: Service
Dell PowerEdge R710 Service Pack 2 is Pack 2 is
(No Service and T610 Servers
Pack contained Pack 1 is installed by installed by
in this Media) installed by EXPPlus media. EXPPlus media.
EXPPlus
media.

5.6. Considerations for using Dell Reinstallation Operating System (OS) Media
Dell Dell Platform Dell Media Part Number

Reinstallation
Media R301.1.002 R301.2 and Other Experion
R310.2 and TPS release
nodes
Dell Windows All qualified Dell MK996 MK996 MK996

Server 2003 servers including new Note: Service Note: Service
Service Pack 1 Dell PowerEdge R710 Pack 2 is Pack 2 is
and T610 Servers installed by installed by
EXPPlus media. EXPPlus media.
Dell Windows All qualified Dell Not YY317 YY317

Server 2003 servers including new applicable
Service Pack 2 Dell PowerEdge R710
and T610 Servers
Dell Windows All qualified Dell KK136, KK136, U5183, KK136, U5183,
XP Professional workstations including U5183, KY938, UT993, KY938, UT993,
Service Pack 2 new Dell Precision KY938, U957G, JY011, U957G, JY011,
Workstation T5500 UT993, TD876 TD876
U957G, Note: Service
JY011, Pack 3 is
TD876 installed by
EXPPlus media.
Dell Windows All qualified Dell Not Not applicable F098F, R272R
XP Professional workstations including applicable
Service Pack 3 new Dell Precision
Workstation T5500

5.7. Consideration for loading Common Component type software from the support media (PAR 1-
8CP051)
5.7 Consideration for loading Common Component type

software from the support media (PAR 1-8CP051)
ATTENTION
You cannot load the additional software packages such as Sign-on Manager
or Experion GUS Display Builder from the R310.2 support media.
Contact Honeywell TAC to load these software packages.

6. Known Issues
This section describes known problems and limitations in this release, including
symptoms and Workarounds.
6.1 Server
Eng-EM Engineering
ISR/ Problem and Workaround
PAR
88240/1-6K3P1V Description: Unable to add TPS tags in ACM ManagerClient by

connecting to EAS having DSA with ESVT301.
Workaround: When entering nodes in Configuration Studio, use the
node name rather than the IP address.
Installation and Migration

PAR
88750 Description: During a migration to R310 when an OS Change or OS

Re-install occurs Custom views on the alarms pages are lost.
Workaround: Manually recreate the views after migrating to Experion
R310.2.
6.2 Console Station

Console Station
PAR
65626 Description: Station stops responding for a short time, or presents an

error dialog on a Console Station when using the OPC Integrator
displays when the server is unavailable.
Workaround: None.

6. Known Issues
6.3. Client
6.3 Client
Quick Builder
PAR
89145 Description: Cancelling the migration wizard while migrating an old

QB project leads to loss of data.
Workaround: 1) Before migrating the project, perform a manual
backup of the project. 2) Do not cancel the migration wizard.
Station
PAR
84407 Description: IE becomes unresponsive when accessing the HPS

support website if HendrixBHO IE add-on is installed.
Workaround:
1. Use Explorer rather than Internet explorer to access the HPS
website, enter "http://hpsweb.honeywell.com/" directly in the
address bar in Explorer. IE will still freeze if it navigates to an
effected page, but the add-on can be left enabled.
2. Disable the add-in in IE, functionality that requires the add-on
will not work. In IE6 go to Tools, Manage Add-ons, and select
HendrixBHO Class and select the Disable radio button in
Settings below the list of add-ons.
85065/1-4C35JO Description: Flex nodes occasionally do not failover to redundant

host.
Workaround: On the Retry/Cancel dialog, click Retry.
85276/1-4EKXSR Description: Refreshing Trend Summary display may result in a

truncated display.
Workaround: Navigate away from the display and then back again.

6. Known Issues
6.4. Knowledge Builder
6.4 Knowledge Builder

PAR Function Description
1-2V4S2T Software Error Indication: Duplicate IP Address condition

Installation can be caused by individually connected nodes
User’s Guide (Non-FTE) on an FTE Node using DHCP after a
cable or switch failure.
Description: Individually connected nodes in an FTE
system may place zeros for the MAC address of the
Green adapter in their ARP Table for an FTE node
using DHCP for IP addressing. This may cause a
duplicate IP address condition on the FTE network
for the FTE Node.
This condition is unique to DHCP nodes that are on
an FTE system recovering from a loss of complete
network communication between the ‘Yellow’ and
‘Green’ side of the network for more than 10
minutes. This causes the individually connected
machines on the FTE network to lose their ARP table
that contains the IP to MAC Address mapping. This
condition could easily cause the ‘Yellow’ adapter to
have the same problem depending on which side of
the network the individually connected nodes are
placed.
Recovery: If this condition is observed, the
individually connected nodes need to be restarted.
To confirm if you have the problem, go to the single
connected node and on the command prompt type
"arp -a" and the following line is displayed:
10.1.4.26 00-02-b3-a7-c2-6c dynamic
10.1.4.27 00-00-00-00-00-00 dynamic
Where, the first entry may be the ‘Yellow’ adapter
which is correct; and the second entry is Green
which is not correct.
The FTE node with the problem will require restarting
as Microsoft does not automatically turn on a
duplicate IP address adapter after the problem is
resolved.
Workaround: None.

6. Known Issues
6.4. Knowledge Builder
PAR Function Description
1-1MJIXD Missing/Incorrec Error description: Refer to description.

tion information Description: The backup of a Dell 360Windows XP
Experion Console Station with Experion Backup
Restore is taken and loaded into a different Dell 360
with the same type of NIC card (Intel Pro 100). The
restored image does not transfer the IP addresses of
the original to the restored system. FTE services are
bound to incorrect NIC cards.
Recovery: None
Workaround: Refer to Fault Tolerant Ethernet
Installation and Service Guide for R3xx for
information on unbinding non-existent adapters and
binding the new adapters to FTE.

7. Special Considerations for Systems with Process
Points
The following describes known problems and limitations found in this release. The
problems and symptoms are stated along with a work around solution.
7.1 Phase and Goto Behavior in R300.1

This section summarizes the current RCM and Phase block behavior in Single Step Mode
when you use the Table View Goto dialog box. This information pertains to pars 1-
1EA5ZV and 1-2W62CS. Refer also to the Sequential Control User’s Guide for
additional information.
About Goto behavior
Goto describes putting an RCM into Single Step Mode, selecting Target Steps/Phases,
and commanding the change of location. Single stepping from one location to another
can be performed from the Status tab of the RCM Properties form, or more commonly
from the Table view Goto dialog box.
Default configurations for parameters on the Phase Settings tab
Following are the parameters on the Phase Settings tab of the Phase block properties
form with their default configurations. If you change the default settings, the behavior
will be different than that described.
Parameter Default
configuration
Acquire Equipment Before Execution (ACQUIREOPT) On
Execute On The Equipment (EXECUTEOPT) On
Wait For Terminal State (TERMSTATEOPT) On
Release Equipment After Execution (RELEASEOPT) On
EQM State Projection Up To Recipe - Override Recipe Level Off

Configuration (EQMTORECENB)
Recipe State Propagation Down To EQM - Override Recipe Off

Level Configuration (RECTOEQMENB)

7. Special Considerations for Systems with Process Points
7.1. Phase and Goto Behavior in R300.1
Default RCM Projection and Propagation settings

The following table lists the RCM State Projection and Propagation settings on the
Recipe Settings tab of the RCM properties form with their default configuration.
Parameter Default
configuration
EQM State Projection Up To Recipe () – EQMTORECMAP [6..8]
Recipe State Propagation down to EQM () - [6..8]

RECTOEQMMAP
Parameter Id error when using the Table View Goto dialog

A Parameter Id error is received for the REEXECOPTOG parameter for the Phase
block(s) that are the destination of a Goto. The error occurs after YES is clicked on the
Goto dialog to execute the requested Goto operation. The error can be safely ignored by
clicking OK on the error dialog, and the Goto operation will be commanded successfully.
This error does not occur when initiating SingleStep mode related commands from the
SCM/RCM properties form or detail display.
Going away from an active Phase block
On leaving an active Phase block in which the underlying SCM is Acquired and
Running, the following occurs:
 Underlying SCM remains Acquired and Running.
 Phase block color is magenta in chart/table view to indicate it is partially complete
On completion of the RCM (either normal processing to completion or a commanded Abort):
 Underlying, “abandoned” SCM is released but is left running.
On Reset of the RCM:
 Abandoned Phase block color in chart/table view is reset to Gray.
Going to an inactive Phase block
When the underlying SCM is not Running, Phase execution is the same as if the Phase
was reached in the normal sequential flow of the RCM.

7.2. Control Functions
RCM reaches Phase block whose underlying SCM is already Running

This scenario can happen when using the Goto to jump around an RCM, or by starting an
RCM again after Goto operations have caused one or more SCMs to be abandoned.
When a Phase block becomes active and encounters an SCM that is already running the
following occurs:
 Phase block State becomes ProcModeTrk and SCM resource is acquired.
 Phase block color in chart/table view becomes magenta.
 If the SCM execution then completes (either through the normal sequential flow or an
operator commanded abort):
 Phase block commands another execution of the SCM (note that if EXECUTEOPT is Off,
then an additional SCM execution is not commanded).
 Phase block color will appear Green and Blue as normal based on the progress of the SCM
execution.
7.2 Control Functions

621 IO-LIOM
PAR Problem and Workaround
1-88I5J5 Description: Under the following circumstances the LIOM may not swap over:
Primary port of the SIOM is removed.
If any of the LSC I/O rack is powered off.
If any of the LSC I/O rack is powered off.
If LIOM RJ45 link port is removed from primary LIOM.
Workaround: To avoid this scenario keep both Primary and Secondary SLINK
Settings as Ceases to Operate.

C300 Controller
1-5A5TAA Error Indication: Loss of one or more connections between a C300 Controller
through an FTEB to Series A I/O.
Description: A network storm introduced by improperly creating a loop on one
CF9 may affect FTEB communications, causing the FTEB to drop I/O
connections from a C300 Controller.
Recovery: Remove improper loop from CF9.
Workaround: None.
1-882D8R Error Indication: Per design, C300 Controllers do not adopt a changed SNTP
configuration until reboot.
Description: The Knowledge Builder recommendation to re-start the bootp
service to update the changed SNTP only updates the bootp service.
Recovery: Reboot of non-redundant C300 Controller or 2 (two) Switchovers of
a Redundant C300 controller will update the SNTP addresses.
Workaround: Refer to Recovery.
CDA-Embedded
1-77ZLOR Error Indication: OFFNET Alarms are Generated.

Description: FIM4 Modules lose connection with all the console stations
when a crossover loop is connected between GREEN and Yellow.
Recovery: This is a momentary failure and will return to normal after about 20
seconds.
Workaround: None
1-78UV9B Error Indication: Loss of exchange connection between a C300/C200

controller connected through a switch to another C300/C200 controller.
Description: During an FTE fault which may occur due to powering down of
one of the L2 switches, the exchange connection between a C300/C200
controller connected to another C300/C200 controller through the switch
breaks. During this scenario, the requestor block immediately changes the PV,
PVFL values to Fail safe.
Recovery: If the logic in ReqNumArray, ReqFlagarray, ReqTextarray block is
setup in such a way that READYFL flag is connected to SENDFL flag, then the
exchange connection recovers after the initial disconnect.
Workaround: None.
1-87ALPD Error Indication: The Push Store momentarily fails when there is a peer


connection between C200 and ACE.
Description: When push blocks are configured to write values from C200 to
ACE, it is seen that sometimes momentarily values are not pushed to ACE
controller. It is seen that the momentary failure lasts for 200ms.
Recovery: It recovers automatically. No user action required.
Workaround: None.
CF-Control Function
1-84BWWS Error Indication: PV will be written to SP one cycle after one shot
initialization if PVTRAKOPT is selected, even if PVTRAKOPTAI is not selected
when in Auto mode.
Description: Tracking occurs for Auto Initialization even when the option is
not selected.
Recovery: Manually or Programmatically adjust the SP value.
Workaround: Don't use either PV Tracking option if SP integrity is required
during One Shot initialization (generally on block activation or through the use
of the CTLINIT parameter).Depend on initialization through the cascade
connection for robust PV tracking and initialization combinations.
1-86QG91 Error Indication: SP does not track PV for PVTRAKOPTAI if scenario is

entered directly from Bad Control, without recovery.
Description: One would expect the SP value to track PV for PVTRAKOPTAI
if the PID is in Auto, and is being initialized from downstream. However, if you
enter this state directly from a Bad Control situation by forcing the Bad PV to a
Manually controlled PV with Manual Status. The PID block SP will not
immediately start tracking this new Manual PV value.
Recovery: The PID must currently recover from Bad Control (Normal PV)
before the PV tracking rearms.
Workaround: Manually change the SP to match the entered Manual PV to
balance loop prior to return from initialization.
CK-Control Kernel
1-5486LT Error Indication: During event regeneration of ACE/C200/C300, it is possible

that Alarm Summary Display falsely indicates that a block is in alarm when
detail display suggests that it is not in alarm.
Recovery: If the Server Alarm Summary Display contains one or more false
indication of alarms existing on a particular controller when detail display


suggests that it is not in alarm, then the following steps should be taken:-
1).If the controller is the source of any chattering alarms that cause more than
10 alarms per second to be reported from the controller, then the alarm rate
must be brought down within controller notification specification of 10 alarms
per second by removing the source of chattering alarms.
2) Disable alarms Server wide. Once alarms have been disabled, re-enable
alarms Server wide. A corrected set of alarms should exist in the Server Alarm
Summary.
Workaround: None.
1-6QGVTH Error Indication: If any C200, Sim-C200, Sim-C300, ACE, Sim-ACE in a

cluster is generating 10 alarm and/or return to normal events per second for a
sustained period of time, then the Server Alarm Summary may not be correct.
Recovery: The Server Alarm Summary will correct itself once no C200, Sim-
C200, C300, Sim-C300, ACE, Sim-ACE in a cluster is generating more than
10 alarm and/or return to normal events per second.
Workaround: Ensure there are no chattering alarms in the system. Chattering
alarms may generate alarms and/or return to normal events at a rate higher
than the controller notification specification of 10 alarms per second, resulting
in some notifications being missed. If the Server Alarm Summary Display
contains one or more false indication of alarms existing on a particular
controller when detail display suggests that it is not in alarm, then the following
steps should be taken: - Disable alarms Server wide Once alarms have been
disabled, re-enable alarms Server wide. A corrected set of alarms should exist
in the Server Alarm Summary.
1-734GWT Error Indication: A redundant C300 controller pair loses sync when CEE is
commanded to transition from RUN to IDLE
Description: A redundant controller pair looses synchronization due to
CleanPoint Overrun because the primary is loaded with a large number of
container blocks that have many component blocks and CEE is commanded
to transition from RUN to IDLE.
Recovery: Open either the Primary / Secondary configuration form and
command synchronization of the redundant controller pair.
Workaround: None.
1-7SLO8D Error Indication: When the Migration Readiness Tool is run prior to migration
the issue of “Dangling Connections” is highlighted as a problem area and the
customer is encouraged to repair this problem before migration. If the
customer chooses to migrate without change, the problem is again highlighted
by the Migration Wizard as “Block at other end of connection missing for block
....”.Customers can choose to continue with migration, resulting in an eventual
Secondary controller crash with the error FAIL 00D1 displayed.


Description: The controller code attempts to access a missing connection via
a NULL pointer, resulting in the crash.
Recovery: Rollback Secondary controller changes (reflash, reload
Secondary), migrate after fixing database.
Workaround: Do not proceed with migration until MRT reports no dangling
connections. Remedy strategies before migration attempt.
1-7T4M4P Error Indication: When the Migration Readiness Tool is run prior to migration
the issue of “Dangling Connections” is highlighted as a problem area and the
customer is encouraged to repair this problem before migration. If the
customer chooses to migrate without change, the problem is again highlighted
by the Migration Wizard as “Block at other end of connection missing for block
....”.Customers can choose to continue with migration, resulting in a failure
during the indirect sync step.
Description: The controller cannot successfully complete a migration with
dangling connections.
Recovery: Rollback Secondary controller changes (reflash, reload
Secondary), migrate after fixing database.
Workaround: Do not proceed with migration until MRT reports no dangling
connections. Remedy strategies before migration attempt.

Control Firewall 9Port

1-76Z4SB Error Indication: Crossover cable connected between two Firewall ports can
cause loss of view and control.
Description: When two ports are crossed connected, a network storm
degrades the ability of the Firewall to pass data. This is very unlikely to occur
because it requires special cabling that is not ordinarily available to plant
personnel. Additionally, both ends of the cable must be inserted into two
downlink Control Firewall ports and the cable must be left in place for 10
minutes before a problem is realize.
Recovery: Remove the cross connect cable that introduced the dual fault into
the system.
Workaround: Ensure that cross connect cables are not made available to
plant personnel.
I/O-Chassis-Series A
1-8NU12R Error Indication: Loss of C300 to FTEB-Series A IO module communication

following a Checkpoint Restore or Reload with Contents to a C300 in IDLE.
Description: Checkpoint Restore or Reload with Contents to a C300 in IDLE
may result in loss of C300 to FTEB-Series A IO module communication.
Some IOM connections are not formed; some IOMs appear Red on the
Control Builder monitoring tree. This problem will not occur when performing
these operations to a C300 in the NODB state.
Recovery: Restart the C300 into the NODB state; then perform the
Checkpoint Restore or Reload with Contents again.
Workaround: Do not perform Checkpoint Restore or Reload with Contents to
a C300 in IDLE with Series A IO modules loaded.
I/O-Profibus
1-6AUTID Error Indication: Faulted Primary and Secondary CPMs and RMs.
Communication with the CPMs will not be possible until the modules are
power cycled. They will appear RED in the Control Builder Monitor Tab.
Description: When a user loads a Profibus Interface Module FB or a
DeviceNet Interface Module FB in which either Input Connection Size or
Output Connection Size was set to the illegal value of 0 (ZERO), ignoring the
error message displayed in Control Builder in the process AND then
subsequently deletes this FB, both Primary and Secondary CPMs may enter


the faulted state at the time of the FB deletion. RMs may also enter the faulted
state as a result of the CPM fault.
Recovery: Power cycle the affected CPM modules and Redundancy Modules
and do not load a Profibus Interface Module Function Block or a DeviceNet
Interface Module Function Block in which either Input Connection Size or
Output Connection Size is set to 0 (ZERO).
Workaround: 1) Do not enter a value of 0 (ZERO) -which is illegal - for either
Input Connection Size or Output Connection Size for either a Profibus
Interface Module FB or a DeviceNet Interface Module FB
2) If a 0 (ZERO) is entered in either of these cases, the resulting error
message in Control Builder should not be ignored and the load of this FB
should be cancelled.
I/O-Series C
1-7SRUI1 Error Indication: Continuous report of SOELost/SOELostNotCorr events in

SOE/events summary page in station.
Description: If all 32 channels of a DI-SOE IOM are configured (event option
EVTOPT as NONE) with DiMode as SOE. And if the inputs are changing at
more than ~500 times (means 500 events) per sec continuously...then you will
see these SOELost events in station. This behavior is dependent of IOM scan
rate configuration.
Recovery: Inactivate the channels or make IOM idle till the inputs
stops/slowdown changing the PVs less than above mentioned rate.
Workaround: Configure the IOM as Normal or LowLatency.
1-8D5TR8 Error Indication: Status light blinks and a "Input-Output Loopback Failure"
soft failure is annunciated.
Description: When an input RTNs from an open input condition an "Input-
Output Loopback Failure" soft failure is inappropriately annunciated.
Recovery: With the "Swap_Primary" command, make the reporting module
the secondary module then, with the "Disable_Sync" command, disable
module synchronization. This will IDLE the secondary and clear the soft
failure.
Workaround: The only known way to prevent this from occurring is to disable
OWD on all channels.
OPM-Controller Migration

1-4GPUC9 Error Indication: Appearance of an UnknownError code at the end of

migration (when cancel migration is selected.)
Description: During OPM if errors are generated due to snapshot restore a
continue/cancel dialog appears .Selecting cancel migration will cause an
Unknown error code to be displayed at the end.
Recovery: Ignore the error code.
Workaround: Ignore the error code and proceed, there after manually verify
that all the modules of the chassis are flashed to the previous versions and the
controllers are in sync.
1-6JIPLR Error Indication: An error dialog was encountered indicating that there was a
problem with a dependency of pscdasrv.
Description: At the very beginning of migration (before connection to EMSN)
the migration app tries and fails to shut down Experion services. An error
dialog was encountered indicating that there was a problem with a
dependency of pscdasrv.
Recovery: Acknowledge the error, kill the application and restart migration.
Workaround:
1. Acknowledge the error dialog.
2. An error message indicating a failure of dbmigwiz and ccmigrplugin is
encountered.
3. Migration continues to screen requesting EMSN information.
4. Kill Migration through task manager.
5. Restart migration.
6. Services were successfully shut down and migration proceeds correctly.

1-75T0YL Error Indication: Series C IO module failed to migrate even though the
migration wizard indicates success.
Description: The Control Builder migration wizard indicates a successful
migration of multiple Series C IO modules, but in CTools it appears one
module was not successfully upgraded. This problem can happen if the
IOLINK block tag name contains lower case letters.
Recovery: For the IOM pair that failed to migrate, perform a manual OPM as
follows:
1) Disable IOM synchronization by setting the IOM's Command parameter to
"Disable_Sync".
2) Using CTools, upgrade the secondary IOM to the new firmware.
3) Enable IOM synchronization by setting the IOM's Command parameter to
"Enable_Sync".
4) Force an IOM switchover by setting the IOM's Command parameter to
"Swap_Primary".
5) Disable IOM synchronization by setting the IOM's Command parameter to
"Disable_Sync".
6) Using CTools, upgrade the new secondary IOM to the new firmware.
7) Enable IOM synchronization by setting the IOM's Command parameter to
"Enable_Sync".
Workaround: None.

7.3. Engineering Tools
7.3 Engineering Tools

Checkpoint
1-23KLS2 Error Indication: Auto Checkpoints getting Missed on 2 Hours Intervals.

Description: This problem may happen under high CPU loads on the primary
server. At this scenario there may be a possibility of missing auto checkpoint
task that was scheduled.
Recovery: No message/event will be given to the user that an auto-task run
was skipped. In order to be able to determine if this miss happened, the user
should be well acquainted regarding the periodicity schedule of the auto-
checkpoint task. One can go investigate that auto-task's subdirectory (of its
checkpoint files) in each node's auto-checkpoint task subdirectory (under the
CHECKPOINT share). If one sees that a checkpoint was skipped/missed, then
the user must determine if that should be made up for by doing a new save. If
the user sees that at least one successful save has occurred since the missed
periodic save then it makes no sense to try to make up the missed periodic
save.
Workaround: The only workaround for a missed run of a periodic checkpoint
task is to perform an equivalent manual task save. (An equivalent manual
checkpoint task would be configured with the same nodes as that auto-
checkpoint task that had missed its periodic run.) If the user wants to act on the
instance in time that a periodic save may be missed, he must know each time
that checkpoint auto-task is to run. If after a few minutes of when the task
should be running, no “task started” event yet appears in the event summary
journal, then most likely that run of the auto-checkpoint task was missed. At
that time, the user should initiate a manual checkpoint task save of an
equivalent manual checkpoint task. In this way, the execution of the manual
task will provide the saves (especially updating of the latest.cp files) that the
auto-task would have done if it had ran.
1-3S4F64 Error Indication: Snapshot serialization errors on checkpoint restore and

project/monitor loading. Manual / Auto Checkpoints have Complete Status
even though the points are missing. Checkpoint restore possible also results
in red (err2130) CMs in monitor tree upon the completion/abort.
Description: When the .snapshot file is corrupted due to checkpoint error (ex:
snapshot serialization error), some points and their parameters are actually
missing in the snapshot file. Manual / Auto Checkpoints have Complete Status
even though the points are missing. Hence, when a user tries to restore the
checkpoint based on the manual or auto checkpoint file, points will be shown in
red (err2130) upon the completion. One of the sources of this error is
performing a CB engineering operation (i.e. load/upload/delete) from a Level 3
Flex station whose network card is set to auto-negotiate on duplex/speed. As
of R301.2, and R310.2 releases, checkpoint alarms will be generated when

such a problem occurs with the checkpoint save. This will at least alert the user
that such a problem exists. It remains the user's responsibility to determine
what windows machine (having the incorrect network card configuration)
introduced the problem when an engineering operation was performed from it.
Recovery: Ensure all level 2 flex/console/servers and level 3 flex stations have
their network cards fixed with regard to duplex/speed. None should be set to
auto-negotiate.
Workaround:(1) Correct any network card setting as stated in above
recovery.(2) Rebuild checkpoint files on affected controllers and then perform
checkpoint save.
1-479C8V Error Indication: Checkpoint auto-task (scheduled) saving in a system that is

experiencing many ERDB access errors (such as from engineering activities
(loads, deletes) may cause the checkpoint service to consume exorbitant
amounts of the active primary process server's CPU (50%), and its memory.
Description: Occurs when a server cluster that is experiencing degradation in
ER performance due to communication/access problems with SQL/ERDB. If, at
that time, a scheduled auto checkpoint save begins running, the Experion PKS
Checkpoint Service may begin to consume much of the processor's CPU
resource (up to 50% loading), and more than its acceptable amount of the
machine’s memory. Happens only on the active primary process server as that
is the only place where the Experion PKS Checkpoint Service runs. An
aggravating stimulus for causing this problem is to have engineering
(delete/load) activities occurring from two or more CBs.
Recovery: If this problem occurs, one can recover from it by restarting the
checkpoint service as stated in the workaround.
Workaround: (1) Launch Windows services panel (Services.msc) on the
primary process server.
(2) Select the Experion PKS Checkpoint Service (on primary server) by double
clicking on it.
(3) Now stop the Experion PKS Checkpoint Service (on primary server). Close
out by pressing OK.
(4) Within 30 seconds you should see the Experion PKS Checkpoint Service
restart. (This is automatically done by Experion PKS System Repository
Service on the primary process server.)
(5) Close/cancel out all engineering dialog box(s) that are open in the Control
Builders (CBs) of this server cluster.
(6) Close out each CB on the servers/stations in this process server cluster.
(7) Restart the needed CBs in the servers/stations in this process server
cluster.

1-4MWT6X Error Indication: Engineering operations such as a multiple controller load is

in progress and then scheduled checkpoint task starts to run. Saves fail as
expected, but load gets hung while "composing latest.cp".
Description: When ten controllers have tags loaded at the same time and a
scheduled checkpoint save begins on those controllers, the aborts as expected
when the loading to the controllers completes. The load dialog hangs indicating
that it is composing the controller node's latest.cp file and cannot be cancelled
until the checkpoint service is shutdown and restarted.
Recovery: Restart the checkpoint service as stated in the workaround.
(1) Launch Windows services panel (Services.msc) on the primary process
server.
(2) Select the Experion PKS Checkpoint Service (on primary server) by double
clicking on it.
(3) Now stop the Experion PKS Checkpoint Service (on primary server). Close
out by pressing OK.
(4) Within 30 seconds you should see the Experion PKS Checkpoint Service
(5) Close/cancel out all engineering dialog box(s) that are open in the Control
Builders (CBs) of this server cluster.
(6) Close out each CB on the servers/stations in this process server cluster.
(7) Restart the needed CBs in the servers/stations in this process server
cluster.
1-5A5HEL Error Indication: Scheduled checkpoint task started to run, and failed to finish,
causing permanent locking out engineering operations on five controllers.
Description: Auto-checkpoint saving was launched at the time that a large
export of 5000 tags was in progress. The first five controllers (that had their
individual saves launched in the checkpoint auto-save task) ended up in
condition where no engineering operation (i.e. load/delete) could be
successfully launched on them. This problem is more of a file locking issue on
the node's .snapshot file rather than ERDB locks. Before the engineering
load/upload/delete occurs, CB's ctrlsession needs to cache the current
.snapshot file into memory in order for the engineering operation to modify it.
However, because of the exception occurring in checkpoint save thread, this
thread keeps exclusive access to the .snapshot file, preventing ctrlsession from
reading it. The shutting down of the checkpoint service has the underlying
window's file handling remove all file locking, thus allowing ctrlsession to
acquire use of it.
Recovery: If this problem occurs, one can recover from it by restarting the
checkpoint service as stated in the workaround.


Workaround:
1) Launch Windows services panel (Services.msc) on the primary process
server.
2) Select the Experion PKS Checkpoint Service (on primary server) by double
clicking on it.
3) Now stop the Experion PKS Checkpoint Service (on primary server). Close
out by pressing OK.
4) Within 30 seconds you should see the Experion PKS Checkpoint Service
5) Close/cancel out all engineering dialog box(s) that are open in the Control
Builders (CBs) of this server cluster
6) Close out each CB on the servers/stations in this process server cluster.
7) Restart the needed CBs in the servers/stations in this process server
cluster.
1-72AGG5 Error Indication: Multiple checkpoint rebuilds encounter 'Failed to Commit

database transaction' errors.
Description: This error will most likely occur when in a single CB, a user
selects a multiple number of controllers on the monitor side, and launches
checkpoint rebuild for all of those controllers at the same time. In addition, the
problem will be further aggravated, if from another CB, a user selects a number
of other (different) controllers, and launches an "Upload to controller" on them.
In this scenario, it is possible for the checkpoint rebuilding to fail. This problem
gets encountered because checkpoint rebuild (which executes the same load
queries to ERDB as monitor reload) operates much faster than monitor load.
This is because checkpoint rebuild is not slowed up by communication with
controller that a monitor reload has. As such, checkpoint rebuild can somewhat
overload SQL (really ER server) with a lot of SQL queries. It really gets
overloaded when a multiple number of rebuilds are happening at same time as
other engineering activities, such as Upload from controller to monitor.
Workaround: The user needs to limit the number of parallel engineering
activities (i.e. checkpoint rebuild and other engineering operations) occurring at
any one time in a multi-user CB environment. This is especially true if the
engineering operations being launched on each controller are encompassing a
large number of blocks. Checkpoint rebuild always rebuilds the entire
controller. The user does not have any selection to just rebuild a subset of the
tagged blocks for the checkpoint file. If one encounters a "Commit Transaction"
error when rebuilding a number of controllers at one time, then to recover from
this, the user just needs to serially rebuild each controller while limiting the
number of heavy engineering activities (such as loading a lot of blocks) on
other CBs in that server cluster.

1-84FI1F Error Indication: "??????" appear for controller node name(s) in checkpoint
save system events and error logs. This can be associated with any automatic
or manual checkpoint task that may be run.
Description: If upon running a checkpoint manual or automatic task, the
checkpoint system events (as seen in Station's Event Summary display) have
“???????” showing for the controller name(s) in that event description, then the
workaround as stated below must be executed in order to re-establish the
correct information for that given checkpoint task parameters that are resident
in SR.
Recovery: Refer to the Workaround.
Workaround :(The term of "task" below represents the given automatic
checkpoint task or manual checkpoint task that is experiencing the “???????”
string for configured controller names in that task.)
1. Create a dummy C200 on the project side.
2. Just create only the CPM/CEE of this C200 - no need to have any CM
blocks with it.
3. Go to Checkpoint Scheduler display and stop the given checkpoint task.
4. Edit the given task - this takes you to the "Define Task" display.
5. You should see “????????” string for one or more node(s) in the "Assigned
Nodes" pane of this display.
6. Get rid of these “??????” strings from this "AssignedNodes" pane of this by
just selecting them in this pane, and transferring them back (<<) to "Available
Nodes" pane.
7. If you do not see an expected controller node name in the "Assigned Nodes"
pane of this display, then it was probably this controller that was replaced by
the “???????” string. Again transfer that expected controller node name(s)
from the "Available Nodes" pane to the "Assigned Nodes" pane (using >>).
8. Also, you should see the dummy C200 in the "Available Nodes" pane.
9. Transfer the name of this dummy C200 to the "Assigned Nodes" pane.
10. Press "Define".
11. Again edit the task. This takes you back to the "Define Task" display.
12. You should not see any “???????” strings as node names in the "Assigned
Nodes" pane of this display.
13. You may still see “???????” strings as node names in the "Available
Nodes" pane of this display. This condition doesn't interfere with any
checkpoint save operations. If you wish to get rid of these “???????” strings as
node names in the "Available Nodes" pane, then you will need to restart SR
after this workaround is finished.
14. Remove the dummy C200 in the "Assigned Nodes" pane of this display, by

transferring it back to "Available Nodes" pane.
15. Press "Define". This will cause SR to get updated with correct parameters
from the given checkpoint task.
16. Restart that given auto-task (i.e. schedule it to run right away), or start the
manual task.
17. You should no longer see any “???????” strings as controller name(s) in
the checkpoint events that get generated from running of this task.
18. You can now delete the dummy C200 from the project side.
Knowledge Builder Contents

1-868VEJ Error Indication: Busy icon is shown and KB goes for non-responding mode
Description: If you search for a given word for example - "lcn control
cascade" and click on any one of search item present in left pane, then the
busy icon will be shown and KB goes for non-responding mode.
Recovery: NA
Workaround:
1) Open task manager (type taskmgr.exe in Start->Run)
2).Select process tab.
3) Right click on StartApp.exe and click on End Process option to get a warning
message pop-up.
4) Click Yes button to close the application.
Control Builder
1-1DCW3Q Error Indication: When a DO OFF/ON pulse channel is in MAN and you re-
issue pulse with same value.
Description: When a DO OFF/ON pulse channel is in MAN and you issue a 5
second pulse, after the pulse executes you cannot re-issue another 5 second
pulse.
Recovery: first send a zero pulse then reissue the 5 second pulse.
Workaround: None.

1-1G5J36 Error Indication: Delete of CMs takes up long time and CPU taking up 100%
from Console Station.
Description: Deleting CMs from Console Station takes up time and CPU.
Recovery: None.
Workaround: Consider deleting CMs from Flex stations or deleting them in
batches of 50 CMs.
1-1MINNK Error Indication: The Low Limit and High limit values of Target and Entry
parameter does not reflect the scaled values.
Description: [UCF] the indication of scaled value range is wrong in RCM
Detail Display, Parameters & TV Tabs.
Recovery: None.
Workaround: None.
1-1TQOVZ Error Indication: OPC tag gets locked when configured using multiple users.
Description: OPC tag locking error when using multiple control builders to
configure OPC tags for SCM.
Recovery: None.
Workaround: None.
1-20LL57 Error Indication: This problem is encountered whenever a configuration form

is open when station times out and operator logs in back.
Description: This is because the station reloads the chart when timeout
happens. However the configuration form displayed is still linked to the old
chart instance. Hence if you try to operate on the form or even close it, the
station window crashes.
Recovery: Restart Station and the chart will open fine.
Workaround: It is recommended not to leave any modal popups such as
Configuration form open when station could timeout.
1-2U6SJ6 Error Indication: Failed to inactivate the multiple CM's one contains tagged
objects and other has no tagged objects.
Description: Failed to inactive the multiple CM's in which one CM contains
the tagged object and another CM does not have any tagged object.
Recovery: Yes.
Workaround: Inactivate the CMs one by one.

1-37J8TA Error Indication: In STATION Event summary RCM delete event is generated
twice.
Description: RCM delete event is getting generated twice, with different
timestamp.
Recovery: None.
Workaround: None.
1-3EFLU9 Error Indication: Point picker will not be listing OPC gateway parameters
Description: Point picker will not be listing OPC gateway parameters as these
parameters are defined as External in ERDB.
Recovery: None.
Workaround: Type OPC parameters manually in point picker edit control.
1-3F7RGT Error Indication: Both Project and Monitoring trees do not refresh after
performing a series of configuration change in bulk, such as, point assignment,
point deletion, and point unassignment.
Description: Inactivate all the CMs in C300_IMI (PERF_SAI0xxx,
PERF_SAC0xxx, PERF_SAO0xxx, and PERF_SDEV0xxx). Delete all at once.
Upon completion, all the deleted points are still lingered and are shown in red.
Recovery: Close and Open new Tree pane.
Workaround: Close and Open new Tree pane.
1-3FFP53 Error Indication: “Force Delete” option is enabled in SCM/RCM expanded

condition.
Description: “Force Delete” option behaves inconsistently, i.e. in some cases
it is present in expanded state in some it is present in collapsed state.
Recovery: None.
Workaround: None.

1-3S3FTP Error Indication: FF Device load fails while loading two devices of different FF
links from multi CB.
Description: error occurs while loading the FF devices of different links of
FIM4 from multi CB. Loading of one device is successful and another device
load failed The device loading was initiated by using the "Commission Device
without preconfiguration" method for Rosemount 3051 (17_03) device. By force
deleting the device from monitor view, FF link from control builder is not
displaying this un- commissioned device; even the FIM4 module display is
showing all the devices. Inactive and active the link and shutdown and startup
the link didn't display this device.
Recovery: None
Workaround: None
1-3TRNPT Error Indication: In SCM, entering and canceling alias name and again on
entering the same name says duplicate name.
Description: If we enter some alias name in the Alias tab of an SCM, and
cancel it and then again if we give the same name, it says duplicate name. This
occurs even if we save and open that SCM and give the same alias name,
which we gave and cancelled previously.
Recovery: Choose different Alias name.
Workaround: None.
1-3UFBI9 Error Indication: Even if a Phase block is deleted from control library from a
console station it still appears on another console connected to same server.
Description: as above
Recovery: none
Workaround: close the CB and reopen
1-3XALJF Error Indication: EQNEUNITSOPT parameter is not available on the

configuration forms for PID-FF and PID-PL .
Description: As above.
Recovery: None.
Workaround: None.

1-3XZJHJ Error Indication: if user copy and paste the Projected parameters, changing
the name of pasted parameter will effect original one.
Description: Not able to define Projected Parameters in CM with copy/paste
operation, throws error.
Recovery: cancel the form page and reopen the form page.
Workaround: User has to give projected parameter names manually, copy
paste will not work.
1-3Y6Q6L Error Indication: When altering a connection related to a Link with all
available VCRs used the change cannot take place.
Description: If a Link has no VCRs available, because they are all either
configured (i.e. allocated by devices on the link, or used for connections) or
were previously configured and have been loaded, any new connections from
Experion blocks to FF blocks on the Link.
Recovery: Unused devices should be removed from the Link. Also, after any
connections are deleted a re-load should be performed on the CM allow VCRs
to be freed up.
Workaround: Be careful about how many VCRs are used on each Link. It is
advisable to always leave some spare VCRs (at least 2) on each Link.
1-3Z0195 Error Indication: Projected Parameters are not propagating from new parent
after change parent.
Description: Projected Parameters are not propagating from new parent after
change parent.
Recovery: None.
Workaround: Reconfigure the projected parameters.

1-3ZNWN2 Error Indication: There is no immediately obvious indication of this problem.

But if the properties form of the block is opened, and the "Dependencies" tab is
viewed, it will be seen that the object's parent is unchanged. Or, if the original
parent object's properties form is viewed, and its "Dependencies" tab is viewed,
it will be seen that the object is no longer listed in the "Instances and Sub-
Templates" window.
Description: After a revert of an object that has a different parent than the
version in the project or library tree the object's parent remains as the parent
was, not the parent specified in the reverted version. This occurs in the
following situations:1)The object is a User Defined Template (UDT) sub-
template (i.e., its parent is another UDT), and its parent has been changed to a
higher level UDT2)The object has an instance of a UDT and its parent has
been changed to the base (system) type. The revert works correctly if the
object is an instance of a UDT which is a sub-template and its parent has been
changed to a higher level UDT.
Recovery: Delete the object from the project or library tree and perform a
revert to the desired version.
Workaround: Before reverting to a version of an object with a different parent,
first delete the object and then revert.
1-41RO4L Error Indication: when user checks showparameter check box it’s not
showing parameter names for table headers. Still it's showing parameter
description only.
Description: Parameter Names are not displayed in ENHAUXCALC FB’s
Configuration Form Main tab.
Recovery: None.
Workaround: None.
1-4790KB Error Indication: PTIMEPUB parameter may get stuck at "0" in certain FF
devices in a specific scenario.
Description: When changing the boot class of a ST3000 or STT35 device the
PTIMEPUB parameter is cleared to "0" by the device. If an Upload is
performed followed by an Update to Project the value "0" will be set in the
Project database and it cannot be changed back by the user.
Recovery: No user recovery possible. Have Honeywell correct value(s) using
BigBlue, followed by Upload and Update to Project.
Workaround: Do not perform Upload followed by and Update to Project for
ST3000 or STT35 after changing the device's boot class. Only after another
load to the device should these operations be taken.

1-492BEN Error Indication: Control Builder crashes when loading strategies during
server synchronization.
Description: Control Builder crashes when loading strategies.
Recovery: None
Workaround: Load strategies after Server synchronization is completed.
1-49JZAJ Error Indication: An error comes up "Invalid version"

Description: Create a SCM template with three or more handlers. Instantiate
the template. Go to the table view of the instantiated SCM template. An error
comes up "Invalid version".
Workaround: Open the SCM chart view and double click on the SCM chart to
open the property page of SCM. Click OK on the property page and now try to
open the table view of SCM. or delete some connection and create the same
again.
1-49LDMJ Error Indication: NNumeric / NString / Nflag is not updated in the 'Status/Data'
tab.
Description: In Numeric/Flag/Text Modbus Request block configuration
dialog, when a value is entered in the NNumeric field, hit tab and hit
'Status/Data' tab, the grid for the PV value is not getting updated with the new
value of NNumeric. Instead it is showing the number of PV values from the old
NNumeric.
Recovery: None.
Workaround: Instead of hitting Tab directly go to status Tab.

1-4CYIVR Error Indication: Alias name not present in Alias Table can be used in RCM
Step transition in a particular scenario.
Description:
1) Open CB, Configure RCM with Step and Transition.
2) Go to Alias Tab of RCM
3) Configure NUMALIASES = 5 and NUMINSTANCES = 2
4) Name the Aliases as Alias1, Alias2, Alias3, Alias4 and Alias5.MOdel Block
as "Utility:numeric" and Model Param as "PV"
5) Click other tab without Saving the changes made under Alias Tab.
6) Again Open Alias TabObservation : Only Alias1 is visible, all other created
columns are deleted.
7) Again try to configure Alias with "Alias2" name.Observation:It dispalys an
error as duplicate alias ,even though this Alias name is not present now.
8) Reconfigure the second alias as "al2" with Model block as "utility:numeric"
and a valid numeric point in a CM.
9) Save and exit the Alias Table tab.
10) Configure Step and transition as ALIAS2. Observation: This configuration
does not return any error even though there is no Alias named ALIAS2 in the
Alias table.
Recovery: Manually type the name.
Workaround: None.
1-4GNBGB Error Indication: The host ip is resolved to as the ip of the local system when
an non-English text is entered as the host name.
Description: User is able to enter a mixture of localized text and English text
for host name. The resultant host name is not valid.
Recovery: Give the appropriate host name.
Workaround: Give the IP address of the system instead of the host name.
1-4HYN49 Error Indication: Change parent of SCM/RCM templates with HANDLERS

gives improper configuration.
Description: Change parent of SCM/RCM templates with HANDLERS gives
improper configuration.
Recovery: None.
Workaround: None.

1-4M3FHZ Error Indication: Error dialogue indicating that the block is in use
Description: The Chart view of the block may be open for configuration by
other user. Occurs in the following scenario
1) Configure one FF device(d1-which has AI and PID FBs) under link and two
CMs (CM1 and CM2).
2) ASsign FB from the d1 say AI to CM1 and PID to CM2( don't make any
connection between these two blocks).
3) Now save both CMs.
4) Now first open CM1 and then CM2, while both CMs are open at the node;
try to delete the PID FB from CM2. It throws an error related to the "CM1 is
being used by xejshah"(here it throws error for the CM which was opened
first in this step.)refer attached jpeg.
5) Now close CM2 and open the CM2 from any other node; and now delete
the PID FB. It is not giving any message.
Recovery: Close the chart view of the CM.
Workaround: Ensure that the container and the assignment parent are closed
with respect to the chart view before deleting the blocks.
1-4RK1Y6 Error Indication: When connecting to a server in Configuration Studio that is

at a release different from the release of the Configuration Studio, the tasks for
“Control strategies” are not disabled. When one of these tasks is selected,
error messages are displayed to the user indicating problems with connecting
to the database, etc.
Description: This error will only occur in a system where workstations and
servers are not all at the same release.
Recovery: To be able to execute a task, a client station that is at the same
release as the server must b e used for the configuration tasks.
Workaround: In Configuration Studio, only connect to a system. Then servers
that are not at the same release will not have any tasks enabled.
1-4TW9MZ Error Indication: Error occurs during PID to PID-PL conversion.

Description: After localization, error occurs during PID to PID-PL conversion.
Recovery: NA.
Workaround: If the engineering tools resource file is in English then this
functionality is working properly. For that either change the language folder
name present @ C:\Program Files\Honeywell\Experion PKS\Engineering Tools
\RC\<lang>ORChange the User locale from Control panel.& do the operation.
Once the conversion is done, restore the settings/folder name as it is.

1-4WQFK9 Error Indication: User is able to change the IP of OPC Gateway when the
OPCG is in loaded state.
Description: User can change the IP address of OPC Gateway i.e. OPC
Gateway location even when the block is in loaded state.
Recovery: None.
Workaround: None.
1-4XXRN3 Error Indication: In LIOM detail display the EE command is listing RUN
command.
Description: Call the LIOM module in detail display with MNGR access..In
that main TAB, EE COMMAND is available. Click the COMBO BOX. It is listing
RUN Command.
Recovery: Don’t issue RUN command from Station for LIOM Module if The
command is listed.
Workaround: None.
1-4YD0NR Error Indication: Error message saying " Unable to delete HandlerRef
connection between Step and Main".
Description: Unable to delete/copy/create the invisible connection between
main handler and step block
Recovery: None.
Workaround: Create a new step block from library.
1-55FGZP Error Indication: SCM sub template disrupts expression propagation

Description: Expression propagation is disrupts after change parent
Recovery: Refer to the workaround.
Workaround: Rewrite the expression.
1-567FF9 Error Indication: Selecting Dynamic/Common SCM relationship and a mode

attribute reference in a CM results in “<CM Name>.MODEATTRREF :
Configuration Mismatch Error”.
Recovery: None.
Workaround: None.

1-5CECE9 Error Indication: Dropdown value not reset when invalid in monitor mode
Description: Dropdown value not reset when invalid in monitor mode for
PCDI_MASTER block.
Recovery: Close the Configuration form and reopen it.
Workaround: None.
1-5ENMLD Error Indication: Changing TREND.NUMPARAMS from monitoring side does

not give warning message. Attempt to change TREND.NUMPARAMS or
HIST.NUMPARAMS from monitoring side changes the rows displayed.
Description: As above
Recovery: Reopen the property page
Workaround: None.
1-5OENZS Error Indication: Station gives error if the CEE Command is changed
continuously in a specific scenario.
Description: The Station Page becomes blank after error is popped due to
changing CEE Command in the Station.
Workaround: Load the CEE Display Page again.
1-6CT82T Error Indication: Communication loss with the Controller happening while
loading strategies.
Description: While loading strategies that are part of a controller
configuration, a re-cache operation in SR may fail for the controller such that
the controller's information is removed from the cache. This will cause LOV to
the controller configuration.
Workaround: Perform a "Load Server Points" operation on the controller in the
monitoring tree. This causes the controller's data to get re-cached in SR.
1-6J6IO3 Error Indication: If the ACE name given in Control Builder is modified and
downloaded, the new name is not getting reflected in Station point detail
display, even if the page is reloaded/refreshed.
Description: If the ACE name given in Control Builder is modified and
downloaded, the new name is not getting reflected in Station point detail
display, even if the page is reloaded/refreshed.
Workaround: Unassign and reassign all modules assigned to a CEE after you
change its name.

1-6K3EFX Error Indication: CEE assignment does not happen after import in some
cases.
Description: CEE assignment does not happen in some cases even if we
import the points with CEE assignment option selected.
Recovery: assign manually after import.
Workaround: assign manually after import.
1-6NTEVX Error Indication: Alias Configuration is lost after setting ALIASOPT parameter
to OFF through Bulk edit.
Description: Alias Configuration is lost after setting ALIASOPT parameter to
OFF through Bulk edit.
Workaround: Reconfigure the Alias or Import SCM/RCM if it has been
exported before the ALIASOPT has been changed.
1-6ZTO8J Error Indication: Transaction ID error is generated in Monitoring side chart of

RCM Template instance in a specific scenario.
Description: A TransactionID Error is reported after load for a instance of
RCM template that has been changed.
Recovery: None.
Workaround: None.
1-7IOUGL Error Indication: An alarm is reported in the station with a "No Tag"
description.
Description: There is an alarm reported with "No Tag" description during
loads of huge number of CMs. Also "No Tag" alarm is seen during controller
switchovers.
Recovery: None.
Workaround: None.
1-8454WN Error Indication: Station gives errors - "This display has experienced an error
and will be closed." followed by "Errors have occurred on this page..." error.
Description: Refreshing the page after the Point Picker is launched from
trends in the Server Displays tab of the Config Details leads to an error that
makes the page blank.
Recovery: None.
Workaround: Reload the page..

1-86J0TL Error Indication:

ERR_CL_HIDDEN_CONNECTION_CONFLICTS_WITH_EXISTING (10055)
Description: If a contained CM has a projected parameter whose origin is a
SP (anything that supports back calc) that's pulling from an OP (anything that
has backcalcin) then the copy of that contained CM will get an error on that
connection. This error stops subsequent connections from getting copied.Error
is ERR_CL_HIDDEN_CONNECTION_CONFLICTS_WITH_EXISTING(10055).
Recovery: NA.
Workaround: Before the copy, remove parameter connectors to projected
parameters from the source CM. If possible, these connections can also be
converted to pure graphical connections and then the copy will work. These
graphical connections will not get copied on purpose (you can't have 2
initializable connections to the same parameter) and you'll get a different error,
but other connections will be copied correctly.
1-89DA15 Expected: Alias table load should update the FF block parameters similar to
other Experion parameters.
Error Indication: Alias table load shows completed but references for FF
block parameters are not updated after an alias table load. Essentially, alias
table will continue to use the old alias references for data transfer. Note that if
the alias table did not have a reference defined prior to the alias table load then
an error will be returned when that alias reference is used for data transfer.
Otherwise, the “old” alias reference will be used for data transfer as displayed
by monitoring side of database.
Description: Changing alias table references for the instance that is currently
NOT selected and requesting an alias table load results in the alias table load
to complete without errors but references for FF block parameters are not
loaded to CEE and updated on the monitoring side of the db. Note that after
load the delta flag clears to indicate that alias table load completed but the
references are not updated in CEE.
Recovery: Inactivate the SCM/RCM and reload SCM/RCM from project side of
database.
Workaround: None

1-8DZT4H Error Indication: "FF Schedule Exceeds Macro Cycle" error occurred when
deleting all CMs from monitor associated with a failed load during simultaneous
loads from 4 CB clients.
Description: When loading CMs with Fieldbus block content from 4 CB
clients, one load failed with “Database query execution error" as shown in the
attachment. The next step was to attempt the load again to the impacted C300
after first deleting all CMs from the monitor. When attempting the delete the
error "FF Schedule Exceeds Macro Cycle" occurred.
Recovery: Load all of the CMs with blocks assigned to the problem link at the
same time. If this doesn’t work open the latest
FFLinkSchedulennnnnnnMONITOR.txt file, where nnnnnnn is the internal
identifier for the last link loaded. This file is stored with the error logs in
C:\Documents and Settings\All Users\Application Data\Honeywell\Experion
PKS. The top part of the file (FFLinkSchedule20073210MONITOR.txt in this
example) may look something like below where the ID in the first line
(20073210 in this example) will match the id in the file name.SCHEDULE FOR
LINK ID - 20073210Natural ScheduleCM Block Parameter Start Duration
[20075151]20072819 0 90020072818 900 230 [20075159]20072814 0
90020072813 900 230NATURAL SCHEDULECM Block/Param Name Start
Dur End [20075151]---NO OPT SCHED--- 0 900 899 [20072819]---NO OPT
SCHED--- 900 230 1129 [20072818] [20075159]---NO OPT SCHED--- 0 900
899 [20072814]---NO OPT SCHED--- 900 230 1129 [20072813] Call TAC for
further help.
Workaround: Do not perform simultaneous significant database operations
involving CMs containing Fieldbus blocks.
1-NQ5HM Error Indication: Error Indication: Have problem to scroll or click on the
CM Chart.
Description: Both Servers are down when the CM Chart is displaying.
Recovery: Restart one of the ERDB servers on the redundant server system.
Workaround: None
Control Builder-Browser
1-4A8DQ5 Error Indication: Browser Orchestration Service is still firing queries after the
Stop Button has been clicked.
Description: Browser Orchestration Service is still firing queries after the Stop
Button has been clicked.
Recovery: None.
Workaround: Restart the Browser Orchestration Service on both the servers


of the redundant set up.
Control Builder-Point Picker

1-4YWMQX Error Indication: During commissioning of a FF device, Point Picker of

Associate Asset for Field Device is Not populating available configured Assets
List.
Description: While commissioning a FF device, associated asset value
cannot be set using point picker.
Recovery: Manually enter the asset name during commissioning of FF device.
Workaround: Manually enter the asset name.
CTools
1-3CA8JM Error Indication: Open CTools instance on primary and secondary server on
redundant server pair. Select few controllers/IO modules on from one and start
FW load. Select different modules in other instance. While FW is in progress in
one instance the selected modules from the other instance will get deselected.
Description: Open CTools instance on primary and secondary server on
redundant server pair. Select few controllers/IO modules on from one and start
FW load. Select different modules in other instance. While FW is in progress in
one instance the selected modules from the other instance will get deselected.
Workaround: When loading FW from one CTools instance, do not
select/deselect or perform any operation from the other CTools instance.
1-43S4FQ Error Indication: While upgrading the FW using CTools, sometimes IOM goes
to Alive state.
Description: While upgrading the FW using CTools, sometimes IOM goes to
Alive state.
Workaround: User will be able to upgrade the Boot and App firmware
separately using right click popup menu (Load->Control File).
1-471GKD Error Indication: 1. Open the CTools in console station sign on in Engineer
access level.
2. Select the SCIO modules and click LoadFW.
3. The CTools status panel (bottom) displays “nothing to load”.
4. Again select the same SCIO modules and load the FW.


5. CTools crashes.
Description: CTools crashes on attempt to load firmware to the SCIO
modules from console station in Eng sign on.
Workaround: Log in as an Administrator and perform the load operation.
1-78NM6U Error Indication: CTools gets closed after selecting upload option from
diagnostic capture with multiple I/O modules.
Description: CTools gets closed after selecting upload option from diagnostic
capture with multiple I/O modules.
Workaround: Select diagnostic capture for one module only.
Enterprise Model Builder

1-3992NF Error Indication: The alarms under the Alarm group are not visible in the
station when a FF device is added as a alarm group item while creating a new
alarm group.
Description: Alarm group not getting loaded & no alarm when a FF Device is
selected as one of the group items.
Recovery: Delete the "FF Device" from the alarm group and reload it to the
station.
Workaround: To prevent this error either avoids adding the FF Device as the
first group item under a particular alarm group or do not add the FFdevice as
the group item.
Fieldbus Library Manager

1-3R7G7V Error Indication: Unable to import FF-DD files while logged in as an engineer
in windows domain.
Description: Login the windows account with Engineer Access. Through
control builder select the option Fieldbus Device.
Description Import. Select the specific path and DD file to import. It will pops up
the windows with progress. After finishing the task you can see in library DD
file is not updated.
Recovery: Login to windows as an administrator and perform the same task.
Workaround: Login to windows as an administrator and perform the same


task.
1-3TW9GR Error Indication: FF-device Methods Manager is not working from control
builder as well from station.
Description: Login the windows account with Engineer Access. After
commissioning the device successfully, selecting specific device and launch
device methods manager will pops up the window with different methods
available with that device. But if you select any method from that window, it
pops up the window with the message “Methods has aborted. Please press the
close button to close the dialog.”
Recovery: Login to windows as an administrator and perform the same task.
Workaround: Login to windows as an administrator and perform the same
task.
Installation-Engineering Tools
1-7C6UN3 Error Indication: The EMB SA installation fails with the message “EMB
installation is only supported for SQL Server 2005 with SP2, please install then
proceed”.
Description: The error comes when SQL server 2005 with SP2 is installed
and EMB SA installer fails to check its presence.
Recovery: Click on Ok button.
Workaround: 1.Open the log file “EMBInstaller.log” then go to second last line
which says where installer is expecting “sqlservr.exe” e.g. “Could not Find
Existence of C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn\sqlservr.exe”2.Copy the sqlservr.exe to the
path where installer is expecting.3.Restart the EMB SA installation.
1-7C6UT3 Error Indication: The EMB installer gets terminated pre-maturely with the
error “*ERROR* - Unable to create [C:\Install]EMBInstaller.log”.
Description: Standalone EMB install fails, when the C:\install directory
doesn't have correct permissions.
Workaround: Please login with an administrator user account then restart the
EMB SA installation. For EMB SA installation it is must to login with an
administrator account.
1-7F3EB1 Error Indication: EMB installer gets terminated with the error "Experion
Application Framework is not installed on the system. Aborting the installation."
Description: This error comes when EMB SA installer fails to check presence


of Experion Application Framework.
Workaround: Install EAF Package and then restart the EMB SA installation.
Installation-Experion Station TPS

1-6TSMHJ Error Indication: Nodes which contain TPS components may not have the
TPS Components migrated automatically.
Description: During the migration of a node which contains TPS
Components, their presence may not be detected properly. If not, the
Customer Information and Licenses dialog selection for TPS Components may
be set to 'No' instead of 'Yes'.
Recovery: If the TPS components are not migrated properly, they can be
reinstalled manually by inserting the Application DVD, and running the
'Optional Software' installation process.
Workaround: When migrating a node containing TPS Components, ensure
that the selection is set to 'Yes'.
IXP-Import Export
1-3U23F3 Error Indication: IXP throws error and does not overwrites the strategy.
Description: IMPORT of the SCM/RCM templates Container should work
properly.
Recovery: Change the name of the strategy in CB that is getting clashed with
the ones being imported. Later delete the strategy that had to be over-written.
Workaround: None.
1-4BGTX3 Error Indication: Importing only child rcm/scm templates resulted in distorted
library.
Description: Importing only child templates show distorted strategy in the
"USER" library. Then Re-importing the templates along with the parent
template with 'Overwrite existing objects' option selected as per the warning
makes the templates lose the parent-child hierarchy and still shows distorted
strategy.
Recovery: None.
Workaround: import the parent and child both together.

1-4BVAT1 Error Indication: Changing the parent of an RCM/SCM template to make

them individual templates and then importing original parent child templates
does not work.
Description: After exporting a parent and derived children templates make
them as individual templates and then import the originally exported parent
children templates. This will result in failed import with 'Cannot refer parameter
error...' error.
Recovery: None.
Workaround: None.
1-4DS06F Error Indication: PMIO\Series C AICHANNELs import will throw error.

Description: CMs containing unassigned AICHANNELS will throw error.
Recovery: None.
Workaround: delete the existing CM before importing.
1-4GLJZ1 Error Indication: Export CM (Including Expression) in Short Name option,

and imports it again, non Major errors happen.
Description: Configure a CM_1 with an ENHAUXCALC FB. Fill out the
expression 1 of ENHAUXCALC FB with $.period. Save CM_1. Open System
preferences in CB and set Short Name option. Export CM_1. Import again
whatever Full/Short Name option, a non-major error happens. Close the
import window and open CM_1 again. In Expression 1 of ENHAUXCALC FB
“??” , is shown.
Recovery: Re-configure the steps and transitions with short name by removing
the appended questions marks. Then select Full name from the system
preferences to view the full name.
Workaround: Users should always change their "relative reference display
option" from Control Builder's System Preferences options to Full Name before
doing an export.
1-5VNI48 Error Indication: In the Import functionality with ,"Overwrite existing object"
option does not work.
Description: In the Import functionality with ,"Overwrite existing object" option
does not overwrite block names, expressions in CM/SCM/SCM templates/CM
templates properly.
Recovery: None.
Workaround: Delete the existing SC/SCM/Template and then import.

1-67VOW1 Error Indication: Import of field device template types fails in some cases.
Description: Import of field device template types fails throwing error that one
of the enum files or bsd files is not found in the path from where they are
getting imported. The error actually is a result of erroneous export which
creates the file names in truncated form.
Recovery: Create the devices using FLM.
Workaround: To prevent this error, create device using FLM first and then
import the entire database.
1-6A450B Error Indication: Sometimes import fails with ER timeout error.

Description: Import operation sometimes fails with ER server timeout error.
Recovery: None.
Workaround: Import again.
1-6AHLF7 Error Indication: E&H, ABB Fieldbus Devices cannot be imported with
'Overwrite existing Objects' option.
Description: Importing E&H, ABB Fieldbus Devices with 'Overwrite existing
Objects' option results in "Invalid name- conflicts with the name of an existing
block" error.
Recovery: None.
Workaround: Delete existing devices and then import.
LCNP4
1-DYU5U9 Error Indication: LCNP address was configured manually even after running
the "emulators_patch.exe" file.
Platform hardware change migration was performed to R310.2. After
completing the server migration, performed the procedures of
"emulators_patch.exe" as mentioned in the R311.5 EXPPlus SCN.
After a server reboot, LCNP loses its address.
TDC emulator services stopped.
Description: Refer to Error Indication.
Recovery: None.
Workaround:
Record TPS node information before Initiating Migration.
This procedure defines what you will need to do to capture critical TPS node
information before you start a migration. This information is not saved to the


EMSN during the normal migration tasks.
1) Choose Start >Programs >Honeywell Experion PKS >System
Management menu, select Configuration Utility.
1) Select Board 0, or your node name from the Configuration drop-down
menu.
1) Record all the information, including the LCN address, from the LCNP tab.
1) Click Cancel.
Configuring software:
The following procedure applies to both Servers and Stations to re-configure
your TPS software on your Experion node.
1) Choose Start >Programs >Honeywell Experion PKS >System
Management menu, select Configuration Utility.
1) Select Board 0, or your node name from the Configuration drop-down
menu.
1) Click the LCNP tab and enter the information in the appropriate fields that
you recorded during the preparing for the on-process migration step.
1) Click OK.
Ntools
1-4H9E2A Error Indication: Unable to flash firmware to a SIM in a remote chassis.

Description: Unable to flash firmware to a SIM in a remote chassis.
Recovery: A
Workaround: Put the module in local chassis and flash the firmware.
OPM-Migration Readiness Tool

1-7NKNI4 Error Indication: Wrong version reported by MRT for CNI / RM modules.
Description: Wrong version reported by MRT for CNI / RM modules.
Recovery: None.
Workaround: Manually verify the firmware versions of the modules before
migration by using ntools.
OPM-On Process Migration


1-6DTYZ9 Error Indication: C200 Controller migration wizard throws an error, if Cancel
option is selected during OPM.
Description: While performing a C200 migration the Controller Migration
Wizard (CMW) may fail when updating components in the secondary chassis if
Cancel option is selected during OPM.
Workaround: Depending upon the stage at which the error is encountered,
user can either manually upgrade the firmware or retry using Controller
Migration wizard. When cancel migration is done the secondary chassis is in
new release and primary is in old release(on-control). Downgrade the
secondary chassis using ntools. After downgrade synchronize both the
chassis.
1-755U64 Error Indication: Appearance of an MFC Application error by OPM wizard

gave OPMWiz.
Description: During migration OPM wizard throws MFC Application error.
Recovery: Cancel the error message which is thrown.
Workaround: Cancel the MFC Application error message which is thrown and
continue with migration.
1-7OB7P7 Error Indication: Controller OffPM from R211.1.T03 to R310.2 fails

occasionally.
Description: Controller OffPM from R211.1.T03 to R310.2 fails occasionally.
Recovery: NA.
Workaround: Please use Ntool for flashing firmware.
QVCS
1-35AED1 Error Indication: When attempting to check in instances of a User Defined

Template(UDT) a message is displayed “Object is already locked”.
Description: After importing a UDT, the instances of it cannot be checked in.
Recovery: To clear the locks, go to Configuration Studio and select the
“Administer the Control Strategy Database” for the server where QVCS is
experiencing the problem. Select the “VCS Admin Tasks” from the DB Admin
window and then “Synchronize VCS”. This will clear the locks.
Workaround: Do not import a UDT without importing all of its instances. To
locate the instances of a UDT, open the properties form for the UDT and select
the “Dependencies” tab. Use this list to import all of them along with the UDT.

1-3ZNW2Q Error Indication: There is no obvious indication of this problem. But if the
properties form of the block is opened, and the "Dependencies" tab is viewed,
it appears that the object's parent is unchanged. Or, if the original parent
object's properties form is viewed, and its "Dependencies" tab is viewed, it
appears that the object is no longer listed in the "Instances and Sub-
Templates" window.
Description: After an undo check out of an object that has had its parent
changed while it was checked out, the objects parent remains as the new
parent, not the original parent. Occurs when 1)The object is a User Defined
Template (UDT) sub-template and its parent has been changed to a higher
level UDT. 2)The object has an instance of a UDT and its parent has been
changed to the base (system) type. The undo works correctly if the object is an
instance of a UDT which is a sub-template and its parent has been changed to
a higher level UDT.
Recovery: If the object’s parent was changed to another template (i.e.,
condition 1 in the description section), then to restore the original parent, do the
following:
1) Check out the object, and change its parent back to the original parent.
2) Perform an undo check out on the object.
If the object’s parent was changed to a system type (i.e., condition 2 in the
description section), then to restore the original parent do the following:
1) Check out the previous version of the object (specify “Keep” on the
“Keep/Break” relation dialog).
2) perform an undo check out on the object. If these steps fail to work, delete
the object from the project or library tree and perform a revert to the desired
version.
Workaround: To prevent the error, do not perform an undo check out of the
object if it has had its parent changed.
Search engine
1-4P9WEH Error Indication: A message will appear that description is not found.
Description: If Japanese file is added as part of Bookset and if user enters a
string in katagana script, this error will come.
Recovery: There is no loss of data. Only a message box will appear.
Workaround: None.

SIM-C300
1-77UPEK If you receive a 2108 error when loading modules to a SIM-C300 in

SIMFREEZE, unfreeze the SIM-C300 (set to SIMRUN) and attempt the load
again. For most situations this will resolve the problem. If repeated loads to the
SIM-C300 are made, while the controller is in SIMFREEZE, it may be possible
to get in a situation where the above workaround does not resolve the issue. In
this case, the controller must be restarted to clear up the issue:(1) Save a
Checkpoint of the affected controller(2) Save a dynamic snapshot (i.e. from
UniSim)(3) Command a shutdown of the controller from the SIM-C300 block
module properties main tab(4) Restore the controller from the previously saved
Checkpoint(5) Restore dynamic snapshot (i.e. from UniSim).
Table View
1-33BOHN Error Indication: The confirmable instructions checkbox does not reflect the
correct value in some scenarios in Station TableView
Description: The confirmable instructions checkbox in tableview does not
refresh to show the correct value when control confirm or Esig is cancelled.
Recovery: Refresh the page.
Workaround: Refresh the page.
1-43J3OD Error Indication: TableView of R211 can't be seen from R310 station and
vice-versa.
Recovery: None.
Workaround: None.
1-46TC1A Error Indication: Switching from tableview to chartview sometimes throws

error.
Recovery: Reopen the Chart View.
Workaround: Reopen the ChartView.
1-4CKTBH Error Indication: Launching TableView in Station from Alarm/Alert Summary

page sometimes results in Unhandled Exception error.
Description: While we navigate to table view from Alarm summary / Alerts
page, by double clicking on the Alarm / Alert, an unhandled exception error is
thrown. This happens if the filter in table view is ON with 'Active Block' or
'Active Block + Next' or 'Active Block + Preferred Next'. If the filter is OFF or
ON with 'Preferred path', the exception does not occur.

7.4. Operational

Recovery: Reload the tableView Page.
Workaround: None.
7.4 Operational
CDA-Control Data Access
1-6WRYPH Error Indication: Hold breath alarms are seen in the station.
Description: In a scenario where ACE is communicating with EHG and ACE
has few prefetch CMs, PUB-SUB CMs loaded into it. The Prefetch CMs should
be referring to parameters from EHG or from points on the Hiway. Now reload
of at least 5 PUB-SUB CMs results in hold breath alarm being raised.
Recovery: Hold breath alarm returns to normal without further reloads of PUB-
SUB CMs after the initial hold breath alarm condition.
Workaround: Load one PUB-SUB CM at a time.
1-7N9SJP Error Indication : Console station loses communication with CDA Server .
Description: During duplicate ID testing, a Console Station lost
communication with CDA Server. This will occur if a node is given the same id
as an existing node.
Recovery: This is a momentary failure and will return to normal after about 11
seconds.
Workaround : None.
1-86BECP Error Indication: Control Builder crash while downloading large number of
points.
Description: Due to lack of memory, CB can sometimes crash while
downloading large number of points.
Recovery: Launch CB and try reloading the points again.
Workaround: Reduce the number applications running on the system and
retry the load operation.
1-86MZAF Error Indication: CDA Server process (pscdasrv.exe) consumes 2GB of RAM.
Description: The CDA Server service process(pscdasrv.exe) consumed
about 2 GB of memory on one of the ESCs.
Recovery: Stop the service and restart the service from the Service Control
Panel.
Workaround: None.

7.4. Operational
1-8CA9S9 Error Indication: Control Data Access Server service is stopped on the
Server.
Description: Control Data Access Server service crashes and stops on the
server. If this is a redundant server and if it is configured for automatic failover,
one would notice a server failover.
Recovery: Restart this service from the service control panel.
Workaround: None.
1-8DJYGL Error Indication: After the ACE is upgraded with the Common Components
Updates, loss of communication between ACE-T and one or more of the
Server(s) and/or console Station(s) may occur with the ACE-T red in the
monitoring tree.
Description: 1) The problem is experienced when the ACE node is upgraded
with common components (FTE driver) updates. 2) The communication to this
ACE node must have been good before the upgrade. 3) ACE, its CEE and its
CMs show up RED in Control Builder and forms have error code 7007 if Server
is experiencing LOV. 4) If a Console Station is experiencing LOV to the ACE,
the details displays referencing this ACE will appear in reverse video. 5) One
would be able to ping the ACE node from the Server node or Console Stations
from there the LOV is experienced.
Recovery: Restart Control Data Access Server service from the Console
Station or the Server where LOV (Loss of View) is experienced. If multiple
Console Stations experience this problem, restart the service on one Console
Station at a time.
Workaround: None.
1-8GMZ2D Error Indication: ACE station turns red in control builder.

Description: ACE uncommanded shutdown observed with CDA sp watchdog
time out on ACE node.
Recovery: Restart CDAsp, and then perform a checkpoint restore on the
shutdown ACE node.
Workaround: None.
1-8LTKB7 Error Indication: An event appears in the event summary for the disconnected
ACE node as Source appears with description as "Server: Connection
TIMEOUT".
Description: ACE disconnects with the server machine momentarily and
connects back to the server.
Recovery: Restart CDA Server service on the primary Experion server
machine. Please note that if it is a redundant server and it is configured to
"Failover to backup server on CDA hosts, devices or nodes Communications

7.4. Operational

Subsystem failure if servers are synchronized" option then, there will be
failover to the backup server during the restart of the CDA Server service.
Workaround: None.
1-8MO7KF Error Indication: Alarm does not appear from the FTEB. Also the system time
on the FTEB doesn't reflect the current time. Detail
Description: FTEB will not be able to send any of its notifications. CPM and
IOLIM notifications will continue to work.
Recovery: None.
Workaround: None.

7.4. Operational
Detail Displays
1-3SVWAQ Description - : the alarm color description given in the detail display of
annunciation panel display is misleading.
Error Indication - : the alarm color description given in the detail display of
annunciation panel display is misleading.
Recovery - : None.
Workaround - : Please refer to system alarm summary page, by clicking
system status pane.
1-4C7YFT Error Indication: Valve direction indications are not properly aligned.
Description: Valve direction indication markers displayed on top and bottom
of OP bar in the center panel of the faceplates are not aligned properly in
certain cases.
Recovery: None.
Workaround: None.
1-71YJDY Error Indication: OPC Gateway detail display, OPC is showing Active, but it is
not active.
Description: In OPC gateway faceplate when gateway
state(GWOPCGSTATE) parameter is not active , the text "Active" is still
displayed in the center panel of the faceplate when the "Display using inverse
video" option is selected in server wide settings page.
Recovery: None .
Workaround: Use "Display as question marks" option in server wide settings
page or click on the parameter and actual value of the parameter will be shown
in the station message. zone.
1-72WUWV Error Indication: In Rampsoak detail display, after clicking on "Alarm" tab if
one clicks on "Active Profile Graph" tab then it throws error and doesn't allow to
open it.
Description: In Rampsoak detail display, after clicking on "Alarm" tab if one
clicks on "Active Profile Graph" tab then it throws error and doesn't allow to
open it.
Recovery: None.
Workaround: Navigate to any other tab except "Alarm" tab and then navigate
back to "Active Profile Graph" tab.

7.4. Operational
1-814D7X Error Indication: The chart toolbar showing the trend period and trend
interval options does not appear in the Maintenance tab detail display of
PVALGO ( DATAACQ) block.
Description: If "sysdtldataacqa" display is used as the point detail display of a
CM containing a DATAACQ block which is named "PVALGO", in the
"Maintenance" tab detail display in Station, the trend does not have the chart
tool bar which lets the user select the trend interval and period.
Recovery: None.
Workaround: Consider using the system trend ( say, the standard trend
display-sysTnd03.htm) for plotting this data and to edit the trend interval and
period.
1-8DLWD9 Error Indication: Not able to set REDTAG for HTMOTOR block and no alarm
description shown in the faceplate of HTMOTOR in Station.
Description: 1. When REDTAG parameter is turned ON from the detail
display of HTMOTOR block, it is reset back to OFF automatically.
2.When HTMOTOR block has an alarm, the alarm description is not shown in
the faceplate in Station.
Recovery: None.
Workaround: For issue 2, navigate to the alarm summary to view the
description of the alarm.
Experion Station-Gus Display

1-6AEVAF Error Indication: Cannot configure the remote GUS displays server computer
name.
Description: In Flex Node (having Gus Remote Displays client as a optional
package) configure Gus Remote display client using the configuration utility.
Then if the checkbox "Enable connection to the server" is unchecked/applied,
and re-checked again, it may become impossible to browse for the server
name.
Recovery: Configure server name after executing the workaround
described below.
Workaround: Delete the
HKEY_LOCAL_MACHINE\SOFTWARE\Honeywell\Remote Displays key from
registry and open the configuration page for "GUS Remote Displays client"

7.4. Operational
GLC-Generic Comm Layer

1-64ZD6C Error Indication: Complete loss of view to the CDA server points on the Flex
station, Control builder on Server and Console stations on restarting Server B
which is acting as the Primary EPKS Server.
Description: In a condition where Server B is running as the primary EPKS
Server and the SR on Server B is not yet completely built from the ERDB, if
Server B is switched off/restarted, causing a switchover of the Server, will
cause a loss of view to the CDA Server points.
Workaround: Bring up Server B and sync the servers.
1-88U1SR Error Indication: OPC Strategies configured to do writes and reads through
Experion OPC Server may fail when attempting to upgrade embedded nodes.
Detailed Description: Experion OPC Server fetches and writes, if configured,
use CDA Server service on the Server node. It is possible that in the event
where some embedded nodes that are currently configured and loaded that
are communicating with the Server are rebooted for the sake of firmware
upgrades or otherwise, the stores and fetches that are being done through the
Experion OPC Server may fail during the reboot of the embedded nodes.
Please note that these embedded nodes may not be involved in the fetches or
stores.
Recovery: Automatic. The fetches and stores that may have failed
automatically return to normal as soon as the module reboot completes.
Workaround: Try keeping the number of embedded nodes simultaneous
rebooting to a minimum.
Honeywell Communications Interface

1-8E9DWE Error Indication: DSS server crashes just after it starts within 5- 10 seconds if
a client is already running trying to connect to it.
Description: If a OPC client is already waiting to connect to a OPC server
when the server comes up then the server crashes within five to 10 seconds.
The reason being that the client had added a group to the server before the
server could get a Handlesize from the DSS.
Recovery: "Restart the server after stopping the client and don't connect to the
server until it had started and shows up as Running/Idle in system
management display".
Workaround: To avoid this error make sure that the OPC server had started
and had come up as "Idle" or "Running" in system management display before

7.4. Operational

actually trying to connect to it using a OPC client.
OPC Gateway
1-78FUXN Error Indication: The shut down event notifications are seen when user tries
to select shut down command when the OPCG is in ACTIVE state.(this
problem is seen only in ACE).
Description: The false shut down alarms are seen when the use tries to
shutdown OPCG in ACTIVE state. (The requirement is user cannot shut down
OPCG when it is in ACTIVE state).
Recovery: None.
Workaround: None.
Redirection Manager
1-7SU0DJ Error Indication: The affected RDM instance will not start and an error will be
placed in the application event log.
Description: This failure is a result of an incorrect configuration. This occurs
after RDM has successfully created an OPC connection to the target servers
and is trying to establish a callback connection, which requires the client
application to be able to receive calls from the target server. If the account that
the target server is running on cannot be authenticated on the client node, this
failure can occur. If this occurs on one target node, RDM currently shuts down
rather than attempting to run with only one server connection.
Recovery: Correct the system configuration per the user's guide.
Workaround: Correct the system configuration per the user's guide.

7.5. Advanced Control
7.5 Advanced Control

System Management
1-6D5OL6 Description: Computer detail display "Components" tab 'Select Component'

combo box, does not show the list of components for selection.
Workaround: Double-click on the component in the list box.
1-8CLO3D When the offending node is deleted from the Network tree and then re-added,
the download then succeeded. The offending node can be determined from the
CDF.LOG file.
7.6 Miscellaneous
Network-CNI
1-P6UN7 Error Indication: Removal or insertion of a CNI in a powered chassis may

affect (cause reset or crash) other modules in the chassis.
Description: The module backplane connector includes a 'short' pin that
mechanically makes for a safe RIUP by delaying connection on that pin during
an insertion and removing connection to that pin first on a removal. If a module
is RIUP'd too quickly, the short time between the pin insertions/removals could
result in a failed RIUP, i.e., reset all modules on backplane.
Recovery: Cycle power on chassis.
Workaround: Remove power from chassis before removing or inserting CNI.
RSLinx
1-7PJPBF Error Indication: Migration of R301 Server to R310 results in RSlinx uninstall
error.
Description: When the server is migrated from earlier version to the R310,
Rslinx gives un-install error.
Recovery: Ignore the error by clicking OK. It would have already un-installed
the RSlinx software.
Workaround: None.

7.6. Miscellaneous
SE-Sys Engr
1-40WNDY Error Indication: Gaps in SOE events during Server Failover

Description: During Server failover, SOE events may not be continuous (in
time) and may incur some gaps when controllers have generated them
continuous in time. Server failover is random and hence cannot guarantee
events yet to be replicated (or events yet to be delivered to EPKS Server) to be
available on the new Primary after failover. SOE events cannot be recovered like
Alarms from controllers since they are not cached/stored on the controller and
hence are lost forever.
Recovery: None.
Workaround: None.
1-7R79VH "Description: OPC data read from Experion Server OPC Server can freeze for
a short period of time. For the known incidents, 16 seconds has been the
longest time that data updates are not received.
Error Indication: None. Previous values continue to be read without errors.
Recovery: The system automatically recovers without any user prompting, and
then fresh data is read as expected.
Workaround: None, but to detect when values read are stale or frozen, a
watchdog strategy can be constructed to monitor that data values are regularly
being updated. The watchdog strategy should include a continually changing
data value in the data owners and detection logic in the reading client to check
that the values read do not remain the same for more than 4-6 seconds."
Third Party Components

1-3YSVXH Error Description: A DELL Poweredge 1600 that has been clean loaded with
EXPPlus prior to R301.1 as an ExperionTPS Server node may result in the
system continuously rebooting.
Workaround: When installing Experion R301 on a Dell 1600SC platform in a
TPS environment, there is a potential for the server to reboot every 6 minutes
once loaded, even if running the proper BIOS version (A12). This appears to be
the result of a timing issue that is known to Dell and which Dell is working to
correct. If this issue should occur, the solution at this point is to go into Dell
Open Manage, on the main system screen, and select the Auto
Recovery target on the top menu. Select NONE as the option and then
select Apply.

7.6. Miscellaneous
1-46UMV3 Error Indication: Loss of view or loss of control to Fieldbus devices connected
to an H1 link where a firmware update to an ST3000, STT35, or LX1400 device
is being performed.
Description: While updating firmware to an ST3000, STT35, or LX1400 device
on a running link using Control Builder, other devices on the link may drop off
the H1 network.
Recovery: If devices drop off the link, they will recover automatically however a
loss of control and a loss of view will occur during the drop off.
Workaround: Do not upgrade devices mentioned above on a running link. All
devices on a link should be off control before upgrading firmware to an ST3000,
STT35, or LX1400 device.
1-4WCDP Error Indication: Orphan Transducer Alarms can remain on Alarm Summary
for STT35F.
Description: In STT35F when a Sensor fault occurs and sensor fault detection
is enabled, the Transducer Block Alarm goes ON and an InFail alarm is posted
in the Alarm Summary. After the Sensor fault is fixed the Transducer Block
Alarm goes OFF but the InFail alarm in the Alarm Summary does not return to
normal. The Event Journal shows that an InFail Alarm is logged and an
Unspecified Alarm is returned to normal although the original InFail condition
goes away.
Recovery: Disable and then Re-enable Server Wide Alarms.
Workaround: No workaround.
1-EZI4B Error Indication: On rare occasions a device Block Alarm cannot be cleared
after being acknowledged by Host.
Description: Honeywell devices, version 4.02.02 or older and Flowserve
devices, versions 2.02.02 or older will on occasion appear to ignore
acknowledgement of the block alarm for an Out Of Service condition, resulting in
retransmission of the original alarm. Individual Alarm journal entries in Experion
Host will be made for each recurring alarm until device is restarted.
Recovery: Restart device.
Workaround: None.

8. Problems Resolved in this Update
This section describes the notable problems resolved in this release of the Software
Update tools.
8.1 Control Functions

C300 Controller
ISR/PAR Description
1-52IHPQ When RCM acquires SCM in peer controller the Acquire and Release
Events are reported twice.
1-53EE3C Cleanup EXECUTIONMODE.
1-5A984O End of Control (EOC) event in phase block is out of order.
1-5QWLN9 In RCM/SCM - Spell mistake for the word Execution in Step Output delay
and also while loading.
1-5T29ZI [PCT] 'Source' field is missing for few events when RCMs are executed.
1-5X3611 [CommDev] Transition after IEC output will never be passed in peer
scenario.
1-5X8MZN [CommDev] Multithreaded RCM may get stuck if common devices are
used.
1-6EWHMZ [PCT] Start of control events are not generated when phase block acquire
UCM, but it generates EOC.
CF-Control Function
ISR/PAR Description
1-55YQER ERDB Migration fails to import one block from R211.1.T02 to R310.1-60.0.
1-5X8N39 Reserve memory in ONDELAY and OFFDELAY for later fix of 1-4MUBGR.
1-617L65 SignalSel block's Deviation alarm Returns to Normal on its own without
any change in Alarm state.
1-89EIGL [AOSP] Signal Select block with default values no longer loads without
warning.

CK-Control Kernel
ISR/PAR Description
1-5486LT [PCT]Some CEE alarms do not return to normal after server failover.
1-7EU7BH [PCT] Alarms did not RTN after C300 RRR.
1-7SLO8D [C300]OPM FAIL 00D1 when have CM Inactive Dangling control

connection.
Control Firewall 9Port

ISR/PAR Description
1-7HMUX7 [PCT]C300 and FIM4 loss of communication during CF-9 switchover test
results to LOC and SHED.
Fieldbus Interface Module

ISR/PAR Description
1-5SBB83 [FIM/FIM4] Fieldbus alarms are regenerated with incorrect (current)

timestamp.
Fieldbus Interface Module-Series C

ISR/PAR Description
1-5NSUDR [PCT]FIM4-C300 Peer subscription period is incorrectly set to 100 ms.
I/O-Serial Interface
ISR/PAR Description
1-42KTQP R1218:Activating/Inactivating a CM containing ARRCH block affects

ARRCH blocks in other CMs.

I/O-Series C
ISR/PAR Description
1-6O4HOH Redundant DI-24V modules will not synch when DIMODE is LowPriority.
1-6S64NT [SCIO] FPGA Read Back Error occurred after updating to R310 firmware.
1-6XRWV7 [Hartless] Hartless AO channel with IOP type AO displays as IOP type
AO-HART.
1-72IY2N Series C, DI migration fails from R301.1.002 to R310.2.
1-7CNHI5 On DISOE, PVs are not available in Factory Test mode.
1-7EQFSV SeriesC AO-HART migration fails from R301.1 to R310.2.
1-7J6AU9 [SCIO] AO + MTL 4546C barrier fails over twice (sometimes continuously)
on open circuit condition.
ModBus TCP Infrastructure

ISR/PAR Description
1-5QYCYH SM running with Faults condition should send an alarm for PCDI like the
Idle state does.
1-6NIUI1 [UT] C300-SM comm is interrupted causing a bump in I/O when SM in use
is set to IDLE.
1-6O4XI8 Channels may hang during C300 switchover.
1-7KOANE The substitution override feature of "last known good value" results in a
NaN.
1-7MKAHP Loss of yellow switch causes PCDI block to not be operational - causes
frozen data.
1-84Q2OR PCDI Master Block sometimes fail to connect or connection is delayed.
Network-FTE Bridge
ISR/PAR Description
1-6ABO9K [PCT] Bad PV reported for Series A IO communicating with C300

controller during stability run.
1-6DDGGR FTEB does not programmatically display manufacturing information.

OPM-Controller Migration
ISR/PAR Description
1-4GPUC9 C200 OPM from R301.1 to R310.1 gives unknown error code when
Cancel Migration option is selected.
1-78KLGJ After migration Powerflex channels could not be assigned to PowerFlex

modules.
1-82VQZ9 MRT not working after completion of Server Migration.
Redundancy-RM
ISR/PAR Description
1-5Z49LR C300 controller migration fails during indirect sync of RampSoak with large
profiles.
SCM-Sequential Control Module

ISR/PAR Description
1-4D2IBX Inactivating a SCM doesn’t cause the inactivation of Alarms / Events from
Alarms Window.
1-4XDNXT Condition and Transition EXECSTS does not react on INCONNSTS=2240
1-5C13AM Description of Error 2026 contains multiple errors introduced in 3 different

Releases.
1-5X35WJ SCMs/RCMs in Program will remain inactive after checkpoint restore and
warmstart.

UCF-Unit Control Function

ISR/PAR Description
1-4728PZ [SID]RCM in COMPLETE state is not getting INACTIVE- giving error

"event journaling not yet complete".
1-4V3PFD PCT- Loop count on phase block shows negative values after some
maximum number of iterations
1-52IHPQ When RCM acquires SCM in peer controller the Acquire and Release
Events are reported twice.
1-53EE3C Cleanup EXECUTIONMODE.
1-5A984O End of Control (EOC) event in phase block is out of order.
1-5QWLN9 In RCM/SCM - Spell mistake for the word Execution in Step Output delay
and also while loading.
1-5T29ZI [PCT] 'Source' field is missing for few events when RCMs are executed.
1-5X3611 [CommDev] Transition after IEC output will never be passed in peer
scenario.
1-5X8MZN [CommDev] Multithreaded RCM may get stuck if common devices are
used.
1-6EWHMZ [PCT] Start of control events are not generated when phase block acquire
UCM, but it generates EOC.

8.2 Engineering Tools

CEE Database
ISR/PAR Description
1-47PVV3 Wrong text in error message when inactivating RCM when all batch events
haven’t been journaled.
1-4SGRSD SIM_C200 HOST IP ADD/HOST NAME enable in monitor view.
1-53I9C9 Unable to see the input descriptions of the RegSummer FB.
1-5ZOO1S SCM step and transition blocks allow PCodeSize to be uploaded from
controller to monitor-side.
1-6DQ5VS Default value of parameter SUBSCPERIOD for ceec300 block is displayed

as 500mS instead of 'DEFAULT'.
1-6MKO5V ERDB migration fail import Step block From R211.1.T03 to R310.2.
Checkpoint
ISR/PAR Description
1-3S4F64 Man/Auto Checkpoint Status show Complete even if snapshot file is

corrupted due to checkpoint error.
1-4Y2MT5 Checkpoint restore failure, many CMs in red although CMs are in
checkpoint file.
1-52W917 Archive Progress bar should not be accessible unless any option selected
at Read Only Dialogue.
1-53GXR7 Scheduler: Assign Node, Delete Default Name, Remove Node & again
Assign Node do not add Default name.
1-59UTFN Archive Checkpoint Completed Successfully without ErrorMsg when

Destination Disk has no enough space.
1-5L84XF In C300_SIM click view check point tasks and click refresh now error
message window open.
1-5LUW85 [CR639]Detail display not shown properly.
1-5QFZUE System alarm display does not show new checkpoint alarm desc replacing
prior alarm desc.

ISR/PAR Description
1-5X0544 Relevant error msg to be displayed if both source n destination path is

same for archiving checkpt.
1-5X69A9 A sorted list of scheduled checkpoint tasks gets unsorted on Refresh.
1-61QOPJ The UI for Restore of Checkpoint cannot be closed using "escape " button.
1-6DPCHN On clicking "Edit" button default name of checkpoint task is restored

instead of the given name.
1-6LXBAL CheckPoint_Proxy.dll (TestSupport Dll for Function Block Tester tool) is

not getting compiled.
1-6O5EUH [PCT] Change in CheckpointBase shared files not getting replicated on

Load or Delete of CM.
1-6TPSF3 [PCT] ACE Checkpoint rebuild takes 3 hours. Checkpoint rebuild works
fine for other controllers.
1-6WW709 Checkpoint Save performance degradation due to residual CRC testing.
1-723VAD Restore of checkpoint gives a error for ACE controller contains CMs with
CAB blocks.
Control Builder
ISR/PAR Description
1-1ZF3X8 [SCM-UDT] Cannot Template Define the Invoke Main Transition

description parameter DESC, gives error.
1-2DN3ZZ [EMR300.0] Problem with CAB Parameter Reference through OPC

Gateway.
1-3PTRCZ The CB in the ESC (only on the ESC) is not showing the right information
in the status tab of the IO.
1-3PV46B Duplicate CM names allowed when creating templates.
1-3S1SJ7 Station crashes on selecting scale factor in UCM chartview for particular
UCM.
1-3V1ZKB [SCM CP] After change parent operation connection between blocks gets
deleted.
1-458HKJ DLME config link settings are not changing for FF devices in monitoring if
changed in project side.

ISR/PAR Description
1-4762BB [FIM] "unexpected error" message pops up when tried to assign FFblock
of different link to a link CM.
1-49U995 Station Crashes on writing to any SR parameter in Config dtl display

followed by clicking system
1-4AWMAZ Installing T02 cause a LOV with customer having PMIO.
1-4HL6VB Bulk edit doesn't edit PULSECMDTEXT correct.
1-4NRDGD [PCT] CB crashed with 'Out of Memory' error while deleting 100 SCMs.
1-4TBQKV [SID][CP] Change parent fails for SCM/RCM Templates containing

Datablock.
1-4UCTLZ SCM Templates with 1-24WYK4-like expressions have import errors

14212,10017,14141.
1-4X9M03 While trying to open an RCM it is returning error multiple times in a

particular scenario.
1-55DIAI Station is crashing in particular Scenario.
1-55MHWZ Code needs to be changed to support various Languages.
1-567CP1 [CP] SCM Change parent shows DATAblock deleted in CP wizard but the
same is actually not deleted.
1-5ATWXF You can drop a phase block into a SCM template.
1-5ENVS5 QVCS error report is not read only it is allowing to delete, and edit the
error messages.
1-5FKD9T SCM step block form is bigger than CB view and it's not showing OK, Help
options. Refer attachment.
1-5IAEMX Control Builder crashes on importing of R301.1 exported RCM/SCM

strategies.
1-5MVJ59 [UDR] Some Letters are not fully visible in UTR warning window.
1-5NK9TZ SR service stopping on the Primary server while performing Engineering

operations on the clients.
1-5R6Z2V [PCT] 'Connection to resource Not' error is seen when Name and
EQUIPNAME are same in phase block.

ISR/PAR Description
1-5RF6GR [UDT CP] Template defined parameters remain UNCHANGED even after
change parent in SCM/RCM templates.
1-5RFC1X Error observed when alias is browsed for a template defined

X_USENAMEREF parameter.
1-5SJVQR [PCT] Not possible to change AND/ OR blocks PIN state from monitoring
side
1-5SU4LS [UDT CP] Change parent operation to RCM template instance having alias
table doesn't add it.
1-5VKILV [PCT] ERDB was corrupted after Force Deleting 6000 SIMFF devices and
the containing SIMFIMs.
1-60ZWHX Trying to delete C300/C200 controller from monitoring side throws error as
"invalid user name".
1-6CT82T Communication loss with the Controller happening while performing

Engineering Operations.
1-6ETYET Control builder is crashing by matching the FF device in control builder.
1-6JAR36 [UDT CP]Block pins are not propagated properly after Change Parent.
1-6K4ZHU Expressions with indexed parameters on substitute names fail to parse.
1-6LQFIF Control Builder is crashing while doing bulk build in a particular scenario.
1-6M4JB9 HART cannot be used with CM templates.
1-72NPTN [PCT] MUCB: Import failed on 3 clients when import was done from 4
clients simultaneously.
1-7IOUGL [PCT] An alarm is generated with a source of "No Tag" and no description.
1-81KE0D [PCT] Attempting to modify the Base IP results in a CB crash.(Nothing

loaded to Monitor-Only Project.

Control Builder-Browser
ISR/PAR Description
1-45D9MF Pressing F1 launches KB but does not show RB related Help.
1-49K7ND [FIT] Browser is unable to search the Asset\Alarm group name contain
special characters.
1-5607O9 In Advance search, value field is not get updated according to condition.
1-5D5OX3 Browser search for CM/SCM templates/CAB/CDB/phase block library

items results in zero results.
1-5QYXVR Browser Column organizer showing error in engineer access.
Control Builder-CAB
ISR/PAR Description
1-48M83F Loading CAB from monitoring side fails in dual primary mode.
CTools
ISR/PAR Description
1-6AUKQ9 Multicast address of 239.255.0.1not working for CTools, ep. Site changed
this to 224.0.0.105.
DDManager
ISR/PAR Description
1-67VZMZ [PCT] Export failed with error "System cannot find the path specified".
Refer notes for details.
Enterprise Model Builder

ISR/PAR Description
1-6PNETF EMDB DBadmin is not available in SCADA-only system.
Installation-Engineering Tools
ISR/PAR Description
1-7JQX01 [PCT]CDA Registry Keys Missing in R310.1 and R310.2

IXP-Import Export
ISR/PAR Description
1-4M7599 IXP Tool index range checking is incorrect.
1-5IV2IT Import problems when importing Container CM's created from template.
ModBus TCP Network support and Equipment

ISR/PAR Description
1-5LJP36 Redundant bridge cable disconnection not seen for several hours.
OPM-Migration Readiness Tool

ISR/PAR Description
1-1J4WGP No tool tips for tasks associated with On Process Migration.
1-56DZC1 MRT gives a false error on C300 with IOP soft fail.
1-63A3YP MRT does not show "Ready for on process migration" field for server
readiness check.
1-64W53K All IO modules are reported as misconfigured using same slot in different
chassis.
1-657R2M [SID]MRT tool is not opened from config studio.
1-7CYLE3 MRT does not work for the server readiness from R211.1.T03, S01 to
R310.2.
OPM-On Process Migration

ISR/PAR Description
1-4M4JB1 Change of CEESTARTOPT default value causes potential loss of setting

on migration.
1-5NHZ0L On process migration fails for C200 with Fatal error “CPM was not able
sync after Migration upgrade”.
1-6NXO7D While migrating Server B , During DB migration it shows successful

completed but Shows Fail in logs.

QVCS
ISR/PAR Description
1-3URU2O User is able to rename the block if it is associated with another CM, which
is not in Checkout.
SIM-C300
ISR/PAR Description
1-65DRT1 Unable to change the signal data 0 bits(x=0-7), data type error is
occurring.
SIM-FFD
ISR/PAR Description
1-5A846X [PCT] The NUMBLOCKUSED parameter adds up and will not reduce
(release) even if the device is unloaded.
1-5E3NPL [PCT] SIMFIM4s that have the devices loaded continuously generate
RCVBEGN event once it is triggered.
1-5R35T7 [PCT]SIMFIMs crashed after inactivating and activating the SIMFIMLINKs.
1-5RFTIH [PCT] An inactive CM that has SIMFF Device AI block continuously

generates OOS events.
1-6IET9F Memory compaction after deletion is not working as Intended.
Table View
ISR/PAR Description
1-4IIJRV [SID]Phase block state warning does not appear in status bar when icon
is clicked.
1-4WSXW7 In RCM/SCM Table view showing all procedure levels(Acquired), right

click navigates to parent.
1-59ZKQ1 Inconsistent detail in Table view value for corresponding formula

parameters in the detail display.
1-5L254R Warning "Procedure not in Program" & error 2955 seen for Phase block
acquiring UCM in Table view.

8.3. Operational Functions
8.3 Operational Functions

CDA-Control Data Access
ISR/PAR Description
1-4I69EH [PCT] No Descriptor Found events flooding in CDA log for every 10
Seconds -Root cause is SIMFFD.
1-4YHBRD CDAsp retains TCP\BTC connections even after associate strategies are
deleted.
1-4Z4D23 [PCT] Loss of View observed for 3 C300 and 5 SIMFFD after multiple
server Switchovers.
1-5QTH7R CDA-sp crashes while trying to load an OPCG.
1-60FSYX Peer to peer data loss happening when C200 is publisher.
1-60HUUP [PCT] CDA server crashed on multiple console station. Refer notes for
steps.
1-6K3B9F [C300] Loss of P2P CDA Initiator connections when more than 2600 are
requested.
1-6MYP2R [PCT] Questionable state OFFNET Alarm is reported for all FTEBs on
Server & Consoles.
1-6VSU1Z CDASp crashed when an existing connection is dropped.
1-8894IF [PCT] CDA server crashed on 3 console stations during pre-stability test
on PCT Sys1.
Detail Displays
ISR/PAR Description
1-2G7E33 On sysdtlpidplb, using set trends to default button sets op to incorrect

range.
1-2IH918 Wrong slot appears for DHP Slot no.-12 in DFB point detail display.
1-2R3SER Switch, POSPA, & CDA faceplate display requires changes.
1-2TQC7P PMIO display has TAB names of 'Checkpoint operations' and 'Config
Details' reversed.
1-36ZPGL In station the state diagram for RCM is not updated.

ISR/PAR Description
1-3AH33H Station/Display sends continuous command for doorbell pt even after state
change key is released.
1-3FAST1 For AMC AUTIMAN INIT Configuration parameter is not applicable but it is
configurable from dtl disp.
1-3FB3X1 For AMC OVERHISEL/OVERLOSEL PV parameter is not applicable still it

is showing in dtl disp.
1-3FB3Y5 For AMC MULTWMAN/SUMRWMAN/ ALGO PVTRAK is not applicable

still they are configurable form pt dtl dis.
1-3IXIFM Bad value ''B'' indication continuously blinking on faceplate.
1-3J3GWO "ALARM" name is not visible on Device Net IM faceplate for failure
conditions.
1-3NHAF3 In station Non redun CPM redundancy page should be show as Non-
Redundant.
1-3UR5CE AFE_FIT: Engg. unit description overlaps the intermediate ranges.
1-3UR5R6 PVRAW value is showing some invalid char in the tool tip of PID
faceplate in station.
1-3XLUGK Message zone not displayed for FFDevice faceplate.
1-41K3C6 tool tip on PV field of REGCTL block is not showing PV & PVRAW values.
1-43GPDP Chart tab of PIDPL point detail display is not opening when user clicks on
it at first time.
1-45SS0O Detail display of Ff-device doesn't show Name(spelling) for manufacturer

properly.
1-46DOLN [SID]Script error is coming in station while clicking on the Full Size Trend
icon in table view.
1-477422 In Simulation SERIES C modules detail display SIMULATION STATE and

SIMRUN are overlapping.
1-4775MB SCIO Detail display spelling mistakes should be corrected.
1-47HORK The detail display for Alarm annunciator panel and valve damper block is
not displaying Assigned con.
1-47Z1EP In FTEB detail display INTERLAN led displayed is not aligned properly.

ISR/PAR Description
1-48BYK9 TC_IAH161 module has wrong tab name in station.
1-48UA9P FF Device Detail Display shows Launch Methods Manager always

enabled even if the Device is not.
1-48WJNJ Command mode is unable to select in station for SIM_ACE & SIM_C200.
1-491HM5 The numeric values in HT motor detail display is not matching with Control
Builder, it rounds OFF.
1-49C6ED Cmd Open is found to be missing in Valve Damper detail display.
1-49KOCH In IOLINK detail display IOM number and IOM names are overlapping.
1-4ANBZC Error in displaying alarm enable state of DACA detail display.
1-4APHH3 In Detail Disp of MAINIBV FB the Alm Tab caption changes as Input
States when navigated between Tabs.
1-4B3AXZ The Group Capability value in GRPCAPRBKA is showing ??? in station for
the value More than 6 Digits.
1-4C7C1F [SID] Tool Tip does not show current and Preferred SP values if PV is not
connected through DATAACQ.
1-4C7YFT In faceplate Valve direction indication is not properly aligned.
1-4EAMV4 Error in detail display of PIDPL (Connection tab).
1-4F5LZB IOLINK Faceplate Status for Warning does not show up properly.
1-4IZB2V Station crashes when opening PowerFB(HTMOTOR) detail display and

clicking permissive interlock.
1-4M122H FIT:LOCALMAN option is not disabled/hidden for devicecontrol blocks with

zero no of outputs.
1-4OQJUN In ACE detail display Mem.(B) not proper display.
1-4TGVCT FTEB display name in the Title bar is not consistent when we switch from
one tab to the other.
1-4WW432 In LIOM detail display controller spelling is incorrect.
1-4X94JF In CPM detail display synchronization spelling is incorrect.
1-4XE4KP EU desc is not fitted in two lines in group fdetail display for
REGCTL(sysdtlregctl)&PIDPLALTA block.

ISR/PAR Description
1-4XUYPZ Detail display of C300 is not proper after Server off process migration.
1-4YBL11 Alarm acknowledgement button not working on UCM detail display and
faceplate.
1-50QV5L In RCM/UCM detail display, when in inactive state, Exec period can be
edited but Combo box not seen.
1-5227K5 in RCM detail display STOP alarm not proper display in RCM faceplate.
1-523RRE Border line of OP is not visible for switch block in 1024x768 resolution.
1-52XAQS Tool tip on pvfield is showing 123 for REGSUM,REMCAS & RBIAS
BLOCKS in AUTO mode.
1-55F9HP In Valvedamper detail display, the word "open" is missing in "cmd open"
under Output states tab.
1-55IRUF Detail Display file name is displayed partially in Connections tab of

POWERGEN FB's Detail display.
1-564M4C In LIOM, IOM Displays, under IOM Information, alignment is not proper for
"IOM type" information.
1-566JDH "total No.of pages" value in formula and report tab of SCM,RCM is not
dynamic(always 0).
1-57R5QE The series C AI redundant module faceplate is not proper.
1-5CWZQ1 Tool tip on Op bar should show its unit as % as shown for ffpid displays.
1-5D4XZL In Group Displays SWITCH FBs faceplate is not properly scaled.
1-5DNHRV The IOP Type in Group Display for PMIO HLAIHART module is not
showing all characters.
1-5E1137 CPM200SEC Command is not working in station for engineer access.
1-5HVDEL In group detail display PID-PL faceplate in “SP” P not properly display Also
in “EU” U not properly.
1-5I57QG Formula parameter& Report parameter alignment is not proper.
1-5I6VOR In C300 detail display synchronization spelling is incorrect.
1-5JE49F PV and PV Raw value is not shown on tool tip in PIDPL faceplate.
1-5JE4A1 PV and PV Raw value is not shown on tool tip in SysDtlpidplalta_fp.htm.

ISR/PAR Description
1-5RMCRC PIDPL faceplate showing preferred SP value even the Enable Preferred
SP option is disabled in station.
1-5SXO9G Timer faceplate always showing Preferred SPval irrespective of Enable

Preferred SP option on station.
1-5V6EWX The “Back” button in the Detail Display of a FF device always refer back to
the main Blocks Page.
1-5VARNS Rampsoak faceplate shows max time limit(9999.99) while pointing mouse
over Remaining Soak column.
1-5VV93Z script error for valve damper.
1-5ZDCKB Error in showing value of OP field in POSPROP block detail display and
faceplate.
1-65X9I6 Faceplates should use PREFSPSET parameter to save PREFSP.
GCL-Generic Comm Layer

ISR/PAR Description
1-5QBY8J [FTEB2] GCL doesn't handle "GCL" disconnect cmd properly and waits for
timeout instead.
OPC Gateway
ISR/PAR Description
1-63E4XL Operator access can give GWCOMMAND in ICGateway from station.
1-6O3TI1 Stores to Inter-cluster Gateway fail (reads still work) when ICG process
goes to 100% CPU usage.
1-71MD6N [PCT] Uncommanded OPC gateway shutdown during continuous Server

Failovers.
1-7595VT [PCT] OPCGateway is crashing on PHX test bed during PCT tests -
WRITE PENDING ISSUE.
1-75IKGQ [PCTB] PUSH/STORE requests are failing with OPCG communication.

error 2990.

8.4. Supervisory Control Functions
8.4 Supervisory Control Functions

CAB-Runtime
ISR/PAR Description
1-52E9SX Only 30 string Prefs can be configured to pull data from OPC and each
consumes a WA resource.
1-5T4OOY Restore of CAB Algorithm returns cdaresult as 2303 - CAB Loading.
Miscellaneous
Network-CNI
ISR/PAR Description
1-5HYOIM Primary CNI crash when secondary CNI is unstable due to h/w problem.
1-77SRZ3 CNI does not to complete drop-synchronization processing and fails.
8.5 Server
Batch Reporting
PAR
82154 Description: ' Batch Report does not generate Excel output if using
Excel 2007.
Display Subsystem
ISR/PAR Problem and Workaround
738181/2G3QY8 Description: When changing trend type from Standard to

Single/Dual/Triple X-Y with multi-range unselected, the ranges of ALL
trend pens change to the range that was changed last instead of the trend
range.
85073 Description: The trend plot for a bad TPS point parameter shows nothing
even though there is previous good history.
86375/1-5ZS3BU Description: Allow for the ability to use display file names with all
numericsnumeric’s in their name.

8.5. Server
87273 Description: On an operator based station without login to station, some

displays can be called up such as summary pages, reports, system
displays.
73818/1-2G3QY8 Description: When changing trend type from Standard to

Single/Dual/Triple X-Y with multi-range unselected, the ranges of ALL
trend pens change to the range that was changed last instead of the trend
range.
86375/1-5ZS3BU Description: Allow for the ability to use display file names with all
numeric’s in their name.
GDA Points
85411 Description: On the large system test bed gdamngr can leak a small
amount of memory while doing acquires over DSA.
86159/1-5ZS5QO Description: Slow display callup caused by interaction between loaded

LCN and delayed display update cycle.
86812/1-5ZS3DL Description: Trend traces flatlined for 1 hour following time change from
daylight savings to standard time.
88297/1-6RO41G Description: CF9 faceplate port icons not updated on the non monitoring
Server when CF9 powered off.
History Subsystem
85921/1-5ZS3AO Description: The History Backfill task (hstbck) terminates unexpectedly

when backfilling data for more than one point parameter.
85958 Description: Inappropriate (possibly nuisance) error messages are

generated for every put into history carried out by the History Backfill task
(hstbck).
Internationalization Infrastructure
87552 Description: Safety Manager Experion Message Files need to be

updated.

8.5. Server
License Management
85782/1-5ZS5Q3 Description: Non-licensed PSA points cannot be created if the systems

licensed SCADA point count has been reached.
Notification Management
87963 Description: Events raised on console stations are not sent to

alarm/event printers.
Notification Presentation
87159 Description: Filters on all summary displays fail due to change in

regional and language options-decimal symbol.
87711/1-62GUWZ Description: Two console station are not responding to user commands.
87975 Description: TPS RTN events for alarms have an incorrect timestamp
when printed.
OPC Alarm/Event Client

84949 Description: After failover of the redundant OPC A/E Server remote
clients may fail to connect.
86332 Description: Acking a simple-to-condition message on a DSA subscriber

only acks the message locally on the DSA subscriber, leaving the
message on the DSA publisher unacked.
OPC Data Client (Flexible)

83570 Description: Cannot configure a URT system interface.
OPC HDA Server

85204 Description: Experion OPC HDA Server is always setting the update rate
for a point parameter to the fast history rate.

8.5. Server
Operator Security
75433 Description: Operator with "Ack Only" security level cannot confirm
messages with ESig.
PHD Tag Sync

67414 Description: When the range is changed via the Native Window or a
detail display for a synchronized tag, the range is not updated in PHD.
Point/Group displays and faceplates

80501 Description: Point detail History summary page

(sysDtlAnaHistorySummary.htm) occasionally doesn't display all the
trends.
83750 Description: In some conditions the Mode change may operate on the
wrong faceplate when two faceplates are open .
86242 Description: Arrow keys do not select the next faceplate in the group
display if the alphanumeric is highlighted.
87980 Description: Scanning tab on Status point detail page shows navigating
incomplete from history tab to scanning.
Reports
76939 Description: Point Attribute report enhancement to support TPS inhibit &
disable and Cx JournalOnly.
Scanning
84906/1-4TSJLZ Description: Unable to change the Data Type in the User Defined dta
formats Window.

8.6. Console Station
8.6 Console Station

Console Station
PAR
87519 Description: dsredcli reconnects too fast and too quickly if the connect
call fails immediately resulting in log flooding and performance
degradation.
87660/1-6FLL2L Description: System configuration data is not replicated to Console

Station, and dbrepcli process uses large amounts of memory.
8.7 Client
HMIWeb Display Builder
73734 Description: Inserting a specific shape into HMIWeb display builder

crashes HDB.
Quick Builder
83483 Description: Quickbuilder can get confused and try and upload from the
wrong server in a redundant pair.
87535 Description: Include Omni Channel and controller in Atlas build.
87669 Description: When the upload of a point which does not exist in the
server is performed from QB, it crashes.
87673 Description: The Point components in Quick Builder should not accept
illegal characters.
88140 Description: Need to change the default connect timeout for an OPC
channel from 10 to 20 seconds.
88205 Description: Copyright information on Splash screen and About->Help

needs to be updated with SoftCo changes.

8.7. Client
Station
76963/1-3ZCMGJ Description: If a faceplate is configured with the _fp extension already

included the faceplate will not be loaded.
87451 Description: Y axis edit boxes incorrectly display scientific notation.
80062/1-5MYLN0 Description: When configuring multiple toolbars, command zone and

icons may be missing on second toolbar.
83986 Description: Cannot Copy paste from Trend Pages in eserver Premium
Access.
84085/1-4J9ULT Description: IKB SP/OP key not responding sometimes when trying to
call up Exxon custom popups.
85067 Description: Events and tabular history both views may be displayed on
the same trend page when using rapid history navigation under certain
circumstances.
85088 Description: On Scada point faceplate lower and upper limit values are
not displayed, if CStn reconnect to Server.
85269 Description: Calling up pages via the F5/F6/F7 command may cause an
increase in Station.exe resources.
85913 Description: You cannot invoke a popup in multi window Station.
86315 Description: Push-pinned faceplates on a Flex Stn do not get cleared

when server fails over.
87451 Description: Y axis edit boxes incorrectly display scientific notation.

8.7. Client

9. Appendix
9.1 Honeywell Software Components and Revisions
This section lists the software components and revisions for the following:
 Experion PKS Software Components for Systems with Process Points
 Experion PKS Server/Client Software Revisions
 Experion Common Components Software Revisions
 Honeywell Application Software Revisions
Checking software versions and revisions
From the Add/Remove Programs windows – select the package and click on “Support
Information” to verify the installed version.
Experion PKS Software Components for Systems with Process Points

Component Version Verification Mechanism (One
alternative is listed)
Control EXP310.1.65.28 Execute application from

Builder Configuration Studio -> Control
Strategy -> Configure Process
Control Strategies
Click Help\About…
DBADMIN 310.1.65.28 Run Windows Explorer. Right click

c:\Program Files\Honeywell Experion
PKS\Engineering
Tools\system\bin\.pserdbadmin.dll
Click properties, Versions tab.
Import/ EXP310.1-65.31 Execute and log in application using

Export Tool Start\Programs\ Honeywell Experion
PKS\Engineering Tools \Import-
Export Tool
Click Help\About…
Migration EXP310.1-65.31 Execute application from

Readiness Configuration Studio -> On Process
Tool Migration -> Migration Readiness
Tool
Click Help\About…

9. Appendix
9.1. Honeywell Software Components and Revisions

IOTOOL Release 310. Execute application from

1-65.0 Configuration Studio -> Control
Strategy -> Maintain IO Modules
Click Help\About…
Network EXP310.1.65.28 Execute application from

Tools Configuration Studio -> Control
Strategy -> Maintain Control System
Firmware
Click Help\About...
Engineering V10.0 ERDB Release Execute application using

Tools EXP310.1.65.31 Start\Programs\Honeywell Experion
Database PKS\Engineering Tools \Import-
Export Tool
Click Help\About... ERDB version is
displayed below Import-Export Tool
version
Application 310.1.65.34 Run Windows Explorer. Right click

Control c:\Program Files\Honeywell Experion
Environment PKS\Engineering
(ACE) Tools\system\bin\ace.exe
Simulation 310.1.65.34 Run Windows Explorer. Right click

(SIM-C200) Tools\system\bin\sce.exe
Simulation 310.1.65.31 Run Windows Explorer. Right click

(SIM-C300) Tools\system\bin\simc300.exe

9. Appendix

IOLIM 310.1.65.34 Run Windows Explorer. Right click

Simulation c:\Program Files\Honeywell Experion
(SIM-IOLIM) PKS\Engineering
Tools\system\bin\simiolim.exe
Performance Knowledge Builder Tools 4.5.0.18 Execute application

Support Tools using Start\Programs\Honeywell
Experion PKS\Knowledge Builder
Tools\Knowledge Builder Click
Preferences tab. Version information
can be found at the Knowledge
Builder Tools Information area at
bottom of window.

9. Appendix
Experion PKS Server/Client Software Revisions

Component Version Verification Mechanism
(There are several, one alternative is listed.)
Experion Server R310.2 (Build From a Server, open the file C:\Program
310.2-32.0) Files\Honeywell\Experion PKS\Server\Setup\Software
RevM Update Log.txt and look for the line:
Experion PKS Server-Station R310.2
(EXPS_SC_310.2-32.0)(RevM) installed on
DD/MM/YYYY HH:MM:SS
Experion R310.2 (Build From a Console Station, open the file C:\Program
Console Station 310.2-32.0) Files\Honeywell\Experion PKS\Server\Setup\Software
RevM Update Log.txt and look for the line:
Experion PKS Server-Station R310.2
(EXPS_SC_310.2-32.0)(RevM) installed on DD/MM/YYYY
HH:MM:SS
Station R5.2.783.1951 Execute Station using Start\Programs\Honeywell

Experion PKS\Server\Station
Click Help\About...
HMIWeb Display R5.2.783.1951 Execute HMIWeb Display Builder using

Builder Start\Programs\Honeywell Experion PKS\Server\HMIWeb
Display Builder
Click Help\About...
Display Builder 320.4.0050 Execute Display Builder using Start\Programs\Honeywell

Experion PKS\Server\Display Builder
Click Help\About...
Quick Builder 2.21.0.271 Execute Quick Builder by launching Configuration Studio

(as per below), then launching Quickbuilder from within it
Click Help\About…
Configuration R3.0.0.604 Execute Configuration Studio using

Studio Start\Programs\Honeywell Experion PKS\Configuration
Studio
Click Help\About...

9. Appendix
Experion Common Components Software Revisions

Component Version
Honeywell Admin Support Files 031.005.16528
Honeywell CANE Details 031.005.16528
Honeywell Computers and Network Equipment 031.005.16528

Provider
Honeywell Experion Analysis Tools 031.005.16528
Honeywell FTE Status 031.005.16528
Honeywell Node Definition Tool 031.005.16529
Honeywell Packaged Redistributables 031.004.14900
Honeywell System Management Runtime 031.005.16532
Honeywell System Management Status Display 031.005.16528
Honeywell_FTE_Driver 031.005.16534
Honeywell_HCI_Runtime 031.005.16529
Honeywell_Redirection_Manager 031.005.16528
Honeywell_SafeView 031.005.16523
Honeywell_SignOn_Manager 031.005.16525
Honeywell Security Model - Workstation 031.004.16500
Honeywell_IKB_Service 031.005.16525
Honeywell Add Route 031.005.16528
Experion_TPS_System_Displays 031.005.16525
Experion_Station_Console_TPS 031.005.16531
Experion_Remote_Native_Window 031.005.16525
Experion_Server_TPS 031.005.16531
Experion_GUS_Display_Builder 031.005.16528
Experion_GUS_Display_Runtime 031.005.16528

9. Appendix
Experion Common Components Software Revisions

Component Version
Experion_GUS_Multiple_Displays 031.005.16523
Experion_GUS_Remote_Displays 031.005.16528
Honeywell File Transfer - Client 031.005.16525
Honeywell Security Model - Domain GrpPol 031.004.16500
Honeywell System Event Server 031.005.16531
TPN_Backup_Restore 031.005.16525
Honeywell File Transfer - Server and Client 031.005.16525
Honeywell Control Firewall Update 031.005.16527
Honeywell Snmp Monitor 031.005.16528
Honeywell System Performance Server 031.005.16532
Honeywell TPS Domain Console Configuration 031.005.16528
Honeywell Application Software Revisions

Component Version Limitations/Compatibility
Profit Suite R310
TotalPlant Batch (TPB) 9.0 Contact Honeywell concerning

updates
Procedure Analyst (PA) R6.0 Contact Honeywell concerning

updates
Uniformance (PHD) R210.1.1

and above
Application Processing Platform R310 Contact Honeywell

(APP)

9. Appendix
9.2. Other third-party software components
9.2 Other third-party software components

Adobe Acrobat Version 8 Run Adobe Reader

Reader Click Help \ About
Dell Open Manage 6.1.0 Using Control Panel, go to Add/Remove

Server Administrator Programs, select Dell Open Manage and click
‘support information’.
Limitations/Compatibility
All PowerEdge Servers
1800, 2850, 2600, 2950, 2900, T610, R710
Dell Open Manage 5.3 Using Control Panel, go to Add/Remove

Server Administrator Programs, select Dell Open Manage and click
‘support information’.
PowerEdge 1600 Server

Client Programs, select Dell Open Manage and click
Instrumentation ‘support information’.
For Precision P360, 370, 470, P490, T5400
and T5500 machines only.

Client Programs, select Dell Open Manage and click
Instrumentation ‘support information’.
For Precision 360 machines only.
Dell Open Manage 6.1 Open file ‘C:\Program Files\

Client Dell\OpenManage\client\
Instrumentation readme.htm
For Precision 340 and earlier machines.

9. Appendix

Internet Explorer 7.0 Run PSc Knowledge Builder (or Internet

Explorer directly).
Click Help \ About
Microsoft .NET v1.1 Sp1 Ensure the following directory is present:

Framework v2.0 C:\WINDOWS\Microsoft.NET\
v3.0 Framework\v1.1.4322
3.5 SP1
MS Visual Basic Run- 6.0.97.82 Run Windows Explorer. Right click

Time DLLs (Used C:\windows\System32\
with Model No. MZ- msvbvm60.dll
NTDE04 Application Click properties, Versions tab.
Development
Toolkit.)
MS Visual C++ Run- 7.0.3790.3959 Run Windows Explorer. Right Click

Time DLLs \winnt\system32\MSVCRT.dll (Microsoft Run
Time Library).
RSLinx 2.51.00.21(CPR 7) Double click RSLinx icon. Click Help \ About

RSLinx. Verify version info.
Seagate Crystal 8.5.0.461 Run Windows Explorer. Right click

Reports c:\windows\system32\crpe32.dll
Click Properties, Version tab.
SQL Server 2005 9.00.3042.00 Verify which version of SQL Server you have
SP3 by opening up Query Analyzer, typing in
"select @@version" (without the quotes)
and pressing F5.
Stingray Objective 310.1.65.7 Run Windows Explorer. Right click Program

Grid Files\
\Honeywell\ExperionPKS\Engineering\System\
Bin\
objgrid.dll
Click properties, Version Tab.
Windows XP SP3 Click Start, Programs, Command Prompt. Type

WinVer and press enter.

9. Appendix

Windows Server SP2 Click Start, Programs, Command Prompt. Type

2003 WinVer and press enter.

9. Appendix
External, Third Party Qualified Software Components

This section identifies third party Windows-based software applications that are supported on
an Experion PKS station client. Special care must be exercised when using any of these third
party packages.
WARNING
Note that the user assumes all responsibility for issues resulting from the installation
and operation of any components that have not been tested as compatible by
Honeywell. In addition, it is the customer’s responsibility to ensure that the
combinations of third party components have sufficient resources (e.g. memory, CPU
performance, disk space, display space, and so on.).
Component and Version Verification Mechanism

National Instruments NI-FBUS Execute Fieldbus Interface Configuration using Start\Programs\NI

Communications Manager 2.3.4 FBUS\Interface Config.
Click the System Menu.
Select about fbConfig_NT.
Model Number TC-NIFB01, for use with Model Number 1757-CN2FF
Fieldbus Linking Device. Only this model number should be purchased
and not the general release of the Configurator from NI.
MS Office 2007 SP1 Products Certified Microsoft Office Package includes the following individual Office
Products.
Microsoft Excel
Microsoft Word
Microsoft PowerPoint
Microsoft Access
NOTE: Any specific Office components not mentioned in the list above
(Outlook, Communicator, etc.,) are not tested and are not supported.
For more information go to:
http://hpsweb.honeywell.com/Cultures/en-
US/Support/SecurityOtherUpdates/3rdPartyMOC/default.htm
MS Office 2007 SP2 Products Certified Microsoft Office Package are provided in the Honeywell OLS web

9. Appendix

site.
US/Support/SecurityOtherUpdates/3rdPartyMOC/default.htm
MS Visual C++ (Used with Model Run Windows Explorer.

No. MZ-NTDE04 Application Right Click \winnt\system32\mscvrt.dll (Microsoft Run Time Library).
Development Toolkit.)
6.0 with service Pack 6
Use on client only. (Station)
MS Visual Basic (used with Model Run Windows Explorer.

No. MZ-NTDE04 Application Right click \winnt\system32\msvbvm50.dll and
Development Toolkit.) 6.0 \winnt\system32\msvbvm60.dll
Use on client only. (Station)
Honeywell TotalPlant Batch R310.1 Certified batch functionality to the latest Honeywell control systems
For more information, refer to TotalPlant Batch Software Change Notice
available in the HPS Support website.
US/Support/SystemProducts/BatchManagement/TotalPlantBatch/default.h
tm

9. Appendix
9.3. Microsoft Security Information and Qualified Anti-Virus Packages
9.3 Microsoft Security Information and Qualified Anti-

Virus Packages
For latest information
For latest information concerning Microsoft Security Hotfixes and how they relate to
your Experion system please refer to the following Honeywell website:
US/Support/SecurityOtherUpdates/MicrosoftSecurityUpdates/default.htm In addition the
following table provides the website links for obtaining the latest information concerning
several Honeywell qualified Anti-virus Packages.
Qualified Anti-Virus Packages

McAfee NT Scan v8.5i

Patch See SSOL for currently qualified anti-viral versions.
Level 14 http://hpsweb.honeywell.com/Cultures/en-
US/Support/SecurityOtherUpdates/MicrosoftSecurityUp
Symantec Corporate 10 dates/default.htm
AntiVirus
McAfee Virus Scan V8.5i

Patch 5

9. Appendix
9.4. Component Revisions for Optional SCADA Interfaces
9.4 Component Revisions for Optional SCADA Interfaces

Modicon Netlib Run Windows Explorer.

(Use with Model Number MZ-NTIF05 Modicon Right click \winnt\system32\netlib.dll
Interface Software.) 2.1
RSNetworx OEM Double click RSNetworx icon.

1.80.30 Click Help \ About RSNetworx.
Verify version info.
RSLogix 5 OEM 3.2.1 Double click RSLogix icon.

Click Help \ About RSLogix.
PLC-5C 6.1 Use Network Tools application (see Section 4.)
RSLogix 5000 OEM 2.10 Double click RSLogix icon.

Click Help \ About RSLogix.
CL5550 FW 3.25
Siemens TF API for Industrial Ethernet

(Use with Model Number MZ-NTIF12 Semen’s
S5 and TI PLC Via H1 / TF API.) 2.0

9. Appendix
9.5. Firmware Revision File Reference
9.5 Firmware Revision File Reference

This table details the current firmware versions. Those items shown in bold are included
within this Tools software update.
Firmware revision files
Component Model Revision Directory* File

Name Number Level for
R310.2
*Use this base directory path to locate the firmware directories and files for the following modules:
c:\Program Files\Honeywell\Experion PKS\Engineering Tools\system\firmware\
C200 Control TC-PRS021/ EXP310.1- Controllers\C200CPM Cee5.pcm
Processor (CPM) TK-PRS021 65.34 \R310.1.34\ Cee50.pcm
(Redundant- Cpmboot.pcm
Compliant)
C300 Control CC-PCNT01 EXP310.1- Controllers\C300\ c300.lcf

Processor (CPM) 65.34 R310.1.34\
FOUNDATION TC-FFIF01/ EXP310.1- FIM\R310.1.34\ Fimrex.nvs

Fieldbus TK-FFIF01 65.34
Interface Module
Series C CC-PFB401 EXP310.1- FIM4\R310.1.34\ fim4.lcf

FOUNDATION 65.34
Fieldbus
Interface Module
FTE Bridge TC-FTEB01 EXP310.1- FTEB\R310.1.34\ Ftebrex.nvs

TK-FTEB01 65.34
Control Firewall, CC-PCF901 X CF9\R310.1.34\ CF9_Part2.bin

9 Port CF9_Part1.hex
I/O Link Module TC-IOLI01 EXP310.1- Iolim\ R310.1.34\ iolimapp.nvs

TK-IOLI01 65.34
Legacy I/O TK-ZLCSR1 EXP310.1- LIOM\R310.1.34\ liomapp.nvs

Module 65.34
Serial Interface TC-MUX021/ EXP310.1- IOM\Serial\R310.1.34\ Simboot.pcm

Module (SIM) TK-MUX021 65.34 simrex.pcm

9. Appendix

R310.2
ControlNet TC-CCN011 2.30 cni\seriesA\FW_02.30\ SeriesA_CNI.nvs
Interface module (Single Media)
(CNI)
TC-CCR011
Series A (Dual Media)
ControlNet TC-CCN012 4.24 cni\seriesC\FW_04.24\ SeriesC_CNI.nvs

Interface module (Single Media)
(CNI)
TC-CCR012
Series C (Dual Media)
ControlNet TC-CCN013 7.15 cni\seriesD\ SeriesD_CNI.nvs

Interface module (Single Media) FW_07.15.11\
(CNI)
TC-CCR013
Series D (Dual Media)
TK-CCR013
(Dual Media -
Conformal
Coated)
ControlNet TC-CCN014 10.11 cni\seriesE\ SeriesE_CNI.nvs

Interface module (Single Media) FW_10.11.01\
(CNI)
TC-CCR014
Series E (Dual Media)
TK-CCR014
(Dual Media -
Conformal
Coated)
Redundancy TC-PRR021/ 3.52 Rm\FW_03.52\ rm.nvs

Module (RM) TK-PRR021
ControlNet TC-PGCN11 4.3 Railgateway\ FW_04.03\ gw.nvs

Gateway, Series H (Redun media)
ControlNet TC-FCCN01 4.3 Railgateway\ FW_04.03\ gw.nvs

Gateway, Series A (Single media)
TC-FCCR01
(Redun media)

9. Appendix

R310.2
ControlNet PCI TC-PCIC01 3.10 Pcic\FW_3.10.42\ 2mnbtpcic3x.nvs
Interface card
ControlNet PCI TC-PCIC02 4.10 Pcic\FW_4.10.42\ mnbtpcic4x.nvs

Interface card
ControlNet to 1757-CN2FF 1.2 Linkingdevice\FW_01.02\ cn2ff.nvs

Fieldbus Linking
Device
Series A Ethernet TC-CEN011 1.19 enet\seriesa\FW_01.19\ enet_a_app.nvs

TCPIP Interface
Card
(Replaced by TC-
CEN021)
10-100Mb TC-CEN021 3.10 enet\10-100Mb_CEN021\ CEN021.nvs

Ethernet TCPIP FW_3.10.01\
Interface Card
(Replaces TC-
CEN011)
Pulse Input TC-MDP081/ 1.9 iom\pulse\FW_01.09\ pim.nvs

Module TK-MDP081
Analog I/O TC-IAH061/ 1.9 IOM\IAH061\FW_1.9\TC TC-IAH061.nvs

Modules TK-IAH061 1.9 IOM\IAH061\FW_1.9\TK TK-IAH061.nvs
TC-IAH161/ 1.4 IOM\IAH161\FW_1.4\TC TC-IAH161.nvs

TK-IAH161 1.4 IOM\IAH161\FW_1.4\TK TK-IAH161.nvs
TC-IXL061/ 1.9 IOM\IXL061\FW_1.9\TC TC-IXL061.nvs

TK-IXL061 1.9 IOM\IXL061\FW_1.9\TK TK-IXL061.nvs
TC-IXL062/ 1.13 IOM\IXL062\FW_1.13\TC TC-IXL062.nvs

TK-IXL062 1.13 IOM\IXL062\FW_1.13\TK TK-IXL062.nvs
TC-IXR061/ 1.9 IOM\IXR061\FW_1.9\TC TC-IXR061.nvs

TK-IXR061 1.9 IOM\IXR061\FW_1.9\TK TK-IXR061.nvs
TC-OAH061/ 1.9 IOM\OAH061\FW_1.9\TC TC-OAH061.nvs

TK-OAH061 1.9 IOM\OAH061\FW_1.9\TK TK-OAH061.nvs

9. Appendix

R310.2
TC-OAV061/ 1.9 IOM\OAV061\FW_1.9\TC TC-OAV061.nvs
TK-OAV061 1.9 IOM\OAV061\FW_1.9\TK TK-OAV061.nvs
TC-OAV081/ 1.5 IOM\OAV081\FW_1.5\TC TC-OAV081.nvs

TK-OAV081 1.5 IOM\OAV081\FW_1.5\TK TK-OAV081.nvs
TC-HAO081 2.13 IOM\HAO081\FW_02.13\T TC-HAO081.nvs

C
TC-HAI081 2.10 IOM\HAI081\FW_02.10\TC TC-HAI081.nvs
AC Digital I/O TC-IDX081 2.5 IOM\IDX081\FW_2.5\TC TC-IDX081.nvs

Modules TK-IDX081 2.5 IOM\IDX081\FW_2.5\TK TK-IDX081.nvs
TC-IDX081 3.2 IOM\IDX081\FW_3.2\TC TC-IDX081.nvs

TK-IDX081 3.2 IOM\IDX081\FW_3.2\TK TK-IDX081.nvs
TC-ODX081 2.4 IOM\ODX081\FW_2.4\TC TC-ODX081.nvs

TK-ODX081 2.4 IOM\ODX081\FW_2.4\TK TK-ODX081.nvs

TC-IDA161 2.4 IOM\IDA161\FW_2.4\TC TC-IDA161.nvs

TK-IDA161 2.4 IOM\IDA161\FW_2.4\TK TK-IDA161.nvs
TC-IDA161 3.2 IOM\IDA161\FW_3.2\TC TC-IDA161.nvs

TK-IDA161 3.2 IOM\IDA161\FW_3.2\TK TK-IDA161.nvs
TC-ODA161 2.3 IOM\ODA161\FW_2.3\TC TC-ODA161.nvs

TK-ODA161 2.3 IOM\ODA161\FW_2.3\TK TK-ODA161.nvs
TC-ODA161 3.2 IOM\ODA161\FW_3.2\TC TC-ODA161.nvs

TK-ODA161 3.2 IOM\ODA161\FW_3.2\TK TK-ODA161.nvs
TC-IDK161 1.6 IOM\IDK161\FW_1.6\TC TC-IDK161.nvs

TK-IDK161 2.1 IOM\IDK161\FW_2.1\TK TK-IDK161.nvs

TK-IDK161 3.2 IOM\IDK161\FW_3.2\TK TK-IDK161.nvs
TC-IDW161 1.6 IOM\IDW161\FW_1.6\TC TC-IDW161.nvs

9. Appendix

R310.2
TK-IDW161 2.1 IOM\IDW161\FW_2.1\TK TK-IDW161.nvs

TK-IDW161 3.2 IOM\IDW161\FW_3.2\TK TK-IDW161.nvs
TC-ODK161 1.6 IOM\ODK161\FW_1.6\TC TC-ODK161.nvs

TK-ODK161 2.1 IOM\ODK161\FW_2.1\TK TK-ODK161.nvs

TK-ODK161 3.2 IOM\ODK161\FW_3.2\TK TK-ODK161.nvs
DC Digital I/O TC-IDX161 2.5 IOM\IDX161\FW_2.5\TC TC-IDX161.nvs

Modules TK-IDX161 2.5 IOM\IDX161\FW_2.5\TK TK-IDX161.nvs
TC-IDX161 3.2 IOM\IDX161\FW_3.2\TC TC-IDX161.nvs

TK-IDX161 3.2 IOM\IDX161\FW_3.2\TK TK-IDX161.nvs


TC-IDD321 2.8 IOM\IDD321\FW_2.8\TC TC-IDD321.nvs

TK-IDD321 2.8 IOM\IDD321\FW_2.8\TK TK-IDD321.nvs
TC-IDD321 3.5 IOM\IDD321\FW_3.5\TC TC-IDD321.nvs

TK-IDD321 3.5 IOM\IDD321\FW_3.5\TK TK-IDD321.nvs
TC-ODD321 2.4 IOM\ODD321\FW_2.4\TC TC-ODD321.nvs

TK-ODD321 2.4 IOM\ODD321\FW_2.4\TK TK-ODD321.nvs
TC-ODD321 3.2 IOM\ODD321\FW_3.2\TC TC-ODD321.nvs

TK-ODD321 3.2 IOM\ODD321\FW_3.2\TK TK-ODD321.nvs
TC-IDJ161 1.6 IOM\IDJ161\FW_1.6\TC TC-IDJ161.nvs

TK-IDJ161 2.1 IOM\IDJ161\FW_2.1\TK TK-IDJ161.nvs

TK-IDJ161 3.2 IOM\IDJ161\FW_3.2\TK TK-IDJ161.nvs

9. Appendix

R310.2
TC-ODJ161 1.6 IOM\ODJ161\FW_1.6\TC TC-ODJ161.nvs

TK-ODJ161 2.1 IOM\ODJ161\FW_2.1\TK TK-ODJ161.nvs

TK-ODJ161 3.2 IOM\ODJ161\FW_3.2\TK TK-ODJ161.nvs
TC-ORC081 2.1 IOM\ORC081\FW_2.1\TC TC-ORC081.nvs

TK-ORC081 2.1 IOM\ORC081\FW_2.1\TK TK-ORC081.nvs



Series C Analog CC-PAIH01 1.01 SeriesCIO\AIH\ aih_1_01_34.s28

I/O Modules FW_1.01
SeriesCIO\AIHBOOT\ aihboot_1_01_22.s28
FW_1.01
2.00 SeriesCIO\AIH\ aih_2_00_66.s28
FW_2.00
SeriesCIO\AIHBOOT\ aihboot_2_00_47.s28
FW_2.00
CC-PAIM01 1.01 SeriesCIO\LLMUX\ llmux_1_01_27.s28

FW_1.01
SeriesCIO\LLMUX llmuxboot_1_01_22.s2
\FW_1.01 8
2.00 SeriesCIO\LLMUX\
FW_2.00 llmux_2_00_66.s28
SeriesCIO\LLMUX
\FW_2.00 llmuxboot_2_00_47.s2
8

9. Appendix

R310.2
CC-PAOH01 1.01 SeriesCIO\AOH\ aoh_1_01_35.s28
FW_1.01
SeriesCIO\AOHBOOT\ aohboot_1_01_22.s2
FW_1.01 8
2.00 SeriesCIO\AOH\
FW_2.00 aoh_2_00_67.s28
SeriesCIO\AOHBOOT\
FW_2.00 aohboot_2_00_53.s2
8
Series C Digital CC-PDIH01 1.01 SeriesCIO\DI\ di_1_01_31.s28

I/O Modules CC-PDIL01 FW_1.01
SeriesCIO\DIBOOT\ diboot_1_01_24.s28
FW_1.01
2.00 SeriesCIO\DI\ di_2_00_68.s28
FW_2.00
SeriesCIO\DIBOOT\ diboot_2_00_47.s28
FW_2.00
CC-PSOE01 2.00 SeriesCIO\DISOE\ disoe_2_00_66.s28

FW_2.00
SeriesCIO\DISOEBOOT\ disoeboot_2_00_47.s2
FW_2.00 8
CC-PDOB01 1.01 SeriesCIO\DO\ do_1_01_28.s28

FW_1.01
SeriesCIO\DOBOOT\ doboot_1_01_23.s28
FW_1.01
2.00 SeriesCIO\DO\ do_2_00_66.s28
FW_2.00
SeriesCIO\DOBOOT\ doboot_2_00_47.s28
FW_2.00

9. Appendix
9.6. Hardware/Firmware Components
9.6 Hardware/Firmware Components

About firmware revisions
WARNING
The hardware requirements listed in this section are the minimum required; a
module with a revision higher than that listed is generally acceptable.
Firmware revisions listed in this section are the revisions provided in this
release.
Series C I/O Hardware/Firmware Components
NR IOTA Red. CPLD #1 CPLD FPGA Supported OPM Latest FW/SW

IOTA #2 FW/SW Rev Rev
CC-PCNT01: C300 Control Processor
C N/A Min: N/A N/A EXP301.1-22.25 EXP310.1-65.34

D (0x13) EXP310.1-65.0
Recom- EXP310.1-65.11
mend
F (0x15)
CC-PFB401: Fieldbus Interface Module 4 Nets
A C Min: N/A N/A EXP301.1-22.25 EXP310.1-65.34

K (0x13) EXP310.1-65.0
Recom- EXP310.1-65.11
mend
L (0x14)
CC-PCF901: Control Firewall, 9 Port
E N/A N/A N/A N/A N/A X
CC-PDIL01: Low Voltage Digital Input, 32 ch. (24 volts DC) pass 1 IOM Note 4
Min: A Min: A G N/A N/A BV 01.01.24 BV 2.00.47

AV 01.01.31 AV 2.00.68
Recom- Recom-
mend B mend B AV 02.00.65

9. Appendix

CC-PDIL01: Low Voltage Digital Input, 32 ch. (24 volts DC) pass 2 IOM
Min: A Min: G N/A N/A BV 01.01.24 BV 2.00.47

A AV 01.01.31 AV 2.00.68
Recom-
mend B Recom- AV 02.00.65
mend B
CC-PDOB01: Bussed Low Voltage Digital Output, 32 ch. (24 volts DC) Note 3, 5
Min: A Min: F D N/A BV 01.01.23 BV 2.00.47

A AV 01.01.28 AV 2.00.66
Recom-
mend C Recom-
mend B
CC-PAIH01: High Level Analog Input with HART, 16 ch.
A A B N/A A BV 01.01.22 BV 2.00.47

(note AV 01.01.34 AV 2.00.66
6)
CC-PAOH01: Analog Output with HART, 16 ch.
B B A N/A A BV 01.01.22 BV 2.00.53

(note AV 01.01.35 AV 2.00.67
6)
CC-PAIM01: Low Level Mux Input, 64 ch. Note 1,7
A N/A A N/A A BV 01.01.22 BV 2.00.47

(note AV 01.01.27 AV 2.00.66
6)
CC-PDIH01: High Voltage Digital Input, 32 ch 120V pass 2 IOM
120V A 120V B G N/A N/A BV 01.01.24 BV 2.00.47

AV 01.01.31 AV 2.00.68
AV 02.00.65

9. Appendix

CC-PDIH01: High Voltage Digital Input, 32 ch 120V pass 1 IOM Note 4
120V A 120V B G N/A N/A BV 01.01.24 BV 2.00.47

AV 01.01.31 AV 2.00.68
AV 02.00.65
CC-PDIH01: High Voltage Digital Input, 32 ch 240V pass 2 IOM
240V A 240V B G N/A N/A BV 01.01.24 BV 2.00.47

AV 01.01.31 AV 2.00.68
AV 02.00.65
CC-PDIH01: High Voltage Digital Input, 32 ch 240V Pass 1 IOM Note 4
240V A 240V B G N/A N/A BV 01.01.24 BV 2.00.47

AV 01.01.31 AV 2.00.68
AV 02.00.65
CC-PSOE01: 24VDC Digital Input, Sequence of Events
Min: A Min: A A N/A N/A BV 2.00.47

Recom- Recom AV 2.00.66
mended B mended
B
Note 1: While other IOMs can be redundant or non-redundant, this IOM is ONLY
available as a non-redundant IOM.
Note 2: Capable of 125 volts DC, but limited to 16 channels.
Note 3: Used with Bussed and Relay IOTAs.
Note 4: Functionally equal to pass 2
Note 5: Pass 1 no longer supported
Note 6: The FPGA image is contained in the firmware boot code, and is loaded by the
microcontroller at initialization. The FPGA revision displayed by Experion is therefore
dependent upon the firmware revision.
Note 7: Contact TAC to upgrade AT1 IOTA

9. Appendix
Controller Hardware/Firmware Components

Card Description TAB Hardware Firmware Firmware Rev.
Rev. Rev. on Displayed on
Module Network Tools
Label* application*
C200 CPM -225 E D

TC-PRS021 AV
-325 H J EXP310.1-65.34
BV
C200 CPM -275 E D
EXP310.1-65.34
TK-PRS021
-375 H J
Redundancy -125 B B
Module
TC-PRR021 -225 F B
-325 J B AV 3.52
BV 3.2
Redundancy -175 B B
Module
TK-PRR021 -275 F B
-375 J B
Verification Mechanism:
 Run Network Tools application.
 Display controller in question.
 See Version in module in question.
 Exit Network Tools application (This application should not be left running).
Communication Hardware/Firmware Components
Card Description Hardware Firmware Firmware Rev.

Label* application*
PCIC ControlNet Interface A -- 3.10

 TC-PCIC01 (Driver V 4.05.01)
PCIC ControlNet Interface A -- 4.10

 TC-PCIC02 (Driver V 4.05.01)

9. Appendix

Label* application*
ControlNet Interface Module A01 -- V 2.30

 TC-CCN011
 TC-CCR011

 TC-CCR012
 TC-CCN012

 TC-CCR013
 TC-CCN013
 TK-CCR013
 TK-CCN013
ControlNet Interface Module -- V 10.11

 TC-CCR014
 TK-CCR014
 TK-CCR014
 TK-CCN014
Ethernet TCP/IP Communications Interface A -- 1.19

Module
 TC-CEN011
(Replaced by TC-CEN021)
10-100Mb Ethernet TCP/IP A -- 3.10

Communications Interface Module
 TC-CEN021
(Replaces TC-CEN011)
ControlNet to Fieldbus Linking Device A -- 1.2

 1757-CN2FF

9. Appendix

Label* application*
1756-DNB
 Display controller in question.
 See Version in module in question.
 Exit Network Tools application (This application should not be left running).
I/O hardware/firmware components
I/O Module I/O Module Description Hardware Firmware

Revision Revision
TC-IAH061 Analog Input, 6 ch., 10V / 4-20 mA, Isolated C01* 1.9
TK-IAH061
TC-IXL061 Analog Input, 6 ch., Thermocouple (TC/mV) C01* 1.9

TK-IXL061
TC-IXL062 Analog Input, 6 ch., Thermocouple (TC/mV) C01* 1.13

TK-IXL062
TC-IXR061 Analog Input, 6 ch., RTD C01* 1.9

TK-IXR061
TC-OAH061 Analog Output, 6 ch., 4-20 mA, Isolated C01* 1.9

TK-OAH061
TC-OAV061 Analog Output, 6 ch., 10 VDC, Isolated C01* 1.9

TK-OAV061
TC-IAH161 Analog Input, 16 ch., 10V / 4-20 mA A01 1.4

TK-IAH161
TC-OAV081 Analog Output, 8 ch., 10 V / 4-20 mA A01 1.5

TK-OAV081
TC-HAI081 HART Analog Input 4-20ma A 2.10

TK-HAI081

9. Appendix

Revision Revision
TC-HAO081 HART Analog Output 4-20ma A 2.13

TK-HAO081
TC-IDK161 Digital Input, 16 ch., 120V AC, Isolated A01 1.6

TK-IDK161 D01 2.1
3.2
TC-IDW161 Digital Input, 16 ch., 159-265V AC, Isolated A01 1.6

TK-IDW161 D01 2.1
3.2
TC-IDX081 Digital Input, 8 ch., 120V AC, Diagnostic A01 2.5

TK-IDX081 3.2
TC-IDA161 Digital Input, 16 ch., 120V AC A01 2.4

TK-IDA161 3.2
TC-ODK161 Digital Output, 16 ch., 120/220 V AC, A01 1.6

TK-ODK161 Isolated D01 2.1
3.2
TC-ODX081 Digital Output, 8 ch., 120V AC, Diagnostic A01 2.4

TK-ODX081 3.2
TC-ODA161 Digital Output, 16 ch., 120/220 V AC A01 2.3

TK-ODA161 3.2
TC-IDJ161 Digital Input, 16 ch., 24V DC, Isolated A01 1.6

TK-IDJ161 D01 2.1
3.2
TC-IDX161 Digital Input, 16 ch., 24V DC, Diagnostic A01 2.5

TK-IDX161 3.2
TC-IDD321 Digital Input, 32 ch., 24V DC J01 2.8

TK-IDD321 A01 3.5

9. Appendix

Revision Revision
TC-ODJ161 Digital Output, 16 ch., 24V DC, Isolated A01 1.6

TK-ODJ161 D01 2.1
3.2
TC-ODX161 Digital Output, 16ch., 24V DC, Diagnostic A01 2.3

TK-ODX161 3.2
TC-ODD321 Digital Output, 32 ch., 24V DC A01 2.4

TK-ODD321 3.2
TC-MDP081 Pulse Input, 8 ch., w/ 2 channel fast-cutoff A AV 1.9

TK-MDP081 digital output BV 1.1
TC-ORCO81 Relay Output, 8 Channel Isolated Relay L01 2.1

TK-ORCO81 C01 3.2
TC-ORC161 Relay Output, 16 Channel Isolated Contact L01 2.1

TK-ORC161 C01 3.2
TC-MUX021 Serial Interface, 32 ch. A AV

TK-MUX021 EXP310.1-
65.34
BV
EXP310.1-
65.34
TC-IOLI01 I/O Link Module A AV

TK-IOLI01 EXP310.1-
65.34
BV
EXP310.1-
65.34
TC-FFIF01 Fieldbus Interface Module A AV

TK-FFIF01 EXP310.1-
65.34
BV
EXP310.1-
65.34
TC-FTEB01 FTE Bridge A AV

EXP310.1-

9. Appendix

Revision Revision
TK-FTEB01 65.34
BV
EXP310.1-
65.34
SST- PROFIBUS Interface Module -- 6.6

PFBCLX
 In the Desktop tree, double Click on the CNI that is connected to a KTC
 After a drawing depicting the ControlNet configuration is displayed, check I/O Modules’
Firmware versions displayed on the front panel (e.g. V1.9).
 Exit Network Tools application (this application should not be left running).
Series H Din Rail I/S Hardware/Firmware Components
Module Module Description Hardware Firmware

Revision Revision
TC-PIB161 Series H Digital Input B A
TC-POB041 Series H Digital Output B A
TC-PIA082 Series H Analog Input B A
TC-POA081 Series H Analog Output A A
TC-PIL081 Series H Temperature Input B C
TC-PGCN11 Series H ControlNet Gateway B B
TC-PBFO01 Series H Repeater Adapter B A
TC-PMFO01 Series H Fiber Module A (no f/w)
Fiber Optic Communication Components

Revision Revision
TC-RPA001 ControlNet Modular Adapter Fiber 301 (no f/w)

9. Appendix

Revision Revision
Module
TC-RPFM01 ControlNet Modular Repeater 301 (no f/w)

Medium-distance Fiber Module
TC-RPFS01 ControlNet Modular Repeater Short- 301 (no f/w)

distance Fiber Module

9. Appendix
Series A DIN Rail Hardware/Firmware Components

Revision Revision
TC-FCCN01 ControlNet Adapter A01 B
TC-FCCR01 Dual Media ControlNet Adapter A01 B
TC-FIDA81 120 VAC Input, 8 pt A01 (no f/w)
TC-FODA81 120 VAC Output, 8 pt B01 (no f/w)
TC-FID161 24 VDC Input, 16 pt A01 (no f/w)
TC-FOD161 24 VDC Output, 16 pt A01 (no f/w)
TC-FIAH81 High Level Analog In, 8 pt (4-20ma & A01 (no f/w)
10v) non-isolated
TC-FOA041 Analog Output, 4 pt (4-20ma & 10v) B01 (no f/w)

non-isolated
TC-FIR081 3-wire RTD Analog Input 8 pt B01 K
TC-FIL081 Thermocouple Analog Input 8 pt C01 K
TC-FOR081 Relay Digital Output Form A (N.O.) A01 (no f/w)

Isolated, 8 pt

9. Appendix
PM I/O Hardware/Firmware Components
Module Module Description Current Minimum

(Part Number) Firmware Firmware
Revision Revision
Analog Input Modules
MU-PAIL02 Low Level Analog Input Processor, J (6.00) J (6.00)

(51304481-100) (8 Inputs)
MC-PAIL02
(51304481-150)
MU-PAIH03 High Level Analog Input Processor, G (6.01) G (6.01)

(51304754-100) (16 Inputs)
MC-PAIH03
(51304754-150)
MU-PLAM02 LLAI Multiplexer, F (4.01) F (4.01)

(51304362-100) (32 Inputs)
MC-PLAM02
(51304362-150)
MU-PSTX03 Smart Transmitter Interface G (6.01) F (6.00)

(51304516-200) (Multivariable) Processor,
MC-PSTX03 (16 Inputs)
(51304516-250)
MU-PRHM01 Remote Hardened Multiplexer, E (6.00) E (6.00)

(51404109-125) (32 Inputs)
MC-PRHM01
(51404109-175)
MU-PHAI01 Hart Analog Input, C (1.02) B (1.01)

(51403476-100) (16 Inputs)
MC-PHAI01
(51403476-150)
Analog Output Modules
MU-PAOX03 Analog Output Processor, D (4.03) C(4.02)

(51304672-100) (8 Outputs)
MC-PAOX03
(51304672-150)

9. Appendix

Revision Revision
MU-PAOX02 Analog Output Processor, E (3.09) D (3.04)

(51304483-100) (8 Outputs) Note a
MU-PAOX01 Analog Output Processor, E (3.09) D (3.04)

(51303985-200) (8 Outputs) Note a
MU-PAOY22 Analog Output Processor, D (1.03) C (1.02)

(80363969-100) (16 Outputs)
MC-PAOY22
(80363969-150)
MU-PHAO01 Hart Analog Output, C (1.02) B (1.01)

(51403479-100) (16 Outputs)
MC-PHAO01
(51403479-150)
Digital Input Modules
MU-PDIX02 Digital Input Processor, (32 Inputs) D (5.00) C (3.03)

(51304485-100)
MC-PDIX02
(51304485-150)
MU-PDIX01 Digital Input Processor, D (5.00) C (3.03)

(51303997-300) (32 Inputs)
MU-PDIY22 Digital Input 24 Vdc Processor, D (1.03) C (1.02)

(80363972-100) (32 Inputs)
MC-PDIY22
(80363972-150)
MU-PDIS12 Digital Input Processor for Sequence G (4.05) G(4.05)

(51402625-125) of Events,
MC-PDIS12 (32 Inputs)
(51402625-175)
MU-PDIS11 Digital Input Processor for Sequence F (4.04) F(4.04)

(51304690-100) of Events,
MU-PDIS11 (32 Inputs)
(51304690-150)

9. Appendix

Revision Revision
Digital Output Modules
MU-PDOY22 Digital Output Processor, (32 F (1.05) D (1.03)

(80363975-100) Outputs)
MC-PDOY22
(80363975-150)
MU-PDOX02 Digital Output Processor, (16 H (3.08) F (3.06)

(51304487-100) Outputs)
MC-PDOX02
(51304487-150)
MU-PDOX01 Digital Output Processor, (16 H (3.08) F (3.06)

(51303994-100) Outputs)
Note that AO Rev. E (3.09) supports 0.0 mA operation.

9. Appendix

Honeywell Process Solutions
1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA

R310.2 Support Software Change Notice

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

R310.2 Support Software Change Notice

Uploaded by

Copyright:

Available Formats

Experion

Copyright 2010 by Honeywell International Inc.

Honeywell Process Solutions

ii Experion Support Software Change Notice R310.2

United States and Canada

Europe, Middle East, and Africa (EMEA)

Contact: Honeywell Global TAC – Korea

People’s Republic of China

iv Experion Support Software Change Notice R310.2

Mail: Honeywell Japan Inc.

World Wide Web

R310.2 Experion Support Software Change Notice v

ATTENTION: Identifies information that requires special

TIP: Identifies advice or hints for the user, often in terms of

REFERENCE - INTERNAL: Identifies an additional source of

CAUTION Indicates a situation which, if not avoided, may result in equipment

CAUTION: Indicates a potentially hazardous situation which, if not

WARNING: Indicates a potentially hazardous situation which, if not

vi Experion Support Software Change Notice R310.2

1. ABOUT R310.2 SUPPORT SOFTWARE.....................................13

2. INSTALLING SUPPORT SOFTWARE.........................................15

3. REMOVING SUPPORT SOFTWARE...........................................33

R310.2 Experion Support Software Change Notice vii

4. DOCUMENTATION UPDATES/ADDITIONAL INFORMATION .. 37

5. SPECIAL CONSIDERATIONS .................................................... 45

viii Experion Support Software Change Notice R310.2

7. SPECIAL CONSIDERATIONS FOR SYSTEMS WITH PROCESS

R310.2 Experion Support Software Change Notice ix

7.3 Engineering Tools .........................................................................................68

8. PROBLEMS RESOLVED IN THIS UPDATE............................. 107

x Experion Support Software Change Notice R310.2

Fieldbus Interface Module-Series C ...................................................................................108

R310.2 Experion Support Software Change Notice xi

OPC Alarm/Event Client .................................................................................................... 126

xii Experion Support Software Change Notice R310.2

To check the Honeywell Online Support site:

R310.2 Experion Support Software Change Notice 13

1.2 Applicability of R310.2 Support Software

1.3 Contents of this Update

14 Experion Support Software Change Notice R310.2

Scenario For further information

Factory installation Follow the instructions in the Experion Software

Update from R310.1 to R310.2 Follow the instructions in this section.

1 Server, e-Server, ESVT

2 Console Station, Flex Station, EST

3 e-Server premium access client

5 SIM-C200, Remote Engineering and Station Server

6 EMB servers and EMB clients

7 C200/C300 controller nodes

R310.2 Experion Support Software Change Notice 15

Verifying the version of Experion installed on the node

To verify Experion version for EMB Server and EMB client:

To verify Experion version for all other nodes:

Loss of view during installation of Support Software

16 Experion Support Software Change Notice R310.2

Virus Scanning and Protection

2.2 Server, e-Server and ESVT Installation

Preparing a redundant server (go to step 6 if there is no redundant server)

Updating server nodes

R310.2 Experion Support Software Change Notice 17

12 a) From the Installation Confirmation screen appears.

18 Experion Support Software Change Notice R310.2

Verifying the updates are successful

14 Verify the CAB update was successful: