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

    Extruder 0 reports too little movement

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    4
    5
    930
    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.
    • unstableTableundefined
      unstableTable
      last edited by

      New install on Ender 3, obvious under extrusion on the bed. Tried keeping extrusion clip very loose on the extruder thinking it was a failure to feed filament.

      If it's a firmware tuning issue then I'm not sure where to start?

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

        Z-Bot CoreXY Build | Thingiverse Profile

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

          You are evidently using a filament monitor. What type of filament monitor is it? How have you configured it in config.g? Have you calibrated it?

          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

          unstableTableundefined 1 Reply Last reply Reply Quote 0
          • unstableTableundefined
            unstableTable @dc42
            last edited by unstableTable

            @dc42 I am not using a filament monitor of any kind. But I suspect that I have improperly wired the board.

            I can get all 3 axes to home properly.
            Nozzle and bed get to proper temp.

            Any print stops within 2 min and "Extruder 0 reports too little movement"

            1 Reply Last reply Reply Quote 0
            • AndreSundefined
              AndreS
              last edited by

              Check for any M591 commands in your config.g
              Post your config.g
              After the print aborted type M591 D0 in the console and show the report.

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