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

    Tips for autotuning a very large heated chamber?

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    4
    22
    782
    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.
    • p8blrundefined
      p8blr @droftarts
      last edited by

      @droftarts the 30 minute time limit makes sense, I expect I will need a lot longer than that just due to the amount of air, and thermal mass of the bed + the inner walls of the chamber.

      I'll give your suggestions a shot and post an update. It's tough to say how long I'll need, I'm trying to do the calculations to find the heat capacity of the entire system and my heat losses. Perhaps the time to heat limit could be a user parameter? We've actually been trying to compile the firmware ourselves, but we're not very familiar with compiling for arm32 and it's been a challenge to get it to compile without errors.

      droftartsundefined 1 Reply Last reply Reply Quote 0
      • droftartsundefined
        droftarts administrators @p8blr
        last edited by

        @p8blr I've raised a feature request to add a parameter to override the default timeout: https://github.com/Duet3D/RepRapFirmware/issues/948
        That doesn't help you immediately, though!

        We've actually been trying to compile the firmware ourselves, but we're not very familiar with compiling for arm32 and it's been a challenge to get it to compile without errors.

        I've asked @dc42 for information on what needs changing in the firmware to change the timeout. If you are having trouble compiling, post a new thread with the errors you are getting. I assume you have seen this page? https://github.com/Duet3D/RepRapFirmware/wiki/Building-RepRapFirmware

        Ian

        droftarts created this issue in Duet3D/RepRapFirmware

        open [FeatureRequest]: Configurable timeout for M303 tuning #948

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        p8blrundefined 1 Reply Last reply Reply Quote 0
        • p8blrundefined
          p8blr @droftarts
          last edited by p8blr

          @droftarts I'll have to get back to you on the compiling errors, but yes we're using that page as a guide.

          On a different note, I attempted to autotune to 60C today, it hit that temperature very quickly, but got stuck in phase 3 and DWC stopped working. Refreshing the page gets to the "connecting" page but that's it. I've tried different phones/PCs but all get stuck at connecting. This has happened a lot before, but I figured it was a normal bug, but now I've noticed that it's correlating with me combining the heaters. It messes it up to the point that when I reboot the printer, that it won't connect again until I pull out the sd card, modify config.g and then start it up again.

          connecting.PNG

          Both versions of my config.g are over 2000 characters so I'm just attaching them
          workingconfig.g
          brokenconfig.g
          DriveSetup.g
          startup.g
          daemon.g

          I should also note that I'm running a raspberry pi 4 in sbc mode with a fast 32gb samsung evo card, and I'm on release candidate 2 (same issue with 1)

          chrishammundefined 1 Reply Last reply Reply Quote 0
          • chrishammundefined
            chrishamm administrators @p8blr
            last edited by

            @p8blr Can you press F12 or open the dev tools in your browser session and check for potential errors in the console? If nothing shows up there, can you please check the duetcontrolserver log? See the section about journalctl in https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#increasing-log-level.

            It doesn't look like DSF loses connection to the Duet so I suspect something else is going on.

            Duet software engineer

            p8blrundefined 2 Replies Last reply Reply Quote 0
            • p8blrundefined
              p8blr @chrishamm
              last edited by

              @chrishamm I'll have to put that code back and run a PID autotune again, I'll get back to you with an update.

              1 Reply Last reply Reply Quote 0
              • p8blrundefined
                p8blr @chrishamm
                last edited by p8blr

                @chrishamm I changed the settings and restarted and got the error, I didn't even have to autotune.

                97e4ba9d-713e-4e49-ac6a-7fea46b9f670-image.png

                journalctl -u duetcontrolserver -f
                dc78f4ab-e4e6-4fb0-b36a-2e8183918d05-image.png

                Also I should mention that putty freezes up very frequently when this error happens.

                chrishammundefined 1 Reply Last reply Reply Quote 0
                • chrishammundefined
                  chrishamm administrators @p8blr
                  last edited by

                  @p8blr If PuTTY freezes as well that probably means the Pi stops working at some point. In that case I'd rather check the electronics again. Are you operating the Pi from the Duet's 5V rail? If yes, consider removing the 5V -> SBC jumper and hook up the Pi to an external 5V PSU.

                  Duet software engineer

                  p8blrundefined 1 Reply Last reply Reply Quote 0
                  • p8blrundefined
                    p8blr @chrishamm
                    last edited by

                    @chrishamm I'm powering the pi via a usb C supply. My suspicion is that because the freezing happens at a regular pace, perhaps it has to do with the daemon.g. Is that possible?

                    chrishammundefined 1 Reply Last reply Reply Quote 0
                    • chrishammundefined
                      chrishamm administrators @p8blr
                      last edited by

                      @p8blr I need the full DuetControlServer log to answer that. Your excerpt didn't show anything significant.

                      Duet software engineer

                      p8blrundefined 1 Reply Last reply Reply Quote 0
                      • p8blrundefined
                        p8blr @chrishamm
                        last edited by

                        @chrishamm How do I generate that?

                        chrishammundefined 2 Replies Last reply Reply Quote 0
                        • chrishammundefined
                          chrishamm administrators @p8blr
                          last edited by

                          @p8blr journalctl -u duetcontrolserver --no-pager -b

                          Duet software engineer

                          p8blrundefined 1 Reply Last reply Reply Quote 0
                          • chrishammundefined
                            chrishamm administrators @p8blr
                            last edited by

                            @p8blr I believe this is a duplicate of this report. Can you try out one of those DWC builds and check if it is fixed then? See here.

                            Duet software engineer

                            p8blrundefined 2 Replies Last reply Reply Quote 0
                            • p8blrundefined
                              p8blr @chrishamm
                              last edited by

                              @chrishamm
                              report.txt

                              1 Reply Last reply Reply Quote 0
                              • p8blrundefined
                                p8blr @chrishamm
                                last edited by

                                @chrishamm I can, I'll get back to you on it...

                                1 Reply Last reply Reply Quote 0
                                • p8blrundefined
                                  p8blr @chrishamm
                                  last edited by

                                  @chrishamm So far I'm not getting any more issues connecting to the web interface with the heaters combined now, just errors that the DWC versions don't match.

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

                                    @p8blr have you refreshed page? this bites me on occasion on upgrades!

                                    www.duet3d.com

                                    p8blrundefined 1 Reply Last reply Reply Quote 0
                                    • p8blrundefined
                                      p8blr @T3P3Tony
                                      last edited by

                                      @T3P3Tony refreshing the page seems to work fine. I know what you mean though, sometimes before when I refreshed the page it wouldn't reconnect.

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

                                        @p8blr yep if DWC is upgraded the page needs to be refreshed before it's upgraded in the version you browser is displaying!

                                        www.duet3d.com

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