开云体育

Hi

I am relatively new to the NanoVNA thus the NanoVNA-Saver but I have spent a number of hours in front of an 8753C :-) I really like the NanoVNA-Saver and therefore have some ideas for further improvements. If I didn't like it I wouldn't even bother to make suggestions :-D

Ideas rel. to 0.0.12
- make it possible to save the full NanoVNA-Saver window and/or each plot without having to do a screen dump via another tool
- It would be ideal if there is a save dialog with an input field that is used as preamble in the file name(s) and/or also for caption in the pictures. In the file name please use underscore instead of spaces
- the dialog box could have check boxes for which pictures to save, perhaps even a check box for adding a time stamp YYYYMMDD_HHMM to the file name(s)

- in addition to the S-parameter files also to have a set of files for plain amplitude/attenuation vs. frequency

- x dB auto markers, e.g. 1 dB, 3 dB, 6 dB, 30 dB, 60 dB is difficult in general on the NanoVNA, and buttons for finding these points on LPF, HPF, BPF and Notch fillters
- more than three markers in general

Cosmetics
- the lines on my monitor are rather thin. It might be related to my screen resolution being 2560 x 1440 pixels on a 32" monitor. But it might be an idea to allow for thicker traces lines
- reduce the number of decimals, e.g. fF and pH resolutions are not important
- there is a missing space between the impedance value and the Ohm-symbol, 1234.5ohm-symbol -> 1234.5 ohm-symbol (ISO 80000)
- there is a missing space between the band value and the meter, 2200m -> 2200 m (ISO 80000)
- show the marker color in the caption of the marker value panes
- auto 1000 separators on frequency input boxes
- COM port dropdown box listing COM-ports and the logical names if available. It will make it easier to find the device. Perhaps even auto connect if logical name is found

Segments
- I am not sure I understand "segments", however, I do understand points which might be an old habit. The Hz/step unit of the segments is confusing to me

Bo

qrp.ddc,

You are absolutely wrong in saying TDR on the NanoVNA is a 'waste of time'.

This is essentially an Amateur Radio hobby forum.

Amateurs have been at the forefront of many new innovations in radio communication - because they EXPERIMENT with practically anything and everything technical.

For you to say this and that is a waste of time belittles the accomplishments of many Amateurs.

TDR on the NanoVNA is an EXPERIMENT!
It is to be played-with!
It is to be commented on in ways to MAKE IT BETTER.

All you are doing is pushing negativity about. Please don't.
Most of the forum members here will absolutely agree that playing with that particular version of firmware is interesting.

If you cannot understand that - don't use that version of firmware.
Simple, eh?

So - instead of bashing the TDR function, how about you coming up with some alternate functionality that you would like to replace the TDR with.
That way everyone here can experiment with different 'flavours' of firmware.

You said you would like to see: better calibration, more measurement points, more graphs etc.
It's all opensource and you are already writing software - so why no try adding what you want to the firmware yourself?
Several others are already doing that......

Regards,
Larry

How can you tell if it is shielded?? I see several small shielding "cans" on the PCB.? Is that the only shielding that the "shielded" ones have???
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

Rune,?
The only problem I had was that Norton AV thinks it is malware and quarentines it.
Mike WY6K


"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."

On Fri, Sep 27, 2019 at 03:44 AM, hwalker wrote:

I don't understand all the theoretical limitations associated with different
FFT sizes; but from a practical use point of view if my $50 device, as a
additional throw-in, can measure a 65 meter length cable accurate to 0.1 meter
then I'm impressed.

more FFT size leads to better time resolution. I don't need to measure cable length with TDR, this is not reliable way, because it depends on cable velocity factor which may vary even through cable length and is not stable, it very depends on temperature, frequency and other factors. More easy and reliable way to measure cable length is to use meter or with measurement tape.

TDR allows to analyze cable and connector issues, such as bad contact, impedance change, delay to incident plane, etc. But it needs at least picosecond resolution to be usable. This is why firmware TDR implementation is useless. With nanosecond resolution it's just a toy for those who want to see what TDR is. NanoVNA memory is too small for better resolution, because it needs at least 16384 points FFT. But you can do it on the PC.

I think that waste valuable controller memory for useless feature such as TDR just for one-time use DEMO purposes is a bad way. It is better to use this memory for more useful features, such as better calibration, more measurement points, more graphs etc. If you're needs TDR, you can do it on PC with much better resolution

Hi Norbert,
Thanks for testing the new functionality! The warnings are normal, sadly,
and really just show how the data from the NanoVNA sometimes shows up very
corrupted on the PC. I don't know what causes them, nor really what can be
done about it. I would have expected a pure serial-over-USB connection to
have far fewer of that sort of error.

I hope the software proves useful for you regardless!

Rune / 5Q5R
=============================================

The first time I ran the software - the current release - I got COM errors as well. They went away when I switched on the nanoVNA. Oops!

One thought, if the current drain of the nanoVNA is too high (when charging) perhaps it's beyond what the USB port can supply? By chance, I'm running mine via a powered, USB 2, hub. Thin USB cables can cause power drop problems too.

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

UOn Fri, 27 Sep 2019 at 15:12, yza <yzaVNA@...> wrote:

18 : @Dr. David Kirkby from Kirkby Microwave Ltd :

/g/nanovna-users/message/3181

Hello,

Thank you very much for your interest in our work !

No problem at all. This looks interesting.

We much appreciate that; indeed. Therefore, allow

us, please, to inform you that, on the one hand
English is -obviously- not our native language,

I realise that. I believe if the information was written in English, to
that the best of your English permits, that would be adequate.

and,

on the other hand, we are deeply regret since our
limited presentation abilities still create so much
confusion to you, even after you already read all
of our references on this subject, of course,
because these are : "the document" "including
adequate references, much like a scientific paper"
you ask for.

People are not going to read all the references in an attempt to follow
you, unless they have some idea what you are trying to achieve. Your very
first post in this thread is

*We just uploaded the current version:*

we don’t know what what this is about. There are other threads from you
started on a similar topic.


However, and in addition to these,

we already wrote, but obviously you didn't notice
it too, at:

14 : /g/nanovna-users/message/3111

This is part of the problem. Your work is spread across multiple threads.
It is very difficult to follow.

Please ask people how many people are following this. I expect it is very
few.

Nevertheless, it is needless to say that we don't
agree at all with your, obviously subjective, comment
that "The whole issue is far from simple"
-
which, by the way, it appears as it is orchestrally
emanated from some honorable specialists of
this forum

I believe that I am correct to say that the problem is not simple. If you
look at the VNWA, there are no proper uncertainty specifications. The
designer of that product is a university professor, but in my opinion at
least, there are no adequate specifications of uncertainty. The subject is
not easy.

Uncertainty of VNA measurements is still an active area of research. There
are many IEEE papers on the topic.

-
as it unreasonably discourages any Radio Amateur,
who is absolute beginner or newcomer to the subject
to even give it a chance to attempt to follow it !

I do not believe absolute beginners will be worry about uncertainty of
S-parameter measurements, as they will not even know what S-parameters
are! Absolute beginners will not know why a short, open and load are used
for calibration.

I personally believe that only once has a certain level of experience will
people start to question the uncertainty of their measurements.

Many amateur radio enthusiasts have very good knowledge of the use of VNAs.


And, as your scientific titles imply, it is certain that

you know very well that this is the worst anti-scientific
attempt to patronize the unsuspecting innocent
victim who comes here wanting to learn.

That is an unfair comment. I am just trying make you aware that few people
are following your posts. That is why this thread contains more posts from
yourself than everyone else added together.

Anyway, since we always try to be good

listeners, we shall also attempt to follow your
valuable subjective suggestions on this very subject
and to learn our lessons : Thank you once more !

I am trying to be constructive. I am trying to bring to your attention that
few, if any people are following your posts, which is why very few are
replying.

Now, regarding the objective points you had the

kindness to also set, which, we assume, you are
definitely referenced to:

[17] : From A Common User's Point Of View
/g/nanovna-users/message/2521

allow us, please, to also gladly answer them, as follows:

No I have not looked, as I do not have a good understanding of what you are
writing about.

(1) You are absolutely right about the "incomplete

definitions of the equations".

This was a deliberate omission, in order to check how
many of the honorable members of this forum
-
who desperately declare their thirsty for the Knowledge,
that is they also passionately seek it in way which
exactly coincides with that permanent of ours
-
are indeed interested for it. Therefore, we also thank
you very much, since you are giving us the happiness
to notice that:

If I understand you correctly, you are saying that you are *deliberately
not defining the terms in your equations to see who is following you. *That
sort of practice *maybe* acceptable if you are trying to teach school
children, but it certainly *not* appropriate practice in this forum. I
believe that the subject is sufficiently complicated for people to
understand, without your deliberate attempts to obscure the subject, just
to see who is following you.

I believe that you need to attempt to make your work understandable by as
many uses of this group as possible, rather than purposely obscure the
subject.

the capital letters are representatives of the "true value"

-
[ well, if you don't have a feeling of what this exactly
[ means, then allow us, please, to inform you that
[ you are not alone, but just one of us, and that all
[ together we are, with many others who have the
[ scientific honesty to admit that they also don't know
[ what that really means, because, in our humble
[ opinion, this is a notion lying on the boundaries
[ between the philosophy and the science, that is it
[ is a primitive notion, an undefined term, and all that
[ in addition to the fact that there are many others,
[ who do not accept that exists such a "true value"
-
A, B. C of three "known" loads, and Gama is of the

If A, B & C are the calibration standards, I would suggest that you use the
term “calibration standards”, rather than “loads”. I appreciate that
English is not your first language, but the term “loads” in the English
technical of VNAs will be considered by most as resistive devices.

*Normally*, the calibration standards for a one port calibration would be
termed the short, open and load in the English speaking world. In waveguide
and high microwave frequencies other standards are necessary.


"unknown" one, while the small letters are the

representatives of the corresponding (VNA or
nanoVNA) "raw" measurements, with the rest
of the multi-letters to stand for either the well-known
indexed S-parameters or for intermediate variables
-
just for the corresponding indexed Numerators to
be used in the calculations and|or the computations
-
which facilitate, as we hope, not only the
comprehension but also the programming, in the
way we are mentioning in [17], that is of complex
variables as they are all the aforementioned ones.

(2) Regarding your interesting contributing notes
about the phase matter, allow us, please to reserve
ourselves from commenting it right now.

Sincerely,

yin&pez@arg

Please understand that I am trying to help you and others by bringing to
your attention the fact that few, if anyone on this group is following you.


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

On Fri, Sep 27, 2019 at 01:04 PM, Rune Broberg wrote:

I just released 0.0.12:



This release of NanoVNA-Saver offers a number of new features, all of which
have been widely requested.

First of all, there's now the option of scaling the plots: right click them
for a menu, where it's possible to set the maximum and minimum values for
the frequency and data axes. Sadly not yet ready for the polar plots, and
mouse control of zoom is also pushed to a future release.

Second, it's not possible to have "bands" displayed in the frequency based
plots: Select "Display setup" to find the option for this. The default data
is for amateur radio bands - or you can put in your own.

Thirdly, the calibration procedure has received a new "calibration
assistant": A series of popup messages prompting you to switch between
calibration standards, and code to automatically sweep them for you and
store the results.

Finally, there's as always a number of bugfixes and stability improvements.

With more than 800 downloads of the 0.0.11 version, I can't wait to hear
what you all think of it this time - and I can't thank this community and
mailing list enough for the support, encouragement, suggestions and testing
you have provided!

I am interested in knowing what platforms you are getting this software
running on, *particularly* if you had had to jump through hoops or do
anything unexpected to get it to run: Do email me at mihtjel@... if
you can tell me what you had to do to make it work, so that I may update
the documentation, or make things easier to install in the future.

Thank you!
--
Rune / 5Q5R

Hi Rune, at the moment I haven't downloaded the latest version, but the new features further improve the program.
In particular, the new calibration routine is really welcome.
As soon as I try the new version I will post my impressions of use and any suggestions regarding subsequent changes.
Best Regards
IZ1MDJ Maurizio

On Fri, Sep 27, 2019 at 04:56 PM, sala nimi wrote:

Transmitter outputs are not matched to the output transistor or fet collector
impedance. That impedance is usually very high. Usually matching circuits are
made so that efficiency is best, that is the output device does not get too hot

max efficiency happens when you match output impedance with the load on the output connector.
More hot on the load means better match and better efficiency. This is pretty easy.

For maximum efficiency and maximum match you're needs to tune it in such way to get maximum hot on the load.

So if you really measure output impedance of a transmitter, you get
strange results.

I do that many times and never got strange results. The result is always expected - about 50 ohms for good equipment

Hi Rune
I forgot the saving calibration is not providing and info for where to save. I doubt it is saving at all.
The guided calibration is perfectly done clear and crisp to understand
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Rune Broberg
Sendt: 27. september 2019 13:05
Til: [email protected]
Emne: [nanovna-users] NanoVNA-Saver 0.0.12

I just released 0.0.12:



This release of NanoVNA-Saver offers a number of new features, all of which have been widely requested.

First of all, there's now the option of scaling the plots: right click them for a menu, where it's possible to set the maximum and minimum values for the frequency and data axes. Sadly not yet ready for the polar plots, and mouse control of zoom is also pushed to a future release.

Second, it's not possible to have "bands" displayed in the frequency based
plots: Select "Display setup" to find the option for this. The default data is for amateur radio bands - or you can put in your own.

Thirdly, the calibration procedure has received a new "calibration
assistant": A series of popup messages prompting you to switch between calibration standards, and code to automatically sweep them for you and store the results.

Finally, there's as always a number of bugfixes and stability improvements.

With more than 800 downloads of the 0.0.11 version, I can't wait to hear what you all think of it this time - and I can't thank this community and mailing list enough for the support, encouragement, suggestions and testing you have provided!

I am interested in knowing what platforms you are getting this software running on, *particularly* if you had had to jump through hoops or do anything unexpected to get it to run: Do email me at mihtjel@... if you can tell me what you had to do to make it work, so that I may update the documentation, or make things easier to install in the future.

Thank you!
--
Rune / 5Q5R

Hi Rune
Version 0.0.12 great news.
I have tested your calibration using the Delay and L/C coefficients together with my HP83033C female calibration standards and tested the calculated data for equivalent L and C and at 100MHz they are OK.
The scaling of the Data Axis is super but some problem still exist. The R+jx is if setting to + - 11 is showing 10. I suppose it will come but the Dara Axis for any of the phase displays are greyed out. That was what I stumbled over.
I did a T-Check manipulation where I copied the S11 to S22 and S21 to S12 after I subtracted the Thru adaptor delay (42ps) from S21/S11. Result attached but is not nice simply because there is no 12term error correction performed. Adding a 10 or 20dB attenuator in front of Port1 would help as linearizing the port1 input impedance to be closer to 50ohm
Keep up the good work very much appreciated.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Rune Broberg
Sendt: 27. september 2019 13:05
Til: [email protected]
Emne: [nanovna-users] NanoVNA-Saver 0.0.12

I just released 0.0.12:



This release of NanoVNA-Saver offers a number of new features, all of which have been widely requested.

First of all, there's now the option of scaling the plots: right click them for a menu, where it's possible to set the maximum and minimum values for the frequency and data axes. Sadly not yet ready for the polar plots, and mouse control of zoom is also pushed to a future release.

Second, it's not possible to have "bands" displayed in the frequency based
plots: Select "Display setup" to find the option for this. The default data is for amateur radio bands - or you can put in your own.

Thirdly, the calibration procedure has received a new "calibration
assistant": A series of popup messages prompting you to switch between calibration standards, and code to automatically sweep them for you and store the results.

Finally, there's as always a number of bugfixes and stability improvements.

With more than 800 downloads of the 0.0.11 version, I can't wait to hear what you all think of it this time - and I can't thank this community and mailing list enough for the support, encouragement, suggestions and testing you have provided!

I am interested in knowing what platforms you are getting this software running on, *particularly* if you had had to jump through hoops or do anything unexpected to get it to run: Do email me at mihtjel@... if you can tell me what you had to do to make it work, so that I may update the documentation, or make things easier to install in the future.

Thank you!
--
Rune / 5Q5R

Hi David,
thanks for offering to try out on Solaris - it'd be fun if it worked there
as well :-) I don't have any architecture-specific code, so as long as the
prerequisites (pyqt5 and pyserial) are available, it should run! :-)

--
Rune / 5Q5R

On Fri, 27 Sep 2019 at 15:46, Dr. David Kirkby from Kirkby Microwave Ltd <
drkirkby@...> wrote:

On Fri, 27 Sep 2019 at 12:04, Rune Broberg <mihtjel@...> wrote:

I just released 0.0.12:




I am interested in knowing what platforms you are getting this software
running on, *particularly* if you had had to jump through hoops or do
anything unexpected to get it to run: Do email me at mihtjel@...

if

you can tell me what you had to do to make it work, so that I may update
the documentation, or make things easier to install in the future.

Thank you!
--
Rune / 5Q5R

I’m not using my NanoVNA yet, as I have not got around to box it up
properly. But I will give your software a try on Solaris later. I have both
SPARC and x86. I don’t expect anyone else has tried that.

My normal computer is a quad core Xeon machine with OpenSolaris on it. I
also have a SPARC with Solaris 10, but I expect it would require too much
messing around to install all the software needed - git, python etc.

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

Hi Nick,
the scaling of the R+jX axes works for me - make sure you switch it from
"automatic" to "fixed"; otherwise, it won't take effect.

If you still have problems, I might need to have a further look at what
could be going wrong. In that case, please contact me directly at
mihtjel@...

--
Rune / 5Q5R

Hi Norbert,
Thanks for testing the new functionality! The warnings are normal, sadly,
and really just show how the data from the NanoVNA sometimes shows up very
corrupted on the PC. I don't know what causes them, nor really what can be
done about it. I would have expected a pure serial-over-USB connection to
have far fewer of that sort of error.

I hope the software proves useful for you regardless!
--
Rune / 5Q5R

Hi DMR,
I found the bug you are referring to - I'll get it fixed in the next
version, and obviously pushed to GitHub as soon as it's fixed :-)

Thanks!
--
Rune / 5Q5R

Hi Nick,
make sure you're running 0.0.12 - the version number should be in the title
bar. The "Calibration assistant" button is what you're after:

[image: image.png]

--
Rune / 5Q5R

And of course, the real answer to your question is the following: If you want a reliable radio equipment, buy reputable a ham radio =radio amateur products or even professional radio products. They keep their promises, no need to worry or guess anything. They'll cost something but quality costs.

Hi Rune

How do I start this wizard? Can't see it in the Calibration window.

Using Mint Linux 19.2 x64, Python 3.7.3.

73
Nick
G3VNC

On Fri, 27 Sep 2019 at 15:04, <reuterr@...> wrote:

Hello David,
Thank you very much for the clear and polite words.

If the topic is really *important* for the community, the it is the duty
of the originators
to convert their FORTAN programs to Python, and show some
*input* *output* data examples.

73, Rudi DL5FA

Rudi,

It is *not* anyone’s duty to convert their Fortran to Python! Nor is it
their duty to show examples of show input or output, nor is it it their
duty to write the information in a coherent way.

I do however think writing the information in a coherent manner and showing
some examples of input and output would be *very* useful. Without the
information being written in a coherent way, it is of very little value.

Converting Fortran to Python seems to be taking things too far though.
Porting code has the possibility of introducing bugs. Anyone technically
competent enough to understand the content should be able to use a Fortran
compiler. If not, they should be able to find someone who can compile a
Fortran program.

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

BTW..... this version is the so-called "better" one with shielding. It is better construction than my "white salamander worst" unit or my black "worse" one. The noise floor might be slightly lower on this one but I find no practical measurement differences among the three. Given a choice I would probably choose this one but I would also be perfectly happy with either of the other two.

WA8TOD