Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    3.4.0beta7 - RC2 overheating when the model fan is turned on

    Beta Firmware
    4
    9
    268
    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.
    • Del87
      Del87 last edited by

      There are some strange behavior on heater when the model fan turns on high/low speed.
      Firmware 3.4.0beta6 - straight line temperature, maximum deviation +0.5 degree when model fan 100%.
      Firmware 3.4.0beta7-3.4.0RC2 - +1 degree on 2-3 layers of the model (fan 15-30%). +2 degree when model fan 100%.
      PID calibration new/old doesnt matter - same behavior.
      Duet 3 mini 5+ Pt1000
      And a small note: same models printed 3.4.0beta6 - no messages about driver0 stuck , 3.4.0RC2 - there was messages. I use sensorless homing, is there some changes mentioned in upgrade notes?

      Dmitry

      A Former User 1 Reply Last reply Reply Quote 0
      • Moved from Firmware developers by  Phaedrux Phaedrux 
      • Phaedrux
        Phaedrux Moderator last edited by

        Can you give us some more information on your setup. Heaters, etc.

        Can you share your config.g and your PID tune values?

        What is the exact driver error message?

        Z-Bot CoreXY Build | Thingiverse Profile

        Del87 1 Reply Last reply Reply Quote 0
        • A Former User
          A Former User @Del87 last edited by

          @del87 said in 3.4.0beta7 - RC2 overheating when the model fan is turned on:

          There are some strange behavior on heater when the model fan turns on high/low speed.
          Firmware 3.4.0beta6 - straight line temperature, maximum deviation +0.5 degree when model fan 100%.
          Firmware 3.4.0beta7-3.4.0RC2 - +1 degree on 2-3 layers of the model (fan 15-30%). +2 degree when model fan 100%.
          PID calibration new/old doesnt matter - same behavior.
          Duet 3 mini 5+ Pt1000
          And a small note: same models printed 3.4.0beta6 - no messages about driver0 stuck , 3.4.0RC2 - there was messages. I use sensorless homing, is there some changes mentioned in upgrade notes?

          About same issue for me with the RC1, look here: https://forum.duet3d.com/topic/27533/temperatures-totally-wrong

          1 Reply Last reply Reply Quote 1
          • Referenced by 
          • Del87
            Del87 @Phaedrux last edited by

            @phaedrux
            All pid tuning by M303 T0 S235
            Pid parameters after tuning on firmware RC2:
            M307 H1 R2.017 K0.304:0.121 D5.56 E1.35 S1.00 B0 V23.8
            Old parameters firmware beta6 (works great):
            M307 H1 R2.096 C266.944:211.319 D5.59 S1.00 V23.9 B0 I0
            config.g

            I guess it is all about the model fan cooling compensation, beta6 perfect for me, later ones are much worse.

            driver0 a lot of reports about stall detection on one Z height (didn't copy it). Old firmware - no reports, same gcode.

            Dmitry

            1 Reply Last reply Reply Quote 0
            • Dogma2k
              Dogma2k last edited by

              And the same i said here
              https://forum.duet3d.com/post/270688

              1 Reply Last reply Reply Quote 0
              • Del87
                Del87 last edited by Del87

                3.4.rc2+2 pid works stable. But the problem with driver stuck is actual. There was the message about driver 0 and 1 (X Y) stuck then motor Y (h-bot configuration) stopped working. Firmware 3.4.beta6 no messages, no problems with stucks, sensorless homing, motors.

                What changes in motor/driver or sensorless settings was made after beta6 firmware?

                dbb83800-6e7c-49a6-b407-1c798261703d-image.png

                no such messages on firmware 3.4.beta6.

                Dmitry

                1 Reply Last reply Reply Quote 0
                • Del87
                  Del87 last edited by Del87

                  some new investigations:
                  G28 via console - no error messages
                  G28 in gcode (only one command). Error messages after this gcode start printing.

                  f4d6f391-6a47-408d-8e3f-3fa244d9159c-image.png

                  homeall.g

                  Dmitry

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

                    @del87 Can you start a new thread with your details for this issue?

                    Z-Bot CoreXY Build | Thingiverse Profile

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

                      @phaedrux okay

                      Dmitry

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