S7-1500 OPC UA Error 16#B080_C400: Enable Client Interface

S7-1500 OPC UA Error 16#B080_C400 (Simatic_ClientNotEnabled): Activating the Client Interface

An S7-1500 acting as an OPC UA client returns STATUS = 16#8601 with sub-status 16#B080_C400 on SFB "OPC_UA_Connect" when the OPC UA client runtime has not been enabled in the CPU configuration. The same symptom appears when an S7-1500 tries to reach an S7-1200 OPC UA server, even though third-party OPC UA clients (UaExpert, etc.) and the TIA Portal OPC UA client wizard can still reach the server. This reference isolates the failure to a single configuration bit in TIA Portal, lays out the hardware and firmware prerequisites, and documents every related sub-status value the OPC_UA_ConnectStatus output can deliver.

1. Problem Statement

Symptom reported on an S7-1500 user block calling SFB OPC_UA_Connect:

• STATUS = 16#8601 — "Error during connect (SFB 'OPC_UA_Connect')"
• OPC_UA_ConnectStatus = 16#B080_C400 — Simatic_ClientNotEnabled
• ERROR = TRUE, DONE = FALSE, BUSY = FALSE

The OPC UA server (an S7-1200 in the typical reference topology) is reachable from a generic OPC UA client and from the TIA Portal client wizard, so the network path, server certificate, and TCP/4840 endpoint are known to be valid. The failure is on the S7-1500 client side, not on the server.

2. OPC UA Status Code Architecture

The OPC UA client runtime on S7-1500 reports failures through two parallel outputs on every SFB in the OPC_UA family:

When the high word is 16#B080, the sub-code is a Siemens (SIMATIC) extension rather than an OPC UA standard code. The convention B080_xxxx identifies a vendor-specific namespace; OPC Foundation standard codes use values defined in OPC 10000-6 Part 6: Mappings — OPC UA Connection Protocol.

Common high-level STATUS values

3. Hardware, Firmware and Software Prerequisites

Before attempting to enable the client interface, confirm the S7-1500 and S7-1200 involved are capable of running OPC UA and that the project is on a TIA Portal version that exposes the configuration UI.

3.1 S7-1500 client-side prerequisites

3.2 S7-1200 server-side prerequisites

3.3 TIA Portal version

The OPC UA client configuration UI under CPU properties > OPC UA > Client requires TIA Portal V14 SP1 Update 4 or higher. Use the version that matches the S7-1500 firmware generation: V15.1 / V16 / V17 / V18 are appropriate depending on the latest firmware installed on the controller. Mixing TIA Portal versions across project, controller firmware, and HMI can suppress the OPC UA pages on the client CPU even though the firmware supports OPC UA.

4. Root Cause: Client Interface Disabled in CPU Configuration

By default, the S7-1500 ships with the OPC UA client runtime disabled. The TIA Portal project that compiles the CPU configuration contains an OPC UA property group with a single, decisive check-box: "Activate OPC UA client" (German: OPC-UA-Client aktivieren). When the box is unchecked, the OPC UA client engine is not loaded into the CPU firmware image. The SFB call still compiles, the SFB still returns a structured status — but every OPC_UA_Connect request is rejected before the first TCP SYN is sent, because the OPC UA client stack is simply not present at runtime.

This is by design: OPC UA carries licensing terms that Siemens makes explicit through runtime licenses on the server side and through project-side configuration on the client side. Leaving the client disabled by default also keeps the attack surface minimal when an automation cell does not actually require OPC UA client services.

The two parallel diagnostics — a successful UaExpert connection and a successful TIA Portal client-wizard connection — confirm the server is healthy. The S7-1500 connection failure is therefore purely a configuration issue on the client side.

5. Solution: Activating the OPC UA Client in TIA Portal

Activate the OPC UA client interface and recompile the CPU configuration. The procedure is the same for every S7-1500 project that contains an OPC UA client block.

1. In the TIA Portal project tree, expand Devices & networks and select the S7-1500 CPU that hosts the SFB OPC_UA_Connect instance.
2. Open Properties > OPC UA > Client. (Older TIA Portal versions place the page under Properties > OPC UA > Client server interface; the V17/V18 wording is OPC UA > General > Client.)
3. Check "Activate OPC UA client". If the checkbox is greyed out, the firmware loaded in the device configuration does not support OPC UA — update the firmware version in the device configuration first.
4. Under Security policy select the policy the server requires. Use None only for lab commissioning; production deployments must select Basic128Rsa15, Basic256, Basic256Sha256, or Aes128_Sha256_RsaOaep depending on the S7-1200 firmware.
5. Under Authentication set Anonymous (lab only) or Username and password and provide the credentials configured on the S7-1200 server.
6. Compile the project (Project tree > CPU > right-click > Compile > Software (only)) and download the configuration to the CPU. A reload of the program blocks is not sufficient; the OPC UA client engine is part of the system data and must be recompiled and downloaded.
7. Cold-restart the S7-1500 if the firmware prompts a restart after the configuration change.

After the configuration is downloaded, retest SFB OPC_UA_Connect. STATUS should return 16#0001 on success and OPC_UA_ConnectStatus should be 16#0000_0000.

6. Activating the OPC UA Server on the S7-1200

Although the reported error is on the S7-1500 client, the matching S7-1200 server configuration is worth verifying so a follow-up error does not surface after the client side is fixed.

1. Select the S7-1200 CPU in the project tree and open Properties > OPC UA > Server.
2. Enable "Activate OPC UA server".
3. Set the port (default 4840). Verify the S7-1500 PROFINET interface can route to that port on the S7-1200 IP — corporate firewalls or VLAN ACLs frequently drop port 4840.
4. Choose the security policy: None for lab work, Basic256Sha256 for production.
5. Compile, download and cold-restart the S7-1200.
6. Once the server is up, the endpoint URL passed to OPC_UA_Connect follows the OPC Foundation convention:

opc.tcp://<S7-1200 IP>:4840

The URL is transmitted inside the SFB call as a STRING parameter. Maximum accepted length is 4096 characters per the OPC UA binary protocol definition; in practice, 30–60 characters is the typical form. Anything longer triggers Bad_TcpEndpointUrlInvalid on the client side.

7. Endpoint URL Parsing and Transport Layer

The first packet an OPC UA client transmits is a HEL (Hello) message carrying the endpoint URL. The receiving server parses the URL, validates the host portion (DNS or IP), and either accepts the connection or replies with Bad_TcpEndpointUrlInvalid as defined in OPC UA Part 6 — 7.1 OPC UA Connection Protocol. The full set of pre-session error codes that can surface in OPC_UA_ConnectStatus on S7-1500 includes:

8. Security Certificate Exchange

Once the client interface is enabled, the next failure mode that commonly surfaces is a certificate trust error, because OPC UA mandates mutual authentication above SecurityPolicy = None. The S7-1500 generates its own OPC UA client certificate on first connection attempt; the S7-1200 generates its server certificate likewise.

8.1 Trusting the S7-1200 server certificate on the S7-1500

1. Open the S7-1200 online diagnostics in TIA Portal (Online & Diagnostics > Certificate manager) and export the OPC UA server certificate.
2. On the S7-1500 project, open CPU properties > OPC UA > Client > Trusted certificates and import the S7-1200 server certificate.
3. Alternatively, copy the certificate to the S7-1500's /opcua/certs folder via the Web server's "File browser" page or via S7 file functions.

8.2 Trusting the S7-1500 client certificate on the S7-1200

1. The S7-1500 auto-generates a self-signed client certificate. Export it from CPU properties > OPC UA > Client > Own certificates or from /opcua/certs.
2. Import the certificate into the S7-1200 OPC UA > Server > Trusted certificates list.

9. SFB OPC_UA_Connect Reference

The SFB is the entry point of every OPC UA call sequence on the S7-1500. Its input / output interface (LAD / FBD / SCL):

Recommended SCL call skeleton:

// Rising edge of REQ starts the job
IF i_StartConnect AND NOT i_ConnectBusy THEN
    "db_OpcUa".OPC_UA_Connect(REQ := TRUE,
                                 ID := 16#0001,
                                 ServerEndpointUrl := 'opc.tcp://192.168.0.10:4840',
                                 SecurityPolicy := 0,
                                 Timeout := T#20s);
END_IF;

// Status evaluation
IF "db_OpcUa".OPC_UA_Connect.DONE THEN
    // Connected
END_IF;
IF "db_OpcUa".OPC_UA_Connect.ERROR THEN
    i_Status := "db_OpcUa".OPC_UA_Connect.STATUS;
    dw_SubStatus := "db_OpcUa".OPC_UA_Connect.OPC_UA_ConnectStatus;
END_IF;

10. Verification Procedure

After the client checkbox is set and the configuration is downloaded, verify the connection without leaving TIA Portal.

1. Go online with the S7-1500. Online & Diagnostics > OPC UA > Client connections lists active sessions.
2. Open a watch table that includes the OPC UA instance DB. Trigger REQ and observe BUSY, DONE, ERROR, STATUS and OPC_UA_ConnectStatus.
3. Confirm STATUS = 16#0001 and OPC_UA_ConnectStatus = 16#0000_0000 after a few seconds.
4. If a status trace is required, record the instance DB over 30 seconds with the S7-1500 Trace function and mark the rising edge of DONE.
5. From an external client (UaExpert), connect to opc.tcp://<S7-1500 IP>:4840 to verify the S7-1500 server (if it is also acting as a server).

Diagnostic flow chart

11. Common Edge Cases and Field Pitfalls

12. FAQ