OPC DA Client Configuration

Example connection for KEPServerEX and TOPServer

The following steps show how to connect to KEPServerEX and TOPServer using the OPC DA client.

Step 1: Create the module: (Config => Modules => button to the left of Modules => New module)

Figure 17. New module creation

Step 2: Provide a name for the module (in this case OPCDAClient01), assign the module type (in this case OpcDaClient) and save the new configuration.

Figure 18. Configuring a new module as OpcDaClient

Step 3: Configure the log (usually the default values are sufficient). Save the log configuration.

Figure 19. Default log configuration

Step 4: Create the OPC DA connections. Each connection is an independent OPC DA client.

Figure 20. Creating a new OPC DA connection to a server

Step 5: Configure the OPC DA client to connect to KEPServerEX or TOPServer.

• Host: Enter the Hostname/IP address of the target OPC server. Empty means localhost.
• Server: Instance name of the target OPC server, also known as Prog ID. For KEPServer6 the instance name is Kepware.KEPServerEX.V6 and for KEPServerEX 5 the instance name is Kepware.KEPServerEX.V5. For TOPServer 6 the instance name is SWToolbox.TOPServer.V6 and for TOPServer 5 the instance name is SWToolbox.TOPServer.V5.

Save the configuration and select restart the module. Figure 21. OPC DA client configuration for connecting to KEPServerEX 6 in the same host

Step 6: Create a tag to connect to the OPC sever: Config => Tags => New Tag

Figure 22. New tag creation

Step 7: Configure the tag. All details regarding the communication should be configured in Source entry: 

• Source.Enabled: True
• Source.Module Type: OpcDaClient
• Source.Module name: OPCDAClient01 (the module created in previous steps)
• Source.Config.Client: KEPServerEX_local (the connection created in previous steps)
• Source.Config.Address: The tag ID in the OPC server. In this example, a valid tag ID would be Channel1.Device1.Tag1 since KEPServerEX is running the default configuration after installation.

Figure 23. New tag configuration

Step 8: The tag should now be available, displaying as good quality in the Real-Time display.

Figure 24. Tag value in real-time display

Example connection to Matrikon OPC Simulation

The following steps show how to connect to Matrikon OPC simulation using N3uron OPC DA client

Step 1: Create the module: (Config => Modules => button to the left of Modules => New module)

Figure 25. New module creation

Step 2: Provide a name for the module (in this case OPCDAClient01), assign the type of module (in this case OpcDaClient) and save the new configuration.

Figure 26. Configuration of the new module as OpcDaClient

Step 3: Configure the log (usually the default values are sufficient). Save the log configuration.

Figure 27. Default log configuration

Step 4: Create the OPC DA connection to an OPC client and name it MatrikonOPCDA. Each connection is an independent OPC DA client.

Figure 28. Creating a new OPC DA server connection

Step 5: Configure the OPC DA client to connect to Matrikon.

• Host: Enter the Hostname/IP address of the target OPC server. Empty means localhost.
• Server: Instance name of the target OPC server, also known as Prog ID. For Matrikon Simulator the instance name is “Matrikon.OPC.Simulation.1”. 

Save the configuration and select restart the module.

Figure 29. OPC DA client configuration for connecting to Matrikon OPC in the same host.

Step 6: Create a tag to connect to the OPC sever: Config => Tags => New Tag

Figure 30. New tag creation

Step 7: Configure the tag. All details regarding the communication should be configured in Source entry: 

• Source.Enabled: True
• Source.Module Type: OpcDaClient
• Source.Module name: OPCDAClient01 (the module created in previous steps)
• Source.Config.Client: MatrikonOPCDA (the connection created in previous steps)
• Source.Config.Address: The tag ID in the OPC server. In this example, a valid tag ID would be “Saw-toothed Waves.Real4” to retrieve simulated data from Matrikon Simulator.

Figure 31. New tag configuration

Step 8: The tag should now be available, displaying as good quality in the Real-Time display. 

Figure 32. Tag value in real-time