Fujitsu M2488 manual Operator Panel Off-Line Diagnostics, Err

MAINTENANCE AND SERVICING

M2488 PRODUCT GUIDE

Table 8-17.

Operator Panel Off-Line Diagnostics (Continued)

COMMAND

SELECTION

DESCRIPTION

OR RESPONSE

*Add

A:

####

Add a test to the end of the test list. The following example shows how to add

Routine 0x09, Test 0x02:

Example: A: 0902

A

:

0

9

0

2

Test Number

“Add”

Routine Number

Options

STOP ERR

Select STOP ERR for stop on error or CONT ERR for continue on error.

CONT ERR

*Delete

D:

####

Delete the test at node number n in the current test list. The following example

shows how to delete node 8 through the end of the current test list:

Example: D: 0800

D

:

0

8

0

0

Ending node

“Delete”

Beginning node

*List

L:

####

List the tests in the current test list. The following example shows how to list

nodes 5 through 10 of the current test list:

Example: L: 050A

L

:

0

5

0

A

Ending node

“List”

Beginning node

* This command is available only if FACTORY MODE is enabled.

8-4.3.2 Off-Line Diagnostic Menu through the Remote Maintenance (RS-232) Interface

Off-Line diagnostic tests may be invoked and run through the RS-232 interface as well as the Operator Control Panel interface. Diagnostic tests are selected and executed in the same manner regardless of which interface is used, however the RS-232 interface is easier to use, more flexible, and provides more detailed error information.

The RS-232 user interface is a command-set driven architecture. A basic set of commands is pro- vided to facilitate the selection and execution of diagnostic tests. The Diagnostic Microcode archi- tecture is a list processing architecture. The RS-232 user interface command set enables the creation, modification, and deletion of tests to build a test list. The command set also includes the capability to begin test execution, provide user help information, and exit the Off-Line diagnostic mode. Multiple commands may be entered on the same line using a semicolon “;” as a separator.

The usual sequence of operations would be to first create a list of tests to be executed. Then, mod- ify any test options as desired. Finally, begin test execution. A description of the commands to accomplish these steps are outlined in section .

8-20 CG00000-011503 REV. A April 1997