Duet 3 SBC DCS has stopped

A Former User · 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.

Phaedrux · 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?

dhusolo · 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.

chrishamm · 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.

A Former User · 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.....

dhusolo · 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

chrishamm · 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.

dhusolo · 16 Nov 2020, 22:16

@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

chrishamm · 16 Nov 2020, 22:33

@dhusolo What triggers are you using? Can you share the corresponding macro files?

dhusolo · 16 Nov 2020, 23:41

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

dhusolo · 17 Nov 2020, 17:03

@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

dhusolo · 23 Nov 2020, 16:18

Well it happened again while running 3.2.b3. It has been printing pretty good the last week. Over night the print cancelled but it just stopped printing. The heaters are still at temp and the head was in the same position on the print, it didn't run pause.g.

When I started DWC on my PC the print status was still printing. I pressed pause and that's when it ran pause.g. I tried to resume the print and it said cannot print no file selected

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 (12 max)
=== RTOS ===
Static ram: 122236
Dynamic ram: 139788 of which 64 recycled
Never used RAM 130104, free system stack 118 words
Tasks: Linux(ready,67) HEAT(blocked,295) CanReceiv(blocked,948) CanSender(blocked,343) CanClock(blocked,352) TMC(blocked,18) MAIN(running,669) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 14:24:35 ago, cause: software
Last software reset at 2020-11-22 19:53, reason: User, GCodes spinning, available RAM 130104, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu
Error status: 0x00
MCU temperature: min 35.4, current 37.2, max 38.3
Supply voltage: min 24.2, current 24.6, max 24.8, 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: position 200, standstill, reads 25360, writes 21 timeouts 0, SG min/max 0/202
Driver 1: position -200, standstill, reads 25349, writes 33 timeouts 0, SG min/max 0/1023
Driver 2: position 5843, standstill, reads 25350, writes 33 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 25350, writes 33 timeouts 0, SG min/max 0/1023
Driver 4: position 0, standstill, reads 25351, writes 33 timeouts 0, SG min/max 0/1023
Driver 5: position 0, standstill, reads 25352, writes 33 timeouts 0, SG min/max 0/1023
Date/time: 2020-11-23 10:17:46
Slowest loop: 278.17ms; fastest: 0.09ms
=== 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: 354, MaxWait: 10418300ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 480277, completed moves 480277, StepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 207659, send timeouts 207659, longest wait 0ms for type 0, free CAN buffers 47
=== SBC interface ===
State: 0, failed transfers: 1
Last transfer: 19ms ago
RX/TX seq numbers: 27088/26081
SPI underruns 3, 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: 32.32

chrishamm · 26 Nov 2020, 19:26

@dhusolo Please upgrade to 3.2-b4, it should be fixed in the latest builds.

medicusdkfz · 6 Dec 2020, 10:44

Same here with 3.2beta4 on a Duet3 6HC/3HC: Freezing during the print without a pause command... Only solution is to close any web connection in the browser (on a Macbook Pro tested with Safari/Edge/Chrome - it doesn't matter). Also problems with more than one browser connection to the board...

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta4 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1DJ-3SN6M-9S0YG
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 123212
Dynamic ram: 168800 of which 488 recycled
Never used RAM 99692, free system stack 180 words
Tasks: NETWORK(ready,189) ETHERNET(blocked,110) HEAT(blocked,297) CanReceiv(blocked,898) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1127) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:13:05 ago, cause: software
Last software reset at 2020-12-06 11:17, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 99652, slot 2
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x0444a804 BFAR 0x00000016 SP 0x2040b928 Task ETHE
Stack: 20423888 00000000 ffffffff 00000002 204098a4 0040fdf9 004109a2 61000000 204098ec 20423830 2042384c 0040fdf9 2041df64 2041b3cc 2041de94 0040c7a9 20411574 00000000 00000001 2041b3cc 204098a4 00000002 00000002 2041b3cc 20409872 a4b2a8c0 2040ba34
Error status: 0x00
MCU temperature: min 36.5, current 36.7, max 39.5
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
Driver 0: position 0, standstill, reads 12266, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 12266, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 12267, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 12268, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 12269, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 12270, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-12-06 11:30:20
Slowest loop: 5.04ms; fastest: 0.15ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.6ms, 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 idle 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: 6.42ms; fastest: 0.03ms
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: 1 of 8

Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0
=== CAN ===
Messages queued 3151, send timeouts 0, received 3152, lost 0, longest wait 10ms for reply type 6027, free buffers 47

chrishamm · 6 Dec 2020, 11:09

@medicusdkfz You are running in standalone mode and now version 3.2.0-b4.1 is available. Please upgrade to that version first and open a new thread with a fresh dump of M122 if the problem persists.

medicusdkfz · 6 Dec 2020, 11:53

Great news! I will support you with a M122 in case of a reboot during the printout...

Thank you,
Pierre

dc42 · 6 Dec 2020, 16:21

@medicusdkfz, your M122 report indicates that LWIP (the TCP/IP stack) is making a TCP/IP callback with a null argument. I have just made some code changes to handle that possibility. These will be included in the next 3.2 beta or RC release.

Does anything in particular trigger the problem, for example Telnet or FTP access?

medicusdkfz · 6 Dec 2020, 16:29

@dc42 said in Duet 3 SBC DCS has stopped:

@medicusdkfz, your M122 report indicates that LWIP (the TCP/IP stack) is making a TCP/IP callback with a null argument. I have just made some code changes to handle that possibility. These will be included in the next 3.2 beta or RC release.
Does anything in particular trigger the problem, for example Telnet or FTP access?

Hi,

I don't use Telnet or FTP...

But I realized another lost of my web connection to my 6HC. Then it's impossible to connect till a manually reboot of the 6HC.

Sorry for that,
Pierre

dc42 · 7 Dec 2020, 07:54

From your M122 report I think you may have enabled either Telnet or FTP in config.g.