Which config.yaml?

I am building a LR4. With Jackpot controller. I am having trouble jogging. Reading the posts here, reloading the config.yaml file is frequently listed as a troubleshooting step. The links point to the github page. That page has the file for v2 and v3 but not v4. The v2 file appears newer than the v3 file. Which should I use?

I only see two. V2 is older and working well, V3 is a newer version of the webui that should be stable but hasn’t been widely used. The config yaml should be the same for both.

Hey! Assuming you are on this page:

… I think there, the “v2” and “v3” are not referring to LowRider version numbers, but rather the FluidNC webUI version numbers. I think that WebUI v2 and WebUI v3 are essentially the same in basic functionality, while v3 has some new support for things like skins and extensions.

1 Like

I should have added: if you bought your Jackpot from Ryan, it came preloaded, and I think that means it came with WebUI v2.

Thanks Doug. Way too many V’s. Turns out my problem was with my Computer/Browser not working with the Jackpot web page.

1 Like

What was the issues and what was the fix?

1 Like

I was using a Surface Go Tablet, Win10. I could open the Fluidnc.local, but the Jog dialog would not work at all. The command prompt would work. $H started the home cycle, but Y0 stepper did not run. Y1, X, Z1 and Z0 did run.

I think the Surface had the browser locked down enough to block the Jog. I tried my iPhone and a Android Tablet. Both worked. Y0 also started working. I also changed SD cards, don’t know if that effected anything.

Completed a home cycle. On to Squaring tomorrow. I think I am over the hump.

1 Like

That is STA mode, I have not used that very much to confirm, but in AP mode some browsers give you a popup captive site, and you can click “use this site as is” and open up a full browser and the controls are much better.

I told the tablet to forget Fluidnc. Reconnected. Got the redirecting to captive web site. Did not get the black ‘syncing with esp32’ message. The move control still would not work. The Surface Go, when I got it from Microsoft was very locked down. I think there maybe a ‘don’t run child app’ setting somewhere.

I tried with a newer Surface and it worked fine.

Thanks, Mark

closing old topic to help fight spambots