Why is the DSM Hypertrend graph x axis is tied to windows system time not the timestamps of the data

[viScience]

I am using the 2009 Distributed System Manager to view logged cRIO NSV data.  I have gone to alot of trouble to

get the cRIO's sync'd to GPS time so that all of the data timestamps are accurate and correlated.  The problem is that

the Hypertrend display within the DSM does not use the cRIO timestamps to calculate the right hand end of the x-axis.

Windows system time is used and any since Windows does not sync to 1588 GPS time my viewing window within Hypertrend is never current to

the actual data timestamps.  Is there a way to fix this? 

[Hueter]

Could you please post some of your code or at least your datafile so we can see how you are reading it with the hypertrend VI?

[mdai]

The data points are logged in Citadel database with the RT system timestamp, but the Hypertrend window updates with Windows clock when auto plotting is on.  Considering you can actually view logged traces from different targets, so it's probably the best way it can do.

A little trick to make sure you see the latest logged data is to set your Windows clock a little ahead of the RT target, for example 1 minute.  In that case Hypertrend window will set the right limit of X axis to the latest data point as there is no data points from the "future".

Hoper this helps

[viScience]

I have found that the hypertrend graph still get confused when trying to display real time data.  For example on a windows machine generate a sine wave and publish it to a NSV that is being logged to citadel.  On the same machine open up the DSM or any hypertrend vehicle and observe weird trace artifacts if you are displaying at the current system time on the x axis.  If you just click anywhere on the graph the traces redraw and seems to know how to properly connect the dots.  Why don't you just do the same in the hypertrend code and put to an end this embarrassing bug.