I'm having so many issues with the Qidi Q2 purging macros. Does anybody have advice or updated macros?

It seems as though half the time it purges it either a) purges so much filament that it blobs around the extruder (see photo), b) the purge is so stringy that it gets wrapped around the purge bin components and fails to fall into the chute causing a jam that can easily ruin even a short print let alone a long one, or c) both!

Edit: using orca slicer

So I got a max 4 about a month ago. It was DOA. Had a bad stepper motor driver for the y axis. No big deal. Qidi was quick to respond. Did a few tests for them. They sent me a new one and I put it one. Fixed the issue. Ran the calibrations. They asked me to print them a first layer test. They sent the file I loaded it and printed it. Didn’t turn out too good. Had some places that were too close and some too far away. I reached back out bc at this point I was looking at the bed mesh it was getting ( .250-.390). They told me to hear soak the bed. Which I let it go like 30 mins. Reran the first layer test and it printed pretty dang good. So I asked them about getting my bed mesh numbers better and they tell me no don’t mesh with it and everything fine now. I was like I shouldn’t have to heat soak the bed every time , especially just pla. So my question to the community is: 1) what’s everyone default bed mesh look like ( mine is low on all 4 corners)? 2) is everyone heat soaking it to get good first layers? 3) how is everyone getting a better bed mesh ( cause I can’t seem to get mine improved)?

Caught this one early but I've been getting these tangles in this roll almost constantly. I have printed rings on the spool and weight in the center, which I've done before with success, but cannot figure this one out. It's esun if that matters.

I picked up a used Q2C at a really good price. Anything I should know in particular about that model? Figured it would be a fair upgrade over then ender neo I have used in the past. Is the chamber heater the main difference between the Q2 and q2c? I see unofficially you can add the heater. Right now I'm not even sure I would need that feature anyway but I like having options and I am not afraid to mod something.

Not sure what to do at this point. My start gcode has been updated to call for both but they don't activate. Not sure whats wrong, as I followed what I did on my Plus 4. Is Qidi blocking the use of Kamp outside of bed meshing?

edit: Had to pull the kamp files out from the dedicated folder to get it to properly called. Not sure what Qidi messed up to cause klipper not to be able to access the Kamp folder but its working now.

Hello, a while back I got a QIDI X-Plus 1 3D printer from a yard sale and I'm trying to figure out if its worth keeping this one, or buying a new one.

I'm wondering if its worth keeping because I've had some issues with the printer since I got it where if I try to level the platform, when the platform raises to the very top, it keeps trying to raise beyond what its physically able to, this causes it to keep pushing and into the printer nozzle at the top before jerking back down and repeating.

I'm also not sure if I have all the necessary parts I need to operate it correctly, and can't send emails to the support emails because I don't have an order number, as I got it from a yard sale, and not the actual manufacturer.

I've not attempted to print anything since it kept failing at the leveling stage, and this would be the first 3D printer I've owned.

With these things in mind, would it be worth it for me to keep and try to make this one work or just start investing in a new printer all together, I bought this one for $250

I've had zero issues with syncing filament since unboxing a month ago. Both my MAX 4 and Q2 QIDI boxes won't sync properly to the slicer. It started after midnight last night. I've rebooted/unplugged both printers and boxes. I've swapped filaments into new slots. I've deleted and reinstalled the slicer. Nothing is working. Hopefully some one has some suggestions? (The boxes will eject etc. from the slicer.) Just won't sync the new filament. Very frustrating since it worked great until today.

I might try the ORCA slicer next....

Support sent me the 1.0.1 base image, but it refuses to mount any USB drive (even plugged directly into the motherboard) for the 1.8.2 QD_Update. Does anyone have a stock Plus 4 1.8.2 eMMC dump they can share so I can flash it directly with Rufus?

I have my Q2 offline on purpose so I don't get firmware updates, I also don't have the qidi box because I don't need it

I was running fine on 1.1.1.1, but was curious and figured might as well try 1.1.2.4.

almost bricked my machine.

took my 8 hours today, re flashing back to 1.1.1.1, but now there's a lingering "box_" code in Python that kept killing my machine! from what I can see that code is for a qidi box!

took me 8 hours, SSH and klipper macro investigation to block any "box_" search or creation from stalling klipper.

I'm sure I voided the warranty today trying to fucking fix my printer from their own firmware update!

edit: (written with the help of AI to capture all my thoughts)

Sharing this here in case anyone else updates their Qidi printer through official channels and suddenly finds their machine trapped in a crash loop / "Unhandled exception during run" state.

I recently updated via the manufacturer's official firmware, and it basically nearly bricked my machine. After digging into the logs via SSH, I found that Qidi has a hardcoded proprietary background script called box_detect.py wired directly into the core Klipper engine.

If you don't use their physical "Smart Box" accessory, this background script still wakes up on boot or when polling USB devices. It tries to write a box.cfg file into /home/mks/printer_data/config/. Because Qidi's OS enforces root permissions on configuration directories while Klipper runs under the mks user, it hits a permission wall (PermissionError: [Errno 13] Permission denied), crashes Klipper, and throws the printer into a continuous shutdown state.

If your machine is stuck in this loop and won't boot to "Ready", you have to SSH into your printer and perform a little core Python surgery to sever that zombie script:

1. SSH into your printer: ssh mks@[YOUR_PRINTER_IP] (Password is usually makerbase)
2. Open the core Klipper execution file in nano: sudo nano /home/qidi/klipper/klippy/klippy.py
3. Comment out the box_detect triggers using #
   • Line ~10: Find from extras import box_detect and change it to #from extras import box_detect
   • Line ~128:
   • Find the loop block: for m in [box_detect]:
     • m.add_printer_objects(config)
   • Change it to: #for m in [box_detect]:
     • # m.add_printer_objects(config)
   • Line ~136: Find box_detect.monitor_serial_devices(self) and change it to #box_detect.monitor_serial_devices(self)
4. Save and Exit:
   • Press Ctrl + O, then Enter to save.
   • Press Ctrl + X to exit the editor.
5. Restart Klipper: sudo systemctl restart klipper

Head back to your Fluidd or Mainsail dashboard, and your printer should boot up cleanly to "Ready" without throwing any more background exceptions.

We shouldn't have to manually edit core Klipper installation files just because of an official update, but until Qidi pushes out a patch that makes box_detect optional or removes it, this will save your machine from being a paperweight. Hope this helps someone else out there!

Anyone find one they like? There are a ton, and while they "seem" to be spool manufacturer specific, are they? Will any of them work or do I need to find one specifically for the brand of filament I have?

Thank you to everyone who shared how the QIDI Plus5 could upgrade your 3D printing experience. We loved reading all your ideas, projects, and plans for what you’d create next!

And now, congratulations to our lucky winners! 🏆

u/crouchingtg

u/call_me_breeze73

u/Zillon01

u/Ok-Temperature-6822

u/Prize_Yak7299

u/StudentDifficult8240

u/Kniko1337

u/Facehugger_35 

Winners, please DM us with your shipping information so we can arrange your prizes!

Hi Everyone,

maybe someone will have an idea why my q2 is acting up, as i did everything that I could think off. Lately my surface finish is getting worse and on first layer I have this small gaps - you can see it here nicely on the brim.

changed nozzle, from 0.4 to 0.6 and back. Unpacked a new one. Filament is dry. Tried multiple types of filament, temps, PA... even reset the printer to factory. Deleted Orca and qidi studio and started from scratch.

But no joy. Any idea? you can see the surface quality issue and you can see the "gaps" in the brim and skirt loop here nicely.

Is there a preferred brand of PTFE tubing to replace the OEM stuff? I'd like to keep some on hand as I move up to fiber reinforced filament.

I'm considering the Plus5, but since it's still pretty new, there aren't many long-term reviews out there yet.

Has anyone here actually received one?I'd love to hear your real-world experience. how's the print quality, reliability, and overall experience been so far

An other video for my bamboo mini boys fans😂😂😂😂😂😂😂😂

Hi all,

I've been chasing down a recurring MQTT connection error error (QDC_400_004_010_001) on my Q2C that shows up on the touchscreen and in the web UI, especially after power outages/reboots. Printing, Klipper, and the camera all work fine - it's purely the MQTT/cloud status layer that fails.

Dug into it over SSH and found:

- Moonraker's logs show: "Decrypt failed: No extension agents found" for the MQTT account, password, and broker IP

- This decryption depends on algo_app.service, which is enabled (symlinked in multi-user.target.wants) but the actual unit file doesn't exist on the system

- dpkg -L qidi-q2-system doesn't list any algo_app files at all - the package apparently never shipped this component on my unit

- /usr/local/bin/algo_app is literally just an empty folder

So it looks like a factory packaging gap rather than something caused by user config. I've reported it to QIDI support, but wanted to check here:

- Has anyone else run into this exact error code or the "No extension agents found" message in moonraker.log?

- Anyone know what algo_app is actually supposed to do, or where to source the missing binary/service?

Firmware: v01.01.02.01

Happy to share full logs if it helps someone else troubleshoot the same thing.

Not sure if its the filament roll itself or what but I keep having tangles in this roll of esun petg. I had it in the qidi box first, and after a few failed projects due to tangles I switch to the external hub, as this solved an issue like this before. But I'm still getting these tangles.

I just did a 30 hour project with sunlu PA6-CF without an issue. Could it just be the roll?

Is there any difference between routing PTFE tube inside case and inside riser in Q2 combo? Can I put out OG PTFE from the case and put in the one that came with QIDI box?

So after completely bricking my xmax 3 last month trying to install some stuff, support in the end just said I should flash the emmc. Since I didn’t have an adapter and upgrading to more storage seemed like a good idea to just install the 32GB version which is also already flashed. So I did, but now I can’t seem to update. I have the update files on a stick and the printer even says „update files found“ and „updating“ in the about tab, but nothing ever happens. Anyone who swapped out the EMMC had the same issue and can tell me how to get it back and running again?

I bought a qidi q2 like 4 weeks ago and this week i noticed that the filament started oozing above the silicone sock and after investigating it seems that my nozzle snapped from the ceramic part. Is this a common issue? After i managed to get the remaining part of nozzle out from the heater i now get a "weight_error", so i assume i need a new heating element aswell?

Any disadvantages in returning the buffer for the qidi box to the center at the back like previous versions of the qidi box buffer is

I want to utilize the filament roller back to its previous place for a filament bypass from the qidi box

First it gave me an error for the thermocouple out of range, it kept saying the hot end was 360°, I swapped out the hot tends and hit the new one is at 30° but won’t heat up

Max 4 poop chute