Heater Bug or Feature at Reset
-
Ver 3.2
After reset (config.g save or M999), heater and Homing functions spin if selected until the HE temp drops below 50C. Everything kicks in around 50C and functions normally.
A work around is to set both HE temp and Bed Temp to desired value first and then activate each heater. The normal use case is when Z Zero is adjusted in Config.g file at steady state temps.
Separately, it would be nice to be able to save conditions before a reset and auto load the current settings on a reset.
Is this normal and is this workaround intentional and why? Just trying to understand the logic. -
@tommyb said in Heater Bug or Feature at Reset:
Separately, it would be nice to be able to save conditions before a reset and auto load the current settings on a reset.
Is this normal and is this workaround intentional and why? Just trying to understand the logic.This make no sense because, Reset will set the duet board to a defined state and switch every heater to off. This make the sense that if something went wrong that the printer does not run into this issue again.
for example:
Let's say your thermistor is defective and your hotend heats and heats... if you now reset the printer the hotend will switched off and all is secure. But with your whish the hotend will be reaktivated after a reset and it will heats again ... -
@tommyb maybe post your config.g file (and config-override.g if you use it) and we can see what is happening at boot?
Typically I don't use the reboot function when I edit the config file. If it is just one line (e.g. G31 to update z offset), I just copy paste the new line into the console in DWC to apply the new setting. For larger changes, you can run M98 P"config.g" to run the config as a macro. Either way it's quicker than rebooting and having to reset the heaters
-
@engikeneer
Ah - that is a really good solution....thank you for the recommendation. I should have tested this before posting.As for for Resetting with persistent settings, it is true there could be issues, but the point is that in a known state, it could be an option to hold all attributes on restart. And that would be up to the user to decide. It is always true for any over-ride situation, such as ignore over-travel limits, it could be bad, but when needed, it is a very useful option.
