New firmware 1.20 Release Candidate 2 - please try it!
-
I'm not sure what I'm doing wrong, but every time I update I break the wifi and have to go through a different procedure to get it reconnected.
Currently I can't reset the wifi module or anything through Pronterface. I think I need to upload directly to sd card then?
Is there a specific wifiserver version I need for RC2? I had 1.20a1 so updated to b10 for this thinking that's what I need.
-
Back online. I replaced the wifiserver file with one from a backup, M997 S1 then was able to get it online.
-
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
-
Starting with Beta11, with the M584 changes, with the U axis hidden if I run G29 the printer starts probing, but after the first row the U drive, which is my second Z motor starts moving up rather than down.
-
Not sure where to report DWC issues, so posting it here. Dark theme is broken in the latest 1.20-RC1 - it is visible immediately upon switching (and applying) the Dark theme. Some backgrounds remain white.
-
I'm not sure what I'm doing wrong, but every time I update I break the wifi and have to go through a different procedure to get it reconnected.
Currently I can't reset the wifi module or anything through Pronterface. I think I need to upload directly to sd card then?
Is there a specific wifiserver version I need for RC2? I had 1.20a1 so updated to b10 for this thinking that's what I need.
DuetWiFiserver 1.20beta10 is recommended for RC2. As explained in the upgrade notes, it often needs to be installed twice over earlier versions. Something to do with the bootloader and reserved flash areas having changed in the later version SDK I think.
-
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?
-
To those using the dark theme: It is now fixed in DWC 1.20-RC2, available here.
-
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. -
-
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 H5to 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.
-
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?
-
Installed on kossel XL, 9-hour lithophane print completed successfully.
-
I'm about to start a print but can already confirm that M28/M29 is working as expected again, thanks!
-
-
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.
-
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?
-
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.
-
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.
-
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