c300pm overview and implementation guide

Experion PKS

Release 511

C300PM Overview and Implementation GuideEPDOC-X729-en-511A

September 2021

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

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

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

Copyright 2021 - Honeywell International Sàrl

- 2 -

Contents

Chapter 1 - About this guide 5

1.1 Scope 5

1.2 Revision history 5

1.3 Intended audience 5

1.4 Related documents 5

Chapter 2 - Introduction to C300PM 7

2.1 Functional overview 7

2.2 Hardware overview 7

2.2.1 C300PM functionality 7

2.2.2 C300PM card/module types 8

2.2.3 C300PM card file configurations 11

2.2.4 C300PM Front Panel LED display information 11

2.3 C300PM vs EHPM 13

2.4 C300PM Deployment Requirements 18

2.5 Example of UCN and EUCN topology diagram showing addition ofC300PM 21

Chapter 3 - C300PM Deployment Considerations 23

3.1 FTE Community and UCN Considerations 23

3.2 FTE Device Index and IP Addressing 23

3.3 Experion TPS Node Configuration Requirements for C300PM 24

3.3.1 Configuring Experion Base IP Address and (S)NTP IP Address 24

3.3.2 Time Synchronization Considerations 24

3.4 Supported System Topologies 24

3.5 Security Considerations for EUCN 26

3.6 LVRLOG report 26

3.7 Audit Tool report 26

Chapter 4 - Installation 27

Chapter 5 - Configuration 28

5.1 Updating initial firmware using Experion Firmware Manager 28

5.2 Configuring platform block using Control Builder 28

5.2.1 Overview 28

5.2.2 Creating and configuring a C300PM block 28

- 3 -

5.2.3 CDA data access effect on C300PM performance 31

5.2.4 Importing C300PM points into ERDB 31

5.2.5 Loading a C300PM block 43

5.2.6 Deleting/moving C300PM points having existing Experion Server Peer Responderconnections 46

5.2.7 Deleting/moving C300PM points having existing CDA peer-to-peer connections 47

5.2.8 Establishing peer-to-peer communication between ACE/C300 and C300PM 48

5.2.9 Control Builder operations on C300PM Controller 49

Chapter 6 - Operation 58

6.1 IDLE state after flashing firmware and rebuilding 58

6.2 To check C300PM operation from Experion Detail Displays 58

6.3 To check TPN and FTE Status Display 64

6.4 Interpreting C300PM icons in Control Builder 65

6.5 Redundancy operation 71

6.6 Viewing event/alarm displays and journals 72

6.7 Managing C300PM node using Experion Dashboards 72

6.7.1 Introducing Experion Dashboards 72

6.7.2 Dashboard Configuration Checklist 73

6.7.3 Configuring ES-T connection for dashboards 86

6.7.4 Configuring which display is called up by the TPS System and Console Statusindicators 86

6.7.5 Viewing C300PM node status in Experion using automatically created dashboards 87

6.7.6 Operations on C300PM node from Experion 87

6.7.7 Calling up Native Window displays from Experion 89

Chapter 7 - Service 90

7.1 Flash firmware on an operational C300PM 90

7.1.1 To Update Firmware on an on-process Operational Redundant C300PM node 90

7.1.2 To Update Firmware on a Non-Redundant C300PM Node 97

7.2 Troubleshooting tools 100

Chapter 8 - HPM/EHPM to C300PM on-process migration 104

- 4 -

ABOUT THIS GUIDE

1.1 Scope

This guide contains instructions and configuration requirements for implementing the Fault TolerantEthernet (FTE)-based C300 Process Manager (C300PM) node. This guide includes detailed instructionsfor software installation, configuration, operation, and troubleshooting, with references to other documentsas needed.

1.2 Revision history

Revision Date Description

A September2021 Initial release of the document.

1.3 Intended audience

This guide is primarily intended for engineers who integrate C300PM node into an Experion system andare responsible for planning, installing, and administering the standard TPS system. It is thereforeassumed that the user of this document possesses a high degree of technical knowledge and a familiaritywith the EUCN and Experion process control systems.

1.4 Related documents

The following list identifies publications that contain information relevant to the information in thisdocument.

Document Description

C300PM Overviewand ImplementationGuide

Provides detailed comprehensive software/system configuration information,including migration procedures for C300PM.

C300PM Planning,Installation, andService Guide

Provides information for planning, installing, and servicing the C300PM hardware.

Control BuilderComponentsTheory

Provides information about the usage of the function blocks in the Control Builder.

Control BuilderComponentsReference

Provides quick reference about the function blocks.

Control BuilderError CodesReference

Provides information related to the errors that appear in the Control Builder.

- 5 -

CHAPTER

1

Document Description

Control BuilderParameterReference

Provides information about the parameters.

Control BuildingUser's Guide

Describes the usage of the Control Builder for configuring and loading thestrategies.

Experion FirmwareManager ToolUser’s Guide

Describes the prerequisites, installation and use of the Firmware Manager Tool.This tool is used to load firmware to a Honeywell Universal Embedded Appliance(UEA), and to access diagnostic information from it.

Experion LCNEngineeringOperations Guide

Provides information about the instructions and configuration requirements for theExperion LCN (ELCN) engineering operations.

Engineer'sReference Manual

Provides information about configuration, startup, and reconfiguration efforts forTPN-based TPS systems.

TPS System AuditTool User's Guide Describes the installation, preparation, and running of the System Audit Tool.

- 6 -

Chapter 1 - About this guide

INTRODUCTION TO C300PM

2.1 Functional overview

Beginning with Experion R511.5 and TPN R690.1, an existing UCN-based High-Performance ProcessManager (HPM), or Fault Tolerant Ethernet (FTE)-based Enhanced High-Performance Process Manager(EHPM) node can be upgraded to an FTE-based C300 Process Manager (C300PM) node. This upgradecan be performed on-process.

The C300PM hardware consists of a Fault Tolerant Ethernet-based C300PM Communication/ControlCard, Power Backup Module, and FTE Interface module. The High-Performance I/O Link Module is notrequired in C300PM configuration as this functionality is integrated with the C300PMCommunication/Control Card. No changes are necessary to the physical I/O link cables.

C300PM is an ARM processor based common embedded hardware platform that executes HPM nodepersonality software. The personality software is built into the C300PM firmware and hence, there is noneed to load a C300PM with HPM personality software. The C300PM comes up in IDLE state uponbooting and you only need to restore the checkpoint. The C300PMs do not require separate CF9 switchesin the network as they have a built-in Control Firewall functionality and will connect directly to the L2switch.

The UCN status displays are updated for C300PM. Displays that are important for fault scenarios ormaintenance of the EUCN FTE network and their elements are modified to reflect the C300PM node.

2.2 Hardware overview

2.2.1 C300PM functionality

The C300PM Module provides:

l HPM Control functions

l Communications with the Local Control Network (LCN) Enhanced Network Interface Module (ENIM),ELCN ENIM variants of UEA/UVA ENIM, and Enhanced Network Bridge (ENB) through the EnhancedUniversal Control Network (EUCN)

l HPM Communication processor functions

l Communications through the I/O Link Interface with Input/Output Processors (IOPs) and I/O LinkExtenders

l A power backup module (PBM)

l Redundancy control for both HPM

l The C300PMs do not require separate CF9 switches in the network as they have a built-in ControlFirewall functionality and will connect directly to the L2 switch.

- 7 -

CHAPTER

2

2.2.2 C300PM card/module types

The C300PM board set consists of the C300PM PWA, Power Backup Module PWA and FTE InterfaceModule. The FTE interface module is mounted in the 50-pin connector below the C300PM PWA in the firstleft-most card file slot. The cards and the module are described in the following table.

C300PM Card/Module Types

Card/Module Type Function

CEP-based C300PMCommunication/ControlCard

Consists of:

l Dual core ARM processor

l IOLink communication processor

l FTE interface to the C300 PM FTE Interface module

l redundancy interface to another C300PM

l front panel LEDs and a four-character alphanumericdiagnostic display.

Power Backup Module Consists of:

l Super capacitor based power backup circuit

FTE Interface Module The FTE Interface module has 3 ethernet ports (1 yellow FTE, 1green FTE, and 1 orange redundancy port) with RJ45 connectorsand LEDs. The backplane interfaces between the C300PM andFTE Interface.

The FTE Device Index is physically set on this FTE Interface Cardusing the three rotary switches. Note, the FTE Interface used withEHPM and C300PM are the same.

CF9 Switches The C300PMs do not require separate CF9 switches in thenetwork as they have a built-in Control Firewall functionality andwill connect directly to the L2 switch.

C300PM Communication/Control Card

The following figure illustrates the front of the C300PM Communication/Control Card as well as theindicators and Diagnostic display.

The C300PM Communication/Control Card has an upgradable firmware. The firmware can be upgradedfrom the Experion system by using Firmware Manager. For more details, see section "Getting Started withFirmware Manager for C300 Process Manager (C300PM)" in the Firmware Manager User's Guide.

- 8 -

Chapter 2 - Introduction to C300PM


C300PM Communication/Control Card (Front Panel)

Power Backup Module

C300PM controller supports RAM Retention Restart feature. This feature allows retention of userconfiguration data in the event of loss of main 120V /230V A.C. power supply.

When main 120V /230V A.C. power supply is lost, C300PM controller receives power for approximately 5seconds from Power Backup Module. During this period, C300PM controller backs up user configurationdata in an on-board non-volatile memory.

For retaining the IOP configuration data, the C300PM and IO chassis should be backed up by the CMOSbattery backup circuitry. Ensure that you have a set of 3 CMOS Alkaline batteries in power supply forretaining the IOPs to their original state after power failure.

- 9 -

Power Backup Module (Front Panel)

FTE Interface module

The following figure illustrates the front panel of the FTE Interface module. Each FTE cable (yellow andgreen) is connected to a CF9 or L2 Ethernet Switch (yellow and green).

Redundant C300PMs connected to an Experion network have a crossover cable connecting theredundancy ports (bottom port) of the two FTE Interface modules.

FTE Interface Module (Front Panel)

- 10 -



Note that the existing EHPM FTE modules may be used in place of a new one.

2.2.3 C300PM card file configurations

There are 3 C300PM card file configurations. They are as follows:

l Left 7-Slot C300PM card file

l Right 7-Slot C300PM card file

l 15-Slot C300PM card file

15-Slot C300PM card file

The following figure is an illustration of a 15-Slot C300PM card file.

15-Slot C300PM card file

2.2.4 C300PM Front Panel LED display information

C300PM Front Panel display indications

C300PM Front Panel LEDdisplay

Indicates… Recovery action

AUTH ENIM failed to authenticateC300PM.

Check $FTESTS2 schematicdetails for the AUTHGROUP. There might be a

- 11 -

C300PM Front Panel LEDdisplay

Indicates… Recovery action

duplicate BOOTP server onthe network. Manualfailover to backup ENIMmay be necessary.

BRN Firmware load in progress. Wait for firmware load tocomplete.

DUP C300PM either has a duplicateFTE Device Index, or duplicatePdTag, or both duplicate FTEDevice Index and PdTag ofanother device in the FTECommunity.

Identify the duplicateproblem in the FTECommunity (using$FTESTS2 schematic orPC’s FTE Status Display)and remedy duplicate.

TS C300PM Controller is attemptingconnection to a configured timesource or the time server is notavailable (Transient state).

Set the correct time sourceon the Experion Server (thatis, SNTP or PTP).

NODB Before loading\reloadingC300PM platform block inControl Builder, the C300PMundergoes reboot operation. TheNODB status is displayed afterthe reboot operation.

SF If Soft Fail is detected on thehardware, the details of thefailure gets displayed in the UCNDetailed Status Display.

For example, In the ControlConfig, if IO link is not connectedto either of the A, B cables, thenan IOLINK failure status getsdisplayed in the UCN DetailedStatus Display.

Depending on the failurescenario, the recoveryaction can be performed.

IDLE C300PM controller when insertedon the chassis, it displays IDLEmode.

RUN Once the Database is restored, itis fed into the C300PM controller.On Startup, the C300PMcontroller shows RUN.

BKUP For a redundant C300PMController in the runningcondition, the Primary nodeshows RUN and the Backup nodeshows BKUP.

When you try to swap thecontroller by using Primary swap,the current primary node restartsand then shows BKUP while thesecondary node shows RUN.

- 12 -



For more information, see HPM/EHPM to C300PM Upgrade Kit Instructions (51195766-044) Guide.

2.3 C300PM vs EHPM

The following are the differences between C300PM and EHPM controllers.

Scenario C300PM EHPM

FAILOVER/SWITCHOVER During FAILOVER/SWITCHOVER,the new C300PM Backup nodeundergoes reboot. It takes about5 minutes for the Backup node toreboot fully and come back to theBACKUP state. This is consistentwith other CEP-based nodes.

DuringFAILOVER/SWITCHOVER,the new EHPM Backup nodedoes not undergo reboot.

In case of FAILOVER, thenew Backup EHPM nodeshows the status asFAIL/OFFNET.

In case of SWITCHOVER, thenew Backup EHPM nodeshows the status asBACKUP.

CF9 switches The C300PMs do not requireseparate CF9 switches in thenetwork as they have a built-inControl Firewall functionality andcan connect directly to the L2switch.

The EHPMs requireseparate CF9 switches toconnect to the L2 switch.

High-Performance I/O LinkModule

The High-Performance I/O LinkModule is not required inC300PM configuration as thisfunctionality is integrated withthe C300PMCommunication/Control Card.

The High-Performance I/OLink Module is a separateboard which is required inEHPM configuration.

Default start-up state The default start-up state forC300PM is IDLE. After flashingthe firmware or after powering upthe C300PM controller, C300PMcomes up with IDLE state andthe Backup node will come up asBACKUP. A Backup node willautomatically synchronize toBACKUP state after beingpowered on.

The personality software is builtinto the C300PM firmware. Thereis no need to load a C300PMwith HPM personality software,you only need to restore thecheckpoint.

The default start-up statefor EHPM is ALIVE. Afterflashing the firmware orafter powering up the EHPMcontroller, EHPM comes upwith ALIVE state and theBackup node will come upas ALIVE. A Backup nodewill automaticallysynchronize to BACKUPstate after being poweredon.

The personality softwareneeds to be loaded into theEHPM firmware.

RAM retention inC300PM/EHPM controller

Power Backup Module is requiredfor RAM retention in C300PMcontroller.

The Power Backup circuitryis integrated with the EHPMhardware. No separatehardware is required.

- 13 -


Homogeneous redundantpair (both Primary andBackup are C300PM orboth Primary and Backupare EHPM)

When both the Primary andBackup controllers are C300PM,the back plane Private Path HPMRedundancy cable is not requiredfor redundancy.

When both the Primary andBackup controllers areEHPM, both Ethernet 3rdport and the back planePrivate Path HPMRedundancy cable arerequired for redundancy.

Display button onC300PM/EHPM controller

There is no "Display " button forscrolling on C300PM controller.

The "Display" button forscrolling is available onEHPM controller.

Requirement for platformblock

Platform block is mandatory foran operational RedundantC300PM.

Platform block is optionalfor an EHPM, needed whenthe EHPM has beenintegrated with Experionand has the Experion BOOTand APP firmware flashed.

Firmware Flashing Use Firmware Manager forFirmware flashing in C300PM.

Separate power cycle process isnot required for C300PM as theFirmware Manager tool is able toreboot after flashing the C300PMfirmware.

Use the Stand Alone EPATool for Firmware flashingin EHPM.

On-process migration andon-process upgrade

Use Controller Migration Wizardfor on-process migration and on-process upgrade of C300PM. Seesection "To Update Firmware on anon-process Operational RedundantC300PM Node".

NOTE

C300PM doesnotsupport on-processbackward migration.

Use the Standalone EPAtool for on-processmigration and on-processupgrade of EHPM.

Standalone (BOOT only) C300PM does not supportStandalone firmware (BOOTonly).

EHPM supports Standalonefirmware (BOOT only).

Supported networks For C300PM, Experion IntegratedBOOTP network is mandatory.

EHPM supports Default IPseries (10.0.0.x), where x isthe Device Index configuredon the hardware or Non-BOOTP network.

Rebooting Rebooting C300PM takes longertime due to common embeddedplatform infrastructure. (time)

Rebooting EHPM takesshorter time.

CPUFREE behavior For C300PM, all Control and EHPM shows CPUFREE

- 14 -




Communication processes rununder the same processor andhence, the individual processescannot be distinguished. Theexisting CPUFREE parametersare modified as Core 0 and Core1 processors.

For C300PM, the COMM andCTRL CPUFREE values comefrom Core 0 and Core 1processors and they will notmatch with the COMCFAVG,CTLCFAVG or$NMxxByy.$UCNLSB (35) and(36) of EHPM even if thedatabase configuration and theload on the controller is thesame. Do not compare EHPMCOMM and CTRL CPUFREEvalues with C300PM Core 0 andCore 1 processor values.

value for individualprocessors like CommProcessor, CTRL Processorand EUCN Processorseparately.

Behavior of BackupC300PM/EHPM in theabsence of a PrimaryC300PM/EHPM

For a redundant C300PM, in theabsence of Primary C300PM, theBackup C300PM comes up withBackup state and then ittransitions to NODB state after afew seconds. If it does nottransition to NODB state, thenuse the ‘Become Primary’ optionfrom Redundancy tab in theBackup C300PM platform block.

For a redundant EHPM, theBackup EHPM directlycomes up with ALIVE state.

REBOOT option in RUNSTATES TARGET

The RUN STATES target in theNative Window’s UCN Status andUCN Detailed Status displays hasthe REBOOT option for aC300PM. A C300PM inIDLE/BACKUP state can berebooted using this option.

NOTE

When a C300PM is inOFFNET state inNative Window, theRUN STATES targetdoes not show theREBOOT option inNative Window. Itshows the defaultoption SHUTDOWN,which is not applicablefor a C300PM inOFFNET state.

The RUN STATES TARGETdoes not have the REBOOToption for EHPM controllers.

- 15 -


Use the followingaction to performreboot operation.

l From FirmwareManager, right-click on theDevice Index andclick REBOOT.

Servicing of data requests C300PM has improvedprocessing capabilities and canservice data requests at a higherrate than the EHPM. UnlikeEHPM, C300PM can servicethese additional requests withoutthrottling the data. Due to this,the C300PM may consumeadditional I/O link bandwidthwhen compared to an equallyloaded EHPM. Ensure that theC300PM’s I/O Link BandwidthFree is 20% or more.

EHPM throttles the dataaccess when the dataaccess requests are morethan the NPARAVGparameter or the COMMCPUFREE of EHPM is lessthan 20%.

Status LED Display onports

C300PM shows communicationonly with the TX LED that will beblinking with green light.

EHPM showscommunication with bothTX and Link. The TX LED willbe blinking with green lightwhereas the Link LED willbe displaying orange light.

The following are the differences between C300PM and EHPM during fault scenarios.

Fault Scenario C300PM EHPM

3rd port FTEredundancy cableremoval orbreakage fromPrimary or BackupC300PM/EHPMnode.

When the 3rd port FTEredundancy cable is removedfrom the Primary or BackupC300PM, the Backup C300PMreboots and goes to BackupNOSYNC state.

l Hardware LED Displayshows BKUP

l Native Window UCNStatus Display showsBackup node as OFFNET

l Firmware Manager showsBKUP

To recover, reconnect the 3rdport FTE redundant cable.

When the 3rd port FTE redundancycable is removed from the Primary orBackup EHPM,

l Hardware LED Display showsBackup SF

l Native Window UCN StatusDisplay shows Backup SF

To recover, reconnect the 3rd port FTEredundant cable.

C300PM/EHPM When C300PM goes to FAIL When EHPM goes to FAIL state, Native

- 16 -




node goes to FAILstate.

state,

l Hardware LED Displayshows FAIL

l Native Window UCNStatus Display showsOFFNET

l Firmware Manager showsFAIL

To view the correct status,physically reboot the C300PMwhich is in FAIL state orperform reboot operation fromFirmware Manager.

Window’s UCN STATUS shows EHPM’sstatus as FAIL.

To recover, select the node which is inFAIL state and click RECOVER targeton the UCN or HPM Status Display inNative Window.

FTE cables removalor breakage fromthe BackupC300PM/EHPMnode.

When both the FTE cables(Yellow and Green) areremoved from the BackupC300PM, the Backup C300PMwill lose synch with PrimaryC300PM.

l Hardware LED Displayshows BKUP

l Native Window UCNStatus Display showsOFFNET

l Firmware Manager showsBKUP

To recover, reconnect both theFTE cables. The BackupC300PM will reboot and cometo BACKUP state, and getsynched with Primary C300PM.

When both the FTE cables (Yellow andGreen) are removed from the BackupEHPM,

l Hardware LED Display showsBackup SF

l Native Window UCN StatusDisplay shows OFFNET

To recover, reconnect both the FTEcables to Backup EHPM.

Performing SWAPoperation onredundantC300PM/EHPMnodes.

When SWAP operation isperformed on redundantC300PM nodes, the BackupC300PM (Primary before SWAPoperation) undergoes rebootbefore becoming the Backupnode.

Note: The reboot might takearound 5 minutes.

When SWAP operation is performed onredundant EHPM nodes, the BackupEHPM (Primary before SWAPoperation) transitions from SWAP toSYNCH on the Hardware LED Displaybefore becoming the Backup node.

Duplicate UCNNode Numbersituation in thenetwork.

When a C300PM node is setup and powered ON withduplicate UCN Node Number,

l For Primary C300PM, theHardware LED Displayshows NODB

l For Backup C300PM, the

The new EHPM node does not comeup in network and the Hardware LEDDisplay remains in STRT and thenbecomes blank after detecting theduplicate address.

- 17 -


Hardware LED Displayshows BKUP

The new C300PM node showsin $FTESTS2 but not in$FTESTS1. This does notimpact the operation of theactual running C300PMhaving that UCN node number.

In a hybrid setup with EHPM as Primary and C300PM as Backup controller, when the EHPM platform blockis loaded, the C300PM shows NP state in hardware display and BKUP state in Native Window.

2.4 C300PM Deployment Requirements

Task Detailed Description Done?

Scheduling Installation of this upgrade kit requires powering-offthe backup node. Perform the upgrade activity at anappropriate time to avoid disturbance to the processand potentially hazardous consequences toequipment and personnel. Determine in advance thatthe scheduling of this procedure is in accordance withproper system operation.

This step is applicable if you are planning to upgradefrom HPM/EHPM to C300PM.

Card file Determine whether you are going to use a newC300PM card file or a spare HPM card file to installC300PM.

EUCN Configuration DataChecklist

Record the existing UCN and LCN address informationin the EUCN Configuration Data Checklist entries forHPMs/EHPMs. Record the FTE Device Indexinformation for EHPMs.

See section “Appendix A: EUCN Configuration DataChecklist” in the HPM/EHPM to C300PM Upgrade KitInstructions (51195766-044) Guide.

This step is applicable if you are planning to upgradefrom HPM/EHPM to C300PM.

Control Builder PlatformBlock

It is mandatory to configure the Platform block for thePrimary and Backup C300PMs in the Control Builderand load them to C300PM in order to get the C300PMrunning in redundant configuration.

For EHPM controller, the platform blockconfiguration in Control Builder is optional

- 18 -




and not a mandatory requirement forestablishing redundancy in EHPM.

NIM to ENB/ENIMupgrade

NIMs must be migrated to ENB to perform on-processmigration from HPM/EHPM to C300PM.

If you want to perform off-process migration, you canmigrate from NIM to ENIM.

For information on NIM to ENIM migration, see theNIM to ENIM Upgrade Kit Instructions (51195195-383). For information on NIM to ENB migration, seethe NIM to ENB Upgrade Kit Instructions (51195195-403).

Firmware upgrade If the EHPMs are on BOOT-Only firmware (EHPM_4.23), ensure that you migrate from standalone(BOOT-only) firmware to Experion-integrated (BOOTand APP) firmware.

For the migration procedures, see the CustomerRelease Guide for TPN R690.1.

CF9 Switch Installation C300PMs do not require separate CF9switches in the network as they have a built-in Control Firewall functionality and can bedirectly connected to L2 switches.

Installation of Honeywell-qualified CF9 Ethernetswitches is optional for HPM/EHPM to C300PM. IfCF9 is desired, ensure that prior to the installation ofthis upgrade kit, Honeywell-qualified CF9 Ethernetswitches are installed in the HPM cabinet.

For information about mounting and configuring theCF9 Ethernet switches in the LCN cabinet, see theCF9 Switch Upgrade Kit Instructions (51195766-036).

CF9 Hardware Rev. C should be flashed withfirmware version UU or later and CF9Hardware Rev. C should be flashed withfirmware version JJ or later.

TPN R690.1 The minimum version of TPN software required is TPNR690.1.

All TPN nodes and controllers must first be migratedto R690.1 before starting the migration.

For the migration procedures, see the CustomerRelease Guide for TPN R690.1.

Experion R511.5 The minimum version of Experion software required isExperion R511.5. All Experion nodes and controllersmust first be migrated to R511.5 before starting themigration.

EUCN migration It is required that all LCN and UCN nodes migrating to

- 19 -


EUCN must be on TPN R690.1.

EUCN node integrationwith Experion

Direct communication between Experion and C300PMrequires the optional C300PM-Experion ConnectionEnabler license. If you want to use this feature, thenyour Experion system must be at a minimum ofExperion R511.5 and TPN system at a minimum ofTPN R690.1.

If the EHPMs run the Boot-only firmware (e.g. EHPM_4.23), then it must be migrated to the ExperionIntegrated firmware (Boot and APP) before attemptingon-process upgrade to C300PM. The migration fromBoot-only to Experion Integrated firmware can also beperformed on-process.

Ensure that prior to the migration, the existing EHPMsmust be flashed with the Experion BOOT and APPfirmware. For more information on Firmware Manager,see the Firmware Manager User’s Guide (EPDOC-X470-en).

C300PMCommunication/ControlCard and EHPM FTEInterface Moduleavailability

Ensure that prior to the installation of this upgrade kit,the C300PM Communication/Control Card and theEHPM FTE Interface Module are available for upgrade.Note that existing EHPM FTE modules may be used inplace of a new one.

UCN terminators If the UCN is not completely migrated to EUCN, andyou will have any operational UCN nodes, then ensurethat you have spare UCN terminators. These arerequired when you have upgraded all HPMs toC300PMs and the UCN coaxial cabling can becompletely removed from the UCN cabinet.

Ethernet cables Ethernet cables are not included in an n upgrade kit,because the length of the cable used is customer-specific. You can use cables with part numbers51305482-1XX (where, 1 specifies yellow boots andXX = length in meters) and 51305482-2XX (where, 2specifies green boots and XX = length in meters).

As an alternative, for total cable distances less than 33meters, you can use an all-yellow ScTP cable(51305978-1YZ; where, YZ = length in feet) and an all-green ScTP cable (51305978-2YZ; where, YZ = lengthin feet).

For more information, see the Fault Tolerant EthernetOverview and Implementation Guide.

Check Power Switch onI/O Link Card

Before removing the High-Performance I/O Link Card,ensure that you check the card for frozen or stuckpower switches using the procedure mentioned in thePriority Notification PN 2018-15.

In order to validate the usefulness of the High-Performance I/O Link card to be removed for possiblespare stock usage, perform the procedure mentioned

- 20 -




in the Priority Notification PN 2018-15.

To download the Priority Notification PN 2018-15,visit the Honeywell Online Support website(honeywellprocess.com).

Experion BOOTPconfiguration

C300PM derives its IP Address from the Base IPconfigured in Experion Server. The first 3 octets aretaken from the Base IP and the last octet is derived byadding the last octet of Base IP and the device indexconfigured for the C300PM. If there are multipleExperion clusters in the same FTE community, thenthe service “Experion PKS BootP Server” must berunning only in one cluster where the Base IP isconfigured and in other clusters it must be disabled.For more information on BOOTP server and Base IPaddressing, see Section “Running the EPA tool on theEnhanced Universal Control Network” in the HPMInstallation Manual (HP20-600).

SNTP configuration C300PM can synchronize its time either usingPrecision Time Protocol (PTP) or Simple Network TimeProtocol (SNTP). Primary and Backup Experion Serversshall be configured as Primary and Backup SNTPservers. In that case, the Primary and Backup ExperionServers must be setup as SNTP server using thentpconfig utility that is available under 'C:\ProgramFiles (x86)\Honeywell\ExperionPKS\Utilities\NTPSetup'. For more information, see thefollowing Experion documents.

l Supplementary Installation Tasks Guide, section“Setting up time synchronization in a Windowsdomain checklist”

l Control Builder User’s Guide, section “ControlBuilder System Administration,” subsection“Setting System Preferences”

2.5 Example of UCN and EUCN topology diagram showingaddition of C300PM

The following diagram illustrates one example UCN and EUCN topology diagram showing addition ofC300PM, described as follows.

- 21 -

The on-process migration from HPM/EHPM to C300PM is accomplished by shutting down the SecondaryHPM/EHPM and upgrading it to C300PM while the Primary HPM/EHPM is still running. After the upgradedsecondary node takes over as the Primary C300PM (after performing SWAP PRIMARY operation), theC300PM platform block is loaded from the Control Builder, the original Primary HPM/EHPM is shut downand upgraded to a C300PM.

The complete upgrade from HPM/EHPM to C300PM can be performed on-process for a redundantHPM/EHPM node.

Prior to shutting down the HPM/EHPM, checkpoint the node and perform LCN backup of all the checkpointed files.

For more details about the migration procedure, see:

Hardware: PM/APM to C300PM Upgrade Kit Instructions (51195766-043) and HPM/EHPM to C300PMUpgrade Kit Instructions (51195766-044)

Software: section "Migration" in the C300PM Overview and Implementation Guide (EPDOC-X729)

- 22 -


C300PM DEPLOYMENT CONSIDERATIONS

3.1 FTE Community and UCN Considerations

In summary, the following FTE and UCN constraints apply to the deployment of C300PM in an ExperionLCN network.

l An EUCN must belong to the same FTE community as the Experion LCN to which it is connected.

l An Experion LCN may connect to multiple EUCNs.

l An EUCN cannot be shared between Experion LCNs.

l Honeywell FTE Best Practices must be followed.

REFERENCE: For more details, see Experion Network Best Practices.

3.2 FTE Device Index and IP Addressing

You must assign each node within an FTE community a unique Device Index. The Device Index is the FTEnode number.

Device Index rules - For a non-redundant node or the primary of a redundant pair, always assign an odd-numbered Device Index. For a redundant pair, assign the next even-numbered Device Index to thesecondary.

The FTE IP address of a node is calculated as: FTE IP Address = base IP address + Device Index

The FTE network uses floating IP addresses for C300PM Nodes. The node in the primary role uses thelower (odd) IP address, and the node in the secondary role uses the higher (even) IP address. This IPaddress follows the primary when a switchover occurs.

Example:

Base IP address - 192.168.1.0

Primary C300PM address - 192.168.1.23, where 23 is the user assigned physical Device Index

Secondary C300PM address - 192.168.1.24

Example: If the Device Index is 257, then the IP Address of the primary is 192.168.2.1

The FTE IP address rules for the C300PM are:

l the Experion Base IP address must be configured,

l the “Experion PKS BOOTP Server” Windows service must be running on the primary ESV-T, and

l the Device Index must be entered into the FTE Interface Module for the physical primary andsecondary C300PM.

- 23 -

CHAPTER

3

3.3 Experion TPS Node Configuration Requirements forC300PM

3.3.1 Configuring Experion Base IP Address and (S)NTP IP Address

Base IP Address

Embedded FTE nodes, such as the C300PM nodes, receive their IP addresses from the FTE bootstrap(BOOTP) server based upon the server’s Base IP Address and the node’s Device Index. In order for theC300PM Nodes to be assigned an FTE IP address, the Experion Base IP address must be configured andthe “Experion PKS BOOTP Server” Microsoft Windows service must be running on the primary ExperionServer.

Note that EHPM and C300 also receive their IP Addresses from the BOOTP server.

Typically, Default Gateway is not used.

(S)NTP Server IP Address

The (S)NTP Server IP Address must be configured in order for nodes to synchronize their time. Thepreferred time source is Network Time Protocol (NTP) operating on the primary and secondary ESVTs (asa time server).

As a best practice, enter the IP addresses as follows:

Primary Server – IP address of the “B” (intended backup) ESVT. Assign the backup ESVT as the primarytime source.

Secondary Server – IP address of the “A” (intended primary) ESVT.

3.3.2 Time Synchronization Considerations

Configure NTP Time Source

Since the Windows-based Experion TPS nodes are required to be part of a Microsoft Windows domain,these nodes will use the Microsoft Windows domain time source for synchronizing time. A known good timesource should be used in the Microsoft Windows domain setup.

An NTP Time Source should be configured. Typically, the ESVTs are configured to be the NTP TimeSource. A Precision Time Protocol (PTP) time source is optional.

A PTP time source is required if using EHPMs/C300PMs with DISOE IOP, when precision SOEtimestamps are desired.

REFERENCE: For more information see the section “Configuring Experion Base IP Address and (S)NTPIP Address”.

3.4 Supported System Topologies

C300PM can support many different network topologies. Depending on the ENIM under which the C300PMis configured, there can be different topologies. C300PM controller can be configured to run under:

l EPNI2-based ENIM

l ENB

l ELCN UEA ENIM

l ELCN UVA ENIM

- 24 -

Chapter 3 - C300PM Deployment Considerations


The FTE traffic on the ELCN ENIMs transports two streams of data. One stream is the encapsulated UCNdata between the ENIM and C300PMs. The other stream is the encapsulated LCN data between theENIMs and other ELCN nodes.

C300PM controller is considered as one FTE node against the 330 FTE node limit on an Experion cluster.Note that redundant C300PMs count as 2 FTE nodes against the 330 FTE node limit on a C300PM cluster.

The following are the two examples depicted with the topology diagrams.

Example Topology 1

C300PM controller is directly connected to the Level 2 network and communicates with other controllersover the FTE network. When C300PM is directly connected to the Level 2 network, the port to which it isconnected must be configured with 'AUTO' speed.

Example Topology 2

C300PM controller connected to the L2 switch via CF9. In a scenario, if we do not want to disturb any wiringwhile upgrading EHPM to C300PM in the existing installation and architecture, then we will have to connectit via CF9.

- 25 -

3.5 Security Considerations for EUCN

Limit physical access to the system. Make arrangements for key-locked cabinets with access allowed onlyto authorized personnel.

Key-locked cabinets, with access allowed only to authorized personnel, are required.

Restrict network access to the Experion LCN. L3 users should not be able to communicate to the ExperionLCN TPS Nodes through the L2 switch. Follow the Experion Security Model for placing files/folders,providing folder permissions, Experion user accounts, Experion group policies, and execution rights.

Place TPN Checkpoint files in a folder that can only be accessed by authorized users. Use the defaultinstallation directory for the .lcn files. If you choose to use a different directory, the permissions should beset to have only the TPN users access the directory.

REFERENCE: See the following documents for specific security information.

l For information on securing peer-to-peer communications between devices, see the Experion Networkand Security Planning Guide.

l For information on restricting the systems to authorized users, see the Experion Network BestPractices.

l For information on FTE network architecture, guidelines, and requirements, see the FTE Overview andImplementation Guide (FTE02).

3.6 LVRLOG report

For more information, see section "LVRLOG General Functionality" in the Engineer’s Reference Manual(SW09-605).

3.7 Audit Tool report

For more information, see section "File Formats and Post-Processing" in the TPS System Audit Tool UsersGuide (TP21).

- 26 -


INSTALLATION

Initial startup of a C300PM involves interpreting the status LEDs and front panel display following power-up, entering the FTE Device Index through the front panel display, and then verifying the FTE IP Addressacquired from the Experion BOOTP server for both the Primary and Secondary C300PMs.

For detailed procedures to perform initial C300PM startup, see section "HPM/EHPM to C300PM on-process migration" in the HPM/EHPM to C300PM Upgrade Kit Instructions (51195766-044) Guide.

- 27 -

CHAPTER

4

CONFIGURATION

5.1 Updating initial firmware using Experion FirmwareManager

For more details, see section "Getting Started with Firmware Manager for C300 Process Manager(C300PM)" in the Firmware Manager User's Guide.

5.2 Configuring platform block using Control Builder

5.2.1 Overview

Starting with Experion R511.5, the C300PM nodes are integrated in the Experion network. Peer-to-Peercommunication between the C300PM Controller and the ACE/C300/UOC controllers is supported fromthis release onwards, the ACE/C300/UOC initiates peer-to-peer communication and the C300PM acts asthe responder.

5.2.2 Creating and configuring a C300PM block

C300PM block is a platform block that represents the actual C300PM hardware. Configuring a C300PMblock is similar to configuring other Experion platform blocks like ACE or C300 or UOC. The platform blockused for C300PM is same as the platform block used for EHPM controller. To configure a C300PM block,you must have the following details.

l UCN network number

l Corresponding HPM node number in the UCN network

l Device index of C300PM

l Device Index of Owning ENIM

NOTE

This procedure is applicable for both redundant and non-redundant C300PM blocks.

Do not leave the C300PM block locked in Control Builder for a prolonged period, the ELCN DatabaseImport Utility cannot update the C300PM points in ERDB during this time.

To create and configure a C300PM block

- 28 -

CHAPTER

5

1. For primary and non-redundant C300PM block, on the Control Builder File menu, click File > New >Controllers > EHPM – EUCN Controller.

The C300PM configuration form appears.

2. On the Main tab, complete the following details.

a. Tag name: Type a unique tag name for identification.

b. Device Index: Type the unique FTE device index number of the C300PM.

c. Enable DEB Operations: If you enable the “Enable DEB Operations” check box, Control Builderis used for C300PM points configuration and load. In this case, navigate to the 'Point Mix' taband ensure that the point mix matches with the UCN Node Specific configuration. Also, ensurethat all the IOPs that are configured are imported to ERDB and listed under the EHPM platformblock in Control Builder Project side.

If you do not plan to use Control Builder for C300PM points configuration and load, disable the“Enable DEB Operations” check box and load the C300PM platform block.

d. Platform Type: This is a ViewOnly parameter. It displays EHPM or C300PM when loaded to anEHPM or C300PM controller.

NOTE

For information about these parameters, see the Control Builder Parameter Reference.

3. For primary C300PM blocks (in a redundant configuration) only: If the C300PM is a redundant node,select Module is redundant under Redundancy Configuration.

NOTE

Secondary C300PM block is created only if you check the Module is Redundant checkbox.

4. On the EUCN tab, complete the following details.

a. UCN Network Number: Type the UCN Network Number.

b. HPM Node Number: Type the corresponding node number in the UCN network for the C300PMbeing configured.

c. Device Index of Owning ENIM: Type the unique FTE device index of the Owning ENIM.

NOTE The ENIM IP address is calculated based on the Owning ENIM device indexentered.

d. Device Index of Remote ENIM: Type the unique FTE device index of the Remote ENIM.

NOTE The ENIM IP address is calculated based on the Remote ENIM device indexentered.

e. If you want to import C300PM points into ERDB from the Remote ENIM, check the EnableImport check box.

- 29 -

Chapter 5 - Configuration


f. If you want to enable automatic C300PM point import into ERDB, check the Enable automaticpoint import check box.

Before enabling automatic point import, consider the following.

l It is recommended that you import C300PM points into ERDB using the EHPM Point ImportUtility if you are doing it for the first time. For subsequent imports, you can enable automaticpoint import.

l Ensure that the ENAME back plane module that executes on ENIM is configured. Forinformation on configuring ENAME back plane module, see the Customer Release Guide inthe TPN/TPS book set.

l Ensure that TPS File Transfer is installed, configured, and TPS File Transfer must berunning in ESVT B.

l Ensure Experion PKS EHPM Auto Import service is running on the ESVTB.

l If the C300PM block is checked-in under QVCS, do not enable automatic point import,instead, always perform manual import of C300PM points into ERDB.

For information on manually importing C300PM points into ERDB using the EHPM Point ImportUtility, see Importing EHPM points into ERDB.

Beginning with Experion R511.3, for information on importing TPN points into ERDB using theELCN Database Import Utility, see section "Importing TPN points into ERDB" in the "ExperionLCN (ELCN) Engineering Operations Guide".

After enabling automatic point import, verify that the Experion PKS EHPM AutoImport Servicehas established connection with the ENIM and executed first transfer of point data for theC300PM.

NOTE Check pointing C300PM from Native Window triggers automatic transfer ofC300PM points into ERDB.

g. EHPM Data Access: Select one of the two options from the drop-down box as perrequirements. Peer to Peer Only option is selected by default.

l If you select Peer to Peer Only option, it allows the C300PM points to do peer-to-peercommunication only.

l If you select Peer to Peer and ExpServer, it allows the C300PM points to do peer-to-peercommunication and they can be downloaded to the Experion server. On selecting thisoption, any display or history Read request to the controller is accessed through the CDApath. Any Write operation from display will go through the TPN path.

Before changing the C300PM Data Access option from Peer to Peer Only to Peer to Peer andExpServer, you must evaluate the effect of this switch on the C300PM Controller.

For more information, see CDA data access effect on EHPM performance.

The value of C300PM Data Access parameter defined on the C300PM block applies to all theC300PM points of the respective C300PM Controller.

h. Select a value for Display Subscription Cache FrshFt. 50 is selected by default. This enablesinternal caching of parameters requested by subscribed CDA display clients.

NOTE When multiple CDA display clients send requests to the same parameters,data may be returned from cache, effectively reducing PPS load on the respectiveC300PM.

- 30 -

Importing_EHPM_points_into_ERDB-cb_g.html

If you set the value to 0, then the internal caching is disabled and all subscribed CDA displayclients are serviced independently of each other.

i. Set a value for Display Subscription Max PPS. 500 is set by default. This configures PPSthreshold on subscribed CDA display read requests. If the limit is reached, the C300PM reducesthe collection rates for subscribed CDA display requests approximately by a factor of two.

5. Click OK.

Results

The configured C300PM block appears on the Project view of the Control Builder. You may now proceedwith importing of C300PM points into ERDB.

5.2.3 CDA data access effect on C300PM performance

Before you configure ACE/C300 peer-to-peer references to the C300PM points, you must evaluate theeffect of additional load on the C300PM that is generated by the requests executed on behalf of the CDAclients.

The limit on parameter throughput in the C300PM has been estimated at 1000 parameters per second. Thetotal number of parameter requests from all TPN and CDA clients to any individual C300PM should notexceed this value.

Experion clients (for example, HMIWeb displays, applications, history and so on) that are executing onExperion server and console stations may redirect read requests to C300PM through CDA., whereas writerequests are not redirected to CDA.

Parameter throughput is the total number of parameters that can be serviced per second.

If you are configuring CDA peer-to-peer references to a C300PM, ensure that the C300PM has enoughspare processing capacity to take up additional load.

The parameter throughput load that is generated by the CDA peer-to-peer clients is estimated as follows:

l Read: determined by the initiating node’s peer subscription period. All peer-read requests generated bythis node follow this period.

NOTE It is not recommended to use C300 Peer Subscription Period = 100 ms, for theC300PM references.

l Write: usually determined by the execution rates of the writing CMs on the initiating node.

The CDA data access to the C300PM, that is generated by the Experion server imposes a similar load tothe load originally imposed on the C300PM before switching data access path from the TPN Server to theCDA Server.

For more information, see the HPM Implementation Guidelines in the TPN/TPS book set.

5.2.4 Importing C300PM points into ERDB

After you have configured the C300PM platform block, import the C300PM points into ERDB. Thisprocedure can be completed using the ELCN Database Import Utility that can be invoked from PrimaryESVT, Backup ESVT, ES-T or Flex stations, by browsing to the following path: Start\Honeywell ExperionTools\All Honeywell Tools\Engineering Tools\ELCN Database Import Utility.

The ELCN Database Import Utility is added to the Experion Engineering tool set for transferring LCN/UCNpoint configuration data to Experion databases.

- 31 -



ATTENTIONThe NCF.CF file must be copied from NET > &ASY to the same folder as the checkpoint filesotherwise the unit name parameter will be empty causing the point load to fail.

NOTE

If there are already existing Experion Server Peer Responder connections to the points in theC300PM controller, you cannot update/import those points on the ERDB. If you want to import thosepoints, delete the associated Experion Server Peer Responder connections, and then proceed withimport.

The import will list those points and that list can be used for the delete operation.

NOTE

While creating any new channel or point in Native Window, do not use syntax similar to the ERDBTemplate Names or Channel Names. If any of the following ERDB Template Names or ChannelNames are used in the syntax, while performing Auto-Import/Manual Import, the error “IXP—TAG:point name: Creating Function Blocks – Another Function Block with the same name ‘point name’already exists.[EXPKS_E_IXP_DUPLFBNAME]” is reported.

Please see the following table for Template Names to be avoided.

- 32 -

Template names

EHPM

EHPMSEC

CEEEHPM

EHPMEE

EHPMANALGIN

EHPMANALGOUT

EHPMARRAY

EHPMDEVCTL

EHPMDIGCOMP

EHPMDIGIN

EHPMDIGOUT

EHPMFLAG

EHPMLOGIC

EHPMNUMERIC

EHPMPROCMOD

EHPMREGCTL

EHPMREGCTL_AUTOMAN

EHPMREGCTL_INCRSUM

EHPMREGCTL_MULDIV

EHPMREGCTL_OPSELCT

EHPMREGCTL_ORSEL

EHPMREGCTL_PID

EHPMREGCTL_PIDERFB

EHPMREGCTL_PIDFF

EHPMREGCTL_PIDPOSPR

EHPMREGCTL_POSPROP

EHPMREGCTL_RAMPSOAK

EHPMREGCTL_RATIOCTL

EHPMDIGINA

EHPMDIGINA_C

EHPMDIGINS_C

EHPMDIGOUTP

EHPMDIGOUTP_C

EHPMDIGOUTS

EHPMDIGOUTS_C

EHPMFLAG_C

EHPMLOGIC_C

EHPMNUMERIC_CEHPMPROCMOD_C

EHPMREGCTL_C

EHPMREGCTL_AUTOMAN_C

EHPMREGCTL_INCRSUM_C

EHPMREGCTL_MULDIV_C

EHPMREGCTL_OPSELCT_C

EHPMREGCTL_ORSEL_C

EHPMREGCTL_PID_C

EHPMREGCTL_PIDERFB_C

EHPMREGCTL_PIDFF_C

EHPMREGCTL_PIDPOSPR_C

EHPMREGCTL_POSPROP_C

EHPMREGCTL_RAMPSOAK_C

EHPMREGCTL_RATIOCTL_C

EHPMREGCTL_SUMMER_C

EHPMREGCTL_SWITCH_C

EHPMRPV EHPMRPV_C

EHPMRPV_CALCLTR

EHPMRPV_CALCLTR_C

- 33 -



EHPMREGCTL_SUMMER

EHPMREGCTL_SWITCH

EHPMREGPV

EHPMREGPV_CALCLTR

EHPMREGPV_DATAACQ

EHPMREGPV_FLOWCOMP

EHPMREGPV_GENLIN

EHPMREGPV_HILOAVG

EHPMREGPV_MIDOF3

EHPMREGPV_SUMMER

EHPMREGPV_TOTALIZR

EHPMREGPV_VDTLDLAG

EHPMTIMER

EHPMANALGIN_C

EHPMANALGOUT_C

EHPMDEVCTL_C

EHPMDIGCOMP_C

EHPMRPV_DATAACQ

EHPMRPV_DATAACQ_C

EHPMRPV_FLOWCOMP

EHPMRPV_FLOWCOMP_C

EHPMRPV_GENLIN

EHPMRPV_GENLIN_C

EHPMRPV_HILOAVG

EHPMRPV_HILOAVG_C

EHPMRPV_MIDOF3

EHPMRPV_MIDOF3_C

EHPMRPV_SUMMER

EHPMRPV_SUMMER_C

EHPMRPV_TOTALIZR

EHPMRPV_TOTALIZR_C

EHPMRPV_VDTLDLAG

EHPMRPV_VDTLDLAG_C

To check the errors, click Import Errors on the IMPORT COMPLETED page for C300PM.

Or, view the log file in the following path C:\ProgramData\Honeywell\Experion PKS\IMPORTLOGS.

The following is an example of the Import Errors log file.

Prerequisites for importing C300PM points into ERDB

l The C300PM Checkpoint files that contain the C300PM points are already created in the .cp formatand the files are transferred using the File Transfer utility and copied to a folder in the respectivemachine.

- 34 -

l The NET > &ASY > NCF.CF file should be available.

l C300PM Platform block is configured in Control Builder.

l For redundant server, make sure that the Server B is running.

l The ES-T should have an active connection with the LCN.

To import C300PM points into ERDB

1. Launch the ELCN Database Import Utility from the following location: Start > Honeywell ExperionTools > All Honeywell Tools > Engineering Tools > ELCN Database Import Utility.

The Import Options page appears.

2. Enter the Server Name.

You must either enter the base name of the server without suffix A/B or the complete name of thecurrent primary server with suffix A/B or IP address of Primary server.

3. Click Connect.

A connection with the server is established.

Click Disconnect if you want to disconnect and then connect to another Experion Server.

4. Enter the following server details:

User Name

Password

Domain

NOTE

If Domain is not present, provide the primary server host name.

- 35 -



The server details are required to establish connection with the ESVT B for successfully loading thestrategies to the Monitoring Tree.

5. Perform the following to import C300PM checkpoints.

To import C300PM points

Select NIM under Select Node Type.

- 36 -

To Import Checkpoints

a. Select CHECKPOINT under Select to Import to import NIM checkpoints.

b. Browse the Checkpoint file to select the NIM Checkpoint file.

c. Click NEXT. The Node Selection page appears.

d. Select the node that you want to import.

- 37 -



e. Click NEXT. The Switch Active Peer Responder Connections page appears.

To use the CDA capability in C300PM, it is recommended to switch the C300PM CDA PeerResponder Connections to the direct CDA peer-to-peer connection.

To remove the C300PM CDA Peer Responder Connections, see section "Deleting/movingC300PM points having existing Experion Server Peer Responder connections". Once theconnections are removed, the ELCN Database Import Utility will automatically switch theconnections to direct CDA.

- 38 -

NOTEAfter deletion of the C300PM CDA Peer Responder Connections from ControlBuilder, to enable the Switch Connection check box, click Back and then click Nexton the Node Selection page.

f. If you have any peer responder connections, click Save to File to save them.

If you do not have any peer responder connections, the message "No active peer responderconnections. Please click next." displays.

g. Click NEXT. The Review Selections page appears.

h. Click Modify of Step 1 to change the Experion Server, Select to Import option, Node Type andCheckpoint File.

Click Modify of Step 2 to change the Node selected.

Click Modify of Step 3 to save the Switch Active Peer Responder Connections, if not savedalready.

i. Click IMPORT.

The confirmation message "Are you sure you want to start the Import?" appears. Click Yes.

- 39 -



j. The import status report page appears. Click START NEW IMPORT to import new checkpoints.

The following table has description of the information provided by the Import status report.

- 40 -

Description

Import status The status of import operation.

Controller name The platform block name configured inControl Builder.

Controller status The status of whether the platform blockloaded to the Monitoring Tree

Points deleted The number of points deleted in ControlBuilder. Click the Deleted Points option toknow which points are deleted in ControlBuilder.

Pointsadded/changed

The number of points that are added orchanged in Control Builder. Click the AddedPoints option to know which points areadded in Control Builder.

Points inCheckpoint file

The total number of points in the HPMcheckpoint file being imported.

Points inController beforeimport

The total number of points in the ControlBuilder Database (ERDB) before performingimport.

Points inController afterimport

The total number of points in the ControlBuilder Database (ERDB) after importing.

Added Points The total number of points added in ControlBuilder.

Deleted Points The total number of points deleted in ControlBuilder.

NOTE

The points in checkpoint file match with the points in controller after import. If thereare any invalid points or ghost points in the checkpoint file, there may be a differencein the number of points in checkpoint file and the number of points in controller afterperforming import. Such points may be visible under Unassigned section in theControl Builder Project Tree.

k. Click FINISH to complete the process

- 41 -



NOTEWhen a C300PM SCADA point’s parameter is configured in a CM/SCM Expression and thatCM/SCM is selected for Switch Active Peer Responder Connections, after the completion of ELCNDatabase Import operation, the Control Module load may fail with “CL_BLKLOADFAIL” error onperforming manual load.

As part of import, if any C300PM point parameters are configured as peer connections in C300AUX_CALC/SCM Expression, then ensure that "?" is not present at the end of the point.parametername. If "?" is present, remove the “?” from the end of the parameter name, save the configuration,and then load the CM/SCM.

Results

Import log: A detailed log file is available under:

For C300PM: C:\ProgramData\Honeywell\Experion PKS\EhpmImport.log

This log file has details such as the date and time of import, checkpoint file name that was imported and thelist of point names that were imported along with any errors encountered during the import operation.

C300PM Auto Import Functionality

After the ELCN platform block configuration, you can import the TPN points into ERDB. This procedure canalso be performed using the C300PM Auto Import functionality. The new C300PM Auto Import functionalityis applicable for Experion release R511.3 or later.

Prerequisites

l TPS File Transfer License must be available, configured, and TPS File Transfer must be running inServer B.

l Latest ENIM, C300PM checkpoint, and NCF files are available in History Module (HM).

l HM must be running with Online Personality.

l C300PM platform block must be configured in ERDB and the AUTOIMPORT option must be checkedduring platform block configuration.

l The service “Experion EHPM Auto Import Service” must be running in Server B.

Beginning with the Experion R511.3, the Auto Import functionality for EHPMs is supported only on ESVTnodes (ESVT-B, in case of a redundant server), when the TPS File Transfer Application is installed andconfigured. The Auto Import service on ESVT uses the new ELCN Import Library created for the UnifiedEngineering Tools feature that is introduced in R511.3. This new import library requires the NCF file, ENIMand EHPM checkpoints to be saved/available in the History Module (HM). When there is a trigger for AutoImport, the new Auto Import service starts copying the required files from HM toC:\ProgramData\Honeywell\Experion PKS\EnimPointFiles path followed by importing to ERDB.

If the AUTOIMPORT option is enabled in the EHPM platform block, then the following triggers Auto Importoperation:

l The ENIM checkpoint save is initiated from Native Window (either manually or with scheduled task).

l ENIM failover occurs in a redundant ENIM setup.

l Experion PKS EHPM Auto Import Service is restarted on the ESVT-B server.

If Auto Import is not functioning on ESVT node, perform the following steps:

- 42 -

1. Disable the AUTOIMPORT option and then enable it on the EHPM platform block.

2. Start the TPS File Transfer Service using the Services Console, if it is not running.

3. Stop the Experion PKS EHPM AutoImport Service using the Services Console, if it is running.

4. Open Windows Task Manager and check if any File Transfer applications like “ftcopy.exe” or “ ftsearch.exe” are running, if yes, kill these applications.

5. Start the Experion PKS EHPM AutoImport Service.

6. Wait for the EHPM Auto Import to complete.

NOTE

Beginning with Experion R511.3, the Auto Import operation might take slightly longer time tocomplete as compared to the previous releases as it imports additional parameters for each of thepoints.

On every Auto Import operation, only the points that are added or deleted in Native Window will beupdated in the Control Builder. Any parameter changes on the existing points through theRECONSTITUTE operation will not be updated during Auto Import.

In order to get the updated parameter information from the Controller after RECONSTITUTE fromNative Window, perform Upload to Monitoring and Update to Project operation. This ensures thatany subsequent reload of the point from the Control Builder Project Form has the latest informationas the point on the Controller.

If multiple points are reconstituted from Native Window due to unavoidable circumstances, it isrecommended to rerun the ELCN Database Import Utility manually. This might take some time.

NOTE

After the LCN checkpoints are imported into ERDB, it is recommended to use Control Builder as theengineering tool, that is, use Control Builder to perform operations such as,adding/modifying/deleting point database. If these operations are performed using Native Window,then you must verify and compare the point import after a manual import/auto import is triggered.

This also requires the value 'Enable DEB operations' to be set in the C300PM platform block and areload of the C300PM platform block.

5.2.5 Loading a C300PM block

Use the following procedure to load a C300PM block.

NOTE

l There is no CEE associated with a C300PM block.

l Loading a C300PM block also loads C300PM points if any, into ERDB.

l During loading of an C300PM block, if TPS points do not exist in the Experion Server or isnot configured properly in the Experion Server, then the load operation skips the entiredownload to server operation.

l For a C300PM Controller, “Load” operation includes “Load with Contents”. A separate“Load with Contents” option is not available for the C300PM Controller.

- 43 -



NOTE

C300PM Data Access can be configured by using any of the following two options, after setting thevalue of the C300PM Data Access parameter on the C300PM block, load/reload of the C300PM isrequired to make the changes effective on C300PM points.

l Loading a C300PM block with Peer to Peer and ExpServer option: Enables peer dataaccess between the Experion controllers and the C300PM points through the CDA.Experion Server (re)discovers any display or any client data read access path to theC300PM point(s) parameters, C300PM point(s) parameters are then routed through CDApath. Any Data write access request from Displays or other Experion clients will go throughTPN path.

The C300PM block must be loaded to the Monitoring tree in Control Builder to reflect the change inparameter value.

Prerequisites

l Control Builder is running.

l C300PM block must be configured.

l License validation checks must be made before loading the C300PM block.

l C300PM hardware installation and configuration is complete.

l C300PM is already part of the Experion network.

l TPN Server is running on the primary Experion server .

l CDA Server is running on the primary Experion server .

l If 'Enable DEB Operations' is set in the platform block of C300PM for an existing configuration, ensurethe following.

o The C300PM points are imported into ERDB.

o The point mix in the 'Point mix' tab on platform block should match with the UCN NodeSpecific configuration.

o The IOPs configured in Node Specific Configuration are imported into ERDB and are listedunder the C300PM platform block.

To load a C300PM block

- 44 -

1. Right-click on the configured C300PM block and then click Load.

Loading a C300PM platform block to Monitoring tree gives the following warning.

This is displayed only when the 'Enable DEB Operations' is set.

Although the warning mentions EHPM, it is for C300PM and can be ignored. Click Continue to fix theerror.

Loading a C300PM platform block to Monitoring tree gives the following warning.

This is displayed only when the 'Enable DEB Operations' is not set.

Although the warning mentions EHPM, it is for C300PM and can be ignored. Click Continue to fix theerror.

Load confirmation dialog box appears.

2. Click Continue.

Load Dialog box is displayed which provides a list of objects that can be loaded. Since the C300PMblock is selected, it lists the selected C300PM block in the Load Dialog box.

3. Click OK.

Load box shows the progress of load operation.

Results

After load operation is completed, C300PM block icon appears on the Monitoring tree in Control Builder.

NOTE

For C300PM controller, configuration of platform block in Control Builder and loading is mandatory.This was optional for an EHPM controller.

- 45 -



5.2.6 Deleting/moving C300PM points having existing Experion ServerPeer Responder connections

When C300PM points are moved to different hardware location or deleted from the controller, and peer-to-peer connection to these points exist in the ACE /C300 CEE, then delete or move the associated ExperionServer Peer Responder connections and then proceed with import.

Consider a scenario:

l CM_1 executes in a C300 CEE; periodically reads TIC101.PV directly from the C300PM.

l CM_2 executes in ACE CEE; periodically reads TIC102.PV directly from the C300PM.

l TIC101 point is moved to a different slot in the C300PM.

l TIC102 point is deleted.

1. From the browser search report (“WhereUsed” Search), list down all the connections where TIC101and TIC102 are referenced.

CM_1 and CM_2 are displayed.

2. Deactivate CM_1 and CM_2 and then delete them from the Monitoring tree of the C300 CEE and ACECEE respectively.

3. Make sure that there no active alarms on the Experion Alarm Summary for the TIC101 and TIC102points, in case of any alarms, clear them.

4. If the TIC101 point to be moved is assigned to history, groups, or trends on the local server, performthe following steps on the primary ESVT:

a. Ensure the ESVT is synchronized with its backup server.

b. Log in using an account that is a member of the Product Administrators group.

c. At the command prompt, type:

bckbld -np -tag PSA -out ESVTConfig.pnt

This creates an ESVTConfig.pnt point build file with a list of the Experion group, trend, andhistory configuration for TPS points.

d. Save the ESVTConfig.pnt in a safe place. If for some reason you lose the group, trend, or historyconfiguration for your TPS points you can restore it with this file. TIP: Not all points output areTPS points.

e. If the TIC101 and TIC102 points exist in the history, groups, or trends on the local server,remove them.

5. If the TIC101 point to be moved is assigned to groups or trends on remote servers, perform thefollowing steps on each remote server (ESV or ESVT):

a. Ensure the remote server is synchronized with its backup server.


c. At the command prompt, type (Z is a number):

bckbld -np -tag RDA -out ESVConfig Z.pnt

This creates a ESVConfigZ.pnt point build file with a list of the Experion group and trendconfiguration for DSA points, some of these may be TPS points.

d. Save the ESVConfigZ.pnt in a safe place. If for some reason you lose the group, trend, or historyconfiguration for your TPS points you can restore it with this file.

If you have problems during the TPS point move procedure, you should contact TAC. You willneed the ESVTConfig.pnt and ESVConfigZ.pnt files.

TIP: Not all points output are TPS points.

e. If the TIC101 and TIC102 points exist in the groups or trends on remote servers, remove them.

6. Move TIC101 to a different slot in the C300PM.

- 46 -

7. From the UCN Status Display, select the ENIM you want to checkpoint, and then select theLOAD/SAVE RESTORE target and then select the SAVE DATA target.

8. Using the TPN Data Entity Builder, delete the TIC102 point.

9. Delete any references to the TIC102 point in CM_2.

10. At this point in time, the checkpoint operation triggers an automatic import of C300PM points using theEHPM Point Import Utility.

RESULT: TIC101 point is moved from C300PM1 to C300PM2 in the ERDB and TIC102 point isdeleted from the ERDB.

11. Load and activate CM_1 on the Monitoring tree in the C300 CEE.

12. Load and activate CM_2 on the Monitoring tree in the ACE CEE.

13. To assign the TIC101 point to history, groups, or trends on the local server, configure the TIC101 pointin the history, groups, or trends on the local server.

5.2.7 Deleting/moving C300PM points having existing CDA peer-to-peer connections

When C300PM points are moved from one controller to another and CDA peer-to-peer connection to thesepoints exist in the ACE/C300 CEE, perform the following procedure to avoid any undesirable behavior.

Consider a scenario:

l CM_1 executes in C300 CEE; periodically reads TIC101.PV directly from C300PM1

l CM_2 executes in ACE CEE; periodically reads TIC102.PV directly from C300PM2

l TIC101 point needs to be moved from C300PM1 to C300PM2

l TIC102 point needs to be deleted

1. From the browser search report (“WhereUsed” Search), list down all the connections where theTIC101 and TIC102 points are referenced.

CM_1 and CM_2 are displayed.

2. Deactivate CM_1 and CM_2 and then delete them from the Monitoring tree of the C300 CEE and ACECEE respectively.

3. Make sure that there no active alarms on the Experion Alarm Summary for the TIC101 and TIC102points, in case of any alarms, clear them.

4. If the TIC101 point to be moved is assigned to history, groups, or trends on the local server, performthe following steps on the primary ESVT:

a. Ensure the ESVT is synchronized with its backup server.


c. At the command prompt, type:

bckbld -np -tag PSA -out ESVTConfig.pnt

This creates an ESVTConfig.pnt point build file with a list of the Experion group, trend, andhistory configuration for TPS points.

d. Save the ESVTConfig.pnt in a safe place. If for some reason you lose the group, trend, or historyconfiguration for your TPS points you can restore it with this file. TIP: Not all points output areTPS points.

e. If the TIC101 and TIC102 points exist in the history, groups, or trends on the local server,remove them.

- 47 -



5. If the TIC101 point to be moved is assigned to groups or trends on remote servers, perform thefollowing steps on each remote server (ESV or ESVT):

a. Ensure the remote server is synchronized with its backup server.


c. At the command prompt, type (Z is a number):

bckbld -np -tag RDA -out ESVConfig Z.pnt

This creates a ESVConfigZ.pnt point build file with a list of the Experion group and trendconfiguration for DSA points, some of these may be TPS points.

d. Save the ESVConfigZ.pnt in a safe place. If for some reason you lose the group, trend, or historyconfiguration for your TPS points you can restore it with this file.

If you have problems during the TPS point move procedure, you should contact TAC. You willneed the ESVTConfig.pnt and ESVConfigZ.pnt files.

TIP: Not all points output are TPS points.

e. If the TIC101 and TIC102 points exist in the groups or trends on remote servers, remove them.

6. Move the TIC101 point from C300PM1 to C300PM2.

7. Using the TPN Data Entity Builder, delete the TIC102 point.

8. Delete any references to the TIC102 point in CM_2.

9. From the UCN Status Display, select the ENIM you want to checkpoint, and then select theLOAD/SAVE RESTORE target and then select the SAVE DATA target.

10. At this point in time, if you have Experion R432.1 and TPN R686.1 installed, the checkpoint operationtriggers an automatic import of C300PM points using the EHPM Point Import Utility.

OR

If you have earlier releases of Experion and TPN installed, you must manually import the C300PMpoints using the EHPM Point Import utility from the current ENIM checkpoint.

RESULT: TIC101 point is moved from C300PM1 to C300PM2 in the ERDB and TIC102 point isdeleted from the ERDB.

11. Reenter the point name that is TIC101 and save the CM_1.

12. Load and activate CM_1 on the Monitoring tree in the C300 CEE.

13. Load and activate CM_2 on the Monitoring tree in the ACE CEE.

14. To assign the TIC101 point to history, groups, or trends on the local server, configure the TIC101 pointin the history, groups, or trends on the local server.

5.2.8 Establishing peer-to-peer communication between ACE/C300and C300PM

Peer-to-peer communications is a function in Control Builder whereby data can be shared among separatetagged blocks.

Peer to peer communication is supported between ACE/C300/UOC and C300PM. The ACE/C300communicate with the C300PM through the CDA.

Prerequisites


l Tree windows are open.

To establish peer-to-peer communications

- 48 -

1. Designate (determine) the definition (def) block in the subscribing CEE.

l The definition block defines the parameter value which would be useful for the reference block toacquire or possibly modify.

l See the Experion Control Builder Components Theory, Peer-to-Peer Functionality, Basic Peer-to-Peer Design Concepts and Implications for Control Builder Configuration for rules and tips forconfiguring the def block.

2. Designate (determine) the reference (ref) block in the subscriber CEE.

l The reference block receives parameter data from the definition block so long as the data type ofthe reference parameter matches the data type of the definition parameter.

l See the Experion Control Builder Components Theory, Peer-to-Peer Functionality Basic Peer-to-Peer Design Concepts and Implications for Control Builder Configuration for rules and tips forconfiguring the ref block.

3. Right-click on the subscribing CPM's icon symbol in the Project tab, then click Configure ModuleParameters. Set the update rate for the subscribing CEE to a desired value. Click OK to close theconfiguration form.

l The update rate is the rate at which the publishing CEE publishes its data to its subscriber. Theupdate rate is set for the whole of the CEE and hence all references are published at that rate.See the Experion Control Builder Components Theory, Peer-to-Peer Functionality, Basic Peer-to-Peer Design Concepts and Implications for Control Builder Configuration for the maximumnumber of parameter references allowed for each update rate.

4. Click on Insert > Parameter Connector. The chart containing the reference block must have thefocus. The pointer turns into a cross-hair.

5. Click on the desired input pin on the reference block.

6. Double-click at the required Parameter Connector location in the same CM.

TIP

Clicking in different places outside the block symbol results in the Parameter Connectorbeing placed in different locations. Try single-clicking to establish a path to a desiredlocation before double-clicking. Press the ESC key to cancel the operation and start over ifdesired.

7. Type in the full name of the desired definition block parameter, including Control Module. Block Name(Tag). Parameter and press the <Enter> key.

Alternate method: Click on the button with the dot leader icon (three dots) to access the PointSelection dialog. Use this dialog to find the desired point name and parameter and then click on thebutton titled Select to insert the specified parameter into the parameter connection field. Then click theClose button on the top right-hand corner of the Point Selection dialog to close the dialog and return tothe control drawing.

5.2.9 Control Builder operations on C300PM Controller

C300PM platform block is configured using Control Builder. After configuration, C300PM controller will bevisible in Control Builder tree view. You can select the C300PM controller and perform operations on it.

The following operations are supported on C300PM controller:

l Export: Exports the C300PM controller along with C300PM points.

l Import: Imports the C300PM controller.

l Load: Loads the C300PM controller.

l Load Server Points: Loads the C300PM controller into HSC server and builds a Server Point.

- 49 -



l Upload/Update To Project with Contents: Not visible on C300PM since all children blocks are hidden.

l Export with Contents: Not visible on C300PM since all children blocks are hidden.

l Delete: Deleting C300PM controller from Project-Assignment tab deletes all the associated blocks andalso C300PM points (if any) in ERDB, while deleting C300PM controller from the Monitoring-Assignment tab deletes all the associated blocks and also C300PM points (if any) in ERDB and SR.

l Delete Server Points: Deletes the C300PM controller from server only if C300PM points are notpresent.

l List views: Displays the C300PM controller.

l Rename: Allows you to rename the C300PM controller.

l QVCS operations: Allows you to apply QVCS operations on the C300PM controller. Checkin/Checkoutthe C300PM controller to perform operations on it.

l Upload/Update To Project: Upload option uploads data from the controller/server to monitoringdatabase. Update To Project option updates monitoring database data to Project-Assignment tab.

l License checks: License checks are applicable for C300PM Controller. If the license count exceedsthe limit specified or if there is no license then you cannot load C300PM Controllers.

l ERDB Backup/Restore: You can take a backup of ERDB. If C300PM points are not included in theERDB backup process, then C300PM points must be imported manually again after restore.

l Migrate: This option is used for performing On-Process Migration (OPM). This option invokes themigration wizard for C300PM.

l Checkpoint: Checkpoint operation is applicable for C300PM. Only C300PM and CEE block can becheck pointed. EE blocks and C300PM Points are not included in checkpoint file. All checkpointoperations like Save, Restore, Rebuild are supported.

When checkpoint file for C300PM is restored in Control Builder, C300PM points are not restored.Checkpoint restore will only restore controller parameters which can be check pointed, but C300PMPoints will still be present in the monitoring database. Hence no change is required after checkpointrestore.

The following operations are not supported on C300PM controller (these menu options are disabled onC300PM controller):

l Bulk Build: Does not list C300PM controller.

l Bulk Edit: C300PM points are not displayed in Bulk Edit dialog.

l Activate/Inactivate: Not applicable since the C300PM controller stays active once it is loaded.

l Load with Contents: Not supported.

l IdentifyERDB/ControllerInconsistencies: Not applicable.

l Freeze and SwitchOver: Disabled for C300PM. Supported with Experion R520.2.

l PrintAllTreeProject/Monitor TreeCharts: This menu option is available on the File > Print Toolbar andis not with respect to any block types. It tries to print all SCM and CM charts. Hence this menu optioncan be kept as enabled .

Enable Auto Detection functionality is disabled for AO16 under C300PM.

- 50 -

Loading server points for C300PM controller

Prerequisites




l TPS File Transfer Service should be configured and running.

l Native Window should be on Engineering Main Menu.

l Native Window Access Lock should be ENGR.

l GUS Server should be up and running.

l LCN configuration path should be configured.

l In the TPS Interface of the Experion Station, ensure that the Experion assets are mapped tocorresponding TPS units.

l The TPS Data and Notification Connections LEDs should be GREEN.

- 51 -



To load server points for C300PM controller

Right-click on the C300PM controller and then click Load .

Result: The C300PM Controller is loaded to Monitoring Database.

To load points for C300PM controller

Right-click on the C300PM controller and then click Load Server Points.

C300PM controller is now loaded to the server.

Deleting a C300PM block

NOTE

l Deleting the C300PM block terminates any currently executing peer-to-peer communicationbetween the C300PM Controller and the ACE/C300 Controller.

l Deleting a C300PM block from the monitoring side deletes all the associated blocks andalso C300PM points if any, in the monitoring side of ERDB and SR while the associatedblocks and C300PM points (if any) remain unaffected in the project side of ERDB. C300PMpoints are loaded on the TPS system, and hence even if you delete the C300PM points,they are removed from the Monitoring side and not from the actual C300PM Controller.Generate a ‘Where Used’ search report in browser to determine the C300PM points whichhave been configured for peer-to-peer communication.

l Delete option for C300PM block is enabled irrespective of controller state (RUN or IDLEstate). Force Delete option is available for the C300PM, if the controller is in red state.

NOTE

During configuration of history support for C300PM points, if the C300PM Data Access parametervalue is set to Peer to Peer and ExpServer, after deleting the C300PM block from the Monitoringtree, the standard history access path are routed through the TPS path. If the C300PM Data Accessparameter value is set to Peer to Peer Only, then no change is done on the Experion Server.

To delete a C300PM block

1. Right-click the C300PM block and then click Delete.

Delete Selected object(s) dialog box appears.

2. Click Delete Selected object(s).

Delete operation progress bar shows the progress of deletion.

Results

C300PM block is now removed from Control Builder tree view after deletion.

- 52 -

Deleting server points for C300PM controller

Prerequisites




l TPS File Transfer Service should be configured and running.

l Native Window should be on Engineering Main Menu.

l Native Window Access Lock should be ENGR.

l GUS Server should be up and running.

l LCN configuration path should be configured.

l In the TPS Interface of the Experion Station, ensure that the Experion assets are mapped tocorresponding TPS units.

l The TPS Data and Notification Connections LEDs should be GREEN.

To delete soft points for C300PM controller

Right-click on the soft point in the Monitoring Tree of Controller and then click Delete Points.

NOTE

If there are loaded C300PM points assigned to C300PM controller then an error message isdisplayed when you click on Delete Server Points.

If there are no C300PM Points present in Monitoring database, then Delete Server Points deletesthe C300PM controller point that is built on server.

NOTE

When C300PM points, with valid PTEXECST parameter, are deleted from Native Window, the pointstatus in Control Builder's Monitoring Tree is Blue instead of Red. Therefore, the 'Force Delete'option is not listed as a context menu item and only 'Delete' option is available. The 'Delete' option isnot applicable as the points are not available in TPN.

Hence, these points remain in Monitoring Tree of ERDB.

For example: Regulatory points, DIGCOMP points.

Use Control Builder for deleting points if engineering is done from Control Builder.

Exporting C300PM controller

Export on C300PM would actually perform export with contents. C300PM Points will also be exportedalong with the C300PM Controller when you choose Export menu option.

To export a C300PM controller

- 53 -



1. Select the C300PM controller and then click on Export.

The selected C300PM controller appears in the list of objects that can be exported.

2. Click Export.

The Export Data dialog box shows the progress of export.

Importing C300PM controller

1. Select the C300PM controller and then click on Import.

The selected C300PM controller appears in the list of objects that can be imported.

2. Click View Connection Details to ensure that the import set has all the C300PM points that areconfigured for peer to peer communication.

3. Click Import.

Performing ERDB backup or restore

To take a backup of ERDB

- 54 -

1. From the Configuration Studio home page, go to SystemName .> Servers>LSTF-ESVT-E1>ControlStrategy. Under Process Control Strategies, click on Administer the control strategy database.

ERDB Admin Tasks page appears in Windows explorer view.

2. Click Backup Database.

3. Browse to the folder where you want to store the backup set and then click Select.

- 55 -



4. Click OK when asked for confirmation.

- 56 -

Viewing Native Window parameters

NOTE

The parameters HPM_HWREV, HPM_FWREV, and HPM_IOL_HWREV are not applicable forC300PM and display the value '0'.

The following parameters can be viewed on both Native Window as well as Control Builder's platformblock. The parameters in the Native Window column are also available on Control Builder as described inthe Control Builder platform block column.

Native WindowControl Builder platformblock

COMMUNICATION H/W or COMM/CTRLCARD H/W

Hardware Version

COMMUNICATION F/W Hardware Revision

COMMUNICATION VERS HPM Comm SoftwareVersion

COMMUNICATION REV HPM Comm SoftwareRevision

CONTROL VERS HPM Control SoftwareVersion

CONTROL REV HPM Control SoftwareRevision

SERIAL NUMBER Serial Number

ASIC REVISION Programmable LogicRevision

- 57 -


OPERATION

6.1 IDLE state after flashing firmware and rebuilding

The default start-up state for C300PM is IDLE. After flashing the firmware or after powering up theC300PM controller, C300PM comes up with IDLE state. This does not compromise any other functionality,except user experience.

6.2 To check C300PM operation from Experion DetailDisplays

The C300PM Node has an Experion Detail Display. Verify that the Detail Display has no failure and alarmindications.

Perform the following steps to view the Experion Detail Display.

Step Action

1 Open the Station application.

2 From the top menu bar, click View > System Status Display.

3 In the Location Pane, navigate to the node of interest.

To view the configured C300PM Nodes, click Controllers.

4 Double-click the node of interest in the Location Pane.

In the following example, the primary C300PM node C300PM_U7B5 (4) is selected.

- 58 -

CHAPTER

6

Step Action

RESULT: The Detail Display appears. Example Details Displays follow Step 6.

5 Verify that the Local FTE Status LEDs are green, and that there are no alarmspresent.

REFERENCE: For details on the LED and alarm indications, see the section “ToCheck C300PM Node Operation Using the Detail Display Faceplate”

- 59 -

Chapter 6 - Operation


C300PM Main Tab

C300PM EUCN Tab

- 60 -

C300PM Soft Failures Tab

C300PM Point Mix Tab

- 61 -



C300PM Config Details Tab

To Check C300PM Node Operation Using the Detail Display Faceplate

The following table describes the Faceplate appearing on the Detail Display of the C300PM Node.

- 62 -

Item Description

1 Tag Name of primary block

Controller

Device/Node Type

2 Status of C300PM Node – SeeNODESTATESTR parameter in theControl Builder Parameter Reference andthe Control Building User’s Guide.

3 Local FTE Status

Off - Not in error.

FTE: The FTE Linkintegrity is OK, withtransmit activity onlink.

Error Condition

UncertainCondition

WarningCondition

4 Indicates current CPU free %. You canconfigure alarm limits in the Main tab ofControl Builder block.

5Alarm The word “Alarm”

appears if an activealarm is in AlarmSummary. To view thealarm, click the alarmicon on the ExperionStation status bar.

Click toacknowledge/silencealarm(s).

Alarm status icon.Changes appearanceto indicate urgent,unacknowledged,cleared, and so forth.

- 63 -



Item Description

TIP: Hover cursor overicon to view tooltip. Fordescriptions of alarmicons, see “Calling upthe Alarm Summary” inExperion Operator’sGuide.

6 Redundancy: PRIMARY or SECONDARY(blank if non-redundant). SeeRDNROLESTATE in Control BuilderParameter Reference.

7 FTE LEDs: A red LED indicates failure.See “Troubleshooting Network Issues” inFault Tolerant Ethernet Overview andImplementation Guide.

6.3 To check TPN and FTE Status Display

FTE Status Display

FTE Status Display is used to monitor Fault Tolerant Ethernet health. For more information, see the section"Use the FTE Status Display" in the Engineer's Reference Manual.

TPN Detail Display

Experion provides a set of native HMIWeb displays that access an extended set of standard operationalparameters associated with a given TPN point. The displays provide access to TPN operationalparameters.

With Experion R410, you can view and control all the parameters, using Experion TPN point detail displaysas you can with the Native Window point detail displays. While the Native Window display provides the datain a series of separate pages, Experion station display provides the same data as a set of tabbed displays.The tabbed displays framework of Experion Station window incorporates all the components that aresupported in the Native Window. The following figure is an example of

- 64 -

To check C300PM operation from Native Window

The Native Window is updated to reflect C300PM as a node type. The other functions for C300PM nodework the same as an EHPM node

For more details about operation from Native Window, see Process Operations Manual SW11-601.

6.4 Interpreting C300PM icons in Control Builder

Adding a C300PM platform block to the Control Builder Project side, results in the appearance of an iconthat represents a redundant pair of C300PM Nodes.

After the platform block in Control Builder has been loaded, the icons appear in the Control BuilderMonitoring side. The appearance of the icons in the Monitoring side is determined by the ICONSTATEparameter, which is derived from the following parameters:

l C300PM node status (NODESTATESTR)

l Redundancy Role parameter (RDNROLESTATE)

l Redundancy Synchronization State parameter (RDNSYNCSTATE)

l Soft Failure parameter (SOFTFAIL)

When a C300PM platform block is defined, two icons appear as follows:

l primary - lower-left icon

l secondary - upper-right icon

The appearance of either icon on top in a redundant pair indicates the active C300PM Node status.

C300PM platform block icon indications in Control Builder

The following table shows the icon appearance in Control Builder based on the current C300PM platformblock state.

- 65 -



Icon Represents . . . C300 Controller(C300STATE)

Project Tab

(gray)

C300PM Controller configured for non-redundant operation. N/A

(gray,simulation)

C300PM Controller configured for non-redundant operation.Simulation mode enabled.

N/A

(gray & white)

C300PM Primary configured for redundant operation. N/A

(white & gray)

C300PM Secondary configured for redundant operation. N/A

Monitor Tab

(red)

C300PM is non-redundant and not communicating No Communication(Offnet)

(red,simulation)

C300PM is non-redundant. Simulation mode enabled. No Communication(Offnet)

(red & white)

Primary C300PM is not communicating. No Communication(Offnet)

(white & red)

Secondary C300PM is not communicating. No Communication(Offnet)

C300PM is non-redundant No Database

Table 6.1 C300PM Controller icon indications in Control Builder

- 66 -


(yellow)

(yellow,simulation)

C300PM is non-redundant. Simulation mode enabled. No Database

(yellow &yellow)

Primary C300PM is not synchronized and partner C300PM isvisible

No Database

(yellow &shadow)

Primary C300PM is not synchronized and partner C300PM isabsent or incompatible

No Database

(blue)

C300PM is non-redundant. Idle

(blue,simulation)

C300PM is non-redundant. Simulation mode enabled. Idle

(blue & white)

Primary C300PM is synchronized Idle

(blue & white,pause)

Primary C300PM, standby synchronization Idle

(blue & yellow)

Primary C300PM is not synchronized and partner C300PM isvisible.

Idle

Primary C300PM is not synchronized and partner C300PM isabsent or incompatible.

Idle

- 67 -




(blue &shadow)

(green)

C300PM is non-redundant Run or OK

(green,simulation)

C300PM is non-redundant. Simulation mode enabled. Run or OK

(green & white)

Primary C300PM is synchronized Run or OK

(green & white,pause)

Primary C300PM, standby synchronization Run or OK

(green &yellow)


Run or OK

(green &shadow)


Run or OK

(white & green)

Secondary C300PM is synchronized Backup

(white & green,pause)

Secondary C300PM, standby synchronization Backup

Secondary C300PM is not synchronized and partnerC300PM is visible

Backup

- 68 -


(yellow &yellow)

(shadow &yellow)

Secondary C300PM is not synchronized and partnerC300PM is absent or incompatible.

Backup

(blue)

C300PM is non-redundant Idle Soft Fail

(blue,simulation)

C300PM is non-redundant. Simulation mode enabled. Idle Soft Fail

(blue & white)

Primary C300PM is synchronized Idle Soft Fail

(blue & white,pause)

Primary C300PM, standby synchronization Idle Soft Fail

(blue & yellow)


Idle Soft Fail

(blue &shadow)


Idle Soft Fail

(green)

C300PM is non-redundant Run Soft Fail or OKSoft Fail

C300PM is non-redundant. Simulation mode enabled. Run Soft Fail or OKSoft Fail

- 69 -




(green,simulation)

(green & white)

Primary C300PM is synchronized Run Soft Fail or OKSoft Fail

(green & white,pause)

Primary C300PM, standby synchronization Run Soft Fail or OKSoft Fail

(green &yellow)


Run Soft Fail or OKSoft Fail

(green &shadow)


Run Soft Fail or OKSoft Fail

(white & green)

Secondary C300PM is synchronized Backup Soft Fail

(white & green,pause)

Secondary C300PM, standby synchronization Backup Soft Fail

(yellow &yellow)

Secondary C300PM is not synchronized and partnerC300PM is visible partner present.

Backup Soft Fail

(shadow &yellow)

Secondary C300PM is not synchronized and partnerC300PM is absent or incompatible

Backup Soft Fail

- 70 -

6.5 Redundancy operation

Synchronization States

The RDNSYNCSTATE parameter indicates the synchronization state of a redundant C300PM.

Given a redundant pair, synchronization is the act of transferring configuration and execution data from theprimary to the secondary, so that the secondary has the same information as the primary when it is neededto transition into the primary role.

Synchronization is only possible for a compatible redundant pair. When a compatible partner is found, theC300PM transitions from the No Partner state to the Partner Visible state.

During the first time transfer of synchronization data (initial-sync), after the platform blocks in ControlBuilder are loaded, the redundant C300PMs are in the Sync in Progress state. After initial-sync completes,the redundant pair enters the Synchronization Maintenance state during which synchronization ismaintained (data that changes is synchronized to the secondary), and the secondary is a viablereplacement for the primary.

Synchronization states of Redundant C300PM Nodes:

Redundancy Failure Conditions and Failover Indications

When a C300PM Node failover occurs, you get Experion system alarms, including Partner not visible onFTE network and Not Synchronized.

At any time, if you want to know if a failover occurred, you can also check for the following in theRedundancy tab on the Detail Display or the platform block in the Monitoring tree of Control Builder (shownhere).

l Last Loss of Sync Time indicates time of last failover.

l The No Partner status is present in Redundancy History.

In addition, you will observe that the primary has a different Device Index than it had prior to the failover.

NOTE

In the C300PM Redundancy tab, when we perform "Disable Synchronization", the backup C300PMreboots and comes back in unsynchronized Backup state, whereas, in Native Window, the backupC300PM shows as OFFNET. Once "Enable Synchronization" is performed, the backup C300PMsynchronizes with the primary C300PM and shows as Backup in Native Window.

- 71 -



6.6 Viewing event/alarm displays and journals

For viewing System alarm, click System tab, under System components, expand Controllers and selectthe C300PM controller.

For viewing Events summary, go to View > Events > Events Summary, under System components,expand Controllers and select the C300PM controller.

6.7 Managing C300PM node using Experion Dashboards

6.7.1 Introducing Experion Dashboards

The Dashboard pane in the Experion System Status display provides a graphical view of the status of yoursystem and network components in a way that allows relationships and criticality to be represented. TheLCN and ELCN nodes of your system are represented in one or more dashboard displays that areautomatically created and maintained by Experion.

In this discussion of Experion dashboard displays, the term LCN and ELCN nodes represents the following:

l LCN and UCN nodes connected with coaxial cable,

l ELCN nodes connected with the FTE network, and

l ELCN bridges.

To use an automatically generated dashboard across DSA, the dashboard can be copied to another FTEcluster; however, the dashboard components will not be updated across DSA. For example, a copieddashboard will display status information correctly, but the components included on the dashboard will notbe updated to reflect changes made in TPS. If you are migrating a system that has multiple ESVTs on asingle LCN, a review of the FTE community configuration needs to be done in consultation with HoneywellTechnical Assistance Center (TAC).

LCN and ELCN nodes can also be represented in custom designed dashboard displays that you create andmaintain. If you create a custom dashboard, it is important that you save the display file somewhere otherthan the AutoGeneratedDashboards folder and you should use a file name for the display that will not beconfused with the automatically created dashboards. Automatically created dashboards have a file namethat begins with auto.

REFERENCE: For more information about Experion dashboard displays, refer to following documents:

- 72 -

l “About dashboard displays”, HMIWeb Display Building Guide

l “Using the Dashboard pane on the System Status display”, Experion Operator’s Guide

l “Creating a dashboard display”, Experion HMIWeb Display Building Guide

l “Creating a dashboard hierarchy for the System Status display”, Experion Server and ClientConfiguration Guide

6.7.2 Dashboard Configuration Checklist

Configuring ES-T connection for dashboards

ESVTs cannot access system information directly from LCN and ELCN nodes, therefore, ESVTs must beconfigured to access LCN and ELCN node information via an ES-T. You can change which ES-T is used byan ESVT to receive the required information.

LCN and ELCN node information is used to create the automatically created dashboards. For moreinformation about these dashboards, see “Viewing LCN and ELCN node status in Experion usingautomatically created dashboards.” Additionally, LCN and ELCN node status information is also sourcedvia this connection. If the connection between an ESVT and the selected ES-T fails, the automaticallygenerated dashboards will not be updated with new or deleted LCN and ELCN nodes and node status willnot be available to Stations that depend on the ESVT for status information (for example, Flex stations).

To configure which ES-T connection is used to source automatic dashboard component and statusinformation

1. In Configuration Studio, click the ESVT node, then click System Interfaces, and then click ConfigureSystem Interfaces.

- 73 -



2. Under System Configuration, click System Hardware, click System Interfaces, select TPS from theSystem Interfaces dropdown.

3. On the Configuration tab, in the Configuration options section, select the ELCN ES-T node from thedropdown for the ES-T for Flex Station ELCN Dashboards.

This is the ES-T computer name that will be used to source the automatic dashboard component andstatus information to be shown on Flex Stations.

Configuring which display is called up by the TPS System and ConsoleStatus indicators

The TPS System and Console Status indicators are found in the Station Status Bar.

REFERENCE: For more information, see “The Station Status Bar” in the Experion Operator’s Guide.

- 74 -

To configure which display is called up by the TPS System and Console Status indicators

1. In Station, choose Configure > System Hardware > System Interfaces.

RESULT: The System Interfaces configuration display opens.

2. Click the TPS interface.

RESULT: The TPS Connection configuration display opens.

3. On the Configuration tab, select Call up LCN System Status Dashboard for TPS System Status andCall up Experion Console Detail display for TPS Console Status according to how you want the TPSSystem and Console Status indicators to function.

Download Network configuration information to Experion Server

1. In Configuration Studio, navigate to the Network branch, and select Define FTE communities.

- 75 -



2. Make sure all the ELCN nodes are selected as members of the FTE community, click Apply, and thenclick OK.

You can select the other Experion nodes which need to appear in System Tree view as well based on yourrequirements.

- 76 -

3. Click Load network configuration to servers. A warning message appears.

4. Click OK.

5. The node to be loaded to the server appears. Click OK.

The network loading on the selected server proceeds.

- 77 -



6. From the Station, go to the Location Pane, navigate to Network > Devices > FTE Community to seethe nodes loaded to the Experion server.

Configuring File Replication of the ELCN Dashboards on Flex Stations andConsole Extension Stations

1. In Configuration Studio, navigate to the System Name > Servers > ESVT >Advanced Options > FileReplication, and then click Configure file replication.

- 78 -

2. Click the “abstract” file replication entry from the list by clicking in the blank space under Name columnin front of the row 1.

- 79 -



3. On the configuration page for the “abstract” file replication, select the “Specific PC’s” check box andadd the network name of each Flex Station and Console Extension Station that requires the LCNStatus dashboard, click Save, and then click Replicate Now.

Configuring Operator access to ELCN Dashboards

1. In Configuration Studio, navigate to System Name > Servers > LSTF-ESVT-E5 > System Access, andthen click Configure operators and Windows group accounts.

2. Select an operator or group.

- 80 -

3. Click the Advanced tab and configure the Default dashboard setting.

4. Click the Assignment tab, click the Direct assignment option. The LCN System Status and UCN Statusdashboards are shown underneath System Alarm Groups. Give the operator or group access to therequired dashboards by assigning access to the local server.

5. Repeat for other operators and groups, if needed.

- 81 -



Configuring Flex Station access to ELCN Dashboards

1. In Configuration Studio, navigate to System Name > Servers > LSTF-ESVT-E5 > Stations andConsoles, and then click Configure flex stations.

2. Click a flex station. For example, STASTA1.

- 82 -

3. Click the General tab and select the dashboard from the Default dashboard drop down.

4. Click the Assignment tab, then select the Direct Assignment option. The LCN System Status and UCNStatus dashboards are shown underneath System Alarm Groups. Give the flex station access to therequired dashboards by assigning access to the local server.

- 83 -



5. Repeat for other flex stations, if needed.

Configuring Console Station access to ELCN Dashboards

1. In Configuration Studio, navigate to System Name > Servers > LSTF-ESVT-E5 > Stations andConsoles, then under Stations and Consoles, if all console stations belong to a console selectConfigure consoles, otherwise select Configure console stations.

2. Select a console or console station.

- 84 -

3. Click the Options tab, configure the Default dashboard setting.

4. Click the Assignment tab, select the Direct assignment option. The LCN System Status and UCNStatus dashboards are shown underneath System Alarm Groups. Give the console or console stationaccess to the required dashboards by assigning access to the local server.

5. Repeat for other consoles or console stations, if needed.

If you are invoking a dashboard over a ELCN network for the first time, note that it may take at leastthree seconds for each configured LCN/UCN/IOP point to be created in the Server and populatedunder Location pane tree view, therefore, it may take several minutes to create LCN/UCN dashboarddepending on the number of nodes configured in LCN/UCN network. Once all the configured pointsare created in the Server and populated under Location pane tree view, you can invoke the respectivedashboard on any ELCN ES-T in the ELCN network without any errors.

- 85 -



6.7.3 Configuring ES-T connection for dashboards

ESVTs cannot access system information directly from LCN and ELCN nodes, therefore, ESVTs must beconfigured to access LCN and ELCN node information via an ES-T. You can change which ES-T is used byan ESVT to receive the required information.

LCN and ELCN node information is used to create the automatically created dashboards. For moreinformation about these dashboards, see “Viewing LCN and ELCN node status in Experion usingautomatically created dashboards.” Additionally, LCN and ELCN node status information is also sourcedvia this connection. If the connection between an ESVT and the selected ES-T fails, the automaticallygenerated dashboards will not be updated with new or deleted LCN and ELCN nodes and node status willnot be available to Stations that depend on the ESVT for status information (for example, Flex stations).

To configure which ES-T connection is used to source automatic dashboardcomponent and status information



2. Click the TPS interface.RESULT: The TPS Connection configuration display opens.

3. On the Configuration tab, in the ES-T for Flex Station ELCN Dashboards list, click the ES-T computername that will be used to source the automatic dashboard component and status information to beshown on Flex Stations.

6.7.4 Configuring which display is called up by the TPS System andConsole Status indicators

The TPS System and Console Status indicators are found in the Station Status Bar.

REFERENCE: For more information, see “The Station Status Bar” in the Experion Operator’s Guide.

To configure which display is called up by the TPS System and ConsoleStatus indicators



2. Click the TPS interface.

RESULT: The TPS Connection configuration display opens.

3. On the Configuration tab, select Call up LCN System Status Dashboard for TPS System Status andCall up Experion Console Detail display for TPS Console Status according to how you want the TPSSystem and Console Status indicators to function.

- 86 -

6.7.5 Viewing C300PM node status in Experion using automaticallycreated dashboards

To view C300PM node status using automatically created dashboards

1. In the Experion System Status Summary display, open the Dashboard pane.

2. Click the dashboard list.

3. Select a dashboard that has been automatically generated.You can choose from LCN System Statusor UCNxx Status, where xx is the UCN process network number.

RESULT: The C300PM node included in the selected dashboard will be shown with status information in alayout similar to Native Window.

TIPTo maximize the space available to show C300PM node in the Dashboard pane, it is notrecommended to have the Location pane open at the same time as the Dashboard pane.

6.7.6 Operations on C300PM node from Experion

Operations can be performed on C300PM node from the Status pane of the Experion System Statusdisplay or the detail display of the node.

- 87 -



REFERENCE: For more information, refer to the following documents:

l “System Status Display Status pane reference”, see the Experion Operator’s Guide.

l For operations, see the TPS Operator’s Digest.

To perform an operation on a C300PM node from Experion

1. In the Experion System Status Summary display, open the dashboard that includes the requiredcomponent.

2. You can perform operations from the Status Pane or the detail display associated with a component:

For these operations Do this

LOAD (NET)

SAVE (NET)

DUMP (NET)

SHUTDOWN

RESTORE

1. On the dashboard, select thecomponent.

2. Open the Status Pane.

Other operations. For example, Load, Save, orDump to specific locations.

1. On the dashboard, double-click the component.

The detail display of thecomponent will appear.

2. On the detail display, click theCommands tab.

- 88 -

3. Click the required operation and follow the prompts. The status of the component may be updated onthe dashboard if relevant.

REFERENCE: For more information, see “Components of the System Status display” in the ExperionOperator’s Guide.

6.7.7 Calling up Native Window displays from Experion

If your system has been configured accordingly, the Native Window System Status display will be called upinstead of the Experion System Status display if you click S in the Station Status Bar.

Similarly, the Native Window Console Status display will be called up instead of the Experion Consoledetail display if you click C in the Station Status Bar.

REFERENCE: For more information, see section "Configuring which display is called up by the TPSSystem and Console Status indicators".

Alternatively, you can call up the relevant Native Window display from the Status pane associated with theselected component.

To call up Native Window from the Status pane

1. In the Dashboard pane or the Location pane of the Experion System Status display, select a C300PMnode.

2. Open the Status pane.

3. Click to open the relevant Native Window display for the selected component.

- 89 -


#_Configuring_which_display

#_Configuring_which_display

SERVICE

7.1 Flash firmware on an operational C300PM

7.1.1 To Update Firmware on an on-process Operational RedundantC300PM node

ATTENTION

Using Controller Migration Wizard(CMW) is only applicable once you have fully operationalredundant C300 controller pair. If you are migrating to C300PM, firmware manager should be used.

In Experion R511.5, use the Controller Migration Wizard (CMW) to update firmware on an on-processOperational Redundant C300PM node.

Step Action Done?

Checkpoint the node from Native Window

1 From the UCN Status Display, select the C300PM you want tocheckpoint, and then select the LOAD/SAVE RESTORE target andthen select the SAVE DATA target.

When the SAVE DATA target is selected, prompters request that themedia specifies where the checkpoint is to be stored. NET specifiesthe checkpoint should be stored in the HM that has the checkpointvolume for the physical node. $Fn specifies a removable media drive.If more than one disk is needed to complete the checkpoint,prompters ask you to mount a new media.

It is recommended that you disable automatic checkpointing forC300PM during the upgrade procedure. Do not request a demandcheckpoint when you are using DEB to load entities in the node.

When you do a demand checkpoint to removable media, use just-initialized disks only. If, for some reason, a demand checkpoint to aremovable media is not completed and that media contained an oldercheckpoint, some of the checkpoint data will be new and some may beold. This results in useless data.

Use demand checkpoints as backups for HM checkpoint data, ratherthan copies of HM checkpoint data. If more than one disk is needed,the data for one unit may be split between disks, and such datacannot be reloaded.

2 Go to either of the following displays to view the Device Index of theBackup C300PM.

- 90 -

CHAPTER

7

Step Action Done?

Experion Node Detail Display:

1. Open the Station application.

2. From the top menu bar, click View>System Status Display.

3. In the Location Pane, under “Controllers” category, navigate toand double-click on the secondary - <nodename>SEC.

Monitoring tree of platform block in Control Builder:

l In Control Builder, double-click on the secondary C300PM Nodeplatform block - <nodename>SEC

Ensure that the C300PM with the even-numbered Device Index is operatingas the Backup C300PM Node

Check the etherenet IP from the main tab

3 Check that the C300PM with the even-numbered Device Index is theBackup C300PM Node.

If the BACKUP has the even-numbered Device Index, go to step 4.

If the BACKUP does NOT have the even-numbered Device Index, thendo the following to cause a switchover to occur.

1. In the Native Window, navigate to the UCN Status display of therequired EUCN.

2. Choose the C300PM on the display grid.

3. Select RUN STATES target on the C300PM Detail Status display.

4. Choose the SWAP PRIMARY target and execute the commandby selecting the ENTER target.

RESULT: The old primary C300PM goes for a reboot and after thereboot it comes up as BACKUP. The C300PM with the even-numberedDevice Index is now the Backup C300PM Node.

4NOTE

Controller migration must be started from theControl Builder running on a server.

On redundant Experion servers, controllermigration must be started from Control Builderrunning on Server B.

Log on to Control Builder with Engineer (Engr) securitypermissions.

5 In Control Builder Monitoring tree, select the controller tobe migrated. Right-click on the controller and selectMigrate… to start the Experion PKS Controller MigrationWizard.

- 91 -

Chapter 7 - Service

Chapter 7 - Service

Step Action Done?

6 The following dialog box appears.

Click Yes.

7 Click Next on the Welcome dialog box.

8 Select the release for migration.

l To migrate your components to the latest major release availablefor this system, select Migrate Components to the LatestRelease. The current major release is EXP511.1-42.0.

l To migrate your components to the latest servicepack available for their current release, select MigrateComponents to the Latest Service Packand thenselect the service pack from the drop-down.

- 92 -

Step Action Done?

9 Click Next to continue. The Controller Migration Wizard collectsinformation about each component to determine if the component ismismatched and requires migration.

10 Select Perform On-process Migration of <controllername> check box, and then click Next.

11 The Verify Your Selection page appears. Review the list ofcomponents to be migrated on-process and click Next.

12 The following dialog box appears.

- 93 -

Chapter 7 - Service

Chapter 7 - Service

Step Action Done?

Click Yes.

The Controller Migration Wizard does the following.

l When a C300PM controller is selected for migration, the wizard updates the Checkpointof the controller before migration begins. Depending on the size of your database, thisoperation may take several minutes.

l Migrates selected components. The wizard updates all of the selected components. Thisoperation may take several minutes.

13 The Checkpoint Creation page appears. Click Next tocontinue.

14 The Migrating Selected Components page appears.Depending on the controller type that is being migrated,the Controller Migration Wizard indicates different stepsand status throughout.

For C300PM controller migrations, the following stepsand status are listed during the migration.

- 94 -

Step Action Done?

On-Process Migration Progress:

l Updating Secondary Module

l Performing Synchronization and Switchover

l Updating New Secondary Module

l Performing Synchronization

Click Continue when "Performing Synchronization andSwitchover" is completed.

15 Click Next when all the four steps are completed.

- 95 -

Chapter 7 - Service

Chapter 7 - Service

Step Action Done?

16 Once migration is complete, a summary of all thecompleted component updates is displayed. Click Finish.

Verify that firmware of C300PM has been updated

17 After updating firmware, use any of the following methods to verifythat the firmware of the C300PM has been updated to the expectedversion.

Firmware Manager: Shows the updated firmware version in green

- 96 -

Step Action Done?

color, indicating that it is the most recent version available.

Control Builder: In the Monitoring tree of the C300PM Node platformblock, the Main tab shows the Application Image Version.

RESULT: The firmware has been updated on both redundantC300PMs.

7.1.2 To Update Firmware on a Non-Redundant C300PM Node

In Experion R511.5, use the Firmware Manager to update firmware on a Non-Redundant C300PM Node.

Step ActionDone()

Checkpoint the node from Native Window

1 From the UCN Status Display, select the C300PM you want to checkpoint,and then select the LOAD/SAVE RESTORE target and then select the SAVEDATA target.

When the SAVE DATA target is selected, prompters request that the mediaspecifies where the checkpoint is to be stored. NET specifies thecheckpoint should be stored in the HM that has the checkpoint volume forthe physical node. $Fn specifies a removable media drive. If more than onedisk is needed to complete the checkpoint, prompters ask you to mount anew media.

It is recommended that you disable automatic checkpointing for theC300PM during the upgrade procedure. Do not request a demandcheckpoint when you are using the DEB to load entities in the node.

When you do a demand checkpoint to removable media, use just-initializeddisks only. If, for some reason, a demand checkpoint to a removable mediais not completed and that media contained an older checkpoint, some ofthe checkpoint data will be new and some may be old. This results inuseless data.

Use demand checkpoints as backups for HM checkpoint data, rather thancopies of HM checkpoint data. If more than one disk is needed, the data forone unit may be split between disks, and such data cannot be reloaded.

Shutdown the node from Native Window to place it in the IDLE state

2 Select the C300PM node, go to RUN STATES and make it IDLE.

l Choose the ENIM/ENB node in the display grid that the C300PM isresident on and then select the NTWK/HWY target to invoke the UCNStatus display.

l Choose the C300PM on the display grid and then select the RUNSTATES target on the C300PM Detail Status display.

l Choose the IDLE target and execute the command by selecting theENTER target.

RESULT: The C300PM enters the IDLE state.

- 97 -

Chapter 7 - Service

Chapter 7 - Service

Step ActionDone()

Shut down the C300PM to place it in the Ready state

3 From Control Builder, go to the Monitoring tree of C300PM Node platformblock.

4 Select Shutdown from the “Module command” drop down on the Main tab.A confirmation dialog is displayed. Click Yes to proceed with the Shutdown.

RESULT: The C300PM reboots and goes from IDLE to RDY (Ready) state,as can be seen on the physical C300PM's front panel display. The valueson the Detail Display show reverse video.

Native Window will display node state as OFFNET and C300PMhardware/Firmware Manager will display node state as RDY (Ready).

NOTEIf the C300PM is in the OK state or IDLE state when you attemptfirmware loading, the Firmware Manager tool will not flash thefirmware and will return an error indicating that the “Module isOn Control”.

Open the Firmware Manager tool and select node to be loaded

5 Open the Firmware Manager tool: click Start > Honeywell Experion Tools >All Honeywell Tools > Firmware Manager.

RESULT: The Firmware Manager tool queries the network and displays theFTE IP address and FTE Device Index of each C300PM.

The color of the Boot/Recovery and Application fields indicates whether ornot a more recent version of the firmware is available.

Version status of C300PM firmware images (Boot/Recovery andApplication):

green – version supported and latest

blue – version supported but not latest

red – version not supported

6Select the check box for the C300PM node.

7 Right-click on the C300PM node, and select Load Version.

- 98 -

Step ActionDone()

Choose the Load Version option if you want to select the firmware that isinstalled as part of the Experion software installation.

Choose the Load File option if you want to select the firmware from customlocations where you would have copied the firmware manually.

RESULT: The Select Firmware Version dialog box appears.

8 Click on the Firmware Version (for example, EXP511.1-42.510), and thenclick Show Personality.

RESULT: The available C300PM personalities are listed.

Actual version may be different, see the Experion PKS Software ChangeNotice associated with the release for information on the latest firmwareversion.

9 Click Load Firmware.

RESULT: The firmware loads and then the C300PM reboots to the IDLEstate. Note that the firmware upgrade process takes 3-5 minutes tocomplete.

Verify that firmware of C300PM has been updated

10 After updating firmware, use any of the following methods to verify that thefirmware of the C300PM has been updated to the expected version:

Physical C300PM front panel display: Select the DETAILS option to viewthe firmware version.

Firmware Manager: Shows the updated firmware version in green color,indicating that it is the most recent version available.

Control Builder: In the Monitoring tree of the C300PM Node platformblock, the Main tab shows the Application Image Version.

Restore the C300PM checkpoint

11 From the UCN Status Display, select the C300PM you want to checkpoint,and then select the LOAD/SAVE RESTORE target and then select theRESTORE DATA target and press ENTER target.

When the RESTORE DATA target is selected, prompters request to selectthe media where the checkpoint is stored. NET specifies the checkpoint is

- 99 -

Chapter 7 - Service

Chapter 7 - Service

Step ActionDone()

stored in the HM and $Fn specifies it is stored in removable media drive.

RESULT: The restoring of checkpoints to C300PM node is successful.

After flashing the firmware or after powering up the C300PMcontroller, C300PM comes up with IDLE state and does nothave it's personality loaded.

12 Select the RUN STATES target on the C300PM Detail Status display.Choose the STARTUP target and then the WARM STARTUP target andexecute the command by selecting the ENTER target.

RESULT: The C300PM node goes to OK state.

7.2 Troubleshooting tools

Troubleshooting Displays

The following displays can be used to troubleshoot failures or issues on the C300PM.

l Experion System Status Display

l Experion Node Detail Display/Faceplate

l Native Window Node Status Display on UCN

l Experion Alarm Summary and Event Summary - View > Events > Event Summary

l C300PM platform block on Control Block

C300PM Statistics

The Experion Detail Display shows statistics on the Main tab. The platform block in Control Builder has aStatistics tab. The statistical parameters are used for maintaining and monitoring data flow, networkstatistics, etc.

CPUFREE behavior with C300PM

As opposed to HPM/EHPM, all processes for C300PM run under the same processor and hence, theindividual processes cannot be distinguished. The existing CPUFREE parameters of HPM or EHPM aremodified as Core 0 and Core 1 processors.

For C300PM, the COMM and CTRL CPUFREE values come from Core 0 and Core 1 processors and theywill not match with the COMCFAVG, CTLCFAVG or $NMxxByy.$UCNLSB (35) and (36) of HPM/EHPMeven if the database configuration and the load on the controller is the same. Do not compare EHPMCOMM and CTRL CPUFREE values with C300PM Core 0 and Core 1 processor values.

Responding to Soft Failures

Soft failures do not cause a change in the state of the execution environment. There is no loss of control orloss of view when the C300PM Node detects a soft failure.

- 100 -

Experion reports C300PM Soft Failures on the following displays.

l Alarm Summary

l Monitoring tree of the Control Builder block, Soft Failures tab

l Detail Displays in Station

Any active soft fail would be indicated in red color.

Monitoring tree of Control Builder block - Soft Failures tab

Description of C300PM Node Soft Failures

The following table describes the C300PM Node Soft Failures.

Soft FailureScreen Text

Condition when indicator is illuminated

Factory DataError

True if the factory data in the device EEPROM is missingor invalid for the currently loaded firmware.

ROM ApplicationImage ChecksumFailure

Displays softfail condition.

WDT HardwareFailure

True if the device detects a failure with the hardwarewatchdog functionality. Note that this diagnostic detectsonly if the hardware watchdog is functioning.

WDT RefreshWarning

Displays the Watch Dog Timer Software Failure.

- 101 -

Chapter 7 - Service

Chapter 7 - Service



ROM Boot ImageChecksumFailure

Displays softfail condition.

Debug FlagEnabled

Displays Soft Fail condition, which indicates that theimage loaded to the module was built with one or moredebug flags asserted.

DiagnosticTraces Enabled

True if a Trace Flags parameter(s) is configured with anonzero value and the Diagnostic Trace Enabledparameter is enabled on the Traces tab of a C300PMNode platform block.

ThermometerFailure

True if the device hardware thermometer has failed.

Non-GenuineHardwareDetected

NVS/RetentionRestart MediaError

Critical TaskWatchdogWarning

True if one or more tasks fails to update the critical taskwatchdog within 5 seconds.

Partner NotVisible On FTE

True if the redundant partner is not visible on the FTEnetwork.

UncorrectableInternal RAMSweep Error

Displays status of detected RAM errors. True if anuncorrectable memory error has been detected.

CorrectedInternal RAMSweep Error

True if a correctable memory error has been detectedwithin the last 24 hours.

UncorrectableUser RAM SweepError

Displays status of detected errors in backup RAM.

Corrected UserRAM Sweep Error

Displays errors detected within backup RAM that arecorrected through a scrub operation.

- 102 -



Minimum HWRevision

True if device hardware fails to meet the minimumrecommended hardware revision for the currently loadedfirmware.

CurrentConditions

FTE NetworkError (see FTETab)

FTE Network has partially failed – there is an FTEconnection failure at the C300PM Node.True if device detected an FTE network error; for example,FTE cable failure.

Partner NotVisible On FTENetwork

Indicates redundant module partner is not visible on FTE.

EnclosureTemperatureCritical

True if the enclosure temperature exceeds the criticallimit.

CPU Free Critical

NVS Free Critical

Main RAM FreeCritical

WDT RefreshWarning

Critical TaskWatchdogWarning

- 103 -

Chapter 7 - Service

HPM/EHPM TO C300PM ON-PROCESS MIGRATION

For more information, see section "HPM/EHPM to C300PM on-process migration" in the HPM/EHPM toC300PM Upgrade Kit Instructions (51195766-044) Guide.

- 104 -

CHAPTER

8

NoticesTrademarksExperion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of Honeywell International, Inc.

Experion® and SafeBrowse® are registered trademarks of Honeywell International, Inc.

ControlEdge™ is a trademark of Honeywell International, Inc.

OneWireless™ is a trademark of Honeywell International, Inc.

Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is a business unit of HoneywellInternational, Inc.

Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of Honeywell International, Inc.

Other trademarksMicrosoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or othercountries.

Other brands or trademarks are trademarks of their respective owners.

Trademarks that appear in this document are used only to the benefit of the trademark owner, with no intention of trademarkinfringement.

Third-party licensesThis product may contain or be derived from materials, including software, of third parties. The third party materials may be subject tolicenses, notices, restrictions and obligations imposed by the licensor. The licenses, notices, restrictions and obligations, if any, maybe found in the materials accompanying the product, in the documents or files accompanying such third party materials, in a filenamed third_party_licenses on the media containing the product.

Documentation feedbackYou can find the most up-to-date documents on the Honeywell Process Solutions Support website at:http://www.honeywellprocess.com/support

If you have comments about Honeywell Process Solutions documentation, send your feedback to: [email protected]

Use this email address to provide feedback, or to report errors and omissions in the documentation. For immediate help with atechnical problem, contact HPS Technical Support through your local Customer Contact Center, or by raising a support request onthe Honeywell Process Solutions Support website.

How to report a security vulnerabilityFor the purpose of submission, a security vulnerability is defined as a software defect or weakness that can be exploited to reducethe operational or security capabilities of the software.

Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.

To report a potential security vulnerability against any Honeywell product, please follow the instructions at:

https://www.honeywell.com/en-us/product-security.

Support

http://www.honeywellprocess.com/support

mailto:[email protected]

https://www.honeywell.com/en-us/product-security

For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find your local CCC visit thewebsite, https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx.

Training classesHoneywell holds technical training classes that are taught by process control systems experts. For more information about theseclasses, contact your Honeywell representative, or see http://www.automationcollege.com.

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

http://www.automationcollege.com/

c300pm overview and implementation guide

Documents