[APBeta] ASCOM (Paul Rodman)

[Bob Rose]

Paul,
One of the things you might want to take a look at is starting the telescope 
interface when AP fires up.  From an end users standpoint I don't see why it 
can't startup on demand instead of starting with AP.  It would also allow 
faster startups on systems that have Bluetooth but aren't actively paired 
with a serial device.  I feel this is one of the reasons many are having 
trouble with ASCOM/POTH. AP has to be first, always. The other programs may 
be connected only after AP.
Another pit fall to the telescope interface starting with AP is that if you 
have Bluetooth and have an AirCable BT serial which requires a pass code. 
Buy the time you key it in, AP or Windows had reset the connection, the pass 
code is ignored and demands a new one.  Right now I get around this by using 
another ASCOM program to start the BT to Aircable connection, disconnect 
then start AP with ASCOM and it works. This works because the pass code is 
remembered for each windows session ASCOM only. The workaround fails if I 
try to use the native AP scope drivers.  This may be a Vista only problem. I 
did not have this on V1 on XP laptop.
If you need any specific procedures tested quickly drop me a note. I have a 
scope set up inside (meade) and can usual test same day, in the evening 
sometimes within minutes.
Bob



--------------------------------------------------
From: "Paul Rodman" <paul at ilanga.com>
Sent: Thursday, August 06, 2009 11:33 AM
To: "AstroPlanner Beta Testers" <apbeta at lists.astroplanner.net>
Subject: Re: [APBeta] ASCOM (Paul Rodman)

> I am, in fact, re-implementing ASCOM support from the ground up. It  might 
> take a while, and I might be asking some ASCOM-related questions  here in 
> the next day or two to make sure I understand what is expected  of APV2 in 
> terms of ASCOM support. I have already found a number of  areas for 
> improvement.
>
> Paul R.
>
>