One of the biggest problems encountered by beginners in LabVIEW is that they use the Dreaded DAQ Assistant, and its Evil Twin, the Dynamic Data Wire. Look at the first function you have on the DDW -- do you know what it does? It basically throws away the time information that you are so desperate to put back in!
It is so much easier to learn proper DAQmx usage (starting with getting familiar with your Device using MAX, creating a Task in MAX, and then wiring up at most 4 DAQmx functions that "do what you want", and preserve the data as either an Array of Waveforms (which include the starting time, t0, and the time between samples, dt, as part of a Cluster) (it's an Array if you have multiple channels, one Waveform per channel) or as a 2D array of samples (for multiple channels, but you lose the time information this way).
If you are interested, do a Web search for "Learn 10 Functions in NI-DAQmx and Handlee 80 Percent of your Data Acquisition Applications", get rid of the DAQ Assistant, and get rid of the Dynamic Data Wires (please!).
Bob Schor
P.S. -- I just noticed the "Wait (ms)" function inside of your DAQ loop, which means you really do not understand the ideas of Data Acquisition and sampling. You also attached a picture instead of a VI, so I can't "poke around in your code" to really see what you are trying to do. Read the paper I cited above, learn how DAQ works, and let your hardware time your acquisition loops (the clock in DAQ hardware is usually much better than the msec clock in your PC -- no Windows updates, no virus checks, nothing else trying to use CPU cycles and mess up the timing ...).
