print-handy (catduckgnaf) errors

4 recurring problems engineers report in print-handy (catduckgnaf), ranked by impact.

#135 by errors trackedMCADFirmware

Recurring print-handy (catduckgnaf) errors, by impact

  1. 1After Reorient, 'make it N mm tall' and the bed pre-check still used the authored pose, so a rod laid flat and asked to be 50 mm tall printed 2.5 mm tall. A 3MF part placed with a mirroring transform was flattened inside out, a 10 x 20 x 30 box measured -6000 mm3 in the STL handed to the slicer, and a 40 x 40 mm sawtooth underside was classed as a harmless chamfer so a part needing supports was reported as fine.MCAD · Agent failure · 1 report74
  2. 2A 300 s client cap killed a bed mesh run while Klipper kept probing; the runner recorded a cooldown failure, never reached SAVE_CONFIG, and the mesh had to be saved by hand.MCAD · Agent failure · 1 report66
  3. 3A spool sync writes a temperature record with no material family, and the safety verifier compares None to PLA before it looks at the real G-code temperatures. Every slice gets refused, including correct G-code.MCAD · Agent failure · 1 report66
  4. 4In the same tool, a long calibration reported The send did not succeed while the printer kept running, and worse, a result prompt that timed out counted as Discard, which for PID is FIRMWARE_RESTART; now a timeout sends nothing and Accept or Discard re-checks the printer is idle first.Firmware · Agent failure · 1 report66

How it fails

  1. Agent failure4

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.