Many thanks David, all working,
Mike

@r0n_dL:

Also making the assumption the more important mesh leveling using the stock probe and heatbed with the embedded 9 detection points are supported.

Yes you can define a probing mesh that lines up with the existing probe points if you need to probe at only those points. I guess the i3 has a bed with varying inductance so it might make sense to probe at only those points I suppose.

@iDevelo:

@Texzin:

The Folger Tech FT-5 has 2z , 2y, 1x. So if I just use the Duetwifi with out the Duex2/5 I will have to connect the Y steppers in series. Can I series the Y steppers without causing problems or should I add the Duex2/5?
Can the E1 be mapped to run second y steppers?

My config above is for a FT5 Z is on the Z port (both connectors).

Thanks

Yes, that works in recent firmware versions.

LJ12A3-4-Z/BX NPN wired
output to cathode, anode to E0 STP pin
ground to ground
power to vin
think i got a bat43 diode but might have been a 1N4148 cant remember right now what one radio shack had in stock at the time and its heat shrinked at the time

A flat piezo element used in the same manner as a foil strain gauge element certainly sounds lie it is worth trying. I would think that most places that you could put a single element on a PCB effector would have differing sensitivities in the X and Y planes but that would not be likely to have any effect on a straightforward Z probing operation. Thermal effects may be more of a problem but they can probably be worked around as they are with piezo diaphragms.

Another one that may be worth looking at are thickness mode piezo rings such as this one from Steiner and Martins https://www.steminc.com/en/piezo-ring-18x12x12mm-18-mhz-2-wl At $5 per ring they are a lot more than diaphragms but still not very pricey.

Mike.

p.s., I am the Mike that DjDemonD mentioned a few postings ago. I haven't yet got to 1 gram having hit the wall at 5 grams but will try again over the next few days.

Check out:

https://duet3d.com/wiki/Choosing_stepper_motors

The stepper motors used are always well below the VIN voltage 1.4V is fine. The stepper drivers limit the the current flowing through the motors.

If the height map is all red then that just means that the homed height is not exactly the 250mm that you quoted in the M208 Z parameter. If you want to see what the height map looks like, position the head over the center of the bed and probe there using a single G30 command, before you run G29.

@T3P3Tony:

While you can have up to 6 movement axis configured on the Duet they are synced together and all.run off the one gcode stream. So the two.machines could not run at once without some very crazy gcode hacking.

With remapping and custom configuration you could run two machines at different times. So you could have a duet with Duex5 wired to a delta and a Cartesian printer that has two seperate config.g files, remapped the axis as appropriate. You would then rename the config file you wanted to use to config.g and restart.

Saying that this is way more effort than it's worth.

OK, thanks 🙂

Chamber temperature is not implemented in Panel Due yet.

Adding the second 22K resistor in parallel with the first brought the voltage at the signal wire down to 2.97 volts. The probe is working fine.

tbh I think 16 with interpolation is an ideal setting

that's exactly what I did so that I can just hit the button on the web control rather than using the dropdown, you could of course add the M557 into bed.g and remove from config.g for convenience as well.

ok, Thanks!!!!

you might want to note that on the Gcode page(s) that's good to know!

~Russ

@T3P3Tony:

Hi, yes for some reason the auto subscribe to Individual threads you comment on it not working. For now you need to subscribe to a thread

Perhaps you may find a way to fix "auto subscribe" but at least, for now, there is a workaround.

Thanks much.

Frederick

I'll re-test it in firmware 1.18.1.

Andy - It was how I was doing it, but as I wrote earlier the issue is that the tool change scripts are executed and then the next movement command for the new tool, which inevitably is some distance away.

What I ended up doing was used "Z hop" in the slicer (0.2mm worked fine for me) which raised the ehozzle by just enough to clear everything whenever there is a travel move, and also happens on a tool change.

Edited to add that all movement in a G1 command is executed to synchronise over the move. If you want XY, then Z, use two G1 commands.

Sounds like you've blown the VSSA fuse.

https://duet3d.com/wiki/Connector_and_spare_part_numbers