Snapmaker 2.0 Freezing Mid-print

I received my SM2.0 A350 on Wednesday. I had an initial issue with the calibration as it dropped down and seriously gouged into my build surface, but I was able to get it to not jam into the bed by reseating all of the cables. I am curious if it is supposed to actually press into the bed, causing thew bed to bend down slightly (light enough that it doesn’t mar the surface) when calibrating, or simply get very close without touching it.

My main issue right now is that the print stops, and the system seems to freeze. Most often it freezes before the skirt is completed. The other times it freezes partway into the print. When it freezes I’ve tried to adjust the z-offset via the touchscreen to see if anything would respond, but it sits there. The system does nothing else until I power it off and turn it back on.

I have tried flashing the firmware again. I have reseated all the cables multiple times. I have tried transferring via wifi, serial, usb stick, and even tried different usb sticks. I also tried multiple different files, including the one included. In almost all cases, the same result.

I say almost all cases as yesterday, after a round of firmware flashing and cable reseating, I decided to try to print with the heated with the temp set to 0. This print completed. I then tried one of my original files from the previous night, no heat on the bed, and it completed. Now I had a possible avenue to look at for why things failed, so I tried the same print again with the bed heated this time. I did expect it to fail, but it completed. That certainly shot my theory at the time right out the window.

Thinking that maybe the issue was resolved, I tried a print I’d been wanting to do, something rather simplistic, and it froze when laying down the first layer.

I do have a support ticket open, but I figured I could cast my net wide with the Community as well since it may be a bit before I get further responses from support with the weekend and holiday coming up soon.

Any advice or suggestions would be appreciated.

Edit: I should also add that after it would freeze, I’d check the Controller and the light on it was still breathing.

It’s clearly not supposed to push the nozzle into the bed when doing the calibration. They have chosen the proximity sensor for a reason :). Just move the sensor down a little bit as you’ve already seen over here: Calibration pushing deep into buildplate

I’m still on my first print and have no issues with freezing. Could you upload your model so someone else is able to test? There are also online-services which do repair 3D models. Just google for them, there are a few out there. The model may be corrupt which could produce bad g-code.

Hope this helps…

Yeah, I plan on checking the sensor once I get home. See his post made me think to go ahead and post the other issues I’ve been having as well to see any advice.

The models it was freezing on were calibration cubes from thingiverse, and even the vase from the Luban sample projects. I tried numerous files as I thought it could be a broken model as well. If it hadn’t printed fine with the same gcode, or hadn’t failed on the sample model, I’d have been thinking I just had poor luck in choosing models.

I’ll grab the model when I get home in an hour or so and upload it.

As requested, these are the two different cubes I tried. The 20mm one is the one I mentioned worked. CHEPCalibrationCube.stl (17.9 KB)
20mm_calibration_cube.stl (6.7 KB)

I have this same problem with the random freezes.

I almost had a work around by relying on the power failure recovery but it’s a little “sketchy” and could cause the machine to hit your print depending on the build location. But if your print is small on on the back side of the build plate it might work. Just unplug the machine and plug it back in again. The print recovery will try and resume the print.

I’m having other issues with the tool head thinking it’s not connected. I have to turn it off and back on again to fix that too.

What model of machine do you have? I’m also glad to hear that this issue is not just isolated to me.

My auto-recovery was working, but the last few rounds have seen that feature not popping up. Not sure what’s happening there now.

Hey. Kerrida. Could you please record the info in the touchscreen when the machine stops working?

Hi Dengpeng,

I had sent a link to a Google Drive in through my ticket, but I can post it here as well.


Hi Kaeli, it’s Edwin here.
I am sorry that we are still working on this issue by our side.

It seems like that the main controller cannot commute with the touchscreen successfully.

Please try one more time to check if the cable is inserted in the main controller firmly.

Unplug it and re-plug it firmly, then try to print a small model.

Hello together
After 3 months of enjoyment and successful work with all 3 modules is before
3 days ago exactly the problem occurred with me.
First a work with cmc was not finished, the machine just says stop and light off. On the touch screen could enter commands, but none was followed, neither light on nor move any axis.
So, and after 20 seconds on again.
The job could not be processed any further. I made the rest by hand.
I switch to the 3D module but no matter what job I want to edit, small or large, old or new, always the same.
The machine heats up, starts and stops after a few minutes. Machine stop, light off and freeze.
I work with housing and the firmware Snapmaker2_V1.10.0.
Subsequently, I have changed to Snapmaker2_V1.9.0 and Snapmaker2_V1.8.0.
I have plugged and unplugged as enpfohlen, unfortunately all without success.
I will now try the whole thing with the laser, but have little hope and believe that my controller is defective and be replaced.
Will probably have to contact support.

Translated with DeepL Translate: The world's most accurate translator (free version)

Hello Edwin,

I have been trying 3 d printing since a month now and i am a fresher in this interesting field. I today experienced random freeze today , the job timing was 22 hours and unfortunately may be due to power loss the printing may have halted. Now when i see the screen i was surprise to see the recovery screen is not displayed. Hence now i have no option but to restart the same program.

Also is there any relation with the work speed since the work speed was 150% and are there any guidelines for work speed.

As per my views when the program is for long time the printing should auto recover in case of power loss condition. Now only option i see is to install a UPS.

Can i expect some solution on this, i have the latest version on the system.

Power recovery and runout recovery ONLY work if you start the job from the touch screen.

If you used the touch screen to start the job, then you have found a bug.

Please send me the log files and the G-code file to me for further investigation. Tell me the approximate time when the issue happened.

You can export the log files from the touchscreen and here is an image for your reference. You can find the log files in your USB stick and please send them to me.

1 Like

Hello Edwin, good morning.

Thanks for quick reply. also noted the reply from IT maze, that auto recovery works only when we start the printing from touch screen, true may be since i started the job from PC after wifi transfer. anyway i am installing a UPS today since i have a job which shall work for 48 hours.

were can i get the log file? the G code for the job as attached.

tray-cavity-3-4-trail-final_49039069.rar (1.0 MB)


find attached the log file note , the date of the file is 2098 :wink:

SC_0.rar (187.4 KB)

Hello ITmaze,

that’s a very good observation and feedback, true i had started the job after transferring the file via WIFI and started the job from there.

Then filament run-out and power save should work.
It’s only when you’re running from with Luban that it doesn’t.
As long as you’re starting and controlling from touchscreen it should be okay, but it doesn’t always.

yes , true you stay guessing if it works or not

Had a similar experience yesterday, started a CNC job and it stopped mid way, didn’t reset, didn’t home just stopped with rotation off and the cutter still in the wood.
I had transferred the job via wifi and started it from the console.
I started the job off and was not even in the same room as the machine when it stopped (it’s monitored from a camera). Nor was I doing anything remotely though Luban was open on my laptop but not connected. Thankfully it was a CNC job so I just started it off again and it cut air until it got to where it failed then continued on.

Looking at the logs the Touchscreen had an application started even at 15:53:12 - for no apparent reason which generated a screen plugged in event in the Firmware logs that stopped the job. Hope this issue gets resolved soon.

Firmware version V1.10.1_20200822
Touchscreen 1.10.0
Controller V3.2.2

Relevant part of the logs below
1611071075071,2021.01.19 15:44:35.071,INFO,SC,Start print.
1611071075093,2021.01.19 15:44:35.093,INFO,SC,Print started.
1611071075102,2021.01.19 15:44:35.102,INFO,SC,set line number takes 1 ms
1611071141534,2021.01.19 15:45:41.534,INFO,SC,line 1000: G1 X29.854 Y24.805 Z-1.161 F100
1611071199354,2021.01.19 15:46:39.354,INFO,SC,line 2000: G1 X29.275 Y27.485 Z-4.000 F400
1611071259319,2021.01.19 15:47:39.319,INFO,SC,line 3000: G1 X30.506 Y26.006 Z-6.756 F100
1611071323399,2021.01.19 15:48:43.399,INFO,SC,line 4000: G1 X39.616 Y68.669 Z0.610 F100
1611071382504,2021.01.19 15:49:42.504,INFO,SC,line 5000: G1 X39.356 Y68.501 Z-2.652 F100
1611071441564,2021.01.19 15:50:41.564,INFO,SC,line 6000: G1 X39.221 Y68.311 Z-5.911 F100
1611071499380,2021.01.19 15:51:39.380,INFO,SC,line 7000: G1 X69.668 Y128.627 Z1.818 F100
1611071592681,2021.01.19 15:53:12.681,INFO,SC,Application started!
1611071592791,2021.01.19 15:53:12.791,DEBUG,SC,Reset overrides.
1611071593247,2021.01.19 15:53:13.247,DEBUG,SC,HTTP server started.
1611071593290,2021.01.19 15:53:13.290,INFO,SC,Connecting serial port…
1611071593347,2021.01.19 15:53:13.347,INFO,SC,onConnection, connected = true
1611071593348,2021.01.19 15:53:13.348,INFO,SC,Enable heartbeat.
1611071593362,2021.01.19 15:53:13.362,DEBUG,SC,Machine model 3, size x 345 y 357 z 334
1611071594366,2021.01.19 15:53:14.366,DEBUG,SC,Head type 2 found.
1611071594584,2021.01.19 15:53:14.584,DEBUG,SC,Route: Create HomeFragment
1611071594587,2021.01.19 15:53:14.587,DEBUG,SC,Route: Create LauncherFragment
1611071598118,2021.01.19 15:53:18.118,DEBUG,SC,Wi-Fi connected.
1611071598123,2021.01.19 15:53:18.123,DEBUG,SC,Start checking new version…

1611071075091,2021.01.19 15:44:35.091,INFO,SC-FW,SC req START work
1611071075092,2021.01.19 15:44:35.092,INFO,SC-FW,SC req -> Sucess
1611071593345,2021.01.19 15:53:13.345,INFO,SC-FW,success to create marlin task!
1611071593356,2021.01.19 15:53:13.356,INFO,SC-FW,success to create HMI task!
1611071593358,2021.01.19 15:53:13.358,INFO,SC-FW,success to create heartbeat task!
1611071593360,2021.01.19 15:53:13.360,INFO,SC-FW,Screen Plugged!
1611071593365,2021.01.19 15:53:13.365,INFO,SC-FW,SC req Exception
1611071593369,2021.01.19 15:53:13.369,INFO,SC-FW,SC req enclosure sta

I am excited to see Edwin wants to see your log that means they want to address the problem :smiley:

1 Like