The Q1 Pro is a Klipper-based QIDI machine, and like the rest of QIDI’s current lineup it reports faults as plain text strings pulled from the Klipper/Moonraker stack rather than as a fixed numbered list. QIDI has been rolling out a structured framework called QDC (QIDI Diagnostic Center) across its newer printers, where each fault gets a segmented code such as QDC_200_001_005_001 and a dedicated wiki page reachable by scanning a QR code on the touchscreen. Checking the live QDC index at wiki.qidi3d.com/en/QDC shows every single entry, across the Printer, Toolhead, QIDI BOX, AP, and AI categories, tagged only for the X-Max4. There is no Q1 Pro tag anywhere on that page. So while QDC exists as a company-wide initiative, it has not been extended to the Q1 Pro yet, at least not in the public wiki as it stands today. There’s also an older QDE numbered format tied to the QIDI BOX hub, but the direct wiki URL for that framework (wiki.qidi3d.com/en/QDE) returns a 404, so it isn’t something that can be verified as covering the Q1 Pro either.
What QIDI does provide for the Q1 Pro is a short “Error Message” page under the printer’s own wiki section, plus a couple of extra fault strings tucked into the clog-troubleshooting article. Between those two pages, five distinct error messages are documented with any kind of explanation or fix. That’s a small list next to the dozens of coded entries QIDI has built out for the X-Max4, and it means this index is necessarily shorter than what a full QDC writeup would look like. It’s worth naming that gap up front instead of padding the list with guesses.
One more thing worth flagging before getting into the messages themselves: QIDI’s own documentation is inconsistent about what to call this printer. The wiki’s landing page is titled “Q1 Pro” and lives at the URL /Q1-Pro, but several sub-pages, tags, and downloads under that same section just say “Q1” with no “Pro” attached, including the firmware reflashing page, which lists a download called “QIDI Q1 Image for eMMC” alongside images for the Plus 4, Max 3, and Q2. There’s no indication QIDI sells a separate non-Pro “Q1” model. This reads as inconsistent internal labeling on QIDI’s part rather than two different products, but anyone searching the wiki should know that “Q1” and “Q1 Pro” point to the same machine in these docs.
Thermal and hot end faults
The clearest of the documented messages is the thermocouple fault, which QIDI’s wiki lists as [Mcu mcu shutdown: Thermocouple ADC out of range.]. This shows up on both the main Q1 Pro error message page and the clog-troubleshooting page, worded identically in each place. QIDI’s fix is short: replace the thermocouple, or replace the entire hot end if swapping just the thermocouple doesn’t resolve it. This is a standard Klipper MCU shutdown message, meaning the analog-to-digital reading from the temperature sensor has gone outside the range the firmware considers valid, which usually points to a damaged or disconnected thermocouple wire rather than a software problem.
The second thermal-adjacent message is [Heater extruder not heating at expected rate], documented on the clog-troubleshooting page. QIDI frames this as a hot end problem and recommends testing with a different hot end to isolate the cause. If the replacement hot end has the same issue, the wiki says to contact after-sales for a new hot end. If the error persists across two different hot ends, QIDI’s guidance shifts to the adapter board, meaning it may need replacement instead. There’s no further detail on what internally triggers this message (whether it’s a timeout on temperature ramp rate or a heater power check), so treat the two-step swap test as the extent of QIDI’s own troubleshooting path here.
Bed leveling and probe faults
The Q1 Pro’s error message page also lists !!Probe samples exceed samples_tolerance, probe failed, but without any accompanying explanation or fix. This is the raw text of a Klipper probe error, thrown when repeated probe samples during bed mesh or Z-tilt calibration disagree by more than the tolerance the firmware allows. In general Klipper terms this points to a probe giving inconsistent readings, often from a dirty nozzle, a loose probe mount, vibration during probing, or debris on the bed, but QIDI’s own Q1 Pro page doesn’t spell out any of that. The wiki does have a separate Platform Calibration Guide for the Q1 Pro that walks through the manual bed leveling procedure using the three adjustment nuts, and a general adhesion troubleshooting page that covers Z-offset adjustment and bed cleaning, but neither of those pages ties back to the probe-tolerance message specifically. If your Q1 Pro throws this error, QIDI’s guidance amounts to running platform calibration and contacting after-sales if the problem doesn’t go away, not a cause-and-fix pairing tied to the message itself.
Mainboard and communication faults
[Lost communication with MCU MKS_THR] is the one mainboard-level fault QIDI documents for the Q1 Pro. According to the clog-troubleshooting page, most cases trace back to either the print head cable or the adapter board, and the fix is to replace the type-C cable running to the toolhead or swap the adapter board if a new cable doesn’t fix it. MKS_THR appears to be the internal name QIDI’s firmware uses for the toolhead MCU, so this message is specifically about the print head losing its connection to the mainboard rather than a general USB or network dropout. There’s no mention on the Q1 Pro pages of separate communication faults for Wi-Fi, MQTT, or the touchscreen itself, the kind of thing that does show up in the X-Max4’s QDC “AP” category, so it isn’t clear whether the Q1 Pro simply doesn’t produce those faults or whether QIDI hasn’t documented them yet.
Other reported messages
The last item on the Q1 Pro error message page is Error taking timelapse frame, listed with no explanation of what causes it or how to resolve it. Given the wording, it’s presumably tied to the camera or timelapse function failing to capture a frame during a print, but since QIDI hasn’t published any cause or fix for it, nothing more specific can be said without guessing. If you hit this message, it’s worth checking that the camera is connected and the SD card or storage target has free space, but that’s a general suggestion, not something confirmed by QIDI’s documentation.
QIDI’s QDC diagnostic framework currently only covers the X-Max4; see the QIDI MAX4 Error Code Index for how that fuller, coded system works on the printer where QIDI has actually rolled it out.