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

    Duet 2 with Duex 5, cannot get BLtouch to function

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    5
    19
    720
    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.
    • Macgyverundefined
      Macgyver
      last edited by

      Hi Everyone and thanks in advance for the help.

      Doing a from scratch enclosed machine and want to eventually use the 4 point bed levelling offered while using the Duex 5.

      have an issue with the BLtouch, Originally I plugged it into the 4 pin header next to the LCD, and put the ground from the Zprobe to pin 2 of the panel Duo connector. in this configuration the pin would deploy and stow twice on startup but would not get any blue light at all.

      Originally, I thought it may be a wiring issue, but I think I may have a pin assignment wrong somewhere. I am ok with moving the BLtouch over to a PWM channel on the Duex not sure what may be easier at this point.

      I eventually want to add a heated chamber to the printer so I at least what to keep a heater channel or 2 available for future expansion.

      Maybe a suggestion from you guys with more experience as to the best place for the BLtouch?

      when I tried to run a BLtouch test I was getting an error of (the P option in the M42 command is too high) I changed the P option to , error went away but no probe on the BL. Again I still think this is original wiring issue. I you need a pic o the wiring just let me know.

      BLtouch macro is here:
      M291 S3 R"BL-Touch self-test" P"The BL-Touches pin will be deployed and retracted ten times - Press OK to continue"
      M280 P7 S60 I1
      ;M280 P3 S60 I1
      M42 P8 S100 ; Turn on LED
      ;M42 P22 S100
      G4 S1
      M280 P7 S120 I1
      ;M280 P3 S120 I1
      G4 S9
      M291 R"Thank you" P"BL-Touch self-test has been accomplished" T46

      I am going to paste my configuration below, I think I may have made a mess of it.

      M569 P0 S0 ; physical drive 0 goes backward (Y)
      M569 P1 S1 ; physical drive 1 goes forwards (Y)
      M569 P2 S0 ; physical drive 2 goes forwards (X)
      M569 P3 S1 ; physical drive 3 goes forwards (E0)
      M569 P4 S1 ; Physical Drive 4 goes Forwards (E1)
      M569 P5 S1 ; Physical Drive 5 goes forward (Z-LR)
      M569 P6 S1 ; Physical Drive 6 goes forward (Z-LF)
      M569 P7 S1 ; Physical Drive 7 goes forward (Z-LF)
      M569 P8 S1 ; Physical Drive 8 goes forward (Z-LF)

      M584 X2 Y0:1 Z5:6:7:8 E3:4 ; set drive mapping

      M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400.00 E420.00:420.00 ; set steps per mm
      M566 X900.00 Y900.00 Z60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S180 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X500 Y500 Z500 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
      M574 Z1 S2 ; configure Z-probe endstop for low end on Z

      ; Z-Probe
      M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
      M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
      G31 P500 X5 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
      M557 X15:485 Y15:485 S20 ; define mesh grid

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @Macgyver
        last edited by

        @macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

        M950 S0 C"duex.pwm1" ; create servo pin 0 for BLTouch

        you're setting the servo as servo 0 in M950
        but in M280 you're using servo 7 (P7).
        You should be using P0

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        1 Reply Last reply Reply Quote 0
        • Macgyverundefined
          Macgyver
          last edited by

          HI Jay

          THanks for the reply. I've updated the test Macro file as below

          M291 S3 R"BL-Touch self-test" P"The BL-Touches pin will be deployed and retracted ten times - Press OK to continue"
          M280 P0 S60 I1
          ;M280 P3 S60 I1
          M42 P8 S100 ; Turn on LED
          ;M42 P22 S100
          G4 S1
          M280 P0 S120 I1
          ;M280 P3 S120 I1
          G4 S9
          M291 R"Thank you" P"BL-Touch self-test has been accomplished" T46

          I'm still not getting the blue light to come on when the machine is booted, therefore no pin is being deployed when I attempt to home Z.

          when I run the BLTouch test macro its tells me it's running but it actually does not. That tells me that there is a pin assigned just not the right one to trigger the probe.

          My Wiring is as follows: in the Z probe header on the Duet 2, Pin closest to the Panel Due header heading away from it, THis is a true Antlabs BLtouch, White, Brown, Yellow, Red. The Black wire is again on the gnd (2) of the conn_SD header. Maybe I have a wire messed up?

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @Macgyver
            last edited by

            @macgyver can you post a photo of your wiring?

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            Macgyverundefined 1 Reply Last reply Reply Quote 0
            • Macgyverundefined
              Macgyver @jay_s_uk
              last edited by

              @jay_s_uk

              HI Jay

              Absolutely Pic is attached

              20210811_095415.jpg

              1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk
                last edited by

                @macgyver ok, you're wiring doesn't look correct to me. I suggest you read through this link
                https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_2_WiFi_Ethernet_with_Duex_2_Duex_5_or_Expansion_Breakout_Board

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                Macgyverundefined 1 Reply Last reply Reply Quote 0
                • Macgyverundefined
                  Macgyver @jay_s_uk
                  last edited by

                  HI @jay_s_uk

                  I was suspecting that I was considering moving the 3 wires over to the PWM5 on the Deux. what I am unsure of is how do I tell the firmware that's where the BLtouch probe is located? is there a pins diagram somewhere to tell me the pin number?

                  I'm used to building marlin firmware and there is just something I'm missing in this translation to Duet.

                  I guess the question now becomes, Currently I have my config.g Its setup and S0 or pin0, how do I find out the pin number for PWM5 so I can update the S0?

                  Maybe I am missing something, Do I change the Duex.pwm1 to Duex.pwm5 to reallocate the pin. Then I lease S0 alone? sorry just losing something in firmware translation.

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

                    Here are your pin names.
                    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

                    And here is the Duex wiring diagram
                    https://duet3d.dozuki.com/Wiki/Duex_wiring_diagrams

                    @macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

                    Duex.pwm5

                    Would be correct if you want to use the PWM5 port on the duex.

                    M950 S0 C"duex.pwm5"

                    All else would stay the same.

                    Also make sure your deployprobe.g and retractprobe.g files have the correct M280 P0 commands to deploy and retract, and make sure those files are in the /sys folder. Test with M401 and M402 before trying to do a G30.

                    See here for further guidance on safely testing the probe.
                    https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Macgyverundefined 1 Reply Last reply Reply Quote 0
                    • Macgyverundefined
                      Macgyver @Phaedrux
                      last edited by

                      HI @phaedrux

                      so just to make sure that I understand, the P0 ref is just a arbraturary number that you assign to PWM5 by ref both in the same M950 command?

                      Similar in Marlin to making a ref call to the pins file, but instead of pins you call the Duex.pwm5 file?

                      instead of just fixing it trying to understand where the call is coming from that's all.

                      I think this is correct?

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

                        @macgyver basically. M950 S0 creates servo pin 0. It's an index number. You can have many servo pins. S1 S2 S3 etc. And each one has a physical pin assigned to it. In this case duex.pwm5.

                        And when you want to target that servo pin you target the index number in your servo movement command. M280 p0 or p1 p2 etc.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        Macgyverundefined 1 Reply Last reply Reply Quote 0
                        • Macgyverundefined
                          Macgyver @Phaedrux
                          last edited by

                          @phaedrux

                          that's awesome, thank you for the info,

                          I appreciate the time 2 you both.

                          1 Reply Last reply Reply Quote 1
                          • Macgyverundefined
                            Macgyver
                            last edited by

                            still have a bit of an issue, when I am doing the dynamic testing I run the M401 and M402 and now the probe deploys and retracts as it should,

                            • (note; the blue light only comes on after I deploy the first time, will not come on at boot)

                            The Probe status in the dashboard shows zero "0"
                            when I run the M401 / M402 the BLtouch status does not change

                            However when I unplug one of the white/black wire the BLtouch status the status goes to "1000"

                            this tells me that the BLtouch is triggering however the input is not being seen by the Duet.

                            My M574 is defined with a type S2, and I have removed the M307 from the config.g as I am using firmware version 3X.

                            ; Endstops
                            M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
                            M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
                            M574 Z1 S2 ; configure Z-probe endstop for low end on Z

                            ; Z-Probe
                            M950 S0 C"duex.pwm5" ; create servo pin 0 for BLTouch
                            M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
                            M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
                            G31 P500 X5 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
                            M557 X15:485 Y15:485 S23.5 ; define mesh grid

                            Phaedruxundefined 1 Reply Last reply Reply Quote 0
                            • Macgyverundefined
                              Macgyver
                              last edited by Macgyver

                              Looks like I may have it,

                              originally in my config.g I had the following
                              M574 Z1 S2 ; configure Z-probe endstop for low end on Z

                              I read in a note about version 3 firmware that the S2 switch is intended for non-Z axis only.

                              Updated the command to

                              M574 Z1 S1 ; configure Z-probe endstop for low end on Z

                              now when the probe is triggered the bed stops and pulls down as it should.

                              Still no blue light on boot up but all functionality tests appear to work. After the first deployment of the BLtouch the blue light comes on not an issue. is this something I should rectify?

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

                                @macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

                                The Probe status in the dashboard shows zero "0"
                                when I run the M401 / M402 the BLtouch status does not change

                                That's not what the trigger status is watching for. Deployment is totally separate. It will only show triggered very briefly when the pin is deployed and gets pushed back up. It will only change the display for a split second and go back to un triggered. You may not even see it there.

                                @macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

                                M574 Z1 S1 ; configure Z-probe endstop for low end on Z

                                M574 will have no effect on the probe settings. Just M558 and G31 apply to the probe.

                                @macgyver said in Duet 2 with Duex 5, cannot get BLtouch to function:

                                but all functionality tests appear to work

                                That's all that matters.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • Macgyverundefined
                                  Macgyver
                                  last edited by

                                  ok, thanks again for your time, I appreciate it.

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

                                    @macgyver is it working now?

                                    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

                                    matej1006undefined 1 Reply Last reply Reply Quote 0
                                    • matej1006undefined
                                      matej1006 @dc42
                                      last edited by

                                      @dc42 Hello sorry for stealing this topic but i have same problem and on web shows 1000 for Z-PROBE
                                      when i unplug bl touch goes to zero?

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

                                        @matej1006 said in Duet 2 with Duex 5, cannot get BLtouch to function:

                                        @dc42 Hello sorry for stealing this topic but i have same problem and on web shows 1000 for Z-PROBE
                                        when i unplug bl touch goes to zero?

                                        Please create a new thread.

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        1 Reply Last reply Reply Quote 0
                                        • Macgyverundefined
                                          Macgyver
                                          last edited by

                                          Hi Guys

                                          Sorry, I missed the update, Yes all is working now. thanks again for your help.

                                          Up to the last tests I was doing it was a coding issue, as it turns out somewhere along the line the BLtouch sensor went bad. I wrote a script to probe 10 times and report the divination. the number was never the same, or even close for that point. turned out the touch was bad.

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