It seems like daylight savings throws a monkey wrench into the minds of a
lot of people with regard to their LX200. All the LX200 really cares
about is GMT, and when you put in your local time with the offset, all
the LX200 is doing is calculating the GMT from that. When you move your
clock an hour, there is no need to change it in the LX200 because you
would need to change the offset by an hour as well.

Accurately set the LX200's clock to GMT and everything should work fine.
Use the offset only as a convenience.

Chris Vedeler
http://www.isomedia.com/homes/cvedeler/space.htm
Tucson, AZ


> Last night, the first clear one for ages, I had problems with my
> LX200 + Starry Night + ACP set-up. The telescope was properly
> aligned at start-up, pointing South, but then failed by a wide margin
> to find the Moon. Experiments revealed that it was an hour "late",
> so was looking too far West. I checked all the telescope clock
> settings, location etc., all were correct. On connecting to Starry
> Night, through ACP, the cursor pointed at the Moon, Mars or
> whatever, but the scope did not. Starry Night and ACP location and
> time settings were also checked and found to be correct.
> Eventually I set the 'scope to a -1Hr offset to GMT, and all was well.
> We are located about 18 Miles West of the Greenwich Meridian,
> and Daylight Saving is in force. Should all three components of my
> set-up acknowledge that fact, or should I, for example, set only the
> 'scope to Local Time, and the other components to GMT? Are their
> respective offsets additive? What could explain the extra 1-hour
> error? I don't think that it has happened before.
>
> Tonyk

View index by [date] [author] [subject]
Previous message: [M]: Re: Meade Piggyback #5940, La Pointe
Next message: Re: [M]: Software Recommendation, please..., g. n. paleologopoulos
Next message in thread: Re: [M]: Re: Clock Setting of LX200, Bob Denny
Previous message in thread: [M]: Re: Clock Setting of LX200, Email address hidden