Module Problems

Considerations

Review the following items before you begin a module test procedure.

System Components

Before running a module test, make sure the following system components are working:

Power supply

Processor. Save the system programming onto a floppy disk. See System Programming and Maintenance (SPM.) To back up onto a memory card, see Appendix D, “Backing Up with a Memory Card.

Maintenance Terminal (MLX-20L console or PC). To run tests on the MLX module connected to the MLX-20L console, you must run the test from the PC, not from the MLX-20L console.

Busy-Out/Reset

Before running a module test, busy-out or reset the modules. Busy-Out is the best method, but it will not work if any line or extension is on a stable call. See “Busy-Out” and “Reset,” later in this chapter, for more information on these features.

Test Notes

For each test, you should note the following:

When beginning the board controller test or the internal Ioopback module test, choose to run it once or repetitively.

You can interrupt any module test by selecting Exit ( (F5) on the PC).

A module test can fail for one of the following reasons:

— The module being tested was not busied-out. Exit the test, busy-out the module, and try again.

— The error messages indicate that the module is faulty.

If errors indicate that the module is faulty, record them on the module repair tag immediately after running the test.

Control Unit Problems 4-35

Page 413
Image 413
AT&T 3.0 manual System Components, Busy-Out/Reset, Test Notes, Power supply