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

    Filament Runout Sensor Strange issue in Duet 3 MB 6HC

    Scheduled Pinned Locked Moved Unsolved
    Filament Monitor
    2
    4
    272
    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.
    • selva_tviundefined
      selva_tvi
      last edited by

      Hi all

      Board - Duet 3 MB 6HC V1.02

      Firmware Version - 3.4.5

      The filament runout sensor (3 Pin end-stop switch with Enclosure) is connected to io5.

      e382481e-f0f4-4de6-8cd2-304de24d9401-image.png

      I tried with both Black and White sensors.

      Tried enabling in config.g
      M591 D0 P1 C"io5.in" S1

      Condition 1:

      1. If there is no filament also, the print starts without any warning
      2. When the print is running, Ii I insert the filament into the sensor and then remove it, it shows the filament is not present and pauses the print (I didn't enable any Filament-error. g)
      3. Then if I resume the print without loading the filament, the print continues.

      When I enter, M591 D0 in the console, it is clearly showing whether the filament is present or not.
      "Simple filament sensor on pin io5.in, enabled, output low when no filament, filament present: yes / no"

      I tried changing the config lines as below:
      M591 D0 P1 C"io5.in" S1
      M591 D0 P1 C"!^io5.in" S1 - Here the logic got inverted. But issue is same
      M591 D0 P1 C"^io5.in" S1 - Same issue

      I tried a Tachometer-based switch also. Same issue
      09bbb850-8508-4a71-8e23-573622647be8-image.png

      I installed the latest 3.5 beta version also. The same issue

      selva_tviundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined Phaedrux moved this topic from Duet Hardware and wiring
      • Phaedruxundefined Phaedrux marked this topic as a question
      • selva_tviundefined
        selva_tvi @selva_tvi
        last edited by

        @Phaedrux @dc42 Could you please solve this issue?

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

          @selva_tvi a filament error event will only be generated when there is a new filament error. I can look at changing this so that an error will also be generated when you start a new print and the sensor is reading out-of-filament. Meanwhile I suggest you add a check to your start.g file that filament is present. You could also create a filament-error.g file to handle the filament out condition during a print, using M25 to pause the print, ask the user to load filament, and then check that filament is present before resuming.

          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

          selva_tviundefined 1 Reply Last reply Reply Quote 0
          • selva_tviundefined
            selva_tvi @dc42
            last edited by selva_tvi

            @dc42 Thank you. Previously with Duet 3 Mini 5, the Filament runout works flawlessly. Even at the start of the print, if the filament is not there, it wont start the print. (Without any special codes). It was with
            firmware 3.4.0

            I tried the following code in start.g (Got from a thread):

            if sensors.filamentMonitors[0].status = "sensorError"
            echo "SensorError-0 Continuing to Print"

            if sensors.filamentMonitors[0].status != "sensorError"
            M25
            set global.beepbeep1 = 1
            M591 D0
            M118 P0 S"filament error" L2```

            It worked. When there is no filament at the start, it paused the print.
            But when i resumed it without loading the filament, it continues (it means it is not continuously checking).

            I kept the same code in resume.g, but it didnt work.

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