im currently building a zenxy table but my homing seems off.
im using a rambo board from my lowrider2 build. i reflashed firmware to be zenxy rambo firmware and the gantry seems to move fine.
At homing the “printhead” runs into the “motor mount” activating (light activates) the optical end stops but it just keeps running into the mount not initiating a “bump off” to set the position to 0. i end up kill switching to stop it.
The end stops trigger manually (checked with m119)
I have a ZenXY that is running a RAMPS stack on Marlin, works fine.
I have opto end stops that are positive and negative trigger. I used a different set first before the type that V1 uses (table was originally a V1, upgraded to a V2) and I had to change the pin defjnitions in the firmware, and I don’t remember if I changed it back when I updated the endstops… M119 should tell you though.
Homing order is important. Y before X. Also the pull-out for X is weird because of the long trigger bar.
i was going to send a part of my config showing the homing section, but then i said lets take another look.
Double check stuff, i would like to say i know exactly what i did but i cant. But my best guess is my motors were plugged in wrong, or backwards. I also may have been wrong with what axis was what thinking it was moving correctly but on the wrong axis in my controller. I have it mounted “upside” down causing me to think x was moving in + when really movinng - …?
And correct me if im wrong, the two motors work in tandem to move both axis?
Also i may have been clicking home x instead of home Y, not really realizing thats impossible.
So ultimately i think ill thank both folks that responded. And V1E for providing this forum, because it only takes being able to talk/text it out with others to help, even if its only to help clear the mind.
Homing Works fine. I CAN NOT WAIT TO MOUNT IT TO A FINISHED TABLE
ALSO A WORD TO THE WISE. YOUR OPTICAL ENDSTOPS WILL NOT WORK CORRECTLY IF YOU PRINT THIS IN CLEAR PETG. (**this was found out before any homing issues arose)
That’s what we call “rubber duck debugging”. Explaining the issue to someone else is enough for you to figure out the issue. You can use a rubber duck as the audience (but posting here will help someone in the future, for sure).