New firmware 1.20 Release Candidate 2 - please try it!

[dc42]

@Jason:

having trouble with Wifi disconnects in RC2. I updated from an earlier beta where everything was fine. Cant seem to stay connected for more than 5 mins now. I just added a duex5 and rewired everything so there is a chance I tweaked something in the process but im pretty sure I had no issues after the rewire until RC2…. Anyone else? Is the last 19 beta living somewhere to roll back to?

anything I can do to help identify a bug in either the version or my own work? Im not super familiar with the debugging process but im pretty good at following directions.

Also the new web interface killed my dark theme. I had to roll that back to 19.3

Which version of DuetWiFiServer are you using?

[chrishamm]

To those using the dark theme: It is now fixed in DWC 1.20-RC2, available here.

[Immutef]

How do i wire / configure multiple bed heaters? Are the wiki docs updated to reflect the feature?
I'd like to revive my idea of a zoned heatbed with 4 heaters/thermistors for a larger printer tho.

[deckingman]

@chrishamm:

To those using the dark theme: It is now fixed in DWC 1.20-RC2, available here.

Thanks.

[chrishamm]

Please be aware that multiple bed heaters are not yet supported on DWC but in principle it is fairly easy to configure them. Assuming you want to map heaters 3-5 to heated beds leaving heater 0 as the first bed heater, you could send

M140 P1 H3
M140 P2 H4
M140 P3 H5

to the firmware to set everything up. Just make sure you don't put excessive load on the heater channels - in fact you may want to consider connecting an SSR to each of them before you continue.

[Immutef]

Thanks @chrishamm. I always forget the GCodes used are important whether a heater is a bed, hotend or chamber …

I explicitly use SSRs for my silicone heaters since I only use 230V/AC ones, so I won't do it any different in the future or with multiple heaters

So, in practice, I'd set all four heaters to my target temperature (e.g. 80°C) and the Duet takes care that each zone reaches 80°C and stays at it. I know the zones will affect each other, but in the end, the Duet will figure out which zone to heat, right?

[DjDemonD]

Installed on kossel XL, 9-hour lithophane print completed successfully.

[darookee]

I'm about to start a print but can already confirm that M28/M29 is working as expected again, thanks!

[dc42]

@DjDemonD:

Installed on kossel XL, 9-hour lithophane print completed successfully.

@darookee:

I'm about to start a print but can already confirm that M28/M29 is working as expected again, thanks!

Thanks for the confirmation, both of you.

[chrishamm]

@Immutef:

So, in practice, I'd set all four heaters to my target temperature (e.g. 80°C) and the Duet takes care that each zone reaches 80°C and stays at it. I know the zones will affect each other, but in the end, the Duet will figure out which zone to heat, right?

Yes, that is right.

[dc42]

@Immutef:

So, in practice, I'd set all four heaters to my target temperature (e.g. 80°C) and the Duet takes care that each zone reaches 80°C and stays at it. I know the zones will affect each other, but in the end, the Duet will figure out which zone to heat, right?

That's correct. Currently you will need to send M140 P0 S80, M140 P1 S80, M140 P2 S80 and M140 P3 S80. Then M116 to wait for them all to reach temperature. M140 with no P parameter defaults to P0.

I am considering making a couple of changes:

1. Use M140 H0:2:3:4 to configure multiple bed heaters, instead of M140 P0 H0, M140 P1 H3 etc.

2. Make M140 Sxxx (also M190) with no P parameter set the temperature of all bed heaters. So the bed temperature commands generated by slicers would apply to all bed heaters by default.

These changes would also apply to the M141 command to configure and control chamber heaters.

Thoughts?

[DjDemonD]

I don't have a multiple-zone bed, but that seems like a sounds scheme, if you don't specify then it applies to the entire bed, if you want to zone things off then you would expect to have to be more specific.

[Immutef]

@dc42:

@Immutef:

So, in practice, I'd set all four heaters to my target temperature (e.g. 80°C) and the Duet takes care that each zone reaches 80°C and stays at it. I know the zones will affect each other, but in the end, the Duet will figure out which zone to heat, right?

That's correct. Currently you will need to send M140 P0 S80, M140 P1 S80, M140 P2 S80 and M140 P3 S80. Then M116 to wait for them all to reach temperature. M140 with no P parameter defaults to P0.

I am considering making a couple of changes:

1. Use M140 H0:2:3:4 to configure multiple bed heaters, instead of M140 P0 H0, M140 P1 H3 etc.

2. Make M140 Sxxx (also M190) with no P parameter set the temperature of all bed heaters. So the bed temperature commands generated by slicers would apply to all bed heaters by default.

These changes would also apply to the M141 command to configure and control chamber heaters.

Thoughts?

Exactly what I thought of as a final solution. Sounds awesome. In the meantime, I have no problem to set each heater to temperature, since I use Macros on my Duet to control hotend/heatbed temperature (I have macros for each filament I use, with settings for retraction, pressure advance, etc …) so I don't have to bother with the Slicer settings/profiles (Simplify3D). Maybe the DWC could have a third filament macro type, like "print", beside the "load" and "unload"

Will it be possible to add an additional thermistor to that heater combination? E.g. have a fifth one sitting in the center of the bed? Since the silicone heaters may have a different temperature than the actual build platform itself, that'd be handy to have the possibility to add more thermistor than heaters.

[Jason K]

@dc42:

@Jason:

having trouble with Wifi disconnects in RC2. I updated from an earlier beta where everything was fine. Cant seem to stay connected for more than 5 mins now. I just added a duex5 and rewired everything so there is a chance I tweaked something in the process but im pretty sure I had no issues after the rewire until RC2…. Anyone else? Is the last 19 beta living somewhere to roll back to?

anything I can do to help identify a bug in either the version or my own work? Im not super familiar with the debugging process but im pretty good at following directions.

Also the new web interface killed my dark theme. I had to roll that back to 19.3

Which version of DuetWiFiServer are you using?

I was using 1.20beta11… Ill try beta10. I thought the update notes said to use beta11 when it was available

[SuperJETT]

I printed overnight with it on my corexy, no issues though I didn't have time to check the console this morning before leaving.

[frafa]

Hi David
1.20RC2 ok for me on Scara
Thanks !

[deckingman]

I wrote this post when testing RC1 with DWC 1.19.3 but then realised it might have been a slicer issue so changed the text to strike through. However, I am printing another set of parts which are sliced correctly and am having the same issue, so here is the post again:

I've just noticed something that may be a firmware issue but may be a DWC thing. I'm currently printing an object using all 5 extruders with a mixing ratio of 0.20:0.20:0.20:0.20:0.20 and notice that on the Print Status page of DWC, in the Machine Status panel top right, under Head Position I have Extruder Drives but it's only showing incrementing values for Drives 3 to 5 2 to 4 - Drives 1 and 2 0 and 1 are showing 0.0. (and yes, all 5 extruders are indeed moving and all at the same speed). To be clear, the values for drives 2 to 4 are increasing as the print progresses but drives 0 and 1 are stuck at zero.

I've no idea if this issue applies to other mixing ratios - it's not something I take much notice of. For the same reason, this issue could have been present for some time and not specifically related to 1.20RC1 release.

So the issue was first noticed using firmware 1.20RC1 and DWC 1.19.3 and persists using 1.20RC2 and DWC 1.20-RC2. But as stated above, the problem may well pre-date both of these and may have been present for some considerable time.

I can't see anything obviously amiss with the gcode file, all the commented stuff looks to be correct but if someone tells me what to look for, I'll check.

I'm only about 18% into this print but the estimations are 4 hrs for filament, 8 hrs for file and 15 hrs for layers and for this particular print, I'd say that's correct. By that I mean that the print time based on total filament usage is probably correct and is being based on all 5 extruders despite 0 and 1 showing zero in the display area.

One other teeny weeny thing in DWC. On the print status page, bottom right is "Extrusion factors" and they are all set to 100% but the lable for the top one (Extruder 0) is offset to the right whereas all the other labels are directly above the blue dot.

[paulowisk]

I am testing the gcode M81 S1 and found that the ATX shutdown is occurring at a temperature well below that programmed in the thermostatic fan.
For example, here I use the following fan:
M106 P0 L0.7 I0 F500 H1 T80
and the atx shutdown temperature is occurring at 44C.
Was this supposed to be happening?

ps. I'm using 1.20rc2 in a duet wifi.

[chrishamm]

@deckingman:

One other teeny weeny thing in DWC. On the print status page, bottom right is "Extrusion factors" and they are all set to 100% but the lable for the top one (Extruder 0) is offset to the right whereas all the other labels are directly above the blue dot.

Thanks for the hint, I'll fix that.

[dc42]

@paulowisk:

I am testing the gcode M81 S1 and found that the ATX shutdown is occurring at a temperature well below that programmed in the thermostatic fan.
For example, here I use the following fan:
M106 P0 L0.7 I0 F500 H1 T80
and the atx shutdown temperature is occurring at 44C.
Was this supposed to be happening?

ps. I'm using 1.20rc2 in a duet wifi.

I expect you have left Fan0 at its default setting of thermostatically controlled from heater 1 at temperature 45C.