What OPC UA actually is
OPC UA is not a fieldbus and not a broker. This course places it precisely: what it moves that other protocols do not, where it sits between the PLC and the MES, and how the specification is numbered, which is the first thing that confuses everyone.
| Lessons | 8 |
|---|---|
| Time | about 62 minutes |
| Prerequisites | None |
| Cost | Free: written lessons open, video and labs need a free account |
What you will be able to do
- You can explain OPC UA to a colleague in two minutes without saying 'Industry 4.0'.
- You can read a specification reference like OPC 10000-4 and know what document it names.
- You can say what a version like 1.05.07 does and does not guarantee about interoperability.
- You can place OPC UA against MQTT, Modbus and PROFINET without treating them as rivals.
Syllabus
-
1
Read the problem OPC UA was built to solve7 min
Twelve vendors, twelve dialects, and integration as bespoke engineering every time. What that actually costs on a shop floor, and what a self-describing protocol changes.
Asset A table of six real machine protocols with what each one carries and what it omits
-
2
See what OPC UA moves that a byte protocol does not8 min
The same pressure reading over Modbus and over OPC UA, side by side: a register number versus a typed, named, ranged, timestamped value with a status.
Asset A screenshot of the same value in a Modbus poller and in UaExpert, with both payloads written out
-
3
Place OPC UA in the stack6 min
Fieldbus below, unified namespace and MES above. Why OPC UA is the semantic layer and not the cheapest transport, and why that trade is usually right and sometimes wrong.
Asset A layer diagram naming real products at each level, with the protocol on each boundary
-
4
Decode the three numbering schemes7 min
OPC 10000-4, IEC 62541-4 and 'Part 4' are one document. Companion specs use other series entirely. This lesson makes every later reference readable.
Asset A conversion table between the three schemes plus the companion-spec series, with real examples
-
5
Read a version number correctly6 min
1.05 is a release family; the fourth digit is an errata level. Why 'we support 1.05' is not an interoperability statement, and what to ask a vendor instead.
Asset The published nodeset release dates for 1.05.04 through 1.05.07, with what changed between them
-
6
Tell client-server from PubSub before you need either8 min
Two communication models in one standard. What each is for, and the fact that most plants never need PubSub at all.
Asset A decision table mapping eight real data flows to the model that fits
-
7
Meet the free servers you will use all course9 min
Three public OPC UA servers and three one-command local ones. Connect to one now and see an address space, before learning any theory.
Asset Working connection to opc.tcp://opcua.umati.app:4840 in UaExpert, with the browse tree screenshotted
-
8
Know what OPC UA does not do11 min
It is not real-time by default, not a database, not a scheduler, and it will not give you planned production time. Naming the boundaries now prevents a bad architecture later.
Asset A list of five things teams routinely expect OPC UA to provide, and where each actually comes from
Lab
Free account required
Connect to opc.tcp://opcua.umati.app:4840 with UaExpert or opcua-commander, find the Machines folder, and write down three things the server tells you about itself that a Modbus device could not.
Unlock the lab →Last verified 7 September 2026 against OPC UA 1.05.07. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.