- Topic ID: id_11039046
- Version: 2.0
- Date: Jan 30, 2019 9:42:50 PM
X-Ray Generation Error Codes
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.
-
List of diagnostics aids and explanation of diagnostics.
1.1 JEDI tests and diagnostics
There are different levels of tests and diagnostics implemented in the JEDI generator.
1.1.1 Power-on self tests
At power-up the PPC kV control performs its own initialization, checks its memory integrity (checksum of program and NVRAM) and starts the communication with its peripherals as well as the system. Communication is permanently checked afterwards. It then initializes the Rotation board and Heater board with their respective database parameters and loads PPC kV control FPGA. Eight LEDs (from DS17 to DS24) on PPC kV control board show the software status. During power-on, the Heater board and the Rotation board CPUs are initialized and check their memory integrity and hardware. If a problem is encountered, a PRD error is reported to the PPC kV control.
1.1.2 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. Refer to the recommended action in the error list and troubleshooting guide.
1.1.3 Manual Diagnostics
On the generator we can also perform test to check its functions independently.
-
heating function
-
rotation function
-
inverter gate command diagnostic
-
inverter in short circuit diagnostic
-
no load HV function diagnostics
-
Fan diagnostics
These tests are referred to as manual diagnostics or diagnostics. Diagnostics are usually implemented in the system console or in the service software (executed from the service laptop).
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 focus 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 and Warning Code List
The error and warning code list and associated short description is presented below. For example if "JEDI 60DC Lite" column is marked, error is applicable to JEDI 60DC Lite. If the column “Deprecated” is marked that means that the error is no more generated by the software (old error).
2.1 Error code list
2.2 Warning code list
3 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 Error troubleshooting
This chapter describes diagnostics tools based on error codes and specific diagnostics.
![]() |
|
4.1 Detailed Error Description and Troubleshooting Guide
The table below provides the guidelines to troubleshoot the Generator problems based on the error codes.
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. 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)
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:
1: Spit in anode side
2: Spit in cathode side
4: Spit in both sides
8: kV regulation error.
For an exposure with anode and both sides spit, the data will be 5.
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 and Lite.
4.2.11 Ingrid Errors (Code 130)
Not Applicable to Jedi 60DC and Lite.
4.2.12 Tube Switch Errors (Code 140)
Not Applicable to Jedi 60DC and Lite.
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.

