Close



Results 1 to 6 of 6
  1. #1
    Student
    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.

  2. #2
    Super Moderator
    Join Date
    May 2020
    Posts
    705
    Could be that only Qidi tech can solve this, however perhaps try a print using Prusa or Orca slicer to see if the result is the same. How old is the printer? If still in warranty and problem not solved try for a replacement or refund.

  3. #3
    Yeah, that was going to be my advice as well, see what you get with a different slicer.

    When this happens you say it is at the end of the print, like how close to the end? A few layers, a few CM, how close to the end is this happening?

    Is it any print you generate using your current slicer, or do you keep trying to print this same part and it fails? Are you near the maximum height for your printer?

    Have you looked at the sliced file code? You can open the file with Notepad on your PC or laptop. The structure of the sliced part is fairly simple and follows a pattern where you can see the elevation change layer by layer. It would be interesting to know if all of the layers progress in elevation or if they do to a point and then bottom out for some reason.

    Let us know what you find.

  4. #4
    Student
    Join Date
    Mar 2025
    Location
    Taxachusetts
    Posts
    6
    Yeah was kind of thinking that when I was typing. Will run in Orca slicer. I am pretty sure somehow that code is getting added to Gcode into prints causing issue at end of print.....it was printing fine all week and that cal was not showing in those prints. Not sure why all of sudden the cal file shows in them again.....going to hunt cal file down and delete off of computer. Thanks all. Will post update.

  5. #5
    Student
    Join Date
    Mar 2025
    Location
    Taxachusetts
    Posts
    6
    Quote Originally Posted by Bikeracer2020 View Post
    Could be that only Qidi tech can solve this, however perhaps try a print using Prusa or Orca slicer to see if the result is the same. How old is the printer? If still in warranty and problem not solved try for a replacement or refund.
    Will give that a try, reading my own mind that I need to try in different slicer first. It still printing amazing that slam into nozzle has to be that cal file appearing in gcode is my thoughts. GOing to hunt down where I saved that cal file....

    If works in Orca will just stick with Orca which I love. Qidi studio and ORca the same core.....
    My plus 4 can print that plate no issues, and that cal file does not appear on Plus4 so somehow associated only with my Q1 which is probably one that cal was run on at some point few months ago...For whatever reason, that cal file is getting activated with prints on the q1. Thanks!

  6. #6
    Student
    Join Date
    Mar 2025
    Location
    Taxachusetts
    Posts
    6
    Quote Originally Posted by VidJunky View Post
    Yeah, that was going to be my advice as well, see what you get with a different slicer.

    When this happens you say it is at the end of the print, like how close to the end? A few layers, a few CM, how close to the end is this happening?

    Is it any print you generate using your current slicer, or do you keep trying to print this same part and it fails? Are you near the maximum height for your printer?

    Have you looked at the sliced file code? You can open the file with Notepad on your PC or laptop. The structure of the sliced part is fairly simple and follows a pattern where you can see the elevation change layer by layer. It would be interesting to know if all of the layers progress in elevation or if they do to a point and then bottom out for some reason.

    Let us know what you find.
    This is any print I setup on Q1 only in QIdi studio.....that cal file keeps showing in the slice.....so pretty sure that is root of all evil. Unit is printing fantastic as usual and quiet as always......I have four other printers none do this in studio...so it must be that Q1 used that cal file at some point. Will find that cal file on my computer delete all traces and may have to do hard reset on the Q1, but will try Orca first see what happens. If Orca runs no issues, then Q1 can just stay on Orca is fine by me. Thank you.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •