Closed robvoi closed 5 years ago
Hi @robvoi,
It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions).
Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days.
For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md
The log can still be attached to this ticket - just add a comment and attach the log to that comment.
Best regards, ~ Your friendly GitIssueBot
PS: I'm just an automated script, not a human being.
There is documentation in examples-extras.cfg, although admittedly it makes an assumption that you understand how to use Klippers pause/resume functionality. The filament sensor makes use of the [pause_resume] module if you have pause_on_runout set to True. After a change you use the RESUME gcode to proceed with the print.
It appears the Klipper log file was not provided. I'm closing this now, sorry. Feel free to attach the log to this ticket sometime in the future, or create a new issue once you can provide the log file.
I don't get how the filemant runout sensor feature is meant to work. I see that I can set gcode for the case the filament runs out. Clear. How do I proceed the job once the filament has been changed?
Some explanation and maybe an example config would be great. Thanks fot the support.