开云体育

More negative reviews than I would like to see and many of them appear pretty serious.

I asked this "US Ship" ebay seller straight up and he replied that yes, his NanoVNA has in fact a v3.4 PCB. I also asked this morning on a follow up message if he could post some pictures of the PCB

Thank you everybody who answered my question. I got the answer I wanted. 73/Torbjorn

Hi Kurt, That would be nice! My nanovna-h and the torque wrench are not shipped yet. At the flea market in Rosmalen (NL) I will look for leads (hope for Huber Suhner for reasonable prices) and

Hi, Interpolation problem not only nanovna exist. If you use nanovna saver 10 segment = 1010 points data. But another interpolation errors occured, because double calibration not ok. Nanovna saver

See Erik's msg # 10886 for why a 101 point calibration performed using a wide frequency span, may not be accurate when applied to a 101 point measurement in a different frequency span. - Herb

Greetings, Using the "NanoVNA-Saver" PC app to control my mid quality nanoVNA I spent considerable time testing the high impedance measurement accuracy. I had previously made up a variety of loads

Unless you understand why it should work you should always recalibrate when changing frequency span. Search the group for longer explanation In short. A linear interpolation in two dimensions between

Somewhat longer answer Calibration creates a set of known calibration data points. 101 in total Any frequency used during measurement that does not uses exactly one of these calibrated data points

Best is to ALWAYS calibrate the device for any measurement using exactly the same frequency span you are using in the measurement. Only when you know why it should work you are allowed to use a

Ok, I am still on a steep learning curve. Are you saying that if I am working with the 2 M and I should set the upper and lower limits before calibrating?

Thanks for your response Gyula. However as I wrote the frequency step will change if I change frequency range. In my example case the step changes from 9 MHz to 90 kHz each, that is a change that

When you pick up the frequency range, you determine the location of the steps - you will get a wrong result without calibration. So after recording each frequency range, first Reset, then Calibrate

Here is a question for fw programmers and hw specialist. I am using a NanoVNA-H with Hugen fw 20200118. If I have made a calibration for 50 kHz to 900 MHz I get a frequency step of 8,999 or 9,000 MHz.

If for 2m, please calibrate between 140 and 150 MHz (or narrower), as we have only 101 points and no smooth interpolation between those points occurs - due to limited storage of the device. Generally,

Im new to this, but wondering how often does the nano need calibrating? Can it be calibrated all freq at once or has to be in segments? Does the cal have to be "saved"?? <bob91343@...>

Good luck and please let us know what you find.

Thank you both for the replies. I only have the default calibrations (SMA) ones currently (working on making some other ones, PL259, etc) So my nanoVNA was calibrated at the onboard SMA port, The

I think it's a calibration issue.? My nano measures accurately over a wide range of values.? It sort of gets sloppy over a few thousand Ohms of resistance.? Good up to at least 10 microfarads. The

Have you considered the impedance change along the coax between the antenna and the VNA? Did you calibrate with S/O/50 at the antenna connection directly? 40cm of coax will be near electrical 1/4 wave