Error: Probe was not triggered during probing move

milan.baca

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC3 (2021-05-26 12:29:42) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9FJ-3S86R-1T96T
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 150784
Dynamic ram: 62052 of which 160 recycled
Never used RAM 141196, free system stack 126 words
Tasks: SBC(ready,5.2%,338) HEAT(delaying,0.0%,295) Move(notifyWait,0.0%,275) CanReceiv(notifyWait,0.0%,945) CanSender(notifyWait,0.0%,360) CanClock(delaying,0.0%,333) TMC(notifyWait,7.9%,59) MAIN(running,86.8%,922) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:38:42 ago, cause: software
Last software reset at 2021-06-13 15:27, reason: User, none spinning, available RAM 141196, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Step timer max interval 133
MCU temperature: min 39.4, current 39.6, max 53.4
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 66722, standstill, reads 27175, writes 23 timeouts 0, SG min/max 0/227
Driver 1: position -24410, standstill, reads 27175, writes 23 timeouts 0, SG min/max 0/227
Driver 2: position 28000, standstill, reads 27184, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 27176, writes 22 timeouts 0, SG min/max 0/228
Driver 4: position 0, standstill, reads 27176, writes 22 timeouts 0, SG min/max 0/233
Driver 5: position 0, standstill, reads 27177, writes 22 timeouts 0, SG min/max 0/246
Date/time: 2021-06-13 16:06:00
Slowest loop: 177.37ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 297675ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 43, completed moves 43, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 20904, send timeouts 20901, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 11614/0/0
Last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 16462/16462
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8bc
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-rc3
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.35
Codes per second: 0.09
Maximum length of RX/TX data transfers: 2756/864

M98 P"config.g"
Error: M350: Driver 3 does not support x0 microstepping with interpolation
Driver 4 does not support x0 microstepping with interpolation
Driver 5 does not support x0 microstepping with interpolation
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 516C

Phaedrux

@milan-baca said in Error: Probe was not triggered during probing move:

Error: M350: Driver 3 does not support x0 microstepping with interpolation
Driver 4 does not support x0 microstepping with interpolation
Driver 5 does not support x0 microstepping with interpolation

Those are your Z drivers, correct? Have you changed microstepping since posting your config.g above?

Phaedrux

Remove this from your homeall

G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

milan.baca

@phaedrux yes I change it to
M350 X16 Y16 Z16:16:16 E16 I1

I change it back to Z16 and now

M98 P"config.g"
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 516C

milan.baca

@phaedrux
I removed G92 Z0 from homeall.g

but still same error

Phaedrux

Reduce your dive height from M558 H15 to H5

milan.baca

@phaedrux not helped, Error: This kinematics does not support auto-calibration is still there

dc42

@milan-baca I think you must have made another change to config.g. Please post it as it is now.

milan.baca

@dc42 config.g

jay_s_uk

easier to read

; 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 Apr 04 2021 22:18:55 GMT+0200 (CEST)

; General preferences
G90                                                  ; send absolute coordinates...
M83                                                  ; ...but relative extruder moves
M550 P"Duet 3"                                       ; set printer name
M669 K1                                              ; select CoreXY mode
M912 S-13.7										     ; mcu temperature correction

; Drives
M569 P0.0 S0 ;H50 V50 D3                             ; physical drive 0.0 goes forwards axis X
M569 P0.1 S0 ;H50 V50 D3                             ; physical drive 0.1 goes forwards axis Y
M569 P0.2 S0                                         ; physical drive 0.2 goes forwards EXTRUDER
M569 P0.3 S0 ;H50 V50 D3                             ; physical drive 0.3 goes forwards
M569 P0.4 S0 ;H50 V50 D3                             ; physical drive 0.3 goes forwards
M569 P0.5 S0 ;H50 V50 D3                             ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.3:0.4:0.5 E0.2                     ; set drive mapping
M671 X-26,188:155,021:331,23 Y-20,717:307,493:-20,717 S50 ;Z Lift Point position

M350 X16 Y16 Z16 E16 I1                        	 	 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z1600.00 E712.00                 ; set steps per mm
M566 X1200.00 Y1200.00 Z30.00 E120.00                ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z1800.00 E1200.00           ; set maximum speeds (mm/min)
M201 X1600.00 Y1600.00 Z100.00 E250.00               ; set accelerations (mm/s^2)
M906 X1400 Y1400 Z1400 E300 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 X320 Y320 Z321 S0                               ; set axis maxima

; Endstops
M574 X1 S1 P"io0.in"                                 ; configure active-high endstop for low end on X via pin io0.in
M574 Y1 S1 P"io1.in"                                 ; configure active-high endstop for low end on Y via pin io1.in

; Z-Probe
M950 S0 C"io7.out"                                   ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H15 F150 T6000 R0.2 A5
G31 P25 X22.775 Y5.21 Z2.5                           ; set Z probe trigger value, offset and trigger height
M557 X25:282 Y10:282 P5:5                            ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4267         ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                   ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00                                     ; enable 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"temp1" Y"thermistor" T100000 B3950         ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1                                   ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R3.678 C133.6 D6.67 S1.00 V24.0
M143 H1 S280                                         ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7" ;Q250                                 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H1 T45                                    ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out4" Q500                                 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H-1                                    	 ; set fan 1 value. Thermostatic control is turned of

; 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

;M581 Y S1 T2
; Miscellaneous
M308 S10 Y"mcu-temp" A"MCU"

M501
M911 S22 R23.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0

Your M671 doesn't look valid to me
how is your bed supported? what are the co-ordinates of the screws?

dc42

I agree with @jay_s_uk. Change the commas in the M671 command to fullstops.

milan.baca

@jay_s_uk
I am using calculator from this project
https://miragec79.github.io/HevORT/firmwaresettings.html

milan.baca

@dc42 thank you very much guys problem was in M671 command in numbers

I look at it many times but after you point to that command I saw the problem. It was decimal separator in coordinates

milan.baca

@dc42
G32 command now work well

still have a problem with G29
after few points I got
Error: Probe already triggered before probing move started

ps: should I make a new thread or can I continue here?

dc42

@milan-baca does it do that at the same probe point each time, or at different points?

In this line:

M558 P9 C"io7.in" H15 F150 T6000 R0.2 A5

you could try increasing R0.2 to R0.3. If that doesn't fix it then I suspect that the pin of the BLTouch may be sticky. Is it a genuine BLTouch, or a clone?

milan.baca

@dc42 triangle lab (not genuine) - but this one I am using on my other printer (I took it from there) with duet2 wifi for years and it works well there

dc42

@milan-baca you could also try reducing the maximum Z speed in M203, in case the Z axis can't keep up with the commanded speed when the probe is raised.

milan.baca

@dc42 thank you very much again R0.3 was the trick