Proximity Switches N/O On 7i77 with 5i25

PNP proximity switches work better with the 7i77 (which appears to be something that you have already realised)

You might be able to use the encoder inputs, but bear in mind that these are multiplexed (2 sets of ABZ pins for each 3 gpio pins on the 5i25) so it might not be as simple as it appears.

I believe that the normal advice for 7i77 and PNP proximity sensors is to pull the input pin up to the field power rail with a resistor (2k should be fine, so there is only 10mA flowing through the prox. Lower would give better noise immunity, depending on the current rating of the sensor) and then let the sensor pull that down to signal a change in state.

skyfab wrote:

however where do I comment that in the hal file?? a example hal limit

The HAL depends on which limit each sensor is. It is possible to wire many prox switches in parallel to share input pins, but your machine probably doesn't do that.

There are three HAL pins from the motion component per axis/joint.

axis.N.home−sw−in
axis.N.neg−lim−sw−in
axis.N.pos−lim−sw−in

These can be connected separately, all together or in combination.

For example
Or, equivalently, and in any order, anywhere in the HAL file
You seemed to hint that home and min-X were the same sensor, so you might have
the format of a net command is:
net signal-name pin-name (pin-name)
ie there has to be a signal name, then it is followed by on or more pin names. Only one pin name can be a writer-to-HAL
The signal names are something you choose yourself (they have no special meaning) but the pin names have to exist
each pin name can only exist in one net statement. To use a signal in more than one place re-use the signal name, not any pin names.
You can add => <= and <=> symbols to aid human readability, but they are ignored by the HAL parser.