Daughterboard inputs not recognized in HALMETER

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

I've measured +24v to the pin when the limit switch is triggered. Pin 1 on SB6 is also directly wired from +24V on the power supply plug to it, as an always on signal for this testing.

ok that's good, can you from a command prompt do a
dmesg | grep 6i25 and attach the output
also with pathpilot running in the MDI do a ADMIN HALCMD SHOW
then also attach your /home/operator/gcode/logfiles/pathpilotlog.txt

also, how are you running halmeter? are you starting it from within pathpilot with a ADMIN HALMETER?
please?