LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to place time stamps without creating delays?

I tried placing the Waveform Array Indicator but unfortunately it didn't give any new information, delta t was still listed as 0. My data is coming from an optical encoder and thus is determined by the motion of the system, there is no constant delta t between the arrival of data bits.

It is precisely because my data is coming in at non-equal intervals that the time-stamp is so important.

It is possible that some of the data points could come in faster than a ms but then I would just expect the same time stamp to be placed on two adjacent data points if labview could not distinguish between them.

However,  for the purposes of testing and getting things running the signals have been coming in at around 100-300Hz which should not pose a problem.

I am a little bewildered, any ideas?

Harry

 

 

0 Kudos
Message 11 of 12
(581 Views)
If you are using the VI you posted a JPG of earlier, then you are not collecting a record of timestamps for each point.  The code assumes some sort of regular timing when you specify an external clock - and it does not know what this timing is.  The only timestamp you will get is for the first point.  When you collect data, you need to collect some sort of timestamp at the same time.  As I mentioned earlier, you may be able to do this by simultaneously collecting a counter value, which you can then convert to a timestamp, knowing the counter interval and the initial timestamp.  Unfortunately, E-series DAQ boards were not designed for single-point acquisitions like this, so making it work is not trivial.  I would suggest using one of the DAQ board clocks as a timer and reading it with one of the DAQ counters.  Simultaneously acquire both the analog and counter data and you should be good to go, with a bit of math on the counter data.

Note that the resolution of the timestamp data type is about 5x10-20 seconds, so the data type itself is not an issue.  Getting that much accuracy in your actual data is another matter, as mentioned earlier.
Message 12 of 12
(570 Views)