How-to
Connect an S7-1500 to SCADA over OPC UA from TIA Portal
Short answer
The S7-1500 has a built-in OPC UA server from firmware V2.0, deactivated by default. Enable it in the CPU device properties in TIA Portal, select the installed server license, copy the endpoint URL, and download. Paste the opc.tcp address into any OPC UA SCADA client, trust the certificates on both sides, then browse the PLC variables and map them to SCADA tags.
On this page
An S7-1500 needs no gateway and no extra card to feed an OPC UA SCADA: from firmware V2.0 the standard S7-1500 CPUs — and the F and T variants — carry a built-in OPC UA server, and it ships deactivated. The whole job is short: activate the server in the CPU device properties in TIA Portal, select the installed server license, copy the endpoint URL it displays, download, then paste that URL into any OPC UA client and browse PLC variables into SCADA tags. Because OPC UA is the IEC 62541 standard — one endpoint format, one subscription model, one certificate exchange — the client side is generic, and the procedure below is the same whatever SCADA package runs it.
What you need before you start #
- CPU firmware V2.0 or higher. Reads, writes and subscriptions are served from that version; OPC UA methods a client can call additionally need firmware V2.5 with TIA Portal V15.
- The server runtime license delivered with the CPU, because the configuration asks you to select it.
- A TIA Portal project that contains the CPU: the server is part of the device configuration, not something you switch on over the network.
- If clients reach the CPU through a CP 1543-1 instead of the CPU interface, the documented pairing is CPU firmware V2.8 or higher with CP 1543-1 firmware V2.2 or higher.
- For desk testing, S7-PLCSIM Advanced; plain S7-PLCSIM has no OPC UA server.
- TCP port 4840 permitted between client and CPU.
Enable the server in TIA Portal #
- Open the project, select the S7-1500 in the device view, and open the CPU device properties.
- Activate the OPC UA server — it is deactivated by default, so an as-delivered CPU serves nothing.
- Select the server license installed for this CPU.
- Choose the data-block variables the server exposes. The client can only browse what is mapped to the server, so keep the list to what SCADA uses, and keep client writes away from variables your interlock logic depends on.
- Copy the server address shown, character for character. A CPU at 192.168.0.10 serves an endpoint of the form opc.tcp://192.168.0.10:4840 — the IP here is illustrative; your address field builds the real one from the CPU address and port 4840.
Download, and desk testing on one PC #
- Save the project and download it to the CPU; the server starts with the CPU and listens on the endpoint.
- To test without hardware, start the simulated instance in S7-PLCSIM Advanced through the PLCSIM Virtual Ethernet Adapter TCP/IP access point, and download the project to that instance.
- Treat the simulated server as the real one from the client side. Do not substitute plain S7-PLCSIM: it provides no OPC UA server, and the client will find nothing to connect to.
Connect the SCADA client and map tags #
- On the client station — if that station is new, an industrial panel PC for the SCADA client is the machine-side computer for this job — create a new OPC UA connection.
- Paste the endpoint URL from TIA Portal without retyping it. One mistyped character is the most common reason a fresh connection stays dead.
- Work through the certificate exchange. With the default security policy the server and the client each present a certificate, and each side must trust the other before data flows; the controller-side half of that step is the one described for trusting the Citect OPC UA client certificate on a B&R PLC.
- Test the connection. A healthy client reports the endpoint as connected and lists the server namespace.
- Browse the PLC nodes and map the chosen variables to SCADA tags.
- Group the mapped tags by update rate, as the worked example below shows. Reads are the reliable half; when a mapped write does nothing, the causes behind why a SCADA write to a PLC real address fails silently apply to OPC UA as well.
Worked example: one screen's traffic #
Take an overview screen that maps 12 analog Real values and 24 discrete states: 36 tags on one subscription with a 500 ms publishing interval. Publishes per second: 1 ÷ 0.5 s = 2. Value updates per second at most: 36 tags × 2 publishes/s = 72 updates/s.
Twenty of those discretes are slow-moving states. Move them to a second subscription at 5000 ms: the fast group keeps 12 analog plus 4 fast discrete tags = 16 tags × 2 publishes/s = 32 updates/s, and the slow group adds 20 tags ÷ 5 s = 4 updates/s. Total: 36 updates/s, half of the single-subscription figure of 72, with the slow states still updating well inside an operator scan.
Decision: run two subscriptions by rate. The numbers are illustrative — they size wire traffic and client load, not a CPU limit — and at 36 updates/s you are nowhere near needing a second controller or a split server.
When the client will not connect #
- Confirm the server is activated and that the project holding that configuration is the one downloaded; the setting does nothing until download.
- Confirm the endpoint is pasted exactly, opc.tcp prefix and port intact. A URL that carries a hostname the client cannot resolve fails in its own way, the case covered by resolving OPC UA endpoint URL hostname errors on an S7-1500.
- Ping the CPU and confirm TCP 4840 is open on every firewall or routed segment between client and CPU; translated addresses are the subject of configuring OPC UA endpoint URL hostnames behind NAT.
- Confirm both certificates are trusted; a server that rejects the client certificate looks like a timeout from the client side.
- If this client reaches one S7-1500 and not a second, the fault is usually in the path, and troubleshooting a SCADA PC station that reaches only one S7-1500 walks that split.
Controllers with no built-in server #
Not every controller has this route. A controller with no native OPC UA server — an S7-200, for example — reaches SCADA through a separate server: a PC-based OPC UA server or a gateway appliance that speaks the controller's own protocol on one side and OPC UA on the other. The S7-1500 procedure above does not apply there; a built-in server is exactly what lets this CPU skip the middle box.
Questions asked
Which S7-1500 firmware and TIA Portal versions support the OPC UA server?
Every standard S7-1500 CPU from firmware V2.0 has the server, and the F and T variants carry it too. OPC UA methods that clients can call need firmware V2.5 together with TIA Portal V15. Reaching the server through a CP 1543-1 needs CPU firmware V2.8 and CP firmware V2.2. A CPU on firmware below V2.0, such as V1.5, has no server to configure in any TIA Portal version.
Can I test this without hardware?
Yes. Start the simulated CPU in S7-PLCSIM Advanced through the PLCSIM Virtual Ethernet Adapter access point, download the project to that instance, and point the client at it the same way. Plain S7-PLCSIM does not provide an OPC UA server, so a client scanning the PC for endpoints finds nothing there. The simulated server listens on port 4840 like the physical CPU.
Does the S7-1500 OPC UA server need a license?
Yes. Part of enabling the server is selecting the server runtime license delivered with the CPU, and the TIA Portal configuration step asks for it. The article number depends on the CPU and on what you expose, so take it from your license certificate rather than guessing. The SCADA client side needs no license from the controller vendor to talk OPC UA to the server.
The client connects but one tag will not update or accept a write. What should I check?
Check the data types first: a client writing a 32-bit float into a 64-bit LReal node, or an integer into a Real, fails quietly. Then confirm the variable is mapped to the server with write access, and that no PLC logic overwrites the value every scan. A write that disappears immediately is usually your own code, not the protocol.
What if the controller has no built-in OPC UA server?
Put the server beside it. A PC-based OPC UA server or a gateway appliance speaks the controller native protocol on one side and serves OPC UA to SCADA on the other; controllers such as the S7-200 have no native server, so that middle box is the standard route. Only controllers with a built-in server, like the S7-1500, skip it.