G29 Bed Probe consistently failing.
-
@Titus-A-Duxass
Further progress.
I manually align all corners with a ruler and both G29 and G32 completed successfully. -
@Titus-A-Duxass
I now need to do some reading on M671 - I think I need to enter the physical points where the bed attaches to the Z drives - but I do not understand why? -
@Titus-A-Duxass
As an aside - I successfully carried out my first nozzle to bed grind (it was bound to happen). -
@Titus-A-Duxass
Question:
Do the P0-P3 entries indicate corner positions or are they the motor designations?M671 S20
G1 F6000 X20 Y10 Z10
G30 P0 X20 Y35 Z-99999 ; Probe near corner XXG1 F6000 X280 Y235 Z10
G30 P1 X20 Y260 Z-99999 ; Probe near corner XXG1 F6000 X280 Y10 Z10
G30 P2 X280 Y260 Z-99999 ; Probe near corner XXG1 F6000 X280 Y10 Z10
G30 P3 X280 Y35 Z-99999 S4; Probe near corner XX -
@Titus-A-Duxass said in G29 Bed Probe consistently failing.:
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4
@Titus-A-Duxass said in G29 Bed Probe consistently failing.:
Duet 3 MB6HC FIRMWARE_VERSION: 3.4.5
Your firmware is out of sync as well. If you're running in standalone mode please try uploading the 3.4.5 zip file once more.
-
@Phaedrux
Then your statement in another thread confuses me - The firmware for expansion boards has not changed with 3.4.5, so the expansions reporting 3.4.4 still is correct in this case. -
@Titus-A-Duxass
I have been on the Github firmware page and have found this:Release 3.4.5 Latest
This is a bugfix release. For the list of bugs fixed, see https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-345.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 release
Important! Some users have experienced issues with the printer failing to complete homing in this release. This is under investigation; in the meantime please revert to version 3.4.4 if you experience this issue.
Although though my printer homes okay, there issue when I send it a G32. Will reverting to 3.4.4 help?
-
@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.
