--- title: "Quick User Guide | Modbus TCP Config | N3uron KB V.1.20" slug: "quick-user-guide-modbus-tcp-configuration" description: "Welcome to N3uron, the modern and highly customizable Industrial IoT and SCADA software solution to accomplish any data collection project." updated: 2022-03-29T07:53:50Z published: 2022-03-29T07:53:50Z canonical: "docs.n3uron.com/quick-user-guide-modbus-tcp-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. # Modbus TCP Client Configuration Example The following steps show how to read data from a Modbus TCP server. This User Guide assumes a basic understanding of Modbus communication protocol. **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 9. New module creation **Step 2:** Provide a name for the module (in this case MbClient), assign the type of module (in this case ModbusClient) and save the new configuration. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure10.png) Figure 10. Configuring new module as ModbusClient **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%2011(4).png) Figure 11. Default log configuration **Step 4:** Set up the Modbus channel. Each connection to a Modbus server is setup with a channel and a device. The channel represents the connection media (Ethernet or serial connection) and the device represents the Modbus server (or Modbus slave for serial connections). This means that in order to connect to a Modbus sever, a Modbus channel must be created and configured first, providing all the necessary communication settings. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2012(3).png) Figure 12. New Modbus channel set up **Step 5:** Set up the Modbus device. Save the Modbus driver configuration and restart the module once the device has been configured. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2013(4).png) Figure 13. New Modbus device setup ![Figure 13-BIS- New Modbus Device setup](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2013-BIS-%20New%20Modbus%20Device%20setup.png)Figure 13-bis. New Modbus device setup **Step 6:** Create a tag to connect through to the Modbus sever: Config => Tags => New Tag. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2014(3).png) Figure 14. New tag generation **Step 7:** Configure the tag. All details regarding the communication should be configured in Source entry: - **Source.Enabled:** True - **Source.Module Type:** ModbusClient - **Source.Module name:** MbClient (the module created in previous steps) - **Source.Config.Device:** Channel01/1 (the channel/device created in previous steps) - **Source.Config.Modbus Address:** The Modbus address of the tag - **Source.Config.Data type:** The Modbus data type - **Source.Config.Scan rate:** The signal’s scan rate ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure-15-nueva.png) Figure 15. Configuration of tags belonging to Modbus devices **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%2016(2).png) Figure 16. Tag value in real-time display Note:Log files for troubleshooting can be downloaded from the WebUI in Diagnostics => This node => Export logs button.