New stable software version 3.5.0 now available

[chrishamm]

On behalf of the Duet3D team I am very pleased to announce the availability of stable version 3.5.0. Highlights of this release include:

• Support for multiple motion systems and our new scanning Z-probe
• Input shaping support on axes driven by CAN-connected expansion boards
• New WiFi firmware version 2.1 featuring (partial) WPA enterprise support
• Modern code editor in DWC based on the VSCode editor (Monaco)
• Transition of DWC code files from JavaScript to TypeScript and upgrade from Webpack 4 to 5
• Input Shaping plugin now integrated in DWC
• New DSF HTTP compatibility layer for RepRapFirmware rr_ HTTP requests
• DSF suppot for new Debian Bookworm images (for new DuetPi images)
• New ConfigTool with many more improvements

As with every stable release, we highly recommend reading the upgrade notes or using the ReleaseMgr plugin in order to avoid upgrade issues for:

• RepRapFirmware
• DuetWebControl
• DuetSoftwareFramework

Users in standalone mode can obtain the upgrade bundle here.

New stable DuetPi images based on the latest Raspberry Pi OS (Debian Bookworm) including upgrade instructions are now available here. Users in SBC mode should consider upgrading to that DuetPi version because the current version will reach its EOL soon (Debian Buster's EOL is scheduled for June 30th, 2024). If you're in SBC mode and don't want to upgrade, you can update the packages as always using the regular apt update/upgrade method. This upgrade method will be surperseded by M997 S2 in the new image to simplify the update process.

If you see "Incompatible Software Versions" in your browser upon first launch, press Ctrl+Shift+R to reload the cached version in your browser. In case you encounter other problems, please open a new thread with [3.5.0] in the title.

[dc42]

If you are a Duet 3 user planning to upgrade to this release, please heed the following upgrade note:

• Very important! If you use a M400 command in your deployprobe.g or retractprobe.g file (or the corresponding files with the probe number added e.g. deployprobe0.g) or in any macro files that are called by those files, and your main board supports multiple motion systems (e.g. any Duet 3 main board), you must add parameter S1 to that command. Failure to do so is likely to result in head movement outside the configured M208 limits.

Adding the S1 parameter to M400 commands has no effect if you are running older firmware versions, so you won't need to remove it if you subsequently revert to an earlier firmware version.

[gtrider]

@dc42 Wish I had read this before I upgraded. Luckily I can flip the flex PEI sheet over and use the other side. I keep telling myself to wait a few weeks before updating.

[dc42]

We have decided to withdraw the Duet 3 main board firmware binaries from this release, because of the unexpected and potentially damaging side-effects when M400 is used in a deployprobe.g or retractprobe.g file. We expect to release 3.5.1 in the very near future.

[dc42]

We are in the process of releasing software 3.5.1 which has a fix for this issue. The standalone files have already been released and the package server is in the process of being updated. We'll make an announcement when the release is complete.