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

    Heater fault after PIDtuning/firmware update.

    Scheduled Pinned Locked Moved
    Firmware installation
    3
    13
    396
    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
      last edited by

      Interesting, because theoretically the results should be the same provided that the fan was off when you ran the second command; except that the first command will generate the second C parameter.

      Temperature "rising more slowly" suggests that the auto tuning has over-estimated the heating rate. The first command produced 3.033 vs 2.819 for the second. So you may get good results if you take the first set of M307 parameters but use the R value from the second set.

      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
      • TSchmeltzerundefined
        TSchmeltzer
        last edited by TSchmeltzer

        Thank you David, that seems to work. Did a small print for 10 min and the temperature were stable.

        Just noticed this when running M501:
        Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 213C
        Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 636C

        Should I do something about this?

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

          @TSchmeltzer https://duet3d.dozuki.com/Wiki/FAQ#Section_M307_Heater_1_appears_to_be_over_powered_If_left_on_at_full_power_its_temperature_is_predicted_to_reach_521C

          It's a warning to take precautions.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • TSchmeltzerundefined
            TSchmeltzer
            last edited by

            Thanks 😁 completely missed that when trying to figure it out.

            1 Reply Last reply Reply Quote 0
            • TSchmeltzerundefined
              TSchmeltzer
              last edited by

              I still have the problem, although it only happens once when going from 22c to 210.
              Not really sure what to do.

              Changing the values like @dc42 suggested, made it better, but i still get the heater fault. Not sure why i didn't get that when i tested the other night.

              Could it be an indication of an impending hardware failure?

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

                It seems off for a hotend to fault like this. Can you post some photos of your setup?

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • TSchmeltzerundefined
                  TSchmeltzer
                  last edited by TSchmeltzer

                  Sure.
                  20210305_090716.jpg 20210305_090738.jpg

                  1 Reply Last reply Reply Quote 0
                  • TSchmeltzerundefined
                    TSchmeltzer
                    last edited by

                    20210305_090653.jpg

                    1 Reply Last reply Reply Quote 0
                    • TSchmeltzerundefined
                      TSchmeltzer
                      last edited by TSchmeltzer

                      I have run with this hotend setup for about a year without problems before 3.2.2.

                      Hidden away in there is a micro swiss all metal hotend.
                      Thermistor and heater is the original that came on the CR-10 mini.

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

                        1. Can you confirm that the print cooling fan was off when you tried to heat up and had the fault?

                        2. Please can you heat to 205C with the print cooling fan off, then send M573 P1 to report the heater PWM. Continue to send M573 P1 at intervals until the reported PWM value stabilises. Then report that value here. From that I can calculate another estimate of the gain, which may help to work out what is going wrong.

                        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
                        • TSchmeltzerundefined
                          TSchmeltzer
                          last edited by TSchmeltzer

                          @dc42 Ok, so today i do not get the heater fault. The only thing that is changes from yesterday is the ambient temp was around 22 yesterday, and today it's 24 because it's cold outside.

                          1. Yes the part cooler was off.
                          2. I did the readings without it faulting. I took a reading roughly every 5 sec.
                            https://pastebin.com/X6bZzbAZ

                          e4bd36f6-7b30-4f15-961c-b32da13a0714-image.png

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