need help！ mesa 7i95 connection problem

Bit difficult with a multimeter but if you email the card serial number
to Mesa they can send a replacement card.

PCW wrote:

Bit difficult with a multimeter but if you email the card serial number
to Mesa they can send a replacement card.

Ok！ thank you very much!

You are a good man！

I am facing a very similar situation. (almost identical to the above descriptions)
I had some issue with the Linux installation to do apt-get, so today I tried to install the latest ISO image new.

Then the Mesa card was not giving any response at all.

I tried lots of different things. Now in my desperation I tried to ping the card from a windows computer and the 4 green LEDs on the 7i95 start with some life signs) aa ping. 192.168.1.121 gives me responses.

Verdict: Probably some mishap with the networkadapter on the NUC PC.

Any advise how to narrow down the Ethernet problem on the Linux installation?

I can also change the card to 10.10.10.10 and ping it from the Windows machine.
My assumptions

• 7i95 card seems not to be damaged
• 5 V power seems O.K.
• the patch cable is not causing the issue 

First thing I would do is setup the LinuxCNC host computer with a static IP address of say 10.10.10.100
 This is most reliably done by editing the interfaces file as described in the hm2_eth man page:

man hm2_eth

Then after rebooting (or setting the interface down and then up) verify that the host Ethernet device
is set to the 10.10.10.100 static IP address with:

ip a

Then set the FPGA card to a 10.10.10.10 IP address and cycle its power.

finally check that you can ping the card:

ping 10.10.10.10


 

This is mysterious. After I had success with the windows PC I tried another harddrive with a Windows in the linux computer. I could ping the card from windows.
So the Ethernet adapter seemed to work.

Now I re-installed the Linux hard drive and suddenly it worked again. I did the static IP address 10.10.10.1 and set the jumpers down/up.
Only idea I have now that the network adapter was in some weird state and that it was re-set after disconnecting the power and re-booting.

ping times are about 0.5 ms

Ping times of 0.5 ms are close to unusable

Do you have 

hardware-irq-coalesce-rx-usecs 0

in the interfaces file?

This is needed if you have a Intel Ethernet interface chip
 

i typed in "sudo apt-get install ethtool" in order to follow some things mentioned here

forum.linuxcnc.org/27-driver-boards/3868...rking-issues?start=0

Now if I type "sudo ethtool -c enp86s0"

I get a bunch of messages.
most items are marked n/a
rx-usecs: 0
tx-usecs: 0

I assume I switched off what you suggested.

The ping times went down from approx. 0.5 ms to 0.5 ms ?

"63 packets transmitted, 63 received, 0% packet loss, time 63476 ms
rtt min/avg/max/mdev = 0.185/0.455/0.577/0.05 ms"

I am not sure what the conclusion is.

p.s. that I get anything at all is a plus.  From all packets lost to 0% is progress.

Maybe you don't have a Intel MAC

lspci -nn | grep -i ethernet

Should list what you have.

Have you run a normal latency test?

 

Hello,

sudo lspci -nn|grep -i ethernet delivers:

"Ethernet controller [0200]: Intel Corporation Ethernet Controller I225-V [8086:15f3] {rev 03}"

further trials did not result in much other than: again 1:45 am

I tried another mini PC that I bought really cheap. Some difficulties to install from USB stick. I am not sure why it refused to install "uefi files" at first. (yet again I "fixed it" by random clicks on different options). The Ethernet adapter on this cheap Mini (it worked yesterday with the now deleted Windows 11) is a Motorcomm YT6801. This Ethernet adapter was not detected during installation. I tried to get it running using this instruction.
github.com/dante1613/Motorcomm-YT6801/bl...20-%20instruction.md
I have the feeling, that I messed the installation up quite a bit, not knowing what I am doing... .
The Motorcomm adaper showed (initial value for rx-usecs: 200), smallest value I could set with the ethtool (trying), was rx-usecs:3. The ping times seem to be influenced by that and went down from approx. below 0.5 ms to below 0.2 ms

Latency test in general I did not do these days.

Thank you for helping, so I am relieved that the 7i95 is still working.