There's really no good way to diagnose this without seeing that conditions underwhich?this happened, the specific error message text, and looking at the logs
Generally speaking, the router is likely not going to be a bottleneck. I've run these routers for a couple years now, nearly every night, with everything connected together, running remote desktop, including stellarium (which is a hog) and i've never had communications?issues.?
On Sat, Jun 6, 2020 at 8:01 AM Arun Hegde <arun.k.hegde@...> wrote:
Last night, when I was imaging, I was using the method outlined in my previous thread - connecting both the imaging computer and the mount though a router. On occasion, the Gemini server would complain about "Communication error". My sense is that perhaps the router was not able to handle or properly queue the volume of data since I had also logged in from my laptop through the router to monitor and the commands from the ASCOM server to Gemini timed out.? But curious if anyone else has seen this? If my explanation is correct, the fix is to simply connect Gemini directly to the imaging box through USB which doesn't need the bandwidth of the router. It didn't affect my imaging - the bigger oops was me forgetting to connect the power cable of the dew shield to the controller. My heart skipped a beat as I discovered that this morning. Fortunately, the dew shield appears to have been effective.
