Duet 3 Expansion 3HC sensorless homing via CAN

Cognirit

Good afternoon! I'm facing the same problem.

I am doing a scientific project, I am making a printer as a platform for researching and comparing different kinematic schemes. I expect to use up to 12 independent axes.

In this regard, I was really hoping for Sensorless homing to avoid drowning in wires. I didn't expect that an expansion board might not have full functionality. =/

And the Duet ecosystem is very much to my ideological liking in this respect.

And there is hardly any board for 12 motors

Is there any way to help the Duet project with this problem?

jay_s_uk

@Cognirit theres the fly-super8pro which can run RRF. That has 8 driver sockets and you can add another 3 using a BTT-EXP-MOT.
Or theres the Fly-ProX10, that has 10 driver sockets
That gets you to 10 or 11 where they can all do sensorless homing.

dc42

@Cognirit I can try to squeeze stall endstops for motors on expansion boards into the 3.6.0 release, but it won't make 3.6.0beta 2.

Cognirit

@dc42 thank you for reply! Am I correct that we would be best off waiting for this feature in 3.6.0beta3 or later? So as not to interfere with work on beta2?

dc42

@Cognirit yes, we intend to release beta2 as soon as we have fixed two bugs in beta1.

Cognirit

@dc42 Can you tell us if there is at least a rough prediction of when the update we need will be released at least in beta? We would love to take on testing it and actively share the results.

Cognirit

@dc42 Good day!

I noticed the release of beta3 in the project changelog.

Could you please let me know if the sensorless homing issue for the Duet3 Extension 3HC board is planned to be fixed in beta3?

Thank you!

tru_ann

@dc42 Good afternoon!
We join the question from Cognirit about issue solution in beta3. We also are very much looking forward to a soon release in which this problem will be fixed. Thanks!

gnydick

I didn't know this was a limitation of the expansion boards. I ignorantly went out and got the 3HC, converted my RailCore to AWD and sensing works. My 3HC is CAN ID 1 and I see messages in the console that tell me driver 1.0 or 1.1 stalled.

The issue I do face, please don't discuss here, I'll start a post and not steal this thread, is that the steppers become increasingly unsynced after homing each axis.

dc42

@tru_ann @Cognirit we've scheduled this feature to be included in 3.6 and I've started work on it. It may not be finished in time for 3.6 beta 3 but will be in 3.6 RC1.