Orbiter 2.0 Filamentsensor config for Ratrig
As of now i currently have the attached file as config for my ratrig filament sensor it doest seem to work correctly loading and unloading are fine but when it comes to detect a filament outrun druing the print it doest stop the printer, to unload and ask for more. (Tested during the print , filament was cutted and the printer displayed "cannot unload filament now" or so)
I appreciate any help :)
6 Replies
ok solved this code works flawless instead of the old one
thanks to Helge Keck
Sorry for waking up an old post. I have it connected to an EBB36 (so different pins) but above setup causes my printer to unload and load multiple times. Any ideas why @Helge Keck
[filament_switch_sensor filament_sensor]
event_delay: 0.1
pause_on_runout: True
runout_gcode:
UNLOAD_FILAMENT
insert_gcode:
LOAD_FILAMENT
switch_pin: ^toolboard: PB3
[gcode_button sensor_button]
pin: ^!toolboard: PB4
press_gcode:
UNLOAD_FILAMENT
WAIT! I think I have it!!! Removed exclamation mark at
[gcode_button sensor_button]
pin: ^!toolboard: PB4
Now filament unload does no longer cause multiple unloads... Test tomorrow how printing goes (I am trying to move away from the very difficult OrbitorSensor.cfg )
Not sure if now the toolhead is also parked if it senses a runout.
@Helge Keck Might I ask for some assistance on above? I have an issue with my printer that is throws an error when I resume the print after runout and inserting new filament. So when I put in new filament, it passes the filmant into the extruder and hot end, then purges a bit and then halts. I press resume and then it briefly moves a bit and halts, stating:
10:11 FIRMWARE_RESTART
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
10:11 MCU 'mcu' shutdown: Rescheduled timer in the past
This generally occurs when the micro-controller has been
requested to step at a rate higher than it is capable of
obtaining.
Once the underlying issue is corrected, use the
"FIRMWARE_RESTART" command to reset the firmware, reload the
config, and restart the host software.
Printer is shutdown
10:11 Klipper state: Shutdown
10:11 Filament loaded!
10:10 Filament unloaded! Please inspect the tip of the filament before reloading.
Also, prior to that, When the sensor detects no filament, it parks, retracts the last stump as far a the extruder will go. If I then pull out the last stump of filament, it immediately starts the "Filament_load" sequence,... not sure if this has anything to do with above,...
im not at my desk atm
please ope a new thread and share your configs as well
ping me in the evening again please
Hi, I have the EBB42 1.2version which uses the same pins PB3 and PB4 but can I ask why you need the ^ pull up? The original OrbiterSensor.cfg used ! to reverse to direction???. I had the same issue with multiple unloads plus when restarting the firmware it would immediately heat the extruder and attempt an unload.
you need it to avoid false alerts
Hi, and thats why you need the ^? So my config should be: switch_pin: ^toolboard: PB3 & pin: ^toolboard: PB4