Examples

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 => Model => New module)

Figure 4. 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 5. Configuring a new module as OpcDaClient

• Step 3: Configure the Logger and API sections (usually the default values are sufficient). Save the configuration.

Figure 6. Default log configuration

• Step 4: Create the connection to the OPC DA Server. Each connection is an independent OPC DA client.

Figure 7. 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 settings and select "restart module". 

Figure 8. OPC DA client configuration for connecting to KEPServerEX 6 in the same host

• Step 6: Create a tag to connect to the OPC Server: Config => Model => New Tag

Figure 9. New tag creation

• Step 7: Configure the tag. All details regarding 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 10. New tag configuration

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

Figure 11. Tag value in real-time display

Example Connection to Matrikon OPC Simulation

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

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

Figure 12. 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 13. Configuration of the new module as OpcDaClient

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

Figure 14. 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 15. 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 module".

Figure 16. 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 => Model => New Tag

Figure 17. New tag creation

• Step 7: Configure the tag. All details regarding 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 18. New tag configuration

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

Figure 19. Tag value in real-time