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

    Clog detector make random filament missing errors

    Scheduled Pinned Locked Moved
    MultiAxis Printing
    5
    14
    532
    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.
    • David Piskaundefined
      David Piska
      last edited by

      Hello,
      I have Modix3D large printer with Duet2 wifi electronic. Small models can be printed perfect, but in large models, there is a issue:
      "Printing paused for filament change at X374.6 Y330.2 Z1.9 U680.5"

      Issue is happend random after ( 20 mins, 2h or 6h) I am going one month around it. Try change filament brands, different teflon tubes to reduce filament friction, calibrations, remove clog detector wires separately avoid EMC problems and SW setting the clog detector sensitivity.

      Now in config file is very large volatility and 500mm for detection (was going from small steps to this numbers)

      In the console: M591 D0
      Pulse-type filament monitor on pin e0stop, enabled, sensitivity 3.315mm/pulse, allowed movement 3% to 800%, check every 500.0mm, measured sensitivity 3.321mm/pulse, measured minimum 99%, maximum 100% over 49025.8mm

      In my opinion, electronic detects in real very small difference 99-100%, in settings is 3-800% but errors still happend sometimes.

      Is here any tool or macro to save every pulse of the clog detector and time for analysis, or any other way whre can be the problem?

      Thank you, David.

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @David Piska
        last edited by

        @David-Piska what firmware version are you running?
        Can you post your config files?

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        David Piskaundefined 1 Reply Last reply Reply Quote 0
        • David Piskaundefined
          David Piska @jay_s_uk
          last edited by

          @jay_s_uk Here it is all files from system directory, please download here:
          https://www.uschovna.cz/zasilka/QD5MN3YUBZNF7ZA7-7JW/
          , thank you

          gloomyandyundefined 1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy @David Piska
            last edited by

            @David-Piska You still haven't told us what version of RRF you are using (run the M115 command and post the output from that here).

            David Piskaundefined 1 Reply Last reply Reply Quote 0
            • David Piskaundefined
              David Piska @gloomyandy
              last edited by

              @gloomyandy
              M115
              FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.5 ELECTRONICS: Duet WiFi 1.02 or later + DueX5v0.11 FIRMWARE_DATE: 2022-11-30 19:36:12

              1 Reply Last reply Reply Quote 0
              • David Piskaundefined
                David Piska
                last edited by

                I have 1100mm long tube for filament, now filament trully ends, led stops blink, but clog detector did not catch it. (in config is 500mm) for stop.
                Now I have camera focused to led and printer. will send more info, when stops again.

                1 Reply Last reply Reply Quote 0
                • David Piskaundefined
                  David Piska
                  last edited by David Piska

                  Dear Friends,
                  I am sending video of this issue here
                  https://www.uschovna.cz/zasilka/QDFV7JC2HA6K52XX-7FM/

                  Printer paused at 19:33:50, please see log. Led of the clog detector is still blinking and is in left up corner.

                  cf2b937e-bce2-4159-88e9-70592e9bdec1-image.png

                  any ideas? It will be very helpful, thank you all very much, David.

                  David Piskaundefined 1 Reply Last reply Reply Quote 0
                  • David Piskaundefined
                    David Piska @David Piska
                    last edited by

                    @David-Piska Changed config file to "normal" values and happend again at 20:33:38
                    Video: https://www.uschovna.cz/zasilka/QDPMEM7YUU23XIWP-YLN/

                    9e41188e-810d-4ec8-98ed-2e5ef6d793cf-image.png

                    Is here any opportunity how to log each pulse of clog detector? Checking log will eliminate HW problem.

                    Much appreciate your help. David.

                    David Piskaundefined 1 Reply Last reply Reply Quote 0
                    • David Piskaundefined
                      David Piska @David Piska
                      last edited by

                      One note, in new settings "checked every 100.0mm" - stops after 450mm filament lenght when i was cut it for checking if clog detector works. Thank you!

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

                        You may want to check directly with Modix support on the performance of the filament monitor and how it's expected to be configured.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • jay_s_ukundefined
                          jay_s_uk @David Piska
                          last edited by

                          @David-Piska i would also suggest updating to 3.5.2 as there was a couple of changes to improve filament monitor diagnostics

                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                          David Piskaundefined 1 Reply Last reply Reply Quote 0
                          • David Piskaundefined
                            David Piska @jay_s_uk
                            last edited by

                            @jay_s_uk thank you, will update it after 6 days when print finished and send a report. THX,d.

                            David Piskaundefined 1 Reply Last reply Reply Quote 1
                            • David Piskaundefined
                              David Piska @David Piska
                              last edited by

                              Dear All - thanks to Modix3D support for idea to check M600 command.

                              "Automatic color change" was set by default in PrusaSlicer - dont know why?
                              After disabling in preferences, GCODE is without M600 - thats probably the goal - thank you and will let you know later in next print.

                              1500d029-2831-4cf0-9d70-3aefa08c5c77-image.png

                              droftartsundefined 1 Reply Last reply Reply Quote 1
                              • droftartsundefined
                                droftarts administrators @David Piska
                                last edited by

                                @David-Piska said in Clog detector make random filament missing errors:

                                thanks to Modix3D support for idea to check M600 command.

                                Good catch! Sometimes the simplest answer is the best. Often we look for more complicated reasons! The 'error' (not an error, it's doing what it's told to do) message should have been the clue...

                                Ian

                                Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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