Duet3D System won't turn on now

you need an sudo apt updatein there before the upgrade/reinstall.

Danal

Ahh... good catch. It will actually be apt-get so, from this point:

sudo apt-get update
sudo apt-get install --reinstall duetsoftwareframework

apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'

@Danal said in Duet3D System won't turn on now:

. It will actually be apt-get so,

apt-get is the old syntax, but still works. might as well get with the times

Jim46

Wonderful guys!
I now have:
duetcontrolserver 1.2.5.0
duetruntime 1.2.5.0
duetsd 1.0.5
duetsoftwareframework 1.2.5.0
duettools 1.2.5.0
duetwebcontrol 2.0.7-1
duetwebserver 1.2.3.1

BTW, how do you capture part of he PuTTy screen as Danal shows in his "This is what I get: " screen shot above?
Thanks again,
Jim

@Jim46 said in Duet3D System won't turn on now:

how do you capture part of he PuTTy screen

just drag and select with the mouse; it copies to the clipboard automatiacally.

then paste and use the code formatting button (in the forum's editor when replying)

Jim46

Yep, I was able to highlight an area I wanted to copy, the following steps didn't work.
What does the S with line mean? Then how does the </> work? I get newline error msgs.
Then what does the chain link symbol mean? I think I need a beer!

Danal

S with line = ~~strike through text~~ Highlight the text (with mouse) and click it.

</> really just types three backticks for you, on two different lines, and places the cursor between those two lines so you can paste. You can type the three backticks yourself if you wish.

Danal

OK, we've gotten past the flash once a second, and we've got you on current releases.

Are you able to connect to DWC?

If not, can you please verify IP address, as shown way above?

Jim46

Thanks for the comments and advice.
Presently, RPi4 is connected to the SunFounder 10.1 touch screen. The Pi is connected to the Duet3d. 12v Power comes to the SF screen. It connects to the Pi. The Pi is ribbon cable connected to the Duet3d. There is no SD card in the Duet3d. The Pi has its card installed.
The Duet has UBS power 5v coming in from a UBS plug on a power-strip. I've run it with no UBS power going to the Duet3d or having UBS power going into the Duet3d.
I've verified the IP address on my router. It shows RPI4 and the IP number I'm using.
I'm using a new Firefox download.
I load in the IP address in the search bar and the Duet Web Control 2 comes up and quickly says Failed to Connect 192.168.1.xxx, DCS unavailable.

I've also done this w/o the SF screen being attached. Same result. I've also opened up the browser using Pi on the SF screen and input the IP. The Duet Web Control comes up and gives the same result.

Above dc42 mentioned differing version of RRF and DCS being an issue. With recent results on PuTTy is that still an issue? I certainly don't understand why progress is hampered.
Any miracles available?

Jim46

I seems to have UBS (Union Bank System) on the brain rather than the USB.... duh!

@Jim46 said in Duet3D System won't turn on now:

DCS unavailable.

what does service duetcontrolserver statussay from the ssh?

Danal

@Jim46 said in Duet3D System won't turn on now:

With recent results on PuTTy is that still an issue?

You are on correct releases. No issues there.

Just a tiny modification to what bearer asked; please show us two commands:

sudo service duetcontrolserver restart
sudo service duetcontrolserver status
● duetcontrolserver.service - Duet Control Server
   Loaded: loaded (/lib/systemd/system/duetcontrolserver.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-03-29 18:07:24 CDT; 6s ago
 Main PID: 17210 (DuetControlServ)
    Tasks: 19 (limit: 4915)
   Memory: 17.9M
   CGroup: /system.slice/duetcontrolserver.service
           └─17210 /opt/dsf/bin/DuetControlServer

Mar 29 18:07:24 duet3 systemd[1]: Started Duet Control Server.
Mar 29 18:07:25 duet3 DuetControlServer[17210]: Duet Control Server v1.2.5.0
Mar 29 18:07:25 duet3 DuetControlServer[17210]: Written by Christian Hammacher for Duet3D
Mar 29 18:07:25 duet3 DuetControlServer[17210]: Licensed under the terms of the GNU Public License Version 3
Mar 29 18:07:25 duet3 DuetControlServer[17210]: [info] Settings loaded
Mar 29 18:07:25 duet3 DuetControlServer[17210]: [info] Environment initialized
Mar 29 18:07:25 duet3 DuetControlServer[17210]: [info] Connection to Duet established
Mar 29 18:07:25 duet3 DuetControlServer[17210]: [info] IPC socket created at /var/run/dsf/dcs.sock

Jim46

Hi All ,
Here is what I get processing the two commands requested.
I'm still not getting the method you sue to capture the screen. So, here's another pic. I hope you can read it. On a side note, you all are world class with this program. I'd like to catch up a little. Where would you suggest I go to learn this rather quickly?
Cheers,
Jim

Doesn't really say why its not starting. But the only thing that should keep it from starting is not finding the Duet3. Maybe its time for a picture of how its connected?

Jim46

![0_1585597426269_IMG_5078.JPG](Uploading 100%) ![0_1585597463081_IMG_5079.JPG](Uploading 100%)

Here are two shots of my setup. The Duet is powered by the USB from a power strip. The SunFounder is powered by its plug in the same power strip. The Pi4 is powered by a connection to the SF board.
The latest message from the Duet Web Control 2 is "Failed to connect to IP, Network error".
Also, this Duet messaging system is not showing the Preview. WError?
Jim

Jim46

Okay here are the shots. I hope they help.
J

Jim46

By any chance is this indicative of a bad Duet board?

dc42

We need to know whether the Duet is running RRF. With the Duet connected via USB to a PC by a suitable cable (one that connects the data pins, not just power), does the USB port show up on the PC? If so, does it respond to sending M115?

Jim46

Hi DC. I'm not sure of he answer to your question. This is the cable connected from power strip to the Duet. Perhaps this pic will help?
Thanks,
j

Plug it back in the Pi and check if you have a /dev/ttyACM0 device. Connect to it with your serial terminal of choice and send it M115 to see if the Duet board responds.

if the above didn't make sense, just copy and paste the commands below and share the results

lsusb
stty -F /dev/ttyACM0 57600 raw -echo && { 
cat /dev/ttyACM0 & PID=$! 
echo "M115" > /dev/ttyACM0
sleep 0.5s ; kill $PID ; wait $PID
}

(edit: for those who finds the thread later - the above assumes micro usb of Duet is connected to the Pi)