Duet3D System won't turn on now

Jim46

I ran it and got new results.. I wanted to copy and paste the results to this page, but it acted strange. How did you do the screen above with the scrolling function?
So, I ran wget again and got different results again. I'm post these below here:

what do you think of these?

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

what do you think of these?

I'm not sure, but I suspect the Duet3d guys will have some input now as we have a clear fault to address. Maybe you can try another USB cable while waiting for them to catch up to the development.

Jim46

above the Done in 3.467 seconds it said,
bash
bash Duet 3 6HC
erase flash

done in 3.4xxx seonds

Jim46

Okay I switched to a short USB cable

The line that said SAM-BA operation failed is what I was refering to, the firmware download failed for an unknown reason, and I suspect dc42 knows more than me about that bit. But as I said see if another USB cable gives a different output, and I'll change the flashing to include debugging output as well. If it still fails you'll have a file bossa.log in your home directory that may be of interest to the Duet3d guys.

Jim46

Bearer, thanks for sticking with me here. I've run lsusb on the Pi using a 12" cable between Pi and Duet instead of the 6' cable I used between my PC and the Duet. Any better info?

Hmm, lsusb shoud show you either
Bus 001 Device 008: ID 03eb:6124 Atmel Corp. at91sam SAMBA bootloader
or
Bus 001 Device 004: ID 1d50:60ee OpenMoko, Inc.

if the cable is okay; the latter is what you'll see once the firmware is successfully updated, until then it will show as the first entry. None of the entries would suggest the cable isn't working, or at least lacking the data connection.

Jim46

Hi, I reran the wget on the Pi with the short USB cable mentioned above, Here is the result:
The lsusb looks a lot like yours. Yet the results above it say no device found...doesn't sound great!

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

above it say no device found...doesn't sound great!

will never be any difference between just lsusb and the output at the end of the script wget downloads and runs btw; they do the exact same thing.

it could be the cable you changed to is one of those charging only type of cables, which you can easily enough test by going back to the one that partially worked.

Jim46

I dug up a 3rd 12' USB cable and reran wget. Here are the results. Progress?

Jim46

Opps 12" cable number 3

droftarts

@Jim46 I have little knowledge of the Raspberry Pi, but when it comes to flashing firmware to Duets... I wrote the documentation! The original issue seems to have been a corrupted firmware, and now you're trying to run a firmware update with Bossa on the Pi. But have you put a jumper on the ERASE pins (you know, the ones I thought you'd left a jumper on before), powered up the Duet for 5 seconds, powered down, removed the jumper, then tried updating the firmware? You may need to do this a few times; despite showing a Bossa port, the firmware sometimes seems quite tenacious. Also, make sure your Bossa version is 1.9.1, or the Duet 3 processor won't be supported.

Alternatively, switch to a Windows desktop and run Bossa from there. Always works first time for me on Windows. The Mac version of Bossa is broken for Duet 3, unfortunately.

Ian

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

I dug up a 3rd 12' USB cable and reran wget. Here are the results. Progress?

Bingo! you now have RRF3 3.0 running on your duet.

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

Also, make sure your Bossa version is 1.9.1

the script he ran builds it from git and sorts out everything (when the cable works:)

droftarts

@bearer Ah, that all happened while I was writing my post! Wow, this has been a journey. Well done to everyone for persevering, and especially to you for your knowledge.

What's the major learning from this thread, that I can document?

Ian

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

What's the major learning from this thread, that I can document?

that he didn't run M115 a week ago when asked to do so

.. anyways; hopefully he gets duetcontrolserver started and connected to duetwebcontrol; i believe the systemd unit will keep trying dcs, if not a reboot should get it going.

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

What's the major learning from this thread, that I can document?

come to think of it, its at least the 2nd time someone has said bossa failed because "file not found" when using the graphical version - partly why i figured copy/paste one line is a simpler instruction than installing software, setting options etc.

Jim46

Hi All, thank you for your amazing help. Based on what comes up now, it may be a break through. Here is what I see. BTW, I have tried M115 many times but nothing worked. Presently, YAT says I don't have a Serial Port available. Not sure how to see a list to see what is going on.

Right now I'm not able to look at Duet Web Control 2. Not sure why.
Do you think things are looking better

Jim46

Okay, it said Duet Web Control briefly before it brought up the raspberrypi screen above. Is this normal? if this is okay, is setting up the parameters to match my custom printer the next step?

Jim46

I would like to make the motors move to ensure what they are doing before I install them on the printer frame.

Danal

That screen looks great. YES, it is time to load your configuration. This is on the "system" tab.

You can make motors move. Reminder: POWER OFF when plugging or unplugging motors!!

X, Y and Z won't move until the printer is homed. Enter "M564 H0" to allow movement. Enter it in the "send code" line at the top. Some releases of DWC have a bug that you must push the "Send" button twice. It won't hurt anything to send this command more than once.

Also, your extruder motor will not turn until the extruder is hot. Enter "M302 P1" to allow cold extrudes.