FAQ | Frequently Asked Questions: PLCcom OPC UA SDK
Welcome to our FAQ section for the PLCcom OPC UA SDK
Here you will find answers to the most frequently asked questions about our software. Whether technical details, installation aids or use cases - we have compiled the most important information for you to make accessing Opc Ua Funktionalitäten mit PLCcom so einfach wie möglich zu machen.
The PLCcom OPC UA SDK is available for .NET and Java.
The .NET version supports classic .NET Framework applications from .NET Framework 4.7.2, .NET Standard 2.1, as well as .NET 6, .NET 7, .NET 8, .NET 9 and .NET 10.
The Java version has been tested and approved for Java 8 through Java 26. It also works with OpenJDK-based runtime environments.
It can be used in 32-bit and 64-bit environments. Depending on the version, integration is handled via NuGet or Maven.
Depending on the version, integration is handled via NuGet or Maven.
For .NET projects, the SDK can be integrated directly as a NuGet package. For Java projects, the SDK is available via Maven Central.
This makes the SDK a direct part of your own application. Additional external API layers, COM registrations or manually copying libraries into Java runtime directories are not required.
You can find the current packages here:
NuGet:
https://www.nuget.org/packages/PLCcom.Opc.Ua.Sdk
Maven Central:
https://central.sonatype.com/artifact/com.indi-an.plccom/plccom-opc-ua-sdk
Yes. Depending on the version, the PLCcom OPC UA SDK is a 100% .NET or Java library and is integrated directly into your own application.
Additional external API layers, COM registrations or native wrapper constructions are not required. This keeps integration straightforward and the project structure clean.
Yes. The PLCcom OPC UA SDK can be used in 32-bit and 64-bit environments.
The PLCcom OPC UA SDK is designed for OPC UA.
With the client part, you can connect to OPC UA servers. With the server part, you can provide your own OPC UA servers in .NET or Java applications.
Classic DCOM-based OPC interfaces such as OPC DA, OPC AE or OPC HDAare not supported directly.
The OPC UA endpoints must be reachable within the network. Depending on the transport and configuration, this may include firewall rules, open ports, hostnames, IP addresses and certificates.
The PLCcom OPC UA SDK supports the common OPC UA communication options. It is important that client and server can reach the same endpoint and that the certificates used are trusted by both sides.
If direct connections are not possible or not desired, Reverse Connect can be used depending on the scenario.
The current documentation for the PLCcom OPC UA SDK is available in the online help for .NET and Java.
In addition, extensive workshop repositories for .NET and Java are available on GitHub. They include runnable examples for typical client and server scenarios, such as connecting, reading, writing, monitoring, methods, alarms, historical data, Reverse Connect and custom server functions.
The PLCcom OPC UA SDK is available as a Freelancer & Single-User License or as a Company License.
The Freelancer & Single-User License is intended for freelancers, self-employed developers and companies with exactly one developing user. It is not intended for teams, departments or multiple developers within a company.
The Company License is intended for companies, teams and departments with multiple developing users. It is required as soon as more than one person uses the library for development, build, testing or debugging.
Applications created with the SDK can be delivered and operated without additional runtime licenses. This means the license is required for development, not for every later installation of your application.
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.
Yes. You can test the PLCcom OPC UA SDK before purchasing with a 14-day trial version.
This allows you to check whether the SDK technically fits your project – including integration, client and server functions, examples and documentation.
The license is passed directly to the PLCcom OPC UA SDK in code. For this, the licensee/user and the serial number are set in the application.
A separate runtime installation is not required. Licensing examples are available in the documentation and in the workshop projects.
As soon as more than one person uses the library for development, build, testing or debugging, a Company License is required.
The Freelancer & Single-User License is only intended for freelancers, self-employed developers and companies with exactly one developing user. It is not intended for teams, departments or multiple developers within a company.
No. The PLCcom OPC UA SDK license itself may not be passed on or transferred to customers.
However, you may deliver applications that you have developed with the SDK to your customers. No additional runtime licenses are required for these applications.
The SDK license is intended for development, build, testing and debugging with the library.
Yes, we are happy to support requests for non-commercial educational purposes. Just contact us if you would like to use the PLCcom OPC UA SDK in a school, university, training course or similar educational environment.
Briefly describe the context in which the SDK is intended to be used. In most cases, we will find a suitable solution.
The data provided during registration, trial license request or purchase is processed and stored by us in accordance with the GDPR. We use this data to process your request, provide the license, handle the contractual relationship and manage the related communication.
The data is retained only for as long as required for these purposes or as long as statutory retention obligations apply. After that, it is deleted unless there is another legal basis for processing.
Further information can be found in our privacy policy.
