Hello all,

I've had an (off-list) inquiry about a problem with NexStar scope
control, involving a situation where the scope responds to "Slew Scope",
but not "Slew Guide".

Also, there's a problem when using the NexRemote software that is
now supplied with just about all Celestron scopes. This software offers
a "virtual port" capability, which isn't working with Guide. (But which
_does_ work with some other software.)

And now Arild is mentioning problems on a system that is, at least
in theory, Celestron-compatible. (Arild, I've a theory on this one,
at least. Celestron scopes have five almost identical, but slightly
different, control languages. To determine which "flavor" is in use,
Guide tries all of them. "Real" Celestron scopes will respond to only
one of them. I'm wondering if the SynScan scope is responding to some
of the others, in a way that's confusing Guide... do you get any sort
of error message? At what point do things fail?)

Anyway... if anyone has encountered similar (or other) problems with
Celestron or Celestron-compatible scopes, please let me know, either
on or off list. I'm hoping to spot some patterns that will help in
debugging and diagnosing the issues.

Thanks! -- Bill