Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is my PXI 6608 Frequency measurment too high?

I'm using a new PXI 6608 to measure the clock frequency on a board. The expected frequency is 1.05MHz and I am consistantly measuring 27Hz too high. Using less accurate instruments, I have verified that the clock speed is within 3 Hz of the specified 1.05MHz, so the 6608 is indeed counting wrong. I am using one counter to gate another and counting pulses during said time. I am following the tutorial: http://zone.ni.com/devzone/conceptd.nsf/webmain/CD2C8AAED8FA59A486256C230078FE75?opendocument
and using the LabVIEW vi's downloaded from: http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E61756A4E034080020E74861&p_node=DZ52329&p_submitted=&p_rank=&p_answer=&p_source=External

There are 3
vi's here and I am using 'Frequency using two 6608 counters.vi' The front panel configuration is shown in the attached jpg file.

One thought is that I may be getting ringing in the line where the coax is terminated in the terminal block. Is there a method to adjust the threshold? Am I just really doing something wrong?

Thanks for any suggestions.
-Keith
0 Kudos
Message 1 of 5
(3,836 Views)
Unfortunately I'm on an assignment away from any LabVIEW terminal and can't look at the code. Based on the screenshot, it appears you're using the so-called 'Method 2' where you count cycles of your test signal during a known time interval.

The first thing I'd generally investigate is quantization error, though I have my doubts in this particular case. First of all, you describe a consistent bias in your result where quantization would typically dither on two values surrounding the correct one. Also, the size of the error (about 1 part in 39000) doesn't really correspond to a typical measurement duration. Nonetheless, I'll pose a couple questions and we'll see if we can get anywhere...

What is the duration of the time interval you use to gate the cy
cle counting you do? (Likely equal to the pulse width of the gating pulse. To explain a 27 Hz error on a 1.05 MHz signal, it'd require a pulse width of 0.037 sec.) How does the measurement error vary when you change this interval?
Have you tried using the referenced 'Method 3" yet? What dividers have you tried? How does the error vary when you change the divider?

Finally, is there a chance that the 6608 actually is mroe accurate than your other devices?
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 2 of 5
(3,835 Views)
Thanks for the advice Kevin. The duration of the time interval varies between 2 seconds (for an accuracy of 0.5Hz to 10 seconds (for an accuracy of 0.1Hz). The downloaded vi makes this time interval calculation for you depending on how much error you can accept. I was trying method 2, but on your advice tried method 3 and received the same results. The quantization error is small as we are taking between 2 and 5 million samples. It has been suggested that the error comes from noise generated by ringing. I'm not sure I buy into this giving a reliable 28 extra spikes every million samples. At this point, I am trying to get an independent measurement to compare the results with. I am still curious about what the voltage threshold is for the 66
0x to count a pulse. Thanks.
0 Kudos
Message 3 of 5
(3,835 Views)
You can eliminate the possibility of noise by using the built-in digital filters on the 6608. There is a shipping example "Count Edges - Digital Filter (NI-TIO).vi" that shows how to turn on digital filters for a particular PFI line.

gus
0 Kudos
Message 4 of 5
(3,835 Views)
Keith,

Did you try Gus' suggestion of enabling the digital filtering on the 6608? Did this solve the problem?

Ames
Applications Engineering
National Instruments
0 Kudos
Message 5 of 5
(3,835 Views)