modbus_tcp_server
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
modbus_tcp_server [2019/01/10 15:19] – emozolyak | modbus_tcp_server [2022/02/09 11:07] (current) – emozolyak | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Modbus/TCP server function ====== | ====== 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**. |
+ | |||
+ | {{ :: | ||
+ | |||
+ | 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; | ***read** - Modbus function **#3** or** #4** is used, Holding or Input Register; | ||
Line 9: | Line 13: | ||
An interesting application is the connection of heterogeneous systems to each other when WebHMI devices are installed in different systems, allowing them to exchange data among themselves. In this case, for example, to read the register using the Modbus / TCP protocol from another WebHMI device, you need to use the address in the format IRxxxxx (where xxxxx is the server address). | An interesting application is the connection of heterogeneous systems to each other when WebHMI devices are installed in different systems, allowing them to exchange data among themselves. In this case, for example, to read the register using the Modbus / TCP protocol from another WebHMI device, you need to use the address in the format IRxxxxx (where xxxxx is the server address). | ||
- | | + | <WRAP center round important 60%> |
- | | + | ATTENTION! For correct reading from the WebHMI registers of Double Word type (time, float, etc.) via the Modbus TCP protocol, the Modbus - client should use a group register read, i.e. to use the data length of 2. |
- | + | </ | |
- | {{setup_modbus_server.png? | + | |
+ | <wrap em> | ||
+ | {{ network: | ||
+ | |||
+ | <wrap em> | ||
+ | {{ network:setup_modbus_server.png? | ||
modbus_tcp_server.1547133574.txt.gz · Last modified: 2019/01/10 15:19 by emozolyak