I have reported same/similar fault: After that, I have experienced another one, during print, at 1st quarter of 2-hour job. Same type of error message. Between my report and that last fault, I have upgraded/replaced my PSU and heaters to 24V versions and have re-run autotuning. Since it has been difficult to reproduce and I really haven't had the time to test thoroughly, I haven't complained anby minimum - Duet
Found a typo: Quote14:55.21 M303 Heater 1 tuning succeeded, use M207 H1 to see result Should be M307 Updating reprap wiki regarding autotuning releated topics would be nice tooby minimum - Duet
Quotedc42- It would make sense to stop or at least pause the print if a heater fault occurs. I'll add this to the work list for the next release. Any thoughts on what would be best? I think Smoothieware responds to a heater fault by executing an emergency stop, but perhaps that is a little too drastic? Yes, please add that. As to what would be best, I wish I knew. Some kind of configurable optioby minimum - Duet
Creep is fixed. I tried to use the new autotuning feature: For test temp, I set 200C. Heats up nice and very smoothly until temp more or less stabilises at about 197.5-198C. After a short period I get message "Error: heating fault on heater 1, temperature rising much more slowly than the expected 0.0°C/sec" and heater faults. I'm sure most of the problem is coming from my abnormally powerful hby minimum - Duet
Quotedc42 1. What temperature did you set, before you saw it creep to 170C? 2. Are you measuring the temperature using a thermistor, thermocouple, or RTD? If a heater gets into a fault state, you can reset it using M562 P# where # is the heater number. M0 will turn all heaters off. UPDATE: I have just managed to reproduce heat creep on one of my printers by using a noisy thermistor channel. Soby minimum - Duet
1.15a: Right after firmware upgrade (and reboot that follows), temperature creep still there. Switching off and on seemed to do the trick until after some time got message "Error: heating fault on heater 1, temperature excursion too large". After that of course heater at fault and unresponsive. Tried once more off-on, now got temp creeping up again. I'm able to control heater but since I leftby minimum - Duet
Silly me didn't back up www directory before upgrading DWC ... So now after downgrading firmware to 1.14, I'll get right after log in to web control the next message: QuoteCommunication Error An AJAX error has been reported, so the current session has been terminated. Please check if your printer is still on and try to connect again. Error reason: Unknown request Tried flushing browser's (Cby minimum - Duet
Yup, the temperature creep is still there. Hard reset works. Freshly downloaded 1.15 with DWC 1.12 Edit: And so is the heater H1 "fault" still there. All the same as in my 1st post. Back to 1.14by minimum - Duet
Quotedc42Mait, were you running one of the 1.15 release candidates, or the 1.15 release? Both those issues were reports in the release candidate, and both are believed fixed in the 1.15 release, which is available here . Ok, I downloaded it a few days ago, and I think it was rc3 (can't check right now). Will download the final 1.15 and re-upgrade. Thanks for fast reply PS: I vote for the changelby minimum - Duet
I just ran into two issues after upgrade. 1. Web interface reported H1 heater fault, heater not responding to web interface controls or G-code controls. I run a 12V module-type PSU on about 15VDC (cranked up the Vadjust) because my chinese (supposedly 12V) bed takes about an hour to get ~60C. With 15V, I'll get 90 to 100C which is OK with buildtak bed surface. New M303 auto-tuning seems to funcby minimum - Duet