Duet 3 Expansion 3HC sensorless homing via CAN
-
@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! -
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 Great to hear that! Thank you!
-
@Cognirit this has been implemented in 3.6 beta3:
https://forum.duet3d.com/topic/37289/software-version-3-6-0-beta-3-now-available
-
@T3P3Tony Thank you for writing! @dc42
I can't properly convey how glad I am that I came across your developments and Duet2 about 7 years ago - and I still use them primarily in projects and research.
In my opinion it is currently the most flexible and user-friendly system for enthusiasts who are trying to create something new in the world of CNC machines.
Thank you and your team for all the work and effort you've put into this ecosystem and I hope it thrives for a long time to come!
-
@Cognirit thanks for the kind words!
-
-
@dc42 @T3P3Tony Hello! We installed firmware 3.6 beta3 and tested sensorless homing on the Duet3 3HC board. Individually all Z-axes perform homing without problems. However, when we tried to run homing with independent stopping (M574 Z2 S4) the system worked the same way as with S3 mode: when the first axis reached the end, all axes stopped. We tried running homing with the same settings, connecting the motors to the Duet3 6HC main board and it worked as it should: each motor stopped at the correct time. Is it possible that this is another unresolved problem with the Duet3HC Expansion board? I am attaching our configuration files. Thanks!
homez.g
config.g -
@tru_ann thanks for testing and reporting this, we will investigate further