Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    " Probe was not triggered during probing move" Emergency Stop?

    General Discussion
    2
    6
    86
    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.
    • PCR
      PCR last edited by

      Hello,

      i am using a D5M+ with a BLTouch.

      This is my Routine

      Home XY
      G30 in the middle of the bed
      G32 to adjust 3 leadscrews
      G29 to do a mesh

      Sometimes, when the moon is not in the right position, the leadscrews have to much difference etc
      The probe will not trigger and DWC will say " Probe was not triggered during probing move"

      Most of the time it will occure when leveling the leadscrews or at mesh bed.

      My min "problem" is that even if DWC says " Probe was not triggered during probing move" it will proceed to print the file.

      This could result in the nozzle hitting the bed or in other damage....

      So my Question is:

      • Is there a option to halt the job if the probe is not triggerd?
      fcwilt 1 Reply Last reply Reply Quote 1
      • fcwilt
        fcwilt @PCR last edited by

        @pcr

        I don't know that answer to your question. I think you can depending on the firmware. What firmware version are you using?

        Are you using the file bed.g for leveling the bed and the file mesh.g for creating the height map?

        Have you tried increasing the dive height parameter (H) in M558 when leveling the bed?

        Frederick

        Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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

          @fcwilt

          thats possible but not the solution of the poblem 😉 even if i increase H and the probe would not deploy because of some junk on the probe pin it would not solve the issue

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

            @pcr said in " Probe was not triggered during probing move" Emergency Stop?:

            @fcwilt

            thats possible but not the solution of the poblem 😉 even if i increase H and the probe would not deploy because of some junk on the probe pin it would not solve the issue

            So what firmware version are you using? That ability to check for an error I believe depends on the firmware version.

            Frederick

            Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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

              @fcwilt

              ahh sorry 3.4B5

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

                @pcr said in " Probe was not triggered during probing move" Emergency Stop?:

                @fcwilt

                ahh sorry 3.4B5

                Scroll down in this documentation to where they have an example of using result and abort during bed leveling.

                The example uses a while loop which aborts if the bed leveling fails.

                Bed Leveling Example

                Frederick

                Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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