Posts made by Neufra

@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!

Everything on the softwareside works perfectly now!

Thanks everyone for your help!

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

I´ll make my configs now.

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?

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?

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...

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?

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

@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?

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":

And this is the Problem in BOSSA:

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.

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?

ohhh, I overlooked that. Thanks
Edit: now the reversing of the motor works!

; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"MGN-Cube"                        ; set printer name
M667 S1                                 ; select CoreXY mode

; Network
M552 S1                                 ; enable network
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

; Drives
M569 P0 S0                              ; physical drive 0 goes forwards X
M569 P1 S0                              ; physical drive 1 goes forwards Y
M569 P2 S0                              ; physical drive 2 goes forwards Z-L
M569 P3 S0                              ; physical drive 3 goes forwards Z-R
M560 P4 S1                              ; physical drive 4 goes forwards E
M560 P5 S0                              ; physical drive 5 goes forwards Z
M584 X0 Y1 Z2:5 E3                      ; two Z motors connected to driver outputs Z and E0
M671 X-60:360 Y150:150 S15              ; leadscrews at left (connected to Z) and right (connected to E1) (of X axis)
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
M92 X200.00 Y200.00 Z4266.67 E420.00    ; set steps/mm
M566 X900.00 Y900.00 Z12 E120.00        ; set jerk (mm/min)
M203 X6000.00 Y6000.00 Z90 E1200.00     ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z50 E250.00        ; set accelerations (mm/s^2)
M906 X800 Y800 Z1600 E800 I30           ; set motor currents (mA) and motor idle factor in percent
M84 S5                                  ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                        ; set axis min
M208 X300 Y300 Z365 S0                  ; set axis max

; Endstops
M574 X1 Y1 S1                           ; set active high endstops
M574 Z1 S2                              ; set endstop controlled by probe

; Z-Probe
M558 P1 H5 F120 T6000                   ; set Z probe type to IR-Probe and the dive height + speed
G31 P500 X0 Y0 Z2.5                     ; set Z probe trigger value, offset and trigger height
M557 X0:280 Y5:300 S80                  ; define mesh grid

; Heaters
M307 H0 B0 S1.00                        ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4725 C7.060000e-8 R4700             ; set thermistor + ADC parameters for heater 0
M143 H0 S120                            ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.060000e-8 R4700             ; set thermistor + ADC parameters for heater 1
M143 H1 S280                            ; set temperature limit for heater 1 to 280C

; Fans
M106 P0 S0 I0 F500 H-1                  ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T50               ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0                        ; define tool 0
G10 P0 X0 Y0 Z0                         ; set tool 0 axis offsets
G10 P0 R0 S0                            ; set initial tool 0 active and standby temperatures to 0C

; Custom Configuration

well, DuetWebControl asks me the following, after any change in config.g:

Reset board?
Would you like to restart your board to apply the updated configuration? 

I click "yes" there.
And on top of the config.g editor it says:

0:/sys/config.g

Your command gives me that:

M98 P"/sys/config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Writing to file: 4 S1
Done saving file.
Error: Bad command: 560 P5 S1

No. That´s not what I mean. The motor works, independently of the connector direction. But I can´t change the motor direction through confi.g, only by reversing the connector.

The motor works now, I can´t reverse it, but it works. (I just flipped the connector)

Soo, disconecting the duex doesn´t seem to change anything, the Motor connected to the E0 output still doesn´t move.

About the thermistors, I put in the correct values for the Hotends.
(I have this heater for my bed. I will contact their support and ask them about the thermistor type!)

I don´t know wich specific type of thermistor my bed has, it just says: "Thermistor 100k". (My hotends have those "Semitec-104gt-2" thermistors you mentioned)
When I disconect the duex, do I have to change something in the firmware as well?