IM 689-2
27
The wizard attempts to communicate with all level-2 and -3 controllers in the network. A report
is generated for each controller; for example:
MicroTech Controller Address – 01.00
Controller Series – 200
Software IDENT – ART1E06D
Number of Level 3 Slaves – 0
MicroTech Controller Address – 02.00
This Controller Is Not Responding.
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.
Note that the MicroTech network diagnostic will show reports for all level-2 and -3 controllers
on the network, including any that have not been defined in the BACdrop configuration file.
If there is a level-2 BACdrop panel, its report will show “This Controller Is Not Responding.”
This response is normal and expected regardless of whether the BACdrop is online or not. The
MicroTech Network Diagnostic tool cannot detect a BACdrop gateway.
7. Connect each MicroTech controller to the network and verify communications.
This step should be methodically executed and then repeated for each level-2 MicroTech
controller on the network. 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. If there is a level-1 supervisory controller, it
must
be
disconnected from the network or turned off until every repetition of this step is completed.
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 RS-232 to RS-485 converter) 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) MicroTech Network
Diagnostic screen. Click the Refresh Screen button to start another network diagnostic pass.
