hm2/hm2_7i92.0: Error finishing read!

Usually it is Joint 2, sometimes joint 1 or joint 0. I have to shut down the 7i72 card and restart linuxcnc.
The error is running a program, but sometimes I have gotten the error Error finishing read on 7i92 with no movement of the motors. What could this be due to?
I have a Mesa 7i72 board with a 7i76 connected to an orange PI5, The network cable is Cat6, the motors are Chinese servomotors connected as a direction step, I have executed several times the command:

sudo chrt 99 ping -i .001 -q 192.168.1.1 -c 50000

To see if packets are lost and the result is always 0% packets lost.

I have lowered the maximum speed of the engines in the ini file, I don't know what can happen. Any idea?

Angel

what is the result of running

 sudo chrt 99 ping -i .001 -q 192.168.1.121 -c 50000

(the times are important)

 

Change the default IP address with:
mesaflash --device 7I92T --addr 192.168.1.121 --set ip=10.10.10.100.

I have W5 down W6 up

The results are :
sudo chrt 99 ping -i .001 -q 10.10.10.100 -c 50000
PING 10.10.10.100 (10.10.10.100) 56(84) bytes of data.

--- 10.10.10.100 ping statistics ---
50000 packets transmitted, 50000 received, 0% packet loss, time 53160ms
rtt min/avg/max/mdev = 0.017/0.020/0.997/0.026 ms

sudo chrt 99 ping -i .001 -q 10.10.10.100 -c 50000
PING 10.10.10.100 (10.10.10.100) 56(84) bytes of data.

--- 10.10.10.100 ping statistics ---
50000 packets transmitted, 50000 received, 0% packet loss, time 52051ms
rtt min/avg/max/mdev = 0.016/0.019/1.238/0.026 ms

Pinging 10.10.10.100 means you are pinging your PC, not the 7I92
What you need is:

sudo chrt 99 ping -i .001 -q 10.10.10.10 -c 50000


What host hardware do you have?

Sorry for my ignorance, I don't understand network addresses.
Here are the results:

sudo chrt 99 ping -i .001 -q 10.10.10.10 -c 50000
[sudo] contraseña para angel:
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
50000 packets transmitted, 50000 received, 0% packet loss, time 50007ms
rtt min/avg/max/mdev = 0.161/0.163/0.462/0.002 ms
angel@orangepi5:~$ sudo chrt 99 ping -i .001 -q 10.10.10.10 -c 50000
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
50000 packets transmitted, 50000 received, 0% packet loss, time 50003ms
rtt min/avg/max/mdev = 0.161/0.163/1.240/0.005 ms
angel@orangepi5:~$ sudo chrt 99 ping -i .001 -q 10.10.10.10 -c 50000
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
50000 packets transmitted, 50000 received, 0% packet loss, time 50006ms
rtt min/avg/max/mdev = 0.161/0.163/0.215/0.001 ms



Thanks

0.161/0.163/1.240/0.005 ms

That's more that 1 ms so a reason for timeouts

You might try a 2 ms servo thread
(2000000 ns in the ini file)SERVO_PERIOD = 2000000