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

    Filament Not Detected

    Scheduled Pinned Locked Moved
    General Discussion
    3
    6
    542
    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.
    • Modix2021undefined
      Modix2021
      last edited by

      When trying to launch a print today, after a collision 36 hours into a 40+ hour print yesterday, my print head assembly (dual BondTech extruders) would move from Home to 0, 0, 0 after the print bed would drop about 25mm. A window would open to say No Filament Detected in Extruder. Changed extruders, did numerous extrusions of filament commands which worked fine. Tried the touchscreen, went through the Change Filament commands there and wifi Duet 3D. Homed before each launch. Selected filament from Filament File, etc, etc, etc. For three hours. Tried different previously printed files. Always the same response. Are there YAT commands that could be helpful? Thanks for any insights. Dead in the water at the moment. I have a Modix Big 60 V2>V3 upgrade.

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

        @modix2021

        We need to know what kind of filament monitor you have configured.

        From the GCODE console, type M591 D0 and post the results here.

        Hey, what the heck, why not post your entire config.g here also just to save time.

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

        Modix2021undefined 1 Reply Last reply Reply Quote 0
        • Modix2021undefined
          Modix2021 @alankilian
          last edited by

          @alankilian Thank you. My tech will have to do that Friday. I will check out my filament sensor connections tomorrow by undoing and re doing. That's about my level. I just built and own the printer. And try to use it. Will hope to get more diagnostic skills as time goes on. Had four great prints 40-70 hours. Then this. Such is 3D printing.
          Best,
          Larry

          1 Reply Last reply Reply Quote 0
          • Modix2021undefined
            Modix2021
            last edited by

            Well, it ended up being Operator Error. When my tech set up the dual extruders, I did not understand filament needs to be in both filament sensors, even if there is only in one extruder which is printing. So I was only putting filament in the sensor going to the printing extruder and ignoring the other all together. So the guilty party meets me in the bathroom mirror every morning. Thanks to those that posted.

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

              @modix2021 I'm glad you got it working.

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

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

                One way to avoid that requirement for filament to be in the sensor even when not used is to add a command to enable and disable the sensor to the tool change files.

                Z-Bot CoreXY Build | Thingiverse Profile

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