Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    prime the extruder

    Duet Hardware and wiring
    3
    3
    68
    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.
    • A Former User
      A Former User last edited by

      I am getting an error "bad command prime the extruder"

      unfortunately I have no idea what "prime the extruder" means. searched everywhere including this forum but found no results.

      here are the conditions:

      • I am trying to diagnose a situation where I had twice a sudden crush of the head - happening both times at the beginning of the second layer. the head dropped down very quickly and hit the bed.

      • to avoid damage in the investigation, I defined Z zero high above the bed expecting to do only air printing so I can catch the head in time if the problem repeats.

      • I removed the filament from the extruder but kept the high extruding temp on. there is no sensor for the filament (I know I should repeat the test with filament but have not had a chance)

      • under these conditions, I tried to print a different file than the one which had created the problem. it worked well (in the air!) with no crush.

      • then I tried to repeat testing but began to receive those "bad command prime the extruder" warnings.

      • additional notes:
        Error: G0/G1: target position not reachable from current position
        Error: SetPositions called when DDA ring not empty

      deckingman 1 Reply Last reply Reply Quote 0
      • deckingman
        deckingman @Guest last edited by deckingman

        @ooly My best guess is that there is something set up in the slicer to prime the extruder, but the command that the slicer uses isn't a valid RepRap firmware command. Can you post the section of the gcode file you are trying to print at the start of the second layer where the problem happens? . Or if you look through the file yourself you'll probably find the culprit. Look for any commands which come after a G1 Znn move.

        Ian
        https://somei3deas.wordpress.com/
        https://www.youtube.com/@deckingman

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

          It's probably a comment line in your slicer start gcode that is missing a ; to comment it out

          Z-Bot CoreXY Build | Thingiverse Profile

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