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)
 

I get command not found for some reason 

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

I started playing with the on_abort.ngc and it might work. I need to play a little more. At this point it does a little more than I want it to. It will trigger it for F2 (what I want), but also triggers it when exiting a running milling file with the escape key (not what I want) and the machine does not enter machine off.

The machine state I'm dealing with is particular about how it is entered and exited. I can't simply turn it on or off without the machine moving, when the M-code is active, it can be turned off without issue when the machine is not enabled (in machine off). So I only want the on_abort sequence to cancel my M-code state when the machine is aborting to machine off. Aborting to a machine on state, such as when aborting a running g-code file, the M-code state needs to be left alone, and the operator will have to clear it themselves (else the machine will shutdown with following error alarms.)

In the remap instructions I read about making some things conditional. I'm going to try to play with that now.

You can try this in your hal-file:

This reduces the acceleration of the axes when moving with the pendant.