开云体育

On 6/27/22 13:54, Tim Dawson wrote:

I use the ST Micro Cube programmer, and the .bin images from Huygen native on Linux and it works fine. (Search the group - I posted a full "HowTo" procedure a month or so ago).

Tim,

Could you point to this post containing the howto? I don't see anything from you in this group regarding the cube software.

Bob

Yeah I finally got it, I had to add the alt=0 to the command line, and then everything was fine. Now updated to version 1.1, just have to figure out everything that changed and how to use it.

73, Chuck
N0NC

Trust me, *dfu-util* *does* work! (The ST Cube seemed rather overkill for very occasional firmware updates!)

73, YMMV, your approach is just as valid as mine,

Robin, G8DQX

I use the ST Micro Cube programmer, and the .bin images from Huygen native on Linux and it works fine. (Search the group - I posted a full "HowTo" procedure a month or so ago). Considering that ST has dropped the DFU based tool in favor of Cube, seems to be a logical direction in which to make a move . . .

And likely the instructions you found are for the ST DFU tool, and not the open source tool that you are trying to use. (Having said that, I'm pretty sure that "dfu-util" will work, I just never bothered with it, since ST supports Cube on Linux . . .)

- Tim

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Chuck,

it's most certainly possible to update nanoVNA firmware under Linux. There's a *description* at /g/nanovna-users/files/Nano%20VNA%20Saver/nanoVNA-H4%20software%20support%20under%20Ubuntu.pdf.

The listing from *dfu-util* is roughly correct. I've only got an H4 to hand, which offers slightly different results:

~$ dfu-util -l
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=16, cfg=1, intf=0,
path="3-4.1.2", alt=1, name="@Option Bytes? /0x1FFFF800/01*016 e",
serial="205230502031"
Found DFU: [0483:df11] ver=2200, devnum=16, cfg=1, intf=0,
path="3-4.1.2", alt=0, name="@Internal Flash
/0x08000000/128*0002Kg", serial="205230502031"

The two entries refer to two different memory areas. It's likely that there was an issue with the command incantation. The *.dfu* file is to be preferred for the simpler command line necessary (less likelihood of a mistake.)

HTH, 73, Stay Safe,

Robin, G8DQX


On 27/06/2022 21:18, Chuck Miller wrote:

Trying to update the firmware on my NanoVNA-H from linux got the DFU file but keep getting error
dfu-util: More than one DFU capable USB device found! Try `--list' and specify the serial number or disconnect all but one device

dfu-util -l
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=10, cfg=1, intf=0, path="1-10", alt=1, name="@Option Bytes /0x1FFFF800/01*016 e", serial="FFFFFFFEFFFF"
Found DFU: [0483:df11] ver=2200, devnum=10, cfg=1, intf=0, path="1-10", alt=0, name="@Internal Flash /0x08000000/064*0002Kg", serial="FFFFFFFEFFFF"

all the instructions are for Windows and maybe Mac. Can't be done from Linux?
Chuck

On Mon, Jun 27, 2022 at 07:32 AM, F1AMM wrote:

Hello
I use nanovna-saver 0.3.8 because I have Window 7 and a nanoVNA-F I am an
electronics engineer (73 years old); I understand almost all marker charts and
data.

This may be of interest to you. The "official" Saver 0.3.9 and Saver 0.3.10 do NOT run on WIN7 because the version of Python and the QT library are not compatible.

I have compiled a version of Saver 3.10 that runs on WIN 7. You can download it from my Box account


Roger

On Mon, Jun 27, 2022 at 07:32 AM, F1AMM wrote:

I don't understand what the graph identified by
S11 R/ω & X/ω (?Ω / Hz)
Which we select with
[S11 R/ω & X/ω]

It is used when measuring inductors and you wish to know the shape of the complex permeability curves. This is useful when trying to determine the characteristics of an unknown ferrite toroid. It was described by the original NanoVNA Saver author when he released version 2.0. If you read the entire thread you will see questions about it and how it is used.

/g/nanovna-users/topic/54247421#6896

It was implemented at the request of a French ham F4HTQ and he describes it here...

/g/nanovna-users/message/6996

Roger

Hello
I use nanovna-saver 0.3.8 because I have Window 7 and a nanoVNA-F I am an electronics engineer (73 years old); I understand almost all marker charts and data.

I don't understand what the graph identified by
S11 R/ω & X/ω (?Ω / Hz)
Which we select with
[S11 R/ω & X/ω]

Thank you for your help

I think you mix the apple with the pears.
The link cited shows the 2019 status, then there was no V2 plus anywhere.
You can find information about V2 Plus here:

It helps a lot by typing the key words in the Google search and interpreting the descriptions well.
--
Gyula HA3HZ ( )

Hi Members,

I have started working on Nano VNA V2 plus. I want to communicate with Nano VNA using Python. I tried this python code for connection with my VNA but I am not able to get com port information even though I am connected to VNA under COM5 port (as shown in device manager attachment). How do I read active COM port using python script?


Can anyone help me with the connection of Nano VNA using Python Script?

Best Regards

My Saver us the latest 0.4.0 Windows 10 exe. I read there us a 0.5.0 release but only the python files, can't find the windows exe.

For me connecting my Anytone AT-D578 caused a conflict of some kind which makes accessing either it or the NanoVNA impossible. Look for "GD32 Virtual Com Port" in Device Manager. That could be your culprit.


--
73 es God Bless de Ron KK1L <><
KK1L.COM ( )

Metrology level uncertainty study is a humbling science that few engineers understand, including me. I work with VNA data to over 100GHz daily, TDRs over 50GHz, I develop my own cal standards, blah blah blah. I cannot tell you what the measurement uncertainty is in my S11 magnitude at 90GHz for a given reflection coefficient.

In fact, for wafer probing, I personally know guys who developed a lot of this stuff at Cascade Microwave and they struggle.

But from a practical perspective, we have good rules of thumb. We know where our problem areas are (gamma near one, causality of noisy data, reference planes near mode disruptions, SOLT assumes lossless open). So, I usually know how to identify “good enough” data. But as was stated earlier, it sure helps if I only measure time with one clock :)

There are some smart dudes on these message boards though, I’ll keep lurking and learning.

On Fri, Jun 24, 2022 at 03:28 AM, tuckvk3cca wrote:

Firmware version 20200501.
It was running ok until I switched back to a H1 which somehow captured the Com
4 port and the SAA2 no longer recognises it and crashes. This is the error
report before it crashed

(Reminder that copy and pasting into groups.io as text means this traceback would be searchable and easily copied by others.)

There are similar "Issues" reported at

Check to see if any of the similar reports helps you, especially those that refer to SAA2. In a pinch you might need to simply try a more recent version of the application, or see if you can install the tiprev version (assuming you are not already at that latest version). My understanding is that Saver depends on recent firmware on the device(s) as well.

Firmware version 20200501.
It was running ok until I switched back to a H1 which somehow captured the Com 4 port and the SAA2 no longer recognises it and crashes. This is the error report before it crashed



I have tried restarting my Computer and replugging the SAA2 USB wherein win 10 went through a driver installation again. It didn't help. The H1 still runs ok btw.

You should share the details, like the error message and probably firmware version. Share what steps you've take so far to solve this.

My Saver program running perfectly under Win10 for the last few days has now decided to fail to connect to my SAA2. It returns some error failure on the DOS screen and then crashes. Anyone has any ideas on how to fix this?

Many thanks for that advice. I couldn't agree more. That's why I wanted to
make the purchase through R & L and not someone offshore. R & L have proven
themselves to be rock solid reputable people over the years.

Even if they are selling outdated clones and not the latest and greatest
model, they have a lot of very happy customers. Technology like the VNAs
evolves very rapidly. I usually have better experience buying technology a
generation or two behind. The newest stuff often has bugs just like the
older stuff did.

use r&l , they have a phone, they have a real mailing address, they have a real store, and there are people you can talk to if needbe, good people, the other place, is just a passthru shop, good luck if you need to return or warrenty support,.

Hi Gyula - trying your website, I got an emoji with a zipper across the mouth and a message in Hungarian. Fortunately my google-translate has the camera option and told me that your website is down for maintenance. However I have visited before and you do have plenty of excellent info! Cpuld you post here when your site is back up? tnx!
--
72/73 de k1qed, ?bob.c ? ? ? ? qrp 4evr!