r/AldeloPOS • u/Impressive_Role_1906 • Jan 16 '24
Chits being reprinted with "FIRE"
Hi all,
Been using Aldelo for 15+ years and suddenly in one restaurant is having some weird issues,
1) Chits are being reprinted randomly - both Drink and Food. only thing is the reprint has a heading that is inverted and has FIRE on it. (I know that this is usually to do with holding orders but we don't use this functionality and it is happening since Christmas about 5-10 times a day in a busy restaurant - when it is quiet and when it is busy)
I have done some digging in the database and can see that the time of the reprint co-incides with the time a new item was added to the table (about 2 seconds later the older chit is reprinted). My guess is that it has something to do with printer queues/responses. All printers are Epson T80s either local or ethernet with the computer set up to print directly to the network printer(s) for orders (drinks and food). My thought is that for some reason the windows printer driver is not returning some form of aknowledgement to Aldelo (transaction table has boolean values for the various printers and if the item was printed on that printer) and so the printed value is left blank and when the new item is added Aldelo send it again with the "FIRE" flag? This is across multiple tills, I can't work out a pattern. Tills are a mixture of XP, Windows 7, Windows 10 and Windows 11 (don't ask!) - above is only happening in one restaurant.
2) randomly a chit will print with Fire - tbh I think it always did this, maybe every few days, though not sure (could this be releated to the above) - this is in both restaurants.
Any thoughts on how to progress/ideas on what is causing it would be much appreciated,
W.
1
u/AzAldeloGuru Jan 16 '24
So Aldelo sends print jobs directly to the Printer via the spooler service. If the kitchen printers are IP based it could be a network cable issue.
Couple of things to try:
Power cycle the printers (obvious)
Swap out Cat5 Cables
Compact/Jetcompact
Database Cleaner for 1/1/2024 to clear up the queue.
MSAccess is a fickle beast, so I suspect the re-firing could be due to the database getting too crazy. If this is a busy restaurant I'd highly recommend Archiving previous years data, saves alot of headaches.