# BTT SFS v2.0 False trigger **URL:** \ **Category:** General Discussion\ **Created:** [April 24, 2024, 7:24am UTC](https://klipper.discourse.group/t/btt-sfs-v2-0-false-trigger/15995 "2024-04-24T07:24:26Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![PKav](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/pkav/32/4478_2.png) [@PKav](https://klipper.discourse.group/u/PKav)\ **Post date:** [April 24, 2024, 7:24am UTC](https://klipper.discourse.group/t/btt-sfs-v2-0-false-trigger/15995/1 "2024-04-24T07:24:26Z")
### Basic Information: Printer Model: Sapphire Plus with direct extruder mod MCU / Printerboard:MKS Eagle Host / SBC: OrangePi 3 LTS klippy.log [klippy.zip](https://klipper.discourse.group/uploads/short-url/melLju5ul9a3jQNWxfOnhb1sQJW.zip) (1.7 MB) ### Describe your issue: … I need help with debuuging BigTreeTech Smart Filament Sensor v2.0 The motion sensor (encoder) triggers falsely at random moments. The last trigger in attached klippy.log was false. I just manually extruded 10mm of fillament, hit Resume and print continued, so there was nothing wrong with extrusion. According to datasheet, this sensor ticks every 2.88mm of filament. I tried increacing detection\_length up to 20mm in printer.cfg, but false triggers still occur. As I understand, Klipper counts such sensor as triggered if feeder fed more than detection\_length while there was no signal changes from motion sensor. Is it correct? ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [June 23, 2024, 7:24am UTC](https://klipper.discourse.group/t/btt-sfs-v2-0-false-trigger/15995/2 "2024-06-23T07:24:59Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.