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

    Z Probe missing trigger point

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    11
    1.8k
    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.
    • Jaranundefined
      Jaran
      last edited by

      Could this be related to signal interference? I got all my wires from the duet wifi and up to the extruder going side by side the whole way.

      When im doing a G29 command while the printer has not started printing anything it usually manages to get through the 9 points without failing. However when a print is started and the heat bed and extruder is active it rarely get past the third or fourth probe point.

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        That might be due to interference, especially if it is triggering too early. Unfortunately the BLTouch is closed source, so there is no schematic that I can look at to determine how sensitive to interference it is. But if you have it connected to the Z probe input, adding a resistor of about 10K between the Z probe connector IN and 3V3 pins might help. Increasing the P parameter in the G31 command would also make it less susceptible to interference.

        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
        • Jaranundefined
          Jaran
          last edited by

          @dc42:

          That might be due to interference, especially if it is triggering too early. Unfortunately the BLTouch is closed source, so there is no schematic that I can look at to determine how sensitive to interference it is. But if you have it connected to the Z probe input, adding a resistor of about 10K between the Z probe connector IN and 3V3 pins might help. Increasing the P parameter in the G31 command would also make it less susceptible to interference.

          I have not added the 10k resistor so I can give that a shot. If that does not help then I will try to isolate the cables. Thanks for the input!

          1 Reply Last reply Reply Quote 0
          • Jaranundefined
            Jaran
            last edited by

            @dc42:

            That might be due to interference, especially if it is triggering too early. Unfortunately the BLTouch is closed source, so there is no schematic that I can look at to determine how sensitive to interference it is. But if you have it connected to the Z probe input, adding a resistor of about 10K between the Z probe connector IN and 3V3 pins might help. Increasing the P parameter in the G31 command would also make it less susceptible to interference.

            When you say add a 10k resistor to the IN connector, do you mean between the probe itself and the pin or IN between ground?

            1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators
              last edited by

              I mean between the IN pin and the 3V3 pin.

              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
              • Jaranundefined
                Jaran
                last edited by

                @dc42:

                I mean between the IN pin and the 3V3 pin.

                Oh, was not familiar with "3V3" pin, but a google search said that would be the 3.3v pin. All the pins on the board is 5v that it is connected to, so the resistor would be between z probe IN and the ground next to it? (tried that without any diffrence)

                I also came over this: https://plus.google.com/113792662927481823969/posts/Sfig2jd4bvM

                Seems like the ground on the z probe connector is not attached. Is that a possibility too? I guess I got some more trial and error to do. Will post back as soon as I get somewhere.

                Edit: A little more trial and error has been done. Neither of the resistors I have tried made any diffrence. Earlier I was able to finish probing from time to time, but now it seems like the probe won't manage to even track one hit without failing. I noticed that when I retract the probe I can hear three small buzzes before it releasing the alarm.

                I might try to reset all settings and do it from scratch on another port just to be sure that its not a mistake I have made.

                1 Reply Last reply Reply Quote 0
                • Jaranundefined
                  Jaran
                  last edited by

                  Now it seems like my 3DTouch is not tracking any signal what so ever. It can not get through any probing points at all. The z probe value never changes to "1000" upon triggering it. Deploying and retracting works, however when retracting the probe goes into alarm mode. Could my probe be defective?

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators
                    last edited by

                    Does the Bltouch documentation describe what conditions put it in alarm mode? It's closed source, so otherwise it's hard to know.

                    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
                    • Jaranundefined
                      Jaran
                      last edited by

                      @dc42:

                      Does the Bltouch documentation describe what conditions put it in alarm mode? It's closed source, so otherwise it's hard to know.

                      Not as far as I know. Can't seem to find anything on it. As the probe was working from time to time earlier with the same setup I would assume its the probe. Its not triggering at all unless its in the alarm mode.

                      Will probably buy a new probe soon ish, and this time an original bltouch. Got too much finals starting in my studies now so it might take some time before I post back with an update!

                      1 Reply Last reply Reply Quote 0
                      • Jaranundefined
                        Jaran
                        last edited by

                        Alright, so it looks like it was an issue with the 3DTouch. I bought a BLTouch and got it installed today. So far no steps have been skipped!

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