It has been a while since the last blog post covering Qt OPC UA news. This short update will outline what we have primarily worked on in 2022.
basysKom supported the WEINIG Group during the development and implementation of the WWCS while using OPC UA and the open62541 stack: a customer showcase.
Over the last months basysKom contributed a number of improvements to the OpenAPI Generator project. OpenAPI as a standard provides a structured way to define, implement, test and maintain REST-like APIs.
The umati community did its first open source release of the “umati Dashboard OPC UA Client”. To support this effort basysKom has worked with the umati community and ported the client to the open62541 OPC UA stack.
Companion specifications complement OPC UA with the goal of fostering interoperability. This article will provide an overview about implementing a Companion Specification with open62541.
So far programs using Qt OPC UA with the open62541 back-end produced quite a bit of chatter on stdout originating from the open62541 stack itself. Unfortunately there was no simple way to get rid of these low-level logs. We now provide a way to control this behavior.
The Qt OPC UA module has been ported to CMake and will be part of Qt 6 right from the first release.
In addition to numerous bug fixes and improved test coverage, the open62541 plugin has been updated to open62541 v1.1 and uses OpenSSL for security support, thus removing the dependency on mbedTLS.
Getrieben durch Themen wie Industrie 4.0 und IoT hat sich OPC UA als durchgängiger Kommunikationsstandard im Maschinenbau und in der Industrieautomatisierung etabliert. Mit Qt steht
Qt OPC UA is not included in the Qt installer and must be built from source. The open62541 backend is currently the most stable and feature
OPC UA is a central element of the Industry 4.0 story providing seamless communication between IT and industrial production systems. basysKom has initiated Qt OPC
