This is the automatically generated error code documentation for version 1.11 of the printer firmware. A table of attributes for each error is given, followed by documentation for each instance of each error code.
For each error code, the attributes table has the following fields:
You can navigate to an error instance by clicking on an entry in the attributes table below and scrolling down to a particular instance, or by using the following form:
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | FPGA programming error. |
Reason: While preparing to update the FPGA, the incoming bitstream file size was wrong for the fitted FPGA part (LFXP2-8E). This is probably due to a corrupted FPGA bitstream file.
Source: line 90 of ./hal/source/fpga.c (scope: update_fpga)
Reason: While preparing to update the FPGA, the incoming bitstream file size was wrong for the fitted FPGA part (LFXP2-5E). This is probably due to a corrupted FPGA bitstream file.
Source: line 101 of ./hal/source/fpga.c (scope: update_fpga)
Reason: While preparing to update the FPGA, the device ID read from the fitted FPGA was not a recognised one. This is probably either due to a SPI comms failure between the processor and FPGA, or a faulty FPGA.
Source: line 109 of ./hal/source/fpga.c (scope: update_fpga)
Reason: While preparing to update the FPGA, the printer was unable to initialise SPI comms with the FPGA. This is probably either due to a SPI bus problem between the processor and FPGA, or a faulty FPGA.
Source: line 124 of ./hal/source/fpga.c (scope: update_fpga)
Reason: While attempting to erase the FPGA prior to reprogramming, the printer was informed by the FPGA that its erase cycle failed. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 188 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While writing a new bitstream file into the FPGA, the processor didn't receive confirmation from FPGA that it had finished writing one of the rows of data. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 221 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to verify a new bitstream file just written to the FPGA, the processor found that one of the lines of data read back from the FPGA's internal flash did not match the corresponding line of data in the new bitstream file. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 297 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to finalise the reprogramming of the FPGA, the processor failed to receive confirmation from the FPGA that finalisation was successful. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 321 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to refresh the FPGA after reprogramming, the processor failed to receive confirmation from the FPGA that the refresh process completed successfully. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 356 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While preparing to program the FPGA with a new bitstream, the printer was unable to put the FPGA into its programming mode. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 157 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While preparing to program the FPGA with a new bitstream, the printer was unable to disable the FPGA DONE fuse. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 167 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While preparing to program the FPGA with a new bitstream, the printer failed to erase the FPGA. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 177 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While preparing to start writing a new bitstream file into the FPGA, the printer failed to start the FPGA programming cycle. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 198 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While writing a new bitstream file into the FPGA, the processor failed to write one of the lines of data into the FPGA's internal flash. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 211 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to verify a new bitstream file just written to the FPGA, the processor failed to start the FPGA's verification cycle. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 235 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to verify a new bitstream file just written to the FPGA, the processor failed to read one of the lines of data from the FPGA's internal flash. This is probably either due to faulty SPI comms beween the processor and FPGA, or a faulty FPGA.
Source: line 254 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to finalise the reprogramming of the FPGA, the processor failed to receive confirmation from the FPGA that finalisation has completed. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 310 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to finalise the reprogramming of the FPGA, theprocessor failed to take the FPGA out of programming mode. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 333 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
Reason: While attempting to refresh the FPGA after reprogramming, the processor failed to send the refresh command to the FPGA. This is probably either due to faulty SPI comms between the processor and FPGA, or a faulty FPGA.
Source: line 345 of ./hal/source/fpga.c (scope: send_bitstream_to_fpga)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Firmware update failure |
Reason: While processing an incoming firmware upgrade file, the printer failed to allocate memory for decompressing the file's payload. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 100 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While processing an incoming firmware upgrade file, the printer found that the incoming file data was not of the correct format. This may be because the file has become corrupted, or there was an error in the software which produced the file.
Source: line 113 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While processing an incoming firmware upgrade file, the printer found that the incoming firmware version was too old to allow it to replace the current firmware version. This may be because the wrong file was sent.
Source: line 133 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While processing an incoming firmware upgrade file, the printer found that the incoming firmware file was too large. This may be because the wrong file was sent, or there was an error in the software which produced the file.
Source: line 150 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While processing an incoming firmware upgrade file, the printer failed to save the new firmware file into flash storage. This may be due to an SPI comms error between the processor and the flash device, or a faulty flash device.
Source: line 172 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While attempting to verify a new firmware upgrade file was successfully saved to flash memory, the printer failed to allocate enough memory for the verification process. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 193 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While attempting to verify a new firmware upgrade file was successfully saved to flash memory, the printer failed to read the programmed file back from the flash device. This may be due to faulty SPI comms between the processor and the flash device, or a faulty flash device.
Source: line 208 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While attempting to verify a new firmware upgrade file was successfully saved to flash memory, the printer found that the data read back from flash didn't match the data written. This may be due to faulty SPI comms between the processor and the flash device, or a faulty flash device.
Source: line 226 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While attempting to update the printer's identity information following a firmware upgrade, the printer was unable to save the new identity information onto the SD card. This may be due to faulty SPI comms between the processor and the flash device, or a faulty flash device.
Source: line 249 of ./nxd/Optima/firmware.c (scope: update_firmware)
Reason: While attempting to update the printer firmware using the package manager, the printer was unable to open the zip archive. This may be due to a corrupt zip archive.
Source: line 220 of ./nxd/Optima/update_pkg.c (scope: update_package)
Reason: While attempting to update the printer firmware using the package manager, the printer was unable to find the package manifest. This may be due to a corrupt or invalid zip archive.
Source: line 236 of ./nxd/Optima/update_pkg.c (scope: update_package)
Reason: While attempting to update the printer firmware using the package manager, the printer failed to parse the package manifest. This may be due to a corrupt or invalid zip archive.
Source: line 259 of ./nxd/Optima/update_pkg.c (scope: update_package)
Reason: While attempting to update the printer firmware using the package manager, the printer failed to extract the firmware file. This may be due to a corrupt or invalid zip archive.
Source: line 306 of ./nxd/Optima/update_pkg.c (scope: update_package)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Holokote update failure |
Reason: While processing an incoming HoloKote upgrade file, the printer failed to save the new HoloKote file onto the card. This may be due to a faulty SD card.
Source: line 322 of ./nxd/Optima/holokote.c (scope: do_update)
Reason: While attempting to verify a new HoloKote upgrade file was successfully saved to the SD card, the printer failed to allocate enough memory for the verification process. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 315 of ./nxd/Optima/holokote.c (scope: do_update)
Reason: While attempting to verify a new HoloKote upgrade file was successfully saved to the SD card, the printer failed to read the programmed file back from the SD card. This may be due to a faulty SD card.
Source: line 303 of ./nxd/Optima/holokote.c (scope: do_update)
Reason: While attempting to verify a new HoloKote upgrade file was successfully saved to the SD card, the printer found that the data read back from the SD card didn't match the data written. This may be due to a faulty SD card.
Source: line 295 of ./nxd/Optima/holokote.c (scope: do_update)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Capability update failure. |
Reason: While updating the printer's capabilities during boot-up, the printer failed to save the printer's identity information to the SD card. This may be because the SD card is not plugged in correctly, or the SD card has developed a fault.
Source: line 145 of ./nxd/Optima/capabilities.c (scope: init_capabilities)
Reason: While processing an incoming capability upgrade file, the printer failed to update the printer's identity information on the SD card. This may be because the SD card is not plugged in correctly, or the SD card has developed a fault.
Source: line 205 of ./nxd/Optima/capabilities.c (scope: update_capabilities)
Reason: While processing an incoming capability upgrade file, the printer was unable to write the new file to the SD card. This may be because the SD card is not plugged in correctly, or the SD card has developed a fault.
Source: line 240 of ./nxd/Optima/capabilities.c (scope: save_upgrade_file)
Reason: While processing an incoming capability upgrade file, the printer was unable to close the new file on the SD card after writing its contents. This may be due to a firmware bug, or a problem with the SD card.
Source: line 250 of ./nxd/Optima/capabilities.c (scope: save_upgrade_file)
Reason: While processing an incoming capability upgrade file, the printer failed to clear an upgrade slot on the SD card as requested by the incoming file. This may be because the SD card is not plugged in correctly, or the SD card has developed a fault.
Source: line 283 of ./nxd/Optima/capabilities.c (scope: delete_upgrade_file)
Reason: While updating the printer's capabilities during boot-up, the printer was unable to read an installed upgrade file from the SD card. This may be because the file was not installed correctly, or the data on the SD card has become corrupted. Reinstalling the upgrade may help.
Source: line 362 of ./nxd/Optima/capabilities.c (scope: apply_upgrade_if_present)
Reason: While updating the printer's capabilities during boot-up, the printer was unable to allocate a buffer for reading an installed upgrade file from the SD card. This may be because there are too many active jobs in the printer at the moment.
Source: line 371 of ./nxd/Optima/capabilities.c (scope: apply_upgrade_if_present)
Reason: While updating the printer's capabilities during boot-up, the printer found that an installed upgrade file had an invalid size. This may be because the file was not installed correctly, or the data on the SD card has become corrupted. Reinstalling the upgrade may help.
Source: line 380 of ./nxd/Optima/capabilities.c (scope: apply_upgrade_if_present)
Reason: While updating the printer's capabilities during boot-up, the printer failed to close an upgrade file on the SD card after using it. This may be because the SD card is not plugged in correctly, or the SD card has developed a fault.
Source: line 390 of ./nxd/Optima/capabilities.c (scope: apply_upgrade_if_present)
Reason: While processing an incoming capability upgrade file, the printer found that the incoming file data was not of the correct format. This may be because the wrong file was sent, the file has become corrupted, or there was an error in the software which produced the file.
Source: line 435 of ./nxd/Optima/capabilities.c (scope: determine_capability_changes)
Reason: While processing an incoming capability upgrade file, the printer failed to allocate memory for decompressing the file's payload. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 448 of ./nxd/Optima/capabilities.c (scope: determine_capability_changes)
Reason: While processing an incoming capability upgrade file, the printer found that the incoming file was not licensed for this printer. This is probably due to the wrong file being sent, but could also indicate an error in the process which produced the file.
Source: line 500 of ./nxd/Optima/capabilities.c (scope: find_and_run_script)
Reason: While processing an incoming capability upgrade file, the printer found that the incoming file data was not of the correct format. This may be because there was an error in the software which produced the file.
Source: line 509 of ./nxd/Optima/capabilities.c (scope: find_and_run_script)
Reason: While processing an incoming capability upgrade file, the printer found that the incoming file contained unrecognised commands. This may be because the file was produced for printers having a different firmware version, but could also indicate that there was an error in the software which produced the file.
Source: line 557 of ./nxd/Optima/capabilities.c (scope: run_script)
Reason: While processing an incoming capability upgrade file, the printer found that the incoming file was attempting to activate an unrecognised capability. This may be because the file was produced for printers having a different firmware version, but could also indicate that there was an error in the software which produced the file.
Source: line 571 of ./nxd/Optima/capabilities.c (scope: run_script)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | HoloKote verification failure. |
Reason: While processing a HoloKote file, the printer found that the file data was not of the correct format. This may be because the wrong file was sent, the file has become corrupted, or there was an error in the software which produced the file.
Source: line 539 of ./nxd/Optima/holokote.c (scope: decompress_and_perform_checks)
Reason: While processing a HoloKote file, the printer failed to allocate memory for decompressing the file. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 526 of ./nxd/Optima/holokote.c (scope: decompress_and_perform_checks)
Reason: While processing a HoloKote file, the printer found that the file was not licensed for this printer. This is probably due to the wrong file being sent, but could also indicate an error in the process which produced the file.
Source: line 570 of ./nxd/Optima/holokote.c (scope: decompress_and_perform_checks)
Reason: While processing a HoloKote file, the printer found that the unique key did not match the value cached during original installation. This may be because of a failed installation, in which case reinstalling the HoloKote should resolve the problem.
Source: line 552 of ./nxd/Optima/holokote.c (scope: decompress_and_perform_checks)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | HoloKote slot empty. |
Reason: While attempting to retrieve a HoloKote file from the SD card, the printer was unable to read the SD card data. This is probably because the slot specified has no HoloKote bitmap installed, but could also be due to a fault with the SD card hardware.
Source: line 388 of ./nxd/Optima/holokote.c (scope: do_retrieve)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Feature unavailable |
Reason: The printer received a mag read job, but the printer has no detectable mag encoder module fitted. Either the job was sent to the wrong printer, or the printer has a mag module fitted which cannot be detected due to a hardware fault, or the printer has been set up as the wrong model.
Source: line 34 of ./print_engine/src/job_handlers/job_mag_read_handler.cpp (scope: set_job_data)
Reason: While validating the print options at the start of a print job, the printer determined that the job required double-sided printing, yet the printer was a single-sided model. This might be because the wrong options were selected in the driver, or the job was sent to the wrong printer.
Source: line 828 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: While validating the print options at the start of a print job, the printer determined that the job required 600 dpi printing, yet the printer was a 300 dpi model. This might be because the job was sent to the wrong printer.
Source: line 843 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: The printer was requested to carry out an encoder soak test, but could not detect an encoder module. This is possibly because either the encoder module is not fitted correctly, or is faulty, or the connecting cables are faulty.
Source: line 349 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: pre_soak_encoder)
Reason: While attempting to install a new custom logo file, the printer failed to perform the operation. This operation is only supported in factory mode.
Source: line 151 of ./nxd/Optima/customisation.c (scope: update_logo)
Reason: While attempting to install a new custom splash screen, the printer failed to perform the operation. This operation is only supported in factory mode.
Source: line 230 of ./nxd/Optima/customisation.c (scope: update_splash_screen)
Reason: While attempting to program RO_NETWORK data, the printer failed to perform the operation. This operation is only supported in factory mode.
Source: line 375 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to program RO_IDENTITY data, the printer failed to perform the operation. This operation is only supported in factory or dealer mode.
Source: line 430 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: The printer was requested to carry out a chip soak test, but could not detect a chip encoder module. This is possibly because either the encoder module is not fitted correctly, or is faulty, or the connecting cables are faulty.
Source: line 647 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: pre_soak_chip)
Reason: While attempting to install a new custom string file, the printer failed to perform the operation. This operation is only supported in dealer or factory mode.
Source: line 892 of ./nxd/Optima/customisation.c (scope: update_strings)
Reason: While attempting to program DAT_RO_AUTH data, the printer failed to perform the operation. This operation is only supported in factory mode.
Source: line 481 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to reset the printer to factory default settings, the printer detected that it was not in factory mode and refused to carry out the request.
Source: line 1207 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Out of cards |
Reason: While trying to feed a new card from the input hopper to the point where it blocks the feed sensor, it took too many attempts to extract a card. This could be because the hopper was empty, or the card feed motor was not functioning correctly, or the feed opto sensor was faulty.
Source: line 1892 of ./print_engine/src/media/card_ctrl.cpp (scope: from_source_to_feed_sensor)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Card jam. Open door for more options. |
Reason: While feeding a new card from the hopper, and having already extracted the card far enough for it to block the feed sensor, the printer tried to feed the card further forwards to block the print position sensor. However, it took too long for the print position sensor to become blocked. This could be because the card was physically obstructed, or the card drive stepper motor was not functioning correctly, or the print position sensor was faulty.
Source: line 1953 of ./print_engine/src/media/card_ctrl.cpp (scope: from_feed_sensor_to_transfer_standby)
Reason: While trying to feed a card from the heated roller to the transfer standby position (where the card is over the print position sensor), it took too long for the card to block the print position opto sensor. This is probably because either there was a physical obstruction, or the card drive motor was not functioning correctly, or the print position sensor was faulty.
Source: line 1086 of ./print_engine/src/media/card_ctrl.cpp (scope: from_heated_roller_to_transfer_standby)
Reason: While trying to feed a card from the flip standby position (where the leading edge of the card is near the eject sensor) to the transfer standby position (where the card is over the print position sensor), it took too long for the card to block the print position opto sensor. This is probably either because there was a physical obstruction, or the card drive motor was not functioning correctly, or the print position sensor was faulty.
Source: line 1132 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_transfer_standby)
Reason: While trying to move the card from the transfer standby position (where the card is over the print position sensor) to the heated roller, it took too long for the print position opto sensor to become unblocked. This is probably because either there was a physical obstruction, or the card driver motor was not functioning correctly, or the print position sensor was faulty.
Source: line 1178 of ./print_engine/src/media/card_ctrl.cpp (scope: from_transfer_standby_to_heated_roller)
Reason: While trying to feed a card from the flipper to the encoder, it took too long for the card to block the encoder unit's card opto sensor. This may be because of a physical obstruction, the flipper's card drive motor not functioning correctly, or a faulty card opto sensor in the encoder unit.
Source: line 1311 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_to_combined_encoder_unit)
Reason: While trying to feed a card from the transfer standby position (where the card is over the print position sensor) to the flip standby position (where the leading edge of the card is by the eject sensor), it took too long for the eject opto sensor to become blocked. The printer attempted to recover by moving the card back to the feed opto sensor, but it then took too long for the feed sensor to become blocked. This is possibly because there is a physical obstruction, or the card is slipping on the rollers, or the card drive motor is not functioning correctly, or there is a problem with one or both of the feed and eject sensors.
Source: line 1246 of ./print_engine/src/media/card_ctrl.cpp (scope: from_transfer_standby_to_flip_standby)
Reason: While trying to move the card from the encoder unit to the flip standby position (where the card edge is by the eject sensor), and having pulled the card into the flipper from the encoder and rotated the flipper by 90 degrees, the printer attempted to feed the card from the flipper to the flip standby position. However, it took too long for the eject sensor to become blocked. This is possibly because there was a physical obstruction blocking either the card movement or flipper rotation, or because the eject opto sensor was faulty.
Source: line 1421 of ./print_engine/src/media/card_ctrl.cpp (scope: from_combined_encoder_unit_to_flip_standby)
Reason: While trying to move the card from the encoder unit to the flip standby position (where the card edge is by the eject sensor), and having pulled the card into the flipper from the encoder and rotated the flipper by 90 degrees, and also having fed the card to the point where the eject sensor was blocked, the printer attempted to continue feeding the card until the eject sensor became unblocked. However, it took too long for the eject sensor to become unblocked. This is possibly because either there was a physical obstruction, or the eject opto sensor was faulty, or the main card drive motor was not functioning correctly.
Source: line 1452 of ./print_engine/src/media/card_ctrl.cpp (scope: from_combined_encoder_unit_to_flip_standby)
Reason: While about to move the card from the flip standby position (where the card's leading edge is by the eject sensor) to the flipper, the printer detected that the eject sensor was blocked. To ensure the flipper could be rotated safely, the printer tried to drive the card backwards to clear the eject sensor. However, it took too long for the eject sensor to become unblocked. This could be because either the card was physically obstructed, the card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1489 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_flip)
Reason: While trying to move the card from the flip standby position (where the card's leading edge is by the eject sensor) to the flipper, the printer tried to drive the card forwards to the point where it just blocked the eject sensor. However, it took too long for the eject sensor to become blocked. This could be because either the card was physically obstructed, the card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1525 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_flip)
Reason: While trying to move the card from the flip standby position (where the card's leading edge is by the eject sensor) to the flipper, and having already moved the card forwards to the point where it blocked the eject sensor, the printer tried to keep driving the card into the flipper until the eject sensor became unblocked. However, it took too long for the eject sensor to become unblocked. This could be because either the card was physically obstructed, the card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1554 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_flip)
Reason: While trying to move the card from the flipper to the flip standby position (where the front edge of the card is by the eject sensor), the printer attempted to drive the card out of the flipper until the eject sensor became blocked. However, it took too long for the eject sensor to become blocked. This could be because the card was obstructed, or the flipper was misaligned, or the flipper card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1608 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_to_flip_standby)
Reason: While trying to move the card from the flipper to the flip standby position (where the front edge of the card is by the eject sensor), and having driven the card out of the flipper to th epoint where the eject sensor became blocked, the printer tried to drive the card to the point where the eject sensor became unblocked again. However, it took too long for the eject sensor to become unblocked. This may be because the card was physically obstructed, or the main card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1638 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_to_flip_standby)
Reason: While trying to move the card from the post transfer position (where the card is over the eject sensor but also partly in the flipper) to the flip standby position (where the front edge of the card is by the eject sensor), the printer tried to drive the card out of the flipper until the eject sensor became unblocked. However, it took too long for the eject sensor to become unblocked. This could be because the card was physically obstructed, or the card drive motor was not functioning correctly, or the eject sensor is faulty.
Source: line 1678 of ./print_engine/src/media/card_ctrl.cpp (scope: from_post_transfer_to_flip_standby)
Reason: While trying to move the card from the post transfer position (where the card is over the eject sensor but also partly in the flipper) to the flip standby position (where the front edge of the card is by the eject sensor) with the flip mechanism in the upside-down orientation (e.g. from just having rotated a card), the printer tried to drive the card out of the flipper until the eject sensor became unblocked. However, it took too long for the eject sensor to become unblocked. This could be because the card was physically obstructed, or the card drive motor was not functioning correctly, or the eject sensor is faulty.
Source: line 1719 of ./print_engine/src/media/card_ctrl.cpp (scope: from_post_transfer_to_flip_standby_upside_down)
Reason: While trying to move the card from the post transfer position (where the card is over the eject sensor but also partly in the flipper) to the flip mechanism, the printer first tried to move the card forwards until it blocked the eject sensor. However, it took too long for the eject sensor to become blocked. This could be because the card was obstructed, or the card drive motor was not functioning correctly, or the eject sensor was faulty.
Source: line 1754 of ./print_engine/src/media/card_ctrl.cpp (scope: from_post_transfer_to_flip)
Reason: While trying to move the card from the post transfer position (where the card is over the eject sensor but also partly in the flipper) to the flip mechanism, and having reached the point where the card had moved forwards to block the eject sensor, the printer tried to drive the card further forwards into the flipper. However, it took too long for the eject sensor to become unblocked. This may be because the card was obstructed, or the main card drive motor was not functioning correctly, or the flipper card drive motor was not functioning correctly, or the flipper was misaligned, or the eject sensor was faulty.
Source: line 1787 of ./print_engine/src/media/card_ctrl.cpp (scope: from_post_transfer_to_flip)
Reason: The printer was attempting to clear the card feed sensor by driving the card towards the input hopper end of the printer (this is in order to recover from a failed or aborted feed attempt). However, it took too long for the card feed sensor to become unblocked. This could be because either the card was physically obstructed, or the card feed motor was not functioning correctly, or the card feed sensor was faulty.
Source: line 1996 of ./print_engine/src/media/card_ctrl.cpp (scope: from_feed_sensor_to_source)
Reason: The printer was attempting to eject a card out of the input hopper end of the printer, to clear a card jam after a failed attempt at feeding in a card. However, it took too long for the card feed sensor to become unblocked. This could be because either the cleaning was physically obstructed, or the card feed motor was not functioning correctly, or the card feed sensor was faulty.
Source: line 2032 of ./print_engine/src/media/card_ctrl.cpp (scope: from_cleaning_roller_to_source)
Reason: While trying to feed a card from the transfer standby position (where the card is over the print position sensor) to the flip standby position (where the leading edge of the card is by the eject sensor), it took too long for the eject opto sensor to become blocked. The printer attempted to recover by moving the card back to the feed sensor and having a second go at moving forwards to the eject sensor. However, on the second attempt it again took too long for the eject opto sensor to become blocked.This is possibly because there is a physical obstruction, or the card is slipping on the rollers, or the card drive motor is not functioning correctly, or the eject sensor is faulty.
Source: line 1275 of ./print_engine/src/media/card_ctrl.cpp (scope: from_transfer_standby_to_flip_standby)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Flipper card jam |
Reason: While initialising the flipper, the printer attempted to to rotate the flipper clockwise until the flipper opto sensor unblocked, and it took too long for that sensor to unblock. This is probably due to either a faulty flipper opto sensor, the flip rotation motor not functioning correctly, or an obstruction preventing free rotation of the flipper.
Source: line 119 of ./print_engine/src/hal/flipper.cpp (scope: initialise)
Reason: While initialising the flipper, having already unblocked the flipper opto sensor, the printer tried to rotate the flipper clockwise until the flipper opto sensor was blocked. However, it too long for that sensor to become blocked. This is probably due to either a faulty flipper opto sensor, the flip rotation motor not functioning correctly, or an obstruction preventing free rotation of the flipper.
Source: line 139 of ./print_engine/src/hal/flipper.cpp (scope: initialise)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Invalid job option |
Reason: The printer was sent a request to move a card, but the selected card destination was invalid. This may be because the job data was corrupted in transit, or because the job data was sent by a faulty application, or because the printer firmware needs to be updated to a version recognising the given destination.
Source: line 30 of ./print_engine/src/job_handlers/job_move_card_handler.cpp (scope: set_job_data)
Reason: While validating the mag encoding options at the start of a print job, the printer found that the requested mag coercivity was of an unrecognised type. This is possibly because either the job has been corrupted, or the printer firmware needs to be updated to handle the requested coercivity.
Source: line 922 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_mag_data)
Reason: While validating the mag encoding options at the start of a print job, the printer found that the requested mag encoding direction was of an unrecognised type. This is possibly because either the job has been corrupted, or the printer firmware needs to be updated to handle the requested encoding direction.
Source: line 933 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_mag_data)
Reason: While attempting to install a new HoloKote file, the printer determined that the requested HoloKot slot number was invalid. This could be due to a corrupted job, or could indicate that the firmware needs to be updated to support additional slots.
Source: line 233 of ./nxd/Optima/holokote.c (scope: do_update)
Reason: While attempting to retrieve an installed HoloKote file, the printer determined that the requested HoloKot slot number was invalid. This could be due to a corrupted job, or could indicate that the firmware needs to be updated to support additional slots.
Source: line 348 of ./nxd/Optima/holokote.c (scope: do_retrieve)
Reason: While attempting to set the RW_PRINT configuration, the printer detected invalid data. This could be due to a corrupted job, or could be due to a problem with the tool being used to configure the printer.
Source: line 304 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to set the RW_TRANSFER configuration, the printer detected invalid data. This could be due to a corrupted job, or could be due to a problem with the tool being used to configure the printer.
Source: line 326 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to set the RO_IDENTITY configuration, the printer detected invalid data. This could be due to a corrupted job, or could be due to a problem with the tool being used to configure the printer.
Source: line 396 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to set the RW_NETWORK configuration, the printer detected invalid data. This could be due to a corrupted job, or could be due to a problem with the tool being used to configure the printer.
Source: line 344 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
Reason: While attempting to set the RO_NETWORK configuration, the printer detected invalid data. This could be due to a corrupted job, or could be due to a problem with the tool being used to configure the printer.
Source: line 369 of ./nxd/Optima/cmd_exec.c (scope: config_queue_handler)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Heated roller timeout |
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Heated roller cam error |
Reason: While carrying out a printer soak test, the printer was unable to lower the heated roller. This is possibly either because the heated roller cam opto sensor is faulty, or the cam motor is not functioning correctly, or the cam was physically obstructed.
Source: line 578 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: soak_printer)
Reason: During a print job the printer was preparing to retransfer onto the card, but could not raise the heated roller. This is possibly because either the heated roller cam motor is faulty, or the heated roller cam sensor is faulty, or something is obstructing the movement of the heated roller cam.
Source: line 220 of ./print_engine/src/job_handlers/stages/stage_transfer.cpp (scope: prepare_to_transfer)
Reason: During a print job the printer was just finishing retransferring onto the card, but could not lower the heated roller. This is possibly because either the heated roller cam motor is faulty, or the heated roller cam sensor is faulty, or something is obstructing the movement of the heated roller cam.
Source: line 339 of ./print_engine/src/job_handlers/stages/stage_transfer.cpp (scope: transfer)
Reason: While initialising the print engine, the printer was unable to reset the heated roller cam to the open position. This is possibly due to a physical obstruction, the cam motor not functioning correctly, or a faulty cam opto sensor.
Source: line 179 of ./print_engine/src/print_engine.cpp (scope: print_engine_mech_init)
Reason: Towards the end of a single-sided print job the printer was preparing to flatten the card, but could not raise the heated roller. This is possibly because either the heated roller cam motor is faulty, or the heated roller cam sensor is faulty, or something is obstructing the movement of the heated roller cam.
Source: line 155 of ./print_engine/src/job_handlers/stages/stage_flatten.cpp (scope: prepare_to_flatten)
Reason: Towards the end of a single-sided print job the printer was just finishing flattening the card, but could not lower the heated roller. This is possibly because either the heated roller cam motor is faulty, or the heated roller cam sensor is faulty, or something is obstructing the movement of the heated roller cam.
Source: line 264 of ./print_engine/src/job_handlers/stages/stage_flatten.cpp (scope: flatten)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Print roller cam error |
Reason: During a print job, while just about to print one of the colour planes onto the transfer film, the printer was unable to move the print roller to the closed position. This may be because the print roller cam mechanism has been obstructed, or the cam opto sensor is faulty, or the cam motor is not functioning correctly.
Source: line 841 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: adjust_film_and_close_print_roller)
Reason: While initialising the print engine, the printer was unable to reset the print roller cam to the open position. This is possibly due to a physical obstruction, the cam motor not functioning correctly, or a faulty cam opto sensor.
Source: line 190 of ./print_engine/src/print_engine.cpp (scope: print_engine_mech_init)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Dye film panel timeout |
Reason: While attempting to move the dye film to a particular panel, the printer was unable to find the requested panel. This could be because the film movement is being obstructed, or there is a problem with one or both of the film motors, or the dye panel sensor/LED is faulty.
Source: line 137 of ./print_engine/src/media/dye_ctrl.cpp (scope: set_position)
Reason: While attempting to move the dye film on to the next panel in the panel sequence, it took too long for the required panel to be detected by the dye panel sensor. This is possibly because either the dye film movement was physically obstructed, the dye film had run out and gone beyond the end-of-film marker tape, one or both of the dye motors was not functioning correctly, or the dye panel sensor/LED was faulty.
Source: line 243 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_next_panel)
Reason: While attempting to move the dye film on to the next panel in the panel sequence, the printer found the leading edge of the required panel and then tried to move the film further on for a small distance. However, it took too long for the required number of tacho sensor transitions to be detected from the dye film take-up motor. This is possibly because either the dye film movement was physically obstructed, the dye film had run out and gone beyond the end-of-film marker tape, one or both of the dye motors was not functioning correctly, or the dye film take-up motor's tacho sensor was faulty.
Source: line 269 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_next_panel)
Reason: While attempting to move the dye film on to the previous panel in the panel sequence, it took too long for the required panel to be detected by the dye panel sensor. This is possibly because either the dye film movement was physically obstructed, the dye film had run out and gone beyond the end-of-film marker tape, one or both of the dye motors was not functioning correctly, or the dye panel sensor/LED was faulty.
Source: line 382 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_previous_panel)
Reason: While attempting to move the dye film on to the previous panel in the panel sequence, the printer found the leading edge of the required panel and then tried to move the film further on for a small distance. However, it took too long for the required number of tacho sensor transitions to be detected from the dye film take-up motor. This is possibly because either the dye film movement was physically obstructed, the dye film had run out and gone beyond the end-of-film marker tape, one or both of the dye motors was not functioning correctly, or the dye film take-up motor's tacho sensor was faulty.
Source: line 410 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_previous_panel)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Dye film panel unavailable |
Reason: While validating the print options at the start of a print job, the printer determined that the print job required a colour or security feature that was not available with the currently fitted dye film. This is probably because either the wrong type of film is fitted, or the wrong driver options were selected.
Source: line 891 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: While attempting to move the dye film to a particular panel, the printer determined that the currently fitted film does not have the required panel type. This could be because the wrong film was fitted, or the wrong options were selected for the current job.
Source: line 115 of ./print_engine/src/media/dye_ctrl.cpp (scope: set_position)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Transfer film panel timeout |
Reason: During a print job, while printing onto the transfer film, the printer was unable to detect the index mark on the transfer film. This may be because the transfer film is beyond the end-of-film marker tape (i.e. has run out), or the index sensor needs to be recalibrated, or the index sensor is faulty, or the film cannot move due to an obstruction or motor fault.
Source: line 950 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: wait_for_index_mark)
Reason: While waiting for the transfer index mark before stopping the transfer film, it took too long for the printer to detect the leading edge of the index mark. This is possibly because either the transfer film was physically obstructed, one or both of the transfer film motors was not functioning correctly, the transfer film had run out and gone beyond the end-of-film marker tape, or the transfer index sensor/LED was faulty.
Source: line 1211 of ./print_engine/src/media/transfer_ctrl.cpp (scope: get_tick_count)
Reason: While waiting for the transfer index mark before stopping the transfer film, it took too long for the printer to detect the trailing edge of the index mark. This is possibly because either the transfer film was physically obstructed, one or both of the transfer film motors was not functioning correctly, or the transfer index sensor/LED was faulty.
Source: line 1273 of ./print_engine/src/media/transfer_ctrl.cpp (scope: PRINTF)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Mag head home timeout |
Reason: While attempting to return the mag head to the home position, the printer first had to clear the head home opto sensor by moving the mag head a short distance towards the front of the printer. However, the head took too long to clear the head home opto sensor. This may be because there was a physical obstruction preventing the head from moving, or the head stepper motor is not working properly, or the head opto sensor is faulty.
Source: line 301 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_home)
Reason: While attempting to return the mag head to the home position by moving the mag head towards the rear of the printer, it took too long for the mag head to trigger the head home opto sensor. This may be because there was a physical obstruction preventing the head from moving, or the head stepper motor is not working properly, or the head opto sensor is faulty.
Source: line 340 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_home)
Reason: While attempting to return the mag head to the standby position near the front end of print engine, the printer first had to clear the head home opto sensor by moving the mag head towards the front of the printer. However, the head took too long to clear the head home opto sensor. This may be because there was a physical obstruction preventing the head from moving, or the head stepper motor is not working properly, or the head opto sensor is faulty.
Source: line 390 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_standby)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Mag head move timeout. |
Reason: While attempting to encode a mag card in the forwards direction, the printer had to wait for the mag head to unblock the head home opto sensor. However, the head took too long to do so. This may be because there was a physical obstruction preventing the head from moving, or the head stepper motor is not working properly, or the head opto sensor is faulty.
Source: line 810 of ./print_engine/src/hal/encoder.cpp (scope: wait_for_start_of_write_region)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Mag verify |
Reason: The printer attempted to read data from a mag card in order to verify an encode operation, but no data was found, not even leading zeroes. This could mean that the card was loaded in the wrong orientation, the wrong type of card was used, the mag PCB was faulty, the head stepper motor was not functioning properly, or the head was physically obstructed.
Source: line 208 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: verify_card)
Reason: The printer attempted to read data from a mag card in order to verify an encode operation, but no data was found beyond the leading zeroes. This could mean that the mag PCB was faulty, the head stepper motor was not functioning properly, or the head was physically obstructed.
Source: line 260 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: compare_track_data)
Reason: The printer attempted to read data from a mag card in order to verify an encode operation, but less data was read back than was encoded. This could mean that the mag PCB was faulty, the head stepper motor was not functioning properly, or the head was physically obstructed.
Source: line 290 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: compare_track_data)
Reason: The printer attempted to read data from a mag card in order to verify an encode operation, but the data read back did not match the data which was supposed to be encoded. This could mean that the mag PCB was faulty, the head stepper motor was not functioning properly, the head movement was disrupted, or the card was not properly inserted into the encoder.
Source: line 308 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: compare_track_data)
Reason: The printer attempted to read data from a mag card in order to verify an encode operation, but more data was read back than was encoded. This could mean that the mag PCB was faulty, the head stepper motor was not functioning properly, or the head was physically obstructed.
Source: line 327 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: compare_track_data)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Cover open. |
Reason: The printer was about to start a print job, and detected that the cover was open. If the cover is not in fact open, it may be that the cover opto sensor is faulty.
Source: line 573 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: execute_job_delegate)
Reason: While carrying out a printer soak test, the printer detected that the cover had been opened. If the cover is not in fact open, the cover opto sensor may be faulty.
Source: line 549 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: soak_printer)
Reason: Just after encoding a mag card, the printer detected that the cover was open. If the cover was not in fact open, this could mean that the cover sensor was faulty.
Source: line 106 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: encode_and_verify_card)
Reason: Just after verifying a mag card, the printer detected that the cover was open. If the cover was not in fact open, this could mean that the cover sensor was faulty.
Source: line 130 of ./print_engine/src/job_handlers/stages/stage_encode.cpp (scope: encode_and_verify_card)
Reason: During a print job, while just about to print one of the colour planes onto the transfer film, the printer detected that the cover had been opened and had to stop. If the cover was not in fact opened, it may be that the cover opto sensor was faulty.
Source: line 666 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: print_panel)
Reason: During a print job, while in the process of printing one of the colour planes onto the transfer film, the printer detected that the cover had been opened and had to stop. If the cover was not in fact opened, it may be that the cover opto sensor was faulty.
Source: line 1002 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: main_print_loop)
Reason: During a print job the printer was just finishing retransferring onto the card, but detected that the cover had been opened. If the cover is not in fact open, it may be that the cover opto sensor is faulty.
Source: line 362 of ./print_engine/src/job_handlers/stages/stage_transfer.cpp (scope: transfer)
Reason: During a print job, while waiting for the heated roller to reach its target temperature, the printer detected that the cover was opened.
Source: line 54 of ./print_engine/src/job_handlers/stages/stage_wait_for_heated_roller.cpp (scope: action)
Reason: While attempting to move the dye film on to the next panel in the panel sequence, the printer detected that the cover had been opened. If the cover was not in fact open, it may be that the cover opto sensor was faulty.
Source: line 234 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_next_panel)
Reason: While attempting to move the dye film on to the previous panel in the panel sequence, the printer detected that the cover had been opened. If the cover was not in fact open, it may be that the cover opto sensor was faulty.
Source: line 373 of ./print_engine/src/media/dye_ctrl.cpp (scope: go_to_previous_panel)
Reason: While waiting for the transfer index mark before stopping the transfer film, the printer detected that the cover was opened. If the cover was not in fact opened, it may be that the cover opto sensor was faulty.
Source: line 1224 of ./print_engine/src/media/transfer_ctrl.cpp (scope: get_tick_count)
Reason: Just after positioning the transfer film using an index mark, the printer detected that the cover was opened. If the cover was not in fact opened, it may be that the cover opto sensor was faulty.
Source: line 1326 of ./print_engine/src/media/transfer_ctrl.cpp (scope: PRINTF)
Reason: During a print job, while waiting for the printhead to reach its target temperature, the printer detected that the cover was opened.
Source: line 90 of ./print_engine/src/job_handlers/stages/stage_wait_for_printhead.cpp (scope: action)
Reason: While about to begin a soak routine, the printer detected that the cover was open. If the cover is not in fact open, it could be that the cover opto sensor is faulty.
Source: line 69 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: execute_job_delegate)
Reason: While carrying out a soak routine, the printer detected that the cover was open. If the cover is not in fact open, it could be that the cover opto sensor is faulty.
Source: line 109 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: execute_job_delegate)
Reason: Towards the end of a single-sided print job the printer was just finishing flattening the card, but detected that the cover had been opened. If the cover is not in fact open, it may be that the cover opto sensor is faulty.
Source: line 286 of ./print_engine/src/job_handlers/stages/stage_flatten.cpp (scope: flatten)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Transfer film expired. |
Reason: At the start of a print job, the printer determined that the transfer film currently fitted had run out of prints. A new roll of transfer film should be fitted before retrying the print job.
Source: line 101 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
Reason: While initialising the print engine, the printer detected that the transfer film RFID tag had run out of prints. This is probably because the roll of transfer film has run out and needs replacing.
Source: line 348 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: While waiting for the transfer index mark before stopping the transfer film, the printer detected the end-of-film marker tape. If the printer is mistaken and there is more film left, it may be that the transfer film was physically obstructed, one or both of the transfer film motors was not functioning correctly, or the transfer index sensor/LED was faulty.
Source: line 1304 of ./print_engine/src/media/transfer_ctrl.cpp (scope: PRINTF)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Dye film expired. |
Reason: At the start of a print job, the printer determined that the dye film currently fitted had run out of prints. A new roll of dye film should be fitted before retrying the print job.
Source: line 86 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Both films expired. |
Reason: At the start of a print job, the printer determined that the dye film and transfer film currently fitted had both run out of prints. New rolls of film should be fitted before retrying the print job.
Source: line 79 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Index LED calibration failed. |
Reason: While attempting to calibrate the transfer index LED, the printer found that the required LED brightness setting was either too low or too high to be considered trustworthy. This could either be due to a faulty or incorrectly fitted transfer index sensor or LED PCB. It could also be due to something physically obscuring the transfer index sensor/LED during calibration.
Source: line 578 of ./print_engine/src/media/transfer_ctrl.cpp (scope: calibrate)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | Yes | SEV_ERROR | Dye LED calibration failed. |
Reason: While attempting to calibrate the dye film LED, the printer found that one of the required LED brightness settings was either too low or too high to be considered trustworthy. This could either be due to a faulty or incorrectly fitted dye sensor or LED PCB. It could also be due to something physically obscuring the dye sensor/LED during calibration.
Source: line 495 of ./print_engine/src/media/dye_ctrl.cpp (scope: calibrate)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Dye film not found. |
Reason: While validating the print options at the start of a print job, the printer determined that film was required, yet no dye film was fitted. If dye film is in fact fitted, it may be that the tag reader hardware is faulty, or that the tag on the dye film is faulty.
Source: line 866 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: Having printed a copy of a card, the printer was attempting to update the counter on the dye film RFID tag but could not detect the dye film RFID tag. This could be because the RFID tag or tag reader hardware is faulty.
Source: line 93 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: While initialising the print engine, the printer was unable to determine what type of dye film is fitted (although it was able to detect an RFID tag with the appropriate application family ID code). This is possibly due to a misprogrammed dye film RFID tag or a mis-matched partner code value.
Source: line 318 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: At the start of a print job, the printer was unable to detect the RFID tag for the dye film. This is probably because no film is fitted, but could also be due to damaged or incorrectly programmed RFID tags, or a fault in the RFID reading hardware.
Source: line 59 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
Reason: While initialising the print engine, the printer was unable to detect the dye film RFID tag. This is possibly because the dye film is not fitted, or there is a problem with the RFID reader hardware.
Source: line 389 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Transfer film not found. |
Reason: While validating the print options at the start of a print job, the printer determined that film was required, yet no transfer film was fitted. If transfer film is in fact fitted, it may be that the tag reader hardware is faulty, or that the tags on the transfer film is faulty.
Source: line 874 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: Having printed a copy of a card, the printer was attempting to update the counter on the transfer film RFID tag but could not detect the transfer film RFID tag. This could be because the RFID tag or tag reader hardware is faulty.
Source: line 82 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: While initialising the print engine, the printer was unable to determine what type of transfer film is fitted (although it was able to detect an RFID tag with the appropriate application family IDcode). This is possibly due to a misprogrammed transfer film RFID tag.
Source: line 334 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: At the start of a print job, the printer was unable to detect the RFID tag for the transfer film. This is probably because no film is fitted, but could also be due to damaged or incorrectly programmed RFID tags, or a fault in the RFID reading hardware.
Source: line 66 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
Reason: While initialising the print engine, the printer was unable to detect the transfer film RFID tag. This is possibly because the transfer film is not fitted, or there is a problem with the RFID reader hardware.
Source: line 381 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | Film is fitted. Please remove. |
Reason: The printer was requested to carry out a printer soak test, but detected that film was fitted. All film should be removed before retrying the soak test.
Source: line 405 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: pre_soak_printer)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | Yes | SEV_ERROR | No film is fitted. |
Reason: While initialising the print engine, the printer was unable to detect either of the film RFID tags. This is possibly because neither roll of film is fitted, or there is a problem with the RFID reader hardware.
Source: line 366 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: While validating the print options at the start of a print job, the printer determined that film was required, yet neither dye nor transfer film was fitted. If film is in fact fitted, it may be that the tag reader hardware is faulty, or that the tags on the film are faulty.
Source: line 858 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: validate_print_options)
Reason: At the start of a print job, the printer was unable to detect the RFID tags for the transfer and dye films. This is probably because no film is fitted, but could also be due to damaged or incorrectly programmed RFID tags, or a fault in the RFID reading hardware.
Source: line 52 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Printhead timeout. |
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL |
Reason: While processing a newly-inserted soak test dongle, the printer failed to open the dongle. This may be because the dongle was programmed incorrectly, was the wrong dongle, was corrupted, or was faulty. It may also be because the firmware needs to be updated to support the data format.
Source: line 1052 of ./nxd/Optima/storage_mgr.c (scope: PRINTF)
Reason: While copying animation frames from the soak test dongle to the internal SD card, the printer was unable to read the animation data from the soak test dongle. This may be because the soak test dongle was not programmed correctly, or was removed during the read process.
Source: line 500 of ./nxd/Optima/storage_mgr.c (scope: copy_file)
Reason: While processing a newly-inserted SD card, the printer found that the SD card data format version was incompatible with the current printer firmware. This may be because the SD card was programmed incorrectly, was the wrong SD card, was corrupted, or was faulty. It may also be because the firmware needs to be updated to support the data format on the card.
Source: line 1003 of ./nxd/Optima/storage_mgr.c (scope: PRINTF)
Reason: The printer was attempting to render printer information onto a card, but the printing configuration could not be read from the SD card. This may be because the SD card was not fitted correctly, or was not programmed correctly, or was faulty.
Source: line 780 of ./print_engine/src/job_handlers/job_print_handler.cpp (scope: generate_printer_info)
Reason: In the control loop which maintains the heated roller temperature, the printer was unable to read the target heated roller temperature from the SD card. This may be because the SD card was not programmed correctly, was not fitted correctly, or was faulty. The printer will select a safe default temperature of 25 degrees Celsius.
Source: line 58 of ./print_engine/src/threads/heated_roller_control_loop.cpp (scope: get_target_temperature_from_configuration)
Reason: The printer was attempting to render printer information onto a card, but the printing configuration could not be read from the SD card. This may be because the SD card was not fitted correctly, or was not programmed correctly, or was faulty.
Source: line 747 of ./print_engine/src/job_handlers/job_test_renderer.cpp (scope: render_test_image_5)
Reason: In the power-saving module of the firmware, the printer was attempting to reactivate the dye and transfer LEDs, but was unable to read the dye and transfer LED calibration settings from the SD card. This is probably because the SD card was either not correctly fitted, not correctly programmed, or faulty.
Source: line 442 of ./print_engine/src/threads/power_saving_loop.cpp (scope: activate_film_leds)
Reason: During a print job the printer was preparing to retransfer onto the card, but could not read the transfer start position from the SD card. This is probably because the SD card is either not programmed, not fitted correctly, or faulty.
Source: line 140 of ./print_engine/src/job_handlers/stages/stage_transfer.cpp (scope: prepare_to_transfer)
Reason: During a print job the printer was attempting to retransfer onto the card, but could not read the transfer card speed and transfer length from the SD card. This is probably because the SD card is either not programmed, not fitted correctly, or faulty.
Source: line 264 of ./print_engine/src/job_handlers/stages/stage_transfer.cpp (scope: transfer)
Reason: At the start of a print job, the printer was unable to read the heated roller target temperature from the SD card. This may be because the SD card is either not programmed, not fitted or faulty.
Source: line 35 of ./print_engine/src/job_handlers/stages/stage_prepare_for_printing.cpp (scope: action)
Reason: During a print job, while preparing to print onto the transfer film, the printer was unable to read the printing configuration from the SD card. This is possibly because the SD card was either unprogrammed, not fitted correctly or faulty.
Source: line 401 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: action)
Reason: Having printed a copy of a card, the printer was attempting to update the printer usage statistics but was unable to read the current values of the statistics from the SD card. This may be because the SD card is either not fitted correctly, not programmed correctly or faulty.
Source: line 105 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: Having printed a copy of a card, the printer was attempting to update the printer cleaning statistics but was unable to read the current values of the statistics from the SD card. This may be because the SD card is either not fitted correctly, not programmed correctly or faulty.
Source: line 132 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: While validating the print options at the start of a print job, the printer was unable to read the printer identity information from the SD card in order to check the job options against the printer's capabilities. This could be because the SD card is either not fitted correctly, not programmed correctly or faulty.
Source: line 110 of ./nxd/Optima/get.c (scope: "C")
Reason: Towards the end of a single-sided print job the printer was preparing to flatten the card, but could not read the transfer start position from the SD card. This is probably because the SD card is either not programmed, not fitted correctly, or faulty.
Source: line 89 of ./print_engine/src/job_handlers/stages/stage_flatten.cpp (scope: prepare_to_flatten)
Reason: Towards the end of a single-sided print job the printer was attempting to flatten the card, but could not read the transfer card speed and transfer length from the SD card. This is probably because the SD card is either not programmed, not fitted correctly, or faulty.
Source: line 196 of ./print_engine/src/job_handlers/stages/stage_flatten.cpp (scope: flatten)
Reason: The printer was attempting to render an internal test image which displays the printing configuration, but the printing configuration could not be read from the SD card. This may be because the SD card was not fitted correctly, or was not programmed correctly, or was faulty.
Source: line 449 of ./print_engine/src/job_handlers/job_test_renderer.cpp (scope: render_test_image_0)
Reason: While attempting to calibrate the dye film LED, the printer was unable to read the current printing configuration from the SD card. This could be because either the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 523 of ./print_engine/src/media/dye_ctrl.cpp (scope: calibrate)
Reason: While attempting to initialise the dye film, the printer was unable to read the dye LED calibration settings from the SD card. This could be because the SD card was not fitted correctly, not programmed correctly or faulty.
Source: line 748 of ./print_engine/src/media/dye_ctrl.cpp (scope: do_initialise_actions)
Reason: While attempting to calibrate the transfer index LED, the printer was unable to read the current printing configuration from the SD card. This could be because either the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 604 of ./print_engine/src/media/transfer_ctrl.cpp (scope: calibrate)
Reason: While attempting to initialise the transfer film, the printer was unable to read the transfer index LED calibration settings from the SD card. This could be because the SD card was not fitted correctly, not programmed correctly or faulty.
Source: line 898 of ./print_engine/src/media/transfer_ctrl.cpp (scope: read_status_store)
Reason: During printer boot-up initialisation, while attempting to check whether the printer needed to be cleaned, the printer was unable to read the cleaning statistics from the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 73 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_cleaning_required)
Reason: During printer boot-up initialisation, while attempting to check whether the printer needed to be cleaned, the printer was unable to read the cleaning configuration from the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 81 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_cleaning_required)
Reason: Having just completed a roller cleaning cycle, the printer attemped to update the cleaning statistics. However, it was unable to read the current statistics from the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 824 of ./print_engine/src/media/card_ctrl.cpp (scope: clean_rollers)
Reason: In the power-saving module of the firmware, the printer was unable to read the power-saving settings from the SD card. This is probably because the SD card was either not correctly fitted, not correctly programmed, or faulty.
Source: line 414 of ./print_engine/src/threads/power_saving_loop.cpp (scope: read_power_saving_settings_from_flash)
Reason: While processing a newly-inserted SD card, the printer found a bootable SD card. This needs to be replaced with a SD card of the correct type.
Source: line 1014 of ./nxd/Optima/storage_mgr.c (scope: PRINTF)
Reason: While processing a newly-inserted upgrade dongle, the printer failed to open the dongle. This may be because the dongle was programmed incorrectly, was the wrong dongle, was corrupted, or was faulty. It may also be because the firmware needs to be updated to support the data format.
Source: line 1071 of ./nxd/Optima/storage_mgr.c (scope: PRINTF)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Failed to write to the SD card. |
Reason: While attempting to update the printer's partner code, the printer was unable to save the updated identity information onto the SD card. This is probably because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 1125 of ./nxd/Optima/peginterface.cpp (scope: userMessageCallback)
Reason: While copying animation frames from the soak test dongle to the internal SD card, the printer was unable to save the animation data to the internal SD card. This may be because the SD card was not formatted correctly, was removed during the save process, or was faulty.
Source: line 489 of ./nxd/Optima/storage_mgr.c (scope: copy_file)
Reason: While copying animation frames from the soak test dongle to the internal SD card, the printer was unable to open the animation file on the SD card. This may be because the SD card was not formatted correctly, was removed during the save process, or was faulty.
Source: line 547 of ./nxd/Optima/storage_mgr.c (scope: copy_file)
Reason: While attempting to install a new PRN file for an internal demo image, the printer failed to save the new PRN file to the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 685 of ./nxd/Optima/customisation.c (scope: update_prn)
Reason: While attempting to install a new PRN file for an internal demo image, the printer failed to open the file on the SD card for writing. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 713 of ./nxd/Optima/customisation.c (scope: update_prn)
Reason: While attempting to install a new PRN file for an internal demo image, the printer failed to save the new PRN button image to the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 764 of ./nxd/Optima/customisation.c (scope: save_prn_btn)
Reason: While attempting to install a new PRN button image for an internal demo image, the printer failed to open the file on the SD card for writing. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 793 of ./nxd/Optima/customisation.c (scope: save_prn_btn)
Reason: At the end of a printer soak test, the printer attempted to update the flag in the printer identity settings indicating that calibration and soak had been completed successfully, but was unable to save the updated printer identity settings to the SD card. This is probably because either the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 619 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: post_soak_printer)
Reason: While attempting to calibrate the dye film LED, the printer was unable to save the new dye LED settings to the SD card. This could be because either the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 513 of ./print_engine/src/media/dye_ctrl.cpp (scope: calibrate)
Reason: While attempting to calibrate the transfer index LED, the printer was unable to save the new transfer index LED settings to the SD card. This could be because either the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 594 of ./print_engine/src/media/transfer_ctrl.cpp (scope: calibrate)
Reason: During printer boot-up initialisation, while attempting to check whether the printer needed to be cleaned, the printer determined that cleaning was required but was unable to save the updated cleaning information to the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 99 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_cleaning_required)
Reason: During printer boot-up initialisation, while attempting to check whether the printer needed to be cleaned, the printer determined that cleaning was not required but was unable to save the updated cleaning information to the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 120 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_cleaning_required)
Reason: Having just completed a roller cleaning cycle, the printer attemped to update the cleaning statistics. However, it was unable to save the updated statistics to the SD card. This is possibly because the SD card is either not fitted correctly, not programmed correctly, or faulty.
Source: line 838 of ./print_engine/src/media/card_ctrl.cpp (scope: clean_rollers)
Reason: Having printed a copy of a card, the printer was attempting to update the printer usage statistics but was unable to write the updated values of the statistics to the SD card. This may be because the SD card is either not fitted correctly, not programmed correctly or faulty.
Source: line 119 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: Having printed a copy of a card, the printer was attempting to update the printer cleaning statistics but was unable to write the updated values of the statistics to the SD card. This may be because the SD card is either not fitted correctly, not programmed correctly or faulty.
Source: line 144 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: action)
Reason: While copying animation frames from the soak test dongle to the internal SD card, the printer was unable to close the animation file on the internal SD card. This may be because the SD card was not formatted correctly, was removed during the save process, or was faulty.
Source: line 533 of ./nxd/Optima/storage_mgr.c (scope: copy_file)
Reason: While attempting to install a new PRN file for an internal demo image, the printer failed to close the new PRN button file. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 781 of ./nxd/Optima/customisation.c (scope: save_prn_btn)
Reason: While attempting to install a new PRN file for an internal demo image, the printer failed to close the new PRN file on the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 702 of ./nxd/Optima/customisation.c (scope: update_prn)
Reason: While attempting to install a new custom logo file, the printer failed to save the new file to the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 114 of ./nxd/Optima/customisation.c (scope: update_logo)
Reason: While attempting to install a new custom logo file, the printer failed to close the file on the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 133 of ./nxd/Optima/customisation.c (scope: update_logo)
Reason: While attempting to install a new custom logo file, the printer failed to open the file on the SD card for writing. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 143 of ./nxd/Optima/customisation.c (scope: update_logo)
Reason: While attempting to install a new custom splash screen, the printer failed to save the new file to the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 193 of ./nxd/Optima/customisation.c (scope: update_splash_screen)
Reason: While attempting to install a new custom splash screen, the printer failed to close the file on the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 212 of ./nxd/Optima/customisation.c (scope: update_splash_screen)
Reason: While attempting to install a new custom splash screen, the printer failed to open the file on the SD card for writing. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 222 of ./nxd/Optima/customisation.c (scope: update_splash_screen)
Reason: While attempting to install a new custom strings file, the printer failed to save the new file to the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 844 of ./nxd/Optima/customisation.c (scope: update_strings)
Reason: While attempting to install a new custom strings file, the printer failed to close the file on the SD card. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 866 of ./nxd/Optima/customisation.c (scope: update_strings)
Reason: While attempting to install a new custom string file, the printer failed to open the file on the SD card for writing. This is probably either due to the SD card not being formatted correctly, or the SD card not being inserted properly, or the SD card being faulty.
Source: line 876 of ./nxd/Optima/customisation.c (scope: update_strings)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | Internal storage media absent. |
Reason: During boot-up initialisation, the printer's internal SD card failed the authentication check. This may be because the SD card was not programmed correctly, or was faulty.
Source: line 282 of ./nxd/main.c (scope: main)
Reason: During boot-up initialisation, the printer's internal SD card was not detected. This may be because the SD card was not fitted correctly, was not programmed correctly, or was faulty.
Source: line 265 of ./nxd/main.c (scope: main)
Reason: While processing an inserted SD card, the printer was unable to read the SD card identity information. This may be because the SD card is faulty.
Source: line 1173 of ./hal/source/sd_card.c (scope: SD_start)
Reason: While processing an inserted SD card, the printer was unable to initialise the processor's SD card controller. This may be because the controller is faulty.
Source: line 1183 of ./hal/source/sd_card.c (scope: SD_start)
Reason: While processing an inserted SD card, the printer found that the SD card was write protected. Either the card's write protect tab is in the locked position, or there is a fault with the SD card, or there is a fault with the SD card reading hardware.
Source: line 1195 of ./hal/source/sd_card.c (scope: SD_start)
Reason: While attempting to process an inserted SD card, the printer found that no SD card was actually present. Either the SD card is missing or not inserted correctly, or there is a fault with the SD card reading hardware.
Source: line 1206 of ./hal/source/sd_card.c (scope: SD_start)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Partner code mismatch |
Reason: While processing a request to reset the printer's partner code to 0 using a partner code dongle, the printer found that the dongle's partner code did not match that of the printer. Therefore, the request was denied.
Source: line 875 of ./nxd/Optima/storage_mgr.c (scope: partner_code_dongle)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Partner code programming dongle is corrupt |
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR |
Reason: While preparing to print a demo card, the printer was unable to load the image data from the selected card's PRN file on the SD card. This is possibly because the SD card is either not programmed properly, or faulty.
Source: line 415 of ./nxd/Optima/customisation.c (scope: print_sample_prn)
Reason: While preparing to print a demo card, the printer was unable to load the header data from the selected card's PRN file on the SD card. This is possibly because the SD card is either not programmed properly, or faulty.
Source: line 430 of ./nxd/Optima/customisation.c (scope: print_sample_prn)
Reason: While performing filesystem validation on the internal SD card, a problem was detected. This may be because a problem occurred during the soak/upgrade Production stage. The soak/upgrade test stage should be repeated.
Source: line 76 of ./nxd/Optima/maintenance.c (scope: request_maintenance_mode)
Reason: While attempting to read a PRN file from the SD card, the printer was unable to open the file. This is possibly because the SD card has not been programmed correctly.
Source: line 442 of ./nxd/Optima/customisation.c (scope: print_sample_prn)
Reason: While attempting to read a compressed animation frame from the SD card, the printer found that the length of the retrieved file was either zero or too large. This is probably because either the SD card has not been correctly programmed, or the animation data on the SD card has become corrupted.
Source: line 932 of ./nxd/Optima/gui_if_thread.c (scope: gui_tx_thread)
Reason: While attempting to read a compressed animation frame from the SD card, the printer was unable to read from the required point in the animation data. This is probably because either the SD card has not been correctly programmed, or the animation data on the SD card has become corrupted.
Source: line 952 of ./nxd/Optima/gui_if_thread.c (scope: gui_tx_thread)
Reason: While attempting to read a compressed animation frame from the SD card, the printer was unable to open the animation data file. This is probably because either the SD card has not been correctly programmed, or the animation data on the SD card has become corrupted.
Source: line 966 of ./nxd/Optima/gui_if_thread.c (scope: gui_tx_thread)
Reason: While attempting to read an animation from the SD card, the printer was unable to locate the required position in the animation file. This is possibly because the SD card has not been programmed correctly.
Source: line 940 of ./nxd/Optima/peginterface.cpp (scope: userMessageCallback)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | No | SEV_ERROR | Cleaning is overdue. |
Reason: During printer boot-up initialisation, while attempting to check whether the printer needed to be cleaned, the printer determined that cleaning was overdue. This error message is a prompt to the user to carry out the cleaning routine.
Source: line 108 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_cleaning_required)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| Yes | Yes | No | SEV_ERROR | The printer has not been calibrated. |
Reason: During printer boot-up initialisation, while attempting to check whether printer calibration was required, the printer determined that calibration had not yet been performed. This error message is a prompt to the user to carry out the automatic calibration and soak test.
Source: line 143 of ./print_engine/src/threads/print_engine_init_thread.cpp (scope: check_if_calibration_required)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | The printer is too hot to soak test. |
Reason: The printer was requested to carry out a printer soak test, but detected that the heated roller was too hot (above 60 degrees Celsius). The printer should be switched off and allowed to cool, and then switched on without film fitted before retrying the soak test.
Source: line 416 of ./print_engine/src/job_handlers/job_soak_handler.cpp (scope: pre_soak_printer)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | No cleaning card. |
Reason: At the start of a roller cleaning routine, the printer was waiting for the cleaning card to be inserted into the print engine. However, it took too long for the cleaning card's leading edge to be detected at the print position opto sensor. This is probably because the cleaning card was not inserted, but if not then it could be that either the feed motor or card drive motor was not not functioning correctly, or the print position opto sensor was faulty.
Source: line 633 of ./print_engine/src/media/card_ctrl.cpp (scope: prepare_to_clean_rollers)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Incorrect cleaning card type detected. |
Reason: At the start of a roller cleaning routine, and having already detected what should have been a cleaning card being inserted, the printer determined that the inserted card was shorter than expected and therefore probably not actually a proper roller cleaning card. This is probably because the wrong sort of card was inserted, or the card input hopper was not removed before initiating the cleaning cycle.
Source: line 684 of ./print_engine/src/media/card_ctrl.cpp (scope: prepare_to_clean_rollers)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Cleaning card jam. |
Reason: At the start of a roller cleaning routine, and having already detected that a cleaning card had been inserted, the printer was waiting for the cleaning card's leading edge to reach the eject opto sensor. However, it took too long for the eject sensor to become blocked. This is possibly because either the cleaning card was obstructed, or the eject sensor is faulty.
Source: line 668 of ./print_engine/src/media/card_ctrl.cpp (scope: prepare_to_clean_rollers)
Reason: While performing a roller cleaning cycle, and having already fed in a roller cleaning card as far as the flipper rollers, the printer determined tried to feed the cleaning card back out of the print engine. The first part of this process was to wait for the eject opto sensor to unblock, but this took longer than expected. This probably means that the cleaning card has become jammed in the print engine, perhaps due to a physical obstruction or because the card is slipping on the rollers.
Source: line 763 of ./print_engine/src/media/card_ctrl.cpp (scope: clean_rollers)
Reason: While performing a roller cleaning cycle, and having already fed in a roller cleaning card as far as the flipper rollers, the printer tried to feed the cleaning card backwards out of the print engine. The cleaning card had already successfully moved out from under the eject opto sensor by this point, and the next stage was to wait for the print position opto sensor to unblock. However, this took longer than expected. This probably means that the cleaning card has become jammed in the print engine, perhaps due to a physical obstruction or because the card is slipping on the rollers.
Source: line 798 of ./print_engine/src/media/card_ctrl.cpp (scope: clean_rollers)
Reason: After performing a roller cleaning cycle, the printer tried to feed the cleaning card backwards out of the print engine. However, it took longer than expected for the cleaning card to reach the feed sensor. This probably means that the cleaning card has become jammed in the print engine, perhaps due to a physical obstruction or because the card is slipping on the rollers.
Source: line 2346 of ./print_engine/src/media/card_ctrl.cpp (scope: eject_cleaning_card)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_ERROR | Cleaning card not ejected. Please remove card from rear of printer. |
Reason: While performing a roller cleaning cycle, and having already fed in a roller cleaning card as far as the flipper rollers and fed it back again to the point where the print position opto sensor was unblocked, it took too long for the feed opto sensor to become unblocked. This probably means that the cleaning card has become jammed, perhaps due to a physical obstruction or because the card is slipping on the rollers.
Source: line 2375 of ./print_engine/src/media/card_ctrl.cpp (scope: eject_cleaning_card)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | General error |
Reason: While attempting to retrieve a HoloKote file from the SD card, the printer found that an invalid parameter was supplied for selecting how the bitmap should be rotated. This indicates a bug in the firmware.
Source: line 358 of ./nxd/Optima/holokote.c (scope: do_retrieve)
Reason: While attempting to return the mag head to the home position by moving the mag head towards the rear of the printer, it took too long for the head stepper motor to report coming to a stop after triggering the head home opto sensor. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 356 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_home)
Reason: While attempting to encode a mag card, the printer had to wait for the mag head to reach the start of the data region on the mag stripe. However, the stepper motor took too long to report that it had travelled the required distance. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 831 of ./print_engine/src/hal/encoder.cpp (scope: wait_for_start_of_write_region)
Reason: Having just written data to a mag card, the printer had to wait for the mag head to reach the end of the data region on the mag stripe. However, the stepper motor took too long to report that it had travelled the required distance. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 890 of ./print_engine/src/hal/encoder.cpp (scope: wait_for_end_of_write_region)
Reason: While initialising the flipper, having already seen the flipper opto sensor unblock and then block again, the printer waited for the flip rotation motor to come to a stop. However, it took too long for the flip rotation motor to report that it had stopped. This is either due to a bug in the firmware, or an FPGA fault.
Source: line 156 of ./print_engine/src/hal/flipper.cpp (scope: initialise)
Reason: The printer attempted to rotate the flipper to a new orientation, but the flip rotation motor took too long to report that it had reached the required position. This is either due to a bug in the firmware, or an FPGA fault.
Source: line 182 of ./print_engine/src/hal/flipper.cpp (scope: move_by)
Reason: While attempting to initialise the print engine, none of the card sensors were initially blocked and so the printer moved the flipper card drive motor by a small amount to see if this triggered any card sensors. No sensor transition was seen, and the printer then had to restore the flipper card drive motor to its original state by reversing it by a small amount. However, the motor took too long to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 2278 of ./print_engine/src/media/card_ctrl.cpp (scope: locate_card_when_no_sensor_blocked)
Reason: While processing a non-printing job arriving via Ethernet,the printer failed to allocate enough memory to store the job's payload. This may be because there is a large number of jobs pending in the printer's memory.
Source: line 281 of ./nxd/Optima/msg_manager.c (scope: child_server_process)
Reason: While processing a print job arriving via Ethernet,the printer failed to allocate enough memory to store the job's payload. This may be because there is a large number of jobs pending in the printer's memory.
Source: line 339 of ./nxd/Optima/msg_manager.c (scope: child_server_process)
Reason: During a print job, while in the process of printing one of the colour planes onto the transfer film, the printer detected that it had missed its cue for printing one of the lines of the image. This is a bug in the firmware, possibly caused by a high priority thread using too much processor time during printing.
Source: line 1014 of ./print_engine/src/job_handlers/stages/stage_print.cpp (scope: main_print_loop)
Reason: While processing a request to move the card to the transfer standby position, the printer found that the current card position code was invalid. This is due to a bug at a very fundamental layer in the firmware, so rather than attempt to recover the printer opted to reject the request.
Source: line 281 of ./print_engine/src/media/card_ctrl.cpp (scope: to_transfer_standby)
Reason: While processing a request to move the card to the flip standby position, the printer found that the current card position code was invalid. This is due to a bug at a very fundamental layer in the firmware, so rather than attempt to recover the printer opted to reject the request.
Source: line 394 of ./print_engine/src/media/card_ctrl.cpp (scope: to_flip_standby)
Reason: While attempting to feed a card from the flipper to the encoder, and having reached the point where the leading edge of the card triggered the encoder unit's card opto sensor, the printer tried to move the card beyond the opto sensor by a small amount. However, it took too long for the stepper motor to indicate that it had moved the required distance. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 1329 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_to_combined_encoder_unit)
Reason: While attempting to eject a card, and having already placed the card in the flipper and rotated the flipper to the required angle for ejection, the printer tried to run the flipper card drive motor for a particular distance in order to place the card into the stacker. However, the flipper card drive motor took too long to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 2064 of ./print_engine/src/media/card_ctrl.cpp (scope: from_initialised_flip_to_eject)
Reason: While attempting to reject a card, and having already placed the card in the flipper and rotated the flipper to the required angle for rejection, the printer tried to run the flipper card drive motor for a particular distance in order to place the card into the reject area. However, the flipper card drive motor took too long to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 2104 of ./print_engine/src/media/card_ctrl.cpp (scope: from_initialised_flip_to_reject)
Reason: While performing a roller cleaning cycle, and having already fed in a roller cleaning card, the printer tried to feed the cleaning card forward to clean the flipper rollers. However, it took too long for the flipper card drive motor to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 732 of ./print_engine/src/media/card_ctrl.cpp (scope: clean_rollers)
Reason: While performing a roller cleaning cycle, and having already fed in a roller cleaning card as far as the flipper rollers and fed it back again to the point where all the card opto sensors were unblocked, the printer needed to continue driving the card for a short distance. However, it took too long for the card drive stepper motor to report that it had moved by the required amount. This is either due to a bug in the firmware or a problem in the FPGA.
Source: line 2399 of ./print_engine/src/media/card_ctrl.cpp (scope: eject_cleaning_card)
Reason: While feeding a new card from the hopper, and having already extracted the card far enough for it to block the feed sensor followed by the print position sensor, the printer needed to move the card forwards by a small additional distance. However, it took too long for the card drive stepper motor to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 1940 of ./print_engine/src/media/card_ctrl.cpp (scope: from_feed_sensor_to_transfer_standby)
Reason: While trying to feed a card from the heated roller to the transfer standby position (where the card is over the print position sensor), and having reached the point where the print position opto sensor had become blocked, the printer needed to move the card for an additional short distance. However, it took too long for the card drive stepper motor to report that it had moved by the required amount. This is due to either a bug in the firmware, or a problem with the FPGA.
Source: line 1106 of ./print_engine/src/media/card_ctrl.cpp (scope: from_heated_roller_to_transfer_standby)
Reason: While trying to feed a card from the flip standby position (where the leading edge of the card is near the eject sensor) to the transfer standby position (where the card is over the print position sensor), and having reached the point where the print position opto sensor had become blocked, the printer needed to move the card for an additional short distance. However, it took too long for the card drive stepper motor to report that it had moved by the required amount. This is due to either a bug in the firmware, or a problem with the FPGA.
Source: line 1153 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_transfer_standby)
Reason: During the boot-up process, the printer firmware detected that the FPGA was either unprogrammed or unresponsive to SPI commands. This can probably be remedied by reprogramming the FPGA via the support utility, or failing that via JTAG. If neither of those options work, it could indicate a hardware fault requiring a PCB replacement.
Source: line 271 of ./print_engine/src/print_engine.cpp (scope: power_on_test)
Reason: While trying to move the card from the transfer standby position (where the card is over the print position sensor) to the heated roller, and having already reached the point where the print position opto sensor was unblocked, the printer had to move the card an additional short distance. However, it took too long for the card driver stepper motor to report that it had moved by the required amount. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 1197 of ./print_engine/src/media/card_ctrl.cpp (scope: from_transfer_standby_to_heated_roller)
Reason: While trying to move the card from the encoder unit to the flip standby position (where the card edge is by the eject sensor), the printer first had to pull the card into the flipper from the encoder. However, it took too long for the flipper card drive motor to report that it had moved by the required amount. This is due to either a bug in the firmware, or a problem with the FPGA.
Source: line 1383 of ./print_engine/src/media/card_ctrl.cpp (scope: from_combined_encoder_unit_to_flip_standby)
Reason: While trying to move the card from the flip standby position (where the card's leading edge is by the eject sensor) to the flipper, and having already moved the card forwards and just past the point where the eject sensor unblocked, the printer tried to continue driving the card for a small additional distance using the flipper's card drive motor. However, it took too long for the flipper's card drive motor to report that it had moved by the required amount. This is due to either a bug in the firmware or a problem with the FPGA.
Source: line 1577 of ./print_engine/src/media/card_ctrl.cpp (scope: from_flip_standby_to_flip)
Reason: While processing a job arriving via USB, the printer failed to allocate enough memory to store the job's payload. This may be because there is a large number of jobs pending in the printer's memory.
Source: line 343 of ./nxd/Optima/msg_manager_usb.c (scope: msg_manager_usb)
Reason: While processing a job arriving via Wi-Fi, the printer failed to allocate enough memory to store the job'spayload. This may be because there is a large number of jobs pending in the printer's memory.
Source: line 1616 of ./nxd/Optima/wifi.c (scope: WiFi_Handle_Data)
Reason: While trying to move the card from the post transfer position (where the card is over the eject sensor but also partly in the flipper) to the flip mechanism, and having just cleared the eject sensor, the printer needed to move the card for a small additional distance into the flipper. However, it took too long for the flipper card drive motor to report that it had moved by the required amount. This is due to either a bug in the firmware, or a problem with the FPGA.
Source: line 1810 of ./print_engine/src/media/card_ctrl.cpp (scope: from_post_transfer_to_flip)
Reason: While trying to move the transfer film downwards by a specified distance, the transfer take-up stepper motor took too long to report that it had moved the required amount. This is either due to a bug in the firmware or a problem in the FPGA.
Source: line 415 of ./print_engine/src/media/transfer_ctrl.cpp (scope: transfer_down_for_ticks)
Reason: While trying to move the transfer film upwards by a specified distance, the transfer take-up stepper motor took too long to report that it had moved the required amount. This is either due to a bug in the firmware or a problem in the FPGA.
Source: line 460 of ./print_engine/src/media/transfer_ctrl.cpp (scope: transfer_up_for_ticks)
Reason: While the printer was attempting to position the transfer film a particular distance beyond the index mark it had just detected, the transfer take-up stepper motor took too long to report that it had moved the required amount. This is either due to a bug in the firmware or a problem in the FPGA.
Source: line 1343 of ./print_engine/src/media/transfer_ctrl.cpp (scope: last_operation_failed)
Reason: While initialising the print engine, an unexpected error occurred while the printer was trying to communicate with the RFID reader hardware. This is possibly because the RFID reader hardware is faulty.
Source: line 397 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: While attempting to return the mag head to the standby position near the front end of print engine, the head stepper motor took too long to report that it had stopped after clearing the head home opto sensor and moving the required distance towards the front of the print engine. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 407 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_standby)
Reason: During the boot-up process, the printer firmware detected that the installed FPGA bitstream version was too old to be used safely. can probably be remedied by reprogramming the FPGA via the support utility, or failing that via JTAG. If neither of those options work, it could indicate a hardware fault requiring a PCB replacement.
Source: line 287 of ./print_engine/src/print_engine.cpp (scope: power_on_test)
Reason: While attempting to install a new custom string file, the printer failed to validate the supplied XML data. This is due to the data being malformed or corrupt.
Source: line 884 of ./nxd/Optima/customisation.c (scope: update_strings)
Reason: Having printed a copy of a card, the printer was attempting to compute the amount of dye film used but could not do so. This is almost certainly due to a bug in the software.
Source: line 217 of ./print_engine/src/job_handlers/stages/stage_update_counters.cpp (scope: determine_num_dye_panels_sets_used)
Reason: In the firmware module which controls the heated roller temperature, the temperature sensor alarm was triggered even though the measured temperature was at acceptable levels. This could indicate a fault in the temperature sensing circuitry.
Source: line 94 of ./print_engine/src/hal/hr_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
Reason: While trying to update the printer's SD card authentication data, the printer failed to allocate memory for verifying the data signature. This may be because there are a large number of pending jobs in the printer's memory.
Source: line 123 of ./nxd/Optima/auth.c (scope: validate_auth_data)
Reason: While trying to straighten the card after placing it into the transfer standby position, the FPGA took too long to report that the card had moved the required distance. This is either due to a problem with the FPGA or a firmware bug. Reprogramming the firmware and/or FPGA may resolve this problem. If not, there may be a physical problem with communication between the CPU and FPGA.
Source: line 2462 of ./print_engine/src/media/card_ctrl.cpp (scope: straighten_card)
Reason: While initialising the print engine, the printer was unable to communicate with the RFID reader hardware. This is possibly because the RFID reader hardware is faulty.
Source: line 373 of ./print_engine/src/print_engine.cpp (scope: read_film_info)
Reason: In the firmware module which controls the heated roller temperature, the printer detected that the heated roller was taking significantly longer than usual to warm up to the expected temperature. This is usually due to the temperature sensor not properly contacting the heated roller, but may also indicate a bug in the firmware.
Source: line 110 of ./print_engine/src/hal/hr_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
Reason: In the firmware module which controls the heated roller temperature, the printer detected that the heated roller was taking significantly longer than usual to cool down to the expected temperature. This may be due to a firmware bug.
Source: line 119 of ./print_engine/src/hal/hr_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
Reason: In the firmware module which controls the printhead temperature, the printer detected that the printhead was taking significantly longer than usual to warm up to the expected temperature. This may be due to a firmware bug.
Source: line 88 of ./print_engine/src/hal/ph_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
Reason: In the firmware module which controls the printhead temperature, the printer detected that the printhead was taking significantly longer than usual to cool down to the expected temperature. This may be due to a firmware bug.
Source: line 97 of ./print_engine/src/hal/ph_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
Reason: While processing a job arriving via USB, a zero length payload was received. There may be a problem with the application software or a USB outage has occurred.
Source: line 280 of ./nxd/Optima/msg_manager_usb.c (scope: msg_manager_usb)
Reason: While attempting to return the mag head to the home position, the printer first had to clear the head home opto sensor by moving the mag head a short distance towards the front of the printer. However, after the head home opto sensor was unblocked, the head stepper motor took too long to report that it had stopped. This is either due to a bug in the firmware, or a problem with the FPGA.
Source: line 318 of ./print_engine/src/hal/encoder.cpp (scope: mag_head_to_home)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | The heater is over temperature. |
Reason: In the firmware module which controls the heated roller temperature, the printer detected that the heated roller temperature was above the maximum permitted level. This is either due to a fault in the control software, or a problem with the temperature measurement hardware.
Source: line 73 of ./print_engine/src/hal/hr_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | The printhead is over temperature. |
Reason: In the firmware module which controls the printhead temperature, the printer detected that the printhead temperature was above the maximum permitted level. This is either due to a fault in the control software, or a problem with the temperature measurement hardware.
Source: line 66 of ./print_engine/src/hal/ph_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | The heater sensor is disconnected. |
Reason: In the firmware module which controls the heated roller temperature, the temperature sensor alarm was triggerd and the temperatures sensor was reporting an unusually low temperature. This is almost always because the temperature sensor is not connected properly.
Source: line 85 of ./print_engine/src/hal/hr_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)
| Retriable | Cancellable | Retried on closing cover | Severity | Displayed message |
|---|---|---|---|---|
| No | Yes | No | SEV_FATAL | The printhead is disconnected. |
Reason: In the firmware module which controls the printhead temperature, the temperature sensor was reporting an unusually low temperature. This is almost always because the printhead is not connected properly.
Source: line 75 of ./print_engine/src/hal/ph_pid_listener.hpp (scope: PID_TEMP_CTRL_LISTENER)