Extruder gear is not working

Hi there,
I just received Snapmaker 350 and I have a big issue : the extruder gear is not working.
It just works transiently, like a few seconds at initialization, just enough to partially load the filament and then it stops rotating = no sound anymore and no extrusion.
Preheating is done (200°C), and manual loading work, but extruder gear do not.
No clogged nozzle either, because its my first print and the manual extrusion works.
Then I decided to load the filament manually and launch a printing.
What happened : no extrusion but the gear litteraly burned the print sheet !!
I am veeery disappointed (cost+waiting time+not working)

I sent a request to the support, but no reply for now.
What should I do ?

Thank for your help !

Could you post a pic with what you mean that the gear has burned the printsheet?
Did the Nozzle plunge into the Prindbed?
Did the Filament drive rub thought the filament because its not engaging correctly?


Sure ! So here you can see 2 things : 1. that the printsheet actually melt (and this from the beginning, at the corner of the sheet)
2. until it finally pulled the printsheet and displaced it of about 5cm (thats why you see the second print). I just stopped the printing at that point.

may I think that the melting is due to the absence of extrusion ?
or this is a second non related issue ?

Having the same issues. Gear is spinning but it’s creating shavings inside the head. Not grabbing the PLA (snapmaker black w/ kit). Odd thing is, the program always prints the the skirt and first layers fine, even after manual loading malfunctions (It will quit extruding after 1 or 2 manual load cycles @ 205 C)

Also note: I had 2 successful test runs. Everything stopped after that.

There’s a few things that can be wrong here.

  • Looks like the nozzle was too close to the bed, there should not be the line from the bottom left corner, because the nozzle should be above the bed. Double check the calibration when it’s cold, before the print starts the calibration card should be ‘snug’ enough so the card will bend if you lift and push, but not so much you can’t pull the card and slide it back in again. That should be the case most all places on the bed too, within reason (the calibration isn’t perfect, it can’t measure the entire surface of the bed, just a few points).
  • If the nozzle is too close, the extruder won’t be able to force filament out, or will do so but then clog.

Sorry about your bed. At least it’s large and double sided so there’s other places to start prints until you can get a new one.

@dukejunior That’s a weird issue, might be the same, partial clog in the nozzle?
You could try doing a cold pull.
You could also try taking the hot end out and looking through it with a flashlight, see if there’s any shavings building up inside? Might be able to knock some chips out, or clean it out with a small wire.

Thank you for your reply
z position is ok
still cannot load the filament …

https://webmshare.com/VrMVP

this new try after changing the heating head …
I am pretty desperate

could it be a safety stop of the gear ? because of temp problem or non detection of the filament ?
any way to make a diagnosis on Luban ?

@allthatglitter I guess, because of your video you are connected to the right port “Toolhead” and you used the 8-pin connector cable, right?
There is no need of the filamentsensor at the loading process, loading works also without filament.
You need at least 175°C, i guess, to prevent cold extrusion, but that´s all.

What happens if you use a other toolhead, do they work proper?
I would suggest you to write a email to support@snapmaker.com , because you are not able to load filament with the stepper motor of the print module.

Your Z-offset is too tight, you have to get far more away from the bed.- This issue caused your displaced print sheet.

@dukejunior you didn´t have the same problem like @allthatglitter
If you have read the post proper, you would know that.

You are too near to the bed, increase your Z-offset, do some searching in the forum about and please don´t occupy other posts if they don´t have the same issue.
Here is the first hint:

This is solved by firmware i guess: