G29 Bed Probe consistently failing.

Titus A Duxass

Greetings again.
More issues.
Voron 2.4 300

23.12.2022, 14:55:56 M115 b1
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4 (2022-10-14 11:45:56)
23.12.2022, 14:55:48 M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2022-11-30 19:35:23

Config.g

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Dec 18 2022 17:39:32 GMT+0100 (Mitteleuropäische Normalzeit)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"voron" ; set printer name
M669 K1 ; select CoreXY mode

; Wait a moment for the CAN expansion boards to start
G4 S2

; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M584 X1.1 Y1.2 Z0.1:0.5:0.3:0.4 E1.0 ; set drive mapping

M569 P1.1 S0 ; A motor goes forwards
M569 P1.2 S0 ; B motor goes forwards

M569 P0.1 S1 ; FL goes forwards
M569 P0.5 S0 ; RL goes backwards
M569 P0.3 S0 ; RR goes forwards
M569 P0.4 S1 ; FR goes backwards

M569 P1.0 S0 ; Extruder goes backwards

M350 Z16 I0 ; configure microstepping without interpolation
M350 X16 Y16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E436.54 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z4000.00 E250.00 ; set accelerations (mm/s^2)
M906 X1500 Y1500 Z1200 E400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S10 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X290 Y290 Z250 S0 ; set axis maxima

; Endstops
M574 X2 S1 P"^io1.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin ^io1.in
M574 Y2 S1 P"^io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ^io2.in

; Z-Probe
M558 P5 C"^io3.in" H5 F1200:120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y25 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X40:260 Y40:260 S20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Revo" D0 H1 F0:1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Miscellaneous
M501 ; load saved parameters from non-volatile memory
T0 ; select first tool

Bed.g

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Dec 18 2022 17:39:32 GMT+0100 (Mitteleuropäische Normalzeit)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

G29 runs okay until about X0 Y200, it then consistly returns G29 error - Probe already triggered before probing move started.

Can someone point me in the right direction, I've pasted my Config.g and bed.g.

Thanks
TAD

Titus A Duxass

@Titus-A-Duxass

Okay I have found the problem.
I have not aligned the gantry to the bed and on closer inspection the RL corner (and RR) is lower than the FR so the probe triggers but does not untrigger.

How do I calibrate/align the gantry to the bed?

Titus A Duxass

@Titus-A-Duxass
Further progress.
I manually align all corners with a ruler and both G29 and G32 completed successfully.

Titus A Duxass

@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

@Titus-A-Duxass
As an aside - I successfully carried out my first nozzle to bed grind (it was bound to happen).

Titus A Duxass

@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 XX

G1 F6000 X280 Y235 Z10
G30 P1 X20 Y260 Z-99999 ; Probe near corner XX

G1 F6000 X280 Y10 Z10
G30 P2 X280 Y260 Z-99999 ; Probe near corner XX

G1 F6000 X280 Y10 Z10
G30 P3 X280 Y35 Z-99999 S4; Probe near corner XX

Phaedrux

@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.

Titus A Duxass

@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

@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?

jay_s_uk

@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

Titus A Duxass

@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.

jay_s_uk

@Titus-A-Duxass there was no update for the expansion boards so they will continue to show as 3.4.4

Titus A Duxass

@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

@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.

YouTube Short

gloomyandy

@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 release

So 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

Titus A Duxass

@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.

gloomyandy

@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

@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

@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.