I do mean sync. I am on a polar GEM, I have an object centered and I want the autostar to think that is where it is. That was my understanding of the sync command. What is there with that to confuse the autostar. (I have no need to 'align' the autostar, as my polar alignment is excellent. Tracking with toucam and 2x barlow, Saturn stayed in frame for over 1.5 hours!) I have tried different communication timeouts, currently back on 1000.
What is interesting, I did a power off reset on the 497, entered date/time etc. Then I went to the co-ordinate display mode. I could then talk and move the mount! Not sure who is causing the problem, 497 or CDC. Brian --- In [email protected], "Bob Rose" <[EMAIL PROTECTED]> wrote: > > I have used both the ASCOM and the Meade Drivers in 2.76 and the > ASCOM driver in V3. Bother versions preformed well even using > Bluetooth. > > --- In [email protected], "brisleyastro" > <brisleycpc@> wrote: > > > > I am running v2.76 CDC and V3 beta. > > I choose meade as my scope interface. > > I connect to the autostar, set the time. > > Everything checks, autostar beeps. I can do a query, it reports > back > > the correct autostar rom info. > > On the coordinates pain, I can choose directions, and scope moves > > accordingly, coordinates adjust. > > I then center a known object. (polar mounted and aligned) > > I tell CDC to do a sync to the scope. > > "Sync" is not correct. The Autostar (ETX, 497) do not need or want > to be synced. Small "Sync"ing adjustment are ok, but large ones will > confuse the Autostar. If you mean "Connect" then ignore what I just > said. Another thing some Autostars has trouble with is the refresh > rate. I have 2 that work well at 500 but others that don't. I leave > mine at 1000, which equals 1 second. Try changing the refresh rate > and report back in detail and we can go from there. > Bob >
