¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Messages
Expanded Topics Messages
Date
Re: SD Problem #nanovna-h4

 

You might want to try a 16Gb card, lots of reported issues with the
higher capacity cards over the past couple years, Moving to a lower
capacity and all works OK.

-----------------------------------------From: fatraut@...
To: [email protected]
Cc:
Sent: Saturday January 21 2023 5:15:14PM
Subject: [nanovna-users] SD Problem #nanovna-h4

I just received my second NanoVNA H4. I then up dated the software to
"20220831.bin" using the STM32 CubeProgramer.
I purchased this unit because it had an SD Slot in it and I thought
it would work like the TinySA. However I have tried three different
32GB microSD cards and I can't save anything to any of them. I get a
save failure every time. I am very disappointed on how this save
feature is working. The rest of the unit seems to work great so I
don't know what to do from here.





Links:
------
[1] /g/nanovna-users/files
[2]
/g/nanovna-users/leave/11119600/4866111/1865567994/xyzzy
SD Problem #nanovna-h4

[email protected]
 

I just received my second NanoVNA H4. I then up dated the software to "20220831.bin" using the STM32 CubeProgramer.
I purchased this unit because it had an SD Slot in it and I thought it would work like the TinySA. However I have tried three different 32GB microSD cards and I can't save anything to any of them. I get a save failure every time. I am very disappointed on how this save feature is working. The rest of the unit seems to work great so I don't know what to do from here.
recall saved images NanoVNA-h4

 

using ver.1.2.14 that came on the NanoVNA-h4
i looked in 'files' section for documentation on how to recall S1P image on the SD card.

i want to be able to recall a saved swr image to compare it to a active one after i have changed the antenna length.
73, dan
Re: Where to buy a NanoVNA H4 HW rev 4.3?

 

Erik, dl1ecd,

Nach der Bezahlung in 4 Tagen geliefert.
Vladimir, dl7pga
Re: Where to buy a NanoVNA H4 HW rev 4.3?

 

Hello Erik, dl1ecd!
You can buy last HW Version 4.3 of NanoVNA-H4 here:

I have NanoVNA-H4 HW 4.2 from Zeenko Store since 1 year - Micro sd slot, but no clock crystal 32768 Hz (soldering on PC14, PC15).
73 de Vladimir, dl7pga
Re: #nanovna-h4 #firmware #flashing #nanovna-h4 #firmware #flashing

 

Great, I had a similar experience while attempting my first H4 upgrade. As you say you must first?CHOOSE the new firmware file to load the file into the DFU Demo program. Then select UPGRADE?to actually write the new firmware file into the Nano VNA.?As an aside, VNA Saver seems to be the most popular PC based program to provide an interface to the device.?There exists another slick program called NanoVNA App; (OneofEleven). That particular program has a built in?ability to load device firmware directly instead of using DFU Demo. I just thought I would mention an alternative?means of upgrading firmware. Both methods accomplish the task. Actually, the VNA App itself is preferred by some users?as an alternative to VNA Saver. I like both programs, and very much appreciate the folks who spent the time to?create them.

On Saturday, January 21, 2023 at 08:34:40 AM EST, groups.kc3suw.eycn2 via groups.io <groups.kc3suw.eycn2@...> wrote:

This was the fix. Select the software then click upgrade in DfuSe Demo, never click the upload button.

Thank you very much.
nanovna-H black screen

 

Today my nanovna-H bought in 2019 seems to have died.
I connect it to a 5V source and after a few minutes I see the screen flicker a few times (white then black).
I also notice that the traces change shape randomly and finally black screen.
I test connection to computer and I get COM3 in nanovna-app but unable to connect.
DFU mode is recognized by nanovna-app and I can send any FW, but it doesn't wake up nanovna-H.
For a minute I thought that somehow the display could be responsible for blocking the nanovna. I remove the display and still no news.
I think STLink to correct the bootloader? But it doesn't seem to make sense if I have DFU mode?
Perhaps the next step is to change the microcontroller?
Igor
Re: Android NanoVNA app

Ck Hanson
 

I am certainly no expert here, but my experience points to a
security setting?

On Fri, Jan 20, 2023 at 10:47 PM Chris VK5SA <
chris_at_levingston.net_na0l@...> wrote:

My Android phone has always worked with the NanoVNA app and I now get a
¡°No Device Found¡± error.

Any ideas, please?

C connector to C connector cable which works fine using NanoSaver on my
laptop, so that's not it.


--
*N A 0 L*
*_ . . _ _ _ _ _ _ . _ . .*
Re: #nanovna-h4 #firmware #flashing #nanovna-h4 #firmware #flashing

 

This was the fix. Select the software then click upgrade in DfuSe Demo, never click the upload button.

Thank you very much.
Android NanoVNA app

 

My Android phone has always worked with the NanoVNA app and I now get a ¡°No Device Found¡± error.

Any ideas, please?

C connector to C connector cable which works fine using NanoSaver on my laptop, so that's not it.
Re: Stray Coupling Suppression

 

I've dropped the optional .s2p output. Just use the .s1p the program creates.

Here are some curious plots for a file K0JHL sent me. Some sort of narrowband thing. The only processing difference (both are for Y21 stray suppression) is that in one I convert S11+S21 first to S11, clip its magnitude to 0.9998 max, and then convert to Z. The other plot is unclipped. That's the one with negative R! And keeping |S11| < 1 wasn't good enough. The input file has |S11| < 1 and |S21| < 1. It's the internal intermediate value that is the problem. Another file he sent me that has |S11| > 1 for all points but one has no obvious problems. Curious. This is clearly a work in progress.

I've uploaded yet another version that clips the output file.

Brian

1.gif
2.gif

Re: #nanovna-h4 #firmware #flashing #nanovna-h4 #firmware #flashing

 

This may also happen for a different reason: the DFusedemo program uses
"Upload" and "Download" backwards from what many of us think.
Upload fetches the data from the nanovna and stores it in a local file. So
if you did that, using the name of your new file, what you did is overwrite
the new firmware file on your computer with the current firmware from the
nano.
So you may just need to a) first get the new firmware file again, and b)
"Download" it to the nanovna using dfusedemo.
Use the MS version only if your nanovna has _MS in the hardware version
number on the placard on the back of the unit (or you otherwise know it has
an MS version chip in it).
Stan

On Fri, Jan 20, 2023 at 12:17 PM groups.kc3suw.eycn2 via groups.io
<groups.kc3suw.eycn2@...> wrote:

I have a new NanoVNA-H4 that I purchased from RandL directly. When I look
on the device it shows version 1.0.70. I am trying to upgrade the firmware.

I am able to put the device into DFU mode using the buttons.
DFU mode is confirmed by the device appearing in DfuSe Demo.
I Upload and upgrade the firmware using DfuSe Demo.
I reboot the NanoVNA, it shows the same firmware version as before the
upgrade.
I tried NanoVNA-H4-MS_20220831.dfu and NanoVNA.H4.v1.2.00.dfu.
I tried with and without "optimize upgrade duration" checked.

I always get the same results, no changes to the firmware version shown by
the device after rebooting out of DFU mode.

Can anyone point me to the step I am missing or misunderstanding?
Re: #nanovna-h4 #firmware #flashing #nanovna-h4 #firmware #flashing

 

Greetings, It is basically a two step process as I recall. (Step1) You first read the new firmware file into the dfu demo program. (Step 2) Is writing the actual file into the device. I hope this might be helpful.

On Jan 20, 2023, at 15:17, groups.kc3suw.eycn2 via groups.io <groups.kc3suw.eycn2@...> wrote:

?I have a new NanoVNA-H4 that I purchased from RandL directly. When I look on the device it shows version 1.0.70. I am trying to upgrade the firmware.

I am able to put the device into DFU mode using the buttons.
DFU mode is confirmed by the device appearing in DfuSe Demo.
I Upload and upgrade the firmware using DfuSe Demo.
I reboot the NanoVNA, it shows the same firmware version as before the upgrade.
I tried NanoVNA-H4-MS_20220831.dfu and NanoVNA.H4.v1.2.00.dfu.
I tried with and without "optimize upgrade duration" checked.

I always get the same results, no changes to the firmware version shown by the device after rebooting out of DFU mode.

Can anyone point me to the step I am missing or misunderstanding?
#nanovna-h4 #firmware #flashing #nanovna-h4 #firmware #flashing

 

I have a new NanoVNA-H4 that I purchased from RandL directly. When I look on the device it shows version 1.0.70. I am trying to upgrade the firmware.

I am able to put the device into DFU mode using the buttons.
DFU mode is confirmed by the device appearing in DfuSe Demo.
I Upload and upgrade the firmware using DfuSe Demo.
I reboot the NanoVNA, it shows the same firmware version as before the upgrade.
I tried NanoVNA-H4-MS_20220831.dfu and NanoVNA.H4.v1.2.00.dfu.
I tried with and without "optimize upgrade duration" checked.

I always get the same results, no changes to the firmware version shown by the device after rebooting out of DFU mode.

Can anyone point me to the step I am missing or misunderstanding?
Re: nanovna-saver crashes with H4

 

I upgraded the nanoVNA-H 4 to v 1.2.14 and now nano Saver runs OK.
Re: nanovna-saver crashes with H4

 

My NanoVNA-H 4 is running V 1.0.39
Re: nanovna-saver crashes with H4

 

I have the same problem when I connect the to the VNA, Nano Saver app closes.

Nan Saver is V 0.5.4

NanoVNA -H 4
Re: Stray Coupling Suppression

 

More insignificant differences. The animated GIF shows impedance for the Y21 method (no notation) and S21 method (CM suppression disabled) for a 12-turn choke on a F240-31 core. The Y axis is ohms. John, K0JHL, measured the choke with the test fixture shown in the image. It's a commercial product:



I've updated the program to create either an .s1p or .s2p file. One may fit your work flow better than the other. Each has the stray coupling or stray impedance removed.

/g/nanovna-users/files/stray.zip

Brian

plot.gif
fixture.png

Re: Stray Coupling Suppression

 

Yes, the differences are amazing. When I first started on my "journey" of
building and measuring common mode chokes, I began with the S11 method. It
was easy and I didn't have to make a full cal. of both ports on the 8753C.
Then I rapidly discovered too much variation due to the setup. The fixture
I finally used and still do is almost identical to those shown in the
write-up.

Another "discovery" was that one choke does not serve all HF frequencies.
Consequently, I have a "collection" of seven or so chokes, all labeled for
best CMR at various frequencies. When do the commercial suppliers of
"antenna tuners" wise up (or the hams become aware of things they should
know from passing their license exams)? When it comes to rejecting common
mode currents, there is no "one-size-fits-all".

Dave - W?LEV

On Thu, Jan 19, 2023 at 10:56 PM Brian Beezley <k6sti@...> wrote:

Yes, the difference between the S21 and Y21 methods is small for the 2.35
pF stray capacitance exhibited K6JCA's test fixture. But not all stray
impedances are so benign.

Attached is an animated GIF showing the effect of common-mode coupling on
a particular ground probe measurement. N6LF took this data with a VNA2180
that ran from AC power. This provided a long path for common-mode coupling
to arise. This particular result used a two-measurement technique where the
common-mode impedance was essentially measured and then subtracted from the
data. It shows how large stray coupling can be in some cases.

To me the most eye-opening thing in the K6JCA article is the huge
difference between shunt and series measurements above just a few MHz.

Brian





--
*Dave - W?LEV*
--
Dave - W?LEV
Re: Stray Coupling Suppression

 

Yes, the difference between the S21 and Y21 methods is small for the 2.35 pF stray capacitance exhibited K6JCA's test fixture. But not all stray impedances are so benign.

Attached is an animated GIF showing the effect of common-mode coupling on a particular ground probe measurement. N6LF took this data with a VNA2180 that ran from AC power. This provided a long path for common-mode coupling to arise. This particular result used a two-measurement technique where the common-mode impedance was essentially measured and then subtracted from the data. It shows how large stray coupling can be in some cases.

To me the most eye-opening thing in the K6JCA article is the huge difference between shunt and series measurements above just a few MHz.

Brian

probe.gif

9181 - 9200 of 39634