SOLVED "DCS is not started" error - Duet3



  • Hi there,
    I got my duet3 today.
    During the setup, I ran into the following problem:

    https://drive.google.com/file/d/1nAlHIK9otb16Q5Y07_CqbHby2KdrDjNd/view?usp=sharing
    (it´s a Video, showing the Problem)

    I read about this in other posts.
    They always asked for these "commands":
    (I can´t do "M115")

    pi@duet3:~ $ apt list duet\*
    Listing... Done
    duetcontrolserver/stable,now 3.1.1 armhf [installed,automatic]
    duetruntime/stable,now 3.1.1 armhf [installed,automatic]
    duetsd/stable,now 1.0.6 all [installed,automatic]
    duetsoftwareframework/stable,now 3.1.1 armhf [installed]
    duettools/stable,now 3.1.1 armhf [installed,automatic]
    duetwebcontrol/stable,now 3.1.1 all [installed,automatic]
    duetwebserver/stable,now 3.1.0 armhf [installed,automatic]
    
    pi@duet3:~ $ sudo journalctl -u duetcontrolserver -e
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: Licensed under the terms of the G
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Settings loaded
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Environment initialized
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [fatal] Could not connect to Duet
    Aug 17 12:34:20 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
    Aug 17 12:34:25 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:25 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Duet Control Server v3.1.1
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Written by Christian Hammacher fo
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Licensed under the terms of the G
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: [info] Settings loaded
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [info] Environment initialized
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [fatal] Could not connect to Duet
    Aug 17 12:34:27 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
    Aug 17 12:34:32 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:32 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Duet Control Server v3.1.1
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Written by Christian Hammacher fo
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Licensed under the terms of the G
    lines 979-1001/1001 (END)
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: Licensed under the terms of the GNU Public License Vers
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Settings loaded
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Environment initialized
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [fatal] Could not connect to Duet (Board is not availab
    Aug 17 12:34:20 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is
    Aug 17 12:34:25 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:25 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Duet Control Server v3.1.1
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Written by Christian Hammacher for Duet3D
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Licensed under the terms of the GNU Public License Vers
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: [info] Settings loaded
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [info] Environment initialized
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [fatal] Could not connect to Duet (Board is not availab
    Aug 17 12:34:27 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is
    Aug 17 12:34:32 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:32 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Duet Control Server v3.1.1
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Written by Christian Hammacher for Duet3D
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Licensed under the terms of the GNU Public License Vers
    lines 979-1001/1001 (END)
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: Licensed under the terms of the GNU Public License Version 3
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Settings loaded
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [info] Environment initialized
    Aug 17 12:34:20 duet3 DuetControlServer[3391]: [fatal] Could not connect to Duet (Board is not available (no header))
    Aug 17 12:34:20 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
    Aug 17 12:34:25 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 157.
    Aug 17 12:34:25 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:25 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Duet Control Server v3.1.1
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Written by Christian Hammacher for Duet3D
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: Licensed under the terms of the GNU Public License Version 3
    Aug 17 12:34:26 duet3 DuetControlServer[3405]: [info] Settings loaded
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [info] Environment initialized
    Aug 17 12:34:27 duet3 DuetControlServer[3405]: [fatal] Could not connect to Duet (Board is not available (no header))
    Aug 17 12:34:27 duet3 systemd[1]: duetcontrolserver.service: Succeeded.
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart.
    Aug 17 12:34:32 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 158.
    Aug 17 12:34:32 duet3 systemd[1]: Stopped Duet Control Server.
    Aug 17 12:34:32 duet3 systemd[1]: Started Duet Control Server.
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Duet Control Server v3.1.1
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Written by Christian Hammacher for Duet3D
    Aug 17 12:34:32 duet3 DuetControlServer[3419]: Licensed under the terms of the GNU Public License Version 3
    

    The "diag"-LED is constantly on! (but only very dimm/weak)!

    Any ideas what to do now?



  • @Neufra said in "DCS is not started" error - Duet3:

    (I can´t do "M115")

    even if you connect to the micro usb of the the duet?



  • No.
    I can´t acces the duet with "BOSSA".

    I tried it in Standalone-mode (R pi dissabled [removed "5V -> SBC" jumper] and SD card, with the mandatory files on it, inside the duet.) aswell as with the pi enabled. (and no SD card in the duet)

    edit:
    the board doesn´t show up in "BOSSA".
    The erase-jumper is set, and I tried pressing the reset button.



  • Micro usb serves two purposes; usb serial console when the firmware is working. Connect using any terminal software to execute g-codes like M115.

    And secondly after executing M999 P"ERASE" or setting the erase jumper the board should respond to bossa (mind you there have been some reports of bugs on various operating systems, so SAM-BA may be a btter option depending on the actual error you get from bossa).

    use device manager on windows or lsusb on linux to try and identify what the board is present as, if anything.

    https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond

    ☝ while targetd at duet2, its mostly translatable to a duet3 in stand alone mode.



  • wich board do I have to use in "SAM-BA" for the duet3 ?

    This is what I get if I use the "Board for the duet 2":
    samba.PNG

    And this is the Problem in BOSSA:
    bossa.PNG



  • never had to use sam-ba for that so can't say for sure which chip to choose. in bossa its ATSAME70x20

    maybe its worth trying to connect the duet to to the Pi instead, and just run bossa from there, seems to have a higher success rate. seems to be a usb issue on the computer with the warning icon there.

    lazy way is to run wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash on the pi with the duet's micro usb connected to the pi (it'll download, compile bossac and flash the 3.1.1 firmware from /opt/dsf/sd/sys/ all for you)

    did you update to 3.0 before trying 3.1.1?



  • @bearer said in "DCS is not started" error - Duet3:

    wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash

    I get an Error with that command:

    pi@duet3:~ $ wget https://pastebin.com/raw/Wa1kYf3G -O - | tr -d "\r" | bash
    --2020-08-17 14:28:50--  https://pastebin.com/raw/Wa1kYf3G
    Resolving pastebin.com (pastebin.com)... 104.23.99.190, 104.23.98.190, 2606:4700                               :10::6817:62be, ...
    Connecting to pastebin.com (pastebin.com)|104.23.99.190|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [text/plain]
    Saving to: ‘STDOUT’
    
    -                       [ <=>                ]     897  --.-KB/s    in 0s
    
    2020-08-17 14:28:53 (3.53 MB/s) - written to stdout [897]
    
    Cloning into '/home/pi/BOSSA'...
    fatal: unable to access 'https://github.com/shumatech/BOSSA/': Could not resolve                                host: github.com
    bash: line 26: cd: /home/pi/BOSSA: No such file or directory
    make: *** No rule to make target 'bossac'.  Stop.
    /dev/ttyACM0 not found******
    
    

    I didn´t use version 3.0 first...
    How can I install it now?


  • administrators

    @Neufra said in "DCS is not started" error - Duet3:

    The "diag"-LED is constantly on! (but only very dimm/weak)!

    This is not right. What do you have plugged in to the Duet? Try with nothing plugged (including the Pi) and jsut powered with USB.



  • The Diag-LED is still always dimm. I tried with and without the SD card, Plugged into the PC or a Phonecharger... no change


  • administrators

    @Neufra with 5V USB power applied put a jumper on the Erase jumper, then take it back off and power cycle the board. It should not now show up as a BOSSA programming port. you then need to re flash the firmware on the board (use v3.1.1 from the github release).

    https://github.com/Duet3D/RepRapFirmware/releases

    After that it should then show up as a Duet 3 and the diag light should be flashing.



  • @T3P3Tony

    I get the same error on both 2 and 3 duets unless I use a specific micro usb cable which I have now set aside for just using on duet boards but with that cable connects 1st time ..may be of help?



  • I just tried many different things, including different cables, but I just can´t get a conection to the board.. I mean, BOSSA and SAM-BA show the serial port, but I get the same error massages as befor (the pictures further up).

    Is there something im just forgetting about?



  • @Neufra
    Is the board still in the enclosure or on the bench ...best have it on the bench nothing connected but usb honestly I have 10s of cables only 1 that works dunno why.. the others work with everything else I try them with.



  • the board is on my desk.
    Nothing except for the USB-cable, and the SD card is plugged in.

    The cable i´m currently using was included with my duet 2...
    I´ll try all of my other cables, maybe one of them works...



  • @Neufra

    Take the card out you dont need it in to flash the firmware



  • I took it out now. It didn´t change much.
    (and I´m still swapping cable around 👍 )

    @T3P3Tony said in "DCS is not started" error - Duet3:

    It should not now show up as a BOSSA programming port.

    But it does, why´s that?



  • Good News:
    it turned out, that the USB port I used was the Problem.
    After trying all of my micro-USB cables, I thougt: "okay let´s just try a diffrent USB-port!".

    Now the diag-LED is blinking as it shoud!

    Thanks for your help so far!

    What should I do now, in order not to "break" it again?



  • @Neufra

    You updated the firmware ? go to the online rep rap configuration tool and build your configs



  • I don´t know what I originaly did... I messed something up, and than nothing worked anymore 😞 !

    I´ll make my configs now.



  • @Neufra

    Follow the documentation and take your time make sure its all wired correctly following that documentation.



  • Everything on the softwareside works perfectly now!

    Thanks everyone for your help! 😁


  • administrators

    BTW I found out yesterday that "DCS is not started" is a misleading message. I also get it if DCS is unable to communicate with the Duet.



  • @Neufra said in "DCS is not started" error - Duet3:

    fatal: unable to access 'https://github.com/shumatech/BOSSA/': Could not resolve host: github.com

    thats odd, your Pi managed to resolve pastebin.com but not github.com - sounds like have some gremlins on your network. but it is good feedback to improve the scritpt:)

    /dev/ttyACM0 not found******

    just out of curiosity, was this with the same usb cable you succeeded with in the end?

    I didn´t use version 3.0 first...

    when you get a new duet with a pre 3.0 it will break compatibility with dsf without either manually updating to 3.0 before using apt upgrade, or use bossa or sam-ba after apt upgrades to 3.1.1. shame this isn't highlighted better.

    too bad about the series of unfortunate events sort of speak, but glad you got it sorted in the end 👍



  • @bearer said in "DCS is not started" error - Duet3:

    just out of curiosity, was this with the same usb cable you succeeded with in the end?

    no, I belive that was a different cable and the "non working USB-port".

    (It worked when I used a different USB - port. At first I used the port on the backside of my Keyboard (I use a "Corsair K70 LUX"), that woked with the duet2, but not with the 3! In the end, I plugged the duet directly into the front of my PC and using the included cable from the duet2!)

    @bearer said in "DCS is not started" error - Duet3:

    when you get a new duet with a pre 3.0 it will break compatibility with dsf without either manually updating to 3.0 before using apt upgrade, or use bossa or sam-ba after apt upgrades to 3.1.1. shame this isn't highlighted better.
    too bad about the series of unfortunate events sort of speak, but glad you got it sorted in the end

    I didn´t kwon that unfortunately...
    But now everything works, and I have some more knowlage for next time 👍 😀

    Thanks again for your help!


Log in to reply