Ethernet/Ip Connection Problems - Carrier AquaEdge 23XRV Controls Operation And Troubleshooting

SYMPTOMS
The unit does not respond to the instruc-
tions sent by the supervision PC on the
CCN bus.
Communication problem when connect-
ing two buses (primary bus and second-
ary bus).
SYMPTOMS
Start-up page loads, then goes to fault
state.
While accessing the unit via the web
browser, the Java platform launches, but
remains blocked. No file is loaded.
The application has been launched, but
the screens are not shown in the web
browser.
NOTE(S):
a.
The unit cannot automatically obtain the network parameters via a DHCP (Dynamic Host Configuration Protocol) server.
b.
The intranet site address of the unit is the IP address.

Ethernet/IP Connection Problems

Use the following methods to troubleshoot:
UNIT IS POINT-TO-POINT CONNECTED TO A PC
Ensure controller is powered on prior to configuration and check
Ethernet connection and PC Network Interface Card (NIC).
NOTE: In addition to the following procedure, it may be neces-
sary to check the Ethernet connection and/or configure the PC net-
work board.
In Network Settings, open Local Area Connection Properties. Se-
lect Internet Protocol and click Properties. See Fig. 70.
Fig. 70 — Local Area Connection Properties
Table 12 — Hardware Problems
POSSIBLE CAUSES
Problem at the RS485 converter level of
the PC or connection problem on the pri-
mary CCN bus.
Electrical problem between 0 v CCN of
the primary bus and 0 v CCN of the sec-
ondary bus.
Table 13 — Web Interface Problems
POSSIBLE CAUSES
Network property details are not valid.
Ethernet network is not available.
Proxy server problem in the local network. Contact your system administrator.
A proxy server is used to access the unit
and this supplies the old screens to the
browser. Incorrect configuration of the
Java application.
SELECT
a30-5898
CHECKS
Check the CCN cable connections. The
unit CCN address is 0.1 and the com-
munication speed is 9600 baud by
default.
Check the connection of the metal part
of the interface casing to earth.
a,b
CHECKS
Check the network parameters (see the
section Ethernet/IP Connection Prob-
lems on page 36).
Check to see if the orange LED on the
unit is flashing.
Check that the web browser does not go
via a proxy server to access the unit.
Check that the Java application does not
store the internet files on the PC.
The Internet Protocol Properties window is displayed.
• If no IP address is configured in the General and Alterna-
tive Configuration tabs, the unit IP address must be config-
ured to 169.254.xxx.xxx. Modify the unit IP address and
then restart the system.
• If the PC has a fixed IP address configured in one of the
two tabs (General and Alternative Configuration), the IP
address of the PC and the unit IP address must have the
system and sub-system fields in common. The last part of
the IP address is the host number and must be unique on
the sub-system.
172.30.101.11 and PC address — 172.30.101.182. In this
example, 172.30 corresponds to the network, and 101 cor-
responds to the sub-system. Carry out the necessary modi-
fications and try to access the unit again.
In the case of a problem, open a Windows command window
(Start, Execute, type cmd and press Enter), then type the com-
mand ping, followed by the unit IP address. In the example shown
in Fig. 71, the PC receives four positive responses (replies).
Fig. 71 — Ping — Positive Replies
36
SOLUTIONS
Replace the RS485 connector.
Connect the metal part of the interface casing
to earth.
SOLUTIONS
Contact your system administrator.
Check the Ethernet connection to the local
network if the orange LED does not flash.
In agreement with the system administrator,
open the Runtime Java control panel and
select Direct Connection in the system
parameters and/or request in the web
browser (Tools  Options  Connection 
System parameters) that no proxy server is
used to go to the local addresses. If possible,
uncheck "use of an automatic configuration
script." Restart the web browser.
Open the browser and in the system connec-
tion parameters add the IP address of the
unit in the proxy exceptions.
(Tools  Options  Connection  System
parameters  "No proxy for"). See the sec-
tion Java Application Configuration on
page 38.
For example: Unit address —