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

    G1 command not working

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    7
    1.1k
    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.
    • claustroundefined
      claustro
      last edited by

      I can move a the axis with machine control tab correctly but the printer don't respond to G! command
      If I write in console G1 X150 Y150 nothing happen
      Any idea?

      1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt
        last edited by

        Not sure.

        Are those valid co-ords for your machine?

        Did you try adding a F parameter to use a known speed?

        Frederick

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        1 Reply Last reply Reply Quote 0
        • claustroundefined
          claustro
          last edited by

          Thank you for your replay.
          Yes the coordinates are valid ( my bed is 300x300)
          I tryed to add F parameter and it works.
          But I can't understand why , shouldn't it work even without F values?

          1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt
            last edited by

            Hi,

            The F setting seems to be "sticky" - once set it stays set until something changes it.

            Try executing a movement command with a given F parameter.

            Now execute another movement command, with no F parameter, and you should be able to see that the speed is the same.

            Then execute a movement command with a different F parameter - different enough that the speed change is easily discernible.

            Now execute another movement command, again with no F parameter, and you should be able to see that the speed is the again new speed.

            At least that is how it appears to work for me.

            The Machine Control "jog" buttons appear to set the speed but what determines the value used I am not sure - something in the config.g file I would assume.

            Frederick
            .

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            1 Reply Last reply Reply Quote 0
            • T3P3Tonyundefined
              T3P3Tony administrators
              last edited by

              There is more of a discussion on how feedrate works here:

              https://duet3d.com/wiki/G-code#G0_.26_G1:_Move

              The F parameter can be set on its own line or on the same line as other variables (such a new locations to move to). Once set it is set until it is changed.

              www.duet3d.com

              1 Reply Last reply Reply Quote 0
              • claustroundefined
                claustro
                last edited by

                Thank you very much for your answer, so pratically speaking should I add a "sefoult" feedrate in config for use the G1 command without the need to declaring it?

                1 Reply Last reply Reply Quote 0
                • T3P3Tonyundefined
                  T3P3Tony administrators
                  last edited by

                  Hi Claustro, It is not normal to do that, although i don't see why it would be a problem. Slicers normally add the feed rate in at the right point so there is no need to define it.

                  www.duet3d.com

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