Printing suddenly stopped (RRF3.01 beta3 / DWC 2.0.7)



  • I Had an unusual problem today, after printing for about an hour and a half, my printer just stopped, immediately the temperatures started falling so I knew either the hardware or firmware had hit a problem. I managed to log into the DWC and run the diagnostics (M122), listed below. I recently updated my Duet 2 Maestro firmware from 3.01-beta2 to 3.01 beta3 and the DWC to 2.0.7, since updating the firmware and DWC I have put maybe 10 hours or more of printing time in without any problems, maybe this is just a bizarre one off problem that has nothing to do with the software being updated but thought I’d mention it in case others have had the same problem with the 3.01 beta3 firmware and DWC 2.0.7 combination.

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 Maestro version 3.01-beta3 running on Duet Maestro 1.0
    Used output buffers: 3 of 24 (7 max)
    === RTOS ===
    Static ram: 21956
    Dynamic ram: 94636 of which 16 recycled
    Exception stack ram used: 220
    Never used ram: 14244
    Tasks: NETWORK(ready,784) HEAT(blocked,1364) MAIN(running,2016) IDLE(ready,80)
    Owned mutexes:
    === Platform ===
    Last reset 00:04:18 ago, cause: software
    Last software reset time unknown, reason: Hard fault, spinning module none, available RAM 13312 bytes (slot 2)
    Software reset code 0x4071 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x04427803 BFAR 0x4b4b4b4a SP 0x200020cc Task 0x5754454e
    Stack: 00406683 00406dfc 41000000 2000784c a5a5a501 a5a5a5a5 a5a5a5a5 a5a5a5a5 10000000 20007750 33c8e774
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 15.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 35.7, current 36.2, max 38.1
    Supply voltage: min 0.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
    Driver 0: standstill, read errors 0, write errors 1, ifcount 15, reads 10323, timeouts 0
    Driver 1: standstill, read errors 0, write errors 1, ifcount 15, reads 10323, timeouts 0
    Driver 2: standstill, read errors 0, write errors 1, ifcount 15, reads 10323, timeouts 0
    Driver 3: standstill, read errors 0, write errors 1, ifcount 15, reads 10323, timeouts 0
    Driver 4: standstill, read errors 0, write errors 1, ifcount 13, reads 10323, timeouts 0
    Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 10329
    Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 10329
    Date/time: 2020-02-02 12:18:47
    Slowest loop: 21.91ms; fastest: 0.08ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Move ===
    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1, chamberHeaters = -1 -1
    Heater 1 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
    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
    lcd is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 4.69ms; fastest: 0.02ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state 5, link 100Mbps full duplex



  • By the way, after a restart the printer is printing again



  • @Spanners Supply voltage min 0.0. Would indicate a complete loss of power perhaps?


  • administrators

    Thanks for your report. The hard fault address (0x00406dfc) unfortunately makes no sense, because it refers to an instruction that can't generate a hard fault. So I think this may be one of those unexplained glitches, caused by power instability, electrical noise, cosmic rays or the like. If it happens again, please post the M122 report again.



  • Thank you for taking the time to review the post, if anything else occurs I'll be sure to add some comments.



  • It was so two times. The reason is not known. Duet3 (pi) beta 3


Log in to reply