search

michaelrsweet / lprint

A Label Printer Application
https://www.msweet.org/lprint
Apache License 2.0
243 stars 31 forks source link

Setup for Munbyn ITPP941 and Vevor Y428BT printers #130

Open mairas opened 9 months ago

mairas commented 9 months ago

The GitHub project didn't have a Discussion board, so let me misuse this issue for a success report and compliments.

I set up lprint on a Proxmox container. Snap wouldn't readily function because of the container environment, so I built lprint from sources. No issues there, sudo make install even put the systemd service files in place.

Printer setup was more straightforward than expected: the Munbyn ITPP941 worked right away with the tspl_203dpi driver and the Vevor Y428BT likewise worked out of the box with the tspl_300dpi driver.

I couldn't be happier. Thank you for your great work!

This issue report can be closed right away. Sorry for spamming. :-)

michaelrsweet commented 9 months ago

No worries, and thank you for letting me know things are working for you!

If you can provide the output of "lprint devices" then I can explicitly add them to the list of supported devices in a future release.

michaelrsweet commented 9 months ago

Also, I've gone ahead and enabled the discussions section for this project (they are really just issues that are split out on the separate tab, much like PRs...)

mairas commented 9 months ago

Here's the lprint devices output:

root@cups:~# lprint devices
usb://Munbyn%20/ITPP941?serial=9412104036835
usb://VEVOR%20/Y428BT?serial=0000000
root@cups:~#

Apologies for the hostname... :-) The Vevor one is crappy enough that it doesn't even provide a unique serial number.

Beware, though - both of these devices are Chinese knockoff printers that you in some discussion/issue/cantremember noted you preferred to stay clear of. Which is a decision I have absolutely no problem with. That was part of the reason I wanted to write either this issue or a Discussion post: when people Google for them, they'll find this issue to get them started even if explicit documentation wouldn't exist for those printers...

michaelrsweet commented 1 week ago

Could you provide the verbose output? Run:

lprint -o verbose devices

That way I'll see the device IDs to use for matching the driver...