PLCcom OPC UA Client + Server SDK
Get up and running faster with OPC UA in .NET and Java.
The PLCcom OPC UA SDK is a 100% .NET- bzw. Java-Library for OPC UA client and server applications.
It was developed to take work off software developers’ hands that would otherwise quickly consume a lot of project time in a clean OPC UA integration: specification details, security, testing, stabilization and recurring implementation details.
The SDK provides everything you need for this: extensive prebuilt functionality, easy integration, from client to server and without additional runtime licenses.
Optionally available as an extension: PLCcom OPC UA PubSub Add-on.
This allows data to be distributed to multiple subscribers via publisher/subscriber communication –
e.g. for IIoT, edge or MQTT-based applications using a standardised industrial interface.
Functions that save time in your project
Easy to Use — Address Nodes by Path or NodeId
OPC UA nodes can be addressed classically using NodeIds.
That works too – but in code it often looks like this: ns=3;i=2024
With the PLCcom OPC UA SDK, nodes can also be addressed by their path in the address space: Objects.Plant.Line1.Machine1.Temperature
This makes applications more readable, easier to maintain and closer to the structure developers actually see in the OPC UA address space.
NodeId nodeId = client.GetNodeIdByPath(„Objects.Plant.Line1.Machine1.Temperature“);
DataValue value = client.ReadValue(nodeId);
client.WriteValue(nodeId, 23.5);
NodeId nodeId = client.getNodeIdByPath(„Objects.Plant.Line1.Machine1.Temperature“);
DataValue value = client.readValue(nodeId);
client.writeValue(nodeId, 23.5);
One library for client and server
Client and server are built on the same foundation. This keeps the API consistent, reduces onboarding effort and makes dependency management easier when both sides play a role in the project.
Client and server functions according to OPC UA 1.05
The PLCcom OPC UA SDK supports the OPC UA Specification 1.05 and provides an extensive and convenient range of functions for client and server applications. These include:
- Data Access – read, write, browse values and process attributes
- Subscriptions & Monitored Items – monitor value changes and events
- Methods – call OPC UA methods and provide them on the server side
- Events – subscribe to, trigger and process events historically
- Alarms & Conditions – alarm states, acknowledge, confirm and comments
- Historical Access – use historical data and historical events
- Structured Data Types – process structured data types and custom models
- Server-Adressraum & Node-Management – namespaces, dynamic nodes, NodeSet2 import and permissions down to node level
- Reverse Connect – enable connections in restricted network architectures
- Security & Certificates – signing, encryption, user authentication, PKI structure and flexible certificate validation
- Optional OPC UA PubSub add-on – publisher and subscriber applications for distributing machine data via UDP or MQTT, e.g. for IIoT, edge, and MQTT-based applications based on a standardized industrial interface.
Further details on functionality, platforms and licensing can be found in the Data Sheet.
Optional add-on: OPC UA PubSub (Publisher/Subscriber)
The PLCcom OPC UA PubSub add-on extends the SDK to include publisher/subscriber communication for distributing machine data to multiple subscribers – for example, for IIoT, edge and MQTT-based applications using a standardised industrial interface.
For .NET and Java
.NET SDK
For C# and VB.NET. The library can be integrated directly via NuGet and supports classic .NET Framework applications, .NET Standard 2.1, as well as .NET 6, .NET 7, .NET 8, .NET 9 and .NET 10.
Java SDK
For Java applications, for example with Eclipse, NetBeans or IntelliJ IDEA. Integration is handled via Maven. The Java SDK has been tested and approved for Java 8 through Java 26 and also works with OpenJDK-based runtime environments.
Direct integration
You can find the current packages directly on NuGet and Maven Central.
Technical details on platforms, supported versions and more can be found in the Data Sheet.
Workshops, examples and test software
Anyone who wants to try the SDK will find extensive workshop repositories for .NET and Java with runnable examples. They show typical client and server scenarios step by step – from establishing a connection, reading, writing and monitoring through to methods, alarms, historical data, Reverse Connect and custom server functions.
Documentation, test software and a trial license are also available. This makes it easy to check whether the SDK is technically suitable for your own project.
Licensing, maintenance and support
The PLCcom OPC UA SDK is licensed per developer or as a company license. Applications created with the SDK can be delivered and operated without additional runtime licenses.
The first year of the maintenance plan is already included with the purchase. During this period, you receive updates, bug fixes and major upgrades at no additional cost.
The maintenance plan can be renewed if desired. We will inform you in good time before it expires – there is no automatic renewal.
If questions come up, we are available. Not only before the purchase, but also afterwards – so the SDK can be used properly in your project.
Proven in QuickHMI. Available as an SDK.
The PLCcom OPC UA SDK grew out of our own product development. Back in 2012, we needed OPC UA communication for our HMI system QuickHMI that could be integrated cleanly into professional software, run reliably and remain maintainable over the long term.
That origin still shapes the SDK today: it is designed for integration, maintainability and stable operation – and as an integral part of QuickHMI, it is used in many projects worldwide. Anyone looking to integrate OPC UA into their own software gets a foundation that we have been using, maintaining and continuously improving ourselves for years.
Long-standing member of the OPC Foundation
Indi.An has been a member of the OPC Foundation for many years. OPC UA has not just recently become part of our product development; it has long been an integral part of our work on QuickHMI and PLCcom.
The SDK is continuously maintained and further developed. Experience from our own product development, support cases and specific customer requirements flows directly into its ongoing development.
SDK – Informations
