From 94fa733ee85d8fc757ffa2d36ea2e231efd5d17e Mon Sep 17 00:00:00 2001 From: Markus Hitter Date: Sun, 8 Jun 2014 22:24:03 +0200 Subject: [PATCH] home.c: don't move to zero after homing to max endstop. This can be counterproductive if the actual zero point is outside the available build room. For example, if an additional bed probing is going to happen. It also costs quite some time on the Z axis. If you actually want this behaviour, send a simple G0 XYZ after homing. --- home.c | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/home.c b/home.c index 7576907..39e9900 100644 --- a/home.c +++ b/home.c @@ -123,10 +123,6 @@ void home_x_positive() { // set position to MAX startpoint.axis[X] = next_target.target.axis[X] = (int32_t)(X_MAX * 1000.); dda_new_startpoint(); - // go to zero - t.axis[X] = 0; - t.F = MAXIMUM_FEEDRATE_X; - enqueue(&t); #endif } @@ -185,10 +181,6 @@ void home_y_positive() { // set position to MAX startpoint.axis[Y] = next_target.target.axis[Y] = (int32_t)(Y_MAX * 1000.); dda_new_startpoint(); - // go to zero - t.axis[Y] = 0; - t.F = MAXIMUM_FEEDRATE_Y; - enqueue(&t); #endif } @@ -248,9 +240,5 @@ void home_z_positive() { // set position to MAX startpoint.axis[Z] = next_target.target.axis[Z] = (int32_t)(Z_MAX * 1000.); dda_new_startpoint(); - // go to zero - t.axis[Z] = 0; - t.F = MAXIMUM_FEEDRATE_Z; - enqueue(&t); #endif }