I have an ongoing issue with slow/unresponsive browser when using FluidNC. When it is running normal, the status screen is showing updates, basically adding a line every second or so. Then it will pause and sometimes continue or just become unresponsive. Any commands such as jogging or probing can delay a few to 10’s of seconds when this happens. I also see this when running a job and the job will finish but the status will show something less than 100%. One thing I have found that resolves this, at least temporarily, is to refresh the browser. Here are more details of my setup:
LR 4
Jackpot
FluidNC 3.9.1 with UI3
STA mode
Chrome browser on windows 11 laptop
How good is the wifi connection where your machine is? If it has a spotty connection I could see that causing the issues you are seeing.
1 Like
Go back to AP mode to see if that fixes it. This will validate or disprove network issues.
2 Likes
WiFi is good. I have line of site to a net node 30ft away. I don’t think refreshing the browser with poor WiFi would help, but it definitely helps.
I have never been able to get AP mode to work reliably. This has been discussed in other threads that Windows doesn’t like connections without internet. There may be a way to configure this to work better, but I have not been able to do it.
Should be good then. Assuming you don’t have any wires going across the top of the ESP32.
I have had this issue before but that was back in the earlier days. On the version you are running I have not had any issues connecting or staying connected for long periods without ever needing to refresh.
What do you have the polling commands set to? I can see where if you’re sending “?” commands too frequently that could maybe cause issues.
This is what I’m using (auto-reporting every 300 ms with a 30 second manual check just in case):
1 Like
And make sure you don’t have logging set to debug or verbose. That will send way more messages than you need
3 Likes
Where is this located? On UI2 it was on the main screen, but I am not sure where it is in UI3. I looked for it a little the other day, but did not see it.
Settings → ESP3D Interface
1 Like
Could be. Not sure exactly what it does, but if you aren’t currently diagnosing a problem, anything verbose is probably unnecessary.
When it starts to lag, you can also click the little arrow at the top right of the Terminal panel and Clear the terminal.
I don’t think the terminal does any kind of rolling off the back end, so if it’s running for a while, they are likely just piling up
I think Verbose mode for the Terminal is just echoing all the commands that are already being sent.
1 second interval for polling should be ok. You could try auto reporting instead to see if that makes a difference. This means that FluidNC outputs updates when there is something to update at a set max rate as those things happen. Otherwise, you’re interrupting it. At least that’s my understanding.