The balance-of-plant deployment is the focus of this section.
The DeltaV PK controller is a type of DeltaV controller that is configured using the DeltaV engineering tools software (for example, DeltaV Explorer) on a DeltaV node.
The DeltaV PK controller makes control of Ethernet devices easy with built-in Ethernet ports (on the IOP) and native protocols supported by the controller – extra cards are not required.
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.
You can connect to DeltaV IO nodes (CIOC, SZ controllers, or WIOC) on the DeltaV ACN.
Up to a total of 16 CIOCs and WIOCs (combined), plus one SZ controller can be configured in the project. The maximum number of remote nodes is the same for all DeltaV PK controller license versions.
Additional interfaces include Modbus TCP and OPC UA.
A DeltaV PK controller can begin configured to run in a standalone fashion and then be merged into the balance-of-plant DeltaV system. Once merged, the controller is configured, downloaded, updated the same as other DeltaV controllers.
The merging process incorporates the database from the DeltaV PK controller into the DeltaV balance-of-plant database, resulting in a single, native database and system. This process addresses potential conflicts with tags, named sets, and so on, thereby eliminating many of the pains associated with mapping two systems together using communication protocols.