OPC UA · S7-1500 SERVER · SCADA & PYTHON CLIENTS · MQTT EDGE GATEWAY
A hands-on OPC UA course for engineers who have to get plant data out of the controller safely. Configure the S7-1500 OPC UA server in TIA Portal with the right endpoint, security policy and certificate trust, expose the correct tags, then connect real clients — a WinCC Explorer SCADA station and a Python client that stores values in SQL Server. Finish by bridging OPC UA to MQTT through an edge gateway and deciding, per requirement, when OPC UA, MQTT or a REST API is the right route.
Classroom day batches · Online 7:30 PM–9:00 PM · Sunday 11:00 AM–5:00 PM
See the software, protocol stack and practical engineering topics used at each stage of the OPC UA training path. Select a module to view exactly what you will work with.
Training progression: Module 01 secures and verifies the server side, Module 02 connects SCADA, Python and web API clients to it, Module 03 bridges the data outward through an MQTT edge gateway, and Module 04 places the whole path in an IT/OT project with a clear rule for choosing OPC UA, MQTT or REST.
View Detailed OPC UA Training Contents →The OPC UA course is organised as four practical modules covering 11 hands-on IT/OT integration topics. Every topic below is a written lab you can open before or after the session — from server configuration and security through SCADA and Python clients to the MQTT edge gateway and REST API integration.
Start at the source: enable and configure the OPC UA server on the S7-1500, decide endpoints, security policy and user access, expose the right tags, then prove the traffic is really flowing.
Enable the server, set the port and endpoint, choose the security policy and user access, publish the tags and confirm them with a test client.
View training topic →02Capture and read the traffic on the line so a failed session, refused endpoint or certificate problem is diagnosed from evidence, not guesswork.
View training topic →Connect real clients to the server: a WinCC Explorer SCADA station, a Python client that stores values in SQL Server, and the S7-1500 web API route so you can judge when OPC UA is the right choice.
Add the OPC UA channel in WinCC Explorer, trust the certificate, browse the namespace and bring live process values onto the SCADA screen.
View training topic →02Write a Python client that connects, browses node IDs, subscribes to value changes and inserts the data into SQL Server with proper error handling.
View training topic →03Use the S7-1500 web API alongside OPC UA and compare the two routes on setup effort, security, performance and what each is actually good for.
View training topic →Take plant data outward: bridge OPC UA to MQTT through an edge gateway, run a broker, design JSON payloads and topics, and subscribe from Python so the data reaches dashboards and databases.
Map OPC UA nodes to MQTT topics through an edge gateway, publish to the broker and keep the SCADA station reading the same data.
View training topic →02Publish directly from the PLC with the LMQTT client, set up the broker, and work with topics, QoS and retained messages.
View training topic →03Subscribe and publish from Python, parse JSON payloads, and move broker data into SQL Server or a dashboard reliably.
View training topic →Place OPC UA in the wider IT/OT picture: where MQTT and REST API fit, how the protocols are chosen per requirement, and how the full data path is delivered as a working Industry 4.0 project.
Build and consume REST endpoints in Python so plant data can be exchanged with ERP, MES and web applications.
View training topic →02The dedicated MQTT program that follows this course for teams whose data path is broker-based rather than client-server.
View training topic →03The dedicated REST API program for teams integrating plant data with business systems and web dashboards.
View training topic →OPC UA is a vendor-neutral industrial communication standard that lets controllers, SCADA, MES and IT applications exchange structured data securely over Ethernet. It replaces vendor-specific drivers with one browsable address space, built-in security and a data model that keeps meaning attached to the values.
The S7-1500 OPC UA server configured in TIA Portal is the main platform, with WinCC Explorer, a Python client and a test client such as UaExpert on the client side. The concepts apply to any compliant OPC UA server you may have from another vendor.
Yes, in detail. Endpoints and discovery, security policies and message modes, server and client certificate trust, anonymous versus user authentication, and what has to be agreed with the IT team before a server is opened up are all part of the first module.
Siemens requires an OPC UA runtime licence on the CPU for production use, and this is explained honestly in the sessions so there is no surprise at commissioning. Live demonstrations run on a licensed CPU, and client-side work can be practised against simulation and test servers.
A WinCC Explorer SCADA client that brings live values onto the plant screen, and a Python client that browses node IDs, subscribes to value changes and writes the data into SQL Server with error handling and reconnection.
Yes. A working OPC UA to MQTT edge gateway is built, together with broker setup, topic and QoS design, JSON payload structure and a Python subscriber, because most plant data paths today use both protocols rather than one.
Through a repeatable sequence: endpoint and discovery errors, certificate trust on both sides, user credentials, namespace and node ID mismatches, subscription load, and packet capture with Wireshark when the logs alone are not conclusive.
Automation and SCADA engineers moving into IT/OT integration, PLC programmers asked to expose plant data, system integrators building Industry 4.0 projects, and IT engineers who need to consume controller data safely.
Classroom sessions run in the day batches and live online sessions run from 7:30 PM to 9:00 PM on weekdays, with a Sunday batch from 11:00 AM to 5:00 PM. Corporate and in-plant groups can request a different schedule.
Send your requirement for OPC UA training. Mention your controller and TIA Portal version, the client side you need (SCADA, Python, MES or a broker), and whether the data path has to cross into the IT network, so the labs match your integration. Online batch runs 7:30 PM to 9:00 PM on weekdays and 11:00 AM to 5:00 PM on Sunday.
Explore the four modules, server licence and security requirements, the client stack used in the labs and classroom or online batch options.
Content reviewed: 18 September 2026