I'm happy to announce the first beta release of our new Input Shaping plugin!

This DWC plugin is essentially the successor of the old Accelerometer plugin and it lets you predict input shaper effects on-the-fly. It also allows you to record and evaluate motion profiles consisting of multiple accelerometer runs in order to find the best input shaper for your machine.

More detailed instructions about it can be found in our new docs and the plugin itself can be obtained from here (source code is available here). Note that software version 3.4.1 is required to use it.

Please bear in mind that this version is still a beta and some things will change again. For the next versions we have the following roadmap:

• Comparison of two different motion profiles
• Auto-tune functionality
• Display of shaper durations and possibly better highlighting of the effective vibration reduction
• Fine-tuning of custom input shapers (will depend on the next software version)

On behalf of the entire Duet3D team I am pleased to announce the releases of

• RepRapFirmware 3.1.1
• DuetWebControl 3.1.1
• DuetSoftwareFramwork 3.1.1

Starting from this release, we will maintain uniform version numbers for our software products in hope to simplify the upgrade process and compatibility overview. Before you go ahead and install the new versions, please read the upgrade notes for RepRapFirmware. Additional notes for DuetWebControl and DuetSoftwareFramework are available, too, but they are not as important as for RepRapFirmware. If you are upgrading from older firmware versions and ignore this, some things will NOT work! Besides, all our software and hardware files are now available on the same GitHub account.

Users of Duet 3 + Raspberry Pi may upgrade from the stable or unstable package feeds using sudo apt-get update and sudo apt get upgrade from a command-line terminal (via SSH or on the Pi itself). All other Duet users can get the required components from the links at the top (see also here). Apart from that, new DuetPi versions with v3.1.0 are now available (see here).

The new versions provide many bug fixes, various improvements, and conditional G-code. Now that the new object model has been declared stable, we will start documenting it as well. Until then, a preliminary auto-generated documentation can be found here.

If you have any questions or encounter problems, please look for a post in the forum categories for

• RepRapFirmware
• DuetWebControl
• DuetSoftwareFramework

and if you could not find one, please create it there and not here.

On behalf of the Duet3D team I am happy to announce the next pre-release v3.5 beta 2.
This release brings several new features and bug fixes since v3.5 beta 1 with the highlights being:

• Ability to reassign individual array elements using the set command
• New code editor in DWC including new G-code highlighting to support meta G-code expressions
• Improved support of custom array variables
• Several improvements for multiple motion systems
• MQTT publisher support on Duet 3 series WiFi enabled boards (M586 P4 and M586.4)
• Keepout zones (M599)
• Backlash compensation (M425)

Please do not forget to read the upgrade notes for

• RepRapFirmware
• DuetWebControl
• DuetSoftwareFramework

Starting from this release, DSF and DWC will use SemVer v2 for versioning.
This means if you are using MintyTrebor's ReleaseMgr plugin to track impacts on your configuration, you need to upgrade it as well.

In standalone mode, you can obtain the latest versions from here. Please check out to the docs if you want to try it out in SBC mode.

If you encounter any issues, please open a new thread with [3.5.0-b2] in the title and describe it there.

On behalf of the Duet3D team I am very pleased to announce the public release of software version 3.4.2. This version brings bug fixes and minor improvements since 3.4.2. Unless new problems arise that cannot wait, it will remain the last stable software release before we move on to the next beta of software version 3.5.

Highlights of this particular release are:

• Official support of Duet 3 mainboards as expansion boards (e.g. Duet 3 MB6HC driving another MB6HC)
• Better Python 3 plugin support (in SBC mode) and minor changes of the plugin manifest for our new plugin repository
• Several improvements for the Duet 3 MB 6XD
• General bug fixes

Users in standalone mode can obtain the update package as usual from GitHub. This time users in SBC mode must upgrade using sudo apt update / sudo apt dist-upgrade due to changed package dependencies. If apt upgrade is used, apt will keep back the DSF packages and neither DSF nor RRF will be upgraded as before.

Please consult the upgrade notes as well for

• RepRapFirmware
• DuetSoftwareFramework
• DuetWebControl

or use MintyTrebor's excellent UpgradeMgr plugin (also available from our plugin repostitory).

If you encounter a problem, please open a new thread with [3.4.2] in the title and report it.

I am happy to follow David's RepRapFirmware 2.02 release with a brand-new version of Duet Web Control that I rewrote from scratch using Vue.JS and the Vuetify framework. Please be aware that it is still brand-new and despite a lot of testing some things may not work as expected, but you can still revert to DWC1 if anything goes wrong. This can be achieved by clicking "Revert to Duet Web Control 1" on the Settings page.

In order to use this new web interface version, you must upgrade to David's latest RepRapFirmware version 2.02 first. After that the update package can be installed on the System page of DWC1 as usual. Once the update to DWC2 is complete, any following update can be installed by uploading files/ZIPs on the Files/System page. In the longterm this will be replaced by a dedicate (Auto-)Update page.

You can obtain the new DWC2 bundle is available here: https://github.com/chrishamm/DuetWebControl/releases/tag/2.0.0-RC3

This package will form the basis for a lot of the future development like 3D G-code visualising, better OEM customisations, generally improved UX and multi-machine support. I know a few things like full i18n support and more granular settings are still missing but it's been a whole lot of work to get it to this stage and I wanted to give you a first idea about the future of this UI. More ideas/wishes for DWC2 are best to be discussed in the DWC wishlist forum. i18n is partially done but I will need some more time to get everything ready just like for the documentation.

Please let me know what you think. Merry Christmas, everyone!

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.

Hi everyone,

I am pleased to announce a successor of the first RepRapFirmware configuration tool. It is basically a rewrite that takes advantage of modern web development techniques such as VueJS, Bootstrap-Vue and ES2015 features with better performance, safer code and reusable components. As before it is available here: https://configurator.reprapfirmware.org If anyone wants to have a look at the source code, feel free to check out https://github.com/chrishamm/configtool.

Apart from the new frameworks there is now a new steps/mm calculator for extruder drives. It opens up once you enter the corresponding steps/mm input fields. The calculator for thermistor parameters can be opened in the same way, i.e. by focusing one of the thermistor parameter input fields. Also, the support for BLTouch Z-probes has been vastly improved and several minor bugs have been fixed.

If you can, please give it a try and let me know if you experience any problems. This project helped me a lot to understand VueJS in depth, which I will use for a potential successor of DWC. I'll share my thoughts on this in another topic, though.

Thanks for your support!

On behalf of the Duet3D team I am pleased to announce the availability of the first release candidate for v3.5.0. There have been several improvements including certain input shaping enhancements. Please read the release notes for further information for:

• RepRapFirmware
• DuetWebControl
• DuetSoftwareFramework

There may be some more minor bug fixes before the final 3.5.0 release but we don't expect any major changes before then. If you are running a productive machine, please consider testing this version to avoid surprises when the next stable version 3.5.0 is out. Note that SCARA support has been withdrawn from the Duet 2 firmware build due to insufficient flash memory (see upgrade notes).

Users in SBC mode can update using the unstable or unstable-3.5 package feeds, users in standalone mode can obtain the upgrade files as usual from the GitHub pre-release.

If you encounter any issues, please open a new forum thread with [3.5.0-rc.1] in the title.

I'm pleased to announce the first availability of the new configtool beta. Until it is fully stable, it is available via https://configtool.reprapfirmware.org/next/.

Major improvements include:

• Rewritten base using plain Bootstrap 5.3, Vue 3, and TypeScript
• G-code preview per config section
• Greatly improved expansion board support
• Support for LED strips and accelerometers
• Optional dark theme

I expect there will be a few minor bugs but the overall package should be working. I hope we can replace the current (stable) configtool with this one when v3.5.0 is out.

If you give it a try, please leave some feedback here.

Edit: Updated to v3.5.0-beta.3.

I am pleased to announce the first availability of new DuetPi images based on the latest Debian Bookworm version for the Raspberry Pi. From now on we will provide 32-bit and 64-bit builds as well. These builds will replace the current but outdated Buster-based Raspberry Pi images when v3.5 stable is out.

Highlights of these new builds include:

• Support for Raspberry Pi 5
• New network subsystem (based on NetworkManager)
• Faster Wayland desktop backend
• Support for automatic DSF/RRF upgrades via M997 S2
• New approach for automatic USB mounts
• Automatic copying of config.g and other system directories on first boot

Please note that these builds are still somewhat experimental and they use the unstable package feed by default. If you wish to revert to the stable package feed, you can run M997 S2 F"stable" via DWC. Using v3.4 or older in combination with this image may work but it is not recommended due to missing support for NetworkManager and other Bookworm-related interfaces.

You can obtain the different DuetPi builds from here. I will host new images on GitHub when v3.5 is out and when I know the new builds are stable enough. Please see here for upgrade instructions if you are still running the last Buster-based DuetPi image and would like to upgrade.

If you encounter any problems, please report them here or in a new thread with [DuetPi Bookworm] in the title.

PS: Quite soon I will also publish a new DSF plugin which wraps the Spyglass webcam server to add support for the new Raspberry Pi camera models (libcamera).

@wschadow Thanks for reporting this. I've got a bug fix tested and working. Version 3.5 is not affected.

@Surgikill said in Filament change logic is not making sense.:

First, if I select the filament from DWC and click 'unload', it heats the bed and waits for the bed to reach temperature first. Is this intended? This is even before it executes M702. This seems counterintuitive. Is this being influenced by tool change macros? When I run T0, it puts the bed into standby mode. However, my toolchange macros don't call for that to happen.

That does not happen on my machine. When you unload a filament, the corresponding tool (T0) is selected beforfe M702 is called. If the tool has an active temperature set and if M116 is in your tpost0.g, RRF will wait for the active temperature to be reached before the filament change happens.

@Surgikill said in Filament change logic is not making sense.:

Also, when loading filament, it does not load the selected filament parameters before loading.

Are you missing M703 to execute the filament's config.g after M701? DWC calls that automatically after loading via M701. Note that M703 within the load.g macro of your filament has no effect. M703 should be called when the filament has been loaded, because the filament mapping is NOT updated before load.g finishes.

@Subractive Please post your full config.g here as well.

@droftarts No, that dialog is a DWC-only feature and it isn't coupled to any firmware mechanism.

@Surgikill You could write a DWC plugin which reacts to a specific global variable change and which displays a filament dialog whenever that variable changes. But of course that would require some coding skills, yet it should be technically possible.

@droftarts Not quite right, M701 is triggered by the "load filament" dialog when a filament is selected.

@Surgikill The dialog itself is a DWC-only feature. But you might be able to implement a work-around using a multiple choice M291 dialog (M291 S4). Otherwise you'd have to write a DWC plugin or fork DWC.

I'm happy to announce the availability of our next prerelease version 3.6.0-beta.2. Highlights of this version include bug fixes for the new input shaping implementation, a new WiFi server version which addresses potential connectivity issues, and various other improvements.

Please check the upgrade notes as always before upgrading or consider using ReleaseMgr to check for breaking changes. Release notes are available for:

• RepRapFirmware
• DuetWebControl
• DuetSoftwareFramework

The corresponding files for standalone mode are availalbe here. Users in SBC mode can upgrade using M997 S2 F"unstable" followed by M997 S2 (only supported with the Bookworm-based RPi image) or using the usual apt update/upgrade path.

If you encounter a problem, please open a new thread with [3.6.0-beta.2] in the title.

@Kiolia That's fixed then. DWC uses M106 Pnnn Snnn to set specific fan speeds. If you select the tool fan slider, DWC sends M106 Snnn instead.

@Kiolia I've identified and fixed a problem affecting the tools' heating rates which can occur when M106 Pnnn Snnn is used to update the current tool's fan value. It is no issue if only M106 Snnn is used.

If you need that in standalone mode, you may get away with daemon.g, a while loop, and a continuous echo command which keeps appending a line to an arbitrary file.

I'd rather use a plugin in SBC mode which subscribes to the main object model that is provided by DSF. The default interval of OM updates in SBC mode is already 250ms and it may be reduced further (e.g. to 100ms) in a future version. It's already possible to reduce the interval using the DCS settings file.

@fragrama17 I'm quite sure the minor number parameter was an sbyte in early DSF versions. I'll change the parser accordingly. Thanks for pointing this out.

Negative command portions should not be supported so I'll leave that exception there. RRF may be changed to throw an exception, too.