Peter Alcibiades wrote:
On Monday 01 February 2010 09:46:18 Wayne Stallwood wrote:
..... If the printer is configured as a raw device in cups and raw support is enabled then you should be doing lp -dprintername temprint.txt
Then cups will manage the task of spooling the job until the printer is online and it should all be managed properly.
I see this is for a receipt printer because you are sending cutter and drawer kick commands, you aren't hacking receipt printing support onto phppointofsale are you ? If so I probably still have the stuff from when I did that about 4 years ago, no doubt it would need updating and it is so nasty it never got accepted as a patch to the main project :)
Yes, now I see. Finally! I'll have a go with this. It makes sense.
It is a receipt printer, but the POS is my own hack. It works, but I'm painfully aware that it lacks a lot (all?) of the stuff professionally designed POS systems have.
Ahh fair enough, given the state of phppointofsale last time I saw/used it that might be a good thing :)
The reason why I am using a raw printer is money - the one we bought cost £40, new but discontinued model, and one from the same supplier that would be new and run in CUPS in native mode would have been a couple hundred. The difference was important.
I was using an Epson TM88 which I think initially I had configured in CUPS as an LX series dot matrix (not that it actually matters if you are only going to print to it as a raw device)
I've just emailed you the section of PHP where I hacked in the receipt printer support in case it helps you understand what I was up to. Remember if you don't specifically specify the printer as a raw one then you can still send a raw job with -o raw. You just need to make sure the mime types are configured in cups to support raw jobs.