Honestly, this is the easiest way to do it.

https://www.prusaprinters.org/color-print/

Upload your sliced gcode and tell it what layer you want to pause at. It adds the pause gcode. Then you can have a macro to unload and load your new filament and resume.

Many slicers have the ability to insert GCode at layer change.

@EasyTarget:

That looks really sweet!
Will it allow preview (eg if you have a print in simulation mode) ?

I'm in the habit (octoprint) of quickly sanity-checking the print (esp. base layers/support locations+types) before hitting the no-return button

Not currently, The simulate mode doesn't update the current layer info, I could calculate the layer using the z position. Is there a reason the simulation mode doesn't provide layer statistics?

@T3P3Tony:

Thats great!

Can you submit it as a pull request to the Github repository?

Will do when I'm done, Still a lot that needs to be added before it's on par with Octoprint

i will retry to build the .gz file…hope it works 🙂
Replaced [c]"\e129"[/c] with [c]"\e166"[/c]
Replaced [c]"\e130"[/c] with [c]"\e167"[/c]

Had not noticed the 'upload and print' button, will have a look 🙂
Have also been thinking that having an 'automatic simulation' option to get the accurate time estimate by default

@dc42:

Would someone like to specify exactly what preheat would do? Bearing in mind that we have single nozzle, single head dual nozzle, IDEX and mixing extruder configurations.

Step through the gcode file to find the first temperatures that are waited for and set them. Would likely need to go through the simulation routines to determine the active/standby temperatures needed for specific tools (and which tools are active) once any 'wait' type command is encountered.

In my opinion, it should stop at the FIRST command that causes a wait and preheat based on the values set at that point. So, if the gcode file sets only the bed temp and waits for it, then ONLY the bed temperature would be preheated. (In that case, it'd probably be a good idea to set tools to standby temps without waiting before waiting on the bed temp - this causing the tools to be preheated to standby at the same time as the bed is preheated.)

Here's some examples off the top of my head:

G10 (with R/S parameters) followed by M116
M104 followed by M116
M109
M140 followed byM116
M141 followed by M141
M190
M191

NOTE: preheated stuff will cause a bug to be hit that I've reported elsewhere concerning M116 commands being ignored.

I have just tried the same on mine and after a rest boot post Config.g upload mine also stays disconnected

Currently on 1.21RC1 for FW and WiFi Server and 1.20 for DWC.

HTH

@dintid:

@JohnOCFII:

@burtoogle:

Settings -> Machine Control -> Half Z Movements

The state of this is probably stored in the browser, not the Duet.

That was it! Thanks.

In this day and age when it is common (for me anyway) to interact with two to three web browsers on multiple devices (laptop, tablet, phone), even across the duration of a single print, I wonder if this information could be saved and loaded from the Duet itself. It feels like DWC was not designed with the multiple simultaneous browser environment in mind.

John

Correct, it is only designed for 1 consecutive connection at a time. It’s so fast that it’s normally irrelevant, but it does raise questions like these.
If everything were set on Duet you wouldn’t be able to do custom things or client basis, so guess it’s a trade off as always ?

It would be possible by adding a username to the initial login.
Then the settings could be saved on a per user basis.

If your Titan skips steps you need to feed it more current. If that doesn’t solve it, you should be looking at a new motor.

I run it at the highest speed when loading and unloading filaments and at 5 when just extruding the first 100mm to or so.

Used Titan just to be clear.

I would like customizeable steps though. Same as the option to add the drop down temperatures for the heaters.

Thanks, anyway to fail the start of the upload if the name is too long? The first time the upload success msg stayed and the error message flashed by and then the file wasn't shown on site. I had to do it 2 other times, once to read the message, and the next to capture the msg.

Both of these ideas get my vote.

If someone can provide sample GCode files and config.g to demonstrate the problem within the next few hours, I can try to get a fix done in release 1.20.1. Otherwise a fix will have to wait until the next major release, which is many weeks away.

I've moved this thread to the DWC Wishlist section of the forum.

Quite so - and tablets too.

I just tried that while not printing and you are right. But it also looks like the pinning does not work (anymore, or just not while idle) 😐

With most web browsers, (though, not on an iphone IIRC), you can remove elements of a website yourself. In chrome, you can do this by right-clicking on an object and selecting "inspect element."

You can then right click on the highlighted line of HTML, and select "hide element." And the object will disappear until you reload the page (or unhide the element).

Yeah confirmed fixed

Please submit any GCode files that give rise to an incorrect indication of the number of layers.

You can find the latest uploaded file but sorting by date in the gui