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

    Magnet Filament Monitor V4 - Calibration Issue

    Scheduled Pinned Locked Moved Solved
    Filament Monitor
    6
    36
    2.0k
    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.
    • Diamondbackundefined
      Diamondback @T3P3Tony
      last edited by

      @T3P3Tony That's what I assumed it should be, but it always stays constant at the very low mm count.

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

        @Diamondback I just saw you have it checking every 100mm. Try setting that to the default of 3mm

        www.duet3d.com

        Diamondbackundefined 1 Reply Last reply Reply Quote 1
        • Diamondbackundefined
          Diamondback @T3P3Tony
          last edited by

          @T3P3Tony I did that already, the first two logs in the first post use the default 3mm (ie not specified in the M591 call)

          T3P3Tonyundefined dc42undefined 2 Replies Last reply Reply Quote 0
          • T3P3Tonyundefined
            T3P3Tony administrators @Diamondback
            last edited by

            @Diamondback ahh yes I see I have not tested the monitors as much with 3.5b1 as I have with 3.4.x are you seeing the same behaviour with both firmwares?

            www.duet3d.com

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

              @Diamondback use the default 3mm unless you get a very large measured sensitivity range, in which case you could use 6mm. As you have the filament monitor a long way from the extruder drive, you are likely to need an even larger range than that.

              When running a print, the measured sensitivity should be displayed after about 10mm of filament should be extruded. The length over which calibration has been done should gradually increase and the measured sensitivity range will widen at first and then settle down.

              If you pause the print, calibration will restart from the beginning when you resume.

              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

              Diamondbackundefined 1 Reply Last reply Reply Quote 1
              • Diamondbackundefined
                Diamondback @T3P3Tony
                last edited by

                @T3P3Tony I can't run 3.4.5 on the board where the sensors are connected atm since it has a memory leak that was only fixed by @dc42 in a custom 3.5b1+ build for me.

                All filament sensors are connected to a Mini 5 in Expansion mode, same board as the extruder motors.

                1 Reply Last reply Reply Quote 0
                • Diamondbackundefined
                  Diamondback @dc42
                  last edited by

                  @dc42 Ok, that's the behavior I expected from the documentation, but unfortunately it's not what I see.
                  After it first displays some form of calibration data, it just stops there and won't calibrate any further. The reported values then stay constant for the entire duration of the print.

                  If I use the reported values in my M591 call, the sensor appears to "work", as in, it does spawn filament error events when the runout switch triggers etc. However, the calibration distance of just a few mm of course leads to incredibly inaccurate results...

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

                    @Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.

                    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

                    Diamondbackundefined 3 Replies Last reply Reply Quote 1
                    • Diamondbackundefined
                      Diamondback @dc42
                      last edited by

                      @dc42 Thank you 🙂

                      1 Reply Last reply Reply Quote 0
                      • Diamondbackundefined
                        Diamondback @dc42
                        last edited by Diamondback

                        @dc42 Some further info, yesterday my filament didn't detach from the empty spool correctly and got caught during a testprint. The active filament monitor did not catch this, it did not generate any filament error at all even after a few minutes of continuing to print.

                        Its config:

                        M591 D2 P4 C"100.io2.in" S1 L23.2 R70:150 E5
                        

                        I guess something is indeed not working?
                        (The switch part of the monitor works fine btw)

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

                          Did you send M591 to see what it reported after the fail?

                          Z-Bot CoreXY Build | Thingiverse Profile

                          Diamondbackundefined 1 Reply Last reply Reply Quote 0
                          • Diamondbackundefined
                            Diamondback @Phaedrux
                            last edited by

                            @Phaedrux Nope, unfortunately not, but I guess I can easily replicate this. I'll do that when I find some free time 🙂

                            1 Reply Last reply Reply Quote 0
                            • Diamondbackundefined
                              Diamondback @dc42
                              last edited by

                              @dc42 said in Magnet Filament Monitor V3 - Calibration Issue:

                              @Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.

                              Any news on this?

                              Diamondbackundefined 1 Reply Last reply Reply Quote 0
                              • Diamondbackundefined
                                Diamondback @Diamondback
                                last edited by

                                @Diamondback said in Magnet Filament Monitor V3 - Calibration Issue:

                                @dc42 said in Magnet Filament Monitor V3 - Calibration Issue:

                                @Diamondback thanks. It may be that there is a bug in the support for filament monitors on main boards used as expansion boards. I will add this to my investigations list.

                                Any news on this?

                                @dc42 ?

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

                                  @Diamondback please can you update your firmware to 3.5beta4 on both boards and check whether the issue still occurs. There have been some fixes in this area.

                                  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

                                  Diamondbackundefined 1 Reply Last reply Reply Quote 1
                                  • Diamondbackundefined
                                    Diamondback @dc42
                                    last edited by Diamondback

                                    @dc42 Updated everything to 3.5b4 and it seems like I can still not get anything out of my sensors other than the presence switch signal.

                                    Configuration:

                                    ;Filament sensors
                                    M591 D0 P4 C"100.io0.in" S1
                                    M591 D1 P4 C"100.io1.in" S1
                                    M591 D2 P4 C"100.io2.in" S1
                                    M591 D3 P4 C"100.io3.in" S1
                                    

                                    M591 D3 after a print using that extruder:

                                    Duet3D rotating magnet filament monitor v4 with switch on pin 100.io3.in, enabled, sensitivity 28.80mm/rev, allow 60% to 160%, check every 3.0mm, version 4, filament present, mag 132 agc 34, no calibration data
                                    

                                    (the other 3 also don't show any calibration data, but I guess that's expected since they weren't actually used during the print)

                                    Previously it was sometimes showing some data, but now it's just constantly "no calibration data".

                                    1 Reply Last reply Reply Quote 0
                                    • Diamondbackundefined
                                      Diamondback
                                      last edited by

                                      @dc42 anything more I can test or help you with to debug this? I'd really like to get my 4 sensors working beyond the switch signal 😬

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

                                        @Diamondback thanks for the reminder. I'll try to reproduce this next week before we freeze 3.5.0 rc1.

                                        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 1
                                        • patterson6undefined
                                          patterson6 @Diamondback
                                          last edited by patterson6

                                          @Diamondback When you say V4 are you referring about the v3 product on the website that's revision 3.0? The software calls v4 in gcode which is really v3.0 but the fourth revision because of 1.7, 1.7a, 1.7b, then 3.0?

                                          Or is a new filament monitor v4 on the way?

                                          patterson6undefined Diamondbackundefined 2 Replies Last reply Reply Quote 0
                                          • patterson6undefined
                                            patterson6 @patterson6
                                            last edited by

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