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

    G10 in Gcode start

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    10
    1.6k
    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.
    • pcsentinelundefined
      pcsentinel
      last edited by

      Hi, I am trying to get both tools to start a print by heating, with Tool 0 going to active temp and tool1 going to standby temp whilst heating at the same time. I've tried

      G28 XYZ ; home all axes
      G90 ; use absolute coordinates
      G21 ; set units to millimeters
      G1 X10 Y10
      T99
      G10 P0 S200 R170
      G10 P1 S210 R180
      M572 D0 S0.02 ; hardware pressure advance
      M572 D1 S0.02 ; hardware pressure advance
      T0
      M109 T0 S200

      but I'm getting spurious results, sometimes they heat at the same time other times tool 0 heats and then Tool 1

      Any help?

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

        I use this for a single-nozzle prints on a dual nozzle printer:

        M140 S65 ; set bed temperature
        G10 P0 S195 ; set tool 0 active temperature
        G10 P1 R150 ; set tool 1 standby temperature
        T1 ; select tool one momentarily so that it goes to standby when we select tool 0
        T0 ; select tool 0
        M116 ; wait for temperatures

        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
        • pcsentinelundefined
          pcsentinel
          last edited by

          Hi DC, yes I think the issue may be related to the other post about tool change macros, I have M116 in both tpost0 and tpost1 to wait for stabilisation, that's why I put the T99 at the start. IS there a way of disabling the tool change macros at the start of a print, I thought putting T99 might have done that.

          1 Reply Last reply Reply Quote 0
          • DjDemonDundefined
            DjDemonD
            last edited by

            This is something that needs looking at especially for switching hotends as tool change macros running when they are not wanted causes big problems. There needs to be a gcode to disable/enable tool changes or a switch to bypass running the tool change macros after an M109, G10 etc.. Or even a Tx command.

            Simon. Precision Piezo Z-Probe Technology
            www.precisionpiezo.co.uk
            PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

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

              You can change tools using a T command without executing the macros in firmware 1.19beta, and in chrishamm's fork versions 1.17e and later. See https://duet3d.com/wiki/G-code#T:_Select_Tool.

              M109 only causes a tool change if there is an explicit T parameter that is not the number of the current tool, or there is no tool selected. So if you don't want tool change macros run when you execute M109, make sure that the correct tool is selected first.

              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
              • pcsentinelundefined
                pcsentinel
                last edited by

                Hi DC, sorry being thick here, but how would I rearrange my example:

                G28 XYZ ; home all axes
                G90 ; use absolute coordinates
                G21 ; set units to millimeters
                G1 X10 Y10
                T99
                G10 P0 S200 R170
                G10 P1 S210 R180
                M572 D0 S0.02 ; hardware pressure advance
                M572 D1 S0.02 ; hardware pressure advance
                T0
                M109 T0 S200

                so that tool 0 goes to active and tool 1 goes to standby at the same time?

                1 Reply Last reply Reply Quote 0
                • pcsentinelundefined
                  pcsentinel
                  last edited by

                  DC any thoughts?

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

                    Based on the example I gave earlier, this should work

                    T99
                    G10 P1 S0 R180 ; set T1 standby temp, and active temp to 0 to avoid waiting for T1 to heat up when we select it
                    T1 ; turn on T1 so that it will go to standby when we select T0
                    G10 P0 S200 R170 ; set T0 temperatures
                    T0 ; select T0
                    G10 P1 S210 R180 ; set T1 active temperature

                    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
                    • pcsentinelundefined
                      pcsentinel
                      last edited by

                      Great thanks for the help

                      1 Reply Last reply Reply Quote 0
                      • pcsentinelundefined
                        pcsentinel
                        last edited by

                        Hi Dc, I've now put your code in and its working fine, providing (sorry) that the tools are at ambient or less than a particular value. Because I'm doing a lot of experimental prints then often Tool1 is cooling from the previous print after a cancel. With the code above it seems to still take a while until M116 thinks its stable, what's the logic it uses?

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