Auto-resume only on NOT FEEDING; purge check fails on pressure left after the purge
A CLOG DETECTED pause is usually a real blockage: on 2026-11-17 a nozzle blocked right after a swap, the purge check passed (a blocked nozzle also builds pressure) and the automatic resume only printed air until the next CLOG pause. CLOG messages are still cleared after a resume, so a leftover one cannot hide the next NOT FEEDING message. The purge check now also fails when bd_pressure's delta is still above pressure_max_delta (15) when the check stops: 16 good purges -3..+10, two long purges into the blocked nozzle +19/+21 (the short ones did not show it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
385adb5283
commit
2629e70fad
4 files changed
+27
-8
No files matched your search
@@ -16,7 +16,7 @@
|
||||
# (the lane AFC was loading when a tool change failed, otherwise the loaded
|
||||
# lane), and RESUME stops with an error when another lane (or none) is loaded.
|
||||
# RESUME LANE_CHECK=0 resumes anyway (e.g. after remapping with SET_MAP).
|
||||
# An AFC buffer fault pause ("AFC NOT FEEDING" / "CLOG DETECTED") during a
|
||||
# An AFC "NOT FEEDING" buffer fault pause (not "CLOG DETECTED") during a
|
||||
# print runs this RESUME by itself after a few seconds, within limits
|
||||
# (afc/auto_resume.cfg).
|
||||
# A failed bed check in PRINT_START (calibration/bed_scan_check.cfg) pauses with
|
||||
|
||||
Reference in new issue
Block a user