Software bundle 3.4.0-b5 released

[chrishamm]

On behalf of the Duet3D team I am happy to announce the release of the software bundle v3.4.0-b5.

This release features many bug fixes for closed-loop support (EXP1HCL) and SBC mode. As usual you can find the new firmware builds for standalone mode here, users of SBC mode can upgrade using the usual sudo apt update/sudo apt upgrade method (see also here and here for details how to upgrade from the default stable package feed).

Release notes for the different software projects can be found here:

• RepRapFirmware: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-340beta5
• DuetWebControl: https://github.com/Duet3D/DuetWebControl/wiki/Changelog-DWC-3.x#version-34-b5
• DuetSoftwareFramework: https://github.com/Duet3D/DuetSoftwareFramework/wiki/Changelog-DSF-3.x#version-34-b5

For interested .NET devs there is now a new NuGet package to control Duets either in standalone or SBC mode remotely over the HTTP interface.

Please note that the interactive update prompt in SBC mode may complete quicker than you may expect when upgrading from an older version. The underlying bug has been fixed in b5 and will not occur again in the future. However, after a few minutes all expansion boards should have pulled their latest version automatically from the SBC.

If you find any problems, please create a new thread with [3.4-b5] in the title.

[zapta]

@chrishamm, what is the process to upgrade from 3.3 on a Mini5+?

Documentation says

"Updating from RRF 3.x to a newer version
If you are updating from an earlier version of RRF 3.x, you should be able to update by downloading the Duet2and3Firmware-3.x.zip file (where 3.x is the version number)."

but I don't see a similar file at https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.0beta5

[jay_s_uk]

@zapta they only release the combined zip file for stable releases. Otherwise it's download the appropriate upgrade file for your board

[PetrKroupa]

@chrishamm - Does this release solve the pause / resume problem? The changelog does not say anything ....

I'll try to test it tomorrow.

[chrishamm]

@petrkroupa Yes, it does. The DSF changelog says

- Pausing job files was not working if RRF reported no file position

[PetrKroupa]

@chrishamm - OK, I'm sorry, I overlooked it.
Thanks

[zapta]

Thanks @jay_s_uk. What is the process to update mini5 from 3.3 to this beta? Is it explained somewhere?

[jay_s_uk]

@zapta are you in standalone mode or SBC?

[CNCModeller]

@chrishamm
Thanks for the firmware update.

For information as per the last b4 update I had to use a USB connection and double tap the board's reset to upload the firmware directly to my D3 Mini's bootloader area. Uploading via DWC didn't work. I also tried forcing the update with the relevant M gcode command.

I'm wondering if I ought to create a clean build of my SD card in case something has got corrupted?

All the best
Barry M

[droftarts]

@zapta as @jay_s_uk said, download the appropriate upgrade files for your board. In your case, assuming standalone, download Duet3Firmware_Mini5plus.uf2 and DuetWebControl-SD.zip then upload in DWC. DWC should prompt you to install them.

If you're using an SBC, you need to be on the unstable package feed, see https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation

Ian

[zapta]

Thanks @droftarts , yes, standalone. I will give it a try.

The official firmware upgrade documentation mentions .uf2 only in the context USB based update.

https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

[Stephen6309]

@chrishamm 6HC & 1LC with PI4. Using Putty. It got stuck on updating mainboard firmware from beta4. Diag led on, no flashing. After waiting several minutes, I reset the board, diag led started flashing. No response from printer, then I shutdown the printer, fired it back up and beta5 was installed and diag led was flashing. Then I did an emergency stop to get the 1LC working.

[oozeBot]

As of 3.4.0-b5, "M0 Hnnn" is still turning off the heaters.

[T3P3Tony]

@oozebot from 3.4 onwards the "H" flag is not longer used. However an empty (but present) stop.g file should mean no action is taken when stop.g is called. This allows for more nuance in which heaters are left on or switched off based on what you have in stop.g

That said I have just confirmed that an empty stop.g does not prevent the heaters for being turned off so this still needs to be resolved.

[oozeBot]

We are still experiencing random chamber heater faults on 3.4.0-b5 when heating from room temp. I don't think we can tweak our M307 further.. We never saw this prior to the 3.4 betas.

Error: Heater 2 fault: temperature rising much more slowly than the expected -0.0°C/sec

[dc42]

@oozebot is there much noise on the temperature reading? What temperature sensor are you using? From the message it appears that RRF is recording a temperature drop.

[oozeBot]

@dc42 The chamber heaters do bounce around when heating up initially from room temp. To compensate, we've dialed our M307 back to next to nothing. As for the the probe, it's just a run-of-the-mill B3950 thermistor.

M307 H2 B1 C1800 D350 R0.02

The temperature can and does swing negative while initially heating. Some of these faults may be due to momentarily opening the doors to the chamber while heating, but more often than not, the faults occur when the printers have not been touched (and the doors are closed).

We understand the importance of faulting a heater when it's too slow to rise (ex: leaving the doors open), but really would like to see the parameters relaxed while initially heating.. unless there is something more that you can suggest with our M307?