EPICS Device Support module for interfacing to the OPC UA protocol. The architecture allows supporting different implementations of the low level client library.
Linux and Windows builds are supported.
There are two choices for the low-level OPC UA client library:
-
The commercially available Unified Automation C++ Based OPC UA Client SDK. Original, full implementation.
-
The open source client implementation of the open62541 project. Currently experimental, no support for structured data yet.
-
A C++ compiler that supports the C++11 standard.
Microsoft Visual C++ needs to be from Visual Studio 2015 or newer. g++ needs to be 4.6 or above. -
EPICS Base 3.15 (>= 3.15.7) or EPICS 7 (>= 7.0.4).
-
The gtest module if you want to compile and run the Google Test based unit tests.
-
Unified Automation C++ Based OPC UA Client SDK (1.5/1.6/1.7 are supported, as well as their evaluation bundles; 1.8 is having trouble).
-
For OPC UA security support (authentication/encryption), you need openssl/libcrypto on your system - both when compiling the SDK and when generating any binaries (IOCs).
-
In
CONFIG_SITE.local
, setUASDK
to the path of the SDK installation. -
For more details, refer to the
README.md
in thedevOpcuaSup/UaSdk
directory.
-
The open62541 SDK is available at https://open62541.org/
Choose a recent release (1.2 and 1.3 are supported). -
For OPC UA security support (authentication/encryption), you need openssl/libcrypto on your system - both when compiling the SDK and when generating any binaries (IOCs).
-
In
CONFIG_SITE.local
, setOPEN62541
to the path of the SDK installation. -
For more details, refer to the
README.md
in thedevOpcuaSup/open62541
directory.
This is a standard EPICS module.
Inside the configure
subdirectory or one level above the TOP location
(TOP is where this README file resides), create a file RELEASE.local
that sets EPICS_BASE
and GTEST
to the absolute paths inside your EPICS
installation. The GTEST
module is needed to compile and run the tests.
Not defining it produces a clean build, but without any tests.
Configure the compiler on Linux to use the C++11 standard by adding
USR_CXXFLAGS_Linux += -std=c++11
to the CONFIG_SITE
file (or one of the host/target specific site
configuration files).
It is preferable to set this option globally in EPICS Base.
The configuration necessary when building against a specific client library
is documented in the README.md
file inside the respective subdirectory of
devOpcuaSup
.
IOC applications that use the module need to
- add an entry to the Device Support module in their
RELEASE.local
file - include
opcua.dbd
when building the IOC's DBD file - include
opcua
in the support libraries for the IOC binary.
Sparse.
The documentation folder of the Device Support module contains the Requirements Specification (SRS) giving an introduction and the list of requirements that should convey a good idea of the planned features.
The Cheat Sheet explains the configuration in the startup script and the database links.
Please look at the "Assets" sections of specific releases on the release page for binaries. These are fully functional and contain the Unified Automation Client SDK. They can be used without limitations and without any fees.
Please use the GitHub project's issue tracker.
This module is based on extensive prototype work by Bernhard Kuner (HZB/BESSY) and uses ideas and code snippets from Michael Davidsaver (Osprey DCS).
The support for the open62541 client was added by Dirk Zimoch (PSI) with additional help from Carsten Winkler (HZB/BESSY).
This module is distributed subject to a Software License Agreement found in file LICENSE that is included with this distribution.