-
Notifications
You must be signed in to change notification settings - Fork 293
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
Zmin Probe G38.2 Not Working #250
Comments
Forgot to mention. st = 0 |
G38.2 is used for auto leveling. Should you be using G28.2 to Home Z using your touch plate? I am not clear what "It just keeps on chugging" means |
Hi thanks for the feedback. That was a typo on the GCode command. "keeps chugging" = means that once it contacts the touch plate it just keeps moving the z-axis down and doesn't register the hit. |
Give https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Description-and-Operation a read. |
Thanks
On Wednesday, April 15, 2020, 04:27:43 p.m. EDT, Carl McGrath <[email protected]> wrote:
Give https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Description-and-Operation a read.
Do you have Z min set as home as well as NO (st=0)?
Otherwise, it sounds like you are using this process https://github.com/synthetos/TinyG/wiki/Automatic-Z-Homing-When-Milling-PCBs
Here is a thread using G38.2 probing https://openbuilds.com/threads/touch-plate-sends-z-axis-in-the-wrong-direction.11643/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hello!
I have a V0.97 TinyG with firmware build 440.20.
I had a touch plate Z probe setup working. Now it doesn't work.
I've confirmed no broken wires by continuity test.
I've set zsn to all possible settings.
Nothing fancy just a roach clip and a touch pad. When there is continuity it should trigger the tinyG to set Z zero. It just keeps on chugging.
Anyone have any ideas?
I'm thinking a board issue as it was working in the past. As far as I know I didn't change anything to affect it.
Thanks.
The text was updated successfully, but these errors were encountered: