Daughterboard inputs not recognized in HALMETER

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?

Im using ADMIN HALMETER from within Pathpilot itself. Also, ADMIN HALCMD SHOW does not ellicit a response in Pathpilot.

I couldnt get a response in Terminal with dmesg | grep 6i25. Am I doing that wrong?

I've attached my logfiles

Try dmesg | grep 5i25

Derp, it reports as a 5i25. Shoulda remembered

I see in your log you originally used the incorrect bit file and the last entry was the correct 5i25-7i76x2.bit
have you noticed any difference since that change?
the tormach bit file does not support the 7i76 so it would be suspected as a problem.

I'm at work and that was a quick look.
I wouild love to see linuxcnc and/or tomach to timestamp log file (pet peeve of mine)

Well yes, I swapped the bitfile for the 7i76 compatible one and am working on the .hal to use the inputs from the 7i76 instead of Tormach`s card. Where is the tormach timestamp logfile located?

Ideas anyone? Ive been poking around forever and cant get anything meaningful out of my inputs still

I would try LinuxCNC to verify the hardware
(and have access to known working tools)

Dubmfg wrote: Ideas anyone? Ive been poking around forever and cant get anything meaningful out of my inputs still

Which pin names are you looking at?

I do most of my card testing at the command line to reduce the variables.
Copy and paste this into the terminal.
Now you can add the input bits to the halshow "watch" tab and see what happens.