So, I finally got around to making me one of those nifty tool setters. Dunno how I got along without it for so long now. It's kinda like indoor plumbing. Anyhow, I have some strange behavior with it. I have the feed set way up in the macro (using Scott and Gregs code) , say 50 or 75 ipm. When I first start up Mach, it works flawlessly. Then I open up a file, run the file, and then, somehow, the probing routine takes the acceleration settings from the X axis to drive the Z axis. This results in a massive over-travel, and a tool crunch. After a lengthy period of trying to troubleshoot, I decide to delete everything and re-install Mach. So I get all the pins set, axis set, screens installed, script modified, ready to rock 'n roll. As soon as I hit the zero button, it once again took the X axis accel. So I load up a file, run it, and low and behold the probe function works as its supposed to. That's exactly the OPPOSITE of the way it didn't work before the re-install. Strange indeed. So, I mucked around with a gazillion different things, and it appears that some times it works one way, and other times it works another way. One thing did remain constant, however....A probe command from a fresh start-up is different from a probe command after a g-code file has been ran. Obviously, if the feed rate is set to something very slow, it works, or at least it appears to work, as the accel is really not an issue. Any ideas??