Client Development for OPC DA/AE/HDA
The OPC DA/AE/HDA Client .NET Standard offers a fast and easy access to the OPC Classic Client technology. Develop OPC compliant DA, AE and HDA Clients with C#/VB.NET for the .NET Standard 2.1 framework. Also supported are .NET 4.8, .NET 4.7.2 and .NET 4.6.2
The OPC DA/AE/HDA Client .NET Standard API defines classes which can be used to implement an OPC client capable to access OPC servers supporting different specifications with the same API. These classes manage client side state information; provide higher level abstractions for OPC tasks such as managing sessions and subscriptions or saving and restoring connection information for later use. The lower level API’s for OPC DA, OPC AE and OPC HDA defines classes which can be used to access OPC specification specific methods and properties.
The original products for OPC DA, OPC AE and OPC HDA are now getting moved to a dual license. Technosoftware GmbH provides different licenses depending on the component and on the ownership of a purchased license or sponsor status of the user of the sources. A single ZIP file or a single repository can contain multiple components where the sources have different license models. The valid license is in the header of each source file.
- OPC DA/AE/HDA core components follow a dual-license model:
- Owner of a purchased license or sponsor: RPL 1.5
enables Owner of a purchased license or sponsor to deploy their applications using the core component sources without being required to disclose the application code.
- Users that are not Owner of a purchased license or are not a sponsor: GPL 3.0
Based on the GPL 3.0 license terms these users must disclose their application code when using the core component sources.
- Samples and Utilities:
- All samples and most of the utilities are provided under the MIT license for everyone.