I should add that this was never an issue before under RRF2. I don't know exactly when it got introduced.

It may depend on where the macro was originally launched. But maybe that's changed (or was never actually the case and I'm imagining)

@dc42, any thoughts on releasing RRF and DWF together as one update set with a single version?

This has been driving me crazy for months - can confirm console output is restored for G32 (and others for me) with with 2.1.1

Thank you.

@Haffwalker said in Webserver won't start:

How can I close the thread?

awesome!

no need to close, but you can mark it as solved.
https://forum.duet3d.com/topic/7773/forum-feature-mark-as-question-solved?_=1586512391010

It's definitely a learning curve. We're all here to help though, so feel free to ask away. We're also always trying to make it easier, which is tricky because it's a rather complicated endeavour to begin with. Persistence pays off though.

I just changed firmware to 3.0 and it works! I owe you all a pint of beer 🍻

Fantastic support, thanks!

Now let's see what else I can break 😆

@bearer said in Many disconnects - Duet Ethernet:

if you present a worse alternative

Better still, don't present it, when she says no cable simply start to carry the printer upstairs. When she SEES the alternative she'll insist you run the cable.

@Xavier works thanks!

@Phaedrux said in DWC Randomly terminate print at start:

Have you tried recently with DWC 2 and RRF 2.05?

I have not, but thanks for letting me know. I'll check it out at some point when I can afford some down-time 🙂

@dc42 Yes, in config.g I have G31 X0 Y0 for now.
I am working on the physical calibration of the printer at the moment and will add these in when complete.
Thanks

@Phaedrux , there he is:

M117 Preparing ;write Preparing G4 S2 ;delay 2 seconds M140 S60 ;set bed temperature and move on M141 S0 ;set heated chamber temperature and move on M104 T0 S195 ;wait for the extruder to reach desired temperature M107 ;start with the fan off G28 ;home all axes T0 ;select tool 0 G1 X-23 Y-24 F10000 ;go to the center of bed G1 Z10 F1000 ;E go to Z10 M107 P0 ;turn off leds G30 X-23 Y-24 S-2 H1.915 ;probe current position and ajust Z offset G1 Z40 F1000 ;E go to Z40 M106 P0 S1 ;turn on leds T0 ;reset current tool M584 P4 ;apply custom setting G1 X-137 Y160 F10000 ;go to X-137 Y160 M117 Spray print adhesive ;write Spray print adhesive G4 S2 ;delay 2 seconds M226 ;pause M190 S60 ;wait for the bed to reach desired temperature M109 S205 ;wait for the extruder to reach desired temperature G1 U130 F10000 ;go to U130 G92 E0 ;reset the extruder position G1 E25 F500 ; extrude 25mm of feed stock G92 E0 ;reset the extruder position G1 E-4 F5000 ;retract 4mm G1 X-187 F500 ;go to X-187 G1 Y165 F500 ;go to Y165 G10 ;retract G1 X-137 F500 ;go to X-137 and clean nozzle G1 XO Y0 U0 F10000 ;go to X0 Y0 U0 M584 P3 ;apply custom setting G21 ;metric values G90 ;absolute positioning M117 Print starting ;write Print starting G4 S2 ;delay 2 seconds G92 E0 ;reset the extruder position G1 E4 F500 ;unretract 4mm G11 ;unretract

I was considering doing operations using subprograms.
I have to find some time to write and try them.

@Phaedrux
3.0 (2020-01-03b3) and DWC 2.1.1 (though it was doing it before my recent DWC update)

@Jiter a fixed version of DWC has been released, 2.1.1, should resolve this, see https://forum.duet3d.com/topic/15342/duet-web-control-2-1-1-released

Ian

Oh okay, thank you! I'll wait for DSF 1.3

Quick glance and wild guess says 30-40% of the PRs get merged when looking at the github pages; so yeah I'd say if its usefull and follows the conventions you've got good odds for getting changes merged.

@HenryDara said in 2 bugs that need to be fixed:

Trying to understand what is what here.... 2.0.7 that came in the last release (3.01-RC5) is the same as 2.0.7 from before? (No change?)

Yes, that's right, it hasn't changed.

Should we expect anything to be fixed in the latest 2.0.7?

No, there's been no new release, or it would have a different version number.

Should we not expect fixes until 2.1.0 is released?

@chrishamm has said that these issues should be fixed in 2.1.0.

I have been hoping for this one to get fixed for a while...thanks

Me too!

Ian

@droftarts Hi Ian,

That is almost right. My probe is to the right of the nozzle but the bed would have to travel to Y29 before the probe would be over the bed.

@Shue M109 won't work with standby temperatures. It's better to use G10 to set the active and standby temperatures for each tool (you can put this in the slicer start code if you want), and send M116 after tool changes, which waits for all temperatures and other slowly-changing variables to arrive at their set values.

So you code would be something like this, which will turn on both tools, set T1 to be standby, T0 to active, then wait for temperatures to be reached:

G10 P0 S220 R165 ; Set tool 0 active and standby temperatures G10 P1 S220 R165 ; Set tool 1 active and standby temperatures T1 P0 ; Select tool 1 to turn it on but don't execute tool change scripts T0 ; Select tool 0 M116 ; Wait for all temperatures to be reached

This is usually at the beginning of the gcode, but you can do this when changing tool. At tool changes, you just want

T1 ; or T0, whichever tool change is next M116

Rather than setting this up in the slicer, you can also use the tpre[tool_number].g and tpost[tool_number].g scripts to handle how tool changes are managed. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Tool_change_files

Ian