Mesa 7i96s handwheel no motion

Hello guys, i just decide to come and try learning/using linuxcnc with mesa board and i need a little push to understand.
I have connect successfully the board with motors and try to use a handwheel as mpg to move x axis unsuccessfully 3 days now

I start with  Gmoccapy  as gui, linuxcnc 2.8 with debian (buster) and simple setup Mesa 7i96s with one motor on X and a handwheel conected to 7i96s encoder input.

I tried many HAL settings, from PPConf, custom HAL, i homed the AXIS but all the same result. At halshow the enable axis works, scale jog works, encoder shows changing but at  Gmoccapy  nothing change.

Can someone help/point me where to look for the problem??

One more small question, Mesa 7i96s can a input used as analog? For use with potentiometer.

Thanks a lot
Panos

I do not have experience with MPG yet, but I would look at connecting (net) the encoder pins to the HALUI pins in your .hal file.

A __very__ abstract example:

net [HMOT] (CARD0) .encoder.01.position => jog-x-pos

Good luck. Keep asking questions, people smarter than I should be along to help soon

Is the system homed?

(axis jogs dont work until homed)

Yes, always i try after i home all axis. I wonder, it shouldn't somehow tell to software (Gmoccapy) that i want to use mpg?

Did you look at all of LinuxCNC's mpg pins to see why you are not getting motion?

halcmd show all | grep jog

use halmeter to confirm:

axis.x.jog-scale is actually set to something besides 0
axis.x.jog-enable is actually set to 'true'
axis.x.jog-counts actually counts up and down when you spin the MPG

Let us know how that goes.

  I attach as txt what halcmd shows.

axis.x.jog-scale = 10 and change normal from input pin
axis.x.jog-enable = True and change normal from input pin
axis.x.jog-counts = 0 no changes..

ok so now you know it's something to do with the MPG.
Could be connected to wrong physical pins for the encoder number you want.
Again you can use halmeter to check all the Mesa encoder counter pins (hm2_7i96s.0.inm.00.enc0-count etc) to see if any count up and down with the MPG.

Could be physically wired wrong or something wrong with the MPG it's self.

Moved to "GmoccaPy" as it is not a driver board issue.