Please Help with Repetier Server - Klipper - Filament Runout Sensor
Hi,
I'm running a Artillery Sidewinder X1 with Klipper on my Repetier Server. Printings goes very well. But I have problems to setup the Filament Runout Sensor correct.
The probleme is:
If the Sensor is triggert, the printer stops and the nozzle goes to X300 Y300 and instantly goes back to the old position and continues printing.
I have no idea why. And I'm also not sure if its a problem with the RS or Klipper or my Gcode.
Maybe some can help please.
Thats my actual Klipper config. (I tried many versions)
I'm running a Artillery Sidewinder X1 with Klipper on my Repetier Server. Printings goes very well. But I have problems to setup the Filament Runout Sensor correct.
The probleme is:
If the Sensor is triggert, the printer stops and the nozzle goes to X300 Y300 and instantly goes back to the old position and continues printing.
I have no idea why. And I'm also not sure if its a problem with the RS or Klipper or my Gcode.
Maybe some can help please.
Thats my actual Klipper config. (I tried many versions)
[filament_switch_sensor my_sensor]
pause_on_runout: true
#insert_gcode: RESUME
pause_delay: 1
switch_pin: ar2
runout_gcode:
PAUSE
M83 ; relative extrusion mode
G1 E-3 F600 ; Retract a bit
G1 X300 Y300 F9000
M82 ; absolut extrusion mode
Comments
I'm also not sure why I added PAUSE to gcode. I found this in any example. Its M76 to pause a print.
I tried this to. But the printer goes instantly back and continues printing...
Its strange, because in 1 of 4 "sensor triggers" it works correct. But most of the time its faulty....
I tried this config to. But same behavior.
I think I have to ask in a klipper forum, too.
M76
And just this.
runout_gcode:
https://reprap.org/wiki/G-code#M118:_Echo_message_on_host
You can add in server configuration->gcodes a listener rule for that message that then executes
@pause Some message
so server has full control. It might execute a few more commands until pause takes place if they are already in send buffer.
You can also put the move to side in servers start pause script, so you get exactly what you want just controlled by server so you can still use manual control or change filament dialog.
But its crazy...The printer did exact the same thing....
Thanks a lot.
But there is a one little thing. By adding @pause to the gcode, the printer did first the "normal" pause routine and then the new "filament runout routine"
How can I prevent this?
Anyway. I modified the regular RS Pause script to my needs and added only @pause to the listener and its working great!
Thanks a lot!