A setup we did recently is using a kitchen display based on the Bump Bar tutorial:
It’s being used as a coffee screen to show coffees to prepare and in a very busy restaurant (each day they serve 300 or more hot drinks during their morning peak period alone).
I’ve used the same setup a few times before and haven’t had issues.
I’ve got a very strange issue where on the coffee screen system the Task Editor widget is not updating automatically. I have “Auto Refresh” turned on and have tried the “Auto Refresh Interval” at both
0 and higher numbers, such as
Tasks are being created, they show in database and I can “force refresh” the entity screen by either entering and exiting Design mode, or by marking a task as complete then recalling it. Then all the new tasks appear.
I cannot get to the bottom of the issue so here is more info about the setup and what I have found and tried so far.
Using SambaPOS v5.2.14 with SQL Express 2017 database.
Server system running Win 10 64 bit, with SQL Express 2017 and Message Server. Message Server set to run under an Admin Windows user account.
4x POS terminals, running Win 7 32 bit
Coffee screen system running Win 10 64 bit
Everything connected on same network, all wired connections.
When I first set it up, it worked fine, I was placing orders on the server computer and they were showing up almost immediately on the Coffee Screen.
When the system went live, my client reported the coffee screen wasn’t updating. Upon checking, only the server computer orders would show automatically. Any orders from other POS terminals would not show. I restarted everything, then after a few minutes everything appeared to work fine, and it worked fine with all terminals updating the coffee screen automatically for about 5 hours, then stopped working again. I could still place orders from server and they showed up automatically, but none of the POS terminals would update the coffee screen.
I disabled Windows Firewall on all systems - no difference.
Message server is connected on all terminals and entity state updates for table status show instantly on the table entity screen across all terminals, so no issue with those types of updates.
I started to think it was an issue with the terminals connecting via message service given the orders placed on the server computer (where message service is installed) would work.
Then I looked into what the difference was between the terminals and the server. I found out that all the POS terminals and the coffee screen were communicating between each other using TCP/IP v6, whereas between the server and all terminals and coffee screen was using TCP/IP v4.
I thought possibly Message Service is incompatible with TCP/IP v6, so I disabled v6 protocol on all systems then restarted them to force them to use v4.
After this, everything worked!..I thought I had found the cause… however it was short lived, after a few hours, the same issue started again and the coffee screen failed to auto update again…
I set all terminals, coffee screen and server to use static IP, and specified message service on all terminals to use the IP address - no difference.
I tried running the coffee screen on all the terminals, and sometimes it would update automatically and sometimes not, there was no reason or logic as to when it would update or not. Eventually it just didn’t update on all again for a while.
So I gave up on it - the client is very busy and with the volume of orders they can’t cope peak periods without the coffee screen. SambaPOS replaced another system that had a coffee screen, so staff were used to this workflow. They gave an ultimatum that they would have to revert back to the old system if it wasn’t resolved quickly, so I took the drastic approach to rebuild the coffee screen using Ticket Lister, which all worked fine with updates, but they need the “bump bar” (keyboard) to update as they don’t use a touch screen, it’s a 27" monitor mounted up high and their old system had a bump bar too. So currently although I replicated the coffee screen as Ticket Lister, it isn’t working ideal and I have to have many workarounds and still not implemented a way to navigate by keyboard, which is sometime I will have to do (I have ideas…) but I would rather not. It’s going to have to be a whole load of SQL reports and custom scripts to assign 1-9 numbers to the recent tickets and I can’t imagine it will work well performance wise, even with tests after having just about 20 tickets on the screen the screen slows down. Plus I then run into a whole load of other issues about updating tickets, reopening settled tickets to change a ticket state and those events won’t all run in background and flash the screen when updating. That is all a different matter and irrelevant to this topic…
So I want to get the Task Editor coffee screen working properly and auto updating correctly. I really need some help, @emre what could be causing this? What else can I try? Is there any debugging options I can enable to understand more about the messaging and where it is going wrong, or can you implement a way to debug it better so we can get to the bottom of this?