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

    RRF 3.5.0-b3 sporadically stops extruding

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    rrf 3.5.0-b3 bugs
    4
    22
    784
    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.
    • Exerqtorundefined
      Exerqtor @Exerqtor
      last edited by Exerqtor

      I've ran that job file three times now with PA on, and it stops extruding each time it starts the first layer infill.

      I'm printing another one of the same job now, with PA disabled, and it's just finished with the first layer WITHOUT the extruder halting. So it looks like it's something going on with the PA,

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @Exerqtor
        last edited by

        @Exerqtor i can also replicate an issue with PA and IS enabled using 3.5b3. Best to disable PA if you can for now as it seems to print ok without it enabled

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        Exerqtorundefined 1 Reply Last reply Reply Quote 0
        • Exerqtorundefined
          Exerqtor @jay_s_uk
          last edited by Exerqtor

          @jay_s_uk said in RRF 3.5.0-b3 sporadically stops extruding:

          @Exerqtor i can also replicate an issue with PA and IS enabled using 3.5b3. Best to disable PA if you can for now as it seems to print ok without it enabled

          Glad to hear it's not an isolated issue on my end at least. Yup, keeping PA of for the time being, while looking out for other bugs 😅

          EDIT:

          I retract my statement about disabling PA and keep trying it out. Since it's another bug that causes the whole printer to reboot at random (seemingly) intervals without any reason. So i'm reverting to 3.5.0-b2 again.

          RIP 3.5.0-b3, you won't be missed🙈.

          gloomyandyundefined 1 Reply Last reply Reply Quote 1
          • Exerqtorundefined Exerqtor referenced this topic
          • gloomyandyundefined
            gloomyandy @Exerqtor
            last edited by

            @Exerqtor This may be too late, but if you get a reboot can you run M122 after it restarts and post the output. The info in there will help a lot with trying to solve the issue. It is probably worth checking the M122 output now (from whatever version you are now running) as the data from the previous crash may still be present.

            Exerqtorundefined 1 Reply Last reply Reply Quote 0
            • Exerqtorundefined
              Exerqtor @gloomyandy
              last edited by

              @gloomyandy
              Yeah it's way to late at this point, after the third reboot i reverted to b2. Don't look like it's a prevalent issue either since it's not being reported by anyone else.

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

                @Exerqtor It may not be too late, the reset data is stored in flash that may not be erased when you reinstall. Worth checking to see what M122 reports.

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

                  @gloomyandy Also even though others may not be reporting the problem, it may give clues towards other issues, so definitely worth reporting if you possibly can.

                  Exerqtorundefined 1 Reply Last reply Reply Quote 0
                  • Exerqtorundefined
                    Exerqtor @gloomyandy
                    last edited by

                    @gloomyandy I can pull a M122 from both the mobo and toolboard as soon as this print finishes.
                    If it's anything worth looking at or not i have no idea 🤷‍♂️

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

                      @Exerqtor This (and the stack trace that follows it) is the part of interest....

                      Last software reset at 2023-04-15 10:26, reason: HardFault imprec, Gcodes spinning, available RAM 10968, slot 0
                      
                      Exerqtorundefined 1 Reply Last reply Reply Quote 0
                      • Exerqtorundefined
                        Exerqtor @gloomyandy
                        last edited by

                        @gloomyandy
                        This is from the Mini:

                        Last reset 02:45:09 ago, cause: software
                        Last software reset at 2023-04-23 10:32, reason: User, Gcodes spinning, available RAM 5696, slot 1
                        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00446000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                        

                        And the 1LC:

                        Last reset 02:46:46 ago, cause: software
                        Last software reset data not available
                        
                        gloomyandyundefined 1 Reply Last reply Reply Quote 1
                        • gloomyandyundefined
                          gloomyandy @Exerqtor
                          last edited by

                          @Exerqtor Unfortunately it looks like the reset data has been wiped by the older firmware. Oh well, thanks for taking the time to check. If you do decide to try 3.5.0-beta.3 again and you get a reset please grab the m122 output and post it.

                          Exerqtorundefined 1 Reply Last reply Reply Quote 0
                          • Exerqtorundefined Exerqtor referenced this topic
                          • Exerqtorundefined Exerqtor referenced this topic
                          • Exerqtorundefined Exerqtor marked this topic as a question
                          • Exerqtorundefined
                            Exerqtor @gloomyandy
                            last edited by

                            This issue has been solved as of RRF3.5b3+!

                            RogerPodacterundefined 1 Reply Last reply Reply Quote 1
                            • Exerqtorundefined Exerqtor has marked this topic as solved
                            • RogerPodacterundefined
                              RogerPodacter @Exerqtor
                              last edited by

                              i was about to start a new topic. i recently upgrade to 3.5.0-Beta3 and now i have extruder issues. I use 2 toolboards 1LC on an IDEX machine. It appears that my extruder motor stops extruding during printing. it seems to happen right after a toolchange to select the new extruder. The toolchange does some fast extrude retraction.

                              Once this behavior happens i have to reboot the printer to restore back to normal behavior.

                              I am reverting back to firmware 3.4.2 for now. hopefully my issue is part of this fix in the Beta 4 next release.

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