If you've asked a question, please remember to mark the best answer as 'accepted' by clicking the check mark next to your preferred answer. It looks like the checkmark to the left, and is right under the vote section. You'll gain some reputation and it helps us surface the best content.
1

Hi, I am trying to use The Sky 6 with ASCOM to control a Celestron Nexstar11GPS.

I have downloaded and installed the ASCOM Platform and TeleAPI.dll as instructed and I have also installed POTH, the Celestron Scope Driver, MeadeEx Telescope drivers.

The Sky 6 runs as expected.

When I use Telescope:Setup to select the Telescope API and then click Settings and select the Celestron Scope Driver and then click Properties I receive an error dialog that says "Failed to load driver. Cannot create Active X component"

If I select the Meade Classic and AutoStar 1 driver from the Chooser then this appears to allow me to set the Properties correctly.

However if I select POTH, click Settings and then select the "Celestron Scope Driver" I appear to be able to configure the settings. However, if I try to acces the Meade driver through POTH I then get the same error dialog as before.

Why does Properties appear to work for the Meade Driver but not the Celestron driver when used directly but the other way around when using POTH.

Could this be caused by a security setting in Windows 7 preventing the running of Active X controls?

I am running Windows 7 64bit, and The Sky V6.0.0.56

Regards Ian

flag
Please can you check exactly which version of the ASCOM Platform you have installed, and add that information to your question. – Tim Long♦ Jan 26 at 6:42

2 Answers

1

TheSky needs additional DCOM setup for a driver to run properly. Without this it could generate some sort of security error. It's possible that the settings for the Celestron driver are incorrect. There have been sporadic reports of problems but other people saying it's fine.

I can't test because I don't have TheSky.

Using POTH between TheSky and the Celestron driver does work round this problem.

But it doesn't answer why the Meade driver doesn't work.

If there's someone out there, with TheSky, with the problem with the Celestron driver and some familarity with using Regedit to collect and set registry data who wants to help then please contact me and we will try to work through what is happening and how to fix it.

Chris

link|flag
0

It is quite possible that this is a security setting. Check your setting in Internet Explorer, I think it affects this.

link|flag
Internet explorer settings do not affect ASCOM. The IE security settings apply only to ActiveX components that are loaded by Internet Explorer. – Tim Long♦ Jan 26 at 6:40

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.