Build Crash - Please Check this M122 Report!
-
Hi,
If anyone can give me some insight into why my machine just crashed I would greatly appreciate it. The M122 log follows. No apparent temperature issues.
M122
=== Diagnostics ===
RepRapFirmware for Duet version 1.24 running on Duet 0.6
Used output buffers: 3 of 16 (6 max)
=== System ===
Static ram: 44204
Dynamic ram: 42580 of which 3328 recycled
Stack ram used: 136 current, 3084 maximum
Never used ram: 5108
=== Platform ===
Last reset 00:03:10 ago, cause: software
Last software reset at 2019-08-28 16:28, reason: Hard fault, spinning module GCodes, available RAM 0 bytes (slot 2)
Software reset code 0x4033 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00f4e8dd SP 0x20085414
Stack: 000b52bd 000b5374 61000000 a5a5a5a5 a5a5a5a5 20084620 2007d3c0 00000001 c2600000 2007c784 000b55db 20073ddc 20073ddc 00000001 000b3c09 20073e4c 2007d3c0 00000001 c2600000 2007c784 000b3fc7 a5a5a5a5 200759f4 2007beba
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 50.5, current 50.7, max 53.9
Date/time: 1970-01-01 00:00:00
Slowest loop: 136.73ms; fastest: 0.10ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 1, FreeDm: 100, MinFreeDm: 99, MaxWait: 46639ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 1, completed moves: 1, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
Locked: 0, state: 4, listening: 20071bf4, 0, 0 -
I am regularly getting network issues at the moment and sometimes it is displaying the 'failed to get file list' network error.
I have the main V_IN PSU tied to mains earth. I have a seperate 5V PSU (duet v0.6 have noisy internal 5V regs).
I haven't connected my cables shields to ground yet (just testing a new machine) but will prioritise that.
Any chance this is an SD card on it's last legs?
-
@doctrucker said in Build Crash - Please Check this M122 Report!:
Last software reset at 2019-08-28 16:28, reason: Hard fault, spinning module GCodes, available RAM 0 bytes (slot 2)
i would say it ran out of memory.
-
Not an unusual build. There's a bug or fault if that is the cases.
One benchy sliced at 0.25 layer, 0.48 track width, 15% infill, 3 outer perimeters, 3 solid top and bottom layers.
-
If this is a memory issue perhaps it is todo with the frequent drops in network connection.
-
Carried out a repeat build and more complicated build since with no issue, but disconnected network lead during print. This seems to be related to situations where the network drops frequently.
