3.1.0 firmware reboots periodically
-
@dc42 said in 3.1.0 firmware reboots periodically:
Thanks.
You actually have two M575 P1 lines in config.g, of which the second is commented out. You need a M575 P1 command to support PanelDue even if you are using the ribbon cable.
I missed the first one when I was checking to make sure I had one. That explains why it worked when I commented it out.
I'm in the middle of a print and so far so good.
-
Having same issue with my Duet 3. Will install the build linked and report back.
My M122 reports:
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.0 running on Duet 3 MB6HC v0.6 or 1.0 Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 154804 Dynamic ram: 163068 of which 44 recycled Exception stack ram used: 328 Never used ram: 74972 Tasks: NETWORK(ready,68) ETHERNET(blocked,436) HEAT(blocked,1200) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1452) TMC(blocked,204) MAIN(running,4520) IDLE(ready,76) Owned mutexes: === Platform === Last reset 00:00:22 ago, cause: software Last software reset at 2020-05-16 13:30, reason: Stack overflow, spinning module GCodes, available RAM 74648 bytes (slot 0) Software reset code 0x4103 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f80e BFAR 0x00000000 SP 0x2045ffb4 Task NETW Stack: 204120c0 204120f4 00463465 00000000 20412228 0000000a ffffffff 00020021 00462a89 2041211c 20417e30 Error status: 0 MCU temperature: min 45.4, current 45.6, max 45.8 Supply voltage: min 24.2, current 24.2, 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 44331, writes 15 timeouts 0, SG min/max 0/0 Driver 1: standstill, reads 44332, writes 15 timeouts 0, SG min/max 0/0 Driver 2: standstill, reads 44333, writes 15 timeouts 0, SG min/max 0/0 Driver 3: standstill, reads 44334, writes 14 timeouts 0, SG min/max 0/0 Driver 4: standstill, reads 44338, writes 11 timeouts 0, SG min/max 0/0 Driver 5: standstill, reads 44339, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2020-05-16 13:30:50 Slowest loop: 5.78ms; fastest: 0.15ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.1ms, 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: 4.94ms; 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: 2 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.87, errs: frame 7 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 88, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 22277ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 -
On first firmware upgrade to 3.1.0, it would reset every 30 sec to 1 minute. Now with the one from Dropbox, it has been stable for 10 minutes.
Here's my config.g
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 29 2020 20:50:30 GMT-0400 (EDT) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 3 Pro" ; set printer name M918 P1 E4 F2000000 ; configure direct-connect display ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 D3 ; physical drive 0.0 goes forwards M569 P0.1 S1 D3 ; physical drive 0.1 goes forwards M569 P0.2 S0 D3 ; physical drive 0.2 goes backwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E141.32 ; set steps per mm M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z250.00 E6000.00 ; set maximum speeds (mm/min) M201 X300.00 Y300.00 Z200.00 E5000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X245 Y225 Z230 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure to use z-probe ; Z-Probe M558 P1 C"io6.in+io6.out" H2.5 F100 T9000 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 X-22 Y4 Z1.30 ; set Z probe trigger value, offset and trigger height M557 X30:195 Y25:200 P5 ; define mesh grid ; Heaters M308 S0 P"temp1" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp1 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin temp0 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M143 H1 S270 ; set temperature limit for heater 1 to 270C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"out8" Q500 ; create fan 0 on pin out8 and set its frequency M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"!out4" Q25000 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"!out6" Q25000 ; create fan 2 on pin out6 and set its frequency M106 P2 S1 H1 T20 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F-1 ; define tool 0 G10 P0 X-5 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings M591 D0 P5 C"io3.in" R25:130 E3 S1 A0 ; Enable and set Filament monitor ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool M501 ; Load config overrides -
Thanks. When it has been running for a while, please run M122 and post the report here.
-
Just completed a 1hr 42min print with no issues. Here is the M122 after the print:
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.0+ running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MSJ-6JKDJ-3S46L-TVPMB Used output buffers: 3 of 24 (18 max) === RTOS === Static ram: 28260 Dynamic ram: 93992 of which 60 recycled Exception stack ram used: 544 Never used ram: 8216 Tasks: NETWORK(ready,92) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1640) IDLE(ready,80) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:49:28 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: 8 MCU temperature: min 31.1, current 33.5, max 37.0 Supply voltage: min 24.2, current 24.5, 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/257 Driver 6: standstill, SG min/max 0/272 Driver 7: standstill, SG min/max 0/281 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-05-16 14:10:39 Cache data hit count 4294967295 Slowest loop: 82.69ms; 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.7ms, write time 2.1ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 118, MaxWait: 290918ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 47669, completed moves: 47669, 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: 22.55ms; fastest: 0.00ms 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 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 20336 WiFi IP address 192.168.1.16 WiFi signal strength -30dBm, reconnections 0, sleep mode modem Socket states: 0 0 0 0 0 0 0 0 === DueX === Read count 1, 0.01 reads/minUpdate: It's been another 2+ hours and no restarts. It seems happy now.
-
Same here, works great. 2h up time more or less, no more reboots.
M122 results:
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.1.0+ running on Duet 3 MB6HC v0.6 or 1.0 Board ID: 08DJM-956L2-G43S4-6J9D0-3SD6Q-9U5GF Used output buffers: 3 of 40 (24 max) === RTOS === Static ram: 154884 Dynamic ram: 163068 of which 44 recycled Exception stack ram used: 328 Never used ram: 74892 Tasks: NETWORK(ready,84) ETHERNET(blocked,436) HEAT(blocked,1112) CanReceiv(suspended,3820) CanSender(suspended,1488) CanClock(blocked,1424) TMC(blocked,204) MAIN(running,4536) IDLE(ready,76) Owned mutexes: === Platform === Last reset 01:54:43 ago, cause: power up 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.1, current 45.4, max 45.6 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.2, max 12.2, under voltage events: 0 Driver 0: standstill, reads 26432, writes 0 timeouts 0, SG min/max not available Driver 1: standstill, reads 26431, writes 0 timeouts 0, SG min/max not available Driver 2: standstill, reads 26432, writes 0 timeouts 0, SG min/max not available Driver 3: standstill, reads 26433, writes 0 timeouts 0, SG min/max not available Driver 4: standstill, reads 26432, writes 0 timeouts 0, SG min/max not available Driver 5: standstill, reads 26434, writes 0 timeouts 0, SG min/max not available Date/time: 2020-05-16 19:24:41 Slowest loop: 6.87ms; fastest: 0.15ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.4ms, 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: 7.35ms; 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: 5 2 2 2 2 0 0 0 === Filament sensors === Extruder 0: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages sent 7589, longest wait 0ms for type 0 === Linux interface === State: 0, failed transfers: 0 Last transfer: 6883973ms ago RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 Number of disconnects: 0 Buffer RX/TX: 0/0-0 -
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?
