BLTouch working
-
I posted my Endstop section of my config.g two post ahead. I am using M558 P5
-
Please check that you don't have another M558 command later in config.g or in config-override.g. A reading other than 0 or 1000 with M558 P5 doesn't make sense, unless there are continuous pulses on the Z probe input pin.
You can run M558 with no parameters to check which mode the Z probe is in.
-
You might have the same issue that I had…
Instead of M558 P5 X0 Y0 Z1 H5 F100 T2000, try M558 P1 X0 Y0 Z1.5 H5 F100 T2000
Instead of G31 X0 Y0 Z0 P25, try G31 X0 Y0 Z0 P200
I do not know with the 1.20 version but for me (I had RepRapFirmware 1.19.2 at the time), M401 & M402 had to be replaced by M98 Pdeployprobe.g (M280 P3 S10 I1)& M98 Pretractprobe.g (M280 P3 S90 I1).I hope that it helps
-
I found my issue. After looking back at the code in config.g, I somehow uncommented the second M558 line. Placed a colon in front of that and it corrected the problem.
Thanks for the help though.
-
I'm using original Bltouch Smart. Connected it almost like duet3d wiki says, but instead of first 5v pin I've connected it to second 3.3v pin because I set bltouch to use 3.3v logic. Works like a charm.
Besides I've tried to use it half a year ago with MKS SBASE board (3.3 logic), but it was constantly stuck in error mode. I could reset it and move pin, sometimes I could even make a bed leveling. -
I'm using original Bltouch Smart. Connected it almost like duet3d wiki says, but instead of first 5v pin I've connected it to second 3.3v pin because I set bltouch to use 3.3v logic. Works like a charm.
I thought that the bltouch smart still needs 5v for the power… the trace is just for the LOGIC side. So, the red wire always needs 5v (regardless of if the trace is cut or not) and cutting the trace only impacts the logic signals.
(source: https://docs.wixstatic.com/ugd/f5a1c8_6f2b1ea5daf74a3c85967f2be7848cf0.pdf))
Of course, if it's working for you, then I guess it works for you.
I'm reading up on this thread as I've just ordered a BLTouch. At least to start, I'm hoping it makes manual bed levelling a bit easier. As my printer ages, and my X axis rods slowly deform, I'm also hoping the mesh compensation thing helps out.
Take care
Gary -
Okay, so I've read through most a lot of this post and am not much the wiser how best to setup a bltouch smart device on duetwifi. I was given one to test, and I'm curious about it.
Is anyone here using one currently on 1.21 firmware and able to state how they have it connected and configured (happy for it to be brief and technical)?
Since it seems to be a big pain in the butt, I'd gladly offer a discount code on a piezo probe (or any of our other stuff) to anyone who can simplify this for me…
Is the info in the new wiki correct?
-
As in the wiki. Here's a photo of how I connected it for testing firmware 1.21RC2.
-
Thanks David, very helpful.
Installed as per wiki instructions (and your photo - might be worth adding that to the wiki, more pictures to follow is something people have been asking for - don't know if other versions have different wiring etc.).
Remember those following this to comment out any M307 commands in config_override.g which relate to heater 3 (H3) as this was preventing the servo from operating.
I have done some systematic (and fair) testing of the BLtouch which I will report on over in reprap forum http://forums.reprap.org/read.php?1,767998,811976,page=39
-
might be worth adding that to the wiki, more pictures to follow is something people have been asking for
Done!
-
I finally got my extruder mounted on my Hevo. I'm trying to configure my BLTouch to work. I followed this thread and have been able to get the probe to deploy and stop once it triggers. Where I am having an issue is the offset. The nozzles are still too high. If I do an emergency stop I can then move the z up 1.5. So how do I tell the BL touch that this is where it should be. either this is "0" or have it offset.
I thought I would do it here in the code below, but thats not changing anything.
; EndstopsM574 X1 Y1 S1
M307 H3 A-1 C-1 D-1 ; use pin 3 on header for bltouch
M558 P5 X0 Y0 Z1 H5 F500 T2000 ; probe type and use probe for homing z
G31 X26.7 Y22.2 Z1.5 P25 ; Defines offset of sensor in relation to nozzle -
The Z parameter in the G31 command tells the firmware how high the nozzle is when the Z probe triggers. See https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_height.
-
The Z parameter in the G31 command tells the firmware how high the nozzle is when the Z probe triggers. See https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Calibrate_the_Z_probe_trigger_height.
step 8 says to repeat the above steps. When I do that, my height changes each time
7:08:53 AMG30 S-1
Stopped at height 1.834 mm
7:08:31 AMG30 S-1
Stopped at height 2.855 mm
7:08:05 AMG30 S-1
Stopped at height 2.812 mm
7:07:08 AMG30 S-1
Stopped at height 2.588 mm -
I had to lower my probing speeds and also introduced a recovery time. Still the probing heights changes range between -0.03 to 0.03 but my prints especially the first layer never caused me any issues.
From M558 P5 X0 Y0 Z1 H5 F500 T2000
I have M558 P9 X0 Y0 Z1 H5 F160 R0.250 T2000 ; P9 probe -
I've also heard that bltouch may be sensitive to the currents generated by the bed heater. So using the M558 B1 parameter supported in firmware 1.21RC4 may help.
-
I've also heard that bltouch may be sensitive to the currents generated by the bed heater. So using the M558 B1 parameter supported in firmware 1.21RC4 may help.
I'm actually starting to believe this. When using multi-tap with B1 A3 (and leaving S at the default 0.03), my printer probes exactly two times at each point. Without B1, I'd often get a third tap (and sometimes even a warning in the console log about inconsistent measurements.)
Of course, now that I've posted this, I'm sure my BLTouch will start becoming wildly inconsistent regardless of B1 settings or not.
-
I had to lower my probing speeds and also introduced a recovery time. Still the probing heights changes range between -0.03 to 0.03 but my prints especially the first layer never caused me any issues.
From M558 P5 X0 Y0 Z1 H5 F500 T2000
I have M558 P9 X0 Y0 Z1 H5 F160 R0.250 T2000 ; P9 probeNot sure if this was intended for me or not
-
I figured I could post here my question regarding the bltouch smart setup on my duet WiFi.
I am not using the duex, I followed instruction from the betrue blog, compared them with the ones here and can’t seem to get it working. I’ve cut the little logic strip to make it 3.3v. It’s setup on my #7 heater.
When I fire up my board the bltouch does its double pin down/up but after that I can’t get the probe to deploy or move using the M280 P7 S10 I1. The red light on the BlTouch is constantly on (can’t seem to find what that means on their instructions).Any ideas/suggestions?
-
I figured I could post here my question regarding the bltouch smart setup on my duet WiFi.
I am not using the duex, I followed instruction from the betrue blog, compared them with the ones here and can’t seem to get it working. I’ve cut the little logic strip to make it 3.3v. It’s setup on my #7 heater.
When I fire up my board the bltouch does its double pin down/up but after that I can’t get the probe to deploy or move using the M280 P7 S10 I1. The red light on the BlTouch is constantly on (can’t seem to find what that means on their instructions).Any ideas/suggestions?
Post your config.g and config-override.g please.
-
I figured I could post here my question regarding the bltouch smart setup on my duet WiFi.
I am not using the duex, I followed instruction from the betrue blog, compared them with the ones here and can’t seem to get it working. I’ve cut the little logic strip to make it 3.3v. It’s setup on my #7 heater.
When I fire up my board the bltouch does its double pin down/up but after that I can’t get the probe to deploy or move using the M280 P7 S10 I1. The red light on the BlTouch is constantly on (can’t seem to find what that means on their instructions).Any ideas/suggestions?
Post your config.g and config-override.g please.
Well i've switched it to heater 3 and it seems to be working fine. Perhaps is there a bug? The only thing i've changed is the P7 to P3 in my retract and deploy.
