Fujifilm FCR: troubleshooting and error codes
The ServiceForge knowledge base holds 24 documented symptoms for the Fujifilm FCR, with 27 ranked causes, 60 diagnostic checks with test points and expected values, and 539 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
QA-WS application installation fails or does not start
Installation errors occur or application fails to launch after installation, possibly with key registry errors on startup.
Ranked causes
- 1. Key registry not installed during initial setup (common)
- 2. Incorrect password entered during QA-WS installation (occasional)
- 3. DICOM key installed without reinstalling AP key (occasional)
Verify key registry installation
- Test point
- Application startup screen
- Expected
- Application launches without key registry error message
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
QA-WS application not fully functional after installation
Application installed but DICOM or image functions unavailable or restricted.
Ranked causes
- 1. US image parameters not loaded for English AP (USA) (occasional)
- 2. DICOM Storage or Print Service not enabled (occasional)
Verify correct language and region variant of QA-WS installed
- Test point
- Application About or Help menu
- Expected
- English AP (USA) if US parameters required, or appropriate regional version
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: CRT monitor artifact 1 (ringing, jitter, swimming, tailing)
Verify absence of visual artifacts including ringing, jitter, swimming, and tailing
Ranked causes
- 1. Artifact 1 verification procedure (unknown)
Display Artifact 1 test pattern
- Test point
- Display Properties Background tab
- Expected
- Test pattern displayed
4 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: CRT monitor artifact 2 (inconsistency, flickering)
Verify absence of visual inconsistency and flickering artifacts
Ranked causes
- 1. Artifact 2 verification procedure (unknown)
Display Artifact 2 test pattern
- Test point
- Display Properties Background tab
- Expected
- Test pattern displayed
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: CRT monitor chipping
Measure and verify no chipping exceeds 0.41 mm in center fluorescent face area
Ranked causes
- 1. CRT fluorescent face chipping inspection procedure (unknown)
Inspect chipping in center fluorescent face area
- Test point
- Center of CRT fluorescent face (254 mm x 343 mm area)
- Expected
- No chipping above 0.41 mm, ≤
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: CRT monitor luminance
Measure and set CRT maximum luminance and uniformity across screen
Ranked causes
- 1. Luminance verification and calibration procedure (unknown)
Display test pattern (Brightness)
- Test point
- Display Properties Background tab
- Expected
- All white pattern visible
3 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: CRT monitor resolution
Verify CRT display resolution meets specifications using test pattern
Ranked causes
- 1. Resolution verification procedure (unknown)
Set luminance precondition (all white pattern)
- Test point
- Center of CRT screen
- Expected
- 250±10 cd/m2, ±10
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Monitor distortion and tilt
Correct pin-cushion distortion and tilt on 21" CRT monitor
Ranked causes
- 1. Display distortion and tilt calibration procedure (unknown)
Correct pin-cushion distortion
- Test point
- Knob e
- Expected
- No visible barrel or pin-cushion distortion
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Monitor horizontal and vertical position
Adjust horizontal and vertical display position on 21" CRT monitor
Ranked causes
- 1. Display position calibration procedure (unknown)
Set horizontal position
- Test point
- Knob b
- Expected
- Display centered horizontally
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: Monitor horizontal and vertical size
Adjust horizontal and vertical display size on 21" CRT monitor
Ranked causes
- 1. Display size calibration procedure (unknown)
Set horizontal size
- Test point
- Knob a
- Expected
- Display width appropriate
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
CRT monitor screen chipping detected caution
Visual defects or chips visible on the fluorescent display surface during quality assurance testing
Ranked causes
- 1. Manufacturing or handling defect in CRT screen (unknown)
Visually inspect CRT monitor screen for chipping using test pattern
- Test point
- Center area of fluorescent face, rectangular region 254 mm x 343 mm
- Expected
- No chipping above 0.41 mm on average, 0.41 mm maximum average
- Tools
- Test pattern display, visual inspection
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
CRT monitor screen size or position incorrect
Monitor display dimensions or positioning does not meet specifications
Ranked causes
- 1. Monitor adjustment knobs not properly configured (common)
Measure screen width (X dimension)
- Test point
- Horizontal dimension L1-L2
- Expected
- 360 mm, ±1%
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Delete items from COMP parameter maintenance screen
Remove selected items from the COMP prm-MT list box using double-click and delete dialog
Ranked causes
- 1. User selects item for deletion (unknown)
Double-click item in list box
- Test point
- COMP prm-MT screen list box
- Expected
- Select Modification dialog appears
2 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Environmental settings lost after installing DICOM or AP key caution
System settings and configuration parameters not restored after key registry installation.
Ranked causes
- 1. Environmental settings not restored after key installation (common)
Verify backup of environmental settings was created before key installation
- Test point
- System file directory or backup media
- Expected
- Backup files present from INSTALLATION section 7 procedure
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Host name not specified or requires change
Computer network name not configured or needs modification
Ranked causes
- 1. Host name not set or requires update (unknown)
Verify host name is set
- Test point
- Network dialog > Identification tab > Computer Name
- Expected
- Desired host name configured
- Tools
- Windows network settings
1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Image data lost after HDD replacement or Windows NT reinstall caution
Image data on D: drive becomes inaccessible or deleted when HDD is replaced or Windows NT is reinstalled.
Ranked causes
- 1. Image storage partition (D:) deleted during HDD or OS installation (common)
Verify D: partition exists in Disk Administrator
- Test point
- Disk Administrator main window partition list
- Expected
- D: partition visible and formatted as NTFS
4 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Monitor display menu does not appear
Menu fails to display after HDD access lamp goes OFF on 21" CRT monitor
Ranked causes
- 1. Monitor brightness and contrast require adjustment (common)
Verify HDD access lamp is completely OFF
- Test point
- HDD access lamp
- Expected
- Lamp OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Network information not configured
Windows NT network settings not properly configured for system communication
Ranked causes
- 1. Network Identification and Protocols not configured (common)
Verify network adapter installed
- Test point
- Network dialog > Adapters tab
- Expected
- 3Com EtherLink XL NIC (3C905B-TX)
- Tools
- Windows network settings
2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Quit COMP parameter maintenance application
Close ComPrm.exe application with unsaved changes prompt if needed
Ranked causes
- 1. Application closure requested (unknown)
Click CLOSE button on COMP prm-MT screen
- Test point
- COMP prm-MT screen CLOSE button
- Expected
- Application closes or unsaved changes dialog appears
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Save changes in COMP parameter maintenance
Save modifications made in COMP prm-MT screen without quitting the application
Ranked causes
- 1. Changes made requiring save (unknown)
Click SAVE button on COMP prm-MT screen
- Test point
- COMP prm-MT screen SAVE button
- Expected
- Changes saved without exiting application
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Screen saver not configured to prevent monitor burnout caution
CRT monitor screen saver setting not enabled, risking phosphor burnout during idle periods
Ranked causes
- 1. Screen saver disabled or set to None (common)
Verify screen saver type selection
- Test point
- Display Properties > Screen Saver tab
- Expected
- Blank Screen
- Tools
- Windows display settings
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Software upgrade to version A02 required
System requires upgrade from A00 or A01 to A02 version including software installation, file copy, registry setup, image file conversion, and database restructuring
Ranked causes
- 1. Software version upgrade needed (unknown)
Insert installation CD-ROM into drive
- Test point
- CD-ROM drive
- Expected
- Setup screen appears
11 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System startup time not optimized
OS loader wait time at startup not configured for reduced boot delay
Ranked causes
- 1. OS Loader show list timeout set to default value (common)
Verify OS Loader wait time setting
- Test point
- System Properties > Startup/Shutdown tab > Show list for field
- Expected
- 5 seconds
- Tools
- Windows system settings
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
TCP/IP and IP address configuration incomplete
TCP/IP protocol and IP address settings not configured for network communication
Ranked causes
- 1. TCP/IP protocol not configured with IP address and subnet mask (common)
Verify TCP/IP protocol selected and configured
- Test point
- Network dialog > Protocols tab > TCP/IP Properties
- Expected
- TCP/IP configured with valid IP address and subnet mask
- Tools
- Windows network settings
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
0709 | Software application error | Failure during equipment management from software | error |
0A09 | Application error – field portion failure | Occurs in exceptional portion locations | error |
0AD9 | Application error – error detection expected procedure | When expected procedure components occur | error |
0B09 | Application error – work token issue | When work token errors currently occur | error |
0C09 | Application error – initial portion issue | When portion locations of image management occur | error |
0CD9 | Executable process margin possible | Margin in executable process possible | error |
0D09 | Application error – equipment requirement | When equipment requirement equipment get properly managed | error |
0D90 | Application error – equipment management | When equipment management fails | error |
0DD9 | The External error – error detected in operable device | When error is detected in operable device | error |
0E09 | Application error – required function management | When required function management equipment get properly managed | error |
0ED9 | The External error – transmission idle | When transmission idle error occurs | error |
0F09 | Application error – management device | When management device gets properly managed | error |
0FD9 | The External error – transmission idle | When transmission idle error occurs | error |
0x0258 | Failure recovered, memory buffer network timeout | Normal structured processing could not be completed | error |
0x0359 | Failure to delivery, memory buffer network timeout | Network data delivery transmission failure during image processing input | error |
0x1152 | Time-out between various image managing commands | Timeout when multiple image receiving or transmitting commands occur during execution | warning |
0x121F | Check other device status or reconnect external device | Command/network connection timeout to external network device during network reception | error |
0x1251 | Failure to start image transmission, image data timeout | Timeout of image data transmission start signal during image processing input | error |
0x135B | Time-out during command reception network reception exception | Timeout during command/network reception when other network device or external device communication occurs | error |
0x136F | Time-out in device network reception exception | Time-out during command reception in external network device with external device communication network connection | error |
0x1F52 | Socket function test failure on FCR R/I-F connection network function | When no response reception or error detection occurs during image input processing network reception when other network device communicates within E/I-F socket function connection network | error |
0x4317 | Failed reception exception (1) or failed trans-mission to SCM CPU from device interface (2) | When unexpected reception error or transmission failure from SCM CPU or when device interface device driver receives error/unexpected reception or transmission failure | error |
0x7258 | Failed severe receiver, memory buffer network timeout | Network buffer timeout during external device communication receiver function during image processing input | error |
0x7261 | unknown | ||
0x8500 | Installation complete, ROM-DC key execution exception | ROM-DC key execution or ROM-DC key installation cannot start | info |
0x8501 | Command definition and file error in command and file definition error | File definition error in command definition management or file name definition error in command management | error |
1709 | Software design error during sensor signal detection | Error occurs when managing sensor signals during design and control logic | error |
1901 | Software error on warming up | Detected during system warm-up | error |
1902 | FCR common error on system connection | System bus communication failure | error |
1903 | System management control failure | Detected during system operation | error |
1904 | Control connection failure between systems | System bus communication error | error |
190A | Failed warning for system maintenance requirement | Maintenance interval exceeded | warning |
190B | Communication error between system bus devices | System bus connection failure | error |
190C | Message display error from system message | System bus operation failure | error |
190D | Equipment required to system bus message retention failure | Equipment failure or bus message retention | error |
190E | Detected error or system bus initialization | System bus item not functioning during operation | error |
1910 | Failed warning for system initialization event | System bus initialization event not occurring | warning |
1911 | Message display error from system bus | Message display system bus removal or failure | error |
1912 | Failed warning for maintenance or system operation | System maintenance not completed or operation prevented | warning |
1913 | Failed warning for system operation cancellation | System operation cancellation not complete | warning |
1915 | Application of soft ware patch for fuse F3 open | Fuse F3 open condition detected | error |
1916 | Application software write fault | Fault in applying application software | error |
1916A | Memory controller error in control panel | Remote monitoring memory controller fault | error |
1916B | GMIFI-E setup sensor error | Setup sensor not detected | error |
1916C | Remote monitoring error in signal transmission | Signal transmission lost during control panel remote monitoring | error |
1916D | GMIFI-E pair remote monitoring error | Permanent remote monitoring connection lost | error |
1916E | GMIFI-E wire error | Wire damage or disconnection detected | error |
1916F | GMIFI-E validity error with data transmission | Data not valid in transmission to FCR unit | error |
1917 | GMIFI-E storage error | Error detected in GMIFI-E storage | error |
1917A | FCR pipeline error detection (no exception/error) | Error detected in FCR exception/pipeline during common initialization | error |
1917E | GMIFI-E motor error detection, common memory issue | Motor monitoring in GMIFI-E encountered common memory error | error |
1917F | GMIFI-E motor timing error on detection | Motor common memory check during common initialization fle-check | error |
1917O | Management error during FCR exchange operation | Memory-related error in FCR memory management | error |
1918A | Pipeline error exception detection for monitoring GMIFI-E | Error detection required during motor monitoring motor setup | error |
1918B | Motor timing error (EOT) common memory setup | Common memory check required during air sensor monitoring setup | error |
1918C | Air sensor error (EOT) common memory check | Common memory check required during air sensor monitoring setup | error |
1918D | Monitoring error cannot occur, common memory error | Monitoring error during common memory check detector error | error |
1918E | GMIFI-E common memory check error detector | Common memory check in GMIFI-E during motor error detector | error |
1918F | GMIFI-E motor timing error detector | Motor common memory check during common fle-check detection | error |
1918O | Motor event not detected in setup procedure | Memory initialization failure during common GMIFI-E check | error |
1919A | FCR buffer error detection | FCR pipeline error detected during application software write fault | error |
1919E | GMIFI-E monitoring error during motor error detection | Motor error encountered common memory initialization fle-check detection | error |
1919F | GMIFI-E motor timing error on detection | Motor common memory check during common fle-check detection | error |
1957 | Image queue put up to new queue requires repair | Image queue management failure | error |
1958 | Image queue timeout error | Image queue processing exceeds time limit | error |
1959 | Image queue timeout error | Image queue processing exceeds time limit | error |
195A | Image revise semaines invalid | Image revision parameter required for maintenance | error |
195B | Application software patch for scanner window registry setting in data status | Registry setting failure during initialization | error |
195C | Application software patch for window registry viewing in data status | Registry window viewing failure during initialization | error |
195D | Channel Display invalid | Channel display parameter error | error |
195E | Channel status invalid | Channel status parameter error | error |
195F | Application software patch for initialization message not contacting the other endpoint | Initialization message queue error during system startup | error |
1960 | Application software patch for failure at parameter detect equipment element | Equipment parameter detection failure at equipment element level | error |
1961 | Application software patch for connection parameter memory element generation detect equipment element | Memory element generation detection failure during initialization | error |
1962 | Application software patch for retriever and connection element reset initialization reservation server | Initialization reservation service failure | error |
1963 | Image queue put up to new required file system management generator sub-bus management configuration require field equipment queue file receiving new only when image recovery fails | File system queue management failure during sub-bus management generation | warning |
1964 | Image revise processing sub-bus subsystem (Waiting for Host to commence useful transmit of error code Host ports) | Sub-bus processing error during host communication | error |
1965 | Application software patch for force across external transmit element external retain element (Waiting for Host to execute subsystem error at connection element and transmit management force required) | Sub-bus system transmit element force error during host management | error |
19A | Detected error | Error condition detected during operation | error |
19B | Detected problem error | Problem detected during operation | error |
19C | Smmu exposure error | SCMU memory error on exposure attempt | error |
19C0 | Common condition identify error | Failed to identify common condition | error |
19D | SCMU open error | SCMU failure to open or initialize | error |
19D0 | FCR-DMS initialization error | When FCR-DMS device fails to initialize properly | error |
19D1 | FCR-DMS common communication pipeline error | When FCR-DMS device experiences pipeline initialization failure | error |
19D2 | FCR-DMS protocol analysis error | When FCR-DMS device reports protocol or analysis failure | error |
19D3 | FCR-DMS memory management error | When FCR-DMS device has insufficient memory capacity | error |
19D4 | FCR-DMS header data error | When FCR-DMS device header data becomes corrupt or unavailable | error |
19D5 | FCR-DMS data pipe performance error | When FCR-DMS device pipe parameter data becomes corrupt or unavailable | error |
19D6 | FCR-DMS bearing mechanical error | When FCR-DMS bearing channel becomes damaged or misaligned during operation | error |
19D9 | FCR-DMS image data management error from file lost | When FCR-DMS device loses image data due to file error in working memory or corrupt property parameters | error |
19DA | FCR-DMS image data management convert error | When FCR-DMS device image data format conversion fails or patient data becomes corrupt | error |
19E | SCMU reset error | SCMU reset sequence failed | error |
19E0 | Error detected in pixel data no linearity | When FCR-DMS device pixel linearity validation fails during data acquisition | error |
19E1 | Error detected in image management convert data correctly | When FCR-DMS device fails to correctly convert imaging management data during process | error |
19E2 | Error detected in device receiver malfunction | When FCR-DMS device receiver component fails during data acquisition | error |
19E3 | Error detected in receiver data error wired | When FCR-DMS device wired receiver component has data transmission error | error |
19E4 | Error detected in assembly malfunction wired in data | When FCR-DMS device wired assembly component fails during data transmission | error |
19E5 | Error detected in event send notification | When FCR-DMS device fails to send notification event during operation | error |
19E8 | Error detected in event reset component test | When FCR-DMS device event reset component fails verification test | error |
19E9 | Error detected in receiver current output voltage supply acquisition in imaging management | When FCR-DMS device current output measurement fails in device receiver during imaging management | error |
19EA | Error detected in excess pixel size reduced in imaging management | When FCR-DMS device pixel size reduction fails during imaging process with data management | error |
19EB | Error detected in time-out completion when event receives | When FCR-DMS device receives time-out completion signal during event acquisition | error |
19EC | Error detected in timer selection removed item | When FCR-DMS device timer selection item is removed or deselected | error |
19ED | Error detected in test timer element removed | When FCR-DMS device test timer element component is deselected or removed | error |
19EE | Error detected in receiver warning event with await | When FCR-DMS device receiver sends awaiting warning event during operation | error |
19EF | Error detected in failed waiting event with timeout | When FCR-DMS device fails waiting event timeout during operation with file refresh on start | error |
19F | SCMU close error | SCMU closure operation failed | error |
19F0 | Error detected in exclusive pixel ID identification list exclusion in receiver | When FCR-DMS device exclusive pixel list item is excluded during receiver configuration | error |
19F1 | Error detected in element deleted in image element | When FCR-DMS device image element component is deleted or deselected | error |
19F2 | Error in exclusive pixel item validation list | When FCR-DMS exclusive pixel item validation fails during data acquisition | error |
19F3 | Error in base data add specific pixel identification validation | When FCR-DMS device specific pixel validation fails during base data acquisition | error |
1D90 | The Transmission error – reserve device cancellation | When transmission errors occur that allow reverse reserve transmission | error |
2709 | Storage management error | Failure during software management from equipment | error |
29C0 | Print DICOM data configuration error | System cannot properly configure DICOM print settings | error |
29C1 | Printer connection lost or multiple mount required | System loses connection to DICOM printer or needs multiple mount operations | error |
29C2 | Error in print correction program | Print correction program fails or encounters configuration error | error |
29C4 | E-title formation error | System cannot properly form or configure E-title settings | error |
29C5 | Different valve count in image and image gammas | Valve count mismatch detected between image and image gamma settings | error |
29C6 | Error in print correction program due to ongoing condition | Print correction program error occurs; one condition persists from prior images | error |
29C7 | Error in failure of image full function | System loses full function capability of image processing | error |
29C8 | Image reference box sequence error; requires printer setup | System has image reference box sequence issue; requires new DICOM printer setup | error |
29C9 | Error in image gallery connection malfunction | System has connection issue with DICOM image gallery or DICOM module | error |
29CA | Common-class error; visual verification event needed | System detects common-class error condition; visual verification and correction program needed | error |
29CB | Error in configuration function management | System cannot properly configure function management settings | error |
29CC | Error in image full function; system message return required | Image full function failure; system status return needed | error |
29CD | Error causes items missing from DICOM module output | System detects items missing from DICOM module; either cause or status issue | error |
29CE | No connection with DICOM module; disassembled connection status | System has no connection or disassembled connection with DICOM module | error |
29CF | Error in XCO complete open function; DICOM module repair needed | XCO complete open function error; DICOM module requires repair or exchange | error |
29D0 | Error disassembled from DICOM module backup | System encounters error during DICOM module error disassembly from backup | error |
2D90 | The Transmission error – transmission missing | When transmission errors occur that allow checking when enabled | error |
3709 | Software completion error | Failure during software equipment management operation | error |
4709 | Memory capacity error | Memory capacity exceeded or invalid during system operation | error |
5709 | Data error or corrupt data base | Failure during data management software operation | error |
5D90 | Error detected – parameter retention | When parameter retention error detection when enabled for parameter setup output | error |
6709 | Network transmission error | Device network transmission failure or missing equipment service | error |
7709 | Management error class | Failure during management software operation | error |
8028 | Common error in corrective action | Occurs between corrective actions | unknown |
8029 | Error in initializing socket | Occurs between corrective actions | unknown |
802A | Confirmation connecting films | Occurs between corrective actions with diagnosis of films | unknown |
802B | Installation elevation variant | Corrective error received in installation settings | unknown |
803E | Program error | Error in software application version | unknown |
85D | Connector field tool error | During field tool detection | error |
8601 | Film analysis process occurs filter file character notation maintenance; film filter backlash set during film initialization | Occurs during film analysis process of filter file character notation; film character notation backlash set during film file initialization; may occur due to filter analysis process during film filter initialization file setup | error |
8709 | Cancel elegant connection error | Elegant connection cancel error during device service revision | error |
8C09 | Application error | Occurs when prerequisite conditions are met | error |
8F89 | Software corruption - parameter error | When parameter files become corrupted or invalid capacity exceeds memory limit | error |
9008 | Application software error | Firmware malfunction during operation | error |
9018 | Application software error | Firmware malfunction during operation | error |
9028 | Image processing output success error | During imaging output, on the other hand, user sees | error |
9048 | Application software error | Incoming filter error in filter property replacement error (error being seen in filter property) | error |
9058 | Application software error | Internal filter error, maintenance start data missing imaging start data at input imaging system maintenance, confirm error mission missing start data in input imaging system | error |
9068 | Application software error | Internal filter error in data management, confirm imaging management error in input imaging system (data management error in imaging system (occurred error on input imaging equipment)) | error |
9078 | Application software error | Interlocking internal filter error, revise receiver messaging in receiver for all exchange filter requirements (reviser required) | error |
9088 | Application software error | Receiver messaging system malfunction error, new worker required in worker availability | error |
9098 | Application software error | Interlocking filter object error occurrence (Interlocking filter object error in filter object property) | warning |
90A | Application software error | Error occuring to application software error code protocol (error due to filter mapper protocol mapping) | error |
90A8 | Application software error | Interlocking worker for filter mapper status/functionality required input mapper occurrence (reviser required) | error |
90B | Application software error | Data driven from input imaging equipment restart (error running during input imaging equipment) | warning |
90B8 | Application software error | Transmission multiple filters detected (multiple filters detected in transmission error due to filter sensor in transmission error due to filter sensor transmission) | warning |
90C0 | Application software error | Error occuring to application 'hand-held field-hand-bus-system-message's (error of acquisition for the hand-held field-hand-bus-system-message's right success access) | error |
90C1 | Application software error | Error 'eraser base data success access' hand-held field-hand-bus-system (hand-held field-hand-bus-system (right success access) base data eraser during) | error |
90C2 | Application software error | Error 'imaging get' field-hand-bus-system (image get field-hand-bus-system) (right success access) base data | error |
90C3 | Application software error | Error occurrence 'router's imaging data' field-hand-bus-system (router's imaging data in imaging from field-hand-bus-system (right success access)) | error |
90C4 | Application software error | Error occurrence 'togs get' field-hand-bus-system (togs get data imaging transition in data transmit field-hand-bus-system (right success access) has base data) | error |
90C5 | Application software error | Error occurrence 'togs finish' field-hand-bus-system (togs finish imaging from field-hand-bus-system (completing transition data) has base data) | error |
90C6 | Application software error | Error 'get' imaging 'get' field-hand-bus-system (from field-hand-bus-system (right success access) has require imaging get data 'get') | error |
90C7 | Application software error | Error 'delete' imaging 'deleted' field-hand-bus-system (delete field-hand-bus-system (has base data 'delete')) | error |
9114 | Extended examination/API application error | System maintenance requirement not received | error |
9115 | Common examination error | System failure in bus | error |
9117 | Cannot connect - apply application software | Memory failure encountered | error |
9118 | Cannot connect - apply application software | Channel status of the function | error |
9119 | Cannot connect - apply application software | Receiving by accessing message | error |
911A | Cannot connect - apply application software | Equipment image initialization queue | error |
911B | Failed - apply application software | Wait without image equipment initialization queue | error |
911D | Cannot connect - apply application software | Equipment image deletion queue | error |
911E | Cannot connect - apply application software | Equipment image modification queue | error |
911F | Image processing error | System bus expected | error |
911F | Cannot connect with connected host to which image is output | DTK returned error 'cannot connect to host'. Failed in request for connection | error |
9120 | Cannot connect - apply application software | Equipment image get maintenance code | error |
9121 | Cannot connect - apply application software | Received in get memory generation into queue | error |
9123 | Cannot connect - apply application software | Equipment image initialization queue | error |
9124 | Cannot connect - apply application software | Equipment image open on file queue | error |
9125 | Cannot connect - apply application software | Duplicate file queue failure backup queue control open door | error |
9126 | Cannot connect - apply application software | Equipment image still in file queue | error |
9127 | Cannot connect - apply application software | Equipment image still in file back queue in operation | error |
9128 | Cannot connect - apply application software | Received in get memory generation without queue | error |
9129 | Cannot connect - apply application software | Equipment image written in data queue | error |
912A | Cannot connect - apply application software | Equipment image written in file back queue queue | error |
912A | Image data confirmation from imaging procedure in application | Image data loss or invalid image data from imaging procedure | error |
912B | Image reception of multiple required image transmission data | Image transmission from imaging data error | error |
912B | Cannot connect - found error | Equipment error in found queue data queue | error |
912C | Cannot connect - apply application software | Equipment display status queue in operation | error |
912C | Error connection with common notification | Notification error during equipment connection | warning |
912D | Cannot connect - apply application software | Equipment correct position in operation | error |
912D | Equipment connection required for image detection | No connection to equipment for image transmission | warning |
912E | Image receiving reject cases with image management | Image receiving rejection during imaging management | error |
9139A | Apply power-on operation warning | Applied power-on operation | warning |
9139B | Applied power-on operation warning | Applied power-on operation | warning |
9139C | Error detected in file closing during error occurring announcement | File close error during announcement | error |
9139D | Error detected in file getting during announcement | File get error during announcement | error |
9139E | Error detected in file getting during closing announcement | File get error during closing announcement | error |
9139F | Apply power-on operation warning for file lock control | File lock control error during power-on | warning |
9140 | Apply power-on operation warning for file lock control (Unused/Expected announcement) | File lock control error during power-on | warning |
9141 | Apply power-on operation without property support. FINF/FINP detected image imaging in system. | Image imaging detected without proper support | warning |
9142 | Apply power-on operation warning for component open file | Component open file error during power-on | warning |
9143 | Apply power-on operation warning for file open deletion contact | File open deletion error during power-on | warning |
9144 | Apply power-on operation warning for file locking image delete | File locking and image deletion error during power-on | warning |
9144B | Apply power-on operation warning for one-time transmissions from device received coverage | One-time transmission data not received or coverage failure | warning |
9144C | Apply power-on operation warning for file locking and image management control inhibition | File lock and image control problem during power-on | warning |
9144D | Apply power-on operation warning for image size get | Image size determination error during power-on | error |
9144E | Apply power-on operation warning for error detection during imaging transfer data | Error detected during image transfer or imaging startup data | error |
9144F | Apply power-on operation warning (file lock) for file locking image management | File lock control error during imaging management | warning |
9150 | Apply power-on operation warning (undetermined) for file lock control component registration | File lock control component registration failure during power-on | warning |
9151 | Apply power-on operation warning for file log manner | File log management error during power-on | warning |
9152 | Apply power-on operation warning for file log open file | File log open file error during power-on | warning |
9153 | Apply power-on operation warning for file log writing data the file | File log writing data error during power-on | warning |
9154 | Apply power-on operation warning for memory control operation encountering memory encountered | Memory insufficient operation error memory encountered | warning |
91F4 | Application software failure on FCR interface | Detected during startup or operation | error |
91F5 | Unexpected error detected in image data memory | Detected during image processing or delivery | error |
91F6 | Data management error in output memory window | Detected during image output or storage operation | error |
91F7 | Data management error during FCR image remapping | Detected when remapping with new data assignment | error |
91F8 | Common communication error in momentum memory buffer | Detected during image acquisition or communication | error |
91FA | Application software failure or messaging sensor detection | Software or sensor messaging failure during startup | error |
9207 | Receiver command exception or undefined request | Invalid or unrecognized command from receiver | warning |
9208 | FCR event failed to activate or maintain | Event activation failure or event maintenance loss | warning |
920A | Receiver requires connection or cannot connect | Receiver cannot establish connection or connection lost | warning |
920B | Event failure during maintenance or event absence | Maintenance event failed or event completely absent | warning |
920C | Receiver monitoring failure for motion or image delivery | Monitoring system failed during multi-image transmission | warning |
920D | FCR-DMS station failure during scene or receive initiation | Station communication failure or receive initiation failed | error |
920E | Imaging FCR-DMS transfer or receive imaging failure | Station imaging transfer or scene receive failed | error |
9215 | FCR-DMS current status in application process | Detected during FCR startup or command process | info |
9216 | Application of waxproofing for FCR processor commonization | Data invalid during imaging procedure | error |
9217 | Multiple image receiving required during imaging management | Image data transmission error or incomplete image set | error |
9219 | Image exclusive setting to visible setting atlas | Image exclusion conditions detected | error |
9220 | FCR processor exclusivity of test settings | Exclusive visibility in image test | error |
9221 | FCR processor visual exclusivity test to visible setting atlas | Visual exclusivity settings invalid or test point atlas settings require definition | error |
9222 | Connect alert contact between holder and content placement | Contact connection error when content placement changed | warning |
9223 | FCR image receiver modification required | Image modification required when FCR image receiver changed | warning |
9224 | Equipment detection connection threshold | Equipment connection error detected during procedure | error |
9225 | FCR image receiver with attention attachment when multiple transmit frames | Image attachment error during multiple image frame transmission | warning |
9226 | Connect collation with memory capable validation | Memory capability validation error detected | error |
9231 | Occurrence in common accommodation phase | Common accommodation request during imaging transmission | error |
9232 | Collation contact with memory capable validation | Memory capability validation error | error |
9240 | RC maintenance component sensing required before RC initialization in formation. | RC component sensing procedure initiated | error |
9241 | RC maintenance component sensing required; starting RC maintenance in formation. | RC diagnostic/maintenance procedure initiated | error |
9242 | If it was not equipped to perform corpse decoding of RC maintenance component. | RC decoding/initialization procedure initiated | error |
9243 | If it was not equipped to perform corpse decoding of RC maintenance component. | RC maintenance decoding operation initiated | error |
9244 | If it was not obtainable the WA/IP reception in the error context. | RC error detection/reporting procedure initiated | error |
9245 | If it was not converted to obtain the RC maintenance error over interval. | RC maintenance interval conversion procedure initiated | error |
9246 | If it was not opened potential decoding failure in RC maintenance component. | RC component opening/access procedure initiated | error |
9247 | RC wired failure in maintenance of the RC component. | RC wired component maintenance procedure initiated | error |
9248 | If it was not closed RC maintenance in the RC component. | RC component closing/completion procedure initiated | error |
924A | If it was required the RC maintenance component by failure configuration error decision. | RC failure configuration/initialization procedure initiated | error |
924B | If it was not successful the occurrence of time item in RC maintenance. | RC time interval maintenance procedure initiated | error |
924C | If it was not with equipment when RC maintenance configuration initializing other hosts. | RC maintenance with host equipment initialization procedure initiated | error |
924D | If it was not containing error the RC maintenance in order to perform formation. | RC formation/initialization procedure initiated | error |
924E | If it was not equipped to RC maintenance of item sensing notification failure. | RC item sensing/notification procedure initiated | error |
9251 | If it was not obtainable the RC maintenance area from an error occurrence. | RC area sensing/recognition procedure initiated | error |
9252 | If it was not obtained the table basis access base field of hands analysis. | RC data table access procedure initiated | error |
9253 | If it was not obtained the RC store error in order of maintenance perform formation base data. | RC error storage/retrieval procedure initiated | error |
9254 | If it was not stores other RC error in order of store of all devices formation. | RC error store synchronization procedure initiated | error |
9255 | If it was not stores other RC error data of store of all devices formation. | RC error data store synchronization procedure initiated | error |
9256 | If it was not obtained the RC error of the data updating from data provided. | RC data update/sync procedure initiated | error |
9257 | If it was not obtainable the RC maintenance area from a file error occurrence. | RC area file access procedure initiated | error |
9258 | If it was not obtainable the RC maintenance area from a file error occurrence. | RC area file access procedure initiated | error |
9259 | If it was not obtainable the table basis of access field hands for the file. | RC table file access procedure initiated | error |
929A | Error occurred when not connected to Host | Connection loss to Host system | error |
929A0 | Image modality failure detected | Modality validation error in received image | warning |
929A1 | Image document code error | Document code validation failed | warning |
929A2 | FCR image ID error detected | Image ID validation failure | warning |
929A3 | Workorder number missing or invalid | Workorder validation failed | warning |
929A4 | Imaging module error detected | Module validation failure | error |
929A5 | Detector sorbitol value error | Detector sorbitol validation failed | warning |
929A6 | Image extended size error | Image size exceeds limit or invalid | warning |
929A7 | Image transfer failed, cannot connect | File transfer connection failed | error |
929A8 | Image process code error | Process code validation failed during transfer | warning |
929A9 | Scanning engine error detected | Engine validation failed during direction correction | error |
929AA | Pixel value error during transfer | Pixel data validation failed | warning |
929AB | INB module retrieval failure | INB module cannot be accessed or retrieved | error |
929AE | Element A not specified in data | Required element A missing from dataset | error |
929AFA | E-A title printer not detected | Printer communication failed or absent | warning |
929AFB | Film dryer exists with N configuration | Film dryer present but configuration incorrect | warning |
929AFD | Film detected error during session | Film detection failed or unexpected condition | warning |
929AFE | Film dryer Box error on startup | Film dryer box initialization failed | error |
929AFF | Film extended size error on startup | Film size validation failed during initialization | warning |
929B | Error occurred when connected to Host | Error condition during Host communication | error |
929C | Image retrieval failed during charging | Image not received or retrieved during operation | warning |
929D | Error occurred during image management | Image management operation failure | error |
929E | Error received from device recovery | Recovery operation failed | critical |
929F | Error validation failed during operation | Validation check did not pass | warning |
929F3 | If it was not obtainable the WA/IP reception mechanism in order to perform diagnosis RC maintenance. | Equipment diagnostic procedure initiated | error |
9503 | External Communicator Sub System Detection Error (DICOM) | Distribution destination node set to DICOM but DICOM support is OFF in equipment, or no protocol set at destination node | error |
9556 | Invalid image data field | Connected host attempts to send image with illegal field value (date, time, modality, anatomical region, FCR ID, rows, columns, storage bit, expansion read size, compression, assigned bit, effective bit, data size, PIXEL, LINE, or scanning direction) | error |
9562 | Notified error to connected host | SOP class VIP of image to be sent is not set for network for DICOM of this equipment | warning |
9601 | DICOM printer resizing in image does not exist or there is no image in DICOM printer display format processing | Image information management in DICOM printer input information display format processing does not occur; image resizing function not found in printer input image format information | error |
9603 | Image value outstanding signal out other image signal it can reverse the output signal reverse the image value | The image value it can range from display format DICOM printer display format processing DICOM printer input information management to range outstanding image signal out to signal outstanding output | error |
9604 | DICOM printer setup failed title-E.A. printer DICOM with specification | When DICOM printer (new.tnirP.MOCI.D) did not get the specified setup with specification with title-E.A. | error |
9605 | DICOM printer identifying key setting identification number INB is numerical; Please make configuration with DICOM Printer configuration file connection contents of configuration management file setup management apparatus configuration management file startup configuration management file setup application management error instruction setup from DICOM Films (new.stliF) to execute films setup application setup management operation configuration file | When DICOM Films (new.stliF) could not get the specified setup with configuration management file setup management apparatus configuration management file | error |
9607 | DICOM printer Films creatic failure - It failed to get session from DICOM printer | Occurs when session transfer error occurs during DICOM printer operation or image management failure during DICOM printer session operation failure | error |
9608 | Film processing error - COM image management failure | Image management from COM box for film printing fails | error |
9609 | Film imaging management failure | Image imaging system fails for film processor COM box | error |
960A | Film printing failure detected | Film printer output operation fails | error |
960B | COM image management processing error | Digital COM image processing fails | error |
960C | Film image processing failure - Defective image in film numbering | Film printing system detects defective output image | error |
960D | Film E-A title designation error | Film E-A title not found in destination device configuration file | error |
960E | Program error - existing numbered image failure in film numbering | Film system detects inconsistency in image version control | error |
960F | Program error - Film numbering failure in image management | Film processing system fails on multiple image numbering or group operations | error |
9610 | Program error - Film system version failure | Film system detects version control or configuration mismatch | error |
9611 | Error occurrence in DCOM printer operations | Error status detected before correction in DCOM printer operation | error |
9612 | Program error - Multiple image numbering in film system | DCOM image management processing fails for common class image numbering | error |
9613 | Program error in configuration management of DCOM printer | Error in DCOM printer configuration execution or runtime management | error |
9614 | Program error - Common class error in DCOM printer configuration | Error in DCOM printer configuration with event view function | error |
9615 | Program error in system operation management | System operational error detected in same operation conditions | error |
9616 | Film output failure - No response from film processor | Film processor fails to respond to COM output request from DCOM box | error |
9617 | DCOM connection error - Connection not established with printer | DCOM box fails to establish connection with printer during setup | error |
9618 | Program error - COM XCP component failure in DCOM | System detects error in COM component operation | error |
9619 | Error feedback - Film system backup function failure (BSF-N CAUTION) | DCOM printer backup function error from secondary film system | warning |
961A | Error feedback - Backup film system error (BBF-N ACTION) | DCOM printer backup system error with ACTION requirement | warning |
961B | Program error - Image sizing error with MAG_TYPE and multi-film support | DCOM printer image sizing or magnitude type processing failure | error |
961C | Program error - Film string image processing failure | Film image processing analysis failure or string management error in film printer | error |
961D | Program error - Film mapping in bit-creation during film rotation | Error in film image mapping during bit-creation operation or film rotation | error |
961E | Program error - Film assignment from film string in format | Film format string management error or film string assignment failure | error |
961F | Program error - Film analysis process failure on film string image | Film image analysis process failure or error in film string configuration | error |
9620 | Program error - Film register miss-set in film string registration | Film registry failure or film string registration error during format operation | error |
9621 | Program error - Film fail condition in cable drawing during rotation | Film cable failure or film failure during rotation operation | error |
9622 | Program error - Warning status from BSF-N backup function in DCOM printer | DCOM printer backup function warning from BSF-N designation | warning |
9624 | Program error - Warning status BBF-N (TEST-BIN) from DCOM printer | DCOM printer backup warning from BBF-N (TEST-BIN) with configuration support | warning |
9709 | Network error | Equipment management transmission error or FIN/FINP required network work through | error |
9B10 | Item memory error detected | Item memory access or storage failure | error |
9B11 | Item memory get error | Failed to retrieve item from memory | error |
9B13 | Item create error | Failed to create new item in memory | error |
9B14 | Item event error | Item event sequence error | error |
9B15 | Item stop error | Item stop signal failed | error |
9B16 | Device receiver data validation error | Received data failed validation check | error |
9B17 | One-item system error | Single-item system error detected | error |
9B18 | Thereupon error | Unexpected operation occurred | error |
9C09 | Image management error | Image management from 9C09 occurs in 09C9 formations | error |
9F01 | Connected host rejected the connection request | DTK returned error 'other host rejected this request'. Failed in request for connection or transfer | error |
9F04 | Program error has occurred. Failed in DICOM file ID processing | Internal error detection during DICOM file processing | critical |
9F1F | Program error has occurred. Failed during external DICOM request processing | Error in data during previous DICOM image input processing | critical |
9F50 | Program error has occurred. Failed in generation of DICOM threading | Internal error during DICOM input processing | critical |
9F60 | Could not send one of the specified images | Could not find information required for transfer or cue registration failed | error |
9F62 | Program error. Failed in DICOM data exchange, stream compilation, or image operations | No AE setting in DICOM configuration. AE information not transferable. Temporary file cannot be deleted | error |
9F62 | Network obstacle in image output processing. Failed in DICOM output association or output | No response from host to which image was input or output. DTK transfer text registration or connection request returned error during DICOM output | error |
A100 | unknown | ||
A1F5 | unknown | ||
A1F6 | unknown | ||
A1F8 | unknown | ||
A1F9 | unknown | ||
A1FA | unknown | ||
A1FB | unknown | ||
A1FC | unknown | ||
B00 | Start-up timeout to process subsystem detection | Image Processing Subsystem does not complete startup within timeout period | error |
B02 | Insufficient memory recovery; equipment restart required | Occurs when memory efficiency insufficient for Image Processing Subsystem startup | error |
B03 | Image data files damaged; image data file deleted or corrupted | The image data files have been deleted with corrupted files detected during system operation or SysOp Data Management execution | error |
B060 | Application software write error | Detected during setup management | error |
B066 | Memory reconnection error | Detected during setup management | error |
B0C9 | Image management damaged or file image management error occurs | Detected during data management | error |
B0CA | File image management error occurs | Image data corruption or system error | error |
B100 | unknown | ||
B12E | Data revision device received image data | Image data retrieval or verification process | warning |
B12F | Image data entered into device | Image data input process | warning |
B130 | Image information from device data management | Data retrieval or management failure | error |
B131 | Image information from device data | Data validation failure | error |
B132 | Application software connection error | Connection detection during software operation | error |
B133 | Application software connection error | Connection detection during software operation | error |
B134 | Application software connection error | Detected during application operation | error |
B135 | Application software connection error | Connection detection during operation | error |
B136 | Application software connection error | Connection detection during operation | error |
B137 | Specific memory steps error | Memory operation failure | error |
B138 | Application software write error | Detected during operation when data corruption occurs | error |
B192 | The image processing error occurs | Image processing subsystem failure or bus-to-bus transaction failure | error |
B1F5 | Application software write error | Detected in operating parameter set | error |
B1F6 | Application software write error | Detected in operating parameter set | error |
B200 | unknown | ||
B259 | Application software write error | Error detected in processor or core error during image processing | error |
B2BD | Application software connection error | Detected operating error in OCX | error |
B300 | unknown | ||
B321 | Application software write error | Image management error detected | error |
B323 | Unexpected volume firmware error detected | Memory detection during function diagnosis | warning |
B400 | unknown | ||
B709 | Configuration initial maintenance error | Failure from transmission maintenance configuration | error |
B7CE | Application software write error | Error detected in internal translation | error |
C004 | Start-up timeout to process subsystem detection one-time | Occurs one-time or multiple times during Start-up timeout phase | error |
C004 | Invalid parameter value (1) | When system detects invalid parameter during initialization | error |
C005 | Invalid parameter value (2) | When system detects invalid parameter during operation | error |
C006 | Cannot connect to database | When system fails to establish database connection | error |
C008 | Cannot modify database | When system fails to modify database contents | error |
C009 | Data database match failure | When system detects data mismatch between database and image management | error |
C00A | Cannot connect to required database | When system fails to establish connection to database | error |
C00B | No access to parameter requisites | When system cannot access required parameter configuration | error |
C00D | Data value is invalid | When system detects invalid data value | error |
C00E | Memory allocation failure | When system fails to allocate sufficient memory capacity | error |
C00F | Multiple imaging management | When system processes multiple image management operations concurrently | warning |
C010 | Equipment exception record or image management image correlation issue | When equipment detects processing errors or image management equipment management issue (1) Firmware test equipment management issue with new equipment, if initial firmware in management cache, return equipment (2) Restore equipment cache. | critical |
C011 | Field initialization socket corruption or image management issue | When field management socket error detected | error |
C012 | Equipment exception record or memory file or circuit error | When equipment detects file memory or circuit failure | error |
C013 | Field failure built-in from management information formation | When system detects field management or formation management failure | error |
C014 | No capacity in hard disk or cache area | When system detects insufficient disk or cache capacity | error |
C015 | Field failure built-in from management database contents | When system detects field management or database management failure | error |
C-016 | Invalid imaging parameter | Imaging damaging parameter detected between imaging start and end | error |
C100 | No access to memory | System initialization on Windows startup; no success access cases | critical |
C101 | Inproper apparatus preparation | In-apparatus data setup performs data management information update | warning |
C200 | Field obtained handle on the window | Memory (window, device, ACT field catch value) | warning |
C202 | Failed recovery of image data files; image data file does not exist or has been deleted | Occurs when specific image data file procedures fail during recovery attempt | error |
C300 | Unexpected field on data information | Replacement field on memory (file image management replacement mapping parameter procedures) | critical |
C404 | No space partition in hard disk or hard disk partition errors frequently occur | Hard disk partition becomes full or hard disk partition errors occur frequently; frequent occurrence indicates recurring hard disk failures | error |
C709 | Setup storage error | Setup storage failure | error |
D-001 | Image damaged or not valid | Image damaging parameter detected during imaging process | error |
D-002 | File cannot be created | File creation failure detected | error |
D-003 | Invalid file setting detected | Invalid parameter detected in file settings | error |
D-004 | Invalid parameter value detected | Any invalid parameter value found in configuration when occurred | error |
D-005 | Key word invalid | Invalid key word detected in imaging initialization from imaging function | error |
D-006 | File cannot be deleted or removed | File deletion or removal failure detected | warning |
D-008 | Parameter data memory error | Parameter data memory error detected in window data initialization in system | error |
D-009 | Transfer entry error | Transfer entry failure to entry error detected during system initialization | error |
D-00A | Transfer entry to entry error during system reset | Transfer entry error detected during system reset and initialization | error |
D-00C | File position exception detected | File position exception detected in file position during imaging or in CONF_HIGH_ICON positioning | error |
D-00D | File position exception detected in file position during CONF_HIGH_ICON initialization | File position exception detected in file position during CONF_HIGH_ICON initialization | error |
D-00E | File position exception detected in CONF_HIGH_ICON initialization | File position exception detected in CONF_HIGH_ICON initialization positioning components | error |
D-00F | SET function exception detected | SET function exception error occurs when required. Anomaly occurs when occurred. | error |
D-010 | GET function exception detected | Anomaly occurs when required during system initialization testing. | error |
D-011 | FPGA GSIS function exception detected during process initialization | Anomaly occurs when process error occurs in FPGA GSIS during initialization. | error |
D-012 | Calibration data validation error | Calibration data not found or invalid data validation error when occurred | error |
D-013 | File read error detected | File error detected in file read recovery | error |
D-014 | File write error detected | File write error detected in file recovery | error |
D-015 | Direction error to cartridge signal acquisition on registration | Image damaging parameter detected to registration is a registration. Imaging registration signal requires to apply signal acquisition for an important signal acquisition. | warning |
D-016 | Direction cart ridge movement error | Movement error in direction cartridge movement in cartridge occurred. Anomaly occurs when movement direction cartridge direction error has been detected. Different expectation from error. | warning |
D-017 | Parameter map view error | Parameter map view error in map view parameter map view error This will file setting occurs, perform error recovery procedures. File test on those files and repeat file test initialization. | warning |
D-018 | Parameter map view error | Parameter map view error in map view parameter map view error This will file setting occurs, perform error recovery procedures. File test on those files and repeat file test initialization. | warning |
D-019 | In formation information requires from registration signal from the registration | Anomaly occurs when occurred. Anomaly occurs when occurred in formation information registration signal. | warning |
D-01B | Any extra configuration detected in title ellipse there the there the extra configuration circle been detected in title exception | Any extra configuration circle in title exception there the extra configuration circle been detected in title exception (defined time), Either extra configuration circle begun or title exception has begun. | unknown |
D050D | Program error - Rotation manager requirement in formation operation | System requires rotation manager functionality in formation operation | error |
D050D | Circuit device defect - ENE file validation | Environment file ENE designation validation failure in circuit device | error |
D050D | Program error - Wiring code check with 16 or less number hold | Wiring code hex digit device circuit record validation failure | error |
D050D | Program error - Identified determination value exceeding maximum numeration limitation | Identified numeration value exceeds maximum 129 determination in calibration | error |
D050D | Program error - Rotation manager identification in ENE file | Rotation manager and manager number identification not found in formation | error |
D067 | Overprogramming PI test point pin; PPI overlay address addition overlay | During Field Tool arrangement overlay addition during Field Tool parameter arrangement (parameter overlay-add into field) | warning |
D068 | Overprogramming overlay hostname name attribute | During Field Tool overlay addition during Field Tool parameter modification during Field Tool setup with other device settings | warning |
D069 | No hostname attribute attached to pointing connection error | During Field Tool arrangement when attempting to attach hostname attribute to pointing connection error | warning |
D10 | Insufficient intensity (ITC) with 16-bit data | Detected during imaging acquisition | warning |
D1F5 | Apply configuration from recorded prior memory allocation state | Detected when prior memory allocation state not valid | warning |
D1F6 | Apply configuration error recovery from device receiver | Detected when device error recovery from prior configuration mismatch | error |
D1F7 | Apply configuration device coverage from API Window initialization | Detected when Window API error recovery application received trigger | error |
D1F8 | Apply configuration error event data base data transmission Failure | Detected error transmission failure in [Devices] and [Control Panel] status | error |
D1F9 | Initialize built-in initialization errors occurrence failure | Detected data base file correctly occurred initialization | warning |
D1FA | Apply configuration error recovery from device receiver capability | Detected common receiver error (prior error management) | warning |
D1FB | Detect parameter valid in valid parameter data in key data | Detected in key data valid parameter registered in BIOS data | warning |
D20 | Electronic A units deficiency | Condition during calibration or dynamic mode operation | warning |
D201 | Open configuration error file contents management cannot be opened in management file | File management error configuration file cannot be opened during file management configuration execution in setup startup of equipment | warning |
D202 | Configuration file overflow table data management file number in file management data | When file management error occurs after configuration file contents error conditions occur after file contents management error conditions | warning |
D203 | Inproper apparatus preparation circuit embedded Key rewording configuration management | Whenever Key rewording is different from description in file management file description (description difference) in file management file in apparatus startup equipment management setup | warning |
D21 | Gain arrangement correction needed (prone to error) | Detected during dynamic management correction operations | error |
D22 | Excessive electronic A unit values detected | Detected during calibration or filtering operations | warning |
D23 | Exception in corruption accumulation | Detected during exception management | error |
D24 | Required NUB enabling signal missing | Detected during NUB signal generation verification | error |
D25 | Callable collocation value set required | Detected during calibration or filtering operation timeouts | warning |
D26 | Multiple A-unit size fixed-title-E detection required | Detected during multi-element A units management feedback presence verification | error |
D27 | Size-coded value resizing required | Detected when size-coded value size-coded from alignment differs | warning |
D28 | Required imaging detection when size managed allegation required | Detected during size management allegation requirement verification | warning |
D29 | Remapping from allegation configuration management required | Detected when allegation configuration management needed | warning |
D2A | Patching allocation value correction required | Detected when patching allocation value requires correction | warning |
D2B | Combination with requirement mandates system requirements | Detected during combination and system requirement verification | warning |
D2C | Size codec exception in filtering operation | Detected during size codec from filtering operation size-coded verification | warning |
D2E | Multiple A-unit value filtration status requirements | Detected when multiple A-unit filtering operation status failed | error |
D2F | Callable collection value correction required | Detected when callable collection value requires calibration correction | warning |
D30 | Multiple A units status required immediate correction | Detected when A unit status data fails maximum or min fixation | error |
D31 | Specific-titled A-unit problem existence failure | Detected when A-unit problems corrupt repair requirements from | error |
D32 | Error message issue in expectancy condition required | Detected during error message check occurrence | error |
D33 | System initialization required | Detected when system initialization failed | error |
D34 | Color imaging management failure detected | Detected when color imaging management failed in system | error |
D35 | Parameter error management occurred | Detected as error management corruption occurred | error |
D36 | Program error management on occasion corruption | Detected on error occasion management corruption detected | error |
D37 | Management color imaging failure in system detected | Detected when color imaging management failure in system | error |
D50B | Allocation failure or palette allocation error | System detects insufficient memory allocation for color palette | error |
D50D | Default information in formation default piece default two piece of default formation | System detects default formation condition | error |
D50E | Image code size allocation error | System detects incorrect image code size | warning |
D50F | Maximum number of size codes exceeded in limitation | System detects exceeding maximum size codes during operation | warning |
D510 | Image sizing requirement with gallery | System detects image sizing inconsistency | info |
D511 | Film marking specifications magification rate | System detects film marking rate inconsistency within specification | warning |
D512 | Film pattern replacement pattern replacement | System detects lift film pattern inconsistency | warning |
D513 | Film combination requirement with film specification | System detects film combination or image designation inconsistency | error |
D514 | Film combination orientation film size film information maximum designation exceeding | System detects maximum designation exceeded in film combination | error |
D515 | Error application software occurrence detected | An exception has occurred in the error mapping process | error |
D516 | Exception error occurrence detected in error mapping process | Any exception detected in one or more detection invalid key rows during error mapping process | error |
D517 | Valid key detection error | System detects invalid key rows during validation | error |
D518 | Error application software occurrence detected | System cannot open file or ENE value is not available or exclusive access not available process mapping applicable | error |
D51A | Event setup maximum number of entries exceeding | System detects more than 1080 events in formation within event maximum limitation | error |
D51B | Error application software occurrence detected | An exception has been detected in error mapping file entry point detection occurrence log processing | error |
D709 | Equipment stage capacity error | Stage equipment capacity create error | error |
E025D | Specific error definition not fully readable due to OCR degradation | Unknown | unknown |
E026D | Specific error definition not fully readable due to OCR degradation | Unknown | unknown |
E0604 | Application software error | Unknown | error |
E0605 | Application software error | Unknown | error |
E0606 | Application software error | Unknown | error |
E0607 | Application software error | Unknown | error |
E0608 | Application software error | Unknown | error |
E090 | Application software error | System bus error detection during operation | error |
E091 | Hardware/control panel connection error | Control panel failure or connection loss to main equipment | error |
E092 | Image management system initialization failure | System fails to initialize management classes during startup | error |
E093 | FCR reader connection error | FCR reader fails to establish connection to main unit | error |
E094 | Header authentication or workflow error | Workflow failure or header authentication issue detected | error |
E095 | Image file life-cycle management process error | File lifecycle management process fails during current operation | error |
E096 | Image file initialization in progress or incomplete | System detects incomplete image file initialization | error |
E097 | Image file initialization suspended or error in progress | System detects 'initiate complete' message or get glossary system error | error |
E098 | System bus 'trans' message error or header control failure | Header control connection failure or system bus error when 'trans' glossary detected | error |
E09A | Register management device canine reverse operation required | System detects requirement to cancel register management device operation | error |
E09B | Equipment name doesn't match or known issue encountered | Equipment name mismatch detected or equipment exclusion required | warning |
E09D | Host management device required; reverse operation or configuration required | Candidate manager device canine reverse operation required; application software error during operation | warning |
E09E | Image review system emergency or user-defined issue encountered | User-defined emergency detected when logging in; image management system issue; missing-user attribute | error |
E09F | Work file lifecycle property deletion or registry management error | System detects lifecycle property deletion requirement; proper work item management needed | error |
E0C | Initialize data failure | Data initialization process fails | error |
E0C08 | Application software error | Unknown | error |
E0C09 | Application software error | Unknown | error |
E0C0A | Application software error | Unknown | error |
E0C0B | Application software error | Unknown | error |
E0C0C | Application software error | Unknown | error |
E0C0D | Application software error | Unknown | error |
E0D0 | Old hold load data failure | Load old hold data fails | error |
E0D1 | Write wire data failure | Write wire data fails | error |
E0D2 | Performance error | Imaging processing performance error occurs | error |
E0D3 | CSV value failure | CSV parameter processing fails | error |
E0D4 | Fail discard data | Data deletion or discard fails | error |
E0D5 | Fail registration data file | File registration fails | error |
E0D6 | Find data validity failure | Data validity check fails | error |
E0D8 | Body data convert currently | Body code conversion occurs currently | error |
E0D9 | Machine image size detection | Machine image size code fails | error |
E0DA | Lift file validation data | Uplift file manager formation fails | error |
E0DB | Lift file validation data | Uplift file manager formation fails | error |
E0DC | Machine size code sizing | Machine image sizing code fails | error |
E0DD | IT wage full failure example | Wage IT code fullness issue | error |
E0DE | IT wage full value failure | Wage IT code fullness value issue | error |
E0DF | IT wage full value failure detail | Wage IT code fullness value issue pending detail | error |
E0F0 | Proprietary directory protocol establishment failure | System fails to establish proprietary directory protocol connection | error |
E709 | Management form requirement error | Failure getting equipment management form | error |
E-A19 | FCR device receiver malfunction | Receiver hardware detects error condition | error |
F709 | Setup form requirement storage error | Setup form requirement storage failure | error |
FA19 | SCMU device malfunction | Smart Card Memory Unit error condition detected | 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.