Welcome! Log In Create A New Profile

Advanced

Errorrinter halted. kill() called! [ERROR] Errorrinter halted. kill() called!

Posted by Coolerooney 
Errorrinter halted. kill() called! [ERROR] Errorrinter halted. kill() called!
October 01, 2020 01:36PM
hi all

tried my luck at the pronterface forum- alas, no luck there…….

need help here- Pronterface keeps shutting down my " prints" after 3 cycles, motors move normally- with the KILL message:

Print started at: 19:08:14
echo:busy: processing
echo:busy: processing
echo:busy: processing
Errorrinter halted. kill() called!
[ERROR] Errorrinter halted. kill() called!

application is CNC
have dummy thermocouple 998/999 on tried various settings
commented out various temp controls:

MARLIN:
#define TEMP_SENSOR_0 999
//#define TEMP_SENSOR_1 0
//#define TEMP_SENSOR_2 0
//#define TEMP_SENSOR_3 0
//#define TEMP_SENSOR_4 0
//#define TEMP_SENSOR_BED 0
//#define TEMP_SENSOR_CHAMBER 0

// Dummy thermistor constant temperature readings, for use with 998 and 999
#define DUMMY_THERMISTOR_998_VALUE 0
#define DUMMY_THERMISTOR_999_VALUE 0

// Use temp sensor 1 as a redundant sensor with sensor 0. If the readings
// from the two sensors differ too much the print will be aborted.
//#define TEMP_SENSOR_1_AS_REDUNDANT
//#define MAX_REDUNDANT_TEMP_SENSOR_DIFF 10

// Extruder temperature must be close to target for this long before M109 returns success
//#define TEMP_RESIDENCY_TIME 10 // (seconds)
//#define TEMP_HYSTERESIS 3 // (degC) range of +/- temperatures considered "close" to the target one
//#define TEMP_WINDOW 1 // (degC) Window around target to start the residency timer x degC early.

// Bed temperature must be close to target for this long before M190 returns success
//#define TEMP_BED_RESIDENCY_TIME 10 // (seconds)
//#define TEMP_BED_HYSTERESIS 3 // (degC) range of +/- temperatures considered "close" to the target one
//#define TEMP_BED_WINDOW 1 // (degC) Window around target to start the residency timer x degC early.

// The minimal temperature defines the temperature below which the heater will not be enabled It is used
// to check that the wiring to the thermistor is not broken.
// Otherwise this would lead to the heater being powered on all the time.
//#define HEATER_0_MINTEMP 5
//#define HEATER_1_MINTEMP 5
//#define HEATER_2_MINTEMP 5
//#define HEATER_3_MINTEMP 5
//#define HEATER_4_MINTEMP 5
//#define BED_MINTEMP 5

// When temperature exceeds max temp, your heater will be switched off.
// This feature exists to protect your hotend from overheating accidentally, but *NOT* from thermistor short/failure!
// You should use MINTEMP for thermistor short/failure protection.
//#define HEATER_0_MAXTEMP 275
//#define HEATER_1_MAXTEMP 275
//#define HEATER_2_MAXTEMP 275
//#define HEATER_3_MAXTEMP 275
//#define HEATER_4_MAXTEMP 275
//#define BED_MAXTEMP 150


also:
//#define PREVENT_COLD_EXTRUSION
//#define EXTRUDE_MINTEMP 170

/**
* Prevent a single extrusion longer than EXTRUDE_MAXLENGTH.
* Note: For Bowden Extruders make this large enough to allow load/unload.
*/
//#define PREVENT_LENGTHY_EXTRUDE
//#define EXTRUDE_MAXLENGTH 200


//#define THERMAL_PROTECTION_HOTENDS // Enable thermal protection for all extruders
//#define THERMAL_PROTECTION_BED // Enable thermal protection for the heated bed


endstops are ok

keep getting the ^*^*TT*&!!! error message!

help very much appreciated

thx!

C
Re: Errorrinter halted. kill() called! [ERROR] Errorrinter halted. kill() called!
October 01, 2020 09:23PM
even if you disable thermistors in firmware if your gcode contains heating codes.. it will cause this error.

open up your gcode file and look for any M140, M190, M141, M191 M104 or M109
You need to remove all of these.

On machines like this I disabled these gcodes in marlin so it doesn't know what they are and just skips them. No need to edit the gcode then
Re: Errorrinter halted. kill() called! [ERROR] Errorrinter halted. kill() called!
October 02, 2020 01:32AM
The other option is you have home command in the gcode and no endstops.. depending on how you have it configured, the machine will try and move to home and after it thinks it moves > max distance for the axis it errors.

gcode is just text

you can send each line in pronterface and determine which one is hanging up...
Sorry, only registered users may post in this forum.

Click here to login