diff options
| author | dc42 <dcrocker@eschertech.com> | 2020-04-11 21:47:50 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-11 21:47:50 +0300 |
| commit | b4b7d9b69ab5f702f2f941c1a6e61ad906639cf2 (patch) | |
| tree | 28f3a913d11b42dd2eeb16aee961ac71ba0c548b /WHATS_NEW_RRF3.md | |
| parent | 3fdcf50b393c19d7a724e3bc747fdcacb2f0198e (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 df181978..7609cca6 100644 --- a/WHATS_NEW_RRF3.md +++ b/WHATS_NEW_RRF3.md @@ -24,7 +24,8 @@ Bug fixes: - The object model sequence numbers were not updated when several object model variables were changed, so DSF and DWC did not know they had changed and did not update their copies of them - M950 J# command with no other parameters reported the incorrect state of the input - If nested config.g files were used (e.g. because M505 was used to change the system folder) then the effect of M83, G1 Fxxx etc. commands in the nested file were lost -- G30 and G29 commands did not set variable 'result' when some types of error occurred, e.g. when the Z probe was already triggered at the start of the proibing move. +- G30 and G29 commands did not set variable 'result' when some types of error occurred, e.g. when the Z probe was already triggered at the start of the probing move. +- In the object model the speed factor and extrusion factors were only reported to one decimal place - Other fixes related to communication with DSF Known issues and limitations: as for 3.01-RC6 |