When I run 3D jobs, I keep running into a minor-but-annoying problem where it pops up a window saying it's lost contact with the wireless XHB mpg. Like several times per min. It doesn't interfere with the machine running, luckily.
The mpg didn't get moved, and this warning doesn't come up under normal 2D cuts. My theory is that the XHC driver is a userspace component and, if you demand enough intense tiny g-code vectors rapidly on the realtime threads, it gets too starved of cycles and times out. Could this be the case? Is there a good way to fix it? Danny ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
