¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: NanoVNA Saver or firmware bug???

 

All of my gear is in storage so I can't test ATM but if I
remember correctly, upon first connect it does not detect
the version string that it expects, so it newer runs the
get_running_frequencies function.

It usually prints out a message in the console, but I don't remember
what it was.

On Sat, 17 Jul 2021 at 16:54, DiSlord <dislordlive@...> wrote:

If i correct understand problem in loaded from NanoVNA start/stop range?

NanoVNA Saver not correct do this if not detect VNA:
Here this code:
def _get_running_frequencies(self):
'''
If possible, read frequencies already runnung
if not return default values
Overwrite in specific HW
'''
return 27000000, 30000000

This function not defined for H4 ?:
def _get_running_frequencies(self):

if self.name == "NanoVNA":
logger.debug("Reading values: frequencies")
try:
frequencies = super().readValues("frequencies")
return frequencies[0], frequencies[-1]
except Exception as e:
logger.warning("%s reading frequencies", e)
logger.info("falling back to generic")
else:
logger.debug("Name %s, fallback to generic", self.name)

return VNA._get_running_frequencies(self)






Re: Capturing and saving measurements

 

On Fri, Jul 16, 2021 at 09:41 AM, ward harriman wrote:

I¡¯ll update nanoVNA connect when I get home.
Ward,
if you have something that I can beta test on my NanoVNA H4/V2plus4 I¡®m very willing to do that

Uwe.


Re: NanoVNA Saver or firmware bug???

 

If i correct understand problem in loaded from NanoVNA start/stop range?

NanoVNA Saver not correct do this if not detect VNA:
Here this code:
def _get_running_frequencies(self):
'''
If possible, read frequencies already runnung
if not return default values
Overwrite in specific HW
'''
return 27000000, 30000000

This function not defined for H4 ?:
def _get_running_frequencies(self):

if self.name == "NanoVNA":
logger.debug("Reading values: frequencies")
try:
frequencies = super().readValues("frequencies")
return frequencies[0], frequencies[-1]
except Exception as e:
logger.warning("%s reading frequencies", e)
logger.info("falling back to generic")
else:
logger.debug("Name %s, fallback to generic", self.name)

return VNA._get_running_frequencies(self)


Re: NanoVNA Saver or firmware bug???

 

That is a quirk with Saver when it can't detect the version
of NanoVNA. Disconnect / connect fixes it on occasion.

On Sat, 17 Jul 2021 at 10:01, Nick <g3vnc@...> wrote:

Original NanoVNA 2.8" screen

Linux Mint 19.3
Python 3.7.5
NanoVNA Saver 0.3.9

When NanoVNA Saver connects to device Sweep Range always defaults to 27 -
30MHz.
After manually setting Sweep Range 1 - 100MHz NanoVNA Saver behaves
normally.

Sweep Range does not appear to be stored in
~/.config/NanoVNASaver/NanoVNASaver.ini.

Using putty

ch> clearconfig 1234

Recalibrated device and NanoVNA Saver. No change.

Flashed problem
disappears.
Reflashed
problem returns.

Problem does not occur when SimSmith 18.3 is used to connect to
NanoVNA+hugen79 1.0.45

Any ideas please?






Re: NanoVNA Saver or firmware bug???

 

The same behaviour, on a quick test, appears under firmware 1.0.53 DiSlord, nanoVNA Saver 0.3.8, running Python 3.7 in a PVE on Ubuntu 18.04.

If the latest DiSlord firmware would seem to deal with the problem, then¡­

73, Stay Safe,

Robin, G8DQX

On 17/07/2021 09:01, Nick wrote:
Original NanoVNA 2.8" screen

Linux Mint 19.3
Python 3.7.5
NanoVNA Saver 0.3.9

When NanoVNA Saver connects to device Sweep Range always defaults to 27 - 30MHz.
After manually setting Sweep Range 1 - 100MHz NanoVNA Saver behaves normally.

Sweep Range does not appear to be stored in ~/.config/NanoVNASaver/NanoVNASaver.ini.

Using putty

ch> clearconfig 1234

Recalibrated device and NanoVNA Saver. No change.

Flashed problem disappears.
Reflashed problem returns.

Problem does not occur when SimSmith 18.3 is used to connect to NanoVNA+hugen79 1.0.45

Any ideas please?


Re: Nano VNA Prt I Basics: Part II Under the Hood de k3eui #video

 

Thanks Barry.

It seemed like an excellent job to me for my low knowledge.

This has clarified issues that I could not understand.

Jose EA7GAH


NanoVNA Saver or firmware bug???

 

Original NanoVNA 2.8" screen

Linux Mint 19.3
Python 3.7.5
NanoVNA Saver 0.3.9

When NanoVNA Saver connects to device Sweep Range always defaults to 27 - 30MHz.
After manually setting Sweep Range 1 - 100MHz NanoVNA Saver behaves normally.

Sweep Range does not appear to be stored in ~/.config/NanoVNASaver/NanoVNASaver.ini.

Using putty

ch> clearconfig 1234

Recalibrated device and NanoVNA Saver. No change.

Flashed problem disappears.
Reflashed problem returns.

Problem does not occur when SimSmith 18.3 is used to connect to NanoVNA+hugen79 1.0.45

Any ideas please?


Re: Regarding calibration of a nano-vna #calibration

 

Thanks again everyone! I've watched several of W2AEW's videos but hadn't
seen this one yet.

73,
David, K2DBK
k2dbk.com
twitter: @k2dbk

On Fri, Jul 16, 2021 at 2:28 PM Fred Moore <n40cla@...> wrote:

David, I have been following this thread and thought I might add something
that might help you. This link that I have attached should give you an
easy way of making your Short/Open/Load standards using SO-239 connectors.

Fred - N4CLA



On Fri, Jul 16, 2021 at 12:12 PM David Kozinn, K2DBK <dkozinn@...>
wrote:

Thanks for all the replies. It sounds like for the frequencies I'm
looking
at, there won't be much of a difference no matter which method I use.

@Lou W7HV: Could you point me to where I could pick one a low-power 50
ohm
PL-259 as you mentioned? I looked and all I've found so far were dummy
loads with a minimum rating for 10W, which is way more than what's needed
for me. Same with looking for resistors, except for industrial supply
places where I could get a resistor for $0.50 plus $7.00 shipping.

73,
David, K2DBK










Re: Regarding calibration of a nano-vna #calibration

 

David, I have been following this thread and thought I might add something
that might help you. This link that I have attached should give you an
easy way of making your Short/Open/Load standards using SO-239 connectors.

Fred - N4CLA



On Fri, Jul 16, 2021 at 12:12 PM David Kozinn, K2DBK <dkozinn@...>
wrote:

Thanks for all the replies. It sounds like for the frequencies I'm looking
at, there won't be much of a difference no matter which method I use.

@Lou W7HV: Could you point me to where I could pick one a low-power 50 ohm
PL-259 as you mentioned? I looked and all I've found so far were dummy
loads with a minimum rating for 10W, which is way more than what's needed
for me. Same with looking for resistors, except for industrial supply
places where I could get a resistor for $0.50 plus $7.00 shipping.

73,
David, K2DBK






Re: 1/2 coax wavelength #nanovna-h4

 

When you go to put a connector on the open end, make sure the center conductor of the cable is flush with the end of the center contact on the connector. Trim the outer cover, shield, and dielectric as needed. Then double check with the VNA.
Ed


Re: Capturing and saving measurements

ward harriman
 

Note that the calibration standard can be any value BUT the reference impedance (impedance for S11 being 0) remains 50 ohms. Allowing you to set the calibration impedance simply frees you from the tedium of trying to make a reference load of exactly 50 ohms.

Ward
ae6ty


Re: Regarding calibration of a nano-vna #calibration

 

On 7/16/21 9:12 AM, David Kozinn, K2DBK wrote:
Thanks for all the replies. It sounds like for the frequencies I'm looking at, there won't be much of a difference no matter which method I use.

@Lou W7HV: Could you point me to where I could pick one a low-power 50 ohm PL-259 as you mentioned? I looked and all I've found so far were dummy loads with a minimum rating for 10W, which is way more than what's needed for me. Same with looking for resistors, except for industrial supply places where I could get a resistor for $0.50 plus $7.00 shipping.
I've used 30w Caddock noninductive TO-220 package resistors for this kind of thing, but they *are* a few bucks each.


You're probably better off just buying some cheap metal film 50 ohm resistors and testing them for parasitic L. 50 ohms is low enough that it's probably not a "spiral", rather just a uniform film.


Re: Capturing and saving measurements

ward harriman
 

Thank you for the info. I¡¯ll update nanoVNA connect when I get home.

Ward
Ae6ty


Re: Regarding calibration of a nano-vna #calibration

 

Thanks for all the replies. It sounds like for the frequencies I'm looking at, there won't be much of a difference no matter which method I use.

@Lou W7HV: Could you point me to where I could pick one a low-power 50 ohm PL-259 as you mentioned? I looked and all I've found so far were dummy loads with a minimum rating for 10W, which is way more than what's needed for me. Same with looking for resistors, except for industrial supply places where I could get a resistor for $0.50 plus $7.00 shipping.

73,
David, K2DBK


Re: Nano VNA Prt I Basics: Part II Under the Hood de k3eui #video

 

Hope, We have this video again.

Luis T.

El vie., 16 jul. 2021 9:04, Barry K3EUI <k3euibarry@...> escribi¨®:

HELLO ALL

As of July 16th:

I gave the Nano VNA talk in two installments to the Leicester Radio
Society (UK) but I did not record it and I did not post it. I'll contact
the person who did post it and see what happened to it.

I only reference this (recorded) video as the latest talk I have given on
the Nano VNA

Part I was the basic stuff - very low math but I do mention Smith Chart
I treat the nano VNA as just another tool in your ham radio toolkit
I show how you can use the Nano VNA to check out coax, filters, and
antennas.
All of the graphs were produced by NANO VNA SAVER software (free,
Win 10).
THANK YOU to the author of that app.

Part II Uner the Hood - looks at all of the measurements and calculated
parameters in more detail.
You can Calibrate the Nano VNA via software (Nano VNA SAVER) and do a
lot more with the tool.
I then go into gory detail about the Smith Chart - but not assuming
one is already familiar with it.
Part II ends with looking at resistance, reactance, and impedance and
how these plot on Smith Charts.
How do antenna tuners "cancel" the reactance on your feedline by
introducig a CONJUGATE match?
There is a bit of magic and fancy math, but I try to avoid that.
Warning: there is a Smith Chart quiz in the talk and in the PDF.

Conclusion: antennas do not "need to be resonant" to work well
(i.e. 43 ft vertical) but the entire antenna system (including feed line)
needs to present a reasonable load to your rig. The typical SWR meter gives
you a reading (2:1) but gives no information as to what you can do to
improve your antenna.

Thus, the Nano VNA is a much better "tool" at analyzing your antenna than
a mere SWR meter.

This is the best I've been able to do and explain (as a non-engineer)
after one year experience with VNA.

If I can get it posted again, feel free to share both the video and the
extended PDF with others.

This has been and continues to be a learning challenge for me.
There are many ways to "see" a concept. I'm looking for a 9th grade level
right now.
I hope my video Zoom and the PDF is aiming at the right audience.

73
K3EUI Barry
Philadelphia
K3euibarry@...







Re: Resistor measurements

 

On 7/16/21 8:12 AM, Zack Widup wrote:
I found this fascinating. I need to make an attenuator for my FT817 on
transmit as a 432 MHz
microwave IF radio. I have the appropriate carbon-film resistors. I
measured them on my NanoVNA to see what they measure at 432 MHz. This is
something I never could do before I had a NanoVNA. Two 200 ohm 1 watt
resistors measure 198 ohms on my DVM. The NanoVNA measures 198 ohms up to
about 500 kHz, and then the resistance starts to climb. At 432
MHz they both measure 225 ohms with a small amount of inductance (12 nH). I
measured a 68 ohm carbon-film resistor with similar results - it measures
67.5 ohms with the DVM and the NanoVNA up to about 500 kHz. At 432 MHz it
measures 86 ohms and a small inductance. I measured a 100 ohm carbon
composition resistor. It measured 102 ohms on the DVM and with the NanoVNA
up to about 1 MHz. The resistance barely changed on the NanoVNA above that.
At 432 MHz it measured 106 ohms.
Yes, the NanoVNA opens up a whole new world of "hands on understanding" of things like parasitic L and C.? It's an amazing device for this.




I kind of figured the carbon film resistors weren't as accurate at VHF/UHF
frequencies compared to carbon composition resistors. This verified it.
Probably a skin effect problem.
And, thus, one begins diving into the rabbit hole <grin>


Resistor measurements

 

I found this fascinating. I need to make an attenuator for my FT817 on
transmit as a 432 MHz
microwave IF radio. I have the appropriate carbon-film resistors. I
measured them on my NanoVNA to see what they measure at 432 MHz. This is
something I never could do before I had a NanoVNA. Two 200 ohm 1 watt
resistors measure 198 ohms on my DVM. The NanoVNA measures 198 ohms up to
about 500 kHz, and then the resistance starts to climb. At 432
MHz they both measure 225 ohms with a small amount of inductance (12 nH). I
measured a 68 ohm carbon-film resistor with similar results - it measures
67.5 ohms with the DVM and the NanoVNA up to about 500 kHz. At 432 MHz it
measures 86 ohms and a small inductance. I measured a 100 ohm carbon
composition resistor. It measured 102 ohms on the DVM and with the NanoVNA
up to about 1 MHz. The resistance barely changed on the NanoVNA above that.
At 432 MHz it measured 106 ohms.

I kind of figured the carbon film resistors weren't as accurate at VHF/UHF
frequencies compared to carbon composition resistors. This verified it.
Probably a skin effect problem.

73, Zack W9SZ


Re: Regarding calibration of a nano-vna #calibration

 

It is important to remember that "accuracy" and "precision" are two separate characteristics of any measurement.

DaveD

On 7/16/2021 11:02 AM, Donald S Brant Jr wrote:
The need for calibration and how frequently, varies with the measurement. If you need great precision, like accurately measuring a 40-db return loss, you might need to carefully calibrate several times a day. If you only need to know the frequency of an S11 dip, like tuning a small loop antenna in the field where there is only a single adjustment, you don't even need to calibrate at all.
73, Don N2VGU



--
This email has been checked for viruses by Avast antivirus software.


Re: Regarding calibration of a nano-vna #calibration

 

The need for calibration and how frequently, varies with the measurement. If you need great precision, like accurately measuring a 40-db return loss, you might need to carefully calibrate several times a day. If you only need to know the frequency of an S11 dip, like tuning a small loop antenna in the field where there is only a single adjustment, you don't even need to calibrate at all.
73, Don N2VGU


Re: Regarding calibration of a nano-vna #calibration

 

I always do the calibration with the NanoVNA by itself, not connected to a
computer. I have saved several band segments that I frequently use (say, 45
to 55 MHz, 140 to 150 MHz, 420 to 450 MHz) with the calibration done for
each of those segments and, for what I do, I haven't needed to re-calibrate
each time.

73, Zack W9SZ

On Thu, Jul 15, 2021 at 12:37 PM Richard Clemens <rich.clemens@...>
wrote:

On Thu, Jul 15, 2021 at 09:27 AM, Jim Lux wrote:
Very helpful -- however when I do a calibration with nanovna-saver's tool
it does not ask for a frequency range when starting the process -
confusion...

2) If the frequency span of the measurements is different than the
frequency
span of the calibration. The NanoVNA does some interpolation, but if
you did
a cal from 0-50 MHz and now you're measuring a DUT from 200-300 MHz, the
measurement might be iffy. Likewise if you did a cal from 0-900 MHz, and
the
measurement is from 20-30 MHz.