Baike.dev
All toolsAI codingTrendingOpen sourceNewsSubmit
Log in
< Back to tools
O

open62541

> 开发工具
Open source

Open source implementation of OPC UA (OPC Unified Architecture) aka IEC 62541 licensed under Mozilla Public License v2.0

3.2K stars0 likes0 views
WebsiteGitHub

About

Open source implementation of OPC UA (OPC Unified Architecture) aka IEC 62541 licensed under Mozilla Public License v2.0


open62541 (http://open62541.org) is an open source implementation of OPC UA (OPC Unified Architecture / IEC 62541) written in the C language. The library is usable with all major compilers and provides the necessary tools to implement dedicated OPC UA clients and servers, or to integrate OPC UA-based communication into existing applications. See the features overview for full details. The open62541 library is platform independent: All platform-specific functionality is implemented via exchangeable plugins for easy porting to different (embedded) targets.

open62541 is licensed under the Mozilla Public License v2.0 (MPLv2). This allows the open62541 library to be combined and distributed with any proprietary software. Only changes to the open62541 library itself need to be licensed under the MPLv2 when copied and distributed. Some plugins and examples are in the public domain (CC0 license) and some are licensed under MPLv2. The CC0 licensed ones can be reused under any license and changes do not have to be published.

The library is available in standard source and binary form. In addition, the single-file source distribution merges the entire library into a single .c and .h file that can be easily added to existing projects. Example server and client implementations can be found in the /examples directory or further down on this page.

Documentation and Support

A general introduction to OPC UA and the open62541 documentation can be found at http://open62541.org. Past releases of the library can be downloaded at https://github.com/open62541/open62541/releases.

The overall open62541 community handles public support requests on Github and the mailing list. For individual discussion and support, use the following channels:

  • Mailing List
  • Issue Tracker
  • Pull Requests

o6 Automation GmbH employs the core contributors to open62541 and provides commercial support. The project is however open to outside contributions and contributors retain their individual copyright. This prevents future relicensing under different license conditions.

We want to foster an open and welcoming community. Please take our code of conduct into regard.

Commercial Use

open62541 is licensed under the MPLv2. That is, changes to files under MPLv2 fall under the same open-source license. But the library can be combined with private development from separate files, also if a static binary is produced, without the license affecting the private files. See the full license document for details.

Official Certification

An example server built with open62541 v1.4 was certified for the 'Standard Server 2017 Profile' by the OPC Foundation. See https://open62541.org/certification for more details.

Build System, Code Structure and Dependencies

The build environment of open62541 is generated via CMake. See the build documentation for details. To simplify the integration with existing software projects, the open62541 sources can be compressed (amalgamated) into a single-file-distribution, a pair of open62541.c/.h files. The functionality included in the single-file-distribution depends on the current CMake configuration.

The source code is structured as follows:

  • Public API (/include): The public API is exposed to applications using open62541. The headers for plugin implementations are in /plugins/include.
  • Core Library (/src): The core library has no dependencies besides the C99 standard headers.
  • Architecture Support (/arch): Architecture support is implemented via the EventLoop plugin. This keeps the architecture-specific code - for example to use the POSIX APIs - out of the core library. Ports to different (embedded) architectures are provided.
  • Default Plugins Implementations (/plugins): The plugin interfaces allow the integration with different backend systems and libraries. For example concerning crypto primitives, storage of the information model, and so on. Default implementations are provided.
  • Dependencies (/deps): Some additional libraries are used via git submodules or have been internalized in the deps/ folder. More information on the third-party libraries and their respective licenses can be found in deps/README.md
  • Building and Code Generation: Some code is auto-generated from XML definitions that are part of the OPC UA standard. The code generation scripts use Python as part of the build process.

On most systems, a bare-bones open62541 requires the C standard library only. Depending on the build configuration, open62541 depends on additional libraries, such as mbedTLS or OpenSSL for encryption.

Development

As an open source project, new contributors are encouraged to help improve open62541. The file CONTRIBUTING.md aggregates good practices that we expect for code contributions. The following are good starting points for new contributors:

  • Report bugs
  • Improve the documentation
  • Work on issues marked as "good first issue"

For custom development that shall eventually become part of the open62541 library, please keep one of the core maintainers in the loop.

Code Quality

We emphasize code quality. The following quality metrics are continuously checked and are ensured to hold before an official release is made:

  • Zero errors indicated by the Compliance Testing Tool (CTT) of the OPC Foundation for the supported features
  • Zero compiler warnings from GCC/Clang/MSVC with very strict compilation flags
  • Zero issues indicated by unit tests (we target more than 80% code coverage)
  • Zero issues indicated by clang-analyzer, clang-tidy, cpp-check and the Codacy static code analysis tools
  • Zero unresolved issues from fuzzing the library in Google's oss-fuzz infrastructure
  • Zero issues indicated by Valgrind (Linux), DrMemory (Windows) and Clang AddressSanitizer / MemorySanitizer for the CTT tests, unit tests and fuzzing

Security and Vulnerability Handling

The project has established a process for handling vulnerabilities. See the SECURITY.md for details and how to responsibly disclose findings to the maintainers.

Installation and Examples

On Debian/Ubuntu systems, a simple apt install libopen62541-1.4-dev installs the library and the development header files. Using the GCC compiler, just run gcc -std=c99 <server.c> -lopen62541 -o server.

A more detailed explanation on how to install the open62541 SDK is given in our documentation. In essence, clone the repository and initialize all the submodules using git submodule update --init --recursive. Then use CMake to configure your build.

A complete list of examples can be found in the examples directory.

Example Server Implementation

…

Example Client Implementation

…

Issues· 830 open

View all issuesOpen on GitHub

No open issues yet, or sync has not completed.

> Tags

Ccclientiec-62541industrial-automation

No comments yet. Be the first to share.

> Details

PublishedAug 1, 2026
UpdatedSep 17, 2026
Category开发工具
PricingOpen source

> Related tools

V
VS Code
流行的开源代码编辑器
G
Git
分布式版本控制系统
V
Vite
下一代前端构建工具