Print jobs paused mid-print even there was lots of filament remaining

General Discussion
1

Basic Information:

Printer Model: Prusa i3MK3S+
MCU / Printerboard: Einsy
Host / SBC: RPi 5
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:

The filament sensor was fine on my MK3S+. After switching to Klipper, I got several successful small prints (each about 30-45 minutes) but all of a sudden, most of the time the print jobs were paused in the middle of the print. Either the Console showed “Print already paused” or “Print already paused” and “Filament Runout Detected”.

As a test, without filament, I typed: query_filament_sensor on the Console and it returned “Error on ‘query_filament_sensor’ : missing SENSOR”. I then inserted a filament into the extruder. The Console returned 'Filament Load Detected". Then it automatically sucked in the filament and extruded it from the nozzle. When I tried to insert a filament, I could not so I suspected there was some filament inside the extruder. I pressed the “UNLOAD FILAMENT” button on the GUI and a filament of about 3-4 cm came out. Then, I re-inserted it into the extruder. This time, Console did not show 'Filament Load Detected". When I typed: query_filament_sensor while I could see the filament partly outside and partly inside the extruder, the Console gave me “Error on ‘query_filament_sensor’: missing SENSOR”.

It is suspected that it might be due to software/configuration issue. I installed Klipper using this method:

dz0ny/klipper-prusa-mk3s: Structured Klipper config for Prusa MK3s 3D printer

Enclosed is the log file. Could you please check if there is something wrong? Thank you.

klippy.log (2.0 MB)

2

You will need to prepend ^ as a pull-up before the pin, or better yet, choose one that has a hardware pull-up already.

1 Like
3

Thanks for your reply. Do you mean in klipper-prusa-mk3s/mk3s/einsy-rambo.cfg,
change the

switch_pin: !PK0

to

switch_pin: ^!PK0

like the following?

[filament_switch_sensor fsensor]
pause_on_runout: True
runout_gcode:
    M118 Filament Runout Detected
    M600
insert_gcode:
    M118 Filament Load Detected
    LOAD_FILAMENT
event_delay: 3.0
pause_delay: 0.01
switch_pin: ^!PK0

Why it is better to choose one that has a hardware pull-up already? Any good recommendation for the Prusa i3MK3S+?

4

Exactly, whereas I cannot comment on the negation !. This depends on your hardware.

A hardware pull-up is more stable than the pull-ups that can be activated in the MCU via ^. But the “soft pull-ups” usually work fine as well.

I’m not sure how your board exactly looks or what its schematic is. From a cursory look at the schematics of the original Einsy Rambo v1.1 board, there are no suitable pins left, as the board is quite Spartan.

1 Like
5

Thanks. First print was successful. I will keep an eye on it and report back if there is any problem.

How come the following command sometimes returned the status immediately but sometimes it took, say 7-10 seconds, to do that? At one point, I issued that query multiple times since the status was not shown. It was like Klipper thought about it for 7-10 seconds. Then, returned a bunch of status all at the same time.

QUERY_FILAMENT_SENSOR SENSOR=fsensor

6

It seems strange. In any case, it’s impossible to tell without a log. Whenever you make any changes and have questions about them, post a klippy.log file showing the issue.

2 Likes
7

Same log as the one I originally posted. Just changed that

switch_pin: ^!PK0

Do you think the Einsy Rambo board is a bit tardy for Klipper? Perhaps better to change to another board?

8

It’s hardly possible since your previous configuration rendered the filament sensor basically inoperative.

1 Like
9

Sorry. I just updated the log file.

10

New information always to a new post - and never to the first post.

1 Like
11

OK. I will keep that in mind. Thanks

12

@ Sineos I tried several print jobs the past two days and all completed without being paused in the middle of the jobs. Thank you.

1 Like
13

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