Downloaded and installed the Helper.NET program. It ran with no problems. Restarted computer just to play it safe.
Double checked to ensure BT was working by connecting to scope via non-ASCOM drivers in TheSky6 and Astroplanner. No problem connecting. Disconnected and closed other programs. Started CdC and set up telescope (CPC1100). Set to COM4 which is what my BT connects through via the USB to serial emulator and what the other programs successfully used. When I hit "Connect" I now get the error message "Object reference not set to an instance of an object". ??? --- In [email protected], Chris Rowland <chris_group_m...@...> wrote: > > There's an upgrade to the ASCOM serial drivers that may help. It's > called HelperNET and is available from the files area of the Ascom-Talk > group. This replaces the older MSCOMM32.vbx serial driver with a more > up to date .NET serial driver that seems to be supported better by > serial devices. > > An number of people who have had problems with USB to serial devices > have found that this helps and so it might also help with a Bluetooth > serial device. > > Let us know how it goes, > > Chris > > Steve Berte wrote: > > Bob, > > > > Thanks. My laptop is a Dell Vista machine. Will double check to > > ensure I have latest BT driver. > > > > I'll have to check, but I don't think my ACS3 is > > connecting/disconnecting like you describe. I certainly get no > > indication of that in the 4 non-ASCOM programs with which I do > > successfully control my scope via BT. > > > > I'll check out the Widcomm alternative. I suspect the problem does > > lie with the laptop BT driver clashing with ASCOM given non-ASCOM BT > > works like a charm. > > > > What make/model telescope are you driving? > > > > Steve > > > > --- In [email protected], "Bob Rose" > > <bobrose500@> wrote: > >> 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" > >> <atnberte@> 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 > >>> > > > > > > > > > > ------------------------------------ > > > > Yahoo! Groups Links > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > No virus found in this incoming message. Checked by AVG - www.avg.com > > Version: 8.5.339 / Virus Database: 270.12.53/2155 - Release Date: > > 06/04/09 17:55:00 > > >
