I turned on my X1C after not having used it for 3 weeks and was prompted to install a firmware update, which I did without issue. After two successful prints, while starting a third (no bed leveling or flow calibration) the machine errored during the homing tool head phase, forcing the print bed up well beyond the nozzle tip, then proceeded to grind deep gouges into the plate until I physically switched the printer off.
As far as slicer settings go, I don’t believe there is a way to change settings to make this happen even if I WANTED to, let alone by accident.
I do have plate detection disabled, and have for 6 months without incident.
The firmware update involved bed leveling as well as numerous other calibrations and, as I mentioned, two prints were successfully completed immediately afterword.
Also, I think I recall seeing a message about the lidar lens being dirty, but I’ve successfully printed despite that message a number of times before.
I have not attempted another print since this happened.
Normally the community would be jumping in to make suggestions but in this case, I think your photo is pretty conclusive. This is one where you really need to put in a ticket if you haven’t already done so. As you pointed out, there isn’t really a way to even force this kind of issue within the slicer short of loading custom Gcode. Let Bambu know. They will ask for your logs though so be prepared to supply those. Please let use know how that works out.
Thanks for your straightforward reply.
I will figure out how to access my logs prior to submitting a ticket and let you know how they decide to handle this.
I determined the cause of this problem on my own, which is the way it should be, considering it was due to my own ignorance in the first place.
My X1 rests atop 4 Sorbothane cushions, one under each foot, to help with noise and vibration. One of them managed to migrate a few inches toward the middle of the machine, compromising the functionality of a threaded rod.
With everything back in place now the printer works fine.
I respect the importance of time and apologize for any you may have been robbed of by my embarrassingly large oversight.
Your input is appreciated, nevertheless.
Thanks!
No need to apologize at all! Honestly, you did what so many of us do—experimenting and learning as we go. Unlike others who might’ve left the thread hanging, you took the honorable route by coming back to close the loop. That helps a lot, especially since so many of us were scratching our heads with you. I’m sure many here appreciate the time you took to share what happened and what you figured out. Thanks for seeing it through!
