| PM | Quote | Reply | Full Topic |
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5495 |
| Status: |
Offline
|
For Modbus/TCP, the Modbus Master is also referred to as Client, and the Slave as Server. A Modbus/TCP Slave has an IP address and Port. The Modbus/TCP Master (which is the other device communicating with the UCM/Modbus) should set the Target IP and Port to the UCM/Modbus.
For Modbus/TCP, the Modbus Master is also referred to as Client, and the Slave as Server. A Modbus/TCP Slave has an IP address and Port. The Modbus/TCP Master (which is the other device communicating with the UCM/Modbus) should set the Target IP and Port to the UCM/Modbus.
If Modbus/TCP is used for the Server/Slave, the Properties page shall show a link to Comfort Server Manager
The Comfort Server Manager screenshots below show Modbus Slave (10.0.0.188), along with other ETH03 which may be in the same network (which can be ignored). Note that the Modbus ETH03 should show Universal firmware 1.16
For the UCM/Modbus Slave, select the ETH03 on the left pane. Look at the IP address parameters on the right pane.
DHCP checkbox – This determines if the IP address for UCM/Modbus is to be assigned automatically by the DHCP server.
For Transport Protocol, select “TCPâ€.
For Routing Mode, select “Serverâ€.
In Port 1, select the port number of the UCM/Modbus Server/Slave.
For the other modbus device which acts as the Master (client), enter the IP Address and Port number of the Slave (Server), in this example, 10.0.0.188 Port 1005. This will allow the external Modbus Master to talk to the Modbus Slave via the IP address and Port. Note that the Modbus Master must also comply to the Modbus/TCP standard in order to work with UCM/Modbus as Slave.
Last edited on Monday Dec 11th, 2017 11:21 am by slychiu
| Close Window |