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

Duet 3 SBC DCS has stopped

Scheduled Pinned Locked Moved Solved
Beta Firmware
8
80
3.7k
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
    dhusolo
    last edited by 8 Nov 2020, 20:37

    Sure. Should I use the getting started link or manually flash? I've tried compiling the firmware myself but with no success which is why I used the instructions in the link

    undefined 1 Reply Last reply 8 Nov 2020, 20:43 Reply Quote 0
    • undefined
      jay_s_uk @dhusolo
      last edited by jay_s_uk 11 Aug 2020, 20:43 8 Nov 2020, 20:43

      @dhusolo that should be all you need to follow to move over to the unstable branch.
      There's no need to use the erase button to load the firmware as it will be updated as part of the upgrade process

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 1
      • undefined
        dhusolo
        last edited by 8 Nov 2020, 20:53

        I thought i did it correct but I got this error

        pi@duet3:~ $ sudo apt-get install duetsoftwareframework
        Reading package lists... Done
        Building dependency tree
        Reading state information... Done
        The following additional packages will be installed:
        duetcontrolserver duetruntime duetsd duettools duetwebcontrol duetwebserver
        reprapfirmware
        The following packages will be upgraded:
        duetcontrolserver duetruntime duetsd duetsoftwareframework duettools
        duetwebcontrol duetwebserver reprapfirmware
        8 upgraded, 0 newly installed, 0 to remove and 118 not upgraded.
        Need to get 34.0 MB of archives.
        After this operation, 0 B of additional disk space will be used.
        Do you want to continue? [Y/n] y
        Get:1 https://pkg.duet3d.com unstable/armv7 armhf duetsoftwareframework armhf 3.2.0-beta3 [2,034 B]
        Get:2 https://pkg.duet3d.com unstable/armv7 armhf duetsd all 1.1.0 [2,102 B]
        Get:3 https://pkg.duet3d.com unstable/armv7 armhf duettools armhf 3.2.0-beta3 [62.2 kB]
        Get:4 https://pkg.duet3d.com unstable/armv7 armhf duetcontrolserver armhf 3.2.0-beta3 [226 kB]
        Get:5 https://pkg.duet3d.com unstable/armv7 armhf duetruntime armhf 3.2.0-beta3 [28.9 MB]
        Get:6 https://pkg.duet3d.com unstable/armv7 armhf duetwebserver armhf 3.2.0-beta3 [83.9 kB]
        Get:7 https://pkg.duet3d.com unstable/armv7 armhf duetwebcontrol all 3.2.0-beta3 [3,507 kB]
        Get:8 https://pkg.duet3d.com unstable/armv7 armhf reprapfirmware all 3.2.0-beta3-1 [1,260 kB]
        Fetched 34.0 MB in 19s (1,813 kB/s)
        Reading changelogs... Done
        (Reading database ... 79179 files and directories currently installed.)
        Preparing to unpack .../0-duetsoftwareframework_3.2.0-beta3_armhf.deb ...
        Unpacking duetsoftwareframework (3.2.0-beta3) over (3.1.1) ...
        Preparing to unpack .../1-duetsd_1.1.0_all.deb ...
        Unpacking duetsd (1.1.0) over (1.0.6) ...
        Preparing to unpack .../2-duettools_3.2.0-beta3_armhf.deb ...
        Unpacking duettools (3.2.0-beta3) over (3.1.1) ...
        Preparing to unpack .../3-duetcontrolserver_3.2.0-beta3_armhf.deb ...
        Unpacking duetcontrolserver (3.2.0-beta3) over (3.1.1) ...
        Preparing to unpack .../4-duetruntime_3.2.0-beta3_armhf.deb ...
        Unpacking duetruntime (3.2.0-beta3) over (3.1.1) ...
        Preparing to unpack .../5-duetwebserver_3.2.0-beta3_armhf.deb ...
        Unpacking duetwebserver (3.2.0-beta3) over (3.1.0) ...
        Preparing to unpack .../6-duetwebcontrol_3.2.0-beta3_all.deb ...
        Unpacking duetwebcontrol (3.2.0-beta3) over (3.1.1) ...
        Preparing to unpack .../7-reprapfirmware_3.2.0-beta3-1_all.deb ...
        Unpacking reprapfirmware (3.2.0-beta3-1) over (3.1.1-1) ...
        Setting up duetruntime (3.2.0-beta3) ...
        Setting up duetcontrolserver (3.2.0-beta3) ...
        Installing new version of config file /opt/dsf/conf/config.json ...
        Creating group dsf with gid 995.
        Creating user dsf (n/a) with uid 995 and gid 995.
        Setting up duettools (3.2.0-beta3) ...
        Setting up duetwebserver (3.2.0-beta3) ...
        Setting up duetsoftwareframework (3.2.0-beta3) ...
        To modify config files consider adding yourself to the dsf groupd: # usermod -a -G dsf <username>
        Setting up duetwebcontrol (3.2.0-beta3) ...
        Setting up duetsd (1.1.0) ...
        Setting up reprapfirmware (3.2.0-beta3-1) ...
        Sending update request to DCS... Error: Failed to send update request
        Unhandled exception. System.Threading.Tasks.TaskCanceledException: A task was canceled.
        at DuetAPIClient.BaseConnection.PerformCommand[T](BaseCommand command, CancellationToken cancellationToken) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetAPIClient/BaseConnection.cs:line 188
        at DuetControlServer.Program.CheckForAnotherInstance() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 305
        at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 84
        at DuetControlServer.Program.<Main>(String[] args)
        undefined 1 Reply Last reply 8 Nov 2020, 20:57 Reply Quote 0
        • undefined
          jay_s_uk @dhusolo
          last edited by jay_s_uk 11 Aug 2020, 20:57 8 Nov 2020, 20:57

          @dhusolo
          Are you still able to connect to the board via DWC?
          If you can confirm the firmware version using 3.1.1
          If it's still 3.1.1, send M997 B0
          I would be interested to see if you get any errors reported

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          undefined 1 Reply Last reply 8 Nov 2020, 21:02 Reply Quote 0
          • undefined
            dhusolo @jay_s_uk
            last edited by 8 Nov 2020, 21:02

            @jay_s_uk
            I had to start DCS and DWS manually but I was able to get to the web interface.

            M122 "DSF"
            === Duet Control Server ===
            Duet Control Server v3.2.0-beta3
            Code buffer space: 4096
            Configured SPI speed: 8000000 Hz
            Full transfers per second: 32.68
            11/8/2020, 2:58:59 PM```
            M122
            === Diagnostics ===
            RepRapFirmware for Duet 3 MB6HC version 3.2-beta3 running on Duet 3 MB6HC v1.01 or later (SBC mode)
            Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
            Used output buffers: 1 of 40 (10 max)
            === RTOS ===
            Static ram: 122124
            Dynamic ram: 137508 of which 0 recycled
            Never used RAM 132560, free system stack 185 words
            Tasks: Linux(ready,131) HEAT(blocked,362) CanReceiv(blocked,948) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,66) MAIN(running,1300) IDLE(ready,19)
            Owned mutexes: HTTP(MAIN)
            === Platform ===
            Last reset 00:09:17 ago, cause: software
            Last software reset details not available
            Error status: 0x00
            MCU temperature: min 25.3, current 26.2, max 26.4
            Supply voltage: min 0.3, current 0.3, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
            12V rail voltage: min 0.1, current 0.2, max 0.2, under voltage events: 0
            Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
            Date/time: 2020-11-08 14:58:59
            Slowest loop: 743.08ms; fastest: 0.16ms
            === Storage ===
            Free file entries: 10
            SD card 0 not detected, interface speed: 37.5MBytes/sec
            SD card longest read time 0.0ms, write time 0.0ms, max retries 0
            === 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, 0], CDDA state -1
            === AuxDDARing ===
            Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 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 doing "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 idle 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
            Aux2 is idle in state(s) 0
            Autopause is idle in state(s) 0
            Code queue is empty.
            === CAN ===
            Messages sent 0, send timeouts 0, longest wait 0ms for type 0, free CAN buffers 47
            === SBC interface ===
            State: 0, failed transfers: 1
            Last transfer: 14ms ago
            RX/TX seq numbers: 17902/17903
            SPI underruns 0, overruns 0
            Number of disconnects: 0, IAP RAM available 0x20aa0
            Buffer RX/TX: 0/0-0
            === Duet Control Server ===
            Duet Control Server v3.2.0-beta3
            Code buffer space: 4096
            Configured SPI speed: 8000000 Hz
            Full transfers per second: 32.56
            undefined 1 Reply Last reply 8 Nov 2020, 21:09 Reply Quote 0
            • undefined
              jay_s_uk @dhusolo
              last edited by 8 Nov 2020, 21:09

              @dhusolo well at least you're back on the latest firmware.
              @chrishamm any comments on the error above whilst updating?

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              1 Reply Last reply Reply Quote 0
              • undefined
                dhusolo
                last edited by 9 Nov 2020, 00:55

                More of a status update: I've started the same print again but I don't load any filament. I didn't want to waste the filament if it's going to cancel on me again.

                However I can now hear some strange jerky movements. I have a coreXY so it's hard to narrow down what stepper it's coming from especially since there's no filament going through it.

                undefined 1 Reply Last reply 9 Nov 2020, 19:39 Reply Quote 0
                • undefined
                  oliof
                  last edited by 9 Nov 2020, 13:50

                  I think my recent post about issues with 3.2b3 are very similar to this issue.

                  <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                  1 Reply Last reply Reply Quote 2
                  • undefined
                    Phaedrux Moderator @dhusolo
                    last edited by 9 Nov 2020, 19:39

                    @dhusolo Thanks for the update. In the meantime are you able to downgrade to 3.1.1 and use standalone mode to get back printing reliably?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    ? undefined 2 Replies Last reply 9 Nov 2020, 19:43 Reply Quote 0
                    • ?
                      A Former User @Phaedrux
                      last edited by 9 Nov 2020, 19:43

                      @Phaedrux said in Duet 3 SBC DCS has stopped:

                      @dhusolo Thanks for the update. In the meantime are you able to downgrade to 3.1.1 and use standalone mode to get back printing reliably?

                      Oh the irony.....

                      undefined 1 Reply Last reply 9 Nov 2020, 20:14 Reply Quote 0
                      • undefined
                        dhusolo @Phaedrux
                        last edited by 9 Nov 2020, 19:50

                        @Phaedrux I'm going to attempt to go back to RRF 3.1.1 with RPI since issues with connecting are resolved. Doesn't make a lot of sense that it was working previously for 3 months without any issue.

                        If that brings the same symptoms I'll run it in standalone until RRF 3.2 is stable. At least I know the board isn't bad

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Phaedrux Moderator @A Former User
                          last edited by 9 Nov 2020, 20:14

                          @CaLviNx It's not irony because no one ever disagreed with you.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          ? 1 Reply Last reply 10 Nov 2020, 02:24 Reply Quote 0
                          • undefined
                            dhusolo
                            last edited by 10 Nov 2020, 02:09

                            Can confirm going back to 3.1.1. the bug is still present. No idea why it appeared months after the original upload and weeks after any update to my config.

                            I did notice under Linux interface it shows a failed transfer, some bit loss and a SPI underrun

                            M122
                            === Diagnostics ===
                            RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
                            Board ID: 08DJM-956L2-G43S8-6J9D0-3S46T-9U2LF
                            Used output buffers: 1 of 40 (12 max)
                            === RTOS ===
                            Static ram: 154604
                            Dynamic ram: 163392 of which 140 recycled
                            Exception stack ram used: 584
                            Never used ram: 74496
                            Tasks: NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1384) CanClock(blocked,1436) TMC(blocked,60) MAIN(running,2672) IDLE(ready,76)
                            Owned mutexes:
                            === Platform ===
                            Last reset 03:06:26 ago, cause: power up
                            Last software reset at 2020-11-09 16:57, reason: User, spinning module LinuxInterface, available RAM 77008 bytes (slot 1)
                            Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
                            Error status: 0
                            MCU temperature: min 34.4, current 37.6, max 39.2
                            Supply voltage: min 24.2, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
                            12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
                            Driver 0: standstill, reads 55804, writes 22 timeouts 0, SG min/max 0/193
                            Driver 1: standstill, reads 55797, writes 30 timeouts 0, SG min/max 0/1023
                            Driver 2: standstill, reads 55797, writes 30 timeouts 0, SG min/max 0/1023
                            Driver 3: standstill, reads 55794, writes 34 timeouts 0, SG min/max 0/1023
                            Driver 4: standstill, reads 55794, writes 34 timeouts 0, SG min/max 0/1023
                            Driver 5: standstill, reads 55795, writes 34 timeouts 0, SG min/max 0/1023
                            Date/time: 2020-11-09 20:05:07
                            Slowest loop: 9.46ms; fastest: 0.14ms
                            === Storage ===
                            Free file entries: 10
                            SD card 0 not detected, interface speed: 37.5MBytes/sec
                            SD card longest read time 0.0ms, write time 0.0ms, max retries 0
                            === Move ===
                            Hiccups: 0(0), FreeDm: 375, MinFreeDm: 317, MaxWait: 669637ms
                            Bed compensation in use: mesh, comp offset -0.024
                            === MainDDARing ===
                            Scheduled moves: 169139, completed moves: 169139, 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 = 0 -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 idle 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
                            Aux2 is idle in state(s) 0
                            Autopause is idle in state(s) 0
                            Code queue is empty.
                            === Network ===
                            Slowest loop: 1.44ms; fastest: 0.01ms
                            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
                            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
                            === Filament sensors ===
                            Extruder 0 sensor: ok
                            === CAN ===
                            Messages sent 44905, longest wait 0ms for type 0
                            === Linux interface ===
                            State: 0, failed transfers: 1
                            Last transfer: 17ms ago
                            RX/TX seq numbers: 36691/32296
                            SPI underruns 1, overruns 0
                            Number of disconnects: 0
                            Buffer RX/TX: 0/0-0
                            === Duet Control Server ===
                            Duet Control Server v3.1.1
                            Daemon:
                            Finishing macro daemon.g, started by system
                            > Next stack level
                            Code buffer space: 4096
                            Configured SPI speed: 8000000 Hz
                            Full transfers per second: 32.48
                            1 Reply Last reply Reply Quote 0
                            • ?
                              A Former User @Phaedrux
                              last edited by 10 Nov 2020, 02:24

                              @Phaedrux said in Duet 3 SBC DCS has stopped:

                              @CaLviNx It's not irony because no one ever disagreed with you.

                              The irony is that time and effort has been needlessly expended in a vain attempt to fix an issue that the reason for (at this point of time) is evidently unknown when, instead of trying to fix it, the smart approach would have been to just go standalone in the first place which would have resulted in getting the machine printing again, and printing is the whole point of the exercise.

                              undefined undefined 2 Replies Last reply 10 Nov 2020, 02:27 Reply Quote 0
                              • undefined
                                Phaedrux Moderator @A Former User
                                last edited by 10 Nov 2020, 02:27

                                @CaLviNx It must be difficult going through life with such superior intellect. How do you manage to survive amongst us?

                                Z-Bot CoreXY Build | Thingiverse Profile

                                ? 1 Reply Last reply 16 Nov 2020, 14:21 Reply Quote 0
                                • undefined
                                  dhusolo @A Former User
                                  last edited by 10 Nov 2020, 02:31

                                  @CaLviNx seriously stop commenting. I do beta testing and bug fixing for a living. I took the steps I did for a reason. Everyone else has been trying to help while all you've been doing is throwing jabs in and out of this thread. I don't need you to tell me what the "smart approach" is because "the whole point of the exercise" is to figure out what happened and to see if I could fix it, not applying a band-aid.

                                  1 Reply Last reply Reply Quote 2
                                  • undefined
                                    chrishamm administrators
                                    last edited by 16 Nov 2020, 13:45

                                    To get back to the topic: I think the previously reported problems should be fixed in 3.2.0-b3.2. Feel free to test this again.

                                    Duet software engineer

                                    undefined 1 Reply Last reply 16 Nov 2020, 18:38 Reply Quote 0
                                    • ?
                                      A Former User @Phaedrux
                                      last edited by 16 Nov 2020, 14:21

                                      @Phaedrux said in Duet 3 SBC DCS has stopped:

                                      @CaLviNx It must be difficult going through life with such superior intellect. How do you manage to survive amongst us?

                                      Trust me dealing with such stupidity on a daily basis is tiresome.....

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        dhusolo @chrishamm
                                        last edited by 16 Nov 2020, 18:38

                                        @chrishamm That did fix the issue but after updating to 3.2.b3 I started to have jerky movements while printing that wasn't present before the update

                                        undefined 1 Reply Last reply 16 Nov 2020, 18:40 Reply Quote 0
                                        • undefined
                                          chrishamm administrators @dhusolo
                                          last edited by 16 Nov 2020, 18:40

                                          @dhusolo Please confirm that the installed RRF version is 3.2.0-beta3.2 and not 3.2.0-beta3.

                                          Duet software engineer

                                          undefined 1 Reply Last reply 16 Nov 2020, 22:16 Reply Quote 0
                                          58 out of 80
                                          • First post
                                            58/80
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA