Watchdog has bit

The ping results are still quite bad

Here is what I would expect from a reasonably fast machine like yours:

64 bytes from 10.10.10.10: icmp_seq=605 ttl=64 time=0.083 ms
64 bytes from 10.10.10.10: icmp_seq=606 ttl=64 time=0.084 ms
64 bytes from 10.10.10.10: icmp_seq=607 ttl=64 time=0.080 ms
^C
--- 10.10.10.10 ping statistics ---
607 packets transmitted, 607 received, 0% packet loss, time 126033ms
rtt min/avg/max/mdev = 0.068/0.081/0.104/0.004 ms

( An old Core Duo E8500 with a Intel MAC )


I see the rx-usecs setting in your interfaces file but it might be good to verify
that its really set by:

sudo ethtool -C [your_ethernet_device-name] rx-usecs 0
and re-trying the ping

Also its really best to _not_ use the 192.168.1.121 IP address on the FPGA card if it overlaps your local NAT range, but rather use 10.10.10.10 instead

I use a straight RJ45 cable directly to the mesa board.

Made the ip change to 10.10.10.10 and seems to have better results but not great.
min/avg/max 0.150/0.166/0.251

The error still remains

I use a straight cable RJ45 directly to the mesa board.

I changed the ip to 10.10.10.10 and have better ping results but not great.
min/avg/max 0.150/0.166/0.251

The error still remains

What should I check?

Can you check the kernel log (via dmesg) and see if perhaps the link has dropped?
This would be an indication of a Ethernet problem on the host or a power issue at the 7I96.

Another thing to do is check the hal function tmax values to see where things are hanging.

To do this, run LinuxCNC, wait for the error and then run this command from a terminal window:

halcmd show param *tmax*

and paste the results here (note that these times are in CPU clock cycles,
so the CPU speed would be helpful to interpret the results)

I try to dmesg and couldn't show correctly the values.
Restarted and show this
Then I was able to see some changes, not so often occur the error watchdog has bit, these time after running a gcode file watchdog has bit. But it has longer periods.
the CPU speed is 3.1 GHz. the tmax in terminal

So you can see that the read-time is close to 10 ms which likely means that something
hung in the Ethernet hardware or driver. I suspect it may be an issue with the
Ethernet chip on your CPU. I would try a add-in Realtek or Intel Ethernet card as a
way of debugging this.

Also there is clearly a USB issue of some kind that needs to be fixed.

sharp_reaper, did you end up fixing this issue?

I am having the same issue.

Hi , I had the same issue and resolved it by tightening all the wires on the 7i96s and the motor drivers then the issue went away. I don’t  know which wire caused the issue.