Duet3D System won't turn on now

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

A Former User

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)

Jim46

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?

A Former User

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.

https://streamable.com/2wq9j

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:~ $

A Former User

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

Jim46

Hello,
I rebooted my PC and the Pi/Duet. The commands were now accepted. Here is what came back.

A Former User

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.

Jim46

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!

A Former User

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)

Jim46

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.

NexxCat

@Jim46
The port name is shown as "BOSSA Program Port" in YAT, I believe that means the Duet is in programming mode, hence why it won't reply to gcode commands.

Hopefully this helps you to program the firmware onto it: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

droftarts

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

@Jim46
The port name is shown as "BOSSA Program Port" in YAT, I believe that means the Duet is in programming mode, hence why it won't reply to gcode commands.

Also, is the DIAG light flashing? (This indicates the firmware is running.) In your pictures earlier, it looks dimly lit (which it would be if there's a jumper on the erase pins, and not flashing). Also, it looks like you have a jumper on the 'erase' pins of the Duet! That's the pin next to the three 5V select pins. Remove it!

(Edited for clarity)

Ian

A Former User

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

Also, it looks like you have a jumper on the 'erase' pins of the Duet!

.. how about that ..!

Jim46

Hi Guys, here is a pic of the Duet3d powered by USB 2.0 from the PC It is how it was out of the box. As far as I can tell there is nothing on the erase pins near the Atmel D3M chip. Any place else a concern? I'm trying Nexxcat recommendation, but this is where I started with Tony helping remotely. I'll let you know what happens.
![0_1585762105791_IMG_5090.JPG](Uploading 100%)
I'm getting a server parsing error when I try to upload this photo. What's happening? I'll try to reboot and upload again.

Jim46

A Former User

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

I'm trying Nexxcat recommendation, but this is where I started with Tony helping remotely.

as long as the serial port is called BOSSA you will need to complete the firmware update procedure. If using the Bossa program doesn't help report back and I'll post instructions for using the command line version as that seems to help some struggling with the flashing.

I'm getting a server parsing error when I try to upload this photo. What's happening? I'll try to reboot and upload again.

I'm seeing a lot of that myself; reload the page and trying again usually sufficient.

Jim46

Trying the Duet Web Control process doesn't work as it says unable to connect as DCS is unavailable. So back to square one. what happens if you press the reset button?

A Former User

If you're trying Duet Web Control I presume you sorted out the firmware update issue and sending M115 to the board now gives you a response?

Jim46

Not really, the DWC isn't working. So I.'m dead in the water. The BOSSA is om y RPi, but all the files are empty. I tried to follow this procedure:
o update via USB (using a Raspberry Pi host):
Part1: Install bossa on the Pi with these commands:
sudo apt update && sudo apt install -y libwxgtk3.0-dev libreadline-dev
git clone https://github.com/shumatech/BOSSA
cd BOSSA
make
Part 2: Connect the Duet to the Pi.
Use a data capable USB cable from any port on the Pi to the Duet.
It is OK to power the Duet from only the USB (which implies the Pi has its own power)
It is OK to power the Duet with VIN
Do one or the other; do not power both ways.
If the Pi is part of a Duet 3 with ribbon cable, it is OK to leave this attached.
Part 3: Obtain firmware
If the Pi is part of a Duet 3, firmware will be in /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin

The Pi4 screen came back and said, bash /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin there is no such file or directory.
Looks like I need a simple and clear way to get past this stumbling block.
Jim

A Former User

DWC isn't going to work until the Duet stops showing up as a BOSSA serial port; so until that is fixed it will not function as this implies the firmware that makes the Duet function has been erased/corrupted.

If you now have the Duet connected to your Pi (edit: with the USB cable!) can you please run the command lsusb from the SSH shell on the Pi and confirm it has a line that says something like Bus 001 Device 008: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader the first part can vary a little.

If, and only if you do, we can proceed to flash the firmware from the Pi. (if you don't please copy paste or take a picture of what you do have)