Which kernel version is best for real time?

PCW wrote:

Do you have a Ethernet connected motion device? 
If so, the latency test is relatively useless for determining the actual
LinuxCNC latency.
A simple ping test is much more informative:
sudo chrt 99 ping -i .001 -q -c 60000 [Device_IP]
(will run 1 minute and print out timing statistics)
Where device _IP is the IP address of your Ethernet motion control interface.

PCW wrote:

Yes PCW, is the same Realtek with dkms driver for fix latency.
Maybe I'm asking the wrong question: is it really necessary to do the test with YouTube?

When you get an error, what does:

halcmd show param *.tmax

(typed in a terminal)

show?



 

langdons wrote:

Did ya set the governor to performance?

Try to remove unnecessary hardware.

blacklist kernel modules of unneeded devices.

Mask and disable unneeded services.

Ensure you have plenty of RAM; disk I/O should be avoided as much as possible.

Caching and buffering will reduce disk I/O and latency, but requires ample free RAM.

PCW wrote:

Warning: Spoiler!

When you get an error, what does: halcmd show param *.tmax (typed in a terminal) show? This will help determine where the fault lies

halcmd show param *.tmax
Parameters:
Owner   Type  Dir         Value  Name
    41  s32   RW          14985  encoder.capture-position.tmax
    41  s32   RW          19158  encoder.update-counters.tmax
    29  s32   RW          54482  motion-command-handler.tmax
    29  s32   RW         108007  motion-controller.tmax
    38  s32   RW          48125  nvmpg.update.tmax
    33  s32   RW       16640759  remora.read.tmax
    33  s32   RW          23424  remora.update-freq.tmax
    33  s32   RW       14829214  remora.write.tmax
    30  s32   RW       19134687  servo-thread.tmax