Timelaps causing issues with PAUSE

Frontends
1

Dear all,

this is my first post in this forum. I have got my Ender-3 V3 se about a month now. After a single print, I changed it to run Klipper using a Raspberry 4 that I assembled into the printer stand. This way its quite handy to use the printer’s power supply to also supply the raspberry.
I also added a camera and a LED strip to the printer, both connected to the Raspberry. Additionally, I put a 7 inch touch screen with Klipperscreen to it and printed a nice housing for it. I am quite happy with my setup.

However, after my successful implementation of the M600 command to exchange filament during printing, I found out, that the timelaps addon influences the PAUSE function. Everytime when timelaps is activated and a PAUSE command is send, the printer moves to the parking postition, stops some seconds before a message pops up in the console saying // Print already paused and the printer starts printing again. It doesn’t matter how the PAUSE command is send - via Macro or manual. As soon as I deactivate timelaps, this behaviour disappears and I can PAUSE the printer as it is intended.

That means, with timelapse activated I am not able to exchance filament using the M600 code because it uses the PAUSE command to park the print head to wait for the exchange.

Is there anybody who may know this issue or has an idea how to fix this?

Cheers and thanks in advance.
Michael

IMG_20250428_134308
IMG_20250428_1343081920×2560 395 KB

2

Hi @mofman84 ,

Please do not delete the template. We need to know all the information there, especially your klippy.log to help you.

3

Also it’s - for timelapse is frontend stuff - the sub-fotum Frontends

1 Like
4

ok, thanks for mentioning. May the Admin be able to move it to the correct sub-forum?

1 Like
5

Already happend

6

Hi, please find my klippy.log file attached from today.
I started with an empty log file and started a small test print. Timelapse was activated.
In line 3653 and 3798 you can find the // Print already paused message. Unfortunately my PAUSE command was not logged in that file, but I’ve done this by sending a PAUSE command via the console. For the latter one, I made a CLEAR_PAUSE command immediately before the PAUSE command, but without any improvement.

klippy (1).log (734.2 KB)