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

    Override heater fault error

    Scheduled Pinned Locked Moved Solved
    General Discussion
    5
    15
    553
    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.
    • Velviaundefined
      Velvia
      last edited by

      I keep getting this error since my bed is slow to heat up. PID tuned it several times. It's a 320mm AC bed of 300w, which isn't enough to heat the 380x5mm aluminium bed fast enough. It does reach it's final temp eventually, so I just need to override the error. It's a Duet 3 MB6HC.

      Homegrown, grass fed and organically built 350mm delta

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

        What error are you getting exactly?

        What does your temp graph look like?

        What are your PID values?

        What firmware version?

        Z-Bot CoreXY Build | Thingiverse Profile

        Velviaundefined 1 Reply Last reply Reply Quote 0
        • Velviaundefined
          Velvia @Phaedrux
          last edited by

          @Phaedrux

          • Error: Heater 0 fault: temperature rising too slowly: expected 0.40°C/sec measured 0.11°C/sec

          • M307 H0 R0.687 K0.500:0.000 D2.48 E1.35 S1.00 B0

          • Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.1 (2022-06-01)

          Don't have a picture of my graph right now. It's an AC heater through an SSR.

          Homegrown, grass fed and organically built 350mm delta

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

            At what point does it error out? I get the same errors myself, usually it's right near the end of the heating phase when it's nearly at temp.

            Z-Bot CoreXY Build | Thingiverse Profile

            Velviaundefined 1 Reply Last reply Reply Quote 0
            • Velviaundefined
              Velvia @Phaedrux
              last edited by

              @Phaedrux Usually during the beginning. At like 10-20% if that makes sense. Sometimes later.

              Homegrown, grass fed and organically built 350mm delta

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

                300w is a bit on the low side for a 320mm plate, but should still be able to hit temp reliably when tuned.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • Velviaundefined
                  Velvia
                  last edited by

                  Did a new PID and it now does 0.13 instead of 0.11

                  Heater 0 fault: temperature rising too slowly: expected 0.44°C/sec measured 0.13°C/sec
                  

                  I just want this to not interrupt the heating. Is there no way to disable it?

                  Homegrown, grass fed and organically built 350mm delta

                  gloomyandyundefined dc42undefined 2 Replies Last reply Reply Quote 0
                  • gloomyandyundefined
                    gloomyandy @Velvia
                    last edited by

                    @Velvia I don't think you can disable that function. However you can probably manually adjust your heater parameters (in the M307 command) to better match what actually happens see: https://docs.duet3d.com/User_manual/Connecting_hardware/Heaters_tuning You may want to decrease the R parameter, or perhaps increase the D parameter.

                    The other thing to consider is is there anything different in the environment when you tune the heater compared to when you are heating the bed for a print (so for instance is there any sort of fan that is active when printing, but not when tuning)?

                    Velviaundefined 1 Reply Last reply Reply Quote 0
                    • Velviaundefined
                      Velvia @gloomyandy
                      last edited by

                      @gloomyandy

                      Thanks for the tips. Will try playing around with those parameters. Also thinking of adding some insulation under the silicon mat.

                      Homegrown, grass fed and organically built 350mm delta

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

                        Insulation would help for sure. You may also want to try creating a macro that heats the bed in stages. It may take a bit longer, but would hopefully be a bit more reliable until we can figure out what's going on.

                        Z-Bot CoreXY Build | Thingiverse Profile

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

                          @Velvia how close to the desired temperature is it when that fault is generated?

                          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

                          Velviaundefined 1 Reply Last reply Reply Quote 0
                          • Velviaundefined
                            Velvia @dc42
                            last edited by

                            @dc42 It's random. I set it to 105, then the fault will happen at anything between 40 and 105. It helped to decrease the R parameter and increase the D parameter. Haven't had the fault since.

                            Homegrown, grass fed and organically built 350mm delta

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

                              @Velvia I'm glad you found a workaround. Reducing the R parameter reduces the heating rate that RRF expects. Increasing the D parameter delays the start of checking the heating rate.

                              You may also find it less sensitive in more recent firmware versions.

                              I'll mark this as solved, but feel free to change it back if the problem recurs.

                              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 marked this topic as a question
                              • dc42undefined dc42 has marked this topic as solved
                              • joekoundefined
                                joeko
                                last edited by

                                i have the same error with the latest firmware (3.45)

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

                                  @joeko please start a new thread. This one is marked as solved, and your situation may be significantly different,

                                  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