Differences

This shows you the differences between two versions of the page.

--- modbus_tcp_server [2020/10/12 14:10] – atolstov
+++ modbus_tcp_server [2022/02/09 11:07] (current) – emozolyak
@@ Line 1: / Line 1: @@
 ====== Modbus/TCP server function ======
-There is the possibility of external access to the WebHMI registers via the Modbus / TCP protocol. To do this, go to the menu **Configuration -> Modbus / TCP server**. If you specify the option Export in the list for registers, this register can be accessed externally via the Modbus / TCP protocol, with the address entered in the **ModBus / TCP Address**. The address format is a value from 0..65535. In this case, it's not about the address of the Modbus data model (for example 40001-49999 for holding registers), but about the address in the modubs telegram(PDU address).
+There is the possibility of external access to the WebHMI registers via the Modbus / TCP protocol. To do this, go to the menu **Configuration -> Modbus / TCP server**.
+{{ ::settings:mb_tcp_enable.png?direct&800 |}}
+If you specify the option Export in the list for registers, this register can be accessed externally via the Modbus / TCP protocol, with the address entered in the **ModBus / TCP Address**. The address format is a value from 0..65535. In this case, it's not about the address of the Modbus data model (for example 40001-49999 for holding registers), but about the address in the modubs telegram(PDU address).
   ***read** - Modbus function **#3** or** #4** is used, Holding or Input Register;
@@ Line 13: / Line 17: @@
 </WRAP>
+<wrap em>Modbus TCP server configuratoin page after 4.0 fw</wrap>
-{{setup_modbus_server.png?direct}}
+{{ network:modbus_tcp_src.png?800 |}}
+<wrap em>Modbus TCP server configuratoin page before 4.0 fw</wrap>
+{{  network:setup_modbus_server.png?direct&800}}