OPC UA PubSub is an extension to OPC UA that enables communication between OPC UA applications using a Publish-Subscribe message pattern instead of the Request-Response message pattern. The Publish-Subscribe message pattern decouples senders of messages from their receivers which allows for the development if systems based on middleware such as an MQTT broker. The difference between the two patterns is illustrated in the following figure:
The Publish-Subscribe message pattern is a powerful tool for factory owners that want to collect data from large numbers of publishers. In particular, it is a technology that is well suited for publishing factory data to the cloud. Publish-Subscribe is not well suited for use cases, such as device configuration, where a Client is blocked until it receives information back from the Server. OPC UA supports both message patterns because it is the best way to meet the complex needs of modern factories.
The purpose of this starter is to provide a bare bones implementation of OPC UA PubSub which illustrates the following:
- Implementing OPC UA PubSub is easy to do using standard Open-source libraries;
- OPC UA PubSub allows Subscribers discover Publishers and metadata about what they are publishing;
- How to integrating OPC UA PubSub with OPC Client-Server.
| Date | Changes |
|---|---|
| 2021-12-01 | Added command line arguments to set MQTT broker username/password. |
| 2022-07-30 | Major update to support the draft topics defined by the specification and support for actions and binary data. |
| 2023-11-06 | Major update to support the 1.05.03 version of the specification. Features that have not been released have been removed for now. |
The code in this repository is covered under the MIT license, however, some of the applications link to the UA-.NETStandard project which is has a dual license model. Note that Quickstarts 001 through 003 do not use the UA-.NETStandard stack and show how to implement a basic PubSub application using only MIT licenced code.
This code is developed as a learning tool and is missing some of the features that a commercial product would require, such as robust error handling.
This StarterKit contains software designed to run on a Raspberry Pi or other Linux device with GPIO ports.
It will also run on a Linux or Windows machine without GPIO ports in simulation mode.
This version of StarterKit uses .NET 6.0.
The recommended development tool to build for the Raspberry Pi is Visual Studio Code
The recommended development tool to build for Windows platforms is Visual Studio 2022.
An MQTT broker is required. Eclipse Mosquitto is used in the StarterKit documentation.
A MQTT monitoring application, such as MQTT Spy, is also helpful.
All of the code and documentation can be found on GitHub.
-
Setting up the Build Environment
1.1 Linux
1.2 Raspberry Pi with a Windows Development Environment -
Quickstarts
2.1 Building a Simple Publisher and Subscriber
2.2 Describing the Content of Data Messages
2.3 Using Connection Metadata to discover Message Structure
2.4 Acquiring Data from an OPC UA Server
2.5 Handling Multiple Header Profiles -
Complete Applications
3.1 Publisher
3.2 Subscriber
