"Z probe already triggered at the start of the homing move."????
-
Crap! the return window is closed, so I will have to try and fix this tomorrow, or order another. Sheesh
-
Ok, so I ordered another BLTouch. It will be here Monday.
@Phaedrux: In the meantime, I know there no since trying to figure out what was going on now that I know there was a problem with the wires, but does the bed.g look ok?
-
The bed.g looks like it wouldn't have any problems, but there's only two commands in it. And G29 will automatically cancel any active bed compensation before running, so it's really only calling G32 to run G29. Might as well just call G29.
-
Maybe I should elaborate on how G29 can be used.
G32 used to be used to do a 5 point compensation routine that would generate a plane through 5 points you specified in bed.g. G29 has now taken over that roll, but it can do more than just 5 points. It's far more flexible. With G29 you specify a grid (with M557) and then a detailed network of points gets probed to allow for more fine grained adjustments.
You can still use G29 with a sparse grid of points to get the same effect as the old way if you know your bed is really flat already and want to probe it quickly before every print this is not a bad way to go.
However, if your bed isn't very flat but the platform itself is pretty stable, you can do a high detail G29 with lots of points and save that resulting heightmap and reload it before a print without needing to reprobe. Usually it would be loaded at startup in config.g or after homing, or right before printing.
Does that kind of make sense on your options for using G29?
Now that G29 is the recommended way of doing compensation, G32 and bed.g are usually used for printers with 2 or more independently Z axis lead screws so you can do automatic leveling.
-
Ok, I think I’ve got it. I am pretty confident that my bed is level: 0.25” tool and jig grade extruded aluminum. There will be a bed leveling need though. The rails that the x gantry ride on are out of parallel by a about 0.4 mm in 305mm and have not been able to get that fixed.
I will give this all a fresh start on Monday when the replacement probe arrives.
Thank again for all your help. Everyone!
-
If your printer has a Z endstop switch, you can home Z using that. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z.
-
@dc42 : yes it does have a z e/s. And I am using the same code as is in the link. That part is working fine. It’s just the bed leveling that I need to get ironed out. Thanks.
-
Ok, got the new BLT and tested all the wiring and all good. (the Z probe now shows 0 instead of 1000) I decided to try and do all the commands first from the DWC to see what happens, so I did the following....
homed all three axis
dropped the bed 50mm
entered these commands in the DWC...M557 X0:200 Y0:200 S50
M558 P9 X0 Y0 Z1 F500 T5000 H3
G30The bed immediately started rising, but the probe was not deployed. I was not sure if it would deploy once it got to the Z home, but decided I was not feeling real safe about what would happen next, so I stopped it.
Should G30 have automatically deployed the probe, waited until it returned to z home, or some other behaviour.
What should have happened with the commands above?
If these are not correct, can you offer any suggested changes? -
Yes G30 should deploy the probe. Do you have the deploy and retract servo commands entered into the deployprobe.g and retractprobe.g macros in the sys folder?
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
-
I've went back through this several times. I'm really stumped. When I first fire up the printer, the probe deploys and retracts twice and the Z probe is at 0, so I assume the probe is not defective.
I've looked at the deployprobe.g and retractprobe.g several times and everything looks as the setup directions say.
I've ran through the troubleshooting guild a couple times and I don't see any issues or potential issues related to that.
I ran the commission code to deploy but nothing seems to happen.
I checked that I am connected to the proper pins: 1:red, 2:brown and 8:orange Z probe in: white GND: black
I've added the following to config.g to no effect....
; BLTouch code
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000
G31 X30 Y15 Z3 P25@dc42 has said I don't need the |1
When I start the single probe, I get
M112
M999
Z-probe was not triggered dring probing moveI can't seem to get the probe to deploy by any method.
I am very sure I am doing something wrong, but can't figure out what.
-
So you're saying if you send M401 and M402 in the console nothing happens?
What commands are you using in deployprobe and retractprobe?
M307 H3 A-1 C-1 D-1means that you're trying to use heater pin 3 on the expansion connector. Is that correct? That would mean that your servo commands should use P3. -
@phaedrux That is correct. Nothing. Tried it several time after several restarts
-
Here is deployprobe.g
M280 P3 S10
and retractprobe.g
M280 P3 S90
-
Try adding
I1to those. -
Ok, is that a pipe or I
-
I tried
M280 P3 S10|1
no joy
-
it's the letter i, for invert.
M280 P3 S10 I1
M280 P3 S90 I1 -
When I ordered a replacement BLT because of the broken wire, I did not mount it on the printer, but rather just attached and tested the new wire on the old BLT. If I don't get anywhere today on this, I may try switching to the new probe as well. I hate doing that unless I am pretty sure thats where the fault lies
-
I'm quite sure that adding the inversion flag will solve your problem.
-
Oh wow!!!! It deloyed with M401 and retracted with M402. I tried the I1 and the |1 both and neither would work, but I was not putting a space before them because that is what I thought I saw elsewhere. At any event, it worked. Now I need to back and walk through the testing again.
