开云体育

Far as I can tell on the H-4 STMicroelectronics download is a must, you have to register to get it. Then download the rar file you wish from the Disloards choices under files on this site (group.IO) 1.0.39 or 1.0.45 rar file. get the rar from your downloads folder and send it to the folder of your choice as the rar file it is. ( 7 Zip for windows is freeware) I downloaded 7 Zip and instaled it. To put the H4 into DFU mode you hold down on the rocker toggle and turn the nano on. Open the DfuSe Demo and click Choose, choose the dfu file you've extracted from the rar file using 7 Zip. Then the upgrade, after upgrading, click leave DFU mode.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------(-before you download/upgrade you will need to run down where you sent the rar file and right click on it... choose extract which will convert the rar file to a dfu file right in the same folder using 7 zip -) my system is win 10, worked for me.( some down both 1.0.39 and 1.0.45 some use one to erase the other incase of problems) you can only install a dfu file in a device that is in dfu mode, rar file won't go. Connect to USB cable right after you open DfuSe Demo This is a little vague but may offer some direction.

Hi Richard,

I’m glad I wasn’t the first to point out that this mistake isn’t called a “brick”. Stop causing panic, because in his position, when not in use, this will not happen unless he has dropped and broken his display or walked on with his car. Then you can say it's a brick.

It appears from your description that you downloaded a 4 "version firmware for the 2.8" version. This is not good! This is a bad choice.
It’s good to have a ST-Link v2 hardware, but put that aside for now.
My first question is, what exactly did you do? He found it wasn't working.
What to do: First, make sure that the device battery is not exhausted.
If discharged first recharge and then turn on when it works: glad.
If it doesn't work and your battery is charged, I have an additional question:
Have you ever tried to use your device while connected to your computer?
You can connect to the computer via a COM port using a driver, in which case the device is visible in the device manager.
Possible in DFU (i.e. Device Firmware Upgrade) mode where it is NOT VISIBLE between COM ports.
In this mode, it is possible to upload (or download) the operating firmware to the device's microprocessor.
You can do this by uploading a .dfu file using DfuSe.
Before I write about a lot of things here, please read the article Using NanoVNA on my website.
There is a lot of help here. If reading these doesn’t help, ask where you got stuck.

Please don’t give up on someone whose solution is unknown, in despair. But this is not the case. There is help.
The 2.8 "-H device would require the installation of the DiSlord 1.0.45 firmware, which is the current latest.
If you have switched the device to DFU mode and do not log in in the solo mode after the firmware has been loaded, it will still remain in DFU mode.
That is, dfu must be loaded until it logs in after on / off.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Hi Manfred,

I’m glad you got to the end of things, so you got to know many thing.
The point is that in DFU mode, the device firmware is loaded, which means that the device is NOT accessible from the PC on one of the COM ports.
If you want to use the machine to communicate with a PC, look for a COM port in Device Manager.
You will then need a driver for your computer to see the device.
To understand this well, you need to get to what you have just achieved. So thinking is help.
Telemedicine is only possible if the perpetrator of the problem is working with someone who knows the solution well.
You could say who can ask well, he already knows the answer. Most new device owners are not like that.
Oh and we shouldn’t give up because there’s a solution, we don’t see it at first.
Because of this, the questioner may be irritated or nervous.
The forum works and works well when we post the solution. As you did in the message above.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Well, I got it to work now. I successfully updated my NanoVNA 1.0.45.

The problem was that I hadn't realized that after installing the DfuSe Demo software, I still needed to manually install the driver from the Windows 7 directory in the DfuSe Demo directory in Program Files. That Windows 7 driver works fine with Windows XP too.

NanoVNA App does not see the NanoVNA in DFU mode while this driver isn't installed. NanoVNA App works fine just by copying its files into a directory, but only for USING the NanoVNA, not for updating it. To update it, it does need the mentioned driver. At least in my Windows XP system. And with the old firmware I had in my NanoVNA, NanoVNA App didn't work correctly.

I think that the firmware upgrade procedure isn't sufficiently clear in the documentation. I had to work through three different documentation files, and apply some logical thinking which at my age works maybe for two hours in the morning, two days per week, to find out how to do it.

Anyway, now it works. I can use NanoVNA App just fine. I enjoy the larger number of points and the extra graph formats. I hate the slow speed that comes attached with using many points. And I wonder while the reading below 50kHz is so very unstable. It seems to be a lot better with the old software. But overall the new software is better. I probably will like it even more when I get used to it.

Gyula, I also tested NanoVNA Partner, several weeks ago, but I got the impression that it doesn't really do much more than the older program. It only shows more things at the same time, and I preferred the simpler display of NanoVNA MOD.

So, to clear things up:

There is one driver that works with NanoVNA in normal (measurement) mode, which comes in a file named stsw-stm32102.zip. This driver does NOT work in DFU mode, so it cannot be used to upgrade the NanoVNA's firmware. I had this already installed, and I don't remember whether NanoVNA MOD installed it automatically, or I did in order to use that software. Neither do I know whether NanoVNA App needs it at all. Maybe not.

And then there is another driver that's required to upgrade firmware in DFU mode. This driver comes packed with DfuSe Demo, in a file named en.stsw-stm32080.zip. After installing DfuSe Demo using the setup program in that file, one has to manually install the driver from the appropriate Win directory installed by that setup program. In a normal Windows XP installation this ends up in C:/Program Files/STMicroelectronics/Software/SfuSE v3.0.6/Bin/Driver/Win7/x86. Running the exe file in that directory will install the driver required by NanoVNA App for firmware upgrade!

It just took me a while to find out... And I hope that this post may help others who have run into the same apparent dead end.

People using newer Windows versions, maybe 64 bit ones, probably need to find out where DfuSe Demo gets installed, and need to choose the proper Win directory and file. Being old-fashioned and using just Windows XP, I can only guess that.

Manfred

Hi Richard,

The term "bricked" is commonly used when irreparable damage has turned a device useless. In the context of firmware upgrades it refers to a failed upgrade that not only renders the device non-functional but also prevents any subsequent to repeat the firmware upgrade or to install any other firmware. This type of failure is common on microcomputers where the bootloader and the application code are a single firmware image that are being replaced together. However in the NanoVNA (all variants as far as I know) this type of failure is impossible because even if someone insists on installing the wrong application firmware, the bootloader is protected and all you need to do to recover is install the correct firmware.

Any original NanoVNA and NanoVNA-H (but not -H4!) can use the same firmware versions.
NanoVNA-H4 requires firmware made for NanoVNA-H4.
NanoVNA-F requires firmware made for NanoVNA-F.
NanoVNA2 requires firmware made for NanoVNA2.

I have a NanoVNA-H4 and it can be put in DFU mode (to install new firmware) by simply holding the toggle switch while turning it on. I'm not sure whether this is also the case on the NanoVNA-H (some 2.8 inch models of the NanoVNA require a jumper to be installed in order to put them into boot/DFU mode).

Therefore, stop panicking since your NanoVNA-H is not bricked (you just installed the wrong firmware made for the -H4 with a 4 inch display which is why you don't see anything meaningful on your 2.8 inch display).

Start by reading the excellent "Absolute Beginner Guide to the NanoVNA" (available in the Files section) and pay particular attention to the sections dealing with "Putting NanoVNA in DFU mode" and of course "The Firmware Upgrade Procedure".

73,
Thomas

Possibly the H4 firmware is for the 4” version – not the 2.8”?


From: VE2DX<mailto:ve2dx@...>
Sent: Tuesday, February 23, 2021 10:44 AM
To: [email protected]<mailto:[email protected]>
Subject: [nanovna-users] Bricked NanoVNA-H

Ok, after a couple of months on the shelve my 2.8inch NanoVNA-H Hardware version is bricked (I think!).

From my reading online, it sounds to be common, I just hope newer firmware will prevent this?

I downloaded NanoVNA-H4_20210131.HEX from one of your posts, hope it is the correct version, there seem to be many variations.

And I have an ST-Link V2 Mini STM8/STM32 unit coming from Amazon.

just a bit confused (a lot) as to what software I need to do this. Obviously, I can not do a DFU process, since I can not communicate with the unit even holding the select center switch during powerup using DFUSeDemo, can't find any devices. Tried the select key in all possible positions during power-up Nothing!

The exact symptoms, before I jump to a conclusion, are at power-up get white high raster screen with no data or graphics, battery led (RED) is flashing at approx 1 pulse/sec, upon power-up the Blue System LED does show some random activity and then starts flashing at approx 1 pulse/sec.

the unit is enclosed in a plastic enclosure, opening it the PCB is ided as NanoVNA-H V3.4

If this unit is NOT Bricked, then how do I bring it back? Hard reset?

hope you can help me

Thanks

73

Richard G. Desaulniers Sr., VE2DX

Ok, after a couple of months on the shelve my 2.8inch NanoVNA-H Hardware version is bricked (I think!).

From my reading online, it sounds to be common, I just hope newer firmware will prevent this?

I downloaded NanoVNA-H4_20210131.HEX from one of your posts, hope it is the correct version, there seem to be many variations.

And I have an ST-Link V2 Mini STM8/STM32 unit coming from Amazon.

just a bit confused (a lot) as to what software I need to do this. Obviously, I can not do a DFU process, since I can not communicate with the unit even holding the select center switch during powerup using DFUSeDemo, can't find any devices. Tried the select key in all possible positions during power-up Nothing!

The exact symptoms, before I jump to a conclusion, are at power-up get white high raster screen with no data or graphics, battery led (RED) is flashing at approx 1 pulse/sec, upon power-up the Blue System LED does show some random activity and then starts flashing at approx 1 pulse/sec.

the unit is enclosed in a plastic enclosure, opening it the PCB is ided as NanoVNA-H V3.4

If this unit is NOT Bricked, then how do I bring it back? Hard reset?

hope you can help me

Thanks

73

Richard G. Desaulniers Sr., VE2DX

On Mon, Feb 22, 2021 at 05:19 AM, Marc Verdi wrote:

@mirskym thank you for you thoughtful response. I will give it a try and let
everyone know the results. 73 de W6MGV Coxsackie, NY, USA

=============================================================================

I ran into the same problem with Windows 10 not seeing my NanoVNA in DFU mode. I found the fix via a Google search that led me to forum on www.deviationtx.com. One of the members by the handle of "Nuggetz" suggested that the driver in use was not the DFU version. This is what he did, and it worked for me:

Connect the NanoVNA and put it in DFU mode. Go into device manager and find the STM device under "Universal Serial Bus devices" (at the very bottom of the window). Expand this item and you will probably see "Hub Controller" and "STM32 BOOTLOADER". Right Click on "STM32 BOOTLOADER" and select update driver then choose "Browse my computer for drivers". After that, select "Let me pick from a list of available drivers on my computer".

The driver choices you see there should include "STM device in DFU mode". Select the DFU mode one and that'll do it.

If you don't see both "STM32 BOOTLOADER" and "STM device in DFU mode", then you probably need to install the driver using the dpinst_amd64.exe utility, found in the Win10 folder under Program Files(x86)/STMicroelectronics/Software/DfuSe v3.0.6/Bin/Driver.

Hope this Helps.
73,
Don, KB5QR

Hi Manfred,
In Windows XP, just copy the NanoVNA-App files to a folder in the C: / root directory and launch it. That's all.
Before that approx. a year ago I tested NanoVNA Partner under XP.
To do this, I wrote a pdf, here I described what needs to be installed for it to work.
Search for "Preparing to run NanoVNAPartner on Windows XP.pdf".
What is described here is necessary for the PC to recognize NanoVNA.
If you can’t find it elsewhere, it’s definitely there on my website.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

I can do searches just fine without it. I don't see the necessity for it.

Zack

On Tue, Feb 23, 2021 at 6:13 AM Alan G4ZFQ <alan4alan@...> wrote:

It's called a hashtag.

Properly used it's supposed to make message searches easier.
Only if it's used correctly, only for those that do search before they
post a question.

Alan

<>
Virus-free.
www.avast.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

It's called a hashtag.

Properly used it's supposed to make message searches easier.
Only if it's used correctly, only for those that do search before they post a question.

Alan

On Mon, Feb 22, 2021 at 08:46 AM, Zack Widup wrote:

I have a general question. What is the deal with the # symbols in the
subject line, in this case, "#features #nanovna-saver"? Is it some kind of
a secret code?

It's called a hashtag. A trendy, modern thing. I have not found a use for it.

--
Doug, K8RFT

On Mon, Feb 22, 2021 at 05:24 PM, Manfred Mornhinweg wrote:

NanoVNA-H in DFU mode, connected it, but NanoVNA-App doesn't see it.

As I remember doing it, NanoVNA-App does not use Dfuse mode. Try using NanoVNA-App without running Dfuse.
Just use the NanoVNA-App by itself. Run the app (with the correct port settings) to connect to the device, and Click the "double up arrows" icon - it has the tooltip "upload vna firmware".

--
Doug, K8RFT

What "same" problem?

Great Thread .... starting to understand this stuff ....:)

--
Cheers,
Ian
Melbourne, Australia

Does DfuSE find it when it shows up as STM32 BOOTLOADER? - If so it's only a matter of selecting the firmware file with choose, then clicking upgrade. I don't see that as any less friendlier :)

Mike,

Personally, I always use NanoVNA-App for firmware updates, rather than
DfuSE... much friendlier.

Could you perhaps help me in this? I was told to update the firmware in mine, but today I tried for about three hours and had no success. For some reason the driver doesn't seem to work. I downloaded the driver from the ST website as instructed in the user manual, installed it, it told me that all is fine, then I put my NanoVNA-H in DFU mode, connected it, but NanoVNA-App doesn't see it.

Checking in the Windows Device Manager, the NanoVNA shows up as "STM32 BOOTLOADER", with no driver installed.

I removed and reinstalled the ST driver, same result.

I saw that NanoVNA-App comes with a Zadig driver, I tried to run that one, but it tells me that it's not a valid Win32 application.

So, how is this done? Which is the correct driver to update the firmware from NanoVNA-App in Windows XP 32 bit?

The ST driver is claimed to be compatible with Windows XP, but maybe NanoVNA-App doesn't work with it?

Manfred

On Fri, Feb 19, 2021 at 12:44 AM, Adnan Yousaf wrote:

I want to use NanoVNASaver for continuously reading and storing S1.p data i.e.
automating my experiments for long duration tests (few hours). Since there is
no LabVIEW tool available for NanoVNA, I tried to use the Saver version v0.3.8
but with no success.
Would be great if someone has already a tip or solution in this context.

There is a Labview package for the NanoVNA V2+ and V2+4 written by joeqsmith. It is discussed on the eevblog at the link below which is the most recent discussion. He originally did not release this software because he did not want to offer user support. He has kindly released it and a manual BUT do not ask him for support. You can read his posts and the user manual and figure it out yourself.

eevblog link -
manual link -
software download - multiple zip files -

I have not used this software so I can't provide any more info. You will have to modify it to record the files but if you are a Labview user that should not be much trouble.

Good luck - Roger

This post is about measuring low resistances using the S11 method and testing the ESR of capacitors. It is surprising how well the NanoVNA can measure resistances that are much higher or lower than the system impedance of 50 ohms using the S11 method to calculate complex impedance R+/-jX.

For this test I used a SMA connector test jig, like the one I posted earlier, to measure a 1 ohm 0805 SMD resistor. The resistance of the part (soldered to a pin header) was first measured using a 4 wire Kelvin resistance meter at the following frequencies: DC - .990 ohms and at 100 kHz. - .995 ohms. Then it was connected to the SMA test jig. The sweep was from 10 kHz to 1 MHz. and there was excellent agreement with the Kelvin measurement. The graph is attached below.

The measurement of low resistance is something we are interested in when testing electrolytic capacitors. The equivalent series resistance ESR is an important parameter when using electrostatics in power supply filtering and in certain bypass applications. It is desirable to have a low value of ESR and a high ESR is one of the ways that an electrolytic can be checked for failure or selected for use in a circuit. Electrolytic capacitor manufacturers rate these components at a low frequency with 100 Hz. and 120 Hz. being the most common. The NanoVNA does not measure that low but recent firmware has been developed that goes down to 10 kHz. or lower.

A 10uF 50 V electrolytic from my parts bin was selected for this test. It's characteristics were first measured on a DE-5000 LCR meter. Note how capacitance and ESR both decrease with frequency.

100 Hz. 10.2 uF ESR of 6.5 ohms
1 kHz. 9.5 uF ESR of 2.0 ohms
10 kHz. 8.7 uF ESR of 1.3 ohms
100 kHz. 6.5 uF ESR of 1.2 ohms

The capacitor had 1" (2.5 cm) leads that were inserted into the pin header of the SMA test jig at the reference plane.

The results were very close to those obtained with the LCR meter (which is optimized for low frequency operation). Graphs are posted below. The rising "apparent capacitance" in the graph is due to the 1" lead inductance increasingly affecting the value of reactance measured as the frequency increases. This can clearly be seen in a test I did some time ago on a small 10 pf capacitor that was measured with long leads which were then shortened for comparison.

I hope this post has illustrated how a NanoVNA can be used to accurately measure capacitors if a decent test jig is used.

Roger

You started a new thread so it is not clear what the
"same problem" is.