Klipper did not pause even the PAUSE command was issued

General Discussion
1

Basic Information:

Printer Model: Prusa i3MK3S+
MCU / Printerboard: Einsy
Host / SBC RPI
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Besides the Connection Timeout issue and MCU SHUTDOWN issue, I have a new problem:

I was able to go to Orca Slicer and manually added a PAUSE command to any specific layer. The printer moved the extruder to the right and paused at that layer. However, today I saw the extruder moved to the right but it quickly went back to continue the print without pausing. In one print, I had four PAUSE commands in the gcode but Klipper just did what I mentioned without pausing. What is wrong?

klippy_pause_notworking.zip (4.0 MB)

2

Hi @printeruser ,

Klipper already thinks it’s paused.

Print already paused

If you run a CLEAR_PAUSE, then PAUSE, does it pause as expected?

3

Why Klipper already thinks it’s paused but it didn’t? First time have this problem.

Do you want me to add CLEAR_PAUSE and then PAUSE in those layers I want to pause within Orca Slicer. Then try the print job again?

4

Your PAUSE macro both pauses and cancels pause

[gcode_macro PAUSE]
description = Pause the actual running print
rename_existing = PAUSE_BASE
gcode = 
	PAUSE_BASE
	_TOOLHEAD_PARK_PAUSE_CANCEL

You also have macros for PAUSE_NEXT_LAYER and PAUSE_AT_LAYER

5

I am a bit confused. It was working fine for the past few days. I did not change the macro. Why suddenly pause and cancel? In order to fix it, what shall I do? Just put a CLEAR_PAUSE before each PAUSE at specific layers of interest, type CLEAR_PAUSE at the Console before launching each print job or something else?

6

You should put a CLEAR_PAUSE command in your print start macro or slicer Start G-code.

7

Where in printer.cfg shall I put it? Just before # Heat bed for probing?

[gcode_macro START_PRINT]
gcode:
{% set BED_TEMP = params.BED_TEMP|default(60)|float %}
{% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(190)|float %}
# Heat bed for probing
M190 S{BED_TEMP}
# Use absolute coordinates
G90
# Home the printer
G28

# If you are using QGL:
#QUAD_GANTRY_LEVEL
#G28 Z

# If you are using Z-Tilt:
#Z_TILT_ADJUST

# To fix bed_mesh: min/max points too close together
#BED_MESH_CALIBRATE AREA_START={params.AREA_START|default("0,0")} AREA_END={params.AREA_END|default("10,10")}


# If you are generating a new bed mesh:
# Uncomment below if using traditional method
#BED_MESH_CALIBRATE
# if not using traditional method but adaptive method, use the below line
BED_MESH_CALIBRATE ADAPTIVE=1 ADAPTIVE_MARGIN=5
## NOTE:    The adaptive meshing feature requires exclude_object     ##
##      and may require 'Label Objects' to be enabled in the slicer  ##
##           To mesh without it just use BED_MESH_CALIBRATE          ##

# If you are loading an existing mesh:
#BED_MESH_PROFILE LOAD=default

# Move the nozzle near the bed
G1 Z5 F3000
# Set and wait for nozzle to reach printing temperature
M109 S{EXTRUDER_TEMP}
# Add code for Prime line if needed. Alternatively use KAMP which draw the purge line.
# Start printing!

Enable exclude_object for adaptive meshing

[exclude_object]
8

It doesn’t really matter. I would put it at the very start, but that’s just preference.

9

Thank you very much.

1 Like
10

Great! If my solution worked for you, please mark it as the solution so other people know this is solved.

1 Like
11

So far so good. Thank you.

1 Like