3DPrinting

15759 readers

124 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful, especially when disagreeing. Everyone should feel welcome here.
No porn (NSFW prints are acceptable but must be marked NSFW)
No Ads / Spamming / Guerrilla Marketing
Do not create links to reddit
If you see an issue please flag it
No guns
No injury gore posts

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 2 years ago

MODERATORS

Have you ever seen this type of print failure? (lemmy.world)

submitted 1 year ago by nucleative to c/3dprinting

13 comments fedilink hide all child comments

Pretty sure I'm having heat creep up the Bowden tube, as it's getting jammed a few cm back from the hot end and then can't push the filament any more. When I get it out there's a little molten bulb at the filament.

In this fail, I think it jammed as usual and the extruder found a way to keep going.

I tried turning down the hot end from 215 to 200 and it's still failing. My cooling fan is running at 100%.

This is the third time I've had this print fail at about this layer, around 1 hour into what will be a 26 hour print.

Any ideas?

you are viewing a single comment's thread
view the rest of the comments

[–] nucleative 1 points 1 year ago* (last edited 1 year ago)

Thanks for these useful suggestions. I'm learning all about how retractions work now and surprised I never ran into issues like this before.

We are about 4.5 hours into another attempt (previous all failed around 1hr), now with the updated retraction length. It's still going strong. Seems like this is the solution!