diff options
| author | dc42 <dcrocker@eschertech.com> | 2020-04-24 18:17:03 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-24 18:17:03 +0300 |
| commit | d942bded69fdb2c24f61b3f6f031d11057a8af45 (patch) | |
| tree | c4532c171df64c2fe25885cbb61261dc9bd70fd4 /WHATS_NEW_RRF3.md | |
| parent | 35c5d2e5d30d7b045c703c69f3dba2947dd5b8c6 (diff) | |
Update WHATS_NEW_RRF3.md
Diffstat (limited to 'WHATS_NEW_RRF3.md')
| -rw-r--r-- | WHATS_NEW_RRF3.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/WHATS_NEW_RRF3.md b/WHATS_NEW_RRF3.md index 38c69155..6256d05c 100644 --- a/WHATS_NEW_RRF3.md +++ b/WHATS_NEW_RRF3.md @@ -23,7 +23,8 @@ Bug fixes: - When the minimum extrusion or retraction temperature was changed using M302, the updated values were not reported in the rr_status and M308 responses (this is long-standing bug) - When the minimum extrusion or retraction temperature was changed using M302, the appropriate object model sequence number was not upated, so DWC and DSF were not aware of the change - Non-movement commands that needed to be synchronised to the movement queue were sometimes executed too early -- M3 and M5 commands in laser mode were sometimes executed too early +- M3 and M5 commands in laser mode were sometimes executed too early, often by 1 move +- Error messages from G1 and G2/G3 commands were lost RepRapFirmware 3.01-RC9 ======================= |