Emerson DeltaV (DCS) — via OPC UA
DeltaV values are collected by connecting to DeltaV's OPC UA server with the OPCUA driver.
Follow Connecting a DCS (OPC UA) for the procedure.
Overview
| Item | Value |
|---|---|
| Collection path | DeltaV's OPC UA server → OPCUA driver |
| Driver to use | OPC-UA driver |
DELTAV entry | Placeholder (stub) — does not collect |
The connection between DeltaV and Edge has not been verified on real site equipment. There are no customer installations yet either.
The DELTAV entry is a stub
DELTAV is in the opc_type list, but there is no implementation that communicates with DeltaV.
It is a placeholder that simply inherits the common stub.
| Item | Value |
|---|---|
opc_type | DELTAV |
| Implementation class | plantpulse.driver.protocol.deltav.DeltaVDriver (extends AbstractStubDriver) |
| connect | Not attempted — only logs a warning and leaves the connection status DISCONNECTED |
| read | Empty value ("") |
| write | Not supported (false) |
If you register it as DELTAV, no values arrive. Register it as OPCUA.
Registering with OPCUA
If DeltaV's OPC UA server endpoint is opc.tcp://<IP>:<port>/<path>, split it as follows.
| Field | Value |
|---|---|
opc_type | OPCUA |
opc_agent_ip | <IP> |
opc_agent_port | <port> — confirm with the DCS administrator |
options.servername | <path> (empty if there is none) |
options.username · options.password | Read-only account |
The detailed meaning of the fields and the tag plc_address (NodeId) format are in OPC-UA driver.
For the current state of secure connection, see Connecting a DCS (OPC UA).