Duet3D Logo

    Duet3D

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

    Solved BlTouch not homing

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

      Hi,

      i hate Bltouch....

      Well that, that the Zprobe, a BlTouch gives a strange error.

      Background:

      • 2 hours ago it worked.
      • Now it works in part, or I think it's from the BlTouch
        • When you turn on the printer, it does the initial test.
        • If you send the gcodes, display, collect, test works.

      But it does NOT go.

      • When you try to do a homing, and it reaches the Z axis, it doesn't do it because it says that the "Z Probe its triggered"

      What can be?

      6/3/2022 10:53:31	Error: Probe already triggered at start of probing move
      6/3/2022 10:53:28	G28
      Error: Probe already triggered at start of probing move
      
      fcwilt 1 Reply Last reply Reply Quote 0
      • fcwilt
        fcwilt @peirof last edited by

        @peirof

        That can happen when you try to probe with the probe too close to the bed for the pin to extend all the way.

        If that is the cause you need to include a commands something like G91 G1 H2 Z-5 to move the probe away from the bed first.

        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

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

          @fcwilt the bed its at Z=50... sure, dont touch

          peirof 1 Reply Last reply Reply Quote 1
          • peirof
            peirof @peirof last edited by

            SOLVED

            I was able to solve it... obviously it was my fault, although I still don't know why... I explain the solution here in case it helps someone.

            For those who don't know, BlTOuch connects to Duet with 2 connectors, one with 2 pins and the other with 3 pins.... which in Duet becomes 4...

            Well, in the part of Bltouch, to save cables, I have joined the two connectors in 1 of 5 PINs, respecting the same order... Well NO, it has not worked for me, it was displayed, collected and did the test, but it did not do homing, it said that it was already activated, which I have indicated before.

            I have tried to separate them again, and yes, now it works, as before....

            i hate bl touch

            fcwilt 1 Reply Last reply Reply Quote 1
            • fcwilt
              fcwilt @peirof last edited by

              @peirof said in BlTouch not homing:

              SOLVED

              I was able to solve it... obviously it was my fault, although I still don't know why... I explain the solution here in case it helps someone.

              For those who don't know, BlTOuch connects to Duet with 2 connectors, one with 2 pins and the other with 3 pins.... which in Duet becomes 4...

              Well, in the part of Bltouch, to save cables, I have joined the two connectors in 1 of 5 PINs, respecting the same order... Well NO, it has not worked for me, it was displayed, collected and did the test, but it did not do homing, it said that it was already activated, which I have indicated before.

              I have tried to separate them again, and yes, now it works, as before....

              i hate bl touch

              What wire colors did you connect to what pins?

              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

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

                @fcwilt If I haven't made a mistake, the same ones that were connected when there were two cables... well, I don't know... the fact is that now it works like before...

                1 Reply Last reply Reply Quote 1
                • Topic has been marked as a question  Phaedrux Phaedrux 
                • Topic has been marked as solved  Phaedrux Phaedrux 
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA