• Topic ID: id_15460511
  • Version: 3.0
  • Date: Apr 22, 2019 12:56:16 AM

JEDI Error Handling

1 Functional Overview

JEDI software performs auto-test at power up and continuously monitors the correct operation of its functions during application. Any malfunction is stored in the Jedi errorlog and reported to the system through a protocol that vehicles error code.

Errors found can only be reported if the generator is powered on and alive.

2 Diagnostics

There are different levels of diagnostics:

2.1 Power On Diagnostics

At power up, the kV control board performs its own initialization, checks its memory integrity (Checksum of program and NVRam), and starts the communication with its peripherals and the system; Communication is permanently checked afterwards. Then it initializes the Rotation board and Heater board with their respective Data base parameters and loads the kV control board's FPGA.

8 LEDs (S7...S0) on kV control board show the software status.

During power on, the Heater board and the Rotation board CPU's initialize themselves and check their memory integrity and hardware. If a problem is encountered, a PRD error is reported to the kV control board.

2.2 Alive Diagnostics

2.2.1 Under Application

Faults will be reported through an error code and associated message.

2.2.2 Diagnostics Run Separately

  • Heating without HV nor rotation

  • Rotation without HV nor filament

  • Inverter gate command diagnostic

  • Inverter in Short circuit diagnostic

  • No load kV without anode rotation nor filament heating

2.2.3 Manual Diagnostics

See troubleshooting section for more detail.

3 Error Code Structure

The error code structure described here applies to the JEDI error detection and logging. All JEDI errors are reported to the system's gesyslog.

3.1 Simplified Error Code Definition

The simplified error code is a grouping of the Jedi error codes. This field gives a fast understanding of which part of Jedi is faulty. This is located in the body of the error message found in the gesyslog as the prefix of the entire error code

3.2 Error Code Definition

Each error code suffix consists of two fields (which cannot be generated and used separately):

  • the first field describes the Jedi function which is faulty (referred to as 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

As an example of a possible error code using both prefix and suffix:

EXAMPLE: (60-0317) Spit Ratio Error

  • 60 - Exposure error

  • 03 - kV control board function is faulty

  • 17 - Error that this maps to. In this particular case, it is "Spit Ratio Error."