diff options
-rw-r--r-- | WHATS_NEW_RRF3.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/WHATS_NEW_RRF3.md b/WHATS_NEW_RRF3.md index 76e8c438..4600a389 100644 --- a/WHATS_NEW_RRF3.md +++ b/WHATS_NEW_RRF3.md @@ -20,20 +20,20 @@ New features/changed behaviour: - The PanelDue port (or IO_1 on Duet 3) can now be configure to operate in raw (non-PanelDue) serial mode using command M575 P1 S2 B### where ### is the required baud rate. In this mode it will default to Marlin-type responses. - HTTP command rr_gcode with no gcode parameter now returns the buffer space, and rr_gcode with an empty gcode parameter no longer adds an empty command to the buffer - Skew compensation parameters have been added to the object model, in move.compensation.skew -- Duet WiFi/Ethernet only: added I2C transaction count and transactions/minute to M122 diagnostics +- Duet WiFi/Ethernet: added I2C transaction count and transactions/minute to M122 diagnostics - Added longest SD card read time (since last M122) to diagnostics - Longest SD card write time in diagnostics now excludes delays inserted by RRF between retries and the CRC calculation time - The "unknown value" message when looking up object model values now includes the name of the unknown value - The object model now reports invisible axes as well as visible ones -- It was not possible to set up a M581 trigger to trigger on both low->high and high->low transitions of an endstop or input pin -- If you used the M581 C parameter and you had a C axis, it would trigger on changes to the state pof the C endstop -- Disabling a trigger response to an niput or endstpo changed using the C-1 parameter didn't work 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 a CAN address for which no board was present +- It was not possible to set up a M581 trigger to trigger on both low->high and high->low transitions of an endstop or input pin +- If you used the M581 C parameter and you had a C axis, it would trigger on changes to the state of the C endstop +- Disabling a trigger response to an input or endstop using the C-1 parameter didn't work +- Duet 3 with SBC only: 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 |