Dual Y and Z steppers, etc - will this be doable in the future

fcwilt

Hi,

I posted an earlier question related to this but it was incomplete. Hopefully I've covered all the issues this time.

I am looking at a printer that would require 5 stepper motor drivers for the single X, dual Y and dual Z stepper motors AND 5 stepper motor drivers for the 5 extruder stepper motors.

It would seem that it will also need dual Y and dual Z end stop switches.

I look at the discussion on dual Z end stop switches but it seemed (I may be wrong) that it required a unused stepper motor output.

Any hope (now or in the future) of using a Duet setup on this printer?

Thanks much.

Frederick

dc42

Dual Z endstop switches require one driver per Z motor, instead of connecting the two Z motors in series drive from a single driver.

In a previous post I advised mapping the additional homing axes to an unused driver when not homing. But this is just a precaution against sending a G1 command with a U parameter, so it's not essential. If it helps, I'll allow a dummy driver number (e.g. -1) to be specified in the M584 command in future, for when you want to disable an axis.

Your total motor count is 10, which is the number supported by a Duet WiFi/Duet Ethernet + DueX5.

fcwilt

@dc42:

Dual Z endstop switches require one driver per Z motor, instead of connecting the two Z motors in series drive from a single driver.

In a previous post I advised mapping the additional homing axes to an unused driver when not homing. But this is just a precaution against sending a G1 command with a U parameter, so it's not essential. If it helps, I'll allow a dummy driver number (e.g. -1) to be specified in the M584 command in future, for when you want to disable an axis.

Your total motor count is 10, which is the number supported by a Duet WiFi/Duet Ethernet + DueX5.

Do you foresee a time when the firmware supports dual end stops in a straightforward manner that doesn't use the somewhat confusing (to me anyway) approach you listed in the other thread?

Thanks.

Frederick

dc42

Yes, however it's a low priority compared to other features that can't yet be configured in the existing firmware.

fcwilt

@dc42:

Yes, however it's a low priority compared to other features that can't yet be configured in the existing firmware.

That makes perfect sense. I will just have to study the current approach and see if I can wrap my head around it.

Thanks much.

Frederick