6053Re: Console and PC time
- Apr 6 6:01 AMThis is the error message I get in the WUHU log
Fri Apr 06 07:49:56 2007 > Failed to retrieve weather data from console.
Possible invalid/corrupt data detected. Verify that the console's clock
and the PC's clock are set to within 30 seconds of each other
My console does not seem to be updating the time and I have it set to
receive the WWVB signal.
--- In email@example.com, "plasmaboy3" <pjweix@...>
> Quite often I will get an error message in the log that says the two
> clocks are not within 30seconds of each other and today it stopped
> communicating with the console and uploading data.
> What does the 30 seconds of the clocks being so close have to do with
> anything of communicating between the PC and the console?
> --- In firstname.lastname@example.org, "wuhu_software"
> wuhu_software@ wrote:
> > Pete,
> > The clock on my console should not drift much once you have it set
> > correctly. My console can stay within a minute or two over a several
> > month period.
> > The reason it is important to keep the clocks in sync (for the
> > consoles anyway), is because the console will attempt to receive thethe
> > WWVB radio signal from 12am to 7am. When it is attempting to aquire
> > radio signal, the console will refuse to communication for a few
> > minutes.
> > When the clocks are set closely, WUHU will detect that the time sync
> > in progress and will not generate console communication errors in
> > log.to
> > Other than that, the clock on the console is not used.
> > --- In email@example.com, "plasmaboy3" pjweix@
> > wrote:
> > >
> > > Why is it so important to have the console time and the PC time
> > > 30 seconds of each other? I am using a time synchronizing program
> > > keep my PC synced to the world time servers but my console doesn'tin
> > > seem to be receiving the WWVB clock signal. It always lags behind
> > time.
> > >
> > > Pete
> > >
- << Previous post in topic Next post in topic >>