View Single Post
  #6  
Old 30-01-2018, 09:27 AM
gaseous's Avatar
gaseous (Patrick)
Registered User

gaseous is offline
 
Join Date: May 2016
Location: Brisbane
Posts: 837
Quote:
Originally Posted by astroturf View Post
thanks Pat and Dave
its starting to look like w10 is the culprit
I have tried different versions of ascom drivers for my scope and different r232 adapters to no avail

its really annoying to know that it worked wonderfully on my old clunker (laptop) with windows xp

I'm a bit challenged as far as altering things on w10 goes, so i'll just have to go with it, & look at books when I want to find something via the handset

cheers
Bryan
Hi Bryan, my setup is different to yours (goto dob), and before the recent purchase of a Wifi adapter I'd never used any ASCOM drivers, but the most recent version that I've seemed to get working is 6.3. I believe there were other peripheral things I needed to download as well, which you should be prompted for on the ASCOM site. You might also need to make sure your W10 has all the recent updates - I found the latest version of Stellarium has some sort of MS Visual C++ error (whatever that is), before I updated Windows for the first time in ages. I could do up a list of the steps I've taken to get my scope to connect wirelessly to my laptop via Synscan Pro (the wifi adapter app)/StellariumScope/Stellarium if you like, but I'm not sure how much would be applicable to an EQ mount. It's a trial and error process and I've only done it inside (without star alignment), but I can control the scope via Stellarium wirelessly at least.
Reply With Quote