There are three Thermal Error screens in the current design.
If any one of those conditions is triggered, it may not be clear whether the problem is with the Nozzle or the Bed.
Hoping to provide important troubleshooting clues, I have added Nozzle and Bed Sensor and Target readouts to all three of these thermal error screens:
Thermistor Error
Thermal Runaway
Heating Failed
While making these edits, I was also made aware (by InsanityAutomation) of a problem with the Z-Offset buttons implemented on the Printing Tune menu, which caused problems when held down rather than being tapped. I implemented the fix that he recommended; changing up/down buttons to a disposable signal instead of a constant signal.
Other miscellaneous edits made at this pull request are:
Nudged the temperature value displays to a common and suitable spacing on all screens.
Replaced the two-part zip files of the new DGUSTool with a single consolidated file. (Was able to Push from Desktop GitHub to Online GitHub, Uploading to Online GitHub enforces a smaller filesize limitation.)
Added a folder of Sample Screen Images, to help guide and inform users of this firmware
Stopped using the build.ps1 script to build the DWIN_SET. Noticed that it renames files 13 and 14 from what names the new tool is giving them. Speculating (but have not yet confirmed by testing) that the white noise screen at the end of flashing to DGUS2 v4.5 screens may be a condition aggravated by those filenames having been changed.
I have designated this DWIN_SET as 61F_RC_090522_v2.
There are three Thermal Error screens in the current design.
If any one of those conditions is triggered, it may not be clear whether the problem is with the Nozzle or the Bed.
Hoping to provide important troubleshooting clues, I have added Nozzle and Bed Sensor and Target readouts to all three of these thermal error screens:
While making these edits, I was also made aware (by InsanityAutomation) of a problem with the Z-Offset buttons implemented on the Printing Tune menu, which caused problems when held down rather than being tapped. I implemented the fix that he recommended; changing up/down buttons to a disposable signal instead of a constant signal.
Other miscellaneous edits made at this pull request are:
I have designated this DWIN_SET as 61F_RC_090522_v2.