Hello:
Question: How to reduce the minimum default aperture (?timeOut?) of 32msec to 16msec and to 8msec?
Connected the 1054 Frequency Counter to measure frequency from a programmable TTL signal generator, the UDB1005.
http://www.amazon.com/SainSmart-UDB1005S-Function-Generator-Frequency/dp/B00JTRFZB4
Running C++ on Open Suse Linux 13.2 x64, and the Phidgets "FrequencyCounter-simple.c" //FrequencyCounterTest.cpp
The example program tracks correctly the dial-in frequency in the sense that the aperture automatically tracks the lower frequencies by becoming longer to capture a longer period.
Here below are (abbreviated) results:
Attach handler ran!
PhidgetFrequencyCounter
Version: 101 SerialNumber: 427727
// Dial-in a decreasing frequency:
// 10-->9-->8-->7-->6-->5-->4-->3-->2-->1 [KHz] and
// 1000-->900-->800-->700-->600-->500-->400-->300-->200-->100 [Hz] and
// 100-->90-->80-->70-->60-->50-->40-->30-->20-->10 [Hz] and
// 10-->9-->8-->7-->6-->5-->4-->3-->2-->1 [Hz]
Count Event (0) - 320 counts in 32ms - 10003Hz
Count Event (0) - 288 counts in 32ms - 9000Hz
Count Event (0) - 256 counts in 32ms - 8000Hz
Count Event (0) - 225 counts in 32ms - 7001Hz
Count Event (0) - 192 counts in 32ms - 6002Hz
Count Event (0) - 160 counts in 32ms - 5003Hz
Count Event (0) - 128 counts in 32ms - 4003Hz
Count Event (0) - 96 counts in 32ms - 3000Hz
Count Event (0) - 64 counts in 32ms - 2000Hz
Count Event (0) - 32 counts in 32ms - 1000Hz
Count Event (0) - 29 counts in 32ms - 900Hz
Count Event (0) - 25 counts in 31ms - 800Hz
Count Event (0) - 23 counts in 33ms - 700Hz
Count Event (0) - 20 counts in 33ms - 600Hz
Count Event (0) - 16 counts in 32ms - 500Hz
Count Event (0) - 13 counts in 32ms - 400Hz
Count Event (0) - 9 counts in 30ms - 300Hz
Count Event (0) - 6 counts in 30ms - 200Hz
Count Event (0) - 4 counts in 40ms - 100Hz
Count Event (0) - 3 counts in 33ms - 90Hz
Count Event (0) - 2 counts in 25ms - 80Hz
Count Event (0) - 2 counts in 29ms - 70Hz
Count Event (0) - 1 counts in 17ms - 60Hz
Count Event (0) - 2 counts in 40ms - 50Hz
Count Event (0) - 2 counts in 50ms - 40Hz
Count Event (0) - 1 counts in 33ms - 30Hz
Count Event (0) - 1 counts in 50ms - 20Hz
Count Event (0) - 1 counts in 100ms - 10Hz
Count Event (0) - 1 counts in 111ms - 9Hz
Count Event (0) - 1 counts in 125ms - 8Hz
Count Event (0) - 1 counts in 143ms - 7Hz
Count Event (0) - 1 counts in 167ms - 6Hz
Count Event (0) - 1 counts in 200ms - 5Hz
Count Event (0) - 1 counts in 250ms - 4Hz
Count Event (0) - 1 counts in 333ms - 3Hz
Count Event (0) - 1 counts in 500ms - 2Hz
Count Event (0) - 1 counts in 1000ms - 1Hz
...
//Dial-in a frequency step:
//1KHz-->1Hz-->10KHz-->1Hz-->100KHz-->1Hz-->1MHz-->1Hz-->1KHz
Count Event (0) - 32 counts in 32ms - 1000Hz
Count Event (0) - 1 counts in 1000ms - 1Hz
Count Event (0) - 320 counts in 32ms - 10006Hz
Count Event (0) - 1 counts in 1000ms - 1Hz
Count Event (0) - 3201 counts in 32ms - 100000Hz
Count Event (0) - 1 counts in 1000ms - 1Hz
Count Event (0) - 32020 counts in 32ms - 1000000Hz
Count Event (0) - 1 counts in 1000ms - 1Hz
Count Event (0) - 32 counts in 32ms - 1000Hz
Closing
Would very much need to reduce the 32msec aperture to 8msec.
I do not need frequency readout smoothing(averaging).
For lower frequencies the example program increases the aperture in order to capture one longer period, this is fine.
For higher frequencies, the example program reduces the aperture down to 32msec, beyond which the aperture remains a constant 32msec.
At 1KHz I just need 1msec not 32msec.
My goal is to get as many frequency readings as possible, and live with the numeric jitter.
Need more data points and less numeric A/D precision.
The frequency I am monitoring varies from 0Hz to 300Hz max, in less than 1 minute.
The frequency variation is monotonic, decreasing (300Hz-->0Hz) or increasing (0Hz-->300Hz).
At 300Hz would like the aperture to adjust (decrease) to 4msec.
I could not locate the 32msec limit in the example program.
Please advise.
Thank you,
Dan