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

    Firmware install caused MB6HC to fail to connect

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    3
    6
    303
    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.
    • kroybalundefined
      kroybal
      last edited by

      I was searching the forum to see if this was a solved problem, however, I couldn't find any valuable info on my issue:

      The temp here at the lab was updating the firmware such that we can have closed loop control on our encoded motors.

      Our setup is for a IDEX printer consisting of a D3MB6HC + two Duet 3 Exp 1HCL. We have two 17E1K-07 motors installed into the X and U axes.

      We found our prints to be failing due to layer shifts in The X direction and decided to upgrade the machine.

      When the temp flashed the firmware by uploading a .zip file (Duet2and3Firmware-3.4.1.zip) to the DWC sys directory, the machine now fails to start up properly. The Panel Due shows an endless "Connecting..." and we recently purchased a new MB6HC with a fresh, factory setting SD card which upon swapping, still has no impact on the machine's ability to boot up and connect.

      I am out of ideas with how to regain our machine without swapping in the new board.

      jay_s_ukundefined droftartsundefined 2 Replies Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @kroybal
        last edited by

        @kroybal I suggest working through this first https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

        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

        kroybalundefined 1 Reply Last reply Reply Quote 0
        • droftartsundefined
          droftarts administrators @kroybal
          last edited by

          @kroybal is the status light dimly lit? Most likely the firmware has erased, but has failed to flash new firmware; it happens occasionally. You just need to follow these instructions to manually flash the firmware: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2

          Use the firmware file as specified here: https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_firmware#firmware-file-naming

          Ian

          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

          1 Reply Last reply Reply Quote 0
          • kroybalundefined
            kroybal @jay_s_uk
            last edited by

            @jay_s_uk Thank you for the link

            Here are my results:

            I am in this regime:

            If the firmware has been erased the DIAG/STATUS LED will glow permanently (ie not full brightness).

            And:

            If neither port is shown, then the Duet may be faulty or it may not have valid firmware installed. With USB power applied, erase the firmware. Only erase the firmware if your board is completely unresponsive, or if instructed to do so by Duet3D. On older boards do this by holding down the Erase button for at least 1 second, then press the Reset button. On newer boards there is no Erase button; so fit a jumper across the Erase pins, then connect to USB for a few seconds, then disconnect from USB, remove the jumper and connect to USB again. You may have to do this a couple of times if the Duet does not appear in the Device Manager.

            Kind of seems like I need to erase 😲

            1 Reply Last reply Reply Quote 0
            • kroybalundefined
              kroybal
              last edited by

              I wasn't present to witness the cause of failure during the update that erased/corrupted its firmware. Which would be interesting to know and of course it was the temp's last day here at the lab (I am sure he feels bad 😆, good kid).

              If anyone knows what could cause a firmware flash to render a board unresponsive I would be interested to know.

              However, I followed the erasing procedure and and using Bossa I was able to flash the most up to date firmware. Wired the machine up and printed a benchy boat just fine. Which makes this a resolved topic.

              Thanks!

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

                @kroybal I have seen the odd update fail on a 6HC that led to the firmware being erased. Never found out why it happened

                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

                1 Reply Last reply Reply Quote 2
                • Phaedruxundefined Phaedrux marked this topic as a question
                • Phaedruxundefined Phaedrux has marked this topic as solved
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA