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

    Auto tune cancelled because temperature peak was not identified

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    5
    19
    2.3k
    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.
    • deckingmanundefined
      deckingman
      last edited by

      Tried yet again with the target set to 140 which is what I think I used when I last successfully tuned the bed heater on earlier firmware. This time I got this:

      14:10:46 Auto tune cancelled because target temperature was not reached
      13:50:46 Auto tune phase 1, heater on
      13:50:40 M303 H0 S140
      Auto tuning heater 0 using target temperature 140.0C and PWM 1.00 - do not leave printer unattended

      I tried manually heating the bed to 140 and it does get there - just takes while longer than the auto tuning will allow. If I recall correctly, when I tuned the bed before using an older firmware version, I think I had a message to the effect that the heater was over powered and could reach 500 plus deg C.

      Not sure what to try now. I'm guessing comment out the old M307 for heater 0 and try again?

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

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

        Looks like I need to change the peak detection code to accept a fall of in the rate of increase of temperature instead of an actual peak. My guess is that your bed cools so slowly that noise is preventing the code from seeing a single peak.

        The auto tune code allows 20 minutes for the target temperature to be reached when tuning a bed or chamber heater, or 5 minutes when tuning an extruder heater.

        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
        • deckingmanundefined
          deckingman
          last edited by

          Hi David,

          Yes the bed is 10mm thick and has 12mm insulation underneath so it takes forever to cool (but it does reach a peak about 30 to 50 seconds after heater off and drops slowly back to the set temperature after 2 minutes. Also, I'd say there is probably 0.2 degrees of noise in the readings as well, - ( I'm using a 4 wire pt100).

          I just tried again and even in bang bang mode, after 20 minutes my bed reaches 128 deg C from a starting temp of 30. I'd normally only want to use 60 degrees max so that's not an issue for me but you might want to mention the 20 minute limit in the wiki, just in case someone else tries to tune a big bed to a high temperature at some time in the future.

          It's on my list of things to do, to change the bed from 10mm to 8mm. I can't see it having any detrimental effect even though it's 400mm square. It'll speed up the warm up time but it's a fair bit a hassle to do, (and I'd have to buy another silicone heater because I doubt that I'd be able to unstick the one I have without destroying it).

          I can run with the original settings or bang bang mode for now. It all works so it's no big deal. Let me know if and when you want me to test any new code.

          Ian

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

          1 Reply Last reply Reply Quote 0
          • ElmoCundefined
            ElmoC
            last edited by

            @dc42:

            Looks like I need to change the peak detection code to accept a fall of in the rate of increase of temperature instead of an actual peak. My guess is that your bed cools so slowly that noise is preventing the code from seeing a single peak.

            The auto tune code allows 20 minutes for the target temperature to be reached when tuning a bed or chamber heater, or 5 minutes when tuning an extruder heater.

            Has anything been done in regards to this? I am seeing the same problem. 300x300x6 bed with 120v 600w heater. Get up to temperature in under 4 minutes then get the peak not detected message about 30 seconds later.

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

              It's still on my list to do something about. Meanwhile, you may find it helps to have the print cooling fan turned on and blowing on the bed. Or you can use the manual tuning method.

              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
              • Wernerundefined
                Werner
                last edited by

                Hi David and Ian, I too have experienced all of the above issues discussed over the past year. I have found workarounds and ended up setting things up manually with crazy numbers like A100 C1000 D200. I sure would like to be able to use auto tune but same a Ian I have a huge thermal mass at 10mm think 800 square mm. I have been able to to get past some of my problems with setting M570 H0 P300 T30 ; Load new Heater Fault parameters. The thing that has been stopping me from completing autotune it the 2 min limit to cool down. I will overshoot about 28c but it will take more than 2 min to start coming down. Is there anything I can do to on my end to increase that limit? I think this is an important thing to nail down as more and more high performance and more pro like machines have bigger platens.

                Thanks for the help!

                Werner

                Werner Berry
                Designer-builder, BerryBot3D Pro

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

                  David,

                  Did you ever get around to looking at this? TBH I'd forgotten all about it myself so haven't tried tuning the bed heater since starting this thread.

                  Ian

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

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

                    Thanks for the reminder, I'll try to include a fix in the next beta.

                    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
                    • deckingmanundefined
                      deckingman
                      last edited by

                      I meant to say that I tested this the other day using latest 1.19 beta11 and it's likely fixed. That is to say it did report a peak after phase 2 although the peak was reported at 7 seconds after heater off but the true peak was about 1.4 degrees higher and occurred at around 100 seconds after heater off. I can't say what would happen after that as it takes my bed an awful long time to cool down and DWC disconnected (reason - timeout) before phase 3 completed.

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

                      1 Reply Last reply Reply Quote 0
                      • Dougal1957undefined
                        Dougal1957
                        last edited by

                        I had this issue the other day when trying to tune mine I sent a manual D param of d60 and that seemed to allow it to complete?

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