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

    Help with pulse-generating Filament Sensor

    Scheduled Pinned Locked Moved
    Filament Monitor
    9
    28
    2.3k
    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.
    • T3P3Tonyundefined
      T3P3Tony administrators
      last edited by

      @kordris as dc42 said, you L value is way too low:

      measured sensitivity 6.650mm/pulse

      which may be correct or may be long between pulses. depends on the sensor. what does the sensor manual say about pulses per mm?

      anyway try setting the L parameter in M591 to 6.65

      www.duet3d.com

      1 Reply Last reply Reply Quote 0
      • kordrisundefined
        kordris
        last edited by

        This is the pdf on the filament sensor, it says use 7mm on marlin for the sensor. But I dont think thats for the pulse. It doenst give much info on what other info for setting for duet stuff. Im having to figure it out for my self.
        PDF File Github Link

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

          certainly looks like 7 or 6.65 would be a good start point for the L parameter.

          www.duet3d.com

          1 Reply Last reply Reply Quote 0
          • kordrisundefined
            kordris
            last edited by

            Even if I use that, i still get no postion data. Which then leads to the printer stopping because it says theres to little movement. I dont think it's getting postion data correctly. Is there anything else should I enable in my config.g for the endstop on the extruder side. Since I'm using the extruder endstop E1. When I tried to get calibration data, it's the se way. Theres no postion point. So as soon as I go to enable the filament sensor it's going to error tell me there little or no movement.

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

              @kordris run the monitor disabled by using the M591 S0 switch for now so we can gather some data.

              looking at our previous output 6.650mm/pulse, measured minimum 7%, maximum 8% over 2334.0mm that shows that is was sensing something as it measured some minimum and maximum. What does M591 D0 show now?

              I have not tried it myself but I am not sure what position data is displayed for a pulse type sensor. it may just be movement as the pulse sensor does not send position.

              www.duet3d.com

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

                A pulse generating sensor doesn't distinguish between forward and reverse motion, so position cannot be inferred. I'll check why the firmware prints a position.

                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
                • dc42undefined
                  dc42 administrators
                  last edited by

                  I've checked the code, and I confirm that the "current position" has no meaning for a pulsed filament monitor. I'll remove it from the report in the next firmware build.

                  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
                  • kordrisundefined
                    kordris
                    last edited by

                    Ok, so when I try to run it with just those lines. I get little movement error. This is why I think that line postion has something to do with the error. Because it expecting to get the position data but its not. This is the last calibration data that I got. I guess until you fix it. I wont be able to use it.

                    Pulse-type filament monitor on endstop input 4, enabled, sensitivity 6.650mm/pulse, allowed movement 60% to 140%, check every 3.0mm, current position 0.0, measured sensitivity 12.004mm/pulse, measured minimum 0%, maximum 111% over 24.0mm
                    
                    1 Reply Last reply Reply Quote 0
                    • kordrisundefined
                      kordris
                      last edited by

                      When I change the E to 7mm distance I get a lot longer print time before it errors out before it wants to give me the problem with no little movement. So I guessing I might be close to the right settings maybe?

                      M591 D0 C4 P7 R60:140 A1 L6.65 E7 S1      ; pulse-generating sensor drive 0 Connected to C4 input, 40% to 130% tolerance, 7mm detection length
                      M591 D0                                   ; display filament sensor parameters for extruder drive 0
                      

                      This is the last one M591 D0

                      Pulse-type filament monitor on endstop input 4, enabled, sensitivity 6.650mm/pulse, allowed movement 60% to 140%, check every 7.0mm, current position 0.0, measured sensitivity 6.886mm/pulse, measured minimum 47%, maximum 104% over 185.9mm
                      
                      1 Reply Last reply Reply Quote 0
                      • kordrisundefined
                        kordris @T3P3Tony
                        last edited by

                        @T3P3Tony said in Help with pulse-generating Filament Sensor:

                        M591 S0

                        To get the Calibration data better do I just run M591 S0 ? I do I run the full M591 command with the S0 on the end like I had and then just check it with M591 D0 command.

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

                          @kordris said in Help with pulse-generating Filament Sensor:

                          @T3P3Tony said in Help with pulse-generating Filament Sensor:

                          M591 S0

                          To get the Calibration data better do I just run M591 S0 ? I do I run the full M591 command with the S0 on the end like I had and then just check it with M591 D0 command.

                          See https://duet3d.dozuki.com/Wiki/Duet3dFilamentMonitor_LaserVersion#Section_Calibration. It's written for the laser filament monitor, but it's the same for your filament monitor.

                          As it appears that your sensor only generates 1 pulse per approx. 6mm of filament, you will need to set the measurement distance (E parameter) several times greater then 6mm in order to get consistent results.

                          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

                          kordrisundefined 1 Reply Last reply Reply Quote 0
                          • kordrisundefined
                            kordris @dc42
                            last edited by

                            @dc42 Is the position data going to cause any problems or is that just going to just unrelated till you fix in the next firmware fix? I try to set the pulse to higher number. But I kept getting a error about every 5 mins telling little or no movement when I tried to enable the sensor with the S1. So Im guessing I still don't have something just right.

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

                              No, the position data being reported as zero shouldn't cause any problems. However, I can't guarantee that the code is entirely correct, because it was adapted from the code for Duet3D laser and magnetic filament monitors, so it isn't well-suited to low-resolution sensors. With a window of 60 to 140%, my guess is that you will need at least 20mm measurement length, perhaps even 25mm. A wider window will allow a shorter length, but even then the measurement length should be more than twice the extrusion length per pulse.

                              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
                              • lifeformundefined
                                lifeform
                                last edited by

                                @kordris would you like to share with me how you plug the cable of the bigtreetech smart filament sensor with duet?

                                keith89undefined 1 Reply Last reply Reply Quote 0
                                • keith89undefined
                                  keith89 @lifeform
                                  last edited by

                                  @lifeform not sure if you figured out the wiring but if you trace the wires to the sensor, there is a 4 pin connector with only 3 wires. the single wire on the end with no wire next to it is Vin. the middle wire is signal and the wire right next to that is ground.

                                  Back to the original topic, has anyone figured out the correct mm/pulse for this sensor?

                                  1 Reply Last reply Reply Quote 0
                                  • omniundefined
                                    omni
                                    last edited by

                                    Hi guys,

                                    Has anyone managed to properly set the Bigtreetech smart filament sensor to Duet meanwhile?

                                    I am just finishing my build with Duet 2, and I have connected the sensor - but still haven't done any configuring.

                                    Maybe the settings used in Marlin 2.0 can help?

                                    So if anyone of you managed to set it correctly - please help.

                                    Thanks!

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

                                      Start with https://duet3d.dozuki.com/Wiki/Gcode#Section_M591_Configure_filament_sensing.

                                      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

                                      omniundefined 1 Reply Last reply Reply Quote 0
                                      • omniundefined
                                        omni @dc42
                                        last edited by

                                        @dc42

                                        Thanks for the answer.
                                        I've tried it yesterday - but it seems that Duet is not recording any data from the sensor.

                                        I configured the sensor as following, just to log data when printing :

                                        M591 D0 P7 C"^e0stop" L0.07853981634 R90:110 E3 S0

                                        but it did not receive any data.

                                        Any ideas on what I can try is highly appreciated.

                                        Thanks again

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

                                          @omni said in Help with pulse-generating Filament Sensor:

                                          S0

                                          S0 is disabled, is it not? Try S1 maybe?

                                          Z-Bot CoreXY Build | Thingiverse Profile

                                          omniundefined 1 Reply Last reply Reply Quote 0
                                          • omniundefined
                                            omni @Phaedrux
                                            last edited by

                                            @Phaedrux
                                            Hi Phaedrux,
                                            Thanks for the reply.

                                            Yes, it is disabled - meaning it does not stop the process of printing, but it should be receiving and collecting data.
                                            It's because it only works when the printing from the SD card starts, but since it is not gathering any data if I choose S1 it would stop the print.
                                            I just wanted to see if DUET is receiving anything - and it seems it is not.

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