Bluetooth Serial Adapter
Posted 02 December 2008 - 10:31 PM
Well sure the other program has it! Ha.
Ed-- that software package for Nexstar must control the ports opening and closing.... or am I missing something?
Posted 03 December 2008 - 09:10 AM
Posted 03 December 2008 - 11:11 AM
You have to start NexHub first assigning its master port to the port that the Bluetooth USB is connected to. Then assign your astro apps to NexHubs slave ports (virtual com ports) and all should work. There are 9 slave ports on NexHub. Thatâ€™s way too many ports for me to use.
Posted 03 December 2008 - 11:40 AM
I guess i am still looking for a solution.
Posted 03 December 2008 - 03:29 PM
Posted 03 December 2008 - 03:42 PM
Currently I use POTH(Ascom) to control the scope, focus and dome. I use Stellarium(really heats up the laptop) through the network to interface to POTH at the dome from my laptop. I am not all that happy with POTH, thus I try to use AutostarSuite over the network at times. I also use tightVNC to control the dome computer from remote locations, like my house. I would like to be able to connect both at the same time to the LX200R. That way POTH would know where the scope is pointing and would keep the dome in sync with it. I could then use Meade's software to focus and point the scope. When both Comm ports on the scope are used, the scope gets bogged down, thus I am trying to figure out a way to keep the polling trafic to a minimum.
The error i get when connecting NexHub in "port not available".
Posted 03 December 2008 - 06:10 PM
Posted 03 December 2008 - 10:07 PM
After futher review, I did get the nexHub working with both the Ascom MeadeGPS driver and the AutostarSuite at the same time. It was still kind of flakey.
Posted 08 December 2008 - 11:42 AM
Posted 08 December 2008 - 02:30 PM
Posted 10 December 2008 - 03:25 PM
1. Using an Acer One with XP Home, a no name bluetooth dongle, an Air Cable 3, a special Astro Cable connector that plugs into the 497 Controller and has a 9 volt battery connection built in to power the Air Cable 3.
This cable: http://www.astrocabl...ion/item/id/12/
I used the Meade software to control the scope (inside) for a test. It connected and I brought up the Meade controller panel using the software and "aligned" the scope-- then I did a fake slew to several objects using the Acer One and the Meade software--
Here is the small issue-- I left it alone for about 5 minutes and it lost the connection. I was able to use the Meade software to re-acquire the scope and continue doing gotos --- this has to be something in Windows that is idling the connection when there is no activity for a time (on bluetooth)--- ????? It did reacquire the Air Cable-- however I would prefer that it NEVER drops the communication. Anyone have a suggestion for how to retain the bluetooth connection in Windows XP.
Appreciate your help.
Posted 11 December 2008 - 01:07 PM
Posted 11 December 2008 - 01:33 PM
I do not see and "idle" setting of any kind-- in bluetooth; the wifi card does have a "turn off power saving" -- but not the bluetooth.
Posted 13 December 2008 - 10:36 AM
Posted 17 December 2008 - 06:31 PM
I have successfully controled the scope using the Meade Autostar suite planetarium program. Everything appears to work just fine.
However, Cartes du Ciel and Stellarium do not work using the ASCOM drivers. I am posting questions on the ASCOM Yahoo forum, but no real answers yet. It just may be that ASCOM will not work over bluetooth?
Will keep you advised-- but the Meade software does work. I have not tested the "Scope Driver" control software yet... I will do that next.... with their trial version.
Additionally-- I am using the Meade regular serial cable that you use to update the firmware on the 497 hand controller. I just plug the Air Cable 3 into the serial port connection on the cable and plug the "phone plug" side into the 497 hand controller. This arrangement has given me a good connection. I am also using the "Little" slave Basic program located on the Air Cable web site-- I just added one line of code for BAUD 96, and sent the program to the Aircable 3 using the regular Windows bluetooth SEND command. Air Cable's Basic programs are here--
Posted 18 December 2008 - 10:48 AM
Posted 18 December 2008 - 11:16 AM
Your comment about using bluetooth with CDC is interesting but I have no answer for why yours would work and mine does not??? Everything works with a hard wired cable-- and Meade's software works on my bluetooth..... but not the other programs.
I was hoping some of the computer "geeks" on this forum might have a solution?
Posted 19 December 2008 - 10:46 AM
Posted 19 December 2008 - 01:47 PM
I get " does not appear to be anything connected" error message...... the Air Cable blue light lights up indicating a transmission from the laptop. Usually this stays on permanently once a connection is made. After maybe 10 seconds I get the above message..... and the blue led goes off.
EDIT-- guess I should have said the one for the 497 hand controller-- but I have also tried the LX200 driver neither of them work.
Posted 22 December 2008 - 10:14 AM
Posted 26 December 2008 - 09:44 AM
Posted 26 December 2008 - 10:45 AM
Posted 21 January 2009 - 01:49 PM
Now when I reload the software that DID work with the Meade Autostar Suite --- even the Meade program does not work. !
This has been a frustrating bluetooth experience. A direct cable USB-Serial connection still works perfectly. But nothing works across bluetooth; not even the Autostar software as previously reported. Aircable tells me that their USB branded dongle will setup a SINGLE COM port automatically with any other Aircable branded device. However it costs about $70 --- a little too expensive just to run a "test".
Edward-- it might be my USB bluetooth dongle-- but who knows without buying another one which would be the Kensington as you recommend?????
I will probably just use a hard wired connection and try to figure out how to keep the cables away from the kids at our public observing events. So far the bluetooth telescope control has been a complete failure, on my XP laptop using the Windows bluetooth stack-- the Aircable 3, and a normal USB bluetooth dongle on the laptop.
Posted 23 January 2009 - 05:13 PM
Looking back through the post, I did notice that it was never mentioned that astro apps must be routed through the real HC or virtual HC (Nexremote) to operate property. I thought I would through that out for future readers looking for info here.
Donâ€™t lose heart Joe. We are on the cutting edge of technology here so there are always issues to iron out. My issue right now is that I can use my wireless setup when routed through the real HC (NexStar GPS 11) but not through the PC Port using NexRemote. Oh well.