开云体育

Where can I find the nanoVNA-App software you speak of? I don't find it with a web search. Does it have a different name under which I might find it?

TNX

Ian,

I have the 2plus4 VNA and found the nanoVNA-App for Windows the "best" software tool for my needs. The VNA-QT is vy simple, the VNA-Saver does sweep -slooooow- and I do not like the trace resolution. Mr. Smith LabView soft is vy nice but more for testing C, R, L, Xtal etc..to confusing for me...and have other nice tools for those measurements.

Using the VNA here for RF-filters, Duplexers, Diplexers, Isolators, Antennas, Tuner and LPF-Alignment, Attenuators etc etc.....

The 206Version of the nanoVNA-App does not show the -errorbox- on startup here, and I had to find out a Firmware, which works with the 2plus4 and the App. This is a version from
Dislord V2Plus4 v1.0.64 noFPU.bin ( thank you Dislord) and this combo does vy well here. Maybe you will give it a try ?

To OneOfEleven, sri that this real fine software is no more in your line of support .... but I know the stressing demand of some users is frustrating.... all the best for you !

Kind Regards
Helmut

The mA referred to is the programmable current drive strength from the output device of the si5351, which is related to the output power at the source port.
73, Don N2VGU

On 03.07.21 04:02, Anne Ranch wrote:

When I received my hardware I downloaded and had running "nanoVNA-saver" as expected.
That was several versions of my OS - Ubuntu - ago.
Now I am on 21.04 , following same "git - hub" download instructions and so far no "saver" .
Since "nanoVNA-saver " is written in python I added several python packages to my current OS , but still no go.

If you don't want to cope with python's dependency system, the you can
also try the all in one binary blobs.



Download and unzip the file. On MacOS and Linux you will have
to make the extracted file executable via 'chmod +x file'.
Then you can execute that binary.

ciao
Holger, DG5DBH

Just another little bug in the NanoVNA-App software Ian.

If I were to write it again I'd do things a little differently, such as make it much easier to follow and edit the source code.
It started as just a simple little piece of test software for my own use, but kept getting requests to develop it further, so I did (without much thought of how it's laid out etc).

Thanks for your response. I got a bit confused because units are in mA and
usually power units are dbm or dbd, or in watt. Thanks a lot for the
clarification. I will leave it in auto for the present time.
Best regards

this option not for battery calibration.

NanoVNA use si5351 generator, it allow generate 4 power level signals.
For some measures better use max power setting, for some less.
Select power option need before calibration!

Good evening everyone,
I bought a NanoVNA-H from a fairly well-known Asian site. It was delivered to me on time, with the two cables with SMA connectors and the "open" "closed" and "load" calibration plugs.
I have performed a firmware update to version 1.0.45 as of January 30, 2021.
I observed that in the new menu there is a Power calibration option. Could someone explain to me how to properly calibrate the internal battery of the NanoVNA-H from its menu?
Thank you in advance for your comments and advice.

Mine has a STM32F072CBT6, which - according to the data sheet - offers 128K.

And even if you have a ..C8 device, it usually typically has 128K.
In automotive electronics we call this "umbrella device", the supplier just builds a generic chip and names it differently depending on what you ordered - in most cases the devices are not even screened and selected.
No need to worry, even the original FW is always >64K.

Hi Anne,
nanovna-saver doesn't need to be installed on Linux, just install the right modules (use pip, this will fetch the newer packages, you don't need to remove the older ones with apt remove ...) and run it with "python nanovna-saver.py" (assuming you have python3 set as default).
->
This has the advantage that you can easily do small changes and test the program immediately.

First let me answer two of you questions:

3. If successfully updated - how do I " manually reset" ?

Switch off and switch on again - voilà!

I have found that I have to "start/run" "nanosaver" AFTER boot is done , hence not directly after

it was downloaded / installed.

No, nanosaver doesn't wait for boot is done, boot takes just 1 second. BUT - the FW uses USB serial emulation (that's good) and announces itself as being a modem (that's bad) and Linux's ModemManager grabs this "modem" and holds it for half a minute until it detects that's not a real modem (that's ugly).
This issue is found in many USB serial implementations for STM32 (e.g. also BlackMagic probe). But we're lucky because this issue can easily be fixed: I've submitted issues to hugen () and DiSlord () as well as a PR ().

But now for your main concern, how to update the FW:
Proposed you're talking about the NanoVNA-H (the original device with the small 2.8" screen) and working under Linux then it's easy: just get the source of the FW you want from GitHub (either hugen's version from , latest is 1.0.45 or the bleeding-edge version 1.0.65 from DiSlord ). Then easyly type "make" to build the FW, enter dfu mode and type "make flash" to program - that's it!

If you do not like to build it on your own, just use the command from the make that is "dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D <YOUR_FW_VERSION.bin>"

dfu-util tells you how to use it:

dfu-util -h
Usage: dfu-util [options] ...
-h --help Print this help message
-V --version Print the version number
-v --verbose Print verbose debug statements
-l --list List currently attached DFU capable devices
-e --detach Detach currently attached DFU capable devices
-E --detach-delay seconds Time to wait before reopening a device after detach
-d --device <vendor>:<product>[,<vendor_dfu>:<product_dfu>]
Specify Vendor/Product ID(s) of DFU device
-p --path <bus-port. ... .port> Specify path to DFU device
-c --cfg <config_nr> Specify the Configuration of DFU device
-i --intf <intf_nr> Specify the DFU Interface number
-S --serial <serial_string>[,<serial_string_dfu>]
Specify Serial String of DFU device
-a --alt <alt> Specify the Altsetting of the DFU Interface
by name or by number
-t --transfer-size <size> Specify the number of bytes per USB Transfer
-U --upload <file> Read firmware from device into <file>
-Z --upload-size <bytes> Specify the expected upload size in bytes
-D --download <file> Write firmware from <file> into device
-R --reset Issue USB Reset signalling once we're finished
-s --dfuse-address <address> ST DfuSe mode, specify target address for
raw file download or upload. Not applicable for
DfuSe file (.dfu) downloads

As a suggestion, not a complaint
Number 1 concern in applying / using ANY antenna tuner
assume you start working the variables ( knobs / software ) TOTALLY out of reasonable SWR.

Any modern TX will tolerate that
BUT
low power , meaning input , device likes nanoVNA WILL DEFINITELY result
in proverbial ( and for real )
"plug it in and watch for smoke"

So what I am saying – the interface to the nanoVNA has to be “high power” protected.

Second – and purely personal opinion – you are operating , not designing an antenna system, hence you are in “power mode” and simply looking for “best match” irregardless how it is done .
Your system should look for best match and IMHO it is not necessary to know all the “bells and whistles” how it is getting low SWR.
But as a demo / teaching aid - go for it.

Anne,
You've posted 3 messages so far but you have not stated the model of nanovna you have, the current version of it's FW, nor the operating system/PC you're using.?
Looks like you're on Linux, so yes, place the device into dfu mode using the menu.?
This topic has been discussed many times in the forum messages.?
Please use the forum search tool and search for keywords of Linux and dfu-util
Read my Search help file in the wiki, it's the very first entry.?
Cheers,?Larry


On Sat., 3 Jul. 2021 at 11:48 a.m., Anne Ranch<anneranch2442@...> wrote: OK, let me stay here
Found dfu-util and now have TWO DFU devices and trying to retrieve? nanaVNA firmware and do not know which "DFU device " to use




qe@qe-desktop:~$ sudo dfu-util -l -v
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Found DFU: [0483:df11] ver=2200, devnum=13, cfg=1, intf=0, path="1-1.3.3", alt=1, name="@Option Bytes? /0x1FFFF800/01*016 e", serial="FFFFFFFEFFFF"
Found DFU: [0483:df11] ver=2200, devnum=13, cfg=1, intf=0, path="1-1.3.3", alt=0, name="@Internal Flash? /0x08000000/064*0002Kg", serial="FFFFFFFEFFFF"

Just read the Absolute Beginners Guide in the Files section of this group. It will tell you how to update the firmware.

Roger

OK, let me stay here
Found dfu-util and now have TWO DFU devices and trying to retrieve nanaVNA firmware and do not know which "DFU device " to use




qe@qe-desktop:~$ sudo dfu-util -l -v
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to

Found DFU: [0483:df11] ver=2200, devnum=13, cfg=1, intf=0, path="1-1.3.3", alt=1, name="@Option Bytes /0x1FFFF800/01*016 e", serial="FFFFFFFEFFFF"
Found DFU: [0483:df11] ver=2200, devnum=13, cfg=1, intf=0, path="1-1.3.3", alt=0, name="@Internal Flash /0x08000000/064*0002Kg", serial="FFFFFFFEFFFF"

I have found that I have to "start/run" "nanosaver" AFTER boot is done , hence not directly after
it was downloaded / installed.
Now the green LED on right side of the power switch is steady and "nanaVNA- saver " serial port works fine.
Still need some help with "DFU"

Thanks for confirming which is an official git hub link.

Than I have to apologize to the authors of the code - they do specify "the modules".

I am not sure why "coders" do not advertise "dependencies", however Ubuntu is pretty clear what "modules" are missing.
The only unclear is usage of "pip" , but the command line - in "nanovna" folder eventually works

As far as "pi" goes - I need to red--up on that . On first - it looks as same as " apt update / install ".....

Then I will add - if the code authors provide instruction for Windoze Uninx Mac etc. why not
"here is a script to install on OS x
"install nanoVNA Windoze-Bob ....
"install nanoVNA Unix_Unintu...

I am not sure what is the customary here - continue the post or start a new one.
This post answered my original question.

So I will switch to the other one I started.

I have done something similar at a former employer. We were building a passive intermodulation test set and I incorporated a 1-port Copper Mountain (great company by the way) USB VNA into the design, to check the return loss of the device being tested and to ensure that a load was actually connected before bringing the RF amplifier (two +43dBm tones) online.
Your suggestion would be a step beyond the QRPometer which switches in a simple SWR bridge to measure the match before transmitting.
73, Don N2VGU

On 7/3/21 5:28 AM, Dragan Milivojevic wrote:

This is the official repo:
Any recent Linux distro should have the needed
python modules in it's repositories so there is no
need for pip.

One might hope this is the case, but I just had some issues with versioning of things like pyserial and wound up removing pyserial and reinstalling it. Likewise, I had a bit of trickiness getting the right versions of qt5 and numpy installed on a RPi - I wound up doing

sudo apt-get update

sudo apt-get upgrade?? (this takes a while!)

sudo apt-get remove numpy

sudo apt-get install libatlas3-base

sudo pip3 install numpy

sudo pip3 install scipy

apparently, pip3 picks up a newer version than apt-get.



The other thing that can catch you is which version of python is set up as the default.? nanovna_saver uses #! /bin/env python at the top, and if "python" points to the wrong python install (say you've got both 2.7 and 3.8 installed) then it will start the wrong one.

On 7/2/21 6:12 PM, Kees T wrote:

Has anyone built and packaged a simple manual L/C QRP Antenna Tuner (stand alone) which incorporates the NanoVNA in the hardware ? The NanoVNAs are relatively inexpensive and readily available....maybe you upgraded to a newer model and have an old one sitting around. You can thoroughly analyze the proposed antenna you are about to use, make sure you have a low enough SWR, etc before powering it up with a demonstrably picky QRP Class E amplifier (QCX, QCX+, QCX-Mini, uSDX, etc.).

Interesting idea - I'm building something a bit more complex than that. It's a phased array of two verticals using an LDG AT200PC tuner on each element.

One thing to think about is isolation from the Transmitter to the VNA - you don't want to inadvertently blow up the VNA.? You want some relay(s) with enough isolation.? Say your Tx puts out 100W, and you want to limit the power to the VNA to 0dBM (1mW) - you need 50 dB of isolation across the relay.?? With your QRP rig, maybe you only need 40dB.

And it's not just the relay that's important, there's all the other circuitry and effects (for instance, in my set up, I have to worry about coupling from one antenna to the other).? It's sort of like a multi rig setup in that sense - you want positive automatic isolation so that the Tx doesn't connect to another Rx.