New firmware 1.20beta1
-
If your uncalibrated CPU temperature under-reads a lot, then the Duet could still be getting quite warm.
-
Well, in fact, default reading was 13°C above real CPU temp. So, fans started running at 35°C instead of 45°C. So CPU temp is not the issue.
-
Hi David,
Is using the HW floating point beneficial to specific performance aspects at this point? Also, is this release including all of alpha 7 enhancements? -
Feedback:
In Chrome on Win10 x64 I can scroll down on pages (print status, gcode files, etc) but within a second or two (AJAX refresh?) it pops back to the top. 1.19 was the same where earlier versions did not.On a print I had going this morning, I was at 97% and slid the speed control from 100% to 112% and the board crashed/restarted. The print is still usable, just not done, but it was a functional part and the top doesn't matter really. At some point during that print, it had acquired a different IP address also which was interesting.
-
Hi David,
Is using the HW floating point beneficial to specific performance aspects at this point? Also, is this release including all of alpha 7 enhancements?It mostly benefits particular machine architectures like SCARA which need to do a lot of floating point computations.
Feedback:
…On a print I had going this morning, I was at 97% and slid the speed control from 100% to 112% and the board crashed/restarted. The print is still usable, just not done, but it was a functional part and the top doesn't matter really. At some point during that print, it had acquired a different IP address also which was interesting.Did you run M112 after the restart to capture the software reset data? If so, please share it.
-
I actually did try m112 but it reset again. I'll do some testing to learn how to use that properly?
-
Great to have the new version out.
In case of a heater error, will it pause the printer?
-
Great to have the new version out.
In case of a heater error, will it pause the printer?
Beta 1 doesn't, but beta 2 will.
-
Feedback:
In Chrome on Win10 x64 I can scroll down on pages (print status, gcode files, etc) but within a second or two (AJAX refresh?) it pops back to the top. 1.19 was the same where earlier versions did not.Same thing happens to me (Also In Chrome on Win10 x64) I'm still on 1.19, I was hoping 1.2 might fix it (but I guess not?)
-
That would almost certainly be an issue between Chrome and DWC, so a firmware change won't help. I mostly use FireFox to access my Duets these days, because Chrome on my Win64 PC had a frequent habit of become completely unresponsive (on all tabs) for about 30 seconds before recovering - even when I wasn't connected to a Duet.
