-
Notifications
You must be signed in to change notification settings - Fork 31
Changelog DSF 3.x RC
Christian Hammacher edited this page Aug 31, 2022
·
23 revisions
Compatible versions:
- RepRapFirmware 3.4.2-rc3
- DuetWebControl 3.4.2-rc3
Upgrade notes:
- Instead of the previous
apt upgrade
command it is now required to useapt dist-upgrade
. Users ofunattended-upgrade
are not affected
New features:
- Program from the
duettools
package now provide return codes and come with improved error handling
Bug fixes:
-
pip3
(Python 3) is now used for dependency installations instead ofpip
(Python 2.7) - Disposal of already closed code files could lead to unexpected exceptions
Compatible versions:
- RepRapFirmware 3.4.2-rc2
- DuetWebControl 3.4.2-rc2
Changed behaviour:
- Job task flushes pending codes one last time on completion to allow for user-generated G-codes
Bug fixes:
- Codes from an intercepting connection were intercepted again by the same connection
Compatible versions:
- RepRapFirmware 3.4.2-rc1
- DuetWebControl 3.4.2-rc1
New features:
- Added new "tags" string array to plugin manifest
Bug fixes:
- Made SPI error recovery on empty data more robust
Compatible versions:
- RepRapFirmware 3.4.1-rc2
- DuetWebControl 3.4.1-rc2
New features:
- Added OpenAPI definition for HTTP APIs
Changed behaviour:
- Main object model class is no longer sealed
Bug fixes:
- Improved logging in IPC backend to avoid unnecessary memory allocations
- Rotary delta configurations set the wrong kinematics type in the object model
- Added network.interfaces[].state in SBC mode
- Sequential printing could provoke an exception in the layer update code (i.e. when the layer number went down)
Compatible versions:
- RepRapFirmware 3.4.1-rc1
- DuetWebControl 3.4.1-rc1
Changed behaviour:
- Improved SPI protocol error handling
- DCS outputs an info message when the connection is lost because of too little CPU time
Bug fixes:
- DSF user and AppArmor templates were missing permissions for webcam access on Debian Buster
- Some object model values were not reactive in DuetAPI
- Usage of the
custom
input shaper was not supported -
M112
andM999
did not wait for potential firmware updates to finish first - Code files could be edited while they were being processed
- DuetHttpClient did not set valid
X-Session-Key
when reconnecting to Duets in SBC mode
Compatible versions:
- RepRapFirmware 3.4-rc2
- DuetWebControl 3.4-rc2
Upgrade notes:
- Now DSF uses
pip
for management of third-party Python libraries. It is recommended to install it usingsudo apt install python3-pip
- The default group of I²C device nodes has been changed to
gpio
. If you are using I²C, make sure that applications accessing it are part of thegpio
group (e.g. viagpasswd -a <user> gpio
) - When you upgrade the DuetPiManagementPlugin package from v3.4-b6 or older, you will see an error message due to a missing dependency of the old package being upgraded (
Error: An assembly specified in the application dependencies manifest (PluginManager.deps.json) was not found
). You can ignore this message, it should be fixed as soon as v3.4-rc1 or newer is installed.
New features:
- Implemented new GPIO permission (includes I2C and SPI devices) for third-party plugins
- Added new array to plugin manifest allowing custom installation of Python libraries via pip (requires pip to be installed first)
- Thumbnail data is now checked for valid base64 content before it is assigned
Bug fixes:
- DWC launch script was not included in the source files
- Even object heights were not correctly processed
- duettools package was not fully updated before the update of duetpimanagementplugin started resulting in possible (yet harmless) error messages
- M997 and M999 could show "Operation has been cancelled" rather than completing normally
- When plugins were uninstalled and they were auto-started, they were not removed from the auto-start list
- Update prompt did not display expansion board names
- Absolute file paths without leading slash (e.g.
M98 P"0:macros/foo.g"
instead ofM98 P"0:/macros/foo.g"
) were not correctly processed by DSF
Compatible versions:
- RepRapFirmware 3.4-rc1
- DuetWebControl 3.4-rc1
New features:
- Added thumbnail support
Changed behaviour:
- DuetPiManagementPlugin uses relative file paths to support more Linux distros
Bug fixes:
- Tool for custom HTTP endpoints did not replace query values when starting other programs
- Packaged plugins (like duetpimanagementplugin) could be uninstalled using DWC
- Removed redundant info message during upgrade from removal script
Compatible versions:
- RepRapFirmware 3.3-rc3
- DuetWebControl 3.3-rc3
Bug fixes:
- M0 called
stop.g
instead ofcancel.g
when a print was cancelled - DCS does no longer check SPI responses from IAP while upgrading the firmware to lower the risk of upgrade issues
- Plugins were never started in non-SPI mode
- DCS postinst script failed if the service was previously enabled but no Duet was attached at the time of the upgrade
- When codes were intercepted, the
SourceConnection
property was not always populated - When DCS was configured to never terminate on reset, sometimes it failed to establish a connection again
- Subscribe connection clients failed to clear
global
dictionary on reset - Fixed
exists
function in conditional G-code - When retrieving file info, DCS returned the simulated time instead of the slicer time
- Fixed timing issue causing simulation times to be written incorrectly to G-code files
Compatible versions:
- RepRapFirmware 3.3-rc2
- DuetWebControl 3.3-rc2
New features:
- Added new
Disconnected
state to indicate when DSF/DWC is not connected to RRF - .deb packages can be installed over DWC if support for package management and root plugins is enabled (see plugins.json and config.json)
Changed behaviour:
- Only G0 and G1 are repeated for Fanuc-style G-code to follow RRF implementation
- M955 P-parameter is passed as a driver identifier like M569 P
- Added extra fallbacks for main firmware files (
directories.firmware
->0:/firmware
->0:/sys
)
Compatible versions:
- RepRapFirmware 3.3-rc1
- DuetWebControl 3.3-rc1
New features:
- Added support for abbreviated G-codes in CNC and Laser mode (Fanuc and LaserWeb G-code style)
- Added new code streaming mode to the API for easier Repetier and Octoprint integration
- Implemented new command line utility to test and demonstrate the new code stream mode
Bug fixes:
- Global variables in the OM were not cleared when DSF lost connection to RRF
- When prints were paused during macros, under special cirumstances the macro was run again on resume
Compatible files:
- RepRapFirmware 3.2.0-rc2
- DuetWebControl 3.2.0-rc2
Changed behaviour:
- Increased SPI connection timeout from 2.5s to 4s (same value as in RRF)
- Partial SPI transmissions may not take longer than 500ms (same value as in RRF)
Bug fixes:
- M997 and M999 could generate "Operation has been cancelled" errors
- When DCS terminated sockets of command connections were not correctly shut down
- Object model write locks were not correctly disposed of when DCS terminated
- Calling abort in macro files could cause an exception
- M501 could freeze if no config-override.g was found
- "Macro not found" warning messages were not output as part of code results
Compatible files:
- RepRapFirmware 3.2.0-rc1
- DuetWebControl 3.2.0-rc1
Changed behaviour:
- RRF downgrades from later protocol versions are now possible
- CORS headers are only sent if explictly configured by
M586 C
-parameter - SPI transfers use CRC32 instead of CRC16 with new protocol version
- DCS service notifies systemd when it is up and running
- DCS terminates when a firmware update of the main board is complete (unless
NoTerminateOnReset
is set) -
runonce.g
is no longer processed if DCS starts in update-only mode (i.e. with-u
parameter) - Third-party DSF plugins cannot be installed any more (TBD for v3.3)
Bug fixes:
- Fixed incompatibilities when updating RRF from older firmware versions
- LockMovementAndWaitForStandstill retransmissions were logged
- Expressions were not automatically evaluated in the code processors
- Internally processed codes were only logged if they resulted in a warning or error
- DWS didn't send correct
Cache-Control
header which could result in DuetPi using outdated DWC versions - Sometimes the filament mapping was not fully restored if the
NoTerminateOnReset
option was enabled - M929 was not fully implemented for new log levels