-
Notifications
You must be signed in to change notification settings - Fork 16
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 Indefinitely - D110 #33
Comments
What version of D110 do you have (203 dpi or 300 dpi with reverse feed support)? Can you send screenshot of printer info (gear button near printer name)? I have same behaviour on my B1 when choosing V3 print task instead of V4. Try choosing V4 print task in print preview dialog and print again. If it working for you, you can press lock near print task. |
This worked perfectly, thank you!!! Within the screen shot of the printer info, it stated that the printer is V4. changing a V4 print task works great. Thanks for the quick response! |
Thanks again! |
Glad to hear! |
One other note: I think that under the model metadata, with the DPI being 203, and the printer being 300, this is causing degradation in print quality. |
Nice, thank you!
DPI is not using during prints. The single use of it is here - to convert mm to pixels: Printer operates with pixels units. You should use 11.81 as dpmm (300 DPI). Can you make a photo of bad quality print and screenshot of print preview? P.S. On you screenshot protocolVersion=4. There is not same as print task version. protocolVersion is some sort of "printer revision" and used to change some aspects of packet sending in official applications. Currently it have no use in niimblue. |
Have a new D110 printer. Through the app, when I hit print, the printer starts to print the same label, indefinitely. I have the number of copies set to 1, but it won't stop printing. I have to hit cancel within the UI, at which point, the printing stops.
I am running the server off OSX, and in the latest version of Chrome.
Great project BTW!
The text was updated successfully, but these errors were encountered: