How 2 upgrade 3.2beta+1 to 3.3 w/ D3M5+
-
Just trying to figure out how to update from 3.2beta+1 to 3.3 with a Duet 3 Mini 5+??? I am also having issues when trying to upload any sort of large files into the system section of the DWS? It will stay connected to the WiFi no problem but then every dern time I try to upload and install any sort of large zip files like DSF which has 1015 or so files it almost always cancels the upload never completing the upload and therefore I can not upgrade to a stable version of RRF? It is wierd how it stays connected then all of a sudden the D3M5+ decides it wont stay connected to the WiFi connection when I try to upload some bigger zip files its frustrating its like it doesnt want to be updated or upgraded or something? I have tried connecting my Raspberry Pi 4b to the board via the included 26 to 40pin ribbon cable and the Pi updates to 3.3.0 on all of the everything but as soon as it tries to connect to the board it always states that Duet Control Server hasnt started and Ive tried via SSH/Putty to install and start the DCS manually but I get this return whenever I check to see what happened:
root@duet3:/home/pi# sudo journalctl -u duetcontrolserver
-- Logs begin at Sat 2021-06-19 02:17:01 CDT, end at Sat 2021-06-19 03:14:02 CDT
Jun 19 02:17:05 duet3 systemd[1]: Starting Duet Control Server...
Jun 19 02:17:07 duet3 DuetControlServer[440]: Duet Control Server v3.3.0
Jun 19 02:17:07 duet3 DuetControlServer[440]: Written by Christian Hammacher for
Jun 19 02:17:07 duet3 DuetControlServer[440]: Licensed under the terms of the GN
Jun 19 02:17:08 duet3 DuetControlServer[440]: [info] Settings loaded
Jun 19 02:17:08 duet3 DuetControlServer[440]: [info] Environment initialized
Jun 19 02:17:08 duet3 DuetControlServer[440]: [fatal] Could not connect to Duet
Jun 19 02:17:08 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Jun 19 02:17:08 duet3 systemd[1]: Failed to start Duet Control Server.
Jun 19 02:17:09 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
Jun 19 02:17:09 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
Jun 19 02:17:09 duet3 systemd[1]: Stopped Duet Control Server.
Jun 19 02:17:09 duet3 systemd[1]: Starting Duet Control Server...
Jun 19 02:17:09 duet3 DuetControlServer[603]: Duet Control Server v3.3.0
Jun 19 02:17:09 duet3 DuetControlServer[603]: Written by Christian Hammacher for
Jun 19 02:17:09 duet3 DuetControlServer[603]: Licensed under the terms of the GN
Jun 19 02:17:10 duet3 DuetControlServer[603]: [info] Settings loaded
Jun 19 02:17:10 duet3 DuetControlServer[603]: [info] Environment initialized
Jun 19 02:17:10 duet3 DuetControlServer[603]: [fatal] Could not connect to Duet
Jun 19 02:17:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result
Jun 19 02:17:11 duet3 systemd[1]: Failed to start Duet Control Server.
Jun 19 02:17:11 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=I guess it does this because the RPi / Raspbian /Duet3d OS is on 3.3.0 and all of the everything is updated and upgraded to the latest everything meanwhile the actual Duet 3 Mini 5+ is on 3.2Beta+1 ....... I promise to God I will go and get a genuine Duet3D board next go around cause this updating and upgrading from Beta is a pain I swear I know there must be some sort of a fix for this sorry for the long initial post lols!!!
-
I'm a bit confused. Are you using a Pi? If so you would be updating everything with sudo apt update and sudo apt upgrade. If it's failing to update the Duet because it's on a beta firmware you can manually update the Duet over USB to get back in sync.
https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Firmware#Section_Updating_firmware_via_USB
