Experion Local Control Network

This article is about honeywell experion, experion lx, honeywell experion dcs system architecture, honeywell experion controller, honeywell enim, honeywell automation and control solutions, honeywell control builder and honeywell control systems.

Experion Local Control Network

Experion-Local-Control-Network

The Experion Local Control Network (ELCN) is an innovative solution provided by Honeywell that utilizes the proven Experion Fault Tolerant Ethernet (FTE) infrastructure. It allows for the migration of Classic COAX Local Control Network (LCN) nodes to the FTE-based Experion LCN nodes, providing a seamless transition and the elimination of the legacy LCN-based system.

The ELCN system consists of two main parts: the ELCN Bridge and the conversion of LCN nodes to Experion LCN nodes. The ELCN Bridge acts as a bridge between the Classic LCN and the Experion LCN, enabling the coexistence and interoperability of both systems during the migration process. The Bridge translates LCN messages into Ethernet messages and vice versa, allowing for communication between the two networks.

To migrate to ELCN, an ELCN Bridge node is installed to connect the Classic LCN to the Experion LCN, creating a hybrid network. The migration process can then proceed incrementally by upgrading the Classic LCN nodes to Experion LCN nodes one at a time. During the upgrade, the logical role of the node remains unchanged, and it appears unchanged in configuration to its operating peer nodes. This process can take place over an extended period until all nodes are migrated, and the ELCN Bridge can be removed.

The Universal Embedded Appliance (UEA) is a hardware component of ELCN that can function as both an ELCN Bridge and an ELCN appliance node. The UEA is used to establish the connection between the LCN and the ELCN. It converts LCN analog signals to digital signals and vice versa, enabling full two-way communication between the LCN and ELCN networks.

The requirements for implementing an ELCN Bridge include having the appropriate TPN/LCN and Experion PKS releases, running Windows 10 or Server 2016 operating systems on the Experion TPS nodes, configuring the Experion Base IP address, running the BOOTP Server service on the ESVT, and configuring the NCF clock on the ESVT server.

The configuration of the ELCN Bridge and Appliance nodes involves using tools such as the Firmware Manager Tool to load firmware and the Control Builder to configure the nodes. The ELCN Appliance nodes have the same personality image as their LCN equivalents and can be virtual machines, hardware-based (UEA), or a combination of both.

Overall, the Experion Local Control Network (ELCN) provides a smooth and flexible migration path for upgrading from the legacy LCN system to the modern Experion LCN solution. It enables the retention of existing control strategies, field terminations, applications, history, and graphics, while offering optional lifecycle advantages through virtualization.

honeywell experion dcs system architecture

The provided diagram illustrates a basic Experion Local Control Network (ELCN) system architecture for a migration scenario. Here is an overview of the components and their roles in the system:

1. Redundant ELCN Bridge UEA Boxes: These boxes serve as the bridge between the legacy LCN and the Experion FTE networks. They facilitate the communication between the two networks during the migration process.
2. Microsoft Windows-based Nodes: The nodes such as ESVT (Experion Server for TPS), ES-T (Experion Station), ACE-T (Application Control Environment – TPN connected), and E-APP (Experion APP node) have been converted from LCNP4E-based nodes to run as virtual machines on x86 servers with the Microsoft Windows operating system. These virtual machines are equipped with thin clients and provide control room interfaces.
3. Virtualized History Module: The History Module, responsible for handling historical data, has been virtualized to run as a virtual machine on an x86 server platform. It can be hosted on a physical server with Server 2016 or as a virtual machine.
4. Converted LCN Nodes: The K4LCN-based ENIM, NIM, AM, EPLCG, NG, and EHB with C300s have been converted to UEA hardware, allowing them to be part of the Experion LCN system. The LCN NIM, AM, EPLCG, EHB, and NG are still providing data to the Experion system through the ELCN Bridge.
5. Experion LCN Nodes: The Experion LCN nodes, including ES-T, ACE-T, ESVT, E-APP, HM (History Module), ENIM, AM, EPLCG, EHB, and NG, are implemented either as virtual nodes in VMware or as standalone PCs without LCN-connected hardware (LCNP4E2).
6. User Interface Node Conversion: Legacy LCN-based user interface nodes, such as Universal Station (US), UxS (third-party user interface), and GUS, need to be converted to ES-T nodes. This can be achieved either by upgrading the PC-based software to use both encapsulated LCN communication and legacy LCN communication or by virtualizing the user interface node and using a thin client with peripherals for user interface functions.

It’s important to note that the ELCN Bridge must be installed as a redundant pair for proper functionality. The ACE-T, ES-T, ESVT, E-APP, HM, ENIM, AM, EPLCG, EHB, and NG nodes can exist in both physical and virtual platforms, providing flexibility in the system architecture.

Please be aware that the information provided here is based on the specific scenario described in the text. The actual system architecture may vary depending on the implementation and requirements of the ELCN system.

What is Experion LCN? Honeywell Control System Explained