I guess, in the end, we need to figure out why motion woudl be bad. Im thinking it is indeed CPU usage..
One proof of that is in the Darwin drivers config. If you make sure the port status screen is green
and press reset if its red, then use the jog box on the motors page the motion will tell you if the problem
is one of Mach4 or if its the computer itself vs Darwin. Theres a slider to select speed of the jog.
If the jog is smooth it means Darwins having no trouble at all, so if the motion is bad, it probably means Mach4 is
being too heavy on CPU. That doesntr mean it always will be. Ive seen several iterations of M4 where it uses a lot of cpu,
and version where it doesnt. M4 I think is a great many threads, it may take awhile to balance them all to keep
cpu usage down. I havent made m4 screens yet, can one remove the toolpath display? If the motion smooths with it
gone it will tell a tale I think...
Art