-
Notifications
You must be signed in to change notification settings - Fork 16
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
Home X sometimes fails #22
Comments
I have just done your steps and got the same response, Z moves upwards a 1cm and X moves 1cm away from home. |
Duplicate Probably related to newer marlin version. Will try to merge the fixes up to 1.1.4 of marlin when i find time to do it |
I have this same issue with the stock version of the MakerSelect and Wanhao firmwares. As a workaround, If you disable the steppers before homing, it works as expected. It must do something different if it already thinks it is homed. I've added this to my GCode for starting prints and resuming after a pause (for filiment change), and it works well. I do still see the issue when using the lcd for homing/leveling. |
Probably a cheap way to fix it but if you add a M84 command at the beginning of the home X function you could solve this problem from multiple angles. Not sure if adding it there would be destructive to other functions. |
I can confirm that I also have this problem, both with stock Monoprice firmware and i3Plus+. Also, disabling steppers then rehoming seems to always work. So, it's definitely a widespread issue. |
I also had this issue and I had never seen it before until after I installed Beta 3. I was running Wanhao V09 before that. |
Same issue here on a version of master from a few weeks ago. Thanks for the detailed repro steps @pigrew |
I'm using my own build of the beta3 firmware. Sometimes, the on-screen HOME X command fails.
What happens is that the Z axis moves up about 1 cm, and then the X axis moves right about 1 cm. The X axis isn't homed.
Can anyone else replicate this?
The USB monitor lists "G1 E1 F120", "G90", "G28 X0" as being enqueued.
The text was updated successfully, but these errors were encountered: