OPC UA .NET SDK + OPC Classic

How to use

The OPC UA .NET SDK enables the development of OPC UA client and server applications according to OPC UA v1.03 and higher. The support of OPC Classic enables communication with OPC Classic Servers via OPC DA, OPC HDA and OPC AE. To implement a server, it is sufficient to define the data nodes (see below). The IP address and the transport protocol are defined with the default values "localhost:4840" and "opc.tcp". To establish a client connection, the server address together with the transport protocol scheme is sufficient (see below). To connect to an OPC Classic server, the ProgId and ClassId are also required. No membership in the OPC Foundation and no licence other than that for Traeger's SDK is required for development!

An OPC UA Server can be realised with just as few lines of code as an OPC UA Client. The OPC UA Server shown above provides a data node including the string value "Hello World!" The provision of the desired data nodes works without a multi-line "node setup". An OPC UA client which processes this data node is shown in the following example of an OPC UA client application.

Access to the respective data nodes works with the usual NodeId syntax (even after optional resolution via the Browse and Translate services). Any .NET language such as C#, VB.NET and C++/CLI can be used for programming. The interfaces themselves only differ in terms of the programming language used. For the connection to OPC Classic Server, the SDK must be used under Windows.

Advantages

• Free evaluation without registration
• Simple and fast development
• Industrial reliability
• API design according to Microsoft standards
• Royalty-free licences
• Qualified support
• Many code examples
• Regular updates
• No additional software required for OPC UA
• Usable without OPC Foundation membership

Characteristics

• Easy Node Access via BrowseName and NodeId
• Data Access with Methods, Subscriptions and Files
• Structured Data Types via Name-Value Paare, .NET Dynamic / Types
• Configuration via Code, XML-File or dynamic
• Alarms, Events and Conditions
• Security Policies: None, Sign & SignAndEncrypt
• Security Algorithm: None, Basic128Ras15, Basic256 & Basic256Sha256

OPC Classic API

• Data Client
• Alarm Client
• Event Client
• Historical Data Client
• Discovery Client

OPC UA API

• Data Client & Server
• Alarm Client & Server
• Event Client & Server
• Historical Data Client & Server
• Discovery Client & Server

OPC UA Profile

• Core Characteristics
• Generic Features
• Data Access (DA)
• Event Access (EA)
• Alarm & Condition (AC)
• Alarm & Events (AE)
• Historical Data Access (HDA)

Undecided?

Only OPC UA Client and Server need to be developed? The OPC UA SDK is also available without OPC Classic: OPC UA .NET SDK

Do you want to equip a component, control system or plant with an OPC UA server? This can be done quickly and easily without programming with our OPC UA middleware: Codabix Industrial IoT

The data of several OPC (UA) servers should be merged, retrievable via REST API, stored in a database, forwarded to other devices or simply visualised? Take a look at our OPC UA Middleware: Codabix Industrial Edge

Still undecided? We will be glad to advise you free of charge and without obligation: Contact us now!

Licensing

Our license options – as individual as your projects. Design your software development the way that suits you best. Whether subscription or lifetime – our license models offer you complete freedom, first-class support and continuous updates. Whether one-off or flexible – find the perfect solution for your vision. Find out more about our license models.