3DPrinting
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 
Moderation policy: Light, mostly invisible
view the rest of the comments
The only thing other than the temperature change I changed between the previous print and the fateful one was I pressed the auto level function on the printer. Then I homed the printer again, and printed.
Okay, so by running the auto-levelling routine, you will have reset the printer's coordinate system. Sounds like it maybe ended up thinking that the bed was lower than it actually is, and therefore plowed into it. If the bed wasn't at the absolute limit of the allowed z-axis travel, the limit switch might not have engaged.
On the model of printer I have, plowing the bed is usually a sign that the sensor in the print head has gotten displaced before or during levelling, so check to see if yours looks crooked or pushed back, or if any wires that should be stuck to it have come loose. It might be useful to know what kind of sensor it is—the one in my printer triggers on metals, so it's possible to test it with a coin and see if the attached LED lights to indicate that it's working.
I suppose it's also possible that the autolevel data is somehow not being correctly saved. Your printer may or may not have some method of inspecting the saved data (and it might be anything from a neat GUI to "pass this gcode through a serial console").
Inspect the gcode of the print you attempted for weird z-offsets if you know how, just in case it was telling the system to start printing at -10Z or something.
Manually leveling the thing might be worth a try if it offers that option.