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

    BL Touch help after firmware 2.05 upgrade

    Scheduled Pinned Locked Moved Solved
    Third-party add-ons
    5
    14
    599
    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.
    • 87ninefiveoneundefined
      87ninefiveone
      last edited by 87ninefiveone

      Deployprobe.g has M280 P7 S10 I0, but I found a mistake in the retractprobe.g file which had M280 P7 S90 I1 instead of I0. I suspect this was part of the issue.

      I corrected this, changed the M558 command to use P9 and moved the wiring connections from E1 STOP to the Z PROBE connections. I'm running a bed leveling routine now, so we'll see how it goes. I'll also check the M401 and M402 commands once it completes.

      1 Reply Last reply Reply Quote 0
      • 87ninefiveoneundefined
        87ninefiveone
        last edited by 87ninefiveone

        M401 and M402 commands are working and I was able to get through two bed leveling routines without an issue. Looks like it's now working as intended.

        One more quick question, is it now best practice to use M401 and M402 command for probe deployment/retraction in macros and startup g-code or is using M280 commands still okay? Just curious if I need to edit my macros and .g files to use the M401/402 commands so the board can properly track the probe state?

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

          @87ninefiveone said in BL Touch help after firmware 2.05 upgrade:

          One more quick question, is it now best practice to use M401 and M402 command for probe deployment/retraction in macros and startup g-code or is using M280 commands still okay? Just curious if I need to edit my macros and .g files to use the M401/402 commands so the board can properly track the probe state?

          Use M401 and M402. That allows the firmware to track the deployment state.

          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

          87ninefiveoneundefined DIY-O-Sphereundefined 2 Replies Last reply Reply Quote 1
          • 87ninefiveoneundefined
            87ninefiveone @dc42
            last edited by

            @dc42 Will do. Thank you for your help!

            1 Reply Last reply Reply Quote 0
            • DIY-O-Sphereundefined
              DIY-O-Sphere @dc42
              last edited by

              @dc42 said in BL Touch help after firmware 2.05 upgrade:

              That allows the firmware to track the deployment state.

              Is this also tracked in G30?

              (UTC+1)

              Phaedruxundefined 1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator @DIY-O-Sphere
                last edited by

                @DIY-O-Sphere said in BL Touch help after firmware 2.05 upgrade:

                @dc42 said in BL Touch help after firmware 2.05 upgrade:

                That allows the firmware to track the deployment state.

                Is this also tracked in G30?

                Yes. When using the P9 probe type for BLTouch all of the commands that require the pin to be deployed keep track of the pin state.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • jens55undefined
                  jens55
                  last edited by

                  Ran some test on the BLtouch operation - it drops the probe, it lifts the probe, it self tests .... but for some reason the operation of 'cancel alarm and lift probe' does not run ....

                  This runs:
                  M280 P0 S90 ; Send PWM channel 7 the S90 (angle) command
                  This does NOT run:
                  M280 P0 S160; Alarm Release and Push-Pin UP

                  I don't get why this is happening ?

                  1 Reply Last reply Reply Quote 0
                  • DIY-O-Sphereundefined
                    DIY-O-Sphere
                    last edited by

                    This will release a "blinking" Bltouch. It doesn't take effect in normal status.

                    (UTC+1)

                    1 Reply Last reply Reply Quote 0
                    • jens55undefined
                      jens55
                      last edited by

                      Hmmm .... will do more tests
                      Thanks!

                      1 Reply Last reply Reply Quote 0
                      • jens55undefined
                        jens55
                        last edited by

                        Yup, you are correct, if it blinks then the command works.
                        Still got some gremlins here .....

                        Ok, I got it figured out. While the macros for the bltouch all worked, the 'retractprobe.g' had an error in it so it was behaving strangely

                        Thanks!

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