Releases: RaaLabs/Connectors.OPCUA
Releases · RaaLabs/Connectors.OPCUA
Release v2.0.1
Summary
Remove trivy scanner from dotnet action.
Release v2.0.0
Summary
Smaller improvements for the Opcua Connector.
- The connector can now both read and subscribe to nodes, configurable from the configuration file
- Certificates are not supported anymore
Release v1.2.0
Summary
Adapt connector to work with certificates.
- Added function to verify server certificate from the OPC UA server
- Application creates a self-signed certificate that can be used to establish trust with the server
- Update to dotnet 8
- Use editorconfig and implement feedback
Release v1.1.2
Summary
- Update Opc.Ua dependencies
Release v1.1.1
Summary
- Update RaaLabs edge framework to 1.16.1
Release v1.1.0
Summary
- Update to dotnet 7 & framework 1.13.6
- Add batching config
- Add metrics
- upgraded workflows
- Update Nuget packages & removed unused referenes
Release v1.0.0
Summary
First edition of the OPC UA connector, using the OPC UA package from the OPC foundation (https://opcfoundation.github.io/UA-.NETStandard/). This package is to my knowledge the only maintained and open source C# nuget package for working with OPC UA servers.
Largely based on their reference client found here: https://github.com/OPCFoundation/UA-.NETStandard/blob/master/Applications/ConsoleReferenceClient/UAClient.cs
Added
- GPL 2.0 license (because the opc foundation requires that if we use their SDK, we also need to opensource the code before using it), this repo cannot be MIT because of their license
OPCUAClient
class, with functionality to connect, read and disconnect from a OPC UA serverOPCUAConfiguration
class, which consists ofserverUrl
andnodeIds
, this might need to be tweaked, as we start using it, it works well with the Prosys OPC UA simulation serverOPCUAConnector
class, which creates an instance ofOPCClient
and connects to the server from the config , and reads the values for the nodes in the config- Currently no security, even though OPC UA supports authentication and authorization between clients and server. This is something to look into, but for our early development not required.
I added a link in the readme to download the Prosys OPC UC simulation server, which can be used to test this connector locally.
I know you're on holiday, this is not urgent at all.