开云体育

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

I bought the same Nanovna and mine too came without a battery. I bought this one from eBay. It fits (barely) and works perfectly.



Warren Allgyer
WA8TOD

18 : @Dr. David Kirkby from Kirkby Microwave Ltd :
/g/nanovna-users/message/3181

Hello,

Thank you very much for your interest in our work !

We much appreciate that; indeed. Therefore, allow
us, please, to inform you that, on the one hand
English is -obviously- not our native language, 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. 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 the current state of published research on
this subject, excluding some papers under preparation
in order to be published in our small journal:


"
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
-
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 !

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.

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 !

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:

(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:

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
"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

18

Scaling does not work. The schedule remains the same.
Check someone else out.
Thank.

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

Output impedance of a transmitter is not simple thing. 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. So if you really measure output impedance of a transmitter, you get strange results. Besides, you may burn your transmitter or measuring device.

Hi Rune,
I tested your new guided calibration routine as well and all works fine with Win10 pro. Very well done! Thank you very much!
I keep getting some warnings, and I have no idea if the performance of the NanoVNA will suffer from those!? This is not related to the current version, I had that "feature" with all versions. The messages were generated during calibration.

Kind regards
Norbert, DG1KPN

Great stuff Rune!

On the R+jX chart the frequency axis scaling works FB but I cannot make the scaling of the data axes work.

73
Nick
G3VNC

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

Thanks for the effort with the software, Rune. Works fine on my Windows 10.