I have tried different setting of the WLAN connection, i.e. use the “maslow” WLAN as well my private network. After I began the cut, it takes about 1 min and then I loose the WLAN connection to the maslow and the cut stops immediately. Does have anyone a clue to solve this issue?
1 Like
Usually this is a computer setting. What my guess is is that because the network doesn’t have an internet connection the computer will disconnect from the Maslow network after one minute automatically.
Maybe the next version of the M4 should have a networking router built in so you can connect to the M4 and have an Internet connection. Then your whole home can depend on an Internet connection that is moving and vibrating! 
3 Likes
It not related to the internet connection. Because, I added the maslow to my local router (network with internet) and I tried also the AP of the maslow. Additionally, I switched the computer. Nothing helped. Is it possible to use the USB connector of the maslow instead? Does the maslow actually need the computer running to carve? I did a closer look and it seems now, that the maslow crashes at first and then the connection get lost. After the reconnection I found an “MSG:ERR:Skipping configuration file due to panic” error message. Is there a way to log the error messages in the maslow and read it after the recovery?
I just ran another cut to safe the serial output. Here it comes:
Maslow-serial(15).log (2.8 KB)
For completeness I will add the gcode file. It was generated by easel:
Untitled(2).nc (640.1 KB)
I took a look into the code and it seems that the panic exception is responsible for the reset. Therefore, the WLAN connection is not causing the stop. In my case, the calibration fitness of 0.46 seems to be too bad to make a cut close to the edges.
I ran into a similar problem when I would switch to another tab in my browser. It turned out that my browser had a feature where it would “sleep” unused tabs after a certain amount of time.
Once I turn that off, the problem went away.
Are you switching tabs while it’s cutting?
I think that you are spot on here. The maslow does not need the computer while running, but if the maslow crashes it will disconnect.
Which panic exception are you seeing? It shouldn’t be causing a crash
You can find the “[MSG:ERR: Skipping configuration file due to panic]” within the Maslow-serial(15).log (2.8 KB) file. This is the log file, after my computer was reconnected to the maslow. If I do a hard reset, i.e. power it off and on, the message disappears.
1 Like
Thank you for the tip. I will keep it mind 
1 Like