diff options
| author | dc42 <dcrocker@eschertech.com> | 2020-04-30 17:32:25 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-30 17:32:25 +0300 |
| commit | 5041973caba0f3b83a2ab4b1e0a7bee4189391b2 (patch) | |
| tree | d43adeee24523acd6ece4ec6c1495e06e2630dfb /WHATS_NEW_RRF3.md | |
| parent | 70a81d93eb44267840661a8caa0ec824afa0574c (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 401eca4c..76e8c438 100644 --- a/WHATS_NEW_RRF3.md +++ b/WHATS_NEW_RRF3.md @@ -33,7 +33,8 @@ Bug fixes: - Pause and resume sometimes caused a small Z shift if bed compensation was in use and the tool had an X or Y offset - When an error message occurred in a GCode meta command, the error message included the command number/letter of the previous normal GCode command, which was confusing - When M584 was used to change the visibility of axes, seqs.move was not updated in the object model -- Duet3 with SBC: the SPI timeout was longer than the CAN timout, so SPI timeout errors were sometimes reported when a command used the CAN address a non-present board +- Duet3 with SBC: the SPI timeout was longer than the CAN timout, so SPI timeout errors were sometimes reported when a command used a CAN address for which no board was present +- Duet 3 only: Object model value fans[].actualValue was always reported as zero for fans on expansion and tool boards RepRapFirmware 3.01-RC10 ======================== |