开云体育

** No, the "clicks" are never in the same place. We will say, to simplify, that it is parasites that cause this. We find the same thing in the .S1p files but it's less troublesome. If I want data

Hello Francois, What if you slightly change the frequency range and/or number of segments? Are the errors still at the same frequency? Good work you are doing by trying to make it clear! All the best,

** Hello I am posting an example. The calibration file (.cal) corresponds to the end of a 50 m coaxial cable (50 Ω). The frequency sweep range is 1 to 20 Mhz in 20 segments. Follows the description

What Stan said. It appears that the nanovna is doing a "mean average". In statistics, the N number of samples are examined to find the largest and smallest, or other measure of outlier, values which

Fran?ois, It would be helpful if you described the specific frequency span you are using, the number of segments, and the frequencies where the "errors" occur. If there is some sort of bug in the

The NanoVNA makes multiple sweeps, and NanoVNA-Saver averages them. One thing to remember is that if the sweep is >101 points, it's actually multiple sweeps strung together. I do not know. Maybe it's

I have a NanoVNA H version 3.5 software 1.0.64, kernel 4.0.0 I need to check where the bump is. It does not happen always... When i see it again, I will report. All the best, Victor Op vr 29 jul. 2022

Which nano and which firmware? Do different nano-types or firmware versions make a difference? On my old nano (H3.2) I had a bump around 6 MHz, but it was a known errror. Arie PA3A

I also see sometimes these 'clicks' coming at the same frequency in the measured results. But after a recalibration they are most of the times gone.But they indeed happen, why I don't understand. I

Hello I didn't understand the meaning of: - Number of measurements to average - Number to discard - Common values ??are 3/0, 5/5, 9/4 and 25/6 1/ Could you explain to me what you understand about

Cracked it at last using Nano vna. Analysis shows cut length of 16feet and 6 inches is too long as resonates at 13.198MHz and not my target of 14.175. Reverse maths gives a constant of 218 (resonant

Or use a tuner at the feedpoint. Small changes in resonant frequency (10%) are easily tuned out with minimal loss. Even with a feedline, and tuner at the radio end, the losses are small.

The formula (feet)=234/MHz for a quarter wavelength is just a rough starting point. The resonant length is affected by many variables, like conductor diameter and the placement of nearby conductors

This can be a problem... Some installers are less than smart, and copy all the files into a new directory each time, add that directory to the path that python searches, and then that longer path gets

If you would take your existing board and use a sharp knife to remove the excess copper you might get a better result, or at least see what changes occur. Trimming the connector pins back will also

Hi Thanks a lot for your responses. Jim, I was not aware that Er would potentially drop significantly by frequency. I will check if data exists for Er vs frequency. Thanks. Donald, good point on the

Since I switched to nanovna-saver 0.3.10 -win7 the display time of the "console" window remains displayed for 12 seconds. Previously with version 0.3.8 it was only 3 seconds. It really is a great

I think the startup delay has a lot to do with what version of windows you are using. Mine used to start up fast like that, 3sec or so - but after the latest Saver update, which happened to coincide

Sounds like you have a lot of overhead background running, or slow/low resources, or both. Mine launches within a few seconds of the DOS terminal. Stephen W9SK

Mine starts goes to DOS window and then windows window in under 3 seconds.Add some laser oil to your dilithium crystals.....or how much stuff is in your process table