"Error: Probe already triggered at ...." based on location??!
-
I now read almost all topics I found about "Error: Probe already triggered at start of pra betnobing move". And none did help. Almost any mentioned to check wiring etc ...
How it did start: I got a genuine bltouch probe working fine with a bent pin. So I took the chance to replace it with a triangle labs clone just to see how it would perform.
I also installed a genuine e3d all metal hotend, so I had to calibrate z-trigger height. As soon as I did the last step and entered "G30 S-1", and entered the measured height to config.g the problems occured.
Running G32 (for a dual z-axis setup) and these commands (bed.g):
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Feb 20 2021 00:36:17 GMT+0100 (Mitteleuropäische Normalzeit) M561 ; clear any bed transform G1 E-5 F50 G30 P0 X112 Y0 Z-99999 ; probe near a leadscrew back G30 P1 X112 Y205 Z-99999 S2 ; probe near a leadscrew frontNow running G32 I could probe the first axis, then the head moved to the second on, deployed the needle, immediately retracted it, and threw the "already triggered error".
I was completely lost and removed the bltouch, checked everyhing etc. Until this morning I used the configuration tool to create a new config. And tadaaa! It worked instantely.
Great I thought, but I want z-probing in the middle of the bed, so I changed homez.g:
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.12 on Mon Aug 15 2022 12:23:00 GMT+0200 (Central European Summer Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning ;G1 X15 Y15 F6000 ; go to first probe point G1 X115 Y115 F6000 ; go to middle of bed G30 ; home Z by probing the bedGuess what. It throws the same error again. I can't probe at 115/115 as it says "probe already triggered". Changing probing point back to 15/15 works fine again!
HOW CAN THAT BE?!? Any ideas?
This is release 3.4.1
; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.12 on Mon Aug 15 2022 12:23:00 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender5_2" ; set printer name M918 P2 E4 ; enable 12864 M150 R255 U255 B255 P255 S13 ; LCD Backlight full white ; Network M587 xxxxxxxx ; set password M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards X? M569 P1 S0 ; physical drive 1 goes backwards Y? M569 P2 S1 ; physical drive 2 goes forwards = Z1 M569 P3 S1 ; physical drive 3 goes forwards = Extruder M569 P4 S0 ; physical drive 4 goes backwards = Z2 M584 X0 Y1 Z2:4 E3 ; set drive mapping M671 X115:115 Y-70:240 S4 ; Set the Z motor relative locations M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z800.00 E413.00 ; set steps per mm 428=old 413=bgm M566 X1600.00 Y1600.00 Z800.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X10000.00 Y10000.00 Z600.00 E3600.00 ; set maximum speeds (mm/min) M201 X800.00 Y800.00 Z50.00 E5000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z900 E800 ; set motor currents (mA) M84 S0 ; Disable motor idle current reduction ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X225 Y210 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z3 ; set Z probe trigger value, offset and trigger height M557 X50:215 Y15:185 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M307 H0 R0.300 C548.0 D4.19 S1.00 V24.0 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 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"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 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 M501 ; load saved parameters from non-volatile memory -
@izeman maybe try increasing the dive height a bit (the H value in M558)? or increase the Z height on line 6 from 5 to 10?
-
@jay_s_uk said in "Error: Probe already triggered at ...." based on location??!:
@izeman maybe try increasing the dive height a bit (the H value in M558)? or increase the Z height on line 6 from 5 to 10?
Thanks for the suggestion but none helped. Result is the same.
What's REALLY strange is: Running a MESH COMPENSATION it starts at like 15/15, then moves to the left (increases X by 20), 35/15, 55/15, 75/15 work fine, 95/15 doesn't work.
I can repeat that as often as I want.
I then changed G32 to probe X112/Y205 firstm to check if it maybe is just the second probe that doesn't work, but no. I says "already triggered at 112/205 then goes to 112/0 and probes just fine.
-
@izeman only other thing I can think of is add a small amount of recovery time in on your M558 e.g.
R0.2 -
Next test: I moved the nozzle mm per mm and issued a G30 command to measure z-height.
It's easy to predict when it will not work any more, because as soon as i cross the X125/Y41 mark the z-probe in web interface jumps from 0 to pink 1000. So everything below X125 and below Y41 is ok, once X>125 or Y>41 it triggers the error - I don't even need to issue the G30 command.
-
Doesn't seem to be so easy: it isn't a horizontal or vertical line I need to cross.
The line seems to go from 152/0 to like 0/90.
Maybe something with the heightmap?!
-
btw: I print perfectly fine though. I just need to ignore the G32 errors etc, but it can reach all bed positions and works fine.
-
@izeman sounds like a wiring issue then and moving passed a set point pulls a wire
-
@jay_s_uk said in "Error: Probe already triggered at ...." based on location??!:
@izeman sounds like a wiring issue then and moving passed a set point pulls a wire
OH MAN! Seems it REALLY IS A WIRING ISSUE. I checked all connectors, measured for short and voltage before. Twice, three times, but it seems the long wire coming from the board is broken somewhere.
I can trigger the PINK 1000 by moving the wire.THANKS!!
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
