Differences

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

--- comfilehmi:hmi_connection_modbus_tcp:index [2023/06/30 06:05]
COMFILE Technology
+++ comfilehmi:hmi_connection_modbus_tcp:index [2024/02/01 13:13] (current)
COMFILE Technology [Using the ComfileHMI as a Modbus TCP Server (Slave)]
@@ Line 1: / Line 1: @@
 ====== Modbus TCP ======
-As of v2.62, the ComfileHMI editor now supports Modbus TCP running as either a client (master) or as a server (slave).
+As of v2.62, Comfile Studio now supports Modbus TCP running as either a client (master) or as a server (slave).
+When operating as a Modbus TCP server (slave), only the ComfileHMI's [[comfilehmi:hmieditor_susik:index#internal_memory|internal memory]] is addressable.  Modbus address 0 corresponds to internal memory address 0, Modbus address 1 corresponds to internal memory address 1, etc. in a 1-to-1 mapping for the entire address range.  Only 16-bit Modbus functions (e.g. Register reading and writing) are supported.  If the user stores a value larger than 16-bits to the internal memory location, only the least significant 16-bits will be read from or written to through the Modbus TCP server.
 ===== Using the ComfileHMI as a Modbus TCP Client (Master) =====
@@ Line 10: / Line 12: @@
 There are many ways to configure a TCP/IP network, but the image above illustrates a typical scenario when the ComfileHMI is operating as a Modbus TCP client (master).  Each Modbus TCP server (slave) will be assigned a unique IP address.  In the diagram above the Moacon and the Modbus TCP gateway are both operating as Modbus TCP servers.  However, behind the Modbus TCP gateway, there are two individually addressable PLCs:  The CUBLOC/MSB and the Modport.
-In the ComfileHMI Editor's //Project Properties//, each channel corresponds to an individual Modbus TCP server, and each channel can have one or more PLCs.  For the configuration above, the configuration may look like the image below.
+In Comfile Studio's //Project Properties//, each channel corresponds to an individual Modbus TCP server, and each channel can have one or more PLCs.  For the configuration above, the configuration may look like the image below.
 {{ :comfilehmi:hmi_connection_modbus_tcp:master_channel_config.png }}
@@ Line 18: / Line 20: @@
 | {{ :comfilehmi:hmi_connection_modbus_tcp:master_plc_modport.png }}     | :::                                                                    |
-Once configured, you can address the PLCs just as you would any other PLC in the ComfileHMI editor.
+Once configured, you can address the PLCs just as you would any other PLC in Comfile Studio.
 ===== Using the ComfileHMI as a Modbus TCP Server (Slave) =====
-To use the ComfileHMI as a Modbus TCP server (slave), enable the Modbus TCP server in the ComfileHMI Editor's //Project Properties//.
+To use the ComfileHMI as a Modbus TCP server (slave), enable the Modbus TCP server in Comfile Studio's //Project Properties//.
 {{ :comfilehmi:hmi_connection_modbus_tcp:slave_settings.png }}
@@ Line 32: / Line 34: @@
 {{ :comfilehmi:hmi_connection_modbus_tcp:setupscreen1.png?nolink |}}
+Touch SETUP in System screen.
+{{ :comfilehmi:hmi_connection_modbus_tcp:e4.png?nolink |}}
 {{ :comfilehmi:hmi_connection_modbus_tcp:runtime_network_settings.png }}
-When operating as a Modbus TCP server (slave), only the ComfileHMI's [[comfilehmi:hmieditor_susik:index#internal_memory|internal memory]] is addressable.  Modbus address 0 corresponds to internal memory address 0, Modbus address 1 corresponds to internal memory address 1, etc. in a 1-to-1 mapping for the entire address range.  Only 16-bit Modbus functions (e.g. Register reading and writing) are supported.  If the user stores a value larger than 16-bits to the internal memory location, only the least significant 16-bits will be read from or written to through the Modbus TCP server.
 [[comfilehmi:index#ComfileHMI_Connectivity| Back to ComfileHMI]]

User Tools

Site Tools

Differences

Page Tools