Help with runout macro

General Discussion
1

Basic Information:

Printer Model: Two Trees SP5
MCU / Printerboard: Robin Nano V3
Host / SBC BTT Pad 7
klippy.log NA

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:

I have a BTT filament runout sensor with a switch that is way too sensitive. Even the slightest wobble in the filament triggers it. I looked for a macro with a sort of debounce function but didn’t find any. For the heck of it I asked ChatGPT to write one. It looks impressive but will it work? I was wondering if I could get some of the natural intelligence here to look it over and tell me.
Thanks!
[filament_switch_sensor switch_sens.txt (3.5 KB)

…

2

Rather than complicating the setup with lengthy macros, perhaps tuning the config will solve it instead.

I also have a BTT filament sensor (v2 I think, the bulky one) and not had any issues with sensitivity. Are you using the motion sensor in Klipper? That alone should resolve the sensitivity as it’s required to indicate no filament for a length of extrusion before Klipper accepts it as out of filament or jammed.

Here’s my config:

[filament_motion_sensor filament_sensor]
extruder: extruder
detection_length: 14
pause_on_runout: True
runout_gcode:
    M117 Filament Runout Detected
switch_pin: ^PG11

[delayed_gcode DISABLEFILAMENTSENSOR]
initial_duration: 1
gcode:
    SET_FILAMENT_SENSOR SENSOR=filament_sensor ENABLE=0

(The PRINT_START and PRINT_END macros enable and disable the sensor so it doesn’t trigger when not actively printing.)

I see you left off the klippy.log but it’s still relevant (it would clear up my questions about the config).

Hope that helps!

1 Like
3

@stolowma
Sidenote:

When you open a new topic, please start the text at 1, not at 2, else all is written in bold letters.

grafik
grafik643×346 16.4 KB

4

Sorry, I didn’t realize that.

1 Like
5

The problem is in the runout switch, it triggeres a shut down as soon as it is opened. Even a light touch on the filament near the input triggers it. It doesn’t wait to see if filament is moving or not. I had to remove the sensor because I needed the printer so that’s why no klippy file. I’ll see if I can get it hooked up tonight, compare with your config and get you further info.

1 Like
6

@cloakedcode I haven’t tried out your config yet but I had thought about going your route and not using the “runout” switch and just relying on the motion switch. When I think about it why do you need both? I’ll try to give this a shot later today and let you know. Many thanks.

7

@cloakedcode I’ve finally got a chance to try a print with your config. It starts the print but very soon goes into filament runout. I notice uses switch_pin, should that be something else like encoder_pin to keep it from triggering when the encoder changes state? I’ve included the
klippy.log (1.9 MB)
kllippy.log as you requested.

8

It has to be “switch_pin”, that’s the only config option. There’s a “filament_switch_sensor” but it also uses “switch_pin”. But here’s the BTT sample config, pick whichever matches your device:

On top of that, here are some further troubleshooting steps. In particular, double check that the filament after the sensor is entirely constrained or you’ll get false alarms.

Try those things ^ and lemme know how it goes. I think I also went the lube/shim route to make things extra smooth (it’s been installed for years, hard to remember exactly what I did initially).

9

Thanks for the info. The mods listed don’t apply because this is their latest new and improved(?) model. It has a completely different mechanism. I’ll start looking at that config and see if I can find what I’m doing wrong.