• Tags
  • Documentation
  • Order
  • Register
  • Login
Duet3D Logo Duet3D
  • Tags
  • Documentation
  • Order
  • Register
  • Login

Duet3D System won't turn on now

Scheduled Pinned Locked Moved
General Discussion
11
107
4.9k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • undefined
    Jim46
    last edited by 1 Apr 2020, 17:45

    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?

    1 Reply Last reply Reply Quote 0
    • ?
      A Former User
      last edited by 1 Apr 2020, 17:50

      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?

      1 Reply Last reply Reply Quote 0
      • undefined
        Jim46
        last edited by 2 Apr 2020, 02:05

        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

        1 Reply Last reply Reply Quote 0
        • ?
          A Former User
          last edited by A Former User 4 Feb 2020, 02:50 2 Apr 2020, 02:15

          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)

          1 Reply Last reply Reply Quote 1
          • ?
            A Former User
            last edited by A Former User 4 Feb 2020, 05:04 2 Apr 2020, 02:44

            You can also try to run this command, it could work, but I can't say for sure as I don't have a Duet3 to test it with, but it will not do any harm at least.

            wget -q https://pastebin.com/raw/wekeLGhS -O - | tr -d '\r' | bash

            It will download a script I started earlier to automatically detect and recover a Duet connected to a Pi. This is how it looked when recovering a Duet 2 Meastro, it should look similar, but obviously with different filenames for you.

            pi@raspberrypi:~ $ wget -q https://pastebin.com/raw/wekeLGhS -O - | tr -d '\r' | bash
            Cloning into '/home/pi/BOSSA'...
            remote: Enumerating objects: 11, done.
            remote: Counting objects: 100% (11/11), done.
            remote: Compressing objects: 100% (10/10), done.
            remote: Total 1727 (delta 4), reused 5 (delta 1), pack-reused 1716
            Receiving objects: 100% (1727/1727), 1.15 MiB | 964.00 KiB/s, done.
            Resolving deltas: 100% (1318/1318), done.
            make: wx-config: Command not found
            make: wx-config: Command not found
            CPP APPLET src/WordCopyArm.cpp
            CPP COMMON src/Samba.cpp
            CPP COMMON src/Flash.cpp
            CPP COMMON src/D5xNvmFlash.cpp
            CPP COMMON src/D2xNvmFlash.cpp
            CPP COMMON src/EfcFlash.cpp
            CPP COMMON src/EefcFlash.cpp
            CPP COMMON src/Applet.cpp
            CPP COMMON src/WordCopyApplet.cpp
            CPP COMMON src/Flasher.cpp
            CPP COMMON src/Device.cpp
            CPP COMMON src/PosixSerialPort.cpp
            CPP COMMON src/LinuxPortFactory.cpp
            CPP BOSSAC src/bossac.cpp
            CPP BOSSAC src/CmdOpts.cpp
            LD bin/bossac
            2020-04-02 03:43:22 URL:https://github-production-release-asset-2e65be.s3.amazonaws.com/15792831/8d0ad700-4b31-11ea-9191-66b95646e549?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20200402%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20200402T024223Z&X-Amz-Expires=300&X-Amz-Signature=2a797e70c703b8a93dec6934054f655c9ce980cd6a4bf0baa19e3ed6b6bf13c6&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DDuetMaestroFirmware.bin&response-content-type=application%2Foctet-stream [412148/412148] -> "/home/pi/DuetMaestroFirmware.bin" [1]
            Erase flash
            
            Done in 4.605 seconds
            Write 412148 bytes to flash (805 pages)
            [==============================] 100% (805/805 pages)
            Done in 6.139 seconds
            Verify 412148 bytes of flash
            [==============================] 100% (805/805 pages)
            Verify successful
            Done in 6.172 seconds
            Set boot flash true
            FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1
            pi@raspberrypi:~ $
            
            1 Reply Last reply Reply Quote 0
            • undefined
              Jim46
              last edited by 2 Apr 2020, 19:44

              Hi Bearer,
              I've tried to run both suggestions. Here are the results. 1) is from PuTTy on my PC. 2) is from RPi4. The Duet is connected to the Pi with the ribbon cable and the USB cable from the Duet to the Pi. Hope this is useful:

              IMG_5092 (3024 x 2268).jpg IMG_5091 (3024 x 2268).jpg

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by 2 Apr 2020, 19:48

                Lets go with the last setup; we should make that work. Try it again.

                1 Reply Last reply Reply Quote 0
                • undefined
                  Jim46
                  last edited by 2 Apr 2020, 19:50

                  Okay, will do now.. thank you. best way to try use PuTTy or on the Pi?

                  ? 1 Reply Last reply 2 Apr 2020, 19:53 Reply Quote 0
                  • ?
                    A Former User @Jim46
                    last edited by A Former User 4 Feb 2020, 19:54 2 Apr 2020, 19:53

                    @Jim46 My bad, either should work (i mistook the first picture). Putty is fine if its easier, both run the commands on the Pi.

                    (But we're after running the wget blah blah... command again)

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      Jim46
                      last edited by 2 Apr 2020, 19:54

                      Okay, I'll rerun the wget line on PuTTy now

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Jim46
                        last edited by 2 Apr 2020, 20:12

                        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:
                        IMG_5093.JPG
                        what do you think of these?

                        ? 1 Reply Last reply 2 Apr 2020, 20:14 Reply Quote 0
                        • ?
                          A Former User @Jim46
                          last edited by 2 Apr 2020, 20:14

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

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            Jim46
                            last edited by 2 Apr 2020, 20:16

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

                            done in 3.4xxx seonds

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              Jim46
                              last edited by 2 Apr 2020, 20:19

                              Okay I switched to a short USB cable

                              1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User
                                last edited by 2 Apr 2020, 20:25

                                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.

                                undefined 1 Reply Last reply 6 May 2020, 18:42 Reply Quote 0
                                • undefined
                                  Jim46
                                  last edited by 2 Apr 2020, 20:35

                                  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?
                                  IMG_5094.JPG

                                  1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User
                                    last edited by A Former User 4 Feb 2020, 20:38 2 Apr 2020, 20:38

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Jim46
                                      last edited by 2 Apr 2020, 20:57

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

                                      ? undefined 2 Replies Last reply 2 Apr 2020, 21:02 Reply Quote 0
                                      • ?
                                        A Former User @Jim46
                                        last edited by 2 Apr 2020, 21:02

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

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          Jim46
                                          last edited by 2 Apr 2020, 21:18

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

                                          ? 1 Reply Last reply 2 Apr 2020, 21:27 Reply Quote 0
                                          68 out of 107
                                          • First post
                                            68/107
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA