*SOLVED*LCD displays "killed", cuts power to bed/hotend

Having a problem? Post it here and someone will be along shortly to help
Post Reply
User avatar
Mike B
Printmaster!
Posts: 44
Joined: Wed May 21, 2014 1:10 pm
Location: West Lafayette, IN

*SOLVED*LCD displays "killed", cuts power to bed/hotend

Post by Mike B »

I was having issues with my bed getting up to temp so installed new power supply RM750. Now when I turn the bed and hotend either through LCD or Repetier, and do anything like home the printer, it shuts power off to the heaters and displays "killed" on the LCD. The printer is basically useless at this point. I added a copper heat spreader, PEI, power supply and Rambo cooling fan recently. I took the copper and glass off thinking maybe the Rambo was overheating and pointed fans at the Rambo with the LCD panel off.. still get same result. Any ideas?

**My Solution**
In case anyone else has this problem, reflashing the EEPROM was the solution. After power on of the Rostock Max, it would change from "Rostock Ready" to "killed" after about 10 seconds and reloading the EEPROM fixed it.
User avatar
Eaglezsoar
ULTIMATE 3D JEDI
Posts: 7185
Joined: Sun Apr 01, 2012 5:26 pm

Re: *SOLVED*LCD displays "killed", cuts power to bed/hotend

Post by Eaglezsoar »

Mike B wrote:I was having issues with my bed getting up to temp so installed new power supply RM750. Now when I turn the bed and hotend either through LCD or Repetier, and do anything like home the printer, it shuts power off to the heaters and displays "killed" on the LCD. The printer is basically useless at this point. I added a copper heat spreader, PEI, power supply and Rambo cooling fan recently. I took the copper and glass off thinking maybe the Rambo was overheating and pointed fans at the Rambo with the LCD panel off.. still get same result. Any ideas?

**My Solution**
In case anyone else has this problem, reflashing the EEPROM was the solution. After power on of the Rostock Max, it would change from "Rostock Ready" to "killed" after about 10 seconds and reloading the EEPROM fixed it.
That is a great tip and others have had the same problem. Now I will know what to advise thanks to your tip. Thanks!
Post Reply

Return to “Troubleshooting”