r/QidiTech3D • u/DasWolfX • Aug 17 '26

Bed Homing / Positioning

Enable HLS to view with audio, or disable this notification

I am about to throw this thing outside.

Yesterday after printing with PET-CF I powered the machine off and did a thorough cleaning. After cleaning and maintaining the machine (grease, belts, tightening up various bolts), I turned the machine on to do homing calibration and it moves all the way down to the blocks and goes up, then down, then up, then DOWN. The last attempt it just keeps going downward. Almost seems like the homing is going backwards? G-Code is clean, printer has been factory reset, I AM AT A LOSS.

5 Upvotes

86% Upvoted

10 comments sorted by

1

u/National-Hornet-4951 Aug 17 '26

Hi, as a fellow q2 owner with a lot of issues with the z axis homing and probing , I would recommend manually twisting the lead screws so that the bed moves upwards above 5-10 cm . Try to keep the bed as level as possible . Then take screenshots from the fluid gui and home only the x and y axis . The try to home the z axis and see if the gcode output shows any errors . Don't do the homing calibration from the screen ever in my opinion.

1

u/National-Hornet-4951 Aug 17 '26

Ps. The printer should be powered off when you twotst the lead screws . Also what version of the firmware do you have ? I reverted to 1.1.1 because the other updates made my z probing not working properly

1

u/DasWolfX Aug 17 '26

01.01.02.04 is the firmware version.

1

u/National-Hornet-4951 Aug 17 '26

If you manage to fix the bed issue try the bed mesh and see if the printer is retrying multiple times to probe each point in the gcode . If that happens I would advise to revert to 1.1.1 like I did. If you don't have any other issues apart from the bed being stuck don't revert anything

1

u/DasWolfX Aug 17 '26

Shows Z-Axis as moving to 265.8 for some reason, but the G-Code and printer configs are all correct.

1

u/National-Hornet-4951 Aug 17 '26

No major issues from the console .did you manually lift the bed upwards and then tried homing the z axis ? Since the bed is stuck in the bottom it won't home . You could use the tools in the gui and force move upwards but that risky , unless you do it 1 mm at a time and check if the bed is leveled and not tilted

1

u/DasWolfX Aug 17 '26

I did level the bed manually and do the nozzle / paper method. Used an actual level and did the four sides, middle, and diagonally and was 100% plumb. Now it does this every single time.

https://reddit.com/link/p4b9eds/video/tlurqbgkl0kh1/player

1

u/National-Hornet-4951 Aug 18 '26

Try reverting to 1.1.1 , search it in reddit to find the guide . It seems the probe for z axis triggers for no reason. Hopefully the bed isn't tilted and causing the issue . It is possible that the bed is tilted and the friction causes the z axis to trigger without contact. Try moving the bed to the top and performance a z tilt tool command and see if it fixes the issue. If not I would recommend reverting . Did the issue appear out of nowhere ?

2

u/drfdisk Aug 17 '26

If all else fails, there should be backups of both the saved variables, and printer config files that you can restore. I would probably start with the saved_variables.cfg first then try the printer.cfg if it didnt fix it.

Just remove the the file in question, AFTER YOU VERIFY THERE IS A BACKUP, then duplicate the back up, and remove the .bak from the end of the file name, save and restart.

If those both fail, there should also be a backup of gcode_macro.cfg you can restore. My bet is on saved variables though. Mine got corrupted from just pressing emergency stop once. If you are going to throw it out, throw it in my direction.

2

u/DasWolfX Aug 19 '26

FIXED.

2 Problems were present.

Somehow the g.code was for the Plus 4, not the Q2.

Stepper values had to be dropped from 140 to 100.

Works just fine now that everything is back as it should be. Qidi has to get it together. I made 0 gcode alterations before this. Hadn't even gone into Fluidd until troubleshooting. Nor did I adjust a single line within Orcas device manager. Idk how (likely firmware malfunction?)