Duet3D System won't turn on now
-
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? -
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? -
@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 -
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?
-
 
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 -
Okay here are the shots. I hope they help.
J -
By any chance is this indicative of a bad Duet board?
-
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?
-
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
M115to 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)
-
So sorry Bearer. Don't know how to do the ACM0 M115 line.
So I launched PuTTy and tried to execute the 7 lines of code in the black panel. Nothing was understood. I imagine I'm missing a basic understanding on how to start this. What should I do? -
Not sure what to tell you man, I specifically tried this with a raspberry pi and a duet board to make it as simple as copy and paste.
video didn't capture right clicking the selected text and choosing copy, nor right clicking once back in the ssh terminal to paste the text, but it works with the default setup (putty behaves in the same way, but the chrome ssh client was just easier to record as it was all in a single window)
@Jim46 said in Duet3D System won't turn on now:
Nothing was understood.
that also tells me nothing about what went wrong.
edit; copy/pasted the ssh session for those who can't view the video (with a slight change to commands)
pi@raspberrypi:~ $ lsusb Bus 001 Device 005: ID 1d50:60ed OpenMoko, Inc. Bus 001 Device 004: ID 0424:7800 Standard Microsystems Corp. Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ stty -F /dev/ttyACM0 57600 raw -echo && { > cat /dev/ttyACM0 & PID=$! > echo "M115" > /dev/ttyACM0 && > sleep 0.5s && kill $PID ; wait $PID > } [2] 829 FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1 [2]+ Terminated cat /dev/ttyACM0 pi@raspberrypi:~ $ -
Maybe you can try the documentation for the Duet 2; steps 1 though 5 should be the same for the Duet 3.
https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7 -
Hello,
I rebooted my PC and the Pi/Duet. The commands were now accepted. Here is what came back.
-
And that is with the Duet connected to the Pi with a USB cable?
Then you might need to try another cable, the Pi is not seeing the Duet.
-
Here's is my set up:
The Pi and Duet are connected by the ribbon cable. The Pi is connect to the router. The Pi is connected to the SunFounder Touch Screen. The SF runs on 12v. It then powers the Pi. It also powers the Duet via the Pi ribbon cable. The Duet can also be powered directly via USB using the cable above. It makes seems to make no difference to the to the Duet Web Control 2 (on my PC with Firefox) if the Duet is powered via the Pi/SF alone or via USB as far as I can tell. If I run the Duet Web Control off the Pi, I get the same result "Failed to connect to 192.168.1.xxx, DCS Unavailable."
With all your amazing help, the Duet still seems to be the issue. Yes? Which brings me back to the same question Is it a bad board? Hope not! -
Still not clear how the Duets usb port is connected; either from the micro usb port on the Duet to the Pi and run the little script posted - OR - connect the micro usb port on the Duet to your computer and follow the getting connected guide linked above.
(The goal of that is to find out if the board is working, which is also why another usb cable needs to be tested if they do not work as expected)
-
Here is the result of trying the M115 command using YAT. Device Manage (Windows 10) has no Yellow Triangles, The Generic USB showed the drive installed and that it is working. A new USB cable is connect directly to Duet microUSB port and a USB port on my PC. The Duet is no connected to the Pi at this point. There is no response to the YAT command.I've reconnect the Pi and Duet and left the Duet connect to the PC via USB cable. Ran YAT M115 command again. No reply.
