@vicious1 are you using index.html.gz from the repo referenced by Jackpot docs, or a newer build uploaded somewhere, or, do you run a WebUI you built locally (using VSCode + PlatformIO) ? Think Mike and Jason are running locally built WebUI on their machines, guessing VSCode + PlatformIO?
I’ve been following Jackpot docs and using files at https://github.com/V1EngineeringInc/FluidNC_Configs/tree/main/LowRider%20CNC/UI%20V3%20LRCNC including the 6 month old index.html.gz in that folder … Mentioning incase there’s some updates/fixes missing for folks following Jackpot docs? Am not even using Jason’s neat extensions/mods just yet until I understand what I need to do (and not do) to always reliably cut.
Created https://youtu.be/6d5CHlRZiMs shared yesterday to show what I’m seeing, so people can tell me if I’m doing something(s) wrong, and/or, help others navigate the sunny path to success…
- 0:00 Overview/Problem - going to show ways to crash FluidNC, and, how we can avoid crashes…
- 0:30 Details and cause, see https://github.com/bdring/FluidNC/issues/1322
- 1:14 My setup:
- FluidNC 3.8.3 - USB cable from ESP32 to PC to monitor serial comms
- 2:28 V1E specific config and files from https://github.com/V1EngineeringInc/FluidNC_Configs/tree/main/LowRider%20CNC/UI%20V3%20LRCNC
- 2:50 Set IP to 1.2.3.4 for FluidNC ESP32 so my client PC can straddle my home network (ethernet), and connect to FluidNC AP (wifi).
- 4:04
Some JSON scripting/error, not reassuring, but am just ignoring… “Bad control character in string literal in JSON at position…” in scary red error notification popups. Recently fixed by Mike, see https://github.com/bdring/FluidNC/pull/1336. - 4:30 Start a cut job using .gcode file on SD card.
- 5:07 FluidNC crashes when Settings clicked while CNC job active. StoreProhibited fault
- 6:38 FluidNC behavior when network connectivity lost
- 6:55 Distraction… The scary red JSON scripting/error again…
- 7:49 Back to network behavior again…
- 8:50 FluidNC behavior when network down for over 1min (?) “Connection Error. Connection with board is lost. Connect again”.
- 9:50
The simple workaround page FluidNC folks created for 3.8.3+ to help protect a running job:
- 10:50
Simulate less than 30s network unavailable… FluidNC will auto reconnect and continue. - 11:20 Summary/tips… Don’t click on stuff when job is cutting. Configure client to not auto sleep/shutdown/energy-saver/etc… Reconnect less than 1min to avoid seeing the basic 3.8.3 workaround screen.