Thank you for this video. It allowed me to get my Ender 5 Pro EZOUT working. I had identified the pin but did not (yet) research the rest. It worked without issue all thanks to you and this video.
Chris thank you so much for this video. I have been racking my brain trying to figure out why it would never pause when the sensor was triggerard and after watching your video I figured it out. Thanks again for ALL your great videos I really do learn a lot from them
Chris, lots of good information to explain the process and get started. Hopefully you will expand on this. I have worked on getting a good M600 replacement in Klipper and have been using the one in RATOS since the last version upgrade. It is very simple as all of the work is done in a macro M600 Here is the printer.cfg entry [filament_switch_sensor runout_sensor] pause_on_runout: False switch_pin: PG15 # also known as e4stop / e4det runout_gcode: M600 # The M600 code does all of the movement of the carriage and retraction of the filament, It also makes sure that the bed stays on. This use of the M600 enables it to be called from gcode for filament changes during printing.
I was about to ask, if M600 would do, but you already provided the answer 👍 Actually I find klipper more difficult to set up. Not because it's different from Marlin, but because there are dozens of macro implementations to choose from, all slightly different, some maybe too old for 0.12. Documentation of macros and klipper configuration itself could need some improvement 😉
@@kimmotoivanen I'm lucky, as most of my Klipper use is in Ratos for the Rat Rigs. The other Klipper install is on the Peoply Magneto X and the installed macros are all I need. The M600 command is the main one I use for color changes and both Orca or Prusa slicer will add it automatically when you do a color change
@@ChrisRiley It is not, it's 5 mm. The percent symbol is from the Jinja block and because the return type of printer.toolhead.axis_maximum.whatever is the maximum axis size in mm, the return type of the whole expression will be 5 mm from the actual maximum.
Hi Chris, greetings from France, you helped me a lot understanding Marlin and now putting Klipper on my Enders. Would you make a video about configuring the speeds and accelerations into slicers please? I'm a bit lost doing trial and error, even after changing some values, my print time is not so shorter, maybe I'm missing some points. Keep it up and thank you for the great videos!
Thank you! Yes, these can be very hard to understand on how to actually make things faster. I will see what I can do to put all this in a video. Thank you for watching!
11:22 I would love a video on going deeper into macros and all that confusion. For someone who doesn’t understand much about code it is like a whole differ language 😂. Very helpful video as always Sir 👍🇦🇺😊
I would love to see more detail on preventing an issue if you accidentally press resume. Why does it even allow you to press resume if there is no filament?
Great video Chris! I've been trying to make my K1C printer to keep printing until uses 50cm of filament between the moment the sensor is triggered and the printer pauses. This is the distance between the sensor and the extruder and this is the waste amount I ended up when I run out of filament. I can't figure out a way to do this. I see you used time... any help here? Thanks
I just bought two of the BTT sensor v2 for a tronxy x5sa and an Octopus Pro board, cant use it though, the TMC 2209's refuse to work without throwing errors and disabling themselves.
Chris. What if u have a ptfe tube all the way from the hotend to the sensor? And the sensor is a regular endstop switch with a lever? Won`t the filament collide with the lever when u retract that much?
Yes, it can, I have run into that before. I have seen printer where they leave the PTFE loose on the extruder side so when it backs out, it will push the tube out of the way.
hi chris! very interesting video.. but you got me a little confused. If everything is set up correctly, and i run out of filament, the system will pause, do what ever i tell it and i hit resume once the new filament is in place and it will restart.. OK, i got that.. But if i run out a second time? it seemed to me in the video that it will not stop but continue? or did i misunderstand? Luc
Hey, as long as you reset the switch after it runs out, it will trigger again. So filament runs out, it will pause, you load more resetting the switch, then hit resume, everything will work as it should. Next time it runs out, it will do the same thing. The only time you run into an issue is if you hit resume with out resetting the filament switch.
I have filament runout set on my sv06 plus. It is running on a pad 7 with klipper and we'll I have to say it is not reliable. It seems to work when it wants to. I noticed that it will work sometimes and keep bed warm and other times it will not keep bed warm and then require a home before you can resume. And guess what. If you hit home it will crash into the print. Lol. So my trust in the option is not so good. I had no issues with it on marlin.
I am trying to get klipper to work for the 12 time. Installing on a Dell Wyse 3040 Thin Client with Debian 12. 1st issue is no wifi, and during setup of configuration, wifi is seen and i add my PW to log in and click continue but it takes me back to choosing my ssid, which i choose and go through it all again
Yeah, that's cool. But I recommend installing filament movement sensor instead of this useless switch. Which is much more versatile and a must have in my opinion. You can make it from a bearing and an optical sensor. Plenty of models on the web.
If you want to have Klipper check the runout sensor before the print starts, and cancel the print before it actually prints, try placing this code into your start_print macro just before the purge line is drawn: {% if not printer["filament_switch_sensor "].filament_detected %} RESPOND TYPE=error MSG="No filament detected, aborting print" #replace with M117 if you have klipperscreen CANCEL_PRINT {% else %} RESPOND MSG="Filament detected... continuing print" #replace with M117 if you have klipperscreen {% endif %} This code Is driven by the sensor state, and not by a trigger event. It should be included in main Klipper in my opinion.
well done.
Thank you!
Thank you for this video. It allowed me to get my Ender 5 Pro EZOUT working. I had identified the pin but did not (yet) research the rest. It worked without issue all thanks to you and this video.
Glad it helped!
Chris thank you so much for this video. I have been racking my brain trying to figure out why it would never pause when the sensor was triggerard and after watching your video I figured it out. Thanks again for ALL your great videos I really do learn a lot from them
Happy to help! Thanks for watching
Chris, lots of good information to explain the process and get started. Hopefully you will expand on this. I have worked on getting a good M600 replacement in Klipper and have been using the one in RATOS since the last version upgrade. It is very simple as all of the work is done in a macro M600
Here is the printer.cfg entry
[filament_switch_sensor runout_sensor]
pause_on_runout: False
switch_pin: PG15 # also known as e4stop / e4det
runout_gcode: M600 #
The M600 code does all of the movement of the carriage and retraction of the filament, It also makes sure that the bed stays on.
This use of the M600 enables it to be called from gcode for filament changes during printing.
Great Dave, thanks for the info!
I was about to ask, if M600 would do, but you already provided the answer 👍
Actually I find klipper more difficult to set up. Not because it's different from Marlin, but because there are dozens of macro implementations to choose from, all slightly different, some maybe too old for 0.12.
Documentation of macros and klipper configuration itself could need some improvement 😉
@@kimmotoivanen I'm lucky, as most of my Klipper use is in Ratos for the Rat Rigs. The other Klipper install is on the Peoply Magneto X and the installed macros are all I need. The M600 command is the main one I use for color changes and both Orca or Prusa slicer will add it automatically when you do a color change
Hey, I'm looking for a tutorial on adding an endstop runout sensor to my v-core3, do you have a link?
Another great video Chris! I'm setting up Klipper on the Artist-D Pro and your video made the code for the filament runout sensors very easy. Thanks!
That's great, thanks for watching!
11:00 isn’t it -5mm not 5%? Looking forward for your next video. You did a tap install on Vorons or other printer with Klipper already?
I THINK that would be 5% of the move, but I will confirm. I haven't done the tap install yet, but I do intended to do a video on it for the Trident.
@@ChrisRiley It is not, it's 5 mm. The percent symbol is from the Jinja block and because the return type of printer.toolhead.axis_maximum.whatever is the maximum axis size in mm, the return type of the whole expression will be 5 mm from the actual maximum.
Thanks as always Chris. I like a deep dive.. ❤
Thank you!
Hi Chris, greetings from France, you helped me a lot understanding Marlin and now putting Klipper on my Enders. Would you make a video about configuring the speeds and accelerations into slicers please? I'm a bit lost doing trial and error, even after changing some values, my print time is not so shorter, maybe I'm missing some points. Keep it up and thank you for the great videos!
Thank you! Yes, these can be very hard to understand on how to actually make things faster. I will see what I can do to put all this in a video. Thank you for watching!
11:22 I would love a video on going deeper into macros and all that confusion. For someone who doesn’t understand much about code it is like a whole differ language 😂.
Very helpful video as always Sir 👍🇦🇺😊
Thanks! More to come
I would love to see more detail on preventing an issue if you accidentally press resume. Why does it even allow you to press resume if there is no filament?
Yes, I think we would have to build in some more complicated logic in the macro to make it fact check the sensor to keep this from happening.
Cool video!
Thank you!
Exellent! I'n just about to implement my btt smart filament sensor after the marlin to klipper switchover
Cool, let us know how it goes!
Thanks alot for this detailed infos. Possible to get your configuration file as a reference?
Here you go. drive.google.com/file/d/107AKfb9pdSrDl3zWpGUwOQBPdlGNTGDt/view?usp=drive_link
Wonder if this can be done with an optical sensor. I have one left over from a TAP project.
I'm sure it would work. It would be best to create a mount that uses a flag to trigger the sensor rather than the filament itself.
Great video Chris! I've been trying to make my K1C printer to keep printing until uses 50cm of filament between the moment the sensor is triggered and the printer pauses. This is the distance between the sensor and the extruder and this is the waste amount I ended up when I run out of filament.
I can't figure out a way to do this. I see you used time... any help here?
Thanks
Yeah, I would have to look at this again, time was the only way I could think of to do it. Maybe there is a better way, count steps maybe?
I just bought two of the BTT sensor v2 for a tronxy x5sa and an Octopus Pro board, cant use it though, the TMC 2209's refuse to work without throwing errors and disabling themselves.
Strange, what type of errors are you getting?
Chris. What if u have a ptfe tube all the way from the hotend to the sensor? And the sensor is a regular endstop switch with a lever? Won`t the filament collide with the lever when u retract that much?
Yes, it can, I have run into that before. I have seen printer where they leave the PTFE loose on the extruder side so when it backs out, it will push the tube out of the way.
hi chris! very interesting video.. but you got me a little confused. If everything is set up correctly, and i run out of filament, the system will pause, do what ever i tell it and i hit resume once the new filament is in place and it will restart.. OK, i got that.. But if i run out a second time? it seemed to me in the video that it will not stop but continue? or did i misunderstand?
Luc
Hey, as long as you reset the switch after it runs out, it will trigger again. So filament runs out, it will pause, you load more resetting the switch, then hit resume, everything will work as it should. Next time it runs out, it will do the same thing. The only time you run into an issue is if you hit resume with out resetting the filament switch.
I have filament runout set on my sv06 plus. It is running on a pad 7 with klipper and we'll I have to say it is not reliable. It seems to work when it wants to. I noticed that it will work sometimes and keep bed warm and other times it will not keep bed warm and then require a home before you can resume. And guess what. If you hit home it will crash into the print. Lol. So my trust in the option is not so good. I had no issues with it on marlin.
I'm a big fan of Marlin, thanks for watching!
I am trying to get klipper to work for the 12 time. Installing on a Dell Wyse 3040 Thin Client with Debian 12.
1st issue is no wifi, and during setup of configuration, wifi is seen and i add my PW to log in and click continue but it takes me back to choosing my ssid, which i choose and go through it all again
Hey George, my guess is Network Manager isn't starting, not sure if this would be helpful. th-cam.com/video/ulBeN9pFRE4/w-d-xo.html
@@ChrisRiley Thank You
Yeah, that's cool. But I recommend installing filament movement sensor instead of this useless switch. Which is much more versatile and a must have in my opinion.
You can make it from a bearing and an optical sensor. Plenty of models on the web.
I have played around with them and done some videos, I might look into making one myself.
TFT E3 V3 FIRMWARE UPDATE, please.l can't fix my printer, and I think that is the problem
Hey, what seems to be the issue?
If you want to have Klipper check the runout sensor before the print starts, and cancel the print before it actually prints, try placing this code into your start_print macro just before the purge line is drawn:
{% if not printer["filament_switch_sensor "].filament_detected %}
RESPOND TYPE=error MSG="No filament detected, aborting print" #replace with M117 if you have klipperscreen
CANCEL_PRINT
{% else %}
RESPOND MSG="Filament detected... continuing print" #replace with M117 if you have klipperscreen
{% endif %}
This code Is driven by the sensor state, and not by a trigger event. It should be included in main Klipper in my opinion.
Awesome! Thanks