Experion PKS

Release 530

Experion LCN Overview and

Implementation Guide
EPDOC-X478-en-530C
August 2024
 DISCLAIMER
This document contains Honeywell proprietary information.
Information contained herein is to be used solely for the
purpose submitted, and no part of this document or its
contents shall be reproduced, published, or disclosed to a third
party without the express permission of Honeywell
International Sàrl.
While this information is presented in good faith and believed
to be accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a purpose and makes no
express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special,
or consequential damages. The information and specifications
in this document are subject to change without notice.
Copyright 2024 - Honeywell International Sàrl

2
CONTENTS
Chapter 1 - About this guide 13
Scope 14
Revision history 14
Intended audience 15
Planning Considerations 15
Related documents 15

Chapter 2 - Introduction to Experion LCN 17

Experion LCN Overview 18
Experion LCN (ELCN) Engineering Operations 19
Honeywell UEA Hardware Overview 20
Overview of Experion LCN Platforms and Operating Systems 23
ELCN User Interface Nodes 24
LCN to Experion LCN Migration Example 25
Introduction to C300pm 26
Introduction to EHPMX 28

Chapter 3 - Experion LCN Deployment Considerations 30

FTE Community and UCN Considerations 31
LCN Addressing 32
LCN Node Limit on Coax Segment 33
LCN Cable Master 33
FTE Device Index and IP Addressing 34
Experion LCN Multicast IP Address 35
Experion TPS Node Configuration Requirements for ELCN 35
NCF Clock Source nodes must be ESVTs 35
ELCN HM (new Experion TPS node) 38

3
 To enable ELCN Interface for Experion TPS Nodes 39
Configuring Experion Base IP Address and (S)NTP IP Address 40
Time Synchronization Considerations 41
Virtualization Considerations 44
ELCN-EHB Considerations 45
ELCN- EHB Configuration supported 45
System Topologies supported 46
ELCN-ENIM Considerations 49
ELCN Appliance Nodes Considerations 50
ELCN-EPLCG Considerations 53
ELCN NG Consideration 54
AM Ride-Through functionality for ELCN Nodes 55
ELCN Bridge and ELCN Appliance Node Configuration Overview 55
ELCN Bridge Deployment Requirements 56
ELCN Bridge Minimum Requirements 56
ELCN Bridge Requirements for an Experion On-Process
Migration 57
ELCN Bridge Requirements for an Experion Off-Process
Migration 57
ELCN Bridge Requirements for a New Experion System 58
ELCN Node Automatic Dump 58
ELCN On-Demand Dump 58
Collecting dump for a UEA UVA node 61
Maximum number of ELCN ES-Ts per ELCN ESVT cluster 64
Security Considerations for Experion LCN 65
Experion LCN Migration Preparation Checklist 65
Prerequisites for ELCN UEA Appliance Node migration 66

Chapter 4 - UEA Hardware Overview and Initial Startup Procedures 89

4
 UEA Hardware Overview 90
UEA Site Planning Considerations 90
UEA Hardware Components and Cabling 91
UEA Processor Module 91
UEA Termination Assembly 91
Cables for ELCN Bridge/ENIM/AM/EHB Termination Assembly 93
Cables for ELCN EPLCG Termination Assembly 94
Overview of UEA Front Panel 96
Operating UEA Front Panel 98
UEA Front Panel Display Auto-Dim Feature 98
Initial Startup of UEA 99
Setting the UEA’s FTE Device Index 99
To Set the Device Index Using the UEA Front Panel 100
Loading UEA Firmware 103
Overview of UEA Firmware Loading 103
Considerations before Loading UEA Firmware 104
Node flashing procedure for a UEA node coming from the
factory with only the Boot Recovery image 109

Chapter 5 - Configuring ELCN Platform Blocks in Control Builder 111

Overview of Experion LCN Platform Blocks in Control Builder 112
Considerations When Loading ELCN Platform Blocks 113
To Create and Load the ELCN Platform Blocks 114
Control Builder ELCN Platform Block Parameter Descriptions 123
To Reconfigure an ELCN Appliance Node to be Redundant 131
Renaming ELCN AM Node Block 133

Chapter 6 - Commissioning the ELCN Bridge during Experion OPM 134

Overview of the ELCN Bridge Commissioning Server 135

5
 To Commission ELCN Bridge Using Commissioning Server 138

Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes 155
Migration from HM to ELCN-HM 156
To install the ELCN-HM Node 156
Pre-configuration tasks 163
To configure the ELCN-HM Node 165
Post installation tasks for System HM 172
Post installation tasks for Data HM 176
Migration from HM to ELCN-HM with Disk Drive Synchronization 178
To install the ELCN-HM Node 179
Pre-configuration tasks 179
To configure the ELCN-HM Node 188
Migration from Classic AM to Experion LCN AM 192
Prerequisites 193
Classic AM shutdown 193
Installing UEA 197
Installing FTE switches 198
Startup of UEA 198
Migrating from Non-Redundant Classic AM to ELCN-AM 198
Migrating from Redundant Classic AM to ELCN-AM 204
Backing out of ELCN-AM to Classic AM 211
Off-process Migration from Classic NIM to Experion LCN ENIM 213
Prerequisites 214
Off-process migration from Classic NIM to ELCN-ENIM 214
Backing out of ELCN-ENIM to Classic NIM 228
On-process Migration from Classic ENIM to Experion LCN ENIM 230
Prerequisites 231

6
 On-process migration from Classic Backup ENIM to ELCN-
ENIM 231
On-process migration from Classic Primary ENIM to ELCN-
ENIM 246
Backing out of ELCN-ENIM to Classic ENIM 256
Migration from Classic EPLCG to Experion LCN EPLCG 259
Prerequisites 260
Classic EPLCG shutdown 260
Installing UEA 263
Installing FTE switches 264
Startup of UEA 264
Migrating from Non-Redundant Classic EPLCG to ELCN-
EPLCG 265
Migrating from Redundant Classic EPLCG to ELCN-EPLCG 274
Backing out of ELCN-EPLCG to Classic EPLCG 283
Migration from Classic EHB to Experion LCN EHB 285
Prerequisites 285
On-process migration from Classic EHB to Experion LCN EHB 286
Migrating back to Classic EHB from ELCN-EHB 335
Migration from Classic NG to Experion LCN NG 340
Prerequisites 341
Classic NG shutdown 341
Installing UEA 343
Installing FTE switches 344
Installing PIN Switch 344
Startup of UEA 344
Migrating from Classic NG to Experion LCN NG 345
Migration from EAPP to ELCN-EAPP 351

7
 Pre-migration tasks 351
To install the ELCN- EAPP Node 352
To configure the ELCN- EAPP Nodes 357
Post installation tasks for Data EAPP 359
Migrate UEA ELCNNODE to UVA On Process and Vice Versa 359
Summary 359
Problem Description 360
Prerequisites: 360
Procedure: 360
Migrate UVA ELCNNODE to UEA On Process 364
Procedure: 364

Chapter 8 - Verifying Operation of Experion LCN 369

To Check ELCN Bridge Operation from Native Window 370
To Check ELCN Operation from Experion Detail Displays 370
To Check ELCN Bridge or ELCN Node Operation Using the
Detail Display Faceplate 376
Description of Shutdown Command 378
Description of Reset Command 379
Interpreting ELCN Icons in Control Builder 380
ELCN Bridge and ELCN Node icon indications in Control
Builder 381
Viewing ELCN/LCN Node Numbers 384
ELCN Bridge view of LCN/ELCN – Bridge Status tab of Detail
Display 384
Node Types shown on the Bridge Status tab 386
Duplicate LCN Node Numbers 391
Indication of duplicate LCN Node Numbers 391
To recover from duplicate LCN Node Numbers and ISOLATED 391

8
 Nodes
Redundancy Operation 392
Synchronization States 392
Redundancy Failure Conditions and Switch Over Indications 393
ELCN Bridge Redundancy Commands 393
Handling Dual-Fault Scenarios 395
ELCN UEA States and Transitions 395

Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards 396
Introducing Experion Dashboards 397
Dashboard Configuration Checklist 398
Configuring ES-T connection for dashboards 398
Configuring which display is called up by the TPS System and
Console Status indicators 400
Download Network configuration information to Experion
Server 400
Configuring File Replication of the ELCN Dashboards on Flex
Stations and Console Extension Stations 402
Configuring Operator access to ELCN Dashboards 404
Configuring Flex Station access to ELCN Dashboards 406
Configuring Console Station access to ELCN Dashboards 408
Configuring ES-T connection for dashboards 410
To configure which ES-T connection is used to source
automatic dashboard component and status information 411
Configuring which display is called up by the TPS System and
Console Status indicators 411
To configure which display is called up by the TPS System and
Console Status indicators 411
Viewing LCN and ELCN node status in Experion using
automatically created dashboards 412

9
 To view LCN and ELCN node status using automatically
created dashboards 412
Operations on LCN and ELCN nodes from Experion 412
To perform an operation on an LCN node or on an ELCN node
from Experion 413
Calling up Native Window displays from Experion 413
To call up Native Window from the Status pane 414
Configuring Experion options for managing LCN and ELCN nodes 414
Collecting On-Demand Dump 414
Reducing load caused by ELCN System Management Dashboard
on LCN data owners 415

Chapter 10 - Servicing and Troubleshooting Experion LCN 418

Replacing UEA Hardware 419
Troubleshooting Tools 419
Troubleshooting Displays 419
ELCN Statistics 419
Responding to Soft Failures 420
Description of ELCN Bridge and ELCN Node Soft Failures 421
To resolve node state FAIL or ISOL mismatch between displays 424
Responding to Control Builder Error 2123 425
Manually Rebooting UEA from Front Panel Display 426
To Manually Reboot UEA from Front Panel Display 427
Troubleshooting LCN Coax Cables on an ELCN Bridge 428
Updating Firmware on Operational UEAs 442
Overview of Firmware Update for Redundant ELCN Bridge 443
To Update Firmware on Operational Redundant ELCN Bridge 444
Overview of Firmware Update for Non-Redundant ELCN
Appliance Node 454

10
 Overview of Firmware Update for Redundant ELCN Appliance
Node 455
To Update Firmware on Operational Non-Redundant ELCN
Appliance Nodes 459
To Update Firmware on Operational Redundant ELCN
Appliance Nodes 463
Backward Migration to Prior Experion Release 477
Checking Microsoft Windows application event logs for errors 477
Capturing Failure Status for Honeywell Technical Assistance
Center Analysis 481
Prior to Diagnostic Dump of Experion TPS Node 483
Resolving data communication loss between ELCN-EPLCGs and
PLCs 483
Reducing load caused by ELCN System Management Dashboard
on LCN data owners 484
ELCN Bridge 484
Redundancy Behaviour 484
Effect of Cable operation 486

Chapter 11 - Decommission/Recommission Nodes 489

To Decommission LCN Nodes 490
Consideration for Small LCN Networks 493
Recommissioning an LCN Node 493
To Decommission the ELCN Bridge 494
To Initialize a UEA to the Factory (FACT) Image 496

Terms and definitions 499

Notices 503

11
12
CHAPTER

1 ABOUT THIS GUIDE

In this section:

Scope 14
Revision history 14
Intended audience 15
Planning Considerations 15
Related documents 15

13
Chapter 1 - About this guide

This document is intended to be used in conjunction with the

Experion LCN Planning, Installation, and Service Guide and
Experion LCN Hardware Upgrade Kit Instructions documents.
n The Planning, Installation, and Service Guide contains
detailed comprehensive planning and servicing information,
along with abbreviated installation and software/system
configuration information.
n The Upgrade Kit Instructions contains detailed
comprehensive ELCN hardware installation instructions.
n This document (Overview and Implementation Guide)
contains detailed comprehensive software/system
configuration information, including migration procedures
for various nodes.

Scope
This guide contains instructions and configuration
requirements for implementing the Experion LCN (ELCN) and
its components, including the ELCN Bridge and ELCN Nodes.
This guide includes detailed instructions for software
installation, configuration, operation, and troubleshooting, with
references to other documents as needed.

Revision history
Revision Date Description

A March 2024 Initial release of the

document.

B June 2024 Updated the following

chapters.
l ELCN Universal Virtual
Appliances
l Migrating HM, AM, NIM,
ENIM, EPLCG, and EHB to
ELCN nodes

C August 2024 Updated section Overview of

Firmware Update for
Redundant ELCN Appliance

14
 Chapter 1 - About this guide

Revision Date Description

Node.

Intended audience
This guide is primarily intended for engineers who integrate
LCN nodes into an Experion system and are responsible for
planning, installing, and administering the Honeywell Experion
LCN. It is therefore assumed that the user of this document
possesses a high degree of technical knowledge and a
familiarity with the LCN and Experion process control systems.

Planning Considerations
If a fresh UEA box from the inventory (factory) or a UEA box
that underwent a factory reset is flashed with the Experion
R530 firmware, it cannot be downgraded to previous Experion
releases using the on-process downgrade procedure. Such a
downgrade needs to be done using the off-process method.
However, a UEA box that was already installed in a previous
Experion release and that did not undergo a factory reset and
was migrated to Experion R530.1 can be downgraded to the
previous Experion release by following the on-process method.

Related documents
The following list identifies publications that may contain
information relevant to the information in this document.

Document Description

Experion LCN This guide provides information for planning, installing, and
Planning, servicing the UEA hardware for the ELCN Bridge and UEA
Installation, hardware-based ELCN Appliance Nodes, such as the ENIM and AM.
and Service
Guide

Experion Provides “best practices” advice for planning the installation of

Network Best Experion FTE networks, and connecting them into the plant
Practices information network.

15
Chapter 1 - About this guide

Document Description

Experion This document lists the supported DELL and HP hardware

Software platforms and guides you through the standard Experion software
Installation installation.
User’s Guide

Experion This guide describes the prerequisites, installation and use of the
Firmware Firmware Manager Tool. This tool is used to load firmware to a
Manager Tool Honeywell Universal Embedded Appliance (UEA), and to access
User’s Guide diagnostic information from it.

Experion PKS This guide describes procedures to perform basic tasks within the
Control Control Builder application, such as configuring hardware devices,
Building continuous control strategies, and sequential control strategies. The
User’s Guide guide also provides information about parameters associated with
configuration forms for Control Builder blocks.

Experion PKS This dictionary provides definitions of all Experion PKS parameters,
Control including range and default value.
Builder
Parameter
Reference

Guidelines for This document provides guidelines for replacing Hiway Boxes with
Replacing LCN-connected C300 emulations. The replacement of the legacy
Hiway Boxes Hiway boxes with the Experion C300 controllers can be achieved by
with LCN- creating emulations of the Hiway boxes and their algorithms to run
connected in Experion controllers.
C300
Emulations

16
CHAPTER

2 INTRODUCTION TO EXPERION LCN

In this section:

Experion LCN Overview 18

Experion LCN (ELCN) Engineering Operations 19
Honeywell UEA Hardware Overview 20
Overview of Experion LCN Platforms and Operating Systems 23
LCN to Experion LCN Migration Example 25
Introduction to C300pm 26
Introduction to EHPMX 28

17
Chapter 2 - Introduction to Experion LCN

The Experion LCN (ELCN) is the Fault Tolerant Ethernet (FTE)

version of the coaxial cable-based LCN, where LCN
communications are encapsulated on FTE. Each Experion LCN
node has FTE cabling, but no LCN cabling. There is no LCN
coaxial cable or LCNI devices. The Experion LCN is one
component of Honeywell’s strategy to preserve the user’s
investment in TDC 3000 (TDC, LCN, TPS, and TPN), while
providing the advantages of the Experion System, the Fault
Tolerant Ethernet network, and virtualization technology. All
existing user-created LCN data objects (such as checkpoints,
button configuration files, display objects, and CL/AM objects)
run on the Experion LCN platforms, without recompile, rebuild,
or reconstruction. For any given user-created data object
source file, there is only one compiled object file. A single
image of each TPN/LCN personality (node) can execute on
both the legacy platform and on the Experion LCN platform.

Experion LCN Overview

The ELCN Bridge is a key component in LCN to ELCN
migration. The ELCN Bridge connects the coax-based LCN to
the FTE-based ELCN, creating a single logical hybrid network.
The ELCN Bridge translates LCN messages into Ethernet
messages and vice versa, providing a means for legacy LCN
functions and the Experion version of those functions to
coexist and interoperate while you migrate the LCN nodes to
the ELCN counterpart.
The ELCN Bridge is NOT required if performing an off-process
migration of ALL LCN nodes to Experion LCN. The ELCN
Bridge IS required for the following migrations:
n If performing an on-process migration, the ELCN Bridge is
required. After establishing the ELCN Bridge, you migrate
each coax- based LCN node to its Experion LCN node
counterpart, one at a time.
n If one or more coaxial LCN nodes are to remain on the
coaxial LCN, then the ELCN Bridge is required for data
transfer to occur between the remaining coaxial LCN nodes
and the Experion LCN nodes – even if an off- process
migration had been performed.
The ELCN migration may occur incrementally over time. After
the last LCN node is migrated to ELCN (no nodes remain

18
 Chapter 2 - Introduction to Experion LCN

connected to the LCN coaxial network other than the ELCN

Bridge), the ELCN Bridge can be removed.
There are two general categories of ELCN Nodes: TPS Nodes
and Appliance Nodes. ELCN TPS Nodes are Experion nodes
deployed on a physical Microsoft Windows-based platform or
as a virtual machine. You migrate legacy LCN user interface
nodes (US, UxS, and GUS) to the ELCN as TPS Nodes. You also
deploy the ELCN History Module as a TPS node. You migrate
LCN data owner nodes (such as the ENIM, AM, EPLCG, and
EHB) as ELCN Appliance Nodes or ELCN Virtual Nodes. ELCN
Appliance Nodes use the Honeywell Universal Embedded
Appliance (UEA) hardware platform, as does the ELCN Bridge.

Experion LCN (ELCN) Engineering Operations

Beginning with Experion R511.3, the Experion Engineering
tools facilitate NIM point configuration. Experion Engineering
tools can be used to perform most of the Native Window Data
Entity Builder operations for NIM nodes. Unified Engineering
tools provides an environment having consistent user
experience in the unified Experion system.
Beginning with Experion R511.4, the Experion Engineering
tools facilitate Application Module (AM) point configuration
and support all the operations mentioned in this section as
applicable to AM.
Some of the engineering operations that can be performed are:
n Creating node Platform blocks
n EHPM node specific configuration
n Configuring IO modules
n Channel and Point building
n User programming (CL)
n Modification and deletion of the channels and points
ELCN Database Import Utility is added to the Experion
Engineering tool set for transferring LCN/UCN point
configuration data to Experion databases.
The unified Experion system leverages a common platform
framework which is supported on a common system

19
Chapter 2 - Introduction to Experion LCN

specification resulting in reduced deployment time and

complexity.
The following are the benefits of the unified Experion system:
n Provides a consistent user experience for all configuration
tasks.
n Ease of migration of database from UCN to the unified
Experion system.
n Increase in productivity in accomplishing configuration
tasks, as well as user programming.
n Reduces qualification efforts on different flavors of
engineering user station specifications.
n Reduces training needs on Native Window and Data Entity
Builder operations.
For more information on Unified Engineering tools, refer to the
ELCN Engineering Operations Guide.

Honeywell UEA Hardware Overview

The Universal Embedded Appliance (UEA) is a Honeywell
hardware platform for the following functions:
n Bridging capabilities for systems under migration from LCN
to Experion LCN (ELCN Bridge),
n Core TDC 3000 capabilities (ENIM, AM, EPLCG, and EHB),
(NG in a future releases),
n Interfaces to other systems (TCMI).
LCN nodes that currently exist in 5-Slot and Dual Node LCN
hardware modules (such as ENIM, AM, EPLCG, and EHB) can
be migrated to UEA hardware.
The following diagram illustrates the main components of the
UEA hardware.
Only the ELCN Bridge uses the LCN MAU D-connectors to
connect to the LCN coax cables. Non-bridge UEAs (such as
ENIM, AM, EPLCG, and EHB) do not use the LCN MAU
connectors and do not connect to the LCN coax, because their
LCN communications are encapsulated over FTE.

20
 Chapter 2 - Introduction to Experion LCN

The FTE ports (yellow A port and green B port) receive ELCN
communications. For ENIMs, the same FTE ports received both
ELCN and EUCN communications.
A redundant UEA has a redundancy cable between the partner
UEA boxes. The ELPCG UEA redundancy port is labeled “INER-
LINK”, instead of “REDUNDANCY” as the ELCN Bridge, ENIM
and AM UEA labeling has. The Bridge must be deployed as a
redundant pair of UEAs.
The UEA has a key locked front panel from which the user
assigns the FTE Device Index, which is required in order for the
UEA to obtain an FTE IP Address.
The following illustrations show ELCN UEA ports and cabling
specific to an ELCN Bridge, ENIM or AM node. Note that the
LCN MAUs are only used by ELCN Bridges.

The EPLCG UEA has two communication ports (PORT 1 and

PORT 2) and a “CONFIG JUMPERS” port. Ports 1 and 2 are
isolated RS-232 field ports used for serial communication with

21
Chapter 2 - Introduction to Experion LCN

PLCs and communication interfaces. The Config Jumpers port

is a non-isolated RS-232 port used for protocol selection. The
Inter-Link port is an RS-422 port used for redundancy
communication between ELCN EPLCGs.
The following illustrations show ELCN UEA ports and cabling
specific to an ELCN EPLCG node. Note that EPLCG cabling will
differ according to various customer system configurations.

Another view of the cabling attached to the Termination

Modules specific to the ELCN ELPCG is illustrated below:

22
 Chapter 2 - Introduction to Experion LCN

Overview of Experion LCN Platforms and

Operating Systems
You can deploy Experion LCN Nodes on the following
platforms, depending on the node type:
n Honeywell Universal Embedded Appliance (UEA) hardware
platform,
n x86 Intel processor based Virtual Machine, and
n COTS x86 Intel processor based hardware platform
supported by Microsoft Windows 10 or Windows Server
2016.
The following table summarizes the Experion LCN platforms
and Microsoft operating systems available in Experion R501.4
and TPN R688.1:

23
Chapter 2 - Introduction to Experion LCN

Physical Platform Virtual Platform

COTS PC/x86 UEA Virtual Machine/x86

(Dell or HP) (Essentials or
Premium)

ELCN Bridge X

ELCN TPS Nodes

ESVT Windows Server Windows Server 2016

2016

ES-T Windows 10 Windows Server 2016

orWindows Server
2016

ACE-T Windows Server Windows Server 2016

2016

E-APP Windows Server Windows Server 2016

2016

HM Windows Server Windows Server 2016

2016

ELCN Appliance and Virtual Nodes

ENIM X Linux

AM X Linux

EPLCG* X Linux*

EHB X Linux

* (Virtual EPLCG will not be available for a production

application, but only for Open VEP (Virtual Engineering
Platform). The virtual EPLCG may be used for configuration or
training purposes.)
The ELCN NG node will be available in a future release.

ELCN User Interface Nodes

Prior to the Experion LCN, TPS Nodes (Windows-based nodes
connected to the TPN/LCN) used LCNP boards (LCNP, LCNP4,
LCNP4M, LCNP4E and LCNP4E2) attached to an LCN MAU,

24
 Chapter 2 - Introduction to Experion LCN

that attached to the TPN/LCN coaxial cables. With ELCN, the

LCNP boards and LCN MAUs are no longer needed. As you
migrate each of these nodes to Experion LCN, you can deploy
them on either physical or virtual platforms. You can migrate
earlier types of user interface LCN nodes (US, GUS, UxS) to
Microsoft Windows-based hardware platforms, or you can
virtualize them.
To virtualize a node in a virtual machine (one node per VM),
remove the old hardware, and provide a thin client and
peripherals (video, keyboard, cursor control, removable media,
etc.), such as the Honeywell Orion Console, for user interface
functions.
To deploy a node on a Windows-based hardware platform,
ensure that the required Experion software release and the
required Microsoft Windows operating system support the
hardware platform that you select.
REFERENCE: To view the list of Honeywell-qualified platforms,
refer to the Experion PKS System Initialization media Software
Change Notice available in the HPS support website.

LCN to Experion LCN Migration Example

There are many scenarios for migration of LCN to Experion
LCN. The following diagram illustrates one example migration
scenario, described as follows:
1. A redundant pair of ELCN Bridge UEA boxes has been
installed and connected to the LCN and FTE networks.
2. The Microsoft Windows based nodes (ESVT, ES-T, ACE-T,
and E-APP) have been converted from LCNP4E-based
nodes to run as Virtual Machines on x86 servers running
Microsoft Windows operating system. These Virtual
Machines have been provided with thin clients. The
following diagram shows a Honeywell Orion Console used
for the control room thin clients.
3. The History Module has been virtualized to run as a Virtual
Machine on an x86 server platform.
4. The K4LCN-based ENIM has been converted to UEA
hardware. Note that the LCN NIM, AM, EPLCG, and EHB

25
Chapter 2 - Introduction to Experion LCN

with C300’s can also be migrated to equivalent ELCN UEA

nodes.
5. This example system has the ELCN Bridge receiving data
from the remaining LCN NIM, AM, EPLCG, and EHB for the
Experion System.

Introduction to C300pm
Beginning with Experion R520.2 TCU1 and TPN R690.2, an
existing UCN-based High-Performance Process Manager
(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
upgrade can be performed on-process.
The C300PM hardware consists of a Fault Tolerant Ethernet-
based C300PM Communication/Control module, Power
Backup Module, and FTE Interface module. The High-
Performance I/O Link Module is not required in C300PM
configuration as this functionality is integrated with the
C300PM Communication/Control module. No changes are
necessary to the physical I/O link cables.
C300PM is an ARM processor based common embedded
hardware platform that executes HPM node personality
software. The personality software is built into the C300PM
firmware and hence, there is no need to load a C300PM with
HPM personality software. The C300PM comes up in IDLE
state upon booting and you only need to restore the
checkpoint. The C300PMs do not require separate CF9
switches in the network as they have a built-in Control Firewall
functionality and will connect directly to the L2 switch.

26
 Chapter 2 - Introduction to Experion LCN

EUCN systems provide communication between Enhanced

Network Interface Module (ENIM) or Enhanced Network Bridge
(ENB) and C300PM using Fault Tolerant Ethernet (FTE).
The UCN status displays are updated for C300PM. Displays
that are important for fault scenarios or maintenance of the
EUCN FTE network and their elements are modified to reflect
the C300PM node.
The following diagram illustrates one example UCN and EUCN topology diagram
showing addition of C300PM.

27
Chapter 2 - Introduction to Experion LCN

Introduction to EHPMX
ATTENTION: The EHPMX uses the same hardware as
C300PM controller and based on the firmware flashed onto
the "Controller" hardware, it works as an EHPMX or
C300PM controller. In the rest of the document, where ever
EHPMX Communication/Control Card is mentioned, it
actually denotes a "Controller" hardware running EHPMX
firmware.

The EHPMX is the next version in the family of Enhanced High

Performance Process Manager (EHPM) controllers. The
EHPMX is based on common embedded hardware platform
and it can functionally replace the EHPM controller. It supports
a higher data access rate compared to EHPM (i.e. EHPMX
supports 1500 Parameters/second data access rate as
opposed to 1000 Parameters/sec with EHPM). The personality
software is built into the EHPMX firmware and hence, there is
no need to load a EHPMX with HPM personality software. The
EHPMX comes up in IDLE state upon booting and you only
need to restore the checkpoint. The EHPMX does not require
separate CF9 switches in the network as they have a built-in
Control Firewall functionality and will connect directly to the L2
switch.
The UCN status displays are updated for EHPMX. Displays that
are important for fault scenarios or maintenance of the EUCN
FTE network and their elements are modified to reflect the
EHPMX node.
An existing UCN-based High-Performance Process Manager
(HPM), or Fault Tolerant Ethernet (FTE)-based Enhanced High-
Performance Process Manager (EHPM) node can be upgraded
to an FTE-based EHPMX node. This upgrade can be performed
on-process.
EHPMX can be upgraded to C300PM Controller (that provides
the CEE capability) by following the on process upgrade
procedure.
The following diagram illustrates one example UCN and EUCN topology diagram
showing addition of EHPMX.

28
Chapter 2 - Introduction to Experion LCN

29
CHAPTER

3 EXPERION LCN DEPLOYMENT

CONSIDERATIONS

In this section:

FTE Community and UCN Considerations 31

LCN Addressing 32
LCN Cable Master 33
FTE Device Index and IP Addressing 34
Experion LCN Multicast IP Address 35
Experion TPS Node Configuration Requirements for ELCN 35
Virtualization Considerations 44
ELCN-EHB Considerations 45
ELCN-ENIM Considerations 49
ELCN Appliance Nodes Considerations 50
ELCN-EPLCG Considerations 53
ELCN NG Consideration 54
AM Ride-Through functionality for ELCN Nodes 55
ELCN Bridge and ELCN Appliance Node Configuration
Overview 55
ELCN Bridge Deployment Requirements 56
ELCN Node Automatic Dump 58
ELCN On-Demand Dump 58
Maximum number of ELCN ES-Ts per ELCN ESVT cluster 64
Security Considerations for Experion LCN 65
Experion LCN Migration Preparation Checklist 65

30
Chapter 3 - Experion LCN Deployment Considerations

This section describes the rules and considerations for

migrating to the Experion LCN. In this section, the term “one
ELCN” is analogous to “one LCN”; that is, a set of LCN nodes in
a single address space sharing a single Network Configuration
File (NCF).

ATTENTION: For TPS and Experion TPS Nodes (GUS, ES-T,

APP, EAPP, ACE-T ESVT**), prior to rebooting or shutting
down the node, you must go to another station’s native
window and perform a shutdown of that specific node
twice, so it goes to QUALIF and then to the FAIL state,
which is the correct state to stop the token passing and
prevent cable errors and/or node isolation from occurring.
If the PC is then rebooted or shut down, then perform one
final shut-down of the node from the Native Window to
bring the node to the OFF state on the LCN.
If multiple reboots are expected (i.e., during patching), it’s
recommended to change the LCN address to 0 via the
Board 0 configuration in the TPS Configuration Utility
(remembering to record the number before setting it to 0)
before you reboot. When done with activities that require
rebooting, you must change the LCN address back to the
original value and then reboot one final time.
** ESVT nodes go to the FAIL state on the first shut-down
command

FTE Community and UCN Considerations

In summary, the following FTE and UCN constraints apply to
the deployment of the Experion LCN:
n There can be only one FTE community per Experion LCN.
n If there are multiple ESVTs per LCN, in separate FTE
communities, they must be changed to be in one FTE
community prior to implementation of the ELCN Bridge.
n If there are two separate LCNs in the same FTE community
(for example, same switch), then you need to separate the
LCNs into two, separate FTE communities.

31
 Chapter 3 - Experion LCN Deployment Considerations

n An EUCN must belong to the same FTE community as the

Experion LCN to which it is connected.
n An Experion LCN may connect to multiple EUCNs.
n An EUCN cannot be shared between Experion LCNs.
n Honeywell FTE Best Practices must be followed.
REFERENCE: Refer to the document Experion Network Best
Practices.

LCN Addressing
The "address space" of both the Experion LCN network and all
physical LCN segments is comprised of a single common
address space spanning 1 to 96, reflecting a single duplicate-
free network census.
All nodes, whether LCN or Experion LCN, have a unique LCN
node number (address), so that the complete population is free
of duplications. A particular node number can only be assigned
to one node.
The Experion Control Builder assigns LCN addresses 97 and 98
to the ELCN Bridge redundant pair – you cannot change these
addresses. Control Builder assigns LCN address 97 to the
ELCN Bridge that has an odd-numbered FTE Device Index, and
98 to the redundant partner.
It is important to prevent duplicate LCN addresses from
occurring during the LCN to ELCN migration. The ELCN Bridge
detects duplicate addresses and alarms them, but it is
imperative to avoid the following types of scenarios:
n A user forgets to shut down the legacy LCN node prior to
bringing up the replacement ELCN node.
n When configuring the replacement ELCN Appliance Node
through the Control Builder, a user accidentally enters the
wrong LCN Node Number that is a duplicate of a running
LCN node connected through the ELCN Bridge.
n When configuring Experion TPS Nodes (ES-T, ESVT, ACE-T,
E-APP), the user accidentally enters the wrong LCN Node
Number in the LCNP Board0 configuration.

32
Chapter 3 - Experion LCN Deployment Considerations

When assigning or changing the LCN node number of any LCN

or ELCN node, it is imperative that the intended node number
is not already in use by another LCN or ELCN node.
If you cause a duplicate node number situation to occur, the
invalid duplicate node fails, and the existing running node may
become ISOLATED from some LCN and ELCN nodes.
To recover from this situation, power-off the node with the
invalid address, change its LCN node number to an unused
LCN address, power it back on, and reload the existing running
node that may have become ISOLATED. To load an ISOLATED
ELCN Node, first shut down the node (using System Status
display in Native Window) and then load the node.

LCN Node Limit on Coax Segment

ATTENTION: Do not exceed the 40 node limit on an LCN

coax segment at any point of the migration.

The maximum number of LCN nodes per coax segment is 40 -

39 nodes plus the LCN Extender (which counts as a node to
make it 40). The two ELCN Bridge modules count toward the 40
maximum LCN nodes on a single LCN coax segment. If the
ELCN Bridge will put your coax segment over the limit, then
you will have to shut down two US-type nodes (such as US,
GUS, or ES-T) on that segment until you migrate those two
nodes to the FTE-based Experion LCN.

NOTE: Experion LCN nodes do not count toward the coax

segment limit, as they are not connected to the coax LCN –
the limit applies only to a physical coax segment.The ELCN
Bridge is the only Experion LCN module that connects to
the coax LCN.The other Experion LCN modules connect
only to FTE.

LCN Cable Master

Starting with TPN R687.1, the LCN Cable Master node will
remain a US-type node (US, GUS, or ES-T) with the lowest LCN
node address, as long as the lowest numbered US-type node is
still a coax-based node.

33
 Chapter 3 - Experion LCN Deployment Considerations

After you migrate all US-type nodes to Experion LCN ES-Ts

(they no longer have a coax LCN connection), then the lowest
numbered coax-based LCN node, even if it is not a US type
node, becomes the LCN Cable Master node. During the
transition of migrating from LCN to Experion LCN, there always
will be at least one coax-connected LCN node to be the LCN
Cable Master.
After you migrate the last coax-connected LCN node to ELCN,
the LCN Cable Master function is no longer needed, because
all LCN communications are being handled by Fault-Tolerant
Ethernet (FTE).
REFERENCE: For the complete description of the LCN Cable
Master function, refer to the LCN Guidelines, Implementation,
Troubleshooting, and Service document, section “LCN Cable
Operation and Related Displays” – located in the TPN User
Assistance set. Note that when you see references to “LCNI
hardware” in the LCN guidelines document, remember that an
Experion LCN node (for example, ES-T and ESVT) has an
emulated LCNI, not LCNI hardware.)

FTE Device Index and IP Addressing

You must assign each node within an FTE community a unique
Device Index. The Device Index is the FTE node number.
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 ELCN Bridge
and ELCN Appliance Nodes. The node in the primary role uses
the lower (odd) IP address, and the node in the secondary role
uses the higher (even) IP address. This IP address follows the
primary when a switchover occurs.
Example:
Base IP address - 192.168.1.0Primary ELCN Bridge address -
192.168.1.23, where 23 is the user assigned physical Device
IndexSecondary ELCN Bridge address - 192.168.1.24
Example: If the Device Index is 257, then the IP Address of the
primary is 192.168.2.1

34
Chapter 3 - Experion LCN Deployment Considerations

The FTE IP address rules for the ELCN Bridge and any ELCN
Appliance Node are:
n the Experion Base IP address must be configured,
n the “Experion PKS BOOTP Server” Windows service must be
running on the primary ESVT, and
n the Device Index must be entered into the physical primary
and secondary UEAs.

Experion LCN Multicast IP Address

The ELCN Multicast IP Address must match on the ELCN
Bridge and all Experion LCN Nodes in order for them to
communicate.
Default ELCN Multicast IP Address: 234.129.239.100
Honeywell strongly recommends that you use the default ELCN
Multicast IP Address and not change it unless you are familiar
with the use of the IP Multicast Protocol.
If you change this value from the default, then you need to
change the value on the ELCN Bridge and all ELCN nodes.
After the ELCN Bridges and ELCN Nodes are running, any
changes to the ELCN Multicast IP Address should not be done
on-process.
Consult Honeywell or your personnel familiar with the use of
the IP Multicast Protocol and Honeywell Fault Tolerant
Ethernet to determine the repercussions of changing the ELCN
Multicast IP Address.

Experion TPS Node Configuration

Requirements for ELCN
NCF Clock Source nodes must be ESVTs
A prerequisite of installation or migration to Experion R501, is
making ESVT nodes the NCF Clock Sources:
n Configure the primary and secondary ESVT nodes in the
NCF as Clock Source Primary and Clock Source Secondary.

35
 Chapter 3 - Experion LCN Deployment Considerations

n For multiple ESVT pairs installed (up to five pairs per a

single LCN), choose the first pair to be migrated as the node
numbers for the NCF Clock Source Primary and Clock
Source Secondary.
n If you do not have ESVTs installed (that is, you do not have
Experion), then you must first configure ESVTs into the NCF.
After configuring the ESVTs into the NCF as LCN nodes,
then add them as NCF Clock Source Primary and Clock
Source Secondary.
You may use the LCN’s PERFMENU CLKSWTCH schematic to
switch the Clock Source Primary and Clock Source Secondary
nodes online without having to initially reboot any node in the
LCN network.

ATTENTION: When ELCN ESVTs are the Clock Source

nodes (Clock Primary and Clock Secondary), you cannot
switch the Clock Source to LCN node from the CLKSWTCH
schematic.

Using the TPN CLKSWTCH Schematic to Change the Time

Source
If you do not have ESVTs, ESVTs and ELCN Bridges need to be
installed first, then the ESVTs are made into ELCN ESVTs. Use
the CLKSWTCH schematic in the process of migrating to ELCN
ESVTs, then go back and change their NCF once fully migrated.
After the Backup ESVT is migrated to ELCN and Primary ESVT
is still a coaxial node, use the CLKSWTCH schematic to change
the Backup ESVT as the clock primary and Primary ESVT as the
secondary. The LCN nodes will continue to be Listeners.
The following is an example of steps taken to make the ESVTs
as the NCF Clock Source nodes using the CLKSWITCH
schematic. In this case, HM and NIM are the current
primary/secondary clock sources.
1. Make an Online NCF change to take the clock sources from
the HM and NIM to the two ESVTs (Primary and Backup
ESVT).

36
Chapter 3 - Experion LCN Deployment Considerations

2. On the “TPN Time Sync” tab of the “Board 0” settings of the

TPS Configuration Utility, check the Enable Experion/TPS to
TPN Time Sync checkbox and then reload the two ESVTs
(wait for the synch after migrating the Backup ESVT).
3. On the TPN CLOKSTAT schematic, verify that the ELCN-
ESVTs are running as the NCF Clock Source Primary and
Secondary.
4. From the Native Window, go to Displays > System > SYSTEM
MENU and click NCF STATUS target, and make sure that the
two ESVTs are in green color (Synched) and rest of the
nodes are in white color.
5. Check the LCNP Status Displays for both ESVTs at the
bottom (the Time Sync field) for the “TPS Time” and “TPN
Time” to be very close to each other (within 2 seconds).

6. If you intend to change TIME and DATE of the LCN, make

sure you reload the station from where you are attempting
to change the time. If you do not reload the station, then the
request for the change will not reach the new clock master.
REFERENCE: For details on the CLKSWTCH schematic, refer to
the Engineer’s Reference Manual, section “How to switch the

37
 Chapter 3 - Experion LCN Deployment Considerations

clock source nodes without rebooting any LCN Nodes” in the

TPN PDF Collection set.

ELCN HM (new Experion TPS node)

The ELCN History Module is a new type of Experion TPS Node,
deployed using RAID for the storage subsystem (either physical
or virtual).

Microsoft Patch Installation Considerations

With the migration from Classic HM to ELCN-HM, ELCN-HMs
are now Microsoft Windows-based nodes. This implies that
during Microsoft Windows patch installation, the ELCN-HMs
are periodically rebooted for the changes to take effect. Always
load and restart the ELCN-System HM followed by other ELCN
nodes in the network; failure to do so will result in other ELCN
nodes failing to load in the case of System HM unavailability
during the reboot process. You can use either of the following
approaches to install patches on ELCN nodes in the network.
Approach 1
1. Install patch on all ELCN nodes in the network (except
ELCN-System HM).
2. Restart and load all ELCN nodes (except ELCN-System HM).
3. Make sure that all ELCN nodes transition to OK or
OK/BACKUP state.
4. Install patch on the ELCN-System HM.
5. Restart and load the ELCN-System HM.
6. Make sure that the System HM transitions to OK state.

38
Chapter 3 - Experion LCN Deployment Considerations

OR
Approach 2
1. Install patch on all ELCN nodes in the network.
2. Restart and load the ELCN-System HM.
3. Make sure that the ELCN-System HM transitions to OK
state.
4. Load other ELCN nodes in the network.
5. Make sure that all ELCN nodes transition to OK or
OK/BACKUP state.

To enable ELCN Interface for Experion TPS Nodes

To enable the ELCN interface for an Experion TPS Node, you
must specify ELCN as the Auxiliary Network.
Make the following selections on the Experion Network
Selection screen in order for the node (physical or virtual) to
support Experion LCN:
n Network for communicating to/from Controllers (EPN -
Experion Process Network): FTE
n Network for communicating between Experion Nodes
(Server Client or Supervisory): FTE
n Auxiliary Network Selection: ELCN

39
 Chapter 3 - Experion LCN Deployment Considerations

Configuring Experion Base IP Address and (S)NTP IP

Address

Base IP Address
Embedded FTEnodes, such as the ELCN Bridge and ELCN
Appliance 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 the ELCN
Bridges and Experion LCN Nodes to be assigned an FTE IP
address, the Experion Base IP address must be configured and
the “Experion PKS BOOTP Server” Microsoft Windows service
must be running on the primary Experion Server.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. The preferred time source is
Network Time Protocol (NTP) operating on the primary and
secondary ESVTs (as a 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 primary time source.Secondary Server
– IP address of the “A” (intended primary) ESVT.

To configure Base IP Address and (S)NTP IP Address

The Experion System Preferences can be configured using
Control Builder. The configuration is saved in the Engineering
Repository Database (ERDB).Click Tools > System Preferences>
Embedded FTE.

40
Chapter 3 - Experion LCN Deployment Considerations

REFERENCE: For more information, see the following Experion

documents:- Supplementary Installation Tasks Guide, section
“Setting up time synchronization in a Windows domain
checklist”- Control Building User Guide, section “Control
Builder System Administration,” subsection “Setting System
Preferences”

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 time source should be used in the
Microsoft Windows domain setup.

41
 Chapter 3 - Experion LCN Deployment Considerations

An NTP Time Source should be configured. Typically, the ESVTs

are configured to be the NTP Time Source. A Precision Time
Protocol (PTP) time source is optional.

NOTE: A PTP time source is required if using EHPMs with

DISOE IOP.

REFERENCE: For more information refer to the section

“"Configuring Experion Base IP Address and (S)NTP IP Address"
on page 40”.

Experion TPS to TPN Time Sync functionality

On R501 and later, you must configure the main ESVTs to be
Clock Source Primary and Clock Source Secondary in the LCN
NCF.
When the ELCN Bridge is installed, the existing Experion/ TPS
to TPN Time Sync functionality operates unchanged, and is still
the method expected to be used for proper Experion/ TPS to
TPN Time Sync when ELCN Bridge is in place.
On Experion Systems that have ELCN Nodes and an ELCN
Bridge, the ELCN Nodes get their TPN time from the ESVT
Clock Source (by way of the “time sync frame” FTE message).
The TPN Time from the Clock Source Master ESVT is shown on
its LCNP Status Applet.
When the ESVT Clock Source Master starts broadcasting a
“time sync frame” every second on FTE, all other ELCN Nodes
hear the “time sync frame” and sync their time to the time
received in this message and change their CLK_MOD to a value
of “LISTENER”.
Upon hearing the ESVT Clock Source “time sync frame”, the
primary ELCN Bridge assumes the role of TPN Clock Source
Master Proxy. In that role, the ELCN Bridge tells its LCNI to go
into a master mode, and starts sending out standard LCN Time
Sync frames on its LCN coax cables for all LCN coax nodes to
hear. These LCN coax nodes then become “LISTENER” nodes.

42
Chapter 3 - Experion LCN Deployment Considerations

ATTENTION: Until the Clock Master node is migrated from

LCN to ELCN, any node that has completed migration from
LCN to ELCN will show Clock Mode (CLK_MOD) as Local.

Enable Experion TPS to TPN Time Sync

All of the operations of the “TPN Time Sync” tab of the “Board
0” settings of the TPS Configuration Utility apply to the ELCN.
On the primary and secondary ESVT, which are designated as
the LCN Clock Source nodes, check the checkbox to Enable
Experion /TPS to TPN Time Sync, as shown in the following
example, to synchronize “Experion TPS” time to “TPN/LCN”
time.Click Honeywell Experion Tools>All Honeywell
tools>System Management>TPS Configuration
Utility>Board0>TPN Time Sync.

REFERENCE: Refer to the Configuration Utility User’s Guide,

section “TPN Time Sync Page” – the definitions apply to ELCN
Time Sync functionality.

43
 Chapter 3 - Experion LCN Deployment Considerations

Enable Button to ‘Set TPN to TPS Time’

Install Signon Manager on the primary and secondary ESVTs to
make available the ‘Set TPN to TPS Time’ button in the LCNP
Status Applet, as shown in the following example; otherwise, it
will be grayed-out. Note that the “Demand Time Sync” and “Set
TPN to TPS Time” buttons are enabled for use only on the ESVT
that is designated as the Clock Source Master.

Virtualization Considerations
REFERENCE: If virtual Experion TPS Nodes are desired, refer to
the Experion PKS Virtualization Planning and Implementation
Guide (EPDOC-X147-en) for configuring and allocating
resources for Experion virtual machines.
If virtual ELCN Appliances are desired, see the Chapter “ELCN
Universal Virtual Appliances”.

44
Chapter 3 - Experion LCN Deployment Considerations

ELCN-EHB Considerations
ELCN- EHB Configuration supported

HG addressing
Each HG requires one Data Hiway address ("box number" on
the configuration form). An HG pair requires two consecutive
addresses. The primary HG is assigned an even address and
the secondary is assigned an odd address, for example, 02 and
03. Each HG retains its assigned address regardless of which
one has control.

Simple gateway configuration

ELCN-EHB supports only simple gateway configuration for
migration from Classic EHB to ELCN-EHB.
In a simple gateway configuration, EHB provides an interface
for connectivity between the LCN and the emulations of Hiway
boxes in the Experion network. The emulations of Hiway boxes,
which are functionally equivalent to the physical Hiway boxes,
exist in the C300 controllers on the Experion network. The EHB
and the C300 controllers are connected through FTE.
Therefore, EHB functions as a one-to-one gateway that
connects the LCN and the FTE network.
However, in a simple gateway configuration, EHB does not
facilitate connectivity to the Data Hiway.
Consider the following illustration, in which the box CB1 has
been migrated to C300. Therefore, the emulations of the Hiway
box, CB1, exist in C300. The LCN nodes can now read data of
the migrated CB1 in the required format from C300 through
EHB. EHB provides the required interface for the LCN nodes to
connect to the emulated Hiway box in the C300 controller,
through the FTE.

NOTE: The following illustration is also applicable to EC

and PIU boxes.

45
 Chapter 3 - Experion LCN Deployment Considerations

NOTE: In a Simple Gateway configuration, you cannot

perform a hot cutover. Migration from Hiway controller to
C300 emulations must be done offline.

System Topologies supported

NOTE: EHB does not support the topologies which include

RemoteHG. EHB is only designed to support one LCN to
one FTE and two LCN to two FTE system topologies.

1. Topology 1: One LCN to one FTE

The following diagram displays a topology of a typical HG-
based LCN network. This network includes one cluster.

46
Chapter 3 - Experion LCN Deployment Considerations

This network in its pure LCN form includes three HGs namely
HG1, HG2, and HG3, of which HG1 and HG2 are on the same
physical Hiway with a relationship of “ThisHG” and “AddedHG.”
This LCN network also includes many HPMs connected
through NIMs.
After migration/cut-over, the HG1 and HG2 are moved to EHB1
and EHB2 with the same
relationship along with emulated boxes. One of the NIMs
(shown on the right) is upgraded to EHPMs/ENIM
combination. The network also includes C300_1 and C300_2
controllers which are included for new needs. EHPMs, C300_1,
C300_2, and ACE-T all can exchange data under peer access.
LCN nodes, AM, HM, ACE-T, ESR and ESVT can access the TPN
data from all HPMs, EHPMs, physical and emulated boxes
through TPN data access.

ATTENTION: Honeywell strongly recommends that the write

access to parameters in emulations from a non-emulation
strategy must not be attempted. It must be accessed
through the HG point.
There are 2 ways by which you can have non-emulated
strategies to access emulated strategies:
Access the HG points from the ACE_T node where the non-
emulated strategies reside,

47
 Chapter 3 - Experion LCN Deployment Considerations

l Access the HG points from local or peer CEE (where the

non-emulated strategies reside) through peer server
responder.
l Access HG points from local or peer CEE (where the non-
emulated strategies reside) through peer server
responder.

To the box emulation HBSE_1, EHB1 is the “ThisHG EHB”, and

EHB2 is the “AddedHG EHB” EHB1, EHB2, and ENIM are
migrated, and in the FTE network. HG3 and NIM are not
migrated and remain in LCN network.
2. Topology 2: Two LCNs to two FTEs with data access across
FTEs
This following topology is of the network that has two LCNs and
an equivalent to two FTEs. An L2.5 router is used to bridge the
Experion cluster.

To the emulated controller HBSE_1, EHB1 is the “ThisHG EHB”,

EHB2 is the “AddedHG EHB”. Similarly, for the emulated
controller HBSE_2, EHB3 is the “ThisHG EHB” and EHB4 is the
“AddedHG EHB”. The communication between HBSE_1 and
and HBSE_2 across FTE communities is through L2.5 router.
This topology splits two LCNs to two different FTE
communities. This type of topology may be suitable when there
are large number of nodes, and they cannot fit into one FTE

48
Chapter 3 - Experion LCN Deployment Considerations

community, or the customer wants to segment the network in

order to limit “Scale of Loss” when there are network failures.

ELCN-ENIM Considerations
Hardware Platform Reboot due to Experion Floating IP Address
Functionality: Redundant ELCN-ENIMs have a functionality
known as “Floating IP Address”. Floating IP Address means that
the IP address of the ENIM is determined by which ENIM is
running as primary, irrespective of their configured device
indexes. In the case of a primary node with an odd IP address,
and secondary node with an even IP address, if you want the
backup node to take over as the primary, or if the primary node
fails due to unforeseen circumstances, the current backup
node causes a reboot of the primary node, then gains the odd
IP address to become the primary node.

NOTE: Due to this functionality, while loading both ELCN-

ENIMs (of a redundant pair) from the PWR_ON state, may
result in a load failure for the ENIM with an odd IP address,
if the ELCN-ENIM with an even IP address starts loading
first, causing a reboot of the ELCN-ENIM with an odd IP
address. Wait for at least two minutes for the rebooted
ELCN-ENIM to transition to the PWR_ON state before
performing another load operation from the Native
Window.

Shut Down before Maintenance: Do not perform any

maintenance activities (such as FTE cable removal) on a
running ELCN-ENIM node, doing so may lead to Loss of View
(LOV) condition. Always shut down the node from the Native
Window and then perform any maintenance activity before
loading the node from the Native Window.
Redundancy Cable Fault Indications: In the case of a
redundancy cable breakage or if it is disconnected between a
redundant pair of ELCN Appliance nodes, the Native Window
does not give any indication of the problem and shows the
node states as OK/BACKUP. However, the Experion Detail
Display, Experion System Alarm Summary Display, and Control
Builder – Redundancy Tab give an indication that there is a

49
 Chapter 3 - Experion LCN Deployment Considerations

problem with the redundancy cable. Use these displays to

diagnose any redundancy cable related issues.
$FTESTS Schematics AUTH SERVER IP Addresses: For a
redundant pair of ELCN-ENIM nodes, the AUTH SERVER IP
addresses shown on the $FTESTS schematics are interchanged
(that is, the Primary ENIM will show the AUTH SERVER IP
Address of the Backup ENIM and the Backup ENIM will show
the AUTH SERVER IP Address of the Primary ENIM).
Device Index reconfiguration for a running Backup ELCN-ENIM
from the UEA Front Panel Display: Do not reconfigure the
Device Index of a running node (either backup or primary).
Make sure that you follow the documented procedures for
proper methods of setting or reconfiguring the Device Index.
Failure to do so may result in unpredictable behavior.
Back migration of UEA-based redundant ELCN Bridge and
ELCN-ENIM Nodes from R501.1 to R510.x is not supported:
After migrating UEA-based redundant ELCN Bridges and
ELCN-ENIM nodes from R501.1 to R510.x, if there is a need to
migrate back to R501.1, you cannot perform back migration to
R501.1. The only way to achieve back migration is by
performing off-process migration of the affected nodes.

ELCN Appliance Nodes Considerations

Hardware Platform Reboot due to Experion Floating IP Address
Functionality:
Redundant ELCN Appliance Nodes have a functionality known
as “Floating IP Address”. Floating IP Address means that the IP
address of the node is determined by which node is running as
primary, irrespective of their configured device indexes. In the
case of a primary node with an odd IP address, and secondary
node with an even IP address, if you want the backup node to
take over as the primary, or if the primary node fails due to
unforeseen circumstances, the current backup node causes a
reboot of the primary node, then gains the odd IP address to
become the primary node.

NOTE: Due to this functionality, while loading both ELCN

Appliance Nodes (of a redundant pair) from the PWR_ON

50
Chapter 3 - Experion LCN Deployment Considerations

state, may result in a load failure for the node with an odd
IP address, if the node with an even IP address starts
loading first, causing a reboot of the ELCN Appliance Node
with an odd IP address. Wait for at least two minutes for the
rebooted node to transition to the PWR_ON state before
performing another load operation from the Native
Window.

Shut Down before Maintenance: Do not perform any

maintenance activities (such as FTE cable removal) on a
running ELCN Appliance Node, doing so may lead to Loss of
View (LOV) condition. Always shut down the node from the
Native Window and then perform any maintenance activity
before loading the node from the Native Window.
Redundancy Cable Fault Indications: In the case of a
redundancy cable breakage or if it is disconnected between a
redundant pair of ELCN Appliance Nodes, the Native Window
does not give any indication of the problem and shows the
node states as OK/BACKUP. However, the Experion Detail
Display, Experion System Alarm Summary Display, and Control
Builder – Redundancy Tab gives an indication that there is a
problem with the redundancy cable. Use these displays to
diagnose any redundancy cable-related issues.
$FTESTS Schematics AUTH SERVER IP Addresses (ELCN-ENIM
only): For a redundant pair of ELCN-ENIM nodes, the AUTH
SERVER IP addresses shown on the $FTESTS schematics are
interchanged (that is, the Primary ENIM will show the AUTH
SERVER IP Address of the Backup ENIM and the Backup ENIM
will show the AUTH SERVER IP Address of the Primary ENIM).
Device Index reconfiguration for a running Backup ELCN
Appliance Node from the UEA Front Panel Display: Do not
reconfigure the Device Index of a running node (either backup
or primary). Make sure that you follow the documented
procedures for proper methods of setting or reconfiguring the
Device Index. Failure to do so may result in unpredictable
behavior.
Back migration of UEA-based redundant ELCN Bridge and
ELCN-ENIM Nodes from R501.1 to R510.x is not supported:
After migrating UEA-based redundant ELCN Bridges and
ELCN-ENIM nodes from R501.1 to R510.x, if there is a need to

51
 Chapter 3 - Experion LCN Deployment Considerations

migrate back to R501.1, you cannot perform back migration to

R501.1. The only way to achieve back migration is by
performing off-process migration of the affected nodes. Delete
Platform Block from Monitoring Side in Control Builder when
there is no active connection to the respective node(s), this
operation does not upload/delete the configuration from
Physical/Virtual node: DO NOT delete the platform block from
the Monitoring side in Control Builder when there is no active
connection to the respective node(s). For example, if a node is
in the process of rebooting (that is, icon shows red color in
Monitoring side), wait for the connection to be re-established
before deleting the platform block from the Monitoring side. If
not, the nodes will retain the old configuration even though it is
not loaded in Control Builder. For example, if the node is an
ELCN-ENIM with device index 153 and LCN/UCN address as
31/01, after the reboot, it retains the same configuration and
transitions to PWR_ON in Native Window even though the
platform block is not appearing in Monitoring side.
Non-redundant or Backup node shutdown for Physical or
Virtual node: Beginning with Experion R501.6, the following is
the non-redundant or backup node behavior during a TPN
personality failure.
If for some reason, a non-redundant or backup node transitions
to FAIL state on the Native Window, the following occur in a
sequence.
1. An automatic dump process is initiated by the device.

NOTE: Using Firmware Manager, the dump files can

be retrieved from the device’s local memory after a
reboot.

2. UEA or UVA node reboots and transitions to PWR_ON state

on the Native Window.

NOTE: A double shutdown from Native Window is an

example of transition to a FAIL state which will cause
these actions.

52
Chapter 3 - Experion LCN Deployment Considerations

ELCN-EPLCG Considerations
Cabling: The ELCN EPLCG module supports the following 6
different customer configurations (referred to as
Configurations 1 through 6) to satisfy PLC customers. There
are 4 different cabling procedures that cover the 6
configurations.
n Configurations 1 and 2 (Allen Bradley and/or
Modicon/Other Protocol)
n Configurations 3 and 5 (Modicon/Other Protocol)
n Configuration 4 (Allen Bradley Protocol)
n Configuration 6 (Allen Bradley Protocol)
For more information, see section “Cable Installation for
EPLCG” in the Experion LCN Hardware Upgrade Kit
Instructions (51195195-415).
Redundant communications option: The ELCN-EPLCG
“redundant communications” option is not supported in
Experion R501.4.
Allen Bradley Report-By-Exception feature: The Allen Bradley
Report-By-Exception feature is not supported in Experion
R501.4.
ENABLE SWAP option on Hiway Status Display:

53
 Chapter 3 - Experion LCN Deployment Considerations

The ENABLE SWAP option on the Hiway Status Display is not

applicable for EPLCG based Hiway networks. This option is not
applicable as the Hiway boxes under an EPLCG based Hiway
network do not have any physical Hiway cable connections.

ELCN NG Consideration
The ELCN-Network Gateway (NG) is an ELCN node that
connects the ELCN to a Plant Information Network (PIN). This
connection enables the exchange of data between the local
ELCN and remote ELCN on the same PIN. A Classic NG and an
ELCN NG cannot communicate with one another. For
successful communication, each ELCN NG on each LCN can
communicate with ELCN NG only. So, each Classic NG on LCN
must be converted to ELCN NG.
The NG acts as a transparent conduit for data exchange
requests between the local LCN and remote LCN (currently
limited to other LCNs) connected to the same PIN. The NG
contains no database except the NCF data required for
communication routing; therefore, the NG does not
"checkpoint," thus eliminating the need for node level
redundancy of the NG.
There are two NGs that work in close association with each
other. The names are:
1. ResponsibleNG: default node used for communication
2. AlternateNG: this node automatically takes over when
ResponsibleNG is not working. When ResponsibleNG resumes
working, the control is shifted back to it.
Note that these two nodes just work in close association with
each other. It does not mean that the NG is a redundant pair.
For each ELCN NG, there are two PINs, A and B, using which
the communication takes place. Depending on the Node
Configuration Form settings, select the PIN.
The following is the consideration:
n Ensure that both local LCN and remote LCN are FTE-based
ELCNs.

54
Chapter 3 - Experion LCN Deployment Considerations

AM Ride-Through functionality for ELCN Nodes

Application Module (AM) Ride-Through functionality is NOT

supported in these ELCN Nodes: E-APP and ACE-T.
AM Ride-Through functionality is the ability of an Experion
platform to ensure uninterrupted Application Processing
Platform (APP) control even while the Window’s-based platform
is being rebooted. For ELCN E-APPs and ACE-Ts (physical or
virtual), the LCNP4 card functionality is emulated by the
Microsoft Windows processor. When the Windows-based
platform is rebooted, the Microsoft Windows processor
emulating the LCNP4 card functionality is also rebooted,
negating the AM Ride-Through functionality. Hence, E-APPs
and ACE-Ts deployed as ELCN Nodes do not have AM Ride-
Through functionality.

ELCN Bridge and ELCN Appliance Node

Configuration Overview
The following diagram shows the user inputs required to
configure the ELCN Bridge and ELCN Appliance Nodes:
n From the UEA Front Panel, the user enters a unique FTE
Device Index, enables BOOTP for the UEA, and reboots the
node. The Experion Server acting as the BOOTP server then
assigns an IP Address to the UEA.
n After the UEA acquires an IP Address, the user can use the
Firmware Manager Tool on an Experion Server to load two
personality images to the UEA: the ELCN Application
personality image (either ELCN Bridge or ELCN Node), and
the Boot/Recovery personality image (same for all UEA node
types).
n After loading the firmware, the user must create and load
the platform blocks in Control Builder.
n After the platform blocks are loaded from Control Builder,
the ELCN Bridge is fully functional.
n For ELCN Appliance Nodes (such as AM, ENIM, EPLCG, and
EHB), the TPN/LCN Personality and Checkpoint file must be

55
 Chapter 3 - Experion LCN Deployment Considerations

loaded, typically from the History Module. (The TPN/LCN

personality is not the same as the UEA ELCN Personality
Image (UEAELCN) that is loaded as firmware.)
n The ELCN Bridge must be fully operational before any data
transfer can occur between the LCN and the ELCN. If you
implement an ELCN ES- T and the ELCN System History
Module, then you do not need the ELCN Bridge to load
TPN/LCN Personalities and Checkpoint files to ELCN Nodes
(such as ELCN ENIM, AM, EPLCG, and EHB). You need the
ELCN Bridge to load coaxial LCN nodes (such as coaxial
AM, ENIM, EPLCG, and so on) from an ELCN System History
Module.

ELCN Bridge Deployment Requirements

ELCN Bridge Minimum Requirements
The following minimum requirements must be in place prior to
deploying an ELCN Bridge:
n TPN/LCN Release R687.1 – You must upgrade all TPN/LCN
nodes, UCN nodes, and Data Hiway nodes to TPN/LCN
687.1 (or later) before migrating them to Experion LCN.

56
Chapter 3 - Experion LCN Deployment Considerations

ELCN Bridge Requirements for an Experion On-

Process Migration
If you are planning to implement the ELCN Bridge during an
Experion On-Process Migration (OPM) of your existing
Experion System, then you must install an additional, separate
R501 Experion Server to “commission” the ELCN Bridges and
then monitor them during the Experion On-Process Migration.

ATTENTION: This ELCN Bridge Commissioning Server is

needed only when migrating from Experion pre-R501 to
R501 (or later). There is no need for the ELCN Bridge
Commissioning Server if you are migrating from R501 or
later to a newer release.

REFERENCE: For more information, refer to the section

"Commissioning the ELCN Bridge during Experion OPM".

ELCN Bridge Requirements for an Experion Off-

Process Migration
For an off-process Experion System, the following requirements
must be met prior to deploying the ELCN Bridge:
n The ESVT(s), physical or virtual, must be running Experion
R501 (or later) and Microsoft Windows Server 2016.
n The ES- T (s), physical or virtual, must be running either
Microsoft Windows 10 (physical) or Microsoft Windows
Server 2016 (physical or virtual).
n The Experion Base IP address must be configured on the
primary ESVT and its “Experion PKS BOOTP Server”
Windows service must be running.
n You must have an R501 Experion Server with the Firmware
Manager Tool available on the server to be able to load
(flash) the firmware of the ELCN Bridge and any UEA
hardware- based ELCN Appliance Nodes. Install the R501
ESVT first, to be able to flash the firmware.

57
 Chapter 3 - Experion LCN Deployment Considerations

ELCN Bridge Requirements for a New Experion

System
ELCN Bridge requirements for a new Experion System are the
same as for an Experion Off-Process migration of an existing
Experion System. Refer to the section “ELCN Bridge
Requirements for an Experion Off-Process Migration” for these
requirements which must be met prior to deploying the ELCN
Bridge in a new Experion System.

ELCN Node Automatic Dump

If an ELCN Node changes state to FAIL, an automatic dump
process is initiated by the device.
The result of this dump process is different to that of the
manual dump that is initiated from Native Window or Universal
Station, such that the dump file is stored in the device’s flash
memory versus being stored on the History Module.
The dump files can be retrieved from the device at the time of
failure or after a reboot using Firmware Manager, following the
procedure for Diagnostic Capture.

ELCN On-Demand Dump

The dump feature initiated from Native Window requires an
ELCN Node to transition to FAIL state. The required
information is captured well but the point of origin of the issue
remains unknown. This results in two issues:
1. Node downtime – While the node is in FAIL state and it
remains unusable during that time
2. Reliability – the information from the dump is not adequate
to troubleshoot an issue
Beginning with TPN R688.3 and Experion R501.6, to overcome
these limitations of the Automatic Dump feature, a new feature
called On-Demand Dump is introduced on the Experion System
Management Dashboard to generate a dump of the selected
ELCN Node while the node is in one of the running states as
follows: OK, BACKUP, WARNING, and SEVERE.

58
Chapter 3 - Experion LCN Deployment Considerations

Honeywell representatives use the TPN Dump Analyzer Tool to

analyze the captured dump. This dump is used to further
investigate and understand the issues related to,
n Heap memory fragmentation
n Node isolation
n LCN network sluggishness
n Display/Schematic call-up failure and other functionalities
n Performance related issues
The On-Demand Dump provides a mechanism to:
n Keep a close- eye on the first instance of an abnormal
behavior and its gradual transition to node failure.
n Trace the root cause of the failure based on the information
captured.
To initiate TPN dump collection for a PC-type node (ESVT/ES-
T/ACE-T/E-APP/HM)/UEA or UVA node using the On-Demand
Dump feature, identify the node that is deviating from normal
behavior and perform the following procedure.
1. Open Experion System Management Dashboard.
2. From the Experion System Management Dashboard, locate
the node you wish to perform the On-Demand dump, and
then double-click the node to open its specific detail display.

3. From the COMMANDS tab, click On-Demand Dump. A

message appears that displays the path where the dump file
is stored.
4. Click Execute.

59
 Chapter 3 - Experion LCN Deployment Considerations

The dump collection process progresses.

The dump collection completes.

60
Chapter 3 - Experion LCN Deployment Considerations

The dump file is saved in the following location by default,

..\ProgramData\Honeywell\TPSLogs\TPSDumps.

The naming convention used for a dump file is dump_

odx.zip, where x is 1,2,3, and so on.

Collecting dump for a UEA UVA node

For a UEA/UVA node, the dump file is stored in the node itself.
Use Firmware Manager to retrieve TPN dump for a UEA/UVA
node. To retrieve the TPN dump using Firmware Manager:

1. Click Start > Honeywell Experion Tools > All Honeywell Tools
> Firmware Manager.
RESULT: The Firmware Manager window appears.

61
 Chapter 3 - Experion LCN Deployment Considerations

2. Click the node you want to retrieve the dump for (for
example, 10.1.1.109), and then click Diagnostic Capture.

The dump file retrieval process progresses.

62
Chapter 3 - Experion LCN Deployment Considerations

3. The path where the dump is stored appears. The path is

C:\Programdata\Honeywell\FirmwareManager\Logs\Diagno
sticCapture

4. Go to the above mentioned path to access the zipped dump

file for the UEA/UVA node. The naming conventions used for:

l UEA node - UEA-<IP address of system>

l UVA node - UVA-<IP address of system>
Note that the On-Demand dump option is available only
on ELCN ES-T.

63
 Chapter 3 - Experion LCN Deployment Considerations

Maximum number of ELCN ES-Ts per ELCN

ESVT cluster
Beginning with Experion R501.6 and TPN R688.3, you can
configure up to 30 ELCN ES-Ts per ELCN ESVT cluster without
impacting the system performance, however, ensure that the
following conditions are met, if not, configuration of up to 20
ELCN ES-Ts is supported per ESVT cluster:
n This enhancement is not supported if there are C300
controllers integrated with your system, this includes
products such as, EHB and C300 controller based ELMM.
n While using the increased number of ELCN ES-Ts, enough
care must be taken to ensure that the data owners and
controllers in the LCN are not loaded beyond their
documented limits.
n When you are migrating GUS or US stations to ES-Ts, you
must consider the number of ES-Ts which already exist in
the network.
l After migrating existing GUS or US stations to ES-Ts, do

not create additional load on the data owners by invoking

displays such as, HMIWeb, GUS and US displays.
l If you are using HMIWeb display instead of US/GUS

display after configuring up to 30 ES-Ts and this causes

additional load on the data owners, examine the station
and display update rates, and check that the default
station update rate is not set at 1 second.

ATTENTION: If the ELCN System Management Dashboard

feature is configured in Station and you are trying to
configure more than 20 ELCN ES-Ts, this results in high
PARSEC load on the ENIMs in the LCN and may lead to an
undesirable behavior. The PARSEC value approximately
increases by 20 per ELCN ES-T configured under the
network. Therefore, it is important that you consider the
existing load on an ENIM before you configure more ELCN
ES-Ts with the ELCN System Management Dashboard
feature configured in the network.

64
Chapter 3 - Experion LCN Deployment Considerations

Security Considerations for Experion LCN

Limit physical access to the system. Make arrangements for
key-locked cabinets with access allowed only to 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 Experion LCN 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 default installation
directory for the .lcn files. If you choose to use a different
directory, the permissions should be set to have only the TPN
users access the directory.
REFERENCE: Refer to the following documents for specific
security information:
n For information on securing peer-to-peer communications
between devices, refer to the Experion Network and Security
Planning Guide.
n For information on restricting the systems to authorized
users, refer to the Experion Network Best Practices.
n For information on FTE network architecture, guidelines,
and requirements, refer to the FTE Overview and
Implementation Guide (FTE02).

Experion LCN Migration Preparation Checklist

n Honeywell highly recommends that an IAA/SPB (Integrated
Automation Assessment/System Performance Baseline) be
performed prior to the ELCN installation, so there is a
baseline prior to the upgrade.
n Honeywell recommends the site have all preparations in
place before the removal of the nodes from the LCN. This
includes the LCN coax cables and Tees (A and B) be
preinstalled and ready to hook up once the machine has

65
 Chapter 3 - Experion LCN Deployment Considerations

been decommissioned.
n The site must prepare the system to be changed if the node
(s) to be decommissioned are the LCN Clock Sources. If this
is the case, it is highly recommended the LCN Clock source
change be implemented prior to the decommissioning. Note
that the Clock Sources on ELCN must be changed to be
ESVTs. For more information, refer to section “NCF Clock
Source nodes must be ESVTs”.
n The minimum LCN version is R687.1. This must be installed
on all nodes prior to the ELCN installation.
n The minimum Utilities and Load Module version is R301.18.
These files (disk_&z12.lcn and disk_&z14.lcn files) must be
copied to the HM prior to the implementation of the ELCN
Nodes. Use the MSCHEMZ.EC file on disk_&z14.lcn to
upgrade the Load Modules to the HM.
n Verify the ELCN node replacement EXTERNAL LOAD
MODULES have been accurately configured and
implemented in the LCN NODE CONFIGURATION.
REFERENCE: For complete details, please refer to the
Integrated Experion-TPS User’s Guide (EX23), “Preparing
TPN/LCN for Experion Nodes”.
n The minimum Experion PKS release is R501.1. This must be
installed on all Experion PKS devices.

Prerequisites for ELCN UEA Appliance Node migration

The following are the common prerequisites for all the ELCN
UEA Appliance Nodes.

Step Detailed Description Done

LCN/UCN/EUCN All LCN / UCN / EUCN nodes display a

node status good FTE, UCN, and LCN cable status.

LCN Extender If you are using an existing node chassis

(LCNE) card as an LCN Extender, and this is the node
you plan to migrate to an ELCN node,
you need to take special caution that the
LCN Extender card is moved to a
different node’s chassis as part of the
ELCN migration.

66
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

Refer to the following documents for

more information on LCN Extender card:
l LCN Planning (SW02-601)
l LCN Guidelines Implementation,
Troubleshooting, and Service (LC09-
610)

ELCN-ESVTs Make the primary and secondary ELCN-

configured as ESVT nodes the NCF Clock Source
Clock Master Primary and Clock Source Secondary.
nodes

(cont.) ELCN- Verify that the ELCN-ESVTs (in this case,

ESVTs configured nodes 51 and 52) are running as the
as Clock Master NCF Clock Source Primary and Clock
nodes Source Secondary nodes.

REFERENCE: For information on

changing the time source, see section
“3.6.1.1 ”.

ELCN Bridge A redundant pair of ELCN Bridge UEA

boxes must be installed, configured in
Control Builder and running.

Ethernet crossover Ensure that an Ethernet crossover cable

cable is available for connecting the

67
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

redundancy ports of the primary and

secondary UEA boxes for each redundant
node pair.

NOTE: Do not connect this cable

until instructed to do so.

BOOTP Server Make sure that BOOTP Server is available

Availability in the Experion LCN Network for
assigning IP addresses.

NOTE: BOOTP Server provides IP

addresses to the nodes in the FTE
community.

NOTE: If there are more than one

cluster in the same FTE
community, make sure that the
BOOTP Server is running only in a
single Experion Cluster.

Configure Experion Configure Experion Base IP Address and

Base IP Address SNTP IP Address.
and SNTP IP
Address
NOTE: The primary and secondary
server IP addresses are of ELCN
ESVTs.

The Experion System Preferences can be

configured using Control Builder. The
configuration is saved in the ERDB. Click
Tools > System Preferences > Embedded
FTE.

68
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

For more information, see the Control

Building User's Guide, section “Setting
System Preferences”.

Configure NTP A minimum of an NTP (Network Time

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

NOTE: A PTP time source is

required when using EHPMs with
DISOE IOP.

For more information, see section “Time

Synchronization Considerations”.

Enable Experion / See section “3.6.5.3 ”.

TPS to TPN Time
Sync

L2 FTE Switch port Make sure that you have the following L2
configurations port configurations for the FTE switches
connected to the ELCN nodes.
l “Network Speed” set to AUTO
l “Communication Type” set to FULL
DUPLEX

L2 ports Make sure that you have sufficient L2

availability on FTE ports available on the FTE switches.
switches

69
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

ELCN Appliance Note that the UEA boxes have built-in

nodes are Level 2 control firewall, therefore ELCN
nodes Appliance Nodes do not require separate
CF9 switches in the network.

In addition to the prerequisites mentioned here, there are a few node-specific

prerequisites as follows:

Migration from Classic AM to ELCN UEA AM

License Migration to Non-Redundant ELCN-AM

requires the “Upgrade to ELCN AM (TC-
ZLAM01)” license. Migration to
Redundant ELCN-AM requires the
“Upgrade to ELCN AM Red (TC-
ZLAM02)” license.

TPN version Minimum of TPN R687.1 must be

installed for Non-Redundant AM
migration, and TPN R688.1 for
redundant AM migration.

Experion version Minimum of Experion R501.1 must be

installed for Non-Redundant AM
migration, and R501.4 for redundant AM
migration.

Migration from Classic NIM to ELCN UEA ENIM

License Migration to ELCN-ENIM requires the

“Upgrade to ELCN-ENIM RED from NIM
RED (TC-ZLNIM2)” license.

TPN version Minimum of TPN R687.1 must be

installed.

Experion version Minimum of Experion R501.1 must be

installed.

Copying ENIM For the ELCN-ENIM nodes to operate

Load Module to properly on the LCN, system files called
HM external load modules ENIM.LO and
ENAME.LO are required in the “&CUS”
directory on the TPN/LCN system
History Module.

70
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

When using the PRS4VOLZ.EC (or

optionally PRS2VOLZ.EC) file, type YES
when you are prompted with the
message “Copy &OVG (OPTIONAL) to net
(YES/NO)?” to copy both ENIM.LO and
ENAME.LO to the History Module.

NOTE: Configuring ENAME load

module in the NIM’s NCF
configuration is optional. It is
required only if you want to
automatically import the EHPM
points into ERDB for use with
Experion (for peer-to-peer
communication, for example).
However, configuring the ENIM
load module in the NIM’s NCF
configuration is required for an
ENIM.

ATTENTION: This procedure needs

to be performed only once per
TPN/LCN, not per node.

Adding Load
Modules to NCF ATTENTION: This procedure needs
to be performed only on the
Primary NIM node. The
configuration is automatically
copied to the Secondary NIM’s
NCF configuration.

1. Choose Engineering Main Menu >

Support Utilities > Modify Volume
Paths, to ensure that the NCF
BACKUP PATH is defined, for example,
$FX>&ASY>.
2. Insert the removable media in the
specified drive.

71
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

3. From the Engineering Personality

Main Menu, select the LCN Nodes
target.
RESULT: A display appears with a
target for each node possible on the
LCN.
4. Verify that the configurator is in the
ON-LINE mode in the upper right
corner of the display.
5. Select the target for the node number
of the NIM that you want to configure
for ENIM.
6. Select the Modify Node target.
7. Now, page forward to page two. Enter
the name of the appropriate version
for both external load modules, ENIM
and ENAME and their associated
personality type, NMO.

NOTE: Configuring ENIM load

module is required. Adding
ENAME load module is optional,
but is required if you want to
automatically import the EHPM
points into ERDB for use with
Experion (for example, peer-to-
peer communication). An optional
license “EHPM-Experion
Connection Enabler” is required
for the Experion-integrated
firmware for this functionality.

8. Enter a value for the Maximum

External Module Memory (Words)
which must be 20,000 greater that the
value shown in Total (Modules Plus
Additional Memory), such that the
ENIM load module could grow without
affecting the future

72
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

updates/migrations.
9. Press ENTER.
10. Press [CTL-F1] to check the new NCF.
11. Press [CTL-F2] to install the new NCF.
12. Press ENTER to confirm the install.
13. Return to the Engineering Personality
Main Menu.
RESULT: A message appears at the
bottom of the display indicating
successful completion of the NCF
installation.

ATTENTION: After the NCF

configuration is complete, on the
NCF Status Display, the NIM(s) are
highlighted in yellow color
indicating that you have to reboot
the respective node for the NCF
change to take effect.

Migration from Classic ENIM to ELCN UEA ENIM

License Migration to ELCN-ENIM requires the

“Upgrade to ELCN-ENIM (TC-ZLNIM4)”
license.

TPN version Minimum of TPN R687.1 must be

installed.

Experion version Minimum of Experion R501.1 must be

installed.

ENBs must be You cannot perform on-process

migrated to Classic migration directly from ENB to ELCN-
ENIMs ENIM. You must first migrate to Classic
ENIM when you reach the “last UCN
node” scenario as described in the NIM
to ENB Upgrade Kit Instructions
(51195195-403), section “On-process
migration from ENB to ENIM”. Once you

73
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

have a redundant Classic ENIM, you can

migrate them to ELCN-ENIMs.

ENIMs must be Make sure that the Classic ENIMs are

flashed with flashed with Experion-integrated
Experion- firmware (EXP501.1-xx.xx). If not, use the
integrated (BOOT Stand Alone EPA Tool to flash the
and APP) firmware Experion-integrated firmware to Classic
ENIMs.
For more information, see the Customer
Release Guide (CRG-687) or later,
chapter “Migration from standalone
firmware (BOOT-only) to Experion-
integrated (BOOT and APP) firmware”.
Verify that the firmware versions
displayed are:
For example,
BOOT firmware version: EXP501.1-38.91
APP firmware version: EXP501.1-38.91

NOTE: Actual version may be

different, refer to the Experion PKS
R501.1 (or later) Software Change
Notice for information on the
latest firmware version.

Migration from Classic EPLCG to ELCN UEA EPLCG

License Migration to Non-Redundant ELCN-

EPLCG requires the “Upgrade to ELCN
EPLCG (TC- ZLPLG1)” license. Migration
to Redundant ELCN-EPLCG requires the
“Upgrade to ELCN EPLCG Red (TC-
ZLPLG2)” license.

74
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

TPN version Minimum of TPN R688.1 must be

installed.

Experion version Minimum of Experion R501.4 must be

installed.

EPLCG Cables Make sure that all required cables

supplied in the kit(s) are available prior to
performing migration procedures.
Depending on the customer system
configuration, these cables may include:
l FTE Cables
l Port Cables (PORT 1 and PORT 2)
l Configuration Jumper Cable (CONFIG
JUMPER)
l Module Interlink and CEP
Redundancy Cable (INTER-LINK)

NOTE: It is mandatory to connect

BOTH the Primary/P1 Side of the
Interlink Cable and the Primary/P1
Side of the Configuration Jumper
cable to the same UEA module,
that is, the installation may not
have P1 of Interlink and P2 of
Configuration Jumper Cable
together connected to the same
UEA module. Module redundancy
will not work if the cables are
crossed.

For information on UEA installation

specific to the EPLCG, see the Experion
LCN Hardware Upgrade Kit Instructions
(51195195-415).

Make a note of the Make a note of the Baud Rate and Parity
Baud Rate and settings as per the TS2 jumpers on the
Parity settings EPLCI board before migrating from
Classic EPLCG to ELCN-EPLCG.

75
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

Use the silk-screen labels on the printed

circuit board to interpret the TS2
JUMPERS settings on the EPLCI board.
For example, PORT1’s and PORT2’s Baud
Rate values are set to 9600 and Parity
values are set to EVEN as shown in the
following image.

Migration from Classic EHB to ELCN UEA EHB

License Migration to ELCN-EHB requires the

“Upgrade to ELCN-EHB (TC-ZLNIM4)”
license.

TPN version Minimum of TPN R688.1 must be

installed. TPN R688.1 is required for
migration to ELCN-EHB.

Experion version Minimum of Experion R501.4 must be

installed.

Junction gateway You cannot perform on-process

should be migration directly from Classic EHB to
migrated to Simple ELCN-EHB using Junction gateway. To
gateway perform the migration, you must migrate
from Junction gateway to Simple
gateway.

EHB network mode EHB should be in the EHB network mode

of FTE ($EHBNTWK set to FTE) where all
the HG boxes are transitioned to the
Hiway box emulations in C300.

Hardware K4LCN-16MW and EHBI card are

present in the LCN chassis for each EHB.

Remote HG All configurations with Remote HG need

to be re-engineered. Remote HG topology
is not supported with ELCN EHB, only

76
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

ThisHG and AddedHG topologies are

supported.

Migration from Classic NG to ELCN-NG

License Migration to ELCN-NG requires the

“Upgrade to ELCN NG (TC-ZLNG01)”
license.

TPN version Minimum of TPN R688.3 must be

installed.

Experion version Minimum of Experion R501.6 must be

installed.

NG Cables Make sure that all required cables

supplied in the kit(s) are available prior to
performing migration procedures.
Depending on the customer system
configuration, these cables may include:
l FTE Cables
l PIN Cables PIN A and/or PIN B
For information on UEA installation
specific to the NG, see the Experion LCN
Hardware Upgrade Kit Instructions
(51195195-415) and ELCN Planning,
Installation, and Service Guide. And for
information related to NG, refer Network
Gateway Implementation and Operation,
Network Gateway Site Planning and
Installation.

PIN Configuration Before migrating to ELCN NG, plan the

ELCN NG PIN A and B network
configuration and topology in advance.
For more details, refer ELCN NG
Planning, Installation, and Service Guide.

Prerequisites for ELCN UVA Appliance Nodes

Step Detailed Description Done

LCN/UCN/EUCN All LCN / UCN / EUCN nodes display

77
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

node status a good FTE, UCN, and LCN cable

status.

ELCN-ESVTs Make the primary and secondary

configured as Clock ELCN-ESVT nodes the NCF Clock
Master nodes Source Primary and Clock Source
Secondary.

(cont.) ELCN-ESVTs Verify that the ELCN-ESVTs (in this

configured as Clock case, nodes 51 and 52) are running
Master nodes as the NCF Clock Source Primary and
Clock Source Secondary nodes.

REFERENCE: For information on

changing the time source, see section
“3.6.1.1 ”.

ELCN Bridge A redundant pair of ELCN Bridge UEA

boxes must be installed, configured in
Control Builder and running.

BOOTP Server Make sure that BOOTP Server is

Availability available in the Experion LCN
Network for assigning IP addresses.

NOTE: BOOTP Server provides

IP addresses to the nodes in
the FTE community.

78
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

NOTE: If there are more than

one cluster in the same FTE
community, make sure that the
BOOTP Server is running only
in a single Experion Cluster.

Configure Experion Configure Experion Base IP Address

Base IP Address and and SNTP IP Address.
SNTP IP Address
NOTE: The primary and
secondary server IP addresses
are of ELCN ESVTs.

The Experion System Preferences can

be configured using Control Builder.
The configuration is saved in the
ERDB. Click Tools > System
Preferences > Embedded FTE.

For more information, see the Control

Building User's Guide, section
“Setting System Preferences”.

Configure NTP Time A minimum of an NTP (Network Time

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

NOTE: A PTP time source is

required when using EHPMs

79
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

with DISOE IOP.

For more information, see section

“Time Synchronization
Considerations”.

Enable Experion / TPS See section “3.6.5.3 ”.

to TPN Time Sync

L2 FTE Switch port Make sure that you have the following
configurations L2 port configurations for the FTE
switches connected to the ELCN
nodes.
l “Network Speed” set to AUTO
l “Communication Type” set to FULL
DUPLEX

Configure ESXi host Refer chapters “Preparing a

management ESXi host” and
“Preparing a Production ESXi host” in
Virtualization Planning and
Implementation Guide.

In addition to the prerequisites mentioned here, there are a few node-specific

prerequisites as follows:

Migration from Classic AM to ELCN UVA AM

License The following licenses are available

for migration from Classic AM or
ELCN UEA AM to UVA-based ELCN
AM. Choose the license as per your
requirement.
l EP-LCNV01 (Experion LCN VIRT
APPLIANCE USAGE LIC)
l EP-LCNV05 (Experion LCN 5 VIRT
APPLIANCE USAGE LIC)
l EP-LCNV10 (Experion LCN 10
VIRT APPLIANCE USAGE LIC)

TPN version TPN R687.1 is required for migration

80
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

to virtual ELCN AM.

Experion version Experion R501.4 is required for

migration to virtual redundant and
non-redundant ELCN AM.

Migration from Classic NIM to ELCN UVA ENIM

License The following licenses are available

for migration from Classic NIM or
ELCN UEA NIM to Virtual ENIM.
Choose the license as per your
requirement.
l EP-LCNV01 (Experion LCN VIRT
APPLIANCE USAGE LIC)
l EP-LCNV05 (Experion LCN 5 VIRT
APPLIANCE USAGE LIC)
l EP-LCNV10 (Experion LCN 10
VIRT APPLIANCE USAGE LIC)

TPN version TPN R688.1 is required for migration

to virtual ELCN ENIM.

Experion version Experion R501.4 is required for

migration to virtual ELCN ENIM.

Copying ENIM Load For the ELCN-ENIM nodes to operate

Module to HM properly on the LCN, system files
called external load modules
ENIM.LO and ENAME.LO are required
in the “&CUS” directory on the
TPN/LCN system History Module.
When using the PRS4VOLZ.EC (or
optionally PRS2VOLZ.EC) file, type
YES when you are prompted with the
message “Copy &OVG (OPTIONAL) to
net (YES/NO)?” to copy both ENIM.LO
and ENAME.LO to the History
Module.

NOTE: Configuring ENAME

load module in the NIM’s NCF

81
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

configuration is optional. It is
required only if you want to
automatically import the EHPM
points into ERDB for use with
Experion (for peer-to-peer
communication, for example).

NOTE: However, configuring

the ENIM load module in the
NIM’s NCF configuration is
required for an ENIM.

ATTENTION: This procedure

needs to be performed only
once per TPN/LCN, not per
node.

Adding Load Modules

to NCF ATTENTION: This procedure
needs to be performed only on
the Primary NIM node. The
configuration is automatically
copied to the Secondary NIM’s
NCF configuration.

1. Choose Engineering Main Menu >

Support Utilities > Modify Volume
Paths, to ensure that the NCF
BACKUP PATH is defined, for
example, $FX>&ASY>.
2. Insert the removable media in the
specified drive.
3. From the Engineering Personality
Main Menu, select the LCN Nodes
target.
RESULT: A display appears with a
target for each node possible on

82
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

the LCN.
4. Verify that the configurator is in
the ON-LINE mode in the upper
right corner of the display.
5. Select the target for the node
number of the NIM that you want
to configure for ENIM.
6. Select the Modify Node target.
7. Now, page forward to page two.
Enter the name of the appropriate
version for both external load
modules, ENIM and ENAME and
their associated personality type,
NMO.

NOTE: Configuring ENIM

load module is required.
Adding ENAME load module
is optional, but is required if
you want to automatically
import the EHPM points into
ERDB for use with Experion
(for example, peer-to-peer
communication). An optional
license “EHPM-Experion
Connection Enabler” is
required for the Experion-
integrated firmware for this
functionality.

8. Enter a value for the Maximum

External Module Memory (Words)
which must be 20,000 greater that
the value shown in Total (Modules
Plus Additional Memory), such that
the ENIM load module could grow
without affecting the future
updates/migrations.

9. Press ENTER.

83
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

10. Press [CTL-F1] to check the new

NCF.

11. Press [CTL-F2] to install the new

NCF.

12. Press ENTER to confirm the install.

13. Return to the Engineering

Personality Main Menu.
RESULT: A message appears at the
bottom of the display indicating
successful completion of the NCF
installation.

ATTENTION: After the NCF

configuration is complete, on
the NCF Status Display, the
NIM(s) are highlighted in yellow
color indicating that you have
to reboot the respective node
for the NCF change to take
effect.

Migration from Classic ENIM to ELCN UVA ENIM

License The following licenses are available

for Migration from Classic ENIM or
ELCN UEA ENIM to Virtual ENIM.
Choose the license as per your
requirement.
l EP-LCNV01 (Experion LCN VIRT
APPLIANCE USAGE LIC)
l EP-LCNV05 (Experion LCN 5 VIRT
APPLIANCE USAGE LIC)
l EP-LCNV10 (Experion LCN 10
VIRT APPLIANCE USAGE LIC)

TPN version TPN R688.1 is required for migration

to virtual ELCN ENIM.

84
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

Experion version Experion R501.4 is required for

migration to virtual ELCN ENIM.

ENBs must be You cannot perform on-process

migrated to Classic migration directly from ENB to ELCN-
ENIMs ENIM. You must first migrate to
Classic ENIM when you reach the
“last UCN node” scenario as
described in the NIM to ENB Upgrade
Kit Instructions (51195195-403),
section “On-process migration from
ENB to ENIM”. Once you have a
redundant Classic ENIM, you can
migrate them to ELCN-ENIMs.

ENIMs must be Make sure that the Classic ENIMs are

flashed with Experion- flashed with Experion-integrated
integrated (BOOT and firmware (EXP501.1-xx.xx). If not, use
APP) firmware the Stand Alone EPA Tool to flash the
Experion-integrated firmware to
Classic ENIMs.
For more information, see the
Customer Release Guide (CRG-687)
or later, chapter “Migration from
standalone firmware (BOOT-only) to
Experion-integrated (BOOT and APP)
firmware”.
Verify that the firmware versions
displayed are:
For example,
BOOT firmware version: EXP501.1-
38.91
APP firmware version: EXP501.1-
38.91

85
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

NOTE: Actual version may be

different, refer to the Experion
PKS R501.1 (or later) Software
Change Notice for information
on the latest firmware version.

Migration from Classic EHB to ELCN UVA EHB

License The following licenses are available

for Migration from Classic EHB or
ELCN UEA EHB to UVA-based ELCN
EHB. Choose the license as per your
requirement.
l EP-LCNV01 (Experion LCN VIRT
APPLIANCE USAGE LIC)
l EP-LCNV05 (Experion LCN 5 VIRT
APPLIANCE USAGE LIC)
l EP-LCNV10 (Experion LCN 10
VIRT APPLIANCE USAGE LIC)

TPN version TPN R688.1 is required for migration

to ELCN-EHB.

Experion version Experion R501.4 is required for

migration to virtual ELCN-EHB.

Junction gateway You cannot perform on-process

should be migrated to migration directly from Classic EHB
Simple gateway to ELCN-EHB using Junction
gateway. To perform the migration,
you must migrate from Junction
gateway to Simple gateway.

EHB network mode EHB should be in the EHB network

mode of FTE ($EHBNTWK set to FTE)
where all the HG boxes are
transitioned to the Hiway box
emulations in C300.

Hardware K4LCN-16MW and EHBI card are

present in the LCN chassis for each

86
Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

EHB.

Remote HG All configurations with Remote HG

need to be re-engineered. Remote HG
topology is not supported with ELCN
EHB, only ThisHG and AddedHG
topologies are supported.

Migration from Classic NG to ELCN-NG

License The following licenses are available

for Migration from Classic NG or
ELCN-NG to UVA-based NG. Choose
the license as per your requirement.
l EP-LCNV01 (Experion LCN VIRT
APPLIANCE USAGE LIC)
l EP-LCNV05 (Experion LCN 5 VIRT
APPLIANCE USAGE LIC)
l EP-LCNV10 (Experion LCN 10
VIRT APPLIANCE USAGE LIC)

TPN version Minimum of TPN R688.3 must be

installed.

Experion version Minimum of Experion R501.6 must be

installed.

PIN Configuration Before migrating to ELCN NG, plan

the ELCN NG PIN A and B network
configuration and topology in
advance. For more details, refer ELCN
NG Planning, Installation, and Service
Guide.

NG Cables Make sure that all required cables

supplied in the kit(s) are available
prior to performing migration
procedures. Depending on the
customer system configuration, these
cables may include:
l FTE Cables
l PIN Cables PIN A and/or PIN B

87
 Chapter 3 - Experion LCN Deployment Considerations

Step Detailed Description Done

For information related to NG, refer

Network Gateway Implementation and
Operation, Network Gateway Site
Planning and Installation.

88
CHAPTER

4 UEA HARDWARE OVERVIEW AND INITIAL

STARTUP PROCEDURES

In this section:

UEA Hardware Overview 90

UEA Hardware Components and Cabling 91
Initial Startup of UEA 99
Loading UEA Firmware 103

89
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

This section provides an overview of the Universal Embedded

Appliances (UEA) hardware used by the ELCN Bridge and
ELCN Appliance Nodes. This section also provides detailed
procedures to perform initial UEA startup. Initial startup of a
UEA 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
Address acquired from the Experion BOOTP server for both the
primary and secondary UEAs.
REFERENCE: For details on UEA hardware planning and
installation, refer to the Experion LCN Planning and Installation
Guide.

UEA Hardware Overview

UEA Site Planning Considerations
Cabinet and Power - Installation of a Honeywell UEA upgrade
kit requires a 19 inch rack mount cabinet. The cabinet that is to
contain a redundant UEA pair must be equipped with
redundant Power Distribution Units (PDUs).
Redundant UEAs - The redundant ELCN Bridge pair and any
redundant ELCN Appliance Nodes should be deployed with
similar practices followed for current and/or legacy redundant
nodes. For example, deploy with physical separation of ELCN
Bridges and power. In the event of a dual ELCN Bridge failure,
LCN isolation recovery procedures apply.
Be aware that if you deploy an ELCN Appliance Node as non-
redundant, and then in the future determine that you need to
make it redundant, you will not be able to configure the node as
redundant while the node is running – you will have to do a
Native Window shut down of the node prior to reconfiguring it.
LCN Cables for ELCN Bridge - The planned ELCN Bridge
location should be near the existing LCN cables in order to add
a length of LCN cable and BNC Tees for connection to the
ELCN Bridge’s MAU cables.
Route FTE Cables from FTE Switch - Sufficient Level 2 Fault
Tolerant Ethernet (FTE) switch ports must be available within
sufficient distance from the FTE switch for all ELCN Bridges
and ELCN Appliance Nodes.

90
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

UEA Hardware Components and Cabling

UEA Processor Module
The UEA Processor Module (front box) contains the processor,
user interface display, push button controls, key switch, power
supply, and fan.

UEA Termination Assembly

The UEA Termination Assembly provides all external cable
connections to the processor. It slides into the rear of the
Processor Module. The Termination Assembly contains no user
serviceable parts and may be replaced in the event of
termination assembly receptacle damage. Receptacle usage is
application dependent. For example, the LCN cable receptacles
are only used for MAU cable connections when the UEA is used
as an ELCN Bridge.
ELCN Bridge/ENIM/AM/EHB Termination Assembly connector
ports include:
n Ethernet connectors (2 sets of paired, 1 single)
n 2 Local Control Network (LCN) Media Access Unit (MAU)
mini D connectors
(Termination Assembly for ELCN Bridge and
ENIM/AM/EHB/NG)

91
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

EPLCG termination assembly connector ports include:

n 2 Ethernet connectors (FTE A and FTE B)
n 2 isolated RS-232 field ports used for serial communication
with PLCs and communication interfaces (PORT 1 and
PORT 2)
n 1 configuration jumper connector used to reconfigure the
ELCN EPLCG for Modicon/Allen-Bradley protocols (CONFIG
JUMPERS)
n 1 RS- 422 port used for redundancy communication
between ELCN EPLCGs and an Ethernet communication
signals used for Experion redundancy (INTER-LINK)
(Termination Assembly for ELCN EPLCG)

92
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Cables for ELCN Bridge/ENIM/AM/EHB Termination

Assembly

LCN MAU Cables for ELCN Bridge

The LCN connection to an ELCN bridge is made with of a pair
of MAU cables. The MAU cables contain electronics that
convert LCN analog signals to digital signals, which are then
processed by the ELCN Bridge to be made compatible with
ELCN FTE. The reverse occurs when ELCN FTE signals are sent
to LCN nodes. This two-way process allows for full two-way
LCN to ELCN communication. The following illustration shows
the ELCN Bridge MAU cable – it is a new “in-cable” MAU.

The D-connectors on one end of the ELCN Bridge MAU cables

attach to receptacles on the Termination Assembly at the rear
of the primary and the secondary UEAs. The following figure
shows the LCN cable receptacles and ELCN Bridge MAU cable
B (green) secured by captive screws.

Redundancy Cable
A single Redundancy cable (orange) directly connects to the
Redundancy port of each UEA termination module of a
redundant pair.

93
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

FTE Cables
The FTE cables A (yellow) and B (green) connect to the
termination panel of each UEA. FTE cables with yellow and
green insulation jackets are constructed with stranded
conductors. FTE cables with white jackets have solid
conductors. The solid conductor cables have a strain relief
requirement (radius of any bend should be three inches
minimum, and the loop diameter should be six inches
minimum).
FTE cables connected to the UEA and switch ports must be
Category 5e shielded twisted pair cable with 100-ohm
impedance and electrical characteristics supporting
transmission rates of up to 100 Mbps. The cable must be
compliant with the TIA/EIA-568A wiring standard, and the
100BaseTX IEE-802.3u specification.
The maximum length for a stranded FTE cable run to a switch
is 100 meters. The maximum length for a stranded FTE patch
cable according to TIA/EIA-568-B.1 is 5 meters on each end,
however, Honeywell typically uses up to 10 meters.
Refer to the Fault Tolerant Ethernet (FTE) Specification and
Technical Data EP03-500-200 for details about FTE cable
usage and available Honeywell pre-configured cables.

Cables for ELCN EPLCG Termination Assembly

The following illustration shows installed UEA cable
connections for an ELCN EPLCG pair. Note that EPLCG cabling
will differ according to various customer system configurations.

94
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

FTE Cables
The FTE cables A (yellow) and B (green) connect to the
termination panel of the UEA. The description of the cables is
the same as previously described for the ELCN
Bridge/ENIM/AM/EHB.

EPLCG Port Cables (PORT 1 and PORT 2)

Isolated RS-232 field cables are used for serial communication
with PLCs and communication interfaces.

Configuration Jumper Cable (CONFIG JUMPERS)

Configuration jumper cables are used to reconfigure ELCN
EPLCG for Modicon or Allen-Bradley protocols.

Module Interlink and CEP Redundancy Cable (INTER-LINK)

This cable is used for redundancy communication between
ELCN EPLCGs, and Ethernet communication signals (used for
Experion redundancy).

95
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Overview of UEA Front Panel

UEA Front Panel Indicators

After applying power to the cabinet and UEAs, the PWR
indicator on the UEA front panel illuminates green.
After self-testing completes, the STS indicator illuminates
green.
n PWR - Power LED
n Illuminated (green): Node is turned on and receiving correct
power.
n Not illuminated: Node is off.
n STS - Status LED
n Green: Normal operating state; no “box level” or “application
level” issues.
n Amber: Warning condition exists. The LED remains amber
color as long as the key switch is in the “C” (Config) position
and if the platform block is not loaded from Control Builder.
The warning LED may also occur if the box temperature is
excessive, or when there is an FTE communication issue or
an “application-level” issue.
n Red: Failure condition exists.
n Blue:Indicates that node state is NotConfig or NotLoaded.

Initial Power-up of UEA received from the factory

n A UEA from the factory boots into “Alive” state.
n “BOOT” is the initial Application Name displayed.
n “UEA.xxx.xxx” is the version of the Boot/Recovery (factory)
firmware image.
n The IP Address of 10.0.0.101 is the factory default.
Power applied:

96
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Self-test completed:

Power-up of a previously operational UEA

After the power-up and booting of a previously operational
node, the Application Name and State are displayed. The
Application Name is either ELCN_BRG (for an ELCN Bridge) or
ELCN_NODE (for an ELCN Application Node).
n If there is a running primary UEA, and you power- up the
backup UEA, it boots into the BACKUP state.

n If you power-up both UEAs of a redundant pair, they both

boot into the “Not Loaded” state.

n If you power- up a non- redundant node, it boots into the

“Not Loaded” state.
The “Not Loaded” state indicates that the platform block is not
loaded in Control Builder.

97
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Operating UEA Front Panel

The 5-way button panel provides the user interface for the UEA,
and is described as follows:

n Navigate to menu options by pressing the navigation arrow

buttons, which highlight the next option in the navigated
direction.
n Highlighted items are either a) a selectable command or b)
an editable numeric value.
n Pressing OK on a selectable command will execute that
command.
n Pressing OK on an editable number will enable digit-by-digit
modification, increasing or decreasing the value, using the
up/down navigation arrow buttons. During numeric editing,
the entire multi-digit number remains highlighted, and the
digit being modified will flash.
n Navigate ‘away’ from an edited number by using the
left/right navigation arrow buttons. The edited number is
retained.

UEA Front Panel Display Auto-Dim Feature

After the Application personality firmware is loaded to a UEA,
its front panel display “auto-dim” feature is enabled. The
display automatically un-dims when the UEA Status LED is in a
non-normal state. The bright display allows you determine from
a distance when a given UEA box is in a non-normal state. This
aids in locating a problem UEA, for example when it is mounted
among several UEAs in one or more racks - the non-normal
UEA will be the only one in un-dimmed state. When the UEA is
in a normal state, the display appears as follows:
n The display dims after no user interaction for 10 minutes. It
un-dims upon any user interaction (buttons or key switch).

98
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

n The dimmed display remains readable.

n To maintain LCD health, every 30 minutes the display
undims to 100% brightness and then dims again to 10% of
full brightness to preserve the life of the LCD.

Initial Startup of UEA

Setting the UEA’s FTE Device Index
Each UEA must have a Device Index that is unique in the FTE
community. You enter the Device Index using the UEA box front
panel display by performing the following:
n Configure the FTE Device Index.
n Change the BOOTP setting from NO to YES.
n Save these changes (this reboots the box and the UEA will
get its FTE IP Address from the Experion BOOTP Server.)
Prerequisites
n The UEA hardware is installed in cabinet(s) and:
n Redundant power entries are provided.
n Redundancy cable is connected for each redundant UEA
pair.
n FTE cables are connected.
FTE cables must be connected per the recommended best
practices, otherwise, improper system operation may result.
n LCN MAU cables are connected to existing LCN (ELCN
Bridge only).
n UEA boxes are successfully powered up to the Alive state.
n An ESVT is available with the Base IP address configured
and the “Experion PKS BOOTP Server” Windows service
running.
Rules
n Configure the Device Index on both the primary and
secondary UEA boxes.

99
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

n Configure and save the changes on the intended primary

first, such that it reboots first, acquiring its FTE IP Address
first.

To Set the Device Index Using the UEA Front Panel

Perform the following steps to set the Device Index into the
primary and secondary UEAs. The entry must follow these rules:

ATTENTION: For the intended primary, the Device Index

must be an odd number. For the intended secondary, the
Device Index must be the primary’s Device Index plus 1 (an
even number).

NOTE: Later when you configure the UEA’s platform block,

the Control Builder will assign LCN address 97 to the ELCN
Bridge that has an odd-numbered Device Index, and assign
LCN Address 98 to its redundant partner.

REFERENCE: For information about operating the UEA Front

Panel, refer to section “"Operating UEA Front Panel" on
page 98.”

Step Action Done Ö

1 Begin at the intended primary UEA box, then repeat this

procedure for the intended secondary.
On the UEA front panel, rotate the key clockwise to the C
position.RESULT: The display shows DETAILS, CONFIG,
TEST, and REBOOT options.

NOTE: This procedure begins with the UEA box

booted into the Boot/Recovery (factory default)
personality. appears in the display, as shown in the
following example.

2 Press the right navigation arrow to highlight CONFIG.

100
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Step Action Done Ö

3 Press OK to select CONFIG.RESULT: The display shows

the FTE Index field.

4 Press the down navigation arrow to highlight the value

(101 shown in the example).Press OK to enable editing of
the first digit of the value.RESULT: The digit blinks,
indicating that it is editable.

5 Press the up/down navigation arrows to change the digit

value. Press right/left navigation arrows to enable editing
of the adjacent digit value.After editing the desired digits
(011 shown in the example), press the right or left
navigation arrow buttons until the FTE Index is no longer
highlighted.

6 Press the down navigation arrow to highlight the BOOTP?

(Y) field.

7 Press the left/right navigation arrows as needed to

highlight (Y).Press OK.RESULT: BOOTP?=Y, specifies that
a BOOTP Server exists and is running on an ESVT.

101
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Step Action Done Ö

8 Press the down navigation arrow to navigate down to

(SAVE/RBOOT).
With (SAVE/RBOOT) highlighted, press OK.
RESULT: The changes are saved and the UEA reboots.

9 During reboot, the display shows “Node Rebooting.”

After the node reboots, the display returns to the main

menu.
The status should show “Alive”, because the UEA is still
running the Boot/recovery image.

NOTE:
The STS indicator may illuminate amber.

RESULT: The UEA will now get its FTE IP Address from the
Experion BOOTP Server.

Verify IP Address Assignment:

10 Position the key switch in one of the R positions.

RESULT: The configuration menu is removed, and the FTE

102
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Step Action Done Ö

IP Address and the Device Index show on the display.

NOTE:
FTE IP Address = base IP address + Device Index

Repeat procedure at intended secondary UEA box:

11 For a redundant UEA, perform this same procedure at the

intended secondary UEA box.

Next Step
After the primary and secondary UEA boxes have their FTE IP
Addresses, the next step is to use the Firmware Manager Tool
to load (flash) the firmware of the primary and secondary UEA
boxes. See the section “"Loading UEA Firmware" below”.

Loading UEA Firmware

Overview of UEA Firmware Loading
For the ELCN Bridge and Experion LCN Appliance Nodes
deployed on UEA hardware, you must use the Firmware
Manager Tool to load (flash) the UEA’s firmware. The Firmware
Manager Tool is automatically installed along with the Experion
R501 (or later) software on Experion user interface nodes such
as the ESVT and ES-T.
There are two personality images that you need to load to the
firmware of each UEA that is being deployed:
n Boot/recovery personality image (UEARECOVERY) -
Honeywell loads the boot/recovery image at the factory, but
you may need to update it. The Firmware Manager Tool
indicates if a newer version of a personality image is
available.
n Application personality - specific to the node type
(UEAELCN_BRG or UEAELCN_NODE)

103
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

n UEAELCN_BRG for the ELCN Bridge

n UEAELCN_NODE for the ENIM, AM, EPLCG, EHB and other
ELCN Appliance Nodes
The UEA box from the factory will have only the boot/recovery
firmware image. If a later version of the Boot/Recovery image is
available, you cannot flash it before flashing the Application
image. The Application firmware image (ELCN Bridge or ELCN
Node) must be flashed before updating the Boot/Recovery
image.

NOTE: The TPN/LCN Personality (such as AM, ENIM,

EPLCG, and EHB) is loaded from the HM to the ELCN
Appliance node.This personality is not the same as the UEA
ELCN Personality Image (UEAELCN) which is loaded as
firmware.

Considerations before Loading UEA Firmware

You must have an R501 (or later) Experion Server with the
Firmware Manager Tool available on the server to be able to
load (flash) the firmware of the ELCN Bridge and any UEA
hardware-based ELCN Appliance Nodes. The following rules
apply:
n For an Experion On-Process Migration where you are using
the ELCN Bridge Commissioning Server, this is the server
you could use to flash the firmware.
n For a new or off-process Experion System, install the R501
ESVT first, to be able to flash the ELCN Bridge firmware.
Before loading the UEA firmware, you must have performed the
initial startup of the primary and secondary UEA boxes,
including powering up, entering an FTE Device Index into the
primary and secondary UEA boxes, and acquiring the FTE IP
address for each UEA box from the Experion BOOTP server. The
Firmware Manager Tool will not detect the UEA if it does not
have a correct IP Address.

104
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

NOTE: Firmware flashing fails if the UEA hardware is not in

the ALIVE, READY, or BACKUP state.

REFERENCE: For information on the Firmware Manager Tool,

refer to the Experion Firmware Manager Tool User’s Guide.

TIP: After installing the Firmware Manager Tool, you can

click the Help button to display the user’s guide.

To Load Firmware on a New (non-operational) UEA

Perform the following procedure from an Experion Server that
has the Firmware Manager Tool installed.

ATTENTION: This procedure is only for a non-operational

ELCN Bridge or ELCN Appliance Node. Do not use this
procedure to update the firmware on an operational UEA,
but instead refer to the appropriate procedure
“Skin/Formats/CrossReferencePrintFormat("Updating
Firmware on Operational UEAs" on page 1)”.

ATTENTION: The first time you load firmware on a UEA box,

load the Application personality image before the
Boot/Recovery (UEARECOVERY) personality image. The
Firmware Manager Tool will not overwrite the existing
UEARECOVERY personality image until an Application
personality image (either UEAELCN_BRG or UEAELCN_
NODE, depending on the node type) is present and
available to the UEA.
The first time you load firmware for a new UEA box received
from the factory (or a box that was re-initialized to the
factory state using the FACT command through the UEA
front panel), you must load the Application personality
image (UEAELCN_BRG or UEAELCN_NODE) before
updating the UEARECOVERY personality image.
If you attempt to load the UEARECOVERY personality
image without an Application personality image present,

105
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

the following error message appears in the Firmware

Manager Tool:
Error Response = (1015) Compatibility check fail
For subsequent updates of the firmware for an UEA box,
you may load the personality images in any order.

Done
Step Action
(Ö)
1 To open the Firmware Manager Tool, click Start > Honeywell
Experion Tools > All Honeywell Tools > Firmware Manager.RESULT:
Firmware Manager queries the network and displays the IP
address and Device Index of each UEA.
If the platform block in Control Builder is not yet loaded, the Name
shows “Not Configured” and the Status is “Alive”.
Version status of UEA firmware images (Boot/Recovery and
Application):green – version supported and is the latestblue –
version supported but is not latestred – version not supported

2
Select the checkbox for the UEA to be loaded. Load the
intended primary first (odd-numbered Device Index).

Loading the Application Personality Image

3 Right-click on the UEA, and select

RESULT: The
Select Firmware Version dialog box appears.

4 Click on the Firmware Version (for example, EXP501.1-16.0), and

then click Show Personality.RESULT: The available UEA
personalities are listed.

5 Select the personality that applies to the UEA node type.

Select this personality…For this type of node… UEAELCN_
BRGELCN BridgeUEAELCN_NODEELCN Appliance Node (ENIM,
AM, EPLCG, EHB, and NG)

106
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Done
Step Action
(Ö)

In the following example, UEAELCN_BRG is selected for the ELCN

Bridge node type.

6 After selecting the personality, click Select.RESULT: The Select

Firmware Version dialog box closes.

7 Click Load Firmware.

RESULT: The firmware loads and then the UEA reboots. When the
process completes successfully, the Refresh Completed message
appears in the Status window at the bottom of the display.

The name of the Application personality image that was loaded

(UEAELCN_BRG for an ELCN Bridge) is displayed in the
Personality column and the Application firmware version is
displayed in green text, indicating that the latest version is now
installed.

Loading the Boot/Recovery Personality Image

107
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Done
Step Action
(Ö)
8 The next step is to load the Boot/Recovery personality image.
Right-click on the same UEA, and select Firmware
Version.RESULT: The Select Firmware Version dialog box appears.

9 Click on the Firmware Version (for example, EXP501.1-16.0), and

then click Show Personality.RESULT: The available UEA
personalities are listed.

10 Select UEARECOVERY.

11 After selecting the personality, click Select.RESULT: The Select

Firmware Version dialog box closes.

12 Click Load Firmware.RESULT: The firmware loads and then the

UEA reboots. When the process completes successfully, the
Refresh Completed message appears in the Status window at the
bottom of the display.
As shown in the following example, both personality images are
now loaded to UEA 97 - the version of each personality image is
green, indicating that it is the most recent version available.

To Load Firmware of Redundant Partner

13 For redundant nodes, such as the ELCN Bridge, you must now
load the firmware of the redundant partner.
Select the checkbox of the redundant partner UEA. In the following
example, UEA 98 is selected.

14 After the redundant partner is selected, repeat Steps 2–12.

RESULT: After performing Steps 2-12, the firmware for both
personality images for both redundant partner UEAs is flashed and
the procedure is complete. The following example indicates that
UEA 97 and UEA 98 are at the most recent firmware versions for
the ELCN Bridge.

108
 Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

Done
Step Action
(Ö)

NOTE:
After the UEA firmware is loaded, the “auto-dim” feature is
enabled for the front panel display of the physical UEA box.
Thus, you can expect the display to behave differently after
firmware loading. For details, see the section “UEA Front
Panel Display Auto-Dim Feature”.

Next Step
After loading the firmware, the next step is to configure and
load the platform blocks in Control Builder.
If you are implementing the ELCN Bridge during an Experion
On-Process Migration of Experion pre-R501 to R501 (or later),
then you must configure the ELCN Bridge platform blocks in
Control Builder on the ELCN Bridge Commissioning Server.
Refer to the section Commissioning the "ELCN Bridge during
Experion OPM".
If you are not performing an Experion On-Process Migration,
then you may go directly to the section “"Configuring ELCN
Platform Blocks in Control Builder" on page 111.”
If the ELCN Bridge is already fully operational, and you are
ready to configure the Control Builder blocks for your ELCN
Appliance Nodes, such as the ENIM, AM, EPLCG, EHB, and NG,
continue to the section “"Configuring ELCN Platform Blocks in
Control Builder" on page 111.”

Node flashing procedure for a UEA node coming from

the factory with only the Boot Recovery image
n This condition is only applicable when flashing the Experion
R530.1 (or later) firmware. This modified procedure is
required due to a change in the underlying operating system
introduced in the R530.1 release.

109
Chapter 4 - UEA Hardware Overview and Initial Startup Procedures

n Before installing the Experion R530.1 (or later) release

firmware onto the UEA box, install a pre-R530.1 (ex: R511.5,
R520.2) application personality image that is compatible
with the UEA Boot/Recovery image (UEA_110.1-07.0 or
prior), which is already loaded on the node.
n Refer to the table below for the compatibility matrix.

n Update the Boot/Recovery image to UEA_120.1-01.0 (or

later).
n Update the Application personality image that is compatible
with the Boot/Recovery image.

110
CHAPTER

5 CONFIGURING ELCN PLATFORM BLOCKS IN

CONTROL BUILDER

In this section:

Overview of Experion LCN Platform Blocks in Control

Builder 112
Considerations When Loading ELCN Platform Blocks 113
To Create and Load the ELCN Platform Blocks 114
To Reconfigure an ELCN Appliance Node to be Redundant 131
Renaming ELCN AM Node Block 133

111
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Overview of Experion LCN Platform Blocks in

Control Builder
The primary and secondary ELCN Bridge and each ELCN
Appliance Node (primary if redundant) requires a platform
block for operations and monitoring. The platform block is an
object in the ELCN data organization hierarchy in Control
Builder. It has configuration forms that present the following
properties representing the physical hardware:
n Control Data Access (CDA) parameters, which allow for the
configuration of properties common to supported protocols.
n System operational parameters, allowing for the control of
key behaviors such as redundancy.
n Statistical parameters, allowing for the view of runtime
performance metrics.
You create the platform blocks in the Project tab of Control
Builder. After you enter values for properties and parameters of
a platform block, the configuration exists in the Engineering
Repository Database (ERDB).
In Control Builder, you load the platform block from the Project
side/tab, and then view the online operation from the
Monitoring side/tab. You may make changes to certain
parameters from the Monitoring side, but your changes will not
be entered into the ERDB. To save your changes, configure
them on the Project side and then load them to the Monitoring
side.
An ELCN platform block must be configured in Control Builder
for:
n The primary and secondary ELCN Bridge, and
n Each ELCN Appliance Node (primary and secondary, if
redundant).
When you specify redundancy for the primary ELCN Bridge or a
primary redundant ELCN Appliance Node, then Control Builder
creates a platform block for the secondary also. You must load
the platform block to both the primary and the secondary.

112
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

NOTE: Commissioning the ELCN Bridge during Experion

OPM

Considerations When Loading ELCN Platform

Blocks
If the IP address shown in the block does not match the IP
address of the corresponding UEA hardware, the load fails. If
the IP address cannot be reached, the load fails with an error
indicating that the Control Builder cannot establish connection
with the ELCN Bridge or ELCN Appliance Node.
After a successful load, the block appears in the Control Builder
Monitoring side/tab.
You should load the platform blocks to both the primary and
the secondary, because synchronization alone does not inform
the Control Builder’s Monitoring side of the secondary;
consequently, you are not able to view the online status of the
secondary until you load its block.

ATTENTION: When configuring a redundant pair of ELCN

bridges, it is highly recommended to always load the
platform blocks in Control Builder for both the primary and
the secondary ELCN Bridges. This will provide the best
Experion integration experience.
If only the primary ELCN Bridge platform block is loaded to
the Control Builder Monitoring side, it configures and
activates both the primary and secondary ELCN Bridges.
The secondary ELCN Bridge does not have to be loaded to
the Control Builder Monitoring side in order to activate
redundant operations of the ELCN Bridge pair – loading of
the primary ELCN Bridge activates it.
However, if the secondary ELCN Bridge is not loaded to the
Control Builder Monitoring side, then the platform block
parameters are not accessible from Experion. There is no
indication that the secondary ELCN Bridge is not loaded to
the Control Builder Monitoring side.

113
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

To Create and Load the ELCN Platform Blocks

Step Action

To Create the Platform Blocks in Control Builder

1 In Control Builder, click File> New> ELCN and then click either ELCN_
BRG - ELCN Bridge or ELCN_NODE – ELCN Appliance Node, depending
on the type of block to be configured.

RESULT: The configuration form opens with the Main tab selected.
The following are Main tab examples for the ELCN Bridge, ENIM, AM, and
EHB.
ELCN Bridge configuration form - Main tab:

ENIM configuration form - Main tab:

114
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

AM configuration form - Main tab:

115
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

EHB configuration form – Main tab:

EHB configuration form – Main tab(cont):

116
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

2 Under the Main tab, enter the following:

Tag Name.
(optional) Item Name and Associated Asset
Device Index.
For the ELCN Bridge:
Module is redundant
LCN Node Number (automatically assigned by Control Builder)
For an ELCN Appliance Node:
Module is redundant (if the node is redundant)
Virtual Environment
ELCN Node Type
LCN Node Number –This
LCN Node Number – Partner (if the node is redundant)
UCN Node Number (ENIM only)

ATTENTION: There are important recommendations and

precautions related to certain configuration entries. Refer to the
following section for instructions on entering the required
configuration: Skin/Formats/CrossReferencePrintFormat("Control
Builder ELCN Platform Block Parameter Descriptions" on page 1)

NOTE: You may choose to change other parameters, or leave them

at their default values.

TIP: If needed, press F1 to access Help for each parameter in the

configuration form.

3 After configuring the parameters, click OK to accept the changes.

RESULT: The blocks are entered into the ERDB. The Tag Names and
icons appear on the Project side/tab, ready for loading. The following

117
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

example shows the icons for a redundant pair of ELCN Bridges.

To Load the Platform Blocks in Control Builder

Prerequisites: To perform the initial load of platform blocks for the ELCN Bridge
and ELCN Appliance Nodes, the firmware must have been loaded to the primary and
secondary UEAs, their Device Index numbers must have been entered at the
physical hardware box, and their FTE IP Addresses must have been acquired.

4 On the Project tree of Control Builder, select the block(s) to be loaded.

ATTENTION: If the block is redundant, Ctrl/Select both the primary

and secondary blocks.

RESULT: The selected block(s) are highlighted. In the following example

both the primary and secondary ELCN Bridge blocks are selected.

118
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

5
Right-click and then select Load, or click the green down arrow on
the Control Builder toolbar.

119
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

RESULT: The Load Operation dialog box appears as shown below.

120
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

NOTE: The Options checkboxes and the warning message at the

bottom of the screen, do not apply to the ELCN Bridge.

6 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to the primary and
secondary. The secondary then synchronizes with the primary. The
operation of the ELCN Bridge or ELCN Appliance Node is activated.
The icons in the Control Builder Monitoring side reflect the current state
of the primary and secondary.
The following example shows the icons for the primary and secondary
ELCN Bridges.

121
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

7 To view the status of the synchronization that occurs between the primary
and secondary, select the primary or secondary block in the Control
Builder Monitoring tree and then click the Redundancy tab of the form.
RESULT:In the Redundancy tab, Initial Sync Progress (%) indicates
percent of completion. In the Main tab of the form, after synchronization
completes, the Synchronization State is SYNCMAINT.

ATTENTION: For a redundant pair of ELCN Appliance Nodes, if you

select and load only the Primary platform block in Control Builder,
be aware that both the Primary and the Backup will transition to
the PWR_ON state in the Native Window upon Primary load
(provided the backup hardware is available with the Redundancy
cable connected). Since you did not load the Backup along with the
Primary, you will now need to select and load the Backup’s Control
Builder block.

ATTENTION: If you enter an invalid LCN Node Number (not

configured in NCF, or already in use by a different running LCN
node) and then load the block in Control Builder, the block loads,

122
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

but the node status remains in the “Not Loaded” state. The
following displays will indicate the “Not Loaded” state along with
the invalid LCN Node Number: UEA front panel display, Control
Builder Main tab, and Experion Detail Display/Faceplate.
To fix this, you must enter a valid LCN Node Number and reload
the platform block in Control Builder.

Next Step
ELCN Bridge - After loading the Primary and Secondary ELCN
Bridge platform blocks in Control Builder, the next step is to
verify the operation. For instructions, refer to the section
“"Verifying Operation of Experion LCN" on page 369”.
ELCN Appliance Node - After loading the ELCN Appliance Node
platform block(s) in Control Builder, the node is ready for
loading of its TPN Personality and Checkpoint file.
REFERENCE: For instructions, refer to the “Node Loading
Procedures” section of the Process Operations Manual in the
TPN/LCN PDF collection.
After loading the TPN Personality and Checkpoint file, the next
step is to verify the ELCN Appliance Node operation. For
instructions, refer to the section “"Verifying Operation of
Experion LCN" on page 369”.

Control Builder ELCN Platform Block Parameter

Descriptions
The following table describes the key ELCN platform block
parameters that must be considered in Control Builder for the
ELCN Bridge and ELCN Nodes.

Item Description

Tag Name The block is automatically assigned a

unique default tag name when it is
created:
ELCN Bridge Default: ELCN_BRG

123
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

<random number>
ELCN Appliance Node Default:
ELCN_NODE <random number>
Honeywell recommends that you
enter a unique identification that is
meaningful to you and that follows
your network naming conventions.

Associated Asset Optional. Select an Asset from those

configured in the Enterprise Model
Database to set the scope of
responsibility for this Tag Name.

Device Index Enter the unique FTE Device Index.

(DEVICEIDX) It should always be an odd number
for the intended primary. Control
Builder automatically assigns the
next even number to the secondary
(the primary’s Device Index plus 1).
The Device Index numbers in Control
Builder must match the numbers
that were entered at the physical
primary and secondary UEA boxes.

l If they do not match, then when

you attempt to load the primary
and secondary blocks, the load
fails.
l If they do match, then upon a
successful load, the Device Index
becomes Read Only, and no
changes to the Device Index will
be allowed from Control Builder.

NOTE: Non-redundant
appliance nodes (for example,
AM or NG) must have an odd-
numbered Device Index.

Module is redundant ELCN Bridge: Select the checkbox for

124
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

(MODISREDUN) the ELCN Bridge - Honeywell

requires that the ELCN Bridge be
redundant.
ELCN Appliance Node: Select the
checkbox if the node is redundant.
NGs are always non-redundant.
RESPONSIBLENG and
ALTERNATENG are not redundant
like other node types such as, ENIM,
AM, EPLCG, or EHB.

NOTE: The Device Index and

LCN Node Number are
incremented by one (1) for the
backup. The IP Address does
not need to be incremented by
one (1) for the backup.

If you deploy a non-redundant ELCN

Appliance Node and then in the
future determine that you need to
make it redundant, you cannot
reconfigure the node from Control
Builder while the node is running –
you must shut down the node from
the Native Window.REFERENCE: For
details, see “To reconfigure an ELCN
Appliance Node to be redundant.”

Secondary Tag Name The secondary is automatically

assigned the Tag Name of the
(SECMODNAME) primary followed by the abbreviation
SEC. The Secondary Tag Name is
Read Only.
Default: <tagname of primary>SEC

LCN Bridge Node Number ELCN Bridge Only: By default,

Control Builder assigns LCN
(ELCNBNUM) addresses 97 and 98 to the ELCN
Bridge redundant pair – these

125
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

addresses cannot be changed.

Control Builder assigns LCN address
97 to the ELCN Bridge that has an
odd-numbered Device Index, and
assigns LCN Address 98 to its
redundant partner.

ELCN Multicast Address Default: 234.129.239.100

(ELCNMULTIIPADDRSTR) The Secondary contains the same
value as the Primary.
Honeywell strongly recommends that
you use the default ELCN Multicast
IP Address and not change it unless
you are familiar with the use of the IP
Multicast Protocol.
The ELCN Multicast IP Address must
match on the ELCN Bridge and all
ELCN Nodes on this network,
including Control Builder block
configuration of ELCN Appliance
Nodes (such as ENIM, AM, EPLCG,
and EHB) and the Board0
configuration of Microsoft Windows-
based TPS Nodes (ES-T, ESVT, ACE-
T, and E-APP) in order for them to
communicate.
If you decide to change this value
from the default, then you will need
to change the value on the ELCN
Bridge and every ELCN Node.
After the ELCN Bridges and ELCN
Nodes are running, any changes to
the ELCN Multicast IP Address
should not be done on-process.
Consult Honeywell or your personnel
familiar with the use of the IP
Multicast Protocol and Honeywell
Fault Tolerant Ethernet to determine
the repercussions of changing the
ELCN Multicast IP Address.

126
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

Virtual Environment ELCN Appliance Node only: This

parameter specifies whether the
node is virtual.

l OFF – Physical node

l ON – Virtual node

ELCN Node Type ELCN Appliance Node: Select the

node type. For example, ENIM, AM,
(ELCNNODETYPE) EPLCG,, EHB, or NG

LCN Node Number-This ELCN Appliance Node: Enter the LCN

node number of the primary ELCN
(ELCNNODENUM) Node. The secondary platform block
automatically configures this LCN
node number in its “LCN Node
Number – Partner” parameter.

When assigning or changing the LCN

node number of any LCN or ELCN
node, it is imperative that the
intended node number is not already
in use by another LCN or ELCN node.
If you cause a duplicate node
number situation to occur, the invalid
duplicate node fails, and the existing
running node may become
ISOLATED from some LCN and ELCN
nodes. To recover from this situation,
power-off the node with the invalid
address, change its LCN node
number to an unused LCN address,
power it back on, and reload the
existing running node that may have
become ISOLATED. To load an
ISOLATED ELCN Node, first shut
down the node (using System Status
display in Native Window) and then
load the node.

LCN Node Number-Partner ELCN Appliance Node: Enter the LCN

127
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

(ELCNNODENUMPARTNER) node number of the backup ELCN

Node. The secondary platform block
automatically configures this LCN
node number in its “LCN Node
Number – This” parameter.
This node number does not have to
be odd or consecutive. For example, a
valid LCN node number for the
primary ENIM can be 24 and a valid
LCN node number for the secondary
ENIM can be 30.
When assigning or changing an LCN
node number of any LCN or ELCN
node, it is imperative that the
intended node number is not already
in use by another LCN or ELCN node.

ENIM UCN Node Number ENIM Only - Enter the UCN node
number of the primary ENIM (such
(UCNNODENUM) as 1, 3, 5 or 7).

Experion PKS Migration Mode Enabled ELCN Bridge Only

(EPKSMIGRATIONMODE) This parameter is used only during
an Experion On-Process Migration
when migrating from an Experion
Release prior to R501 to an Experion
Release of R501 (or later).This
parameter is necessary for the initial
installation of the ELCN Bridge and
only during an Experion On-Process
Migration.
As long as the Experion Migration
Mode Enabled checkbox remains
checked, you can delete the ELCN
Bridge platform blocks in Control
Builder from the “ELCN Bridge
Commissioning Server” without
affecting the running state
functionality of the ELCN Bridge(s).
This parameter is

128
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

l Writeable only at ELCN Bridge

platform block build time in
Control Builder.
l Read Only after loading to the
Control Builder Monitoring side.
l Visible only on the primary ELCN
Bridge platform block in Control
Builder.
l Not Visible on the Experion Detail
Display of either the Primary or
Secondary ELCN Bridge.
REFERENCE: For instructions on
how to use this parameter under the
circumstances described, see section
"Commissioning the ELCN Bridge
during Experion OPM".

NOTE: The Secondary ELCN

Bridge platform block in
Control Builder does not show
this parameter. It is
automatically synchronized
and configured from the value
in the Primary block.

Define Physical Gateway Emulation Classic EHB and ELCN-EHB only:

Define Physical Gateway emulation
(DFNPHWYEM)

Hiway Number Classic EHB and ELCN-EHB only:

This parameter specifies the number
(HWYNUM) by which the Hiway box is known on
the LCN.

Hiway Number Partner Classic EHB and ELCN-EHB only:

This parameter specifies the logical
(HWYNUMPRT) Hiway number of the EHB, if any,

129
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

which is connected to the same LCN

under the same Experion Server
cluster and which had been
connected to the same physical
Hiway through a partner HG. This is
an LCN-local number which is not
globally unique. When DFNPHWYEM
is set to OFF, HWYNUMPRT remains
unconfigured in the form. Instead,
when the EHB platform block is
loaded, it is populated automatically
based on the partner EHB indicated
by the HWYNUM parameter.

PHWYPRTLC Classic EHB and ELCN-EHB only;

Tag name of the one other EHB
connected to same Server cluster, the
same LCN, and formerly the same
Hiway.

PHWYPRTLCIP Classic EHB and ELCN-EHB only:

Local Partner IP Address.

Enable OPM to LCN ELCN-EHB only: This parameter

enables the backward migration from
(ENABLEOPMTOLCN) ELCN EHB to Classic EHB. Control
Builder does not allow the
deconfiguration or deletion of a
platform block when the device is
running. This parameter enables the
deconfiguration of the ELCN_NODE
(EHB) platform block from Control
Builder.

Enable OPM to ELCN Classic EHB only: This parameter

enables the OPM from Classic EHB
(ENABLEOPMTOELCN) to ELCN EHB. Control Builder does
not allow the deconfiguration or
deletion of a platform block when the
device is running. This parameter
enables the deconfiguration of the
classic EHB platform block from
Control Builder.

EHB Node Number ELCN-EHB only: This is the EHB

130
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Item Description

(EHBHWYNUM) address on the Data Hiway network.

To Reconfigure an ELCN Appliance Node to be

Redundant
If you deploy a non-redundant ELCN Appliance Node, then
afterwards you need to make it redundant, you cannot
reconfigure the node from Control Builder while the node is
running – you must SHUT DOWN the node from the Native
Window.
Perform the following procedure to configure a running non-
redundant ELCN Appliance Node as a redundant node.

Step Action

1 From the Native Window, SHUT DOWN the

node.

2 From the Monitoring side of Control Builder,

delete the existing Control Builder block.

3 From the Project side of Control Builder, go to

the Main tab and perform the following:

1. Select the Module is redundant checkbox

to configure the node as redundant.
2. Enter the LCN node numbers for both
Primary and Secondary in these fields:
LCN Node Number – ThisLCN Node
Number – Partner
When assigning or changing the LCN node
number of any LCN or ELCN node, it is
imperative that the intended node number is
not already in use by another LCN or ELCN
node.
If you cause a duplicate node number
situation to occur, the invalid duplicate node
fails, and the existing running node may
become ISOLATED from some LCN and

131
Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Step Action

ELCN nodes. To recover from this situation,

power-off the node with the invalid address,
change its LCN node number to an unused
LCN address, power it back on, and reload the
existing running node that may have become
ISOLATED. To load an ISOLATED ELCN Node,
first shut down the node (using System
Status display in Native Window) and then
load the node.

4 Select and Load the Primary and Secondary

platform blocks in Control Builder.

5 From the Native Window, LOAD the Primary

and Secondary nodes.

132
 Chapter 5 - Configuring ELCN Platform Blocks in Control Builder

Renaming ELCN AM Node Block

To Rename the CEE for the ELCN AM node block and ensure its
normal operation, the following steps should be followed:
1. Shut down the AM from the Native Window interface.
2. Delete the ELCN AM platform from the monitoring tab.
3. Rename the CEE for the ELCN AM in the project tab.
4. Download the updated ELCN AM block from the project tab.
5. Reload the ELCN AM from the Native Window.

NOTE: If the ELCN AM's CEE already contains points, all of

them must be deleted before proceeding with renaming the
CEE as per the steps mentioned above.

133
CHAPTER

6 COMMISSIONING THE ELCN BRIDGE

DURING EXPERION OPM

In this section:

Overview of the ELCN Bridge Commissioning Server 135

To Commission ELCN Bridge Using Commissioning Server 138

134
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Overview of the ELCN Bridge Commissioning

Server
ATTENTION: The ELCN Bridge Commissioning Server is
needed only when migrating from Experion pre-R501 to
R501 (or later). There is no need for the ELCN Bridge
Commissioning Server if you are migrating from Experion
R501 or later to a newer release.

ATTENTION: Only load ELCN Bridge blocks. Appliance

nodes must not be migrated during Experion OPM.

If you are planning to implement the ELCN Bridge during an

Experion On-Process Migration (OPM) of your existing
Experion System, then you must install an additional, separate
R501 Experion Server to “commission” the ELCN Bridges and
then monitor them during the Experion On-Process Migration.
“Commissioning” the primary and secondary ELCN Bridges
involves loading firmware and then configuring and loading
platform blocks in Control Builder.

ATTENTION: Prior to R520.1, the FTE community

information was configured in the control builder.
From Experion R520.1
When Firmware Manager and CTools fail to discover the L1
devices, perform the following steps:
1. Create and configure FTE community in configuration
studio similar to the production system.
2. Load the network configuration to servers.
3. Open Control Builder after loading the network
configuration to servers.
4. Perform the above steps would replicate the details of
ERDB.
Refer section " Adding FTE communities to the Network tree"
in the Server and Client Configuration Guide, for more
details.

135
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

The ELCN Bridge Commissioning Server is a temporary, non-

redundant R501 Experion Server (ESV or ESVT) that you need
to install before starting the On-Process Migration of your
existing Experion System. The ELCN Bridge Commissioning
Server does not communicate with the existing Experion
System (for example, through Distributed System Architecture
[DSA]) - it remains separate.
The ELCN Bridge Commissioning Server can be on a physical
platform or a virtual platform. The ELCN Bridge Commissioning
Server should use the same Experion software license as the
main Experion Server. When installing the R501 Experion
software for the ELCN Bridge Commissioning Server, there is
no need to specify the ELCN Auxiliary Network.

NOTE: In the context of the procedure to commission the

ELCN Bridges, the “Main Backup” ESVT is the backup of
the redundant pair of ESVTs, where your Engineering
Repository Database (ERDB), System Repository (SR), and
Enterprise Model Database (EMD) are located for your
Experion System controllers and Experion Stations.

The following table summarizes the steps to commission the

ELCN Bridge using the ELCN Bridge Commissioning Server.
REFERENCE: For the detailed procedure to commission the
ELCN Bridges during Experion OPM, refer to section “"To
Commission ELCN Bridge Using Commissioning Server" on
page 138”.

Summary of steps to commission the ELCN Bridges using the ELCN Bridge
Commissioning Server
1 Install ELCN Bridge Commissioning Server.

2 Install and configure the ELCN Bridge UEA.

The configuration includes the following:
Enter Device Index and obtain IP Address of
primary and secondary ELCN Bridges.
Load firmware of primary and secondary
ELCN Bridges.

136
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Summary of steps to commission the ELCN Bridges using the ELCN Bridge
Commissioning Server
3 Check the Experion Migration Mode Enabled
checkbox for the primary ELCN Bridge
platform block in Control Builder.
Configure and Load platform blocks in
Control Builder for primary and secondary
ELCN Bridges.
The ELCN Bridge platform blocks will be the
ONLY blocks built in Control Builder on the
ELCN Bridge Commissioning Server.

4 Migrate the Main Backup ESVT.

The migration causes this server’s ERDB to
become locked, due to Dual Primary Mode,
where this ESVT has been migrated and is
operating with the new release ((R501or
later), and its redundant partner server is
operating with the base release.

5 Complete the R501 Experion On-Process

Migration (ES-T, ACE-T, E-APP, and main
primary ESVT).

6 After the Experion system is fully migrated to

the new Experion release, and is no longer in
Dual-Primary Mode, then you must delete the
ELCN Bridge platform blocks in Control
Builder from the ELCN Bridge
Commissioning Server and add the blocks to
the main primary R501 ESVT Control Builder.
After you delete the ELCN Bridge platform
blocks in Control Builder on the ELCN Bridge
Commissioning Server, limitations (including
suspension of CDA) will exist until you load
the blocks on the main primary ESVT.
To reduce the amount of time that CDA is
suspended, you should efficiently delete, and
then quickly reload the blocks, by performing
the following sequence:
Configure, but DO NOT LOAD, ELCN Bridge
platform blocks in Control Builder on the fully

137
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Summary of steps to commission the ELCN Bridges using the ELCN Bridge
Commissioning Server
migrated Main Primary ESVT. Have the
blocks created and waiting in the Control
Builder Project tree of the main primary ESVT
– ensuring that the configuration is identical
to the ELCN Bridge Commissioning Server
EXCEPT the checkbox for Experion Migration
Mode should be unchecked.
When it is time to delete the blocks from the
Monitoring side of Control Builder on the
ELCN Bridge Commissioning Server, delete
them and then, as quickly as possible, load
the blocks in Control Builder on the main
primary ESVT. Honeywell suggests
accomplishing this move within 30 seconds.

To Commission ELCN Bridge Using

Commissioning Server
The following steps describe how to commission the ELCN
Bridge using the ELCN Bridge Commissioning Server.

ATTENTION: The ELCN Bridge Commissioning Server is

needed only when migrating from Experion pre-R501 to
R501 (or later). There is no need for the ELCN Bridge
Commissioning Server if you are migrating from R501 or
later to a newer release.

Location Step Action Done

Install ELCN Bridge Commissioning Server

ELCN Bridge 1 Install an R501 (or later) Experion Server to be the

Commissioning ELCN Bridge Commissioning Server. It must have the
Server following configuration:

l Choose a Device Index that will give the server a

unique IP Address in the same FTE Community
address range as the main Experion Server.

138
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

l Configure all of the “Embedded FTE” System

Preferences in Network Configuration(for example,
Base IP Address) to be the same as the main
Experion Server.See R520 Server and Client
Configuration Guide EPDOC-X127-en for more
information on “Adding FTE communities to the
Network tree.
l Stop the “Experion PKS BOOTP Server” Windows
service, and then change its “Startup type” to
Disabled.
l Configure Flex Station, so that you will be able to
view the ELCN Bridge alarms and operation.

Enter Device Index and obtain IP Address of primary and

secondary ELCN Bridges

ELCN Bridge 2a At the physical UEA box of the

physical UEA intended primary ELCN Bridge,
boxes enter its FTE Device Index.
For the procedure, see section
"Setting the UEA’s FTE Device
Index".
RESULT: UEA box has an FTE
Device Index and an IP Address.

2b At the physical UEA box of the

intended secondary ELCN Bridge,
enter its FTE Device Index.
For the procedure, see section
"Setting the UEA’s FTE Device
Index".
RESULT: UEA box has an FTE
Device Index and an IP Address.

Load firmware of primary and secondary ELCN Bridges

ELCN Bridge 3 At the ELCN Bridge

Commissioning Commissioning Server, use the
Server Firmware Manager Tool to load
both of the ELCN Bridge
personality images to the firmware

139
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

of the UEA that has the odd-

numbered Device Index (intended
primary) and the UEA that has the
even-numbered Device Index
(intended secondary).
For the procedure, see section
"Loading UEA Firmware".
RESULT: The UEA boxes reboot
and their front panel display shows
“NotLoaded”.

Configure and Load platform blocks in Control Builder for primary

and secondary ELCN Bridges

ATTENTION: Only load ELCN Bridge blocks. Appliance nodes must not be
migrated during Experion OPM.

ELCN Bridge 4a Go to the Control Builder

Commissioning connected to the ELCN Bridge
Server Commissioning Server.

4b Choose New> ELCN> ELCN_BRG – ELCN Bridge as

the block type.

4c On the Main tab of the

configuration form, configure the
following:
If desired, change the Tag Name.
If desired, select an Associated
Asset.
Enter the Device Index.
Check the Module is redundant
checkbox.
If desired, change the ELCN

140
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

Multicast Address, however,

Honeywell strongly recommends
you use the default of
234.129.239.100.
Most importantly, check the
Experion Migration Mode Enabled
checkbox.
Leave everything else at the
default value.
REFERENCE: For configuration
details, see "To Create and Load
the ELCN Platform Blocks".
For parameter definitions, see
section "Control Builder ELCN
Platform Block Parameter
Descriptions".

4d Click OK.
RESULT: The block configuration
enters into the ERDB of the ELCN
Bridge Commissioning Server. The
icons for the primary and
secondary blocks are shown in the
Project tree and the blocks are
ready for loading.

4e To load the platform blocks for the

ELCN Bridge, Ctrl/select both the
primary and secondary blocks in
the Project tree.

141
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

RESULT: The selected block(s) are

highlighted.

Right-click and then select Load in

the drop-down list, or click the
green down arrow on the Control
Builder toolbar.

RESULT: The Load Operation

screen appears.

4f Click Load to confirm the

operation.
RESULT: Control Builder loads the
blocks to the primary and
secondary ELCN Bridges. The
secondary synchronizes with the
primary. The ELCN Bridge
operation is fully activated and
operational.
The icons in the Control Builder
Monitoring tree reflect the current
state.

142
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

The “Experion Migration Mode

Enabled” parameter is grayed out,
signifying that it is Read Only and
not changeable by the user after
the ELCN Bridge platform blocks
have been loaded in Control
Builder.
View of the primary block:

View of the secondary block:

ELCN Bridge 5 From Flex Station, you may invoke

Commissioning the Experion Detail Display and the
Server Experion System Status display to
monitor any ELCN Bridge system
alarms.
Migration Mode Indicator:
When the “Experion Migration
Mode Enabled”
(EPKSMIGRATIONMODE)
parameter is TRUE (checked), and
the platform blocks are loaded in
Control Builder, the ELCN Bridges
have an “(M)” appended to their
Application State. This indicates to
you that the ELCN Bridges have
the Experion Migration Mode
Enabled.
The Faceplate shows (M) next to
the state.
The Detail Display Main tab

143
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

contains a replica of the UEA Front

Panel Display – it shows (M) next
to the state.

UEA Front Panel UEA Front

Display of Primary: Panel
Display of
Secondary:

This (M) (Migration Mode Enabled)

indication will be significant later,
after you delete the ELCN Bridge
platform blocks in Control Builder
on the ELCN Bridge
Commissioning Server (Step 9) and
before you load them to the Main
Primary Experion Server (Step 10).
In that brief period between those
two operations, the (M) indicates to
users that the ELCN Bridges are
running and operational,
performing their bridging
functions.

Migrate the Main Backup ESVT

Main Backup 6a Migrate the Main Backup Experion

Experion Server Server to Experion R501 (or later).
– TPS (ESVT) Select ELCN as the Auxiliary
Network Selection.

144
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

Main Backup 6b After migrating the Experion Server

Experion Server software, configure the TPN side as
– TPS (ESVT) follows:

1. Enter the LCN node number.

When assigning or changing the
LCN node number of any LCN
or ELCN node, it is imperative
that the intended node number
is not already in use by another
LCN or ELCN node.
If you cause a duplicate node
number situation to occur, the
invalid duplicate node fails, and
the existing running node may
become ISOLATED from some
LCN and ELCN nodes. To
recover from this situation,
power-off the node with the
invalid address, change its LCN
node number to an unused LCN
address, power it back on, and
reload the existing running node
that may have become
ISOLATED. To load an
ISOLATED ELCN Node, first
shut down the node (using
System Status display in Native
Window) and then load the
node.
2. Enter the Multicast IP Address
that matches the one configured
for the ELCN Bridge.
3. Install the APP Personality (if
not already).

145
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

REFERENCE: For details, refer to

the Experion PKS Integrated
Experion-TPS User's Guide.
RESULT: The migration causes this
server’s ERDB to become locked,
due to Dual Primary Mode, where
this ESVT has been migrated and is
operating with the new release, and
its redundant partner server is
operating with the base release.

Complete the Experion On-Process Migration

Experion System 7a
NOTE: Migrate the Experion
TPS nodes (ES-T, ACE-T, and
E-APP) to R501 (or later)
ELCN, one at a time,
according to node migration
best practices.

NOTE: You must add all

Windows-based ELCN
Experion TPS nodes to a
Windows Domain. For
information on adding nodes
to a Windows Domain, see
section “Adding a node to a
Windows domain” in the
Windows Domain
Implementation Guide for
Windows Server 2016.

For each of the TPS nodes (ES-T,

ACE-T, E-APP) perform these
additional configuration steps:

1. Enter the LCN node number.

vdvgdb

146
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

When assigning or changing the

LCN node number of any LCN
or ELCN node, it is imperative
that the intended node number
is not already in use by another
LCN or ELCN node.
If you cause a duplicate node
number situation to occur, the
invalid duplicate node fails, and
the existing running node may
become ISOLATED from some
LCN and ELCN nodes. To
recover from this situation,
power-off the node with the
invalid address, change its LCN
node number to an unused LCN
address, power it back on, and
reload the existing running node
that may have become
ISOLATED. To load an
ISOLATED ELCN Node, first
shut down the node (using
System Status display in Native
Window) and then load the
node.

2. Enter the Multicast IP Address

that matches the one configured
for the ELCN Bridge.
3. Install the APP Personality (if
not already).
REFERENCE: For details, refer to
the Integrated Experion-TPS User's
Guide.
Use the Node Configuration Utility
to configure the ELCN node:

1. Launch the TPS Node

Configuration Utility. Click Start
> Honeywell Experion Tools > All
Honeywell Tools > System

147
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

Management and click TPS

Configuration Utility.
2. Open the Board 0 page
(Configuration Utility > Board 0)
and on the LCNP tab, provide
the following details:
1. LCN Address: Unique address
within the network and must not
be a duplicate.
2. LCN Name
3. ELCN Multicast IP: This must
match the one provided on the
ELCN Bridge.
4. NG name
5. Select the Enable Auto Restart
check box. This setting
determines if the ELCN node
will boot automatically in case of
a machine restart or a TDC
Emulatorsservice restart.
6. Personality is displayed and is
non-editable.
Shown below is a screenshot of the
ES-T node. For others nodes you
are configuring (ACE-T, E-APP) you
will see a similar screen.

After the configuration is complete,

restart the computer.

7b Migrate the remaining Main

Primary ESVT to Experion R501 (or
later).

148
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

NOTE: You must add this

node to the same Windows
Domain to which you had
added the ELCN Experion
TPS nodes in Step 7a. For
information on adding nodes
to a Windows Domain, see
section “Adding a node to a
Windows domain” in the
Windows Domain
Implementation Guide for
Windows Server 2016.

7c Complete your Experion On-

Process Migration.

Configure ELCN Bridge Platform Blocks in Control Builder on Main

Primary Experion Server

Main Primary 8a Connect Control Builder to the

(fully migrated Main Primary (and fully migrated
to ELCN) to ELCN) ESVT.
Experion Server
– TPS (ESVT)

8b Configure, but DO NOT LOAD, the

primary and secondary ELCN
Bridge platform blocks in Control
Builder.
Ensure that the configuration of
the ELCN Bridge platform blocks in
Control Builder on the Main
Primary Experion Server is the
same as the configuration of the
blocks in Control Builder on the
ELCN Bridge Commissioning
Server – especially the ELCN
Multicast IP Address.
Leave the checkbox unchecked for

149
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

Experion Migration Mode Enabled

– the default is unchecked
(EPKSMIGRATIONMODE
parameter is FALSE).Click OK to
enter your configuration.RESULT:
Control Builder enters the blocks
into the ERDB of the main
Experion Server on the Project side
of Control Builder.

ATTENTION: The next step requires that you delete the ELCN Bridge platform
blocks in Control Builder on the ELCN Bridge Commissioning Server. After
you delete the blocks, the following limitations exist until you load the blocks
on the Main Primary (and fully migrated to ELCN) ESVT:
l ELCN Bridge functionality that requires CDA (Control Data Access)
suspends.
l There is no view to the Detail Displays or the Control Builder Monitoring
side.
l ELCN Bridge Redundancy is not supported.

If the checkbox is checked for Experion Migration Mode Enabled on the Project side
of Control Builder, you can delete the blocks from the Monitoring side without
affecting the running state functionality of the ELCN Bridges. You can verify that
the ELCN Bridges are still running and operational by looking at their front panel
displays at the physical UEA boxes.
Primary ELCN Bridge:

Secondary ELCN Bridge:

It is important to minimize the time between when the blocks are deleted from the

150
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

ELCN Bridge Commissioning Server and when they are moved to the Main Primary
(and fully migrated to ELCN) ESVT. It should take no longer than 30 seconds,
otherwise there is a risk of switch over of Primary to Secondary.

Delete ELCN Bridge Platform Blocks in Control Builder on ELCN Bridge

Commissioning Server

ELCN Bridge 9a Go to the Control Builder

Commissioning connected to the ELCN Bridge
Server Commissioning Server to delete
the ELCN Bridge blocks.

9b From the Monitoring tab of Control

Builder, right-click the primary
ELCN Bridge block and select
“Delete…”. RESULT: You receive a
warning dialog box.

9c This warning message does not

apply to the ELCN Bridge
procedure. Click Continue.

RESULT: You receive a

confirmation dialog box.

9d To confirm the operation, click

Delete Selected objects(s).

RESULT: The blocks are deleted

from the Control Builder
Monitoring tree. The ELCN Bridges
are still performing the bridging
functionality

ATTENTION: Perform the next step as soon as possible

Load ELCN Bridge Platform Blocks in Control Builder on Main ESVT

151
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

Main Primary 10a Go to the Control Builder

and fully connected to the Main Primary
migrated to (and fully migrated to ELCN) ESVT.
ELCN) Experion
Server – TPS 10b To load the ELCN Bridge blocks
(ESVT) that you previously created, select
both the primary and secondary
blocks in the Project tree

Right-click and then select Load in

the drop-down list, or click the
green down arrow on the Control
Builder toolbar.RESULT: The Load
Operation screen appears.

10c Click Load to confirm the

operation.

RESULT: The blocks are loaded to

the Control Builder Monitoring tree
of the Main Primary ESVT. The
moving of the ELCN Bridge
platform blocks is now
complete.“ELCN Migration Mode
Enabled” was not enabled (it was
left in the default state of
unchecked), so the Application
States of the primary and
secondary blocks are OK and

152
Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

BACKUP, respectively. Note that

the migration mode (M) indicator is
not present.
View of Primary ELCN Bridge:

View of Secondary ELCN Bridge:

ELCN Bridge 11 RESULT: The ELCN Bridges are

Commissioning fully implemented. The ELCN
Server Bridge Commissioning Server is no
longer needed and can be shut
down and removed from the
network.

After the ELCN Bridges are fully implemented, the ELCN Bridge Commissioning
Server and the “Experion Migration Mode Enabled” checkbox and are no longer
needed. The checkbox should remain unchecked (off). For future software upgrades
of Experion (for example R501 to R510), the normal Experion on-process migration
(that is, Dual Primary Mode) will be used to migrate the ELCN Bridge platform
blocks in Control Builder. At that time, the “Experion Migration Mode Enabled”
checkbox should remain unchecked (off).

Migrating nodes 12 You can now proceed with the

to UEA-based following migrations:
ELCN AM and
l HM to ELCN- HM, see section
ENIM
“Migration from HM to ELCN-
HM”.
l Classic AM to UEA-based ELCN-
AM, see section “Migration from
Classic AM to Experion LCN
AM”.
l Classic NIM to UEA- based

153
 Chapter 6 - Commissioning the ELCN Bridge during Experion OPM

Location Step Action Done

ELCN- ENIM, see section “Off-

process Migration from Classic
NIM to Experion LCN ENIM”.
l Classic ENIM to UEA- based
ELCN- ENIM, see section “On-
process Migration from Classic
ENIM to Experion LCN ENIM”.
l Classic EPLCG to UEA- based

ELCN- EPLCG, see section

“Migration from Classic EPLCG
to Experion LCN EPLCG”
l Classic EHB to UEA- based
ELCN- EHB, see section
“Migration from Classic EHB to
Experion LCN EHB”.
Note that the term “Classic” refers
to LCN coaxial-based nodes.

154
CHAPTER

7 MIGRATING HM, AM, NIM, ENIM, EPLCG,

AND EHB TO ELCN NODES

In this section:

Migration from HM to ELCN-HM 156

Migration from HM to ELCN-HM with Disk Drive
Synchronization 178
Migration from Classic AM to Experion LCN AM 192
Off-process Migration from Classic NIM to Experion LCN
ENIM 213
On-process Migration from Classic ENIM to Experion LCN
ENIM 230
Migration from Classic EPLCG to Experion LCN EPLCG 259
Migration from Classic EHB to Experion LCN EHB 285
Migration from Classic NG to Experion LCN NG 340
Migration from EAPP to ELCN-EAPP 351
Migrate UEA ELCNNODE to UVA On Process and Vice
Versa 359
Migrate UVA ELCNNODE to UEA On Process 364

155
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

This section provides step-by-step instructions to migrate HM

to ELCN-HM, and Classic AM, ENIM, EPLCG, and EHB nodes to
UEA-based ELCN nodes.

Migration from HM to ELCN-HM

ATTENTION: Beginning with TPN R688.3 and Experion
R501.6, a new feature has been introduced for
synchronizing SBHM disks with emulated disks mounted
on ELCN ES-T. This feature helps optimize SBHM to ELCN
HM migration. For more information, refer section
“Migration from HM to ELCN-HM with Disk
Synchronization”.

ELCN History Module (HM) (ELCN-HM) is a software and data

repository node on ELCN that archives process history and
Journals including Alarms, Operator changes, system
configuration, and system maintenance information.
ELCN-HM is a new type of Experion TPS node deployed (either
physical or virtual) using RAID (redundant array of independent
disks) for the storage subsystem. ELCN-HM runs on the
Microsoft Windows Server 2016 operating system.
For more information about ELCN-HM physical infrastructure
requirements, see the Experion LCN Planning Installation and
Service Guide, ELCN Overview and Implementation Guide and
Experion Software Installation User's Guide.
Virtualization sizing guidelines are the same as those
applicable to E-APP. See the HPS Virtualization Specification
document for more information.

ATTENTION: Migrate the System HM on the network and

then proceed with migrating the Data HM (if any). Migrate
only one HM node to ELCN-HM node at a time.

To install the ELCN-HM Node

Use the Experion installer to install ELCN-HM software on the
selected computers. Installation can be done using the
Experion DVD, ESIS, or removable media.

156
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

See the Experion Software Installation User’s Guide for detailed

steps to launch the installation wizard and perform the
installation.
This procedure provides steps to install the ELCN-HM node
using ESIS.

Step Action Done

1 Launch ESIS and run the Setup.exe.

2 Choose the appropriate installation option.

3 Provide the ESIS User Name and Password. This is to

connect to the machine configured to run as ESIS. Click
Next.

4 Choose the appropriate installation option and click Next.

157
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

5 Provide Operating System and User Account information.

6 Provide Windows Administrator Account and Password and

click Next.

7 Select Network Type as FTE, select No. of Adapters and click

NIC Properties.

8 Provide the FTE configuration – TCP/IP details and click OK.

158
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

9 Provide Multicast IP Address details under FTE

Configuration: Multicast Address, Device Index, UDP Source
Port and click Next.

10 Select ELCN History Module and click Next.

11 Enter Customer Information and click Next.

159
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

12 Select the location to install the software and click Next.

13 Choose Network Type for your EPKS connection and click

Next.

160
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

14 Choose Typical as the EPKS Install Option and click Next.

15 Enter Experion accounts passwords and click Next.

161
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

16 The summary of your selections is displayed. If you are

satisfied with the selections you have made, click Continue to
complete installing the ELCN-HM node. If not, click Back,
modify your options and continue.

RESULT: The HM Node is installed on the computer.

You must now add the Windows-based HM node to the same Windows Domain to
which you had added the ELCN Experion TPS nodes in section “To Commission
ELCN Bridge Using Commissioning Server” (Step 7a). See section “Adding a node to
a Windows domain” in the Windows Domain Implementation Guide for Windows
Server 2016.

162
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Pre-configuration tasks
1. Take full backup for both System HM and/or Data HMs
(whichever you are planning to migrate to ELCN) on the
network. To take a backup of an HM node, see the Customer
Release Guide CRG687 or later.

ATTENTION: Use caution if this is the System HM that

you will upgrade to ELCN-HM. In this case, it is
recommended to take the backup into two storages
devices, such as cartridges or drives.

As the System HM is shut down for upgrade, if the HM is

NOT an SBHM (that is, it is a Type 7 with 2 disks), then you
must make the NCF change to a cartridge and/or emulated
drive which contains the System HM Backup.
Also, it is recommended to prepare a fast-load cartridge to
load other nodes in the network. This is required in the event
of a system disruption, such as a power failure. Once the
required nodes have power reapplied and are ready to be
reloaded, then a “path to the system” can be quickly
restored through the use of the prepared fast-load cartridge.
For information on preparing a fast-load cartridge, see the
section “Fast-Load Feature” in the Engineer’s Reference
Manual.
2. You need ELCN Bridges in place if you have any Classic
coaxial-based nodes. However, if the HM which you are
planning to migrate is the last coax node to migrate, you do
not need the ELCN Bridge.
3. Make sure the existing HM is a SBHM (that is, it is a Type 7
with 2 disks), if not, then an NCF change is mandatory. For
detailed information on making NCF changes, see the
section “On-Line Network Reconfiguration” in the Network
Data Entry document SW11605. Perform the following
procedure to make the NCF change:
a. Select VOLUME CONFIGURATION from the Engineering
Main Menu.
b. Select the HM node you are initializing.
c. Make the following selections from the VOLUME
CONFIGURATION page:

163
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

l NUMBER OF WINCHESTER DISKS: 2

l DISK TYPE/SIZE: 7

d. Increase the volume size and user volumes, if required.

e. If you did modify the Volume Configuration:
l Press CTRL + F1 to run the CHECKER.

l Press CTRL + F2 to perform an INSTALL.

l Press Enter to save Volume Configuration changes.

l Exit VOLUME CONFIGURATION and then re-enter it from

the Engineering Main Menu.

4. Once the System HM/Data HM has been fully backed up,
then shut down the System HM/Data HM:
a. Perform a SHUT DOWN of the node you want to migrate
from the Native Window System Status display. Select the
node and select the SHUT DOWN target and press Enter.
This causes an “orderly” shutdown to the QUALIF state.
b. Shut down the node from the Native Window for the second
time to place it into the FAIL state.

ATTENTION: If the node is not shut down two (2) times

and placed into the "FAIL" state, and then powered
OFF, the LCN will continue to look for that node in the
token for 1 minute and 57 seconds (it takes 1 minute
and 57 seconds before the system will eventually
ISOLATE the node.). During this time, the system is
extremely sluggish (if not placed in the “FAIL” state).

c. Power-off the node by removing power from the HM. This

node is now in the FAIL state as shown on the System
Status Display or Node Status Display.
d. Shut down the node from the Native Window for the third
time to transition from the FAIL state to the OFF state.

164
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

To configure the ELCN-HM Node

ATTENTION: Do not perform these steps until you have

fully backed-up the existing HM and have made your NCF
change (only if migrating a non-SBHM).
Turn the HM off, otherwise you will have duplicate LCN
node addresses, and the system may encounter
unexpected conditions due to messages traversing in both
directions across the ELCN Bridge.

Use instructions in this section to complete the configuration

of the ELCN-HM node. After the configuration is complete,
restart the computer.

Step Action Done

1 Use the HM Node Configuration Utility to configure

the ELCN-HM node.
Launch the TPS Node Configuration Utility. Click
Start > Honeywell Experion Tools > All Honeywell
Tools > System Management and click TPS
Configuration Utility.

2 Open the Board 0 page (Configuration Utility > Board

0) and on the LCNP tab, provide the following details:

l LCN Address: Unique address within the network

and must not be a duplicate.
l LCN Name
l ELCN Multicast IP (must match on the ELCN
Bridge and all Experion LCN Nodes in order for
them to communicate)
l NG name
l Select the Enable LCNP Auto Restart check box.
This setting determines if the ELCN-HM node will
boot automatically in case of a machine restart or
a TDC Emulators service restart.
l Personality is displayed as HM and is non-
editable.

165
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

3 On the Common tab, you will have default options

enabled as shown here for the ELCN-HM node.

ATTENTION: The following step for the Emulated Disks tab is not normally
used for normal operations. This tab is used for maintenance or special
situations.

4 On the Emulated Disks tab, you have options to

configure the location and file name for the .lcn files
which would act as disk drives 2, 3, 4, and 5 on the
ELCN-HM node. By default, these lcn filenames and
location will be set to:

166
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

HM Drive 2: <Program Data

path>\Honeywell\EngineeringData\HMEmulatedDis
ks\sbhm_dev2.lcn
HM Drive 3: <Program Data
path>\Honeywell\EngineeringData\HMEmulatedDis
ks\sbhm_dev3.lcn
HM Drive 4: <Program Data
path>\Honeywell\EngineeringData\HMEmulatedDis
ks\sbhm_dev4.lcn
HM Drive 5: <Program Data
path>\Honeywell\EngineeringData\HMEmulatedDis
ks\sbhm_dev5.lcn
You can edit the file names and set the location
based on your preference.

ATTENTION: Honeywell strongly recommends

you use the default location for the path data.
You can choose the file name appropriately.

ATTENTION: Configuration on this page can be

made only when TDC Emulator service is not
running. Mounting/dismounting of drives will
be disabled when the ELCN- HM node is
running.

167
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: The default files you see when you open

this page to configure the node for the first
time, even before the HM node is running, are
only an indication. The actual files with their
displayed names will be created when the TDC
Emulator service starts.
If you choose to change the file names, you
must create the files using the Create button,
then dismount the files from the respective
drive locations, and then mount the created
files which represent the drives.

ATTENTION: After creating a new file, it is

mandatory to perform HM initialization.You
cannot exit the configuration page without
mounting all 4 drives.HM Drive 2, HM Drive 3,
HM Drive 4 and HM Drive 5 represent the four
HM drives which will now reside in the
Windows address space.

This table describes the available buttons on the

Emulated Disks tab display and the actions you can
perform using them.

168
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Button Description

Mount To mount an emulated disk. The

emulated disk to be mounted must be
included in the Available (Dismounted)
Emulated Disks list. To mount a disk in a
drive that already has an emulated disk
mounted, you must first dismount the
disk before proceeding. See instructions
given under Dismount in this table.

1. Select the available emulated disk to

be mounted from the Available
(Dismounted) Emulated Disks list.
2. Click Mount and select the drive that
you wish to mount. Only those drives
that are not already mounted with an
lcn file will be available for mounting.

ATTENTION: You can also drag an

emulated disk from the available
list to 2, 3, 4, and 5 HM Drives.

The selected emulated disk will now

appear as mounted on the chosen drive.
When you mount a newly created lcn file,
it is mandatory that you perform HM
initialization.

Set Sets the default location where the HM

Path emulated drive files will be located. The
default path is “<Program Data
path>\Honeywell\EngineeringData\HME
mulatedDisks\”.

169
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

This path is changeable. Use this button

to navigate and choose a file with a
different name that you might create.

Dismo Dismounts the lcn files from the

unt respective drives. Click the Dismount
button corresponding to the drive on
which you want to dismount the files.

Create Provides flexibility to choose file

names/paths, which are created
in the chosen location. These
can later be mounted on the
required HM drive location.

ATTENTION: If you create

a new lcn file, you must
perform HM initialization
after mounting it.The size
is fixed at 1795 MB and
is not editable as this size
is fixed for HM drives.The
Allocation and Access
fields are also not
changeable during the
file creation.

170
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Properties Displays file properties when a

file is selected in the Available
(Dismounted) Emulated Disks
list.

Refresh Refreshes the Available

(Dismounted) Emulated Disks
list.

ATTENTION: Mounting or dismounting

emulated disks is done in pairs (2 and 4; 3 and
5). If you choose to mount or dismount an
individual disk, it is mandatory to perform HM
initialization.

Delete Before deleting a mounted

disk, first dismount the disk
before proceeding. Use
instructions provided under
Dismount in this table.
To delete an emulated disk:

1. Select a dismounted
emulated disk from the
Available (Dismounted)
Emulated Disks list.
2. Click Delete. The message,
'Do you want to free the disk
space?' appears.
3. Click:
l Yes to remove the
emulated disk from the
list and physically delete
the file from its storage
location.
l No to remove the

171
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

emulated disk from the

Available (Dismounted)
Emulated Disks list, but
not physically delete the
file from its storage
location.

Restart
5 the computer.

Proceed
6 with procedures in either the “"Post
installation tasks for System HM" below” or “"Post
installation tasks for Data HM" on page 176” section
as appropriate.

Post installation tasks for System HM

Step Action Done

1 Click Start > Honeywell Experion > LCNP Status to launch the
LCNP Status window. The HM node will now be in PWR ON state.

172
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

2 Perform HM Initialization.
Pre-requisites: An ES-T (with Native Window) must be present,
which has access to the emulated disk for the TPN R687.1 (or
later) disk_&z1.lcn media, as well the HM Node Backup Disk (for
the NCF).

1. Mount the System HM Backup file and disk_&z1.lcn file:

1. On the Native Window of an Engineering Station node, select
Mount/Dismount Emulated Disks… from the Access menu.
2. Mount the TPN R687.1 (or later) disk_&z1.lcn file to the left
drive and the System HM Backup to the right drive.
3. Click OK.
Load the HM with Offline or INIT personality by performing the
following procedure:

2. From the Native Window’s System Status Display, select the HM

and click Node Status.
3. Click LOAD/DUMP.
4. Click MANUAL LOAD.
5. Click INIT PROGRAM.
6. Select the left drive number for the Program Source and the
right drive number for the Data Source.
RESULT: After the node loads, the node type changes from “HM”
to “HMOF”.
On the ES-T node that is already loaded and available, perform the
following procedure:

7. Select COMMAND PROCESSOR from the Engineering Main

Menu.
8. Type SP and then make the following changes:

NOTE: Below, the values $F2 and $F1 are used as

examples only. The actual paths may be different (e.g.
$F20 and $F19).

1. Change NETWORK CONFIG path to $F2>&ASY>, where “$F2”

173
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

is the path to the emulated drive to which you have taken the
System HM Backup.

2. Change CONFIGURE OVRLY path to $F1>&OP1>, where

“$F1” is the path to the disk_&z1.lcn file.

3. Press Enter.
4. Click EXIT.
9. Select VOLUME CONFIGURATION from the Engineering Main
Menu.
10. Select the HM node you are initializing.
11. Press CTRL + F6 to initialize the SBHM.
Pressing CTRL + F6 will INITIALIZE the ELCN HM, and erase all
data!
Make sure that you have taken a backup to an emulated disk
and/or cartridge.

ATTENTION: Initialization may take at least three minutes.

Wait until you receive an initialization complete message
before going to the next step.

3 Restore the System HM Backup and then reload the node by

performing the following procedure:

1. From the disk_&z1.lcn, run the LOC_VOLZ.EC with the proper

parameters.
2. From the disk_&z1.lcn, run the SYS_VOLZ.EC with the proper
parameters.
3. Type n for the Copy &ASY ? option.
4. When finished, ensure you copy the entire &ASY directory from
the correct drive to the HM using the PN:nn syntax.

174
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Example: “CP $Fd>&ASY>*.* PN:nn>&ASY>= -D”, where d represents

media drive number and nn is the HM node number in this
example.

ATTENTION: You must copy the NCF.CF which contains the

proper configuration for the SBHM. Make sure that the
NCF.CF file on the removable media is the most recent one
(if you made a subsequent NCF change to removable media,
and not the NCF from the backup).

5. Select the Enable LCNP Auto Restart check box on the

Configuration Utility’s Board 0 page.
6. At this point, you must be able to auto boot the HM by pressing
Reset LCNP button from the LCNP Status window. The HM will
begin to auto boot. Note that this step must be performed on
the HM node that is in the PWR_ON state now.
7. You can now run PRS4VOLZ.EC (and optionally PRS2VOLZ.EC),
followed by MSCHEMZ.EC (with disk_&z14.lcn and disk_
&z12.lcn mounted).
8. Protect NCF.CF file in “&ASY” directory before restoring
contents of your HM from backup, .e.g., PROT
PN:09>&ASY>*.CF.

NOTE: You protect the NCF.CF file such that it does not get
over-written by the RESTORE process initiated in the next
step.

9. You can now restore the contents of your HM from TPN Backup
and then restore the contents of your HM using whatever
means you used to back up the HM. Once restore is fully
complete, you should unprotect the NCF.CF file (e.g., UNPT
PN:09>&ASY>*.CF).

ATTENTION: To re-load an HM node, click the Reset LCNP

button twice in the LCNP Status window.

175
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Post installation tasks for Data HM

Step Action Done

1 Click Start > Honeywell Experion > LCNP Status to

launch the LCNP Status window. The HM node will now
be in PWR ON state.

2 Perform HM Initialization.
Pre-requisites: An ES-T must be present and configured
with the same Multicast IP as this HM node and loaded
with either of these:

l R687.1 (or later) personality through disk_&z1.lcn and

the NCF backup taken from the System HM as
described in the “"Pre- configuration tasks" on
page 163” section.
l Personality and NCF from the system HM that is
already running.

3 On the ES-T node that is already loaded and available:

1. Open Native Window

2. Mount the disk_&z1.lcn from R687.1 (or later) in the
left drive.

176
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

3. Select the HM and click Node Status.

4. Click Load/Dump.
5. Click Manual Load.
6. Click INIT PROGRAM.
7. Select the left drive number for the Program Source
and NET for the Data Source.
RESULT: After the node loads, the node type changes
from “HM” to “HMOF”.

8. Select VOLUME CONFIGURATION from the

Engineering Main Menu.
9. Select the HM node you are initializing.
10. Press CTRL + F6 to initialize the SBHM.
Pressing CTRL + F6 will INITIALIZE the ELCN HM, and
erase all data!

ATTENTION: Initialization may take at least three

minutes. Wait until you receive an initialization
complete message before going to the next
procedure.

11. From the disk_&z1.lcn, run the LOC_VOLZ.EC with the

proper parameters.
12. Select the Enable LCNP Auto Restart check box on
the Configuration Utility’s Board 0 page.
At this point, you will be able to auto boot the HM by
pressing Reset LCNP twice from the LCNP Status
window until the node transitions to the PWR_ON state.

13. You can now restore the contents of your HM from

TPN Backup and then restore the contents of your
HM using whatever means you used to back up the
HM. Once restore is fully complete, you should
unprotect the NCF.CF file (e.g., UNPT
PN:09>&ASY>*.CF).

177
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ATTENTION: To re-load an HM node, click the

Reset LCNP button twice on the LCNP Status
Display.

Migration from HM to ELCN-HM with Disk

Drive Synchronization
Beginning with TPN R688.3 and Experion R501.6, a new
feature has been introduced for synchronizing SBHM disks
with emulated disks mounted on ELCN ES-T. This feature helps
optimize SBHM to ELCN-HM migration.
Prior to TPN R688.3 and Experion R501.6, after performing
ELCN-HM node installation, the following post installation
tasks have to be performed to make HM emulated disk files to
be fully operational with online personality.
n Perform full backup of History Module
n Load ELCN-HM with offline personality
n Perform HM initialization
n Restore HM data from HM backup (full backup taken from
SBHM) to HM emulated disk files.
These post installation tasks involved in making the HM
emulated disk files to be fully operational with the online
personality are complex, involve user intervention, and are time
consuming.
To avoid this, a new option to the Command Processor’s
SYNCH command has been introduced for synchronizing
SBHM disks with emulated disks mounted on ELCN ES-T.
SBHM to ELCN-HM migration aims at synching SBHM disk
drives (2, 3, 4, and 5) to ELCN-HM Emulated disk files (.lcn files
representing each of the SBHM disk drives) by using the new
ELCN syntax option in the Command Processor’s SYNCH
command. After the synch, the ELCN-HM emulated disk files
would be the exact replicas of SBHM disk drives. These ELCN-
HM emulated disk files can be readily used to boot up ELCN-

178
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

HM node with the online personality after the ELCN-HM node

installation.
Post installation steps involved in migrating from SBHM to
ELCN-HM node would be minimized thus optimizing the
migration procedure.

ATTENTION: This migration procedure is only supported for

a SBHM migration of Type 7 with 2 disks in the NCF. The
SYNCH command with ELCN option is not supported for
SPCHM. For more information, refer section "Migration
from HM to ELCN-HM"to perform NCF change.

To install the ELCN-HM Node

See section To install the ELCN-HM Node.

Pre-configuration tasks

To synchronize disk drive between SBHM and ELCN-HM

ATTENTION: Perform this migration on only one SBHM per

ELCN at a time.

Convert an ELCN ES-T (preferably an Engineering ES-T) into a

disk synchronization station to perform this migration. This is a
temporary procedure. After completion of the migration, you
can convert it back to a regular ES-T.
Prior to Experion R501.6 and TPN R688.3, you can also backup,
initialize and restore the HM using the older methods.
Beginning with Experion R501.6 and TPN R688.3, it is optional
to use the SYNCH ELCN option. However, it is recommended to
use the SYNCH ELCN option to perform disk drive
synchronization between SBHM and ELCN-HM.

179
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Prerequisites
n Ensure that you have product administrator privileges.
n Run 'TPS Node Configuration Utility’ with administrator
privileges.
n Ensure that you have at least 7.2 GB of free disk space in
ELCN ES-T’s C:\ drive.
n Ensure that the ELCN ES-T used to perform the SBHM to
ELCN HM disk synchronization is not being used for any
operation involving emulated disk till this procedure is
completed successfully.
Perform the following procedure on an ELCN ES-T to
synchronize disks between SBHM and emulated disks mounted
on ELCN ES-T.
1. Stop the service “LCNP4EmulationManagementService”.
This service is tied to three other services, and the
confirmation message to stop the other 3 services appears.

Click Yes.
2. Launch the TPS Node Configuration Utility. Click Start >
Honeywell Experion Tools > All Honeywell Tools > System
Management, right-click on TPS Configuration Utility and
click Run as administrator.
3. Click Configuration Utility > Board 0.
4. On the Common tab, under SBHM to ELCN-HM Migration,
check the ELCN SCSI-HD check box.

180
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

After the ELCN SCSI-HD check box is selected, the SCSI

Slot is replaced with SCSI-HD Slot Emulation.

n Go to ELCN ES-T emulated drive, dismount 2,3,4,5 drives if

they are already mounted. The dismount operation
dismounts the lcn files from the respective drives.

181
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

a. Click the Dismount button corresponding to the drive on

which you want to dismount the files.
b. Delete the dismounted files by performing the following
procedure.
To delete an emulated disk:
i. Select a dismounted emulated disk from the Available
(Dismounted) Emulated Disks list.
ii. Click Delete. The message, 'Do you want to free the
disk space?' appears.
iii. Click Yes to remove the emulated disk from the list and
physically delete the file from its storage location.
And click No to remove the emulated disk from the
Available (Dismounted) Emulated Disks list, but not
physically delete the file from its storage location.
6. Restart the node.
Once the node is loaded, check LCNP Status and Emulated
disks tab for the following changes.
n SCSI Slot should be replaced with SCSI-HD Slot in LCNP
Status.

n Emulated disk files should be replaced with HM Emulated

disk files in Emulated disk tab.

182
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

HM emulated disk files are created in the following default

location:
C:\ProgramData\Honeywell\EngineeringData\HMEmulated
Disks.

At this point in time, ensurethat the SBHM disk is updated

to TPN R688.3 or a later TPN release.
7. Go to Native Window Command Processor and execute the
following Native Window command,
SYNCH PN: NN ELCN
Where
NN : HM’s LCN Node number
ELCN : new syntax switch option which enables sync
between SBHM and ELCN HM Drives mounted on an
ELCN ES-T
RESULT: This enables the disks synchronization between
ELCN ES-T and SBHM.
8. To know the synchronization status, run the following
command:
STA PN:nn -d
Where

183
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

nn: node number of the ELCN ES-T node (disk

synchronization station) where the synchronization is
initiated

ATTENTION: "nn" is NOT the node number of the HM.

It is the node number of the ELCN ES-T node (disk
synchronization station) where the synchronization is
initiated.

-d : (optional) if you want to see details of each volume of

the SBHM
The following are the states and their descriptions:

Step Action

OFFLINE Synchronization is not initiated.

NOTE: When the disk state

shows OFFLINE, volume state
shows NOT INIT’D.

SYNC_IP Synchronization is in progress.

OK Synchronization is complete.

NOTE: When synchronization

is initiated, the volume state
will first transition to SYNC_IP
and then OK. The disk state
will transition to OK only
when all the volumes are
synchronized and their status
is OK.

FAILED Volume synchronization failed.

Refer step 17 for reinitiating
synchronization.

9. Once all the volumes are synched and their status shows
OK, stop the service “LCNP4EmulationManagementService”.
This service is tied to three other services, and the
confirmation message to stop the other 3 services appears.

184
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Click Yes.

ATTENTION: The synchronization time may vary based

on the size of the volume to be synchronized.

10. Dismount the HM Emulated disk files.

ATTENTION: Do not dismount the HM Emulated disk

files until the TDC Emulators and LCNP4 Emulators
services have stopped.

11. Take a backup of all the disk drives, 2, 3, 4, and 5.

12. Zip the backed up .lcn files for mounting purpose in the
section “To configure the ELCN-HM Node”.
13. From the TPS Configuration Utility, on the Common tab,
under SBHM to ELCN-HM Migration, uncheck the SCSI-HD
Slot Emulation.
The SCSI-HD Slot changes to SCSI Slot.
14. Restart the node.
15. You can now use the ELCN ES-T for normal operations.
16. Shut down the System HM/Data HM:
a. Perform a SHUT DOWN of the node you want to migrate
from the Native Window System Status display. Select the

185
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

node and select the SHUT DOWN target and press Enter.
This causes an “orderly” shutdown to the QUALIF state.
b. Shut down the node from the Native Window for the
second time to place it into the FAIL state.

ATTENTION: If the node is not shut down two (2)

times and placed into the "FAIL" state, and then
powered OFF, the LCN will continue to look for that
node in the token for 1 minute and 57 seconds (it
takes 1 minute and 57 seconds before the system
will eventually ISOLATE the node.). During this time,
the system is extremely sluggish (if not placed in
the “FAIL” state).

c. Power-off the node by removing power from the HM. This

node is now in the FAIL state as shown on the System
Status Display or Node Status Display.
d. Shut down the node from the Native Window for the third
time to transition from the FAIL state to the OFF state.
17. If you get the following error, the SYNCH command has
failed.

Perform the following steps before re-initiating the SYNCH

command with the ELCN option.
a. Stop the service “LCNP4EmulationManagementService”.
This service is tied to three other services, and the
confirmation message to stop the other 3 services
appears.

186
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Click Yes.
2. Go to ELCN ES-T emulated drive and dismount 2,3,4,5
drives. This will dismount the lcn files from the respective
drives.
3. Delete the dismounted files by performing the following
procedure.
i. Select each dismounted emulated disk file from the
available (Dismounted) Emulated Disks list.
ii. Click Delete. The message, 'Do you want to free the disk
space?' appears.
iii. Click Yes. This will physically delete the file from its
storage location.
4. Restart the services in the following order.
i. LCNP4EmulationManagementService
ii. TDC Emulators Service
iii. K4LCN Reset Server
iv. TPNCommSvc
5. Re-initiate the Synch command with ELCN option.

187
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

To configure the ELCN-HM Node

ATTENTION: Turn the HM off, otherwise you will have

duplicate LCN node addresses, and the system may
encounter unexpected conditions due to messages
traversing in both directions across the ELCN Bridge.

Perform the following procedure to complete the configuration

of the ELCN-HM node.

Step Action Done

1 Use the HM Node Configuration Utility to configure the

ELCN-HM node.
Launch the TPS Node Configuration Utility. Click Start >
Honeywell Experion Tools > All Honeywell Tools > System
Management , right-click on TPS Configuration Utility
and click Run as administrator.

2 Open the Board 0 page (Configuration Utility > Board 0)

and on the LCNP tab, provide the following details:
l LCN Address: Unique address within the network and
must not be a duplicate.
l LCN Name
l ELCN Multicast IP (must match on the ELCN Bridge
and all Experion LCN Nodes in order for them to
communicate)
l NG name
l Select the Enable LCNP Auto Restart check box. This
setting determines if the ELCN-HM node will boot
automatically in case of a machine restart or a TDC
Emulators service restart.
l Personality is displayed as HM and is non-editable.

188
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

3 On the Common tab, you will have default options

enabled as shown here for the ELCN-HM node.

ATTENTION: The following step for the Emulated Disks tab is not normally
used for normal operations. This tab is used for maintenance or special
situations.

189
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

4
ATTENTION: Ensure that the TDC Emulators and
LCNP4 Emulators services have stopped.

1. Go to ELCN-HM emulated drive, dismount 2,3,4,5

drives if they are already mounted. The dismount
operation dismounts the lcn files from the respective
drives.
Click the Dismount button corresponding to the drive
on which you want to dismount the files
2. To delete them after dismounting, perform the
following procedure: Delete the dismounted files by
performing the following procedure:
1. Select a dismounted emulated disk from the
Available (Dismounted) Emulated Disks list.
2. Click Delete. The message, 'Do you want to free the
disk space?' appears.
3. Click Yes to remove the emulated disk from the list
and physically delete the file from its storage
location.
And click No to remove the emulated disk from the
Available Dismounted Emulated Disks list, but not
physically delete the file from its storage location.
3. Unzip the folder containing the four .lcn files (from
step 12 in Pre-configuration tasks) from the ELCN
ES-T default path (the files may also be available in a
custom path)
Default path: <Program Data
path>\Honeywell\EngineeringData\HMEmulatedDisk
s\>
And copy the four .lcn files to ELCN-HM default path
Default path: <Program Data
path>\Honeywell\EngineeringData\HMEmulatedDisk
s\>
manually.

4. Open Config Utility.

5. Go to Configure > Board 0 > Emulated Disks > Create.

190
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

The create option provides flexibility to choose file

names/paths, which are created in the chosen location.

Open the four .lcn files one at a time and click OK.

6. To mount an emulated disk, perform the following

steps:
The emulated disk to be mounted must be included in
the Available (Dismounted) Emulated Disks list.
Click Mount and select the drive that you wish to
mount. Only those drives that are not already
mounted with an lcn file will be available for
mounting.

191
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ATTENTION: You can also drag an emulated disk

from the available list to 2, 3, 4, and 5 HM drives.

The selected emulated disk will now appear as mounted

on the chosen drive.

5 Start the services in the following order.

1. LCNP4EmulationManagementService

2. TDC Emulators Service

3. K4LCN Reset Server

4. TPNCommSvc

6 After it is loaded, the HM will transition to OK state.

RESULT: You have now successfully migrated from SBHM to ELCN-HM.

Migration from Classic AM to Experion LCN AM

This section describes the off-process migration from Classic
AM to ELCN-AM.

ATTENTION: In Experion R501 and TPN R687, only a non-

redundant UEA-based ELCN-AM is supported. A minimum
of Experion R501.4 and TPN R688.1 is required for
migration to redundant ELCN-AM, or virtual ELCN AM.

192
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

UEAs shipped from the factory have UEA RECOVERY firmware

and no APP firmware image. The factory-shipped UEA has the
firmware version UEA_100.1-11.0.

NOTE: The first time you load firmware on a UEA box, load
the Application personality image before the Boot/Recovery
(UEARECOVERY) personality image. The Firmware
Manager Tool will not overwrite the existing
UEARECOVERY personality image until an Application
personality image (UEAELCN_NODE) is present and
available to the UEA. The UEAELCN_NODE application
image is available for download using the Firmware
Manager.

ATTENTION: Migration from Classic AM to an ELCN-AM

requires powering-off the Primary and Backup classic
nodes. Perform this activity at an appropriate time to avoid
disturbance to the process and potentially hazardous
consequences to equipment and personnel. Determine in
advance that the scheduling of this procedure is in
accordance with proper system operation.

Prerequisites
Before you migrate from Classic AM to ELCN-AM, ensure that
the prerequisites described in section “Prerequisites for ELCN
UEA Appliance Node migration” are complied with.

Classic AM shutdown
Perform the following procedure to perform an orderly
shutdown of the Classic AM to migrate to ELCN-AM. This
procedure shuts down a single AM (node 37 in the example
displays) to migrate this single node to ELCN AM. This
procedure may be repeated for a redundant AM also, when
migrating redundant AMs to ELCN.

193
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

1 From the Native Window System Status Display, select the

Classic AM to be shut down (node 37 in the example
display below), then select the SAVE SELECT target and
press Enter. Save the checkpoint to NET.

ATTENTION: It is highly recommended that you also

save the AM checkpoint into an Emulated Drive as
well, to have a second source of a known good
checkpoint.
You can restore this checkpoint in case you want to
migrate back from ELCN-AM to Classic AM due to
any issues found during or after Classic AM to
ELCN-AM migration.

2 At a station (for example, US or ES-T), perform a SHUT

DOWN of the chosen Classic AM from the Native Window
System Status display. Select the node and select the
SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the
QUALIF state.

NOTE: Beginning with TPN R690 or later, the

following changes are applicable:

194
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l For a primary node in a redundant configuration,

which is an ELCN (UEA/UVA only) node, the
system will actually send two SHUT DOWN
commands, automatically.
l This applies only when the SHUT DOWN
command is issued at the primary node of a
ELCN UEA/UVA. This is done because when a
SHUT DOWN command to a primary UEA/UVA
node is issued, the UEA/UVA node reboots and
sends a second SHUT DOWN command which
takes the node to an OFF state while the
UEA/UVA node reboots to the PWR_ON state.

3 Shut down the Classic AM from the Native Window for the
second time to place it into the FAIL state.

ATTENTION: If the node is not shut down two (2)

times and placed into the "FAIL" state, and then
powered OFF, the LCN will still be looking for that
node in the token for 1 minute and 57 seconds (it
takes 1 minute and 57 seconds before the system
will eventually ISOLATE the node.). During this

195
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

time, the system is extremely sluggish (if not placed

in the “FAIL” state).
The best practice is to always shut down the node
that is to be powered down, two (2) times to place it
in the "FAIL" state. Then power it down and perform
the required work so the LCN can communicate
normally.

Experion Bridge Status Display when node 37 is in the

FAIL state:

4 Power-off the node by placing the LCN chassis power

supply switch in the OFF position. This node is in the FAIL
state as shown on the System Status Display or Node
Status Display.

ATTENTION: Do not accidentally power-off the

wrong node. If it is a DNCF, use the arrows to
identify the appropriate power switch.

5 Shut down the Classic AM from the Native Window for the
third time to transition from the FAIL state to the OFF
state.

196
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Experion Bridge Status Display when node 37 is in the

OFF state:

6 If migrating redundant AMs to ELCN, repeat Steps 2-5 to

shut down the remaining redundant Classic AM.

Installing UEA
Install the UEA hardware as described in the referenced
document below. For redundant AM migration, install a pair of
UEA boxes.
REFERENCE: For information on UEA installation, see the
Experion LCN Hardware Upgrade Kit Instructions (51195195-
415).

197
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Installing FTE switches

Install FTE switch(es) as needed, as described in the referenced
document below.
REFERENCE: For information on mounting and configuring
the Ethernet switches for the ELCN, see the FTE Switch used
with LCN cabinet Upgrade Kit instructions (51195195-384).
After FTE switch installation, connect the FTE cables between
the UEA FTE ports and the L2 ports on the FTE switch.

Startup of UEA
Each UEA must have a Device Index that is unique in the FTE
community. You enter the Device Index through the front panel
display at the physical UEA box. At a high level, the user must
do the following from the front panel of the UEA box:
n On the UEA front panel, rotate the key clockwise to the C
position to enter the CONFIG menu.
n Configure the FTE Device Index.
n Change the BOOTP setting from NO to YES.
n Save these changes (this reboots the box and the UEA will
get its FTE IP Address from the Experion BOOTP Server.)
n After the reboot, node transitions into the “Alive” state.
For detailed procedures, refer to section “"To Set the Device
Index Using the UEA Front Panel" on page 100”.

Migrating from Non-Redundant Classic AM to ELCN-

AM
Perform the following procedure to migrate from a Non-
Redundant Classic AM to ELCN-AM.

Step Ation Done

1 Verify that the node is in the Alive state at the UEA

Front Panel Display.

NOTE: The LCN will still show the AM node in

the OFF state.

198
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

2 Using the Firmware Manager Tool, flash the

Application personality image followed by the
UEARECOVERY personality image to the node.
For more information, see section “"Node flashing
procedure for a UEA node coming from the factory
with only the Boot Recovery image" on page 109”.
RESULT: After the node reboots, it goes to the
“NotLoaded” state.

3 In Control Builder, click File > New > ELCN and then
click ELCN_NODE – ELCN Appliance Node.

RESULT: The configuration form opens with the Main

tab selected.
AM configuration form - Main tab:

199
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

4 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index here which

you have configured on the UEA box.

l Under the ELCN Node Type drop-down list, select

AM
l Do not enter an ENIM UCN Node Number.
l Do not select the Module is redundant checkbox.
l ELCN Multicast Address

NOTE: Make sure that you have the same ELCN

Multicast Address as configured for the ELCN
Bridge(s).

l LCN Node Number – This

Enter the LCN Node number of the AM you are
migrating to ELCN.
When assigning or changing the LCN node number of
any LCN or ELCN node, it is imperative that the
intended node number is not already in use by

200
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

another LCN or ELCN node.

If you cause a duplicate node number situation to
occur, the invalid duplicate node fails, and the
existing running node may become ISOLATED from
some LCN and ELCN nodes. To recover from this
situation, you must power-off the invalid node,
change its LCN node number to an unused LCN
address, power it back on, and reload the existing
running node which may have become ISOLATED.

l Do not enter an LCN Node Number – Partner

5 After configuring the parameters, click OK to accept

the changes.
RESULT: The ELCN-AM block is entered into the
ERDB. The Tag Name and icon appear on the Project
side/tab, ready for loading.

6 On the Project tree of Control Builder, select the block

to be loaded.

7 Right-click and then select Load, or click on the

Control Builder toolbar.

RESULT: The Load Operation dialog box appears.

201
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

8 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to the

node. The operation of the ELCN-AM is activated.
The ELCN-AM node transitions to the PWR_ON state.

Experion Bridge Status Display when node 37 is in the

PWR_ON state:

202
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

9 From the Native Window System Status Display,

select the AM (in the PWR_ON state shown below),
and load the ELCN-AM from the NET (or from the
Emulated Drive to which you had saved the
checkpoint earlier).
To load the node (TPN/LCN Personality), select the
node and click LOAD SELECT and press Enter.

RESULT: The node’s status will transition to NET_LD,

and then to OK after the load is complete.

203
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Ation Done

RESULT: You have now successfully migrated your Classic AM to ELCN-AM. You
may want to check the Experion Detail Displays and Control Builder “Main Tab” to
verify that they are reflecting the OK state. You may need to perform a refresh on the
Experion Detail Display to update the node status.

ATTENTION: After ensuring that the node is communicating over FTE and
there is no need to go back to Classic AM, you can decommission this node.
For more information, see section “Decommission/Recommission Nodes”.

ATTENTION: Make sure that the ELCN-AM is functioning correctly and then
checkpoint the ELCN-AM.

Migrating from Redundant Classic AM to ELCN-AM

Perform the following procedure to migrate from a redundant
Classic AM pair to ELCN-AM.

Step Action Done

1 Verify that the nodes are in the Alive state at the UEA
Front Panel Displays.

NOTE: The LCN will still show the AM nodes in

the OFF state.

2 Using the Firmware Manager Tool, flash the

204
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Application personality image followed by the

UEARECOVERY personality image to the node.
For more information, see section “"Node flashing
procedure for a UEA node coming from the factory
with only the Boot Recovery image" on page 109”.
RESULT: After the node reboots, it goes to the
“NotLoaded” state.

3 In Control Builder, go to the Project tree, click File >

New > ELCN and then click ELCN_NODE – ELCN
Appliance Node.

RESULT: The configuration form opens with the Main

tab selected.
AM configuration form - Main tab:

205
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

4 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index here which

you have configured on the UEA box.

l Under the ELCN Node Type drop-down list, select

AM
l Do not enter an ENIM UCN Node Number.
l Select the Module is redundant checkbox.
l ELCN Multicast Address

NOTE: Make sure that you have the same ELCN

Multicast Address as configured for the ELCN
Bridge(s).

l LCN Node Number – This

NOTE: Enter the LCN Node number of the

206
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Primary AM.

When assigning or changing the LCN node number of

any LCN or ELCN node, it is imperative that the
intended node number is not already in use by
another LCN or ELCN node.
If you cause a duplicate node number situation to
occur, the invalid duplicate node fails, and the
existing running node may become ISOLATED from
some LCN and ELCN nodes. To recover from this
situation, you must power-off the invalid node,
change its LCN node number to an unused LCN
address, power it back on, and reload the existing
running node which may have become ISOLATED.

l LCN Node Number – Partner

NOTE: Enter the LCN Node number of the

Backup AM.

5 Make sure you connect an Ethernet crossover cable

between the redundancy ports of the primary and
backup UEA boxes.

6 After configuring the parameters, click OK to accept

the changes.
RESULT: The Primary and Backup ELCN-AM blocks
are entered into the ERDB. The Tag Names and icons
appear on the Project side/tab, ready for loading.

7 On the Project tree of Control Builder, select the

Primary ELCN-AM block and Backup ELCN-AM
blocks to be loaded.

8 Right-click and then select Load, or click on the

Control Builder toolbar.

RESULT: The Load Operation dialog box appears.

207
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

9 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the blocks to the
primary and backup nodes. The operation of both the
Primary and Backup ELCN-AM are activated.
The ELCN-AM nodes transition to the PWR_ON state
(Native Window). Node 33 is shown below as an
example.

Experion Bridge Status Display when nodes 33 and 34

are in the PWR_ON state:

208
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

10 From the Native Window System Status Display, load

the Primary ELCN-AM (node 33 in below display) from
the NET (or from the Emulated Drive to which you had
saved the checkpoint earlier).
To load the node (TPN/LCN Personality), select the
node and click LOAD SELECT and press Enter.
RESULT: The node’s status will transition to NET_LD,
and then to WARN after the load is complete.

The Control Builder shows the Node State as “WARN”

and Redundancy Role as “PRIMARY”.

209
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

11 From the Native Window System Status Display, load

the Backup ELCN-AM (with even-numbered Device
Index) from the NET. To load the node, select the node
and click LOAD SELECT and press Enter.
RESULT: The node’s status will transition to NET_LD,
and then BACKUP after the load is complete. The
Primary ELCN-AM will now transition to the OK state.

Experion Bridge Status Display when nodes 33 and 34

are in the OK and BACKUP state respectively.

For UVA-based ELCN AM, refer the below Experion

Bridge Status Display

210
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

In the case of a redundant UEA-based or UVA-based

ELCN Appliance node, during an onprocess migration
from any pre-R501.6 release to R501.6 or later
version, an additional switch over is required to
complete the migration. Beginning with R501.6, a soft
failure indicator, “Deployment Incomplete”, appears
on the Soft Failures tab of an ELCN Node Control
Builder block which indicates this switch over has not
been completed. This is not applicable for migration
from R501.6 onwards to any later release.

RESULT: You have now successfully migrated your Classic AM redundant pair to
ELCN-AM redundant pair.

ATTENTION: After ensuring that the nodes are communicating over FTE and
there is no need to go back to Classic AM, you can decommission them.
For more information, see section “Decommission/Recommission Nodes”.

ATTENTION: Make sure that the ELCN-AMs are functioning correctly and
then checkpoint the Primary ELCN-AM.

Backing out of ELCN-AM to Classic AM

This procedure assists you in migrating from ELCN-AM to
Classic AM if you encounter a problem during, or after, Classic
AM to ELCN-AM migration, and you would like to go back to
the original Classic AM.

211
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

ATTENTION: Make sure the LCN node(s) is(are) installed

and ready to be powered up and loaded before performing
this procedure.

Done
Step Action
(√)
1 At a station (for example, US or ES-T), perform a SHUT DOWN of
the node from the Native Window System Status display. Select
the node and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

2 Shut down the node from the Native Window for the second time
to place it into the FAIL state.

3 In Control Builder, select the ELCN-AM platform block from the

Monitoring tree.

4 Right-click on the block and click Delete.

RESULT: The ELCN-AM platform block is deleted from the
Monitoring tree and the UEA box reboots and transitions to the
“NotLoaded” state.

5 While the node reboots, loosen the threaded captive screws in

counter-clockwise direction and pull-out the UEA box (but leave
the box in the chassis) from the chassis until the power supply is
interrupted.

NOTE: Use the handles to slide the UEA box.

6 Repeat Step 4 to delete the block from the Project tree.

NOTE: You may wish to retain this block in the Project side
for ease of going back to the ELCN-AM node.

7 Shut down the node from Native Window for the third time to
transition from the FAIL state to the OFF state.

8 Power-on the Classic AM by placing the LCN chassis power

supply switch in the ON position.

9 Using the Native Window System Status Display, verify that the
node transitions to the PWR_ON state.

212
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
10 From the Native Window System Status Display, load the Classic
AM using the checkpoint saved in the NET (or Emulated Drive)
earlier.
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then to
OK after the load is complete.

RESULT: You have now successfully migrated back to Classic AM from ELCN-AM.

Off-process Migration from Classic NIM to

Experion LCN ENIM
This section describes the off-process migration from a Classic
NIM redundant pair to an ELCN-ENIM redundant pair.

ATTENTION: Upgrading from NIM to ELCN-ENIM is done

off-process. This requires powering-off the node. Perform
the upgrade activity at an appropriate time to avoid
disturbance to the process and potentially hazardous
consequences to equipment and personnel.

ATTENTION: In Experion R501 and TPN R688.3, only the

UEA-based ELCN-ENIM is supported. A minimum of
Experion R501.6 and TPN R688.3 is required for migration
to virtual ELCN ENIM.

You must have minimum of Experion R501.6 and TPN R688.3

installed (for Virtual ENIM migration). This involves upgrading
the firmware (for both UEA RECOVERY and APP images) of
ELCN-ENIM.

213
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

NOTE:
l PM/APM to EHPM (CE Compliant) Upgrade Kit
Instructions (51195766-034)
l PM/APM to EHPM (Non- CE Compliant) Upgrade Kit
Instructions (51195766-038)
l HPM to EHPM Upgrade Kit Instructions (51195766-
035)
l LM to ELMM Upgrade Kit Instructions (51195766-039)

Prerequisites
Before you migrate from Classic NIM to ELCN-ENIM, ensure
that the prerequisites described in section “Prerequisites for
ELCN UEA Appliance Node migration” are complied with.

Off-process migration from Classic NIM to ELCN-

ENIM
Perform the following procedure to perform off-process
migration from a Classic NIM pair to an ELCN-ENIM redundant
pair.

Step Action Done

1 From the Native Window’s System Status Display, save the

checkpoint to NET by selecting the Primary NIM you want to
checkpoint, and then select the SAVE SELECT target and press
Enter.

214
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

When the SAVE DATA target is selected, prompters request that

the media specifies where the checkpoint is to be stored. NET
specifies the checkpoint should be stored in the HM that has the
checkpoint volume 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.

ATTENTION: It is highly recommended that you also save

the NIM checkpoint into an Emulated Drive as well, to
have a second source of a known good checkpoint.
You can restore this checkpoint in case you want to
migrate back from ELCN-ENIM to Classic NIM due to any
issues found during or after Classic NIM to ELCN-ENIM
migration.

2 At a station (for example, US or ES-T), perform a SHUT DOWN of

the Classic Backup NIM (node 42 below) from the Native
Window System Status display. Select the node and select the
SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

NOTE: Beginning with TPN R690 or later, the following

changes are applicable:

215
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l For a primary node in a redundant configuration, which

is an ELCN (UEA/UVA only) node, the system will
actually send two SHUT DOWN commands,
automatically.
l This applies only when the SHUT DOWN command is
issued at the primary node of a ELCN UEA/UVA. This is
done because when a SHUT DOWN command to a
primary UEA/UVA node is issued, the UEA/UVA node
reboots and sends a second SHUT DOWN command
which takes the node to an OFF state while the
UEA/UVA node reboots to the PWR_ON state.

Experion Bridge Status Display before migration:

3 Shutdown the Classic Backup NIM from the Native Window for
the second time to place it into the FAIL state.

ATTENTION: If the NIM Node is not shut down two (2)

times and placed into the "FAIL" state, and then powered

216
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

OFF, the LCN will still be looking for that node in the
token for 1 minute and 57 seconds (it takes 1 minute and
57 seconds before the system will eventually ISOLATE the
node.). During this time, the system is extremely sluggish
(if not placed in the “FAIL” state).
The best practice is to always shutdown the node that is
to be powered down, two (2) times to place it in the "FAIL"
state. Then power it down and perform the required work
so the LCN can communicate normally.

4 Power-off the Backup node by placing the LCN chassis power

supply switch in the OFF position. This node is in the FAIL state
as shown on the System Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off the wrong NIM.

If it is a DNCF, use the arrows to identify the appropriate
power switch.

Experion Bridge Status Display when node 42 is in the FAIL

state:

5 Shutdown the Backup node from the Native Window for the third
time to transition from the FAIL state to the OFF state.

217
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Experion Bridge Status Display when node 42 is in the OFF

state:

Native Window - Process Networks Node Status Display when in

the OFF state:

6 Repeat Steps 1-5 to shut down the Classic Primary NIM. Step 1
will now checkpoint the Backup NIM, and Steps 2-5 will shut
down the Primary NIM.

7 Install a redundant pair of UEAs.

REFERENCE: For information on UEA installation, see the
Experion LCN Hardware Upgrade Kit Instructions (51195195-
415).

8 Connect the FTE cables between the UEA’s FTE ports and the L2
ports on the FTE switch.

218
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

9 Make sure you connect an Ethernet crossover cable between the

redundancy ports of the primary and backup UEA boxes.

10 Perform a startup of both the Primary and Backup ELCN-ENIM

UEA boxes.
Each UEA must have a Device Index that is unique in the FTE
community. You enter the Device Index through the front panel
display at the physical UEA box. At a high level, the user must do
the following from the front panel of the UEA box:
l On the UEA front panel, rotate the key clockwise to the C
position to enter the CONFIG menu.
l Configure the FTE Device Index.

NOTE: Set an odd-numbered device index and even-

numbered device index for the primary and backup nodes
respectively.

l Change the BOOTP setting from NO to YES.

l Save these changes (this reboots the box and the UEA will get
its FTE IP Address from the Experion BOOTP Server.)
l After the reboot, nodes transition into the “Alive” state.
For more information, refer to section “"To Set the Device Index
Using the UEA Front Panel" on page 100”.

11 Verify that the nodes are in the Alive state at the UEA Front
Panel Display.

12 Using the Firmware Manager Tool, flash the Application

personality image followed by the UEARECOVERY personality
image to the nodes.
For more information, see section “"Node flashing procedure for
a UEA node coming from the factory with only the Boot Recovery
image" on page 109”.
RESULT: After the nodes reboot, they transition to the
“NotLoaded” state.

13 In Control Builder, click File > New > ELCN and then click ELCN_
NODE – ELCN Appliance Node.

219
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

13 cont RESULT: The configuration form opens with the Main tab
selected.
ENIM configuration form - Main tab:

14 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #

220
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l (optional) Associated Asset #

l Device Index

NOTE: Enter the same device index here which you have
configured on the UEA box.

l Under the ELCN Node Type drop-down list, select ENIM

l ENIM UCN Node Number

NOTE: Enter the UCN Node Number of the Primary ENIM.

l Select the Module is redundant checkbox.

NOTE: The Device Index and LCN Node Number are

incremented by one (1) for the backup. The IP Address
does not need to be incremented by one (1) for the
backup.

l ELCN Multicast Address

NOTE: Make sure that you enter the same ELCN Multicast
Address as configured for the ELCN Bridge(s).

l LCN Node Number –This

NOTE: Enter the LCN Node Number of the Primary ENIM.

When assigning or changing the LCN node number of any LCN

or ELCN node, it is imperative that the intended node number is
not already in use by another LCN or ELCN node.
If you cause a duplicate node number situation to occur, the
invalid duplicate node fails, and the existing running node may
become ISOLATED from some LCN and ELCN nodes. To recover
from this situation, you must power-off the invalid node, change
its LCN node number to an unused LCN address, power it back
on, and reload the existing running node which may have
become ISOLATED.

221
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l LCN Node Number – Partner

NOTE: Enter the LCN Node Number of the Backup ENIM.

15 After configuring the parameters, click OK to accept the

changes.
RESULT: The Primary and Backup ELCN-ENIM blocks are
entered into the ERDB. The Tag Names and icons appear on the
Project side/tab, ready for loading.

16 On the Project tree of Control Builder, select the Primary ELCN-

ENIM block and Backup ELCN-ENIM blocks to be loaded.

17 Right-click and then select Load, or click on the Control Builder

toolbar.

RESULT: The Load Operation dialog box appears.

18 Click the Load button to confirm the operation

RESULT: The Control Builder loads the blocks to the primary
and backup nodes. The operation of both the Primary and
Backup ELCN-ENIM are activated.
The ELCN-ENIM nodes transition to the PWR_ON state (Native

222
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Window state). Node 41 is shown below as an example.

Experion Bridge Status Display when node 41 and node 42 are

in the PWR_ON state.

18 cont Native Window - Process Networks Node Status Display when in

the PWR_ON state:

19 From the Native Window System Status Display, load the

Primary ELCN-ENIM (with odd-numbered Device Index) from
the NET.
To load the node (TPN/ LCN Personality), select the node and
click LOAD SELECT and press Enter.
RESULT: The node’s status will transition to NET_LD, and then
WARN after the load is complete.

223
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

19 cont The Control Builder shows the Node State as “WARN” and
Redundancy Role as “PRIMARY”.

20 From the Native Window, choose Engineering Main Menu >

Builder Commands > Reconstitute to reconstitute the Primary
NIM point. Enter $NMuuNnn in the ENTITY Name pick, and then
press ENTER.
Where “uu” is the UCN Network Number and “nn” is the NIM’s
UCN Node Number. For example, if the UCN Network Number is
10 and the Primary NIM’s UCN Node Number is 01, the entity

224
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

name would be $NM10N01.

Enter a value for the Authentication Group into the port for the
$DEVIDX parameter. Press ENTER to accept the change and
then press CTL+F12 to load the point.

NOTE: It is highly recommended that the value for the

Authentication Group should match the value configured
on the UEA box for the FTE Device Index.For information
about Authentication Group configuration, refer to the
section “ENIM UCN Node Address Selection” in the
document.

20 cont
ATTENTION: Initially the $DEVIDX parameter will be “0”.
After you change the value from 0 to a non-zero value, a
warning message is displayed which says “WARNING:
CHANGING $DEVIDX WHILE IN A RUNNING STATE MAY
CAUSE LOSS OF VIEW. $NMuuNnn EXISTS – SELECT
OVERWRITE OPTION <F5> IF DESIRED”.
Where “uu” is the UCN Network Number and “nn” is the
primary NIM’s UCN Node Number.

Press CTL+F5 to overwrite the value of 0 for the Authentication

Group (the example below shows the overwritten value of 177).

225
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

21 Enter the value of Secondary NIM’s UCN node number (Primary

NIM’s UCN node number + 1) in the NODENUM field and then
press ENTER. The example below shows node number 02.

NOTE: The Authentication Group is not shown on a

Secondary NIM Node.

22 Press CTL+F12 to load the Secondary NIM point.

23 From the Native Window System Status Display, load the Backup
ELCN-ENIM (with even-numbered Device Index) from the NET.
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then
BACKUP after the load is complete. The Primary ELCN-ENIM will
now transition to the OK state.

226
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Experion Bridge Status Display when node 41 and node 42 are

in the OK and BACKUP state respectively.

For UVA-based ELCN ENIM, refer the following Experion Bridge

Status Display screenshot.

Native Window - Process Networks Node Status Display after

migrating both the Classic NIMs to ELCN-ENIMs.

RESULT: You have now successfully migrated from Classic NIM redundant pair to

227
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ELCN-ENIM redundant pair.

ATTENTION: After ensuring that the nodes are communicating over FTE, and
there is no need to go back to Classic ENIM, you can decommission them.

ATTENTION: Make sure that the ELCN-ENIMs are functioning correctly and
then checkpoint the Primary ELCN-ENIM.

Backing out of ELCN-ENIM to Classic NIM

This section assists you in performing off-process migration
back to Classic NIMs from ELCN-ENIMs. You can perform this
procedure if you come across any problem during or after
Classic NIMs to ELCN-ENIMs migration and you would like to
go back to the original Classic NIMs.

ATTENTION: Make sure the LCN node(s) is(are) installed

and ready to be powered up and loaded before performing
this procedure.

ATTENTION: Perform this procedure first on the Backup

ELCN-ENIM (with even-numbered Device Index) followed
by the Primary ELCN-ENIM (with odd-numbered Device
Index).

Done
Step Action
(√)
1 At a station (for example, US or ES-T), perform a SHUT DOWN of
the Backup ELCN-ENIM (with even-numbered Device Index) node
from the Native Window System Status display. Select the node
and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

2 Shutdown the node from the Native Window for the second time
to place it into the FAIL state.

3 Repeat Steps 1-2 for the Primary ELCN-ENIM (with odd-

228
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
numbered Device Index).

4 In Control Builder, select the Primary ELCN-ENIM platform block

from the Monitoring tree.

5 Right-click on the block and click Delete.

RESULT: The Primary and Backup ELCN-ENIM platform blocks
are deleted from the Monitoring tree and the UEA box reboots.

6 While the node reboots, loosen the threaded captive screws in

counter-clockwise direction and pull-out the UEA box (but leave
the box in the chassis) from the chassis until the power supply is
interrupted.

NOTE: Use the handles to slide the UEA box.

7 Repeat Step 5 to delete the blocks from the Project tree.

NOTE: You may wish to retain this block in the Project side
for ease of going back to the ELCN-ENIM node.

8 Shutdown the nodes from Native Window for the third time to
transition from the FAIL state to the OFF state.

9 Using the Native Window System Status Display, verify that the
nodes transition to the PWR_ON state.

10 From the Native Window System Status Display, load the Primary
NIM (with odd-numbered Device Index) using the checkpoint
saved in the Emulated Drive.
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then
WARN after the load is complete.

11 From the Native Window System Status Display, load the Classic
Backup NIM (with even-numbered Device Index) using the
checkpoint saved in the Emulated Drive.
To load the node, select the node and click LOAD SELECT and

229
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
press Enter.
RESULT: The node’s status will transition to NET_LD, and then
BACKUP after the load is complete. The Primary NIM will now
transition to the OK state.

RESULT: You have now successfully migrated back to Classic NIM redundant pair
from ELCN-ENIM redundant pair.

On-process Migration from Classic ENIM to

Experion LCN ENIM
This section describes the on-process migration from a Classic
ENIM redundant pair to an ELCN-ENIM redundant pair.

ATTENTION: You cannot perform on-process migration of a

Non-Redundant ENIM.

ATTENTION: In Experion R501 and TPN R687, only the

UEA-based ELCN-ENIM is supported. A minimum of
Experion R501.4 and TPN R688.1 is required for migration
to virtual ELCN ENIM.

You must have minimum of Experion R501.1 and TPN R687.1

installed (for UEA-based ELCN-ENIM migration). This involves
upgrading the firmware (for both UEA RECOVERY and APP
images) of ELCN-ENIM.
UEAs shipped from the factory have UEA RECOVERY firmware
and no APP firmware image. The factory-shipped UEA has the
firmware version UEA_100.1-11.0.

ATTENTION: Always perform on-process migration from

Classic ENIM to ELCN-ENIM one redundant pair at a time.

230
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Prerequisites
Before you migrate from Classic ENIM to ELCN-ENIM, ensure
that the prerequisites described in section “Prerequisites for
ELCN UEA Appliance Node migration” are complied with.

On-process migration from Classic Backup ENIM to

ELCN-ENIM
Perform the following procedures to perform an orderly
shutdown of the Classic Backup ENIM to migrate to ELCN-
ENIM.

Step Action Done

1 It is required that you perform this

step to account for the Experion
“Floating IP address” functionality
during migration to ELCN-ENIM.
ELCN-ENIMs will have a functionality
known as “Floating IP address.”
“Floating IP address” means that the
IP address of the ENIM is determined
by which ENIM is running as primary.
If this is not the case, then perform a
switch over so that the ENIM node
with an even-numbered device index
takes over as primary.
For example, ENIM 41 is running with
an odd-numbered device index, ENIM
42 is running with an even-numbered
device index, and the ENIMs are
running as the primary and backup
nodes, respectively.
Now, perform a switch over of the
primary node (ENIM 41), so that the
node with the even-numbered device
index (ENIM 42) takes over as the
primary.

TIP: You can use the $FTESTS1

Native Window schematic, and

231
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

select the respective ENIM’s

FTE Status line to obtain
detailed information about the
ENIMs including the FTE
Device Index.

Perform the switch over procedure as

follows:

1. At a station (for example, US or

ES-T), perform a SHUT DOWN of
the running Primary ENIM with the
odd IP address from the Native
Window System Status display.
Select the node and select the
SHUT DOWN target and press
Enter.RESULT: This causes an
“orderly” shutdown to the QUALIF
state and the backup node takes
over as the primary and transitions
into the WARN state.
2. Select the backup node and then
click LOAD SELECT to load the
current backup node so that
backup transitions into the
BACKUP state and the running
primary node transitions to the OK
state.

2 From the Native Window System

Status Display, save the checkpoint
to NET by selecting the ENIM you
want to checkpoint, and then select
the SAVE SELECT target and press
Enter. The backup ENIM (node 41) is
shown below as an example.

232
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

When the SAVE DATA target is

selected, prompters request that the
media specifies where the checkpoint
is to be stored. NET specifies the
checkpoint should be stored in the
HM that has the checkpoint volume
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.

ATTENTION: It is highly
recommended that you also
save the ENIM checkpoint into
an Emulated Drive as well, to
have a second source of a
known good checkpoint.

You can restore this checkpoint in

case you want to migrate back from
ELCN-ENIM to Classic ENIM due to
any issues found during or after
Classic ENIM to ELCN-ENIM
migration.

3 At a station (for example, US or ES-T),

perform a SHUT DOWN of the Classic
Backup ENIM (node 41 below) from
the Native Window System Status
display. Select the node and select
the SHUT DOWN target and press
Enter.

233
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: Use the $FTESTS1

Native Window schematic, and
select the Backup Classic
ENIM to verify that this is the
node with the odd-numbered
device index.

RESULT: This causes an “orderly”

shutdown to the QUALIF state.

Experion Bridge Status Display

before migration:

4 Shut down the Classic Backup ENIM

(node 41) from the Native Window for
the second time to place it into the
FAIL state.

ATTENTION: If the ENIM Node

is not shut down two (2) times
and placed into the "FAIL"
state, and then powered OFF,
the LCN will still be looking for
that node in the token for 1
minute and 57 seconds (it
takes 1 minute and 57 seconds
before the system will

234
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

eventually ISOLATE the node.).

During this time, the system is
extremely sluggish (if not
placed in the “FAIL” state).

The best practice is to always shut

down the node that is to be powered
down, two (2) times to place it in the
"FAIL" state. Then power it down and
perform the required work so the LCN
can communicate normally.

5 Power-off the Backup node (41) by

placing the LCN chassis power
supply switch in the OFF position.
This node is in the FAIL state as
shown on the System Status Display
or Node Status Display.

ATTENTION: Do not
accidentally power-off the
wrong ENIM. If it is a DNCF,
use the arrows to identify the
appropriate power switch.

Experion Bridge Status Display when

node 41 is in the FAIL state:

6 Shut down the Backup node (41)

from the Native Window for the third
time to transition from the FAIL state
to the OFF state.

ATTENTION: At this point in

235
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

time, wait for at least 70

seconds before you power-on
the Primary ELCN-ENIM.

RESULT: At this point in time, the

Classic Primary ENIM (node 42)
transitions to the “WARN” state on
the Native Window.
Do not shut down the primary node in
Native Window until the backup node
is upgraded to ELCN ENIM.

Experion Bridge Status Display when

node 41 is in the OFF state:

Native Window - Process Networks

Node Status Display when in the OFF
state:

7 Install a redundant pair of UEAs by

performing the following procedure:

1. At the front of the cabinet, slide

one UEA Processor Module into
the shelf until fully seated. Note
that the shelf has a guide slot

236
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

(channel) that the bottom UEA

module chassis flange must slide
into.
2. Tighten 2 captive screws to secure
the UEA module to the shelf, then
close the screw covers.
3. At the rear of the cabinet, slide the
termination assembly into the rear
of the UEA Processor Module until
fully seated. Note that the shelf
has a guide slot (channel) that the
bottom flange of the termination
assembly chassis must slide into.
4. Tighten 4 captive screws to secure
the termination assembly to the
UEA shelf.
5. Install the AC power cables into
the rear of the termination
assembly and fasten with 2 screws
per cable and external tooth lock
washers.
6. Repeat Steps 1-5 for the second
UEA box.
7. Apply power to the cabinet and
UEA(s).
REFERENCE: For detailed
information on UEA installation, see
the Experion LCN Hardware Upgrade
Kit Instructions (51195195-415).

ATTENTION: Before connecting the FTE cables, power-on the UEA boxes and
make sure that the factory-shipped UEA boxes are configured with “0” as the
Device Index.

8 Connect the FTE cables between the

UEA’s FTE ports and the L2 ports on
the FTE switch.

ATTENTION: Make sure that

237
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

you have the following L2 port

configurations for the FTE
switches connected to the
ELCN nodes.
“Network Speed” set to AUTO
“Communication Type” set to
FULL DUPLEX

9 Perform a startup of the intended

Primary ELCN-ENIM UEA box (to be
node 41).
Each UEA must have a Device Index
that is unique in the FTE community.
You enter the Device Index through
the front panel display at the physical
UEA box. At a high level, the user
must do the following from the front
panel of the UEA box:

l On the UEA front panel, rotate the

key clockwise to the C position to
enter the CONFIG menu.
l Configure the FTE Device Index.

NOTE: Set the same odd-

numbered device index (41) as
the Classic Primary ENIM for
the intended Primary ELCN-
ENIM.

l Change the BOOTP setting from

NO to YES.
l Save these changes (this reboots
the box and the UEA will get its
FTE IP Address from the Experion
BOOTP Server.)
l After the reboot, node transitions

238
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

into the “Alive” state.

For more information, refer to section
“"To Set the Device Index Using the
UEA Front Panel" on page 100”.

10 Verify that the node is in the Alive

state at the UEA Front Panel Display.

NOTE: The Native Window

System Status Display will still
show the node in the OFF
state.

11 Using the Firmware Manager Tool,

flash the Application personality
image followed by the
UEARECOVERY personality image to
the node.
For more information, see section
“"Node flashing procedure for a UEA
node coming from the factory with
only the Boot Recovery image" on
page 109”.

NOTE: You can optionally

upgrade the UEARECOVERY
personality image only if the
factory-shipped image is not at
the latest version.

RESULT: After the node reboots, it

goes to the “NotLoaded” state.

12 In Control Builder, click File > New >

ELCN and then click ELCN_NODE –
ELCN Appliance Node.

239
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

RESULT: The configuration form

opens with the Main tab selected.
ENIM configuration form - Main tab:

13 Under the Main tab, enter the

following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device

index (41) here which you have
configured on the UEA box.

l Under the ELCN Node Type drop-

down list, select ENIM
l ENIM UCN Node Number

240
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: Enter the UCN Node

Number of the Primary ELCN
ENIM.

l Select the Module is redundant

checkbox.

NOTE: The Device Index, IP

Address, and UCN Node
Number are all incremented by
one (1) for the backup. These
are not changeable by the user.

l ELCN Multicast Address

NOTE: It is highly
recommended that you use the
default ELCN Multicast
Address. Verify that it matches
the value as configured for the
ELCN Bridge(s).

l LCN Node Number –This

NOTE: Enter the LCN Node

Number of the ELCN ENIM
with the odd-numbered device
index.

When assigning or changing the LCN

node number of any LCN or ELCN
node, it is imperative that the
intended node number is not already
in use by another LCN or ELCN node.
If you cause a duplicate node number
situation to occur, the invalid
duplicate node fails, and the existing

241
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

running node may become ISOLATED

from some LCN and ELCN nodes. To
recover from this situation, you must
power-off the invalid node, change its
LCN node number to an unused LCN
address, power it back on, and reload
the existing running node which may
have become ISOLATED.

l LCN Node Number – Partner

NOTE: Enter the LCN Node

Number of the ELCN ENIM
with the even-numbered device
index. At this point in time, this
is the LCN Node Number of the
Classic ENIM (node 42).

14 After configuring the parameters,

click OK to accept the changes.
RESULT: The Primary and Backup
ELCN-ENIM blocks are entered into
the ERDB. The Tag Names and icons
appear on the Project side/tab, ready
for loading.

15 On the Project tree of Control Builder,

select the Primary ELCN-ENIM block
to be loaded.

ATTENTION: Do not load the

Backup ELCN-ENIM block at
this point of time as the
Backup UEA box is not
configured yet.

242
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

16 Right-click and then select Load, or

click on the Control Builder toolbar.

RESULT: The Load Operation dialog

box appears.

17 Click the Load button to confirm the

operation.

NOTE: Another dialog box

“Parameter Comparison and
Reconciliation [Load] –
[Project]” may appear, click to
proceed.

RESULT: The Control Builder loads

the block to the primary node. The
operation of the Primary ELCN-ENIM
(node 41) is activated.
The Primary ELCN-ENIM node

243
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

transitions to the PWR_ON state (as

viewed from the Native Window) with
Redundancy Role as “PRIMARY” (CEP
state).

Experion Bridge Status Display when

node 41 is in the PWR_ON state and
not loaded:

Native Window - Process Networks

Node Status Display when in the
PWR_ON state:

18 From the Native Window System

Status Display, load the ELCN-ENIM
from the NET or Emulated Drive to
which you had saved the checkpoint
earlier.
To load the node (TPN/ LCN
Personality), select the node and click
LOAD SELECT and press Enter.
RESULT: The node’s status

244
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

transitions to NET_LD, and then

BACKUP after the load is complete.

NOTE: Wait for at least 7

minutes after the node
transitions to the BACKUP
state.

The Control Builder shows the Node

State as “BACKUP-NOSYNC” (where
“BACKUP” is the LCN redundancy
state on the Native Window and
“NOSYNC” is the CEP redundancy
state of the UEA box since it does not
have a Backup at this time) and
Redundancy Role as “PRIMARY” (CEP
state of the UEA box).

You may need to perform a refresh on

the Experion Detail Display to update
the node status.
Experion Bridge Status Display when
node 41 is in the BACKUP-NOSYNC
state:

For UVA-based ELCN ENIM, refer the

following screenshot for Experion
Bridge Status Display

245
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

RESULT: You have now successfully migrated your Classic Backup ENIM to ELCN-
ENIM.
At this point in time, the Classic ENIM (node 42) is running as the primary node and
in the “OK” state on the Native Window and the ELCN-ENIM (node 41) is running as
the secondary node and in the “BACKUP” state on the Native Window.

Native Window - Process Networks Node Status Display after migrating the Classic
Backup ENIM to ELCN-ENIM:

To migrate the remaining Classic ENIM to ELCN ENIM, perform the procedures in
the next section.

On-process migration from Classic Primary ENIM to

ELCN-ENIM
Perform the following procedures to perform an orderly
shutdown of the Classic Primary ENIM to migrate to ELCN-
ENIM.
The following sequence of shutting down the Classic Primary
ENIM node (thrice, to place it into the OFF state) must be done
quickly so that the previously-installed ELCN-ENIM takes over
as the primary on the Native Window.

Step Action Done

ATTENTION: Before performing this procedure, make sure that migration of

246
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

the Classic Backup ENIM to ELCN-ENIM has been accomplished.

1 At a station (for example, US or ES-T),

perform a SHUT DOWN of the Classic
Primary ENIM (node 42 in the
example displays that follow) from the
Native Window System Status display.
Select the node and select the SHUT
DOWN target and press Enter.
RESULT: This causes an “orderly”
shutdown to the QUALIF state.

NOTE: Beginning with TPN

R690 or later, the following
changes are applicable:
l For a primary node in
aredundant configuration,
which is an ELCN (UEA/UVA
only) node, the system will
actually send two SHUT
DOWN commands,
automatically.
l This applies only when the
SHUT DOWN command is
issued at the primary node
of a ELCN UEA/UVA. This is
done because when a SHUT
DOWN command to a
primary UEA/UVA node is
issued, the UEA/UVA node
reboots and sends a second
SHUT DOWN command
which takes the node to an
OFF state while the
UEA/UVA node reboots to
the PWR_ON state.

2 Shut down the Classic Primary ENIM

from the Native Window for the

247
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

second time to place it into the FAIL

state.

ATTENTION: If the NIM Node is

not shut down two (2) times
and placed into the "FAIL" state,
and then powered OFF, the
LCN will still be looking for that
node in the token for 1 minute
and 57 seconds (it takes 1
minute and 57 seconds before
the system will eventually
ISOLATE the node.). During this
time, the system is extremely
sluggish (if not placed in the
“FAIL” state).

Experion Bridge Status Display when

node 42 is in the FAIL state:

For UVA-based ELCN ENIM, refer the

following screenshot for Experion
Bridge Status Display.

3 Power-off the Primary ENIM by

placing the LCN chassis power supply
switch in the OFF position. This node
is in the FAIL state as shown on the
System Status Display or Node Status
Display.

248
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ATTENTION: Do not
accidentally power-off the
wrong ENIM. If it is a DNCF,
use the arrows to identify the
appropriate power switch.

4 Shut down the Primary ENIM from

the Native Window for the third time
to transition from the FAIL state to
the OFF state.

ATTENTION: At this point in

time, wait for at least 70
seconds before you perform a
startup of the Backup ELCN-
ENIM.

RESULT: At this point in time, the

ELCN-ENIM (node 41) takes over as
the primary and transitions to the
“WARN” state on the Native Window.

Experion Bridge Status Display when

node 42 is in the OFF state:

Native Window - Process Networks

Node Status Display when node 42 is

249
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

in the OFF state:

5 Make sure you connect an Ethernet

crossover cable between the
redundancy ports of the primary and
backup UEA boxes.

6 Perform a startup of the intended

Backup ELCN-ENIM UEA box.
Each UEA must have a Device Index
that is unique in the FTE community.
You enter the Device Index through
the front panel display at the physical
UEA box. At a high level, the user
must do the following from the front
panel of the UEA box:

l On the UEA front panel, rotate the

key clockwise to the C position to
enter the CONFIG menu.
l Configure the FTE Device Index.

NOTE: Set the same even-

numbered device index as the
Classic Backup ENIM for the
intended Backup ELCN-ENIM.

l Change the BOOTP setting from

NO to YES.
l Save these changes (this reboots
the box and the UEA will get its
FTE IP Address from the Experion
BOOTP Server.)
l After the reboot, node transitions
into the “Alive” state.
For more information, refer to section
“"To Set the Device Index Using the

250
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

UEA Front Panel" on page 100”.

7 Verify that the node is in the Alive

state at the UEA Front Panel Display.

NOTE: The Native Window

System Status Display will still
show the node in the OFF state.

8 Using the Firmware Manager Tool,

flash the Application personality
image followed by the UEARECOVERY
personality image to the node.
For more information, see section
“"Node flashing procedure for a UEA
node coming from the factory with
only the Boot Recovery image" on
page 109”.
RESULT: After the UEA box reboots,
the intended Backup ELCN-ENIM
goes to the “PWR_ON” state.

ATTENTION: For a redundant

pair of ELCN Appliance Nodes,
if you select and load only the
Primary platform block in
Control Builder, be aware that
both the Primary and the
Backup will transition to the
PWR_ON state in the Native
Window upon Primary load
(provided the backup hardware
is available with the Ethernet
crossover cable connected).

9 On the Project tree of Control Builder,

select the Secondary ELCN-ENIM
block to be loaded.

251
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: You had already created

this block when you created the
primary block.

10 Right-click and then select Load, or

click on the Control Builder toolbar.

RESULT: The Load Operation dialog

box appears.

11 Click the Load button to confirm the

operation.
RESULT: The Control Builder loads
the block to the backup node. The
operation of the Backup ELCN-ENIM
is activated.
The Backup ELCN-ENIM node (42)
transitions to the PWR_ON state.

252
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Experion Bridge Status Display when

node 42 is in the PWR_ON state.

For UVA-based ELCN, refer the

following screenshot for Experion
Bridge Status Display

Native Window - Process Networks

Node Status Display when in the
PWR_ON state:

12 From the Native Window System

Status Display, load the ELCN-ENIM
from the NET (or Emulated Drive, to
which you had saved the checkpoint
earlier.
To load the node (TPN/ LCN
Personality), select the node and click
LOAD SELECT and press Enter.
RESULT: The node’s status

253
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

transitions to NET_LD, and then

BACKUP after the load is complete.

NOTE: Wait for at least 7

minutes after the node
transitions to the BACKUP
state.

The Control Builder shows the Node

State as “BACKUP” (where “BACKUP”
is the LCN redundancy state on the
Native Window) and Redundancy Role
as “SECONDARY” (CEP state of the
UEA box).

13 In the case of a redundant UEA-based

or UVA-based ELCN Appliance node,
during an onprocess migration from
any pre-R501.6 release to R501.6 or
later version, an additional switch
over is required to complete the
migration. Beginning with R501.6, a
soft failure indicator, “Deployment
Incomplete”, appears on the Soft
Failures tab of an ELCN Node Control
Builder block which indicates this
switch over has not been completed.
This is not applicable for migration
from R501.6 onwards to any later
release.

RESULT: You have now successfully migrated your Classic Primary ENIM to ELCN-

254
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ENIM. You may need to perform a refresh on the Experion Detail Display to update
the node status.
Experion Bridge Status Display after migrating the Classic Primary ENIM to ELCN-
ENIM (node 42):

For UVA-based ELCN ENIM, refer the following screenshot

Native Window - Process Networks Node Status Display after migrating the Classic
Primary ENIM to ELCN-ENIM:

ATTENTION: After ensuring that the Primary and Secondary ELCN-ENIMs are
communicating over FTE and there is no need to go back to Classic ENIMs,
you can decommission them.
For more information, see section “Decommission/Recommission Nodes”.

ATTENTION: Make sure that the ELCN-ENIMs are functioning correctly and
then checkpoint the Primary ELCN-ENIM.

255
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Backing out of ELCN-ENIM to Classic ENIM

This section assists you in performing on-process migration
back to Classic ENIMs from ELCN-ENIMs. You can perform
this procedure if you encounter any problem during or after
Classic ENIMs to ELCN-ENIMs migration and you would like to
go back to the original Classic ENIMs.

ATTENTION: Make sure the LCN node(s) is(are) installed

and ready to be powered up and loaded before performing
this procedure.

ATTENTION: Perform this procedure first on the Backup

ELCN-ENIM (with even-numbered Device Index) followed
by the Primary ELCN-ENIM (with odd-numbered Device
Index).

Done
Step Action
(√)
1 At a station (for example, US or ES-T), perform a SHUT DOWN of
the Backup ELCN-ENIM (with even-numbered Device Index) node
from the Native Window System Status display. Select the node
and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

2 Shut down the node from the Native Window for the second time
to place it into the FAIL state.

3 In Control Builder, select the Backup ELCN-ENIM platform block

from the Monitoring tree.

4 Right-click on the block and click Delete.

At the Delete Selected Object(s) confirmation dialog box, click
Continue.
Click Delete Selected Object(s).
RESULT: The ELCN-ENIM platform block is deleted from the
Monitoring tree.

5 Loosen the threaded captive screws in counter-clockwise

direction and pull-out the UEA box (but leave the box in the
chassis) from the chassis until the power supply is interrupted.

256
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)

NOTE: Use the handles to slide the UEA box.

6 Repeat Step 4 to delete the block from the Project tree.

NOTE: You may wish to retain this block in the Project side
for ease of going back to the ELCN-ENIM node.

7 Shut down the node from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at least 70 seconds before you
power-on the Classic Backup ENIM.

8 Power-on the Classic Backup ENIM (with even-numbered Device

Index) by placing the LCN chassis power supply switch in the ON
position.

9 Using the Native Window System Status Display, verify that the
node transitions to the PWR_ON state.

10 From the Native Window System Status Display, load the Classic
Backup ENIM using the checkpoint saved in the NET (or
Emulated Drive).
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status transitions to NET_LD, and then
BACKUP after the load is complete.

NOTE: Wait for at least 7 minutes after the node transitions

to the BACKUP state.

RESULT: You have now successfully migrated back to Backup Classic ENIM from
Backup ELCN-ENIM.

Perform the following procedure to migrate back to Classic Primary ENIM from
Primary ELCN-ENIM (with odd-numbered Device Index).
The following sequence of shutting down the Primary ELCN-ENIM (thrice, to place it
into the OFF state) must be done quickly so that the Classic Primary ENIM (with

257
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
odd-numbered Device Index) takes over as the primary on the Native Window.

11 At a station (for example, US or ES-T), perform a SHUT DOWN of

the Primary ELCN-ENIM (with odd-numbered Device Index) node
from the Native Window System Status display. Select the node
and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.
The Classic Backup will transition to the WARN state.

12 Shut down the node from the Native Window for the second time
to place it into the FAIL state.

13 In Control Builder, select the Primary ELCN-ENIM platform block

from the Monitoring tree.

14 Right-click on the block and click Delete.

RESULT: The ELCN-ENIM platform block is deleted from the
Monitoring tree and the UEA box reboots.

15 While the node reboots, loosen the threaded captive screws in

counter-clockwise direction and pull-out the UEA box (but leave
the box in the chassis) from the chassis until the power supply is
interrupted.

NOTE: Use the handles to slide the UEA box.

16 Repeat Step 14 to delete the block from the Project tree.

NOTE: You may wish to retain this block in the Project side
for ease of going back to the ELCN-ENIM node.

17 Shut down the node from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at least 70 seconds before you
power-on the Classic ENIM with the odd-numbered Device Index.

18 Power-on the Classic ENIM (with odd-numbered Device Index) by

placing the LCN chassis power supply switch in the ON position.

258
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
19 Using the Native Window System Status Display, verify that the
node transitions to the PWR_ON state.

20 From the Native Window System Status Display, load the Classic
ENIM with the odd-numbered Device Index using the checkpoint
saved in the NET (or Emulated Drive).
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then
BACKUP after the load is complete. At this point of time, the
Classic ENIM with the even-numbered Device Index will transition
from the WARN state to the OK state.

RESULT: You have now successfully migrated back to Classic ENIM redundant pair
from Primary ELCN-ENIM redundant pair.

Migration from Classic EPLCG to Experion LCN

EPLCG
This section describes the off-process migration from Classic
EPLCG to ELCN-EPLCG.
You must have minimum of Experion R501.4 and TPN R688.1
installed. This involves upgrading the firmware (for both UEA
RECOVERY and APP images) of ELCN-EPLCG.
UEAs shipped from the factory have UEA RECOVERY firmware
and no APP firmware image. The factory-shipped UEA has the
firmware version UEA_100.1-11.0.

NOTE: The first time you load firmware on a UEA box, load
the Application personality image before the Boot/Recovery
(UEARECOVERY) personality image. The Firmware
Manager Tool will not overwrite the existing
UEARECOVERY personality image until an Application
personality image (UEAELCN_NODE) is present and
available to the UEA. The UEAELCN_NODE application

259
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

image is available for download using the Firmware

Manager.

ATTENTION: Migration from Classic EPLCG to an ELCN-

EPLCG requires powering-off the classic node. Perform this
activity at an appropriate time to avoid disturbance to the
process and potentially hazardous consequences to
equipment and personnel. Determine in advance that the
scheduling of this procedure is in accordance with proper
system operation.

Prerequisites
Before you migrate from Classic EPLCG to ELCN-EPLCG,
ensure that the prerequisites described in section
“Prerequisites for ELCN UEA Appliance Node migration” are
complied with.

Classic EPLCG shutdown

Perform the following procedure to perform an orderly
shutdown of the Classic EPLCG to migrate to ELCN-EPLCG.
This procedure shuts down a single EPLCG (node 65 in the
example displays) to migrate this single node to ELCN EPLCG.
This procedure may be repeated for a redundant EPLCG also,
when migrating redundant EPLCGs to ELCN.

Done
Step Action
(√)
1 From the Native Window System Status Display, select the chosen
EPLCG (node 65 in the example display below), then select the
SAVE SELECT target and press Enter. Save the checkpoint to NET.

260
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)

ATTENTION: It is highly recommended that you also save

the EPLCG checkpoint into an Emulated Drive as well, to
have a second source of a known good checkpoint.
You can restore this checkpoint in case you want to migrate
back from ELCN-EPLCG to Classic EPLCG due to any issues
found during or after Classic EPLCG to ELCN-EPLCG
migration.

2 At a station (for example, US or ES-T), perform a SHUT DOWN of

the EPLCG from the Native Window System Status display. Select
the node and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

261
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)

3 Shut down the Classic EPLCG from the Native Window for the
second time to place it into the FAIL state.

ATTENTION: If the node is not shut down two (2) times and
placed into the "FAIL" state, and then powered OFF, the LCN
will still be looking for that node in the token for 1 minute
and 57 seconds (it takes 1 minute and 57 seconds before
the system will eventually ISOLATE the node.). During this
time, the system is extremely sluggish (if not placed in the
“FAIL” state).
The best practice is to always shut down the node that is to
be powered down, two (2) times to place it in the "FAIL"
state. Then power it down and perform the required work so
the LCN can communicate normally.

Experion Bridge Status Display when the node is in the FAIL state:

4 Power-off the node by placing the LCN chassis power supply

switch in the OFF position. This node is in the FAIL state as shown

262
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
on the System Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off the wrong node.

If it is a DNCF, use the arrows to identify the appropriate
power switch.

5 Shut down the node from the Native Window for the third time to
transition from the FAIL state to the OFF state.

Experion Bridge Status Display when the node is in the OFF state:

6 If migrating redundant EPLCGs to ELCN, repeat Steps 2-5 to shut

down the remaining redundant EPLCG.

Installing UEA
Install the UEA hardware as described in the referenced
document below. For redundant EPLCG migration, install a pair
of UEA boxes.

263
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

REFERENCE: For information on UEA installation specific to

EPLCG nodes, see the Experion LCN Hardware Upgrade Kit
Instructions (51195195-415).

Installing FTE switches

Install FTE switch(es) as needed, as described in the referenced
document below.
REFERENCE: For information on mounting and configuring
the Ethernet switches for the ELCN, see the FTE Switch used
with LCN cabinet Upgrade Kit instructions (51195195-384).
After FTE switch installation, connect the FTE cables between
the UEA FTE ports and the L2 ports on the FTE switch.

Startup of UEA
Each UEA must have a Device Index that is unique in the FTE
community. You enter the Device Index through the front panel
display at the physical UEA box. At a high level, the user must
do the following from the front panel of the UEA box:
n On the UEA front panel, rotate the key clockwise to the C
position to enter the CONFIG menu.
n Configure the FTE Device Index.

NOTE: Always set an odd-numbered device index for a

single ELCN-EPLCG, or for the Primary ELCN-EPLCG in a
redundant installation. In a redundant installation, connect
the protocol cable connector marked as “Primary” to the
odd-numbered UEA.

n Change the BOOTP setting from NO to YES.

n Save these changes (this reboots the box and the UEA will
get its FTE IP Address from the Experion BOOTP Server.)
n After the reboot, node transitions into the “Alive” state.
For detailed procedures, refer to section “"To Set the Device
Index Using the UEA Front Panel" on page 100”.

264
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Migrating from Non-Redundant Classic EPLCG to

ELCN-EPLCG
Perform the following procedure to migrate from a Non-
Redundant Classic EPLCG to ELCN-EPLCG.

Step Action Done(√)

1 Verify that the node is in the Alive state at the UEA

Front Panel Display.

NOTE: The LCN will still show the EPLCG node

in the OFF state.

2 Using the Firmware Manager Tool, flash the

Application personality image followed by the
UEARECOVERY personality image to the node.
For more information, see section “"Node flashing
procedure for a UEA node coming from the factory
with only the Boot Recovery image" on page 109”.
RESULT: After the node reboots, it goes to the
“NotLoaded” state.

3 In Control Builder, click File > New > ELCN and then
click ELCN_NODE – ELCN Appliance Node.

RESULT: The configuration form opens with the Main

tab selected.
EPLCG configuration form - Main tab:

265
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

4 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index here which

you have configured on the UEA box.

l Under the ELCN Node Type drop-down list, select

EPLCG
l Do not enter an ENIM UCN Node Number.
l Do not select the Module is redundant checkbox.
l ELCN Multicast Address

NOTE: Make sure that you have the same ELCN

Multicast Address as configured for the ELCN
Bridge(s).

l LCN Node Number – This

NOTE: Enter the LCN Node number of the

266
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

EPLCG you are migrating to ELCN.

When assigning or changing the LCN node number of

any LCN or ELCN node, it is imperative that the
intended node number is not already in use by
another LCN or ELCN node.
If you cause a duplicate node number situation to
occur, the invalid duplicate node fails, and the existing
running node may become ISOLATED from some LCN
and ELCN nodes. To recover from this situation, you
must power-off the invalid node, change its LCN node
number to an unused LCN address, power it back on,
and reload the existing running node which may have
become ISOLATED.

l Do not enter an LCN Node Number – Partner

5 Select the EPLCG tab.

EPLCG configuration form - EPLCG tab:

NOTE: For Allen Bradley Configuration 4, it is

mandatory to configure the Channel 2 Port
settings to match the Channel 1 Port settings
even though Port 2 is not used. The redundant
EPLCG firmware uses Port 2 to “listen” to
outgoing messages while Port 1 is receiving

267
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

messages. Any mismatch in Port 1 and Port 2

settings will affect the functionality.

6 Under the EPLCG tab, enter the following from the

drop-down menus for Channel 1 Port Configuration
and Channel 2 Port Configuration as appropriate:

l Baud Rate
l Parity

NOTE: By default, the Baud Rate value is set to

9600 and Parity is set to ODD, you must
manually set the Baud Rate and Parity values
as per the Baud Rate and Parity settings made
using the TS2 jumpers on the EPLCI board to
establish communication with PLCs.

In this case, set the Channel 1 Port Configuration’s

and Channel 2 Port Configuration’s Baud Rate values
to 9600 and Parity values to EVEN to match the
EPLCI board’s TS2 JUMPERS settings as shown in the
following image.

Select the following checkboxes as appropriate:

l Redundant Communications
l Multi-Buffer Pipelining
l User Output Suppression

268
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

7 After configuring the parameters, click OK to accept

the changes.
RESULT: The ELCN-EPLCG block is entered into the
ERDB. The Tag Name and icon appear on the Project
side/tab, ready for loading.

8 On the Project tree of Control Builder, select the block

to be loaded.

9
Right-click and then select Load, or click on the
Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

10 Click the Load button to confirm the operation.

269
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

RESULT: The Control Builder loads the block to the

node. The operation of the ELCN-EPLCG is activated.

10 cont The ELCN-EPLCG node transitions to the PWR_ON

state.

Experion Bridge Status Display when the node is in

the PWR_ON state:

270
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

11 From the Native Window System Status Display, select

the EPLCG (in the PWR_ON state shown below), and
load the ELCN-EPLCG from the NET (or from the
Emulated Drive to which you had saved the
checkpoint earlier).
To load the node (TPN/LCN Personality), select the
node and click LOAD SELECT and press Enter.

RESULT: The node’s status will transition to NET_LD,

and then to OK after the load is complete.

271
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

12 After loading the HG checkpoint, the emulated EPLCG

DHP boxes which are available under the NTWK/HWY
STATUS will remain in the ADDR ERR state, you
should manually clear them using the INIT ADDR
operation, click NTWK/HWY STATUS > HIWAY CMND >
INIT ADDR. This step is crucial for loading the box
checkpoint successfully.

13 After the INIT ADDR operation, select the EPLCG node

(line 8 as shown in the following image) and click
LOAD DATA > START FUNCTION. The box must be

272
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

loaded from the same checkpoint source as

mentioned in Step 11.

RESULT: The box’s status transitions to the OK state.

RESULT: You have now successfully migrated your Classic EPLCG to ELCN-EPLCG.
You may want to check the Experion Detail Displays and Control Builder “Main Tab”
to verify that they are reflecting the OK state. You may need to perform a refresh on
the Experion Detail Display to update the node status.

ATTENTION: After ensuring that the node is communicating over FTE and
there is no need to go back to Classic EPLCG, you can decommission this
node.
For more information, see section “Decommission/Recommission Nodes”.

ATTENTION: Make sure that the ELCN-EPLCG is functioning correctly and

then checkpoint the ELCN-EPLCG.

273
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Migrating from Redundant Classic EPLCG to ELCN-

EPLCG
Perform the following procedure to migrate from a redundant
Classic EPLCG pair to ELCN-EPLCG.

Step Action Done(√)

1 Verify that the nodes are in the Alive state at the UEA
Front Panel Displays.

NOTE: The LCN will still show the EPLCG nodes in

the OFF state.

2 Using the Firmware Manager Tool, flash the Application

personality image followed by the UEARECOVERY
personality image to the node.
For more information, see section “"Node flashing
procedure for a UEA node coming from the factory with
only the Boot Recovery image" on page 109”.
RESULT: After the node reboots, it goes to the
“NotLoaded” state.

3 In Control Builder, click File > New > ELCN and then click
ELCN_NODE – ELCN Appliance Node.

3 cont RESULT: The configuration form opens with the Main

tab selected.
EPLCG configuration form - Main tab:

274
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

4 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index here which

you have configured on the UEA box.

l Under the ELCN Node Type drop- down list, select

EPLCG
l Do not enter an ENIM UCN Node Number.
l Select the Module is redundant checkbox.
l ELCN Multicast Address

NOTE: Make sure that you have the same ELCN

Multicast Address as configured for the ELCN
Bridge(s).

l LCN Node Number – This

275
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

NOTE: Enter the LCN Node number of the Primary

EPLCG.

When assigning or changing the LCN node number of

any LCN or ELCN node, it is imperative that the intended
node number is not already in use by another LCN or
ELCN node.
If you cause a duplicate node number situation to occur,
the invalid duplicate node fails, and the existing running
node may become ISOLATED from some LCN and ELCN
nodes. To recover from this situation, you must power-
off the invalid node, change its LCN node number to an
unused LCN address, power it back on, and reload the
existing running node which may have become
ISOLATED.

l LCN Node Number – Partner

NOTE: Enter the LCN Node number of the Backup

EPLCG.

5 Select the EPLCG tab.

EPLCG configuration form - EPLCG tab:

NOTE: For Allen Bradley Configuration 4, it is

276
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

mandatory to configure the Channel 2 Port

settings to match the Channel 1 Port settings
even though Port 2 is not used. The redundant
EPLCG firmware uses Port 2 to “listen” to
outgoing messages while Port 1 is receiving
messages. Any mismatch in Port 1 and Port 2
settings will affect the functionality.

6 Under the EPLCG tab, choose the appropriate options

from the drop-down menus for Channel 1 Port
Configuration and Channel 2 Port Configuration:

l Baud Rate
l Parity

NOTE: By default, the Baud Rate value is set to

9600 and Parity is set to ODD, you must manually
set the Baud Rate and Parity values as per the
Baud Rate and Parity settings made using the TS2
jumpers on the EPLCI board to establish
communication with PLCs.

In this case, set the Channel 1 Port Configuration’s and

Channel 2 Port Configuration’s Baud Rate values to
9600 and Parity values to EVEN to match the EPLCI
board’s TS2 JUMPERS settings as shown in the
following image.

Select the following checkboxes as appropriate:

277
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

l Redundant Communications
l Multi-Buffer Pipelining
l User Output Suppression

7 After configuring the parameters, click OK to accept the

changes.
RESULT: The Primary and Backup ELCN-EPLCG blocks
are entered into the ERDB. The Tag Names and icons
appear on the Project side/tab, ready for loading.

8 On the Project tree of Control Builder, select the Primary

ELCN-EPLCG block and Backup ELCN-EPLCG blocks to
be loaded.

9
Right-click and then select Load, or click on the
Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

10 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the blocks to the
primary and backup nodes. The operation of both the
Primary and Backup ELCN-EPLCG are activated.

10 cont The ELCN-EPLCG nodes transition to the PWR_ON state

(Native Window). Node 65 is shown below as an example.

278
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

Experion Bridge Status Display when nodes are in the

PWR_ON state:

11 From the Native Window System Status Display, load the

Primary ELCN-EPLCG (node 65 in below display) from
the NET (or from the Emulated Drive to which you had
saved the checkpoint earlier).
To load the node (TPN/LCN Personality), select the node
and click LOAD SELECT and press Enter.
RESULT: The node’s status will transition to NET_LD,
and then to WARN after the load is complete.

279
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

11 cont The Control Builder shows the Node State as “WARN”

and Redundancy Role as “PRIMARY”.

12 From the Native Window System Status Display, load the

Backup ELCN-EPLCG (with even-numbered Device
Index) from the NET. To load the node, select the node
and click LOAD SELECT and press Enter.
RESULT: The node’s status will transition to NET_LD,
and then BACKUP after the load is complete. The
Primary ELCN-EPLCG will now transition to the OK
state.

280
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

Experion Bridge Status Display when nodes are in the

OK and BACKUP state respectively.

13 After loading the HG checkpoint, the emulated EPLCG

DHP boxes which are available under the NTWK/HWY
STATUS will remain in the ADDR ERR state, you should
manually clear them using the INIT ADDR operation,
click NTWK/HWY STATUS > HIWAY CMND > INIT ADDR.
This step is crucial for loading the box checkpoint
successfully.

281
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

14 After the INIT ADDR operation, select the EPLCG nodes

and click LOAD DATA > START FUNCTION. The box must
be loaded from the same checkpoint source as
mentioned in Step 12.

RESULT: The box’s status transitions to the OK state.

15 In the case of a redundant UEA-based or UVA-based

ELCN Appliance node, during an onprocess migration
from any pre-R501.6 release to R501.6 or later version,

282
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done(√)

an additional switch over is required to complete the

migration. Beginning with R501.6, a soft failure
indicator, “Deployment Incomplete”, appears on the Soft
Failures tab of an ELCN Node Control Builder block
which indicates this switch over has not been completed.
This is not applicable for migration from R501.6 onwards
to any later release.

RESULT: You have now successfully migrated your Classic EPLCG redundant pair to
ELCN-EPLCG redundant pair.

ATTENTION: After ensuring that the nodes are communicating over FTE and
there is no need to go back to Classic EPLCG, you can decommission them.

For more information, see section “"Decommission/Recommission Nodes" on

page 489”.

ATTENTION: Make sure that the ELCN-EPLCGs are functioning correctly and
then checkpoint the Primary ELCN-EPLCG.

Backing out of ELCN-EPLCG to Classic EPLCG

This procedure assists you in migrating from ELCN-EPLCG to
Classic EPLCG if you encounter a problem during, or after,
Classic EPLCG to ELCN-EPLCG migration, and you would like
to go back to the original Classic EPLCG.

ATTENTION: Make sure the LCN node(s) is(are) installed

and ready to be powered up and loaded before performing
this procedure.

Done
Step Action
(√)
1 At a station (for example, US or ES-T), perform a SHUT DOWN of
the node from the Native Window System Status display. Select
the node and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

283
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)

NOTE: Beginning with TPN R690 or later, the following

changes are applicable:
l For a primary node in a redundant configuration, which
is an ELCN (UEA/UVA only) node, the system will
actually send two SHUT DOWN commands,
automatically.
l This applies only when the SHUT DOWN command is
issued at the primary node of a ELCN UEA/UVA. This is
done because when a SHUT DOWN command to a
primary UEA/UVA node is issued, the UEA/UVA node
reboots and sends a second SHUT DOWN command
which takes the node to an OFF state while the UEA/UVA
node reboots to the PWR_ON state.

2 Shut down the node from the Native Window for the second time
to place it into the FAIL state.

3 In Control Builder, select the ELCN-EPLCG platform block from

the Monitoring tree.

4 Right-click on the block and click Delete.

RESULT: The ELCN-EPLCG platform block is deleted from the
Monitoring tree and the UEA box reboots and transitions to the
“NotLoaded” state.

5 While the node reboots, loosen the threaded captive screws in

counter-clockwise direction and pull-out the UEA box (but leave
the box in the chassis) from the chassis until the power supply is
interrupted.

NOTE: Use the handles to slide the UEA box.

6 Repeat Step 4 to delete the block from the Project tree.

NOTE: You may wish to retain this block in the Project side
for ease of going back to the ELCN-EPLCG node.

7 Shut down the node from Native Window for the third time to
transition from the FAIL state to the OFF state.

284
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
8 Power-on the Classic EPLCG by placing the LCN chassis power
supply switch in the ON position.

9 Using the Native Window System Status Display, verify that the
node transitions to the PWR_ON state.

10 From the Native Window System Status Display, load the Classic
EPLCG using the checkpoint saved in the NET (or Emulated
Drive) earlier.
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then to
OK after the load is complete.

RESULT: You have now successfully migrated back to Classic EPLCG from ELCN-
EPLCG.

Migration from Classic EHB to Experion LCN

EHB
This section describes the on-process migration from Classic
EHB to ELCN-EHB.

Prerequisites
Before you migrate from Classic EHB to ELCN EHB, ensure
that the prerequisites described in section “Prerequisites for
ELCN UEA Appliance Node migration” are complied with.
The following info graphic depicts high-level overview of the
major stages in on-process migration from Classic EHB to
ELCN EHB.

285
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Note that this infographic just provides the high-level overview,

for step-by-step procedure, refer section “Migrating from
Classic EHB to Experion LCN EHB”.

ATTENTION: The Experion C300 controllers supported for

Hiway Emulations are C300 (CC-PCNT01) and C300 (CC-
PCNT02). C300 (CC-PCNT05) is not supported for Hiway
Emulations.

On-process migration from Classic EHB to Experion

LCN EHB

On-process migration from Classic EHB to Experion LCN EHB

A typical EHB simple gateway connected on the LCN looks as
shown in the following figure.

286
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

The existing coax LCN based EHB already has a platform block
that is used to download the Hiway configuration parameters to
the EHBI. This is referred to as “Classic EHB Platform block’. As
part of ELCN-EHB, ELCN Appliance node platform block can
be configured as ELCN-EHB platform block.

Deleting EHB block

To delete an EHB block, it’s reference in C300 controller (CEE)
needs to be removed.
For removing the reference of any EHB block in C300 controller
(CEE), perform the following procedure:
1. From Native Window, shutdown the Primary and Backup
EHB. Wait for the status to transition to PWR_ON state.
2. From Control Builder Project side, under EHB
Communications tab, remove any EHB block references to
C300 CEE controller.
3. Download C300 from Project side to Monitoring side in
order for changes to take effect.
4. Delete the EHB block from Monitoring side.

ATTENTION: To delete EHB platform block from

monitoring side, remove the EHB reference from any
C300 configured with this EHB and then reload the
C300 to monitoring side.

5. Provide the reference of the EHB block in the new C300-

CEE controller in Project side.
6. Load the EHB blocks from Project side to Monitoring side.
7. Load the new C300 controller from Project side to
Monitoring side.
8. From native window, load the EHB nodes to OK/BACKUP
State.
Migrating Added EHB from Classic EHB to Experion LCN EHB
Added EHB allows two different EHBs, connected to the same
physical Hiway and to the same LCN, to share the total data
access load arising from the boxes on the Hiway. In this

287
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

arrangement, each EHB owns a mutually exclusive set of boxes.

Each EHB views the boxes it does not own as AddedEHB and
knows only enough about them to stay out of the way when the
partner EHB does primary data access.
There are two EHB node pairs: Defining Classic EHB and Non-
Defining Classic EHB.
To migrate from Added EHB to ELCN EHB, you must first
migrate the Non-Defining Classic EHB to ELCN EHB followed
by the Defining Classic EHB.
If the Define Physical Hiway parameter shows OFF, it is the
Non-Defining Classic EHB as shown in the following
screenshot. Consider the following, node EHB_59 as part of
Logical Hiway number 17.

When the Define Physical Hiway parameter is in ON state, it is

Defining Classic EHB as shown in the following screenshot.
EHB_57 is taken as an example with Logical Hiway number 1.

Perform the following procedure to migrate Non-Defining

Classic EHB to ELCN EHB.

288
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

1 In Control Builder, under the Project tree, double-

click the Primary Classic EHB block.

RESULT: The Primary Classic EHB block appears.

2 On the Main tab, under the EHB Migration

Configuration, select Enable OPM to ELCN
checkbox. (2)

This checkbox enables the deconfiguration of the

Classic EHB platform block from Control Builder.

NOTE: The Control Builder does not allow

deconfiguration or deletion of a platform
block when the device is running. Beginning

289
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

with Experion R501.4, this enforcement will

be relaxed for the case of EHB migration to
ELCN and back. Hence, this checkbox is
added.

3 Go to the Project tree, right-click Primary Classic

EHB, and then select , or click on the
Load
Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

4 In Native Window System Status display, make

sure that the node with an even-numbered device
index is running as the primary node.

290
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

5 Perform the SHUT DOWN of the odd-numbered

Classic Backup EHB from the Native Window
System Status display. Select the node, select the
SHUT DOWN target, and then press ENTER.
RESULT: This causes an “orderly” shutdown to the
QUALIF state.

6 Shut down the Backup Classic EHB from the

Native Window for the second time to place it into
the FAIL state.

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token for
1 minute and 57 seconds (it takes 1 minute
and 57 seconds before the system will
eventually ISOLATE the node.). During this

291
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

time, the system is extremely sluggish (if not

placed in the “FAIL” state).The best practice
is to always shut down the node that is to be
powered down, two (2) times to place it in
the "FAIL" state. Then power it down and
perform the required work so the LCN can
communicate normally.

Experion Bridge Status Display when node 59 is in

the FAIL state:

7 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This node
is in the FAIL state as shown on the System Status
Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

8 Shut down the Backup Classic EHB from the

Native Window for the third time to place it into the
OFF state.

9
ATTENTION: Note down the EHB
configuration details and export the block

292
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

configuration before removing the platform

block configuration. The exported block
configuration will be used as a reference if
there is a need to migrate back to Classic
EHB from ELCN-EHB.

In Control Builder, go to the Monitoring tree, right-

click the Primary Classic platform block, and then
click ForceDelete.

NOTE: The C300-EHB communication

remains uninterrupted and the box
emulations continue to be operational even
after the Classic EHB platform block
configuration is removed. However, the view
to EHB statistics and HDT communication
details will be lost.

10 Go to the Project tree, right-click the Primary

Classic EHB platform block, and then click Delete.

293
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

11 Install the primary UEA by performing the

following procedure:

1. At the front of the cabinet, slide one UEA

Processor Module into the shelf until fully
seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
2. Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw covers.
3. At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
4. Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
5. Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
6. Apply power to the cabinet and UEA.

294
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

REFERENCE: For detailed information on UEA

installation, see the Experion LCN Hardware
Upgrade Kit Instructions (51195195-415).

12 Configure the UEA with an odd-numbered device

index. The device index for the UEA must be the
same as the one corresponding to the Classic EHB
that was shut down and powered-off.
Enter the device index through the front panel
display at the physical UEA box. At a high level, you
must do the following from the front panel of the
UEA box:
l On the UEA front panel, rotate the key clockwise
to the C position to enter the CONFIG menu.
l Configure the FTE Device Index.
This UEA with an odd-numbered device index
assumes the role of primary and gets the odd IP
address. At this point, it is not configured as EHB
yet, and is waiting to receive the platform
configuration.

NOTE: Do not accidently power-on the UEA

with an even-numbered device index.

Creating and Configuring ELCN-EHB platform blocks in Control Builder

13 In the Control Builder, go to the Project tree, click

Root > New > ELCN, and then click ELCN_NODE –
ELCN Appliance Node.

13 Cont RESULT: The configuration form opens with the

Main tab selected. ELCN-EHB configuration form

295
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

- Main tab:

13 Cont Under the Main tab, enter the following:

l Tag Name – Provide a Tag Name same as the
Classic EHB tag name.
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index (59) here

which you have configured on the UEA
box/Virtual Machine.

l Under the ELCN Node Type drop-down list,

select EHB
l Select the Module is redundant checkbox.

NOTE: Note the difference in term used to

denote the secondary block in the Classic
EHB and the ELCN EHB blocks. In the
Classic EHB Platform block the secondary
block was named with suffix of “_PTNR”
whereas in ELCN EHB suffix of “_SEC” is
used to denote the secondary block.

NOTE: The Device Index and IP Address are

incremented by one (1) for the backup.
These are not changeable by the user.

296
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l Logical Hiway Num – note that this entry must

match the entry made in the Classic EHB
platform block.
l Logical Hiway Num Partner – Hiway number for
the Defining Classic EHB.
l LCN Node Number –This

NOTE: Enter the LCN Node Number of the

ELCN EHB with the odd-numbered device
index (node 59).

When assigning or changing the LCN node

number of any LCN or ELCN node, it is imperative
that the intended node number is not already in
use by another LCN or ELCN node.If you cause a
duplicate node number situation to occur, the
invalid duplicate node fails, and the existing
running node may become ISOLATED from some
LCN and ELCN nodes. To recover from this
situation, you must power-off the invalid node,
change its LCN node number to an unused LCN
address, power it back on, and reload the existing
running node which may have become ISOLATED.
l LCN Node Number – Partner

NOTE: Enter the LCN Node Number of the

ELCN EHB with the even-numbered device
index. At this point in time, this is the LCN
Node Number of the Classic EHB (node 61).

14 After configuring the parameters, click OK to

accept the changes.
RESULT: The Primary and Backup ELCN-EHB
blocks are entered into the ERDB. The Tag Names
and icons appear on the Project side/tab, ready for
loading.

15 A delta sign will appear next to the Defining Classic

EHB on the project side as shown in the following

297
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

image. Reload the Defining Classic EHB and then

load the Non-Defining Classic EHB.

16 Go to the Project tree, right-click ELCN-EHB

platform block, and then select Load, or click
on the Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

17 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to the

Backup node. The operation of the Primary ELCN-
EHB is activated.

18 RESULT: On the Native Window System Status

display, the secondary node transitions to the
PWR_ON state.

19 From the Native Window System Status Display,

select the ELCN-EHB (in the PWR_ON state), click
LOAD SELECT, and press Enter.NOTE: The UEA
based ELCN-EHB is now the active Backup to the
Classic EHB node on the LCN side.

298
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

At this point, the ELCN-EHB statistics is visible on

the ELCNNODE platform block for EHB.

20 Wait for at least 5 minutes, and then from the

Native Window System Status display, perform the
SHUT DOWN of the Classic EHB that is running as
primary to switch over to ELCN-EHB.
RESULT: The Classic EHB transitions to QUALIF
state, and ELCN-EHB will assume the role of
primary. The Emulated Hiway communication is
now routed through the ELCN-EHB.

21 Shut down the Classic EHB running as Primary

from the Native Window for the second time to
place it into the FAIL state.

299
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token for
1 minute and 57 seconds (it takes 1 minute
and 57 seconds before the system will
eventually ISOLATE the node.). During this
time, the system is extremely sluggish (if not
placed in the “FAIL” state).
The best practice is to always shut down the
node that is to be powered down, two (2)
times to place it in the "FAIL" state. Then
power it down and perform the required work
so the LCN can communicate normally.

Experion Bridge Status Display when node 61 is in

the FAIL state:

22 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This node
is in the FAIL state as shown on the System Status
Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

300
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

23 Shut down the Classic EHB running as primary

from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at

least 70 seconds before you perform a
startup of the Backup ELCN-EHB.

24 In Control Builder, on the EHB Communications

tab, in the Local EHB 1 section, change the
Tagname # to add an extra character, and then
click OK.

NOTE: The “Load values while Active” option

gets enabled only when there is a change in
the platform block.

25 Go to the Project tree, right-click CEEC300, and

then click Load Values while Active.

NOTE: Load Values while Active option re-

establishes the linkage of the CEE block with
the ELCN platform block internally. This
does not impact C300 emulations.

301
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

26 Install the secondary UEA by performing the

following procedure:

1. At the front of the cabinet, slide one UEA

Processor Module into the shelf until fully
seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
2. Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw covers.
3. At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
4. Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
5. Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
6. Apply power to the cabinet and UEA.
REFERENCE: For detailed information on UEA
installation, see the Experion LCN Hardware
Upgrade Kit Instructions (51195195-415).

27 Configure the UEA with an even-numbered Device

Index. The device index for the UEA must be the
same as the one corresponding to the Classic EHB

302
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

that was shut down and powered-off. Enter the

device index through the front panel display at the
physical UEA box. At a high level, you must do the
following from the front panel of the UEA box:
l On the UEA front panel, rotate the key clockwise
to the C position to enter the CONFIG menu.
l Configure the FTE Device Index.

This UEA with an even-numbered Device Index

assumes the role of secondary and gets the even
IP address.RESULT: The UEA with an even-
numbered Device Index transitions to PWR_ON
state.

28 From the Native Window System Status, select the

Secondary ELCN-EHB that is in PWR_ON state,
click LOAD SELECT, and press Enter. At this point,
both the EHBs are running on the ELCN side and
the coax EHBs that are powered-off can be
decommissioned.RESULT: The node with even-
numbered Device Index assumes role of the
Secondary ELCN-EHB.

Result: The Non-Defining Classic EHB is migrated to ELCN EHB.

303
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Perform the following procedure to migrate Defining Classic EHB to ELCN

EHB.

Step Action Done

1 In Control Builder, under the Project tree, double-

click the Primary Classic EHB block.

RESULT: The Primary Classic EHB block appears.

2 On the Main tab, under the EHB Migration

Configuration, select Enable OPM to ELCN
checkbox.

This checkbox enables the deconfiguration of the

Classic EHB platform block from Control Builder.

NOTE: The Control Builder does not allow

deconfiguration or deletion of a platform
block when the device is running.
Beginning with Experion R501.4, this
enforcement will be relaxed for the case of
EHB migration to ELCN and back. Hence,
this checkbox is added.

3 Go to the Project tree, right-click Primary Classic

304
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

EHB, and then select Load, or click on the

Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

4 In Native Window System Status display, make

sure that the node with an even-numbered device
index is running as the primary node.

5 Perform the SHUT DOWN of the odd-numbered

Classic Backup EHB from the Native Window
System Status display. Select the node, select the
SHUT DOWN target, and then press ENTER.
RESULT: This causes an “orderly” shutdown to the
QUALIF state.

6 Shut down the Backup Classic EHB from the

Native Window for the second time to place it into
the FAIL state.

305
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token
for 1 minute and 57 seconds (it takes 1
minute and 57 seconds before the system
will eventually ISOLATE the node.). During
this time, the system is extremely sluggish
(if not placed in the “FAIL” state).
The best practice is to always shut down
the node that is to be powered down, two
(2) times to place it in the "FAIL" state. Then
power it down and perform the required
work so the LCN can communicate
normally.

Experion Bridge Status Display when node 57 is

in the FAIL state:

7 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This
node is in the FAIL state as shown on the System
Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

8 Shut down the Backup Classic EHB from the

306
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Native Window for the third time to place it into

the OFF state.

9
ATTENTION: Note down the EHB
configuration details and export the block
configuration before removing the platform
block configuration. The exported block
configuration will be used as a reference if
there is a need to migrate back to Classic
EHB from ELCN-EHB.

In Control Builder, go to the Monitoring tree,

right-click the Primary Classic platform block, and
then click ForceDelete.

NOTE: The C300-EHB communication

remains uninterrupted and the box
emulations continue to be operational even
after the Classic EHB platform block
configuration is removed. However, the view
to EHB statistics and HDT communication
details will be lost.

10 Go to the Project tree, right-click the Primary

Classic EHB platform block, and then click Delete.

307
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

11 Install the primary UEA by performing the

following procedure:
l At the front of the cabinet, slide one UEA
Processor Module into the shelf until fully
seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
l Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw
covers.
l At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
l Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
l Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
l Apply power to the cabinet and UEA.
REFERENCE: For detailed information on UEA
installation, see the Experion LCN Hardware
Upgrade Kit Instructions (51195195-415).

12 Configure the UEA with an odd-numbered device

index. The device index for the UEA must be the
same as the one corresponding to the Classic
EHB that was shut down and powered-off.
Enter the device index through the front panel
display at the physical UEA box. At a high level,
you must do the following from the front panel of
the UEA box:

308
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l On the UEA front panel, rotate the key

clockwise to the C position to enter the
CONFIG menu.
l Configure the FTE Device Index.
This UEA with an odd-numbered device index
assumes the role of primary and gets the odd IP
address. At this point, it is not configured as EHB
yet, and is waiting to receive the platform
configuration.

NOTE: Do not accidently power-on the UEA

with an even-numbered device index.

Creating and Configuring ELCN-EHB platform blocks in Control

Builder

13 In the Control Builder, go to the Project tree, click

Root > New > ELCN, and then click ELCN_NODE –
ELCN Appliance Node.

13 cont RESULT: The configuration form opens with the

Main tab selected.
ELCN-EHB configuration form - Main tab:

13 cont Under the Main tab, enter the following:

l Tag Name – Provide a Tag Name that is
different from the Classic EHB tag name.

309
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

l (optional) Item Name #

l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index (57)

here which you have configured on the UEA
box/Virtual Machine.

l Under the ELCN Node Type drop-down list,

select EHB
l Select the Module is redundant checkbox.

NOTE: Note the difference in term used to

denote the secondary block in the Classic
EHB and the ELCN EHB blocks. In the
Classic EHB Platform block the secondary
block was named with suffix of “_PTNR”
whereas in ELCN EHB suffix of “_SEC” is
used to denote the secondary block.

NOTE: The Device Index and IP Address are

incremented by one (1) for the backup.
These are not changeable by the user.

l Logical Hiway Num – note that this entry must

match the entry made in the Classic EHB
platform block.
l Logical Hiway Num Partner – Hiway number
for the Non-Defining Classic EHB.
l LCN Node Number –This

NOTE: Enter the LCN Node Number of the

ELCN EHB with the odd-numbered device
index (node 57).

310
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

WARNING: When assigning or changing the

LCN node number of any LCN or ELCN node,
it is imperative that the intended node
number is not already in use by another LCN
or ELCN node.
If you cause a duplicate node number
situation to occur, the invalid duplicate node
fails, and the existing running node may
become ISOLATED from some LCN and
ELCN nodes. To recover from this situation,
you must power-off the invalid node, change
its LCN node number to an unused LCN
address, power it back on, and reload the
existing running node which may have
become ISOLATED.

l LCN Node Number – Partner

NOTE: Enter the LCN Node Number of the

ELCN EHB with the even-numbered device
index. At this point in time, this is the LCN
Node Number of the Classic EHB (node
58).

14 After configuring the parameters, click OK to

accept the changes.
RESULT: The Primary and Backup ELCN-EHB
blocks are entered into the ERDB. The Tag Names
and icons appear on the Project side/tab, ready
for loading.

15 A delta sign will appear next to the Non-Defining

Classic EHB on the project side as shown in the
following image. Reload the Non-Defining ELCN
EHB and then load the Defining ELCN EHB.

311
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

16 Go to the Project tree, right-click ELCN-EHB

platform block, and then select Load, or click
on the Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

17 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to

the Backup node. The operation of the Primary
ELCN-EHB is activated.

18 RESULT: On the Native Window System Status

display, the secondary node transitions to the
PWR_ON state.

312
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

19 From the Native Window System Status Display,

select the ELCN-EHB (in the PWR_ON state), click
LOAD SELECT, and press Enter.
NOTE: The UEA based ELCN-EHB is now the
active Backup to the Classic EHB node on the
LCN side.

At this point, the ELCN-EHB statistics is visible on

the ELCNNODE platform block for EHB.

20 Wait for at least 5 minutes, and then from the

Native Window System Status display, perform
the SHUT DOWN of the Classic EHB that is
running as primary to to ELCN-EHB.
RESULT: The Classic EHB transitions to QUALIF
state, and ELCN-EHB will assume the role of
primary. The Emulated Hiway communication is
now routed through the ELCN-EHB.

313
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

21 Shut down the Classic EHB running as Primary

from the Native Window for the second time to
place it into the FAIL state.

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token
for 1 minute and 57 seconds (it takes 1
minute and 57 seconds before the system
will eventually ISOLATE the node.). During
this time, the system is extremely sluggish
(if not placed in the “FAIL” state).
The best practice is to always shut down
the node that is to be powered down, two
(2) times to place it in the "FAIL" state. Then
power it down and perform the required
work so the LCN can communicate
normally.

Experion Bridge Status Display when node 58 is

in the FAIL state:

314
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

22 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This
node is in the FAIL state as shown on the System
Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

23 Shut down the Classic EHB running as primary

from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at

least 70 seconds before you perform a
startup of the Backup ELCN-EHB.

24 In Control Builder, on the EHB Communications

tab, in the Local EHB 1 section, change the
Tagname # to add an extra character, and then
click OK.

NOTE: The “Load values while Active”

option gets enabled only when there is a
change in the platform block.

315
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

25 Go to the Project tree, right-click CEEC300, and

then click Load Values while Active.

NOTE: Load Values while Active option re-

establishes the linkage of the CEE block
with the ELCN platform block internally.
This does not impact C300 emulations.

26 Install the secondary UEA by performing the

following procedure:
1. At the front of the cabinet, slide one UEA
Processor Module into the shelf until fully
seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
2. Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw

316
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

covers.
3. At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
4. Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
5. Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
6. Apply power to the cabinet and UEA.
REFERENCE: For detailed information on UEA
installation, see the Experion LCN Hardware
Upgrade Kit Instructions (51195195-415).

27 Configure the UEA with an even-numbered Device

Index. The device index for the UEA must be the
same as the one corresponding to the Classic
EHB that was shut down and powered-off.
Enter the device index through the front panel
display at the physical UEA box. At a high level,
you must do the following from the front panel of
the UEA box:
l On the UEA front panel, rotate the key
clockwise to the C position to enter the
CONFIG menu.
l Configure the FTE Device Index.

This UEA with an even-numbered Device Index

assumes the role of secondary and gets the even
IP address.
RESULT: The UEA with an even-numbered Device
Index transitions to PWR_ON state.

317
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

28 From the Native Window System Status, select the

Secondary ELCN-EHB that is in PWR_ON state,
click LOAD SELECT, and press Enter.
At this point, both the EHBs are running on the
ELCN side and the coax EHBs that are powered-
off can be decommissioned.
RESULT: The node with even-numbered Device
Index assumes role of the Secondary ELCN-EHB.

Result: The Defining Classic EHB is migrated to ELCN EHB.

Migrating from Classic EHB to Experion LCN EHB

Step Action Done

Deleting Classic EHB redundant block configuration from Control

Builder

1 In Control Builder, under the Project tree, double-

click the Primary Classic EHB block.

318
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

RESULT: The Primary Classic EHB block appears.

2 On the Main tab, under the EHB Migration

Configuration, select Enable OPM to LCN
checkbox.

This checkbox enables the deconfiguration of the

Classic EHB platform block from Control Builder.

NOTE: The Control Builder does not allow

deconfiguration or deletion of a platform
block when the device is running.

319
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Beginning with Experion R501.4, this

enforcement will be relaxed for the case of
EHB migration to ELCN and back. Hence,
this checkbox is added.

3 Go to the Project tree, right-click Primary Classic

EHB, and then selectL , or click on the
Load
Control Builder toolbar.RESULT: The Load
Operation dialog box appears.

4 In Native Window System Status display, make

sure that the node with an even-numbered device
index is running as the primary node.

5 Perform the SHUT DOWN of the odd-numbered

Classic Backup EHB from the Native Window
System Status display. Select the node, select the
SHUT DOWN target, and then press
ENTER.RESULT: This causes an “orderly”
shutdown to the QUALIF state.

320
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

6 Shut down the Backup Classic EHB from the

Native Window for the second Utime to place it
into the FAIL state.

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token
for 1 minute and 57 seconds (it takes 1
minute and 57 seconds before the system
will eventually ISOLATE the node.). During
this time, the system is extremely sluggish
(if not placed in the “FAIL” state).The best
practice is to always shut down the node
that is to be powered down, two (2) times
to place it in the "FAIL" state. Then power it
down and perform the required work so the
LCN can communicate normally.

Experion Bridge Status Display when node 31 is

in the FAIL state:

321
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

7 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This
node is in the FAIL state as shown on the System
Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

8 Shut down the Backup Classic EHB from the

Native Window for the third time to place it into
the OFF state.

9
ATTENTION: Note down the EHB
configuration details and export the block
configuration before removing the platform
block configuration. The exported block
configuration will be used as a reference if
there is a need to migrate back to Classic
EHB from ELCN-EHB.

In Control Builder, go to the Monitoring tree,

right-click the Primary Classic platform block,
and then click ForceDelete.

322
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: The C300-EHB communication

remains uninterrupted and the box
emulations continue to be operational even
after the Classic EHB platform block
configuration is removed. However, the
view to EHB statistics and HDT
communication details will be lost.

10 Go to the Project tree, right-click the Primary

Classic EHB platform block, and then click
Delete.

11 Install the primary UEA by performing the

following procedure:

1. At the front of the cabinet, slide one UEA

323
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

Processor Module into the shelf until fully

seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
2. Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw
covers.
3. At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
4. Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
5. Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
6. Apply power to the cabinet and UEA.
REFERENCE: For detailed information on UEA
installation, see the Experion LCN Hardware
Upgrade Kit Instructions (51195195-415).

12 Configure the UEA with an odd-numbered device

index. The device index for the UEA must be the
same as the one corresponding to the Classic
EHB that was shut down and powered-off. Enter
the device index through the front panel display
at the physical UEA box. At a high level, you must
do the following from the front panel of the UEA
box:
l On the UEA front panel, rotate the key
clockwise to the C position to enter the
CONFIG menu.
l Configure the FTE Device Index.

This UEA with an odd-numbered device index

assumes the role of primary and gets the odd IP
address. At this point, it is not configured as EHB
yet, and is waiting to receive the platform
configuration.

324
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: Do not accidently power-on the UEA

with an even-numbered device index.

Creating and Configuring ELCN-EHB platform blocks in Control Builder

13 In the Control Builder, go to the Project tree, click

Root > New > ELCN, and then click ELCN_NODE
– ELCN Appliance Node.

13 cont RESULT: The configuration form opens with the

Main tab selected. ELCN-EHB configuration
form - Main tab:

13 cont Under the Main tab, enter the following:

l Tag Name – note that this entry must match
the entry made in the Classic EHB platform
block. As ELCN EHB tag name must be the
same as Classic EHB tag name, it will not
follow the standard format of “ELCN_NODE_

325
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

<Nodenumber>”.
l (optional) Item Name #
l (optional) Associated Asset #

l Device Index

NOTE:Enter the same device index (31) here

which you have configured on the UEA
box/Virtual Machine.
l Under the ELCN Node Type drop-down list,
select EHB
l Enter 2 as a value for EHB Node Number.
l Select the Module is redundant checkbox.

NOTE: Note the difference in term used to

denote the secondary block in the Classic
EHB and the ELCN EHB blocks. In the
Classic EHB Platform block the secondary
block was named with suffix of “_PTNR”
whereas in ELCN EHB suffix of “_SEC” is
used to denote the secondary block.

NOTE: The Device Index and IP Address are

incremented by one (1) for the backup.
These are not changeable by the user.

l Logical Hiway Num – note that this entry must

match the entry made in the Classic EHB
platform block.
l LCN Node Number –This

NOTE: Enter the LCN Node Number of the

ELCN EHB with the odd-numbered device
index (node 31).

CAUTION: When assigning or changing the

LCN node number of any LCN or ELCN

326
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

node, it is imperative that the intended

node number is not already in use by
another LCN or ELCN node. If you cause a
duplicate node number situation to occur,
the invalid duplicate node fails, and the
existing running node may become
ISOLATED from some LCN and ELCN
nodes. To recover from this situation, you
must power-off the invalid node, change its
LCN node number to an unused LCN
address, power it back on, and reload the
existing running node which may have
become ISOLATED.

l LCN Node Number – Partner

NOTE: Enter the LCN Node Number of the

ELCN EHB with the even-numbered device
index. At this point in time, this is the LCN
Node Number of the Classic EHB (node
32).

14 After configuring the parameters, click OK to

accept the changes.RESULT: The Primary and
Backup ELCN-EHB blocks are entered into the
ERDB. The Tag Names and icons appear on the
Project side/tab, ready for loading.

15 Go to the Project tree, right-click ELCN-EHB

platform block, and then select Load, or click

on the Control Builder toolbar.RESULT: The Load

Operation dialog box appears.

327
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

16 Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to

the Backup node. The operation of the Primary
ELCN-EHB is activated.

17 RESULT: On the Native Window System Status

display, the secondary node transitions to the
PWR_ON state.

18 From the Native Window System Status Display,

select the ELCN-EHB (in the PWR_ON state),
click LOAD SELECT, and press Enter.

328
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

NOTE: The UEA based ELCN-EHB is now

the active Backup to the Classic EHB node
on the LCN side.

At this point, the ELCN-EHB statistics is visible

on the ELCNNODE platform block for EHB.

19 Wait for at least 5 minutes, and then from the

Native Window System Status display, perform
the SHUT DOWN of the Classic EHB that is
running as primary to switch over to ELCN-
EHB.RESULT: The Classic EHB transitions to
QUALIF state, and ELCN-EHB will assume the
role of primary. The Emulated Hiway
communication is now routed through the ELCN-
EHB.

329
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

20 Shut down the Classic EHB running as Primary

from the Native Window for the second time to
place it into the FAIL state.

ATTENTION: If the node is not shut down

two (2) times and placed into the "FAIL"
state, and then powered OFF, the LCN will
still be looking for that node in the token
for 1 minute and 57 seconds (it takes 1
minute and 57 seconds before the system
will eventually ISOLATE the node.). During
this time, the system is extremely sluggish
(if not placed in the “FAIL” state).The best
practice is to always shut down the node
that is to be powered down, two (2) times
to place it in the "FAIL" state. Then power it
down and perform the required work so the
LCN can communicate normally.

Experion Bridge Status Display when node 32 is

in the FAIL state:

330
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

For UVA-based ELCN EHB, refer the following

Experion Bridge Status Display screenshot

21 Power-off the node by placing the LCN chassis

power supply switch in the OFF position. This
node is in the FAIL state as shown on the System
Status Display or Node Status Display.

ATTENTION: Do not accidentally power-off

the wrong node. If it is a DNCF, use the
arrows to identify the appropriate power
switch.

22 Shut down the Classic EHB running as primary

from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for

at least 70 seconds before you perform a
startup of the Backup ELCN-EHB.

331
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

23 In Control Builder, on the EHB Communications

tab, in the Local EHB 1 section, change the
Tagname # to add an extra character, and then
click OK.

NOTE: The “Load values while Active”

option gets enabled only when there is a
change in the platform block.

24 Go to the Project tree, right-click CEEC300, and

then click Load Values while Active.

NOTE: Load Values while Active option re-

establishes the linkage of the CEE block
with the ELCN platform block internally.
This does not impact C300 emulations.

332
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

25 Install the secondary UEA by performing the

following procedure:

1. At the front of the cabinet, slide one UEA

Processor Module into the shelf until fully
seated. Note that the shelf has a guide slot
(channel) that the bottom UEA module chassis
flange must slide into.
2. Tighten 2 captive screws to secure the UEA
module to the shelf, then close the screw
covers.
3. At the rear of the cabinet, slide the termination
assembly into the rear of the UEA Processor
Module until fully seated. Note that the shelf
has a guide slot (channel) that the bottom
flange of the termination assembly chassis
must slide into.
4. Tighten 4 captive screws to secure the
termination assembly to the UEA shelf.
5. Install the AC power cables into the rear of the
termination assembly and fasten with 2 screws
per cable and external tooth lock washers.
6. Apply power to the cabinet and UEA.
REFERENCE: For detailed information on UEA

333
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

installation, see the Experion LCN Hardware

Upgrade Kit Instructions (51195195-415).

26 Configure the UEA with an even-numbered

Device Index. The device index for the UEA must
be the same as the one corresponding to the
Classic EHB that was shut down and powered-
off. Enter the device index through the front
panel display at the physical UEA box. At a high
level, you must do the following from the front
panel of the UEA box:
l On the UEA front panel, rotate the key
clockwise to the C position to enter the
CONFIG menu.
l Configure the FTE Device Index.

This UEA with an even-numbered Device Index

assumes the role of secondary and gets the even
IP address.RESULT: The UEA with an even-
numbered Device Index transitions to PWR_ON
state.

27 From the Native Window System Status, select

the Secondary ELCN-EHB that is in PWR_ON
state, click LOAD SELECT, and press Enter. At
this point, both the EHBs are running on the
ELCN side and the coax EHBs that are powered-
off can be decommissioned.RESULT: The node
with even-numbered Device Index assumes role
of the Secondary ELCN-EHB.

334
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

28 In the case of a redundant UEA-based or UVA-

based ELCN Appliance node, during an on-
process migration from any pre-R501.6 release to
R501.6 or later version, an additional switch over
is required to complete the migration. Beginning
with R501.6, a soft failure indicator, “Deployment
Incomplete”, appears on the Soft Failures tab of
an ELCN Node Control Builder block which
indicates this switch over has not been
completed. This is not applicable for migration
from R501.6 onwards to any later release.

Migrating back to Classic EHB from ELCN-EHB

This procedure assists you in migrating from ELCN-EHB to
Classic EHB if you encounter a problem during, or after, Classic
EHB to ELCN-EHB migration, and you would like to go back to
the original Classic EHB.

ATTENTION: Make sure the LCN node(s) is(are) installed

and ready to be powered up and loaded before performing
this procedure.

Done
Step Action
(√)

1. In Control Builder, under the Project tree, double-click the Primary

ELCN EHB block.

335
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
RESULT: The Primary ELCN EHB block appears.

2. On the Main tab, select Enable OPM to LCN checkbox.

This checkbox enables the deconfiguration of the ELCN EHB
platform block from Control Builder.

NOTE: The Control Builder does not allow deconfiguration or

deletion of a platform block when the device is running.
Beginning with Experion R501.4, this enforcement will be
relaxed for the case of EHB migration to ELCN and back.
Hence, this checkbox is added.

3. At a station (for example, US or ES-T), perform a SHUT DOWN of

the Backup ELCN-EHB (with even-numbered Device Index) node
from the Native Window System Status display. Select the node
and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.

4. Shut down the node from the Native Window for the second time
to place it into the FAIL state.

5. In Control Builder, select the Backup ELCN-EHB platform block

from the Monitoring tree.

6. Right-click on the block and click Delete.

At the Delete Selected Object(s) confirmation dialog box, click
Continue.
Click Delete Selected Object(s).
RESULT: The ELCN-EHB platform block is deleted from the
Monitoring tree.

NOTE: EHB platform block cannot be deleted from

monitoring side if any C300 controller is associated to this
EHB platform block. To delete this EHB platform block from
monitoring side perform following steps:
1. Shutdown primary and backup EHB from Native window.
2. Put the CEE of the associated C300 where corresponding

336
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)

EHB strategies are loaded, in IDLE state from monitoring

side.
3. Inactivate and delete all the EHB strategies under C300
from monitoring side .
4. Unconfigure the EHB from EHB communication tab under
CEE by providing EHB highway network number as zero
from project side.
5. Reload C300 along with CEE to the monitoring side.
6. Delete primary and backup EHB block from monitoring
side.

7. Loosen the threaded captive screws in counter-clockwise direction

and pull-out the UEA box (but leave the box in the chassis) from
the chassis until the power supply is interrupted.

NOTE: Use the handles to slide the UEA box.

8 Shut down the node from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at least 70 seconds before you
power-on the Classic Backup EHB.

9. Power-on the Classic Backup EHB (with even-numbered Device

Index) by placing the LCN chassis power supply switch in the ON
position.

10 Using the Native Window’s System Status Display, verify that the
node transitions to the PWR_ON state.

11. From the Native Window’s System Status Display, load the Classic
Backup EHB using the checkpoint saved in the NET (or Emulated
Drive).
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status transitions to NET_LD, and then

337
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
BACKUP after the load is complete.

NOTE: Wait for at least 7 minutes after the node transitions

to the BACKUP state.

RESULT: You have now successfully migrated back to Backup Classic EHB from
Backup ELCN-EHB.

Perform the following procedure to migrate back to Classic Primary EHB from
Primary ELCN-EHB (with even-numbered Device Index).
The following sequence of shutting down the Primary ELCN-EHB (thrice, to place it
into the OFF state) must be done quickly so that the Classic Backup EHB (with
even-numbered Device Index) takes over as the primary on the Native Window.

12. At a station (for example, US or ES-T), perform a SHUT DOWN of

the Primary ELCN-EHB (with odd-numbered Device Index) node
from the Native Window System Status display. Select the node
and select the SHUT DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the QUALIF state.
The Classic Backup will transition to the WARN state.

13. Shut down the node from the Native Window for the second time
to place it into the FAIL state.

14. In Control Builder, select the Primary ELCN-EHB platform block

from the Monitoring tree.

15. Right-click on the block and click ForceDelete.

RESULT: The ELCN-EHB platform block is deleted from the
Monitoring tree and the UEA box reboots.

16. While the node reboots, loosen the threaded captive screws in
counter-clockwise direction and pull-out the UEA box (but leave
the box in the chassis) from the chassis until the power supply is
interrupted.

NOTE: Use the handles to slide the UEA box.

338
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
17. Repeat Step 15 to delete the block from the Project tree.

NOTE: You may export and save the configuration for future
reference.

18. Shut down the node from the Native Window for the third time to
transition from the FAIL state to the OFF state.

ATTENTION: At this point in time, wait for at least 70 seconds before you
power-on the Classic EHB with the even-numbered Device Index.

19. Power-on the Classic EHB (with odd-numbered Device Index) by

placing the LCN chassis power supply switch in the ON position.

20. Using the Native Window System Status Display, verify that the
node transitions to the PWR_ON state.

21. From the Native Window System Status Display, load the Classic
EHB with the odd-numbered Device Index using the checkpoint
saved in the NET (or Emulated Drive).
To load the node, select the node and click LOAD SELECT and
press Enter.
RESULT: The node’s status will transition to NET_LD, and then
BACKUP after the load is complete. At this point of time, the
Classic EHB with the even-numbered Device Index will transition
from the WARN state to the OK state.

Creating and Configuring Classic-EHB platform blocks in Control Builder

22. In the Control Builder, go to the Project tree, click Root > New >
Gateway, and then click EHB-Experion Hiway Bridge.
RESULT: The configuration form opens with the Main tab selected.
Classic-EHB configuration form - Main tab: reconfiguration the
Classic-EHB with exact same configuration as ELCN-EHB.

23. After configuring the parameters, click OK to accept the changes.

RESULT: The Primary and Backup Classic-EHB blocks are entered
into the ERDB. The Tag Names and icons appear on the Project
side/tab, ready for loading.

339
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(√)
24. Go to the Project tree, right-click Classic-EHB platform block, and
then select Load, or click on the Control Builder toolbar.
RESULT: The Load Operation dialog box appears.

25. Click the Load button to confirm the operation.

RESULT: The Control Builder loads the block to the Monitoring
tree. The operation of the Primary Classic-EHB is activated.

26. Modify the Tagname of each C300 block.

Go to the Project tree, expand Primary C300 block and double-
click CEE block. Under the EHB Communications tab, modify the
Tagname # by adding additional character for example EHB_33x
and click OK.

27. Right-click the CEE block of each C300 and select the Load Values
while Active option.

RESULT: You have now successfully migrated back to Classic EHB from ELCN-
EHB.

Migration from Classic NG to Experion LCN NG

This section describes the off-process migration from Classic
NG to ELCN-NG.
You must have a minimum of Experion R501.6 and TPN R688.3
installed. This involves upgrading the firmware (for both UEA
RECOVERY and APP images) of ELCN-NG.
UEAs shipped from the factory have UEA RECOVERY firmware
and no APP firmware image. The factory-shipped UEA has the
firmware version UEA_100.1-11.0.

NOTE: The first time you load firmware on a UEA box, load
the Application personality image before the Boot/Recovery
(UEARECOVERY) personality image. The Firmware
Manager Tool will not overwrite the existing
UEARECOVERY personality image until an Application
personality image (UEAELCN_NODE) is present and

340
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

available to the UEA. The UEAELCN_NODE application

image is available for download using the Firmware
Manager.

ATTENTION: Migration from Classic NG to an ELCN-NG

requires powering-off the classic node. Perform this activity
at an appropriate time to avoid disturbance to the process
and potentially hazardous consequences to equipment and
personnel. Determine in advance that the scheduling of
this procedure is in accordance with proper system
operation.A Classic NG and an ELCN NG cannot
communicate with one another. For successful
communication, each ELCN NG on each LCN can
communicate with ELCN NG only. For more information,
refer Experion LCN Planning, Installation, and Service
Guide, Experion LCN NG Planning, Installation, and Service
Guide, and ELCN Upgrade Kit Instructions.

Prerequisites
Before you migrate from Classic NG to ELCN-NG, ensure that
the prerequisites described in section “Prerequisites for ELCN
UEA Appliance Node migration” are complied with.

Classic NG shutdown
Perform the following procedure to perform an orderly
shutdown of the Classic NG to migrate to ELCN NG. This
procedure shuts down a single NG (node 55 in the example
displays) to migrate this single node to ELCN NG.

Step Action Done

1 At a station (for example, US or ES-T), perform a SHUT

DOWN of the NG from the Native Window System
Status display. Select the node and select the SHUT
DOWN target and press Enter.
RESULT: This causes an “orderly” shutdown to the
QUALIF state.

341
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

2 Shut down the Classic NG from the Native Window for

the second time to place it into the FAIL state.

ATTENTION: If the node is not shut down two

(2) times and placed into the "FAIL" state, and
then powered OFF, the LCN will still be looking
for that node in the token for 1 minute and 57
seconds (it takes 1 minute and 57 seconds
before the system will eventually ISOLATE the
node.). During this time, the system is extremely
sluggish (if not placed in the “FAIL” state).
The best practice is to always shut down the
node that is to be powered down, two (2) times
to place it in the "FAIL" state. Then power it
down and perform the required work so the
LCN can communicate normally.
Experion Bridge Status Display when the node
is in the FAIL state:

342
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

3 Power-off the node by placing the LCN chassis power

supply switch in the OFF position. This node is in the
FAIL state as shown on the System Status Display or
Node Status Display.

ATTENTION: Do not accidentally power-off the

wrong node. If it is a DNCF, use the arrows to
identify the appropriate power switch.

4 Shut down the node from the Native Window for the
third time to transition from the FAIL state to the OFF
state.

Experion Bridge Status Display when the node is in

the OFF state:

Installing UEA
REFERENCE: For information on UEA installation specific to
NG nodes, see the Experion LCN Hardware Upgrade Kit
Instructions (51195195-415).

343
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Installing FTE switches

REFERENCE: For information on mounting and configuring
the Ethernet switches for the ELCN, see the FTE Switch used
with LCN cabinet Upgrade Kit instructions (51195195-384).
After FTE switch installation, connect the FTE cables between
the UEA FTE ports and the L2 ports on the FTE switch.

Installing PIN Switch

REFERENCE: For information on mounting and configuring the
PIN switches for the ELCN, see the ELCN NG Planning,
Installation, and Service Guide.
After PIN switch installation, connect the PIN cables between
the NG and ports configured in the same switch.

ATTENTION: If both FTE connections (FTE-A and FTE-B)

and/or both PIN connections (PIN A and PIN B) from the
virtual host is disconnected, the UVA-based NG
communications is disrupted. After this disrupted
connection is resolved, it is recommended to reboot the
affected UVA-based NGs.

Startup of UEA
Each UEA must have a Device Index that is unique in the FTE
community. Enter the Device Index through the front panel
display at the physical UEA box. At a high level, perform the
following procedure from the front panel of the UEA box:
n On the UEA front panel, rotate the key clockwise to the C
position to enter the CONFIG menu.
n Configure the FTE Device Index.

NOTE: Always set an odd-numbered device index for a

RESPONSIBLENG and ALTERNATENG.

n Change the BOOTP setting from NO to YES.

344
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

n Save these changes (this reboots the box and the UEA will
get its FTE IP Address from the Experion BOOTP Server.)
n After the reboot, node transitions into the “Not Loaded”
state.
For detailed procedures, refer to section "To Set the Device
Index Using the UEA Front Panel".
For information about setting up PIN Switches and PIN Cables,
refer Experion LCN NG Planning, Installation, and Service
Guide.

Migrating from Classic NG to Experion LCN NG

Perform the following procedure to migrate from a Classic NG
to ELCN-NG.

Done
Step Action
()
1 Verify that the node is in the Alive state at
the UEA Front Panel Display.

NOTE: The LCN will still show the

NG node in the OFF state.

2 Using the Firmware Manager Tool, flash

the Application personality image
followed by the UEARECOVERY
personality image to the node.
For more information, see section “To
Load Firmware on a New (non-
operational) UEA”.
RESULT: After the node reboots, it goes
to the “NotLoaded” state.

3 In Control Builder, click File > New >

ELCN and then click ELCN_NODE –
ELCN Appliance Node.

345
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()

RESULT: The configuration form opens

with the Main tab selected.
configuration form - Main tab:

4 Under the Main tab, enter the following:

l Tag Name
l (optional) Item Name #
l (optional) Associated Asset #
l Device Index

NOTE: Enter the same device index

here which you have configured on
the UEA box.

l Under the ELCN Node Type drop-

down list, select NG
l In case of NG, the Module is
redundant checkbox is disabled.
l ELCN Multicast Address

346
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()

NOTE: Make sure that you have the

same ELCN Multicast Address as
configured for the ELCN Bridge(s).

l LCN Node Number – This

NOTE: Enter the LCN Node

number of the NG you are
migrating to ELCN.

CAUTION: When assigning or

changing the LCN node number of
any LCN or ELCN node, it is
imperative that the intended node
number is not already in use by
another LCN or ELCN node. If you
cause a duplicate node number
situation to occur, the invalid
duplicate node fails, and the existing
running node may become
ISOLATED from some LCN and
ELCN nodes. To recover from this
situation, you must power-off the
invalid node, change its LCN node
number to an unused LCN address,
power it back on, and reload the
existing running node which may
have become ISOLATED.

5 After configuring the parameters, click

OK to accept the changes.
RESULT: The ELCN-NG block is entered
into the ERDB. The Tag Name and icon
appear on the Project side/tab, ready for
loading.

6 On the Project tree of Control Builder,

select the block to be loaded.

7 Right-click and then select Load, or click

347
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()

on the Control Builder toolbar.

RESULT: The Load Operation dialog box
appears.

8 Click Load to confirm the operation.

RESULT: The Control Builder loads the

block to the node. The operation of the
ELCN-NG is activated.

8 The ELCN-NG node transitions to the

PWR_ON state.

348
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()

Experion Bridge Status Display when the

node is in the PWR_ON state:

9 From the Native Window System Status

Display, select the ELCN NG (in the
PWR_ON state as shown in the following
image), and load the node from the NET.
To load the node (TPN/LCN Personality),
select the node and click LOAD SELECT
and press Enter.

RESULT: The node’s status will transition

to NET_LD, and then to OK after the load
is complete.

For UEA-based NG, Experion Bridge

349
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()
Status Display when the node is in the
OK state:

For UVA-based NG, Experion Bridge

Status Display when the node is in the
OK state

RESULT: You have now successfully migrated your Classic NG to ELCN-NG. You
may want to check the Experion Detail Displays and Control Builder “Main Tab” to
verify that they are reflecting the OK state. You may need to perform a refresh on the
Experion Detail Display to update the node status. Repeat this procedure for
Alternate NG (if any).

ATTENTION: After ensuring that the node is communicating over FTE and
there is no need to go back to Classic NG, you can decommission this node.
For more information, see section “Skin/Formats/CrossReferencePrintFormat
("Decommission/Recommission Nodes" on page 1)”.
For an LCN that has both Responsible NG and Alternate NG, while the
Responsible NG is being upgraded, Alternate NG goes to WARN state as it
does not indicate the other node in the network while it is being upgraded. All
Classic NG must be migrated to ELCN NG as communication between Classic
NG and ELCN NG is not possible.

ATTENTION: The above-mentioned procedure is just an example. If there are

multiple NGs per LCN, repeat the procedure for RESPONSIBLE NG and
ALETRNATE NG (if any).
When the RESPONSIBLE NG and ALTERNATE NG are in the same PIN
network, while a node is being migrated, the other node will be display WARN
state.
For multiple NGs to communicate in the same LCN, ensure that all Classic
NGs are migrated to ELCN NG.

350
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
()

ATTENTION: During the communication between the local LCN and the
remote LCN, if user selects "Only Use Net B" for PIN cable preference in the
local LCN, user must also select the same option for PIN cable preference in
the remote LCN. This ensures that PIN B of Responsible NG or Alternate NG
of local LCN communicates with PIN B of Responsible NG or Alternate NG of
remote LCN. The same configuration must be done if user selects "Only Use
Net A." This configuration is a must for to prevent communcation failure with
the remote LCN.

Migration from EAPP to ELCN-EAPP

ELCN Experion Application Processing Platform is the Experion
system's advanced applications platform on ELCN. The APP
combines the security and integrity needed for advanced
process control and optimization. The APP can run complex
applications developed by Honeywell, by users, and by third-
party suppliers. Integrating process and business data, the APP
uses industry-standard technologies, such as the Microsoft
Windows Server 2016 operating system, and communication
interfaces, such as DCOM, OLE, and OPC.

Pre-migration tasks
1. Record the LCN Node Number, LCN Name, and NG name
from TPS Configuration Utility of the EAPP node.
2. You need ELCN Bridges in place if you have any Classic
coaxial-based nodes. However, if the EAPP which you are
planning to migrate is the last coax node to migrate, you do
not need the ELCN Bridge.
3. Once the EAPP has been fully backed up, then shut down
the EAPP:
a. Perform a SHUT DOWN of the node you want to migrate
from the Native Window System Status display. Select the
node and select the SHUT DOWN target and press Enter.
This causes an “orderly” shutdown to the QUALIF state.

351
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

b. Shut down the node from the Native Window for the
second time to place it into the FAIL state.

ATTENTION: After EAPP is shut down, you can

disconnect the coaxial LCN cable connection (Since
ELCN does not require LCN connection and only
classic EAPP node requires a coaxial LCN cable
connection).
If the node is not shut down two (2) times and
placed into the "FAIL" state, and then powered OFF,
the LCN will continue to look for that node in the
token for 1 minute and 57 seconds (it takes 1
minute and 57 seconds before the system will
eventually ISOLATE the node.). During this time, the
system is extremely sluggish (if not placed in the
“FAIL” state).

c. Power-off the node by removing power from the EAPP.

This node is now in the FAIL state as shown on the
System Status Display or Node Status Display.
d. Shut down the node from the Native Window for the third
time to transition from the FAIL state to the OFF state.
e. Shut down LCN.
f. Shut down Windows.

To install the ELCN- EAPP Node

Use the Experion installer to install ELCN- EAPP software on
the selected computers. Installation can be done using the
Experion DVD, ESIS, or removable media.
See the Experion Software Installation User’s Guide for detailed
steps to launch the installation wizard and perform the
installation.
This procedure provides steps to install the ELCN- EAPP node
using ESIS.

352
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(Ö)
1 Launch ESIS and run the Setup.exe.

2 Choose the appropriate installation option.

3 Provide the ESIS User Name and Password. This is to

connect to the machine configured to run as ESIS.
Click Next.

4 Choose the appropriate installation option and click

Next.

5 Provide Operating System and User Account

information.

6 Provide Windows Administrator Account and

Password and click Next.

353
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(Ö)

7 Select Network Type as FTE, select No. of Adapters

and click NIC Properties.

8 Provide the FTE configuration – TCP/IP details and

click OK.

9 Provide Multicast IP Address details under FTE

Configuration: Multicast Address, Device Index, UDP
Source Port and click Next.

10 Select App Node (EAPP) and click Next.

354
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(Ö)

11 Enter Customer Information and click Next.

12 Select the location to install the software and click

Next.

355
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(Ö)
13 Choose Network Type for your EPKS connection and
click Next.

14 Choose Typical as the EPKS Install Option and click

Next.

15 Enter Experion accounts passwords and click Next.

356
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Done
Step Action
(Ö)

16 The summary of your selections is displayed. If you

are satisfied with the selections you have made, click
Continue to complete installing the ELCN- EAPP
node. If not, click Back, modify your options and
continue.

RESULT: The EAPP Node is installed on the computer.

You must now add the Windows-based EAPP node to the same Windows Domain to
which you had added the ELCN Experion TPS nodes in section “To Commission
ELCN Bridge Using Commissioning Server” (Step 7a). See section “Adding a node to
a Windows domain” in the Windows Domain Implementation Guide for Windows
Server 2016.

To configure the ELCN- EAPP Nodes

Use instructions in this section to complete the configuration
of the ELCN- EAPP node. After the configuration is complete,
restart the computer.

357
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Step Action Done

1 Use the EAPP Node Configuration Utility to configure

the ELCN- EAPP node.
Launch the TPS Node Configuration Utility. Click Start
> Honeywell Experion Tools > All Honeywell Tools >
System Management and click TPS Configuration
Utility.

2 Open the Board 0 page (Configuration Utility > Board

0) and on the LCNP tab, provide the following details
details captured in the Pre-migration steps:
l LCN Address: Unique address within the network
and must not be a duplicate.
l LCN Name
l ELCN Multicast IP (must match on the ELCN
Bridge and all Experion LCN Nodes in order for
them to communicate)
l NG name
l Select the Enable LCNP Auto Restart check box.
This setting determines if the ELCN- EAPP node
will boot automatically in case of a machine restart
or a TDC Emulators service restart.
l Personality is displayed as EAPP and is non-
editable.

358
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Post installation tasks for Data EAPP

Step Action Done

1 Click Start > Honeywell Experion > LCNP Status to

launch the LCNP Status window. The EAPP node will
now be in PWR_ON state.

Migrate UEA ELCNNODE to UVA On Process

and Vice Versa
NOTE: This procedure only works for ELCN ENIMs and
ELCN EHBs. It does not work for ELCN NGs, ELCN AMs, or
ELCN EPLCGs.

ATTENTION: Read this document in full before starting

this detailed procedure to accomplish this migration
between the platform types.

Summary
Migration of ELCN UEA to ELCN UVA is not supported due to
the redundancy configuration of both the UEA and
Virtualization Redundancy Network infrastructure. This restricts
the ability of the primary ELCNNODE to communicate with and
synchronize with the secondary. Customers desire a method of
migrating from UEA to UVA (and vice versa).

359
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

Problem Description
Officially, it is documented that you need to pick which
platform of ELCN node you desire (UEA or UVA) and that you
will not be able to migrate on-process between the two
platforms. Customers have expressed a strong desire to do so,
especially from physical UEA to virtual UEA, as virtualization
becomes more common and more stable.
This procedure gives a procedure (using a custom HMIWeb
schematic) that allows you to migrate, on-process, from
redundant UEA to redundant UVA (and vice versa).

Prerequisites:
1. Have two separate Control Builder (CB) sessions open on
different computers.
2. Have a view of the PC’s FTE status on both computers.
3. Have a view of the native window display on at least one
computer.
4. On one Control Builder, have the Secondary ELCNNODE’s
Monitoring View selected with the Redundancy Tab.
5. On the other Control Builder, have the primary’s ELCNNODE
block selected in Project View (selected-not opened).
6. Have full admin rights to the vSphere client infrastructure
for virtualization administration.
7. Apply the Tools and Controller Update for your supported
release that is detailed in PN2022-13A.

Procedure:

NOTE: This procedure details using an ENIM.

1. Place the UEA ENIM such that the BACKUP ENIM has the
EVEN Device Index. Use the front panel, or $FTESTS1
schematic to determine this,
2. If not the case, and the PRIMARY ENIM has the EVEN
Device Index, then perform a SHUT DOWN command from
Native Window (NW) to failover such that the PRIMARY
ENIM now has the ODD Device Index.

360
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

l This causes the former PRIMARY UEA to reboot.

l Skip to Step 4.

3. Perform a SHUT DOWN command from NativeWindow on

the BACKUP ENIM node to the QUALIF state. To set the
BACKUP ENIM node to FAIL, perform a second SHUT
DOWN.
l This causes the BACKUP ENIM to reboot.
4. Power off the secondary UEA.
5. Perform another SHUT DOWN command from
NativeWindow to take the BACKUP ENIM to the OFF state.
6. Deploy and Power on the UVA following ELCN virtualization
guidelines using the vSphere client.

NOTE: This VM must be given the EVEN Device Index

(the same Device Index as the UEA that was powered
off).

7. In Control Builder, monitor the status on the Redundancy

Tab of the Secondary ELCNNODE Block and verify that the
Redundancy Compatibility shows “NOPARTNER” and the
Inhibit Sync Reason shows “PartnerAbsent”.

8. From Experion Station, open the display named

“ELCNSecConfig.htm”.
l This display is located C:\ C:\Program Files

(x86)\Honeywell\Experion PKS\Client\System\R5xx
where xx is your major release e.g. C:\Program Files

361
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

(x86)\Honeywell\Experion PKS\Client\System\R520

9. Enter the Primary Control Builder Block Name in the box

‘Enter Primary Node Name’ and press enter.
l If the name is correct, it gets displayed below the text

entry, and the fields in grey below get populated.

l If the node type is an ENIM, the following details are also

shown:

l If the node type is an EHB, the following details are also

shown:

10. Enter the Secondary Control Builder BlockName in the box

‘Enter Secondary Node Name’ and press enter.
l If the name is correct, it gets displayed below the text

entry, and the fields below are populated.

l The node specific details are shown.

11. Once the ELCNNODE has been powered up, wait at least 60
seconds to allow it to enter a mode that allows for manual
configuration.

362
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

12. Press the ‘>>> Copy From Primary >>>’button.

l If you press this button and the display shows an error,

the ELCNNODE may not have been powered on for long

enough. You can check the Statistics tab, ‘Time Since
Powerup’. This must be at least 2 minutes and 30
seconds.
l If the ELCNNODE is in the correct state for recovery, after

pressing this button, the parameters ELCNNODENUM,

ELCNNODENUMPARTNER, and ELCNMULTIIPADDR
show a value that is not zero.
13. Check that the node-specific parameters are correct.
l For ENIM: Check that the UCNNODENUM is correct. This

is the UCN address of this secondary.

l For EHB: Check the EHBHWYNUM is correct. This is the

address of this secondary on the Hiway.

14. Click the button ‘Write Config Parameters’ and make sure to
click “Yes” on the “Write config to <Secondary Block Name>”
confirmation dialog box.
15. CHECK The secondary NODESTATESTR and the Native
Window shows PWR_ON for this node after a few seconds.
16. From the Native Window select the secondary LCN node in
the PWR_ON state and perform a LOAD SELECT.
17. Once the node shows the BACKUP state, wait at least 2
minutes. After 2 minutes, the PRIMARY node can now be
shut down. From the Native Window, select the Primary LCN
node and perform a SHUT DOWN command.
l The secondary becomes primary and the old original
primary reboots.
18. Unplug the power from the original primary UEA (odd device
index).
19. From Experion Station, call up the HMIWeb detail display for
the BACKUP node (e.g., ELCN_ENIM_43SEC).
20. Go to the Redundancy tab on the HMIWEB Detail schematic
(not the platform block), select “Become Primary,” and press
enter.
a. Wait for at least 1 minute after shutting down the original
primary node before the command works; otherwise, an
error saying “Primary IP is still occupied” appears.

363
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

21. From the Project side on ControlBuilder, re-load the

PRIMARY ELCN Node’s platform block to Monitoring.
22. Deploy and power on the UVA following ELCN virtualization
guidelines from the Vsphere client.

NOTE: This VM must be given the ODD Device Index

(the same Device Index as the UEA that was powered
off).

23. After the ODD Device Index UVA gets an IP address, the
Native Window shows the PWR_ON state.
24. From Native Window, select the node in PWR_ON and
perform a LOAD SELECT.
25. After the node is loaded and shows BACKUP, then from
ControlBuilder, perform a re-load of the backup Platform
Block.

NOTE: You may observe a soft failure on the primary

ELCN NODE’s platform block, which shows
“Deployment Incomplete." If this is the case, perform
one final failover of the ELCN node (from NW) and
reload the backup from NativeWindow when you see
the state change to PWR_ON.

26. The procedure to migrate UEA to UVA is complete.

Migrate UVA ELCNNODE to UEA On Process

Procedure:

NOTE: This procedure details using an ENIM.

1. Place the UVA ENIM such that the BACKUP ENIM has the
EVEN Device Index. Use $FTESTS1 schematic to determine
this,
2. If not the case, and the PRIMARY ENIM has the EVEN
Device Index, then perform a SHUT DOWN command from
Native Window (NW) to failover such that the PRIMARY
ENIM now has the ODD Device Index.

364
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

lThis causes the former PRIMARY UVA to reboot.

l Skip to Step 4.

3. Perform a SHUT DOWN command from NativeWindow on

the BACKUP ENIM node to the QUALIF state. To set the
BACKUP ENIM node to FAIL, perform a second SHUT
DOWN.
l This causes the BACKUP ENIM to reboot.
4. Power off the secondary UVA (EVEN Device Index) from the
vSphere client.
5. Perform another SHUT DOWN command from
NativeWindow to take the BACKUP ENIM to the OFF state.
6. Power on the UEA ELCN Node with the EVEN Device Index.
7. In Control Builder, after the EVEN Device Index shows up in
FTE Status, monitor the status on the Redundancy Tab of
the Secondary ELCNNODE Block and verify that the
Redundancy Compatibility shows “NOPARTNER” and the
Inhibit Sync Reason shows “PartnerAbsent”.

8. From Experion Station, open the display named

“ELCNSecConfig.htm”.
l This display is located C:\ C:\Program Files
(x86)\Honeywell\Experion PKS\Client\System\R5xx
where xx is your major release e.g. C:\Program Files
(x86)\Honeywell\Experion PKS\Client\System\R520

9. Enter the Primary Control Builder Block Name in the box

‘Enter Primary Node Name’ and press enter.

365
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

l If the name is correct, it gets displayed below the text

entry, and the fields in grey below get populated.

l If the node type is an ENIM, the following details are also

shown:

l If the node type is an EHB, the following details are also

shown:

10. Enter the Secondary Control Builder BlockName in the box

‘Enter Secondary Node Name’ and press enter.
lIf the name is correct, it gets displayed below the text
entry, and the fields below are populated.
l The node specific details are shown.

11. Once the ELCNNODE has been powered up, wait at least 60
seconds before it enters a mode that allows for manual
configuration.
12. Press the ‘>>> Copy From Primary >>>’button.
l If you press this button and the display shows an error,
the ELCNNODE may not have been powered on for long
enough. You can check the Statistics tab, ‘Time Since
Powerup’. This must be at least 2 minutes and 30
seconds.
l If the ELCNNODE is in the correct state for recovery, after
pressing this button, the parameters ELCNNODENUM,
ELCNNODENUMPARTNER, and ELCNMULTIIPADDR
show a value that is not zero.

366
 Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

13. Check that the node-specific parameters are correct.

l For ENIM: Check that the UCNNODENUM is correct. This
is the UCN address of this secondary.
l For EHB: Check the EHBHWYNUM is correct. This is the

address of this secondary on the Hiway.

14. Click the button ‘Write Config Parameters’ and make sure to
click “Yes” on the “Write config to <Secondary Block Name>”
confirmation dialog box.
15. Check that the secondary NODESTATESTR shows PWR_ON
after a few seconds.
16. From the Native Window or ELCN System Management
display, select the secondary LCN node and perform a LOAD
SELECT.
17. Once the node shows the BACKUP state, wait at least 2
minutes. After 2 minutes, the primary can now be shut
down. From the Native Window or ELCN System
Management display, select the primary LCN node and
perform a SHUTDOWN command.
The secondary becomes the primary, and the old primary
l

reboots.
18. Power off the original Primary UVA (ODD Device Index) from
the vSphere client.
19. From Experion Station, call up the HMIWeb detail display for
the BACKUP node (e.g. ELCN_ENIM_43SEC).
20. Go to the Redundancy tab on the HMIWEB Detail schematic
(not the platform block), select “Become Primary,” and press
enter.
l Wait for at least 1 minute after shutting down the original
primary node before the command works; otherwise, an
error saying “Primary IP is still occupied” appears.
21. From the Project side on ControlBuilder, re-load the
PRIMARY ELCN Node’s platform block to Monitoring.
22. Power on the UEA ELCN Node with the ODD Device Index.
23. After the ODD Device Index UEA gets an IP address, the
Native Window shows the PWR_ON state.
24. From Native Window, select the node in PWR_ON and
perform a LOAD SELECT.

367
Chapter 7 - Migrating HM, AM, NIM, ENIM, EPLCG, and EHB to ELCN nodes

25. After the node is loaded and shows BACKUP, then from
ControlBuilder, perform a re-load of the backup Platform
Block.

NOTE: You may observe a soft failure on the primary

ELCN NODE’s platform block, which shows
“Deployment Incomplete." If this is the case, perform
one final failover of the ELCN node (from NW) and
reload the backup from NativeWindow when you see
the state change to PWR_ON.

26. The procedure to migrate UVA to UEA is complete.

368
CHAPTER

8 VERIFYING OPERATION OF EXPERION LCN

In this section:

To Check ELCN Bridge Operation from Native Window 370

To Check ELCN Operation from Experion Detail Displays 370
Description of Shutdown Command 378
Description of Reset Command 379
Interpreting ELCN Icons in Control Builder 380
Viewing ELCN/LCN Node Numbers 384
Duplicate LCN Node Numbers 391
Redundancy Operation 392
ELCN UEA States and Transitions 395

369
Chapter 8 - Verifying Operation of Experion LCN

To Check ELCN Bridge Operation from Native

Window
To check the operation of the ELCN Bridge, go to an ELCN ES-
T and invoke the Native Window System Status Display.
Select an LCN coax-connected node and display its STATUS
DETAIL.
Successful display of a LCN coax-connected node’s status
detail information demonstrates successful access of data from
the LCN to the ELCN through the ELCN Bridge.

To Check ELCN Operation from Experion Detail

Displays
The ELCN Bridges and each ELCN Appliance Node has an
Experion Detail Display. Verify that the Detail Display has no
failure and alarm indications.
Perform the following steps to view the 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 ELCN Appliance Nodes (such as AM and ENIM), click
Controllers.
To view the configured ELCN Bridges and any coax-connected LCN nodes
that are not yet migrated to ELCN, click LCN.

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

In the following example, the primary ELCN Bridge (ELCN_BRG_97) is
selected.

370
 Chapter 8 - Verifying Operation of Experion LCN

Step Action

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

5 Verify that the Local LCN Status LEDs are green (for ELCN Bridge), the
Local FTE Status LEDs are green, and that there are no alarms present.
REFERENCE: For details on the LED and alarm indications, refer to the
section “"To Check ELCN Bridge or ELCN Node Operation Using the Detail
Display Faceplate" on page 376”

6 On the ELCN Bridge Detail Display, select the ELCN Bridge Status tab and
check that the ELCN and LCN nodes are listed correctly.
REFERENCE: For details on interpreting the ELCN Bridge Status tab, refer
to section “"ELCN Bridge view of LCN/ELCN – Bridge Status tab of Detail
Display" on page 384”

To locate the installed UEA box you have selected on the LCN
Bridge Detail Display, you may select the Locate button to
make the UEA box front panel display STS LED blink (for 5
minutes, or until interacted with).

371
Chapter 8 - Verifying Operation of Experion LCN

ELCN Bridge Detail Display Example –- Secondary

ENIM Detail Display Example – Primary

ENIM Detail Display Example – Secondary

372
 Chapter 8 - Verifying Operation of Experion LCN

AM Detail Display Example - Primary

EHB Detail Display Example – Primary

EHB Detail Display Example – Secondary

ELCN NG Detail Display Example – Responsible NG

373
Chapter 8 - Verifying Operation of Experion LCN

ELCN NG Detail Display Example – Alternate NG

NOTE: In ELCN NG Detail Display, the following parameters

appearing in the Statistics tab are not applicable for ELCN
NG and will always display the value “0”.

Table Section Outside Table:

RPARSEC Indicates this node’s
Table Cell Outside Table: parameter-per-second read
NG Statistics Parameter Name access rate on other nodes.

Table Cell Outside Table:

NGPAREQS Total count of parameter access
NG Statistics Parameter Descriptionrequests since last reset to 0.

374
 Chapter 8 - Verifying Operation of Experion LCN

RECVFLMG Number of receive file

messages.

RECVFLWD Word count for receive

messages.

RECVERRS Number of PIN errors reported.

RECVTMOT Time out for receive messages.

XMITFLMG Number of transmit file

messages.

XMITFLWD Word count for transmit

messages.

XMITERRS Number of PIN errors reported.

XMITTMOT Time out for transmit

messages.

NGPAREAD Total number of parameter

reads from a particular network.

NGPASTOR Total number of parameter

stores from a particular
network.

NGPAGSDE Total number of get self-

defining enum requests from
network.

375
Chapter 8 - Verifying Operation of Experion LCN

To Check ELCN Bridge or ELCN Node Operation

Using the Detail Display Faceplate
The following table describes the Faceplate appearing on the
Detail Display of the ELCN Bridge and ELCN Nodes.

Item step Description

1 Tag Name of primary block

Tag Name of secondary block (click to go to secondary
Detail Display)
Device/Node TypeLCN Node Number
FTE Device IndexFTE IP Address

2 Status of ELCN Bridge or ELCN Node – See

NODESTATESTR parameter in the Control Builder
Parameter Reference and the Control Building User’s
Guide.

3 Local FTE Status and Local LCN Status LEDs (LCN

LEDs appear only on ELCN Bridge)

Off - Not in error.

FTE: The FTE Link

integrity is OK, with
transmit activity on
link.LCN: The LCN cable
status is OK. Letter A/B
appears white for Active
cable and gray for Backup
cable. In this example,
LCN B cable is Active.

Error Condition

Uncertain Condition

Warning Condition

NOTE: The FTE and LCN Local Status LEDs do

376
 Chapter 8 - Verifying Operation of Experion LCN

Item step Description

not indicate cable faults emanating from the

rest of the network - they only show local cable
faults emanating from the ELCN Bridge’s or
ELCN Node’s own hardware.

4 Indicates current CPU free %, RAM free %, and

hardware temperature. You can configure alarm limits
in the Main tab of Control Builder block.

5 Sync. State: SYNCMAINT (synchronization

maintenance) is the normal state. See
RDNSYNCSTSATE in Control Builder Parameter
Reference.

6 Redundancy: PRIMARY or SECONDARY (blank if non-

redundant)See RDNROLESTATE in Control Builder
Parameter Reference.

7
Alarm The word “Alarm” appears if an
active alarm is in Alarm
Summary. To view the alarm,
click the alarm icon on the
Experion Station status bar.

Click to acknowledge/silence
alarm(s).

Alarm status icon. Changes

appearance to indicate urgent,
unacknowledged, cleared, and so
forth.

TIP: Hover cursor over icon

to view tooltip. For
descriptions of alarm
icons, see “Calling up the
Alarm Summary” in
Experion Operator’s Guide.

377
Chapter 8 - Verifying Operation of Experion LCN

Item step Description

8 FTE LEDs: A red LED indicates failure. See

“Troubleshooting Network Issues” in Fault Tolerant
Ethernet Overview and Implementation Guide.

Description of Shutdown Command

The Shutdown command causes the related UEA box to Reboot
into the “Ready” state. This “Ready” state makes the UEA box
capable of a firmware load. In the “Ready” state, only the
Firmware Manager tool can “talk” to the UEA; Experion Control
Builder or Detail Displays cannot.

ATTENTION: For the ELCN Appliance Node, first Shut Down

the TPN-side of the node in the Native Window to place the
node in the QUALIF state, then shut down the UEA.

If you do not perform a firmware load following a Shutdown

command, then you will have to Reboot the UEA from the front
panel display at the physical box. The Reboot does the
following:
n For the ELCN Bridge, the reboot returns the UEA to a fully
operational state – typically this would be BACKUP, as the
primary would be running.
n For the ELCN Appliance Node, the reboot returns the UEA
box to the PWR_ON state on the LCN. You will need to LOAD
the LCN Personality and Checkpoint file to make the ELCN
Node operational again.
You can perform the Shutdown command from the Monitoring
side of the platform block in Control Builder (Choosing
“Shutdown” from the “Module Command” dropdown on the
Main tab).
The Shutdown command requires that you select YES in
response to a confirmation message to proceed with the
Shutdown.
REFERENCE: For other details, refer to the ELCNBCOMMAND
parameter (for the ELCN Bridge) and the

378
 Chapter 8 - Verifying Operation of Experion LCN

ELCNNODECOMMAND (for ELCN Nodes) in the Control

Builder Parameter Reference.

Description of Reset Command

NOTE: Only ELCN Appliance Nodes have states of “RESET”
and “SHUTDOWN”. ELCN Bridge only has “SHUTDOWN”
state.

Command/State of ELCN Appliance Node

Command/State of ELCN Bridge
The Reset command causes the related ELCN Appliance Nodes
to reset to the “PWR_ON” state, it is equivalent to the Reset
button on the power supply of classic LCN Chassis. This
command is only functional on the following:
n secondary nodes
n non-running states of Non-redundant nodes
n non-running states of primary nodes when the secondary is
not running (not loaded)
where following are the non-running states:
PWR_ON, FAIL, QUALIF, NET_LOAD, ISOL, READY, OFF.
If the Reset command operation is performed for the node
which is in running state, it will fail and show “Invalid State”
error.

379
Chapter 8 - Verifying Operation of Experion LCN

This operation cannot be performed from the Station Display of

the Appliance Node.
You can perform the Reset command from the Monitoring side
of the platform block in Control Builder (Choosing “Reset” from
the “Module Command” dropdown on the Main tab).
The Reset command requires that you select YES in response
to a confirmation message to proceed with the Shutdown.
This operation helps users to transition an ELCN Appliance
node to PWR_ON state instead of performing the same
operation on the hardware.

Interpreting ELCN Icons in Control Builder

Adding an ELCN platform block (non-redundant or redundant)
to the Control Builder Project tab, results in the appearance of
an icon that represents a single or redundant pair of ELCN
Bridges or ELCN Nodes.
After the platform blocks in Control Builder have been loaded,
the icons appear in the Control Builder Monitoring side/tab.
The appearance of the icons in the Monitoring tab is
determined by the ICONSTATE parameter, which is derived
from the following parameters:
n Execution State parameter (ELCNBSTATE for the ELCN
Bridge. ELCNNODESTATE and NODESTATESTR for ELCN
Nodes)
n Redundancy Role parameter (RDNROLESTATE)
n Redundancy Synchronization State parameter
(RDNSYNCSTATE)
n Soft Failure parameter (SOFTFAIL)

380
 Chapter 8 - Verifying Operation of Experion LCN

When a single ELCN Bridge or ELCN Node platform block is

defined, the icon appears as a single “controller” icon. When a
redundant ELCN Bridge or ELCN Node platform block is
defined, two icons appear as follows:
n primary - lower-left icon
n secondary - upper-right icon
The appearance of either icon on top in a redundant pair
indicates the active “controller”.

ELCN Bridge and ELCN Node icon indications in

Control Builder
The following table shows the icon appearance in Control
Builder based on the current ELCN Bridge or ELCN Node state.

Icon Represents State

Project Tab

ELCN Bridge/ELCN Node N/A

configured for non-redundant
operation.
(gray)

ELCN Bridge/ELCN Node Primary N/A

configured for redundant
operation.
(gray & white)

ELCN Bridge/ELCN Node N/A

Secondary configured for
redundant operation.
(white & gray)

Monitoring Tab

ELCN Bridge/ELCN Node non- No Communication

redundant and not communicating

(red)

Primary ELCN Bridge/ELCN Node No Communication

is not communicating.

381
Chapter 8 - Verifying Operation of Experion LCN

Icon Represents State

(red & white)

Secondary ELCN Bridge/ELCN No Communication

Node is not communicating.

(white & red)

ELCN Bridge/ELCN Node is non- No Database

redundant.
Communication established, but
(yellow)
ELCN Bridge/ELCN Node is not
loaded.

Communication to Primary and No Database

Secondary ELCN Bridge/ELCN
Node has been established but
(yellow & yellow) they are not loaded.

Primary ELCN Bridge/ELCN Node No Database

is not synchronized and partner is
absent or incompatible
(yellow & shadow)

ELCN Bridge/ELCN Node is non- Run or OK

redundant

(green)

Primary ELCN Bridge/ELCN Node OK

is synchronized

(green & white)

Primary ELCN Bridge/ELCN Node OK

is not synchronized and partner is
visible
(green & yellow)

Primary ELCN Bridge/ELCN Node OK

is not synchronized and partner is
absent or incompatible
(green & shadow)

382
 Chapter 8 - Verifying Operation of Experion LCN

Icon Represents State

Secondary ELCN Bridge/ELCN Backup

Node is synchronized

(white & green)

Secondary ELCN Bridge/ELCN No Database

Node is not synchronized and
partner is visible
(yellow & yellow)

Secondary ELCN Bridge/ELCN Backup

Node is not synchronized and
partner is absent or incompatible.
(shadow & yellow)

ELCN Bridge/ELCN Node non- OK Soft Fail

redundant and soft fail(s) are
present.
(green)

Primary ELCN Bridge/ELCN Node OK Soft Fail

is synchronized and soft fail(s) are
present on the primary.
(green & white)

Primary ELCN Bridge/ELCN Node OK Soft Fail

is not synchronized and partner is
visible and soft fail(s) are present
(green & yellow) on primary.

Primary ELCN Bridge/ELCN Node OK Soft Fail

is not synchronized and partner is
absent or incompatible and soft fail
(green & shadow) (s) are present on primary.

Secondary ELCN Bridge/ELCN Backup Soft Fail

Node is synchronized and soft fails
(s) are present on secondary.
(white & green)

Secondary ELCN Bridge/ELCN Backup Soft Fail

Node is not synchronized and
partner is visible and soft fails(s)

383
Chapter 8 - Verifying Operation of Experion LCN

Icon Represents State

(yellow & yellow) are present on secondary.

Secondary ELCN Bridge/ELCN Backup Soft Fail

Node is not synchronized and
partner is absent or incompatible
(shadow & yellow) and soft fails(s) are present on
secondary.

Viewing ELCN/LCN Node Numbers

ELCN Bridge view of LCN/ELCN – Bridge Status tab
of Detail Display
The BRIDGE STATUS tab of the ELCN Bridge Experion Detail
Display shows the ELCN Bridge’s view of the LCN/ELCN. From
this display, you can see the assigned node numbers for the
operating LCN coax-connected nodes, Experion LCN nodes,
and ELCN Bridges. Information presented in the fields in the
LCN, ELCN and TYPE columns of the LCN/ELCN Network
Topology View display indicates the status conditions of the
nodes.

Node Description in the TYPE Column

Some Node Type examples from the illustrated display
are:Node 01 – ELCN V/W EST is an ELCN Virtual Windows-
based ES-TNode 48 – ELCN V/W HMON is an ELCN Virtual
Windows-based History ModuleNode 54 – ELCN P/A AM is an
ELCN Physical Appliance (UEA-based) Application Module

384
 Chapter 8 - Verifying Operation of Experion LCN

For the complete list of node types refer to section “"Node

Types shown on the Bridge Status tab" on the next page”.

Node Status Indications

Information presented in the LCN, ELCN and TYPE column
fields indicate status conditions of nodes. The TYPE is defined
by $NODETYP parameter. The following table describes the
possible meanings of the node status indications.

LCN/ELCN Network Topology View Indications Possible Node Status

LCN ELCN TYPE

Green checked Blank Node type value Node is on the LCN

and is functional
(that is, node is in the
OK or BACKUP state).

Green checked Blank Blank Node is on the LCN

and is not functional
(that is, node is in one
of these states:
QUALIF, PWR_ON,
ISOLATED, FAIL,
NET_LOAD, LOC_
LOAD, READY).

Blank Green checked Node type value Node is on the ELCN

and is functional
(that is, node is in the
OK or BACKUP state).

Blank Green checked Blank Node is on the ELCN

and is not functional
(that is, node is in one
of these states:
QUALIF, PWR_ON,
ISOLATED, FAIL,
NET_LOAD, LOC_
LOAD, READY).

Blank Blank Blank Node number is

unused or node is in
the OFF state.

385
Chapter 8 - Verifying Operation of Experion LCN

Node Types shown on the Bridge Status tab

The following table lists the Node Types shown on the Bridge
Status tab and in LVRLOG.
Note that the LVRLOG (LCN Node Version/Revision Logging
function) now provides this “node type” information also.
REFERENCE: For LVRLOG details, see the Engineer’s
Reference Manual in the TPN/LCN PDF collection.
Alternatively, you can enter $PRSTS##.$NODETYP on the
PERFMENU’s DATACHNG display (where ## is the LCN node
number) to return that node’s type, whether LCN-coax
connected or Experion LCN.

Text shown in
$NODETYP Value Meaning
LVRLOG/AUDIT reports
ELCN-P/A-AM ELCN Physical (UEA) ELCN-P/A
Appliance AM

ELCN-V/A-AM ELCN Virtual Appliance ELCN-V/A

AM

ELCN-P/A-ENIM ELCN Physical (UEA) ELCN-P/A

Appliance ENIM

ELCN-V/A-ENIM ELCN Virtual Appliance ELCN-V/A

ENIM

ELCN-P/A-PLCG ELCN Physical (UEA) ELCN-P/A

Appliance EPLCG

386
 Chapter 8 - Verifying Operation of Experion LCN

Text shown in
$NODETYP Value Meaning
LVRLOG/AUDIT reports
ELCN-V/A-PLCG ELCN Virtual Appliance ELCN-V/A
EPLCG

ELCN-P/A-EHB ELCN Physical (UEA) ELCN-P/A

Appliance EHB

ELCN-V/A-EHB ELCN Virtual Appliance ELCN-V/A

EHB

ELCN-P/W-APP ELCN Physical Windows- ELCN-P/W

based ACE-T

ELCN-P/W-APP ELCN Physical Windows- ELCN-P/W

based EAPP

ELCN-P/W-EST ELCN Physical Windows- ELCN-P/W

based ES-T

ELCN-P/W-ESVT ELCN Physical Windows- ELCN-P/W

based ESVT

ELCN-P/W-HMOF ELCN Physical Windows- ELCN-P/W

based HM (OFF
PROCESS)

ELCN-P/W-HMON ELCN Physical Windows- ELCN-P/W

based HM

ELCN-P/W-OPR ELCN Physical Windows- ELCN-P/W

based Operator
Personality Universal
Station Module

ELCN-P/W-UNVL ELCN Physical Windows- ELCN-P/W

based Universal
Personality Universal
Station Module

ELCN-V/W-APP ELCN Virtual Windows- ELCN-V/W

based ACE-T

ELCN-V/W-APP ELCN Virtual Windows- ELCN-V/W

based EAPP

ELCN-V/W-EST ELCN Virtual Windows- ELCN-V/W

387
Chapter 8 - Verifying Operation of Experion LCN

Text shown in
$NODETYP Value Meaning
LVRLOG/AUDIT reports
based ES-T

ELCN-V/W-ESVT ELCN Virtual Windows- ELCN-V/W

based ESVT

ELCN-V/W-HMOF ELCN Virtual Windows- ELCN-V/W

based HM (OFF
PROCESS)

ELCN-V/W-HMON ELCN Virtual Windows- ELCN-V/W

based HM

ELCN-V/W-OPR ELCN Virtual Windows- ELCN-V/W

based Operator
Personality Universal
Station Module

ELCN-V/W-UNVL ELCN Virtual Windows- ELCN-V/W

based Universal
Personality Universal
Station Module

ETN-AM ETN based Application ETN-AM

Module

ETN-APP ETN based Application ETN-APP

Processing Platform
(EAPP)

ETN-APP ETN based Application ETN-APP

Processing Platform
(ACET)

ETN-EST ETN based Experion ETN-EST

Station

ETN-ESVT ETN based Experion ETN-ESVT

Server

ETN-OPR ETN based Operator ETN-OPR

Personality Universal
Station Module

ETN-OPR ETN based Operator ETN-OPR

Personality Universal
Station Module (PCUS)

388
 Chapter 8 - Verifying Operation of Experion LCN

Text shown in
$NODETYP Value Meaning
LVRLOG/AUDIT reports
ETN-UNVL ETN based Universal ETN-UNVL
Personality Universal
Station Module

ETN-UNVL ETN based Universal ETN-UNVL

Personality Universal
Station Module (PCUS)

KLCN-AM K2/K4LCN based KLCN-AM

Application Module

KLCN-EHB-JG K2/K4LCN based KLCN-EHB

Experion Hiway Bridge –
Junction Gateway

KLCN-EHB-SG K2/K4LCN based KLCN-EHB

Experion Hiway Bridge –
Simple Gateway

KLCN-ENB K4LCN based Enhanced KLCN-ENB

Network Bridge

KLCN-ENIM K4LCN based Enhanced KLCN-ENIM

Network Interface
Module

KLCN-HG K2/K4LCN based Hiway KLCN-HG

Gateway Module

KLCN-HMOF K2/K4LCN based History KLCN-HMOF

Module (OFF PROCESS)

KLCN-HMON K2/K4LCN based History KLCN-HMON

Module

KLCN-NIM K2/K4LCN based KLCN-NIM

Network Interface
Module

KLCN-NG K2/K4LCN based KLCN-NG

Network Gateway Module

KLCN-OPR K2/K4LCN based KLCN-OPR

Operator Personality
Universal Station Module

389
Chapter 8 - Verifying Operation of Experion LCN

Text shown in
$NODETYP Value Meaning
LVRLOG/AUDIT reports
KLCN-UNVL K2/K4LCN based KLCN-UNVL
Universal Personality
Universal Station Module

LCNP-AM LCNP4 based LCNP-AM

Application Module

LCNP-APP LCNP4 based LCNP-APP

Application Processing
Platform

LCNP-APP LCNP4 based LCNP-APP

Application Processing
Platform (EAPP)

LCNP-APP LCNP4 based LCNP-APP

Application Processing
Platform (ACET)

LCNP-EST LCNP4 based Experion LCNP-EST

Station

LCNP-ESVT LCNP4 based Experion LCNP-ESVT

Server

LCNP-GUS LCNP4 based Global LCNP-GUS

User Station

LCNP-OPR LCNP4 based Operator LCNP-OPR

Personality Universal
Station Module

LCNP-OPR LCNP4 based Operator LCNP-OPR

Personality Universal
Station Module (PCUS)

LCNP-UNVL LCNP4 based Universal LCNP-UNVL

Personality Universal
Station Module

LCNP-UNVL LCNP4 based Universal LCNP-UNVL

Personality Universal
Station Module (PCUS)

390
 Chapter 8 - Verifying Operation of Experion LCN

Duplicate LCN Node Numbers

It is possible to inadvertently add a node with a duplicate LCN
node number/address of a running node. If this situation is left
undetected, the system may encounter unexpected conditions
due to messages traversing in both directions across the ELCN
Bridge.
To mitigate this failure mode, the ELCN Bridge recognizes the
receipt of messages from either the LCN or ELCN side with the
same LCN Node Number. The ELCN Bridge annunciates the
condition as an Experion System Alarm and refuses to pass
traffic from an ELCN Node to a legacy LCN node with the
duplicate node number.

Indication of duplicate LCN Node Numbers

The following indications annunciate the occurrence of
duplicate LCN Node Numbers:
n An alarm will display on Experion Station with the text
Duplicate LCN Node Addresses Detected.
n The ELCN Bridge platform block in the Control Builder
Monitoring side show Soft Failure, and the Soft Failures tab
shows the LED Duplicate LCN Node Addresses Detected
illuminated in red.
When assigning or changing the LCN node number of any LCN
or ELCN node, it is imperative that the intended node number
is not already in use by another LCN or ELCN node.
If you cause a duplicate node number situation to occur, the
invalid duplicate node fails, and the existing running node may
become ISOLATED from some LCN and ELCN nodes. To
recover from this situation, perform the steps in section “"To
recover from duplicate LCN Node Numbers and ISOLATED
Nodes" below”.

To recover from duplicate LCN Node Numbers and

ISOLATED Nodes
1. Power-off the off the node with the invalid address.
2. Change its LCN node number to an unused LCN address.
3. Power the node back on

391
Chapter 8 - Verifying Operation of Experion LCN

4. Reload the existing running node that has the correct node
number (and may have become ISOLATED).To load an
ISOLATED ELCN Node, first shut down the node (using the
System Status display in Native Window) and then load the
node.

Redundancy Operation
Synchronization States
The RDNSYNCSTATE parameter indicates the synchronization
state of a redundant ELCN Bridge or a redundant ELCN
Appliance Node.
Given a redundant pair, synchronization is the act of
transferring configuration and execution data from the primary
to the secondary, so that the secondary has the same
information as the primary when it is needed to transition into
the primary role.
Synchronization is only possible for a compatible redundant
pair. When a compatible partner is found, the UEA 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 Control Builder are loaded,
the redundant UEAs are in the Sync in Progress state. After
initial-sync completes, the redundant pair enters the
Synchronization Maintenance state during which
synchronization is maintained (data that changes is
synchronized to the secondary), and the secondary is a viable
replacement for the primary.
Synchronization states of Redundant ELCN Bridge and ELCN
Appliance Nodes:

392
 Chapter 8 - Verifying Operation of Experion LCN

Redundancy Failure Conditions and Switch Over

Indications
When an ELCN Bridge or ELCN Appliance Node switch over
occurs, you get Experion system alarms, including Partner not
visible on FTE network and Not Synchronized.

At any time, if you want to know if a switch over occurred, you

can also check for the following in the Redundancy tab on the
Detail Display or the platform block in the Monitoring side of
Control Builder (shown here).
n Last Loss of Sync Time indicates time of last switch over.
n 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 switch over.

ELCN Bridge Redundancy Commands

The following ELCN Bridge redundancy commands are
available on the Redundancy tab of the platform block’s
Monitoring side in Control Builder.

ATTENTION: The Redundancy commands can be

performed at the Operator access level; however, a
Redundancy command should be performed only when

393
Chapter 8 - Verifying Operation of Experion LCN

necessary and only when such action is intended by

personnel familiar with its purpose and effect.

Command Description

Disable Synchronization The Disable Synchronization command

triggers a synchronizing/ synchronized/
standby redundant pair to abort
synchronization. Also, the Auto-
Synchronization State is set to DISABLED.

Enable Synchronization The Enable Synchronization command

triggers an unsynchronized redundant pair
to attempt initial-synchronization.
Additionally, the Auto-Synchronization
State transitions to ENABLED (if previously
set to DISABLED).

Become Primary The Become Primary command is used to

cause an unsynchronized secondary to
transition into the primary role in the
absence of a partner. Specifically, this
command applies only if the
unsynchronized secondary has no view to a
partner across the redundancy cable and
the primary IP address is not occupied.

Initiate Switchover The Initiate Switchover command triggers a

realistic switchover scenario. The original
primary reboots into the secondary role
and the Synchronized or Standby
Secondary assumes the primary role to
continue operations.

ATTENTION: After initiating a

Switchover or a fresh power-on of a
redundant ELCN Bridge, wait for at
least three minutes after the pair of
ELCN Bridges show the
Synchronization State of
SYNCMAINT before initiating
another Switchover operation. This
allows the pair of ELCN Bridges to
fully synchronize.

394
 Chapter 8 - Verifying Operation of Experion LCN

Handling Dual-Fault Scenarios

The redundancy on the ELCN Bridge or ELCN Node does not
support a “dual fault” scenario. The redundancy scheme
handles a single fault, but a dual fault does not cause a switch
over to the backup, so a loss of view may occur.
Single fault: Both FTE cables or both LCN cables or the
redundancy link cable – this is handled by the redundancy
scheme.
Dual fault: Such as the redundancy cable fault, followed by
both FTE cables – this does not cause a switch over to the
backup.
After fixing the “dual fault,” you must reboot the node with the
fault condition.
In the event of an FTE dual cable fault on a redundant ELCN
Appliance Node, after three seconds the UEA hardware reboots
and comes back to the PWR_ON state, requiring a load
operation from the Native Window.

ELCN UEA States and Transitions

The following diagram illustrates Application States and
transitions between states during the life cycle of an ELCN
UEA.

395
CHAPTER

9 MANAGING LCN AND ELCN NODES USING

EXPERION DASHBOARDS

In this section:

Introducing Experion Dashboards 397

Dashboard Configuration Checklist 398
Configuring ES-T connection for dashboards 410
Configuring which display is called up by the TPS System
and Console Status indicators 411
Viewing LCN and ELCN node status in Experion using
automatically created dashboards 412
Operations on LCN and ELCN nodes from Experion 412
Calling up Native Window displays from Experion 413
Configuring Experion options for managing LCN and ELCN
nodes 414
Collecting On-Demand Dump 414
Reducing load caused by ELCN System Management
Dashboard on LCN data owners 415

396
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Introducing Experion Dashboards

The Dashboard pane in the Experion System Status display
provides a graphical view of the status of your system and
network components in a way that allows relationships and
criticality to be represented. The LCN and ELCN nodes of your
system are represented in one or more dashboard displays that
are automatically created and maintained by Experion.
In this discussion of Experion dashboard displays, the term
LCN and ELCN nodes represents the following:
n LCN and UCN nodes connected with coaxial cable,
n ELCN nodes connected with the FTE network, and
n ELCN bridges.
To use an automatically generated dashboard across DSA, the
dashboard can be copied to another FTE cluster; however, the
dashboard components will not be updated across DSA. For
example, a copied dashboard will display status information
correctly, but the components included on the dashboard will
not be updated to reflect changes made in TPS. If you are
migrating a system that has multiple ESVTs on a single LCN, a
review of the FTE community configuration needs to be done in
consultation with Honeywell Technical Assistance Center (TAC).
LCN and ELCN nodes can also be represented in custom
designed dashboard displays that you create and maintain. If
you create a custom dashboard, it is important that you save
the display file somewhere other than the
AutoGeneratedDashboards folder and you should use a file
name for the display that will not be confused with the
automatically created dashboards. Automatically created
dashboards have a file name that begins with auto.
REFERENCE: For more information about Experion dashboard
displays, refer to following documents:
n “About dashboard displays”, HMIWeb Display Building
Guide
n “Using the Dashboard pane on the System Status display”,
Experion Operator’s Guide

397
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

n “Creating a dashboard display”, Experion HMIWeb Display

Building Guide
n “Creating a dashboard hierarchy for the System Status
display”, Experion Server and Client Configuration Guide

Dashboard Configuration Checklist

Configuring ES-T connection for dashboards
ESVTs cannot access system information directly from LCN
and ELCN nodes, therefore, ESVTs must be configured to
access LCN and ELCN node information via an ES-T. You can
change which ES-T is used by an ESVT to receive the required
information.
LCN and ELCN node information is used to create the
automatically created dashboards. For more information about
these dashboards, see “Viewing LCN and ELCN node status in
Experion using automatically created dashboards.”
Additionally, LCN and ELCN node status information is also
sourced via this connection. If the connection between an ESVT
and the selected ES-T fails, the automatically generated
dashboards will not be updated with new or deleted LCN and
ELCN nodes and node status will not 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 status
information
1. In Configuration Studio, click the ESVT node, then click
System Interfaces, and then click Configure System

398
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Interfaces.

2. Under System Configuration, click System Hardware, click

System Interfaces, select TPS from the System Interfaces
dropdown.

3. On the Configuration tab, in the Configuration options

section, select the ELCN ES-T node from the dropdown 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 and status
information to be shown on Flex Stations.

399
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Configuring which display is called up by the TPS

System and Console 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

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 and Call up Experion
Console Detail display for TPS Console Status according to
how you want the TPS System 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.

400
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

2. Make sure all the ELCN nodes are selected as members of

the FTE community, click Apply, and then click OK.

NOTE: You can select the other Experion nodes which

need to appear in System Tree view as well based on
your requirements.

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.

401
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

The network loading on the selected server proceeds.

6. From the Station, go to the Location Pane, navigate to

Network > Devices > FTE Community to see the nodes
loaded to the Experion server.

Configuring File Replication of the ELCN Dashboards

on Flex Stations and Console Extension Stations
1. In Configuration Studio, navigate to the System Name >
Servers > ESVT >Advanced Options > File Replication, and

402
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

then click Configure file replication.

2. Click the “abstract” file replication entry from the list by

clicking in the blank space under Name column in front of
the row 1.

3. On the configuration page for the “abstract” file replication,

select the “Specific PC’s” check box and add the network
name of each Flex Station and Console Extension Station

403
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

that requires the LCN Status 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, and then click Configure
operators and Windows group accounts.

404
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

2. Select an operator or group.

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 Status dashboards
are shown underneath System Alarm Groups. Give the
operator or group access to the required dashboards by

405
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

assigning access to the local server.

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

Configuring Flex Station access to ELCN Dashboards

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

406
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

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

3. Click the General tab and select the dashboard from the
Default dashboard dropdown.

4. Click the Assignment tab, then select the Direct Assignment

option. The LCN System Status and UCN Status dashboards
are shown underneath System Alarm Groups. Give the flex
station access to the required dashboards by assigning

407
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

access to the local server.

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 and Consoles, then under
Stations and Consoles, if all console stations belong to a
console select Configure consoles, otherwise select
Configure console stations.

408
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

2. Select a console or console station.

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 UCN Status dashboards
are shown underneath System Alarm Groups. Give the
console or console station access to the required

409
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

dashboards by assigning access to the local server.

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

NOTE: If you are invoking a dashboard over a ELCN

network for the first time, note that it may take at least
three seconds for each configured LCN/UCN/IOP
point to be created in the Server and populated
under Location pane tree view, therefore, it may take
several minutes to create LCN/UCN dashboard
depending on the number of nodes configured in
LCN/UCN network. Once all the configured points are
created in the Server and populated under Location
pane tree view, you can invoke the respective
dashboard on any ELCN ES-T in the ELCN network
without any errors.

Configuring ES-T connection for dashboards

ESVTs cannot access system information directly from LCN
and ELCN nodes, therefore, ESVTs must be configured to
access LCN and ELCN node information via an ES-T. You can
change which ES-T is used by an ESVT to receive the required
information.
LCN and ELCN node information is used to create the
automatically created dashboards. For more information about
these dashboards, see “Viewing LCN and ELCN node status in
Experion using automatically created dashboards.”

410
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Additionally, LCN and ELCN node status information is also

sourced via this connection. If the connection between an ESVT
and the selected ES-T fails, the automatically generated
dashboards will not be updated with new or deleted LCN and
ELCN nodes and node status will not 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 status
information
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, in the ES-T for Flex Station ELCN
Dashboards list, click the ES-T computer name that will be
used to source the automatic dashboard component and
status information to be shown on Flex Stations.

Configuring which display is called up by the

TPS System and Console 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 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 and Call up Experion
Console Detail display for TPS Console Status according to

411
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

how you want the TPS System and Console Status indicators
to function.

Viewing LCN and ELCN node status in

Experion using automatically created
dashboards
To view LCN and ELCN 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 Status or
UCNxx Status, where xx is the UCN process network
number.
RESULT: The LCN and ELCN nodes included in the selected
dashboard will be shown with status information in a layout
similar to Native Window.

TIP: To maximize the space available to show LCN and

ELCN nodes in the Dashboard pane, it is not
recommended to have the Location pane open at the
same time as the Dashboard pane.

Operations on LCN and ELCN nodes from

Experion
Operations can be performed on LCN and ELCN nodes from
the Status pane of the Experion System Status display or the
detail display of the node.
REFERENCE: For more information, refer to the following
documents:
n “System Status Display Status pane reference”, see the
Experion Operator’s Guide.

412
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

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

To perform an operation on an LCN node or on an

ELCN node from Experion
1. In the Experion System Status Summary display, open the
dashboard that includes the required component.
2. You can perform operations from the Status Pane or the
detail display associated with a component:

For these operation Do

LOAD (NET) 1. On the dashboard, select the

component.
SAVE (NET)
2. Open the Status Pane.
DUMP (NET)
SHUTDOWN
RESTORE

Other operations. For example, 1. On the dashboard, double-

Load, Save, or Dump to specific click the component.
locations.
The detail display of the
component will appear.
2. On the detail display, click
the Commands tab.

3. Click the required operation and follow the prompts.The

status of the component may be updated on the dashboard
if relevant.
REFERENCE: For more information, see “Components of the
System Status display” in the Experion Operator’s Guide.

Calling up Native Window displays from

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

413
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Similarly, the Native Window Console Status display will be

called up instead of the Experion Console detail display if you
click C in the Station Status Bar.
REFERENCE: For more information, see section "Configuring
which display is called up by the TPS System and Console
Status indicators".
Alternatively, you can call up the relevant Native Window
display from the Status pane associated with the selected
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 an LCN node or an ELCN
node.
2. Open the Status pane.
3. Click to open the relevant Native Window display for the
selected component.

Configuring Experion options for managing

LCN and ELCN nodes
To assist with managing LCN and ELCN nodes, you must
configure which ES-T connection is used to gather component
and status information to be shown on dashboards. You can
also configure which display is called up when the TPS System
or Console Status indicator buttons are clicked on the Experion
Station Status Bar.

Collecting On-Demand Dump

Beginning with R501.6, A new feature called On-Demand
Dump is introduced on the Experion System Management
Dashboard on an ELCN ES-T to generate a dump of any ELCN
node in the network while the node is in one of the running
states as follows: OK, BACKUP, WARNING, and SEVERE. The
captured dump is analyzed later by a Honeywell representative
to understand the node's behavior in the ELCN network.

414
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Note that this option is available only on ELCN ES-T.

Reducing load caused by ELCN System

Management Dashboard on LCN data owners
If the ELCN System Management Dashboard is running on an
ELCN ES-T, the Dashboard fetches some predefined system
parameters from all LCN/ELCN nodes in the network, this may
put additional load on the LCN data owners, such as, ENIM,
HG, AM. If you do not want to put this additional load caused by
the ELCN System Management Dashboard of the ELCN ES-T,
you can optionally disable the ELCN System Management
Dashboard functionality of the ELCN ES-T that is putting this
additional load on the LCN data owners by performing the
following procedure:

415
 Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Step Action

1 From the ELCN ES-T’s Native Window, navigate to the STATUS DETAIL
DISPLAY and then select SM Interface as shown in the following image
and then click VIEW OBJECT DETAIL.

2 Click STOP and then press ENTER to stop the TPN System
Management Interface. This will block all data access to TPN from the
ELCN ES-T for ELCN System Management Dashboard.

RESULT: The status shows that the ELCN System Management

interface is not running.

416
Chapter 9 - Managing LCN and ELCN Nodes Using Experion Dashboards

Step Action

NOTE: With this procedure, note that the ELCN System Management
Interface task resumes the next time you launch Native Window.

417
CHAPTER

10 SERVICING AND TROUBLESHOOTING

EXPERION LCN

In this section:

Replacing UEA Hardware 419

Troubleshooting Tools 419
Responding to Soft Failures 420
To resolve node state FAIL or ISOL mismatch between
displays 424
Responding to Control Builder Error 2123 425
Manually Rebooting UEA from Front Panel Display 426
Troubleshooting LCN Coax Cables on an ELCN Bridge 428
Updating Firmware on Operational UEAs 442
Checking Microsoft Windows application event logs for
errors 477
Capturing Failure Status for Honeywell Technical
Assistance Center Analysis 481
Resolving data communication loss between ELCN-
EPLCGs and PLCs 483
Reducing load caused by ELCN System Management
Dashboard on LCN data owners 484
ELCN Bridge 484

418
Chapter 10 - Servicing and Troubleshooting Experion LCN

Replacing UEA Hardware

REFERENCE: For the procedure to replace UEA hardware, refer
to the ELCN Planning, Installation, and Service Guide, section
“Replacing the UEA in a Cabinet”.

Troubleshooting Tools
Troubleshooting Displays
The following displays can be used to troubleshoot failures or
issues on the ELCN:
n Experion System Status Display
n Experion Node Detail Display/Faceplate
n Native Window System Status Display
n Experion Alarm Summary and Event Summary - View >
Events > Event Summary.

ELCN Statistics
The Experion Detail Display shows statistics on the Main tab.
The platform block in Control Builder has a Statistics tab. The
statistical parameters are used for maintaining and monitoring
data flow, network statistics, etc.
REFERENCE: The following sections of the Control Building
User Guide summarize the parameter data you can monitor:
“ELCN Bridge Configuration Form Reference” and “ELCN Node
Configuration Form Reference”.

CPUFREE behavior with ELCN

CPUFREE is the available processing capacity of the UEA box
CPU, based on the status from its operating system.
Following are the differences in CPUFREE behavior with ELCN:
n There is a mismatch between the CPUFREE values shown
on the Control Builder platform block and the Native
Window. This is due to the fact that the Control Builder
platform block’s CPUFREE (%) value (parameter

419
 Chapter 10 - Servicing and Troubleshooting Experion LCN

CPUFREEAVG) indicates the overall UEA box processing

capacity, whereas the Native Window CPUFREE parameter
value indicates the UEA box’s LCN emulation processing
capacity.
n For the same load on an AM or ENIM, the CPUFREE values
shown for a Classic AM or ENIM and an ELCN-AM or ELCN-
ENIM are different, as they run on different hardware
platforms.
n For the same load on an HM or Experion TPS nodes (E-APP,
ES-T, ESVT, and ACE-T), the CPUFREE values shown for a
Classic HM or LCNP4- based Experion TPS nodes and
ELCN- HM or ELCN Experion TPS nodes are different, as
they run on different hardware platforms.
n For the same load on an ES-T Node, the CPUFREE values
shown for a PC-based Microsoft Windows 10 ES-T node and
Virtual Microsoft Windows Server 2016 ES- T node are
different, as they run on different Microsoft Windows
Operating System platforms.
n When an ELCN NG is loaded beyond the maximum PARSEC
limit (1200 PARSEC) and if a single or a dual PIN cable fault
occurs, the ELCN NG’s CPUFREE value will go to zero. To
recover from the zero CPUFREE situation, reload the node.

Responding to Soft Failures

Soft failures do not cause a change in the state of the
execution environment. There is no loss of control or loss of
view when the ELCN Bridge or ELCN Node detects a soft
failure.
In a redundant pair,
n a soft failure in a synchronized primary does not cause a
switchover to the backup, and
n a soft failure in the backup does not result in a loss of
synchronization if the redundant pair is synchronized.
Experion reports ELCN Soft Failures in the following displays:
n Alarm Summary

420
Chapter 10 - Servicing and Troubleshooting Experion LCN

n Monitoring side of the Control Builder block, Soft Failures

tab (the following example shows the ELCN Bridge)
n Detail Displays in Station – for ELCN Bridges and ELCN
Appliance Nodes
For more information, see the section “"Description of ELCN
Bridge and ELCN Node Soft Failures" below”.
Monitoring Side of Control Builder block - Soft Failures tab
(ELCN Bridge example)

Description of ELCN Bridge and ELCN Node Soft

Failures
The following table describes the ELCN Bridge and ELCN Node
Soft Failures.

Soft Failure Screen Text Condition when indicator is illuminated

Corrected Internal RAM Sweep Error True if a correctable memory error has
been detected within the last 24 hours.

Critical Task Watchdog Warning True if one or more tasks fails to update
the critical task watchdog within 5
seconds.

Duplicate LCN Node Addresses Applies only to ELCN Bridge - The second
Detected node with the same LCN node number will
not start up properly. This node will need to
be shut down, reconfigured, and then
reloaded.

421
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Soft Failure Screen Text Condition when indicator is illuminated

REFERENCE: Refer to section “"To recover

from duplicate LCN Node Numbers and
ISOLATED Nodes" on page 391”.

ELCN Bridge Partner has Different Applies only to ELCN Bridge - The
Network View redundant ELCN Bridge partners do not
see the same LCN nodes. Check LCN cable
status.
Occasionally, when performing certain
node loading scenarios on the network, one
or both of the redundant ELCN Bridges
may report this soft failure for a short
period of time. This is due to each ELCN
Bridge separately updating its view of the
network, and they become slightly out of
sync. If the soft failure still exists after 10
minutes, use the Detail Display’s “Bridge
Status” tab to compare the view from both
the Primary and Secondary. If the view
from the Backup is different than the view
from the Primary, consider rebooting the
backup ELCN Bridge.REFERENCE: For the
procedure, refer to section “"Manually
Rebooting UEA from Front Panel Display"
on page 426”.

Enclosure Temperature Critical True if the enclosure temperature exceeds

the critical limit.

Factory Data Error True if the factory data in the device

EEPROM is missing or invalid for the
currently loaded firmware.

Fan Fault Condition The UEA box has detected the cooling fan
is not operational.

FPGA Hardware Failure True if the device detects a failure with the
FPGA functionality.

FTE Network Error FTE Network has partially failed – there is

an FTE connection failure at the ELCN
Bridge or ELCN Node.

Key switch in ‘C’ position The UEA box has its key switch in the

422
Chapter 10 - Servicing and Troubleshooting Experion LCN

Soft Failure Screen Text Condition when indicator is illuminated

configuration position. The “C” indicates

that the UEA box key state currently
enables user configuration editing, node
rebooting, and initializing the node to the
boot/recovery personality image, also
known as the factory (FACT) image.
Although the box is operational with the
key switch in the “C” position, it is
vulnerable to being made unusable for its
specific application function.

LCD Display Panel Errors The UEA box front panel display is not
operational.

Minimum Recommended HW Revision True if device hardware fails to meet the

minimum recommended hardware revision
for the currently loaded firmware.

Partner Not Visible on FTE Network True if the redundant partner is not visible
on the FTE network.

Power Supply Alarm The UEA box power is beyond operating

limits.

Thermometer Failure True if the device hardware thermometer

has failed.

Uncorrectable Internal RAM Sweep True if an uncorrectable memory error has

Error been detected.

WDT Hardware Failure True if the device detects a failure with the
hardware watchdog functionality. Note that
this diagnostic detects only if the hardware
watchdog is functioning.

Diagnostic Traces Enabled; True if a Trace Flags parameter(s) is

configured with a nonzero value and the
Diagnostic Trace Enabled parameter is
enabled on the Traces tab of a ELCN Node
platform block.

Deployment incomplete True when an additional switch over is

required after an onprocess migration from
any pre-R501.6 release to R501.6 or later
release.

423
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Soft Failure Screen Text Condition when indicator is illuminated

ETH1 communication error True if there is a communication breakage

over this NG’s PIN A cable.

ETH2 communication error True if there is a communication breakage

over this NG’s PIN B cable.

NOTE: This is applicable only if the

NG is configured to communicate
over both PIN A and PIN B cables.

To resolve node state FAIL or ISOL mismatch

between displays
Symptom
In the case of a TPN personality failure of an ELCN Appliance
Node or if the ELCN Appliance node goes to ISOLATED state,
only the Native Window displays the correct state of FAIL or
ISOL respectively - however, the same states are not reflected
on the following displays:
n Control Builder Monitoring side - Main tab "Node State"
n Experion Faceplate Display
n UEA Front Panel Display
Cause
Anomaly
Solution
Reboot the UEA at the physical box.
REFERENCE: For the procedure, see section “"Manually
Rebooting UEA from Front Panel Display" on page 426”.
Result
Consistent display of Node State.

424
Chapter 10 - Servicing and Troubleshooting Experion LCN

Responding to Control Builder Error 2123

Symptom
The platform blocks in Control Builder for the ELCN Bridge or
ELCN Appliance Node cannot be loaded and the following
Control Builder error occurs:
*EXPKS_E_Bad EE Code (6L .101.2123) ELCNBRG or
ELCNNODE_<nodenumber>: Null or invalid EE Code in System
Handle
REFERENCE: For other Control Builder errors, refer to the
Control Builder Error Code Reference.
Cause
The internal synchronization between Control Builder and the
module has been lost. The issue may occur rarely in certain
scenarios as follows:
n migration between releases
n forced delete of the block from the Control Builder
Monitoring side (or clearing the ERDB) and recreation of the
block in the Control Builder
Solution
To resolve the error, you must clear the EE Code in the UEA.
Detailed procedure is as follows.

ATTENTION: Note that this procedure will restart the UEA,

resulting in temporary loss of function.

Result
After Reboot, the UEA no longer knows its previous state, and
you can successfully load the platform block in Control Builder
to the respective UEA.
Perform the following steps to clear the EE Code and restart
the UEA.

Done
Step Action
(Ö)

1 If the nodes are redundant, SHUTDOWN the secondary

425
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Done
Step Action
(Ö)
node from the platform block in Control Builder Monitoring
side. At the secondary UEA node – wait until the node
restarts and shows Ready on the Front Panel Display.

2 At the UEA primary node, rotate the key clockwise to the C

position.
RESULT: The display shows DETAILS, CONFIG, TEST and
REBOOT options.

3 Select the CONFIG option on the main menu and press OK.
RESULT: The display shows the UEA configuration menu.

4 Press the bottom navigation arrow until the SAVE/RBOOT

option is highlighted and then press OK.
RESULT: The UEA begins rebooting and the front panel
display reflects that process.
When the reboot completes, the UEA display should show
NotLoaded state.

5 If the nodes are redundant, restart the secondary node

following the procedure “"Manually Rebooting UEA from
Front Panel Display" below”.
RESULT: the node restarts and transitions to the
ConfigWait state on the UEA display.

6 Load the platform block to the Monitoring side in Control

Builder.

Manually Rebooting UEA from Front Panel

Display
After a failure, the UEA may need to be manually Rebooted. The
Reboot must be performed from the front panel display at the
physical UEA box.

426
Chapter 10 - Servicing and Troubleshooting Experion LCN

To Manually Reboot UEA from Front Panel Display

Done
Step Action
(Ö)

1 Rotate the key clockwise to the C position.RESULT: The display

shows DETAILS, CONFIG, TEST and REBOOT options.

2 Select the REBOOT option on the main menu as follows:

Press the down navigation arrow to highlight DETAILS.
Press the right navigation arrow to highlight REBOOT.
Press OK to select REBOOT.
RESULT: The display shows the UEA Reboot/FactoryInit menu.

3 Press the right navigation arrow to highlight RBOOT, then press

OK to execute the reboot command.

RESULT: The UEA begins Rebooting and the front panel display
reflects that process.
When the Reboot completes, the UEA should be in one of the
following states:
OK
BACKUP
NOTLOADED (Need to load the platform block from Control
Builder.)

4 EXIT to return to the main menu.

5 Rotate the key switch to the R1 or R2 position. You may remove

the key as desired.

NOTE: If the key switch remains in the C position, a soft

failure alarm is generated to inform the Experion users. The
alarm is shown on the Station alarm displays and Detail
Display, and the platform block Monitoring side in Control
Builder.

427
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Troubleshooting LCN Coax Cables on an ELCN

Bridge
A major function of the redundant ELCN Bridge is to
communicate on the LCN. Both the primary and secondary
ELCN Bridges have LCN coax cables, cable A (yellow) and cable
B (green), connected to the existing LCN network. The LCN
node numbers of the primary and secondary ELCN Bridges are
hard-coded as 97 and 98, which are higher than the legacy
LCN node range of 1-96, so they do not appear as nodes on the
Native Window LCN System Status display or LCN Cable
Diagnostic displays.
Important: If you are migrating from LCN to Experion LCN, and
are in the transition period during which ELCN Bridge(s) are in
place, you must be aware of how ELCN Bridge LCN Cables
affect the existing LCN cable troubleshooting procedures.
As with other LCN nodes, an LCN cable fault on the ELCN
Bridge(s) may cause a SUSPECT LCN cable state (as shown
from the Native Window System Status display); however, the
existing LCN Cable troubleshooting tools and schematics used
to identify the cause of such errors cannot identify the ELCN
Bridge(s) as the cause.
When any SUSPECT LCN cable occurs anywhere on the LCN
coax network (node numbers 1-96),
n The LCN Native Window reports the LCN cable as
“SUSPECT” when there is an active LCN cable fault - this
fault may or may not be caused by the ELCN Bridge.
n There is no indication on the Experion ELCN Bridge status
displays, other than an increase of statistical counts of
Media Deads for LCN Cable A or B.
n The Experion System Status reports the LCN System alarm
caused by the faulty LCN cable. This is aggregated from the
“S” LED on the status bar of the Native Window on an ES-T.
It also is shown as an “S” on the bottom of an ES-T’s
Experion Station display.
n Use the existing LCN Cable Troubleshooting methods to
find the LCN Cable fault.

428
Chapter 10 - Servicing and Troubleshooting Experion LCN

If you have followed the existing LCN cable troubleshooting

procedures and have not found an existing LCN node in the
range of 1-96 to be the cause of the problem, then the cable
fault problem may lie in the ELCN Bridge nodes 97 and/or 98
or associated hardware on the ELCN side of your LCN-ELCN
system, and you should view the Experion displays for
additional information.
When an ELCN Bridge detects an LCN coax cable connectivity
error with its own LCN cable,
n The ELCN Bridge sets that specific LCN Cable Status to a
Failed state.
n The Faceplate area of the ELCN Bridge Experion Detail
Displays indicate which LCN cable has failed through the
respective LCN LEDs.
n The Experion System Alarm Summary annunciates the
alarm.
n The alarm description on the Experion Alarm Summary
provides detailed information identifying the specific ELCN
Bridge and specific LCN cable as the cause of the LCN
cable failure.
Six examples of detected errors with associated display
indications are provided as follows:
Example 1
A non-ELCN Bridge coax-based node (for example, an ES-T) in
the LCN network has a fault on LCN Cable A, which causes a
SUSPECT LCN Cable A condition.
Native Window
n The Native Window indicates Cable A as SUSPECT. Click the
“S” button to display the Native Window System Status.

429
 Chapter 10 - Servicing and Troubleshooting Experion LCN

n On an Experion Station (ES-T), an LCN System Alarm is

annunciated by a highlighted “S” button.

ELCN Bridge Detail Display

n Neither ELCN Bridge detects an LCN cable fault on its own
local LCN cables.
n The ELCN Bridge(s) Local LCN Status LED indicators do not
show LCN cable faults emanating from the LCN coax-based
network (they will only show LCN cable faults emanating

430
Chapter 10 - Servicing and Troubleshooting Experion LCN

from their own, individual (local) ELCN Bridge hardware).

Example 2
The primary ELCN Bridge (named ELCN_BRG_WEST in this
example) detects an error on its own LCN Cable A, causing the
active LCN cable to swap to LCN Cable B.
Native Window
n The Native Window indicates SUSPECT for LCN Cable A.

Experion Alarm Summary

n The alarm Source indicates the primary ELCN Bridge,
ELCN_BRG_WEST.

431
 Chapter 10 - Servicing and Troubleshooting Experion LCN

n The alarm Description is ELCN Bridge has a Failure on its

own Local LCN Cable A.

ELCN Bridge Detail Display

n A red LED indicates that the Local LCN Cable A Status is
bad on the primary ELCN Bridge.
n The presence of the Alarm text indicates that an alarm is in
the Experion System Alarm Summary Display.
n The secondary ELCN Bridge shows both LCN cables as
good and the active LCN cable is B (white color).

Example 3
The primary ELCN Bridge (named ELCN_BRG_WEST in this
example) detected an error on its own LCN Cable B, causing
the active LCN cable to swap to LCN Cable A.

432
Chapter 10 - Servicing and Troubleshooting Experion LCN

Native Window
n The Native Window indicates SUSPECT for LCN Cable B.

Experion Alarm Summary

n The alarm Source indicates the primary ELCN Bridge,
ELCN_BRG_WEST.
n The alarm Description is ELCN Bridge has a Failure on its
own LCN Cable B.

Primary ELCN Bridge Detail Display

n A red LED indicates that the LCN Cable B Status is bad on
the primary ELCN Bridge.
n The presence of the Alarm text indicates that an active
alarm is in the Experion Alarm Summary.
n The secondary ELCN Bridge shows both LCN cables as
good and the active LCN cable is A (white color).

433
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Example 4
The secondary ELCN Bridge (named ELCN_BRG_WESTSEC in
this example) detected an error on its own LCN Cable A,
causing the active LCN cable to swap to LCN Cable B.
Native Window
n The Native Window indicates SUSPECT for LCN Cable A.
Experion Alarm Summary
n The alarm Source indicates the secondary ELCN Bridge,
ELCN_BRG_WESTSEC.

434
Chapter 10 - Servicing and Troubleshooting Experion LCN

n The alarm Description is ELCN Bridge has a Failure on its

own LCN Cable A.

ELCN Bridge Detail Display

n The red LED indicates that the LCN Cable A Status is bad on
the secondary ELCN Bridge.
n The presence of the Alarm text indicates that an alarm is in
the Experion Alarm Summary.
n The primary ELCN Bridge shows both LCN cables as good
and the active LCN cable is B (white color).

Example 5
The secondary ELCN Bridge (named ELCN_BRG_WESTSEC in
this example) detected an error on its own LCN Cable B,
causing the active LCN cable to swap to LCN Cable A.

435
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Native Window
n The Native Window indicates SUSPECT for LCN Cable B.
Experion Alarm Summary
n The alarm Source indicates the secondary ELCN Bridge,
ELCN_BRG_WESTSEC.
n The alarm Description is ELCN Bridge has a Failure on its
own LCN Cable B.

ELCN Bridge Detail Display

n The red LED indicates that the LCN Cable B Status is bad
on the secondary ELCN Bridge node.
n The presence of the Alarm text indicates that an alarm is in
the Experion Alarm Summary.
n The primary ELCN Bridge shows both LCN cables as good
and the active LCN cable is A.

436
Chapter 10 - Servicing and Troubleshooting Experion LCN

Example 6
The secondary ELCN Bridge (named ELCN_BRG_WESTSEC in
this example) detected a dual LCN cable fault on its own LCN
Cables. Since it is a secondary ELCN Bridge, the redundancy
mechanism does not initiate a switch over. Note that a dual
LCN cable fault on a primary ELCN Bridge causes a switch over
to the secondary (if the secondary is present and
synchronized).
Native Window

437
 Chapter 10 - Servicing and Troubleshooting Experion LCN

n The Native Window indicates SUSPECT for LCN Cable A and

for LCN Cable B.

Experion Alarm Summary

n The alarm Source indicates the secondary ELCN Bridge,
ELCN_BRG_WESTSEC.
n The Alarm Descriptions are:
n Not Synchronized
n ELCN Bridge has a Failure on its own LCN Cable A
n ELCN Bridge has a Failure on its own LCN Cable B

Secondary ELCN Bridge Detail Display

n The red LEDs indicate that LCN Cable A Status and LCN
Cable B Status are bad.
n The Front Panel Display indicates No LCN Cables.
n The presence of the Alarm text indicates that an active
alarm is in the Experion Alarm Summary.
The primary ELCN Bridge shows both LCN cables as good
and the active LCN cable is B (white color).

438
Chapter 10 - Servicing and Troubleshooting Experion LCN

ELCN Bridge Statistics

View the ELCN Bridge Statistics for both the primary and
secondary ELCN Bridge using either of the following displays -
these displays show the same tabs with the same information:
n In Experion Station – Experion ELCN Bridge Detail Display –
Bridge Statistics Tab
n In Control Builder – Monitoring side of ELCN Bridge Block –
ELCN Bridge Statistics Tab
The monitoring side of the primary ELCN Bridge Control
Builder block (named ELCN_BRG_WEST) is illustrated below.
n The ELCN Bridge Statistics tab shows the Alone in Ring and
Media Dead counters for LCN Cable A and LCN Cable B.
n The “Total Cable A Media Dead” and “Total Cable B Media
Dead” statistics show counts for the entire LCN coax-based
network, including LCN cable faults on the ELCN Bridge(s).
n The “Total Cable A Alone in Ring” and “Total Cable B Alone
in Ring” statistics typically show counts for LCN cable faults
on the individual ELCN Bridge node experiencing the LCN
cable fault.

The Experion Station ELCN Bridge Detail Display (named

ELCN_BRG_97) is illustrated below. Note that no faults are
shown in this example (counts all are 0).

439
 Chapter 10 - Servicing and Troubleshooting Experion LCN

ATTENTION: Prior to checking the ELCN Bridge, or

associated hardware on the ELCN side of your LCN-ELCN
system, to locate the cause of a cable error, inhibit LCN
Cable Swapping. This is a precautionary measure that is
recommended for critical process control systems.

or associated hardware on the ELCN side of your LCN-ELCN

system
If you determined that the ELCN Bridge or associated hardware
may be the cause of the problem, go to the physical ELCN
Bridge hardware and check the components listed in the table
that follows.
REFERENCE: For more information, refer to the ELCN
Planning, Installation, and Service Guide.

Component Action

LCN MAU cable connection to the Ensure that the Yellow and Green MAU
UEA termination module cables connect securely to the MAU ports
on the UEA termination module. Make sure
that the MAU connector/receptacle,
pins/sockets are not bent, loose or pushed.
Make sure connectors and receptacles are
free from corrosion and contaminants.
Make sure that the physical and electrical
attachments between each MAU cable

440
Chapter 10 - Servicing and Troubleshooting Experion LCN

Component Action

connector and its associated cable is not

degraded or compromised.

Connections to BNC Tees (LCN MAU Ensure that the yellow and green MAU
connectors and LCN cable connectors connect securely to the BNC Tee
connectors) connectors of the existing LCN cables.
Ensure that all LCN cable connections to
BNC Tees are secure. Make sure all
connectors and receptacles are free from
corrosion and contaminants. Make sure
that the physical and electrical (center
conductors/shielding) attachments
between each cable connector and its
associated cable is not degraded or
compromised.

Replaceable components Replace any of the following components to

attempt to resolve the condition:
l MAU cables
l BNC Tees
l UEA Termination Module
l UEA Processor Module

Next Step
If it was necessary to perform LCN cable maintenance, after
performing the LCN cable repair, check the Detail display for
the ELCN Bridge to verify that its Local LCN Status LEDs have
returned to normal (green).

441
 Chapter 10 - Servicing and Troubleshooting Experion LCN

The Native Window System Status Display may take several

minutes to reflect the good LCN cables. LCN Cables A and B
both need to show “OK” for LCN coax communications to
function properly.

Updating Firmware on Operational UEAs

NOTE: Node migration from prior release to R530.1 (or
later).
Follow the existing migration scenario with the addition of
the following steps to update the Boot/Recovery image
prior to the Application image.
l Update the Boot/Recovery image to UEA_120.1-01.0 (or
later) on the backup node.
l Update the Application personality image to be
compatible with the Boot/Recovery image on the backup
node.
l Ensure that the backup node synchronizes with the
primary.
l Wait for 5 minutes and perform a node failover.
l Update the Boot/Recovery image to UEA_120.1-07.0 on
the old primary node (new backup). ·
l Update the Application personality image that is
compatible with the Boot/Recovery image on the old
primary node (new backup).

NOTE: If the Boot/Recovery Firmware Upgrade from UEA_

100.1-11.0 to UEA_110.1- 03.0 of an ELCN Bridge/Node
fails with the error "Send Command Failed: Error Response
= (1017) Cannot Upgrade firmware. Module is on-control",
perform the following.

442
Chapter 10 - Servicing and Troubleshooting Experion LCN

1. Upgrade Primary and Backup ELCN APP image to the

latest Experion release version by performing the standard
on-process migration procedure provided in the section
"Updating Firmware on Operational UEAs".
2. After upgrading the ELCN APP image, upgrade the UEA
Recovery Image of primary and backup ELCN
Bridge/Nodes to the latest version by performing the
firmware upgrade procedure provided in section "To Update
Firmware on Operational Redundant ELCN Appliance
Nodes".

Overview of Firmware Update for Redundant ELCN

Bridge
The firmware loading for an operational redundant ELCN
Bridge is summarized as follows:
Prior to loading firmware
n Ensure that the UEA with the even-numbered Device Index
is operating as the secondary.. If this is not the case, then
from the secondary’s Experion Detail Display or from the
Monitoring side of the secondary ELCN Bridge platform
block in Control Builder, select the Initiate Switchover
command to make the primary Bridge the new secondary
Bridge.
n From the Monitoring side of the secondary ELCN Bridge
platform block in Control Builder, select the Shutdown
command to take the secondary from BACKUP to READY
state.
Firmware loading
n Use the Firmware Manager tool to load firmware on the
secondary, then wait for it to synchronize with the primary.
n Wait for 3 minutes before initiating a switchover.
n From the secondary’s Experion Detail Display or from the
Monitoring side of the secondary ELCN Bridge platform
block in Control Builder, select the Initiate Switchover
command to make the updated secondary the new primary.

443
 Chapter 10 - Servicing and Troubleshooting Experion LCN

n From the Monitoring side of the secondary ELCN Bridge

platform block (that is, the primary that has just become the
new secondary) in Control Builder, select the Shutdown
command.
n Use the Firmware Manager tool to load firmware on the new
secondary, then wait for it to synchronize with the primary.
n From the secondary’s Experion Detail Display or from the
Monitoring side of the secondary ELCN Bridge platform
block in Control Builder, perform an Initiate Switchover
command to return the updated secondary to be the new
primary.
REFERENCE: For the detailed procedure, refer to the section
“"To Update Firmware on Operational Redundant ELCN Bridge"
below”.

To Update Firmware on Operational Redundant ELCN

Bridge

Step Action Done

Ensure that the UEA with the even-numbered Device Index is operating as the
BACKUP ELCN Bridge

1 Go to either of the following displays to view the Device

Index of the Backup UEA:
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 “LCN” category, navigate
to and double-click on the secondary -
<nodename>SEC.
Monitoring side of platform block in Control Builder:
In Control Builder, double-click on the secondary ELCN
Bridge platform block - <nodename>SEC

2 Check that the UEA with the even-numbered Device Index

is Backup ELCN Bridge.

444
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

3 If the Backup ELCN Bridge does not have the even-

numbered Device Index, then go to the Monitoring side of
the secondary ELCN Bridge platform block in Control
Builder, select the Redundancy tab, and perform an
Initiate Switchover command.
RESULT: The UEA with the even-numbered Device Index
is now the Backup ELCN Bridge. Wait until the ELCN
Bridges come to OK and BACKUP states.

Shut down the secondary UEA to place it in the Ready state

4 Wait for 3 minutes and then from the Monitoring side of

the secondary ELCN Bridge platform block in Control
Builder, choose “Shutdown” from the “Module Command”
dropdown on the Main tab.

5 After you select the “Shutdown” command , a

confirmation dialog is displayed.
Click Yes to proceed with the Shutdown.
RESULT: The secondary UEA reboots and goes from the
BACKUP to READY state, as can be seen at the physical
UEA’s front panel display. The values on the Detail Display
show reverse video because the Shutdown removed the
ELCN Bridge platform block from the UEA.

NOTE: If the UEA is in the OK or BACKUP state

when you attempt firmware loading, the Firmware
Manager tool will not flash the firmware and will
return an error indicating that the “Module is On
Control”.

Open the Firmware Manager tool and select the node to be loaded

6 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 the FTE IP address and FTE Device Index of
each UEA.
The color of the Boot/Recovery and Application fields
indicates whether or not a more recent version of the

445
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

firmware is available.
Version status of UEA firmware images (Boot/Recovery
and Application):green – version supported and latest
blue – version supported but not latestred – version not
supported

7 Select the checkbox for the Backup ELCN Bridge in the

READY state (Name = primary tagnameSEC).

Use the color coding to determine which firmware images

need to be updated for the selected UEA.
UEA with a Device Index of 98, which is running as the
Backup ELCN Bridge is selected in the following example.
Both of its firmware images (Boot/Recovery and
Application) appear red and need to be updated.

8 Right-click on the Backup UEA, and select Load Version.

Choose the Load Version option if you want to select the

firmware that is installed as part of the Experion software
installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The Select Firmware Version dialog box appears.

9 Click on the Firmware Version (for example, EXP501.1-

17.0), and then click Show Personality.
RESULT: The available UEA personalities are listed.

446
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

NOTE: Actual version may be different, refer to the

Experion PKS Software Change Notice associated
with the release for information on the latest
firmware version

Load the Boot/Recovery personality image

NOTE: Skip to Step 13 if the Boot/Recovery image does not need

to be updated – that is, its version status is green, indicating that
it is the most recent version.

10 Select the UEARECOVERY personality image.

11 Click Select.
RESULT: The Select Firmware Version dialog box closes.

12 Click Load Firmware.

RESULT: The firmware loads and then the UEA reboots to
the Alive state. Note that the firmware upgrade process
takes 3-5 minutes to complete.

Load the Application personality image

13 Right-click on the Backup UEA (for example, UEA with a

Device Index of 98), and select Load Version.

Choose the Load Version option if you want to select the

firmware that is installed as part of the Experion software

447
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The Select Firmware Version dialog box appears.

14 Click on the Firmware Version (for example, EXP501.1-

14.0), and then click Show Personality.
RESULT: The available UEA personalities are listed.

NOTE: Actual version may be different, refer to the

Experion PKS Software Change Notice associated
with the release for information on the latest
firmware version

15 Select the personality image to be loaded.

For the ELCN Bridge, select UEAELCN_BRG.

16 Click Select.
RESULT: The Select Firmware Version dialog box closes.

17 Click Load Firmware.

RESULT: The firmware loads and then the secondary UEA
reboots, synchronizes with its primary, and then goes to
the BACKUP state. Note that the firmware upgrade
process takes 3-5 minutes to complete. The version of
each personality image is green, indicating that it is the
most recent version available.

448
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Verify that the firmware of the BACKUP UEA has been updated

18 After updating firmware, use any of the following methods

to verify that the firmware of the Backup UEA has been
updated to the expected version:
Physical UEA front panel display: Select the DETAILS
option to view the firmware version.
Firmware Manager tool: Shows the updated firmware
version in green color, indicating that it is the most recent
version available.
Control Builder: In the Monitoring side of the ELCN
Bridge platform block, the Main tab shows the firmware
version, as shown in the following example.

Initiate a Switchover and load firmware to the new Backup UEA

19 Wait for 3 minutes and then from the Monitoring side of

the Backup ELCN Bridge platform block in Control
Builder, select the Redundancy tab.

20 Before performing the next step, make sure that the icons
for both primary and secondary ELCN Bridges in the
Control Builder Monitoring side are displayed in green
color.

21 Select the Initiate Switchover command.

RESULT: The updated Backup UEA becomes the new
primary and goes to the OK state. For R501.1, R501.2 and
R501.4, the previous primary reboots and becomes the
new backup in the BACKUP state.
Wait for 2 minutes for the new primary/backup to go to
OK/BACKUP states. For R510, note that the new backup

449
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

UEA hardware/Control Builder will display the node state

as ConfigWait. Wait for 3 minutes before proceeding to
the next step.

Shut down the ELCN Bridge platform block of the new Backup UEA in Control
Builder

22 On the Monitoring side of the new backup ELCN Bridge

platform block in Control Builder, choose “Shutdown”
from the “Module Command” dropdown on the Main tab.

23 After you select the “Shutdown” command , a

confirmation dialog is displayed.
Click Yes to proceed with the Shutdown.
RESULT: For R501.1, R501.2 and R501.4, the new backup
UEA reboots and goes from the BACKUP to READY state,
as can be seen at the physical UEA’s front panel display.
For R510, the new backup UEA reboots and goes from
ConfigWait to READY state, as can be seen on the
physical UEA’s front panel display. The values on the
Detail Display show reverse video, because the Shutdown
removed the ELCN Bridge platform block from the UEA.
For R510, Native Window will display node state as ISOL
and UEA hardware/Control Builder will display node state
as READY.

NOTE: For R501.x, R51x and later, if the UEA is in

the OK or BACKUP state when you attempt
firmware loading, the Firmware Manager tool will
not flash the firmware and will return an error
indicating that the “Module is On Control”.

Open the Firmware Manager tool and select node to be loaded

24 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 the FTE IP address and FTE Device Index of
each UEA.

450
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

The color of the Boot/Recovery and Application fields

indicates whether or not a more recent version of the
firmware is available.
Version status of UEA firmware images (Boot/Recovery
and Application):
green – version supported and latest
blue – version supported but not latest
red – version not supported

25 Select the checkbox for the new backup in the READY

state (Name = primary tagname).

Use the color coding to determine which firmware images

need to be updated for the selected UEA.
UEA with a Device Index of 97, which is running as the
Backup ELCN Bridge is selected in the following example.
Both of its firmware images (Boot/Recovery and
Application) appear red and need to be updated.

26 Right-click on the secondary UEA, and select Load

Version.

Choose the Load Version option if you want to select the

firmware that is installed as part of the Experion software
installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The Select Firmware Version dialog box appears.

451
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

27 Click on the Firmware Version (for example, EXP501.1-

39.18), and then click Show Personality. RESULT: The
available UEA personalities are listed.

NOTE: Actual version may be different, refer to the

Experion PKS Software Change Notice associated
with the release for information on the latest
firmware version

Load Boot/Recovery personality image

NOTE: Skip to Step 31 if the Boot/Recovery image does not need to be

updated – that is, its version status is green, indicating that it is the most
recent version.

28 Select the UEARECOVERY personality image.

29 Click Select.
RESULT: The Select Firmware Version dialog box closes.

30 Click Load Firmware.

RESULT: The firmware loads and then the UEA reboots to
the Alive state. Note that the firmware upgrade process
takes 3-5 minutes to complete.

Load Application personality image

31 Right-click on the Backup UEA (for example, UEA with a

Device Index of 97), and select Load Version.

452
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Choose the Load Version option if you want to select the

firmware that is installed as part of the Experion software
installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The Select Firmware Version dialog box appears.

32 Click on the Firmware Version (for example, EXP501.1-

39.101), and then click Show Personality.
RESULT: The available UEA personalities are listed.

NOTE: Actual version may be different, refer to the

Experion PKS Software Change Notice associated
with the release for information on the latest
firmware version

33 Select the personality image to be loaded.

For the ELCN Bridge, select UEAELCN_BRG.

34 Click Select.
RESULT: The Select Firmware Version dialog box closes.

35 Click Load Firmware.

RESULT: The firmware loads and then the Backup UEA
reboots, synchronizes with its primary, and then goes to

453
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

the BACKUP state. Note that the firmware upgrade

process takes 3-5 minutes to complete. The version of
each personality image is green, indicating that it is the
most recent version available.

Verify that firmware of Backup UEA has been updated

36 After updating firmware, use any of the following methods

to verify that the firmware of the Backup UEA has been
updated to the expected version:
Physical UEA front panel display: Select the DETAILS
option to view the firmware version.
Firmware Manager tool: Shows the updated firmware
version in green color, indicating that it is the most recent
version available.
Control Builder: In the Monitoring side of the ELCN
Bridge platform block, the Main tab shows the firmware
version.
RESULT: The firmware has been updated on both of the
redundant UEAs. The procedure is complete.

Overview of Firmware Update for Non-Redundant

ELCN Appliance Node
The firmware loading for an operational, non-redundant ELCN
Appliance Node is summarized as follows:
Prior to loading firmware
n In the Native Window*, shut down the node to place it in the
QUALIF state.
n From the ELCN Node platform block Monitoring side in
Control Builder, select Shut Down to take the UEA from
QUALIF to READY.
Firmware loading
n Use the Firmware Manager tool to load the firmware on the
node.

454
Chapter 10 - Servicing and Troubleshooting Experion LCN

After loading firmware

n Load the ELCN Node platform block from the Project side in
Control Builder.
n In the Native Window*, load the LCN personality/checkpoint
files to the node from the History Module.
REFERENCE: For the detailed procedure, see “To Update
Firmware on Operational Non-Redundant ELCN Appliance
Nodes”

Overview of Firmware Update for Redundant ELCN

Appliance Node
The firmware loading for an operational redundant ELCN
Appliance Node is summarized as follows:
Prior to loading firmware
n Ensure that the UEA with the even-numbered Device Index
is operating as the Backup ELCN Node.
l If this is the case, then in the Native Window*, shut down

the secondary to place it in the QUALIF state.

l If this is not the case, then in Native Window*, shut down

the current primary to make it the secondary in the PWR_

ON state.
n From the Monitoring side of the secondary ELCN Node
platform block in Control Builder, select Shut Down to take
the UEA from PWR_ON/QUALIF to READY state.
Firmware loading
n Use the Firmware Manager tool to load the firmware on the
secondary.
n After the firmware upgrade, the secondary (backup) is in the
PWR_ON state. In the Native Window*, load the backup
node. Wait for 7 minutes after loading the backup node,
then shut down the current primary to make it the new
secondary (backup).
n In Control Builder, from the Monitoring side of the new
secondary ELCN Node platform block (that is, the primary
that has just become the secondary), select the Shut Down

455
 Chapter 10 - Servicing and Troubleshooting Experion LCN

command to take the new secondary from PWR_ON to

READY state.
n Load the firmware on the new secondary, then wait for it to
come to the PWR_ON state.
n In the Native Window*, load the new secondary node, then
wait for it to come to the BACKUP state.
n Wait for 7 minutes after the new secondary node transitions
to the BACKUP state.
n If you want to have the node with the odd-numbered Device
Index be the primary, then in the Native Window*, shut down
the primary to cause a switchover.
* Instead of using the System Status Display on the Experion
Native Window, you can use a US/GUS.
REFERENCE: For the detailed procedure, see “"To Update
Firmware on Operational Non-Redundant ELCN Appliance
Nodes" on page 459
The following tables show the node state changes that occur
during the firmware loading procedure for an operational,
redundant ELCN Node.

Node States for BACKUP (even-numbered Device

Index) ELCN Node
This table shows the node states when performing actions on
the BACKUP (even-numbered Device Index) ELCN Node:

Primary ELCN Node BACKUP ELCN Node

This Action… Causes this state to occur…

TPN Node UEA State TPN Node UEA State

State State

<initial state> OK OK<odd- BACKUP BACKUP<even-

numbered numbered Device
Device Index> Index>

Shut down WARN WARN QUALIF QUALIF

Secondary

456
Chapter 10 - Servicing and Troubleshooting Experion LCN

Primary ELCN Node BACKUP ELCN Node

node in
Native
Window

Shut down WARN WARN-No ISOL

R
This Action… Secondary Sync E
platform A
block D
using Y
Control
Builder
Module
Command

Load Firmware WARN WARN ISOL NOT LOADED

Load WARN WARN PWR_ON PWR_ON

Secondary
platform block
in Control
Builder

Load OK OK BACKUP BACKUP

Secondary
node in Native
Window

Node states for BACKUP (odd-numbered Device

Index) ELCN Node
This table shows the node states when performing actions on
the PRIMARY (odd-numbered Device Index) ELCN Node.

This Action… Primary ELCN Node BACKUP ELCN Node

Causes this state to occur…

TPN Node UEA State TPN Node UEA State

State State

Shut down WARN WARN<even- PWR_ON PWR_ON

Primary numbered
node in device index> (New (New BACKUP -
Native BACKUP - previous

457
 Chapter 10 - Servicing and Troubleshooting Experion LCN

This Action… Primary ELCN Node BACKUP ELCN Node

Window to previous primary)<odd-

cause primary) numbered device
switchover index>

Shut down WARN WARN-No ISOL READY

Secondary Sync
platform
block using
Control
Builder
Module
Command

Load WARN WARN ISOL NOT LOADED

Firmware

Load WARN WARN PWR_ON PWR_ON

Secondary
platform
block in
Control
Builder

Load OK OK BACKUP BACKUP

Secondary
node in
Native
Window

Shut down WARN WARN PWR_ON PWR_ON(original

Primary secondary)<even-
node in numbered device
Native index>
Window to
cause
switchover

Load OK OK BACKUP BACKUP

Secondary
node in
Native
Window

458
Chapter 10 - Servicing and Troubleshooting Experion LCN

To Update Firmware on Operational Non-Redundant

ELCN Appliance Nodes

Step Action Done

Checkpoint the node from Native Window

1 From the Native Window System Status Display, select

the AM you want to checkpoint, and then select the
SAVE SELECT target and press Enter. Save the
checkpoint to NET.

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

2 From the ES-T Native Window (or on a US/GUS), call

up the System Status Display.
1. Select the node of interest.
2. Select the SHUT DOWN command to cause the
node to go to the QUALIF state.
RESULT: The node goes to the QUALIF state.

Shut down the UEA to place it in the Ready state

3 Wait for 3 minutes and then from Control Builder, go

to the Monitoring side of ELCN Node platform block.

4 Select Shutdown from the “Module command”

dropdown on the Main tab. A confirmation dialog is
displayed. Click Yes to proceed with the Shutdown.
RESULT: The UEA reboots and goes from QUALIF to
READY state, as can be seen on the physical UEA’s
front panel display. The values on the Detail Display
show reverse video.
Native Window will display node state as ISOL and
UEA hardware/Control Builder will display node state
as READY.

NOTE: If the UEA is in the OK state when you

attempt firmware loading, the Firmware
Manager tool will not flash the firmware and will
return an error indicating that the “Module is
On Control”.

Shutdown the node from Native Window for the second time to place it in the OFF

459
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

state

5 Shutdown the node from the Native Window for the

second time to transition from the ISOL state to the
OFF state while the UEA is rebooting.

Open the Firmware Manager tool and select node to be loaded

6 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 the FTE IP address and FTE
Device Index of each UEA.
The color of the Boot/Recovery and Application fields
indicates whether or not a more recent version of the
firmware is available.
Version status of UEA firmware images
(Boot/Recovery and Application):
green – version supported and latest
blue – version supported but not latest
red – version not supported

7
Select the checkbox for the node in the OFF state.
Using the color coding, determine which personality
images (Boot Recovery and/or Application) need to be
updated for the selected UEA.

8 Right-click on the UEA, and select Load Version.

Choose the Load Version option if you want to select

the firmware that is installed as part of the Experion

460
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

software installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The Select Firmware Version dialog box
appears.

9 Click on the Firmware Version (for example,

EXP501.1-39.18), and then click Show Personality.
RESULT: The available UEA personalities are listed.

NOTE: Actual version may be different, refer to

the Experion PKS Software Change Notice
associated with the release for information on
the latest firmware version

Load Boot/Recovery personality image

NOTE: Skip to Step 13 if the Boot/Recovery image does not need

to be updated – that is, its version status is green, indicating that
it is the most recent version.

10 Select the UEARECOVERY personality image.

11 Click Select.
RESULT: The Select Firmware Version dialog box
closes.

12 Click Load Firmware.

RESULT: The firmware loads and then the UEA reboots
to the NOT LOADED state. Note that the firmware
upgrade process takes 3-5 minutes to complete.

461
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Load Application personality image

13 Right-click on the secondary UEA, and select Load

Version.

Choose the Load Version option if you want to select

the firmware that is installed as part of the Experion
software installation.
Choose the Load File option if you want to select the
firmware from custom locations where you would have
copied the firmware manually.
RESULT: The “Select Firmware Version” dialog box
appears.

14 Click on the Firmware Version (for example,

EXP501.1-39.101), and then click Show Personality.
RESULT: The available UEA personalities are listed.

NOTE: Actual version may be different, refer to

the Experion PKS Software Change Notice
associated with the release for information on
the latest firmware version

15 Select UEAELCN_NODE as the personality image to

be loaded.

16 Click Select.

462
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

RESULT: The “Select Firmware Version” dialog box

closes.

17 Click Load Firmware.

RESULT: The firmware loads and then the UEA reboots
to the PWR_ON state. Note that the firmware upgrade
process takes 3-5 minutes to complete.

Verify that firmware of UEA has been updated

18 After updating firmware, use any of the following

methods to verify that the firmware of the UEA has
been updated to the expected version:
Physical UEA front panel display: Select the DETAILS
option to view the 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 side of the ELCN
Node platform block, the Main tab shows the
Application Image Version.

Load the LCN-side of the UEA

19 Make sure that the LCN-side of the UEA is in the

PWR_ON state and then from the LCN System Status
Display in the ES-T Native Window or on a US/GUS,
select the node of interest, and then select the LOAD
SELECT command, and complete the load.
RESULT: The LCN-side of the node goes from PWR_
ON to OK state. The procedure is complete.

To Update Firmware on Operational Redundant ELCN

Appliance Nodes

Step Action Done

Checkpoint the node from Native Window

1 From the Native Window System Status Display,

select the ENIM you want to checkpoint, and

463
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

then select the SAVE SELECT target and press

Enter. Save the checkpoint to NET.

2 Go to either of the following displays to view the

Device Index of the Backup UEA:
Experion Node Detail Display:
Open the Station application.
From the top menu bar, click View>System
Status Display.
In the Location Pane, under “Gateways”
category, navigate to and double-click on the
secondary - <nodename>SEC.
Monitoring side of platform block in Control
Builder:
In Control Builder, double-click on the
secondary ELCN Node platform block -
<nodename>SEC

Ensure that the UEA with the even-numbered Device Index is operating as the
Backup ELCN Node

3 Check that the UEA with the even-numbered

Device Index is the Backup ELCN Node.
If the BACKUP has the even-numbered Device
Index, do the following:

1. From the ES-T Native Window (or on a

US/GUS), call up the System Status Display.
2. Display the Node Status Display for the node
type of interest.
3. Select the BACKUP node of interest.
4. Select the SHUT DOWN command to cause
the Backup ELCN Node to go to the QUALIF
state.
If the BACKUP does NOT have the even-
numbered Device Index, then do the following
to cause a switchover to occur:

464
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

1. From the ES-T Native Window (or on a

US/GUS), call up the System Status Display.
2. Display the Node Status Display for the node
type of interest.
3. Select the primary node of interest.
4. Select the SHUT DOWN command to cause a
switchover to occur.
5. The Backup ELCN Node takes over the
Primary role and transitions to WARN state.
6. The new Backup ELCN Node (the previous
primary) reboots and transitions to PWR_ON
state.
RESULT: The UEA with the even-numbered
Device Index is now the Backup ELCN Node in
the PWR_ON state.

Shut down the secondary UEA to place it in the Ready state

4 Wait for 3 minutes and then go to the

Monitoring side of the secondary (Backup)
ELCN Node platform block in Control Builder.

5 Select Shutdown from the “Module command”

dropdown on the Main tab.A confirmation
dialog is displayed. Click Yes to proceed with
the Shutdown.
RESULT: The secondary UEA reboots and goes
from PWR_ON/QUALIF to READY state, as can
be seen on the physical UEA’s front panel
display. The values on the Detail Display show
reverse video.
Native Window will display node state as ISOL
and UEA hardware/Control Builder will display
node state as READY.

NOTE: If the UEA is in the OK or BACKUP

state when you attempt firmware loading,
the Firmware Manager tool will not flash
the firmware and will return an error
indicating that the “Module is On

465
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Control”.

Shutdown the secondary node from Native Window for the second time to place it in
the OFF state

6 Shutdown the secondary node from the Native

Window for the second time to transition from
the ISOL state to the OFF state while the UEA is
rebooting. The UEA hardware will still display
node state as READY.

Open the Firmware Manager tool and select node to be loaded

7 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 the FTE IP address
and FTE Device Index of each UEA.
The color of the Boot/Recovery and Application
fields indicates whether or not a more recent
version of the firmware is available.
Version status of UEA firmware images
(Boot/Recovery and Application):
green – version supported and latest
blue – version supported but not latest
red – version not supported

8
Select the checkbox for the secondary in the
READY state (Name = primary tagnameSEC).
Using the color coding, determine which
personality images (Boot Recovery and/or
Application) need to be updated for the
selected UEA.

466
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

9 Right-click on the secondary UEA, and select

Load Version.

Choose the Load Version option if you want to

select the firmware that is installed as part of
the Experion software installation.
Choose the Load File option if you want to
select the firmware from custom locations
where you would have copied the firmware
manually.
RESULT: The Select Firmware Version dialog
box appears.

10 Click on the Firmware Version (for example,

EXP501.1-17.0), and then click Show
Personality.RESULT: The available UEA
personalities are listed.

NOTE: Actual version may be different,

refer to the Experion PKS Software
Change Notice associated with the
release for information on the latest
firmware version

Load Boot/Recovery personality image

467
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

NOTE: Skip to Step 14 if the Boot/Recovery image does not

need to be updated – that is, its version status is green,
indicating that it is the most recent version.

11 Select the UEARECOVERY personality image.

12 Click Select.
RESULT: The Select Firmware Version dialog
box closes.

13 Click Load Firmware.

RESULT: The firmware loads and then the UEA
reboots to the NOT LOADED state. Note that
the firmware upgrade process takes 3-5
minutes to complete.

Load Application personality image

14 Right-click on the secondary UEA, and select

Load Version.

Choose the Load Version option if you want to

select the firmware that is installed as part of
the Experion software installation.
Choose the Load File option if you want to
select the firmware from custom locations
where you would have copied the firmware
manually.
RESULT: The “Select Firmware Version” dialog
box appears.

15 Click on the Firmware Version (for example,

EXP501.1-14.0), and then click Show
Personality.

468
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

RESULT: The available UEA personalities are

listed.

NOTE: Actual version may be different,

refer to the Experion PKS Software
Change Notice associated with the
release for information on the latest
firmware version

16 Select UEAELCN_NODE as the personality

image to be loaded.

17 Click Select.
RESULT: The “Select Firmware Version” dialog
box closes.

18 Click Load Firmware.

RESULT: The firmware loads and then the
secondary UEA reboots to the BACKUP state.
Note that the firmware upgrade process takes
3-5 minutes to complete. The version of each
personality image is green, indicating that it is
the most recent version available. Native
Window will display the node state as PWR_ON.

Verify that firmware of Backup UEA has been updated

19 After updating firmware, use any of the

following methods to verify that the firmware of
the Backup UEA has been updated to the
expected version:

469
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Physical UEA front panel display: Select the

DETAILS option to view the 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 side of the
ELCN Node platform block, the Main tab shows
the Application Image Version.

Load the LCN-side of the Backup UEA

20 Make sure that the LCN-side of the UEA is in

the PWR_ON state and then from the LCN
System Status Display in the ES-T Native
Window or on a US/GUS, select the Backup
ELCN Node of interest, and then select the
LOAD SELECT command, and complete the
load.
RESULT: Wait for 7 minutes for the LCN-side of
the Backup ELCN Node to go from PWR_ON to
BACKUP state and the LCN-side of the Primary
ELCN Node to go from WARN to OK state. The
update of the Backup UEA is complete.

Shut down the Primary node in the Native Window

21 From the ES-T Native Window (or on a

US/GUS), call up the System Status Display
and do the following:

1. Display the Node Status Display for the node

type of interest.
2. Select the primary node of interest.
3. Select the SHUT DOWN command.
RESULT: A switchover occurs. The current
Backup ELCN Node takes over the Primary role
and transitions to the WARN state. For R501.1,
R501.2 and R501.4, the current Primary ELCN
Node transitions to the PWR_ON state. For
R510, the current Primary ELCN Node
transitions to the ConfigWait state (as seen on

470
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

the UEA hardware/Control Builder/Station

Display).

Shut down the ELCN Node platform block of the new Backup UEA in Control Builder

22 Wait for 3 minutes and then from the

Monitoring side of Control Builder, select the
new Backup ELCN Node platform block, then
select Shutdown from the “Module command”
dropdown on the Main tab.A confirmation
dialog is displayed. Click Yes to proceed with
the Shutdown.
RESULT: For R501.1, R501.2 and R501.4, the
new secondary UEA reboots and goes from
PWR_ON to READY state, as can be seen on the
physical UEA’s front panel display. For R510,
the new secondary UEA reboots and goes from
ConfigWait to READY state, as can be seen on
the physical UEA’s front panel display. The
values on the Detail Display show reverse video.
Native Window will display the node state as
ISOL and UEA hardware/Control Builder will
display node state as READY.

NOTE: If the UEA is in the OK or BACKUP

state when you attempt firmware loading,
the Firmware Manager tool will not flash
the firmware and will return an error
indicating that the “Module is On
Control”.

Shutdown the new backup node from Native Window for the second time to place it
in the OFF state

23 Shutdown the new backup node from the

Native Window for the second time to transition
from the ISOL state to the OFF state while the
UEA is rebooting. The UEA hardware will still
display node state as READY.

Open the Firmware Manager tool and select node to be loaded

471
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

24 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 the FTE IP address
and FTE Device Index of each UEA.
The color of the Boot/Recovery and Application
fields indicates whether or not a more recent
version of the firmware is available.
Version status of UEA firmware images
(Boot/Recovery and Application):
green – version supported and latest
blue – version supported but not latest
red – version not supported

25
Select the checkbox for the node in the
READY state.
Using the color coding, determine which
personality images (Boot Recovery and/or
Application) need to be updated for the
selected UEA.

26 Right-click on the UEA, and select Load

Version.

Choose the Load Version option if you want to

select the firmware that is installed as part of
the Experion software installation.
Choose the Load File option if you want to
select the firmware from custom locations

472
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

where you would have copied the firmware

manually.
RESULT: The Select Firmware Version dialog
box appears.

27 Click on the Firmware Version (for example,

EXP501.1-39.18), and then click Show
Personality. RESULT: The available UEA
personalities are listed.

NOTE: Actual version may be different,

refer to the Experion PKS Software
Change Notice associated with the
release for information on the latest
firmware version

Load Boot/Recovery personality image

NOTE: Skip to Step 31 if the Boot/Recovery image does not need to be

updated – that is, its version status is green, indicating that it is the most
recent version.

28 Select the UEARECOVERY personality image.

29 Click Select.
RESULT: The Select Firmware Version dialog
box closes.

30 Click Load Firmware.

RESULT: The firmware loads and then the UEA
reboots to the NOT LOADED state.
Note that the firmware upgrade process takes
3-5 minutes to complete.

473
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

Load Application personality image

31 Right-click on the secondary UEA, and select

Load Version.

Choose the Load Version option if you want to

select the firmware that is installed as part of
the Experion software installation.
Choose the Load File option if you want to
select the firmware from custom locations
where you would have copied the firmware
manually.
RESULT: The “Select Firmware Version” dialog
box appears.

32 Click on the Firmware Version (for example,

EXP501.1-39.101), and then click Show
Personality.
RESULT: The available UEA personalities are
listed.

NOTE: Actual version may be different,

refer to the Experion PKS Software
Change Notice associated with the
release for information on the latest
firmware version

33 Select UEAELCN_NODE as the personality

image to be loaded.

474
Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

34 Click Select.
RESULT: The “Select Firmware Version” dialog
box closes.

35 Click Load Firmware.

RESULT: The firmware loads and then the UEA
reboots to the BACKUP state. Note that the
firmware upgrade process takes 3-5 minutes to
complete.

Verify that firmware of UEA has been updated

36 After updating firmware, use any of the

following methods to verify that the firmware of
the UEA has been updated to the expected
version:
Physical UEA front panel display: Select the
DETAILS option to view the 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 side of the
ELCN Node platform block, the Main tab shows
the Application Image Version.
RESULT: The firmware has been updated on
both of the redundant UEAs.

Load the LCN-side of the new Backup UEA

37 Make sure that the LCN-side of the UEA is in

the PWR_ON state and then from the LCN
System Status Display in the ES-T Native
Window or on a US/GUS, select the node of
interest, and then select the LOAD SELECT
command, and complete the load.
RESULT: The LCN-side of the ELCN node goes
from PWR_ON to BACKUP state. The procedure

475
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Step Action Done

is complete.

Cause a Switchover so the Backup UEA has the even-numbered Device Index
(optional, this is only necessary if you desire to obtain your preferred odd
number/primary ELCN-ENIM and even number/secondary ELCN-ENIM node
order).

38 Wait for 7 minutes and then from the ES-T

Native Window (or on a US/GUS), call up the
System Status Display and do the following:
1. Display the Node Status Display for the node
type of interest.
2. Select the primary node of interest.
3. Select the SHUT DOWN command.
RESULT: A switchover occurs. The current
Backup ELCN Node takes over the Primary role
and transitions to the WARN state. The current
Primary ELCN Node transitions to the PWR_ON
state.

Load the LCN-side of the new Backup UEA

39 Make sure that the LCN-side of the Backup

UEA is in the PWR_ON state and then from the
LCN System Status Display in the ES-T Native
Window or on a US/GUS, select the Backup
ELCN Node of interest, and then select the
LOAD SELECT command, and complete the
load.
RESULT: Wait for 7 minutes for the LCN-side of
the Backup ELCN Node to go from PWR_ON to
BACKUP state and the LCN-side of the Primary
ELCN Node to go from WARN to OK state. The
Backup UEA has the even-numbered Device
Index.
The procedure is complete.

476
Chapter 10 - Servicing and Troubleshooting Experion LCN

Backward Migration to Prior Experion Release

ATTENTION: If a factory reset is performed on the UEA

ELCN Node and Experion R530.1 firmware is flashed
onto this UEA node (or) Experion R530.1 firmware is
flashed onto a brand new UEA node from factory (and)
this UEA ELCN node is used as a redundant partner in a
redundant ELCN Node pair, on process backward
migration of this ELCN node pair to a prior Experion
release is not supported.

If a UEA ELCN node is migrated from a prior Experion release

to R530.1 firmware and factory reset is NOT done on the UEA
node, then on process backward migration to the prior release
of Experion is supported with the following modification.
1. Update the Boot/Recovery image to UEA_110.1-07.0 on the
backup node.
2. Update the Application personality image that is compatible
with the Boot/Recovery image on the backup node.
3. Ensure that the backup node synchronizes with the primary.
4. Wait for 5 minutes and perform a node failover.
5. Update the Boot/Recovery image to UEA_110.1-07.0 on the
old primary node (new backup). ·
6. Update the Application personality image that is compatible
with the Boot/Recovery image on the old primary node (new
backup).

NOTE: For off-process migration or new UEA board freshly

installed with R530.1 (or later), a backward on-process
migration is NOT possible and will prevent the nodes from
synchronizing.

Checking Microsoft Windows application event

logs for errors
In the case of RPC, Named Pipe, and shared memory failures,
there may be ELCN Experion TPS Node operational issues,
check the windows application event log for the errors and
troubleshoot them. You may have to reload the respective node
to resolve the following errors.

477
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Error Code Description

2 (0x2) - ERROR_FILE_NOT_FOUND The system cannot find the file

specified.

3 (0x3) - ERROR_PATH_NOT_FOUND The system cannot find the path

specified.

5 (0x5) - RROR_ACCESS_DENIED Access is denied.

6 (0x6) - ERROR_INVALID_HANDLE The handle is invalid.

193 (0xC1) - ERROR_BAD_EXE_FORMAT %1 is not a valid Win32 application

229 (0xE5) - ERROR_PIPE_LOCAL The pipe is local.

230 (0xE6) - ERROR_BAD_PIPE The pipe state is invalid.

231 (0xE7) - ERROR_PIPE_BUSY All pipe instances are busy.

232 (0xE8) - ERROR_NO_DATA The pipe is being closed.

233 (0xE9) - ERROR_PIPE_NOT_ No process is on the other end of the

CONNECTED pipe.

234 (0xEA) - ERROR_MORE_DATA More data is available.

535 (0x217) - ERROR_PIPE_CONNECTED There is a process on other end of

the pipe.

536 (0x218) - ERROR_PIPE_LISTENING Waiting for a process to open the

other end of the pipe.

574 (0x23E) - ERROR_UNHANDLED_ {Application Error} The exception %s

EXCEPTION (0x%08lx) occurred in the
application at location 0x%08lx.

1064 (0x428) - ERROR_EXCEPTION_IN_ An exception occurred in the service

SERVICE when handling the control request

1067 (0x42B) - ERROR_PROCESS_ The process terminated

ABORTED unexpectedly.

1068 (0x42C) - ERROR_SERVICE_ The dependency service or group

DEPENDENCY_FAIL failed to start.

1069 (0x42D) - ERROR_SERVICE_LOGON_ The service did not start due to a

FAILED logon failure.

478
Chapter 10 - Servicing and Troubleshooting Experion LCN

Error Code Description

1070 (0x42E) - ERROR_SERVICE_START_ After starting, the service hung in a

HANG start-pending state.

1242 (0x4DA) - ERROR_ALREADY_ The service is already registered.

REGISTERED

1243 (0x4DB) - ERROR_SERVICE_NOT_ The specified service does not exist.

FOUND

1700 (0x6A4) - RPC_S_INVALID_STRING_ The string binding is invalid.

BINDING

1701 (0x6A5) - RPC_S_WRONG_KIND_OF_ The binding handle is not the correct

BINDING type.

1702 (0x6A6) -RPC_S_INVALID_BINDING The binding handle is invalid.

1703 (0x6A7) - RPC_S_PROTSEQ_NOT_ The RPC protocol sequence is not

SUPPORTED supported.

1704 (0x6A8) -RPC_S_INVALID_RPC_ The RPC protocol sequence is invalid.

PROTSEQ

1705 (0x6A9) - RPC_S_INVALID_STRING_ The string universal unique identifier

UUID (UUID) is invalid.

1706 (0x6AA) - RPC_S_INVALID_ The endpoint format is invalid.

ENDPOINT_FORMAT

1707 (0x6AB) - RPC_S_INVALID_NET_ADDR The network address is invalid.

1708 (0x6AC) - RPC_S_NO_ENDPOINT_ No endpoint was found.

FOUND

1709 (0x6AD) - RPC_S_INVALID_TIMEOUT The timeout value is invalid.

1710 (0x6AE) - RPC_S_OBJECT_NOT_ The object universal unique identifier

FOUND (UUID) was not found.

1711 (0x6AF) - RPC_S_ALREADY_ The object universal unique identifier

REGISTERED (UUID) has already been registered.

1712 (0x6B0) - RPC_S_TYPE_ALREADY_ The type universal unique identifier

REGISTERED (UUID) has already been registered.

1713 (0x6B1) - RPC_S_ALREADY_ The RPC server is already listening.

LISTENING

479
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Error Code Description

1714 (0x6B2) - RPC_S_NO_PROTSEQS_ No protocol sequences have been

REGISTERED registered.

1715 (0x6B3) - RPC_S_NOT_LISTENING The RPC server is not listening.

1717 (0x6B5) - RPC_S_UNKNOWN_IF The interface is unknown.

1718 (0x6B6) - RPC_S_NO_BINDINGS There are no bindings.

1719 (0x6B7) - RPC_S_NO_PROTSEQS There are no protocol sequences.

1721 (0x6B9) - RPC_S_OUT_OF_ Not enough resources are available

RESOURCES to complete this operation.

1722 (0x6BA) - RPC_S_SERVER_ The RPC server is unavailable.

UNAVAILABLE

1723 (0x6BB) - RPC_S_SERVER_TOO_BUSY The RPC server is too busy to

complete this operation.

1725 (0x6BD) - RPC_S_NO_CALL_ACTIVE There are no remote procedure calls

active on this thread.

1726 (0x6BE) - RPC_S_CALL_FAILED The remote procedure call failed.

1727 (0x6BF) - RPC_S_CALL_FAILED_DNE The remote procedure call failed and

did not execute.

1728 (0x6C0) - RPC_S_PROTOCOL_ERROR A remote procedure call (RPC)

protocol error occurred.

1729 (0x6C1) - RPC_S_PROXY_ACCESS_ Access to the HTTP proxy is denied.

DENIED

1741 (0x6CD) - RPC_S_UNKNOWN_AUTHN_ The authentication type is unknown.

TYPE

1759 (0x6DF) - RPC_S_INTERFACE_NOT_ The interface was not found.

FOUND

1760 (0x6E0) - RPC_S_ENTRY_ALREADY_ The entry already exists.

EXISTS

1761 (0x6E1) - RPC_S_ENTRY_NOT_FOUND The entry is not found.

1762 (0x6E2) - RPC_S_NAME_SERVICE_ The name service is unavailable.

UNAVAILABLE

480
Chapter 10 - Servicing and Troubleshooting Experion LCN

Error Code Description

1764 (0x6E4) - RPC_S_CANNOT_SUPPORT The requested operation is not

supported.

1766 (0x6E6) - RPC_S_INTERNAL_ERROR An internal error occurred in a remote

procedure call (RPC).

Capturing Failure Status for Honeywell

Technical Assistance Center Analysis
When an ELCN Bridge or ELCN Node failure occurs, gather
information about the failure and the conditions under which it
occurred. This information helps the Honeywell Technical
Assistance Center (TAC) diagnose and correct the problem.
Use the following list to obtain information, so that when you
contact Honeywell TAC, you can provide a complete description
of the problem.

Obtain this Information…

State shown on the faceplate of the Experion

Detail display

Experion System release number

Hardware and Firmware Versions shown in the

Hardware Information tab in the Project side
of the Control Builder block (if the UEA can
still communicate with Control Builder):

Hardware revision of the UEA

Firmware revision of Boot/Recovery image,

also known as the factory (FACT) image.

Firmware revision of Application image

TPN release number

Upload UEA diagnostic information using the

Firmware Manager Tool’s Diagnostic Capture
feature. It retrieves a zipped file that you can
send to Honeywell TAC.

481
 Chapter 10 - Servicing and Troubleshooting Experion LCN

ATTENTION: In the case of an

unexpected ELCN Bridge switch over,
capture UEA diagnostic information
from both primary and secondary nodes
using the Firmware Manager Tool’s
Diagnostic Capture feature and then
send to Honeywell TAC for further
analysis.

REFERENCE: For details, refer to the

Firmware Manager User’s Guide.
If an ELCN Node changes state to FAIL an
automatic dump process is initiated by the
device. The result of this dump process is
different to that of the manual dump that is
initiated from Native Window or Universal
Station, such that the dump file is stored in
the device’s flash memory versus being stored
on the History Module. The dump files can be
retrieved from the device at the time of failure
or after a reboot using Firmware Manager,
following the procedure for Diagnostic
Capture.

Additional Information to obtain - node conditions and sequence of events

Was the node operating in a redundant or

non-redundant hardware configuration?

If redundant, what was the redundancy state

at the time of the failure?

Any other status or fail indications on the

faceplate observed at the time of the failure or
following the event.

What were the Control Builder Monitoring view

indications at the time of the failure or
following the event?

What does the Alarm Summary show for the

time interval around the event?

Provide a detailed summary of the sequence of

482
Chapter 10 - Servicing and Troubleshooting Experion LCN

events leading up to the failure.

What operations preceded the event, such as

load, change parameter, synchronization, or
switchover?

Prior to Diagnostic Dump of Experion TPS Node

Prior to taking a memory dump of a failed TPS node, disable
the LCNP Auto Restart option (uncheck the checkbox) in the
Configuration Utility > Configure >Board0.
After the dump is completed, the node will not autoload, so you
will need to re-enable the LCNP Auto Restart option (check the
checkbox) and then the node will autoload.

Resolving data communication loss between

ELCN-EPLCGs and PLCs
Symptom
Loss of data communication between ELCN-EPLCGs and
PLCs:
n OP writes from EPLCGs to MODBUS PLCs freeze
n EPLCG DHP boxes transition to the DEV FAIL state which
means no data is read or written.
Cause
This may be due to incorrect cabling/loose termination to the
ELCN-EPLCG UEA modules, check the following cabling to the
ELCN-EPLCG UEA modules:
n FTE cables
n Port cables (PORT 1 and PORT 2)
n Configuration Jumper Cable (CONFIG JUMPER)
n Module Interlink and CEP Redundancy Cable (INTER-LINK)

NOTE: It is mandatory to connect BOTH the Primary/P1

Side of the Interlink Cable and the Primary/P1 Side of the
Configuration Jumper cable to the same UEA module, that
is, the installation may not have P1 of Interlink and P2 of

483
 Chapter 10 - Servicing and Troubleshooting Experion LCN

Configuration Jumper Cable together connected to the

same UEA module. Module redundancy will not work if the
cables are crossed.

Solution
Make sure that the ELCN-EPLCG cabling is done correctly.

Reducing load caused by ELCN System

Management Dashboard on LCN data owners
Symptom
Sluggish behavior of LCN data owners resulting in node
overruns and unpredictable behavior.
Cause
If the ELCN System Management Dashboard is running on an
ELCN ES-T, the Dashboard fetches some predefined system
parameters from all LCN/ELCN nodes in the network, this may
put additional load on the LCN data owners, such as, ENIM,
HG, AM.
Solution
If you do not want to put this additional load caused by the
ELCN System Management Dashboard of the ELCN ES-T, you
can optionally disable the ELCN System Management
Dashboard functionality of the ELCN ES-T that is putting this
additional load on the LCN data owners, see Section "Reducing
load caused by ELCN System Management Dashboard on LCN
data owners" on page 415.

ELCN Bridge
Redundancy Behaviour
The ELCN Bridge takes action, as detailed in the following
sections, and now has the primary ELCN Bridge failover to the
secondary ELCN Bridge when the Primary Bridge detects a
sustained error rate on both LCN cables. This functionality is
controlled by the parameter LCN Cable Fault State

484
Chapter 10 - Servicing and Troubleshooting Experion LCN

(LCNCBLFLTSTATE) which enables or disables the respective

bridges ability to respond to LCN Cable errors. The error rate
that the bridge responds to is defined by the LCN Error Rate
Limit (LCNERRRATELM).

NOTE: These two parameters, LCNCBLFLTSTATE and

LCNERRRATELM, are NOT synchronized between the
ELCN Bridges and must be set on both ELCN Bridges

When the primary ELCN Bridge detects 10 LCN cable errors on

the active LCN cable within a 15 second window, it forces the
active cable to another LCN cable if that cable is in good
condition, that is, the cable is connected and there are no
errors.
If the other LCN cable is detected to be bad (as mentioned
above), if the primary is synchronized, the primary initiates a
failover to the backup ELCN Bridge.
When the ELCN Bridge is not synchronized to its backup, no
failover action takes place.
The rolling average for Cables A and B is shown in control
builder forms under parameters RCVERRAAVG and
RCVERRBAVG available on the ‘ELCN Bridge Statistics’ tab. The
previous 15-second window is shown as parameters
RCVERRAMAX and RCVERRBMAX on the same tab.

These errors, when tripped, appear as a soft failure under the

‘Soft Failures’ tab, 'Sustained Errors on LCN Cable A' or
'Sustained Errors on LCN Cable B, and are also logged in the
Experion PKS events summary in addition to a system alarm
being generated.

485
 Chapter 10 - Servicing and Troubleshooting Experion LCN

When the backup ELCN Bridge detects LCN cable errors

exceeding the error rate defined by LCNERRRATELM (default
50) on the active LCN cable within a 15 second window, the
backup ELCN Bridge automatically disables synchronization.
This synchronization state on the backup ELCN Bridge will be
enabled once the error has cleared.
The sustained error condition for each LCN cable will be
cleared when there are no errors detected on the respective
LCN cable for a minimum of 2 minutes.
The LCN Error Rate Limit (LCNERRATELM) has been set to a
default value of 50, which may be high for some LCN networks,
and this value can be tuned to the network. This value is
recommended to be set at the cable threshold limit ($CBLMTP)
multiplied by the number of LCN nodes. For example, for a
given network of 20 LCN nodes, the recommended limit for
$CBLMTP is 1 or 2. LCNERRRATELM should be set between 20
– 40.
When performing LCN cable maintenance, this functionality
may need to be disabled for the duration of the maintenance.

NOTE: If the ELCN Bridges have not been synchronized for

at least 180 seconds, the above functionality has no effect.

Refer to ‘LCN Guidelines Implementation, Troubleshooting, and

Service’ and ‘Experion LCN Overview and Implementation
Guide’ for further details on troubleshooting the LCN system.

Effect of Cable operation

The following tables details the behavior of the ELCN Bridges
when LCN and/or FTE cables are disconnected from the ELCN
Bridge.

486
Chapter 10 - Servicing and Troubleshooting Experion LCN

Primary ELCN Bridge

LCN Cable LCN Cable

Result
A State B State

OK OK Normal Operation

Failed OK ELCN Bridge forces communication to

LCN Cable B

OK Failed ELCN Bridge forces communication to

LCN Cable A

Failed Failed ELCN Bridge initiates a failover to

secondary if synchronized

FTE Cable A FTE Cable B

Result
State State

OK OK Normal Operation

Failed OK ELCN Communication uses FTE cable

B

OK Failed ELCN Communication uses FTE cable

A

Failed Failed ELCN Bridge reboots and failover to

secondary occurs

Secondary ELCN Bridge

LCN Cable A LCN Cable B

Result
State State

OK OK Normal Operation

Failed OK ELCN Bridge forces communication

to LCN Cable B

OK Failed ELCN Bridge forces communication

to LCN Cable A

Failed Failed ELCN Bridge disables

synchronization

487
 Chapter 10 - Servicing and Troubleshooting Experion LCN

FTE Cable A FTE Cable B

Result
State State

OK OK Normal Operation

Failed OK ELCN Communication uses FTE

cable B

OK Failed ELCN Communication uses FTE

cable A

Failed Failed ELCN Bridge reboots

488
CHAPTER

11 DECOMMISSION/RECOMMISSION NODES

In this section:

To Decommission LCN Nodes 490

Recommissioning an LCN Node 493
To Decommission the ELCN Bridge 494
To Initialize a UEA to the Factory (FACT) Image 496

489
Chapter 11 - Decommission/Recommission Nodes

To Decommission LCN Nodes

In this context, the term “decommission” refers to how to
deactivate an original LCN coax-connected node and prepare
for its physical removal after the node has been migrated to its
ELCN equivalent. Employ a standard practice to decommission
any of your LCN coax-connected hardware, including Experion
TPS Node hardware (such as ES-Ts and ESVTs) and other LCN
node hardware, such as USs, GUSs, AMs, NIMs, and so forth.
The nodes that are supported on the ELCN are ESVT, ES-T,
ACE-T, E-APP, ENIM, AM, HM, EPLCG, and EHB.
When migrating an LCN coax-connected node to the ELCN,
perform the following steps to decommission the old hardware
of the migrated node.

Step Action Done

1 Shut down the node twice from a US or through the GUS/ES-T

Native Window, as described below:
For non-TPS and non-Experion TPS Nodes (US, AM, CLM, NG,
NIM, HG, PLCG, EPLCG, EHB), the first shutdown takes them to
QUALIF (Qualify), the second shutdown takes them to FAIL, which
is the correct state to stop token passing and prevent cable errors.
For the HM - Go to the History Module Node Status Display,
select ENB AUTO LOAD/DMP, and make sure the Current Load
State is Disable, then shut down twice.
For TPS and Experion TPS Nodes (GUS, ES-T, APP, E-APP, ESVT,
ACE-T), prior to shutdown, disable LCNP Auto Restart in the
Configuration Utility > Configure >Board 0, and then go to a
different station and shut down the specific node twice, so it goes
to the FAIL state, which is the correct state to stop token passing
and prevent cable errors.

NOTE: The following LCN nodes may remain on the coax

LCN, however, they will not be supported for direct
migration to the ELCN. Some of these nodes may upgrade
alternatives compatible with ELCN.

l PCUS,
l HG,

490
 Chapter 11 - Decommission/Recommission Nodes

Step Action Done

l CLM,
l CGs using VAX,
l NIM (must be upgraded to ENIM),
l APP,
l GUS,
l US

2 For non-TPS and non-Experion TPS Nodes (for example, ENIM,

AM, EPLCG, EHB), power down the node at the 5-slot/10-slot or
dual node chassis power supply.
For TPS and Experion TPS Nodes, in Windows close all programs
and at Start do a Shut Down, then power off the node and pull the
AC plug.
Go to a different station and select the LCN address of the node
to be decommissioned and select the specific node (showing
FAIL) and shut it down.The status will go to the OFF state.

NOTE: If the node displays the ISOLATED state, it will take

two different Native Window stations to resolve the issue:

1. Go to the first Native Window station, select the

ISOLATED node, select SHUT DOWN, and press ENTER.
2. Now go to a different Native Window station, select the
SAME node (it will show OFF), select SHUT DOWN, and
press ENTER again.

RESULT: Within two minutes, the NETWORK VIEW at the top of

the Native Window station will disappear.

3
NOTE: It is good practice to leave the BNC Tees connected
to the machine until the ELCN replacement node is fully
operational.

After the ELCN replacement node has run long enough to

determine it is fully operational as a replacement, remove the LCN
Tees from the connectors on the original node’s LCN interface
(LCN I/O or MAU).

491
Chapter 11 - Decommission/Recommission Nodes

Step Action Done

Use caution when removing the excess LCN coax cable(s) for
Cable A and B.
Make sure the CABLE SWAP configured time is sufficient to
perform this task. If the CABLE SWAP configured time is not
sufficient, please have someone select the Active cable every
minute until the replacement cable has been fully connected.
If the LCN CABLE SWAP configured time has not been
configured, it defaults to 1 minute and 57 seconds - that is the
standard LCN cable swap time.
To determine what the CABLE SWAP configured time is, do either
of the following:

1. Check the NCF Configuration:Go to the System Wide

Values>Console Data>Go to page 5 and at the TOP of the page,
it indicates the LCN CABLE SWAP INHIBIT TIME IN MINUTES.
(This specifies the length of time, in minutes, the system is to
remain on the same cable. The default value is 0 and indicates
the function is disabled.)
Or,

2. Go to the System Status display.Select LCN DIAG.Select CABLE

SWAP INH.Select INHIBIT SWAPPING.On the right side, you will
see the INHIBIT TIME REMAINING.

NOTE: If you use this process to check the cable swap

configured time, select PERMIT SWAPPING, to allow the
LCN to swap.

NOTE: Open Tee connections can introduce noise and

errors to the LCN system. Honeywell recommends removal
of all unused Tees attached to LCN cabling. If an unused, or
partially used (one Tee connection point is unused) Tee
remains, it must be positioned or insulated in such a
manner to prevent any possible electrical contract,
including any electrical grounds.

492
 Chapter 11 - Decommission/Recommission Nodes

ATTENTION: It is important that you prevent the possibility

of someone inadvertently reconnecting a decommissioned
LCN node to the ELCN/LCN system, causing duplicate
LCN addresses on the new ELCN.

It is a good practice is to communicate to all applicable

personnel that they do not connect any disconnected BNC Tees
and/or power on a disconnected node without making sure that
this action would not result in creating a duplicate LCN
address.

Consideration for Small LCN Networks

As LCN nodes are migrated to ELCN, the number of LCN nodes
decreases, however,for the LCN token ring to operate, a
minimum of 3 LCN nodes is required. As the ELCN Bridge is
redundant, in the event of failures, one can shut down or
reboot, and this may leave the LCN with not enough active LCN
nodes, which may cause the token ring to fail. To mitigate this,
a ballast node should be added to the LCN.
When all nodes have been migrated, the ballast nodes can be
turned off and continued with "To Decommission the ELCN
Bridge."
What is a Ballast Node?
A ballast node is simply an LCN device that is powered on and
set to an unused and valid LCN address.

Recommissioning an LCN Node

Before you recommission an LCN node, check to see that there
is not an ELCN or LCN node that is using the same LCN
Address before powering up the node and reconnecting it to
LCN coax. The fail-safe way to determine what LCN node
numbers are not being used is to check the Network
Configuration File (NCF).
When assigning or changing the LCN node number of any LCN
or ELCN node, it is imperative that the intended node number
is not already in use by another LCN or ELCN node.

493
Chapter 11 - Decommission/Recommission Nodes

If you cause a duplicate node number situation to occur, the

invalid duplicate node fails, and the existing running node may
become ISOLATED from some LCN and ELCN nodes. To
recover from this situation, power-off the node with the invalid
address, change its LCN node number to an unused LCN
address, power it back on, and reload the existing running node
that may have become ISOLATED. To load an ISOLATED ELCN
Node, first shut down the node (using System Status display in
Native Window) and then load the node.

To Decommission the ELCN Bridge

When all coaxial LCN nodes have been migrated to the
Experion LCN and there is no longer a need for the ELCN
Bridge, you may perform the following steps to decommission
the ELCN Bridge.

Step Action Done

1 Verify that there are no coaxial LCN

nodes listed in the Bridge Status tab of
the Primary ELCN Bridge’s HMIWeb
Detail Display..

2 From the Control Builder Monitoring

side, right-click the primary ELCN
Bridge platform block, and click Delete.
RESULT: Both primary and secondary
ELCN Bridge blocks are deleted from
the Monitoring side. This also changes
the UEAs to the “NOT LOADED” state, as
seen from the UEA’s front LED display.

3 Initialize the UEA to the factory firmware

image (FACT). It is preferred that you
perform these steps on both UEA boxes
for the primary and secondary ELCN
Bridge at the same time.

1. Rotate the key clockwise to the C

position. RESULT: The display shows
DETAILS, CONFIG, and REBOOT
options.

494
 Chapter 11 - Decommission/Recommission Nodes

Step Action Done

2. Press the down navigation arrow to

navigate to and highlight the
REBOOT option.

3. Press OK to select REBOOT. RESULT:

The display shows the
Reboot/FactoryInit menu.

EXIT To return to the

initial menu.

RBOOT To reboot the

node without
making any
changes.

FACT Returns this

FACT=Factory UEA to the
Image! Factory
Firmware
Image (after
confirmation).

4. Press the right navigation arrow to

highlight FACT, then press OK.
RESULT: The message PLEASE
CONFIRM displays.

495
Chapter 11 - Decommission/Recommission Nodes

Step Action Done

5. Press the right navigation arrow

again to highlight FACT, and then
press OK again to confirm that you
want the factory image.
RESULT: The current application and
configuration is removed, and the
node is rebooted into the Factory
image.
6. Rotate the key back to the R1
position. You may remove the key as
desired.

4 After initializing the primary and

secondary UEAs to the factory image, do
the following to decommission the
UEAs:
1. Remove the power.
2. Disconnect the redundancy cable.
3. Disconnect the ELCN MAUs.
4. Disconnect the FTE cables.
The procedure is complete.

5 Optional: Go to the Control Builder

Project side, right-click the primary
ELCN Bridge platform block, and click
Delete.
RESULT: Both primary and secondary
ELCN Bridge blocks are deleted from
Project side of Control Builder.

To Initialize a UEA to the Factory (FACT) Image

Perform the following procedure from the UEA front panel
display, to initialize the UEA to the Boot/recovery personality
image, also known as the Factory image.

496
 Chapter 11 - Decommission/Recommission Nodes

ATTENTION: The UEA should not be currently in use when

you initialize it to the factory image. This procedure is only
for non-operational UEAs. When you perform the FACT
command, the current Application firmware image and all
Control Builder platform block configuration is removed
from the UEA. The UEA is rebooted into the Factory image
and placed in the Alive state.

Step Action Done

1 Rotate the key clockwise to the C position.

RESULT: The display shows DETAILS,
CONFIG, TEST and REBOOT options.

2 Press the down navigation arrow to

navigate to and highlight the REBOOT
option.

3 Press OK to select REBOOT.RESULT: The

display shows the Reboot/FactoryInit
menu.

EXIT To return to the

initial menu.

RBOOT To reboot the

node without
making any
changes.

FACTFACT=Factory To remove from

Image! the UEA, the
current
Application
personality
image, all
Control Builder
block
configuration,
and then reboot
into the
Boot/recovery

497
Chapter 11 - Decommission/Recommission Nodes

Step Action Done

personality
image (also
known as the
Factory image)
and to the Alive
state

4 Press the right navigation arrow to

highlight FACT, then press OK.
RESULT: The message PLEASE
CONFIRM displays.

5 Press the right navigation arrow again to

highlight FACT, and then press OK again
to confirm that you want the factory
image.
RESULT: The current application and
configuration is removed, and the node is
rebooted into the Factory image.

6 EXIT to the main menu. Rotate the key to

the R1 position. You may remove the key
as desired.

7 Repeat Steps 1-6 for the secondary UEA,

if redundant.

498
CHAPTER

12 TERMS AND DEFINITIONS

Term Definition

ACE-T Application Control Environment that TPN/LCN-connected. The ACE-

T is a control platform that can be used for applications that do not
require an embedded controller – such as supervisory control
applications, procedural operations using standard function blocks,
and custom applications using Honeywell Custom Algorithm Blocks.
On the Experion LCN, the ACE-T is a Windows-based node that has
an emulated LCN interface presented to its TPN/LCN personality and
no actual LCN coax connection.

AM Application Module. The AM is a TPN/LCN node that supports

supervisory control functions and facilitates the implementation of
advanced calculations and control strategies. On the Experion LCN,
the AM has an emulated LCN interface presented to its TPN/LCN
personality and no actual LCN coax connection.

CDA Control Data Access. The Experion System communication

infrastructure and data access interface schema that provides
application integration with Experion system objects. It supports both
parameter access response messaging and notification messaging.

Classic Refers to an LCN coaxial-based node (as opposed to an ELCN FTE-

based node).

COTS/x86 Commercial Off The Shelf PC hardware platform that uses an Intel
x86 processor. The x86 line of processors includes the Core, Xeon,
Pentium, Atom and earlier 286, 386 and 486 models (hence, the "86").

DSA Distributed System Architecture. DSA provides global access to point

parameter data on all servers in the Experion System. Each server
provides automatic dynamic caching of remote data for all of its
clients, so that clients access their local server for all data.

E-APP Experion Application Processing Platform. The E-APP is a TPN/LCN

connected Windows-based APP node acting as the primary data
access portal to LCN/UCN data, often used for large scale data
access to L3 applications (such as PHD, Profit Suite and TotalPlant
Batch) by way of communication interfaces, such as DCOM, OLE, and
OPC. The E-APP configuration does not use Control Builder and does
not go into the Experion ERDB. It has the TPN Server connectivity

499
Terms and definitions

Term Definition

Client package and Experion APP TPS Client. On the Experion LCN,
the E-APP has no actual TPN/LCN coax connection or LCNI device;
instead, an emulated LCNI is presented to its TPN/LCN personality.

EHB Experion Hiway Bridge. The EHB is a TPN/LCN node that is an

enhanced Hiway Gateway (HG), wherein FTE replaces the coax Data
Hiway. It is capable of connecting to Data Hiway box emulations
loaded on Experion C300 controllers.

ENIM Enhanced Network Interface Module. The ENIM is the gateway device
between the FTE-based Enhanced UCN (EUCN) and the TPN/LCN.
The ELCN version of the ENIM has no actual TPN/LCN coax
connection or LCNI device; instead, an emulated LCNI is presented to
its TPN/LCN personality.

EPCLG Enhanced Programmable Logic Controller Gateway. The EPCLG is a

TPN/LCN node that provides a direct interface to any of several
Programmable Logic Controllers (PLCs) available from various
manufacturers.

ERDB Engineering Repository Database. The database in which all Experion

Control Builder data is stored. Located on the preferred backup
Experion server.

ES-T Experion Station that is TPN/LCN-connected. The ES-T is a Windows-

based node providing the Station application as an operator interface
for status displays, alarms, graphic displays, trends, and other
operations displays. In addition, the ES-T provides the Native Window
application that emulates a Universal Station. The ELCN-enabled ES-
T has no actual LCN coax connection or LCNI device; instead, an
emulated LCNI is presented to its TPN/LCN personality.

FTE Fault Tolerant Ethernet - FTE is the Ethernet-based, redundant

control network of Experion.

ESIS Experion Software Installation Server. Tool used for installing

Experion PKS operating system and/or products (nodes).

ESVT Experion Server that is TPN/LCN-connected. The ESVT is an

optionally redundant Windows-based node providing tools, such as
Control Builder and HMIWeb Display Builder, and acting as the
central repository for all system data. It also runs core system
functions, including the following:
• Data acquisition and processing

500
 Terms and definitions

Term Definition

• Alarm and event management

• History collection, archiving and trending
• Reporting subsystem
• Sign-on security
The ELCN-enabled ESVT has no actual TPN/LCN coax connection or
LCNI device; instead, an emulated LCNI is presented to its TPN/LCN
personality.

EUCN Enhanced UCN – The EUCN supports the ENIM and EHPM, where
the traditional coaxial cable UCN system is replaced by FTE.

MAU Media Access Unit. Each ELCN Bridge requires a MAU cable pair to
connect to the LCN A and B coax cables. This ELCN MAU is a new in-
cable MAU. The MAUs that were used to connect Experion TPS Nodes
to the LCN are not needed on ELCN-enabled Experion TPS Nodes.

NG Network Gateway. The NG is a TPN/LCN node that provides a

communications path between two or more Local Control Networks
(LCNs).

On-Process Migration of an Experion system or an Experion system component

Migration while maintaining view and control of the process. This is achieved by
(OPM) using redundant system components.

PdTag Physical Device Tag Name of a device. For UEA nodes, Pdtag
combines the name of the UEA personality image that executes in the
node with the node’s FTE Device Index. The FTE Status Display shows
Pdtag.

Platform The object at the top of the ELCN data organization hierarchy in
Block Control Builder. It presents the following for the ELCN Bridge and
each ELCN Appliance Node:
•Control Data Access (CDA) parameters, which allow for the
configuration of properties common to all supported downlink
protocols.
•System operational parameters, which allow for the control of key
behaviors such as redundancy.
•Statistical parameters, which allow for the view of runtime
performance metrics.

501
Terms and definitions

Term Definition

An ELCN platform block is a CDA point in Experion, so each block has

its own HMIWeb point detail display and faceplate.

Thin Client Thin clients are used for provide user interaction with virtual
machines. A Thin Client is a device that fulfills the role of a
workstation computer while the actual workload resides on a remote
server. A Thin Client extends the audio, video, and USB signals
through a network cable connection to the CPU of a remote virtual
machine on the same network.

TPN TotalPlant™ Solution Network, formerly known as LCN.

TPS TotalPlant™ Solution, formerly known as Total Distributed Control

(TDC 3000).

UEA Universal Embedded Appliance. A Honeywell hardware platform

based on the Linux operating system that provides a platform for
core TDC 3000 capabilities, interfaces to other systems, and bridging
capabilities for systems under migration from LCN to ELCN. The user
loads (flashes) the UEA firmware in order to define the platform’s
specific application, such as ELCN Bridge or ELCN Application Node.

VM Virtual Machine. A software implementation of a physical computer

that runs an operating system and applications.

502
 Notices

NOTICES
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC
3000® are registered trademarks of Honeywell International,
Inc.
Versatilis® and Signal Scout® 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
Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH.
Movilizer GmbH is a business unit of Honeywell International,
Inc.

Other trademarks
Microsoft and SQL Server are either registered trademarks or
trademarks of Microsoft Corporation in the United States
and/or other countries.
Other brands or trademarks are trademarks of their respective
owners.
Trademarks that appear in this document are used only to the
benefit of the trademark owner, with no intention of trademark
infringement.

Third-party licenses
This product may contain or be derived from materials,
including software, of third parties. The third party materials

503
Notices

may be subject to licenses, notices, restrictions and obligations

imposed by the licensor. The licenses, notices, restrictions and
obligations, if any, may be found in the materials
accompanying the product, in the documents or files
accompanying such third party materials, in a file named third_
party_licenses on the media containing the product.

Documentation feedback
You can find the most up-to-date documents in the Support
section of the Honeywell Process Solutions website at:
https://process.honeywell.com
If you have comments about Honeywell Process Solutions
documentation, send your feedback to:
[email protected]
Use this email address to provide feedback, or to report errors
and omissions in the documentation. For immediate help with
a technical problem, contact HPS Technical Support through
your local Customer Contact Center, or by raising a support
request on the Honeywell Process Solutions Support website.

How to report a security vulnerability

For the purpose of submission, a security vulnerability is
defined as a software defect or weakness that can be exploited
to reduce the operational or security capabilities of the
software.
Honeywell investigates all reports of security vulnerabilities
affecting Honeywell products and services.
To report a potential security vulnerability against any
Honeywell product, please follow the instructions at:
https://www.honeywell.com/us/en/product-security.

Support
For support, contact your local Honeywell Process Solutions
Customer Contact Center (CCC). To find your local CCC visit the
website, https://process.honeywell.com/us/en/contact-us.

504
 Notices

Training classes
Honeywell holds technical training classes that are taught by
process control systems experts. For more information about
these classes, contact your Honeywell representative, or see
https://process.honeywell.com/us/en/services/training.

505