mesaflash does not detect 7i92TF

Hi, I have recently purchased a 7i92TF card, I received it yesterday, and today I have started to configure it, but it does not work, I do not know what I am doing wrong, but it does not recognize the card.

The configuration I have in IPv4:

Address: 192.168.1.121 (it is by default, I haven't moved the jumper).
Network mask: 8
Gateway: 10.10.10.10

It seems that there is communication between the PC and the card.
I ping 192.168.1.121
And it ret:

PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from 192.168.1.121: icmp_seq=2 ttl=64 time=0.043 ms
64 bytes from 192.1

68.1.121: icmp_seq=3 ttl=64 time=0.045 ms
64 bytes from 192.168.1.121: icmp_seq=4 ttl=64 time=0.045 ms
64 bytes from 192.168.1.121: icmp_seq=5 ttl=64 time=0.046 ms
64 bytes from 192.168.1.121: icmp_seq=6 ttl=64 time=0.045 ms
64 bytes from 192.168.1.121: icmp_seq=7 ttl=64 time=0.046 ms
64 bytes from 192.168.1.121: icmp_seq=8 ttl=64 time=0.045 ms
64 bytes from 192.168.1.121: icmp_seq=9 ttl=64 time=0.046 ms
^C
--- 192.168.1.121 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8085ms
rtt min/avg/max/mdev = 0.043/0.044/0.046/0.001 ms

When I run in the terminal:
mesaflash --device=ETHER --addr 192.168.1.121 --readhmid
the response is:
No ETHER board found

mesaflash --device=7i92t --addr 192.168.1.121  --readhmid
No 7i92T board found

I have upgraded to version 3.5 of mesaflash from Gihub.
Mesaflash version 3.5.5
 

It looks to me like you have the host IP address set to 192.168.1.121
so the ping is actually pinging the host PC

The host needs to be set to an address that's different but in the
same range and the 7I92TF say 192.168.1.200

And actually for LinuxCNC operation its better to set the host address
to say 10.10.10.100 and the 7I92TF card to 10.10.10.10

If the IP address of the Mesa board is 192.168.1.121 the IP address of your computer can not be 192.168.1.121 it must be 192.168.1.xxx with xxx being less than 255 but not 121.
There is no need for a gateway as that interface will only be connected directly to the Mesa card.

I have changed the address of the host to 192,168.1.200 I have done ping 192.168.1.121 The result: PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=1 ttl=64 time=0.151 ms
64 bytes from 192.168.1.121: icmp_seq=2 ttl=64 time=0.099 ms
64 bytes from 192.168.1.121: icmp_seq=3 ttl=64 time=0.090 ms
64 bytes from 192.168.1.121: icmp_seq=4 ttl=64 time=0.100 ms
64 bytes from 192.168.1.121: icmp_seq=5 ttl=64 time=0.103 ms
64 bytes from 192.168.1.121: icmp_seq=6 ttl=64 time=0.109 ms
64 bytes from 192.168.1.121: icmp_seq=7 ttl=64 time=0.114 ms
64 bytes from 192.168.1.121: icmp_seq=8 ttl=64 time=0.105 ms
From 192.168.1.200 icmp_seq=9 Destination Host Unreachable
From 192.168.1.200 icmp_seq=10 Destination Host Unreachable
From 192.168.1.200 icmp_seq=11 Destination Host Unreachable
64 bytes from 192.168.1.121: icmp_seq=12 ttl=64 time=0.158 ms
64 bytes from 192.168.1.121: icmp_seq=13 ttl=64 time=0.105 ms
64 bytes from 192.168.1.121: icmp_seq=14 ttl=64 time=0.104 ms
64 bytes from 192.168.1.121: icmp_seq=15 ttl=64 time=0.105 ms
From 192.168.1.200 icmp_seq=16 Destination Host Unreachable
From 192.168.1.200 icmp_seq=17 Destination Host Unreachable
From 192.168.1.200 icmp_seq=18 Destination Host Unreachable
64 bytes from 192.168.1.121: icmp_seq=19 ttl=64 time=0.200 ms
64 bytes from 192.168.1.121: icmp_seq=20 ttl=64 time=0.105 ms
64 bytes from 192.168.1.121: icmp_seq=21 ttl=64 time=0.107 ms
From 192.168.1.200 icmp_seq=22 Destination Host Unreachable
From 192.168.1.200 icmp_seq=23 Destination Host Unreachable
From 192.168.1.200 icmp_seq=24 Destination Host Unreachable
64 bytes from 192.168.1.121: icmp_seq=25 ttl=64 time=1024 ms
64 bytes from 192.168.1.121: icmp_seq=26 ttl=64 time=0.098 ms
64 bytes from 192.168.1.121: icmp_seq=27 ttl=64 time=0.139 ms
64 bytes from 192.168.1.121: icmp_seq=28 ttl=64 time=0.100 ms
From 192.168.1.200 icmp_seq=29 Destination Host Unreachable
From 192.168.1.200 icmp_seq=30 Destination Host Unreachable
From 192.168.1.200 icmp_seq=31 Destination Host Unreachable
64 bytes from 192.168.1.121: icmp_seq=32 ttl=64 time=0.159 ms
64 bytes from 192.168.1.121: icmp_seq=33 ttl=64 time=0.090 ms
64 bytes from 192.168.1.121: icmp_seq=34 ttl=64 time=0.085 ms
From 192.168.1.200 icmp_seq=35 Destination Host Unreachable
From 192.168.1.200 icmp_seq=36 Destination Host Unreachable
From 192.168.1.200 icmp_seq=37 Destination Host Unreachable
64 bytes from 192.168.1.121: icmp_seq=38 ttl=64 time=0.153 ms
64 bytes from 192.168.1.121: icmp_seq=39 ttl=64 time=0.107 ms
64 bytes from 192.168.1.121: icmp_seq=40 ttl=64 time=0.107 ms
^C
--- 192.168.1.121 ping statistics ---
41 packets transmitted, 25 received, +15 errors, 39.0244% packet loss, time 40945ms
rtt min/avg/max/mdev = 0.085/41.078/1024.165/200.671 ms, pipe 4

As there are errors:  Destination Host Unreachable

I turned off and turned on again and now the CR7 LED in red the CR8 yellow LEDs, now the PC does not detect any network

My guess would be that you have a 5V power supply issue

Thank you very much for your help and sorry for being so tiresome and so clumsy.

I have replaced the 5V power supply with another one and now it seems to work fine.

The ping result
120 packets transmitted, 120 received, 0% packet loss, time 121743ms
rtt min/avg/max/mdev = 0.064/0.094/0.156/0.018 ms

No packet loss anymore, are those good numbers?

with mesaflash --addr 192.168.1.121 --device=7i92t --readhmid
Now it detects the card.


According to PCW's answer
And actually for LinuxCNC operation its better to set the host address
to say 10.10.10.100 and the 7I92TF card to 10.10.10.10.10

Do I have to change the jumpers of W5 and W6 ?

I have to connect to a 7i76.
 Do I have to flash the 7i92T, the correct file is 7i92t_7i76x2d.bin?
 

You need to move W6 up (and a power cycle) to get the 10.10.10.10 IP address
and yes, you need 7i92t_7i76x2d.bin firmware to interface to a 7I76

mesaflash --device 7i92t --addr 10.10.10.10 --write 7i92t_7i76x2d.bin --reload
 

After configuring the 7i92TH when I connect the 7i76 daughter card it does not create the pins of the 7i76.
The 7i76 card is with the jumpers as it comes by default.
(This is the way it was with the 5i25 I had).
I have changed in the hal file that I had working all the inputs that referenced the old 5i25 to hm2_7i92.0.
It seems to create the pins of the 7i92 card, but it gives error in the first entry of the hal file that refers to the 7i76 card.

I have tried halrun and it creates the pins of the 7i92 but the 7i76 card does not appear, the DB25 cable is the one I had before about 3 meters shielded and 1 to 1 cables, is not a cheap printer cable.

I have also tried with Pncconfig but when I get to the option to test the motors the motor does not move it does nothing.
There seems to be no communication between the 7i92 board and the 7i62 daughter board.

Some idea that I could be doing wrong.
 

Does the 7I76 have both 5V power and Field power?

(5V power arrangement depends on 7I76 W2 position and 7I92TF W4 position)

Please read "CABLE 5V POWER" section of 7I76 manual

After configuring the 7i92TF card (Thanks to PCW for his help and patience) I don't get pwmgens.
I burned the firmware with: mesaflash --device 7i92t --addr 10.10.10.10 --write 7i92t_7i76x2d.bin --reload

In the hal file I have it like this:
loadrt hostmot2
loadrt hm2_eth board_ip="10.10.10.10.10" config="num_encoders=1 num_pwmgens=1 num_stepgens=4 sserial_port_0=20xxxx"

The encoder, stepgens and serial port are there but pwmgens is not.

Do I need a different firmware?
Is it well declared in the hal file?