I agree, I look at changes I make as "WHAT IF" that way, I don't mess
things up. However, when a good thing happens, I always recal.........Then
save with new name.
Mel, K6KBE
On Fri, Oct 18, 2019 at 11:27 AM Maurizio IZ1MDJ <redifon500@...>
wrote:
Hi Nick , my suggestion is that the " save calibration " , save also the
state of the instruments , like all the vna i know.
If you , change some sweep parameter with the calibration applied , it's
ok to put a warning at the operator that the currently calibration may be
not valid.
Sincerely I don't understand what is the convenience to mantain sweep
setup that my be not agree with the calibration.
Of course this is my opinion.
Best Regards
Maurizio IZ1MDJ
On Fri, Oct 18, 2019 at 03:39 PM, Nick wrote:
Hi Rune
I would not expect measurements made outside of the frequency range of
the
current calibration to be "accurate".
I would not want nvna-s to change the sweep setup when a calibration is
loaded. But I might expect to be reminded.
Having loaded a calibration how about warning the user if they try to
make
measurements outside the calibrated frequency range?
e.g. by flashing up an out of calibration message box, watermarking the
plots
etc.
73
Nick
On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:
I agree that calibrations should save the
start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever
frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?
