Quantcast
Channel: Reprap Forum - RAMPS Electronics
Viewing all articles
Browse latest Browse all 1807

Error Printer halted. kill() called! HELP ME :( (2 replies)

$
0
0
Hi,

I have RAMPS V1.4 hooked up to an Arduino Mega (that was an anet A8), I've some issues with y axis of my printer (like in this video), and I tried to resolve that changing the current in the axis driver (DRV8825). Then I tried to send G28 to homing and this error was showed:
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

Any suggestions?

Viewing all articles
Browse latest Browse all 1807

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>