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

    Fan0 issues, only responds to m106 when NOT printing

    Scheduled Pinned Locked Moved Solved
    General Discussion
    5
    11
    463
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Can you share a sample gcode?

      Z-Bot CoreXY Build | Thingiverse Profile

      stavrosgmtlundefined 1 Reply Last reply Reply Quote 0
      • deckingmanundefined
        deckingman @stavrosgmtl
        last edited by

        @stavrosgmtl You say the fan stopped working. Can you confirm that it used to work and that it stopped working without you making any changes to the configuration? If that is the case, then we need to concentrate on the actual gcode that you are printing or something other than a configuration issue. One other possibility is that you have an intermittent bad connection such as a poor crimp which makes or breaks as the print head moves around. So sometimes it responds to an M106 and at other times it does not.

        Ian
        https://somei3deas.wordpress.com/
        https://www.youtube.com/@deckingman

        1 Reply Last reply Reply Quote 0
        • stavrosgmtlundefined
          stavrosgmtl @Phaedrux
          last edited by

          @Phaedrux m106 works perfectly, except when printing. So before starting a print, m106 works, after a print ends, it works. The identical m106 commands in the gcode are ignored.

          So i tested the fan on one of the always on ports, it worked perfectly. I swapped fans, no change.
          I tried different duet boards as well. no change.

          I did some calibration tweaks to my config recently as I switched to rails, and upgraded to 3.44. I checked the profile gcode vs code that worked in the past. I didn't see anything there.

          I downgraded to 3.4, and no change.

          So to your point, I think I've narrowed it down to to config or firmware.

          I 'll create some small sample gcode now for a 2 layer cube, and get back to everyone.

          Karimundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
          • Karimundefined
            Karim @stavrosgmtl
            last edited by Karim

            @stavrosgmtl This works for me, I am using prusa slicer 2.5.

            
            ; Fans
            M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
            M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
            M950 F1 C"fan1" Q500                               ; create fan 1 on pin fan1 and set its frequency
            M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on
                      
            
            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator @stavrosgmtl
              last edited by

              @stavrosgmtl said in Fan0 issues, only responds to m106 when NOT printing:

              So to your point, I think I've narrowed it down to to config or firmware.

              It's possible there is an intermittent break in the wiring that only comes into effect when the print head is moving during a print?

              Z-Bot CoreXY Build | Thingiverse Profile

              stavrosgmtlundefined 1 Reply Last reply Reply Quote 0
              • stavrosgmtlundefined
                stavrosgmtl @Phaedrux
                last edited by

                @Phaedrux not a bad idea to inspect wiring. Ill do that next.

                stavrosgmtlundefined 1 Reply Last reply Reply Quote 0
                • stavrosgmtlundefined
                  stavrosgmtl @stavrosgmtl
                  last edited by

                  fans tested wiring is perfect, replaced anyway, same thing.

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

                    You can send M950 F0 and M106 P0 by themselves during a print to see what the firmware reports back as their current values.

                    Then try sending the M106 P0 S1 fan command manually during a print.

                    Z-Bot CoreXY Build | Thingiverse Profile

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

                      @stavrosgmtl perhaps something is wrong with the tool fan mapping. Please send T-1 and then test whether you can control the fan using M106 S0 and M106 S1. Then send T0 and test the fan again.

                      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

                      stavrosgmtlundefined 1 Reply Last reply Reply Quote 0
                      • stavrosgmtlundefined
                        stavrosgmtl @dc42
                        last edited by

                        @dc42 @Phaedrux I appreciate the help, I rewired the whip and voila it worked. Thank you everyone for your time. I should have rewired it from the start, the config is NOT that hard!

                        Cheers

                        1 Reply Last reply Reply Quote 0
                        • Phaedruxundefined Phaedrux marked this topic as a question
                        • Phaedruxundefined Phaedrux has marked this topic as solved
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA