My Factory Reset Journey

Hi all, just wanted to share my experience today so that any others trying to factory reset their Maslow can avoid doing what I did!

I managed to connect my Maslow to the local network in hopes to have internet connection as well as connection to the Maslow. The problem was that I couldn’t find my Maslow on the network and it was essentially inaccessible. It was at this point that I decided a factory reset would be best.

I went to the FluidNC-Maslow-Main file I downloaded from GitbHub (GitHub - BarbourSmith/FluidNC: The next generation of motion control firmware) to access the full-install.bat file.
When I did this I came up against the error ‘The system cannot find the path specified’ which lead me down a long journey of trying to identify the correct USB port and installing Python to use the esptool.py file to hopefully stumble upon a fix.

It was then that I came back to the forum to find out if there was an alternate FluidNC-Maslow-Main file that had the win64\esptool.exe file in there. I found Bar’s post on this thread (Maslow #29 BuildLog - #166 by bar) which had an alternate link which indeed had all the files I was needing! Go here first for factory resets!

Here’s hoping that this post helps a Maslower in need!

3 Likes

Also, in case anyone stumbles on this topic looking, there is also a way to reset the filesystem over the air without usb but it requires platformio. I already had it before maslow4 came along, so I’ll refer you to the interwebs for detailed instructions on installing it if anyone wants to try this method. I am pretty sure it requires python and I use it with vscode, which is likely the easiest way to get it up and running.

If you have platformio you can check out the Maslow-Main branch of GitHub - BarbourSmith/FluidNC: The next generation of motion control firmware, from that repository (assuming platformio is set up and your maslow is on the network) you can run

pio run -t uploadfs

and it will rebuild the flash filesystem on the maslow. If your maslow is called something other than maslow.local on your network, you can add --upload-port xxxx with either the hostname of the maslow or the ip address and that will also work.

There are many other targets to build and upload the firmware, etc if you want to play around with the code, but this was super handy for me before I fixed the rename bug. Hopefully someone else will find it useful too.

1 Like