Steve, I am using Aircable BTserial (older models) with ASCOM and CdC. One of the things I found out that Microsofts standard BT stack is weak with the Aircables. Widcom is much better if your hardware is widcom compatible. One of the changes I encountered with a change from XPP to Vista was that the connection became on demand. Which means paring is needed on the start of each session. This would not be necessary if Aircable would make PIN optional. Once paired it connects and disconnects as needed without further keying in of the PIN. You might want to check with the laptops manufacture site for updated driver for your BT hardware. The new one for mine from Dell greatly improved performance. Bob
--- In [email protected], "Steve Berte" <atnbe...@...> wrote: > > I'd appreciate hearing from anyone out there who is successfully connecting > to their scopes using CdC ASCOM drivers through a BT device. Specifically, > which brand/model of BT device works for you? Please also include the scope > you use. > > I'm asking because although my AirCable Serial 3 device works flawlessly with > other software programs I have (Astroplanner and TheSky6)to control my scope > (Celestron CPC1100) using non-ASCOM drivers, I've never been able to get CdC > to connect via BT. Cable connections work every time, but never BT. BT > attempts yield "no telescope connected" messages. > > I've seen a post that noted that "some USB serial ports have problems with > the MSCOMM32.vbx". That's above my head, but it indicates to me that perhaps > my particular device clashes with some portion of the ASCOM driver system. > > I'd also be interested if anyone out there DOES control their scope with CdC > and an AirCable Serial 3. > > Thanks, > Steve >
