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.
    • 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
                          • Phaedruxundefined
                            Phaedrux Moderator @omni
                            last edited by

                            @omni Sorry. I'm not really failiar with that sensor. Perhaps best to start a new thread with your issue rather than tack on to this older thread.

                            Z-Bot CoreXY Build | Thingiverse Profile

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

                              Well it was related to the same sensor and same problem, that is why I thought it was best to just follow up on that - in case someone who was following it already resolved the problem... But thanks anyway, hope I will find a solution...

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

                                @omni A new post will get more visibility for your issue, especially with a descriptive title.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • arhiundefined
                                  arhi @omni
                                  last edited by

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

                                  Bigtreetech smart filament sensor

                                  I'm waiting on that one for a while but stuff stopped arriving 😞 so I gave up already so I'm not 100% sure, but looking at the MARLIN conf it looks like it does not generate pulses but the "smart" in the name means it internally looks at encoder data and instead of sending encoder data it calculates if / when filament is run out and switches the signal on/off so it behaves like simple switch?!?!?!? Not sure but that's what it looks like from what I read. Opening it up and checking out the electronics seems to be the only way to know for sure and hacking it to work as a pulse generator should be super simple - taking A or B pin of the encoder directly as signal pin should bypass the "smart" part inside and let duet get all the data it needs (pulses) 😄 directly from encoder.

                                  1 Reply Last reply Reply Quote 0
                                  • semi55undefined
                                    semi55
                                    last edited by semi55

                                    @omni @kordris I got mine working with the following settings:

                                    M591 D0 P7 C"ystop" L7 R80:115 E8 S1
                                    

                                    What caused problems with my setup was that I've used an endstop pin from an axis where sensorless homing was enabled. Switching to an endstop without sensorless homing solved it for me.

                                    I am using a third party controller board with a STM32 chip structure. I don't know if that has any impact on the error that I had but this might also help you if you are using an original Duet board.

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