This might be more of a GCODE question, but let’s see what we get…
I’ve been printing my larger GCODE files from my PC through the USB and Luban. (For some reason if I try to parse a GCODE large than 250MB it the console crashes.) Normally this works fine, until the PC shutsdown for some reason. I’ve had a few crashes, but I’ve also shut the d@rnd thing off after forgetting that it was running the print.
It should be possible to recover from this. After all, Snapmaker can continue a print if it loses power or something like that.
Ideally you would tell Luban to start a GCODE at a given line, so it essentially just continues the print, but that’s probably not a feature. The trick would be figuring out which line it stopped at, but if you could do that, getting the print to start at that line should be too difficult.
Is there a way to edit a GCODE file so that Luban would just continue from a specific point so I don’t lose my print?