开云体育

Thank you for the feedback.
Unfortunately, the developers of the program made a mistake somewhere.
--
Gyula HA3HZ

not a circle but a green line
--
Gyula HA3HZ

What was left out:
I installed the firmware downloaded from the DiSlord Github site on my own machine and installed it. It works.
As for nanoVNA-D, since then version 0.8 and all other firmware has been DEVELOPED by Dislord and created as used. You rightly mark it with -D! :-) And not only develops -H, but all related nanoVNA families: -H, H4, V2, Lite

(I hate machines that distort what I have to say)
--
Gyula HA3HZ

Hi Ian,
This is when I usually pull out my own machine and do the operations all the way through so as not to miss steps.
To see what happens please launch a tiny program called USBDeview without installing it.
This allows you to see what your USB port is seeing.
Here are two examples: when I put it in DFU mode, you see it as "STM Device in DFU mode". When you want to communicate via the USB port, you will see it as "STMicroelectronics Virtual COM Port" on the USBDeview monitor in the green circle. Attention: USBDeview will show all USB drivers installed since you used your computer. When you connect, a solid green circle at the beginning of the line will show the current connection.

So you identified that you are in dfu mode.
You will then start the DfuSeDemo program, where you will see: "STM Device in DFU Mode" by clicking on the Available STM Device window in the upper left corner. Now you know that your .dfu program sees nanoVNA.
You need to find the .dfu on the machine you want to upload. You can check this by clicking the "Choose" button below the text "Upgrade and Verify Action". Press "Upgrade" to upload to nanoVNA. In the meantime, there will be a window confirming that Yes, I want to.
You will then remove the USB plug from your computer. After removal, nanoVNA will restart.

In my previous post, I wrote that the DFU and COM ports have different drivers. You can see it here.

When nanoVNA is in DFU mode, it is not visible on the COM port. When nanoVNA is in DFU mode, it will remain in that mode until you load a compatible dfu program on it.

Let's work.

--
Gyula HA3HZ

I had a very similar problem with my LiteVNA when I was in the process of preparing for firmware update. Opened it up, disconnected the battery, and then reconnected after a few minutes, it came back to life

Best wishes

Mike G8EII

Hi all,

I should have included in my Post above that with the nanoVNA H in "white screen mode", the nanoVNA is not recognised at all by my PC, no COM port recognition, no Windows Pinging, nothing.

I am comfortable in having a go at shorting out of VDD and Boot0 Pins, if that is the only way to bring it back to life.

And I am asking for some advice as to whether the file "NanoVNA.H.v1.1.00.dfu" file in the GitHub pages for "nanoVNA-D" is the correct Firmware upgrade for my nanoVNA, before I repeat the same mistake ..... :(

--
Cheers,
Ian
Melbourne, Australia

Ian, Assuming you can "see" the device in DFU mode... Not on a com port, but rather as below.(assuming windows device manager)Try loading or reloading the correct firmware. I have never seen the white?screen you are describing. But, as they say where there's life, there's hope. The odds you did permanent?damage by misloading wrong code is virtually nil.

Hi Chris et al,

I am an absolute beginner when it comes to the software updating/drivers etc etc ... and yes, that Guide is excellent. Yesterday, I was making a dumb mistake.

That aside, I now have a completely white screen on my nanoVNA H ... I have the nanoVNA-App latest version v1.1.208 downloaded and running, my nanoVNA H had been running DiSlords v1.0.69 firmware for several months, I can put my nanoVNA into DFU mode ... as recognised by the nanoVNA-App and Device Manager etc ... after pointing the App to DiSlord v1.1.00 and running it, I got a message within the App saying to power the nanoVNA off and on. That's when the white screen appeared.

I think the white screen is caused by using the wrong firmware. But as stated in my first Post I have used the "NanoVNA.H.v1.1.00.dfu" file in the GitHub pages for "nanoVNA-D".

Have I used the wrong Firmware file?? Powered off and on incorrectly (nanoVNA was still connected to PC)??

Any help appreciated ....
---
Cheers,
Ian
Melbourne, Australia

On 3/10/22 6:22 PM, AG6CX wrote:

Hello Jim:

Hope this finds you well.

Looking at a reply of yours to nanoVNA users back a year or so (referenced herein) and your Excel spreadsheet, I’m wondering if you were dealing in the power domain when you suggested rho = 10 ^ (mag S11/10) ?

I have used rho= 20^(mag S11/10) when converting between S11 and Z.

Given that your spreadsheet is working the impedance, with Z= Zo x (1 + Gamma)/(1-Gamma), I would have anticipated seeing the rho = 20^(mag S11/10) form of conversion.

Please advise if I have this fouled up.

Thanks,

probably - rho is the voltage reflection coefficient so 20 log10 would be the right calculation.

Hello Jim:

Hope this finds you well.

Looking at a reply of yours to nanoVNA users back a year or so (referenced herein) and your Excel spreadsheet, I’m wondering if you were dealing in the power domain when you suggested rho = 10 ^ (mag S11/10) ?

I have used rho= 20^(mag S11/10) when converting between S11 and Z.

Given that your spreadsheet is working the impedance, with Z= Zo x (1 + Gamma)/(1-Gamma), I would have anticipated seeing the rho = 20^(mag S11/10) form of conversion.

Please advise if I have this fouled up.

Thanks,

Ed McCann
AG6CX

Greetings, Although you may not actually be an absolute beginner, may I suggest you have a look the the
very comprehensive guide to the nanovna. I must say, I have found the information contained very helpful
indeed. Please take a look at the linked file below, and I hope you find it helpful as well.
===> LINK:===> /g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf

Thank you!
It works now.

?n joi, 10 mar. 2022 la 23:00, HA3HZ <gyula@...> a scris:

Hi Larry,

Thanks for the reply. I don't think code written in 2019 (for the H variant) will work on the H4 or F variants; they use different hardware architectures.

That would make this a feature request for the current H4 / F line up, as of March 2022.

Regards.

Yes, it works now. Thank you.

73,
Cliff, AE5ZA

On Thu, Mar 10, 2022 at 01:06 PM, Kevin Zembower wrote:

Thanks, again, for everyone's help and advice. Now, on to building the folding
J-pole.

Just make sure if you have a good RF choke on that J Pole. They are notorious for radiating off the coax feedline. They also de-tune quickly if any objects are in the vicinity.

Roger

Just to bring this thread to a proper conclusion:

I finally completed my measurements. My window line was 202 3/4 inches long, so 5.150m. Sweeping from 7-17MHz showed a crossing of the R line of the Smith chart at 11.410MHz. With wavelength = C/frequency, I got 26.27 meters as a full wavelength and 6.569m as a quarter wavelength. 5.150/6.569 = 0.7840 for the velocity factor, close to the spec that Bob found of 0.80.

Thanks, again, for everyone's help and advice. Now, on to building the folding J-pole.

-Kevin
KC3KZ

Thanks to the forum users, the bug is with the program developers. A script that uses Java now works with a hack. The solution was posted on another forum, I posted a fix, it works for me now.

So the problem is SOLVED.
Sorry for the annoying mistake, thanks for your attention.

--
Gyula HA3HZ

The VNA-App is shown on the com port, .dfu needs another driver inside the DfuSe program / Bin folder.
--
Gyula HA3HZ

Problem SOLVED

--
Gyula HA3HZ

Hi Jim,

I found a solution in the forum for the Google translate module to work. It was a problem for others as well, so I have already found the solution as many users. Thanks to the users who provided a solution on the forum.
I hope it works for someone else now!

--
Gyula HA3HZ