Connect WinCC Explorer to an S7-1500 OPC UA Server: Step-by-Step Lab

Start from a server that already works

Complete the S7-1500 OPC UA server lesson first. Keep its endpoint, namespace/NodeId mapping and security configuration beside you. The server runs on the CPU; WinCC Classic is the client in this exercise. This does not require turning WinCC into the source OPC UA server.

Confirm the OPC UA client channel is installed and supported in your WinCC release. The Siemens WinCC V7.5 connection example documents adding the OPC UA WinCC Channel in Tag Management and creating a connection. Its example connects WinCC computers; here the remote server is the separately verified S7-1500.

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 the WinCC connection

1. Open the training project in WinCC Explorer and open Tag Management.
2. Use the driver/channel addition workflow for your release and select OPC UA WinCC Channel. Do not configure an OPC DA connection by mistake.
3. Create a connection named U101_S71500_UA.
4. Configure the verified S7-1500 endpoint through the connection’s discovery/server settings.
5. Match the server security policy and message mode. Configure the intended user authentication separately from certificate trust.
6. Establish certificate trust on the relevant client/server sides using the release-specific certificate store procedure. Verify identities and clock validity instead of blindly accepting an unknown certificate.
7. Check the channel diagnostics before adding many tags. Resolve endpoint, trust and authentication failures at this stage.

The two certificate roles are easy to confuse: the client must trust the intended server, and the server may need to trust the client application certificate under the chosen configuration. A valid username does not fix a certificate mismatch.

Map the verified nodes to process tags

Browse/import or assign the actual nodes using the WinCC channel workflow for your release. Confirm each WinCC type matches the source. The member names above are the mapping intent, not literal NodeIds.

If these names already exist as internal tags from the graphics lab, replace the training source deliberately; do not create ambiguous duplicate names. Save a project backup and record which connections and tag references change.

Bind and verify the Graphics Designer picture

1. Open U101_Overview.pdl or create a small test picture with two output fields and pump state text.
2. Connect level and flow to their mapped WinCC tags and display the units.
3. Drive pump appearance from feedback/fault, not an operator request.
4. Configure the selected objects’ update behavior and the project’s bad-quality indication.
5. Activate the training Runtime and compare all values with the PLC watch table.
6. Inspect SampleSeq and the channel/tag quality to distinguish a frozen source from a disconnected channel.

An ordinary Boolean called DataValid is only as reliable as the logic that supplies it. The earlier P&ID lab’s internal helper is not a substitute for channel/tag-quality handling in this connected project.

Fault isolation and acceptance

• Server browser works, WinCC fails: compare the endpoint, client certificate, policy, credentials and channel configuration.
• Connection works, one tag fails: inspect the actual NodeId, namespace, source type and access rights.
• Value never changes: compare the PLC watch table and SampleSeq, then check object updating and mapping.
• Communication is lost: the picture must show invalid/unavailable data rather than a false stopped or zero state.
• Communication returns: values and quality recover without reassigning tags manually.

Deliver: a screenshot from your own Runtime, the five-tag mapping, channel settings with secrets omitted, and normal/loss/recovery test results. This website lesson supplies the procedure; it does not include a tested WinCC project file.