Solved SBC not started after update
-
Hey,
I recently updated my Duet 6hc+SBC from 3.2.2 to 3.4, or at least I tried.
After the update I´ll get an error message "Failed to connect to duet, please check your connections".Checking with USB and 115 I´ll get follwing message
SENDING:M115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta3 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-08-24 13:58:02
journalctl -fu duetcontrolserver returns:
pi@duet3:~ $ journalctl -fu duetcontrolserver -- Logs begin at Fri 2021-09-10 09:17:01 BST. -- Sep 10 10:02:44 duet3 DuetControlServer[851]: [warn] Restarting transfer because the Duet received a bad response (header) Sep 10 10:02:44 duet3 DuetControlServer[851]: [fatal] Could not connect to Duet (Invalid protocol version 6) Sep 10 10:02:44 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Sep 10 10:02:44 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= 100ms expired, scheduling restart. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j ob, restart counter is at 10. Sep 10 10:02:45 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Start request repea ted too quickly. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'. Sep 10 10:02:45 duet3 systemd[1]: Failed to start Duet Control Server.
sudo journalctl -u duetcontrolserver -e returns:
pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Sep 10 10:02:43 duet3 DuetControlServer[838]: [info] Environment initialized Sep 10 10:02:43 duet3 DuetControlServer[838]: [fatal] Could not connect to Duet Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Failed with result Sep 10 10:02:43 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:02:43 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:02:43 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:02:43 duet3 systemd[1]: Starting Duet Control Server... Sep 10 10:02:44 duet3 DuetControlServer[851]: Duet Control Server v3.2.2 Sep 10 10:02:44 duet3 DuetControlServer[851]: Written by Christian Hammacher for Sep 10 10:02:44 duet3 DuetControlServer[851]: Licensed under the terms of the GN Sep 10 10:02:44 duet3 DuetControlServer[851]: [info] Settings loaded Sep 10 10:02:44 duet3 DuetControlServer[851]: [info] Environment initialized Sep 10 10:02:44 duet3 DuetControlServer[851]: [warn] Restarting transfer because Sep 10 10:02:44 duet3 DuetControlServer[851]: [fatal] Could not connect to Duet Sep 10 10:02:44 duet3 systemd[1]: duetcontrolserver.service: Failed with result Sep 10 10:02:44 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:02:45 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Start request repea Sep 10 10:02:45 duet3 systemd[1]: duetcontrolserver.service: Failed with result Sep 10 10:02:45 duet3 systemd[1]: Failed to start Duet Control Server.
Upgraded DCS to 3.3, still not working.
pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Sep 10 10:37:40 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:37:40 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:37:40 duet3 systemd[1]: Starting Duet Control Server... Sep 10 10:37:40 duet3 DuetControlServer[2552]: Duet Control Server v3.3.0 Sep 10 10:37:40 duet3 DuetControlServer[2552]: Written by Christian Hammacher fo Sep 10 10:37:40 duet3 DuetControlServer[2552]: Licensed under the terms of the G Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Settings loaded Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Environment initialized Sep 10 10:37:41 duet3 DuetControlServer[2552]: [warn] Restarting transfer becaus Sep 10 10:37:41 duet3 DuetControlServer[2552]: [fatal] Could not connect to Duet Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Failed with result Sep 10 10:37:41 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:37:41 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:37:41 duet3 systemd[1]: Starting Duet Control Server... Sep 10 10:37:41 duet3 DuetControlServer[2565]: Duet Control Server v3.3.0 Sep 10 10:37:41 duet3 DuetControlServer[2565]: Written by Christian Hammacher fo Sep 10 10:37:41 duet3 DuetControlServer[2565]: Licensed under the terms of the G Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Settings loaded Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Environment initialized
So it seems like the firmware update was succesful, but DCS is now on the wrong version or broken? How can I fix this (ideally without reflashing everything)?
-
@com3 What steps did you use to update the SBC?
-
I so I tried the stuff I found in other posts:
sudo apt-get update
sudo apt-get upgradeand:
sudo apt update
sudo apt upgrade duetsoftwareframeworkthats currently the situation here:
pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e Sep 10 10:37:40 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:37:40 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:37:40 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:37:40 duet3 systemd[1]: Starting Duet Control Server... Sep 10 10:37:40 duet3 DuetControlServer[2552]: Duet Control Server v3.3.0 Sep 10 10:37:40 duet3 DuetControlServer[2552]: Written by Christian Hammacher fo Sep 10 10:37:40 duet3 DuetControlServer[2552]: Licensed under the terms of the G Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Settings loaded Sep 10 10:37:41 duet3 DuetControlServer[2552]: [info] Environment initialized Sep 10 10:37:41 duet3 DuetControlServer[2552]: [warn] Restarting transfer becaus Sep 10 10:37:41 duet3 DuetControlServer[2552]: [fatal] Could not connect to Duet Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Failed with result Sep 10 10:37:41 duet3 systemd[1]: Failed to start Duet Control Server. Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec= Sep 10 10:37:41 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j Sep 10 10:37:41 duet3 systemd[1]: Stopped Duet Control Server. Sep 10 10:37:41 duet3 systemd[1]: Starting Duet Control Server... Sep 10 10:37:41 duet3 DuetControlServer[2565]: Duet Control Server v3.3.0 Sep 10 10:37:41 duet3 DuetControlServer[2565]: Written by Christian Hammacher fo Sep 10 10:37:41 duet3 DuetControlServer[2565]: Licensed under the terms of the G Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Settings loaded Sep 10 10:37:42 duet3 DuetControlServer[2565]: [info] Environment initialized
Is there a way to extract all the sys files and macros (did not find anything on the SD-Card)? I could at least reflash it without losing everything
-
@com3 If you want to use 3.4 you will need to switch to the unstable repo feed. See: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Software_Installation
and the section on using beta software.
-
@gloomyandy thanks a lot, that worked!!