Resume macro doesn't heat up

General Discussion
1

Basic Information:

Printer Model:
MCU / Printerboard:
Host / SBC
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:

Hello i have a BTT Pad 7 and was wondering once my filament runs out and i insert more click resume on the screen it doesn’t heat up to the previous temp then resume. It will just try to resume and then cancels print because its not upto temp.

If i use my heat and resume print macro then i will set the temp in the macro then send the macro but it will turn off the heater and continue then when it gets too cold cancels iand says too cold. Some times if i set the temp to resume at in the macro but on the screen not through the web interface it will not do anything.

klippy.log (95.1 KB)

This has i believe the normal btt pad 7 screens resume button macro
mainsail.cfg (15.3 KB)

These are my macros that go into my macro list
FILAMENT_RUNOUT.cfg (909 Bytes)
RESUME.cfg (2.5 KB)
INSERT_FILAMENT.cfg (1.4 KB)
LOAD_FILAMENT.cfg (430 Bytes)
PAUSE.cfg (1015 Bytes)
UNLOAD_FILAMENT.cfg (443 Bytes)

2

Your current setup is configured this way.

try to remove “M104 S0” from runout_wait macro

3

The only reason I have it in there is because when it pauses I want to heater to cool down so if im not at the printer it doesn’t stay hot for possibly an hr or so.

4

Then you’re going to have to modify your RESUME macro to bring it back up to temp.

1 Like
5

The issue with runout_wait is following:
it will be started after 120 seconds.

Runout processing macros is a multistage process,
first FILAMENT_RUNOUT will be called which will call PAUSE
PAUSE script is responsible for pushing your current temperature to RESUME script
then FILAMENT_RUNOUT will order delayed execution of runout_wait and system will stop.

So it depends when you call RESUME
if you call RESUME sooner than 120s - runout_wait will be executed after RESUME - and as an result it will set your temperature to 0

1 Like
6

Most probably you can try to fix this issue by introducing following code in the beginning of RESUME gcode

UPDATE_DELAYED_GCODE ID=runout_wait DURATION=0

this should cancel execution of runout_wait if it was not launched yet.

But it’s very hard to understand what order of commands was executed in your case as your klippy.log doesn’t contain records about event, most probably you publish klippy.log file long after (few days) after you experienced this issue.
I would suggest to reproduce it and then upload latest klippy.log with records about event’s.

1 Like
7

Thank you. Tomorrow I will try putting the code you suggested first and see how that works and if it doesn’t do as I want it to, then I will reproduce the fault amd upload a new klippy.log

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.