by cncdrive » Thu Jun 29, 2017 10:21 pm
If it happens with jogging then the things I can think of is that the computer is too weak for the UCCNC or an ethernet card problem,
however that it works OK with Mach3 crosses out the second idea about an ethernet card problem.
What are your computer properties? Especially interesting is the graphics card properties, because the UCCNC requires less computer resources than Mach3, except the graphics card,
because the UCCNC using hardware accelerated graphics with OpenGL, so it is adviced to have at least 256MByte graphics card memory (VRAM) which is the very minimum we advice, the recommended value is 512MByte which is still a low value for todays' cards but if the card is older than it may not have this much memory and then what happens is that the graphics images can't fit into the VRAM memory and so OpenGL starts copying the images continously between the RAM and the VRAM and it doing this frequently, because the screen update rate of the UCCNC is high, 30Hz. And this can cause issues for the application.
One thing you can check is the communication latency graph on the Profiles/statistics page, that graph should never touch the top which is 20msec latency, if it does is not good and is an indication that something is wrong with the computer.