Sounds plausible to me. I have done it hundreds of times, tuning my
2m/70cm antennas before shipping. Every time I run the 420-450 scan, I
have to reboot the VNA to get accurate readings on the next scan in the
test set. Upgraded the firmware and upgraded saver, I have three versions
of saver, including the latest, and they all suffer from it when running
NanoVNA Saver. Also, does not matter what firmware I am running, be it
from Dislord, BN5HNU, or edy555. However, I do not see the problem when
running Nanovna Software based on edy555's version. But it is not pretty,
nor does it show the data in quite the same way.
Jim Barber
*N7FZ*
Phone: 503.547.9524
<>
toggle quoted message
Show quoted text
On Mon, Dec 12, 2022 at 2:03 PM Jim Lux <jimlux@...> wrote:
On 12/12/22 1:53 PM, Jim Barber wrote:
Good afternoon,
I have had the same experience. I have t to calibrate and save the
calibration for the exact width I am looking for to one of the memories.
Then, after scanning with one of the calibrations, save those results.
Then, disconnect the saver, reboot, and manually load the other
calibration. Reconnect. For some reason, the back-to-back scan results
get
wonky without a reboot on the higher frequencies. I never have this
problem
below ~200mhz.
I wonder if it's the result of an inconsistency in how the multiple
sweep ranges interact with the discontinuity when stepping across the
harmonic boundary. Both NanoVNA and NanoVNA-Saver do linear
interpolation of the calibration coefficients. If the "threshold" is 300
MHz, and you have a sweep that spans 300 MHz (e.g. from 290-310) there
might be some wonkiness.
