Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Error: Probe was not triggered during probing move

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    5
    24
    2.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • milan.bacaundefined
      milan.baca @Phaedrux
      last edited by

      @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

      1 Reply Last reply Reply Quote 0
      • milan.bacaundefined
        milan.baca @Phaedrux
        last edited by

        @phaedrux
        I removed G92 Z0 from homeall.g

        but still same error

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Reduce your dive height from M558 H15 to H5

          Z-Bot CoreXY Build | Thingiverse Profile

          milan.bacaundefined 1 Reply Last reply Reply Quote 0
          • milan.bacaundefined
            milan.baca @Phaedrux
            last edited by

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

            dc42undefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @milan.baca
              last edited by

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

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              milan.bacaundefined 1 Reply Last reply Reply Quote 0
              • milan.bacaundefined
                milan.baca @dc42
                last edited by

                @dc42 config.g

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @milan.baca
                  last edited by 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?

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  dc42undefined milan.bacaundefined 2 Replies Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @jay_s_uk
                    last edited by

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

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    milan.bacaundefined 2 Replies Last reply Reply Quote 0
                    • milan.bacaundefined
                      milan.baca @jay_s_uk
                      last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • milan.bacaundefined
                        milan.baca @dc42
                        last edited by

                        @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 🙂

                        1 Reply Last reply Reply Quote 1
                        • milan.bacaundefined
                          milan.baca @dc42
                          last edited by

                          @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?

                          dc42undefined 1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators @milan.baca
                            last edited by

                            @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?

                            Duet WiFi hardware designer and firmware engineer
                            Please do not ask me for Duet support via PM or email, use the forum
                            http://www.escher3d.com, https://miscsolutions.wordpress.com

                            milan.bacaundefined 2 Replies Last reply Reply Quote 0
                            • milan.bacaundefined
                              milan.baca @dc42
                              last edited by 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

                              dc42undefined 1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators @milan.baca
                                last edited by

                                @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.

                                Duet WiFi hardware designer and firmware engineer
                                Please do not ask me for Duet support via PM or email, use the forum
                                http://www.escher3d.com, https://miscsolutions.wordpress.com

                                1 Reply Last reply Reply Quote 0
                                • milan.bacaundefined
                                  milan.baca @dc42
                                  last edited by

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

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA