On Sat, Apr 26, 2025 at 10:39 AM, Dean W8ZF wrote:
because MAYBE it depends on the H4's cal state
From the nanovna-saver github readme ():
Quote:
Calibration
Before using NanoVNA-Saver, please ensure that the device itself is in a reasonable calibration state.
A calibration of both ports across the entire frequency span, saved to save slot 0, is sufficient. If the NanoVNA is completely uncalibrated, its readings may be outside the range accepted by the application.
-------------
And from the code itself, the following code fragment shows that nanovna-saver uses the "scan" command, rather than the "scanraw" command, to get its data from nanovna. The "scan" command returns S11/S12 data with nanovna internal calibration (if any) applied.
def setSweep(self, start, stop):
self.start = start
self.stop = stop
list(self.exec_command(f"scan {start} {stop} {self.datapoints}"))
-------------
So nanovna-saver indeed does depend on the calibration state of the nanovna; they are not independent.
Q.E.D.
If you want independent calibration, use nanovna-app instead. It is a quite different application with its own learning curve, but it has specific settings to use the nanovna internal or nanovna-app calibration. I use both apps, they both have excellent features.
Stan KC7XE
