Problem with BLTouch after firmware update
-
Hello, after updating my firmware to 3.3, my BLTouch started to act very strangely. The probe repeatedly deploys and retracts. How do I fix this?
My gcode:
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun Jul 11 2021 22:49:11 GMT+0300 ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M669 K1 ; select CoreXY mode ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes backwards M569 P0.5 S1 ; physical drive 0.5 goes forwards M584 X0.0 Y0.1 Z0.2 E0.5 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X550 Y350 Z400 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io2.in" ; configure active-high endstop for low end on X via pin io2.in M574 Y1 S1 P"io5.in" ; configure active-high endstop for low end on Y via pin io5.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"^io7.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:550 Y15:350 S50 ; define mesh grid ; Heaters M308 S0 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp1 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp0 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 R3.618 C135.2:115.2 D6.65 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out8" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out7" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; 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 ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
-
My board is Duet 3
-
At what point does it start doing that?
It seems as if power is being switched on and off. Check the crimps on the 5v wire.
-
@phaedrux
I noticied that it starts doing that with every console error -
-
@peter247
G28
Error: Probe already triggered at start of probing moveFor example
-
Hi,
I have a similar problem with my blTouch after upgrading to RRF3.3 (Board: Duet wifi 2 ).
I replaced the wiring with a shielded cable, but the issue is still there. -
Just noticied that fan0 control also triggers BLTouch probe deployment and retraction
-
@dkkovalev this may not solve it, but you should remove the ^ in the M558 command. On Duet 2 it's needed when you're using the Z probe input, but on Duet 3 it reduces the noise margin.
-
@dc42
No, removing the ^ from M558 didn't help -
@dkkovalev
But after removing the ^ from M558 the probe started to deploy and retract much less often -
@dkkovalev said in Problem with BLTouch after firmware update:
@dkkovalev
But after removing the ^ from M558 the probe started to deploy and retract much less oftenIs the BLTouch cable running next to a stepper motor cable?
-
@dc42 Yes, all cables from the printing head as well as the cable from a stepper motor are in the same harness
-
This post is deleted! -
@dkkovalev my guess is that either you have a bad ground connection between the BLTouch and the Duet, or the BLTouch cable is picking up noise inductively from the stepper motor cable.
-
@dc42
Sorry for long response, tried to move BLTouch cable from motor as far as I could, double checked and tested the GND wire, but it did nothing to me -
@dkkovalev Did you ever figure out a solution cause Im having the same issue? I ran an M558:
M558
Z Probe 0: type 9, input pin io3.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03Why does it say output pin nil when I have it configured in the RR Configurator as io3.out?
It was working fine and then I installed a new PSU and cant seem to get it working right since then and I went back to the old PSU and still it is a no go dont know what is going on. When the board is powered up, regardless of PSU source, it will always detract and retract the probing pin two or three times but then when I home X, Y, then try for Z I get a:
G28 Z
Error: Probe already triggered at start of probing move
Error: Probe already triggered at start of probing moveDont know what is going on?
-
@pickett said in Problem with BLTouch after firmware update:
Why does it say output pin nil when I have it configured in the RR Configurator as io3.out?
The output pin it's talking about is the mod pin used for something like the smart effector. It's not the same as the servo pin for the bltouch.
@pickett said in Problem with BLTouch after firmware update:
Error: Probe already triggered at start of probing move
Check your white wire. If you need more, start a new thread.
-
@pickett
Well, not really, but after tuning steps/mm on all motors the issue suddenly disapeared. Also i checked and rang all wires