Quote Originally Posted by DarkAlchemist View Post
I spotted this issue after I installed his code so I fell back to the original code and it did the exact same thing. Something funky in the G29 coding, that I can't find, and that is not in the G28 or the G30. I went looking to see if could spot something that was possibly left out of G29 from 28 and 30 but no go.
Hmm, very strange. You mentioned this issue in Pronterface. Have you actually tried to start a print (that does G29) and does it also move all the axes instead of just one?