Changelog DSF 3.x RC

Version 3.3-rc3

Compatible versions:

• RepRapFirmware 3.3-rc3
• DuetWebControl 3.3-rc3

Bug fixes:

• M0 called stop.g instead of cancel.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

Version 3.3-rc2

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)

Version 3.3-rc1

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

Version 3.2-rc2

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

Version 3.2-rc1

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