Comm errors are caused by the control PC becoming busy with some task that is taking too long to complete. When communication with the bot is interrupted for too long of time a comm error occurs.
Things that can do this are fast-search options, automatic software updates, etc. These things watch mouse and keyboard activity and determine that the computer "isnt busy" so they suddenly spring to life and start running. About the time the cut job is half way through. Then disaster..
The way to fix these, is to get rid of all necessary processes. Look at the startup menu folder for unnecessary programs and "helpful features" like toolbar and launch monitors. Then check the registry for auto run programs and be sure they are all really needed. (Turn off one at a time so you know what to restore if the computer really needed the setting.)
Lastly look at "services" under the Control Panel:Administrative Tools:Services. Most of these have been carefully named things that obscure their purpose. So look each name up on the internet and find out if it is essential, if not, try making it "manual", or "disabled". Once again do one and wait. Then do the next one the next day. Slowly the problem will go away, and your computer will have all this time available that was eaten by these hidden time hogs. Most of which are there for the benefit of others, not the user.
And a useful tool, download "process explorer" from "procexp.exe" from Microsoft, its a free download. Run it in the background where you can see it while the bot is running. It logs everything that starts and takes CPU time. You may be able to identify the culprit directly with that tool.
Grounds are extremely unlikely to be the problem. If the problem appears to go away "fixing the ground" gets the credit, when the process that took the time stopped running for some other reason.
Hope that helps-
D
"The best thing about building something new is either you succeed or learn something. Its a win-win situation."
--Greg Westbrook