I thought that the PREEMPT RT kernel patch was specifically written to overcome the problem of maintaining real time within a specific process and preempting any interruption of that process by other system tasks such as WiFi. It would seem to me that WiFi should not have an effect on LinuxCNC and, if it does, perhaps there's a way to use WiFi but specifically preventing LinuxCNC from using that as a means of connecting to any boards or motion controllers.
Since LinuxCNC can use Mesa cards, for example, I would think that WiFi might be included as a means of connecting those cards by default. There must be a way to prevent the LinuxCNC process from including WiFi among the possible means of connection and thereby avoid any jitter while still having WiFi available to other non-real time processes like web browsers and email.
I sure wish there was a GUI that would display all connections and processes for that matter, and allow enable/disable for choosing whether each of them should be real-time or not. It sure seems like the Unix gurus the world around despise GUI dependent dumb-dumbs like me!
