r432.2 software change notice - honeywell › library › support › ... · 2.2 new features and...

Experion PKSR432.2 Software Change Notice

EPDOC-X175-en-4322BJanuary 2018

Release 432.2

Document Release Issue DateEPDOC-X175-en-4322B 432.2 0 January 2018

DisclaimerThis document contains Honeywell proprietary information. Information contained herein is to be used solelyfor the purpose submitted, and no part of this document or its contents shall be reproduced, published, ordisclosed to a third party without the express permission of Honeywell International Sàrl.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the impliedwarranties of merchantability and fitness for a purpose and makes no express warranties except as may be statedin its written agreement with and for its customer.

In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The informationand specifications in this document are subject to change without notice.

Copyright 2018 - Honeywell International Sàrl

2 www.honeywell.com

Contents

1 Before you begin ................................................................................................................................... 52 Introduction ............................................................................................................................................ 7

2.1 About this point release ...................................................................................................................................... 82.2 New features and enhancements ......................................................................................................................... 92.3 Limitations ........................................................................................................................................................ 102.4 Resolved PARs .................................................................................................................................................. 11

2.4.1 Resolved PARs ................................................................................................................................... 112.5 Change impact .................................................................................................................................................. 27

2.5.1 Control change impact ....................................................................................................................... 272.5.2 Operational change impact ................................................................................................................ 272.5.3 Infrastructural change impact ............................................................................................................ 28

2.6 Known Issues .................................................................................................................................................... 292.6.1 Engineering Tools/Advanced Control/Operations ............................................................................. 292.6.2 Engineering Tools/Control ................................................................................................................. 352.6.3 Control ............................................................................................................................................... 692.6.4 Operational/Control ........................................................................................................................... 72

2.7 What task do you want to accomplish? ............................................................................................................ 752.7.1 Clean installation of R432.2 .............................................................................................................. 752.7.2 Upgrade to R432.2 from R432.1 ....................................................................................................... 752.7.3 Migrate to R432.2 from R43x.x and R4xx.x releases ....................................................................... 75

3 Getting started ...................................................................................................................................... 773.1 Applicable nodes .............................................................................................................................................. 783.2 Applicable modules .......................................................................................................................................... 793.3 Supported migration and upgrade paths ........................................................................................................... 80

3.3.1 Supported server migration paths ...................................................................................................... 803.4 Supported server upgrade paths ........................................................................................................................ 813.5 Supported controller migration paths ............................................................................................................... 823.6 Downloading the point release media ............................................................................................................... 843.7 Downloading the Experion PKS PDF Collection media .................................................................................. 853.8 Downloading Experion PKS Upgrade Tool Components media ..................................................................... 86

4 Upgrade to Experion PKS R432.2 ....................................................................................................... 874.1 Upgrade sequence ............................................................................................................................................. 884.2 Upgrade checklist ............................................................................................................................................. 894.3 Preparing for upgrade ....................................................................................................................................... 904.4 Upgrading the non-redundant server node by installing the point release ....................................................... 91

4.4.1 Pre-installation steps .......................................................................................................................... 914.4.2 Stopping the services ......................................................................................................................... 914.4.3 Installing the point release ................................................................................................................. 924.4.4 Validating the point release installation ............................................................................................. 924.4.5 Post-installation tasks ........................................................................................................................ 93

4.5 Upgrading the redundant server by installing the point release ....................................................................... 944.5.1 Pre-installation steps .......................................................................................................................... 944.5.2 Stopping the services ......................................................................................................................... 954.5.3 Installing the point release ................................................................................................................. 954.5.4 Validating the point release installation ............................................................................................. 96

3

4.5.5 Post-installation tasks ........................................................................................................................ 964.6 Installing the point release on Server A ............................................................................................................ 97

4.6.1 Pre-installation steps .......................................................................................................................... 974.6.2 Stopping the services ......................................................................................................................... 974.6.3 Installing the point release ................................................................................................................. 984.6.4 Validating the point release installation ............................................................................................. 984.6.5 Post-installation tasks ........................................................................................................................ 99

4.7 Upgrading clients with the point release ........................................................................................................ 1004.7.1 Pre-installation steps ........................................................................................................................ 1004.7.2 Stopping the services ....................................................................................................................... 1004.7.3 Installing the point release ............................................................................................................... 1014.7.4 Installing the point release on Premium Access clients ................................................................... 1014.7.5 Validating the point release installation ........................................................................................... 1024.7.6 Post-installation tasks ...................................................................................................................... 102

4.8 Upgrading the ACE/ SCE/ EHG by installing the point release .................................................................... 1034.8.1 Pre-installation steps ........................................................................................................................ 1034.8.2 Stopping the services ....................................................................................................................... 1034.8.3 Installing the point release ............................................................................................................... 1044.8.4 Validating the point release installation ........................................................................................... 1044.8.5 Post-installation tasks ...................................................................................................................... 104

4.9 Post Install Activities after all nodes have been upgraded ............................................................................. 1064.10 Updating common components .................................................................................................................... 1074.11 Installing PHD Point Server Patch ................................................................................................................ 108

4.11.1 Installing PHD Point Server patch ................................................................................................. 1084.11.2 Validating PHD Point Server installation ...................................................................................... 108

4.12 Migrating controllers .................................................................................................................................... 1094.12.1 Updating the firmware ................................................................................................................... 1094.12.2 Firmware revisions ........................................................................................................................ 109

5 Problems resolved in R432.1 ............................................................................................................. 1135.1 Common components resolved PARs ............................................................................................................. 1145.2 Installation and migration resolved PARs ....................................................................................................... 1175.3 Servers and stations resolved PARs ................................................................................................................ 1185.4 Controllers and tools resolved PARs .............................................................................................................. 119

6 Troubleshooting Instructions ............................................................................................................ 1237 Special considerations in R432.2 ..................................................................................................... 125

7.1 Running eServer on systems with Internet Explorer 11 ................................................................................. 1267.2 Microsoft hotfixes ........................................................................................................................................... 1277.3 Alarm Paging .................................................................................................................................................. 1287.4 Patch Considerations in R432.2 ...................................................................................................................... 129

7.4.1 DSA – Alarm and Event Report ...................................................................................................... 1297.4.2 DSA Advanced Security .................................................................................................................. 1297.4.3 IEC60870 Interface .......................................................................................................................... 1307.4.4 Uniformance PHD and history tag synching ................................................................................... 1307.4.5 Integration with other products ........................................................................................................ 130

8 Support and other contacts .............................................................................................................. 1338.1 Documentation feedback ................................................................................................................................ 1348.2 How to report security vulnerability? ............................................................................................................. 1358.3 GTAC Support ................................................................................................................................................ 136

8.3.1 Subscribe for Automated Email Alerts: ........................................................................................... 1368.3.2 Further support required? ................................................................................................................ 1368.3.3 Training classes ................................................................................................................................ 136

9 Notices ................................................................................................................................................ 137

CONTENTS

4 www.honeywell.com

1 Before you begin

HPS Migration Center of Excellence (COE) handles Experion migration planning related activities. For all pre-migration and site-specific queries, contact Migration COE at [email protected].

For any issues while performing migration, contact Global Technical Assistance Center (GTAC). For moreinformation, refer to “GTAC Support” section in this document.

AttentionThe latest software, documentation, and antivirus updates are available in the www.honeywellprocess.com. Ensure touse the latest updates before performing an upgrade or migration procedure

5

1 BEFORE YOU BEGIN

6 www.honeywell.com

2 Introduction

Related topics“About this point release” on page 8“New features and enhancements” on page 9“Limitations” on page 10“Resolved PARs” on page 11“Change impact” on page 27“Known Issues” on page 29“What task do you want to accomplish?” on page 75

7

2.1 About this point releaseThis point release has the following major enhancements.

• Addresses issues and provides improvements requested since the release of Experion PKS R432.1.

Attention1. This point release is applicable for R400.1, R410.1, R430.1, R431.1, R432.1 or with point releases on them.2. This feature is qualified if individual server patches or TPN server patches are installed on the point releases.3. This feature is not qualified if individual Tools or Controller patches are installed on PC nodes. For example,

R400.1 Controller Patch 3, R400.2 Tools and Controller Patch 9, R410.1 Controller Patch 4, and so on. In suchcases, you must install the later qualified point release on the PC nodes and use this feature. For example, ifyou are at R400.2 Controller Patch 7, you must install R400.3 and then install R432.2.

4. This feature is not qualified if there are Controlled Patch Controlled Release or Hotfixes installed on thesystem. These patches or hotfixes have to be uninstalled from the PC nodes (excluding the controllers/IOs),and the cluster (including controller/IOs) must be upgraded to the qualified point release before using thisfeature. For more information, contact HPS Migration Center of Excellence (COE).

5. This new feature does not impact the earlier rule of direct migrations of controllers or IOs from any pointrelease or patch to any target release as mentioned in the site-specific migration guide and scenario-specificmigration guide. For qualified controller migration paths, refer to the Supported Controller Migration Pathssection in this SCN.

Attention– Controller firmware upgrade or migration is only required if the system is experiencing one or more problems

resolved given in the Tools and Controller resolved PARs section.– If you intend to upgrade or migrate controllers, be sure to contact HPS Migration Centre of Excellence (COE)

at least four weeks before installing this point release.– This SCN includes a prioritized Product Anomaly Report (PAR) summary. Contact the Honeywell Technical

Assistance Center (TAC) for assistance if you observe issues not addressed in this SCN.

2 INTRODUCTION

8 www.honeywell.com

2.2 New features and enhancements

Support for Series C MARK-II IOs• Starting from R432.2, Series C Mark-II IOs (DI-24, DO-24, DISOE) can be configured on C300 controller.• For more information on Series C Mark-II IOs, refer Series C Mark II IO User’s Guide.

AttentionUsing MARK-II IOs before migrating the C300 controller to R432.2 impacts future release migration. So, ensurethat MARK-II IOs are used only after migrating the C300 controller to R432.2.

Virtual Infrastructure Notifications in Experion System Alarm Summary• You can use the System Status Display in Experion Station to monitor the various virtual infrastructure

status alarms. For more information about virtual infrastructure status alarms, refer to System AlarmsReference.

Security enhancemen• Experion PKS Client Tools are vulnerable to a Denial of Service attack. A client tool process is used for

configuring Series C devices firmware and it is not part of critical process control. The process is used onlyto configure firmware and not continuously running in the background.

2 INTRODUCTION

9

2.3 Limitations

Point release removal

AttentionYou cannot uninstall/remove point releases. Take a backup of your system, for more information contact your localHoneywell Process Solutions Customer Contact Center (CCC) or visit www.honeywellprocess.com or contactMigration COE at [email protected].

Localization

[ ] Not impacted [ ] Point release may contain strings in English. A Localization version to be included in the nextrelease.

Point release distribution

[ ] Not limited [ ] Limited

2 INTRODUCTION

10 www.honeywell.com

2.4 Resolved PARs

Related topics“Resolved PARs” on page 11

2.4.1 Resolved PARs

AttentionThe Patch Name column indicates if this PAR was resolved in a previous Patch/Hotfix.

Server

PAR Subsystem Description Patch Name

1-5KLI3QD Alarm Pager

Unable to send alarm pages via SMS ifthe GSM modem does not support someAT commands Not Applicable

1-5TYZSXH Displays - GeneralALGO 69 parameter block values notdisplaying in sysalgo069.htm Not Applicable

1-2VL0M7XDisplays - SCADAControllers

If the Station access level changes (e.g.oper to mngr), the list of controllersshown on the SCADA ControllersDisplay does not update unless thedisplay is refreshed Not Applicable

1-4ZXVGTXDisplays - SCADAControllers

On the SCADA Controllers page thecount of controllers may be incorrect

Experion PKS R432.1 ServerPatch 1

1-5LWIP7XDisplays - SCADAControllers

The SCADA Controllers Summary isunable to display Chinese Characters Not Applicable

1-499WDLF DSPLY Subsystem

Calling a Group Display using Groupkey or Group toolbar button from aGroup Trend view always navigates tothe same group. Not Applicable

1-4MJGB8L DSPLY Subsystem

On rare occasions it is possible for allflex stations to disconnectsimultaneously Not Applicable

1-5GDVO7P DSPLY Subsystem

Unable to perform a data entry on analphanumeric that has a data binding aswell as script data binding. Not Applicable

1-6GMVAZ1 DSPLY Subsystem

After silencing or acknowledging aselected display element, that element isdeselected Not Applicable

1-6C72AGD DSPLY Subsystem

Performing a write using script data to apoint that has control confirmationenabled may not complete successfully. Not Applicable

1-77EZP85 DSPLY Subsystem

Station Raise and lower button is notshowing all the output states of statuspoints (SCADA) on a DSP schematicwhen using "auto select of OP" option. Not Applicable

2 INTRODUCTION

11


1-4JZQC1T Eng - Point Build (pntbld)

When downloading a point having aspace character in the Engineering Unitsfield, the Engineering Units field will betruncated. All the characters after thespace will be removed. Not Applicable

1-3WOOIY1 Event Archiving

Nightly removal of archived events doesnot occur after a migration from pre-R400 Not Applicable

1-55EKMA5 GDA - Notifications

When a server(publisher) is connectedvia DSA to an older releaseserver(subscriber), some actions on thepublisher may cause a "Error synchingtags" alarm to occur on the subscriber Not Applicable

1-5LXAATS GDA - Points

When using peer reference to write toSCADA points, if the source point is inerror a temporary DSA disconnect canoccur Not Applicable

1-4EQQXUD History - Periodic

Gap is seen on trend when standardhistory parameters are configured withan offset Not Applicable

1-57GE2SJ History - Periodic

Averages will not be calculated for pointparameters with offsets greater than thehistory rate Not Applicable

1-4REEE99 Notification Management

Online comments for an alarm are notvisible in the alarm summary if thecomments get captured as part of anevent archive but is visible when the textin the comments box are highlighted Not Applicable

1-5BY7EFZ Notification Management

Points that re-alarm constantly for aperiod of time and contain at least onestring flexible attribute may cause anapplication error in server notificationmanager Not Applicable

1- 52HP9IP Notification Presentation

When server wide settings areconfigured to prevent an operator frompausing the alarm summary, the systemstill allows the operator to pause thealarm summary even though the Pausebutton is shown as disabled. Not Applicable

1-50YJU4J OPC HDA Server

If a new tag is assigned to standardhistory in Experion, Experion may stopsending history to PHD for all tags at thesame history rate as the new tag Not Applicable

1-5385PWX Reports

The Point Attribute "State" report outputmay be missing some CDA pointparameters that match the report criteria Not Applicable

1-4WWZA5N TPS Interface

If the TPS System Status or TPSConsole Status indicator is configuredfor audible annunciation, sometimes theaudible annunciation may be triggeredincorrectly Not Applicable

1-61CGWYS CDA Integration

Server may not failover automaticallywhen CDA service stops on primaryserver Not Applicable

2 INTRODUCTION



1-614YNM1 Console Station

A newly installed console station willnot synchronize with a server that hasbeen migrated to R432


1-474EQ3D GDA - Points

Display callup slower than expected forDSA data on console station when theDSA link is a high latency channel Not Applicable

1-4JWIEYZ GDA - Points

GDAServer can unexpectedly terminatewhen performing a subscribe cancel inan overloaded state Not Applicable

1-6JMLH7J GDA - PointsEnhancement to allow logging of OPCapplication writes to Experion log files


1-6XPWMUX IEC 870 InterfaceIEC870 Point Server Interface DataConnection is showing Access Denied Not Applicable

1-68YG9O9 Notification Management

When console stations are restarted,previously non suppressed CDA andTPS alarms on that console station canbe automatically suppressed if they arepart of an active suppression group Not Applicable

1-6BHMSUJ Notification Management

Messages are not automatically markedas confirmed when the message block isset to INACTIVE in the controller Not Applicable

1-68YG9RX Notification Management

The priority column for electronicsignature events contains the string "J00" instead of being blank Not Applicable

1-6P17ID1 Notification ManagementOption to annunciate alarms even whenoperator is logged off does not work Not Applicable

1-6FIP9XH Notification Management

In rare circumstances, alarms and eventsmay not be annunciated on a redundantserver when it becomes primary Not Applicable

1-6S4OJO1 Notification Management

In rare circumstances, the ServerNotification Manager memory mayincrease while the alarm summaryremains open, which could result inperformance degradation of the server Not Applicable

1-52BH2RH Notification Presentation

When using print and print preview fromthe event summary the values in the"previous value" column does not matchwhat is seen in the summary Not Applicable

1-6JX45EP ODBC Driver

ODBC query to flexible point table maycause many transactions to TPS whichmay cause delays to other clients readingand writing TPS point parameters


1-6CE2DPJ Operator Security

Advanced Parameter Security settings donot work with SCADA auxiliaryparameters with custom names Not Applicable

1-71R0PU1 Operator SecuritySome CDA parameters cannot becontrolled by Electronic Signature Not Applicable

1-6CEI07T Point databaseIf a DCT is taken, shheap.exe mayunexpectedly terminate


1-6AX08X1 Point Servers

PHD point server will continuallydisconnect from Experion when datasubscribed


2 INTRODUCTION

13


1-6P5CXP5 Reports

Running a Point Attribute BadPV reporton a system with lots of OMA PointServer points may cause the OMA PointServer to disconnect Not Applicable

1-7A79NPP Scanning Subsystem

Manually setting the PV of a SCADApoint from an alarmable value to a non-alarmable value does not return thealarm to normal Not Applicable

1-6N0F0UR System LibrariesReliability improvements to DSA andconsole stations Not Applicable

1-6SJHA8U System Libraries

Unexpected server failover occurringwhen referencing history parametersindirectly in trends or server scripts Not Applicable

1-452JMJP TPS Interface

If multiple messages are generated onTPS with identical descriptions andtimestamps, they may not all be correctlyannunciated on the Experion messagesummary causing a mismatch betweenExperion and native window Not Applicable

1-61CI8M9 TPS Interface

On the alarm summary and trend display,the units for some TPS HG points showsas blank Not Applicable

1-72NR95X GDA - Points

DSA may show incorrect value forparameter if written over DSA thenimmediately toggled back by controller Not Applicable

1-7ATE9CP Scanning SubsystemDNP3 SCADA Point does not show badquality in case of open loop in the field


1-7BH2KYW TPS Interface

The TPS System Status and TPSConsole Status indicators in the Stationstatus bar may show as blank boxes afterthe ES-T is rebooted Not Applicable

1-5FSH4YN Alarm Pager

When alarms are elevated using alarmelevation, the elevated alarms are notpaged


1-5XDJXKX Allen Bradley InterfaceAllen Bradley scan task does not handleuser defined scan formats. Not Applicable

1-4F6UBP Console Station

Console Station temporarily losessynchronization with server while pointsare being downloaded to server


1-5JAN1IF Displays - General

The option ""MNGR or ENGR securitylevel required to change traces” is notenforced on System Trend Configurationdisplay. Not Applicable

1-5VU5LJF Displays - GeneralSummary Restriction in Server widesettings is not working Not Applicable

1-4UDMILX DSPLY Subsystem

Cannot open Native Window Displays("0xxx") using Associated Displayfunction of the Experion Station if theassociated display contains only numberswith a leading zero. Not Applicable

2 INTRODUCTION



1-5OX49OR DSPLY Subsystem

Repeatedly doing a reload on a faceplatewhile having the Engineering tab on thepoint display open may cause thefaceplate to show dashes. Not Applicable

1-66AGIF5 DSPLY Subsystem

An invalid value can be written to an SPor OP if an out of tolerance value isentered and a table linked to the sameparameter is scrolled before the resultingcall out is closed


1-5FUFN55Electronic FlowMeasurement

Bristol Babcock devices provide non-existent times for EFM records during aDST changeover, which causes therecord not to get exported Not Applicable

1-4ZWXRUP GDA - Points

Requesting enumeration info for non-enumerated parameters over DSA cancause stability issues on the Experionserver


1-4PN6MID History - Exception

Gaps in trend can sometimes occur forpoint parameters assigned to exceptionhistory


1-3R7084A Installation - PatchesAfter migration log files show donglerelated entries that shouldn't be shown Not Applicable

1-4QEJZ5D DSPLY Subsystem

Unable to page forward/back to navigatefrom a HMIWeb display to a NativeWindow display. Not Applicable

1-4RS9YKJ Notification Management

Modification of system alarm prioritiesin Configuration Studio should only beallowed by a user with MNGR access Not Applicable

1-4SQPO3V Notification PresentationAlarm help cannot be viewed fromconsole stations


1-4A8HFQB OPC Data Client (Flexible)Unable to upload OPC Advance pointsto Quick Builder


1-53OEB9P OPC Data Server

Browsing the Experion OPC server willnot work for a remote DSA point whenthe point has been built on 2 or moreservers with the same name Not Applicable

1-5DC4Y85 Reports - Microsoft ExcelExcel reports configured for printeroutput fails for MS Excel 2013


1-4M5S1D3 TPS Interface

If an EST is not running when combopoints are downloaded, combo pointparameters from this EST will be readvia the TPS interface rather than theCDA interface


1-4TP653J Utilities (non- engineering)

The rule 'Non blank page titles' in theHmiwebupdate sample files needs to beremoved Not Applicable

1-4GIPR5G Notification Management

No ENABLE event is generated forSCADA points when the "Journal Only"option is enabled Not Applicable

1-7LBRAH3 DSPLY Subsystem

When accessing large amounts of variantstring data, the Server Display processresource usage may increase Not Applicable

2 INTRODUCTION

15


1-86BHJUZ DSPLY Subsystem

Setting a value via script data takeslonger than expected to get reflectedback to the display. Not Applicable

1-469ECSN Eng - Point Build (pntbld)

The auxiliary parameter name on theANA auxiliary display tab is showinginverse video. Not Applicable

1-45L8OUT Notification ManagementDynamic Alarm Suppression does notshow all SCADA alarm conditions Not Applicable

1-83DL4VV GDA - DSA Events

In the filtered Event Summary, the alarmlimit appears incorrectly as a very largenumber Not Applicable

1-5PXYBIZ GDA - Points

In rare circumstances after a redundantfailover, DSA subscribers and consolestations may take up to 30 minutes tosynch to the new primary server. Not Applicable

1-81FJBWZ History — Periodic

History values are interpolated in StationTrend for extended history values if theextended history snapshot is set to 15-minute periods. Not Applicable

1-7LERZAG Migration[M & I] On R432.2 setup Experionrelease Showing R432.1 Not Applicable

1-7LRAW5T Migration

[M & I] Migrated Console connectedwith ServerA (On R431.4) during dualprimary Not Applicable

1-7XU724X GDA — Notifications

Occasionally the messages in the NativeWindow and Experion messagesummaries may not match. TPSconfirmable messages may reappear inthe Experion message summary a shorttime after being cleared and be requiredto be cleared again. Not Applicable

1-57YP52N GDA — Points

DSA subscription resource usage canincrease resulting in disconnect andreconnect of DSA periodically Not Applicable

1-4M5R9Y5 Notification Presentation

The alarm help faceplate doesn't pre-select an alarm condition if the alarmhelp is called on a container point andthe most important alarm is on a statuspoint Not Applicable

1-7M2RJ31 ODBC Driver

Snapshot history value can returnINTERPOLATED even though rawhistory value is GOOD at same reportedtimestamp Not Applicable

1-53LU7XH OPC Data ServerUnable to browse container points fromthe Experion OPC Server Not Applicable

1-7JNTAM1 Presentation - Esig dialog

In rare cases, invoking the ElectronicSignature Dialog from the messagesummary may cause a Stationapplication error Not Applicable

1-4VC0FQ3 Redundancy - Server

Synchronization of servers with manyhistory points assigned may fail, andbackup server has windows event forunexpected termination of dual_onsrv Not Applicable

2 INTRODUCTION



1-7JHJF5T Reports

When requesting an Alarm and EventDSA report using Experion R43x froman earlier release over DSA, the reportmay state "Unable to connect to server"in the report output Not Applicable

1-7LWW66H TPS Interface

When an alarm is received on a combopoint parameter, the parameter mayrevert back to reading through TPSinstead of through CDA which maycause LCN congestion Not Applicable

Quick Builder


1-4H3810D ComponentsOut of memory error happens afteropening and closing QB many times Not Applicable

1-4RHF819 Property Sheets

Download point fail when switchingdifferent types of point and pointproperty UI doesn't refresh when listview has some special columns Not Applicable

1-5IZDHMV Object Editing

Unable to select a child asset duringpoint creation whilst in Quick builderasset browser Not Applicable

1-89GLNOF Components

QB is not opening after 2nd attempt ofreconnecting config studio with any userleave access. Not Applicable

HMI


1-THVUCJ Station Callouts

The prompt to confirm a page alarmacknowledgement may not show thedisplay name Not Applicable

1-529DISL Station Rendering

Localizing Experion system displaysmay cause an application error inStation. Not Applicable

1-3YM94U3 Station PrintingNeed method for enabling Metafileprinting on a per display basis. Not Applicable

1-47LFZEPStation ApplicationFramework

Station does not show a warningmessages that Script Scan is enabledwith McAfee 8.8. Not Applicable

1-2WFZSO7 HDB Script EditorDisplay Performance Report details doesnot match for scripts. Not Applicable

1-3A9J7R1 Station Navigation

Station does not register first called updisplay in navigation history aftersigning on as a user having differentsecurity level than the previous user. Not Applicable

1-4MDYF0X Station Navigation

Single window station should have anoption to retain navigation history afteran operator level changes. Not Applicable

2 INTRODUCTION

17


1-3E20OZX Station Chart/Trend

Adding a point to a trend after scrollingforward in time results in the pointparameter incorrectly plotted. Not Applicable

1-5ZHKLZX Station Web Browser

Displays in .DSP format do not getdisplayed in eServer premium accessbrowser Not Applicable

1-3FKDOFL HDB other or unknown

HMIWeb Display Builder unable tohandle certain non-ASCII characterinputs such as Japanese, Chinese andKorean Not Applicable

1-3OXO0JDStation eServer StandardAccess

eServer Standard Access does not loadthe page when URL has specialcharacters in arguments Not Applicable

1-3OZ06IZ HDB Display Migrator

Non-English text characters (forexample, German umlauts) in HMIWebdisplays are replaced with non-readablecharacters when the display is migratedusing the Bulk Display Migrator. Not Applicable

1-3SMSKMD HDB ValidatorScript validation does not recognize me/this and custom properties Not Applicable

1-3S2YM07 Station CommunicationsNative Window "F" LED Does NotLight Up when configured with IKB. Not Applicable

1-3UBRTHK Station Keyboard Support

Station does not call next group detailspage after group number 1600 inresponse to Keyboard Pg-Down or PG-FWD commands Not Applicable

1-3TWUIT5Station NotificationPresentation

Configuring an alarm state icon to showdisable state may show Errors on Pageerror when an incorrect parameter isused. Not Applicable

1-3R4C1M6 Station Keyboard Support

Performing a number of rapid raise/lower operations on a TPS faceplate andthen quickly pressing AUTO beforethese complete can result in a subsequenterror for each queued raise/lower duringwhich you can't do further controloperations Not Applicable

1-3ULKMRCStation ApplicationFramework

Enhance Station to better support issuewhere there is a lag between a controllerreport being written to disk and sharedon a network share, and when it isactually able to be accessed from Stationrunning a remote node. Not Applicable

1-3UKP9S0 Station Chart/TrendHeadings of trend with tabular historymay be missing on call up Not Applicable

1-3XWO2ED Station Chart/Trend

Horizontal axis toolbar and scrollbar forthe chart area may not get rendered whentrend type is changed or station windowis resized. Not Applicable

1-43XIDOL Station Web Browser

Buttons configured to callup anotherdisplay do not work in eServer PremiumAccess client node. Not Applicable

2 INTRODUCTION



1-4E00B1V Station PrintingOption "page setup" for print notworking Not Applicable

1-3YGQAN9Station eServer StandardAccess

Displays contains an alarm table do notload on eServer client Not Applicable

1-40HZQJ4 Station PrintingPrinting Trend on 100% zoom level doesnot print entire trend legend. Not Applicable

1-3S5STEO HDB Zooming

Scroll bars not appearing in the HMIWebDisplay Builder when zoom set to 100%or greater. Not Applicable

1-44D94VF Station Script Data AccessArray type data returned from the servercannot be accessed by display script. Not Applicable

1-47NCI07 Station Connection Dialog

Audible notification configured for analarm in Server configuration may notsound if a wav file has not beenconfigured in station connectionproperties. Not Applicable

1-48N8XDR Station other or unknown

Station in Multi-Window mode withmultiple command zones configuredmay experience an application errorwhen re-connecting. Not Applicable

1-46PSSVJ Station other or unknownMessages causing default beep sound tobe played regardless of settings. Not Applicable

1-49Y1VCF Station Alphanumeric

Unable to enter value in thealphanumeric that has a parameter beingupdated through a script. Not Applicable

1-4AA4HUV Station Alphanumeric

Value entered in an alphanumeric getstruncated if its fillColor property is beingupdated by a script. Not Applicable

1-4AOKC0BStation NotificationPresentation

If the alarm summary is open on asystem with a large number of alarms,resource usage for Station will increaseand will cause station to becomeunresponsive Not Applicable

1-4EK38Q1 Station Display Scripting

Provide a means to defer the firing ofOnUpdate event until after the entirepage has received its first data updateand the OnPageComplete event hasfired. Not Applicable

1-4IWPLMU HDB Shapes

HMIWeb Display Builder does notremove the shape files upon deleting anembedded shape from a display. Not Applicable

1-4IQJQUNStation ApplicationFramework

Scrollbars appear in Station at 100%zoom level even when display is smallerthan window size. Not Applicable

1-4OKHJGL Station Scripting

Page position properties returned byscript on page unload is inconsistentwhen tabs are enabled in multiwindowstation. Not Applicable

1-4Z41CQJ Station Navigation

First mouse clicks are ignored by multi-window station with tabbed browsingenabled. Not Applicable

2 INTRODUCTION

19


1-5KNO20R Station Script Data Access

Blinking and navigation may not work ifshape script data is bound to multiplecustom properties that has its value set to<NULL> on the display. Not Applicable

1-5DDFGSV Station Popups/Faceplates

Station may exit with an applicationerror if TabletInputService is notrunning. Not Applicable

1-5D50B7PStation eServer StandardAccess

eServer Standard Access does not loadtemplate/parameterized displayscorrectly. Not Applicable

1-5FT2850 Station ScriptingUnable to access GetOptionList propertyof Combobox object via script. Not Applicable

1-5J6T0B1 Station Popups/FaceplatesFaceplates for TPS DIGIN points taketoo long to load on operator touch panel. Not Applicable

1-6092NU1 Station Operator Touch PanelOTP change zone not enabled when TPSfaceplate is loaded. Not Applicable

1-5SA2SGR HDB Custom Properties

Updating shapes in HMIWeb DisplayBuilder does not always work asexpected. Not Applicable

1-5TDV6KR Station Operator Touch Panel

Custom faceplate loaded in OperatorTouch panel gets replaced with thedefault faceplate when attempting tochange a parameter. Not Applicable

1-5HXKY9DStation ApplicationFramework

Unable to "restore" the next display toprevious size in safe view placeholderafter maximizing and then closingdisplay Not Applicable

1-5ZPN0XF Station Operator Touch Panel

Provide an option to allow displays to beinvoked on the screen by default, insteadof the Operator Touch Panel Not Applicable

1-62I20IZ Station Operator Touch Panel

Difficult to change the OP on thesysdtldigcomp_fp.htm faceplate from theOperator Touch Panel. Not Applicable

1-6C8RX0L Station other or unknown

On Japanese localized systems, when analarm is shelved, the Station messagezone displays an error message. Not Applicable

1-6K95K4RStation ApplicationFramework

Station may exit with an applicationerror when performing a detail commandresulting in a user prompt with nowindow selected. Not Applicable

1-6S0UT5S Station DSP Displays

In DSP displays raise/lower operationsdo not work correctly on points that havecontrol confirmation enabled. Not Applicable

1-6T09ORB Station Navigation

In single window Station, faceplates thatare "pushpinned" are closed after morethan 50 other displays are opened. Not Applicable

1-71T6Y4P Station Web Browser

In PA Client, push button navigating to anon-existing display causes the InternetExplorer to go to non-responsive state. Not Applicable

1-72V3JILStation eServer StandardAccess

eServer Standard Access fails to connectafter connecting a few times. Not Applicable

2 INTRODUCTION



1-7J6A8ZVStation eServer StandardAccess

eServer Standard access does not processparameterized displays with more thanone custom parameters. Not Applicable

1-7JZS09D Station Operator Touch Panel

Station with Operator Touch Panelconfigured and 'Auto hide message zone'set may experience an application errorwhen responding to a prompt. Not Applicable

1-7S6WERR Station Popups/Faceplates

Station application error may occur usingscriptable callouts with a Yes/No userresponse on faceplates contained withina Detail or Group detail display. Not Applicable

1-8086DSXStation ApplicationFramework

Station unable to call up displays afterreconnecting following a disconnectfrom a thin client remote session Not Applicable

Tools and Controller


1-3N3C5RD OPM-Upgrade Tool

[PCT] Readiness Check of C300controllers having UIOModConfig inHTS PCT SYS1 goes to Pending state. Not Applicable

CR 1323

FIM8 Module Redesigned to HandleYamaha controller Obsolescence (PAR1-402JB2N) Not Applicable

1-5DF8UQTControl Builder-Configuration Form

R430.4 - C300/C200 - DST did notimplement to cee's automatically. Not Applicable

1-5MQ3OD3 CTools[SFT] FIM8 Old module should be ableto flash back in older release. Not Applicable

1-3VHPSW5 C300 Controller[C300] intermittent loss of sync (DMAunderrun) -- R410 and newer releases Not Applicable

1-43QDTKB OPM-Migration Tool

Controller OPM fails via MigrationWizard when upgrading to anintermediate release (not latest) Not Applicable

1-41ZIIAM CEE-DatabaseHoneywell OPC DA Server BrowsingPoint Parameter Issue due to SR Not Applicable

1-3XYB3U7 Control Builder-Print

Fit chart on one page printing option hasbeen removed and defeats SBdocumentation strategy Not Applicable

1-4EHUYNT EBM-ToolsCB - Substitutes with Class based phasenot working Not Applicable

1-4IEW6ITSeries C Universal IOModules

SIM-C300 controller crashes when UIOHART parameters used in controlModule. Not Applicable

1-4MDYF9JControl Builder-Load/Upload/Update

Load Value While Active does not workfor inactive alias reference. Not Applicable

1-4MDYF85 Turbine ControlSpeed channels take long time to detectspeed and reset PV from NaN value. Not Applicable

1-1PY86FR Control Builder-HARTNewly added parameters are not gettingupdated after DB Migration Not Applicable

1-3GENLDR Control Builder-Chart[21790] - Inverted inputs with Bubble isnot working in R430. [BW-23642] Not Applicable

2 INTRODUCTION

21


1-J3UL85 I/O-Series C

Unexpected Idle on Series C IO Card.Improve logging capabilities to capturecause. Not Applicable

1-45C1VMV ModBus TCP Tools

Error 10409 LOOPMODE not storedwhen upload / update to project PCDImaster block Not Applicable

1-4LVQYI8 Control Builder-ChartMoving parameters on a faceplate usesthe wrong avatar, refer notes. Not Applicable

1-4LVQYHX Control Builder-ChartPrintjob name for autoprint is always"ChartPrinting" Not Applicable

1-45HABO5 Control Builder-Chart

Block configuration chart in blockproperty tabs empty if input parameterinverted Not Applicable

1-5AHMANT ModBus TCP Blocks

Experion R430/ Master Logic PLCcommunication testing issue with PCDI& C300 Not Applicable

1-58RPBWD Control Builder-Chart

Control builder consumes more than 1GB RAM while opening CM that hasfew OLE objects Not Applicable

1-57ITRMJ C300 ControllerNEXTPHASE should be part ofbacktrack save and restore Not Applicable

1-5BOZM7R Control Builder-LoadMismatch between Project andMonitoring after download Not Applicable

1-4JS04WJ Control Builder-Chart

All Blocks disappeared from MainHandler in Chart View but Table view isOK Not Applicable

1-5GXIU2J Control Builder-Chart

Wire color is getting updated on CBchart view but not getting the color at thestation chart view. Not Applicable

1-3XAHFEB Control BuilderHelp function in ControlBuilder do notwork correct Not Applicable

1-5JFWC0X Control Builder-ChartLarge charts in the Control Buildermainly SCM cannot be scrolled down Not Applicable

1-5ENI1B9 CTools

[PCT] C300 controller went into RDYstate and hold firmware flash whenflashing from 50 ms to 20 ms. Not Applicable

1-5IYFDP1 C200 to C300 Upgrade

API support for handling RevertOperation after CNET to FTE and C200to C300 upgrade. Not Applicable

1-68KMFFN C200 to C300 UpgradeRevert label not applied on vcs objectsnot upgraded for fte network Not Applicable

1-6ET7WQH C200 to C300 Upgrade

[M&I] Reverting to a label created priorto Up. was successful after Cnet to FTEwith QVCS Up. Not Applicable

1-5OF0HS7 Control BuilderIOREFERENCE blocks types cannot bechanged on the instance of the template Not Applicable

1-5J8FWRFControl Functions -Continuous

R430.2 Rolling Average For 1 monthand 1 Year fails Not Applicable

1-5Y86F0D EIP-COMMUNICATION

EIP - C300 Connection limitation: Only31 devices employing multicast canconnect with C300 Not Applicable

2 INTRODUCTION



1-63PU562 Profibus Interface Modules

When PGM switchover, all signals fromTurckIO devices become BadPV for fewseconds Not Applicable

1-476FASV Profibus Interface Modules

PGMs constantly dropping sync due toprofibus driver view of secondary lost toPrimary PGM Not Applicable

1-483ZP4R Profibus Interface ModulesPGM link failed with watch dog error onDSB load Not Applicable

1-64TNDN3 Profibus Interface ModulesSometimes PGM freezes and Noswitchover happens. Not Applicable

1-5N1DZGE Control Builder-Chart

Control Builder crash on Movingfunction block from project side in aninstance of template Not Applicable

1-5WFGE3L SIM-C300Exp R431.2 I/O reference block will notreceive output Not Applicable

1-6AVYGGNSeries C Universal IOModules

Corrupted UIO configuration after a'Module Not Calibrated' alarm Not Applicable

1-6FPB1MBEmbedded Controller/Gateway Platform

[C300] Cannot build boot2x_20 inR432.1 Not Applicable

1-6IHPSKR Control Builder-Chart

[21790] - Inverted inputs with Bubble isnot working in R430. [BW-23642] - Part2 of Fix Not Applicable

1-5Y1EVZLSCM-Sequential ControlModule

SCM transition gate output is not as perexpected. Not Applicable

1-5FJC9LZSCM-Sequential ControlModule

R410.2 ACE Behavior of SCM changedwhenever Dynamic Fetch is enabled Not Applicable

1-4D660E5 EBM-Controller[BASF] Phase Block Behavior uponRCM Restart Not Applicable

1-6FFE9T3 SIM-FFDMode switching of FF devicesconfigured in SIM-FFD does not work Not Applicable

1-6BII4XV Control Builder-ChartNew WPF-based TextComment blockcausing chart to load extremely slow Not Applicable

1-6BIMBLR Detail DisplaysHuge chart can fail to reload in case ofsecurity level change (Detail Displays) Not Applicable

1-44HZYH5 Server - Displays - GeneralTestscript still present onsysdtlPmioiopB.htm (Detail Displays) Not Applicable

1-5GNHBM7 Detail DisplaysScript error by sysdtlregctlb (DetailDisplays Not Applicable

1-4KV0YFH Control Builder-Chart

Chart View lose the navigation toselected blocks when zooming out,zooming in Not Applicable

1-3XPDBBS Control Builder-Chart

For several actions the CB chart viewjumps to the left upper corner of thechart (page A:1) Not Applicable

1-45MIXBX Control Builder-Chart

[M&I] CR1294] Control Builder issluggish when we open Chart View andCB is going to Not Responding st Not Applicable

1-5VW44OLEmbedded Controller/Gateway Platform

C300 cannot load Experion HiwayBridge firmware Not Applicable

CR1308 New Firmware update utility for CF9 Not Applicable

2 INTRODUCTION

23


1-6BQ1MYV IXP-Import Export

PMIO channel corruption on monitoringside after PMIO import and load withstrategy Not Applicable

1-6FHTM9D Checkpoint

[SFT_BL]After Rebooting the C300controllers without battery and restoringCP, data is not flowing Not Applicable

1-5TFXQ85Control Builder-SystemRepository

SR slowness in LRPC calls resulted inCDA DATA disconnects & LOV Not Applicable

1-6BBPB3TSeries C Universal IOModules

[ITT-UIO2] Secondary IOM's droppingsync/re-syncing causing a secondaryIOM crash to crash. Not Applicable

1-5ZRM9GHSeries C Universal IOModules

[ITT-UIO2] OPFAIL soft failure occursunder steady state running conditions. Not Applicable

1-6GC05OLSeries C Universal IOModules

UIO2 Secondary IOM periodically dropssync and then will re-syncs. Not Applicable

1-68S6OGNSeries C Universal IOModules

UIO-2 IOLINK timing variations fromStandard Series C Modules Not Applicable

1-6I3UGIZSeries C Universal IOModules

[SFT] After Secondary IOM powers upand sync's IOLINK errors are occurring. Not Applicable

1-44M4XUW SIM-C300

EPKS: Values are not communicated toAO channel configured usingIOREFERENCE after a CM load Not Applicable

1-3T0AHPR PGM Hilscher Sycon .NETSycon.net does not honor the slotassignment rules defined in the GSD Not Applicable

1-45HABO5 Control Builder-ChartBlock configuration chart in blockproperty tabs empty if input parameter Not Applicable

1-402JB2NFieldbus Interface Module-Series C

FIM8 Module Redesigned to HandleYamaha controller Obsolescence Not Applicable

1-5MQ3OD3 CToolsFIM8 Old module should be able to flashback in older release. Not Applicable

1-747WKBPFieldbus Interface Module-Series C

Firmware Flash Failed in New FIM8HW Rev C Not Applicable

1-7MQL1QD Control Builder-Chart

UDT CM navigation from another CM isshowing error (did not merge the fix of1-4LVQYHX to R432.2) Not Applicable

1-7K46OHD Firmware

With L2 Switches not configured perHON Best FTE Practices, Double EHPMfailure occurred. Not Applicable

1-71SLBYL CDA-Embedded

Momentary loss of peer to peer datawhen SCM with Dynamic Fetch enabledis running Not Applicable

1-6WY5OFZ OPM-On Process MigrationThe Patchdb.exe fails in scenarios whereEMDB is not opted as "Add-on Features Not Applicable

1-6W82OVNSeries C Universal IOModules

UIO alarms "Module Not Calibrated" onrapid temperature change Not Applicable

1-7XLS9QO C300 ControllerC300 Fail 00D1 on fetch of HARTparam from chan > 32 Not Applicable

1-3PFVFQB Network-FTE BridgeFTEB is susceptible to latent fault thatmay prevent comm path recovery Not Applicable

2 INTRODUCTION



1-7FQQA8PFieldbus Interface Module-Series C

Support for FIM4 HW revision-3 modulein Experion Not Applicable

1-3KER42VStandard Series C IOModules

Data corruption when counters arelatched during the read. Not Applicable

1-7XJLBGTStandard Series C IOModules

TVPROC is not getting turn on whenFCO was enabled Not Applicable

1-6MV9JY5 FF Interface Modules

Process values from ST3000 andSTT35Fs stop updating during FIM4migration. Not Applicable

Common Component


1-6AWH6P5 Experion Station-Faceplate

SWITCHAM TPS Points statusdisplayed in Experion Faceplate“sysdtltpsswitch_fp.html” Not Applicable

1-4E5XIRZ Experion Station-FaceplateNot able to change SP using IKB forHPM RegPV TOTALISER point. Not Applicable

1-5U8V83V Experion Station-FaceplateTPS faceplate heading on Orion Consolestation doesn't show TPS tag name Not Applicable

1-50XLTIZ Experion Station-Faceplate

Experion TPS & C300 Faceplates -operator confusion due to miss locationof Safety Interlock indicator Not Applicable

1-6092NU1 Experion Station-FaceplateOTP change zone not enabled when TPSfaceplate is loaded. Not Applicable

1-4YL169B Experion Station-FaceplateMissing point description on (fpcommonshape) faceplates, e.g., sysdtltpspid_fp Not Applicable

1-5VLJV2R Firmware

[ENB] EHPM Firmware does not updateIP Address that $FTESTSx displays useduring Experion migration. Not Applicable

1-4412Q77 HMIWeb TPN DetailsACM Alarm Help item is missing inExperion TPS Context menus Not Applicable

1-6WOQJV3 HMIWeb TPN Details[EHB-PIU]-HMI web display is missingfew PIU parameters please refer disp Not Applicable

1-5EL8Y5T HMIWeb TPN Details

FRCPERM parameter is missing inconfig page of station for RegPVHILOAVG point type. Not Applicable

1-5EL8Y8W HMIWeb TPN Details

SVALDBEU parameter is missing inconfig page of station for Processmodule point type. Not Applicable

1-5SGIY7T HMIWeb TPN Details

[EHB-PIU]-For emulated AO pointemulation(E) indication is not appearingin station Not Applicable

1-5ELW817 HMIWeb TPN Details

"CHOFSTPR" and "DIGALFMT"parameters are missing in station forDIGIN HG point type. Not Applicable

1-6AUK14FNetwork-Equipment andSupport

[PCT_HUW] CF9 uplink port goes downon network storm fault b/w L1 switch &CF9 nonuplink ports Not Applicable

2 INTRODUCTION

25


1-3HTGA7T SafeviewSetting global focus on tabbed displayscrashes non-Station displays Not Applicable

1-6GHC4QP Safeview

Can no longer drag small-maximizedwindows - SafeView should respectdisabled OS auto-arrange option Not Applicable

1-6P2MODT TPNServer

Unable to browse Hci.TPNServer pointparameters on an EAPP running v431.3from an OPC client. Not Applicable

1-748UO53 Safeview

Station multiwindow display crasheswhen navigating to detail tab inSafeView Not Applicable

1-71UW1YB SafeviewSafeView's wsmcli exception causingStation crash in given scenario Not Applicable

1-5207P43 HMIWeb TPN DetailsDiscrepancy on RegHG detail displayOP trip point parameters Not Applicable

1-7J85UT3 Safeview

Displays appear to iconize-restore uponinvocation, made obvious by Microsoftanimation Not Applicable

1-7JM58RN Experion Station-FaceplateSysdtltpsdiginout_fp missing rampreturn to value script Not Applicable

1-6JSCOCF Network FTEBSOD after Rebinding Adapters toFTEMUX without rebooting computer Not Applicable

1-7OER2JD Network FTEFTE Driver generates invalid ARPrequests adding to ARP traffic Not Applicable

1-7XY0PGP Operations

EHPM pointype PROCMOD parameterSEQERR is different on LCN (NativeWindow) as on HMIWeb display Not Applicable

1-7J85UT3 Safeview

Displays appear to iconize-restore uponinvocation, made obvious by Microsoftanimation Not Applicable

1-7LY2Y5D Safeview

LCNWINDOW randomly freezes...[leaks GDI objects with Menu bar OFFoption] Not Applicable

1-7M10Z4R SafeviewSafeView replacement of maximizeddisplay may be incorrectly positioned Not Applicable

1-82IS2S5 SafeviewSafeView titlebar buttons may shift in ananimated fashion Not Applicable

1-5VLJV2R Firmware

EHPM Firmware does not update IPAddress that $FTESTSx displays useduring Experion migration. Not Applicable

1-6P2MODT TPNServer

Unable to browse Hci.TPNServer pointparameters on an EAPP running v431.3from an OPC client. Not Applicable

1-6AUK14FNetwork-Equipment andSupport

CF9 uplink port goes down on networkstorm fault b/w L1 switch & CF9nonuplink ports Not Applicable

1-86J8UXF TPNServer

Post upgrade to R431.4, Exp graphicscannot write to TPS points usingindirection (with .external) Not Applicable

1-7HSTFR3 Signon Manager Signon Manager fails intermittently Not Applicable

2 INTRODUCTION


2.5 Change impactChange impact addresses the areas where control, operational, or infrastructural changes are delivered as part ofthe PAR fix. This is observed when migration occurs from a prior release to the current patch. A noticeablechange in behavior is observed after installing the patch. This section describes such change in behavior.

This point release affects multiple subsystems and some other products that integrate with Experion PKS. Somesubsystems will behave differently depending on whether an equivalent patch has been installed on the othersystems.

Please read Patch considerations for detailed information.

Related topics“Control change impact” on page 27“Operational change impact” on page 27“Infrastructural change impact” on page 28

2.5.1 Control change impactNot Applicable.

2.5.2 Operational change impactThe following PARs have operational change impact.

PAR 1-4MDYF0XDescription: Single window station should have an option to retain navigation history after an operator levelchanges.

Impact: In Single Window Station, when a user access level changes, the navigation history is reset. The fix forthis PAR introduces a registry key that allows optionally retaining navigation history after an operator change.

To configure this, add a registry key as below:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Honeywell\Station (DWORD32)ClearHistoryOnOperatorChangeWhen set to 0, Station will retain navigation history.

PAR 1-4EK38Q1Description: Provide a means to defer the firing of OnUpdate event until after the entire page has received itsfirst data update and the OnPageComplete event has fired.

Impact: In some cases the order in which certain events fire in Station could lead to undesired outcome. The fixfor this PAR introduces a registry key that allows synchronizing firing of OnUpdate event before all elements ofthe page have been loaded.


HKEY_LOCAL_MACHINE\Software\Wow6432Node\Honeywell\Station (DWORD 32) DeferOnUpdateWhen set to 1, Station will defer firing of OnUpdate event until the entire page has been loaded.

PAR 1-3R4C1M6Description: Performing a number of rapid raise/lower operations on a TPS faceplate and then quickly pressingAUTO before these complete can result in a subsequent error for each queued raise/lower during which youcan't do further control operations.

2 INTRODUCTION

27

Impact: Consecutive raise/lower commands get queued in Station, whereas the mode change commands are notqueued but processed asynchronously causing the above issue. This PAR fix allows for queueing of modechange commands via a new registry key.


KEY_LOCAL_MACHINE\Software\Wow6432Node\Honeywell\Station (DWORD 32)ModeCommandQueueEnabledWhen set to 1, Station will queue mode commands along with other commands.

Change in appearance of editable fields on faceplatesDescription: Improvements in visibility of currently selected element.

Impact: To make it easier to find the currently selected element on large screen displays as well as in generalusage, an alphanumeric is now highlighted with a blue background when selected.

2.5.3 Infrastructural change impactNot Applicable.

2 INTRODUCTION


2.6 Known IssuesThis section lists Experion known issues and workarounds for this point release.

Related topics“Engineering Tools/Advanced Control/Operations” on page 29“Engineering Tools/Control” on page 35“Control” on page 69“Operational/Control” on page 72

2.6.1 Engineering Tools/Advanced Control/Operations

Checkpoint

PAR Description1-286ELKP Error Indication: Checkpoint Service stops responding.

Description: When Checkpoint saves automatically (with Auto checkpointoption enabled) at times Checkpoint service stops responding after long run.

Recovery: Automatically checkpoint service gets restarted after the crash.

Workaround: None.

1-2BCAB6J Error Indication: Checkpoint service stops responding.

Description: Checkpoint services.exe stops responding during stability run.

Recovery: Automatically checkpoint service gets restarted after the crash.

Workaround: None.

1-TK8YFP Error Indication: Checkpoint file is in "Incomplete state".

Description: After loading a controller with CMs configured, restore window isshowing checkpoint file is in incomplete state

Recovery: Perform a manual checkpoint Save and try again the checkpointrestore operation.

Workaround: Perform a manual checkpoint Save and try again the checkpointrestore operation.

Experion Station- Faceplate

PAR Description1-7YASDYF Error Indication: "IN-SI" indicator remains even when one or both

INITMAN/SI states no longer 'true'.

Description: INITMAN and SI indicators are combined into "IN-SI" indicationwhen both are active; the indicator continues (incorrectly) to be shown when oneor both of the states is no longer active.

Recovery: To recover - i.e., not show the IN-SI indication when both no longeroccurring, reinvoke display.

Workaround: Re-invoke display (faceplate) Refresh the display/ Reinvoke thedisplay.

2 INTRODUCTION

29

PAR Description1-8POEE1F Error Indication: When entering a value in an alphanumeric, the black text on

blue background of the alphanumeric may adversely impact readability for someoperators.

Description: Editable text fields now have a blue background with black textwhen editing. This is difficult to read for color blind operators.

Recovery: None.

Workaround: None.

Experion Station-Native Window

PAR Description1-41F7B0N Error Indication: After key level is changed using IKB Key switch,

occasionally, the Native Window does not respond to the IKB Keystrokes forsome time (around 3-4 seconds).

Description: After key level is changed using IKB Key switch, occasionally,further keystrokes on the IKB will not be responded by the Native window forsome time (around 3- 4 seconds).

Recovery: Native window will recover from this condition, without any actionbeing required from the user.

Workaround: None.

HMIWeb Station - General

PAR Description1-3R1FRO9 Error Indication: Premium Access client does not work on ignoring IE prompt

to enable/disable HendrixBHO add-on.

Description: Unable to open the eServer homepage for Premium Access clientfor the first time after installation on ignoring IE prompt to enable/disableHendrixBHO add-on.

Recovery: None.

Workaround: When loading the eServer home page for the first time, click“Enabled” when Windows prompt for the HendrixBHO Class add-on.

2 INTRODUCTION


OPC Gateway

PAR Description1-2GZIVP6 Error Indication: Data values coming from the OPC Gateway may freeze based

on incorrect OPC Server function.

Description: Once the OPC Gateway subscribes to an OPC Server for a datavalue, it is unable to detect if the OPC Server has stopped updating this pointcorrectly. This can be visible where the data is seen to be "frozen" coming fromthe OPC Gateway but a new connection to the OPC Server by another client canget correct "live" data.

Recovery: The OPC Gateway is unable to recover only a single data value. If anOPC Server stops updating one of the points to the OPC Gateway one of twoactions can be taken. (1) (2)

1. Remove all requests for this point by clients of the OPC Gateway. Thisrequires unloading these points from Monitor.

2. Set the OPC Gateway to IDLE. This will result in the connection to the OPCServer being closed and ALL DATA from the OPC Gateway will go toFailsafe values. Commanding the OPC Gateway to RUN will restore all datafrom all points coming from the OPC Gateway.

Workaround: None.

Secure Communication Manager

PAR Description1-1TRB5UD Error Indication: Experion nodes stop communicating and/or deployment of

secure communications policies fail after a re-synchronize command.

Description: This outcome is possible if the configuration information of arestored Security Manager does not match or is incompatibly different than thesecure communication policies deployed and operating in the system.

Recovery: Modify secure communications configuration to restore systemcommunications. The changes to be made are dependent on which nodes havelost communication and whether the nodes are currently secured or not.

Workaround: First, always backup the Security Manager after securecommunications configuration changes, so that subsequent restores of theSecurity Manager will always match what has been deployed to the system.Secondly, before using the Re-synchronize command, carefully evaluate theconfiguration to be deployed vs the current system to decide if the commandshould be executed. See the Secure Communications User Guide for additionalinformation on backup/restore considerations and use of the re-synchronizecommand.

2 INTRODUCTION

31

PAR Description1-289JLQB Error Indication: Hardware replacement of the ESV node designated as

Security Manager with no backup or unusable backup results in a loss of SecureCommunications configuration data.

Description: If the Security Manager node is replaced and a backup of theSecure Communications configuration (through EBR or other means) was nottaken or cannot be restored, the configuration data is effectively lost and Securednodes can no longer be managed through the Secure Communications tool.

Recovery: Recovering the Secured nodes requires clearing their individualSecure Communications configuration and re-configuring the SecureCommunications system. Please refer to the "Secure Communications User'sGuide", Section "Node Maintenance" - Scenario "Restoring Security Managerwithout a valid backup".

Workaround: Plan regular backups of the Security Manager node. Recommendtaking a backup of the Security Manager node and its Secure Communicationsconfiguration whenever a new node has been Secured or an already Secured nodehas been Unassigned / removed.

Secure Communication Agent

PAR Description1-3JXC9T1 Error Indication: Secured, redundant Experion Servers with ServerB as primary

and ServerA as backup, ServerA is rebooted and ends up taking over as primary.

Description: This can occur when ServerA is started after reboot. Server A maytimeout waiting for communications with Server B to be established before theIPSec negotiation succeeds, which can be up to 2minutes. ServerA will assume aprimary role, resulting in dual primary Servers. Once the IPsec negotiationsucceeds the Servers will start communicating and Server B will step down to thebackup role knowing that ServerA is the preferred primary.

Recovery: None needed if ServerA in primary role and ServerB in backup role isok. If ServerB needs to be in the primary role, then command a Server swap.

Workaround: Take secured Experion Server pairs out of SecureCommunications before staring critical operations that will cause a reboot, suchas an Experion migration or Windows patch update. After the operation iscompleted, the Experion Sever pair can then be re-secured. From the SecureCommunications user interface, nodes are taken out of Secure Communicationsby Unassigning them from the Secured Nodes list, and nodes are added to SecureCommunications by Securing them from the Unassigned Nodes list.Furthermore, when it is known in advance that the system is expecting to berunning Server B as primary and Server A is likely to have a period where it maynot be able to communicate with Server B, additional action is recommended toensure that when communications are re-established, ServerA will not elevate toa primary role. Follow the instructions documented (associated with PAR1-2TXBDD5) to stop and disable the Experion System service on Server Abefore doing the critical operation, and subsequent restart and enable of theservice after the operation is completed.

1-288O73J Error Indication: C300 remain "updating" in Secure Communications UI;policies are not applied

Description: After un-assigning a Security Manager proxy from the SecureCommunications UI, any nodes communicating with the Security Managerthrough that proxy will no longer receive policy updates.

Recovery: Secure the removed proxy node

Workaround: To prevent this situation do not un-assign proxy nodes or ensureall BOOTP servers point to one proxy node. See the Secure CommunicationsUser Guide for further information.

2 INTRODUCTION


PAR Description1-1XVYCPZ Error Indication: C300 temporarily lose communication with console stations

during policy deployment.

Description: When securing a large number of Windows and C300 nodes atonce, C300 has been observed to temporarily lose communication with consolesstations in the same security zone.

Recovery: Not required, communication restores automatically.

Workaround: Refer to the Secure Communications User Guide for therecommended procedure to secure nodes. In addition, securing nodes in severalparts (for example 10-15 nodes at a time) vs all at once will further increase theprobability of avoiding interruptions in communication.

System Management

PAR Description1-MZ6L8J Error Indication: FTE nodes disjoin and reconnect.

Description: FTE nodes gets disjoined and reconnected when time in NTPsource is slightly modified.

Recovery: None required system automatically recovers.

Workaround: None.

1-MNAFT7 Error Indication: Server data connection is lost

Description: Server lost data connection to System management by launchingthe L2.5 switch display from the station. Issue is caused by slow response fromthe switch.

Recovery: Switch to another display to continue working, and retry the switchdisplay later.

Workaround: None

1-1EYHNCP Error Indication: Missing Managed Component alarm in alarm summary.

Description: Sometimes the MANCOMP is not shown when a network failureoccurs (such as disconnecting one of the FTE cables).

Recovery: Restart System Event Provider.

Workaround: Restart the System Event Provider service (sm-System EventProvider) using Computer Management -> Services.

1-3QHX3Q9 Error Indication: Flex node goes to non-responsive state due to syncrep.exeerrors.

Description: In network and loading conditions, a Flex node may becomeunresponsive. This issue is still being investigated and a more permanent solutionwill be created in a future update.

Recovery: Restart the node.

Workaround: Same as recovery.

2 INTRODUCTION

33

System Repository

PAR Description1-1RTR2H5 Error Indication: CDA disconnects seen when performing "Load with contents"

of a controller.

Description: CDA disconnects were seen when doing "Load with contents" of acontroller having a huge amount of heavy strategies (1000+ RCMs) is done on aheavily loaded setup.

Recovery: Perform switchover of servers to recover from the CDA disconnect ifthe recovery doesn't happen automatically.

Workaround: The workaround to avoid this issue is to download the strategiesunder the controller in smaller chunks instead of doing a "Load with contents"for the controller.

1-3ILK9CN Error Indication: Failed to get the parameter information from SystemRepository for Parameter.

Description: Failed to get the parameter information from System Repository forParameter error for CEE SCADA points on reload after modifying the previousCEE SCADA in Expressions.

Recovery: Close control builder, invoke again and load.

Workaround: None.

1-3RJVPCT Error Indication: CreateTypeDef error message is observed in SystemRepository logs after importing a specific IEC template using IEC61850 IEDDevice Description Import from Control Builder.

Description: CreateTypeDef fails in System Repository database for a templatewhich has name length more than 50 characters. CreateTypeDef error message isseen in SR logs.

Recovery: In such a scenario perform the following steps.

1. Export this type from Control Builder.2. Open the

SIPROTEC5_LNTYPE_PTRC_FN_STR_NONPHSSEL_WITHOUT_DIR.def.xml file in notepad from the exported location.

3. Edit the value ofSIPROTEC5_LNTYPE_PTRC_FN_STR_NONPHSSEL_WITHOUT_DIR toSIPROTEC5_LN _PT, when you name it, ensure that this name is unique inthe type.

4. Save and close theSIPROTEC5_LNTYPE_PTRC_FN_STR_NONPHSSEL_WITHOUT_DIR.def.xml file.

5. Import the types def xml from the exported location using Control Builder.

Workaround: None.

2 INTRODUCTION


Server - other or unknown

PAR Description1-7SSNMCV Error Indication: Default number of addresses for ControlEdge PLC is set to

1000.

Description: Default number of addresses for ControlEdge PLC is set to 1000.

Recovery: None.

Workaround: In an administrative command prompt, run the command "sysbld-preserve" and follow the on screen prompt to change the size of OPC number ofaddresses to the desired number (eg: 3000).

Server - TPS Integration

PAR Description1-452JMJP Error Indication: The message summary in Experion and Native Window may

go out of synch.

Description: If multiple messages are generated on TPS with identicaldescriptions and timestamps, they all are may not be correctly annunciated on theExperion message summary causing a mismatch between Experion and NativeWindow.

Recovery: None.

Workaround: Ensure that all messages that are required to be unique will havedifferent timestamps or descriptions. For example, if the TPS messages aregenerated with CL SEND commands, add a “WAIT 1 SECS” line between eachSEND.

Signon Manager

PAR Description1-43HBRXV Error Indication: After upgrading PCUS to R431.2, the LCN address of PCUS

board 0 and Board 1 becomes 0.

Description: After upgrading the LCN address field in US0 and US1 defaults to0.

Recovery: make a note of the LCN addresses before upgrade and enter the sameafter upgrade the LCN address field.


2.6.2 Engineering Tools/Control

2 INTRODUCTION

35

C300 Controller

PAR Description1-OF7R1R Error Indication: Different communications are observed after powering

up a C300 controller.

Description: Experion embedded nodes when powered up may notproperly detect duplicate IP Addresses. They will attempt to join thenetwork, and this will disrupt communications with the other already-running node(s). However, the FTE Status Display will correctly reportduplicate device index.

Workaround: Keep a record of assigned addresses to avoid duplicates.Verify through the FTE status display that the intended device index is free.

Recovery: change the device index on the newly powered node and reboot/power cycle it.

CEE-Database

PAR Description1-SMAA33 Error Indication: CHECKBOOL.IN[1] parameter does not take input

when written through OPC gateway.

Description: This error occurs when flag block's input in ACE is connectedto a source like flag in C300 controller using OPC gateway.

Recovery: None.

Workaround: None.

1-VPKU61 Error Indication: DP_NUMBER parameter is not visible on monitoringside of ISO_5167_DUAL block.

Description: DP_NUMBER parameter is not visible on monitoring side ofISO_5167_DUAL block. There is no harm to control. InternallyDP_NUMBER parameter takes intended value.

Recovery: None.

Workaround: None.

Control Builder-Fieldbus

PAR Description1-107BU07 Error Indication: EPKS is unable to differentiate the case-sensitive units

like mpa & Mpa, Mg & mg.

Description: Experion displays selected units as Mpa and value is processwith unit mpa. Same is the case with other units which differs with case-sensitive.

Recovery: None.

Workaround: None.

1-1ZQHZDT Error Indication: "Unspecified FMS Initiate" error message is displayedwhile loading CM.

Description: When you try to make Azbil FF device as the Link Master theerror is displayed.

Recovery: Acknowledge the message and try the workaround.

Workaround: Try keeping the FIM or other devices as Link Master.

2 INTRODUCTION


PAR Description1-1ZQHZJN Error Indication: Method Manager application stops responding.

Description: Method Manager stops responding while executing "Test Key2" method of Sensor TB block.

Recovery: Kill the process using windows task manager (or) wait untilerror is generated. Clean the database locks to continue executing othermethods.

Workaround: None.

1-MDH0OZ Error Indication: Cannot use a block from one FF link in a CM on adifferent link (6L.101.10746)

Description: It was observed, CM with FF device function block assignedto FF link is not able to re-assign to any other CEE (like C300 or ACE) ofother controllers. But other way i.e., from C300 to FF link working fine.And CM under FF link is not able to un-assign as well.

Recovery: Acknowledge the error message.

Workaround: Create a new CM in the C300 and re-assign the FF blocks.

1-MW3V5X Error Indication: FFBlock from 1 FFLink can be Used in CM assigned toother FFLink in a specific scenario.

Description: Reassigning the CM (Which is having FF device functionblocks) from c300 to FIM FFLink is allowed. But it must not be allowed.

Recovery: None.

Workaround: None.

1-OYOV8F Error Indication: Replacing FF device with identical FF device fails withthe following error "Device offnet".

Description: The replacement wizard will throw error saying"EXPKS_E_NonExistentDevice (2L .101.3311)3051_1402_P1_7: Devicedoes not exist"

Recovery: Acknowledge the error.

Workaround: Attempt the replacement of the same device once again fromFF device replacement menu, Replacement is succeeded.

1-OYUXXR Error Indication: Device replacement fails saying device not found error(Device off net).

Description: Device replacement fails saying device not found error(Device off net).

Recovery: Acknowledge the error and close the replacement wizard

Workaround: Manually change the device tag and address before devicereplacement/Perform second attempt of the same device replacement.

2 INTRODUCTION

37

PAR Description1-PAAF0B Error Indication: Trying to simultaneously load the same FIM from

different Control Builders may result in Load Failures.

Description: Multiple, simultaneous loads to the same FIM from differentControl Builders impacts the devices on the FIM Links when you attemptto load.

Recovery: Multiple, simultaneous loads to the same FIM from differentControl Builders can have several unexpected side effects, includinginability to load, "device does not exist" error, "parameter not found indatabase error", and device not seen in Control Builder.

Workaround: The best course of action is to attempt an immediate reloadof the failed block from a single Control Builder. There are severalwarnings in both the Experion Standard Operating Procedures Guide whichstates, "Maximum number of clients that can perform controller-relateddatabase operations on the same controller at the same time: 1". Multiple,simultaneous you must avoid loading to the same FIM at the same time.

1-Q322Y2 Error Indication: FF Device delete operation from monitor view fails withDB query execution error.

Description: Deletion of FF devices from Control Builder monitor viewfails in database query execution error and all the devices showed in REDfrom monitor view with error 7005.

Recovery: Close and re-open the Control Builder and reload the devicesfrom project view or force delete the devices from monitor view and loadagain. But, 1st recovery option seems more appropriate to avoid any DBinconsistencies and load the SR to proper state.

Workaround: None.

1-T9A7RI Error Indication: Method execution failure.

Description: Method Execution failure for Function blocks.

Recovery: None.

Workaround: None.

1-T9CEKR Error Indication: Method Execution Aborts.

Description: Method Execution Aborts for method "Test V Item" oftransducer block.

Recovery: None.

Workaround: None.

1-TGJO3P Error Indication: Method Execution Fails.

Description: Method Execution fails with "Built-in error" for some of themethods in TMT 162 Rev2 device

Recovery: None.

Workaround: None.

1-TP28YN Error Indication: "Macrocycle exceeded limit" while try to load the CMwith signal characterizes block of the device.

Description: "Macrocycle exceeded limit"

Recovery: None.

Workaround: None.

2 INTRODUCTION


PAR Description1-TVXKWL Error Indication: Reloading of FF FB having connection with SCM

forcing schedule in monitoring to NO_OPT.

Description: Reload the CM having FF AI function block havingconnection with SCM is forcing the optimized schedule to Non-optimizedin monitoring database.

Recovery: Reload both SCM and CM together, this will bring back theschedule to OPT.

Workaround: Reload both SCM and CM together, this will bring back theschedule to OPT.

1-3E9JFPF Error Indication: Diagnostic Parameter values are not displayed for theirE&H Levelflex FMP5x FF device in Experion Control Builder.

Description: Diagnostic Parameter values are not displayed for their E&HLevel flex FMP5x FF device in Experion Control builder.

Recovery: None.

Workaround: None.

1-TKOXL0 Error Indication: X-Axis range does not change to plot the dynamicvalues.

Description: X-Axis range does not change to plot the dynamic values.

Recovery: Use the Zoom option in the Chart.


Control Builder-Bulk Build/Edit

PAR Description1-11SICGP Error Indication: Control Builder stops responding.

Description: While performing bulk edit operation, Control Builder stopsresponding with Run time error.

Recovery: Close and re-open the Control Builder.

Workaround: None.

1-12Y56T9 Error Indication: Improper warning or failed error messages are observedduring save to ERDB operation of various workflow of Bulk ConfigurationTools.

Description: The error messages like Entry does not Exist, configurationrelated errors are displayed with Failed status even though the save toERDB is successful.

Recovery: Ignore the improper errors with status as failed.


1-3ILPKOZ Error Indication: HART channels are not displayed in the Bulk Edit list.

Description: Hart channels are not displayed in the bulk edit list. Youcannot edit the HART channel parameters.

Recovery: None.

Workaround: Use Bulk Configuration Tools->Bulk Edit work flow.

2 INTRODUCTION

39

PAR Description1-3JZ83JT Error Indication: Display of error message "Runtime Error R6025 - Pure

Virtual Function Call" during Bulk Edit on update Monitor of CHANNUM.

Description: The error is displayed due to an internal error that is causingthe issue. This issue is not reproducible on demand.

Recovery: Retry Bulk Edit.

Workaround: None.

1-3NHR0K1 Error Indication: "Save to ERDB failed error is displayed.

Description: If you do not specify the new channel names for the ReplicaIOM in the configuration sheet, the existing channels in Typical IOM ismoved to the replica IOM.

Recovery: Reassign the channels to Typcial IOM using Bulk Edit.

Workaround: Provide new channel names in the configuration sheet sothat the new channels are created and assigned to new IOM.

Control Builder-Configuration Form

PAR Description1-3QDACAH Error Indication: During the migration of Quick Builder project from

R430 to R431, the migration wizard gives a warning about unresolvedproperty (Auxiliary) for EFM. This property is not used in R431 release.

Description: Refer to the Error Indication.

Recovery: None.

Workaround: None.

1-12RNGG1 Error Indication: When you perform controller migration you will be ableto close the Configuration Studio.

Description: While performing Migration of Controllers, closing ofconfiguration must be restricted. Closing of Configuration studio whileperforming migration of controller leads to incomplete migration ofControllers.

Recovery: None.

Workaround: You must not close the Configuration studio during themigration of Controller.

1-1A4KN3Z Error Indication: Two different IO channels of same IO module showsame IO channel number and Control Builder stops responding whileassigning these channels.

Description: Two different IO channels of same IO module may showsame IO channel number during Series C IO channel assignment afterrelated strategies are imported from release R410.1 or prior. In addition,one of the channels may still hold the last assign channel block name eventhough it already unassigned. Control Builder may also stops respondingwhen these channels are assigned.

Recovery: Un-assign the channel from CM and delete the channels andIOM. After that re-configure new IOM and assign the channels in CM.

Workaround: None.

2 INTRODUCTION


PAR Description1-1T9HS0S Error Indication: No Units are showing for Bearing PV in the Control

Builder.

Description: Wireless Vibration Transmitter has a vendor provided unitsfor Bearing PV which are not shown/supported in the Control Builder.

Recovery: None.

Workaround: For you to check the ZFS user interface understand theconfigured unit for Bearing PV.

1-3IK19PU Error Indication: Redundant FTEB is not created and redundancyfunctionality is not available for imported FTEB.

Description: When a non redundant FTEB is created and is attempted toconvert to redundant then secondary FTEN is not created. Also redundancyfunctionality is not available for imported FTEB. Assigning C200Eredundant module to FTEB sometimes creates the secondary controller asunassigned.

Recovery: Create a new FTEB module as redundant instead of creating itas non redundant and then converting it to redundant.

Workaround: Create a new FTEB module as redundant.

1-RZZXUB Error Indication: Maintenance Mode change is not reflected back inST800 DTM in FDM, when the change is done while the DTMconfiguration is open.

Description: From Control builder for ST800 device, if the channel'sparameter 'PVSOURCE' is changed from AUTO to MAN, the displayshows 'Available for Maintenance'. Again change from MAN to AUTO, thedisplay removes the 'Available for Maintenance'. This is not updated inDTM configuration form when you do the operation while DTM screen isin open state in FDM.

Recovery: None.

Workaround: Before performing the required PVSOURCE change inControl Builder, close the corresponding ST800 DTM in FDM. Once thedesired change is done, then re-launch the DTM in FDM to view thechange in Maintenance Mode.

1-UPBZT1 Error Indication: When entering base IP address with lowest octet otherthan multiple of 10, then the address is replaced with lowest octet asmultiple of 10 and throws error message 12613.

Description: While entering the base IP address 10.66.51.128, CB isthrowing error message 12613 and the address is directly replaced by10.66.51.130.

Recovery: Change the base IP address with lowest octet of multiple of 10.

Workaround: Configure the base IP address with lowest octet as multipleof 10.

1-W92HO6 Error Indication: Local UDP Listeners have only 4 entries for C300 andother FTE nodes.

Description: For C300 and other FTE node types, on its form, navigate to"UDP/TCP" tab. You will see that for "Local UDP Listeners", there areONLY 4 entries. In C300, there are more than 4 that may be used. It is notpossible to see all of them in Configuration form.

Recovery: None.

Workaround: None.

2 INTRODUCTION

41

PAR Description1-Z3FUD5 Error Indication: Assigning control modules with particular CDB blocks

to ACE/C300 failing.

Description: After importing specific CDB blocks and trying to assign thecontrol module to C300/ACE it fails to assign and shows CDB notcompatible with execution environment.

Recovery: Since this happens only for particular CDB blocks, the belowcompatible platforms must be added in CDB def xml file and then it can beimported.

<CompatiblePlatform>C200</

CompatiblePlatform><CompatiblePlatform>C300</

CompatiblePlatform><CompatiblePlatform>SCE</

CompatiblePlatform><CompatiblePlatform>C200E</

CompatiblePlatform>

Workaround: Add the below lines in exported CDB Block's def xml fileand then import it. It will then allow control module to be assigned toC300.

<CompatiblePlatform>C200</

CompatiblePlatform><CompatiblePlatform>C300</

CompatiblePlatform><CompatiblePlatform>SCE</

CompatiblePlatform><CompatiblePlatform>C200E</

CompatiblePlatform>

Control Builder-Batch

PAR Description1-13BFFO7 Error Indication: Proxy CBR is not listed after the validation of Proxy

CBR. You cannot configure it manually.

Description: If you create and validate new Proxy CBR in local cluster (forNewly created CBR in remote cluster), the Proxy CBR does not list in Unitfunction reference point picker and it is not validated manually as well.

Recovery: Delete the proxy CBR from Control Builder and re create theproxy CBR.


1-WJV6I5 Error Indication: An orphan activity will be created in the orphan activitysummary display.

Description: After Terminal Stop command given to PROC layer Activityand it finishes, UPROC layer Child activity is listed under orphan activitysummary. CEE and UPROC MR show activity associated with them too.

Recovery: Remove the orphan activity from the orphan activity summarydisplay. This will resolve the issue.

Workaround: None.

2 INTRODUCTION


PAR Description1-XFDMT9 Error Indication: No error displayed, The default value of new parameter

added in the phase block is not displayed in datablock.

Description: In Datablock default value is not populated for the newlyadded parameter for a phase block.

Recovery: Open the PDE of phase block and deselect the Use Valuereference option and save the Phase block. and then open the Datablock ofrecipe. Observe that default value is displayed for newly added parameter,then open the phase block in PDE, select the "Use value reference" optionand save the PDE

Workaround: None.

1-ZESYD7 Error Indication: Reverse video observed in Child RCM and Child SCMdetail display during ICPP runtime.

Description: It is observed that Parent navigation option does not existafter navigating to Child detail display

Recovery: Go back to parent detail display through back button in Stationtool bar.

Workaround: None.

Control Builder-Load/Upload/Update

PAR Description1-13TQQLP Error Indication: "Out Of memory pop up or Last minute catch of

unexpected exception in error logs is generated.

Description: Last minute catch of unexpected exception is displayed due toexcessive memory usage when lot of bulk database operations have beendone without closing Control Builder.

Recovery: Manually close Control Builder.exe via the Task Manager.

Workaround: Close and open Control Builder, then try to load thestrategies.

1-1RT7EKD Error Indication: SQLServer.exe consumes lot of CPU time onperforming Load With contents.

Description: If the number of strategies loaded exceeds the DFS spec, theload dialog could become unresponsive for a prolonged time.

Recovery: Cancel the load and perform the load operation by selecting thestrategies in small numbers.

Workaround: Perform the load operation by selecting the strategies insmall numbers.

1-3EG37WV Error Indication: Error "Comm Path is not set up for secondary C300Controller" displayed during load.

Description: This error occurs during the load of redundant C300controller, but occurs occasionally.

Recovery: None.

Workaround: Uncheck and check the "Module is redundant" option inC300 main configuration form and try reloading.

2 INTRODUCTION

43

PAR Description1-3J99M63 Error Indication: Mismatch between QVCS version number and mismatch

in configurations on the IO Module between the project and monitoringside.

Description: Revert to version & load of IOM is updating the version only.But content remains same on monitoring.

Recovery: This can be recovered either by making the configurationchanges of the IOM in project side to match with monitoring side and thenreload the IOM. Or Delete the configuration changes which are differentfrom project side IOM i.e., (by deleting the channel blocks from monitoringside) and then reload the IOM.

Workaround: Do Not revert QVCS version of IOM when there isconfiguration mismatch between project and monitoring.

1-3M63XJF Error Indication: Checkpoint restore operations failed entries in theControl builder error log for specific IOM.

Description: Dataflow stops if checkpoint restore for specific IOM fails.The checkpoint restore for specific IOM fails occasionally.

Recovery: This can be recovered by Reloading the corresponding Outputchannels or Reload the CM's Containing or referring channels.

Workaround: None.

1-SJ4W66 Error Indication: C300 synchronization fails.

Description: After loading a CM containing DO channels connected toDEVCTL blocks, synchronization breaks between C300s when the IOMcontaining the loaded DO channels does not exist.

Recovery: The C300 Synchronization will restart automatically andcomplete successfully.

Workaround: To prevent this situation, do not load a CM containing DOchannels connected to DEVCTL blocks unless the IOM is present.

1-TNX8CL Error Indication: Control Builder stops responding on trying to re-load astrategy with dangling connection.

Description: Control Builder stops responding if a Control Module withdangling connection is loaded.

Recovery: None.

Workaround: Open the Control Module containing dangling connectionand delete the dangling connection in Control Module. Reload the ControlModule.

1-3E4HHLP Error Indication: Controller will inactivate and re-activate CMs.

Description: During load of controllers having same device index acrossclusters are loaded, it leads to the loaded controller inactivating andreactivating the CMs in the other cluster.

Recovery: The Controller recovers automatically.

Workaround: Ensure same device index is not used across clusters for thecontrollers.

2 INTRODUCTION


Control Builder-Profibus

PAR Description1-16JFE8J Error Indication: You are able to delete the first item from any grouped

modules when there is a DSB associated with that NETTAG.

Description: It must give an error popup message (for example, "You havemade a change to I/O definitions that has PDC references in the ControlApplication.") when you try to remove an item from the grouped moduleswhen there are PDC references. Currently it allows to remove the first itemfrom the group where as it works as intended when deleting other modulesthan the first one.

Recovery: Re-configure the modules

Workaround: Re-configure the modules

Control Builder-Delete

PAR Description1-1A27Z5V Error Indication: Cannot force delete the offline device from monitoring

tree

Description: Unable to delete OW Adapter device from CB treemonitoring when the device is in offline state. 'Force Delete' option doesnot appear for OW Adapter device which is in offline state.

Recovery: Check if device is powered off or run out of battery.

Workaround: None.

Control Builder-Chart

PAR Description1-3QFNDMJ Error Indication: Station number in Flex Station configuration page

reverts to 1 when switching between tabs.

Description: When an operator browses between the 3 tabs "General,Assignment and operator keyboard " in flex station configuration window,it is observed that the station number jumps to station 1.

Recovery: None.

Workaround: Manually change the station number by entering the stationnumber. or update station number by using Page up/Page down key andproceed with further configuration.

1-1A58B5B Error Indication: IOP details are missing for PMIO channels.

Description: After assigning unassigned channels multiple times in CMLoaded C200 with IOLIM and PMIO shows IOP details are missing on theassigned channels.

Recovery: None.

Workaround: None.

2 INTRODUCTION

45

PAR Description1-1P915L9 Error Indication: After adding a phase block with function reference into a

Master Recipe chart, saving the Master Recipe, closing and opening theMaster Recipe again sometimes crashes Control Builder.

Description: After adding a phase block with function reference into aMaster Recipe chart, saving the Master Recipe, closing and opening theMaster Recipe again sometimes crashes Control Builder. Opening ControlBuilder again and opening the same Master Recipe chart will work.

Recovery: Open Control Builder again and open the Master Recipe chartagain.

Workaround: None.

1-Q2XSJX Error Indication: Detail Displays (Charts) take 10 to 20 seconds to invokefrom station during normal run.

Description: Chart Visualization Displays in Point Detail Displayssometime takes 10-20 seconds to come up. It is more often with chartscontaining large number of UDTs.

Recovery: None.

Workaround: Open the monitoring side charts from Control Builder forthe same point to view the details.

1-3L4KQ9D Error Indication: In certain scenarios REF parameter defaults to UDTtemplate name.

Description: Manual configuration of REF parameter.

Recovery: Re-enter correct REF value.

Workaround: Use Point Picker to enter REF value rather than typingmanually.

1-45MIXBX Description: If you open a considerably large CM after Completion ofMigration it will take approximately 10 to 15 seconds to open, ControlBuilder is going to Not responding state for some time.

Recovery: None.

Workaround: None.

1-485382C Error Indication: Undesired behavior is detected in the form of wire re-routing and re-alignment which may cause additional time for you to fixmanually.

Description: When you add the first input pin to a block (top/left) orremove the last input pin (top/left), the system should automatically adjustthe position of the function block faceplate so undesired wire re-routingoccurs. This works properly under most scenarios, except when the functionblock is located in an instance of a User Defined Template for a ControlModule. In this case, the logic fails to do the proper job.

Recovery: You need to move affected function block to the desired placeand/or realign the wire appropriately.

Workaround: None.

2 INTRODUCTION


Control Builder-Change Parent/User Defined Template

PAR Description1-1PQWSTZ Error Indication: Duplicate Phase/Map block created due to change parent

operation when validate operation is used again.

Description: Change Parent operation for phase block creates duplicatecopy in the chart.

Recovery: Delete the duplicate phase block.

Workaround: If you want to use the validate operation again, close theexisting change parent dialog and invoke again, validate and performoperation.

1-3Q0K7WY Error Indication: On performing Change Parent(CP) of UDTCM1 to bethe child of UDTCM2 both configured with old style channels AIChannel->PID->AOchannel blocks, CP fails with unexpected error in case there is aninstance for the UDTCM1 and if there is no instance, then shows error"Existing background connection exists...".

Description: Doing a change parent operation between two UDTscontaining Channel blocks throws an error.

Recovery: None.

Workaround: None.

Control Builder-HART

PAR Description1-3ILPL1F Error Indication: An issue is observed in listing Smart Channels in

Synchronize Maintenance Mode dialog.

Description: When you log in through local Engineer account, SynchronizeMaintenance Mode dialog does not list Smart Channels and clicking on thedialog throws exception.

Recovery: Close the Control Builder and open Synchronize MaintenanceMode dialog from Administrator account.

Workaround: Open Synchronize Maintenance Mode dialog fromAdministrator account.

1-3IW5W4I Error Indication: Synchronize operation in Synchronize MaintenanceMode dialog fails.

Description: When IOM switchover is in progress, Synchronize operationof Maintenance Mode dialog is failing.

Recovery: Close the Maintenance Mode dialog, wait for IOM switchover tocomplete, then Open Maintenance Mode dialog and do Synchronize.

Workaround: Perform Synchronize operation in Maintenance mode dialogonce IOM switchover completes.

1-3LZALJS Error Indication: Enabling of "Enable Auto Detection" feature throws"Configuration mismatch" error.

Description: After loading HART IO channels, Enabling of "Enable AutoDetection" checkbox from HART Status tab of IOM Properties frommonitoring side throws Enabling of "Enable Auto Detection" error message.

Recovery: Close the error message and proceed.

Workaround: None.

2 INTRODUCTION

47

PAR Description1-SHYPIT Error Indication: FF and Hart DD import function do not working with

Engineer login.

Description: It is observed that FF and Hart DD import does not work withEngineer login. If you click on DD import icon it displays the followingerror Failed to read FF attributes SQL database from server.

Recovery: Close the error message and try to open DD Manager usingProduct Administrator access account.

Workaround: Logon to the machine using Product Administrator accountprivileges and open HART DD manager from the path Honeywell ExperionPKS-> Engineering Tools-> Device Description Manager.

Using the same Product Administrator access account open Control Builderand click on the icon, Fieldbus Device Description Import.

Control Builder

PAR Description1-G3WCZ1 Error Indication: When attempting to enable/disable FF maintenance

alarms from chart tabs in Station- checkbox values may not change unlessyou change the tabs and return. Some bit checkboxes may fail to getenabled.

Description: Same as error indication.

Recovery: Same as workaround.

Workaround: Open the equivalent tab in Control Builder monitoring sideand enable/disable maintenance alarms there.

1-I3GBVR Error Indication: When system was idle for hours after opening CM inConsole, stops Responding Control Builder.

Description: Chart View of control builder is opened for 10 CM's inconsole with 3 GB RAM. Keeping system idle for three hours crashescontrol builder automatically. System was in base load with cycles scriptsrunning.

Recovery: None.

Workaround: None.

1-LH4MXJ Error Indication: While importing the database (corrupted) having phaseblock without library name, it throws error while importing.

Description: While importing the database (corrupted) having phase blockwithout library name, it throws error while importing, a phase block withempty library name is created in database.

Recovery: Contact TAC team to get the script to fix this issue for theparticular build.

Workaround: Run ECC before migration, if any phase block withoutlibrary name is present in the database is listed out. - contact TAC team toget the script to fix this issue for the particular build.

2 INTRODUCTION


PAR Description1-O3WK4X Error Indication: The Remote Shed option "Normal Shed, No Return"

option does not work in Cerabar_S 05 Rev.

Description: The Remote Shed Option "Normal Shed, No Return" of PIDBlock of E&H Cerabar_S Rev 05 sheds to Actual Mode "AUTO" andTarget Mode "AUTO" when the intended behavior is Actual Mode "CAS"and Target Mode "CAS". The normal Mode "CAS" is selected. Actuallywhen this option is selected, in case of a failure of remote input (RCAS_Inor ROUT_In) the next lower priority Non-remote mode must be selected astarget than the actual mode.

Recovery: None.

Workaround: None.

1-PJDOPP Error Indication: In CB/RB while generating report (Paginated Text) forSCM/RCM with a same name (an existing report name) an error isgenerated "Crystal Reporting Export: File I/O error".

Description: In B/RCM while generating a report (paginated Text format)for RCM/SCM/MR with a same name (already on report with a file nameexist in same path). It generates an error "Crystal Reporting Export: File I/Oerror"

Recovery: NONE

Workaround: You can provide a different file name for the reportgenerated while saving or you can change a directory path for the given filename. This issue can be avoided by giving a new file name or changing thedirectory path of the report.

1-PM89OX Error Indication: PVSOURCE option is not grayed out in PA channelinstances even though all options including PVSOURCE parameter isdefined in PA channel template.

Description: PVSOURCE option is not grayed out in PA channel instanceseven though all options including PVSOURCE parameter is defined in PAchannel template.

Recovery: None.

Workaround: None.

1-QLJ7FD Error Indication: Few methods are not working in Magnetrol TA2 Rev1 inR400.2 TB

Description: Following Methods are not working for Transducer Block(a)Zero Power Test.(b) Low Cal Validation.(c) High Cal Validation. Themethod will keep on running endlessly in the Experion host with no results.

Recovery: None.

Workaround: None.

1-RDTD13 Error Indication: Method manager fails to execute the methods.

Description: Method manager fails to execute the methods.

Recovery: None.

Workaround: None.

2 INTRODUCTION

49

Control Builder-Load

PAR Description1-KKLCSZ Error Indication: Reload of a loaded C200E causes "unexpected error" to

be shown.

Description: During the load of C200E this error is shown occasionally.

Recovery: Close the error dialog and reload.

Workaround: None.

Control Builder-System Repository

PAR Description1-PV3SMT Error Indication: Peer-to-peer communication between CEE controller and

Experion Server points (SCADA, DSA, TPS, OPC, OPC Advanced point)fails with NaN values.

Description: If a server with incomplete information in System Repository(System Repository sync state can be observed from Server Redundancypage) takes over the Primary role then, there is a high likelihood to loseExperion Server points information in System Repository resulting in peer-to-peer communication failures between CEE controller and ExperionServer points.

Recovery: None.

Workaround: None.

1-Y390VS Error Indication: When QCS subsystem tries to validate points in Serverthrough SR at a high rate, failures are seen.

Description: When QCS subsystem tries to validate points in Serverthrough SR at a high rate, failures are seen.

Recovery: Do a Stop and Start of Experion Server from "Start-StopExperion PKS Server" tool to recover.

Workaround: None. Lowering the number of non CEE point handlerequests to SR per second would avoid this.

Control Builder-Assign

PAR Description1-TETYQT Error Indication: Control Builder stops responding when the Print Preview

option is selected.

Description: In case you double click the FFLINK in Control Builder, themacro cycle schedule becomes visible. Later when you select the PrintPreview option the Control Builder stops responding.

Recovery: None.

Workaround: None.

2 INTRODUCTION


Control Builder-Search

PAR Description1-UXS811 Error Indication: Display of error message "Search will be aborted due to

server connection timeout error" during simultaneous execution of WhereUsed Search and Online Data Search from Configuration Studio on thePrimary server.

Description: The error is displayed since the services "Experion PKSBrowser Orchestration" and "Experion PKS Browser Support Service" arestopped in the Primary server on which the search is executed.

Recovery: Restart the services "Experion PKS Browser Orchestration" and"Experion PKS Browser Support Service" on the Primary server.

Workaround: None.

Control Kernel

PAR Description1-XGHDCZ Error Indication: An alarm generated from CAB function block may

appear active in Station, though it is in normal condition. This can be crossverified by monitoring faceplate of the CAB function block.

Description: If an active alarm generated by CAB function block is returnedto normal condition while C300 switchover is in progress; there ispossibility that this particular alarm still appears as active in station.

Recovery: Toggle ALMENBSTATE parameter of CM containing CABfunction block. This will trigger a re-notification of alarm state to station.

Workaround: None.

EIP-COMMUNICATION

PAR Description1-11RAB1P Error Indication: 3 to 5 seconds delay in establishing connection to the

EIP IO's on reloading the EIP IO's from monitoring side.

Description: This delay is not easily visible, and happens only if there issome EIP IO on the monitoring side which is not powered up or not presenton the network.

Recovery: Automatically recovers.

Workaround: None.

Embedded Controller/Gateway Platform

PAR Description1-2ED9BQB Error Indication: Loss of communication with Ethernet/IP device.

Description: Any break in the communication path to a singly-attacheddevice may take up to a minute for FTE to resolve, if there is an alternativepath.

Recovery: An alternative path is resolved and the connection is restoredafter a minute.

Workaround: None.

2 INTRODUCTION

51

Enterprise Model Builder

PAR Description1-BBESLV Error Indication: Assets can be downloaded to Server by you without

having engineer access.

Description: Same user name has been used to create user accounts on twodifferent servers. The privileges provided to you is different in both servers.In one Server ( Server1) you have Engineer privilege whereas in the otherserver (Server2) you do not have Engineer privilege. Adding both Servers tothe system of Server1, the system model or assets model can be downloadedto both the servers.

Recovery: Ensure that the user accounts having the same user names indifferent servers have the same privileges.

Workaround: None.

1-J3B3SH Error Indication: In a dual primary scenario while migrating from R400.1to R410.1 release, the Assets or Alarm Groups configuration builderlaunched from ServerA indicated that the connection is made to the primaryserver. The OPM status is indicated in the status bar. However instead ofindicating secondary server the status bar shows that the connection hasbeen made to the primary server.

Description: In a dual primary scenario while launching the Assets orAlarm Groups Builder, it is expected that the status bar on the right bottomcorner must indicate OPM and Secondary Server connection status. In thisscenario you see a primary server connection indicated on the status bar. Inthis scenario, the configuration change is not allowed at this time as theOPM status is enabled. This is a cosmetic anomaly and you can ignore theindication on the status bar.

Recovery: None.

Workaround: None.

EBM-Controller

PAR Description1-NDXIBN Error Indication: Loss of inter-community peer-peer communications.

Description: Powering down the top-level yellow switch disruptscommunications through the level 2.5 router.

Recovery: Correct network condition.

Workaround: None.

1-NW1WPL Error Indication: No error is displayed to the user. An RCM starts runninglike it has acquired equipment properly when in fact it hasn't.

Description: An RCM is configured to acquire a UCM. The RCM is startedand acquires the UCM. The UCM is inactivated and deleted. The RCM isaborted, inactivated, activated, and started. The RCM does not try to acquirethe UCM again before it starts. In this case it cannot acquire it because theUCM was deleted.

Recovery: None.

Workaround: Once the RCM is inactivated, reload it before you activate itagain.

2 INTRODUCTION


PAR Description1-PK1QJ5 Error Indication: After performing freeze and switchover , when a new

activity is created and started, it is struck in Acquiring Resource in Pre-ExecState.

Description: When an OPM is performed on a controller having an MRwith multiple CR's running, the old CR's get removed as expected but afterOPM newly created Activities are not executing, they are struck in Pre-Execstate with Acquiring Resource as Info.

Recovery: None.

Workaround: Remove the CR. Inactivate and Activate the MR then Createa new CR.

1-3QM82LT Error Indication: A step block displays an error of 2447 when trying to seta unit.

Description: You are unable to select a unit.

Recovery: Abort the strategy.

Workaround: None.

1-LU37LJ Error Indication: You may observe that some activities you thought youcreated do not show up in the activity summary display. The same activitydetail display may update from multiple activities which may causeincorrect to be presented.

Description: Scenario:-

RCM_1 is running and it is acquired (either by another recipe or anactivity).

RCM_2 is trying to acquire RCM_1 (RCM_2 is in RCM_1s arbitrationqueue, or listed as an un managed conflict). Idle->Cold start the controller.

Command RCM_1 to start. RCM_1 will reuse its Activity ID.

Recovery: There are no user steps for recovery. Once RCM_1 is run asecond time after the cold start, the problem will correct itself.

Workaround: Do not idle the controller when RCMs/SCMs are not in aterminal state. i.e., Do not idle the controller when RCMs are in the runningstate.

EBM-Tools

PAR Description1-NS6M1L Error Indication: Load operation fails to load or does not give any error for

the updated range values of formula parameters in Data block/phase block.

Description: Loading of an RCM configured with the phase block havinginvalid range values for its parameters does not give any errors and theupdated values are not reflected on monitoring side.

Recovery: None.

Workaround: None.

2 INTRODUCTION

53

PAR Description1-O0GF6A Error Indication: Key parameters in Table view display.

Description: When batch is executing across clusters such as parent andchild are in different clusters, the key parameter in table view of the parentrecipe that display child recipe key information could display.

Recovery: N/A.

Workaround: You must click the blank area which is right above keyparameters. This allows you to navigate to the child recipe detail Displaywhich displays all the information of the child recipe including the keyinformation.

1-PADH2J Error Indication: Running SCM after CP Save/ Restore after LWA of Aliasmay result in harmful effect.

Description : When LWA is performed for SCM/RCM in active state and ithas changes to selected instances in alias table, then selected instances arenot loaded but the values in checkpoint are updated. CP save and restoreafter that may point to the new values.

Recovery: For such scenario, when LWA is performed for SCM/RCM inactive state and it has changes to selected instances in alias table, performCheckpoint Rebuild after LWA

Workaround: After CP rebuild, CP save and restore works properly.

1-UMLIDH Error Indication: Proxy blocks are not listed from different release servers.

Description: ICP2P is not supported on two different releases duringconfiguration time due to GCL connection limitation.

Recovery: None.

Workaround: None.

1-VIAD8V Error Indication: The number of activities shown in CEE statics Tab isdifferent from the number of activities shown in Batch tab of CEE.

Description: The NUMACT value as seen in the Batch Tab of the CEEshows a mismatch with the CEE-Activity Statistics -TOTALACTCAP.

Recovery: Reload the ACE node in server.

Workaround: Same as Recovery.

1-ZX2IMV Error Indication: C300 controller and FTEB CPUFREE goes down by7%-8% when UT is running

Description: C300 controller and FTEB CPUFREE goes down by 7%-8%when UT is running. This issue is observed for all C300 controller andFTEBs when executing Readiness Check of the controllers/chassis.

Recovery: None.

Workaround: None.

2 INTRODUCTION


Fieldbus Library Manager

PAR Description1-OMCM9H Error Indication: "Store Echo curve of the Setup" method fails to execute

for Vegapuls FF device.

Description: "Store Echo curve of the Setup" method fails to execute forthe following Vegapuls Rev 6 Devices and crashes Methods manager.1)Vegapuls 612) Vegapuls 623) Vegapuls 634) Vegapuls 655) Vegapuls 666)Vegapuls 677) Vegapuls 688) Vegapuls SR 689) Vegapuls WL 68

Recovery: Clear the ERDB lock and Invoke the Methods manager againand do not execute "Store Echo curve of the Setup" method.

Workaround: None.

1-Q407YH Error Indication: Scroll bar is not available & Get string value built-inmethod is not supported.

Description: In Method manager, for drop down menu if menu more ofoption then user has to use scroll bar to scroll down or up, but scroll bar isnot available and Get string value built-in method, Experion in unable toread the parameter.

Recovery: None.

Workaround: None.

1-R3X0ZN Error Indication: Flow Units and User Units of the Transducer blockdisplays unit as "Kbytes".

Description: Which is "Kbytes" for "1599".

Recovery: None.

Workaround: None.

Fieldbus Interface Module

PAR Description1-PAPV2D Error Indication: Changing the address or TAG for Uncommissioned

device is resulting in inconsistent behavior.

Description: Changing the TAG name and address for twouncommissioned devices with same TAG name and temp address isshowing inconsistent behavior as devices end up with same TAG name andaddress.

Recovery: Following steps were followed to recover the state:

1. Remove one of the problematic device.2. Configure and reload the other device.3. Then connect the first device and reload it.

Workaround: This issue is observed following issues with other operation.After following steps to recovery, it is not observed.

2 INTRODUCTION

55

Fieldbus Interface Module-Series C

PAR Description1-Y3T5WR Error Indication: Some ST800 Resource block parameters not updating in

FDM.

Description: Some Resource block parameters on the ST800, includingSimulation Active and Write Lock, will not reflect updates in FDM if thevalue changes on the device. If the DTM on FDM is connected to theDevice then these parameters will also not appear to update in the ControlBuilder block configuration pages.

Recovery: Values update correctly in Control Builder if the DTM is notconnected to the Fieldbus device. Close the DTM on the FDM and monitorstatic parameters through Control Builder configuration forms only.

Workaround: When enabling Simulation or changing Write Lock of theST800, close the DTM on the FDM and verify the changes to theseparameters through the Control Builder block properties page.

1-3QIZ2V1 Error Indication: During FIM4 failover test of15 FIM4s, 5 FIM4s stopsresponding with the following error 0x03B3. Some FIM4s fail after 30failovers and 2 fail after 100 failovers.

Description: Fieldbus stack stops responding, FB_FS 0x0002-C 0x00-T0xCF-M 166-L 0x0000-C 0x00D1-D with some kind of time out onfieldbus operation. This may lead to control shed.

Recovery: Restart the affected module.

Workaround: None.

IEC61850_Embedded

PAR Description1-3KPXXJX Error Indication: After the first read request error 6520-6530 is displayed.

Description: The provided SCL file does not match the IED.

Recovery: The Physical device must be unloaded and the correct CID filemust be loaded.

Workaround: None.

1-3OZ2O8L Error Indication: IIM lose communication with various IEDs for 6seconds during stability run.

Description: Data takes longer than 6 seconds to refresh, due to somenetwork issue.

Recovery: 850M recovers on its own.

Workaround: None.

1-3OGBUW7 Error Indication: Secondary 850M fails with error 0x00d2 while reloadingmultiple IEDs (more than 13 IEDs at once).

Description: While reloading multiple IEDs from project view aftermaking changes, sometimes, 850M secondary fails with error 0x00d2. Thisfailure is observed only when you reload multiple devices in a single loadoperation and is not observed during single device reload. Reloadingmultiple IEDs at once results in improper stack fragmenting which may bea major contributing factor to this failure.

Recovery: Reboot the failed 850M module.

Workaround: Reduce the number of IED devices getting loaded in a singleload operation or maintain more than 4.0 mb driver reserved free memoryof 850M.

2 INTRODUCTION


PAR Description1-3QY3645 Error Indication: In extremely high network traffic (100% bandwidth)

IEDs disconnect from the network and do not rejoin. The result ispermanent loss of communication to the IED.

Description: In extremely high network traffic (100% bandwidth) IEDsdisconnect from the network and do not rejoin. The result is permanent lossof communication to the IED.

Recovery: Perform a switchover.

Workaround: Restart the IEDs or restart the controller.

1-3FDCPMY Error Indication: Import and Export of IEC-870 points functionality is notworking as expected.


Recovery: None.

Workaround: None.

Profibus Interface Modules

PAR Description1-1WK0AHV Error Indication: During PGM Switchover if a channel goes BAD then all

the channels in the grouped PDC will go BAD.

Description: Upon PGM switchover, just after the secondary takes over therole of Primary and the new secondary is still coming up, at that time if achannel goes bad, then all the channels in that PDC become BAD.

Recovery: Perform PGM Switchover.

Workaround: None.

1-3HBNUST Error Indication: After loading link1 master shows as offline with numberof configured slaves as zero. Connecting to PGM master in SYCON, errormessage in link1 shows Timeout while resetting Profibus.

Description: This is observed in testbed with 125 slaves configured oneach link with lots of simulated slaves. Happens only during load so notvery critical.

Recovery: Reboot PGM2. Switchover PGM in case of redundant PGM. Innon redundant case reboot PGM and load.

Workaround: None.

1-3NEJNEZ Error Indication: Negative enumeration values larger than ENUM64supported by IEC61850 are not read by Control Builder.

Description: TYPECONVERT, PUSH and other blocks only supportenumerations from 0 - 63.

Recovery: None.

Workaround: You must use SCM steps and transitions to read these valuesor cab blocks.

2 INTRODUCTION

57

IXP-Import Export

PAR Description1-3YLHQMA Error Indication: "Template name not found" error while importing CM

and template at once.

Description: Same as Error Indication.

Recovery: Delete the imported CM and Library.

Workaround: Close and reopen the Control Builder session. Performimport operation again.

1-1L2XTPG Error Indication: Error appears as "An unexpected error was encountered"in QVCS window.

Description: This issue appears in ERDBs migrated from releases beforeR310.2, with strategies having duplicate FF IO channel names, which arechecked in QVCS. When you do a revert operation for the channel or CMfrom a newer QVCS version to older version, then error appears as 'Anunexpected error was encountered" in QVCS window.

Recovery: Acknowledge the error. Keep the strategy or IO Channel in thesource QVCS version itself.

Workaround: Delete the strategy from monitoring side, re-configure toolder QVCS version.

1-28C3M4F Error Indication: After DD import(FF\wireless) QVCS checked instrategies are editable.

Description : Checked in Control modules (having reference to FF blocks)become editable after performing dd import of the same FF device.

Recovery : Close and reopen Control Builder.

Workaround : Close and reopen Control Builder.

1-3IWH9K7 Error Indication: Problem is observed after import of CM usingIXPTOOL.exe, block connections are missing.

Description: Export a CM using IXPTOOL.exe.Export is successful. Afterthe Export delete the CM in Control Builder. Import the exported CM usingIXPTOOL. Import is successful but when the chart is opened the pinconnections in the CM is lost.

Recovery: Import using Control Builder.

Workaround: Import using Control Builder.

1-VM137H Error Indication: Error appears as "Entry does not exist[EXPKS_E_CL_ENTNOTEXIST (4L .101.10020)].

Description: When we have a tagged basic block which is an embeddedchild in a CM (for example, HART AO BLOCK with Hart enabled,embedded and assigned in a CM), importing another CM with an assignedHART AO with the same name fails and connection to the HART AOBlock is lost in imported strategy. Error appears as the import failed andthere is a name conflict for child blocks.

Recovery: Acknowledge the error. Re-configure the imported strategy withnon-conflicting IO channel name and assignment.

Workaround: Ensure that there are no name conflicts within child blocks.Need to check the IO Channel names in CMs, correct it before import ifpossible.

2 INTRODUCTION


PAR Description1-WQUL43 Error Indication: Error appears with error code

"EXPKS_E_IXP_EXPORTBLOCKTYPEFAILED (4L .101.14231)" onExporting HART template.

Description :HART IO templates failed to export with an error code onExporting HART template.

Recovery: Acknowledge the error by clicking OK.

Workaround : Close the control builder and reopen once the importoperation is completed.

1-3IAI1H5 Error Indication: PID connected to Series-A AI or AO sheds Mode onswitchover.

Description :If the following actions occur while using the topology of aC300 controlling Series-A I/O through an FTE Bridge module in the I/Ochassis and if a Serial Interface Module resides in the same chassis as otherSeries-A I/O Modules: 1) Multiple Serial Interface I/O module blocks areconfigured to map to the same physical Serial Interface Module in the I/Ochassis by using the same FTE Bridge Name and IOM Slot Number. 2)Both Serial Interface I/O module blocks are loaded to the C3003. Aswitchover is performed. Then on switchover there may be a momentarilyloss of communication between the C300 and other Series-A I/O moduleswhich reside in the same chassis as the FTE Bridge and Serial InterfaceModule. If a PID block is providing a process value to the Series-A I/Ochannel this loss of communication may be observed by the Mode of thePID block shedding to Manual. No warning or error is raised during theconfiguration or load operation of the Serial Interface Module blocks.

Recovery: Perform all of the following steps:

1. Delete all Control Modules containing Serial Array Channels assignedto both of the Serial Interface Module blocks.

2. Delete both the Serial Interface module blocks.

NoteOnly one Series A IO Module block may be configured to mapto any one physical Series-A IO Modules.

3. Identify the correctly configured Serial Interface Module block. Loadthe correctly configured Serial Interface Module block.

4. Load all Control Modules containing Serial Array Channels assigned tothe correctly configured Serial Interface Module block.

5. Switch off power to the I/O chassis containing the FTE Bridge andSerial Interface Module5).

6. Perform a Checkpoint Restore to the C3006).7. Switch on power to the I/O chassis containing the FTE Bridge and

Serial Interface Module. For verification of the recovery perform aswitchover of the C300 and verify the connection is not lost to the otherSeries-A IO modules in the chassis.

Workaround : To avoid a momentarily loss of connection to Series-AChassis I/O and possibility of a Mode shed while using the C300 to Series-A Serial Interface Module through FTE Bridge topology take the followingprecautions:.

Before loading Serial Interface Module blocks to a C300 verify the pathconfiguration details are not identical to any currently loaded SerialInterface Module blocks.

If all the actions have occurred except a switchover has not yet beenperformed follow the steps identified in the Recovery.

2 INTRODUCTION

59

Profit Loop Assistant

PAR Description1-3KWWNT3 Error Indication: Experion R430, Profit Loop, Step Testing Bug in Level

Loops

Description: When step testing level loops (i.e. integrators) there is aproblem if you change parameters which effect the future signal generation(PRBS signal). In this case the SP of the loop gets set to match the OP ofthe process for a single interval and then resumes its step. This can cause alarge spike in the SP to the loop if there is a large mismatch between the SPand OP of the loop. This is a problem if any of these parameters aremodified during a test: upper/lower bounds of step, estimated responsetime, move filter.

Recovery: None.

Workaround: Do not modify any of the following parameters during a test:upper/lower bounds of step, estimated response time, move filter.

Table View

PAR Description1-F8BHKD Error Indication: Trendparameter for SCM is not displayed in mini trend

display in the station.

Description: Trendparameter for SCM is not displayed in mini trenddisplay in the station.

Recovery: None.

Workaround: None.

1-HI1PMN Error Indication: When Report and Formula parameter is printed forRCM, the report does not show the correct value.

Description: When Report and Formula parameter is printed for RCM, thereport does not show the correct value. Printing the report and formulaparameters, does not prints the current value.

Recovery: None.

Workaround: None.

PGM

PAR Description1-I1C2F3 Error Indication: CPULoLo Resource and CPU Lo Resource Alarm is

popping on PGM switch over.

Description: CPU Low resource and Low-Low resource alarm is poppingin station during PGM switch over.

Recovery: This is a momentary alarm, it is recommended that youacknowledge the alarm in station.


2 INTRODUCTION


PAR Description1-MUCYTT Error Indication: Wrong channel status is observed in PDC on PROFIBUS

network cable disconnect & reconnect with DP/Asi link offline.

Description: Basically what is happening here is that DP/Asi link is madeoffline and then PROFIBUS network cable is disconnected from the device.When the DP/Asi link is made offline all the channel status shows Bad.Now when the PROFIBUS network cable is disconnected and reconnectedfew channels statuses are showing good which were actually Bad earlier.

Recovery:

If the DP/Asi Link is made online the channel statuses show up correctly.

or

Perform PGM Switchover.

Workaround:

Perform PGM Switchover.

or

Make the DP/Asi link online.

1-WDNURN Error Indication: When there is FTE cable disconnect and reconnect, andwhen the "HoldOnFailure" is not selected for the outputs, the outputs are notinitialized with the CHINIT values for the output channels.

Description: When the FTE cable is disconnected and reconnected and ifthe Hold On Failure option for the outputs is not enabled, then the Initvalues provided in the CHINIT parameter will not be written to the outputsupon FTE cable reconnect.

Recovery: None.

Workaround: Hold On Failure option must be used to hold the outputs, thefeature of back initializing the outputs with the CHINIT values cannot beused for Drives.

1-1275R3B Error Indication: On removal and re-insertion of Profibus cable from bothprimary and the secondary PGM, output channels become bad in TURCKand SiemensET200M DSB.

Description: When Profibus cable is removed from primary PGM,switchover is initiated and when the Profibus cable is again removed fromthe new primary also all the outputs will go bad and is expected. But whenthe cable is reconnected on both the PGM's, output channels remain bad anddo not recover.

Recovery: It does not recover automatically.

Workaround: Perform PGM Switchover, all the output channels recover.

2 INTRODUCTION

61

PAR Description1-3UBSPIL Error Indication: PGM OPM fails if NVS failure exists. Compact NVS

prior to OPM.

Description: During OPM of PGM, there is a risk of migration failure if theNVS (Non-Volatile Storage) is in failed state.

Recovery:

1. Compact NVS on primary PGM and make sure there is no NVS Softfailure.

2. Make sure NVS usage is < 70%.3. Perform switchover.4. Again compact the NVS in the new primary.5. Make sure NVS usage is < 70%.6. Perform PGM OPM.

Workaround: Same as Recovery.

Rockwell Network

PAR Description1-11H1RD1 Error Indication: RsLinx does not show the Series A IO/SIM Card with

Module Icon.

Description: RsLinx application does not show the Series A IO/SIM Cardwith Module Icon.

Recovery: None.

Workaround: None.

1-13QB7PX Error Indication: RsLinx automation tool fails when executed.

Description: RsLinx Automation doesn't stop the required services andthrows error

Recovery: None.

Workaround: Manually stop the Experion Server logger service fromServices.msc application and then re-run this tool. After stopping thisservice RsLinx Automation works fine.

Standard Series C IO Modules

PAR Description1-11VNY3X Error Indication: A "Device PV Range Mismatch" alarm is reported.

Description: When any PV Range extent has a non-whole number value, a"PV Range Mismatch" alarm is reported when one does not exist.

Recovery: None.

Workaround: Avoid using decimal values for PV Range extents.

2 INTRODUCTION


FF-Configuration

PAR Description1-123KRXP Error Indication: "VCR Limit exceed" error is displayed while loading

Fieldbus device

Description: VCR limit exceed error while loading.

Recovery: Acknowledge the error.

Workaround: Cross check if the connections are done within the limitation.If not, try to delete the block and recreate the required connections.

1-14E2RC8 Error Indication: None.

Description: Control Builder allows to un-assign even if the device isloaded.

Recovery: None.

Workaround: Ensure the device is not loaded before making any changes inthe Project side.

1-3PF1Q5L Error Indication: When user executes Read Echo Curve method forHoneywell GWR level transmitter SLG700, graph does not get plotted.

Description: The data is not fetched from the Auxiliary transducer block forthis device while executing the method in Experion.

Recovery: None.

Workaround: None.

ModBus TCP Blocks

PAR Description1-3KTUVO9 Error Indication: C300 PCDI CM array Error flag does not turn "ON"

when a single Modbus device communication (TCP) is lost.

Description: C300 PCDI Device disconnect is not updating in a timelymanner - can take up to five minutes.

Recovery: Once the device is flagged as failed - ERROR FLG = "ON" thenno recovery is necessary.

Workaround: None.

Third Party Components

PAR Description1-2BPGTNP Error Indication: E3 plus relay is in "Blocked Start" state.

Description: E3 plus relay may trip with `Blocked Start indication duringoperation even when the motor or starter is not connected to the relay.

Recovery: The trip condition can be recovered from the Control Builder bygiving the "E3[0]: Fault Reset" command through the E3 plus outputchannel.

Workaround: Configure the Starts/Hour parameter and the Starts Intervalparameters as follows:-Configure the Starts/Hour to allow more starts perhour-Shorten the interval between the starts in the Starts Interval parameter.For more information about troubleshooting related to E3 plus relay trip witha Blocked Start indication, see the E3 & E3 Plus Solid-State Overload RelayUser manual from the Rockwell Literature Library.

2 INTRODUCTION

63

PAR Description1-G04A9M Error Indication: BADPV Alarms are reported against CM's using Siemens

ET200 IO Module (AI 331-1KF01-0AB0) after PGM Switchover.

Description: Intermittent BADPV Alarms are logged against ControlModules using Siemens ET200 331-1KF01-0AB0 AI module after a PGMSwitchover. No loss of Communication to the device itself occurs or no suchevent is logged. Problem recovers within a few seconds. However if Controlis configured to Shed on a Single BADPV, it will shed.

Recovery: Recovers automatically within few seconds.

Workaround: The workaround is not to use module type AI331-1KF01-0AB0 in redundant systems. According to Siemens data sheetthe basic execution time of this module is 488 ms. In case of fail over thistime is too long.

1-NMO0DJ Error Indication: Input process data of TURCK IO modules go bad onPGM switchover if one of the Turck gateway modules is removedphysically. It is also noticed that outputs are lost on PGM switchover, if theTurck excom gateway module firmware version is less than 2.2.x.

Description: Input process data of TURCK IO modules go bad on PGMswitchover if one of the Turck gateway modules is removed physically. It isalso noticed that outputs are lost on PGM switchover, if the Turck excomgateway module firmware version is less than 2.2.x.

Recovery: None.

Workaround: It is recommended to have both Turck gateway modulesconnected physically in Turck excom rack. The Turck excom gateway(GDP-IS) firmware version must be at least 2.2.x. With firmware versionless than 2.2.x, the outputs are not lost on PGM switchover if DPV1 isenabled in PROFIBUS device configuration.

1-11KCT39 Error Indication: Profibus IO module appears RED on Monitoring with thePFB Communication Status shown as ""PfbOffline and DEVSTATUSparameter of these blocks shows 'PfbNotInRun'.

Description: PBI_DEVICE blocks go offline and appear in red inmonitoring side after load of many remote-chassis I/O including SST blockat the same time. This was also seen when chassis IO modules are loaded ina particular order like Pulse input module, then Analog Output Modules andthen SST module along with its I/O modules.

Recovery: Delete all the modules and load the Profibus modules first andthen load the other chassis I/O modules.

Workaround: None.

1-17FPCH Error Indication: Internal error occurs when you try to open the documentsrelated to SST_PFB_CLX in SST Profibus installation CD part nr.705-0004,Rev. 03-02.

Description: Internal error occurs when you try to open the documentsrelated to SST_PFB_CLX in SST Profibus installation CD part nr.705-0004,Rev. 03-02. Because of this the user documentation cannot be used whichwill assist in installation or up-gradation of firmware.

Recovery: None.

Workaround: Use next version of SST_PFB_CLX in SST Profibusinstallation CD part nr.705-0004, Rev. 07.10.0.0 where issue is resolved.

2 INTRODUCTION


PAR Description1-PPG7GR Error Indication: C200 5ms controller is losing Connection with Server

Intermittently resulting in loss of View at Control Builder (everything turnsRED at Monitoring side) and Loss of View at Station for C200 DetailDisplay.

Description: Loss of View / Server Connection fail on Control Builder &Station for C200 5ms (Non-Redundant), when there is Peer-to-peer (P2P)Connection between C200 5ms & ACE on CNET and cable is disconnectedas per below: Remove Control Net Cable A of Non-Redundant C200 5ms &Remove Control Net Cable B of ACE. Remove Control Net Cable B of Non-Redundant C200 5ms & Remove Control Net Cable A of ACE. In the abovetwo Scenarios, Loss of Peer-to-peer data communication between C200 &ACE is observed which is expected. But in this scenario, the C200 5ms islosing Connection with Server Intermittently (disconnects and connectsback) and hence resulting in Loss of View at Control Builder (everythingturns RED at Monitoring side) and Loss of View at Station for C200 DetailDisplay.

Recovery: Reconnect the cables back.

Workaround: None.

1-TVWXHJ Error Indication: After checkpoint restore, output modules configuredthrough SST module remain in red color in monitoring side withDEVSTATUS set to PfbNotInRun.

Description: It is observed that after checkpoint restore, analog and digitaloutput modules remain in red color in monitoring side with DEVSTATUSset to PfbNotInRun.

Recovery: Take the C200E to NODB, reload the Master SST ProfibusInterface and IO modules.

Workaround: None.

1-WBOGBR Error Indication: SST-PFB-CLX module LCD becomes blank with noindications. The OK LED is OFF and one or both of the COMM LED andSYS LED is ON (RED).

Description: After upgrading the SST-PFB-CLX module to firmware 6.07and loading a big configuration (exceeding what is mentioned in SSTspecification of 246 words output data, 248 words input data and 250 wordsstatus), two modules get bricked. LCD on the module becomes blank withno indications. The OK LED becomes OFF and one or both of the COMMLED and SYS LED becomes ON (RED). Restarting the modules does nothelp to bring them back.

Recovery: None.

Workaround: None.

CF-Control Function

PAR Description1-RTYWYZ Error Indication: Incorrect Event flags are set momentarily in

RAMPSOAK block during profile transition.

Description: During transition from one profile to another, some Event flagof upcoming profile is set to ON for a moment.

Recovery: The incorrect Event flags state set remain in that statemomentarily and recover automatically. The correct profile Event flag is setafter the recovery.

Workaround: None.

2 INTRODUCTION

65

PAR Description1-US3KDR Error Indication: Output of Offdelay block becomes ON after a delay when

input is read from safety manger.

Description: A boolean read from the safety manager through ECI gives awrong behavior on the offdelay function block. When the input is energizedthe output must energize immediately but in this case the output is onlyenergized after the delay time.

Recovery: None.

Workaround: None.

SE-System Engineering

PAR Description1-SKJSF4 Error Indication: The user may see reverse videos on display, may see loss

of trend values.

Description: During normal operation, the servers may lose view from thecontrollers under a situation where an unresponsive node may exist in thenetwork. This may be because of a faulty device below the unresponsivenode. This may result in a loss of view condition.

Recovery: Manual. Remove the device/node that is causingunresponsiveness and Stop/Restart EPKS Control Data Access service.

Workaround: None.

Network-CNI

PAR Description1-WCZEO9 Error Indication: Remote IO communication failed with a CNI Line error

3416.

Description: Remote IO communication failed with a CNI Line error 3416.

Recovery: None.

Workaround: None.

1-XG5K9X Error Indication: CNET cable removal system alarm RTN even thoughcable fault is live

Description: CNET cable removal system alarm RTN even though cablefault exists

Recovery: None.

Workaround: None.

Network-FTE

PAR Description1-3G2TAP4 Description: R400 to R410 Migration: during the install of R410, the server

lost communication to the ESIS.

Recovery: Disconnected the Green cable to force network communicationthrough Yellow adapter if the machine cannot connect to the network.

Workaround: If the migration is reloading the operating system and FTE isnot installed, Yellow adapter Metric interface set to 1.

2 INTRODUCTION


I/O-Series C

PAR Description1-3GAHYYS Error Indication: Outputs that were POWERED when field power was lost

will return POWERED momentarily before initializing when power is againrestored.

Description: Unexpected output behavior upon return of lost field power.For more details, see PN2014-30.

Recovery: None.

Workaround: For any output that was POWERED when field power waslost ensure that the output cannot return immediately to the POWERED statewhen the field power is restored. For more detail on how this can beaccomplished see PN2014-30.

1-3I90BL7 Error Indication: HART communication errors continuously accumulate.

Description: AI-HART Analog Input module cannot communicate properlywith a WIKA T32 transmitter.

Recovery: None.

Workaround: None.

1-3NDHL6P Error Indication: The I/O module is in the No Response state.

Description: For the Digital Input module CC-PDIL51 on a system prior toR410.1, CTools does not recognize the IOM. But it will still allow afirmware download with the incorrect firmware to occur. This action rendersthe I/O module unusable.

Recovery: The I/O module must be sent back to Honeywell for recovery.

Workaround: None.

1-RM2T8X Error Indication: On Process Migration of UIO module fails with"EHI_INTERNAL" error in Experion PKS R431.2.

Description: On Process Migration of UIO module fails with"EHI_INTERNAL" error in Experion PKS R431.2

Recovery: None.

Workaround: None.

Control Functions-Hiway Emulation

PAR Description1-3RPU7B3 Error Indication: When Box HRB is made inactive from Control Builder,

TPN Hiway status display should indicate hiway error.


Recovery: None.

Workaround: None.

2 INTRODUCTION

67

Server - Installation and Migration

PAR Description1-4GHHUF7 Description: ESIS Preparation utility is not properly upgrading ESIS

repository with R431.2.

Recovery: None.

Workaround:

1. Browse to the R431 ESIS location.2. Delete the folder D_SUP and its contents.3. Use ESIS Preparation utility to create the support media folder (D_SUP)

with the latest R431 update.

1-47YJQ4H Description: While migrating from Experion R410 to either ExperionR430.1 or Experion R431.x without Operating System change and if thesecurity update KB3072630 is already installed in the machine, theninstallation fails at Server Station step.

Recovery: None.

Workaround: Before migrating from R410.x to Experion R430.1 orExperion R431.1, uninstall Microsoft Security update KB3072630 from themachine.

1-447BR3F Description: Sometimes an error message“ExperionPKS_Update_Manager.exe has stopped working” might appearduring R431.2 clean installation.

Recovery: None.

Workaround: Acknowledge the error and continue with the installation.

OPM-Upgrade Tool

PAR Description1-4RHWXMB Error Indication: Upgrade Tool (UT) is unable to detect Series C module

while launching from R400.8.

Recovery: None.

Workaround: On R400.8, even though the UT is unable to identify theSeries C components, continue with remaining steps of UT and generate thedocument for Server migration. Once the Servers are migrated to R431.3,again launch UT on Server B and generate the migration document for SeriesC modules.

2 INTRODUCTION


2.6.3 Control

CDA-Embedded

PAR Description1-15CPF6R Error Indication: You notice that connection to C200E is in RED state

and all the IOs in the C200e do not give any value and display data accessof these IOs shows reverse video.

Description: On removal of Enet module the C200e connection is lost.

Recovery: There is no specific recovery mechanism for this scenario, oneway to ensure any connection loss for C200e, Enet module must be verifiedif it is connected properly or not.

Workaround: None.

1-1NJX441 Error Indication: Noticed un-command shutdown ACE nodes duringstable run.

Description: This error is observed on stable system run, when ace.exeprocess shuts down you try to restore the checkpoint and activate them tomake them work properly.

Recovery: Restore checkpoint of ACE nodes and make the controlleractive.

Workaround: None.

1-NI0RKX Error Indication: Momentary failure in exchange block communicationwith C300/C200E & PLC 5/PLC5550.

Description: Momentary failure in exchange blocks communication withC300/C200E & PLC 5/PLC5550 observed while C300 connected throughENET, C200E to PLC5 while connected through Control net, C200Econnected to PLC5550 through remote chassis.

Recovery: This error is a temporary condition and recovery happensautomatically. This error does not have any major impact on the execution.

Workaround: None.

1-QL372H Error Indication: Parent phase block displays that child activity alreadyexists.

Description: The phase block is out of sync with the child activity

Recovery: The child RCM will need to be executed then aborted and reset.After this the parent Activity will take control of the child RCM. This has agreater chance of happening on an inter cluster peer to peer configuration.

Workaround: None.

1-VI032H Error Indication: Connection will be disconnected for 7 seconds toexchange block during C300 switch over when exchange block configuredon different FTE community.

Description: Seven seconds connection loss is observed for exchangeblocks during C300 switch over when exchange block configures ondifferent FTE community.

Recovery: Automatic recovery after 7 seconds.

Workaround: None.

2 INTRODUCTION

69

PAR Description1-3OO0E8N Error Indication: LOV and LOC observed on C300 while doing

continuous switch over (Power switchover).

Description: C300 switchover by cutting down the primary controllerpower, there was a LOV and LOC observed after it has switched overabout 200 times (Primary restarted 200 and Secondary restarted 200 times).The C300 is configured with the max load as specified in the PCT spec.

Recovery: Stop the switchover and restart the Controllers.

Workaround: None.

CDA-Server

PAR Description1-1EE8TQT Error Indication: New devices added to the Experion network are not

detected in FDM, also any existing device removal do not dynamically getupdated in FDM.

Description: This error occurs in a scenario where dynamic loading/unloading of device and dynamic removal/connection of devices happen.

Recovery: If its redundant software mux, you have to stop the softwaremux service on primary which enables software mux to switch over to backup . On non redundant system, you have to rebuild network after stoppingthe software mux service to recover from this issue.

Workaround: None.

1-1JLODM1 Error Indication: You can notice that the connection to FIM4 fails onLoad while active operation.

Description: This error occurs in scenario where cable is disconnectedfrom yellow CF9 and you try to perform Load while active operation, theload fails.

Recovery: No Recovery.

Workaround: Reconnect the Yellow UPlink cable from CF9. Theconnection is restored.

1-1LSM0ZQ Error Indication: You may notice server lost data connection to CDAafter server failover from Server B to Server A.

Description: After server fail over from server B to server A, continuousdata disconnect is observed.

Recovery: Synchronize the server and do fail over to server A.

Workaround: None.

1-1U5Z8ST Error Indication: CDA Server stops responding during normal operation.

Description: pscdasrv.exe(CDA Server) terminated unexpectedly during astable load with ActivityCreate/Delete. This may result in loss of viewcondition. The probability of this occurrence is very low.

Recovery: Manual Start of EPKS Control Data Access service.

Workaround: None.

1-SZJRS9 Error Indication: Peer to Peer between 2 SIM C300 nodes does not work.

Description: After rebooting the SIM node and checkpoint restore, it isobserved that Peer to Peer between 2 SIM C300 nodes does not work.

Recovery: Restart the Primary Server.

Workaround: None.

2 INTRODUCTION


PAR Description1-WCPMRX Error Indication: Console CDA crashed after deleting OPCG & ICG.

Description: CDA on console station crashed, after deleting OPCG andICG. This may result in loss of view condition. The probability of thisoccurrence is very low.

Recovery: Manual Start of EPKS Control Data Access service.

Workaround: None.

1-Y3OQTM Error Indication: You may see reverse videos on Display and may viewloss of trend values.

Description: During normal operation, the servers may lose view to the L1network in a situation where an unresponsive component exists aroundCDA Server. This may be because of a faulty device, too highcommunication load. This may result in a loss of view condition.

Recovery: Remove the device/node that causes unresponsiveness orreduces the communication load to be within spec. Stop/Restart EPKSControl Data Access service.

Workaround: None.

CDA-Control Data Access

PAR Description1-MXX9XL Error Indication: CDAsp on a SIM node stops responding if there are 10

or more SIM nodes configured on a single SIM node and all of them have ap2p reference to Safety Manager.

Description: During loading CM's to SIM nodes which have a p2pconfigured to Safety Manager, cdasp on the SIM node might crash if thereare 10 or more SIM nodes are created on the same node.

Recovery: none

Workaround: Do not configure 10 or more SIM nodes on a singlemachine and all initiating

1-N2IKQ7 Error Indication: You may see reverse videos on display and may observeloss of trend values.

Description: During normal operation, the servers may lose view from thecontrollers under very high communication load situation. This may resultin a loss of view condition.

Recovery: Manual. Stop/Restart of EPKS Control Data Access service.Workaround: None.

1-NE4TG3 Error Indication: Loss of View observed or Server failover is observed.

Description: If for any reason, the primary CF9 loses power and switchesover to the partner CF9, you may notice Loss of View to the controllers inthe cluster. In case of redundant Servers, you may notice that Server hasfailed over.

Recovery: For non-Redundant Servers, restart the Control Data AccessServer service manually if not already running. For Redundant Serversetup, if Server has failed over, go over to the old Primary and restart theControl Data Access Server service manually if not already running.

Workaround: None.

2 INTRODUCTION

71

PAR Description1-P9OBD9 Error Indication: The Server may lose data connection to the Controller

and result in LOV.

Description: If there are multiple controllers switching oversimultaneously, this will cause a burst of alarms to be regenerated whichmay affect the data connection to the controllers that are not switchingover.

Recovery: Automatically recovers after few seconds

Workaround: None.

1-UNZ125 Error Indication: None.

Description: Removal of cable from QCS node will not be detected inExperion station.

Recovery: Since this feature is not supported there is no specific recoverymechanism. When you detect that the values do not get updated in QCS,one way to recover is manual verification of the cables, ensure that thecables are connected and working.

Workaround: None.

1-VK9U47 Error Indication: LOV observed and controller status shows red incontrol builder.

Description: You may see reverse video for display data access, andcontroller status shows red in Control Builder.

Recovery: Switchover the Server A where this issue is observed or youmust start the CDA server manually in case of permanent LOV observed.

Workaround: None.

2.6.4 Operational/Control

Server

PAR Description1-3QRGYB9 Error Indication: The ODBC Query using MS access or odbcclient.exe application does

not include the “Point Type” value for flexible points and this field shows as blank for allflexible points.


Recovery: None.

Workaround: None.

1-5FS5EDB Error Indication: Cannot click the OP radio button on C300 Device Control faceplates tochange OP.

Description: Cannot click the OP radio button on C300 Device Control faceplates tochange OP.

Recovery: None

Workaround: The OP combo-box continues to be available as the alternate means tochange the OP.

1-3QRIISV Error Indication: Status point's PVState and OUTPUT State showing “??????” textinstead of state when query the status points using ODBC driver.


Recovery: None.

Workaround: None.

2 INTRODUCTION


PAR Description1-1P64VQD Error Indication: A file replication record cannot be configured if the Windows

sharename is 16 characters long.

Description: When configuring a new file replication record in Experion, the recordcannot be saved if the Windows sharename is 16 characters long.

Recovery: None.

Workaround: The Windows sharename should be 15 characters or less for the filereplication record to be saved correctly.

1-116TKEP Description: ODBC queries to FlexiblePoint table can return an error if the Experionserver has a disabled DSA.


Workaround: Either re-enable the DSA connection or clean the points on the disabledDSA links.

1-48YPYMT Description: Auxiliary names show server name after migration for analog points display.

Recovery: None.

Workaround: Run the following commands from the Command prompt on Primaryserver.

• Bckbld –tag ana –out allana.pnt• Pntbld allana.pnt

1-7SSNMCV Description: Default number of addresses for ControlEdge PLC is set to 1000.

Recovery: None.

Workaround: In an administrative command prompt, run the command "sysbld -preserve"and follow the on screen prompt to change the size of OPC number of addresses to thedesired number (eg: 3000).

IEC61850 Client Interface

PAR Description1-3S5PF5Z Error Indication: IEC61850 SCADA HCI interface terminates abruptly when logging

level is set to 'FLOW'.

Description: IEC61850 SCADA HCI interface terminates abruptly when logging level isset to 'FLOW'. In this case the interface terminates and restarts automatically.


Workaround: Perform the following steps.

1. Open the corresponding OPC Config.XML that is terminating.2. Change the Driver log level from FLOW to ERROR as per the following entry.

<DrvrLogLvl btype="Enum" type="LogLvl">ERROR</DrvrLogLvl>3. Restart the corresponding driver.

1-54062S1 Error Indication: When clicked on IEC61850 IED’s Link under Configuration tab ofIEC61850 Interface the following error is thrown “The Display file syscfgIEDSummarywas not found”.

Description: syscfgIEDSummary Display files is an IEC 61850 Edition-2 feature and willbe available for IEC61850 Edition-2 Package.

Recovery: Ignore the error Message.

Workaround: None.

2 INTRODUCTION

73

MLDP Driver Software for Experion Integration

PAR Description1-3OCXMW0 Error Indication: If the password for mngr contains a blank space, enabling the Master

Logic channel fails in the first attempt. This was observed on a clean R431 installation aswell as during migration from R400 to R431 on R431 SERVERB at dual primary stage.


Recovery: Disable the Master Logic channel on failure.

Workaround: Perform the following steps.

1. In the Windows Command Console, type dcomcnfg on the Experion PKS Servermachine.

2. Right-click Console Root -> Component Services -> Computers -> My Computer -> DCOM Config ->Hci Server for Master Logic and then select Properties.

3. Click the Identity tab and re-enter the password for the mngr user overwriting theexisting entry.

4. Enable the ML channel again from Station.

2 INTRODUCTION


2.7 What task do you want to accomplish?This section describes the tasks you need to perform depending upon your requirement.

Related topics“Clean installation of R432.2” on page 75“Upgrade to R432.2 from R432.1” on page 75“Migrate to R432.2 from R43x.x and R4xx.x releases” on page 75

2.7.1 Clean installation of R432.21 Create the Experion PKS Support Software media by downloading the latest point release media content

from “www.honeywellprocess.com” website -CM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.iso.

2 Start installation. Refer to the Experion Software Installation User’s Guide for assistance in installation.

2.7.2 Upgrade to R432.2 from R432.1

AttentionBefore upgrading/migrating to this point release, register with the Migration COE by raising a new Service Request atleast 4-6 weeks before performing the upgrade/migration procedure. You can raise a Service Request either bycontacting your local Honeywell Process Solutions Customer Contact Center (CCC) or visiting “www.honeywellprocess.com” or contact Migration COE at “[email protected]”.

If you have any prior release tools and controller Hotfixes, uninstall the Hotfix by referring to the appropriateHotfix SCN.

Performing upgrade/migration procedure1 Create the Experion PKS Support Software media by downloading the latest point release media content


2 Prerequisites:a Experion PKS R432.1 must be installed on the system.b Verify the present version.

If the following line is present, the node has the appropriate product version to upgrade to this pointrelease.

+Experion PKS R432.1 Support Media Install completed on MM/DD/ YYYY HH:MM:SS AM/PM3 Start upgrade. Refer to section, “Upgrade to Experion PKS R432.2”.

2.7.3 Migrate to R432.2 from R43x.x and R4xx.x releases


If you have any prior release tools and controller Hotfixes, uninstall the Hotfix by referring to the appropriateHotfix SCN.

You can migrate to Experion R432.2 from Experion R400.x, Experion R410.x, and Experion R430.x withoutstopping at the base release Experion R432.1.

2 INTRODUCTION

75

To migrate to R432.2 from R43x.x and R4xx.x1 Create the Experion PKS Support Software media by downloading the latest point release media content


2 Prerequisites:a Experion PKS R32x.x, R400.x, R410.x or R430.x must be installed on your system.b Take a backup of the system image using Experion Backup and Restore before installing this point

release on any node.c Enable Windows firewall.d On ES-T and ES-CE nodes (a Remote GUS Client) install the IKB Service package on the node.

(Installation of IKB Service is MANDATORY irrespective of whether physical IKB is used).The IKB Service can be installed from the Experion Application DVD, IKB OEP package.

3 Verify the present version.a Using Notepad, open the ProductVersion.txt file located in the following path.

<%User selected path%>\Honeywell\Experion PKS>For example, C:\Program Files(X86) \Honeywell \Experion PKS

b In the ProductVersion.txt, verify if one of the following lines is present. These lines indicate that thenode has the appropriate product version to migrate to this point release.• +Experion PKS R310.x Install completed on MM/DD/ YYYY HH:MM:SS AM/PM• +Experion PKS R311.x Install completed on MM/DD/ YYYY HH:MM:SS AM/PM• +Experion PKS R400.x Install completed on MM/DD/ YYYY HH:MM:SS AM/PM• +Experion PKS R410.x Install completed on MM/DD/ YYYY HH:MM:SS AM/PM• +Experion PKS R430.x Install completed on MM/DD/ YYYY HH:MM:SS AM/PM

Here, “x” indicates the subsequent migration path as mentioned in the section “Supported servermigration paths”

4 Start migration. Refer to the Experion Migration Planning Guide for assistance in migration.

Sever client migrationThe different server/client migration and installation scenarios supported for Experion R432.2 are describedin the Experion Migration Planning Guide. The document also describes ` the Microsoft Windows operatingsystems supported for different Experion node types and the behavior of the Install Sequencer when it is runon the system. Some migration scenarios may require a hardware upgrade.

Controller migration

AttentionController migration is optional; it is only required when a controller-related error needs to be fixed. Refer tothe list of “Tools and Controller resolved PARs” in this SCN. Server/client-related fixes are decoupled from thecontroller-related fixes.

The migration of controllers and control hardware can be performed in a number of ways, depending uponthe system topology and the compliment of the installed I/O. Typical scenarios are described in the ExperionMigration Planning Guide. Note that controller migration is performed, after server/client migration iscompleted.

2 INTRODUCTION


3 Getting started

Related topics“Applicable nodes” on page 78“Applicable modules” on page 79“Supported migration and upgrade paths” on page 80“Supported server upgrade paths” on page 81“Supported controller migration paths” on page 82“Downloading the point release media” on page 84“Downloading the Experion PKS PDF Collection media” on page 85“Downloading Experion PKS Upgrade Tool Components media” on page 86

77

3.1 Applicable nodesThis point release is applicable for the following nodes.

Sl. No. Node Is Experion PKS R432.2 applicable?1 Application Server (EAS) Yes

2 Application Control Environment (ACE) Yes

3 Application Control Environment TPNConnected (ACET)

Yes

4 Console Station (ES-C) Yes

5 Console Station TPN Connected (EST) Yes

6 Console Extension Station (ES-CE) Yes

7 Experion Server (ESV) Yes

8 eServer Yes

9 Experion Server TPN Connected (ESVT) Yes

10 Experion HiWay Gateway (EHG) Yes

11 Experion Application node. (E-APP) Yes

12 Flex Station (ES-F) Yes

13 Simulation Control Environment (SCE) Yes

14 Collaboration Station Yes

15 PCUS Yes

16 Remote Engineering Station Server (RESS) Yes

17 Optional Feature Yes

18 PHD point server Yes

3 GETTING STARTED


3.2 Applicable modulesThe following section is for upgrading from R432.1 to R432.2, for other migrations/upgrades, contact MigrationCOE.

AttentionThe following applicable modules may change depending on the point release you have installed. For moreinformation about applicable modules, contact Migration COE at [email protected]

Sl. No. Node Is applicable for ExperionR432.2?

1 CF9 No

2 C200CPM No

3 C200E controller Yes

4 C300 controller Yes

5 Fieldbus Interface Module Yes

6 Fieldbus Interface Module 4 Yes

7 Fieldbus Interface Module 8 Yes

8 Fault Tolerant Ethernet Bridge Module Yes

9 IO Link Interface Module Yes

10 I/O Module Yes

11 Legacy I/O Link Module No

12 PROFIBUS Gateway Module 2 Yes

13 Enhanced High-Performance Process Manager Yes

14 Experion HiWay Bridge Yes

15 Enhanced TPS Node Yes

16 Enhanced Network Interface Module Yes

17 Ethernet Interface Module Yes

3 GETTING STARTED

79

3.3 Supported migration and upgrade pathsThe following migration paths are supported.

Related topics“Supported server migration paths” on page 80

3.3.1 Supported server migration pathsThe following server migration paths are supported.

Sl. No. Direct migration of server and clients supported to R432.2 without hoppingthrough R432.1

1 Experion R400.1

2 Experion R400.2

3 Experion R400.3

4 Experion R400.4

5 Experion R400.5

6 Experion R400.6

7 Experion R400.7

8 Experion R400.8

9 Experion R410.1

10 Experion R410.2

11 Experion R410.3

12 Experion R410.4

13 Experion R410.5

14 Experion R410.6

15 Experion R410.7

16 Experion R410.8

17 Experion R410.9

18 Experion R430.1

19 Experion R430.2

20 Experion R430.3

21 Experion R430.4

22 Experion R430.5

23 Experion R430.6

24 Experion R431.1

25 Experion R431.2

26 Experion R431.3

27 Experion R431.4

3 GETTING STARTED


3.4 Supported server upgrade pathsThe following server migration paths are supported.

Sl. No. Server path1 Experion R432.1

3 GETTING STARTED

81

3.5 Supported controller migration pathsThe following controller migration paths are supported.

AttentionYou cannot migrate from any subsequent point releases after migrating from the point releases mentioned in thefollowing table to R432.x releases

Sl. No. Controller path1 Experion R310.2 Controller Patch 1

2 Experion R310.3 Controller Patch 3





7 Experion R310.3 Tools and Controller Patch 12





12 Experion R311.3










22 Experion R400.1




26 Experion R400.2









3 GETTING STARTED


Sl. No. Controller path35 Experion R400.2 Tools and Controller Patch 9

36 Experion R400.3

37 Experion R400.4

38 Experion R400.5

39 Experion R400.6

40 Experion R400.7

41 Experion R400.8

42 Experion R410.1

43 Experion R410 Controller Patch 3

44 Experion R410 Controller Patch 4

45 Experion R410.2

46 Experion R410.2 Rev2

47 Experion R410.3

48 Experion R410.4

49 Experion R410.5

50 Experion R410.6

51 Experion R410.7

52 Experion R410.8

53 R410.9

54 R430.1

55 R430.2

56 R430.3

57 R430.4

58 R430.5

59 R430.6

60 R431.1

61 R431.2

62 R431.3

63 R431.4

64 R432.1

3 GETTING STARTED

83

3.6 Downloading the point release mediaThe latest point release media is available as multiple zip files (7z files) on the Honeywell Process Solutionswebsite. Download these zip files to create an ISO image before you begin installation.

To download the latest point release media, refer to the Experion Update Matrix using the following link:

“https://www.honeywellprocess.com/library/support/software-downloads/Experion/experion-update-matrix.zip”

Prerequisites7zip software must be installed on your system before you begin extraction.

To download the point release media1 Locate the latest point release zip files on Honeywell Process Solutions website (“https://

www.honeywellprocess.com/library/support/software-downloads/Experion/EXP-R432.2.pdf”).2 Download the three zip files to a temporary location from the Download Software section on your hard disk.3 Select the three zip file, and extract the contents. The tool extracts all the file contents.

a The zip files are extracted to the folderCM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121

b An ISO image is created automatically after extraction.4 Extract the CM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.iso file.

AttentionEnsure that you have the ISO extraction software to extract the Experion PKS R432.2 ISO content. For example,you can use the “Virtual CloneDrive” as ISO extraction software.

5 Copy the extracted files to a temporary folder on your hard disk.6 Copy the extracted files to all nodes and also ensure that ISO content is copied without missing any file on

each node.

AttentionIf you have installed the Whitelisting application, ensure to follow the procedure mentioned in the WhitelistingImplementation Guide before installing the patch.

Example1 Locate the latest point release zip files on Honeywell Process Solutions website (“https://

www.honeywellprocess.com/library/support/software-downloads/Experion/EXP-R432.2.pdf”).2 The following zip files are listed.

• CM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.z01• CM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.zip

3 Download the above zip files.4 Select the three zip file, and extract the contents. The tool extracts all the file contents.

a The files are extracted to the folderCM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.

b The CM_EXP432.2-04.1_Experion_Support_Software_DVD_R432.2_51156121.iso is createdautomatically.

3 GETTING STARTED


https://www.honeywellprocess.com/library/support/software-downloads/Experion/experion-update-matrix.zip

https://www.honeywellprocess.com/library/support/software-downloads/Experion/EXP-R432.2.pdf




3.7 Downloading the Experion PKS PDF Collection mediaFor R432.2, there is no separate Experion PKS PDF Collection media. You can download the R432.1 ExperionPKS PDF Collection media from “www.honeywellprocess.com”. Note that a number of documents are updatedfor R432.2 and can be downloaded from “www.honeywellprocess.com”.

3 GETTING STARTED

85

3.8 Downloading Experion PKS Upgrade Tool Components mediaFor R432.2, there is no separate Experion PKS Upgrade Tool Components media. You can download theR432.1 Experion PKS Upgrade Tool Components media from “www.honeywellprocess.com”.

3 GETTING STARTED


4 Upgrade to Experion PKS R432.2

Related topics“Upgrade sequence” on page 88“Upgrade checklist” on page 89“Preparing for upgrade” on page 90“Upgrading the non-redundant server node by installing the point release” on page 91“Upgrading the redundant server by installing the point release” on page 94“Installing the point release on Server A” on page 97“Upgrading clients with the point release” on page 100“Upgrading the ACE/ SCE/ EHG by installing the point release” on page 103“Post Install Activities after all nodes have been upgraded” on page 106“Updating common components” on page 107“Installing PHD Point Server Patch” on page 108“Migrating controllers” on page 109

87

4.1 Upgrade sequence

AttentionThis section describes about upgrading your system to this point release from R432.x

This point release must be installed on Experion nodes in the following order. Refer to the respectiveinstallation sections in the document.

Sl. No. Experion nodes Refer to the section...1 Server B "Upgrading the redundant server

by installing the point release "

2 Non-redundant server "Upgrading the non-redundantserver node by installing thepoint release"

3 Flex Station/Collaboration Station "Upgrading the ExperionApplication Server/ Console/Flex/Collaboration Station/Console Extension Station/eServer/Premium Access clientsby installing the point release"

4 Console Station "Upgrading the ExperionApplication Server/ Console/Flex/Collaboration Station/Console Extension Station/eServer/Premium Access clientsby installing the point release"

5 Server A "Upgrading the redundant serverby installing the point release"

6 ACE/SCE/EHG "Upgrading the ACE/ SCE/EHG by installing the pointrelease"

7 E-APP/Experion Application Server/ eServer "Upgrading the ExperionApplication Server/ Console/Flex/Collaboration Station/Console Extension Station/eServer/Premium Access clientsby installing the point release"

AttentionIf you are using Experion Support and Maintenance (ESM) to install the point release on the Experion cluster, add thepoint release to the ESM Server. For more information, refer to the Installation Builder User's Guide.

4 UPGRADE TO EXPERION PKS R432.2


4.2 Upgrade checklistUpgrading to Experion PKS R432.2

Task ReferenceCheck for any PN, BW, and GTAC audit documents. Refer to the “GTAC Support” section in this document.

Check the applicable nodes. Refer to “Applicable nodes” in this SCN.

Install Experion PKS R432.2 on the applicable nodes. Refer to “Preparing for upgrade” in this SCN.

Review the Experion Update Matrix and determine if any ofthe patches that are available for this point release areapplicable to your system. If they are then download themand install them.

Experion Update Matrix at: www.honeywellprocess.com/library/support/software-downloads/Experion/experion-update-matrix.zip


89

4.3 Preparing for upgradeEnsure to take back up before any upgrade.

Performing upgrade/migration procedure




4.4 Upgrading the non-redundant server node by installing the pointrelease

AttentionYou must execute the ERDB Consistency Checker (ECC) tool before any upgrade activity to identify any potentialdatabase related issue which may cause a migration failure in the future.

Related topics“Pre-installation steps” on page 91“Stopping the services” on page 91“Installing the point release” on page 92“Validating the point release installation” on page 92“Post-installation tasks” on page 93

4.4.1 Pre-installation steps1 Ensure that you are logged on to the server using an account that is part of both the Windows Administrators

and the Product Administrators group. It is not recommended to use HPSInstall account as it is a temporaryaccount used for installation/migration purpose only.

AttentionEnsure that you log on with the required privileges.

2 For systems with licensed QVCS only: Open the QVCS Manager application and complete the requiredQVCS operations (for example: Check in, check out, revert, and so on). Close the QVCS Managerapplication manually.

3 Perform the following Checkpoint tasks.a Disable all the Checkpoint tasks; click Stop for all the scheduled Checkpoint tasks.

AttentionCheckpoint tasks that are currently executing must be completed. Ensure that all the automatic or manualCheckpoint Save tasks are complete.

b Ensure that the Checkpoint share has replicated correctly to all the Console stations.c To verify the replication of the Checkpoint shares, check the Event Summary Display page on the

Station after the manual/auto Checkpoint Saves are completed for all controllers. If the EventSummary Display page does not display any replication failure event, the replication is successful.

4 Disable all virus scan/protection/backup applications or services. If the DVM Logger service is present, itmust be disabled.

AttentionYou must enable the services after completing the procedure.

5 Close all the running applications.

4.4.2 Stopping the servicesBefore installing the point release, you must stop the SNMP services. If PMD is installed, use PDS Server toolfrom Start > All Programs > PMD > Start or Stop PDS Server and stop the PMD services. Perform thefollowing steps to stop all services manually.1 Choose Start > All Programs > Honeywell Experion PKS.


91

2 Right-click Experion PKS Services Control Panel tool and then click Run as Administrator.3 Click the Stop all Services and click OK.

AttentionInstalling the point release on a non-redundant server leads to a loss of view.

a If AEA Event Collection service is in the running state, perform following steps to stop the service.b Click Start > Run, type Services.msc and press Enter.c Right-click AEA Event Collection and click Stop to stop the service.

4.4.3 Installing the point release1 If you are using Experion Support and Maintenance (ESM) to install the point release, install the point

release from the ESM client. For more information, refer to the Installation Builder User's guide. If you arenot using ESM to install the point release, go to step 2.

2 Browse to the folder containing the installer Experion PKS R432.2 > supportsoftware.exe. If theinstallation is from the network, then map the location where the installer folder is located to the networkdrive.a In the command prompt, as an Administrator, type the following command.

net use <drive>: \\computername\share\<folder> (for example, net use Z: “\\199.63.5.151\temp\ExperionPKS R432.2” )

b Ensure that the path mapped (for example, \\199.63.5.151\temp\<point release>) has both ‘Read’ and‘Write’ permissions.

c Type the user name and password (must be in quotes if there is a blank).d In the same command prompt window, change to the above mapped drive and run supportsoftware.exe.

3 Right-click supportsoftware.exe and then click Run as Administrator. If the User Account Controldialog box is displayed, click Yes to continue.The Welcome to Experion PKS Update Manager dialog box appears.

4 Click Next and enter the Password in the Login Credentials panel to perform the auto logon after restart.Confirm that you have resolved all ERDB inconsistencies by selecting the ECC check box.

5 Click Next to start the installation.

AttentionIf you notice "Failed to stop <service name> Installation will be aborted now." acknowledge the error message,stop the service manually and restart the installation.

If the installation is being performed from the network, map the drive again after each system restart and executeSupportSoftware.exe to continue the installation. To map the drive, perform the steps mentioned in step 2 a.

6 Follow the on-screen instructions and click Finish. The node restarts after the installation is complete.

4.4.4 Validating the point release installation1 Using Notepad, open the ProductVersion.txt file located in the following path: C:\Program Files(X86)

\Honeywell \Experion PKS OR <User selected path>\Honeywell\Experion PKS.2 Verify the ProductVersion.txt for the following:

+Experion PKS R432.2 Install completed on MM/DD/YYYY HH:MM:SS AM/PMIf the above line is present, it indicates that the installation is successful.

AttentionAfter this point release is installed, an entry is made in the registry to indicate that the system is upgraded toExperion PKS R432.2. However, no other references are being updated. Hence, you may also see previousExperion release references in the product information.



4.4.5 Post-installation tasks1 Log on as a member of Windows Administrators and Product Administrators group.2 From Station or Control Builder, enable all the Checkpoint tasks.3 Enable all virus scan/protection/backup applications or services. If the DVM Logger service is present and

disabled, it must be enabled.4 Perform the following steps to migrate the Quick Builder project.

a Open Configuration Studio.b Select Build Channels.

The Quick Builder migration wizard appears.c Click Next to proceed with the migration.d Click Finish to complete the migration. The Quick Builder project opens automatically.

AttentionDuring the migration, you may come across the Unresolved Properties page, with the appearance ofControlInhibit in the list. Ignore the prompt and proceed with the migration.


93

4.5 Upgrading the redundant server by installing the point releaseHoneywell recommends that for redundant servers you first install the point release on Server B, followed byone Client to perform system tests before promptly migrating Server A. Once Server A is migrated, theremaining Clients and then Controllers can be migrated.





2 Confirm that Server A is primary.3 If the servers are not synchronized, click Synchronize.4 Turn off file replication of the mapping files.

a In Station, click Configure > File Replication. Do not change the Send check box in this display.b Click mapping entry.

The configuration page for mapping file replication entry appears.c Clear the Replicate files from this path check box.d Click Save.

5 Perform the following Checkpoint tasks.a Disable all the Checkpoint tasks; click Stop for all the scheduled Checkpoint tasks.

AttentionCheckpoint tasks that are currently executing must be completed. Ensure that all the automatic or manualCheckpoint Save tasks are complete.

b Ensure that the CPBASE and Checkpoint shares have replicated correctly between Server B and ServerA.

c Ensure that the Checkpoint share has replicated correctly to all the Console stations.d To verify the CPBASE and the replication of the Checkpoint shares, check the Event Summary Display

page on the Station after the manual/auto Checkpoint Saves are completed for all controllers. If theEvent Summary Display page does not display any replication failure event, the replication issuccessful.






8 Perform the following steps to disable ERDB replication.a Open Configuration Studio.b Select Administer Control Strategy Database. Perform the required steps to disable ERDB replication.

9 Perform the following steps to disable EMDB replication.a Open Configuration Studio.b Select Administer the System Database. Perform the required steps to disable EMDB replication.

10 Close all the running applications.The installer automatically stops most of the required Experion services. However, certain services that arenot stopped by the installer must be stopped manually.

4.5.2 Stopping the servicesBefore installing the point release, you must stop the SNMP services. If PMD is installed, use PDS Server toolfrom Start > All Programs > PMD > Start or Stop PDS Server and stop the PMD services. Perform thefollowing steps to stop all services manually.1 Choose Start > All Programs > Honeywell Experion PKS.2 Right-click Experion PKS Services Control Panel tool and then click Run as Administrator.3 Click the Stop all Services and click OK.




net use <drive>: \\computername\share\<folder> (for example, net use Z: “\\199.63.5.151\temp\Experion PKS R432.2” )




4 Click Next and enter the Password in the Login Credentials panel to perform the auto logon after restart.Confirm that you have resolved all ERDB inconsistencies by selecting the ECC check box.





95






4.5.5 Post-installation tasks1 If you want to install Internet Explorer 11, you can run Technology Updates installer (“https://

www.honeywellprocess.com/library/support/software-downloads/Experion/Technology-Update-Software.pdf”).

2 Log on as a member of Windows Administrators and Product Administrators group.3 Click Start > All Programs > Honeywell Experion PKS > Server > Station to start the station.4 On the Redundancy tab, click Synchronize to synchronize the servers.5 Click Manual Failover.

AttentionServer B becomes primary after the server failover.

6 If you have plan to install the point release on client nodes before installing on Server A, then on theRedundancy tab, click Synchronize to synchronize the serves. And also, confirm the connectivity to ServerB from client nodes before installing point release on Server A.

7 Enable all virus scan/protection/backup applications or services. If the DVM Logger service is present anddisabled, it must be enabled.

8 Perform the following steps to migrate the Quick Builder project.a Open Configuration Studio.b Select Build Channels.





https://www.honeywellprocess.com/library/support/software-downloads/Experion/Technology-Update- Software.pdf



4.6 Installing the point release on Server A

AttentionAfter installing this point release on Server B, continue with point release installation on Flex Station/CollaborationStation and Console Station nodes before proceeding with point release installation on Server A.





2 Confirm that Server B is primary.3 Disable all virus scan/protection/backup applications or services. If the DVM Logger service is present, it

must be disabled.


4 Close all the running applications.The installer automatically stops most of the required Experion services. However, certain services that arenot stopped by the installer must be stopped manually.

5 Disable the Experion PKS Server System service. To disable the Experion PKS Server System service,perform the following steps.a Choose Start > All Programs > Accessories > Command Prompt.b Right-click Command Prompt and click Run as Administrator. Click Yes in the prompt to continue.c In the Command Prompt, type the following command sc config HSCSERVER_System start= disabled

and click ENTER (the command must have a space after the equal sign).d Ensure that you see the following message once the Experion PKS Server System service is disabled

successfully [SC] ChangeServiceConfig SUCCESS.



97









AttentionFor redundant servers only: Before you restart the redundant server, review the network configuration forredundant servers to ensure that the network settings are correct for each node. If network settings are notconfigured or restored properly after installation, both the servers may act as primary servers and you mayexperience loss of view depending on server or station configuration.

If you notice "Failed to stop <service name>. Installation will be aborted now." acknowledge the error message,stop the service manually and restart the installation.


5 Follow the on-screen instructions and click Finish. The node restarts after the installation is complete.6 Start the Experion PKS Server System service. To start the Experion PKS Server System service, perform

the following steps.a Choose Start > All Programs > Accessories > Command Prompt.b Right-click Command Prompt and click Run as Administrator. Click Yes in the prompt to continue.c In the Command Prompt, type the following command sc config HSCSERVER_System start= auto and

press Enter (the command must have a space after the equal sign).d Ensure that you see the following message [SC] ChangeServiceConfig SUCCESS.e In the Command Prompt, type the following command hscserver /start /y and press Enter.f Ensure that you see the following message once the Experion PKS Server System service is started

successfully Starting Server.hsc_Server_Control_s -stateRequired=4 hsc_Server_Control_s- Exiting, atend with returnval 4 Completed successfully.









2 Log on as a member of Windows Administrators and Product Administrators group.3 Perform the following steps to enable ERDB replication.

AttentionThis step must be performed on Server B.

a Open Configuration Studio.b Select Administer Control Strategy Database. Perform the required steps to enable ERDB replication.

4 Perform the following steps to enable EMDB replication.a Click Start > All Programs > Honeywell Experion PKS > Server > Station to start the station.b On the Redundancy tab, click Synchronize to synchronize the servers.c If the servers are not synchronized, click Synchronize.d Click Manual Failover.

AttentionServer A becomes primary after the server failover.

5 Click Synchronize to synchronize the servers.6 Turn on file replication of the mapping files.

a In Station, click Configure > File Replication. Do not change Send check box in this display.b Click mapping entry.c The configuration page for mapping file replication entry appears.d Select Replicate files from this path check box.e Click Save.

7 Enable all virus scan/protection/backup applications or services. If the DVM Logger service is present anddisabled, it must be enabled.

8 From Station or Control Builder, enable all the Checkpoint tasks.9 If the point release has been already installed on the Server B, then perform the following steps to migrate

the Quick Builder project.a Open Configuration Studio.b Select Build Channels.




99




4.7 Upgrading clients with the point release

Related topics“Pre-installation steps” on page 100“Stopping the services” on page 91“Installing the point release” on page 101“Installing the point release on Premium Access clients” on page 101“Validating the point release installation” on page 92“Post-installation tasks” on page 102





3 Perform the following Checkpoint tasks.a Disable all Checkpoint tasks; click Stop for all the scheduled Checkpoint tasks.

AttentionAny currently executing Checkpoint tasks must be complete before continuing. Ensure that all the automaticor manual Checkpoint Save tasks are complete. Checkpoint file replication fail alarm is generated ifCheckpoint file replication is enabled and Checkpoint schedule is ON during console patch up-gradation.

b Ensure that the Checkpoint share has replicated correctly to all the Console stations.c To verify the replication of the Checkpoint shares, check the Event Summary Display page on the

Station after the manual/auto Checkpoint Saves are completed for all controllers. If the EventSummary Display page does not display any replication failure event, the replication is successful.



5 Close all running applications.




AttentionInstalling the point release on a non-redundant server leads to a loss of view.

a If AEA Event Collection service is in the running state, perform following steps to stop the service.b Click Start > Run, type Services.msc and press Enter.c Right-click AEA Event Collection and click Stop to stop the service.












4.7.4 Installing the point release on Premium Access clients1 Ensure that the eServer associated with the Premium Access client is already updated.2 Ensure that you are logged on to the server using an account that is part of both the Windows Administrators


AttentionEnsure that you log on with required privileges.

3 From the Start > Control Panel > Add or Remove Programs, select and remove the following programs.• HMIWeb Browser Runtime• Experion PKS Server Client Side Components

4 Open eServer home page and click on the link - Click here to install Premium Access components.5 Click the appropriate link to install the Premium Access components.6 Click the appropriate link to install the server client components.


101







2 Log on as a member of Windows Administrators and Product Administrators group.3 From Station or Control Builder, enable all the Checkpoint tasks..4 Enable all virus scan/protection/backup applications or services. If the DVM Logger service is present and

disabled, it must be enabled.5 Perform the following steps to migrate the Quick Builder project. This step can be an optional step for

Console Station node if you have not migrated the Quick Builder project on Server nodes and opened theQuick builder for 1st time on Console Station node.However, this step is not applicable for other nodes like eServer, Experion Application Server, Flex,Collaboration Station, and Premium Access clients.a Open Configuration Studio.b Select Build Channels.

The Quick Builder migration wizard appears.c Click Next to proceed the migration.d Click Finish to complete the migration. The Quick Builder project opens automatically.

AttentionDuring the migration, you may come across the Unresolved Properties page, with the appearance of ControlInhibitin the list. Ignore the prompt and proceed with the migration.






4.8 Upgrading the ACE/ SCE/ EHG by installing the point release





2 Perform the following steps.

AttentionPerform step a through step d on Control Builder from Server B (redundant server) or Experion server (non-redundant).

a From Control Builder Monitoring view, right-click the node FB and select Upload/Update to Projectwith Contents.The Upload/Update to Project with Contents box is displayed.

b Clear Server Configuration Information check box and click Continue.The tuning constants are uploaded from the controller to the Monitoring view of ERDB.

c Perform a manual Checkpoint Save of the controller.d Ensure that the Checkpoint shares have replicated correctly between the server and all the Console

stations.e To verify the replication of the Checkpoint shares, check the Event Summary Display page on the

Station once the manual Checkpoint Save is completed for this controller. If the Event SummaryDisplay page does not display any replication failure event, the replication is successful.

3 Modify the node FB CEESTATE to IDLE.4 Change the node FB ACE / SIM command to SHUTDOWN. For more information, refer to the Control

Building User’s Guide.5 Shutdown the node FB from the Control Builder.



103


















2 Log on as a member of Windows Administrators and Product Administrators group.3 Perform a Checkpoint Restore for the node and correct any errors that are observed during the Checkpoint

Restore.4 From the Control Builder Monitoring view, perform a COLDSTART or WARMSTART of ACE-CEE and

SCE-CEE as follows:






a Open the ACE-CEE Configuration form.b Click WARMSTART/COLDSTART (as applicable) from the CEE Command. For more information

about COLDSTART and WARMSTART, refer to the Control Building User’s Guide.5 Perform a Checkpoint Save after the node is successfully started. The CMs/SCMs are made active (in case

of a COLDSTART only). This ensures that the necessary runtime information and the correct executionstates of the CMs/SCMs is available in the latest. cp file of the ACE node.


105

4.9 Post Install Activities after all nodes have been upgradedFor systems that meet the following prerequisites there is an additional command that should be executed:

• Cluster consists of ESVT and ES-Ts• This point release has been installed on the ESVTs and ES-Ts• Have an EHPM configured and loaded in Control Builder• The EHPM has the "EHPM Data Access" setting set to "Peer to Peer and ExpServer"

If the above prerequisites are met, then on the primary ESVT and each ES-T open a command prompt and run:primecombopoints /validate /all



4.10 Updating common components

AttentionNote that these steps must be performed ONLY if you install an optional common component package using ExperionPKS Installation media after installing this point release. To update the installed optional common component packageversion to Experion PKS R432.2 versions, you must reinstall Experion PKS R432.2.

Follow the steps provided in the following respective sections to update the installed optional commoncomponent package version to Experion PKS R432.2.

• Installing the point release on a non-redundant server• Installing the point release on Server B• Installing the point release on Server A• Installing the point release on Experion Application Server/ Console/ Flex/Collaboration Station/Console

Extension Station/eServer/Premium Access clients• •Installing the point release on ACE or SCE


107

4.11 Installing PHD Point Server Patch

Related topics“Installing PHD Point Server patch” on page 108“Validating PHD Point Server installation” on page 108

4.11.1 Installing PHD Point Server patch1 Log in using an account that is a member of the Windows administrator’s group.2 Start the Experion PKS Services Control Panel program (from Start > All Programs > Honeywell

Experion PKS > Experion PKS Services Control Panel).Once started, select StopAll services and click OK to stop all Experion services.

3 Click Exit to exit the Experion PKS Services Control Panel program.4 Navigate to the software patch package, Experion PKS R432.2 > Packages\ServerClient

\PHDPointServer\Experion PKS R432.2 PHD Point Server.exe, in Windows Explorer and right clickRun as administrator.

5 Click Yes when prompt asked if you want to allow the patch to run. The patch will begin to extract.6 Click OK when asked if you want to install the following update. A Command Prompt window with the

text “Installing patch…” and a few windows installer dialogs will appear.7 Once the patch installation is finished, a message ‘Experion PKS R432.2 PHD Point Server.exe’ is

installed successfully will appear.8 Using the Server Experion PKS Services Control Panel program to restart all services.

AttentionIf the software patch installer reports that some programs must be closed before installing, click “OK” to acceptthis and let the installer to terminate these programs. Otherwise, click “Cancel” to abort installation.

4.11.2 Validating PHD Point Server installation1 Using Notepad, open the ProductVersion.txt file located in the following path: C:\Program Files(X86)


++Experion PKS R432.2 PHD Point Server Installed on MM/DD/YYYY HH:MM:SSIf the above line is present, it indicates that the installation is successful.



4.12 Migrating controllers

Related topics“Updating the firmware” on page 109“Firmware revisions” on page 109

4.12.1 Updating the firmware1. Perform the upgrade readiness checks using the Upgrade Tool (UT) and Migration Readiness Tool (MRT).

For more information about UT, refer to the Experion Migration Planning Guide and Upgrade Tool UsersGuide.

2. Migrate the controllers and modules using the Controller Migration wizard (CMW).

CMW can be used for both on-process and off-process migration in an automated way. NTools and CToolscan be used for manual firmware upgrade.

For more information about CMW, refer to Controller Migration in the respective Scenario- specificmigration guide.

4.12.2 Firmware revisionsThe following table provides details about the firmware versions.

Module Module number Firmware version FileAIH Cx-PAIHx1 05.00.03 aih_5_00_03.s28

AIBOOT Cx-PAIHx1 05.00.01 aih_5_00_03.s28

AOH Cx-PAOHx1 05.00.04 aoh_5_00_04.s28

C300

Cx-PCNT01

CC-PCNT02 EXP432.1–10.112

c300.lcf

c300_ehb.lcf

c300app2.pcm

c300app2_20.pcm

c300app2_ehb.pcm

c300boot2.pcm

c300boot2_20.pcm

c300boot2_ehb.pcm

c300boot2x.pcm

c300boot2x_20.pcm

c300boot2x_ehb.pcm

C200 TK-PRS022 EXP432.1–10.112

Cee50e.pcm

Cpmboote.pcm

DI Cx-PDILx1 05.00.01 di_5_00_01.s28

EHPM EC-THPM01 EXP432.1-10.112

ehpm.lcf

ehpmapp1.pcm

ehpmboot1.pcm


109

Module Module number Firmware version File

EHB EC-EHB01 EXP432.1–10.112

ehb.lcf

ehbapp1.pcm

ehbboot1.pcm

enim2ehb.lcf

ELMM CC-ELMM01 EXP432.1–10.112

elmm.lcf

elmmapp2.pcm

elmmboot2.pcm

ENIM EC-TNIM01 EXP432.1-10.112

epni2.lcf

epni2app1.pcm

epni2boot1.pcm

ETN EC-ETB01 EXP432.1–10.112

etn.lcf

ETNapp1.pcm

ETNboot1.pcm

FIM TK-FFIF01 EXP432.1–10.112

fimboot.nvs

fimboot.pcm

fimrex.nvs

fimrex.pcm

FIM4 Cx-PFB401 EXP432.1–10.112

fim4.lcf

fim4app2.pcm

fim4app3.pcm

fim4boot2.pcm

fim4boot3.pcm

FIM8

Cx-PFB801

CC-PFB801 EXP432.1–10.112

fim8.lcf

fim8app2.pcm

fim8boot2.pcm

FTEB TC-FTEB01 EXP432.1–10.112

ftebboot.nvs

ftebboot.pcm

ftebrex.nvs

ftebrex.pcm

IOLIM TC-IOLI01 EXP432.1–10.112

iolimapp.nvs

iolimapp.pcm

iolimboot.nvs

iolimboot.pcm

PI Cx-PPIX01 05.00.02 pi_5_00_02.s28

PIBOOT Cx-PPIX01 05.00.01 piboot_5_00_01.s28

PGM2 Cx-IP0101 EXP432.1–10.112

pgm2.lcf

pgm2app1.pcm

pgm2boot1.pcm

SP CC-PSP401 02.02.01 sp_2_02_01.s28

UIO Cx-PUIO01 04.01.08 uio_5_00_08.s28

UIOBOOT Cx-PUIO01 05.00.01 uioboot_5_00_01.s28



Module Module number Firmware version FileUIO2APP Cx-PUIO31 04.03.31 uio2app_4_03_31.srec

UIOBOOT Cx-PUIO31 04.03.31 uio2boot_4_03_31.srec


111

5 Problems resolved in R432.1

Related topics“Common components resolved PARs” on page 114“Installation and migration resolved PARs” on page 117“Servers and stations resolved PARs” on page 118“Controllers and tools resolved PARs” on page 119

113

5.1 Common components resolved PARs

HMIWeb TPN Details

PAR Function Description

1-3VHOTM0 HMIWeb TPN DetailsRandom filled box appears at the bottom right on thepoints sysdtltps- tablogicdevctl.

1-3X0TY6A HMIWeb TPN DetailsFFOPT parameter is not mapped correctly on theExperion Detail Display sysdtltps-config.

1-43HG8VH HMIWeb TPN DetailsExperion TPS displays need UTF-8 encoding to workwith new IE11 default browser in Experion.

1-4C0F5YB HMIWeb TPN DetailsSome of the parameters are missing in station for SMdigcomp point compare to NW in config tab.

1-4EXAHTB HMIWeb TPN DetailsPV connect and control connect pages are missing instation for regulatory RAMPSOAK point.

1-4EXAHSZ HMIWeb TPN DetailsThere is no drop-down list to select enumerations instation for S1SEGID and S2SEGID parameters.

ETN-Enhanced TNode Virtualization


1-4K7RZOS ETN-Enhanced TNode VirtualizationRandomly observed connection failure status in nodeseven if the connection was fine.

1-4K7RZOJ ETN-Enhanced TNode VirtualizationETN431 with TPN 686 junk character appears duringpersonality change.

Experion TPS Infrastructure


1-3Y4M5NE Experion TPS InfrastructureEST node crashing whenever any continuous alarmprinter fails or runs out of paper.

Experion Station-Native Window

PAR Function Description1-DLHZ3R Experion Station- Native Window Native window is not loading frequently in R400.

Experion Station-Gus Display


1-44E65DH Experion Station-Gus DisplayCustomer requires disabling the functionality, double-click for call TPS faceplates.

5 PROBLEMS RESOLVED IN R432.1


System Management


1-4M5Y0ER System ManagementSES sends incorrect AREAS attribute for source namescontaining an additional period--completed.

1-472WWYZ System ManagementSystem Management Display Application Crashes whenselecting RDM Auxiliary Display.

TPNServer


1-3MCIY4N TPNServerThe system detail displays for an dig.comp point ofFSC/SM (on LCN) does not present the addresses.

1-3X65SSN TPNServer TPNDSS memory leak

1-3XQC809 TPNServer TPN Server crash on Clear CL Message

1-40NPFNL TPNServerNeed to disable default lazy-update of self-definedenumerations on ESVTs.

1-4DFQ6HZ TPNServerSystem mgmt display crashes on adding load on EAPPTpnserver through OPC validator.

1-4FPHRE9 TPNServerSlow response when changing negative OP values upand down.

Signon Manager


1-3YVB3TZ Signon Manager[PCUS] DEE-24267: LCN parallel printer not working -found PCUS, applies to EST as well.

Safeview


1-49WE6GZ SafeViewSafeView windows become unmanageable if closeglobal focused windows those do not have placeholder.

1-48N8XDR SafeViewStation.exe crashing on server failover with SafeviewDual Command Configuration.

1-4SN2EY6 SafeViewOS-triggered maximize/restore from window drag mayput non- draggable window in wrong position.

1-H9INSM SafeView Safeview window at 0,0 may jump to alternate location.

Experion Station-Faceplate


1-3N7YU7U Experion Station- FaceplateProblem with controlling valve (digital composite -momentary) with a single pulse using the mouse.

1-3RN9QUZ Experion Station- FaceplateExperion Logic PM Detail display is different fromNative Window Detail.

1-3RVOHWK Experion Station- FaceplateSwitch faceplate (sysdtltpsswitch_fp) may miss Yes/Noresponse.


115


1-4HC32WE Experion Station- FaceplateAnalgin faceplate focus issues when non running onEST (BW26507).

1-4HP806V Experion Station- FaceplateFaceplates on Server Station (single window flexstation) all show up too small and heavily distorted.

1-4JYVJNP Experion Station- FaceplateIn single-window station, faceplates may not be sizedcorrectly.

1-3XNT8MN Experion Station- Faceplate

Experion TPS DIGOUT faceplate combo box does notwrite to OP for Safety Manager (SM) points (fixupdated for LM points also).

1-4YL169B Experion Station- FaceplateMissing point description on (fpcommon shape)faceplates, e.g., sysdtltpspid_fp

1-501NKF7 Experion Station- FaceplateMissing point description and grey level barbackground.



5.2 Installation and migration resolved PARs

INS-Experion Installer


1-415CMZ9 INS-Experion InstallerInstallation thrown error message as “Call was canceledby the messenger filter".

1-45ZMF57 INS-Experion InstallerSecurity Password storage should not have permissionsto everyone. Only Admin should be able to access.

1-3YQHKB5 INS-Experion InstallerInstallation is getting failed if some service or process isin use.

1-466B2JN INS-Experion InstallerConsolidated patch fails to install on optional featuresand domain controller nodes.

1-4DZZFP9 INS-Experion InstallerR431.2 SM installation gives error at the time of HotfixKB2721341 installation.

1-3RCL0HB INS-Experion InstallerExperion Wrapper logs to write proper information forpatch failures.


117

5.3 Servers and stations resolved PARs

Station


1-529DISL StationLocalizing Experion system displays may cause anapplication error in Station.

1-3TWUIT5 Station

Configuring an alarm icon to show disable state mayshow Errors on Page error when an incorrect parameteris used.

1-5CWSHG1 StationStation does not trigger OnPage script events for contextmenus.

Server - DSA and Point Servers


1-51CCIHV Server - DSA and Point ServersAn old value can be returned to display scripting ifrequested as a 'once- off' read.



5.4 Controllers and tools resolved PARs

C300 Controller

PAR Function Description1-4VDG3K9 C300 Controller C300 controller crashes after a RAM retention restart.

CCL

PAR Function Description1-4IWNP9Z CCL AGA8 Gross Method 1 Heating value clamping issue.

Control Builder

PAR Function Description1-BKPNEX Control Builder FF Method Manager does not work on Function Blocks.

1-4ICRVXJ Control Builder

Modules are listed in unknown order in CB-Containment View at R431.1 (Different from pastreleases).

Control Builder-Chart


1-4P5DISS Control Builder-ChartCB crashes if multiple blocks are deleted continuouslyfrom the CM chart view.

1-3XPDBBS Control Builder-ChartFor several actions the CB chart view jumps to the leftupper corner of the chart.

1-4KV0YFH Control Builder-ChartChart View lose the navigation to selected blocks whenzooming out, zooming in.

1-45MIXBX Control Builder-ChartControl Builder is sluggish when we open Chart Viewand CB is going to Not Responding state.

Control Builder-Fieldbus


1-3TULRYL Control Builder- FieldbusSome parameters are ReadOnly in Project side andEDDL RW, UI issue.

1-3IXNSV8 Control Builder- FieldbusDuring device replacement load the confirmation msgnot displayed properly.

1-TCM7IH Control Builder- FieldbusDeletion of instantiated FF function block is notupdating in device Block instantiation tab.

1-OYUXXR Control Builder- FieldbusDevice replacement is getting failed for the devices withinstantiating function block.

1-4UKMFKH Control Builder- FieldbusControl builder application crash after fieldbus DD"Refresh" operation.


119

Control Builder-Load


1-4ZYR64L Control Builder-LoadPerforming continuous engineering operations on a CMin CB leading to inconsistent behavior.

EHG-Experion Hiway Gateway


1-4SQQKGV EHG-Experion Hiway Gateway[EHG]-Script error is coming while calling detaildisplay configuration tab in station for CB point.

1-3SJR53L EHG-Experion Hiway GatewayRedundant EHG switch-over is not successful in R431.1with minimal or no load.

FF Interface Modules


1-YNBH6L FF Interface ModulesBlock alarm for OOS mode is displayed as¿Unspec¿ under alarms.

FF-Configuration


1-107BU07 FF-ConfigurationEPKS is unable to differentiate the case-sensitive unitslike mpa & Mpa, Mg & mg.

1-2GE4KYB FF-ConfigurationDevice Parameters DEV_CFG_XX is providing wrongvalue in CB.

1-3FIJTVH FF-ConfigurationHuman factor issues observed in DD View of ControlBuilder.

1-11X2YX7 FF-ConfigurationBlocks cannot be instantiated to device from lib iftemplate is renamed.

FF-DDImport, HIST


1-39JLB8F FF-DDImport, HISTParameter Read Write Issues in Control Builder for FFDevices.

Fieldbus Interface Module


1-4BGDX0T Fieldbus Interface ModuleShort disruption of Fieldbus segment communicationcauses Metso positioner output to go to 0%.

Fieldbus Library Manager


1-Q3YACV Fieldbus Library ManagerImages in DD shown in EDD View in CB are comingwith improper resolution, See description




1-Q407YH Fieldbus Library ManagerIn Method manager, scroll bar is not available & Getstring value built- in method is not supported.

I/O-Series C


1-4T1S865 I/O-Series CUIO module hardfail with hardfail status "Dmtimout"during continuous power cycle.

IXP-Import Export


1-4CCCY9D IXP-Import ExportTPSR error get throw away as part of setvalue. This is acustomer visible problem.

1-4C30GKB IXP-Import Export Import of channel level UDT results in db corruption.

NTools


1-51PQ3OH NToolsRepetitive entry window appears when launchingNTools.

SE-Sys Engr


1-3JYAO48 SE-Sys EngrFIM data caching issue, because of which many DTMsdoesn't work properly.

SIM-FFD


1-44SAZZ5 SIM-FFDSIMFIM crash while accessing property page for FFblock.

Turbine Control


1-4M3R587 Turbine ControlThe issue reported by CM (Welco): The TC-SVPmodules were failing in Stress test, During Low Margin.


121

6 Troubleshooting Instructions

When the Station or the Premium Access Client or the Collaboration Station applications fails to connect, thefollowing message appears:

Unable to Connect. Attempt to reconnect

Diagnostic checkPing the server to which the client attempts to connect and check with the system administrator to find out ifICMP traffic has been disabled.

CauseIf ICMP is disabled, the application will not be able to connect.

Solution• Make the following setting in the station.ini file for direct Station connection.

[station]

DisablePingRequest=1

• Make the following setting in C:\Program Files (X86)\Honeywell\Experion PKS\Client\System\R400\default.stn or an equivalent CIP file path of eServer for Premium access client.

[station]


• Make the following setting in C:\ProgramData\Honeywell\Experion PKS\Client\Station\CollabStation.stn for Collaboration Station.

[station]


123

6 TROUBLESHOOTING INSTRUCTIONS


7 Special considerations in R432.2

Related topics“Running eServer on systems with Internet Explorer 11” on page 126“Microsoft hotfixes” on page 127“Alarm Paging” on page 128“Patch Considerations in R432.2” on page 129

125

7.1 Running eServer on systems with Internet Explorer 11For eServer Premium Access clients to work as intended on Internet Explorer 11, perform the following settingsmanually after installing the eServer.

To run the eServer on systems with Internet Explorer 111 Close all instances of Internet Explorer and start a new instance with the administrator rights.2 To add the eServer URL to the compatibility view, perform the following steps.

a On the Tools menu, click Compatibility View Settings.The Compatibility View Settings dialog box appears.

b Under Add this website, enter the URL of the eServer node.c Click Add.d Click Close.

3 To enable the BHO Add-on, perform the following steps.a On the Tools menu, click Manage add-ons.b Enable Honeywell BHO in the Manage add-ons dialog box.c Click Close.

4 Restart Internet Explorer.

7 SPECIAL CONSIDERATIONS IN R432.2


7.2 Microsoft hotfixesMicrosoft hotfixes fail in multiple steps during installation on systems that are part of a domain. Perform thefollowing steps if an error occurs due to Microsoft hotfixes failure.

To run the installation on systems that are part of a domain1 Acknowledge the error which is displayed to stop the installation.2 Install all hotfixes (msu files) available in the path

<ESIS>\D_EID\Packages\Microsoft\IE11\ and

<ESIS>\D_EID\Packages\Microsoft\Hotfix\ manually.3 After the installation, reboot the system.4 Browse <Software Path>>\Honeywell\Experion PKS\Install\ and right-click hwinstallsequencer.exe and

choose Run as administrator.


127

7.3 Alarm PagingFor security reasons, when setting up Experion alarm pager to page alarms/alerts using email, the SMTP servershould not be hosted on the Experion Server Computer. SMTP relay functions should be hosted on a separateserver node



7.4 Patch Considerations in R432.2This point release affects some specific functionality of Experion PKS and other products that integrate withExperion PKS. If any of the items below are used on your system this section highlights additional preparationrequired before you install this patch. If you do not use any of these features, you will not be affected and youcan disregard this section.

• DSA Alarm and Event Report• Only when reporting from servers other than your local server• DSA Advanced Security• IEC60870 Interface• Uniformance PHD and history tag synching• Integration with other products• Profit Blending and Movement (PBM) or Blending and Movement Automation (BMA)• ACM

7.4.1 DSA – Alarm and Event ReportIf you use the DSA Alarm and Event Report to query other systems, you will need to ensure you that thatsystem is at the appropriate patch level. Use the following table to determine the minimum patch level.

Installing patches to the subscribing servers first will minimize disruption of DSA Alarm Event Report querieswhilst patching the servers in your system.

Release Patch LevelR310.3 ExperionPKS.R310.3.Server.Patch687.PAR1-6GU86WN

R400.8 Experion PKS R400.8 Server Patch 822




R431.4 Experion PKS R431.4


R500.1 Experion PKS R500.1

7.4.2 DSA Advanced SecurityIf you are installing this point release on a server that uses DSA Advanced Security, either for publishing orsubscribing, it was previously documented as a recommendation that Windows accounts being used were addedto a Windows local group called ‘Remote Servers’. This is now a compulsory requirement and DSA AdvancedSecurity connections will fail after installation of the point release if they are not in this group.

Ensure that this procedure is followed for seamless DSA Advanced Security connectivity during patching:

1. Prior to patch installation, ensure all Windows accounts used for DSA Advanced Security (both forpublishing and subscribing to this server) are added to a local Windows group called ’Remote Servers’.Perform this step on both servers if they are redundant. See ‘Creating a Remote Servers group’ in theExperion Server and Client Configuration Guide for more information. If created after DSA setup systemwill need to be restarted.

2. If connecting via DSA to a R410 system, the R410 system must be at R410.2 or later.3. Install this patch on the servers as per this SCN.


129

Note, this does not affect users of standard DSA security.

7.4.3 IEC60870 InterfaceThis point release is not compatible with the standard R431 version of the IEC60870 point server and it shouldnot be installed if an IEC60870 interface is being used. Please delay installation of this point release untilapplication of an IEC60870 patch listed as being compatible with:

PAR 1-6N0F0UR Robustness improvements to DSA and console stations

7.4.4 Uniformance PHD and history tag synchingEnsure you follow Section Installing PHD point server patch on PHD server to update your PHD system.

If you’re using Uniformance PHD’s optional Experion PKS tag synching service, you need to ensure theExperion PKS Server is correctly configured.

When you first installed the tag synching service, you had the opportunity to set the account to be used toconnect to the Experion PKS system. This setting is called “Experion User Account” and can be found in the“Configure User Accounts” tree on the “Final Steps” tab of the PHD installation.

To check what account you’ve used, or to change this account:

• Launch the Uniformance System Console• Connect to your Uniformance PHD server and log in• Select the “Uniformance PHD Tag Synchronization Server” item from the tree• Right click on the item and select “Properties”• Select the “Tag Synchronization Users” tab• Check or change the “Experion Client User Account”

It’s important that the account you used in the above configuration:

• If using a non-domain account, then an identical account (account name and password) must exist on theExperion PKS servers

• If using a domain account, then the PHD server and the Experion PKS servers are in the same domain• The account has been added to the “Local Servers” group on the Experion PKS servers

If a non-domain account is used, then the PHD tag sync service will also need to run under this account:

• Launch the Windows services applet (services.msc)• Navigate to the service “Uniformance PHD Tag Synchronization Server”• Change the “Log On” to the non-domain account (entering account name and password)• If prompted as to whether to grant the “run as a service” privilege to the account, grant this privilege• The account should be added to the local “Product Administrators” group• Stop and restart the “Uniformance PHD Tag Synchronization Server” service

7.4.5 Integration with other products

Profit Blending and Movement (PBM) or Blending and Movement Automation (BMA)Before applying this point release, customers who have implemented Profit Blending and Movement (PBM)or Blending and Movement Automation (BMA), must ensure that [a] the BMA / PBM point server dated 14-Jan-2016 or later (file version 4.3.2.14 or later) is running on their system or, alternatively, [b] the BMA /PBM software is at the following point release level or higher:

• PBM R500.1



• PBM R431.2• BMA R430.3

ACMThis point release is not compatible with the standard R431 version of the ACM point server and it shouldnot be installed if an ACM point server interface is being used. Please delay installation of this point releaseuntil application of an ACM patch listed as being compatible with:

PAR 1-6N0F0UR Robustness improvements to DSA and console stations


131

8 Support and other contacts

Related topics“Documentation feedback” on page 134“How to report security vulnerability?” on page 135“GTAC Support” on page 136

133

8.1 Documentation feedbackYou can find the most up-to-date documents on the Honeywell Process Solutions support website at: “http://www.honeywellprocess.com/support”

If you have comments about Honeywell Process Solutions documentation, send your feedback to: “[email protected]”

Use this email address to provide feedback, or to report errors and omissions in the documentation. Forimmediate help with a technical problem, contact your local Honeywell Process Solutions Customer ContactCenter (CCC) or Honeywell Technical Assistance Center (TAC) listed in the “Support and other contacts”section of this document.

8 SUPPORT AND OTHER CONTACTS


http://www.honeywellprocess.com/support


8.2 How to report security vulnerability?For the purpose of submission, a security vulnerability is defined as a software defect or weakness that can beexploited to reduce the operational or security capabilities of the software.

IHoneywell investigates all reports of security vulnerabilities affecting Honeywell products and services.

To report a potential security vulnerability against any Honeywell product, please follow the instructions at: “https://honeywell.com/pages/vulnerabilityreporting.aspx”

Submit the requested information to Honeywell using one of the following methods:

• Send an email to “[email protected]”.

or• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical

Assistance Center (TAC).


135

https://honeywell.com/Pages/vulnerabilityreporting.aspx

8.3 GTAC Support

Related topics“Subscribe for Automated Email Alerts:” on page 136“Further support required?” on page 136“Training classes” on page 136

8.3.1 Subscribe for Automated Email Alerts:Honeywell advises all users to subscribe for alerts on “HoneywellProcess.com” to receive an email alert everytime a new Notification or patch is posted. A tutorial is available (“Learn to Subscribe” link at the bottom righthand side of any page of “HoneywellProcess.com”) to help guide you through the subscription process and totailor subscriptions to be appropriate to your system and needs. In addition you may also Subscribe to theGTAC Knowledge Sharing Mails which provide users on a regular basis with valuable tips & tricks, lessonslearned and recommendations.

8.3.2 Further support required?If you have any questions concerning this notification, please contact your local Honeywell office or the GlobalTechnical Assistance Centre (GTAC). Visit HoneywellProcess.Com and select “Contact Us” for country-specific Customer Contact Numbers. After you log on to “HoneywellProcess.Com” you may also Search ourKnowledge Base or Submit a Support Request to request help.

8.3.3 Training classesHoneywell holds technical training classes on Experion PKS. These classes are taught by experts in the field ofprocess control systems. For more information about these classes, contact your Honeywell representative, orsee “http://www.automationcollege.com”.



http://www.automationcollege.com

9 Notices

TrademarksExperion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of HoneywellInternational, Inc.

OneWireless™ is a trademark of Honeywell International, Inc.

TrademarksExperion®, PlantScape®, and SafeBrowse® are registered trademarks of Honeywell International, Inc.

TrademarksExperion® and SafeBrowse® are registered trademarks of Honeywell International, Inc.

PlantCruise™ is a trademark of Honeywell International, Inc.

Other trademarksMicrosoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in theUnited States and/or other countries.

Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intentionof trademark infringement.

Third-party licensesThis product may contain or be derived from materials, including software, of third parties. The third partymaterials may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses,notices, restrictions and obligations, if any, may be found in the materials accompanying the product, in thedocuments or files accompanying such third party materials, in a file named third_party_licenses on the mediacontaining the product, or at http://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedbackYou can find the most up-to-date documents on the Honeywell Process Solutions support website at:

http://www.honeywellprocess.com/supportIf you have comments about Honeywell Process Solutions documentation, send your feedback to:

[email protected] this email address to provide feedback, or to report errors and omissions in the documentation. Forimmediate help with a technical problem, contact your local Honeywell Process Solutions Customer ContactCenter (CCC) or Honeywell Technical Assistance Center (TAC).

How to report a security vulnerabilityFor the purpose of submission, a security vulnerability is defined as a software defect or weakness that can beexploited to reduce the operational or security capabilities of the software.

137

http://www.honeywell.com/ps/thirdpartylicenses


mailto:[email protected]

Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.

To report a potential security vulnerability against any Honeywell product, please follow the instructions at:

https://honeywell.com/pages/vulnerabilityreporting.aspx

Submit the requested information to Honeywell using one of the following methods:

• Send an email to [email protected].

or• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical

Assistance Center (TAC) listed in the “Support” section of this document.

SupportFor support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find yourlocal CCC visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx.

Training classesHoneywell holds technical training classes about Experion PKSExperion HSExperion LXPlantCruise byExperion. These classes are taught by experts in the field of process control systems. For more informationabout these classes, contact your Honeywell representative, or see http://www.automationcollege.com.

9 NOTICES


https://honeywell.com/Pages/vulnerabilityreporting.aspx

mailto:[email protected]

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

http://www.automationcollege.com

r432.2 software change notice - honeywell › library › support › ... · 2.2 new features and...

Documents