My filament sensor randomly keeps triggering M600 macro, is there a way to ignore split-seconds triggers ? I asked it on klipper discord no one knew how to do that..
#Filament sensor randomly triggering , is there a way to ignore split-second sensor triggers?
wintry cypress
umbral pagoda
Not possible by default. The more important question is why your sensor does that
wintry cypress
honestly I dont know, checked the cables, it randomly triggers
sometimes it's okay for week
then poof, random filament change in the middle of the night
it doesn't move , it is in fixed position on frame
umbral pagoda
Is it a motion or a switch sensor?
wintry cypress
switch sensor
[filament_switch_sensor my_sensor]
pause_on_runout: True
When set to True, a PAUSE will execute immediately after a runout
is detected. Note that if pause_on_runout is False and the
runout_gcode is omitted then runout detection is disabled. Default
is True.
runout_gcode: M600 #calls a macro with the name M600 (so it can be called by slicers too)
A list of G-Code commands to execute after a filament runout is
detected. See docs/Command_Templates.md for G-Code format. If
pause_on_runout is set to True this G-Code will run after the
PAUSE is complete. The default is not to run any G-Code commands.
insert_gcode: M117 Filament inserted #just a throwaway GCode command to have something in this space. You can add your own.
A list of G-Code commands to execute after a filament insert is
detected. See docs/Command_Templates.md for G-Code format. The
default is not to run any G-Code commands, which disables insert
detection.
event_delay: 3.0
The minimum amount of time in seconds to delay between events.
Events triggered during this time period will be silently
ignored. The default is 3 seconds.
pause_delay: 0.5
The amount of time to delay, in seconds, between the pause command
dispatch and execution of the runout_gcode. It may be useful to
increase this delay if OctoPrint exhibits strange pause behavior.
Default is 0.5 seconds.
switch_pin:!P1.27