G29 Bed Probe consistently failing.
-
@Titus-A-Duxass if you used the duet2and3release.zip file, redownload the one off GitHub and use that, the issue has been fixed. It was just limited to the mini 5+ though
-
@jay_s_uk
Downloaded it again this morning.
Again I still have 3.4.4 on the expansion board.
And, yes I did a forced firmware update on the expansion board. -
@Titus-A-Duxass there was no update for the expansion boards so they will continue to show as 3.4.4
-
@jay_s_uk
What I am supposed to do here, I have one moderator telling me that the firmware is out of sync, and one telling that it is okay?The github firmware page suggests that I should downgrade.
-
@Titus-A-Duxass
Here is a, horrible, video of the printer carrying out a G32. You can see the Z drop at about 36 seconds, it's also quite clear the Z is not aligned. -
@Titus-A-Duxass said in G29 Bed Probe consistently failing.:
What I am supposed to do here, I have one moderator telling me that the firmware is out of sync, and one telling that it is okay?
From the github release page:
Important! There are no changes to firmware binaries for Duet 3 expansion boards, so they remain at version 3.4.4 in the Duet2and3Firmware-3.4.5.zip file in this releaseSo there is no 3.4.5 expansion board version.
@Titus-A-Duxass said in G29 Bed Probe consistently failing.:
The github firmware page suggests that I should downgrade.
It seems that this issue has been resolved DC42's comments in this thread: https://forum.duet3d.com/topic/30814/homing-issues-with-rrf-3-4-5-on-duet-3-mini/7
-
@gloomyandy
Thank you. So what firmware I have installed on the boards is correct.I'll have to track down the G32 issues but I am at a loss where to begin.
-
@Titus-A-Duxass I'd recommend you start by posting your current config.g file, your current bed.g file and the output produced when running G32.
-
@Titus-A-Duxass
I think this is where my problem is:
You must use the M671 command to define the X and Y coordinates of the leadscrews. The M671 command must come after the M584 command and must specify the same number of X and Y coordinates as the number of motors assigned to the Z axis in the M584 command; and these coordinates must be in the same order as the driver numbers of the associated motors in the M584 command. The M671 command must also come after any M667 or M669 command.I think the coordinates are not in the same order as the driver numbers of the motor.
This is my M584 X1.1 Y1.2 Z0.1:0.5:0.3:0.4 E1.0. -
@Titus-A-Duxass
Changing M584 to - M584 X1.1 Y1.2 Z0.1:0.5:0.3:0.4 E1.0. fixed it.
It still takes the long way round to get to each point but now the Z is levelled and does not drop.28.12.2022, 12:31:45 G32
Leadscrew adjustments made: -0.014 0.006 -0.009 0.012, points used 4, (mean, deviation) before (-0.001, 0.005) after (-0.000, 0.000)
28.12.2022, 12:31:06 G32
Leadscrew adjustments made: -0.048 0.003 0.011 0.048, points used 4, (mean, deviation) before (0.003, 0.020) after (0.000, 0.000)
28.12.2022, 12:30:31 G32
Leadscrew adjustments made: -0.573 0.103 -0.014 0.161, points used 4, (mean, deviation) before (-0.097, 0.157) after (0.000, 0.000)
28.12.2022, 12:29:50 G32
Leadscrew adjustments made: -1.588 -5.402 1.795 6.958, points used 4, (mean, deviation) before (0.757, 2.826) after (0.000, 0.000)Before the change it was constantly adding (Ca. 7mm)to the negative reading on the first lead screw.
