Mesa 7i96s with 5 encoders and Modbus

OK, standard not self "compiled" 7i96sd_pktv2.bin
and afforementioned relayboard.mod

still nothing

Not sure.

Hal file issues?
 Measurement issues?

Hal file issues ? Doubt it the compenent is loading and running (HAL Show config)

Measurement issues? Dito, attaching an oszi between ground and tx is not so a big deal.

5Volts with some ripples at 15kHz from the vfd

Just tested relayboard.mod with LinuxCNC 2.9.3
and 7I96S with 7i96sd_pktv2.bin and this hal/ini file set:

 

And it's working as expected (busy clicking away)

 

Nothing, njente, nada 5Volts

The encoder input on TB2 is not working either  -- that's what got me into implementing the other encoder inputs on P1 as seen in the .vhd

(output of mesaflash -read):
P1-01/DB25-01          34   IOPort       QCount           1        Quad-A          (In)
P1-02/DB25-14          35   IOPort       QCount           1        Quad-B          (In)
P1-03/DB25-02          36   IOPort       QCount           2        Quad-A          (In)
P1-04/DB25-15          37   IOPort       QCount           2        Quad-B          (In)
P1-05/DB25-03          38   IOPort       QCount           3        Quad-A          (In)
P1-06/DB25-16          39   IOPort       QCount           3        Quad-B          (In)
P1-07/DB25-04          40   IOPort       QCount           4        Quad-A          (In)
P1-08/DB25-17          41   IOPort       QCount           4        Quad-B          (In)
P1-09/DB25-05          42   IOPort       QCount           5        Quad-A          (In)
P1-11/DB25-06          43   IOPort       QCount           5        Quad-B          (In)

and as I was planning to use sserial for some other things I tried to implement an additional pktUart port on P1 as well

(mesaflash output):
P1-13/DB25-07          44   IOPort       PktUARTTX        0        TXData          (Out)
P1-15/DB25-08          45   IOPort       PktUARTRX        0        RXData          (In)

So let us assume that this part of the board emitted magic smoke.

I'm going to open a new topic to explore this possible workaround.

thx to PCW