Patrick: I'll test out the interface over the weekend. We're going to get grazed by Hurricane Earl, but then the weather's supposed to get very nice (i.e. *not* 35°C and humid!), and it's a holiday weekend here, so I may actually get a chance to go out to the mountains for some serious observing.
Cheers, Geoff --- In [email protected], Patrick Chevalley <p...@...> wrote: > > Geoff, > > The old CdC telescope plugins cannot work with Win64 (any version). > > For this reason I added the capability to connect directly to an ASCOM > driver. > You can now select ASCOM instead of "CdC plugin" from the System / Telescope > configuration (or right click the telescope button). This is working, even if > this window look unfinished :) > > The only problem at the moment is with the ASCOM telescope chooser, it not > work from a 64 bit application so the Select button only give an error > message. This will probably be fixed in a future ASCOM release. > I suggest using the POTH hub (it is set by default) and select the telescope > model from POTH after you click the Configure button. This must avoid any > problem with a specific driver not ready for 64 bit as POTH itself is a 32 > bit application. > > If you already configure your telescope with the 32bit version it must keep > the setting. So it is best to edit the file scope.ini in the user setting > directory and replace the driver name by POTH.Telescope (or delete the file). > > I tested this last week with Win7 x64 and the Celestron driver, all is > working fine. > > Also if you change from 32 to 64 bit do not forget to uninstall the 32bit > version first to avoid any mismatch between C:\Program Files(x86)\Ciel and > C:\Program Files\Ciel > > I will appreciate more testing with this 64 bit version. > > Patrick >
