Extruder Heater Activation turns off the printer.

Just finished putting a Micro Delta Rework 3D printer together. Installed Repeater host, calibration was smooth sailing until I tried to heat up the extruder.

I can heat up the heat bed no trouble. But every time I click on Extruder Heater Activation, it shuts the printer down.The printer turns back on immediately, and reconnecting to the printer happens without issue. But clicking the extruder heater activation button turns it off again. It's almost as if I had hit the reset button.

It doesn't even give me an error message. Does this happen often? What can I do about it?

Comments

  • Check the log - many firmwares write the restart reason like brown out (power loss if you have a short or PSU has not enough power), reset or watchdog.

    Depending on this you can search further. The problem is either firmware using wrong pins for heater or hardware problem like using too much power or creating a short or there is a bridge between an output and something that can trigger reset.

    Host is just sending the command "M104 Stemperature".
  • Hrm. Here is a copy of the log. The M104 is when the restart happens. I'm sorry, I don't know if there is an error message in there or not. Does this give a clue as to what might be happening?

    16:55:03.573 : N24 M105*17
    16:55:03.577 : ok T:22.2 /0.0 0
    16:55:03.577 : ok
    16:55:06.633 : N25 M105*16
    16:55:06.636 : ok T:22.2 /0.0 0
    16:55:06.636 : ok
    16:55:09.695 : N26 M105*19
    16:55:09.699 : ok T:22.3 /0.0 0
    16:55:09.699 : ok
    16:55:10.358 : N27 M104 T0 S200*22
    16:55:10.360 : ok
    16:55:10.361 : ok
    16:55:25.338 : No start signal detected - forcing start
    16:55:25.340 : N1 M110*34
    16:55:25.341 : ok
    16:55:25.341 : N2 M115*36
    16:55:25.342 : ok
    16:55:25.342 : N3 M105*36
    16:55:25.343 : ok
    16:55:25.343 : N4 M114*35
    16:55:25.344 : ok
    16:55:25.367 : ok T:22.3 /0.0 0
    16:55:25.367 : N5 M111 S6*98
    16:55:25.368 : ok
    16:55:25.368 : ok C: X:0.0000 Y:0.0000 Z:0.0000 E:0.000
    16:55:25.368 : ok
    16:55:25.369 : N6 T0*60
    16:55:25.369 : ok
    16:55:25.369 : N7 M20*22
    16:55:25.371 : ok
    16:55:25.371 : N8 M80*19
    16:55:25.371 : ok
    16:55:25.372 : N9 M105*46
    16:55:25.372 : ok
    16:55:25.380 : Begin file list
    16:55:25.380 : firmware.cur
    16:55:25.380 : system volume information/
    16:55:25.381 : .dropbox.device
    16:55:25.381 : config.txt
    16:55:25.381 : read_me.txt
    16:55:25.381 : spoolholder_v2.gcode
    16:55:25.382 : End file list
    16:55:25.382 : ok
    16:55:25.382 : ok
    16:55:25.383 : ok
    16:55:25.384 : ok
    16:55:25.389 : ok T:22.3 /0.0 0
    16:55:25.389 : ok
    16:55:28.398 : N10 M105*22
    16:55:28.408 : ok T:22.2 /0.0 0
    16:55:28.408 : ok
    16:55:31.462 : N11 M105*23
    16:55:31.467 : ok T:22.3 /0.0 0

  • What firmware are you using? Seems like it is not very chatty or you missed the start also I see M104 mentioned. So I guess no hint from firmware side for the error. So you have to check all possible reasons I named.
  • I see, tanks for your help.
Sign In or Register to comment.