GE Exclusive Use Only

Direction  5409363-8EN,  Rev#  22
Optima CT660 Service Methods (Res)
Module Version  5.0,  Version Date  6/12/15

Real-In-On Console Diagnostics (10HW10.x / 10HW33.x /

11HW34.x)
Last Revised: June 12, 2015

1  Overview
Console Diagnostics are a series of hardware specific scripts that utilize common commands
automatically. This allows the user to test and or retest consistently without the need for manual
keyboard entry. The commands used are basic.

To access the Common Service Desktop, click on the [Service] icon, then [Diagnostics],

then [Console Diagnostics]. (See Illustration 1.) Instructions are provided to shut down applications
and perform manual entry in a Unix shell to invoke the diagnostic tool.

Illustration 1:  Console Diagnostics Screen

NOTE: Class C must be loaded and the Service Key installed to perform Console Diagnostics.
2  Requirements
1. Application Software must be brought down with one of the following methods:
o CSD (Common Service Desktop) via the Utilities / Application Shutdown selection
o Unix Shell: {ctuser@hostname} cleanMon
2. The Operator Console should be rebooted before starting Auto-Console Diagnostics.

If a failure occurs during the testing and the Operator Console has not been rebooted prior to
performing the diagnostic test selections, then reboot and retest the Auto-Console
Diagnostics.

3. Media Failures: New (approved) media should be reserved for the SCSI Tower testing. Media
should be formatted in advance and not write-protected.

3  Issues
1. Media Failures: during the media towers test the media content will be destroyed. There may
be content / data on media that may cause the tests to fail. Whenever possible, new or
specific media should be reserved for the media towers testing. Additionally, if the media
towers tests fail, repeat the test and it may pass (and continue to pass). This may be a timing
issue.

All system or customer media must be removed from the PMT before performing Auto-
Console Diagnostics. This is done to avoid overwriting the DVD System State or any content.
Media towers tests are always destructive to the content of the media installed in the media
towers.

2. Try not to move the mouse around in the pop-up windows. Wait until the tests are completed
to view the results.
3. Test including DIP will allow selection of the subsequent DIP Test script is performed with or
without loopback capability. If loopback capability is selected (Yes, run the loopback test ) the
DIP Board diagnostic will test the RX/TX ports.
4. If the test fails when loopback capability is selected, the site problem may be one of the
following issues:
o The Console's internal Fiber Optic Cable is faulty. Isolate the DIP from the internal
fiber optic cabling and re-run the DIP loopback test.
o The loopback cabling is not installed, it is bad, or it is not fully installed (clicked in).
o The DIP board is faulty and must result in a replacement

4  Invoking Console Diagnostics

1. Install the Service Key.
2. If the user cannot perform the required reboot , then shutdown Application software to run
diagnostics. Open a Unix Shell from the Toolchest and bring down Application software if
necessary:

{ ctuser@hostname} cleanMon

NOTE: Console Diags requires an Operator Console reboot for optimal performance.

3. Close this Unix Shell.

4. With Application Software down, open a Unix Shell and type the following:
o {ctuser@hostname} cd /usr/g/bin
o {ctuser@hostname} ls *onsole*
 console* ConsoleDiags@ consolediagsgui.py* HartConsoleCollect*

o {ctuser@hostname} ConsoleDiags
5. A Pink Pop-Up Box appears. Click on the [ENTER] box to continue. The message below is
displayed:

====================================================

Starting console diagnostics...

Console diags tool must be run as root.

Enter the root password when prompted.

====================================================

6. Input the required root Password:

Password: #bigguy

7. The Auto-Configuration Screen appears describing the Console Type and the number of IG
Nodes presently configured.
8. Click on the [Next] button to move forward. The [Previous] button allows the user to return to
a previous screen. The [Cancel] button cancels the Auto-Console diagnostic script and allows
the script to perform the clean-up process. The [Start Over] button places the user at the
Auto-Configuration Screen.
9. The screen displays information describing the system, Host and GPU present.

Illustration 2:  Invoking Console Diagnostics Screen

5  Menu Selections for Console Diagnostics
The Menu Screen provides the selection methodology for testing the various hardware residing within
the Operator Console when performing Auto-Console Diagnostics.

Illustration 3:  Console Diagnostics Screen

  DIP/SDDA/GPU (Recon Hardwares)
 Host Computer
 Host: USB HUB
 Host: Video Card (FX1800)
 Host: GPU (FX4800)
 Host: DIP Card
 Host: Scan Data Disk Array(SDDA)
 MOD: SCSI Host Adapter (destructive to media content)
 PMT: DVD-RAM (destructive to media content)
 PMT: DVD-RW (destructive to media content)
 All Non-Destructive Tests
 ALL ABOVE

6  Running Console Diagnostics

1. Click on a test menu selection.
2. Click on the [Next] button to move forward to the Repetitive Screen.

6.1  Repetitive Screen

1. The next screen (not shown) is repetitive information of the test selection.
2. Click on the [Next] button to move forward to the Contact Screen.

6.2  Contact Screen

1. The Contact Screen allows the user to inform other service personnel and Customers that the
Operator Console is in use and provides important Contact Information.
2. If necessary, position the cursor in the Name entry block and click.
 3. Enter your Name or the on-call contact.
4. Press the Tab keyboard selection.
5. Enter the Phone number you can be reached at or the on-call contact number.
6. Click on the [Next] button to move forward to the Iteration Screen (or the Loopback Screen for
DIP Test ONLY).

6.3  Iteration Screen

1. The Iteration Screen allows the user to select the number of passes or iterations required to
determine the present failure. Normally, a single (1) iteration is usually adequate to determine
a failure, however, intermittent failures may require extensive iterations.
2. In the Iterations entry field block, input the number of iterations to be performed.
3. Click on the [Next] button to move forward to the Loopback or Start Screen

6.4  Loopback Screen

1. Whenever Test DIP is selected. This test script allows for a choice to test the DIP Board in a
stand-alone manner or with a loopback capability. If loopback capability is selected the DIP
Board diagnostic will test the RX/TX ports when the loopback cable is installed.

Illustration 4:  How to connect loop-back cable

2. Click the button

o Yes, run the loopback test
 o No, do not run the loopback test
3. Click on the [Next] button to move forward to the Start or Media Screen.

6.5  Media Screen

1. Whenever Test MOD or DVD is selected the media inserted/ warning screen will appear. This
screen informs the user that the content /data of any media installed in the MOD Tower or
PMT (Peripheral Media Tower for DVD) will be lost/destroyed. Additionally, the user is
informed that the System State should or write-protected media should not be used. Some
users may have issues with media containing DICOM.
2. Insert the media (MOD and DVD) into the SCSI Tower drives.
3. Wait one minute or until the media inserted has completed initializing.
4. Click the button: Yes, the media has been inserted.
5. Click on the [Next] button to move forward to the Start Screen.

6.6  Start Screen

The Start Screen allows the user the choice of starting the Auto-Console Diagnostic Tests at any time.

When the [Start] button is selected the user may no longer select the [Previous] button to

NOTE:
adjust test selection set-up.

Click on the [Start] button to begin testing.

7  Test Log Files

The Auto-Console Diagnostic log files are overwritten with each time the script is run.

[ctuser@hostname] cd /usr/g/ConsoleDiags/log

[ctuser@hostname] more display.log

[Ctrl+C] to exit viewing log file.

8  Example Output for Console Diagnostics

In this section, examples are provided to assist the user in determining potential output. To view a
selection, click on a link below. Not every example of output can be provided (failing vs. passing).

 Section 10.1 - Host Test - Z800

 Section 10.2 - Host USB HUB Test
 Section 10.3 - Video Card (FX1800) Test
 Section 10.4 - GPU Test
 Section 10.5 - DIP Card Test with Loopback selected but no loopback Cable Installed
 Section 10.6 - DIP Card Test with Loopback Cable Installed
 Section 10.7 - Non-Destructive Disk Array Test
 Section 10.8 - Destructive Disk Array Test
 Section 10.9 - MOD Test
 Section 10.10 - DVD-RAM Test
 Section 10.11 - DVD-RW Test

9  Additional Information

9.1  Host ifconfig command

The ifconfig command as run on the Z800 Host Computer from ctuser will verify if there is any type of
active connection - but not necessarily the correct active connection. Active connections can be
verified using the ping process. Look for running. Remember that running is a moment in time and
does not mean the connection is still active for the next moment in time.

{ctuser@hostname} ifconfig

Table 1:  Z800 NIC Address Definition

NIC Description Connection

Address Port
eth0 Empty D
eth1 Gantry TGP C
eth2 Hospital Backbone B
eth3 AW (Switch Hub) A
lo Under Unix/Linux this is the local device that is the local system N/A
(Software pseudo device)

9.2  GPU Card Diagnostics

9.2.1  Check GPU Graphic Card Number

Check the number of graphics cards installed. If both "0" and "1" display, both FX1700 and FX4800
(GPU) cards are installed.

{ctuser@hostname} ls /proc/driver/nvidia/cards

0,1

9.2.2  GPU Test Command

{root@hostname} gpudiag

If TEST SUCCEEDED. GPU functions well.

If TEST FAILED, refer to the display message and RECOMMENDED ACTION.

THIS MAY NOT BE A HARDWARE ISSUE.

Verify that the system software has been loaded correctly.

{ctuser@hostname} [2] su -

Password:enter

{root@hostname} # gpudiag

Examples of test passed.

{root@bay ~} # gpudiag

GE Healthcare - GPU Diagnostic

ATI Technologies Inc.: No GPU card
Testing - NVIDIA Corporation - Quadro FX 4800
-----------------------------------------
info - /usr/X11R6/bin/xauth merge -
info - /usr/X11R6/bin/xauth merge -
info - 1 displays running
info - GPU is connected to display :0.1; GLX version 2.1.2 NVIDIA 177.86
info - measured FPS 23.692800
TEST PASSED - no defects found

{root@bay ~} #

10  Output Examples

10.1  Host Test - Z800

Illustration 5:  Host Computer - Z800 Test

10.2  Host USB HUB Test

Illustration 6:  USB HUB Test

10.3  Video Card (FX1800) Test

Illustration 7:  Video Card Test

10.4  GPU Test

Illustration 8:  GPU Diagnostic Test

10.5  DIP Card Test with Loopback selected but no loopback Cable Installed

Illustration 9:  DIP Card Test without Cable Installed

10.6  DIP Card Test with Loopback Cable Installed

Illustration 10:  DIP Card Test with Cable Installed

10.7  Non-Destructive Disk Array Test

Illustration 11:  Non-Destructive Disk Array Test

10.8  Destructive Disk Array Test

Illustration 12:  Destructive Disk Array Test

10.9  MOD Test

Illustration 13:  MOD Test
10.10  DVD-RAM Test

Illustration 14:  DVD-RAM Test

10.11  DVD-RW Test

Illustration 15:  DVD-RW Test