Programs running ~30 secs before clock hits run time

[johnnyt]

Was debugging something and noticed programs were executing almost 30 secs ahead of the clock in the GUI. The "last run time" would update to the expected new run time, e.g. 5:30:00 PM but the clock at the top left of the console was at about 5:29:34 or something like that when the "last run time" was updated.

 

I tried a manual time sync and it didn't change the time, and there's no indication the automatic syncs aren't working (every 6 hours in my case). I did notice the GUI is a few seconds ahead of my PC clock.

 

In this case the GUI had been running about 30 minutes or so when I noticed this, so if it gets it's time from either the PC or ISY at startup, it certainly loses track of it quickly.

 

Any idea what's going on?

 

Edit: am running ISY 3.1.11, Java 1.6 update 29, W7

[LeeG]

Michel posted on this subject before. I'll update with the link when I find it.

 

Syncing the clock relates to syncing the ISY not the Admin Console. Exit the Admin Console and reinvoke to bring the times together. From memory I think Michel indicated the Admin Console can be up to 8 minutes out of sync with the ISY itself if the Admin Console remains running for a long period of time.

 

EDIT:

 

sorry it is 5 minutes. See this link.. viewtopic.php?f=27&t=6915&hilit=sync+time

[matapan]

Doesn't the ISY sync its time to a NTP server? I think my Mac and most Windows machines now have the same capability. So, theoretically, the time wouldn't be that far off, would it?

[LeeG]

It is not the ISY time that is "off". It is the time the Admin Console is keeping separate from the ISY. Refer to the link I posted earlier with Michel explanation..

[Michel Kohanim]

LeeG, thanks so very much! You are 100% correct.

johnnyt, there's a bug in 3.1.x where the time in the Admin Console does not get updated properly. The issue is in the Admin Console and not ISY.

 

With kind regards,

Michel