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

    Fine tuning the Magnetic Filament Monitor

    Scheduled Pinned Locked Moved Solved
    Filament Monitor
    5
    19
    941
    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.
    • BlueDustundefined
      BlueDust
      last edited by BlueDust

      This is my config....
      M591 D0 P3 C3 R85:115 E6.0 L24.84 S1

      And the printer stops printing with too much movement error every other print.
      M98 P"0:/macros/Filament Sensor/Current Status"
      Duet3D magnetic filament monitor on input 3, enabled, sensitivity 24.84mm/rev, allow 85% to 115%, check every 6.0mm, version 2, measured sensitivity 24.92mm/rev, min 86% max 124% over 23348.5mm

      Any way I can fine tune this better or should I just update the config to be above the max range mentioned the last time the printer paused?
      It just seems like it is too high of a range...

      M591 D0 P3 C3 R85:125 E6.0 L24.92 S1

      Thanks!

      Fun, that 3 letter word with "u" in the middle.

      1 Reply Last reply Reply Quote 0
      • jchodakowskiundefined
        jchodakowski
        last edited by

        If I'm not mistaken that unit has older firmware on it? Should ideally be version 3 to start... the report will then tell you more about "how" sensitive it is:

        Duet3D magnetic filament monitor on input 3, enabled, sensitivity 25.20mm/rev, allow 70% to 130%, check every 3.0mm, version 3, mag 133 agc 93, no calibration data
        

        (mine hasn't gone anywhere today) what's important there are the mag and agc values. Knowing those lets you know if you're in a good bracket to start with (I had to modify my sensor housing a little) and once I got in a good reading realm, the data was more accurate and I had fewer if any false stops

        BlueDustundefined 1 Reply Last reply Reply Quote 0
        • BlueDustundefined
          BlueDust @jchodakowski
          last edited by

          @jchodakowski

          I am guessing the answer is no..... but is the sensor updateable?

          Fun, that 3 letter word with "u" in the middle.

          1 Reply Last reply Reply Quote 0
          • jchodakowskiundefined
            jchodakowski
            last edited by

            Yes, it is updateable although it's a bit of a process.

            mitchundefined 1 Reply Last reply Reply Quote 0
            • mitchundefined
              mitch @jchodakowski
              last edited by

              @jchodakowski can you point to the process to update the firmware?

              1 Reply Last reply Reply Quote 0
              • BlueDustundefined
                BlueDust
                last edited by

                bump

                how do you update the sensor?

                Fun, that 3 letter word with "u" in the middle.

                1 Reply Last reply Reply Quote 0
                • jchodakowskiundefined
                  jchodakowski
                  last edited by

                  By "a bit of a process" I meant you'll need to activate your google-fu.
                  The firmware is in github and you need a pogo-pin firmware loader - the rest should be not unlike loading firmware on other simple rt devices.

                  I have never seen "a documented process".

                  1 Reply Last reply Reply Quote 0
                  • T3P3Tonyundefined
                    T3P3Tony administrators
                    last edited by

                    I have put some documentation for this here:

                    https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_RotatingMagnetVersion?#Section_Flashing_the_firmware

                    www.duet3d.com

                    1 Reply Last reply Reply Quote 0
                    • mwolterundefined
                      mwolter
                      last edited by

                      I have three of the magnetic filament monitors and they also report over extrusion occasionally. From what I can tell, they most often report over extrusion on very short infill patterns. All three are version 2.0 and I would like to update them to 3.0 to see if this helps.

                      My question, is there a wiring diagram and STL for the pogo pins?

                      1 Reply Last reply Reply Quote 0
                      • T3P3Tonyundefined
                        T3P3Tony administrators
                        last edited by T3P3Tony

                        the pogo pins are a standard ISP 6 pin pinout:

                        efdf781a-a46a-4dbd-a6a3-7880e4d565f9-image.png

                        Updated the documentation to show this image.

                        www.duet3d.com

                        mwolterundefined 1 Reply Last reply Reply Quote 1
                        • mwolterundefined
                          mwolter @T3P3Tony
                          last edited by mwolter

                          @T3P3Tony
                          Followed the steps to program the MFM and the ELF software file in the release-44a directory on github is v1. This is the URL of the file https://github.com/Duet3D/MagneticFilamentMonitor/raw/master/Release-44a/FilamentSensor.elf.

                          As you can see in the screenshot below, it was v2 before uploading and is now v1. Did I do something improperly? Or is there a link for v3?

                          Screen Shot 2020-10-10 at 8.39.03 AM.jpg

                          Here is the output from avrdude when uploading the file

                          C:\avrdude>avrdude.exe -pt44 -cusbtiny -Uflash:w:FilamentSensor.elf:e
                          
                          avrdude.exe: AVR device initialized and ready to accept instructions
                          
                          Reading | ################################################## | 100% 0.02s
                          
                          avrdude.exe: Device signature = 0x1e9207 (probably t44)
                          avrdude.exe: NOTE: "flash" memory has been specified, an erase cycle will be performed
                                       To disable this feature, specify the -D option.
                          avrdude.exe: erasing chip
                          avrdude.exe: reading input file "FilamentSensor.elf"
                          avrdude.exe: writing flash (1826 bytes):
                          
                          Writing | ################################################## | 100% 1.41s
                          
                          avrdude.exe: 1826 bytes of flash written
                          avrdude.exe: verifying flash memory against FilamentSensor.elf:
                          avrdude.exe: load data flash data from input file FilamentSensor.elf:
                          avrdude.exe: input file FilamentSensor.elf contains 1826 bytes
                          avrdude.exe: reading on-chip flash data:
                          
                          Reading | ################################################## | 100% 1.14s
                          
                          avrdude.exe: verifying ...
                          avrdude.exe: 1826 bytes of flash verified
                          
                          avrdude.exe: safemode: Fuses OK (E:FF, H:DF, L:E2)
                          
                          avrdude.exe done.  Thank you.
                          

                          Also, receiving the following error when setting the fuses. Not sure if this is related. Are additional files needed to set the fuses?

                          C:\avrdude>avrdude.exe -p t44 -c usbtiny -U lfuse_w_0xe2_m -U hfuse_w_0xdf_m -U efuse_w_0xff_m
                          
                          avrdude.exe: AVR device initialized and ready to accept instructions
                          
                          Reading | ################################################## | 100% 0.01s
                          
                          avrdude.exe: Device signature = 0x1e9207 (probably t44)
                          avrdude.exe: NOTE: "flash" memory has been specified, an erase cycle will be performed
                                       To disable this feature, specify the -D option.
                          avrdude.exe: erasing chip
                          avrdude.exe: reading input file "lfuse_w_0xe2_m"
                          avrdude.exe: error opening lfuse_w_0xe2_m: No such file or directory
                          avrdude.exe: can't determine file format for lfuse_w_0xe2_m, specify explicitly
                          avrdude.exe: read from file 'lfuse_w_0xe2_m' failed
                          
                          avrdude.exe: safemode: Fuses OK (E:FF, H:DF, L:E2)
                          
                          avrdude.exe done.  Thank you.
                          

                          Thanks for your help.

                          1 Reply Last reply Reply Quote 0
                          • mwolterundefined
                            mwolter
                            last edited by

                            @T3P3Tony @dc42 Can you help with this? Did I do something wrong or was v1 firmware posted by mistake?

                            1 Reply Last reply Reply Quote 0
                            • T3P3Tonyundefined
                              T3P3Tony administrators
                              last edited by T3P3Tony

                              Fuse setting has an error, should be:

                              C:\avrdude\avrdude -p t44 -c usbtiny -U lfuse:w:0xe2:m -U hfuse:w:0xdf:m -U efuse:w:0xff:m

                              Looks like the colons were removed on the Dozuki site and replaced with underscores 😖 i have updated that. so should work now but I don't think that is the cause of this issue

                              please try this firmware:
                              FilamentSensor.elf

                              www.duet3d.com

                              1 Reply Last reply Reply Quote 0
                              • mwolterundefined
                                mwolter
                                last edited by

                                @T3P3Tony
                                Thank you for the reply. Unfortunately that firmware file also reports as v1. Not sure if this makes a difference or not but Release 44a and the file you uploaded are both 32,204 bytes.

                                1 Reply Last reply Reply Quote 0
                                • T3P3Tonyundefined
                                  T3P3Tony administrators
                                  last edited by

                                  I will have a look, which version of the filament monitor board do you have?

                                  www.duet3d.com

                                  1 Reply Last reply Reply Quote 0
                                  • mwolterundefined
                                    mwolter
                                    last edited by mwolter

                                    @T3P3Tony
                                    I have three and they all were purchased late 2019. This particular one was purchased November 16, 2019 from Filastruder. They all say 1.7 but I believe they are 1.7a.

                                    IMG_3176.jpg IMG_3175.jpg

                                    1 Reply Last reply Reply Quote 0
                                    • mwolterundefined
                                      mwolter
                                      last edited by

                                      @T3P3Tony Not sure if you saw the last post but would like to get this machine running again. Thanks!

                                      1 Reply Last reply Reply Quote 0
                                      • T3P3Tonyundefined
                                        T3P3Tony administrators
                                        last edited by T3P3Tony

                                        hi @mwolter yes those use the attiny44a so the version 3 firmware that I shared is right for that. I am very surprised that it shows up as version 1.

                                        I got a version 1.7 sensor from my spares and flashed the firmware to it (there are a few minor differences between 1.7 and 1.7a - none that should effect his but I may as well have exactly the setup you have).

                                        This is the response from a printer running RRF 2.0.5.1:daf18c35-7a1f-4d5c-9cd2-c8dcb34340ea-image.png

                                        Error code 6 is expected because i just plugged the board in no magnet to detect.

                                        The key point is its showing as version 3. This is the firmware I flashed

                                        FilamentSensor.elf

                                        please download and overwrite whatever firmware you have with this one ☝ and test again.

                                        Since it originally changed from version 2 to version 1, to me that indicates it is likely to be an issue with the firmware file being flashed

                                        www.duet3d.com

                                        1 Reply Last reply Reply Quote 0
                                        • mwolterundefined
                                          mwolter
                                          last edited by

                                          @T3P3Tony
                                          Thank you, that worked. I believe the issue was that no magnet was detected. Mounted the board in it's proper location (next to the magnet) and it reported v3. With it just plugged and hanging in it reported v1. This is a Duet3 no SBC on v3.1.1. Thanks again.

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