Temp controlled output does not obey delay after print finishes #150
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
My enclosure ventilation fan is configured as "temperature controlled" , auto start up (when print starts) = yes, startup delay =0, auto shutdown = yes, shutdown delay = 600, temp control type = cooler, default value = 56, deadband = 2.
When print finishes the fan goes to "off" and does not ventilate/cool the enclosure. But it should.
Which log files should I provide to find out the cause?
And again, thank you for the best plugin ever, Vitor.
I was reviewing the code, I have not implemented the delay when the output type is set to "Temperature / Humidity Control", so it was really a bug letting you choose the delay. But I think I'll implement as it might be a good feature.
Thank you. It is be a good feature when you print toxic abs or nylon and want to ventilate the enclosure for like 10 minutes after print finishes. I would wait for this implementation :-)
thank you!
But keep in in mind that “cooling” might not be enought for this. As if the temperature of the enclosure get’s lower than the set temperature it will turn off the cooling either way, the delay on the auto shut off will not matter.
However You have several ways to get the funcionally that you want.
You can create a pwm linked temperature with a default off 100% and auto shutdown. This will keep a fan slower and controling cooling the temperature while printing, set it to 100% when the print is done and turn it off with the delay. You would need to usea mosfet to control thr fan, instead of a relay.
Another option is to use gcode on your end script to manually turn on and off the fan. The enclosure plugin understand special set of gcodes to control gpios from your pi.
Fixed on new release, but I'm actually have a better solution for this on a few days.
What is the better solution for this ?
Would it be easier to leave the pwm linked temperature script constantly active ?
Or at least as long as the delay is not respected?