BLTouch working
-
Yep my printer is pretty solid and prints consistently. I took it apart to make sure nothing got loose, tightened a few things, didn't help sadly. I am still getting deviations of 0.5mm maximum.
The grid is pretty random, I can upload the map if you want but I dont think it will help much.
I actually didnt get any docs with my BLTouch,, although it looked legit. I got it from spool3d.com. I modelled my own mount, and the distance from probe (retracted) to tip of nozzle is just 1.61mm. I read a distance of 2mm is optimal, so I don't think my mount height is causing any issues. Honestly at this point im thinking the probe is defective.
Thanks a lot for the help, I really appreciate it.
-
I thought the probe I got was defective at one point as well. It turned out my config override was causing the issues. You've ruled that out already. See if you can get it to probe the same exact spot over and over to P0 P1, P2, etc and see how much the values vary.
Jeff
-
If you are not getting consistent results from a Z probe, using a lower probing speed may help. It's the F parameter in the M558 command.
-
I probed the same spot 20 times and I ended up getting a standard deviation of 0.054.
Hopefully we can get this solved, I am losing hope though lol.
EDIT: Thanks for the input dc42. I dropped the probing speed to 100. I had already tried that with bad results, but this time I got a standard deviation of 0.026.
I will lower the speed again.I dropped the speed again to 50. Standard deviation is 0.032.
Any other ideas?
-
If the BL touch is genuine then contact the manufacturer and ask what repeatability they expect. Could be a hardware fault.
-
I just ran a bed probe:
This was on a dirty piece of glass with some left over print residue.
35 points probed, mean error -0.125, deviation 0.055On a different piece of semi clean glass:
35 points probed, mean error -0.050, deviation 0.076and again on the same peice:
35 points probed, mean error -0.170, deviation 0.073What command did you run to get the multi point probe ? I can try that.
Edit: Whatever my results I'm getting really nice flat first layers with even widths. Probes were done at F300.
Jeff
-
So I will take the 5v and Gnd from the expansion port (pin 1 & 2) also taking the Servo pin from the same source (pin 8 (heater 3)).
Now when wiring the bltouch black and white wires into the DuetWifi Z- probe pins do they go to 3.3v and Gnd or Z- probe in and GND?
Also is it OK to crimp the resistor in with the pin connectors?
-
So I will take the 5v and Gnd from the expansion port (pin 1 & 2) also taking the Servo pin from the same source (pin 8 (heater 3)).
Now when wiring the bltouch black and white wires into the DuetWifi Z- probe pins do they go to 3.3v and Gnd or Z- probe in and GND?
Also is it OK to crimp the resistor in with the pin connectors?
Z probe in and gnd. Be sure to use probe type 5 in M558. Also I dont see any problem crimping the resistor in the pin connector, as long as they are connected properly across. It might be easier to strip some insulation further up the wire though and put a bit of solder, but either or should work.
–---
And (In)Sanity here is my probing files, I have been using G30 S-1 to probe the single spot, the centre of my bed. For the G32 probe (auto bed compensation) my bed.g file contains this:
M98 Pdeployprobe.g
; Probe the bed at 5 points
G30 P0 X25 Y15 H0 Z-99999
G30 P1 X25 Y175 H0 Z-99999
G30 P2 X185 Y175 H0 Z-99999
G30 P3 X185 Y15 H0 Z-99999
G30 P4 X100 Y100 H0 Z-99999 S
M98 Pretractprobe.gMy mesh leveling macro is as follows:
G91
G1 Z6 F200
G90
M98 Pdeployprobe.g
G29 S2
M557 X20:180 Y20:180 S40
G29
M98 Pretractprobe.gI have contacted Antclabs, but if anyone has any other suggestions please let me know! Thanks
-
Do you have to define the servo pin anywhere? I'm thinking back to the way you use pins_Rumba.h to define the pins used in marlin, is there anything similar.
-
The servo pin is defined by the P3 parameter in the M280 commands in the deployprobe.g and retractprobe.g files.
-
Excellent! Do you define the bed limits for probing anywhere? Does this all currently look on track?
Config.g:
; *** BLTouch and Compensation
M558 P5 X0 Y0 Z1 H3 F200 T5000 ; BLTouch Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
G31 P1 X-25.0 Y58.0 Z-1.0 ; Set the Z-probe position and thresholdBed.g:
G28 ;home all
G91 ;relative mode
G1 Z4 F200 ;move Z up 4mm for clearence
G90 ;absolute mode
M98 Pdeployprobe.g ;call macro
G29 S2 ;clear bed compensation
G29 ;run auto bed mesh level
M98 Pretractprobe.g ;call macro
G1 X10 Y10 F5000 -
this is from my own config
M557 X20:290 Y60:280 S60 ;probe boundaries with roughly 16 points (290-20=270/4=67.5 280-60=220/4=55)bounding box of x20 to x290, y60 to y280 with 60mm spacing
-
Deckingman said "I currently use DC42s excellent probe" what is this probe? I am in the market for my next printer…
-
Deckingman said "I currently use DC42s excellent probe" what is this probe? I am in the market for my next printer…
IR probe
-
Excellent! Do you define the bed limits for probing anywhere? Does this all currently look on track?
Config.g:
; *** BLTouch and Compensation
M558 P5 X0 Y0 Z1 H3 F200 T5000 ; BLTouch Z probe, used for homing Z axis, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
G31 P1 X-25.0 Y58.0 Z-1.0 ; Set the Z-probe position and thresholdBed.g:
G28 ;home all
G91 ;relative mode
G1 Z4 F200 ;move Z up 4mm for clearence
G90 ;absolute mode
M98 Pdeployprobe.g ;call macro
G29 S2 ;clear bed compensation
G29 ;run auto bed mesh level
M98 Pretractprobe.g ;call macro
G1 X10 Y10 F5000The Z-1.0 in the G31 command is wrong because the trigger height will be positive. You need to define the probing grid somewhere using M557. You don't need the G29 S2 before the G29.
-
So I have wired everything loaded all my macros, re-pinned a z-stepper (grr) and now everything is nice and smooth. I am now stuck on how to calibrate the BLTouch on the Duet? I have done it in marlin before but wondered if anyone can point me in the right direction when doing it with the Duet?
-
I got my BLTouch installed and working on my CoreXY printer. I can home Z with it with no problems. I am now trying to get the rest of the configuration files setup for it.
I am running on a Duet 0.8.5 with 1.16 Firmware. My BLTouch (when looking from the front of the printer) is to the right and back of the nozzle (X50 Y37).
In config.g, I have
[c]M558 P4 X0 Y0 Z1 H5 F100 T2000 ; Switch for Z probe.
; Move 5mm between probes.
; Probe speed 100mm/min.
; Travel speed 500mm/min.G31 X50 Y36 Z2.35 P5 ; Set the probe height and threshold (put your own values here)
[/c]From what I was reading for the G31 command, when I home Z and it triggers, it should set the Z position to 2.35. This is the distance I measured the nozzle is from the bed after homing the Z axis. But after homing, Z is at zero. So I'm not understanding something here.
For the axis minimums (this command is before the M558 and G31 commands), I have…
[c]M208 X-8 Y0 Z0 S1 ; set axis minimum (adjust to make X=0 and Y=0 the edges of the bed)[/c]Another question I have is with the G30 probing and the XY locations. If I use G30 with X150 Y100 in the bed.g file, where is the nozzle position suppose to end up? Would the nozzle be at 150,100 or would the offsets in the G31 be applied and the nozzle would actually be at 100, 64?
-
according to the bltouch people, to work with 3.3v logic electronics you only need a 240ohm resistor in line with the 2-wire endstop. that could be where your not getting a response.
I am feeling a little slow here, but is this in series with one of the wires, or bridging the IN and GND wires at the PROBE connector on a DuetWifi?
I finally got the +5VDC, COM, and H3 connections correct, and the probe deploying/retracting, but am not getting any input from the probe, and am really starting to doubt my wiring of the sensor portion.
Currently I have a 240 Ohm resistor across the two wires, crimped into Dupont pins with the wires from the hall sensor output, but it shows up as 0 on the Z-Probe on the web control screen when tested with the auto-test macro that was posted in this thread, nor if pressed directly. If it is unplugged, I see a value of 1000 on the Z-probe, and the field is shaded red.
-
according to the bltouch people, to work with 3.3v logic electronics you only need a 240ohm resistor in line with the 2-wire endstop. that could be where your not getting a response.
I am feeling a little slow here, but is this in series with one of the wires, or bridging the IN and GND wires at the PROBE connector on a DuetWifi?
.
Spot on, you need to bridge the In and GND on the Z probe pins with the resistor.
-
according to the bltouch people, to work with 3.3v logic electronics you only need a 240ohm resistor in line with the 2-wire endstop. that could be where your not getting a response.
I am feeling a little slow here, but is this in series with one of the wires, or bridging the IN and GND wires at the PROBE connector on a DuetWifi?
I finally got the +5VDC, COM, and H3 connections correct, and the probe deploying/retracting, but am not getting any input from the probe, and am really starting to doubt my wiring of the sensor portion.
Currently I have a 240 Ohm resistor across the two wires, crimped into Dupont pins with the wires from the hall sensor output, but it shows up as 0 on the Z-Probe on the web control screen when tested with the auto-test macro that was posted in this thread, nor if pressed directly. If it is unplugged, I see a value of 1000 on the Z-probe, and the field is shaded red.
ok, due to the refresh rate of the website, it doesnt always capture the tiny pulse of the pin being triggered. that doesnt mean that the trigger isnt happening. If you put the bltouch(genuine, clones unknown) in an error state(blinking), an M119 should show the endstop triggered. Once you verify that use:
M280 P3 S10 I1 ```and manually trigger the pin over and over until you see it display in the web control. It wont display all the time but it will occasionally. It may not show a trigger(color change) on the web control, but you may get a value change on the signal value displayed. you need to put your tigger value below that number(or just use 25)
