UNSOLVED 3.2 heating failed, print starts anyway - bug?



  • I tried to do the hotend manual calibration on a toolboard following this guide. Updated the values and rebooted.

    Then sent a print, the heating failed (the web console shows the hotend as "failed") but the print started anyway at 100°C.

    PS: I reset the calibration and the head works again albeit not calibrated.


  • Moderator

    Hi, can you confirm that the main board and tool board are both running FW 3.2? M122 and M122 B1

    Was there an error message in the console?

    The print started at 100c, but what was the intended temp?

    Can you share the first 50 lines or so of the gcode file?

    What tuning values were you using? Can you share your config.g?



  • Thanks for your reply

    Versions as follow

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC version 3.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
    Board ID: 08DJM-956BA-NA3TJ-6J1FJ-3S86Q-1T96T
    Used output buffers: 1 of 40 (12 max)
    === RTOS ===
    Static ram: 149788
    Dynamic ram: 62432 of which 76 recycled
    Never used RAM 146536, free system stack 129 words
    Tasks: Linux(ready,101) HEAT(blocked,277) CanReceiv(blocked,813) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,19) MAIN(running,1189) IDLE(ready,19)
    Owned mutexes: HTTP(MAIN)
    === Platform ===
    Last reset 01:13:57 ago, cause: software
    Last software reset at 2021-01-13 17:53, reason: User, GCodes spinning, available RAM 146668, slot 2
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Aux1 errors 0,0,0
    MCU temperature: min 44.3, current 44.8, max 46.5
    Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: position 4800, standstill, reads 30634, writes 81 timeouts 0, SG min/max 0/243
    Driver 1: position 0, standstill, reads 30635, writes 81 timeouts 0, SG min/max 0/254
    Driver 2: position 35200, standstill, reads 30678, writes 38 timeouts 0, SG min/max 0/164
    Driver 3: position 0, standstill, reads 30678, writes 38 timeouts 0, SG min/max 0/143
    Driver 4: position 0, standstill, reads 30678, writes 38 timeouts 0, SG min/max 0/193
    Driver 5: position 0, standstill, reads 30705, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2021-01-13 19:07:18
    Slowest loop: 174.41ms; fastest: 0.03ms
    === 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 118603ms, bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves 579, completed moves 579, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 23], 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
    Heater 0 is on, I-accum = 0.2
    Heater 1 is on, I-accum = 0.0
    === 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.
    === CAN ===
    Messages queued 18280, send timeouts 0, received 53421, lost 0, longest wait 2ms for reply type 6049, free buffers 48
    === SBC interface ===
    State: 1, failed transfers: 0
    Last transfer: 1ms ago
    RX/TX seq numbers: 26382/26382
    SPI underruns 0, overruns 0
    Number of disconnects: 0, IAP RAM available 0x2c8a8
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.2.0
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 35.51
    Maximum length of RX/TX data transfers: 3160/1236
    

    Toolboard

    M122 B20
    Diagnostics for board 20:
    Duet TOOL1LC firmware version 3.2 (2021-01-05)
    Bootloader ID: not available
    Never used RAM 3984, free system stack 50 words
    HEAT 90 CanAsync 85 CanRecv 83 TMC 54 MAIN 218 AIN 64
    Last reset 01:15:26 ago, cause: software
    Last software reset data not available
    Driver 0: position 1144482, 695.0 steps/mm, standstill, SG min/max 0/16, read errors 0, write errors 1, ifcnt 59, reads 35135, writes 19, timeouts 0, DMA errors 0
    Moves scheduled 469, completed 469, in progress 0, hiccups 0
    No step interrupt scheduled
    VIN: 24.6V
    MCU temperature: min 31.9C, current 32.4C, max 38.3C
    Ticks since heat task active 54, ADC conversions started 4508784, completed 4508782, timed out 0
    Last sensors broadcast 0x00000002 found 1 57 ticks ago, loop time 0
    CAN messages queued 54466, send timeouts 0, received 41274, lost 0, free buffers 36
    

    @Phaedrux said in heating failed, print starts anyway - bug?:

    Was there an error message in the console?

    No errors in the console. The heater just stopped heating and reported as "fault" in the web console.

    The print started at 100c, but what was the intended temp?

    215°C

    Can you share the first 50 lines or so of the gcode file?

    it was a quick test cube (1 wall). Please note that the same code worked without the manual calibration.

    ; generated by PrusaSlicer 2.3.0-rc2+linux-x64-GTK3 on 2021-01-13 at 17:44:36 UTC
    
    ; 
    
    ; external perimeters extrusion width = 0.60mm
    ; perimeters extrusion width = 0.60mm
    ; infill extrusion width = 0.60mm
    ; solid infill extrusion width = 0.60mm
    ; top infill extrusion width = 0.60mm
    ; support material extrusion width = 0.55mm
    ; first layer extrusion width = 0.65mm
    
    M107
    ;TYPE:Custom
    M140 S60 ; bed temperature
    M109 S215 ; set initial tool temp and wait
    M190 S60 ; wait for bed temperature
    
    G28 ; home all axes
    
    G21 ; set units to millimeters
    G90 ; use absolute coordinates
    M82 ; use absolute distances for extrusion
    G92 E0
    ; Filament gcode
    ;LAYER_CHANGE
    ;Z:0.4
    ;HEIGHT:0.4
    G1 Z0.400 F8400.000
    G1 E-0.80000 F2400.000
    G92 E0
    G1 X163.706 Y160.916 F8400.000
    G1 E0.80000 F2400.000
    ;TYPE:Skirt
    ;WIDTH:0.65
    G1 F1800.000
    G1 X164.486 Y160.769 E0.87539
    G1 X245.575 Y160.774 E8.57085
    G1 X246.286 Y160.913 E8.63958
    G1 X247.012 Y161.217 E8.71431
    G1 X247.518 Y161.553 E8.77191
    G1 X248.343 Y162.358 E8.88129
    G1 X248.848 Y163.113 E8.96752
    G1 X249.109 Y163.788 E9.03618
    G1 X249.231 Y164.488 E9.10365
    G1 X249.231 Y245.512 E16.79294
    G1 X249.056 Y246.387 E16.87763
    G1 X248.762 Y247.048 E16.94627
    

    What tuning values were you using? Can you share your config.g?

    M307 H1 R2.892 C203.0:103.0 D4.50 S1.00 V24
    

  • Moderator

    Thanks. I'll ask DC42 to take a look.

    Did auto tuning not work? Or what was the reason for manual tuning.



  • @Phaedrux said in heating failed, print starts anyway - bug?:

    Thanks. I'll ask DC42 to take a look.

    Did auto tuning not work? Or what was the reason for manual tuning.

    Does automatic tuning work now on the toolboard? I heard it will be activated in 3.3.

    I will route some cables to the main duet3 tomorrow and run the auto tuning from there.


  • Moderator

    Right, sorry, you may be correct about that and tool boards.

    It would be interesting to see what the auto tune arrives at compared to the values you arrived at.

    That's unrelated to how the heater fault was handled. Not sure exactly what the intended behaviour is in that situation. I would have expected a heater fault message in the console.



  • @Phaedrux before the auto-tuning I tried a second time manually to see if values changed. In doing so I believe I've found the problem.

    The new values are M307 H1 R2.9 C204.0:102.0 D4.00 S1.00 V24 that are very close to the previous ones and indeed I got a fault again BUT it works perfectly if I remove the second C value.

    So it seems that at least the toolboard has some issues with the second cooling time constant, removing it solves the issue (or at least it doesn't trigger the issue).

    Remains that the duet should not fault without error.


Log in to reply