3.4b1 SBC mode M702 crashes DCS
-
Hi!
With 3.4b1 installed on my MB6HC + raspi changing fillament appears to be imposible. Indeed M702 causes DCS to crash and has to be manually restarted.
m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta1 (2021-07-10 16:20:28) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S8-6J9D8-3S86J-9B36F Used output buffers: 1 of 40 (10 max) === RTOS === Static ram: 150904 Dynamic ram: 64380 of which 36 recycled Never used RAM 138872, free system stack 219 words Tasks: ACCEL(notifyWait,0.0%,348) SBC(resourceWait:,0.3%,308) HEAT(delaying,0.1%,325) Move(notifyWait,0.0%,300) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,6.6%,93) MAIN(running,92.7%,967) IDLE(ready,0.3%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:03:02 ago, cause: software Last software reset at 2021-07-13 16:56, reason: User, GCodes spinning, available RAM 135800, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 Step timer max interval 740 MCU temperature: min 45.6, current 45.8, max 46.9 Supply voltage: min 0.2, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.1, current 12.2, max 12.8, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 36701, writes 11 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 36702, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 36702, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-07-13 16:59:57 Slowest loop: 26.60ms; fastest: 0.04ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 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 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" 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. === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 1625, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 913/0/0 Tx timeouts 0,0,912,0,0,711 last cancelled message type 4514 dest 127 === SBC interface === State: 4, failed transfers: 0, checksum errors: 0 Last transfer: 2ms ago RX/TX seq numbers: 793/793 SPI underruns 0, overruns 0 Disconnects: 1, timeouts: 1, IAP RAM available 0x2c7a4 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.4-b1 Code buffer space: 4096 Configured SPI speed: 8000000Hz Full transfers per second: 37.82, max wait times: 56.8ms/0.0ms Codes per second: 0.05 Maximum length of RX/TX data transfers: 3096/40Systemd log
-
@serbitar Thanks for the report, I am looking into it.
-
This will be fixed in the next version.
