开云体育

I just released NanoVNA-Saver 0.1.5:



Release notes:
This release, after a short break in the release schedule, offers a few new
features and improvements:

Configurable Markers
There are a number of new configuration options for markers:

The size of the markers can be changed under Display Setup,
Marker numbers can be displayed in the charts,
Marker data box headings can be coloured or not, depending on user
preference,
The data displayed for markers is now configurable
Impedance Analysis
The Time Domain Reflectometry window now has a display of an impedance
transform, showing the calculated impedance of the transmission line the
NanoVNA is looking at from the calibration plane onwards.

New analyses - and automatic running
The Analysis window has two new analysis options, peak search and VSWR
analysis. It also adds the option to run the analysis automatically
whenever new data is acquired, for example for adjusting filters.

Frequency display changed
DG5DBH kindly sent me updated functions to display frequencies on GitHub.
You can still enter frequencies in the manner you are used to, as Hz, kHz
or MHz, but now calculated or read frequencies should more consistently be
displayed in a nicely formatted way.


As ever, dear mailing list users, I very much look forward to your
comments, feedback, suggestion and bug reports. I already have a number of
things I want to try to get done for next week - so it shouldn't be a
2-week gap this time around! :-)

Thank you to all the testers who helped me fix the bugs in the first two
alpha releases of this!

--
Rune / 5Q5R

return loss gets poorer > 100MHz.

It looks better without USB connection.
Adding a ferrite core improved results with USB connection:

Hi Gabriel -

From those graphs it's obvious your calibration is way off because S11 exceeds
0dB (meaning outside of the smith chart) by quite a bit. If you plot the smith
chart you I'm guessing it will be all over the place, rather than making
circles around the center like it should. Please show the smith chart instead
next time because it's hard to see what's really going on with those graphs
(impedance is always a 2 dimensional quantity).

I guess you meant message 6456, and agree that was a poor choice of graphs.
I do not calibrate for such a wide range. So, second attempt:
Looking at logmag for CH0 and CH1 terminated by 50 Ohms
(AKA Isolation), then you will notice that return loss gets poorer > 100MHz.

Dear Hans,

many thanks for interesting and useful information. My initial suggestion
of a scheduled scan has exactly this purpose, to eliminate the influence of
cables or operator.

I think the RF on the USB cable wouldn't be an issue. The TX level of
NanoVNA is very low. Some ferrites can be added on the USB / UTP cable.
The UTP cable can be installed perpendicular to the antenna to minimize the
influence.

However, I'm still thinking the software solution, if possible to
implement, would be more elegant: a scheduled scan followed by a pause.

Andrew,
The support group for the NanoVNA-F that you own is located at /g/nanovna-f . You should leave a message on the board there ( /g/nanovna-f/messages ) and hopefully the developer of the NanoVNA-F will respond. The only documentation I was able to find was the same quick start guide you referred to at /g/nanovna-f/wiki/home . Hopefully over time the members of the nanovna-f group will start to produce better documentation for the NanoVNA-F. We went through similar lack of documentation when the NanoVNA was first marketed.

- Herb

So, it has been less than a month and my 4.3 inch long little wonder
arrived from Alixpress today. It had a Quick Start Guide lol. Are you
kidding me? It might as well be encrypted.

Has anyone come up with a video or true quick start guide for calibration
and basic antenna analysis?

Andrew
W1RNY

Andrew Baer, M.D.
301-355-9999

You may also need to add the try group to your user profil. I found that I needed to on RaspberryPi.
M Walter

Hi Oristo
In the help file search in index for "trace types" there all the various and very many trace types are described also custom traces. The trick is to double click on any trace type name e.g. Smith on the lower line, and that mean any of the trace name, and the page come up with all the trace settings, and in the six wide prompt line you decided what you want to have displayed form a long drop down list e.g. dB Smith, phase and so on. In the slim prompt line you decide to what the representation just chosen must belong to, from another long drop down list S21, S11, S12, S22 and so on, and here you find the 6 custom traces. Notice if using subexpressions all 6 custom traces share these subexpression, but the top Expression line are fully individual, and in most cases you can hold the entire expression in that line.
Each custom trace can be given a Caption name, which is shown along the custom traces in the lower trace line. Here is a refinement for all traces as a right click on the trace name, e.g. the custom trace caption name and on other traces e.g. S11, you get the option to save to s1p.
For a custom trace to open the trace settings window to e.g. change color, you mist double click on the trace representation e.g. dB, to the right for the caption name. If you double click on the caption name the Custom trace is opened.
There are many other feature by right clicking around.
If the help file will not open as an old fashion Windows help file, I have a little tool which in window 10 open up for the chm files.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Oristo
Sendt: 4. november 2019 23:53
Til: [email protected]
Emne: [nanovna-users] VNWA software #calibration

If you have calibration data as impedance and delay, but want S11 s1p format, then VNWA software can generate it, according to Kurt Poulsen.

in the VNWA software you simply open a custom trace

I did not expect this "simply" to be so tricky. It appears that VNWA documentation >>never explains<< how to open a custom trace window.

Help has a section about what to do when already in custom sweep window, but getting there may be something that lucky folks are born already knowing...

Also, Frequency Range, under Settings, >>does not set Start and Stop<<, only Linear vs Log vs Listed...?

I guess this software may discourage many from purchasing the supported hardware.

The answers:
* right-click mouse button in the main window and select Trace Options,
which launches a dialog box titled 'Display Settings'
Custom is selected by scrolling down in small box next to color sample for Trace 1-6

* left double-click near Start or Stop frequencies will launch 'Input' dialog box
to set those frequency values. Sweep Mode is also selected here,
making Frequency Range option in main window Settings less than useful.

in the Expression line write s_load or s_open or s_short or
s_thrumatch or s_thru then the trace is shown according for the custom
trace to be shown as you like in Smith, dB of what ever representation
then to save directly as s1p file by a right click on the trace and use the "Export to s1p file" function.

Well, right-click on trace launches another dialog box, but no options for saving it

apparently "facupov" is pseudo for "from a common user's point of view",

From A Common User's Point of View

Sorry for question, but what means word "facupov"?
It is often mentioned here, but I cannot understand what you're talking about...

Just tried to google it, but unfortunately with no success

From: Ady, YO2NAA: Your suggestion to use a USB extender is a good one, thank you.

What about RF on the USB cable?

Rune,

I attached a screen shot of the image you ask for. That is a full screen of a scan I saved. I noticed when I first loaded the file the image fit the screen perfectly but when I added Marker3 the image changed size to where you see it.

I fi I can supply any additional information will do my best to do so. This is running Win7 with the latest upgrades.

73,

Wes
WA5TKU

If you have calibration data as impedance and delay, but want S11 s1p format,
then VNWA software can generate it, according to Kurt Poulsen.

in the VNWA software you simply open a custom trace

I did not expect this "simply" to be so tricky. It appears that
VNWA documentation >>never explains<< how to open a custom trace window.

Help has a section about what to do when already in custom sweep window,
but getting there may be something that lucky folks are born already knowing...

Also, Frequency Range, under Settings, >>does not set Start and Stop<<, only Linear vs Log vs Listed...?

I guess this software may discourage many from purchasing the supported hardware.

The answers:
* right-click mouse button in the main window and select Trace Options,
which launches a dialog box titled 'Display Settings'
Custom is selected by scrolling down in small box next to color sample for Trace 1-6

* left double-click near Start or Stop frequencies will launch 'Input' dialog box
to set those frequency values. Sweep Mode is also selected here,
making Frequency Range option in main window Settings less than useful.

in the Expression line write s_load or s_open or s_short or s_thrumatch or s_thru
then the trace is shown according for the custom trace to be shown
as you like in Smith, dB of what ever representation
then to save directly as s1p file by a right click on the trace and use the "Export to s1p file" function.

Well, right-click on trace launches another dialog box, but no options for saving it

I don't entirely agree, Erik. GitHub issues can easily be marked as
"enhancement" - I certainly use that a lot to weed out what I need to work
on, and what's optional. As long as you're polite, descriptive, and don't
expect a response from a busy author, adding feature requests can be fine.

I do note that both edy555 and hugen79 could benefit from setting up bug
and feature request templates on their respective githubs, to make it
easier to distinguish.

--
Rune / 5Q5R

PLEASE only give feedback on what is supposed to work but does not.
Don't submit hundreds of new feature requests as there is only one hugen79 and one edy555 (ttrftech)
Github can not be used as some kind of voting system for new features. There exits better solutions
--
Erik, PD0EK

That UTP cable is just as much detuning your antenna by common mode current as
feeding the antenna by coax without balun would do.
Common mode current via the NanoVNA and the UTP cable to ground has just the
same detuning effect.

That detuning should be investigated;
I suppose it depends on match between nanoVNA and antenna.
For antennas typically using a balun to feed coax, then nanoVNA should have the same.

Perhaps running several turns of cat6 thru a ferrite core near the nanoVNA would mitigate.
Supposing that one has some other indication of antenna tune at the shack end of coax,
could useful experiments to minimize nanoVNA + USB-via-cat 6 impacts
be conducted with antennas conveniently lowered?
I have no feel/experimental results for Yagi proximity to earth...

I am wondering what mechanism causes S11 impact depending on a cable (the
rotation speed versus frequency is roughly proportional with the length of the
cable) but with a different rotation speed?
I'm observing a sin(f)*e(f) effect
Could this be the cable capacitance????

Rotations are mostly by cable delay,
and I guess that differences from 180 degrees
between rotations for open and short measurements
are provoked by non-ideal open and short calibration characterization.
This can be simulated e.g. @ 5 MHz with 2m LMR-400
by substituting 3.5 wire turns for short and 390pf for open.

I intend to experiment for reducing this using VNWA software..

Hi Andy,


I cannot support your last statement:

> The UTP cable will have some influence on the antenna but not important I think

That UTP cable is just as much detuning your antenna by common mode current as feeding the antenna by coax without balun would do.
Common mode current via the NanoVNA and the UTP cable to ground has just the same detuning effect.

If in doubt, see attached powerpoint.

NanoVNA grounding by holding it in your hand can be avoided by mounting it on a PE board as shown in the pic.
The 6mm PE board was hot air bent a bit in a vice, because of the inclined SMA connectors. The PE board was
left long for holding it without touching the NanoVNA. Insulation is more practical than needing a suitable balun
for each antenna situation.

73, Hans
DJ7BA



-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von Ady, YO2NAA
Gesendet: Montag, 4. November 2019 15:12
An: [email protected]
Betreff: Re: [nanovna-users] Storing and recalling scan later via Nano VNA saver (or similar) #internals #consolecommands

Usually, the distance to the antenna feed point is 15-20m in my case, but it can be more on high towers.
Your suggestion to use a USB extender is a good one, thank you. It will work great for YAGIs on a pole.

However, in the case of a wire dipole, all the UTP cable weight will put a heavy load on the NanoVNA's USB and SMA connectors, unless the UTP cable is tied up to the antenna using nylon rope. The UTP cable will have some influence on the antenna but not important I think.

On Mon, Nov 4, 2019 at 3:45 PM Oristo <ormpoa@...> wrote:

Install the antenna on the working position

How distant is working position?
USB extender up to 150ft costs < US$10

--
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.