Error code documentation for DTC printer firmware version 11.38

Reason: The lid was opened while the print engine was performing an operation. Close the lid and try again.

Source: line 1366 of print_engine_driver.cpp

Reason: The lid was open at the point the printer was about to begin a print job. Close the lid and try again.

Source: line 571 of print_ctrl.cpp

Reason: While feeding a card from the hopper, it took too long for the rear sensor to block.

Source: line 1203 of print_engine_driver.cpp

Reason: While trying to feed a card from the hopper, it took too long for the front sensor to block.

Source: line 1183 of print_engine_driver.cpp

Reason: While hand feeding a card, it took too long for the front sensor to block.

Source: line 1146 of print_engine_driver.cpp

Reason: While hand feeding a card, it took too long for the hopper sensor to detect a card.

Source: line 1140 of print_engine_driver.cpp

Reason: While moving the card forwards to the front sensor in preparation for placing it in the contactless encoding position, it took too long for the front sensor to block.

Source: line 1077 of print_engine_driver.cpp

Reason: While moving the card backwards from the front sensor to the contactless encoding position, it took too long for the front sensor to unblock.

Source: line 1085 of print_engine_driver.cpp

Reason: While feeding a card from the smart encoder to the flipper, it took too long for the smart extract sensor to indicate that the card was free of the encoder.

Source: line 1105 of print_engine_driver.cpp

Reason: While moving a card from the flipper into the smart encoder, it took too long for the smart insert sensor to trigger.

Source: line 1120 of print_engine_driver.cpp

Reason: While moving the card from the flipper to the standby position, it took too long for the mid sensor to block.

Source: line 1127 of print_engine_driver.cpp

Reason: While feeding a card from the hopper, and having seen the card reach the rear sensor, it took too long for the mid sensor to block.

Source: line 1196 of print_engine_driver.cpp

Reason: While feeding a card from the hopper, and having seen the card reach the mid sensor, it took too long to clear the rear sensor by rewinding the feed motor.

Source: line 1209 of print_engine_driver.cpp

Reason: While moving the card forwards to feed into the flipper, it took too long for the card's leading edge to block the front sensor.

Source: line 1223 of print_engine_driver.cpp

Reason: While moving the card from the front sensor to the standby position, it took too long for the front sensor to unblock.

Source: line 1265 of print_engine_driver.cpp

Reason: While moving the card from the rear sensor to the standby position, it took too long for the rear sensor to unblock.

Source: line 1279 of print_engine_driver.cpp

Reason: While moving a card from the flipper into the smart encoder, it took too long for the smart extract sensor to trigger. This may mean that there is no encoder actually fitted.

Source: line 1112 of print_engine_driver.cpp

Reason: While feeding a card past a sensor, and having seen the card reach that sensor, it took too long for the sensor to unblock.

Source: line 1216 of print_engine_driver.cpp

Reason: While moving the card into position for a printing or encoding operation, it took took long for the reference edge of the card to move in front of the sensor used for positioning. In the case of extended mono prints, this means the mid sensor took too long to block. In other cases, this means it took too long for the rear sensor to unblock.

Source: line 1243 of print_engine_driver.cpp

Reason: While moving the card into position for a printing or encoding operation, it took took long for the reference edge of the card to move behind the sensor used for positioning. In the case of extended mono prints, this means the mid sensor took too long to unblock. In other cases, this means it took too long for the rear sensor to block.

Source: line 1254 of print_engine_driver.cpp

Reason: While trying to eject the card, it took too long for the leading edge of the card to block the front sensor.

Source: line 1092 of print_engine_driver.cpp

Reason: While trying to eject the card, and having seen the leading edge of the card reach the front sensor, it took too long for the front sensor to unblock.

Source: line 1098 of print_engine_driver.cpp

Reason: While moving the card from the flipper to the standby position, and having seen the card reach the mid sensor, it took too long for the mid sensor to unblock.

Source: line 1133 of print_engine_driver.cpp

Reason: While trying to feed a card from the hopper, and having seen the card reach the front sensor, it took too long for the front sensor to unblock.

Source: line 1189 of print_engine_driver.cpp

Reason: While moving the card backwards to feed into the flipper, it took too long for the card to block the mid sensor.

Source: line 1230 of print_engine_driver.cpp

Reason: While moving the card from the mid sensor to the standby position, it took too long for the mid sensor to unblock.

Source: line 1272 of print_engine_driver.cpp

Reason: While moving the card to the front sensor, it took too long for the front sensor to block.

Source: line 1286 of print_engine_driver.cpp

Reason: While moving the card to the rear sensor, it took too long for the rear sensor to block.

Source: line 1292 of print_engine_driver.cpp

Reason: While moving a dye panel edge from the dye sensor to the printhead, it took too long for the tacho wheel to move the required amount. The film has probably either run out or snapped.

Source: line 1298 of print_engine_driver.cpp

Reason: While advancing to the next dye panel, it too long for the next panel boundary to be detected.

Source: line 1325 of print_engine_driver.cpp

Reason: It took too many attempts for the printer to find a particular panel of dye film (possibly because the dye sensor needs calibration).

Source: line 1331 of print_engine_driver.cpp

Reason: A valid dye film RFID tag was found, but no physical ribbon could be detected while trying to take up the film slack.

Source: line 1023 of print_engine_driver.cpp

Reason: A valid dye film RFID tag was found, but there were no shots remaining.

Source: line 865 of print_engine_driver.cpp

Reason: After printing a card, the printer was unable to decrement the number of remaining prints on the dye film RFID tag.

Source: line 2270 of print_ctrl.cpp

Reason: When about to print a panel, the printer detected the end-of-film marker.

Source: line 1319 of print_engine_driver.cpp

Reason: While moving the dye film, too great a time elapsed between tacho sensor counts. The film has probably either run out or snapped.

Source: line 1306 of print_engine_driver.cpp

Reason: While trying to take up the film slack, no tacho pulses were observed within a reasonable amount of time

Source: line 1338 of print_engine_driver.cpp

Reason: After completing a print job, the printer detected the end-of-film marker.

Source: line 596 of print_ctrl.cpp

Reason: While trying to move past the transition region beween two dye panels, it took too long for the dye motor to move the the required amount.

Source: line 1344 of print_engine_driver.cpp

Reason: Just before starting to print a panel, the printer detected the end-of-film marker.

Source: line 1284 of print_ctrl.cpp

Reason: The fitted dye film had an invalid RFID tag. Either the tag was not programmed correctly or there is a problem with the RFID tag reader.

Source: line 828 of print_engine_driver.cpp

Reason: A dye film ribbon was detected, but a valid dye film RFID tag could not be found. This printed is not configured to permit tagless film.

Source: line 1004 of print_engine_driver.cpp

Reason: The fitted dye film does not have the right region code for this printer. Try another roll of film.

Source: line 835 of print_engine_driver.cpp

Reason: The fitted dye film does not have the right dealer code for this printer. Try another roll of film.

Source: line 841 of print_engine_driver.cpp

Reason: The fitted dye film does not have the right project code for this printer. Try another roll of film.

Source: line 847 of print_engine_driver.cpp

Reason: The fitted dye film does not have the right grade code for this printer. Try another roll of film.

Source: line 853 of print_engine_driver.cpp

Reason: The printer detected film was loaded when trying to calibrate dye LEDs and dye motor.

Source: line 1313 of print_engine_driver.cpp

Reason: The printer detected film was loaded when trying to carry out an operation that requires no film to be present.

Source: line 54 of error_if_film_present_handler.cpp

Reason: While moving the printhead cam to the closed position, it took too long to detect the trailing edge of the cam pulley flag.

Source: line 1050 of print_engine_driver.cpp

Reason: While initialising the cam, it took too long to detect the leading edge of the cam pulley flag.

Source: line 1057 of print_engine_driver.cpp

Reason: While initialising the cam, and having detected the leading edge of the cam pulley flag, it took too long to detect the trailing edge of the flag.

Source: line 1063 of print_engine_driver.cpp

Reason: While moving the printhead cam to the open position, it took too long to detect the leading edge of the cam pulley flag.

Source: line 1070 of print_engine_driver.cpp

Reason: While initialising the flipper, it took too long to detect the the start of the blocked region of the flange.

Source: line 1351 of print_engine_driver.cpp

Reason: While initialising the flipper, and having detected the start of the blocked region of the flange, it took too long to detect the start of the unblocked region (the start of the slot).

Source: line 1358 of print_engine_driver.cpp

Reason: While moving the card backwards to feed into the flipper, and having seen the card arrive at the mid sensor, it took too long for the mid sensor to unblock.

Source: line 1236 of print_engine_driver.cpp

Reason: The printer received a print job. The side number specified for one of the sides of the image data was invalid. This probably means the print job file was corrupt.

Source: line 115 of card_handler.cpp

Reason: The printer received a print job. The format specified for the image payload was not supported. If updating the firmware does not fix this, it may be that the print job file is corrupt.

Source: line 148 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. One of the tracks specified an invalid track number.

Source: line 246 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. The number of bits specified for one of the tracks was out of range. This probably means that the print job file was corrupt.

Source: line 291 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. The number of bits specified for one of the tracks was too great for the provided payload size. This probably means that the print job file was corrupt.

Source: line 302 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. The bit density specified for one of the tracks was out of range. This probably means that the print job file was corrupt.

Source: line 314 of card_handler.cpp

Reason: The printer received a print job. The panel ID specified for one of the panels was invalid. This probably means that the print job file was corrupt.

Source: line 352 of card_handler.cpp

Reason: The printer received a print job. The width or height specified for the card was out of range. This probably means the print job file was corrupt.

Source: line 167 of card_handler.cpp

Reason: The printer received a print job. The payload provided was not large enough to hold the image width specified. This probably means the print job file was corrupt.

Source: line 517 of card_handler.cpp

Reason: The printer received a print job. The power adjustment for one of the panels was out of range. This probably means the print job file was corrupt.

Source: line 530 of card_handler.cpp

Reason: The printer received a print job. The number of copies specified was less than 1. This means that the print job file is corrupt.

Source: line 137 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. The number of encoding attempts requested was less than one.

Source: line 214 of card_handler.cpp

Reason: The printer received a print job containing magnetic track data. The number of verification attempts requested was less than zero.

Source: line 224 of card_handler.cpp

Reason: The printer received a print job. The x adjustment specified for a panel was out of range. This probably means the print job file was corrupt.

Source: line 469 of card_handler.cpp

Reason: The printer received a print job. The y adjustment specified for a panel was out of range. This probably means the print job file was corrupt.

Source: line 480 of card_handler.cpp

Reason: The printer received a print job. An area or hole setting for one of the panels was missing a required element. This probably means the print job file was corrupt.

Source: line 421 of card_handler.cpp

Reason: The printer received a print job. An area or hole setting for one of the panels had an out-of-range value. This probably means the print job file was corrupt.

Source: line 437 of card_handler.cpp

Reason: The printer received a print job. The X coordinate for the HoloCode is out of range. This probably means the print job file was corrupt.

Source: line 642 of card_handler.cpp

Reason: The printer received a print job. The Y coordinate for the HoloCode is out of range. This probably means the print job file was corrupt.

Source: line 652 of card_handler.cpp

Reason: The printer received a print job. The module size for the HoloCode is out of range. This probably means the print job file was corrupt.

Source: line 661 of card_handler.cpp

Reason: The printer received a print job. The margin for the HoloCode is out of range. This probably means the print job file was corrupt.

Source: line 671 of card_handler.cpp

Reason: The printer received a print job. The format for the HoloCode is unsupported. This probably means the print job file was corrupt.

Source: line 685 of card_handler.cpp

Reason: The printer received a print job. The data for the HoloCode is either empty or too long. This probably means the print job file was corrupt.

Source: line 697 of card_handler.cpp

Reason: The fitted dye film has a data format which the printer could not understand. The printer software needs to be upgraded in order to support this type of dye film.

Source: line 821 of print_engine_driver.cpp

Reason: While hand feeding a card, the rear sensor blocked before the front one.

Source: line 1152 of print_engine_driver.cpp

Reason: While hand feeding a card, and having seen the card reach the front sensor, the rear sensor blocked before the front sensor unblocked.

Source: line 1158 of print_engine_driver.cpp

Reason: While feeding a card from the hopper, the front sensor blocked before the mid one.

Source: line 1165 of print_engine_driver.cpp

Reason: While feeding a card from the hopper, the front sensor blocked before the rear one.

Source: line 1171 of print_engine_driver.cpp

Reason: While trying to feed a card from the hopper, the mid sensor triggered before the front one.

Source: line 1177 of print_engine_driver.cpp

Reason: The printhead took too long to reach a temperature suitable for printing. There may be a fault with the printhead temperature sensor.

Source: line 1736 of print_ctrl.cpp

Reason: The mag PCB MCU reported that an error occurred while trying to carry out an operation or interpret a command.

Source: line 163 of usb_mag_encoder.cpp

Reason: The mag driver reported that an error occurred while trying to carry out an operation.

Source: line 156 of usb_mag_encoder.cpp

Reason: Communication with the print engine microcontroller failed. If rebooting the printer does not fix this problem, try updating the firmware. If that does not work, there is probably a hardware fault.

Source: line 1042 of print_engine_driver.cpp

Reason: The print engine microcontroller reported an error. If rebooting the printer does not fix this problem, try updating the firmware. If that does not work, there is probably a hardware fault.

Source: line 1419 of print_engine_driver.cpp

Reason: During initialisation the printer could not program the FPGA. Ensure the printer is running the latest software, reboot the printer, and try again. If this does not work there is either a bug in the printer software or a hardware fault.

Source: line 591 of application.cpp

Reason: The printhead driver was not initialised.

Source: line 1438 of application.cpp

Reason: Communication with the mag encoder microcontroller failed. If rebooting the printer does not fix this problem, try updating the firmware. If that does not work, there is probably a hardware fault.

Source: line 436 of i2c_mag_encoder.cpp

Reason: The mag encoder microcontroller reported an error. If rebooting the printer does not fix this problem, try updating the firmware. If that does not work, there is probably a hardware fault.

Source: line 445 of i2c_mag_encoder.cpp

Reason: While updating the dye control calibration, the printer detected that the blue duty cycle was out of range.

Source: line 901 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the green duty cycle was out of range.

Source: line 905 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the green and blue duty cycles were out of range.

Source: line 909 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the red duty cycle was out of range.

Source: line 914 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the red and blue duty cycles were out of range.

Source: line 918 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the red and green duty cycles were out of range.

Source: line 923 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the red, green and blue duty cycle were out of range.

Source: line 928 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current was out of range.

Source: line 933 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and blue duty cycle were out of range.

Source: line 937 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and green duty cycle were out of range.

Source: line 942 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and green and blue duty cycles were out of range.

Source: line 947 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and red duty cycle were out of range.

Source: line 952 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and red and blue duty cycles were out of range.

Source: line 957 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and red and green duty cycles were out of range.

Source: line 962 of print_engine_driver.cpp

Reason: While updating the dye control calibration, the printer detected that the motor current and red, green and blue duty cycle were out of range.

Source: line 967 of print_engine_driver.cpp

Reason: The internal SD card did not have a valid signature.

Source: line 562 of print_ctrl.cpp

Reason: While attempting to validate a Holokote file, the printer found that the file was not in the right format. Either it is not the right type of file, or the data has been corrupted.

Source: line 175 of overcoat_manager.cpp

Reason: While attempting to validate a Holokote file, the printer found that the file was not licensed for this printer. It is possible that the file was intended for a different printer.

Source: line 191 of overcoat_manager.cpp

Reason: While attempting to validate an upgrade file, the printer found that the file was not in the right format. Either it is not the right type of file, or the data has been corrupted.

Source: line 97 of capability_manager.cpp

Reason: While attempting to validate an upgrade file, the printer found that the file was not in the right format. Either it is not the right type of file, or the data has been corrupted.

Source: line 113 of capability_manager.cpp

Reason: While attempting to validate an upgrade file, the printer could not interpret the file's upgrade commands. Either it is not the right type of file, or the data has been corrupted.

Source: line 213 of capability_manager.cpp

Reason: While attempting to validate an upgrade file, the printer found that the file was not licensed for this printer. It is possible that the file was intended for a different printer.

Source: line 131 of capability_manager.cpp

Reason: While performing a system software update, an error occurred while trying to write temporary update data to the SD card.

Source: line 72 of update_manager.cpp

Reason: While attempting to apply an upgrade, the printer was unable to create the upgrade directory on the SD card. Either the SD card is missing, unformatted or functioning incorrectly.

Source: line 183 of capability_manager.cpp

Reason: While attempting to install a custom Holokote image, the printer was unable to create the overcoat directory on the SD card. Either the SD card is missing, unformatted or functioning incorrectly.

Source: line 302 of overcoat_manager.cpp

Reason: While attempting to update the system image, the printer was unable to create the system upgrade directory on the SD card. Either the SD card is missing, unformatted or functioning incorrectly.

Source: line 58 of update_manager.cpp

Reason: While attempting to format the SD card at the start of a soak routine, the formatting process failed.

Source: line 32 of start_soak_test_handler.cpp

Reason: While attempting to back up the printer settings to the shipped store, the printer failed to write the settings file to the SD card. Either the SD card is missing, unformatted or functioning incorrectly.

Source: line 56 of save_handler.cpp

Reason: While performing a system software update, an error was reported by the software update script.

Source: line 92 of update_manager.cpp

Reason: The printer received a double-sided print job, but does not have duplex printing enabled.

Source: line 836 of print_ctrl.cpp

Reason: The printer received a print job which required mag encoding, but does not have mag encoding enabled.

Source: line 852 of print_ctrl.cpp

Reason: The printer received a colour print job, but does not have colour film fitted.

Source: line 886 of print_ctrl.cpp

Reason: The print engine MCU reported a dye film motor fault.

Source: line 1372 of print_engine_driver.cpp

Reason: The print engine MCU reported a card feed motor fault.

Source: line 1377 of print_engine_driver.cpp

Reason: The print engine MCU reported a printhead cam motor fault.

Source: line 1382 of print_engine_driver.cpp

Reason: The print engine MCU reported a flip position motor fault while moving the card. Note that this is the flipper motor which drives the card, not the rotation motor.

Source: line 1388 of print_engine_driver.cpp

Reason: The print engine MCU reported a flip position motor fault while rotating the flipper. Note that this is the flipper motor which drives the card, not the rotation motor.

Source: line 1396 of print_engine_driver.cpp

Reason: The print engine MCU reported a flip rotation motor fault. Note that this is the flipper motor which rotates the flipper, not the one which drives the card

Source: line 1404 of print_engine_driver.cpp

Reason: The print engine MCU reported a main card drive motor fault.

Source: line 1412 of print_engine_driver.cpp

Reason: On start-up, the printer detected that it was overdue for cleaning.

Source: line 1475 of application.cpp

Reason: The printhead does not seem to be fitted.

Source: line 1444 of application.cpp

Reason: The internal SD card could not be detected.

Source: line 1458 of application.cpp

Reason: While attempting to verify mag data after an encoding operation, the printer found that the data read back from the mag stripe did not match the data written.

Source: line 1476 of print_ctrl.cpp

Reason: The printer received a colour print job, but does not have colour printing enabled.

Source: line 879 of print_ctrl.cpp

Reason: The printer recevied a job with neutral panel options, but the fitted dye film does not have neutral panels.

Source: line 926 of print_ctrl.cpp

Reason: Mag options were provided to the printer, but not mag data was present in the print job payload. If mag encoding is required, at least one mag track should be non-empty.

Source: line 265 of card_handler.cpp