• Topic ID: id_16157492
  • Version: 3.0
  • Date: Apr 22, 2019 12:56:17 AM

X-Ray Generation Error Codes (LS16, Ultra, Plus)

1 Introduction - Diagnostics and Error Management

JEDI software performs self-test at power up and continuously monitors the correct operation of its functions during application. Any malfunction is stored in the JEDI error log and reported to the system through a protocol that transports error code. Errors found can only be reported if the generator is powered on and live.

This document is to introduce the JEDI Generator with the following information:

  • Power-on self-tests LED indication.

  • List all the potential error codes that can be issued by JEDI Generator.

  • Provide error code explanation.

1.1 Application Self Tests

Under application mode the generator continuously monitors the correct operation of its functions. Faults are reported through an error code and associated message. Some are straightforward and convey the root cause.

1.2 Error Code Structure

1.2.1 General

Application self tests and diagnostics generate errors. The error code structure described in this section applies to JEDI error detection and logging. The JEDI error log file can be accessed from the system through the system console or a laptop (JEDI error log upload functionality).

When an error is detected, it is sent to the system and is logged in parallel in the JEDI error log file. The file contains a maximum of sixty-four logs.

Each log shows the following structure:

The fields are described in the following sections.

1.2.2 Simplified Error Code Definition

The simplified error code is a grouping of the JEDI error codes. This field gives a rapid understanding of which part of JEDI is faulty.

1.2.3 Generator Phase Definition

The generator phase field contains the state of the generator when the error occurred.

1.2.4 Error Class Definition

There are five classes of errors that correspond to different levels of impact to the system. The class of errors corresponds to the seriousness of the error and the system software will manage operations.

1.2.5 Error Code Definition

Each error code comprises two fields (which cannot be generated and used separately);

  • the first field describes the JEDI function which is faulty (referred to as the function code)

  • the second field describes the error detected.

Example: error code 0306 means:

  • 03: high voltage generation function;

    06: no kV feedback on anode.

1.2.6 Data Associated with the Error Code

The field data associated with the error code shows detailed information over the state of the generator when the error occurred. Examples: rotation high speed acceleration state, small focal spot preheat.

1.2.7 Number of Occurrences

The field number of occurrences is used to log the same error occurring several times consecutively. Instead of filling the error log file with the same error, which has occurred consecutively several times, the first error is logged and successive errors are recorded through increasing the ”number of occurrences” field.

1.2.8 Date & Time

The field date & time stores the date and time when the error occurred. This is the JEDI internal date and time, which may be different form the system date and time. In the case of logging the same error several times, the field indicates the date and time of the first occurrence.

2 Error Code List

The error code list and associated short description is presented below. Only those error codes with an "X" in the right-most column pertain to the JEDI60DC in this CT. These error codes with an “X” may or may not apply to Jedi HP.

3 Warning Code List

The error code list and associated short description is presented below. Only those error codes with an "X" in the right-most column pertain to the JEDI60DC in this CT.

Also, see Warning Errors.

4 Error Reporting

The system eventlog adds to the simplified error code the following information:

  • error message

  • system phase: state of the system when the error occurred.

  • system time: date and time when the error occurred.

Whenever a Generator error is logged in the system eventlog file and displayed on the operator console (or workstation), the Jedi eventlog upload functionality is available to get more detailed information about the error. This function must be performed from the operator console (or workstation).

The simplified error code must be used to find the Jedi error code in the Jedi errorlog file.

4.1 Detailed Error Description and Troubleshooting Guide

  • warning
  • Potential for shock
  • Voltage may be present.
  • Before any manual intervention, ensure the main power is off. Apply lock out-tag out procedure for your own safety when manipulating inside the equipment.

For each error code this manual shows an associated message and additional explanation related to the error occurrence.

Codes are sorted by ascending order both for simplified code and error code. Refer to Error Code Structure, for error code structure. Information about associated data structure is located at the end of each error code subset whenever it applies.

Before servicing the JEDI retrieve the eventlog with the service laptop or console to have the list of the last errors and warnings.

4.2 Errors

4.2.1 Tube Spits Detection Errors (Code 30)

note:

Regarding 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 kinds of spits.

In the data of this error we can distinguish between the different spits:

(Data in Hex) / Data in binary conversion

(0001H) / 0000 0000 0000 0001 : Spit in anode side

(0002H) / 0000 0000 0000 0010 : Spit in cathode side

(0004H) / 0000 0000 0000 0100 : Spit between anode and cathode

(0008H) / 0000 0000 0000 1000 : kV regulation error when kV > kV active

(0010H) / 0000 0000 0001 0000 : kV regulation error during kV rise when kV < kV active (75% kV reference). Treated as spit but not counted as spit.

Actual spits occurrence will be single one or combination of each spits.

Data example of combination spits

(0005H): Spits Anode + Anode to Cathode

(0012H): Spits Cathode + kV regulation during rise time

In case of KV regulation error , decrease kV-mA target of exposure (for example 60kV-50mA).

4.2.2 Anode Rotation Errors (Code 40)

4.2.3 Filament Heater Errors (Code 50)

4.2.4 Exposure Errors (Code 60)

4.2.5 Power Supply Errors (Code 70)

4.2.6 Hardware Errors (Code 80)

4.2.7 Application Errors (Code 90)

4.2.8 Communication Errors (Code 100)

4.2.9 Thermal Errors (Code 110)

4.2.10 Manipulation Errors (Code 120)

Not Applicable to Jedi 60DC.

4.2.11 Ingrid Errors (Code 130)

Not Applicable to Jedi 60DC.

4.2.12 Tube Switch Errors (Code 140)

Not Applicable to Jedi 60DC.

4.3 Warning Errors

Warnings (class 1 and 2 errors) are the result of automated and regular background monitoring for either software events or voltages check.

Those errors are merely for engineering use and do not indicate any hardware error failure.

Warnings are also logged into the generator event log file, just as the previous list of errors, and can help to sort them out. Refer to the Error and Warning code list chapter for the complete list of warnings.

However some warnings listed below give important information to the user and may need some action.