Warning: Lost connection to Duet
-
Setup in standalone mode, same issue as before... any other ideas?
2/20/2022, 3:17:34 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 (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6JKF0-3S86T-1VBLS
Used output buffers: 3 of 40 (13 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 94628 of which 0 recycled
Never used RAM 105060, free system stack 208 words
Tasks: NETWORK(ready,26.4%,259) ETHERNET(notifyWait,0.1%,168) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.8%,92) MAIN(running,65.2%,1115) IDLE(ready,0.4%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:25 ago, cause: software
Last software reset at 2022-02-20 15:17, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 104676, slot 1
Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x0044a804 BFAR 0x20429f94 SP 0x2041b648 Task MAIN Freestk 1756 ok
Stack: 20429f28 2042b068 2042b068 00000003 000002d8 0048423f 0045e5fe 810d0000 a5a5a5a5 0045e243 20429390 00000001 0002e78f 00413525 0c99a195 3f94cd3f 00000000 42e80000 42960000 42960000 00000000 20429f28 20429f28 00000000 00000003 0045e5e3 2042406c
Error status: 0x00
Step timer max interval 126
MCU temperature: min 34.7, current 35.2, max 35.3
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.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 88, reads 12775, writes 14 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 472, reads 12775, writes 14 timeouts 0
Driver 2: pos 0, standstill, SG min 0, mspos 948, reads 12775, writes 14 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 260, reads 12775, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 8, reads 12778, writes 11 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 12779, writes 11 timeouts 0
Date/time: 2022-02-20 15:17:34
Slowest loop: 4.37ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.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 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
=== CAN ===
Messages queued 232, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 130/0/0
Tx timeouts 0,0,129,0,0,101 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 3.99ms; fastest: 0.02ms
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: 5 2 2 2 2 0 0 0
- Ethernet -
-
Can you share a gcode file that you're printing when this happens?
-
-
Is there any grounding left to improve?
When and where did you purchase the Duet?
-
I've had this duet for quite awhile, its been running great up until now. Probably over a year ago? as far as grounding, I'm not sure what else to try. I probably got it from filastruder as I'm stateside.
Is the next step to start unplugging pieces and dry running gcode?
-
New thing I'm going to try is grounding all of the steppers, I found some posts where people had success after going through their machine to ensure they're all grounded. does anyone have any recommendations on where to ground with the stepper motors? I'm seeing a pretty high resistance between the aluminum gt pulley and the screws on the stepper motors (around 10K ohms).
I also tried running a gcode script with no extrusion, but this didn't help either. I was able to just run the extruder for a few minutes in place while just melting a pile of filament. This leads me to believe that it's something to do with the X and Y motors. After this, I wrote a script that just moved the printer back and forth between X200Y200 and X300Y300 at F3000. It ran for about a minute like usual. I'm going to try grounding the motors and running this again.
-
Update: grounding a bolt on the back of each X/Y stepper directly to ground of the 24v PSU didn't solve the issue, even with a really basic Gcode routine...
I also found that grounding through a fan pin wasn't a great connection to ground, so I ran a dedicated line to the ground pin on the power supply as well. This would have ensured that everything (extruder stepper and hotend) were properly grounded, no luck running a simple script:
g1 x300 y300 F5000
g1 x200 y200(25x this code to perform 50 lines of gcode)
I also tried unplugging the heater and thermistor, but that didn't help either.
-
@michaelr123 said in Warning: Lost connection to Duet:
I've had this duet for quite awhile, its been running great up until now. Probably over a year ago? as far as grounding, I'm not sure what else to try. I probably got it from filastruder as I'm stateside.
Did anything change around the time the problem started happening?
If you were within a year of purchase when it started happening we could try replacing under warranty.
-
It looks like I've had it for 14 months, but now that I think about it, I've had sporadic failures like this where mid-print the system just clicks and resets with no explanation throughout the time I've had it, it's just now gotten to the point where I can't run a job at all. Here are the things I changed recently:
-
I rebuilt the belt system. Before I had a screw and nut that wedged into the 80/20 and pressed the belt into the extrusion on one end, and a plastic anchor on the other side. I'm not proud of the old design, but it worked for a long time, I also wonder if it some how grounded the belt, though when I cut up a piece of belt I could find any continuity along the fiber glass. I designed a nylon plastic piece that has a loop for the belt and hole for an M5 screw and hammer nut and have been using that since.
-
while changing swapping out a nozzle, I broke off a leg of the heating cartridge, so I ordered a replacement from filastruder and installed that. That doesn't seem like a big deal to me, only other change is I added some quick disconnect spade connectors here so that I could disconnect the heating cartridge's next time I did a nozzle swap (helps deal with the wires wrapping around as you un screw the long barrel of the super volcano).
-
I went from 2x 24v part cooling fans in parallel to 1x, and removed the fan.
After that, I started printing some test squares that came out beautifully (due to the increased belt tension) but had the print fail to this error. From there the time to failure has just gotten faster and faster to the point where now I can't even run 25x jogs back and forth.
-
-
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
