Daughterboard inputs not recognized in HALMETER

Hello everyone, me again.

Long story short, I fried my old Pathpilot setup (much to my horror) and have rebuilt it now with a 6i25 and 7i76 combo. It seems I didn't back up the most recent (working) version of my files before it got... crispy.

Needless to say, I'm back to a similar issue to the one I experienced previously, and would love to hear your thoughts. I've successfully been able to jog my axis around with the attached .HAL configuration (for a short while anyway), but I cannot get my limit switches to be read. When monitoring them in HALMETER I don't see any changes, and I've verified that the signal is getting all the way to the pins (TB6 1, 2, and 3 for x, y and z). I'm running 5V power through the DB25 cable and 24V Vfield. Both CR1 and CR2 LED's are illuminated on the 7i76.

Is there some reason that serial communication would not be functioning between the 7i76 and the 6i25?

If the xxxx.7i76.xxxx pins are there, sserial communication is working at least to start
No idea what the hm2 driver version is or whether it reports errors in the Pathpilot GUI
(if the 7I76 pins where there and you lost communication, under LinuxCNC you would have a major
splat of error reports)

Yes, the pins are there but unresponsive when manually triggered and viewed through HALMETER. Its the strangest thing.

can you post the states of:

hm2_5i25.0.sserial.port-0.run
hm2_5i25.0.sserial.port-0.fault-count

Does Pathpilots halmeter work properly? That is does is reflect other signals changing dynamically?

hm2_5i25.0.sserial.port-0.run TRUE
hm2_5i25.0.sserial.port-0.fault-count 0 (0x00000000)

I'm unable to change the pin state and see it in HALMETER, either physically or with setp from within my .HAL file (throws pin not writable error).

OK so it seems like the sserial interface is running

You should not be able to change an input pin state since its of type=out (it drives pins of type in in hal)

does PathPlots halmeter work on other changing pins? (that is, is it updated dynamically?)

I do believe it is updated dynamically if I remember correctly, but I'm not able to see changes to pins at the moment of course

The way to check is to look at some pin that does change (say a position pin when in motion)

So by forcing debounce.0.0.in to 1 I'm able to force the machine into Machine.ok TRUE.

I can't however monitor the pins while jogging the axis to see if they change dynamically in Halmeter or Halscope, as they go to the background as soon as I try to change screens in pathpilot.

Quick question as I don't see it asked
the input on the 7i76 is sinking inputs which means you must supply a positive voltage to them so that a value greater than 50% of the field power is applied to be read. If have a limit switch, one side goes to the field power the other side goes to the input pin.

Want to be sure we're not looking at a hardware issue as this would explain the behavior your seeing.

if you put one end to ground instead and the other to the input it would never see a change in state to register the switch being tripped.

hopefully it's that simple