¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Messages
Expanded Topics Messages
Date
Re: upgrade firmware

 

I don't have one, but I think you can check your currently installed version of firmware and it will be obvious. Look in the menu system to display the current firmware version.
Gary
W9TD
Re: upgrade firmware

 

Gary thanks for the reply. How can it be found out? Do I have to disassemble the box and read it from the IO?
Zdenek
Re: check "Dollar Tree" store. Now Dollar and a Quarter!

 

If you can recommend a brand that you think will provide better bang for the buck, I'd consider buying some.
Try Monoprice or the Amazon Basics brands. Monoprice also sells on Amazon, at a higher price than their own website, but I think on Amazon it has Prime shipping.


Donald KX8K
Re: Strange "Scatter" Sweep Traces VNA ver 1.1

Brandon Parker
 

No clue what this refers to but you seem pretty stoked and that gets me
pumped too way to go man!

On Wed, Mar 1, 2023, 9:26 AM Chuck Carpenter <w5usj@...> wrote:

I now have a 'new' Ver 1.1, 21Dec2021**

The features and functions I needed are now at Hand.

Excelsior!

**LIkely others by now.
--
Chuck, W5USJ
Re: upgrade firmware

 

The two are for the Silicon Labs Si5351 or the MS5351 clone. You need to know which is used in your NanoVNA
Gary
W9TD
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

Europeans use the period '.' and comma ',' exactly opposite to how Americans do.

For Americans, 1.234 is slightly more than one. For Europeans, slightly more than one thousand.

On Wednesday, March 1, 2023, 07:18:30 AM EST, Brian Beezley <k6sti@...> wrote:

On Wed, Mar? 1, 2023 at 02:25 AM, <btomek@...> wrote:


Full s1p in attachment.
I'm curious why your Touchstone files use commas rather than periods in decimal numbers. The utilities and programs I write used to check for commas and replace them with periods, but to simplify the code I dropped that check after not encountering any files with commas for a long time. None of that software will work with your files. This includes a utility that checks for |Sij| > 1, which is invalid but occurs in several of your files.

Brian
upgrade firmware

 

Please what is the difference between NanoVNA-H-MS_20220831.dfu and NanoVNA-H-SI_20220831.dfu ?
I have NanoVNA-H Version: 0.4.4-1-g42cc6a8 and I don't know which firmware to choose from the two mentioned. Thank you very much for your advice.
Zdenek
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

On Wed, Mar 1, 2023 at 05:54 AM, <btomek@...> wrote:


I think both separators should be supported when reading the file.
The compiler may not support comma separators. For example, my compiler yields 1 when evaluating this string: 1,234. You can get around this by evaluating the number character by character, which is complicated if you allow scientific notation in all its variations, or you can replace commas with periods. The latter is easy, but it fails when the code processes a CSV file, which some VNAs generate and which most of my programs are designed to handle. It was easy to accommodate commas in the program that checks S-parameter magnitudes since it does not have to deal with CSV files. Incidentally, the updated program is here:



Note that your "GOOD" files also have invalid |S11| values.

Brian
Strange "Scatter" Sweep Traces VNA ver 1.1

 

I now have a 'new' Ver 1.1, 21Dec2021**

The features and functions I needed are now at Hand.

Excelsior!

**LIkely others by now.
--
Chuck, W5USJ
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

I changed the code to accommodate your files. One offending point for
OPEN_CHANGED.s1p occurs at 300 MHz. That may provide a clue::
@Brian - My s1p was generated in NanoVNA-App. Whether there is a period or a comma probably depends on operating system's regional settings.
According to wikipedia more countries use a comma instead of a period.
In NanoVNA-App, the lower left corner says what the decimal separator character is. In NanoVNA device, you can choose what the separator should be: Menu/Config/Expert settings/More/Separator
I think both separators should be supported when reading the file. When writing, it should be as the standard specifies. If it specifies.
Going back to the test, I wanted to check whether the calibration data from the frequency 888750625 is responsible for the measurement result on 888750625 or maybe for something else, such as a bug on a neighboring result. However, it came out that every single calibration point affects 4 results, which was a surprise to me. The value of the result is not important, because the calibration data at the changed points is random, but such that it deviates significantly from what it was. Hence, the result will also be random, and may be > 1.
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

I changed the code to accommodate your files. One offending point for OPEN_CHANGED.s1p occurs at 300 MHz. That may provide a clue::

297033500 1,001980424e+00 1,973727951e-03
299283375 8,971092105e-01 1,766025904e-03
301533250 -1,148890305e+01 8,992123604e+00
303783125 -6,962405443e-01 5,263801292e-02
306033000 8,130612373e-01 -7,944851182e-03

Brian

ck.gif

Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

On Wed, Mar 1, 2023 at 02:25 AM, <btomek@...> wrote:


Full s1p in attachment.
I'm curious why your Touchstone files use commas rather than periods in decimal numbers. The utilities and programs I write used to check for commas and replace them with periods, but to simplify the code I dropped that check after not encountering any files with commas for a long time. None of that software will work with your files. This includes a utility that checks for |Sij| > 1, which is invalid but occurs in several of your files.

Brian
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

Roger, thank you for reproducing the experiment. We have clarity that it is a Bug after all.

I did an experiment in which I change the calibration data for a 4 specific frequencies by editing a copy of the .cal file in Notepad and I compared the s1p results for the correct cal file and the changed one. It seems to me that change one specific frequency should affect the results for that specific frequency, while affecting as many as 4 results. On top of that, the most affected result is not the one for which the calibration is changed, but an erlier one, especialy on higher frequencies.There was no cable here, only calibration directly on the NanoVNA SMA, and measurements directly on this SMA.
changed cal freq: 74295875, 303783125, 801005500, 888750625

Examples for short:
| Freqency|GoodRe|GoodIm|ChanRe|ChanIm|

| 74295875:
| 69796125|-1,0005|-0,0006|-0,9948|-0,0025|
| 72046000|-1,0005|-0,0007|-1,1217| 0,0452|
| 74295875|-1,0005|-0,0007| 0,4790| 0,3642|
| 76545750|-1,0007|-0,0008|-0,9309|-0,0208|

303783125:
|299283375|-0,9999|-0,0052|-0,9071| 0,0064|
|301533250|-1,0016|-0,0021|-3,1341|-5,7410|
|303783125|-1,0016|-0,0021| 0,8167|-0,2290|
|306033000|-1,0031|-0,0023|-0,8319| 0,0202|

801005500:
|796505750|-1,0076|-0,0061|-0,8507|-0,0095|
|798755625|-1,0068|-0,0033| 0,2271| 0,1437|
|801005500|-1,0081|-0,0062|-1,4934| 0,0379|
|803255375|-1,0075|-0,0055|-0,9863|-0,0060|

888750625:
|884250875|-1,0099|-0,0032|-0,9716| 0,0039|
|886500750|-1,0100|-0,0040| 0,2426| 0,1202|
|888750625|-1,0105|-0,0051|-1,0426|-0,0117|
|891000500|-1,0063|-0,0056|-1,0061|-0,0055|

Full s1p in attachment.

There is probably some function that tries to smooth the calibration data, average it or filter it. Perhaps this function is used for interpolation if the calibration frequencies do not match the measurement frequencies.
Just trying to guess, maybe I am writing nonsense. I don't really know how this calibration correction works, and I would love to know.
It would be great if someone would fix it.

TEST.ZIP
TEST.ZIP

Re: Driver for nanVNA

 

Hi David
If you right click on the STM Device in dfu mode and select properties.
Go to update driver.
Browse to the install directory for the STM software ( prob in programs x86) and press enter.
That should fix it.
Other thing to check is that the com port assigned to the STM USB driver is correct and not clashing with another in device manager.

Worked for me with W10 on 64 bit machine.

On 1 Mar 2023, at 12:35 am, David Reams <dwr.kj4de@...> wrote:

?I am still unable to get the nanoVNA to assign a port. I have Windows 10
and the nanoVNA will not automatically assign a port and the program
suggested above does not assign a port. When I place the nanoVNA in DFU
mode it does show "STM Device in DFU Mode". under Universal Serial bus
Controllers. Otherwise it shows "Unknown device" if not in DFU mode. No
port assignment is indicated at all. I might be having a problem with
the nanoVNA equipment itself. When not connected to a PC, the device works
fine.

Maybe this problem can be solved, but if there is, in fact, a problem with
the device, no solution would be forthcoming.

Again, thanks for all of your help!!

David
.

On Tue, Feb 28, 2023 at 1:31?PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Mon, Feb 27, 2023 at 06:33 PM, David Reams wrote:


Can you give me some more information on the STM boot loader and a
source to
download?

David,

There are two different drivers required when using a NanoVNA-H or
NanoVNA-H4. One is required to get a COMxx: port so that your PC can
exchange data with a NanoVNA. The other driver is required when you want
to do firmware updates on your device.

COM port driver
---------------------

With Windows 10 and Windows 11 the required driver will be installed by
Windows when you connect your NanoVNA to a USB port. With Windows 7 and
Windows 8 you have to manually install the driver and then plug in your
NanoVNA. If Windows 10 fails to install the driver (rarely happens) you
can use the Windows 8 driver. You can check that the driver is working by
plugging in and turning on your NanoVNA and then going into Device Manager
and looking under ports to get the COM port number that has been assigned
If you power off the NanoVNA the COM port should disappear from Device
Manager. I have put a copy of the drivers on my BOX account for you to
download. Here is a link where you can download it >>

Unzip and select the 32 or 64 bit version for your computer.

Firmware Upgrade driver
---------------------------------
This driver is only required when you want to upgrade your firmware. It
does not assign a COM port when the NanoVNA is plugged in and in DFU mode.
DFU mode is activated in different ways depending on your device and the
firmware installed. Old devices had to be put in DFU mode by opening the
case and shorting the Boot0 and DFU pins. In other cases DFU was accessed
by a Menu selection. DFU mode on the -H4 is activated by depressing the
rocker switch down and powering on the anoVNA. When in DFU mode the screen
will be black. You can check that the driver is installed correctly by
looking under USB controllers and seeing if it shows that your device is in
DFU mode (see attached screenshot). I have posted a link to the DfuSe
package on my Box account for you. It will install the DFU driver and the
DfuSe firmware upgrade application.

The Absolute Beginners Guide in the file section of this group tells you
how to install the DFU drivers that are needed for firmware update and how
to install the latest firmware.


/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf

You don't have to register to get the DFU program and drivers. I have put
a copy on my Box account for you...


Roger










-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#31590): /g/nanovna-users/message/31590
Mute This Topic: /mt/96994660/1030204
-=-=-
Learn about the NanoVNA in the following forum areas:
Documentation & Update Files: /g/nanovna-users/files
Knowledge-based Wiki: /g/nanovna-users/wiki
-=-=-
Group Owner: [email protected]
Unsubscribe: /g/nanovna-users/leave/12063674/1030204/1581205739/xyzzy [robertmiles.home@...]
-=-=-=-=-=-=-=-=-=-=
Re: S-Band NanoVNA

 

On Tue, Feb 28, 2023 at 05:25 PM, Ed Wilson wrote:


I received my LiteVNA today and calibrated it right away over several
frequency ranges, one up to 6 GHz. I checked the response of a 1.3 GHz and a
2.3 GHz microstrip LPF and a 2.3 GHz microstrip BPF that I recently designed
and fabricated and the curves look pretty good. I am using it with the
NanoVNA-App software on a Windows 10 machine.
The firmware installed on the device is dated August 30, 2022 so I am
wondering if a more recent version is available and where I might check for
newer versions as they become available (with download links)?
You have the latest official version from Hugen.


DiSlord has made many updates to the firmware since then. Try joining this group for more info...
/g/liteVNA/

Roger
Re: S-Band NanoVNA

 

I received my LiteVNA today and calibrated it right away over several frequency ranges, one up to 6 GHz. I checked the response of a 1.3 GHz and a 2.3 GHz microstrip LPF and a 2.3 GHz microstrip BPF that I recently designed and fabricated and the curves look pretty good. I am using it with the NanoVNA-App software on a Windows 10 machine.

I plan to try to design, fabricate, and test some higher frequency filters, amplifiers and mixers in the very near future so this new ¡°toy¡± will be put to good use. I realize that the specs are somewhat degraded above 3 GHz but they will be ok for my purposes.

The firmware installed on the device is dated August 30, 2022 so I am wondering if a more recent version is available and where I might check for newer versions as they become available (with download links)?

Thanks,

Ed, K0KC
Re: Driver for nanVNA

 

I am still unable to get the nanoVNA to assign a port. I have Windows 10
and the nanoVNA will not automatically assign a port and the program
suggested above does not assign a port. When I place the nanoVNA in DFU
mode it does show "STM Device in DFU Mode". under Universal Serial bus
Controllers. Otherwise it shows "Unknown device" if not in DFU mode. No
port assignment is indicated at all. I might be having a problem with
the nanoVNA equipment itself. When not connected to a PC, the device works
fine.

Maybe this problem can be solved, but if there is, in fact, a problem with
the device, no solution would be forthcoming.

Again, thanks for all of your help!!

David
.

On Tue, Feb 28, 2023 at 1:31?PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Mon, Feb 27, 2023 at 06:33 PM, David Reams wrote:


Can you give me some more information on the STM boot loader and a
source to
download?

David,

There are two different drivers required when using a NanoVNA-H or
NanoVNA-H4. One is required to get a COMxx: port so that your PC can
exchange data with a NanoVNA. The other driver is required when you want
to do firmware updates on your device.

COM port driver
---------------------

With Windows 10 and Windows 11 the required driver will be installed by
Windows when you connect your NanoVNA to a USB port. With Windows 7 and
Windows 8 you have to manually install the driver and then plug in your
NanoVNA. If Windows 10 fails to install the driver (rarely happens) you
can use the Windows 8 driver. You can check that the driver is working by
plugging in and turning on your NanoVNA and then going into Device Manager
and looking under ports to get the COM port number that has been assigned
If you power off the NanoVNA the COM port should disappear from Device
Manager. I have put a copy of the drivers on my BOX account for you to
download. Here is a link where you can download it >>

Unzip and select the 32 or 64 bit version for your computer.

Firmware Upgrade driver
---------------------------------
This driver is only required when you want to upgrade your firmware. It
does not assign a COM port when the NanoVNA is plugged in and in DFU mode.
DFU mode is activated in different ways depending on your device and the
firmware installed. Old devices had to be put in DFU mode by opening the
case and shorting the Boot0 and DFU pins. In other cases DFU was accessed
by a Menu selection. DFU mode on the -H4 is activated by depressing the
rocker switch down and powering on the anoVNA. When in DFU mode the screen
will be black. You can check that the driver is installed correctly by
looking under USB controllers and seeing if it shows that your device is in
DFU mode (see attached screenshot). I have posted a link to the DfuSe
package on my Box account for you. It will install the DFU driver and the
DfuSe firmware upgrade application.

The Absolute Beginners Guide in the file section of this group tells you
how to install the DFU drivers that are needed for firmware update and how
to install the latest firmware.


/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf

You don't have to register to get the DFU program and drivers. I have put
a copy on my Box account for you...


Roger
white screen

 

Hi to all, I am new to this group. Thanks.

I was using mi nanovna-h , hardware ver. 3.5 , with dislord 1.2 firmware.
All went fine till i had the bad idea of changing the firmware to Hugen
version 1.2.14 (file name: NanoVNA-H-SI_20220831.dfu from the web:
and the process via dfu
(Dfusedemo) got stuck on 6% for 1 hour.
Then I got a persistent white screen on nanovna.
A couple of days ago I upgraded the nanovna without any problem from the
original firmware to dislord 1.2, using the same computer and software.
:(
Is there a way to bring it to life?

Many thanks
LU1FP Ezequiel
Re: check "Dollar Tree" store. Now Dollar and a Quarter!

Terry Perdue
 

Same experience with their headphones. Great price if they¡¯d last more than a week.

On Feb 28, 2023, at 11:27 AM, Jim Allyn - N7JA <jim@...> wrote:

?On Mon, Feb 27, 2023 at 11:19 AM, Clyde Lambert wrote:

I purchased a couple of USB lead wires from Dollar Tree. They lasted about
three or four weeks, then the insulation started separateing from the back of
the connector housing.
I've noticed that with some of the cables I have purchased from Dollar Tree also, but mine are two or three years old, maybe more. Some are plugged into and unplugged from the phone or other devices daily, sometimes more than once a day. Maybe I'll buy some expensive cables some day, maybe not. If you can recommend a brand that you think will provide better bang for the buck, I'd consider buying some.
Re: NanoVNA-App in app calibration problem (bug?) #calibration #nanovna-app

 

Correction to last post. One of the Short plots was mislabelled. Corrected versions attached.

Roger

Short App.PNG
Short VNA.PNG

8641 - 8660 of 39648