when printing the model during the calibration procedure, the printer ran into the right near corner of the table when measuring depths and ran into the corner hard. The head-table contact sensor, as I understand the situation, glitched and some loud cracking was heard. I don’t know what it was, I assume the protective mechanism was triggered. As a result, the printing procedure stopped with error 2526 (problem with the Z axis).
I ran the printing again and everything went well. Why it didn’t run into the hole described below, I don’t understand.
During the next print, I found hole in the plate. When starting the print, the head tries to detect the depth in this place, but hits the hole. After that, the printer’s roof goes crazy, the head drives up to the control platform and doesn’t hit it (it’s on the left). Catching error 506 (lidar calibration problem)
I understand that to solve the problem I need to replace the plate with a new one. But I am more interested in finding out the reasons for this situation and how to eliminate/avoid it in the future.
For some obscure reason, after a normal print I remove the printed part and send another one with a printer calibration option enabled, but it all started very oddly.
The bed all times goes up until it reach the nozzle, but this time it went down to the bottom and slammed hard there a couple of times, jumping teeths or god knows what more. After that, it went to the up portion and again, hit the nozzle hard, jumping teeths again and there were nothing I can do to stop it. Stop/pause were not working, probably due to CPU thread timing, and I have to cut the power off.
After that, all went as expected. I have a couple of issues before but this was the worst until now.
The fact is, I started to see a pattern here related to reliability.
After each print, there seems to be issues with memory or who knows what more which causes errors to accumulate, culminating in catastrophic failures as we are experiencing.
I will send an e-mail to creality support to have this addressed and I will share here my findings and solutions, if there is one…
For now, as a workaround of this piece of firmware trash code, I am shutting down and restarting the printer after every single print. Every single one.
