Hi Ben, all,

According to Celestron's documents on how to communicate with their scopes,
nothing has changed. Obviously, though, something _has_ changed. (Celestron
has done a poor job of documenting these things in the past, so I'm not
totally surprised. For a long time, most of what I knew about Celestron
control came from people other than Celestron.)

So. A request to anyone running into problems with NexStar scopes: run
Guide, and hit Alt-J, and enter

DEBUG_FILENAME=debug.txt

Then try to control the scope.

When you're done, there should be a file 'debug.txt' in your Guide folder.
It will contain details of what was sent to the scope and what came back. I'll
look at that and, I hope, be able to see what Celestron has done to make
life difficult this time. (Past changes haven't been anything big -- things
like "send E rather than E plus carriage return", "values are separated by
a comma instead of a space", etc. Such changes are annoying and seem totally
pointless. But on the bright side, they usually aren't hard to work around.
Let's hope that's the case this time, too!)

-- Bill