R501.1 Software Change Notice - Balibago Update file/Experion...Experion PKS Support Media Software Change Notice in the Search box. 3 Click Search. The All Support Search Results

Experion PKSR501.1 Software Change Notice

EPDOC-X166-en-5011ANovember 2017

Release 501.1

Document Release Issue DateEPDOC-X166-en-5011A 501.1 0 November 2017

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 2017 - Honeywell International Sàrl

2 www.honeywell.com

Contents

1 About this document ............................................................................................................................. 52 Introduction ............................................................................................................................................ 7

2.1 Check for updates on Honeywell Process Solutions website ............................................................................. 82.2 Who must read this document? ......................................................................................................................... 102.3 Change impact .................................................................................................................................................. 11

2.3.1 Control change impact ....................................................................................................................... 112.3.2 Operational change impact ................................................................................................................ 112.3.3 Infrastructural change impact ............................................................................................................ 12

3 Contents of this release ....................................................................................................................... 133.1 Contents of Experion R501.1 software media kit ............................................................................................. 143.2 Experion R501.1 PDF Collection ..................................................................................................................... 15

3.2.1 Contents of Experion R501.1 System Documentation PDF Collection ............................................ 153.2.2 Contents of Experion R501.1 SCN, Installation, and Migration PDF Collection ............................. 20

4 Getting started ...................................................................................................................................... 214.1 About Experion installation and migration documents .................................................................................... 224.2 Supported server/client migration paths ........................................................................................................... 234.3 Supported controller migration paths ............................................................................................................... 24

5 Supported software / hardware / firmware ........................................................................................ 275.1 Platform hardware ............................................................................................................................................ 285.2 Antivirus software ............................................................................................................................................ 295.3 Microsoft Office compatibility ......................................................................................................................... 305.4 Microsoft security updates ................................................................................................................................ 315.5 Windows operating system ............................................................................................................................... 325.6 Experion Backup and Restore .......................................................................................................................... 335.7 Application Whitelisting ................................................................................................................................... 34

6 New features and enhancements ....................................................................................................... 356.1 Experion-TPS integration ................................................................................................................................. 36

6.1.1 Experion Local Control Network (ELCN) ........................................................................................ 366.2 Smart Test and Automated Commissioning (STAC) Enhancements ............................................................... 396.3 SCADA enhancements ..................................................................................................................................... 446.4 Integration of MeterSuite .................................................................................................................................. 456.5 ControlEdge RTU Supports Foundation Fieldbus ............................................................................................ 466.6 Series C Mark II Phase 3 enhancements ........................................................................................................... 476.7 Collaboration Station enhancements ................................................................................................................ 486.8 System Management for Experion LCN .......................................................................................................... 496.9 Automated Device Commissioning (ADC) Device Rename ........................................................................... 506.10 HART Point Parameter Access ....................................................................................................................... 536.11 Long Point Names for Process Points ............................................................................................................. 566.12 Experion software installation enhancements ................................................................................................ 586.13 UIS enhancements .......................................................................................................................................... 596.14 System configuration enhancements .............................................................................................................. 656.15 SmartLine Transmitter Point Detail Displays & Faceplates ........................................................................... 66

7 Problems resolved ............................................................................................................................... 71

3

7.1 Common components ....................................................................................................................................... 727.2 Installation and Migration ................................................................................................................................. 737.3 Servers and Stations .......................................................................................................................................... 747.4 Controllers and Tools ........................................................................................................................................ 75

8 Special considerations ........................................................................................................................ 778.1 SmartLine Transmitter Faceplates .................................................................................................................... 788.2 ELCN Bridge and Appliance Node Migration (1-8MXCD67) ........................................................................ 798.3 Control Firewall 9 (CF9) Connections (1-8G8SN4J) ....................................................................................... 808.4 Migration from Experion R3xx to R501 .......................................................................................................... 818.5 RSLinx Classic software and Experion R501 (1-86VLEH5 and 1-8H5CPBD) .............................................. 828.6 Qualified/Supported FTE switches for use with Experion LCN ...................................................................... 83

9 Known issues ....................................................................................................................................... 859.1 Common components ....................................................................................................................................... 869.2 Installation and Migration ................................................................................................................................. 939.3 Servers and Stations .......................................................................................................................................... 999.4 Controllers and Tools ...................................................................................................................................... 1019.5 PDF Documentation ...................................................................................................................................... 120

10 Honeywell software components and versions ............................................................................ 12110.1 Common component versions ...................................................................................................................... 12210.2 Controllers and tools version ........................................................................................................................ 13010.3 Server and client versions ............................................................................................................................. 13210.4 TPS Software Component Versions .............................................................................................................. 13310.5 Compatibility with TPN releases .................................................................................................................. 134

11 Honeywell-qualified third-party software component version ..................................................... 13711.1 Honeywell-qualified third-party embedded software component versions .................................................. 13811.2 Honeywell-qualified third-party software component versions ................................................................... 140

12 Support for optional SCADA interfaces ......................................................................................... 14113 Notices .............................................................................................................................................. 149

CONTENTS

4 www.honeywell.com

1 About this document

This Software Change Notice contains information for all the users of Experion R501.1. This SCN must be readprior to installing and managing the system. The document describes the new features and enhancementsintroduced with the R501.1 release. Additionally, it contains resolved PARs, issues, special considerations, andlast minute documentation updates.

Revision history

Revision Date DescriptionA November 2017 Initial release of the document.

5

1 ABOUT THIS DOCUMENT

6 www.honeywell.com

2 Introduction

The Experion Process Knowledge System provides a single, integrated platform encompassing continuous andbatch control, safety, security, electrical, SCADA, and asset management. With Experion R501.1, Experionintroduces new features and enhancements that improve security, reliability, and performance.

Following are some of the new features and enhancements:

• Experion TPS integration (Experion LCN)• Alarm and event management (such as, enhancement to the toolbar, summary value format, console and

system alarms, and audible alarm for Critical alarms and Alarm Help tab are added).• Smart Test and Automated Commissioning (STAC) Enhancements• SCADA enhancements• Integration of MeterSuite• ControlEdge RTU Supports Foundation Fieldbus• Series C Mark II Phase 3 enhancements• System management (such as, enhancements to the dashboard displays for ELCN).• Collaboration Station enhancements• Automated Device Commissioning (ADC) Device Rename• HART Point Parameter Access• Long Point Names for Process Points• Experion software installation enhancements• UIS enhancements• System configuration enhancements• SmartLine Transmitter Point Detail Displays & Faceplates

7

2.1 Check for updates on Honeywell Process Solutions websiteThe Honeywell Process Solutions website, http://www.honeywellprocess.com contains the most up-to-datesoftware updates, documentation, and recommended antivirus updates. You can find the latest version of thisSCN on Honeywell Process Solutions website.

To access the Honeywell Process Solutions website1 In a web browser, type the following URL.

https://www.honeywellprocess.com/support

The SUPPORT page appears, and the Search Knowledge Base tab is selected by default.2 Select Click Here to Login in the top-right corner of the page.

The home page appears.3 If you are a new user, register at this website. Click Register, and follow the on-screen instructions.4 If you are already registered, type your Account Login user name and password, and click Login.

Your account name appears in the top-right of the page.

To download documents, security updates, or antivirus notifications1 Click Latest Documentation as shown in the following image.

The All Support Documentation page appears as a new page.2 In the Search box, type the name of the required document, security update, or antivirus notification.

For example, to download an SCN, type Experion PKS General Release Software Change Notice orExperion PKS Support Media Software Change Notice in the Search box.

3 Click Search.The All Support Search Results page appears with the search results.

4 In the left pane, use the Search Result Filters to further filter the document, security update, or antivirusnotification. For example, if you are locating a Software Change Notice:a Under Document Type, click Software Change Notice.b Under Product Release, click the required Experion product release.

2 INTRODUCTION

8 www.honeywell.com

http://www.honeywellprocess.com


https://www.honeywellprocess.com/support

5 Click the document, security update, or antivirus notification link to open it.

2 INTRODUCTION

9

2.2 Who must read this document?The information in this the Experion Software Change Notice is useful if you are planning to install, migrate, orconfigure the Experion R501.x system. See the SCN to understand the overall product, releaseinteroperabilities, system dependencies, problem resolutions, known issues, and special considerations. It mustbe readily available for reference at any stage of Experion system setup.

2 INTRODUCTION

10 www.honeywell.com

2.3 Change impact

Related topics“Control change impact” on page 11“Operational change impact” on page 11“Infrastructural change impact” on page 12

2.3.1 Control change impactPAR 1-4D660E5DescriptionCompleted PHASE blocks should not re-execute after restarting RCM from the HELD state.

ImpactWhen an RCM is restarted, the PHASE blocks in RCM which are completed (Phase blocks in Active/ActiveComplete State) will not re-execute. This behavior is applicable only in a scenario when RCM returnsfrom different handler (HOLD > RESTART). PHASE blocks behavior during normal execution and singleSTEP execution will not be affected with this change. Also, this change does not impact STEP blocks.

2.3.2 Operational change impactPAR 1-PYDBC1DescriptionThe excel.exe process may continue to run in Task Manager under the Station login account even afternavigating away from an opened Microsoft Excel Report in Station.

ImpactIn Experion R501, when a Microsoft Excel report is displayed in Station, the associated excel.exe process doesnot terminate after navigating to a different Station display and the associated Microsoft Excel spreadsheet isnot closed. This can prevent future instances of the report from generating correctly. Honeywell is working thisissue with Microsoft. Note that this affects Microsoft Excel reports displayed in Station only. Periodic MicrosoftExcel reports are not affected by this problem.

PAR 1-6FBJ8O3DescriptionSupport for Evans AlarmLinc alarm lights controller with Experion PKS.

ImpactThe Evans AlarmLinc controller is now supported on Experion Orion consoles to drive the Alarm Light. Todetermine the type of controller, visually inspect the alarm light controller, typically be located in the Equipmenttray, this will be labelled ‘EVANS AlarmLinc’.

If the Alarm Lights controller delivered with Experion Orion console is ENTTEC Pixie Driver, then there is noadditional configuration required. If the Experion Orion console includes the new EVANS AlarmLinccontroller, follow the steps below to enable this controller:

Using the controller on a physical R500 console node: Edit the station connection properties file (.stn) and addthe following section:

[Station]

AlarmDeviceType = 1

2 INTRODUCTION

11

Using the controller on a WYSE node: Ensure that the station connection file DOES NOT have any entry forAlarmDeviceType. To make changes permanent, log on to the Dell Wyse Z90 Thin Client with an Administratoraccount, then on the desktop, double-click the red FBWF disable icon. This will disable File Based Write Filterwhich will preserve following changes.

On the WYSE node, manually add the registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE \Honeywell\Station]

"AlarmDeviceType"=dword:00000001

Using WYSE TCX Client configuration utility, set EVANS controller to be used as a local device.

2.3.3 Infrastructural change impactNot Applicable.

2 INTRODUCTION


3 Contents of this release

Related topics“Contents of Experion R501.1 software media kit” on page 14“Experion R501.1 PDF Collection” on page 15

13

3.1 Contents of Experion R501.1 software media kitThe Experion R501.1 software media kit (EP-PKS501) consists of following two DVD kits and ExperionRead Me First Instructions.

• Experion R501 Multi DVD Kit-1 (Part number 51156197)• Experion R501 Multi DVD Kit-2 (Part number 51156198)• Experion Read Me First Instructions (Part Number 51154497)

3 CONTENTS OF THIS RELEASE


3.2 Experion R501.1 PDF Collection

AttentionExperion user documentation is available on the Honeywell Process Solutions website (http://www.honeywellprocess.com/), and the PDF Collection. The Honeywell Process Solutions website contains the latestuser documentation, including document revisions after the Experion R501.1 release. To ensure that you are accessingthe latest documentation, use the Honeywell Process Solutions website.

The PDF Collection media contains the following two installer files and the Adobe Reader folder.

• Experion_PKS_R501.1_SCN_Installation_Migration_PDF_Installer.msi

This Windows Installer Package installs the SCN, installation, and migration documentation.• Experion_PKS_R501.1_PDF_Collection_Installer.msi

This Windows Installer Package installs all other user documentation, such as, configuration, operations, andtroubleshooting-related documents.

• Adobe Reader folder

This folder includes the Adobe Reader (11.0.20 version) application.

Related topics“Contents of Experion R501.1 System Documentation PDF Collection” on page 15“Contents of Experion R501.1 SCN, Installation, and Migration PDF Collection” on page 20

3.2.1 Contents of Experion R501.1 System Documentation PDF CollectionThe following table lists the Experion user documentation contained in the System Documentation PDFCollection.

Document name Document IDABB TotalFlow Interface Reference EPDOC-X340-en-501A

Allen-Bradley Drive Interface through ControlNet Reference EPDOC-XXX2-en-501A

Allen-Bradley Interface Reference EPDOC-XXX3-en-501A

Application Control Environment User’s Guide EPDOC-XXX4-en-501A

Application Control Environment Cutover Solution Guide EPDOC-X405-en-501A

Application Development Guide EPDOC-XXX5-en-501A

ASEA Interface Reference EPDOC-XXX6-en-501A

Batch Implementation Guide EPDOC-X161-en-501A

Batch Overview and Planning Guide EPDOC-XXX7-en-501A

Bristol Babcock Interface Reference EPDOC-XXX8-en-501A

Bristol Babcock OpenBSI Interface Reference EPDOC-XXX9-en-501A

C200/C200E Troubleshooting and Maintenance Guide EPDOC-XX10-en-501A

C300 Controller User's Guide EPDOC-XX11-en-501A

CL Server User's Guide EPDOC-XX12-en-501A

Collaboration Station User's Guide EPDOC-X245-en-501A

Configuration Studio Overview Guide EPDOC-X113-en-501A

Configuration Utility User's Guide EPDOC-XX14-en-501A

Control Builder Components Reference EPDOC-XX15-en-501A


15

Document name Document IDControl Builder Components Theory EPDOC-XX16-en-501A

Control Builder Error Codes Reference EPDOC-XX17-en-501A

Control Builder Parameter Reference EPDOC-XX18-en-501A

Control Building User's Guide EPDOC-XX19-en-501A

Control Component Library (CCL) Reference EPDOC-X152-en-501A

Control Firewall User's Guide EPDOC-XX20-en-501A

Control Hardware Installation Guide EPDOC-XX21-en-501A

Control Hardware Planning Guide EPDOC-XX23-en-501A

Controller Hardware Notifications Theory EPDOC-XX22-en-501A

ControlNet Fiber Optic Implementation Guide EPDOC-XX24-en-501A

ControlNet Installation Guide EPDOC-XX25-en-501A

Custom Algorithm Block and Custom Data Block User's Guide EPDOC-XX26-en-501A

DeviceNet Interface Implementation Guide EPDOC-XX27-en-501A

Diagnostic Studio User's Guide ESDOC-XX28-en-2401A

Dictionary EPDOC-XX29-en-501A

DNP3 Interface Reference EPDOC-XX31-en-501A

Engineering Data Builder User’s Guide EPDOC-X417-en-501A

Enron Modbus Interface Reference EPDOC-X233-en-501A

Enterprise Model Builder User's Guide EPDOC-XX32-en-501A

Ethernet Implementation Guide EPDOC-XX34-en-501A

Ethernet Interface Module User’s Guide EPDOC-X406-en-501A

Ethernet IP Implementation Guide EPDOC-X399-en-501A

ETN Quick Start Guide EPDOC-X329-en-501A

Experion Cluster Communication for ACE Interface Reference EPDOC-XX13-en-501A

Experion LCN Overview and Implementation Guide EPDOC-X478-en-501A

Experion LCN Quick Start Guide EPDOC-X480-en-501A

Experion Legacy IO Link Module Parameter Reference Dictionary EPDOC-X151-en-500

Experion Mobile Access User's Guide EPDOC-XX72-en-501A

Experion Node Configuration Tool User’s Guide EPDOC-X427-en-501A

Experion On-Process Migration in Virtualized Environment Guide EPDOC-X328-en-5001A

EXTIO 2 Remote Peripheral Solutions Installation Instructions EP-DPCX24

Fault Tolerant Ethernet Bridge Implementation Guide EPDOC-XX35-en-501A

Fault Tolerant Ethernet Installation and Service Guide EPDOC-XX36-en-501A

Fault Tolerant Ethernet Overview and Implementation Guide EPDOC-XX37-en-501A

Fault Tolerant Ethernet Status Server and Auxiliary Display User's Guide EPDOC-XX38-en-501A

Fisher ROC Interface Reference EPDOC-X341-en-501A

FMC 722 on ACE Configuration Guide EPDOC-X332-en-501A

FMC 722 on ACE Parameter Reference EPDOC X333-en-501A

Operational Application Suite Configuration Guide EPDOC-X264-en-501A

Operational Application Suite User's Guide EPDOC-X265-en-501A

GE Fanuc Series 90 Interface Reference EPDOC-XX39-en-501A



Document name Document IDGEC GEM80 Interface Reference EPDOC-XX40-en-501A

Getting Started with Experion Software Guide EPDOC-X112-en-501A

Guidelines for Replacing Hiway Boxes with LCN-connected C300Emulations

EPDOC-X268-en-501A

GUS Basic Script User's Guide EPDOC-XX41-en-501A

GUS Basic Scripting Language Reference EPDOC-XX42-en-501A

GUS Display Authoring Tutorial EPDOC-XX43-en-501A

GUS Display Builder User's Guide EPDOC-XX44-en-501A

GUS Display Scripting User's Guide EPDOC-XX45-en-501A

GUS Display Search Tool User's Guide EPDOC-XX46-en-501A

GUS Display Translator User's Guide EPDOC-XX47-en-501A

GUS Faceplate, Alarm, and Message Scripting User's Guide EPDOC-XX48-en-501A

GUS Remote Display User's Guide EPDOC-XX49-en-501A

Hardware and Point Build Reference EPDOC-XX50-en-501A

HART IO Implementation Guide EPDOC-XX51-en-501A

HCI/OPC Data Access User's Guide EPDOC-XX52-en-501A

Hitachi Interface Reference EPDOC-XX53-en-501A

Hiway Slot Emulation Creator User Guide EPDOC-X267-en-500

HMIWeb Display Building Guide EPDOC-XX54-en-501A

HMIWeb Object Specification EPDOC-X174-en-501A

HMIWeb Solution Pack Operator and Alarm Philosophy EPDOC-X173-en-501A

Honeywell DPR Interface Reference EPDOC-XX55-en-501A

Honeywell FSC Integration Reference EPDOC-XX56-en-501A

Honeywell LCS620 Interface Reference EPDOC-XX57-en-501A

Honeywell Modbus TCP Firewall User's Guide EPDOC-X162-en-501A

Honeywell Series 9000 Integration Reference EPDOC-XX60-en-501A

Honeywell TDC 3000 Data Hiway Interface Reference EPDOC-XX61-en-501A

Honeywell Turbine Control Solution Parameter Reference EPDOC-XX62-en-501A

Honeywell UDC Integration Reference EPDOC-XX63-en-501A

Honeywell Universal Modbus Interface Reference EPDOC-XX64-en-501A

HP ProLiant DL360P Gen8 Honeywell Server Planning Installation andService Guide

HWDOC-X330-en

IEC 61850 Client Interface SCADA Configuration Guide EPDOC-X412-en-501A

IEC 60870 SCADA Configuration Reference Guide EPDOC-X358-en-501A

IEC 60870 SCADA Parameter Reference Guide EPDOC-X376-en-501A

IEC 61850 SCADA Configuration Reference Guide EPDOC-X375-en-501A

Integrated Experion TPS User's Guide EPDOC-XX66-en-501A

LCNP Status User Guide EPDOC-XX67-en-501A

LLMUX2 TC and RTD FTAs User Guide EPDOC-XX68-en-501A

MasterLogic Experion Integration User’s Guide EPDOC-X365-en-501A

METTLER TOLEDO Integration Reference EPDOCXX69-en-501A


17

Document name Document IDML200 CPU and SoftMaster User’s Guide EPDOC-X367-en-501A

ML200 Installation and Commissioning Guide EPDOC-X366-en-501A

Modbus Interface Reference EPDOC-XX71-en-501A

Moore Mycro Interface Reference EPDOC-XX73-en-501A

Native Windows User's Guide EPDOC-XX74-en-501A

Network and Security Planning Guide EPDOC-XX75-en-501A

OEP IKB and Touch Screen Device Adapters Installation Instructions EP-DPCXX3

Omni Interface Reference EPDOC-XX77-en-501A

OPC Client Interface Reference EPDOC-XX78-en-501A

OPC Gateway for ACE Interface Reference EPDOC-XX79-en-501A

Operator's Guide EPDOC-XX80-en-501A

Operator Touch Panel Installation, Configuration, and Operation Guide EPDOC-X356-en-501A

Overview EPDOC-XX81-en-501A

Parallel Operation Keyboard User’s Guide EPDOC-XX82-en-501A

Parallel Redundancy Protocol User's Guide EPDOC-X410-en-501A

Parameter Definition Editor Reference EPDOC-XX83-en-501A

Peer Control Data Interface Implementation Guide EPDOC-XX84-en-501A

PM IO Hardware Troubleshooting and Maintenance Guide EPDOC-XX85-en-501A

Procedure and Sequence Custom Display Building Guide EPDOC-XX86-en-501A

PROFIBUS Gateway Module Parameter Reference EPDOC-XX87-en-501A

PROFIBUS Gateway Module User’s Guide EPDOC-XX88-en-501A

PROFIBUS Interface Implementation Guide EPDOC-XX89-en-501A

Profit Controller User’s Guide EPDOC-X463-en-501A

Qualification and Version Control User’s Guide EPDOC-XX90-en-501A

Quick Builder User’s Guide EPDOC-XX91-en-500

R320 Honeywell Server Planning Installation Service Guide HWDOC-X238-en

R5500 Honeywell Workstation Planning Installation and Service Guide EP-DPCX25

R7610 Honeywell Workstation Planning Installation Service Guide HWDOC-X273-en

R7910XL Honeywell Workstation Planning Installation Service Guide HWDOC-X369-en

Rail IO Series A Implementation Guide EPDOC-X114-en-501A

Rail IO Series H Implementation Guide EPDOC-X115-en-501A

Redirection Manager Users Guide EPDOC-X116-en-501A

Redundant Power Supply Installation Guide EPDOC-X117-en-501A

Safety Manager Integration Guide EPDOC-X119-en-501A

SafeView User’s Guide EPDOC-X120-en-501A

Search Utility User’s Guide EPDOC-X121-en-501A

Secure Communications User’s Guide EPDOC-X270-en-501A

Sequential Control User’s Guide EPDOC-X122-en-501A

Serial Interface Module Implementation Guide EPDOC-X123-en-501A

Series A Fieldbus Interface Module User’s Guide EPDOC-X124-en-501A

Series C Fieldbus Interface Module User’s Guide EPDOC-X125-en-501A



Document name Document IDSeries C IEC 61850 Interface Module User’s Guide EPDOC-X374-en-501A

Series C IO User’s Guide EPDOC-X126-en-501A

Server and Client Configuration Guide EPDOC-X127-en-501A

Server and Client Planning Guide EPDOC-X128-en-501A

Server Scripting Reference EPDOC-X129-en-501A

Siemens S7 Interface Reference EPDOC-X130-en-501A

SIM ACE User’s Guide EPDOC-X131-en-501A

SIM C300 User’s Guide EPDOC-X133-en-501A

SIM-C200E Implementation Guide EPDOC-X132-en-501A

SIM-FFD User Guide EPDOC-X134-en-501A

Site Planning Guide EPDOC-X135-en-501A

Spirit IT FlowX Interface Reference EPDOC-X297-en-501A

Startup and Shutdown EPDOC-X137-en-501A

Supplementary Installation Tasks Guide EPDOC-X138-en-501A

Switch Configuration Tool User’s Guide EPDOC-X246-en-501A

System Administration Guide EPDOC-X139-en-501A

System Alarms Reference EPDOC-X140-en-501A

System Management Configuration Guide EPDOC-X141-en-501A

System Management Operations Guide EPDOC-X142-en-501A

T130 Honeywell Server Planning Installation Service Guide HWDOC-X450-en


R330XL Honeywell Server Planning Installation Service Guide HWDOC-X452-en

R430 Honeywell Server Planning Installation Service Guide HWDOC-X453-en


T3600XL Honeywell Workstation Planning Installation Service Guide HWDOC-X230-en

T5810XL Honeywell Workstation Planning Installation Service Guide HWDOC-X398-en

TPN Server User’s Guide EPDOC-X143-en-501A

TPS File Transfer Installation and User's Guide EPDOC-X144-en-501A

Troubleshooting Guide EPDOC-X243-en-501A

Turbine Control Users Guide EPDOC-X145-en-501A

Virtualization Planning and Implementation Guide EPDOC-X147-en-501A

Virtualization with BladeCenter S Guide EPDOC-X241-en

Windows Domain and Workgroup Implementation Guide EPDOC-X148-en-501A

Windows Domain and Workgroup Planning Guide EPDOC-X250-en

Windows Domain Implementation Guide for Windows Server 2008 R2 EPDOC-X251-en

Windows Domain Implementation Guide for Windows Server 2012 EPDOC-X263-en

Wyse Z90DE7/Z90DE7P Thin Client Planning Installation Service Guide HWDOC-X280-en

Yamatake MA500 Interface Reference EPDOC-X149-en-501A

Z440 Honeywell Planning Installation and Service Guide HWDOC-X368-en

Z620 Honeywell Planning Installation and Service Guide HWDOC-X223-en


19

3.2.2 Contents of Experion R501.1 SCN, Installation, and Migration PDF CollectionDocument name Document IDACE and SCE Off-Process Migration Guide EPDOC-XXX1-en-501A

Application Control Environment Cutover Upgrade Tool User’s Guide EPDOC-X404-en-501A

Collaboration Station Off-Process Migration Guide EPDOC-X355-en-501A

Control Hardware and IO Modules Firmware Upgrade Guide EPDOC-X150-en-501A

Controller Interoperability Reference for Controller Migration EPDOC-X240-en-501A

EApp Off-Process Migration Guide EPDOC-X176-en-501A

eServer Off-Process Migration Guide EPDOC-XX33-en-501A

Experion On Process Migration in Virtualized Environment Guide EPDOC-X328-en-R501A

Experion PKS R501.1 General Release Software Change Notice EPDOC-X166-en-501A

Experion Support and Maintenance Software Change Notice ESDOC-X183-en-240A

Experion Support and Maintenance Installation Guide ESDOC-X165-en-240A

Firmware Manager User’s Guide EPDOC-X470-en-501A

Getting Started with Experion Software Guide EPDOC-X112-en-501A

HMIWeb Solution Pack Installation Guide EPDOC-X171-en-501A

HMIWeb Solution Pack Migration Guide EPDOC-X170-en-501A

HMIWeb Solution Pack Software Change Notice EPDOC-X172-en-501A

Installation Builder Users Guide ESDOC-XX65-en-240A

Migration Planning Guide EPDOC-XX70-en-501A

Orion Console Installation Guide EPDOC-X313-en

RPS Migration Guide for Extio2 EPDOC-X163-en-501A

Software Installation User's Guide EPDOC-X136-en-501A

Supplementary Installation Tasks Guide EPDOC-X138-en-501A

System Initialization Media Software Change Notice (SCN) EPDOC-X185-en-124A

Upgrade Tool Components Media Software Change Notice (SCN) EPDOC-X153-en-501A

Upgrade Tool User's Guide EPDOC-X146-en-501A



4 Getting started

Related topics“About Experion installation and migration documents” on page 22“Supported server/client migration paths” on page 23“Supported controller migration paths” on page 24

21

4.1 About Experion installation and migration documentsThe Read Me First-Experion PKS is provided in printed form with the Experion R501.1 media. All the otherdocuments, such as, the Software Change Notices, Software Installation User’s Guide are available in a printer-friendly PDF format in the Experion R501.1 PDF collection CD. For migrations from Experion R3xx toR501.1, see the Upgrade Tool Components Media Software Change Notice.

The following table lists the documents to be used during the installation or migration. These documents mustbe read and followed to install or migrate an Experion system.

Name of the document Document usageExperion R501.1 Software Change Notice Before installing or upgrading to Experion R501.1.

Getting Started with Experion Software Guide To get an overview of the Experion system, and the overallinstallation or migration task flow.

Software Installation User’s Guide To perform a clean installation of Experion R501.1.

Migration guides Site-specific migration guides: The Upgrade Tool uses themigration guides available on the Experion Upgrade ToolComponents media and depending on the site configuration,generates the site-specific migration guides. The site-specific migration guides contain complete informationabout the migration instructions for a component or nodewith a particular configuration. The site-specific migrationguides are specifically for the R3xx to R501.1 migrationpath.

Supplementary Installation Tasks Guide To complete additional tasks once you have completedinstallation or upgrade of Experion.

Integrated Experion-TPS User's Guide If you have TPS nodes in your system, use this document toperform additional mandatory tasks after the Experioninstallation is complete.

System Initialization Media Software Change Notice The SCN provides the latest information about the ExperionPKS System Initialization media and the platformssupported through that Initialization media.

Windows Domain and Workgroup Planning Guide The document provides the planning information for theWindows domain and workgroups.

For R501.1, the Experion domain controller userdocumentation is aligned with the qualification of domaincontroller operating systems. For more information aboutinstructions to install and configure a domain controller forExperion, see the following documents.

• Windows Domain Implementation Guide for WindowsServer 2008

• Windows Domain Implementation Guide for WindowsServer 2008 R2


• Windows Domain Implementation Guide for WindowsServer 2012 R2


4 GETTING STARTED


4.2 Supported server/client migration pathsThe following are the supported server migration paths for Experion R501.1.

• Experion R310.3 to R501.1 (on-process and off-process migration)

NoteExperion R310.1/R310.2 must first be migrated to Experion 310.3 and any mandatory patch, before migratingto Experion R501.1.

• Experion R311.3 to R501.1 (on-process and off-process migration)

NoteExperion R311.1/R311.2 must first be migrated to Experion 311.3 and any mandatory patch, before migrating toExperion R501.1.

• Experion R400.1 to R501.1 (on-process and off-process migration)• Experion R400.2 to R501.1 (on-process and off-process migration)• Experion R400.3 (with or without R400.4/R400.5/R400.6/R400.7/R400.8 patch) to R501.1 (on-process and

off-process migration)• Experion R410.1 to R501.1 (on-process and off-process migration)• Experion R410.2 (with or without R410.3/R410.4/R410.5/R410.6/R410.7/R410.8/R410.9 patch) to R501.1

(on-process and off-process migration)• Experion R430.1 to (with or without R430.2/R430.3/R430.4/R430.5/R430.6 patch) to R501.1 (on-process

and off-process migration)• Experion R431.1 (with or without R431.2/R431.3/R431.4 patch) to R501.1 (on-process and off-process

migration)• Experion R432.1 (on-process and off-process migration)• Experion R500.2 to R501.1 (on-process and off-process migration)

NoteExperion R500.1 must first be migrated to Experion R500.2, before migrating to Experion R501.1.

4 GETTING STARTED

23

4.3 Supported controller migration paths

AttentionContact HPS Migration Center of Excellence (COE) or your local Honeywell Technical Assistance Center (TAC)before migrating.

The following controller migration paths are qualified for Experion R501.1.

• Experion R301.1.2• Experion R301.2• Experion R301.2 Controller Patch 3 (B51)• Experion R301.2 Controller Patch 4 (B52)• Experion R301.2 Controller Patch 6 (B54)• Experion R301.2 Controller Patch 7 (B200)• Experion R301.3 Controller Patch 1 (B60)• Experion R301.3 Controller Patch 2 (B63)• Experion R301.3 Controller Patch 3 (B300)• Experion R301.3 Controller Patch 4 (B302)• Experion R301.3 Controller Patch 5 (B304)• Experion R310.2 Controller Patch 1 (B35)• Experion R310.3 Controller Patch 3 (B64)• Experion R310.3 Controller Patch 4 (B70)• Experion R310.3 Controller Patch 5 (B77)• Experion R310.3 Controller Patch 6 (B81)• Experion R310.3 Controller Patch 7 (B83)• Experion R310.3 Tools and Controller Patch 12• Experion R310.3 Tools and Controller Patch 13• Experion R311.2 Controller Patch 1 (B2 and B5)• Experion R311.2 Controller Patch 2 (B6)• Experion R311.2 Controller Patch 3 (B12)• Experion R311.3 (B300)• Experion R311.3 Controller Patch 1 (B301)• Experion R311.3 Controller Patch 2 (B304)• Experion R311.3 Controller Patch 3 (B305)• Experion R311.3 Controller Patch 4 (B308)• Experion R311.3 Controller Patch 5 (B312)• Experion R311.3 Controller Patch 6 (B317)• Experion R311.3 Controller Patch 7 (B321)• Experion R311.3 Tools and Controller Patch 8• Experion R311.3 Tools and Controller Patch 9• Experion R400.1 (B20)• Experion R400.1 Controller Patch 1 (B50)• Experion R400.1 Controller Patch 2 (B54)• Experion R400.1 Controller Patch 3 (B55)• Experion R400.2 (B200)• Experion R400.2 Controller Patch 1 (B206)

4 GETTING STARTED


• Experion R400.2 Controller Patch 2 (B208)• Experion R400.2 Controller Patch 3 (B212)• Experion R400.2 Controller Patch 4 (B214)• Experion R400.2 Controller Patch 5 (B218)• Experion R400.2 Controller Patch 6 (B220)• Experion R400.2 Controller Patch 7 (B224)• Experion R400.2 Controller Patch 8 (B232)• Experion R400.2 Tools and Controller Patch 9 (B234)• Experion R400.3 (B305)• Experion R400.4 (B311)• Experion R400.5 (B330)• Experion R400.6 (B350)• Experion R400.7 (B370)• Experion R400.8 (B392)• Experion R410.1 (B85)• Experion R410 Controller Patch 3 (B106)• Experion R410 Controller Patch 4 (B112)• Experion R410.2 (B208)• Experion R410.2 Rev2 (B210)• Experion R410.3 (B221)• Experion R410.4 (B230)• Experion R410.5 (B250)• Experion R410.6 (B270)• Experion R410.7 (B315)• Experion R410.8 (B390)• Experion R410.9 (B432)• Experion R430.1 (B92)• Experion R430.2 (B100)• Experion R430.3 (B121)• Experion R430.4 (B154)• Experion R430.5 (B183)• Experion R430.6• Experion R431.1 (B0)• Experion R431.2 (B104)• Experion R431.3 (B132)• Experion R431.4• Experion R432.1• Experion R500.1• Experion R500.2

The Controller Migration wizard is used for migrating process controller firmware and control hardwarefirmware. This wizard automates many of the tasks performed during controller migration and is used for bothon-process and off-process migration. It can be accessed from the Controller menu in Control Builder.

For more information, see the Experion Migration Planning Guide and the Upgrade Tool User’s Guide.

4 GETTING STARTED

25

4 GETTING STARTED


5 Supported software / hardware / firmware

Related topics“Platform hardware” on page 28“Antivirus software” on page 29“Microsoft Office compatibility” on page 30“Microsoft security updates” on page 31“Windows operating system” on page 32“Experion Backup and Restore” on page 33“Application Whitelisting” on page 34

27

5.1 Platform hardwareThe following physical and virtual platforms are supported.

AttentionVariations from the tested configuration may negatively impact the operation and/or performance of the hardwarewhen used as the specified node types.

Physical platforms• HP platforms

The following HP platforms are supported.

Workstation ServerHP Z440 workstation HP Proliant DL360p Gen8 server

HP Z620 workstation

• Dell platformsThe following Dell servers and workstations are supported.

Workstation ServerDell Precision R5500 workstation Dell PowerEdge T320 server

Dell Precision T3600XL workstation Dell PowerEdge R320 server

Dell Precision R7610 workstation Dell PowerEdge R330 server

Dell Precision R7910 workstation Dell PowerEdge T330 server

Dell Precision T5810XL workstation Dell PowerEdge T130 server

Dell PowerEdge R430 server

Attention• The performance workstation hardware can be used as a Experion Flex Server - ESV on Windows Client

Operating System.• To plug in FTE cables on a Dell Precision R7610 workstation, refer to the NIC connection requirements section

in the Fault Tolerant Ethernet Installation and Service Guide.

Virtual platformsHoneywell provides qualified virtual platforms that can be used with supported applications. The entire solutionis supplied and supported by Honeywell. The virtual platforms can be used for clean installation or migration.

The following virtual platforms are supported.

• VMware Virtual workstation• vSphere

For more information about virtualization support, see the following documents on the Honeywell ProcessSolutions website.

• HPS Virtualization Specification• Experion Virtualization Planning and Implementation Guide

For more information about the hardware supported for Experion, see the latest System Initialization MediaSoftware Change Notice.

In addition, you may download the following spreadsheet from http://www.honeywellprocess.com.

• Experion Update Matrix

5 SUPPORTED SOFTWARE / HARDWARE / FIRMWARE


https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/EP03-700-100_V1_Virtualization.pdf

https://www.honeywellprocess.com/en-US/support/pages/default.aspx

5.2 Antivirus softwareTo obtain the latest antivirus software information, you may access the following links in the HoneywellProcess Solutions website. If you are a new user, you must register at http://www.honeywellprocess.com.

• Click the following link for Antivirus Software Guidelines.

https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/anti-virus-software-guidelines.pdf

• Click the following link for Antivirus Quick Reference.

https://www.honeywellprocess.com/library/support/notifications/Experion/anti-virus-quick-reference-guide.pdf


29






5.3 Microsoft Office compatibilityClick the following link for latest information about the qualified Microsoft Office packages for the Experionproducts.

https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/certified-microsoft-office-packages.pdfThe latest Microsoft Office package information is available at the Honeywell Process Solutions website. If youare a new user, you must register at http://www.honeywellprocess.com.



https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/certified-microsoft-office-packages.pdf

https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/certified-microsoft-office-packages.pdf


5.4 Microsoft security updatesYou can access the latest Microsoft security updates at the Honeywell Process Solutions website. If you are anew user, you must register at http://www.honeywellprocess.com.• To access the latest Microsoft security update information at the Honeywell Process Solutions website, click

the following link.https://www.honeywellprocess.com/library/support/security-updates/Customer/Honeywell-Qualification-Matrix.zip

• After you register at the website, click the following link for ISO User Guide.https://www.honeywellprocess.com/library/support/security-updates/Entitled/suit-iso-user-guide.pdf


31


https://www.honeywellprocess.com/library/support/security-updates/Customer/Honeywell-Qualification-Matrix.zip

https://www.honeywellprocess.com/library/support/security-updates/Customer/Honeywell-Qualification-Matrix.zip

https://www.honeywellprocess.com/library/support/security-updates/Entitled/suit-iso-user-guide.pdf

5.5 Windows operating systemHoneywell has an Original Equipment Manufacturer (OEM) agreement with Microsoft for supplying operatingsystem media for Experion releases. The following Windows operating systems (English edition) are supported.

• On client nodes

– Microsoft Windows 10 Enterprise 2016 LTSB (x64)• On server nodes

– Microsoft Windows Server 2016 Standard (x64)



5.6 Experion Backup and RestoreExperion Backup and Restore (EBR) R501.1 will be qualified with Experion R501.1. For more information,please refer to EBR R501.1 User’s guide.


33

5.7 Application WhitelistingApplication Whitelisting is not supported in Experion R501.1.



6 New features and enhancements

Related topics“Experion-TPS integration” on page 36“Smart Test and Automated Commissioning (STAC) Enhancements” on page 39“SCADA enhancements” on page 44“Integration of MeterSuite” on page 45“ControlEdge RTU Supports Foundation Fieldbus” on page 46“Series C Mark II Phase 3 enhancements” on page 47“Collaboration Station enhancements” on page 48“System Management for Experion LCN” on page 49“Automated Device Commissioning (ADC) Device Rename” on page 50“HART Point Parameter Access” on page 53“Long Point Names for Process Points” on page 56“Experion software installation enhancements” on page 58“UIS enhancements” on page 59“System configuration enhancements” on page 65“SmartLine Transmitter Point Detail Displays & Faceplates” on page 66

35

6.1 Experion-TPS integration

6.1.1 Experion Local Control Network (ELCN)Beginning with Experion R501.1 and TPN R687.1, the Experion Local Control Network (ELCN) has beenintroduced. With Experion LCN, the legacy coaxial cable system is replaced by the Fault Tolerant Ethernet(FTE) system. The objective of the ELCN is to convert classic LCN nodes to FTE-based Experion LCN nodes.

ELCN migration is divided into two general parts. The first part is installing the ELCN Bridge which operatesas a translator between the LCN and FTE. The second part is the conversion of LCN nodes to Experion LCNnodes. An Experion LCN node is a hardware/software entity that performs the same function as its LCN nodecounterpart, where an FTE network replaces the coaxial cable network.

Migration to the ELCN requires an ELCN Bridge to connect the Classic LCN to the Experion LCN, creating asingle logical hybrid network. The ELCN Bridge must be installed as a redundant pair.

The ELCN Bridge translates LCN messages into Ethernet messages and vice versa. The ELCN Bridge providesa means for legacy LCN functions and the Experion version of those functions to coexist and interoperateduring migration of the classic LCN nodes to Experion LCN nodes. After the ELCN Bridge creates acommunication path between the LCN and the FTE network, you can upgrade the classic LCN nodes one at atime.

Before migration to ELCN can be accomplished, an Experion R501.1 system with redundant ESVTs, MicrosoftWindows 10 Operating System and Microsoft Windows Server 2016, and TPN R687.1 are required.

The upgrade process may occur over an extended period of time until no nodes remain connected to LCN, otherthan the ELCN Bridge. At this time the ELCN Bridge may be removed (as the final step of the upgrade) andreused as a spare part (Experion LCN node or ELCN Bridge).

Included in the first release of ELCN are ES-T, ESVT, EAPP, ACE-T, and History Module (virtual andphysical), as well as the introduction of appliance redundant ENIM and appliance non-redundant AM (bothphysical).

The following figure illustrates a simple architecture of ELCN.

Figure 1: ELCN Architecture

Benefits of ELCN are:

• Replacement of coaxial cables with superior Fault Tolerant Ethernet, which tolerates all single faults andmany multiple faults, and is much easier to maintain.

6 NEW FEATURES AND ENHANCEMENTS


• Retaining intellectual property in legacy assets by conserving applications running on the TPS/LCN.• Increased plant longevity through Unified Control (Experion PKS and TPS).• Retaining point processing and checkpoints from classic nodes.

The major ELCN components are:

• ELCN Bridge: Migration to the Experion LCN requires an ELCN Bridge to connect the classic LCN to theFTE-based Experion LCN, creating a single logical hybrid network.

• ACE-T and EAPP: ACE-T is an Experion Virtual or Microsoft Windows-based controller with TPNconnection. EAPP is an Experion Virtual or Microsoft Windows-based node with direct connection to LCN.EAPP is used by applications needing Read or Write access to data. ACE-T and EAPP run on WindowsServer 2016.

• ES-T and ESVT: ES-T is an Experion Virtual or Microsoft Windows-based user interface node. ESVT is anExperion Virtual or Microsoft Windows-based server. ES-T and ESVT run on Microsoft Windows Server2016. Microsoft Windows 10 is optional for ES-T. ES-T and ESVT may need a Microsoft Windows 10 PCor a Thin Client (to avoid the need of a VMWare Server) to connect with the user interface.

• Universal Embedded Appliance (UEA): The UEA is a core component of the ELCN, providing ahardware platform for the following ELCN functions:

– Bridging capabilities for systems under migration from LCN to ELCN (ELCN Bridge)– Physical TDC 3000 capabilities (ENIM, AM), (EHB, EPCLG, NG in later releases)– Interface to other systems like Triconex Safety Controller

• ELCN Bridge Media Access Unit (MAU) Cable: The LCN connection to an ELCN bridge is made viaMAU cables. The in-cable-MAU contains electronics that convert LCN analog signals to digital signals,which are then processed by the ELCN Bridge to be made compatible with ELCN FTE. The reverse occurswhen ELCN FTE signals are sent to LCN nodes. This two-way process allows for full two-way LCN-ELCNcommunication.

• History Module (HM) A node that provides mass storage. They are principally used to store historical dataincluding continuous history, and various journals and logs. They can also be used to store software, systemfiles, and user files. HMs are also used to load other ELCN nodes. HMs run on Microsoft Windows Server2016.

• FTE Switch/Cable: FTE switches and cables are used in the Experion system. FTE is the control networkfor the Experion system. FTE provides multiple communication paths between nodes, enabling an FTEnetwork to tolerate all single faults and many multiple faults. An FTE network is implemented through FTEnodes that contain FTE software and appropriately configured switches.

• Virtual Infrastructure: Virtual ELCN nodes that may run on servers are the previously described ACE-T,EAPP, ES-T and ESVT, as well as the History Module (HM).

• Thin Client: A thin client is a device that fulfills the traditional computational role of a typical workstationcomputer while the actual workload resides on a remote server, not on the thin client itself.

• ESXi and ESXi Host: ESXi is a virtualization layer that runs on physical servers that allows the sharing ofthe underlying physical machine resources between different virtual machines, each running its ownoperating system. ESXi Host is a PC that is running ESXi virtualization software to run virtual machines.

The following list identifies all documents that may be sources of reference for material discussed in thissection.

Document Name Document Type Document SetELCN Planning, Installation, and ServiceGuide Planning and Design; Troubleshooting Experion PKS

ELCN Overview and Implementation Guide Planning and Design Experion PKS

Experion Migration User’s Guide (EMUGs) Installation and Upgrades Experion PKS

ELCN Quick Start Guide Reference Experion PKS


37

Document Name Document Type Document SetELCN Upgrade Kit Instructions(51195195-415) Installation and Upgrades Release Independent

Customer Release Guide Installation and Upgrades TPN/TPS

Experion Software Installation User’s Guide Installation and Upgrades Experion PKS

Control Building User’s Guide Configuration Experion PKS

Integrated Experion-TPS User’s Guide Configuration Experion PKS andTPN/TPS

Virtualization Planning and ImplementationGuide

Planning and Design; Installation andUpgrades Experion PKS

Server and Client Planning Guide Planning and Design Experion PKS

Server and Client Configuration Guide Configuration Experion PKS

Control Builder Parameter Reference Reference Experion PKS

Control Builder Components Reference Reference Experion PKS

Experion PKS R501.1 Software Change Notice Reference Experion PKS

TPN Personalities R687.1 Software ChangeNotice Reference TPN/TPS



6.2 Smart Test and Automated Commissioning (STAC) EnhancementsBeginning with Experion R501, the enhancements for Project Engineering Tool, Engineering Data Builder andHART Point Parameter Access are introduced.

Engineering Data Builder enhancementsFilter: With Experion 501, users can save the filter criteria. It is saved in a text format by clicking Save Filterto any user defined location. This helps users to reuse the filter criteria. The following image illustrates thescreen of a saved text document with filter criteria.

The following image illustrates the screen of a saved text document with filter criteria.

Back Build Workbook: Beginning with Experion 501, a new feature is added on Building Workbook front,called Back Build Workbook.

This feature allows users to create a workbook from the existing database. The following image illustrates the“Select Hardware Types” screen.


39

The “Select Hardware Types” workflow allows users to retrieve a subset of available items by using filters foruse in creating hardware selections of the rows in the spreadsheet. A new workbook is created based on thecontent of the database.

The following image illustrates the “Select IO and Control” screen for multiple filtering and addition ofinstances.



The “Select IO and Control” workflow allows users to retrieve the type (available under project) and typical(available in library) of the strategies from the selected subsystem. The user can create a new workbook basedon the template available in the database.

The following image illustrates the “Edit Data Worksheet” screen.


41

The “Edit Data Worksheet” that is saved can be edited or using Invoke Excel to Edit.

Project Engineering Tool enhancementsWith Experion R501, a new feature is added in ADC (Automated Device Commissioning) to rename a deviceand to link to its channel. Any inconsistency in device name can be fixed using this Rename Device feature.This feature allows renaming of un-commissioned channels through ADC workflow. The system provides theability for the user to store a name to the long name of a HART device during the match step of automateddevice configuration.

NoteRenaming a device is only possible using the renaming feature, renaming a channel cannot be achieved using thisfeature. There are certain criteria following which the users can rename the device.

HART point parameter accessBeginning with Experion R501, a new feature is added which supports accessing standard HART parameters.This helps users to access standard HART parameters from display or external applications. The HART data isaccessed through Experion OPC Server.

HPPA supports the following:

• “Read Only” access of HART parameters• HART 5, 6 and 7 versions of HART devices• HART Universal and Common Practice Command parameters• OPC Interface Browsing for HART parameters

There is no migration impact from previous release to R501.



NoteDDs must be imported in Experion system to ensure that HART parameter access is supported upon migration.


43

6.3 SCADA enhancementsThere have been a number of SCADA based enhancements made to the system which are listed below. Inaddition, there has been a general user interface improvement made to the Server Redundancy Status display.

EMDB BCC IntegrationEMDB has been updated in R501 to allow installation on the Experion Server machines in BCC topologies.EMDB system changes will be restricted to the server location where the changes are being made, to continueconfiguration in the alternative server location will require restoring a previously backed up EMDB file.

For more information about configuring EMDB for BCC, see "Example file replication scenario: EMDBbackup file in systems with BCC" in the Server and Client Configuration Guide.

RDM BCC IntegrationRDM has been updated in R501 to support BCC topologies, configuration now allows for up to a maximum oftwo BCC Server Locations. If RDM detects that the primary server has been lost it will stop forwardingmessages and attempt to locate the new primary server across both server locations, connect to that and restartmessage forwarding.

For more information about configuring RDM for BCC, see "Redundancy behavior in Experion system withBackup Control Center (BCC)" in the Redirection Manager User's Guide.

BCC Automatic Server Location FailoverR501 has introduced automatic failover between server locations for BCC based topologies. This option willallow a backup server location to promote itself to active if communication with the current primary has beenlost for a configurable amount of time. The option will be off by default, once switched on the user can specifythe server location failover time which will default to 15 seconds.

For more information about configuring automatic server location failover, see "Configuring automatic failoverbetween server locations" in the Server and Client Configuration Guide.



6.4 Integration of MeterSuiteBeginning with Experion R501.1, the following MeterSuite CCLs are available as standard CCLs.

Library Name Block NameAPI_NGL API_NGL

AGA_10 AGA_10

Metering FISCAL_TOT

PCDI_FLOAT64

The calculations are supported in C200E, C300 and ACE and their simulation environments. With theproductization of the above CCLs, all the required calculations for Liquid/Gas flow measurement will be a partof standard CCLs and no separate MeterSuite installations are required. This release also provides detail displaysupport for all the MeterSuite CCLs including the CCLs productized with Experion R400.1. This release alsosupports viewing MeterSuite reports from an Experion Station.


45

6.5 ControlEdge RTU Supports Foundation FieldbusBeginning with Experion R501, Series C FIM4 can be used as the Foundation Fieldbus Interface Module for theControlEdge RTU. As part of this enhancement, Series C FIM4 supports a Modbus TCP interface to connectwith ControlEdge RTU (non-redundant and redundant controllers). Control Builder is used to configure theModbus TCP interface for FIM4. With this interface, Foundation Fieldbus data can be accessed in the RTU andused in the ControlEdge Builder for RTU programming. It is recommended to use a physical switch to establisha physical connection between FIM4 and RTU.



6.6 Series C Mark II Phase 3 enhancementsSeries-C Mark II DCS system is meant for high growth, highly competitive regions where cost is a drivingfactor. Series-C Mark II allows less up-front engineering effort to install through enhanced power distributioninfrastructure in a cabinet.

Phase 3 program overview and enhancements:Phase 3 program scope includes the following to make it a complete Low Cost Solution DCS system:

• Cabinet Infrastructure enhancements: new power distribution system with a new cabinet architecture• The following Series C Mark II I/O items are included in phase 3:

NNP Part list ModuleDC-TFB413 SC MK FIM4 RED IOTA

DC-TFB813 SC MK FIM8 RED IOTA

DC-TFB403 SC MK FIM4 Non RED IOTA

DC-TCF902 SC MK II CF9 IOTA

DC-TDIL11 SC MK II DI24V RED IOTA

DC-TPIX11 SC MK II PI IOTA

DC-TUIO41 SC MK II UIO2 RED IOTA

DC-TUIO31 SC MK II UIO2 NON RED IOTA

51454909-100 CCA assembly

50135106-100 Header board bracket

DU-PWMR21 Meanwell Power supply w/o Diode

DU-PWPR21 Phoenix Contact Power Supply w/o Diode

51202971-202, 212, 402, 412 SC MK II Combo cable

DC-TPOX01 SC MARK II PGM IOTA

DC-TEIM01 Ethernet Interface Module

DC-TDIL01 SC MARK II DI 24V Non Redundant IOTA

DC-TDOB01 SC MARK II DO 24V BUSS Non-Redundant IOTA

DC-TDOB11 SC MARK II DO 24V BUS Redundant IOTA

DC-TDOR01 SC MARK II DO Relay Non-Redundant

DC-TDOR11 SC MARK II DO Relay Redundant

DC-TAID11 SC MARK II AI Diff Redundant IOTA

DC-TAID01 SC MARK II AI Diff Non Redundant IOTA

DC-TDI110 SC MARK II DI 110V Non Redundant IOTA

DC-TDI220 SC MARK II DI 220V Non Redundant IOTA


47

6.7 Collaboration Station enhancementsExperion Collaboration Station has been enhanced to focus on Control Room use on the Process ControlNetwork (PCN). With Experion R501, Collaboration Station supports a read only, direct connection to anExperion PKS Server when used on the PCN (that is, eServer is not required). This significantly reduces theengineering effort required. Other major enhancements in Experion R501 include:

• UHD (4K) Touch Screen support. Nine Experion PKS displays (or other operational documents) can besimultaneously open and easily legible on the UHD touch screen.

• Multiple workspaces. In Experion R501, Collaboration Station supports a hierarchy of multiple workspacesfor your entire process. Use touch to navigate between workspaces, from a level one process overviewworkspace down to detailed level 2/3 workspaces.

Existing Collaboration Station installations currently on the business network and connected via eServer willcontinue to be supported.



6.8 System Management for Experion LCNLCN and ELCN (Experion LCN) system components can now be represented in dashboard displays in theSystem Status display. One or more dashboards are automatically created to provide a graphical view of LCNsystem components from within Experion in a similar layout to the Native Window displays. For moreinformation, see "Managing LCN and ELCN nodes from Experion" in the ELCN Overview and ImplementationGuide. Custom dashboards can also be created to include LCN and ELCN nodes.

Native Window displays and relevant TPS operations can be performed from the Status pane of the SystemStatus display.

The TPS System and Console Status indicators found on the Status Bar can now be configured to call up therelevant Experion or TPS display when S or C is clicked. For more information, see "Configuring which displayis called up by the TPS System and Console Status indicators" in the ELCN Overview and ImplementationGuide.


49

6.9 Automated Device Commissioning (ADC) Device RenameThis section describes the Automated Device Commissioning (ADC) feature introduced with Experion R501.1.

Beginning with Experion R501, a new feature is added in ADC to rename a device and to link to its channel.Any inconsistency in device name can be fixed using this Rename Device feature. This feature allows renamingof un-commissioned channels through ADC workflow. The system provides the option for the user to store aname to the long tag name of a HART device during the match step of automated device configuration. Userwill be presented the option to rename the device only when there is no channel in the ERDB with the name ofthe device being interrogated.

To rename a device1. Click .

The Status Panel Area is displayed.

2. Enter the desired device name.



3. Click Rename Device.

After rename operation, click Close.

Conditions and Messages for renaming device:

• When the device name is empty, or duplicate, or contains ‘?’ marks.

– Message: Device name is not specified or is invalid or is duplicate. Please enter the new device name.• When a match is not found in the database.

– Message: <devicename> channel match not found in database. Consider renaming the device,


51

• When there are duplicated devices in the scope.

– Message: Duplicate device name <devicename> has been detected in channel position<listofchannelnumbers>. Consider renaming the device.

• When the rename is successful.

– Message: Device has been renamed to <newdevicename>.

Validation:

• If the user enters a device name already detected in the given IOM or CABINET.

– Message: Duplicate device name found in the ADC scope. Please enter a unique device name.• If user enters more than 40 characters.

– Message: Invalid Name: Length exceeds 40characters.• If user does not enter any name.

– Message: Invalid Name: Name cannot be empty.• If user enters invalid characters.

– Message: Invalid name: Illegal character(s) encountered.

NoteThe name of the device and the channel are case insensitive.

CAUTIONWhen you rename a device with a wrong long tag name, which corresponds to a matching channel in ERDB, thenyou will not have any option to rename the device again using the PET plugin. You will have to use a hand helddevice or FDM application to rename the device again.



6.10 HART Point Parameter AccessThis section describes the HART Point Parameter Access (HPPA) introduced with Experion R501.1.

HART Point Parameter Access (HPPA) will provide system wide read-only access by name to HART device.HART data access is available only if Experion Server is available. The scope in Experion R501.1 is to supportREAD-ONLY HART data access for the following applications. HART diagnostics support will be provided ina future release.

• Station Applications/Operator displays• Application integration through Experion Server interfaces (for example, OPC Clients, Server API and so

on)

HPPA supports:

• “Read Only” access of HART parameters• HART 5, 6 and 7 versions of HART devices• HART Universal and Common Practice Command parameters• IO Modules Series C AI, AO, UIO1 and UIO2

NoteDDs must be imported into Experion system to ensure that HART parameter access is supported upon migration.HART data access is slower in performance compared to data access through CDA Server.

HART data through OPC Applications can be accessed through Experion OPC Server. For redundancy support,Redirection Manager should be used for Experion OPC Server to avoid loss of HART data during server switchover or failover scenarios. HART data access is slower in performance compared to data access through CDAServer. HART parameters which are not exposed through CDA Server can be access through HPPA and used.HART Data parameters which are DD-based cannot be accessed through Control Builder.


53

Figure 2: HART Point Parameter Access

HART Resident Data can be used in any of these applications:

• Honeywell OPC Applications

– Sentinel– PHD (through Experion server only)– Advanced Control Application

• Internal Applications like:

– Faceplates and detail displays– Trends and Groups– Reports– History

• External OPC Applications:

– IBM Maximo– OSI PI

Reading Hart Data from Experion ServerExperion OPC Server is used to access HART parameter data.

To access the HART parameter data using Experion OPC, the user must select HWHsc.OPCServer5 andprovide an Item ID in the form of HartPointName.Parameter. In Experion R501.1, Hart Parameter Browse is notsupported. Therefore, you can refer to vendor specific Device manual for accessing HART Parameters whichare exposed through variables.



Figure 3: OPC Server selection

To add the Item ID user must follow a proper naming convention, which is, “Channel.Parameter”.

Example: “STTTransmitter_01.longTag”, where “STTTransmitter_01” is the devicename represented in Controlbuilder in that slot position, “longTag” is the parameter and “.” is the specifier.

Limitations of HPPA:

• A total of 800 HART devices are supported, that is, data can be fetched from 800 devices at a time inclusiveof all clients like displays and any OPC Clients.

• OPC Interface Browsing for HART parameters not supported.• Fast history is not recommended for HART data access due to slowness in performance.• Reading of local variables is not supported.• It is recommended to access 15 parameters per device simultaneously from all clients (for better

performance and avoiding disconnections due to time out).• Bit ENUM parameters cannot be historized.• Unlike device replacements, should be performed only after deleting the HART channel from Control

Builder.


55

6.11 Long Point Names for Process PointsBeginning with Experion R501.1, Point name length has increased from 16 to 40, bringing Process Points inline with SCADA Points. The Expression length has increased from 255 to 1024 characters. All expressionsupported blocks allow expression length up to 1024 characters.

Long point names will be displayed in the below tools:

• Enterprise Model Builder• Control Builder• Station Displays• CTools• Upgrade Tool• Firmware Manager• NCT (Node Configuration Tool)• L1 Audit Tool

The following are the exceptions for the long point name support:

• Server Alias Name: Server alias name will be restricted to 16 characters. Server alias names longer than 16characters are not supported due to limitations in the server database.

• FF Devices: FF Devices support name length up to 32 characters. But FIM and FFLINK support 40characters.

• Wireless Devices: Wireless Devices support name length up to 16 characters. But wireless device managerand other wireless interfaces support 40 characters.

• FTEB: name length supports up to 16 characters.

Figure 4: Long Point Name in Detail Display



Figure 5: Long Point Name in Alarm Display


57

6.12 Experion software installation enhancements

Integration of TPS personality media installation with Experion installationTPS personality media installation is integrated with Experion. An option to select TPN Application Module orGUS TPN Software appears in the Feature Selection dialog box during T-node installation. For informationabout installing the TPS personality media during Experion installation, refer to the Software Installation User’sGuide.

Integration of Microsoft Updates media installation with Experion installationMicrosoft Updates media installation is integrated with Experion. An option to select Microsoft Updates mediaappears in the Feature Selection dialog box during installation. For information about installing the MicrosoftUpdates media during Experion installation, refer to the Software Installation User’s Guide.



6.13 UIS enhancements

Experion Detail Display enhancementsNavigation to a related point detail display from Experion TPS Detail Display (UIS 4539)Certain point types may include related point names such as, LOGICSRC, EIPPCODE and PRIMMODparameters. Beginning with Experion R501.1, when any of these parameter point names apply, they will appearas hyperlinks, with which you can navigate directly to the given point’s detail display.

NoteNote that this applies only to the following point types (as defined by DISPTYPE parameter categorization):

• DIGCOMP• DEVCTL• DIGIN• DIGOUT• DIGINOUT

Figure 6: Navigation to a related point detail display from Experion TPS Detail Display

Display Override Selector state on Experion TPS Faceplate (UIS 3727)Beginning with Experion R501.1, the “Override Selector” state as indicated by the Point Override Status(PTORST*) parameter on the Native Window is reflected on the Experion TPS Faceplate. An indication ispresented on the point’s faceplate when its PTORST value is “SEL” or “NOTSEL”. Pictured below is whenPTORST = SEL. For PTORST=NOTSEL, the indication on the faceplate is “OR not Sel”.


59

For information on Override Selector Algorithm and Point Override Status Parameter, refer to the PM ControlFunctions and Algorithms and PM Family Parameter Reference Dictionary in the TPN/TPS bookset.

NotePTORST parameter indicates the override status of a point.

Figure 7: Override Selector state

Alarm and Data enhancementsThere are 2 enhancements to Alarm Shelving functionality in Experion R501:

• A new 'End of shift' shelving period makes it easy to shelve an alarm until the end of the current shift. Thereis also a configuration option to delay unshelving until after the shift handover period.

• A new 'Custom' shelving period allows unshelving at a specific date and time in the future, such as whenplanned maintenance will be completed. There are additional configuration options for the longer maximumshelving periods.

See the 'Alarm Shelving Tab' topic in the Server and Client Configuration Guide and the 'Shelving an Alarm orAlert' topic in the Operator's Guide for more information.

There are improved monitoring and diagnostic capabilities for Distributed System Architecture (DSA)connections in Experion R501:

• A new 'Response time' alarm can be optionally enabled per DSA connection to provide advance warning ofan overload or slow connection. This can be useful to initiate diagnostic activity and address a problembefore a DSA disconnection occurs.

• A new 'Performance' tab on the DSA configuration display shows a trend of response time on theconnection. This historical data is a first level of diagnostics to assess the performance of a connection andhelp identify the cause of an overload, such as an application performing excessive reads or writes at certaintimes.



See the 'Performance alarms' description and the 'Monitoring distributed server connection performance' topic inthe Server and Client Configuration Guide for more information.

Experion software installation enhancements (UIS 4561 and UIS 4625)There are 2 enhancements to Experion software installation in Experion R501:

TPN personalities installation along with Experion installation (UIS 4561)This solution integrates the installation of TPN personalities along with Experion installation. This saves theadditional effort required to install TPN personalities as a separate entity after the Experion software installationhas been completed.

This functionality will be available on the following Experion nodes:

• TPN Application Module

– Server TPN Connected (ESVT)– Application Control Environment TPN Connected (ACE-T)– App Node (E-APP)

• GUS TPN Software

– Console Station TPN Connected (ES-T)

The following enhancements have been made to accommodate the installation of TPN personalities:

• Experion Software Installation Server (ESIS) based installations: enhance ESIS to accommodate the TPNpersonalities media.

• Experion software installer: enhance Experion software installer to install TPN personalities during theExperion installation/migration, provided you have selected TPN personalities as part of feature selection toinstall it.


61



• TPN personalities: enhance TPN personalities and related applications to be compatible with Experioninstallation such that it follows all the guidelines provided for integration with the same.

• Experion software installation DVD: enhance Experion software installer to prompt for TPN personalitiesCD and install TPN personalities during the installation/migration, provided you have selected TPNpersonalities as part of feature selection to install it.

SUIT media installation along with Experion installation (UIS 4625)This solution integrates the installation of latest SUIT updates along with Experion installation. This saves theadditional effort required to install SUIT updates as a separate entity after the Experion software installation hasbeen completed.

This functionality will be available on the following Experion nodes:

• Server (ESV)• Server TPN Connected (ESVT)• eServer• Application Control Environment (ACE)• Application Control Environment TPN Connected (ACE-T)• Simulation Environments• Console Station (ES-C)• Console Station TPN Connected (ES-T)• Console Extension Station (ES-CE)• Flex Station (ES-F)• Collaboration Station• Experion Hiway Gateway (EHG)• App Node (E-APP)• Application Server (EAS)• PC Universal Station (PCUS)The following enhancements have been made to accommodate the installation of SUIT media:

• Experion Software Installation Server (ESIS) based installations: enhance ESIS to accommodate the SUITmedia.

• Experion software installer: enhance Experion software installer to install SUIT updates at the end ofExperion installation/migration, provided you have selected SUIT updates as part of feature selection toinstall it.


63

• SUIT media: enhance the SUIT media to be compatible with Experion installation such that it follows all theguidelines provided for integration with the same.

• Experion software installation DVD: enhance Experion software installer to prompt for SUIT DVD andinstall SUIT updates at the end of Experion installation/migration, provided you have selected SUIT updatesas part of feature selection to install it.



6.14 System configuration enhancementsSystem Configuration has been enhanced through the introduction of an option to Enable confirmation of anyServer Wide Settings changes. You can use this option to enable a confirmation callout for any change made tothe Server Wide Settings. A minimum security level of MNGR is required to set this configuration option.

SCADA point alarm and event configuration has been enhanced through the introduction of an option to enableChange of State events on a Status point. If the PV state for a Status point is changed and this option is enabled,a CHANGE event is journaled. A minimum security level of MNGR is required to set this configuration option.Note that configuration of the alarm functionality and the CHANGE event functionality have no impact on eachother.


65

6.15 SmartLine Transmitter Point Detail Displays & FaceplatesNew optional point detail displays and faceplates have been introduced specifically for Honeywell SmartLinetransmitters in Experion R501.1. These new displays and faceplates were designed and implemented to improveuser experience. The goal is to deliver the best user experience through the modern visual design, simplenavigation and intuitive arrangement of information, such that plant operators and maintenance technicians canaccess important process, configuration and diagnostic information of the SmartLine transmitters easily andperform any necessary actions promptly.

The new point detail displays and faceplates are available for the following SmartLine transmitters:

• Guided Wave Radar Level (SLG700)• Multivariable (SMV800)• Pressure (ST700 and ST800)• Temperature (STT700, STT750 and STT850).

The new SmartLine point detail display follows a similar layout as the previously existing generic point detaildisplay for analog point. The top bar in the SmartLine point detail display indicates how the analog point of thetransmitter is connected to the other components in the system hierarchy. The left section of the display isreserved for the new SmartLine faceplate. Like any Experion faceplates, the new SmartLine faceplate can becalled up from a custom display as a standalone feature to provide operators with quick access to key processinformation. The rest of the point detail display houses one of the four sub-displays. These sub-displays arenamed Overview, Faults & Resolutions, Range and Device Details, and can be called up individually byclicking their corresponding navigation buttons located across the top of the SmartLine point detail display. Thefollowing image shows the SmartLine point detail display with the Overview sub-display requested.

Figure 8: SmartLine Point Detail Display with Overview sub-display

As shown on the left side of the SmartLine point detail display, the SmartLine faceplate provides informationabout the type of SmartLine transmitter the analog input channel is connected to. In addition to displaying thevalues of the analog PV and digital dynamic variables (PV, SV, TV and QV), the SmartLine faceplate has beenenhanced to show the engineering units and descriptions of these variables. The faceplate continues to provide ameans to acknowledge active alarms of the analog input point and a link to the control module’s point detaildisplay if the analog input point is associated with a control module.



The Overview sub-display is the default sub-display on the initial load of the SmartLine point detail display.This sub-display is intended to provide a quick overview of the critical information about the SmartLinetransmitter right at the first glance. The Overview sub-display has three sections: Fault Conditions, DeviceStatus and Alarm Enabling. The Fault Conditions section displays the active fault conditions reported by theSmartLine transmitter or the analog input module. An active fault condition is shown as a line item with a roundpriority indicator and a text string to describe the fault condition. The color of the round indicator shows thepriority of the fault condition: red for critical condition and yellow for non-critical condition. A maximum of sixactive fault conditions can be shown in the descending order of priority. When there are more than six activefault conditions, only the six conditions of the highest priorities are shown. To view all the active faultconditions, the user can click the View Details> hyperlink at the top right corner of the Fault Conditions sectionto navigate to the Faults & Resolutions sub-display. When there is no active fault condition, the FaultConditions section shows one line item with a gray round status indicator and a text string of “No faultconditions”, and hides the View Details> hyperlink.

The Device Status section displays the states of various important status conditions for the SmartLinetransmitter. Some of these status conditions are transient such as Cold Start and Configuration Changed, whileothers are of a more permanent nature, such as Fixed Current Mode and Maintenance Required. Some statusindicators are for alerting the user of failures such as Device Variable Alert and Critical Power Failure. TheAlarm Enabling section provides the means to enable or disable the alarm reporting function and journal onlyoption for the analog point.

The following image shows the Faults & Resolutions sub-display of the SmartLine point detail display. Asmentioned previously, in addition to clicking the Faults & Resolutions display navigation button, the user cannavigate to the Faults & Resolutions sub-display from the Overview sub-display by clicking the View Details>hyperlink in the Fault Conditions section if the SmartLine transmitter has active fault conditions.

Figure 9: SmartLine Point Detail Display with Faults & Resolutions sub-display

The Faults & Resolutions sub-display provides quick and easy access to potential cause and resolutioninformation for the active fault conditions of the SmartLine transmitter, and facilitates the process oftroubleshooting the fault conditions. The sub-display is divided into three vertical sections: Condition, Causeand Resolution. The Condition section is for displaying all active fault conditions for the SmartLine transmitterand its analog point. An active fault condition is shown as a line item with a round priority indicator and a textstring to describe the fault condition. The color of the round indicator shows the priority of the fault condition:red for critical condition and yellow for non-critical condition. The section can show a maximum of 14 activefault conditions in the descending order of priority. If more than 14 fault conditions are active, the <Prev and


67

Next> buttons will appear at the base of the section for the user to go back and forth to review all active faultconditions. The Cause section shows detailed information about the potential causes of a particular faultcondition, while the Resolution section describes the steps in resolving a particular fault condition. When theuser clicks on an active fault condition in the Condition section, the Cause and Resolution sections will bepopulated with information for the selected fault condition. The selected fault condition is shown in a whitebackground, same as that of the Cause and Resolution sections. When there is no active fault condition, theCondition section shows one line item with a gray round status indicator and a text string of “No faultconditions” and the Cause and Resolution sections are blank.

The following image shows the Range sub-display of the SmartLine point detail display. The Range sub-displayis divided into three vertical sections: Transmitter, Analog Signal and AI Channel. The information in the threesections illustrates how the measurement signal originates from the transmitter, converts into the electric currentin the wire and finally arrives at the Experion analog input module.

Figure 10: SmartLine Point Detail Display with Range sub-display

In the Transmitter section, the digital PV is shown on a scale marked with the measurement range limits: URV(upper range value) and LRV (lower range value), and the sensor limits: URL (upper range limit) and LRL(lower range limit). In the Analog Signal section, the loop current is shown on a scale marked with the currentrange limits and saturation limits. The scale also indicates whether the failure mode used is fail high or fail lowby showing the red segment at either the high end or low end of the scale. In the AI Channel section, the analogPV is displayed on a scale marked with the PV range limits (Hi and Lo) and extended range limits (Ext Hi andExt Lo).

To accurately represent the signal of the transmitter in the analog input channel, it is important that thetransmitter’s range values (URV and LRV) match the analog input channel’s range limits (Hi and Lo) and thatthe transmitter’s range limits (URL and LRL) match the analog input channel’s extended range limits (Ext Hiand Ext Lo). If any pair of values are set differently, the line connecting the values will change from gray to redcolor. The error Device PV Range Mismatch will also appear at the top of the Range sub-display. Furthermore,the status of the signal is shown above the signal scale as a round status indicator and a text string to describethe status in each section. The color of the round status indicator shows whether the status is normal (gray), forinformation only (white), a warning (yellow) or an error (red). The area below the signal scale in each sectiondisplays the parameters used in processing the signal.

The following image shows the Device Details sub-display of the SmartLine point detail display. The DeviceDetails sub-display is divided into two top and bottom sections: I/O Channel and Transmitter. The I/O Channelsection shows the identification information of the SmartLine transmitter on the analog input channel side as



well as the I/O module-specific and supplementary information. The Transmitter section shows theidentification information of the SmartLine transmitter inside the transmitter and HART revision information.The sub-display also provides the means to resolve potential identification conflicts, such as the use of adifferent device ID for the analog input channel from the transmitter device ID. In this case the Device IDMismatch error will show up at the top left corner of the sub-display, and the Accept Transmitter ID button willappear to the right side of the error. The user can click this button to have the analog input channel use the samedevice ID as configured inside the transmitter.

Figure 11: SmartLine Point Detail Display with Device Details sub-display

It is important to note that in Experion R501.1, any analog input points including those for the SmartLinetransmitters are configured to use the previously existing generic analog point detail display and faceplate bydefault. In order to use the new SmartLine point detail displays and faceplates for SmartLine transmitters,additional configuration steps should be performed using the Control Builder when building the analog inputchannel for the transmitter. First open the project configuration screen for the analog input channel. Then selectthe Server Displays tab as shown in the following image.


69

Figure 12: Control Builder block - Server Displays tab

In the Point Detail Display field, delete the html file name of the default point detail display and type in the htmlfile name of the new SmartLine point detail display. In the Group Detail Display field, delete the html file nameof the default faceplate and type in the html file name of the new SmartLine faceplate. The following tableshows the files names of the new point detail displays and faceplates for the four types of SmartLinetransmitters.

Table 1: File names of new point detail and faceplate displays

SmartLine Transmitter Type SmartLine Point Detail Display SmartLine FaceplateGWR Level sysdtlSmartLineLevel sysdtlSmartLineLevel_fp

Multivariable sysdtlSmartLineMultivariable sysdtlSmartLineMultivariable_fp

Pressure sysdtlSmartLinePressure sysdtlSmartLinePressure_fp

Temperature sysdtlSmartLineTemperature sysdtlSmartLineTemperature_fp

The SmartLine point detail displays and faceplates are to be used for Honeywell SmartLine transmitters only.Do not use these displays and faceplates for other Honeywell transmitters that are not SmartLine or transmittersfrom other vendors. Once the correct SmartLine point detail display and faceplate file names are entered, clickOK to exit the screen.



7 Problems resolved

This chapter provides the details of resolved PARs.

NoteA documentation PAR is included in the SCN only if it is reported by customer and has a priority severity position2.1 and previously.

Related topics“Common components” on page 72“Installation and Migration” on page 73“Servers and Stations” on page 74“Controllers and Tools” on page 75

71

7.1 Common components

Experion Station - Faceplate

PAR Function Description

1-4YL169BExperion Station -Faceplate

Missing point description on (fpcommon shape) faceplates, for example,sysdtltpspid_fp.

Table View

PAR Function Description1-F8BHKD Table View [SFT] Mini trend for SCM is not displayed in station.

Network - CNI

PAR Function Description1-WCZEO9 Network - CNI CNI Line error 3416. 3rd time lost IO rack same remote IO rack.

Server - TPS Integration


1-452JMJPServer - TPSIntegration Problems with non-unique messages sent from CL.

7 PROBLEMS RESOLVED


7.2 Installation and Migration

Server - Installation and migration


1-6QSA66QServer - Installation andMigration Update migration plug-in to support migration of OTP favorites.

OPM-On Process Migration


1-6WY5OFZOPM-On ProcessMigration

[DEE#29559] The Patchdb.exe fails in scenarios where EMDB is notopted as "Add-on Features".

7 PROBLEMS RESOLVED

73

7.3 Servers and Stations

Servers and stations


1-6RXJDL7 Server - RedundancySystem Alarm Priority overrides are not being migrated correctly forsome Server Redundancy alarms.

1-6Q8M0LX Server - ReportsThe performance statistics report may show incorrect average data ingraphs.

Detail Displays


1-3QFNDMJ Detail DisplaysStation number in Flex Station configuration page reverts to 1 whenswitching between tabs.

7 PROBLEMS RESOLVED


7.4 Controllers and Tools

Control Builder - Configuration Form


1-6O1VOTBControl Builder-Configuration Form DST Event every 15 minutes.

1-Z3FUD5Control Builder-Configuration Form

[PCT] Assigning CMs' with CDB blocks to ACE/C300 CEE fails withCDB not compatible with execution.

Control Builder - Fieldbus


1-6ZO4YSZControl Builder -Fieldbus FIM2 Device Replacement Fails.

Control Builder


1-5J5YYYF

Control Builder -Change Parent/UserDefined Template

Not passing the signal from one CM to another CM after doing Changeparent Operation.

Control Functions - Batch


1-5FBR8UZControl Functions –Batch C300 controller crashes when reference to a non-peer struct parameter.

OPM-Upgrade Tool


1-6SQ71FP OPM-Upgrade Tool[SFT_BL] Upgrade tool check for NTP configuration for controller failswhen NTP is correctly configured.

Profit Loop Assistant

PAR Function Description1-3KWWNT3 Profit Loop Assistant Experion R430, Profit Loop, Step Testing Bug in Level Loops.

7 PROBLEMS RESOLVED

75

7 PROBLEMS RESOLVED


8 Special considerations

This chapter provides the details of special considerations.

Related topics“SmartLine Transmitter Faceplates” on page 78“ELCN Bridge and Appliance Node Migration (1-8MXCD67)” on page 79“Control Firewall 9 (CF9) Connections (1-8G8SN4J)” on page 80“Migration from Experion R3xx to R501” on page 81“RSLinx Classic software and Experion R501 (1-86VLEH5 and 1-8H5CPBD)” on page 82“Qualified/Supported FTE switches for use with Experion LCN” on page 83

77

8.1 SmartLine Transmitter FaceplatesDescription:The new SmartLine transmitter faceplates currently cannot make use of the additional transmitter informationmade available by HPPA due to some technical constraints. The information about the specific transmittermodel is unfortunately essential for the faceplates to have the most accurate display of the data. As a result, thefollowing limitations apply:

• For SmartLine pressure transmitter, the faceplate is not able to show the type of pressure measurement,whether it is absolute, gauge or differential pressure, as descriptions for the analog and digital PVs. Insteadthe faceplate can only show “pressure” as a generic description.

• For SmartLine pressure transmitter which measures either absolute or gauge pressure, the dynamic variableTV which shows static pressure does not exist. TV exists for differential pressure transmitter and should beshown on the faceplate. The faceplate does not have the information to determine whether TV exists or not,and has to resort to showing TV regardless of the type of pressure measured. This means for an absolute orgauge pressure transmitter, the faceplate shows NaN for TV.

• For SmartLine temperature transmitter, ideally the faceplate should show only one sensor temperature as TVfor a single-input transmitter and two sensor temperatures as TV and QV for a dual-input transmitter. Thefaceplate, without the information to determine whether the transmitter is single-input or dual-input, has toresort to showing both TV and QV for now. This means for a single-input temperature transmitter, thefaceplate shows NaN, zero or some meaningless value for QV.

8 SPECIAL CONSIDERATIONS


8.2 ELCN Bridge and Appliance Node Migration (1-8MXCD67)Description:The Controller Migration Wizard (CMW) enables automated on-process upgrade of a controller firmware froma prior Experion release to the current Experion release. This automated on-process migration using ControllerMigration Wizard is currently not supported for the ELCN Bridge and ELCN Appliance nodes, that is, when theuser selects the ELCN Bridge or ELCN Appliance Node in the monitoring side of Control Builder and navigatesto ‘Controller’ menu bar item, the option ‘Migrate’ will be grayed out.

Consequences:The on-process or off-process upgrade of the ELCN Bridge or ELCN Appliance node firmware cannot be doneusing the Controller Migration Wizard.

Workaround:The on-process and off-process upgrade of ELCN Bridge or ELCN Appliance node firmware should be donemanually using the Firmware Manager Tool. Refer to the ELCN Overview and Implementation Guide, section“Updating Firmware on Operational UEAs” and follow the steps for upgrading the firmware of ELCN Bridgeand ELCN Appliance nodes.


79

8.3 Control Firewall 9 (CF9) Connections (1-8G8SN4J)Description:The Control Firewall (CF9) module provides eight Downlink ports for FTE connections to C300s and Series CFIMs within a Series C cabinet as well as FTE Bridge modules (FTEB) in a Series A Chassis I/O chassis. It hasa ninth port for an uplink connection to the supervisory FTE network and level 2 control area.

CF9 connection requirements• Always connect the Control Firewall uplink port to an L2 switch.• Do not stack the Control Firewall.• Connect the Control Firewall to an interface configured for portfast.• Connect All Series C FIMs and C300s to a Control Firewall Downlink port.• Connect any FTE Bridge (FTEB) module communicating to a C300 to the same Control Firewall as the

C300.

Consequences:In case an L2 Switch port gets connected to CF9 Downlink port by accident, the CF9 module will drop Uplinkconnection to the supervisory FTE network.

All nodes connected to that CF9 module report permanent silent for that interface (either FTE A or B) for about4 minutes.

Workaround:Verify CF9 connections according to the requirements mentioned in this section. Remove connection betweenL2 switch and CF9 Downlink port to recover operation.



8.4 Migration from Experion R3xx to R501Description:A direct migration from Experion R3xx to R501 is supported. Following are the important points that oneshould take care during migration planning and execution:

Migrations from R301.x to R501.x• Migration of server, client and ACE from Experion R301.x to R501.x has to hop through an intermediate

release. Contact HPS Migration Center of Excellence (COE) to determine the correct intermediate hop thatshould be selected.

• Controllers and IOs in Experion R301.x firmware can be migrated on-process or off-process directly afterthe servers have been migrated to Experion R501.x. Refer to the “Supported controller migration paths”section in this document for more details. Note that while migrating C300 and FIM4 modules from ExperionR301.x firmware to R501.x, an intermediate release (R400.1-96.396 is recommended while migrating toExperion R501.1) has to be selected using the “Migrate components to Latest service pack” option in theController Migration Wizard. Once the migration to the intermediate hop is completed, migrate the moduleto Experion R501 using the “Migrate components to Latest release” option in the Controller MigrationWizard.

• All modules other than C300 and FIM4 can be migrated from Experion R301.x firmware directly to R501.xusing the “Migrate components to Latest release” option.

• Any mandatory patch required for migration on Experion R301.x has to be installed before commencing themigration.

• In a multi cluster system, interoperability is supported between Experion R301.x and R501.x clusters(ensure to use Experion R301.3 Server Patch093) so that the multi hops can be carried out on the samecluster consecutively before moving on to the next cluster.

Migrations from R31x.x to R501.x• All supervisory nodes including server, client and ACE can be migrated from Experion R310.3/R311.3

directly to R501.x.• Controllers and IOs in Experion R31x.x firmware can be migrated on-process or off-process directly after

the servers have been migrated to Experion R501.x. Refer to the “Supported controller migration paths”section in this document for more details. Note that while migrating C300 and FIM4 modules from ExperionR31x.x firmware to R501.x, an intermediate release (R432.1-10.97 is recommended while migrating toExperion R501.1) has to be selected using the “Migrate components to Latest service pack” option in theController Migration Wizard. Once the migration to the intermediate hop is completed, migrate the moduleto Experion R501 using the “Migrate components to Latest release” option in the Controller MigrationWizard.

• All modules other than C300 and FIM4 can be migrated from Experion R301.x firmware directly to R501.xusing the “Migrate components to Latest release” option.

• Any mandatory patch required for migration on Experion R31x.x has to be installed before commencing themigration.

• In a multi cluster system, interoperability is supported between Experion R31x.x and R501.x clusters(ensure to use Experion R310 Server Patch680 and Experion R311.2 Server Patch243) to facilitatemigration.


81

8.5 RSLinx Classic software and Experion R501 (1-86VLEH5 and1-8H5CPBD)

Description:• The Experion Allen Bradley SCADA interface via RSLinx is not supported with Experion R501 due to

issues found with RSLinx integration.• Also, if the PLC is interfaced with an Experion system through Honeywell’s TC-CEN021 module, the PLC

cannot be contacted through RSLinx Classic v3.9.

Consequences:• Experion system is not able to fetch values of the Allen Bradley PLC points configured through Quick

Builder.• If the TC-CEN021 is being used to interface with the PLC, the communication to PLC breaks down from

the configuration node.

Workaround:• None. If you are using the Allen Bradley SCADA interface via RSLinx in an earlier release of Experion, do

not migrate to Experion R501 for now. Honeywell is working on this issue with Rockwell.• Replacing the TC-CEN021 with Rockwell’s latest Ethernet Interface Module “1756-EN2T” will resolve the

communication issue with the PLC from the configuration node.



8.6 Qualified/Supported FTE switches for use with Experion LCNDescription:In Experion R501, HP switches are not qualified for use with ELCN nodes. Instead, you can use all qualified/supported Cisco FTE switches, for a list of qualified/supported Cisco switches, refer to the latest ExperionPlatform Fault Tolerant Ethernet (FTE) Specification and Technical Data.

Also, Huawei switches are not supported for use with TPN/ Experion TPS nodes.


83



9 Known issues

This chapter provides the information about the Experion issues and workarounds.

AttentionExperion PKS R501.1 Software Change Notice reflects only Product Anomaly Reports (PARs) with priority severityposition 2.1 and above.

The PARs positioned at 2.2 and below are not included in this Software Change Notice.

NoteSome of the ELCN issues in this section are tagged with RELCN-<unique identifier>/RELCNTN-<uniqueidentifier> indicating that they are tracked in JIRA database as opposed to PARs in Siebel database.

Related topics“Common components” on page 86“Installation and Migration” on page 93“Servers and Stations” on page 99“Controllers and Tools” on page 101“PDF Documentation ” on page 120

85

9.1 Common components

Experion - TPS Infrastructure


1-4K5UHS7 Experion - TPSInfrastructure

Description: Deselecting Classic Faceplate selection for group displayconfiguration, this is a common Configuration for all displays

OPC Gateway


1-26I375 OPC Gateway

Error Indication: Refer to Engineering Notes.

Description: Some parameters of OPC Gateway cannot be referencedthrough parameter connectors.

Recovery: None

Workaround: None

1-2GZIVP6 OPC Gateway

Error Indication: Data values coming from the OPC Gateway mayfreeze based on incorrect OPC Server function.

Description: Once the OPC Gateway subscribes to an OPC Server for adata value, it is unable to detect if the OPC Server has stopped updatingthis point correctly. This can be visible where the data is seen to be"frozen" coming from the OPC Gateway but a new connection to theOPC Server by another client can get correct "live" data.

Recovery: The OPC Gateway is unable to recover only a single datavalue. If an OPC Server stops updating one of the points to the OPCGateway one of two actions can be taken. (1) Remove all requests forthis point by clients of the OPC Gateway. This requires unloading thesepoints from Monitor. (2) Set the OPC Gateway to IDLE. This will resultin the connection to the OPC Server being closed and ALL DATA fromthe OPC Gateway will go to Failsafe values. Commanding the OPCGateway to RUN will restore all data from all points coming from theOPC Gateway.

Workaround: None

Signon Manager


1-4T1DB5N Signon Manager

Error Indication: Signon Manager does not provide correct access.

Description: Signon Manager does not provide correct access when thePC Universal Station is used both locally and remotely.

Recovery: Use the PC Universal Station either locally or remotely, butnot in both modes.

Workaround: If the PC Universal Station is to be used locally, then it isto only be used locally; if the PCUS is to be used remotely, then it is toonly be used remotely. Setting up a PCUS to be used both locally andremotely is not currently supported.

9 KNOWN ISSUES



1-5X96F9U Signon Manager

Error Indication: New ACS card readers’ functionality.

Description: New ACS card readers do not function with MFA orSignon Manager.

Recovery: Users will have to continue with existing card readers or usethe Lumidigm fingerprint reader.

Workaround: None. Users will have to continue with existing cardreaders or use the Lumidigm fingerprint reader.

1-6O9TJO5 Signon Manager

Error Indication: FPR icon getting disabled in the MFA UI.

Description: If Windows logon is disabled through a domain policyupdate, the Fingerprint reader is disabled after it has been used to unlocka workstation.

Recovery: Reboot required.

Workaround: Reboot the workstation to re-enable the fingerprintreader.

1-6VXTJ53 Signon Manager

Error Indication: FPR icon disabled after connecting to the FPRdatabase in non-Experion node.

Description: FPR icon disabled after connecting to the FPR database innon-Experion node and restarting the Flex node.

Recovery: None

Workaround: None

Redirection Manager


1-6KKT1OB Redirection Manager

Description: Manual switchover option is not available in Experiondual-primary/migration use case.

Recovery: None

Workaround: In order to force a switchover in this scenario you willhave to bring down the currently-connected Primary.

System Management


1-1EYHNCP System Management

Error Indication: Missing Managed Component alarm in alarmsummary.

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

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

Workaround: Same as the Recovery, Restart System Event Provider.

9 KNOWN ISSUES

87


1-28CKTBT System Management

Error Indication: The memory usage for the System ManagementSynchronized Repository service (SyncRep.exe) rapidly increases onmultiple nodes on a network and network utilization increasessignificantly. There may be system performance impact, and thesynchronization of alarms between the nodes may be delayed. If asyncrep memory leak occurs on only a single system, it is not this issue,and this recovery procedure does not apply.

Description: This behavior has been encountered on only one networkto date, and only under the specific scenario of unplugging the currentprimary server from the network, and then later plugging it in again.Warning: until there is a fix for this issue, all sites should avoid theabove scenario. Even under this specific scenario, the frequency ofoccurrence of the syncrep memory leak is low.

Recovery: Contact Honeywell TAC for more information about thisissue.

Workaround: The best way to work around or avoid this problem is toavoid the specific scenario where this has been observed (seeDescription above). If this issue should occur even once at a site, thefollowing procedure is recommended in order to prevent repeatedoccurrence:

• Log on to one of the systems affected using a domain administratoraccount.

• Open the system management display. • Ensure the correct set ofcomputers displayed is correct for your current configuration.

• Right-click the scope item (domain or OU) in the left pane andselect properties.

• In the properties dialog, as the Settings Source, select one of thenodes that is properly configured for the Synchronized Repositorysettings (in particular, the multicast address).

• In the Synchronized Repository Configurations section at thebottom of the properties page, for each of the three selectable valuesfor Repository Name (TPS_ComponentInfo, TPS_SysEvt, andTPS_SysEvtExt), set the value of Maximum Response Time (ms) to250.

• Click OK or Apply, which will cause the Save CommonConfiguration dialog to appear.

• This dialog will list all the nodes the above settings will apply to.• Check the list, and if any nodes are red, determine the cause, and get

them back on-line if possible, as this timing change will not beapplied to nodes that are not running, only to the nodes that have thestatus Connection OK.

• Click the OK button to apply the changes. For each node thatdisplays Connection OK, the status should change to “Configurationinformation was changed successfully.

• Once this process has completed, click the Close button.

9 KNOWN ISSUES



1-69ZB9N8 System Management

Error Indication: Failed to restart SES and SPS after stopping fromlocal and remote node.

Description: Unable to start SES and SPS Components from SystemManagement Display on local and remote node.

Recovery: There are two options:

• Restart the node where the SES and SPS are failed to start.• From windows task manager kill the processes “spsdss.exe” and

“sysevtsvr.exe”. Try starting the SES and SPS components fromSystem Management Display.

Workaround: None

1-MNAFT7 System Management

Error Indication: Server data connection is lost.

Description: Server lost data connection to System management bylaunching the L2.5 switch display from the station. Issue is caused byslow response from the switch.

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

Workaround: None

1-61Z3X71 SafeView

Error Indication: when managing a remote-app window (vs. remote-desktop) in SafeView, if the window is explicitly positioned bySafeView, the pointer coordinates may be offset.

Description: when using Microsoft remote-app to remote a singleserver application, using RAIL protocol, and managing that remote-appwindow in SafeView, the mouse/pointer coordinates may be offset onthe SafeView window as compared to the server host where theapplication is actually running. This is due to the Microsoft RAILprotocol not propagating programmatic window positioning, as it doesfor manual window positioning, for remote-app windows. SafeViewmay programmatically reposition a window when position/size arespecified in the workspace for a given managed display.

Recovery: once a display's location is offset between the client andserver, it must be closed on the client, and then re-invoked withoutbeing programmatically repositioned by SafeView.

Workaround: either do not manage remote-app displays in SafeView,or do not explicitly configure position/size for a remote-app managedwindow. Alternatively, you may take advantage of the default-positioning behavior, in which a remote-app window is positionedwhere it was last-positioned. To do this follow these steps: 1. invoke aremote-app window outside of SafeView, to a specific location (e.g. alower-left screen); plan to always use this position for this remote-appdisplay. 2. always pick up the remote-app window in a SafeViewwindow in that same location (e.g. the lower-left screen).

9 KNOWN ISSUES

89


1-7J85UT3 SafeView

Error Indication: Use of Microsoft window-animation feature causesbrief cosmetic issue upon display invocation in SafeView.

Description: If Microsoft is configured to diverge from the standardExperion configuration in regards to Microsoft window-animation, theremay be an annoying visible brief animation in which a display - uponinvocation in SafeView - appears to iconize/de-iconize.

Recovery: there is no needed recovery, as the issue is purely cosmeticand temporal.

Workaround: this issue does not occur in standard Windowsconfiguration in Experion; if the standard Windows setting has beenadjusted and the problem is seen, it is recommended to revert theWindows setting per standard Experion installation, by modifying the<Animate windows when minimizing and maximizing> WindowsSetting. Location: Control Panel > System and Security> AdvancedSystem Settings> System Properties> Advanced Tab> PerformanceSettings.

9 KNOWN ISSUES


Series A IO Modules


1-2IAI1H5 Series A IO Modules

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

Description: If the following actions occur while using the topology ofa C300 controlling Series-A I/O through an FTE Bridge module in theI/O chassis and if a Serial Interface Module resides in the same chassisas other Series-A I/O Modules: 1) Multiple Serial Interface I/O moduleblocks are configured to map to the same physical Serial InterfaceModule in the I/O chassis by using the same FTE Bridge Name andIOM Slot Number. 2) Both Serial Interface I/O module blocks areloaded to the C300. 3) A switchover is performed. Then on switchoverthere may be a momentarily loss of communication between the C300and other Series-A I/O modules which reside in the same chassis as theFTE Bridge and Serial Interface Module. If a PID block is providing aprocess value to the Series-A I/O channel this loss of communicationmay be observed by the Mode of the PID block shedding to Manual. Nowarning or error is raised during the configuration or load operation ofthe Serial Interface Module blocks.

Recovery: Perform all of the following steps:

1. Delete all Control Modules containing Serial Array Channelsassigned to both of the Serial Interface Module blocks.

2. Delete both the Serial Interface module blocks.3. Only one Series A IO Module block may be configured to map to

any one physical Series-A IO Modules.

a. Identify the correctly configured Serial Interface Module block.b. Load the correctly configured Serial Interface Module block.c. Load all Control Modules containing Serial Array Channels

assigned to the correctly configured Serial Interface Moduleblock.

4. Switch off power to the I/O chassis containing the FTE Bridge andSerial Interface Module.

5. Perform a Checkpoint Restore to the C300.6. Switch on power to the I/O chassis containing the FTE Bridge and

Serial Interface Module.7. For verification of the recovery perform a switchover of the C300

and verify the connection is not lost to the other Series-A IOmodules 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 toSeries-A Serial Interface Module through FTE Bridge topology take thefollowing precautions:

1. Before loading Serial Interface Module blocks to a C300 verify thepath configuration details are not identical to any currently loadedSerial Interface Module blocks.

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

9 KNOWN ISSUES

91

Software Configuration Management - Phoenix


1-5HLSY0B Software ConfigurationManagement - Phoenix

Copy the package available from DGIT Share. Install DVD-2-->PACKAGES-->STAC-FDM folder to Experion Installed node. Thisworkaround is applicable for Server, console and flex nodes:

1. Get the STAC-FDM package (along with zip file) from the DGITshare.

2. Run the following command in cmd.exe (Run as administrator).Also copied the command in the attached test file. Unable viewproperly in TAC DB Query link.Msiexec.exe /I“<PackageLocation>\STAC-FDM.msi” /qb!Example:Msiexec.exe /I“C:\STAC-FDM\STAC-FDM.msi” /qb!.

3. Update the passwords for the below Services (Do not change theService account) Experion PKS FDS CommunicationServerExperion PKS Field Device ServerExperion PKS HARTMultiplexerFDM Safety Network Interface.

4. Follow this step only on Server nodes - Extract the contents ofzipped folder "Release" to default path C:\ProgramData\Honeywell\FDS\Repository or if CIP [Runtime data path]\Honeywell\FDS\Repository.

9 KNOWN ISSUES


9.2 Installation and Migration

Rockwell Network


1-11H1RD1 Rockwell Network

Error Indication: RsLinx does not show the Series A IO/SIM Cardwith Module Icon.

Description: RsLinx application does not show the Series A IO/SIMCard with Module Icon.

Recovery: None

Workaround: None

1-13QB7PX Rockwell Network

Error Indication: RsLinx automation tool fails when executed.

Description: RsLinx Automation does not stop the required servicesand throws 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.

Experion Migration


1-88GK081 Experion Migration

Error Indication: During migration from an earlier release to R501, theInstaller may pause indefinitely during the Restore Server Data step.

Description: During migration from an earlier release to R501, theInstaller may pause indefinitely during the Restore Server Data step.

Recovery: Open Windows Task Manager, locate the scpevt.exe task andmanually stop the task using Task Manager.

Workaround: None

Third Party Components


1-11KCT39 Third PartyComponents

Error Indication: Profibus IO module appears RED on Monitoringwith the PFB Communication Status shown as ""PfbOffline andDEVSTATUS parameter 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 SSTblock at the same time. This was also seen when chassis IO modules areloaded in a particular order like Pulse input module, then AnalogOutput Modules and then SST module along with its I/O modules.

Recovery: Delete all the modules and load the Profibus modules firstand then load the other chassis I/O modules.

Workaround: None

9 KNOWN ISSUES

93


1-17FPCH Third PartyComponents

Error Indication: Internal error occurs when you try to open thedocuments related to SST_PFB_CLX in SST Profibus installation CDpart 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 cannotbe used which will 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 isresolved.

1-OIW24V Third PartyComponents

Description: Trying Disable-Enable of FTE Yellow-Green causing theBSOD Crash of Server Grade.

Recovery: Reboot the machine for each disable or enable of theadapter.

Workaround: Invalid test case, if the machine is ON PROCESS. Donot disable all adapters and enable all adapters without a reboot.

Reboot the machine for each disable or enable of the adapter.

1-PPG7GR Third PartyComponents

Error Indication: C200 5ms controller is losing Connection withServer Intermittently resulting in loss of View at Control Builder(everything turns RED at Monitoring side) and Loss of View at Stationfor C200 Detail Display.

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 isdisconnected as per below: Remove Control Net Cable A of Non-Redundant C200 5ms & Remove Control Net Cable B of ACE. RemoveControl Net Cable B of Non-Redundant C200 5ms & Remove ControlNet Cable A of ACE. In the above two Scenarios, Loss of Peer-to-peerdata communication between C200 & ACE is observed which isexpected. But in this scenario, the C200 5ms is losing Connection withServer Intermittently (disconnects and connects back) and henceresulting in Loss of View at Control Builder (everything turns RED atMonitoring side) and Loss of View at Station for C200 Detail Display.

Recovery: Reconnect the cables back.

Workaround: None.

1-TVWXHJ Third PartyComponents

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 anddigital output modules remain in red color in monitoring side withDEVSTATUS set to PfbNotInRun.

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

Workaround: None.

9 KNOWN ISSUES



1-WBOGBR Third PartyComponents

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

Description: After upgrading the SST-PFB-CLX module to firmware6.07 and loading a big configuration (exceeding what is mentioned inSST specification of 246 words output data, 248 words input data and250 words status), two modules get bricked. LCD on the modulebecomes blank with no indications. The OK LED becomes OFF andone or both of the COMM LED and SYS LED becomes ON (RED).Restarting the modules does not help to bring them back. Not sure ifloading big configuration resulted in the bricking. Communication withMolex on the same is in progress.

Recovery: None.

Workaround: None.

1-1275R3B Third PartyComponents

Error Indication: Upon removal and re-insertion of Profibus cablefrom both primary and the secondary PGM, output channels becomebad in TURCK and SiemensET200M DSB.

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

Recovery: Perform PGM Switchover, all the output channels willbecome good.

Workaround: None

1-494825W Third PartyComponents

Error Indication: Upon PGM Switchover all the channels of HARTPDC in TURCK DSB goes Bad momentarily.

Description: When a HART channel is configured for Secondaryvariables (HART data) but HART transmitter is not connected in thatchannel, then corresponding channel status will be Bad_HARTError.But upon switchover the other channels in the PDC will become BADfor few seconds.

Recovery: The Channels recover automatically.

Workaround: Do NOT configure Secondary Variables (HART data)for the channels in which you are NOT connecting HART device/transmitter.

1-6Y69I6R Third PartyComponents

After PGM RRR, all DSB's that's having DPV1 records configuredneed to be deleted from CB monitoring side and then reload it from CBProject side.

9 KNOWN ISSUES

95


1-8DVCN3B Third PartyComponents

Description: If PROFIBUS slaves configured with PGM are enabledfor DPv1 messages, then on switchover of PGM the slave drops masterand connects. On this disconnect some slaves (other than TURCK,P&F, STAHL and so on) may drop the output leading to failures in theplant.. Honeywell haven’t yet identified the exclusive list of slaves thatexhibit this anomaly. SIMOCODE DP Configured with PGM, alwaysdrops master and field outputs on PGM switchover for a particularconfiguration (as explained under Actions Section). Project customerneeds to analyze their requirements in order to find out whether or notthey are affected by the issues.

Workaround: The SIMOCODE programming software comes with~10-15 examples for the main use cases of SIMOCODE. 90% of allSIMOCODE users are re-using these examples either 100% or as abaseline for their own SIMOCODE implementation, becauseSIMOCODE is a kind of a small PLC. In these standard examples thereare spare places for the status and command data in the control andstatus word which the programmer could utilize for the programcustomization (basically he could redefine anything, but there aresufficient spare places and most of the programmers would be too lazyto redefine anything from scratch…). In the program examples allcommands (with the exception of the remote control bit) are just usingthe rising edge to perform a command at the device. So in normaloperations these bits are “0” or they can drop to 1->0 any time withoutreaction of the device. As a result a SIMOCODE user either reusing theSIMOCODE example programs 100% or following the samephilosophy in their custom application, shall not suffer from thisredundancy failover behavior. For the users coming from old hard-wired times and as a result they believe it is the safest way to havecritical signals transferred as a steady “1”, because in the old times ifsomebody cut the wire this signal just went to “0” and stopped theprocess. Nowadays this is of course not fully correct anymore, becausefor a bus system there are different mechanisms to detect a broken wireand a cut wire is only stopping the update of the values at the device,but not dropping the value unless the device detects it and reset itinternally.

Recovery: None

Workaround: To use a steady “0” signal for the good indication andnot a steady “1”. This way they can sustain the redundancy failoverwithout issues. However, Honeywell is working on a fix for a solutionwithout workaround.

1-57RIO4V Profibus InterfaceModules

Description: Backup PGM taking even IP address even afterconverting it in to non-redundant PGM.

Recovery: PGM will recover to NODB state and will start odd IPaddress.

Workaround: Flash the backup PGM module with any other PGMfirmware.

9 KNOWN ISSUES


INS-Installation


1-BAEM01 INS-Installation

Problem: Machines that have been updated with the latest Daylight-Saving Time (DST) update (e.g., KB955839, December 2008cumulative time zone update) must have that DST update uninstalled inorder for the Experion media to proceed successfully with its install.This is due to the fact that Experion media attempts to install KB933360(August 2007 cumulative time zone update) which is an old version ofthe DST updates. Older versions of DST updates fail their install if theydetect a newer DST update on the machine.

Workaround: During migration, Please uninstall any DST updatesprior to using Experion media. You can uninstall a KB by locating thatKB in the Windows directory then executing its spunist.exe. Forexample, if DST KB955839 was installed on the machine, then beforemigration, execute the KB uninstall file: c:\Windows\$NtuninstallKB955839$\Spuninst\spuninst.exe. This problem will becorrected in the future by removing DST updates from Experion media.For more information on DST, please see Microsoft’s website: http://support.microsoft.com/gp/cp_dst.

1-FHI43O INS-Installation

Error Indication: System is not function after running server namechange utility after configuring the system.

Description: This utility does not support computer name change.noderenameutil.exe available under C:\Program Files\Honeywell\Experion PKS\Utilities\NodeRenameUtil\ has to be used for computerchange. Computer name can be changed before doing anyconfigurations in the system.

Recovery: None

Workaround: None

Installation ESIS


1-6FVAF0O Installation ESIS

Error Indication 1: Some Installation or migration steps fail and thenumber of steps for installation\migration are very less as compared tothe general number of steps.

Error Indication 2: During the migration of FTE systems, theSummary page of DialogManager shows the network as "None" forSupervisory and EPN networks. If this is ignored, the FTE driver doesnot get installed on the system which might lead to installation andfunctional issues.

Description: This issue is observed when the user clicks the "Next"button on the DialogManager screens without waiting for the dialog toload completely which leads to loss in information required for install.

Recovery: None

Workaround: The user needs to start the installation\migration again byensuring that the complete dialog is loaded before they click on "Next"on each dialog.

9 KNOWN ISSUES

97

C200 to C300 Upgrade


1-7IO82RF C200 to C300 Upgrade

Workaround:

1. Go to QVCS Manager > Query > Select Revert Label from Queryon dropdown list > Select label to be reverted to from Valuedropdown list > Click List.

2. Select respective deleted object which appears in the list.3. Right Click on the selected object > Select Revert Labels > Select

Apply/Remove > Select To selected version > Remove label fromApplied Revert Labels(for the version).

4. Follow step 3 for all the deleted objects in the list. Ensure label isremoved for all the deleted instances of the particular object.

5. When user tries to revert to a label applied before upgrade, revertshould be successful.

BCC Migration


1-8JPHAST BCC Migration

Error Indication: On a BCC system after failing over to the alternateserver location both servers become primary, after a short while one ofthe servers shall drop back to backup.

Description: On BCC systems when failing over between serverlocations both Servers in the backup server location become primary fora short while before one goes to backup state. This race condition cancause a loss of view.

Recovery: Wait for a short time until one of the servers drops back tobackup.

Workaround: None

ELCN


RELCN-1171 andRELCNTN-443 ELCN

Description: When assigning or changing the LCN node number of anyLCN or ELCN node, it is imperative that the intended node number isnot already in use by another running LCN or ELCN node. If aduplicate node number situation is encountered, the invalid duplicatenode will fail, and the existing running node may become ISOLATEDfrom some LCN and ELCN nodes.

Recovery: To recover from this situation, power-off the invalid node,change its LCN node number to an unused LCN address, power it backon, and reload the existing running node which may have becomeISOLATED.

9 KNOWN ISSUES


9.3 Servers and Stations

Detail Displays


1-8IEVJ0E Detail Displays Please ignore these error message shown. There is no functional impactdue to this error message.

1-8HFARGN Detail Displays

Error Indication: Powered down servers can be shown as running onthe server redundancy display page.

Description: Server Redundancy Display always showing servers asrunning even if they are powered down. If you perform a Server Syncthe backup Server status will update as expected. However if youperform a shutdown of a Server the Server status will remain as running.

Recovery: Attempt to do a manual sync to the powered down server.

Workaround: Check link status for servers to validate redundancystatus, if all server links are down then the server is unavailable.

Server - Alarm/Event


1-7Q18HVF Server - Alarm/EventRunning a report of the alarm and event summary shows that the valuesare independent and correct. However, when viewed from the eventsummary, it is not updating / populating correctly.

HMIWeb Station - Displays


1-5UEU04N HMIWeb Station -Displays

Description: It has been observed that, after migration from an olderrelease to R501, any .html File( ECC Generated report ) is gettingopened in HMI Web builder instead of Internet Explorer.

Workaround 1:

If .html file (ECC report ) opens up in HMI Web builder then go toControl panel > Programs > Default Programs > Set Associations andset association of .html to Internet explorer from HDB.exe.

Workaround 2: Open internet explorer and just drag and drop ECCreport (html file ) in it.

9 KNOWN ISSUES

99

Station Server Script Editor


1-8NK13H9 Station Server ScriptEditor

Error Indication: Server scripts cannot be committed and will insteadbe deleted when trying to commit Server Scripts by copying and pastinginto the Station Server Script Editor.

Description: When trying to commit Server Scripts using the StationServer Scripting Editor by copying text and pasting into the scriptdialog, the server script cannot be committed and will be deleted.

Recovery: None

Workaround: After pasting the text, insert a space after all of the text(or apply any other manual text edits) before trying to commit thescripts.

9 KNOWN ISSUES


9.4 Controllers and Tools

CDA-Control Data Access


1-8JGJBW1 CDA-Control DataAccess

Error Indication: C200E reported Err2123 BAD EE code during runtime.

Description: This occurs very rarely. If it occurs there will be acomplete loss of view/control for that controller.

Recovery: Delete the strategies from monitoring side and reload.

Workaround: None

1-PK0TEY CDA-Control DataAccess

Error Indication: C300, FIM4, FIM8, PGM may power cycle toNODB.

=

Description: Multiple bootp servers may not be returning identicalinformation, causing controllers to invalidate their databases.

Recovery: Reload configuration.

Workaround: Disable all but one bootp server.

CDA-Embedded


1-1NJX441 CDA-Embedded

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 themto make them work properly.

Recovery: Restore checkpoint of ACE nodes and make the controlleractive.

Workaround: None

1-8HP0CM7 CDA-Embedded

Error Indication: Switchover causes P2P data freeze for up to 18Seconds in peers when UOC is responder.

Description: After about 18 seconds of value freeze the value startsupdating automatically, no manual intervention required.

Recovery: None

Workaround: None

1-8JEL0HR CDA-Embedded

Error Indication: Primary UOC got crashed after 30 continuousswitchover.

Description: observed only after 30 continuous switchover tests leadingto Loss of view and control.

Recovery: Reboot controller and Checkpoint restore or reloadstrategies.

Workaround: None

9 KNOWN ISSUES

101

CF-Control Function


1-7HX0PMR CF-Control Function

Error Indication: User cannot browse EPC block pins.

Description: User can type the EPC block pin names, but cannotbrowse them.

Recovery: None

Workaround: None

1-50PW9ZF CF-Control Function

Description: C300 sync breaks on inactivate and active CMs containingDEADTIME blocks.

Recovery: C300 syncs on its own immediately.

Workaround: Error may occur if a huge number of DEADTIMEblocks are activated together. Therefore, avoid activating CM containingtoo many DEADTIME blocks.

Control Builder


1-3S1VMJ7 Control Builder

Description: Control builder crashes while trying to create MAP block.

Recovery: Reopen control builder. Clear the lock on the created MAPblock if there is any.

Workaround: None

1-EYEHI9 Control Builder

Error Indication: After performing OPM from R211.1T04,HF2 toR311.2 the PMIOs associated with IOLINK is not able to readIOLINKCOLOR parameter.

Description: After performing OPM from R211.1T04,HF2 to R311.2the PMIOs associated with IOLINK is not able to read IOLINKCOLORparameter.

Recovery: None

Workaround: None

RELCN-1173 andRELCN-1124 Control Builder

Description: In some cases, the Control Builder node state icons do notdisplay the correct node state color as per the actual state of a node.

Recovery: None

Workaround: You can use one of the following displays to verify thestatus of a node:

• Control Builder - Main tab “Node State”• Experion Faceplate Display• UEA Front Panel Display• Native Window Display

9 KNOWN ISSUES


Control Builder-Bulk Build/Edit


1-11SICGP Control Builder-BulkBuild/Edit

Error Indication: Control Builder stops responding.

Description: While performing bulk edit operation, Control Builderstops responding with Run time error.

Recovery: Close and re-open the Control Builder.

Workaround: None.

1-12Y56T9 Control Builder-BulkBuild/Edit

Error Indication: Improper warning or failed error messages areobserved during save to ERDB operation of various workflow of BulkConfiguration Tools.

Description: The error messages like Entry does not Exist,configuration related errors are displayed with Failed status even thoughthe save to ERDB is successful.

Recovery: Ignore the improper errors with status as failed.

Workaround: Same as recovery.

1-3SHZPM6 Control Builder-BulkBuild/Edit

Error Indication: Improper failed error messages are observed during"Export as XML" operation of various workflows of Bulk ConfigurationTools.

Description: The Error message "Save to ERDB failed" is displayed tothe user with failed status for Export as XML operation. Thefunctionality is working fine and problem is only with showing theimproper error message and status. It misleads the user as the status ofthe operation is failed even if the Export as XML is successful.

Recovery: Ignore those improper errors with status as failed.

Workaround: None

1-45BBWBR Control Builder-BulkBuild/Edit

Error Indication: Bulk Build of loaded IOM moves channels fromtypical IOM to new IOM.

Description: Performing Bulk build operation of loaded IOM havingloaded channels (either old style assignment, reference blockassignment or just a loaded channel) through Smart builder, all thechannels which are present in old IOM(except the channels which areassigned in CM channel block in contained style) are moved to newIOM.

Recovery: Move channels manually to old IOM.

Workaround: Use the IOM typical which is not loaded. In R500 useEDB for Bulk Build operations.

1-3NHR0K1 Control Builder-BulkBuild/Edit

Error Indication: "Save to ERDB failed error is displayed.

Description: If you do not specify the new channel names for theReplica IOM in the configuration sheet, the existing channels in TypicalIOM is moved to the replica IOM.

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

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

9 KNOWN ISSUES

103


1-50P6T7T Control Builder-BulkBuild/Edit

Error Indication: Bulk Build of CM containing the OLE objectsresulting into CB crash.

Description: Bulk Build the CM (containing the OLE objects) usingBulk Configuration tool, it has been observed that after bulk build CB iscrashed.

Recovery: Restart the CB and use the clone feature to bulk build theCM.

Workaround: Use the clone feature in Bulk Configuration tool to copyfrom a CM typical.

1-6ESQ6LP Control Builder-BulkBuild/Edit

Error Indication: Bulk Build and assigning the channels resulted intosame channel number.

Description: It has been observed that if we are create SC AI, AO, DO,DI bulk channels using smart builder then assign same bulk channels torespective SIMIOM under project side. We have observed that after loadof SIM IOM & channels, the all channels no are shows as “1” inmonitoring side. If we are turn on single channel output (DO Ref block)from CM using DEVCTL then all other DO channels output are becomeon.

Recovery: to unassign all the channels first and Delete the SIMIOM inthis case. Create a new SIMIOM and then assign the channels usingManage IOChannels Option of Smart Builder.

Workaround: Needs to follow 2 Steps process to bulk build and assignChannels using Smart Builder as a workaround 1. Engineer can justbulk build the channel blocks using “Bulk Build Strategies” Option inSmart Builder. Do not do any IO assignment in this step. 2. Engineercan select all the Channels created in first step and Choose “Manage IOChannels” Option in Smart Builder to do IO Assignment which assignsthe Channel blocks correctly with proper channel number to thecorresponding IO module. Note: If channels are assigned to SIMIOMthen user need not specify even the Channel Num, Only SIMIOM nameis sufficient. If IOM is not SIMIOM then IOMName and Channelnumber both has to be specified.

Control Builder-Configuration Form


1-4SZ9242 Control Builder-Configuration Form

Error Indication: This error is seen upon executing the belowmentioned steps.

1. Configure C300 controller along with UIO1 or UIO-2 or DOmodule.

2. Configure few channels as DO channel from spare channel.3. Configure CM and drag DOREF blocks to it. Refer DO channels to

REF block.4. Expose onpulse or offpulse or PWM block pin to DOREF block and

keep DO type as a “Status".5. Click OK.

Description: No validation error prompted for onpulse, offpulse andPWM when DOTYPE=Status and DOREF blocks used. AlsoReproducible with UIO-1 and Series C DO module.

Recovery: Change the parameter value and try again.

Workaround: None

9 KNOWN ISSUES



1-6ASKHK5 Control Builder-Configuration Form

Error Indication: The user will not be able to navigate to other tabsfrom the DO Status Tab of a DO module in Monitoring side of ControlBuilder or Station.

Description: The issue occurs only with the below configuration. 1. ANOT block output pin is connected the Input pin of the same NOTblock. 2. The NOT block output pin is connected to the SO pin of 16 ormore DO channels (belonging to the same DO module) using parameterconnecter. This configuration has to be loaded and when the user isnavigating to the DO Status tab of the DO module in Monitoring side,he/she will not be able to navigate to other tabs.

Recovery: The Control Builder or Station has to be manuallyterminated and launched again.

Workaround: None

1-3L4KQ9D Control Builder-Configuration Form

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-4V5Q9HJ Control Builder-Configuration Form

Error Indication: 1. Loaded C300ME and loaded the strategies belongsto C300ME. 2. Activated all the strategies in monitoring side. To testRRR set the CEE STATE option in C300ME CEE as WARMSTART.Then for all the CMs started setting the CEERESTART option as"followCEE". It was observed that we are able to set it for few CMs(6-8CMs) but when we set for 9/10th CM CB crashes. This is seen everytime when we run this test.

Description: Control Builder crashes when CEERESTART is set in theCMs.

Recovery: Close CB and reopen again.

Workaround: None

Control Builder-Load


1-8BX52X9 Control Builder-Load

Error Indication: There is no error prompted to user on loading theUOC Controller if there are more number of activities configured in iton a heavily loaded system. But the TOTAL NUMBER OFACTIIVITIES parameter on Configuration form of CEE showsmismatch in number from project to monitoring.

Description: This issue is not reproducible on demand and can be seenon a heavily loaded system with only UOC Controller. When this issueoccurs this can be verified In the Control Builder error log by seeingsome join nested transaction error.

Recovery: Perform a Load While active operation on the CEE in orderto load the activities completely and rectify the mismatch in TotalNumber of activities number.

Workaround: None

9 KNOWN ISSUES

105


1-8HFAR5J Control Builder-Load

Error Indication: No error will be thrown to user but there can bebroken connections in the CM either receiving incorrect signals or notreceiving signals from the corresponding function block.

Description: Refer document Broken Connection Issue ScenariosALL.docx to know the scenarios in which Broken connection issue canhappen.

Recovery: User can recover from the issue by downloading all thereferred Control modules (SCMs, RCMs) which have connections to themodified control module.

Workaround: Whenever user performs any of the specified operationsas mentioned in document Broken Connection Issue Scenarios ALLUser has to load the modified CM along with all the referred CM /SCM's along with it to avoid broken connection issue.FINDTAGSTOLOAD.exe tool can be used after performingengineering operations like import export, change parent, deletion ofblocks etc. in order to know the list of CM's that needs to be loaded inorder to avoid broken connection.

Control Builder-Load/Upload/Update


1-SJ4W66 Control Builder-Load/Upload/Update

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 containingDO channels connected to DEVCTL blocks unless the IOM is present.

1-4KSJ8TD Control Builder-Load/Upload/Update

Error Indication: Control builder tree view shows incorrect CM Nameagainst the channel in Monitoring side even though CM is not loaded.

Description: When CM and channels are loaded together, if CM loadfails due to some reason, then IO channels which got loadedsuccessfully to monitoring side show the CM name in the tree view andin the form which they were associated to. But since CM's are notloaded successfully it should not display the CMname against theChannels.

Recovery: Reload the CM which had failed earlier.

Workaround: None

1-TNX8CL Control Builder-Load/Upload/Update

Error Indication: Control Builder stops responding on trying to re-loada strategy with dangling connection.

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

Recovery: None.

Workaround: Open the Control Module containing danglingconnection ( indicated as '????') and delete the dangling connection inControl Module. Reload the Control Module.

9 KNOWN ISSUES



1-68IJJAB Control Builder-Load/Upload/Update

Error Indication: Upload and update to project fails with an error“Overwriting loaded blocks is not allowed in systems using Fieldbus”for reference blocks configured with channels.

Description: Upload and update to project fails with an error“Overwriting loaded blocks is not allowed in systems using Fieldbus”for reference blocks configured with channels. This behavior is seen inAI, AO, DI, DO reference blocks configured with correspondingchannels.

Recovery: Perform UploadUpdate operation on the IO module itselfsuch that monitoring side changes gets updated to Project side.

Workaround: To prevent from this situation, use Upload/Update onIOM.

1-69Q1RV1 Control Builder-Load/Upload/Update

Error Indication: System allows to change the duty cycle for DOchannel when REDTAG is enabled.

Description: In monitoring view, when REDTAG is enabled, on reloadof such channel and error/warning should be thrown to the user thatREDTAG is enabled and should allow the user to continue with channelload.

Recovery: None

Workaround: User to confirm that channels are not in REDTAG beforeperforming Load.

1-6L3M1PS Control Builder-Load/Upload/Update

Error Indication: When Upload Update operation is performed onSCM's which has JUMPZone Configured then error is thrown to usersaying "Illegal Parameter Index JumpZOne (1,11) and upload andupdate operation fails for that SCM.

Description: Upload and Update operations fails for SCM configuredwith JumpZOne when done in Interoperable scenarios, that is, whenserver is in R500 and Controller is in Previous releases.

Recovery: None.

Workaround: Avoid doing Upload Update for such SCM's which hasJumpZone configured.

1-72WCYRR Control Builder-Load/Upload/Update

Error Indication: There will not be any error thrown to user butPrimary PID block will continue its execution even though Secondaryoutput reference block is deleted.

Description: When Primary PID block is in one CM and is writing toOutput reference block in another CM, Deletion of the CM with outputreference block from monitoring side should stop PID block executionand PID should show BADCTL and InitMAN should be ON. But PIDin primary CM continues to execute.

Recovery: Either delete the AO channel from monitoring side andreload again.

Workaround: None

9 KNOWN ISSUES

107

Control Builder-System Repository


1-PV3SMT Control Builder-SystemRepository

Error Indication: Peer-to-peer communication between CEE controllerand Experion Server points (SCADA, DSA, TPS, OPC, OPC Advancedpoint) fails with NaN values.

Description: If a server with incomplete information in SystemRepository (System Repository sync state can be observed from ServerRedundancy page) takes over the Primary role then, there is a highlikelihood to lose Experion Server points information in SystemRepository resulting in peer-to-peer communication failures betweenCEE controller and Experion Server points.

Recovery: None.

Workaround: None.

1-Y390VS Control Builder-SystemRepository

Error Indication: When QCS subsystem tries to validate points inServer through 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: Lowering the number of non CEE point handle requeststo SR per second would avoid this.

1-1RTR2H5 Control Builder-SystemRepository

Error Indication: CDA disconnects seen when performing "Load withcontents" of a controller.

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

Recovery: Perform switchover of servers to recover from the CDAdisconnect if the recovery doesn't happen automatically.

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

Control Functions - Batch


1-5P545LL Control Functions -Batch

Error Indication: Class based recipes over multiple C300's withindirect addressing fails the execution of the steps and transition.

Description: Expressions using Indirect Referencing over peer C300sdoes not work and hence results in failure of Step/Transition execution.

Recovery: None

Workaround: Reconfigure the strategies to be within the samecontroller.

9 KNOWN ISSUES


Control Kernel


1-XGHDCZ Control Kernel

Error Indication: An alarm generated from CAB function block mayappear active in Station, though it is in normal condition. This can becross verified by monitoring faceplate of the CAB function block.

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

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

Workaround: None

EBM-Controller


1-3QM82LT EBM-Controller

Error Indication: A step block displays an error of 2447 when trying toset a unit.

Description: You are unable to select a unit.

Recovery: Abort the strategy.

Workaround: None.

1-6CDPENZ EBM-Controller

Error Indication: C300 controller crashes when SCMs are commandedto run, with specific configurations.

Description: Controller crash is caused by the self-referencingGateOutputs in a Transition, or referencing the other Gate ouput inparallel transitions.

Recovery: None

Workaround: None It is advisable to run the ECC to ensure that thereare no strategies with this configuration. If the ECC flags suchconfigurations, the user is expected to reconfigure the expression to notuse the Gate output from the same Transition, or another parallelTransition and vice versa.

1-7JXC6Z9 EBM-Controller

Error Indication: Cannot recover Batch from scenarios where Phaseblock have communication errors.

Description: When Phase blocks have communication errors due tounderlying child being Aborted and or Reset, the Batch gets into a stuckstate and there is no way to recover except Aborting the Batch.

Recovery: None

Workaround: None

9 KNOWN ISSUES

109

EBM-Tools


1-VIAD8V EBM-Tools

Error Indication: The number of activities shown in CEE statistics Tabis different 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.

EIP-COMMUNICATION


1-6CROGAL EIP-COMMUNICATION

Issue: C300v3 configured with EIP IO's and/or EIP Tag requests,through EIM. Sometimes, a simultaneous switchover of both C300v3and EIM can cause disconnect and reconnect of all EIP IO's and tags.

Recovery: Issue recovers automatically.

Workaround: None.

1-81VFC5T EIP-COMMUNICATION

Error Indication: EIP armor point IO devices disconnects momentarilyon UOC switchover.

Description: On a UOC Switchover, the Armor Point IOs loaded to theUOC may get disconnected momentarily. The error is observed in theStation in form of a transient Communication Error Diagnostic Alarm.

Recovery: The IO modules connect back automatically after a briefperiod.

Workaround: Enable Consolidate Connections option when workingwith Armor Point IOs.

1-8EGALT9 EIP-COMMUNICATION

Error Indication: EIP devices disconnect permanently on restoringcheckpoint on UOC controller.

Description: A permanently disconnect of EIP devices might happen onrestoring checkpoint on UOC controller.

Recovery: Rebooting the EIP device recovers the error.

Workaround: None

1-8C9M091 EIP-CEE-EMBEDDED

Error Indication: EIP IO module do not generate alarms configuredagainst enumeration parameters.

Description: EIP IO module do not generate alarms configured againstenumeration parameters.

Recovery: None

Workaround: Configure the parameter data type to an integer type,save the template and reload the device.

9 KNOWN ISSUES


FF Interface Modules


1-3QIZ2V1 FF Interface Modules

Error Indication: New primary FIM4 fails with error 0x3b3 afterswitchover. This may result in loss of control of the FIM4.

Description: During stress testing of FIM4 redundancy withswitchovers in a lab environment a primary FIM4 failed with error0x3b3 after transitioning to the primary role. This failure has only beenobserved in a lab environment in a disruptive condition where loss ofpower to a large number of nodes was simulated, similar tosimultaneous fuse failures on 15 FIM4s. This testing results in high anddisruptive FTE network traffic due to multiple FTE nodes disconnectingand reconnecting which may be a major contributing factor. Control andview may be lost. The frequency of occurrence is seen once every 2700switchovers.

Recovery: Correct the cause of the initial switchover condition andrestart the module that failed with error 0x3b3. Review networkconditions and take corrective action to ensure the network is stable.

Workaround: Review network conditions and take corrective action toensure the network is stable.

Fieldbus Library Manager


1-89KASZV Fieldbus LibraryManager

Workaround:

1. Export the template file from Experion PKS R310.32. Import the files in Experion PKS R311.23. After successful completion of Import, commission the device.

I/O-Series C


1-3GAHYYS I/O-Series C

Error Indication: Outputs that were POWERED when field power waslost will return POWERED momentarily before initializing when poweris again restored.

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

Recovery: None.

Workaround: For any output that was POWERED when field powerwas lost ensure that the output cannot return immediately to thePOWERED state when the field power is restored. For more detail onhow this can be accomplished see PN2014-30.

1-3I90BL7 I/O-Series C

Error Indication: HART communication errors continuouslyaccumulate.

Description: AI-HART Analog Input module cannot communicateproperly with a WIKA T32 transmitter.

Recovery: None.

Workaround: None.

9 KNOWN ISSUES

111


1-5S2EVPM I/O-Series C

Error Indication: SC AIH IOM state changes from RUN->IDLE on itsown.

Description: The primary module for Series C AI, AO, DI and DOmodules may go to IDLE mode then revert back to RUN mode by itself.This will happen in a short frame of time (roughly 6 seconds). Duringthis time, the primary module will still continue acting as primary (thereis no switchover). No disruption to the process has been observed upuntil this point since the interval for mode change is quite short.

Recovery: IOM recovers on its own. IOM come back to RUN again.

Workaround: None

1-8JO2ZV7 I/O-Series C

Error Indication: Commanded switch over of the redundant PI IOMcauses the PI totalizer PV jumps to very large value.

Description: On commanded switchover of PI IOMs, PITOTALIZERblock reads the AVRAW count (from the new primary) less than the lastAVRAW count (read from the old primary) and when it computes thePV value it becomes negative value (current AVRAW – previousAVRAW) and storing in an unsigned 32 bit results a large value. Thiswill happen if the primary and secondary PI IOM have differentAVRAW counts.

Recovery: Disable the sync between primary and secondary PI IOM byissuing Disable_Sync Command (from PI IOM Main Tab). Once thesync is disabled, enable the sync by issuing Enable_Sync command.

Workaround: None

CDA-Server


1-6E4T61N CDA-Server

Error Indication: FDM rebuild network fails with Error code 7012.

Description: When FDM rebuild network is initiated, occasionally(after multiple rebuilds, save history, parallel device updates) it failswith error code 7012. This error code is usually returned when CDAServer becomes unresponsive. If CDA Server process is examined atthis time, process memory usage may be very high and after some point,CDA Server might crash. The reason for this is explained below. If thereis any unresponsive/slow responding nodes in the network and if thereare subscriptions for parameters of this node, then there is a possibilitythe CDA Server will start reporting Scatter timeouts. After some time, itmay so happen that CDA Server becomes unresponsive by the waythreads have been designed in CDA Server which is a known constraintas on today and hence the behavior reported in this PAR. Theprobability of occurrence of this issue has been found to be low.

Recovery: Experion PKS Server Switch over.

Workaround: None

1-86UKYOT CDA-Server

Error Indication: Control Data Access Server crash observed in R505Experion Server.

Description: One time occurrence of CDA server crash during runtime.

Recovery: Restart CDA Service.

Workaround: None

9 KNOWN ISSUES


CEE-Database


1-SMAA33 CEE-Database

Error Indication: CHECKBOOL.IN[1] parameter does not take inputwhen written through OPC gateway.

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

Recovery: None.

Workaround: None.

1-VPKU61 CEE-Database

Error Indication: DP_NUMBER parameter is not visible onmonitoring side of ISO_5167_DUAL block.

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

Recovery: None.

Workaround: None.

Checkpoint


1-8HK13FX Checkpoint

Error Indication: Checkpoint tab for the controller on the stationdisplay file shows that the Checkpoint save has failed.

Description: Sometimes the checkpoint save fails for auto scheduledtask.

Recovery: Usually, the next time the task is run, the auto save issuccessful.

Workaround: Perform a manual save of the checkpoint for the givencontroller.

Enterprise Model Builder


1-J3B3SH Enterprise ModelBuilder

Error Indication: In a dual primary scenario while migrating fromR430.1 to R500.1 release, the Assets or Alarm Groups configurationbuilder launched from Server A indicated that the connection is made tothe primary server. The OPM status is indicated in the status bar.However instead of indicating secondary server the status bar showsthat the connection has been 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 rightbottom corner must indicate OPM and Secondary Server connectionstatus. In this scenario you see a primary server connection indicated onthe status bar. In this scenario, the configuration change is not allowedat this time as the OPM status is enabled. This is a cosmetic anomalyand you can ignore the indication on the status bar.

Recovery: None

Workaround: None

9 KNOWN ISSUES

113

CAB Runtime


1-7JQ9JQ5 CAB Runtime

Error Indication: After migrating servers to latest release and if ACEis in prior release then dynamic reference will not work.

Description: Experion infrastructure does not support CAB DynamicRe-Referencing interoperation between the source releases and targetrelease during and after migration.(R3xx,R40x,R41x to any futurereleases). Refer to PN # PN 2007-25 for more details.

Recovery: None

Workaround: Migrate the ACE node to the latest release whichmatches to server.

Control Builder - Automated Device Commissioning


1-6CQRXN9Control Builder -Automated DeviceCommissioning

Error Indication: Open PET tool and perform bulk reassignment inADC flow.

Description: When bulk reassignment is done through PET ADC tool,occasionally an extra channel has been seen in the project tree.

Recovery: Unselect the extra channel from ADC UI and continue withthe operations.

Workaround: None

Control Builder - Connections


1-7J62ED1 Control Builder -Connections Deleting entire monitoring side and reloading everything.

EIP Tools


1-6WOK7XT EIP Tools

Error Indication: EIM is communicating with EIP devices without thelicense.

Description: In a specific scenario where the EIM EIP license is notenabled, the EIM is allowing the EIP communication with EIP devices.In this scenario the Protocol Block load has failed but the EIM blockstill gets loaded. EIM is allowing the EIP communication to go throughin this scenario.

Recovery: None

Workaround: None

1-6WUEV3D EIP Tools

Error Indication: User is able to use C300 in EIP direct mode withoutenabling the license.

Description: In a specific scenario the user is able to load the C300with EIP Direct mode without enabling the required license. The systemis not validating the license check for the loaded C300 in this scenario.

Recovery: None

Workaround: None

9 KNOWN ISSUES



1-86ZG2F0 EIP Tools

Error Indication: If the IOREF block is assigned to an IOPOINT blockand the reference type is IOPoint_Param, then the bad PV status is notshown in the IOREF block.

Description: In the IOREF block the bad PV status is not shown if theparameter is read through the IOPoint_Param reference type. This issueis observed where the parameter is read from the Generic Deviceinstance.

Recovery: None

Workaround: None

1-8I8YTYU EIP Tools

Error Indication: During the import of any EDS file, errors may getreported for the enumeration definitions that contain negative ordinals.In some scenarios the import may succeed. In such cases, the otherengineering operations like configuration of instance or load of instancemight fail.

Description: The negative ordinals in an enumeration set are nothandled properly in Control Builder. The user may see someinconsistent behavior while working with such enumeration parameters.

Recovery: None

Workaround: If possible update the enumeration definition and specifyordinals that are greater than 0.

IEC870 Interface

PAR Function Description1-85YZ8I2 IEC870 Interface Download the IEC channel/controller and points from QB.

1-85YZ8IC IEC870 Interface

Error Indication: When running the IEC870 database sync utility thesync would seem to complete, with a green synchronized LED, then goto "not synch'd".

Description: If user logs in as domain user then IEC870 Sync utilityfails to sync.

Recovery: Create a bat file which contains "runas /savecred /user:ExperionAdmin "Path to tool exe".

Workaround: Log in as a local administrator.

IXP - Import Export


1-28C3M4F IXP - Import Export

Error Indication: After DD import (FF\wireless) QVCS checked instrategies are Editable.

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

Recovery: Close and reopen Control Builder, which will make thestrategies non editable.

Workaround: Close and reopen Control Builder, which will make thestrategies non editable.

9 KNOWN ISSUES

115

ModBus TCP Blocks


1-3KTUVO9 ModBus TCP Blocks

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"then no recovery is necessary.

Workaround: None

1-7WRV2U7 ModBus TCP Blocks

Error Indication: When primary cable is removed from device it takesaround 3 minutes for secondary to take over.

Description: On a redundant device when primary cable is removed ittakes time for PCDI block to switch to secondary connection. Duringthis time data at channel block is retains its old value.

Recovery: None

Workaround: None

1-86K3OF0 ModBus TCP Blocks

Error Indication: During stable run PCDI Master block reportsConnection Fail or Single Device Fail alarm intermittently.

Description: The failure alarm RTN automatically within a second ortwo. No Input NaN or Output drop occur during this time. This issue isexperienced only with simulator so far and not with real devices.

Recovery: None

Workaround: None

PGM


1-G04A9M PGM

Error Indication: BADPV Alarms are reported against CM's usingSiemens ET200 IO Module (AI 331-1KF01-0AB0) after PGMSwitchover.

Description: Intermittent BADPV Alarms are logged against ControlModules using Siemens ET200 331-1KF01-0AB0 AI module after aPGM Switchover. No loss of Communication to the device itself occursor no such event is logged. Problem recovers within a few seconds.However if Control is configured to Shed on a Single BADPV, it willshed.

Recovery: Recovers automatically within few seconds.

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

PM I/O

PAR Function Description1-6BKDENJ PM I/O None

9 KNOWN ISSUES


I/O-Series C


1-69Q1RVN I/O-Series C

Error Indication: DO Channel PWM period parameter can be changedeven REDTAG is enabled on the channel.

Description: When REDTAG is enabled on the DO channel and if theuser updates the period parameter and load, IOM is accepting thechange instead of throwing error. Because of this output is affected.

Recovery: User should update the PWM period parameter back toprevious value.

Workaround: When REDTAG is enabled on the DO channel, usershould not update the period parameter.

1-8K31GH1 I/O-Series CDownload configuration but not active channel automatically (select In-active under POST-Download) if no sensor connected. When sensorconnected later, then active it.

ControlEdge PLC and RTU


1-8KLFJ1H ControlEdge PLC andRTU

Error Indication: ControlEdge PLC and RTU diagnostic alarms suchas 'Minimum CPU free threshold" are observed in System Summarysome minutes after the channel and controller are downloaded when nocommunications has occurred to the controller.

Description: ControlEdge PLC and RTU diagnostic alarms such as"Minimum CPU free threshold" are observed in System Summary someminutes after the channel and controller are downloaded when nocommunications has occurred to the controller.

Recovery: None

Workaround: These alarms will clear once communications isestablished to the PLC or RTU controller and a normal CPU free is readfrom the device. For virtual or test environments where it is not possibleto connect to a controller the alarms may be ignored, shelved, or can becleared by putting the SCADA channel into 'simulation mode' and thenconfiguring a display to enable write to point $COUTROLLERnnnn(where nnnn is zero padded RTU number such as for controller 23,$CONTROLLEROO23) and parameter Cpu_Free. After putting thechannel in simulation modes, use the display to write a value that isgreater than 5 and less than 100 will dear the alarm. When system goeson process the simulation mode on the channel should be disabled andnormal processing of value from controller shall resume.

9 KNOWN ISSUES

117

ELCN


RELCN-1168 ELCN

Description: In the case of a TPN personality failure of an ELCNAppliance Node or if the ELCN Appliance node goes to ISOLATEDstate, only the Native Window displays the correct state of FAIL orISOL respectively. However, the same states are not reflected on thefollowing displays:

• Control Builder Monitoring side - Main tab "Node State"• Experion Faceplate Display• UEA Front Panel Display

Recovery: None

Workaround: Reboot the UEA at the physical box.

RELCN-1001 ELCN

Description: Due to some specific FTE issues in the network, theELCN Bridge/ELCN Appliance Node reports a "FTE InterLAN CommFailed" alarm on the Experion Alarm Summary display and Faceplatedisplay, as expected. However, the Experion Alarm Summary displaykeeps rebroadcasting this alarm till the issue is resolved.

Recovery: To resolve this issue, troubleshoot the FTE issues in thenetwork that are causing this alarm.

Workaround: Same as the recovery.

RELCNTN-421 ELCN

Description: ELCN nodes shows CLK_MOD as LOCAL when LCNnode is the Clock Master.

Workaround: None. Note that until the Clock Master node is migratedfrom LCN to ELCN, any node that has completed migration from LCNto ELCN will show Clock Mode (CLK_MOD) as Local.

RELCNTN-164 ELCN

Description: Node does not autoload after dump when LCNPautorestart is enabled.

Workaround: Before taking a dump of a failed node, ensure that theEnable LCNP Auto Restart option is unchecked. After the dump iscompleted, the node does not autoload and you must perform the loadmanually by restarting the TDC Emulator service.

RELCNTN-404 andRELCNTN-408 ELCN

Description: CLKSWTCH fails to switch clock source nodes when youtry to switch from ELCN nodes to LCN nodes.

Workaround: None. When ELCN ESV-Ts are the Clock Source nodes(Clock Master and Clock Backup), you cannot switch the Clock Sourceto LCN node from the CLKSWTCH schematic.

RELCNTN-135 ELCN

Description: If ELCN Bridge (Primary and Secondary) is down formore than 2 minutes, all ELCN nodes will go to ISOLATED state. Anyattempt to load an Isolated node will cause it to crash.

Workaround: To load an Isolated ELCN node, first shut down the node(using System Status display in Native Window) and then load the node.

9 KNOWN ISSUES



RELCN-408 ELCN

Description: Whenever an ELCN Bridge or ELCN Applianceredundant node is swapped over, an alarm “Server: ConnectionTimeout” is reported by the primary ELCN Bridge and returns tonormal (RTN) in a few seconds (less than 5 seconds).

During a switchover, the alarm “Server: Connection Timeout” isexpected from the NEW secondary ELCN Bridge as it reboots when afailover is initiated. But the same alarm “Server: Connection Timeout”from the NEW primary (even if it RTNs within 5 seconds) may causesome confusion. This is the expected behavior and you can safely ignorethis alarm.

Workaround: None

RELCNTN-449 ELCNDescription: For an ELCN T-node or ELCN-HM, when the nodereboots, the TDC Emulator Service takes around 5 minutes to start.

Workaround: None

RELCNTN-429 ELCN

Description: For ELCN Experion TPS nodes, the LCNP Status Displayshows Substate as “DUPLICATE” when a duplicate device index isdetected in the network.

Workaround: Make sure that you do not have a node with a duplicatedevice index.

RELCNTN-350 ELCN

Description: In the case of a Virtual ES-T Node deployed using atemplate, you cannot dismount an emulated drive using the Mount/Dismount Emulated Disks Utility.

Workaround: None

RELCNTN-358 ELCN

Description: Occasionally, for an ELCN-HM or ELCN Experion TPSnodes, the LCNP Status Display shows Substate as “LCNEMFAIL”when you perform a LCNP reset using the Reset LCNP option, the resetoperation fails.

Workaround: Restart the TDC Emulator Service or the system.

RELCN-1243 ELCN

Description: For ELCN Appliance nodes and ELCN Bridges, youcannot acknowledge a system alarm for the respective node using theAcknowledge Alarm button on the Experion Faceplate Display.

Workaround: You can acknowledge the alarm using one of thefollowing options:

• Right-click on the alarm on the Experion Faceplate Display andclick Acknowledge Alarm.

• Go to the Experion Alarm Summary Display, right-click on thealarm and click Acknowledge Alarm.

RELCN-1277 ELCN

Description: For a Primary ELCN-ENIM node, the LCN CPUFREEvalue may drop by up to 4-5% and the CRUFREE value for the UEAbox may drop by up to 16-17%.

Workaround: None

RELCN-1196 ELCNDescription: An ELCN-AM may report a system alarm “NotSynchronized” and it may disappear after some time.

Workaround: None. You can safely ignore this alarm.

RELCNTN-548 ELCN

Description: TPN Server of ELCN ESVTs and ES-Ts crash when theEnable Auto Restart of LCN Connectivity option is checked.Therefore, for an ELCN ESVT/ES-T Node, it is recommended that youalways uncheck the Enable Auto Restart of LCN Connectivity optionon the Maintenance tab of the TPN Server Configuration Page.

9 KNOWN ISSUES

119

9.5 PDF Documentation

PDF Collection


1-8Q4II19 PDF Collection

Description: There is no reference from the Server migrationdocuments (EMUGs) to the ELCN Overview and Implementation Guidefor information on migrating your system from Classic T-Nodes usingLCNP4 cards or ETN nodes to ELCN based T-Nodes.

Workaround: None.

Knowledge Builder


1-3NDHL6P Knowledge Builder

Error Indication: The I/O module is in the No Response state.

Description: For the Digital Input module CC-PDIL51 on a systemprior to R410.1, CTools does not recognize the IOM. But it will stillallow a firmware download with the incorrect firmware to occur. Thisaction renders the I/O module unusable.

Recovery: The I/O module must be sent back to Honeywell forrecovery.

Workaround: None.

1-LU37LJ Knowledge Builder

Activities are created using duplicate IDs.

Error Indication: You may observe that some activities you thoughtyou created do not show up in the activity summary display. The sameactivity detail display may update from multiple activities which maycause incorrect 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 thecontroller.

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 therunning state.

9 KNOWN ISSUES


10 Honeywell software components and versions

This chapter lists the versions of Honeywell software components.

Related topics“Common component versions” on page 122“Controllers and tools version” on page 130“Server and client versions” on page 132“TPS Software Component Versions” on page 133“Compatibility with TPN releases” on page 134

121

10.1 Common component versions

Component Version Version verification(Only one option is listed)

App_TPS_Base 050.101.03900 Perform the following steps to verify the version.

1. Launch the Maintenance Tool.

The Maintenance Tool window appears.2. In the Maintenance Tool window, click View

Experion Feature Packages/Uninstall ExperionProduct.

AppTPSCL 050.101.03900 Perform the following steps to verify the version.




AppTPSClient 050.101.03900 Perform the following steps to verify the version.




App_TPS_Solution 050.101.03900 Perform the following steps to verify the version.




Experion CAB 050.101.03900 Perform the following steps to verify the version.




Honeywell_CAB_Support 050.101.03900 Perform the following steps to verify the version.




Honeywell Computers and NetworkEquipment Provider

050.101.03900 Perform the following steps to verify the version.




10 HONEYWELL SOFTWARE COMPONENTS AND VERSIONS



Honeywell CANE Detail Displays 050.101.03900 Perform the following steps to verify the version.




Experion_Station_Console_TPS 050.101.03900 Perform the following steps to verify the version.




Honeywell Security Model - DomainController





HSE_Creator_Tool 050.101.03800 Perform the following steps to verify the version.




Honeywell FTE MUX Driver 050.101.03900 Perform the following steps to verify the version.




Honeywell_FTE_Driver 050.101.03900 Perform the following steps to verify the version.




Honeywell_GUSDISP_Support 050.101.03900 Perform the following steps to verify the version.





123


Experion_GUS_Display_Builder 050.101.03900 Perform the following steps to verify the version.




Experion_GUS_Display_Runtime 050.101.03900 Perform the following steps to verify the version.




Experion_GUS_Multiple_Displays 050.101.03900 Perform the following steps to verify the version.




Experion_GUS_Remote_Displays 050.101.03900 Perform the following steps to verify the version.




Honeywell_HCI_Runtime 050.101.03900 Perform the following steps to verify the version.




Honeywell_IKB_Service 050.101.03900 Perform the following steps to verify the version.




Honeywell_INF_Support 050.101.03900 Perform the following steps to verify the version.







lcnp4drv 050.101.00700 Perform the following steps to verify the version.




Honeywell_Redirection_Manager 050.101.03900 Perform the following steps to verify the version.




Experion_Remote_Native_Window 050.101.03900 Perform the following steps to verify the version.




Honeywell_Safeview 050.101.03900 Perform the following steps to verify the version.




Experion_Server_TPS 050.101.03900 Perform the following steps to verify the version.




Honeywell Signon Manager 050.101.03900 Perform the following steps to verify the version.




Honeywell Signon ManagerACR120USB plugin





Honeywell FTE Switch ConfigurationTool

050.101.03900 Launch the Launch switchtool.exe.

Help > About


125


Honeywell System ManagementRuntime





TPN_Backup_Restore 050.101.03900 Perform the following steps to verify the version.




Honeywell_TPNFT_Support 050.101.03900 Perform the following steps to verify the version.




Experion_TPS_System_Displays 050.101.03900 Perform the following steps to verify the version.




Honeywell TPS Domain ConsoleConfiguration





Honeywell File Transfer - Server andClient





Honeywell File Transfer - Client 050.101.03900 Perform the following steps to verify the version.







Honeywell_TPSINT_Support 050.101.03900 Perform the following steps to verify the version.




Honeywell USB Storage Disable 050.101.03900 Perform the following steps to verify the version.




Honeywell PC Universal Station 050.101.03900 Perform the following steps to verify the version.




Honeywell Security Model -Workstation





Honeywell FTE MUX Win10 Driver 050.101.03900 Perform the following steps to verify the version.




Honeywell Multifactor Authentication 050.101.03900 Perform the following steps to verify the version.




Honeywell MultifactorAuthentication32






127


Honeywell Multifactor Domain PolicyTemplates





Honeywell Signon Manager DatabaseServer





Honeywell Signon ManagerFingerprint Enrollment





Honeywell Signon ManagerFingerprint Plugin





Honeywell Signon Manager HandlerLumidigm





Honeywell HSR MUX Driver 050.101.03900 Perform the following steps to verify the version.




Honeywell PRP MUX Driver 050.101.03900 Perform the following steps to verify the version.







ELCN_node 050.101.03900 Perform the following steps to verify the version.




HM_base 050.101.03900 Perform the following steps to verify the version.





129

10.2 Controllers and tools version


Control Builder R501.1 1. Launch the Configuration Studio.2. Choose Configuration Studio > Control Strategy >

Configure Process Control Strategies.3. Choose Help > About…

DBADMIN 501.1.39.0 1. Open Windows Explorer and browse to C:\ProgramFiles(X86)\Honeywell Experion PKS\Engineering Tools\system\bin\pserdbadmin.dll

2. Click Properties > Details .tab

Import/ Export Tool EXP501.1-39.0 1. Launch the Import-Export Tool.2. Choose Help>About…

IOTOOL EXP501.1-39.0 1. Launch the Configuration Studio.2. Choose Control Strategy > Maintain IO Modules.3. Choose Help > About…

Network Tools EXP501.1-39.0 1. Launch the Configuration Studio.2. Choose Control Strategy > Maintain Control System

Firmware.3. Click Help > About...

Engineering ToolsDatabase

EXP501.1-39.0 1. Launch the Import-Export Tool.2. Choose Help > About... ERDB version is displayed after

Import-Export tool version.

Application ControlEnvironment (ACE)

501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell Experion PKS\Engineering Tools\system\bin\ace.exe.

2. Right-click Properties > Details tab.

Simulation ControlEnvironment (SIM-C200E)

501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell Experion PKS\Engineering. Tools\system\bin\sce.exe.


Simulation ControlEnvironment (SIM-C300)

501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell Experion PKS\Engineering Tools\system\bin\simc300.exe.


IOLIM Simulation(SIM-IOLIM)

501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell Experion PKS\Engineering. Tools\system\bin\simiolim.exe.


Upgrade Tool 501.1.39.0 Open Configuration Studio.

1. Choose Configuration Studio > Experion PKS ClusterUpgrade> Prepare the Cluster for an Upgrade.

This opens the Upgrade Tool.2. In Upgrade Tool, choose Help > About…




FTE Driver 501.1.39.0 1. Launch the Maintenance Tool.

The Maintenance Tool window appears.2. Select View Experion Feature Packages/Uninstall

Honeywell Product Honeywell FTE MUX Driver.


131

10.3 Server and client versions


Experion Server 501.1.44.0 You can verify version in the following path after installation.

1. Launch the Start-Stop Experion PKS Server.2. In the Experion PKS Server dialog box, choose File > About

Experion ConsoleStation

501.1.44.0 You can verify version in the following path after installation.

1. Launch the Start-Stop Experion PKS Console Station.2. In the Experion PKS Server dialog box, choose File > About.

HMIWeb Station 6.8.300.242 1. Choose Honeywell Experion PKS > Server > Station.2. Choose Help > About...

.

HMIWeb DisplayBuilder

R320.4 1. Choose Honeywell Experion PKS > Server > HMIWebDisplay Builder.

2. Choose Help > About...

.

Quick Builder 5.1.301.37 1. Launch Configuration Studio.2. Under Provider, look for

Honeywell.QB.QBProvider.Provider.

Configuration Studio 4.2.2.110 1. Launch Configuration Studio.2. Under Application, look for Honeywell.CDF.ConfigStudio.



10.4 TPS Software Component Versions


GUS Display Builder 501.1.39.0.0 1. Choose Honeywell Experion PKS > TPS Applications >GUS Display Builder.

2. Choose Help > About Honeywell GPB.

Native Window 501.1.39.0.0 1. Choose Honeywell Experion PKS > TPS Applications >Native Window.

2. Click Help > About Native Window.

TPN Backup Restore 501.1.1.0.0 1. Choose Honeywell Experion PKS > TPS Applications >TPN Backup-Restore.

2. Choose Help > About....

Component LibraryEditor

501.1.39.0.0 1. Choose Honeywell Experion PKS > TPS Applications >GUS Display Builder Tools > Component Library Editor.

2. Choose Help > About Library Editor.

HOPC Server 501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell\TPS\GUS\ hopcsrvr.exe.

2. Right-click Properties > Details tab and verify File Version.

NWDDB Server 501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell\TPS\GUS\ nwddb_server.exe.


LCNP Status Applet 501.1.39.0 1. Open Windows Explore and browse to C:\Program Files\Honeywell\TPS\Emulators\ emstatus.exe.


File Transfer 501.1.1.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell\TPS\TPSxfer\ FTService.exe.


CL Server 501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell\TPS\CLAPPServer\clsrvrdss.exe.


TPN Server 501.1.39.0 1. Open Windows Explorer and browse to C:\Program Files\Honeywell\TPS\TPNServer\ tpndss.exe.



133

10.5 Compatibility with TPN releasesThe following table presents the compatibility between the Experion (ESVT, ES-T, ACE-T) and TPN releases.

Experion release Minimum TPN system software

R201, R21x , R301.x TPN R641.2

R31x.x , R400.x, R410.x,

R430.x, R431.x, R432.x, R500.x, R501.x

TPN R535.2 or later R5xx releases in this series.

TPN R652.1 or later R6xx releases in this series.

Note• For customers with no existing US or GUS nodes: GUS-TPN Software CD R652.1 (or later) is required.• For customers with no existing Experion APP or AM nodes: TPN Application Module Software CD R652.1 (or

later) is required.

To use some Experion features, newer versions of TPN are required for proper integration with Experion. Theyare enumerated as follows:

TPN softwarerelease version

Required for this functionality Notes

TPN R687.1 • Experion Local Control Network (ELCN• Triconex Communication Module Interface (TCMI)

For TCMI capability, ULM R301.18 is alsorequired.

TPN R686.2 • Experion Console Enable/Disable Functionality• Stop ACK events for shelved TPS alarms• Enhanced Network Bridge (ENB)

ULM R301.15 is also required.

For Experion Direct Connection capability(optional license), a minimum of ExperionR432.1 is required.

TPN R685.3 • EUCN Part 2b (i.e. automatic NIM point import toExperion database).

• Experion Hiway Bridge (EHB)


EHB is supported for On-ProcessMigrations starting Experion R431.

TPN R685.1 EUCN Part 2 (that is, peer-to-peer from C300Controllers to EHPM Controllers).

ULM R301.12 is required.

TPN R685.3 EUCN Part 2b (i.e. automatic NIM point import toExperion database)


TPN R685.1 The ability to load Sequence Programs from theExperion Detail Display.

Functionality gives a warning message ifattempted to be used from an earlier TPNversion.

TPN R683.2 (orlater)

Fully functioning integration for HMI Web TPS DetailDisplays.

Experion R410.x (or later) is also required.


EUCN Part 1 (ENIM/EHPM) functionality. Need ULM R301.11 (or later).

TPN R681.x (orlater)

Proper integration of Selective Contact Cutoutfunctionality.

In addition, Experion R311.x (or later) isrequired.


Not displaying disabled alarms on Flex Stations. In addition, Experion R310.x (or later) isrequired.


To allow the “Option to display Uncertain Quality forTPS points” functionality.

Option found in TPN Server componentconfiguration.

The Utilities & Load Module Media (ULM) contains (among other things) the EST and ESVT load modules,which are necessary for proper Experion integration. It is crucial to have the version of the ULM that matcheswith your version of Experion software to ensure proper integration. Following are specific features and theirversions:



Utilities & Load Module Media (ULM) requirements• The Utilities and Load Module Media (ULM) version for Experion R410.x is R301.9.• The Utilities and Load Module Media (ULM) version for Experion R430.x/Experion R431.x is R301.12.• The Utilities and Load Module Media (ULM) version for Experion R432.x/Experion R500.x would be

R301.15.• The Utilities and Load Module Media (ULM) version for Experion R501.x would be R301.18.

EST Load Module version Required for this functionality Notes

EST.LO load module version68.9 (or later)

Required for Experion Console Enable/DisableFunctionality.

Functionality introduced in ExperionR500 and later.


Required for the TPS System Status Indicator(S) and TPS Console status indicator (C) on theExperion Station status bar.

Currently not supported in TPNR53x.x.


Required for “Message clear required”functionality.

Additionally, supported on TPNR53x.x with EST.LO load moduleversion 53.2 (or later).


135



11 Honeywell-qualified third-party software componentversion

Related topics“Honeywell-qualified third-party embedded software component versions” on page 138“Honeywell-qualified third-party software component versions” on page 140

137

11.1 Honeywell-qualified third-party embedded software componentversions

Component Version Verification mechanism(Only one option is listed)

Adobe AcrobatReader

11.0.07 1. Open Adobe Reader.2. Choose Help > About Adobe Reader

Dell Open ManageServer Administrator

8.4 1. Click Start > Windows System > Control Panel > Programs> Programs and Features.

2. Check Dell OpenManage System Management Software(64–Bit).version in the Version column of the page.

Dell Open ManageClientInstrumentation

9.1.0.98 1. Click Start > Windows System > Control Panel > Programs> Programs and Features.

2. Check Dell OpenManage System Management Software(64–Bit).version in the Version column of the page.

HP SystemManagementHomepage

7.6.0.11 1. Click Start > Windows System > Control Panel > Programs> Programs and Features.

2. Check HP System Management Homepage.version in theVersion column of the page.

Internet Explorer 11.0 1. Open Internet Explorer directly.2. Choose Help > About Internet Explorer.

Microsoft .NETFramework

4.6.2 Ensure the following directory is available:

C:\WINDOWS\Microsoft.NET\ Framework\v1.1.4322.

MS Visual BasicRun-Time DLLs(Used with ModelNo. MZ-NTDE04ApplicationDevelopmentToolkit.)

6.0.98.15 1. Open Windows Explorer and browse to C:\windows\syswow64\msvbvm60.dll.

2. Right-click msvbvm60.dll.3. Right-click Properties. Click Versions tab.

MS Visual C++ Run-Time DLLs

7.0.14393.0 1. Open Windows Explorer and browse to C:\windows\syswow64\MSVCRT.dll (Microsoft Run Time Library).

2. Right-click MSVCRT.dll.3. Right-click Properties. > Click Versions tab

Crystal Reports 8.5 8.5.0.461 1. Open Windows Explorer and browse to C:\windows\syswow64\crpe32.dll.

2. Right-click Properties. Click Details tab.

SQL Server 2012Standard SP3

12.0.5000.0 1. Open SQL Server Management Studio.2. Type select @@version and press F5 key.

Objective Grid 13.0.0.0 1. Open Windows Explorer and browse to C:\ProgramFiles(x86)\Honeywell\ExperionPKS\Engineering Tools\System\Bin\og1300asu.dll.

2. Right-click og1300asu.dll.3. Click Properties > Details tab.

Embedded MicrosoftWindows 10Enterprise 2016LTSB (x64)

1607 (OS build 14393.187) 1. Right-click Start > Run.2. On Command prompt, type Winver and press ENTER.

11 HONEYWELL-QUALIFIED THIRD-PARTY SOFTWARE COMPONENT VERSION


Component Version Verification mechanism(Only one option is listed)

Embedded MicrosoftWindows Server2016 Standard

1607 (OS build 14393.187) 1. Right-click Start > Run.2. On Command prompt, type Winver and press ENTER.


139

11.2 Honeywell-qualified third-party software component versionsThis section identifies third-party, Windows-based software applications that are supported on an Experionclient system.

AttentionHoneywell is not responsible for issues resulting from the installation or use of any software that have not been testedfor Experion compatibility by Honeywell. In case, you must use any of the third-party software, ensure sufficientsystem resources such as memory, CPU performance, disk space, display space, and so on are available.

Software application and version Verification Mechanism(Only one option is listed)

National Instruments NI-FBUSCommunications Manager

1. Choose Start > Programs > NI FBUS > Interface Config.2. Click the System menu and select About fbConfig_NT.

Limitations/Compatibility

Model Number TC-NIFB01 must be used with Model Number 1757-CN2FFFieldbus Linking device. Only this model number must be purchased and notthe general release of the Configurator from NI.

Microsoft Office Qualified Microsoft Office products include the following:

• Microsoft Excel• Microsoft Word• Microsoft PowerPoint• Microsoft Access

Note: Any other MS components not mentioned in the list (Outlook,Communicator, and so on.) are not supported.

For latest information about the qualified Microsoft Office packages for theExperion products, refer to the following link.

McAfee NT Scan Qualified McAfee Antivirus package is available on the Honeywell ProcessSolutions website.

Symantec Qualified Symantec package is available on the Honeywell Process Solutionswebsite.

Honeywell TotalPlant Batch Contact Honeywell TAC for more information.

Procedure Analyst Contact Honeywell TAC for more information.



https://www.honeywellprocess.com/library/support/Documents/Trusted/Experion/certified-microsoft-officepackages. pdf

12 Support for optional SCADA interfaces

Interface support levelHoneywell provides varying levels of support for each SCADA interface dependent on availability of hardwareand the level of support third-party vendors support their software. The following table provides the levels ofsupport.

SCADA InterfaceSupport Level

Description

Supported SCADA interfaces that are fully supported by Honeywell and third party vendors.

If interface relies on third party drivers then these are officially supported and qualified on theplatforms required by Experion.

Validated SCADA interfaces that have been validated by Honeywell on Experion R50x. However, theseSCADA interfaces rely on third-party vendors who have either withdrawn the interface or do notofficially support the platforms required by Experion.

Honeywell support may be dependent on third-party vendors.

Not Validated SCADA interfaces that have not been fully validated by Honeywell on Experion R50x.

These SCADA interfaces either rely on third-party vendor software that were not supported on theplatforms required by Experion during development, or there is limited hardware availability or thehardware is obsolete.

Honeywell support may be dependent on third-party vendors.

The following tables describes the levels of support for each SCADA interface.

Honeywell devices


ConsiderationsR50x

Honeywell TDC 3000 Not Validated Not applicable

Honeywell S9000 Integration Not Validated Not applicable

Honeywell 620 LCS Serial and EthernetInterface

Not Validated Not applicable

Honeywell UDC 3000/5000/6300 Integration Not Validated Not applicable

Honeywell DPR Recorders Not Validated Not applicable

Honeywell RM7800 Flame Safeguard Not Validated Not applicable

141


ConsiderationsR50x

Honeywell Universal Modbus Interface Supported Allows communication withUMC800, HC900 and othercompatible devices and controllers.Please refer to the HoneywellUniversal Modbus InterfaceReference for more details.

Honeywell MasterLogic Not Validated Please contact TAC or your SalesAccount Manager if you require thisinterface.

Honeywell FSC and Safety Manager Supported Not applicable

RTU2020 Supported Enhanced integration introduced inR50x.

Industry standard interfaces

SCADA Interface Support Level ConsiderationsR50x

Modbus (RTU, Plus, ASCII & TCP) Interface Supported R50x: Validated with CyberlogicMBX driver suite 7.1 and ModbusPlus has not been validated for thisrelease.

DNP3 Protocol Interface Supported Not applicable

OPC Interface (OPC SCADA Client) Supported It is recommended thatMatrikonOPC servers are used forthird party integration.

IEC-61850 Protocol Interface Not Validated R50x: IEC-61850 Protocol Interfaceis currently not supported.

IEC-60870 Protocol Interface Not Validated R50x: IEC-61850 Protocol Interfaceis currently not supported.

Third-party devicesThe remaining interfaces support third-party controllers. Note that some of the interfaces requirecommunication software manufactured by the third-party.

For third-party devices not listed here, contact Honeywell TAC to discuss options including the use ofMatrikonOPC drivers.

Legacy Experion interfaces not listed here may still be supported for upgrades only. For more information, referto the latest Experion Software Change Notice.


ABB Totalflow Supported R50x: Supported

Validated with TCI Toolkit version3.07, an XRC6990 RTU, and alsowith the ABB Totalflow emulator.

Allen-Bradley Interface Not Validated Rockwell is still to release theofficially supported version ofRSLinx on Windows Server 2016and Windows 10. It will likely be

12 SUPPORT FOR OPTIONAL SCADA INTERFACES



RSLinx v3.9 or later. Honeywell willqualify as soon as it is available.

R50x: Expected to work but not yetvalidated on a BCC topology.

Allen-Bradley ControlLogix Interface Supported Matrikon OPC Server for Allen-Bradley PLC’s is recommended forcommunications with Allen-BradleyControlLogix PLC’s.

Applicom Not Validated Honeywell has not validated thisinterface with Experion R50x. TheApplicom Interface has beenwithdrawn from public general salein Experion. Consider using DSA toa previous Experion Server releaseto interface to Applicom devices.

Asea Interface Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

Very low risk as this is a serialinterface.

Honeywell plans to work withcustomers to validate. In the event ofany issues found during validation,Honeywell support may bedependent on third party vendors.

Bailey Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

The Bailey Interface has beenwithdrawn from public general salein Experion.

Note that the Bailey software(semAPI Release 1.2) does notsupport the Windows Server 2008R2 64-bit platform required byExperion Server.

Consider using Honeywell’smigration solution for Baileysystems: https://www.honeywellprocess.com/en-US/explore/products/control-monitoring-and-safety-systems/integrated-control-and-safety-systems/third-party-system-migration/Pages/migration-solution-for-bailey-systems.aspx

Or using a MatrikonOPC server tointerface to Bailey INFI90 orNetwork 90 systems.

Bristol Babcock OpenBSI Interface Not Validated R50x: Available for approvedcustomers only. Contact TAC if thisinterface is required.

Expected to work but not yetvalidated on a BCC topology.


143

http://solutionsbank.abb.com/SBankData/S/LOC/Advant/INFI90/ElectronicDocumentationCDVersi/MANUALS/776425Z148918/app/i_apint/docsumm.pdf

https://www.honeywellprocess.com/en-US/explore/products/control-monitoring-and-safety-systems/integrated-control-and-safety-systems/third-party-system-migration/Pages/migration-solution-for-bailey-systems.aspx









Reference: http://www.documentation.emersonprocess.com/groups/public/documents/instruction_manuals/d301414x012.pdf

Bristol Babcock RTU Serial Interface Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

Enron Modbus Supported R50x: Supported.

Validated with “NuFlo CameronScanner 2000” device.

Fisher ROC Not Validated Supports both Fisher ROC andFisher ROC Plus protocols.

R50x: Validated against FloBoss 107and ROC800L devices.


GE Fanuc Series 90 PLC via Ethernet Not Validated GE Fanuc Series 90 Interface hasbeen qualified with GE Fanuc HostCommunication Toolkit version 1.02distributed as part ofIC641SWP058B Toolkit forWindows NT C/C++ Applications.

GE 9030 and GE Rx7i have beenvalidated.

Note that the GE HostCommunications Toolkit has beendiscontinued by GE. Honeywell isnot in a position to provide supportfor the toolkit. However, Honeywellhas validated this interface to workwith Experion server.

Also refer to the Be-Aware for moredetails on supported models: https://www.honeywellprocess.com/library/support/notifications/Customer/BW2005-14RevA_Experion-PSc%20GE%20Fanuc.pdf

GE Series 6 Not Validated Honeywell has not validated thisinterface with Experion R50x. TheGE Series 6 Interface has beenwithdrawn from public general salein Experion.

Consider using DSA to a previousExperion Server release to interfaceto GE Series 6 devices.

GEC GEM80 PLC Interface Not Validated Honeywell has not fully validatedthis interface with Experion R50x.




http://www.documentation.emersonprocess.com/groups/public/documents/instruction_manuals/d301414x012.pdf





https://www.honeywellprocess.com/library/support/notifications/Customer/BW2005-14RevA_Experion-PSc%20GE%20Fanuc.pdf






Hitachi Interface Not Validated Honeywell has not fully validatedthis interface with Experion R50x.


Micromax LPU & Video Paperless Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

The L&N Micromax Interface hasbeen withdrawn from public generalsale in Experion.

Consider using DSA to a previousExperion Server release to interfaceto Micromax devices.

Moore 351, 352, 353, 383 Interface Not Validated Honeywell has not validated thisinterface with Experion R50x.

Very low risk as this is a serialinterface.


Moore APACS Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

As of the date of this publication, thelatest release of the Siemenssoftware is APACS Runtime APIv4.51 distributed as part ofSIMATIC PCS 7/APACS+ OSOption Software V8.0 SP1.


Consider using a MatrikonOPCserver to interface to Moore APACSDCS.

Reference: http://cache.automation.siemens.com/dnl/Dg/DgxMTIzNQAA_79061961_DL/PCS7_APACS_OS_V80_SP1_ReadMe.pdf

Omni Flow Computer Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

An Omni Enhanced interface wasadded for customers requiring EFMdata from Omni Flow Computers.This has been tested with emulators,


145

http://cache.automation.siemens.com/dnl/Dg/DgxMTIzNQAA_79061961_DL/PCS7_APACS_OS_V80_SP1_ReadMe.pdf







but has not been validated againstOmni hardware.

Consider using a MatrikonOPCserver to interface to Omni FlowComputers. This will not be usefulfor reading EFM data.

Honeywell plans to work withcustomers to validate. In the eventof any issues found duringvalidation, Honeywell support maybe dependent on third party vendors.

Siemens S5 Not Validated Honeywell has not validated thisinterface with Experion R50x.

As of the date of this publication, thelatest release of the Siemenssoftware is SIMATIC NET PCSoftware V8.2. This release of theSiemens software does not supportthe TF communications protocolanymore.

Consider using DSA to a previousExperion Server release to interfaceto Siemens S5 devices.

Reference: https://cache.automation.siemens.com/dnl/jU/jUyNzc0NQAA_61630923_HB/INH_SIM-NET_76.pdf

Siemens S7 Not Validated As of the date of this publication, thelatest release of the Siemenssoftware is distributed as part ofSIMATIC NET PC Software V13.

Honeywell plans to work withcustomers to validate this release. Inthe event of any issues found duringvalidation, Honeywell support maybe dependent on third party vendors.

Honeywell has validated theprevious software version S7-1613V8.1 distributed as part of SIMATICNET PC Software V8.2.

Reference: https://support.industry.siemens.com/cs/document/63098071/simatic-net-dvd-v8-2-released-for-delivery?dti=0&lc=en-WW

https://support.industry.siemens.com/cs/document/109346876/simatic-net-dvd-v13-released-for-delivery?dti=0&lc=en-WW

Spirit IT Flow-X Interface Not Validated R50x: Available in Experion R50x,Run-time data is polled through



https://cache.automation.siemens.com/dnl/jU/jUyNzc0NQAA_61630923_HB/INH_SIM-NET_76.pdf




https://support.industry.siemens.com/cs/document/63098071/simatic-net-dvd-v8-2-released-for-delivery?dti=0&lc=en-WW











Modbus interface, and EFM dataqueried through HTTP Web Service.


Texas Instruments Not Validated Honeywell has not fully validatedthis interface with Experion R50x.

The Texas Instruments Interface hasbeen withdrawn from public generalsale in Experion.

Consider using DSA to a previousExperion Server release to interfaceto Texas Instrument devices.

Yamatake MA500 Interface Not Validated Not applicable


147



13 Notices

TrademarksExperion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of HoneywellInternational, Inc.

OneWireless™ 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.

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

149

http://www.honeywell.com/ps/thirdpartylicenses

http://www.honeywellprocess.com/support

mailto:[email protected]

https://honeywell.com/Pages/vulnerabilityreporting.aspx

mailto:[email protected]

• Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell TechnicalAssistance 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 PKS. These classes are taught by experts in the fieldof process control systems. For more information about these classes, contact your Honeywell representative, orsee http://www.automationcollege.com.

13 NOTICES


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