Bacnet Ip Communication Troubleshooting - Carrier 30XW User Manual

7 BACNET IP COMMUNICATION TROUBLESHOOTING

In the case of BACnet IP communication problem, i.e. the unit is not responding to the
Building Manager System, please read the following section to learn more about the
possible causes.
Possible cause
1. The BACnet activation
dongle is not detected
by the chiller application
2. The Ethernet cable is
not correctly connected
3. Network parameters are
invalid
4. There is an IP router
between the equipment
and the BMS
5. BACnet Enable in the
BACnet Parameters
menu is set to NO.
Back to Beginning of Chapter – Table of Contents
ECG–UG–14-002
30XAXW
BACnet Option
Solution
Open the metal casing of the Touch Pilot controller and
verify that the blue BACnet dongle is correctly connected
(see also section 2).
On the Ethernet connector, verify that the green LED is
ON and the orange LED is blinking (see also IOM Control).
Open a command prompt under Windows
(Start > Run > type "cmd" > OK).
Type the command "ping" followed by the unit IP address,
e.g. ping 169.254.0.10). The equipment must respond.
Go to the Setup menu on the Touch Pilot user interface
and verify all network parameters (see also section 6).
To verify the connection, you need to have any BDT
software (BACnet Discovery Tool) installed. This software
will allow you to display the list of devices connected to
the BACnet network, including the physical names and
instance numbers.
To discover devices connected to the BACnet network:
1. Run the BDT software and execute the "Who Is" command.
2. A list of devices connected to the BACnet network will be
displayed.
3. Find the required device according to the BACnet device
instance configured, i.e. 1600001.
Free download is available at:
www.ccontrols.com/sd/bdt.htm
Navigate to the Configuration menu and check BACnet
parameters (see also section 3.2).
Note: Only Carrier service can access BACnet Parameters.
REVISION
Rev G December 2016
DATE PAGE
54 OF 56