KILLED: Printer halted during cuts and sitting idle

I’ve been running cuts without any problems for months. This morning, my machine just started a serious problem, and I’m seeking some help. While cutting with nobody near the machine, the job stops. The display says this:

KILLED. :
PRINTER HALTED
Please Reset

Three jobs in a row. I’m ruining wood. I Just found the machine sitting idle - not even running a job and the display switched to the “killed” message.

What I’ve done so-far - Opened the display box and blew-out any dust. I removed the red button for halting jobs, just-in-case - then covered the hole with tape. No difference. It is still halting.

Any advice for what to look for?

I think I found the problem. “Someone” did a really crappy job connecting the power with the jumpers. One of those jumpers fell out, and was making a very intermittent connection. I put in new jumpers, wetting (soldered) the ends this time. No more twist-connections. I have a 2 hour job running now, so time will tell.

1 Like

Problem is NOT solved :cry:

The power connection is SOLID now, and all the other wiring seems to have good connections. Are there any logs that I can access that might reveal the problem?

I plugged-in with Repetier Host and see the log. Here is a complete log from power-up to failure. I never started a cutting job. Does that message indicate that the abort button was pressed, or the circuit otherwise closed?

13:41:48.614 : Printer reset detected - initializing
13:41:48.627 : start
13:41:48.627 : echo:Marlin 418 bugfix-2.0.x
13:41:48.627 : echo: Last Updated: 2020-01-22 | Author: (V1 Engineering, Ryan, 418)
13:41:48.627 : echo:Compiled: Aug 18 2020
13:41:48.627 : echo: Free Memory: 3435 PlannerBufferBytes: 1488
13:41:56.345 : echo:SD init fail
13:41:56.355 : Error:EEPROM datasize error.
13:41:56.355 : echo:Index: 603 Size: 599
13:41:56.357 : echo:Hardcoded Default Settings Loaded
13:41:56.617 : FIRMWARE_NAME:Marlin 418 bugfix-2.0.x (GitHub) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1 CNC EXTRUDER_COUNT:0 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
13:41:56.617 : Cap:SERIAL_XON_XOFF:0
13:41:56.619 : Cap:BINARY_FILE_TRANSFER:0
13:41:56.619 : Cap:EEPROM:1
13:41:56.619 : Cap:VOLUMETRIC:0
13:41:56.619 : Cap:AUTOREPORT_TEMP:0
13:41:56.619 : Cap:PROGRESS:0
13:41:56.619 : Cap:PRINT_JOB:1
13:41:56.619 : Cap:AUTOLEVEL:0
13:41:56.624 : Cap:Z_PROBE:0
13:41:56.624 : Cap:LEVELING_DATA:0
13:41:56.624 : Cap:BUILD_PERCENT:0
13:41:56.624 : Cap:SOFTWARE_POWER:0
13:41:56.628 : Cap:TOGGLE_LIGHTS:0
13:41:56.628 : Cap:CASE_LIGHT_BRIGHTNESS:0
13:41:56.628 : Cap:EMERGENCY_PARSER:0
13:41:56.628 : Cap:PROMPT_SUPPORT:0
13:41:56.628 : Cap:AUTOREPORT_SD_STATUS:0
13:41:56.632 : Cap:THERMAL_PROTECTION:1
13:41:56.632 : Cap:MOTION_MODES:1
13:41:56.632 : Cap:CHAMBER_TEMPERATURE:0
13:41:56.646 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0
13:41:56.646 : echo:DEBUG:INFO,ERRORS
13:41:56.646 : Begin file list
13:41:56.647 : End file list
13:41:56.647 : echo:Unknown command: “M80”
13:41:56.652 : echo:Unknown command: “M221 S100”
13:41:56.652 : echo:DEBUG:INFO,ERRORS
13:41:56.673 : Error:!! KILL caused by KILL button/pin
13:41:56.696 : Error:Printer halted. kill() called!

I unplugged everything but the USB cord and the power. It still crashes. @Ryan, is this a bad board?
I recorded this video

I was going to guess it was emi on the lcd wires. But you said you unplugged it.

Is the bottom of the board box clean? Can you look closely at the exp pins and make sure nothing is sorted?

Can you connect a multimeter to the power and make sure that is 12V?

1 Like

Check Jeffeb3’s suggestions first, make sure the box has standoffs so none of the pins are making contact on the bottom.

12V steady, watch the meter after booting.

Re-flash is the third step. This is a new one that I have not seen.

The box is all wood, including the 7mm stand-offs. I even pulled the board out and ran it on my wooden workbench with the same results. Voltage is a steady 12.7. I don’t have an oscilloscope, so I can’t measure it over-time when the “halt” happens. I do notice though when I leave it without power for an extended period, it runs for a longer time without error - 10-15 mins. Once it “warms up”, it halts at every boot-up immediately.

I’ll let it warm-up and then test the voltage again. It could still be the power supply.

1 Like

The voltage seemed to stay very steady at 12.73 through an incident. I have a 12vDC supply that I use for my 2M radio. I’ll wire that up and see if there’s any difference.

1 Like

When was the last time you saw a power supply that was made in the USA? This thing is probably older than most people on the forum here.

Anyway… steady 12v applied. After about 5 minutes, it halted again. :rage:

09:59:49.755 : echo:Unknown command: "M221 S100"
09:59:49.755 : echo:DEBUG:INFO,ERRORS
10:04:33.776 : Error:!! KILL caused by KILL button/pin
10:04:33.798 : Error:Printer halted. kill() called!

All that’s left, I think is the board.

Does it reset if you are not using the USB, just the LCD?

That error you are seeing on repetier, if you scroll up or expand the error window, what firmware does it say is on there?

I think this is saying that it is coming from the reset button on the lcd. Maybe I need to grep the source to confirm.

I get the same error with or without the USB plug. I normally cut from the SD card and don’t use the USB. I only connected the USB to determine the cause. To be sure, I just powered the board with the LCD connected, but the USB disconnected. 8 minutes in, and it halted. As @jeffeb3 noted, it says I pressed the “stop” button on the display controller - even when the ribbon cables aren’t connected to the RAMBo.

Here’s the firmware info:

09:59:42.517 : echo:Marlin 418 bugfix-2.0.x
09:59:42.521 : echo: Last Updated: 2020-01-22 | Author: (V1 Engineering, Ryan, 418)
09:59:42.521 : echo:Compiled: Aug 18 2020

I considered flashing with the latest, but I don’t know the risks of flashing with the system in this condition.

I’ve disconnected everything, including the USB and the display. The only connection is power. I’ll run it for 20 mins, then connect the USB to read the health. I did find that when Repetier connects, it will show the log history. This is to determine if it chokes with only power and nothing else.

When you connect to repetier is should reset the board. At least last time I checked.

418 is really old, I am not sure if it had any issues. Flash the current and see if it still happens.

I don;t think we have ever had a rambo go bad after it has proven to work. I think the worst we have seen is a 1-2 bad drivers (they were missing a resistor).

I’m betting on the flash to fix it.

I’ll try the flash. I haven’t connected the dual end-stop switches yet (I need to order some connectors for extension wires). Which firmware should I use, considering it isn’t connected yet, but I want to use them in the near future?

image

I picked the “DualLR” firmware. Flashed successfully, but still has the same problem. Here’s the log. See the firmware version at the top.

12:24:35.225 : Printer reset detected - initializing
12:24:35.226 : X?JPecho:start
12:24:35.226 : Marlin 509DL 2.0.7.2
12:24:35.226 : echo: Last Updated: 2020-10-15 | Author: (V1 Engineering, Ryan, 509DL)
12:24:35.226 : echo:Compiled: Jan 18 2021
12:24:35.226 : echo: Free Memory: 3256  PlannerBufferBytes: 1552
12:24:42.092 : DIGIPOTS Loading
12:24:42.092 : DIGIPOTS Loaded
12:24:42.100 : DIGIPOTS Loading
12:24:42.100 : DIGIPOTS Loaded
12:24:42.105 : echo:V82 stored settings retrieved (649 bytes; crc 52386)
12:24:42.369 : FIRMWARE_NAME:Marlin 509DL 2.0.7.2 (Jan 18 2021 12:22:19) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:V1CNC 509DL EXTRUDER_COUNT:0 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff
12:24:42.369 : Cap:SERIAL_XON_XOFF:0
12:24:42.369 : Cap:BINARY_FILE_TRANSFER:0
12:24:42.369 : Cap:EEPROM:1
12:24:42.371 : Cap:VOLUMETRIC:0
12:24:42.371 : Cap:AUTOREPORT_TEMP:0
12:24:42.371 : Cap:PROGRESS:0
12:24:42.371 : Cap:PRINT_JOB:1
12:24:42.371 : Cap:AUTOLEVEL:0
12:24:42.371 : Cap:RUNOUT:0
12:24:42.371 : Cap:Z_PROBE:1
12:24:42.375 : Cap:LEVELING_DATA:0
12:24:42.375 : Cap:BUILD_PERCENT:0
12:24:42.375 : Cap:SOFTWARE_POWER:0
12:24:42.375 : Cap:TOGGLE_LIGHTS:0
12:24:42.379 : Cap:CASE_LIGHT_BRIGHTNESS:0
12:24:42.379 : Cap:EMERGENCY_PARSER:0
12:24:42.379 : Cap:PROMPT_SUPPORT:0
12:24:42.379 : Cap:SDCARD:1
12:24:42.379 : Cap:AUTOREPORT_SD_STATUS:0
12:24:42.383 : Cap:LONG_FILENAME:0
12:24:42.383 : Cap:THERMAL_PROTECTION:1
12:24:42.383 : Cap:MOTION_MODES:1
12:24:42.383 : Cap:ARCS:1
12:24:42.383 : Cap:BABYSTEPPING:0
12:24:42.387 : Cap:CHAMBER_TEMPERATURE:0
12:24:42.401 : X:0.00 Y:0.00 Z:200.00 E:0.00 Count X:0 Y:0 Z:80000
12:24:42.401 : echo:DEBUG:INFO,ERRORS
12:24:42.402 : echo:No media
12:24:42.402 : echo:Unknown command: "M80"
12:24:42.408 : echo:Unknown command: "M221 S100"
12:24:42.408 : echo:DEBUG:INFO,ERRORS
12:24:42.428 : Error:!! KILL caused by KILL button/pin
12:24:42.450 : Error:Printer halted. kill() called!

Start with the one that isn’t dual. Once you get through this once, you will not mind doing it again. It is more intimidating than anything.

Well, that doesn’t matter. If it is still broke.

Ok. I’ll put the non-dual firmware on now. I’m not intimidated by this. 35 years in IT/Ham radio and other geeky hobbies - this stuff is easy :slight_smile: