Advanced Search

webbyguy wrote:

Should I try a pci graphics card instead of the Radeon HD4250 integrated graphics?  Any recommendations?

Yes, Matrox G200 or G450, but those are AGP, so very old.
You can try any older ATI/AMD you can find for 10-30$, but first check the motherboard if it has AGP or PCI-E slot.

Dang, that is some good latency!
Nice move changing PC's.

Well, I have installed the DKMS driver r8168 and repeated the ping test and histogram. Ping is a little slower but base thread in the histogram is way better than before!

Here is my ip a and test of r8168:
hanno@Linuxcnc-1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:1b brd ff:ff:ff:ff:ff:ff
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute enp2s0
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:55:94:28 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.178.22/24 brd 192.168.178.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
hanno@Linuxcnc-1:~$ lsmod | grep r8168
r8168 581632 0

What do you think about it?

Kind regards and thank you for your support!
Hanno

Here my photos:
 

 

 

Can you post your hal/ini files?
 

I have no output to my drives, i 'm not sure why?

If you have both Intel and Realtek MACs available, I would choose the Intel device for realtime.
 (especially if there are issues installing the DKMS Realtek driver)
 

Still the same..

ok, ill give that a try

A 1 deadzone and 1 ferror limit pretty much guarantees a following error.

I would set the deadzone to 0 for setup and tuning.

So I increased dead band to 1 and following error to 1 and still get the same results. I used my power supply to run the drives and they work perfectly when I force a +/- voltage.

Hello PCW, tommylight,
Yes, I have switched to the optional Realtec Network Controller, because with the Intel i got triple as bad pings as with the Realtec when using it for the Mesa Card. (The Intel is very unstable indeed, Internet sometimes connects only with fixed IP, sometimes only with DHCP, that has cost me nerves the last weeks)

hanno@Linuxcnc-1:~$ lspci  | grep -i ether
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
I try to find the DKMS driver, if you say this could help.
(oops, trying to load DKMS, I see "dkms ist schon die neueste Version (3.0.10-8+deb12u1)." But I can install/write the driver with r8168 new. I wait until I have done all the steps for that driver.

tommylight: ip a gives back:
hanno@Linuxcnc-1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0a:cd:00:00:1b brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute enp2s0
       valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:23:24:55:94:28 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
    inet 192.168.178.22/24 brd 192.168.178.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever

What does that mean in relation to my pings?

Thanks for your support!
Hanno


 

What would be a good base number to enter for the dead band and following error?

Thank you Tommy,
You were right that that was the PATA setting in the bios.  I changed it to AHCI, and now that interrupt is no longer on the list anymore. 
 
Unfortunately, it doesn't appear that was the cause of my jitter.

Now the only things causing interrupts are
18 - Radeon HD 4250 internal graphics
LOC - (Local timer interrupts)
RES (Rescheduling Interrupts)

Is there anyway to see what causes the RES and LOC timer interrupts to see if the jitter is caused by one of those?

Sometimes 19 also happens, but it doesn't seem to sync up with times that the jitter has variance.

For some reason the nosmt=force setting in the kernal boot parameters doesn't seem to work anymore with the rtai kernel.  Should nosmt still work in the rtai kernel?

I have the following settings in:
ro quiet skew_tick=1 nosmt=force mitigations=auto,nosmt irqaffinity=0-1 kthread_cpus=0-1 rcu_nocb_poll rcu_nocbs=2-7 nohz=on nohz_full=2-7 isolcpus=2-7 intel_pstate=disable idle=poll cpufreq.off=1 intel_idle.max_cstate=0 amd_idle.max_cstate=0 processor.max_cstate=0 nowatchdog nosoftlockup acpi_irq_nobalance noirqbalance

I'm also using the irq affinity script from:  forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity

Should I try a pci graphics card instead of the Radeon HD4250 integrated graphics?  Any recommendations?

That fixed it.

Now I need to add a section to match the pocket to the tool when putting away the tool.

Update:
The machines works again, without unexpected real time delay and a very good latency, but i had to take the PC of my Lathe. (the lathe machine uses the Mesa 7i76e card)
That PC has a on-board graphic card, but i first tested it with the VGA that was already there and i got the same latency issues. As soon as i used the on-board vga, the latency was perfect and no "realtime errors" at start up.

I have started latency-histogram, with 4 x glxgears and a youtube video running for about 1 hour.
I first started the histogram, then opened one glxgears and waited to check if anything spikes happen. Then i opened 3 more glxgears. No latency spike. Then the youtube video and the pc was running like that for almost one hour without any change to the base thread.
On tomorrow i will run a milling program and check if anything bad happens.

Also i will connect that "latency issue PC" to the Lathe and hope there will be no problems, but i think with the Mesa card there shouldnt be any.