24
IM 689-2
The first example report shows good communications with a controller at address 01.00. The
IDENT is read out of the MicroTech controller’s memory, thus proving communications.
The second example report shows a device that (a) has not yet been connected to the network, (b)
is powered off, or (c) has some other communications problem.
7. Verify communications with the BACdrop gateway.
If the wizard is communicating with the BACdrop gateway, it will show a report similar to the
one above. The IDENT will have a different format; for example, “BACdrop v 1.57.” (This is the
software ID of the BACdrop program file, not the PMF.)
8. Connect each MicroTech controller to the network and verify communications.
This step should be methodically executed and then repeated for each MicroTech controller on
the network. If there is a level-1 MicroTech supervisory controller, it
must
be connected first.
You can connect the level-2 MicroTech unit controllers in any order; however, it is better to
follow the daisy-chain as you proceed. This will make troubleshooting easier if communications
problems occur.
a.
Set the network address (hex switch setting) to match the address on the prepared address
schedule.
b. Turn on power to the MicroTech controller. Refer to the controller installation manuals for
information on how to turn on power to each controller. (If the power was already on, turn it
off and then on again to set the network address into memory.)
c.
Check the voltages of port B directly on the port. The trunk must
not
be connected to the
controller when you do this.
Use a DC voltmeter to test for proper voltages. With the ground lead on the control panel
chassis (ground), check the voltage at the “+,” “–,” and “ground” terminals. Refer to Table 6
for the correct voltage levels.
If no voltage or improper voltage levels are found, verify that the controller is energized.
d. Check for proper communication trunk voltages at the field wiring terminals (if any) or
directly on the port connector. The trunk must
not
be connected to the controller when you
do this.
This check assumes that at least one other device (e.g., the BACdrop gateway) is connected
to the trunk already. If no voltage or improper voltages are found, check the wiring between
the port terminals and the field terminals (if any). Using Table 6 and Figure 9 or 10, verify
that the three conductors are properly terminated in the network communications connector.
If there is still a problem, verify that the communications trunk wiring is intact.
e.
Plug the network connector into port B.
f.
Verify communications with the MicroTech controller.
The BACdrop Setup Wizard should still be showing the main (fourth) BACnet Network
Diagnostic screen. Click the Refresh Screen button to start another network diagnostic pass.
If you see the IDENT for that unit, communications exist. If not, there is a communications
problem. Check the following:
Make sure the controller has power supplied to it.
Make sure the hex switches on the controller are set to the correct values. Did you cycle
power after setting the hex switches?
Make sure the communication line is properly connected to port B.
Make sure the controller is level 2 by directly connecting the PC to it. Also check its
port configuration. See the “
Working With MicroTech Controllers
” section in the
“BACdrop Setup Wizard User’s Guide” portion of this manual.
If there is a level-1 supervisory controller in the network, verify that its number of
slaves parameter was set high enough to cover the level-2 BACdrop’s address. See
“
Task 2: Configuring a Level-1 MicroTech Supervisory Controller
.”