Hello everyone,

I am having problems installing the StarShoot Pro ASCOM driver under Windows 7
64 bit. I am using ASCOM platform 5.0b with the 5.5.1 update. The StarShoot Pro
just does not show up as an option in my hardware selection.

When I switched to Windows Vista a while back, there was a procedure to manually
register a device in ASCOM, but that procedure does not seem to work for me any
more.

I believe there was another person asking about this a few months ago, but I did
not see a resolve of that issue.

Can anyone help me with this issue? I can help in any way, screen shots, logs,
etc.

Thanks,
-Mike

I am testing my own camera's ASCOM driver and it seemed my camera worked with
Maxim DL but I found one error.
I selected my camera's driver from ASCOM cameras driver list and selected
connect menu and I could use my camera and camera worked well but after I
disconnected and connected it again.
There was below error message and camera did not work and I had to plug out and
it again.
"could not retrieve camera properties"

Could anyone help me where this error is from? And how could I fix it?

It's difficult to help as it's your code and we don't have any insight
into what it's doing. You don't even mention what programming language
you're using - but I'll hazard a guess that you might be using C# or
VB.NET. What might be happening is that your driver is not properly
cleaning up when it is disconnected. My guess would be that the driver
is holding the camera connection open, so that when you reconnect it in
MaxIm, Maxim tries to load another instance, which then fails to connect
because the existing (orphaned) instance is still holding the resources.
If that is the case, then when the application (MaxIm) sets your
Connected property to False, you must fully disconnect the
communications channel and release all resources related to it. You
should also implement the IDisposable interface in your driver for good
measure (see http://www.codeproject.com/KB/cs/idisposable.aspx).

If you need further help then we'll need to see source code. If you
don't mind your code being publicly visible then you can add it to the
ASCOM version control server (contact me off list if you want to do
that) then ASCOM developers will be able to look at your code and help
you resolve your issues.

Regards,
--Tim Long

-----Original Message-----
From: ASCOM-Talk@yahoogroups.com [mailto:ASCOM-Talk@yahoogroups.com] On
Behalf Of Moon
Sent: 01 June 2010 03:28
To: ASCOM-Talk@yahoogroups.com
Subject: [ASCOM] [MaxIM DL] ASCOM Camera Driver error

I am testing my own camera's ASCOM driver and it seemed my camera worked
with Maxim DL but I found one error.
I selected my camera's driver from ASCOM cameras driver list and
selected connect menu and I could use my camera and camera worked well
but after I disconnected and connected it again.
There was below error message and camera did not work and I had to plug
out and it again.
"could not retrieve camera properties"

Could anyone help me where this error is from? And how could I fix it?




------------------------------------

For more information see http://ASCOM-Standards.org/.

To unsubscribe from this group, send an email FROM THE ACCOUNT YOU USED
TO SUBSCRIBE(!) to:
ASCOM-Talk-unsubscribe@yahoogroups.com

Yahoo! Groups Links




--
ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=o51EcGkf016385&from=tim@tigranetwo\
rks.co.uk
Complete email hygeine and business continuity solution available from
http://www.tigranetworks.co.uk

Your best option is to write a test harness that reproduces the problem, then
use that to debug through your driver code, and so find out what's happening.

Once you know what's happening the solution will probably be obvious.

Chris

--- In ASCOM-Talk@yahoogroups.com, "Moon" <moon9211@...> wrote:
>
> I am testing my own camera's ASCOM driver and it seemed my camera worked with
Maxim DL but I found one error.
> I selected my camera's driver from ASCOM cameras driver list and selected
connect menu and I could use my camera and camera worked well but after I
disconnected and connected it again.
> There was below error message and camera did not work and I had to plug out
and it again.
> "could not retrieve camera properties"
>
> Could anyone help me where this error is from? And how could I fix it?
>

Thank you for your comments and I will test my code again.



--- In ASCOM-Talk@yahoogroups.com, "Chris" <chris_group_mail@...> wrote:
>
> Your best option is to write a test harness that reproduces the problem, then
use that to debug through your driver code, and so find out what's happening.
>
> Once you know what's happening the solution will probably be obvious.
>
> Chris
>
> --- In ASCOM-Talk@yahoogroups.com, "Moon" <moon9211@> wrote:
> >
> > I am testing my own camera's ASCOM driver and it seemed my camera worked
with Maxim DL but I found one error.
> > I selected my camera's driver from ASCOM cameras driver list and selected
connect menu and I could use my camera and camera worked well but after I
disconnected and connected it again.
> > There was below error message and camera did not work and I had to plug out
and it again.
> > "could not retrieve camera properties"
> >
> > Could anyone help me where this error is from? And how could I fix it?
> >
>

For those of you who want to, you can follow the proposal here:
http://area51.stackexchange.com/proposals/51/astronomy

If you confirm your email, you will get a jump-start in the process, but you
don't need to if you just want to follow a proposal. If this doesn't make sense,
read the FAQ: http://area51.stackexchange.com/faq

Hi,
i just downloaded the TeleAPI.dll file. i plan to use it with TheSky as per
instructions.

I copied it to the c:\Programmi|File Comuni\System directory (my windows XP is
in italian)

then i went to TheSky, and selected "Telescope API", went to Settings, and the
ASCOM telescope chooser opens up.

There i chose "MEADE LX200" (my scope) and click Properties.

A window pops up stating "Failed to load driver, cannot create the component
ActiveX".

The same if i open the POTH hub, and go selecting my Meade LX200 scope.

I have seen this message reported in several posts here, but none referring to
my situation.
I have installed the last ASCOM upgrade.

TheSky connects properly to my telescope on COM3.
POTH connects properly to a "TheSky controlled telescope".
Any suggestion?

thanks,
Paolo Gramigna from Italy

Hello,

I'm am trying to connect a DFK 21AU04 USB CCD camera to Maxim DL 5.09. The
computer is running Windows 7 on a Dell Studio XPS Intel Core i7. I have ASCOM
Platform 2008 (v5.5) and I downloaded and installed the DMK CCD driver v1.3 from
www.deepsky-online.com and the driver from the disk that came with the camera

The trouble comes when I try to connect. I went to the Camera Control window
clicked Setup Camera, chose ASCOM as the Camera Model. In Advanced I chose
DMKCCD Camera V1.3. Then I tried to connect. Two windows pop up. Astronomy
Camera Properties and Device Settings. I can select DFx 21AU04 in the Device
Settings dialog box, but when I press OK it gives me these errors: "DMKCCDV1.3:
Index was outside the bounds of the array." and "Error opening camera The camera
link has failed" again.  Also, I was able to connect a DMK 21AU04.AS and that
camera works and connects in Maxim DL. I installed IC Capture and both cameras
are able to connect and work. So, the only problem is the combination of the DFK
21AU04 with Maxim DL. Does anyone know why I cannot connect to the DFK 21AU04?

Thanks for your help.

Tim

Hello,

I'm trying to get my QHY5 to work with PHD and when I use the ASCOM platform i'm
having several issues. The ASCOM platform is installed, the update was
downloaded, and all drivers appear to have been installed. When in PHD I can
choose the ASCOM platform, then choose the QHY5 and PHD does recognize the
camera.

If I hit loop exposure I get the message "Exception thrown during image capture
- bailing" and it will not take an image. It worked 1 time last week but
suddenly stopped when I went out to image. I only have a few days before the
CSSP to get this straightened out...

If I try to take a dark, it will ALWAYS say to cover the guidescope, even when
it is covered. Then it will have an unhandled exception and proceed to crash
PHD.

If I use QGVideo the camera responds perfectly normal so it is something between
PHD and the ASCOM platform. Any ideas?

Thanks guys,
Jeremy

I am looking at the ASCOM specifications for the Camera interface and
have some questions about ImageData

In Version 1 this was a safearray of ints.  In version 2 this is a safe
array of longs.

Some questions:

1. This apparently means that Version 2 is not backwards compatible with
Version 1 unless an int is now a long  (I know the safearray should have
the type of the array [int or long] so it should be a minor issue)

2. Has long been defined as a fixed size (e.g., 32 bits)?   There are
computers where a long is 64 bits.

3. Are there any cameras that digitize to more than 16 bits? or are we
assuming that there could be sometime in the future.


Thanks,
Ralph Pass

From what I can see the Camera V1.0 specification specifies ImageArray as a
safearray of longs, and although it doesn't say what's meant is 32 bits, the VB6
long.

Is it V2 that specifies ints? In which case it means 32 bit ints, the C# int.

I believe that V2 just adds properties to the V1 specification but does not
change those that are already defined so they are compatible.

I think the definitions are:
Short 16 bits signed
Long  32 bits signed
Double 32 bit float
int  32 bits signed

The original specifications were all written assuming that VB6 data types would
be used, maybe it needs a documentation update to make it clearer.

I don't know of a camera that uses more than 16 bits but assuming there will be
one day seems pretty safe.

Chris

--- In ASCOM-Talk@yahoogroups.com, Ralph Pass <rppass@...> wrote:
>
> I am looking at the ASCOM specifications for the Camera interface and
> have some questions about ImageData
>
> In Version 1 this was a safearray of ints.  In version 2 this is a safe
> array of longs.
>
> Some questions:
>
> 1. This apparently means that Version 2 is not backwards compatible with
> Version 1 unless an int is now a long  (I know the safearray should have
> the type of the array [int or long] so it should be a minor issue)
>
> 2. Has long been defined as a fixed size (e.g., 32 bits)?   There are
> computers where a long is 64 bits.
>
> 3. Are there any cameras that digitize to more than 16 bits? or are we
> assuming that there could be sometime in the future.
>
>
> Thanks,
> Ralph Pass
>

First, It's not AstroAnswers it's a totally new site.

And now, after much effort by lots of people, the management have
decided that it's not doing what they want so they have removed all the
voting and everybody's karma so you can't do anything without starting
again.

I don't think this lot can be trusted to run a site and we will be
better off with something that's less susceptible to the whims of these
people.

Chris

On 02/06/2010 14:11, Arlen Beiler wrote:
> For those of you who want to, you can follow the proposal here:
> http://area51.stackexchange.com/proposals/51/astronomy
>
> If you confirm your email, you will get a jump-start in the process,
> but you don't need to if you just want to follow a proposal. If this
> doesn't make sense, read the FAQ:
> http://area51.stackexchange.com/faq
>
>
>
> ------------------------------------
>
> For more information see http://ASCOM-Standards.org/.
>
> To unsubscribe from this group, send an email FROM THE ACCOUNT YOU
> USED TO SUBSCRIBE(!) to: ASCOM-Talk-unsubscribe@yahoogroups.com
>
> Yahoo! Groups Links
>
>
>
>
> No virus found in this incoming message. Checked by AVG -
> www.avg.com Version: 9.0.819 / Virus Database: 271.1.1/2911 - Release
> Date: 06/01/10 19:25:00
>

 

First, It's not AstroAnswers it's a totally new site.

And now, after much effort by lots of people, the management have
decided that it's not doing what they want so they have removed all the
voting and everybody's karma so you can't do anything without starting
again.

I don't think this lot can be trusted to run a site and we will be
better off with something that's less susceptible to the whims of these
people.

Chris

I am using ASCOM's 5.5 platform, along with POTH 5.3.0, and ASCOM's Celestron's
5.0.1.4 scope driver. When setting up POTH, I select Celestron's driver for the
scope, but neither the Nexstar 4 or 5SE models are not listed. Is there a
current Celestron driver which does ?

Is anyone working on updating the teleapi.dll file so that the new Astro-Physics
ASCOM Driver can be used with TheSkyX Pro? I think the changes were supposed to
be pretty minor.

Thanks,
KW

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the ASCOM-Talk
group.

   File        : /Bob Denny/TeleAPI-SkyX-Beta.zip
   Uploaded by : dc3dreamer <rdenny@...>
   Description : Update to TeleAPI.dll that supports TheSky X (still works with
TheSky 5/6)

You can access this file at the URL:
http://groups.yahoo.com/group/ASCOM-Talk/files/Bob%20Denny/TeleAPI-SkyX-Beta.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/forms/general.htmlfiles

Regards,

dc3dreamer <rdenny@...>

> Is anyone working on updating the teleapi.dll file so that the new
> Astro-Physics ASCOM Driver can be used with TheSkyX Pro? I think the changes
> were supposed to be pretty minor.

Yes, I am. In fact, after a several day wrestle with COM innards, I believe I
have the TeleAPI working. TheSky X calls into TeleAPI from multiple threads, and
I had to jump through some hoops to allow TheSky  X to call out to an ASCOM
driver which must be assumed to be "apartment" (a form of single) threaded. It's
easy to call the needed changes 'minor' before you actually try :-)))

I've uploaded it to the Bob Denny folder in the files section of this group. I
would appreciate any feedback, positive or negative. Please remember this is a
BETA(!!) so don't jump my a** if it has problems ;-)

   -- Bob

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the ASCOM-Talk
group.

   File        : /Bob Denny/TheSky Driver-SkyX-Beta.zip
   Uploaded by : dc3dreamer <rdenny@...>
   Description : TheSky Driver which supports TheSky X. Tracking control does not
work and slew errors may not be reported, both due to limitations in TheSky X.
Replace (yeah REPLACE!) the existing driver DLL with this one.

You can access this file at the URL:
http://groups.yahoo.com/group/ASCOM-Talk/files/Bob%20Denny/TheSky%20Driver-SkyX-\
Beta.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/forms/general.htmlfiles

Regards,

dc3dreamer <rdenny@...>

Paolo --

How did you get/install the Meade LX200 driver? It sounds like it got on
to your system some way besides the
driver installer on the ASCOM site. If needed, download the latest Meade
LX200 and Autostar driver from the ASCOM site, run the installer and
report back.

    -- Bob

You said:
> Hi,
> i just downloaded the TeleAPI.dll file. i plan to use it with TheSky as per
instructions.
>
> I copied it to the c:\Programmi|File Comuni\System directory (my windows XP is
in italian)
>
> then i went to TheSky, and selected "Telescope API", went to Settings, and the
ASCOM telescope chooser opens up.
>
> There i chose "MEADE LX200" (my scope) and click Properties.
>
> A window pops up stating "Failed to load driver, cannot create the component
ActiveX".
>
> The same if i open the POTH hub, and go selecting my Meade LX200 scope.
>
> I have seen this message reported in several posts here, but none referring to
my situation.
> I have installed the last ASCOM upgrade.
>
> TheSky connects properly to my telescope on COM3.
> POTH connects properly to a "TheSky controlled telescope".
> Any suggestion?
>
> thanks,
> Paolo Gramigna from Italy
>

Hi ALl --

I've posted beta versions of TheSky Controlled Telescope driver and the TeleAPI
plugin, both of which support TheSky X Professional (10.1.6 tested). If you're
confused about these two components, please see

http://ascom-standards.org/FAQs/TheSky.htm

TeleAPI should just work. If you are on a 64-bit system be sure to put it into
C:\Program Files (x86)\Common Files\System since TheSky X is a 32-bit program.
This is vital!

If you want to try TheSky Controlled Telescope using TheSky X as a telescope
controller, replace the TheSky Driver.dll in C:\Program Files\Common
Files\ASCOM\Telescope Drivers (or Program Files (x86) if on a 64-bit system!).
And yes I mean REPLACE the file, don't play games with names. If you want to
keep the old one copy it somewhere else.

TheSky driver does not support tracking on/off due to a limitation in TheSKy X
(it still works fine in TheSky 5/6). Also, (rare) slew errors are not picked up
if using TheSky X (only), also due to a limitation in same.

Before trying to connect, be sure to click Properties in the Chooser and set the
driver for TheSky X!!

Both components are in the Bob Denny folder of the Files section of this group,
each in its own separate ZIP file).

   -- Bob

Bob,

That's great news!

Can I make a suggestion?  Why don't we build an installer for the TeleAPI
plug-in, and make it a separate download?  That would be MUCH easier to explain
to customers than the current procedure.

Doug

--

Doug George
dgeorge@...

Diffraction Limited
Makers of Cyanogen Imaging Products
http://www.cyanogen.com/

100 Craig Henry Dr., Suite 202
Ottawa, Ontario,
Canada, K2G 5W3

Phone:    (613) 225-2732
Fax:      (613) 225-9688



On 2010-06-04 10:53 PM, Bob Denny wrote:
> Hi ALl --
>
> I've posted beta versions of TheSky Controlled Telescope driver and the
TeleAPI
> plugin, both of which support TheSky X Professional (10.1.6 tested). If you're
> confused about these two components, please see
>
> http://ascom-standards.org/FAQs/TheSky.htm
>
> TeleAPI should just work. If you are on a 64-bit system be sure to put it into
> C:\Program Files (x86)\Common Files\System since TheSky X is a 32-bit program.
> This is vital!
>
> If you want to try TheSky Controlled Telescope using TheSky X as a telescope
> controller, replace the TheSky Driver.dll in C:\Program Files\Common
> Files\ASCOM\Telescope Drivers (or Program Files (x86) if on a 64-bit system!).
> And yes I mean REPLACE the file, don't play games with names. If you want to
> keep the old one copy it somewhere else.
>
> TheSky driver does not support tracking on/off due to a limitation in TheSKy X
> (it still works fine in TheSky 5/6). Also, (rare) slew errors are not picked
up
> if using TheSky X (only), also due to a limitation in same.
>
> Before trying to connect, be sure to click Properties in the Chooser and set
the
> driver for TheSky X!!
>
> Both components are in the Bob Denny folder of the Files section of this
group,
> each in its own separate ZIP file).
>
>    -- Bob

Yes indeed.

> Can I make a suggestion?  Why don't we build an installer for the TeleAPI
> plug-in, and make it a separate download?  That would be MUCH easier to
explain
> to customers than the current procedure.

Hi Bob,

just to be sure, i re-installed the LX200 driver (the LX200 non-GPS "classic"
one, this is the scope i use in TheSky and it works flawlessly since my 10micron
mount uses that protocol). I went to the driver section, downloaded a fresh copy
of the exe file; then i went to the ASCOM profile explorer, modified the version
to "5" since the exe file will not work on the 5.5 version; installed the exe
file; resetted the version to 5.5.

At this point, i went to TheSky, choose Telescope API for my scope,  click
settings, Choose LX200 scope and click Properties.

The same message appeared as before:
"Failed to load driver, cannot create the component ActiveX"

if i choose the telescope simulator, then i can click properties and all works.

if i choose POTH, and then click properties, the POTH opens and there i can
choose "TheSky controlled telescope" and all works well; but i have added an
un-necessary layer...

teleAPI.dll is in my programmi/file comuni/system directory, and it is the last
version.

i'm relly confused... hope you can help me.

thanks,
paolo




--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Paolo --
>
> How did you get/install the Meade LX200 driver? It sounds like it got on
> to your system some way besides the
> driver installer on the ASCOM site. If needed, download the latest Meade
> LX200 and Autostar driver from the ASCOM site, run the installer and
> report back.
>
>    -- Bob
>
> You said:
> > Hi,
> > i just downloaded the TeleAPI.dll file. i plan to use it with TheSky as per
instructions.
> >
> > I copied it to the c:\Programmi|File Comuni\System directory (my windows XP
is in italian)
> >
> > then i went to TheSky, and selected "Telescope API", went to Settings, and
the ASCOM telescope chooser opens up.
> >
> > There i chose "MEADE LX200" (my scope) and click Properties.
> >
> > A window pops up stating "Failed to load driver, cannot create the component
ActiveX".
> >
> > The same if i open the POTH hub, and go selecting my Meade LX200 scope.
> >
> > I have seen this message reported in several posts here, but none referring
to my situation.
> > I have installed the last ASCOM upgrade.
> >
> > TheSky connects properly to my telescope on COM3.
> > POTH connects properly to a "TheSky controlled telescope".
> > Any suggestion?
> >
> > thanks,
> > Paolo Gramigna from Italy
> >
>

It doesn't matter much which you select, all it does is set some defaults such
as the aperture.

So choose another scope of a similar type and it should be fine.

Chris

--- In ASCOM-Talk@yahoogroups.com, "Roger" <leeroger24@...> wrote:
>
> I am using ASCOM's 5.5 platform, along with POTH 5.3.0, and ASCOM's
Celestron's 5.0.1.4 scope driver. When setting up POTH, I select Celestron's
driver for the scope, but neither the Nexstar 4 or 5SE models are not listed. Is
there a current Celestron driver which does ?
>

Hi Bob,
just an upgrade.
i reinstalled from scratch the ascom platform, and then the upgrade.

whatever hub i open (focusmax, maxpoint, POTH) the only telescopes that i can
connect with are "The Sky controlled telescope", and the "generic LX200" scope.
the first one works, the second does connect but does not work with my mount.

all the other telescopes, on clicking properties, are producing the same
message: A window pops up stating "Failed to load driver, cannot create the
component ActiveX".

my idea was to stop using TheSky, and change to SkyMap pro which is ascom
compliant (and simpler to use). So i can use maxpoint as a hub, and connect both
Skymap pro and focusmax to it.

this procedure works if i select "generic lx200" as my scope, so that both
focusmax and Skymap Pro will work through maxpoint.

unfortunately, the "generic LX200" does not work with my mount... it appears
that the "LX200 non GPS" is required; but then the ominous message is popping
up...

any suggestion?

thanks,
Paolo


--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Paolo --
>
> How did you get/install the Meade LX200 driver? It sounds like it got on
> to your system some way besides the
> driver installer on the ASCOM site. If needed, download the latest Meade
> LX200 and Autostar driver from the ASCOM site, run the installer and
> report back.
>
>    -- Bob
>
> You said:
> > Hi,
> > i just downloaded the TeleAPI.dll file. i plan to use it with TheSky as per
instructions.
> >
> > I copied it to the c:\Programmi|File Comuni\System directory (my windows XP
is in italian)
> >
> > then i went to TheSky, and selected "Telescope API", went to Settings, and
the ASCOM telescope chooser opens up.
> >
> > There i chose "MEADE LX200" (my scope) and click Properties.
> >
> > A window pops up stating "Failed to load driver, cannot create the component
ActiveX".
> >
> > The same if i open the POTH hub, and go selecting my Meade LX200 scope.
> >
> > I have seen this message reported in several posts here, but none referring
to my situation.
> > I have installed the last ASCOM upgrade.
> >
> > TheSky connects properly to my telescope on COM3.
> > POTH connects properly to a "TheSky controlled telescope".
> > Any suggestion?
> >
> > thanks,
> > Paolo Gramigna from Italy
> >
>

Hello together,

after using the search function within this group I checked, if anyone else is
having trouble with this error while trying to start the POTH.

As EQAlign is asking for ASCOM5 I installed ASCOM5 and the update to 5.5
yesterday evening. When starting the POTH I get the error message: Runtime Error
"Type Mismatch". Until yesterday I was running 4.1 without any problems, so
going back to the old version is no big deal.

But anyway, I would like to understand, where this error comes from. I already
tried to change the decimal from "," to "." because this is what I thought might
cause the error, but without any changes on the ewrror. Still there...

So, does anyone of you guys have an idea, how this problem could be solved?

Many thanks in advance for responding.

Kind regards from Austria,
Chris

Hi Bob,

I connected TheSkyX using the new teleAPI.dll with the new AP ASCOM driver.
Everything seemed to work fine except the driver wasn't terminated upon
disconnect from TheSky X. I had to go to Task Manager and kill it.  I should be
able to test more over the next couple of nights.

Thanks,
Kerry

--- In ASCOM-Talk@yahoogroups.com, Bob Denny <rdenny@...> wrote:
>
> Hi ALl --
>
> I've posted beta versions of TheSky Controlled Telescope driver and the
TeleAPI
> plugin, both of which support TheSky X Professional (10.1.6 tested). If you're
> confused about these two components, please see
>
> http://ascom-standards.org/FAQs/TheSky.htm
>
> TeleAPI should just work. If you are on a 64-bit system be sure to put it into
> C:\Program Files (x86)\Common Files\System since TheSky X is a 32-bit program.
> This is vital!
>
> If you want to try TheSky Controlled Telescope using TheSky X as a telescope
> controller, replace the TheSky Driver.dll in C:\Program Files\Common
> Files\ASCOM\Telescope Drivers (or Program Files (x86) if on a 64-bit system!).
> And yes I mean REPLACE the file, don't play games with names. If you want to
> keep the old one copy it somewhere else.
>
> TheSky driver does not support tracking on/off due to a limitation in TheSKy X
> (it still works fine in TheSky 5/6). Also, (rare) slew errors are not picked
up
> if using TheSky X (only), also due to a limitation in same.
>
> Before trying to connect, be sure to click Properties in the Chooser and set
the
> driver for TheSky X!!
>
> Both components are in the Bob Denny folder of the Files section of this
group,
> each in its own separate ZIP file).
>
>   -- Bob
>

Good and bad news. I'll look at this as soon as I can. Thanks for the
report!

   -- Bob

> I connected TheSkyX using the new teleAPI.dll with the new AP ASCOM driver.
Everything seemed to work fine except the driver wasn't terminated upon
disconnect from TheSky X. I had to go to Task Manager and kill it.  I should be
able to test more over the next couple of nights.
>
> Thanks,
> Kerry
>
>