Bl-touch re-deploy after probing or z homing

BLV

@phaedrux said in Bl-touch re-deploy after probing or z homing:

I think it being a clone has more to do with it than anything.

Have you verified the trace is cut with a multimeter?

I dont think so, because yeataday i installed my friend's genuine Bltouch v2.0 smart and it has the same problem.
Yes, i used a microscope at work to cut the trace and verified with a fluke.

Phaedrux

@blv sorry I missed that.

What are using for M558?
What are your movement speed settings?

BLV

@phaedrux
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T6000

bugm

@dc42 said in Bl-touch re-deploy after probing or z homing:

Is this on a Duet WiFi, Ethernet, or Maestro?

i got the 1.01 - i erased the firmware and installed again 2.02RC2 from scratch - no difference.
no idea what to do, replacing the wires made no difference.
even while homing z axis alone, every 2-3 homing it keeps happening - after probing the pin deploys
again while the bed moving down (core xy). it hits the glass before the bed went down, then retracts.
just to check as @Blv - i installed it on my mks gen-l and it works without any issue.

genghisnico13

I've been having some problems with my 3D Touch (when it probes a hot bed), so I made a video to ask for a new one, is your probe behaving different from how its seen in the video?
Sorry for the background noise around the middle, the power company is making some holes.

Phaedrux

@genghisnico13 How do you have the probe mounted? Your video makes it look like there is a bolt right above the top of the probe and it looks like it might be right beside a stepper motor? It uses an electromagnet and could be susceptible to pieces of metal being too close to it. If you take the probe out of the mount and just suspend it in the air and trigger it by hand, does it behave the same way?

BLV

@genghisnico13 said in Bl-touch re-deploy after probing or z homing:

I've been having some problems with my 3D Touch (when it probes a hot bed), so I made a video to ask for a new one, is your probe behaving different from how its seen in the video?
Sorry for the background noise around the middle, the power company is making some holes.

Its almost identical, except that in my case its deploying the pin only one time after it already probed the point. (On your video its deploying even more).

genghisnico13

@phaedrux You could be right, but since the seller has already agreed to send me a new one.... I'll test it in mid air when the new one arrives (couple of months). Worst case I end up with 2 working probes.
I assumed it was designed to be in close proximity to ferrous materials and put it in the only place with free space that doesn't limit movement length, could have been a bad choice, will see after testing.

dc42

It's also worth remembering that high-current bed heaters can affect the trigger height of a BLTouch, although I've not heard of them causing the pin to redeploy. So if you are probing with the bed heater turned on, try turning it off, or add parameter B0 to the M558 command.

bugm

@dc42 Do you have any idea what should i do please?
I'm so frustrated and praying to the 3d printing god to get it work

bugm

@dc42 said in Bl-touch re-deploy after probing or z homing:

It's also worth remembering that high-current bed heaters can affect the trigger height of a BLTouch, although I've not heard of them causing the pin to redeploy. So if you are probing with the bed heater turned on, try turning it off, or add parameter B0 to the M558 command.

The heater is off always .

dc42

Please share your config.g, deployprobe.g and retractprobe.g files. Also run M115 to verify which firmware version is running, in case the firmware update failed.

bugm

@dc42 said in Bl-touch re-deploy after probing or z homing:

Please share your config.g, deployprobe.g and retractprobe.g files. Also run M115 to verify which firmware version is running, in case the firmware update failed.

Thank you @dc42

M115:

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02RC2(RTOS) ELECTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2018-09-07b2

Here are my files:
config.g:

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on 

; General preferences
G90                                                ; Send absolute coordinates...
M83                                                ; ...but relative extruder moves

M667 S1                                            ; Select CoreXY mode

; Network
M550 PBugmBugm                                     ; Set machine name
M552 S1                                            ; Enable network
M587 S"********" P"********"                       ; Configure access point. You can delete this line once connected
M586 P0 S1                                         ; Enable HTTP
M586 P1 S0                                         ; Disable FTP
M586 P2 S0                                         ; Disable Telnet

; Drives
M569 P0 S0                                         ; Drive 0 goes forwards
M569 P1 S0                                         ; Drive 1 goes forwards
M569 P2 S1                                         ; Drive 2 goes backwards
M569 P3 S0                                         ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1                            ; Configure microstepping with interpolation
M92 X200 Y200 Z400 E413.49                         ; Set steps per mm
M566 X720 Y720 Z12 E120                            ; Set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 E1200                        ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E1000                          ; Set accelerations (mm/s^2)
M906 X1600 Y1600 Z1600 E1600 I30                   ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X-20 Y-20 Z0 S1                               ; Set axis minima
M208 X350 Y350 Z350 S0                             ; Set axis maxima

; Endstops
M574 X1 Y1 S1                                      ; Set active high endstops

; Z-Probe
M574 Z1 S2                                         ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1                                ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F100 T7000                              ; Set Z probe type to bltouch and the dive height + speeds 
G31 P25 X28.5 Y-5 Z0.86                            ; Set Z probe trigger value, offset and trigger height
M557 X15:285 Y15:285 S60                           ; Define mesh grid

; Heaters
M305 P0 T100000 B4138 C0 R4700                     ; Set thermistor + ADC parameters for heater 0
M143 H0 S100                                       ; Set temperature limit for heater 0 to 100C
M305 P1 T100000 B4138 C0 R4700                     ; Set thermistor + ADC parameters for heater 1
M143 H1 S260                                       ; Set temperature limit for heater 1 to 260C

; 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 T45                          ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45                          ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H1                                      ; Define tool 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

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured
M564 H0                                   	   ; Let the Jog buttons work

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on
M280 P3 S10 I1	        ;deploy the probe.
G4 P200 	        ;delay 200ms.

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool on
M280 P3 S90 I1          ;retract.
G4 P200 		;delay 200ms.

dc42

I'm not sure about those G4 P200 commands in deployprobe.g and retractprobe.g. I'm not aware of other people using them. So I suggest you remove them and add parameter R0.2 to the M558 command instead..

bugm

@dc42 said in Bl-touch re-deploy after probing or z homing:

I'm not sure about those G4 P200 commands in deployprobe.g and retractprobe.g. I'm not aware of other people using them. So I suggest you remove them and add parameter R0.2 to the M558 command instead..

@dc42 it added the delay line only yesterday after someone suggested, but it not solved the problem.
i even upgraded to 2.02RC3 and problem still there.
does my config looks alright? any idea what more should i check?

dc42

My guess is that your clone behaves a little differently from a genuine BLTouch. You could try changing your deployprobe.g file to this:

M280 P3 S10 I1 ; deploy the probe.
G4 P200 ; delay 200ms.
M42 P3 S0 I1 ; stop sending the deploy command

bugm

@dc42 I fixed the issue by switching to your mini IR module
works great without any issue, Thanks

paul12

@dc42 am facing the same issue, will try this method and inform the result