The standalone deployment is the focus of this section.
The Standalone DeltaV PK controller provides a control solution for smaller-scale applications such as skid units or small unit operations. It is designed to operate in a standalone fashion, meaning that it runs without requiring a connection to a server, panel HMI, or other typical DCS system elements.
It is configured using the DeltaV PK controller engineering software installed on a laptop or workstation of your choosing (provided it meets the minimum system requirements).
Control of Ethernet devices is made easy with built-in Ethernet ports and native protocols supported by the controller – extra cards are not required.
You can connect to DeltaV IO nodes (CIOC or WIOC) on the DeltaV ACN. You can also connect to and obtain IO from the DeltaV logic solvers.
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.
The IP addressing that the system assigns to the Standalone DeltaV PK controller and its device network nodes is appropriate for an independent standalone system. However, if you network the multiple Standalone DeltaV PK controllers, IP address conflicts will occur. Therefore, you can modify the IP addresses manually such that all nodes in the network have a different IP address. You must manually track all the IP addresses you assign so that you avoid any conflicts.
Additional interfaces include Modbus TCP and OPC UA.
It is recommended that you use the controller's physical key switch and the DeltaV lock feature to protect your Standalone PK controller from unauthorized access.
Any time after being configured to run in a standalone fashion, the DeltaV PK controller can be merged into a broader DeltaV system. 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.