OPC UA Configuration for GE Mark VIe and Yokogawa CENTUM VP Data Exchange

A field-proven approach to configuring OPC UA server endpoints, security certificates, and subscription parameters for reliable real-time data exchange between GE Mark VIe turbine controllers and Yokogawa CENTUM VP DCS — including fault isolation and performance benchmarking procedures.
Why OPC UA Between Mark VIe and CENTUM VP
Gas turbines under GE Mark VIe control must share speed, exhaust temperature, fuel flow, and alarm states with the plant DCS. Yokogawa CENTUM VP is the DCS of choice in many LNG and refinery sites. Traditional OPC DA (DCOM-based) connections between these systems are fragile. DCOM authentication fails after Windows security patches. OPC UA eliminates DCOM dependency.
GE Mark VIe runs an embedded OPC UA server on the UCSC controller, compliant with IEC 62541. Yokogawa CENTUM VP acts as the OPC UA client through its OPC UA Gateway option. Both support security policy Basic256Sha256 with SignAndEncrypt, satisfying IEC 62443-3-3 SR 3.1 for encrypted cross-zone data transport.
Mark VIe OPC UA Server Endpoint Configuration
Access the Mark VIe OPC UA server settings in the ToolboxST application. Navigate to Unit — Communications — OPC UA Server. The default endpoint URL format is opc.tcp://[Mark VIe IP]:4840. Set the IP to the dedicated OPC UA VLAN address. Do not use the IONet ring IP for OPC UA traffic. Mixing OPC UA browse traffic with IONet deterministic I/O traffic causes IONet frame errors above 500 pps browse rate.
Configure the security policy as follows:
- Step 1: Open ToolboxST. Navigate to Unit — Communications — OPC UA Security. Set Security Policy to Basic256Sha256. Set Message Security Mode to SignAndEncrypt.
-
Step 2: Export the Mark VIe server certificate from ToolboxST. The certificate is stored as a .DER file. Copy this file to the Yokogawa CENTUM VP OPC UA Gateway trusted certificates folder at
C:\YokogawaOPCUA\PKI\trusted\certs\. - Step 3: Export the CENTUM VP client certificate from the Yokogawa OPC UA Configuration Tool. Copy it to the Mark VIe trusted certificates path in ToolboxST. Navigate to Unit — Communications — OPC UA Security — Trusted Clients — Import Certificate.
- Step 4: Restart the Mark VIe OPC UA server service in ToolboxST. Confirm the server status shows "Running" with a green LED indicator. Allow up to 60 s for the certificate exchange handshake to complete.
- Step 5: In CENTUM VP OPC UA Gateway, add a new server connection. Enter the Mark VIe endpoint URL. Select the security policy matching the server configuration. Browse the Mark VIe namespace to confirm tag visibility before building the tag import list.
Subscription Publishing Interval and Monitored Item Tuning
OPC UA publishing interval determines how quickly CENTUM VP receives updated values from Mark VIe. For turbine protection data (speed, exhaust temperature, vibration), set publishing interval to 500 ms. For slower process data (fuel flow totals, load setpoints), use 2,000 ms to reduce bandwidth.
Set monitored item queue size to 5 for fast tags. If the CENTUM VP client polls at 1,000 ms and Mark VIe updates at 500 ms, a queue size of 3 is sufficient. Increase to 10 if the historian shows gap patterns during network congestion.
Configure the CENTUM VP OPC UA Gateway Deadband per tag group. Apply 0% deadband to digital status tags (alarm states, trip relays). Apply 0.5% deadband to analog process values such as compressor discharge pressure and inlet air temperature. This reduces historian load without losing alarm fidelity.
Five-Step OPC UA Connectivity Fault Isolation
OPC UA connection failures between Mark VIe and CENTUM VP fall into five categories. Use this sequence to isolate the root cause efficiently:
-
Step 1 — Network layer: Ping the Mark VIe OPC UA VLAN IP from the CENTUM VP gateway server. If no reply, check VLAN routing table and firewall rules. TCP 4840 must be open in both directions between VLAN 10 (turbine) and VLAN 20 (DCS). Verify with
netstat -anon the CENTUM VP gateway server. - Step 2 — Certificate trust: Open the Mark VIe ToolboxST OPC UA Security log. Look for "Certificate rejected" entries. Re-import the CENTUM VP client certificate. Confirm certificate validity period has not expired. OPC UA certificates default to 1-year validity. Renew before expiry using the Yokogawa OPC UA Certificate Manager utility.
-
Step 3 — Session timeout: CENTUM VP OPC UA Gateway logs show "Session timeout" at 600 s intervals. This indicates TCP keepalive failure. Enable TCP keepalive on the gateway server NIC: set KeepAliveTime to 30,000 ms in the Windows registry at
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. - Step 4 — Tag address mismatch: CENTUM VP historian shows BAD quality for selected tags after a Mark VIe firmware upgrade. ToolboxST firmware upgrades can change NodeID integer identifiers. Re-browse the Mark VIe namespace in CENTUM VP OPC UA Gateway. Rebuild the tag address mapping file and reload the CENTUM VP OPC UA client configuration.
- Step 5 — Subscription data stale: CENTUM VP operator console shows last-known-good values with timestamps frozen 30+ seconds behind real time. Cause: Mark VIe subscription publish queue overflow. Reduce the number of monitored items per subscription below 500. Split large subscriptions into multiple smaller ones with staggered publishing intervals.
Conclusion and Action Advice
OPC UA integration between GE Mark VIe and Yokogawa CENTUM VP delivers reliable, encrypted cross-vendor data exchange without DCOM instability. Use Basic256Sha256 with SignAndEncrypt for all security policies. Separate OPC UA traffic onto a dedicated VLAN away from IONet. Set publishing intervals at 500 ms for protection data and 2,000 ms for process totals. Apply 0.5% analog deadband to reduce historian load. Renew certificates before expiry and rebuild NodeID mappings after every Mark VIe firmware upgrade. These practices keep turbine-DCS integration stable across planned and unplanned maintenance cycles.
Author: Li Wei is an industrial automation engineer with over 10 years of experience in PLC, DCS, and control systems.
