RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released

dc42

On behalf of the Duet3D team I am pleased to announce the release of this new firmware/software bundle. This makes GCode meta commands available to Duet 3 + Raspberry Pi users, and fixes bugs that have been reported in the previous bundle (RRF 3.01-RC8, DWC 2.1.3, DSF 2.0.0).

Users of Duet 3 + Raspberry Pi can upgrade to this bundle from the unstable package feed using sudo apt-get update and sudo apt get upgrade as usual. All other Duet users can get it from https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC9.

RRF 3.01-RC9 release notes: https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md
DWC 2.1.4 release notes: https://github.com/chrishamm/DuetWebControl/blob/master/WHATS_NEW.md
DSF 2.1.0 release notes: https://github.com/chrishamm/DuetSoftwareFramework/blob/dev/WHATS_NEW.md

If you find any issues with this release, please start a new thread for each one.

A Former User

DSF 2.1.0 release notes: https://github.com/chrishamm/DuetSoftwareFramework/blob/dev/WHATS_NEW.md

ohlala! conditional g-code!

boldnuts

Look's like you have duplicated the same link for all other Duet users
and the release notes

dc42

@boldnuts said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

Look's like you have duplicated the same link for all other Duet users
and the release notes

Thanks, now fixed.

boldnuts

@dc42 Cheers

deckingman

@dc42 A couple of question regarding limitations with expansion boards https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations................

It used to be that M581 external triggers didn't work with expansion boards but it's not on the list of limitations, neither have I seen any reference to it being implemented in any release notes (unless I missed it). So is it now fixed or still a limitation which isn't documented as being such?
Likewise hiccups. IIRC they weren't reliably reported for expansion boards but I don't know if that is still the case or if it's another (undocumented) limitation.
Linked to 2 - I'd like to know what the maximum micro stepping value is that I can use with my mixing extruders but without a hiccup count, I can't evaluate. Alternatively, do we yet know what the maximum step pulse frequency is? If so, I could make calculate the maximum usable micro-stepping from that.

dc42

@deckingman said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

@dc42 A couple of question regarding limitations with expansion boards https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations................

It used to be that M581 external triggers didn't work with expansion boards but it's not on the list of limitations, neither have I seen any reference to it being implemented in any release notes (unless I missed it). So is it now fixed or still a limitation which isn't documented as being such?

That was fixed several RCs ago

Likewise hiccups. IIRC they weren't reliably reported for expansion boards but I don't know if that is still the case or if it's another (undocumented) limitation.

Still not passed back to the main board to allow it to resync, but has been reported by M122 B# for several versions.

Linked to 2 - I'd like to know what the maximum micro stepping value is that I can use with my mixing extruders but without a hiccup count, I can't evaluate. Alternatively, do we yet know what the maximum step pulse frequency is? If so, I could make calculate the maximum usable micro-stepping from that.

See answer to #2.

deckingman

@dc42 Thanks - must have missed that in the release notes somewhere.

Dr_Ju_Ju

Getting there, if I run my multi G32 macro from the PanelDue, I get the final 'run' output on the PanelDue, console window, but it is missing out the previous 6, and still no output in the DWC console window.

And I still can't Bed tune to 150 e.g.

21/04/2020, 14:47:25 M303 H0 P1 S150
Error: M303: heater 0 target temperature must be no hiher than the temperature limit for this heater (125.0C)

with my M143 setting way above the target (testing setup only)

; Bed
M308 S0 P"bedtemp" Y"thermistor" A"Bed" T105000 B4138 C0 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S180 ; set temperature limit for heater 0 to 180C
M307 H0 B1 ; enable bang-bang mode for the bed heater
M140 H0 ; map heated bed to heater 0
M144 S1 ; set bed 'Active'

dc42

@Dr_Ju_Ju said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

Getting there, if I run my multi G32 macro from the PanelDue, I get the final 'run' output on the PanelDue, console window, but it is missing out the previous 6, and still no output in the DWC console window.

Please explain what you mean: the previous 6 what? And start another thread for this issue, as I requested at the top of this thread.

And I still can't Bed tune to 150 e.g.

21/04/2020, 14:47:25 M303 H0 P1 S150
Error: M303: heater 0 target temperature must be no hiher than the temperature limit for this heater (125.0C)

Please send M143 H0 to confirm the M143 setting. I think you may need to move the M143 command to be later in config.g than the M140 command, because defining that heater as a bed heater sets the default temperature limit.

Dr_Ju_Ju

Thank you David, putting M143 after M140 sorted it, & I'll raise a new topic for the PanelDue G32 reporting issue.

c310

DWC bug: extrusion controls kept inactive (grayed out) even if i enable cold extrusion by M302 P1

chas2706

@c310 said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

DWC bug: extrusion controls kept inactive (grayed out) even if i enable cold extrusion by M302 P1

For me that is nothing new.

I got it and i'm on 3.01RC6:

dc42

@c310 said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

DWC bug: extrusion controls kept inactive (grayed out) even if i enable cold extrusion by M302 P1

Thanks, I can confirm that one.

chrishamm

@c310 Thanks for the report, I could reproduce it as well. As a work-around, you can send M302 S-273.15 R-273.15 and reload the web interface. We will fix this in the next firmware version.

dc42

@c310 said in RRF 3.01-RC9, DWC 2.1.4 and DSF 2.1.0 released:

DWC bug: extrusion controls kept inactive (grayed out) even if i enable cold extrusion by M302 P1

I've put new RRF firmware builds to correct this at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. Note, if you use these on a Duet WiFi, Ethernet or Maestro, then heater 0 is no longer a bed heater by default, so you may have to add a M140 command to config.g (after your M950 H0 command, but before your M143 H0 command if you have one). If you created the RRF3 config .g file using the online configurator then the M140 H0 command should already be present.

Danal

Feedback: The whole

apt update
apt upgrade

process is getting very smooth and nice. A very effective way to install everything.

arhi

RC9, largest print on duet2ethernet for me ever (not longest nor heaviest, just physically biggest, almost full volume of ender5, but only 3 shells, .35mm layer, 3% infill, .6mm nozzle) ~13 hours no issues. I guess positive feedback should exist too

ChrisP

As with previous recent versions, I'm still experiencing bugs with filament loading/unloading. Link to thread: Filament load/unload issue (RRF 3.01-RC9, DWC 2.1.4, DSF 2.1.0)

ChrisP

Having completed a few prints with the new updates I fairly confident that whatever was causing the mid-print hangs/pauses I was experiencing with the previous release now seems to have been fixed!