Skip to content

Add QIN LabelPrinter / LW650XL PRO (2e3c:5757) to known TSPL ids - #6

Merged
ikwach merged 2 commits into
RunTheWall:mainfrom
owlot:add-qin-lw650xl-pro-id
Sep 2, 2026
Merged

ikwach merged 2 commits into
RunTheWall:mainfrom
owlot:add-qin-lw650xl-pro-id

Conversation

@owlot

@owlot owlot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds USB id 2e3c:5757 (QIN LabelPrinter, model LW650XL PRO) to KNOWN_IDS in backend/tspl so tspl://auto picks it up.
  • Like the XP-420B already documented in this file, ieee1284_id reports CMD:XPP,XL with no literal "TSPL" string — confirmed TSPL support by direct write to /dev/usb/lp0 and a successful physical test print.

Test plan

  • Plugged in the printer, confirmed vid:pid via sysfs (idVendor=2e3c idProduct=5757)
  • Pointed a CUPS queue at tspl://2e3c-5757 and printed a test TSPL label — printed correctly
  • With this change, tspl://auto should now match it directly without pinning by vid-pid

owlot and others added 2 commits September 1, 2026 16:36
Confirmed TSPL by direct write to /dev/usb/lp0; ieee1284_id reports
CMD:XPP,XL with no TSPL string, same pattern as the XP-420B already
noted in this file.
The udev rules and the README supported-printers table are hand-kept
mirrors of KNOWN_IDS, so an id that lands only in the backend leaves the
LW650XL PRO without its /dev/usb/tspl-label symlink and off the list
that tells owners it is supported. Both mirrors now carry 2e3c:5757,
the README names it under Confirmed working, and its ieee1284 string
joins the XP-420B as the second example of a TSPL printer that never
says TSPL.

2e3c is not registered to a printer vendor: it is Artery's AT32 MCU
vendor id, the default in their USB device SDK, and absent from
usb.ids. The LW650XL PRO is an Aimo/Quyin OEM unit and that family
enumerates under its chipset's ids, so other rebadges may share the
pair. The comment says so and keeps the entry pinned to :5757 rather
than wildcarded the way the Poskey vendor ids are.

A stub bus with only this printer sends the token through is_known();
it is the first exact-match entry after the wildcards, so a typo there
or a dropped entry now fails the suite instead of merging green.
@ikwach
ikwach merged commit 020bc84 into RunTheWall:main Sep 2, 2026
2 checks passed
@ikwach

ikwach commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Thank you for your help! @owlot
Issue was fixed in new relase. Please confirm if this now works as you expect?

Also make sure to check out constly.com
Now its available on every platform and free.

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

Successfully merging this pull request may close these issues.

2 participants