Koike Aronson Plasma Conversion - sanity check on Mesa board selection?

I think my understanding of the encoder mapping was incorrect. I had it connected to the encoder plug on the 7i96s and couldn't get any readings off of it (I used a bench supply to simulate arc voltage). I switched it to the 7i77 encoder 2 and it works perfectly from there. Thanks for the assist!

Yes, to read the THCAD you need to:
1. Select the correct encoder
2. counter-mode for that encoder must be set to 1

For the rest to work the velocity pin of the selected encoder must be
connected to the appropriate qtplamac signal

I tried encoder 6 and 7 via hal configuration (thinking that this would map to the encoder port on the 7i96s) and they showed -22 for the voltage. However, when I changed the hal mapping (and moved the plug) over to 7i77 encoder 2 everything worked appropriately. What I'm not sure about is if the encoder port on the 7i96s is active at all in the 7i96s+7i77 configuration.

edit: @tommylight: That's interesting, I don't have this setup in my custom.hal at all, just in my normal one

It looks like there was an error in the firmware, sorry...
( A typo in the pinout file gave the 7I96S encoder (6)
2 A inputs instead of A and B )

Here is fixed firmware:

 

tommylight wrote:

Counter mode is set by PlasmaC/QtPlasmaC, so the only change required should be changing the encoder number.
And wiring ...
Edit,
To quick, encoder number must be changed also in the custom.hal file, i think that is where the encoder mode and some other stuff are.

Configs made with PNCconf  typically only have the debounce delays in custom.hal, almost everything else is in <machine_name>.hal

tommylight wrote:

Using PlasmaC or QtAxis PlasmaC or QtPlasmaC?

There is no QtAxis PlasmaC that I am aware of.

If you are meaning this one , it is based on AXIS like the old PlasmaC, it is not a Qt GUI.