The module on the DeltaV PK controller that houses the Ethernet ports. There are two IOPs on the DeltaV PK controller: primary (left side) and secondary (right side). The secondary is normally used for redundant networks for your IO communication. The IOP can communicate using native DeltaV, Modbus TCP, OPC UA server, and either Modbus or Ethernet IP client protocols.
This process takes the database from the Standalone DeltaV PK controller and combines it with the existing balance-of-plant DeltaV database to create one unified database, and places the DeltaV PK controller (and DeltaV local panel HMI if present) as native nodes on the DeltaV network.
The merge process identifies potential tag name conflicts; saves the last configuration on the Standalone DeltaV PK controller; shows the license demand of the standalone system; decommissions the Standalone DeltaV PK controller and commissions it as a node on the DeltaV network.
The tools you use to configure the Standalone DeltaV PK controller. The software applications make it easy to establish communications with a Standalone DeltaV PK controller and to manage project files associated with different controllers. The tools are essentially the same as the DeltaV balance-of-plant engineering tools, with the main limitation being that the DeltaV PK controller engineering software cannot be used to configure controllers other than DeltaV PK controllers; and, it can only configure one DeltaV PK controller per project.