mirror of
https://github.com/OPCFoundation/UA-.NETStandard.git
synced 2026-10-27 21:55:54 +08:00
* add the Aes128 and Aes256 profiles * Aes profies were tested on IoP workshop against Ascolab, Softing, Matrikon, Milo, ProSys and others * Pss padding is not supported on all platforms, so autodetect if it is supported and filter out Aes256 if not * not a breaking change: not specifying the SecurityProfileUri in the config xml will automatically add all supported profiles but not deprecated profiles (e.g. Basic256Sha256, Aes128, Aes256). Aes256 is only added if the platform supports Pss padding. This will simplify the maintenance of config xml, since automatically all supported and secure profiles are exposed.
OPC Foundation UA .Net Standard Library COM Server Wrapper
Introduction
This OPC UA COM Server Wrapper is designed to map OPC Classic server information to OPC UA to help vendors migrate to OPC UA based systems while still being able to access information from existing OPC Classic systems. For more information please refer of the OPC Unified Architecture specification:
- for OPC Data Access (DA) refer to the OPC UA specification, Part 8: Data Access, ANNEX A
- for OPC Alarms and Events (AE) refer to the OPC UA specification, Part 9: Alarms & Conditions, ANNEX D
- for OPC Historical Data Access (HDA) refer to the OPC UA specification, Part 11: Historical Access, ANNEX A
How to build and run the Windows OPC COM Server Wrapper
- Start the OPC Classic Server.
- Open the solution UA COM Interop.sln with VisualStudio.
- Choose the UA COM Server Wrapper project in the Solution Explorer and set it with a right click as
Startup Project. - Enter the
ServerUrlfor the OPC Classic Server DA, AE and HDA connection in the configuration file: Opc.Ua.ComServerWrapper.Config.xml. - Hit
F5to build and execute the sample. - Connect to the UA COM Server Wrapper with a OPC UA Client to access the namespace of the OPC Classic Server.