开云体育

Hello everybody,

Because the product can be connected to multiple versions and multiple operating systems, it’s pretty hard for everyone to “chew by mouth” what to do.
I’m not even talking about people being at different levels of electronics knowledge.
Therefore, in many cases, the description is either too detailed or provides too little information.
When someone asks a question, they either know the answer (it mostly turns out the way they ask) or don’t really understand what they need to do.
In the latter case, he is still in an enhanced nerve condition. It is nervous that this is happening with His structure.
So there are many of us and we react to a given question or answer in many different ways.

The forum will help us try to solve the problem.
As the firmware and PC software development of the products is likely to push its limits, there is probably not much development i.e. change not expected.
We know the time course of product development. For those who don’t know, it’s worth reading my website.
From the first release, I try to gather the information and if I find that someone else needs to know it, I will publish it.

Now, for example, a firmware upgrade has occurred.
In DFU (Device Firmware Upgrade) mode, the device cannot be accessed through a COM port.
After all, the firmware required for the operation of the device is uploaded (or downloaded).
In DFU mode, the device driver must be searched among the USB contollers as the STM Bootloader driver when the device is connected to the USB port in DFU mode.
I repeat, then the device is not available on the Communication port, it makes sense.
Earlier operating systems required more manual installations, there were no automatic driver installations.
We learn all this together. You can just build on the basics, do you.

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

Hi everyone

Thank You Don, for msg #20899
A little addition for those who run into this problem under Windows XP.
The STM Bootloader driver is not automatically installed on this operating system when installing the DfuSe demo, so you must do so as above (exclamation point in yellow triangle for USB contorollers in Device Manager) after placing NanoVNA in DFU mode and PC USB connection in Device Manager.
So look for the error message, click on it, and after unpacking, mark the STM Bootloader Driver package so that the system can install it.
If you have already installed something, delete it and install it. This package also solves the problem on XP.
Link:
If you still get stuck, visit my website as well.

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

Barry-

Very nice presentation on the basics of VNA analysis. Quite well done. I’m sure you put in considerable time on it.

After doing a quick review of your slides there were only a couple items that I felt needed correction.

They both relate to your discussion of TDR measurements using a VNA. In slides # 9 and 19 you speak about pulses of RF being sent out. That would be correct for a conventional TDR, however the TDR plots generated by a VNA are created by applying a FFT to the steady state (not pulsed) reflected signal of the VNA. No electrical pulses are involved. The TDR function is based on the mathematical FFT.

The remainder of the slide set looked pretty good based on my quick reading.

Best Regards,

Ray
WB6TPU

Here is my latest rendition of the pdf file: Nano VNA: An Antenna Stethoscope
After giving a few Zoom club talks on the Nano VNA, I've changed my approach a bit.
This is still a very basic look at how a VNA can be used as a "tool" in your antenna toolbox.
I hope it explains why impedance changes with feed line length and approaches resonance in a novel way.

Feedback is appreciated, both on and off this IO group.

de K3eui
Barry
West Chester PA
k3euibarry@...

Good Afternoon,

Did you reset and calibrate per band you were sweeping? In my
experience, getting those kinds of results usually means either the antenna
is not resonant on those bands or there is something wrong with the
calibration. I usually calibrate each band separately and save them out.
Set the sweep start and stop points. Go to the calibration menu, hit
reset, then perform a calibration.



Jim Barber
KJ7JGB
Phone: 503.547.9524
<>

Properly used it only links to other subjects with the same hashtag - it's superfluous in a group like this and should be constrained to twitter where the trendy junk originated from..

Don:

You were spot-on. I opened Windows Device Manager, manually updated the driver to the DFU-capable driver. NanoVNA H is now running version 1.x build from Jan 2021.

72,

Marc, W6MGV

Ref Dave W0LEV antenna drawing

I don't see any dimensions for the horizontal elements? Can you add them to drawing?

Thanks

On Mon, Feb 22, 2021 at 11:58 AM, Chris wrote:

I’m having exactly the same problem

Well then, you should try the same solution.

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