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

    [3.3-rc2/3] "Change filament" Does not work correctly

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    23
    904
    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.
    • Diamondbackundefined
      Diamondback
      last edited by

      Might have found the cause. As you can see, one of the last things my unload does is to display a blocking message that waits before the tool is allowed to cool down again.

      The error appears in the console while the blocking message is still being displayed, ie before I confirmed it.

      It reminds me of this issue: https://forum.duet3d.com/topic/23579/3-3rc3-tool-change-don-t-wait-on-m116-p/25

      @dc42 is this possibly related?

      1 Reply Last reply Reply Quote 1
      • Diamondbackundefined
        Diamondback
        last edited by

        Update, tested the RC3+7 from the linked thread, this does not solve the issue. Still sounds like a ver similar thing.

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

          @diamondback Now that 3.3 final is available can you test with that?

          Z-Bot CoreXY Build | Thingiverse Profile

          Diamondbackundefined 2 Replies Last reply Reply Quote 0
          • Diamondbackundefined
            Diamondback @Phaedrux
            last edited by Diamondback

            @phaedrux Same thing as before, here's a screenshot showing the behavior I mentioned (error from load in the console while the dialog from unload is still being displayed)
            2021-06-16_23-27-21.png

            Will remove the dialog and re-test to confirm.

            1 Reply Last reply Reply Quote 0
            • Diamondbackundefined
              Diamondback @Phaedrux
              last edited by Diamondback

              @phaedrux Ok, yea when I remove the M291 S2 from the unload script, it "works", as in it successfully executes unload and then load.
              So looks like the blocking M291 is indeed the issue here due to M701 being executed while M702 is still "active" due to the blocking dialog.

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

                Thanks. Will investigate.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 1
                • Diamondbackundefined
                  Diamondback
                  last edited by Diamondback

                  @phaedrux Any news? This is still bugging my daily 😁

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

                    @diamondback are you running in standalone or SBC mode?

                    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

                    Diamondbackundefined 1 Reply Last reply Reply Quote 0
                    • Diamondbackundefined
                      Diamondback @dc42
                      last edited by

                      @dc42 Standalone. (Duet 2 Wifi + Duex 5)

                      1 Reply Last reply Reply Quote 0
                      • Diamondbackundefined
                        Diamondback
                        last edited by

                        Any news about this @dc42 ?

                        1 Reply Last reply Reply Quote 0
                        • Diamondbackundefined
                          Diamondback
                          last edited by

                          Any news on this? Would love to get the "change" functionality back... @chrishamm @dc42

                          1 Reply Last reply Reply Quote 0
                          • Diamondbackundefined
                            Diamondback
                            last edited by

                            I don't know when exactly this got solved, but starting with one of thhe 3.4 beta builds, this is no longer an issue and works fine again. 🙂

                            1 Reply Last reply Reply Quote 1
                            • Diamondbackundefined Diamondback has marked this topic as solved
                            • First post
                              Last post
                            Unless otherwise noted, all forum content is licensed under CC-BY-SA