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

    Bed Heater fault [3.4.B5]

    Scheduled Pinned Locked Moved
    Beta Firmware
    7
    21
    1.0k
    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.
    • PCRundefined
      PCR @T3P3Tony
      last edited by

      @t3p3tony yes.

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @PCR
        last edited by

        @pcr please send the M307 command that the tuning suggested

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • SIamundefined
          SIam @SIam
          last edited by

          I hope that I have not bored you, but the Heater fault does still persist in 3.4.b6
          after the PID Tuning with 3.4.b6 I got this result:

          M307 H0 B0 R0.460 C286.3 D0.90 S1.00 V24.3
          

          and here is the old known error message:

          6.11.2021, 19:31:14	Error: Heater 0 fault: at 53.2°C temperature is rising at 0.1°C/sec, well below the expected 0.3°C/sec
          

          😢😭

          Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
          Duet WiFi 1.02 or later + DueX5
          RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
          Duet WiFi Server: 1.26
          Duet Web Control 3.4.0beta4 (2021-09-27)

          T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
          • T3P3Tonyundefined
            T3P3Tony administrators @SIam
            last edited by

            @siam I am not sure why the tuning is reporting the bed can heat at 0.46 deg/s but is only heating at 0.1 deg/s can you try changing your M307 command to lower the R parameter (try R0.3).

            www.duet3d.com

            SIamundefined 1 Reply Last reply Reply Quote 0
            • SIamundefined
              SIam @T3P3Tony
              last edited by SIam

              @t3p3tony said in Bed Heater fault [3.4.B5]:

              I am not sure why the tuning is reporting the bed can heat at 0.46 deg/s but is only heating at 0.1 deg/s

              then there are two of us 😉

              If I reduce the R value, The Problem is gone, but I think that this is not the solution maybe (or better Hopefully) I'm wrong, but I think if the final rrf3.4 is out with this PID algorithm more people will have this problem.

              Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
              Duet WiFi 1.02 or later + DueX5
              RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
              Duet WiFi Server: 1.26
              Duet Web Control 3.4.0beta4 (2021-09-27)

              T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
              • T3P3Tonyundefined
                T3P3Tony administrators @SIam
                last edited by

                @siam can you post an image of the temp graph that point at which you get the fault, and let me know the target temperature. That way we can see if it's faulting when the PID may be slowing the heating rate to not overshoot, or during the main section of full power heatup.

                www.duet3d.com

                SIamundefined 1 Reply Last reply Reply Quote 0
                • SIamundefined
                  SIam @T3P3Tony
                  last edited by

                  @t3p3tony Sorry for The delay I had last week, a small working accident. I recorded a Video from The heating Process, you can find the heating error at 1:20 min. 2:40 min. and 4:10 min.

                  https://kleinersonnenschein.eu/heaterror.mp4 if you need more tests, let me know!

                  Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                  Duet WiFi 1.02 or later + DueX5
                  RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                  Duet WiFi Server: 1.26
                  Duet Web Control 3.4.0beta4 (2021-09-27)

                  T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                  • T3P3Tonyundefined
                    T3P3Tony administrators @SIam
                    last edited by

                    @siam thanks that's helpful.

                    I measured the first minute of your video the bed heater raised by 17.7 degrees in 60 seconds so that is an R of 0.295 so Changing R to 0.29 is a good idea.

                    Once you have done that, If you don't mind recording a M303 tuning for the bed that would be super helpful. I am curious why the tuning is suggesting an R of 0.46

                    www.duet3d.com

                    SIamundefined 2 Replies Last reply Reply Quote 0
                    • SIamundefined
                      SIam @T3P3Tony
                      last edited by

                      @t3p3tony with R0.29 the heating was successful! Now I have to wait for cooldown of the bed, and then I will start the PID tuning I think this I can do this tomorrow

                      Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                      Duet WiFi 1.02 or later + DueX5
                      RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                      Duet WiFi Server: 1.26
                      Duet Web Control 3.4.0beta4 (2021-09-27)

                      1 Reply Last reply Reply Quote 1
                      • SIamundefined
                        SIam @T3P3Tony
                        last edited by

                        @t3p3tony and here is a video from the PID tuning process https://kleinersonnenschein.eu/pidtuning.mp4

                        Hypercube-Evolution-Hybrid, Piezo Orion, Orbiter
                        Duet WiFi 1.02 or later + DueX5
                        RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.0beta4 (2021-09-27 11:30:36)
                        Duet WiFi Server: 1.26
                        Duet Web Control 3.4.0beta4 (2021-09-27)

                        1 Reply Last reply Reply Quote 0
                        • SIamundefined SIam referenced this topic
                        • btmcmahanundefined
                          btmcmahan
                          last edited by btmcmahan

                          Hey @SIam Did you find a solution for this? I've having the same problem with firmware 3.4.0. After reading this thread, I think I can tweak my R#, but this seems like a band-aid not a real solution. Obviously I would prefer if Auto-Tune gave me working values.

                          1 Reply Last reply Reply Quote 0
                          • Skanundefined
                            Skan
                            last edited by

                            Did anyone fix this issue? I am having the same issue with my large bed

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

                              @Skan can you start a new thread please and provide all the relevant information

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