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

    BLTouch V3.0 Reassemble

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    49
    1.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.
    • jaurandundefined
      jaurand @Phaedrux
      last edited by

      @Phaedrux said in BLTouch V3.0 Reassemble:

      @jaurand said in BLTouch V3.0 Reassemble:

      M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves

      That betrue3d guide is a little out of date. The BLTouch has its own sensor type now, so instead of M558 P5 you should use M558 P9.

      The info here should be up to date. https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

      Yep I did catch that and is setup as P9 in my config file.

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

        @jaurand said in BLTouch V3.0 Reassemble:

        Do I need to add the following BLTouch instructions to the config.g code? (Push-pin down, alarm release, self test, etc)

        It may be a good idea to include the alarm release and pin retract commands in the config.g so that they get executed at startup. Just in case the BLTouch is too close to something at startup and the pin contacts something during the power on test and goes into an alarm state. If you try to home the printer while it's alarmed you could end up with a bed crash. It's not a bad idea to put them into the beginning of homeall.g as well.

        Z-Bot CoreXY Build | Thingiverse Profile

        jaurandundefined 1 Reply Last reply Reply Quote 1
        • jaurandundefined
          jaurand @Phaedrux
          last edited by

          @Phaedrux does M280 P7 S150 I1 need to go anywhere? or does bltouch do this already without any additional input?

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

            You don't need to use that command for the Duet.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • jaurandundefined
              jaurand
              last edited by

              https://photos.app.goo.gl/syd2vYXHDURhdonS9

              So everything works but the BLTouch blinks red with pin up. Am I missing something?

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

                It looks like it doesn't have a pin. That's probably throwing it's detection circuit for a loop.

                Z-Bot CoreXY Build | Thingiverse Profile

                jaurandundefined 1 Reply Last reply Reply Quote 0
                • jaurandundefined
                  jaurand @Phaedrux
                  last edited by

                  @Phaedrux yea the pin should be in tomorrow, as it broke in during a print. I'll report back once that is installed.

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

                    I suspect that if you send the alarm release command it would stop blinking, but I'm not sure how it will behave with no pin there for the hall effect sensor to trigger with.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    jaurandundefined 1 Reply Last reply Reply Quote 0
                    • jaurandundefined
                      jaurand @Phaedrux
                      last edited by

                      New pin installed. At start up still blinks, even with putting M280 P7 S160 I1 in the config.g file. When I run M280 P7 S160 I1 macro, BLTouch still blinks red, but when I initiate Alarm Release & Touch SW " M280 P7 S60 I1" blinking stops but z-probe indicates 1000, with pin retracted.

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

                        I'm confused. So it's working now, or not working?

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • Vetiundefined
                          Veti
                          last edited by

                          @jaurand said in BLTouch V3.0 Reassemble:

                          New pin installed. At start up still blinks,

                          when the printer start the bltouch does a self test. if it blinks it says there is a problem. maybe the new pin is not working.

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

                            The set screw on the top of the body needs to be adjusted somewhat for best operation. Try giving it a turn in either direction.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            1 Reply Last reply Reply Quote 0
                            • jaurandundefined
                              jaurand
                              last edited by

                              Moved scripts around. Originally I had them under the heading ;bltouch in the config.g, bit then moved them under endstops. Also made a separate folder for the deploy and retract macros, labeled bltouch.

                              At startup bltouch does not perform self-test, however it was not doing that before anyways,but is no longer blinking.

                              Interesting to see that location of code effected this

                              infiniteloopundefined 1 Reply Last reply Reply Quote 0
                              • infiniteloopundefined
                                infiniteloop @jaurand
                                last edited by

                                @jaurand said in BLTouch V3.0 Reassemble:

                                Also made a separate folder for the deploy and retract macros, labeled bltouch.

                                Perhaps not the best idea of the day: M401 and M402 call these macros but won’t find them - neither in your config.g nor in the folder „bltouch“. How should they know?

                                Please have a short look at the documentation: here and here.

                                jaurandundefined 1 Reply Last reply Reply Quote 1
                                • jaurandundefined
                                  jaurand @infiniteloop
                                  last edited by

                                  @infiniteloop Well I can run M401 and M402 and the pin extends and retracts....so not sure what to say but it does work

                                  infiniteloopundefined 1 Reply Last reply Reply Quote 0
                                  • infiniteloopundefined
                                    infiniteloop @jaurand
                                    last edited by

                                    @jaurand said in BLTouch V3.0 Reassemble:

                                    Well I can run M401 and M402 and the pin extends and retracts…

                                    In this case, you must have left additional copies of deployprobe.g and retractprobe.g in the sys/ directory - just where they belong. Remove the folder „bltouch“ - M401 and M402 should still work.

                                    jaurandundefined 1 Reply Last reply Reply Quote 0
                                    • jaurandundefined
                                      jaurand @infiniteloop
                                      last edited by

                                      @infiniteloop i misunderstood, I have a set of macros for deploy and retract labeled bltouch. looking under system editor, deployprobe.g and retractprobe.g are in the sys/ directory

                                      1 Reply Last reply Reply Quote 0
                                      • jaurandundefined
                                        jaurand
                                        last edited by

                                        still confused why the bltouch is not performing the self test at start up. other than that it appears to be operating correctly

                                        1 Reply Last reply Reply Quote 0
                                        • lucundefined
                                          luc
                                          last edited by

                                          I say mine, maybe it has been tried but you never know.
                                          If with the machine off you pull out the pin and then turn it on, does the Bltouch work? Yes?
                                          If yes, make the extension wiring new from scratch ... I change wires I used the Cat5 ones for network cables and above all crimp the terminals well (and with the pliers).

                                          jaurandundefined 1 Reply Last reply Reply Quote 0
                                          • jaurandundefined
                                            jaurand @luc
                                            last edited by

                                            @luc said in BLTouch V3.0 Reassemble:

                                            If with the machine off you pull out the pin and then turn it on, does the Bltouch work?

                                            The BLTouch works, just does not perform the default self test when it printer is turned on

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