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

    BL-Touch - multiple problems -

    Scheduled Pinned Locked Moved Unsolved
    Firmware installation
    5
    60
    2.5k
    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
      last edited by

      @JoergS5
      I reduced the amount...

      @PaulHew
      I changed it. Same problem.....

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

        The software is homing Z without triggering anything. That´s really confusing for me..

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

          @PaulHew
          Like this?
          ; Endstops
          M574 X2 S1 P"!io3.in" ; configure active-high endstop for high end on X via pin !io3.in
          M574 Y2 S1 P"!io0.in" ; configure active-high endstop for high end on Y via pin !io0.in

          ; Z-Probe
          M558 P9 C"^io7.in" H15 F120 T1400 ; set Z probe type to bltouch and the dive height + speeds
          M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
          G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
          M557 X15:650 Y15:650 S30 ; define mesh grid

          1 Reply Last reply Reply Quote 0
          • JoergS5undefined
            JoergS5 @dutti
            last edited by JoergS5

            @barbarossa-cologne the CAN errors mean your Duet misses the expansion board.

            You should set X and Y offsets for BLTouch in G31. This is described with an example in https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+5:+Upgrades/54#s231
            G31 Z value means trigger height, 2.5 mm seens too low, please try a higher value.

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

              @JoergS5
              Done.
              In general I know About the settings. The main problem is that its not deploying or retracting. Also the software is crazily homing without triggerning the BL.
              Selftest ist working

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

                @JoergS5
                Trigger height - 4 --> not working.
                Is it a big problem that I haven´t connect the expansion board?

                JoergS5undefined 1 Reply Last reply Reply Quote 0
                • JoergS5undefined
                  JoergS5 @dutti
                  last edited by JoergS5

                  @barbarossa-cologne you can check the core position of BLTouch. This is the allen hex screw on top of the BLTouch. It is turnable by 180° to change deploy-retract distance.
                  https://www.antclabs.com/bltouch-v3
                  the picture " Correct position of Core (V3.x)" the black core's position can be changed by turning the screw with an inbus (Allen key).
                  CoreV3.jpg

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

                    @barbarossa-cologne said in BL-Touch - multiple problems -:

                    @JoergS5
                    Is it a big problem that I haven´t connect the expansion board?

                    I don't have this board, I don't know, it was only a comment about why the error message appeared.

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

                      @JoergS5
                      I tried to turn in almost 20 positions. Not working.... 😕

                      JoergS5undefined 1 Reply Last reply Reply Quote 0
                      • JoergS5undefined
                        JoergS5 @dutti
                        last edited by JoergS5

                        @barbarossa-cologne you posted the wiring as
                        Wiring:
                        BL ---------Duet
                        White - io7.in
                        Black - GND
                        Yellow - io7.out
                        Red - 5v

                        but the BLtouch has 5 cables, 2 for endstop and 3 for servo. You can check whether cabling is ok by controlling the match. In my experience the colors of the cables are sometimes wrong, so I would look the original positions on the 5-pin-connector *) on the BLTouch and compare them with yours, then check that they are connected correctly to the Duet 3 pins.

                        *) On my Smart 2.0, Smart 3.1 and Geetech clone: viewed from the back, pin down: from left to right brown-red-yellow-black-white. 3 servo + 2 endstop.

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

                          @JoergS5
                          https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_Num_3

                          I wired like this....

                          JoergS5undefined 1 Reply Last reply Reply Quote 0
                          • JoergS5undefined
                            JoergS5 @dutti
                            last edited by JoergS5

                            @barbarossa-cologne my experience is that the colors are sometimes wrong, better check the positions on the 5-pin-connector to be sure. I saw an image in the internet of the antclabs where black and white were exchanged. And the Creality ones cross a cable for the 3 pin connector.

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

                              @JoergS5
                              Without seeing the picture I thougth the same. I´ll try it on sunday.
                              Thanks for your help!!

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

                                At this point I think you should try swapping from io7 to io4 or io5 just to try a different connection. Update the config as needed to point to the new connection.

                                And if that still doesn't work I would try connecting the BLTouch directly to the board with the short leads straight from the BTouch without the extension.

                                If that still doesn't work I would get another BLtouch to test with.

                                Z-Bot CoreXY Build | Thingiverse Profile

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

                                  @Phaedrux
                                  Ok. I'll do it on Sunday!
                                  I have a cheap Chinese BL fake at home. Should I take this BL at last try?
                                  Is there any other sensor you can recommend if it's not working?
                                  The duet one?

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

                                    The BLtouch is a good probe when it's working. It's surface agnostic and a contact probe and it's quite accurate and repeatable when configured correctly. It's the most popular option for a reason.

                                    The IR Probe is also very good, but your print surface must be compatible with the IR sensor.

                                    Z-Bot CoreXY Build | Thingiverse Profile

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

                                      @Phaedrux
                                      ok. Then I´ll do everything to become the BL to work.

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

                                        @JoergS5
                                        Changing the cable order wasn´t helpful.
                                        There is also the problem that the duet homes the z axis. Also when the BL isn´t connected.
                                        @Phaedrux

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

                                          ; Z-Probe
                                          M558 P9 C"^io7.in" H15 F120 T1400 ;set Z probe type to bltouch and the dive height + speeds
                                          M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
                                          G31 P500 X20 Y100 Z4 ; set Z probe trigger value, offset and trigger height
                                          M557 X15:650 Y15:650 S60 ; define mesh grid

                                          JoergS5undefined 1 Reply Last reply Reply Quote 0
                                          • JoergS5undefined
                                            JoergS5 @dutti
                                            last edited by JoergS5

                                            @barbarossa-cologne from documentation, setting lower P for G31 seems better:
                                            G31 P25 X20 Y100 Z4

                                            and
                                            M558 P9 C"io7.in" H15 F120 T1400
                                            without the ^, because Duet 3 IO ports all have pullups already.

                                            https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Duet_3_endstop_inputs each IO of Duet 3 has already pullup resistors: "Endstop devices can be connected to the IO_0 through IO_9 connectors. Each endstop input has a 27K pullup resistor, so the endstop devices only need to sink 0.12mA."

                                            You wrote above, that removing ^ didn't work, but how did you mention, maybe it was the wrong P of G31 or some other cause.

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