Research note: QIDI does not maintain a full numbered error code table for the Q2C the way Bambu Lab or Creality do for their machines. The official QIDI Wiki has exactly one documented fault code for the Q2 platform, QDE_002_001, covering a model cooling fan speed fault. Everything else the Q2C shows you, leveling failures, probe errors, filament and clog warnings, the Fluidd display glitch, the power loss recovery prompt, is communicated as plain text on the touchscreen or in the Klipper-based console rather than a numbered code. This guide covers what QIDI actually documents for the Q2 and Q2C shared platform (wiki.qidi3d.com/en/Q2), and says so plainly where the company has not published a specific code.
The Q2C is the base, non-AI-camera model in QIDI’s Q2 lineup. It shares the frame, the 370 C bimetal hotend, the CoreXY motion system, and the loadcell-based nozzle leveling sensor with the standard Q2, but it drops the actively heated chamber, the AI monitoring camera, and comes with the air filter and camera as optional add-ons rather than standard equipment. That matters here because a few of the fault conditions people ask about online (spaghetti detection pauses, AI-flagged defects) simply do not apply to a stock Q2C. Keep that in mind before you go hunting for a fix to a problem your printer cannot actually have.
How to read the message correctly
Before you search for anything, write down the exact text on the Q2C’s 4.3 inch touchscreen, not your paraphrase of it. “Leveling error” and “probe error” point to different root causes even though they sound similar, and QIDI’s wiki treats them as one combined troubleshooting path with two separate checks. If the message includes a code string like QDE_xxx_xxx, note the whole string exactly, dashes and all, since that is what QIDI’s own error code page and after-sales team will ask for. If you’re running the Q2C through Fluidd or Mainsail on its Klipper-based firmware, the console log usually gives you a more specific line than the touchscreen summary does, so check that too if the printer is networked.
Leveling and calibration messages
Leveling Error / Probe Error. This is the most common calibration complaint on the Q2 platform, and QIDI’s wiki (Leveling Error or Probe Error page) treats it as two separate mechanical checks rather than a software bug.
First, home the printer and watch the build plate rise. If it contacts the Z-axis fixtures on either side before reaching the top, the plate has drifted out of position. QIDI’s fix is mechanical: loosen the side panel, loosen the platform screws, nudge the plate slightly to the right so it clears the fixture, and retighten. This is a real alignment issue, not something auto leveling can compensate around.
Second, if the plate itself is severely tilted, the printer’s automatic leveling routine cannot fully correct for it and you need to run manual four-point platform calibration. The Q2C ships with built-in calibration models for this. If the plate is already reasonably flat, skip this step. Because the Q2C uses a loadcell sensor built into the hotend rather than a separate probe, most leveling failures trace back to plate position or tilt rather than a failing sensor, so check the mechanical side first.
First layer not sticking. Not strictly an error message, but it produces enough support requests that QIDI documents it alongside leveling issues. If you see gaps between first layer lines, the nozzle is too far from the plate and you need to reduce Z-offset in small 0.05 mm increments during the first layer, waiting about a second between taps to see the effect. If the plate is simply dirty, clean the PEI surface with isopropyl alcohol and avoid touching it with bare hands afterward. A thin layer of glue stick or a light hairspray coat can help on stubborn filaments, but persistent adhesion trouble after calibration and cleaning is a support ticket, not a settings tweak.
Fan and cooling messages
QDE_002_001, cooling fan speed error. This is the one formally coded fault QIDI publishes for the Q2 platform. The on-screen message reads roughly “fan speed 0 may be error” for the model cooling fan. It almost always means the model cooling fan is physically obstructed, and the usual culprit is the white hotend cable resting against the fan blades. Open the back of the print head, check whether the cable is touching or blocking the fan, gently reroute it clear of the blades, and restart. The Q2C’s part cooling, auxiliary cooling, and hot end fans are all 4-pin PWM units with RPM feedback, which is exactly why the firmware can detect a stalled or underspeed fan instead of just running it blind.
If a different fan throws a similar speed warning, the check is the same regardless of which fan it is: power off, inspect for dust buildup or a snagged cable, and clear the obstruction before assuming the fan itself has failed.
Filament and extrusion messages
The Q2C uses a hardened steel dual-gear extruder and a runout sensor mounted above the extruder. A filament runout message during a print is usually exactly what it says, an empty spool or a snapped filament path, and clearing it is a matter of reloading and resuming.
Clogs are more involved. QIDI’s clog guide splits into two cases. For a straightforward jam, remove the extruder, take off the front cover, and clear the blocked filament or debris before reassembling. If filament is stuck in the extruder gear itself rather than further down the path, you need to go further: remove the extruder, take off the runout sensor, pull the four housing screws, split the extruder open, and clean the gears directly. This is a fifteen minute job with a hex driver, not a full teardown, but it does mean removing the toolhead cover.
Tangle detection on the Q2C requires a QIDI Box attached. Without one, the stock printer relies on the runout sensor alone for feed problems.
Thermal and safety behavior
QIDI’s own spec sheet for the Q2C describes a smart PTC fuse paired with dual temperature sensors that monitor heating in real time and cut power immediately if they detect abnormal heat. This is a hardware safety cutoff rather than a recoverable “error message” you troubleshoot and clear. If your Q2C ever shuts power to a heater unexpectedly and shows a thermal fault on screen or in the Klipper console, do not just power cycle and reprint. Check that the hotend and bed thermistor connections are seated, that nothing is pinching the wiring near the toolhead, and if the fault repeats on a second attempt, stop and contact support rather than forcing more heat cycles through a heater that may be genuinely failing.
Interface and connectivity issues
If the Fluidd web interface loads blank or broken after a firmware update, QIDI’s wiki has a specific fix: SSH into the printer (default credentials are documented on their site, do not leave them at default if you expose the printer to your network), delete the existing fluidd folder, and replace it with a fresh copy of the interface files. If Fluidd still won’t load after that, the next step is deleting the moonraker-sql.db database file and restarting the printer. This is a known, if slightly technical, fix rather than a sign of hardware failure.
For general network trouble, the Q2C supports 2.4 GHz Wi-Fi, Ethernet, and offline USB printing, so if cloud or Wi-Fi connectivity drops, printing from a USB drive is the fallback while you sort out the network side.
Power loss recovery prompt
After an unexpected power cut, restarting the Q2C shows a recovery prompt rather than an error. Confirming it resumes the print from where it stopped, rehoming X and Y but not Z, since Z position is restored from memory to avoid crashing the nozzle into the model. The default recovery window is 72 hours, after which the printer will not offer to resume. This works better on PETG and TPU, which tolerate the pause well, than on PLA, which can detach from the plate as it cools, or ABS and PC, which are prone to warping from the temperature swing. A visible line at the recovery layer is normal and not a fault.
QIDI’s larger CoreXY machines run a different firmware track worth knowing about if you own more than one QIDI printer: the QIDI X-Max3 Error Message Index covers the X-series’ Klipper-based console messages, which look nothing like the Q2C’s mostly plain-text prompts and its one numbered QDE code.
When to stop and contact QIDI support
Mechanical fixes, cable rerouting, leveling recalibration, and clearing a clog are all reasonable owner-level tasks. Contact QIDI directly (Q2support@qidi3d.com or Q2support02@qidi3d.com) when a thermal safety cutoff repeats after you’ve checked the wiring, when a fan speed error persists after the cable is clearly clear of the blades, when the mainboard or toolhead adapter board itself seems to be the point of failure rather than a cable or fan, or when you’re looking at a specific QDE or QDC code that isn’t covered on the wiki’s published pages. QIDI’s after-sales team can also point you to the correct wiki page if a QDC notification includes a QR code you can’t scan or a code string that doesn’t match anything published yet, since QIDI is still actively expanding that documentation.