Here is another output I forgot to send you
Sequence was
Start calibration (90 points)> console list points > machine moves to all points and operates belts > console never updates with waypoints > process appears frozen on console with nothing recorded > after 10 min console says
$J=G91F1000X-100
I’m pretty sure it was 65. I remember reading about the improvements.
Regardless I’ll redo it to be sure!
Already added in the next version
0.65 adds a feature where if it gets disconnected, it will finish the computation when you reconnect so if you get to the situation where the calibration is finished and nothing has showed up in the console, you could try closing and reopen the browser. It might automatically start the calibration process once you do.
I need to do more testing today with what happens if the Wi-Fi connection goes down during the calibration process. It should be robust to the computer turning off, but I don’t know about the Wi-Fi network.
This has been added in the nightly release 0.65.1 and will be part of the full Wednesday release.
I did some testing with it and I’m excited to share that if the wifi connection goes down the machine will automatically reconnect, you just need to refresh the browser window to re-establish the connection from the browser.
I found the issue here…and it’s super pedantic. Apparently we can’t have space after the numbers or it will fail to load. 
I could work on making the FluidNC yaml parser more robust, but I think that the real long term solution is that we need to get rid of editing the file entirely. It just creates too many opportunities for something silly to go wrong.
Thank you for helping to find that. I will bump making the calibration process not require editing that file up on my todo list and I will now know what to look for in helping someone else with the same issue.
The good news is that the calibration process seems to recover well from a loss of WiFi connection in the middle of the calibration process (which I think is what you were running into). I made a quick video to show how I was able to get it to recover:
One last thing that I did was to turn my shop wifi off completely and double check that calibration works without an internet connection by connecting directly to the maslow wifi network and that worked too so that is an option also.
This is really great. Thanks for all the effort.
I didn’t realize there was an option to reload the page without killing the whole thing.
It had been doing exactly what you described- moving though the points and stopping on the last with no further activity.
I’ll try this afternoon!
There wasn’t until last week. I added that because someone else asked for it…I just do what you all tell me to do and you have lots of great ideas 
To chime in for future users. I did get this same error with the file name being maslow.yaml.
Combed through the code and found an extra “.” in one of my parameters. Removing that solved the problem.