Time System Advanced Problem Unresolved

[Squire66]

Please see the link for a couple of screen shots. I need to know what the alarm is and why it is happenning.

https://homepage.usask.ca/~nmz027/

Background:
I am running Lookout 6.02, which is connected to a Modicon 984 plc. They are linked by a modbus connection.

Problem:
Randomly, I receive an error in Lookout " System time advanced 03:34:43.532 from 5/10/07 15:42:57 to 05/10/07 07:05:06." During this time Lookout is not recording any information (trend screens are blank). At the same time there is a "No communication response from Modbus secondary" alarm. Does anyone know what is causing the problem?

Some questions I have answered about this problem already:

Do you programmatically change the Lookout system time in your process? (No)

Do you set any Time Servers for your process? (No)

Perhaps it's also because of the Daylight Saving Time. (It is on but the clock does not automatically update. Plus this should only cause a problem twice a year, not 5 times a week).

Message Edited by Squire66 on 06-12-2007 01:39 PM

[Bob_L]

Squire66,

You wrote:

>Randomly, I receive an error in Lookout " System time advanced 03:34:43.532 from 5/10/07 15:42:57 to 05/10/07 >07:05:06."

The minimum advanced time is 1:11:33.626. All other examples are approx. multiples of that. ie 02:23, 03:34, 05:57.

Can't be coincidence.

Your profile doesn't show an E-mail address. I've got some questions on the .lks and .ini files that you may not wish to answer on the web for security or other reasons. Send me a contact address and/or phone number.

Bob

Message Edited by Bob_L on 06-12-2007 05:17 PM

[Ryan.S]

Are you using AMD 64 dual core?

There is a known issue with this processor.

[Squire66]

I think we have the problem figured out. It has to do with rebooting the computer. Seems to be a time correction or something on restart.

[Mike@DTSI]

please tell me about the amd dual core problem.  We use them

[Ryan.S]

We have got several issues about Lookout's timing.  Some of them use AMD 64*2 Dual Core processor. Lookout keeps reseting the clock and generating alarms. We are not 100% sure if it's the processor's issue, but at least two customers solved it by installing a processor's updates, called AMD Dual-Core Optimizer.

I have not been able to reproduce this issue, so just some information for you but not the official voice. 

[Bob_L]

Well it appears that a similar problem exists in ver 6.1. I don't get any alarm or error but the logged data is incorrectly time stamped which makes the hypertrend useless. I can see the Lookout time (lower left of screens) jump ahead 1 hr 11 sec. for a short duration (1-2 minutes) and then return to normal. I've seen it happen twice in succession for a total of 2 min 22 secs. and a few times directly to 2 hrs 22 secs ahead. Problem occurs more than once an hour.

Lookout 6.1 plus latest published patch

CPU is genuine Intel

OS Windows 2000 SP 4

W2K Daylight savings time patch applied.

Bob

Message Edited by Bob_L on 05-06-2008 08:22 PM