Warning: Lost connection to Duet
-
Alright, new issue that recently cropped up, all of the sudden as I'm starting a print (testing tighter belts) I get about a layer in, and then the print stops, I get this error, the system resets, and the print is lost. It started with letting me run a few layers of a print with no infill, so it possibly could be a certain number of lines or runtime?
I'm not sure what's going on with this one, I've tried power cycling everything, double checking connections between the PI 3 and the duet 3, any ideas?
here's the print out from M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 61564 of which 0 recycled
Never used RAM 141724, free system stack 219 words
Tasks: SBC(ready,4.9%,328) HEAT(notifyWait,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.3%,93) MAIN(running,87.6%,1252) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:03:29 ago, cause: software
Last software reset at 2022-02-13 13:21, reason: HardFault imprec, Platform spinning, available RAM 141508, slot 0
Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00403803 BFAR 0x00000000 SP 0x2041b1d8 Task MAIN Freestk 1685 ok
Stack: 20433c60 00000000 00000000 00000000 00000000 004695f9 00469490 010f0000 00000000 ffffffff 00000000 00000001 20418194 00000000 00000000 0047a51f 0047a51e 610f0000 00000000 3fae1500 a941c360 3f7767e8 00000000 42e80000 42960000 42960000 00000000
Error status: 0x00
Step timer max interval 139
MCU temperature: min 33.5, current 33.7, max 34.2
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 54990, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 54990, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 54990, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 54990, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 54993, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 54993, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2022-02-13 13:24:56
Slowest loop: 0.45ms; fastest: 0.04ms
=== 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 ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 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.
=== CAN ===
Messages queued 1880, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 1047/0/0
Tx timeouts 0,0,1046,0,0,832 last cancelled message type 30 dest 127=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 15364/7391
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 35.24, max wait times: 488.2ms/0.0ms
Codes per second: 1.60
Maximum length of RX/TX data transfers: 3184/1196 -
@michaelr123 I am no expert by any means, but did you check all your power connections? Some times it is a dumb simple thing.. bad connection heats up, drops current, everything stops.. current flows, board starts up..
-
thanks for the suggestions. So far I've checked all the connections, tried it powered, unpowered, swapped to my brand new raspberry pi 4, no luck. I also tried starting the job from the raspberry pi as well as from my computer over wifi, same result.
It's like clockwork at exactly one layer in the console says:
2/13/2022, 5:07:23 PM Warning: Controller has been reset
2/13/2022, 5:07:23 PM Connection to Duet established
2/13/2022, 5:07:23 PM Warning: Lost connection to Duet (Board is not available (no header))I'm not sure what else to try at this point. I'll try running through all the connections on the duet board next, but it doesn't seem like its an SBC thing.
-
First thing I would try would be to run in standalone mode without the SBC at all and see if it will complete a print successfully.
To run in standalone mode you'll just need to prepare an SD card with the correct DWC files for the firmware version and your config files.
The SD card structure can be found here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#sd-card-structure
You can backup your config files through DWC. You'll need the config.g and homing files from the system tab.
The DWC files for the /www folder can be downloaded here: https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/DuetWebControl-SD.zip
Place the SD card in the Duet and it will boot up in standalone mode.
You'll need to connect it to your network since the SBC isn't doing that for it anymore.
https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet
-
Would a factory reset make sense? then I could just reboot from my config file?
without the SBC, the duet will need to be plugged into the network via ethernet, correct? I think I've got a spare ethernet cable. At some point I would like to get a wireless connection going to this duet again.
-
@michaelr123 are you printing a job with a lot of objects on the print bed; and are you using a slicer that labels the objects using M486? If so then there is a bug in RRF 3.3. that can cause this sort of behaviour. Workaround: turn off M486 object labelling in the slicer, or upgrade to 3.4RC1.
-
@michaelr123 I suggest you upgrade to version 3.4-rc1 using the unstable package feed and check if the problem persists.
-
@dc42 nope, just sliced one standard box in prusa slicer. Next I'm going to look through the Gcode and see if there's anything weird. Maybe I'll try running a job from Cura.
I ran a box with no infill or bottom first, and that made it a few layers up, so it could be a number of lines problem? It's performing Z hops properly, so it's not that.
-
@michaelr123 please can you try upgrading to RRF 3.4.0RC1 and see if the problem still occurs.
Also, please record a M122 response after any reset that you get. It helps us to see whether the resets are random (in which case they are generally caused by transients or ESD) or at the same location or a small set of locations.
-
Will do, I’ll give that a shot later today.
One other thought, I replaced my super volcano heater cartridge because I broke off one of the wires while changing a nozzle. I added spade connectors so that I could disconnect the heater block completely. That seems to be working well, so I doubt it’s that. I also removed one of 2x 24v cooling fans. I chopped the wires and wrapped the ends off with electrical tape for now because I was lazy. I doubt this is the issue as the cooling fan channel was working properly, but I’ll re-run that line to the one fan properly as well just to make sure.
I’ll run the m122 code again as well. Unfortunately the error codes haven’t been super descriptive to know if I’m shorting something.
-
disregard, I missed the bit that I need to update from the package server. Let me try that quick. (duet 3 + SBC - do not update through DWC)
-
Updated to the latest firmware, same issue:
2/14/2022, 7:44:58 PM Warning: SPI connection has been reset
2/14/2022, 7:44:58 PM Connection to Duet established
2/14/2022, 7:44:57 PM Warning: Lost connection to Duet (Board is not available (no header))
2/14/2022, 7:43:27 PM M32 "0:/gcodes/leg test 1.gcode"
File 0:/gcodes/leg test 1.gcode selected for printing
2/14/2022, 7:43:17 PM Connected to duet3.localM122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 64528 of which 0 recycled
Never used RAM 135160, free system stack 219 words
Tasks: SBC(resourceWait:,0.5%,515) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.4%,92) MAIN(running,90.1%,1245) IDLE(ready,1.9%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:08 ago, cause: software
Last software reset at 2022-02-14 19:55, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 134728, slot 1
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x00000970 SP 0x2041b500 Task MAIN Freestk 1674 ok
Stack: 00000004 20432350 0000002c 000008c4 00000002 00408c55 00408cb0 010f0000 00000000 00000001 00000000 00483ef7 2042bf34 00000000 00000000 0048423f 00000000 00484417 2042c2d8 20429f28 00000000 2041b594 a5a5a5a5 0045c427 ffffffff 00000000 2042c2d8
Error status: 0x00
Step timer max interval 151
MCU temperature: min 33.8, current 34.0, max 34.2
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min 0, mspos 552, reads 49784, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 344, reads 49784, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 420, reads 49784, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 764, reads 49784, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 49788, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 49788, writes 11 timeouts 0
Date/time: 2022-02-14 19:55:36
Slowest loop: 1.10ms; fastest: 0.05ms
=== 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 ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 queued 79, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 45/0/0
Tx timeouts 0,0,44,0,0,33 last cancelled message type 4514 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 40911/360
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bca8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 13
Full transfers per second: 39.44, max time between full transfers: 796.0ms, max pin wait times: 61.9ms/5.1ms
Codes per second: 0.62
Maximum length of RX/TX data transfers: 3500/1248 -
I also tried running a Gcode script that worked before (a few weeks ago) same problem.
I also re-tuned the hotend (super volcano like's to throw faults), properly wired the part cooling fan, and re-ran a bed leveling script.
Still seeing the same issue.
-
@michaelr123 I've analysed the crash report you posted after upgrading the 3.4.0rc1. It looks like a random crash of the sort typically caused by electrostatic discharge or a transient. But it's difficult to be sure from a single crash report; so next time it happens, please post the M122 report again. Meanwhile, here are a few questions for you:
- What power supplies are you using to power the Pi and the Duet? Depending on the grounding arrangements, it's possible that ground noise fed through the SBC interface could cause random crashes.
- Have you grounded the hot end metalwork? We've strong evidence that extruding plastic causes static charge to build up on the hot end if it is not grounded, and this can flash across to the temperature sensor connections.
-
@dc42
I'll run another couple back to back and post them later today. The board loses connection for a few seconds after it happens, but I'll get an M122 as soon after as possible.I was just running the Pi 3 I was using before over the ribbon cable without a second power source. I tried powering that separately and had the same issue. The PI 4 I've been using since has a usb C connection for it as I think it requires one per dozuki. It's all plugged into the same power strip if that makes a difference?
I'm not sure if it's random, it's fairly consistent that it fails a certain time after starting, or a certain number of lines of gcode (I tried running a spiral vase cylinder part to see if it was something to do with the layer change code, but it does the same thing after making it a few revolutions up). It seems like its triggered by something, though it could be a build up of static that's now occurring?
Weird idea, there used to be a screw running through the belts as an anchor, which would have connected the belts to "ground" (the aluminum frame). Now the belt is captured by a plastic printed loop, and the screw is completely separate. No idea if this is related, but the belts are the major thing that changed. The frame isn't technically connected to electrical ground, but it's an idea. The printer is fairly large, (1000x500mm) so the belts are fairly long and built from aluminum extrusion. - Just adding as more information.
I'll get the exact power supply model later, but its just a run of the mill 24v, 480w power supply from zyltech I believe.
The hotend (aluminum block?) is not formally grounded. I can take a look at this. If its building up charge like a capacitor after a certain time and then discharging that would create a regular timed failure mode.
This getting to be quite the trouble shooting puzzle!
-
@michaelr123 I suggest you start by grounding the hot end. If you don't already have a ground wire to the hot end and you want to avoid adding one, it's sufficient to connect the hot end metalwork through a 100K or 1M resistor to the ground side of the thermistor connection.
-
This may be a dumb question, but do you literally mean run a wire between ground on the duet 3 and create a screw terminal on the extruder?
I'm running a hemera extruder, would you recommend connecting the wire directly to the heater block? Or could it be on the cold side of the extruder? Though it may be anodized, which may cause problems.
As for the ground connection, I can just connect it to a ground channel for one of the fans correct?
-
@michaelr123 said in Warning: Lost connection to Duet:
do you literally mean run a wire between ground on the duet 3 and create a screw terminal on the extruder?
Yes. Using a multimeter to test for continuity can help determine what is electrically connected or not.
-
Thanks for verifying!
For all those wondering, the extruder stepper is grounded to the nozzle. On the hemera extruder there is an open threaded hole on the top which worked perfect for adding a short screw and wire to tie into the ground connection going to the 24v part cooling fan on the assembly.
I connected this, and re-ran the code I was using yesterday, but there's no change in the failure mode unfortunately... Any other ideas?
The power supply is a meanwell 24v 350 LRS model.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 64528 of which 0 recycled
Never used RAM 135160, free system stack 219 words
Tasks: SBC(ready,0.7%,510) HEAT(notifyWait,0.0%,355) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.3%,92) MAIN(running,87.5%,1245) IDLE(ready,4.6%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:03 ago, cause: software
Last software reset at 2022-02-15 19:24, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 134776, slot 1
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x2045b5b8 SP 0x20420d28 Task Move Freestk 381 ok
Stack: 00009818 00000001 00083985 2045b448 ffffffff 0043d8af 0043b052 61000000 00000001 20459ac8 00000000 00000000 00000000 0043b481 00000000 46974e4a 46974e4a 42fd88c0 2042e560 0000000a 00000001 00000000 2042e560 00000000 00000001 0043d8a7 a5a5a5a5
Error status: 0x00
Step timer max interval 152
MCU temperature: min 32.1, current 32.3, max 32.4
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min 0, mspos 600, reads 17947, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 504, reads 17947, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 380, reads 17947, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 340, reads 17947, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 17951, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 17951, writes 11 timeouts 0
Date/time: 2022-02-15 19:24:23
Slowest loop: 1.12ms; fastest: 0.04ms
=== 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 ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 queued 28, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 17/0/0
Tx timeouts 0,0,16,0,0,10 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 29579/138
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bca8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 13
Full transfers per second: 39.55, max time between full transfers: 231.0ms, max pin wait times: 55.4ms/1.6ms
Codes per second: 4.73
Maximum length of RX/TX data transfers: 3448/1196
2/15/2022, 7:24:20 PM Warning: SPI connection has been reset
2/15/2022, 7:24:20 PM Connection to Duet established
2/15/2022, 7:24:20 PM Warning: Lost connection to Duet (Board is not available (no header))
2/15/2022, 7:22:32 PM M32 "0:/gcodes/Shape-Cylinder.gcode"
File 0:/gcodes/Shape-Cylinder.gcode selected for printing
2/15/2022, 7:19:49 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 64528 of which 0 recycled
Never used RAM 135160, free system stack 219 words
Tasks: SBC(resourceWait:,0.5%,512) HEAT(notifyWait,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.5%,92) MAIN(running,91.2%,1245) IDLE(ready,0.8%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:20 ago, cause: software
Last software reset at 2022-02-15 18:57, reason: AssertionFailed, GCodes spinning, available RAM 134776, slot 0
Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041b55c Task MAIN Freestk 1697 ok
Stack: 000004eb 0048f590 00408d6f 2042ba78 20429f28 00000000 1422e454 a5a5a5a5 a5a5a5a5 a5a5a5a5 0045c553 00000000 2042ba7c 00000001 2041b59c 00000101 2042ff00 00000000 2043001c 00000000 0000018c 2042406c 00000000 00000000 ffffffed 00000000 00000000
Error status: 0x00
Step timer max interval 132
MCU temperature: min 30.3, current 30.9, max 31.0
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min 0, mspos 328, reads 49974, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 568, reads 49974, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 660, reads 49974, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 788, reads 49974, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 49977, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 49978, writes 11 timeouts 0
Date/time: 2022-02-15 19:19:48
Slowest loop: 1.10ms; fastest: 0.04ms
=== 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 ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 queued 184, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 104/0/0
Tx timeouts 0,0,103,0,0,79 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 18726/822
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bca8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 4
Full transfers per second: 10.67, max time between full transfers: 88.5ms, max pin wait times: 34.5ms/4.0ms
Codes per second: 0.25
Maximum length of RX/TX data transfers: 3448/1196 -
Another interesting development, I held the raspberry pi 4 in my hand and it ran about 10 times longer than it has in a few days. It still failed eventually, but here's the M122:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 64528 of which 0 recycled
Never used RAM 135160, free system stack 219 words
Tasks: SBC(ready,0.7%,510) HEAT(notifyWait,0.0%,355) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.3%,92) MAIN(running,87.5%,1245) IDLE(ready,4.6%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:03 ago, cause: software
Last software reset at 2022-02-15 19:24, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 134776, slot 1
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x2045b5b8 SP 0x20420d28 Task Move Freestk 381 ok
Stack: 00009818 00000001 00083985 2045b448 ffffffff 0043d8af 0043b052 61000000 00000001 20459ac8 00000000 00000000 00000000 0043b481 00000000 46974e4a 46974e4a 42fd88c0 2042e560 0000000a 00000001 00000000 2042e560 00000000 00000001 0043d8a7 a5a5a5a5
Error status: 0x00
Step timer max interval 152
MCU temperature: min 32.1, current 32.3, max 32.4
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min 0, mspos 600, reads 17947, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 504, reads 17947, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 380, reads 17947, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 340, reads 17947, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 17951, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 17951, writes 11 timeouts 0
Date/time: 2022-02-15 19:24:23
Slowest loop: 1.12ms; fastest: 0.04ms
=== 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 ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 queued 28, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 17/0/0
Tx timeouts 0,0,16,0,0,10 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 29579/138
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bca8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 13
Full transfers per second: 39.55, max time between full transfers: 231.0ms, max pin wait times: 55.4ms/1.6ms
Codes per second: 4.73
Maximum length of RX/TX data transfers: 3448/1196
2/15/2022, 7:24:20 PM Warning: SPI connection has been reset
2/15/2022, 7:24:20 PM Connection to Duet established
2/15/2022, 7:24:20 PM Warning: Lost connection to Duet (Board is not available (no header))
2/15/2022, 7:22:32 PM M32 "0:/gcodes/Shape-Cylinder.gcode"
File 0:/gcodes/Shape-Cylinder.gcode selected for printing
2/15/2022, 7:19:49 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 64528 of which 0 recycled
Never used RAM 135160, free system stack 219 words
Tasks: SBC(resourceWait:,0.5%,512) HEAT(notifyWait,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.5%,92) MAIN(running,91.2%,1245) IDLE(ready,0.8%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:20 ago, cause: software
Last software reset at 2022-02-15 18:57, reason: AssertionFailed, GCodes spinning, available RAM 134776, slot 0
Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x2041b55c Task MAIN Freestk 1697 ok
Stack: 000004eb 0048f590 00408d6f 2042ba78 20429f28 00000000 1422e454 a5a5a5a5 a5a5a5a5 a5a5a5a5 0045c553 00000000 2042ba7c 00000001 2041b59c 00000101 2042ff00 00000000 2043001c 00000000 0000018c 2042406c 00000000 00000000 ffffffed 00000000 00000000
Error status: 0x00
Step timer max interval 132
MCU temperature: min 30.3, current 30.9, max 31.0
Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 0, standstill, SG min 0, mspos 328, reads 49974, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 568, reads 49974, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 660, reads 49974, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 788, reads 49974, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 49977, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 49978, writes 11 timeouts 0
Date/time: 2022-02-15 19:19:48
Slowest loop: 1.10ms; fastest: 0.04ms
=== 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 ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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 queued 184, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 104/0/0
Tx timeouts 0,0,103,0,0,79 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 18726/822
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2bca8
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 4
Full transfers per second: 10.67, max time between full transfers: 88.5ms, max pin wait times: 34.5ms/4.0ms
Codes per second: 0.25
Maximum length of RX/TX data transfers: 3448/1196I then tried switching back to the raspberry pi 3 running just over the ribbon cable, no external power supply, same result.