Duet 3 SBC DCS has stopped
-
Well you normally don't need to erase the firmware, but yes the jumper is the way to do that. Once erased you will need to use usb to flash a firmware again.
A different SD card won't help since the firmware is flashed to the board itself. The firmware bin file on the sd card is just there for storage during in place flashing.
What version is flashed to the duet right now?
What version is the Pi running?If you're completely back on 3.1.1 right now, are you on the unstable branch for apt-update? How did you originally try to update to the beta?
-
@Phaedrux I think I got it back to 3.1.1.
What's the command to verify version info including DWS and DWC?
-
From the gcode console send M122 and post the results please.
Additionally send M122 "DSF"
-
I haven't loaded my config file but I flashed Duet3Firmware_MB6HC.bin through Bossa. It looks like it's communicating with the RPI again.
M122
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 (10 max) === RTOS === Static ram: 154604 Dynamic ram: 161360 of which 20 recycled Exception stack ram used: 236 Never used ram: 76996 Tasks: NETWORK(ready,1980) HEAT(blocked,1452) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(suspended,252) MAIN(running,5184) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:09:59 ago, cause: power up Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 15.0, current 25.8, max 25.9 Supply voltage: min 0.2, 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.1, max 0.2, under voltage events: 0 Driver 0: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max 0/0 Date/time: 2020-11-08 14:26:06 Slowest loop: 2.36ms; fastest: 0.13ms === 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 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 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.03ms; 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 === CAN === Messages sent 0, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 12ms ago RX/TX seq numbers: 19460/19461 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 5.64M122 DSF
m122 DSF === 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: 161360 of which 20 recycled Exception stack ram used: 236 Never used ram: 76996 Tasks: NETWORK(ready,1980) HEAT(blocked,1452) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(suspended,252) MAIN(running,4512) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:12:41 ago, cause: power up Last software reset at 2020-11-05 20:48, reason: User, spinning module LinuxInterface, available RAM 74612 bytes (slot 3) Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 25.6, current 25.8, max 26.0 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: ok, reads 0, writes 0 timeouts 0, SG min/max not available Driver 1: ok, reads 0, writes 0 timeouts 0, SG min/max not available Driver 2: ok, reads 0, writes 0 timeouts 0, SG min/max not available Driver 3: ok, reads 0, writes 0 timeouts 0, SG min/max not available Driver 4: ok, reads 0, writes 0 timeouts 0, SG min/max not available Driver 5: ok, reads 0, writes 0 timeouts 0, SG min/max not available Date/time: 2020-11-08 14:28:49 Slowest loop: 1.97ms; fastest: 0.13ms === 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 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 D0 S0 F0" 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.03ms; 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 === CAN === Messages sent 0, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 12ms ago RX/TX seq numbers: 24793/24794 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.1.1 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 32.80 -
@dhusolo said in Duet 3 SBC DCS has stopped:
M122 DSF
I think the quotes around DSF are required. I'll admit I haven't used that command yet.
-
m122 "DSF" === 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.83 -
@dhusolo said in Duet 3 SBC DCS has stopped:
=== Duet Control Server === Duet Control Server v3.1.1
Regardless, I think you're on 3.1.1 across the board now.
-
but to your earlier question I tried updating to the beta following this and updating the source list to use unstable version
-
Would you be willing to test beta 3 once again?
-
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
-
@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 -
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) -
@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 -
@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 -
@dhusolo well at least you're back on the latest firmware.
@chrishamm any comments on the error above whilst updating? -
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.
-
I think my recent post about issues with 3.2b3 are very similar to this issue.
-
@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?
-
@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.....
-
@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
