Advanced Search

type: sudo ethtool --set-eee eno1 eee off

this will be lost on boot so to make it permanent
type
sudo grub-customizer
open the second tab and on the line it says quiet, add: igb.EEE=0
save and reboot. 
check eee is off again with ethtool

With energy efficient Ethernet enabled, sometimes your NIC has a holiday which is not good for latency

Also type man hm2_eth and follow the instructions so disable coalescing if you have not done that yet on your 10.10.10.1 NIC

Very nice
Set BASE_PERIOD to 5000. spindle_at_speed works correctly.
Thanks for help !

sudo ethtool works 

I have several motor controllers that are driven by differential signals (CLK, #CLK, DIR, #DIR) – the inputs (5V, Ri = 120 Ohm) are not optically isolated. At first glance, it seems that controlling it with my Mesa 7i76EU works perfectly.

For testing purposes, I'd like to use the parallel port or possibly a RP2040 – in addition, I have a "Benezan Mini Breakout Board" left over from a previous setup that I could use.
It would be great if there were a solution for this.

probably needs sudo ethtool

I installed ethtool and I am still getting command not found 

I did a video recently about this

isolate the last core with isolcpus
Disable coalescing if intel
Use dkms driver if realtek
Set CPU affinity for NIC interrupt to be same as the isolated core

Yes, the network is not setup properly (no fixed IP address)
 

sudo apt install ethtool
-
And the network is not set up properly or not connected???

I get command not found for some reason 

We would need more info about what you want to do and what you already did.

Really nice and very useful debug tool. Thanks for sharing! I think this should be shipped with linuxcnc. What do you think?

Only a little note to the selection behaviour - when I click on several components after each other, and when I hold down on the last one and drag, all the previous clicked components are in the selection and are moved together. I think it would be more intuitive to do that with Ctrl click.

The BASE_PERIOD in the sim config is too low for that spindle speed so the sim_encoder component cannot calculate the speed correctly.
Setting a lower BASE_PERIOD in the gmoccapy.ini increases the possible maximum spindle speed
 

Yes with adding the conditional code from the manual seems to be working just the way I want it to.
Here is what I have in the on_abort.ngc file