Please help me get this Homing Sequence Right

eighthaxis wrote:

To be even more clear the positive and negative limit switches on each axis are connected to the same physical input for that axis.
So even though there are 8 limit switches ( 2 each on axis XYZ) and 1 for each rotary axis they are only using a total of 5 inputs on the Mesa Card.

Why would you do that? you have the switches, they should be one input for each. There should be plenty on mesa board. I didnt check which one you had but, drop the neg limit then.

Did you get it working?

No just even more confused

I did what you said Tommy

net y-home-sw <= hm2_5i25.0.7i77.0.0.input-01
net both-y <= hm2_5i25.0.7i77.0.0.input-01


All that should be

net both-home-y <= hm2_5i25.0.7i77.0.0.input-01

now here is my newest error and files.:
Debug file information:
Note: Using POSIX realtime
./Bostomatic.hal:120: Pin 'hm2_5i25.0.7i77.0.0.input-00' was already linked to signal 'both-x'
1478
Stopping realtime threads
Unloading hal components
RTAPI_PCI: Unmapped 65536 bytes at 0x7fea57c9e000
Note: Using POSIX realtime

I think we need to slow down a second. The best analogy for what your missing is that your wires (hal wording) are not connecting to the correct things. Look at this example:

# --- BOTH-X ---
net both-x <= hm2_5i25.0.7i77.0.0.input-00

This would work functionally the same as:

net i-like-turtles <= hm2_5i25.0.7i77.0.0.input-00

The words after net are just a naming convention and anything can be used for that particular "wire". The parts after the i-like-turtles is what wires connect to. Right now you just have a loose wire with one side connected.

A better way to right connections that visually make sense is:
net both-x hm2_5i25.0.7i77.0.0.input-00 =>
joint.0.home-sw-in

This says that the wire called both-x connects the 7i77 in 00 to the motion control pin for x axis home switch. The below says the same exact thing but written a different way:

net both-x hm2_5i25.0.7i77.0.0.input-00

net both-x joint.0.home-sw-in

Does this make sense? Your physical pins need to be connected to motion control of Linuxcnc.
linuxcnc.org/docs/2.8/html/man/man9/motion.9.html#JOINT%20PINS

You also have this:
net both-home-x <= hm2_5i25.0.7i77.0.0.input-00
which means you have two instances of loose wires for the same input

So the above was just for a single x axis home switch. If you want the same pin to be used as a limit switch then you will need to connect the following:
joint.N.neg-lim-sw-in
and
joint.N.pos-lim-sw-in


Something like the following should make the same input function for negative limits, positive limits and homing switch also:
net both-x hm2_5i25.0.7i77.0.0.input-00

net both-x joint.0.home-sw-in

net both-x joint.0.neg-lim-sw-in

net both-x joint.0.pos-lim-sw-in

I am doing this from my phone and can't view some of the items I normally would but this should work.

Thank you for the continual input. I will give it a try and get back to you.

Hurray I have had some success thanks to your Help!
It will now Autohome XYZ successfully after adding your HAL entries and modifying the ini file a few times.
A and B are not homing correctly.
I keep getting joint following errors.
I can JOG B around with no joint following errors (although the scaling is wrong) but when homing it moves to the switch backs off about 25 degrees then give the joint following error
A-axis I can't jog at all because I can't figure out how to get the A jog buttons to appear in GMOCCAPY: forum.linuxcnc.org/gmoccapy/39723-edit-j...tons?start=10#208997
A-Axis moves fine when tested in PncConf

OK I have got rid of the Joint Following Errors
I still need to figure out how to get the rotary index's A and B to be scaled correctly.