-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add manual bed clearing - check if bed is clear using BedReady plugin every x seconds #209
Comments
Hey @Defozo - I see the value in having a way to automatically start up again when conditions are again good for printing. Could you share what your current clearing script is doing, including the GCODE/preprocessors? I might be able to offer more specific advice. One general concern I have is that BedReady may think the bed is clear while your on-site user is still clearing the bed - which sounds frustrating at best and a hazard to them at worst. Here are some ideas:
|
Thank you for your response and ideas. Just to add, the on-site user who clears the bed is not very tech-savvy and doesn't have much experience with using OctoPrint or CP. That's why I'm trying to find a way to simplify the process for him. Currently, the on-site user clears the bed manually whenever they see that the printer has finished printing. We have a system where he moves the bed along the Y-axis to the back (since when the printer finishes the print it moves the bed to the front), which lets me know that the bed is cleared by looking at the camera. This is also the position in which I took the snapshot with the BedReady plugin. I appreciate your ideas. I didn't actually know that I could use these REST API commands to resume the job. However, considering the above, I don't think I need any other interface for the on-site user and I think this functionality would be beneficial for other users of CP too. I'm using the standard setup that comes after installing CP with the profile for Prusa Mini. This is my bed-clearing script:
Finished script:
Managed Cooldown: My preprocessors: However, I'd like to clarify, I don't use CP when printing parts that have greater bed adhesion (eg. when using a brim) or when I want to make sure the part comes out in excellent quality. This is the case when I want the manual bed clearing. So, I'm not sure about the usefulness of my current scripts in this regard. I hope this clarifies things. Let me know if you have any further questions or suggestions. |
Moving the gantry to signal readiness is a pretty smart solution :) If you'd rather avoid a custom solution, then it sounds like a direct use of the plugin would be the best option. I'm imagining CPQ polling the check_bed method in BedReady when the next print is about to start. It wouldn't be too difficult to add - but I've got several other features in the pipe so it may take some time for this to be implemented. |
Small update - I've been sending PRs to fix up BedReady in preparation for deeper integration. Details at jneilliii/OctoPrint-BedReady#16 |
Is your feature request related to a problem? Please describe.
I don't find automatic bed clearing useful in some applications. Eg. sometimes when printing with TPU and brim the parts are stuck hard and they move with the bed. Then, I need to ask someone else to clear the bed as I often don't have physical access to the printer I use. This, however, may not happen immediately.
Describe the solution you'd like
I'd like to be able to add gcodes to the queue and make the Continuous Print wait for the bed to be ready before starting each print.
Describe alternatives you've considered
This probably could be already achieved using Scripts & Preprocessors, but I'm unsure how.
Additional context
There are some API/Helpers available for the BedReady plugin if that's necessary: jneilliii/OctoPrint-BedReady#9
The text was updated successfully, but these errors were encountered: