This is the second time I’ve gone to resume a long form laser engrave print and it has frozen the next day when I am attempting to resume basically making the past 8 hours its been printing a waste of time. We need a feature that shows the G-Code Line number that the device is currently on on the machine itself and then the ability to resume from a specific g-code line number. This would fix most issues with prints like this moving forward as long as the medium isn’t moved at all. This is getting very frustrating for a 2k machine.
1 Like
Hi grim42,
You can actually accomplish this with a bit of editing of the GCode itself - because I ran into the same issue. IF you’re able to connect to your snapmaker over wifi, it will show the last position (as long as the machine wasn’t “homed” after the failure). Armed with that information you can export the g-code you were using, open it in a text editor and find the coordinates in the file. e.g. G1 X###.## Y##.## where the ##'s are from your luban. Delete everything up to that point (be sure to leave the job details and other GCODE at the top, for example, leave everything (below included) above what looks like this:
; Laser multi-pass, pass 1 with Z = 0
; G-code for laser engraving
; Generated by Snapmaker Luban
; G-code START <<<
G90
G21
M106 P0 S255
G0 F1500
G1 F2500
DELETE EVERYTHING FROM HERE DOWN TO YOUR LAST KNOWN POSITION example:
G1 X###.## Y##.##
Save, load it back into Luban (you should only see the remaining media to be etched)
Send it to the snapmaker and start etching. So while it’s a bit more involved, it’s much quicker/better than redoing a print (in my case that took 20 hours) and it failed with 4 hours to go.
Hope this helps,
m.