From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Digitizer Sample Rate Values

Hello,

 

    I'm trying to determine the proper value if samples to take to properly acquire a measurement via the digitizer. 

 

A little background: I'm developing a VI that measures THD on an amplifier. I'm putting in a quick 20 cycle (+/- ramp cycles) burst into an amplifier. So I need the digitizer to skip the first few cycles and only take measurements on the middle 10 cycles. My arb waveform generator and digitizer are both sync'd with an external clock, but I'm getting some weird numbers and need to tweak either the number of samples the digitizer takes, or possibly where the digitizer is taking the measurement. There's a wide range of frequencies that I'm measuring, say 50Hz up to 500kHz, so the digitizer needs to adapt to the frequency. 

 

I've attached my code and the measurements take place in the ADV SHELL.vi, in the  ADV GO.vi. I think what might need to be adjusted is the Num Samples value as seen in the image below. (Found in the ADV GO.vi)  Any help would be appreciated!

 

JayWW_0-1652460577945.png

 

0 Kudos
Message 1 of 5
(848 Views)

Are you using NI boards?

0 Kudos
Message 2 of 5
(811 Views)

Hello,

 

    Yes. My clock signal is supplied by a PXI-5404, the ARB signal is supplied by a PXI-5421 and the DIGI (used as a scope) is supplied by a PXI-5122.

 

Thanks, 

Jay

0 Kudos
Message 3 of 5
(788 Views)

I don't know if this is a programming issue or a LabVIEW issue.

 

There is also a forum devoted to DAQ https://forums.ni.com/t5/Multifunction-DAQ/bd-p/250

Message 4 of 5
(769 Views)

Thanks for the info. I think I've figured out the issue. The digitizer was losing it's hardware label after the first iteration after initialization. I passed everything through a shift register and now it seems to be working. 

 

 

--Jay 

0 Kudos
Message 5 of 5
(754 Views)