Help with BLTouch

Mike McG

First let me apologize I realize this is probably already been covered
But I am unable to Figure out The BLTouch Sensor I have it wired And can trigger The pen deployment Using macros But I am having trouble With Deploy and retract.g Files I created the files With the proper GCode Inside One of my problems is the .G files I'm not triggering Or something I am using The DuetWiFi And is running the current Firmware I think
Where do I start Can I get a working configuration From someone? The printer is a corexy Hypercube With dual z motors
Thanks in advance For your help

I'm sorry about the screwed up way I'm writing But my eyes are bad So this is hardMike..

The new guy lol

BPisLife

@mike-mcg When you homez, does that work?

If the macros are working for it to drop the probe needle and retract it then you have it wired properly. Make sure you have deployprobe.g and retractprobe.g in the same location as config.g and not in the macros folder. It was a mistake I made it took me way longer than it should have for me to figure it out.

Can you post your config file?

Make sure you z is set to be probed:
M574 Z1 S2 ; Set endstops controlled by probe

Also that it is configured properly.
M558 P9 H5 F100 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves

This is my homez.g file:

G1 Z10 F6000 S2 ; lift Z relative to current position
G1 X70 Y100 F4000 ; Move probe to middle of bed
G30 ; Do a single probe to home our Z axis
G1 Z10 F500 ; Rapidly move the Z axis to Z=10.

Phaedrux

First, double check that things are wired correctly. Make sure it matches the way it's shown here: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

You'll need something like this in config.g

; BLTouch
M574 Z1 S2						; Use zprobe and home to Z Min.
M307 H3 A-1 C-1 D-1					; Unbind heater 3 pins for probe use.
M558 P9 H3 F100 T6000 A5 R0.1				; P9 for BLTouch, dive height 3mm, probe at 100mm/s, travel 6000mm/s, up to 5 probes, pause 0.1s
G31 X-43.2 Y31.9 Z1.812 P25				; probe XY offset and Z trigger height and trigger value 
M557 X10:280 Y35:270 S15				; Define mesh grid for full bed print

Mike McG

@bpislife

This is my current Config.g;By; weConfiguration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Apr 16 2018 20:44:39 GMT+0200 (CEST)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M307 H7 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board.
M667 S1 ; Select CoreXY mode

; Network
M550 Hypercube MAX 3D ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S1 ; Enable FTP
M586 P2 S0 ; Disable Telnet

; Drives
; Define Drives
; Physical Drive connection
M569 P0 S1 ; Drive 0 X
M569 P1 S0 ; Drive 1 Y
M569 P2 S0 ; 1st z-motor (original Z)
M569 P3 S0 ; Extruder0
M569 P4 S0 ; 2nd Z-motor - Normally used as Extruder 1
M584 X0 Y1 Z2:4 U4 E3 ; Driver 0 For X, 1 for Y, Z=2:4 U=4, Extruder 3
M350 X16 Y16 Z16 U16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 U400 E100 ; Set steps per mm
M566 X800 Y800 Z12 U12 E800 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z400 U400 E9000 ; Set maximum speeds (mm/min)
M201 X800 Y800 Z250 U250 E800 ; Set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 U1000 E1000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 U0 S1 ; Set axis minima
M208 X300 Y200 Z300 U300 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z1 U1 S0 ; S1=Normally closed S0=Normally open 1=Minimum 2=Maximum

; Z-Probe
M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. Not using on XY, but using it on Z.
G31 P25 X0 Y-25.3 Z0.0 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
M557 X15:285 Y50:285 S20 ; Define mesh grid

; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B3950 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S300 ; Set temperature limit for heater 1 to 300C
M307 H0 A80.0 C233.2 D15.9 S1 B0 ; PID autotuning BED
M307 H1 A694.4 C155.0 D 4.6S1 ; PID autotuning Tool 1

; Fans

M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T50 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

; Tools

M563 P0 D0 H1 F0 ; Define tool 0: extruder 0, heater 1 fan 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M572 D0 S0.1 ; Enable pressure advance (linear)

I'm sure the problem starts here somewhere
Once again thanks for your help

dc42

You have P5 in your M558 command. Assuming you are using firmware 2.0 or 2.01, we recommend you use P9 instead.

BPisLife

@mike-mcg Three questions:

1)Can you also post your homez and homeall?
2) Also is the retractprobe.g and deployprobe.g in the same exact location as config.g?
3) Can you just confirm that the macros for deploy and retract work if you run them manually (click on them and click run)?

Mike McG

@bpislife yes the retract and deploy files are in the same directory as config.g I will post the homeZ file and homeall file as soon as I can

Mike McG

@bpislife
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Mon Apr 16 2018 20:44:39 GMT+0200 (CEST)
G91 ; relative positioning
G1 Z5 F7200 S2 ; lift Z relative to current position
G1 S1 X-255 Y-215 F3600 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-255 ; home X axis
G1 S1 Y-215 ; home Y axis
G1 X5 Y5 F7200 ; go back a few mm
G1 S1 X-255 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-215 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X42.25 Y15 F7200 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
G1 Z5 F120 S2 ; uncomment this line to lift the nozzle after homing

G1 Z-200 S1 F400 ; move Z down until the switch triggers
G1 Z2 F400
G1 Z-200 S1 F40 ; move Z down until the switch triggers
G90 ; back to absolute mode
G92 Z0.0 S2 ; tell the firmware that we are at Z=0.3mm
; homez.g
; called to home the Z axis
G91 ; relative mode
G1 Z4 F200 S2 ; raise head 4mm to ensure it is above the switch trigger height
G90 ; back to absolute mode
;G1 X-5 Y-5 S2 F2000 ; put the head wherever you want it to be when you home Z (omit this line if it doesn't matter)
G91 ; relative mode
G1 Z-200 S1 F400 ; move Z down until the switch triggers
G1 Z2 F400
G1 Z-200 S1 F40
G90 ; back to absolute mode
G92 Z0.0 S2 ; tell the firmware that we are at Z=0.3mm

BPisLife

@mike-mcg can you confirm question 2, which was does the macros work?

Not sure why you are moving Z down to a switch trigger after you probe. This is my homez.g and I recommend you try it. Comment out everything by putting a semicolon in front of each line.

homez.g
G1 Z10 F6000 S2 ; lift Z relative to current position
G1 X42.25 Y15 F7200 ; Move probe to middle of bed
G30 ; Do a single probe to home our Z axis
G1 Z10 F500 ; Rapidly move the Z axis to Z=10.

homeall.g
G91 ; relative positioning
G1 Z5 F7200 S2 ; lift Z relative to current position
G1 S1 X-255 Y-215 F3600 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-255 ; home X axis
G1 S1 Y-215 ; home Y axis
G1 X5 Y5 F7200 ; go back a few mm
G1 S1 X-255 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-215 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 Z10 F6000 S2 ; lift Z relative to current position
G1 X42.25 Y15 F7200 ; Move probe to middle of bed
G30 ; Do a single probe to home our Z axis
G1 Z10 F500 ; Rapidly move the Z axis to Z=10.

Mike McG

@bpislife thanks for your help quick question it looks like when the G30 command is issued the bed moves down until it crashes any ideas

BPisLife

@mike-mcg I think it is as easy as changing the motor direction "M569 P2 S0 to M569 P2 S1" and since you have two motors for z, M569 P4 S0 to M569 P4 S1.

Try that and let me know.

dc42

@bpislife said in Help with BLTouch:

@mike-mcg I think it is as easy as changing the motor direction "M569 P2 S0 to M569 P2 S1" and since you have two motors for z, M569 P4 S0 to M569 P4 S1.

Try that and let me know.

@Mike-McG, just to be clear: if it is the bed that moves in the Z direction (not the nozzle), then +Z should move the bed down and -Z should move the bed up. This is because the Z coordinate is the distance between the nozzle and the bed.

Mike McG

@dc42 thanks I figured that out the motor Direction was wrong but the BL touch is not deploying when the G30 command is issued does the G30 command automatically call to the deployprobe.g file?

dc42

@mike-mcg said in Help with BLTouch:

@dc42 thanks I figured that out the motor Direction was wrong but the BL touch is not deploying when the G30 command is issued does the G30 command automatically call to the deployprobe.g file?

Yes (unless you are using very old firmware), unless you have previously sent M401 to deploy the probe yourself and not used M402 to retract it.

Mike McG

I'm using 2.01 but it's still not deploying or retracting at G30 command

dc42

Try sending M401 and M402 from the command line. If they don't deploy and retract the probe, check the wiring, the config.g file, and the deployprobe.g and retractprobe.g files.

Qdeathstar

Did you cut the trace to make it 3.3v and not 5v? Also, is the bl-touch blinking red or steady red or off?

pro3d

Sorry if i missed it and I am late to this but did you post the deploy.g and retract.g? Did you do self test M280 Px S120? and M280 Px S160?

Mike McG

Well after very close examination of the trace on the back of the BL touch the trace was almost cut through but not enough it works thank you very much for all your help

Mike McG

@qdeathstar it was the 3. 3 volt logic Trace and now everything seems to be fine go figure something as small as a little Trace thanks for your help