Hi Rune,
Again, I would like it very much when "uncalibrated" or? the description of the active calibration-file is shown in the MAIN window, to avoid confusion while working.
Jos
Op 25-11-2019 om 09:26 schreef Rune Broberg:
toggle quoted message
Show quoted text
Hello DE8MSH,
Thank you for your comments and your suggestions!
Currently, NanoVNA-Saver has no interaction with the calibration on the
NanoVNA itself. The application assumes that you have a calibration on the
NanoVNA covering at least the span of frequencies read - in order to put
the readings in the expected span of values, or at least close to that span.
The calibration you can do in NanoVNA-Saver is a further calibration to
refine the accuracy and to allow more than 101 data points, and it is not
saved on the NanoVNA, but it is possible to save it as files (I use the
extension ".cal").
The NanoVNA firmware does not offer a way to write calibration data to it.
It does allow triggering the short/open/load/isolation/through functions
for calibration on the device, but this is not currently utilized by
NanoVNA-Saver.
I am looking into running the NanoVNA in uncalibrated mode, and purely
handling the calibration in NanoVNA-Saver, in order to save the step of
calibrating the NanoVNA itself for those users who purely use it when
connected to a computer.
NanoVNA-Saver does not currently load the previous calibration. This is a
deliberate design choice, as the calibration is heavily dependent on what
cables, connectors etc. are used with the NanoVNA, and I would rather not
load any calibration than load a wrong calibration and display completely
erroneous data. So currently, NanoVNA-Saver by default shows the same data
as is displayed on the NanoVNA itself.
I hope these comments explain some of the reasons why things currently are
as they are. :-)
