diff options
author | dc42 <dcrocker@eschertech.com> | 2018-07-14 12:27:53 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-07-14 12:27:53 +0300 |
commit | dd360ac29a1dc96ecea19a17d24ffbc45b927c66 (patch) | |
tree | dd4eadadfd5c7396b253602171d292d3aeaeb6e9 /WHATS_NEW.md | |
parent | 9ec1b9619370f412f725a4316ae4574cbb9a9a26 (diff) |
Updated whatsnew for release 2.01beta2
Diffstat (limited to 'WHATS_NEW.md')
-rw-r--r-- | WHATS_NEW.md | 31 |
1 files changed, 29 insertions, 2 deletions
diff --git a/WHATS_NEW.md b/WHATS_NEW.md index 3265c199..264d2de8 100644 --- a/WHATS_NEW.md +++ b/WHATS_NEW.md @@ -1,8 +1,35 @@ Summary of important changes in recent versions =============================================== -Version 2.01beta1 (Duet 2 series) and 1.21.2 (Duet 06/085) -========================================================== +Version 2.01beta2 (Duet 2 series) and 1.22beta1 (Duet 06/085) +============================================================= + +[This release is in preparation] + +Upgrade notes: +- Compatible files are DuetWiFiserver 1.21 and DuetWebControl 1.21.2beta2. Use of DWC 1.21 or earlier may result in "Not authorized" disconnections if you have a password set. However, if your machine is a CoreXY then you may need to use DWC 1.21 for the axis jog buttons to work correctly. + +Bug fixes: +- Non-movement commands were not correctly synchronised with movement commands when there were more than 8 non-movement commands interspersed with more than 2 seconds of movement +- If M28/M29 was used in a macro file to then the commands between M28 and M29 were executed as well as being written to the target file +- If you used the jog buttons in DWC before homing the axes, and you didn't use M564 H0 in config.g, then as well as the "insufficient axes homed" error message, a stack underflow error message was produced +- Neither M561 nor G29 S2 adjusted the user Z coordinate if bed compensation was previously active (G29 S2 did if you ran it twice) +- Duet 06/085 only: fixed a buffer overflow in the Netbios responder code +- Duet 2 series: when an under-voltage event occurred, spurious driver status warnings/errors were sometimes reported +- Duet 2 series: when an under- or over-voltage event occurred, the VIN voltage reported was the current voltage, not the voltage when the event was recorded + +New features/changed behaviour: +- On the Duet 2 Maestro, the 2 optional add-on drivers are now assumed to be TMC2224 with UART interface +- When the Z probe type is set to 9 for BLTouch, the probe output is no longer filtered, for faster response +- If an error occurs while reading or writing the SD card, the operation is retried. The M122 report includes the maximum number of retries that were done before a successful outcome. +- On the Duet WiFi/Ethernet, at startup the firmware does additional retries when checking for the presence of a DueX2 or DueX5 and/or additional I/O expansion board +- When a resurrect.g file is generated, it now includes G92 commands just before it invokes resurrect-prologue.g, to set the assumed head position to the point at which power was lost or the print was paused. This is to better handle printers for which homing Z is not possible when a print is already on the bed. Caution: this doesn't allow for any Z lift or other movement in the power fail script. +- RTOS builds only: added a separate software watchdog to monitor the Heat task +- RTOS builds only: the software reset data now includes which task was active +- Upgraded compiler to 2018-q2-update + +Version 2.01beta1 (Duet 2 series) and 1.21.2beta1 (Duet 06/085) +=============================================================== Upgrade notes: - Compatible files are DuetWiFiserver 1.21 and DuetWebControl 1.21.2beta2. Use of DWC 1.21 or earlier may result in "Not authorized" disconnections if you have a password set. |