Console (Z8G4_W10) Diagnostics (Adv)

Though Console Diagnostics is listed in the navigation of the CSD, the environment necessary to execute these diagnostics requires that the applications software be terminated. Hence, Console Diagnostics cannot be launched from CSD. Instead a message is provided when selecting Console Diagnostics from the CSD instructing the user to shut down applications and perform manual entry in a terminal window to invoke the diagnostic tool.

Class C proprietary software must be loaded on the system and the service key installed to perform Console Diagnostics. Check CSD Home page to Access Level status.

Figure 1. CSD Home Page Proprietary Access Status

note:

After inserting Service Key, sometimes it is necessary to check the security level of the system first, before the CSD recognizes the Service Key. Click on the Tool Chest on the desktop and select Check Security.

Figure 2. ToolChest – Check Security

note:

To access the Common Service Desktop, click the Service icon, then Diagnostics Tab, then Console Diagnostics menu selection. The Diagnostic Help Menu will appear, instructing the proper method for launching diagnostics.

Figure 3. Class C Common Service Desktop - Console Diagnostics - Diagnostic Help Menu

Detailed procedure for launching console diagnostics is shown in following section.

1. Reboot the Operator Console:

   1. If applications are running, reboot the system by clicking the Shutdown icon on the desktop and selecting the Restart option.

      Or

   2. Open a terminal window using the Toolchest:

      Type: {ctuser@hostname} reboot <Enter>

2. Just after the Operating System finishes loading and before applications start, click Cancel in the Application Startup window to stop applications from loading.

   note: Applications cannot be running when performing Console Diagnostics.

3. Open a terminal window using the Toolchest:

   1. Type: {ctuser@hostname} su – <Enter>

   2. Type the root password and press <Enter>

4. Launch the Console Diagnostics:

   Type: [root@hostname ~] /usr/g/bin/ConsoleDiags <Enter>

   Figure 4. Terminal Window – Console Diagnostic

   

5. A warning pop-up box appears. Click ENTER to continue.

   Figure 5. Warning Pop-Up – Console Diagnostic

   

6. The Console Diagnostics Window - Auto-Configuration screen appears describing the Console Type presently detected and configured.

   Figure 6. Console Diagnostics Window – Auto Configuration

   

   note: Additional information describing the Operator Console hardware and software present is listed in this window. This information is pulled mainly from the /usr/g/config/INFO file.

1. Leave Auto Configuration selected as Yes.

2. Click next to move forward. The prev button allows the user to return to a previous screen. The quit button cancels the ConsoleDiags diagnostic script. The start over button places the user at the Auto-Configuration screen.

3. The Console Diagnostics Hardware Selection menu window appears.

   Figure 7. Example Test Selection Menu Window – Console Diagnostic

   
   note: This graphic is an example of a Console. Actual displayed information will vary based on console type.

4. Select the hardware to be tested by selecting the radio button next to the desired test and click next.

   note: When selecting which test to run, the Hardware Selection window displays the test details of the selection to be performed.
5. The next window displayed appears after every Hardware Test selection. This information is logged for future reference and may be used by OLC or Headquarter Engineers that need to speak with persons executing the Console Diagnostics.

   Figure 8. FE Information Window – Console Diagnostic

   

   note: The Telephone Number must be numeric characters only. Do not use spaces or other characters in the field (i.e. -, /, #...etc).

6. Enter Name and Phone Number as requested.

   note: Fields in this form may be left blank.

7. If desired, the selected test can be run more than once. Select the number of iterations desired and click next.

8. The Hardware Test selected previously will now be readied for execution.

   note:

   Some of the tests require special preparation before execution: See list below.

   Information Pop-Up will occur before test execution.

   Figure 9. Information Pop-Up – Loopback Test

   

9. Click Start. The Results window will be displayed, Test will execute, and upon completion a Test Pass/Fail status window.

   Figure 10. Example Test Execution Window – Console Diagnostic

   

10. Upon completion of the test, click OK in the Result Message window. Click either the prev or start over button to return to the main Hardware Test selection window.

notice Running Console Diagnostics in Manual Mode is not recommended. Misidentifying or selecting incorrect options will lead to failures in executing diagnostics. Only experienced users shall use the Manual Configuration Mode.

1. Change Auto Configuration selection to No.

   Figure 11. Console Diagnostics Window – Manual Configuration

   

2. Click next to move forward. The prev button allows the user to return to a previous screen. The quit button cancels the ConsoleDiags diagnostic script. The start over button places the user at the Auto-Configuration screen.

3. For TAI X, the options are not allowed to set, click Next with default setting.

4. The rest operations and executions are same as described in the Auto Configuration Mode described above.

The following menu selection descriptions discuss each of the hardware tests available.