¿ªÔÆÌåÓý

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

NanoVNA-Saver 0.1.4


 

Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release notes:

This release adds a number of new features, some bug fixes, and some
internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on
your screen. In fact, the software does not stop there: You can even add
markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|,
|S11| and |S21| in linear format, S11 and S21 logarithmic on the same chart
at the same time, and the raw S11 and S21 real/imaginary S-parameter values.

Calibration updates:
The calibration assistant has become more talkative, and should be better
at telling you what has gone wrong when it won't apply a calibration. When
applying a new calibration, or applying after changing to a different
calibration standard set, the previous sweep is immediately updated to show
the effect of the new values. This should be useful for finding the right
values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts
after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates,
and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software
for the past two or so months. I'm now going to take a little break and
relax, and I therefore don't expect to make any new releases next week
(*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your
appreciation, as well as pointing out bugs, misunderstandings, potential
improvements and new ideas. I appreciate this greatly, and I hope you will
continue to do so, even as I take a week or so to relax ;-)

--
Rune / 5Q5R


 

Hi Rune,
Hi nanovna-users,


the go-ahead from Avast for 0.1.4 alpha just had arrived.

Attached you find a pic of my Hugen mounted on a PE board with N Extension, and two pics with the same configuration, but very different results.

Description:

using my Hugen NanoVNA mounted on a PE board with N extension (pls disregard the 70 cm dipole shown on that older pic),
after calibrating to this N-plane directly on the Hugen (just O-S-L for S11),
never switching off,
then after again calibrating to this same N-plane via saver 0.1.4 alpha (just O-S-L for S11),
never switching off,
I first compared calibration results on both Smith Charts, Hugen and saver, for O, S and L. Both were identical with respect to the 3 cal points on both Smith Charts,
never switching off,
then - for some test - I connected via N-male-to SMA-female adapter one of the two SMA-male-SMA-male cables that came with the Hugen,
never switching off,
in the range of 400MHz ... 500MHz, as entered in saver, which also showed up on the Hugen, too,

... I looked at the saver pic and an the Hugen photo shot (sorry for the poor quality without stand) and compared:

The two are quite different:

The saver screen shot shows - as I would expect - a circle close to the outer rim of the Smith Chart, even going a little bit outside |Gamma| =1 , which
is possible for lossy lines and not an indication of an impossible result. The attenuation makes it spiraled towards the Smith center, which is 50 Ohms.

The Hugen photo, however, shows a circle fully inside the traditional Smith Chart outer rim, centered around a point much less than 50 Ohms
having a much smaller diameter.

Imho your saver screenshot is as ok as can be expected, the Huigen pic, showing exactly the same thing, however is not.

How comes?

Probably I did something wrong, but I have no idea, what.

Theoretically there is, however, also a remote possibility of both using different calculations.
Checking both source codes for that is beyond my current possibilities.

Who in the group has had a similar experience?
Who perhaps knows why?
What needs perhaps to be done differently?

73, Hans
DJ7BA




-----Urspr¨¹ngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von Rune Broberg
Gesendet: Mittwoch, 23. Oktober 2019 09:57
An: [email protected]; [email protected]
Betreff: [nanovna-users] NanoVNA-Saver 0.1.4

Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release notes:

This release adds a number of new features, some bug fixes, and some internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on your screen. In fact, the software does not stop there: You can even add markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|,
|S11| and |S21| in linear format, S11 and S21 logarithmic on the same
|S11| chart
at the same time, and the raw S11 and S21 real/imaginary S-parameter values.

Calibration updates:
The calibration assistant has become more talkative, and should be better at telling you what has gone wrong when it won't apply a calibration. When applying a new calibration, or applying after changing to a different calibration standard set, the previous sweep is immediately updated to show the effect of the new values. This should be useful for finding the right values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates, and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software for the past two or so months. I'm now going to take a little break and relax, and I therefore don't expect to make any new releases next week (*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your appreciation, as well as pointing out bugs, misunderstandings, potential improvements and new ideas. I appreciate this greatly, and I hope you will continue to do so, even as I take a week or so to relax ;-)

--
Rune / 5Q5R




--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr¨¹ft.


 

Who in the group has had a similar experience?
Who perhaps knows why?
What needs perhaps to be done differently?
In nanoVNA DISPLAY menu:
* select the TRACE being used for Smith,
e.g. turn off/on or turn off all others
* select SCALE and set SCALE/DIV 1 x1

With NanoVNA-H_AA_20191018.dfu,
SCALE - REFERENCE POSITION settings do not affect Smith format plot centering,
but perhaps it may on some other firmwares

Because of (IMO) poor menu arrangements,
it is too easy to accidentally change trace settings for a wrong trace.


 

Enjoy your well deserved break. I will have a look at the software at the
weekend .

Paul G0VKT

On Wed, 23 Oct 2019, 08:56 Rune Broberg, <mihtjel@...> wrote:

Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release notes:

This release adds a number of new features, some bug fixes, and some
internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on
your screen. In fact, the software does not stop there: You can even add
markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|,
|S11| and |S21| in linear format, S11 and S21 logarithmic on the same chart
at the same time, and the raw S11 and S21 real/imaginary S-parameter
values.

Calibration updates:
The calibration assistant has become more talkative, and should be better
at telling you what has gone wrong when it won't apply a calibration. When
applying a new calibration, or applying after changing to a different
calibration standard set, the previous sweep is immediately updated to show
the effect of the new values. This should be useful for finding the right
values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts
after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates,
and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software
for the past two or so months. I'm now going to take a little break and
relax, and I therefore don't expect to make any new releases next week
(*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your
appreciation, as well as pointing out bugs, misunderstandings, potential
improvements and new ideas. I appreciate this greatly, and I hope you will
continue to do so, even as I take a week or so to relax ;-)

--
Rune / 5Q5R




 

Is't it time for you to change the version to "1.0"???


 

Hi Oristo,



Thank you very much for your assistance.

It seems, I needed perhaps more practice and patience, too, before I posted it:

Meanwhile it workes fine - after a number of recalibration attempts on the Hugen.

It took several complete new attempts to calibrate and then - all at a sudden it worked ok.

It probably was some contact problem, but I am not sure.
Another possibility: When it finally worked ok, I had also
used the same center and span in both CAL attempts, Hugen and saver.


Here now find the good result pics,
this time taken with the stand.

Thanks again Oristo and group.
It is so good to know you can get assistance in a group like this.

73, Hans
DJ7BA



-----Urspr¨¹ngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von Oristo
Gesendet: Mittwoch, 23. Oktober 2019 12:26
An: [email protected]
Betreff: Re: [nanovna-users] NanoVNA-Saver 0.1.4



Who in the group has had a similar experience?
Who perhaps knows why?
What needs perhaps to be done differently?


In nanoVNA DISPLAY menu:

* select the TRACE being used for Smith,

e.g. turn off/on or turn off all others

* select SCALE and set SCALE/DIV 1 x1



With NanoVNA-H_AA_20191018.dfu,

SCALE - REFERENCE POSITION settings do not affect Smith format plot centering,

but perhaps it may on some other firmwares



Because of (IMO) poor menu arrangements, it is too easy to accidentally change trace settings for a wrong trace.







--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren gepr¨¹ft.


 

On Wed, Oct 23, 2019 at 01:56 AM, Rune Broberg wrote:


I'm now going to take a little break and
relax
Rune,

Please take a well deserved break. Thanks for your tremendous effort on this software. I really like many of the new features. Here are a few examples 1) more markers, 2) seeing termination tuning results after clicking apply without running another scan, more plots, the TDR plot is very helpful, the flexibility available in calibration, and many more. You have done a great service to the community.

My hat is off to you! We must, of course, remember the developers of this hardware and firmware! They have made huge strides as well.

73
--
Bryan, WA5VAH


 

Enjoy your break and thanks a ton for your excellent 'saver' program! 0.1.4. looks great!


 

What a tool!
0.1.2 has just now been updated to 0.1.4. here.
Do take a rest, Rune. If you don't lay another finger on this potent
application, it will remain as a superb achievement for years.

+++++

A little note for new Linux users who find that Rune's application
is not seeing the NanoVNA when it is physically connected: root's
privileges will be required in running the application so that the
application is permitted to make a connection to the NanoVNA. If the
issue is that the application has not been permitted to open a port,
there will be a report to that effect in the console display.

+++++

On behalf of all of us, Rune, many, many thanks.
John
at radio station VE7AOV
+++++


On 2019-10-23 12:56 a.m., Rune Broberg wrote:
Hello all,
I just released NanoVNA-Saver 0.1.4. Here are the release notes:

This release adds a number of new features, some bug fixes, and some
internal reorganisation:

Adding markers:
You can now add or remove markers, allowing you as many as you can fit on
your screen. In fact, the software does not stop there: You can even add
markers which you can't fit on your screen!

New charts:
A number of new chart types have been added, allowing you to plot |Z|,
|S11| and |S21| in linear format, S11 and S21 logarithmic on the same chart
at the same time, and the raw S11 and S21 real/imaginary S-parameter values.

Calibration updates:
The calibration assistant has become more talkative, and should be better
at telling you what has gone wrong when it won't apply a calibration. When
applying a new calibration, or applying after changing to a different
calibration standard set, the previous sweep is immediately updated to show
the effect of the new values. This should be useful for finding the right
values for calibration standard sets.

Bugfixes:
Line thickness and point size should now load correctly and apply to charts
after you restart the software.
SWR marker colours should similarly also load correctly.
The software should now be able to run and attempt to check for updates,
and not crash when you don't have an internet connection.

I hope these features and updates are useful to the community!


I look forward to hearing the feedback from you all!

And a little announcement: I have been really quite busy with this software
for the past two or so months. I'm now going to take a little break and
relax, and I therefore don't expect to make any new releases next week
(*gasp*), and I might even be slow in responding to your emails.

You have all been very kind in writing to me both showing your
appreciation, as well as pointing out bugs, misunderstandings, potential
improvements and new ideas. I appreciate this greatly, and I hope you will
continue to do so, even as I take a week or so to relax ;-)
--


 

I can not find in Nanovna-saver port extension feature. If not exist, feature request it. Already calibrated reference plane easy sifted software to end cable/connector. Not a best precision method, but useful. Cable delay input parameter in picoseconds, more useful if selectable delay or/and delay computed from transmission line velocity factor with real cable length in millimeter. More useful, if not only cable delay used, coax cable loss used too. I see, nanovna support simple electrical lenght compensation. But useful if nanovna-saver support to with extended features.


 

On 23/10/2019 20:21, John Nightingale via Groups.Io wrote:
--------------snip------------------
A little note for new Linux users who find that Rune's application
is not seeing the NanoVNA when it is physically connected: root's
privileges will be required in running the application so that the
application is permitted to make a connection to the NanoVNA. If the
issue is that the application has not been permitted to open a port,
there will be a report to that effect in the console display.
Please don't encourage people to run Linux GUI applications as root. It's a very bad idea.

It's likely that the regular user is not in the dialout group which is easily rectified by entering the following command in a terminal:

sudo usermod -G dialout $USER

You will then need to log out and back in once, after which nanovna-saver should always be run as a regular user.

Cheers,
Barry
G4MKT


 

You may also need to add the try group to your user profil. I found that I needed to on RaspberryPi.
M Walter


 

On Wed, Oct 23, 2019 at 04:59 AM, DJ7BA wrote:
The Hugen photo, however, shows a circle fully inside the traditional Smith
Chart outer rim, centered around a point much less than 50 Ohms
having a much smaller diameter.
My currently installed firmware allows changing scale of Smith plot, but not center.
Perhaps a firmware bug in October overwrote scale and offset...