I installed 1.14 and can no longer access my Maslow 4.1
My router shows that it is picking up a DHCP address, but I am unable to access the web UI and it doesn’t respond to pings. 
Try turning off your wifi from the router and see if you can access the Maslow directly via 192.168.0.1 and if that doesn’t work you could try reloading via the USB port. It won’t have completely bricked the Maslow, more likely a comms problem. Reloading via USB will wipe everything and set it back to “factory” settings.
1 Like
hi, I can confirm. I installed the latest firmware yesterday, of course it messed up my communication because it basically resets.
but classically through his site I set up access to my wi-fi again and had to give a static address again which I gave exactly what I know and this is how maslow works for me when it goes through dhcp the address is always different and basically it never worked for me find.mymaslow it never worked for m
e.
2 Likes
Using a USB cable and full-install.bat worked. Thank you for the guidance.
This is curious tho:
This appeared after the full-install procedure, so I uploaded the 1.14 html and yaml, but the message remains.
Dave
1 Like
Yes, click on ok, it is safe to ignore it, you may have also got some memory low errors, also safe to ignore.
1 Like
that’s a bug with the comparison popup (it wasn’t possilbe to test that well before new versions were actually released as the version numbers were actually different, we didn’t know it was comparing the entire string, not just the version)
Bar has a fix that eliminates the popup and just puts an entry in the log, I have a fix that does a smarter comparison, and will give you an option to not see the warning again until there is a new release, you can try it here
(just finished building, not tested, but the worst case should be that it’s as annoying as the current version 
)
download and unzip the “updated UI” link at the bottom of the page and upload the index.html.gz in there
it will report as something like v1.14-3-gdef456 (to show that you are 3 commits past v1.14 on commit def456 not important unless you are reporting a bug
I installed your merge request file and restarted FluidNC. Got this:
I clicked ‘Don’t Warn’ and then restarted FluidNC again. The Warning was still displayed.
I also did this in Hamburger → Preferences
Then I saved and restarted FluidNC. The Hamburger → Preferences dialog reverted to this
Dave
that last looks like what I would expect, does it continue to give you the warning after that is set?
Yes, I still get the warning. In short, the disable button, either from the popup or the Preferences dialog, does not inhibit further popups after a reload of the Maslow tab from a F5, a power cycle, or a ‘Restart FluidNC’.
Confirming @Dave_Covert’s insisting dialogue/modal issue on 1.14 