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

Change Filament fails

Scheduled Pinned Locked Moved
Firmware installation
3
4
668
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.
  • undefined
    zerspaner_gerd
    last edited by 16 Nov 2018, 02:03

    Why does the direct filament switch over DWC
    0_1542332669445_Change Filament.jpg
    fail with this error:
    Error: M701: Unload the current filament before you attempt to load another one

    When I first unload and then load it works

    Here are my macros

    Change Filament fails.zip

    Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

    1 Reply Last reply Reply Quote 0
    • undefined
      zerspaner_gerd
      last edited by 27 Mar 2019, 20:59

      I still could not find a solution?

      DWC sends the following code:

      T0
      M702
      M701 S"GreenTEC black"
      M703
      

      After unloading comes this error:
      Error: M701: Unload the current filament before you attempt to load another one

      Does nobody else have a problem with that? (Affects only the direct filament change via DWC)

      Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 28 Mar 2019, 09:35

        Chrishamm is the expert on both filament management and DWC, so I have asked him to reply.

        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

        1 Reply Last reply Reply Quote 0
        • undefined
          chrishamm administrators
          last edited by 28 Mar 2019, 10:24

          To me it looks like M702 completes before it is actually finished, so M701 is called out-of-order which generates this message. We will investigate why this is happening.

          Duet software engineer

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