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

    Trouble with Duet 3 6HC Raspberry pi setup

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    14
    728
    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.
    • amostolundefined
      amostol @Phaedrux
      last edited by

      @phaedrux Okay I did the sudo apt update and upgrade, then restarted everything, but it made no difference.

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you send m122 and post the results?

        Z-Bot CoreXY Build | Thingiverse Profile

        amostolundefined 2 Replies Last reply Reply Quote 0
        • amostolundefined
          amostol @Phaedrux
          last edited by

          @phaedrux
          m122
          === Diagnostics ===
          RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later
          Board ID: 08DJM-956BA-NA3TJ-6JTDL-3SS6J-9TB2VUsed output buffers: 1 of 40 (10 max)
          === RTOS ===
          Static ram: 154572
          Dynamic ram: 160848 of which 52 recycled
          Exception stack ram used: 216
          Never used ram: 77528
          Tasks: NETWORK(ready,2076) HEAT(blocked,1412) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,5036) IDLE(ready,80)
          Owned mutexes:
          === Platform ===
          Last reset 14:55:08 ago, cause: software
          Last software reset at 2021-05-01 19:00, reason: User, spinning module LinuxInterface, available RAM 77248 bytes (slot 1)
          Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
          Error status: 0
          Free file entries: 10
          SD card 0 not detected, interface speed: 37.5MBytes/sec
          SD card longest block write time: 0.0ms, max retries 0
          MCU temperature: min 48.9, current 49.4, max 50.1
          Supply voltage: min 22.7, current 22.8, max 22.8, under voltage events: 0, over voltage events: 0, power good: yes
          12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0
          Driver 0: standstill, reads 13874, writes 14 timeouts 0, SG min/max 0/0
          Driver 1: standstill, reads 13877, writes 11 timeouts 0, SG min/max 0/0
          Driver 2: standstill, reads 13875, writes 14 timeouts 0, SG min/max 0/0
          Driver 3: standstill, reads 13875, writes 14 timeouts 0, SG min/max 0/0
          Driver 4: standstill, reads 13876, writes 14 timeouts 0, SG min/max 0/0
          Driver 5: standstill, reads 13876, writes 14 timeouts 0, SG min/max 0/0
          Date/time: 2021-05-02 09:56:24
          Slowest loop: 3.56ms; fastest: 0.14ms
          === Move ===
          Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
          Bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
          === AuxDDARing ===
          Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
          === Heat ===
          Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          === GCodes ===
          Segments left: 0
          Movement lock held by null
          HTTP* is ready with "M122" in state(s) 0
          Telnet is idle in state(s) 0
          File is idle in state(s) 0
          USB is idle in state(s) 0
          Aux is assembling a command in state(s) 0
          Trigger* is idle in state(s) 0
          Queue is idle in state(s) 0
          LCD is idle in state(s) 0
          SBC is idle in state(s) 0
          Daemon* is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 1.47ms; fastest: 0.01ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
          HTTP sessions: 0 of 8

          • Ethernet -
            State: disabled
            Error counts: 0 0 0 0 0
            Socket states: 0 0 0 0 0 0 0 0
            === CAN ===
            Messages sent 0, longest wait 0ms for type 0
            === Linux interface ===
            State: 0, failed transfers: 1
            Last transfer: 14ms ago
            RX/TX seq numbers: 41738/41739
            SPI underruns 1, overruns 1
            Number of disconnects: 0
            Buffer RX/TX: 0/0-0
            === Duet Control Server ===
            Duet Control Server v3.2.2
            Code buffer space: 4096
            Configured SPI speed: 8000000 Hz
            Full transfers per second: 39.81
            Maximum length of RX/TX data transfers: 3088/724
          chrishammundefined 1 Reply Last reply Reply Quote 0
          • amostolundefined
            amostol @Phaedrux
            last edited by

            @phaedrux I fixed the low voltage issue, the power from the duet is not enough, but it did not fix the looping problem.

            1 Reply Last reply Reply Quote 0
            • chrishammundefined
              chrishamm administrators @amostol
              last edited by

              @amostol You do have a very old firmware installed on the MB6HC, please upgrade it once via bossa before you try anything else: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_All_other_Duet_boards

              Duet software engineer

              amostolundefined 1 Reply Last reply Reply Quote 0
              • amostolundefined
                amostol @chrishamm
                last edited by

                @chrishamm Ok thanks, I'll try that. Just one question, how can you tell? This can get very confusing, the is the OS for the pi, the DWC software, the printer/cnc files (like the config), and the firmware itself, it all seems a little overwhelming.

                Phaedruxundefined chrishammundefined 2 Replies Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator @amostol
                  last edited by

                  @amostol Well the pi runs a linux OS, so it gets updated pretty easily with sudo apt update and sudo apt upgrade. Once your duet firmware is up to date that command will also update all of the Duet stuff as well. So when it's working, it's actually pretty simple.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • chrishammundefined
                    chrishamm administrators @amostol
                    last edited by

                    @amostol It is part of the M122 response:

                    RepRapFirmware for Duet 3 MB6HC version 3.01-RC9 running on Duet 3 MB6HC v1.01 or later

                    The latest stable version is 3.2.2 (also installed on your Pi, see the end of that response).

                    Duet software engineer

                    amostolundefined 1 Reply Last reply Reply Quote 0
                    • amostolundefined
                      amostol @chrishamm
                      last edited by

                      @chrishamm I tried updating via Bossa, however, I can't get my pc or pi to recognize the duet. I have erased the firmware on the duet with the erase pins. I even followed the instruction on this page https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7 to the best of my ability, but nothing seems to work. Most of the instructions on the duet website absolutely suck, they are very short and leave many questions unanswered. Such as does the duet need a sd card in the sd card slot when doing the firmware upgrade?

                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @amostol
                        last edited by

                        @amostol said in Trouble with Duet 3 6HC Raspberry pi setup:

                        Such as does the duet need a sd card in the sd card slot when doing the firmware upgrade?

                        Not when doing it via USB and Bossa.

                        Does your USB cable handle data and power?

                        Does the PC make a chime when you connect the device?

                        Do the power LEDs on the board light up?

                        Did you remove the erase jumper from the pins?

                        Z-Bot CoreXY Build | Thingiverse Profile

                        amostolundefined 1 Reply Last reply Reply Quote 0
                        • amostolundefined
                          amostol @Phaedrux
                          last edited by

                          @phaedrux Yea my problem was the USb cable I was using, apparently it was power only, I tried a thicker one and it worked, from my pc at least. I also tried it from the pi, but it keeps saying it could not communicate with the duet, at least it recognized it this time. So I just used my pc and now everything works fine, no more of that looping.

                          Thank you very much, I really appreciate you taking the time to help me.

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA