Possible Heater Chamber Code Bug



  • Hello,

    I think I may have discovered a code bug in relation to heater chamber.

    Long story short - when I powered up my chamber heater, it drew more power than I anticipated (voltmeter might have been off), and blew the duex 7A heater fuse.

    I starting immediately having some problems with the following error:

    Error: Short-to-ground on drivers 0 1 2 3 4 5 6 7 8 9
    Error: Over temperature shutdown on drivers 0 1 2 3 4 5 6 7 8 9

    When I replaced the fuse and started debugging, those ultimately went away. Not exactly sure what caused it.

    Now, however, the Duet will crash any time it reads the chamber g-code (M141 H5 S10). Heater still works and I can assign that channel to a regular heater and run it that way.

    Here's the diagnostics:

    2‎:‎08‎:‎17‎ ‎PM
    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet Ethernet 1.02 or later + DueX5
    Board ID: 08DGM-9T6BU-FG3SN-6J1FL-3SJ6M-18WBG
    Used output buffers: 3 of 20 (9 max)
    === RTOS ===
    Static ram: 28380
    Dynamic ram: 96380 of which 28 recycled
    Exception stack ram used: 332
    Never used ram: 5952
    Task NETWORK ready, free stack 460
    Task HEAT blocked, free stack 1176
    Task MAIN running, free stack 3560
    === Platform ===
    Last reset 00:00:23 ago, cause: power up
    Last software reset at 2018-11-19 14:07, reason: Hard fault, spinning module GCodes, available RAM 5484 bytes (slot 3)
    Software reset code 0x4033 HFSR 0x40000000, CFSR 0x01000000, ICSR 0x0441f803, BFAR 0xe000ed38, SP 0x20004964
    Stack: 0041e831 0041f218 21000000 20008ef0 20004990 00000001 0043a2cd 0000000a 20000178 200001d8 0000008d 00000000 20004c8c 20013ec8 a5a5a5a5 20002b78 0044c6fb 200001d8 00000000 0000000a 2000aef0 2000a428 2000aef0 0000008d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 5.0ms
    MCU temperature: min 28.4, current 29.9, max 30.2
    Supply voltage: min 24.4, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0
    Driver 0: standstill, SG min/max not available
    Driver 1: standstill, SG min/max not available
    Driver 2: standstill, SG min/max not available
    Driver 3: standstill, SG min/max not available
    Driver 4: standstill, SG min/max not available
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Expansion motor(s) stall indication: no
    Date/time: 2018-11-19 14:08:14
    Slowest loop: 14.57ms; fastest: 0.07ms
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 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 ===
    Slowest loop: 14.90ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8
    Interface state: 5
    === Expansion ===
    DueX I2C errors 0


  • administrators

    @tlas said in Possible Heater Chamber Code Bug:

    Long story short - when I powered up my chamber heater, it drew more power than I anticipated (voltmeter might have been off), and blew the duex 7A heater fuse.
    I starting immediately having some problems with the following error:
    Error: Short-to-ground on drivers 0 1 2 3 4 5 6 7 8 9
    Error: Over temperature shutdown on drivers 0 1 2 3 4 5 6 7 8 9
    When I replaced the fuse and started debugging, those ultimately went away. Not exactly sure what caused it.

    I can see why that happens. The VIN monitor reports that the voltage is in the operating range of the stepper drivers, so they ought to respond correctly to SPI communications; but in fact they have no power because of the blown fuse.

    Now, however, the Duet will crash any time it reads the chamber g-code (M141 H5 S10). Heater still works and I can assign that channel to a regular heater and run it that way.

    Please install firmware 2.02RC4. If the problem still happens, post the M122 report again.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.