I have a NanoVNA H version 3.5 software 1.0.64, kernel 4.0.0
I need to check where the bump is. It does not happen always... When i see
it again, I will report.
All the best,
Victor
Op vr 29 jul. 2022 om 13:10 schreef Arie Kleingeld PA3A <pa3a@...>:
Which nano and which firmware?
Do different nano-types or firmware versions make a difference?
On my old nano (H3.2) I had a bump around 6 MHz, but it was a known errror.
Arie PA3A
Hello
I didn't understand the meaning of:
- Number of measurements to average
- Number to discard
- Common values ??are 3/0, 5/5, 9/4 and 25/6
1/ Could you explain to me what you understand about this subject?
I saw that these parameters were also used during the calibration.
During
the calibration sequence (short open load), some measurements are
marred by
a gross error (click). These errors, despite a 25/6 filtering, remain
present in the produced .cal file. There is nothing more unpleasant
than to
find, then, always in the same place, these errors in the normal
measurements using this .cal file
I have to go back, almost by hand, to the raw .cal file to correct its
errors. I detect errors with Excel and I correct them by doing a linear
extrapolation with the previous value and the next value. The result is
satisfying but not very effective.
My questions
-------------
2/ What is the nature of the current filtering algorithm that leaves so
much error
3/ Could this algorithm be improved?
4/ Has anyone ever come up with a spinner, to run on the raw .cal file;
to
correct these gross errors
73
--
F1AMM (Fran?ois)
