Random reboot/reset. RepRap 3.4.5
-
Hi, random reboot the machine.
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9K662-MGPSN-6J9DL-3SN6K-1SY6W
Used output buffers: 1 of 26 (15 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 81896 of which 0 recycled
Never used RAM 3492, free system stack 184 words
Tasks: NETWORK(ready,12.1%,237) HEAT(notifyWait,0.1%,317) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,83.9%,438) IDLE(ready,4.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:19 ago, cause: software
Last software reset at 2023-07-27 16:09, reason: OutOfMemory, none spinning, available RAM 4, slot 2
Software reset code 0x41d2 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x20003e98 Task Move Freestk 348 ok
Stack: 20019fb4 0041009d 200038c8 00410273 00000008 00000054 20003eec 00428e8b 2001aa00 2001e7a8 200082f3 0042786f 2000cb18 0041aff1 391aa800 200082f4 0000000b 0000000b 20003eec fffffffc 0042a045 33053224 3d9e076c 00000000 4471220d 00000000 301c5fff
Error status: 0x00
Step timer max interval 0
MCU temperature: min 32.0, current 32.7, max 33.0
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/3, heap memory allocated/used/recyclable 2048/30/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2023-07-27 16:09:22
Cache data hit count 722776272
Slowest loop: 7.75ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.5ms, write time 3.6ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 2 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
Heater 0 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== DueX ===
Read count 1, 3.10 reads/min
=== Network ===
Slowest loop: 19.51ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.27
WiFi MAC address f4:cf:a2:69:47:9a
WiFi Vcc 3.34, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26120
WiFi IP address 192.168.1.205
WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0it happens in duplicate mode.
-
Can you share your config.g and the gcode file being printed?
Was this M122 captured immediately after the reset?
Does it happen at the same place in the file?
Does it happen with other files? -
@Klnvrsn2-0 It looks like your machine is running out of memory. Do you use a lot of variables/macros?
-
@Klnvrsn2-0 as @chrishamm says, you are running out of RAM in that configuration. It's trying to allocate additional memory needed to queue movement for X and U at the same time, and failing because there is none available.
If you post your config.g file then we may be able to make suggestions about how to use less. Meanwhile here are some general suggestions:
- If you use an attached 12864 display, keep each menu small and simple;
- Don't create a lot of tools;
- Don't use M595 to increase the movement queue length.
