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

    G32 Error:´´ Z probe was not triggered during probing move´´

    Scheduled Pinned Locked Moved
    Firmware installation
    4
    95
    4.7k
    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.
    • duttiundefined
      dutti @fcwilt
      last edited by

      @fcwilt
      Probe is working.
      I don´t know what I have to change in my bed.g file...
      you told me you wanna make a test. So I did it.... and now? 😞
      I made a G32 and it´s doing a G29. Why? 😕
      I just wanna make a 4 point true auto level.... thats the last thing I have to do before printing. SOS

      fcwiltundefined 1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @dutti
        last edited by

        @barbarossa-cologne

        Hi,

        When you did the G32 did you see the popup message saying beg.g was running?

        Frederick

        Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

        duttiundefined 1 Reply Last reply Reply Quote 0
        • duttiundefined
          dutti @fcwilt
          last edited by

          @fcwilt
          drives to the first probe point of mesh compension and --> g32 -->
          Error: Z probe already triggered before probing move started

          fcwiltundefined 1 Reply Last reply Reply Quote 0
          • duttiundefined
            dutti
            last edited by

            6eed32cd-fd37-48f1-b4fa-ab133e2890b3-image.png

            only this message came

            1 Reply Last reply Reply Quote 0
            • fcwiltundefined
              fcwilt @dutti
              last edited by

              @barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

              @fcwilt
              drives to the first probe point of mesh compension and --> g32 -->
              Error: Z probe already triggered before probing move started

              And this was with bed.g only having the M291 command?

              Frederick

              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

              duttiundefined 1 Reply Last reply Reply Quote 0
              • duttiundefined
                dutti @fcwilt
                last edited by

                @fcwilt yes

                fcwiltundefined 1 Reply Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @dutti
                  last edited by

                  @barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

                  @fcwilt yes

                  And you didn't see the popup message about bed.g running?

                  Frederick

                  Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                  duttiundefined 1 Reply Last reply Reply Quote 0
                  • duttiundefined
                    dutti @fcwilt
                    last edited by

                    @fcwilt no. just the message you see on the screenshot.

                    fcwiltundefined 1 Reply Last reply Reply Quote 0
                    • fcwiltundefined
                      fcwilt @dutti
                      last edited by

                      @barbarossa-cologne

                      Hi,

                      Do you know how to enter commands directly into Duet Web Control using the Console page?

                      Frederick

                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                      duttiundefined 1 Reply Last reply Reply Quote 0
                      • duttiundefined
                        dutti @fcwilt
                        last edited by

                        @fcwilt yes

                        fcwiltundefined 1 Reply Last reply Reply Quote 0
                        • fcwiltundefined
                          fcwilt @dutti
                          last edited by

                          @barbarossa-cologne

                          Good.

                          Enter M98 P"bed.g" and let me know what happens.

                          Frederick

                          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                          duttiundefined 2 Replies Last reply Reply Quote 0
                          • duttiundefined
                            dutti @fcwilt
                            last edited by

                            @fcwilt said in G32 Error:´´ Z probe was not triggered during probing move´´:

                            M98 P"bed.g"

                            fd839bdf-6c9d-4a79-9679-a3ab76d5e05e-image.png

                            fcwiltundefined 1 Reply Last reply Reply Quote 0
                            • duttiundefined
                              dutti @fcwilt
                              last edited by

                              @fcwilt
                              and bed hasn´t reached the pin of the BL. I think it goes back to the same high then the bed was before the comand started.

                              1 Reply Last reply Reply Quote 0
                              • fcwiltundefined
                                fcwilt @dutti
                                last edited by

                                @barbarossa-cologne

                                Well it seems the bed.g file you edited to enter the M291 command is not the bed.g file that G32 is executing.

                                Are you editing the bed.g file that is in the system directory - the directory where the config.g file is located?

                                Frederick

                                Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                                duttiundefined 2 Replies Last reply Reply Quote 0
                                • duttiundefined
                                  dutti @fcwilt
                                  last edited by dutti

                                  @fcwilt

                                  for your question:
                                  9cb0f965-e3a6-4bdb-9517-7a2c92ef857b-image.png

                                  1 Reply Last reply Reply Quote 0
                                  • duttiundefined
                                    dutti @fcwilt
                                    last edited by

                                    @fcwilt something to do with this code in config.g?

                                    
                                    
                                    ; Z-Probe
                                    M558 P9 C"io4.in" H10 F200 T1800 ; set Z probe type to bltouch and the dive height + speeds
                                    M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
                                    G31 P25 X-20 Y-20 Z2.5 ; set Z probe trigger value, offset and trigger height
                                    M557 X15:650 Y15:650 S200 ; define mesh grid
                                    
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • fcwiltundefined
                                      fcwilt
                                      last edited by

                                      Hi,

                                      Now we are getting somewhere I think.

                                      Notice on the left hand side you have MACROS selected.

                                      Is that correct?

                                      If so the files there are not the system files the firmware is using.

                                      Those file are in the SYSTEM directory - the item below the MACROS item.

                                      Select the SYSTEM item and take a look and see what is there.

                                      Frederick

                                      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                                      duttiundefined 1 Reply Last reply Reply Quote 1
                                      • duttiundefined
                                        dutti @fcwilt
                                        last edited by

                                        @fcwilt
                                        ahhhh I know what you mean.... at the systems page my bed.g is:

                                        ; bed.g
                                        ; called to perform automatic bed compensation via G32
                                        ;
                                        ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit)
                                        M561 ; clear any bed transform
                                        G29  ; probe the bed and enable compensation
                                        
                                        
                                        
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • fcwiltundefined
                                          fcwilt
                                          last edited by

                                          Hi,

                                          Well there is the G29 that G32 has been invoking.

                                          I think you have a problem with files being in the MACROS directory rather than the SYSTEM directory.

                                          You are going to have to determine if the some or all files in the MACROS directory need to be moved to the SYSTEMS directory.

                                          If the files in the SYSTEMS directory are the ones you want to keep you should delete the files in the MACROS directory that have the same name.

                                          For example - you should have homeall.g in your SYSTEMS directory. You should NOT have homeall.g in your MACROS directory.

                                          Think you can get this sorted out?

                                          Frederick

                                          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                                          1 Reply Last reply Reply Quote 1
                                          • duttiundefined
                                            dutti
                                            last edited by

                                            yes.. I know. It was stupid....
                                            Now I took every code into the systems page.
                                            Now, I have the message ´´failed to enable endstops´´when I make a single z probe. 😞

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