Page 1 of 2

Losing Time

Posted: Wed Aug 30, 2006 12:06 am
by Osler
I just created a task built on If/Or statements that checks the system time every hour from 8am to 10pm to set a script state to "running". Since creating this task, HB is losing time. I started the task at 11am today and currently it has lost over an hour compared to the true time displayed on the computer (HB displays 9:41pm, computer displays 11:04pm). Any ideas on a work-around?

Osler

Losing Time

Posted: Wed Aug 30, 2006 6:39 am
by dozinjp
Hello, I have never had this problem, However I have several task which executes scripts just in time.
Could you post an export of your task, it could certainly help has the resolution of your problem.

Thank you in advance
Ethan

Posted: Wed Aug 30, 2006 8:58 am
by ScottBot
So are you saying that the System Time Device is not showing the correct time? If so, double check to make sure it is still enabled. That device gets the time from the PC twice a second, so I'm not sure how it could get out of sync. It even has special measures for the odd case where it gets behind (heavy CPU load or time change).

Posted: Wed Aug 30, 2006 5:09 pm
by Osler
Yes, it gets behind the CPU clock. The time device is enabled. I will try to get more details this evening when I get home.

Osler

Posted: Wed Aug 30, 2006 9:30 pm
by Osler
Hmmm....seems to be keeping time ok since the restart of HB last night. I will keep an eye on it and see if this recurs.

Osler

Posted: Fri Sep 01, 2006 11:35 pm
by markd
Mine is drifting too.

Reporting 11:25, real time is 11:41.

Is there anything useful I can check? I won't restart yet.

Markd

Posted: Mon Sep 04, 2006 4:14 pm
by ScottBot
Can you send me a screen-shot of the System Time Device showing all of it's properties and values and the system clock on the same screen? It's not that I don't believe you, but there may be something with the other properties that may give me a clue.

Also, send me a screen shot of the 'history' tab of the System Time.Time property.

Posted: Tue Sep 05, 2006 8:17 am
by markd
Funny, I almost took that shot. (The first one) Unfortunately, I have since restarted (a couple of times) and last time I checked, the systime was ok. I'll keep an eye on it, see if it gets out of sync again. I'm playing with the system daily right now, so if it is repeatable, I should catch it.

The system had not been running too long, day or two. And I had been doing a lot of editting and playing with scripts. But then I have the last couple of days too, and no problems sice, so who knows???

Thanks

Markd

Posted: Tue Sep 19, 2006 12:22 am
by Osler
Scott:

I caught the problem on-screen. It is with the 'Time Without Seconds' value. See attached screen shots.

Image

Image

Osler

Posted: Tue Sep 19, 2006 12:29 am
by Osler
Nearly 10 minutes behind for all properties here.

Image

Image

Osler

Posted: Tue Sep 19, 2006 9:04 am
by ScottBot
Is there much load on this machine? Does it ever run anything that is very CPU intensive?

I found one minor issue that may somehow be effecting things, but I'm not convinced that it is causing the problem. However, please download, unzip, and copy this new System Time plugin into your \HouseBot\Plugins\Devices directory over the old one (you should probably backup the old one first). Let me know if you continue to see the problem with it.

Posted: Tue Sep 19, 2006 11:48 am
by Osler
The PC is Shuttle (AMD 64 3200+, 512 MB RAM) whose sole purpose is to run HouseBot and act as a media storage area (600 GB). The only thing ever up and running is HB.

I will do the install this evening when I get home.

None of my time-based tasks are executing at all right now.

Osler

Posted: Tue Sep 19, 2006 4:27 pm
by Osler
A temporary fix for this problem can be downloaded from here:

http://home.comcast.net/~jpbrowning2/Ho ... _Clock.zip


Osler

Posted: Tue Sep 19, 2006 7:20 pm
by Osler
Newer .dll installed and waiting. I will keep you updated.

Osler

Posted: Wed Sep 20, 2006 11:31 pm
by Osler
Still stable. I will migrate my tasks back to the SystemTimeDevice tomorrow and see if the problem develops.

Osler