why did my Printer melt?

Killernoy

My E3D Kraken did melt because every heater output is set to 100% at startup?
config.g:

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Drives
M569 P0 S1 ; Physical drive 0 goes forwards
M569 P1 S1 ; Physical drive 1 goes forwards
M569 P2 S1 ; Physical drive 2 goes forwards
M569 P3 S1 ; Physical drive 3 goes forwards
M569 P4 S1 ; Physical drive 4 goes forwards
M569 P5 S1 ; Physical drive 5 goes forwards
M569 P6 S1 ; Physical drive 6 goes forwards
M569 P7 S1 ; Physical drive 7 goes forwards
M569 P8 S1 ; Physical drive 8 goes forwards
M569 P9 S1 ; Physical drive 9 goes forwards
M584 X5 Y6 Z0:1:2:3 E4:7:8:9 ; Apply custom drive mapping
M671 X-230.5:-230.5:230.5:230.5 Y-286:286:286:-286 S2
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; Set steps per mm
M566 X50 Y50 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X40000.00 Y16000.00 Z180.00 E1200.00 ; Set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
M906 X2000.00 Y2000.00 Z500.00 E800.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-215.5 Y-215.5 Z0 S1 ; Set axis minima
M208 X 215.5 Y 215.5 Z500 S0 ; Set axis maxima

; Endstops
M574 X1 S0 P"xstop" ; X min active low endstop switch
M574 Y1 S0 P"ystop" ; Y min active low endstop switch

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M558 P9 C"^zprobe.in" H5 F120 T6000 ; BLTouch connected to Z probe IN pin
M950 S1 C"!duex.pwm5" ; create servo/gpio 0 on heater 3 pin on expansion
G31 P500 X-35 Y0 Z1.5 ; Set Z probe trigger value, offset and trigger height

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700
M950 H0 C"!bedheat" T0 ; Heated Bed Internal Temp Sensor (Activ)
M308 S1 P"e0_temp" Y"thermistor" T100000 B4138 R4700
M950 H1 C"!e0heat" T1 ; Hotend 1
M308 S2 P"e1_temp" Y"thermistor" T100000 B4138 R4700
M950 H2 C"!e1heat" T2 ; Hotend 2
M308 S3 P"e2_temp" Y"thermistor" T100000 B4138 R4700
M950 H3 C"!duex.e2heat" T3 ; Hotend 3
M308 S4 P"e3_temp" Y"thermistor" T100000 B4138 R4700
M950 H4 C"!duex.e3heat" T4 ; Hotend 4
M308 S5 P"e4_temp" Y"thermistor" T100000 B4138 R4700
M950 H5 C"e6heat" T5 ; Heated Bed Edge Temp Sensor (Dummy)

; Fans
M950 F2 C"!Fan0"
M950 F3 C"!Fan1"

; Tools
M563 P0 D0 H2 ; Define tool 0
G10 P0 X-10 Y+10 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P1 D1 H3 ; Define tool 1
G10 P1 X-10 Y-10 Z0 ; Set tool 0 axis offsets
G10 P1 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P2 D2 H4 ; Define tool 2
G10 P2 X10 Y-10 Z0 ; Set tool 0 axis offsets
G10 P2 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
M563 P3 D3 H5 ; Define tool 3
G10 P3 X10 Y10 Z0 ; Set tool 0 axis offsets
G10 P3 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

; Custom settings are not configured

; Miscellaneous
T0 ; Select first tool

jay_s_uk

If they're on from start up then the mosfet has failed due to more than likely a short in the wiring.
Any pictures of the melted hot end?

Phaedrux

Which board? Firmware?

Killernoy

@jay_s_uk it is disassembled right now but the Heater blocks are melted the ´last temp i saw before shut down were around 650 C

Killernoy

@Phaedrux Duet2 Wifi with duex5 and RRF3

Killernoy

One of the Heatblocks the thermistor is still in it but I had to rip the cable of because plastic was molten around it

Phaedrux

@Killernoy said in why did my Printer melt?:

RRF3

which version specifically?

Phaedrux

@Killernoy said in why did my Printer melt?:

every heater output is set to 100% at startup?

Every heater was on full power at startup?

Killernoy

This post is deleted!

Killernoy

@Phaedrux said in why did my Printer melt?:

@Killernoy said in why did my Printer melt?:

every heater output is set to 100% at startup?

Every heater was on full power at startup?

Yes

Killernoy

@Phaedrux said in why did my Printer melt?:

@Killernoy said in why did my Printer melt?:

every heater output is set to 100% at startup?

Every heater was on full power at startup?

3.0 beta12 2019-11-02b1

Phaedrux

Is it still doing it? Can you get an M122 diagnostic report from it?

Killernoy

@Killernoy said in why did my Printer melt?:

@Phaedrux said in why did my Printer melt?:

@Killernoy said in why did my Printer melt?:

every heater output is set to 100% at startup?

Every heater was on full power at startup?

Yes

correction not every just Bed and E2 E3 and E6

Killernoy

@Phaedrux said in why did my Printer melt?:

Is it still doing it? Can you get an M122 diagnostic report from it?

Yes it is

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.0beta12 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-95BLL-N65TJ-6J9F4-3S46L-1JWVL
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25812
Dynamic ram: 99608 of which 0 recycled
Exception stack ram used: 256
Never used ram: 5396
Tasks: NETWORK(ready,1448) HEAT(suspended,920) DUEX(suspended,160) MAIN(running,3652) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:43 ago, cause: power up
Last software reset at 2019-12-17 16:50, reason: Unknown, spinning module Webserver, available RAM 4992 bytes (slot 2)
Software reset code 0x40b2 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20001ec4 Task 0x5754454e
Stack: 0044f28f 00450e22 81000000 00000000 40740000 3edb6db7 b7b4d800 3331bb4c 40000000 3f317200 b5ddea0e 388aa908 41e2ece8 00000000 00000000 00000000 00000000 00000000 40400000 80000010 00449277 00000001 004067db
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 24.9, current 29.1, max 29.4
Supply voltage: min 0.3, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 132068223
Slowest loop: 0.76ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 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 -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 ready with "m122" 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: 15.55ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8

WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 2c:3a:e8:0a:f2:1b
WiFi Vcc 3.41, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 26096
WiFi IP address 192.168.178.77
WiFi signal strength -72dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
ok

dc42

I'm sorry to hear of your misfortune. The only time I have heard of this happening before was when there was over-voltage on the +5V rail (due to a short to +12V or +24V) which resulted in failure of the mosfet driver chip. It's labelled U11 and it's close to the reset button and extruder heater mosfets. Does it look damaged?

Are you powering anything external to the Duet from the +5V supply? What fan voltage are you using?

Killernoy

@dc42 said in why did my Printer melt?:

I'm sorry to hear of your misfortune. The only time I have heard of this happening before was when there was over-voltage on the +5V rail (due to a short to +12V or +24V) which resulted in failure of the mosfet driver chip. It's labelled U11 and it's close to the reset button and extruder heater mosfets. Does it look damaged?

No it does not look damaged to me, but take a look for your self

Are you powering anything external to the Duet from the +5V supply?

The fans

What fan voltage are you using?

5V

jay_s_uk

U11 looks damaged to me. it has a hole in it

Killernoy

@jay_s_uk said in why did my Printer melt?:

U11 looks damaged to me. it has a hole in it

I don´t know if I´m right but to me it looks like a Texas Instruments Logo IMG_20191217_174953[1].jpg

dc42

U11 looks OK to me in that photo, but the symptom suggests to me that it has failed.

As you are running 5V fans. I suggest you check very carefully that there is no possibility of a short between the fan wires and the hot end heater wires. We've seen users damage Duets before because of such shorts. That's why I argued (successfully) for us not to provide a jumper to select 5V fans on Duet 3 (OTOH, Duet 3 has a 12V regulator on board so that 12V fans can be used).

Some fans and other devices (especially servos) pump power into the supply rail when they turn off, although in the case of small brushless fans, the smoothing capacitors on the supply rail should take care of that without excessive over-voltage.

Phaedrux

This post is deleted!