My wifi connection from the laptop to the maslow gets lost very often. This often happens during belt retracion and extention. So I have to do it again. But it appears in allmost every moment, even during gcode program running. Leaving the maslow powered on, will cause errors and loss of settings because of disconnecting wifi.
I use a Lenovo Laptop and set the maslow to Access Point wifi. Connection over chrome browser.
This part is very unexpected to me. Loss of WiFi should not cause the machine to lose its settings, it should just wait to reconnect.
To me it sounds like there is something more complicated going on than just the WiFi disconnecting.
Which firmware version are you using?
Here is my system information:
Chip ID: 10444
CPU Cores: 2
CPU Frequency: 240Mhz
CPU Temperature: 37.9°C
Free memory: 59.19 KB
SDK: v4.4.7-dirty
Flash Size: 8.00 MB
Sleep mode: Modem
Available Size for update: 1.88 MB
Available Size for LocalFS: 192.00 KB
Web port: 80
Data port: 23
Hostname: maslow
Current WiFi Mode: Access Point (4A:27:E2:C7:CC:28)
SSID: maslow
Visible: Yes
Radio country set: CH (channels 1-13, max power 20dBm)
Authentication: WPA2-PSK
Max Connections: 4
DHCP Server: Started
IP: 192.168.0.1
Gateway: 192.168.0.1
Mask: 255.255.255.0
Connected channels: 1
18: 56:80:15:36:FA 192.168.0.2
Disabled Mode: Client Station (48:27:E2:C7:CC:28)
Notifications: Disabled
FW version: FluidNC v0.82 (Maslow-Main-63b36223-dirty)
WebUI version: github.com/MitchBradley/ESP3D-WEBUI@6a91cc4
Ok sorry, maybe I have to more precise.
The main problem is, that every time it loses connection, the belt messurement goes lost. The other settings maslow normally remembers.
After loosing connection i could often reconnect to the machine, but there was no possibily to give it commands.
Thanks for help Florian
This isn’t what I would expect. The machine should not lose track of the belt positions just because the wifi connection resets. To me this implies that the machine is restarting entirely which is not expected.
Could it be a power interruption or anything like that?
I controlled if there is a power connecting issue. But every thing looks allright. The green led’s are steady glowing.
Tell me more about this, how are you restarting FluidNC?
By switching to the fluidnc tab in the browser and clicking the red restart power button.
That’s what’s triggering the machine to lose it’s position, pressing the restart power button will make the machine restart and lose it’s location. You shouldn’t need to press that button.
What’s the reason for wanting to do that?
Because often after loosing wifi connection and reconnecting. All the buttons to control the maslow in the browser don’t work. For example, if I push the move +x button with 100, in the command text it says jog x +100, but the maslow doesn’t move at all. The only possibilty I know is to restart after that. Then everything works fine until there is a connection failure.
Is there an other way to reset if the program gets stuck?
Interesting, does refreshing the browser tab help?
Another thing that I think will help is connecting directly to the machine by going to the IP address of 192.168.0.1 rather than relying on the msftconnecttest.com thing, those can be fickle and cause issues
No, by hitting the enter button in the browser command line to refresh there is still nothing usable
Is it possible to eliminate the selfconnecting via http://msftconnecttest.com/ everytime the network will reconnect?
Is this when looking at 192.168.0.1? Can you try holding down control while pressing the refresh button? That will refresh and clear the cache.
I think so but that would be a windows thing I think 
I’ll try tomorrow!
A strange thing is that in front of 192.168.0.1 there is written, that it is an unsave adress. Maybe that’s a problem too?
Does it say the same thing for 192.168.0.1? We want that msftconnecttest.com address to go away entirely
Yes I think it does the same for 192.168.0.1
Have to try tomorrow in the workshop…
Now the wifi connection is relatifly stable. If I use 192.168.0.1 to connect. I deactivated the prompt to reconnect via msftconnecttest.com. But there are still some disconnections.
If the machine gets stuck, I can refresh, holding Ctrl at the same time, this works only for one command. then it’s stuck again. (Video attached). But I’m happy to not loosing belt length.
The unsafe in front of the url ist still there and I’ve not yet managed to get safe.
That is so weird!
I haven’t seen anything like that before.
What web browser are you using?
the only time I’ve seen something like this before is when someone is using the
popup browser for portals, not a full browser instance.
David Lang
