Autoleveling issue with BLTOUCH
Posted by strangeloop
|
Autoleveling issue with BLTOUCH September 12, 2018 06:41PM |
Suddenly, my Anycubic Kossel Linear Plus printer is sending the print head crashing into the bed whenever i run the G29 command.
Here is the debug log:
There is a strange call to do_blocking_move to -300 just after the bltouch is deployed.
Has anyone seen this? Any suggestions on what could be happening?
Here is the debug log:
18:26:03.746 : X:0.00 Y:0.00 Z:233.83 E:0.00 Count X: 37578 Y:37578 Z:37578 18:26:13.164 : echoEBUG:LEVELING 18:26:17.454 : current_position=(0.00, 0.00, 233.83) : >>> gcode_G29 18:26:17.454 : Machine Type: Delta 18:26:17.454 : Probe: BLTOUCH 18:26:17.455 : Probe Offset X:0 Y:-35 Z:-1.40 (Middle-Front & Below Nozzle) 18:26:17.455 : Auto Bed Leveling: BILINEAR 18:26:17.455 : G29 Auto Bed Leveling 18:26:17.458 : current_position=(0.00, 0.00, 233.82) : sync_plan_position_kinematic 18:26:17.463 : current_position=(0.00, 0.00, 233.82) : setup_for_endstop_or_probe_move 18:26:17.465 : current_position=(0.00, 0.00, 233.82) : set_probe_deployed 18:26:17.465 : deploy: 1 18:26:17.467 : do_probe_raise(50.00) 18:26:17.469 : >>> do_blocking_move_to(0.00, 0.00, 233.82) 18:26:17.469 : destination=(0.00, 0.00, 233.82) : set_destination_to_current 18:26:17.474 : current_position=(0.00, 0.00, 233.82) : xy move 18:26:17.475 : <<< do_blocking_move_to 18:26:17.475 : reset_bed_level 18:26:17.477 : >>> probe_pt(-55.00, -55.00, no stow) 18:26:17.482 : current_position=(0.00, 0.00, 233.82) : 18:26:17.482 : do_probe_raise(10.00) 18:26:17.482 : >>> do_blocking_move_to(-55.00, -20.00, 233.82) 18:26:17.483 : destination=(0.00, 0.00, 233.82) : set_destination_to_current 18:26:17.915 : current_position=(-55.00, -20.00, 233.82) : xy move 18:26:17.978 : <<< do_blocking_move_to 18:26:17.982 : current_position=(-55.00, -20.00, 233.82) : set_probe_deployed 18:26:17.982 : deploy: 1 18:26:17.984 : current_position=(-55.00, -20.00, 233.82) : >>> run_z_probe 18:26:17.986 : >>> do_blocking_move_to(-55.00, -20.00, 11.40) 18:26:17.988 : destination=(-55.00, -20.00, 233.82) : set_destination_to_current 18:26:17.992 : current_position=(-55.00, -20.00, 233.82) : xy move 18:26:17.994 : destination=(-55.00, -20.00, 11.40) : prepare_uninterpolated_move_to_destination 18:26:17.998 : current_position=(-55.00, -20.00, 11.40) : z lower move 18:26:25.720 : <<< do_blocking_move_to 18:26:25.720 : current_position=(-55.00, -20.00, 11.40) : >>> do_probe_move 18:26:25.774 : set_bltouch_deployed(1) 18:26:25.774 : >>> do_blocking_move_to(-55.00, -20.00, -300.26) 18:26:25.775 : destination=(-55.00, -20.00, 11.40) : set_destination_to_current 18:26:25.780 : current_position=(-55.00, -20.00, 11.40) : xy move 18:26:25.782 : destination=(-55.00, -20.00, -300.26) : prepare_uninterpolated_move_to_destination 18:26:25.786 : current_position=(-55.00, -20.00, -300.26) : z lower move 18:26:28.550 : Printer reset detected - initalizing
There is a strange call to do_blocking_move to -300 just after the bltouch is deployed.
Has anyone seen this? Any suggestions on what could be happening?
Sorry, only registered users may post in this forum.