mesaboard 7i76e + 7i85s + 7i85 with ssi for absolute encoder bitfile

Yes, that format string specifies 2 bits of data (not sure what it is)
followed by 12 bits of encoder data.

Do you have the encoder data sheet?

Hello I pass you the data sheet of encoder and the chip of the encoder.
Thanks.
 

This is the data sheet of the chip from page 1_12 because the all sheet exceed.
The info for ssi is there.
Thanks again.

Hello again.
I have done to work the encoder in the 7i85s without problems, but in the 7i76e the encoder do not stop to jump. I have read the pins with a tester and in the 7i85s the clock pairs give me 5 volt I imagine because they are high to begin and the data pins give near 0 volts.
But in the 7i76e the pairs of the clock they are jumping, jingleing, or osclitating between - and + volts, very quick. Maibe is this the problem.
In the hal show, the pins of rawcount are continualy movimg.
I have changed the pairs, a lot of combinations but none of them worked.
Maybe something in the bitfile?
Maybe in future I will buy a 7i85 to combine with 7i76e + 7i85s if I can not do to work the sistem with rs422 of the 7i76e.
Some suggestion?
Thanks a lot.

Yes, I think there was an error in the bitfile (wrong enable polarity for the RS-485
interface on the 7I76E) so the CLK output is floated. This should be a correct bitfile:

 

 

Hello I have verify the bitfile with mesaflash and give me this result in the terminal.

usuario@debian:~/Descargas/7i76e_7i76x1_7i85sx1_ssid_2022-03-22$ mesaflash --device 7i76e --addr 10.10.10.10 --verify 7i76e_7i76x1_7i85sx1_ssid.bit
Checking file... OK
File type: BIT file
Boot sector OK
Verifying EEPROM sectors starting from 0x100000...
|VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
Error at 0x1493BB expected: 0x0 but read: 0x5

Do I have to write this bitfile?

Thanks again.

Yes, its a different (and hopefully fixed) bitfile.

But one question.
The new bitfile when I verify with mesaflash give me an error. The doubt I have is if I can write this bitfile to fpga without problems?

I would expect it to get an error if you have not written it yet because
--verify is comparing the old bitfile in the flash chip with the new bitfile

Ok I understand.
Tomorrow I will write the new bitfile.
Thanks a lot.