Thanks Rune. I did not understand the relationship between device cals and nvna-s cals.
toggle quoted message
Show quoted text
Please allow me to check my understanding. Let's say I want to measure a ferrite choke from 1 to 50MHz. I set up the cables and do a device cal over that frequency range using an appropriate cal kit. I save that cal to say C0. With C0 selected on the device, I repeat the cal on nvna-s using the same frequency range, same cables, same cal kit and save it to cal_0.cal. I can then measure my choke over the same frequency range using nvna-s with as many data points as I like using multiple segments. Let's say I then want to measure a UHF filter over the range 100MHz to 900MHz. Obviously I cannot use C0 and cal_0.cal. So I set up with different cables and a different cal kit. I do a device cal over that frequency range and save it to C1. With C1 selected on the device, I repeat the cal on nvna-s using the same frequency range, same cables, same cal kit and save it to cal_1.cal.. I can then measure my filter over the same frequency range using nvna-s with as many data points as I like using multiple segments and save the results to s*p files. What if I then want to measure the filter over a restricted frequency range, say 400 to 500MHz? Or a VHF filter with the same the cables and connectors from 100MHz to 200MHz? Do I need a new pair of cals in either of these cases? (I would say not.) Is it possible for nvna-s to detect what cal the device is set to i.e. C0 through C4, tell the user and set the correct scan range? If nvna-s could read raw data from an uncalibrated nvna would that mean that all cals for fixed bench work could be performed by, and saved in, nvna-s if the user so wished? Obviously for portable use the device cals are the only ones available. On Fri, Nov 8, 2019 at 11:46 AM, Rune Broberg wrote:
by same I mean the *same*. The NanoVNA-Saver calibration is *not* |