Diagnostic applications

Edit online

Diagnostic Applications should use one of the following screen types: INFORMATIVE, SINGLE SELECTION, TRANSITIONAL or POPUP.

The following template shows a sample screen that is used when running diagnostics on a resource. The DA would use the diag_resource_screen library function to display this screen.

The Title line is split between lines 1 and 2. The ACTION, TEST MODE, and the menu number go on the first line. ACTION is defined as one of the following:

  • TESTING
  • ANALYZING ERROR LOG
  • ANALYZING POST RESULTS
  • ANALYZING FIRMWARE STATUS
  • ANALYZING SUBSYSTEM STATUS
  • ANALYZING CHECKSTOP STATUS

If the ACTION is TESTING, the TEST MODE will be displayed on the first line. TEST MODE is defined as:

  • ADVANCED MODE
  • LOOP MODE (Advanced Mode is always assumed if Looping.)

The TEST MODE field will be blank if running non-advanced mode diagnostics.

The Menu Number represented by xxxxxx, goes on the first line. The Resource Name and Location Code go on the second line. 

             1         2         3         4         5         6         7
   01234567890123456789012345678901234567890123456789012345678901234567890123456789
   --------------------------------------------------------------------------------
 1 ACTION          {TEST MODE}                                               xxxxxx
 2 Resource Name   Location Code
 3
 4 +
 5 |
 6 |
 7 |
 8 |
 9 |
10 |
11 |
12 BODY OF MENU
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 +
22                     ___________________________________________
23 Function Key Area  | Progress Indicator Area                  |
24 Function Key Area  |                                          |
   --------------------------------------------------------------------------------

The BODY of the menu can assume multiple personalities depending on the screen type. It includes all text of the menu, including the INSTRUCTION line. The BODY does not include the TITLE.