Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Printing failures - false negative limitation #35

Open
wassermandh opened this issue Jan 13, 2025 · 1 comment
Open

Printing failures - false negative limitation #35

wassermandh opened this issue Jan 13, 2025 · 1 comment
Assignees

Comments

@wassermandh
Copy link

wassermandh commented Jan 13, 2025

Description

Hey all,

I’m currently working with printer model SP700 and am running into an issue tracking print job failures. The problem usually occurs when I attempt to print several items in relatively quick succession. I run openAsync and then printAsync, and for most of these items, the print executes as expected, and printAsync doesn’t throw any errors.

However, for one or two of these items, I will receive an error message from printAsync, even though the print did go through successfully. The three errors I have been seeing are, in order of frequency:
StarIO10UnprintableException with a “Print timed out” message
StarIO10UnprintableException with an “Initialize failed” message
StarIO10CommunicationException with a “Request timed out” message

To clarify, the print jobs are successful, but because printAsync throws an error in our code for them, they are programmatically marked as failures. This will create issues for us as we want to give our users an opportunity to retry a failed print job, and retrying these false negative instances would print out a duplicate.

Reading through the printAsync docs, it says at the bottom of the page: “If any of the following errors are thrown, the printing may have been executed, but its printed content is not guaranteed”. So, it seems like an error being thrown doesn’t always indicate the print failed.

I was thinking of ignoring these listed errors as noise, and not marking the print job as failed when they occur, but that would be ignoring over half (7/12) of the errors that printAsync could throw. My concern with this would be creating false positives (marking true failures as successes). I also saw we have the ability to set a “printTimeout” property on the starPrinter, but I’m not sure if that could lead to other problems. Also, even increasing it to 10 seconds didn’t resolve the issue.

Does anyone have any experience dealing with accurately tracking print job failures for the SP700 model? It looks like for some other models (e.g. MCL32BI) you can query for a print job to get status (e.g. here), but this doesn’t seem possible with SP700.

Any advice would be much appreciated. Thank you in advance!

Your printer

  • Model Names:
    SP700
@KHosozawa
Copy link

@wassermandh
No such problem has ever been reported to us.

Therefore we would like to investigate this issue.
Could you please provide us with the following information?

  • A picture of the printer's self-printing results
    • When the printer is turned on while holding down the Feed button, it self-prints. Keep the Feed button pressed until the printer starts printing.
  • Printer Interface (USB / Bluetooth / Ethernet)
  • A picture of what you printed from the application
  • Frequency of occurrence

@KHosozawa KHosozawa self-assigned this Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants