Duet 3 losing connection whilst printing
-
@camcamnz said in Duet 3 losing connection whilst printing:
RepRapFirmware for Duet 3 MB6HC version 3.2-RC2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Please try updating to 3.2 final release now that it's out. Did you try a fresh DuetPi installation and update?
@camcamnz said in Duet 3 losing connection whilst printing:
Powering the pi off the duet works fine in all scenarios, I have just noticed that I get the disconnection messages far more often when powered that way.
That's contradictory. If you're getting disconnected more often, it's not working fine in all scenarios, now is it?
-
@Phaedrux I just tried a fresh re-image and updating to the latest version, and still have the same issue.
@Phaedrux said in Duet 3 losing connection whilst printing:
That's contradictory. If you're getting disconnected more often, it's not working fine in all scenarios, now is it?
I meant in all other scenarios, other than when the bed heater is on
-
Can you try running the Duet 3 in standalone mode to take the Pi and DSF out of the equation so we can confirm that the board itself is working ok.
https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Running_in_standalone_mode
-
@Phaedrux
I have it running in standalone.
I am getting a lot of errors, but now they are HTTP timeouts.
Besides the errors however, all seems to be working properly so far, I got through PID autotune and some other commands successfully (ie heating the bed a few times).
I am going to figure out how to re-mount the duet to try to see if I can get something printed successfully
-
Are you using the same SD card from the Pi in the Duet, or a fresh SD card?
-
@Phaedrux Same SD Card, and same config files (just copied to the correct location and added the M552 command)
-
@Phaedrux A further update, I have successfully finished a small print, so seems to be working well in standalone mode (apart from the HTTP errors)
-
Can you post an M122 from standalone mode?
I assume you got fresh files from the 3.2 release to populate the SD card?Would you also be able to try running a ping command on the Duet IP address for a while and seeing if there are any dropped responses?
I'm surprised the network drops have followed to the standalone Duet.
-
@Phaedrux actually, the timeouts have stopped.
I did 2 test prints, the first took an hour, and I had 51 timeouts, the seconds took 90 minutes and I had none.
I have had it running now again for 30 minutes and also none (no drops on the ping either.When I re-imaged the sd card on the 9th, it seems that the image i downloaded already had the 3.2 release, and I didnt do any further changes to it apart from the config files.
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6J1FL-3SN6N-998YU
Used output buffers: 3 of 40 (23 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 93540 of which 64 recycled
Never used RAM 115440, free system stack 124 words
Tasks: NETWORK(ready,199) ETHERNET(blocked,85) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,344) CanClock(blocked,349) TMC(blocked,19) MAIN(running,1119) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:33:49 ago, cause: power up
Last software reset at 2021-01-09 12:49, reason: User, GCodes spinning, available RAM 147848, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 44.6, current 45.4, max 45.5
Supply voltage: min 23.9, current 24.0, max 24.0, 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 27120, standstill, reads 13736, writes 2 timeouts 0, SG min/max not available
Driver 1: position 26800, standstill, reads 13736, writes 2 timeouts 0, SG min/max not available
Driver 2: position 6040, standstill, reads 13736, writes 2 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 13737, writes 2 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 13738, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 13738, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-01-12 20:56:38
Slowest loop: 4.79ms; fastest: 0.06ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 822, completed moves 822, 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
Heater 1 is on, I-accum = 0.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.
=== Network ===
Slowest loop: 2.72ms; 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 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 3007, send timeouts 6765, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
- Ethernet -
-
@Phaedrux I am seeing the http drops again today.
Ping is not showing anything, I am continuously getting <1ms over the time, no delays or drops when the HTTP drops occur -
@camcamnz said in Duet 3 losing connection whilst printing:
Same SD Card,
Can you try with a fresh SD card?
-
@Phaedrux I tried with the SD card that came with the Pi (That i had been using previously), and I get exactly the same result
-
I have exactly the same problem and have tried everything with SD card, new image etc.
Does anyone else have any ideas what this could be?
-
I have come a little closer to solving the problem:
Keyboard, mouse, HDMI, USB touchscreen cable all unplugged from the Raspberry Pi 4.
Raspberry Pi 4 has its own power supply
Remote access to the Pi via AnyDesk
Don't click anything in the web GUI while printing-> Lost connection problem is gone
If you click around in the Web GUI (while printing) the problem comes back immediately
Seems to be a problem when the Pi is busy with something else while printing -
@Thoma308 said in Duet 3 losing connection whilst printing:
If you click around in the Web GUI (while printing) the problem comes back immediately
Seems to be a problem when the Pi is busy with something else while printingWhat speed class is your SD card?
-
@Phaedrux said in Duet 3 losing connection whilst printing:
n the Web GUI (while printing) the problem comes back immediately
Seems to be a problem when the Pi is busy with something else while printingA1 SanDisk Ultra UHS-I Speed UP TO 98 MB/s 653X 16GB
-
@Thoma308 said in Duet 3 losing connection whilst printing:
click around in the Web GUI (while printing) the problem comes back immediately
Seems to be a problem when the Pi is busy with something else while printingI have now done another test:
Raspberry PI without LAN and without WLAN (offline).
I got the Lost connection message 2 times in about 2 hours - but without aborting the print ...
still funny the whole thing -
@Thoma308 said in Duet 3 losing connection whilst printing:
I have now done another test:
Raspberry PI without LAN and without WLAN (offline).
I got the Lost connection message 2 times in about 2 hours - but without aborting the print ...
still funny the whole thingEven after some more tests and an update to the latest versions, the problem is still there and unsolved.
So I would be glad for more ideas
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J1FL-3SJ6J-186LG
Used output buffers: 1 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62488 of which 64 recycled
Never used RAM 146492, free system stack 128 words
Tasks: Linux(ready,71) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,19) MAIN(running,1217) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:17:13 ago, cause: software
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 23.8, current 29.9, max 31.1
Supply voltage: min 23.7, current 23.9, max 24.1, 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 111288, standstill, reads 17312, writes 59 timeouts 0, SG min/max 0/1023
Driver 1: position 69098, standstill, reads 17312, writes 59 timeouts 0, SG min/max 0/1023
Driver 2: position 102, standstill, reads 17312, writes 59 timeouts 0, SG min/max 0/1023
Driver 3: position 0, standstill, reads 17308, writes 63 timeouts 0, SG min/max 0/340
Driver 4: position 0, standstill, reads 17309, writes 63 timeouts 0, SG min/max 0/321
Driver 5: position 0, standstill, reads 17329, writes 43 timeouts 0, SG min/max 0/461
Date/time: 2021-01-24 10:59:34
Slowest loop: 181.18ms; fastest: 0.03ms
=== 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 476875ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 107, completed moves 107, hiccups 0, stepErrors 0, LaErrors 0, Underruns [16, 0, 42], 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 = -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 queued 18522, send timeouts 41688, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 149
Last transfer: 1ms ago
RX/TX seq numbers: 33443/55116
SPI underruns 192, overruns 31
Number of disconnects: 10, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.68
Maximum length of RX/TX data transfers: 2548/36
24.1.2021, 11:01:28: M122 "DSF": === Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.76
Maximum length of RX/TX data transfers: 2548/36
24.1.2021, 11:15:39: M122: === Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J1FL-3SJ6J-186LG
Used output buffers: 2 of 40 (10 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62488 of which 64 recycled
Never used RAM 146492, free system stack 128 words
Tasks: Linux(ready,71) HEAT(blocked,296) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,19) MAIN(running,1141) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:33:18 ago, cause: software
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 29.6, current 30.0, max 30.3
Supply voltage: min 23.8, 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.1, max 12.2, under voltage events: 0
Driver 0: position 111288, standstill, reads 27870, writes 0 timeouts 0, SG min/max not available
Driver 1: position 69098, standstill, reads 27870, writes 0 timeouts 0, SG min/max not available
Driver 2: position 16102, standstill, reads 27870, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 27866, writes 4 timeouts 0, SG min/max 0/280
Driver 4: position 0, standstill, reads 27866, writes 4 timeouts 0, SG min/max 0/274
Driver 5: position 0, standstill, reads 27870, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-01-24 11:15:38
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 1432576ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 109, completed moves 109, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 = -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 queued 3859, send timeouts 8682, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 149
Last transfer: 2ms ago
RX/TX seq numbers: 2360/24033
SPI underruns 192, overruns 31
Number of disconnects: 10, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.72
Maximum length of RX/TX data transfers: 4080/156 -
Can you check your rPi syslog file (/var/log/syslog) and look for warnings/errors from duet control server. if there are any do they match up with when you had the lost connections?
-
@gloomyandy said in Duet 3 losing connection whilst printing:
/varlog/syslog
Yes, I just started the heater, and instantly saw warnings in that log file, as below
Jan 24 13:17:49 duet3 DuetWebServer[564]: [DoCode] Executing code 'M140 P0 S60'
Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
Jan 24 13:17:49 duet3 DuetWebServer[564]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
Jan 24 13:17:49 duet3 DuetWebServer[564]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 121.9828ms
Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
Jan 24 13:17:49 duet3 DuetWebServer[564]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Jan 24 13:17:49 duet3 DuetWebServer[564]: Request finished in 124.107ms 200 text/plain; charset=utf-8
Jan 24 13:17:49 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x00000022)
Jan 24 13:17:49 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x00000011)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x000000b2)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0x02635649)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0xabbbd02c)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0x66f47fab)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because the number of maximum retries has been exceeded
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x00000074)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [info] Connection to Duet established
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xfee53e33, got 0x29af8a10)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x0000002c)
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 24 13:17:50 duet3 DuetControlServer[3086]: [info] Connection to Duet established
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0xffffffe1)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x0000007a)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0x147bc906, got 0x094245ad)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0x147bc906, got 0xb45e66d9)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x00000070)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0xffffff77)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0xffffff77)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xf639780f, got 0x6abe97ec)
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x000000de)
