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

    Prints stuck at layer 2 with Prusa Slicer

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    158
    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.
    • bezzundefined
      bezz
      last edited by bezz

      I'm having some issues with progress estimates and the displayed current layer does not go past 2. Prints fine.
      Running RepRapFirmware 3.1.1 but the issue was also present with 2.05 before upgrading

      Update: The total layer count on this specific print is supposed to be 50. The layers started incrementing after layer ~150, so it seems like it is inserting 150 layers to the estimate and not incrementing until the end.

      Annotation 2020-05-21 174752.png
      InkedAnnotation 2020-05-21 174803_LI.jpg

      Sample snip of a layer change (neither format seems to increment the layer)

      G1 X100.134 Y54.598 E0.01299
      G1 X100.134 Y59.163 E0.15299
      M204 S1000
      G92 E0.0
      
      
      G1 Z0.800 F10800.000
      ;LAYER:3
      ;Layer 3
      G1 E-0.80000 F2100.00000
      G1 X100.398 Y50.048 F10800.000
      G1 E0.80000 F2100.00000
      G1 F3000.000
      G1 X129.157 Y50.008 E0.37187
      G1 X129.757 Y50.082 E0.00781
      G1 X132.696 Y50.897 E0.03944
      
      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        It's probably your end gcode.

        The conditional statement there has a Z move in it which is confusing the total z height. Try adding an E to the comment. as in ; E Move print head up

        You should also make sure that move is a relative movement.

        Z-Bot CoreXY Build | Thingiverse Profile

        bezzundefined 1 Reply Last reply Reply Quote 0
        • bezzundefined
          bezz @Phaedrux
          last edited by

          @Phaedrux
          Thanks. Looks like prusaslicer has a bunch of Z movements that are not at .2 intervals, which might be messing up the estimates

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