Mesa 5i25 and 7176 getting started

amhfabs wrote:

So, now I've got to figure out how to get these MPG counts to actually do something and change the position indicated in the DRO.... this could be fun!

What do you want them to do?

If you are using the Axis GUI you can use that to choose the jog increment by adding this to a HAL file:

net jog-inc axisui.jog.increment => axis.0.jog-scale axis.2.jog-scale

Then connect the mpg to each axis:

net x-jog hm2_5i25.0.7i76.0.0.enc0.count => axis.0.jog-counts
net z-jog hm2_5i25.0.7i76.0.0.enc1.count => axis.2.jog-counts

And assuming you want those jog wheels to always be active:

setp axis.0.wheel-jog-active 1
setp axis.2.wheel-jog-active 1

Of course there are literally several other ways to configure this. For example to use one wheel for all axes, with the axis chosen on the Axis GUI you would use
net x-jog-enable axisui.jog.x => axis.0.wheel-jog-active
net y-jog-enable axisui.jog.y => axis.1.wheel-jog-active
...
And net the same enc0.count pin to the jog-counts pin of every axis.

Things to note. The "signal" name after the "net" does not have any special meaning to the system. You can choose them freely. The pin names have to exist and do have special meanings to the system. You can see them all in Machine->show HAL config, or by opening a terminal and typing "halcmd show pin" when LinuxCNC is running.

amhfabs wrote:

I've got a 6 pos and a 4 pos selector switch ordered, the 6 pos for the "axis" selection and the 4 pos for increment when using X Y Z or A

OK, when the time comes you would wire the inputs relating to the axis selectors directly to the wheel-jog-enables and use a partially populated mux16 for the increment
(partially populated as mux16 has an output for every combination of the bit inputs). Unless you prefer to save pins and leave one position unconnected, the other taking 1 input high, the other a second bit and the fourth both bits high, and then you could use mux4