S7-1500 OPC UA Server in TIA Portal: Practical Configuration and Tag Test

Confirm the hardware and software combination

Use an S7-1500 CPU/firmware that supports the intended OPC UA server features and the matching TIA Portal version. Check the CPU-specific OPC UA runtime license requirement. Do not assume that enabling a checkbox proves licensing or that a generic PLC simulator exposes the same external OPC UA endpoint as the physical CPU.

Prepare the controller address, engineering workstation address, time settings, an OPC UA test client and a read-only user/role as appropriate to the project’s security model. Record the endpoint rather than assuming a fixed port. A common example is opc.tcp://192.168.10.10:4840, but use the configured value.

Lab scope: use an isolated training CPU/network, TIA Portal compatible with its firmware and a supported WinCC Classic release where required. Check the exact CPU order number, firmware, license and installed software before following configuration steps. Examples use read-only telemetry; no example writes a motor command. The addresses, tag names and values are teaching choices.

Create and document the training DB

In TIA Portal create a global DB named DB_IIoT and add these members. Use a training watch table to observe the values before configuring OPC UA. Set accessibility/exposure for the intended interface according to your TIA/CPU version; a member existing in a DB does not automatically mean it is exposed to every client.

Retain a controlled interface. Export only the telemetry needed for this lesson. Do not change block optimization or enable unrelated legacy communication options merely to make a browse attempt work.

Configure the server and its interface in TIA Portal

1. Select the CPU and open its properties. Locate the OPC UA server settings and enable the supported server function.
2. Record the configured network interface and endpoint. Check that the test client can reach that interface on the training network.
3. Configure a security policy and message mode supported by both ends; use signed/encrypted communication for the lab connection where available.
4. Configure the server certificate and the client-trust handling. Validate the certificate identity and time validity; handle client trust according to the selected policy.
5. Configure users/roles and give the test account only the required read access.
6. In the OPC UA server-interface configuration, expose the selected DB members or use the supported standard server interface with controlled tag access. Keep names understandable.
7. Compile and download the changed hardware/software configuration to the training CPU. Check diagnostics for server startup, certificate or license errors.

Siemens’ server-configuration example is the reference for this workflow. Exact property labels and interface choices vary with firmware/TIA release.

Browse rather than guessing a NodeId

1. Add the configured endpoint in the test client and inspect the presented server certificate.
2. Choose the matching security policy/mode and authenticate with the permitted user.
3. Browse to the exposed interface and locate LevelPct.
4. Record its NodeId, namespace URI, data type and access level. Namespace indexes can differ between servers or after configuration changes, so do not copy an arbitrary ns=3 from a tutorial.
5. Read the current value and status, then subscribe to changes using an interval suitable for the teaching sequence.
6. Change level in the training PLC and compare the client value with the watch table.

For each sample distinguish the value from its status/quality. A numeric value without current valid quality is not proof of a healthy communication path.

Run the connection tests

Deliver: the endpoint, namespace URI/NodeId mapping and test record. Do not move to the WinCC connection lesson until an independent client reads this interface reliably.