Duet 3 SBC DCS has stopped
-
@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
-
@CaLviNx It's not irony because no one ever disagreed with you.
-
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 -
@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.
-
@CaLviNx It must be difficult going through life with such superior intellect. How do you manage to survive amongst us?
-
@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.
-
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
-
@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.....
-
@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
-
@dhusolo Please confirm that the installed RRF version is 3.2.0-beta3.2 and not 3.2.0-beta3.
-
@chrishamm can confirm it was 3.2.b3
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta3.2 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: 122236 Dynamic ram: 139164 of which 24 recycled Never used RAM 130768, free system stack 200 words Tasks: Linux(ready,97) HEAT(blocked,296) CanReceiv(blocked,948) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,54) MAIN(running,1189) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:20 ago, cause: software Last software reset at 2020-11-16 16:14, reason: User, GCodes spinning, available RAM 130768, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu Error status: 0x00 MCU temperature: min 38.3, current 38.7, max 38.8 Supply voltage: min 24.6, current 24.7, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Driver 0: position 0, standstill, reads 35729, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 35730, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 35731, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 35732, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 35733, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 35733, writes 14 timeouts 0, SG min/max 0/0 Date/time: 2020-11-16 16:14:56 Slowest loop: 1.42ms; fastest: 0.19ms === 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 = 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 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. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages sent 55, send timeouts 55, longest wait 0ms for type 0, free CAN buffers 47 === SBC interface === State: 0, failed transfers: 0 Last transfer: 20ms ago RX/TX seq numbers: 440/442 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x20a30 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: 30.36 -
@dhusolo What triggers are you using? Can you share the corresponding macro files?
Duet software engineer
-
@chrishamm Actually I'm not actively using the trigger anymore. That was originally configured for RRF2 as a shutdown button. trigger2.g might exist but it's not defined in config.g.
I've tried printing with 3.2.b3 to see if the jerky movements come back. So far it hasn't. It's a different model and it's slower speeds so i'm wondering if the print speeds had been related to why it was doing it. I'm going to try that other file again to see if I can replicate it. If I can at my normal print speeds I'll slow it down to see if it happens again.
-
@chrishamm I ran the print that had the jerky movement after updating and it seemed like it printed normally.
I made sure I followed the getting started link verbatim. Originally I didn't use Etcher or the Raspberry Pi Imager program to write the image. I used a program called USB Image Tool because i've been using it for years. This time I used the Raspberry Pi Imager. The only other thing I can think I did different was I don't remember changing the buffer size before
echo "options spidev bufsiz=8192" | sudo tee /etc/modprobe.d/spidev.conf
