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

    Stuck at Connecting...

    Scheduled Pinned Locked Moved
    Beta Firmware
    4
    16
    474
    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.
    • jay_s_ukundefined
      jay_s_uk @p8blr
      last edited by

      @p8blr is it flashing or is it steady?

      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

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

        @jay_s_uk flashing

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

          @p8blr what version was installed on the 6XD before?
          It may be best to go and BOSSA the latest image onto the 6XD directly https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#all-other-duet-boards

          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

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

            @jay_s_uk It shouldn't have changed, it was working great on 3.5.0 RC3. During the ordeal, I did attempt switching to stable and doing a downgrade according the documentation, which worked and DWC was connecting, but then when switched back to unstable, it started getting stuck at connecting... again. I want to also mention, that I have the printer beep at the end of the config.g file, and I hear it, so that means the code is at least running. It makes me think the issue is more on the web-interface side. I will try BOSSA and get back to you soon.

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

              @p8blr if it doesn't work then we'll need the logs from the SBC side.

              • log into your Single Board Computer
              • run sudo journalctl -xe -u duetcontrolserver

              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

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

                @jay_s_uk No dice. Even tried updating the web control files according to the documentation.

                logs.txt

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

                  As a troubleshooting step I would try a fresh SD card, fresh download of Duet Pi stable, and use bossa to flash 3.4.6 to the Duet, and see if it will connect with a stock config setup. And then go from there. Add in your configs. If it still works, upgrade to unstable channel.

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

                    @Phaedrux @jay_s_uk

                    It seems to be correlated with my config.g file. Adding that back in sometimes, but not all the time, prevents it from connecting...

                    See anything that might cause the instability?
                    config.g
                    DriveSetup.g
                    startup.g

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

                      What do you have in daemon.g?

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

                        @Phaedrux daemon.g
                        heaterFaultBed.g
                        heaterFaultChamber.g

                        Also, I'm stuck at connecting... again.

                        I modified config.g so that my bed and chamber heaters were no longer combined and I think that solved the entire issue. I was experiencing it in this thread but never got it resolved.
                        https://forum.duet3d.com/topic/34758/tips-for-autotuning-a-very-large-heated-chamber?_=1710270256740

                        Johnnygundefined 1 Reply Last reply Reply Quote 0
                        • Johnnygundefined
                          Johnnyg @p8blr
                          last edited by

                          This post is deleted!
                          Phaedruxundefined 1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • Phaedruxundefined
                              Phaedrux Moderator @Johnnyg
                              last edited by

                              @Johnnyg Please start a new thread.

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