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

    constant pause

    Scheduled Pinned Locked Moved Solved
    Filament Monitor
    7
    22
    1.1k
    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.
    • poohzazaundefined
      poohzaza
      last edited by

      is it a probem with logic of fliment sensing or a conection issue just speculating

      Monster Deltaundefined 1 Reply Last reply Reply Quote 0
      • Monster Deltaundefined
        Monster Delta @poohzaza
        last edited by

        @poohzaza what do you mean by logic of filament sensing?

        poohzazaundefined 1 Reply Last reply Reply Quote 0
        • poohzazaundefined
          poohzaza @Monster Delta
          last edited by

          @Monster-Delta said in constant pause:

          t do you mean by logic of filament sensing?
          you mention before that it triggered constantly maby invert that logic or the sensor is broken or recheak you config.g resume.g and pause.g

          1 Reply Last reply Reply Quote 0
          • JamesMundefined
            JamesM
            last edited by

            For an issue like this I would start by either copying the data from the SD card and re-formatting it or just get a new SD card and copy everything over from the old one. a 16gig class 10 microsd card is rather cheap.

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

              Please see the other thread about a similar issue experienced by another user with a magnetic filament monitor.

              I intend to take a detailed look at issues with magnetic filament monitors later this week.

              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

              Monster Deltaundefined 1 Reply Last reply Reply Quote 0
              • Monster Deltaundefined
                Monster Delta @dc42
                last edited by

                @dc42 did you get chance to look into this

                1 Reply Last reply Reply Quote 0
                • droftartsundefined
                  droftarts administrators
                  last edited by

                  What wiring are you using? I think the advice is to use shielded twisted pair cable, as the sensitivity of the sensor can be influenced if it runs near stepper motors and/or other cabling. There's a couple of other threads that might be worth checking:
                  https://forum.duet3d.com/topic/12182/magnetic-sensor
                  https://forum.duet3d.com/topic/3371/filament-monitor-working-well
                  https://forum.duet3d.com/topic/12005/magnetic-filament-monitor-calibration

                  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
                  • themelleundefined
                    themelle @Monster Delta
                    last edited by themelle

                    @Monster-Delta said in constant pause:

                    Any one.

                    I had quite similar issues with the rotating magnet filament monitor (see https://forum.duet3d.com/topic/11591/rotating-magnet-filament-monitor-frame-errors/22).
                    Turned out to be a faulty monitor, which I got replaced by Duet3D. The new one works as expected, throwing no more errors and putting out way more reliable data.

                    As for the wiring I can - for my setup - confirm that braided but otherwise unshielded wires do work very well. But be sure to double check the crimp connections, and redo them in case of slightest doubts.

                    1 Reply Last reply Reply Quote 0
                    • Monster Deltaundefined
                      Monster Delta
                      last edited by

                      Its not the wiring as it worka fine with the laser version. Im just about out of ideas i think I'll send it back and see if the folks at duet can figure it out

                      1 Reply Last reply Reply Quote 0
                      • DarylMcMundefined
                        DarylMcM
                        last edited by

                        I just installed our magnetic filament monitor and about 4 layers into a 400 layer print, I was optimistic, it started pausing. Tried a bunch of things but nothing worked. It would pause within seconds of resuming. I ended up setting the R parameter to 1/330 and it started printing again. Realizing that almost defeats the purpose of the monitor, I ran the 591 reports every few minutes.
                        They showed a somewhat smaller sensitivity then the 28.4 I started out with and a min variation of 2% while the max variation was around 113%.
                        I reset the L parameter on the fly with the gcode console to a value close to what it was reporting, 26.4 I believe and immediately got a pause, which I immediately resumed. Within a few layers the min variation was up to 28% and the max was 117%. After a few more layers the sensitivity was reading 27.13 and kinda holding there so again I set the L parameter on the fly and again got a pause and resumed.
                        The print is 75% done and I just changed the L parameter to 27.88 and now the min variation is 48% and the max is 112%. So it is really close to the 60% spread of the original 70/130.
                        The print show some impact at 4-6 layer area because of the the stuff I was trying, but it is not a wasted print.
                        I think the big problem is crap filament that the customer supplied and is the reason for the filament monitor purchase in the first place.
                        I guess the takeaway is patients and insist on buying your own filament.
                        I do notice that the monitor we received blinks red and green, one flash each constantly if filament is not moving. This behavior is not mentioned anywhere in the documentation, but it dose not seem to indicate anything other than no motion.
                        Don't know if this applies to the original posting, but it may help someone.

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

                          @DarylMcM said in constant pause:

                          I do notice that the monitor we received blinks red and green, one flash each constantly if filament is not moving. This behavior is not mentioned anywhere in the documentation, but it dose not seem to indicate anything other than no motion.

                          That is the expected behaviour when the filament monitor detects no motion, and the filament monitor is running version 2 firmware. The green flashes are position reports, the red ones are status reports.

                          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
                          • Monster Deltaundefined
                            Monster Delta
                            last edited by

                            replacement received and all is working as it should now

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