Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

On XP Machine dedicated to Lookout 6.5. The Hypertrends are not moving at proper pace according to the scale at the bottom of the trend graph. After 60 seconds it is 40 seconds behind, so the trace makes up the time with a straight line an repeats.

On XP Machine dedicated to Lookout 6.5.  The Hypertrends are not moving at proper pace according to the scale at the bottom of the trend graph.  After 60 seconds it is 40 seconds behind, so the trace makes up the time with a straight line and then repeats.  Even without any traces on the graph, it does the same thing.

 

I've uninstalled and reinstalled the 6.5 software.  Nothing else runs on this machine.  It is dedicated to Lookout.  I've installed a gauge object, with the same datapoint that the hypertrend is trying to graph, that updates very rapidly with no problem, so doesn't appear to be a network problem.

 

I'm only tracking one datapoint, at this time, until this issue is solved.  Help please?

0 Kudos
Message 1 of 11
(6,696 Views)

Here is the screen shot.

 

Definitions for this post:

 - "streaming data" = Data coming in over ethernet from datapoint that is being polled.

 - "1 scale-second" = 1 second of time based on the scale on the bottom of the graph

 

Remember that data continues to trace.  However, according to the scale at the bottom of the graph, the graph traces 60 seconds of streaming data in @10 scale-seconds, then displays .01 second of streaming data over 50 scale-seconds.  The .01 second of data is the long straight lines that you see between the rapid data traces that appear to be 50 scale-seconds.

 

Even without any datapoints being traced, the graph clicks forward 1 scale-second every 6 real-time seconds.  It does this for @10 seconds then clicks forward  @50 scale seconds, instantly.  Then repeats, as you can see in the graph.

 

The gauge that is on the same control panel, that you see in the screen shot, is tracking the same data point as the graph.  It is polling the data point at real time and never stops updating, so I know that the network is streaming just fine.

 

513.850.9509 - if I can help clear things up.

0 Kudos
Message 3 of 11
(6,672 Views)

Ryan,

 

If we don't have an answer for this, will you help me get authorization to install the software on another machine?  How does Lookout run on Windows7?

 

Thanks,

 

MK

0 Kudos
Message 4 of 11
(6,650 Views)

Can you send me your lookout process file? ryan.shi@ni.com

Which driver do you use? How is the streaming data being sent to lookout? It looks like the streaming data doesn't come in at real time.

 

If you log the gauge, and display it on hypertrend, do you see the problem? If you don't see the hypertrend display problem with the gauge, I don't think it's computer's issue.

 

Anyway, you can call customer service for switching the lookout to another computer.

 

 

Ryan Shi
National Instruments
0 Kudos
Message 5 of 11
(6,639 Views)

OK.  I'll get with customer service.  I've been using LookoutDirect/Lookout for at least 6 years.  We've had many issues, but this one is new.

 

Yes.  If the hypertrend is tied to the gauge, it will do the same thing.  Gauge is polling real time and updating like crazy.

 

As I indicated earlier in this thread, even if I don't add any traces/items to the hypertrend, it still behaves the same way.  The trend moves along at a 1 to 6 ratio, according to the scale.  Then it will bump ahead 50 seconds on the scale in a split-second to catch up.  Thus the long straight line.  It's bringing in all the data for 60 seconds withinin a 10 second scale segment.  All the data is coming into the hypertrend, it's just not scaled correctly in respect to time.

 

Like I said, hard to explain via text.  If I can help explain, feel free to call me at 513.850.9509.

 

OK........WAIT........EXPLAIN THIS ONE - I WALK OVER TO THE LOOKOUT COMPUTER TO PUT THE DATAFILE ON A USB THEN ATTACH IT TO THIS THREAD REPLY, AS REQUESTED BY YOU.  I PLUG THE GENERIC FLASH DRIVE INTO THE USB AND THE HYPERTREND STARTS WORKING CORRECTLY.  I UNPLUG THE USB AND THE HYPERTREND SLOWS DOWN AGAIN.  IT IS REPEATABLE!  DO YOU HAVE AN EXPLANATION FOR THAT???  WIERD.

 

Thanks, Ryan.

 

 

0 Kudos
Message 6 of 11
(6,634 Views)

Is there a "save to usb" option in Lookout?  Is Lookout looking for USB storage to store the hypertrend data?  If USB storage is not available, it slows down?

 

I don't know.  Just trying to guess here.

 

MK

0 Kudos
Message 7 of 11
(6,632 Views)

Smiley Surprised

 

It's weird. Looks like the USB affects a "clock". Lookout doesn't use USB or save data to USB.

 

When the lookout is running, go to Control Panel->administrative Tools->Services, Stop the National Instrument Time Synchronization. See if anything changed.

 

 

 

Ryan Shi
National Instruments
0 Kudos
Message 8 of 11
(6,615 Views)

Stopping the NI time sync service has seemed to work.  I'll try it for a few days.  Reboot, restart, etc.

 

What does the time sync do for me?  In other words, how will disabling this service impair our SCADA?  Is there a fix for this?

 

Another quick question:

     - When cut and pasting objects on the same panel, is there a way I can separate the objects, after pasting, and give them a different identity?  I need to create a grid of gauges on one panel.  I'd like to cut and paste all the gauges that I need, and then modify each gauge object properties to have each gauge display a different data point.  The way it works now is that I can cut and paste a bunch of guages, but if I change the properties of one, they all change.

 

Thanks, Ryan.

 

MK

0 Kudos
Message 9 of 11
(6,608 Views)

The time sync service is for synchronizing the local lookout time with remote time server. It's useful to sync the time between lookout server and clients.

 

If you don't set the time server in lookout, this service doesn't take effect. But it's just a workaround but not a solution. When lookout starts, this service will be started automatically. So you need to manually stop it every time lookout starts.

 

It looks like the problem is in the timing. For example, we had a issue with AMD CPU which caused the lookout time incorrect. This issue was resolved by an AMD fix.

Ryan Shi
National Instruments
0 Kudos
Message 10 of 11
(6,600 Views)