3.5.0-B4, having random CAN error timeouts
-
@engikeneer from what i understand, although the firmware now know's that, its only a warning and nothing is done with it https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events
it may be worth implementing a macro to pause the print so at least you can possibly save it.
The only issue I could envisage is that the configuration won't get resent to the toolboard without restarting or sendingM98 P"config.g"so you may need to have another macro containing just the toolboard config info so you can get it reconfigured before restarting the print. -
@jay_s_uk Hi, yeah I do need to set up the events system to control how it handles things. However the default behaviour should at least report it in the console and that print did not seem to have anything reported.
However, I have just had repeated the same issue with using EI2 shaper, got the out-of-memory reset and it reported it in the console. It got slightly further through the print this time (so it's probably not a specific print issue). It also had potentially more of the random under-extrusions - this may or may not be a red herring and I intend to swap the hemera on that tool to see if it is mechanical.
I will try again with no shaper at all. Is there anything else I could try/provide to help narrow this down?
Data with EI2 shaper:
M122
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: QUS4M-U096U-D65J0-40KMD-3W03Z-ZK6H6 Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 102996 Dynamic ram: 123924 of which 12 recycled Never used RAM 11548, free system stack 124 words Tasks: NETWORK(2,nWait,29.4%,205) HEAT(3,nWait,0.1%,327) Move(4,nWait,4.8%,244) CanReceiv(6,nWait,0.2%,658) CanSender(5,nWait,0.1%,328) CanClock(7,delaying,0.0%,342) TMC(4,nWait,1.5%,74) MAIN(1,running,61.9%,698) IDLE(0,ready,0.4%,29) AIN(4,delaying,1.7%,266), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 03:11:17 ago, cause: software Last software reset at 2023-06-27 07:33, reason: User, Gcodes spinning, available RAM 10628, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 11478083, completed 11478082, timed out 0, errs 0 MCU temperature: min 32.5, current 34.6, max 40.2 Supply voltage: min 24.4, current 24.6, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/156/156, gc cycles 0 Events: 3 queued, 3 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 60, reads 10777, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 60, reads 10776, writes 16, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 31, reads 10788, writes 3, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 36, read errors 0, write errors 0, ifcnt 37, reads 10789, writes 3, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 0, ifcnt 41, reads 10788, writes 4, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-06-27 10:45:15 Cache data hit count 4294967295 Slowest loop: 1000.15ms; fastest: 0.10ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 9.6ms, write time 2.1ms, max retries 0 === Move === DMs created 83, segments created 30, maxWait 80617ms, bed compensation in use: mesh, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 165321, completed 165321, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 30, 0], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 245248, received 421404, lost 0, boc 1584 Longest wait 271ms for reply type 6029, peak Tx sync delay 48880, free buffers 18 (min 3), ts 57129/55779/0 Tx timeouts 528,0,609,0,0,266 last cancelled message type 52 dest 22 === Network === Slowest loop: 217.54ms; fastest: 0.06ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta4 MAC address f0:08:d1:02:ed:e4 Module reset reason: Power up, Vcc 3.35, flash size 2097152, free heap 33056 WiFi IP address 192.168.1.168 Signal strength -44dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 3 0 0 0 0 0 0 0M122 B22
M122 B22 Diagnostics for board 22: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4 (2023-06-08 16:22:30) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 1272, free system stack 88 words Tasks: Move(3,nWait,0.4%,111) HEAT(2,nWait,0.1%,101) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.1%,75) CanClock(5,nWait,0.0%,66) ACCEL(3,nWait,0.0%,53) TMC(2,nWait,3.0%,57) MAIN(1,running,91.4%,438) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,142), total 100.0% Last reset 00:37:41 ago, cause: software Last software reset at 2023-06-27 09:59, reason: OutOfMemory, available RAM 4, slot 1 Software reset code 0x01c0 ICSR 0x00000000 SP 0x200054a8 Task Move Freestk 137 ok Stack: 200057e0 000062df 200057f8 ae3a643e 36f08716 00009f99 200057f8 00007dd5 0001e926 3f62a79c 20005108 20007538 3d926a20 3d926a20 2dfcf290 200074c0 200074f4 00000000 470550b8 2ef478c0 2ef478c0 2000554c 20007538 20005108 00000000 00008c91 00000000 Driver 0: pos 0, 80.0 steps/mm, standstill, SG min 0, read errors 0, write errors 1, ifcnt 50, reads 15453, writes 11, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 867312 Moves scheduled 32394, completed 32394, in progress 0, hiccups 264, step errors 0, maxPrep 435, maxOverdue 2031906521, maxInc 2030421997, mcErrs 0, gcmErrs 0, ebfmin 0.00, ebfmax 1.00 Peak sync jitter -6/36, peak Rx sync delay 233, resyncs 11/1, no timer interrupt scheduled VIN voltage: min 24.4, current 24.5, max 24.5 MCU temperature: min 40.1C, current 40.3C, max 56.9C Last sensors broadcast 0x00000000 found 0 59 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 18111, send timeouts 2, received 60794, lost 0, free buffers 18, min 17, error reg ff0000 Last cancelled message type 4525 dest 0 dup 9, oos 284/99/0/242, bm 0, wbm 0, rxMotionDelay 367, adv -2031906298/222232 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
i3 clone with a bunch of mods -
@engikeneer I don't think so, its just waiting on @dc42 to look at the issue.
I've been printing mostly using RP2040 based toolboards recently and extrusion has been fine there so I don't think there are currently any more extrusion issues, I think its more down to lack of memory than anything else.
Maybe try a different shaper again sych asZVDorZVDD.
I think also providing the file you are printing as well as your config.g, any start files and daemon.g will help dc42 investigate the issue -
@engikeneer if it got further with EI2 that suggests that it is indeed the extra RAM used to implement input shaping that is causing it to run out of memory. You could try ZVD or MZV, both of which use less RAM than EI2.
I'll work on freeing up RAM for the next build of the tool board firmware.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks for the feedback. I can confirm that the same print managed to complete with all input shaping turned off. M122 and M122 B22 for that below
M122
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: QUS4M-U096U-D65J0-40KMD-3W03Z-ZK6H6 Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 102996 Dynamic ram: 123996 of which 216 recycled Never used RAM 11464, free system stack 122 words Tasks: NETWORK(2,nWait,188.1%,203) HEAT(3,nWait,0.4%,329) Move(4,nWait,32.5%,244) CanReceiv(6,nWait,1.2%,646) CanSender(5,nWait,0.5%,328) CanClock(7,delaying,0.1%,342) TMC(4,nWait,9.1%,74) MAIN(1,running,413.9%,704) IDLE(0,ready,3.7%,29) AIN(4,delaying,10.7%,266), total 660.2% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 03:27:55 ago, cause: software Last software reset at 2023-06-27 10:48, reason: User, Gcodes spinning, available RAM 11548, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 12476123, completed 12476122, timed out 0, errs 0 MCU temperature: min 34.4, current 34.6, max 40.2 Supply voltage: min 24.4, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/156/156, gc cycles 0 Events: 23 queued, 23 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 93, reads 274, writes 30, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 93, reads 273, writes 30, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 48, reads 288, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 56, reads 285, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 63, reads 285, writes 19, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-06-27 14:15:58 Cache data hit count 4294967295 Slowest loop: 1518.61ms; fastest: 0.09ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 10.3ms, write time 2.1ms, max retries 0 === Move === DMs created 83, segments created 22, maxWait 28487ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 213813, completed 213813, hiccups 0, stepErrors 0, LaErrors 0, Underruns [9, 218, 4], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 299313, received 476178, lost 0, boc 5514 Longest wait 518ms for reply type 6033, peak Tx sync delay 49047, free buffers 18 (min 3), ts 62379/56331/0 Tx timeouts 3407,0,3644,1,0,1956 last cancelled message type 4514 dest 127 === Network === Slowest loop: 217.85ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta4 MAC address f0:08:d1:02:ed:e4 Module reset reason: Power up, Vcc 3.35, flash size 2097152, free heap 39612 WiFi IP address 192.168.1.168 Signal strength -48dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0M122 B22
M122 B22 Diagnostics for board 22: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4 (2023-06-08 16:22:30) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 772, free system stack 88 words Tasks: Move(3,nWait,0.4%,111) HEAT(2,nWait,0.5%,57) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.1%,75) CanClock(5,nWait,0.0%,66) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,3.0%,57) MAIN(1,running,91.1%,344) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,142), total 100.0% Last reset 03:28:25 ago, cause: software Last software reset at 2023-06-27 09:59, reason: OutOfMemory, available RAM 4, slot 1 Software reset code 0x01c0 ICSR 0x00000000 SP 0x200054a8 Task Move Freestk 137 ok Stack: 200057e0 000062df 200057f8 ae3a643e 36f08716 00009f99 200057f8 00007dd5 0001e926 3f62a79c 20005108 20007538 3d926a20 3d926a20 2dfcf290 200074c0 200074f4 00000000 470550b8 2ef478c0 2ef478c0 2000554c 20007538 20005108 00000000 00008c91 00000000 Driver 0: pos 0, 405.0 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 66, reads 54732, writes 1, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 1412618 Moves scheduled 151605, completed 151605, in progress 0, hiccups 535, step errors 0, maxPrep 639, maxOverdue 1611293, maxInc 629772, mcErrs 0, gcmErrs 0, ebfmin -1.00, ebfmax 1.00 Peak sync jitter -15/43, peak Rx sync delay 285, resyncs 101/1, no timer interrupt scheduled VIN voltage: min 24.2, current 24.5, max 24.5 MCU temperature: min 36.4C, current 39.7C, max 57.5C Last sensors broadcast 0x00000002 found 1 202 ticks ago, 0 ordering errs, loop time 1 CAN messages queued 68358, send timeouts 151, received 94836, lost 0, free buffers 18, min 17, error reg ff0000 Last cancelled message type 4514 dest 127 dup 22, oos 557/212/0/757, bm 0, wbm 0, rxMotionDelay 444, adv -1611092/222205 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 0, other errors 0There were two new things that I did spot which I am not sure if they are related.... First is I got a bunch of timeout errors on my two toolboards for their temp sensors (see below from console). I managed to watch it and it did look like it lost CAN connection/sync from what I could see of the LED's. You can see a bunch of timeouts in the CAN part of M122.
The second thing is that at certain points in the print, the head motion seemed to get very jerky. The print is three objects - one printed fine and two have horrific under extrusion. The times I saw it, the jerky motion was on the poorly printed parts. I wonder if the CAN timeouts meant that the movement queue got interrupted so the toolhead had to stop? Might just have been luck that one part came out fine?
6/27/2023, 1:40:33 PM Error: Expansion board 21 stopped sending status Error: Expansion board 22 stopped sending status Debug from 22: temp timeout on sensor 1 Debug from 22: temp timeout on sensor 1 temp timeout on sensor 1 temp timeout o Debug from 22: n sensor 1 temp timeout on sensor 1 Debug from 21: temp timeout on sensor 2 Debug from 21: temp timeout on sensor 2 temp timeout on sensor 2 temp timeout o Debug from 21: n sensor 2 temp timeout on sensor 2 temp timeout on sensor 2Print file below. rename back to a .zip and extract to get the gcode - was slightly too big....
Low Poly Tall candle holder v2x3_TC.zip.txtI have no daemon.g and no start.g. I can provide the homing files etc but there's not much interesting in them - I haven't really needed to use much meta commands yet.
Edit: Here is an image of the print. Back object is okay, front two are not happy! They should all be the same
-
@engikeneer I've put a new build of the tool board firmware with more free RAM at https://www.dropbox.com/sh/c4aatfdsejjjab0/AACGuZ4qUBvZz49zxErkhmnWa?dl=0. Please try it to see if this out-of-memory issue is resolved.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks, that appears to have fixed it and the print completed fine and thge jerky motion I saw was gone. M122 and M122 B22 below if you're intersted.
The under extrusion remains but is much less severe. I got couple of
Expansion board 22 stopped sending status(and board 21) during the print. It seems fine printing from T1 (board 21), so I am guessing that this is due to a CAN wiring issue or some interference on T0 (board 22) as that is the first board in the chain. I will make up some new CAN cables in the next week or so, but either way I am convinced it is not a Beta FW issueM122
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.4 (2023-06-08 23:40:14) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: QUS4M-U096U-D65J0-40KMD-3W03Z-ZK6H6 Used output buffers: 3 of 40 (40 max) === RTOS === Static ram: 102996 Dynamic ram: 123924 of which 216 recycled Never used RAM 11152, free system stack 128 words Tasks: NETWORK(2,nWait,49.4%,205) HEAT(3,nWait,0.1%,327) Move(4,nWait,8.4%,244) CanReceiv(6,nWait,0.3%,672) CanSender(5,nWait,0.1%,328) CanClock(7,delaying,0.0%,342) TMC(4,delaying,2.4%,74) MAIN(1,running,35.5%,698) IDLE(0,ready,0.8%,29) AIN(4,delaying,2.9%,266), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 04:35:03 ago, cause: software Last software reset at 2023-07-01 09:00, reason: User, Gcodes spinning, available RAM 14832, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 16505513, completed 16505513, timed out 0, errs 0 MCU temperature: min 29.2, current 34.0, max 38.9 Supply voltage: min 24.4, current 24.6, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/312/312, gc cycles 0 Events: 2 queued, 2 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 57, reads 15760, writes 42, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 57, reads 15759, writes 42, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 15786, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 34, reads 15783, writes 18, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 36, reads 15780, writes 21, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-07-01 13:35:54 Cache data hit count 4294967295 Slowest loop: 999.94ms; fastest: 0.10ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 10.3ms, write time 8.0ms, max retries 0 === Move === DMs created 83, segments created 38, maxWait 218705ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === Scheduled moves 213781, completed 213781, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 3, 1], CDDA state -1 === DDARing 1 === 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, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 377421, received 659870, lost 0, boc 578 Longest wait 480ms for reply type 6029, peak Tx sync delay 47658, free buffers 18 (min 3), ts 82520/82158/0 Tx timeouts 63,0,89,0,0,53 last cancelled message type 30 dest 127 === Network === Slowest loop: 215.44ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta4 MAC address f0:08:d1:02:ed:e4 Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 39628 WiFi IP address 192.168.1.168 Signal strength -53dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0M122 B22
Diagnostics for board 22: Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.4+ (2023-06-30 15:40:06) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 2760, free system stack 88 words Tasks: Move(3,nWait,1.5%,71) HEAT(2,nWait,1.7%,37) CanAsync(5,nWait,0.0%,54) CanRecv(3,nWait,0.4%,75) CanClock(5,nWait,0.1%,66) ACCEL(3,nWait,0.0%,53) TMC(2,delaying,10.4%,57) MAIN(1,running,69.4%,322) IDLE(0,ready,0.0%,27) AIN(2,delaying,16.7%,114), total 100.0% Last reset 04:34:51 ago, cause: software Last software reset at 2023-06-27 09:59, reason: OutOfMemory, available RAM 4, slot 1 Software reset code 0x01c0 ICSR 0x00000000 SP 0x200054a8 Task Move Freestk 137 ok Stack: 200057e0 000062df 200057f8 ae3a643e 36f08716 00009f99 200057f8 00007dd5 0001e926 3f62a79c 20005108 20007538 3d926a20 3d926a20 2dfcf290 200074c0 200074f4 00000000 470550b8 2ef478c0 2ef478c0 2000554c 20007538 20005108 00000000 00008c91 00000000 Driver 0: pos 0, 405.0 steps/mm, standstill, SG min 0, read errors 1, write errors 0, ifcnt 39, reads 28857, writes 2, timeouts 3, DMA errors 0, CC errors 0, failedOp 0x6f, steps req 0 done 11981257 Moves scheduled 220948, completed 220948, in progress 0, hiccups 2525, segs 51, step errors 0, maxPrep 1497, maxOverdue 764587, maxInc 239236, mcErrs 0, gcmErrs 0, ebfmin -1.00 max 1.00 Peak sync jitter -10/29, peak Rx sync delay 393, resyncs 3/0, no timer interrupt scheduled VIN voltage: min 24.2, current 24.5, max 24.5 MCU temperature: min 32.4C, current 39.1C, max 51.3C Last sensors broadcast 0x00000002 found 1 8 ticks ago, 0 ordering errs, loop time 1 CAN messages queued 325377, send timeouts 6, received 436534, lost 0, free buffers 18, min 17, error reg ff0000 Last cancelled message type 4514 dest 127 dup 6, oos 712/200/0/149, bm 0, wbm 0, rxMotionDelay 584, adv -763616/100219 Accelerometer: LIS3DH, status: 00 Inductive sensor: not found I2C bus errors 0, naks 0, other errors 0 -
@engikeneer thanks for confirming that the changes I made were sufficient for your print and machine configuration.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
undefined engikeneer referenced this topic
-
@dc42 I just had another out of memory occur related to the tool board - I have this patch applied (actually a more recent one I believe), and it ran out again.
-
@Nuramori Please post the output for M122 B22 so we can check the build you have installed and the reset reason.
-
undefined Phaedrux marked this topic as a question
