Canon CXDI NE: troubleshooting and error codes
The ServiceForge knowledge base holds 82 documented symptoms for the Canon CXDI NE, with 94 ranked causes, 102 diagnostic checks with test points and expected values, and 208 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
70C image loss
Images from 70C sensor are lost during capture or transmission to monitor
Ranked causes
- 1. Outdated 70C firmware (common)
- 2. Outdated Cisco AP link firmware (common)
- 3. Wireless channel congestion or interference (occasional)
Verify CXDI NE software version
- Test point
- System software
- Expected
- v1.30.2.3 or higher
6 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC calibration protocol creation radiation
Create or modify AEC calibration protocol when detector is added or protocol deleted from database
Ranked causes
- 1. Detector added without AEC calibration protocol (common)
- 2. AEC calibration protocol deleted from database (occasional)
- 3. Existing AEC calibration protocol requires modification (occasional)
Verify detector is registered and workspace created
- Test point
- Protocol Editor Service Tool
- Expected
- Detector and workspace appear in system
3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: detector QC functions radiation
QC tool provides calibration, performance test and self-diagnosis functions for detector verification
Ranked causes
- 1. Detector requires periodic QC maintenance (common)
- 2. Performance verification needed (common)
- 3. Self-diagnosis verification required (common)
Access QC Tool from CXDI Control Software NE
- Test point
- Tool screen
- Expected
- QC Tool available and responsive
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Firmware update: Ferry type FPD detector
Update firmware or FPGA code for Ferry protocol connected detectors using Ferry Type FPD Maintenance Tool
Ranked causes
- 1. Firmware update required for detector (occasional)
- 2. FPGA configuration update needed (occasional)
- 3. Sensor information file update required (rare)
Enter local IP address of control computer
- Test point
- Local IP Address field
- Expected
- 192.168.100.10
5 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Sensor log collection and analysis
Collect sensor and diagnostic logs using Collection Tool for troubleshooting
Ranked causes
- 1. Diagnostic logs required for troubleshooting (common)
- 2. Database backup required (common)
- 3. QC result data collection needed (occasional)
Start Collection Tool from Service Tool screen
- Test point
- Service Tool menu
- Expected
- Collection Tool option available and clickable
5 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector issued error radiation
Detector reports error condition; operator action required before continuing
Ranked causes
- 1. Detector error condition triggered (unknown)
- 2. Persistent detector error after operation (rare)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Generator disconnected or communication failed radiation
System detects loss of generator connection; QC operations cannot proceed
Ranked causes
- 1. Generator communication failure during QC initiation (common)
- 2. Generator condition settings failed (occasional)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
70C communication failures
Communication errors between detector and system with 70C sensor
Ranked causes
- 1. Software incompatibility with 70C sensor (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
70C images lost radiation
X-ray images from 70C sensor are not captured or saved
Ranked causes
- 1. Software issue in CXDI NE with 70C sensor (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
70C sensor disconnection
Sensor connection is lost or becomes intermittent during operation
Ranked causes
- 1. Wireless communication failure due to firmware or channel issues (common)
Collect system event logs for analysis
- Test point
- Windows System and Application logs
- Expected
- Log files collected without errors
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Blank images displayed on CXDI NE system patient safety
Windows Aero themes enabled causing blank images in digital radiography systems
Ranked causes
- 1. Windows Aero themes enabled in system configuration (common)
Verify Windows Aero themes status in system settings
- Test point
- Personalize menu, Theme selection
- Expected
- Theme set to Basic or High Contrast (not Aero)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration data invalid or out of date radiation
Stored calibration data is incorrect or expired; system rejects compensation
Ranked causes
- 1. Calibration data not correct or stale (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration data not available at startup radiation
Error displayed when control software starts up without prior calibration; system enters QC-tool-only mode, preventing normal operation.
Ranked causes
- 1. Detector calibration not yet performed (common)
Verify calibration has been performed since system installation
- Test point
- Control software startup status
- Expected
- System enters normal operation mode, not QC-tool-only mode
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration data upload failed radiation
SPCC data upload error during QC Tool operation; system restart required
Ranked causes
- 1. Ferry communication or power connection error during upload (occasional)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC calibration protocol creation and modification radiation
Creating or modifying AEC calibration protocols after detector addition or protocol deletion; configuring image processing parameters for AEC calibration
Ranked causes
- 1. AEC Calibration Protocol needs creation or modification (common)
For Case 1: Verify detector and workspace created
- Test point
- Service Tool - Protocol Editor
- Expected
- Detector registered, workspace visible in AEC Calibration Protocol
3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC image processing parameters adjustment radiation
Adjust image processing parameters after AEC calibration protocol creation
Ranked causes
- 1. Image processing parameters require update for AEC calibration (common)
Identify current image processing parameters
- Test point
- Protocol workspace image processing configuration
- Expected
- Before change state documented in section 5.1.3
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC phototimer adjustment radiation
Setting up AEC phototimer to achieve target EI (exposure indicator) values across different kV settings and acrylics thickness for various imaging units
Ranked causes
- 1. AEC calibration procedure required during installation/setup (common)
Prepare acrylics sheets for exposure
- Test point
- calibration setup
- Expected
- 5cm, 10cm, 20cm thickness sheets ready
7 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC protocol deletion after adjustment patient safety
Removal and hiding of AEC calibration protocols from operator interface after service engineer completes phototimer adjustment, to prevent accidental use by general operators.
Ranked causes
- 1. AEC protocols must be hidden to prevent operator misuse after adjustment (common)
Access Protocol Editor from System Settings
- Test point
- System button > Protocol Editor button
- Expected
- Protocol Editor screen displays with tray containing AEC protocols
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: AEC protocol setup and activation radiation
Selecting and starting the AEC Calibration protocol through the system interface
Ranked causes
- 1. AEC Calibration protocol must be activated for phototimer adjustment (common)
Open Utility Protocol category
- Test point
- system interface
- Expected
- Utility Protocol category visible and expandable
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Detector correction data creation radiation
Procedure to create detector correction data and establish system calibration baseline; required during installation and annually.
Ranked causes
- 1. Periodic calibration maintenance requirement (common)
Establish calibration mode and select target detector
- Test point
- QC tool detector list
- Expected
- Detector appears in list and is selectable
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Input data transformation using regular expressions
Configure pattern matching and replacement rules for input calibration using regular expressions in the service tool
Ranked causes
- 1. Need to apply regex pattern replacement to input fields (common)
Verify pattern field is set when input calibration function is ON
- Test point
- Service tool input calibration settings
- Expected
- Pattern must be defined; if not set, no processing occurs
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Input data transformation using Script with character limit overflow
Handle character limit exceeding during Script processing and determine appropriate operation
Ranked causes
- 1. Processed output exceeds character limit after Script execution (occasional)
Monitor output character count during Script execution
- Test point
- Script processing output
- Expected
- Output within default character limit
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Input data transformation using VBScript
Configure input calibration using VBScript for magnetic card input and medical examination automation pack NE/Studix optional product
Ranked causes
- 1. Need to apply script-based transformation to input data (common)
Verify Script is enabled and VBScript file is specified
- Test point
- Service tool Script setting and Script file name
- Expected
- Script setting ON; valid VBScript file path specified
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Input data using regular expressions
Configure input calibration for magnetic card input and medical examination automation pack NE to transform patient data (Accession Number, Patient Name variants, Patient ID, Patient Sex) using regular expression patterns.
Ranked causes
- 1. Setup of regular expression patterns for data transformation (common)
Verify Input Correction setting is enabled
- Test point
- Input calibration setting screen
- Expected
- Input Correction = ON
2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Input data using VBScript
Configure input calibration for magnetic card input and medical examination automation pack NE/Studix using VBScript to transform patient data with cross-item referencing capability.
Ranked causes
- 1. Setup of VBScript for data transformation with inter-item referencing (common)
Verify Script setting is enabled
- Test point
- Service tool Studix setting screen
- Expected
- Script = ON
3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Performance test execution radiation
Procedure to verify detector maintenance and control through performance testing; recommended annually.
Ranked causes
- 1. Periodic performance verification requirement (common)
Adjust X-ray generator settings based on previous calibration
- Test point
- X-ray generator parameter configuration
- Expected
- Settings match values from Exposure Memo of previous calibration
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Phototimer (AEC) adjustment radiation
Automatic Exposure Control optimization to minimize patient dose while maintaining diagnostic image quality. Performed during installation using AEC calibration protocols with Exposure Index (EI) measurement.
Ranked causes
- 1. Phototimer requires spectral sensitivity adjustment across kV settings (common)
Start CCS and perform calibration
- Test point
- CCS system
- Expected
- System ready for AEC adjustment
6 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Remove AEC Calibration protocol after completion
Deleting AEC Calibration protocol and hiding Utility Protocol tab after all adjustments are completed
Ranked causes
- 1. AEC Calibration protocol must be removed after adjustment to prevent accidental activation by users (common)
Enter system settings screen
- Test point
- system interface
- Expected
- System Settings Screen displayed
4 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
CCRHIS library error
Error occurred in CCRHIS library processing. May be due to incorrect settings, file I/O error or other problems.
Ranked causes
- 1. Studix processing failed due to incorrect settings or file I/O error (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Collection Tool startup when Service Tool is active
Collection Tool cannot run while Service Tool is operating; unsaved settings prompt appears.
Ranked causes
- 1. Service Tool has unsaved data being edited (common)
Observe dialog box when Collection Tool is invoked
- Test point
- Service Tool main window
- Expected
- Confirmation dialog appears asking to save settings
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Collection Tool startup with unsaved data
Settings save confirmation dialog appears if Collection Tool is started while data is being edited in Service Tool
Ranked causes
- 1. Service Tool has unsaved edits (occasional)
Check for settings save dialog on Collection Tool startup
- Test point
- Service Tool screen during Collection Tool initialization
- Expected
- Settings save confirmation dialog appears if edits pending
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Communication failures with 70C sensor radiation
Communication errors or dropped connections between detector and system
Ranked causes
- 1. Software incompatibility in CXDI NE with 70C sensor (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Cooling unit attached or detached during study
Processing halted due to cooling unit operation during active acquisition
Ranked causes
- 1. Cooling unit operated during study (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector analog power supply abnormality high voltage
Abnormality detected in the analog power supply for the detector.
Ranked causes
- 1. Analog power supply abnormality in detector (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector battery depleted or insufficient charge
Detector battery charge is critically low; imaging operations halted
Ranked causes
- 1. Battery charge insufficient (common)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector calibration data check failed radiation
SPCC data validation failed; possible detector abnormality or power supply issue
Ranked causes
- 1. Detector power supply off or cable disconnected (common)
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector characteristics compensation data invalid radiation
System encounters illegal detector calibration compensation data; internal processing error
Ranked causes
- 1. Corrupted or incorrect detector compensation data (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector communication error
Detector communication error occurred. Cable may be disconnected or power discontinuity detected.
Ranked causes
- 1. Ethernet interface communication error (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector communication error fatal
Fatal detector communication error. System restart required. cxdcap.ini file not installed.
Ranked causes
- 1. cxdcap.ini file not installed (rare)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector control line connection error caution
Control line connection error detected in detector. Broken cable between detector and power box may be involved.
Ranked causes
- 1. Control wire error or broken cable between detector and power box (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector control wire cable length mismatch caution
Discrepancy between cable length settings for detector-to-power box connection and XRAY board cable.
Ranked causes
- 1. Cable length settings discrepancy between detector cable and XRAY board cable (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector hardware error occurred radiation
Internal detector malfunction; system restart required
Ranked causes
- 1. Detector internal error (rare)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector internal temperature approaching upper limit caution
Internal temperature of detector is close to upper limit. Do not leave detector in Ready condition.
Ranked causes
- 1. Detector temperature approaching upper limit (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector internal temperature exceeds upper limit
Detector temperature warning; continues operation but at elevated risk
Ranked causes
- 1. High ambient temperature or insufficient detector cooling (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector issued fatal error radiation
Detector reports fatal error condition; system restart required
Ranked causes
- 1. Detector fatal error condition triggered (rare)
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector issued warning radiation
Detector reports non-critical warning condition; operation may continue
Ranked causes
- 1. Detector warning condition triggered (unknown)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector serial number discrepancy caution
Discrepancy between serial number of detector and DP number detected.
Ranked causes
- 1. Serial number discrepancy between detector and DP (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector structure abnormality detected caution
Abnormality detected in detector structure. Illegal value written for serial number.
Ranked causes
- 1. Illegal value written for detector serial number (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Detector temperature critically high
Detector internal temperature exceeds safe operating limit; processing halted
Ranked causes
- 1. Abnormally high detector temperature (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Drive circuit error caution
PLD error detected by detector AD board. System cannot proceed.
Ranked causes
- 1. PLD error detected by detector AD board (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Drive circuit PLD config error caution
PLD Config error detected by detector AD board. System cannot proceed.
Ranked causes
- 1. PLD Config error detected by detector AD board (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Entered information has invalid value patient safety
Exam information containing illegal values for items other than key items was acquired. Invalid values are replaced with blanks.
Ranked causes
- 1. Exam information with illegal values for non-key items from Studix (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error code E040100054
System is receiving E040100054 error code indicating communication or image loss issue
Ranked causes
- 1. Combination of outdated firmware and wireless interference (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Extra defect correction file not loaded
System fails to load the extra defect correction file required for imaging. Error occurs during system operation.
Ranked causes
- 1. Extra defect correction file does not exist (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Firmware backup area management caution
Understand double firmware architecture for safe updates
Ranked causes
- 1. Understand backup firmware protection (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Firmware update: IP address configuration
Change IP addresses for Ethernet-connected detectors using Ferry Type FPD Maintenance Tool
Ranked causes
- 1. IP address change required for detector network configuration (occasional)
Confirm detector supports Ethernet connection
- Test point
- Detector model type
- Expected
- CXDI-40EG, 40EC, 40G Compact, 50G, 50C, 55G, 55C, 60G, 60C, CXDI-401G/C or CXDI-401G/C Compact
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Firmware version mismatch
Firmware version differs from expected. Wrong detector firmware may have been written.
Ranked causes
- 1. Wrong detector firmware written (rare)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Flash ROM erase error
Flash ROM error detected in detector. Flash ROM erase error occurred.
Ranked causes
- 1. Flash ROM erase error detected by detector AD board (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Flash ROM ID error
Flash ROM error detected in detector. Flash ROM ID error occurred.
Ranked causes
- 1. Flash ROM ID error detected by detector AD board (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Flash ROM write error
Flash ROM error detected in detector. Flash ROM write error occurred.
Ranked causes
- 1. Flash ROM write error detected by detector AD board (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
More symptoms
- Generator initialization communication failed
- Gray pixel values displayed in image
- Grid error at detector
- Grid error may have caused image abnormality
- Grid ID loading error
- Image data transfer failed
- Image data transfer stopped
- Image rotation not applied to output
- Invalid detector specified in system settings
- Invalid studies acquired
- Invalid workspace specified in system settings
- Memory allocation failed
- No battery attached to detector
- Periodic noise detected in acquisition data
- Phototimer adjustment: AEC calibration setup
- Self-diagnosis: Detector and power box system test
- Specified ID not found in examination file
- System setting: Enable EI (Exposure Indicator) display annotation
- Undefined detector error file download
- Undefined detector error hex format
- Verify AEC Calibration Protocol configuration
- Workspace creation required before calibration
22 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
020201003 | Detector battery charge dropped below 8% | Detector battery remaining charge falls below 8% of full charge | error |
020201004 | Gamma adjustment unavailable due to pattern file loading failure | All pattern files for simplified gamma adjustments failed to load | error |
020201004 | Unexpected error occurred. Gamma adjustment is not available. | All loading of pattern files used for simplified gamma adjustments has failed. | error |
020201005 | Failed to connect to the barcode reader | Exception occurred in barcode reader connection initialization process | error |
020201005 | Barcode reader connection failed | Exception during barcode reader connection initialization | error |
020201006 | Cannot start specified examination. | Examination specified during Studix operation when specification using ccrhis.dvr file is ignored, or patient specified during magnetic card operation when specification is ignored. | error |
020201007 | Detector communication error during exposure | Reception timeout from detector or detector power-off during exposure | error |
020201008 | Detector temperature reached dangerous levels | Detector temperature reached dangerously high level triggering Sleep status | error |
020201008 | The detector temperature has reached dangerous levels. Images cannot be captured until temperature has dropped. | Detector temperature reached dangerously high level, establishing Sleep status. | error |
020201009 | Failed to start up the OverwrapSoftware | Startup failed due to invalid path of overlapping software set by service tool | error |
020201009 | OverwrapSoftware startup failed | Startup failed due to invalid overlapping software path configuration | error |
020202001 | Detector temperature reached warning level | Detector temperature notification from Ferry indicates warning level reached | warning |
020202002 | Detector temperature reached dangerous level (warning state) | Ferry notification that detector temperature reached dangerous level | warning |
020202003 | The detector is not available. Irradiation has finished. | Notification received that detector became invalid during irradiation. | warning |
020202004 | The detector battery is weakening. Charge the detector battery. | Remaining charge of detector battery dropped below 4% of full charge. | warning |
020202005 | Specified disk space could not be cleaned up | Space greater than examination to be deleted was specified | warning |
030100001 | No calibration data available | Workspace calibration has not been completed | error |
030100005 | Required COM+ servers not installed | One or more necessary COM+ servers not installed during system startup | critical |
030201001 | Detector communication error occurred | Acquisition of detector information from capture manager failed when inspection started | error |
030201002 | Periodic noise detected in acquisition data | Grid-embedded detector calibration performed with grid in place | error |
030201003 | Cooling unit operation during study | Cooling unit attached or detached during active acquisition | error |
030201003 | The cooling unit has been attached or detached. Processing was halted. | Cooling unit was operated (attached or detached) during the study. | error |
030201004 | Calibration data (SPCC) check failed | QCT completion returns error on SPCC data validation | error |
030201005 | Generator disconnected | Generator disconnection event occurred | error |
030201006 | Generator is disconnected (communication failure) | Generator communication failure during calibration, performance test, or self-diagnosis initiation | error |
030201007 | Generator is disconnected (condition setting failure) | Generator condition setting fails during calibration, performance test, or self-diagnosis | error |
030201007 | Imaging preparation failed | Setting of conditions in generator or detector failed | error |
030201008 | Detector battery charge insufficient | Detector battery remaining charge is deficient | error |
030201008 | Detector cannot be used because the battery has lost its charge. Processing was halted. | Remaining charge of detector battery dropped to deficient level. | error |
030201009 | The detector temperature has reached dangerous levels. Processing was halted. | Notification received from detector of abnormally high temperature. | error |
030201009 | Detector temperature reached dangerous level during QC | Detector notification of abnormally high temperature | error |
030201010 | No battery is attached to the detector. Attach the battery. | Battery has not been installed with a wired connection. | error |
03020200E | Memory allocation failed | Insufficient system RAM when QC Tool starts or examination begins | critical |
03020201B | Calibration data upload failed | Error during SPCC data upload operation in QC Tool | critical |
03020201C | Image data transfer failed | Error during automatic image transfer from detector to system | critical |
03020201F | Detector error occurred | Internal detector error indication during operation | critical |
030203003 | Detector internal temperature exceeds upper limit | Detector temperature reaches warning threshold | warning |
03020FFFF | An internal error occurred | Both X-ray exposure and exposure cancel occur at the same time, or software bug | critical |
040100001 | Invalid workspace has been specified | Attempt to use unregistered workspace configuration | error |
040100008 | Invalid detector has been specified | Attempt to use unregistered detector configuration | error |
040100023 | Generator communication failed | Generator initialization communication error at system setup | error |
040100041 | Internal error - illegal detector compensation data | Detector characteristics compensation data is illegal during image processing | error |
040100042 | Internal error - illegal detector compensation data | Detector characteristics compensation data is illegal during operation | error |
040100045 | Calibration data is invalid | Calibration data is not correct or corrupted | warning |
040100052 | Detector issued a warning | Warning notification from detector occurred | warning |
040100053 | Detector issued an error | Error condition reported by detector during operation | error |
040100054 | Detector issued a fatal error | Fatal error condition reported by detector during operation | critical |
040100056 | Generator disconnected | Retry button canceled during X-ray generator imaging condition setup failure | error |
040300000 | Detector has not been started up | Selected detector not attached or detector power supply issue | error |
040300002 | Internal error occurred | Selected detector not attached or hardware malfunction | error |
040400003 | Failed to acquire system settings | Database data defective, insufficient table records | critical |
040500003 | Exceeded maximum number of study order acquisitions | C-FIND-RSP study exceeds maximum configured acquisitions | error |
040500004 | Received some invalid studies | Data contravening the DICOM rules are contained in C-FIND-RSP received | error |
040500005 | Received tag contains invalid value; value replaced by null | Data contravening DICOM rules in C-FIND-RSP received | error |
040500006 | Unsupported character set received | Characters not in received character set present; auxiliary kanjis or decoding failure | error |
040500006 | Characters not in received character set present, may not display correctly | Characters cannot be decoded properly or auxiliary kanjis received from RIS | error |
040500007 | Characters do not match current character code; automatic correction applied | Japanese-language data received despite English (ASCII) character set configured | warning |
040500007 | Character code mismatch | Data received with character code different from service tool setting | warning |
040500008 | Date entry before 1753 included in acquired Exam | Date type (DA) data prior to January 1, 1753 received from RIS | error |
040500009 | Failed to copy tag to C-STORE | DICOM rule violation in data during tag copy process from C-FIND to C-STORE; non-existent or invalid tag specified | warning |
04050000A | Failed to copy tag to DicomFile | Violation of DICOM rules when copying tags from C-FIND to DicomFile, or non-existent tag specified | warning |
04050000C | Failed to load DICOMDIR | DICOMDIR file loading failure due to damage or corruption | error |
04050000D | Output error occurred | Output information unavailable after system restart due to power discontinuity | error |
040501011 | Cannot continue processing; file already exists at storage destination | File with same name exists at configured save destination | error |
040501012 | Cannot continue processing; access to storage destination denied | Save destination folder cannot be accessed; insufficient user permissions | error |
040501013 | Insufficient storage space | Not enough space at specified storage destination | error |
040501013 | Cannot continue processing; insufficient space at storage destination | Not enough disk space available at configured save destination | error |
040501014 | DICOM GSPS output halted; object image transfer incomplete | C-STORE processing of GSPS executed while C-STORE of target images failed or incomplete | error |
040501016 | Network communication cut off during file output | Network problem or interruption during media storage over network | error |
040501017 | Unsupported DICOMDIR loaded | DICOMDIR file not created by CXDI NE/RF loaded | error |
040501018 | Output error occurred during version upgrade | Version upgrade from pre-V1.30 performed while media storage queue exists | error |
040502002 | Association negotiation failed | Permanent rejection by service provider (ACSE-related function) with no reason | error |
040502003 | Association negotiation failed - unsupported abstract syntax | Service provider rejected unsupported abstract syntax sent | error |
040502004 | Association negotiation failed - unsupported forward syntax | Service provider rejected unsupported forward syntax | error |
04050200D | Association negotiation failed - ACSE rejection without reason | Permanent rejection by service provider (ACSE-related function) | error |
04050200E | Association negotiation failed - unsupported protocol version | Protocol version not supported by service provider | error |
04050200F | Association negotiation failed - temporary service rejection | Temporary rejection by service provider (ACSE-related function) | warning |
040502010 | Association negotiation failed - temporary protocol version rejection | Temporary rejection due to unsupported protocol version | warning |
040502011 | Association negotiation failed - temporary congestion | Permanent rejection by service provider (presentation-related) due to temporary congestion | warning |
040502012 | Association negotiation failed - local restrictions exceeded | ASSOCIATE-RJ received with RESULT=1, SOURCE=3, REASON=2 during negotiation | error |
040502013 | Association negotiation failed - presentation temporary congestion | Temporary rejection by service provider (presentation-related) due to congestion | warning |
040502014 | Association negotiation failed - presentation restrictions exceeded | Temporary rejection by service provider (presentation-related) - local restrictions exceeded | warning |
04050201B | Association stopped - aborted by service provider | Association aborted by service provider without reason | warning |
04050201C | Association stopped - PDU not recognized | Association aborted because service provider cannot recognize PDU | error |
04050201D | Association stopped - unexpected PDU received | Association aborted due to unexpected PDU from service provider | error |
04050201E | Association stopped - PDU parameters not recognized | Association aborted because PDU parameters cannot be recognized | error |
04050201F | Association stopped - unexpected PDU parameters | Association aborted due to unexpected PDU parameters | error |
040502020 | Association stopped - invalid PDU parameter value | Association aborted due to invalid PDU parameter value | error |
040502021 | Association negotiation failed - timeout on readout standby | No response from communication partner within readout standby timeout period | warning |
040502023 | Association negotiation failed - RELEASE-RQ received out of sequence | RELEASE-RQ received at time other than association release phase | error |
040502058 | Association negotiation failed - invalid IP or port | Association initiated with no valid communication partner IP address and port | error |
040505001 | DICOM communication error - unsupported attribute tag | Status tag (0000,0900) value error received; non-existent attribute set | error |
040505002 | DICOM communication error - invalid attribute value | Status tag (0000,0900) value error; invalid attribute value set | error |
040505003 | DICOM communication warning due to attribute list error | Status tag (0000,0900) value error with attribute list problem | warning |
040505004 | DICOM communication error, status tag (0000,0900) value error | Processing failed | error |
040505005 | DICOM communication error - multiple SOP instances | Status tag (0000,0900) value error; multiple SOP instances present | error |
040505006 | DICOM communication error - non-existent object instance | Status tag (0000,0900) value error; non-existent object instance set | error |
040505007 | DICOM communication error - non-existent event type | Status tag (0000,0900) value error with non-existent event type set | error |
040505008 | DICOM communication error - non-existent argument | Status tag (0000,0900) value error with non-existent argument set | error |
040505009 | DICOM communication error due to invalid argument in status tag (0000,0900) | Status tag (0000,0900) value error received with invalid argument set | error |
04050500A | DICOM communication warning - attribute value out of range | Status tag (0000,0900) value error with attribute value outside range | warning |
04050500B | DICOM communication error due to invalid object instance in status tag | Status tag (0000,0900) value error with invalid object instance set | error |
04050500C | DICOM communication error - non-existent SOP class | Status tag (0000,0900) value error with non-existent SOP class set | error |
04050500D | DICOM communication error - class instance contradiction | Status tag (0000,0900) value error with contradiction in class instance | error |
04050500E | DICOM communication error due to missing attribute in status tag | Status tag (0000,0900) value error with missing attribute | error |
04050500F | DICOM communication error due to missing attribute value | Status tag (0000,0900) value error with missing attribute value set | error |
040505010 | DICOM communication error - non-supported SOP class | Status tag (0000,0900) value error with non-supported SOP class set | error |
040505011 | DICOM communication error due to non-existent action type | Status tag (0000,0900) value error with non-existent action type | error |
040505012 | DICOM communication error due to repeated startup | Status tag (0000,0900) value error with repeated startup condition | error |
040505013 | DICOM communication error - unrecognized operation | Status tag (0000,0900) value error with unrecognized operation | error |
040505014 | DICOM communication error due to erroneous input argument | Status tag (0000,0900) value error with incorrectly input argument | error |
040505015 | DICOM communication error due to resource restriction | Status tag (0000,0900) value error with resource limitation | error |
040505017 | DICOM communication error - ununderstandable setting | Status tag (0000,0900) value error with unintelligible setting | error |
040505018 | DICOM communication error due to insufficient resources | Status tag (0000,0900) value error with insufficient resources | error |
04050501B | DICOM C-FIND error due to identifier/SOP class mismatch | C-FIND status tag (0000,0900) value error with identifier mismatch | error |
04050501C | DICOM C-STORE warning - data factor coercion | Status tag (0000,0900) value error in C-STORE with data coercion | warning |
04050501D | DICOM C-STORE warning - factor abandoned | Status tag (0000,0900) value error in C-STORE where factor was dropped | warning |
04050501E | DICOM C-STORE warning - dataset/SOP class mismatch | Status tag (0000,0900) value error in C-STORE where dataset does not match SOP | warning |
04050501F | DICOM C-STORE error due to dataset/SOP class mismatch | C-STORE status tag (0000,0900) value error with dataset mismatch | error |
040505020 | DICOM C-STORE error due to no resources at destination | C-STORE status tag (0000,0900) value error with no resources | error |
040505027 | DICOM printer output error due to missing film box SOP instances | N-ACTION status tag (0000,0900) error with BasicFilmSession class | error |
040505028 | DICOM printer output error due to full print queue | N-ACTION status tag (0000,0900) error; print queue full | error |
040505029 | DICOM printer output error due to image size exceeding image box size | N-ACTION status tag (0000,0900) error with oversized image | error |
04050502A | DICOM printer output error due to linked print image exceeding box size | N-ACTION status tag (0000,0900) error with linked image too large | error |
04050502C | DICOM printer output N-ACTION error; print queue is full for BasicFilmBox | N-ACTION status tag (0000,0900) value error when SOP class was BasicFilmBox | error |
04050502E | DICOM printer error due to unprinted film box and unsupported film session operation | N-CREATE status tag (0000,0900) error with BasicFilmSession class | error |
04050502F | DICOM printer output N-SET error; insufficient printer memory for images | N-SET status tag (0000,0900) value error when SOP class was GrayScaleImageBox | error |
040505030 | DICOM printer output warning; printer status is WARNING | Printer status tag (2110,0010) value of N-GET during Printer operation is WARNING | warning |
040506001 | DICOM printer output halted due to printer failure status | Printer status tag (2110,0010) N-GET received with FAILURE status | error |
040507001 | DICOM StorageCommitment failed with reason code 0x0110 | N-EVENT-REPORT failure with reason (0008,1197) = 0x0110 | error |
040507002 | DICOM StorageCommitment failed with reason code 0x0112 | N-EVENT-REPORT failure with reason (0008,1197) = 0x0112 | error |
040507003 | DICOM StorageCommitment failed with reason code 0x0119 | N-EVENT-REPORT failure with reason (0008,1197) = 0x0119 | error |
040507004 | DICOM StorageCommitment failed with reason code 0x0122 | N-EVENT-REPORT failure with reason (0008,1197) = 0x0122 | error |
040507005 | DICOM StorageCommitment failed with reason code 0x0131 | N-EVENT-REPORT failure with reason (0008,1197) = 0x0131 | error |
040507006 | DICOM StorageCommitment failed with undefined reason code | N-EVENT-REPORT failure with non-DICOM-defined reason (0008,1197) | error |
040507007 | DICOM StorageCommitment failed with undefined reason code | N-EVENT-REPORT failure with non-DICOM-defined reason (0008,1197) | error |
040600008 | Disc access failed | Disk could not be accessed during media storage free space check | error |
040600008 | Disk access failed during media storage free space check | Disk could not be accessed during free space check at time of media storage | error |
040600009 | Insufficient free disk space during process | Free space check at media storage shows insufficient space | error |
04060000B | Process error prevents retry | Power discontinuity, software bug, or image processing failure | error |
04060000B | Retry failed due to error during media output processing | Power discontinuity or software bug; ID key did not exist or image processing failed | error |
04060000C | Old study info cannot execute; created before rebinding | System attempting transfer of old study from pre-rebinding | error |
040700006 | Failed to load image file; file does not exist | Attempt to load non-existent image file | error |
040700100 | System memory settings invalid; exceeds installed memory | Service tool specifies memory size larger than installed RAM | critical |
040700100 | System memory settings are invalid; exceeds installed capacity | Service tool specified memory size larger than installed memory | critical |
040800100 | Examination cannot be started due to non-existent protocol | Protocol contained in pending examination has been deleted from database | error |
040D0001F | Providing free space on the hard disk failed | System unable to delete data equivalent to prescribed number of records | error |
040E01000 | Image analysis processing failed | Image analysis processing routine failed during execution | error |
040E01001 | Failed to load extra defect correction file | Extra defect correction file does not exist or is missing | error |
041000004 | Invalid studies are acquired | Exam information containing illegal values for key items (ACC#, patient ID, patient name) acquired from Studix | error |
041000005 | Entered information has invalid value | Exam information containing illegal values for non-key items acquired from Studix | error |
041000006 | Specified ID is not found in the examination file | Exam information with specified key values did not exist in examination file | error |
041000008 | An error has occurred during script-based input calibration | Script compilation error, script processing error, script standard error output, or script return value other than 0 | error |
041000010 | An error has occurred in CCRHIS library | Studix processing failed due to incorrect settings, file I/O error or other problem | error |
041000011 | Workflow library version is not supported | Version of CCS does not match automatic examination pack version | error |
041000012 | Error occurred in CCRHIS library | Studix, Workflow, or magnetic card processing failed due to invalid setting or file I/O error | error |
041000020 | Examination file loading halted due to maximum reserved exams exceeded | Maximum number of reserved exams registered to database exceeded | error |
041000021 | Invalid studies loaded and cannot be displayed | Invalid value detected in required items of exam information | error |
041000022 | Entered information has invalid value in user-specified items | Invalid value detected in user-specified values | error |
041000023 | Failed to read examination file | Exam file not found at specified location | error |
041000024 | Error occurred during automatic examination file updating | Error during exam file monitoring with automatic update configuration | error |
041000025 | Failed to read examination file during loading | Error occurred during loading of exam file | error |
041100004 | CxdiInfo startup failed | Specified DLL does not exist or lacks expected interface | error |
050501002 | A flash ROM error was detected in the detector | Flash ROM ID error detected by detector AD board | warning |
050501003 | A flash ROM error was detected in the detector | Flash ROM Write error detected by detector AD board | warning |
050501004 | A flash ROM error was detected in the detector | Flash ROM Erase error detected by detector AD board | warning |
050501005 | There may be problem in the images because of a grid error | Grid warning detected by detector AD board but imaging continued | warning |
050501005 | Grid error may have caused image abnormality | Grid warning detected during imaging | warning |
050501006 | Detector internal temperature exceeds upper limit | Detector internal temperature exceeds safety threshold | error |
050501007 | The internal temperature of the detector is nearing its upper limit | Detector internal temperature approaching upper limit | warning |
050501008 | A drive circuit error occurred | PLD error detected by detector AD board | error |
050501009 | A drive circuit error occurred | PLD Config error detected by detector AD board | error |
05050100A | An abnormality was detected in the detector structure | Illegal value written for detector serial number | error |
05050100B | An abnormality was detected in the detector structure | Discrepancy between detector serial number and DP number | error |
05050100B | Detector serial number discrepancy | Mismatch between detector serial number and DP number | error |
05050100C | A control line connection error was detected in the detector | Control wire error detected by detector AD board; broken cable between detector and power box | error |
05050100D | A control line connection error was detected in the detector | Control wire error detected by detector AD board; cable length mismatch between detector-power box and XRAY board | error |
05050100D | Control wire cable length mismatch | Cable length settings mismatch between detector and XRAY board | error |
05050100E | Undefined detector error hex format | Hex format error during firmware or PLD download | warning |
05050100E | An error was detected by the detector | Undefined error detected by detector AD board; Hex format error during firmware or PLD download | warning |
05050100F | An error was detected by the detector | Undefined error detected by detector AD board; Hex format error during firmware, PLD or DP file download | warning |
05050100F | Undefined detector error file download | Hex format error during firmware, PLD, or DP file download | warning |
050501010 | Image data transfer failed | DMA timeout in PCB-Di during reduced-size image read | error |
050501010 | Failed to transfer the image data | DMA inside PCB-Di timed out when reduced-size images were read | error |
050501011 | The transfer of the image data was stopped | Transfer of Full image data was aborted | warning |
050501012 | An abnormality was detected in the analog power supply for the detector | Abnormality detected in detector analog power supply | error |
050501013 | A grid ID loading error was detected | Grid ID loading error detected | warning |
050501014 | A grid error was detected | Grid error detected at the detector AD board | error |
050501015 | A grid error may have caused an image abnormality | Grid warning detected by detector AD board but imaging continued | warning |
050501016 | The firmware is different | Wrong detector files written during firmware writing | error |
050502009 | A detector communication error has occurred | cxdcap.ini file has not been installed | critical |
050502026 | A detector communication error occurred | Communication error detected by Ethernet interface; cable disconnected; detector power discontinuity | error |
E040100054 | 70C sensor communication failure or image loss error | Loss of communication between 70C sensor and system or failure to complete image transmission | error |
E040500005 | MWL DICOM violation error | Illegal DICOM data received from MWL | error |
E040500006 | MWL DICOM violation error | Illegal DICOM data received from MWL | error |
E040500008 | MWL DICOM violation error | Illegal DICOM data received from MWL | error |
E040501010 | System error from exceeded SQL Server database size limit | Diskstore database exceeds 4GB capacity when more than 1000 studies stored continuously on large-capacity media without shutdown | critical |
ERROR | Error condition requiring user action; imaging can continue once remedied | System enters error state | error |
ERROR | Error level system error affecting operation | Error condition occurs during system operation | error |
FATAL | Fatal condition requiring service call; imaging cannot be continued | System enters fatal error state | critical |
FATAL | Fatal level system error that prevents normal operation | Occurs during any operational state; error dialog appears automatically | critical |
Pattern Match Error | Error occurred while applying regular expression replacement | Regular expression processing fails on one or more items during input calibration | warning |
Script compilation error | Syntax or compilation error detected in VBScript code | Invalid VBScript syntax when Script execution begins | error |
Script Error | Error occurred during VBScript execution | VBScript execution fails, compilation error, or error in return value | error |
Script return value error | Script return value is invalid or unexpected type | Script completes but return value does not match expected type | error |
Standard error output in Script | Standard error message generated within Script execution | Script encounters runtime error and outputs to stderr | warning |
WARNING | Warning condition; no immediate user action required | System enters warning state | warning |
WARNING | Warning level non-critical system alert | Warning condition detected during system check or operation | warning |
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.