You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SCOPE: Use precise timestamp per TP for tpInput data
In our TP data we used until now only simply DateTime of the moment the
data was sent into analysis for the timestamp. This resulted in multiple
TPs (all from the same new FIFO data) having nearly the same timestamp.
Now the timestamp of each TP based on the acquisition start and TP
position in the acquisition is determined.
Note regarding the calculation:
(tpCounter + i) * tpInput.samplingIntervalDAC * tpInput.tpLengthPointsDAC * MILLI_TO_ONE
tpCounter originates from NI devices in TP acquisition mode.
There the acquisition with a single TP repeats itself in hardware.
The TPs are counted based on the FIFO data and each TP is sent to
SCOPE_UpdateOscilloscopeData separately. Thus, i is always zero and
tpCounter the number of the TP since acquisition start.
For all other hardware devices and acquisition modes tpCounter is zero and
i counts the absolute TP number based on the position of the data in the FIFO.
0 commit comments