02-17-2009 02:32 PM
The new PC does use the AMD dual core processor that is talked about in another thread.
I have downloaded the AMD optimizer and installed it. The system time and date do not jump all over the place now.
However I do notice that the Lookout time changes at least one second before the computer time updates.
I have tried using the sychronization time that Lookout has but the same thing is happening with the time.
The trends are still showing extra traces, but I am back to one extra per trace.
Lookout updates are installed.
I have deleted the database again and created a new database again.
02-18-2009 01:17 AM
If the lookout time is keeping jumping, it looks like the issue in this KB.
http://digital.ni.com/public.nsf/allkb/230017406BDDAFF686256DF3006FD57A?OpenDocument
This problem about messed display on hypertrend is not in Citadel or hypertrend, but the time is incorrect.
After you install the AMD optimizer, do you still get lookout event that says "lookout time is set advanced by xxx"?
You can try to stop the time synchronization service. After you start Lookout, go to Control Panel->Administrative Tools->Services, stop "National Instruments Time Synchronization". This service is started automatically when you start lookout. However you can stop it after lookout is started. If you don't set any time synchronization in Lookout, this service can be stopped. I remember that the time jumping problem can be avoided with this service stopped. So, try to stop it and let's see if the lookout time goes to normal. With the time jumping, I'm not sure if the "horizontal lines" on hypertrend is caused by the jumping time or a bug in hypertrend.
02-20-2009 05:34 PM
Thanks to all. We have got all data back now.
The desktop had AMD dual core processor running. I installed the optimizer program and started it. Because Lookout had been running while the time and date in Lookout had been jumping forward 1-5 hrs and then back again the data was corrupt in the database.
I left Lookout running for a day trending data and once we had passed the time of the corrupt traces the trending went back to normal.
I still had problems recovering my old data. I had created a new database when we installed the new PC and I was using the archive function to try and transfer the data into my new database. I would get a message say transfer complete however no recovered data was ever transfered. (Lookout is always shutdown)
Today I changed Lookout so that Citadel database was looking at the "recovered database" and then saved and shutdown Lookout.
I then archived the last two weeks of data into the recovered database. Then I archived into my database backup.
Then into my regular database and changed Lookout back to looking at the "database".
All is good. Trends are back to normal.