Test/Troubleshooting; Tests; Test Procedures - Honeywell MT13-520 Manual

8-node multinode module service

Hide thumbs

Table Of Contents

Table of Contents

3.1 TESTS

Testing of the Multinode Module is accomplished through both hardware/firmware tests

and software. Hardware/firmware tests are built into the module to provide two means of

functionally checking the unit, whether or not it is connected to the LCN. The first test is

initiated when power is applied. Pressing the

firmware test. Software tests can be accomplished when the module is connected to the

system. As an example, loading each node's personality initiates a software Quality Logic

Test (QLT).

There may be up to four nodes physically contained in a Multinode Module. Each node has

a processor which can be loaded and tested independently and each node has a different

LCN address. The

RESET

module.

Figure 3-1 is a flow diagram showing the relationship of the hardware and software tests.

3.2 TEST PROCEDURES

Each Node in a Multinode Module must have a processor board installed before it can be

tested. Multiple functions, such as processor, LCN interface, and memory, are physically

located on the K2LCN board.

Initiate power-up tests by setting the power switch to on. The red LEDs on the boards in eacsh

node light for a few seconds (less than 30), then turn off and the green LEDs turn on as each of

the boards passes its processor dialog tests. When the tests have been completed, each

node's alphanumeric display indicates its node address.

Check the power supply ERROR and POWER OK LEDs at the bottom of the unit and the FAN

ALARM LED on the right side of the unit to ensure that no red LEDs are on and the green

POWER OK LED is lighted.

Press the

button. The red LEDs momentarily go on as above, then go out when the

RESET

green LEDs come on. Recheck the power supply, board, and fan LEDs as above. Note

that each alphanumeric display indicates its node address.

If any of the above conditions cannot be met, refer to subsection 3.3 Troubleshooting.

Multinode Module Service

RESET

button simultaneously initiates self-tests on all nodes in the

NOTE

3-1