it seems that the embedded data logger does not record gaps when the log trigger is triggered multiple times when recording on the same file.
Is mine a correct assumption? I tried viewing the excel export and the TDMS viewer output and there is no trace of the "missing" data.
If I try recording 10 minutes and strop the log for 2 minutes I get a solid file which shows 8 minutes of recording with no gaps. Does the TDMS format support gaps such that a custom TDMS exctraction tool can show the gaps (implying a limit on the TDMS viewer that ship with VeriStand 2011)?
System time seems to be relative.
We are now running a model that return the RT system clock time and translate it to an excel datetime float64, plotted data shows the gap and makes life easier to go on and spot the correct data when post analyzing long test sessions.