From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Hypertrend Delay Concern
AaronGesicki
Member
06-20-2001 09:31 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
We had a weather related power outage this morning. 30 seconds.
When I got the SCADA computer back up, running Lookout 4.5.1 Build 18, it
took 14 minutes for the Hypertrend panel to show data. The data gap was only
90 seconds.
Is it normal for the delay to be this long?
--
Aaron Gesicki
Sparta, Wisconsin
When I got the SCADA computer back up, running Lookout 4.5.1 Build 18, it
took 14 minutes for the Hypertrend panel to show data. The data gap was only
90 seconds.
Is it normal for the delay to be this long?
--
Aaron Gesicki
Sparta, Wisconsin
Greg Caesar
Member
06-20-2001 12:09 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Was this a one-time delay, or does this delay occur every time you launch Lookout? The reason I ask is because Logos, the protocol Lookout uses to read and write from the Citadel database, will automatically repair damaged databases if possible. It is possible that the database files were corrupted when power was lost, and the 14-minute delay occurred because logos was repairing the files in the background. This is a very powerful feature of the database.
Regards,
Greg Caesar
National Instruments,
Applications Engineer
Regards,
Greg Caesar
National Instruments,
Applications Engineer
06-20-2001 02:31 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Greg -
If I close Lookout, but leave the computer on, then reopen Lookout, the
hypertrend is there immediately.
If I Restart the computer, clicking the Lookout prompts to close when they
come up, then reopen Lookout after Windows has loaded, then the Hypertrend
comes up in about 15 seconds.
Does this mean that everything is working normally, and that what I saw this
morning is actually normal? By the way, while this delay was occurring,
there did not seem to be any outwardly noticeable computer activity.
Certainly the hard drive was not humming and clicking like it usually does
when something is happening.
--
Aaron Gesicki
Sparta, Wisconsin
"gsc" wrote in message
news:5065000000050000008A310000-991728092000@quiq.com...
> Was this a one-time delay, or doe
s this delay occur every time you
> launch Lookout? The reason I ask is because Logos, the protocol
> Lookout uses to read and write from the Citadel database, will
> automatically repair damaged databases if possible. It is possible
> that the database files were corrupted when power was lost, and the
> 14-minute delay occurred because logos was repairing the files in the
> background. This is a very powerful feature of the database.
>
> Regards,
> Greg Caesar
> National Instruments,
> Applications Engineer
If I close Lookout, but leave the computer on, then reopen Lookout, the
hypertrend is there immediately.
If I Restart the computer, clicking the Lookout prompts to close when they
come up, then reopen Lookout after Windows has loaded, then the Hypertrend
comes up in about 15 seconds.
Does this mean that everything is working normally, and that what I saw this
morning is actually normal? By the way, while this delay was occurring,
there did not seem to be any outwardly noticeable computer activity.
Certainly the hard drive was not humming and clicking like it usually does
when something is happening.
--
Aaron Gesicki
Sparta, Wisconsin
"gsc"
news:5065000000050000008A310000-991728092000@quiq.com...
> Was this a one-time delay, or doe
s this delay occur every time you
> launch Lookout? The reason I ask is because Logos, the protocol
> Lookout uses to read and write from the Citadel database, will
> automatically repair damaged databases if possible. It is possible
> that the database files were corrupted when power was lost, and the
> 14-minute delay occurred because logos was repairing the files in the
> background. This is a very powerful feature of the database.
>
> Regards,
> Greg Caesar
> National Instruments,
> Applications Engineer
