I have a few programs that I run that will run perfectly on my Longmill MK2.5 and then they consistently will freeze the servos at the same spot. I am able to hit pause in gSender and then wait a few seconds and hit play to restart the carve and it will finish the carve.
This error thankfully doesn’t ruin a carve but it is annoying. I have tried to recreate my gcode from Easel (I am going to switch to Vcarve soon) but I end up with the same hangup. I have looked at the ggcode for any lines that could cause this freezeup but I don’t see anything abnormal.
The programs that this occurs on are seemingly random. With every new carve I have to be cautious it may not finish. gSender will show 1 line remaining every time it freezes. I’m putting this in the gSender category because the programs if run through Easel will not freeze up. This seems to be a gSender bug but it happens on random programs.
Let me know if you need code snippets or have any questions that may help with this error. It’s not a critical failure just an annoying one.
This is the first program that I noticed the I probably gave more code than needed but I have looked at this for awhile and maybe someone can find the issue.
@kpeoples86 From my meagre understanding, the G4 command is a pause execution command. The P says for how long. You may want to delete that line and try to run the project again. Just run it in air to see if it will run to the end.
@gwilki I removed the last line and ran the program from a starting position about 800 lines from the end and it did not freeze. I noticed on all my programs that have been downloaded from Easel the last line is always G4 P0.1. My guess is that is has something to do with how gSender buffers the lines of gcode as it is carving and maybe the chunks of buffering if it ends on the G4 line may cause the freeze or hangup. I have never watched the console screen as its carving maybe I can try to catch the issue in real time.
Let me know if my theory is plausible but I will start deleting the last line on every program and hopefully the issue goes away.
@kpeoples86 I’m glad that this simple solution resolved your problem. I am not competent to reply to your theory. I suggest that you write to sienci tech support, linking to this thread.
In the meantime, as you have the solution, I am closing this topic.