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

    Lots of heater fault since RRF 3.4

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    5
    14
    722
    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.
    • e4dundefined
      e4d
      last edited by

      Hello, I updated to RRF 3.4 a few days ago and I now have a lot of heater fault (eg : Error: Heater 0 fault: temperature rising too slowly: expected 0.63°C/sec measured 0.10°C/sec). I already tried retuning the PID with M303 command but it doesn't change this behaviour. Is it something known in this version ? How can I correct this ?

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

        @e4d did you try tuning as a heater or a tool? what type of hotend is it? can you post a photo? does it have a sock on?

        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

        e4dundefined 1 Reply Last reply Reply Quote 0
        • e4dundefined
          e4d @jay_s_uk
          last edited by e4d

          @jay_s_uk I used M303 T0 S210, so I guess I tuned it as a tool.

          My tool is a classic E3D Toolchanger bowden tool but I don't have the sock on. Never had for a year now and it worked great so I'm not sure why this would be the cause.
          da437c8a-6c89-4eed-8a47-3ff34368b58a-image.png

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

            @e4d i would suggest not having a sock is the cause

            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 0
            • Miss Rebekahundefined
              Miss Rebekah
              last edited by

              did you store your values with config over ride or actually add it to main config? i use 3edv6 w 60 watt heater no sock never used a sock not gonna start . i have a wire brush that deploys and scrubs nozzle at start of every print sock would last long. i was over shooting by 20 degrees

              i deleted config override and added autotune code into main config works fine now. autotune will give you a line of code in the console when its done add/replace that where your heater is at in config. dunno why m500 wasn't sticking for me.

              hope this helps

              e4dundefined 1 Reply Last reply Reply Quote 0
              • e4dundefined
                e4d @Miss Rebekah
                last edited by

                @miss-rebekah Hello, I put it in the main config file. It has been rebooted several times since the begining so I'm sure it has been executed

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

                  @e4d do you get that error when heating the tool from cold, or when it is already warm (and if so, at what temperature)?

                  I just tried re-tuning one of my Bowden tool changer hot ends (with silicone sock) using RRF 3.4. This was the resulting command:

                  M307 H2 R2.077 K0.385:0.112 D5.52 E1.35 S1.00 B0 V24.1

                  The R value is a little higher than I was getting with older version (it was about 1.8 before). The other values are similar. I didn't have any problem heating it to 205C starting from 35C.

                  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

                  e4dundefined 1 Reply Last reply Reply Quote 0
                  • e4dundefined
                    e4d @dc42
                    last edited by

                    @dc42 I have it while printing at 210C. Here's my tuning :
                    M307 H1 R2.096 K0.441:0.084 D5.95 E1.35 S1.00 B0 V24.3
                    Pretty similar to your values

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

                      Thats heater 0 so the bed heater, not the tool heater?

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

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

                        @oliof so it is, my mistake. Although there is a bug in 3.4 (that was fixed in 3.4.1-RC1) where the heater 0 was being reported as having a fault regardless of which heater actually had the fault.
                        Maybe @e4d can confirm which he was heating at the time the fault occurred

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

                          @e4d said in Lots of heater fault since RRF 3.4:

                          @dc42 I have it while printing at 210C.

                          The error you reported was "temperature rising too slowly". That is usually generated only when the tool is heating up initially. So do you mean that you get the error when heating up? Or do you get a different error when printing?

                          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

                          e4dundefined 1 Reply Last reply Reply Quote 0
                          • e4dundefined
                            e4d @dc42
                            last edited by

                            @dc42 I have the error in around 1 in 10 prints when I'm actually printing. I always pre-heat the head before starting the print, the heating process don't give me error. But sometimes I have "temperature rising too slowly" error during the print (could be already an hour in).

                            oliofundefined dc42undefined 2 Replies Last reply Reply Quote 0
                            • oliofundefined
                              oliof @e4d
                              last edited by

                              @e4d do you have a screenshot of the temperature plot shown in DWC when that happens?

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

                                @e4d if you have "temperature rising too slowly" during a print that means there has been a substantial temperature drop during the print. The most likely cause is sudden additional cooling from the print cooling fan caused by the geometry of the print. A silicone sock may fix that.

                                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
                                • First post
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA