What am I doing wrong ? - get different frequency measurements when changing time base #86
-
|
I connected a Tek 10X probe to Haasoscope Pro calibration terminal marked 1Khz 2.5 volts. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments
-
|
To measure frequency correctly, a large number of cycles must be captured. This is why you see it get more accurate as the timebase is increased. It's not a "frequency counter", it is doing an FFT of the captured data and finding the main peak frequency. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks - that makes sense.
On Monday, February 23, 2026 at 07:53:49 PM PST, Andy ***@***.***> wrote:
To measure frequency correctly, a large number of cycles must be captured. This is why you see it get more accurate as the timebase is increased. It's not a "frequency counter", it is doing an FFT of the captured data and finding the main peak frequency.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
1. The period measurement also changes when the time base changes.
2. Where are screen shots stored on PC ?
On Monday, February 23, 2026 at 07:53:49 PM PST, Andy ***@***.***> wrote:
To measure frequency correctly, a large number of cycles must be captured. This is why you see it get more accurate as the timebase is increased. It's not a "frequency counter", it is doing an FFT of the captured data and finding the main peak frequency.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Would you consider adding a new measurement which calculates period the same way as old-fashioned analog [non FFT] scope as the time distance between zero crossings ?
Your response time sets a record in all support !
On Tuesday, February 24, 2026 at 06:23:25 AM PST, Andy ***@***.***> wrote:
- Yes, the period will just be 1/freq, so it changes as well, for the same reasons.
- Screenshots should be saved in the "current directory", which should be the directory you were in when you ran python, or the directory of the .exe if you ran from that. Check in HaasoscopePro/software/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
It helps that I only have a few hundred users worldwide. :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks - your future success will bring millions more.
On Tuesday, February 24, 2026 at 08:07:49 AM PST, Andy ***@***.***> wrote:
It helps that I only have a few hundred users worldwide. :)
New measurements are in the v32_test branch, if you want to try them out.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
To measure frequency correctly, a large number of cycles must be captured. This is why you see it get more accurate as the timebase is increased. It's not a "frequency counter", it is doing an FFT of the captured data and finding the main peak frequency.