Homing pins for each axis

I have plenty of pins left over so I want to have one homing pin for each axis.
However having trouble getting AXIS happy with my wording.
I can home using pin 07 but as soon as I unblock more than one I get errors.
How should I phrase it to get them working?




# homing pins
#net x-home <= hm2_5i25.0.7i77.0.0.input-05
#net home-switch <= hm2_5i25.0.7i77.0.0.input-06
net home-switch <= hm2_5i25.0.7i77.0.0.input-07
#net home-switch <= hm2_5i25.0.7i77.0.0.input-08

net home-switch => axis.0.home-sw-in
net home-switch => axis.1.home-sw-in
net home-switch => axis.2.home-sw-in
net home-switch => axis.3.home-sw-in

# Use index, to home
net x-index-enable hm2_5i25.0.encoder.00.index-enable <=> axis.0.index-enable
net y-index-enable hm2_5i25.0.encoder.01.index-enable <=> axis.1.index-enable
net Z-index-enable hm2_5i25.0.encoder.02.index-enable <=> axis.2.index-enable
net a-index-enable hm2_5i25.0.encoder.03.index-enable <=> axis.3.index-enable

I have plenty of pins left over so I want to have one homing pin for each axis.
However having trouble getting AXIS happy with my wording.
I can home using pin 07 but as soon as I unblock more than one I get errors.
How should I phrase it to get them working?

The error message would have been helpful

You can only connect one OUT pin to a signal, so you need a different signal name for each axis for a start.

Have to guess that is the error.

regards

The error is:
It already has out pin.

The error was longer but nothing help full in the rest.

Am I the only one using separate pins and if not what signal names are people using?
If I am the only person using separate pins is it not recommended?

Thanks in advance.

As ArcEye said, you cannot connect multiple 'out' pins to one signal

In your previous hal code you had multiple sources (out pins)
driving a single signal. That is, you had pins hm2_5i25.0.7i77.0.0.input-06,
hm2_5i25.0.7i77.0.0.input-07, and hm2_5i25.0.7i77.0.0.input-08
all driving the signal 'home-switch'

This is a logical conflict. Linuxcnc detects this and aborts the startup.

That is, what value should 'home-switch' take when hm2_5i25.0.7i77.0.0.input-06,
hm2_5i25.0.7i77.0.0.input-07, and hm2_5i25.0.7i77.0.0.input-08 differ?

The solution is to use different signal names. For example:

# homing pins
net x-home-switch <= hm2_5i25.0.7i77.0.0.input-05
net y-home-switch <= hm2_5i25.0.7i77.0.0.input-06
net z-home-switch <= hm2_5i25.0.7i77.0.0.input-07
net a-home-switch <= hm2_5i25.0.7i77.0.0.input-08

net x-home-switch => axis.0.home-sw-in
net y-home-switch => axis.1.home-sw-in
net z-home-switch => axis.2.home-sw-in
net a-home-switch => axis.3.home-sw-in

should work

Note that the signal names are not important except as a guide to function and so:

# homing pins
net red <= hm2_5i25.0.7i77.0.0.input-05
net yellow <= hm2_5i25.0.7i77.0.0.input-06
net blue <= hm2_5i25.0.7i77.0.0.input-07
net green <= hm2_5i25.0.7i77.0.0.input-08

net red => axis.0.home-sw-in
net yellow => axis.1.home-sw-in
net blue => axis.2.home-sw-in
net green => axis.3.home-sw-in

should also work (but is less readable)

Fantastic!
All I can say is this Halloween I am having my wife sew up Superman suits for the grand kids with that goat picture replacing the giant "S".