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

    Duet 3 DCS not starting / Diag light 1hz

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    2
    5
    296
    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.
    • Cassiopeiaundefined
      Cassiopeia
      last edited by Cassiopeia

      So I had a perfectly running Duet3 when i tried to update to RRF3.4beta2 through the DWC. (From Stable 3.3)

      Result was a loop of DWC saying its installing the Firmware. Honestly: I dont remember if it finished or if i killed the power. But it was at least running for 10-15 minutes.

      So now i am stuck with:
      DCS is not started.JPG

      my setup is a Duet 3 6HC with a Rpi4 connect (so SBC mode) the following log is created by 5V -> SBC by the Duet3

      sudo journalctl -u duetcontrolserver

      gives me the following

      -- Logs begin at Mon 2021-08-23 18:41:58 BST, end at Mon 2021-08-23 20:08:11 BST. --
Aug 23 19:11:08 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:10 duet3 DuetControlServer[421]: Duet Control Server v3.3.0
Aug 23 19:11:10 duet3 DuetControlServer[421]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:10 duet3 DuetControlServer[421]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:10 duet3 DuetControlServer[421]: [info] Settings loaded
Aug 23 19:11:11 duet3 DuetControlServer[421]: [info] Environment initialized
Aug 23 19:11:11 duet3 DuetControlServer[421]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:11 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1.
Aug 23 19:11:11 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:11 duet3 DuetControlServer[558]: Duet Control Server v3.3.0
Aug 23 19:11:11 duet3 DuetControlServer[558]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:11 duet3 DuetControlServer[558]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Settings loaded
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Environment initialized
Aug 23 19:11:12 duet3 DuetControlServer[558]: [warn] Restarting transfer because the Duet received a bad respon
Aug 23 19:11:12 duet3 DuetControlServer[558]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:12 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 2.
Aug 23 19:11:12 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:13 duet3 DuetControlServer[570]: Duet Control Server v3.3.0
Aug 23 19:11:13 duet3 DuetControlServer[570]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:13 duet3 DuetControlServer[570]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Settings loaded
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Environment initialized
Aug 23 19:11:14 duet3 DuetControlServer[570]: [fatal] Could not connect to Duet (Timeout while waiting for tran
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:14 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 3.
Aug 23 19:11:14 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:15 duet3 DuetControlServer[590]: Duet Control Server v3.3.0
Aug 23 19:11:15 duet3 DuetControlServer[590]: Written by Christian Hammacher for Duet3D
lines 1-41...skipping...
-- Logs begin at Mon 2021-08-23 18:41:58 BST, end at Mon 2021-08-23 20:08:11 BST. --
Aug 23 19:11:08 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:10 duet3 DuetControlServer[421]: Duet Control Server v3.3.0
Aug 23 19:11:10 duet3 DuetControlServer[421]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:10 duet3 DuetControlServer[421]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:10 duet3 DuetControlServer[421]: [info] Settings loaded
Aug 23 19:11:11 duet3 DuetControlServer[421]: [info] Environment initialized
Aug 23 19:11:11 duet3 DuetControlServer[421]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:11 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1.
Aug 23 19:11:11 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:11 duet3 DuetControlServer[558]: Duet Control Server v3.3.0
Aug 23 19:11:11 duet3 DuetControlServer[558]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:11 duet3 DuetControlServer[558]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Settings loaded
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Environment initialized
Aug 23 19:11:12 duet3 DuetControlServer[558]: [warn] Restarting transfer because the Duet received a bad response (header)
Aug 23 19:11:12 duet3 DuetControlServer[558]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:12 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 2.
Aug 23 19:11:12 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:13 duet3 DuetControlServer[570]: Duet Control Server v3.3.0
Aug 23 19:11:13 duet3 DuetControlServer[570]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:13 duet3 DuetControlServer[570]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Settings loaded
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Environment initialized
Aug 23 19:11:14 duet3 DuetControlServer[570]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:14 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 3.
Aug 23 19:11:14 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:15 duet3 DuetControlServer[590]: Duet Control Server v3.3.0
Aug 23 19:11:15 duet3 DuetControlServer[590]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:15 duet3 DuetControlServer[590]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:15 duet3 DuetControlServer[590]: [info] Settings loaded
Aug 23 19:11:15 duet3 DuetControlServer[590]: [info] Environment initialized
Aug 23 19:11:16 duet3 DuetControlServer[590]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:16 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 4.
lines 1-49

      The log shows the same when i power Duet 3 and the RPi4 both with external 5V. Duet via EXT 5V pin ( I am using PS_ON with an SSR to turn 24V PSU on and OFF)

      If have been searching the forum for hours now...have reinstalled the SD card several times nothing helps. (including apt get update/upgrade etc...)

      I have flashed the board succesfully via bossa (Windows USB)
      M115 gives me:

      m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-08-03 12:42:44<LF>ok<LF>

      I dont know what else i can do?
      The Diag light flashes with 1hz which it also has been when the duet was working..

      The only thing i havent done is operating the board in Standalone mode.

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by Phaedrux

        When running with a Pi, in order to use beta firmware you must also update the DCS to the beta using the unstable package server.

        See here on how to switch from stable to unstable branch.
        https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#unstable-package-feed

        At this point it may be easiest to flash the board back to 3.3 so that DCS can communicate with it again, and then do the unstable branch update on the Pi.

        Z-Bot CoreXY Build | Thingiverse Profile

        Cassiopeiaundefined 2 Replies Last reply Reply Quote 0
        • Cassiopeiaundefined
          Cassiopeia @Phaedrux
          last edited by

          @phaedrux thx for your quick response i will try this next. (and give feedback)

          FYI for everyone else reading this thread. Just for completion of troubleshooting:
          The standalone mode works fine with the Beta.bin in /sys and the provided "Beta" DWC files in /www

          1 Reply Last reply Reply Quote 0
          • Cassiopeiaundefined
            Cassiopeia @Phaedrux
            last edited by

            @phaedrux THX.. i should have asked earlier 😞 would have saved me couple of hours 😛 ...well i followed the unstable wiki and changed the branch and apt update & upgrade now DWC is working again. Didnt even had to flash 3.3 again. BIG THX

            1 Reply Last reply Reply Quote 1
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by

              Also, the diag light blinking at 1hz is a sign it's normal. Like a heartbeat.

              Z-Bot CoreXY Build | Thingiverse Profile

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