Beware of cheap underperforming clones

As of 2023 there are many badly performing clones on the market. V2/3GHz NanoVNA uses parts like ADF4350 and AD8342 which are costly and clones have been cutting costs by using salvaged or reject parts.

See official store and look for V2 Plus4/V2 Plus4 Pro versions only to avoid getting a bad clone. We have stopped selling V2.2 versions since October 2020, so all V2 hardware that are not Plus or Plus4 are not made by us and we can not guarantee performance.

NanoVNA V2 Forum

Note: this page is a mirror of https://groups.io/g/NanoVNAV2.
Click here to join and see most recent posts.

factory calibartion?


hb9 iiu 2024/05/12 00:09

Hello,

I've encountered a peculiar issue with my V2 Plus4. I've been using it within a Python application, gathering raw uncalibrated values with the skrf.vi.vna.NanoVNAv2 class, and everything has been functioning smoothly so far. However, when I use it directly with NanoVNA Saver on Linux, I'm now compelled to calibrate each time within the application, or else I receive entirely inaccurate measurements.

My question is, are there (or were there) any factory calibration networks saved somewhere within the device?

I've never had to do this in the past (though I'm aware that it's always better to calibrate).

Thank you, and
73! de HB9IIU

nanov2support 2024/05/23 23:00

Hi, it is always necessary to calibrate before making measurements, but you can store the calibration in a file in your program. The factory calibration only makes minor adjustments to device parameters and isn't a substitute for user calibration, which needs to be done with external Short, Open, and Load standards.
Thanks,
NanoRFE Support

To reply to this topic, join https://groups.io/g/NanoVNAV2

View this thread on groups.io