@chrishamm Thanks for reply. I fully understand it's not going to be a priority, and mostly I should just be more careful, but I thought I'd log the request.

I'll look at the links, but I suspect it will be beyond me.

@chrishamm

Whoop whoop! 🕺

@droftarts thank-you, but ... it's a pretty obvious thing to include in the web control thing --- which is where I posted this.

@chrishamm Awesome to hear! 🙂

Please upvote the first post so hopefully this feature gets some traction

@axiom said in reduce the driving speed of the z-axis via the DWC:

how can I reduce the driving speed of the z-axis when controlled via the DWC without affecting the speed of other functions (e.g. homing).

Is there a reason why you want to reduce the speed of moving the axis below the maximum speed for that axis that you set in M203?

Thinking back a ways, I think I ran into this kind of error once or twice before but never chased it down to an unprintable character. I believe I ended up cutting out a section of code and re-typing it.
I have absolutely zero clue as to how the character in question managed to creep in. I am pretty sure that all my interaction with the code was through the DWC window.

@chrishamm ok, thanks, so I will stay at the current solutions for the moment, as Blazor is C# based.

@MintyTrebor thanks that's great, I'll have a look next time I fire up the printers.

Much appreciated 👍😎
Cheers
Barry M

@sindarius thank you

I want to bump up this thread, since I'm tinkering with a toolchanger and want to optimize print settings for different nozzle sizes.
I also saw that PrusaSlicer (and surely others too) changes extrusion width often.
It's mentioned as a comment in the gcode file.

;WIDTH:0.727092

Q: would it be possible to see the current extrusion width in the object model? Or extract it somehow?

Do you have an instance of DWC open in a browser? It's the browser doing the unzipping when a zip file is uploaded. The Duet itself doesn't have the resources.