Printer paused 10 minutes after start printing

What is the problem?

Since yesterday my printer change its state from "printing" to "pause" about 10-15 minutes after start the printjob. Using Octoprint and Klipper. Never had this problem before.

What did you already try to solve it?

Checked the logs for notices. Nothing helpful. Checked the cable connections. Changed the filament. Tried other (older) printjobs that worked fine before. Checked the gcodes. Checked the configurations. Restarted everything. Replugged any usb. Removed all api devices.

Have you tried running in safe mode?

I will try immediatly

Did running in safe mode solve the problem?

Testing...

Systeminfo Bundle

Octoprint

2024-02-04 13:30:02,950 - octoprint.util.comm - INFO - Starting job on behalf of user octoprint

2024-02-04 13:30:02,956 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"

2024-02-04 13:30:02,969 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: xyz.gcode, owner: octoprint, user: octoprint

2024-02-04 13:30:03,011 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0

2024-02-04 13:30:03,023 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"

2024-02-04 13:30:03,440 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from https://plugins.octoprint.org/plugins.json

2024-02-04 13:30:04,351 - octoprint.util.pip - INFO - Using "/home/octoprint/oprint/bin/python3 -m pip" as command to invoke pip

2024-02-04 13:30:04,357 - octoprint.util.pip - INFO - pip installs to /home/octoprint/oprint/lib/python3.7/site-packages (writable -> yes), --user flag needed -> no, virtual env -> yes

2024-02-04 13:30:04,358 - octoprint.util.pip - INFO - ==> pip ok -> yes

2024-02-04 13:30:04,826 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid

2024-02-04 13:30:05,022 - octoprint.plugins.softwareupdate - INFO - Saved version cache to disk

2024-02-04 13:30:10,906 - octoprint.server.heartbeat - INFO - Server heartbeat <3

2024-02-04 13:30:30,097 - octoprint.util.comm - INFO - Externally triggered heatup detected

2024-02-04 13:38:21,550 - octoprint.plugins.octopod - INFO - *** Printer paused for user ***

2024-02-04 13:38:22,411 - octoprint.util.comm - INFO - Printer signalled that it paused, switching state...

2024-02-04 13:38:22,412 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Pausing"

2024-02-04 13:38:22,432 - octoprint.printer.standard.job - INFO - Print job paused - origin: local, path:xyz.gcode, owner: octoprint, user: None

2024-02-04 13:38:22,837 - octoprint.util.comm - INFO - Changing monitoring state from "Pausing" to "Paused"

Klipper

[2024-02-04 13:29:58,416] INFO: Klipper state: Disconnect
Klipper state: Ready

[2024-02-04 13:32:35,404] INFO: probe at 17.000,0.000 is z=1.890000

[2024-02-04 13:32:38,211] INFO: probe at 17.000,0.000 is z=1.892500

[2024-02-04 13:32:41,017] INFO: probe at 17.000,0.000 is z=1.895000

... a lot of more probes ...

[2024-02-04 13:34:50,934] INFO: probe at 77.000,148.975 is z=1.820000

[2024-02-04 13:34:54,593] INFO: probe at 17.000,148.975 is z=1.870000

[2024-02-04 13:34:57,402] INFO: probe at 17.000,148.975 is z=1.870000

[2024-02-04 13:35:00,208] INFO: probe at 17.000,148.975 is z=1.870000

[2024-02-04 13:35:00,952] INFO: Mesh Bed Leveling Complete
Bed Mesh state has been saved to profile [default]
for the current session. The SAVE_CONFIG command will
update the printer config file and restart the printer.

[2024-02-04 13:38:22,833] INFO: action:paused

Additional information about your setup

OctoPrint version 1.9.3
OctoPi version 0.18.0 (just seen)
printer Ender 5 S1
firmware Klipper 0.12.0
browser Chrome
operating system Windows

From your Klipper logs, it seems that Klipper is deciding to pause the printer. OctoPrint's log says 'printer signalled it is paused'. The pause is coming from the printer, and OctoPrint looks to be handling it ok. There's no clues as to why Klipper thinks it's paused here.

1 Like

Do someone know a way to find out whats the problem?

If the issue is Klipper based, I recommend to consult the Klipper forum:

Solved!

Trouble with the filamentsensor.

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