开云体育

Ok, ya got me. Reading the introductions to the two papers left me going, huh? But I do hope it is easy, and that you do publish a simple method.

36 : Primary AnyVNA Measurements

35 : Straight In The Heart of The Matter - 6 October 2019 :
/g/nanovna-users/message/4177
@Gary O'Neil

Hello Gary,

Well, to start from the beginning, would you clarify for us,
please, if would you unreservedly agree with us on that :

"
Primarily, anyVNA measures
( Amplitude Ratio , Phase Difference )
couples in terms of
Frequency
"
?

Regards,

gin&pez@arg

36

It would seem sensible to add a reciprocal command if at all possible.

Particularly if NanoVNA-H V2 may have no touch screen
or is controlled via BlueTooth or USB from mobile devices
(as now by WebUSB app with recent Android versions)

On Sun, Oct 6, 2019 at 10:49 AM, <erik@...> wrote:

no reciprocal command to upload data from the PC to the nanoVNA

It would seem sensible to add a reciprocal command if at all possible.

Anything to avoid having to physically manually enter long sequences is very desirable, especially as it's only possible to retain a small number of configurations internally.

The ability to reload (or clone) settings when new firmware is installed or the memories are wiped would also be handy.

Regards,

Martin - G8JNJ

Please have a look at the firmware.
The "save" command saves the internally measured calibration data to the internal save location [0-4], recall is the reciprocal command to load calibration data from the internal save location.
The "save" command does NOT upload calibration data from outside the nanoVNA into the nanoVNA
The "data" command downloads data from thenanoVNA to the PC, there is no reciprocal command to upload data from the PC to the nanoVNA

you're measuring your inductor through two transformers (coax cables). So, the capacitance shown on the display of NanoVNA is capacitance on the cable input, but not on the inductor. When you connect unmatched circuit on the end of coax cable, the coax cable starts to works as RF transformer. It transforms impedance. Read about transmission lines...

30 : our final report 1
33 : the mathematical expressions

[ for the sake of completeness of the topic, the contents of this
[ message are just a repetition of the following two 2 messages:
[ 4 October 2019 : /g/nanovna-users/message/3989
[ 5 October 2019 : /g/nanovna-users/message/4068
[ which we wrongly sent outside of this topic
[ -
[ please accept our apologies

30 : our final report 1

29 : ann : our nanovna will be evaluated tonight :
/g/nanovna-users/message/3867

hello all,

this is our final report on the comparison of our
[nanovna] and [vna] in terms of frequency

1 : for nominal values without uncertainty :

red : nanovna - blue : vna

r :
x :

after all that said, accept, please, our humble - but sincere - congratulations

sincerely yours,

gin&pez@arg

30

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

33 : the mathematical expressions

hello,

allow us, please, to emphasize that the mathematical
expressions we used for:

30 : our final report 1 - 4 Oct 2019
/g/nanovna-users/message/3989

are just those mentioned at:
16 : 27 September 2019
/g/nanovna-users/message/3161

that is the ones shown at:


sincerely,

gin&pez@arg

33
30

Hi,
I received my nanoVNA a couple of weeks back, and since then, I am trying to improve my understanding of RF and basic concept using this wonderful tool.
I am trying to understand the behaviour of an inductor that I plan to use as a chocke for an RF amplifier. I wound the inductor over an FT23-43 ferite core, and mounted it in an S21 mode as seen in photo "DUT FT23-43 Inductor".
I used nanoVNA Saver excellent application to sweep from 50KHz to 300MHz, and included the output S2P file "13uH FT23-43 Ferrite Inductor".

Out of this test, I got multiple questions around basic RF concepts I wish I can find answer for it from more experienced group members:

1) From the S11 smith chart (photo nanoVNA S11 Smith S21), and from the nanoVNA Saver displays, I see that the inductor turns into capacitor around 42MHz onward. I would expect this due to inter winding capacitance. However, I would expect that the S21 attenuation starts to reduce as we go beyond this frequency. However, I see that the S21 attenuation remains constant at -21db till 300Mhz. How come?

2) As I understand it, -21db is around 1/100 of power attenuation. I made an oscilloscope setup (photo nanoVNA S21 CW 60MHz Osc Connected) to see what is actually going on. Introducing the oscilloscope measurement does not seem to affect the reading as at CW=60MHz, it shows still -21dB of attenuation.
Looking at photo "Oscilloscope", I see a voltage attenuation of 20.
I thought that -21db expressed in voltage as a drop of 1/10 requires same input and output impedance, which is not the case. The input impedance at 60MHz is 972.37-j398.09 while the output impedance is 50Ohm of the S21 port of the nanoVNA. Any idea what is going on?

35 : Straight In The Heart of The Matter

@Gary O'Neil - 6 October 2019:
/g/nanovna-users/message/4169

Hello Gary,

Well, to put it simply : in our small world, your
last message sounds really Great ! Thank you
very much; indeed.

OK then. But, it would take some time, in order
to reply you - in a sequence of parts, of course.
Therefore, please, stay tuned.

Kind regards,

73

nikolitsa oe3zgn|sv7dmc & petros oe3zzp|sv7bax @ arg iaoi nfi

35

Pretty sure nanovnasharp does this.
Tried decompiling the thing but im no coder so all i found was this
private void save0Button_Click(object sender, EventArgs e)
{
this.controller.SendDataToCom("save 0\r\n");
this.saveGroupBox.Visible = false;
this.stateGroupBox.Visible = true;
this.responseGroupBox.Visible = true;
this.languageGroupBox.Visible = true;

with save 0 to 4
and then recall 0 to 4

All working well.
I merged the edy555 additions with my modified scan command and made the build firmware available in the firmware section.
Build 0.2.2_1
/g/nanovna-users/files/Firmware/NanoVNA%20firmware%20build%20by%20Erik
Usage (assuming your SI5351 supports up to 250MHz):
threshold 250000000
saveconfig
Remember to do a saveconfig after updating the threshold otherwise the setting will be lost after reset

Hello,

This email message is a notification to let you know that the following files have been uploaded to the Files area of the [email protected] group.

• /Firmware/NanoVNA firmware build by Erik/Release 0.2.22_1 with modified scan command and harmonic threshold setting.zip

Uploaded By: erik@...

Description:
Release 0.2.2_1 from edy555 with modified scan command to be compatible with TAPR VNA software for PC allowing unlimited scans and added harmonic threshold command Usage: threshold 250000000 saveconfig Without saveconfig the updated threshold will be lost after reset

Cheers,
The Groups.io Team

On Sat, Oct 5, 2019 at 07:21 PM, W5DXP wrote:

Where does it tell how to hook those 4 wires up to a NanoVNA? NRST->RST?
TCK->SWCLK? TMS->SWIM? GND->GND? How about SWDIO on the ST-link?

ST-LINK uses just 2 wires: SWDIO and SWCLK.
Also you're needs to connect VDD to 3.3V and GND to GND.

You can also connect 5-th wire RST to RST, but it is required only when SWD pins are reprogrammed in firmware. NanoVNA doesn't use SWD pins, so you can connect with STLINK with no need for RST connection.

Here's what can happen:

Someone has an eBay account and they decide they want to make some quick money from it. Or they hijack an account for the same reason.

So they'll sell something at a "price that's too good to be true." They sell a bunch of an item that they're never going to ship out. And they set it up so that there's a long time before you're supposed to get it. They are counting on at least some buyers forgetting about it until it's too late to ask for a refund. They get as much money as they can out of their PayPal account before they're caught and shut down.
And in many countries a few hundred dollars goes a long way! Often they don't need to get many buyers to make good money for themselves.
It sounds like that's what this is. So make sure that you don't forget to make a claim against it when the time comes that you can.

For something suspicious like this I usually put it in my calendar on my phone, set to a date a couple of months in the future with a notification that reminds me to check on it. I was duped once, but now I set a notification in the future so I don't forget.

I use the stylus from Galaxy Note phone...never did use it with the phone.

yin, gin & pez@arg

Thank you for your gracious response and compliance to my request.

In my efforts to understand your project, I think I may have had a bit of an epiphany that may start me toward understanding your needs.

I hope my response here will be of some help toward getting what I believe you are looking for from the NanaVNA users on this forum and possibly elsewhere as well.

I will begin by first referring you to page 12/15 of your presentation document:

I believe the box on the right of page 12/15 describes a four step process that is the functional flow through the software tools you have developed, and have been describing, To summarize the steps, I interpret them as follows:

1)The configuration data for the VNA measurements is entered via the (Physical State) GUI illustrated on page 4/15.
This GUI tool looks like it performs the identical function as the NanoVNA configuration setup when connected to a PC. There is no provision in this GUI tool for the input of Calibration Standards correction coefficients. If my understanding is correct, the omission of calibration coefficients is intentional. Please comment on this and correct me on this assertion. I sense this is a point you wish to make visible without ambiguity or confusion.

2) The results of four VNA measurement sweeps of a short circuit (SH.SC), an open circuit (OP.SC), a load standard (LD.LD), and a device measurement (ME.ME) are collected as 4 independent files and formatted to the input specifications of the REGION tool. These are the tasks of the ANALYSE tool.

A fifth file (INPUT.TXT) is externally and independently created which describes the magnitude only uncertainties to be used by the REGION tool. It is not clear how the uncertainty parameters are determined or specified, but they do not appear to be standards coefficients and are described as uncertainties in magnitude only. I do however suspect that they are intended to be used to statistically bias the measurements of arbitrary calibration devices (equally to or as an alternative to the use of characterized standards); and these are used for the computation of error regions surrounding each of the measured (raw) complex data points. These assertions also need corrected or made clear to remove ambiguity and enhance understanding.

3) Utilizing the output created by the ANALYSE tool; the REGION tool computes DER's and DEI's and outputs the results in both rectangular and polar form for each of the measurement frequencies.

4) Finally; the DERDEI tool formats and plots the computed output results of the REGION tool which then yields the graphical presentation that reveals the bounded region of uncertainty of the measurements.

My comments:

What I think I have been able to comprehend to this point may be close enough for me to offer a few comments that may prove useful toward reaching your goal. While it still remains unclear; I will state your goal here as a desire to obtain multiple random test cases using your software to estimate VNA measurement uncertainty. My guess is that the randomness of measurements made with uncharacterized DIY calibration standards is of special interest/benefit to you in the evaluation and defense of your software and associated algorithms.

If the software flow is as I have described, there may be some minor revisions you could make which would greatly simplify and expedite getting the data you are pursuing.

Referring back to step #1 above; the (Physical State) GUI.Input tool looks redundant to the tasks performed by VNA users traditionally and generally. It appears however that it outputs data in a format that satisfies the input requirements of your ANALYSE tool. There are many sources of S-parameter data, and the RF Test equipment industry has adopted, or at the very least supports Touchstone; a simple, text readable, defacto standardized approach to formatting, porting and saving S-parameter data. I have attached a copy of that standard here for your reference. A simple one line header (e.g. # MHz S MA R 50 ) provides all the information required to interpret the data that follows.

If your REGION tool can be easily modified to accept Touchstone formatted data as its input, you could do away with the GUI.Input and ANALYZE tools altogether, since their task is simply to gather and format the data used in the REGION and DERDEI tools. More importantly; you would gain easy access to more data than you will want or need, as libraries of Touchstone formatted S-parameter data exist in abundance. Furthermore; the ANAlYSE tool is also used to gather data via a GPIB iinterface. This too is not required, as it is only the NanoVNA's (or any VNA) data that is of interest to you, and GPIB is utilized in complex test or volume manufacturing environments, and rarely (if at all) in individual user applications.

Additionally; If modified as described, the REGION tool could be easily combined with a simple input GUI that enables a user to input the four input data files and the parameters necessary to compose the uncertainty limits file.

Appending the DERDEI tool to the REGION tool and compiling them as a single executable would result in a compact and easy to distribute and use utility that would be better positioned to gain exposure and attention across the RF test and measurement community.

Alternatively; your REGION tool if made Touchstone compatible, is sufficient (without need for distribution) to enable you to specify the requirements of random measurements that you may desire of various component types such as Antennas, components, Filters, Amplifiers, etc, and even DIY calibration kits as needed throughout the evolution of your research; leaving your team to assess, compare, and refine the output of the DERDEI tool.

I look forward to your response and perhaps a better understanding of how or if I can advance to a level of understanding where I am able to contribute in a meaningful manner.

--
73

Gary, N3GO

Hi,I have just tried to run your latest build for the Android app and find it is still trying to access the internet at startup to this address:? ?172.217.1.10:443
This is owned by Google. Does your app use Google analytics???
The app will not run until I allow network access.? Can that be changed?
Thanks,Larry


On Sat, 5 Oct 2019 at 9:59 AM, cho45<cho101101@...> wrote:

Can you please add an exit or quit command to the menu so we do not have to
press the Android home button to exit.?

I will add.

Also, is it possible to create a standalone Android app so there is no need
for network access?

The resource is in the application and Internet access is not required.

In fact, we have confirmed that the application works without a network connection.

However, I still have permission for INTERNET access.

I think on the CAL line, reset should be the very first item opposite CAL and everything else is below. Why? You need to do a reset before you do the rest of the cal steps.?
Leave 'calibration' at the bottom as you rarely use it.?
Also, as soon as you press Done, you get the save menus, no?
There is one more entry after the DFU button

That's it for now. Looks good!

On Sat, 5 Oct 2019 at 6:09 PM, Oristo<ormpoa@...> wrote: Annotated menu map for updated firmware, take 1:


* broken branch FORMAT->LOGMAG requires CSS fix, may take awhile..
* links and help text not yet reworked..

I mainly want feedback about missing menu branches and/or leaves

Does anyone know why ELECTRICAL DELAY is under SCALE
instead of e.g. CONFIG?

Hip Hip Hurra
A bright invention
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Torbj?rn
Toreson
Sendt: 5. oktober 2019 14:42
Til: [email protected]
Emne: [nanovna-users] Screen stylus tip

Just a little screen stylus tip (in double sense).

Torbjorn