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

    Tool 1 offset not being applied in 3.4

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    8
    348
    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.
    • Tinchusundefined
      Tinchus
      last edited by

      Hello . I have upgraded from 3.3 stable version to 3.4 stable, and my T1 tool is not receinving its offset now. When I issue a T1 command, the tool changes and it is active, but the offset is not applied, has anything changed in 3.4 version with the G10 command

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

        @tinchus there has been no intentional change in RRF 3.4 that I think explains what you have reported.

        Please use the Object Model Browser in DWC to check that the tool offsets have been set correctly.

        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

        Tinchusundefined 2 Replies Last reply Reply Quote 0
        • Tinchusundefined
          Tinchus @dc42
          last edited by

          @dc42 Offset are there. I can see the Y=-66.95 X=0 Z=-1.6

          1 Reply Last reply Reply Quote 0
          • Tinchusundefined
            Tinchus @dc42
            last edited by

            @dc42 I have just noticed: the X and Y offsets are being applied, I can see the movments corectio when issuing a T1 command, it is the Z offset the one not being executed

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

              @tinchus please see the RRF3.4 upgrade notes. After a tool change the original Z position is no longer restored because too many users complained that it was not appropriate on their systems. You can restore the original Z position taking account of the Z offset by adding G1 Z0 R2 Fxxx at the end of the tpost file, where xxx is an appropriate feed rate for the Z axis.

              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

              Tinchusundefined 1 Reply Last reply Reply Quote 0
              • Tinchusundefined
                Tinchus @dc42
                last edited by

                @dc42 Ok, my bad for not reading that. Doc says:

                we suggest you add command G1 R2 X0 Y0 Z2 Fxxx followed by G1 R2 Z0 Fxxx to the end of your tpost#.g files,

                Why the second line of command?

                gloomyandyundefined 1 Reply Last reply Reply Quote 0
                • gloomyandyundefined
                  gloomyandy @Tinchus
                  last edited by

                  @tinchus That's doing the move in a slightly safer/better way by splitting it into two steps. The first moves to the saved X/Y point but 2 mm above it and the second move will then move vertically down to the full X/Y/Z point. By doing it that way you are less likely to hit the part or cause scarring etc by moving over it with say a nozzle that has filament built up on it.

                  1 Reply Last reply Reply Quote 0
                  • Tinchusundefined
                    Tinchus
                    last edited by

                    Question solved, thank you very much for the help

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