Brian,
Is your router and pc mounted on the OTA deck (moves with slews) or stationary ?
(I have my router velcro'd to the back of my Gemini-2 mini) and have not seen connectivity losses caused by slewing,
but rather I believe that some app's appear to perform lenghty ASCOM calls on the main UI thread. Some apps are better than others in this regard. I believe this coincides with the dropouts for me, likely that the UI thread appears to freeze and either RDP perceives this as trouble (a guess) or the UI thread is just unable to keep up and drops (another guess). A slightly similar (but 'significantly' different) condition test is used by the OS to determine when to display "... The application is not responding..." in the task manager.?
You can observe this condition by manipulating the app in question's ASCOM connectivity/functionality and observing if the UI 'freezes' while the ASCOM function is occurring. Some apps seem to have no effect in the UI Thread, others effectively 'lock up' the UI briefly while the activity is occurring. You may be surprised at the results. I can provide more information and specific reproducible examples if desired.?
Modern, well written programs really should not affect the UI thread at all, while these calls are occurring.
Consider what happens when an automation program is managing multiple other programs, each with their own ASCOM connectivity performing some of these tasks at near the same times...
Also, the RDP connection profile is just a text file with a paticular file name extension.
It is well documented, there are numerous additional parameters that may be useful. To see them, just use the "save as" in the RDP applet, then "open with" the file using fav text editor and customize...
Thanks,
Astronut Tim
