EasyManua.ls Logo

CLIVET GW3-MOD Gateway - Debugging; Checking the Communication between the Gateway and Refrigerant System; Opening Web Debugging Page

CLIVET GW3-MOD Gateway
72 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
06
1 Debugging
1.1 Checking the Communication Between the Gateway
and Refrigerant System
1.1.1 Opening Web Debugging Page
According to the description above, connect the X Y E ports on the ODU to those on the
access Gateway. (*1)
A1 B1 E ports provide Modbus RTU protocol interfaces, and the LAN port provides
Modus TCP protocol interfaces. The integrator can select the access mode based on
the actual project requirements, and select the corresponding access mode for
debugging.
On the web page embedded on the Gateway, check whether the Gateway and
refrigerant system are communicating normally.
Before integrated development by a third party, ensure that all steps in section 1
Debugging are completed on the Modbus Gateway on site.
In the address bar of Chrome browser (*3), enter "http://Gateway IP address" to open
the web page of the Gateway. For example, the default IP address of the Gateway is
192.168.1.200. enter" http://192.168.1.200" to open the web page as shown below.
(*1) When the refrigerant system is powered on, system detection will take some
time. During this period, the Gateway may obtain incorrect information of the
refrigerant system. You are advised to perform Modbus Gateway debugging after
the refrigerant system is stable (about 15 minutes after power-on, depending on the
actual refrigerant system).
(*2)
1. The PC and the Gateway need to be in the same network segment. For specific
settings, consult relevant IT personnel.
2. The PC OS can be Windows 7 (32-bit or 64-bit) or later versions.
(*3)
1: Chrome browser needs to be in 70.0 or any later version.
2. Other browsers may be incompatible, preventing the Web function from working
properly.