PLCcom OPC UA Toolkit

PLCcom OPC UA Clienttoolkit

The PLCcom.OPC.UA.Toolkit is a highly optimized and modern component specially developed for .NET software developers to provide a convenient access to a client-side OPC UA interface, e.g. To read or write data.

Innovative and quick

With the PLCcom.OPC.UA.Toolkit you will be able to add a standardized OPC.UA client access to their developed applications with a few lines of code. Connect you application quick and easy with one or more OPC-UA-Server(s) and read, write or monitore data. Make you application fit for Industrial 4.0

Find some easy examples below (more examples):

Example: Queries of existing endpoints of a server
  • C#
  • Visual Basic
//discovery over discovery server
 string[] Endpoints = OpcUaClient.GetDiscoveryUrls(Hostname);
'discovery over discovery server
 Dim Endpoints As String() = OpcUaClient.GetDiscoveryUrls(Hostname)

Example: Queries of existing endpoints of a server

Example: Browse nodes
  • C#
  • Visual Basic
//simple browse command example
 ReferenceDescriptionCollection rc = client.Browse("Objects.Server");
'simple browse command example
 Dim rc As ReferenceDescriptionCollection = client.Browse("Objects.Server")

Example: Browse nodes

Example: Read data
  • C#
  • Visual Basic
//read values from OPC UA Node into DataValue object
 DataValue value = client.ReadValue("Objects.Server.Data.Static.Scalar.Int64Value");
'reading values from OPC UA Node into DataValue object
 Dim value As DataValue = client.ReadValue("Objects.Server.Data.Static.Scalar.Int64Value")

Example: Read data

Example: Write data
  • C#
  • Visual Basic
//write value 123 to OPC UA Node and receive the status code
 StatusCode sc = client.Write("Objects.Server.Data.Static.Scalar.Int64Value",123);
'writing value 123 to OPC UA Node and receive the status code
 Dim sc As StatusCode = client.Write("Objects.Server.Data.Static.Scalar.Int64Value", 123)

Example: Write data

Example: Monitore nodes
  • C#
  • Visual Basic
 //create and register monitoring item

 //catch the monitoring event
 private void Client_MonitorNotification(string Identifier, 
                                         MonitoredItem monitoredItem, 
                                         MonitoredItemNotificationEventArgs e)
        MonitoredItemNotification notification = 
                                e.NotificationValue as MonitoredItemNotification;
        Console.WriteLine(Identifier + " " + monitoredItem.StartNodeId + 
                          " Value: " + notification.Value + " Status: " + 
 'create and register monitoring item

 'catching the monitoring event
 Private Sub Client_MonitorNotification(Identifier As String,
                                        monitoredItem As MonitoredItem,
                                        e As MonitoredItemNotificationEventArgs)

     Dim notification As MonitoredItemNotification = 
                         TryCast(e.NotificationValue, MonitoredItemNotification)

     Console.WriteLine((Identifier & " " & monitoredItem.StartNodeId.ToString() &
                        " Value: ") & notification.Value.ToString() &
                        " Status: " & notification.Value.StatusCode.ToString())    
 End Sub

Example: Monitore nodes

Tutorial, test software and code examples

Included in the software package are extensive code examples and tutorials, which illustrate the easy connection of an OPC UA server via an OPC interface to your application and can also be used in your projects.
For development support, test server and client applications are included in the delivery package.


♦ finding nodes via node path e.g. "Objects.Server.Data.Static.Scalar.Int64Value"
♦ automatical connect and disconnect of server connections (can be switched off)
♦ no limits at instance, connections or subscription numbers
♦ compatible to OPC specification 1.02
♦ extanded security features, secure connection via certificate exchanges (possible)
♦ usable with .Net-Framework version 4.5.2 or higher
♦ and many more

Especially for DotNet developers

Depending on the version, the libraries are 100% .Net files. The component can be directly linked as a reference, API calls are not necessary.
It is easily to use the components in 32 or 64 bit environments as well as across platforms.
The internal routines are optimized for high-performance access.

Easy lisencing, top level support

PLCcom.OpcUa.Toolkit needs a license for each developer a runtime license is not necessary.
Try PLCcom.OpcUa.Toolkit 30 days test version, before licening.
After purchase we are not going to leave you alone.
If you have any problems or questions regarding our product do not hasitate to contact us. We will support you by finding a solution.

Indi.Systems is OPC foundation member for many years

langjähriges Mitglied der OPC-Foundation

With the OPC UA specification, the OPC Foundation provides a newly developed communication model for the uniform transport of machine data.
The goal was to adapt the OPC communication model to the requirements of future applications and to compensate for the existing disadvantages of the DCOM-based OPC interface.
The first version of the OPC UA specification was made available in 2006, a revision took place in 2009.

With OPC UA, a future-proof standardized communication standard is provided that also covers the requirements of industry 4.0 applications.

Indi.Systems is OPC foundation member for many years

OPC Client Toolkits



Single developer license *

€ 799,00 (excl. taxes)

Info plus 19% VAT 151,81 €

€ 950,81 (incl. taxes)


Company license **

€ 2290,00 (excl. taxes)

Info plus 19% VAT 435,10 €

€ 2725,10 (incl. taxes)

*License for one developer plus 1 year Top-Level-Support*** + complimentary updates and upgrades.

**Company license for enterprises up to 300 employees plus 1 year Top-Level-Support*** + complimentary updates and upgrades. If you are interested in a company license for a company with more than 300 employees give us a brief information via E-Mail. We will sent you a special offer for that purpose.

***Top-level support: Support requests via mail / phone (in German or English), which are processed with high priority. Maximum 2 business days response, usually processed immediately.