Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

G28 max end-stop issue #42

Closed
AndrewDiehl opened this issue Dec 27, 2011 · 4 comments
Closed

G28 max end-stop issue #42

AndrewDiehl opened this issue Dec 27, 2011 · 4 comments

Comments

@AndrewDiehl
Copy link

I have my end-stops set up so X and X home to min values, and Z homes to it's max value

When I do a home to Z ( G28 Z) the Z axis homes correctly, but as soon as I issue any G command the Z axis immediately goes to Z=0 instead of staying put at Z=191.8

Also, if I home Z (max) and then home X and Y (min) the Z gets set to Z = 0 when it should be Z = 191.8 (in my case)

My End stop Settings if that helps:

Z_HOME_DIR = 1 (Max),
INVERT_Z_DIR = true,
Z_ENDSTOPS_INVERTING = false

@bkubicek
Copy link
Contributor

a cheap workaround for now might be G28 Z119.8

@pnit
Copy link

pnit commented Jan 23, 2012

I have this problem on my Y-Axis. Poking around the marlin.pde I found the following lines:

  if(code_seen(axis_codes[X_AXIS])) 
  {
    current_position[0]=code_value()+add_homeing[0];
  }

  if(code_seen(axis_codes[Y_AXIS])) {
    current_position[1]=code_value()+add_homeing[1];
  }

  if(code_seen(axis_codes[Z_AXIS])) {
    current_position[2]=code_value()+add_homeing[2];
  }

These really need to be aware of homing direction. I've never homed and set a position at the same time, so I just commented them out. Works fine.

@AndrewDiehl
Copy link
Author

Looks like this is fixed in the latest release.

seefood pushed a commit to seefood/Marlin that referenced this issue Mar 30, 2015
thinkyhead referenced this issue in thinkyhead/Marlin Sep 6, 2019
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants