Thermostatic Fan no longer functions after print job abort
-
@adammhaile I meant manually turn on the heater to above 50 degrees - does the fan come on an off when you're not using any macros/gcode files?
-
@Phaedrux said in Thermostatic Fan no longer functions after print job abort:
How are you aborting the print job? Can you post your cancel.g file?
I don't have a cancel.g file
My stop.g file is empty (not sure if that's the same thing)
You can find all my configs here: https://github.com/ManiacalLabs/3DPrinterData/tree/d4753824bfa84177b212049f7c56c2eb2026ae9f/Daedalus/config@qablos said in Thermostatic Fan no longer functions after print job abort:
@adammhaile I meant manually turn on the heater to above 50 degrees - does the fan come on an off when you're not using any macros/gcode files?
Yes - it will work as expected if I change the hotend temp up until I cancel an in progress print.
-
What do you have in your slicer start gcode?
M106 P0 S1 H1 T50
Can you try using S1 instead of S255?
-
@Phaedrux said in Thermostatic Fan no longer functions after print job abort:
What do you have in your slicer start gcode?
From PrusaSlicer
M140 S[first_layer_bed_temperature] M104 S[first_layer_temperature] G28 M190 S[first_layer_bed_temperature] M109 S[first_layer_temperature] G1 X0.0 Y0.0 Z1.0 F1000.0 ; prepare to prime G92 E0 ; reset extrusion distance G1 Z0.2 F1000.0 G1 X60.0 E9.0 F1000.0 ; priming G1 X125.0 E12.5 F1000.0 ; priming G1 Z0.5 F1000.0 G92 E0 ; reset extrusion distanceS1 vs S255 doesn't make a difference.
-
Try creating a cancel.g and defining what you want to happen when you cancel the print. (turn off heaters, home x and y, etc) and see if that makes a difference.
-
Do you have the same problem when a print job ends by completion?
-
@baird1fa said in Thermostatic Fan no longer functions after print job abort:
Do you have the same problem when a print job ends by completion?
No - it works fine if it completes normally.
@Phaedrux said in Thermostatic Fan no longer functions after print job abort:
Try creating a cancel.g and defining what you want to happen when you cancel the print. (turn off heaters, home x and y, etc) and see if that makes a difference.
Ok, I'll see if I can come up with something.
Any examples on hand I can draw from? -
What is in you ending script from the slicer? I had something similar happen with my BLTouch servo pin (PWM) and it turns out that is was caused by the stepper for the direct drive staying active. I had to send an M18 E0:1 command time disable my extruder.
It might be something similar if you have a direct drive or an M18 that is in the ending script of your slicer GCodes.
-
@baird1fa said in Thermostatic Fan no longer functions after print job abort:
What is in you ending script from the slicer? I had something similar happen with my BLTouch servo pin (PWM) and it turns out that is was caused by the stepper for the direct drive staying active. I had to send an M18 E0:1 command time disable my extruder.
It might be something similar if you have a direct drive or an M18 that is in the ending script of your slicer GCodes.
But it's not getting that far - this is only for canceled jobs. The end script never occurs.
Besides it's just:M106 S0 ; turn off cooling fan M104 S0 ; turn off hotend M140 S0; turn off bed G91 G1 H2 Z3 F6000 ; lift Z relative to current position G90 G1 X0 Y280; part removal G91 G1 H2 Z-2 F6000 ; lower Z again G90 ; absolute positioning -
When you cancel a job do you pause it first, then cancel? If so the you are calling pause.g then stop.g, so there is no need for cancel.g. But try adding the ending script into stop.g and see if that works.
Except maybe the part removal moves.
-
Ok, we ended up creating a
cancel.gfile with the same content as the above end script and now it all works fine. -
Interesting. The cancel.g file is optional and does not exist by default, so if this was a widespread bug I think we'd have heard about it more by now.
-
@Phaedrux said in Thermostatic Fan no longer functions after print job abort:
Interesting. The cancel.g file is optional and does not exist by default, so if this was a widespread bug I think we'd have heard about it more by now.
Yeah - I don' t know. Maybe something that should/could be tweaked in my config.g
Though, in general I've found the Duet3 to be.... maybe not buggy, but quirky. For example, if you try to adjust baby-steps while it's heating before a print job, the whole thing hangs and will never start printing. Have to power cycle everything. Stuff like that and a few other small thing I just haven't gotten around to posting about
-
@adammhaile that's an interesting not about the babysteps during preheat. I've done that a few times and it hasn't cause me a problem. the bugs must also be linked to specific setups, a perfect storm situation as it were.
