Skip to content

Save precise start times per TP #2408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

MichaelHuth
Copy link
Collaborator

close #336

The time is saved as global string as ISO8601 timestamp.

The specialized HW_XX_StartAcq have been made static and the calling locations
adapted to use the public HW_StartAcq function.
@MichaelHuth MichaelHuth self-assigned this Apr 25, 2025
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TP results plotting looks different for TP during DAQ and TP during ITI
1 participant