Best posts made by jbjhjm

@chrishamm works perfectly fine thank you for helping me out!

@t3p3tony just upgraded, will check this later today!

Had some heater faults due to layer fan cooling down hotend too much.
Have to figure out why PID is off/doesn't compensate, but that's another topic.

This is about when heater fault state actually kicks in.
The annoying experience I just made is: One will not notice until it is too late to check/fix.
The printer will not pause, there will be no error message.
If you're lucky you'll stumble upon the lowering temp chart graph or notive the small "fault" label on DWC.

My proposal for improvements are:

• RRF should log an error message on heater fault to make it more visible
• RRF should call system macro heaterfault.g if it exists to allow for individual handling

A fault should attract attention immediately. It may be a threat to the printer, even catch fire. In best case the print is unusable.
In any of these cases I would want to be notified immediately.

Old threads discussing this without visible results:

• https://forum.duet3d.com/topic/1603/temperature-fault-macro
• https://forum.duet3d.com/topic/3156/how-should-the-firmware-respond-to-a-heater-fault/13

OwenD created a deamon.g which can be used.
But I consider it a workaround - complicated solution, and it will not react immediately due to ~1Hz frequency.
Pausing the print there might already be too late for flawless continuation.
https://forum.duet3d.com/topic/20722/heater-fault-checking-routine-to-be-run-in-daemon-g

A macro would be best; I'd use it to do various things:
pause the job, display an error, saving resurrect state and generate audible sound to let me know something's off there.

Pausing works fine again and the speed multiplier seems to be fixed too!

@t3p3tony weird, I just powered up to check on any errors as you suggested, but this time everything was initialized correctly.
I'll let you know here in case it happens again.

@chrishamm that fixes it thank you!