3DPrinting

15590 readers

134 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: [email protected] 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 1 year ago

MODERATORS

[email protected]

164

Word of warning to those with Prusa MK4 and Satin beds. There is a chance that the auto bed leveler will mess up and destroy your print surface. (lemmy.world)

submitted 8 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]

57 comments fedilink hide all child comments

I've tried to report the issue to Prusa support but they keeps trying to diagnose it as user error. But at this point I'm at a loss and presume that it's either a firmware issue or a sensor issue on my unit.

Either way im very disappointed.

And before you ask, this is the opposite side

PXL_20240301_160413072

EDIT: I will note that this print sheet is ruined for my use case, since those patterns will be shown on the underside of my prints. But the print surface still works and can be used without issue... if you ignore the gouges that are being detailed into every print.

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

[–] [email protected] 4 points 8 months ago

I caution you to not put too much stock into OPs anecdotal experience. This is not a problem other people are having and is certainly not a firmware issue. I can say for certain that it has never happened for me.