[APBeta] Current ASCOM Support?

[Bob]

I have not tested POTH with AP in the last few releases but in the past AP
had some trouble with initializing POTH. I found if I use another program
like CdC to initially connect via POTH then AP could join in. This seemed to
work well and allowed both to communicate the scope.  After changing AP to
ASCOM power cycle AP. The setup for the scope is after POTH is started. Look
under the Setup button. 

Bob

-----Original Message-----
From: apbeta-bounces at lists.astroplanner.net
[mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of Jared
Sent: Saturday, March 20, 2010 3:37 PM
To: AstroPlanner Beta Testers
Subject: [APBeta] Current ASCOM Support?


Hey all, 
I've been changing up my configuration lately and I'm trying to get POTH hub
working with AstroPlanner.  I'm doing this because I have some issues with
my BlueStar connector when using AstroPlanner and I'm trying to see if
connecting to ASCOM rather than directly to the BlueStar would help to
alleviate some of the problems (I also realize that this will likely create
some fun new problems too!)

Anyways I know there were initially some ASCOM issues with AP and I was
trying to figure out if ASCOM is currently working and my setup is just bad
or what the deal is.  Right now I have The scope simulator running and I'm
attempting to connect to it through the POTH but I keep getting a "No
response from telescope..." error.  There doesn't seem to be a lot of
configuration under the "edit" option for the ASCOM driver in AP.  I'm
guessing when I click the connect button that I should see the ASCOM
telescope box pop up and I can select whatever I want it to connect to...is
this normally the case?  

Running on Win 7 64bit with the latest ASCOM platform. Just grabbed AP
2.0b76.

Also is there any place to search this list?

Thanks!
Jared


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.astroplanner.net/pipermail/apbeta-astroplanner.net/attachments/20100320/e1169adc/attachment-0003.htm>