Resuming a "Print from Luban"

Snapmaker Luban
1

Using Luban 4.2.3 and using the print from Luban over wi-fi because the console crashes when it tries to load the model.

Anyway, it’s a 2 and half day print and it was going find for about 30 hours when the filament ran out. Usually, when printing from the console this is simple load the new filament and go kinda thing, but when running from Luban it doesn’t prompt for loading new filament and the Load/Unload buttons on the screen interface aren’t responsive. Attempting to use the touchscreen gives me a message that disconnecting will abort the job.

Any thoughts? I’d hate to waste the 300g of filament I’ve already put into this print

2

You can try to edit the gcode, if you can figure out what layer you left off from.

1 Like
3

I could help you editing the gcode if you measure the exact height of your model by not moving it on the bed at all and sharing your gcode.
There are a few threads in the forum about resuming prints.

1 Like
4

Hit the pause and the printer head will move to the home position. In Luban make sure the hot end is still up to temp 200 degrees and the load/unload buttons should be available for use. Load the new filament and then hit resume.

5

Interested in this. The disconnection thing seems like the same thing mine is doing

6

Thanks, wish I’d seen this answer before I tried it myself. I must have messed up the restart line because it ran for about 5 minutes and then tore the print off the bed. :face_with_diagonal_mouth:

7

I had a “wooden” train bridge clog part way and carry on air printing so I stopped it, measured the height, went into cura/luban and worked out which layer that was (removed one extra for generosity) and started a new print with the first few hundred layers removed (included normal header code to home) and started from the line where the z-height was mentioned in a G1 command, just above a layer number.
When I started that it clearly was about to crash into the model by about 1cm so I added about 1.3cm and tried from that point of the GCode file, and it worked (PETG 235c). There was a visible minor step on two of the four walls, but one was almost seamless.
I actually had one more attempt first where I left out the homing commands, let’s just say that was also a quick turn off at the mains, it needs the homing command to understand x0 y0 correctly again

1 Like