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

    3.2b1 issue - BLTouch toolboard not responding to G30

    Scheduled Pinned Locked Moved
    Beta Firmware
    5
    12
    453
    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.
    • dc42undefined
      dc42 administrators
      last edited by dc42

      I just re-tested BLTouch (v3.0, genuine) on tool board, and it's working for me. In config.g I have:

      M558 K0 P9 C"121.io0.in"
      M950 S0 C"121.io0.out"

      In deployprobe.g:

      M280 P0 S10

      In retractprobe.g:

      M280 P0 S90

      Self-test at power up is working too.

      PS - I am using 24V power to the tool board. Are you too?

      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

      oozeBotundefined 1 Reply Last reply Reply Quote 0
      • oozeBotundefined
        oozeBot @dc42
        last edited by

        @dc42 Thank you, David. I'm pulling a new Duet3 and toolboard out of the box to run another test now and will report back. Note that our configs are identical and yes, we are using Meanwell 24v power supplies. The only difference I see is we have BLTouch v3.1 (genuine). I am not sure the differences between 3.0 and 3.1 as I've not been able to find any clear info on the web..

        1 Reply Last reply Reply Quote 0
        • oozeBotundefined
          oozeBot
          last edited by

          Update - brand new Duet3, RPi, toolboard, and BLTouch v3.1 (all fresh out of the box) upgraded to 3.2b1. G30 is working correctly.

          I will update the same machine we tested yesterday again following the same upgrade path I just took and report back. I am in hopes this was just user error on our end.

          However, I'd like to point out that the BLTouch v3.1 is not self-testing upon startup like @dc42 was able to achieve without the work-around identified in my other thread. I will test with a capacitor soon..

          Phaedruxundefined 1 Reply Last reply Reply Quote 0
          • oozeBotundefined
            oozeBot
            last edited by

            Last response - this was user error on our end as we apparently botched the upgrade.. I apologize for the false alarm!

            We will let this thread die and respond back to the BLTouch workaround thread after testing with capacitors like suggested as that is still occurring.

            A Former User? 1 Reply Last reply Reply Quote 0
            • A Former User?
              A Former User @oozeBot
              last edited by

              @oozeBot

              As the old saying goes: measure twice, cut once.......

              oozeBotundefined whopping pochardundefined 2 Replies Last reply Reply Quote 0
              • oozeBotundefined
                oozeBot @A Former User
                last edited by

                @CaLviNx well, we did actually.. we just botched the upgrade in the same way twice. Doh! Chris Hamm posted a cleaner upgrade procedure in a different thread that allowed us to successfully upgrade.

                1 Reply Last reply Reply Quote 0
                • whopping pochardundefined
                  whopping pochard @A Former User
                  last edited by

                  @CaLviNx It just struck me that the equivalent advice for additive manufacturing might legitimately be, "measure once, print twice"! 😂

                  A Former User? 1 Reply Last reply Reply Quote 0
                  • A Former User?
                    A Former User @whopping pochard
                    last edited by A Former User

                    @whopping-pochard that's usually how it goes right enough

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

                      @oozeBot said in 3.2b1 issue - BLTouch toolboard not responding to G30:

                      However, I'd like to point out that the BLTouch v3.1 is not self-testing upon startup

                      This has been reported once before with the 3.1 Bltouch. Not sure what has changed in it's logic or how it deals with 3.3 and 5v.

                      Z-Bot CoreXY Build | Thingiverse Profile

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

                        @Phaedrux said in 3.2b1 issue - BLTouch toolboard not responding to G30:

                        @oozeBot said in 3.2b1 issue - BLTouch toolboard not responding to G30:

                        However, I'd like to point out that the BLTouch v3.1 is not self-testing upon startup

                        This has been reported once before with the 3.1 Bltouch. Not sure what has changed in it's logic or how it deals with 3.3 and 5v.

                        The tool board uses 5V for everything except the filament monitor input (IO1), so 3.3V vs. 5V is not relevant.

                        My best guess is that the self-test issue is connected with available power. The tool board has less 5V power available than a full controller board has; however it should be plenty enough to power a BLTouch.

                        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
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA