Advanced Search

not sure if that is in a linuxcnc update thing or not, i would ask in the general chat maybe. i can confirm in 2.9.3 here shift key does not change the jog speed. so i'm not certain where the disconnect occurred. from some quick research it appears gmoccapy used the shift key to double the default linear velocity setting, but i do not see in linuxcnc where this is a standard and I know i never wrote that functionality into probe basic. in probe basic the only control over the jog speed that is built into the ui is the jog slider.

Latency is basically unimportant with Mesa hardware _if_  you never get timeouts

Also the latency test does not test network latency which is more important for
Ethernet connected cards.

To check network latency:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10
(will run for ~ 1 minute and print stats)

Assuming the Ethernet card is set for 10.10.10.10

Things that improve network latency:

isolcpus to last CPU, and pinning the Ethernet IRQ to the last CPU

disabling power management, disabling Intel AMT
 

Mon24 13:59: hm2/hm2_7i76e.0: Watchdog has bit! (set the .has-bit pin to False to resume)

Indicates relatively huge network latency (>5 ms if the watchdog setting is the default 5 ms)
That sounds like maybe a power management issue so you might try adding pcie_aspm=off
in your kernel command line.

What is the current kernel command line?
 (cat /proc/cmdline)