--- title: "Quick User Guide | OPC DA Client Config | N3uron KB V.1.20" slug: "quick-user-guide-opc-da-client-configuration" description: "Welcome to N3uron, the modern and highly customizable Industrial IoT and SCADA software solution to accomplish any data collection project." updated: 2022-01-14T09:29:48Z published: 2022-01-14T09:29:48Z canonical: "docs.n3uron.com/quick-user-guide-opc-da-client-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt > Use this file to discover all available pages before exploring further. # 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)* ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure9.png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2018(2).png) Figure 18. Configuring a new module as OpcDaClient **Step 3:** Configure the log (usually the default values are sufficient). Save the log configuration. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2019(3).png) Figure 19. Default log configuration **Step 4:** Create the OPC DA connections. Each connection is an independent OPC DA client. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2020(2).png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2021(2).png)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 ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2022(3).png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2023(1).png) Figure 23. New tag configuration **Step 8:** The tag should now be available, displaying as good quality in the Real-Time display. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2024(1).png) Figure 24. Tag value in real-time display Note: Usually, no changes are required in the DCOM since N3uron runs as a service and the default configuration for KEPServerEX permits the connection of local applications running as System. --- Log files for troubleshooting can be downloaded from the WebUI in Diagnostics => This node => Export logs button. ## 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)* ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure9.png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2018(2).png) Figure 26. Configuration of the new module as OpcDaClient **Step 3:** Configure the log (usually the default values are sufficient). Save the log configuration. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2019(3).png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2020(2).png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2029(2).png) 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 ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2022(3).png) 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. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2031(2).png) Figure 31. New tag configuration **Step 8:** The tag should now be available, displaying as good quality in the Real-Time display. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2024(1).png) Figure 32. Tag value in real-time Note: Usually, no changes are required in the DCOM since N3uron runs as a service and the default configuration of Matrikon OPC permits the connection of local applications running as System. --- Log files for troubleshooting can be downloaded from the WebUI in Diagnostics => This node => Export logs button.