Z-probe commissioning problem
-
Notes from the Wiki.
Version 1.19
Upgrade notes from version 1.18.2:
•Recommended DuetWebControl version is 1.19
•Recommended DuetWiFiServer version is 1.19
•Important! If you use an IR Z probe or some other type that does not need to be deployed, delete the files sys/deployprobe and sys/retractprobe.g if they exist, because they are now called automatically. You can do this in the System Files Editor of the web interface.You do need those two files removed, so your issue is somewhere else.
-
So, now when the nozzle is at the bed, the web interface reads 0 for Z height?
-
Notes from the Wiki.
Version 1.19
Upgrade notes from version 1.18.2:
•Recommended DuetWebControl version is 1.19
•Recommended DuetWiFiServer version is 1.19
•Important! If you use an IR Z probe or some other type that does not need to be deployed, delete the files sys/deployprobe and sys/retractprobe.g if they exist, because they are now called automatically. You can do this in the System Files Editor of the web interface.You do need those two files removed, so your issue is somewhere else.
If I remove deployprobe.g then I get the freezing issue. It contains the following:
[[language]] ; Probe deployment routine for Mini Kossel M564 S0 ; don't apply limits G1 X25 Y93 Z40 F10000 ; put probe arm next to belt G1 X-5 F500 ; move probe arm across belt G1 X12 F1000 ; move probe back G1 X0 Y0 F10000 ; move to somewhere sensible M564 S1 ; apply limits againWith that file in place, it seems to execute the commands, then probes the bed (green LED flash) and then stops with z=-0.1. Without that file it does none of those operations and enters a permanently busy state.
I will try and comment those lines out 1 by 1 to find which one is required to make G30 work.
-
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?
-
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!
