Fastcounter elapsed time

[simonschmitt2]

What is affected by this bug?

Getting the elapsed time from the fast counter can return misleading information. The pulsed measurement starts after the pulser is turned on and not when the fast counter is turned on. So the measurement duration is the time given from the fast counter minus the time needed to turn on the pulser. Since this might take very long (for AWG70k up to several minutes for long waveforms for example), taking the elapsed time from the fast counter is not always a good choice.

When does this occur?

How do we replicate the issue?

Expected behavior (i.e. solution)

To fix that one possible option is to measure the time the pulser needs to turn on and then subtract this duration from the time given by the fast counter. Maybe even better would be to calculate the elapsed time using the elapsed sweeps and the duration of a single sweep...

Other Comments