HI Guys:
I believe version 1917 fixes this for everyone, but I cant verify that as yet. Im using 1917 here with very smooth motion and CPU at nearly
zero%.
I think youll find the next posted version of Mach4 fixes all this, my understanding was its a program thread acting up. ( I think its a display thread
but I cant verify that.). Be patient till next version of M4 put out, since mine is 1917 I suspect the next one will be at least that for you. Thanks to
Freeman for that video, it made it quite clear to me whats happening. M4 is so bogging the CPU that the trajectory filling is working in spurts and
not outputting enough data to keep ahead of the step usage by the motors. When the CPU% drops, the output should be great.
The one thing I can tell you, is that if the motion is mooth in Darwin itself, then its very likely you will not have to upgrade hardware to make things
work. Could happen, but Im doubtfull youll have to. I suspect almost all of this is due to some code acting badly.
Thx for the testing.
Art