ECG–UG–14-002 REVISION DATE PAGE30XAXWBACnet Option Rev G December 2016 54 OF 56Back to Beginning of Chapter – Table of Contents7 BACNET IP COMMUNICATION TROUBLESHOOTINGIn the case of BACnet IP communication problem, i.e. the unit is not responding to theBuilding Manager System, please read the following section to learn more about thepossible causes.Possible cause Solution1. The BACnet activationdongle is not detectedby the chiller applicationOpen the metal casing of the Touch Pilot controller andverify that the blue BACnet dongle is correctly connected(see also section 2).2. The Ethernet cable isnot correctly connectedOn the Ethernet connector, verify that the green LED isON and the orange LED is blinking (see also IOM Control).3. Network parameters areinvalidOpen 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 interfaceand verify all network parameters (see also section 6).4. There is an IP routerbetween the equipmentand the BMSTo verify the connection, you need to have any BDTsoftware (BACnet Discovery Tool) installed. This softwarewill allow you to display the list of devices connected tothe BACnet network, including the physical names andinstance 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 bedisplayed.3. Find the required device according to the BACnet deviceinstance configured, i.e. 1600001.Free download is available at:www.ccontrols.com/sd/bdt.htm5. BACnet Enable in theBACnet Parametersmenu is set to NO.Navigate to the Configuration menu and check BACnetparameters (see also section 3.2).Note: Only Carrier service can access BACnet Parameters.