Philips PQ: troubleshooting and error codes
The ServiceForge knowledge base holds 569 documented symptoms for the Philips PQ, with 667 ranked causes, 1258 diagnostic checks with test points and expected values, and 948 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
Floppy LED does not flash
LED indicator on floppy drive should flash on and off during boot sequence but does not
Ranked causes
- 1. Power connector disconnected or loose to floppy drive or controller (common)
- 2. SCSI cable disconnected or faulty (common)
- 3. Floppy drive or controller jumpers incorrectly set (common)
- 4. SCSI ID conflict or duplicate ID (occasional)
- 5. SCSI termination missing or incorrect (occasional)
- 6. Floppy controller or drive failure (rare)
Cycle power to system
- Test point
- Power button
- Expected
- LED flashes during boot sequence
7 more checks with pass and fail actions, 6 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Archive cassette drive does not respond to command
Orange LED not lit; tape drive unresponsive to commands from system
Ranked causes
- 1. Tape media issue or bad connection (common)
- 2. SCSI cable not seated properly (common)
- 3. SCSI terminator issue (occasional)
- 4. Incorrect SCSI ID configuration (occasional)
- 5. Tape drive firmware issue (occasional)
Listen for tape drive spinup
- Test point
- tape drive motor
- Expected
- spinup sound audible
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
No gantry motion on bootup caution
Gantry does not move during system startup sequence
Ranked causes
- 1. Gullwing interlock switch in interlock position (common)
- 2. Drives interlock switch on AC Control Box in interlock position (common)
- 3. Fuses F310, F311, or F312 blown (occasional)
- 4. Servo drive power supply improper voltage (occasional)
- 5. Error logged in Error Logger program (unknown)
Verify gullwing interlock switch position
- Test point
- Gullwing interlock switch
- Expected
- Not in interlock position
5 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Parameter error (PARAM_ERR) generated by calfmr
System generates PARAM_ERR when calfmr receives out-of-range parameter from optable, control, or database during calibration operations
Ranked causes
- 1. MA offset parameter out of range (common)
- 2. Invalid command from CALM to CALF (occasional)
- 3. Calibration buffer handle mismatch (occasional)
- 4. Calibration file size mismatch (occasional)
- 5. Parameter size out of range for calibration type (occasional)
Verify MA offset parameter validity
- Test point
- MA_offset calculation
- Expected
- Parameter within valid range calculated from SCAN MA and AirCal MA
3 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Tape drive does not spin up
Archive tape drive fails to spin when activated
Ranked causes
- 1. Power supply issue (common)
- 2. Defective tape (occasional)
- 3. SCSI cable connection issue (common)
- 4. SCSI terminator misconfiguration (occasional)
- 5. SCSI ID conflict (occasional)
Check power to tape drive
- Test point
- Power connector
- Expected
- Power present
4 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Tape intermittently ejects during archive operation
Tape drive intermittently kicks out or ejects tape during archive/hardcopy operations
Ranked causes
- 1. Defective or incompatible tape (common)
- 2. SCSI cable connection loose or unseated (common)
- 3. SCSI terminator configuration incorrect (common)
- 4. Tape drive malfunction (occasional)
- 5. Power supply voltage out of specification (occasional)
Try new tape cartridge
- Test point
- Tape drive
- Expected
- Tape operates without ejecting
4 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ELTP touch panel not responding
Touch panel screen not responding to user input; no menus or data displayed when activated
Ranked causes
- 1. Power or cable continuity failure (common)
- 2. Improper jumper settings or connector pin configuration (occasional)
- 3. Serial communication cable fault (occasional)
- 4. ELTP module or circuit failure (rare)
Verify ELTP power supply and visual checks
- Test point
- Power connector and cable
- Expected
- Power connected; no visible cable damage
4 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Hard drive does not spin up
Hard drive fails to spin up; system exhibits SCSI failure
Ranked causes
- 1. Loose or disconnected SCSI cable (common)
- 2. Loose or disconnected power cable (common)
- 3. SCSI bus malfunction or device conflict (occasional)
- 4. Failed tape or floppy drive affecting SCSI chain (occasional)
Verify SCSI cable connection
- Test point
- SCSI connector at hard drive and controller
- Expected
- Firmly seated connection
3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
AC input chassis removal procedure high voltage
Removal of AC input chassis from scan frame requires cable disconnection, mounting bolt removal, and careful handling due to heavy weight (68.5-106.0 lbs depending on model)
Ranked causes
- 1. AC input chassis requires removal for service or replacement (unknown)
- 2. Heavy weight of AC input chassis (68.5-106.0 lbs) (common)
- 3. Lifting bracket availability varies by model (common)
7 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
ANB error in SIF communications
Serial communication error between SIF and GPU or SIF and XSC; ASCII message indicates error type and port in error
Ranked causes
- 1. Maximum number of retries (common)
- 2. Maximum number of errors (parity or checksum errors) (occasional)
- 3. Operating system overload or ANB software problem (rare)
Examine ASCII error message for error type and port number
- Test point
- Console or log display
- Expected
- Error name, error detected, and port in error clearly visible
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ANB error in SIF-GPU or SIF-XSC communication
Serial communication protocol error between SIF and GPU or SIF-XSC with ASCII message containing error name, detected error type, and port information
Ranked causes
- 1. Maximum number of retries - complete lack of communication in at least one direction (common)
- 2. Maximum number of errors - parity or checksum errors detected by SIF (occasional)
- 3. Operating system overload or ANB software problems (rare)
Examine ASCII error message for error name, detected error type, and port information
- Test point
- SIF error display
- Expected
- Error message with 3 pieces of information
2 more checks with pass and fail actions are in ServiceForge. Connect ServiceForge to your AI
Archive does not load tape
Tape archive system fails to load or recognize tape cartridges
Ranked causes
- 1. SCSI connection or termination issue (common)
- 2. Defective tape cartridge (common)
- 3. Tape drive requires reboot (occasional)
Reseat SCSI cables
- Test point
- SCSI connector
- Expected
- Secure connection
5 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Solenoid and switch adjustment
Position ball bearing on solenoid arm, set microswitch clearance to specification, and tighten fasteners to ensure proper actuator engagement.
Ranked causes
- 1. Ball bearing not centered on actuator (common)
- 2. Microswitch not positioned for proper closure (common)
- 3. Excessive clearance between switch and actuator blade (common)
Verify ball bearing is centered on actuator
- Test point
- Ball bearing center, actuator position
- Expected
- Ball bearing center aligned with actuator
4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Database key value changed unexpectedly
Key value in database changed without expected action
Ranked causes
- 1. Database configuration file .DBP changed without rebuilding databases (common)
- 2. Databases rebuilt without shutting down first (occasional)
- 3. CPU board memory is being clobbered (rare)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector module replacement criteria
Criteria for replacing detector modules based on pattern and count of bad channels detected during calibration procedures.
Ranked causes
- 1. Excessive bad channels in detector module (occasional)
- 2. Adjacent bad channels detected (occasional)
- 3. Bad channel affecting other channels in quadrature manner (rare)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry tilt movement abnormal patient safety
Tilt display flashing or blank; gantry tilts with excessive noise; movement is erratic; limit switches do not stop tilt
Ranked causes
- 1. Tilt transducer position feedback error or misalignment (occasional)
- 2. Tilt motor circuit fault (occasional)
- 3. Tilt limit switch failure (occasional)
Verify gantry moves in both tilt directions
- Test point
- Gantry with Gantry Control Panel switches for forward/backward tilt
- Expected
- Smooth movement forward and backward; no stalling
4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Hard drive 60 does not load heads
Drive fails to load read/write heads; may be detected as offline or unresponsive in SCSI diagnostics
Ranked causes
- 1. No power to drive (common)
- 2. SCSI or power cable loose or incorrectly seated (common)
- 3. Drive failure (occasional)
Verify power supply to hard drive 60
- Test point
- Drive power connector
- Expected
- Power present
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient Support horizontal (table top) movement abnormal patient safety
Horizontal display flashing or blank; table top moves erratically or with excessive noise; limit switches do not stop movement
Ranked causes
- 1. Horizontal transducer position feedback error (occasional)
- 2. Horizontal motor or drive circuit malfunction (occasional)
- 3. Limit switch failure at horizontal extremes (occasional)
Verify table top moves in both directions
- Test point
- Table top with Gantry Control Panel switches
- Expected
- Smooth in/out motion; no stalling or excessive resistance
4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient Support vertical movement abnormal patient safety
Vertical display flashing, blank, shows erratic numbers, or Patient Support moves with excessive noise, stalling, or jerky motion
Ranked causes
- 1. Vertical transducer malfunction or position feedback error (occasional)
- 2. Limit switch failure or misalignment (occasional)
- 3. Vertical motor drive circuit fault (occasional)
Verify Patient Support moves in both directions
- Test point
- Patient Support with Gantry Control Panel switches
- Expected
- Smooth upward and downward motion in both directions
4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
ARDAS detector module non-functioning radiation
Individual ARDAS detector module fails performance verification during autocalibration; scatter channel not working as expected; potential image artifacts if module is in critical position
Ranked causes
- 1. ARDAS detector module failure at critical position (0-19, 40-79, 100-119) (unknown)
- 2. ARDAS detector module failure at non-critical position (unknown)
Run ARDAS detector verification autocalibration program
- Test point
- All ARDAS detector channels
- Expected
- Individual module means within range of global mean; scatter channel functional
- Tools
- CT autocalibration software
4 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Auto Voice character response error
Command 8 sent to Auto Voice; console receives improper character count in response; timeout or missing characters returned
Ranked causes
- 1. Intercom volume turned down or audio circuit failure (common)
- 2. Serial communication or Auto Voice module failure (occasional)
Verify intercom volume setting
- Test point
- Intercom volume control
- Expected
- Volume turned up (non-minimum setting)
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Background zero test - channels out of specification
Some detector channels exhibit response values outside specification limits
Ranked causes
- 1. Detector channel response drift or malfunction (occasional)
- 2. Channel noise or offset calibration error (occasional)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Ballscrew drive damage during support lowering caution
Vertical support brace must be removed before lowering patient support; leaving brace in place will damage ballscrew drive mechanism
Ranked causes
- 1. Vertical support brace left in place during lowering (occasional)
- 2. Vertical support brace not returned to holder (occasional)
Verify vertical support brace is removed before lowering patient support
- Test point
- vertical support brace position
- Expected
- brace removed and stored in holder
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Brake makes excessive noise during operation caution
Loud chattering or abnormal noise from brake during vertical motion control
Ranked causes
- 1. Brake hub not properly aligned (common)
- 2. Brake wiring connections loose or disconnected (occasional)
Listen for excessive noise during patient support raise/lower cycles
- Test point
- Brake area audible inspection
- Expected
- Normal brake operation; minimal or no chattering
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Button timeout error on System Monitor Board caution
Timeout occurs when button not pressed before test timeout period expires or button is defective
Ranked causes
- 1. Button not pressed within timeout period (common)
- 2. Button defective or intermittent (occasional)
Verify button press is detected within timeout window
- Test point
- Button input port
- Expected
- Button Hit Detected message displayed
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration Request error (NOCALFILE_ERR)
Requested calibration file cannot be found or accessed
Ranked causes
- 1. Scanner not completely calibrated for all protocols (common)
- 2. Calibration file not found or unreadable on disk (occasional)
Calibration: Center calibration
Generation of centering constants for detector positioning and scan frame circularity correction during autocalibration
Ranked causes
- 1. Detector center position variation across tilt angles (common)
- 2. Scan frame not perfectly circular (common)
Verify generation of global centering constants
- Test point
- Centering calibration file
- Expected
- 61 Global Constants in output file
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Gantry Processor Unit DIP switch configuration high voltage
Set/verify DIP switch settings on wire wrap versions of GPU circuit card
Ranked causes
- 1. DIP switches require initial configuration or verification (common)
- 2. Static discharge risk during PCB handling (common)
5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: GPU DIP switch configuration high voltage
Set or verify DIP switch settings on GPU circuit card wire wrap versions to ensure correct gantry processor unit configuration
Ranked causes
- 1. DIP switches require initial setup or verification (common)
- 2. High voltage hazard during open gantry service (common)
Verify gantry power is off
- Test point
- Main power disconnect
- Expected
- Power removed per Power Up/Down procedures
4 more checks with pass and fail actions, 6 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Patient Support vertical position
Adjust vertical zero and scale potentiometers on CTCC card to calibrate patient couch height; verify display word 9 values and physical measurements at upper and lower limits
Ranked causes
- 1. Vertical zero potentiometer out of adjustment (unknown)
- 2. Vertical scale potentiometer out of adjustment (unknown)
Access Regulus screen and cocal program
- Test point
- Gantry interface
- Expected
- cocal menu with option #5 available
12 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Scan drive offset and phasing
RDC offset and Motor Pole offset adjustment for X-ray beam detector alignment and servo motor phase relationship
Ranked causes
- 1. RDC offset requires adjustment for detector zero alignment (common)
- 2. Motor Pole offset requires adjustment for servo phase relationship (common)
Remove gantry power
- Test point
- ELTP
- Expected
- Gantry Powerdown option selected
7 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Scan drive resolver offset high voltage
Adjust RDC offset switches so Fine RDC circuit output is zero when X-ray center beam points at detector zero; adjust Motor Pole offset switches to align phase relationship between A, B, C commands and stator voltages to prevent smooth rotation failure or backward rotation attempts
Ranked causes
- 1. Resolver offset requires calibration after resolver replacement or PMDC replacement with settings change (occasional)
- 2. Poor image quality, intercom noise, or gantry vibration from excessive resolver error (occasional)
6 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: X-ray drift evaluation radiation
Performance utility to assess X-ray generation equipment stability during high voltage startup; collects data 50 msecs after HV generator powers up and displays stability information from detectors numerically or graphically
Ranked causes
- 1. Delta Data enabled (common)
- 2. Pilot source fans data not enabled (common)
Verify pilot source fans data save is enabled
- Test point
- site_cnf program menu
- Expected
- Pilot source fans data save enabled
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: X-ray tube center positioning radiation
Lateral and global positioning errors detected during centering calibration scan; tube may be misaligned relative to detector center
Ranked causes
- 1. Tube lateral misalignment exceeds tolerance (>0.005 in.) (unknown)
- 2. Tube lateral misalignment within tolerance (<0.005 in.) (unknown)
Scan centering pin using CENTER CAL protocol
- Test point
- Scanner utility test protocols
- Expected
- CENTER CAL protocol selected; large focal spot; Comp=Norm
- Tools
- Scanner utility
4 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Couch collision with gantry during diagnostic movement patient safety
Patient couch moves during Couch Drive Diagnostic test and may extend into gantry, risking collision with objects or personnel
Ranked causes
- 1. Objects left on couch during diagnostic execution (common)
- 2. Personnel in couch or gantry path during motion (common)
Verify couch surface is clear of all objects
- Test point
- Patient couch platform
- Expected
- No objects present on couch
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Couch position error during pilot scan patient safety
Error message displayed: 'couch position must be outside of view, 450mm or less' with actual couch position value shown. Occurs when pilot scan includes objects in scan field.
Ranked causes
- 1. Table incremented too far into scan circle (common)
- 2. Phantom or object protruding into scan field during pilot scan (common)
Verify couch position outside scan circle
- Test point
- Couch
- Expected
- Position 450mm or less from scan circle edge
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector number sequencing error patient safety
Detector numbers in scan data are not in sequential order, possibly due to aborted scan reprocessing
Ranked causes
- 1. Reprocessing of aborted or incomplete scan (occasional)
- 2. Detector hardware malfunction or data corruption (rare)
Disk write error
System unable to write to disk, often accompanied by full disk or corrupted filesystem messages
Ranked causes
- 1. Disk partition "/usr" is full (common)
- 2. Regulus filesystem on "/usr" is corrupted (common)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
EL touch panel inoperative after replacement
Touch panel commands do not execute or system does not respond to panel input
Ranked causes
- 1. Touch panel not properly connected or installed (common)
- 2. Mounting nuts and washers not properly secured (occasional)
Verify cable connections at touch panel PCB
- Test point
- Lower right corner of touch panel PCB
- Expected
- Both cables firmly seated and engaged
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Environmental sensor error reported in Error Logger
Error Logger displays name and location of tripped environmental sensor
Ranked causes
- 1. Air flow sensor obstruction (common)
- 2. Temperature sensor lead disconnected (common)
Access Error Logger to identify tripped sensor
- Test point
- Error Logger
- Expected
- Sensor name and location displayed
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error on alert board detected during pre-scan check
SCAREMAN test at scan start detects SIF or MPM in crash condition and displays error message naming the board
Ranked causes
- 1. SIF in crash condition (unknown)
- 2. MPM in crash condition (unknown)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry cannot be turned off from service panel
Gantry does not power down when attempting to turn off after service work or troubleshooting from the Gantry Service Panel.
Ranked causes
- 1. Emergency Stop Pushbutton not depressed (common)
- 2. Service/O/Normal keyswitch not returned to Normal position (common)
Depress Emergency Stop Pushbutton
- Test point
- Any Emergency Stop Pushbutton on Gantry Service Panel
- Expected
- Gantry stops immediately
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry cannot be turned on from service panel
Gantry does not respond when attempting to power on using the Gantry Service Panel during service, troubleshooting or preventive maintenance.
Ranked causes
- 1. Service/O/Normal keyswitch not in Service position (common)
- 2. START pushbutton not pressed (common)
Verify Service/O/Normal keyswitch position
- Test point
- Service/O/Normal keyswitch on Gantry Service Panel
- Expected
- Service position
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry covers removed - dangerous voltage exposure high voltage
Technician operating or working on equipment with gantry covers removed may contact exposed dangerous voltages
Ranked causes
- 1. Service procedure requires gantry covers to be removed (common)
- 2. Exposed high-voltage circuits in gantry assembly (common)
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry power-up verification incomplete radiation
System not yet powered up or tube type not verified before applying gantry power
Ranked causes
- 1. Tube type not verified before gantry power-up (common)
- 2. Tube type mismatch detected (rare)
Apply power to console only
- Test point
- console power switch
- Expected
- console fully powered and ready for command input
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry spins in reverse direction after boot caution
On system startup, the gantry rotates in opposite direction from normal operation
Ranked causes
- 1. Incorrect motor pole offset setting (common)
- 2. Motor control circuit malfunction or incorrect wiring (occasional)
Verify motor pole offset setting is correct
- Test point
- Motor pole offset configuration
- Expected
- Setting configured for normal (forward) direction rotation
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Intercom PCB replacement high voltage
Remove and replace the console intercom PCB as part of maintenance or repair
Ranked causes
- 1. Intercom PCB requires replacement (unknown)
- 2. Equipment exposure to high voltage during open-cover work (common)
Remove console power
- Test point
- Console power supply
- Expected
- Power removed per powerup/powerdown procedure
12 more checks with pass and fail actions, 10 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Intercom speaker or microphone not operating
Speaker or microphone functionality fails after microphone PCB replacement or during normal operation
Ranked causes
- 1. Microphone PCB not properly seated or connector misaligned (common)
- 2. Defective replacement microphone PCB (occasional)
Verify microphone PCB is firmly pressed against mounting surface
- Test point
- PCB mounting area inside cone
- Expected
- PCB seated flush with secure contact
3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Invalid GPU command
GPU receives invalid command from SIF touchpanel interface
Ranked causes
- 1. GPU not programmed to understand command (occasional)
- 2. GPU in state that cannot accept command (occasional)
ISAM error 200 or higher
ISAM error code 200 or above indicates memory corruption or untested software
Ranked causes
- 1. Computer memory is corrupt, probable hardware failure on CPU board (occasional)
- 2. Untested software is clobbering memory (occasional)
Loose cables or restricted travel detected caution
Cables loose or catching during scan frame rotation; clearance issues between rotating and stationary frame cables.
Ranked causes
- 1. Loose cables in rotating assembly (occasional)
- 2. Insufficient clearance between rotating and stationary frame cables (occasional)
Rotate scan frame counterclockwise by hand
- Test point
- Entire rotation range
- Expected
- No loose cables; smooth rotation without resistance
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Memory test failures during diagnostic
Memory diagnostic tests report errors at multiple address ranges during PIPE & 68000 to DATA MEMORY TEST execution
Ranked causes
- 1. Defective data memory module or address range (unknown)
- 2. DMA controller malfunction (unknown)
Execute full memory diagnostic with DMA testing
- Test point
- PICKER ARRAY PROCESSOR PIPE-DATA MEMORY DIAGNOSTIC menu
- Expected
- All memory tests at ranges 9d180, 9e100, 9f080, 81000, 81f80, 82f00, 83e80, 84e00, 9a300, 9b280, 9c200, 9d180, 9e100, 9f080 complete without errors
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support brake does not stop immediately patient safety
Vertical motion continues when gantry control switches are released; brake makes excessive noise or fails to arrest motion
Ranked causes
- 1. Brake hub not properly aligned (common)
- 2. Brake wiring connections loose or faulty (common)
Raise patient support a few centimeters using gantry control panel
- Test point
- Gantry control panel switches
- Expected
- Patient support rises smoothly
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support does not raise or lower smoothly patient safety
Scissor mechanism binds or moves erratically during height adjustment via gantry control panel
Ranked causes
- 1. Vertical support brace misaligned or not properly positioned (occasional)
- 2. Ballscrew damaged from carriage collision (rare)
Verify vertical support brace position and clearance
- Test point
- Green safety vertical support brace on scissor carriage
- Expected
- Brace installed per Figure 38 with scissor carriage stopping just before touching brace
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support does not stop immediately patient safety
Vertical motion continues after control switches are released; brake fails to halt descent
Ranked causes
- 1. Brake hub not properly aligned (common)
- 2. Wiring connections loose or incorrect (occasional)
Brake operational response to control input
- Test point
- Gantry control panel switches
- Expected
- Vertical motion stops immediately when switches are released
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support does not stop immediately when brake control released patient safety
Vertical motion continues after operator releases gantry control panel switches; brake does not halt patient support promptly
Ranked causes
- 1. Brake hub not properly aligned (common)
- 2. Brake wiring connections loose or faulty (occasional)
Operate patient support vertical motion using gantry control panel switches
- Test point
- Gantry control panel switches
- Expected
- Vertical motion stops immediately when switches are released
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support does not stop immediately when brake is released patient safety
Vertical motion continues after gantry control switches are released; brake may make excessive chattering noise
Ranked causes
- 1. Brake wiring connections loose or disconnected (common)
- 2. Brake hub not properly aligned (common)
Operate patient support vertical motion using gantry control panel
- Test point
- gantry control panel switches
- Expected
- vertical motion stops immediately when switches are released
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Patient support does not stop immediately when brake switches released patient safety
Vertical motion continues after operator releases gantry control panel switches; brake fails to halt patient support
Ranked causes
- 1. Brake hub not properly aligned (common)
- 2. Brake wiring connections loose or disconnected (common)
Raise patient support a few centimeters using gantry control panel
- Test point
- Gantry control panel switches
- Expected
- Patient support rises smoothly
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Remove inverter diagnostic board CRX-200 high voltage
Procedure to remove and replace inverter diagnostic board; requires 50 minutes and involves high voltage safety precautions
Ranked causes
- 1. Inverter diagnostic board requires service or replacement (unknown)
- 2. Reassemble gantry and restore power (unknown)
De-energize gantry at wallbox
- Test point
- External power wallbox
- Expected
- Gantry power off; five-minute wait for rail voltage discharge
2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Replace XSC+ PCB caution
Removal and installation of XSC+ printed circuit board during repair procedures
Ranked causes
- 1. XSC+ PCB requires replacement (unknown)
- 2. Scan frame positioning after PCB replacement (unknown)
4 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
More symptoms
- Scan control panel not responding
- Slip ring misalignment detected during calibration
- SMADD diagnostic displays error during small drives test
- Unswitched Voltage Indicator not lit
- 8 mm tape drive replacement
- 8mm tape drive replacement
- AC input chassis replacement
- Access Error Reporting Program for troubleshooting
- Accidental contact with exposed high voltage
- Actual Length of Exposure (ALE) fault
- Address counter overrun
- Address counter underflow
- Air bubbles in water phantom
- Anode high voltage module removal and replacement
- Anode HV module handling safety
- Anode multiplier handling hazard
- Anode multiplier removal required
- Anode multiplier weight and handling hazard
- Anode/Cathode Arc detection during exposure
- Array processor data memory crosstalk suspected
- Audible knocking detected during vertical patient support movement
- Audible knocking detected in vertical patient support movement
- Audible knocking in vertical patient support movement
- Background zero test - excessive coherent noise detected
- Backprojector memory diagnostic test execution
- Ballscrew damage from carriage contact
- Ballscrew damage from scissor carriage contact
- Ballscrew drive damage from lowering support with brace installed
- Ballscrew drive damage from patient support lowering with vertical support brace installed
- Ballscrew drive damage from vertical support brace not removed
- Ballscrew drive damage risk from vertical support brace
- Ballscrew misalignment from carriage-brace contact
- Ballscrew misalignment from scissor carriage collision
- Ballscrew removal and replacement
- Beam limiter does not cycle on/off
- Beam Limiter Solenoid calibration
- Bearing – carbon top defective
- Belt tension adjustment
- Blower not operating
- Blower not operating after replacement
- Blower replacement
- Brake cable disconnect
- Brake cable replacement procedure
- Brake makes excessive noise
- Cable obstruction in frame travel range
- Calibration after front-end repair
- Calibration files not updating
- Calibration: -15V power supply
- Calibration: -18V A-B power supply
- Calibration: -18V A-B power supply PS204
- Calibration: –15 VDC power supply adjustment
- Calibration: –15 VDC power supply verification
- Calibration: –15 Volt adjustment
- Calibration: –15 Volt DC Power Supply
- Calibration: –20 VDC power supply verification
- Calibration: +15 VDC output adjustment
- Calibration: +15 VDC power supply verification
- Calibration: +15 volt DC power supply
- Calibration: +15V power supply
- Calibration: +18V A-A and -18V A-A power supplies
- Calibration: +18V A-A power supply
- Calibration: +18V A-A power supply PS202
- Calibration: +18V A-B power supply
- Calibration: +18V A-B power supply PS203
- Calibration: +20 VDC power supply verification
- Calibration: +5, +15, –15, +20 and –20 VDC power supply verification
- Calibration: +5, ±15 volt DC power supply
- Calibration: +5, ±15, ±20 Volt DC power supply verification
- Calibration: 12 o'clock laser alignment
- Calibration: 7-inch X-ray tube mounting rails installation
- Calibration: 7" tube system installation and alignment
- Calibration: AC control panel startup and power supply voltage adjustment
- Calibration: Adjust vertical travel limit switches
- Calibration: Air calibration after detector module or VFSCC replacement
- Calibration: Air calibration file interpolation
- Calibration: Air calibration for PQ protocols
- Calibration: Air calibration half field and full field
- Calibration: Aircal interpolation
- Calibration: Anode multiplier replacement post-service
- Calibration: Apply threadlocker to mounting screws
- Calibration: ARDAS detector verification
- Calibration: Axial alignment block pivot positioning
- Calibration: Ballscrew greasing and motor alignment
- Calibration: beam limiter solenoid
- Calibration: Beam limiter solenoid actuator extension
- Calibration: Beam Limiter Solenoid alignment
- Calibration: Beam limiter solenoid extension
- Calibration: Beam pivoting adjustment
- Calibration: Brush block alignment
- Calibration: Brush block radial alignment
- Calibration: Cathode multiplier replacement
- Calibration: Center program execution
- Calibration: Collimator alignment verification
- Calibration: Collimator eccentric alignment
- Calibration: Collimator opening alignment
- Calibration: Console air filter direction verification
- Calibration: Couch drive belt pulley alignment
- Calibration: Couch horizontal drive belt tension
- Calibration: Custom calibration
- Calibration: DC power supply verification
- Calibration: Drive verification
- Calibration: Electronic centering
- Calibration: Field detector module evaluation
- Calibration: Fine RDC Zero Adjustment
- Calibration: Fine zero adjustment
- Calibration: FLATSS manual flat field correction
- Calibration: FLATSS manual flatfield correction
- Calibration: FLATSS verification
- Calibration: Full Field FLATSS
- Calibration: Gantry cover and scan drive procedures
- Calibration: Gantry tilt drive
- Calibration: Gantry tilt potentiometer and pulley replacement
- Calibration: Half field flats
- Calibration: Half Field FLATSS
- Calibration: Horizontal timing belt replacement
- Calibration: Laser alignment
- Calibration: Laser alignment for scan frame
- Calibration: Laser beam crosshairs verification
- Calibration: Lateral centering
- Calibration: LRDC Gantry power supply
- Calibration: Lump correction
- Calibration: mA curve
- Calibration: Main drive excitation level
- Calibration: Main drive excitation level adjustment
- Calibration: Manual FLATSS
- Calibration: Manual FLATSS for X-ray imaging
- Calibration: Patient Support horizontal centering
- Calibration: Patient support table limit switches
- Calibration: Patient Support table position limits
- Calibration: Patient support vertical positioning
- Calibration: Patient Support vertical travel limit switches
- Calibration: Pilot
- Calibration: Pilot Field
- Calibration: Poly-Sci signal brush block alignment
- Calibration: Power supply outputs
- Calibration: PQ image centering and tube heat
- Calibration: pre-calculated FLATSS verification
- Calibration: Preheat table parameters OL 9 & 10
- Calibration: Preheat values for filament
- Calibration: Resolver error correction circuitry
- Calibration: Scan frame alignment with tube at 12:00
- Calibration: Scan frame laser alignment
- Calibration: servo-controller fan mounting hardware replacement
- Calibration: Shutter operation
- Calibration: Sine wave verification
- Calibration: Site configuration parameter adjustment
- Calibration: Standard Calibration
- Calibration: Standard Performance
- Calibration: Standard performance evaluation
- Calibration: System image alignment and constants
- Calibration: System image calibration
- Calibration: System monitor PCB verification
- Calibration: System prerequisites and setup verification
- Calibration: Table top limit switch adjustment
- Calibration: Table top limit switches
- Calibration: Vertical brake installation
- Calibration: Vertical brake removal and replacement
- Calibration: Vertical scale potentiometer
- Calibration: Vertical travel limit switch adjustment
- Calibration: X-ray beam centering
- Calibration: X-ray tube alignment
- Calibration: X-ray tube alignment prerequisite
- Calibration: X-ray tube axial adjustment
- Calibration: X-ray tube change
- Calibration: X-ray tube mechanical alignment
- Calibration: X-ray tube mounting rail installation
- Cannot open database
- Carbon patient support damage from heavy tube placement
- Carbon top bearing replacement required
- Carbon top removal and replacement
- Cardfile circuit board removal and replacement
- Cathode high voltage module replacement
- Cathode multiplier removal requires high voltage discharge time
- Cathode multiplier replacement on CRX-200/CRX-400
- Cathode multiplier replacement procedure
- Cathode multiplier weight hazard during handling
- Check for loose cables and frame clearance
- Collimator alignment verification
- Collimator assembly installation verification
- Collimator diagnostic test
- Compensator diagnostic test
- Console air filter needs replacement
- Console air filter replacement
- Console cardfile PCB requires removal or replacement
- Control word write/read mismatch
- Corrupt pilot scan data
- Couch clearance during diagnostic motion
- Couch drive velocity measurement needed
- Couch drive velocity measurement test
- Couch horizontal drive belt tension adjustment
- Couch movement during diagnostic
- Couch moves unexpectedly during diagnostic test
- Couch position measurement verification
- Couch velocity measurement check
- Couch velocity measurement needed
- Could not get Nth msg from CALF
- Cradle assembly improper seating on 7-inch tube
- Cradle assembly installation on 7-inch tube
- Cradle mounting screws improperly torqued
- DAC calibration with standard vs. touched-up state
- Dangerous high voltage exposure with gantry covers removed
- Dangerous voltage exposure during gantry cover removal
- Dangerous voltage exposure during maintenance
- Dangerous voltage exposure during service
- Dangerous voltage exposure from removed gantry covers
- Dangerous voltage exposure with covers removed
- Dangerous voltage exposure with gantry covers removed
- Dangerous voltages exposed with covers removed
- Dark spot visible in air scan after calibration
- Data acquisition overrun
- Data file English 00-7 missing
- Database already opened by same task
- Database navigation past boundary
- Database record update failed
- DC power supply voltages out of range
- Detector center ray position incorrect
- Detector module select line voltage abnormal
- Detector number out of range in predata word
- DIP switch configuration error
- Disable stand-alone gantry control and restore normal operation
- Discharge high voltage before cathode multiplier work
- DITS counter not reset by MSML
- DITS counter reads incorrect value
- Divide by zero error in plot file
- Divide by zero error, plot file not updated
- Drive belt pulley alignment verification
- Drive belt rides off-center on pulley
- E/L Touch Panel not responding
- EL touch panel inoperative or unresponsive
- EL touch panel operation verification
- EL touch panel physical damage or loose mounting
- EL touch panel removal and replacement
- EL touch panel replacement
- EL touch panel requires replacement
- Electrostatic discharge (ESD) hazard during PCB work
- Electrostatic discharge protection during PCB work
- EMI shield removal (CRX-400)
- Equipment damage or serious injury from exposed high voltage
- Error on alert board during pre-scan test
- Error opening /dev/avoice
- Error opening /dev/avoice – Device file missing
- Error opening tty
- Error opening tty – Fatal error
- Error reading calibration parameters
- Error reading scan data
- Error reading scan data – couch did not reach endpoint
- Excessive couch displacement during diagnostic
- Exposed high voltage hazard during gantry access
- Exposed high voltages during gantry cover access
- Exposure to dangerous voltages during gantry cover removal
- File not found or unreadable
- File NOT in database for parameters
- FLATSS protocol configuration
- Front cone misalignment after replacement
- Gantry air blower replacement needed
- Gantry air blower replacement required
- Gantry air blower requires replacement
- Gantry and couch motion via IQOUT diagnostic tool
- Gantry cover replacement and system verification
- Gantry covers opened for service
- Gantry covers removal hazard awareness
- Gantry electronics do not power on
- Gantry front cover not installed
- Gantry home position rotation hazard
- Gantry overheating due to inadequate blower cooling
- Gantry power not available
- Gantry power-on procedure
- Gantry requires independent power control for service
- Gantry rotation hazard during laser button press
- Gantry scan frame rotation check
- Gantry scan frame rotation hazard
- Gantry speaker phrase not audible
- Gantry tilt motion during scan
- Gantry tilt potentiometer replacement needed
- Glass top breakage during handling
- Gull wing panels sharp edge hazard
- Half Field FLATSS calibration
- Hard drive replacement
- Heavy anode multiplier handling hazard
- High voltage bus exceeds 400 VDC
- High voltage discharge safety hazard during multiplier removal
- High voltage exposure during cover removal
- High voltage exposure during gantry cover removal
- High voltage exposure during gantry service
- High voltage exposure during open-cover operation
- High voltage exposure during service
- High voltage exposure hazard awareness
- High voltage exposure hazard during gantry cover removal
- High voltage exposure hazard during power supply verification
- High voltage exposure with covers removed
- High voltage exposure with gantry covers removed
- High voltage generator control board replacement
- High voltage module service with covers removed
- High voltage present after power removal
- High voltage present on gantry terminal block after interlock
- High voltage present on Spellman cable after power removal
- High voltage present on transformer connections and Spellman cable
- HIGH_VOLTAGE hazard during gantry maintenance
- Horizontal timing belt worn or damaged
- HVG generator errors
- HVGCC component replacement
- Illegal kV Fault
- Illegal signal detected
- Improper circuit board handling causing permanent component damage
- Improper exit error when Control-C pressed
- Intercom audio not audible
- Intercom calibration verification
- Intercom speaker or microphone does not operate
- Intercom system not functioning
- Interference limit reached
- Intermittent memory errors detected during diagnostics
- Invalid or no parameter in optable field
- Invalid SCAREMAN/SCAN state
- Laser alignment verification required
- Laser alignment verification with phantom
- Laser cone replacement
- Lasers not illuminating inside gantry
- Logic ground verification
- Loose cables detected during frame rotation
- Loose cables in scan frame
- Loose cables or contact during frame rotation
- lread of speech data error
- lread of speech header error
- lseek past data header error
- Memory diagnostic test execution
- Memory test execution time monitoring
- Missed EOF at specified register value
- Missed PPI at specified register value
- Motor and ballscrew couplings disengaged
- Motor drive phase misalignment after pole offset adjustment
- Multibus II backplane replacement
- Multibus II backplane replacement verification
- No Exposure error condition
- Opening upper gantry covers
- Operator Console does not turn on
- Operator's Console powered down unexpectedly during service
- Over-current condition on high voltage bus
- Patient support collapse risk during maintenance
- Patient support covers open—high voltage exposure
- Patient support does not lower smoothly
- Patient support falls uncontrolled when vertical motor removed
- Patient support lowers with vertical brace in place
- Patient support telescoping base cover removal preparation
- Patient support telescoping base covers removed
- Patient support uncontrolled descent during vertical motor removal
- Patient support will not lower properly
- Phrase not proper during verbal memory test
- Physical call error
- Physical call error – Fatal error
- Pilot mask bit set for CT scan
- Pilot scan image artifacts or errors
- Post-calibration board replacement and cover restoration
- Power supply voltage out of range
- Power supply voltage out of specification
- Power supply voltages out of range
- PPI occurred early or no data taken
- PPI stuck active or EOF stuck active
- Pre-data word 4 grabber mismatch
- Register load error
- Remove and replace high voltage generator control boards
- Remove anode high voltage module
- Replace 1.1 KVA auxiliary transformer
- Replace AC control chassis circuit board
- Replace anode high voltage module
- Replace beam limiter solenoid assembly
- Replace gantry cardfile circuit board
- Replace gantry microphone PCB
- Replace patient support carbon top
- Replace servo-controller fan
- Replace system control board
- Residual voltage on high voltage bus after de-energization
- Risk of radiation exposure during IQOUT operation
- Risk of serious injury during gantry or couch motion
- Rotate scan frame to 12:00 position
- Rotating gantry frame hazard during equipment operation
- Scan drive does not rotate smoothly or rotates backwards
- Scan drive not rotating smoothly or rotating backwards
- Scan frame cable inspection and clearance check
- Scan frame damage from clockwise rotation
- Scan frame rotated clockwise
- Scan frame rotates incorrectly or slip ring brushes damaged
- Scan frame rotation and cable inspection
- Scan frame rotation causes slip ring brush damage
- Scan frame rotation causes slip ring brush damage
- Scan frame rotation check
- Scan frame rotation check
- Scan frame rotation check after HV module replacement
- Scan frame rotation check after service
- Scan frame rotation check and cable inspection
- Scan frame rotation damage risk
- Scan frame rotation damage to slip ring brushes
- Scan frame rotation damaged slip ring brushes
- Scan frame rotation damages slip ring brushes
- Scan frame rotation inspection
- Scan frame rotation resistance or damage
- Scan frame slip ring brush damage during rotation
- Scissor carriage lowering procedure
- Scissor carriage misalignment after service
- Scissor mechanism entrapment hazard
- Scissor-action mechanism exposed during base cover removal
- Scissor-action mechanism exposed during patient support base cover removal
- Scissor-action mechanism exposure hazard
- Scissor-action mechanism exposure risk
- Scissor-action mechanism hazard during service
- Scissor-action mechanism injury risk
- Scissors carriage collision with vertical support brace
- Sequence error detection
- Sequence interrupted during image save
- Sequence interrupted during processing
- Servo-controller fan installation
- Servo-controller fan removal and replacement
- Servo-controller fan replacement
- Servo-controller fan replacement needed
- Servo-controller fan replacement required
- Servo-controller fan requires replacement
- Setup for console power supply calibration
- Sharp edge and electrical hazard during gantry cover removal
- Sharp edge hazard from upper gull wing panels
- Sharp edges on gull wing panels during gantry cover service
- Shutter binding during beam limiter activation
- Shutter binding during installation
- Shutter binding in beam limiter
- Shutter binding on 7" tube system
- Slip ring brush damage during scan frame rotation
- Slip ring brush damage during scan frame rotation
- Slip ring brush damage from improper scan frame rotation
- Slip ring brush damage risk during service
- Slip ring brushes damaged by scan frame rotation
- Slip ring brushes damaged during scan frame rotation
- Slip ring power absent or low
- Solenoid clamping screw torque
- SPEAK CONSOLE address low response error
- Specific memory area or function test selection
- Startup Options menu not displayed
- Static damage to circuit boards during handling
- Static electricity hazard during circuit handling
- Static electricity protection during circuit board handling
- System does not display Startup Options menu
- System does not power on
- System does not power on after blower replacement
- System does not power up normally
- System generates X-rays unexpectedly via IQOUT
- System image quality verification after blower replacement
- System monitor PCB failure or malfunction
- System monitor PCB not functioning
- System monitor PCB not working
- System monitor PCB not working or boot failure
- System monitor PCB replacement
- System monitor PCB replacement required
- System monitor PCB verification
- System not warmed up before clinical use
- System operation not verified after assembly
- System operation not verified with phantom images
- System operation verification after collimator replacement
- System startup incomplete or bootstrap failed
- System verification after transformer replacement
- System verification with water phantom scan
- System will not boot
- System will not power on after blower replacement
- Tape drive requires removal and repair
- Tape switch foot actuator defective
- Tape switch foot not responding
- Task priority not set
- Task priority not set – Fatal error
- Timed out waiting for calibration agents
- Timing belt tension check
- Too many points out of range
- Tools preparation
- Tube cradle orientation incorrect
- Tube type mismatch before gantry power-up
- Tube type mismatch detected
- Tube type mismatch on power-up
- Unable to attach to CALF Message Queue
- Unable to send message to exchange
- Unable to write image data to file
- Unintended gantry or couch motion via IQOUT
- Unintended X-ray generation during IQOUT operation
- Unit does not boot after system monitor PCB replacement
- Unit stops at C message during bootstrap
- Verification: Full-field flats uniformity
- Vertical brake removal and replacement needed
- Vertical couch motion during scan
- Vertical drive mechanism misalignment
- Vertical motor mounting plate screws loose or improper gap
- Vertical motor not responding to gantry control panel commands
- Vertical patient support collapses or motor coupling disengages
- Vertical position display does not decrease during patient support lowering
- Vertical support brace cable exposed or damaged
- Vertical support brace cable not properly positioned
- Vertical support brace installation
- Vertical support brace misalignment after scissor carriage operation
- Voltage rail out of specification
- Warmup and ELTP operation not completed
- Warmup cycle errors
- Write error to plot.dat file
- Write error to raw data file
- X-ray control chassis removal and replacement
- X-ray control chassis removal hazard
- X-ray generation via IQOUT diagnostic tool
- X-Ray Generator does not power on
- X-ray tube base plate removal
- X-ray tube damage during high voltage connector removal
- X-ray tube mechanical alignment after solenoid replacement
- X-ray tube mechanical misalignment
- X-ray tube removal procedure
- X-ray tube replacement
- X-ray tube replacement procedure
- X-ray tube shutter binding
- Z-beam tube orientation during installation
509 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
0 | New Installation?, Creating Configuration file | First startup or configuration file initialization | info |
1 | Unable to create message exchange of DBIX | System initialization or inter-process communication setup | error |
10 | Unable to get status & id of process '!!se' | Query of process status fails | warning |
100 | Regulus server attachment failure | Unable to connect to Regulus server | error |
100 | Error attaching to Queue IM2S | Archiver cannot attach to message queue IM2S | error |
100 | Attempting to update a record when there is no current record active | No current record active during update attempt | error |
100 | Unable to get regulus server | Server initialization or connection attempt | critical |
1001 | XSC+ BAD XSC-TIMER DRIVER: INVALID DATA | Scan error occurs during XSC+ operation | error |
1001 | Miscellaneous XSC errors including timer driver, command, state, tube type, collimator, filter and compensator issues | XSC timer driver message error, invalid command/data/access, bad host command, improper status request, wrong XSC state for exposure, illegal tube type request, component not ready for X-rays | error |
1001 | Miscellaneous errors | XSC timer driver failures, host command issues, tube type or generator changes not in idle state, or readiness failures for collimator, filter, or compensator | error |
1001-1100 | XSC error range | Various XSC (X-ray System Control) subsystem failures | error |
1002 | High voltage interface driver errors | Message exchange failures with ADC/DAC/HVST/HVCT, DAC initialization error, tolerance violations, incorrect commands, or ADC conversion timeout | error |
1003 | Anode Rotor Soft failure | Anode Rotor Soft component malfunction | unknown |
1004 | Small Drives subsystem failure | Small Drives component malfunction | unknown |
100 (dirp) | Unable to get Regulus server gsvr | Regulus server lookup fails | error |
101 | Regulus server release failure | Unable to release Regulus server connection | error |
101 | Navigation past database or study boundary | Moving past beginning of CL and database or study | warning |
101 | Unable to return/release Regulus server resource | Client releasing server resource after use | error |
1010 | Anode Rotor Hard failure | Anode Rotor Hard component malfunction | unknown |
1011 | HVPSI high voltage power supply failure | HVPSI component malfunction or regulation failure | unknown |
1013 | XSC subsystem failure | XSC component malfunction or communication error | unknown |
101 (dirp) | Unable to return/release Regulus server retsvr | Server release call fails | error |
102 | Cannot receive query request from resource manager queue | System communication failure with resource manager | error |
102 | OPDS queue error | System message from Regulus | error |
102 | Cannot receive on queue; error code <serror> | Attempt to receive message from specified queue | error |
102 | SMB frame manager cannot receive on OPCM | Failed SMB reception during frame processing | error |
102 | Cannot receive message from Resource Manager or cannot receive message from Resource | Resource Manager communication failure during config or imgspace operations | error |
102 | Regulus queue message receive failure | Unable to receive message from Regulus queue | error |
102 | Error doing a msgrcv() | Message receive operation failed | error |
102 | Could not open database | Attempt to open database | error |
102 (dbtb) | Unable to receive message from IRTB_MSG | Message queue communication timeout | error |
102 (didb) | Unable to receive message from DIDB_MSG | Message queue communication timeout | error |
102 (dirp) | Unable to receive message from Regulus queue | Message queue receive timeout | error |
103 | SMB frame manager cannot send on RENN | Failed SMB transmission during frame processing | error |
103 | Cannot send on queue; error code <serror> | Attempt to send message on specified queue | error |
103 | Unable to send a message to Regulus queue for image transfer | Message send failure to image transfer queue | error |
103 | Error doing a msgsnd() | Message send operation failed | error |
103 (dbtb) | Unable to send message to DBTB_MSG | Message queue communication timeout | error |
103 (dirp) | Unable to send message to Regulus queue msgsnd | Message queue send fails | error |
104 | Cannot get module ID for OPCM or RT4AN | Module identification query failure | error |
104 | Cannot create temporary queue or cannot obtain resource manager qid or cannot remove temporary queue | Queue creation, removal, or resource manager ID retrieval fails | error |
104 | OPDS or opcm error | System message from Regulus | error |
104 | SCANMAN cannot attach to LOAD queue | Failed to attach to LOAD message queue | error |
104 | Unable to get message queue id of DBIR_MSG | Queue identifier lookup during initialization | error |
104 (dbtb) | Unable to get message queue id of DBTB_MSG or IRTB_MSG | Message queue lookup failure | error |
104 (didb) | Unable to get message queue id of DIDB_MSG | Message queue lookup failure | error |
104 (dirp) | Unable to get Regulus message queue dirpkey | Queue ID lookup fails | error |
105 | Error opening log file | Cannot open log file for writing | warning |
105 | SCANMAN could not open file | File open operation failed | error |
105 | Cannot find or open $CAM/menu/cameras configuration file | Camera configuration file missing or inaccessible at startup | error |
105 | Phrase file error with status code | Error reading status from load operation | error |
105 | File system error | File operation failure | error |
105 | Unable to open file in Regulus | File open operation failed | error |
107 | Unable to read from file in Regulus | Read request to Regulus file server | error |
107 | Error reading status from load with status code | Load operation status read fails | error |
107 | Cannot seek in config.tbl file or cannot read device or cannot read config.tbl data save | File seek operation fails or device read fails or config.tbl unreadable during save operations | error |
107 | File system error | File operation failure | error |
107 | Error opening log file | Cannot open log file for writing | warning |
107 | Can not read file (x) | File read operation fails on device | error |
107 | Software upgrade in progress or configuration being recreated | System is performing software upgrade or recovering configuration | info |
108 | Cannot write config.tbl; scanning may fail or data save NOT ENABLED or NOT DISABLED | Write operation to config.tbl fails during configuration or save operations | error |
108 | Unable to write to file in Regulus | Write request to Regulus file server | error |
109 | Cannot seek in config.tbl file during save operations | File seek fails in config.tbl during saveoff/saveon | error |
11 | Task deletion failure | Unable to delete task on shutdown or cleanup | warning |
11 | Unable to delete task CROS | Task deletion attempt during shutdown or reset | error |
111 | SCANMAN processor reboot required | Specified processor requires reboot | warning |
112 | SCANMAN load file error | Failed to load specified file to processor | error |
114 | SCANMAN could not write parameter table to processor | Failed to write DISPLAY or SCAN parameter table to specified slot | error |
116 | Not enough EB's or backprojector disabled; cycle time will be increased | warning | |
116 | Cannot find board or no response | Board communication failure | critical |
116 | Insufficient event buffers available | System runs out of available event buffers during operation | warning |
116 | Module or board not found or no response from board | Module discovery failure or timeout during polling | error |
117 | SCANMAN miscellaneous file I/O error | error | |
11-rtvu | Unable to delete task HAIR | Child process deletion failure | critical |
12 | Unable to suspend task EXPO | System cannot pause or suspend EXPO task | error |
1202 | CALM error (CALM_ERR) – internal structures of CALM and/or memory on the MPM gets corrupted | CALM does not know what to do in error situation | error |
1203 | CALF error (CALF_ERR) – calfmr on the MPM (CALM) cannot communicate with calfmr on the CPB (CALF) | Communication failure between CALM and CALF | error |
125 | Attempting to open database when one is already opened by same task | Second database open request while one already active | error |
1501 | SC_LIBRARY_ERROR | Error detected in Scheduler library function call | error |
1502 | SC_PROCESS_REQUEST_ERROR | Processor portion of Reconstruction Software senses error or times out | error |
1502 | Processor portion of Reconstruction Software sensed an error or timed out | Error or timeout during image reconstruction processing | error |
1503 | Error or timeout occurred while saving reconstructed image to disk | Failure during image save operation to disk | error |
1503 | SC_IMAGE_SAVE_ERROR | Error or timeout while saving reconstructed image to disk | error |
1504 | Illegally formatted message received by Scheduler | Malformed message received by Scheduler | error |
1504 | SC_ILLEGAL_MESSAGE | Illegally formatted message received by Scheduler | error |
1505 | Unexpected message received or general message reception failure | Unexpected message arrival or failure in message reception | warning |
1505 | SC_GET_EVENT_FAILURE | Unexpected message received or general message reception failure | error |
1506 | SC_SLICE_Q_MSGSND | Error in sending Slice Query response message to OPCOM | error |
1506 | Error in sending Slice Query response message to OPCOM | Failure to send Slice Query response to OPCOM | error |
1507 | Failure or timeout in use of calibration information | Attempt to access or apply calibration data failed | error |
1507 | SC_CALIB_USE_FAIL | Failure or timeout in attempt to make use of calibration information | error |
1508 | Failure or timeout in attempt to use weighing vectors for spiral scanning | Weighing vector access or processing timeout during spiral scan | error |
1508 | SC_WT_USE_FAIL | Failure or timeout in attempt to make use of weighing vectors for spiral scanning | error |
1509 | SC_LINK_BUFFERS_FAILURE | Failure to link optable and data buffer together | error |
1509 | Failure to link optable and data buffer together | Buffer linking operation failed during processing setup | error |
151 | Cannot remove temporary queue | Temporary queue cleanup fails after operation complete | warning |
151 | SCANMAN message queue error (create, read status, size, flush, send, timeout) | error | |
1510 | SC_UPDATE_FAILURE | Failure in slice number update of previous processing request | error |
1510 | Failure in slice number update of previous processing request | Slice numbering update operation failed | error |
1511 | Failure in the stop reconstruction procedure | Stop reconstruction procedure invoked | error |
1512 | Failure in the Suspend Processing procedure | Suspend processing invoked | error |
1513 | Failure in the Resume Processing procedure | Resume processing invoked | error |
1514 | Failure in the process scheduling procedure | Process scheduling attempted | error |
1515 | Failure in the clear processing procedure | Clear processing invoked | error |
1516 | Failure in the Error reporting communication channel to SCAREMAN | Error reporting attempt to SCAREMAN | warning |
1517 | Failure in the Processing Done procedure | Processing Done notification invoked | error |
1518 | Failure in the Processor Registration procedure | Processor Registration procedure invoked | error |
1519 | Failure in the Slice number querying procedure | Slice number query requested by OPCOM or SCAREMAN | error |
1520 | Failure in the Control Status Query Procedure | Control status query requested by OPCOM | error |
1521 | Failure in the Calibration Use Acknowledgement procedure | During calibration use acknowledgement sequence | error |
1522 | Failure in the Weighing Vector Acknowledge procedure | During weighing vector acknowledgement | error |
1523 | Failure in the changing of Control Modes | During control mode change, possibly during calibration | error |
1524 | Failure in the data input procedures | During data reception tracking or scan error monitoring | error |
1525 | Failure in phase 1 of Scheduler initialization | During initial scheduler startup phase 1 | error |
1526 | Failure in phase 2 of Scheduler initialization | During scheduler startup phase 2 | error |
1527 | Failure in the resource manager interface procedure | When resource manager attempts to communicate with scheduler | error |
1528 | Failure in the scheduler debug procedures | During scheduler debug operation | warning |
1529 | General mode failure in Scheduler | Scheduler mode operation error | error |
153 | Command read from pipe failed | Attempt to read process command from inter-process communication pipe | error |
1530 | General initialization failure | During scheduler initialization | critical |
154 | Acknowledgment or negative acknowledgment write to pipe failed | Attempt to send response via pipe | error |
154 | SCANMAN error writing pipe | error | |
154 | LSTY error | System component failure | error |
1540 | Memory Manager release error. | Memory Manager unable to release allocated memory | warning |
1541 | Internal table overflow. | Internal data table exceeds maximum capacity | error |
1542 | Optable handle not found. | Referenced handle does not exist in Optable | error |
1543 | Invalid incoming event message. | Received event message is invalid or unrecognized | warning |
155 | Pipe close operation failed | Attempt to close pipe read or write end | warning |
1551 | Extraction of parameter from optable failed. | Optable Manager attempts to extract parameter from optable buffer | error |
1552 | Error in OPCOM interface. | Optable Manager interfaces with OPCOM subsystem | error |
1553 | Error in OPCOM interface. | Optable Manager queries OPCOM for operation done status | error |
1554 | Error in creation of Optable. | Optable Manager attempts to create new optable | error |
1555 | Initialization failure. | Optable Manager initialization sequence | error |
1556 | Invalid or illegal event message. | Optable Manager receives event message from system | warning |
1557 | Memory allocation failure. | Optable Manager attempts to allocate memory for operation | critical |
1558 | Error in cancel by DAQMN. | Data Acquisition Manager (DAQMN) attempts to cancel operation in Optable | error |
1559 | Error in freeing of optable memory. | Optable Manager attempts to free allocated optable memory | error |
156 | Unable to fork process rdbi | System process creation failure | critical |
1560 | Failure in optable retrieval by OPCOM | optable retrieval process | error |
1561 | Failure in optable retrieval by OPCOM with 2-ACK protocol | 2-ACK optable retrieval attempt | error |
1562 | Error in debug procedure | debug procedure execution | warning |
1563 | Fill optable manager table failure | optable manager fill operation | error |
1564 | Failure in optable usage by Scheduler | Scheduler attempting to use optable | error |
1565 | Optable Create failure | optable creation operation | error |
1566 | Optable deuse failure | optable deuse operation | warning |
1567 | Failure in deallocation of Optable | optable deallocation operation | error |
1568 | Failure in update of optable information | optable update operation | error |
1569 | Failure in phase 1 of initialization | Optable initialization phase 1 executed | error |
157 | rtroff error with serror code | rtroff operation in /usr/IQ/bin/serv/ fails | error |
157 | Cannot spawn task | Task creation failure | error |
1570 | Failure in phase 2 of initialization. | Initialization phase 2 encounters error condition | error |
1571 | Failure in memory allocation | When system attempts to allocate memory | error |
1572 | Illegal message format. | Received message does not conform to protocol specification | warning |
1573 | Inconsistent Acknowledgement tag received | During message acknowledgement handshake | error |
1574 | Error in Memory Manager interface. | Memory Manager interface operation fails | error |
1575 | Memory Manager lock error | When Memory Manager attempts to lock resources | error |
1583 | DITA or AutoCAL interface error | DITA or AutoCAL interface malfunction | error |
1583 | DM_PIPP_END_ERROR | DITA or AutoCAL interface error | error |
1584 | DITA or AutoCAL interface error | DITA or AutoCAL interface malfunction | error |
1584 | DM_PIPP_CREATE_ERROR | DITA or AutoCAL interface error | error |
1585 | DM_PIPP_HBEAT_ERROR | DITA or AutoCAL interface error | error |
1585 | DITA or AutoCAL interface error | DITA or AutoCAL interface malfunction | error |
1586 | Memory manager lock error | Memory manager unable to acquire lock on memory resource | critical |
1587 | DM_BAD_ALLOACK_STATUS | Memory allocation error | error |
1587 | Memory allocation error | System unable to allocate requested memory | error |
1588 | DM_BAD_ALLOFIX_ACK_STATUS | Fixed memory allocation error | error |
1588 | Fixed memory allocation error | System unable to allocate fixed memory block | error |
1589 | DM_HANDLE_NOT_FOUND | Buffer handle lookup failure | error |
1589 | Buffer handle error | Invalid or unavailable buffer handle referenced | error |
1590 | Optable interface lock failed | Unable to acquire lock on Optable interface resource | error |
1591 | Optable get failure | Optable unable to retrieve requested data | error |
1592 | Internal Data Manager table overflow | Data Manager internal table exceeded capacity | warning |
16 | Unable to allocate memory segment setdsphw | error | |
160 | Key value changed unexpectedly | Database key value mismatch detected | error |
161 | Signal opcom error | Inter-process communication failure | error |
162 | SCANMAN could not allocate full image backup file | error | |
162 | Cannot create config.tbl; scanning will fail | config.tbl file creation fails at startup | error |
162 | Disk full error | Storage device has no free space remaining | critical |
164 | No scan manager | Scan manager service unavailable | critical |
168 | Floppy mount error | Cannot mount floppy disk device | error |
169 | Floppy unmount error | Cannot unmount floppy disk device | error |
17 | Memory allocation failure | Unable to allocate memory for shape table | error |
17 | Unable to allocate memory for message buffer dp_msgbuf | Memory allocation during initialization | critical |
170 | Floppy mkfs error | Cannot create filesystem on floppy disk | error |
171 | Floppy format error | Cannot format floppy disk | error |
172 | Write file failed; Rewind Error; Tape positioning error; Error writing filemark to tape | Cannot write data to tape or rewind/position tape | error |
173 | No last tape dir entry found | Tape directory structure corrupted or missing | error |
173 | Tape read error | Cannot read data from tape | error |
173 | O-Disk Write Error, Unable to search for next image, Unable to transfer tape DB files, Error tried to delete current study, No eot file found, Incomplete study found error, Invalid tape format error, Empty tape error, Tape read error, No last tape dir entry found, No Tape File Sequence Number, Unable to write to floppy | Multiple archival, database, or storage operation failures | critical |
173 | Incomplete study found error | Study archive incomplete or corrupted | error |
173 | Unable to write to floppy | Cannot write data to floppy disk | error |
174 | Unable to allocate memory for image header buffer | Memory allocation for image header data structure | critical |
174 (dbtb) | Unable to allocate memory for file table | Memory allocation request fails | error |
174 (didb) | Unable to allocate memory for image header buffer | Memory allocation request fails | error |
17 (dirp) | Unable to allocate memory segment dirpmsg | Shared memory allocation fails | error |
17 (dpud) | Unable to allocate Graphics Instruction memory segment | Shared memory allocation fails | error |
17-rdbp | Unable to allocate memory buffer for rdbi messages | Memory allocation failure | critical |
18 | Unable to release memory segment | Memory deallocation during task shutdown or resource cleanup | warning |
1 (dpud) | Unable to create message exchange (gkxqname, ttxqname, vtsync) | Message exchange creation fails | error |
1-rdbp | Unable to create message exchange RDBP or PARA | Message exchange initialization failure | critical |
2 | Cannot attach to exchange or StopSIF cannot attach to SFMN | Module initialization failure during startup | error |
2 | Unable to attach to message exchange of DMIX | Inter-process communication attachment during startup | error |
200+ | ISAM error 200 or higher | Any ISAM error code 200 or above | critical |
200 | Data file too big for floppy or bad header error | Attempting to process data file exceeding floppy capacity or corrupted header | error |
200 | SCANMAN error attaching to database | error | |
2006 | Invalid GPU command | Invalid or unsupported command request from SIF to GPU | error |
2007 | Interference limit | Couch-gantry collision attempt or servo mode movement would cause interference | warning |
2008 | Register load error | GPU or XSC parameter register read value does not match load value after verification | error |
2009 | Vertical motion error | Couch vertical movement exceeds 1mm deadband during active scan | error |
201 | SCANMAN error opening database | error | |
2010 | Tilt motion error | Gantry tilt exceeds 0.25 degree deadband during active scan | error |
202 | SCANMAN error closing database | error | |
203 | SCANMAN error reading database field | error | |
204 | SCANMAN error writing to database field | error | |
205 | Error cloning rdb | Database clone operation fails | error |
206 | Error resetting flags | Flag reset operation in database fails | error |
207 | Error doing a dbfrmnky() | dbfrmnky() database function call fails | error |
207 | Database error dbfrmkey in task/function | Database key frame operation | error |
208 | SCANMAN error with miscellaneous database function | error | |
208 | Misc. database error | Unspecified database operation error | error |
209 | SCANMAN error sorting database | error | |
210 | Error doing a dbkeynum() | dbkeynum() function fails | error |
211 | Error doing a dbfndgeq() | dbfndgeq() search function fails | error |
211 | Database error dbfrsrec; error code in task/function | Database record frame operation | error |
212 | Error searching the database | Database search operation fails | error |
213 | SCANMAN error allocating file via database | error | |
214 | SCANMAN error deleting database entry | error | |
215 | Database error dbsiglen in task/function | Database signal length operation | error |
215 | Error adding image to database | Image insertion into database fails | error |
216 | Error doing a dbsiglen() | dbsiglen() function fails | error |
216 | Database error dbmovkey in task/function | Database key move operation | error |
217 | Error doing a dbmovkey() | dbmovkey() function fails | error |
218 | Error doing a dbgetfld() | dbgetfld() field retrieval fails | error |
219 | Error updating rdb | Relational database update operation fails | error |
220 | Task aborted prematurely | Running task terminates unexpectedly | error |
221 | Error doing dbcredbc() for studies | Database creation function fails during studies operation | error |
222 | Insufficient startup arguments | Application launched with missing required arguments | error |
25 | Unable to signal event to a task PPT2 | Event signaling failure to PPT2 task | error |
2 (dirp) | Unable to attach to message exchange name | Named queue attachment fails | error |
2 (dpud) | Unable to attach to DPUC message exchange | Message exchange attachment fails | error |
2-rdbp | Unable to attach to message exchange DBRP | Message exchange attachment failure | critical |
2-rtvu-comm | Unable to attach to message exchange | Communication channel initialization failure | critical |
3 | SCANMAN message receive or timeout error | Failed to receive expected message or timeout during receive operation | error |
3 | Unable to request message from message exchange | System cannot retrieve message from specified exchange | warning |
300 | Could not enable relay | Gantdown relay enable failure | error |
300 | System monitor ROM read failure | Could not read system monitor ROM after 4 attempts | critical |
302 | Drop in airflow with message | Airflow decreases below acceptable threshold | warning |
303 | Keyswitch turned back ON after shutdown | System power restored after improper shutdown | info |
304 | Rise in ambient temperature with message | Ambient temperature increases above acceptable range | warning |
305 | Decrease in plenum temperature with message | Plenum temperature decreases below acceptable range | info |
306 | Keyswitch turned off with tube hot | Power switch turned off while X-ray tube is at high temperature | critical |
307 | Unknown tube type or config error | Spindown tube identification or config failure | warning |
309 | Conflicting switch settings detected | DIP switch configuration does not match expected standard | warning |
310 | SMB DIP switches not set to standard configuration | DIP switch scan during initialization | warning |
311 | Switch value not found in look-up table | DIP switch position maps to undefined configuration | error |
315 | Option enabled but no response | Enabled option does not respond to communication | warning |
316 | Error loading phrase with return codes | Phrase load operation fails with avret and avstat codes | error |
328 | Required parameter missing or invalid in optable field for libcot conversion | libcot attempts conversion when required field values are not found or invalid | error |
33 | Cannot read super block on device | Device super block read fails in imgspace/free/elfree operations | critical |
35 | Can not read super block on (x) | File system super block read failure on device (x) | error |
35 | Free list indirect error block in file system | File system free list corruption detected during imgspace operations | critical |
37 | Disk write error | Attempt to write to disk when partition full or filesystem corrupted | error |
3-rtvu-comm | Unable to request message from message exchange | Message request failure | critical |
4 | Cannot send to exchange or StopSIF cannot send to SFMN | Module communication failure after attachment | error |
4 | Unable to send message to message exchange | Message send operation failed to various exchanges (CROSlucm, Lucm, GETX, DMIX, RESX) | error |
400 | Error on table setup | error | |
401 | Received error on Reconstruction INIT | error | |
402 | Received error on Reconstruction START | error | |
403 | Received error on Reconstruction IMGSTORE | error | |
404 | Received error on Reconstruction ABORT | error | |
405 | Received error on Reconstruction DATAIN or RECDONE | error | |
406 | Did not receive function code from RECON in specified tries | error | |
407 | Error receiving IM OKSTU response from IMSUM | error | |
421 | Unrecognized message type received | Invalid message type in inter-process communication | warning |
422 | Improper process ID | Invalid process identifier in message | warning |
424 | X-ray tube was exposed to high-voltage before warm-up completed | High-voltage applied during tube cold-start phase | critical |
426 | Cannot load algorithm table | Algorithm table loading at startup or during operation | error |
427 | Cannot load trackp | Trackp resource loading | error |
428 | Cannot load cda | CDA resource loading | error |
429 | Unknown function parameter; unknown combination of parameter values | Function call with unrecognized parameters | error |
431 | Incorrect startup | Startup sequence error | error |
433 | No response from ELTP | ELTP component communication attempt | error |
434 | No response on filming shutdown | Filming system shutdown timeout | warning |
435 | Function timed out on specified item with error | Timeout during function execution on specified item | error |
435 | RTD handler timeout or error logger timeout | Tubeheat or error logging process timeout | error |
436 | Cycle time value not found in table | Cycle time lookup for value 0x0000 | error |
437 | Cannot delete selection or cannot update pati; cannot select or selection update failed | Selection deletion or patient info update operation | error |
438 | Cannot calculate scan angles or cannot determine tilt range | Scan angle calculation or tilt range determination | error |
439 | Communication problem with MPM or no response from task | MPM communication attempt or task availability check | error |
441 | Array processor or backprojector disabled | Array processor or backprojector component failure or disabled state | warning |
4-rtvu-comm | Unable to send message to message exchange | Message send failure | critical |
5 | Unable to delete message exchange | Cleanup or shutdown procedure | warning |
512 | ANB error - serial communication protocol error between SIF and GPU or SIF and XSC | Failure in message transmission or reply reception in serial communication channel | error |
529 | Incorrect amount of data error | FIFO contains unexpected data amount after scan on 68020 SIF | error |
530 | Counter interrupt error | Timeout waiting for counter interrupt during data acquisition on 68020 SIF | error |
531 | Total DMA size error | SIF and MPM DMA calculations do not match | error |
601 | SCAREMAN critical event timeout | Timer expires before reception of critical event that SCAREMAN waits on | error |
603 | Invalid SCAREMAN/SCAN state error | SCAREMAN encounters invalid state during SCAN command execution; state conflict prevents command action | error |
605 | Cannot repeat last multi-mode scan procedure | Repeat command received but procedure cannot be repeated (e.g. right after system reboot) | error |
606 | Unknown event received by SCAREMAN | SCAREMAN received an undecipherable external event | error |
607 | Error on alert board - SIF or MPM board communication failure detected during pre-scan test | SCAREMAN performs pre-scan check and detects SIF or MPM board in crash condition | error |
7 | Unable to jam message into exchange | Message insertion into queue fails | error |
701 | Error creating tape database | Tape database creation fails | error |
702 | Error doing a get my_slot() | Slot retrieval function fails | error |
704 | Error doing a sym_to_mpde() | Symbol to mode conversion fails | error |
705 | Error doing a reg_send() | Register send function fails | error |
706 | Error doing a reg_recv() | Register receive function fails | error |
721 | Error doing a rhl_rcp() | rhl_rcp() function fails | error |
722 | Error retry limit exceeded | Operation retries exceed configured limit | error |
724 | Error retry limit exceeded | Operation retries exceed limit again | error |
725 | Unknown msg received | System receives unrecognized message type | warning |
726 | Duplicate receive msg received | Same message received multiple times | warning |
727 | Node number is not in valid range | Network node number falls outside valid range | error |
728 | Circular msg list is full | Circular message buffer reaches capacity | error |
8 | Unable to spawn child task | Process creation failed for CBOX or CROS tasks | error |
8 | SCANMAN could not spawn child process (recon, imgstor, alloc) | error | |
8 | SCANMAN process spawn failure | Could not spawn SCANMAN subprocess (reconstruction, image storage, or allocator) | error |
80 | Error condition exists in SIF system | System detects an error condition | error |
8 (dpud) | Unable to spawn child task ~gmp | Process creation fails | error |
8-rtvu | Unable to spawn child task HAIR | Child process creation failure | critical |
9 | Child task activation failure | Unable to activate spawned child process | error |
9 | Unable to activate child task | Child task activation after spawning | error |
999 | Command shell error | Unknown; document does not provide details | unknown |
9 (dpud) | Unable to activate child task ~gmp | Process activation fails after spawn | error |
9-rtvu | Unable to activate child task HAIR | Child process activation failure | critical |
abrtx of ABORT_TAG to ACKW failed | ABORT_TAG transmission to ACKW process failed | Attempt to send ABORT_TAG to ACKW | error |
abrtx of ABORT_TAG to cali failed | ABORT_TAG transmission to CALI process failed | Attempt to send ABORT_TAG to CALI | error |
'abrtx' of ABORT_TAG to 'chn' failed | Failed to send abort tag to channel task | During abort procedure execution in channel task | error |
abrtx of ABORT_TAG to dsnd failed | ABORT_TAG transmission to DSND process failed | Attempt to send ABORT_TAG to DSND | error |
abrtx of ABORT_TAG to pilo failed | ABORT_TAG transmission to PILO process failed | Attempt to send ABORT_TAG to PILO | error |
abrtx of ABORT_TAG to recn failed | ABORT_TAG transmission to RECN process failed | Attempt to send ABORT_TAG to RECN | error |
abrtx of ABORT_TAG to sdat failed | ABORT_TAG transmission to SDAT process failed | Attempt to send ABORT_TAG to SDAT | error |
ACK/NACK BREAK (ANB) | Communication break error between gantry and console | Signal brush block misalignment during ring diagnostic or normal operation | error |
a failure occurred on last allocation | Memory allocation failure during 68000 or data memory test | Insufficient memory during test execution | error |
Aircal missing message | No air calibration exists for selected protocol | Attempt to scan with uncalibrated protocol | error |
Alert board error (aaa) | Error on alert board; aaa indicates SIF or MPM board in crash condition | SCAREMAN pre-scan test detects SIF or MPM not responding normally | error |
ANB_ERROR | ANB error | ANB system malfunction | error |
Anode Rotor Hard failures | Hard error in anode rotor subsystem | Anode rotor hard error detected in error log | critical |
Anode Rotor soft failures | Soft error in anode rotor subsystem | Anode rotor soft error detected in error log | warning |
An operation on parent exchange failed | Parent exchange operation failed | System attempts operation on parent message exchange | error |
APREPLRECO failed attempting to reply to RECO | RECO reply operation failed in APREPLRECO process | Attempt to send response to RECO | error |
a region parametric error occurred | Region parametric error during memory allocation | Invalid memory region parameters during test | error |
avoice data terminal ready not set error (uart cts) | RS 232 handshake control line check error | Auto Voice serial communication initialization | error |
avoice request to send not set error (uart dcd) | RS 232 handshake control line check error | Auto Voice serial communication initialization | error |
Background failures | Error in background acquisition process | Background scan acquisition failure detected in error log | error |
Bad centering value passed to AP | Invalid centering parameter sent to Analysis Processor | AP received invalid centering offset or position | error |
Bad lump value passed to AP | Invalid lump parameter value sent to Analysis Processor | AP received out-of-range or malformed lump value | error |
Bad PAR scalar weighing flag passed to AP | Invalid scalar weighing flag value for PAR | AP received out-of-range scalar weighing flag | error |
Bad PAR scalar weighing value passed to AP | Invalid scalar weighing coefficient for PAR | AP received out-of-range weighing value | error |
Bad PAR vector weighing size passed to AP | Invalid PAR vector weight array size parameter | AP received inconsistent vector weighing dimension | error |
Bad return tag from calibration 'pplread' | Invalid return tag from calibration read | pplread returned unexpected tag value | error |
Bad return tag from recon table pplread | Invalid response tag received from reconstruction table read | pplread operation completion | error |
Bad 'viewnum' passed to AP | Invalid view number parameter to Analysis Processor | AP received out-of-range or invalid view number | error |
Bad 'viewnum' sequence | Invalid sequence of view numbers detected | AP received views in non-sequential or invalid order | error |
Bad 'viewstat' passed to AP | Invalid view status flag sent to Analysis Processor | AP received invalid or unexpected view status | error |
BPRD | pplread of image from BP did not complete properly | Image read from BP completes but with errors or incomplete data | error |
BPRD | Image size too big | Image reconstruction produces output larger than allocated buffer | error |
BPRD: Image size too big | Reconstructed image exceeds maximum size limit | Image reconstruction resulted in oversized output | error |
BPRD: pplread of image from BP did not complete properly | Incomplete image data read from BP module | Partial data transfer or timeout during image read | error |
BPRD: pplread of image from BP failed | Failed to read image data from BP module | Communication or data read error from backprojection unit | error |
Bus error | Bus communication error occurred | Error detected on system communication bus | critical |
bwfile failed to write AP save data to file | Failed to write AP save data to disk file | System attempts to write AP-provided save data to disk | error |
bwfile failed to write calibration data to file | Calibration data write operation failed | System attempts to save calibration data to disk | error |
bwfile failed to write detector fan data to file | Detector fan data write operation failed | System attempts to write detector fan data to disk | error |
bwfile failed to write ripple vector data to file | Ripple vector data write operation failed | System attempts to write ripple vector calibration data | error |
bwfile failed to write source fan data to file | Source fan data write operation failed | System attempts to write source fan calibration data to disk | error |
C872:S22 | Unable to send FRSTDET message to XIDSK | System attempts to send FRSTDET message during data acquisition | error |
C872:S22 | SIF or MPM board in crash condition detected before scan | SCAREMAN pre-scan test detects SIF or MPM in crash condition | error |
C872:S22 | SPEAK CONSOLE address low response error | SPEAK CONSOLE (C) command sent, received incorrect response format | error |
C872:S22 | Unable to receive message from AP for data save | System attempts to receive data save message from acquisition processor | error |
CALIB database does not exist, creating one | Calibration database file is being created for first time after software revision | First time running calibration procedures after software update | info |
Can't create erlg exchange ERLX | ERLX message exchange cannot be created | PERL task initialization | critical |
Can't create erlg exchange ERLX | System cannot create the ERLX error logging exchange | During PERL task startup | critical |
can't identify plot on display | System cannot verify plot was successfully displayed | After attempting to render plot on display screen | error |
can't identify plot on display | Display system cannot recognize or communicate with plot process | After plot process starts, during display connection handshake | error |
Can't receive a message from erlg exchange ERLX | System cannot receive messages from ERLX exchange | During error logging message handling | error |
can't signal done plot on display | Main control unable to send completion signal to plot process on display | After acceleration data calculation completes, signaling plot to finish | warning |
can't start coddcalc on heurikon | Acceleration calculation software failed to launch on Heurikon processor | When attempting to begin coddcalc process for data analysis | error |
can't start plot on display | Unable to launch plot application on display processor | When system attempts to start graphing module | error |
can't start plot on display | Display plotting software failed to launch | When attempting to begin graphical display of acceleration and velocity data | warning |
CBOX | Unable to delete task | Task deletion failure | error |
CBOX activate | Unable to activate child task CBOX | Child task activation attempt | error |
CBOX delete | Unable to delete task CBOX | Task termination or cleanup attempt | warning |
Center Cal protocol adjustment | Centering calibration protocol configuration | When using Center Cal protocol for phantom or centering pin scan | info |
CMDSHL_ERROR | Command Shell error | Command shell software failure | warning |
CMPR 1 | Unable to create message exchange 'C3dX' | System initialization or message queue setup | error |
CMPR 25 | Unable to signal event to a task 'THRE' | Event signaling operation during inter-task communication | error |
CMPR 3 | Unable to request message from message exchange 'C3dX' | Message request operation during system communication | error |
Couch position predata word 1 error | Couch position value in predata memory location 1 is invalid or out of expected range | During predata validation before test begins | error |
Could not reptstat INITDONE_FAIL to main | Failed to report INITDONE_FAIL status to main process | Attempt to report initialization failure to main | error |
Could not reptstat INITDONE_OK to main | Failed to report INITDONE_OK status to main process | Attempt to send completion status to main | error |
Could not REPTSTAT to 'recn' | Failed to report status to reconstruction component | Array processor initialization or communication failure | error |
Could not REPTSTAT to 'shel' | Failed to report status to shell component | Array processor initialization or communication failure | error |
Creation on AP memory map failed | Memory map allocation exceeded available data memory | AP memory map creation during system initialization | critical |
Creation on AP memory map failed (data memory exceeded) | Memory allocation for AP data failed | RECN task creation | critical |
'creax' failed for 'cali' | CALI task initialization failed | Process creax execution error | error |
'creax' failed for 'chn' | Task initialization failed; CHN task suspends | Internal process creation error during CHN task startup | error |
creax failed for chn | Task creation failed for CHN module | CHN task initialization | critical |
creax failed for cmpl | Task creation failed for CMPL module | CHN task initialization | error |
Creax failed for dmat | DMAT task creation failed | DSND task initialization | error |
creax failed for dsnd | DSND task creation failed | DSND task initialization | critical |
'creax' failed for 'lev' | Task creation failed for LEV module | LEV task initialization | critical |
creax failed for lev | LEV task creation failed | LEV task initialization | critical |
'creax' failed for 'pilo' | PILO task creation failed | PILO initialization attempt | critical |
'Creax' failed for 'recn' | RECN task creation failed | RECN process initialization | error |
'creax' failed for 'sdat' | SDAT task creation failed | SDAT process initialization | error |
creax failed for shel | Process creation failed for SHEL task | SHEL task initialization | error |
CROS | Unable to spawn child task | Child task spawn failure | error |
CROS delete | Unable to delete task CROS | Task termination or cleanup attempt | warning |
CROSS | Unable to activate child task | Child task activation failure | error |
CROSS activate | Unable to activate child task CROSS | Child task activation attempt | error |
CROS spawn | Unable to spawn child task CROS | System initialization or task management failure | error |
dbip 1 | Unable to create message exchange of DBIX | Message exchange initialization failure for DBIX | error |
dbip 100 | Unable to get regulus server | Regulus server connection failure | error |
dbip 102 | Unable to receive message from regulus queue of PVDB_MSG | Message receive failure from PVDB_MSG queue | error |
dbip 104 | Unable to get message queue id of DBIR_MSG | Message queue ID lookup failure for DBIR_MSG | error |
dbip 17 | Unable to allocate memory for message buffer dp_msgbuf | Memory allocation failure during initialization | error |
dbip 2 | Unable to attach to message exchange of DMIX | Message exchange attachment failure for DMIX | error |
dbip 4 | Unable to send message to regulus queue of PVDB_MSG | Message send failure to PVDB_MSG queue | error |
dbir 102 | Unable to receive message from DBIR_MSG | Message receive failure from DBIR_MSG queue | error |
dbir 103 | Unable to send message to IRTB_MSG | Message send failure to IRTB_MSG queue | error |
dbir 104 | Unable to get a message queue id of DBIR_MSG | Message queue ID lookup failure for DBIR_MSG | error |
dbir 174 | Unable to allocate memory for image header buffer | Memory allocation failure for image header | error |
DBIX | Unable to attach message exchange | Message exchange attach failure | error |
DBIX attach | Unable to attach message exchange DBIX | Message exchange attachment during initialization | error |
DCIP 2 | Unable to attach to message exchange 'DSPI' | DCIP subsystem attempting to connect to DSPI | error |
DCIP 26 | Unable to wait for event condition DCIP | Event wait operation during DCIP processing | error |
DCIP-4 | Unable to send message to message exchange 'DSPI' | Message transmission from DCIP | error |
Detector number out of range in predata word for first fan | First fan detector number exceeds valid range in predata | Invalid detector number in scan predata word | error |
Detector numbers in data not in sequence | Detector number sequence is incorrect in scan data | Scan data contains out-of-order or missing detector numbers | error |
DIAGREPORT | Diagnostic error report | Diagnostic procedure generated error | error |
dits counter not reset to 0 error | Digital input/test signal counter did not reset to zero | During acceleration test initialization | error |
divide by 0 error | Plot file not updated due to mathematical error in data processing | Bad data received from couch position system | error |
divide by 0 error | Math division by zero in plot calculation | Invalid data from couch causing zero divisor in formula | error |
DMA to/from AP failed | Direct memory access transfer to or from AP failed | System attempts DMA operation with acquisition processor | critical |
DMIX | Unable to attach message exchange | Message exchange attach failure | error |
DMIX attach | Unable to attach message exchange DMIX | Message exchange attachment during initialization | error |
Drives Disable | Gantry drive system disabled or inhibited | Signal brush block misalignment during operation or diagnostic | error |
DSP_ERR | Digital Signal Processor error | DSP system reported error or malfunction | error |
Duplicated AP_ABORTDONE message | Abort done message received multiple times | Duplicate message sent or not cleared after receipt | warning |
Duplicated AP_INITDONE message | Initialization done message received multiple times | Duplicate message sent or not cleared after receipt | warning |
Duplicated AP_RECONDONE message | Reconstruction done message received multiple times | Duplicate message sent or not cleared after receipt | warning |
Duplicated AP_STARTDONE message | Start done message received multiple times | Duplicate message sent or not cleared after receipt | warning |
eror getsrvr | File open error when getting microcode data file | File may be locked or gone during diagnostic test | error |
ERROR | System error detected and logged | Error condition exists in system | error |
ERROR: bad detector xxxx | A detector channel has been identified as defective during center program execution | Occurs when center program detects defective detector during global centering constant generation | error |
Error executing write | Write operation to system monitor board failed | Write command failure | error |
Error on alert board = aaa | SIF or MPM board in crash condition; aaa indicates which board | SCAREMAN pre-scan test detects SIF or MPM not communicating properly | error |
Error reading calibration parameters | System unable to read calibration parameter data | Calibration memory or file access failure | critical |
error reading scan data | Scan data acquisition failed | Couch did not reach end point or moved during acquisition | error |
error unknown | Unknown error condition | Error detected but cause cannot be determined | unknown |
ESTOPERR | Improper ESTOP sequencing | Emergency stop sequence violated | critical |
Exposure Ends Prematurely | X-ray exposure terminates before programmed duration | HVG generator error or exposure timing circuit fault | error |
Failed to allocate segment for bad detectors | Memory allocation failed for bad detector tracking | System attempts to allocate memory for bad detector list | error |
FATALER | Fatal error | Critical system failure | critical |
fatal message error | Fatal error condition with unspecified cause | Various critical system failures | critical |
fatal message error | Fatal error occurred; scan cannot continue | Various system errors including couch positioning or data write failures | critical |
FAULT | Forward drive, bias or overcurrent fault; test mode active | Forward drive circuit fault, bias circuit fault, overcurrent condition detected, or during test | error |
FIL bit 01 (CRX-125) | Open filament detected | Filament circuit open or disconnected | error |
FIL bit 01 (CRX-200) | Filament feedback fault | Filament feedback circuit failure | error |
FIL bit 02 (CRX-125) | Filament test button pressed | Test button activated by operator | info |
FIL bit 02 (CRX-200) | Filament over current detected | Filament current exceeds maximum threshold | error |
FIL bit 04 (CRX-125) | Filament inverter power supply voltage too low | Filament inverter supply voltage below minimum | warning |
FIL bit 04 (CRX-200) | Open filament detected | Filament circuit open or disconnected | error |
FIL bit 08 (CRX-125) | Filament overcurrent detected | Filament current exceeds maximum threshold | error |
FIL bit 08 (CRX-200) | Filament inverter inoperative | Filament inverter circuit failure | error |
FIL bit 10 (CRX-125) | Filament inverter shoot-thru sensed | Filament inverter shoot-through condition detected | error |
FIL bit 10 (CRX-200) | Filament inverter shoot-thru sensed | Filament inverter shoot-through condition detected | error |
FIL bit 20 (CRX-125) | 15V switched power supplies are too low | 15V supply voltage below threshold | warning |
FIL bit 20 (CRX-200) | Shorted filament | Filament circuit short detected | error |
FIL bit 40 (CRX-125) | Filament current feedback missing | Filament current feedback circuit failure | error |
FIL bit 40 (CRX-200) | Filament test push button pressed or power supply fault | Test button activated or filament supply failure | warning |
FIL bit 80 (CRX-125) | Missing inverter current sense | Filament inverter current feedback missing | error |
FIL bit 80 (CRX-200) | Cannot select filament | Filament selection circuit failure | error |
file: Can't delete image file | Unable to delete image file from storage | File in use or insufficient permissions | warning |
file: Can't write header to new image file | Unable to write header data to new image file | File write failure | error |
file read error | File read error during microcode data retrieval | Cannot read microcode data file contents | error |
file seek error | File seek error during microcode data retrieval | Error accessing file position during diagnostic | error |
FLOAT_ERR | Floating-point exception error | Software floating-point math error | error |
get_info:couch position must be outside of view, 450mm or le | Couch is positioned too close to or inside the scan circle during pilot scan setup | Couch position exceeds 450mm proximity to scan field boundary when pilot scan initiated | warning |
getrenv for $RECON failed | Environment variable RECON retrieval failed | Attempt to read RECON environment variable | error |
getsrvr failed | Server retrieval operation failed | Attempt to get server reference | error |
HCALERR | Heat calculator error | Heat calculation software malfunction | warning |
HINTERR | Hardware interlock ISP error | Interlock system failure or bypass detected | error |
HSSHARD | High Speed Rotor hardware error | HSR hardware malfunction | error |
HSSSOFT | High Speed Rotor software error | HSR software malfunction or control failure | error |
HVBUS | H.V. bus voltage greater than 400 VDC | High voltage bus exceeds 400 volts DC | warning |
HVG_INT | High Voltage Generator hardware error | HVG hardware malfunction or interrupt | error |
HVI_ERR | High Voltage Power Supply Interface software error | HVPSI software malfunction | error |
HVIRINT | HVPSI hardware error | High Voltage PSI hardware malfunction | error |
HVPSI failures | High voltage power supply interface failure | HVPSI error detected in error log | error |
iaddr | Unable to allocate memory for message buffer | Memory allocation failure for messaging | critical |
iaddr buffer | Unable to allocate memory for a message buffer, iaddr | Message buffer creation request | error |
IDSK: An operation on parent exchange failed | Parent exchange operation failure | Exchange communication error | error |
IDSK: bwfile failed to write AP save data to file | File write operation failed for AP save data | Disk write error | error |
IDSK: bwfile failed to write calibration data to file | File write operation failed for calibration data | Disk write error during calibration | error |
IDSK: bwfile failed to write detector fan data to file | File write operation failed for detector fan data | Disk write error during fan data logging | error |
IDSK: bwfile failed to write ripple vector data to file | File write operation failed for ripple vector data | Disk write error during calibration data logging | error |
IDSK: bwfile failed to write source fan data to file | File write operation failed for source fan data | Disk write error during fan data logging | error |
IDSK: DMA to/from AP failed | Direct memory access transfer to/from AP failed | Hardware communication error | critical |
IDSK: Failed to allocate segment for bad detectors | Failed to allocate memory segment for bad detector list | Memory allocation failure | error |
IDSK: Invalid state transition | System attempted invalid state transition | Software state machine error | error |
IDSK: More buffers than the length of Queue | Buffer count exceeds queue capacity | Queue overflow condition | warning |
IDSK: More remote agents than the length of Queue | Remote agent count exceeds queue capacity | Too many remote agents connecting | warning |
IDSK: ppfsendx to AP for ap save data failed | Failed to send save data to AP via ppfsendx protocol | Communication protocol error | error |
IDSK: pplread of save data from AP failed | Failed to read save data from acquisition processor | Communication or data read error | error |
IDSK: pplread/pplwrite failed | Failed to read or write via ppl protocol | Communication protocol error | error |
IDSK: Too many views out of sequence. Buffer overflow | Data buffer overflow due to out-of-sequence views | Excessive out-of-order data or slow processing | error |
IDSK: Unable to attach to exchange on AP | Failed to attach to exchange on acquisition processor | Exchange attachment failure | error |
IDSK: Unable to free bad views memory segment | Failed to deallocate bad views memory segment | Memory management error during cleanup | warning |
IDSK: Unable to free file parameters memory segment | Failed to deallocate file parameters memory segment | Memory management error during cleanup | warning |
IDSK: Unable to grab bad views memory segment | Failed to allocate or access bad views memory segment | Memory allocation failure | error |
IDSK: Unable to grab file parameters segment | Failed to allocate or access file parameters memory segment | Memory allocation failure | error |
IDSK: Unable to grab parameter memory segment | Failed to allocate or access parameter memory segment | Memory allocation failure | critical |
IDSK: Unable to receive message from AP for data save | Failed to receive data save message from acquisition processor | Communication failure during data save operation | error |
IDSK: Unable to send calibration ready message to AP | Failed to send calibration ready notification to AP | Communication failure to AP | warning |
IDSK: Unable to send NOMOREVIEWS message to AP | Failed to send end-of-acquisition message to AP | Communication failure to AP | error |
IDSK: Unable to send SAVEMPM message to home exchange | Failed to send save message to home exchange | Communication failure to exchange | error |
IDSK: Unable to send START_PASS_TAG to AP | Failed to send start pass tag command to AP | Communication failure to AP | error |
illegal signal | Invalid signal received by system | Malformed or unexpected signal data | warning |
'initx' failed for 'ACKW' | Initialization of ACKW task failed | ACKW task cannot initialize | error |
initx failed for ACKW | Initialization failed for ACKW process | ACKW process initialization | error |
'initx' failed for 'ACKX' | ACKX module initialization failed | PILO task startup | error |
initx failed for arbi on the BP | ARBI task initialization failed on backplane | DSND startup sequence | error |
initx failed for cali | Initialization failed for CALI (calibration) process | CALI process initialization | error |
'initx' failed for 'cali' | Calibration task initialization failed | Calibration process initialization during RECN startup | error |
initx failed for chn | CHN task initialization failed | DSND startup or operation | error |
'initx' failed for 'chn' | Channel task initialization failed | Channel process initialization during RECN startup | error |
initx failed for chn in DSND | Initialization failed for CHN module from DSND context | DSND task startup | error |
initx failed for dsnd | Initialization failed for DSND (data send) process | DSND process initialization | error |
'initx' failed for 'IDSK' on the MPM | IDSK initialization failed on MPM module | IDSK process initialization during SDAT startup | error |
'initx' failed for 'iev' | Task initialization failed | Initialization error in IEV subtask during CHN startup | error |
initx failed for lev | Initialization failed for LEV module | CHN task startup | error |
'initx' failed for 'lev' | LEV module initialization failed | PILO task startup | error |
'initx' failed for 'MRCV' on the MPM | MRCV module initialization failed on MPM | MPM startup | error |
'initx' failed for 'msnd' on the MPM | Task initialization failed on Multi-Processor Module | Initialization error for message send task on MPM | error |
'initx' failed for 'pilo' | Initialization of pilot component failed | Pilot component cannot initialize | error |
initx failed for pilo | Initialization failed for PILO process | PILO process initialization | error |
initx failed for recn | Initialization failed for RECN (reconstruction) process | RECN process initialization | error |
'initx' failed for 'recn' | Task initialization failed; CHN suspends | Initialization error in RECN subtask | error |
initx failed for sdat | Initialization failed for SDAT process | SDAT process initialization | error |
'initx' failed for 'sdat' | Task initialization failed | Initialization error in SDAT (save data) subtask | error |
initx failed for shel | SHEL task initialization failed | DSND task startup sequence | critical |
'initx' failed for 'shel' | Shell task initialization failed affecting RECN or SDAT | Shell process initialization during RECN or SDAT startup | error |
input & output buffers don't compare | Input and output buffer contents do not match | Buffer comparison check failed | critical |
Invalid 'numfans' passed to AP | Invalid number of detector fans parameter | AP received invalid detector fan count | error |
Invalid 'numproc' passed to AP | Invalid number of processing units parameter | AP received invalid processor count | error |
Invalid scantype | Scan type parameter is invalid or unrecognized | Scan type validation during initialization | error |
Invalid sequencer flag after ucode pipeline | Unexpected sequencer flag state after microcode execution | Pipeline completion with invalid flag value | error |
Invalid state transition. (State, Tag) | Illegal state transition attempted with given state and tag | System detects invalid state machine transition | error |
Invalid tag received at home exchange | Unrecognized or malformed message tag received | Corrupted or unexpected message in inter-task communication | error |
IOCTL() error obtaining tty info | Terminal interface configuration error | TTY info retrieval failure | error |
ISAV: file: Can't delete image file | System cannot delete image file | Image file deletion operation failure | warning |
ISAV: file: Can't write header to new image file | Cannot write header to new image file | Image file header write operation failure | error |
ISAV: newfile: Can't allocate memory segment to read image h | Memory allocation failed for image header reading | Memory allocation request during image file header read | error |
ISAV: newfile: Can't close newly created image file | Unable to close newly created image file | File close operation failure after image creation | error |
ISAV: newfile: Can't delete full image file | System cannot delete full resolution image file | Full image file deletion operation failure | warning |
ISAV: newfile: Can't link image and full image files | Cannot create link between image and full image files | File linking operation failure | error |
ISAV: newfile: Can't read header from image file | Unable to read image file header | Image header read operation failure | error |
ISAV: newfile: Can't release memory | Memory deallocation failed | Memory release operation failure | error |
ISAV: newfile: Can't rename the image file | Unable to rename image file | Image file rename operation failure | warning |
ISAV: newfile: Can't write image to new image file | System cannot write image data to newly created file | Image data write operation failure | error |
ISAV: Unable to write image data to file | System cannot write image data to storage | Image file write operation failure | error |
KEYX-4 | Unable to send message to message exchange dmux | Task KEYX execution | error |
KV or MA errors | Kilovoltage or milliamperage measurement error | KV or MA error detected in error log | error |
LED update command not understood | LED control command not recognized | Invalid or incompatible LED command | warning |
LOAD PHRASE (L) command sent, response 0 ( ) | Phrase load command failed with 4-character response error | Operator enters phrase from menu, system receives incomplete response | error |
LOGO-1 | Unable to create message exchange LOGX | Task LOGO initialization | error |
LOGO:1 | Unable to create message exchange LOGX | Task LOGO initialization failure | error |
LOGO:17 | Unable to allocate memory segment SHOW | Memory allocation failure during LOGO task startup | critical |
LOGO-17 | Unable to allocate memory segment SHOW | Task LOGO memory allocation | error |
LOGO-2 | Unable to attach to message exchange DPRX | Task LOGO startup | error |
LOGO:2 | Unable to attach to message exchange DPRX | Message exchange attachment failure | error |
LOGO-2a | Unable to attach to message exchange dmux | Task LOGO startup | error |
LOGO-2b | Unable to attach to message exchange Lucm | Task LOGO startup | error |
LOGO:4 | Unable to send message to message exchange dmux | Message send operation failed | warning |
lwrite error to raw data file | Write failure to raw data file | File system or disk I/O error during data write | error |
lwrite of plot.dat error | Write failure to plot data file | File system error or bad couch data during plot generation | error |
MCAT: Detector number out of range in predata word for first | First fan detector number exceeds valid range | Detector number in predata word exceeds maximum valid value | error |
MCAT: Detector numbers in data not in sequence | Detector data sequence is out of order | Detector numbers read from scan data are non-sequential | error |
MCAT: Error reading calibration parameters | Calibration parameters cannot be read | Calibration parameter read operation failure | error |
MCAT: Pilot mask bit set for CT scan in predata word | Pilot mask bit is set in scan predata | Pilot mask bit flag is on in predata word | warning |
MCAT: Timed out waiting for agents to read calibration | Timeout while agents read calibration data | Calibration read exceeds timeout threshold | warning |
MCAT: Timed out waiting for PROCDONE | Timeout while waiting for PROCDONE message | PROCDONE message not received within timeout period | warning |
MCAT: Unable to allocate calibration memory segment | Cannot allocate memory for calibration data | Memory allocation request for calibration fails | error |
MCAT: Unable to free calibration memory segment | Cannot deallocate calibration memory | Memory deallocation failure for calibration data | error |
MCAT: Unable to free recon parameters memory segment | Cannot deallocate reconstruction parameters memory | Memory deallocation failure for recon parameters | error |
MCAT: Unable to send IDSKDONE message to home exchange | Cannot send IDSKDONE message to home exchange | Inter-process communication failure for IDSKDONE message | error |
MCAT: Unable to send IMAGE_IN message to home exchange | Cannot send IMAGE_IN message to home exchange | Inter-process communication failure for IMAGE_IN message | error |
MCAT: Unable to send message to exchange for OSCNDONE_ACT | Cannot send OSCNDONE_ACT message to exchange | Inter-process communication failure for OSCNDONE_ACT message | error |
MCAT: Unable to send message to exchange for PROCDONE_ACT | Cannot send PROCDONE_ACT message to exchange | Inter-process communication failure for PROCDONE_ACT message | error |
MCAT: Unable to send message to exchange for RAWIN_ACT | Cannot send RAWIN_ACT message to exchange | Inter-process communication failure for RAWIN_ACT message | error |
MCAT: Unable to send PROCDONE message to home exchange | Cannot send PROCDONE message to home exchange | Inter-process communication failure for PROCDONE message | error |
MENU:2 | Unable to attach to message exchange MENX | Message exchange attachment failure | error |
MENU-2 | Unable to attach to message exchange MENX | Task MENU startup | error |
MENU-2a | Unable to attach to message exchange RESX | Task MENU startup | error |
MENU-2b | Unable to attach to message exchange CINX | Task MENU startup | error |
MENU-2c | Unable to attach to message exchange COLX | Task MENU startup | error |
MENU-2d | Unable to attach to message exchange IMGX | Task MENU startup | error |
MENU:4 | Unable to send message to message exchange RESX | Message send operation failed | warning |
MENU-4 | Unable to send message to message exchange RESX | Task MENU execution | error |
MENU-4a | Unable to send message to message exchange COLX | Task MENU execution | error |
MENU-4b | Unable to send message to message exchange CINX | Task MENU execution | error |
MENU-4c | Unable to send message to message exchange IMGX | Task MENU execution | error |
MENU:8 | Unable to spawn child task CNPM | Child task spawn operation failed | error |
MENU-8 | Unable to spawn child task CNPM | Task MENU execution | error |
MENU-8a | Unable to spawn child task PRWM | Task MENU execution | error |
MENU-9 | Unable to activate child task CNPM | After spawning CNPM task | error |
MENU:9 | Unable to activate child task CNPM | Child task activation failed | error |
MENU-9a | Unable to activate child task PRWM | After spawning PRWM task | error |
message id set but initdone = 0 | Message ID set while initialization is not complete | Premature message ID assignment during initialization | error |
micro ld failed trying to load microcode memory | Microcode load operation failed | Microcode memory loading attempt | critical |
MISCERR | Miscellaneous error not fitting other categories | Software error not classified elsewhere | warning |
MORE | Unable to release memory segment | Memory deallocation failure | error |
More buffers than the length of Queue | Number of buffers exceeds queue length capacity | System detects buffer count exceeds queue size | warning |
MORE release | Unable to release memory segment MORE | Memory deallocation during shutdown or cleanup | warning |
More remote agents than the length of Queue | Number of remote agents exceeds queue length | System detects more agents than queue can handle | warning |
MREQERR | X_SHOT request error | Scan request failed or rejected | error |
newfile: Can't allocate memory segment to read image header | Memory allocation failed for image header read operation | Insufficient available system memory | error |
newfile: Can't close newly created image file | Unable to close newly created image file after write | File system error or resource exhaustion | error |
newfile: Can't delete full image file | Unable to delete full image file | File in use or insufficient permissions | error |
newfile: Can't link image and full image files | Unable to link image and full image file together | File system error or missing files | error |
newfile: Can't read header from image file | Unable to read image file header | File access error or corrupted file | error |
newfile: Can't release memory | Unable to release allocated memory segment | Memory management error | error |
newfile: Can't rename the image file | Unable to rename image file | File in use or file system error | error |
newfile: Can't write image to new image file | Unable to write image data to newly created file | File write failure or storage error | error |
No Audio | Audio feedback or alarm not functioning | HVG generator error or system malfunction | warning |
No Button Hit Detected | Operator console button not responding | Button press not detected during diagnostic | warning |
NOCALFILE_ERR | Calibration Request error: requested calibration file cannot be found | Calibration file lookup fails or file is corrupt | error |
No DMA resource channel in use | DMA channel resource unavailable | Requested DMA channel is in use or unavailable | warning |
No Exposure | X-ray generator fails to produce exposure | HVG (Spellman) generator malfunction or loss of slip ring power | error |
No Indicator (X-ray ON) | X-ray ON indicator lamp not illuminating | HVG generator error or indicator circuit fault | warning |
no mpc reset initdone = 1 | MPC reset not performed while initialization is complete | System initialization state mismatch | error |
No Small Drives Power | Small drives do not have power | Loss of power to small drives subsystem | error |
no so. mess. in & out complete interrupt error | No solicited message input/output complete; no interrupt raised | Solicited operation timeout without interrupt signal | error |
NOT_IN_ERR | Interpreted as no error | Error code value 1000 | info |
no unsol. mess. rcvne interrupt error | No unsolicited message received; no interrupt error | Expected unsolicited message did not arrive and no interrupt was raised | warning |
ONE | Unable to release memory segment | Memory deallocation failure | error |
ONE release | Unable to release memory segment ONE | Memory deallocation during shutdown or cleanup | warning |
Open failure() | Communication initialization failure | Device communication failure | error |
OPIX | Unable to create message exchange | Message exchange creation failure | error |
OPIX attach | Unable to attach message exchange OPIX | Message exchange attachment during initialization | error |
OPIX message | Unable to create message exchange OPIX | Message system initialization | error |
OSCN: Unable to allocate wtab memory segment | Failed to allocate wtab memory segment | Memory allocation failure | error |
OSCN: Unable to free wtab memory segment | Failed to deallocate wtab memory segment | Memory management error during cleanup | warning |
OVFLT | Rail overcurrent fault; current exceeds 50 amps | Current on power rails exceeds 50 amperes | critical |
PARAM_ERR | Parameter error generated when calfmr receives out-of-range parameter | Out-of-range parameter from optable, control, or database; invalid MA offset; unsupported CALM command; buffer handle mismatch; calibration file size too small; parameter size out of range for calibration | error |
Patient Support Horizontal failures | Horizontal patient support positioning failure | Patient support horizontal error detected in error log | warning |
PDIX | Unable to create message exchange | Message exchange creation failure | error |
PDIX message | Unable to create message exchange PDIX | Message system initialization | error |
PEDX | Unable to attach message exchange | Message exchange attach failure | error |
PEDX attach | Unable to attach message exchange PEDX | Message exchange attachment during initialization | error |
Pilot mask bit set for CT scan in predata word | Pilot scan mode bit incorrectly set in CT scan predata | Incorrect scan mode or data corruption in predata word | warning |
plot timeout | Plot software did not complete drawing within timeout period | During graphical rendering of acceleration and velocity results | warning |
plot timeout | Plot application failed to complete graphing operation within timeout period | During acceleration graph plotting on display | error |
'ppfsendx' of APCSLIB_TAG to MPM failed | Failed to send APCSLIB tag to MPM | Inter-process message send failure | error |
ppfsendx of AP_REJECT to BP failed | Failed to send rejection message to backplane | DSND rejects data or operation | error |
'ppfsendx' of column read request to the MPM failed | Column read request transmission to MPM failed | Column data read request | error |
'ppfsendx' of column request to the MPM fail | Column request transmission to MPM failed | Column processing request | error |
'ppfsendx' of FFT buffer request to the MPM failed | FFT buffer request transmission to MPM failed | IPC send failure for FFT processing buffer | error |
'ppfsendx' of first buffer request to the MPM failed | Failed to send initial buffer request to MPM | Inter-process message send failure | error |
'ppfsendx' of first buffer request to the MPM failed | Buffer request transmission to MPM failed | IPC send failure when requesting first processing buffer | error |
'ppfsendx' of first column request to the MPM failed | First column data transmission to MPM failed | Column data processing | error |
'ppfsendx' of first row request to the MPM failed | First row data transmission to MPM failed | Data processing initiation | error |
'ppfsendx' of float buffer request to the MPM failed | Floating-point buffer request transmission to MPM failed | IPC send failure for float buffer request | error |
'ppfsendx' of integer buffer request to the MPM failed | Integer buffer request transmission to MPM failed | IPC send failure for integer buffer request | error |
'ppfsendx' of row request to the MPM failed | Row request transmission to MPM failed | Row processing request | error |
ppfsendx to AP for ap save data failed | Failed to send save data to AP via ppfsendx | System attempts to send save data to AP | error |
'pplread' completion tag not PPLR_CMP_TAG | pplread operation completed with error status | pplread completion | error |
'pplread' failed for calibration read | Calibration read operation failed | pplread process execution error | error |
pplread failed for recon table read | Reconstruction table read operation failed | pplread function execution | error |
pplread of save data from AP failed | Failed to read save data from acquisition processor | System attempts to read saved data from AP | error |
pplread/pplwrite failed | PPL read or write operation failed | System attempts PPL communication operation | error |
pplwrite completion tag not PPLW SEND OK | Write completion returned unexpected status code | DSND receives write completion notification | error |
pplwrite completion tag not PPLW SEND OK | PPL write completion tag does not indicate successful send | PPL write operation completion in DSND task | error |
'pplwrite' completion tag not PPLW_SEND_OK | pplwrite operation completed with error status | pplwrite completion | error |
'pplwrite' of rows to the MPM failed | Row data write to MPM failed | Data writing operation | error |
pplwrite of views to the BP/EB failed | Failed to write image views to backplane/expansion board | DSND attempts to write reconstructed views | error |
'ppsendx' of read msg to 'IDSK' failed | Failed to send read message to IDSK via parallel port send | During data read from IDSK in SDAT task | error |
Predata sample x =x should = x | Predata sample value does not match expected value at starting position | Validation of initial measurement sample before data collection starts | error |
ptr | Unable to allocate memory segment | Memory allocation failure | critical |
ptr memory | Unable to allocate memory segment ptr | Memory allocation request during startup or operation | critical |
QSPIERR | Queued Serial Peripheral Interface error | QSPI communication failure | error |
rcv. unsol. mess. timeout | Receive unsolicited message timeout | Unsolicited message reception did not complete within timeout period | warning |
readerr | Error logging and help message display system for autocal failures | Any error during Air Cal Touch-up or autocal process | warning |
REGU | Unable to get process id | Process ID lookup fails for a required module | error |
Regulus | Unable to get Regulus message queue id | Queue ID retrieval failure | error |
Regulus queue id | Unable to get a Regulus message queue id | Queue ID retrieval during initialization | critical |
Regulus queue send | Unable to send a message to Regulus queue | Message transmission to Regulus subsystem | error |
REGU: Unable to get process id | Failed to retrieve process identifier | System call to obtain process ID failed | error |
Relay ('sendx') of END_TAG to 'pilo' failed | Failed to relay end tag to pilot component | Inter-task communication failure | error |
Relay ('sendx') of MPM_NOMOREVIEWS_TAG to 'chn' failed | Failed to relay no more reviews tag to channel component | Inter-task communication failure | error |
Relay ('sendx') of P_PASS_TAG to 'pilo' failed | Failed to relay pass tag to pilot component | Inter-task communication failure | error |
Relay ('sendx') of PPLW_CMP_TAG to 'chn' failed | Failed to relay pipeline complete tag to channel component | Inter-task communication failure | error |
Relay ('sendx') of START_PASS_TAG to 'pilo' failed | Failed to relay start pass tag to pilot component | Inter-task communication failure | error |
'reqx' failed at home exchange | Request operation failed at central message hub | Communication or processing failure at home exchange | error |
'reqx' failed for COL_CHN ucode pipeline completion | COL channel ucode pipeline completion request failed | Pipeline processing | error |
'reqx' failed for FLTAIR_CHN ucode pipeline completion | FLTAIR channel ucode pipeline completion request failed | Pipeline processing | error |
'reqx' failed for ROW_CHN ucode pipeline completion | ROW channel ucode pipeline completion request failed | Pipeline processing | error |
'reqx' failed for ucode pipeline completion | Request for microcode pipeline completion failed | Microcode pipeline not responding or timeout | error |
'reqx' failure at 'ACKX' waiting for 'pplread' completion | ACKX module timeout waiting for pplread completion | Data read operation timeout | error |
reqx failure at cmpl waiting for save data completion | Request failed at CMPL waiting for SDAT completion | Data save completion timeout in CHN task | error |
reqx failure at dmat waiting for pplwrite completion | Request failed at DMAT waiting for write completion | DSND synchronizes with view write operation | error |
'reqx' failure at 'pilo' waiting for 'pplwrite' completion | PILO module timeout waiting for pplwrite completion | Data write operation timeout | error |
RESX | Unable to attach message exchange | Message exchange attach failure | error |
RESX attach | Unable to attach message exchange RESX | Message exchange attachment during initialization | error |
Retry expiration | Message retry limit exceeded | Message transmission retry count reached maximum | error |
retsrvr failed trying to release server | Server release operation failed | Attempt to release server resource | error |
rfile failed for downloading of twiddle table | Twiddle table download operation failed | Twiddle table file read/download attempt | error |
ROTOR_TIMER | Rotor timer message; warning or timeout indicator | Rotor timing anomaly detected | warning |
RTR_ERR | Rotor software error | Rotor control software malfunction | error |
RTRRINT | Rotor hardware error | Rotor hardware malfunction or interrupt | error |
RVDP 1 | Unable to create message exchange 'RVDX' | RVDP subsystem initialization | error |
RVDP-1b | Unable to create message exchange 'RMRX' | RVDP module initialization | error |
RVDP-3 | Unable to request message from message exchange 'RVDX' | Message retrieval from RVDP exchange | error |
RVDP 4 | Unable to send a message to message exchange 'RMRX' | Message transmission to RMRX during operation | error |
RVDP-4b | Unable to send a message to message exchange 'CRVX' | Outgoing message transmission | error |
sagc1 | Unable to create message exchange SAG0 | Message exchange creation fails | error |
sagc17 | Unable to allocate memory for strip_buf buffer | Memory allocation fails | error |
sagc2 | Unable to attach message exchange SAGX | Message exchange attachment fails | error |
sagc8 | Unable to spawn task SCCR | Task creation fails | error |
sagc9 | Unable to activate process SCCR | Process activation fails | error |
SC1 0001 | Inverter chassis was source of fault | Inverter chassis fault detected | error |
SC1 0002 | AC Input chassis was source of fault | AC Input chassis fault detected | error |
SC1 0004 | Filament Chassis was source of fault | Filament Chassis fault detected | error |
SC1-0008 | Inverter Diag was source of fault | Inverter Diag fault detected | error |
SC1-0010 | Panel Interlock–Inverter or AC Input fault | Panel interlock fault detected | error |
SC1-0020 | LCL Power–/+ 15 vSW missing on System Control PCB | Power supply voltage missing | critical |
SC1 0040 | Shutdown– the XSC shutdown the HVG's contactor | XSC initiated HVG contactor shutdown | warning |
SC1-0080 | ALE (kv>30) without EXGATE | High voltage output without gate command | critical |
SC1 0100 | Regulation Error– KV out of tolerance > 1% | KV output exceeds tolerance by more than 1% | error |
SC1 0200 | Inverter Frequency Max detected | Inverter operating frequency at maximum | warning |
Scan Data Acquisition failures | Scan data acquisition process failure | Scan data acquisition error detected in error log | error |
Scan Drive positioning failures | Scan drive unable to position correctly | Positioning error or failure at power-up | error |
scan positioning timeout | Couch positioning failed to complete within expected time | During initial couch positioning at acceleration test start | error |
SCIERR | MC68331 serial diagnostic terminal error | MC68331 serial communication malfunction | error |
SDRVSER | Small drives software error | Small drive control software malfunction | error |
See Error Logger | System-level errors detected during startup or operation | Bootstrap completion or during normal operation | unknown |
sendx failed on AP_FREE_BUFF to chn | Failed to send buffer-free message to CHN task | DSND attempts to release buffer | error |
sendx of AP_DMN_OUT to dsnd failed | Failed to send DMN output message to DSND task | CHN task output request to DSND | error |
'sendx' of AP_DONE_SAVEDATA to requesting task failed | Failed to send save complete message to requesting task | AP task completing SAVEDATA operation | error |
sendx of AP_SAVEDATA to sdat failed | Failed to send save data message to SDAT task | CHN task data save request | error |
'sendx' of AP_SAVEDATA to 'sdat' failed | Failed to send save-data command to storage task | IPC send failure to SDAT (save data) task | error |
'sendx' of microcode pipeline complete failed | Message transmission of microcode pipeline completion failed | Microcode pipeline completion event | error |
sendx of microcode pipeline complete failed | Failed to send microcode pipeline completion message from LEV task | LEV task pipeline completion | error |
'Sendx' of RDCAL_TAG to 'cali' failed | Failed to send read calibration tag to calibration task | During calibration data transmission in RECN task | error |
'Sendx' of RDCAL TAG to 'cali' failed | RDCAL tag transmission to calibration module failed | Calibration data exchange | error |
SHUF | No free buffers for shuffle | SENDVIEW attempts to allocate buffer during image reconstruction | warning |
SHUF | pplwrite to AP did not complete (tracer = mid) | Data write to AP module interrupted or stalled mid-transfer | error |
SHUF | Unable to allocate memory for reconmap | Memory allocation fails during reconstruction map setup | error |
SHUF | Unable to free buffer: AP return address mismatch | Buffer deallocation detects address mismatch with AP module | critical |
SHUF | Unable to send NOMOREVIEWS message | SHUF cannot notify completion of view processing | error |
SHUF | Timed out waiting for buffer request (maybe AP) | Buffer request from AP module does not arrive within timeout period | warning |
SHUF | Starting View number out of range | Acquisition initiated with invalid starting view number | error |
SHUF: AP return address mismatch | Cannot free buffer due to address mismatch with AP module | Buffer deallocation attempted with incorrect return address | error |
SHUF: Failed trying to send buffer to MSND | Unable to send processed buffer to MSND module | Communication failure during buffer handoff | error |
SHUF: Invalid view number out of range | View number parameter is outside valid range | Out-of-range view number encountered during processing | error |
SHUF: No free buffers for shuffle | Insufficient buffer memory available for shuffle operation | Buffer pool exhausted during shuffle message processing | error |
SHUF: pplwrite to AP did not complete | Write operation to AP module incomplete | Communication failure during data transfer to AP | error |
SHUF: Starting View number out of range | View number parameter is outside valid range | Invalid starting view number provided to SHUF | error |
SHUF: Timed out waiting for buffer request | Buffer request from AP did not arrive within timeout period | AP process failed to request buffer within expected time | error |
SHUF: Unable to allocate memory for reconmap | Insufficient memory to allocate reconstruction map | Memory exhaustion during reconmap allocation | critical |
SHUF: Unable to free calibration memory segment | Failed to deallocate calibration memory segment | Memory deallocation error during cleanup | warning |
SHUF: Unable to free reconbuff memory segment | Failed to deallocate reconstruction buffer memory segment | Memory deallocation error during cleanup | warning |
SHUF: Unable to grab calibration memory segment | Failed to allocate calibration memory segment | Memory allocation failure during calibration setup | error |
SHUF: Unable to send FRSTDET message to XIDSK | Failed to send FRSTDET message to XIDSK | System processing error during message transmission | error |
SHUF: Unable to send NOMOREVIEWS message | Failed to send NOMOREVIEWS completion message | Communication failure after view processing | error |
SHUF: Unable to send view buffer ready message to MSND | Failed to notify MSND that view buffer is ready | Communication error during buffer handoff | error |
Small drives failures | Small drives subsystem failure | Small drives error detected in error log | error |
solicited input completed in error | Solicited input completed with error status | Input operation reported error status on completion | error |
solicited input complete timeout | Solicited input completion did not occur within timeout | Input operation timeout during solicited message handling | error |
solicited output completed in error | Solicited output completed with error status | Output operation reported error status on completion | error |
Solicited output complete timeout | Solicited output completion did not occur within timeout | Output operation timeout during solicited message handling | error |
SPAWNTIME | System initialization timeout in XSC+ | XSC+ initialization exceeds time limit | warning |
Speak Phrase Overtime Error | System timeout before receiving response to previous command | Previous command response not received before new command issued | error |
SPOTERR | Spot software error | Spot control software malfunction | error |
STARTPROC_TAG received before START successfully finished | STARTPROC_TAG arrived before START sequence completed | Premature STARTPROC_TAG reception | error |
'strtx' of AP_RUN_CHAIN to 'chn' failed | Failed to start chain execution in CHN task | IPC start failure when ordering chain run | error |
strtx of AP_RUN_CHAIN to chn failed | Failed to start AP_RUN_CHAIN on CHN task | Chain run initiation in CHN task | error |
strtx of BP_NOMOREVIEW_TAG to chn failed | Start request for BP no-more-review tag to CHN task failed | DSND attempts to start CHN with message | error |
'strtx' of MPM_NOMOREVIEWS_TAG to 'chn' failed | Failed to start/send end-of-data tag to CHN task | IPC start failure when forwarding MPM completion | error |
strtx of MPM_NOMOREVIEWS_TAG to dsnd failed | Failed to start no-more-reviews tag on DSND task | Review termination request in CHN task | warning |
strtx of STARTPROC_TAG to ACKW failed | STARTPROC_TAG transmission to ACKW process failed | Attempt to send STARTPROC_TAG to ACKW | error |
'Strtx' of STARTPROC_TAG to 'chn' failed | Failed to send start procedure tag to channel task | During procedure initiation in channel task | error |
strtx of STARTPROC_TAG to dsnd failed | STARTPROC_TAG transmission to DSND process failed | Attempt to send STARTPROC_TAG to DSND | error |
strtx of STARTPROC_TAG to pilo failed | STARTPROC_TAG transmission to PILO process failed | Attempt to send STARTPROC_TAG to PILO | error |
strtx of STARTPROC_TAG to recn failed (1) | STARTPROC_TAG transmission to RECN process failed (first instance) | Attempt to send STARTPROC_TAG to RECN | error |
Strtx of START_TAG to ACKW failed | START_TAG transmission to ACKW process failed | Attempt to send START_TAG to ACKW | error |
strtx of START_TAG to cali failed | START_TAG transmission to CALI process failed | Attempt to send START_TAG to CALI | error |
'Strtx' of START_TAG to 'chn' failed | Failed to send start tag to channel task | During channel startup in RECN task | error |
strtx of START_TAG to dsnd failed | START_TAG transmission to DSND process failed | Attempt to send START_TAG to DSND | error |
strtx of START_TAG to pilo failed | START_TAG transmission to PILO process failed | Attempt to send START_TAG to PILO | error |
strtx of START_TAG to recn failed | START_TAG transmission to RECN process failed | Attempt to send START_TAG to RECN | error |
strtx of START_TAG to sdat failed | START_TAG transmission to SDAT process failed | Attempt to send START_TAG to SDAT | error |
THDP-17 | Unable to allocate memory segment MPR_LOAD | Memory allocation during THDP operation | error |
THDP 2 | Unable to attach to message exchange 'THDX' | THDP subsystem attempting to connect to THDX | error |
Timed out before receiving second RDCAL message | Calibration message timeout | Expected RDCAL message not received within timeout period | error |
Timed out waiting for agents to read calibration | Calibration read operation exceeded timeout threshold | Slow process response or communication delay | error |
Timed out waiting for calibration 'pplread' complete | Calibration read operation timeout | pplread completion signal not received | error |
Timed out waiting for PROCDONE | PROCDONE message reception exceeded timeout threshold | Delayed process completion or communication failure | error |
Timed out waiting for recon table pplread complete | Reconstruction table read operation exceeded timeout threshold | pplread table read operation | error |
Time out | Operation timeout | Operation did not complete within timeout period | error |
time out on read | Button press not detected within timeout period | Button not pressed during test or button failed to register press signal | warning |
Time-Out on read of echo back | No response from system monitor board within timeout | Board not responding | error |
timeout on signal from coddcalc done | Coddcalc did not send completion signal within timeout period | After scan data collection, waiting for coddcalc calculation completion | error |
timeout on signal from coddcalc done | Coddcalc failed to send completion signal within timeout period | After scan data collection, waiting for coddcalc to finish calculations | error |
timeout on signal from coddcalc to start scan | No signal received from coddcalc to initiate scan within time limit | After coddcalc launches, waiting for start-scan signal | error |
timeout on signal from coddcalc to start scan | Coddcalc calculation module failed to send scan start signal within timeout period | After coddcalc is started, waiting for signal to begin scanning | error |
too many points out of range | Excessive invalid data points from couch sensor | Couch sensor malfunction or transmission error during scan | error |
Too many views out of sequence. Buffer overflow | View buffer overflow due to out-of-sequence views | System receives more out-of-sequence views than buffer capacity | critical |
TST1 | High voltage generator test register 1 status check | System reads TST1 register during fault diagnosis | error |
Unable to activate child task ISVR | Cannot activate ISVR child process | Process activation failure after creation | error |
Unable to activate child task WR00 | System cannot activate the WR00 child task | During CHRD task execution | error |
Unable to activate child task WR00 | Child task WR00 cannot be activated | Task CHRD startup sequence | error |
Unable to activate child task WR01 | Child task WR01 cannot be activated | Task CHRD startup sequence | error |
Unable to activate child task WR01 | System cannot activate the WR01 child task | During CHRD task execution | error |
Unable to activate child task WR02 | Child task WR02 cannot be activated | Task CHRD startup sequence | error |
Unable to activate child task WR02 | System cannot activate the WR02 child task | During CHRD task execution | error |
Unable to activate child task ZARM | Cannot activate ZARM child process | Process activation failure after creation | error |
Unable to allocate calibration memory segment | Failed to allocate memory for calibration parameters | Insufficient available system memory | error |
Unable to allocate memory segment 256 | System cannot allocate memory segment 256 | During memory initialization or allocation request | critical |
Unable to allocate memory segment 257 | System cannot allocate memory segment 257 | During memory initialization or allocation request | critical |
Unable to allocate memory segment 258 | System cannot allocate memory segment 258 | During memory initialization or allocation request | critical |
Unable to allocate memory segment dbl_buff | Memory allocation failed for double buffer segment | System memory exhaustion or allocation error | error |
Unable to allocate memory segment img_hdr | Memory allocation failed for image header segment | System memory exhaustion or allocation error | error |
Unable to allocate memory segment img_size | Memory allocation failed for image size segment | System memory exhaustion or allocation error | error |
Unable to allocate memory segment reg_msg | Memory allocation failed for registry message segment | System memory exhaustion or allocation error | error |
Unable to allocate memory segment "semabuf" | Shared memory segment allocation failure | During initialization of semaphore buffer | error |
Unable to allocate message buffer memory | System cannot allocate memory for message buffers | During message buffer initialization or allocation | critical |
Unable to allocate wtab memory segment | Failed to allocate wtab memory segment | System attempts to allocate wtab memory | error |
Unable to attach to exchange on AP | Failed to attach to message exchange on acquisition processor | System attempts to establish exchange connection to AP | error |
Unable to attach to message exchange ACKW | Cannot connect to ACKW message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange CINX | Cannot connect to CINX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange COLX | Cannot connect to COLX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange DBIX | Cannot connect to DBIX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange DMIX | Cannot connect to DMIX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange GEPV | Cannot connect to GEPV message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange GOCX | Cannot connect to GOCX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange img_chld | Image child process communication attachment failed | During image processing subsystem initialization | error |
Unable to attach to message exchange MULT | Cannot connect to MULT message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange PILX | Cannot connect to PILX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange PRVX | Cannot connect to PRVX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange RESX | Cannot connect to RESX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange RTVX | Cannot connect to RTVX message exchange | Application startup or inter-process communication failure | error |
Unable to attach to message exchange ZCUX | Cannot connect to ZCUX message exchange | Application startup or inter-process communication failure | error |
Unable to create message exchange chrd | System cannot create the chrd message exchange | During CHRD task startup | critical |
Unable to create message exchange chrd | Message exchange for CHRD task cannot be created | Task CHRD startup | critical |
Unable to create message exchange 'CURC' | System initialization failure for core message queue | Application startup phase when establishing inter-process communication | critical |
Unable to create message exchange HZR_ | Cannot create HZR_ message exchange | Message exchange creation failure during initialization | error |
Unable to create message exchange REGX | Cannot create REGX message exchange | Message exchange creation failure during initialization | error |
Unable to create message exchange RMTX | Cannot create RMTX message exchange | Message exchange creation failure during initialization | error |
Unable to create message exchange SVRX | Cannot create SVRX message exchange | Message exchange creation failure during initialization | error |
Unable to create message exchange wr00 | Message exchange for WR00 cannot be created | Child task WR00 initialization | critical |
Unable to create message exchange wr00 | System cannot create the wr00 message exchange | During WR00 task startup | critical |
Unable to create message exchange wr01 | Message exchange for WR01 cannot be created | Child task WR01 initialization | critical |
Unable to create message exchange wr01 | System cannot create the wr01 message exchange | During WR01 task startup | critical |
Unable to create message exchange wr02 | Message exchange for WR02 cannot be created | Child task WR02 initialization | critical |
Unable to create message exchange wr02 | System cannot create the wr02 message exchange | During WR02 task startup | critical |
Unable to create message exchange Xprv | Cannot create Xprv message exchange | Message exchange creation failure during initialization | error |
Unable to free bad views memory segment | Failed to deallocate bad views memory segment | System attempts to free memory after processing bad views | error |
Unable to free calibration memory segment | Failed to release calibration memory segment | Memory management error | error |
Unable to free file parameters memory segment | Failed to deallocate file parameters memory segment | System attempts to free file parameters memory | error |
Unable to free recon parameters memory segment | Failed to release reconstruction parameters memory segment | Memory management error | error |
Unable to free wtab memory segment | Failed to deallocate wtab memory segment | System attempts to free wtab memory during cleanup | error |
Unable to get Regulus message queue XKEY | Cannot retrieve XKEY message queue from Regulus | Message queue retrieval failure | error |
Unable to grab bad views memory segment | Failed to allocate memory segment for bad views tracking | System attempts to allocate bad views memory | error |
Unable to grab file parameters segment | Failed to allocate file parameters memory segment | System attempts to allocate file parameters memory | error |
Unable to grab parameter memory segment | Failed to allocate parameter memory segment | System attempts to allocate memory for parameters | error |
Unable to open device/driver 256 | System cannot access device/driver 256 | Device initialization or access attempt | error |
Unable to open device/driver 257 | System cannot access device/driver 257 | Device initialization or access attempt | error |
Unable to open device/driver 758 | System cannot access device/driver 758 | Device initialization or access attempt | error |
Unable to open device/driver CHANNELS | System cannot access the CHANNELS device driver | Task CHRD initialization or operation | error |
Unable to read from device/driver 256 | Cannot read data from device driver 256 | Data read request to device 256 | error |
Unable to read from device/driver 257 | Cannot read data from device driver 257 | Data read request to device 257 | error |
Unable to read from device/driver 258 | Cannot read data from device driver 258 | Data read request to device 258 | error |
Unable to request message from message exchange chrd | Cannot retrieve message from CHRD message exchange | Task CHRD message handling | error |
Unable to request message from message exchange wr00 | System cannot receive messages from wr00 exchange | During WR00 task message handling | error |
Unable to request message from message exchange wr02 | System cannot receive messages from wr02 exchange | During WR02 task message handling | error |
Unable to request message from message exchange wr0l | Cannot retrieve message from message exchange wr0l | Message request during operation | error |
Unable to send calibration ready message to AP | Failed to send calibration ready notification to AP | System attempts to notify AP that calibration is ready | error |
Unable to send IDSKDONE message to home exchange | Failed to send IDSKDONE message to home exchange | Inter-process communication failure | error |
Unable to send IMAGE_IN message to home exchange | Failed to send IMAGE_IN message to home exchange | Inter-process communication failure | error |
Unable to send message to exchange for OSCNDONE_ACT | Failed to send OSCNDONE_ACT message to message exchange | Inter-process communication failure | error |
Unable to send message to exchange for PROCDONE_ACT | Failed to send PROCDONE_ACT message to message exchange | Inter-process communication failure | error |
Unable to send message to exchange for RAWIN_ACT | Failed to send RAWIN_ACT message to message exchange | Inter-process communication failure | error |
Unable to send message to Regulus queue XKEY | Cannot send message to XKEY Regulus queue | Message send failure to Regulus queue | error |
Unable to send NOMOREVIEWS message to AP | Failed to send NOMOREVIEWS message to acquisition processor | System attempts to notify AP that scan is complete | error |
Unable to send PROCDONE message to home exchange | Failed to send PROCDONE message to home exchange | Inter-process communication failure | error |
Unable to send SAVEMPM message to home exchange | SAVEMPM message transmission failed to home exchange | System attempts to send save data message to home exchange | error |
Unable to send START_PASS_TAG to AP | Failed to send START_PASS_TAG message to acquisition processor | System attempts to initiate pass tag sequence on AP | error |
Unable to spawn child task ISVR | Cannot create ISVR child process | Process creation failure during startup | error |
Unable to spawn child task "lcal" | Child process launch failure for calibration task | During calibration subsystem initialization | error |
Unable to spawn child task WR00 | System cannot spawn the WR00 child task | During CHRD task initialization | error |
Unable to spawn child task WR00 | Child task WR00 cannot be spawned | Task CHRD initialization | error |
Unable to spawn child task WR01 | System cannot spawn the WR01 child task | During CHRD task initialization | error |
Unable to spawn child task WR01 | Child task WR01 cannot be spawned | Task CHRD initialization | error |
Unable to spawn child task WR02 | Child task WR02 cannot be spawned | Task CHRD initialization | error |
Unable to spawn child task WR02 | System cannot spawn the WR02 child task | During CHRD task initialization | error |
Unable to spawn child task ZARM | Cannot create ZARM child process | Process creation failure during startup | error |
Unable to write image data to file | Image data cannot be written to file storage | Memory allocation or file operation failure during image write | error |
Unable to write to device/driver CHANNELS | Cannot write data to CHANNELS device driver | Data transmission attempt to CHANNELS | error |
Un-calibrated protocol | No aircal exists for selected protocol | Attempting to scan with protocol that lacks air calibration | error |
unexpected message interrupt error interrupt bit $x | Unexpected message interrupt received with interrupt bit set | Interrupt signal received in unexpected context | warning |
unexpected $ not enabled (mct1) mess. interrupt error interr | Message interrupt received on disabled MCT1 channel | Interrupt signal on disabled communication channel | error |
unsol. mess. xmit error | Unsolicited message transmission error | Error during unsolicited message transmission | error |
waddr | Unable to release memory segment | Memory deallocation failure | error |
waddr memory | Unable to allocate memory segment waddr | Memory allocation request during startup or operation | critical |
waddr release | Unable to release memory segment waddr | Memory deallocation during shutdown or cleanup | warning |
Warning: NEW FILENAME NOT UNIQUE /usr/IQ/site/CA.AAAAAAAA | System is creating unique filename for calibration data because requested name already exists | Occurs during program execution when a new filename needs to be created | info |
Warning: pin not very well centered, or detector is bad | Centering pin is not well centered or a detector has failed | Center program detects off-center pin position or bad detector affecting measurement | warning |
Wrong state when AP_ABORTDONE received | AP_ABORTDONE received while array processor in unexpected state | Abort done message received out of sequence | error |
Wrong state when AP_DEN_OUT received | Invalid state machine condition for data output message in DSND | AP_DEN_OUT message arrival in DSND task | warning |
Wrong state when AP_DONE_SAVEDATA received | State machine error on data save completion | Data save completion signal received in wrong state | error |
Wrong state when AP_FREE_BUFF received | Invalid state machine condition for buffer free message | AP_FREE_BUFF message arrival in CHN task | warning |
Wrong state when AP_INITDONE received | AP_INITDONE received while array processor in unexpected state | Initialization complete message received out of sequence | error |
Wrong state when AP_READCALI_DONE received | Unexpected state during calibration completion | AP_READCALI_DONE message received in invalid state | error |
Wrong state when AP_READPARMS_DONE received | Unexpected state during parameter read completion signal | AP_READPARMS_DONE tag received | error |
Wrong state when AP_RECONDONE received | AP_RECONDONE received while array processor in unexpected state | Reconstruction done message received out of sequence | error |
Wrong state when AP_RUN_CHAIN received | Unexpected state during chain run request | AP_RUN_CHAIN message received in invalid state | error |
Wrong state when AP_RUN_CHAIN received | Invalid state machine condition for run chain message | AP_RUN_CHAIN message arrival in CHN task | warning |
Wrong state when AP SAVEDATA received | AP task received SAVEDATA message in unexpected state | AP task receives SAVEDATA command while not ready | warning |
Wrong state when APSAVE_TAG receive | APSAVE_TAG received while AP task in unexpected state | AP task receives APSAVE_TAG message during save operation | warning |
Wrong state when APSAVE_TAG receive | SDAT received APSAVE_TAG in invalid state | AP sends APSAVE_TAG while SDAT not ready | warning |
Wrong state when AP_STARTDONE received | AP_STARTDONE received while array processor in unexpected state | Start done message received out of sequence | error |
Wrong state when BP_NOMOREVIEWS_TAG received | BP_NOMOREVIEWS_TAG received while task in unexpected state | Task receives no more views tag during operation | warning |
Wrong state when BP_NOMOREVIEWS_TAG received | SDAT received NOMOREVIEWS in invalid state | BP signals no more reviews available | warning |
Wrong state when BP_NOMOREVIEWS_TAG received | Invalid state for no-more-reviews tag from backplane | DSND receives BP_NOMOREVIEWS_TAG message | warning |
Wrong state when BUFFERREADY received | Invalid state when buffer-ready message received | DSND receives BUFFERREADY notification | warning |
Wrong state when END_TAG received | END_TAG received while task in unexpected state | End tag received out of sequence | error |
Wrong state when INIT_TAG received | INIT_TAG received while task in unexpected state | Initialization message received out of sequence | error |
Wrong state when MPM_NOMOREVIEWS_TAG received | MPM_NOMOREVIEWS_TAG received while task in unexpected state | No more reviews tag received out of sequence | error |
Wrong state when MPM_NOMOREVIEWS_TAG received | Unexpected state during end-of-views message | MPM_NOMOREVIEWS_TAG received in invalid state | error |
Wrong state when MPM_NOMOREVIEWS_TAG received | Invalid state for no-more-reviews tag from MPM | DSND receives MPM_NOMOREVIEWS_TAG message | warning |
Wrong state when MPM_NOMOREVIEWS_TAG received | State machine error on receiving end-of-data tag | MPM signaled no more reviews in unexpected task state | error |
Wrong state when P_PASS_TAG received | P_PASS_TAG received while task in unexpected state | Pass tag received out of sequence | error |
Wrong state when PPLW_CMP_TAG received | State machine error on completion tag reception | Completion tag received in unexpected state | error |
Wrong state when PPLW_CMP_TAG received | PPLW_CMP_TAG received while task in unexpected state | Pipeline complete tag received out of sequence | error |
Wrong state when RDCAL_TAG received | Unexpected state during calibration message receipt | RDCAL_TAG message received in invalid state | error |
Wrong state when START_PASS_TAG received | START_PASS_TAG received while task in unexpected state | Start pass tag received out of sequence | error |
Wrong state when STARTPROC_TAG received | STARTPROC_TAG received while task in unexpected state | Start process message received out of sequence | error |
Wrong state when START_TAG received | START_TAG received while task in unexpected state | Start message received out of sequence | error |
xmit buffer grant error | Transmit buffer grant failed | Buffer grant operation unsuccessful | error |
xmit buffer request error | Transmit buffer request failed | Buffer request operation failure | error |
XOT_ERR | X-ray overtime error | X-ray exposure exceeds safe duration | error |
X-ray control reset | X-ray contactor drops out or system shutdown occurs | Signal brush block misalignment causing communication loss during operation | critical |
XRAYERR | X-ray software error | X-ray control software malfunction | error |
XREQERR | Exposure request error | X-ray exposure request failed or invalid | error |
XSC failures | XSC subsystem failure | XSC error detected in error log | 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.