"DCS is not started" error - Duet3
-
The Diag-LED is still always dimm. I tried with and without the SD card, Plugged into the PC or a Phonecharger... no change
-
@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.
-
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... -
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?
-
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.
-
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!
-
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 endI didn´t kwon that unfortunately...
But now everything works, and I have some more knowlage for next time 
Thanks again for your help!
