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.

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 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.

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!

@jay_s_uk I invoke a macro file check-filament.g from my start G-code to check the loaded filament (M98 P"check-filament.g" F"PLA" e.g.). It's simple as this:

if move.extruders[0].filament != param.F
  abort "Incorrect filament loaded!"

That will effectively abort the print if the wrong filament is loaded without running any pause/stop macros.

We have just released software version 3.2-RC2 which brings several bug fixes and minor improvements since RC1. RRF for standalone mode is available here, SBC users can install it as usual from the unstable package feed via sudo apt-get update and sudo apt-get upgrade.

Here the different upgrade notes and change overviews:

• RRF https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md
• DWC https://github.com/Duet3D/DuetWebControl/blob/v3.2-dev/WHATS_NEW.md
• DSF https://github.com/Duet3D/DuetSoftwareFramework/blob/v3.2-dev/WHATS_NEW.md

If you find any issues, please create a new thread with 3.2-RC2 in the title and describe your findings there. If everything goes well, we'll release this version as 3.2 stable.

As some of you may have noticed I did some moderation in this forum a few days ago and locked requests that are either duplicates, impossible to implement or those that have already been implemented. If you wish to have a certain feature added to the web interface, please vote for it in the corresponding thread.

If you think it was a wrong decision to lock a specific thread (e.g. because an important feature is still missing), please feel free to open a new one or contact me directly via PM. Please be aware that I locked those threads in order to clean up the list of requests and not to cause frustration among users.

As I expect to rewrite a main part of DWC in the near future I have not focused on better UI customisation yet but I am planning on improving this aspect greatly when I rewrite more of the underlying code.

To give you an idea what will be implemented soon, here a list of the features that I will focus on over the next weeks. I will implement point by point and update this thread after every update - you'll be able to check out the new features on my dev branch too (see https://github.com/chrishamm/DuetWebControl/tree/dev) :

• G-code input history (https://forum.duet3d.com/topic/1631/detailed-print-history)
• G-code visualiser (depending on whether I can get a good visualisation toolkit working in JS) (https://forum.duet3d.com/topic/141/gcode-visualizer)
• Different icons for the babystepping buttons (https://forum.duet3d.com/topic/3963/changeable-z-babystep-icons)
• Ability to change increments for all the movements buttons (https://forum.duet3d.com/topic/288/duet-web-control-change-wish-list/2)
• Better detection of emergency stops/firmware resets (https://forum.duet3d.com/topic/4054/automatic-reconnect-after-reset/4)
• Highlight currently active tool (https://forum.duet3d.com/topic/2204/more-prominent-way-of-showing-active-tool)
• Add S2 parameter to G1 movement codes (only as an option to be chosen in setup) (https://forum.duet3d.com/topic/4333/add-s2-parameter-to-head-movement-button-g1-actions)
• Parse last G29 code and determine if different heightmap file was specified (https://forum.duet3d.com/topic/5105/auto-display-saved-heightmap-file)
• Ability to change movement/feedrate button increments (https://forum.duet3d.com/topic/288/duet-web-control-change-wish-list/2)

I'm happy to announce the release of OpenAPI definition files for our HTTP APIs:

• for standalone mode
• for SBC mode

These files let you create web bindings for other programming languages (see https://editor.swagger.io/) or mock servers for testing (e.g. using Postman). Note there is already a class library for .NET, so there is no need to use WCF.

I plan to use the OpenAPI definition for standalone mode when we add support for the standalone HTTP API to DSF as part of v3.5.

I am happy to announce that the second release candidate of version 3.4.1 is now available. We hope this version will not need any further changes so we can publish it as 3.4.1 stable.
As usual this version is available from GitHub for users in standalone mode and users in SBC mode can update using the regular apt update/upgrade commands provided the unstable package feed is configured.

Here you can find the changes since 3.4.1-rc1 for

• RepRapFirmware
• DuetSoftwareFramework
• DuetWebControl

or use MintyTrebor's excellent ReleaseMgr plugin.
It also lets you check if an update affects your machine configuration in any way.

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

@jasper-k Upgrade RRF and DWC from 3.4.4 to 3.4.5. Where do you get the "Failed to get file list" error message? As soon as you upload a file on the corresponding page, the error message should be gone.

@ShaunCro Thanks for the idea, it will be implemented in 3.5-b2.

@MaxGyver Thanks, confirmed. I'll fix it in the next version.

@Diamondback I was generally referring to your "image" data but of course I don't know where else you reference it. The limiting factor is the maximum output size per (HTTP) request, the JSON response of rr_model?key=global exceeds the current maximum so only HTTP code 503 is returned.

@Diamondback You are using too many and/or too large global variables. Is there any reason you need to make all of them global, wouldn't it suffice to make some of them local using var?

I guess the only way to fix this from our side would be to make model queries of the global key sequential but we need to discuss again how this could be achieved.

@Lamooth You should upgrade to RRF/DWC 3.4.5 and DuetWiFiServer 1.27. Also check out the WiFi troubleshooting guide.

@reneb Downgrade instructions: https://docs.duet3d.com/en/User_manual/Machine_configuration/DSF_RPi#downgrade-packages
DSF HTTP API: https://github.com/Duet3D/DuetSoftwareFramework/wiki/REST-API-(v3.4.4-or-newer)

@reneb This is already fixed fixed in the upcoming 3.5-b2.

@xyzdims Did you see my OpenAPI definition? That should make it quite easy to wrap potentially missing HTTP calls as Python methods.

The rr_ API requires repeated queries within 8 seconds, else the active session times out.

For .NET there's already my DuetHttpClient library which supports both SBC and standalone mode and keeps the session(s) alive automatically.

@Stefanvh Thanks, this may be a duplicate of https://forum.duet3d.com/topic/31129/dwc-3-5-0-b1-button-speed-is-stuck-at-0-5mm-s/4 I'll have a look at it.

PS: Confirmed and fixed in the upcoming 3.5-b2.