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

    Tool offset Z ignored

    Scheduled Pinned Locked Moved
    General Discussion
    4
    14
    1.9k
    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.
    • Kulitorumundefined
      Kulitorum
      last edited by

      I tried this, and that made no difference:

      [init]
      ….....
      ; layer 1, Z = 0.18
      T0
      G91
      G1 Z0.01
      G1 Z-0.01
      G90
      ; tool H0.200 W0.480
      ; skirt
      G1 X128.035 Y135.490 F9000
      G1 Z0.180 F1002
      ......
      G1 X141.305 Y158.772 E4.7989
      G92 E0
      G1 E0.0000 F600
      ; layer 2, Z = 0.18
      T1
      G91
      G1 Z0.01
      G1 Z-0.01
      G90
      ; tool H0.200 W0.480
      ; inner perimeter
      G1 X139.180 Y159.180 F9000
      G92 E0
      G1 X130.820 Y159.180 E0.3003 F1628
      G1 X130.820 Y150.820 E0.6006
      .........

      Any ideas for a workaround?

      1 Reply Last reply Reply Quote 0
      • Kulitorumundefined
        Kulitorum
        last edited by

        And now I am doing this, which still does not work:

        G90
        M82
        M106 S0
        M140 S60
        M190 S60
        G28 ; home all axes
        G10 P0 R210 S210
        G10 P1 R210 S210
        M104 S210 T0
        M104 S210 T1
        M109 S210 T0
        M109 S210 T1
        G28
        G92 E0
        G1 E-1.0000 F1800
        G1 Z1.180 F1002
        ; layer 1, Z = 0.18
        T0
        G1 Z0.180
        ; tool H0.200 W0.480
        ; skirt
        G1 X128.035 Y135.490 F9000
        G1 Z0.180 F1002
        ….................
        G1 X141.305 Y158.772 E4.7989
        G92 E0
        G1 E0.0000 F600
        ; layer 2, Z = 0.18
        T1
        G1 Z0.180
        ; tool H0.200 W0.480
        ; inner perimeter
        G1 X139.180 Y159.180 F9000
        G92 E0
        G1 X130.820 Y159.180 E0.3003 F1628
        G1 X130.820 Y150.820 E0.6006
        .............

        1 Reply Last reply Reply Quote 0
        • Kulitorumundefined
          Kulitorum
          last edited by

          Am I doing this right - this is what you ment, right? - With the G1 Z# after the tool change?

          1 Reply Last reply Reply Quote 0
          • Kulitorumundefined
            Kulitorum
            last edited by

            I just realized - the displays claims that the z position is 4.6 when printing with the second head, but the printer is not at z4.6. Again - the firmware seems to think it is at 4.6, only it is not.

            Kulitorum

            1 Reply Last reply Reply Quote 0
            • Kulitorumundefined
              Kulitorum
              last edited by

              This is worse even….

              Turns out that if you set offset Z for tool 1 to anything other then 0, that head is always printing at the same z position as the first layer. In my case 0.18mm. So every layer is printed at z=0.18m. At the same time, the displays will always show the Z-offset value, so the display in my case always shows 4.6, but it always prints (every layer) at 0.18.

              I fixed it with a metal file. My z-offset is now 0 and that works better.

              BTW, OffsetX is also not used. So I had to calibrate the U axis in homeu.g

              1 Reply Last reply Reply Quote 0
              • Michel000undefined
                Michel000
                last edited by

                Hi i build a machine with dual x carriage and i had the same problem.

                what you need to do after a tool change is add G01 Z[current z value] (in absolute coordinates) and it will work fine.
                i made small script that does this for me. it would be great if we could add
                this in the toolchange files
                with a variable for the current z height

                1 Reply Last reply Reply Quote 0
                • Kulitorumundefined
                  Kulitorum
                  last edited by

                  If you look at my last gcode, is that not exactly what I am doing?

                  Maybe you can post an example gcode? - or parts of it?`

                  Thanks.

                  1 Reply Last reply Reply Quote 0
                  • Kulitorumundefined
                    Kulitorum
                    last edited by

                    Is there any progress on this?

                    Is it fixed in 1.19?

                    1 Reply Last reply Reply Quote 0
                    • MrBlomundefined
                      MrBlom
                      last edited by

                      having same problem any update ?

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

                        Thanks for reminding me. I'll fix it in beta 7.

                        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
                        • Kulitorumundefined
                          Kulitorum
                          last edited by

                          Great! Looking forward to it 🙂

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