[Crossle86]

Yes, exactly! We saw this problem in January and closing and reopening the DS seemed to clear it up but the last few times we have hit this problem closing and reopening DS has not fixed it. We have gone to falling back to Windows and disconnect the router and reconnect. And we had the one case yesterday where that did not work and another robot power cycle was needed. That last case suggests the problem is between the PC and the router as Windows said it could not connect. But, we have also seen cases where the DS won't reconnect but the development PCs do. There seem to be multiple scenarios where there are reconnection problems.

I'm going to go out on a limb and state that we have not seen a case where the bot has been off for an extended time and then we start it up for testing and there is a "initial" connection failure. It only seems to happen after we have been connected and then power cycle the bot.