Wake up! (Lowrider)

Okay, so I’ve experienced this a few times now with my Bumble build. I haven’t used the LR32 enough to know if it has the same issue but could run a test to find out pretty easily I think.

Bumble runs in AP mode, not connected to my home wifi network so when I need to run a job I fire up the Jackpot, try many times to transfer the file (it fails a lot but eventually does transfer…but this is a whole other issue). When the machine is running, if the MacBook screen goes to sleep (only the screen, it’s not the whole machine that goes to sleep) all motion on the LR stops. Wake the screen with a wiggle on the trackpad and the machine resumes all on it’s own. Now, if the MacBook does go to sleep it loses it’s connection to the Jackpot. The network still shows in the “available networks” but if I try to connect to it, it keeps failing on the authentication (won’t accept the password).

Here’s the weird part. When the screen sleeps, the machine pauses. When the MacBook itself sleeps, the LowRider keeps running. But I no longer can control it (pause it, stop it etc) because I cannot connect to the Jackpot.

Maybe AP mode isn’t a good idea in my case? My router is one floor directly above the shop and the signal is strong. I could just run the Bumble the way I run the LR#2.

Thoughts anyone? Has anyone else experienced the same?

That’s really weird. What version of FluidNC is on the Jackpot?

I know that the FluidNC developers don’t support/recommend AP mode other than for configuration to the point that they recommend STA mode using a standalone router if you can’t access your normal one. I’m not sure that has anything to do with this though.

Bizzare. What version of Web UI are you running, and have you customized anything there?
Seems like you have something client side running that is interacting with FluidNC in some way.

I’ve never seen FluidNC do this.

I have not seen this either, but I use STA with my Jackpots. Like Jason said, the FluidNC developers tell everyone not to use AP mode. I also have a FluidDial, which allows me to pause, cancel or resume.

Turning off all “display sleep” and “disk sleep” etc allowed me to run the whole 26 minute file without hiccup but I’ll reset everything and record the phenomenon so it’s at least documented. And then I’ll get it on my network and ff AP mode.

3 Likes