An OPC UA server supporting historical access allows clients to access historical data or historical events. Such a server can act as a process or event historian. open62541-based servers were till recently completely missing the ability to support these use cases. basysKom has extended the server API to support access to historical data using the "read raw" functionality specified in OPC UA part 11. This allows to create a simple process historian. This article provides an overview about this API and a short tutorial how to use it. Continue reading Initial support for servers with historical data access in open62541 at basysKom GmbH.
"OPC UA Reverse Connect" is a special connection mode in which the traditional roles of clients and servers during connection establishment are reversed - the server is responsible for initiating the connection to a client. This mode is intended for criti
zum Artikel gehenbasysKom recently extended this plugin to also accept PEM-based input. PEM is a file format used for certificates and keys which is specified by an RFC and is a preferred format for a lot of open source software. The pull request has been merged and our c
zum Artikel gehenThe 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 suppor
zum Artikel gehenThe open62541 OPC UA stack with its Pub-Sub extension now supports MQTT over TLS as well as MQTT-brokers requiring a login (contributed by basysKom). This allows the direct communication between open62541 and the Azure IoT Hub and therefore highly simplif
zum Artikel gehenQt 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 complete open source backend in Qt OPC UA. The open62541 library has minimal external dependencies and can be built
zum Artikel gehen