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

    intermittent heater failure warning while heater working fine

    Scheduled Pinned Locked Moved
    Duet Web Control
    5
    15
    439
    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

      Sorry, I didn't read your original post carefully enough. Which firmware version are you using?

      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
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        From the screen shot it looks like 2.0.3/1.23/1.22.6

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • jens55undefined
          jens55
          last edited by jens55

          Here are the two screen shots - one of the heater failure message and then the g console pageScreenshot from 2019-09-14 19-37-50.png Screenshot from 2019-09-14 19-38-46.png

          There were no errors for a while but I wasn't printing anything either. I decided to close the Duet window and open it up again and that is when the error appeared. So, in this case, it appeared on startup of the web panel and note that Duet shows both bed and the first extruder as 'active' (ie no fault.
          I am under the impression that the error happened before when it was not related to starting the web panel but it could have happened when I refreshed the page. My embedded monitoring picture freezes quite regularly and I restart it by hitting the refresh button.
          I will try to pay closer attention to exactly when the error happens in the future.

          Edit: tried a bunch of refresh operations and sure enough the error happens every time.

          Edit 2: Just to point out that this is a relatively new issue. I will reboot the computer in a while to see if maybe something got weirded out in the system. I run Linux and sometimes there is a substantial time span before reboots. I have noted though that some programs (ie Cura) seem to have a bit of a memory leakage issue and consuming more and more memory over time. Maybe something got clobbered somewhere.

          Edit 3: Issue still exists after reboot

          1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti
            last edited by

            can you try a different browser? or try in incognito mode?

            1 Reply Last reply Reply Quote 0
            • jens55undefined
              jens55
              last edited by

              Tried in Chrome - same issue
              Tried in 'private' mode on Firefox which is presumably 'incognito' mode and it has the same issue.
              Good call though and a thing that gets me on a daily basis - I block scripts and other stuff and the vast majority of web sites fail with Firefox somewhere sooner or later until I unblock them. It is disgusting how many trackers and related crap I have to allow in order to see what the web site should look like. Duet , refreshingly, does not try to load 20 other web sites or trackers or what have you.
              I am not sure if Duet needs cookies enabled.
              My Chrome installation is vanilla without any blocking so if the issue had gone away I would have confirmed that it was the blocking ... but it wasn't.

              jens55undefined 1 Reply Last reply Reply Quote 0
              • jens55undefined
                jens55 @jens55
                last edited by

                Just a slight update - it seems that the Duet web interface might reproduce the last system error. I received a 'filament out' error message instead of the 'heater fault' error message today.

                dc42undefined 1 Reply Last reply Reply Quote 1
                • T3P3Tonyundefined
                  T3P3Tony administrators
                  last edited by

                  @chrishamm any idea why DWC may be repeating old error messages?

                  @jens55 if you have a chance the try connecting over USB as well and see if you get the error in a terminal.

                  www.duet3d.com

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

                    @jens55 said in intermittent heater failure warning while heater working fine:

                    Just a slight update - it seems that the Duet web interface might reproduce the last system error. I received a 'filament out' error message instead of the 'heater fault' error message today.

                    When DWC connects to a Duet, in effect it asks "What have I missed?". So yes, it is possible to receive old alerts on first connection.

                    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
                    • jens55undefined
                      jens55 @T3P3Tony
                      last edited by

                      @T3P3Tony said in intermittent heater failure warning while heater working fine:

                      @chrishamm any idea why DWC may be repeating old error messages?

                      @jens55 if you have a chance the try connecting over USB as well and see if you get the error in a terminal.

                      I have never connected via USB ... is this something pretty straight forward with a Linux computer ?

                      1 Reply Last reply Reply Quote 0
                      • jens55undefined
                        jens55
                        last edited by

                        Another interesting discovery: The error went away after the Duet went through a power cycle.
                        Under normal circumstances, the power on my Duet is never shut off so this tidbit of information was discovered only by chance.

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