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

    Filament monitoring while printing via USB

    Scheduled Pinned Locked Moved
    Beta Firmware
    7
    32
    1.7k
    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.
    • dc42undefined
      dc42 administrators @timoschuett
      last edited by

      @timoschuett I can look at adding a S2 option to M591 which would be like S1 but enable the filament monitor even when not printing from SD card. You might find it too annoying to have the filament monitors active during startup, filament loading etc. so you may need to use S1 in your slicer start GCode and S0 in your slicer end GCode.

      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

      timoschuettundefined oliofundefined 2 Replies Last reply Reply Quote 0
      • timoschuettundefined
        timoschuett @dc42
        last edited by

        @dc42 That sounds very promising 🙂
        If i understand correctly at this moment there is no point for me to manually enable this and a changes in the firmware need to be made from your site first?
        Can you estimate without obligation how long this takes until its ready to use?

        I think there shouldnt be any problems while filament loading and unloading etc. because (if i understand correctly) the filament monitoring is just checking printing moves (xy moves + extruding) and not move or extrude only commands.

        1 Reply Last reply Reply Quote 0
        • oliofundefined
          oliof @dc42
          last edited by

          @dc42 another option would be to implement Marlin's Host Action Commands as part of setting a Duet board to Marlin compatibility mode. Maybe that's more generally useful?

          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

          timoschuettundefined 1 Reply Last reply Reply Quote 0
          • timoschuettundefined
            timoschuett @oliof
            last edited by

            @oliof is this still needed if the host reads the outputs of the board?
            The board just needs to output a certain message in the console and the host needs to react to this event as for example repetier-server can.

            I would be totally happy with an S2 option for M591. This should resolve many problems.
            If there is a quick and dirty workaround for this, please tell me 🙂

            oliofundefined 1 Reply Last reply Reply Quote 0
            • Phaedruxundefined Phaedrux moved this topic from Filament Monitor
            • oliofundefined
              oliof @timoschuett
              last edited by

              @timoschuett The host reading output from the board is exactly what happens with host action prompts, just in a documented, known, and supported way that is already done by other firmware. Hence I suggested using that instead of inventing another scheme which would require adoption by other systems.

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

              1 Reply Last reply Reply Quote 1
              • jay_s_ukundefined jay_s_uk referenced this topic
              • benecitoundefined
                benecito
                last edited by

                Any update on when it will / might be available?

                chrishammundefined 1 Reply Last reply Reply Quote 0
                • chrishammundefined
                  chrishamm administrators @benecito
                  last edited by

                  @benecito See https://github.com/Duet3D/RepRapFirmware/issues/862

                  jaysuk created this issue in Duet3D/RepRapFirmware

                  closed [FeatureRequest]: M591 filament monitoring option for USB control #862

                  Duet software engineer

                  benecitoundefined 1 Reply Last reply Reply Quote 0
                  • benecitoundefined
                    benecito @chrishamm
                    last edited by

                    @chrishamm @jay_s_uk thanks for the suggestion! Just wanted to try it out, but did not even get that far as it's status stays at "ok" even if there is no more filament in the sensor and the print is paused on a sd print.
                    Also is there a limitation not documented if the filament monitor is connected to a CAN board (duet 3 mini slave)
                    I get information back when sending M591 but no calibration values and the print does not pause. It works when it's connected to the mainboard.

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @benecito
                      last edited by

                      @benecito the filament monitor has to be on the same board as the extruder driver.
                      there are some temporary limitations in place https://docs.duet3d.com/en/User_manual/RepRapFirmware/CAN_limitations

                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                      benecitoundefined 1 Reply Last reply Reply Quote 0
                      • benecitoundefined
                        benecito @jay_s_uk
                        last edited by

                        @jay_s_uk I know about those and the extruder driver was always on the same board as the filament monitor

                        jay_s_ukundefined 1 Reply Last reply Reply Quote 1
                        • jay_s_ukundefined
                          jay_s_uk @benecito
                          last edited by

                          @benecito looks like there are a few things that aren't reported in the OM for filament sensors, especially when over CAN-FD. https://github.com/Duet3D/RepRapFirmware/issues?q=is%3Aissue+is%3Aopen+filament

                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                          benecitoundefined 1 Reply Last reply Reply Quote 0
                          • benecitoundefined
                            benecito @jay_s_uk
                            last edited by

                            @jay_s_uk @chrishamm To be honest I don't care so much if it's reported in the OM or not. The proposed "workaround" at https://github.com/Duet3D/RepRapFirmware/issues/862 does not work if the status is always "ok". Rearranging the extruders and the filament monitors to the mainboard could be done, but is not the preferred option.

                            Is there another parameter than sensors.filamentMonitors[0].status that might help to achieve the idea of using deamon.g

                            jaysuk created this issue in Duet3D/RepRapFirmware

                            closed [FeatureRequest]: M591 filament monitoring option for USB control #862

                            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                            • jay_s_ukundefined
                              jay_s_uk @benecito
                              last edited by jay_s_uk

                              @benecito no, thats the point of my response, sensors.filamentMonitors[0].status is from the object model...
                              there isn't another way to query something

                              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                              benecitoundefined 1 Reply Last reply Reply Quote 0
                              • benecitoundefined
                                benecito @jay_s_uk
                                last edited by

                                @jay_s_uk all right - so the conclusion is, that we can't use any filament monitor as of now?

                                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                • jay_s_ukundefined
                                  jay_s_uk @benecito
                                  last edited by

                                  @benecito you can use them on the mainboard but it looks as though the reporting over CAN-FD needs work. but hopefully someone like @dc42 can chime in

                                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                  benecitoundefined 1 Reply Last reply Reply Quote 0
                                  • benecitoundefined
                                    benecito @jay_s_uk
                                    last edited by

                                    @jay_s_uk But that's my point - even when connected to the mainboard sensors.filamentMonitors[0].status will stay at "ok" when I run out of filament

                                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                    • jay_s_ukundefined
                                      jay_s_uk @benecito
                                      last edited by

                                      @benecito that may be a bug then. what firmware version are you running?

                                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                      benecitoundefined 1 Reply Last reply Reply Quote 0
                                      • benecitoundefined
                                        benecito @jay_s_uk
                                        last edited by

                                        @jay_s_uk 3.5.0 beta 3

                                        1 Reply Last reply Reply Quote 1
                                        • Phaedruxundefined Phaedrux moved this topic from Firmware wishlist
                                        • timoschuettundefined
                                          timoschuett
                                          last edited by

                                          Hi, are there any updates on how to enable filament monitoring while printing via usb? Is there a new enable mode which needs to be used?
                                          Thanks, Timo

                                          jay_s_ukundefined T3P3Tonyundefined benecitoundefined 3 Replies Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @timoschuett
                                            last edited by

                                            @timoschuett you use S2 in M591 https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing
                                            only supported in 3.5RC1 and newer

                                            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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