Z-probe commissioning problem
-
My best guess is that the output of the effector is not connected to the Z probe input pin. Make sure you have the Out and Mod pins of the effector connected to the correct pins on the Z probe connector, and test the cable with a multimeter in case you have a bad crimp connection.
-
Thanks, David, for picking up the diameter error - this is my first delta after a fair bit of experience with a cartesian and I'm finding it a steep learning curve.
Would the fact that the web interface is reporting 1000 when I tap the nozzle, or drop it carefully onto the bed, not mean that the cable is correct?
-
Sorry, I missed the firmware question - M115 reports FIRMWARE_NAME: RepRapFirmware for Duet WiFi FIRMWARE_VERSION: 1.19 ELECTRONICS: Duet WiFi 1.0 FIRMWARE_DATE: 2017-08-14
-
Do you have deployprobe.g and/or retractprobe.g Files in your /sys - Folder?
-
What does the web interface show for Z height when you have the nozzle just touching the bed?
Good call on the deploy and retract files too.
-
…
Good call on the deploy and retract files too.
Thanks, i've trapped into the same issue after i'v exchanged BLTouch against Davids IR-Probe
-
Do you have deployprobe.g and/or retractprobe.g Files in your /sys - Folder?
Yes, I had those - I guess from the default SD install. I renamed both with a 'old_' prefix but now when I do a G30 the printer seems to freeze and the web interface says 'Busy'
Should I have left them in place?
-
Did you check the Connections and proofed if you have bad crimped connections as David suggests?
-
Delete those folders.
-
Did you check the Connections and proofed if you have bad crimped connections as David suggests?
I checked them with a multimeter when I installed the cable - it was OK. I'll check again. Thanks.
-
-
Yes, the deploy and retract files. Delete them completely.
-
Yes, the deploy and retract files. Delete them completely.
OK, I've done that, they are deleted.
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.5And as it touched the bed the Z-probe field went pink and read 1,000 from the normal 0 for a split second.
Going to power it down and check the cable as suggested.
Thanks for the help, I appreciate it!
-
Change the H numbers in M665 to 433. That'll fix the issue.
-
Cable is good, no bad crimps and no crossed wires - they are in the same order on both ends.
-
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!
