Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

Upgrading SLIK-DA OPC DA Server to also be an OPC UA Server

After I upgrade my SLIK-DA license to include OPC UA, how do I add the OPC UA functionality to my OPC Server?

How to add OPC UA to your SLIK-DA Application

1. After applying your new license, replace the old SLIK-DA control on the Form with a new instance of the SLIK-DA control.

  • Before deleting the old SLIK-DA control you must take note of the following properties: Name, AppID, CLSID, AppName, Description, ProgID and VendorName.
  • Remove the old SLIK-DA control from the form and delete the old reference to Interop.NDISLIKDA.
  • Save and shut down Visual Studio and re-open your Project.
  • Add the new SLIK-DA control to the form, and re-assign the following properties: Name, AppID, CLSID, AppName, Description, ProgID and VendorName.
  • Adding the new control will restore Interop.NDISLIKDA as a reference. Open the properties for this reference and set "Embed Interop Types" to False.
  • Go to the Properties of the SLIK-DA control and find the Events (Lightning Bolt Symbol). Make sure the Events of the control are properly tethered to the Events defined in your code.

2. Add a UA configuration .xml file to the executable directory.

  • Copy SLIKDAUAConfig.xml to the directory where your OPC Server executable resides. By default, this file will be located in C:\Program Files\Software Toolbox\SLIK-DA5\Redistributables.

3. Create a file structure to handle the UA security certificates.

  •  The installation of SLIK-DA5 includes a batch file (Add_PKI_dir_stucture.bat) that can be run to automatically create this file structure for you. This batch file is located at C:\Program Files\Software Toolbox\SLIK-DA5\Redistributables. To use the batch file, copy it to the directory where the server executable resides and then double-click on the file to run it.

4. Testing the connection with an OPC UA Client

  • The default End Point for your OPC UA Server is “opc.tcp://[NodeName]:59595”, where NodeName represents the PC where the OPC Server is running.  If the OPC Client and Server are on the same machine, then you can replace [NodeName] with localhost.
  • If you do not have an OPC UA Client to test with we have listed some below.