开云体育

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

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.

Uploaded By: Keystonebart <bdm_brian_meyer@...>

Description:
Another nice case, I purchased and easily installed

Cheers,
The Groups.io Team

Hi Oristo

Yes if you load is also perfect 50ohm but such a load cost many $ ? although the load supplied with the NanoVNA is pretty fine and you correctly mentioned "observe no appreciable reflection" which requires both the candidate cable and load are good quality. Have a look at AC6LA home page about ZPlots and the his coac calbe information where you see the velocity factor which has influence on the delay is frequency dependent. He has a direct graph on this issue
Good luck with your experiment

Kind regards

Kurt



-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Oristo
Sendt: 4. oktober 2019 22:59
Til: [email protected]
Emne: Re: [nanovna-users] Cal-Kit Standards' Definitions



Thanks for the response!

Remember the Electrical delay assumes and ideal 50 transmission line

So, if I

* properly calibrate at the VNA port

* plug in a candidate cable terminated with calibration load

* observe no appreciable reflection



.. then that cable unterminated should be satisfactory for delay testing..

What's the link?

Thanks for the info on the T check.

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?

On Sat, Oct 5, 2019 at 11:25 AM, Bo, OZ2M wrote:

….. When it comes to the NanoVNA numbers may be somewhat confusing. I for one do

have some difficulties sorting one H/W from the other …..

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

Bo, the different hardware is the easiest to sort out if you know the historical background. Here is what I have learned:

1. In 2016 edy555 created the open source NanoVNA project on GitHub. I'm not sure why he did not commercially manufacture the device, but …..
2, In early 2019 hugen cloned the open source schematic, manufactured the NanoVNA with frequency range expansion and NanoVNA Sharp software.
3. hugen's product is the black NanoVNA with shields on CH0 and CH1.
4. Noting the successful and positive feedback from buyer's of hugen's product, other Chinese manufacturers soon started selling clones of the clone.
5. There appeared a white clone with salamander design and a black clone without shields on CH0 and CH1.
6. hugen's clone and all the subsequent clones use the same edy555 schematic design. It is a testament to the robust nature of edy555's design that, performance wise, none of our group member's have been able to demonstrate a difference between the three different clones.
7. In September of this year another NanoVNA was marketed. It is called the NanoVNA-F. The NanoVNA-F is RTOS based, has a 4.3" display, and has a upper frequency limit of 1 GHz. It hasn't been out long enough for end user's to give their reviews but that should start happening soon. Out of the box it does not have a software program ready to use, such as NanoVNA-Sharp or Rune's nanoVNA-saver.
8. edy555 has asked hugen to re-name his product to NanoVNA-H to distinguish it.

So as of now, there are only two hardware versions being sold: The NanoVNA (-H) and the NanoVNA-F. Both edy555 and hugen have started development on a version 2 device, so "stay tuned to a theater near you".

The different firmware versions is another can of worms that hopefully someone else will open.

Herb

On Sat, 5 Oct 2019 at 16:08, <in3elx@...> wrote:

How do you try the edy555 firmware since it is not a .DFU?

DfuSe_Demo_V3.0.6_Setup.exe also installs DfuFileMgr.exe,
which can convert to dfu.

I tried but something is wrong.
I would like to try a tool for the original ady555 binary.

I just did this on Windows 10.
First, get the edy555 0.2.2 file:
from there, click the 'releases' icon near the top
the latest release is 0.2.2
click 'nanovna-firmware-0.2.2.zip' to download it to a place you
will remember. I put mine in c:\addons
Next, unzip it in a place you will remember :-)
I put mine in C:\addons\nanovna-firmware-0.2.2
Next, convert the .bin to .dfu
Start > STMicroelectronics > Dfu file manager
There are two choices. We want to GENERATE a DFU file from a BIN
file. Click OK.
On the right side, half way down there is a button for S19 or Hex. Click that.
Navigate to the place you unzipped 0.2.2, and go down into the build
directory. On my machine that is
C:\addons\nanovna-firmware-0.2.2\build
Click on ch.hex, and then Open.
Click Generate
You will be asked to save the file. I called mine nano_0.2.2.dfu,
and saved it in the same directory.
You get a message 'Success for Image for alternate setting...'
Click OK.

Now I have C:\addons\nanovna-firmware-0.2.2\build\nano_0.2.2.dfu

I used this dfu file to flash the NanoVNA with the DfuSe Demo 3.0.6 program.
I hope that helps!

Ciao!
--buck

On Sat, Oct 5, 2019 at 01:13 PM, Oristo wrote:

do SA612s not feed I and Q into ADC?

Indeed. Two separate signals. For IQ mixing the LO inputs would have to be 90 degrees out of phase and the input must be the same. Both are not the case.
The nanoVna needs to measure two independent signals at the same time. Actually three. But the adc is stereo so one input is switched between reflection and transmission signal

* does not mixing always generate sum and difference frequencies..??
sin A cos B = (sin(A + B)+sin(A - B))/2

Indeed. Here the difference is zero e.g. DC and the output is averaged which is a very effective low pass filter so the sum at 10kHz is eliminated
No need for other filters

Hi Erik -

Thank you!

I have not yet looked at nanoVNA firmware
and supposed more similarity to SDR than evidently exists.

The DSP does quadrature mixing down to DC
so there is no mirror signal to suppress

I need to do homework here:
* do SA612s not feed I and Q into ADC?
* does not mixing always generate sum and difference frequencies..??
sin A cos B = (sin(A + B)+sin(A - B))/2

On Sat, Oct 5, 2019 at 02:34 PM, Oristo wrote:

How do you try the edy555 firmware since it is not a .DFU?

DfuSe_Demo_V3.0.6_Setup.exe also installs DfuFileMgr.exe,
which can convert to dfu.

I tried but something is wrong.
I would like to try a tool for the original ady555 binary.

Edy555 has implemented in his GitHub nanoVNA repository a command to set the threshold for switching to harmonics mode
Command
threshold {Frequency in Hz}
The default is 300MHz.
After changing you can use the save configuration command to permanently store the new value
This greatly simplifies testing if your SI5351 has difficult reaching 300MHz and if so, provides a easy workaround
I can not test now. Maybe tomorrow

On Sat, Oct 5, 2019 at 01:10 PM, Oristo wrote:

It might be helpful to newcomers
if these links could be put into the footer of each message.

Let me know what is missing (bottom Wiki entry):

I like it. I've been using a VM with Ubuntu 18.04, so this gave me a chance to try Windows 10.
I'm already a DIYer who uses STM chips, so flashing firmware is pretty comfortable to me.

What I am hoping for is that the group owner puts a footer in each forum/mail message so that everyone will be aware of the wiki, the files section, and your page.
--buck

I've been using a wooden toothpick. Works great.

--
Phil - AD5X

@Oristo

The help file refers to quadrature sampling done with the SI5351 and the two SA612.
This is wrong. Some of the references go to IQ downconversion for SDR but the nanoVNA works differently
The two SA612 convert two uncorrelated signals ( the bridge unbalance and the power reference) to the 5kHz IF frequency send to the adc's
The DSP does quadrature mixing down to DC so there is no mirror signal to suppress