My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 11: Internal clock and realtime clock are significantly out of sync
1 person starred this issue and may be notified of changes. Back to list
Status:  WontFix
Owner:  nali...@gmail.com
Closed:  Feb 2010
Cc:  nali...@gmail.com


 
Project Member Reported by fuka2@fuxoft.cz, Feb 6, 2010
Checkout and run r38.

Watch Lua log.

It displays the difference (in seconds) between realtime clock and realtime 
clock.

This difference increases by 1 second each 10 seconds, meaning the realtime 
clock is around 10% faster than internal clock.
Feb 6, 2010
Project Member #1 fuka2@fuxoft.cz
The last sentence should be:

This difference DECREASES by 1 second each 10 seconds, meaning the realtime 
clock is around 10% faster than internal clock.
Cc: -nalim68
Feb 7, 2010
Project Member #2 fuka2@fuxoft.cz
Checkout and run r44, watch Lua log.

The main clock routine is called using dynawa.timer.new(1000,true), i.e. each second.

In the log, you can see difference between simple counter (incremented each tick) and 
"seconds" value from realtime clock. The difference should ideally be constant.

But the difference decreases by one each 30 seconds, meaning the realtime clock is 
faster than the timer clock.
Cc: nalim68
Feb 8, 2010
Project Member #3 fuka2@fuxoft.cz
The timer used for dynawa.timer.new() signals is now more precise. The drift from RTC 
is about 2 seconds per minute.

The need for having access to exact time with smaller than 1-second resolution was 
addressed by implementing dynawa.time.get().
Status: WontFix

Powered by Google Project Hosting