The jackpot board is set up on STA mode and is responsive until I start a run. Once the machine begins to move and is about 10% complete, I cannot longer communicate with the controller. It will not pause, stop, nothing. I’ve tried with a PC, Phone, and Tablet. All platforms have similar results.
I have tried to operate in AP mode and get a similar outcome.
Any thoughts on what I have done wrong here?
First thought i have, do you have dust collection?? There is a post on here that static caused alot of problems when chips started to fly. They grounded tube i think.
One thing I noticed with it is that you have to make sure the display doesn’t turn off.
If the display turns off or you leave the tab, etc, I think the WebSocket closes, and I don’t think it will try to reconnect unless you refresh the page.
However, if you try to refresh the page, it will tell you it can’t while it’s in motion.
You can try disabling this in the settings
If it happens to get in that state, you would be able to refresh the web page. However, I’m not sure what effects that might have, or why that was added in 3.6.8
If it happens at the exact same place on all those different devices, we need to see your gocde and some help with about where it stops. We can look at your code and see what is wrong.
If the windows stays open like Mike is saying you will see the error in the terminal, or no error at all. Make sure the device stays awake.
Thank you for the input and ideas. I ended up erasing and reinstalling the firmware and the response improved substantially.
I now see that the problem occurs when I get a warning message: Low Memory. The device seems to be unable to continue to connect. Is there something I can do about the memory issue?
please make sure you are running 3.7.8 or 3.7.10
These have fixes that are supposed to stop memory problem. Also after flashing, make sure you change the sta mode again.
The only way you should ever see low memory is if you have multiple browsers connected to your jackpot at teh same time, bad wifi in STA mode, or refreshing your GUI screen too often.
If none of those seem correct please describe exactly what you are doing to see low memory warning, and exactly how you are connected.
