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

    DWC 3.4 reverts to 3.2.2 after shutdown

    Scheduled Pinned Locked Moved Solved
    Duet Web Control
    2
    5
    237
    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.
    • man_marundefined
      man_mar
      last edited by

      As per title, I have this weird issue that I can't figure out.

      I'm in SBC mode, I upgraded the firmware to the 3.4 release, but I noticed the DWC was still 3.2.2.

      So I proceeded to upgrade the DWC manually uploading the .zip package using the "Upload System Files" in "System". All went smooth, I can see it upgraded to DWC 3.4.

      I do some stuff, then shutdown the machine, turn it back on and I noticed the old UI. I check and it's DWC 3.2.2. What the hell?! I tried several times the same procedure, but no luck.

      I then tried to upgrade using PuTTY, sudo apt-upgrade/update, it does some stuff, but no DWC 3.4.

      I tried also manually deleting the "www" folder in the boot partition of the SD card and replacing it with the 3.4 version: at first I get the DWC3.4, but at the next start up I get DWC3.2.2.

      As last resort I tried formatting the SD card and did a fresh installation with the latest .img, but I still have DWC 3.2.2.

      The only way I'm able to get DWC3.4 is to upload the "DuetWebControl-SD.zip" every time I turn on the machine. But then again if I turn off the machine and turn on I get DWC 3.2.2.

      TBH it wouldn't be that big of a deal if the "Height Map" didn't tell me "Invalid Height Map", and it's a bit annoying 😞

      So...I'm sure I missed something but I can't figure out what.

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

        @man_mar connect to the SBC via SSH and send sudo apt update && sudo apt upgrade -y
        DO NOT update RRF manually using the interface when in SBC mode

        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

        man_marundefined 1 Reply Last reply Reply Quote 0
        • man_marundefined
          man_mar @jay_s_uk
          last edited by

          @jay_s_uk said in DWC 3.4 reverts to 3.2.2 after shutdown:

          @man_mar connect to the SBC via SSH and send sudo apt update && sudo apt upgrade -y
          DO NOT update RRF manually using the interface when in SBC mode

          well...this is driving me insane.

          I took the microSD card, formatted, and followed the instructions I found here ( https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup ).

          Connected via PuTTY and then used sudo apt-get update and then sudo apt-get upgrade, process went apparently well. When I use my browser and I go to "duet3.local", it connects to the DWC but I can already see that it's the old 3.2.2.

          At least the firmware is updated:
          Board: Duet 3 MB6HC (MB6HC)
          DSF Version: 3.4.1
          Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.1 (2022-06-01)

          But the DWC:
          Duet Web Control 3.2.2
          GitHub
          Web Interface developed by Christian Hammacher for Duet3D.
          Licensed under the terms of the GNU General Public License v3

          How the hell am I supposed to update the DWC in order for it to NOT go back to the 3.2.2?

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

            @man_mar then it sounds like a caching issue with your browser.
            clear the cache and try connecting again. DSF is the right version

            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

            man_marundefined 1 Reply Last reply Reply Quote 1
            • man_marundefined
              man_mar @jay_s_uk
              last edited by

              @jay_s_uk

              I'll be damned. I tried with an "new incognito window" and it works. So it's obviously a caching issue, as you predicted.

              Thank you very much for the help.

              1 Reply Last reply Reply Quote 1
              • 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