sentinel filament sensor with voron 2.4 klipper

[Andy H]

does anyone have a config for klipper to setup this sensor?

I have tried using the below to no avail. Even tried using the pullup ^ and inverting the switch ! nothing works. Using an octopus pro board and wiring is all good.

[filament_motion_sensor filament_sensor]
detection_length: 10.00 ; This can be adjusted to your desired level of sensitivity. 10 is a recomended value to prevent flow dropoff false triggers.
extruder: extruder
switch_pin: PG15
pause_on_runout: True ; This can be set to false to debug false positives putting the sensor in "monitor mode". The printer will not pause but it will run the runout_gcode below.
event_delay: 3.0
pause_delay: 0.5
runout_gcode:
    M117 Runout Detected!

thanks

Andy

[Yves ME]

Hello,

is there any solution for using the sentinel under Klipper?

thanks

yves

[Alex LaVelle]

If it helps, I have the Orthus set up on Klipper on an Octopus EZ Max board, works perfectly. I’ll go grab my config when I get to the office. 

Regards,

Alex C. La Velle

--
You received this message because you are subscribed to the Google Groups "DYZE DESIGN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to support-dyze-de...@dyzedesign.com.
To view this discussion visit https://groups.google.com/a/dyzedesign.com/d/msgid/support-dyze-design/6ae3b0fe-1e28-4915-8537-6de51cb26837n%40dyzedesign.com.

[Technical Support]

@Yves

As said previously on this thread, the sentinel is not a filament motion sensor but only detects presence so for Klipper whereas the Orthus falls into the [filament_motion_sensor], the Sentinel would work under [filament_switch_sensor] instead.

I have not tested this yet but as it is a simple switch sensor and pretty straightforward this will probably work, you just need to know the code of the pin where you plugged the Sentinel signal wire on your own board:

(to customize for your own requirements)

[filament_switch_sensor sentinel]
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:
#   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:
#   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: Insert here the code of the pin where the Sentinel signal wire is plugged on your board 
#   The pin on which the switch is connected. This parameter must be
#   provided.

To view this discussion visit https://groups.google.com/a/dyzedesign.com/d/msgid/support-dyze-design/CAJo9-v8_pKKRmamDQQcoAGt9yv0%2BBtDZrO2%3DeuTAPHFBRJABWA%40mail.gmail.com.

--

Flo Support Team Tier 1 Customer Service
	1505 Saint-Thomas Suite 100 Lemoyne, Quebec, Canada, J4P 3S2
	dyzedesign.com