Hi,
I couldn't figure out where the memory leak occurred. I tried to make a temporary fix - automatic reset when the buffer overflow.
Can you test this firmware ? (Based on version 2.04RC3)
https://github.com/mat100/RepRapFirmware/releases/tag/2.04RC3-fix-freeze
Matej
Hi,
below I am sending a diagnostic report from today's freezing
Recv: === Diagnostics ===
Recv: RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03trilab7 running on Duet Ethernet 1.02 or later
Recv: Board ID: 08DGM-917NK-F2MS4-7J1FD-3S86T-1ZTDD
Recv: Used output buffers: 24 of 24 (24 max)
Recv: === RTOS ===
Recv: Static ram: 25708
Recv: Dynamic ram: 93672 of which 312 recycled
Recv: Exception stack ram used: 532
Recv: Never used ram: 10848
Recv: Tasks: NETWORK(ready,472) HEAT(blocked,1236) MAIN(running,372) IDLE(ready,160)
Recv: Owned mutexes:
Recv: === Platform ===
Recv: Last reset 13:34:00 ago, cause: software
Recv: Last software reset at 2019-10-08 18:48, reason: User, spinning module GCodes, available RAM 11072 bytes (slot 3)
Recv: Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Recv: Error status: 4
Recv: Free file entries: 9
Recv: SD card 0 detected, interface speed: 20.0MBytes/sec
Recv: SD card longest block write time: 0.0ms, max retries 0
Recv: MCU temperature: min 44.0, current 44.4, max 44.6
Recv: Supply voltage: min 23.0, current 23.5, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Recv: Driver 0: ok, SG min/max 0/171
Recv: Driver 1: ok, SG min/max 26/153
Recv: Driver 2: ok, SG min/max 0/168
Recv: Driver 3: ok, SG min/max 0/1023
Recv: Driver 4: standstill, SG min/max not available
Recv: Date/time: 2019-10-09 08:23:40
Recv: Cache data hit count 4294967295
Recv: Slowest loop: 1.96ms; fastest: 0.07ms
Recv: I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
Recv: === Move ===
Recv: Hiccups: 0, FreeDm: 141, MinFreeDm: 89, MaxWait: 0ms
Recv: Bed compensation in use: mesh, comp offset 0.000
Recv: === DDARing ===
Recv: Scheduled moves: 1699629, completed moves: 1699589, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
Recv: === Heat ===
Recv: Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Recv: Heater 0 is on, I-accum = 0.2
Recv: Heater 1 is on, I-accum = 0.7
Recv: === GCodes ===
Recv: Segments left: 1
Recv: Stack records: 2 allocated, 0 in use
Recv: Movement lock held by null
Recv: http is idle in state(s) 0
Recv: telnet is idle in state(s) 0
Recv: file is doing "G1 X-16.905 Y-13.359 E0.01805 F1249.6" in state(s) 0
Recv: serial is idle in state(s) 0
Recv: aux is idle in state(s) 0
Recv: daemon is idle in state(s) 0
Recv: queue is idle in state(s) 0
Recv: autopause is idle in state(s) 0
Recv: Code queue is not empty:
Recv: Queued 'M106 S153' for move 1699600
Recv: Queued 'M106 S184' for move 1699601
Recv: 2 of 16 codes have been queued.
Recv: === Network ===
Recv: Slowest loop: 1.05ms; fastest: 0.02ms
Recv: Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
Recv: HTTP sessions: 0 of 8
Recv: Interface state 5, link 100Mbps full duplex
Hi,
We have same problem with freezing duets in longer prints. Is this problem already solved ?
Thank, Supik (TriLAB)