Z-probe commissioning problem
-
I've also homed the printer and slowly dropped the nozzle until it just touches the bed. The Z-height readings were:
Homed: 645.0
Touching bed: 212.5This is what I don't get. When you home a printer, it doesn't count how far it moved until it activates the endstop switches. It just moves until it hits them, backs off, moves slowly until it hits again and usually moves away 5mm or so. That is your homed height. The Duet then uses your H number from M665 to determine how far above the bed the nozzle is. How was yours showing 645 with 550 in the M665? Do you have a config-override.g file?
Yes, there is a config-override.g file with a warning not to edit it as it is machine generated.
With the deployprobe.g file as below, G30 seems to work (although it does leave the nozzle at -0.1)
[[language]] G1 X0 Y0 F25000 ; move to somewhere sensibleWithout that file, or with that line commented out, G30 does not work.
-
Do you have a config-override.g file?
Good point, that is always pain in the ass if you forget it
-
Can you paste what is in it?
-
Please show us your config-override.g
-
I've also homed the printer and slowly dropped the nozzle until it just touches the bed. The Z-height readings were:
Homed: 645.0
Touching bed: 212.5This is what I don't get. When you home a printer, it doesn't count how far it moved until it activates the endstop switches. It just moves until it hits them, backs off, moves slowly until it hits again and usually moves away 5mm or so. That is your homed height. The Duet then uses your H number from M665 to determine how far above the bed the nozzle is. How was yours showing 645 with 550 in the M665? Do you have a config-override.g file?
OK, just realised that was a typo - 645 should have been 445. I'm really sorry for the confusion!
-
No need to say sorry for anything. Still interessted in the override-settings….
-
Have you ran anything that required a M500 command like a hotend or heat bed calibration?
-
Have you ran anything that required a M500 command like a hotend or heat bed calibration?
Yes, I did that twice - for bed PID and hotend PID auto tune.
-
OK, just realised that was a typo - 645 should have been 445. I'm really sorry for the confusion!
But it still showed 212 touching the bed?
-
Please paste the content in.
-
The config-override.g file looks like this:
[[language]] ; This is a system-generated file - do not edit ; Delta parameters M665 R246.6 L440.0 B180 H433 M666 X0.000 Y0.000 Z0.000 A0.00 B0.00 ; Heater model parameters M307 H0 A645.6 C1147.3 D12.1 S1.00 B0 M307 H1 A533.4 C223.7 D3.0 S1.00 B0 M307 H2 A340.0 C140.0 D5.5 S1.00 B0 M307 H3 A340.0 C140.0 D5.5 S1.00 B0 M307 H4 A340.0 C140.0 D5.5 S1.00 B0 M307 H5 A340.0 C140.0 D5.5 S1.00 B0 M307 H6 A340.0 C140.0 D5.5 S1.00 B0 M307 H7 A340.0 C140.0 D5.5 S1.00 B0 ; Z probe parameters G31 T1 P100 X0.0 Y0.0 Z-0.10 G31 T3 P500 X0.0 Y0.0 Z0.70 G31 T4 P500 X0.0 Y0.0 Z0.00 -
I removed the bed to check on the fans in the control box. After re-installing,, the homed Z-height now reads 441.39 and it reads 9.39 when touching the bed.
-
Mhh, the override File looks okay to me.
-
It really has me confused!
Even more so - I've now deleted that deployprobe.g file and it now runs G30 OK!
Homed, Z-height is 441.39, touching bed it is 0 so that looks OK to me.The only thing still worrying me is that the G30 leaves the nozzle set at -0.1 - how do I change that so that it retracts and clears the bed afterwards?
-
The G30 is only going to probe once. That is all. G32 time.
-
Hooray! That seems to be working well now. Thank you so much!
-
What do you have in your bed.g file?
-
Bed.g
[[language]] ; Auto calibration routine for delta printers ; Before running this, you should have set up your zprobe Z offset to suit your build, in the G31 command in config.g. M561 ; clear any bed transform, otherwise homing may be at the wrong height G31 X0 Y0 ; don't want any probe offset for this G28 ; home the printer ;*** Remove the following line if your Z probe does not need to be deployed ;M98 Pdeployprobe.g ; deploy the mechanical Z probe ; The first time the mechanical probe is used after deployment, it gives slightly different results. ; So do an extra dummy probe here. The value stored gets overwritten later. You can remove this if you use an IR probe. ;G30 P0 X0 Y0 Z-99999 ; Probe the bed and do 6- or 7-factor auto calibration G30 P0 X-73.6 Y-42.5 Z-99999 ; X tower G30 P1 X0 Y-85 Z-99999 ; between X and Y towers G30 P2 X73.6 Y-42.5 Z-99999 ; Y tower G30 P3 X73.6 Y20 Z-99999 ; between Y and Z towers G30 P4 X0 Y67 Z-99999 ; Z tower G30 P5 X-73.6 Y20 Z-99999 ; between Z and X towers G30 P6 X-36.8 Y-21.25 Z-99999 ; half way to X tower G30 P7 X36.8 Y-21.25 Z-99999 ; half way to Y tower G30 P8 X0 Y42.5 Z-99999 ; half way to Z tower G30 P9 X0 Y0 Z-99999 S6 ; centre, and auto-calibrate 6 factors ;*** Remove the following line if your Z probe does not need to be retracted ;M98 Pretractprobe.g ; retract the mechanical Z probe G1 X0 Y0 Z150 F15000 ; get the head out of the way of the bed -
That should work just fine. Those are points for a 200mm bed though, If you ever want to probe further out, just add in more G30 P* lines.
You can now add a M557 R180 S20 (might need a larger S number with firmware 1.19) to the bottom of your config.g file and run a bed mesh calibration after your auto calibration to see a graphical view of your bed.
Edit: Maybe a smaller R number so you are not probing at the edge of the bed,
-
Also, M665 and M666 will show you the values that the auto calibration came up with after the probing. M500 will save them to your config-override.g file for you.
