Mesa 7i96 Installing to Run

The error is a real time issue on your host PC

There can be many causes so its best first to get some information:

1. What does uname -a report?
2. What servo thread period are you using?
3. What type of Ethernet hardware do you have?
if you dont know,
dmesg | grep -i eth
can help here
4. What kind of ping times do you get?
to test,
ping -c 5 10.10.10.10
then
sudo chrt 99 ping -i .001 -q -c 1000 10.10.10.10
(then post the stats of the second pin command here)
5. have you run a standard latency test? what were the results?

 

Ad.1
Linux bogicnc 6.1.0-12-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.52-1 (2023-09-07) x86_64 GNU/Linux

Ad.2
Servo thread period is set to 1 ms.

Ad.3

bogicnc@bogicnc:~$ sudo dmesg | grep -i eth
[sudo] password for bogicnc:
[    1.740898] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    1.740902] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    1.740904] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    1.740906] wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
[    1.896161] r8169 0000:08:00.0 eth0: RTL8168h/8111h, e8:6a:64:6d:8f:25, XID 541, IRQ 126
[    1.896166] r8169 0000:08:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[    1.963181] r8169 0000:08:00.0 enp8s0: renamed from eth0
[    2.563237] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle
[    2.600541] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/sw_method_init.bin
[    7.026581] usbcore: registered new interface driver cdc_ether
Ad.4a

bogicnc@bogicnc:~$ ping -c 5 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.247 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.109 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.136 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.130 ms

--- 10.10.10.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4098ms
rtt min/avg/max/mdev = 0.109/0.147/0.247/0.050 ms
Ad.4b

bogicnc@bogicnc:~$ sudo chrt 99 ping -i .001 -q -c 1000 10.10.10.10
[sudo] password for bogicnc:
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.052/0.065/0.114/0.007 ms
 
Ad.5
 

 

That all looks pretty decent other than the latency test, but that
would probably be better if run without the base thread.

Do you get a red light on the 7I96S when you get the "error finishing read" ?

Can you post the results of:

halcmd show param *.tmax

when LinuxCNC is running

(and also your CPU clock frequency as the tmax times are in CPU clocks on x86 hosts)
 

I've managed to install python3-packages and then mesaCT:
 
 

Yes, when i'm getting this error CR6 LED is turning red.

halcmd output:
 
 

Do you get a red light on the 7I96S when you get the "error finishing read" ?
 

I even changed servo thread period from 1ms to 2ms to see if it will help... Started Linuxcnc and now it took longer (more than one minute) to get en error, but it is still there:(

 

Yeah, so it sounds like a issue either with the MAC driver or the OS version.

I know there have been issues with the Realtek MACs but I am not sure what
the current fix is. It may be that updating the kernel to the latest will help
(ISTR that most Ethernet RT issues with older kernels that stated with the 5.x kernels
got fixed sometime around 6.3 )

Yes, i'm getting red light when error come on.

i feel it doesn't sound good to me...
Do i understand it right that the version i have installed has kernel 6.1?

Boogie wrote:

Yes, i'm getting red light when error come on.
 

I ask that because sometimes people have 5V power supply issues
which can cause random card resets, resulting in read errors.
If the card has been reset, the RED init (fault) light will be off, but if the
card has been  powered and loses communication, it will light the red LED
to indicate a watchdog timeout  fault