Halloween bugs and ghost gcode. Won't stop, Can't stop

Troubleshooting
1

Cutting my second file and something weird happened. Also a bee investigated the maslow.

PXL_20251030_181813239
PXL_20251030_1818132391920×1442 278 KB

I got the cut started and things were going well It drilled holes for 3 hours and then my laptop crashed and I had to restart my computer. The machine kept happily drilling. When I tried to reconnect online the computer couldn’t find the web page. I tried with my phone and a different computer and it also couldn’t find anything. I logged into the home router and the maslow was not there. On the running maslow the light was green but there was no blue light. I let it run because I was happy with the holes and it was several hours in. It ran for two hours. I don’t think it was connected but it was just below freezing, maybe a short or something? When I finally unplugged it and restarted it the screen showed nothing in the g code section or on the display of the job but it was unresponsive to any jogging when restarted it all again and eventually when I got it moving I pressed the go home button and it immediately started to pick up the job where it had left even though there was nothing on the screen.

I am now doing ok. This morning It was able to connect to wifi but also unresponsive to the jog commands for a while but when I eventually restarted it enough times I was able to start a new part of the job again I will upload the logs from last night and this morning in case you find them interesting.

Maslow-serial(28).log (4.1 KB)

Maslow-serial(29).log (3.5 KB)

Maslow-serial(30).log (4.5 KB)

1 Like
2

I have seen in the forums, people operating in low temperatures have had belts break. Just so you are aware. I live in a more temperate climate, so can’t speak from personnal experience.

1 Like
3

Thank you. Vinyl does get really brittle quickly here in the winter. I had not thought of that.

4

FluidNC has a limitation that it can’t establish new connections while it is running.

I think that the process of making a new connection while it’s running a file involves too many timing sensitive actions and executing the gcode is also super timing sensitive so if it loses the connection while running a gcode file (like if the computer crashes for example), the machine will prioritize keeping on cutting over reconnecting.

1 Like
5

Thank you. That makes sense

1 Like