josh
/
Teacup_Firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Markus Hitter 2014-06-08 22:24:03 +02:00
parent e2f793c2b3
commit 94fa733ee8
1 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
home.c
View File

@ -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
}