Troubleshooting; Troubleshooting Procedures - Daikin MicroTech II Installation And Maintenance Manual

Troubleshooting Procedures

Follow these general procedures if you can control the
MicroTech II chiller unit controller from the keypad/display, but
are not able to communicate with the unit via the network.
Also refer to Table 10 to diagnose and correct issues related to
the setup and use of the BACnet Configuration Tool.
Network Parameters
→ Confirm that the BACnet communication module
is inserted properly and that the LEDs are functioning
properly (Table 1 and
→ Verify that network parameters are set correctly as
shown in Table 7.
→ Make sure there are no duplicate devices on the
network.
→ Verify the unit controller is set up to communicate
BACnet using the keypad/display. Refer to the proper
Chiller Unit Controller OM for details.
Network wiring
If performance is unsatisfactory or network is experiencing
issues such as noise, loss of data packets, or collisions:
→ Confirm that the shield is landed at only one point in
the trunk.
→ Be aware that network topology must be daisy-chain
or line topology (no T-Taps or ring layout).
→ Verify that network wiring does not exceed 4000 ft
total distance limit (without repeaters) at 76800 bps
baud.
→ Verify that polarity is maintained.
→ Check that there are end-of-line termination resistors
at the first and last device on the trunk. This is required
by the RS-485 specification.
→ Verify that the network trunk avoids strong sources of
electromagnetic interference (EMI).
→ Verify that the network trunk is not located near a DC
load switch (relay).
Communications
→ Verify that other devices on the network are still
communicating.
→ Verify that all appropriate configuration has been done
to BAS server.
Contact the Daikin Applied Controls Customer Support group
at 866-462-7829 for additional assistance, if necessary.
www.DaikinApplied.com
Table 2).
Table 10: BACnet Configuration Tool Troubleshooting
Symptom Issue
MAC Layer Type
incompatibility;
Unable to read or write incorrect setup of
to the unit controller communication
via the communication module and
module BACnet
Configuration Tool
parameters
The Device
Cannot change the
Instance Write
Device Instance
property is
Number
disabled
When selecting MS/TP The serial port is
from the MAC Layer already in use by
Selection options, a another program
series of three errors or the BACnet
appear, including: Configuration Tool
"Error: [5] Access is is trying to use
denied,." "MS/TP Init a serial port that
Failed (-306)" and is not present or
"BACLIBinit failed" working
A "?Write Error [-111]?:
Timeout at MS/TP
An MS/TP Station
Station Address" error
Address may
appears when trying
already exist
to modify the MS/TP
Station Address
Receive the following
Message: "MS/TP
Library Load Failed:
The application
has failed to start
because its side-by-
side configuration
PC is missing a
is incorrect. Please
required Microsoft
see the application
Visual C++ 2008
event log or use the
Redistributable
command-line sxstrace.
Package
exe tool for more
details."
Issue - PC is missing
a required Microsoft
Visual C++ 2008
Redistributable
Package
Figure 27: Event Properties Window
21 IM 906-4 • MICROTECH II CHILLER UNIT CONTROLLER

Troubleshooting

Troubleshooting
Solution
• Check that the MAC Layer Type
has been set to MS/TP
• Verify that the Device Instance
Number of the communication
module has been entered in the
Device Instance field in the BACnet
Device tab
• Make sure the Device Instance
Number of the communication
module is unique on the BACnet
network and does not match the
Device Instance of the BACnet
Configuration Tool. See Verify
BACnet Communication section
• Verify the Baud Rate of the BACnet
Configuration Tool matches the
communication module
Select Enable from the BACnet Device
tab to enable the Device Instance Write
property
Close any programs that are using
the serial port and restart the BACnet
Configuration Tool. If the problem
persists, verify that the BACnet
Configuration Tool is using the correct
serial port by following these steps:
1. Open the Configuration Tool by
selecting BACnet IP as the MAC
Layer Type
2. In the lower right corner of your
task bar, click on the BACdoor OEM
Client icon.
3. Click Configure
4. Change COM Port to the COM Port
on your PC
5. Restart the BACnet Configuration
Tool by choosing MS/TP as the
MAC Layer Type
Change the MS/TP Node Address of
the BACnet Configuration Tool using
the BACdoor OEM Client tab. This
address needs to be unique on the
network. It may already be set to the
address you are trying to write to the
BACnet Configuration Tool
1. Open Event Log by typing, "Event
Viewer" in the search bar of the
Windows Start Menu, then clicking the
"Event Viewer" link.
2. In the left pane of the Event
Viewer window, click to expand the
"Applications and Services Logs."
3. Click BCM Configuration Tool within
the list.
4. From the center pane, double-click
the event.
5. In the message pane, locate the
version of missing Microsoft Visual
C++ 2008 Redistributable Package
(Figure 27).
6. Locate and install the missing
version from Microsoft's website.