Problem when using motion filament runout sensor

[Horgul123]

The M600 support moves the filament sensor config into the M600 script.
When using a motion runout sensor (BIGTREETECH Smart Filament Sensor V2.0), which has a different config in the printer.cfg, installing the M600 support results in 2 runout sensor configs which prevents the printer to start (duplicate use of pin PC15).
When removing the config in the M600 scripts the repro for the helper script becomes dirty.

Is it really nessecary to move the filament sensor config away from the printer.cfg?

Config for the filament sensor:
[filament_motion_sensor filament_sensor] switch_pin: PC15 detection_length: 4.5 extruder: extruder pause_on_runout: true runout_gcode: M117 Filament encoder runout {% if printer.extruder.can_extrude|lower == 'true' %} G91 G0 E30 F600 G90 {% endif %} insert_gcode: M117 Filament encoder inserted

[Guilouz]

The script disable [filament_switch_sensor filament_sensor] config in printer.cfg when you install M600 support.

[Horgul123]

Maybe you should add a check if another filament senor is defined. At the moment installing the M600 script leads to an error with another sensor and it takes a little knowledge to identfiy and fix the cause. And if you alter the M600 scripts you get this error. (deleted the M600 meanwhile, at the beginning it told be, that the M600 script was changed.

[Guilouz]

On k1 max there is 2 filament sensor config and the second one not integere with the one in M600 config.

If you have modified files in helper script it’s normal you have a dirty repo.

[Horgul123]

The smart filament senor ist connected to PC15 instead of the original one. so as shown above in the config you need to address PC15. And in the M600 script there is the original sensor with PC15 configured. This leads to the problem.

Is there a chance to "clean" the repo (without M600 support, I removed this via your script)

[Guilouz]

Script is done for stock machine not modified one.
Sensor PIN is PC15 so it can’t be changed.

just use repair fonction on web interface.

[Horgul123]

I understand, that you can't change it. But maybe you could add a check or a warning.

Repair worked. Thanks.

[ViniSug]

@Horgul123
To resolve the error message of duplicated use os pins, just add PC15 on [duplicate_pin_override] section

[Horgul123]

thanks for the hint. will check this option

[ViniSug]

@Horgul123
I bought the same BTT SFS 2.0.
I know that K1 has 2 pins to connect the runout sensor: PA15 (on the motherboard) and PA10 (on the tool head)
Can you share how you connected the sensors? Did you connect both or just one?

[Horgul123]

I'm just using the motion sensor. Works pretty well :)

Just replaced the existing sensor

[FaintandFuzzies]

@Horgul123 What does your Klipper code look like? I keep getting an error: The value 'filament_sensor' is not valid for SENSOR. My code looks like this:

[filament_motion_sensor motion_sensor]
switch_pin: PC15
detection_length: 7
extruder: extruder
pause_on_runout: false
runout_gcode:
PAUSE # [pause/resume] is required for printer.cfg
M117 Filament Encoder Runout
insert_gcode:
M117 Filament Encoder Inserted

[filament_switch_sensor filament_sensor_2]
pause_on_runout: false
switch_pin: !nozzle_mcu:PA10

I chose to connect the SFS V2 motion sensor to the main board instead of the switch sensor since you can only choose 1 on the K1 (non-Max)

[Horgul123]

I removed the sensor in the meantime. Too many false errors

[CyberWop]

Hello, has anyone successfully managed to use the SFS2.0 with a K1MAX ? I have replaced just the original sensor (green to D, red and black, blue not used) not connected anything to motherboard or tool head. But I can't get it to work, I've tried every possible combination in printer.cfg: either I get an error message, or detects break when not supposed to. I've read of people successfully doing it on K1, but their config does not work on my K1max

[tpruvot]

Look like you need to use the blue wire... the SFSv2 has 2 switches (for 2 inputs), one for the runout, and one which make a tick each 3mm. Both inputs are pulled up on the BTT manta (gnd on signal so, but unsure if its the presence or the missing filament which send the signal)...

So ignore the green wire first, and when its ok you can try to find a free input pin to configure it... But you need the 3 other wires (5v gnd and switch ones)

[tpruvot]

so i finally opened my nozzle cover to double check the availables pins... there is indeed PA10 but also PA8 & PA9 made for a bltouch.. both on rear pcb but not used on the K1Max, the Lidar has its own board/wires & connector

but all these tiny connectors are not usual, need the right ones or to solder directly on the "backside" which is not accessible due to the double PCB system

[tpruvot]

#[filament_switch_sensor nozzle_filament_sensor]
#pause_on_runout: true
#switch_pin: !nozzle_mcu:PA10

[filament_switch_sensor SFSv2_runout]
pause_on_runout: false
switch_pin: ^nozzle_mcu:PA8
runout_gcode:
  M117 SFSv2 runout
  PAUSE
insert_gcode:
  M117 SFSv2 inserted

[filament_motion_sensor SFSv2_encoder]
switch_pin: ^nozzle_mcu:PA9
detection_length: 2.88
extruder: extruder
pause_on_runout: false
runout_gcode:
  M117 SFSv2 encoder runout
  PAUSE
insert_gcode:
  M117 SFSv2 encoder resume

to try.... if you find the 5 pins connector