Error Printer halted. kill() called! HELP ME October 08, 2020 08:35AM |
Registered: 3 years ago Posts: 4 |
Connecting to: /dev/ttyUSB0 Changing monitoring state from "Offline" to "Opening serial port" Connected to: Serial(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor Changing monitoring state from "Opening serial port" to "Connecting" Send N0 M110 N0*125 Send N0 M110 N0*125 Recv start Recv echo:Marlin 1.1.9 Send N0 M110 N0*125 Recv echo: Last Updated: 2018-08-01 | Author: (Lorenzo, test config) Recv echo:Compiled: Oct 8 2020 Recv echo: Free Memory: 5602 PlannerBufferBytes: 1232 Recv echo:Hardcoded Default Settings Loaded Recv echo: G21 ; (mm) Recv echo:Filament settings: Disabled Recv echo: M200 D1.50 Recv echo: M200 D0 Recv echo Steps per unit: Recv echo: M92 X266.67 Y266.67 Z1133.86 E500.00 Recv echo:Maximum feedrates (units/s): Recv echo: M203 X300.00 Y300.00 Z5.00 E25.00 Recv echo:Maximum Acceleration (units/s2): Recv echo: M201 X3000 Y3000 Z100 E10000 Recv echo:Acceleration (units/s2): P R T Recv echo: M204 P3000.00 R3000.00 T3000.00 Recv echo:Advanced: Q S T X Y Z E Recv echo: M205 Q20000 S0.00 T0.00 X10.00 Y10.00 Z0.30 E5.00 Recv echo:Home offset: Recv echo: M206 X0.00 Y0.00 Z0.00 Recv echo PID settings: Recv echo: M301 P22.20 I1.08 D114.00 Recv ok Changing monitoring state from "Connecting" to "Operational" Send N0 M110 N0*125 Recv ok Send N1 M115*39 Recv FIRMWARE_NAME:Marlin 1.1.9 (Github) SOURCE_CODE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Marvin EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff Recv Cap SERIAL_XON_XOFF:0 Recv Cap:EEPROM:0 Recv Cap:VOLUMETRIC:1 Recv Cap:AUTOREPORT_TEMP:1 Recv Cap PROGRESS:0 Recv Cap PRINT_JOB:1 Recv Cap:AUTOLEVEL:0 Recv Cap:Z_PROBE:0 Recv Cap:LEVELING_DATA:0 Recv Cap:BUILD_PERCENT:0 Recv Cap SOFTWARE_POWER:0 Recv Cap:TOGGLE_LIGHTS:0 Recv Cap:CASE_LIGHT_BRIGHTNESS:0 Recv Cap:EMERGENCY_PARSER:0 Recv Cap:AUTOREPORT_SD_STATUS:0 Recv Cap:THERMAL_PROTECTION:1 Recv ok Send M21 Recv echo:Unknown command: "M21" Recv ok Send M155 S2 Recv ok Send G91 Recv ok Send G1 Y100 F6000 Recv ok Send G90 Recv ok Send G91 Recv ok Send G28 Z0 Recv T:21.52 /0.00 @:0 Recv echo busy processing Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly Recv T:21.41 /0.00 @:0 Recv echo busy processing Recv T:21.84 /0.00 @:0 Recv echo busy processing Recv T:21.41 /0.00 @:0 Recv echo busy processing Recv T:21.68 /0.00 @:0 Recv Error Printer halted. kill() called! Changing monitoring state from "Operational" to "Error: Printer halted. kill() called!" Send M112 Send N2 M112*35 Send N3 M104 T0 S0*34 Send N4 M140 S0*97 Changing monitoring state from "Error: "Printer halted". kill() called!" to "Offline (Error: Printer halted. kill() called!)" Connection closed, closing down monitor
Re: Error Printer halted. kill() called! HELP ME October 08, 2020 09:36AM |
Registered: 6 years ago Posts: 1,863 |
Re: Error Printer halted. kill() called! HELP ME October 08, 2020 11:13AM |
Registered: 3 years ago Posts: 4 |
Re: Error Printer halted. kill() called! HELP ME October 08, 2020 05:17PM |
Registered: 6 years ago Posts: 1,863 |
Re: Error Printer halted. kill() called! HELP ME October 11, 2020 02:31PM |
Registered: 3 years ago Posts: 4 |
Quote
Roberts_Clif
Ok???
What are the specs for your Stepper motors.
Current Limit = VREF × 2
So, for example, if you have a stepper motor rated for 1 A, you can set the current limit to 1 A by setting the reference voltage to 0.5 V.
Re: Error Printer halted. kill() called! HELP ME October 11, 2020 08:15PM |
Admin Registered: 13 years ago Posts: 6,995 |
Re: Error Printer halted. kill() called! HELP ME October 12, 2020 03:10AM |
Registered: 3 years ago Posts: 4 |
Before homing, I've done other tests with steppers and endstops but all worked perfectly. Only when I send the gcode for homing, the printer logs this errorQuote
Dust
you can hear there is plenty of current, issue is something else.
I would guess a broken wire between stepper motor and stepper driver.
Have you does basic tests? (before you try homing)
ie move X left and right with gcode or lcd., does it move left and right correctly?
move Y back and forward, does it move back and forward?
move Z up and down, does it move up and down?
and check endstops work with a M119 and manually test each end stop by sending M119 while not triggered, then holding down endstop with finger send second M119 and confirm it changes from open to triggered for every endstop.
Your error log shows G28 Z0, so it is trying to home Z, nothing to do with Y at all.
Re: Error Printer halted. kill() called! HELP ME October 12, 2020 05:54AM |
Admin Registered: 13 years ago Posts: 6,995 |