Re: Z-Axis moving too far
Posted: Fri Feb 15, 2019 2:46 pm
I had been trying for the past year to get this working. The update was ok but adding Gcode: "M92 Z400" command and the Gcode: "M500" to save all worked perfectly.
Geeetech
Here you can share you great ideas about hardware innovation. Here you can enjoy more professional and specialized services, Here is a platform for you to make a difference!
http://forum.geeetech.com/
Z-Axis moving too far
Page 2 of 2
Re: Z-Axis moving too far
Posted: Thu Feb 28, 2019 4:43 am
Great advice, would you know what M92 should be posted if it doesn't have the T8 lead screws? Cheers
Re: Z-Axis moving too far
Posted: Tue Apr 09, 2019 3:15 am
This fixed my problems!
I had actually used M206 to set the Z-axis offset but then my models were printing about 800% too tall.
Here is the M206 documantation:
http://marlinfw.org/docs/gcode/M206.html
If you used that, then you'll need to set the offset to zero when you fix the steps/mm issue with M92.
Now I can do all the other stuff needed to get my prints to come out correctly.
I had actually used M206 to set the Z-axis offset but then my models were printing about 800% too tall.
Here is the M206 documantation:
http://marlinfw.org/docs/gcode/M206.html
If you used that, then you'll need to set the offset to zero when you fix the steps/mm issue with M92.
Now I can do all the other stuff needed to get my prints to come out correctly.
Re: Z-Axis moving too far
Posted: Tue Apr 09, 2019 4:26 am
After further tinkering and testing, I found that I actually needed the steps/mm and z-axis offset to get things working properly.vujsa wrote: Tue Apr 09, 2019 3:15 am This fixed my problems!
I had actually used M206 to set the Z-axis offset but then my models were printing about 800% too tall.
Here is the M206 documantation:
http://marlinfw.org/docs/gcode/M206.html
If you used that, then you'll need to set the offset to zero when you fix the steps/mm issue with M92.
Now I can do all the other stuff needed to get my prints to come out correctly.
So if you find that neither correction fixes the issue, you may need to do both.