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

    Firmware 3.50.rc.4 stops working

    Scheduled Pinned Locked Moved
    Beta Firmware
    5
    24
    557
    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.
    • Chrissundefined
      Chriss @Chriss
      last edited by

      Btw: you can reach me via discord too, if you want to have a call. I'm on the Duet Discord, same avatar, known there as Chris or my Dicord username: warty_towel (Yes I love the hotel in Torquay)

      1 Reply Last reply Reply Quote 0
      • Chrissundefined Chriss referenced this topic
      • gloomyandyundefined
        gloomyandy @Chriss
        last edited by

        @Chriss Is this a repeatable problem? That is if you run the same print again does the same thing happen?

        Chrissundefined 1 Reply Last reply Reply Quote 0
        • Chrissundefined Chriss referenced this topic
        • Chrissundefined
          Chriss @gloomyandy
          last edited by

          @gloomyandy I did not executed the same g-code if you as for that.
          It happened to me the 4th time now with 4 different objects. I can try to re-execute the g-code if this is what you want. Or I can re slice and print it. But again: It is not very easy to reproduce.... I had more than 10 successful prints between the failures. And all of failed prints happened with other objects.

          Cheers, Chriss

          gloomyandyundefined 1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy @Chriss
            last edited by

            @Chriss If you search for similar problems on the forum you will see that this may be caused by static buildup on the printhead. Is your printhead grounded? See: https://forum.duet3d.com/post/325903

            Chrissundefined 1 Reply Last reply Reply Quote 0
            • Chrissundefined
              Chriss @gloomyandy
              last edited by

              @gloomyandy Let me do that.. but let me make one remark here: I have this problem since 3.5rc4, rc3 and earlier versions did not have that problem. And I have not chanced my printer hardware since a while...

              But it would take me at least 10 days to "verify" that the problem has gone than.... I'm sorry, but I have some scars from my wifi problem, this scars teached me not to reboot my board to early.

              (Btw, by other 4 printers with a Mini5+ work without constantly but on a lower firmeware level, and none of them have a "grounded nozzle)

              gloomyandyundefined 1 Reply Last reply Reply Quote 0
              • gloomyandyundefined
                gloomyandy @Chriss
                last edited by

                @Chriss I was not asking you to reboot your board I was simply asking if your toolhead was grounded and pointing out to you previous responses to similar problems.

                Chrissundefined 1 Reply Last reply Reply Quote 0
                • Chrissundefined
                  Chriss @gloomyandy
                  last edited by

                  @gloomyandy Sorry, yes you are right. But I have disassemble the Voron Stealthburner for that... So I have to turn of the printer. I have to pull the power and can connection of the toolboard to disassemble SB to reach the Revo to make that connection.

                  Cheers, Chriss

                  gloomyandyundefined 1 Reply Last reply Reply Quote 0
                  • gloomyandyundefined
                    gloomyandy @Chriss
                    last edited by

                    @Chriss As above I was simply asking you if you had already grounded the toolhead as that would have eliminated that as a potential cause. I have asked @dc42 to take a look at this problem so perhaps it is best to wait for him or one of the other duet folks to comment.

                    Chrissundefined 2 Replies Last reply Reply Quote 0
                    • Chrissundefined
                      Chriss @gloomyandy
                      last edited by

                      @gloomyandy Sorry, my bad. I do not always understand the difference between a question and "you should do that". 🙂

                      Anyway, you are more than right.... I have to do a bigger maintenance job on the toolhead anyway. So I will do this job and ground the hotend, just in case. And lets see of David has a other idea what may cause this problem.

                      Cheers, Chriss

                      1 Reply Last reply Reply Quote 0
                      • Chrissundefined
                        Chriss @gloomyandy
                        last edited by

                        Hi @gloomyandy,

                        It seems that the BTT guys experience a similar problem:
                        https://github.com/jcheger/BTT-SB22xx-undervoltage-reset-issue/blob/main/README.md

                        I ground my my hotend and my extruder now, just in case.

                        Cheers, Chriss

                        oliofundefined 1 Reply Last reply Reply Quote 0
                        • oliofundefined
                          oliof @Chriss
                          last edited by

                          @Chriss That BTT issue is just similar in effect, but may not be related at all in cause (if you go back to the original issue, grounding the metalwork on the effector does not fix it for everyone). Also, in the BTT case it seems to be mostly about their toolboards, the issue is not happening (AFAICT) with BTT main control boards. So I believe it's a red herring.

                          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                          Chrissundefined 1 Reply Last reply Reply Quote 0
                          • Chrissundefined
                            Chriss @oliof
                            last edited by

                            @oliof maybe…. But what else could be the root cause of the problem than? Software may be bad or a mechanical/electrical problem. Anyway, I want to strike out things which are easy to solve.

                            1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined Phaedrux moved this topic from General Discussion
                            • Phaedruxundefined
                              Phaedrux Moderator
                              last edited by

                              Have you tried running the same gcode file again to see if i stops at the same point?

                              Please share a M122 report after each reset.

                              Also please share your config set.

                              Z-Bot CoreXY Build | Thingiverse Profile

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