Homing issues after gsender upgrade

Have the x-carve pro 4x4 machine, using carve pro, running of a Mac using sequoia 15.5. Worked very well with the gsender 14.x series. When upgraded to the gender 15.x series started having homing issues. As the spindle moved to the “home” side of any axis on its way to the 3 axis home, it would start to shake and bounce like it was bouncing off the limit switch. It would continue until I hard stopped or used the pause. It would not lock out. If I came back and moved it in the opposite direction for that axis, and then rehomed it, it would complete the home, at least in that axis. As it approached the home side of another axis it would do the same thing, continuing until I hit the stop button, moved it in the opposite direction, and then hit the home again.

any thoughts welcomed. Again, it worked fine in version 14.x and there have been no other changes to the machine or system.

@doclynn60 I’m not sure what input I can give to your issue. Since day one with gSender all the way to the newer 1.5.# versions all we ever do when we home the machine is send the “$H” command. This activates the homing procedure for any grbl-based machines

Perhaps you could try going to Config → Homing/Limits, and checking the settings for your homing are what you’d expect them to be? Otherwise this could also just be an issue with your machine hardware or electronics themselves

Chris,
Thanks for responding. I did find the issue with the shaking. The x-axis limit switch was positioned to low, so the spindle assembly would hit it intermittently. Once repositioned it worked fine. I am having issues with homing. After a cut, it goes to the work 0 just fine. Then I move it out of the way to inspect the cut, and if I try to send it back to X0, Y0, or XY0, it sends the bit straight down past the Z0 and into the work. If I jog it a little before I send it to the job 0 then it works just fine. I’ve learned to do this to avoid the stab into the work, but I haven’t figured out why it’s doing it and how to correct it so I don’t have to do the work around.
Again, Thanks for the help.

I see, would it be possible for you to follow these steps:

  • remove anything important from your machine like bits, material, etc so you don’t break anything
  • home your machine
  • set a fake zero starting location
  • move away from it
  • press the Go To XY0 button which will make the Z move down as you mentioned
  • once the Z moves down, go to the Stats tab and immediately click the button to download a diagnostic file (on the right side)
  • attach that file here

If I can see that file I might find what’s causing your issue