Mesa i76e error finishing read. Another Time with LinuxCNC 2.9.1

More
21 May 2024 23:07 #301125 by jimmyrig
If you have another hdd load 2.8.2 and see if that helps. I've got computers that run perfect on Debian 10 but have major latency issue on 12.

Please Log in or Create an account to join the conversation.

More
22 May 2024 10:46 #301144 by N3pu
Here is the output of the console:
cnc@LAMA704:~$ ping -i .2 -c 4 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.358 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.227 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.158 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.221 ms

--- 10.10.10.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 611ms
rtt min/avg/max/mdev = 0.158/0.241/0.358/0.072 m
cnc@LAMA704:~$ sudo chrt 99 ping -i .001 -q 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
8010977 packets transmitted, 8010977 received, 0% packet loss, time 8018997ms
rtt min/avg/max/mdev = 0.093/0.145/0.546/0.025 ms

But in this case the Spindle Drive is off and Axis-controler are in STO mode / Standby.

I still have my servothread set to 2ms.
In the .ini file there is P = 744.158356898348. Sometimes I read it should be adjustet?

Trying 2.8 Version could be possible. But the hdd is hard to access. Maybe it´s easyier to do an image of this version and reinstall 2.8.

Are there any options to see if it´s an EMI issue? Because I feel the errors are popping up more, when the spindle is on and changing speed etc.


 

Please Log in or Create an account to join the conversation.

More
22 May 2024 13:38 #301148 by PCW
To check for an EMI issue, you could monitor
hm2_7i76e.0.packet-error-total in the watch tab of
halshow to get an indication of how often packets
are dropped.

Also you might try pinning the Ethernet IRQ to the
last CPU (the one LinuxCNC uses for real time) 
This requires that you isolate the last CPU with
an isolcpus statement in your grub file
(isolcpus=3 for a 4 core CPU for example)
And then pinning the Ethernet IRQ to that CPU

 

Please Log in or Create an account to join the conversation.

Moderators: PCWjmelson
Time to create page: 0.074 seconds
Powered by Kunena Forum