Unsolved [3.4B3 - 6HC + SBC] M0 H1 turns off heaters
-
According to the gCode Wiki, "M0 H1" should leave the heaters enabled. This is not working.
I have no idea when this was introduced as we are just now attempting to use "M0 H1" at the end of a job. It properly runs "stop.g" but is disabling the heaters which we are explicitly trying to avoid in this situation.
Please let me know if we are incorrect in our understanding of M0 or if there is another way.
Thanks
-
@oozebot said in [3.4B3 - 6HC + SBC] M0 H1 turns off heaters:
It properly runs "stop.g"
If you have stop.g M0 will call that and you can specify what you want to happen.
Does M0 H1 work if stop.g is not present?
-
@phaedrux Whether stop.g is present or not, M0 H1 turns off the heaters. We were basing this off the following:
- If no H1 parameter is present, the heaters are turned off too.
It appears M0 is turning off the heaters regardless.
-
@oozebot this is a deliberate change in 3.4beta3. You can use a stop.g and/or cancel.g file to control whether or not heaters are turned off when M0 is run. I will update the wiki.
-
@dc42 Sorry, but M0 alone is also turning off the heaters. It properly calls stop.g but is turning off the heaters prior to it executing.
-
@oozebot I will check this.
-
@dc42 - we just got around to testing this in 3.4b4 and M0 H1 is still turning off the heaters.