开云体育

It has been suggested that I update my NanoVNA-h device but as I am not used to updating any software, I need step by step instructions, with no steps missing. In otherwords evert click or data entry in logical order.
Please.

You can't do any permanent harm to the -H, so just follow the instruction in the Wiki... there's plenty of help there.



Mike
M0MLM



------------------------------------------------------------------------
*From:* ray.dentong7tqt@...
*Sent:* Tuesday, 19 January 2021, 11:50 am
*Subject:* [nanovna-users] NanoVNA-H software update #nanovna-h

Some say that we learn best by making mistakes - and then correcting them.
Don't worry too much - as Mike said, you can't hurt it!
Just accept the fact that you might have to try more than once.
I found that for me, the hardest part was clicking the right 'buttons' in the DfuseDemo upload program. (The worst that happens is that the file doesn't upload!)
--
Doug, K8RFT

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

Mike

------------------------------------------------------------------------
*From:* DougVL [mailto:K8RFTradio@...]
*Sent:* Wednesday, 20 January 2021, 12:43 pm
*Subject:* [nanovna-users] NanoVNA-H software update #nanovna-h

Very true. Unfortunately for me, it wasn't created yet when I did most of my firmware changes. So it's 'habit' now, that brings me to use DfuSE.
Your reminder will help me remember to use NanoVNA-App. Although new firmware versions are slower in coming, these days.
(I also have & use a NanoVNA-F. To upload firmware to it, one only needs to copy the file to the Nano with Windows Explorer.)

--
Doug, K8RFT

Yea - I use DfuSE too and no plans to change as I use it for other devices also. New firmware slowing as probably getting near the limits of what the hardware is capable of and what is useful :)

Hi,
Where do I find the above referenced "NanoVNA-App", I do not see this in the FILES section. I assume that this software makes it easy for a non-computer person to do the Firmware Update.
Glen Jenkins, WB4KTF, Austin, TX

Use the search function in the forum messages and you'll find my mesg with the link - I don't recall it offhand

The firmware updates so far have been designed to perform as many operations as possible from the built-in processor.
This was approached by two very active programmers and one of them developed the firmware (DiSlord) and the other the PC software (OneOfEleven) to a higher level.
No further development is likely to be expected, so I strongly recommend that anyone who can install the latest 1.0.45 firmware and use NanoVNA-App v1.1.205 (Windows) on their computer.
Many thanks to them for making the improvements in their spare time, all selflessly.

73, Gyula HA3HZ

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

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

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 :)

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

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. ( ) ***

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 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. ( ) ***

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.

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. ( ) ***

On Wed, Feb 24, 2021 at 04:33 AM, Gyula Molnar wrote:

when the device is connected to the USB port in DFU mode, then the device is not available on the Communication port,

Yes, in DFU mode the NanoVNA is only a memory storage device, not a 'computing' device. No communication, no calculating, no measuring. It is just a "solid state disk drive" thing.

--
Doug, K8RFT

On Tue, Feb 23, 2021 at 12:03 PM, Manfred Mornhinweg wrote:

And I hope that this post may help others who have run into the same apparent
dead end.

Thanks for publishing your actions and results!

Please seriously consider writing that up as a sort of "magazine article" and posting it in the group's Files directory. It's a lot easier to find things there than to try to search through a zillion posts in so many threads.

--
Doug, K8RFT