3.1.0 firmware reboots periodically
-
When will the internal build be available for a pi update?
-
Happen me the same, After update from RC12, in the first print (around 16h) in the middle (around 60%) the firmware reset...
this is the M122:
m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0 running on Duet Ethernet 1.02 or later Board ID: 08DGM-917DA-G4MSD-6JTD8-3SS6M-K8S38 Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 28180 Dynamic ram: 93332 of which 20 recycled Exception stack ram used: 256 Never used ram: 9284 Tasks: NETWORK(ready,136) HEAT(blocked,1224) MAIN(running,1816) IDLE(ready,80) Owned mutexes: === Platform === Last reset 07:35:56 ago, cause: software Last software reset at 2020-05-17 00:23, reason: Stack overflow, spinning module none, available RAM 8896 bytes (slot 2) Software reset code 0x4111 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80e BFAR 0xe000ed38 SP 0x2001ffb4 Task NETW Stack: 20002860 20002894 00455625 00000000 20000000 200029b8 20002a55 a0000000 00454c35 200028c4 200055f4 Error status: 0 MCU temperature: min 23.2, current 23.7, max 38.9 Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 1970-01-01 00:00:00 Cache data hit count 4294967295 Slowest loop: 6.71ms; fastest: 0.12ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 2.0ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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 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, 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 5.53ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex === Filament sensors === Extruder 0 sensor: ok Extruder 1 sensor: okI go to install the new version of dropbox and i will comment...
Best Regards
-
Sorry again, inside the link of dropbox i see the file Duet2Conbinedfirmware.bin, and also show 3.1.0 folder, inside this folder also the file Duet2Conbinedfirmware.bin.
Which i must use?
-
the file directly in the main folder, not the one in the sub folder. Version should show 3.1.0+ when you do M122
-
@Thalios thank you, testing...
-
@luckyflyer said in 3.1.0 firmware reboots periodically:
When will the internal build be available for a pi update?
We'll do an 3.1.1 release within the next few days. Meanwhile you can install the new binary the old way, i.e. upload it through DWC.
-
Unfortunately I have been unable to reproduce the original problem, or identify what it is in config.g that causes the network task to use more stack than on my test machines.
Therefore, please can any of you who were experiencing this issue install the candidate RRF 3.1.1 binary from https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0, check that the issue remains resolved, and report the network task free stack from the M122 report after it has been running for a while. The network task free stack is this bit:
Tasks: NETWORK(ready,136)I suspect that a good way to reproduce the original fault quickly may be to set the printer doing something that causes motion (e.g. homing) and refresh the browser tab several times while it is doing that.
PS - please check the the build date you are using ends with 18b6.
-
Installing. Will report back.
-
Problem is back it seems.
M122 result:
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 1 of 40 (24 max) === RTOS === Static ram: 154524 Dynamic ram: 163148 of which 44 recycled Exception stack ram used: 560 Never used ram: 74940 Tasks: NETWORK(ready,148) ETHERNET(blocked,436) HEAT(blocked,1112) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1424) TMC(blocked,68) MAIN(running,4464) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:45:42 ago, cause: software Last software reset at 2020-05-16 15:58, reason: Stack overflow, spinning module Platform, available RAM 74648 bytes (slot 2) Software reset code 0x4100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0443780e BFAR 0x00000000 SP 0x2045ffb4 Task NETW Stack: 204120c0 204120f4 00463465 00000000 00000000 204121f0 00000000 a0000000 00462a89 204120fc 20417e30 Error status: 0 MCU temperature: min 47.0, current 47.3, max 47.5 Supply voltage: min 24.0, current 24.3, max 24.4, 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: ok, reads 48824, writes 0 timeouts 0, SG min/max 0/277 Driver 1: ok, reads 48825, writes 0 timeouts 0, SG min/max 0/1017 Driver 2: standstill, reads 48825, writes 0 timeouts 0, SG min/max 0/0 Driver 3: ok, reads 48826, writes 0 timeouts 0, SG min/max 0/969 Driver 4: standstill, reads 48825, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 48826, writes 0 timeouts 0, SG min/max not available Date/time: 2020-05-18 12:51:28 Slowest loop: 6.49ms; fastest: 0.15ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.3ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 370, MinFreeDm: 303, MaxWait: 0ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 31056, completed moves: 31009, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3 === 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 Heater 0 is on, I-accum = 0.6 Heater 1 is on, I-accum = 0.4 === GCodes === Segments left: 1 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.90ms; 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 === Filament sensors === Extruder 0: pos -7.73, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 315, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 2742318ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0I've been printing 2x 30 minutes jobs without hiccups, but it has reset on its own before i printed.
version is 18b6 in machine-specific tab in DWC
-
@Thalios, thank you very much for testing this.
I've put a further build (18b7) of RRF3 for Duet 3 at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. Please try that one, and if it works post the M122 report after it has run for a while, preferably after it has been printing with DWC 3.1.0 connected.
I still have no idea why your configuration uses so much more network stack than mine. The config.g file on my Duet 3 controlled tool changer is much more complex than yours.
-
Will do. Printing a 2h print at the moment though so it'll be right after.
-
One weird thing though, it did it right after the firmware upgrade, but hasn't since it seems.
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 1 of 40 (24 max) === RTOS === Static ram: 154524 Dynamic ram: 163148 of which 44 recycled Exception stack ram used: 568 Never used ram: 74932 Tasks: NETWORK(ready,148) ETHERNET(blocked,436) HEAT(blocked,1112) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1424) TMC(blocked,68) MAIN(running,4464) IDLE(ready,76) Owned mutexes: === Platform === Last reset 01:30:48 ago, cause: software Last software reset at 2020-05-16 15:58, reason: Stack overflow, spinning module Platform, available RAM 74648 bytes (slot 2) Software reset code 0x4100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0443780e BFAR 0x00000000 SP 0x2045ffb4 Task NETW Stack: 204120c0 204120f4 00463465 00000000 00000000 204121f0 00000000 a0000000 00462a89 204120fc 20417e30 Error status: 0 MCU temperature: min 45.6, current 47.4, max 47.4 Supply voltage: min 24.0, current 24.2, max 24.5, 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: ok, reads 28162, writes 8 timeouts 0, SG min/max 0/976 Driver 1: ok, reads 28161, writes 8 timeouts 0, SG min/max 0/332 Driver 2: ok, reads 28163, writes 8 timeouts 0, SG min/max 0/140 Driver 3: ok, reads 28166, writes 4 timeouts 0, SG min/max 0/1023 Driver 4: standstill, reads 28170, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 28170, writes 0 timeouts 0, SG min/max not available Date/time: 2020-05-18 13:36:34 Slowest loop: 113.03ms; fastest: 0.15ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.5ms, write time 40.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 351, MinFreeDm: 301, MaxWait: 846322ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 7273, completed moves: 7214, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3 === 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 Heater 0 is on, I-accum = 0.2 Heater 1 is on, I-accum = 0.4 === 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 doing "G1 X104.142 Y97.383 E0.00889" 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: 40.45ms; 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 === Filament sensors === Extruder 0: pos 4.70, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 5662, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 5448813ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 -
What's most noticeable to me in that report is that it gives the Network task stack remaining (when the M122 report was run, not when the reboot occurred) as 148 bytes. Whereas with that firmware version, the lowest I had was 212 bytes.
-
I'm running in standalone. Does that help?
-
@Thalios said in 3.1.0 firmware reboots periodically:
I'm running in standalone. Does that help?
Thanks, so am I.
-
The firmware build date on dropbox now -18b8 because we added a fix for an unrelated problem.
-
I just updated to b8.
After install, i ran m122 and it gave me this:
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 1 of 40 (12 max) === RTOS === Static ram: 154604 Dynamic ram: 163148 of which 44 recycled Exception stack ram used: 328 Never used ram: 75092 Tasks: NETWORK(ready,308) ETHERNET(blocked,436) HEAT(blocked,1188) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4528) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:00:39 ago, cause: software Last software reset at 2020-05-16 15:58, reason: Stack overflow, spinning module Platform, available RAM 74648 bytes (slot 2) Software reset code 0x4100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0443780e BFAR 0x00000000 SP 0x2045ffb4 Task NETW Stack: 204120c0 204120f4 00463465 00000000 00000000 204121f0 00000000 a0000000 00462a89 204120fc 20417e30 Error status: 0 MCU temperature: min 45.9, current 46.3, max 46.5 Supply voltage: min 24.2, current 24.3, max 24.3, 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: standstill, reads 62009, writes 15 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 62010, writes 15 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 62010, writes 15 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 62012, writes 14 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 62015, writes 11 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 62016, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-05-18 17:03:48 Slowest loop: 6.32ms; fastest: 0.21ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.3ms, 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 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 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: 13.76ms; 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 === Filament sensors === Extruder 0: pos 3.07, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 156, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 39247ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0It is now 308 instead of 148. It also states a stack overflow, but the timestamp coincides with the reboot of the update.
I'm about to start another 1-2h print, will report back after.
-
I did a 2 hour or so print with b6 this morning with no problems and it has been idle since then with DWC connected. I usually have DWC in a separate tab in my browser. I get a lot of connection interrupted (HTTP time out) connection established pairs. Usually when DWC is not the active tab. Here is my current M122 with b6. I'll install B8 and do another print.
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MSJ-6JKDJ-3S46L-TVPMB Used output buffers: 3 of 24 (23 max) === RTOS === Static ram: 27900 Dynamic ram: 94392 of which 60 recycled Exception stack ram used: 552 Never used ram: 8168 Tasks: NETWORK(ready,188) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1632) IDLE(ready,80) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 06:25:25 ago, cause: software Last software reset at 2020-05-16 12:21, reason: User, spinning module GCodes, available RAM 8496 bytes (slot 3) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 31.5, current 32.1, max 37.1 Supply voltage: min 24.2, current 24.6, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 0/1023 Driver 1: standstill, SG min/max 0/1023 Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max 0/1023 Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max 98/1023 Driver 6: standstill, SG min/max 0/265 Driver 7: standstill, SG min/max 0/251 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-05-18 17:16:44 Cache data hit count 4294967295 Slowest loop: 54.33ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.6ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 109, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 101765, completed moves: 101765, 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, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.4 === 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 200.66ms; fastest: 0.09ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 2 WiFi firmware version 1.23 WiFi MAC address ec:fa:bc:01:d6:19 WiFi Vcc 3.43, reset reason Unknown WiFi flash size 4194304, free heap 23568 WiFi IP address 192.168.1.16 WiFi signal strength -31dBm, reconnections 0, sleep mode modem Socket states: 4 0 0 0 0 0 0 0 === DueX === Read count 0, 0.00 reads/min -
Just completed a 2 hour + print with b8. No issues with restarts. Here is the M122.
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MSJ-6JKDJ-3S46L-TVPMB Used output buffers: 3 of 24 (20 max) === RTOS === Static ram: 27980 Dynamic ram: 94392 of which 60 recycled Exception stack ram used: 552 Never used ram: 8088 Tasks: NETWORK(ready,284) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1840) IDLE(ready,80) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 02:11:05 ago, cause: software Last software reset at 2020-05-16 12:21, reason: User, spinning module GCodes, available RAM 8496 bytes (slot 3) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 0 MCU temperature: min 31.1, current 34.5, max 37.1 Supply voltage: min 24.2, current 24.6, max 24.9, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max 0/1023 Driver 1: standstill, SG min/max 0/1023 Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max 0/1023 Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max 0/253 Driver 6: standstill, SG min/max 0/264 Driver 7: standstill, SG min/max 0/277 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-05-18 19:31:35 Cache data hit count 4294967295 Slowest loop: 55.48ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.5ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 109, MaxWait: 277266ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 101767, completed moves: 101767, 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, chamberHeaters = -1 -1 -1 -1 Heater 0 is on, I-accum = 0.0 Heater 1 is on, I-accum = 0.4 === 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 59.40ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.23 WiFi MAC address ec:fa:bc:01:d6:19 WiFi Vcc 3.43, reset reason Unknown WiFi flash size 4194304, free heap 23568 WiFi IP address 192.168.1.16 WiFi signal strength -33dBm, reconnections 0, sleep mode modem Socket states: 4 0 0 0 0 0 0 0 === DueX === Read count 1, 0.01 reads/minI switched back and forth between DWC 3.1.0 and DWC 1.22.6 and with 3.1.0 I get disconnects every few minutes. With 1.22.6 I do NOT get disconnects.
Here is a short log example of the connects/disconnects with 3.1.0:
5/18/2020, 7:37:09 PM Connection established 5/18/2020, 7:35:23 PM Connection interrupted, attempting to reconnect... Network error 5/18/2020, 7:34:53 PM Connection established 5/18/2020, 7:34:53 PM Connection interrupted, attempting to reconnect... HTTP request timed out 5/18/2020, 7:34:29 PM Connection established 5/18/2020, 7:34:29 PM Connection interrupted, attempting to reconnect... HTTP request timed out 5/18/2020, 7:34:18 PM Connection established 5/18/2020, 7:34:17 PM Connection interrupted, attempting to reconnect... HTTP request timed out 5/18/2020, 7:34:00 PM Connection established 5/18/2020, 7:34:00 PM Connection interrupted, attempting to reconnect... HTTP request timed out 5/18/2020, 7:32:52 PM Connection established 5/18/2020, 7:32:52 PM Connection interrupted, attempting to reconnect... HTTP request timed out 5/18/2020, 7:32:37 PM Connection established 5/18/2020, 7:32:36 PM Connection interrupted, attempting to reconnect... HTTP request timed out -
I get disconnects all the time as well. I thought it was my computer... But since b8, I haven't seen any.
Does it on my 3 computers (MacBook Pro, iMac, Mac Mini)
Just been up for 6h. Ran a 4.5h print flawless.
m122:
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 2 of 40 (24 max) === RTOS === Static ram: 154604 Dynamic ram: 163148 of which 44 recycled Exception stack ram used: 568 Never used ram: 74852 Tasks: NETWORK(ready,228) ETHERNET(blocked,424) HEAT(blocked,1088) CanReceiv(suspended,3820) CanSender(suspended,1420) CanClock(blocked,1424) TMC(blocked,60) MAIN(running,4528) IDLE(ready,76) Owned mutexes: === Platform === Last reset 06:22:59 ago, cause: software Last software reset at 2020-05-16 15:58, reason: Stack overflow, spinning module Platform, available RAM 74648 bytes (slot 2) Software reset code 0x4100 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0443780e BFAR 0x00000000 SP 0x2045ffb4 Task NETW Stack: 204120c0 204120f4 00463465 00000000 00000000 204121f0 00000000 a0000000 00462a89 204120fc 20417e30 Error status: 0 MCU temperature: min 45.5, current 45.6, max 48.4 Supply voltage: min 24.0, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Driver 0: standstill, reads 3557, writes 1 timeouts 0, SG min/max 0/1023 Driver 1: standstill, reads 3558, writes 1 timeouts 0, SG min/max 0/1023 Driver 2: standstill, reads 3556, writes 2 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 3557, writes 1 timeouts 0, SG min/max 0/1023 Driver 4: standstill, reads 3558, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 3558, writes 0 timeouts 0, SG min/max not available Date/time: 2020-05-18 23:26:09 Slowest loop: 118.73ms; fastest: 0.21ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.9ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 375, MinFreeDm: 305, MaxWait: 0ms Bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves: 597399, completed moves: 597399, 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 Heater 0 is on, I-accum = 0.5 Heater 1 is on, I-accum = 0.5 === 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: 17.74ms; 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 === Filament sensors === Extruder 0: pos 3.53, errs: frame 7 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 77659, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 22979991ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0
