That issue exists because of a faulty controller. If your machine functions perfectly, it is recommended to update to the latest firmware. If you have some exisiting issues with your machine, please contact our support immediately.
i did a firmwareupdate and printed today, the whole day.
The print stops at 99% and it seems the print is finished so far.
I encountered a very similar issue twice today. I just updated the firmware to Snapmaker2_V1.10.0 - the only update I’ve done since receiving the unit in December (I also recently updated Luban to 3.8.0).
As soon as I updated, two prints stopped at 99% and the controller thinks it lost power. The printer sits idle for hours until I intervene (with heat on, bed - not sure if the nozzle is also hot). Im not able to stop the print since it seems to be stuck in a loop or routine that doesn’t end, so I have to shut off the power.
When I power-cycle it goes through a recovery routine and then completes the print (no actual printing, just a re-homing and then it moves to the last position, completes, and moves back). This happened twice today after slicing an .stl with Luban and sending via Wifi (I used the new function to specify IP instead of using discovery since it has been flaky).
@JKC20, @Edwin do you think this is the same issue as xchrisd describes?
-RC
3 out of 5 prints stuck at 99%, how to solve that without cycling the machine (turn off and on)?
This is a bug of V1.10 and we have fixed it in the new firmware and will release it this week.
Best regards
2 Likes
My machine just started doing this… i rebooted it to get it unstuck and it did it on the next print too…
left a burn mark on my 6 hour print. then i went to print my new swatch for a new color and did it again.
Bout to start a longer print now and going out, i hope i make it back before it finishes so it doesnt ruin the print again…
Of course i have the latest firmware and luban, unless a new version came out in December 2020…
Furthermore, i use s3d to slice, luban to send over wifi, then run the file thru the snapmaker screen itself…
The swatch that just froze i printed 3 others yesterday and it didnt happen.
now i have to bounce back and forth between my lab and my computer to start a new print again
any ideas???
Check your end gcode and delete all comments, this was my problem. S3d swapped the comments to the next line and stops the controller.
That was it all right, looks like for some reason s3d cut the comment line in half to a 2nd line out of nowhere.
THANK YOU!
1 Like
This just happened to me. A 36 hour print stopped at 64%! The head is in the home position and the screen looks like it is all finished. There are no pause or stop buttons, only “complete”. Clearly it’s not complete. I have not tried to unplug it yet to take advantage of the power loss feature, mainly because my SM2 thinks it’s done! I haven’t updated the software recently. I was using the USB drive to upload the file (because I can’t connect via wifi any longer - that’s another issue) Was this error ever fixed? Is there any way to save my print?
Out of curiousity, how big is the gcode file
someone reported htey were using like an 80 mb file and it got stuck in a similar fashion
i had printed s similar skull but i scaled it 50%
also what version of firmware are you using
you might be able to ressurect the print with some clever gcode manipulation or using a slicer that lets you pick up from a certain layer.
its a real bummer to see this happen to people 
The file is 73.1MB but I’ve printed files that are 131.4MB before with no error. I can’t check the firmware without ending the print job (unless you know how I can check the system the way it is now). So let’s say I edit the gcode, how would I be able to use that to restart the current print? End the job then upload the new gcode that starts at the point this one ended?
basically, yes.
not a very easy thing to get perfect but its doable.
there was a thread on this topic recently
Simplify3d offers a “start from x height” option, but thats a lot of money. i actually tried it today on something but i messed it up.
I guess I can try it, but to the original thread - is there any solution to this error? Seems relatively common and I saw a post that SM is looking into the issue.
Not that I am aware of, outside of it possibly being a problem with the firmware version being used.
1.9 is supposed to be the most stable, which is not the newest release.
you with almost certainty will not be resuming that print to the best of my knowledge
i have had this happen to me one time, on a relatively small print actually.
some things that might help you avoid this include not executing the print from luban and not being connected to the printer while it prints. you can use luban to send the job but then execute from the screen, or load via usb card.
I could help you with editing the code.
If you want, share the gcode and meassure the very correct height of the current layer.
Thanks xchrisd, but I had to kill the print. Couldn’t let it sit for days, I needed to get stuff printed. Although now I’m having more issues - can’t connect via wifi any longer, and the USB drive SM sent with the printer died (can’t even re-initialize it). Trying to connect via USB but the SM drivers are out of date and don’t work.
Loved this machine for the first few months, but it’s going downhill fast.
On a 21 hour print with about 4 hours left, my 350 was happily printing. I came back about an hour later and the print head was stopped on an outside wall as if it died mid print. The controller was back to the home screen. It no longer showed the percentage of job complete or ETA. The controller was not frozen, I was able to move through the menus and send the print head back to home position. The print bed was reset and was cooling down, almost to room temp. Is there a way to check to logs to see what happened here? I was printing locally off the controller itself from a file I sent from Luban.