@gludev wrote:
If I use digital IO as a trigger for my measurement the VertualBench report following trigger point: 'timestamp': (1433170387L, 0.199386852), 'T0': (-2082844800L, 0.0). Why is T0 negative?
You can call niVB_ConvertTimestampToValues to convert those values to more understandable formats. When you do that, does it make any more sense?
@gludev wrote:
The function niVB_MSO_ReadAnalogDigitalU64 takes uint64_t* digitalData as parameter. Which elements does digitalData have and at which positions?
From the C Reference Help.
Logic Analyzer Data
Logic analyzer reads returns parallel arrays of data and timing information. The logic analyzer data is represented as a 64-bit integer, with each logic analyzer line corresponding to each bit in the integer. If a line is disabled the value for its bits will always be 0. The logic analyzer timing array indicates the offset of the sample from the initialTimestamp. The units of the timing array are in sample periods. This can be retrieved by calling either niVB_MSO_QueryTiming or, if you have configured the digital timing to be separate from the analog timing, niVB_MSO_QueryAdvancedDigitalTiming. The initialTimestamp is represented as a timestamp.
Does that help?
------
Zach Hindes
NI R&D
