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

Please ask whether node escpos supports parallel port LPT communication printing? Or node escpos does not support parallel port LPT. Is there an alternative? #406

Open
wangshihuyue opened this issue Sep 15, 2022 · 3 comments

Comments

@wangshihuyue
Copy link

Hello, the current ongoing project uses Electron to develop desktop client. The project has printing requirements. Currently, the desktop client supports USB and serial port printing. The customer feedback needs to support parallel port LPT communication printing. Please ask whether node escpos supports parallel port LPT communication printing? If it is possible to give an example for reference, or node escpos does not support parallel port LPT, is there an alternative? Sorry to bother you.

@khetkoong
Copy link

I got the same problem

@Psychopoulet
Copy link
Collaborator

Psychopoulet commented Oct 6, 2022

I had the same problem : for some old printers, there is some stupid rules which give the same VID/PID to the 2 interfaces of the printer, so the package is not able to find which one is for power supply / firmewire update and which one is for the actual escpos communication.

there is no solution, because it's at the binary level of the usb package : libusb does not support that.
it give us the flag at the interface level which identify the 2, but it's unusable 'cause the call is on VID/PID

so, you have to install a software which emulate properly new 2 different VID/PID (my choice) for these interfaces, or by a more recent printer which has 2 different VID/PID

@khetkoong
Copy link

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

3 participants