Where are Mesa 7i76e physical pins configured?

I found the wonderful connection guide that shows the pin names like `hm2_7i76e.0.7i76.0.0.input-05`, but I can't figure out where in the `.hal` file I'd put a line including that to configure it as a limit switch. The pin names generated by PnCConf seem to be higher-level than that:

net max-x => axis.0.pos-lim-sw-in

Where is `axis.0.pos-lim-sw-in` defined?

When I tried to do this:

net max-x <= hm2_7i76e.0.7i76.0.0.input-05
net max-x => axis.0.pos-lim-sw-in

LinuxCNC complains that `axis.0.pos-lim-sw-in ` is already defined. That implies to me that `axis.0.pos-lim-sw-in` and `hm2_7i76e.0.7i76.0.0.input-05` are synonyms for the same pin, but where is that defined?

Sorry for the basic question, still figuring this out.

pncconf does not create pin names, pin names come from LinuxCNCs components

For example:
axis.0.pos-lim-sw-in
is a pin created by LinuxCNCs motion component
(man motion for a list of all of motions pins)

and
hm2_7i76e.0.7i76.0.0.input-05
is a pin created by the hostmot2 hardware driver component

pncconf does create signals ( with the net command ) that link pins from
component to component. ( the created signal is "max-x" in your example )

In fact one of the main purposes of the hal file is to create these connections

It can be a bit confusing at the start. The first thing you need to understand is the net command. Have a short read of that here...
linuxcnc.org/docs/2.7/html/hal/basic-hal.html#_net

In your ini file in the [HAL] section you can see what hal files are being loaded and in what order. The axis.0.pos-lim-sw-in is a signal so you can't assign a signal to a pin.

Assuming your using the 2.7 version of LinuxCNC the pin names for limit switches are axis.N.neg−lim−sw−in and axis.N.pos−lim−sw−in where N is the axis number. The motion pin names are here...
linuxcnc.org/docs/2.7/html/man/man9/motion.9.html

It might be easier to use my 7i76e configuration tool as it is just for that card only.
jethornton.github.io/7i76e/

JT

JetForMe wrote: I found the wonderful connection guide that shows the pin names like `hm2_7i76e.0.7i76.0.0.input-05`, but I can't figure out where in the `.hal` file I'd put a line including that to configure it as a limit switch. The pin names generated by PnCConf seem to be higher-level than that:

net max-x => axis.0.pos-lim-sw-in

Where is `axis.0.pos-lim-sw-in` defined?

When I tried to do this:

net max-x <= hm2_7i76e.0.7i76.0.0.input-05
net max-x => axis.0.pos-lim-sw-in

LinuxCNC complains that `axis.0.pos-lim-sw-in ` is already defined. That implies to me that `axis.0.pos-lim-sw-in` and `hm2_7i76e.0.7i76.0.0.input-05` are synonyms for the same pin, but where is that defined?

Sorry for the basic question, still figuring this out.

This is one of mine, but this is on 2.8

net x-home-sw => joint.0.home-sw-in
net x-home-sw => hm2_5i25.0.7i70.1.0.input-45-not

Are you on 2.8? IF so use joints.

post your hal file..... Then we can see whats going on.

it woudt be a great Help for the people here
if you upload your HAL and INI
so we can understand better what is going on

YOU can get a look on the alredy connecte pins
with MASHINE Menue Halshow
if you are on AXIS

Do you recommend using 2.8? I can upgrade to that if so.

I use 2.8 on 2 of my 3 CNC machines just because I've not gotten around to creating my lathe GUI in QtPyVCP and I'm still polishing up my plasma GUI.

JT

My long-term goal is to run Tormach's PathPilot on this machine, once I get it figured out. I might have to stick to 2.7 to make that easier, we'll see. (I have two other Tormach machines, and I like the interface.)

JT,

Does your config tool require X to run? Can it run on macOS? I tried installing it but skipped the bit about .xsessionrc. When I run I get:

I do have python installed at that location.

Do you know what PathPilot is based on? I have a feeling that it is a hybrid of LinuCNC 2.7 and Machinekit, in which case you probably don't want to go to 2.8 because the HAL and INI are significantly different. (in content rather than in format)

I would wait until / if PP moves to 2.8 before making the switch. Unless you have a gantry machine in which case I think I would suggest 2.8 and _not_ PathPilot.