Emerson DeltaV — DCS
DeltaV is Emerson Process Management's DCS (Distributed Control System). It is widely used in continuous processes such as refining, chemicals, power generation, and pharmaceuticals, and its internal control network (ACN, Area Control Network) is built on proprietary protocols.
Reverse-engineering the DeltaV ACN internal protocol or connecting with unofficial libraries may void your Emerson license / support agreement. Because this affects process safety systems (with audit implications for SIL, FDA 21 CFR Part 11, etc.), never use anything other than the official integration paths (OPC UA / OPC DA / REST).
The DELTAV driver in this gateway is a stub. For actual DeltaV data collection, use one of the official integration paths below.
Official integration paths
Option 1. Built-in DeltaV OPC UA Server (v14 or later — recommended)
An official OPC server that can be enabled on a ProfessionalPLUS or Application station. Previously only OPC DA (COM) was supported, but from DeltaV v14+ an OPC UA Server is provided alongside it.
| PlantPulse driver to use | Page |
|---|---|
OPCUA | OPC-UA |
Option 2. OPC DA → OPC UA gateway (older DeltaV versions)
Systems running DeltaV v13 or earlier often have only OPC DA (COM). In this case, place a gateway such as Kepware KEPServerEX, Matrikon OPC UA Tunneller, or Softing dataFEED on the DeltaV side, and have PlantPulse connect to the gateway's OPC UA Server.
| PlantPulse driver to use | Page |
|---|---|
OPCUA | OPC-UA |
Option 3. DeltaV Live REST API (secondary channel)
DeltaV Live (the v14+ HTML5 operator interface) exposes some data over REST. Recommended only as a secondary channel for operational monitoring.
| PlantPulse driver to use | Page |
|---|---|
HTTP | HTTP push |
Which path should you choose
| DeltaV version | Recommended path |
|---|---|
| v14 or later | Built-in DeltaV OPC UA Server → OPCUA driver |
| v12 – v13 | OPC DA→UA gateway such as KEPServerEX → OPCUA driver |
| DeltaV Live operator screen data | DeltaV Live REST → HTTP driver |
| Other / special requirements | Consultation with an Emerson Local Business Partner recommended |
Common node notation when registering over OPC UA
DeltaV modules / parameters are exposed in the OPC UA namespace in the following form.
| Notation (NodeId format) | Meaning |
|---|---|
ns=2;s=AREA_A1/PIC101/PV.CV | PV (Process Variable) of module PIC101 in area A1 |
ns=2;s=AREA_A1/FIC202/SP.CV | Setpoint of module FIC202 |
ns=2;s=AREA_A1/TIC305/MODE.TARGET | Mode of module TIC305 (AUTO / MAN / CAS) |
ns=2;s=AREA_A1/PUMP01/STATE | ON/OFF status of module PUMP01 |
The namespace index (ns=2) differs by site, and has a different layout when KEPServerEX is used. Confirm the exact NodeId via a module / parameter export from DeltaV Configure or an OPC UA browse tool (UaExpert) before registering.
Security / operations checklist
- Verify permission to enable the OPC UA Server on the DeltaV ProfessionalPLUS console
- Add the PlantPulse host IP to the firewall whitelist of the DeltaV Application Station
- Register and trust OPC UA certificates (X.509) on both sides
- Give the user account read-only permission (never grant write)
- Follow the DeltaV management of change (MOC) procedure — obtain prior approval for all integration work
- Monitor communication traffic — assess the impact on process network load in advance
- A timecycle of 5 seconds or more is recommended on the PlantPulse side (process data does not need to be faster)
stub registration (for reference)
| Input field | What to enter |
|---|---|
| IP address | (unused, dummy) |
| Port | (unused, dummy) |
| Automatic collection | Disabled recommended |
Common problems
| Symptom | Possible cause | Resolution |
|---|---|---|
| No values after registering DELTAV | stub driver | Re-register using the OPCUA path |
| OPC UA certificate rejected | Trust settings missing on one side | Establish two-way trust with UaExpert, then also register the PlantPulse-side certificate |
| Anonymous login blocked | DeltaV security policy (strongly recommended) | Create a read-only user account on the DeltaV side and use username/password |
| Some module nodes are not visible | Omitted from the OPC UA Server export settings | Check "OPC export" for that module in DeltaV Configure |
| Stale values | Process data is inherently slow + sampling rate | Use a timecycle of 5–10 s; small variation ranges are normal |
Next steps
- DeltaV OPC UA Server activation manual — official Emerson guide
- The authentication / certificate section of the OPC-UA registration page
- Technical background: DeltaV driver (advanced)