BTT smart sensor pausing after prime blob, doesn't detect runout after.
Apologies for a repeat a week later, realized this may be more of a ratOS/klipper config issue than printer hardware.
I installed a BTT smart filament sensor V1 and when I start a print during the prime blob it goes from "active" to "empty" in mainsail and pauses the print immediately.
Then to be sure, I snipped the filament before it went in and it didn't detect the runout.
I put the macro in the user overrides config but I might have missed something somewhere. Appreciate any help, I'm dim when it comes to programming and always fear futzing with it cuz I worry it'll damage something. Config included.
14 Replies
Well your detection length is way off, so naturally it doesn't work very well 🙂
Also you're calling FILAMENT_RUNOUT which doesn't exist
Detection length should be 7 for the BTT smart sensor v1, see: https://discord.com/channels/582187371529764864/949807768972460042/949809929206759484
I extended it, but thank you.
What do you mean you "extended it"?
Was told on another forum changing the detection length to be a little longer can help prevent false positives on the startup. That was after I'd left the defaults and it still did the same thing
Ah, this is true, but 15 is over twice the amount which will cause other issues, you can try 8 or 9. The detection length is the length of filament it takes to turn the encoder enough to emit a pulse on the signal pin.
Does it? I saw some people say they were using 20 without issue.
Either way I'm pretty sure I had it initially the same as the linked macro but I'll try again with it.
I can't rule out that it works for some, i can't guarantee it would cause issues either. All i can advise is to stick to the klipper docs and specify the actual value +/- flow compensation/error and what have we.
OK. Also was told there are slicer overrides to add to the, start gcode?
The RR profiles in SS and PS disable/enable "my_filament_sensor", yes. Make sure to check your slicers custom gcode.
I believe they're commented out by default, but i honestly don't remember
Oh and btw, the sensor pin shouldn't be inverted (that will cause "detected" to be "empty" and "empty" to be "detected").
When you restart klipper it takes
detection_length amount of extrusion before the sensor will report detected. This might be the cause of the confusion 🙂Really? Huh. Every other thing I found said otherwise. I'll keep in mind.
Well that's how mine act at least 😄
Octopus 1.1?
Doesn't matter. Whether it's high or low when activated is a property of the sensor circuitry.
Even the official BTT docs say it's high when present and low when not detected:
