¿ªÔÆÌåÓý

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

Re: Cal-Kit Standards' Definitions

 

On Mon, Sep 30, 2019 at 05:57 AM, Kurt Poulsen wrote:


Here is another handy document of general interest
basic knowledge about a transmission line.pdf
I still have a problem to create it as html Hm....
Hi Kurt,

Here's the link (I hope!):

By the way, if I go to your top page, , I don't see this PDF listed in the contents. Did I miss it?

- Jeff, k6jca


Re: Cal-Kit Standards' Definitions

 

On Mon, Sep 30, 2019 at 05:57 AM, Kurt Poulsen wrote:


basic knowledge about a transmission line.pdf


Interesting example on how to get rid of the remaining osculation due to fringe C/L of the calibration load


Re: Another modified nanoVNA software

 

On Mon, Sep 30, 2019 at 06:47 PM, Gyula Molnar wrote:


Hi neb,

TDR is work well.
Hi,

It is nice to know that you made it work.

neb


New document

 

Hi Again Erik

This time by creating a new mail I succeded

basic knowledge about a transmission line.pdf
<
on%20line.pdf>

Kind regards

Kurt


Re: Cal-Kit Standards' Definitions

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Mon, 30 Sep 2019 at 13:46, Kurt Poulsen <kurt@...> wrote:

Hi Oristo
Thank you for your lingual suggestions
I have printed your input for picking up any more suggestions.
Kind regards
Kurt

Kurt,
it might be worth creating a fake Touchstone file with an exponentially
decaying amplitude, ¡°modulated¡± with a sine wave - I *think* that would
produce the right result. If you exaggerated the problem with a bit of fake
data, it would be easier to see.

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: Cal-Kit Standards' Definitions

 

Hi Erik
Thank you for the link in html I tried to change my response to html but is failed
Here is another handy document of general interest
basic knowledge about a transmission line.pdf
I still have a problem to create it as html Hm....
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af erik@...
Sendt: 30. september 2019 07:34
Til: [email protected]
Emne: Re: [nanovna-users] Cal-Kit Standards' Definitions

Kurt.

Thanks for these documents, I updated the link as this will work




It helped me to understand some calibration problems w.r.t. reference planes

Erik.


Re: Cal-Kit Standards' Definitions

 

Hi Oristo
Thank you for your lingual suggestions
I have printed your input for picking up any more suggestions.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Oristo
Sendt: 30. september 2019 11:32
Til: [email protected]
Emne: Re: [nanovna-users] Cal-Kit Standards' Definitions


C%20calibration%20kit.pdf
I am still puzzling thru this. On page 3:
"As seen the trace is not flowing the circumference off the Smithchart which must spiral inwards in a progressive way."

.. evidently "flowing" should be "following" and "off the Smithchart"
should be "of the Smith chart".
I >>guess<<: " which must spiral inwards in a progressive way" should be understood "but is spiraling inwards", e.g.

"Instead of following the Smith chart circumference, the trace is seen spiraling inward."

.. where this trace is from an unterminated non-ideal cable (not airline), and changing (50 Ohm) LOAD shunt capacitance value C from 51.8 to
-108.2 improves "calibration".


Re: Another modified nanoVNA software

 
Edited

Hi Ned would i be able to try your software please
tas758 at hotmail.com


Re: This is the most active group/list I subscribe to

 

Currently, and as one of the owners, that is my take on things. I myself have also felt as if I am drinking from a fire hose (5") at times.

Splitting the group would require that members subscribe to multiple groups. I'm not sure that that would be helpful.

Hashtags ans subgroups require that member's associate their posts with the appropriate hashtag or subgroup (to some extent - this sort of organization can be done automatically, but it's not much different than threading).

I'd be willing to entertain anything that helps; I'd want to see what mechanism is being proposed and how it would affect the readability of the forum content (pros AND cons).

So far, I think the best solution is for members to read what is immediately of value based on need and interest and ignore the rest. Remember, the content is always available online if one wants to go back and review a thread.

DaveD

On 9/29/2019 9:17 PM, mike watts via Groups.Io wrote:
It's great now.? Don't screw it up.
Mike WY6K


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

On Sunday, September 29, 2019, 8:02:01 PM CDT, Dr. David Kirkby from Kirkby Microwave Ltd <drkirkby@...> wrote:
I am on about a dozen different groups for various things

* Website design
* Graphics
* Keysight groups for VNAs
* Keysight group for LCR meters
* A couple of UK based amateur radio sites
* GNU cash
* SageMATH? mathematics software
* UK microwaves
* HP/Agilent/Keysight (I am owner)
* VNWA

There¡¯s more messages from this group than any other - and possibly all the
others combined. ????

I am not sure if that¡¯s a good thing or not. If the popularity of the list
grows much more, I will probably have to start muting topics.

Maybe if the popularity grows much more, the group owners might want to
consider splitting the group, another group, hashtags, subgroups or
anything else that is needed to keep the volume of emails to an acceptable
level.


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


Re: NanoVNA V2 - I vote for a larger instrument...

 
Edited

I wonder how many actually wants a small form factor.
Me, for one;
* not much space next to PC keyboard

* hands are usually full when going to work elsewhere,
making pocket-size VERY handy.
* with more secure connectors, I could hang
small, light, wireless nanoVNA V3 on e.g. antenna connector,
then access UI from smartphone (carried in belt pouch or another pocket).


Re: NanoVNA-Saver 0.0.12

W5DXP
 

Thanks Rune, it's working well now. The only change I would make is to make the traces on the graphs a little wider. Thanks again, Cecil at w5dxp.com


Re: Another modified nanoVNA software

 

Hi Neb.

PLease send me a copy of the software to palolq(at)ymail.com

73! Palo.


Re: Another modified nanoVNA software

 

Hi neb,

TDR is work well.


Re: This is the most active group/list I subscribe to

 

On Sun, Sep 29, 2019 at 10:17 PM, Stuart Landau wrote:

I agree with you Dave; sometimes it is like "drinking from a fire hose". This
is an extraordinarily?active site; it is difficult to try to read the
messages that interest me.?I don't know what the answer is. I have thought of
getting another email address especially for this group.
Stuart K6YAZLos Angeles, USA
Don't forget there are account settings where you decide whether to receive an email for every individual post, or a single digest each day, or no emails etc etc.

I receive a daily digest, but I seldom even look at it since I am checking the forum site multiple times each day - what a delight to see how active things are, and also to watch the number of subscribers growing as more and more folks find out about the nanoVNA.


Re: errors of "error" models

 

23 : On the Uncertainties of the "Standards" - Part I

@ Jeff Anderson : /g/nanovna-users/message/3294

Hello,

Thank you very much for your most encouraging message !

We much appreciate your interest in our work - thank you.

We also thank you for your most valuable * s p e c i f i c *
inquiries regarding it, by which you give us the chance to
explain it, from a common user's point of view, facupov, as
we always try to do.

Regarding your first question:

JA : "... you mention that the S and O standards have 2
uncertainties each (while the load has 1 uncertainty).
How are you defining these uncertainties? "

- (c) gin&pez@arg (cc-by-4.0) 2019 : start -

allow us, please, to answer its last part as follows:

We are not defining the uncertainty of any "standard".

If the manufacturer of a "standard" is a decent one
then he defines its uncertainties, so we could reservedly
adopt it as a 'standard' and proceed in our measurements
with it.

A "standard" without uncertainties is nothing else than
a load with a nominal value, that is one named with a
value: e.g. a "standard" of 50 Ohm is just a load of which
its "true value" is somewhere near by 50 + j0 Ohm.

How much near by?

As much as it is defined by its manufacturer. If he did not
define how much it is, then we don't know how much.

In this, most reasonable way, we could reservedly adopt
as a 'standard' at DC any common resistor part on which
its manufacturer has put -usually by coded colors-
its nominal value in ohms and its tolerance as an
implicitly minus/plus percent of its nominal value in ohms,
that is : its nominal value and its uncertainty, e.g. as
47 Ohm and 10%, which results, instead of a single
"true value", in unaccountably many values, which they
lie between the lower value or bound of:

42.3 Ohm = - 10% x 47 + 47 Ohm = - 4.7 + 47 Ohm

and the upper value or bound of:

51.7 Ohm = 47 + 10% x 47 Ohm = 47 + 4.7 Ohm

or which they lie in the true closed interval of values

[ 42.3 , 51.7 ] Ohm

Therefore, allow us, please, to think that this example
is most than adequate to show the way in which the
Uncertainty is defined facupov for this resistor in DC:

This is exactly these two 2 values or two 2 errors in
the "true value" of 47 Ohm:

the lower error or value -4.7 Ohm and

the upper error or value of +4.7 Ohm

where, also notice that, please, in this case
these two 2 errors lie symmetrically to the
center value of 47 Ohm.

It is very important for our duty of supporting
the true -without putting it between double " "
or single quotation marks ' '- understanding
of our work to conclude the subject with this
"footnote":

This resistor can be also be considered as a
'standard' with a "true value" of 50 Ohm and
an uncertainty expressed by the two 2 error
bounds of -7.7 Ohm and +1.7 Ohm, for the
lower and upper ones, respectively, and
especially : non-symmetrically, simply because
its "true value" of 50 Ohm with its unsymmetrical
Uncertainty [ -7.7 , +1.7 ] Ohm results in exactly
the same invariant interval for the values of this
resistor : [ 42.3 , 51.7 ] Ohm, as it is defined by
the initial "true value" of 47 Ohm and its
symmetrical Uncertainty [ - 4.7 , + 4.7 ] Ohm.

Finally, a Warning Sign in capitals for the Common User:

THE DECENT MANUFACTURER HAS THE KINDNESS
TO SUPPLY THE UNCERTAINTY INFORMATION IN
ORDER TO BE USED BY THE COMMON USER

So, if either a "common user" feels happy or a Common
User feels unhappy when he ignores this uncertainty then
this is just another matter of taste - he has been warned.

- end : (c) gin&pez@arg (cc-by-4.0) 2019 -

Sincerely,

gin&pez@arg


Re: NanoVNA does not want to start -solved

 

the IP5306 (I2C Version) can be programmed to e.g. go to sleep after 8,16,32 and 64 seconds (8sec, 32sec modes has been reported by nanovna users).
It can be programmed as well to stay on. One can buy as well version, which is already pre-programmed for always on. I assume, IP5303 is not much different.

The always on IP5306 Information:



Well, so all those working "bad clones" with IP5306 have probably IP5306_CK soldered.


Re: Cal-Kit Standards' Definitions

 

I am still puzzling thru this. On page 3:
"As seen the trace is not flowing the circumference off the Smithchart
which must spiral inwards in a progressive way."

.. evidently "flowing" should be "following" and "off the Smithchart"
should be "of the Smith chart".
I >>guess<<: " which must spiral inwards in a progressive way" should
be understood "but is spiraling inwards", e.g.

"Instead of following the Smith chart circumference, the trace is seen
spiraling inward."

.. where this trace is from an unterminated non-ideal cable (not airline),
and changing (50 Ohm) LOAD shunt capacitance value C from 51.8 to
-108.2 improves "calibration".


Re: This is the most active group/list I subscribe to

 

It should be selected from topics and easier to organize

Gyula HA3HZ :-)


Re: Issue with Live USB Ubuntu running NanoVNA-Saver

 

Hi Ron,
I'm not strong on how to get Python set up, so I trust others who are able
to help to chime in. :-) But, do try the following:

- In "setup.py", change "PyQt5==5.11.2" to just read "PyQt5". This *could*
fix the problem entirely.
- If not, after doing the above, in the folder containing nanovna-saver.py,
run "python3.7 -m pip install ."

I hope one of these works for you ... Do report back if it does! :-)

--
Rune / 5Q5R

On Mon, 30 Sep 2019 at 03:43, Ron Webb <bigron@...> wrote:

OK... this probably is not so much a problem with NanoVNA-Saver, per se,
but I'm hoping someone can point out what may be wrong. I have a laptop
that I normally boot Windows 10, from which I run NanoVNA-Saver from with
no issues. Lately, I've created an Ubuntu 19.04 Live USB with persistent
memory, as I don't want to create a partition on my laptop. I have
installed python with all the required modules, including "pyqt5", but when
I attempt to start the program, I get the following error:


Traceback (most recent call last):
File "nanovna-saver.py", line 17, in <module>
from NanoVNASaver.__main__ import main
File "/home/ubuntu/Git/nanovna-saver/NanoVNASaver/__main__.py",
line 21, in <module>
from PyQt5 import QtWidgets, QtCore
ImportError: No module named PyQt5


If I type in "pip3 install pyqt5", I get:

Requirement already satisfied: pyqt5 in
/usr/lib/python3/dist-packages (5.12.1)

So, it is already installed... I'm puzzled... Any ideas?




Re: Issue with Live USB Ubuntu running NanoVNA-Saver

 

in <module>
from PyQt5 import QtWidgets, QtCore
ImportError: No module named PyQt5

If I type in "pip3 install pyqt5", I get:

Requirement already satisfied: pyqt5 in /usr/lib/python3/dist-packages (5.12.1)
FWIW, I see this error, but not consistently, on 64-bit Windows 8.1
while running trivial tests of pyqt5
without NanoVNASaver even installed.<<
As a Python newbie, 3 possibilities occur to me:
1) I read that some versions of pyqt5 have been more stable than others
2) Just as Windows uses your %PATH% to find executables,
Python has its own equivalent, which may be screwed up,
e.g. incompatible versions of stuff being found earlier:

import sys
print(sys.path)
3) relative import bug:


[ A similar problem can occur in C with #include "foo.h" vs #include <foo.h>,
but static C builds force that to be resolved once at build time..]