¿ªÔÆÌåÓý

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

Re: gnuplot for nanoVNA Touchstone files

 

If you just want Touchstone files, NanoVNA-Saver was actually, as the name
implies, built to save Touchstone files. ;-) Not easily automated, though
it probably wouldn't be a huge effort to build a Python command-line tool
to do so.

--
Rune / 5Q5R

On Fri, 18 Oct 2019 at 20:52, Oristo <ormpoa@...> wrote:

link added to application notes
/g/nanovna-users/wiki/Application-Notes
nanoVNA shell commands `frequencies` and `data` naturally return columns
of numbers,
so nearly Touchstone format.
The unix utility `paste` trivializes combining text file columns,
and while it is not too tricky to store PuTTY log files,
then edit those logs into files appropriate for `paste`,
that is not easily scripted. As Dr. David noted,
"being able to generate all the PDF plots from a single unix shell script
makes the process much easier".

One challenge is that Windows seemingly lacks a native utility comparable
to Unix `paste`,
but `paste` is available e.g. by Cygwin, Windows Subsystem for Linux (WSL)
or MSYS2


WSL is an option neither for Windows 7 nor 8, and Cygwin is rather
extensive.
MSYS2 `paste.exe` may be already available e.g. if some Ruby is installed,
and appears the least invasive well-supported.

Another challenge is communicating with nanoVNA's virtual COM port from
scripts;
that works for me on Windows 8.1 so far neither from Cygwin nor cmd.exe...

Suggestions are invited; ideally, a utility is wanted that
sends command line arguments in sequence to nanoVNA,
then returns data from the final argument until nanoVNA returns "ch>".




Re: gnuplot for nanoVNA Touchstone files

 

link added to application notes
/g/nanovna-users/wiki/Application-Notes
nanoVNA shell commands `frequencies` and `data` naturally return columns of numbers,
so nearly Touchstone format.
The unix utility `paste` trivializes combining text file columns,
and while it is not too tricky to store PuTTY log files,
then edit those logs into files appropriate for `paste`,
that is not easily scripted. As Dr. David noted,
"being able to generate all the PDF plots from a single unix shell script makes the process much easier".

One challenge is that Windows seemingly lacks a native utility comparable to Unix `paste`,
but `paste` is available e.g. by Cygwin, Windows Subsystem for Linux (WSL) or MSYS2


WSL is an option neither for Windows 7 nor 8, and Cygwin is rather extensive.
MSYS2 `paste.exe` may be already available e.g. if some Ruby is installed,
and appears the least invasive well-supported.

Another challenge is communicating with nanoVNA's virtual COM port from scripts;
that works for me on Windows 8.1 so far neither from Cygwin nor cmd.exe...

Suggestions are invited; ideally, a utility is wanted that
sends command line arguments in sequence to nanoVNA,
then returns data from the final argument until nanoVNA returns "ch>".


Re: Owen Duffy on improvised test fixtures #test-jig

Mel Farrer, K6KBE
 

Hi Jeff, I take a different approach to the test fixture, Mine in a copper
sheet between a pair of PCB mount male connectors with alligator clips to
the DUT. Since most of my work in <100 MHz, it works for me. I get a good
50 dB isolation.
Mel, K6KBE



On Fri, Oct 18, 2019 at 11:33 AM Jeff Anderson <jca1955@...>
wrote:

Bruce, I completely agree. Rune¡¯s code is available to all of us. If
there¡¯s something I¡¯d like to see added (and there are two small mods), I
look at it as an excellent reason to learn Python and make the mods myself.

- Jeff, k6jca




Re: Owen Duffy on improvised test fixtures #test-jig

 

Bruce, I completely agree. Rune¡¯s code is available to all of us. If there¡¯s something I¡¯d like to see added (and there are two small mods), I look at it as an excellent reason to learn Python and make the mods myself.

- Jeff, k6jca


Re: NanoVNA-Saver 0.1.3

Mel Farrer, K6KBE
 

I agree, I look at changes I make as "WHAT IF" that way, I don't mess
things up. However, when a good thing happens, I always recal.........Then
save with new name.

Mel, K6KBE

On Fri, Oct 18, 2019 at 11:27 AM Maurizio IZ1MDJ <redifon500@...>
wrote:

Hi Nick , my suggestion is that the " save calibration " , save also the
state of the instruments , like all the vna i know.
If you , change some sweep parameter with the calibration applied , it's
ok to put a warning at the operator that the currently calibration may be
not valid.
Sincerely I don't understand what is the convenience to mantain sweep
setup that my be not agree with the calibration.
Of course this is my opinion.

Best Regards
Maurizio IZ1MDJ

On Fri, Oct 18, 2019 at 03:39 PM, Nick wrote:


Hi Rune

I would not expect measurements made outside of the frequency range of
the
current calibration to be "accurate".

I would not want nvna-s to change the sweep setup when a calibration is
loaded. But I might expect to be reminded.

Having loaded a calibration how about warning the user if they try to
make
measurements outside the calibrated frequency range?

e.g. by flashing up an out of calibration message box, watermarking the
plots
etc.

73
Nick

On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:

I agree that calibrations should save the
start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever
frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?



Re: NanoVNA-Saver 0.1.3

 

Hi Nick , my suggestion is that the " save calibration " , save also the state of the instruments , like all the vna i know.
If you , change some sweep parameter with the calibration applied , it's ok to put a warning at the operator that the currently calibration may be not valid.
Sincerely I don't understand what is the convenience to mantain sweep setup that my be not agree with the calibration.
Of course this is my opinion.

Best Regards
Maurizio IZ1MDJ

On Fri, Oct 18, 2019 at 03:39 PM, Nick wrote:


Hi Rune

I would not expect measurements made outside of the frequency range of the
current calibration to be "accurate".

I would not want nvna-s to change the sweep setup when a calibration is
loaded. But I might expect to be reminded.

Having loaded a calibration how about warning the user if they try to make
measurements outside the calibrated frequency range?

e.g. by flashing up an out of calibration message box, watermarking the plots
etc.

73
Nick

On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:

I agree that calibrations should save the start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?


Re: Abbreviated documentation for more simplistic tasks?

 

An excellent idea.

Someone new to VNA's and what a complex impedance is will be overwhelmed
if told to check the wiki, all the forum posts, and read some Agilent document.
They just want to measure their antenna's SWR (they think).
Or maybe sweep a filter.
A first document should tell them that without having to first wade through a lot of new material.

We need a single document that tells how to charge it, turn it on, configure it to show SWR
and complex impedance, and then sweep across a range of frequencies.
How to measure that filter.
How to deal with the user interface, what parts of the menu structure they can ignore,

If ambitious, further sections of this document could give a primer on what a complex impedance is.
When calibration might be a good idea.
What a reference plane is.


Maybe set up a few example exercises, using a 100 pF cap and a 100 ohm resistor so the parts are likely on hand.
Keep the frequency fairly low so it's easy to reproduce.
Show them how to measure these parts in various configurations, and what results to expect.
Perhaps add a hand wound inductor to the mix.
And what happens when this stuff is put on the end of 25 feet of cheap RG79 coax.

An appendix with links into other documents with a brief description of what can be found there.
Things like transmission line theory, impedance matching, Smith charts, S parameters.

Jerry, KE7ER


Re: Possible Issue with ttrftech firmware (0.2.3-11) above 300 mhz

 

AA6KL,
Thanks for the info and tips, I was successful in clearing the config and saving the cleared config to slot 0. Re-calibrated the device, and there was still no change with the smith chart above 300 mhz.


Firmware verison 0.1.1 is fine above 300 mhz, and anything above 0.1.1 causes the issue. So i still going back on the firmware is the issue (at least on my device).


What is The Best calibrati¨®n for NanoVna???

TITO-OA4LDR
 

Hello friends! very good day, what is the best way to make the best NanoVNA calibration since I have seen several videos of NanoVNA users that make them in different ways on YouTube and I don't know which one is the best and the most appropriate! Is there any kind of tutorial to do it ??? best regards! 73s


Re: NanoVNA-Saver 0.1.3

 

Hello Rune-

Thanks for the fantastic software! I built an 11-pole 500 kHz Low Pass Chebyshev filter using AADE Filter Design software back in 2010 for use with a Softrock LF Ensemble II SDR kit. It seemed to work as expected, but with NanoVNA and NanoVNA-Saver I was finally able to do a 'proper' analysis- see the attached images. Also, thank you Hugen and edy555 for the fantastic hardware!

73,

Joe F. KC8RKL

<posting this a 2nd time, as the .png images originally attached showed errors in the groups.io web interface>


Re: Can't update firmware

 

As with re-calibration or after a firmware upgrade, you will first perform a Reset and then perform a calibration step by step (if you make a mistake, it will start over again).

So here too, the faulty driver must be removed first and then the new driver installed. (or use the installation wizard.)

Anyone who can ask well knows the answer already :-)


Re: Owen Duffy on improvised test fixtures #test-jig

 

It's been my experience that those who can, do. Those who can't, criticize. I'm sure Rune would appreciate suggestions as to how to improve his software. But, at least he gave us a start. It's up to us to help develop the application.

My nickel's worth.

Bruce Nebergall / K4TQL


Re: NanoVNA-Saver 0.1.3

 

Hi Rune

I would not expect measurements made outside of the frequency range of the current calibration to be "accurate".

I would not want nvna-s to change the sweep setup when a calibration is loaded. But I might expect to be reminded.

Having loaded a calibration how about warning the user if they try to make measurements outside the calibrated frequency range?

e.g. by flashing up an out of calibration message box, watermarking the plots etc.

73
Nick

On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:

I agree that calibrations should save the start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?


Re: errors of "error" models

 

#57 : ann : [LeastVNA] ~ [NanoVNA] later today 57#


Re: errors of "error" models

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Fri, 18 Oct 2019 at 11:43, yza <yzaVNA@...> wrote:

#55 : just because this is research in progress : #55

Many people report work that¡¯s in progress, but report it in a way others
can at least see what is the aims of the work. The title should give some
indication of what the work is about, but even your title is confusing.

I just did a search for ¡°amplifier work in progress¡± Here are the first two
links I found. I did not read any more than the first paragraph of each,
but they are at least presented in a way that others can follow.






despite they are a work in progress.

Here is a description for children on how to make graphs. We see a title on
the graph, the x axis is the year, the y-axes is the population.



I don¡¯t know at what age graphs are taught to children in the UK, but I am
sure by the age of 14, children would know that you need to put labels on
the axes! It is such a basic thing, yet you don¡¯t even label the axes!

When I write software, even if just for my own use, I will put at least
some comments in the code.

Have you considered putting your work onto a webpage, that people could
read and understand without clicking links?

Have you considered writing it like a basic scientific report?



Earlier I wrote that I would try to correct the English if you could write
the work in an understandable way. That offer still stands.

Dave.

--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom


Re: Supply noise at higher harmonics #internals

 

The IP5303 inverter section is running at 350KHz when running off of the internal battery. That will create a pile of noise.

For a good sense of supply line noise, the IP5303 needs to be removed/disabled and a well filtered 5V linear supply used as Erik mentioned earlier.
That is why I suggested running off a 7.2V lithium pack, using a linear 5v regulator with low noise and transient specs.
The service manuals for various VNA analysers are all over the Web - have a look at how they filter their power sources.
A good source of manuals is:?

On Friday, October 18, 2019, 3:16:34 a.m. GMT-4, erik@... <erik@...> wrote:

On Thu, Oct 17, 2019 at 01:02 PM, Dave Daniel wrote:


has anyone measured the +5 V rail(s) to see how noisy they are?
USB power is very noisy.
Hugen79 designed the power part of nanoVNA different from edy555
Hugen79 uses the output of the IP5303 for 5 volt where edy555 uses the USB power.
Did not check noise on IP5303 output but when the nanoVNA is running on internal battery noise is less so I assume its very high frequency noise coming from the USB VBUS, leaking through the IP5303


Re: errors of "error" models

 

#56 : our [OPEN] ~ [SHORT] 'standards' in our [NanoVNA] and our [VNA]

Hello,

Allow us, please, to present our comparative results for the indications or
readings taken with our [OPEN] and [SHORT] 'standards' as they were
measured on the same Reference Plane * with our [NanoVNA] and our
[VNA], which have as follows:

I/II
Measurements with [VNA] : BLUE = [SHORT], CYAN = [OPEN]

[Magnitude] vs [Frequency] in Antilog vs MHz:


[Argument] vs [Frequency] in Degree vs MHz:


II/II
Measurements with [NanoVNA] : RED = [SHORT], MAGENTA = [OPEN]

[Magnitude] vs [Frequency] in Antilog vs MHz:


[Argument] vs [Frequency] in Degree vs MHz:


and take into account, please, that both instruments have the
"same" Characteristic Impedance only because they were named
by their manufacturers with the same Nominal Value of 50 OHM.

* #50 : The Full Final Report 1 :
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Nominal Values Zinp = ( Rinp , Xinp )
of our Standard [ref2007box], in terms of
frequency, using [NanoVNA] and [VNA]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[NanoVNA] ~ [VNA] Comparison
16 October 2019
/g/nanovna-users/message/5061

Sincerely,

gin&pez@arg

56#


Re: errors of "error" models

 

#55 : just because this is research in progress : #55
@Dr. David Kirkby from Kirkby Microwave Ltd
/g/nanovna-users/message/5150


Re: NanoVNA-Saver 0.1.3

 

On Thu, Oct 17, 2019 at 08:01 PM, Rune Broberg wrote:


I *think* the Cs/Ls you are after is already shown in the marker data
display? It's what's shown as "L equiv."/"C equiv."

The series resistance is the resistive part of the impedance display.
Hi Rune,

OK, so this this may just be down to terminology after all.

I guess what I'm looking for is something like the marker information presented in the AIM VNA software (see attached).

Having both Series and Parallel values displayed saves a lot of time if you are trying to work out values for matching networks.

I assume that these are calculated using the following formulae, but only the inductance or capacitance value is shown as appropriate

Rs = Zmag*cos (phase)
Xs = Zmag*sin (phase)
Rp = ( Rs^2 + Xs^2 ) / Rs
Xp = ( Rs^2 + Xs^2 ) / Xs
Ls= Xs / ( 2 * Pi * f )
Cs = 1 / ( 2 * Pi * f * Xs )
Lp= Xp / ( 2 * Pi * f )
Cp = 1 / ( 2 * Pi * f * Xp )
Q = Rp / Xp = Xs / Rs
Rp = Rs ( 1 + Q^2 )

Regards,

Martin - G8JNJ






--
Regards,

Martin - G8JNJ


Re: Purchase sources 4.3 inch NVA

 

From: ambaer52@...

I understand that there is a 4.3 inch version available. Has anyone purchased one? If so, I am in the US. Where is a reliable source to purchase one?
=========================

I bought one and it works well, also working with Rune's nanoVNA saver.

I bought here:



but I see it's now:



and there's a support group here:

/g/nanovna-f/messages

Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv