When G29 is run the heightmap.csv file is displayed at the end on DWC, a really nice feature.
However when e.g. 'G29 S0 P"anotherFile.csv"' is run, the file displayed is still heightmap.csv. It would be nice if DWC could detect this situation and display the written file at the end of the G29 run.
(I know anotherFile.csv can be displayed by going to the 'Settings' tab)

@phaedrux said in Help with Optical endstop.:

It's wired to the Z endstop connection, and the light on both the endstop and the Duet register that the beam as been broken, but when I do a G1 S1 move towards Z max and break the beam by hand, the bed does not stop.

So it sounds like it is wired to the Duet correctly, track through to DWC following the page David linked to ensure that it is seen there and reads the way you expect.

On my optical switch the light is on when the beam is not broken and off when it is broken, that seems like active (beam broken) low? Nonetheless in that case your G1 S1 move should stop immediately?

As you say you are "hitting the melting limit for the hotends" that sounds like you've done the temperature-filament calibration work (e.g. described in step 9 of this post - poorly written but useful math) and know some maximum speed you can accurately lay down a commanded volume of melted plastic with your current setup before the extruder starts missing steps or grinding. If not, this procedure will help you to know the answer for your system without spending any money.

Pushing melted filament out is the rate limiting part of how fast you can print, the rest of the story is all about smoothly and accurately positioning the melted plastic without motion artifacts (quality).

The Volcano's longer melt path will reduce the backpressure by melting the filament faster so the Titan can push more through without skipping steps, until you reach the speed limit for your Titan stepper motor and electronics (24V faster than 12V). If you search around the E3D website, Sanjay has some comments about not being able to use small nozzles with the Volcano because the flow rate is still slower and the plastic gets overcooked (look for "why not always use Volcano") so there are trade-offs.

Sounds like the Bondtech or other dual drive extruder may be able to force more through a given hotend as well. Depending on the failure mode (skipping steps or grinding) this may help (Deckingman has some interesting comments on the Bondtech in this blog post).

If you are staying with the 0.2mm layer height then the 0.5mm nozzle will only lay down a wider strip of plastic. This will give you thicker/stronger walls, but does not seem like this part will necessarily speed things up - though depending on the part design and slicer settings there will of course be cases where that added 0.1mm will help.

It would be nice if there was an audio indicator of reaching temperature, probably configurable so one could differentiate which extruder or bed.

This was asked before in 2016. It still seems like a good idea, especially now I have a PanelDue. By default I want the heating to run without waiting, so I don't think the macro suggested in that thread will work.

Yes it is a total bell-and-whistle featurette, and many who prefer silence (usually including me) won't want it so it would need to be optional. Nonetheless I believe these little bits of polish really grow on people and make the system stand out.

I think this is somehow a weakness of the cartesian / 'i3' design. I go back to fighting it now and then, but don't see it on my delta or the one print I've done on my new-to-me corexy.

I'm the one who got @deckingman's wet PETG, I've actually used it all up now (thanks again!), and used it to drive development of my vacuum filament dryer.
Here's the writeup

gnydick believes the time to finish estimation based on filament usage became less accurate after a recent firmware update.

msbailly thinks that the filament usage counter employed for that estimate is off because it counts retractions but not the return from retraction.

I think prints take a long time anyway and I just check back later.

Thanks David for all your work.

@dc42 Thanks, sent email to sales@duet3d.com

@dc42 Hi, is this offer still open? We were evacuated and now in an airbnb in Berkhamsted so can receive private courier or other options.

@dc42 I was thinking that too!
I see I can't just queue the order so will just wait.
Thanks though!

Thanks that is a great offer
Just put the order through, or do you have another plan?

UK BFPO address.

I'm thinking of just queuing an order and letting it come when it does.

Stay home and stay safe.

Sigh, 17 March and I just missed Duet3D closing the shop.

Any other UK source for the set of 6 Haydn Huntley magballs?

Thanks

@Phaedrux Thanks, I started from those entries, but see I missed in particular that M593 F0 will disable as I was looking for.

To be clear on M569, written under the Hnn parameter it looks like just sending M569 Pn with no parameters will report the defaults -- will try that out tomorrow.

@bot wow, that is an interesting idea. Thank you, I will have to think about that.

@dc42 my interest is in multiple material printing. Is it reasonable to assume that IR sensors would probably be better than a mechanical switch, or not really clear cut?

I'm thinking about converting one pf my printers to be IDEX - independent extruders both on the X axis. I have a Duet2 WiFi and a DueX5 running this machine.

Seems clear there is only one Z-probe connector to use on the Duet2 WiFi, which I currently have connected to a Duet mini IR sensor. Looking at M558 P options, seems like my only other choice is a simple switch?

Would be very grateful if someone who has looked at this could give an overview of ways I might proceed to have a Z-probe on each extruder carriage? Or maybe explain that this is not really workable for some reason I have overlooked? Seems like I can do the hardware part of this on a Duet3 with more probes added on the bus, but would prefer not to replace my existing hardware.

Thanks!

I'm interested in having a play with M569 and M593 (step pulse timing and DAA). For M593 I see that DAA is disabled by default.

So, I can run through a range of values for M593, but how can I reset it to disabled?

For the various M569 options, how can I determine the starting points if I want to test deviations +/-?

In gcode, I assume that I can reset the hardware but I want to do this e.g. while printing a tower.

Thanks!