--- In guide-user@yahoogroups.com, Bill J Gray <pluto@...> wrote:

> I can't say that I can see why that was needed, but I'm glad to
> hear it got things working.

Seems I will need to use that nexhub program if I want to use the nexremte program.

http://www.celestron.com/c3/product.php?ProdID=327#downloads

Because if I use the telescope handcontroller to align the mount, I can get guide 8 to connect to the mount using the scope control option, and then run telescope scope location indicator in real time, and it doeesn't crash.

But If I use nexremote to align the mount, then try to use the scope control option, I get a can't open com port message, after I click on the telescope scope location indicator. Yet in nexremote it shows the com port in use, after I click on the telescope scope location indicator, so guide is causing the port to be in use.

So I will use the nexhub program, since I use nexremote to control the scope from inside the house.

At least I can use the telescope scope location indicator now, that what matters.

Kevin

>

> The URL you mention describes this as a Celestron-only solution, but
> I _assume_ it can work with any serial-port controlled scope, such as
> Meade ones. I've e-mailed the folks at AstroGeeks to confirm this. It
> seems to me it might be of use to people not running ASCOM who have
> multiple applications using the same serial-port controlled scope.
>
> (Of course, the way this _should_ be handled is much simpler:
> a program should not open a serial port and not release it. For
> example, when Guide slews a scope, it accesses the serial port,
> sends data, receives it, and then releases the serial port. Sadly,
> some programs are "greedy" in this regard; ASCOM, in particular,
> doesn't play nicely with others.)
>
> -- Bill
>