diff options
| author | dc42 <dcrocker@eschertech.com> | 2019-11-29 21:46:47 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-29 21:46:47 +0300 |
| commit | 0cdb4672c090c079c4360ac49c22ddfa157a006b (patch) | |
| tree | 4c5ae61f0485e4b55b30f7a896ee1ff4d3306b7d | |
| parent | fb41486a70b981e84a6e3abfb4650974e7a90c9c (diff) | |
Updated whatsnew file for 2.05RC12.05RC1
| -rw-r--r-- | WHATS_NEW.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/WHATS_NEW.md b/WHATS_NEW.md index e8e2b3ba..3cd76338 100644 --- a/WHATS_NEW.md +++ b/WHATS_NEW.md @@ -1,8 +1,8 @@ Summary of important changes in recent versions =============================================== -Version 2.05 (in preparation) -============ +Version 2.05RC1 +=============== Compatible files: - DuetWiFiServer 1.23 - DuetWebControl 2.0.4 (recommended) or 1.22.6 @@ -19,6 +19,8 @@ Bug fixes: - When using SCARA kinematics the calculation of the minimum achoievable radius was incorrect. Depending on the B parameter of the M667 command, this could result in spurious "Intermediate position unreachable" errors, or non-extruding G1 moves being turned into G0 moves. - A badly-formed GCode file that returned the layer height or object height as nan or inf caused DWC to disconnect because of a JSON parse failure - M579 scale factors were not applied correctly to G2 and G3 arc moves +- Spurious newlines were sometimes sent to USB and other output channels when commands such as M106 were deferred to execute in step with movement commands, or when commands were executed in response to triggers +- Messages sent to USB and Telnet output channels did not always time out when the channel became unavailable for writing Version 2.04 ============ |