• Topic ID: id_15460494
  • Version: 2.0
  • Date: Nov 8, 2018 1:37:12 AM

07MW18.4 SW LFC (LS7.X)

1 Scope

This Load from Cold (LFC) procedure only supports systems using this version of 07MW18.4. or upgrading from versions 06MW03.4 and 06MW29.7. (See Figure 1 for example console.)

For a description of the procedural flow of this document, see Table 1.

2 Software Deliverables

  • 5212704 - LightSpeed Xtream Console Operating System

    Version - GEMS Linux 6.2.9 OS

  • 5212589- LightSpeed VCT Applications Software DVD

    Version 07MW18.4

  • 5212235 - Xtream Serial-Over-LAN Service Software

    Supports: Linux Xtream: Jarrell/Westville hardware and OS versions: 4.3.16 and 6.2.9

  • HP xw8200 BIOS Floppy Set - 5191796-3

    - 5191796 BIOS 2.10 Floppy

    - 5191796-2 BIOS 2.10 Configuration Floppy

note:

The Xtream Serial-Over-LAN Service Software is not used during the LFC unless instructed via a pop-up message box. This CD is loaded directly into the VDARC Node. Then press the reset (or cycle power) at the front panel of the VDARC Node as required. This CD will auto-eject when the SOL load process is complete.

3 Pre-LFC Checks and Information Gathering

3.1 Required - Information Gathering

note:

The information in this section is NOT saved to System State.

  1. If you choose, you may start the Save System State process (Table 2) at this time.

  2. Verify and record specific system information in Section 1 of the 07MW18.4 VCT Console Information Sheet.

  3. With Application Software up, record the User Prefs Screen and Film Large Font Annotation Groups selections. Refer to Initial load of this software - Retro Recon / Customize Large Font to understand the information that may need to be gathered.

  4. Select Autovoice Volume (Toolchest, upper right corner) and record the Left Value and Right Value settings. The path to view the all audio settings is as follows: {ctuser@hostname} audioSetting (PCM2 info is the left and right value as described above).

  5. Record DICOM information as required in Section 3 of the 07MW18.4 VCT Console Information Sheet

  6. Open a Unix Shell and type:{ctuser@hostname}  installOptions

  7. Check the box on the Information Sheet next to each Option currently loaded on the system in Section 1.

  8. If Exam Split is present, perform the following to determine ves or hes.

    1. {ctuser@ hostname }   su -

    2. Password: <password>

      note:

      If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

    3. {root@ hostname }   ls -l ~ctuser/ves/.hesMode

      note:

      There are no spaces in the phrase ~ctuser/ves/.hesMode.

    4. Examine the results. If the results are similar to:

      -rw-r--r-- 1 ctuser users 0 Apr 3 12:43 /usr/g/ctuser/ves/.hesMode

      then HES (Hard Exam Split) mode is configured.

  9. If the results show “No such file or directory,” then VES (Virtual Exam Split) mode is configured. Record Exam Split Mode (Hard or Virtual). This info will be used during the LFC Options Installation.

  10. If you have the ConnectPro option and use PPS, perform the following (refer to example):

    {ctuser@ hostname }   cd /usr/g/ctuser/resources/pps

    {ctuser@ hostname }   head -12 ppsserver.cfg

    Output Example:

    PPS_REMOTE_AE_LIST =

    {

    # AppTitle,IPAddress,IPPortNo,HostName;

    DICOM_TEST_RMT,3.70.204.86,4500,Default;

    Record the PPS Information per the following EXAMPLE:

Record the AppTitle

Record the IPAddress

Record the IPPortNo

Record the HostNameRecord

3.2 Additional Console/Gantry/Configuration Information Gathering (not required)

note:

The information in this section IS SAVED to System State. It is up to the user to decide if the information gathered in this section is needed. The information may be gathered electronically and placed onto media (floppy, CD, flash drive).

  1. Service Note 06080312 for the SCSI Tower termination jumper must have been completed. If this has not been completed, the user may fail the Save/Restore System State process on older SCSI Towers.

  2. Visually verify that the SCSI Tower DVD-RAM power is applied.

  3. If applicable, verify that the SCSI Tower terminator LED is lit (located at the rear).

  4. If a DASM is used on the system, verify that it is connected.

  5. Verify that the Host Computer DVD-ROM and floppy drive do not have any media on them.

  6. Record additional information in Section 2 of 07MW18.4 VCT Console Information Sheet.

  7. Verify that the ICOM has its power LED lit. (See Figure 2.)

  8. Record the Tube Information in Section 4 of 07MW18.4 VCT Console Information Sheet. When multiple files exist, record information for a minimum of two years.

  9. (For 06MW03.X and 06MW29.7 Software) Open the Service icon. Select Error Logs and then Tube Usage. Select Details and record the following as required for each tube file applicable to the two-year rule on the Console Information Sheet:

    1. Tube serial no.

    2. Installed on

    3. Last scan on

    4. Exam Usage Total (patient and non-patient)

    5. Select Back for next tube as required.

    6. Close the Tube Usage window when information gathering is complete.

  10. (For 07MW18.4 Software) Open the Service icon. Select Error Logs and then Tube Usage. Select Details and record the following as required for each tube file applicable to the two-year rule on the Console Information Sheet:

    1. Tube serial no.

    2. Installed on

    3. Last scan on

    4. Exam Usage Total (patient and non-patient)

    5. Click on Advanced metric reporting for next tube as required.

    6. Tube mA Seconds (patient and non-patient)

    7. Scan Seconds (patient and non-patient)

    8. Select Back for next tube as required.

    9. Close the Tube Usage window when information gathering is complete.

4 Pre-LFC Save System State

The system state backup saves vital calibration and scanner files. Follow the Save (Table 2) and Restore (Table 3) procedures throughout this document precisely or valuable information may be lost.

5 Host Computer LFC

Whenever the Host Computer LFC is performed, the VDARC software must be loaded. This LFC document must be performed as written in its entirety when loading the Host to be successful.

note:

Before proceeding you must disconnect the console from the Hospital Network. Failure to do this may result in the console broadcasting traffic out to the entire Hospital network.

5.1 Host Computer BIOS Requirement

  1. Open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

  2. Password: <password>

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  3. To determine the Host Computer BIOS version, type the following:

    {root@ hostname }   dmidecode  |  grep  Ver

    Authorized BIOS versions

       Version: JQ.W1.13US = 1.13 for xw8000

       Version: 786B8 v2.10 = 2.10 for xw8200

  4. Ensure that the Host Computer BIOS version is one of the two versions shown above. If correct, skip the following step. If not correct, perform Step 5.

  5. If the Host BIOS version is not correct or if you suspect incorrect Host BIOS settings (changes specified by GE from default), follow the instructions for your specific Host type:

5.2 Linux Operating System (OS) Software Load - Host Computer

note:

During the OS load you need to select Ignore twice when it complains about I/O errors with a SCSI device. These messages will occur on systems with a DASM:

Input/output error during read on /dev/sd?

Input/output error during write on /dev/sd?

  1. Unplug the Hospital Network (HSP) cable from rear Console bulkhead. (See Figure 3.)

  2. Label the cable as HSP and set it aside during LFC.

  3. Remove the Operator Console's front cover.

  4. Ensure that the VDARC/VIG Troubleshooting Video Cable is not connected to the Scan or Display Monitors during the software load.

  5. Insert the OS DVD into the tray on Host Computer DVD-ROM Drive.

    note:

    The Host Computer must be powered ON to insert the software media.

  6. Select one of the following methods to re-power the Operator Console:

    1. If Applications are up, select the Shutdown icon on the Attention screen (Figure 4), Restart, then OK.

    2. If Application Software is down, at the toolchest open a Unix Shell and type:

      1. {ctuser@ hostname }   halt

      2. The Operator Console monitor will display a System halted message when it is acceptable to power OFF the Operator Console. (See Note.)

        note:

        (For 06MW03.X Software) Wait 1-2 minutes after the “System halted” message appears, to allow the VDARC Node to properly power-down. SW release 06MW29.7 and later has corrected this issue.

      3. Power OFF the Operator Console at the front panel switch. (See Figure 5.)

      4. Wait 30 seconds to allow all disk drives to settle; then power ON the Operator Console at the front panel switch.

  7. As the Host Computer restarts, the booting process messages appear. After the booting process completes, the boot: prompt appears. (The OS is a bootable media.)

  8. At the boot: prompt, type one of the following depending on system type:

    (For English Keyboard only) GEHC2

    (For International Command only) iGEHC2

    note:

    If a DASM is connected, select Ignore as required for IO errors. If the boot: prompt does not appear, then either the DVD is bad or the Console Operating System Media is not installed in the drive. Typing GEHC (or iGEHC) results in both scan and display being on one monitor and requires a LFC. Typing any other command not listed in this procedure will result in a LFC.

  9. After approximately 20 minutes, the OS is loaded on the Host Computer. A window appears.

  10. Remove the OS DVD from the Host Computer DVD-ROM drive when it ejects and close the tray.

  11. Press Enter to Reboot.

  12. The Host Computer begins to reboot.

    note:

    Do not insert the Applications Software DVD into the Host Computer until the Host has completed rebooting and the [root@localhost ~] window appears, displaying the prompt:[root@localhost ~]#. (See Figure 6.)

    note:

    The bootup screen changes for each OS version. The 6.2.9 OS Boot-up Screen display (shown below) contains output that may be misunderstood as a Host hardware or software issue. For example screen below, refer to “PCI: Failed to allocate mem resource #6” and “FATAL: Error inserting...” errors). Additionally, whenever the HSP Ethernet cable is disconnected from the Operator Console bulkhead, Firewall PNF errors may occur. Ignore these errors. Any other errors not shown in the screen below should be investigated.

  13. After the Host Computer reboots, verify that a window appears on the Display monitor with the prompt:[root@localhost ~]#.

  14. In the root@localhost ~ window, verify 3 Host drives and the SCSI Tower MOD and DVD are present:

    [root@localhost ~]#   cat  /proc/scsi/scsi

5.3 Application Software Load - Host Computer

All Applications software will be loaded to the Host Computer during this process. If a mouse hang occurs after the OS load on the Host, disconnect all Host USB devices and reset the Host to continue.

  1. Open the tray on the Host Computer DVD-ROM Drive.

  2. Insert the Applications DVD into the DVD-ROM Drive and close the tray.

  3. Select Run Command in the Warning box. (See Figure 7.)

    note:

    If the Warning pop-up box does not appear after two minutes, type the following in the Welcome box pop-up:

    root

    install

    Type the following in the terminal window with the Application media still installed:

    mount /media/cdrom

    /media/cdrom/autorun

  4. Select the Load button in the CT Software Installation window. (See Figure 8.)

  5. System State decision for the Install INFO decision box. (See Figure 9.)

    • If you do not have a valid System State, select No.

    • Insert the System State DVD into the SCSI Tower if you have a valid System State. Wait until the DVD LED stops blinking, then select Yes or OK as needed. Another Install INFO box appears. (See Figure 10.)

  6. If you selected Yes, select ok.

6 Config or Reconfig Setup

  1. Select the System tab. The System Settings screen appears. (See Figure 11.)

  2. Verify that the:

    • Next Patient Exam # shall be the value restored from System State. Otherwise, set it to 1.

    • ProperTime Zone is selected.

  3. Select the Preferences tab. The Preferences Settings screen appears. (See Figure 12.)

    note:

    The current illustration for the Preferences tab will not show the additional languages until after Service Pack 2 (or greater) is loaded. At that time the screen will appear as in Figure 13.

  4. Input the correct:

    1. Units for patient weight

    2. Language

    3. AutoVoice Language

    4. Date Format

    5. Time Format

    6. Preference for Modified in Room Start

      note:

      Modified in Room Start is normally Off, unless the site is in Japan and/or the customer has requested that this be turned On.

    7. Preference for HIPAA Present

      note:

      HIPAA Present is normally Off, unless the customer requests HIPPA to be On.

    8. Site preference for Dose Information Display

      note:

      Dose Information Display is for the site to use in monitoring calculated Patient Dose.

      • On (full CTDiw Display)

      • On without Total DLP (no Dose Length Product Display), or

      • Off (no CTDIw Display)

    9. Preferred kVs

    10. Target Noise Index Table

  5. Select the Hardware tab. The Main Hardware screen appears. (See Figure 14.)

  6. Click on the Hardware Settings (orange button) to access the Select hardware configuration.screen. (See Figure 15.)

  7. Click on CT ONLY. Then, depending on the DAS / Detector rating plate type, click on one of the following VCT hardware configuration selections:

    • VCT64/32 BL VDAS64

    • VCT32 FL VDAS32. (This is the selection for all 32-slice systems.)

    • VCT HALO 64 HDAS64

  8. Select OK to exit hardware configuration.

  9. On the Hardware Settings screen (Figure 16), click on the proper Table Type.

    note:

    Check the label/rating plate at the front bottom of the Table (Figure 17), closest to the Gantry (by the GTCB), and determine the Table Type according to the part number of the Table:

    • 5121647: VT2000

    • 5122080: VT1700

  10. Select proper PDU type.

  11. Click on the configured (1 or 3) Number of IGs. (See Figure 16.)

  12. Select the Network tab. The Network Settings screen appears. (See Figure 18.)

    note:

    The current illustration for the Network Settings tab will not show the Station Name until after Service Pack 2 (or greater) is loaded. At that time the screen will appear as in Figure 19.

  13. Gateway Parameters:

    1. Suite Name - The Suite Name must utilize uppercase letters. It must start with a letter, followed by 3 alphanumeric characters. The total must be four characters long. It is suggested that you choose CT01 for the first scanner (CT02....), unless a different Suite Name is required.

    2. Station Name - The Station Name identifies the text that is stored in the DICOM attribute “Station Name” (DICOM TAG 0008,1010) in all CT images created. Some PACS systems may use the Station Name attribute or system tracking for identification of the scanner where the CT images were generated. Typically, the Host Name and Station Name are the same.

      note:

      The Station Name defaults to the Host Name if it is left blank. If entered it:

      • MUST NOT exceed 16 characters

      • MUST only contain the following characters: a through z, A through Z, 0 through 9, - and _

    3. Host Name

      note:

      The Host Name identifies the hostname and AE Title of the scanner. It:

      • MUST NOT exceed 16 Characters.

      • MUST only contain the following characters: a through z and 0 through 9.

      • With the introduction of Service Pack 2 (or greater), A through Z , -, and _ characters are allowed.

      • MUST have at least one Alpha Character (A - Z or a - z) or a Special Character (_ or -).

    4. IP Address - Site supplied

      1. If the supplied hospital IP Address starts with 172.16.0.xx, click on Advanced Options. Click on the Change DARC Subnet? box, then click on: 169.254.0. Do not input a User Defined IP address unless specified by GE Healthcare Service.

        note:

        Sites requiring a User Defined IP address may be required to load the SOL CD during the VDARC Node software load process. Then, after the LFC procedure is completed, a reconfig (as root) must be performed and the DARC Subnet address can be modified as required. Additionally, the System Sate should be saved.

      2. To set the DARC subnet back to default value of 172.16.0.x, deselect the Change DARC Subnet? box.

    5. Net Mask - Site supplied address.

      note:

      If the hospital backbone IP address is 192.9.220.xx, the Net Mask must be set to 255.255.255.252.

    6. Broadcast Address - Site supplied address

    7. Default Gateway - Site supplied address

    8. If your customer has AW Direct Connect, click on Enable AW DirectConnect?. Insert any information as required.

      note:

      Complete the LFC, making certain to configure AW Direct Connect in AW Direct Connect. (Do not configure AW Direct Connect now.)

    9. Verify with customer’s network administrator if they have NIS. If they do, ensure the Advanced Options and Use NIS? boxes are checked. If they don’t have NIS, ensure these selections are not checked.

      • Domain Name: add your name here (get name from customer’s network administrator).

      • IP Address of Server: add your IP address here (get IP address from customer’s network administrator).

    10. If your customer wants to synchronize the system time to their NTP server, then select Enable Network Time Protocol, and enter the Primary Server IP address.

    11. Change DARC Subnet? (under Advanced Options, see the IP Address Gateway Parameter for specific information. This box is normally not selected.

      note:

      If the Accept tab is selected with the Num Lock hard key activated, load failures may result.

  14. Verify that the Num Lock hard key on the keyboard is not active. If it is, deselect it before selecting the Accept tab in the next step.

    note:

    Make sure that the Num Lock button on the keyboard is not active. If it is, deselect it and then select the Accept button in the next step. Failure to deactivate the Num Lock results in load issues.

  15. Select the Accept tab at the right corner of the User Interface.

  16. An Install INFO Acceptance window appears (see Figure 20).

  17. Select Yes, if correct.

    note:

    If the information is not correct, select No. Selecting No returns you to the Hardware tab. Select Hardware Settings and select the correct hardware configuration from the displayed list. Select the Accept tab again, followed by the Yes button on the Install INFO hardware box to accept the new hardware configuration.

  18. A no-action- required pop-up message appears in approximately 1 minute:

    Please make sure the CT application media is in the drive - the system will be rebooted.

    No action is required for this pop-up. The system will automatically reboot after approximately 10 seconds if the OK button is not selected.

    note:

    Do not remove the Applications Software DVD from the Host Computer until instructed to do so.

  19. After the system reboots, an sh window appears (see Figure 21). The Apps software load begins.

  20. After approximately 15 minutes, the system prompts for reboot (see Figure 22). Answer Yes. The system is going down for reboot NOW.

    note:

    During the reboot, a message may appear to the effect that the system was not able to determine what the tube type was and to run the TIC tool. This message should be ignored at this time.

  21. After approximately 3 minutes, the CT Software Auto-Start Disabled pop-up box appears (see Figure 23). Select OK.

  22. Remove the Applications Software DVD from the Host Computer by pressing the button on the DVD-ROM drive to open the tray.

  23. Close the Host drive tray.

  24. When the Host Computer has completed its reboot, you may continue.

7 VDARC Software Load Process

This section describes the VDARC Software Load Process. This section of the LFC is used for VDARC reload and replacement. In the reload case, if any Service Packs have been released for the software that are specific to Reconstruction, refer to included instructions and verify the Service Packs after the VDARC software load.

7.1 VDARC Reloads Only- Confirm Host Software and VDARC Node Type

  1. Open a Unix Shell and type the following to determine Host Computer software information:

    {ctuser@ hostname }   swhwinfo

    07MW18.4 <hardware revision info here>

  2. {ctuser@ hostname }   swhwinfo –os   for OS version

    Release: GEHC/CTT Linux 6.2.9

    Built: Wed Jan 3 11:05:37 CST 2007

  3. Confirm that the Host OS and Apps results match the OS and Apps versions to be loaded for the VDARC Node.

  4. Log into the VDARC and determine hardware type (Westville = WV or Jarrell = JR):

    {ctuser@ hostname }   ipmitool -H darc -P '' fru | grep -i "Board Product"

    (Example) Board Product : SE7520JR23

    Board Product : Intel(R) Management Module - Professional Edition

  5. To determine VDARC Node type, view the first line at the top of the response. (See examples below.)

    Westville VDARC Nodes will contain a WV string (example, SWV25)

    Jarrell VDARC Nodes will contain a JR string (example, SE7520JR23)

  6. To verify the Telnet process from Host to VDARC:

    1. {ctuser@ hostname } su  -

    2. Password: <password>

    3. [root@ hostname ] service    cliservice    start

    4. [root@ hostname ] telnet    localhost    623

    5. Server: darc

    6. Username: Enter

    7. Password: Enter

      Login successful

    8. dpccli> exit

7.2 Operating System Software Installation on Host Computer for VDARC

If any problems arise during the OS load, verify that the correct media is installed, try loading the SOL CD, or verify that the VDARC BIOS Boot Order is correct (a pop-up will inform the user to check BIOS). Jarrell VDARC and Westville VDARC hardware should not require the change to VDARC BIOS Boot Order unless someone accidentally modified it. The following link is the ONLY process required - there is not any additional process to set the BIOS to its original settings. These are the enable and final settings. (See Change VDARC BIOS Boot Order Settings)

note:

If issues occur during the VDARC OS load, a pop-up may appear stating that the VDARC BIOS must be checked. If the VDARC load continues to fail, determine if the problem is the Ethernet cable, Host NIC, or VDARC Node.

After saving the VDARC BIOS, the BIOS SETUP UTILITY window should disappear (within approximately one minute) and the VDARC will begin to reboot. If this window does not disappear, close the window and attempt to load the VDARC Node. The VDARC Node may require a reset or re-power. Issues have been reported by sites using 06MW29.7 software with Jarrell hardware. In each case, the Save was successful; however, if the load does fail, re-perform the VDARC BIOS Setup Utility process.

If VDARC Node OS load problems continue, perform the VDARC Stand-Alone OS Load procedure. This stand-alone procedure eliminates any external sources causing an issue but does not rule out media issues or internal VDARC Node issues.

  1. Insert the OS DVD into the tray on Host Computer DVD-ROM Drive.

  2. Open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

  3. Password: <password>

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  4. Type the following to begin the OS copy / load:

    1. [root@ hostname ]   cd  /usr/g/scripts

    2. [root@ hostname scripts ]   ./start_darcOS

    3. An Attention window appears (see Figure 24). Follow the list of instructions.

  5. An sh window displays the output below followed by a series of 4 dotted rows.

    Copy OS packages from the DVD to the HOST’s hard drive. This takes about 5 minutes.

    …………………………………………………………………………

  6. Once the copy process is complete, additional output will appear and the OS load begins

    Resetting the DARC to start the OS load. This takes about 3 minutes.

    OS load has started. This takes about 15 minutes.

    ##.## % done.

    note:

    The VDARC OS Load will stop prematurely ONLY if an error is encountered (refer to VDARC/DARC Node OS Load Troubleshooting). An Error Dialog Box may appear with a brief description of the error and instructions. Select OK after completing the instructions displayed in the box. If the OS load fails again, retry the load with new media. SOL Service (Figure 25) and VDARC BIOS (Figure 26) error and attention boxes may appear.

    note:

    A %done status is displayed during the VDARC OS load. This is a timed countdown sequence and does not provide status of the actual load process. When the VDARC OS load has completed a reboot message will appear.

  7. The VDARC reboots:

    sh window

    Waiting for the DARC to boot up…

    OS load is complete, DARC is UP. Please load DARC Applications.

  8. When the VDARC OS load / reboot has completed, an Information box appears. (See Figure 27.).

  9. The OS disk should eject automatically. Remove the OS media from the Host Computer drive and close the drive tray.

  10. Select OK in the Information box.

  11. Open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

  12. Password: <password>

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  13. To verify that the OS has successfully loaded on the VDARC Node, type the following:

    note:

    If the VDARC login prompt [root@localhost ~] is not present (as root), then try reloading the VDARC Node OS again per the procedure.

    1. [root@ hostname ]   rsh darc

    2. [root@localhost ~]   exit

    3. [root@ hostname ]

  14. This completes the OS load for the VDARC Node.

7.3 VDARC Applications Software Load

note:

No media is required for the VDARC Applications load.

  1. In the open Unix Shell as root, type the following:

    [root@ hostname ] cd  /usr/g/scripts

    [root@ hostname scripts ] ./start_darc_load

  2. A shell window pops up and the load begins. A SUCCESSFUL LOAD TAKES ~10 MINUTES. After the VDARC load completes, the load window will disappear. Continue the LFC procedure.

  3. Close the Unix Shell (do not use for the next process).

7.4 Confirm VDARC Software Has Loaded / Security Shell

Verify the OS and Application Software has loaded on the VDARC. If the VDARC OS or Application software is corrupt and requires a reload, then a LFC must be performed.

  1. After the VDARC is rebooted, open a Unix Shell and type the following:

    1. {ctuser@ hostname }   rsh darc

    2. {ctuser@ darc }   exit

  2. If the prompt {ctuser@darc} does not appear, the VDARC Node may require a reload or a hardware failure may be present. Verify the remote shell is successful. If rsh fails, try the ping darc command and check the Host ifconfig to verify the VDARC address and Running message.

  3. Verify the VDARC to Host security shell is successful. If the prompt {ctuser@darc} does not appear, then the LFC process was not followed or a sshd config file has been corrupted.

    1. {ctuser@ hostname }   ssh darc

    2. {ctuser@ darc }   exit

  4. If both the ssh and rsh are successful, continue with next section.

    If the rsh is successful, but the ssh command still fails, Application software will not start properly and the system will eventually halt. Perform the following to correct for port 22 unknown Host issues:

    1. Open a Unix Shell and become root:

      {ctuser@ hostname }   su  -

      Password: <password>

    2. [root@ hostname ]   config_sshd

    3. A message will appear:

      [config_sshd] Setting up sshd on oc and darc for root and ctuser accounts.

      Starting sshd: [OK]

      Starting sshd: [OK]

7.5 VRAC Flash Update

The vrac_flash_update is a required step when performing a VDARC replacement or the LFC.

  1. Verify that each VIG present has LAN communication and a power LED illuminated. If necessary, power on the VIG Node(s) and wait 3 minutes for boot to complete.

  2. Perform VRAC flash:

    {ctuser@ hostname }   vrac_flash_update

    This tool will check the FLASH versions of the VRAC on all IGs CONFIGURED in the system. If any version is not up to date the VRAC will be updated at this time. APPLICATIONS MUST NOT BE RUNNING WHEN THIS STARTS. You MUST NOT ABORT THIS PROCEDURE ONCE STARTED. Are you sure you want to continue?

    note:

    If this FLASH procedure is interrupted, reverify the VDARC rsh process is successful. Check the DARC /var/log to verify the IG Node(s) has properly initialized. Then rerun the command and watch the DARC /var/log for issues. If the vrac_flash_update continues to fail, perform the following: {ctuser@darc} vrac_flash_update ig# (where # = the IG Node placement, perform this for each IG Node)

  3. To continue, type: y.

  4. Verify that the vrac_flash_update was successful. Failure to successfully vrac_flash_update may cause issues with reconstruction and DMPR.

7.6 Initial Setdate

note:

The setdate command provides different output depending on the DARC software state. If DARC software is present:setdate completed with NO ERRORS. If the DARC is not ready or no software exists on the DARC: The darc is not responding. darc will sync time with oc during next darc reboot

  1. Wait 2-4 minutes for the DARC Node to complete the reboot process.

  2. If necessary, open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

    Password: <password>

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  3. Type the following to initially setdate:

    [root@ hostname ]#   setdate  to be prompted through the individual entries. Where:

    Note: Type “q” to quit anytime. Enter to proceed: <Enter>

    Note: TO BE ACCURATE, this tool will prompt you to enter the “Second”. Watch your clock or PC carefully to enter the proper value, and hit [Enter] at the right second to set the accurate time. Enter to proceed: Enter

    Enter the current Year (1980-2030)[2006]:

    Enter the current Month (1-12)[04]:

    Enter the current Day (1-30)[14]:

    Enter the current Hour (Military Time) (0-23) [18]:15

    Enter the current Minute (0-59) [13]:18

    Enter the current Second (0-59) [00]:10

    Updating the time on the OC and DARC, Please Wait...

    connect to address 10.0.1.2: Connection refused

    connect to address 10.0.1.2: Connection refused

    trying normal rsh (/usr/bin/rsh)

    connect to address 10.0.1.2: Connection refused

    connect to address 10.0.1.2: Connection refused

    trying normal rsh (/usr/bin/rsh)

    Current OC date : Fri Apr 14 16:14:05 CDT 2006

    Current DARC date : Fri Apr 14 16:14:04 CDT 2006

    setdate completed with NO ERRORS.

    [root@ hostname ]#

note:

The Host/OC time may drift. 24 hours after the initial setdate is performed, the setdate process will be repeated and these dates will sync up for drift. If messages inform the user that the DARC is not properly communicating at this time, just ignore them until after the software load on the DARC.

note:

During the reboot of the console, a message may appear to the effect that the system was not able to determine what the tube type was and to run the TIC tool. This message should be ignored at this point.

8 CT Applications Start Up

  1. Open a Unix shell and type the following:

    {ctuser@ hostname }   st

  2. A pink pop-up Attention message appears:

    Waiting for System Startup…

    note:

    If a message concerning incorrect DAS configuration is encountered, review the Error Log for the Card List issue. Select from the following two methods to alleviate this issue: Flash Download Update or Power OFF the Axial Drive and HVDC at the Gantry service panel - turn OFF DAS Power for 1 minute - turn DAS Power back ON - turn Axial Drive and HVDC at the Gantry service panel back ON - Flash Download Update - verify error message has disappeared. If error message reappears then troubleshoot the DAS/DCB.

  3. Visually verify that each VIG Node powers up under VDARC control and LAN activity is present at the front of each VIG Node.

  4. Watch for IG Node or Recon error messages.

    note:

    IG NODE NOT RESPONDING: The VIG Node(s) may need to be power cycled. Possibly the VDARC Node was unable to properly start the VIG Node or the VIG Node did not respond due to a bad Ethernet cable or swapped port connection.

  5. Select OK for FastCal and other pink message boxes that appear throughout the reboot process.

  6. Review the Error Log and verify “Selftest completed successfully”.

9 Optional - dvd_search Command

Perform this section whenever a SCSI Tower is replaced or to avoid issues detecting the DVD drive on the SCSI Tower.

  1. Open a Unix Shell and become root:

    {ctuser@ hostname }   su  -

  2. Password: <password>

    note:

    If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

  3. [root@ hostname ]  dvd_search

  4. The following is an EXAMPLE of what may be displayed:

    [dvd_search] SCSI DVD-RAM Drive is found

    [dvd_search] DVD-RAM SW-9574S will be used.

    Alias device dvd: src2b0t4u0 (sr0) -> (sgc2b0t4u0, sg4)

    Alias device mod: sdc2b0t3u0 (sdd) -> (sgc2b0t3u0, sg3)

    Unable to match device for line 3 (alias mod1)

    [root@hostname ~]#

  5. Ignore any “Unable to match device” messages.

  6. Close the Unix Shell.

10 Restore System State

GE Healthcare personnel and customers with Advance Service Limited License agreements must have the Service Software loaded before performing Restore System State (Table 3). If this condition is not met, Restore State will need to be performed again after the Service Software is loaded.

11 Service Software

Service software (Class C and M) applies only to GE Healthcare personnel and customers with an Advance Service Limited License agreement. Load service software per the instructions on the media.

12 Install Software Options

Notice Image
  • notice
  • For Perfusion and Denta Scan:
  • These options are not part of VOX Tool, they are individual options.
  • If you loaded software in a language other than English, please reconfig as root with Applications software down. Change the language to English and select Accept. Restart Applications software. Load Perfusion and Denta Scan as applicable. Failure to load these options in English will cause the options to be unusable.
  • Options must be loaded before Protocols.

  1. Insert the Options DVD-RAM in the SCSI Tower DVD RAM drive.

    note:

    If you do not have the Options DVD-RAM, then you can use the eLicense feature. Follow this link to the eLicense Page: http://egems.gehealthcare.com/elicense/index.jsp

  2. With Applications up, select the Service icon.

  3. Select Configuration.

  4. Select Install Options. The Example Software Options screen appears. (See Figure 28.)

  5. Select Install. The Select Mechanism box appears. (See Figure 29.)

  6. Select Permanent.

  7. Insert the Options DVD into the SCSI Tower. The Select Device box appears. (See Figure 30.)

  8. Select MEDIA.

  9. Select OK for DVD insertion.

  10. Software options available for installation are displayed on the options screen.

  11. Install applicable Options per specific order per Software Options Installation Order in Table 4. The order of installation is critical.

  12. Select Quit to exit the window when the process is complete.

  13. Select Quit again to exit Install Options window.

  14. A window pops-up displaying: “Application should be shutdown and restarted for installed/removed options to take effect.”

  15. Select OK.

    note:

    Options loaded via DVD or CD will NOT be saved to System State.

    Options loaded via e-License WILL be saved to System State.

  16. Press the button on the DVD-RAM drive on SCSI Tower to eject the option DVD.

  17. Close the Service Desktop window in the upper left corner of the screen.

  18. If the language was modified via a reconfig for options, re-perform the reconfig process at this time to re-select the preferred language.

13 Initial load of this software - Retro Recon / Customize Large Font

note:

This section should only be performed when INITIALLY LOADING this software, because the save was not being performed during the Save System State process for previous versions of software releases. If the user modified the Screen and Film Annotation Groups, these will need to be restored manually for the choices listed (Patient_Name, Patient_ID, or Accession_Number.)

The Customize Large Font information will be saved to System State later in this procedure.

The Reconstruction (not Scan) portion of the system is tested at this point via the Retro Recon Test (gold rat image is generated). Additionally, this image is required to access User Prefs.

  1. Select Recon Mgmt then Restart Queue on Scan monitor then Quit. The Display Monitor's FSA Box should show Idle (not Paused or Shutdown).

  2. At the Display monitor, select the Exam Rx icon.

  3. Verify the toggle switch is selecting Auto View Layouts.

  4. Select Auto View Layouts

  5. Select the “four-image” viewer box.

  6. Select Retro Recon on Scan monitor.

  7. Locate and select the gold rat Patient ID.

  8. Select Select Series.

  9. Select Confirm.

  10. Verify the image(s) reconstruct and are displayed without artifacts.

  11. Verify the Display monitor’s FSA Box reports successful completion of images.

  12. Select the Image Works icon. The Image Works Viewer appears. (See Figure 31.)

  13. Select Viewer.

  14. Click on gold rat image.

  15. Select User Prefs at the bottom of the Display monitor. The User Preferences screen appears. (See Figure 32.)

  16. Locate (at the top of the screen on the left) Screen box

  17. Select Customize Large Font. The Large Font Annotation Groups screen appears. (See Figure 33.)

  18. Click on the Annotation Group(s) desired.

  19. Select Ok to save changes. (Repeat steps 17- 20 for Film.)

  20. Select Apply to apply changes.

14 Flash Download

note:

The Flash Download takes 5 - 30 minutes, depending on which subsystem needs updating.

  1. If there are any issues with the FLASH Download Tool update, open a Unix Shell and try to ping the following. Ctrl+C and close the shell when done pinging each one.

    • ping  orp (Ctrl-C to stop ping)

    • ping  tgp (Ctrl-C to stop ping)

    note:

    Flash Download may take a second time before it is successful.

    note:

    If an issue exists with Flash Download, retry, then perform SYSTEM RESETS, SCAN, RUN and verify this passes, and view the log for errors.

  2. Select the Service Icon, Utilities, Install, FLASH Download Tool. (See Figure 34.)

  3. Select Update.

    note:

    Ignore any initial errors or TGP “unknown” messaging. This is not a problem.

  4. If a pop-up appears requesting the Collimator Serial Number, enter the Collimator Serial Number and select Accept.

    note:

    This pop up may not appear if the Collimator Serial Number was retrieved from the System State.

  5. Once the Gantry Hardware Flash Downloads successfully, select Dismiss.

15 Feature Installation

This section describes feature installation.

15.1 HIPAA

If HIPAA is turned ON, then configure it now. (Refer to HIPAA Configuration) When HIPAA configuration is complete, return to this procedure.

15.2 Product Network Filters (PNF)

When a Save System State is performed, all settings made in the PNF Tool are saved to that System State.

For general information on Product Network Filters, please see Product Network Filter Theory.

If you or your customer wishes to have Product Network Filters (PNF) configured, then proceed to Configure Product Network Filters now. When PNF configuration is complete, return to this procedure.

15.3 AW Direct Connect

If requested by the customer, configure AW Direct Connect, now. When configuration is complete, return to this procedure.

16 Connect HSP Cable and Restart the Operator Console

  1. Reconnect the Hospital Network (HSP) Ethernet cable at the Operator Console's rear bulkhead. (See Figure 3.)

  2. Select the Shutdown icon, Restart, then OK.

  3. When Apps starts up, the Admin screen will appear if “HIPAA Present” was set to On during the Application LOAD process. The admin screen requires the following input:

    • Operation:   Login

    • Username:   root

    • Password: <password>

      note:

      If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

    • Select OK.

  4. Wait for the system to fully reboot with Applications software fully up before proceeding.

17 Tube Identification Information

note:

The software checks to see if a GE-supplied tube is present on the system. The check is done via the Tube ID board. This is an automatic feature, so no action is required by the service personnel. If the Tube ID board is not working, Tube Identification Certification must be performed manually to avoid constant pop-up messages. Please refer to the following link: Tube Install Certification

If a non-GE supplied tube is used, GE cannot assure that the system performance will conform to specifications.

18 Service Pack Load

The initial release of a Service Pack CD may not contain any patches. Service Pack CDs will include any new patches and all older patches that are still applicable. If a site is required to uninstall a Service Pack, the previous Service Pack may need to be installed. Therefore, retain the earlier version of the Service Pack.

Refer to instructions (sometimes inside the jewel case, as a Class A instruction, or FMI) and load the most current Service Pack at this time.

note:

If Service Pack questions arise, contact Local GE Service.

  1. Open a Unix Shell.

  2. If Application software is up, perform{ctuser@hostname}cleanMon.

  3. In the Unix Shell, become root:

    {ctuser@ hostname }   su  -

  4. Password: <password>

    note:

    If the Password has not been modified by the site and is not known, contact Local GE Service.

  5. Perform the following steps to install the Service Pack CD:

    1. [root@ hostname ]# start_udev

    2. A message will return: OK

    3. Wait 15 seconds after the OK is returned, then type the following install script:

      [root@ hostname ]# patch_install -c

      note:

      If the Service Pack fails to install, perform [root@hostname]#start_udev. Wait 15 seconds after OK, then retry the Service Pack.

      Any patches on the Service Pack CD will be listed. Before installation of each patch, the window will wait for user's confirmation as follows:

      I will install update Patch Name , is this ok ? [y/n]

    4. Input y to install this patch or n to cancel installation of this patch.

    5. After installing the Service Pack CD, type patch_status in the Shell window to determine which Service Pack patches were installed (if any). The following is an alternate command to verify the Service Pack load:

      [root@ hostname ]# showprods | grep  -i ServicePack

    6. Type:[root@hostname]#reboot

      note:

      A reboot is always required after a patch is installed. Additional processes may be required for installing certain Service Pack media. Refer to the instructions sent with the Service Pack.

19 Apps Startup

  1. Type: {ctuser@hostname}st

  2. When Apps starts up, the Admin screen will appear if “HIPAA Present” was set to ON during the Application LOAD process. The Admin screen requires the following input:

    • Operation:   Login

    • Username:   root

    • Password: <password>

      note:

      If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

    • Select OK.

  3. A pink pop-up Attention Message appears: Waiting for System Startup….

  4. Select OK for FastCal and other message boxes that appear throughout the reboot process.

  5. Wait for the system to fully reboot with Applications software fully up before proceeding.

20 Additional Processes Required

The following subsections contain information that may or may not be fixed when Service Pack 2 (or greater) is loaded. Verify each subsection for your specific host type, and perform adjustments as required.

20.1 XW8000 and XW8200 Host Computer

20.1.1 Autovoice Settings (Fixed with Service Pack 2)

The Autovoice settings process must be performed for every LFC until Service Pack 2 is loaded. It is possible that after performing a LFC without Service Pack 2 (or greater) loaded, the system may exhibit two different problems related to Autovoice settings: Low Volume and / or Feedback (squealing or noise) through the speakers.

20.1.2 Volume Adjustment (Fixed with Service Pack 2)

If Autovoice volume is too low:

  1. Select the “Autovoice Volume” (“audioSetting”) tool from the Tool Chest menu to increase the volume as needed.

  2. Click Save, then OK. Changing Autovoice settings may result in feedback issues. If this occurs, proceed to Feedback Remediation (Fixed with Service Pack 2).

20.1.3 Feedback Remediation (Fixed with Service Pack 2)

If Autovoice feedback issues exist, perform the following steps:

  1. Open a Unix Shell.

  2. Type alsamixer, then Enter. The Autovoice Settings screen appears (Figure 35).

    note:

    Settings shown may not depict the final settings for your console. Settings vary from console to console.

  3. Press the right-arrow key to move the cursor selection to the PCM slider.

  4. Press the up-arrow key to increase the PCM setting to 100%.

  5. If feedback is heard, press the right-arrow key to move cursor selection to the Line slider.

  6. Press the down-arrow key to decrease Line setting until feedback is no longer heard.

    note:

    Do not mute the Line device as it is needed for Autovoice Record.

  7. When you have completed your adjustments, press Esc to exit AlsaMixer.

  8. If the Line setting was changed, then STOP. You have completed Autovoice setup. If the Line setting was not changed, select the Autovoice Volume tool from Tool Chest menu and click Save, then OK to save the PCM settings to file.

    note:

    If Line setting was changed and then the Autovoice Volume settings saved, the Line value set via AlsaMixer is reset to “61.” (It was overwritten by the “Save.”) Repeat steps 5 through 7 to adjust the Line settings.

20.2 XW8400 Host Computer (Needed when XW8400 is introduced)

20.2.1 Autovoice Settings

After Service Pack 2 is installed, if the Autovoice setting is equal to 85 (i.e. factory default setting), then do not perform volume adjustment. If the Autovoice setting is higher or lower than 85, then it is recommended to perform volume adjustment.

20.2.2 Volume Adjustment

  1. Select the “Autovoice Volume” (“audioSetting”) tool from the Tool Chest menu to increase the volume as needed.

  2. Click Save, then OK.

20.3 Gantry Tilt Adjustment - Initial Load Only

The 07MW software/firmware was changed on all 7.X and 5.X gantries to catch systems with tilt speeds grossly out of spec. Since the gantry Home Zero point is reliant upon the Tilt Speed adjustment, if the Gantry Tilt Speed is too slow or too fast the gantry Zero will be incorrect.

The 5.X and 7.X gantry tilt design has two Zero Home positions, one from the Forward direction and one from the Backwards tilt direction. The two Home positions are slightly different, but at both Home locations the gantry display reads 0.0 degrees. The two Home Positions are mainly driven by the coasting-to-a-stop motion of the gantry. When the Forward and Backward Tilt speeds are set as close to 1 degree per second as possible, it ensures the two Zero Home positions are the same.

Resolution: The Tilt speed needs to be adjusted to 1 degree / second

The following procedure can be used for 5.X systems. (For additional methods see the Hydraulic Tilt Motor Speed Adjustment (Figure 36) in the Systems Service Manual.)

  1. Set the Service Switch to Service mode (Figure 37).

  2. Using the gantry controls, tilt the gantry forward and back and the gantry speed will be displayed on the gantry control (Figure 38).

21 System Sanity - Scanning & Network Operation

  1. Select Daily Prep on the Scan monitor.

  2. Perform Tube Warmup.

  3. Select Quit when tube warm-up is completed.

  4. Successfully perform a Scout scan.

  5. Successfully perform a Helical scan.

  6. Successfully perform an Axial scan.

22 Save System State

To Save System State, follow the procedure described in Table 2.

23 Finalization

note:

All PNF settings were restored from System State. Disabling telnet in PNF is recommended. Remote telnet is disabled for security reasons; PNF acts as your firewall.

  1. Set telnet via Product Network Filters (PNF) per customer request.

  2. If the site has DICOM print configured, perform DICOM print to confirm network operation with the PNF firewall set to ON.

  3. If you have archive server configured, perform image archive & retrieve to confirm network operation with the PNF firewall set to ON.

  4. Remove the System State from the SCSI Tower DVD drive.

  5. Verify that all software media has been removed from the DVD tray in the Host Computer and SCSI Tower.

  6. Verify that all floppies have been removed from the floppy drive in the Host Computer.

  7. Verify all software media has been removed from the DVD tray in the DARC Node.

  8. Verify that the DARC/IG Troubleshooting Cable is not connected to Scan or Display Monitors.

    note:

    The troubleshooting cable (used for DARC and IG Node) must not be connected at either end of this cable except when troubleshooting. When connected to a monitor, the DARC/IG Node may take over the monitor, causing customer confusion. EMC requirements are violated if the troubleshooting cable is connected to either the DARC or IG Node.

  9. Verify that the DARC/IG Troubleshooting Video Cable is not connected to the rear of the DARC/IG Node.

  10. Replace the front and rear Operator Console covers.

  11. Remove any phantoms used during System Sanity Scanning.

  12. The LFC process is now complete.

24 Drift Setdate

A second setdate is required to calculate a drift adjustment value. Drift varies for each Host Computer. The usage of the system, internal Host Computer temperature, and the characteristics of the clock located on the Host motherboard can all affect the time drift. Currently, Engineering recommends waiting a minimum of 24 hours after the initial setdate. In the event that this 24-hour interval is not possible, perform setdate now. Understand that setdate may need to be performed more often at some sites.

The time entered must be based on the same clock source used during the initial setdate.

Open a Unix Shell and become root:

{ctuser@ hostname }   su  -

Password: <password>

note:

If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

Utilize the time from your laptop to perform setdate for drift:

[root@ hostname ]#   setdate 

Note: Type “q” to quit anytime. Enter to proceed: <Enter>

Note: TO BE ACCURATE, this tool will prompt you to enter the “Second”. Watch your clock or PC carefully to enter the proper value, and hit [Enter] at the right second to set the accurate time. Enter to proceed: <Enter>

Enter the current Year (1980-2030)[2007]:

Enter the current Month (1-12)[04]:

Enter the current Day (1-30)[14]:

Enter the current Hour (Military Time) (0-23)[18]:

Enter the current Minute (0-59)[13]:

Enter the current Second (0-59)[00]:

Updating the time on the OC and DARC, Please Wait...

Current OC date : Fri Apr 14 15:18:00 CDT 2006

Could not retrieve the DARC TImeZone.

Please make sure the TimeZones for the OC and DARC are the same.

Setdate completed with NO ERRORS.

[root@ hostname ]#

25 Restart the System before Customer Turnover

Notice Image
  • notice
  • NEVER Use CTRL - ALT - DELETE to reboot. This technique will NOT reboot all console subsystems, and as such is an unacceptable practice.

  1. Select the Service icon. On the Attention screen, select Shutdown, then Restart, and OK.

  2. If a Restart was not performed during the Tube Identification Certification process, the related tube pop-up messages shall be verified now beginning at Step 10 of “Tube Identification Certification.”

  3. When Apps starts up, the Admin screen will appear if “HIPAA Present” was set to ON during the Application LOAD process. The Admin screen requires the following input:

    • Operation:   Login

    • Username:   root

    • Password: <password>

      note:

      If the Password has not been modified by the site and is not known, the correct course of action is to contact Local GE Service.

    • Select OK.

  4. A pink pop-up Attention Message appears: Waiting for System Startup….

  5. Select OK for FastCal and other message boxes that appear throughout the reboot process.

  6. Wait for the system to fully reboot with Applications software fully up before proceeding.

26 Final Save System State

The System State may need to be saved again. Refer to Service Pack instructions. The System State must be saved after a new LFC and after the Service pack is installed. A Save System State is also required if additional processes were required because settings were not restored properly from the previous System State, or if the Service Pack corrections affected saved items. If in doubt, resave the System State at this time.

27 Smart Step Option (Fixed with Service Pack 2)

When using Smart Step Option, the cradle release button on the Handheld controller does not work without Service Pack 2 (or greater) loaded. Use the Cradle Release button on the gantry.

28 Appendix: Tables and Graphics

Figure 1. LightSpeed 7.X GOC5 Operator Console (non-Jarrell version)

Figure 2. ICOM Power LED

Figure 3. Rear Console Bulkhead

Figure 4. Attention Screen

Figure 5. Power Switch

Figure 6. Display Monitor Prompt Window

Figure 7. Warning Box

Figure 8. CT Software Installation Window

Figure 9. Install INFO Decision Box

Figure 10. Install INFO Valid System State Box

Figure 11. System Settings Screen

Figure 12. Preferences Settings Screen

Figure 13. Preferences Settings Screen (SP2)

Figure 14. Main Hardware Screen

Figure 15. Select Hardware Configuration.Screen

Figure 16. Hardware Settings Screen

Figure 17. Table Label/Rating Plate

Figure 18. Network Settings Screen

Figure 19. Station Name - Network Settings Screen

Figure 20. Install INFO Acceptance Window

Figure 21. Reboot Message Box

Figure 22. Reboot Decision Box

Figure 23. CT Software Auto- Start Disabled Box

Figure 24. Attention Window

Figure 25. SOL Service Error Box

Figure 26. VDARC BIOS Attention Box

Figure 27. DARC OS Load Information Box

Figure 28. Example Software Options Screen

Figure 29. Select Mechanism Box

Figure 30. Select Device Box

Figure 31. Image Works Viewer

Figure 32. User Preferences Screen

Figure 33. Large Font Annotation Groups Screen

Figure 34. Example Flash Download Screen

Figure 35. Autovoice Settings Screen

Figure 36. Hydraulic Tilt Motor Speed Adjustment

Figure 37. Service Switch Set to Service Mode

Figure 38. Gantry Speed Display

Figure 39. System State Save/Restore Screen

Figure 40. Save System State Box

Figure 41. Successful Completion Message

Figure 42. Restore System State Box