Results 1 to 6 of 6
Threaded View
-
03-29-2025, 05:07 AM #1
- Join Date
- Mar 2025
- Location
- Taxachusetts
- Posts
- 6
Issue on Q1 Pro happening, bed slams into nozzle during final minutes of a print
On my Qidi Q1 Pro getting great prints and layers, but all of sudden seeing at the very end of a print the build plate suddenly will move up 3/4" and slam into the nozzle. This is happening every end of print now in the final few minutes. I worked with tech, they had me put in a new print config file into Kipper. I simply dragged and dropped the new file print config sent into the appropriate spot in Klipper having deleted previous version. I then ran a whole new auto level routine even did a quick manual check with paper using the onboard interface. The tech was thinking that changing Z height through Klipper can cause this issue I guess, anyways did what they said to do. They said should only change Z height in panel on machine not through Klipper interface, which makes no sense to me. Anways, fired it back up and next print in last few minutes it same exact thing, with only few minutes left print looked pretty much complete all of sudden the bed gets pushed a solid 3/4 inch up fast and into nozzle. Now this unit is printing flawless and running great. There is one weird thing going on when I setup a print...I am seeing a calibration or self test calibration file showing on objects that I add to the print que before slicing on this printer. Somehow this calibration file is being automatically generated and added in Qidi studio when I go to drop files and hit slice. So this cal file I am guessing is being added to my gcode for printing or enables somewhere that could be causing this issue is my guess. Attaching few images of print bed how deep it slams and any other relevant stuff. How does one disable or delete that old calibration file that keeps showing? Has it been added perhaps into a config file or something. Any help on this greatly appreciated. This just recently started. Really think a config issue of some type, somehow getting added to Gcode automatically or something like that.
Login Error
06-10-2025, 06:03 PM in Site Related Discussion & News