Click on exe file and it gives an error message about a problem with the file. I will try downloading again.
What is interesting, I finally did get it to work. On the autostar I did a power off, turned it back on, entered date/time etc. Then I put it into position display mode. I could then talk to it with CDC. I will test things further, also check the trace file for differences in what is transmitted. I did nothing to CDC other then disconect and reconnect and tell it to sync to object, which I had tried repeatedly before. I have another program coming that is supposed to talk to the autostar, I will try it out if I get it acting up like this again. Brian --- In [email protected], "Boyer, William" <[EMAIL PROTECTED]> wrote: > > I suggest pursuing the ASCOM workaround. Please describe in detail what > you mean by the Meade patches not working with ASCOM at the ASCOM-Talk > group. Dick Seymour monitors that group! > > Sorry I can't help more, but I have no Autostar, etc. > > HTH > William > > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of brisleyastro > Sent: Thursday, February 08, 2007 12:57 AM > To: [email protected] > Subject: [skychart-discussion] Problem with autostar slewing to > cursor/object > > 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. Coordinates are updated in the autostar. > I then go to another object on screen, click on it and get its info. > I then right click and ask it to goto cursor position or object. I get > a popup that says: LX200 say: and there is no other data. The scope > motors do not move! > (Now if I move the scope with autostar controller, the co-ordinates on > screen keep up with the changes and it tracks the scope ok.) > > I have had this working, but it has been sporadic and I can't find any > good reason for this behaviour. > I have tried different settings on the comm port for timeout/interval. > I have tried different settings on the refresh. Nothing seems to be a > reason behind this. > > I tried the ASCOM drivers, but the meade patch files do not want to > work, and I get an exception thrown when I tell CDC to goto the object. > > I have looked briefly at the trace file, couldn't see anything there as > to the command even being issued to the autostar! > I see a lot of position updates coming back in, but I don't see any > commands telling it to go to other co-ordinates. > > Brian > > > > > > > > Yahoo! Groups Links >
