开云体育

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.

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.

I recently needed the TDR feature for a project and so decided to upgrade the original firmware in my nanoVNA to something more current. I removed it from the 3D printed case I had made and verified the part number of the cpu as stm32f072c8 which is the 64kB flash version the newer hex files all seem larger than that. I carefully used stlink to save the current firmware and then loaded the newer version. I was pleasently suprised when it loaded and works. It seems many of stm32 cpus are actually the larger flash version and labeled as the smaller version and not certified for the full memory capacity. I had found this to be true with a number of bluepill boards labeled as 32kB devices but in fact having 128kB this is fine for hobby users but should not be information used for any commercial application.

The antenna tuner in chapter 9 of “Microcomputer Projects for Amateur Radio” does just this with a DDS and a resistive bridge.
Gary
W9TD

Since I did not want to delete the entire message and I do not see "edit"

Here is a ADDENDUM.

The only difference between "then" and now is "python3.9" - NOT 3.7

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

~/nanovna-saver$ python3.9 nanovna-saver.py

Also
apparently there is more than one "git hub" depository to clone....



or is is all linked back to "original ? (did not bother to check )

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.

I have a sneaky feeling that the original "saver" on git hub is no longer active and "python" is no different from other languages - it "moves"
and it is unclear how many older versions of python I have to have to make "saver" work.

Perhaps there are other versions of "saver" or similar software to interact with "nanoVNA" . ?

A while back I had a go at dumping out a full 2 port model of a VHF BPF using the nanovna and also a lab VNA to see how the results compared. Although this only tested up at VHF I thought the results compared quite well for insertion loss and complex impedance. I don't really plan to use my early nanovnaH above 300MHz and will probably only use it up to 50MHz most of the time but I do think the performance is excellent up to 50MHz. As with any VNA a lot depends on the cal kit and the test fixture and I used a decent homemade SMA mechanical kit with the nanoVNA and an ecal cal module with the lab VNA.

See the image below to see how the two VNAs compared for this simple BPF test. The initial aim here was really to see if my nanovna software was working correctly for s11 s21 s12 s22 data dumping (with a fixture swaparound). I was also quite pleased with how well the results agreed between the two VNAs.

OK, I can read several "how to..." , watch "u-tube " - rather not waste my time there...
OR
I can plug it in ( it works better that way) and push series of self -explanatory buttons UNTIL
I get
(you are in ) DFU mode
and "to get out " of DFU mode "must be manually reset" .

1. I get no visible feedback what is happening , BUT
lsusb reports

Bus 001 Device 013: ID 0483:df11 STMicroelectronics STM Device in DFU Mode

2. Should the funky sort of "single shot wave " under green LED ( right to the power switch) do something ?
3. If successfully updated - how do I " manually reset" ?
4. Lacking much indication about what is happening - what could be
reasonable time for DFU to finish ? ( hours / days / years ?)

I was thinking a MANUAL QRP Tuner for the education.

1) You can readily see the effects of varying the capacitance and inductance on the Smith Chart, so it's an education.
2) Since you are using the NanoVNA to establish a low SWR you are not subjecting your picky "Class E" PA finals to high SWR stress.
3) Great Show and Tell item for the next club meeting especially if packaged neatly in one small box.
4) There are probably other reasons.

73 Kees K5BCQ

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.).

73 Kees K5BCQ