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

    G2 not completing before G1 starts?

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    3
    227
    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.
    • alankilianundefined
      alankilian
      last edited by alankilian

      I'm experimenting with some code like this:

      G1 X0.000000 Y101.599998 Z1.386840 E 383.897919 F 3000.000000
      G1 X0.000000 Y71.500595 Z1.386840 E 389.741913 F 3000.000000
      G2 I0.000000 J-71.500595 X0.000000 Y71.500595 E409.353699
      G60
      G1 X0.000000 Y101.599998 Z1.386840 E 403.353699 F 3000.000000
      G1 X0.000000 Y101.599998 Z1.386840 E 409.197693 F 3000.000000
      G0 R0 F3000
      

      and it seems like the G2 is not quite completing before the following G1 starts.

      Maybe I'll put a pause and see if it changes things.

      Anyway, if you could take a peek, I'd appreciate it.

      I can't guarantee you'll be able to see it, but this image shows a G2 coming around clockwise, and the G1 moves coming towards the viewer.

      See how the lower layers seem to start the G1 before the G2 finishes coming around?

      IMG_4574.jpg

      SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

      wilrikerundefined 1 Reply Last reply Reply Quote 0
      • wilrikerundefined
        wilriker @alankilian
        last edited by wilriker

        @alankilian Is it possible that the filament is not adhering to the layer below well enough and the sudden change in direction pulls it in this "diagonal" direction? Does it also happen if you print slower? Or hotter? Can you observe the print head leaving towards that spike early?

        EDIT: And of course the usual drill: which firmware version, which board?

        Manuel
        Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
        with probably always latest firmware/DWC (incl. betas or self-compiled)
        My Tool Collection

        1 Reply Last reply Reply Quote 0
        • alankilianundefined
          alankilian
          last edited by

          I tried to get a simple failing example for HOURS yesterday and I could not get it to happen using a simpler set of GCode.

          I'm thinking along the same lines you are that it might be peeling off.

          I'll try more experiments again today and post again.
          Also with my printer/firmware information. (Which is in my one other post if you're curious enough to look it up.)

          SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

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