comfilehmi:hmi_connection_modbus_tcp:index
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
comfilehmi:hmi_connection_modbus_tcp:index [2024/02/01 13:12] 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 12: | 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. | 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 }} | {{ :comfilehmi:hmi_connection_modbus_tcp:master_channel_config.png }} | ||
| Line 20: | Line 20: | ||
| | {{ :comfilehmi:hmi_connection_modbus_tcp:master_plc_modport.png }} | ::: | | | {{ :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) ===== | ===== 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 }} | {{ :comfilehmi:hmi_connection_modbus_tcp:slave_settings.png }} | ||
comfilehmi/hmi_connection_modbus_tcp/index.1706760764.txt.gz · Last modified: 2024/02/01 13:12 by COMFILE Technology