[time-nuts] 53132A counter slow frequency update

Rick Karlquist richard at karlquist.com
Tue Jun 28 18:13:40 UTC 2011

Do you have the autotrigger (or whatever it is called) engaged?
That will slow things down if it is hunting for the zero crossing.


John Pease wrote:
> Hello,
> My new to me counter has a strange response when I change the input
> frequency. With the gate set to 1s, I can measure 100 MHz with plenty of
> digits. Then I change the frequency to 1 MHz and it takes several seconds
> to almost a minute for the display to change from 100 MHz to 1 MHz. The
> delay only occurs when I lower the input frequency quite a bit; 100 MHz to
> 10 MHz changes are displayed within 2 gate times. When I increase the
> frequency form 1 MHz to 100 MHz I always get the correct display after two
> gate times. This delay is proportional to the gate time; the updating is
> 10 times faster with 0.1 s gate time.
> Is this behavior typical for this counter?
> Thank you
> John Pease
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

More information about the time-nuts mailing list