[APBeta] Telescope Connection Problem

[Paul Rodman]

There are definitely issues with BlueTooth and AP V2. I have not yet resolved them. It would seem the BlueTooth port is not being closed properly. I'm still trying to figure out if it's my fault, my compiler vendor's fault, or Microsoft's fault. Could even be all three.

Paul R.

On Nov 23, 2009, at 5:07 PM, Jared wrote:

> I've been playing around with this a lot tonight.  It looks like it's something between my BlueStar connector and AP.  If I connect the BlueStar into the USB (acting like a USB->Serial) then it works just fine.  However if I connect to it through BlueTooth (which creates a BlueTooth->Serial connection) then I run into problems.  
> 
> If I have the BlueStar turned on before I start AP then AP won't connect to the telescope.  If, on the other hand, I start up AP and then power on the BlueStar it connects just fine (most of the time) 
> 
> I wonder if this is part of the BlueTooth bug that causes AP to take a while to startup?
> 
> Jared
> 
> On Mon, Nov 23, 2009 at 5:12 PM, Mark Ritchie <markritchie at qx.net> wrote:
> I am running V2 2.0b66 and I can connect to a CGEM mount using the ASCOM interface.  I loaded ASCOM 5.0a and the Celestron driver version 5.  I installed the ASCOM 5.5 update, but that caused issues, so I removed it.  I am running Windows XP SP3 using a Belkin USB/Serial adapter.
> 
>  
> I just got the beta version, so I haven’t had a chance to control the telescope under the stars, but it does connect just fine. 
> 
>  
> I hope this helps
> 
>  
> Mark
> 
>  
> From: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-bounces at lists.astroplanner.net] On Behalf Of Ken Harrison
> Sent: Monday, November 23, 2009 11:40 AM
> To: AstroPlanner Beta Testers
> Subject: Re: [APBeta] Telescope Connection Problem
> 
>  
> I have an HEQ5pro which under PC Control ( Keyspan adaptor usb>Serial Comms 2) usually works under Nexstar 5/8 commands.
> 
> When I try under V2 I get an error message saying comms not connected. ( The telescope window, also comes up blank)
> 
> 
> 
>  
> 
> On 23/11/2009, Jared <jwellman at gmail.com> wrote:
> 
> Can someone confirm that they're at least successfully able to connect with a Celestron mount using a Windows machine with AP?  
> 
> Thanks,
> Jared
> 
> 
> 
> On Sun, Nov 22, 2009 at 11:51 AM, Jared <jwellman at gmail.com> wrote:
> 
> I'm not sure if this has been reported yet or not...or if it's part of the the ASCOM issue.  I just wanted to make sure that this is a real unreported issue before I go and file a bug.
> 
> Anyways, whenever I attempt to connect to either my NexStar SE mount or my CGEM AP almost always takes about 15-30 seconds and then says it can't connect.  Using the same connection port and settings I can open up Starry Night and it connects almost immediately.  
> 
> I'm using a Bluestar adapter for interfacing with the telescope.  Is this a common problem or is this something new?  
> 
> I'm using Windows 7 32Bit. This has been happening for a while now.  Eventually it will connect after closing and opening AP enough times.
> 
> Thanks,
> Jared
> 
> 
> 
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net
> 
> 
> 
> 
> -- 
> "Very funny Scotty... now beam down our clothes!"
> http://tech.groups.yahoo.com/group/astronomical_spectroscopy/?yguid=322612425
> 
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net
> 
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net

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