GE Healthcare CT Pro Speed: troubleshooting and error codes
The ServiceForge knowledge base holds 59 documented symptoms for the GE Healthcare CT Pro Speed, with 121 ranked causes, 95 diagnostic checks with test points and expected values, and 751 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
Power-on self-test fails during DISP Phase 1
DISP or DISP2 board test fails; LEDs display error code and testing halts.
Ranked causes
- 1. ACRTC initialize test failure (DISP test 1) (unknown)
- 2. ACRTC pattern RAM test failure (DISP test 2) (unknown)
- 3. Interrupt test failure on DISP (DISP test 3) (unknown)
- 4. OVL plane control register write test failure (DISP test 4) (unknown)
- 5. DISP control register test failure (DISP test 5) (unknown)
- 6. Interrupt mask control register test failure (DISP test 6) (unknown)
- 7. VSYNC interrupt test failure (DISP test 7) (unknown)
- 8. OVL plane memory test failure (DISP test 8) (unknown)
- 9. ACRTC DMA test failure (DISP test 9) (unknown)
9 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power-on self-test fails during IPU2 test
IPU2 board test fails; LED displays error code $41–$4F and testing halts.
Ranked causes
- 1. IPU2 register access test failure (unknown)
- 2. IPU2 extended mode access test failure (unknown)
- 3. IPU2 command area access test failure (unknown)
- 4. IPU2 CPU mode access test failure (unknown)
- 5. IPU2 CPU extended mode access test failure (unknown)
- 6. IPU2 DMA test failure (unknown)
- 7. IPU2 vector area fetch test failure (unknown)
- 8. IPU2 i860 register access test failure (unknown)
- 9. IPU2 driver area access test failure (unknown)
9 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power-on self-test fails during CPW Phase 1
CPW LEDs display error code and testing halts; no further tests proceed. Error code remains on LEDs.
Ranked causes
- 1. SRAM write/read/verify test failure (CPW test 1) (unknown)
- 2. Bus error during ROM test (CPW test 2) (unknown)
- 3. ROM checksum failure (CPW test 3) (unknown)
- 4. Interrupt handler write/read/verify test failure (CPW test 4) (unknown)
- 5. Control/status register failure (CPW test 5) (unknown)
- 6. DMAC register failure (CPW test 6) (unknown)
- 7. Bus error on IPU2 mode (CPW test 7) (unknown)
- 8. CPW-DRAM write/read/verify test failure (CPW test 8) (unknown)
8 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power-on self-test fails during CPW Phase 2
CPW Phase 2 test fails; LED displays $1F and testing halts. Phase 2 includes advanced tests.
Ranked causes
- 1. FDC register read/write test failure (CPW test 7) (unknown)
- 2. SCSIC register read/write test failure (CPW test 8) (unknown)
- 3. SRAM write/read/verify test 2 failure (CPW test 9) (unknown)
- 4. CPW-DRAM write/read/verify test 2 failure (CPW test 10) (unknown)
- 5. Calendar read test failure (CPW test 11) (unknown)
- 6. DMA CPW-DRAM test failure (CPW test 12) (unknown)
- 7. DMA IPU2 mode test failure (CPW test 13) (unknown)
- 8. Hard disk read test failure (CPW test 14) (unknown)
8 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
System fails during power-up sequence
LED displays error code in hexadecimal during hardware self-test or boot-up phases; system halts and does not reach ready state
Ranked causes
- 1. FMP1 ASSY hardware failure (common)
- 2. MRX ASSY test failure (occasional)
- 3. FMP2 or FMP3 ASSY, PACK, or hard disk error (common)
- 4. Communication error between FMP1 and DMP4 (occasional)
- 5. Hard disk or floppy disk failure (occasional)
- 6. Operating system file not found or corrupted (occasional)
- 7. Memory allocation or layout error (rare)
Monitor LED status on FMP1 board during power-up
- Test point
- FMP1 LED display (8-bit hexadecimal)
- Expected
- 11H through 1BH during normal FMP1 test; 90H at boot end
- Tools
- Visual inspection
4 more checks with pass and fail actions, 8 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Operator console fails during power-up
CPW fails power-on sequence due to operating system failure; LED status indicates error condition
Ranked causes
- 1. Bus error from accessing nonexistent memory or executing inadequate instruction (common)
- 2. Address error from word reference to odd address (occasional)
- 3. Exception from incorrect instruction or corrupted memory (occasional)
- 4. Abnormal termination due to OS-related task abort (occasional)
- 5. Abnormal operation system (occasional)
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
System power-up fails
Display processor fails during power-up self-test sequence; LED status indicates test failure; system does not reach boot-up phase
Ranked causes
- 1. DMP2 assembly hardware failure (common)
- 2. OVL2 assembly or CBRD failure (common)
- 3. IFB2 assembly or CBRD failure (common)
- 4. FCP3B assembly failure (main data memory) (occasional)
- 5. FCP2A or DMP2 assembly communication failure (occasional)
Verify DMP2 ASSY power-up self-test execution
- Test point
- DMP2 LED status
- Expected
- LEDs illuminate in sequence per TABLE 2-1
2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry does not rotate during initialization
Gantry fails to rotate during power-on initialization sequence; ERRG LED on or alternating ERRG/LOOPG LEDs
Ranked causes
- 1. Safety interlock activated during initialization (common)
- 2. Gantry servo error or motor failure (occasional)
- 3. Gantry over-speed condition (occasional)
- 4. Azimuth encoder pulse detection failure (occasional)
Check manual/system mode switch position during initialization
- Test point
- TGP manual switch
- Expected
- Switch in SYS position for automatic initialization
3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ETC board fatal error condition caution
ETC board encountered fatal hardware or software error during initialization; LED status indicates error code and current condition
Ranked causes
- 1. ROM level does not match program level (rare)
- 2. CPU communication or write error (rare)
- 3. Memory allocation or file read failure (rare)
Read ETC LED error code from exception status table
- Test point
- ETC board LEDs
- Expected
- LED pattern matches one of Table 6-3 error codes
- Tools
- Visual inspection, ETC exception LED status reference
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry Processor RAM error on power-on
ERRG, LOOPG, and REQG LEDs illuminate on power-on or reset; gantry processor hangs up
Ranked causes
- 1. Internal RAM failure (PD78310 at U6R, addresses FE00-FEDF) (rare)
- 2. External RAM failure (HM6716P at U7M, addresses C000-C7FF) (rare)
- 3. Dual Port RAM failure (7130 at U6L, addresses D000-D1FF, D3C0-D3FB) (rare)
Observe LED status on power-on or reset
- Test point
- ERRG, LOOPG, REQG LEDs
- Expected
- LOOPG LED flashes on and off if test passes
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Management Processor RAM error on power-on
ERRM, LOOPM, REQM, and MNLM LEDs illuminate on power-on or reset; management processor hangs up
Ranked causes
- 1. Internal RAM failure (PD78310 at U3E, addresses FE00-FEDF) (rare)
- 2. External RAM failure (HM6716P at U3A, addresses C000-C7FF) (rare)
- 3. Dual Port RAM failure (7130 at U6L, U3L) (rare)
Observe LED status on power-on or reset
- Test point
- ERRM, LOOPM, REQM, MNLM LEDs
- Expected
- LOOPM LED flashes on and off if test passes
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Motor does not rotate high voltage
Servo motor will not turn despite power applied
Ranked causes
- 1. No voltage command signal (common)
- 2. RSGO signal issue or fuse failure (occasional)
- 3. Servo Amp malfunction (occasional)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
OS loading timeout or corruption
System reaches boot-up phase but fails during OS load or initialization; display shows error code during OS startup sequence
Ranked causes
- 1. Corrupted OS transfer program or hard disk error (common)
- 2. Corrupted operating system or read error (common)
- 3. Memory allocation error or improper memory size (occasional)
Check crash save area for stored error information
- Test point
- System memory crash save area
- Expected
- Error information accessible for diagnosis
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Table Processor RAM error on power-on
ERRT, LOOPT, REQT, and MNLT LEDs illuminate on power-on or reset; table processor hangs up
Ranked causes
- 1. Internal RAM failure (PD78310 at U3R, addresses FE00-FEDF) (rare)
- 2. External RAM failure (HM6176P at U3M, addresses C000-C7FF) (rare)
- 3. Dual Port RAM failure (IDT7130 at U3L) (rare)
Observe LED status on power-on or reset
- Test point
- ERRT, LOOPT, REQT, MNLT LEDs
- Expected
- LOOPT LED flashes on and off if test passes
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Filter center channel alignment high voltage
Adjustment of bow-tie filter position to align its projection on the detector. System measures filter center channel from air and filter scan files.
Ranked causes
- 1. Filter not centered on detector (common)
- 2. Filter center channel offset from iso-center channel (common)
Verify correct filter center channel value matches detector type
- Test point
- System display after calculation
- Expected
- 406.75 Ch. for Xe Type Detector; 458.75 Ch. for SS Type Detector, +0.3 Ch. during measurement; ±0.02 Ch. after adjustment
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
KV Board test fails or shows errors high voltage
High-voltage board diagnostic test returns non-zero error count; inverter output test incomplete or invalid
Ranked causes
- 1. Inverter outputs not properly short-circuited during test (common)
- 2. Incorrect jumper setting on KV Board (occasional)
Verify inverter outputs are short-circuited
- Test point
- HV tank terminals P1 and P2
- Expected
- Cable connected between P1 and P2 on both anode and cathode tanks
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Rotor Board test error during S11 or S12
Service test S11 or S12 performs rotor board diagnostics. Test result displays hexadecimal codes indicating logical signal changes and errors. At first stage, filament operation check may generate related error codes.
Ranked causes
- 1. Filament operation error during autotest (occasional)
- 2. Rotor board circuit fault (unknown)
Run service test S11
- Test point
- GENERATOR TEST menu
- Expected
- Number of errors occurred = 00
1 more check with pass and fail actions are in ServiceForge. Connect ServiceForge to your AI
Calibration: Gravity sag amplitude measurement high voltage
Measurement of gravitational sag in the X-ray tube assembly at different gantry rotation positions. Part of alignment verification procedures.
Ranked causes
- 1. Gravity sag in tube assembly during rotation (unknown)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Initialize air reference data radiation
Initialize air reference data collection after cold load, X-Ray generator calibration, detector replacement, or system calibration
Ranked causes
- 1. System requires baseline reference data after major maintenance or replacement (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: ISO center channel alignment high voltage
X-ray tube position adjustment to center the detector channel receiving the projection of a calibration pin. System calculates required tube shift from air and pin scan files.
Ranked causes
- 1. X-ray tube not centered on detector (common)
Verify correct iso-center channel value for detector type
- Test point
- System display after calculation
- Expected
- 406.75 Ch. for Xe Type Detector; 458.75 Ch. for SS Type Detector, ±0.02 Ch.
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Phantom centering
Repositioning of calibration phantom to center it on the scan plane. System determines required phantom shift from air and phantom scan files.
Ranked causes
- 1. Phantom position offset from scan plane center (common)
Verify phantom position offset values
- Test point
- System display after calculation
- Expected
- MOVE DOWN e.ee MM (±0.15) and MOVE RIGHT f.ff MM (±0.15), ±0.15 mm
1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: X-Ray tube warm-up radiation
Warm-up routine required after power ON, before first scan, after 3 hours idle, and before phantom calibration to update calibration files
Ranked causes
- 1. X-Ray tube requires thermal stabilization (common)
Execute warm-up scans #1 through #4 without data collection
- Test point
- X-Ray tube output
- Expected
- Scans complete without errors at specified kV and mA settings
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
CPU Board self-test failure
Generator powered-on or reset; CPU Board self-test performs register pattern read/write, EPROM checksum, RAM pattern read/write, DUART test (DTACK, TIMER, internal loops, interrupt), and EEPROM checksum. Failure generates error code to Operator Console.
Ranked causes
- 1. CPU Board internal circuit failure (unknown)
Verify power-on self-test execution
- Test point
- Operator Console
- Expected
- Autotest completes; error codes displayed only if failure
Cradle movement at specified speeds not functioning correctly
Cradle fails to move at expected speeds in helical scan modes (Tests 014-019) or speed settings are not responding correctly to In/Out/Fast button commands.
Ranked causes
- 1. Cradle motor or drive control malfunction (common)
Set T6 of TABLE PROCESSOR DIAG switch to ON position
- Test point
- T6 switch, TABLE PROCESSOR DIAG SWITCH
- Expected
- ON position
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Cradle position display incorrect or out of range
Gantry display shows cradle position value outside expected limits (0-3050 decimal, equivalent to 0-1525mm) or fails to display position in Test 000.
Ranked causes
- 1. Cradle position sensor/encoder malfunction (common)
Set T6 of TABLE PROCESSOR DIAG switch to ON position
- Test point
- T6 switch, TABLE PROCESSOR DIAG SWITCH
- Expected
- ON position
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
DAS trigger pulses incorrect or aperture error detected
OGP Test Mode displays incorrect XG ERR or APERTURE ERR counts during TGP test mode (Test 2-2), indicating missed or extra trigger pulses to the data acquisition system.
Ranked causes
- 1. OGP board trigger detection circuit malfunction or GPLS2 signal loss (common)
Set SW3 DIP switches for correct ROM version
- Test point
- SW3 DIP switches on OGP board
- Expected
- ROM 2121676: S3=OFF, S2=ON, S1=OFF; OR ROM 2107557/P9183ZP/P9183ZQ: S6=OFF, S1=OFF
4 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ETC board power-on test execution
ETC board initializes and runs self-diagnostics during system power-up; LED status indicates test progress and results
Ranked causes
- 1. Normal power-up and initialization sequence (common)
Set DIP switch SW8A configuration
- Test point
- ETC Assy S8A DIP switch bits B0, B1, B2, B3
- Expected
- B0='0', B1='0', B2='0' or '1' (offline), B3='0' or '1' (power-on test)
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ETC ethernet address verification
Validates ethernet address data backup in ETC board internal battery; verifies manufactured date, serial number and ethernet address settings
Ranked causes
- 1. Ethernet data corrupted due to weak or depleted internal battery (occasional)
Connect external terminal to ETC board CN4
- Test point
- ETC board connector CN4
- Expected
- Terminal display connected
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry azimuth position incorrect or out of reference
Gantry display shows azimuth angle value outside expected range (-180° to +180° or equivalent 0-1462 decimal) in Test 400, or rotation home position not correctly identified.
Ranked causes
- 1. Gantry azimuth position sensor or home reference malfunction (common)
Set G6 of GANTRY PROCESSOR DIAG switch to ON position
- Test point
- G6 switch, GANTRY PROCESSOR DIAG SWITCH
- Expected
- ON position
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry Processor ROM error on power-on
ERRG and REQG LEDs illuminate after RAM check; gantry processor hangs up
Ranked causes
- 1. ROM data checksum failure (addresses 0-BFFF) (rare)
Observe LED status after RAM check passes
- Test point
- ERRG, REQG LEDs
- Expected
- LOOPG LED blinks if ROM check passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry rotation time measurement incorrect or encoder pulse count anomalous
Test 020 shows incorrect cradle encoder pulse count per gantry rotation (Home to Home), or Test 401 displays incorrect rotation time from Home position to Home position, indicating timing or encoder issues.
Ranked causes
- 1. Cradle encoder malfunction or counter circuit fault (common)
Set appropriate DIAG switch ON (T6 for Test 020, G6 for Test 401)
- Test point
- T6 or G6 DIAG switch, TABLE/GANTRY PROCESSOR
- Expected
- Switch in ON position
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Invalid entry in Support Display menu
Software displays ** INVALID ENTRY message when unacceptable parameter is entered
Ranked causes
- 1. Parameter value outside acceptable range or invalid format (common)
Enter parameter value in Support Display menu
- Test point
- Menu input field
- Expected
- Value accepted or ** INVALID ENTRY message displayed
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Invalid file name entered in FILE SELECTION
Software displays error when file name is entered incorrectly or file does not exist
Ranked causes
- 1. Incorrect file name spelling or non-existent file (common)
Enter file name in FILE SELECTION menu
- Test point
- FILE SELECTION input field
- Expected
- File name accepted; file displays or error message appears
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Magnetic tape recovery from mis-initialization
Recover images from incorrectly initialized tape or images stored after mis-initialization
Ranked causes
- 1. Incorrectly initialized tape or images stored after mis-initialization (unknown)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Magnetic tape recovery from parity error
Recover MT images unable to be retrieved due to tape parity error or corrupted directory
Ranked causes
- 1. Corrupted MT directory (unknown)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Management Processor ROM error on power-on
ERRM, REQM, and MNLM LEDs illuminate after RAM check; management processor hangs up
Ranked causes
- 1. ROM data checksum failure (addresses 0-BFFF) (rare)
Observe LED status after RAM check passes
- Test point
- ERRM, REQM, MNLM LEDs
- Expected
- LOOPM LED flashes on and off if ROM check passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OD storage errors after unexpected shutdown
Recover optical disk information when errors ER-440, ER-441, or ER-442 appear after system power-off during OD operation
Ranked causes
- 1. System shutdown during OD operation corrupting OD information (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OD study information recovery after power loss
Restore study information destroyed by power-down during image storage to optical disk (requires patient data re-entry)
Ranked causes
- 1. Power-down during image storage to optical disk destroying study information (occasional)
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP communication hardware error during data reception
ERRS and RINGS LEDs illuminate; OGP board cannot receive data from Management Processor via slip rings
Ranked causes
- 1. Slip ring connection failure or signal corruption during OGP reception (occasional)
Inspect slip ring connectors and contacts
- Test point
- OGP slip ring connection
- Expected
- Contacts clean, connectors fully seated
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP communication repeated NACK error
ERRS LED illuminates; OGP board receives NACK from Management Processor three times or transmits NACK
Ranked causes
- 1. Repeated negative acknowledgment during OGP-Management Processor communication (occasional)
Power cycle system and re-run self-test
- Test point
- ERRS LED
- Expected
- ERRS LED off after power cycle
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP communication timeout error
ERRS and RINGS LEDs illuminate; OGP board fails to receive ACK/NACK from Management Processor within timeout period
Ranked causes
- 1. Slip ring communication timeout during acknowledge handshake (occasional)
Verify Management Processor is responding
- Test point
- Management Processor LEDs (ERRM, LOOPM, REQM, MNLM)
- Expected
- No error LEDs illuminated; LOOPM flashing
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP Scan Processor lock-up on power-on
ERRS, LOOPS, REQS, RINGS, and TEST LEDs all illuminate during power-on; processor not responding to watchdog timer
Ranked causes
- 1. OGP Scan Processor hangs or infinite loop (except WDT test mode) (rare)
Verify WDT test mode is not active
- Test point
- System configuration or service switch
- Expected
- WDT test mode disabled
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP Scan Processor RAM error on power-on
ERRS and LOOPS LEDs illuminate on power-on or reset
Ranked causes
- 1. OGP board RAM failure (rare)
Observe LED status during power-on self-test
- Test point
- ERRS, LOOPS LEDs
- Expected
- LEDs off if RAM test passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
OGP Scan Processor ROM error on power-on
ERRS LED illuminates after RAM check; OGP ROM data corruption detected
Ranked causes
- 1. OGP board ROM failure (rare)
Observe ERRS LED status during power-on self-test
- Test point
- ERRS LED
- Expected
- ERRS LED off if ROM test passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Parameter values exceed specified range in Support Display
Software displays ** RANGE ERROR when entered parameters exceed acceptable data range
Ranked causes
- 1. MIN value greater than MAX value or values outside -1000000 to +1000000 range (occasional)
Enter MIN and MAX values in RANGE menu
- Test point
- RANGE input fields
- Expected
- MIN < MAX; both within -1000000 to +1000000
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
PDU test fails or generates no 550/750 VDC output high voltage
Power distribution unit diagnostic test S51/S52 fails; no voltage output detected on rotor or supply rails
Ranked causes
- 1. PDU not outputting 550 or 750 VDC due to internal fault (unknown)
Run PDU diagnostic test from host
- Test point
- Host terminal S51 or S52 command entry
- Expected
- Test begins; PDU generates 550 or 750 VDC output
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Retrieve crash save area information
Transfer processor crash save area containing program counter, status register, registers and LED status to floppy diskette for analysis
Ranked causes
- 1. Need to preserve crash diagnostic data (common)
Initialize crash save diskette
- Test point
- Floppy disk drive
- Expected
- Diskette formatted per Appendix A
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Rotor Board test error during S14 or S16
Service test S14 or S16 performs rotor operation and control check with generator operating as in operation mode. Test monitors phases P1, P2, P3, P7 and checks for error codes generation during rotor operations.
Ranked causes
- 1. Rotor control or KV balance error during operation (unknown)
Run service test S14
- Test point
- GENERATOR TEST menu; command ( begins rotor test
- Expected
- Number of errors occurred = 00; no error codes during phases P2, P3, P7
1 more check with pass and fail actions are in ServiceForge. Connect ServiceForge to your AI
Rotor Board test S17 execution
Service test S17 initiates rotor board test with specific diagnostics. Generator transitions through phases P0 and P1. Test completion exits service mode with SE0 and N commands.
Ranked causes
- 1. S17 test procedure not documented in provided text (unknown)
Execute service test S17
- Test point
- GENERATOR TEST menu
- Expected
- Phase P1 reached; rotor operations complete; SE0 acknowledged
SCSI board diagnostic test failure
Test execution on SCSI board results in error condition indicated by status LEDs; test phase where error occurred is retained on LED display.
Ranked causes
- 1. Hardware failure in tested component during test phase (unknown)
Observe TEST LED status during test execution
- Test point
- TEST LED on SCSI board
- Expected
- LED on during test execution, off after completion
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not display version 5.01 after loading
After executing Custom Parameter Change mode, the CRT monitor does not show 'VER. 05.01' and logo on startup
Ranked causes
- 1. Software loading incomplete or Custom Parameter Change mode not executed (common)
Verify system startup display
- Test point
- CRT monitor
- Expected
- 'VER. 05.01' and logo appear on screen
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
System error occurs during Support Display operation
Software displays ** ERROR XXXXXXXX (error code) and control shifts to Display Support or Maintenance menu
Ranked causes
- 1. Internal system or file access error (rare)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Table height display incorrect or out of range
Gantry display shows table height value outside expected limits (0010-1210 decimal, equivalent to -600mm to 0mm from ISO center) in Test 001.
Ranked causes
- 1. Table height sensor/encoder malfunction or mechanical limit exceeded (common)
Set T6 of TABLE PROCESSOR DIAG switch to ON position
- Test point
- T6 switch, TABLE PROCESSOR DIAG SWITCH
- Expected
- ON position
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Table Processor ROM error on power-on
ERRT, REQT, and MNLT LEDs illuminate after RAM check; table processor hangs up
Ranked causes
- 1. ROM data checksum failure (addresses 0-BFFF) (rare)
Observe LED status after RAM check passes
- Test point
- ERRT, REQT, MNLT LEDs
- Expected
- LOOPT LED blinks if ROM check passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Tilt angle display incorrect or out of range
Gantry display shows tilt angle value outside expected range or incorrect angle orientation in Test 002, with incorrect mapping of FWD/BWD positions.
Ranked causes
- 1. Tilt angle potentiometer sensor malfunction or calibration drift (common)
Set T6 of TABLE PROCESSOR DIAG switch to ON position
- Test point
- T6 switch, TABLE PROCESSOR DIAG SWITCH
- Expected
- ON position
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Unable to select file in Support Display
Software refuses to accept menu selections other than FILE SELECTION until a valid file is selected
Ranked causes
- 1. No file selected or invalid file name entered (common)
Attempt to select a menu option other than FILE SELECTION
- Test point
- Display Support menu
- Expected
- Error or no response; cursor remains at FILE SELECTION option
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Warm-up error detected
System reports WARM-UP ERROR when collected data falls outside specified range
Ranked causes
- 1. Collected data outside specified range (unknown)
Verify last scan data collection
- Test point
- RAW DATA FILE
- Expected
- Data within specified range
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
X-ray generator anode or cathode side test incomplete radiation
Anode side test runs but cathode side test does not execute or is skipped; one side of x-ray tube assembly not tested
Ranked causes
- 1. PDU model P9180AB or P9180AF installed (cathode test skipped) (occasional)
Identify PDU model number
- Test point
- PDU chassis or documentation
- Expected
- PDU model number noted (e.g., P9180AB, P9180AF, or other)
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
X-ray spit detected during scan radiation
Scan test mode indicates X-ray tube spit occurred (XG ERR displays count > 0) during or after HV (high voltage) exposure, preventing planned scans from proceeding in multi-scan sequences.
Ranked causes
- 1. X-ray tube arcing or instability during exposure (occasional)
Set SW3 DIP switches for Scan Test Mode per ROM version
- Test point
- SW3 DIP switches on OGP board
- Expected
- ROM 2121676: S3=ON, S2=ON, S1=OFF; OR ROM 2107557/P9183ZP/P9183ZQ: S5=OFF, S1=OFF
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
0001 | Task ID error | Ethernet task identifier invalid or not found | error |
0003 | Cannot keep memory | Memory allocation failed for Ethernet task | critical |
000A | Time out | Ethernet operation timeout | error |
0020 | Component vector not assigned | Ethernet component function vector missing | error |
0032 | Task is waiting for event flag or semaphore | Task blocked on synchronization primitive | warning |
00XX0100 | Directive No. Remains Undecided | Directive number not resolved | error |
00XX0200 | Invalid Parameter Block Address | Parameter block address invalid | error |
00XX0300 | Invalid Direction Code | DMA direction invalid | error |
00XX0400 | Invalid Memory Address | Memory address out of range | error |
00XX0500 | Invalid Data Size | Data transfer size invalid | error |
00XX0600 | Invalid CPU Number | CPU index out of range | error |
00XX0700 | Channel Bus Error | Channel bus communication failed | error |
00XX0800 | Configuration Error | System configuration invalid | error |
00XX0900 | Operation Timing Error | Timing constraint violated | error |
00XX0A00 | Reserved | Reserved error code | unknown |
00XX0B00 | Address Error | Address invalid | error |
00XX0C00 | Address Error | Address invalid | error |
00XX0D00 | Address Error | Address invalid | error |
00XX0E00 | Address Error | Address invalid | error |
00XX0F00 | Bus Error | Bus communication error | error |
00XX1000 | Bus Error | Bus error detected | error |
00XX1100 | Bus Error | Bus transmission error | error |
00XX1200 | Bus Error | Bus protocol error | error |
00XX1300 | Count Error | Data count mismatch | error |
00XX1400 | Count Error | Count mismatch | error |
00XX1500 | Count Error | Count error | error |
00XX1600 | Count Error | Count fault | error |
00XX1700 | External Compulsory Stop | External stop signal received | warning |
00XX1800 | Software Compulsory Stop | Software stop command executed | warning |
00XX1900 | Time Out | DMA operation timeout | error |
00XXAA00 | Normal Completion | DMA operation completed successfully | info |
01 | There is no designated Study | GET/PUT operation without study | error |
01 | The designated Study was already registered | Study allocation operation | warning |
01 | Directive No. Error | Invalid directive number received | error |
01 | Initialize failure of PDC RAM (PDC context) | PDC RAM test fails during power-up | critical |
01 | Hardware self test does not exist in ROM | ROM checksum or integrity failure | critical |
01H | Hardware self-test code not found in ROM or hardware does not exist | Power-up self-test initialization | error |
02 | The designated Study does not exist | Study access or deletion attempt | error |
02 | There is no specified Study. It is not deleted | Delete without study specification | warning |
02 | Odd Parameter Address | Parameter address is not aligned to even boundary | error |
03 | Invalid Request | Request does not match valid command format | error |
03 | The designated Image was already registered | Image allocation operation | warning |
03 | There was not enough in the specified Study | Delete with insufficient study data | warning |
04 | There is no specified Image. It is not deleted | Delete without image specification | warning |
04 | Image No. Deciding Error | Image numbering operation | error |
04 | Invalid Parameter (W/L Control) | Invalid window/level control parameter received | warning |
05 | There was not enough in specified Image | Delete with insufficient image data | warning |
05 | Access is out of Image Area | Accessing outside image boundaries | error |
05 | Study Area full | Attempting to allocate to study area | error |
05 | Invalid Parameter (Frame Setting) | Frame configuration parameter outside valid range | warning |
06 | There is no space in Image INFO BUFFER | Image information buffer operation | error |
06 | Invalid Parameter (Frame Data) | Frame data packet corrupted or incomplete | error |
06 | Image INFO Block full | Image information allocation | error |
07 | The reading size of Image INFO is too big | Reading oversized image information | error |
07 | The Area in Image File full | Writing to image file | error |
07 | Invalid Parameter (W/L) | Window/Level parameter invalid | warning |
08 | Image File full | Image storage operation | error |
08010003 | Nonexistent Target Task | OS directive references task that does not exist | error |
08010005 | Segment Table Full | OS segment table capacity exceeded | error |
08010006 | Duplicate Segment Name | OS detects duplicate segment name during creation | error |
08010008 | Insufficient Memory | OS memory allocation fails; insufficient free memory | error |
09 | Impossible to delete for all of the appointed study are protected from Delete | Delete protected study | warning |
09 | There is no space in Image INFO BUFFER | Allocating image information | error |
0A | Impossible to delete for some of the appointed study are protected from Delete | Delete partially protected study | warning |
0A | The size of Image INFO is too big | Image information storage | error |
0A | Invalid Parameter (Identify) | Invalid identification parameter | warning |
0A20 | Connection destroyed | Network connection unexpectedly closed | warning |
0A32 | Network is down | Network interface unavailable or unreachable | critical |
0A33 | Cannot connect network due to abnormal AUI cable and ETC | Ethernet board (ETC) cable connection failure | error |
0A3C | Connection time out | Network connection establishment timeout | error |
0A50 | Abnormal configuration parameter | Ethernet configuration validation failed | error |
0A58 | Faulty Lock | Lock mechanism failed in Ethernet driver | error |
0A5A | PANIC (in–in_control) | PANIC condition in input control function | critical |
0B | Study INFO Initial Value Error | Study initialization | error |
0B | Invalid Parameter | Unspecified invalid parameter | warning |
0B | Impossible to delete for the study of the appointed Image is protected from delete | Delete image from protected study | warning |
0C | Image INFO Initial Value Error | Image initialization | error |
0C | Invalid Parameter (Image Display) | Image display parameter error | warning |
0D | The designated Image doesn't exist | Attempting to access image | error |
0D | Invalid Parameter (Image Data Read) | Error reading image data parameters | error |
0E | Number Full (SER/ACQ/IMG) | Image numbering capacity reached | critical |
0E | Unspecified Error | Unknown error condition | error |
0F | Unspecified Error | Unknown error condition | error |
10 | Time Out (Image Display) | Image display operation exceeded timeout | error |
10 | OD Off line | OD device operation | error |
1000000C | Insufficient System Space | File system space exhausted during I/O operation | error |
10000020 | CFMS CPU Time Out | CFMS processor fails to respond within timeout period | critical |
10000021 | CFMS CPU Fail | CFMS processor reports hardware failure or fatal error | critical |
10000082 | Invalid Function | I/O operation requests unsupported or undefined function code | error |
100000C7 | Internal IO Error | Unrecoverable internal I/O subsystem error | error |
100000CD | Disk Space Full | File system disk space exhausted during write operation | error |
100000D1 | Unrecoverable Device Error | Device hardware failure; data transfer cannot proceed | critical |
100000D2 | Data Compare Error | Read-back data does not match written data; checksum or ECC failure | error |
100000E1 | Device not ready | Device initialization or access attempt | error |
100000E2 | Device busy | Attempt to access device while processing | warning |
100000E3 | Data CRC error | Data read or write operation | error |
100000E6 | Timeout | Device operation exceeds time limit | error |
100000E8 | Checksum error | Data validation check failure | error |
100000EF | Bad sector | Attempt to access defective disk sector | critical |
100000F4 | Controller error | Disk controller malfunction | error |
10-1C | Error during DMP2 ASSY test | DMP2 assembly failed power-up self-test | critical |
10-33 | Error during PDC assembly test | PDC hardware test fails during power-up | critical |
$11 | SRAM write/read/verify test 1 failed | CPW Phase 1 self-test execution | error |
11 | OD Protected | OD write operation | warning |
11 | Time Out (Graphic Cursor) | Graphic cursor operation timed out | warning |
11H–1BH | File Processor (FMP1) ASSY hardware test failure | FMP1 ASSY tests during power-up sequence (phases 11H through 1BH) | error |
12 | Impossible to Allocate for Illegal Form of STUDY/IMAGE INFO | Study or image allocation with invalid format | error |
$12 | Bus error during ROM test | CPW Phase 1 self-test execution | error |
$13 | ROM checksum test failed | CPW Phase 1 self-test execution | error |
$14 | Interrupt handler write/read/verify test failed | CPW Phase 1 self-test execution | error |
$15 | Control/status register write/read/verify test failed | CPW Phase 1 self-test execution | error |
$16 | DMAC register write/read/verify test failed | CPW Phase 1 self-test execution | error |
$17 | Bus error during IPU2 mode test | CPW Phase 1 self-test execution | error |
$18 | CPW-DRAM write/read/verify test 1 failed | CPW Phase 1 self-test execution | error |
180000E1 | Device not ready | Device initialization or access attempt | error |
180000E3 | Data CRC error | Data read or write operation | error |
180000E6 | Timeout | Device operation exceeds time limit | error |
180000EF | Bad sector | Attempt to access defective disk sector | critical |
180000F4 | Controller error | Disk controller malfunction | error |
1A | Time Out (W/L Processing) | Window/Level processing exceeded timeout | warning |
1B | Time Out | Generic timeout condition | warning |
1C | Time Out | Generic timeout condition | warning |
1D | Time Out | Generic timeout condition | warning |
1E | Time Out | Generic timeout condition | warning |
$1F | CPW Phase 2 test failed (FDC, SCSIC, SRAM, DRAM, Calendar, DMA, or HD test) | CPW Phase 2 self-test execution | error |
1F | Time Out | Generic timeout condition | warning |
20 | Graphic Sequence Error | Graphics sequence protocol violation | error |
20-2C | Error during OVL2 ASSY test | OVL2 assembly failed power-up self-test | critical |
21 | Directive No. Error | Invalid directive number | error |
21H–22H | MRX ASSY test failure | MRX ASSY (Matrix control unit) test during power-up sequence | error |
22 | Odd Parameter Address | Parameter address misaligned | error |
23 | Device No. Error | Invalid device number in request | error |
24 | Invalid Request | Request format invalid | error |
25 | Invalid Request | Request format invalid | error |
26 | Invalid Request | Request format invalid | error |
27 | Invalid Parameter (Erase Processing) | Invalid erase operation parameter | warning |
28 | Invalid Parameter (Graphic DMA) | Invalid DMA parameter for graphics | error |
28XX0001 | Directive No. remains undecided | DMA directive number not resolved | error |
28XX0004 | Invalid memory address | DMA access to invalid memory address | error |
28XX0080 | Channel Busy | DMA channel currently in use | warning |
28XX0088 | Bus Error | System bus error during DMA operation | critical |
28XX00A0 | Time Out | DMA operation timeout | error |
29 | Invalid Parameter (Screen Save) | Invalid screen save parameter | warning |
2A | Invalid Parameter (Overlay Display) | Invalid overlay display parameter | warning |
2B | Invalid Parameter (Graphic Cursor) | Invalid cursor parameter | warning |
2C | Invalid Parameter (Report Cursor) | Invalid report cursor parameter | warning |
2D | Invalid Parameter (LED/Buzzer) | Invalid LED or buzzer control parameter | warning |
2D, 2E | Error during IFB2 ASSY test | IFB2 assembly failed power-up self-test | critical |
2E | Invalid Parameter | Unspecified invalid parameter | warning |
2F | Invalid Parameter | Unspecified invalid parameter | warning |
30 | Time Out (Erase Processing) | Erase operation exceeded timeout | warning |
$31 | ACRTC initialize test failed | DISP Phase 1 self-test execution | error |
31 | Time Out (Graphic DMA) | Graphic DMA operation timed out | error |
31H–39H | FMP2 or FMP3 ASSY test failure, or PACK/hard disk error | FMP2/FMP3 test or associated PACK and hard disk tests during power-up (ProSpeed/ProSpeed VX uses FMP2; ProSpeed Plus uses FMP3) | error |
$32 | ACRTC pattern RAM write/read/verify test failed | DISP Phase 1 self-test execution | error |
32 | Time Out (Screen Save Overlay) | Screen save overlay exceeded timeout | warning |
32-38 | Error during command write, status read or interrupt reception between FPU and DMP2 | FPU and DMP2 communication test failure | critical |
$33 | DISP interrupt test failed | DISP Phase 1 self-test execution | error |
33 | Time Out (Screen Save Image) | Screen save image exceeded timeout | warning |
34 | Time Out (Graphic Cursor) | Graphic cursor operation timed out | warning |
$34 | DISP control register write/read/verify test failed | DISP Phase 1 self-test execution | error |
$35 | Interrupt mask control register write/read/verify test failed | DISP Phase 1 self-test execution | error |
35 | Time Out | Generic timeout | warning |
36 | Time Out | Generic timeout | warning |
$36 | VSYNC interrupt test failed | DISP Phase 1 self-test execution | error |
37 | Time Out | Generic timeout | warning |
$37 | OVL plane memory write/read/verify test failed | DISP Phase 1 self-test execution | error |
$38 | ACRTC DMA test failed | DISP Phase 1 self-test execution | error |
38 | Time Out | Generic timeout | warning |
$39 | OVL plane control register write test failed | DISP Phase 1 self-test execution | error |
39 | Time Out | Generic timeout | warning |
3A | ACRTIC Command Error | ACRTIC protocol command failed | error |
3A, 3B | Error during expanded main data memory in FPU on local bus | FMD assembly memory test failure | critical |
3B | Graphic Sequence Error | Graphics sequence violation | error |
3C, 3D | Error during DAS buffer memory in FPU on local bus | DAS buffer memory test fails | critical |
3D-31, 39 | Error during main data memory in FPU on local bus | FCP3B assembly main data memory test failure | critical |
40 | Error during communication test between PDC and DMP4 via dual port RAM (PDC context) | PDC-DMP4 communication fails during power-up | error |
40 | Directive No. Error | Invalid directive number | error |
41 | Invalid Parameter Block Address | Parameter block address invalid | error |
$41 | IPU2 register access test failed | IPU2 self-test execution | error |
41-45 | Error during DMP4-PDC communication via dual port RAM | DMP4-PDC communication test fails | critical |
42 | Invalid Parameter | Parameter value invalid | warning |
$42 | IPU2 extended mode access test failed | IPU2 self-test execution | error |
43 | Invalid Request | Request format invalid | error |
$43 | IPU2 command area access test failed | IPU2 self-test execution | error |
$44 | IPU2 CPU mode access test failed | IPU2 self-test execution | error |
44 | Cannot Request Command | Command cannot be executed in current state | warning |
45 | Invalid Number of Characters | Character count mismatch in command | error |
$45 | IPU2 CPU extended mode access test failed | IPU2 self-test execution | error |
45H–47H | Communication test failure between FMP1 and DMP4 | FMP1 attempts to communicate with DMP4 (Scan/Display Processor) during boot | error |
$46 | IPU2 DMA test failed | IPU2 self-test execution | error |
46 | Invalid Parameter | Unspecified parameter error | warning |
46-48 | Error during test of accessing PDC RAM via DMP4 local bus | PDC RAM access test fails | critical |
$47 | IPU2 vector area fetch test failed | IPU2 self-test execution | error |
$48 | IPU2 i860 register access test failed | IPU2 self-test execution | error |
48H–4FH | Communication test failure between FMP1 and DMP2 | FMP1 attempts to communicate with optional DMP2 (Diagnostic Console III processor) during boot | error |
48YY01 | Directive No. Error | Invalid directive number in image data unpack | error |
48YY03 | Unpack Task is Busy | Image unpack task already running | warning |
$49 | IPU2 driver area access test failed | IPU2 self-test execution | error |
50 | Key Board Not Allocated | Keyboard device not allocated | error |
50 | Directive number error | Invalid or unrecognized display directive | warning |
50 | Error during DMP4 internal RAM test via DMP4 local bus (PDC context) | PDC detects DMP4 RAM error | critical |
5000F1 | Display Task is Busy | Display task already executing | warning |
50-55 | Error during communication test between FMP1 and DMP4 | FMP1-DMP4 communication fails during power-up | error |
51 | Channel Bus Response Time Out | Channel bus communication timeout | error |
52 | Hardware Error | Hardware communication failed | error |
53 | Invalid Parameter | Parameter invalid | warning |
5314YY30 | Target CPU halted | Target CPU execution halted or frozen | critical |
54 | Not Defined Area | Memory area not defined | error |
55 | Duplicate Define | Memory area defined twice | warning |
56 | Value Not Defined | Required value not set | warning |
57 | Invalid Area Position | Area position out of range | warning |
58 | Invalid Area Size | Area size invalid | warning |
59 | User Prime Display Function | User display function priority error | warning |
5A | DCB Graphic Flag Double Assigned | Graphic flag multiply assigned | warning |
5B | Invalid Parameter | Parameter invalid | warning |
5C | Invalid Parameter | Parameter invalid | warning |
5C | Error while displaying System Preparation | System display failure during boot sequence | critical |
5D | Invalid Parameter | Parameter invalid | warning |
5E | Invalid Parameter | Parameter invalid | warning |
5F | Invalid Parameter | Parameter invalid | warning |
60 | Read Event Flag Error | Event flag read operation failed | error |
60 | Abnormal termination due to level 7 interrupt before setting vector | Unexpected level 7 interrupt during vector initialization | critical |
60H | Abnormal termination due to Level 7 interrupt before vector is set | Unexpected interrupt at priority level 7 during early boot-up initialization | critical |
61 | Event Status Error | Event status invalid | warning |
62 | Event Bus Busy Error | Event bus communication blocked | warning |
62H | Hard disk or floppy disk error | Disk read/write or initialization failure detected during boot | error |
63 | Not Enable Magnetic Character Error | Magnetic character feature disabled | warning |
63H | Improper sector 0 information on hard disk | Boot sector or partition information corrupted or missing | error |
64 | Cancel Flag Error | Cancel flag error detected | warning |
64H | Unexpected interrupt other than bus or address error | Interrupt received from unexpected source during boot initialization | critical |
65 | Over Split Over Error | Data split exceeded limits | error |
65H | Unexpected interrupt due to bus or address error | Bus error or address error detected during boot-up | critical |
66 | Not Split Device Error | Device does not support split mode | error |
67 | Over Line Error | Line count exceeded | warning |
68 | Invalid Parameter Error | Parameter invalid | warning |
68 | Time out during image display | Image display operation exceeds timeout threshold | warning |
69 | Write FIFO Empty Time Out Error | Write FIFO timeout on empty | error |
6A | Write FIFO Ready Time Out Error | Write FIFO ready timeout | error |
6B | Read FIFO Ready Time Out Error | Read FIFO ready timeout | error |
6C | Read FIFO Empty Time Out Error | Read FIFO timeout on empty | error |
6D | Command End Time Out Error | Command completion timeout | error |
6E | Command End Time Out Error | Command completion timeout | error |
6F | BASIC Command Error | BASIC subsystem command failed | error |
70 | Command Error | Generic command execution failure | error |
70 | Unexpected interrupt during initial program loader execution | Interrupt received during IPL execution | critical |
70H | Unexpected interrupt while executing initial program loader | Interrupt during IPL execution phase | critical |
71 | Invalid Parameter Error | Parameter invalid for operation | warning |
72 | Configuration Error | System configuration is invalid | error |
72H | Operating system software not found in specified disk | IPL or boot routine unable to locate OS files during disk scan | error |
73 | OS loading timeout | Operating system load exceeds time limit | critical |
73 | Operation Timing Error | Operation timing constraint violated | error |
74 | Operation Timing Error | Operation timing constraint violated | error |
74H | Error in hard disk or floppy disk during OS loading | Disk read failure while loading operating system | error |
75 | Address Error | Memory address out of range | error |
76 | Address Error | Memory address invalid | error |
77 | Address Error | Address calculation failed | error |
78 | Address Error | Address out of bounds | error |
79 | Bus Error | Bus communication failed | error |
7A | Bus Error | Bus communication error | error |
7B | Bus Error | Bus transmission failed | error |
7C | Bus Error | Bus protocol violation | error |
7D | Count Error | Data count mismatch | error |
7E | Count Error | Count mismatch detected | error |
7F | Count Error | Count validation failed | error |
80 | Abort | Operation aborted by user or system | warning |
80 | Unexpected interrupt during initialize routine execution | Interrupt received during system initialization | critical |
8010 | Bus error | Invalid bus operation or transaction | critical |
8011 | Address error | Invalid memory address access | error |
8012 | Illegal instruction | Processor executes undefined or illegal instruction | critical |
8013 | Zero divide | Division by zero operation attempted | error |
80H | Unexpected interrupt during OS file initialization or execution | Interrupt during operating system initialization routine | critical |
81 | Unexpected interrupt due to bus error during memory clear | Bus error detected during memory clear operation | critical |
81 | Software Abort | Software abort condition triggered | error |
81H | Unexpected bus error interrupt during memory clear operation | Bus error detected while clearing system memory | critical |
82 | Software contradiction during initialize routine | Conflicting software state during system initialization | critical |
82 | Software Abort | Software abort condition | error |
82H | Software contradiction during initialization routine | OS file inconsistency or read error detected during boot initialization | error |
83 | Memory allocation error | Memory allocation failure during initialization | critical |
83 | Software Abort | Software abort triggered | error |
83H | Memory allocation error | Memory size or layout does not match expected configuration | error |
84 | Software Abort | Software abort | error |
85 | Software Abort | Software abort condition | error |
86 | Software Abort | Software abort triggered | error |
87 | Software Abort | Software abort | error |
88 | DMAC Ready Time Out Error | DMA controller ready timeout | error |
89 | DMAC Ready Time Out Error | DMA ready timeout | error |
8A | DMAC Ready Time Out Error | DMA timeout | error |
8B | DMAC Ready Time Out Error | DMA timeout | error |
8C | DMAC Ready Time Out Error | DMA timeout | error |
8D | DMAC Ready Time Out Error | DMA timeout | error |
8E | DMAC Ready Time Out Error | DMA timeout | error |
8E | ACRTS command error | Invalid or unsupported ACRTS command | error |
8F | Invalid Parameter Error | Parameter invalid | warning |
90 | Program looping or CPU halt; date/time entry display does not appear | CPU halt or infinite loop detected | critical |
90 | PDC ready for boot or error during PDC peripherals initialization; no DMP4 response (PDC context) | PDC initialization error or DMP4 response failure | critical |
90000001 | PINT (FPU to CPU Interrupt) | FPU to CPU interrupt signal | info |
90000004 | TIME OUT | FPU operation timeout | error |
90000005 | BUSY (FPU RUNNING) | FPU currently executing operation | info |
90000007 | ILLEGAL (Error Occurred in FPU) | FPU generated error condition | error |
90000009 | RESET ERROR (CAN NOT RESET) | FPU reset command failed | critical |
9000000B | INTERRUPT OVER (Interrupt Buffer Overflow) | FPU interrupt buffer exceeded capacity | error |
9000000C | The IPU is not idling | IPU not in idle state when operation requested | error |
90H | Program looping or CPU halt; no response on CRT monitor | CPU execution halted or endless loop detected; no CRT display | critical |
980000XX | User/Prime display function error | Display function call with invalid parameters or state | warning |
A0 | Abnormal termination due to insufficient memory, improper layout or missing task | Memory configuration error detected at startup | critical |
A0 | Boot-up failure (PDC) | PDC fails to boot during power-up | critical |
A0000001 | I.D No. Error | RAWCTL identifier number invalid or missing | error |
A0000003 | Transfer Byte Error | Byte transfer validation failed | error |
A0000005 | Size Error | Invalid data size in RAWCTL command | error |
A0H | Abnormal termination due to insufficient memory or improper memory layout | System detects inadequate installed memory or incorrect memory mapping | error |
A1 | No response from DMP4 to PDC boot request (PDC context) | DMP4 fails to respond to boot request | critical |
A1 | Invalid Parameter | Parameter validation failure in display subsystem | error |
A1 | Abnormal termination due to improper memory layout | Duplicate task or missing task detected during initialization | error |
A1H | Abnormal termination due to improper memory layout or configuration | Memory layout error, duplicate task, or missing task detected during initialization | error |
A2 | Not Defined Area | Attempt to access undefined display area | warning |
A3 | Duplicate Define | Duplicate area definition detected | warning |
A3 | Error during PDC boot-up by DMP4 | PDC boot initialization fails | critical |
A8000001 | Internal logic error (IFM Display Error) | IFM display subsystem logic fault | error |
B0 | File read failure (PDC) | PDC fails to read file | critical |
B1 | Error during PDC data file read | PDC fails to read data file | critical |
B7 | Read Event Flag Error | Event flag read operation failed | error |
B8 | Event Status Error | Event status check failed | error |
C0 | No response from DMP4 to PDC boot-up completion message | DMP4 does not respond after PDC boot-up | critical |
C0 | Write FIFO Empty Time Out Error | Write FIFO timeout during empty condition | error |
C001 | Station number error | Invalid station or model number parameter | warning |
C1 | Initialize failure of touch panel | Touch panel fails to initialize | warning |
C-1 | Function No. Error | Invalid function number | error |
C-2 | Station No. Error (It is impossible to change to Model/Machine No.) | Invalid or incompatible station number | error |
C2 | AGDC error | AGDC hardware or function failure | critical |
C3 | Font composition error | Font file corruption or missing | warning |
C-3 | Study No. Error (except for the numeric data) | Invalid study number format or value | error |
C-4 | Series No. Error (except for the numeric data) | Invalid series number | error |
C-5 | ACQ No. Error (except for the numeric data) | Invalid acquisition number | error |
C5 | Command End Time Out Error | Command execution timeout | critical |
C-6 | IMG No. Error (except for the numeric data) | Invalid image number | error |
C-7 | There is no STD in STD INFO which is ready | Accessing uninitialized study information | error |
C-8 | There is no IMG in IMG INFO which is ready | Accessing uninitialized image information | error |
C-9 | The number of Image INFO Block is except for (or ) | Invalid image info block count | error |
C-A | The number of List is less than 1 | Empty list operation | warning |
C-B | Completion Type Error | Invalid completion type value | error |
C-C | Flag Error (Mode etc.) | Invalid flag or mode setting | error |
C-D | It is not Old in spite of the other machine | Version mismatch between machines | warning |
C-E | Search Mode is 0 and Model/Machine No. is 0 | Invalid search parameters | error |
C.E. | Communication Error alarm | Communications failure with motor control | warning |
C-F | Image size is 0 | Zero image size parameter | error |
CPU packet error | CPU packet writing or transmit error | Communication failure during CPU-ETC data exchange | critical |
D0 | Bus error from accessing nonexistent memory or executing inadequate instruction | Power-up sequence attempts access to invalid memory address or executes bad instruction | critical |
D0H | Bus error due to accessing nonexistent memory or inadequate instruction | Bus error during memory access or instruction execution | critical |
D1 | Address error from word reference to odd address | Processor attempts word-aligned access to odd memory address | critical |
D1 | Configuration Error | System configuration validation failed | error |
D1H | Address error due to word reference to odd address | CPU attempts to access word (16-bit) at odd address | critical |
D2 | Operation Timing Error | Timing constraint violation during operation | error |
D2-D8 | Exception from incorrect instruction or corrupted memory | Invalid instruction executed or memory access violation | critical |
D2H–D8H | Unexpected interrupt due to incorrect instruction or corrupted memory | Interrupt from incorrect or corrupted instruction during execution | critical |
D4 | Address Error | Invalid memory address access | error |
D8 | Bus Error | System bus communication failure | critical |
E0 | Abnormal termination due to OS-related task abort | Operating system task unexpectedly terminated | error |
E0 | Abort | System abort requested | critical |
E005 | Lower order not deleted during study pointer delete | Study pointer deletion with undeletedsubordinatedata | error |
E0H | Abnormal termination due to OS-related task abort | Operating system task aborted during execution | error |
E1 | Software Abort | Software-initiated abort | critical |
E1 | Abnormal operation system | Operating system error condition detected | error |
E-1 | Event Code Error | Invalid event code | error |
E-2 | Sub Code Error | Invalid subcode | error |
E270 | Undefined command received by generator | Generator receives command not recognized by system | error |
E271 | Parameter out of allowable range | Generator receives parameter with invalid value | error |
E272 | Parameter modification not allowed in current phase | System attempts to change exposure parameters in wrong phase | error |
E273 | Phase change not allowed in current phase | System attempts invalid phase transition | error |
E274 | Exposure command received at wrong timing | Generator receives exposure command when not ready | error |
E-3 | This was already registered during Study INFO Allocate | Duplicate registration during study allocation | warning |
E-4 | This was already registered during Allocate in Image INFO File | Duplicate during image info allocation | warning |
E-6 | LOWER ORDER is not deleted during Study Pointer Delete | Study pointer delete without lower order removal | error |
E-7 | LOWER ORDER is not deleted during Study INFO Delete | Study info delete without lower order removal | error |
E-8 | LOWER ORDER is not deleted during Image INFO Delete | Image info delete without lower order removal | error |
E8 | DMAC Ready Time Out Error | DMA controller ready signal timeout | error |
E-9 | SCBITOR Error during Study INFO Delete | SCBITOR error in study deletion | error |
E-A | SCBITOR Error during Image PTR/File Delete | SCBITOR error during image deletion | error |
E-B | The area in Image INFO File full | Image info file storage exhausted | error |
E-C | This was already registered during Image INFO Allocate | Duplicate during image info allocation | warning |
E-D | Scan or Load is different from the position in File during Image INFO Allocate | Scan/Load position mismatch | warning |
E/e01 | 550 VDC Supply Error | Correct 550 or 750 VDC could not be measured in x-ray generator | error |
E/e02 | 15V_SAFE Voltage Failure | Power supply voltage for optical devices in KV Inverter and CTVRC out of specified range (13.5–15.5 V) | error |
E/e03 | CTVRC Short-circuit Error | Short-circuit (shoot-through) detected between safety loop closure and 550/750 VDC confirmation | critical |
E/e11 | Rotor Controller Error | Rotor did not start normally or 550/750 VDC supply failed during rotor startup | error |
E/e12 | Rotor Acceleration Error | Specific rotor speed not attained within specified time | error |
E/e16 | Stator Current Error | Current in either stator winding outside specified range; phase-specific (2=acceleration, 3=run, 7=brake) | error |
E/e18 | Stator Current Unbalance | Difference in currents between two windings exceeded specified values; phase-specific (2=accel, 3=run, 7=brake) | error |
E/e21 | Filament Overcurrent | Filament heating current exceeded specification | error |
E/e22 | No Filament Current | Filament heating current not detected | error |
E/e23 | Small Focus Change Error | Filament focus position drifted beyond specification | error |
E/e24 | Invalid Power Supply Voltage For Filament Heating | Filament heating supply voltage out of specification | error |
E/e25 | Filament Inverter Error | Filament inverter circuit failure or malfunction | error |
E/e31 | Tube Current Accuracy Error | X-ray tube currents measured outside specifications | error |
E/e32 | Tube Voltage Accuracy Error | X-ray tube voltages (HV tank output) outside specifications | error |
E/e33 | Spit | Spits detected during exposure at rate exceeding 30 spits/s | warning |
E/e34 | Exposure Overtime | Exposure time exceeded 105% of set time | error |
E/e35 | Anode Over MA | Tube current measured on anode side outside specifications | error |
E/e36 | Cathode Over MA | Tube current measured on cathode side outside specifications | error |
E/e37 | Anode Over KV | Tube anode voltage from HV tank measured above specification | error |
E/e38 | Cathode Over KV | Tube cathode voltage from HV tank measured above specification | error |
E/e39 | Anode Inverter Shoot-through | Surge currents detected in anode inverter | error |
E/e40 | Cathode Inverter Shoot-through | Surge currents detected in cathode inverter | error |
E/e41 | Anode Inverter Overcurrent | Output currents from anode inverter outside specifications | error |
E/e42 | Cathode Inverter Overcurrent | Output currents from cathode inverter outside specifications | error |
E/e43 | HV_ON Error | HV_ON signal (KV >75% of set) became active without exposure command from system | error |
E/e44 | KV Unbalance (Negative) | (Cathode KV – Anode KV) greater than 5 kV | error |
E/e45 | KV Unbalance (Positive) | (Anode KV – Cathode KV) greater than 5 kV | error |
E/e48 | Safety Loop Control Error (Generator Side) | Safety loop detected as open on generator side | critical |
E/e49 | Safety Loop Control Error (System Side) | Safety loop detected as open on system side | critical |
E/e50 | EPROM Checksum Error | Checksum error during EPROM test in background; all generator phases | error |
E/e51 | RAM Checksum Error | Checksum error during RAM test in background; all generator phases | error |
E/e52 | EEPROM Write Error | Write operation into EEPROM did not succeed | error |
E/e53 | EEPROM Checksum Error | Checksum error during EEPROM test at power-up; EEPROM new, replaced, or write failed | warning |
E/e60 | Communication Error | System does not send ACK response after generator transmits communication data | error |
E/e61 | System Request Error | Generator does not receive periodic Request Commands from system during exposure at correct timing | error |
E/e81 | 550 VDC Supply Error at Exposure Preparation Start | Correct 550/750 VDC not measured within 1.2 seconds after safety loop closure before exposure | error |
E/e82 | Exposure Command Timeout Error | No exposure command received within 90 seconds of phase 3 (Exposure Ready) | error |
E/e83 | KV Rise Timeout | Tube voltage did not reach specified minimum within specified time after KV Inverter start | error |
E/e84 | KV Fall Timeout | Tube voltage did not lower to specified level within specified time after KV Inverter shutdown | error |
EF | Abnormal operation system | System operation exception detected | warning |
EFH | Abnormal operation of entire system | System detects abnormal operation status during initialization or execution | error |
ER-001 | System Error | System failure; Error of Directive/System Subroutine etc. | critical |
ER-002 | Undefined Event Received | There was a failure in the Event Data (Communication message) | error |
ER-003 | Abnormal Termination Detected | Task was terminated abnormally | error |
ER-004 | Task Termination | EDSP detected the termination of Task | error |
ER-099 | TREND Task Error | Error occurred when Error Message was about to register to Disk at TREND Task | error |
ER-100 | Aperture Error | Aperture mechanism communication or positioning error | error |
ER-101 | Scan Error | Scan error detected during helical or scout scan operation | error |
ER-102 | Gantry Error | Gantry operation failure or communication error | error |
ER-103 | XG Processor Communication Error | X-ray generator processor communication failure | error |
ER-104 | OGP Event Error | OGP processor event or trigger error | error |
ER-105 | Gantry Processor Communication Error | Communication failure between gantry processor and system | error |
ER-106 | Tilt Error | Gantry tilt position outside acceptable range | warning |
ER-107 | Table Error | Table positioning or movement failure | error |
ER-108 | TGP not System | Gantry rotation switch on TGP board not in System position | warning |
ER-109 | Cradle Error | Cradle positioning, latch, or movement failure | error |
ER-110 | Scan Processor Communication Error | Communication failure between scan processor and system | error |
ER-111 | Table Processor Communication Error | Communication failure between table processor and system | error |
ER-112 | TGP Task Time Out | TGP task execution exceeded time limit | error |
ER-115 | TGE Response Timeout | TGE failed to respond within timeout period for various operations | error |
ER-117 | XG Error | X-ray generator error during various operational states | critical |
ER-118 | SCNCCTL Sequence Error | Scan control sequence violation detected | error |
ER-119 | Study No. Error | Study number is not valid ASCII numeric data | error |
ER-120 | Cooling Wait Too Long | Cooling wait time exceeded specified duration | warning |
ER-121 | Next Scan Preparation Time Out | Scan task failed to complete preparation or return status by start time | error |
ER-122 | X-Ray Zero Detect | DAS detector data is zero during scan | error |
ER-130 | Comm. Write Reg. Ans. Net. Wait | Write register answer interrupt received without corresponding request | warning |
ER-131 | Comm. Receive Buffer Over | Communication receive buffer overflow condition | error |
ER-132 | Comm. Transmit Buffer Over | Communication transmit buffer overflow condition | error |
ER-133 | Comm. Write Reg. Ans. Timeout | Write register answer not received within timeout period | error |
ER-135 | PNLCTL Sequence Error | Panel control sequence violation during system operation | error |
ER-136 | IP Error | Interface processor error or peripheral device failure | error |
ER-137 | Audio Communication Error | Autovoice function error or 6388 audio processor communication failure | warning |
ER-138 | TGP Communication Error | Communication error between MP on TGP and IP on OC interface | error |
ER-139 | DMP4 - IP Communication Error | Communication error between DMP4 and IP on OC interface | error |
ER-140 | Anode Temperatures Over | Tube anode temperature exceeded safe operating limit | critical |
ER-141 | Case Temperature Over | Tube case temperature exceeded safe operating limit | critical |
ER-151 | Scan Timeout | DAS data collection did not complete within timeout period | error |
ER-152 | Warm up Error | Detector warm-up self-test failed | error |
ER-153 | Initialize Air Data Error | Initial air calibration data failed validation | error |
ER-154 | DBM Full | DBM memory filled with raw scan data | warning |
ER-160 | Event Sequence Error | Error in event sequence of data, OK/NG status from offline or soft key | error |
ER–160 | PDC Error (Plazma Display, Touch Panel, etc.) | Errors related to the PDC board | error |
ER–170 | Data Compare Error | Test Pattern Data mismatch in DAS Data Transfer Test | error |
ER–201 | Recon Timeout | Image reconstruction fails to complete within timeout period | error |
ER–202 | Invalid Parameter | Parameter conversion error during operator-CPU communication | error |
ER–203 | View Data Corrected | DAS data transfer error detected during image reconstruction | warning |
ER–204 | View Data Error Not Corrected | DAS data transfer error detected during reconstruction; views cannot be corrected | error |
ER–400 | Duplicate Study ID Deleted | Duplicate STUDY IDs found in STUDY POINTER area | warning |
ER–401 | No Study Inf. ID Deleted | STUDY POINTER lacks corresponding STUDY INF. entry | warning |
ER–402 | Illegal Study Eye Catcher | STUDY INF. EYE CATCHER field differs from expected signature | warning |
ER–403 | Illegal Study ID Deleted | STUDY ID in STUDY INF. differs from STUDY POINTER contents | warning |
ER–404 | Study in Old Area Deleted | STUDY POINTER in old area chains to STUDY INF. in new area | warning |
ER–405 | Old Study Inf. Study Deleted | STUDY POINTER in new area chains to STUDY INF. in old area | warning |
ER–406 | Same Area Inf. Study Deleted | STUDY POINTER with duplicate area found in STUDY INF. | warning |
ER–407 | No Buffer for Image Inf. | System cannot allocate memory buffer to read IMGINF | error |
ER–408 | Image Inf. Size Over | IMGINF data exceeds allocated buffer size | error |
ER–409 | Illegal Image Inf Eye Catcher | IMGINF EYE CATCHER field signature is invalid | warning |
ER–410 | Illegal Study No Image Deleted | STUDY NO. differs between STUDY INF. and IMAGE INF. | warning |
ER–411 | Duplicate Image Inf Deleted | Duplicate IMAGE IDs found in IMGINF | warning |
ER–412 | No Image Data Image Inf Deleted | IMAGE DATA not found for corresponding IMGINF entry | warning |
ER–413 | Illegal Study ID Image Deleted | STUDY ID mismatch between IMAGE INF. and IMAGE POINTER | warning |
ER–414 | Illegal Study ID Image Deleted | IMAGE ID mismatch between IMAGE INF. and IMAGE POINTER | warning |
ER–415 | Same Area Image Inf. Deleted | Duplicate area detected in IMAGE DATA storage | warning |
ER–416 | Image Data Area Size Over | Required IMAGE DATA storage exceeds available space | error |
ER–417 | Duplicate Image Pointer Deleted | Duplicate IMAGE POINTER found with same area IMGINF | warning |
ER–418 | Image Pointer Area Size Over | Required IMAGE POINTER storage exceeds available space | error |
ER–419 | Same Area Image Inf Deleted | Two IMGINF entries found in same storage area | warning |
ER–420 | Image Inf Area Size Over | Required IMGINF storage exceeds available buffer | error |
ER–421 | No Image Inf Study Inf Deleted | STDINF entry exists with no associated IMGINF | warning |
ER–422 | Study Inf Area Size Over | Required STDINF storage exceeds available space | error |
ER–430 | Event Code Error | IMAGE FILE MANAGEMENT PROCESSOR received illegal event | error |
ER–431 | Event Sequence Error | Event received at illegal timing during IMAGE FILE MANAGEMENT operation | error |
ER–432 | Logical Error | Logic error in IMAGE FILE MANAGEMENT processor operation | error |
ER–433 | Image Already Stored | Image attempted for storage already exists on MT or FD | warning |
ER–434 | Image Already Exist | Image retrieval attempted for image already in system memory | warning |
ER–435 | Image Not Found | Image retrieval or store operation fails; image not on requested disk or device | error |
ER–436 | Image in Scan Study, No Load | Cannot load image study number that matches current scanning study | warning |
ER–437 | OD Study Incorrect, No Store | Only Study Inf. OR only Image Inf. exists; incomplete study cannot be stored to OD | warning |
ER–440 | OD Study Inf Nothing | Study has Image Inf. file but OD cannot find corresponding image data | error |
ER-440 | OD Study information nothing | OD operation interrupted by unexpected system shutdown | error |
ER-441 | OD Image information nothing | OD operation interrupted by unexpected system shutdown | error |
ER–441 | OD Image Inf. Nothing | Study exists on OD but Image Inf. file missing; study cannot be accessed | error |
ER–442 | OD Study Inf. Incorrect | Image count mismatch between Study Inf. and actual Image Inf. file entries on OD | warning |
ER-442 | OD Study information incorrect | OD operation interrupted by unexpected system shutdown | error |
ERRG | Gantry Processor error | RAM or ROM check error, gantry azimuth initialize failure | error |
ERRG LED ON | Gantry Processor detected error and hanged up | RAM/ROM/servo error or gantry rotation initialization failure | error |
ERRM | Management Processor error | RAM or ROM check error on TGP board | error |
ERRM LED ON | Management Processor detected error and hanged up | RAM/ROM failure during power-on | error |
ERROR XXXXXXXX | Unspecified system or hardware error occurred | System encounters internal error during file access, processing, or display operation | critical |
ERRS LED ON | OGP Scan Processor error detected | RAM/ROM/communication failure during power-on or operation | error |
ERRT | Table Processor error | RAM or ROM check error in Table Processor | error |
ERRT LED ON | Table Processor detected error and hanged up | RAM/ROM failure or display check failure during power-on | error |
F0 | Time Out Error | General timeout in system operation | error |
F001 | (Memory Space) Table full | Memory management table overflow | error |
F012 | (Packet transmission) Busy | Packet transmission queue full or busy | warning |
F01D | (Packet transmission) Failed | Packet transmission operation failed | error |
F022 | (Packet reception) Busy | Packet reception handler busy or overloaded | warning |
F02D | (Packet reception) Failed | Packet reception operation failed | error |
F101 | Initialization table full | Ethernet initialization task encounters full table condition | warning |
F102 | Initialization busy | Ethernet board busy during initialization | warning |
F103 | Initialization abnormal pattern | Unexpected data pattern during initialization | error |
F104 | Initialization over range | Parameter exceeds valid range during initialization | error |
F106 | Initialization request doubled | Duplicate initialization request received | warning |
F107 | Initialization abnormal designated address | Invalid address specified during initialization | error |
F108 | Initialization not found | Expected initialization resource not detected | error |
F10C | Initialization retry counts exceed specifications | Multiple initialization attempts fail | critical |
F10D | Initialization failed | Ethernet board initialization does not complete | error |
F10E | Initialization not supported | Initialization function unavailable on this hardware | warning |
F10F | Initialization not ready | Ethernet board not ready for initialization | warning |
F111 | Transmission table full | Ethernet transmission queue overflow | warning |
F112 | Transmission busy | Ethernet board occupied during transmission | warning |
F113 | Transmission abnormal pattern | Invalid data pattern in transmission buffer | error |
F114 | Transmission over range | Transmission data exceeds buffer capacity | error |
F116 | Transmission request doubled | Duplicate transmission request detected | warning |
F117 | Transmission abnormal designated address | Invalid destination address for transmission | error |
F118 | Transmission not found | Transmission endpoint not detected | error |
F11C | Transmission retry counts exceed specifications | Multiple transmission attempts fail | critical |
F11D | Transmission failed | Ethernet transmission does not complete | error |
F11E | Transmission not supported | Transmission mode unavailable | warning |
F11F | Transmission not ready | Ethernet board not ready to transmit | warning |
F121 | Reception table full | Ethernet reception buffer overflow | warning |
F122 | Reception busy | Ethernet receiver occupied | warning |
F123 | Reception abnormal pattern | Invalid pattern in received data | error |
F124 | Reception over range | Received data exceeds buffer size | error |
F126 | Reception request doubled | Duplicate reception request | warning |
F127 | Reception abnormal designated address | Invalid source address in received data | error |
F128 | Reception not found | Reception endpoint not detected | error |
F12C | Reception retry counts exceed specifications | Multiple reception attempts fail | critical |
F12D | Reception failed | Ethernet reception incomplete | error |
F12E | Reception not supported | Reception mode unavailable | warning |
F12F | Reception not ready | Ethernet receiver not initialized | warning |
F2 | Cannot Display During Horizontal Blanking | Display refresh attempted during horizontal blanking interval | warning |
F201 | Initialization table full | Second Ethernet interface initialization queue overflow | warning |
F202 | Initialization busy | Second Ethernet interface busy | warning |
F203 | Initialization abnormal pattern | Abnormal data during second interface init | error |
F204 | Initialization over range | Parameter exceeds range on second interface | error |
F206 | Initialization request doubled | Duplicate request on second interface | warning |
F207 | Initialization abnormal designated address | Invalid address on second interface | error |
F208 | Initialization not found | Expected resource missing on second interface | error |
F20C | Initialization retry counts exceed specifications | Multiple failures on second interface init | critical |
F20D | Initialization failed | Second interface initialization fails | error |
F20E | Initialization not supported | Function unavailable on second interface | warning |
F20F | Initialization not ready | Second interface not ready | warning |
F211 | Transmission table full | Transmission queue overflow on second interface | warning |
F212 | Transmission busy | Second interface transmitter occupied | warning |
F213 | Transmission abnormal pattern | Bad data pattern in transmission | error |
F214 | Transmission over range | Transmission data too large | error |
F216 | Transmission request doubled | Duplicate transmission request | warning |
F217 | Transmission abnormal designated address | Invalid destination address | error |
F218 | Transmission not found | Endpoint not detected | error |
F21C | Transmission retry counts exceed specifications | Multiple transmission failures | critical |
F21D | Transmission failed | Transmission incomplete on second interface | error |
F21E | Transmission not supported | Mode unavailable | warning |
F21F | Transmission not ready | Transmitter not ready | warning |
F221 | Reception table full | Reception buffer overflow on second interface | warning |
F222 | Reception busy | Receiver occupied on second interface | warning |
F223 | Reception abnormal pattern | Invalid pattern in received data | error |
F224 | Reception over range | Received data too large | error |
F226 | Reception request doubled | Duplicate reception request | warning |
F227 | Reception abnormal designated address | Invalid source address | error |
F228 | Reception not found | Reception endpoint missing | error |
F22C | Reception retry counts exceed specifications | Multiple reception failures | critical |
F22D | Reception failed | Reception incomplete on second interface | error |
F22E | Reception not supported | Mode unavailable on second interface | warning |
F22F | Reception not ready | Receiver not initialized on second interface | warning |
F911 | Ethernet board initialization table full | Ethernet board init queue overflow | warning |
F912 | Ethernet board initialization busy | Ethernet board busy during init | warning |
F913 | Ethernet board initialization abnormal pattern | Abnormal data during board init | error |
F914 | Ethernet board initialization over range | Parameter exceeds range during init | error |
F916 | Ethernet board initialization request doubled | Duplicate init request on board | warning |
F917 | Ethernet board initialization abnormal address | Invalid address during board init | error |
F918 | Ethernet board initialization not found | Expected resource missing from board | error |
F91C | Ethernet board initialization retry counts exceed specifications | Multiple init failures on board | critical |
F91D | Ethernet board initialization failed | Board initialization does not complete | error |
F91E | Ethernet board initialization not supported | Init function unavailable on board | warning |
F91F | Ethernet board initialization not ready | Board not ready for init | warning |
F921 | Ethernet board queue transmission table full | Queue transmission buffer overflow | warning |
F922 | Ethernet board queue transmission busy | Queue transmission in progress | warning |
F923 | Ethernet board queue transmission abnormal pattern | Invalid data in queue transmission | error |
F924 | Ethernet board queue transmission over range | Transmission data exceeds capacity | error |
F926 | Ethernet board queue transmission request doubled | Duplicate queue transmission request | warning |
F927 | Ethernet board queue transmission abnormal address | Invalid address in queue transmission | error |
F928 | Ethernet board queue transmission not found | Transmission endpoint missing | error |
F92C | Ethernet board queue transmission retry counts exceed specifications | Multiple transmission failures in queue | critical |
F92D | Ethernet board queue transmission failed | Queue transmission incomplete | error |
F92E | Ethernet board queue transmission not supported | Transmission mode unavailable | warning |
F92F | Ethernet board queue transmission not ready | Transmission not initialized | warning |
F931 | Ethernet board mail transmission table full | Mail transmission queue overflow | warning |
F932 | Ethernet board mail transmission busy | Mail transmission in progress | warning |
F933 | Ethernet board mail transmission abnormal pattern | Invalid data in mail transmission | error |
F934 | Ethernet board mail transmission over range | Mail data exceeds buffer capacity | error |
F936 | Ethernet board mail transmission request doubled | Duplicate mail transmission request | warning |
F937 | Ethernet board mail transmission abnormal address | Invalid destination in mail transmission | error |
F938 | Ethernet board mail transmission not found | Destination not detected | error |
F93C | Ethernet board mail transmission retry counts exceed specifications | Multiple mail transmission failures | critical |
F93D | Ethernet board mail transmission failed | Mail transmission incomplete | error |
F93E | Ethernet board mail transmission not supported | Transmission mode unavailable | warning |
F93F | Ethernet board mail transmission not ready | Transmission not initialized | warning |
F941 | Ethernet board temporary stop table full | Stop command queue overflow | warning |
F942 | Ethernet board temporary stop busy | Stop operation in progress | warning |
F943 | Ethernet board temporary stop abnormal pattern | Invalid data in stop command | error |
F944 | Ethernet board temporary stop over range | Stop parameter exceeds range | error |
F946 | Ethernet board temporary stop request doubled | Duplicate stop command | warning |
F947 | Ethernet board temporary stop abnormal address | Invalid target address | error |
F948 | Ethernet board temporary stop not found | Target not detected | error |
F94C | Ethernet board temporary stop retry counts exceed specifications | Multiple stop command failures | critical |
F94D | Ethernet board temporary stop failed | Stop command unsuccessful | error |
F94E | Ethernet board temporary stop not supported | Stop function unavailable | warning |
F94F | Ethernet board temporary stop not ready | Stop not initialized | warning |
F951 | Ethernet board operation resumption table full | Resume queue overflow | warning |
F952 | Ethernet board operation resumption busy | Resume operation in progress | warning |
F953 | Ethernet board operation resumption abnormal pattern | Invalid data in resume command | error |
F954 | Ethernet board operation resumption over range | Resume parameter exceeds range | error |
F956 | Ethernet board operation resumption request doubled | Duplicate resume command | warning |
F957 | Ethernet board operation resumption abnormal address | Invalid target address for resume | error |
F958 | Ethernet board operation resumption not found | Resume target not detected | error |
F95C | Ethernet board operation resumption retry counts exceed specifications | Multiple resume failures | critical |
F95D | Ethernet board operation resumption failed | Resume command unsuccessful | error |
F95E | Ethernet board operation resumption not supported | Resume function unavailable | warning |
F95F | Ethernet board operation resumption not ready | Resume not initialized | warning |
F961 | Ethernet board task deletion table full | Deletion queue overflow | warning |
F962 | Ethernet board task deletion busy | Deletion operation in progress | warning |
F963 | Ethernet board task deletion abnormal pattern | Invalid data in deletion command | error |
F964 | Ethernet board task deletion over range | Deletion parameter exceeds range | error |
F966 | Ethernet board task deletion request doubled | Duplicate deletion request | warning |
F967 | Ethernet board task deletion abnormal address | Invalid target for deletion | error |
F968 | Ethernet board task deletion not found | Target not located | warning |
F96C | Ethernet board task deletion retry counts exceed specifications | Multiple deletion failures | critical |
F96D | Ethernet board task deletion failed | Task deletion unsuccessful | error |
F96E | Ethernet board task deletion not supported | Deletion function unavailable | warning |
F96F | Ethernet board task deletion not ready | Deletion not initialized | warning |
F971 | Ethernet board task load start table full | Task load queue overflow | warning |
F972 | Ethernet board task load start busy | Task load in progress | warning |
F973 | Ethernet board task load start abnormal pattern | Invalid data in task load | error |
F974 | Ethernet board task load start over range | Load data exceeds capacity | error |
F976 | Ethernet board task load start request doubled | Duplicate task load request | warning |
F977 | Ethernet board task load start abnormal address | Invalid load address | error |
F978 | Ethernet board task load start not found | Load target not located | error |
F97C | Ethernet board task load start retry counts exceed specifications | Multiple task load failures | critical |
F97D | Ethernet board task load start failed | Task load did not complete | error |
F97E | Ethernet board task load start not supported | Task load function unavailable | warning |
F97F | Ethernet board task load start not ready | Task load not initialized | warning |
F981 | Ethernet board next operation mode setting table full | Mode setting queue overflow | warning |
F982 | Ethernet board next operation mode setting busy | Mode setting in progress | warning |
F983 | Ethernet board next operation mode setting abnormal pattern | Invalid data in mode setting | error |
F984 | Ethernet board next operation mode setting over range | Mode parameter exceeds valid range | error |
F986 | Ethernet board next operation mode setting request doubled | Duplicate mode setting request | warning |
F987 | Ethernet board next operation mode setting abnormal address | Invalid mode target address | error |
F988 | Ethernet board next operation mode setting not found | Mode target not located | error |
F98C | Ethernet board next operation mode setting retry counts exceed specifications | Multiple mode setting failures | critical |
F98D | Ethernet board next operation mode setting failed | Mode setting unsuccessful | error |
F98E | Ethernet board next operation mode setting not supported | Mode setting unavailable | warning |
F98F | Ethernet board next operation mode setting not ready | Mode setting not initialized | warning |
F991 | Ethernet board memory access table full | Memory access queue overflow | warning |
F992 | Ethernet board memory access busy | Memory access in progress | warning |
F993 | Ethernet board memory access abnormal pattern | Invalid data pattern in memory access | error |
F994 | Ethernet board memory access over range | Access address exceeds memory range | error |
F996 | Ethernet board memory access request doubled | Duplicate memory access request | warning |
F997 | Ethernet board memory access abnormal address | Invalid memory address specified | error |
F998 | Ethernet board memory access not found | Memory location not accessible | error |
F99C | Ethernet board memory access retry counts exceed specifications | Multiple memory access failures | critical |
F99D | Ethernet board memory access failed | Memory access unsuccessful | error |
F99E | Ethernet board memory access not supported | Memory access type unavailable | warning |
F99F | Ethernet board memory access not ready | Memory not initialized | warning |
FA71 | Task load start table full | System task load queue overflow | warning |
FA72 | Task load start busy | System task load in progress | warning |
FA73 | Task load start abnormal pattern | Invalid data in system task load | error |
FA74 | Task load start over range | Task load data exceeds capacity | error |
FA76 | Task load start request doubled | Duplicate system task load request | warning |
FA77 | Task load start abnormal address | Invalid system task load address | error |
FA78 | Task load start not found | System task not located | error |
FA7C | Task load start retry counts exceed specifications | Multiple system task load failures | critical |
FA7D | Task load start failed | System task load did not complete | error |
FA7E | Task load start not supported | Task load function unavailable | warning |
FA7F | Task load start not ready | System task not initialized | warning |
FA91 | System memory access table full | System memory access queue overflow | warning |
FA92 | System memory access busy | System memory access in progress | warning |
FA93 | System memory access abnormal pattern | Invalid pattern in system memory access | error |
FA94 | System memory access over range | System memory address exceeds range | error |
FA96 | System memory access request doubled | Duplicate system memory access request | warning |
FA97 | System memory access abnormal address | Invalid system memory address | error |
FA98 | System memory access not found | System memory location not accessible | error |
FA9C | System memory access retry counts exceed specifications | Multiple system memory access failures | critical |
FA9D | System memory access failed | System memory access unsuccessful | error |
FA9E | System memory access not supported | System memory access type unavailable | warning |
FA9F | System memory access not ready | System memory not initialized | warning |
F.E. | Circuit Breaker Off alarm | Circuit breaker opened due to overcurrent | error |
FF | Initialize failure of plasma display (PDC) | PDC fails to initialize display during power-up | critical |
FILE NOTHING | Specified file does not exist in system | User enters name of file that is not stored in system memory | error |
INVALID CURSOR | Cursor positioned out of valid range or incorrectly placed | User attempts ROI, MAGNIFY, PROFILE (H), PROFILE (V), HISTOGRAM, NUMERICAL, or WHERE functions with cursor positioned outside image bounds | warning |
INVALID ENTRY | Unacceptable parameter or value entered in menu | User enters data outside acceptable format or range for non-RANGE menus | warning |
INVALID FILE | File name format is incorrect or file is corrupted | User enters file name with incorrect spelling or format, or file data is corrupted | error |
IP/Ethernet address error | IP address or ethernet address not set | ETC initialization without valid network configuration | error |
LANCE error | LANCE initiate error, initial error of memory for LANCE, or LANCE initial timeout | Ethernet controller initialization failure | critical |
Memory error | Work area insufficient or file read error | Memory allocation failure or file system access error during initialization | critical |
MS-000 | Abort Button on | Abort Button has been pressed | info |
MS-001 | Start Timeout | Scan Start Timeout (Didn't press the [Start] button in time) | warning |
MS-002 | Insert KEY-FD | "Key" floppy diskette is not inserted | error |
MS-003 | X-Ray Over Range Detect | X-Ray DATA (DAS Data) overrange | warning |
MS-004 | FPU Busy | FPU is busy | info |
MS-005 | Tube Warm up End | Tube Warm up Routine has completed | info |
MS-006 | Tube Warm up Canceled | Tube Warm up routine was canceled | info |
MS-007 | Reconstruction's Queue Full | Number of Queue request for priority Recon is full | warning |
MS-008 | Recon Completion | Reconstruction Completed | info |
MS-009 | Calibration End | Calibration Program has completed | info |
MS-010 | Calibration Canceled | Calibration routine was canceled | info |
MS-011 | Warm up Scan Set Timeout | Scan set wait for Warm up Scan Timeout (Didn't push [Scan Set] in time) | warning |
MS-012 | Data Compare Error | Discrepancy between transferred data and expected data during DAS Data Transfer Test | error |
MS-060 | Display Busy | The requested program is canceled because Display is in use | info |
MS-070 | Image Data Full (Delete & Reset) | Reconstructed Data can not be store in Disk, for Disk is full of Image Data | error |
MS-071 | Image inf. Full in Study | Reconstruction is impossible because Image Inf. of study is full | error |
MS-072 | Next Scan Preparation Time Out | In Dynamic Scan, Scan is not completed within specified delay time | warning |
MS-073 | Pleas delete images in Disk! | Current number of vacant images less than 100 | warning |
MS-099 | On Dynamic Scan | The current function stops for Dynamic Scan | info |
O.C. | Over Current alarm | Motor winding short or shorted transistor detected | error |
O.H. | Over Heat alarm | Servo Amp temperature exceeds threshold | warning |
O.L. | Over Load alarm | Mechanical or motor load exceeds limit | error |
P.E. | Dynamic Brake Function Fail alarm | Dynamic brake resistor or voltage issue | warning |
RANGE ERROR | Entered MIN and MAX values are invalid or out of acceptable range | MIN value is greater than or equal to MAX value, or values exceed ±1000000 | warning |
RINGS | Workstation to Scan Processor communication error | Communication signal loss between workstation and OGP board | error |
RINGS LED ON with ERRS | OGP communication error detected | Slip ring communication failure or timeout during OGP-Management Processor handshake | error |
ROM mismatch | ROM level does not match program level | ETC firmware load or version mismatch during power-up | critical |
S.E. | Speed Error alarm | Motor speed does not match commanded speed | warning |
SVALM | Servo alarm detected | Servo amplifier detects fault condition | warning |
SVALM LED ON | Servo alarm detected by Gantry Processor | Servo amplifier malfunction or motor failure during gantry initialization | error |
TBLSTOP | Table cradle control loss | TGP loses control of cradle In/Out operation | error |
V.E. | Voltage Error Power Fail alarm | Input voltage drop or connection failure | warning |
WARM-UP ERROR | Warm-up sequence data out of acceptable range | Final scan data collection falls outside specified limits | error |
WARM-UP ERROR | Warm-up routine completed but data validation failed | Data collected during calibration scan #5 falls outside specified data range or warm-up scans encounter errors | error |
Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI
Community
0 fixes logged by technicians through their AI, with outcomes, for this model.
ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.