Z-probe commissioning problem
-
What type of motors, pulleys and belts are you running? Reason I ask is your M92 numbers are goofy.
-
What type of motors, pulleys and belts are you running? Reason I ask is your M92 numbers are goofy.
Motors are 17HM19-2004S, pulleys 16-tooth GT2, belt GT2
-
Thanks. You're ok then. Just looked off to me having only ran 20 toothed pulleys.
-
Since deleting those two files, issuing a G30 seems to put the printer into a 'frozen' Busy state and only a power reset or emergency stop seems to allow it to move again.
The status near to the Emergency Stop in the top right corner changes to Busy and nothing moves after that.
-
Thanks. You're ok then. Just looked off to me having only ran 20 toothed pulleys.
Phew, thank goodness for that! Thanks for checking and pointing it out anyway!
-
Have you changed the H number yet? Just wonder if it is freaking out because your homed height is greater than what your config is.
-
M665 R246.6 L440.0 B180 H443
Try this and see what happens.
-
Have you changed the H number yet? Just wonder if it is freaking out because your homed height is greater than what your config is.
Yes, if I manually lower the nozzle from homed position it stops at bed height so that seems OK.
-
M665 R246.6 L440.0 B180 H443
Try this and see what happens.
I have that already - after changing it earlier.
In an effort to fix the 'freezing' problem, I replaced deployprobe.g - it now reacts to the G30 command without freezing - but the original problem returns and it ignores a touch on the nozzle during the G30 operation.
-
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?
