GE HiSpeed Diagnostics Manual

TechnicalPublications

Copyrighte 1998–2005 by General Electric Company

Operating Documentation

2202125Revision 29

CT HiSpeed SeriesDiagnostics

GE MEDICAL SYSTEMS DIAGNOSTICSCT HISPEED SERIES

2202125

a

REV 0

� THIS SERVICE MANUAL IS AVAILABLE IN ENGLISH ONLY.

� IF A CUSTOMER’S SERVICE PROVIDER REQUIRES A LANGUAGE OTHERTHAN ENGLISH, IT IS THE CUSTOMER’S RESPONSIBILITY TO PROVIDETRANSLATION SERVICES.

� DO NOT ATTEMPT TO SERVICE THE EQUIPMENT UNLESS THIS SERVICEMANUAL HAS BEEN CONSULTED AND IS UNDERSTOOD.

� FAILURE TO HEED THIS WARNING MAY RESULT IN INJURY TO THE SERVICEPROVIDER, OPERATOR OR PATIENT FROM ELECTRIC SHOCK,MECHANICAL OR OTHER HAZARDS.

� CE MANUEL DE MAINTENANCE N’EST DISPONIBLE QU’EN ANGLAIS.

� SI LE TECHNICIEN DU CLIENT A BESOIN DE CE MANUEL DANS UNE AUTRELANGUE QUE L’ANGLAIS, C’EST AU CLIENT QU’IL INCOMBE DE LE FAIRETRADUIRE.

� NE PAS TENTER D’INTERVENTION SUR LES ÉQUIPEMENTS TANT QUE LEMANUEL SERVICE N’A PAS ÉTÉ CONSULTÉ ET COMPRIS.

� LE NON-RESPECT DE CET AVERTISSEMENT PEUT ENTRAÎNER CHEZ LETECHNICIEN, L’OPÉRATEUR OU LE PATIENT DES BLESSURES DUES À DESDANGERS ÉLECTRIQUES, MÉCANIQUES OU AUTRES.

� DIESES KUNDENDIENST–HANDBUCH EXISTIERT NUR IN ENGLISCHER SPRACHE.

� FALLS EIN FREMDER KUNDENDIENST EINE ANDERE SPRACHE BENÖTIGT,IST ES AUFGABE DES KUNDEN FÜR EINE ENTSPRECHENDE ÜBERSETZUNGZU SORGEN.

� VERSUCHEN SIE NICHT, DAS GERÄT ZU REPARIEREN, BEVOR DIESESKUNDENDIENST–HANDBUCH NICHT ZU RATE GEZOGEN UND VERSTANDENWURDE.

� WIRD DIESE WARNUNG NICHT BEACHTET, SO KANN ES ZU VERLETZUNGENDES KUNDENDIENSTTECHNIKERS, DES BEDIENERS ODER DES PATIENTENDURCH ELEKTRISCHE SCHLÄGE, MECHANISCHE ODER SONSTIGEGEFAHREN KOMMEN.

� ESTE MANUAL DE SERVICIO SÓLO EXISTE EN INGLÉS.

� SI ALGÚN PROVEEDOR DE SERVICIOS AJENO A GEMS SOLICITA UN IDIOMAQUE NO SEA EL INGLÉS, ES RESPONSABILIDAD DEL CLIENTE OFRECER UNSERVICIO DE TRADUCCIÓN.

� NO SE DEBERÁ DAR SERVICIO TÉCNICO AL EQUIPO, SIN HABERCONSULTADO Y COMPRENDIDO ESTE MANUAL DE SERVICIO.

� LA NO OBSERVANCIA DEL PRESENTE AVISO PUEDE DAR LUGAR A QUE ELPROVEEDOR DE SERVICIOS, EL OPERADOR O EL PACIENTE SUFRANLESIONES PROVOCADAS POR CAUSAS ELÉCTRICAS, MECÁNICAS O DEOTRA NATURALEZA.

WARNING

AVERTISSEMENT

WARNUNG

AVISO


2202125

b

REV 0

� ESTE MANUAL DE ASSISTÊNCIA TÉCNICA SÓ SE ENCONTRADISPONÍVEL EM INGLÊS.

� SE QUALQUER OUTRO SERVIÇO DE ASSISTÊNCIA TÉCNICA, QUE NÃO AGEMS, SOLICITAR ESTES MANUAIS NOUTRO IDIOMA, É DARESPONSABILIDADE DO CLIENTE FORNECER OS SERVIÇOS DE TRADUÇÃO.

� NÃO TENTE REPARAR O EQUIPAMENTO SEM TER CONSULTADO ECOMPREENDIDO ESTE MANUAL DE ASSISTÊNCIA TÉCNICA.

� O NÃO CUMPRIMENTO DESTE AVISO PODE POR EM PERIGO A SEGURANÇADO TÉCNICO, OPERADOR OU PACIENTE DEVIDO A‘ CHOQUES ELÉTRICOS,MECÂNICOS OU OUTROS.

� IL PRESENTE MANUALE DI MANUTENZIONE È DISPONIBILESOLTANTO IN INGLESE.

� SE UN ADDETTO ALLA MANUTENZIONE ESTERNO ALLA GEMS RICHIEDE ILMANUALE IN UNA LINGUA DIVERSA, IL CLIENTE È TENUTO A PROVVEDEREDIRETTAMENTE ALLA TRADUZIONE.

� SI PROCEDA ALLA MANUTENZIONE DELL’APPARECCHIATURA SOLO DOPOAVER CONSULTATO IL PRESENTE MANUALE ED AVERNE COMPRESO ILCONTENUTO.

� NON TENERE CONTO DELLA PRESENTE AVVERTENZA POTREBBE FARCOMPIERE OPERAZIONI DA CUI DERIVINO LESIONI ALL’ADDETTO ALLAMANUTENZIONE, ALL’UTILIZZATORE ED AL PAZIENTE PERFOLGORAZIONE ELETTRICA, PER URTI MECCANICI OD ALTRI RISCHI.

ATENÇÃO

AVVERTENZA


2202125

c

REV 0

IMPORTANT! . . . X-RAY PROTECTION

X-ray equipment if not properly used may cause injury. Accordingly, the instructions herein contained shouldbe thoroughly read and understood by everyone who will use the equipment before you attempt to place thisequipment in operation. The General Electric Company, Medical Systems Group, will be glad to assist andcooperate in placing this equipment in use.

Although this apparatus incorporates a high degree of protection against x-radiation other than the useful beam, nopractical design of equipment can provide complete protection. Nor can any practical design compel the operator totake adequate precautions to prevent the possibility of any persons carelessly exposing themselves or others toradiation.

It is important that everyone having anything to do with x-radiation be properly trained and fully acquainted with therecommendations of the National Council on Radiation Protection and Measurements as published in NCRP Reportsavailable from NCRP Publications, 7910 Woodmont Avenue, Room 1016, Bethesda, Maryland 20814, and of theInternational Commission on Radiation Protection, and take adequate steps to protect against injury.

The equipment is sold with the understanding that the General Electric Company, Medical Systems Group, its agents,and representatives have no responsibility for injury or damage which may result from improper use of the equipment.

Various protective material and devices are available. It is urged that such materials or devices be used.

��

All electrical installations that are preliminary to positioning of the equipment at the site prepared for the equipment shall beperformed by licensed electrical contractors. In addition, electrical feeds into the Power Distribution Unit shall be performedby licensed electrical contractors. Other connections between pieces of electrical equipment, calibrations, and testing shallbe performed by qualified GE Medical personnel. The products involved (and the accompanying electrical installations) arehighly sophisticated, and special engineering competence is required.

In performing all electrical work on these products, GE will use its own specially trained field engineers. All of GE’s electricalwork on these products will comply with the requirements of the applicable electrical codes.

The purchaser of GE equipment shall only utilize qualified personnel (i.e., GE’s field engineers, personnel of third-partyservice companies with equivalent training, or licensed electricians) to perform electrical servicing on the equipment.


2202125

d

REV 0

DAMAGE IN TRANSPORTATION

All packages should be closely examined at time of delivery. If damage is apparent, have notation “damage inshipment” written on all copies of the freight or express bill before delivery is accepted or “signed for” by a GeneralElectric representative or a hospital receiving agent. Whether noted or concealed, damage MUST be reported to thecarrier immediately upon discovery, or in any event, within 14 days after receipt, and the contents and containers heldfor inspection by the carrier. A transportation company will not pay a claim for damage if an inspection is not requestedwithin this 14 day period.

Call Traffic and Transportation, Milwaukee, WI (414) 827–3449 / 8*285–3449 immediately after damage is found. Atthis time be ready to supply name of carrier, delivery date, consignee name, freight or express bill number, itemdamaged and extent of damage.

Complete instructions regarding claim procedure are found in Section “S” of the Policy & Procedure Bulletins.

OMISSIONS & ERRORS

GE personnel, please use the GEMS CQA Process to report all omissions, errors, and defects in this documentation.Customers, please contact your GE Sales or Service representatives.

CAUTION

Do not use the following devices near this equipment. Use of these devices near this equipment could causethis equipment to malfunction.

Devices not to be used near this equipment:

Devices which intrinsically transmit radio waves such as; cellular phone, radio transceiver, mobile radio transmitter,radio–controlled toy, etc.

Keep power to these devices turned off when near this equipment.

Medical staff in charge of this equipment is required to instruct technicians, patients an��

��


2202125

A

REV 29

LIST OF EFFECTIVE PAGES

Tab – Section Page REV

– Title page

Title page rear

29

blank

(Warning and other impor-tant information)

a to d 0

(Revision Information) A to C 29

(System Notation (NP,NP+, ...)

i 12

1 (System) i to ii 26

Service Menu 1–1 to 1–90 29

Message Display 2–1 to 2–5 9

2 (Operator Console) i 25

LED Description 1–1 to 1–33 10

Host Processor Troubleshooting(O2)

2–1 to 2–11 25

Host Processor Troubleshooting(Linux PC)

3–1 to 3–4 25

3 (Table/Gantry) i 20


Power–on Test 2–1 to 2–5 9

Error Message 3–1 to 3–53 20

4 (DAS/Detector) i 8

Channel – Ring Radius Table 1–1 to 1–21 28

LED Description 2–1 4

5 (X–ray Generator) i to ii 21


Errors, Diagnostics &Troubleshooting (NP, NP+, NP+Twin)

2–1 to 2–40 29

Errors, Diagnostics &Troubleshooting (NP++, NP++Twin)

3–1 to 3–45 29

Errors, Diagnostics &Troubleshooting (for p5.4 or laterJEDI Software)

4–1 to 4–47 29

6 (PDU) i 18

LED Description (for PDU2) 1–1 to 1–2 19

AppendixSymbols and Classification A–1 to A–4 13

– Blank/Rear cover –


2202125

B

REV 29

REVISION HISTORY

REV Date Primary Reason for Change

29 07/25/04 System Changed: Troubleshooting for IQ Performance (sec. 1).

X–ray Generator Added: Notes for 313H, 316H, and 317H errors (Sec2, 3, 4)

28 11/30/04 DAS/Detector Corrected: Ring Radius Cross Reference for Twin (Sec. 1)

27 11/30/03 System Added: Note for H/W inventory (sec1)

T/G Added: LED description (sec.1)

26 9/11/03 System Added: IQ performance tool analysis (Sec 1)

25 6/4/03 System Modified: H/W Diagnostics (Sec1)

OC Added: Host Processor Troubleshooting (Linux PC) (Sec2, Sec 3)

24 4/10/03 System Corrected: Scan Analysis (Sec 1)

X–ray Generator Corrected: 1401H battery life–time (Sec2, 3, 4)

23 12/11/02 System Corrected the calculation for mA smudge (Sec. 1).

Operator Console –

Table/Gantry –

DAS/Detector –

X–ray Generator –

PDU –

Appendix –

22 9/019/02 Operator Console Added: RTC battery troubleshoot (sec 2).

21 7/01/02 DAS/Detector Added: Channel No table for Twin (sec 1)

X–ray Generator Added: 0402H error information (sec 2)

Updated: 70–0501H error code (DC bus out of range). (Sec. 2, 3, 4)

20 4/15/02 System Updated: Twin information for IQ scan (Sec. 1).

Operator Console –

Table/Gantry Corrected the applicable system version information for error messages (Sec. 4).

19 11/22/01 PDU Added the RMT board picture (Sec. 1).

18 10/04/01 PDU Added this new tab (PDU).

17 8/22/01 X–ray Generator Added explanations to 30–0324H error (Sec. 3).

16 8/10/01 System Updated: V/R 6 service tools (Sec. 1).

Table/Gantry Updated the error message information for V/R 6 (Sec. 3).

15 4/19/01 System Added: Update System Log Notice

14 3/09/01 System Changed: Service menu for V/R 5.5 (sec1)


2202125

C

REV 29

REVISION HISTORY (continued)

REV Date Primary Reason for Change

13 12/08/00 System Colored: Sec. 1.

Operator Console Colored: Sec. 2.

X–ray Generator Colored: Sec. 1, 2, 3, 4.

Appendix Colored: Appendix A.

12 10/25/00 X–ray Generator Updated the descriptions–which section is applicable to which systems (Sec. 2, 3, 4).

11 8/31/00 System Added (within Sec. 1): View log file note on GSA, Z–axis collimation Diag.

DAS/Detector Added the cross reference tables for Twin systems (Sec. 1).

10 8/15/00 System Added: Scan Analysis – Z–Axis Tracking (Sec. 1).

Operator Console Added: New DASM information (DASM II–VDB (2191523–3), DASM II–LCAM (2191524–2)) (Sec.1).

9 7/03/00 System Adopted the new revision control for Sec. 2. Added a note for Raw Data Functions.

Operator Console Adopted the new revision control for Sec. 1. Added other error message information to IDE tests.

Table/Gantry Adopted the new revision control for Sec. 1, 2.

X–ray Generator Adopted the new revision control for Sec. 2, 3, 4.

8 5/18/00 – Added Twin system related information.

7 4/20/00 – JEDI p5.4 software.

6 2/25/00 – Tube spits log description; Host Processor Troubleshooting, Service Menu

5 12/17/99 – Service Tool for V/R 4.1; Added XG sections.

4 10/19/99 – Corrected Pin numbers in Ring Radius Charts; Corrected and added LED descriptions; AddedOGP Board Power–on Test; Added NP++ XG diagnostics.

3 2/25/99 – Added error codes and power on diagnostics to X–ray Generator.

2 7/10/98 – Added MTF Survey; Added TGP LED and Power–on test descriptions; Updated XG LED descrip-tions.

1 4/07/98 – Updated ‘Service Menu.’ Initial pages for the DAS/Detector tab.

0 3/27/98 – Initial release.


2202125

D

blank


2202125

i

REV 11

SYSTEM NOTATION (NP, NP+, ...)

Hardware Constitution of NP, NP+, NP++, and Twin

According to system models or customer options installed on the system, a number of system specifications or func-tions available may differ from system to system; such are:

� Selectable scan times, MA values, FOV dimensions

� ‘Remote Tilt’ function

� Number of arrays of DAS/detector units, i.e., single or twin DAS/detector subsystem

� ...

However, the ‘HiSpeed’ series scanners are principally grouped into four, for which the following notations are givenrespectively:

‘NP’, ‘NP+’, ‘NP++’ and ‘Twin’In this ‘Diagnostics’ manual, these notations NP, NP+, NP++, and Twin are used to describe differences among thesefour groups and to make descriptions of this manual read simpler.

(However, ‘Twin’ is further grouped into two, that is, ‘NP+ Twin’ and ‘NP++ Twin’. In general outline,NP+ Twin systems are NP/NP+ systems with a twin DAS/detector, and NP++ Twin systems are NP++ systemswith a twin DAS/detector. These notations also will be used when required.)

The following table describes the constitution of the major hardware of NP, NP+, NP++, and Twin.

Hardware Constitution

Subsystem/Component NP NP+ NP++ NP+ Twin NP++ Twin

OC – common

Gantry Mechanics – Position-ing Light

HalogenLamps

Laser

Mechanics – others common

Electrics Firmware only is different.

Table IMS(Intermediate Support)

Standard or Option Standard Standard orOption

Standard

Others common

DAS – common twin DAS

Detector – common twin detector

X–ray Generator – common (Jedi) NP++ Jedi Jedi NP++ Jedi

X–ray Tube – common (D3142T tube) D3152Ttube

D3142Ttube

D3152Ttube

PDU – common


2202125

ii

blank


2202125

SYSTEMi

REV 26

SYSTEM

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 – SERVICE TOOL 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 GENERAL 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1-1 Service Tool Structure 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2 Service Tool Index (Alphabetical Order) 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-3 Service Desktop User Interface (For V/R 5.5x or later ONLY) 1–7. . . . . . . . . . . 1-1-4 Home (For V/R 5.5x or later ONLY) 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-5 Accessing the System Message Log 1–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2 AUDIO CONTROL 1–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 AUTOMATED ALIGNMENT 1–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 DAS DATA TRANSFER TEST 1–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 DASM DIAG 1–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 GENERATOR TEST 1–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 GENERIC SYSTEM ANALYZER 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7-1 View Log Files 1–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-2 Format Raw Data 1–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7-3 Analysis 1–43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8 GETSTATS 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8-1 General 1–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8-2 Command 1–49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9 HEAT SOAK 1–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 H/W DIAGNOSTICS 1–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-10-1 Diagnostics 1–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10-1-1 Interactive Test 1–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10-1-2 Offline Test 1–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-11 IMAGE PROFILE 1–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12 MTF SURVEY 1–61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13 OFFLINE SCAN 1–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-13-1 T/G Control 1–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14 RAW DATA FUNCTIONS 1–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15 SCAN ANALYSIS 1–69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-15-1 Z–Axis Tracking 1–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15-2 DD 1–78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-16 SERVICE CALIBRATION 1–82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17 SERVICE MANUAL 1–83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18 SHUTDOWN 1–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-18-1 Application Shutdown 1–84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19 SYSTEM BROWSER 1–85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20 UPDATE SYSTEM LOG 1–88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21 USER PREFERENCE 1–89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22 VECTOR CONVERT 1–90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

SYSTEMii

REV 26

TABLE OF CONTENTS (Continued)

SECTION PAGE

SECTION 2 – MESSAGE DISPLAY 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 MESSAGE DESKTOP 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 ERROR LOG VIEWER MESSAGE FORMAT 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

SYSTEM1–1

REV 29

SECTION 1 – SERVICE TOOL

1-1 GENERAL

Click on the ‘Service’ icon to display the Service Tool desktop.

1-1-1 Service Tool Structure

Error Logs

OC SYSLOG (System Browser)ViewlogAW Logs (System Browser)StorelogSystem Browser (All features)Tube Usage (System Browser)Update System LogShell

DiagnosticsOffline ScanGeneric System AnalyzerScan AnalysisAuto ScanDAS Data Transfer TestGenerator Test (Shutdown)H/W Diagnostics (Shutdown)View H/W DiagDASM DiagVector ConvertSnapStateVerify SecurityShell

Image QualityGeneric System AnalyzerScan AnalysisImage ProfileMTF SurveyInstall SMTPE ImageVerify SecurityShell

CalibrationAutomated AlignmentService CalibrationCT Number AdjustmentGravity SAGHeat SoakAudio ControlsVerify SecurityShell

ConfigurationUser PreferenceOC Hardware Info (System Browser)Software VersionVerify OptionsVerify SecurityShell

ReplacementOffline ScanGeneric System AnalyzerGenerator Test (Shutdown)Automated AlignmentService CalibrationCT Number AdjustmentVerify SecurityShell

Toolboxes/UtilitiesService ManualRaw Data FunctionIncrement Exam#SavestateSelective SaveSnapStateCalculatorCalendargetStatsShutdown –Application ShutdownVerify SecurityShell

PMOffline ScanGeneric System AnalyzerAudio ControlsSystem BrowsergetStatsService NotepadVerify SecurityShell

The Tools for V/R 5.5x or later ONLY:

Depending on the system version, some tools cannot be used. (Seetable 1–1, Service tool index, Version compatibility.)

HomeSee Section 1-1-4.


2202125

SYSTEM1–2

REV 29

1-1-1 Service Tool Structure (Continued)

System Func. CheckOffline ScanAuto ScanGenerator Test

Service AdjustmentService CalibrationAutomated AlignmentCT Number AdjustmentAudio ControlHeat SoakGravity sag

Diagnostics & analysisH/W DiagnosticsDAS Data Transfer TestGeneric System AnalyzerScan AnalysisMTF SurveyImage Profile

UtilitiesRaw Data FunctionsInstall SMPTE imageVector ConvertIncrement Exam#User PreferenceSnapStateViewlogSaveStateVerify SecurityService ManualSelective SaveDASM DiagUpdate System Log

System ToolsCalculatorCalendarUnix ShellSystem BrowserApplication Shutdown

InformationSoftware Version

The Tools for V/R 5.0x or lower ONLY:Depending on the system version, some tools cannot be used. (Seetable 1–1, Service tool index, Version compatibility.)


2202125

SYSTEM1–3

REV 29

1-1-2 Service Tool Index (Alphabetical Order)

The service tools provided are listed in Table 1–1, in alphabetical order.

Table 1–1 Service Tool Index (Alphabetical Order)

Tool Description System Soft-ware V/R

Section No.(for details)

Application Shutdown Terminates the application software to enter the desk-top menu.

All 1-18

Audio Controls X–ray On Sound Params, Alert Sound Params,Autovoice Volume, CD Sound Volume

All 1-2

Auto Scan You can perform continuous scans automatically withseveral protocols, but this is the tool for engineeringevaluation, not for FE (field engineer).

All –

Automated Alignment Tube Rough ISO Alignment, Tube ISO Alignment, Ra-dial Alignment, Bowtie Filter Alignment, Phantom Cen-tering, Tube POR Alignment

All 1-3

AW Logs (SystemBrowser)

Shows log files of ISO LOGS in System Browser. 5.50 or later 1-19

Calculator Provided functions:

x, /, +, –, 1/x, x^2, SQR, sin, cos, tan, log, ln, y^x, x!, (,), etc.

All –

Calendar Monthly display. All –

CT Number Adjustment KV values only can be selected (80 kV, 120 kV,140kV). It takes approx. 30 minutes to complete it.

Refer to Functional Check/Adjustment.

Note: If you do not click on Confirm in the scan con-firm screen within 15 minutes, Time–out occurs.

All –

DAS Data Transfer Test Tests that test pattern data is correctly sent to the op-erator console.

All 1-4

DASM Diag Analyzes communication status between the HOSTcomputer and DASM or between the HOST computerand camera.

5.00 or later 1-5

Generator Test Retrieve JEDI Error Log, Saved RAM upload, SavedRAM download, kV Diagnostics, Heater Diagnostic,Rotor Diagnostic, (others)

All 1-6


2202125

SYSTEM1–4

REV 29




Generic System Analyz-er

View Log Files

Tube Usage Log

Tube Spits Log

Bad Raw Log

All 1-7

Format Raw Data

Fan Data

DAS Data

Analysis

View Raw Data

View Vector

Calculations

getStats Allows you to know the Gantry revolution and tubespits.

5.50 or later 1-8

Gravity sag Allows you to perform a Gravity sag procedure easily.Refer to Functional Check/Adjustment, System, X–rayAlignment, Gravity sag.

4.00 or later –

Heat Soak Scan protocols (Scan Group# 1 ∼ 7) are programmedfor heat soak scans.

All 1-9

H/W Diagnostics Diagnostics:

Diagnostics for operator console boards and devicesare provided. Read first Cautions written in Section1-10, H/W Diagnostics, when performing safety test.

All 1-10

View Log:

Displays diagnostics related logs.

Image Profile The graphical profile data on selected line of the imagecan be displayed. Horizontal, vertical, and free direc-tion of a line can be selected.

4.00 or later 1-11

Increment Exam# Increments the exam No. All –

Install SMPTE image Installs the SMPTE image (and QA images for V/R 5.5or later) to the OC.

For procedures to install and display the images, referto Functional Check/Adjustment, Introduction, Com-mon Procedures, Basic Operation.

All –

MTF Survey Calculates the image spatial resolution performancedata of the system.

All 1-12

OC Hardware Info (Sys-tem Browser)

Shows log files of OC Info in System Browser. 5.50 or later 1-19


2202125

SYSTEM1–5

REV 29




OC SYSLOG (SystemBrowser)

Shows log files of SYSLOG OC in System Browser. 5.50 or later 1-19

Offline Scan Technic – Scan Type

Axial, Helical, Cine, Scout, Stationary,T/G Control

All 1-13

Raw Data Function For raw data save/load using an MOD. All 1-14

Savestate Saves/restores scan protocols, calibration files,autovoice data, and other data to/from an MOD.

All –

Scan Analysis Analyzes the raw data so that the scan header or calvector can be displayed.

4.10 or later 1-15

Selective Save Saves/restores selectively scan protocols, calibrationfiles, or autovoice data, to/from an MOD.

All –

Service Calibration Auto Sequence 1 ∼ 5, Q Cal, XT Cal, AV Cal, DG Cal,Asymmetric Seq

All 1-16

Service Manual Displays the contents of CT service CD–ROMs. 4.00 or later 1-17

Service Notepad Allows you to make/save a memo.

The memo can be seen in the message log report(Section 1-1-5). In addition, this information is re-corded in the Health page file so that it will be reportedto the OLC via InSite.

5.50 or later –

(Unix) Shell Unix Shell window is displayed. To terminate the shellwindow, enter exit.

All –

Shutdown Includes Application shutdown. All 1-18

SnapState Collects information for debug purpose. All –

Software Version Shows the system name and software version.(e.g., ‘HiSpeed Series 5.01’)

For V/R 5.5 or later only, the detailed information of allsoftwares installed in the system appears. Whenchecking current software version only, see Home, OCApplication Software. (Section 1-1-4) To terminate thiswindow, enter Q.

All –

Storelog Saves core, log, and data file to the file, /usr/sc/log/xxxx.xxx for troubleshooting.

5.50 or later –

System Browser Shows the log files of GE System Log, SYSLOG_OC,IOS_LOGS, Tube_Usage, Run_time_stats, OC_Info,Config_Files, History_log, and Software_Health_Page.

4.10 or later 1-19


2202125

SYSTEM1–6

REV 29




Tube Usage (SystemBrowser)

Shows log files of Tube Usage in System Browser. 5.50 or later 1-19

Update System Log Updates ‘Tube Usage’ log, ‘Tube Spits’ log, or ‘BadRaw’ log.

All 1-20

User Preference Sets ‘Axial image direction’, ‘Gantry direction’, etc. All 1-21

Vector Convert Vectors: Warmup Whole, Warmup History, Hilight, Air& Ptm

All 1-22

Verify Options Shows the options which always have been installed.

To terminate this windows, click on Cleanup in theService desktop or select Quit from the pop–up menuof the left upper corner of the window.

5.50 or later –

Verify Security Displays information of Security Level, Key ExpirationDate, and UserID.

All –

View H/W Diag Views Diag Log, P–ON Test Log, SYSLOG, or HINVinventory.

5.50 or later –

Viewlog Views GE sys log files. The same log files as onesshown in the System browser are displayed.

All –


2202125

SYSTEM1–7

REV 29

1-1-3 Service Desktop User Interface (For V/R 5.5x or later ONLY)

When Starting Service Desktop:

When clicking on Service icon to start the service desktop, the Image works browser also start up and the ServiceDesktop hides behind it.

To display the Service Desktop fully, perform either of the followings:

� Click on Start SV Desktop button or

� Click on the border on the Service desktop

Click button.

Service DesktopClick border.

Cleanup

The Cleanup button on the bottom of the desktop cleans up any previously opened windows, and restores the desktopto its original state, rather than closing or dismissing each individual application visible on the Service Desktop.

The Cleanup button should be selected whenever the user is done with the Service Desktop or whenever it is desiredto get the desktops back to a known state.


2202125

SYSTEM1–8

REV 29

1-1-3 Service Desktop User Interface (For V/R 5.5x or later ONLY) (Continued)

Using the Mouse on the Service Desktop:

Use the mouse to access and operate diagnostics and tools, or open a shell and type/enter a UNIX command line.Use the mouse to make screen selections on the service desktop.

Typical mouse button functions:

Function Mouse Button to be used How?

Window Resize Left button Move the mouse pointer at the border of the window,then press and hold the left button and drag the cursorto resize the window.

Window Move Center button Move the mouse pointer at the border of the window,then press and hold the center button and drag thecursor to move the window.

1-1-4 Home (For V/R 5.5x or later ONLY)


2202125

SYSTEM1–9

REV 29

1-1-4 Home (For V/R 5.5x or later ONLY) (Continued)

System Information

Item Meanings

Facility This information is Hospital Name set in System Configuration –> System setting.

Suite Name This information is Host Name set in System Configuration –> Network setting.

System Type This information is Model Name set in System Configuration –> System setting.

System ID This information is Machine Number set in System Configuration –> System setting.

IP Address This information is IP Address set in System Configuration –> Network setting.

Access Level –

Software InstallationDate

This information is updated automatically when performing LFC or LFW. Note that thisis NOT updated when installing the patch software only.

DASM Camera When selecting System Configuration –> Camera Setting –> Laser Camera, “LaserCamera” is displayed.

DICOM NetworkCameras

This information is Device Files set in System Configuration –> Camera Setting –>DICOM Printer.

Installed Tube This is information recorded in the tube usage file.

This is automatically reset when performing Update system log –> Tube Usage (sec-tion 1-20) at tube replacement.

Tube Install Date This is information recorded in the tube usage file.

This is automatically reset when performing Update system log –> Tube Usage (sec-tion 1-20) at tube replacement.

Current System Status

Item Meanings

System Date To modify this information, use Application shutdown –> Date Setting.

System Time To modify this information, use Application shutdown –> Date Setting.

OC Application Soft-ware

The current application software version is displayed.

Next Patient Exam The next patient examination number is displayed.

Recon Status

Archive Status For a remote user only:The same information as the Scan top panel, illus-

Network StatusThe same information as the Scan top panel, illus-trated on the left, are displayed in these columns.

Filming Status


2202125

SYSTEM1–10

REV 29


System Health Information

Item Meanings

Total Gantry Revolu-tions

Indicates the Gantry rotation numbers in “Status” column. This indication can be resetusing getStats (section 1-8). The date when the counter was reset is displayed in “In-formation” column.

The rotation number is slightly less than the mechanical Gantry rotation counter locatednear the TGP board (a few %), because this software counter does NOT read all of Gpulse interrupt.

The data of rotation number is sent to the OC just when the Gantry stops.

Total Tube Spits Indicates total tube spits numbers currently.

This is automatically reset when performing Update system log –> Tube spits (sec-tion 1-20) at tube replacement.

IQ Performance Tool Status

This tools give us advance notice for IQ performance change.

For the system with V/R 5.5x or later, the two types of warm–up scan can be selected:

� Tube Warm–up: performs tube several warm–up scans. These can achieve 13% case temperature.

� Daily calibration (Warm up): performs conventional tube warm–up scans (tube warm–up scans:30% caseand calibration scans) plus IQ performance measurement scans. (For detail scan protocol, refer to IQperformance Measurement scan described below.)

So, whenever the daily calibration is performed, the IQ performance data are collected and analyzed automatically,and the results are stored in the file, then displayed on the “Status” column of the IQ Performance Tool Status. The“Information” means the date when the status has been determined.The three types of status are displayed:

NoteThe results are stored as a vector file, so that they can also be seen using Scan Analysis, DD fileanalysis function. (For mA Smudge and Scan Time Smudge Only, they can not be seen, becausethe files can NOT be made.) The files is stored up to 5MB. In excess of 5MB, the directory of the files will be cleaned up whenexecuting this tool. Since the vector files of approx. 400 KB per daily calibration are created, 10 days’data can be stored. However calculation in Scan Analysis reduces data to be stored.

� GREEN: displayed when the result is WITHIN allowable specifications. (Also refer to IQ performance toolspecifications.)

� YELLOW: displayed when the result is OUTSIDE OF allowable specifications. There is a possibility toaffect Image Quality. (Also refer to IQ performance tool specifications.)

� RED: displayed when the result is OUTSIDE OF allowable specifications. A serious Image Quality prob-lem might occur. (Also refer to IQ performance tool specifications.)


2202125

SYSTEM1–11

REV 29


IQ Performance Tool Service Recommended Action

When the IQ Performance Tool Status turns YELLOW or RED, perform the followings in a periodic maintenance.When the status turns in Yellow or Red but an IQ issue does not occurs, the urgent action is NOT required.

1. Check if a customer does not have any IQ problems.

2. Check the vector file(s) beyond tolerance level that have been gotten by the IQ performance test, using ScanAnalysis. Then detect and resolve problems according to the troubleshooting guide.

3. Perform the Calibration (Auto Sequence–1 calibration). The YELLOW indicators still exist.

4. Perform Auto CT Number Adjustment to remove the YELLOW indications (changed to all GREEN).

5. Perform Image Performance Test to check if no problem exists.

6. Perform the Daily calibration to verify that all of the IQ Performance Tool Status is GREEN.

IQ Performance Measurement Scan

The following scans are performed as IQ Performance Measurement scans.

Item Scan Type ScanTime

Thick-ness

kV mA Focus Rotor X–ray

Air Calibration 10mm Axial 1.0 10 120 30 Large ON ON

* Air Calibration 7mm Axial 1.0 7 120 40 Large ON ON



Offset SD/Mean Axial 0.8 1 0 0 Large ON OFF

Detector/DAS Linearity Stationary 1.0 3 120 60 Large ON ON



* AB Ratio Stationary 1.0 1 120 100 Small ON ON

* Z–axis stop movement Stationary 3.0 1 120 100 Small ON ON

Note: The air calibration renewal data are used for calculating air calibration drift.

For Twin Detector ONLY


2202125

SYSTEM1–12

REV 29


IQ Performance Tool Specifications

For equation for each item below, refer to IQ Performance Tool Analysis.

Item Meanings Specifications

Green Yellow Red

Offset Mean Validity of offsetMean value.

–1.0 ≤ Mean ≤ 1.0 –2.0 ≤ Mean ≤ 2.0 Mean < –2.0 orMean >2.0

Offset SD Validity of offset SDvalue.

SD ≤ 2.0 SD ≤ 3.5 SD > 3.5

Air Cal Drift 10000 Stability of 10 mmair calibration.

0.95 ≤ New/Old ≤1.05

0.90 ≤ New/Old ≤1.10

New/Old < 0.90 orNew/Old > 1.10

Air Cal Drift 7000 Stability of 7 mm aircalibration.



mA Smudge mA–dependent DASLinearity variation(Center sectiononly)

Differences between#25 and #26 (Cen-ter module) and be-tween #27 and #26≤ 500 ppm (0.05%)

≤ 1000 ppm (0.1%) >1000 ppm (0.1%)

mA Band mA–dependent DASLinearity variation(Total)

Difference amongchannels ≤ 1000

ppm (0.1%)

≤ 2000 ppm (0.2%) >2000 ppm (0.2%)

Scan Time Smudge Scan–time–depen-dent DAS Linearityvariation (Centersection only)

Differences between#25 and #26 (Cen-ter module) and be-tween #27 and #26≤ 500 ppm (0.05%)

≤ 1000 ppm (0.1%) >1000 ppm (0.1%)

Scan Time Band Scan–time–depen-dent DAS Linearityvariation (Total)

Difference amongchannels ≤ 1000

ppm (0.1%)

≤ 2000 ppm (0.2%) >2000 ppm (0.2%)

AB Ratio Q Channel(See Note below.)

A/B ratio (Q channel16 view smoothing)

≤ ± 5 % ≤ ± 10% > ± 10%

AB Ratio Center

(See Note below.)

A/B ratio (Centerchannel 16 viewsmoothing)

≤ ± 20% ≤ ± 30% > ± 30%

AB Ratio Last

(See Note below.)

A/B ratio (Lastchannel 16 viewsmoothing)

≤ ± 20% ≤ ± 30% > ± 30%

Note: The 1 ~ 250 View data are NOT used when calculating AB Ratio.


2202125

SYSTEM1–13

REV 29


IQ Performance Tool Analysis (How to calculate the status)

� Offset Mean/Offset SD (OffsetCheck as Scan Analysis file):Uses data of Offset SD/Mean scan (with Offset correction ON and with others OFF) .

–1 <= Mean <=1: test of DAS data normality, SD <= 2.0: test of offset noise

Mean (Vector 1) SD (Vector 2)

1

–1

2

0

Scale of y–axis is expanded to show the relationship with specifications.Set 1 shows the detector A side, set 2 shows the detector B side

� Air Cal Drift:Uses data of air calibration 3mm~10mm. After completion of calculation for renewing air calibration data,the new Vector is compared with the reference Vector (that is a Calibration Vector acquired at last CT #Adjustment) using the following equation.

New Vector / Reference Vector

Drift of Airdata at each thickness (current/previous) <= 5

10mm (Air Cal Drift 1000) 3mm (Air Cal Drift 3000)

1.05

0.95

1.05

0.95


2202125

SYSTEM1–14

REV 29


� mA Smudge:Uses data of Detector/DAS Linearity scan 60mA and 200mA to calculate linearity difference between #25and #26 (Center) modules of the DAS/Detector and difference between #27 and #26 modules.

How to Calculate:1. The Mean Vector is calculated after performing the Offset and Reference Correction of each scan data.2. Differences between modules are calculated using the following equations, then they are compared withspecifications.

Equation to calculate difference between #25 and #26 (Center) (#25•#26/#26):

��

��

��

��

��

��

��

��

��

��

�� Vec A: 60mA mean vector, Vec B: 200mA mean vector

Equation to calculate difference between #27and #26 (Center) (#27•#26/#26):

��

��

��

��

��

��

��

��

��

��

��Vec A: 60mA mean vector, Vec B: 200mA mean vector

#25 #26 #27

Difference between#26 and #27

Difference between#26 and #25

� Scan Time Smudge:Gap of center module vs neighobr module < 0.05% at 3 sec/1 sec mean.Uses data of Detector/DAS Linearity scan 1sec and 3sec to calculate linearity difference between #25 and#26 (Center) modules of the DAS/Detector and difference between #27 and #26 modules.

How to Calculate:Refer to mA Smudge other than Vec A and Vec B. (Vec A: 3 sec mean vector, Vec B: 1 sec mean vector)


2202125

SYSTEM1–15

REV 29


� mA Band:Uses data of Detector/DAS Linearity scan 60mA and 200mA to calculate linearity difference between adja-cent modules for all channels.

How to Calculate:1. The Mean Vector is calculated after performing the Offset and Reference Correction of each scan data.2. Difference between modules are calculated using the following equations, then they are compared withspecifications.

HPF (Vec A / Vec B)(Vec A: 60mA mean vector, Vec B: 200mA mean vector)

mA Band (maBand): Difference among channels (HPF)<0.1% at 60mA/200mA mean

mA Band

0.1% for band specification

� Scan Time Band:Uses data of Detector/DAS Linearity scan 1sec and 3sec to calculate linearity difference between adjacentmodules for all channels.

How to Calculate:Refer to mA Band other than Vec A and Vec B. (Vec A: 3 sec mean vector, Vec B: 1 sec mean vector)

Scan Time Band (ScanTimeBand): Difference among channels (HPF)<0.1% at 3 sec/1sec mean

Scan Time Band

0.1% for band specification


2202125

SYSTEM1–16

REV 29


� AB Ratio Q Channel/Center/Last:Uses data of AB ratio scan. For Q cal channel, Center Channel, and Last Channel, (kA–B) / (kA+B) arecalculated per view, then they are compared with specifications for16 view smoothing.

The channels to be used:Q cal channel: 1~3 ch, Center Channel: 396~398 ch, Last Channel: 791~793 ch

AB Ratio Q Channel: (kA–B)/(kA+B) <= 5% at each channel w/view smoothingAB Ratio Center: (kA–B)/(kA+B) <= 20% at each channel w/view smoothingAB Ratio Last: (kA–B)/(kA+B) <= 20% at each channel w/view smoothing

Qcal–ch

Center–ch

Last–ch


2202125

SYSTEM1–17

REV 29


� Z–axis step movement:The motor pulse and Z–channel Vectors are only calculated and stored.

Motor and Ratio of Z–movement fine are saved as the dd files. These files represent the input and outputof the Z–movement diver functions. There are no specifications. However, when the profile doesn’t showstair step in the graph bellow, Z–movement motor/driver/data transfer may have some issues.

Motor Z–movement

Ratio Z–movement


2202125

SYSTEM1–18

REV 291-1-4 Home (For V/R 5.5x or later ONLY) (Continued)

Fault Tree Analysis (FTA) For IQ Performance Troubleshooting

� Offset Mean


2202125

SYSTEM1–19


� Offset SD


2202125

SYSTEM1–20


� Air Cal Drift


2202125

SYSTEM1–21


� mA Smudge/mA Band:


2202125

SYSTEM1–22


� Scan Time Smudge/Scan Time Band:


2202125

SYSTEM1–23


� AB Ratio Q Channel/Center/Last:


2202125

SYSTEM1–24


Troubleshooting Guide For IQ Performance

� Baseline of this troubleshooting:Basically air calibration and phantom calibration (Auto Sequence 1) should be finished after YELLOW/RED flag. And still RED/YELLOW is existed, perform Auto CT Number Adjustment to remove the YEL-LOW indicators (changed to all GREEN). Then check this list in sequentail order. After fixing issues, Auto sequence–1 calibration and CT# adjustment are recommended to be done again.

� Sequence of checks:If the IQ performance status shows Yellow/Red, please proceed the checks from upper to lower in therelated item. If the cause is clearly linked to the specific description by ”how to confirm”, only this specifictroubleshooting can be done and there is no need to check other tests in the same item.

Item PossibleFailure (Cor-respondingFTA Item #)

How To Confirm Recommendation RelationshipWith Other Test

Item

OffsetMean

Data transferfrom DAS toOC (OM–2,3,4,5,6)

Check dd file to see profile ofoffset data. If the profile hasspike noises with regular pat-tern, data transfer failure issuspected. Confirm to checkthe raw data if it contains ab-normal view data. Pleasecheck DAS format data forthis view(Use GSA and select’service’ raw data on that dayby Format Raw Data. Selectseries 10 whose kv and mAare set to 0. Select DAS Dataand select ”View” with anyview# and Channel# of 865 todisplay data). If the last 4 dataof this view is not ”fff0 fff00000 0000”, it clearly showeddata transfer error in this view.

Perform DAS transfer test toisolated failure parts. Refer toSection 1-4 & Section 6–2.One of RF receiver, RF trans-mitter, DTRF2, DASIFN2 andsignal Tip kit has failure. Try toreplace each by each to getthe failure one.

Offset SD alsoshows Red or Yel-low. SometimeAIRCAL driftshows Red or Yel-low.

Irregular CAMboard channeloutput (OS–4)

Check dd file to see profile ofoffset data. If the profile hasabnormal profile with onechannel or 16 channels, CAMboard failure is strongly sus-pected.

Check other test items like AirCal Drift, mA Band, ScanTime Band.

Offset SD, AIR-CAL drift, mABand, scan timeband also showssome abnormalstatus for thesame channel.


2202125

SYSTEM1–25




Item

Offset SD Data transferfrom DAS toOC(OS–8,9,10,11,12)

Check dd file to see profile ofoffset data. If the profile hasspike noises with regular pat-tern, data transfer failure issuspected. Confirm to checkthe raw data if it contains ab-normal view data. Pleasecheck DAS format data forthis view(Use GSA and select’service’ raw data on that dayby Format Raw Data. Selectseries 10 whose kv and mAare set to 0. Select DAS Dataand select ”View” with anyview# and Channel# of 865 todisplay data). If the last 4 dataof this view is not ”fff0 fff00000 0000”, it clearly showeddata transfer error in this view.

One of RF receiver, RF trans-mitter, DTRF2, DASIFN2 andsignal Tip kit has failure. Try toreplace each by each (RF re-ceiver is the most probablefrom the statistics) to get thefailure one.

Offset mean alsoshows Red or Yel-low.Sometime AIRCALdrift shows Red orYellow.

Irregular CAMboard channeloutput (OS–4)

Check dd file to see profile ofoffset data. If the profile hasabnormal profile with onechannel or 16 channels, checkother test items like AIRCALdrift, mA Band, scan timeband. If all tests results in-clude irregular profile on thesame channel, CAM boardfailure is suspected.

Replace corresponding CAMboards.

Offset mean, AIR-CAL drift, mABand, scan timeband also showssome abnormalstatus for thesame channel.

GND noiseand Genera-tor noise(OS– 5,6)

Check dd file to see profile ofoffset data. If the profile haslarge periodical pattern orslope in one side of channeledge (1st channel side or thelast channel side), noise com-ing from GND line or radiationnoise from generator is sus-pected.

Check GND line connection ofDAS. Check if DAS cover iscorrectly attached. Scan 42cmPoly phantom (calibrationphantom) with 10mm 1i mode,while changing mA, scan time,kV. If there is no moire typeartifact, the system is judgedto be acceptable. If there isclear moire type artifacts seenin some of mAs and kV com-bination, generator change isrecommended.

Other test itemsare O.K.


2202125

SYSTEM1–26

REV 29




Item

Offset SD Unstable de-tector output(OS– 1,2,3)

Do offline offset scan withSTAY/rotor OFF and 1secrotation/rotor ON. If there issomewhat big difference in theresult, mechanical vibrationimpact to detector output issuspected.

Remove DAS–detector cablefrom DAS and check offset SDby offline scan. If the abnor-mal profile is disappeared,cable itself or cable setting isan issue. If there is nochange, issue seems to be in-side detector, which needs de-tector replacement.


Air CalDrift

Output shiftfrom beamcontrol shift(AC–11)

Check dd file to see profile. Ifthe profile is shifted over totalchannel, and all other slicethickness of AIRCAL drift datainclude similar shift, check ABratio Qcal ch profile. If theview data after 200 view is notconverging to 0 (+/–2%),beam control failure is sus-pected. In case of the correctAB ratio profile, move to thenext (unstable position of fo-cus ).

Check Motor Z–movement fileand Ratio Z–movement in ddof scan analysis. If both of theprofiles don’t have clear stairstep profiles, DAS CIF mayhave problem. In this case, tryto exchange CIF at first andcheck if any change. If onlyRatio Z–movement has notclear stair step in the profile,drive, z–axis movement mech-anism may have issue. In thiscase, driver or collimator ex-change is needed.

AB ratio and Z–movement havealso some issue.

Unstable posi-tion of focus(AC–12)

Above case with correct ABratio.

Do Daily Calibration again. If itchanges to GREEN this time,it is fixed. If still YELLOW/RED is displayed, recommendto do POW–>BOW– >QCALCH RATIO in the SV align-ment again. In this case cal-ibration should be doneagain(Auto sequence 5).

No other items outof specification.

Some objectremained inthe gantryopening (AC–6,7,8,9,10)

Check dd file and see the pro-file of 10mm slice thickness. Ifprofile contains partial drop orhump, check air scan image. Ifair image has CT# drop orraise in the center or has theband artifact, there is a possi-bility that something remainedor attached in the gantryopening. Check the mean pro-file of air scan by GSA wheth-er the data contains somedrop of the profile, which iscaused by existing material inthe X–ray path.

Look whether there is some-thing remaining in the scan-ning plane or not. Please wipegantry opening ring to removeany attached contrast media.If still mean profile of air scancontains some drop of profile,open gantry to clean collima-tor–bowtie–tube window. If thedata is not stable, there is apossibility of tube bubble in oil.In this case, tube replacementis needed.

Most of the case,daily calibrationscan stops with er-ror. But in somecase, scan finisheswithout error. Inthis case all thick-ness has RED orYELLOW, or onlylarger thicknesshas RED or YEL-LOW.


2202125

SYSTEM1–27




Item

Air CalDrift

DAS outputdrift(AC–3,4,5)

Check dd file to see profile. Ifthe profile has 1channel or 16channel drop or surge, do theair scan to check air meanprofile. If there is no clearirregular drop or surge for theissue channels in the profile,the drift of CAM board channelis suspected.

Check the temperature of theroom is appropriate( not toocold or too hot). Identify chan-nels which have abnormal driftand exchange CAM board ofthis channel with other CAMboard to confirm if it is reallyCAM board problem.

Sometime all thick-ness has RED orYELLOW, butsometime only thinthickness has REDor YELLOW.

Detector out-put drift (AC–1,2)

First confirm FOV43 air imageand see if it contains clear ringartifact. After this, check ifDAS is OK in the above pro-cess. If there is no impact ofCAM board exchange inabove item, try to connect De-tector cable to the AdjacentCAM board. If the abnormaloutput of channel moves 16chfrom the initial state, detectorchannel contains problem.

Detector replacement is rec-ommended but before thischange, please try to check inthe following items. 1) Check ifdetector heater is workingproperly by touching detectorsurface(35 degree C). 2) If itworks, do calibration se-quence 1 and check air imag-es several times for more thantwo hours. If ring artifact isdisappeared, move to themonitoring phase for severalweeks.

No other items outof specification.

mASmudge /mA Band

DAS linearityerror(mA–1)

Check to scan water 25cmwith1.5sec/120kV/10mm/170mA/LFOV and SFOV for 10 times.If CT# between ROI of cen-ter(7 pixel radius) and its out-side is within 3 for all 10slices, it is acceptable and noaction is to be taken. Butsome of the scan results ex-ceed this value, the mostprobable failure is CAM board.So first suspect CAM board.

Check dd profile and identifywhich part in the profile hasgap. Corresponding CAMboard is to be replaced tominimize the profile gap.

Sometime ’Scantime Smudge’ alsoshowed YELLOW/RED status.

Detector non-linearity error(mA–2,3)

Same as the above DAS test.If CAM boards replacementdoesn’t affect the results, thenext possible cause is detec-tor non–linearity.

Do Qcal ch ratio calibra-tion(under alignment menu)and do the full calibration (Se-quence 5) then do the 25cmwater phantom test, which isthe same as the above test. Ifthe situation doesn’t change,detector replacement is rec-ommended.

Sometime Scantime Smudge alsoshowed YELLOW/RED status.


2202125

SYSTEM1–28




Item

mASmudge /mA Band

Shift of beamcenter in Z–di-rection (mA–4)

Check if AB ratio is O.K. If it isO.K., and others are normal,very small drift of Qcal chan-nel is suspected.

Do Qcal ch ratio calibra-tion(under alignment menu)and do the full calibration (Se-quence 5) then do the 25cmwater phantom test, which isthe same as the above test. Ifthe situation doesn’t change,detector replacement is rec-ommended.

Shift of beamcenter by col-limator fail(mA–5)

Check if AB ratio is O.K. If it isnot O.K., follow the AB ratiotroubleshooting.

Refer to AB ratio. AB ratio and Z–movement havealso some issue.

Drift of beamquality (mA–6,7)

Air Cal Drift also has out ofspecification. or AIRCAL driftdd file contains some abnor-mal profile partially.

Check bowtie filter if it hascracks or shape change in thecenter part. If bowtie is O.K.and profile change is unstablein AIRCAL drift file, Tubebubble in oil is suspected. Inthis case, tube is to be re-placed.

Air Cal Drift hasYELLOW/REDstatus.

Scan TimeSmudge /Scan TimeBand

Same as mASmudge/mABand (ST–1,2,3)

Same as mA Smudge/mABand.

Same as mA Smudge/mABand.

Same as mASmudge/mA Band.

Large G–sagdifference be-tween 1secand 3 sec(ST– 4,5,6,7)

If only scan time smudge/bandis out of specification and mAsmudge/ band is O.K., check1sec and 3sec images ofcross talk phantom at centerposition( 1sec/ 120kV/10mm/100mA/SFOV and 3sec/120kV/10mm/30mA/SFOV). Ifthere is no big change ofthese phantom images and noclear center artifact, it is O.K.to do nothing and monitor thestatus. If there is center arti-fact only one of the images,do the recommended action.

Gantry unbalance or tube fo-cus movement by rotation issuspected. Tube replacementis recommended.



2202125

SYSTEM1–29




Item

AB Ratio Some objectremained onthe gantryopening inQcal channelpath (AB–6)

Check dd file to see profile af-ter 200 view is not stabilizedto zero position but has thelarge shift.

Look whether there is anythingremaining in the scanningplane or not. Please wipegantry opening ring to removeany attached contrast media.If the data is not stable, thereis a possibility of tube bubblein oil. In this case, tube re-placement is needed.


z–position er-ror (AB–3,4,5)

Check Motor Z–movement fileand Ratio Z–movement in ddof scan analysis. If both of theprofiles don’t have clear stairsteps, DAS CIF may haveproblem. In this case, try toexchange CIF at first and thencheck if any change. If onlyRatio Z–movement has notclear stair steps in the profile,drive, z–axis movement mech-anism may have issue. In thiscase, driver or collimator ex-change is needed.

See left column. All items exceptoffset mean/SDmay have YEL-LOW/RED.

Beam positionerror in Z bytube(AB–2)

Check dd file to see if any ab-normal drop or hump exists inprofile. If it exists, do severalphantom scans (water 25cm)to check if unstable dark orwhite partial area appears ornot some of many images.When this artifact is recog-nized, tube bubble in oil issuspected.

Replace tube. Air Cal Drift hasYELLOW/REDstatus in somecase.


2202125

SYSTEM1–30

REV 29

1-1-5 Accessing the System Message Log

To display the System Message Log Report, click the status message area on the desktop, then click on View Log.

Click thismessagearea.


2202125

SYSTEM1–31

REV 29

1-2 AUDIO CONTROL

Table 1–2 Audio Control

Audio Adjustable Parameter

X–ray On Sound Params Volume, Pitch, Length

Alert Sound Params Volume, Pitch, Length

Autovoice Volume Volume

CD Sound Volume Gantry Volume, Operator Console Volume


2202125

SYSTEM1–32

REV 29

1-3 AUTOMATED ALIGNMENT

Table 1–3 Automated Alignment

Automated Alignment Menu(Sequence)

Displayed Instruction

Tube ISO Alignment Air Scan → Pin Scan

[Adjust Tube position without Bowtie Filter]

Tube Rough ISO Alignment Air Scan → Pin Scan

[Adjust Tube position without Bowtie Filter]

Radial Alignment Air Scan → Rad Pin Scan

[Adjust Detector position without Bowtie Filter]

Tube Alignment must be completed before Radial Alignment.

Bowtie Filter Alignment Air Scan [without BTF] → Air Scan [with BTF]

Adjust Bowtie Filter position.

Phantom Centering –

yste

m

POR Alignment Filmless POR,Refer to Functional Check/Adjustment, System, X–ray alignment, PORfor Twin System.

Twin

Sys

BOW Alignment When POR is correctly adjusted, then filmless BOW (Beam–ON–Win-dow) can be performed. Measure the three points of the channel bandsand move the Detector to align the wave is just on the 0 line. In this ad-justment, vertical axis is normalized in value so that center is 0 and Max,Min is 1 and –1.Refer to Functional Check/Adjustment, System, X–ray alignment, BOWfor Twin System.

Q–cal Channel Ratio Refer to Functional Check/Adjustment, System, X–ray alignment, Q–calChannel Ratio.

NoteThe Tube Rough ISO Alignment and Radial alignment are rarely performed. Only when looseningthe detector locking screw, they must be performed.


2202125

SYSTEM1–33

REV 29

1-4 DAS DATA TRANSFER TEST

Table 1–4 DAS Data Transfer Test

Test Parameter to beSpecified

Selectable Parameter

Test Mode: Bit by Bit Normal, Infinite

Scan Mode Stationary Scan, Rotate Scan

Scan Time 0.8 (or 0.7, if a 0.7 sec option is installed), 1.0, 1.5, 2.0, 3.0, 1.0 <–> 2.0Alternate, Sequential (All)

No. of Scan (arbitrary)

No. of Test (arbitrary)

(The total number of scans performed will be (No. of Scan) X (No. ofTest).)

Until errors occur.

(arbitrary)

(The test scans will be terminated after the specified number of errorsoccur.)

Test Results

[Result of Comparison] → [View Log]:Select either of the following to view test results previously performed:

‘Das Data Transfer Test Log1’‘Das Data Transfer Test Log2’‘Das Data Transfer Test Log3’


2202125

SYSTEM1–34

REV 29

1-5 DASM DIAG

This tool analyzes communication status between the HOST computer and DASM or between the HOST computerand camera. The following tests are performed continuously, then the results are displayed.

� hinv:Display hardware configuration information.

� scsistat:Checks the SCSI bus, connectors, and SCSI ID. Make sure that DASM is powered and being run.

� showdasm:This will query the DASM and provide you with configuration information for it.

� rsp:Once this command is issued, ‘clrsp’, ‘rqs’, and ‘rsp’ programs are executed in this order. You can checkif the DASM is properly connected to the laser camera.


2202125

SYSTEM1–35

REV 29

1-6 GENERATOR TEST

Click on Generator Test, the following message appears. Enter y to enter the Generator test.

Table 1–5 Generator Test

Command Description JEDIsoftwareVersion

Retrieve Board Version Version information of each board is sent to the operatorconsole (OC) and displayed.

All

Retrieve Software Version Software version information of the JEDI generator is sentto the OC and displayed.

All

Clear Filament aging, Tube status Clears data of filament aging and statistics of the x–raytube currently installed.

This command should be executed after the x–ray tube isreplaced; do not execute this command for the currentlyused x–ray tube.

All

Clear Error Log Clears the error log data stored in the JEDI generator. All

Clear generator tracking/trendiing da-tabase

Clears the tracking/trending data stored in the JEDI genera-tor.

P5.xx orlater

Error log retrieve (JEDI) Retrieves the error log stored in the JEDI generator, anddisplays it.

The JEDI error log contains up to 60 error records and theyare more detailed than the corresponding error informationprovided by the system. The date and time recorded in thelog are generated in the generator (i.e., JEDI time).

If the error log is not displayed due to some error, see the‘JEDIerror.log’ or ‘JEDIerror.log.detail’ file in the /usr/g/ser-vice/log directory, as follows:

1. Select Unix Shell from the System Tools menu to openthe winterm window.

2. Enter the following (underlined) in the window.

cd /usr/g/service/log <Enter>JEDIerror.log <Enter> orJEDIerror.log.detail <Enter> (detailed log)

All

(continued)


2202125

SYSTEM1–36

REV 29

1-6 GENERATOR TEST (continued)

Table 1–5 Generator Test (continued)


JEDI tracking/trending datum upload The tracking/trending data stored in the generator is sent tothe OC.

P5.xx orlater

Code Download (JEDI) Sends the JEDI firmware data to the generator.

This command is used when the generator firmware need-ed to be updated.

At first, a data checksum is calculated and then the firm-ware data is sent to the generator, which takes approxi-mately 12 hours.

All

Error Definition file update Updates the error code definition information.

This command should be executed after the Code Down-load (JEDI) command is executed, since error code Nos.are changed by the firmware update.

P5.xx orlater

TnT Definition file update Updates the TnT code definition information.

This command should be executed after the Code Down-load (JEDI) command is executed, since TnT code Nos. arechanged by the firmware update.

P5.xx orlater

Saved RAM data Upload The data stored in the generator is sent to the OC. All

Saved RAM data Download Sends the saved generator data to the generator. All

kV Diagnostic (Gates Drive Test) Tests the inverter operation with no main DC power input.

A delay time until the actual execution starts can be speci-fied.

Refer to Section 2–10 or 3–10–1 ‘Inverter Gate CommandDiagnostics’, of X–ray Generator of this manual.

All

kV Diagnostic (Primary power test) Tests the high voltage inverter operation with the inverteroutput shorted.

Refer to Section 2–11 or 3–10–2 ‘Inverter in Short CircuitDiagnostics’, of X–ray Generator of this manual.

All

kV Diagnostic (no load kV) Tests the high voltage operation without making x–ray ex-posures.

Refer to Section 2–12 ‘No Load HV Diagnostics’ or Section3–10–3 ‘No Load HV Diagnostic without Anode Rotation norFilament Heating’, of X–ray Generator of this manual.

All

(continued)


2202125

SYSTEM1–37

REV 29

1-6 GENERATOR TEST (continued)

Table 1–5 Generator Test (continued)


Heater Diagnostic Tests the filament heating operation.

Refer to Section 2–8 ‘Heating Function Diagnostics’ or Sec-tion 3–8 ‘Heating without HV nor Rotation Diagnostic’, ofX–ray Generator of this manual.

All

Rotor Diagnostic Tests the x–ray tube rotor operation.

Refer to Section 2–9 ‘Rotation Function Diagnostics’ orSection 3–9 ‘Rotation without HV nor Filament Diagnostic’,of X–ray Generator of this manual.

All

Set JEDI time Sets the generator date and time equal to the system ones.

To do this, do ‘get system time’, and then, ‘set JEDI time’.

All

Checksum saved RAM Calculates a checksum of RAM.

This command should be executed after a software patch isperformed using the Saved RAM data Download command.

All

� Click [Apply] to send a selected command to the x–ray generator.


2202125

SYSTEM1–38

REV 29

1-7 GENERIC SYSTEM ANALYZER

1-7-1 View Log Files

IMPORTANT NOTE:For the V/R 5.0x System, this function can NOT be used. (This is available for V/R 4.xx orlower or for V/R 5.5x or later.)

IMPORTANT NOTE:For V/R 5.5x or later system , the Tube Usage Log menu is deleted. Use Tube Usage in ErrorLogs to display the tube usage log.

Table 1–6 View Log Files

View Log FilesMenu

Submenu Description

Tube Usage Log Current Tube(Usage Log of the currently

installed tube)

This log includes the following data:

1. Total tube slice counts2. Number of slices of cluster scans for each scan technique

After Installed(Usage Log of tubes pre-

viously used on the system)

2. Number of slices of cluster scans for each scan technique3. Time of each helical/scout scan

Tube Spits Log – This log includes total spit counts along with time and date.

A trend of spit occurrence frequency can be observed.

Bad Raw Log – This file contains total counts of bad raw data files.

Tube Usage Log

� Use [ ↑ ] or [ ↓ ] keys to scroll the log lists.

� [After Installed] → Previous Tube Usage Log files:Up to the following five log files ( for five tubes) can be displayed.

‘Sv Tube Usage.log.old1’‘Sv Tube Usage.log.old2’‘Sv Tube Usage.log.old3’‘Sv Tube Usage.log.old4’‘Sv Tube Usage.log.old5’


2202125

SYSTEM1–39

REV 29

1-7 GENERIC SYSTEM ANALYZER (continued)

1-7-1 View Log Files (continued)

Tube Spits Log

Tube spits log is graphically displayed as below.The data indicates accumulated values.KV values used while spits occurred are indicated on the graph.

No. of Slices 50000

Spits Log Data

2

01

3

6

45

7

98

10

Bad Raw Log

Bad raw data file log is graphically displayed as below.

No. of Slices 50000

Bad Raw Log Data1

0

–1.0


2202125

SYSTEM1–40

REV 29


1-7-2 Format Raw Data

Table 1–7 Format Raw Data

Format RawData Menu

Submenu Description

Fan Data Store to File, NumericalDisplay

Stores or numerically displays raw data or vector data.The original raw data is converted into floating point numberformat with or without data correction or conversion applied.

DAS Data Numerical Display Displays numerically raw data without any data correction orconversion applied; i.e., displays DAS data itself in hexadeci-mal format.

A Side For Twin System ONLY:GSA has a function to manipulate two raw data (A and B). So we can make mean file orraw file from each detector channel independently. It means, in every scan mode, the twoB Side

GSA has a function to manipulate two raw data (A and B). So we can make mean file orraw file from each detector channel independently. It means, in every scan mode, the tworaw data (A and B) are corrected and used for reconstruction.

Raw Data File Selection

1. Select ‘Generic System Analyzer’ from ‘Diagnostics & analysis.’

2. Select a raw data ID from the lists:

a. Select first an Exam #.

b. Select a Series #.

c. Select an Acq #. If the selected series # above is for a helical scan, further select an Acq #.


2202125

SYSTEM1–41

REV 29


1-7-2 Format Raw Data (continued)

Fan Data

� Fan Data Format – Correction & Conversion:Select whether the following corrections or conversion are to be applied or not.

– Offset File Correction: If ‘Yes’, the raw data is corrected by offset views (offset views are thefirst 64 views which are collected prior to x–ray exposure to gather offset data).

– Reference Correction: If ‘Yes’, the raw data is corrected by reference channel data (referencechannels receive direct x–rays, i.e., which have not passed through an object to be scanned).

– Natural Log Conversion: If ‘Yes’, natural log operation is applied to the raw data.

Then, the following data ‘Fan Data Averages’ are displayed:

– Active ViewsMax of Max = x.xxxxxx channel x view xMin of Min = x.xxxxxx channel x view xAvg of Mean = x.xxxxxxAvg of SD = x.xxxxxx

Offset ViewsMax of Max = x.xxxxxx channel x view xMin of Min = x.xxxxxx channel x view xAvg of Mean = x.xxxxxxAvg of SD = x.xxxxxx


2202125

SYSTEM1–42

REV 29


1-7-2 Format Raw Data (continued)

� Fan Data Format – File Data Type:Select either of the following data types (written in bold) to store it to a raw data file or a vector file, or todisplay (numerically) it.‘Original’ is stored to a raw data file, and the others (‘Active Min’, ‘Active Max’, ...) are stored to a vectorfile. ‘Vector file’ means here a one–dimensional type file, on the other hand, a raw data file is a two–dimen-sional file; i.e., each channel has data for each view.

– Original(Specify 1, 2, ... , or 6, as an ID No. A raw data file stored with this ID No. can be graphically viewedin ‘View Raw Data’ (Generic System Analyzer → Analysis → View Raw Data).)

(For all the ones below, specify a number as a vector file No. A vector file stored with this numbercan be graphically viewed in ‘View Vector’ (Generic System Analyzer → Analysis → View Vec-tor).)

– Active Min (This vector consists of minimum values of each channel during active views.)

– Active Max (This vector consists of maximum values of each channel during active views.)

– Active Mean (This vector consists of mean values of each channel during active views.)

– Active SD (This vector consists of standard deviation values of each channel during activeviews.)

– Offset Min (This vector consists of minimum values of each channel during offset views.)

– Offset Max (This vector consists of maximum values of each channel during offset views.)

– Offset Mean (This vector consists of mean values of each channel during offset views.)

– Offset SD (This vector consists of standard deviation values of each channel during offsetviews.)

DAS Data

� Select ‘Channel’ or ‘View.’

– ‘Channel’ is selected: Specify a channel No. Data for every view, of the specified channel, isnumerically displayed in hexadecimal format.

– ‘View’ is selected: Specify a view No. Data for every channel, of the specified view, is numerical-ly displayed in hexadecimal format.


2202125

SYSTEM1–43

REV 29


1-7-3 Analysis

Table 1–8 Analysis

Analysis Menu Provided Functions Description

View Raw Data Magnify, Minify, GrayScale, Cursor, Numerical,Plot, Erase, ROI Graphics

Displays data of a raw data file as shades.

View Vector Magnify, Numerical, Plot,Erase

Displays data of vector files as graphs.

Calculations Vect/Vect. Op A+B, A–B, AXB, A/B, ln(A), HPF(A), LPF(A), Diff. Filter(A)

Raw/Vect. Op A+B, A–B, AXB, A/B

Raw/Raw Op A+B, A–B, AXB, A/B, ln(A), HPF(A), LPF(A), Diff. Filter(A)

View Raw Data

Before you use this menu, you have to store a raw data file in the ‘Fan Data’ menu (Diagnostics & analysis → GenericSystem Analyzer → Format Raw Data → Fan Data).

1. Select a raw data file from SvSupRaw1, SvSupRaw2, ... , SvSupRaw6.

A raw data file is a two–dimensional type: each channel has data for each view. In this menu, data is shown as shades, i.e., gray scaling.Since the length of the vertical axis (view) is not enough for showing all the views, use the scroll bar to displaythe not–displayed upper or lower part of views.

Channel

View

Scroll Bar

576

10001

By scrolling, up to the 1037th viewcan be displayed.

The actual number of channels orviews varies according to a productmodel.

1


2202125

SYSTEM1–44

REV 29


1-7-3 Analysis(continued)

2. You can use the following functions for the displayed raw data (shades).

� [Magnify]:Scales up both horizontal (channel) and vertical (view) axes by a factor of any of 1, 2, ... , 9.

� [Minify]:Select ‘Remove Odd View’ or ‘Remove Even View.’

� [Gray Scale]:Select ‘Auto range’ or ‘Manual range.’

� [Cursor]:Shows and sets a (+) cursor to the designated location (channel, view). The cursor can be dragged andset (by a second click).

� [Numerical]:Use this after setting a cursor position. Displays values on the positions surrounding the cursor (eightpositions).

Cursor

� [Plot]:Before selecting this function, show and set a cursor to a location of interest (channel, view) by [Cursor].

– Horizontal Profile: Data for each channel is graphically displayed for the specified view; i.e.,shades on a horizontal line (on the specified view) are displayed by a graph.

– Vertical Profile: Data of each view is graphically displayed for the specified channel; i.e., shadeson a vertical line (on the specified channel) are displayed by a graph.

‘Auto Scale’ or ‘Manual Scale’ can be selected for the graph plotting. (For ‘Manual Scale’, enter ‘Minimum’and ‘Maximum’ values.)

� [Erase]:Erases graphs and/or the cursor.


2202125

SYSTEM1–45

REV 29



� [ROI Graphics]:ROI Graphics Menu: ‘Distance’, ‘Erase’, ‘Ellipse’, ‘Erase All’, ‘Rectangle’

The graphics Distance, Ellipse, and Rectangle can be dragged, sized, and numbered.

Distance Ellipse Rectangle

– Distance: Shows a length (distance) by a number of channels and a number of views.

Number ofChannels

Numberof Views

– Ellipse or Rectangle: Shows the following values of the region inside the graphic.

Mean, Standard Deviation (S. D.),


2202125

SYSTEM1–46

REV 29



View Vector

Before you use this menu, you have to store a vector file in the ‘Fan Data’ menu (Diagnostics & analysis → GenericSystem Analyzer → Format Raw Data → Fan Data).

1. Select a vector file.

2. Click on [Plot] and select ‘Auto Scale’ or ‘Manual Scale’ to display a graph.

Data of channels are displayed as a graph.‘Vector File’ means a one–dimensional type file; a typical example is a mean file.

Channel

Data

3. You can use the following functions for the displayed graph.

� [�], [�]:When the ‘Magnify’ function (refer to below) is used, the length of the horizontal axis is not enough forshowing all the channels.Shift the graph in the right or left direction with these buttons to display the not–displayed right or left partof the graph.

� [Magnify]:Scales up both horizontal (channel) and vertical (data) axes.

� [Numerical]:Data for each channel is numerically displayed in the right bottom corner area of the monitor screen.

� [Plot]:Select ‘Auto Scale’ or ‘Manual Scale.’

� [Erase]:Erases the graph currently displayed.


2202125

SYSTEM1–47

REV 29



Calculations

1. Select any of the following as a combination of data types which arithmetic operations are to be applied to.‘Vect/Vect. Op’‘Raw/Vect. Op’‘Raw/Raw Op’ (Vect: Vector file, Raw: Raw data file)

2. Select a kind of operation (addition, subtraction, division, ...).

3. ‘Enter Output Vector (or Raw File) Number’(Enter a number; a file with this identification No. will contain the calculation result.)


2202125

SYSTEM1–48

REV 29

1-8 GETSTATS

1-8-1 General

Click on getStats. The following screen appears to know the Gantry revolution and tube spits.

Show Tube Spits Count

Shows total spits count and last updated date.

Show Tube Spits Log File

Shows total spits count, slice count, and spits count.

Show Gantry Revolution Count

Shows total Gantry revolution count, last updated date, and Gantry revolution count within a specific period.

Reset Total Gantry Revolution Count

Using this function, you can set the total Gantry revolution count to the number you desire. A comment can alsobe entered.

Reset Gantry Revolution Count

Using this function, you can set the Gantry revolution count to 0 (Zero).

Show Total Gantry Revolution Count Log File

Shows the number of Total Gantry revolution per day. (The data of 50 days are displayed.)

Show Total Gantry Revolution Counter Reset History

Shows the reset history of the total Gantry revolution count.


2202125

SYSTEM1–49

REV 29

1-8 getStats (Continued)

1-8-2 Command

You can execute the same getStats function using command line. First run a shell, then enter:

No. Item Command

– getStats main menu getStats

2 Show Tube Spits Count getStats TUBE_SPITS

tubeSpits

tubeSpits –s

3 Show Tube Spits Log file getStats TUBE_SPITS_LOG

tubeSpits –l

4 Show Gantry Revolution Count getStats GANTRY_REV

revCounter –s

5 Reset Total Gantry Revolution Count revCounter TOTALRESET

6 Reset Gantry Revolution Count revCounter RESET

7 Show Total Gantry Revolution Count Log file(for 50 days)

getStats GANTRY_REV 50

revCounter –l 50

– Show any Gantry Revolution Count Log file getStats GANTRY_REV [any number]

revCounter –l [any number]

– Show all Gantry Revolution Count Log file getStats GANTRY_REV_ALL

revCounter –a

8 Show Total Gantry Revolution Counter Reset History getStats GANTRY_REV_HISTORY

revCounter –h


2202125

SYSTEM1–50

REV 29

1-9 HEAT SOAK

Prior to starting Heat Soak

� The x–ray tube should be sufficiently cool.

� If the ‘Cooling time too long’ error message is displayed, you will have to wait at least for 31 minutes tobe able to start Heat Soak.

Table 1–9 Heat Soak

Scan Protocol #Scans

(V4 Cooling) (V5 Cooling)

Scan Group# 1 10 10

Scan Group# 2 10 20

Scan Group# 3 30 10

Scan Group# 4 30 20

Scan Group# 5 20 3

Scan Group# 6 15 –

Scan Group# 7 5 –

� Click [Report] to check the results, after performing heat soak scans.


2202125

SYSTEM1–51

REV 29

1-10 H/W DIAGNOSTICS

CAUTIONUnexpected x–ray exposure! After finishing tests in Diagnostics of H/W Diagnostics, powerOff the system before rebooting the system. This is to avoid unexpected accidental x–rayexposure, because not all the hardware devices are initialized only by rebooting the system.

Click on H/W Diagnostics, the following message appears. Click on YES to enter the H/W Diagnostics.


2202125

SYSTEM1–52

REV 29

1-10 H/W DIAGNOSTICS (continued)

Table 1–10 H/W Diagnostics

H/W DiagnosticsMenu

Submenu Description

Diagnostics

(Refer to below forhow to reach this

menu.)

Interactive Test Provided Tests:

Monitor Test, Keyboard Test, Audio Test,Misc Test (Hardware Inventory, SCSI Test, View SYSLOG,NPR LED, Safety Loop, Shutdown Test),Work Station Default Test (For O2 system only)

(Refer to ‘Interactive Test – XXXXXX’ in Section 1-10-1 (Diag-nostics) in this section.)

Offline Test Provided Tests:

NPR PCI TEST, DBPCI#0 PCI TEST, NPR INTERNAL TEST

(Refer to ‘Offline Test’ in Section 1-10-1 (Diagnostics) in thissection.)

Function Test N/A currently.

View Log* View Diag Log Displays the log of diagnostics results.

View SYSLOG Displays the system log (from the latest system start–up to thepresent).

View P–ON Test Log Displays P–ON Test results.

H/W inventory** Displays a list of main operator console hardware devices.

Open File –

*: Many of the ‘View Log’ submenus are included in ‘Diagnostics’; however, this ‘View Log’ can be used withoutterminating the application unlike ‘Diagnostics.’

**: For the system with V6.05 (NP) or lower / V7.00 (NP–Twin) or lower, when H/W inventory is performed andthe following error might occur, ignore it. “Error: Some of Bit3 PCI Exp cards aren’t found. 2 Bit3 PCI Expcard(s) found.”


2202125

SYSTEM1–53

REV 29


1-10-1 Diagnostics

1. Click [Diagnostics] in the H/W Diagnostics menu, and then the following message is displayed:

******************************* Displayed *******************************

Attention

This requires the application to be shutdown.

Continue ?

************************************************************************

2. Click [YES], and then some messages and windows are shown, and then the following message is displayed:

******************************* Displayed *******************************

Okay to power off the system now.

Press any key to restart.

************************************************************************

3. Switch OFF the power switch on the operator console (OC).

4. Wait for several minutes, and then, switch ON the power switch on the OC.

5. During the power–up sequence, the following screen will appear:

Power on test

DBPCI test

H/W diag

Startup

Shutdown

DBPCI test : OK

Errors :

6. Promptly click [H/W diag].


2202125

SYSTEM1–54

REV 29


1-10-1 Diagnostics (continued)

1-10-1-1 Interactive Test

Misc Test – Hardware Inventory (hinv)

Displays a list of operator console hardware devices which are identified by the operating system software.

Refer to Table 1–11 which lists some of the displayed devices and their names.

Table 1–11 Hardware Inventory (for System Software versions earlier than V4.00)

Displayed Device Device Name

Disk drive: unit 1** on SCSI controller 3 Raw data disk

Disk drive: unit 2 on SCSI controller 3 Raw data disk*

Optical disk: unit 6 on SCSI controller 1 MOD drive)

Optical disk: unit 5 on SCSI controller 1 MOD drive*

Common device: unit 4 on SCSI controller 1 Serial port expander (ST1800)

Disk drive: unit 3 on SCSI controller 1 DASM*

CDROM: unit 1 on SCSI controller 1 CD–ROM drive

Disk drive: unit 2 on SCSI controller 0 System disk*

Disk drive: unit 1 on SCSI controller 0 System disk

PCI SCSI controller 3: Version ADAPTEC 7880 UW SCSI card (AHA–2940UW)

Unknown Type PCI: Bus 2, Slot 6, Function 0, VendorID 0x10b5, Device ID 0x9060

DBPCI board

Unknown Type PCI: Bus 2, Slot 5, Function 0, VendorID 0x10b5, Device ID 0x9061

NPR (NP Recon Engine) Assy

Bit3 PCI Bridge Card: Bus 2, Slot 4 PCI extender card (on the backplane board)

Bit3 PCI Bridge Card: Bus 1, Slot 4 PCI backplane controller card

Bit3 PCI Bridge Card: Bus 0, Slot 4 PCI host card (within the host processor (O2))

Integral SCSI controller 1: Version ADAPTEC 7880 SCSI controller 1 included in the host processor (O2)


*: Indicates that this is an optional device; otherwise (without *), this is a standard device.

**: The number ‘unit 1’ indicates a SCSI device ID number; the set ID number should equal this unit number.(This description applies to other unit numbers.)


2202125

SYSTEM1–55

REV 29



Table 1–12 Hardware Inventory (for System Software V4.00 or later)


Disk drive: unit 1** on SCSI controller 3 Raw data disk


Optical disk: unit 6 on SCSI controller 1 MOD drive

Optical disk: unit 5 on SCSI controller 1 MOD drive*

Common device: unit 4 on SCSI controller 1 ST1800 (alternative to Serial Exp)

Disk drive: unit 3 on SCSI controller 1 DASM*

CDROM: unit 1 on SCSI controller 1 CD–ROM drive

Disk drive: unit 2 on SCSI controller 0 System disk*

Disk drive: unit 1 on SCSI controller 0 System disk

PCI SCSI controller 3: Version ADAPTEC 7880 UW SCSI card (AHA–2940UW)



Serial Exp: PCI Adapter ID (vendor 4277, device36973) pci slot 5

(alternative to ST1800)


**: The number ‘unit 1’ indicates a SCSI device ID number; the set ID number should equal this unit number.(This description applies to other unit numbers.)


2202125

SYSTEM1–56

REV 29



Table 1–13 Hardware Inventory (for System Software V8.00 or later) (Linux PC)


Disk drive: unit 01 on SCSI controller 1 Raw data disk


Optical disk: unit 06 on SCSI controller 0 MOD drive

CDROM: unit c on IDE controller 1 CD–R/W drive

DISK: unit a on IDE controller 1 System HDD

16550A UART serial port: 3F8 COM1

No parallel port configured VGA Card

PCI device 1065:9061 (PLX Technology. Inc) NPR

Ethernet interface configured: eth0 Ethernet

PLX Technology, Inc. 9060PLX Technology, Inc. 9060 (#2)

DBPCI board

Apaptec AIC–7861 SCSI card (Narrow)

Apaptec AHA–9240U/UW/D xxxxxxxxx SCSI card (U/W)



2202125

SYSTEM1–57

REV 29



Misc Test – SCSI Test

Displays detailed information about the SCSI devices which are identified by the host processor.

Verify that detailed information is displayed for each of the SCSi devices which are identified in the ‘Hardware Invento-ry’ (Diagnostics – Interactive Test – Misc Test – Hardware Inventory).

Misc Test – View SYSLOG

Opens a log viewer and displays SYSLOG. SYSLOG is a log file managed by the OS (operating system) and includesinformation on the host processor (O2) and also a part of status/error messages generated by device drivers (soft-ware) for the NPR (NP Recon Engine) and the DBPCI board.

The SYSLOG only contains logs generated since the last start–up which occurred after the last 12 o’clock midnight.When it passes 12 o’clock midnight, the logs contained up to then are stored and the SYSLOG is initialized.

The following log will be displayed (an example).

******************************* Displayed *******************************Mar 9 15:19:46 6F:aoyagi syslogd: restartMar 9 15:19:46 2A:aoyagi unix: IRIX Release 6.3 IP32 Version 12161207System VMar 9 15:19:46 2A:aoyagi unix: Copyright 1987–1996 Silicon Graphics,Inc.

..................

Mar 9 15:19:46 5A:aoyagi unix: NOTICE: pcinre attach: Config.address is0x80022800Mar 9 15:19:46 5A:aoyagi unix: NOTICE: pcinre_attach: Configurationfields:Mar 9 15:19:46 5A:aoyagi unix: NOTICE: Vendor Id = 0x10b5, Device Id =0x9061, Base_Reg = 0x81000000

..................

Mar 9 15:19:46 5A:aoyagi unix: NOTICE: pcindb attach: Config.address is0x80032000Mar 9 15:19:46 5A:aoyagi unix: NOTICE: pcindb_attach: Configurationfields:Mar 9 15:19:46 5A:aoyagi unix: NOTICE: Vendor Id = 0x10b5, Device Id =0x9060, Base_Reg = 0x81400000

************************************************************************

Verify that the underlined information is displayed; other than underlined may be different.If underlined information is displayed, it indicates that the DBPCI board and the NPR (NP Recon Engine) are initializedby the host processor.


2202125

SYSTEM1–58

REV 29



Misc Test – NPR LED

Turns on LEDs on the NPRM (NP Recon Engine Master) board according to the dip switch (S1) setting on the board.Refer to the illustration below (if switch 2 is set to ON, for example, LED6 should light).

12345678

ON

LED7LED6LED5LED4LED3LED2LED1LED0

S1 is set according to the memory capacity and the number of NPRS (NP Recon Engine Slave) boards installed onthe NPRM board. The LEDs turn On during approximately 30 seconds.

Misc Test – Safety Loop

This test turns On/Off the safety loop relay on the REAR CN1 board.

CAUTIONUnexpected hazards! Take appropriate precautions (steering clear of the gantry, etc.) againstgantry/table movement or x–ray exposure before turning On the safety loop relay. And do notforget to turn Off the relay before exiting the test.

Misc Test – Shutdown Test

Tests the OC power off timer function of the FRONT PNL board.


2202125

SYSTEM1–59

REV 29



1-10-1-2 Offline Test

To select a test, refer to below:

� Click [NPR] and [PCI TEST] to select ‘NPR PCI TEST’.

� Click [DBPCI#0] and [PCI TEST] to select ‘DBPCI#0 PCI TEST’.

� Click [NPR] and [INTERNAL TEST] to select ‘NPR INTERNAL TEST’.In ‘NPR INTERNAL TEST’, ‘Master DSP’ or ‘Slave DSP’ can be selected.

Click [DETAIL] to check/set test parameters.

Other selectable parameters:

Parameter Selection

WHEN ERROR OCCUR STOP, CONTINUE

TEST MODE NORMAL, QUICK, MANUAL

For more detailed information about Offline Test, refer to Off–line Test, of the Operator Console tab.


2202125

SYSTEM1–60

REV 29

1-11 IMAGE PROFILE

The graphical profile data on selected line of the image can be displayed. Horizontal, vertical, and free direction ofa line can be selected.

Selections in Image Profile

1. Click on Browse in Functions selection.Application sort screen appears.

2. Upon application sort window, you can highlight an EXAM –> Exam. No. –> Series No., and click on Accept .The desired image appears in the screen.

3. Select the desired image profile type by pressing any of the following buttons:

� Horizontal:The graphical profile data on the selected horizontal line is displayed.

� Vertical:The graphical profile data on the selected vertical line is displayed.

� Free:By selecting two given points, the graphical profile data is displayed.

� FWHM:Full Width Half Maximum

� Auto:sets area automatically for profile graphic representation.

� Use FOV:

� Smooth:Not available yet.

4. Drag a cursor on the displayed image.The graphical profile data is displayed.

5. To delete the lines, click on Erase. To exit from this program, click on Quit.


2202125

SYSTEM1–61

REV 29

1-12 MTF SURVEY

��

�� !��"!#�� $��

# ��!�� "!#��

��

Special Tool

� GE Performance Phantom (2102580) or equivalent

Scanning the GE Performance Phantom

1. %��


2202125

SYSTEM1–62

REV 29

1-12 MTF SURVEY (continued)

2. &�'�� (

a. �� ) ��(��*(

Recon FOV Scan Time (Sec) kV mA Thickness Focal Size

10 (Head) 2.0 120 150 10 L

10 (Body) 1.5 120 130 10 L

b. "��

c. %��

��

+��$� ��'��$��'�� ) ��(�,�� *

Wire Point

X

Y

Scan Center

d. -��

��

��

White band

3. Record the image No.


2202125

SYSTEM1–63

REV 29


Mode – ‘Automatic’, ‘Manual’

4. ‘Manual’:If you select ‘Manual’, proceed to step 5.

‘Automatic’:If you select ‘Automatic’, perform the following:

a. Perform step 5.

b. Proceed to step 9.

If it does not seem to work well, try the ‘Manual’ mode.

Image ID

5. Enter the image No. (Patient ID#.Exam#.Series#.Image#); or, select the image, using the [Browse] function.

‘Pin Center X’, ‘Pin Center Y’

6. Enter X and Y values as follows. X and Y are the locations of the pin center existing within the phantom.

a. Click [Locate]. The pencil cursor appears on the image field.

b. Use the mouse to position the tip of the cursor on the center of the pin. See below:

Pin

c. Click the right button, and then, the location values are entered into the boxes.


2202125

SYSTEM1–64

REV 29


‘Inner ROI’, ‘Outer ROI’

7. Measure the ROI values, of an area within the pin and of an area encompassing the pin:

a. Click [Measure] for ‘Inner ROI’. A circle cursor appears on the image field.

b. Use the mouse to position the cursor within the pin and enter the value, as follows:

i. Position the cursor, by moving the mouse while pressing the center button.

ii. Adjust the cursor size, by moving the mouse while pressing the left button.

iii. Enter the value into the box, by clicking the right button.

c. Click [Measure] for ‘Outer ROI’.

d. Perform step b. In this step, encompass the pin with the cursor.

Advanced Settings – ‘Adjust’, ‘Use Default’

8. Usually select ‘Use Default’.


2202125

SYSTEM1–65

REV 29


[Compute], [View Plot]

9. Click [Compute]. The MTF values are calculated.

10. Click [View Plot].

11. Read the lp/cm values (on the horizontal axis) of the curve at 0.5, 0.1, and 0.05 (on the vertical axis), using themouse. And enter the values in the ‘MTF lp/cm@50%’, ‘MTF lp/cm@10%’, ‘MTF lp/cm@5%’ boxes, respective-ly. Refer to below:

1

0.8

0.6

0.4

0.2

2 4 6 8 10

EXAMPLE

0

0

0.5

0.1

0.05

lp/cm@50% lp/cm@5%lp/cm@10%

[Submit]

12. Click [Submit] to record the data. (File name: /usr/g/service/log/mtf.report)


2202125

SYSTEM1–66

REV 29

1-13 OFFLINE SCAN

Table 1–14 Offline Scan

Parameter Group Parameter Selection

Technic Scan Type Axial, Helical, Cine, Scout, Stationary, T/G Control (Referto Section 1-13-1.)

(others) –

Thickness [mm] For the system with Asymmetric Option Installed only, thisparameter is displayed.

“10: 1” provides 10 mm and 1 mm slices.“10: 2” provides 10 mm and 2 mm slices.“6: 1” provides 6 mm and 1 mm slices.

Scan Environment X Ray ON, OFF

Rotor ON, OFF

Data Collection ON, OFF

DAS Mode NORMAL, PATTERN, DAS64L, DAS16L, DAS16M,DAS4M, DAS4H, DAS1H

Gantry Tilt [deg] (arbitrary)

Tech. for Scan Type (other scan parameters) –

1-13-1 T/G Control

T/G Control

The following mechanical controls of the gantry and table can be performed with this menu. After setting these param-eters, click on Back to return to perform the 1st screen of Offline scan.

� Table Pos. [mm]: The cradle is moved (horizontally) to a specified position. The cradle button on thekeyboard lights during cradle movement.

� Gantry Tilt [deg]: The gantry is tilted to a specified position. You have to press the tilt button on the key-board after it lights and continue to press it until the gantry stops tilting.

If a remote tilt option is not installed on the system, you have to press the tilt button on the gantry to executethe operation.

� Azimuth [deg]: The gantry is rotated to a specified position.

Collimator Control (For Twin System ONLY)

After setting these parameters, click on Back to return to perform the 1st screen of Offline scan.

� Auto Collimator: When set to ON, collimator tracking control during offline scan becomes available.

� Position Change: When set to ON, the collimator can be moved to the desired position using the follow-ing parameters (Move mode and Pulse) .


2202125

SYSTEM1–67

REV 29

1-13 Offline Scan (Continued)

� Move mode: When ‘Position Change’ is set to ON, this parameter can be available.

– Abs.: (Absolute position change) moves the collimator from the reference position (zero position)held by the DAS to the desired position specified by ‘Pulse’ parameter.

– Rel.: (Relative position change) moves the collimator from the current position held by the DASto the desired position specified by ‘Pulse’ parameter.

� Pulse: specifies the collimator travel from –8,192 to 8,191 pulses. (1 pulse = 2 micrometers)

� Reset: When set to ON, the collimator position is reset.

� CIF Mode: (For V/R 5.5 or later ONLY)The following operation can be performed according to the Function mode selected. X–ray ON selectionmust be required.

IMPORTANT NOTE:When selecting Zigzag or Vibration mode, do not select Helical or Cine scan as a Scan Type.This is why one data only is acquired.

CIF Mode

Function Value Operation

Normal 00 Normal Operation

ZIGZAG 01 The collimator moves zigzag. This mode can be used in com-bination with a tracking mode.

STEP A 02 The collimator moves in 20 pulse steps.

STEP B 03 The collimator moves in 5 pulse steps.

STEP C 04 The collimator moves + 10 pulse every one scan.

STEP D 05 The collimator moves + 1 pulse every one scan.

VIBRATION 10 The collimator vibrates, using for belt tension adjustment. Af-ter completion of this test, the Gantry must be reset.

TEST A 11 The collimator moves 20 pulses of a reciprocating motion fortest. (for a manufacturing test use) After completion of thistest, the Gantry must be reset.

TEST B 12 The collimator moves 140 pulses of a reciprocating motion fortest. (for a manufacturing test use) After completion of thistest, the Gantry must be reset.

TEST C 13 The collimator moves [Home → 20 pulses] of a reciprocatingmotion for test. (for an endurance test use) After completion ofthis test, the Gantry must be reset.

Value – Selected when selecting Function as a value. For example, if“01” is entered, the ZIGZAG function is selected.

– 06–0F Reserved

– 14–7F Reserved


2202125

SYSTEM1–68

REV 29

1-14 RAW DATA FUNCTIONS

Table 1–15 Raw Data Functions

Bar Menu Pulldown Menu Function

File Exit Exits ‘Raw Data Functions.’

FunctionSelection

Save to MOD (Selected as default when ‘Raw Data Functions’ is selected.)Selection

Restore/Delete from MOD Loads raw data files from the MOD to the system hard disk, or,deletes raw data files on the MOD.

Reserve/Release –

Initialize MOD Initializes an MOD inserted.

Raw dataSelection

Whole Exam, Whole Series,Individual Raw

Selects a raw data file, or, all the raw data files of a specifiedseries No., or, all the raw data files of a specified exam No.

(Note for Twin Systems only)

For Twin systems, do not select ‘Individual Raw’ in the Raw data Selection menu, otherwise, problems may be causedfor retro recon, etc. due to a Twin system algorithm related reason. This means that you should not handle individualraw data file. Instead, select ‘Whole Exam’ or ‘Whole Series’ in the menu.


2202125

SYSTEM1–69

REV 29

1-15 SCAN ANALYSIS

The scan analysis feature allows users to have interactive access to scan files collected on the scanner. Scan datato be viewed can come from either Patient Scanning or from service mode tools such as Diagnostic Data Collectionor Calibration.

Analysis is divided into three major areas of: SCAN ANALYSIS, dd FILE ANALYSIS, CAL FILE ANALYSIS, and Z–tracking (for Twin ONLY). dd FILE ANALYSIS and CAL FILE ANALYSIS is not yet available for this CT System. Eachmajor section provides an File List Select interface similar to the Image Works List Select, Image Browser. AnalysisList Select allows you to select the appropriate file of interest.

Any of the normal scan files may be selected for processing within Scan Analysis including Axial, Helical, and Scoutscans. Once the scan data of interest is selected you can select one of several processing options which include:Update, Scan Header, Cal Vectors, Plot MSD, Plot VVC, and Save Scan.

Definitions within Scan Analysis

� dd File (Diagnostic Data File):dd files are a result file from some type of operation on the scan data file. dd files are typically some formof view summed file that may have had some specific type of processing applied to it. For example, theprocessing applied to the raw data to calculate the position of the pin in ISO alignment results in a tempo-rary file that is a view summed result that could be saved as a dd file. As long as two dd files have the samenumber of data elements in them the two files may be added, subtracted, multiplied, or divided with eachother.

� Means and Standard Deviation File (MSD): This is usually the result of combining two or more views mathematically which results in Mean Valuesfor each channel in the views and an associated Standard Deviation for each channel in the views. In es-sence all of the user selected views in a scan file are summed together resulting in a single “master view”that contains the averaged data from all of the views. The mean values represent the average data valuefrom the channels and the standard deviation values represent the amount of variability for that channelsdata values across all of the views. The higher the standard deviation the more the channel output variedfrom view to view.

� Scan Header: This is the information contained within the Scan File that identifies the specific settings in affect whenthat scan file was created. The Scan Header includes information at several levels including: Exam, Se-ries, and Scan. Information identifying the technique selections, scan time, acquisition mode, and manyothers may be found in the scan header.

� Cal Vectors: Within Scan Analysis the Cal Vectors are only those vectors contained within the Scan Data File at thetime that the scan was taken.

� VVC (Views vs Channels): This is a way to graphically represent the data values from each channel for each view of data from theS–DAS as a shade of grey. The display will have the views stacked vertically and the channels arrangedacross the display horizontally.


2202125

SYSTEM1–70

REV 29

1-15 SCAN ANALYSIS (continued)

Starting the Scan Analysis

Click on Scan Analysis. The following window appears.

Selections in Scan Analysis

Upon starting the Scan List Select window, you can highlight an EXAM –> SERIES –> SCAN, and perform the desiredanalysis feature by pressing any of the following buttons:

� Update:The UPDATE selection will refresh the List Select Display if new scan files have been created since theScan Analysis Tool was started.

� Scan Header:The SCAN HEADER selection will open a scrolling text window that contains the header text informationcontained in select scan file.

� Cal Vectors:The CAL VECTOR selection will open a window that allows you to select which of the calibration vectorsin the selected scan file that you wish to look at. After the selections are made, OK will process the datarequests and display the results.The resultant plots will be auto–scaled and in some cases the range of data displayed will be set automati-cally. This is to provide a reasonable initial view of the data. Always check the scale on the left hand sideof the plot displays. Cursor reporting of data value and channel numbers is provided.


2202125

SYSTEM1–71

REV 29


� Create MDS DD File: (For V/R 5.5x or later)This will calculate a view averaged “super view” for the selected views and store the results in a separatefile on the systems disk. The display will report the path and filename of the file just created. Once created,dd File can be viewed or compared with other files to check for specific operating characteristics.

� Plot MSD:Provides a set of view summed Means and Standard Deviation Plots of a scan file. The plotter is startedto display the means vectors and the standard deviation vectors, computed across the entire scan for eachdetector macro row. There will be (4) mean and standard deviation plot sets in the display window. After Plot MSD is started, a preprocessing option selection window appears:

– Offset Correction:This processing step removes from the scan data, the signal bias introduced by the acquisitionelectronics. This operation is performed on a channel by channel basis for each view.

– Reference Normalization: Makes use of unobstructed (not blocked by the patient) detector cells at the end of the detectorto adjust for fluctuations in the x–ray beam and effects of aperture size and mA. In the case wherethe reference channels are blocked, the system uses an estimated value for the processing. Thesteps for Reference Normalizing the scan data involves: Offset Correction for the ReferenceChannels, Dividing the Offset Corrected Scan Data by the Averaged Reference Channels foreach view.

– Log Conversion:The log operation is applied.

– Convolved Data: N/A (Do not use this function because a proper calculation can not so far be obtained.)

Cursor reporting of data value and channel numbers is provided.For terminology and usage, refer to Generic System Analyzer.


2202125

SYSTEM1–72

REV 29


� PLOT VVC:The PLOT VVC selection provides Views–vs–Channels display of a grey scale representation for the se-lected scan file. Each view of data (or summed, compressed view) is represented on the display as a hori-zontal line. Each pixel in the line represents the data value for a particular channel from the DAS.After VVC is activated,a preprocessing option selection window appears:

– Offset Correction: This processing step removes from the scan data, the signal bias introduced by the acquisitionelectronics. This operation is performed on a channel by channel basis for each view.

– Reference Normalization: Makes use of unobstructed (not blocked by the patient) detector cells at the end of the detectorto adjust for fluctuations in the x–ray beam and effects of aperture size and mA. In the case wherethe reference channels are blocked, the system uses an estimated value for the processing. Thesteps for Reference Normalizing the scan data involves: Offset Correction for the ReferenceChannels, Dividing the Offset Corrected Scan Data by the Averaged Reference Channels foreach view.

– Log Conversion:The log operation is applied.

– FFT channel Data:N/A (Do not use this function because a proper calculation can not so far be obtained.)

– Convolved Data: N/A (Do not use this function because a proper calculation can not so far be obtained.)

(PLOT VVC, Continued)


2202125

SYSTEM1–73

REV 29


After selecting the box or line cursor using ‘region of Interest’ selection box, click [Plot now]. Once dis-played, the window and level for the displayed data can be changed to better see variations in the data.

CURSOR BEHAVIOR IN VVC:Cross hair Cursor reporting is provided for: Data Value, DAS Channel, Detector Channel, and Viewnumber. The cursor is moved across the display using the mouse.A selection box on the display allows selection of Line Cursors (Channel and View) and Box Cursors (Rec-tangle) which allow the selection of a Channel, View, or Group of channels and views for plotting. The lineand box cursors can be moved around the screen to view specific areas of interest. When the mouse point-er cursor is moved over a line cursor the mouse cursor will change to a four pointer arrow. Pressing theleft mouse button allows you to ‘drag’ the cursor across the display.For the box cursors, the box may be dragged using the left mouse button with the mouse cursor positionedover the box. The size and shape of the box can be changed by moving the mouse cursor over the Bottomor Right edges of the box. When over the Bottom or Right edges of the box you can press the left mousebutton to drag the box edge up and down or left and right.With the Line (Channel and View) cursors the plotted data will represent all Channels for a selected Viewor all Views for a selected Channel.With the Box Cursors the resulting plot will be a view summed Means and Standard Deviation plot for theselected views and channels.

� Save ScanThis will save the selected scan file to a temporary disk location so that it can moved to MOD or transferredvia FTP to another location.


2202125

SYSTEM1–74

REV 29


1-15-1 Z–Axis Tracking

The Z–AXIS TRACKING tool is a new TAB for the twin system ONLY, located within the Analysis Tool. The tool canbe used to plot various tracking functions, using a Scan Data Set. For a scan data set, the analysis package can plotdifferent data versus views in UN–FILTERED (the default) or FILTERED (20 pt. Boxcar) formats.


2202125

SYSTEM1–75

REV 29


1-15-1 Z–Axis Tracking (continued)

In the figures that follow, examples of “known” Tracking plots are shown. Since plots vary from system to system, theexamples shown should be used only as guides. Compare your System’s plots and analyze them relative to the speci-fication shown in each figure. The plots shown are UN–FILTERED views, which is the default option when they areplotted. A 20 point boxcar filter takes the 20 view average and then plots the data.

A value is not considered to be out of specification, unless the limit is exceeded for a sustained interval of 100 viewsor more. In the cases where specifications are not given, consider plots informational only.

To use the function “Save to File” , need to make a directory named “data” under root. Then after performing Saveto File, plot data is displayed and text file will be stored into data directory as named “TrackingVsScan.txt” (about 15KBsize). But it is not so useful because of text file.

It is recommended to remove the directory “data” after checking the TrackingVsScan.txt file for system stability.

� Collimator Position:The plot shows the Collimator Position during a scan. Collimator positions are stored in the Scan file (RawData).The vertical axis shows the pulse count of Z–Axis pulse motor (20�m/pulse).


2202125

SYSTEM1–76

REV 29



� Z–Ratio:Z–RATIO Plot computes the Ratio of Q–Cal Channels A and B. The value is given by the following equa-tion.

Z_Ratio � K * A � BK * A B

A and B means Q–Cal channel average data of each detector plane.(K=Qcal channel ratio)

NoteWhen you make a plot, you may be asked to enter the channel number. This has no meaning, anyinput generates same plot.


2202125

SYSTEM1–77

REV 29



� Center Ratio:CENTER RATIO plot indicates the calculated Focal Spot position relative to the centerline,with the center position being 0. The focal spot moves during a scan due to mA, rotor wobble,gantry rotation wobble, and because of tube (target) heat.

Center_Ch_Ratio � K * A � BK * A B

A and B means active channel data of each detectorplane.(K=Q cal channel ratio)

NoteThe Ref. channel Ratio can not be seen by this tool.


2202125

SYSTEM1–78

REV 29


1-15-2 DD

dd File List Select Overview

dd math is a means for the user to apply mathematical operations: add, subtract, multiply, and divide to dd files, andcalculate the channel to channel difference or ratio of means vs. standard deviation vectors of a dd file. It allows theuser to specify the scaling factor for the output vector, and provides three output modes: plot, dd file, and view num-bers.

dd math is part of the dd analysis user interface. Scan Analysis is used to generate dd files that may then be manipu-lated and or examined using dd File Analysis.


2202125

SYSTEM1–79

REV 29


1-15-2 DD (Continued)

Operating dd Math Function

The dd math operation buttons will be insensitive if no files are selected into the dd math operation panel.

1. The user may start dd math operation(s) by selecting the file(s) and putting them into the selection field by clickingthe button FILE #1 or FILE #2.

If the selected file is not a dd file, the application will not put it into the dd math operation field. A message windowwill pop up and ask user to select a dd file.

If only one file is selected and it is of the file type RTS dd file or MSD dd file, both Ch2Ch (Channel to Channel)and Ratio (RATIO OF MEANS VS. STDV) will become sensitive.

If the selected file is not of the type MSD or RTS, only Ch2Ch will become sensitive.

When two dd files are selected, + (ADD), – (SUBTRACT), x (MULTIPLY), and / (DIVIDE) become sensitive andCh2Ch and Ratio will be insensitive.

2. The user can specify the output file name when the dd file output mode is set. Otherwise a default dd file namewill be provided.

3. The default output scaling factor is 1.0. The user can set the scaling factor to any real number.

4. When the dd math operation buttons are sensitive, the user can select the desired button to start the dd mathoperation.

dd Files Generation

There are 18 different dd file types of six orientations. The orientations are View, Channel, RTS, CAL, Elements, andHeader.

Channel oriented means and standard deviation type dd files are the only type that can be created from scan datafiles in the Scan Analysis application.


2202125

SYSTEM1–80

REV 29



dd Math Functions

dd math consists of the following functions:

� Add

� Subtract

� Multiply

� Divide

� Channel to Channel (Ch2Ch) difference

� Ratio of means vs. standard deviation

Perform: add, subtract, multiply, divide, and channel to channel difference operations on dd files. These operationsare only available for dd file types.

Add, Subtract, Multiply, Divide

Applies add, subtract, multiply, and divide between vectors in two dd files. The output file is a dd file with one of thefollowing suffixes:

� .add

� .dif

� .mul

� .rat

Operations can be performed on dd files in View orientation, Channel orientation, RTS orientation, and Cal orientation.

Currently, no dd type restrictions are applied to operations between dd files, as long as the dd vectors have the samenumber of elements. If one file has a single vector and the other file has multiple vectors the mathematical operationwill be applied multiple times using the single vector.Otherwise the mathematical operation will be applied component wise for the number of vectors in each file.

Channel to Channel Difference

Applies the following calculation to the data from the data set(s) in the dd files for View, RTS or Cal orientation.(X2–X1), (X3–X2), (X4–X3),...,(Xn–Xn–1)Where X is the data value for each channel.The output is channel to channel dd file with extension: .c2c


2202125

SYSTEM1–81

REV 29



Ratio of Means vs. Standard Deviation

Takes a MSD (means and standard deviation) or RTS (real time statistics) type of dd file, calculates the ratio of datain the means vector (1st set) to data in standard deviation vector (2nd set). The output file is a ratio type of dd file with the extension: .rat

dd Math Output Mode

Three output modes are supported in dd math:

� Plot:Will plot the output dd vector using an on screen vector display.

� DD File:Allows the user to specify the output dd file name with a full path or the file basename.If only base name is provided the program will use the default prefix and suffix for the output file. Thecreated dd file will be shown in the dd file list.

� View #’s (Numbers):Prints the numerical data of the dd vector(s) to the display window(s). For image file types and scan filetypes, it will display the VVC plots of the selected files.

Other Functions in dd Analysis User Interface

The dd math operation panel supports the following functions for various file types.

� UpdateRefreshes the display in the dd panel.

� PlotPlots the vector(s) of the selected files in the display window for the following file types:dd Files and Cal Files

� Save (to) MOD / Restore (From) MODSaves the selected files to the MOD and restores all the dd files from /MOD/ddfiles to /data directory.

� Sort By Date or Sort by Type

The user can perform these functions, except dd math operations, by simply selecting one or more files in the list selectwindow, and clicking the function button. The following file types are supported in this panel.

� dd File

� Cal File

� Data File


2202125

SYSTEM1–82

REV 29

1-16 SERVICE CALIBRATION

Table 1–16 Service Calibration

Service Calibration Menu(Sequence)

Displayed Instruction

Auto Sequence 1 Air Cal → Phantom Cal

[for CAM Change & Routine Maintenance]

Auto Sequence 2 Q Cal → Air Cal → Phantom Cal

[for Tube/Collimator/Filter/Slice Thickness Change]

Auto Sequence 3 Q Cal → XT Cal → AV Cal → Air Cal → Phantom Cal

[for Detector Change]

Auto Sequence 4 DG Cal → Air Cal → Phantom Cal

[for DAS Change]

Auto Sequence 5 Q Cal → XT Cal → AV Cal → DG Cal → Air Cal → Phantom Cal

[for 1st Installation]

Q Cal –

XT Cal –

AV Cal –

DG Cal –

Asymmetric Seq Q Cal → Air Cal → Phantom Cal [for Asymmetric Option installa-tion]

� For ‘Auto Sequence 1’ only, 80 kV, 120 kV, or 140 kV can be selected.

Phantom Calibration for Twin System

Because of the X–ray geometry, 10mm Calibration file will be unique vector, and system requires two thickness Cal.data for Phantom Calibration. 10mm Cal. data is not linear against other thickness Cal files (7, 5,3, etc.).

10mm Calibration

7mm Calibration

Used for 10mm Cal. File only.

Used for 7, 5,3,2 and 1mm Cal. File.


2202125

SYSTEM1–83

REV 29

1-17 SERVICE MANUAL

The service documentations CD–ROM can be displayed on the CRT of the OC.

1. Insert the Service Documentation CD–ROM into the CD–ROM drive of the OC.

2. Click on Service icon, then select Service Manual.The start screen of the service manual is displayed on the CRT.

NoteIf “Netscape: Not Recommended Browser” window appears, click on Close.

3. Click on Main Page to select the Service manuals to be displayed.

4. To exit from the service manual, click the button located at the left upper of screen, then select Close.The service manual CD–ROM will be ejected automatically from the drive.

NoteFor V/R 5.5x system or later, the CD–ROM can not be automatically ejected. So, open a shell windowand enter eject to eject the CD–ROM. Then enter exit to close the shell window.


2202125

SYSTEM1–84

REV 29

1-18 SHUTDOWN

1-18-1 Application Shutdown

Click on Application Shutdown to terminate the application software and enter the desktop menu. By using thedesktop menu, perform the followings:

Desktop Menu System Software Version Descriptions

2.5 3.x 4.0 4.1 orlater

Startup x x x x Terminates the desktop menu and starts upthe application software.

Date setting x x x x Sets the date and time.

Reconfig x x x x Performs system configurations.

Savestate x x x x Saves the system state data in a MOD.

Restorestate x x x Restores the system state data saved by ‘Sa-vestate’ function.

Install Options x x x x Installs the option key MOD.

List Options x x x x Displays options installed in the system.

Install Software x x Installs revision–up or patch softwares.

Install InSite x x Installs InSite Software.

Install Patch x Installs revision–up or patch softwares.

List S/W Package x Displays versions of Patch and applicationsoftwares.

Shell x x x x Displays the UNIX shell window. You can usethe UNIX commands.

LFW x x x x To perform the LFW procedures.

Logout x x x x Do not click on this button!! If clicked, enter‘ctuser’ as a login ID and ‘suisei.’ as a pass-word to return the desktop menu (or scan pan-el).

Shutdown x x x x Terminates the OS to power OFF the system.


2202125

SYSTEM1–85

REV 29

1-19 SYSTEM BROWSER

The System Browser is intended to provide a single point user interface for the review of important system informationto aid evaluation and troubleshooting.

Viewer Selections

In the Viewer Selection Area, the user may select one of several system information areas to review.This selection is made using the ‘Pull Down’ window labeled ‘View:’

� GE System Loggesyslog

� SYSLOG OCOC computer IRIX Operating System Log

� IOS LOGSApplication software logs for: Image Browser, Image Database Read Server, Image Database Write Serv-er, Image Server, DICOM Server, Image Acquisition Server, Networking Server, Film Composer Log,Printer Server, Archive, Display, Filming.

� Tube UsageTube slice count and use information for the current and previous X–Ray Tubes.

� OC Info.System software version, Disk usage, Network info., Current Process, Hardware Inventory, OC routetable.

� Configuration FilesOC Host Configuration File, OC Scan Hardware Configuration File.

After the Major Area of interest is selected in the ‘View:’ window, you may select one or more of the items displayedin the ‘Option:’ window directly below the ‘View: Pull Down Window’. This allows more than one group of informationto be viewed together.


2202125

SYSTEM1–86

REV 29

1-19 SYSTEM BROWSER (continued)

After the ‘Option:’ window selects have been made, you may get the selected information from the system by selectingthe button directly to the right of the ‘Option:’ window. The Button name will change depending upon the type of infor-mation being selected. In the case of the GE System Log the button is labeled RETRIEVE BUFFER PAGE and if theselection had been Tube Usage the button selections would be SUMMARY, DETAIL, and CUMULATIVE. Each of theselections will be explained later in this description.

In the Viewer Selection Area you may also enter an alpha–numeric text string to Search for in the currently Displayedinformation.

GE System Log

The System Browser provides convenient viewing of the scanner primary message log/usr/g/service/log/gesys_<suite name>_oc.logAfter the user selects the GE System Log the entire log is read and divided into ‘pages’ of 1000 lines of messages.Each ‘page’ of the log is displayed in the ‘Option:’ window with the following format:Pg # :Day of Week mmm dd hh:mm:ss yyyyYou may then select one or more of the ‘pages’ within the option window and then select ‘Retrieve Buffer Page’. Thisallows you to quickly move to a specific Date/Time of interest and avoid having to scroll through parts of the log thatis not of current interest.

Once the Buffer pages have been retrieved, you can search within the currently displayed pages for any alpha–numer-ic string entered in the Search Field and then selecting the Search Button. The search field is case sensitive. Depend-ing upon the selections for: Next, Previous, First, Last the viewer will display the Next, Previous, First, or Last occur-rence of the Search String. Selecting Search Again will take you to the Next or Previous occurrence if those selectionshad been made.

The Search feature will also display how many of occurrences of the Search string where found in that section(s) ofthe log. The information is displayed in the User Message Area at the bottom of the window in the form of:Search Status: Found XX match(s) of <search string>

SYSLOG – OC

When you select either SYSLOG OC, the System Browser will display the IRX SYSLOG Files on the respective com-puter. These are the logs normally found at /var/adm on the OC system.

Once again you may select one or more of the log files to view in the Options: window and then select the View FileButton to retrieve and display the requested information. The Search and Next, Previous, First and Last functionsoperate the same as for the basic gesyslog viewer.

IOS Logs

The IOS log files are created and updated by various scanner application software processes.These processes include: Image Browser, Image Database Read Server, Image Database Write Server, Image Serv-er, DICOM Server, Image Acquisition Server, Networking Server, Film Composer Log, Printer Server, Archive, Dis-play, and Filming.

The System Browser has the same operation and capabilities as those for viewing the IRIX SYSLOG files.


2202125

SYSTEM1–87

REV 29

1-19 SYSTEM BROWSER (continued)

Tube Usage

The System Browser is used to display information about the currently installed tube as well as previously installedtubes. The Tube Usage viewer provides three different levels of information viewing for Tube Usage: Summary, De-tails, and Cumulative.

NoteFor Tube Warranty purposes ‘Warranty Effective Slices’ is the correct number to report upon tubeunit failure.

� Tube Usage Details InformationThe Tube Usage Details information identifies the selected Tube Unit and Site Information plus details onthe types and number of scans taken on that tube unit.

� Tube Usage Cumulative InformationThe Tube Usage Cumulative Information displays the totaled tube usage information for all tubesthat have been installed on the system.

OC Info

The title for this section may be a little misleading so take a look at the capabilities that the System Browser can provideto you in this area.

The System Browser has the capability of running some of the routinely used IRIX commands usedin gathering data about the system operation and configuration as well as reporting some of thespecific scanner configuration files.

Note that multi–select is available in the ‘Option:’ Window. Note also that the Search Function is available.The command results available in this area are:

� System Software Revisions:showprods

� Disk Usage: df

� OC Network Sockets:netstat –ian

� OC Route Table: netstat –r

� OC Network Configuration:ifconfig

� OC Current Processes Running:ps –aef

� OC Hardware Inventory:hinv

Config Files

The System Browser has the capability of viewing some of the routinely referenced scanner configuration files usedin gathering data about the system:Info file, OC host.cfg, OC scanrecon.cfg, OC option.cfg, etc..


2202125

SYSTEM1–88

REV 29

1-20 UPDATE SYSTEM LOG

The following logs can be updated by this menu.

� ‘Tube Usage’, ‘Tube Spits’, ‘Bad Raw’

NOTICEWhen updating system log(s), reboot the system to enable a newly created file.


2202125

SYSTEM1–89

REV 29

1-21 USER PREFERENCE

The following can be set in this menu.


2202125

SYSTEM1–90

REV 29

1-22 VECTOR CONVERT

Table 1–17 Vector Convert

Parameter to be Specified Selectable Parameter

Vector Warmup Whole, Warmup History, Hilight, Air & Ptm

Generation

(When ‘Warmup Whole’ is se-lected for ‘Vector’ only)

Current, Previous, 2Before, 3Before, ... , 9Before

Item

(When ‘Warmup History’ is se-lected for ‘Vector’ only)

Mean, 1/Mean, SD, SD/Mean, Ratio, HPFratio, AP chk0, APchk90, AP chk180, AP chk270, stRatio, filstRatio

kV, Thickness, Cal.FOV, Fo-cus

(When ‘Air & Ptm’ is selectedfor ‘Vector’ only)

(kV), (Thickness), (Cal.FOV), (Focus)

Store from (arbitrary)

How to Use

1. Specify the parameters described in Table 1–17.

2. Click [Convert vector].

3. Click [Show contents].

The following is displayed.

Table 1–18 ‘Show contents’

Vector Displayed Information

Warmup Whole Date & Time

Warmup History Date & Time

Hilight Date & Time, (others)

Air & Ptm Date & Time, beta, gamma, (others)


2202125

SYSTEM2–1

REV 9

SECTION 2 – MESSAGE DISPLAY

2-1 MESSAGE DESKTOP

When an error occurs, the system gives an alert sound, and displays a message on the message bar. See Illustration2–1.Click the message bar to display the message desktop and to see more messages if any. The screen only showsmessages which are current. To see the message log, click [View Log].

Illustration 2–1 Message Desktop

Scan Display ImageWorks

ShutdownService

IdleAttach in progress

Network statusFilming Status

Clear(dimmed)

View Log Close Memo Update(dimmed)

Current Messages

Message Bar

Message Desktop

Monitor Screen


2202125

SYSTEM2–2

REV 9

2-1 MESSAGE DESKTOP (continued)

Viewing Level

Click [Select Viewing Level] to show a pop–up menu for a Viewing Level selection. Refer to Illustration 2–2 and Table2–1.

Illustration 2–2 Message Log Report

SelectViewingLevel

Message Log Report

Message Desktop

Table 2–1 Selection of Viewing Level

Viewing Level(Pop–up Menu)

Description

All All messages are displayed.

Operator Messages for operators are displayed.

Service Messages for service engineers are displayed.

Support Messages for software engineers are displayed.


2202125

SYSTEM2–3

REV 9

2-2 ERROR LOG VIEWER MESSAGE FORMAT

1. Following is the general format of message which you can see on Error Log viewer. Error code is assigned as uniquenumber in one software version but this may be different if software version is different.

Tue Apr 18 13:30:02 2000Host:ctbay01 Proc:scanRx Error:200109155File:UIRx.cxx Line:10653Function : Data Acquisition : OC ProcessingStart : Prospective Exam : 415 : Protocol : 1.

DateHost name of this system

Process name whichoutput this message

Error code which is assignedfor this software

Explanation

2. In case error is from Table/Gantry, including JEDI and DAS, there are 3 types of explanation format:

(1) XG errorOn V/R4.10 or later, JEDI detail error code is on Error Log viewer(gesyslog) in case that error causes scan stop. Itmeans errors higher than Class3 is displayed there. This is common between V/R4.xx software and V/R5.xx soft-ware. See X–ray Generator Section for detail.

Fri Apr 28 18:25:02 2000Host:ctbay10 Proc:tgp_out Error:186218XG Error.Phase is 2 code is 50.Detail error code : 50–0212HHeater Error : MAINS_DROP detected..


2202125

SYSTEM2–4

REV 9

2-2 ERROR LOG VIEWER MESSAGE FORMAT (continued)

(2) Except XG Error on V/R4.13 or beforeYou can find more detail explanation for each errors on Advanced Diagnostics TAB.

Wed Apr 12 13:38:45 2000Host:ctbay07 Proc:tgp_out Error:186403Cradle Error.SW/HW Error: TGP Error Detected.code is 2

Who detects the error.‘TGP Error Detected’ meansTGP detects the error.

Detail error code in Cradle Error.

What kind of errors happened.

(3) Except XG Error on V/R5.00 or laterError Code which is assigned to identify error is unique even if software version is different. All of errors have theinformation who detects error and detail explanation to help you understand the situation.

Fri Apr 28 20:30:07 2000Host:ctbay10 Proc:tgp_out Error:186327Cradle Error.Code:12–1030–02Error detected by : TGP(TP)Cradle unlatch was detected on CRADLE CMD.

What kind of errors happened. Error Code which is assigned to identify errors

Who detects the error Detail explanation of this error.


2202125

SYSTEM2–5

REV 9

2-2 ERROR LOG VIEWER MESSAGE FORMAT (continued)

Error Code format is as below.

Code:12 – 1030 – 02

Who detects the error.

Error or Information, 1 is Error and 0 is Information.

Detail Error Code.

What kind of error happened

List of code who detects the error.

11 TGP(MP)12 TGP(TP)13 TGP(GP)20 OGP30 CIF(DAS)40 kV Control(JEDI)


2202125

SYSTEM2–6

blank


2202125

OPERATOR CONSOLEi

REV 25

OPERATOR CONSOLE

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 – LED DESCRIPTION 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 BOARDS ON NEST 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 BOARDS ON CONNECTOR BOX 1–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 UNITS ON PERIPHERAL BOX 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-1 DASM–VDB (2191523) 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2 DASM–LCAM (2191524) 1–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3 DASM II–VDB (2191523–3) 1–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-4 DASM II–LCAM (2191524–2) 1–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4 OTHER BOARDS 1–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2 – HOST PROCESSOR TROUBLESHOOTING (O2) 2–1. . . . . . . . . . . . . . . . . . . . . . 2-1 PROBLEM DIAGNOSIS 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 DIAGNOSTIC TESTS 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 RECOVERING FROM SYSTEM CRASH 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 DISABLING THE SYSTEM MAINTENANCE PASSWORD 2–7. . . . . . . . . . . . . . . . . . . . . . 2-5 INTEGRATED DIAGNOSTIC ENVIRONMENT (IDE) TESTS ON THE O2 2–9. . . . . . . .

SECTION 3 – HOST PROCESSOR TROUBLESHOOTING (LINUX PC) 3–1. . . . . . . . . . . . . . . 3-1 DIAGNOSTIC TESTS 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1-1 Entering the Diagnostic Tests 3–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-2 Burn–In Test 3–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-3 Exiting from the Diagnostic Tests 3–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

OPERATOR CONSOLEii

blank


2202125

OPERATOR CONSOLE1–1

REV 10

SECTION 1 – LED DESCRIPTION

1-1 BOARDS ON NEST

Table 1–1 NPRIF LED Description

LED Description

DS1 (PCORQ) Lights while the NPRIF board issues a request to the NPRMboard to access the CM (Communication Memory).

DS2 (PCOAK) Lights while NPRM returns Acknowledge of the request (de-scribed above) to NPRIF.(Both DS1 and DS2 LEDs light while NPRIF accesses the CM)

DS3 (PGM0RQ) Lights while NPRIF issues a request to NPRM to access theGM (Global Memory).

DS4 (PGM0AK) Lights while NPRM returns Acknowledge of the request (de-scribed above) to NPRIF.(Both DS3 and DS4 LEDs light while NPRIF accesses the GM)

DS5 (PZ00RQ) Lights while NPRIF issues a request to NPRM to access theIM (DSP Internal Memory).

DS6 (PZ00AK) Lights while NPRM returns Acknowledge of the request (de-scribed above) to NPRIF.(Both DS5 and DS6 LEDs light while NPRIF accesses the IM)

DS7 (IMT2Z) Lights while NPRIF issues an interrupt to NPRM.

DS8 (OINTRQ) Lights while NPRM issues an interrupt to the host processor.

DS9 (BSERR) Lights when non–existent or non–defined addresses are ac-cessed.

DS10 (LSERR) Lights when LSERR# output from the PCI interface chip is ac-tive. At this time, Target Abort or Master Abort is occurring onthe PCI bus.

DS11 (NPRRST) Lights when NPRIF and NPRM/NPRS board(s) which are con-nected to NPRIF are reset.

DS12 (VCC) Lights while DC power is supplied.


2202125


REV 10

1-1 BOARDS ON NEST (continued)

Table 1–2 DBPCI LED Description

LED Description

PCIREQ Lights when the local bus access is requested by Slave orDMA during PCI access.

Slave Lights during PCI Slave access.

DBMEN Lights when the DBM (DAS Buffer Memory) is enabled to takein DAS data.

DSREQ Lights when the DASIFN board requests data transfer.

DSACK Lights when notifying DASIFN that data has been transferredto the DBPCI board.

FIFO Lights when the FIFO stores data whose quantity is half itscapacity.

LINT Lights when an INTA interrupt is issued to the PCI9060.

Reset Lights while DBPCI is reset.

TREQ Lights upon TREQ (Transfer Request).

E_OVR Lights upon DAS Error Overflow. Goes off upon Reset.

PWR Lights while +5 V power is supplied.


2202125


REV 10


Table 1–3 NPRM LED Description

LED Description

LED7–0 See Illustration 1–1.

MS00 Lights when the master DSP is requesting access of GM. (Master DSP MS00 signal)

MS10 Lights when the master DSP is requesting access of PM. (Master DSP MS10 signal)

MS30 Lights when the master DSP is requesting access of i860cont, INTREQ REG, CM, orComm. REG. (Master DSP MS30 signal)

ACK1 Goes off during a wait cycle by the hardware. (Master DSP ACK signal)

POWER Lights while 5 V power is supplied.

PZ0AK Lights when the host processor (PCI) is accessing the master DSP.

PGMAK Lights when the host processor (PCI) is accessing GM.

PCMAK Lights when the host processor (PCI) is accessing CM.

CMR Lights when the master DSP is accessing CM.

ZXLM Lights when the master DSP is requesting access of the slave DSP PM.

ZXIM Lights when the master DSP is requesting access of the slave DSP IM.

Z0LBG Lights when the master DSP is using the GM bus.

Z1LBG Lights when DSP#1 is using the GM bus.

















2202125


REV 10

Illustration 1–1 NPRM LED

Program Running Status ÉÉ

ÉÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉÉ ÉÉ

ÉÉÉÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉÉ ÉÉ

ÉÉÉÉ

ÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉ

Slave DSP’s Interrupt

PCI’s Interrupt

External DMA Running

Link Port DMA Running

LP5LP4

LP2LP0

Idling Status ÉÉÉÉÉÉÉÉÉÉÉ(Blinking)

ÉÉ


1: Complete Boot Up DMA

ÉÉÉÉ

2: Initialize DSP’ Register

3: Initialize Communication Memory

4: Initialize Internal Memory

5: Set Config Status Block

6: Initialize Communication Register

7: Complete Boot Up Slave DSP

8: Initialize Link Port Register

9: Complete Boot Up

DSP Status LED7–0

Boot Up Phase

Program Running / Idle Phase

Bus Error

Abort by PCI

Error

ÉÉÉÉÉÉÉ

ON

OFF

ON or OFF


2202125


REV 10


Table 1–4 NPRS LED Description

LED Description

F3–0 See Illustration 1–2.

MS0 Lights when the slave DSP is requesting access of GM. (Slave DSP MS00 signal)

MS1 Lights when the slave DSP is requesting access of PM. (Slave DSP MS10 signal)

ACK Goes off during a wait cycle by the hardware. (Slave DSP ACK signal)

HBG0 Lights when the slave DSP is not using the bus because the master DSP requestsaccess of the slave DSP.

Illustration 1–2 NPRS LED

Program Running Status ÉÉÉÉÉÉ

ÉÉÉÉ

ÉÉÉÉÉÉ

ÉÉÉÉÉÉ

External DMA Running

Link Port DMA Running

LP2LP0

Idling Status ÉÉÉÉÉÉ

ÉÉÉÉ(Blinking)

1: Complete Boot Up DMA

ÉÉÉÉ

2: Initialize DSP’ Register

3: Initialize Private Memory

4: Initialize Internal Memory

5: Initialize Link Port Register

6: Complete Boot Up

DSP Status LED (F3–0)

Boot Up Phase

Program Running / Idle Phase

Bus ErrorAbort by Master DSP

Error

ON

OFF

ON or OFF


2202125


REV 10


Table 1–5 PCI Backplane LED Description

LED Description

POWER ON Lights while power is supplied.

Illustration 1–3 PCI Backplane

POWER ON LED

PS3

(P11)

(P12)

(P9)

(P8)


2202125


REV 10

1-2 BOARDS ON CONNECTOR BOX

Table 1–6 DASIFN or DASIFN2 LED Description

LED Description

+5V Lights while +5 V Power is supplied.

VLTN Lights while Taxi Violation occurs.

FECERR Lights when a FEC Correction error occurs.

VSIZE Lights when a View Size Correction occurs.

DSRST Lights when _DSRST is active.

DSCLR Lights when _DSCLR is active.

DSREQ Lights when _DSREQ is active.

DSACK Lights when _DSACK is active.

DSERR Lights when _DSERR is active.

VIEW Lights every transfer view.

ENDNG Lights when receiving View END NG CMD.

FIFO1FF Lights when FIFO1 is full.

FIFO2FF Lights when FIFO2 is full.

FPGACONFIG Lights during configurating the FPGA.


2202125


REV 10

1-3 UNITS ON PERIPHERAL BOX

1-3-1 DASM–VDB (2191523)

Table 1–7 DASM–VDB LED Description

LED Description

Image Ready Indicates that an image has been processed, and is stable at the VDB videooutput.

Image Transfer Indicates that an image in the DASM is being processed and transferred to theVDB frame buffer. Note that the video image is not available at the output portduring this internal transfer.

Power This light indicates that the DASM–VDB is powered up. If this light does notilluminate at power–up, you should first check the power cable connections.

CPU This light indicates that the DASM CPU is active and operating properly. Itflashes continuously (blinks on an off) following power–up.

SCSI This light indicates activity on the SCSI bus, such as commands sent or datareceived.

Personality Mod-ule Interface

This light indicates activity in the DASM–VDB personality module, such as datareceived.

Illustration 1–4 DASM–VDB

PIXEL CLOCK

VDBModule

VIDEO CAMERA CONTROL

DASMModule

Power CPU SCSI PersonalityModuleInterface

Image Transfer Image Ready

(2)(1) (4)


2202125


REV 10

1-3 UNITS ON PERIPHERAL BOX (continued)

Powering On

The following sequence occurs in the LED’s when the power switch is turned on:

1. The Power LED comes on.

2. The octal SCSI ID flashes briefly. The Least Significant Bit is next to the Power LED. Note that if the SCSI IDis zero, no LEDs flash.

3. The three LEDs which represent an octal value flash once and go out.

4. Once the power–up sequence completes, the DASM CPU LED (second light from left) blinks regularly, indicatingthat the CPU is active and functioning normally.

Start Up Sequence

When the DASM–VDB interface module is powering up, it performs start–up diagnostics and other related actions.

At power–up, the DASM unit performs the following tests:

� EPROM checksum test

� MFP 68901 access test (the Multi Function Peripheral chip controls the serial port, timing, and I/O)

� SCSI register access test

� Static RAM test

� Dynamic RAM test

� DMA test

When the DASM CPU LED blinks continuously at about two flashes per second, the initialization sequence is com-plete, and the continuous self–test is in progress. The self–test runs until a SCSI command (a write to block 0 on theDASM) is sent by the host. This test signals an error condition by blinking the CPU, SCSI, and Personal Module Inter-face LEDs in tandem, continuously.


2202125


REV 10


Start Up Problems

To report diagnostic conditions, the LEDs on the DASM–VDB front panel have a corresponding binary presentation.The illustration 1–4 shows the value assigned to each LED (CPU, SCSI, Personal Module Interface LEDs).

DASM LED Error CodesUsing LEDs 1, 2, and 4 (CPU, SCSI, Personal Module Interface LEDs), a binary code signals any of the conditionslisted in Table 1–8. The Power LED is not used to report diagnostic conditions.The three LEDs permit a combined total of only seven error codes. To overcome this limitation, the codes are definedas a series of one or more patterns. Each pattern begins with all LEDs flashing briefly, to indicate the start of the num-ber sequence that follows.For example, to display error code 12 (Failed SCSI Interface Test), the CPU LED displays the first digit (1), stoppingbriefly before the SCSI LED displays the second digit (2), as shown in Illustration 1–5.The display of each digit lasts approximately four times the duration of the initial binary “7” (that if, the flash of all LEDs).The patter then repeats. Only the significant digits for each error condition are listed in Table 1–8.

Note:The first error stops the start–up sequence immediately.

Illustration 1–5 LED Error Code Sequence

= 12

All FlashShort

“1”Long

“2”Long

+ +


2202125


REV 10


Table 1–8 DASM Start–up Error Conditions

Value Significance

1 Failed To Set Timer

2 Failed To Set Baud Rate

3 Failed To Access Receiver Status Reg. For Serial I/O

4 Failed To Start Refresh Clock

5 Failed In Set Up Of Serial I/O

6 Checksum Failed

7 Failed Static RAM Test

11 Failed I/O RAM Test

12 Failed SCSI Interface Test

13 Failed To Start VRTX� Operating System

21 Bus Error

22 Address Error

23 Illegal Instruction

24 Undefined MFP (MC68901) Interrupt

25 Zero–divide – Through Trace Trap Level 5

26 Chk, Trapv, Privilege, Or Trace Interrupt

31 Unknown Interrupt


2202125


REV 10


1-3-2 DASM–LCAM (2191524)

Table 1–9 DASM–LCAM LED Description

LED Description

Power This light indicates that the DASM–LCAM is powered up. If this light does notilluminate at power–up, you should first check the power cable connections.

CPU This light indicates that the DASM CPU is active and operating properly. Itflashes continuously (blinks on an off) following power–up.

SCSI This light indicates activity on the SCSI bus, such as commands sent or datareceived.

Personality Mod-ule Interface

This light indicates activity in the DASM–LCAM personality module, such asdata received.

Illustration 1–6 DASM–LCAM

Power CPU SCSI PersonalityModuleInterface

(2)(1) (4)


2202125


REV 10


Powering On

The following sequence occurs in the LED’s when the power switch is turned on:

1. The Power LED comes on.


3. The three LEDs which represent an octal value flash once and go out.

4. Once the power–up sequence completes, the DASM CPU LED (second light from left) blinks regularly, indicatingthat the CPU is active and functioning normally.

Start Up Sequence

Start Up Sequence

When the DASM–LCAM interface module is powering up, it performs start–up diagnostics and other related actions.

At power–up, the DASM unit performs the following tests:




� Static RAM test


� DMA test

When the DASM CPU LED blinks continuously at about two flashes per second, the initialization sequence is com-plete, and the continuous self–test is in progress. The self–test runs until a SCSI command (a write to block 0 on theDASM) is sent by the host. This test signals an error condition by blinking the CPU, SCSI, and Personal Module Inter-face LEDs in tandem, continuously.


2202125


REV 10


Start Up Problems

To report diagnostic conditions, the LEDs on the DASM–LCAM front panel have a corresponding binary presentation.The illustration 1–6 shows the value assigned to each LED (CPU, SCSI, Personal Module Interface LEDs).

DASM LED Error CodesUsing LEDs 1, 2, and 4 (CPU, SCSI, Personal Module Interface LEDs), a binary code signals any of the conditionslisted in Table 1–8. The Power LED is not used to report diagnostic conditions.The three LEDs permit a combined total of only seven error codes. To overcome this limitation, the codes are definedas a series of one or more patterns. Each pattern begins with all LEDs flashing briefly, to indicate the start of the num-ber sequence that follows.For example, to display error code 12 (Failed SCSI Interface Test), the CPU LED displays the first digit (1), stoppingbriefly before the SCSI LED displays the second digit (2), as shown in Illustration 1–5.The display of each digit lasts approximately four times the duration of the initial binary “7” (that if, the flash of all LEDs).The patter then repeats. Only the significant digits for each error condition are listed in Table 1–8.



2202125


REV 10

1-3-3 DASM II–VDB (2191523–3)

1-3-3-1 DASM II–VDB LED Indicators

The DASM II–VDB front panel has six LEDs, which are used for status and error information. These lights are illus-trated below:

PWRCPUSCSIPIF

XMITRDY

124

From left to right, the lights indicate the following:

� RDYImage Ready light indicates that an image has been transferred, and is stable at the VDB video output.

� XMITImage Transmit light indicates that an image is being transferred from the Common Memory to the VDBField Memory. Note that a printable video image is not available during an image transfer.

� PIFPersonality Interface light activity, in the VDB application, coincides with the image transmit function.

� SCSIThis light indicates the host is accessing the DASM via the SCSI bus, such as commands sent or datareceived.

� CPUThis light indicates that the DASM CPU is active and operating properly. It flashes continuously ( “blinks”on and off) following power–up.

� PWRPower Light indicates that the DASM is powered. If this light does not illuminate at power–up, you shouldfirst check the power cord connections.


2202125


REV 10

1-3-3-2 Start–up Sequence

When the DASM II–VDB is powering up, it performs start–up diagnostics and other related actions.

At power–up, the DASM Controller performs the following tests:




� Static RAM test


� DMA test

When the DASM CPU LED blinks continuously at about two flashes per second, the initialization sequence is com-plete.

If an error occurs, the error condition is reported by blinking the CPU, SCSI, and PIF LEDs in tandem followed by anerror code.

Powering On

The following sequence occurs on the front panel’s LEDs when the power switch is turned on:

1. The Power LED lights.


3. The three LEDs flash once and go out.

4. Once the power–up sequence completes, the DASM CPU LED (second light from right) blinks regularly, indicat-ing that the CPU is active and functioning normally.


2202125


REV 10

1-3-3-3 Self–Test Options

Once the start–up sequence is complete, the resident software reads the state of the DIP switch labeled SW1 on theDASM II–VDB board to determine whether further tests are enabled. To access SW1 you must first remove the topcover. Upon locating SW1 you will notice the numbers 0, 1, and 2 silk screened on the printed circuit board. The waySelf–Test executes is determined by the setting shown below:

Switch Position ContinuousMode

Serial Loop–back

Single Pass Single Pass w/Memory

Debug Mode

0 Closed Closed Open Open Open

1 Closed Open Closed Closed Open

2 Closed Closed Closed Open Open

� Continuous Mode:Is the default setting. After executing the start–up diagnostic, the resident software will continuously runthe VDB self–test. Self–test will continue until the first SCSI command is received by the DASM.

� Serial Loop Test:In this mode the VDB tests the RS422 Driver and Receiver. Prior to executing this, a special loop–backconnector on the front panel of the VDB, without the loop–back connector the test will fail.

The loop–back connector is made by simply adding two wires to a 25–pin Male ‘D’ connector: (pin 8 topin 9) and (pin 21 to pin 22).

� Single Pass:The start–up diagnostics execute once, as described in 1-3-3-2 Start–up Sequence. Please be awarethat when position 0 is open error and other messages encountered during start–up diagnostics are di-rected to the serial port. Otherwise the errors are encoded on the LEDs.

� Single Pass w/Memory:Is controlled by Bit 2. When open the DASM exercises the entire DRAM during the start–up diagnostics.The Single Pass w/Memory test can take several minutes to complete, this is why it is normally disabled.

� Debug Mode:When position 1 is open the program jumps to the I/O Monitor when a diagnostic error occurs. The I/OMonitor gives the basic tools to debug the hardware. Opening positions 0 and 2 allows the technicianaccess to the start–up diagnostic suite via the serial port.


2202125


REV 10

1-3-3-4 Start–up Problem

To report diagnostic conditions, the LEDs on the DASM II–VDB front panel have a corresponding binary representa-tion. The illustration 1–7 below shows the value assigned to each LED. The section after the figure explains how theLEDs represent error codes. Note that this sections deals with error codes related to the DASM Controller, whereSection 1-3-3-5, VDB Error Codes, explains the method used to report an error from the VDB diagnostic.

DASM Controller LED Error Codes

Using LEDs 2 and 4, a binary code signals any of the conditions listed in Table 1–10. The Power light and PIF LEDsare not used to report diagnostic conditions.

The three LEDs permit a combined total of only seven error codes. To overcome this limitation, the codes are definedas a series of one or more patterns. Each pattern begins with all LEDs flashing briefly, to indicate the start of the num-ber sequence that follows.

For example, to display error code 12 (Failed SCSI Interface Test), the CPU LED displays the first digit (1), stoppingbriefly before the SCSI LED displays the second digit (2), as shown in Illustration 1–7.


= 12

All FlashShort

“1”Long

“2”Long

+ +

The display of each digit lasts approximately four times the duration of the initial binary “7” (that is, the flash of allLEDs). The pattern then repeats. Only the significant digits for each error condition are listed in Table 1–8.



2202125


REV 10

1-3-3-4 Start–up Problem (Continued)

Table 1–10 DASM Controller Start–up Error Conditions

Value Significance






6 Checksum Failed





21 Bus Error

22 Address Error







2202125


REV 10

1-3-3-5 VDB Error Codes

The following sequence is used to signal an error during the VDB portion of the Self–test.

First, all three LEDs blink together for the duration of a single pass. This requires approximately 10–15 seconds.Then the specific error code blinks twice before the next pass begins, with all three LEDs blinking together as before.

The bit pattern of the error codes appears as a series of LEDs being turned on and off. The low order bit is first.

When two LEDs blink together, the bit value is 1.When only one LED blinks, the bit value is 0.

To see an example of an error code displayed in this way, do the following:

� Remove the loop–back connector from the front panel of the DASM II–VDB.

� SW 1 position 0 is closed.

� SW 1 position 1 is open.

� Now cycle the AC power on the DASM

� When the first pass of the DASM self–test has completed, the LED display begins. The expected erroris 5 (RS–422 port fail), and the LED sequence is:Least significant first:bit 0 = 2 LEDs on = 1 Value 1bit 1 = 1 LED on = 0bit 2 = 2 LEDs on = 1 Value 4bit 3 = 1 LED on =0

Table 1–11 Serial Error Codes in LEDsLED sequence, from left to right

Checksum 1211 checksum of EPROM

Serial 2121 RS422 test–needs loop–backconnector

DMA_setup 1112 Tests DASM Block

Image_verify 2112 tests full image transfer

DASM Block 2222 nonspecific failure. SCSI to hostis needed


2202125


REV 10

1-3-3-6 RUN–TIME Error Codes

These codes may be found in the DASM Response Block byte 128, when the error bit (bit 2, where bit 0 is first) isset in Response Block byte 0. Only the first of multiple errors is stored in Response Block byte 128. Reading theResponse Block clears the error. Note that the status “invalid command” is returned to the user directly in bit 0 ofthe SCSI status byte; it is not logged in the Response Block.

Table 1–12 DASM Run Time Error Codes

Error Hex Meaning

General Error Codes

E_PARAM 81 Bad parameter to valid command

E_NO_FF 82 No 0xFF terminator in command

E_TMO 83 Timeout

E_PIF_SELF 84 Peripheral interface self–test error

E_PIFNOTRDY 85 Peripheral device not ready

E_OVRRUN 86 Data overrun

E_UNDRUN 87 Data under run

E_COM_LINK 88 Communications link error between DASM and PIF

E_DRAM 8A Error in I/O RAM (Note: This is a warning, which is available in the trace buffer in theDASM response block. During a warning, byte 128 is not updated.)

E_EPROM 8B EPROM checksum error

E_MFP 8C Error in the MC68901 I/O and timer chip

E_SBIC 8D Error in access to SCSI bus interface chip

E_NOTIMER 8E No timer available (all in use)

E_INTERN 8F Internal system software error

E_INV_MSG B0 Invalid / unexpected message from device

E_BAD_S B1 Invalid S–record (from load routine)

E_ODD_ADR B2 Odd address passed to function

E_BOUNDS B3 I/O request overlapped buffer boundary

E_DIRECTION B4 I/O request direction is invalid

E_NOT_NXT B5 I/O request for data is out of sequence

E_AVAIL_CT B6 I/O request exceed available data count

E_PARITY B7 Parity error

E_PIF_REV B8 No PIF revision level supplied

E_TIMER_ID B9 Timer id error

(Continued)


2202125


REV 10

1-3-3-6 RUN–TIME Error Codes (Continued)

Table 1–12 DASM Run Time Error Codes (Continued)

Error Hex Meaning

M_REJECTED 95 Message was <REJ>ected by partner

M_BADREPLY 96 Unexpected reply was received

E_NOTREADY 97 Camera is not ready

E_TIMEOUT 98 EXEC Function did not complete in time

E_TOOLONG 99 Received telegram has too many characters

E_UNEXPECTED 9A Laser camera replied with an unexpected telegram

E_BADPARAM 9B Bad parameter from host found in CMDBLK

VRTX Error Codes

E_VRTX C1–F4 VRTX error range

– C1 Task ID invalid

– C2 No task control block available

– C3 No Memory available

– C4 No Memory block

– C5 Mailbox in use

– C6 Message of Zero

– C7 Buffer full

– C8 WAITC is in progress

– C9 Invalid system call

– CA Timeout

– CB No Message present

– CC Queue ID error

– CD Queue Full

– CE Partition ID error

– CF Fatal initialization error

– D0 No character present

– D1 Invalid configuration parameter at Init

– D2 Invalid parameter to PCREATE/PEXTEND

– E0 No component vector table

– E1 Invalid component

(Continued)


2202125


REV 10



Error Hex Meaning

– E2 Invalid opcode for component

– F0 No control block available

– F1 Event flag group or semaphore ID error

– F2 Tasks pending on event flag group or semaphore

– F3 Event flag group or semaphore is deleted

– F4 Event flag group already set or overflow


2202125


REV 10

1-3-4 DASM II–LCAM (2191524–2)

1-3-4-1 DASM II–LCAM LED Indicators

The DASM II–LCAM front panel has four LEDs, which are used for status and error information. These lights areillustrated below:

PWRCPUSCSIPIF

124

From left to right, the lights indicate the following:

� PIFPersonality Interface light indicates a data transfer from the Common Memory to the LCAM circuitry.

� SCSIThis light indicates the host is accessing the DASM via the SCSI bus, such as commands sent or datareceived.

� CPUThis light indicates that the DASM CPU is active and operating properly. It flashes continuously ( “blinks”on and off) following power–up.

� PWRPower Light indicates that the DASM is powered. If this light does not illuminate at power–up, you shouldfirst check the power cord connections.


2202125


REV 10

1-3-4-2 Start–up Sequence

When the DASM II–LCAM is powering up, it performs start–up diagnostics and other related actions.

At power–up, the DASM Controller performs the following tests:




� Static RAM test


� DMA test

When the DASM CPU LED blinks continuously at about two flashes per second, the initialization sequence is com-plete.

If an error occurs, the error condition is reported by blinking the CPU, SCSI, and PIF LEDs in tandem followed by anerror code.

Powering On

The following sequence occurs on the front panel’s LEDs when the power switch is turned on:

1. The Power LED lights.


3. The three LEDs flash once and go out.

4. Once the power–up sequence completes, the DASM CPU LED (second light from right) blinks regularly, indicat-ing that the CPU is active and functioning normally.


2202125


REV 10

1-3-4-3 Self–Test Options

Once the start–up sequence is complete, the resident software reads the state of the DIP switch labeled SW1 on theDASM II–LCAM board to determine whether further tests are enabled. To access SW1 you must first remove thetop cover. Upon locating SW1 you will notice the numbers 0, 1, and 2 silk screened on the printed circuit board.

SW1

–Open–

210

SP

12

34

The way Self–Test executes is determined by the setting shown below:

Switch Position Single Pass Continuous Mode Single Pass w/Me-mory

Debug Mode

0 Closed Open Closed Open

1 Closed Closed Closed Open

2 Closed Closed Open Open

Note: SW1 position marked “SP” is not used.

� Single Pass:Is the default setting, and is the only setting allowed when connected to a laser camera.The start–up diag-nostics execute once, as described in 1-3-4-2 Start–up Sequence.

� Continuous Mode:After executing the start–up diagnostic, the resident software will continuously run the LCAM self–test.Self–test will continue until the first SCSI command is received by the DASM. Please be aware that whenposition 0 is open error and other messages encountered during start–up diagnostics are directed to theserial port. Otherwise the errors are encoded on the LEDs.

� Single Pass w/Memory:Is controlled by Bit 2. When setting to “open”, the DASM exercises the entire DRAM during the start–updiagnostics. The Single Pass w/Memory test can take several minutes to complete, this is why it is normal-ly disabled.

� Debug Mode:When position 1 is open, the program jumps to the I/O Monitor when a diagnostic error occurs. The I/OMonitor gives the basic tools to debug the hardware. Opening positions 0 and 2 allows the technicianaccess to the start–up diagnostic suite via the serial port.


2202125


REV 10

1-3-4-4 Start–up Problem

To report diagnostic conditions, the LEDs on the DASM II–LCAM front panel have a corresponding binary representa-tion. The illustration 1–8 below shows the value assigned to each LED. The section after the figure explains how theLEDs represent error codes. Note that this sections deals with error codes related to the DASM Controller, whereSection 1-3-4-5, LCAM Error Codes, explains the method used to report an error from the LCAM diagnostic.

DASM Controller LED Error Codes

Using LEDs 2 and 4, a binary code signals any of the conditions listed in Table 1–13. The Power light and PIF LEDsare not used to report diagnostic conditions.

The three LEDs permit a combined total of only seven error codes. To overcome this limitation, the codes are definedas a series of one or more patterns. Each pattern begins with all LEDs flashing briefly, to indicate the start of the num-ber sequence that follows.

For example, to display error code 12 (Failed SCSI Interface Test), the CPU LED displays the first digit (1), stoppingbriefly before the SCSI LED displays the second digit (2), as shown in Illustration 1–8.


= 12

All FlashShort

“1”Long

“2”Long

+ +

The display of each digit lasts approximately four times the duration of the initial binary “7” (that is, the flash of allLEDs). The pattern then repeats. Only the significant digits for each error condition are listed in Table 1–13.



2202125


REV 10

1-3-4-4 Start–up Problem (Continued)

Table 1–13 DASM Controller Start–up Error Conditions

Value Significance






6 Checksum Failed





21 Bus Error

22 Address Error







2202125


REV 10

1-3-4-5 LCAM Error Codes

The following sequence is used to signal an error during the LCAM portion of the Self–test.

First, all three LEDs blink together for the duration of a single pass. This requires approximately 10–15 seconds.Then the specific error code blinks twice before the next pass begins, with all three LEDs blinking together as before.

The bit pattern of the error codes appears as a series of LEDs being turned on and off. The low order bit is first.

When two LEDs blink together, the bit value is 1.When only one LED blinks, the bit value is 0.

The Self–test runs in continuous mode when SW 1 position 0 is “open”. A single failure will cause a error code to flashrepreatedly on the LEDs. Although, other errors may occur during testing only the first one is displayed forever.

First all LEDs will blink together several times indicates a problem. Next, the error code is displayed serially, twicein the two leftmost LEDs.

The pattern is binary and takes 4 blinks for the complete code. When the two LEDs blink together, the bit value is1, when only blinks the bit is 0. The bit order is low to high.

Record the blink pattern in the number of LEDs blinking, 1 or 2.

Record them RIGHT to LEFT, to make them easier to interpret.

1 2 1 2 Subtract 1 from each digit to obtain the bit value.0 1 0 1 The value of the code is 5.

Error code meanings:1: DMA time–out Bypass active2: data error. Bypass active3: data error. ROI active4: data error. Bypass, ROI active5: DMA time–out. Swap & bypass active6: data error. Swap & bypass active7: data error. Swap active8: data error. Swap & ROI active9: data error. Swap, ROI active14:SRAM LUT errorNo others are defined.


2202125


REV 10

1-3-4-6 RUN–TIME Error Codes

These codes may be found in the DASM Response Block byte 128, when the error bit (bit 2, where bit 0 is first) isset in Response Block byte 0. Only the first of multiple errors is stored in Response Block byte 128. Reading theResponse Block clears the error. Note that the status “invalid command” is returned to the user directly in bit 0 ofthe SCSI status byte; it is not logged in the Response Block.

Table 1–14 DASM Run Time Error Codes

Error Hex Meaning

General Error Codes

E_PARAM 81 Bad parameter to valid command

E_NO_FF 82 No 0xFF terminator in command

E_TMO 83 Timeout

E_PIF_SELF 84 Peripheral interface self–test error

E_PIFNOTRDY 85 Peripheral device not ready

E_OVRRUN 86 Data overrun

E_UNDRUN 87 Data under run

E_COM_LINK 88 Communications link error between DASM and PIF

E_DRAM 8A Error in I/O RAM (Note: This is a warning, which is available in the trace buffer in theDASM response block. During a warning, byte 128 is not updated.)

E_EPROM 8B EPROM checksum error

E_MFP 8C Error in the MC68901 I/O and timer chip

E_SBIC 8D Error in access to SCSI bus interface chip

E_NOTIMER 8E No timer available (all in use)

E_INTERN 8F Internal system software error

E_INV_MSG B0 Invalid / unexpected message from device

E_BAD_S B1 Invalid S–record (from load routine)

E_ODD_ADR B2 Odd address passed to function

E_BOUNDS B3 I/O request overlapped buffer boundary

E_DIRECTION B4 I/O request direction is invalid

E_NOT_NXT B5 I/O request for data is out of sequence

E_AVAIL_CT B6 I/O request exceed available data count

E_PARITY B7 Parity error

E_PIF_REV B8 No PIF revision level supplied

E_TIMER_ID B9 Timer id error

(Continued)


2202125


REV 10



Error Hex Meaning

M_REJECTED 95 Message was <REJ>ected by partner

M_BADREPLY 96 Unexpected reply was received

E_NOTREADY 97 Camera is not ready

E_TIMEOUT 98 EXEC Function did not complete in time

E_TOOLONG 99 Received telegram has too many characters

E_UNEXPECTED 9A Laser camera replied with an unexpected telegram

E_BADPARAM 9B Bad parameter from host found in CMDBLK

VRTX Error Codes

E_VRTX C1–F4 VRTX error range

– C1 Task ID invalid

– C2 No task control block available

– C3 No Memory available

– C4 No Memory block

– C5 Mailbox in use

– C6 Message of Zero

– C7 Buffer full

– C8 WAITC is in progress

– C9 Invalid system call

– CA Timeout

– CB No Message present

– CC Queue ID error

– CD Queue Full

– CE Partition ID error

– CF Fatal initialization error

– D0 No character present

– D1 Invalid configuration parameter at Init

– D2 Invalid parameter to PCREATE/PEXTEND

– E0 No component vector table

– E1 Invalid component

(Continued)


2202125


REV 10



Error Hex Meaning

– E2 Invalid opcode for component

– F0 No control block available

– F1 Event flag group or semaphore ID error

– F2 Tasks pending on event flag group or semaphore

– F3 Event flag group or semaphore is deleted

– F4 Event flag group already set or overflow


2202125


REV 10

1-4 OTHER BOARDS

Table 1–15 NAA1 LED Description

LED Description

POWER (LED1) Lights while power is supplied.

Illustration 1–9 NAA1

POWERLED1

CN4 CN2 CN3 CN

1


2202125


blank


2202125


REV 25

SECTION 2 – HOST PROCESSOR TROUBLESHOOTING(O2)

NoteFor the system equipped with the Linux PC, refer to Section 3, Host Processor Troubleshooting (Li-nux PC).

2-1 PROBLEM DIAGNOSIS

If you suspect there is a problem with your hardware, use the flowchart (Illustration 2–1) to help isolate and solve theproblem. To view the flowchart, use the magnification function. See also Diagnostic Tests (Section 2-2).

Illustration 2–1 Diagnostic Flow Chart #1

NoNo LED

Yes

NoSolidredLED

Yes

NoBlinkingamberLED

Yes

NoNo boot

tune

Yes

B

YesSY

MP

TO

MP

OS

SIB

LE S

OLU

TIO

NP

OS

SIB

LE C

AU

SE

“ No power to system“ Power supply failure

“ CPU module failure “ Memory diagnostic failure “ Volume set too low“ Headphones plugged in“ Speaker failure

“ System diagnostics successful

“ Check power connections

“ Replace power supply

“ Re–seat CPU module

“ Replace CPU module

NoSolid

amberLED

Yes

“ System board failure

“ Re–seat CPU module“ Re–seat DIMMS on system board

“ Replace system board

“ Verify slots 1 and 2 are populated“ Re–seat DIMMs on system board

“ Replace DIMMs

“ Turn up volume“ Check if headphones are connected

“ Replace system board“ Replace chassis

“ Record message

Yes

Errorcode

message?

SolidgreenLED

No


2202125


REV 25

2-1 PROBLEM DIAGNOSIS (continued)

Illustration 2–2 Diagnostic Flow Chart #2

NoB Solid green LEDNo display

Yes

No

Solidgreen LED

No keyboardKeyboard prompt

on display

Yes

No

Solidgreen LEDNo mouse

Mouse prompton display

Yes

No

Solid

green LEDNo system

drive

Yes

Solid green LEDNo CD–ROM

Yes

“ Monitor not connected

“ Monitor not turned on“ Monitor in power saving

mode“ Monitor brightness too low

“ Cable failure“ Monitor failure

“ System board failure

“ Keyboard not connected

“ Keyboard failure“ System board failure

“ Mouse not connected

“ Keyboard not connected“ Mouse failure

“ Keyboard failure“ System board failure

“ System drive not inserted

all the way“ System drive failure

“ CD–ROM drive not

connected“ CD–ROM drive failure

“ Check monitor connections“ Turn on monitor

“ Check monitor LED“ Adjust monitor brightness

“ Replace monitor cable

“ Replace monitor

“ Replace system board

“ Check keyboard connection

“ Replace keyboard“ Replace system board

“ Check mouse connection“ Check keyboard connection

“ Replace mouse“ Replace system board

“ Record message

“ Check that system drive locking lever is pushed up

all the way

“ Replace system drive

“ Check CD–ROM connections

“ Replace CD–ROM drive

SY

MP

TO

MP

OS

SIB

LE S

OLU

TIO

NP

OS

SIB

LE C

AU

SE

Yes

No

Errorcode

message?

“ Record message

Yes

No

Errorcode

message?

“ Record message

Yes

No

Errorcode

message?

“ Record message

Yes

No

Errorcode

message?

No Wrong Date orTime Displayed

Yes

“ Battery in the RTC onthe system module rundown.

“ Replace the RTC

NOTICERTC Battery Temporary Solution:If the RTC cannot be gotten yet and a customer system shows a wrong date, first the set dateand time using Application Shutdown > Date Setting. Then start up the system.For this temporary recovered system, the OC main switch MUST not be powered OFF aftershutdown. To use the system again, only click on Restart button.This mean that the date and time will be back to the wrong indication if the power is removedfrom the system.


2202125


REV 25

2-2 DIAGNOSTIC TESTS

There are three types of software diagnostics tests provided on the O2 workstation. Each is described below:

� Power–On Tests

� IDE Tests

Power–On Test

These run automatically on the major hardware components of the workstation each time it is turned on. If the testsfind a faulty part, the LED on the front of the system will be red and there will probably be an error message. See alsoProblem Diagnosis (Section 2-1).

IDE Tests

The Interactive Diagnostic Environment (IDE) tests are more comprehensive than the Confidence Tests, and takelonger (as long as 30–45 minutes) to run. See Integrated Diagnostic Environment (IDE) Tests on the SBC (O2) (Sec-tion 2-5).


2202125


REV 25

2-3 RECOVERING FROM SYSTEM CRASH

In most cases, your system will recover from a system crash automatically if you reboot the system.If, however, you have lost data on your system disk, and you cannot communicate with your system using the mouseor keyboard, or over the network, follow these instructions. The instructions assume you have a backup tape of yoursystem that has been made using the System Manager backup tool, or with the /usr/sbin/Backup script. You also needa CD with your current IRIX operating system level. If you are recovering data from a tape on a remote tape device,you need to know the hostname, tape device name, and IP address of the remote system.

1. Use a pen tip or an unwound paper clip to press the RESET button located on the front panel (Illustration 2–3).

Illustration 2–3 Pressing the Reset Button

Silicon-Graphics

2. When you see the System Startup notifier (Illustration 2–4), click STOP FOR MAINTENANCE or press ESC.

Illustration 2–4 System Startup Notifier


2202125


REV 25

2-3 RECOVERING FROM SYSTEM CRASH (continued)

3. From the System Maintenance menu, choose RECOVER SYSTEM, or type 4 on the keyboard. The SystemRecovery Menu appears (Illustration 2–5).

Illustration 2–5 System Recovery Menu

4. If you have a CD–ROM drive connected to your system and the IRIX CD, click LOCAL CD–ROM. Then clickACCEPT to start. Insert the CD when prompted. The system takes five minutes or more to copy the information.If you don -MOTE DIRECTORY.

5. When a notifier appears asking you for the remote hostname, type the system’s name, a colon (:), and the fullpathname of the CD–ROM drive, followed by /dist. For example, to access a CD–ROM drive. On the systemmars, you would type: mars:/CDROM/distAfter everything is copied from the CD to the system disk, you can restore your data from a recent full backuptape. The backup must be one that has been made using the System Manager backup tool, or with the /usr/sbin/Backup script.Tip: If you need to check something on your system during the restore process, you can get ashell prompt by typing sh at most question prompts.

6. If you have a local tape device, you see this message:

Restore will be from <tapename> OK? ([Y]es, [N]o): [Y]

tapename is the name of the local tape device.


2202125


REV 25

2-3 RECOVERING FROM SYSTEM CRASH (continued)

7. If you have a remote (network) tape device, when no tape device is found, or when you answered ‘No’ to thequestion in the previous step, you see this message:

Remote or local restore ([r]emote, [l]ocal):

– If you answer ‘remote,’ you have chosen to restore from the network, and you must know the hostname, tapedevice name, and IP address of the remote system. You also need to know the IP address of your system. TheIP address, such as 192.0.2.1, always has four components separated by periods.– If you answer ‘local,’ you have chosen a tape device that is connected to your system, and you are promptedto enter the name of the tape device.

8. When you see the following message, remove the CD–ROM, insert your most recent full backup tape, then pressENTER.

Insert the first backup tape in the drive, then press <Enter>,[q]uit (from recovery), [r]estart:

There is a pause while the program retrieves several files from the tape describing the system state at the timethe backup was made. Then you see this message:

Erase /x filesystem and make new one (y,n)? [n]

It prompts you for every file system that was known at the time of the backup. Read the following to decide wheth-er to answer y or n.– If you answer n for no, the system tries to salvage as many files as possible. Then it uses your backup tapeto replace the files it could not salvage. Usually you should answer no, especially if your backup tape is not veryrecent. If the file systems were badly damaged, or the backup was from a different level operating system, youmay need to answer yes.– – If you answer y for yes, the system erases the file system and copies everything from your backup tape tothe disk. The system loses any information on that file system that you created between now and when you madeyour backup tape.

9. You see this message:

Starting recovery from tape.

After two or three minutes, the names of the files that the system is copying to the disk start scrolling. When therecovery is complete, you see this message:

Recovery complete, restarting system.

NoteIf your backup tapes were old, or you were changing your operating system level, you should reinstallthe operating system from the IRIX CD that came with your system after system recovery is com-plete. When you see the Startup System notifier, press ESC, or click STOP FOR MAINTENANCE.Then click Install System Software.


2202125


REV 25

2-4 DISABLING THE SYSTEM MAINTENANCE PASSWORD

If you are in the System Maintenance menu, and you choose INSTALL SYSTEM SOFTWARE, RUN DIAGNOSTICS,RECOVER SYSTEM, or ENTER COMMAND MONITOR, you may be prompted for a password.

If you do not know the password, you can disable it by installing a jumper (a small cap that connects two pins) on thesystem board inside the workstation. The system board is located in the system module. To install the jumper, youmust first remove the system module and the PCI tray. Follow these steps:

1. Turn off the workstation by pressing the power button on the front.

2. Remove the system module by releasing the lever on the extreme left as you face the rear of the workstationand sliding the module out. See Section 1–6 System Module, of OC Tabl of the Component Replacement manual.

3. Release and remove the PCI tray. See Section 1–8 PCI Tray, of OC Tabl of the Component Replacement manual.

NOTICEBefore touching any of the components, attach the wrist strap to your wrist and to a metalpart of the chassis.

4. Remove the jumper from the system board in the location shown in Illustration 2–6.

You must remove the jumper if you choose to reset the PROM password.

Illustration 2–6 Removing the Jumper

Jumper


2202125


REV 25

2-4 DISABLING THE SYSTEM MAINTENANCE PASSWORD (continued)

5. Reinstall the jumper in the location shown in Illustration 2–7.

Illustration 2–7 Installing the Jumper

6. Remove the wrist strap.

7. Reinstall the PCI tray in the system module.

8. Reinstall the system module by sliding it into the chassis.


2202125


REV 25

2-5 INTEGRATED DIAGNOSTIC ENVIRONMENT (IDE) TESTS ON THE SBC (O2)

The IDE tests on the O2 are stand alone tests that must be run at the boot PROM level.

To run the O2 IDE tests from the OC, the user must first shut down applications. Next, cu into the SBC by openinga UNIX shell and typing: cu sbc. Once a serial connection has been established, the O2 must be shut down and re–started. Do this by logging into the SBC as root and typing the ‘halt’ command. Press ENTER when prompted to restartthe SBC. When the system begins start–up, a message appears giving the user the option of performing system main-tenance. Press ESC at this prompt to get to the System Maintenance Menu. Choose Option 3, Run Diagnostics.A hardware probe will be conducted and a default set of test scripts will be run automatically. This set takes approxi-mately 10 minutes to execute. Pass and failure information is updated to the screen.

When you run the tests, the following error message may appear. However, ignore this message.

I2C register test HARDWARE FAILURE DMA test error.

INITIATION OF THE O2 IDE TESTS

{ctuser@baya_oc}[2] su –Password:You have mail.baya_oc 1# cu sbcConnected

login: rootPassword:IRIX Release 6.5IP32 baya_sbcCopyright 1987–1998 Silicon Graphics, Inc. All Rights Reserved.Last login: Wed Jun 17 08:49:49 CDT 1998 on ttyd1You have mail.

TERM = (vt100)baya_sbc 1# haltShutdown started. Wed Jun 17 08:52:17 CDT 1998Broadcast Message from root (ttyd1) on baya_sbc Wed Jun 17 08:52:171998

THE SYSTEM IS BEING SHUT DOWN! Log off now.

INIT: New run level: 0The system is shutting down.Please wait.Jun 17 08:52:45 automount[217]: exiting


2202125


REV 25

2-5 INTEGRATED DIAGNOSTIC ENVIRONMENT (IDE) TESTS ON THE O2 (continued)

Running power–on diagnostics...Okay to power off the system now.Press any key to restart.Starting up the system...To perform system maintenance instead, press <Esc>

System Maintenance Menu

1) Start System2) Install System Software3) Run Diagnostics4) Recover System5) Enter Command Monitor

Option? 3

Starting diagnostic program...

Press <Esc> to return to the menu.

SGI Version 6.5 IP32 IDE field April 30, 1998

System: IP32Processor: 200 or 250 Mhz R5000, with FPU

Primary I–cache size: 32 KbytesPrimary D–cache size: 32 Kbytes

Memory size: 128 MbytesGraphics: CRM, Rev CNetwork: DP83840–0PCI Bus: MACE–PCI(0)

SCSI Disk: scsi(0)disk(1)SCSI Disk: scsi(1)disk(1)

Ide included scripts are ’ip32 cpu graphics fast_mem memory•


2202125


REV 25

2-5 INTEGRATED DIAGNOSTIC ENVIRONMENT (IDE) TESTS ON THE O2 (continued)

Other Error Message

If the following error occurs, it indicates that the diagnostics start–up disk is set to disk(2).

pci(0)scsi(0)disk(2)rdisk(0)partition(X) /stand/ide:no such device

In this case, enter the following in the Enter Command Monitor (command input screen):

>resetenv <Enter>

Enter the following to confirm this response:OSloadPartition=pci(0)scsi(0)disk(1)rdisk(0)par-tion(0).

>printenv <Enter>

Then, run the tests again.


2202125


blank


2202125


REV 25

SECTION 3 – HOST PROCESSOR TROUBLESHOOTING(LINUX PC)

NoteFor the system equipped with the O2, refer to Section 2, Host Processor Troubleshooting (O2).

3-1 DIAGNOSTIC TESTS

The Diagnostic CD (2369467–7) can isolate a problem to the HDD, CD–R/W drive, and memory level. These testsincluded the Burn–In test (Automatic, continuous) and manual test.

Always use the Burn–In test.

NOTICEDo not use the manual test!! It is NOT supported at this time.

Never use Diagnostics > Drive(s) > H.Drives > Destructive test in the manual. This test writestest pattern directly to the HDD, so that all of the data in the HDD are destroyed.


2202125


REV 25

3-1-1 Entering the Diagnostic Tests

1. Insert the Diagnostic CD into the CD–ROM drive of the OC.

2. Shut down the OC.

3. Turn the OC power switch OFF, then ON.

4. Approx. 30 seconds later the following screen appears.Do not touch any key for ten seconds to enter the Burn–in Test.

NOTICEDo not use the manual test!! It is NOT supported at this time.


2202125


REV 25

3-1-2 Burn–In Test

The following test automatically runs. When error occurs during tests, an error status is displayed in red and beepsounds. It takes apporox. 20 minutes to complete one cycle of the tests (1 pass). The Burn–In test continues to beperformed for 240 minutes until you stop it using the ESC key twice. This operation enters the manual test mode.

The FE must perform the Burn–In test at least one cycle of the test (1 pass).

Test to be performed Description Defective FRU parts

1 Display Test Run The detailed information to be testedare displayed.

Linux PC unit Assy

2 Beep on Error Linux PC unit Assy

3 Activity is Keyboard LED’s blinking The LED is lit during test. Linux PC unit Assy

4 Test 3 Times CPU1 The CPU1 test is performed threetimes.

Linux PC unit Assy

5 Test 3 Times CPU2 The CPU2 test is performed threetimes.

Linux PC unit Assy

6 Test 3 Times NPU1 The numerical processor1 test is per-formed three times.

Linux PC unit Assy

7 Test 3 Times NPU2 The numerical processor2 test is per-formed three times.

Linux PC unit Assy

8 Test Timer Tests the System timer. Linux PC unit Assy

9 Test RTC Tests the Real Time Clock. Linux PC unit Assy

10 Test KeyBoard Ctrl Tests the keyboard controller. Linux PC unit Assy

11 Test INT #1 Tests the IRQ1. Linux PC unit Assy

12 Test INT #2 Tests the IRQ2. Linux PC unit Assy

13 Test DMA #1 Tests the DMA controller1 of themother board.

Linux PC unit Assy

14 Test DMA #2 Tests the DMA controller2 of themother board.

Linux PC unit Assy

15 Test Drive #1 Quick Auto Tests the HDD with quick scan. HDD and IDE cable

16 Test COM1 (3F8) AutoDetect Tests the COM1 port while automati-cally detected.

Linux PC unit Assy

17 Test Extended Memory Tests the extended memory. Memory

18 Test Cache Memory Tests the cache memory. Linux PC unit Assy

19 Test 2 Minutes VESA RAM Writes random pattern in the VESAmemory for two minutes.

Linux PC unit Assy

20 Repeat if run time less 240 minutes Repeat the tests 1 ~ 19 for 240 min-utes until the ESC key is pressed.

CD–R/W drive

(If all of the tests 1 ~19 are passed at leastone time, the CD–R/W drive is not de-fective.)


2202125


REV 25

3-1-3 Exiting from the Diagnostic Tests

1. When quiting from the Burn–In test, the following menu appears. Remove the Diagnostic CD from the CD–ROMdrive of the OC.

2. Power OFF the OC.


2202125

TABLE/GANTRYi

REV 20

TABLE/GANTRY

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 – LED DESCRIPTION 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2 – POWER–ON TEST 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 TGP BOARD POWER–ON TEST 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1-1 Gantry Processor 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-2 Table Processor 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-3 Management Processor 2–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2 OGP BOARD POWER–ON TEST 2–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4 – ERROR MESSAGE 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 ERROR MESSAGE 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 ERRORS DETECTED BY TGP BOARD (FOR EARLIER THAN SYSTEM VERSION 5.5) .

3–34-3 ERRORS DETECTED BY TGP BOARD (FOR SYSTEM VERSION 5.5 OR LATER) 3–184-4 ERRORS DETECTED BY OGP BOARD 3–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 ERRORS DETECTED BY DAS 3–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

TABLE/GANTRYii

blank


2202125

TABLE/GANTRY1–1

REV 27


Table 1–1 DTRF or DTRF2 LED Description

LED Description

(B)CONERR Lights when an FPGA Configuration error occurs.

(B)DSON Lights when ‘_DSON’ is active.

(B)DSIN Lights when ‘_DSIN’ is active.

+5V Lights while +5 VDC is supplied.

(B)DXFER Lights when ‘DXFER’ is active.

ACK Lights when ‘ACK’ is active. (DTRF and 2233745 DTRF2)

Always OFF. (2233745–2 DTRF2)

(B)CSTRB Lights when a Taxi command (START, ENDOK, or ENDNG) isissued.

(B)FECERR Lights when an FEC encode error occurs.


2202125

TABLE/GANTRY1–2

REV 27

Table 1–2 TGP LED Description

LED Description

CHANGE Lights when adjustment data is not stored during the gantry or table adjust-ment.

SVALM Lights when the servo amplifier (for gantry rotation) is in an alarm state. Thetype of the alarm is indicated on the LED on the amplifier; or, lights also whenAC 200 V power is not supplied to the amplifier.

ERRM Lights when detecting an error concerning processor communication or scanoperations. Set the DIP Switch G2 on the TGP borad to the ON position (toinitialize Gantry rotation) and press the reset button to go off. Then set the G2to the OFF position.

ERRG Lights when detecting an error concerning gantry rotation operations. Goes offwhen the TGP board is powered off or reset.

ERRT Lights when detecting an error concerning table or tilt operations. Goes offwhen the TGP board is powered off or reset.

XGRAY Lights when the safety loop is closed on the TGP board, which indicates thatthe TGP board grants the power supply to the x–ray generator.

LPM Blinks in a one–second cycle, indicating the interval timer operation for commu-nication and scan operations.

RQM Lights when the TGP board receives commands from the operator console andis executing them.

MNM (Not used)

GSF Lights when the rotation safety switches for gantry covers are set and the TGPboard grants gantry rotation.

LPG Blinks in a one–second cycle, indicating the interval timer operation for gantryrotation operations.

RQG Lights when the TGP board receives commands on gantry rotation from theoperator console and is executing them.

TRG Indicates trigger pulses sent to the OGP board.

LPT Blinks in a one–second cycle, indicating the interval timer operation for tableand gantry tilt operations.

RQT Lights when the TGP board receives commands on table or gantry tilt opera-tions from the operator console and is executing them.

MNT Lights when the table or gantry (tilt) is operated by the gantry panel switches.


2202125

TABLE/GANTRY1–3

REV 27

Table 1–3 OGP LED Description

LED Description

DS1 (TEST) Lights when an error occurs.

DS2 (RINGS) MP–SP communication error.(MP: Management Processor on TGP board; SP: Scan Processor on OGPboard)

DS3 (DENTG) DENTG monitor.

DS4 (EXPCMD) EXPCMD monitor.

DS5(REQS) Lights during a task request.

DS6 (LOOPS) Blinks at intervals of 0.5 sec.

DS7 (ERRS) Lights when an error occurs.

See also the following table showing which LED’s light when an error occurs.

Table 1–4 Error and LED on OGP Board

Error LED(The following LED’s light when the error written

to the left occurs)

RAM check error ERRS, LOOPS

ROM check error ERRS

Hang up (detected by the watchdog timer) ERRS, LOOPS, REQS, RINGS, TEST

Hardware error while OGP receives data ERRS, RINGS

ACK, NACK timeout ERRS, RINGS

NACK detected for three times ERRS

NACK transmitted ERRS

Aperture error ERRS

OGP event error ERRS

Scan error ERRS

XG processor communication error ERRS

The ERRS LED goes off when the x–ray tube rotor starts to rotate.

The RINGS LED will not go off until the OGP board is reset.


2202125

TABLE/GANTRY1–4

REV 27

Table 1–5 RF XMT LED Description

LED Description

LED1 Lights while power is supplied.

The light color becomes red, when the RF XMT is not receiving data from theDTRF board.

The light color becomes green, when the RF XMT is receiving data from theDTRF board (where, data is either das data during scans or sync pattern dataduring standby).

Illustration 1–1 RF XMT

LED1

Table 1–6 XMT LED Description

LED Description

POWER(green)

Lights while power is supplied.

SIGNAL Lights when data is prerent. (Transitin detector)

Illustration 1–2 XMT

SIGNAL POWER

TRANSMITTER


2202125

TABLE/GANTRY1–5

REV 27

Table 1–7 RF RCV LED Description

LED Description

Power LED Lights (in green) while power is supplied to the RF shoe.

(Power is supplied from the RF RCV to the RF shoe via a coaxial cable. The LED does notlight if the cable is not correctly connected to the RF shoe, or if power is not supplied to theRF RCV itself.)

AGC Center LED Lights (in green) when the level of the RF output power from the RF shoe is in the middlewithin the proper range.

RF Output LEDs These LEDs are the indicator for the RF output power from the RF shoe.

� Any one of the ten LEDs lights, normally according to gantry rotation.

� LED colors:Right and left ends: redMiddle two: greenOthers: yellow

� When any LED on ‘Normal’ positions lights, it indicates that the RF output power is normal.

� When any LED on ‘Service’ positions lights, it indicates that the RF output power is tooweak or too strong.(In this case, inspect the RF shoe positioning, the power supply for the rotational gantry,or RF slip ring parts on the rotative side, etc.)


2202125

TABLE/GANTRY1–6

REV 27

Illustration 1–3 RF RCV

AGC Center LED

Low HighPower

Service Normal Service

Power LED

RF Output LEDs

Table 1–8 RCV LED Description

LED Description

POWER(green)

Lights while power is supplied.

SIGNAL Lights when data is prerent. (Transitin detector)

Illustration 1–4 RCV

SIGNAL POWER

RECEIVER


2202125

TABLE/GANTRY1–7

REV 27

Table 1–9 TEMP CONT LED Description

LED Description

±0.5° C(LED1)

Lights when the detector temperature is now ±0.5° C from the set temperature.

±2.0° C(LED2)

Lights when the detector temperature is now ±2.0° C from the set temperature.

HIGH ERR

(LED3)

Lights when the detector temperature exceeds 40° C (error).

LOW ERR

(LED4)

Lights when the thermistor is not connected.

SET ERR

(LED5)

Lights when the set temperature is not normal in the variable set temperaturemode.

HEATER

(LED6)

Lights when the heater is turned on.

LOOP

(LED7)

Normally blinks. Goes off when the microprocessor is hung–up.

Illustration 1–5 TEMP CONT

HIGH ERR

CN1

LOOP

HEATER

SET ERR

LED1±0.5° C

7 LEDs

±2.0° C

LOW ERR

LED2

LED3

LED4

LED5

LED6

LED7

CN2


2202125

TABLE/GANTRY1–8

REV 27

Table 1–10 Servo Amp LED Description

7–segment LED Description

– Servo Off

0 Servo On

1 Overcurrent

2 Overload

3 Overspeed

5 Abnormal driver temperature

6 Abnormal encoder

7 Abnormal driving power

9 Abnormal EEPROM

Illustration 1–6 Servo Amp

CN3

7–segment LED

TB2

CN1 CN2


2202125

TABLE/GANTRY1–9

REV 27

Table 1–11 Step Motor Driver LED Description

LED Description

Power LED Lights while power is supplied.

Illustration 1–7 Step Motor Driver

CN3

Power LED

CN1CN2

Table 1–12 IMS Motor Driver LED Description

LED Description

Ready (green) Lights when servo operation is enabled.

Alarm (red) Lights in an alarm state.

Illustration 1–8 IMS Motor Driver

CN3

READY LED

CN1

CN2

CN4

CN5 ALARM LED


2202125

TABLE/GANTRY1–10

blank


2202125

TABLE/GANTRY2–1

REV 9

SECTION 2 – POWER–ON TEST

2-1 TGP BOARD POWER–ON TEST

The TGP board includes the following three microprocessors.

Processor Main Function

Gantry Processor Controls gantry rotation.

Table Processor Controls table and cradle operations and gantry tilt operation.

Controls the gantry display, and interfaces the gantry panelswitches.

Management Processor Communicates with the operator console and the OGP boardon the gantry rotative frame.

Controls the IMS (Intermediate Support).

After powering on or resetting the TGP board, each processor performs ROM based power–on tests in parallel, asdescribed in Table 2–1.

Table 2–1 TGP Power–on Test

Gantry Processor Table Processor Management Processor

RAM Check

↓RAM Check

↓RAM Check

↓

ROM Check

↓ROM Check

↓ROM Check

Gantry Rotation Check and AzimuthCounter Initialization

Gantry Display and Switch LEDCheck

↓

–

– Gantry Tilt and Table Up/down RelayCheck

–

(See Section 2-1-1 for details.) (See Section 2-1-2 for details.) (See Section 2-1-3 for details.)


2202125

TABLE/GANTRY2–2

REV 9

2-1-1 Gantry Processor

RAM Check

1. The gantry processor (U87) performs read/write checks of its internal RAM, the external RAM (U92), and thedual port RAM (U77).

2. If a RAM check error occurs, the processor will stay in a hang up state, with the ERRG, LPG, RQG LED’s lightingon the TGP board.

If no error occurs, the processor proceeds to the following step.

ROM Check

3. The processor performs a data sum check on addresses 0 ∼ BFFF of the external ROM (U112).

4. If a ROM check error occurs, the processor will stay in a hang up state, with the ERRG, LPG, RQG LED’s lighting.

If no error occurs, the LPG LED blinks, and the processor proceeds to the following step.

Gantry Rotation Check and Azimuth Counter Initialization

5. The gantry processor starts rotating the gantry to check that the operation can be normally performed.

a. If the SYS–OFF–MNL service switch (SW1) on the TGP board is set to OFF, the system waits until the switchis set to SYS or MNL, with the RQG and LPG LED’s alternately blinking.

b. If power is not supplied to the servo amplifier, the rotation check is terminated, with the ERRG LED lighting.

If any other abnormal conditions/operations are found, the rotation check is terminated.

To start the rotation check anew, resolve the problems, and power on or reset the TGP board.

6. The gantry rotates at 15 sec/Rev, and the processor initializes the gantry azimuth counter with the GPLS1 signal.

a. If the initialization of the counter is not performed within 25 sec, the rotation is terminated, with the ERRG LEDlighting.


2202125

TABLE/GANTRY2–3

REV 9

2-1-2 Table Processor

RAM Check

1. The table processor (U42) performs read/write checks of its internal RAM, the external RAM (U64), and the dualport RAM (U48).

2. If a RAM check error occurs, the processor will stay in a hang up state, with the ERRT, LPT, RQT, MNT LED’slighting on the TGP board.


ROM Check

3. The processor performs a data sum check on addresses 0 ∼ DFFF of the external ROM (U68).

4. If a ROM check error occurs, the processor will stay in a hang up state, with the ERRT, RQT, MNT LED’s lighting.

If no error occurs, the LPT LED blinks, and the processor proceeds to the following step.

Gantry Display and Switch LED Check

5. The processor sequentially displays test characters (numbers) on the gantry display, and at the same time, se-quentially lights gantry panel switch LED’s.Refer to the Rotational Operation section of Gantry, of the Functional Check / Adjustment manual.

Gantry Tilt and Table Up/down Relay Check

The gantry tilt or table up/down operation is performed by a pump/valve mechanism which is powered by AC 115 V.This power is conveyed through two relays connected in series on SUB BD. Refer to Illustration 2–1. With theseconnections, if one relay of the two failed (that is, always closed), the power flow can be cut off by the other relay.This check verifies these relay operations.

6. The processor closes one relay which is controlled by the enable lines, and verifies that the gantry tilt or tableup/down does not take place.

If the operation takes place, the other relay (direct) is considered to be failed (closed), since any key on the gantryswitch panel is not pressed while the relay (enable) is activated; and an error message is displayed on the opera-tor console (OC).

7. An LED blinks on the gantry switch panel, and then press the key with the LED blinking.

If the corresponding operation takes place, the other relay (enable) is considered to be failed (closed), since theprocessor does not activate the relay (enable) while the key is pressed; and an error message is displayed onthe OC.


2202125

TABLE/GANTRY2–4

REV 9

2-1-2 Table Processor (continued)

Illustration 2–1 Safety by Double Relays

TableProcessor

TGP Board

SUB Board

Gantry Tilt orTable Up/Down

AC 115 V

GantryPanelSwitch

EnableDirect

2-1-3 Management Processor

RAM Check

1. The management processor (U88) performs read/write checks of its internal RAM, the external RAM (U62), andthe dual port RAM (U48, U77).

2. If a RAM check error occurs, the processor will stay in a hang up state, with one of ERRM, LPM, RQM, MNMLED’s lighting on the TGP board.


ROM Check

3. The processor performs a data sum check on addresses 0 ∼ BFFF of the external ROM (U111).

4. If a ROM check error occurs, the processor will stay in a hang up state, with the ERRM, RQM, MNM LED’s light-ing.

If no error occurs, the LPM LED blinks.


2202125

TABLE/GANTRY2–5

REV 9

2-2 OGP BOARD POWER–ON TEST

The OGP board is equipped on the gantry rotative frame and includes a microprocessor called Scan Processor, andmainly performs the following controls in scan sequence, according to commands from the Management processoron the TGP board.

� Scan control

� DAS control

� X–ray generator (JEDI) control

� Aperture control

� Positioning light control

After powering on or resetting the OGP board, the scan processor performs ROM based power–on tests (RAM check→ ROM check), as described below.

RAM Check

1. The scan processor performs read/write checks of the external RAM and its internal RAM.

2. If a RAM check error occurs, the processor will stay in a hang up state, with the ERRS, LOOPS LED’s lightingon the OGP board.


ROM Check

3. The processor performs a data sum check of the external ROM.

4. If a ROM check error occurs, the processor will stay in a hang up state, with the ERRS LED lighting.

If no error occurs, the LOOPS LED blinks.


2202125

TABLE/GANTRY2–6

blank


2202125

TABLE/GANTRY3–1

REV 20

SECTION 3 – ERROR MESSAGE

3-1 ERROR MESSAGE

The errors described in Table 3–1 through 3–53 are detected by the TGP, OGP, or CIF board. When an error occurs,the error information is sent to the operator console (OC) using the Status communication.

Error with no Error Message

If either of the following errors occur, the microprocessor on the TGP or OGP board are forced to run in an infiniteloop, and no error message is sent to the OC.

� RAM, ROM check error:These checks are performed during a power–up sequence.

� Processor hang up:This is detected by the watchdog timer at intervals of 10.9 msec.


2202125

TABLE/GANTRY3–2

REV 20

3-1 ERROR MESSAGE (continued)

Error Class

The errors detected by the TGP, OGP, or CIF board are either classified as Error Class, or Information Class, accord-ing to below:

� Error:If an error of this ‘Error’ class occurs during a scan, the scan is aborted, and an error message is displayedon the OC monitor.

� Information (written as ‘Infor.’ in Table 3–1 ∼ 3–53):If an error of this ‘Information’ class occurs during a scan, the scan will be continued, and an error messageis not displayed on the OC monitor.

Communication via Slip Rings (RS422)

The scan processor on the OGP board communicates with the management processor on the TGP board via sliprings.Normally, when one of the two processors receives communication data from the other processor, the receiving proc-essor checks a checksum data, and sends back an ACK message to the sender, if the data is OK; otherwise, sendsback a NACK message. When the sender receives this NACK message, it resends the data. If this repeats threetimes (three NACK’s), the communication is regarded as an error. If the receiver does not send ACK nor NACK withina specified time, this also is regarded as an error communication.


2202125

TABLE/GANTRY3–3

REV 20

3-2 ERRORS DETECTED BY TGP BOARD (FOR EARLIER THAN SYSTEM VERSION 5.5)

NoteFor systems with system software version 6 or later, see Section 3-3, Errors Detected by TGP Board(for System Version 5.5 or Later).

Table 3–1 Scan Error

ErrorCode

Code Name Class Description Potential Cause / FRU

0D 11–1001–0D Interlock X–ray. Error TGP received SCAN CMD while relay(RL1) inGantry Rear Switch Box is energized.

1. Other equipment connected with relay(RL1)is unexpectedly active(H).; 2. Cable connec-tion between RL1 and other equipment(M).

Table 3–2 Helical Scan Error

ErrorCode


11 12–1001–11 Cradle Out of Limit.(TP)

Error Cradle position out of limit on Helical SCANCMD.

1. Cradle Potentiometer; 2. IMS potentiometer

12 12–1001–12 Cradle Unlatch. (TP) Error Cradle unlatch was detected on Helical SCANCMD.

1. Accidental push on Latch Switch.; 2. Cab-ling between Latch Switch and TGP includingTBLCON BD and TBL BD.

13 12–1001–13 Cradle Slip. (TP) Error Cradle slip was detected during Helical Scan. 1. Patient movement during Helical Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder

14 10–0001–14 Undefined Infor. – –

15 12–1001–15 Cradle Start PositionError. (TP)

Error Cradle start position is out of specification onHelical Scan.

Cradle Stepping Motor Belt or Cradle SteppingMotor

16 12–1001–16 Interval Position Error.(TP)

Error Cradle Interval is out of specification on HelicalScan.

1. Patient movement during Helical Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder

(continued)


2202125

TABLE/GANTRY3–4

REV 20

3-2 ERRORS DETECTED BY TGP BOARD (FOR EARLIER THAN SYSTEM VERSION 5.5) (continued)

Table 3–2 Helical Scan Error (continued)

ErrorCode


17 12–1001–17 Cradle Move TimeOut. (TP)

Error Cradle acceleration/deceleration time out. Ortotal cradle movement time out on HelicalScan.

1. Patient movement at the beginning of Heli-cal Scan.; 2. Cradle Stepping Motor Belt orCradle Stepping Motor

18 12–1001–18 OC Command Error.(TP)

Error TGP(MP) received unspecified Helical SCANCMD from OC.

Take a best guess and good luck.

19 11–1001–19 SCINITREQ TimeOut. (MP)

Error TGP(MP) did not receive SCINTREQ fromTGP(TP) on Helical Scan.


1A 11–1001–1A OGP Com Not Readyin 1 sec. (MP)

Error Communication with OGP is not ready after1sec during Helical SCAN CMD.

TGP

1B 11–1001–1B TP Com Not Ready in1 sec. (MP)

Error Communication with TGP(TP) is not ready af-ter 1sec during Helical SCAN CMD.

TGP

1C 10–0001–1C Undefined Infor. – –

1D 10–0001–1D Undefined Infor. – –

1E 10–0001–1E Undefined Infor. – –

1F 12–1001–1F Cradle Potentio Error.(TP)

Error Unexpected input from Cradle Potentiometerduring Helical Scan.

Cradle Potentiometer or Cabling between TGPand Cradle Potentiometer.


2202125

TABLE/GANTRY3–5

REV 20


Table 3–3 Scout Scan Error

ErrorCode



Error Cradle position out of limit on Scout SCANCMD.


42 12–1001–42 Cradle Unlatch. (TP) Error Cradle unlatch was detected on Scout SCANCMD.


43 12–1001–43 Cradle Slip. (TP) Error Cradle slip was detected during Scout Scan. 1. Patient movement during Scout Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder



Error Cradle start position is out of specification onScout Scan.




Error Cradle acceleration/deceleration time out. Ortotal cradle movement time out on Scout Scan.




Error TGP(MP) did not receive SCINTREQ fromTGP(TP) on Scout Scan.

TGP


Error Communication with OGP is not ready after1sec during Scout SCAN CMD.

TGP


Error Communication with TP is not ready after 1secduring Scout SCAN CMD.

TGP

4C 11–1001–4C Offset Scan Time Out.(MP)

Error TGP did not receive OFFSET END from OGPon Scout Scan.

OGP or TGP/OGP interface which includesSlip Ring.

(continued)


2202125

TABLE/GANTRY3–6

REV 20


Table 3–3 Scout Scan Error (continued)

ErrorCode



4E 11–1001–4E Scout Scan Time Out.(MP)

Error TGP did not receive SCAN END from OGP onScout Scan.



Error Unexpected input from Cradle Potentiometerduring Scout Scan.



2202125

TABLE/GANTRY3–7

REV 20


Table 3–4 Fluoro Scan Error

ErrorCode









58 11–1001–58 XRAY–on timeout.(MP)

Error mA/kV status was not received from OGP inresponse to Fluoro SCAN CMD.

JEDI(kV control or CT–IF), or interface be-tween JEDI and OGP.

59 11–1001–59 XRAY–off timeout.(MP)

Error mA/kV status from OGP did not stop whenX–ray Foot SW is off during Fluoro Scan.

JEDI(kV control)

5A 11–1001–5A OGP Com is notready in 1sec. (MP)

Error Communication with OGP is not ready after1sec during Fluoro SCAN CMD.

TGP

5B 10–0001–5B Undefined Infor. – –

5C 11–1001–5C Fluoro scan commandin normal mode. (MP)

Error Fluoro SCAN CMD is received from OC whenNFIX is not in Fluoro mode.

NFIX or TGP/NFIX interface

5D 11–1001–5D X–SW is not on for1sec before scancommand. (MP)

Error Fluoro SCAN CMD is received from OC afterX–ray Foot SW is off.

NFIX or Cabling between TGP and NFIX

5E 11–1001–5E Scan command hascome while GNTRYbutton is pushed .(MP)

Error Fluoro SCAN CMD is received while Gantrybutton is pushed.


5F 10–0001–5F Undefined Infor. – –


2202125

TABLE/GANTRY3–8

REV 20


Table 3–5 Gantry Req Error

ErrorCode


1 13–1002–01 Gantry Request Com-mand Error. (GP)

Error Unspecified GNTRY CMD was received fromOC.

Mismatched version between TGP firmwareand OC software.

2 13–1002–02 Gantry Set Time Outin 20 sec. (GP)

Error Gantry position or rotation speed is not readyin 20sec after GNTRY CMD from OC.

1. Servo Amp; 2. Axial Motor

3 13–1002–03 Axial Motor OverHeat. (GP)

Error Axial Motor over heat is detected. 1. Axial Motor; 2. SUB BD

4 13–1002–04 Servo Amp Alarm.(GP)

Error Servo Amp alarm is detected. 1. Too many acceleration/deceleration in shortduration.; 2. Servo Amp; 3. Axial Motor

5 13–1002–05 Gantry Not SystemMode. (GP)

Error Switch of TGP is not set as system mode. Switch of TGP is not set as system mode.

6 13–1002–06 Gantry Rotate NotResponse. (GP)

Error No feedback from Axial motor encoder wasdetected after Gantry rotation request.

1. Service Switch on SUB BD is set.; 2. 24VPower Supply; 3. Servo Amp; 4. Axial Motor;5. Cabling between Axial Motor and TGP

7 13–1002–07 Gantry Rotate OverSpeed. (GP)

Error Gantry rotation speed is over specification. 1. Rotation Speed Adjustment; 2. Servo Amp;3. TGP

8 13–1002–08 Gantry Rotate UnderSpeed. (GP)

Error Gantry rotation speed is under specification. 1. Rotation Speed Adjustment; 2. Servo Amp;3. TGP

9 13–1002–09 Cover Safty SWOpen. (GP)

Error Gantry Cover Switch is open and Axial Motoris not powered.

1. Alignment between Gantry cover andGantry Cover Switch; 2. Gantry Cover Switchand its cabling to TGP

A 13–1002–0A Dynamic Break On.(GP)

Error GNTRY CMD was received while Axial Motordynamic break working.


B 13–1002–0B Gantry Init Error orPosition Error. (GP)

Error Gantry was not initialized correctly. Or azi-muth counter on TGP is overflow.

1. G–Pulse1(M); 2. TGP; 3. Cabling betweenG–Pulse1 and TGP

(continued)


2202125

TABLE/GANTRY3–9

REV 20


Table 3–5 Gantry Req Error (continued)

ErrorCode


C 10–0002–0C Undefined Infor. – –

D 10–0002–0D Undefined Infor. – –

E 11–1002–0E Gantry 130sec(180sat Smartview) timer istimeout on TGP. (MP)

Error Gantry continues to rotate over 130sec withoutGNTRY CMD nor SCAN CMD from OC.

1. Cabling between TGP and OC; 2. OC couldnot send GNTRY CMD nor SCAN CMD toTGP.

F 11–1002–0F Gantry init timeoutack=100ms rdy=7sec.(MP)

Error TGP did not receive reply from OGP in re-sponse to Gantry initialize request.

1. G–Pulse2; 2. OGP or TGP/OGP interfacewhich includes Slip Ring.


2202125

TABLE/GANTRY3–10

REV 20


Table 3–6 Gantry Req Error Code2

ErrorCode


1 13–1002–11 Over Current. Over Current Error was detected on ServoAmp.

1. Servo AMP; 2. Axial Motor

2 13–1002–12 Over Load. Over Load Error was detected on Servo Amp. 1. Gantry acceleration/deceleration too fre-quent.; 2. Servo AMP; 3. Axial Motor

3 13–1002–13 Over Speed. Over Speed Error was detected on ServoAmp.

Servo AMP


5 13–1002–15 Abnormal Servo AmpTemparature.

Servo Amp. Temperature is out of specifica-tion.

Servo AMP

6 13–1002–16 Abnormal Encorder Output from Axial Motor Encoder is out ofspecification.

1. Axial Motor; 2. Servo Amp

7 13–1002–17 Abnormal DrivingPower.

Driving Power of Servo Amp is out of specifi-cation.



9 13–1002–19 Abnormal EEPROM. Abnormal EEPROM error was detected onServo Amp.

1. Servo AMP

A 10–0002–1A Undefined Infor. – –

B 10–0002–1B Undefined Infor. – –



E 10–0002–1E Undefined Infor. – –

F 10–0002–1F Undefined Infor. – –


2202125

TABLE/GANTRY3–11

REV 20


Table 3–7 Cradle Req Error

ErrorCode


1 12–1030–01 Cradle Out of Limit. Cradle position out of limit on CRADLE CMD. 1. Cradle Potentiometer; 2. IMS Potentiometer

2 12–1030–02 Cradle Unlatch. Cradle unlatch was detected on CRADLECMD.


3 12–1003–03 Cradle Slip. Cradle slip was detected in response toCRADLE CMD.

1. Patient movement during cradle movementor some obstacles on bottom of cradle orcradle roller.; 2. Cradle Encoder


5 12–1003–05 Out of ScannableRange.

Scannable range is zero because table posi-tion is too low.

1. Table position is too low. Raise table tohigher position.; 2. Table Height Potentiometer


7 12–1003–07 Cradle Move TimeOut.

Cradle acceleration/deceleration time out. Ortotal cradle movement time out in response toCRADLE CMD.









F 12–1003–0F Cradle Potentio Error. Unexpected input from Cradle Potentiometerin response to CRADLE CMD.



2202125

TABLE/GANTRY3–12

REV 20


Table 3–8 Tilt Req Error

ErrorCode


1 12–1004–01 Out of Tilt Range. Error Out of Tilt range on TILT CMD. Tilt Potentiometer or IMS Potentiometer

2 12–1004–02 Touch Sensor On. Error Gantry Touch Sensor ON was detected duringremote tilt. Bring tilt position back by a fewangle to recover.

1. Gantry Touch Sensor; 2. FCV BD or RCVBD

3 12–1004–03 Already Home Key Onor FWD/BWD KeyOn.

Error TILT CMD was received from OC duringHome/FWD/BWD is ON.

–

4 12–0004–04 Home Key On orFWD/BWD(COUNT-ER DIRECTION) KeyOn.

Error Home/FWD/BWD is pushed during remote–tilt-ing. And Home/FWD/BWD was prioritized asthe result.

–

5 12–0004–05 FWD/BWD(SAME DI-RECTION) Key Off.

Error Home/FWD/BWD is released during remote–tilting and Home/FWD/BWD was prioritized asthe result.

–

6 12–1004–06 Interlock or MovementError.

Error Interlock was detected during remote–tilting. Tilt Potentiometer or IMS Potentiometer

7 12–1004–07 OCTILT Line Off. Error OCTILT line from OC was detected OFF butTILT STOP CMD from OC was not received.

1. OC could not send Tilt Stop CMD to TGP intime.; 2. OC Keyboard.

8 12–1004–08 Tilt Req TimeOut 68sec.

Error Total tilting time from start tilting to end wasover specified duration.

Tilt Valve or Tilt Pump




(continued)


2202125

TABLE/GANTRY3–13

REV 20


Table 3–8 Tilt Req Error (continued)

ErrorCode





F 10–0004–0F Undefined Infor. – –

Table 3–9 Manual Table Error

ErrorCode


1 12–1005–01 Single fault in T/Gmovement, Pleasecall service.

Error Tilt BWD/FWD movement or Table UP/DWNmovement is detected during key switch teston Gantry initialization.

1. KEY SW L or R on Gantry Cover may havethe falure and stay ON.; 2. SUB BD





6 12–1005–06 IMS POTENTIO error. Error Unexpected input from IMS Potentiometer dur-ing manual IMS movement.

IMS Potentiometer or Cabling between TGPand IMS Potentiometer.

7 12–1005–07 CRADLE POTENTIOerror.

Error Unexpected input from Cradle Potentiometerduring manual cradle movement.



2202125

TABLE/GANTRY3–14

REV 20


Table 3–10 Scan Processor Communication Error

ErrorCode


1 11–1010–01 Nack Detected 3Times.

Error TGP(MP) received the message ’Not Acknowl-edged’ from OGP more than 3 times.

TGP or OGP

2 11–1010–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from OGP.


3 11–1010–03 SP is not wake up. Error TGP(MP) did not receive any reply from OGPin response to SysConfig CMD.







2202125

TABLE/GANTRY3–15

REV 20


Table 3–11 Gantry Processor Communication Error

ErrorCode



Error TGP(MP) received the message ’Not Acknowl-edged’ from TGP(GP) more than 3 times.

TGP

2 11–1013–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from TGP(GP).

TGP

3 11–1013–03 GP is not wake up. Error TGP(MP) did not receive any reply fromTGP(GP) in response to SysConfig CMD.

Gantry Initialization did not complete correctly.;1. TGP; 2. G–Pulse1; 3. Cabling between TGPand G–Pluse1; 4. Servo Amp or Axial Motor






2202125

TABLE/GANTRY3–16

REV 20


Table 3–12 Table Processor Communication Error

ErrorCode



Error TGP(MP) received the message ’Not Acknowl-edged’ from TGP(TP) more than 3 times.

TGP

2 11–1012–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from TGP(TP).

TGP

3 11–1012–03 TP is not wakeup. Error TGP(MP) did not receive any reply fromTGP(TP) in response to SysConfig CMD.

TGP





Table 3–13 TGP Task Time Out Error

ErrorCode


1 11–10F0–01 Scan Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to SCAN CMD.


2 11–10F0–02 XG Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to XG CMD.


3 11–10F0–03 Aperture Mode TimeOut.

Error TGP(MP) did not receive any reply from OGPin response to APERTURE CMD.


(continued)


2202125

TABLE/GANTRY3–17

REV 20



ErrorCode


4 11–10F0–04 Gantry Mode TimeOut.

Error TGP(MP) did not receive any reply fromTGP(GP) in response to GNTRY CMD.

TGP

5 11–10F0–05 Cradle Mode TimeOut.

Error TGP(MP) did not receive any reply fromTGP(TP) in response to CRADLE CMD.

TGP

6 11–10F0–06 Tilt Mode Time Out. Error TGP(MP) did not receive any reply fromTGP(TP) in response to TILT CMD.

TGP

7 11–10F0–07 Test Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to TEST MODE CMD.


Table 3–15 TGP not System

ErrorCode


1 11–10F1–01 TGP Not System. Error TGP is not set as System Mode. Set TGP switch(SW1) correctly.

Table 3–16 Safety Loop Open

ErrorCode


1 11–10F2–01 SAFETY LOOPOPEN.

Error mA/kV status was not received from OGP dur-ing X–ray ON. Or X–ray OFF Status was notreceived correctly from OGP. Safety Loopwas opened by TGP as the result.

JEDI(kV control or CT–IF) or interface be-tween JEDI and TGP including OGP and SlipRing.


2202125

TABLE/GANTRY3–18

REV 20

3-3 ERRORS DETECTED BY TGP BOARD (FOR SYSTEM VERSION 5.5 OR LATER)

Table 3–17 Scan Error

ErrorCode


01 11–1001–01 Gantry–Transporterposition is not initial-ized.

Error TGP received SCAN CMD before initializinggantry transporter. Bring gantry transporterback to out end position.

Scan operation before gantry position initializ-ing.

02 11–1001–02 Table is not CT mode. Error ”TABLE READY” signal from Table is open onSCAN CMD

Table system is powered off. Angles of Table–rotations are not directed to CT. Lateral posi-tion of Table top is not in center of Gantry–ap-erture.

03 11–1001–03 Table is moving duringscan.

Error ”TABLE MOVE” signal from Table is open onSCAN CMD

Table movement button is pushed or Tablemovement is not locked during CT scanning.

04 11–1001–04 ”STOP CT” signalcomes from Table onscan process.

Error ”STOP CT” signal from the table is open onSCAN CMD. Reset the table from Emergen-cy Stop status.

STOP button of the Table is pushed.

05 11–1001–05 Undefined Infor. Undefined Error





0A 11–1001–0A Undefined Infor. Undefined Error

0B 11–1001–0B Undefined Infor. Undefined Error

0C 11–1001–0C Undefined Infor. Undefined Error

0D 11–1001–0D Interlock X–ray. Error TGP received SCAN CMD while relay(RL1) inGantry Rear Switch Box is energized. Unex-pected door interlock may cause this.

1. Other equipment connected with relay(RL1)is unexpectedly active(H).; 2. Cable connec-tion between RL1 and other equipment(M).

0E 11–1001–0E Undefined Infor. Undefined Error

0F 11–1001–0F Undefined Infor. Undefined Error


2202125

TABLE/GANTRY3–19

REV 20

3-3 ERRORS DETECTED BY TGP BOARD (FOR SYSTEM VERSION 5.5 OR LATER) (continued)


ErrorCode



Error Cradle position out of limit on Helical SCANCMD.


12 12–1001–12 Cradle Unlatch. (TP) Error Cradle unlatch was detected on Helical SCANCMD.


13 12–1001–13 Cradle Slip. (TP) Error Cradle slip was detected during Helical Scan. 1. Patient movement during Helical Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder



Error Cradle start position is out of specification onHelical Scan.


16 12–1001–16 Interval Position Error.(TP)

Error Cradle Interval is out of specification on HelicalScan.

1. Patient movement during Helical Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder


Error Cradle acceleration/deceleration time out. Ortotal cradle movement time out on HelicalScan.

1. Patient movement at the beginning of Heli-cal Scan.; 2. Cradle Stepping Motor Belt orCradle Stepping Motor

18 12–1001–18 OC Command Error.(TP)

Error TGP(TP) received unspecified Helical SCANCMD from OC.



Error TGP(MP) did not receive SCINTREQ fromTGP(TP) on Helical Scan.



Error Communication with OGP is not ready after1sec during Helical SCAN CMD.

TGP


Error Communication with TGP(TP) is not ready af-ter 1sec during Helical SCAN CMD.

TGP


(continued)


2202125

TABLE/GANTRY3–20

REV 20



ErrorCode


1D 12–1001–1D Transporter ServoAlarm detected

Error Servo Amp alarm is detected at the transport-er.

Any foreign objects on rails or linear guide,Servo Amp & Motor wiring, Brake is held.

1E 12–1001–1E Over Run Switch orTouch Sensor de-tected

Error Over run limit switch of transporter or GantryTouch Sensor ON was detected during Helicalscan. Bring transporter position back by a fewdistance to recover.

Anything touches on touch sensor during Heli-cal scan. Gantry was located to overrun posi-tion manually. Any foreign objects on Overrunsensor.


Error Unexpected input from Cradle Potentiometerduring Helical Scan.



2202125

TABLE/GANTRY3–21

REV 20


Table 3–19 Axial Scan Error

ErrorCode


21 11–1001–21 OC Command Error.(MP)

Error TGP(MP) received unspecified RespiratorySCAN CMD from OC.


22 11–1001–22 Gate Pulse Timeout.(MP)

Error Respiratory Signal Timeout. (Continue H–LEV-EL)

TGP,NFIX,CONNECTION BOX, (RespiratoryMonitor)

23 11–1001–23 Gate Pulse Timeout.(MP)

Error Respiratory Signal Timeout. (not detect risingedge)

TGP,NFIX,CONNECTION BOX, (RespiratoryMonitor)








Error Communication with OGP is not ready after1sec during Respiratory SCAN CMD.

TGP



2D 11–1001–2D Undefined Infor. Undefined Error

2E 11–1001–2E Undefined Infor. Undefined Error

24 11–1001–2F Undefined Infor. Undefined Error


2202125

TABLE/GANTRY3–22

REV 20



ErrorCode



Error Cradle position out of limit on Scout SCANCMD.


42 12–1001–42 Cradle Unlatch. (TP) Error Cradle unlatch was detected on Scout SCANCMD.


43 12–1001–43 Cradle Slip. (TP) Error Cradle slip was detected during Scout Scan. 1. Patient movement during Scout Scan orsome obstacles on bottom of cradle or cradleroller.; 2. Cradle Encoder



Error Cradle start position is out of specification onScout Scan.


46 12–1001–46 Over Run Switch orTouch Sensor de-tected

Error Over run limit switch of transporter or GantryTouch Sensor ON was detected during Scoutscan. Bring transporter position back by a fewdistance to recover.

Anything touches on touch sensor duringScout scan. Gantry was located to overrunposition manualy. Any foreign objects on Over-run sensor._-__-_


Error Cradle acceleration/deceleration time out. Ortotal cradle movement time out on Scout Scan.


48 12–1001–48 Transporter ServoAlarm


Any foreign objects on rails or linear guide,Servo Amp & Motor wireing, Brake is held._-_


Error TGP(MP) did not receive SCINTREQ fromTGP(TP) on Scout Scan.

TGP


Error Communication with OGP is not ready after1sec during Scout SCAN CMD.

TGP


Error Communication with TP is not ready after 1secduring Scout SCAN CMD.

TGP

(continued)


2202125

TABLE/GANTRY3–23

REV 20



ErrorCode


4C 11–1001–4C Offset Scan Time Out.(MP)

Error TGP did not receive OFFSET END from OGPon Scout Scan.


4D 10–0001–4D Undefined Infor. Undefined Error

4E 11–1001–4E Scout Scan Time Out.(MP)

Error TGP did not receive SCAN END from OGP onScout Scan.



Error Unexpected input from Cradle Potentiometerduring Scout Scan.



2202125

TABLE/GANTRY3–24

REV 20



ErrorCode









58 11–1001–58 XRAY–on timeout.(MP)

Error mA/kV status was not received from OGP inresponse to Fluoro SCAN CMD.


59 11–1001–59 XRAY–off timeout.(MP)

Error mA/kV status from OGP did not stop whenX–ray Foot SW is off during Fluoro Scan.

JEDI(kV control)

5A 11–1001–5A OGP Com is notready in 1sec. (MP)

Error Communication with OGP is not ready after1sec during Fluoro SCAN CMD.

TGP


5C 11–1001–5C Fluoro scan commandin normal mode. (MP)

Error Fluoro SCAN CMD is received from OC whenNFIX is not in Fluoro mode.

NFIX or TGP/NFIX interface

5D 11–1001–5D X–SW is not on for1sec before scancommand. (MP)

Error Fluoro SCAN CMD is received from OC afterX–ray Foot SW is off.

NFIX or Cabling between TGP and NFIX

5E 11–1001–5E Scan command hascome while GNTRYbutton is pushed .(MP)

Error Fluoro SCAN CMD is received while Gantrybutton is pushed.


5F 10–0001–5F Undefined Infor. Undefined Error


2202125

TABLE/GANTRY3–25

REV 20


Table 3–22 Gantry Req Error

ErrorCode


1 13–1002–01 Gantry Request Com-mand Error. (GP)

Error Unspecified GNTRY CMD was received fromOC.


2 13–1002–02 Gantry Set Time Outin 20 sec. (GP)

Error Gantry position or rotation speed is not readyin 20sec after GNTRY CMD from OC.

1. Servo Amp; 2. Axial Motor

3 13–1002–03 Axial Motor OverHeat. (GP)

Error Axial Motor over heat is detected. 1. Axial Motor; 2. SUB BD

4 13–1002–04 Servo Amp Alarm.(GP)

Error Servo Amp alarm is detected. 1. Too many acceleration/deceleration in shortduration.; 2. Servo Amp; 3. Axial Motor

5 13–1002–05 Gantry Not SystemMode. (GP)

Error Switch of TGP is not set as system mode. Switch of TGP is not set as system mode.

6 13–1002–06 Gantry Rotate NotResponse. (GP)

Error No feedback from Axial motor encoder wasdetected after Gantry rotation request.

1. Service Switch on SUB BD is set.; 2. 24VPower Supply; 3. Servo Amp; 4. Axial Motor;5. Cabling between Axial Motor and TGP

7 13–1002–07 Gantry Rotate OverSpeed. (GP)

Error Gantry rotation speed is over specification. 1. Rotation Speed Adjustment; 2. Servo Amp;3. TGP

8 13–1002–08 Gantry Rotate UnderSpeed. (GP)

Error Gantry rotation speed is under specification. 1. Rotation Speed Adjustment; 2. Servo Amp;3. TGP

9 13–1002–09 Cover Safty SWOpen. (GP)

Error Gantry Cover Switch is open and Axial Motoris not powered.

1. Alignment between Gantry cover andGantry Cover Switch; 2. Gantry Cover Switchand its cabling to TGP

A 13–1002–0A Dynamic Break On.(GP)

Error GNTRY CMD was received while Axial Motordynamic break working.


B 13–1002–0B Gantry Init Error orPosition Error. (GP)

Error Gantry was not initialized correctly. Or azi-muth counter on TGP is overflow.

1. G–Pulse1(M); 2. TGP; 3. Cabling betweenG–Pulse1 and TGP

C 10–0002–0C Undefined Infor. Undefined Error

(continued)


2202125

TABLE/GANTRY3–26

REV 20


Table 3–5 Gantry Req Error (continued)

ErrorCode


D 10–0002–0D Undefined Infor. Undefined Error

E 11–1002–0E Gantry 130sec(180sat Smartview) timer istimeout on TGP. (MP)

Error Gantry continues to rotate over 130sec withoutGNTRY CMD nor SCAN CMD from OC.

1. Cabling between TGP and OC; 2. OC couldnot send GNTRY CMD nor SCAN CMD toTGP.

F 11–1002–0F Gantry init timeoutack=100ms rdy=7sec.(MP)

Error TGP did not receive reply from OGP in re-sponse to Gantry initialize request.

1. G–Pulse2; 2. OGP or TGP/OGP interfacewhich includes Slip Ring.


2202125

TABLE/GANTRY3–27

REV 20


Table 3–23 Gantry Req Error Code2

ErrorCode


1 13–1002–11 Over Current. Error Over Current Error was detected on ServoAmp.


2 13–1002–12 Over Load. Error Over Load Error was detected on Servo Amp. 1. Gantry acceleration/deceleration too fre-quent.; 2. Servo AMP; 3. Axial Motor

3 13–1002–13 Over Speed. Error Over Speed Error was detected on ServoAmp.

Servo AMP

4 10–0002–14 Undefined Infor-mai-ton

Undefined Error

5 13–1002–15 Abnormal Servo AmpTemparature.

Error Servo Amp. Temperature is out of specifica-tion.

Servo AMP

6 13–1002–16 Abnormal Encorder Error Output from Axial Motor Encoder is out ofspecification.

1. Axial Motor; 2. Servo Amp

7 13–1002–17 Abnormal DrivingPower.

Error Driving Power of Servo Amp is out of specifi-cation.



9 13–1002–19 Abnormal EEPROM. Error Abnormal EEPROM error was detected onServo Amp.

1. Servo AMP

A 10–0002–1A Undefined Infor. Undefined Error

B 10–0002–1B Undefined Infor. Undefined Error



E 10–0002–1E Undefined Infor. Undefined Error

F 10–0002–1F Undefined Infor. Undefined Error


2202125

TABLE/GANTRY3–28

REV 20


Table 3–24 Cradle Req Error

ErrorCode


1 12–1030–01 Cradle Out of Limit. Error Cradle position out of limit on CRADLE CMD. 1. Cradle Potentiometer; 2. IMS Potentiometer

2 12–1030–02 Cradle Unlatch. Error Cradle unlatch was detected on CRADLECMD.


3 12–1003–03 Cradle Slip. Error Cradle slip was detected in response toCRADLE CMD.

1. Patient movement during cradle movementor some obstacles on bottom of cradle orcradle roller.; 2. Cradle Encoder


5 12–1003–05 Out of ScannableRange.

Error Scannable range is zero because table posi-tion is too low.

1. Table position is too low. Raise table tohigher position.; 2. Table Height Potentiometer


7 12–1003–07 Cradle Move TimeOut.

Error Cradle acceleration/deceleration time out. Ortotal cradle movement time out in response toCRADLE CMD.



9 12–1003–09 ”STOP CT” signalcomes from Table dur-ing transport process

Error ”STOP CT” signal from the table is opening onTransport–CMD. / Reset the table fromEmergency Stop status.

STOP button of the Table is pushed.

A 12–1003–0A Gantry–Transporterposition is not initial-ized.

Error TGP received Transport–CMD before initializ-ing gantry transporter. Bring gantry transporterback to out end position.

Gantry movement operation from Operator’sconsole before gantry position initializating.

B 12–1003–0B Touch Sensor de-tected

Error Gantry Touch Sensor ON was detected ontransport–CMD. Bring transporter positionback by a few distance to recover.

Touch sensor on gantry or transporter. Any-thing touches on touch sensor during Gantrymoving operation from Operator’s console.

(continued)


2202125

TABLE/GANTRY3–29

REV 20


Table 3–24 Cradle Req Error (continued)

ErrorCode


C 12–1003–0C Transporter ServoAlarm detected



D 12–1003–0D Over Run Switch Error Over run limit switch of transporter was de-tected on transport.

Gantry was located to overrun position manu-ally. Any foreign objects on the overrun limitswitch.


F 12–1003–0F Cradle Potentio Error. Error Unexpected input from Cradle Potentiometerin response to CRADLE CMD.



2202125

TABLE/GANTRY3–30

REV 20


Table 3–25 Tilt Req Error

ErrorCode


1 12–1004–01 Out of Tilt Range. Error Out of Tilt range on TILT CMD. Tilt Potentiometer or IMS Potentiometer

2 12–1004–02 Touch Sensor On. Error Gantry Touch Sensor ON was detected duringremote tilt. Bring tilt position back by a fewangle to recover.

1. Gantry Touch Sensor; 2. FCV BD or RCVBD

3 12–1004–03 Already Home Key Onor FWD/BWD KeyOn.

Error TILT CMD was received from OC during Home/FWD/BWD is ON.

4 12–0004–04 Home Key On orFWD/BWD(COUNT-ER DIRECTION) KeyOn.

Infor. Home/FWD/BWD is pushed during remote–tilting. And Home/FWD/BWD was prioritized as theresult.

5 12–0004–05 FWD/BWD(SAME DI-RECTION) Key Off.

Infor. Home/FWD/BWD is released during remote–tilting and Home/FWD/BWD was prioritized as theresult.

6 12–1004–06 Interlock or MovementError.

Error Interlock was detected during remote–tilting. Tilt Potentiometer or IMS Potentiometer

7 12–1004–07 OCTILT Line Off. Error OCTILT line from OC was detected OFF butTILT STOP CMD from OC was not received.

1. OC could not send Tilt Stop CMD to TGP intime.; 2. OC Keyboard.

8 12–1004–08 Tilt Req TimeOut 68sec.

Error Total tilting time from start tilting to end wasover specified duration.

Tilt Valve or Tilt Pump


A 10–0004–0A Undefined Infor. Undefined Error

B 10–0004–0B Undefined Infor. Undefined Error




F 10–0004–0F Undefined Infor. Undefined Error


2202125

TABLE/GANTRY3–31

REV 20


Table 3–26 Manual Table Error

ErrorCode


1 12–1005–01 Single fault in T/Gmovement, Pleasecall service.

Error Tilt BWD/FWD movement or Table UP/DWNmovement is detected during key switch teston Gantry initialization.

1. KEY SW L or R on Gantry Cover may havethe falure and stay ON.; 2. SUB BD

2 12–1005–02 Reference position er-ror

Error Reference position detection is out of order. Obstacles on Out Limit Switch or Referenceposition Limit Switch. Adjustment of referenceposition is not done correctly . Adjustmentshould be done in slow speed.

3 12–1005–03 Table does not resetrelative position.

Error CT does not receive ”Table all zero” after re-setting the reference position of CT

Table does not send the signal of ”Table AllZero”. Jumper switch is not correct.

4 12–1005–04 Transporter ServoAlarm detected



5 12–1005–05 Over Run Switch orTouch Sensor de-tected

Error Over run limit switch of transporter or GantryTouch Sensor ON was detected during manualmovement. Bring transporter position back bya few distance to recover.

Anything touches on touch sensor duringmanual movement. Gantry was located tooverrun position manually. Any foreign objectson Overrun sensor.

6 12–1005–06 IMS POTENTIO error. Error Unexpected input from IMS Potentiometer dur-ing manual IMS movement.

IMS Potentiometer or Cabling between TGPand IMS Potentiometer.

7 12–1005–07 CRADLE POTENTIOerror.

Error Unexpected input from Cradle Potentiometerduring manual cradle movement.



2202125

TABLE/GANTRY3–32

REV 20


Table 3–27 Scan Processor Communication Error

ErrorCode



Error TGP(MP) received the message ’Not Acknowl-edged’ from OGP more than 3 times.

TGP or OGP

2 11–1010–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from OGP.


3 11–1010–03 SP is not wake up. Error TGP(MP) did not receive any reply from OGPin response to SysConfig CMD.






Table 3–28 Gantry Processor Communication Error

ErrorCode



Error TGP(MP) received the message ’Not Acknowl-edged’ from TGP(GP) more than 3 times.

TGP

2 11–1013–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from TGP(GP).

TGP

3 11–1013–03 GP is not wake up. Error TGP(MP) did not receive any reply fromTGP(GP) in response to SysConfig CMD.

Gantry Initialization did not complete correctly.;1. TGP; 2. G–Pulse1; 3. Cabling between TGPand G–Pluse1; 4. Servo Amp or Axial Motor






2202125

TABLE/GANTRY3–33

REV 20


Table 3–29 Table Processor Communication Error

ErrorCode



Error TGP(MP) received the message ’Not Acknowl-edged’ from TGP(TP) more than 3 times.

TGP

2 11–1012–02 Ack/Nack Time Out. Error TGP(MP) did not receive neither ACK norNACK from TGP(TP).

TGP

3 11–1012–03 TP is not wakeup. Error TGP(MP) did not receive any reply fromTGP(TP) in response to SysConfig CMD.

TGP






2202125

TABLE/GANTRY3–34

REV 20



ErrorCode


1 11–10F0–01 Scan Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to SCAN CMD.


2 11–10F0–02 XG Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to XG CMD.


3 11–10F0–03 Aperture Mode TimeOut.

Error TGP(MP) did not receive any reply from OGPin response to APERTURE CMD.


4 11–10F0–04 Gantry Mode TimeOut.

Error TGP(MP) did not receive any reply fromTGP(GP) in response to GNTRY CMD.

TGP

5 11–10F0–05 Cradle Mode TimeOut.

Error TGP(MP) did not receive any reply fromTGP(TP) in response to CRADLE CMD.

TGP

6 11–10F0–06 Tilt Mode Time Out. Error TGP(MP) did not receive any reply fromTGP(TP) in response to TILT CMD.

TGP

7 11–10F0–07 Test Mode Time Out. Error TGP(MP) did not receive any reply from OGPin response to TEST MODE CMD.


Table 3–31 TGP not System

ErrorCode


1 11–10F1–01 TGP Not System. Error TGP is not set as System Mode. Set TGP switch(SW1) correctly.

Table 3–32 Safety Loop Open

ErrorCode


1 11–10F2–01 SAFETY LOOPOPEN.

Error mA/kV status was not received from OGP dur-ing X–ray ON. Or X–ray OFF Status was notreceived correctly from OGP. Safety Loopwas opened by TGP as the result.

JEDI(kV control or CT–IF) or interface be-tween JEDI and TGP including OGP and SlipRing.


2202125

TABLE/GANTRY3–35

REV 20

3-4 ERRORS DETECTED BY OGP BOARD

Table 3–33 XG Processor Communication Error

ErrorCode


1 20–1014–01 XG Command Error Error XG CMD, sent from OGP, was rejected byJEDI because of unspecified mA/kV/focus/scan time request.

Mismatched firmware version betweenJEDI(kV control) and OGP.

2 20–0014–02 JEDI Wakeup timeout.

Infor. OGP did not receive any reply from JEDI inresponse to SysConfig CMD nor JEDI Capabil-ity Request CMD.


3 20–1014–03 No answer of mAkV. Error OGP did not receive reply from JEDI in re-sponse to mA/kV setup request.


4 20–0014–04 Received messagewith unknown ID.

Infor. OGP received unspecified message fromJEDI.

Mismatched firmware version betweenJEDI(kV control) and OGP.

5 20–1014–05 CAN BUS OFF Sta-tus.

Error CAN bus between JEDI and OGP becomesOFF Status because of too many communica-tion Errors.


6 20–0014–06 CAN BUS Warningstatus.

Infor. Some retries happened on CAN bus betweenJEDI and OGP and CAN bus becomesWARNING Status as the result.


7 20–0014–07 Return to normal frombus warning

Infor. CAN bus between JEDI and OGP successfullymoved to NORMAL Status from OFF Status.

–


2202125

TABLE/GANTRY3–36

REV 20

3-4 ERRORS DETECTED BY OGP BOARD (continued)

Table 3–34 Aperture Error

ErrorCode


1 20–1020–01 Aperture RequestCommand Error.

Error OGP received unspecified Aperture width fromTGP(MP).

1. DIPSW3 Setting of OGP; 2. Mismatchedversion between OGP firmware and OC soft-ware.

2 20–1020–02 Aperture Reset Error. Error OGP could not detect Aperture reset position. 1. Aperture Assy; 2. Aperture Motor Driver; 3.Cabling between OGP and Aperture PhotoSensor or between OGP and Motor Driver

3 20–1020–03 Encorder Pulse Out ofRange.

Error Encoder pulse input from Aperture is out ofspecification while setting Aperture width.

1. Aperture Assy; 2. Aperture Motor Driver; 3.Cabling between OGP and Aperture PhotoSensor or between OGP and Motor Driver

4 20–1020–04 Z–AXIS control failed Error OGP did not receive READY status from CIFfor z–axis collimator control or OGP detectedAperture is not ready.

1. CIF or interface between CIF and OGP.; 2.Motor Driver for z–axis control; 3. Photo Sen-sor for z–axis control; 4. Firmware version ofOGP and CIF.

2D 20–0020–05 Undefined Infor. – –




2202125

TABLE/GANTRY3–37

REV 20


Table 3–35 OGP Event Error

ErrorCode


1 20–1030–01 Rotor On/Off TimeOut.

Error OGP did not receive any reply from JEDI inresponse to Rotor ON/OFF request.

1. Cabling between JEDI(kV control; CT–IF)and OGP; 2. Fuse on AC/DC; 3. AC/DC,LVPS, Rotor board or Heater Board

2 20–1030–02 DAS Trigger Error. Error DAS Trigger was out of specification duringscan. Or no DAS Trigger was detected afterGANTINTREQ.

1. Rotation Speed Adjustment.; 2. Cabling forDAS Trigger including Slip Ring.

3 20–1030–03 G–Pulse2 Error Error DAS Trigger in one rotation was out of specifi-cation during scan. Or no G–Pulse2 was de-tected.

G–Pulse2

4 20–1030–04 MismatchDIPSW(SW3) andsystem config.

Error DIPSW3 on OGP is mismatched with SysCon-fig CMD which was sent from TGP.

DIPSW3 setting on OGP

5 20–1030–05 3 times NACK De-tected.

Error OGP received the message ’Not Acknowl-edged’ from TGP or CIF more than 3 times.

1. TGP or CIF; 2. OGP

6 20–1030–06 System Config Error Error OGP received unspecified SysConfig fromTGP.

Mismatched version between OGP firmwareand OC software

7 20–0030–07 DAS Wakeup TimeOut.

Infor. OGP did not receive any reply from CIF in re-sponse to SysConfig.

CIF or interface between CIF and OGP.


2202125

TABLE/GANTRY3–38

REV 20


Table 3–36 Axial Scan Error

ErrorCode


21 20–1001–21 Scan Request Com-mamd Error.

Error OGP received unspecified Axial Scan CMDfrom TGP.

Mismatched version between OGP firmwareand OC software.

22 20–1001–22 Offset Scan Time Out. Error DAS trigger for Offset Scan, generated by Ax-ial Motor Encoder and measured in referenceto G–Pulse2,. is out of specification or OffsetScan did not start or end in time on AxialScan.

1. G–Pulse2; 2. Axial Motor Encoder or inter-face between this encoder and OGP includingSlip Ring.

23 20–1001–23 X–ray On ResponseTime Out

Error HV ON was not activated by JEDI on AxialScan after EXPCMD was activated by OGP.

High possibility on JEDI in case with XG error.;In case without XG Error, JEDI(kV control orCT–IF) and interface between JEDI and OGP

24 20–1001–24 X–ray Off ResponseTime Out

Error HV ON was not inactivated by JEDI on AxialScan after EXPCMD was inactivated by OGP.


25 20–1001–25 XG Ready ResponseTime Out.

Error OGP did not receive XG Ready from JEDI onAxial Scan.


26 20–1001–26 DAS Trigger Less. Error DAS trigger of one rotation, between G–Pulse2, is under specification on Axial Scan.


27 20–1001–27 DAS Trigger Many Error DAS trigger of one rotation, between G–Pulse2, is over specification on Axial Scan.


28 20–1001–28 Aperture Error. Error Aperture width is out of specification on AxialScan.


(continued)


2202125

TABLE/GANTRY3–39

REV 20


Table 3–36 Axial Scan Error (continued)

ErrorCode


29 20–1001–29 Not Gantry Initialized. Error OGP received Axial SCAN CMD from TGPbefore DAS Trigger initialization by G–Pulse2.

G–Pulse2

2A 20–1001–2A EXPCMD On BackupTimer Error.

Error The active time of EXPCMD is over Axial Scantime.

1. Rotation Speed Adjustment; 2. G–Pulse2; 3.JEDI

2B 20–1001–2B EXPCMD Unstable Error HV ON was activated by JEDI on Axial Scanwhen EXPCMD is not activated by OGP.

1. OGP; 2. JEDI; 3. Cabling between JEDI(kVcontrol; CT–IF) and OGP

2C 20–1001–2C Scan Start Time Out. Error OGP could not detect count–up of DAS Trig-ger after received Axial SCAN CMD from TGP.

1. OGP; 2. Axial Motor Encoder or interfacebetween this encoder and OGP including SlipRing.



2F 20–1001–2F FPGA Counter Error Error DAS Trigger read out error on Axial Scan. OGP


2202125

TABLE/GANTRY3–40

REV 20


Table 3–37 Stationary Scan Error

ErrorCode



Error OGP received unspecified Stationary ScanCMD from TGP.


32 20–1001–32 Offset Scan Time Out. Error Offset Scan did not start or end in specifiedduration on Stationary Scan. This is mea-sured by internal timer of OGP.

OGP


Error HV ON was not activated by JEDI on Station-ary Scan after EXPCMD was activated byOGP.



Error HV ON was not inactivated by JEDI on Sta-tionary Scan after EXPCMD was inactivatedby OGP.



Error OGP did not receive XG Ready from JEDI onStationary Scan.


36 20–1001–36 DAS Trigger Less. Error DAS trigger, generated and measured by inter-nal timer of OGP, is under specification on Sta-tionary Scan.

OGP

37 20–1001–37 DAS Trigger Many Error DAS trigger, generated and measured by inter-nal timer of OGP is over specification on Sta-tionary Scan.

OGP

38 20–1001–38 Aperture Error. Error Aperture width is out of specification on Sta-tionary Scan.


(continued)


2202125

TABLE/GANTRY3–41

REV 20


Table 3–38 Stationary Scan Error (continued)

ErrorCode




Error The active time of EXPCMD is over StationaryScan time.

1. OGP; 2. JEDI

3B 20–1001–3B EXPCMD Unstable Error HV ON was activated by JEDI on StationaryScan when EXPCMD is not activated by OGP.


3C 20–1001–3C Scan Start Time Out. Error OGP could not detect count–up of DAS Trig-ger after received Stationary SCAN CMD fromTGP. DAS Trigger is generated by OGP inter-nally.

OGP



3F 20–1001–3F FPGA Counter Error Error DAS Trigger read out error on StationaryScan.

OGP


2202125

TABLE/GANTRY3–42

REV 20



ErrorCode



Error OGP received unspecified Helical Scan CMDfrom TGP.


12 20–1001–12 Offset Scan Time Out. Error Offset Scan did not start or end in specifiedduration on Helical Scan.

OGP


Error HV ON was not activated by JEDI on HelicalScan after EXPCMD was activated by OGP.



Error HV ON was not inactivated by JEDI on HelicalScan after EXPCMD was inactivated by OGP.



Error OGP did not receive XG Ready from JEDI onHelical Scan.


16 20–1001–16 DAS Trigger Less. Error DAS trigger of one rotation, between G–Pulse2, is under specification on Helical Scan.


17 20–1001–17 DAS Trigger Many Error DAS trigger of one rotation, between G–Pulse2, is over specification on Helical Scan.


18 20–1001–18 Aperture Error. Error Aperture width is out of specification on HelicalScan.


19 20–1001–19 Not Gantry Initialized. Error OGP received Helical SCAN CMD from TGPbefore DAS Trigger initialization by G–Pulse2.

G–Pulse2

(continued)


2202125

TABLE/GANTRY3–43

REV 20



ErrorCode



Error The active time of EXPCMD is over HelicalScan time.


1B 20–1001–1B EXPCMD Unstable Error HV ON was activated by JEDI on Helical Scanwhen EXPCMD is not activated by OGP.


1C 20–1001–1C Scan Start Time Out. Error OGP did not receive SCINTREQ from TGP inspecified duration. OGP could not start scan-ning as the result.

TGP or interface between OGP and TGP in-cluding Slip Ring.



1F 20–1001–1F FPGA Counter Error Error DAS Trigger read out error on Helical Scan. OGP


2202125

TABLE/GANTRY3–44

REV 20



ErrorCode



Error OGP received unspecified command fromTGP on Scout Scan.


42 20–1001–42 Offset Scan Time Out. Error Offset Scan did not start or end in specifiedduration on Scout Scan, This is measured byinternal timer of OGP.

OGP

43 20–1001–43 X–ray On ResponseTime Out.

Error HV ON was not activated by JEDI on ScoutScan after EXPCMD was activated by OGP.


44 20–1001–44 X–ray Off ResponseTime Out.

Error HV ON was not inactivated by JEDI on ScoutScan after EXPCMD was inactivated by OGP.



Error OGP did not receive XG Ready from JEDI onScout Scan.


46 20–1001–46 DAS Trigger Less. Error DAS trigger, generated by cradle encoder andmeasured by internal timer of OGP, is underspecification on Scout Scan.

1. Cradle Encoder; 2. Cradle Speed Adjust-ment; 3. Interface between OGP and CradleEncoder including Slip Ring and TGP.

47 20–1001–47 DAS Trigger Many. Error DAS trigger, generated by cradle encoder andmeasured by internal timer of OGP is overspecification on Scout Scan.

1. Cradle Encoder; 2. Cradle Speed Adjust-ment; 3. Interface between OGP and CradleEncoder including Slip Ring and TGP.

48 20–1001–48 Aperture Error. Error Aperture width is out of specification on ScoutScan.


(continued)


2202125

TABLE/GANTRY3–45

REV 20



ErrorCode


49 20–1001–49 Not gantry Initialized Error OGP received Scout SCAN CMD from TGPbefore DAS Trigger initialization.

G–Pulse2

4A 20–1001–4A EXPCMD On BackupTimer Error

Error The active time of EXPCMD is over ScoutScan time.

1. Cradle Speed Adjustment; 2. JEDI

4B 20–1001–4B EXPCMD Unstable Error HV ON was activated by JEDI on Scout Scanwhen EXPCMD is not activated by OGP.


4C 20–1001–4C Scan start Time Out. Error OGP did not detect count–up of DAS Triggerafter received Scout SCAN CMD from TGP.DAS Trigger is generated by Cradle Encoder.

1. Cradle Encoder; 2. Interface between OGPand Cradle Encoder including Slip Ring andTGP.


2D 20–0001–4E Undefined Infor. – –

2D 20–0001–4F Undefined Infor. – –


2202125

TABLE/GANTRY3–46

REV 20



ErrorCode



Error OGP received unspecified command fromTGP on Fluoro Scan.


52 20–1001–52 Offset Scan Time Out. Error Offset Scan did not start or end in specifiedduration on Fluoro Scan.

OGP

53 20–1001–53 X–ray On ResponseTime Out.

Error HV ON was not activated by JEDI on FluoroScan after EXPCMD was activated by OGP.


54 20–1001–54 X–ray Off ResponseTime Out.

Error HV ON was not inactivated by JEDI on FluoroScan after EXPCMD was inactivated by OGP.



Error OGP did not receive XG Ready from JEDI onFluoro Scan.


56 20–1001–56 DAS Trigger Less. Error DAS trigger of one rotation, between G–Pulse2, is under specification on Fluoro Scan.


57 20–1001–57 DAS Trigger Many. Error DAS trigger of one rotation, between G–Pulse2, is over specification on Fluoro Scan.


58 20–1001–58 Aperture Error. Error Aperture width is out of specification on FluoroScan.


(continued)


2202125

TABLE/GANTRY3–47

REV 20


Table 3–41 Fluoro Scan Error (continued)

ErrorCode


59 20–1001–59 NOT Gantry Initial-ized.

Error OGP received Fluoro SCAN CMD from TGPbefore DAS Trigger initialization by G–Pulse2.

G–Pulse2


Error The active time of EXPCMD is over FluoroScan time.


5B 20–1001–5B EXPCMD Unstable Error HV ON was activated by JEDI on Fluoro Scanwhen EXPCMD is not activated by OGP.


5C 20–1001–5C Scan Start Time Out. Error OGP could not detect count–up of DAS Trig-ger after received Fluoro SCAN CMD fromTGP.

1. OGP; 2. Axial Motor Encoder or interfacebetween this encoder and OGP including SlipRing.

5D 20–1001–5D HV ON commandtime out.

Error X–ray Foot SW was inactivated on FluoroScan before receiving X–ray Foot SW OFFStatus from TGP.

1. TGP or interface between TGP and OGPincluding Slip Ring

5E 20–1001–5E Fluoro Scan BackupTimer _-_Time Out.

Error OGP detected HV ON time out during TapMode or Continuous Mode.

High possibility on JEDI or Rotation Speed Ad-justment in case with XG error.; In case with-out XG Error, JEDI(kV control or CT–IF) andinterface between JEDI and OGP.

5F 20–1001–5F FPGA Counter Error Error DAS Trigger read out error on Fluoro Scan. OGP


2202125

TABLE/GANTRY3–48

REV 20

3-5 ERRORS DETECTED BY DAS

Table 3–42 DAS Error

ErrorCode


1 30–1010–01 Zero Detect. Error Zero DAS data was detected. 1. CAM; 2. CIF; 2. DDP

2 30–0010–02 Over Range Infor. DAS data Over Range was detected. 1. Reduce scan technic.; 2. CAM, CIF or DDP





7 30–1010–07 Communication error Error Unexpected length or checksum of commandwas detected during communication betweenCIF and OGP.

1. Cable connection between OGP and DAS;2. OGP or CIF

Table 3–43 Z CH CAL Error (Z–axis Collimator)

ErrorCode


0101 30–0101–01 – Infor. CIF received unspecified Qcal Ratio Data fromOC on SysConfig.

Mismatched version between CIF and OCsoftware.

0102 30–0101–02 – Infor. CIF could not receive all Qcal Ratio Data fromOC on SysConfig.

Interface between CIF and OC including SlipRing.


2202125

TABLE/GANTRY3–49

REV 20

3-5 ERRORS DETECTED BY DAS (continued)

Table 3–44 Beam Tracking Para Error (Z–axis Collimator)

ErrorCode


0201 30–1102–01 – Error CIF received unspecified Aperture width fromOC on XG CMD.


0202 30–1102–02 – Error CIF could not find Qcal Ratio Data for currentAperture on XG CMD.

Failed to receive all Qcal Ratio Data from OCduring SysConfig.; Or mismatched version be-tween CIF and OC software.

0301 30–1103–01 – Error CIF received unspecified Scan Time from OCon Scan CMD.


Table 3–45 Home Positioning Error (Z–axis Collimator)

ErrorCode


1101 30–1111–01 – Error BWD and FWD Limit–Photo–Sensors wereinterrupted at the same time during HomePositioning.

1. BWD or FWD Limit–Photo–Sensor(H); 2.Cabling between Limit–Photo–Sensor and CIF.

1102 30–1111–02 – Error BWD Limit–Photo–Sensor was unexpectedlyinterrupted during Home Positioning.

1. BWD and FWD Limit–Photo–Sensor is con-nected conversely with CIF.; 2. Z–Axis Motormovement is reversed.

1103 30–1111–03 – Error On Home Positioning, FWD Limit–Photo–Sen-sor remains interrupted when CIF drives Z–Axis Motor to BWD direction.

1. Z–Axis Motor Driver; 2. Z–Axis Motor; 3.Cabling between Z–Axis Motor and CIF; 4.BWD and FWD Limit–Photo–Sensor is con-nected conversely with CIF.

(continued)


2202125

TABLE/GANTRY3–50

REV 20


Table 3–45 Home Positioning Error (Z–axis Collimator) (continued)

ErrorCode


1104 30–1111–04 – Error On Home Positioning, CIF cannot detect FWDLimit–Photo–Sensor interruption even after itdrives Z–Axis Motor to FWD limit.

1. Z–Axis Motor Driver; 2. Z–Axis Motor; 3.Cabling between Z–Axis Motor and CIF; 4.BWD and FWD Limit–Photo–Sensor is con-nected conversely with CIF.

1105 30–1111–05 – Error On Home Positioning, CIF cannot detect BWDLimit–Photo–Sensor interruption when it drivesZ–Axis Motor from FWD limit to BWD limit.

1. Z–Axis Motor Driver; 2. Z–Axis Motor; 3.BWD Limit–Photo–Sensor; 4. Ball Screw

1106 30–1111–06 – Error The number of pulses for Z–Axis Motor is overspecification when moving from FWD limit toBWD limit on Home Positioning.

1. Position of BWD or FWD Limit–Photo–Sen-sor; 2. Jumper Setting of Z–Axis Motor Driver;3. Ball Screw

1107 30–1111–07 – Error The number of pulses for Z–Axis Motor is un-der specification when moving from FWD limitto BWD limit on Home Positioning.

1. Position of BWD or FWD Limit–Photo–Sen-sor; 2. Jumper Setting of Z–Axis Motor Driver

1108 30–1111–08 – Error During Home Positioning, FWD Limit–Photo–Sensor was interrupted when moving fromBWD limit to Home Position.



2202125

TABLE/GANTRY3–51

REV 20


Table 3–46 Preset Positioning Error (Z–axis Collimator)

ErrorCode


1201 30–1112–01 – Error FWD Limit–Photo–Sensor was interrupted dur-ing Preset Positioning.

In case with error on Home Positioning, FWDLimit–Photo–Sensor or Cabling between Sen-sor and CIF.; In case without error on HomePositioning, Preset CMD from OC may beincorrect.

1202 30–1112–02 – Error BWD Limit–Photo–Sensor was interrupted dur-ing Preset Positioning.

In case with error on Home Positioning, BWDLimit–Photo–Sensor or Cabling between Sen-sor and CIF.; In case without error on HomePositioning, Preset CMD from OC may beincorrect.

Table 3–47 Beam Tracking Out of Limit (Z–axis Collimator)

ErrorCode


2101 30–0121–01 – Infor. FWD Limit–Photo–Sensor was interrupted dur-ing Beam Tracking.

In case with error on Home Positioning, FWDLimit–Photo–Sensor or Cabling between Sen-sor and CIF.; In case without error on HomePositioning, Qcal CH data from DDP may notbe normal by Qcal Obs or z–axis miss–align-ment of Tube or Detector..

2102 30–0121–02 – Infor. BWD Limit–Photo–Sensor was interrupted dur-ing Beam Tracking.

In case with error on Home Positioning, BWDLimit–Photo–Sensor or Cabling between Sen-sor and CIF.; In case without error on HomePositioning, Qcal CH data from DDP may notbe normal by Qcal Obs or z–axis miss–align-ment of Tube or Detector..


2202125

TABLE/GANTRY3–52

REV 20


Table 3–48 Offset View Error (Z–axis Collimator)

ErrorCode


2201 30–1122–01 – Error The number of Offset View is out of specifica-tion.

In case with raw data correction error detectedby OC, Cabling for DAS Trigger including SlipRing.; In case without this error, CIF may befailed.

Table 3–49 FIFO Overview Error (Z–axis Collimator)

ErrorCode


2301 30–1123–01 – Error CIF detected DDP FIFO Overflow during QcalCH data collection(Offset view).

–

2302 30–0123–02 – Infor. CIF detected DDP FIFO Overflow during QcalCH data collection(Active view).

–

Table 3–50 Beam Tracking Calc Error (Z–axis Collimator)

ErrorCode


3101 30–1131–01 – Error Unexpected result of Beam Tracking calcula-tion.

–

3102 30–1131–02 – Error Unexpected result of Beam Tracking calcula-tion.

–


2202125

TABLE/GANTRY3–53

REV 20


Table 3–51 Internal Error (Z–axis Collimator)

ErrorCode


3201 30–1132–01 – Error CIF Internal Error. –

3202 30–1132–02 – Error CIF Internal Error. –

Table 3–52 Z CH Count (Z–axis Collimator)

ErrorCode


4101 30–0141–01 – Infor. Beam Tracking was paused because CIF de-tected Qcal CH Data is under specification.

Qcal CH Obstruction or tube spits.

Table 3–53 Beam Tracking Hold/Resume (Z–axis Collimator)

ErrorCode


4201 30–0142–01 – Infor. Beam Tracking was paused because CIF de-tected Qcal CH obstruction.

Qcal CH Obstruction

4202 30–0142–02 – Infor. Beam Tracking was resumed because QcalCH returned to normal from obstruction.

–


2202125

TABLE/GANTRY3–54

blank


2202125

DAS/DETECTORi

REV 8

DAS / DETECTOR

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 – CHANNEL – RING RADIUS TABLE 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 DETECTOR/DAS CHANNEL – RING RADIUS CROSS REFERENCE 1–1. . . . . . . . . . .

SECTION 2 – LED DESCRIPTION 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

DAS/DETECTORii

blank


2202125

DAS/DETECTOR1–1

REV 28

SECTION 1 – CHANNEL – RING RADIUS TABLE

1-1 DETECTOR/DAS CHANNEL – RING RADIUS CROSS REFERENCE

Table 1–2 through 1–17 are Detector/DAS Channel – Ring Radius Cross Reference.

In these tables:

� CH#: Detector/DAS Channel No.

� FC#: Flex Cable No.

� CB#: CAM Board No.

– Single: for the dectecor of NP, NP+, NP++ systems

– Twin – A: for the A side detector of Twin systems

– Twin – B: for the B side detector of Twin systems

� PN#: Pin No. of the flex cable connector: Actually in Table 1–2 through 1–17, Channel Nos. are shown.See Illustration 1–1 or 1–2.

� R (mm): Radius of image artifact in mm


2202125

DAS/DETECTOR1–2

REV 28

1-1 DETECTOR/DAS CHANNEL – RING RADIUS CROSS REFERENCE (Continued)

Illustration 1–1 DAS/Detector Connector Pin Assignment (NP, NP+, and NP++)

DetectorËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËË

ËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËË Flex

Cable

Flex Cables

24 Pins

d c b a

123456

a b c d

1 CH 8 CH 9 CH10

2 CH 6 CH11 CH12

3 CH 4 CH13 CH14

4 CH 2 CH15 CH16

5

6

FG

FG

FG

FG

SG

SG

SG

SG

CH 7

CH 5

CH 3

CH 1

Cable #1

Cable #51

CAM Boards #1~#9

CAM Boards #10~#18

CAM Boards #19~#27


2202125

DAS/DETECTOR1–3

REV 28


Illustration 1–2 DAS/Detector Connector Pin Assignment (Twin)

Detector

ËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËË

ËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËËË

Flex Cables

Cable #1

Cable #51

CAM Boards #1~#18

CAM Boards #19~#36

CAM Boards #37~#54

D C B A

A B C D

1 2SG 2SG 2SG

2 2SG 2SG 2SG

3 B–1ch A–16ch B–16ch


5

6

A–3ch

A–4ch

B–3ch

B–4ch

A–14ch

A–13ch

B–14ch

B–13ch

2SG

2SG

A–1ch

A–2ch

123456





11

12

FG

FG

FG

FG

FG

FG

FG

FG

A–5ch

A–6ch

A–7ch

A–8ch

789

101112

FlexCable

48 Pins


2202125

DAS/DETECTOR1–4

REV 28


Table 1–1 Channel Number Difference between System Channnels and GSA Channel Report(Twin)

IMPORTANT NOTE:Focus attention on QCAL 1–3, REF 1–16, and REF 17–32 of System channel. They are re-ported as different readout when using GSA.

Detector Module CAM Board # System Channels GSA Channel Re-portA Slice B Slice port

1 1 2 QCAL 1–3 827 – 829

1 2 REF 1–16 794 – 809

3 4 1–3 1–3

2 3 4 4–19 4–19

3 5 6 20–35 20–35

4 5 6 36–51 36–51

5 7 8 52–67 52–67

6 7 8 68–83 68–83

7 9 10 84–99 84–99

8 9 10 100–115 100–115

9 11 12 116–131 116–131

10 11 12 132–147 132–147

11 13 14 148–163 148–163

12 13 14 164–179 164–179

13 15 16 180–195 180–195

14 15 16 196–211 196–211

15 17 18 212–227 212–227

16 17 18 228–243 288–243

17 19 20 244–259 244–259

18 19 20 260–275 260–275

19 21 22 276–291 276–291

20 21 22 292–307 292–307

21 23 24 308–323 308–323

22 23 24 324–339 324–339

23 25 26 340–355 340–355

24 25 26 356–371 356–371

25 27 28 372–387 372–387

26 27 28 388–403 388–403

Note: The center of the DAS is CAM boards #27 and #28.


2202125

DAS/DETECTOR1–5

REV 28

Table 1–1 Channel Number Difference between System Channnels and GSA Channel Report(Twin) (Continued)

Detector Module CAM Board # System Channels GSA Channel Re-portA Slice B Slice port

27 29 30 404–419 404–419

28 29 30 420–435 420–435

29 31 32 436–451 436–451

30 31 32 452–467 452–467

31 33 34 468–483 468–483

32 33 34 484–499 484–499

33 35 36 500–515 500–515

34 35 36 516–531 516–531

35 37 38 532–547 532–547

36 37 38 548–563 548–563

37 39 40 564–579 564–579

38 39 40 580–595 580–595

39 41 42 596–611 596–611

40 41 42 612–627 612–627

41 43 44 628–643 628–643

42 43 44 644–659 644–659

43 45 46 660–675 660–675

44 45 46 676–691 676–691

45 47 48 692–707 692–707

46 47 48 708–723 708–723

47 49 50 724–739 724–739

48 49 50 740–755 740–755

49 51 52 756–771 756–771

50 51 52 772–787 772–787

51 53 54 788–793 788–793

53 54 REF 17–32 810–825


2202125

DAS/DETECTOR1–6

REV 28

Table 1–2 Channel – Ring Radius (#1 ~#50)

CH# FC# CB# PN# R (mm)

Single Twin – A Twin – B1 1 2 3 4 14 249.7

2 1 2 3 4 15 249.1

3 1 2 3 4 16 248.5

4 2 2 3 4 1 248.0

5 2 2 3 4 2 247.4

6 2 2 3 4 3 246.8

7 2 2 3 4 4 246.2

8 2 2 3 4 5 245.6

9 2 2 3 4 6 245.0

10 2 2 3 4 7 244.5

11 2 2 3 4 8 243.9

12 2 2 3 4 9 243.3

13 2 2 3 4 10 242.7

14 2 2 3 4 11 242.1

15 2 2 3 4 12 241.5

16 2 2 3 4 13 240.9

17 2 2 3 4 14 240.4

18 2 2 3 4 15 239.8

19 2 2 3 4 16 239.2

20 3 3 5 6 1 238.6

21 3 3 5 6 2 238.0

22 3 3 5 6 3 237.4

23 3 3 5 6 4 236.8

24 3 3 5 6 5 236.2

25 3 3 5 6 6 235.6

26 3 3 5 6 7 235.1

27 3 3 5 6 8 234.5

28 3 3 5 6 9 233.9

29 3 3 5 6 10 233.3

30 3 3 5 6 11 232.7

31 3 3 5 6 12 232.1

32 3 3 5 6 13 231.5

33 3 3 5 6 14 230.9

34 3 3 5 6 15 230.3

35 3 3 5 6 16 229.7

36 4 3 5 6 1 229.1

37 4 3 5 6 2 228.5

38 4 3 5 6 3 227.9

39 4 3 5 6 4 227.3

40 4 3 5 6 5 226.8

41 4 3 5 6 6 226.2

42 4 3 5 6 7 225.6

43 4 3 5 6 8 225.0

44 4 3 5 6 9 224.4

45 4 3 5 6 10 223.8

46 4 3 5 6 11 223.2

47 4 3 5 6 12 222.6

48 4 3 5 6 13 222.0

49 4 3 5 6 14 221.4

50 4 3 5 6 15 220.8


2202125

DAS/DETECTOR1–7

REV 28




52 5 4 7 8 1 219.6

53 5 4 7 8 2 219.0

54 5 4 7 8 3 218.4

55 5 4 7 8 4 217.8

56 5 4 7 8 5 217.2

57 5 4 7 8 6 216.6

58 5 4 7 8 7 216.0

59 5 4 7 8 8 215.4

60 5 4 7 8 9 214.8

61 5 4 7 8 10 214.2

62 5 4 7 8 11 213.6

63 5 4 7 8 12 213.0

64 5 4 7 8 13 212.4

65 5 4 7 8 14 211.8

66 5 4 7 8 15 211.2

67 5 4 7 8 16 210.6

68 6 4 7 8 1 210.0

69 6 4 7 8 2 209.3

70 6 4 7 8 3 208.7

71 6 4 7 8 4 208.1

72 6 4 7 8 5 207.5

73 6 4 7 8 6 206.9

74 6 4 7 8 7 206.3

75 6 4 7 8 8 205.7

76 6 4 7 8 9 205.1

77 6 4 7 8 10 204.5

78 6 4 7 8 11 203.9

79 6 4 7 8 12 203.3

80 6 4 7 8 13 202.7

81 6 4 7 8 14 202.1

82 6 4 7 8 15 201.5

83 6 4 7 8 16 200.8

84 7 5 9 10 1 200.2

85 7 5 9 10 2 199.6

86 7 5 9 10 3 199.0

87 7 5 9 10 4 198.4

88 7 5 9 10 5 197.8

89 7 5 9 10 6 197.2

90 7 5 9 10 7 196.6

91 7 5 9 10 8 196.0

92 7 5 9 10 9 195.4

93 7 5 9 10 10 194.7

94 7 5 9 10 11 194.1

95 7 5 9 10 12 193.5

96 7 5 9 10 13 192.9

97 7 5 9 10 14 192.3

98 7 5 9 10 15 191.7

99 7 5 9 10 16 191.1

100 8 5 9 10 1 190.5


2202125

DAS/DETECTOR1–8

REV 28




102 8 5 9 10 3 189.2

103 8 5 9 10 4 188.6

104 8 5 9 10 5 188.0

105 8 5 9 10 6 187.4

106 8 5 9 10 7 186.8

107 8 5 9 10 8 186.2

108 8 5 9 10 9 185.5

109 8 5 9 10 10 184.9

110 8 5 9 10 11 184.3

111 8 5 9 10 12 183.7

112 8 5 9 10 13 183.1

113 8 5 9 10 14 182.5

114 8 5 9 10 15 181.8

115 8 5 9 10 16 181.2

116 9 6 11 12 1 180.6

117 9 6 11 12 2 180.0

118 9 6 11 12 3 179.4

119 9 6 11 12 4 178.7

120 9 6 11 12 5 178.1

121 9 6 11 12 6 177.5

122 9 6 11 12 7 176.9

123 9 6 11 12 8 176.3

124 9 6 11 12 9 175.6

125 9 6 11 12 10 175.0

126 9 6 11 12 11 174.4

127 9 6 11 12 12 173.8

128 9 6 11 12 13 173.2

129 9 6 11 12 14 172.5

130 9 6 11 12 15 171.9

131 9 6 11 12 16 171.3

132 10 6 11 12 1 170.7

133 10 6 11 12 2 170.1

134 10 6 11 12 3 169.4

135 10 6 11 12 4 168.8

136 10 6 11 12 5 168.2

137 10 6 11 12 6 167.6

138 10 6 11 12 7 166.9

139 10 6 11 12 8 166.3

140 10 6 11 12 9 165.7

141 10 6 11 12 10 165.1

142 10 6 11 12 11 164.4

143 10 6 11 12 12 163.8

144 10 6 11 12 13 163.2

145 10 6 11 12 14 162.6

146 10 6 11 12 15 161.9

147 10 6 11 12 16 161.3

148 11 7 13 14 1 160.7

149 11 7 13 14 2 160.1

150 11 7 13 14 3 159.4


2202125

DAS/DETECTOR1–9

REV 28




152 11 7 13 14 5 158.2

153 11 7 13 14 6 157.5

154 11 7 13 14 7 156.9

155 11 7 13 14 8 156.3

156 11 7 13 14 9 155.7

157 11 7 13 14 10 155.0

158 11 7 13 14 11 154.4

159 11 7 13 14 12 153.8

160 11 7 13 14 13 153.2

161 11 7 13 14 14 152.5

162 11 7 13 14 15 151.9

163 11 7 13 14 16 151.3

164 12 7 13 14 1 150.6

165 12 7 13 14 2 150.0

166 12 7 13 14 3 149.4

167 12 7 13 14 4 148.7

168 12 7 13 14 5 148.1

169 12 7 13 14 6 147.5

170 12 7 13 14 7 146.9

171 12 7 13 14 8 146.2

172 12 7 13 14 9 145.6

173 12 7 13 14 10 145.0

174 12 7 13 14 11 144.3

175 12 7 13 14 12 143.7

176 12 7 13 14 13 143.1

177 12 7 13 14 14 142.4

178 12 7 13 14 15 141.8

179 12 7 13 14 16 141.2

180 13 8 15 16 1 140.5

181 13 8 15 16 2 139.9

182 13 8 15 16 3 139.3

183 13 8 15 16 4 138.6

184 13 8 15 16 5 138.0

185 13 8 15 16 6 137.4

186 13 8 15 16 7 136.7

187 13 8 15 16 8 136.1

188 13 8 15 16 9 135.5

189 13 8 15 16 10 134.8

190 13 8 15 16 11 134.2

191 13 8 15 16 12 133.5

192 13 8 15 16 13 132.9

193 13 8 15 16 14 132.3

194 13 8 15 16 15 131.6

195 13 8 15 16 16 131.0

196 14 8 15 16 1 130.4

197 14 8 15 16 2 129.7

198 14 8 15 16 3 129.1

199 14 8 15 16 4 128.5

200 14 8 15 16 5 127.8


2202125

DAS/DETECTOR1–10

REV 28




202 14 8 15 16 7 126.5

203 14 8 15 16 8 125.9

204 14 8 15 16 9 125.3

205 14 8 15 16 10 124.6

206 14 8 15 16 11 124.0

207 14 8 15 16 12 123.4

208 14 8 15 16 13 122.7

209 14 8 15 16 14 122.1

210 14 8 15 16 15 121.4

211 14 8 15 16 16 120.8

212 15 9 17 18 1 120.2

213 15 9 17 18 2 119.5

214 15 9 17 18 3 118.9

215 15 9 17 18 4 118.2

216 15 9 17 18 5 117.6

217 15 9 17 18 6 117.0

218 15 9 17 18 7 116.3

219 15 9 17 18 8 115.7

220 15 9 17 18 9 115.0

221 15 9 17 18 10 114.4

222 15 9 17 18 11 113.8

223 15 9 17 18 12 113.1

224 15 9 17 18 13 112.5

225 15 9 17 18 14 111.8

226 15 9 17 18 15 111.2

227 15 9 17 18 16 110.5

228 16 9 17 18 1 109.9

229 16 9 17 18 2 109.3

230 16 9 17 18 3 108.6

231 16 9 17 18 4 108.0

232 16 9 17 18 5 107.3

233 16 9 17 18 6 106.7

234 16 9 17 18 7 106.0

235 16 9 17 18 8 105.4

236 16 9 17 18 9 104.8

237 16 9 17 18 10 104.1

238 16 9 17 18 11 103.5

239 16 9 17 18 12 102.8

240 16 9 17 18 13 102.2

241 16 9 17 18 14 101.5

242 16 9 17 18 15 100.9

243 16 9 17 18 16 100.3

244 17 10 19 20 1 99.6

245 17 10 19 20 2 99.0

246 17 10 19 20 3 98.3

247 17 10 19 20 4 97.7

248 17 10 19 20 5 97.0

249 17 10 19 20 6 96.4

250 17 10 19 20 7 95.7


2202125

DAS/DETECTOR1–11

REV 28




252 17 10 19 20 9 94.4

253 17 10 19 20 10 93.8

254 17 10 19 20 11 93.2

255 17 10 19 20 12 92.5

256 17 10 19 20 13 91.9

257 17 10 19 20 14 91.2

258 17 10 19 20 15 90.6

259 17 10 19 20 16 89.9

260 18 10 19 20 1 89.3

261 18 10 19 20 2 88.6

262 18 10 19 20 3 88.0

263 18 10 19 20 4 87.3

264 18 10 19 20 5 86.7

265 18 10 19 20 6 86.0

266 18 10 19 20 7 85.4

267 18 10 19 20 8 84.7

268 18 10 19 20 9 84.1

269 18 10 19 20 10 83.5

270 18 10 19 20 11 82.8

271 18 10 19 20 12 82.2

272 18 10 19 20 13 81.5

273 18 10 19 20 14 80.9

274 18 10 19 20 15 80.2

275 18 10 19 20 16 79.6

276 19 11 21 22 1 78.9

277 19 11 21 22 2 78.3

278 19 11 21 22 3 77.6

279 19 11 21 22 4 77.0

280 19 11 21 22 5 76.3

281 19 11 21 22 6 75.7

282 19 11 21 22 7 75.0

283 19 11 21 22 8 74.4

284 19 11 21 22 9 73.7

285 19 11 21 22 10 73.1

286 19 11 21 22 11 72.4

287 19 11 21 22 12 71.8

288 19 11 21 22 13 71.1

289 19 11 21 22 14 70.5

290 19 11 21 22 15 69.8

291 19 11 21 22 16 69.2

292 20 11 21 22 1 68.5

293 20 11 21 22 2 67.9

294 20 11 21 22 3 67.2

295 20 11 21 22 4 66.6

296 20 11 21 22 5 65.9

297 20 11 21 22 6 65.3

298 20 11 21 22 7 64.6

299 20 11 21 22 8 64.0

300 20 11 21 22 9 63.3


2202125

DAS/DETECTOR1–12

REV 28




302 20 11 21 22 11 62.0

303 20 11 21 22 12 61.4

304 20 11 21 22 13 60.7

305 20 11 21 22 14 60.1

306 20 11 21 22 15 59.4

307 20 11 21 22 16 58.7

308 21 12 23 24 1 58.1

309 21 12 23 24 2 57.4

310 21 12 23 24 3 56.8

311 21 12 23 24 4 56.1

312 21 12 23 24 5 55.5

313 21 12 23 24 6 54.8

314 21 12 23 24 7 54.2

315 21 12 23 24 8 53.5

316 21 12 23 24 9 52.9

317 21 12 23 24 10 52.2

318 21 12 23 24 11 51.6

319 21 12 23 24 12 50.9

320 21 12 23 24 13 50.3

321 21 12 23 24 14 49.6

322 21 12 23 24 15 49.0

323 21 12 23 24 16 48.3

324 22 12 23 24 1 47.7

325 22 12 23 24 2 47.0

326 22 12 23 24 3 46.3

327 22 12 23 24 4 45.7

328 22 12 23 24 5 45.0

329 22 12 23 24 6 44.4

330 22 12 23 24 7 43.7

331 22 12 23 24 8 43.1

332 22 12 23 24 9 42.4

333 22 12 23 24 10 41.8

334 22 12 23 24 11 41.1

335 22 12 23 24 12 40.5

336 22 12 23 24 13 39.8

337 22 12 23 24 14 39.2

338 22 12 23 24 15 38.5

339 22 12 23 24 16 37.8

340 23 13 25 26 1 37.2

341 23 13 25 26 2 36.5

342 23 13 25 26 3 35.9

343 23 13 25 26 4 35.2

344 23 13 25 26 5 34.6

345 23 13 25 26 6 33.9

346 23 13 25 26 7 33.3

347 23 13 25 26 8 32.6

348 23 13 25 26 9 32.0

349 23 13 25 26 10 31.3

350 23 13 25 26 11 30.6


2202125

DAS/DETECTOR1–13

REV 28




352 23 13 25 26 13 29.3

353 23 13 25 26 14 28.7

354 23 13 25 26 15 28.0

355 23 13 25 26 16 27.4

356 24 13 25 26 1 26.7

357 24 13 25 26 2 26.1

358 24 13 25 26 3 25.4

359 24 13 25 26 4 24.8

360 24 13 25 26 5 24.1

361 24 13 25 26 6 23.4

362 24 13 25 26 7 22.8

363 24 13 25 26 8 22.1

364 24 13 25 26 9 21.5

365 24 13 25 26 10 20.8

366 24 13 25 26 11 20.2

367 24 13 25 26 12 19.5

368 24 13 25 26 13 18.9

369 24 13 25 26 14 18.2

370 24 13 25 26 15 17.5

371 24 13 25 26 16 16.9

372 25 14 27 28 1 16.2

373 25 14 27 28 2 15.6

374 25 14 27 28 3 14.9

375 25 14 27 28 4 14.3

376 25 14 27 28 5 13.6

377 25 14 27 28 6 13.0

378 25 14 27 28 7 12.3

379 25 14 27 28 8 11.6

380 25 14 27 28 9 11.0

381 25 14 27 28 10 10.3

382 25 14 27 28 11 9.7

383 25 14 27 28 12 9.0

384 25 14 27 28 13 8.4

385 25 14 27 28 14 7.7

386 25 14 27 28 15 7.1

387 25 14 27 28 16 6.4

388 26 14 27 28 1 5.7

389 26 14 27 28 2 5.1

390 26 14 27 28 3 4.4

391 26 14 27 28 4 3.8

392 26 14 27 28 5 3.1

393 26 14 27 28 6 2.5

394 26 14 27 28 7 1.8

395 26 14 27 28 8 1.1

396 26 14 27 28 9 0.5

397 26 14 27 28 10 0.2

398 26 14 27 28 11 0.8

399 26 14 27 28 12 1.5

400 26 14 27 28 13 2.1


2202125

DAS/DETECTOR1–14

REV 28




402 26 14 27 28 15 3.4

403 26 14 27 28 16 4.1

404 27 15 29 30 1 4.8

405 27 15 29 30 2 5.4

406 27 15 29 30 3 6.1

407 27 15 29 30 4 6.7

408 27 15 29 30 5 7.4

409 27 15 29 30 6 8.0

410 27 15 29 30 7 8.7

411 27 15 29 30 8 9.3

412 27 15 29 30 9 10.0

413 27 15 29 30 10 10.7

414 27 15 29 30 11 11.3

415 27 15 29 30 12 12.0

416 27 15 29 30 13 12.6

417 27 15 29 30 14 13.3

418 27 15 29 30 15 13.9

419 27 15 29 30 16 14.6

420 28 15 29 30 1 15.2

421 28 15 29 30 2 15.9

422 28 15 29 30 3 16.6

423 28 15 29 30 4 17.2

424 28 15 29 30 5 17.9

425 28 15 29 30 6 18.5

426 28 15 29 30 7 19.2

427 28 15 29 30 8 19.8

428 28 15 29 30 9 20.5

429 28 15 29 30 10 21.1

430 28 15 29 30 11 21.8

431 28 15 29 30 12 22.5

432 28 15 29 30 13 23.1

433 28 15 29 30 14 23.8

434 28 15 29 30 15 24.4

435 28 15 29 30 16 25.1

436 29 16 31 32 1 25.7

437 29 16 31 32 2 26.4

438 29 16 31 32 3 27.0

439 29 16 31 32 4 27.7

440 29 16 31 32 5 28.4

441 29 16 31 32 6 29.0

442 29 16 31 32 7 29.7

443 29 16 31 32 8 30.3

444 29 16 31 32 9 31.0

445 29 16 31 32 10 31.6

446 29 16 31 32 11 32.3

447 29 16 31 32 12 32.9

448 29 16 31 32 13 33.6

449 29 16 31 32 14 34.2

450 29 16 31 32 15 34.9


2202125

DAS/DETECTOR1–15

REV 28




452 30 16 31 32 1 36.2

453 30 16 31 32 2 36.9

454 30 16 31 32 3 37.5

455 30 16 31 32 4 38.2

456 30 16 31 32 5 38.8

457 30 16 31 32 6 39.5

458 30 16 31 32 7 40.1

459 30 16 31 32 8 40.8

460 30 16 31 32 9 41.4

461 30 16 31 32 10 42.1

462 30 16 31 32 11 42.8

463 30 16 31 32 12 43.4

464 30 16 31 32 13 44.1

465 30 16 31 32 14 44.7

466 30 16 31 32 15 45.4

467 30 16 31 32 16 46.0

468 31 17 33 34 1 46.7

469 31 17 33 34 2 47.3

470 31 17 33 34 3 48.0

471 31 17 33 34 4 48.6

472 31 17 33 34 5 49.3

473 31 17 33 34 6 49.9

474 31 17 33 34 7 50.6

475 31 17 33 34 8 51.2

476 31 17 33 34 9 51.9

477 31 17 33 34 10 52.5

478 31 17 33 34 11 53.2

479 31 17 33 34 12 53.9

480 31 17 33 34 13 54.5

481 31 17 33 34 14 55.2

482 31 17 33 34 15 55.8

483 31 17 33 34 16 56.5

484 32 17 33 34 1 57.1

485 32 17 33 34 2 57.8

486 32 17 33 34 3 58.4

487 32 17 33 34 4 59.1

488 32 17 33 34 5 59.7

489 32 17 33 34 6 60.4

490 32 17 33 34 7 61.0

491 32 17 33 34 8 61.7

492 32 17 33 34 9 62.3

493 32 17 33 34 10 63.0

494 32 17 33 34 11 63.6

495 32 17 33 34 12 64.3

496 32 17 33 34 13 64.9

497 32 17 33 34 14 65.6

498 32 17 33 34 15 66.2

499 32 17 33 34 16 66.9

500 33 18 35 36 1 67.5


2202125

DAS/DETECTOR1–16

REV 28




502 33 18 35 36 3 68.8

503 33 18 35 36 4 69.5

504 33 18 35 36 5 70.1

505 33 18 35 36 6 70.8

506 33 18 35 36 7 71.4

507 33 18 35 36 8 72.1

508 33 18 35 36 9 72.7

509 33 18 35 36 10 73.4

510 33 18 35 36 11 74.0

511 33 18 35 36 12 74.7

512 33 18 35 36 13 75.3

513 33 18 35 36 14 76.0

514 33 18 35 36 15 76.6

515 33 18 35 36 16 77.3

516 34 18 35 36 1 77.9

517 34 18 35 36 2 78.6

518 34 18 35 36 3 79.2

519 34 18 35 36 4 79.9

520 34 18 35 36 5 80.5

521 34 18 35 36 6 81.2

522 34 18 35 36 7 81.8

523 34 18 35 36 8 82.5

524 34 18 35 36 9 83.1

525 34 18 35 36 10 83.8

526 34 18 35 36 11 84.4

527 34 18 35 36 12 85.1

528 34 18 35 36 13 85.7

529 34 18 35 36 14 86.4

530 34 18 35 36 15 87.0

531 34 18 35 36 16 87.7

532 35 19 37 38 1 88.3

533 35 19 37 38 2 89.0

534 35 19 37 38 3 89.6

535 35 19 37 38 4 90.2

536 35 19 37 38 5 90.9

537 35 19 37 38 6 91.5

538 35 19 37 38 7 92.2

539 35 19 37 38 8 92.8

540 35 19 37 38 9 93.5

541 35 19 37 38 10 94.1

542 35 19 37 38 11 94.8

543 35 19 37 38 12 95.4

544 35 19 37 38 13 96.1

545 35 19 37 38 14 96.7

546 35 19 37 38 15 97.4

547 35 19 37 38 16 98.0

548 36 19 37 38 1 98.6

549 36 19 37 38 2 99.3

550 36 19 37 38 3 99.9


2202125

DAS/DETECTOR1–17

REV 28




552 36 19 37 38 5 101.2

553 36 19 37 38 6 101.9

554 36 19 37 38 7 102.5

555 36 19 37 38 8 103.2

556 36 19 37 38 9 103.8

557 36 19 37 38 10 104.4

558 36 19 37 38 11 105.1

559 36 19 37 38 12 105.7

560 36 19 37 38 13 106.4

561 36 19 37 38 14 107.0

562 36 19 37 38 15 107.7

563 36 19 37 38 16 108.3

564 37 20 39 40 1 108.9

565 37 20 39 40 2 109.6

566 37 20 39 40 3 110.2

567 37 20 39 40 4 110.9

568 37 20 39 40 5 111.5

569 37 20 39 40 6 112.2

570 37 20 39 40 7 112.8

571 37 20 39 40 8 113.4

572 37 20 39 40 9 114.1

573 37 20 39 40 10 114.7

574 37 20 39 40 11 115.4

575 37 20 39 40 12 116.0

576 37 20 39 40 13 116.6

577 37 20 39 40 14 117.3

578 37 20 39 40 15 117.9

579 37 20 39 40 16 118.6

580 38 20 39 40 1 119.2

581 38 20 39 40 2 119.8

582 38 20 39 40 3 120.5

583 38 20 39 40 4 121.1

584 38 20 39 40 5 121.8

585 38 20 39 40 6 122.4

586 38 20 39 40 7 123.0

587 38 20 39 40 8 123.7

588 38 20 39 40 9 124.3

589 38 20 39 40 10 125.0

590 38 20 39 40 11 125.6

591 38 20 39 40 12 126.2

592 38 20 39 40 13 126.9

593 38 20 39 40 14 127.5

594 38 20 39 40 15 128.1

595 38 20 39 40 16 128.8

596 39 21 41 42 1 129.4

597 39 21 41 42 2 130.0

598 39 21 41 42 3 130.7

599 39 21 41 42 4 131.3

600 39 21 41 42 5 132.0


2202125

DAS/DETECTOR1–18

REV 28




602 39 21 41 42 7 133.2

603 39 21 41 42 8 133.9

604 39 21 41 42 9 134.5

605 39 21 41 42 10 135.1

606 39 21 41 42 11 135.8

607 39 21 41 42 12 136.4

608 39 21 41 42 13 137.0

609 39 21 41 42 14 137.7

610 39 21 41 42 15 138.3

611 39 21 41 42 16 138.9

612 40 21 41 42 1 139.6

613 40 21 41 42 2 140.2

614 40 21 41 42 3 140.8

615 40 21 41 42 4 141.5

616 40 21 41 42 5 142.1

617 40 21 41 42 6 142.7

618 40 21 41 42 7 143.4

619 40 21 41 42 8 144.0

620 40 21 41 42 9 144.6

621 40 21 41 42 10 145.3

622 40 21 41 42 11 145.9

623 40 21 41 42 12 146.5

624 40 21 41 42 13 147.2

625 40 21 41 42 14 147.8

626 40 21 41 42 15 148.4

627 40 21 41 42 16 149.1

628 41 22 43 44 1 149.7

629 41 22 43 44 2 150.3

630 41 22 43 44 3 150.9

631 41 22 43 44 4 151.6

632 41 22 43 44 5 152.2

633 41 22 43 44 6 152.8

634 41 22 43 44 7 153.5

635 41 22 43 44 8 154.1

636 41 22 43 44 9 154.7

637 41 22 43 44 10 155.4

638 41 22 43 44 11 156.0

639 41 22 43 44 12 156.6

640 41 22 43 44 13 157.2

641 41 22 43 44 14 157.9

642 41 22 43 44 15 158.5

643 41 22 43 44 16 159.1

644 42 22 43 44 1 159.7

645 42 22 43 44 2 160.4

646 42 22 43 44 3 161.0

647 42 22 43 44 4 161.6

648 42 22 43 44 5 162.2

649 42 22 43 44 6 162.9

650 42 22 43 44 7 163.5


2202125

DAS/DETECTOR1–19

REV 28




652 42 22 43 44 9 164.7

653 42 22 43 44 10 165.4

654 42 22 43 44 11 166.0

655 42 22 43 44 12 166.6

656 42 22 43 44 13 167.2

657 42 22 43 44 14 167.9

658 42 22 43 44 15 168.5

659 42 22 43 44 16 169.1

660 43 23 45 46 1 169.7

661 43 23 45 46 2 170.4

662 43 23 45 46 3 171.0

663 43 23 45 46 4 171.6

664 43 23 45 46 5 172.2

665 43 23 45 46 6 172.8

666 43 23 45 46 7 173.5

667 43 23 45 46 8 174.1

668 43 23 45 46 9 174.7

669 43 23 45 46 10 175.3

670 43 23 45 46 11 176.0

671 43 23 45 46 12 176.6

672 43 23 45 46 13 177.2

673 43 23 45 46 14 177.8

674 43 23 45 46 15 178.4

675 43 23 45 46 16 179.1

676 44 23 45 46 1 179.7

677 44 23 45 46 2 180.3

678 44 23 45 46 3 180.9

679 44 23 45 46 4 181.5

680 44 23 45 46 5 182.1

681 44 23 45 46 6 182.8

682 44 23 45 46 7 183.4

683 44 23 45 46 8 184.0

684 44 23 45 46 9 184.6

685 44 23 45 46 10 185.2

686 44 23 45 46 11 185.8

687 44 23 45 46 12 186.5

688 44 23 45 46 13 187.1

689 44 23 45 46 14 187.7

690 44 23 45 46 15 188.3

691 44 23 45 46 16 188.9

692 45 24 47 48 1 189.5

693 45 24 47 48 2 190.1

694 45 24 47 48 3 190.8

695 45 24 47 48 4 191.4

696 45 24 47 48 5 192.0

697 45 24 47 48 6 192.6

698 45 24 47 48 7 193.2

699 45 24 47 48 8 193.8

700 45 24 47 48 9 194.4


2202125

DAS/DETECTOR1–20

REV 28




702 45 24 47 48 11 195.7

703 45 24 47 48 12 196.3

704 45 24 47 48 13 196.9

705 45 24 47 48 14 197.5

706 45 24 47 48 15 198.1

707 45 24 47 48 16 198.7

708 46 24 47 48 1 199.3

709 46 24 47 48 2 199.9

710 46 24 47 48 3 200.5

711 46 24 47 48 4 201.2

712 46 24 47 48 5 201.8

713 46 24 47 48 6 202.4

714 46 24 47 48 7 203.0

715 46 24 47 48 8 203.6

716 46 24 47 48 9 204.2

717 46 24 47 48 10 204.8

718 46 24 47 48 11 205.4

719 46 24 47 48 12 206.0

720 46 24 47 48 13 206.6

721 46 24 47 48 14 207.2

722 46 24 47 48 15 207.8

723 46 24 47 48 16 208.4

724 47 25 49 50 1 209.0

725 47 25 49 50 2 209.6

726 47 25 49 50 3 210.3

727 47 25 49 50 4 210.9

728 47 25 49 50 5 211.5

729 47 25 49 50 6 212.1

730 47 25 49 50 7 212.7

731 47 25 49 50 8 213.3

732 47 25 49 50 9 213.9

733 47 25 49 50 10 214.5

734 47 25 49 50 11 215.1

735 47 25 49 50 12 215.7

736 47 25 49 50 13 216.3

737 47 25 49 50 14 216.9

738 47 25 49 50 15 217.5

739 47 25 49 50 16 218.1

740 48 25 49 50 1 218.7

741 48 25 49 50 2 219.3

742 48 25 49 50 3 219.9

743 48 25 49 50 4 220.5

744 48 25 49 50 5 221.1

745 48 25 49 50 6 221.7

746 48 25 49 50 7 222.3

747 48 25 49 50 8 222.9

748 48 25 49 50 9 223.5

749 48 25 49 50 10 224.1

750 48 25 49 50 11 224.7


2202125

DAS/DETECTOR1–21

REV 28




752 48 25 49 50 13 225.9

753 48 25 49 50 14 226.5

754 48 25 49 50 15 227.0

755 48 25 49 50 16 227.6

756 49 26 51 52 1 228.2

757 49 26 51 52 2 228.8

758 49 26 51 52 3 229.4

759 49 26 51 52 4 230.0

760 49 26 51 52 5 230.6

761 49 26 51 52 6 231.2

762 49 26 51 52 7 231.8

763 49 26 51 52 8 232.4

764 49 26 51 52 9 233.0

765 49 26 51 52 10 233.6

766 49 26 51 52 11 234.2

767 49 26 51 52 12 234.8

768 49 26 51 52 13 235.4

769 49 26 51 52 14 235.9

770 49 26 51 52 15 236.5

771 49 26 51 52 16 237.1

772 50 26 51 52 1 237.7

773 50 26 51 52 2 238.3

774 50 26 51 52 3 238.9

775 50 26 51 52 4 239.5

776 50 26 51 52 5 240.1

777 50 26 51 52 6 240.7

778 50 26 51 52 7 241.2

779 50 26 51 52 8 241.8

780 50 26 51 52 9 242.4

781 50 26 51 52 10 243.0

782 50 26 51 52 11 243.6

783 50 26 51 52 12 244.2

784 50 26 51 52 13 244.8

785 50 26 51 52 14 245.3

786 50 26 51 52 15 245.9

787 50 26 51 52 16 246.5

788 51 27 53 54 1 247.1

789 51 27 53 54 2 247.7

790 51 27 53 54 3 248.3

791 51 27 53 54 4 248.8

792 51 27 53 54 5 249.4

793 51 27 53 54 6 250.0


2202125

DAS/DETECTOR1–22

blank


2202125

DAS/DETECTOR2–1

REV 4


Table 2–1 CIF Board LED Description

LED Description

DS1 – 8(8 LEDs)

Blinks while the microprocessor is normally operating (not hung–up).

Illustration 2–1 CIF Board

DS1 – 8 (8 LEDs)


2202125

DAS/DETECTOR2–2

blank


2202125

X–RAY GENERATORi

REV 21

X–RAY GENERATOR

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 – LED DESCRIPTION 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 KV MEASURE BOARD 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1-1 Illustration 1–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 FILAMENT BOARD 1 INV 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2-1 Illustration 1–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 ROTATION BOARD HIGH SPEED 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3-1 Illustration 1–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2 Indicators 1–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4 LV POWER SUPPLY 3 PH BOARD 1–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-1 Illustration 1–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5 GATE COMMAND BOARD 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5-1 Illustration 1–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6 DUAL SNUB BOARD 1–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6-1 Illustration 1–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7 IF BOARD NP 1–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 KV CONTROL BOARD 1–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8-1 Illustration 1–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8-2 Indicators 1–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9 AC/DC THREE PHASE BOARD 1–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9-1 Illustration 1–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2 – ERRORS, DIAGNOSTICS & TROUBLESHOOTING (NP, NP+, NP+ TWIN) 2–1. 2-1 INTRODUCTION 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 POWER ON DIAGNOSTICS 2–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 ERROR CODE LIST 2–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 ERROR REPORTING 2–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 DIAGNOSTICS 2–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-5-1 Detailed Error Description & Troubleshooting Guide 2–8. . . . . . . . . . . . . . . . . . . 2-6 WARNING ERRORS 2–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 OTHER FAILURES 2–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 HEATING FUNCTION DIAGNOSTICS 2–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 ROTATION FUNCTION DIAGNOSTICS 2–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 INVERTER GATE COMMAND DIAGNOSTICS 2–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 INVERTER IN SHORT CIRCUIT DIAGNOSTICS 2–37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 NO LOAD HV DIAGNOSTICS 2–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

X–RAY GENERATORii

REV 21

SECTION PAGE

SECTION 3 – ERRORS, DIAGNOSTICS & TROUBLESHOOTING (NP++, NP++ TWIN) 3–1. 3-1 INTRODUCTION 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 POWER ON DIAGNOSTICS 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 ERROR CODE LIST 3–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 ERROR REPORTING 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4-1 NP Generator Error Reporting 3–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4-2 Tiger Generator Error Reporting (not for NP++ and Ebisu systems) 3–8. . . . . .

3-5 DIAGNOSTICS 3–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5-1 Detailed Error Description & Troubleshooting Guide 3–9. . . . . . . . . . . . . . . . . . .

3-5-1-1 Errors 3–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 WARNING ERRORS 3–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 OTHER FAILURES 3–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 HEATING WITHOUT HV NOR ROTATION DIAGNOSTIC 3–35. . . . . . . . . . . . . . . . . . . . . . 3-9 ROTATION WITHOUT HV NOR FILAMENT DIAGNOSTIC 3–36. . . . . . . . . . . . . . . . . . . . . 3-10 HV POWER DIAGNOSTICS 3–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-10-1 Inverter Gate Command Diagnostic 3–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10-2 Inverter in Short Circuit Diagnostic 3–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10-3 No Load HV Diagnostic without Anode Rotation nor Filament Heating 3–43. . . .

3-11 TROUBLESHOOTING AIDS 3–45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4 – ERRORS, DIAGNOSTICS & TROUBLESHOOTING(FOR P5.4 OR LATER JEDI SOFTWARE) 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1 INTRODUCTION 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 POWER ON DIAGNOSTICS 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 ERROR CODE LIST 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 ERROR REPORTING 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-4-1 NP Generator Error Reporting 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4-2 Tiger Generator Error Reporting (not for NP++ and Ebisu systems) 4–8. . . . . .

4-5 DIAGNOSTICS 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5-1 Detailed Error Description & Troubleshooting Guide 4–9. . . . . . . . . . . . . . . . . . .

4-5-1-1 Errors 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 WARNING ERRORS 4–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 OTHER FAILURES 4–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 HEATING WITHOUT HV NOR ROTATION DIAGNOSTIC 4–36. . . . . . . . . . . . . . . . . . . . . . 4-9 ROTATION WITHOUT HV NOR FILAMENT DIAGNOSTIC 4–37. . . . . . . . . . . . . . . . . . . . . 4-10 HV POWER DIAGNOSTICS 4–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-10-1 Inverter Gate Command Diagnostic 4–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10-2 Inverter in Short Circuit Diagnostic 4–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10-3 No Load HV Diagnostic without Anode Rotation nor Filament Heating 4–45. . . .

4-11 TROUBLESHOOTING AIDS 4–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


2202125

X–RAY GENERATOR1–1

REV 13


1-1 KV MEASURE BOARD

1-1-1 Illustration

This board forms part of the oil seal of the High Voltage Tank. It can only beremoved at the factory. The Field Replaceable Unit (FRU) is the complete HVTank.

LF

CSF

CAUTION


2202125


REV 13

1-2 FILAMENT BOARD 1 INV

1-2-1 Illustration

HIGH VOLTAGE: DO NOT GO INTO GENERATOR UNTIL INDICATOR DS3 GOESOUT.

RST – Red – Board beingreset or powered up

SF_LF – Yellow – SmallFocus / Large FocusRelay Feedback

DS2 – Yellow – StatusLED

DS1 – Yellow – StatusLED

DS3 – Green – +160vDC present

DS4 – Yellow – InverterOutput Running

ON – Yellow – Invert-er Command ON

DC160v LF Common

SF

0

160v

DC

DANGER


2202125


REV 13

1-3 ROTATION BOARD HIGH SPEED

1-3-1 Illustration

HIGH VOLTAGE: DO NOT GO INTO GENERATOR UNTIL INDICATOR DS6 ANDDS7 (NEON–ORANGE) GO OUT.

DS6

CommonDC bus

Auxiliary

DC busMain

DC bus

DANGER


2202125


REV 13

1-3-2 Indicators

INDICATOR COLOR INDICATES:

RESET Red BOARD BEING RESET OR POWERED UP

INV_ON Yellow THE INVERTER IS RUNNING

DS1 Green PRESENCE OF +15 V SUPPLY

DS2 Green PRESENCE OF –15 V SUPPLY

DS3 Green PRESENCE OF +5 V SUPPLY

DS4–DS5 Yellow BOARD STATUS

DS6 Neon (orange) FAN VAC POWER SUPPLY PRESENT

DS7 Neon (orange) DC BUS PRESENT


2202125


REV 13

1-4 LV POWER SUPPLY 3 PH BOARD

1-4-1 Illustration

HIGH VOLTAGE AND HOT SURFACE: DO NOT TOUCH BOARD UNTILINDICATOR NE1 (NEON – ORANGE) GOES OUT.

NE1 – Orange – indicates presence of DC Bus

DS2 – Green – 160 VDC

DS1 – Red – Mains Drop

– 40

0

DC bus

160V

+ 4

00

DC0

DANGER


2202125


REV 13

1-5 GATE COMMAND BOARD

1-5-1 Illustration

HIGH VOLTAGE: DO NOT TOUCH BOARD UNTIL DS300 ON THIS BOARD ANDDS1 ON DUAL SNUB BOARD ARE OUT.Hot surface on transformer T300 and heat sink.

DS

100

DS

102

DS

200

DS

101

DS100 –Yellow–Low IGBT*(Q100) Gate Command run-ning

DS101 – Green – Presence of+20 V Supply on low IGBT*Gate Command

DS200 – Yellow – HighIGBT* (Q200) Gate Com-mand running

DS102 – Green – Pres-ence of –10 V Supply onlow IGBT* Gate Command

DS202 – Green – Pres-ence of –10 V Supply onhigh IGBT* Gate Com-mand

DS300 – Neon (Orange) –Presence of voltage on DCbus for Flyback Converter tocreate power supplies forboth Gate Commands

* Insulated GateBipolar Transistor

DS

300

DS

201

DS

202DS201 – Green – Presence

of +20 V Supply on highIGBT* Gate Command

DC bus

Inverter

current

feedback

ILP

ILR

DANGER

CAUTION


2202125


REV 13

1-6 DUAL SNUB BOARD

1-6-1 Illustration

HIGH VOLTAGE: DO NOT GO INTO GENERATOR UNTIL INDICATOR DS1 (NEON– ORANGE) GOES OUT.

DS1 – Neon (Orange) – Indicates presence of voltage on DC Bus

DANGER


2202125


REV 13

1-7 IF BOARD NP

ServiceLaptop

System I/F

System I/F


2202125


REV 13

1-8 KV CONTROL BOARD

1-8-1 Illustration


2202125


REV 13

1-8-2 Indicators

INDICATOR COLOR INDICATES:

CONF Red FIELD PROGRAMMABLE GATE ARRAY (FPGA)CONFIGURATION NOT ACCOMPLISHED

OK Yellow INVERTER GATE POWER SUPPLY OK

TX_TAV Yellow TRANSMIT TO SERVICE LAPTOP

RX_TAV Yellow RECEIVE FROM SERVICE LAPTOP

T_CAN_X Yellow SYSTEM CAN BUS TRANSMIT

R_CAN_X Yellow SYSTEM CAN BUS RECEIVE

HALT Red MICROPROCESSOR HALTED

RESET Red BOARD BEING RESET

S0 TO S7 Yellow STATUS LEDIN APPLICATION MODE THESE LEDS FLASH IN

SEQUENCE CONTINUOUSLY

DS1 Green –15V SUPPLY

DS2 Green +15V SUPPLY


2202125


REV 13

1-9 AC/DC THREE PHASE BOARD

1-9-1 IllustrationHIGH VOLTAGE: DO NOT GO INTO GENERATOR UNTIL DS1 (NEON – ORANGE)GOES OUT.

Some components on this board can become very hot.

F1 – Fuse – Protects (on DC Bus): LV Power Supply 3 Phase Board Rotor Board High Speed Gate Command BoardType: 15 A, 600 VDC

DS1 – Neon(Orange) – Indi-cates presenceof voltage on theDC Bus.

DC Bus outDC Bus to inverter

DANGER

CAUTION


2202125


blank


2202125


REV 29

SECTION 2 – ERRORS, DIAGNOSTICS &TROUBLESHOOTING (NP, NP+, NP+ Twin)

2-1 INTRODUCTION

This diagnostics section is to introduce the JEDI generator with the following information:Power–On diagnostics LED indication.

List all the potential error codes that can be issued by JEDI Generator.

Provide error code explanation, potential cause and recommended action.

List of diagnostics aids and explanation of diagnostics.

2-2 POWER ON DIAGNOSTICS

Refer to theory of operation for power–on sequence. This paragraph in this section is to providemeaning of boards’ LED status. The LED display status is offering useful information at a glance toproceed to error code based troubleshooting. Whenever in doubt, a simple step is to watch the LEDstatus display on the kV control board, than the Rotation and Heater.

kV control LED status:– During Power On Diagnostics :

S0.........................S7

⊗ ⊗ ⊗ ⊗ ⊗ ⊗ � ⊗

The 8 LED’s (S0...S7) are lit successively in both directions (as indicated by the arrows): the power updiagnostics are completed, kV control board is up and running.

kV control board

S0..................S7

� � � � � � � � � �


2202125


REV 29

S0.....................S7

� ⊗ � ⊗ � ⊗ � ⊗

One out of two is lit: Data base checksum problem. An error code is logged. Refer to error codedescription.

S0.........................S7

� � � ⊗ ⊗ � � �

S7, S6, S5 are lit along with either S0 or S1 or S2 (depending of the type of FPGA down One out oftwo is lit: Data base checksum problem. An error code is logged. Refer to error code description.

– When an application error occurs (Not PRD)

⊗ ⊗ ⊗ ⊗ � ⊗ � ⊗

The simplified error code is displayed on the Leds. They blink; when the error is cleared ( by a returnto the standby mode for example ), the 8 LEDs are lit successively.

Heater board LED status: (See LED Description)

After the power on diagnostics, heater board LEDs DS1 and DS2 are lit successively. Any differentstatus correspond to an abnormal situation. An error code is logged. Refer to error code description.

Rotation board LED status: (See LED Description)

After the power on diagnostics, rotation board LED DS5 is blinking. Any different status correspond toan abnormal situation. An error code is logged. Refer to error code description.


2202125


REV 29

2-3 ERROR CODE LIST

The error code list and associated short description is presented below.

simpli-fied

errorcode

Description ErrorClass

ErrorCode

Description

30 Tube Spits 2 0301H Tube spit (kV+ and kV– dropped)2 0302H Tube spit (kV+ has dropped)2 0303H Tube spit (kV– has dropped)2 0304H Tube spit (kV regulation error)2 0305H FPGA problem (restarting safety signal)

40 Rotation Error 4 0101H No CAN message received within 5 secs4 0102H Database not correct4 0103H Rotation current overload4 0104H Rotation Openload4 0105H Rotation Phases unbalanced4 0106H Rotation Phases error4 0107H Rotation Inverter permanent overcurrent4 0109H MAINS_DROP has failed4 0110H PRD error (Z3Z4=bitmap)4 0111H F0 main frequency problem4 0149H Unknown Rotation error

50 Heater Error 4 0201H No CAN message received within 5 secs4 0203H Inverter overcurrent (HW detected)4 0204H Open circuit (HW detected)4 0205H Inverter short circuit (HW detected)4 0206H Filament too high for Pre–heat4 0207H Filament current too high4 0208H Filament too hot4 0210H Current over estimated (short circuit)4 0211H Current under estimated (open circuit)4 0212H MAINS_DROP detected4 0213H PRD error (Z3Z4=bitmap)4 0214H Stay too long in Boost4 0215H Filament selection error4 0216H current feedback not null when inverter off4 0221H

0222H0223H0224H

Filament database tube 1 errorFilament database tube 2 errorFilament database tube 3 errorFilament database tube 4 error

4 0248H0249H

Unknown Heater LF errorUnknown Heater SF error


2202125


REV 29simpli-

fiederrorcode


Error Description

60 Exposure er-rors

3 0306H No kV Feedback on anode

3 0307H No kV Feedback on cathode3 0308H No kV Feedback on anode and cathode3 0309H kV detected during kV diag3 0310H kV max detected3 0311H ILP current not OK3 0312H ILR current not OK3 0313H ILR max current detected3 0314H ILR current timeout3 0316H Spit Max error3 0317H Spit Ratio error3 0318H kV did not reach 75% after 20ms3 0319H kV unbalanced detected3 0320H FPGA problem (safety signal)3 0323H ILP and ILR currents not OK3 0401H No mA feedback3 0402H mA scale error2 0403H mA accuracy exceeded 5%3 0504H Inverter Gate Power Supply failed3 0801H Exposure backup mAs exceeded3 0802H Exposure backup time exceeded3 0803H Exp cmd while gene not ready3 1406H time counter error3 1407H mAs counter error3 1408H AEC counter error3 1409H mAs meter saturated3 1410H FPGA Locked

Note:When 0313H, 0316H, or 0317H error occur few times a week, the X–ray tube must be earlyreplaced. This error reports spits occurrance or abnormal high pressure of X–ray tube. If thecurrent defective X–ray tube continues to be used, the High voltage cable between HEMIT andtube for NPV3 JEDI Generator or Inverter IGBT for NP JEDI might be damaged.

70 Power Supplyerrors

4 0501H DC bus out of range

4 0503H Inverter Gate Power Supply error4 0505H Mains power supply has dropped during exposure4 0506H DC bus 1 phase precharge error4 0507H DC bus 1 phase discharge error4 0549H Unknown LVPS error4 0553H Detected +160V too high4 0557H Detected +160V too low4 0563H Detected +15V too high4 0567H Detected +15V too low4 0573H Detected –15V too strong4 0577H Detected –15V too weak


2202125


REV 29simpli-

fied errorcode


Error Description

80 Hardware error 4 0180H Rotor board communication problem4 0181H Rotor board has reset4 0280H Heater board communication problem4 0281H Heater board has reset4 0322H kV ref ADC / DAC failed4 0601H RTL error4 0602H External CAN bus off4 0902H tube Fan supply error4 1402H Internal CAN bus off4 1403H Connectic Fault4 1404H FPGA configuration problem4 1405H Tank sensor problem

90 Application er-rors

4 0701H Saved RAM checksum pb

4 0702H Software problem4 0704H Rotor/Heater hold too long

100 Com errors 4 0603H Debug screen com error4 0604H Database download error4 0605H TAV com error4 0606H MPC/Madrid com error4 1301H ADC Board com error

110 Thermal error 5 0804H Tank Thermal Error5 0903H Tube exceeded 70degC3 1454H Jedi inverter temperature too high

10 Rotor Warning 1 0151H CAN Domain command number error1 0152H CAN Domain request with no transfer init1 0153H CAN Domain Toggle bit error1 0154H CAN Domain : less than 2 data to download1 0155H CAN Domain Abort received & applied1 0156H Bad index in config upload1 0157H Tube switch while rotor not off1 0158H Acceleration cmd while no tube selected1 0159H Acceleration cmd while database not OK1 0160H Database download while rotor speeding1 0161H Acceleration command not OK1 0162H Rotor acceleration while in error1 0163H No CAN message received within 4 secs1 0164H Rotation Inverter overcurrent (< 3 times)1 0199H Unknown rotation warning


2202125


REV 29

simpli-fied error

code


Error Description

20 Heater Warn-ing

1 0251H Received command is not OK

1 0252H Heater command not OK1 0253H No CAN message received within 4 secs1 0254H Heater inverter overcurrent (inverter1) (<3 times)1 0255H Filament open circuit (inverter1) (<3 times)1 0256H Heater Inverter short circuit (inverter1) (<3times)1 0257H Tube switch while filaments not OFF1 0258H CAN Domain command number error1 0259H CAN Domain request with no transfer init1 0260H CAN Domain Toggle bit error1 0261H CAN Domain : less than 2 data to download1 0262H CAN Domain Abort received & applied1 0263H Database download while heater not cut1 0299H Unknown Heater warning

25 Low VoltagePower supply

Warnings

1 0550H No more warn +160V too low or too high

1 0551H Detected +160V too high1 0555H Detected +160V too low1 0560H No more warn +15V too low or too high1 0561H Detected +15V too high1 0565H Detected +15V too low1 0570H No more warn –15V too low or too high1 0571H Detected –15V too strong1 0575H Detected –15V too weak1 0599H Unknown LVPS warning

27 Applicationwarnings

1 1401H Saved RAM battery limit reached. Replace thekV board.

1 0703H Watchdog reset has just occurred


2202125


REV 29

2-4 ERROR REPORTING

Np system only gets the simplified error code from the Jedi generator.

The Np system errorlog adds to the simplified error code the following information :

� error message (refer to the Np system documentation)

� system phase : state of the system when the error occurred. Take care, the system state may bedifferent to the generator phase (refer to the Np system documentation)

� system time : date and time when the error occurred. Take care, the system time may be differentto the generator time

Whenever a generator error is logged in the system errorlog file and displayed on the operatorconsole, the Jedi errorlog upload functionality is available to get more detailed information about theerror.

This function must be performed from the operator console.

The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.

Having these two information, look at the Jedi trouble shooting table to find the FRU to replace.

Error codes can also be read by connecting the laptop


2202125


REV 29

2-5 DIAGNOSTICS

This chapter describes diagnostics tools based on error codes and specific diagnostics.

Before any manual intervention, ensure the main power is off. Apply lockout–tag out procedure for your own safety when manipulating inside theequipment is required.

2-5-1 Detailed Error Description & Troubleshooting Guide

The table below provides guidelines to troubleshoot Generator problems based on error code.

For each code, there is :

– Associated message and additional explanation related to the error occurrence.

– List potential cause, in the order of expected probability.

– Recommended action, with, in some cases, link to some more information as indicated wherecases apply, such as to run some specific diagnostics.

Codes are sorted by ascending order both for simplified code and error code.

Refer to the theory of operation for error code structure.

Information about associated data structure is located at the end of each error code subset wheneverit applies.

Whenever wiring, cabling, LED check is mentioned in the recommended actions, refer to the LEDDescription or to Illustration 2–1.

WARNING


2202125


REV 29

Errors

Tube spits detection Errors (Code 30)

Class 2Class 2Error code

Message/explanation Potential cause Recommended action/ Trouble-shooting guide

30–0301H

Tube spit (kV+ and kV–dropped)

kV drop/spit detected

x–ray tube spit. –If too frequent, and varies with HV,replace x–ray tube.Run Open load kV test. (See diag-nostic section)

30–0302H

Tube spit (kV+ hasdropped)kV drop/spit detected on

Anode side

1. Anode side Tube spit.2. Anode HV cable3. HV tank

–Check HV cables and contacts–Tube problem. (Anode side)–Check cable by interchangingthem.–Run Open load kV test. (See diag-nostic section)–Otherwise, HV tank.

30–0303H

Tube spit (kV– hasdropped)kV drop/spit detected on

cathode side

1. Cathode side Tubespit.

2. Cathode HV cable3. HV tank

–Check HV cables and contacts–Tube problem. (Cathode side)–Check cable by interchangingthem.–Run Open load kV test. (See diag-nostic section)–Otherwise, HV tank

30–0304H

kV regulation errorThis is a slow speed safe-

ty circuit in case of“smooth” spits.

1 smooth HV tube spits2 kV control board (HV

regulation problem)3 too much line imped-

ance4 half of AC/DC capaci-

tors open5 Inverter (parallel induc-

tor or filtering capaci-tors)

6 HV tank

–Run inverter diagnostics (Seediagnostic section)–Run Open load kV test. (See diag-nostic section)–Troubleshoot tube and contacts ofHV cable.–Check DC bus voltage.

30–0305H

Re–starting safety. (un-known reason)Error occurring on safetyline, while No root error

present at the error inputs(Err 0301 to 0304). This isprobably due to transient

interference (Spikes).

1. External unknowncause.

2. kV control board.

–Do a power and Grounding Check.Verify cabling and contacts. –If permanent or too systematic,replace kV control board. Report toengineering.


2202125


REV 29

Anode Rotation errors (Code 40)



40–0101H

No CAN message re-ceived within 5 sec’sThe rotation board has notreceived any signal fromthe kV control main soft-

ware for the last 5 sec., in-terpreted as a loss of

communication

1. kV Control main soft-ware lost

2. kV control or Rotationboard driver failure

3. Bad contact on one ofthe pin on the CAN busline connector

–Unlikely to happen. This is a debugerror.–Retry–Re initialise and retry

40–0102H

Data base not correct.The firmware of the rota-tion board has detectedthat the data base re-

ceived from the kV controlboard has wrong data.

1. Wrong kV control database. It can only happenat power up.

–Reload NVRam data base.–ultimate is to replace rotationboard.

40–0103H

Rotation current overloadRotation board has de-tected Main or auxiliaryrotation current too highcompared to the max.Tube motor current.

1. Rotation board2. Rotation board capaci-

tors3. Wrong data base (im-

probable)

Check wiring from rotation board totube.If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shift ca-pacitors.(See diagnostic section).

40–0104H

Rotation current openloadRotation board detectedthat no current is flowing

to the motor.

1. Tube stator winding isopen circuit: x–ray tube

2. Incorrect wiring (Open)3. No DC bus on rotation

board4. Rotation board5. Rotation board phase

capacitors(improbable)

Check wiring from rotation board totube.If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shift ca-pacitors.(See diagnostic section).

40–0105H

Rotation phases unbal-ancedThe amplitude differenceof the current bwtween

main and auxiliary is toolarge.

1. One rotation wiremissing

2. Rotation board3. Rotation board phase

capacitors inverted orwrong value

4. Wrong tubeconfiguration database

– Check wiring from rotation boardto tube.– If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shiftcapacitors. (See diagnostic section)

40–0106H

Rotation phase errorThe rotation board has

detected that the currentin the anode stator does

not shyow the correctphase shift between main

and auxiliary.


capacitors inverted orwrong value

– Check capacitors wiring.– Verify none is in short circuit. If nowiring problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shiftcapacitors. (See diagnostic section)


2202125


REV 29

Error codeError code Message/explanation Potential cause Recommended action/ Trouble-shooting guide

40–0107H

Rotation Inverter perma-nent overcurrentAn overcurrent has been

detected and 3 restarthave been tried unsuc-cessfully within a single

rotation state

1. Rotation board2. Tube stator winding in

short circuit –> x–raytube

3. Wiring incorrect(shorted)

–Check wiring from rotation boardto tube.–Troubleshoot tube windings–Replace rotation board

40–0108H

Rotation command error.Rotation board has in-

formed kV control boardthat the command was er-roneous; this is a DEBUG

error.

No hardware failure None

40–0109H

MAINS_DROP has failedThe firmware of the rota-tion board has detected

the mains_drop signal ac-tivation and transmitted

error to kV control

1. Interference (spikes)2. Mains drop3. Cable or connector

contact in DC bus be-tween power unit andauxiliary unit

4. Rotation board

–Do a power and grounding check.–If systematic, replace rotationboard

40–0110H

PRD errorFirmware checksum, RAMtest and EPLD access areperformed at power up or

reset.

Rotation board Replace rotation board.

40–0111H

FO main frequency prob-lem.EPLD has not applied theinverter start command.

Rotation board – Retry– Replace rotation board

40–0149H

Unknown Rotation error.The main software re-

ceived an error from rota-tion board with no other

code assocxiated.

Software problem – No action– Report if too frequent.

Associated data structure (refer to error code description section) :

PRD error :component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum

rotation database error :

2 bytes data, each value points to a specific parameter found as being erroneous


2202125


REV 29

other errors :rotation state :0=inverter OFF1=acceleration 0 to low speed2=acceleration 0 to high speed3=acceleration low speed to high4=low speed run5=high speed run6=high speed to low speed brake7=brake reverse8=brake DC


2202125


REV 29

Filament Heater errors(Code 50)



50–0201H

No CAN message re-ceived within 5 sec’sThe Heater board has notreceived any commandfrom the kV control main

software for the last 5sec., interpreted as a loss

of communication

1. kV Control main soft-ware lost

2. kV control or Heaterboard driver failure


–Unlikely to happen. This is a debugerror.–Retry–Re initialise and retry.

50–0203H

Heater inverter permanentovercurrent.

Issued by the heaterboard when an overcur-rent has been detected

and 3 restarts have beentried without success with-

in 100 ms

1. Heater board –Restart. If persistent, replaceHeater board

50–0204H

Filament permanent opencircuit.

Issued by the heaterboard when an open hasbeen detected and 3 re-starts have been triedwithout success within

100 ms

1. X–ray tube filamentopen

2. Heater to HV tankcable

3. Cathode HV cable orpin contacts

4. Open circuit in filamenttransformer inside HVTank.

–Switch on the other filament:if no error is reported, heaterboard is working properly. Checkheater board to HV Tank to tubeconnections. If OK, test with Ohm–meter HV Tank heater transformers(primary and secondary) and fila-ment impedance. Order accordinglyIf the same error is reported,check the connections as above. Ifall are right, replace heater board

50–0205H

Heater Inverter permanentshort circuit (HW limit)

Issued by the heaterboard when a short circuithas been detected and 3restarts have been triedwithout success within

100 ms


50–0206H

Filament current too highfor “Pre–Heat”This is the result of an in-tegrated value of the RMScurrent measurement onHeater board comparisonwith max. Tube value in

data base.

1. Tube data base or cal-ibration

2. Heater board

–It’s unlikely, but reload NVRam da-tabase.–Replace heater board.


2202125


REV 29

Error codeError code Message/explanation Potential cause Recommended action/ Troubleshootingguide

50–0207H

Filament current too highfor “Boost”

Same as above


2. Heater board

Same as above

50–0208H

Filament current too highfor “Heat”

Same as above


2. Heater board

Same as above

50–0209H

Heater command errorHeater board has in-

formed kV control boardthat the command was er-roneous; this is a DEBUG

error.

No hardware failure None

50–0210H

Current over estimatedfork

RMS filament currentmeasurement (every 0.5msec.) on heater board is

too high

Heater board Replace heater board

50–0211H

Current under estimatedfork

RMS filament currentmeasurement (every 0.5

m sec.) on heater board istoo low

1. Open circuit2. Heater board

–Switch on the other filament:if no error is reported, heater board isworking properly. Check heater board toHV Tank to tube connections. If OK, testwith Ohm–meter HV Tank heater trans-formers (primary and secondary) and fil-ament impedance. Order accordinglyIf the same error is reported, checkthe connections as above. If all areright, change heater board

50–0212H

MAINS_DROP detected.The firmware of the Heat-er board has detected themains_drop signal activa-tion and has transmitted

error to kV control


contact in DC bus be-tween power unit andauxiliary unit

4. Heater board

–Do a power and grounding check. –If systematic, replace heater board

50–0213H


reset.

1. Heater board2. No –15v on Heaterboard

– Check presence of –15V : proceed tothe recommended action discribedunder error 70–0577H– Replace heater board.

50–0214H

Boost too long on invert-er1.

Boost command stayedlonger than 400ms

May be a loss of commu-nication during boost.

Retry.It will probably be followed by anothercommunication code.

50–0215H

Filament selection error.The relay on the Heaterboard selecting the fila-

ment is in the wrong posi-tion with respect to the

selection



2202125


REV 29


50–0216H

Measured current while in-verter OFFInverter current has beenmeasured while the invert-

er was not commanded


50–0221H0222H0223H0224H

Filament Database notcorrectThe firmware of the heater

board has detected thatthe Received Data basefrom kV control contains

erroneous data for Tube 1,2, 3, or 4.

1. Wrong kV control database. It can onlyhappen at power up.

–Reload NVRam data base.–ultimate is to replace Heaterboard.

50–0248H0249H

Unknown heater errorThe main software

received an error fromheater board with no error

code associated.

Software problem. – No action– Report if too frequent.

Associated data structure (refer to error code description section) :

PRD error :component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum

Filament database error :

2 bytes bitmap ( LSByte=small focus, MSByte=large focus)

Each bit points to an erroneous parameter

other errors :

1 byte bitmap with the following structure :bit7 (MSB) bit6 bit5 bit4 bit3 bit2 bit1 bit0 (LSB)

focus selected tube selected small focus state large focus state0=small focus selected1=large focus selected

1=tube 1 selected2=tube 23=tube 34=tube 4

0=inverter OFF1=preheat2=boost3=heat



2202125


REV 29

Exposure errors (Code 60)



60–0306H

No kV feedback on anodeside kv measured <12kV0,5ms after start of expo-sure on anode side only

1. HV cable short circuit2. HV tank3. kV control board (less

probable)

–Troubleshoot HV cables : run noload kV diagnostic along with invert-ing HV cablesIf HV cables are right, replace HVTank

60–0307H

No kV feedback on cath-ode side kv measured <12kV0,5ms after start of expo-sure on cathode side only


probable)


60–0308H

No kV Feedback (onanode and cathode)

kv measured <12kV0,5ms after start of expo-sure on both anode and

cathode.

1. HV tank2. kV control board

–Verify flat cable connections andsitting between kV control and HVtank.– Replace HV Tank

60–0309H

kV detected during kVdiagnostics. KV measured during in-verter diagnostics while nokV must be generated.

Improper setup before thediagnostic is run.

See HV power diagnostic section.

60–0310H

kV MAX detectedkV reached 160 kv during

exposure

kV control Replace kV control board

60–0311H

ILP current not OK.The current in the parallelresonant circuit of the in-verter did not rise at the

beginning of the exposure.

1. Inverter LC resonantcircuit (Inverter coilassy, capa inverterassy.)

2. Inverter3. kV control

run HV power diagnostics

60–0312H

ILR current not OKThe current in the serialresonant circuit of the in-verter did not rise at the


See above run HV power diagnostics

60–0313H

Inverter max. ILR currentdetected.This is a hardware detec-tion of maximum currentin serial resonant circuit.

1 Casing spit (Tube)2 HV tank3 kV control

– Check Tube– Check HV cable– run HV power diagnostics


2202125


REV 29



60–0314H

ILR Current time out.The current resonant fre-quency is lower than ex-

pected

1. kV control2. Inverter3. Current measurement

circuit.


60–0316H

Spit Max error.kV control has detectedthe number of tube spits

during exposure hasreached the limit (see

theory of operation, soft-ware section)

reasonably x–ray tube –Try again at various kV/mA to con-fine problem.–Troubleshoot HV section. (x–raytube, cable, HV tank)–Diagnose based on tube history.

60–0317H

Spit Ratio error.kV control has detected

the rate of tube spits dur-ing exposure has reachedthe limit (see theory of op-eration, software section)


60–0318H

kV did not reach 75% after20ms.Indicates that there wereno HV ON signal gener-ated for exposure time

count–up

1. kV control Replace kV control.

60–0319H

kV unbalanced detected.Detects that there is morethan 12kV difference be-

tween kV+ and kV –

1. HV tank2. KV control

Replace HV tank

60–0320H

FPGA problem; Safety hitwith unknown reason

No error at the inputswhile checking for error

source.

1. This may be due totransient interference(Spikes).

2. SW bug

Do a power and Grounding Check.Verify cabling and contacts.If permanent or too systematic, re-place kV control board.Report to engineering

60–0323H

ILP and ILR current notOKNo inverter current mea-sures at the beginning of

the exposure

1. Inverter LC resonantcircuit. (Inverter coilassy, capa inverterassy.)

2. InverterkV control board


60–0401H

No mA feedbackmA measurement func-

tion:kV control has detected nomA feedback 20 ms afterthe beginning of the expo-

sure.

1. HV tank2. kV control board3. x–ray tube (filament

open)

– Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is far out of range (4.9 –5.1 ohm including DVM accuracy),replace HV Tank.– Verify filament impedance– Replace kV control board


2202125


REV 29


60–0402H

mA scale errormA has been measured to

be either too low or toohigh with respect to mAdemand 20 ms after the

beginning of the exposure

1. kV control board2. default filament cur-

rents not correctly ad-justed

3. HV Tank (improbable)

– If the tube has just been replacedor installed, run following exposuresuntil the filament correction adjuststhe default filament drive values.

* Stationary, 120 kV 30 mA,small focus, 1 mm x 20 times 1 sec scan 1sec ISD

* Stationary, 140 kV 30 mA,small focus, 1 mm x 20 times 1 sec scan 1sec ISD

* Stationary, 80 kV 60 mA, smallfocus, 1 mm x 20 times 1 secscan 1sec ISD

* Stationary, 120 kV 30 mA,large focus, 10 mm x 20 times 1 sec scan 1sec ISD

* Stationary, 140 kV 30 mA,large focus, 10 mm x 20 times 1 sec scan 1sec ISD

* Stationary, 80 kV 60 mA, largefocus, 10 mm x 20 times 1 secscan 1sec ISD

– If the error occurs after a while ona system :Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is out of range, replace HVTank else replace kV control board

60–0403H

(Class 2 er-ror)

mA accuracy exceeded5%

Measured mA every 50msec exceeded 5% of mA

demand.This error is logged, butdoes not stop the expo-

sure.

1. tube spit no action



2202125


60–0504H

Inverter Gate Power Sup-ply error

gate supply voltage hasdropped below the level

required to drive theIGBTs properly

1. Inverter (gate com-mand board)

2. kV control board3. generator input voltage

too low or line imped-ance too high


60–0802H

Exposure backup time ex-ceeded.The exposure commandlast longer than the dura-tion that was loaded by

the system (Backup time +5%.)

1. System2. System–generator

cable3. I/F board : exposure

line stuck to the activestate

–Retry, changing parameters andduration– disconnect system–generatorcable in different places and checkexposure command line voltage

60–0803H

Exp cmd while gene notready.generator received an ex-

posure command whilenot in ready state

1. Inverter too hot, expo-sure parameters not OK2. Software problem3. Cable / communicationproblem4. External cause

(Spikes)

If problem is persistent, check heat-er, anode rotation and system togenerator preparation command tofind the root cause for the generatornot to be ready

60–1406H

Time counter error.Error found in verifying thecounter normal operation.

kV control board Replace kV control Board

60–1410H

FPGA locked.FPGA detected an error

and did not allow start ex-posure after exposure

command symbol was re-ceived

1. Software problem2 kV control

If persistent, replace kV control


2202125


REV 29

Power supply (Code 70)


Message/explanation Potential cause Recommended action/ Troubleshootingguide

70–0501H

DC bus out if range (<400or >850)

1. mains problem (Toolow or too high)

2. One phase missing atgenerator input

–Check mains line 3 phases incomingvoltage. –Verify line impedance if mains is low.–Verify DC Bus Voltage with a meter, ifDC Bus is in range, replace KV ControlBoard most probably.

70–0503H


1. Mains2. Cable pb3. Gate command board

(Inverter)4. kV control


70–0505H

Mains power supply hasdropped During exposure

unknown None

70–0549H

Unknown LVPS errorThe main software re-ceived an LVPS errorwith no error code associ-ated.

Software problem – No action– Report if too frequent.

70–0553H

Detected +160V too high+160V is higher than225V (measured on heat-er board)

1. LVPS2. Heater board

Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check 160V on CF2/1 on heater board.If OK, replace heater boardElse, disconnect the CF2 cable andmeasure again on the LVPS side. Ifvoltage is wrong, replace LVPS board.

70–0557H

Detected +160V too low+160V is lower than 110V

(measured on heaterboard)


Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check 160V on CF2/1 on heater board.If OK, replace heater boardElse, disconnect the CF2 cable andmeasure again on the LVPS side. Ifvoltage is wrong, replace LVPS board.

70–0563H

Detected +15V too high+15V is higher than 17.3V


1. LVPS open circuit2. Heater board

Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check 15V on heater board (J3, pin4).If OK, replace heater board.Else, disconnect the control bus cablefrom the LVPS board and check thepin2 of the connector : if voltage iswrong replace LVPS board.


2202125


REV 29


Message/explanation Potential cause Recommended action/ Troubleshootingguide

70–0567H

Detected +15V too low+15V is lower than 13V(measured on heater

board)

1. LVPS open circuit2. Heater board3. rotation (short circuit)kV control (short circuit)(improbable)

Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check 15V on heater board (J3, pin4).If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin4) and(J1,pin2).If no continuity, replace heaterboardElse, disconnect the control bus cablefrom the LVPS board and check thepin2 of the connector : if voltage iswrong replace LVPS board. Else,check pin2 of the control bus cablewhen disconnecting the cable fromeach board successively to isolate theboard inducing a voltage drop

70–0573H

Detected –15V too high–15V is lower than –17.3V



Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check –15V on heater board (J3, pin3).If OK, replace heater board.Else, disconnect the control bus cablefrom the LVPS board and check thepin3 of the connector : if voltage iswrong replace LVPS board.

70–0577H

Detected –15V too low–15V is higher than –13V


1. LVPS (open circuit)2. Heater board3. rotation (short circuit)4. kV control (short cir-

cuit) (improbable)

Verify that the DC bus on LVPS boardis in an acceptable range (CF1/CF2) Ifno, verify AC/DC fuse and AC inputvoltage.Check –15V on heater board (J3, pin3).If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin3) and(J1,pin3).If no continuity, replace heaterboardElse, disconnect the control bus cablefrom the LVPS board and check thepin3 of the connector : if voltage iswrong replace LVPS board. Else,check pin3 of the control bus cablewhen disconnecting the cable fromeach board successively to isolate theboard inducing a voltage drop


2202125


REV 29

Hardware errors (Code 80)Class 4

Error codeClass 4

Error code Message/explanation Potential cause Recommended action/ Trouble-shooting guide

80–0180H

Rotation board commu-nication problem.kV control board commu-nication Watch Dog with

Rotation board popped upbecause it did not get re-ply from Rotation board.

1. Rotation board2. Control bus cable3. kV control

A/Check that rotation firmware isrunning (DS5 Led is blinking).If no :1/verify rotation board 5V : Led DS3is lit. If no : verify DS1/DS2 Leds : ifthey are lit, replace rotation board,else go to +/–15V errors trouble-shooting2/ verify that RESET Led is not lit. Ifit is lit, disconnect successively thecontrol bus cable from heater andkV control to find the board which isholding the reset line and replace it.If after disconnecting all the boards,the Led remains lit, replace rotationboard3/ else replace rotation boardB/Verify the flat cable between kVcontrol and auxiliary module is cor-rectly connected to the RotationboardC/else replace kV control

80–0181H

Rotation board has reset. kV control has detected

the Rotation board has re-set. KV control will reload

rotation data base.

1. Rotation board2. Interference (Spikes)

–Reinitialize system, retry.–If persistent, replace Rotationboard or check power and ground-ing.

80–0280H

Heater board communica-tion problemkV control board commu-nication Watch Dog withHeater board popped upbecause it did not get re-ply from Heater board.

1. Heater board2. Control bus cable3. kV control

A/Check that heater firmware is run-ning (DS1/2 Led are lit succes-sively). If no :1/verify heater board 5V : J3/pin2. Ifwrong : verify +15V/–15V (J3,pin3,4) : if they are right, changerotation board, else go to +/–15Verrors troubleshooting2/ verify that RST Led is not lit. If itis lit, disconnect successively thecontrol bus cable from LVPS to rota-tion and kV control to find the boardwhich is holding the reset line andreplace it. If after disconnecting allthe boards, the Led remains lit, re-place heater board 3/ else replaceheater boardB/Verify the flat cablebetween kV control and auxiliarymodule is correctly connected untilthe heater boardC/else replace kV control board


2202125


REV 29

Error codeError code Message/explanation Potential cause Recommended action/ Troubleshootingguide

80–0281H

Heater board has reset.KV control has detectedthe heater board has re-set. KV control will reload

rotation data base.

1. Heater board2. Interference (Spikes)

–Reinitialize system, retry.–If persistent, replace board or checkpower and grounding.

80–0321H

KV conversion errorKV feedback measuredwhile no KV generated

KV control board Replace KV control board

80–0322H

kV ref ADC / DAC failedkV control DAC and ADCcapability are permanently

tested for coherency.

KV control board Only if this error is repetitive andcomes alone (Not following other er-rors), replace kV control board.

80–0601H

RTL error (+ associateddata to check which of the4 RTL lines)

Real Time Lines show awrong state. RTL’s are

tested on a regular basisin stand by.

1. system communicationpower supply (for iso-lated communications)

2. system communicationcable

3. system interface board4. system interface to kV

control flat cable5. kV control board

–Check communication cable–Check system communication powersupply (if any)–Check system interface to kV controlflat cable–replace system interface board–replace kV control board

80–0602H

External CAN bus off 1. system communicationpower supply (for iso-lated communications)




–Check communication cable–Check system communication powersupply (if any)–Check system interface to kV controlflat cable–replace system interface board–replace kV control board

80–0902H

Tube Fan supply error.Rotation board has de-tected that a wrong volt-age is applied to the tube

fan

1. No 115V tube coolingsupply2. Rotation board

–Check presence of the AC voltage(DS6 neon) at the input of the Rotationboard.If ok, replace the rotation board

80–1402H

Internal CAN bus offCan device on kV controlboard detected abnormal

level on it’s 2 line and senterror to the CPU

3. kV control4. Control bus cable3. Heater, Rotation

Check a short circuit on CAN pins ofthe control bus cable. Short circuit maybe either on boards or connector /cable.If no fault detected, replace kV control


2202125


REV 29


80–1403H

Connection FaultOne of the flat cable con-nector is not connected in

Generator.

Multiple, but likely improb-able.

Check connection of the followingcables : kV control to system I/Fboard, kV control to HV tank, HVtank to inverter.

80–1404H

FPGA configuration prob-lem.Detected during power up.The kV control main soft-

ware cannot load theFPGA.

kV control board. Replace kV control board.

80–1405H

Tank temperature sensorproblem.Means that t° value of theHV tank is < 10°C

kV controlHV tank

Replace kV controlReplace HV Tank


2202125


REV 29

Application errors(Code 90)



90–0701H

NV RAM checksum pb.Generator kV control

board has detected cor-ruption in the NV Ram

verification (After powerup)

1. Database problem2. External cause

(Spikes)3. kV control

If persistent :–Reload the Data base. If no im-provement :–Replace kV control board and re-load the data base.

90–0702H

Software problem. 1. Software or Data Baseproblem.

2. kV control board fail-ure.

–Reload the Data base–Reload the software and databaseIf no improvement :–Replace kV control board

90–0703H

Watchdog reset has justoccurred.This error is logged whenthe CPU of the kV control

board is reset by it’sWatch Dog timer.

1. Software or Data Baseproblem.

2. kV control board fail-ure.

–Reload the Data base–Reload the software and databaseIf no improvement :–Replace kV control board

90–0704H

Rotation/Heater hold toolong.Will pop up if preparationcommand from the sys-tem is maintained longer

than 3 minutes.

Software problem. No action


2202125


REV 29

Communication errors(code 100)



100–0603H

Debug screen com. error Engineering use

100–0604H

Database download errorGenerator has detected aproblem during data base

download

1. Database file incorrect2. Transmission problem

RetryCheck data base filePotential laptop incompatibility

100–0605H

TAV communication error.Generator has detected acommunication problembetween the I/F and the

service laptop (When gen-erator is controlled by the

laptop)

1. Software / laptop prob-lem

2. Cable problem

Retry


2202125


REV 29

Thermal errors(code 110)



110–0804H

Tank Thermal ErrorHV tank temperature

measurement hasreached 60 degree C

1. HV tank too hot; normalerror2. HV tank3. kV control

–Wait for error clearance–If persistent while HV Tank is cool :1/check flat cable connection be-tween HV Tank and kV controlboard2/ Check presence of –15v (LEDDS1 on kV control board)3/replace HV tank4/replace kV control

110–0903H

70 degree C thermal safe-ty error

70° loop detected open

1. X–ray tube too hot;normal error

2. Cooling problem3. Wiring problem4. Sensor problem (Tube)5. rotation board

–Wait for error clearance –If persistent :1/Check tube cooling (Fan), trouble-shoot 115 volts from PDU to Fans,through Rotation board; check tubethermal sensor2/ short circuit the sensor feedbackon rotation board connector andverify that error disappears. If no,replace rotation board

GE

ME

DIC

AL S

YS

TE

MS

DIA

GN

OS

TIC

SC

T H

ISP

EE

D S

ER

IES

2202125

X–R

AY

GE

NE

RA

TO

R2–28

RE

V 29

Illustratio

n 2–1

JED

I Visu

al Po

wer S

up

ply D

istribu

tion

OGP12V

NP/IF

DS 1

Gate command board

INVERTER. & LLC.circuit

–15v, +15v

DS 300

DC bus, 400 ... 800 V

*

*

EMC Flt.

PDU

DS 1, 2

”VCC”: +5v

–15v, +15vkV ctrl

K1

*

+ M –

DS 1*

3ph, 380 – 480 VAC

AC/DC

+ ––15v+15v

F 1

Heater board

Rotationboard

DS 3

DC bus,160V (120

to 200V

DS 3, 2, 1+5, –15, +15

DS 7 DS 6

CB1

DC bus, 400 ... 800 V

* *

Neon’sLEDs

*NE 1

–15v+15v

DS 2

115VAC

LVPS

Connection on Gantry base,slip ring, Gantry rotate

Pin1, 9

J2, 3


2202125


REV 29

2-6 WARNING ERRORS

Warning errors are the result of automated and regular background monitoring for either softwareevents or voltages threshold overtaking.

Those errors are merely for engineering usage and do not indicate any hardware error failure.

However, as they are logged into the Generator Err_log file, just as the previous list of error, they arelisted here to help error sorting out.

Should too many of them are seen when viewing error log, it is advised to report them via CQA, sincethe equipment is still operating.

10 Rotation Warn-ing

0151H CAN Domain command number error

0152H CAN Domain request with no transfer init0153H CAN Domain Toggle bit error0154H CAN Domain : less than 2 data to download0155H CAN Domain Abort received & applied0156H Bad index in config upload0157H Tube switch while rotor not off0158H Acceleration cmd while no tube selected0159H Acceleration cmd while database not OK0160H Database download while rotor speeding0161H Acceleration command not OK0162H Rotor acceleration while in error0163H No CAN message received within 4 secs0164H Rotation Inverter overcurrent (< 3 times)0199H Unknown rotation warning

20 Heater Warning 0251H Received command is not OK0252H Heater command not OK0253H No CAN message received within 4 secs0254H Heater inverter overcurrent (inverter1) (<3 times)0255H Filament open circuit (inverter1) (<3 times)0256H Heater Inverter short circuit (inverter1) (<3times)0257H Tube switch while filaments not OFF0258H CAN Domain command number error0259H CAN Domain request with no transfer init0260H CAN Domain Toggle bit error0261H CAN Domain : less than 2 data to download0262H CAN Domain Abort received & applied0263H Database download while heater not cut0299H Unknown heater warning


2202125


REV 29

25 Low VoltagePower Supply

Warnings

0550H No more warn +160V too low or too high

0555H Detected +160V too low0560H No more warn +15V too low or too high0561H Detected +15V too high0565H Detected +15V too low0570H No more warn –15V too low or too high0571H Detected –15V too strong0575H Detected –15V too weak0599H Unknown LVPS warning


1401H Saved RAM battery limit reached. Replace the kVboard.

This message is the result of a computation that ismade by the software based on the Date for a peri-

od of approximately 7 years


2202125


REV 29

2-7 OTHER FAILURES

Errorcode

Message / ex-planation

Potential cause Recommended action Troubleshooting guide

System GENERATORdoes not replyto the system

1. No power on Generator2. EMC filter3. AC/DC– Diode bridge4. Cable between AC/DC

and LVPS5. LVPS down6. CAN cable problem7. kV control8. CT interface9. Rotation board10. Heater board11. Inverter in short circuit12. Generator to system

cable

Perform the troubleshooting in the following way :1/kV control Leds S0–S7 are lit successively : re-fer to system communication errors (code 06xx H)2/Leds S0–S7 show a specific pattern : refer toPRD errors section3/Led RESET is lit : board is maintained in reseteither by the system or by a system I/F failure orkV control failure4/Led HALT is lit : replace kV control5/No Led is lit : verify that +5V on kV control board(J6, pin2).is present. If yes, replace kV control. Ifno :6/ verify if +15V/–15V is present (Leds DS1/DS2).If yes :verify that mains_drop line is not stopping the kVcontrol software (mains_drop active) :6–1/ check if DS1 LED on LVPS board is lit. If yes,replace LVPS board.6–2/ disconnect Heater board control bus cable.Check if kV control software starts. If yes, replaceHeater board.6–3/ Disconnect Rotation board control bus cableand connect it directly to LVPS board. Check if kVcontrol software starts. If yes, replace rotationboard.6–4/ else, replace kV control boardif no :7/ Verify if +15V/–15V is present on rotation board(DS1/DS2) and the 160V is present on the heaterboard (DS3). If yes : check the control bus cableto the kV control board. If no error, change the kVcontrol board. If no :8/ Verify if the LVPS DC input is right. If no, checkAC/DC fuse and input lineIf yes :9/disconnect all output cables from the LVPSboard. Verify the +15V/–15V/160V output. If right :reconnect each board successively to find the onestucking the 15V to ground. If wrong, replaceLVPS board


2202125


REV 29

3 phases CB1breaker tripsin PDU

1. Short circuit on Genera-tor :

IGBT in short circuitACDC or bridge rectifier in

short circuitEMC filter in short circuit

1/ Disconnect DC bus cables between AC/DC andinverter (on AC/DC side)2/ Check if these cables are in short circuit. If yes,replace inverterif no,3/ Disconnect AC line cables between EMC andAC/DC (on EMC side)4/ Check if these cables are in short circuit. If yes,replace AC/DC FRUif no :5/ Disconnect AC line input from EMC board.Check EMC for short circuit between phases. Ifshort circuit, replace EMC board.

Software orData base cor-rupt

1. After software download:–Incorrect or uncompleteddownload–Checksum problem

Retry download


2202125


REV 29

2-8 HEATING FUNCTION DIAGNOSTICS

Purpose :

The purpose of this test is to drive the heater inverter(s) on both filaments and all the tubes connectedto the generator in order to identify a faulty heater FRU or a wrong connection between heater board,HV Tank and tube(s). HV function and Rotation function are disabled during this test.

Pre–requisites :� kV control board alive and running : S0–S7 Leds are lit successively or a combination of them blink

� heater board alive and running : DS1 and DS2 Leds are lit successively

� heater DC supply present : DS3 Led is lit

Test type : No manual interaction

Sequence :

Once selected the tube the test is running on , start the diagnostic.

The following sequence runs on the small focus and then on the large focus :

� 5 seconds preheat

� 0,4s boost

� 5s heat ( focal spot max current – 1Amp )

There is 10s stop time between each focal spot run

During the test , the heater safeties are checked the same way than in application mode

Error codes reporting :

Refer to the troubleshooting table


2202125


REV 29

2-9 ROTATION FUNCTION DIAGNOSTICS

Purpose :

The purpose of this test is to drive the rotation inverter(s) in high speed mode (for applicationsupporting high speed mode ) and low speed mode on all the tubes connected to the generator inorder to identify a faulty rotation FRU or a faulty dephasing capacitors FRU or a wrong connectionbetween rotation board and tube. HV function and Heater function are disabled during this test.

Pre–requisites :� kV control board alive and running : S0–S7 Leds are lit successively or a combination of them blink

� rotation board alive and running : DS5 Led blinking

� rotation DC supply present : DS7 neon is lit

� cabling between rotation board and tube checked

Test type : No manual interaction, no loop on

Sequence :

Once selected the tube the test is running on , start the diagnostic.

The following sequence runs in low speed mode and then in high speed mode (if high speed modeallowed) :

� acceleration ( time depends on tube type )

� 2s run

� brake ( time depends on tube type )

There is 2s stop time between each speed mode.

During the test , the rotation safeties are checked the same way than in application mode

Error codes reporting :error code associated data conclusion

0103H0104H0105H0106H

associated data points only to highspeed mode

Power–off. Check if rotation board K2 relay is shortcircuiting the rotor capacitors. If yes replace the rota-tion board. If no replace the rotor capacitors

0103H0104H0105H0106H

associated data points to both highspeed and low speed mode

– Check presence of –15v (LED DS2 on rotationboard). If not, proceed to the recommended actiondescribed under error 70–0577– replace the rotation board

For the other error codes, refer to the troubleshooting table


2202125


REV 29

2-10 INVERTER GATE COMMAND DIAGNOSTICS

Purpose :

The purpose of this test is to verify that the HV power inverter drive is working properly. The IGBTsgate drive supply and the IGBTs gate drive is verified. At the same time verification is made that noinverter currents nor High voltage are measured. This test is performed without DC voltage applied tothe inverter so that no Xray is generated. Anode rotation and filament drive are not activated duringthis test.

Pre–requisites :� generator input line in an acceptable range ( 380V–10% to 480V+10% for 3–phase AC input )

� kV control board alive and running : S0–S7 Leds are lit successively or a combination of them blink

� inverter gate_cmd board DC supply present : DS300 neon is lit

Test type : Manual operation is required.

Sequence :

1/ Disconnect the 2 DC bus cables from the AC/DC board ( see LED Description )

2/ Power on the generator

3/ Push the TGP board reset switch, or OGP board reset switch.

4/ Verify that the DS1 neon on inverter dual snubbers board is not lit

5/ Start the diagnostic and verify :

� error reported on the operator console

� inverter gate_cmd board Leds DS101, DS 102, DS201, DS202 are lit : IGBTs gate drive supply isworking properly

6/ Press the exposure switch (10s exposure is taken after a 10 sec. delay).

7/ During the “exposure”, verify :

� error reported on the operator console

� inverter gate_cmd board Leds DS100 and DS200 are lit : IGBTs gate drive is working properly

8/ Release the exposure switch

9/ Power off the generator

10/ Reconnect the 2 DC bus cables from the AC/DC board (see LED Description )


2202125


REV 29

Error reporting :

Error ConclusionDS1 neon lit Check that DC bus cables have been removed

DS300 neon off Check the gate_cmd supply cable between AC/DC and gate_cmdboard

0301/0302/0303/0304/0309/0310/0311/0312/0313/0314/0319

/0323 (H)

Check that DC bus cables have been removed.If yes, replace kV control board

0320 if problem persists, replace Kv control board0501 kV control or inverter fault, replace inverter first0503 kV control or inverter fault, replace inverter first0504 kV control or inverter fault, replace inverter first

one ofDS101/DS102/DS201/DS202LEDs off while no error re-

ported

Replace inverter

DS100 and/or DS200 LEDsoff

Check cabling between kV control, HV Tank and gate_cmd board.If cabling is right, kV control or inverter fault, replace inverter first


2202125


REV 29

2-11 INVERTER IN SHORT CIRCUIT DIAGNOSTICS

Purpose :

The purpose of this test is to verify that the HV power inverter is working properly. The inverter iscommanded at a fixed frequency and is loaded with a short circuit. Verification is made that theinverter currents are correctly set. . At the same time verification is made that no High voltage ismeasured. This test is performed without connecting the HV Tank to the inverter so that no Xray isgenerated. Anode rotation and filament drive are not activated during this test.




� inverter dual snubber board DC supply present : DS1 neon is lit

� Inverter gate command diagnostic passed without failure


Sequence :

1/ Disconnect the HV Tank primary cables from the inverter (see the X–ray Generator Componentssection of X–ray Generator, of the Component Replacement manual).

Take care not to disconnect at the same time the parallel inductor cable which is tightened with the HVTank primary cables

Put the short circuit cable ( included in the first aid kit ) between the the two capacitors as shown :


2202125


REV 29

Check that the parallel inductor cable do not remain unscrewed.

2/ Power on the generator

3/ Push the TGP board reset switch, or OGP board reset switch.

4/ Verify that the DS1 neon on inverter dual snubbers board is lit

5/ Verify that the DS300 neon on inverter gate_cmd board is lit

6/ Start the diagnostic and verify that no error is reported on the operator console

7/ Press the exposure switch (500ms exposure is taken)

8/ Release the exposure switch

9/ verify error reported on the console

10/ After exiting the test, power off the generator

11/ Remove the short circuit cable, reconnect the HV Tank primary cables (see the X–ray GeneratorComponents section of X–ray Generator, of the Component Replacement manual).

Verify that the parallel inductor cable is connected.

Error reporting :error Conclusion

DS1 neon off Check that DC bus cables between AC/DC and inverterDS300 neon off Check the gate_cmd supply cable between AC/DC and gate_cmd

board0301/0302/0303/0304/0309/03

10/0319 (H)Check that HV Tank primary cables have been removed.

If yes, replace kV control board0311 No Ilp current detected. See note 20312 No Ilr current detected. See note 30313 replace kV control board0314 Ilr current resonant frequency is lower than expected. See note 40320 if problem persists, replace kV control board0323 Both Ilr and Ilp currents not detected. See note 10501 kV control or inverter can be faulty0503 kV control or inverter can be faulty0504 kV control or inverter can be faulty0505 Isolation fault between inverter components and ground. Check invert-

er inductors. If no faulty component, kV control or inverter can be faultynote 1 : Ilp and Ilr currents not detected

1/ Check the –15V (Led DS1) on kV control board (see LED Description).

If it is not lit, refer to “other failures” section. Else :

2/ Power off the generator. Wait until all neons are off

3/ Check that the currents transformers (capacitor set) to gate_cmd board cable is correctlyconnected. If yes :

4/ Check that the inverter inductors are correctly connected. If yes :

5/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctlyconnected.If yes, change the inverter6/ Reconnect all the cables


2202125


REV 29

note 2 : Ilp current not detected


2/ Check that the parallel inductor is correctly connected. If yes :

3/ Check that the parallel inductor impedance is 0 Ohms. If no : replace inverter. If yes :

4/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : change the capacitor set. Else :

5/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctlyconnected. If yes :

6/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 ofJ2 of HV Tank is 3,3Ohms. If no change the inverter. If yes :

7/ either the fault is at the capacitor set level or at the kV control level.

8/ Reconnect all the cables

note 3 : Ilr current not detected


2/ Check that the inductors are correctly connected. If yes :

3/ Disconnect the currents transformers to gate_cmd board cable. Check that the serial currenttransformer impedance is 0. If no : change capacitor set. Else :

4/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctlyconnected. If yes :

5/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 ofJ2 of HV Tank is 5 Ohms. If no change inverter. If yes :



note 4 : Ilr current resonant frequency is lower than expected


2/ Check that the inductors are correctly connected. If yes :

3/ Check that the resonant capacitor and filtering capacitors are not open. If they are : replace thecapacitor set. Else :

4/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : change the capacitor set. Else :




2202125


REV 29

2-12 NO LOAD HV DIAGNOSTICS

Purpose :

The purpose of this test is to verify that the HV power inverter and HV tank are working properly. The exposure istaken as in application mode except that no filament drive nor anode rotation is running. Verification is made thatthe inverter currents are correctly set and that kV regulation is operating properly. As no filament drive is applied,no XRays are generated. This test also allow to separate generator from HV cable or x–ray tube problem byrunning it with or without the HV cables plugged on the HV tank.






� Inverter in short circuit diagnostic passed without failure

� HV Receptacles must be filled with oil if HV cables are removed.


Sequence :1. Power on the generator

2. Push the TGP board reset switch, or OGP board reset switch.

3. Start the diagnostic and verify :

– error reported on the operator console

– inverter gate_cmd board Leds DS101, DS 102, DS201, DS202 are lit : IGBTs gate drive supplyis working properly

4. Select kV (default = 80) and exp.time (default = 1s).

5. Press the exposure switch

6. During the “exposure”, verify :

– error reported on the operator console

7. Release the exposure switch

8. Power off the generator

Error reporting :

See troubleshooting table


2202125


REV 29

SECTION 3 – ERRORS, DIAGNOSTICS &TROUBLESHOOTING (NP++, NP++ Twin)

NoteThis section is used for NP++ and NP++ Twin systems. However, for the p5.4 or later JEDI software,use Section 4 (ERRORS, DIAGNOSTICS & TROUBLESHOOTING (for p5.4 or later JEDI Soft-ware)). For NP, NP+, and NP+ Twin systems, use Section 2 (ERRORS, DIAGNOSTICS &TROUBLESHOOTING (NP, NP+, NP+ Twin)).

3-1 INTRODUCTION






S0.........................S7

⊗ ⊗ ⊗ ⊗ ⊗ ⊗ � ⊗

The 8 LED’s (S0...S7) are lit successively: the power up diagnostics are completed, kV control boardis up and running.

kV control board

��


2202125


REV 29

S0.....................S7

� ⊗ � ⊗ � ⊗ � ⊗


S0.........................S7

� � � ⊗ ⊗ � � �

S7, S6, S5 are lit along with either S0 or S1 or S2 (depending of the type of FPGA download error):FPGA download problem. An error code is logged. Refer to error code description.


⊗ ⊗ ⊗ ⊗ � ⊗ � ⊗


Heater board LED status: (See central listing)

After the power on diagnostics, heater board LEDs DS1 and DS2 are lit successively. Any differentstatus corresponds to an abnormal situation. An error code is logged. Refer to error code description.

Rotation board LED status: (See central listing)

After the power on diagnostics, rotation board LED DS5 is blinking. Any different status correspondsto an abnormal situation. An error code is logged. Refer to error code description.


2202125


REV 29

3-3 ERROR CODE LIST


simpli-fied

Description Error Error Description

errorcode

Class

code

30 Tube Spits 2 0301H Tube spit (kV+ and kV– dropped)2 0302H Tube spit (kV+ has dropped)2 0303H Tube spit (kV– has dropped)2 0304H Tube spit (kV regulation error)2 0305H FPGA problem (restarting safety signal)2 0324H Spits detected ((1:anode 2:cathode 4:both 8:kVre-

gul)

40 Rotation Error 4 0101H No CAN message received within 5 secs4 0102H Database not correct4 0103H Rotation current overload4 0104H Rotation Openload4 0105H Rotation Phases unbalanced4 0106H Rotation Phases error4 0107H Rotation Inverter permanent overcurrent4 0109H MAINS_DROP has failed4 0110H PRD error (Z3Z4=bitmap)4 0111H F0 main frequency problem4 0112H Rotor HW/FW Config error4 0149H Unknown rotation error

50 Heater Error 4 0201H No CAN message received within 5 secs4 0203H inverter overcurrent (HW detected)4 0204H open circuit (HW detected)4 0205H Inverter short circuit (HW detected)4 0206H Filament current too high4 0207H Filament too high for Boost4 0208H Filament too hot4 0210H Current over estimated (short circuit)4 0211H Current under estimated (open circuit)4 0212H MAINS_DROP detected4 0213H PRD error (Z3Z4=bitmap)4 0214H Stay too long in Boost4 0215H Filament selection error4 0216H current feedback not nul when inverter off4 0221H

0222H0223H0224H


4 0248H0249H

Unknown heater LF errorUnknown heater SF error


2202125


REV 29

simpli-fied


errorcode

Class

code

60 Exposure er-rors


3 0307H No kV Feedback on cathode3 0308H No kV Feedback on anode and cathode3 0309H kV detected during kV diag3 0310H kV max detected3 0311H ILP current not OK3 0312H ILR current not OK3 0313H ILR max current detected3 0314H ILR current timeout3 0316H Spit Max error3 0317H Spit Ratio error3 0318H kV did not reach 75% after 20ms3 0319H kV unbalanced detected3 0320H FPGA problem (safety signal)3 0401H No mA feedback3 0402H mA scale error2 0403H mA accuracy exceeded 5%3 0504H Inverter Gate Power Supply failed3 0801H Exposure backup mAs exceeded3 0802H Exposure backup time exceeded3 0803H Exp cmd while gene not ready3 1411H time counter error3 1407H mAs counter error3 1408H AEC counter error3 1409H mAs meter saturated3 0323H ILP and ILR current not OK3 1410H FPGA locked

Note:When 0313H, 0316H, or 0317H error occur few times a week, the X–ray tube must be earlyreplaced. This error reports spits occurrance or abnormal high pressure of X–ray tube. If thecurrent defective X–ray tube continues to be used, the High voltage cable between HEMIT andtube for NPV3 JEDI Generator or Inverter IGBT for NP JEDI might be damaged.

70 Power Supply 4 0501H DC bus out of rangeerrors 4 0503H Inverter Gate Power Supply error

4 0505H Mains power supply has dropped during exposure4 0506H DC bus 1 phase precharge error4 0507H DC bus 1 phase discharge error4 0577H Detected –15V too weak4 0573H Detected –15V too strong4 0567H Detected +15V too low4 0563H Detected +15V too high4 0557H Detected +160V too low4 0553H Detected +160V too high4 0549H Unknown LVPS error


2202125


REV 29

simpli-fied


errorcode

Class

code

80 Hardware error 4 0180H Rotation board communication problem4 0181H Rotation board has reset4 0280H Heater board communication problem4 0281H Heater board has reset4 0322H kV ref ADC / DAC failed4 0601H RTL error4 0602H External CAN bus off4 0902H tube Fan supply error4 1402H Internal CAN bus off4 1403H Connectic Fault4 1404H FPGA configuration problem4 1405H Tank sensor problem

90 Application 4 0701H Saved RAM checksum pberrors 4 0702H Software problem

4 0704H Rotation/Heater hold too long4 0705H System or database configuration error

100 Com errors 4 0603H Debug screen com error4 0604H Database download error4 0605H TAV com error4 0606H MPC/Madrid com error4 1301H AEC board com error


2202125


REV 29

simpli-fied


errorcode

Class

code

110 Thermal error 5 0804H Tank Thermal Error5 0903H Tube exceeded 70degC3 1454H Jedi inverter temperature too high5 0111H ��HEMIT Thermal error5 0805H Inverter Thermal Error


1 0151H CAN Domain command number error

1 0152H CAN Domain request with no transfer init1 0153H CAN Domain Toggle bit error1 0154H CAN Domain : less than 2 data to download1 0155H CAN Domain Abort received & applied1 0156H Bad index in config upload1 0157H Tube switch while Rotation not off1 0158H Acceleration cmd while no tube selected1 0159H Acceleration cmd while database not OK1 0160H Database download while Rotation speeding1 0161H Acceleration command not OK1 0162H Rotation acceleration while in error1 0163H No CAN message received within 4 secs1 0164H Rotation Inverter overcurrent (< 3 times)1 0199H Unknown rotation warning


2202125


REV 29simpli-

fiedDescription Error Error Description

errorcode

Class

code

20 Heater Warn-ing



25 Low Voltage 1 0570H No more warn –15V too lowPower Supply 1 0570H No more warn –15V too high

Warnings 1 0560H No more warn +15V too low1 0560H No more warn +15V too high1 0550H No more warn +160V too low1 0550H No more warn +160V too high1 0575H Detected –15V too weak1 0571H Detected –15V too strong1 0565H Detected +15V too low1 0561H Detected +15V too high1 0555H Detected +160V too low1 0551H Detected +160V too high1 0599H Unknown LVPS warning

27 Application 1 1401H Saved RAM battery limit reached. Replace thekV board.

warnings 1 0703H Watchdog reset has just occurred


2202125


REV 29

3-4 ERROR REPORTING

3-4-1 NP Generator Error Reporting

Np system only gets the simplified error code from the Jedi Generator.The Np system errorlog adds to the simplified error code the following information:


� system phase : state of the system when the error occurred. Take care, the system state is different ofthe Generator phase (refer to the Np system documentation)

� system time : date and time when the error occurred. Take care, the system time is different of the Genera-tor time

Whenever a Generator error is logged in the system errorlog file and displayed on the operator console, the Jedi error-log upload functionality is available to get more detailed information about the error.This function must be performed from the operator console.The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.Having these two information, look at the Jedi trouble–shooting table to find the FRU to replace.

Error codes can also be read by connecting the service laptop.

3-4-2 Tiger Generator Error Reporting (not for NP++ and Ebisu systems)

Tiger console only displays the simplified error code from the Jedi Generator.

Whenever a Generator error is displayed on the operator console, the Jedi errorlog upload functionality is availableto get more detailed information about the error.This function must be performed from the service laptop.The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.Having these two information, look at the Jedi trouble shooting table to find the FRU to replace.


2202125


REV 29

3-5 DIAGNOSTICS




The first part details errors, while the warning errors are listed in a second part of this chapter.

The table below provides guidelines to troubleshoot Generator problems based on error code.For each code, there is:

–Associated message and additional explanation related to the error occurrence.–List potential cause, in the order of expected probability. –Recommended action, with, in some cases, link to some more information as indicated where cases apply, suchas to run some specific diagnostics.

Codes are sorted by ascending order both for simplified code and error code. Refer to the theory of operation for error code structure.Information about associated data structure is located at the end of each error code subset whenever it applies.

Whenever wiring, cabling, LED check is mentioned in the recommended actions, refer to the central listing.

WARNING


2202125


REV 29

3-5-1-1 Errors


Class 2Errorcode

Message/explanation Potential cause Recommended action/Troubleshooting guide

30–0324H

data=4*



x–ray tube spit. –If too frequent, and varies with HV,replace x–ray tube.Run Open load kV test. (See diag-nostic section)

30–0324H

data=1*(seeNote)


Anode side


Usual in Performix tubes. If too fre-quent:–Check HV cables and contacts–Tube problem. (Anode side)–Check cable by interchangingthem.–Run Open load kV test. (See diag-nostic section)–Otherwise, HV tank.

30–0324H

data=2*(seeNote)


cathode side



Usual in Performix tubes. If too fre-quent:–Check HV cables and contacts–Tube problem. (Cathode side)–Check cable by interchangingthem.–Run Open load kV test. (See diag-nostic section)–Otherwise, HV tank

30–0324H

data=8*(seeNote)



(“smooth” means that therecovery of kV is slow)

1. smooth HV tube spits2. kV control board (HV

regulation problem)3. too much line imped-

ance (between thepower distributionboard and Jedi)

4. half of AC/DC capaci-tors open

5. Inverter (parallel induc-tor or filtering capaci-tors)

6. HV tank


30–0305H






–Do a power and Grounding Check.Verify cabling and contacts.–If permanent or too systematic, re-place kV control board.Report to engineering.


2202125


REV 29

* Note to the error 30 0324H:The generator sends only one message of error for all the spits (0324H) at the end of the exposure.

During the same exposure we may have different kind of spits.In the data of this error we can distinguish between the different spits:1: Spit in anode side2: Spit in cathode side4: Spit in both sides8: kV regulation error.

For a exposure with anode and both sides spit, the data will be “5”.

These data can be displayed in the OC in decimal or in hexadecimal base.

Spits code detailSee data (Z6[#H]) of XG error code 324H. Transfer #H to Binary data. Contents are as follows.

code bit3 bit2 bit1 bit0

KV RegulationError

Insert Spits Cathode sidearching

Anode side arch-ing

1 0 0 0 1

2 0 0 1 0

3 0 0 1 1

4 0 1 0 0

5 0 1 0 1

6 0 1 1 0

7 0 1 1 1

8 1 0 0 0

9 1 0 0 1

A 1 0 1 0

B 1 0 1 1

C 1 1 0 0

D 1 1 0 1

E 1 1 1 0

F 1 1 1 1

ex.)(0324H)Spits (1:anode 2: cathode 4: both 8: kVregul) (Z6[CH]:Z7[0H])

Z6[CH] –> C Hex –> 1100 Bin –> KV regulation + Insert


2202125


REV 29


Class 4Errorcode


40–0101H



communication

1. kV Control mainsoftware lost




40–0102H

Data base not correct.The firmware of therotation board has

detected that the database received from the kVcontrol board has wrong

data.


–Reload NVRam database.–ultimate is to replace Rotationboard.

40–0103H

Rotation current overloadRotation board has

detected Main or auxiliaryRotation current too high

compared to the max.Tube motor current.

1. Rotation boardRotation board capacitors2. Wrong data base

(improbable)

Check wiring from rotation board toHEMIT and HV from HEMIT totube.If no cabling problem, run Rotationdiagnostic.(See diagnostic section).

40–0104H


to the motor.


2. Incorrect wiring (Open)3. No DC bus on Rotation


capacitors(improbable)

Check wiring from rotation board toHEMIT and HV from HEMIT totube.If no cabling problem, run Rotationdiagnostic.(See diagnostic section)


2202125


REV 29

Class 4Errorcode


40–0105H

Rotation Phases unbal-ancedThe amplitude differenceof the current between


1. One Rotation wiremissing

2. Rotation boardRotation board phasecapacitors inverted orwrong value3. Wrong tube

configuration database

4. Tube problem (stator)5. HV cable between

HEMIT and tube

Check wiring from rotation board toHEMIT and HV from HEMIT totube.If no cabling problem, run Rotationdiagnostic.(See diagnostic section)

40–0106H

Rotation phase errorThe Rotation board hasdetected that the currentin the anode stator does

not show the correctphase shift between main

and auxiliary.

1. Rotation board2. Tube problem (stator)3. HV cable between

HEMIT and tube

– Check wiring from rotation boardto HEMIT and HV from HEMIT totube.Verify none is in short circuit.If no wiring problem, run Rotationdiagnostic. (See diagnostic section)


2202125


REV 29

Errorcode


40–0107H

Rotation Inverter perma-nent overcurrent

An overcurrent hasbeen detected and 3

restart have been triedunsuccessfully within a

single rotation state

1. Rotation board2. Tube stator winding

in short circuit –>HEMIT


–Check wiring from rotationboard to tube.–Troubleshoot tube windings–Replace Rotation board

40–0109H

MAINS_DROP has failedThe firmware of the

rotation board has de-tected the mains_dropsignal activation and

transmitted error to kVcontrol


contact in DC busbetween power unitand auxiliary unit

4. Rotation board

–Do a power and groundingcheck.–If systematic, replace Rotationboard

40–0110H

PRD error(Z3Z4=bitmap)Firmware checksum,

RAM test and EPLD ac-cess are performed at

power up or reset.

Rotation board Replace Rotation board.

40–0111H

F0 main frequency prob-lem.EPLD has not applied theinverter start command

Rotation board –Retry–Replace Rotation board.

40–0112H

Rotor HW/FW Config er-ror

Rotation board Download official data base (NPv3)If the problem persists, change rotor

40–0149H

Unknown rotation error.The main software re-

ceived an error from rota-tion board with no error

code associated

Software problem No action.

Associated data structure:PRD error:component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum


2202125


REV 29

Rotation database error:2 bytes data, each value points to a specific parameter found as being erroneous

Other errors:rotation state :0=inverter OFF1=acceleration 0 to low speed2=acceleration 0 to high speed3=acceleration low speed to high4=low speed run5=high speed run6=high speed to low speed brake7=brake reverse8=brake DC


2202125


REV 29

Filament Heater errors (Code 50)

Class 4Errorcode


50–0201H



of communication





50–0203H

Heater inverter permanentovercurrent.(SW limit)



in 100 ms


50–0204H



100 ms






50–0205H



100 ms


50–0206H

Filament current too highon inverter 1 for “Pre–Heat”This is the result of an in-tegrated value of the RMScurrent measurement onHeater board comparisonwith max. Tube value in

data base.


2. Heater board



2202125


REV 29

Errorcode


50–0207H

Filament current too highon inverter 1for “Boost”

Same as above


2. Heater board

Same as above

50–0208H

Filament current toohigh on inverter 1for“Heat”

Same as above

1. Tube data base orcalibration

2. Heater board

Same as above

50–0210H

Current over estimatedfork range

RMS filament currentmeasurement (every 0.5m sec.) on heater board

is too low

1. short circuit2. Heater board

–Switch on the other filament:if no error is reported, heaterboard is working properly. Checkheater board to HV Tank to tubeconnections. If OK, test withOhm–meter HV Tank heatertransformers (primary and secon-dary) and filament impedance.Order accordinglyIf the same error is reported,check the connections asabove. If all are right, changeheater board

50–0211H

Current under estimatedfork/ range

RMS filament currentmeasurement (every 0.5msec.) on heater board

is too high


Replace heater board

50– 0212H


error to kV control



4. Heater board

–Do a power and grounding check. –If systematic, replace heaterboard

50–0213H


reset.

Heater board Replace heater board.

50–0214H

Boost too long on inver-ter1.



Retry.It will probably be followed by anoth-er communication code.

50–0215H



selection



2202125


REV 29

Errorcode


50–0216H

Current feedback notnul when inverter OFF

Inverter current hasbeen measured whilethe inverter was not

commanded


50–0221H0222H0223H0224H






50–0248H

Unknown heater LF er-ror

The main software re-ceived an error from

heater board with no er-ror code associated

1. software problem No action

50–0249H

Unknown heater SF er-ror




Associated data structure:PRD error :component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum

Filament database error :2 bytes bitmap ( LSByte=small focus, MSByte=large focus)Each bit points to an erroneous parameter

other errors :1 byte bitmap with the following structure :

bit7 (MSB) bit6 bit5 bit4 bit3 bit2 bit1 bit0 (LSB)focus selected tube selected small focus state large focus state

0=small focus selected1=large focus selected





2202125


REV 29


Class 3Errorcode


60–0306H



probable)


60–0307H



probable)


60–0308H



cathode.



60–0309H




60–0310H


exposure


60–0311H



1. Inverter LC resonantcircuit (Inverter coilassy, capa inverterassy, current trans-formers.)



60–0312H




60–0313H

Inverter max. ILR cur-rent detected.

This is a hardwaredetection of maximumcurrent in serial reso-

nant circuit.

1 Tube (it can be cas-ing spits, errors0302H and 0303H)

2 HV tank3 kV control



2202125


REV 29

Class 3

Errorcode


60–0314H


pected


circuit.


(*)forNP

60–0316H





(*)forNP

60–0317H




60–0318H

kV did not reach 75% af-ter 20ms.Indicates that there wereno HV ON signal gener-ated for exposure time

count–up


60–0319H



HV tank Replace HV tank

60–0320H



source.


2. SW bug


60–0323H


the exposure

1. Inverter LC resonantcircuit. (Inverter coilassy, capa inverterassy, current trans-formers.)

2. InverterkV control board


60–0401H


tion:kV control has detected

no mA feedback 20 ms af-ter the beginning of the

exposure.


open)4. Cathode HV cable

short–circuited5. Misconnection be-

tween HV+ and HV–after a tank replace-ment

– Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is far out of range, (4.9 to5.1 Ohm, including DVM accuracy)replace HV Tank.– Verify filament impedance– Replace kV control board– After a tank replacement, verify

the HV cable connection.


2202125


REV 29

Errorcode


60–0402H

mA scale errormA has been measured to






– If the tube has just been replacedor installed, run many exposuresuntil the filament correction adjuststhe default filament drive values.– If the error occurs after a while ona system :Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is out of range, replace HVTank else replace kV control board

60–0403H

(Class2 error)




sure.


60–0504H





2. kV control board3. Generator input volt-

age too low or line im-pedance too high


NotonCT

60–0801H

Exposure backup mAs ex-ceededThe exposure command

last so long that the maxi-mum mAs allowed has

been reached

1. exposure commandline stuck to the activestate

60–0802H


the system (Backup time+ 5%.)

1. System2. System–Generator



–Retry, changing parameters andduration– disconnect system–Generatorcable in different places and checkexposure command line voltage

60–0803H

Exp cmd while gene notready.Generator received an ex-


1. Software bug/problem2. Cable / communication

problem3. External cause

(Spikes)

If problem is persistent, check heat-er, anode rotation and system toGenerator preparation command tofind the root cause for the Genera-tor not to be ready

60–1406H




2202125


REV 29

Errorcode


NotCT

60–1407H

mAs counter error.Error found in verifying thecounter normal operation.


NotCT

60–1408H

AEC counter error.If there is no AEC feed-back in AEC station expo-sure.

1. ION chamber2. AEC cable, connection3. AEC board

Run AEC diagnostics (See diagnos-tic section)

NotCT

60–1409H

mAs meter saturated.A check is done on mAscounter operation at thebeginning of exposure andfound the mAs meter withunrealistic value.

1. kV control Replace kV control

601411H

Time counter error Kv control Replace Kv control

60–1410H

FPGA locked.FPGA detected an errorand did not allow start ex-posure after exposurecommand signal was re-ceived.

1. software bug2. kV control

If persistent replace kV control

600323H

ILP and ILR current notOK





2202125


REV 29


Class 4Errorcode


70–0501H



2. One phase missing atGenerator input

–Check mains line 3 phases incom-ing voltage. –Verify line impedance if mains islow.–Verify DC Bus Voltage with a me-ter, if DC Bus is in range, replaceKV Control Board most probably.

70–0503H

Inverter Gate Power Sup-ply error (checked at prep)




70–0505H


unknown None

NotNP

70–0506H

DC bus 1 phase pre–charge error.

Found DC bus did notreach 400V after 10 sec.Charge relay is not acti-vated and pre–charge

relay drops.

1. Pre–charge resistor2. Relay3. ACDC module4. LVPS5. kV control board

WARNING!: Potential residualvoltage. Make sure all the NEONare off. Verify with a DVM, range400VDC that there is no voltageon the capacity bench before anyintervention –Verify LED on LVPS–Listen to relay clicking at poweron.–Check resistor

NotNP

70–0507H

DC bus 1 phase dischargeerror.

Found that DC bus volt-age is > 30 V before pre–

charge.

ACDC Replace ACDC module.


2202125


REV 29

Class 4Errorcode


70–0577H




cuit) (improbable)

Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check –15V on heater board (J3,pin3). If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin3) and(J1,pin3).If no continuity, replaceheater boardElse, disconnect the control buscable from the LVPS board andcheck the pin3 of the connector: ifvoltage is wrong replace LVPSboard. Else,check pin3 of the control bus cablewhen disconnecting the cable fromeach board successively to isolatethe board inducing a voltage drop

70–0573H




Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check –15V on heater board (J3,pin3). If OK, replace heater board.Else, disconnect the control buscable from the LVPS board andcheck the pin3 of the connector: ifvoltage is wrong replace LVPSboard.

70–0567H


board)


Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check 15V on heater board (J3,pin4). If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin4) and(J1,pin2).If no continuity, replaceheater boardElse, disconnect the control buscable from the LVPS board andcheck the pin2 of the connector : ifvoltage is wrong replace LVPSboard. Else,check pin2 of the control bus cablewhen disconnecting the cable fromeach board successively to isolatethe board inducing a voltage drop


2202125


REV 29

Errorcode


70–0563H




Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check 15V on heater board (J3,pin4). If OK, replace heater board.Else, disconnect the control buscable from the LVPS board andcheck the pin2 of the connector : ifvoltage is wrong replace LVPSboard.

70–0557H




Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check 160V on CF2/1 on heaterboard. If OK, replace heater boardElse, disconnect the CF2 cable andmeasure again on the LVPS side. Ifvoltage is wrong, replace LVPSboard.

70–0553H




70–0549H

Unknown LVPS errorThe main software re-ceived a LVPS error withno error code associated

1. Software problem No action


2202125


REV 29

Hardware errors (Code 80)

Class 4Errorcode


80–0180H




A/Check that rotation firmware isrunning (DS5 Led is blinking).If no :1/verify rotation board 5V : Led DS3is lit. If no : verify DS1/DS2 Leds : ifthey are lit, replace rotation board,else go to +/–15V errorstroubleshooting2/ verify that RESET Led is not lit. Ifit is lit, disconnect successively thecontrol bus cable from heater andkV control to find the board which isholding the reset line and replace it.If after disconnecting all the boards,the Led remains lit, replace rotationboard3/ else replace rotation boardB/Verify the flat cable between kVcontrol and auxiliary module is cor-rectly connected to the RotationboardC/else replace kV control

80–0181H

Rotation board has reset.kV control has detected


Rotation data base.




2202125


REV 29

Errorcode


80–0280H



A/Check that heater firmware is run-ning (DS1/2 Led are lit succes-sively).If no :1/verify heater board 5V : J3/pin2. Ifwrong : verify +15V/–15V (J3,pin3,4) : if they are right, changerotation board, else go to +/–15Verrors troubleshooting2/ verify that RST Led is not lit. If itis lit, disconnect successively thecontrol bus cable from LVPS to rota-tion and kV control to find the boardwhich is holding the reset line andreplace it. If after disconnecting allthe boards, the Led remains lit, re-place heater board3/ else replace heater boardB/Verify the flat cable between kVcontrol and auxiliary module is cor-rectly connected until the heaterboardC/else replace kV control board

80–0281H

Heater board has reset.KV control has detectedthe heater board has re-set. KV control will re-

load Rotation data base.


–Reinitialize system, retry.–If persistent, replace board orcheck power and grounding.

80–0322H

kV ref ADC / DAC failedkV control DAC and

ADC capability are per-manently tested for co-

herency.

KV control board Only if this error is repetitive andcomes alone (Not following othererrors), replace kV control board.

80–0601H








–Check communication cable–Check system communicationpower supply (if any)–Check system interface to kV con-trol flat cable–replace system interface board–replace kV control board


2202125


REV 29

Errorcode


80–0602H






80–0902H


fan

1. No 115V tube coolingsupply

2. Rotation board

–Check presence of the AC voltage(DS6 neon) at the input of the Rota-tion board.If ok, replace the rotation board

80–1402H



1. kV control2. Control bus cable3. Heater or Rotation

Check a wrong contact short circuiton CAN lines, pins 5 & 6, of thecontrol bus cable. Short circuit maybe either on Boards or connector/cable.If no fault detected, replace kV con-trol

80–1403H


Generator.



80–1404H




80–1405H


kV controlHV tank



2202125


REV 29

Application errors (Code 90)

Class 4Errorcode


90–0701H







0702H Software problem. 1. Software or DataBase problem.

2. kV control boardfailure.

–Reload the Data base–Reload the software and data-baseIf no improvement :–Replace kV control board

0704H Rotation/Heater hold toolong.

Will pop up if prepara-tion command from thesystem is maintainedlonger than 3 minutes.


0705H System or databaseconfiguration error The identifier of the sys-tem and the database arenot compatible

1. Database problem Download the Data base– Check system software release(OC)


2202125


REV 29


Class 4Errorcode


100–0603H


100–0604H


download



100–0605H

TAV communication error.Generator has detected acommunication problembetween the I/F and theservice laptop (When

Generator is controlled bythe laptop)


2. Cable problem

Retry

notNP

100–0606H

MPC/Madrid communica-tion error.No reply from the console.(This error message canbe seen using the service

laptop)

1. Cable, connectionproblem betweenGenerator and theconsole.

2. Interface board3. Console problem

–verify the console is powered .–Verify EMIT LED on the interfaceboard.–Verify cabling, connection.–Verify communication with theservice computer operates.

notNP

100–1301H

AEC board communica-tion error.

1. Verify cablesconnection

2. AEC board3. Interface board

–


2202125


REV 29


Class 5Errorcode


110–0804H


measurement hasreached 60 degree C


–Wait for error clearance–If persistent while HV Tank is cool :1/check LED DS1 on kV control (topand right of board). If it is off,change kV control2/check flat cable connection be-tween HV Tank and kV controlboard3/replace HV tank4/replace kV control

110–0903H





–Wait for error clearance –If persistent :1/Check tube cooling (Fan),troubleshoot 115 volts from PDU toFans, through Rotation board;check tube thermal sensor2/ short circuit the sensor feedbackon rotation board connector andverify that error disappears. If no,replace rotation board

110–1454H

Jedi inverter tempera-ture too high

1. Parameters kV, mAand time exceededallowed use

2. software bug

– Wait cooling time – change kv–ctrl board (iftrouble always present, report toservice)

110–0111H

HEMIT Thermal error 1. HEMIT tank2. DC Disch board (HE-

MIT assy)3. Rotation board

–Wait for error clearance–If persistent:1/ Check 2A fuse on DC Disch2/ Short circuit the sensor feed-back of the HEMIT. If problemdisappears, replace the HEMIT.2/ Replace DC–Disch3/ short circuit the sensor feedbackon rotation board connector andverify that error disappears. If no,replace rotation board

110–0805H

Inverter thermal error Software bug Download software and databaseagainIf the problem persists, changekV control


2202125


REV 29

3-6 WARNING ERRORS

Warning errors are the result of automated and regular background monitoring for either software events or voltagesthreshold overtaking.Those errors are merely for engineering usage and do not indicate any hardware error failure.

However, as they are logged into the Generator Err_log file, just as the previous list of error, they are listed here tohelp error sorting out.

Should too many of them are seen when viewing error log, it is advised to report them via CQA, since the equipmentis still operating.



0152H CAN Domain request with no transfer init0153H CAN Domain Toggle bit error0154H CAN Domain : less than 2 data to download0155H CAN Domain Abort received & applied0156H Bad index in config upload0157H Tube switch while Rotation not off0158H Acceleration cmd while no tube selected0159H Acceleration cmd while database not OK0160H Database download while Rotation speeding0161H Acceleration command not OK0162H Rotation acceleration while in error0163H No CAN message received within 4 secs0164H Rotation Inverter overcurrent (< 3 times)0199H Unknown rotation warning

20 Heater Warn-ing

0251H Received command is not OK

0252H Heater command not OK0253H No CAN message received within 4 secs0254H Heater inverter overcurrent (inverter1) (<3 times)0255H Filament open circuit (inverter1) (<3 times)0256H Heater Inverter short circuit (inverter1) (<3times)0257H Tube switch while filaments not OFF0258H CAN Domain command number error0259H CAN Domain request with no transfer init0260H CAN Domain Toggle bit error0261H CAN Domain : less than 2 data to download0262H CAN Domain Abort received & applied0263H Database download while heater not cut


2202125


REV 29

25 Low Voltage 0570H No more warn –15V too lowPower Supply 0570H No more warn –15V too high

Warnings 0560H No more warn +15V too low0560H No more warn +15V too high0550H No more warn +160V too low0550H No more warn +160V too high0575H Detected –15V too weak0571H Detected –15V too strong0565H Detected +15V too low0561H Detected +15V too high0555H Detected +160V too low0551H Detected +160V too high0599H Unknown LVPS warning




od of approximately 7 years0703H Watchdog reset has just occurred

– 1 if it often occurs, change kv–ctrl (if real re-set of the board)– 2 if it always occurs, report to service


2202125


REV 29

3-7 OTHER FAILURES

Errorcode

Message /explanation



1. No power on the Gener-ator.

2. EMC filter3. AC/DC– Diode bridge4. Cable between AC/DC

and LVPS5. LVPS down6. CAN cable problem7. kV control8. CT interface9. Rotation board10. Heater board11. Inverter in short cir-

cuit12. Generator to sys-

tem cable.

Perform the troubleshooting in the following way :1/kV control Leds S0–S7 are lit successively : re-fer to communication errors troubleshooting2/Leds S0–S7 show a specific pattern : refer toPRD errors section3/Led RESET is lit : board is maintained in reseteither by the system or by a system I/F failure orkV control failure4/Led HALT is lit : replace kV control5/No Led is lit : verify that +5V on kV control board(J6, pin2).is present. If yes, replace kV control. Ifno :6/ verify if +15V/–15V is present (Leds DS1/DS2).If yes, replace kV control. If no :7/ Verify if +15V/–15V is present on rotation board(DS1/DS2) and the 160V is present on the heaterboard (DS3). If yes : check the control bus cableto the kV control board. If no error, change the kVcontrol board. If no :8/ Verify if the LVPS DC input is right. If no, checkAC/DC fuse and input lineIf yes :9/disconnect all output cables from the LVPSboard. Verify the +15V/–15V/160V output. If right :reconnect each board successively to find the onestucking the 15V to ground. If wrong, replaceLVPS board


1. Short circuit on the Gen-erator :

n IGBT in short circuitn ACDC or bridge rectifier

in short circuitn EMC filter in short cir-

cuit

( 1/ Disconnect DC bus cables betweenAC/DC and inverter (on AC/DC side)2/ Check if these cables are in short circuit. If yes,replace inverterif no,3/ Disconnect AC line cables between EMC andAC/DC (on EMC side)4/ Check if these cables are in short circuit. If yes,replace AC/DC FRUif no :5/ Disconnect AC line input from EMC board.Check EMC for short circuit between phases. Ifshort circuit, replace EMC board.

Software orData basecorrupt


Retry download


2202125


REV 29

3-8 HEATING WITHOUT HV NOR ROTATION DIAGNOSTIC

Purpose :

The purpose of this test is to drive the heater inverter(s) on both filaments and all the tubes connected to the Generatorin order to identify a faulty heater FRU or a wrong connection between heater board, HV Tank and tube(s).

Pre–requisites :





Sequence :

Once selected the tube the test is running on , start the diagnostic.The following sequence runs on the small focus and then on the large focus :


� 0,4s boost


There is 10s stop time between each focal spot runDuring the test , the heater safeties are checked the same way than in application mode




2202125


REV 29

3-9 ROTATION WITHOUT HV NOR FILAMENT DIAGNOSTIC

Purpose :

The purpose of this test is to drive the rotation inverter(s) in high speed mode (for application supporting high speedmode ) and low speed mode on all the tubes connected to the Generator in order to identify a faulty rotation FRU ora faulty dephasing capacitors FRU or a wrong connection between rotation board, HEMIT and tube.

Pre–requisites:




� cabling between rotation board and tube checked

Test type: No manual interaction, no loop on

Sequence:

Once selected the tube the test is running on, start the diagnostic.The following sequence runs in low speed mode and then in high speed mode (if high speed mode allowed) :


� 2s run


There is 2s stop time between each speed mode.During the test , the rotation safeties are checked the same way than in application mode


2202125


REV 29

Error codes reporting :error code associated data conclusion

0103H0104H0105H0106H0107H


Power–off. Check cabling. If problem, replace therotation board. If the problem persists, replace theHEMIT tank. See note *

0109H0111H


Check cabling. If problem, replace the rotation board

0112H associated data points to both highspeed and low speed mode

Download official data base (NPv3). If the problempersists, change rotor.


*Note: Before replacing the rotation board, check the impedance of the primary and secondary of the HEMIT. Inorder to do a correct measure, check before the impedance of the cables of the multimeter.

• The impedance of the primary is measured between two pins of the connector J1 of the Bouchonboard in the HEMIT (3 measures). The value is low, between 0.8 ohm and 1.6 ohm.• If the impedance is too low (short –circuit) replace the HEMIT• If the impedance is too high (open circuit) replace the HEMIT

• The impedance of the secondary. Measure between two pins of the HV connector marked as “ST”.(large, small and common). For the three measures the value should be between 0.8 ohm and 1.6ohm.• If the impedance is too low (short –circuit) replace the HEMIT• If the impedance is too high (open circuit) replace the HEMIT


2202125


REV 29

3-10 HV POWER DIAGNOSTICS

3-10-1 Inverter Gate Command Diagnostic

Purpose :

The purpose of this test is to verify that the HV power inverter drive is working properly. The IGBTs gate drive supplyand the IGBTs gate drive is verified. At the same time verification is made that no inverter currents nor High voltageare measured. This test is performed without DC voltage applied to the inverter so that no Xray is generated. Anoderotation and filament drive are not activated during this test.

Pre–requisites :

� Generator input line in an acceptable range ( 380V–10% to 480V+10% for 3–phase AC input )




Sequence :1/ Disconnect the 2 DC bus cables from the AC/DC board ( see central listing )2/ Power on the Generator

3/ Push the TGP board reset switch, or OGP board reset switch.4/ Verify that the DS1 neon on inverter dual snubbers board is not lit5/ Start the diagnostic and verify :

– error reported on the operator console– inverter gate_cmd board Leds DS101, DS 102, DS201, DS202 are lit : IGBTs gate drive supply isworking properly

6/ Press the exposure switch (10s exposure is taken after 10 sec delay)7/ During the “exposure”, verify :

– error reported on the operator console– inverter gate_cmd board Leds DS100 and DS200 are lit : IGBTs gate drive is working properly

8/ Release the exposure switch9/ Power off the Generator10/ Reconnect the 2 DC bus cables from the AC/DC board (see central listing )


2202125


REV 29


DS1 neon lit Check that DC bus cables have been removedDS300 neon off Check the gate_cmd supply cable between AC/DC and gate_cmd

board0301/ 0302/ 0303/ 0304/ 0309/0310/ 0311/ 0312/ 0313/ 0314/

0319/ 0323 (H)



one ofDS101/DS102/DS201/DS202

Leds off while no errorreported

Replace inverter

DS100 and/or DS200 Ledsoff



2202125


REV 29

3-10-2 Inverter in Short Circuit Diagnostic

Purpose :

The purpose of this test is to verify that the HV power inverter is working properly. The inverter is commanded at afixed frequency and is loaded with a short circuit. Verification is made that the inverter currents are correctly set. . Atthe same time verification is made that no High voltage is measured. This test is performed without connecting theHV Tank to the inverter so that no Xray is generated. Anode rotation and filament drive are not activated during thistest.

Pre–requisites :








2202125


REV 29

Sequence :1/ Disconnect the HV Tank primary cables from the inverter ( see HV Tank D/R job card ).Take care not to disconnect at the same time the parallel inductor cable which is tightened with the HV Tankprimary cablesPut the short circuit cable (included in the first aid kit ) between the the two capacitors as shown (in red, thecable):

Parallelinduc-tor

1/ The parallel inductor must be connected2/ Power on the Generator3/ Push the TGP board reset switch, or OGP board reset switch.4/ Verify that the DS1 neon on inverter dual snubbers board is lit5/ Verify that the DS300 neon on inverter gate_cmd board is lit6/ Start the diagnostic and verify that no error is reported on the operator console7/ Press the exposure switch (500ms exposure is taken)8/ Release the exposure switch9/ verify error reported on the console10/ After exiting the test, power off the Generator11/ Remove the short circuit cable, reconnect the HV Tank primary cables ( see HV Tank D/R job card ).Verify that the parallel inductor cable is connected.


2202125


REV 29



board0301/ 0302/ 0303/ 0304/ 0309/

0310/ 0319 (H)Check that HV Tank primary cables have been removed.

If yes, replace kV control board0311 No Ilp current detected. See note 20312 No Ilr current detected. See note 30313 replace kV control board0314 Ilr current resonant frequency is lower than expected. See note 40320 if problem persists, replace kV control board0323 Both Ilr and Ilp currents not detected. See note 10501 kV control or inverter can be faulty0503 kV control or inverter can be faulty0504 kV control or inverter can be faulty0505 Isolation fault between inverter components and ground. Check

inverter inductors. If no faulty component, kV control or inverter can befaulty

Note 1 : Ilp and Ilr currents not detected1/ Check the –15V (Led DS1) on kV control board (see central listing).If it is not lit, refer to “other failures” section. Else :2/ Power off the Generator. Wait until all neons are off3/ Check that the currents transformers (capacitor set) to gate_cmd board cable is correctly connected. Ifyes :4/ Check that the inverter inductors are correctly connected. If yes :5/ Check that HV Tank is correctly connected to the capacitors set. If yes :6/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes, replace the inverter7/ Reconnect all the cables

Note 2 : Ilp current not detected1/ Power off the Generator. Wait until all neons are off2/ Check that the parallel inductor is correctly connected. If yes :3/ Check that the parallel inductor impedance is 0 Ohms. If no : replace inverter. If yes :4/ Check that inverter capacitors (capacitors set) are not broken. If yes, replace the capacitor set. Else :5/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : replace the capacitor set. Else :6/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes :7/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 of J2of HV Tank is 3,3Ohms. If no replace the inverter. If yes : replace kV control board.8/ Reconnect all the cables


2202125


REV 29

Note 3 : Ilr current not detected1/ Power off the Generator. Wait until all neons are off2/ Check that the inductors are correctly connected. If yes :3/ Disconnect the currents transformers to gate_cmd board cable. Check that the serial currenttransformer impedance is 0. If no : replace capacitor set. Else :4/ Check that inverter capacitors (capacitors set) are not broken. If yes, replace the capacitor set. Else :5/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes :6/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 of J2of HV Tank is 5 Ohms. If no replace inverter. If yes : replace kV control board.7/ Reconnect all the cables

Note 4 : Ilr current resonant frequency is lower than expected1/ Power off the Generator. Wait until all neons are off2/ Check that the inductors are correctly connected. If yes :3/ Check that inverter capacitors (capacitors set) are not broken. If yes : replace the capacitor set. Else :4/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : replace the capacitor set. Else : replace kV control board.5/ Reconnect all the cables

3-10-3 No Load HV Diagnostic without Anode Rotation nor Filament Heating

Purpose :

The purpose of this test is to verify that the HV power inverter and HV tank are working properly. The exposure is takenas in application mode except that no filament drive nor anode rotation is running. Verification is made that the invertercurrents are correctly set and that kV regulation is operating properly. As no filament drive is applied, no XRays aregenerated.This test also allow to separate Generator from HV cable or x–ray tube problem by running it with or without the HVcables plugged on the HV tank. (*)

Pre–requisites :







� (*) HV receptacles must be filled with oil if HV cables are removed.



2202125


REV 29

Sequence :1/ Power on the Generator2/ Push the TGP board reset switch, or OGP board reset switch.3/ Start the diagnostic and verify :


4/select kV (Default = 80 kV) and exposure time (Default = 1 sec.)5/ Press the exposure switch (500ms exposure is taken)6/ During the “exposure”, verify :

– error reported on the operator console7/ Release the exposure switch8/ Power off the Generator

Error reporting :



2202125


REV 29

3-11 TROUBLESHOOTING AIDS

Illustration 3–1 Generator Visual Power Supply Distribution

AC/DC

F1 �

DS 1


Gate command board DS 300 �

�

DS 1

EMC Flt.

� � �DS 3, 2, 1+5, –15, +15

RotorBoard

Heater board

DS 3�

DC bus, 400 ...800 V.

DC bus, 400 ...800 V.

LVPS

≅NE 1 �

�

DC bus,160V(120 to200 V).

+15 V– 15 V

�

kV ctrl“VCC“ + 5 V

+ –

+ M –

+15 V– 15 V

CB1

K1PDU

3ph, 380 – 480VAC115VAC

� �

–15v, +15v

�

+15 V– 15 V

OGP12V

NP I/F

DC Disch (HEMIT assy) � DS1

�DS2 �DS3 �DS4

DS 7 DS 6

�: Neon’s

�: LED’s

DS 1 , 2

DS 2


2202125


blank


2202125


REV 29

SECTION 4 – ERRORS, DIAGNOSTICS &TROUBLESHOOTING (for p5.4 or later JEDI Software)

NoteFor earlier than the p5.4 JEDI software, use Section 2 (ERRORS, DIAGNOSTICS &TROUBLESHOOTING (NP, NP+, NP+ Twin)) or Section 3 (ERRORS, DIAGNOSTICS &TROUBLESHOOTING (NP++, NP++ Twin)).

4-1 INTRODUCTION






S0.........................S7

⊗ ⊗ ⊗ ⊗ ⊗ ⊗ � ⊗

The 8 LED’s (S0...S7) are lit successively: the power up diagnostics are completed, kV control boardis up and running.

kV control board

��


2202125


REV 29

S0.....................S7

� ⊗ � ⊗ � ⊗ � ⊗


S0.........................S7

� � � ⊗ ⊗ � � �

S7, S6, S5 are lit along with either S0 or S1 or S2 (depending of the type of FPGA download error):FPGA download problem. An error code is logged. Refer to error code description.


⊗ ⊗ ⊗ ⊗ � ⊗ � ⊗


Heater board LED status: (See central listing)

After the power on diagnostics, heater board LEDs DS1 and DS2 are lit successively. Any differentstatus corresponds to an abnormal situation. An error code is logged. Refer to error code description.

Rotation board LED status: (See central listing)

After the power on diagnostics, rotation board LED DS5 is blinking. Any different status correspondsto an abnormal situation. An error code is logged. Refer to error code description.


2202125


REV 29

4-3 ERROR CODE LIST


simplifiederror code


Errorcode

Description

30 Tube Spits 2 0301H Tube spit (kV+ and kV– dropped)2 0302H Tube spit (kV+ has dropped)2 0303H Tube spit (kV– has dropped)2 0304H Tube spit (kV regulation error)2 0305H FPGA problem (restarting safety signal)2 0324H Spits detected ((1:anode 2:cathode 4:both 8:kVre-

gul)

40 Rotation Error 4 0101H No CAN message received within 5 secs4 0102H Database not correct4 0103H Rotation current overload4 0104H Rotation Openload4 0105H Rotation Phases unbalanced4 0106H Rotation Phases error4 0107H Rotation Inverter permanent overcurrent4 0109H MAINS_DROP has failed4 0110H PRD error (Z3Z4=bitmap)4 0111H F0 main frequency problem4 0112H Rotor HW/FW Config error4 0113H IUVW short circuit error4 0114H HV cable short circuit error4 0115H HV cable open error4 0149H Unknown rotation error

50 Heater Error 4 0201H No CAN message received within 5 secs4 0203H inverter overcurrent (HW detected)4 0204H open circuit (HW detected)4 0205H Inverter short circuit (HW detected)4 0206H Filament current too high4 0207H Filament too high for Boost4 0208H Filament too hot4 0210H Current over estimated (short circuit)4 0211H Current under estimated (open circuit)4 0212H MAINS_DROP detected4 0213H PRD error (Z3Z4=bitmap)4 0214H Stay too long in Boost4 0215H Filament selection error4 0216H current feedback not null when inverter off4 0221H

0222H0223H0224H


4 0248H0249H

Unknown heater LF errorUnknown heater SF error


2202125


REV 29



Errorcode

Description

60 Exposure er-rors


3 0307H No kV Feedback on cathode3 0308H No kV Feedback on anode and cathode3 0309H kV detected during kV diag3 0310H kV max detected3 0311H ILP current not OK3 0312H ILR current not OK3 0313H ILR max current detected3 0314H ILR current timeout3 0316H Spit Max error3 0317H Spit Ratio error3 0318H kV did not reach 75% after 20ms3 0319H kV unbalanced detected3 0320H FPGA problem (safety signal)3 0401H No mA feedback3 0402H mA scale error2 0403H mA accuracy exceeded 5%3 0504H Inverter Gate Power Supply failed3 0801H Exposure backup mAs exceeded3 0802H Exposure backup time exceeded3 0803H Exp cmd while gene not ready3 1411H time counter error3 1407H mAs counter error3 1408H AEC counter error3 1409H mAs meter saturated3 1410H FPGA locked3 0323H ILP and ILR current not OK3 0321H Spit retry failed (TD computing)3 1420H Tomo cut too early3 1421H Time cut instead tomo

Note:When 0313H, 0316H, or 0317H error occur few times a week, the X–ray tube must be early re-placed. This error reports spits occurrance or abnormal high pressure of X–ray tube. If the cur-rent defective X–ray tube continues to be used, the High voltage cable between HEMIT and tubefor NPV3 JEDI Generator or Inverter IGBT for NP JEDI might be damaged.

70 Power Supply 4 0501H DC bus out of rangeerrors 4 0503H Inverter Gate Power Supply error

4 0505H Mains power supply has dropped during exposure4 0506H DC bus 1 phase precharge error4 0507H DC bus 1 phase discharge error4 0577H Detected –15V too weak4 0573H Detected –15V too strong4 0567H Detected +15V too low4 0563H Detected +15V too high4 0557H Detected +160V too low4 0553H Detected +160V too high4 0549H Unknown LVPS error


2202125


REV 29



Errorcode

Description

80 Hardware error 4 0180H Rotation board communication problem4 0181H Rotation board has reset4 0280H Heater board communication problem4 0281H Heater board has reset4 0322H kV ref ADC / DAC failed4 0601H RTL error4 0602H External CAN bus off4 0902H tube Fan supply error4 1402H Internal CAN bus off4 1403H Connectic Fault4 1404H FPGA configuration problem4 1405H Tank sensor problem4 1406H Inverter sensor problem

90 Application 4 0701H Saved RAM checksum pberrors 4 0702H Software problem

4 0704H Rotation/Heater hold too long4 0705H System or database configuration error

100 Com errors 4 0603H Debug screen com error4 0604H Database download error4 0605H TAV com error4 0606H MPC/Madrid com error4 1301H AEC board com error

110 Thermal error 5 0804H Tank Thermal Error5 0805H Inverter Thermal Error5 0903H Tube exceeded 70degC5 0904H HEMIT thermal error3 1454H Jedi inverter temperature too high

120 Manipul. error 5 1500H Tomo brightness not good5 1501H Release exposure switch5 1502H AEC does not cut exposure


2202125


REV 29



Errorcode

Description


1 0151H CAN Domain command number error

1 0152H CAN Domain request with no transfer init1 0153H CAN Domain Toggle bit error1 0154H CAN Domain : less than 2 data to download1 0155H CAN Domain Abort received & applied1 0156H Bad index in config upload1 0157H Tube switch while Rotation not off1 0158H Acceleration cmd while no tube selected1 0159H Acceleration cmd while database not OK1 0160H Database download while Rotation speeding1 0161H Acceleration command not OK1 0162H Rotation acceleration while in error1 0163H No CAN message received within 4 secs1 0164H Rotation Inverter overcurrent (< 3 times)1 0199H Unknown rotation warning

20 Heater Warn-ing




2202125


REV 29



Errorcode

Description

25 Low Voltage 1 0570H No more warn –15V too lowPower Supply 1 0570H No more warn –15V too high

Warnings 1 0560H No more warn +15V too low1 0560H No more warn +15V too high1 0550H No more warn +160V too low1 0550H No more warn +160V too high1 0575H Detected –15V too weak1 0571H Detected –15V too strong1 0565H Detected +15V too low1 0561H Detected +15V too high1 0555H Detected +160V too low1 0551H Detected +160V too high1 0599H Unknown LVPS warning

27 Application 1 1401H Saved RAM battery limit reached. Replace thekV board.

warnings 1 0703H Watchdog reset has just occurred


2202125


REV 29

4-4 ERROR REPORTING

4-4-1 NP Generator Error Reporting

Np system only gets the simplified error code from the Jedi Generator.The Np system errorlog adds to the simplified error code the following information:


� system phase : state of the system when the error occurred. Take care, the system state is different ofthe Generator phase (refer to the Np system documentation)

� system time : date and time when the error occurred. Take care, the system time is different of the Genera-tor time

Whenever a Generator error is logged in the system errorlog file and displayed on the operator console, the Jedi error-log upload functionality is available to get more detailed information about the error.This function must be performed from the operator console.The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.Having these two information, look at the Jedi trouble–shooting table to find the FRU to replace.

Error codes can also be read by connecting the service laptop.

4-4-2 Tiger Generator Error Reporting (not for NP++ and Twin systems)

Tiger console only displays the simplified error code from the Jedi Generator.

Whenever a Generator error is displayed on the operator console, the Jedi errorlog upload functionality is availableto get more detailed information about the error.This function must be performed from the service laptop.The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.Having these two information, look at the Jedi trouble shooting table to find the FRU to replace.


2202125


REV 29

4-5 DIAGNOSTICS




The first part details errors, while the warning errors are listed in a second part of this chapter.

The table below provides guidelines to troubleshoot Generator problems based on error code.For each code, there is:

–Associated message and additional explanation related to the error occurrence.–List potential cause, in the order of expected probability. –Recommended action, with, in some cases, link to some more information as indicated where cases apply, suchas to run some specific diagnostics.

Codes are sorted by ascending order both for simplified code and error code. Refer to the theory of operation for error code structure.Information about associated data structure is located at the end of each error code subset whenever it applies.

Whenever wiring, cabling, LED check is mentioned in the recommended actions, refer to the central listing.

WARNING


2202125


REV 29

4-5-1-1 Errors


Class 2Errorcode


30–0324H

data=4*



x–ray tube spit. Usual in tubes. If too frequent, andvaries with HV: replace x–ray tube.– Run open load kV test. (See diag-nostic section)

30–0324H

data=1*(seeNote)


Anode side


If too frequent:– Check HV cables and contacts– Tube problem. (Anode side)– Check cable by interchangingthem.– Run Open load kV test. (See diag-nostic section)– Otherwise, HV tank.

30–0324H

data=2*(seeNote)


cathode side



If too frequent:– Check HV cables and contacts– Tube problem. (Cathode side)– Check cable by interchangingthem.– Run Open load kV test. (See diag-nostic section)– Otherwise, HV tank

30–0324H

data=8*(seeNote)



1. smooth HV tube spits2. kV control board (HV

regulation problem)3. too much line imped-

ance4. half of AC/DC capaci-

tors open5. Inverter (parallel induc-

tor or filtering capaci-tors)

6. HV tank


30–0305H






–Do a power and Grounding Check.Verify cabling and contacts.–If permanent or too systematic, re-place kV control board.Report to engineering.


2202125


REV 29

* Note to the error 30 0324H:The generator sends only one message of error for all the spits (0324H) at the end of the exposure.

During the same exposure we may have different kind of spits.In the data of this error we can distinguish between the different spits:1: Spit in anode side2: Spit in cathode side4: Spit in both sides8: kV regulation error.

For a exposure with anode and both sides spit, the data will be “5”.

These data can be displayed in the OC in decimal or in hexadecimal base.Spits code detailSee data (Z6[#H]) of XG error code 324H. Transfer #H to Binary data. Contents are as follows.

code bit3 bit2 bit1 bit0

KV RegulationError

Insert Spits Cathode sidearching

Anode side arch-ing

1 0 0 0 1

2 0 0 1 0

3 0 0 1 1

4 0 1 0 0

5 0 1 0 1

6 0 1 1 0

7 0 1 1 1

8 1 0 0 0

9 1 0 0 1

A 1 0 1 0

B 1 0 1 1

C 1 1 0 0

D 1 1 0 1

E 1 1 1 0

F 1 1 1 1

ex.)(0324H)Spits (1:anode 2: cathode 4: both 8: kVregul) (Z6[CH]:Z7[0H])

Z6[CH] –> C Hex –> 1100 Bin –> KV regulation + Insert


2202125


REV 29


Class 4Errorcode


40–0101H



communication





40–0102H

Data base not correct.The firmware of therotation board has

detected that the database received from the kVcontrol board has wrong

data.


–Reload NVRam database.–ultimate is to replace Rotationboard.

40–0103H

Rotation current overloadRotation board has

detected Main or auxiliaryRotation current too high

compared to the max.Tube motor current.


capacitor shortcircuited (not forNP++)

3. Wrong data base(improbable)

Check wiring from rotation board totube (cable from rotation board toHEMIT and HV cable from HEMITto tube for NP++).If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shiftcapacitors (not for NP++).(Seediagnostic section).

40–0104H


to the motor.


2. Incorrect wiring (Open)3. No DC bus on Rotation


capacitor notconnected (not forNP++ and improbable)

Check wiring from rotation board totube (cable from rotation board toHEMIT and HV cable from HEMITto tube for NP++. See Rotationdiagnosis).Check DC bus cables from AC–DCboard to rotation boardCheck that phases capacitors arecorrectly connected (not for NP++)If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shiftcapacitors (not for NP++).(Seediagnostic section).


2202125


REV 29

Class 4Errorcode


40–0105H

Rotation Phases unbal-ancedThe amplitude differenceof the current between


1. One Rotation wiremissing


capacitors inverted orwrong value or notconnected (not forNP++)

4. Wrong tubeconfiguration database

5. Tube problem (stator)6. HV cable between

HEMIT and tube (onlyfor NP++)

Check wiring from rotation board totube (cable from rotation board toHEMIT and HV cable from HEMITto tube for NP++. See Rotationdiagnosis).Check that phases capacitors arecorrectly connected (not for NP++)If no cabling problem, run Rotationdiagnostic to differentiate betweenrotation board and phase shiftcapacitors (not for NP++).(Seediagnostic section).

40–0106H

Rotation phase errorThe Rotation board hasdetected that the currentin the anode stator does

not show the correctphase shift between main

and auxiliary.

1. Rotation board2. Tube problem (stator)3. HV cable between

HEMIT and tube (onlyfor NP++)

4. Rotation board phasecapacitors inverted orwrong value (not forNP++)

Check wiring from rotation board totube (cable from rotation board toHEMIT and HV cable from HEMITto tube for NP++).Check that phases capacitors arecorrectly connected (not for NP++)Verify none is in short circuit.If no wiring problem, run Rotationdiagnostic. (See diagnostic section)


2202125


REV 29

Errorcode


40–0107H

Rotation Inverter perma-nent overcurrent

An overcurrent hasbeen detected and 3

restart have been triedunsuccessfully within a

single rotation state

1. Rotation board2. Tube stator winding

in short circuit –>cable (NP) or HEMIT(only for NP++)


–Check wiring from rotationboard to tube.–Troubleshoot tube windings–Replace Rotation board

40–0109H

MAINS_DROP has failedThe firmware of the

rotation board has de-tected the mains_dropsignal activation and

transmitted error to kVcontrol



4. Rotation board

–Do a power and groundingcheck.–If systematic, replace Rotationboard

40–0110H

PRD error(Z3Z4=bitmap)Firmware checksum,

RAM test and EPLD ac-cess are performed at

power up or reset.

Rotation board Replace Rotation board.

40–0111H

F0 main frequency prob-lem.EPLD has not applied theinverter start command

Rotation board –Retry–Replace Rotation board.

40–0112H

Rotor HW/FW Config er-ror

Rotation board Download official data baseIf the problem persists, change rotor

NP++ 40–0113H

IUVW short circuit error(only for NP++)

IUVW signal shortcircuitedon rotation board

– Retry– Change rotation board

NP++ 40–0114H

HV cable short circuit er-ror (only for NP++)

Short circuit on:– Tube stator– Hemit secondary– Anode HV cableOr bearings of tube bro-ken

– Check HV cable impedance– Change tube– Change Hemit

NP++ 40–0115H

HV cable open error (onlyfor NP++)

Open circuit on:– Tube stator– Hemit secondary– Anode HV cable

– Check HV cable connection andimpedance. Replace if open.– Check tube stator impedance– Check Hemit secondaryimpedance. Replace HEMIT if open.

40–0149H

Unknown rotation error.The main software re-

ceived an error from rota-tion board with no error

code associated

Software problem No action.


2202125


REV 29

Associated data structure:PRD error:component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum

Rotation database error:2 bytes data, each value points to a specific parameter found as being erroneous

Other errors:rotation state :0=inverter OFF1=acceleration 0 to low speed2=acceleration 0 to high speed3=acceleration low speed to high4=low speed run5=high speed run6=high speed to low speed brake7=brake reverse8=brake DC


2202125


REV 29

Filament Heater errors (Code 50)

Class 4Errorcode


50–0201H



of communication





50–0203H

Heater inverter permanentovercurrent.(SW limit)



in 100 ms


50–0204H



100 ms






50–0205H



100 ms


50–0206H

Filament current too highon inverter 1 for “Pre–Heat”This is the result of an in-tegrated value of the RMScurrent measurement onHeater board comparisonwith max. Tube value in

data base.


2. Heater board



2202125


REV 29

Errorcode


50–0207H

Filament current too highon inverter 1for “Boost”

Same as above


2. Heater board

Same as above

50–0208H

Filament current toohigh on inverter 1for“Heat”

Same as above

1. Tube data base orcalibration

2. Heater board

Same as above

50–0210H

Current over estimatedfork range

RMS filament currentmeasurement (every 0.5m sec.) on heater board

is too low

1. short circuit2. Heater board

–Switch on the other filament:if no error is reported, heaterboard is working properly. Checkheater board to HV Tank to tubeconnections. If OK, test withOhm–meter HV Tank heatertransformers (primary and secon-dary) and filament impedance.Order accordinglyIf the same error is reported,check the connections asabove. If all are right, changeheater board

50–0211H

Current under estimatedfork/ range

RMS filament currentmeasurement (every 0.5msec.) on heater board

is too high


Replace heater board

50– 0212H


error to kV control



4. Heater board

–Do a power and grounding check. –If systematic, replace heaterboard

50–0213H


reset.

Heater board Replace heater board.

50–0214H

Boost too long on inver-ter1.



Retry.It will probably be followed by anoth-er communication code.

50–0215H



selection



2202125


REV 29

Errorcode


50–0216H

Current feedback notnull when inverter OFF

Inverter current hasbeen measured whilethe inverter was not

commanded


50–0221H0222H0223H0224H






50–0248H

Unknown heater LF er-ror




50–0249H

Unknown heater SF er-ror




Associated data structure:PRD error :component failure :0001H=RAM0002H=RAM stack0200H=EPLD8000H=program checksum

Filament database error :2 bytes bitmap ( LSByte=small focus, MSByte=large focus)Each bit points to an erroneous parameter

other errors :1 byte bitmap with the following structure :

bit7 (MSB) bit6 bit5 bit4 bit3 bit2 bit1 bit0 (LSB)focus selected tube selected small focus state large focus state

0=small focus selected1=large focus selected





2202125


REV 29


Class 3Errorcode


60–0306H



probable)


60–0307H



probable)


60–0308H



cathode.



60–0309H




60–0310H


exposure


60–0311H






60–0312H




60–0313H

Inverter max. ILR cur-rent detected.

This is a hardwaredetection of maximumcurrent in serial reso-

nant circuit.

1 Tube (it can be cas-ing spits, error 0324Hdata=1 or 2)

2 HV tank3 kV control4 inv LC resonant cir-

cuit

run HV power diagnostics in or-der to determine if it is associat-ed to tubeIf during the test, you have kV un-balance, see error 0319H.


2202125


REV 29

Class 3Errorcode


60–0314H


pected


circuit.


(*)forNP

60–0316H




reasonably x–ray tube –Try again at various kV/mA to con-fine problem.– if it is associated to kV regul outspit detection, check mains inputvoltage connection–Troubleshoot HV section. (x–raytube, cable, HV tank)–Diagnose based on tube history.

(*)forNP

60–0317H



reasonably x–ray tube –Try again at various kV/mA to con-fine problem.– if it is associated to kV regul outspit detection, check mains inputvoltage connection–Troubleshoot HV section. (x–raytube, cable, HV tank)–Diagnose based on tube history.

60–0318H

kV did not reach 75% af-ter 20ms.Indicates that there wereno HV ON signal gener-ated for exposure time

count–up


60–0319H



HV tank –Try again at various mA to confirmproblem.Replace HV tank

60–0320H



source.


2. SW bug


60–0323H


the exposure

1. Inverter LC resonantcircuit. (Inverter coilassy, capa inverterassy, current trans-formers.)

2. Inverter3. kV control board



2202125


REV 29

Errorcode


60–0401H


tion:kV control has detected

no mA feedback 20 ms af-ter the beginning of the

exposure.


open or short circuited)9. Cathode HV cable

short–circuited10.Misconnection be-

tween HV+ and HV–after a tank replace-ment

11.heater function

– Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is far out of range, (4.9 to5.1 Ohm, including DVM accuracy)replace HV Tank.– Verify filament impedance– Verify filament drive (heater)– Replace kV control board– After a tank replacement, verify

the HV cable connection.60–040

2HmA scale errormA has been measured to






– If the tube has just been replacedor installed, run many exposuresuntil the filament correction adjuststhe default filament drive values.– If the error occurs after a while ona system :Disconnect HV Tank to kV controlflat cable and verify with an Ohm–meter the accuracy of the 5 Ohmsresistor on the HV Tank mA mea-sure. If it is out of range, replace HVTank else replace kV control board

60–0403H

(Class2 error)




sure.


60–0504H





5. kV control board6. Generator input volt-

age too low or line im-pedance too high


NotonCT

60–0801H

Exposure backup mAs ex-ceededThe exposure command

last so long that the maxi-mum mAs allowed has

been reached

2. exposure commandline stuck to the activestate

60–0802H


the system (Backup time+ 5%.)

4. System5. System–Generator



–Retry, changing parameters andduration– disconnect system–Generatorcable in different places and checkexposure command line voltage


2202125


REV 29

Errorcode


60–0803H

Exp cmd while gene notready.Generator received an ex-


1. Software bug/problem2. Cable / communication

problem3. External cause

(Spikes)

If problem is persistent, check heat-er, anode rotation and system toGenerator preparation command tofind the root cause for the Genera-tor not to be ready

60–1411H



NotCT

60–1407H

mAs counter error.Error found in verifying thecounter normal operation.


NotCT

60–1408H

AEC counter error.If there is no AEC feed-back in AEC station expo-sure.

1. ION chamber2. AEC cable, connection3. AEC board

Run AEC diagnostics (See diagnos-tic section)

NotCT

60–1409H

mAs meter saturated.A check is done on mAscounter operation at thebeginning of exposure andfound the mAs meter withunrealistic value.

1. kV control Replace kV control

60–1410H

FPGA locked.FPGA detected an errorand did not allow start ex-posure after exposurecommand signal was re-ceived.

1. software bug2. kV control

If persistent replace kV control

forNP

600321H

Spit retry failed (only forNP/NP+)

1. Tube (most probable)2. HV cables3. HV tank

If this error is associated to spitdetection on anode side, same time,(0324h data 1), change tubeelse run no load HV diagnostics.

600323H

ILP and ILR current notOK




NotNP

601420H

Tomo cut too early (onlyfor RAD)

Positioner cut exposurebefore programmed time

positioner trouble

NotNP

601421H

Time cut instead tomo(only for RAD)

Positioner does not cutexposure

positioner trouble


2202125


REV 29


Class 4Errorcode


70–0501H



2. One phase missing atGenerator input

–Check mains line 3 phases incom-ing voltage. –Verify line impedance if mains islow.–Verify DC Bus Voltage with a me-ter, if DC Bus is in range, replaceKV Control Board most probably.

70–0503H

Inverter Gate Power Sup-ply error (checked at prep)




70–0505H


unknown None

NotNP

70–0506H

DC bus 1 phase pre–charge error.

Found DC bus did notreach 400V after 10 sec.Charge relay is not acti-vated and pre–charge

relay drops.

1. Pre–charge resistor2. Relay3. ACDC module4. LVPS5. kV control board

WARNING!: Potential residualvoltage. Make sure all the NEONare off. Verify with a DVM, range400VDC that there is no voltageon the capacity bench before anyintervention –Verify LED on LVPS–Listen to relay clicking at poweron.–Check resistor

NotNP

70–0507H

DC bus 1 phase dischargeerror.

Found that DC bus volt-age is > 30 V before pre–

charge.

ACDC Replace ACDC module.


2202125


REV 29

Class 4Errorcode


70–0577H




cuit) (improbable)

Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check –15V on heater board (J3,pin3). If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin3) and(J1,pin3).If no continuity, replaceheater boardElse, disconnect the control buscable from the LVPS board andcheck the pin3 of the connector: ifvoltage is wrong replace LVPSboard. Else,check pin3 of the control bus cablewhen disconnecting the cable fromeach board successively to isolatethe board inducing a voltage drop

70–0573H




Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check –15V on heater board (J3,pin3). If OK, replace heater board.Else, disconnect the control buscable from the LVPS board andcheck the pin3 of the connector: ifvoltage is wrong replace LVPSboard.

70–0567H


board)


Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check 15V on heater board (J3,pin4). If OK, replace heater board.If voltage=0, check the continuity onheater board between (J3, pin4) and(J1,pin2).If no continuity, replaceheater boardElse, disconnect the control buscable from the LVPS board andcheck the pin2 of the connector : ifvoltage is wrong replace LVPSboard. Else,check pin2 of the control bus cablewhen disconnecting the cable fromeach board successively to isolatethe board inducing a voltage drop


2202125


REV 29

Errorcode


70–0563H




Verify that the DC bus on LVPSboard is in an acceptable range(CF1/CF2) If no, verify AC/DC fuseand AC input voltage.Check 15V on heater board (J3,pin4). If OK, replace heater board.Else, disconnect the control buscable from the LVPS board andcheck the pin2 of the connector : ifvoltage is wrong replace LVPSboard.

70–0557H





70–0553H




70–0549H

Unknown LVPS errorThe main software re-ceived a LVPS error withno error code associated

1. Software problem No action


2202125


REV 29

Hardware errors (Code 80)

Class 4Errorcode


80–0180H




A/Check that rotation firmware isrunning (DS5 Led is blinking).If no :1/verify rotation board 5V : Led DS3is lit. If no : verify DS1/DS2 Leds : ifthey are lit, replace rotation board,else go to +/–15V errorstroubleshooting2/ verify that RESET Led is not lit. Ifit is lit, disconnect successively thecontrol bus cable from heater andkV control to find the board which isholding the reset line and replace it.If after disconnecting all the boards,the Led remains lit, replace rotationboard3/ else replace rotation boardB/Verify the flat cable between kVcontrol and auxiliary module is cor-rectly connected to the RotationboardC/else replace kV control

80–0181H

Rotation board has reset.kV control has detected


Rotation data base.




2202125


REV 29

Errorcode


80–0280H



A/Check that heater firmware is run-ning (DS1/2 Led are lit succes-sively).If no :1/verify heater board 5V : J3/pin2. Ifwrong : verify +15V/–15V (J3,pin3,4) : if they are right, changerotation board, else go to +/–15Verrors troubleshooting2/ verify that RST Led is not lit. If itis lit, disconnect successively thecontrol bus cable from LVPS to rota-tion and kV control to find the boardwhich is holding the reset line andreplace it. If after disconnecting allthe boards, the Led remains lit, re-place heater board3/ else replace heater boardB/Verify the flat cable between kVcontrol and auxiliary module is cor-rectly connected until the heaterboardC/else replace kV control board

80–0281H

Heater board has reset.KV control has detectedthe heater board has re-set. KV control will re-

load Rotation data base.


–Reinitialize system, retry.–If persistent, replace board orcheck power and grounding.

80–0322H

kV ref ADC / DAC failedkV control DAC and

ADC capability are per-manently tested for co-

herency.

KV control board Only if this error is repetitive andcomes alone (Not following othererrors), replace kV control board.

80–0601H










2202125


REV 29

Errorcode


80–0602H






80–0902H


fan

1. No 115V tube coolingsupply

2. Rotation board

–Check presence of the AC voltage(DS6 neon) at the input of the Rota-tion board.If ok, replace the rotation board

80–1402H



1. kV control2. Control bus cable3. Heater or Rotation

Check a wrong contact short circuiton CAN lines, pins 5 & 6, of thecontrol bus cable. Short circuit maybe either on Boards or connector/cable.If no fault detected, replace kV con-trol

80–1403H


Generator.



80–1404H




80–1405H


kV controlHV tank


80–1406H

Inverter temperature sen-sor problem (not imple-mented).

kV control Replace kV control


2202125


REV 29

Application errors (Code 90)

Class 4Errorcode


90–0701H







0702H Software problem. 1. Software or DataBase problem.

2. kV control boardfailure.

–Reload the Data base–Reload the software and data-baseIf no improvement :–Replace kV control board

0704H Rotation/Heater hold toolong.

Will pop up if prepara-tion command from thesystem is maintainedlonger than 3 minutes.


0705H System or databaseconfiguration error The identifier of the sys-tem and the database arenot compatible

1. Database problem Download the Data base– Check system software release(OC)


2202125


REV 29


Class 4Errorcode


100–0603H


100–0604H


download



100–0605H

TAV communication error.Generator has detected acommunication problembetween the I/F and theservice laptop (When

Generator is controlled bythe laptop)


2. Cable problem

Retry

notNP

100–0606H

MPC/Madrid communica-tion error.No reply from the console.(This error message canbe seen using the service

laptop)

1. Cable, connectionproblem betweenGenerator and theconsole.

2. Interface board3. Console problem

–verify the console is powered .–Verify EMIT LED on the interfaceboard.–Verify cabling, connection.–Verify communication with theservice computer operates.

notNP

100–1301H

AEC board communica-tion error.

1. Verify cablesconnection

2. AEC board3. Interface board

–


2202125


REV 29


Class 5Errorcode


110–0804H


measurement hasreached 60 degree C for

Np/Np+ or 66 degree c forNp++


–Wait for error clearance–If persistent while HV Tank is cool :1/check LED DS1 on kV control (topand right of board). If it is off,change kV control2/check flat cable connection be-tween HV Tank and kV controlboard3/replace HV tank4/replace kV control

110–0805H

Inverter thermal error Software bug Download software and databaseagainIf the problem persists, changekV control

110–0903H





–Wait for error clearance –If persistent :1/Check tube cooling (Fan),troubleshoot 115 volts from PDU toFans, through Rotation board;check tube thermal sensor2/ short circuit the sensor feedbackon rotation board connector andverify that error disappears. If no,replace rotation board

110–0904H

HEMIT Thermal error(only for NP++)

1. HEMIT tank2. DC Disch board (HE-

MIT assy)3. Rotation board

–Wait for error clearance–If persistent:1/ Check 2A fuse on DC Disch2/ Short circuit the sensor feed-back of the HEMIT. If problemdisappears, replace the HEMIT.3/ Replace DC–Disch4/ short circuit the sensor feedbackon rotation board connector andverify that error disappears. If no,replace rotation board

110–1454H

Jedi inverter tempera-ture too high

1. Parameters kV, mAand time exceededallowed use

2. software bug

– Wait cooling time – change kv–ctrl board (iftrouble always present, report toservice)


2202125


REV 29

Manipulation errors(code 120)

Class 5Errorcode


notCT

120–1500H

Tomo brightness not good(RAD)

kV not correctly set change kV

notCT

120–1501H

Release exposure switch(RAD)

during exposure switch isreleased

no action

notCT

120–1502H

AEC does not cut expo-sure (RAD)

backup parameters (mAs,...) cut exposure

– change parameters (kV, mAs)– change AEC


2202125


REV 29

4-6 WARNING ERRORS

Warning errors are the result of automated and regular background monitoring for either software events or voltagesthreshold overtaking.Those errors are merely for engineering usage and do not indicate any hardware error failure.

However, as they are logged into the Generator Err_log file, just as the previous list of error, they are listed here tohelp error sorting out.

Should too many of them are seen when viewing error log, it is advised to report them via CQA, since the equipmentis still operating.



0152H CAN Domain request with no transfer init0153H CAN Domain Toggle bit error0154H CAN Domain : less than 2 data to download0155H CAN Domain Abort received & applied0156H Bad index in config upload0157H Tube switch while Rotation not off0158H Acceleration cmd while no tube selected0159H Acceleration cmd while database not OK0160H Database download while Rotation speeding0161H Acceleration command not OK0162H Rotation acceleration while in error0163H No CAN message received within 4 secs0164H Rotation Inverter overcurrent (< 3 times)0199H Unknown rotation warning

20 Heater Warn-ing

0251H Received command is not OK

0252H Heater command not OK0253H No CAN message received within 4 secs0254H Heater inverter overcurrent (inverter1) (<3 times)0255H Filament open circuit (inverter1) (<3 times)0256H Heater Inverter short circuit (inverter1) (<3times)0257H Tube switch while filaments not OFF0258H CAN Domain command number error0259H CAN Domain request with no transfer init0260H CAN Domain Toggle bit error0261H CAN Domain : less than 2 data to download0262H CAN Domain Abort received & applied0263H Database download while heater not cut


2202125


REV 29

25 Low Voltage 0570H No more warn –15V too lowPower Supply 0570H No more warn –15V too high

Warnings 0560H No more warn +15V too low0560H No more warn +15V too high0550H No more warn +160V too low0550H No more warn +160V too high0575H Detected –15V too weak0571H Detected –15V too strong0565H Detected +15V too low0561H Detected +15V too high0555H Detected +160V too low0551H Detected +160V too high0599H Unknown LVPS warning




od of approximately 7 years0703H Watchdog reset has just occurred

– 1 if it often occurs, change kv–ctrl (if real re-set of the board)– 2 if it always occurs, report to service


2202125


REV 29

4-7 OTHER FAILURES

Errorcode

Message /explanation



13. No power on theGenerator.

14. EMC filter15. AC/DC– Diode

bridge16. Cable between AC/

DC and LVPS17. LVPS down18. CAN cable problem19. kV control20. CT interface21. Rotation board22. Heater board23. Inverter in short cir-

cuit24. Generator to sys-

tem cable.

Perform the troubleshooting in the following way :1/kV control Leds S0–S7 are lit successively : re-fer to communication errors troubleshooting2/Leds S0–S7 show a specific pattern : refer toPRD errors section3/Led RESET is lit : board is maintained in reseteither by the system or by a system I/F failure orkV control failure4/Led HALT is lit : replace kV control5/No Led is lit : verify that +5V on kV control board(J6, pin2).is present. If yes, replace kV control. Ifno :6/ verify if +15V/–15V is present (Leds DS1/DS2).If yes, replace kV control. If no :7/ Verify if +15V/–15V is present on rotation board(DS1/DS2) and the 160V is present on the heaterboard (DS3). If yes : check the control bus cableto the kV control board. If no error, change the kVcontrol board. If no :8/ Verify if the LVPS DC input is right. If no, checkAC/DC fuse and input lineIf yes :9/disconnect all output cables from the LVPSboard. Verify the +15V/–15V/160V output. If right :reconnect each board successively to find the onestucking the 15V to ground. If wrong, replaceLVPS board


2. Short circuit on the Gen-erator :

n IGBT in short circuitn ACDC or bridge rectifier

in short circuitn EMC filter in short cir-

cuit

( 1/ Disconnect DC bus cables betweenAC/DC and inverter (on AC/DC side)2/ Check if these cables are in short circuit. If yes,replace inverterif no,3/ Disconnect AC line cables between EMC andAC/DC (on EMC side)4/ Check if these cables are in short circuit. If yes,replace AC/DC FRUif no :5/ Disconnect AC line input from EMC board.Check EMC for short circuit between phases. Ifshort circuit, replace EMC board.

Software orData basecorrupt


Retry download


2202125


REV 29

4-8 HEATING WITHOUT HV NOR ROTATION DIAGNOSTIC

Purpose :

The purpose of this test is to drive the heater inverter(s) on both filaments and all the tubes connected to the Generatorin order to identify a faulty heater FRU or a wrong connection between heater board, HV Tank and tube(s).

Pre–requisites :





Sequence :

Once selected the tube the test is running on , start the diagnostic.The following sequence runs on the small focus and then on the large focus :


� 0,4s boost


There is 10s stop time between each focal spot runDuring the test , the heater safeties are checked the same way than in application mode

� Run JEDI ERROR LOG RETRIEVE to see the Error Code.




2202125


REV 29

4-9 ROTATION WITHOUT HV NOR FILAMENT DIAGNOSTIC

Purpose :

The purpose of this test is to drive the rotation inverter(s) in high speed mode (for application supporting high speedmode ) and low speed mode on all the tubes connected to the Generator in order to identify a faulty rotation FRU ora faulty dephasing capacitors FRU or a wrong connection between rotation board, HEMIT (only for NP++) and tube.

Pre–requisites:




� cabling between rotation board and tube checked (including HEMIT connections for NP++ only)

Test type: No manual interaction, no loop on

Sequence:

Once selected the tube the test is running on, start the diagnostic.The following sequence runs in low speed mode and then in high speed mode (if high speed mode allowed) :


� 2s run


There is 2s stop time between each speed mode.During the test , the rotation safeties are checked the same way than in application mode

� Run ERROR LOG RETRIEVE to see the Error Code.


2202125


REV 29

Error codes reporting for generators without HEMIT:Refer to the troubleshooting table

Error codes reporting for generators with HEMIT (only for NP++):error code associated data conclusion

0103H0104H0105H0106H0107H


Power–off. Check cabling. If problem, replace therotation board. If the problem persists, replace theHEMIT tank. See note *

0109H0111H


Check cabling. If problem, replace the rotation board

0112H associated data points to both highspeed and low speed mode

Download official data base (NPv3). If the problempersists, change rotor.

40–0114H

HV cable short circuit errorOpen circuit on:– Tube stator– Hemit secondary–Anode HV cable• Or bearings of tube broken(**).

There is a short circuit in the High voltage line betweenHemit and tube. The actions are:– Check HV cable impedance (Hemit ST to Tube +)– Change tube– Change Hemit

40–0115H

HV cable open error There is an open circuit in the High voltage linebetween Hemit and tube. The actions are:– Check HV cable connection and impedance– Check tube stator impedance– Check Hemit secondary impedance. Replace HEMITif open.


*Note: Before replacing the rotation board, check the impedance of the primary and secondary of the HEMIT. Inorder to do a correct measure, check before the impedance of the cables of the multimeter.

• The impedance of the primary is measured between two pins of the connector J1 of the Bouchonboard in the HEMIT (3 measures). The value is low, between 0.8 ohm and 1.6 ohm.• If the impedance is too low (short –circuit) replace the HEMIT• If the impedance is too high (open circuit) replace the HEMIT

• The impedance of the secondary. Measure between two pins of the HV connector marked as “ST”.(large, small and common). For the three measures the value should be between 0.8 ohm and 1.6ohm.• If the impedance is too low (short –circuit) replace the HEMIT• If the impedance is too high (open circuit) replace the HEMIT


2202125


REV 29

4-10 HV POWER DIAGNOSTICS

4-10-1 Inverter Gate Command Diagnostic

Purpose :

The purpose of this test is to verify that the HV power inverter drive is working properly. The IGBTs gate drive supplyand the IGBTs gate drive is verified. At the same time verification is made that no inverter currents nor High voltageare measured. This test is performed without DC voltage applied to the inverter so that no Xray is generated. Anoderotation and filament drive are not activated during this test.

Pre–requisites :





Sequence :1/ Disconnect the 2 DC bus cables from the AC/DC board ( see central listing )2/ Power on the Generator

3/ Push the TGP board reset switch, or OGP board reset switch.4/ Verify that the DS1 neon on inverter dual snubbers board is not lit5/ Start the diagnostic and verify :


6/ Press the exposure switch (10s exposure is taken after 10 sec delay)7/ During the “exposure”, verify :

– error reported on the operator console– inverter gate_cmd board Leds DS100 and DS200 are lit : IGBTs gate drive is working properly

8/ Release the exposure switch9/�Run ERROR LOG RETRIEVE to see the Error Code.10/ Power off the Generator11/ Reconnect the 2 DC bus cables from the AC/DC board (see central listing )


2202125


REV 29


DS1 neon lit Check that DC bus cables have been removedDS300 neon off Check the gate_cmd supply cable between AC/DC and gate_cmd

board0301/ 0302/ 0303/ 0304/ 0309/0310/ 0311/ 0312/ 0313/ 0314/

0319/ 0323 (H)



one ofDS101/DS102/DS201/DS202

Leds off while no errorreported

Replace inverter

DS100 and/or DS200 Ledsoff



2202125


REV 29

4-10-2 Inverter in Short Circuit Diagnostic

Purpose :

The purpose of this test is to verify that the HV power inverter is working properly. The inverter is commanded at afixed frequency and is loaded with a short circuit. Verification is made that the inverter currents are correctly set. . Atthe same time verification is made that no High voltage is measured. This test is performed without connecting theHV Tank to the inverter so that no Xray is generated. Anode rotation and filament drive are not activated during thistest.

Pre–requisites :








2202125


REV 29

Sequence :1/ Disconnect the HV Tank primary cables from the inverter ( see HV Tank D/R job card ).Take care not to disconnect at the same time the parallel inductor cable which is tightened with the HV Tankprimary cablesPut the short circuit cable (included in the first aid kit ) between the the two capacitors as shown (in red, thecable):

(NP++ Configuration)

Parallel��


2202125


REV 29

(NP/NP+/ESR Configuration)

Parallel��

1/ The parallel inductor must be connected2/ Power on the Generator3/ Push the TGP board reset switch, or OGP board reset switch.4/ Verify that the DS1 neon on inverter dual snubbers board is lit5/ Verify that the DS300 neon on inverter gate_cmd board is lit6/ Start the diagnostic and verify that no error is reported on the operator console7/ Press the exposure switch (500ms exposure is taken)8/ Release the exposure switch9/ verify error reported on the console10/ Run ERROR LOG RETRIEVE to see the Error Code.11/ After exiting the test, power off the Generator12/ Remove the short circuit cable, reconnect the HV Tank primary cables ( see HV Tank D/R job card ).Verify that the parallel inductor cable is connected.


2202125


REV 29



board0301/ 0302/ 0303/ 0304/ 0309/

0310/ 0319 (H)Check that HV Tank primary cables have been removed.

If yes, replace kV control board0311 No Ilp current detected. See note 20312 No Ilr current detected. See note 30313 replace kV control board0314 Ilr current resonant frequency is lower than expected. See note 40320 if problem persists, replace kV control board0323 Both Ilr and Ilp currents not detected. See note 10501 kV control or inverter can be faulty0503 kV control or inverter can be faulty0504 kV control or inverter can be faulty0505 Isolation fault between inverter components and ground. Check

inverter inductors. If no faulty component, kV control or inverter can befaulty

Note 1 : Ilp and Ilr currents not detected1/ Check the –15V (Led DS1) on kV control board (see central listing).If it is not lit, refer to “other failures” section. Else :2/ Power off the Generator. Wait until all neons are off3/ Check that the currents transformers (capacitor set) to gate_cmd board cable is correctly connected. Ifyes :4/ Check that the inverter inductors are correctly connected. If yes :5/ Check that HV Tank is correctly connected to the capacitors set. If yes :6/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes, replace the inverter7/ Reconnect all the cables

Note 2 : Ilp current not detected1/ Power off the Generator. Wait until all neons are off2/ Check that the parallel inductor is correctly connected. If yes :3/ Check that the parallel inductor impedance is 0 Ohms. If no : replace inverter. If yes :4/ Check that inverter capacitors (capacitors set) are not broken. If yes, replace the capacitor set. Else :5/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : replace the capacitor set. Else :6/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes :7/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 of J2of HV Tank is 3,3Ohms. If no replace the inverter. If yes : replace kV control board.8/ Reconnect all the cables


2202125


REV 29

Note 3 : Ilr current not detected1/ Power off the Generator. Wait until all neons are off2/ Check that the inductors are correctly connected. If yes :3/ Disconnect the currents transformers to gate_cmd board cable. Check that the serial currenttransformer impedance is 0. If no : replace capacitor set. Else :4/ Check that inverter capacitors (capacitors set) are not broken. If yes, replace the capacitor set. Else :5/ Check that the gate_cmd to HV Tank cable and HV Tank to kV control cables are correctly connected.If yes :6/ Disconnect the HV Tank to kV control cable. Check that the impedance between pin20 and pin21 of J2of HV Tank is 5 Ohms. If no replace inverter. If yes : replace kV control board.7/ Reconnect all the cables

Note 4 : Ilr current resonant frequency is lower than expected1/ Power off the Generator. Wait until all neons are off2/ Check that the inductors are correctly connected. If yes :3/ Check that inverter capacitors (capacitors set) are not broken. If yes : replace the capacitor set. Else :4/ Disconnect the currents transformers to gate_cmd board cable. Check that the parallel currenttransformer impedance is 0. If no : replace the capacitor set. Else : replace kV control board.5/ Reconnect all the cables

4-10-3 No Load HV Diagnostic without Anode Rotation nor Filament Heating

Purpose :

The purpose of this test is to verify that the HV power inverter and HV tank are working properly. The exposure is takenas in application mode except that no filament drive nor anode rotation is running. Verification is made that the invertercurrents are correctly set and that kV regulation is operating properly. As no filament drive is applied, no XRays aregenerated.This test also allow to separate Generator from HV cable or x–ray tube problem by running it with or without the HVcables plugged on the HV tank. (*)

Pre–requisites :







� (*) HV receptacles must be filled with oil if HV cables are removed.



2202125


REV 29

Sequence :1/ Power on the Generator2/ Push the TGP board reset switch, or OGP board reset switch.3/ Start the diagnostic and verify :


4/select kV (Default = 80 kV) and exposure time (Default = 1 sec.)5/ Press the exposure switch (500ms exposure is taken)6/ During the “exposure”, verify :

– error reported on the operator console7/ Release the exposure switch8/ Run ERROR LOG RETRIEVE to see the Error Code.9/ Power off the Generator

Error reporting :



2202125


REV 29

4-11 TROUBLESHOOTING AIDS

Illustration 4–1 Generator Visual Power Supply Distribution

AC/DC

F1 �

DS 1


Gate command board DS 300 �

�

DS 1

EMC Flt.

� � �DS 3, 2, 1+5, –15, +15

RotorBoard

Heater board

DS 3�

DC bus, 400 ...800 V.

DC bus, 400 ...800 V.

LVPS

≅NE 1 �

�

DC bus,160V(120 to200 V).

+15 V– 15 V

�

kV ctrl“VCC“ + 5 V

+ –

+ M –

+15 V– 15 V

CB1

K1PDU

3ph, 380 – 480VAC115VAC

� �

–15v, +15v

�

+15 V– 15 V

OGP12V

NP I/F

DC Disch (HEMIT assy) � DS1

�DS2 �DS3 �DS4

DS 7 DS 6

�: Neon’s

�: LED’s

DS 1 , 2

DS 2

(only for NP++)


2202125


blank


REV 18 2202125

PDU

TABLE OF CONTENTS

SECTION PAGE

SECTION 1 - LED DESCRIPTION (FOR PDU2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11-1 LED Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11-2 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

i PDU


ii PDU


REV 19 2202125

SECTION 1 - LED DESCRIPTION (FOR PDU2)

NotePDU2: Its part No. is any of 2298850 (400 V, 42 kW), 2298851 (400 V, 53 kW), 2298853 (200 V,

42 kW), or 2298854 (200 V, 53 kW).

1-1 LED DESCRIPTION

Table 1-1 RMT Board LED Description

LED DescriptionD2 Lights when PDU system standby statusK9’ Lights when PDU system standby statusK5’ Lights when XG auxiliary circuit workK7’ Lights when OC system works normalK19’ Lights when XG system main circuit work

K24’ Lights gleam one time when CB2 switch handle in the middle location

D2

K7

K5

K19

K6

K9

K24

1-1 PDU


REV 19 2202125

1-2 TROUBLESHOOTING

No. Error Class Description Troubleshooting1 Front Cover'

LED offError PDU system standby

status normally if frontcover' LED on

Check PDB power supply

2 D2 LED off Error Show RMT board standbystatus normally if D2 LEDon

1.Check PDB power supply2.Check power supply whether worksnormally,measure J1 terminal whether 24V DCvoltage3.Check the cable connection4.Test point VCC-GND whether 5V DC voltage5.Replace the RMT board

3 K9' LED off Error Show PDU standby statusnormally if K9' LED on

1.Check PDB power supply2.Check power supply whether worksnormally,measure J1 terminal whether 24V DCvoltage3.Check the cable connection4.Replace the RMT board

4 K5' LED off Error Show Gantry Safety Loopand OC Safety Loop statusnormally if K5'LED on

1.Check Gantry Safety Loop2.Check OC Safety Loop3.Check Fan_Alarm switch in OC whether open4.Check Emergercy circuit whether open5.Replace the RMT Board

5 K6' LED off Error Show Gantry/Table poweron status normally ifK6'LED on

1.Check Fan_Alarm switch in OC whether open2.Check Emergercy circuit whether open3.Replace the RMT Board

6 K7' LED off Error Show OC power on statusnormally if K7' LED on

1.Check Fan_Alarm switch in OC whether open2.Replace the RMT Board

7 K19' LED off Error Show XG is power onstatus if K19' LED on

1.Check Fan_Alarm switch in OC whether open2.Replace the RMT Board

8 K24' LED offafter gleam

one time

Error Transformer over hot andcut off the system powersupply

1.Check CB2 switch handle being on "middle"location2.Check transformer's thermal switch whetheropen

K24' LEDnever on

Information Show transformer worksnormal

Check CB2 switch handle being on "up" or"down" location

1-2 PDU


2202125

A–1

REV 13

APPENDIX A – SYMBOLS AND CLASSIFICATION

Symbol Publication Description

417–5032 Alternating Current

�

335–1 Three–phase Alternating Current

��

335–1 Three–phase Alternating Current with neutral con-ductor

Direct Current

417–5019 Protective Earth (Ground)

348 Attention, consult ACCOMPANYING DOCUMENTS

417–5008 OFF (Power: disconnection from the mains)

417–5007 ON (Power: connection to the mains)

Warning, HIGH VOLTAGE

Emergency Stop


2202125

A–2

REV 13

Symbol Publication Description

Type B

417–5339 X–ray Source Assembly Emitting

417–5009 Standby

Start

Table Set

Abort

Intercom

(on Operator Console)Power On: light onStandby: light off


2202125

A–3

REV 13

Symbol Description

Microphone (Mic)

Contrast

Brightness

��

��

System storage prior to installation:Maintain storage temperature between –10° C and +60° C

��

��

System storage prior to installation:Maintain non–condensing storage

humidity below 95%

DO NOT store system longer than 90 days

��

��

System storage and shipment:Maintain Air Pressure between 750 and 1060hPa


2202125

A–4

REV 13

CLASS 1 EQUIPMENT

Any permanently installed equipment containing operator or patient accessible surfaces must provide backup protec-tion against electric shock,in case the BASIC INSULATION fails. In addition to BASIC INSULATION,Class1 equip-ment contains a direct connection to a PROTECTIVE(EARTH) CONDUCTOR which prevents shocks when a persontouches a broken piece of equipment or touches two different equipment surfaces simultaneously.

TYPE B EQUIPMENT

CLASS I, II, or III EQUIPMENT or EQUIPMENT with INTERNAL ELECTRICAL POWER SOURCES provide an ade-quate degree of protection against electric shock arising from (allowable) LEAKAGE CURRENTS or a breakdownin the reliability of the protective earth connection.

ORDINARY EQUIPMENT

Enclosed EQUIPMENT without protection against the ingress of water.

OPERATION 0f EQUIPMENT

CONTINUOUS OPERATION WITH INTERMITTENT LOADING.

Operation in which EQUIPMENT is connected continuously to the SUPPLY MAINS. The stated permissible loadingtime is so short that the long term on–load operating temperature is not attained. The ensuing interval in loading is,however, not sufficiently long for cooling down to the long term no–load operating temperature.

EQUIPMENT not suitable for use in the presence of a FLAMMABLE ANESTHETIC MIXTURE WITH AIR or WITHOXYGEN or NITROUS OXIDE

CLEANING

The ProSpeed S series system is NOT WATERPROOF. It is NOT designed to protect internal components againstthe ingress of liquids.Clean external system surfaces(Gantry,table,consoles and accessories)with a soft cloth dippedin hot water and wrung DAMP/DRY. (NOT dripping!) IF NECESSARY, use only mild (dish washing liquid) soap to re-move dirt.

NOTICEAvoid damage to equipment! Some ”spray and wipe”cleaners etch and permanently cloudclear plastic surfaces!! Use only warm water and mild liquid soap to clean surfaces.

GE Medical Systems: Telex 3797371P.O. Box 414, Milwaukee, Wisconsin 53201 U.S.A.(Asia, Pacific, Latin America, North America)

GE Medical Systems – Europe: Telex 698626283, rue de la Miniére, B.P. 34, 78533 Buc Cedex, France

GE HiSpeed Diagnostics Manual

Documents

Transcript of GE HiSpeed Diagnostics Manual