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

    [3.2-beta4] Upgrade error

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    6
    165
    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.
    • MartinNYHCundefined
      MartinNYHC
      last edited by

      Just tried to upgrade to 3.2-beta4 via SBC

      Setting up reprapfirmware (3.2.0-beta4-1) ...
      Sending update request to DCS... Error: Failed to send update request
      Unhandled exception. System.Threading.Tasks.TaskCanceledException: A task was canceled.
         at DuetAPIClient.BaseConnection.PerformCommand[T](BaseCommand command, CancellationToken cancellationToken) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPIClient/BaseConnection.cs:line 188
         at DuetControlServer.Program.CheckForAnotherInstance() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 306
         at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 84
         at DuetControlServer.Program.<Main>(String[] args)
      Aborted
      
      1 Reply Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators
        last edited by

        Please try to run M997 from DWC. I'll have a look at this problem.

        Duet software engineer

        1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators
          last edited by

          It looks like DSF is being shut down when the update request is sent over. Can you connect over SSH or open a terminal on the Pi and send me the output of journalctl -u duetcontrolserver -e (provided you didn't restart the Pi in the meantime)?

          Duet software engineer

          1 Reply Last reply Reply Quote 0
          • MartinNYHCundefined
            MartinNYHC
            last edited by

            Did a M997.

            -- Logs begin at Fri 2020-11-27 11:07:45 CET, end at Fri 2020-11-27 12:06:43 CET. --
            Nov 27 11:07:48 duet3 systemd[1]: Started Duet Control Server.
            Nov 27 11:07:51 duet3 DuetControlServer[360]: Duet Control Server v3.2.0-beta4
            Nov 27 11:07:51 duet3 DuetControlServer[360]: Written by Christian Hammacher for Duet3D
            Nov 27 11:07:51 duet3 DuetControlServer[360]: Licensed under the terms of the GNU Public License Version 3
            Nov 27 11:07:52 duet3 DuetControlServer[360]: [info] Settings loaded
            Nov 27 11:07:53 duet3 DuetControlServer[360]: [info] Environment initialized
            Nov 27 11:07:53 duet3 DuetControlServer[360]: [info] Connection to Duet established
            Nov 27 11:07:53 duet3 DuetControlServer[360]: [info] IPC socket created at /var/run/dsf/dcs.sock
            Nov 27 11:07:59 duet3 DuetControlServer[360]: [warn] IPC#4: Client with outdated protocol version connected (got 7, want 10)
            Nov 27 11:08:36 duet3 DuetControlServer[360]: [info] System time has been changed
            Nov 27 11:23:38 duet3 DuetControlServer[360]: [warn] IPC#35: Client with outdated protocol version connected (got 8, want 10)
            Nov 27 11:23:38 duet3 DuetControlServer[360]: [warn] IPC#36: Client with outdated protocol version connected (got 8, want 10)
            Nov 27 12:06:18 duet3 DuetControlServer[360]: [info] Flashing IAP binary
            Nov 27 12:06:18 duet3 DuetControlServer[360]: [info] Flashing RepRapFirmware
            Nov 27 12:06:25 duet3 DuetControlServer[360]: [info] Verifying checksum
            Nov 27 12:06:28 duet3 DuetControlServer[360]: [info] Firmware update successful
            Nov 27 12:06:28 duet3 DuetControlServer[360]: [info] Starting macro file config.g on channel Trigger
            
            chrishammundefined 1 Reply Last reply Reply Quote 0
            • chrishammundefined
              chrishamm administrators @MartinNYHC
              last edited by

              @MartinNYHC The last firmware update was successful and I think the log confirms my assumption. There is no trace of the previous M997 call sent by DCS before your manual firmware update.

              I'll develop a change in DCS to prevent this problem in the future.

              Duet software engineer

              1 Reply Last reply Reply Quote 0
              • MartinNYHCundefined
                MartinNYHC
                last edited by

                Alright, thanks!

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