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

Tool Change: Moving in axis without calling them

Scheduled Pinned Locked Moved
Beta Firmware
3
46
2.0k
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.
  • undefined
    smoki3 @Danal
    last edited by smoki3 17 Dec 2019, 04:39

    @Danal said in Tool Change: Moving in axis without calling them:

    Running:

    Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 1.1.0.5
    Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-12-02b2)

    I backed up all my pre/post/free files and copied yours in exactly. I set a Y tool1 offset of 25.

    I do not see any diagonal moves occur. T0 T1, T0 T-1 T1, no sequence I've tried produces a diagonal move.

    I DO see the final Y coordinate displayed in DWC for T1 jump from 100 to 125, when the T1 sequence ends.

    You have to set the tool offset for T0. Best you try it to set the offset for both tool in all 3 axis. It's always from the tool which is clear.

    I don't think the movement calculation is different for duet 3 and duet 2.

    Here the issue exists and on all the tool changer videos on YouTube you see it as well (moving z axis after tfree)

    1 Reply Last reply Reply Quote 0
    • undefined
      Danal
      last edited by 17 Dec 2019, 14:47

      I will give that a try. I'll just copy your tool offsets exactly.

      Delta / Kossel printer fanatic

      1 Reply Last reply Reply Quote 0
      • undefined
        Danal
        last edited by 17 Dec 2019, 15:16

        OK, I have reproduced the diagonal move.

        Interestingly enough, I then put messages (m117) and delays (G4) in the tpre1.g file... and the diagonal move WENT AWAY. Very, very, odd.

        At this moment, I'm experimenting with delays and similar to find out exactly which command causes the diagonal move.

        Delta / Kossel printer fanatic

        1 Reply Last reply Reply Quote 0
        • undefined
          Danal
          last edited by Danal 17 Dec 2019, 15:39

          OK, to summarize: With exact copies of @smoki3 files, including the pre/post/free and the tool offset, the diagonal move is reproduced on my machine. Which is a CoreXY running:

          Board: Duet 3 MB6HC (MB6HC)
          DSF Version: 1.1.0.5
          Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-12-02b2)

          With all XYZ on the main board, only tools on the expander boards.

          Some experimentation also shows:

          • A delay, such as G4 S1, positioned before any other commands in tpre1.g, stops the diagonal.

          • An M400, positioned before any other commands in tpre1.g, stops the diagonal. Note that I removed all the other M400s.

          • G53 in front of all move commands in tpre1.g has no effect, the diagonal still occurs.

          Given that this appears to be timing sensitive, it begins to make more sense why exact copies of the files are needed to reproduce.

          Anyway, I hope this helps dc42 figure out what's going on.

          Delta / Kossel printer fanatic

          undefined 1 Reply Last reply 17 Dec 2019, 16:57 Reply Quote 0
          • undefined
            smoki3 @Danal
            last edited by 17 Dec 2019, 16:57

            @Danal said in Tool Change: Moving in axis without calling them:

            OK, to summarize: With exact copies of @smoki3 files, including the pre/post/free and the tool offset, the diagonal move is reproduced on my machine. Which is a CoreXY running:

            Board: Duet 3 MB6HC (MB6HC)
            DSF Version: 1.1.0.5
            Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-12-02b2)

            With all XYZ on the main board, only tools on the expander boards.

            Some experimentation also shows:

            • A delay, such as G4 S1, positioned before any other commands in tpre1.g, stops the diagonal.

            • An M400, positioned before any other commands in tpre1.g, stops the diagonal. Note that I removed all the other M400s.

            • G53 in front of all move commands in tpre1.g has no effect, the diagonal still occurs.

            Given that this appears to be timing sensitive, it begins to make more sense why exact copies of the files are needed to reproduce.

            Anyway, I hope this helps dc42 figure out what's going on.

            Thanks for the nice analysis.

            Good point with the timing. It also makes sense. I sure @dc42 will fix it. Maybe already for 3.0RC1 🙂

            1 Reply Last reply Reply Quote 0
            • undefined
              smoki3
              last edited by 17 Dec 2019, 18:32

              So I also tried a M400 in the first line of the tpre script. Then everything is fine 🙂

              undefined 1 Reply Last reply 20 Dec 2019, 10:07 Reply Quote 0
              • undefined
                smoki3
                last edited by 20 Dec 2019, 05:55

                I also noticed that you have this diagonal movement when you dock your tool after the print. But as Danal mentioned it only happen if directly after the tfree script a G1 follows.

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators @smoki3
                  last edited by 20 Dec 2019, 10:07

                  @smoki3 said in Tool Change: Moving in axis without calling them:

                  So I also tried a M400 in the first line of the tpre script. Then everything is fine 🙂

                  Thanks, from that I think I know what is going on, and I can fix it in 3.0 release.

                  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

                  undefined 1 Reply Last reply 20 Dec 2019, 10:12 Reply Quote 1
                  • undefined
                    smoki3 @dc42
                    last edited by 20 Dec 2019, 10:12

                    @dc42 said in Tool Change: Moving in axis without calling them:

                    @smoki3 said in Tool Change: Moving in axis without calling them:

                    So I also tried a M400 in the first line of the tpre script. Then everything is fine 🙂

                    Thanks, from that I think I know what is going on, and I can fix it in 3.0 release.

                    Cool! So please also merge it to 2.xx

                    undefined 1 Reply Last reply 7 Jan 2020, 10:06 Reply Quote 0
                    • undefined
                      dc42 administrators @smoki3
                      last edited by 7 Jan 2020, 10:06

                      @smoki3, I have fixed this in the 3.0 stable release.

                      I am not planning to do any further 2.x releases, but you have an easy workaround (M400 at the start of the tpre and/or tpost file).

                      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

                      undefined 1 Reply Last reply 10 Jan 2020, 06:34 Reply Quote 0
                      • undefined
                        smoki3 @dc42
                        last edited by 10 Jan 2020, 06:34

                        @dc42 said in Tool Change: Moving in axis without calling them:

                        @smoki3, I have fixed this in the 3.0 stable release.

                        I am not planning to do any further 2.x releases, but you have an easy workaround (M400 at the start of the tpre and/or tpost file).

                        I see. Its working fine now.

                        For 2.x I don't use it. I just thought about all the tool changer users....

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