开云体育

It was posted and recorded by AJ3DI back a few messages





This recording (about an hour long) missed the first few minutes, which I thought were essential to compare the Nano VNA to an Antenna Stethoscope and a Smith Chart to an EKG of your heart.

But it is what it is

73
Barry k3eui
K3euibarry at gmail.com

On 2021-02-25, at 16:23, James Anderson <james21170@...> wrote:

This is the excellent and to date latest version of the Guide Richard.

/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf

/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_6.pdf

FTFY.

Grü?e, Carsten

Hi Richard,
So now that you have performed the operations I described in the message /g/nanovna-users/message/20945, you have not forgotten to remove the BOOT0-VDD jumper and it will log in white the next time you turn it on.

What you wrote next, I don't understand:
In the message /g/nanovna-users/message/20957, he writes that he wanted to join VNA-QT and could not.
Why would you want to use a program made for another device for this NanoVNA-H ???
Each device starting with NanoVNA uses different firmware and the PC programs created for it do not match.
Here you may need a terminal program to check if your device is accessible via the COM port, even though you log in with a white screen.
Such a terminal program is Tera Term or PuTTY or if you know another one. If you don’t know, choose from the two above.
If you have a problem with the display, you just don't know that the foil connection between the display and the pcb has ever dropped and broken, so a white display is possible.
So telemedicine is difficult because there is always someone to tell His story to help, disrupting the successful error delineation.
So there we are, there is a chance that there is hardware damage if you still see a white screen and there is no information on the screen.
73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

OK!

Signed! Sealed! Delivered! and up here in the GREAT WHITE NORTH that means a lot...

I WAS able to communicate with the NanoVNA-H and worked 100%

thus my final conclusion is that my unit is WORKING, but the display or circuitry driving the display is not!

so it is a BRICK made of FOAM :P

I can use it if attached to a PC but not in the field...

will look closer at the display, but probabble aint worth it...

James and the rest of the GANG! Many Many Thanks! you guys are a great bunch

73

Richard VE2DX

This is the excellent and to date latest version of the Guide Richard.

/g/nanovna-users/files/Absolute%20Beginner%20Guide%20to%20The%20NanoVNA/Absolute_Beginner_Guide_NanoVNA_v1_5.pdf

I just downloaded the NanoVNA-App.rar and installed that, from there I ran the software and upgraded to the latest version for my NanoVNA device.

I'm kind of hoping that it'll get your device up and running as after this, I really am out of ideas.

Kind regards, James.

Take a look in the files section and look for the guide, An Absolute beginners guide and it lists all the software as links in the PDF.

Here's the link.

I've very little else to right now Richard, I'm one of the shielders in the Uk.

I got all my info from here Richard, /g/nanovna-users/topic/a_guide_for_absolute/78077375?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,78077375

There's a lot to read through but Like I say, I've lots of time on my hands right now.

The NanoVNA-App software is really up to date and a huge improvement on other software that I've used in the past.

This lets you upgrade the firmware from the program which might get you up and running.

It sounds good that you're seeing a com port so that's a start.

Kind regards, James.

It can be hugely frustrating when thing don't go to plan but it looks like you're getting there.

James thanks for all the help, almost like good old pre-covid lab work sitting next each other :P

ok, the NanoVNA is seen as Com 44, was a simple serial port but after updating the driver did see it as "STMicroelectronics STLink Virtual Com Port (Com44)"

where did you download the PC software that you are using what is is called... let me load it so that we may compare apples and apples...


73

Richard,
I have just tried to connect my freshly upgraded NanoVNA device to the VNA-QT software but it keeps giving me this error.

xavna_read_autosweep_failed: Resource deadlock avoided

I know my NanoVNA is on com port 3 three as its in device manager. Using com port 3 it WILL connect to NanoVNA-App.

Hope that helps.

Hi Barry

Is the recording available to see somewhere? Do you have a link you could post?

Regards,
Gregg

--
VE6WGM

Hi Richard.

Have you tried the NanoVNA-App software to do the upgarde.

I upgraded using the option from NanoVNA-App 1-of-11 LSI.

Can you see the NanoVNA in device manager as STM Device in DFU mode within Universal serial bus "controllers"? This for me was critical to connect to the NanoVNA device.

I know you've stated that you can see it as STM Device in bootloader mode but it has to be in STM Device in DFU mode in device manager within Universal serial bus controllers to get connected.

If after that either works or doesn't work then I'm out as I can't think of anything else for now.

I'm just checking out VNA-QT as I write.

Kind regards, James.

I'll have to check out what that VNA-QT is now Richard as I'm not familiar with that.

The only procedure that I did was as described and it worked for me after nearly launching the NanoVNA through the window Hi Hi.

The NanoVNA that I have is a very old first edition I would say unit bought about three years ago so really needed upgrading.

Hope you're getting there with it though.

Regards, James.

Here is an update at this point...

PLEASE! read the complete thing before responding!

device : NanoVNA-H
Screen: 2.8inch
hardware version 3.4
Serial : 20051698
Problem: Unit powers up with white screen
Red LED: Flash 1/s approx
Blue LED : Flashing 1/s approx
DFU Mode: was able to get unit in DFU mode by shorting BOOTO and VDD holes on pcb, note there was no jumpers.
Win10 while in DFU Mode: Commes up as STM32 Bootloader.
Firmware procedure: Using DfuSeDemo was able to find the STM32 Bootloader device, load the firmware ( NanoVNA-H_20210130.bin ), upgraded to NanoVNA-H properly, and ran verify that camme back ok.
Rebooted the NanoVNA-H
unit is still unable to display anything but blank WHITE Screen
Hooked up the device to a USB Port, try connecting to proper comm port (Com44), would not connect to VNA-QT
Hooked up any NanoVNA to same USB port could connect to VNA-QT without any problems

73

Richard VE2DX

After pressing the two points you should be presented with this next screen.

And no problem Richard, this was driving me crazy yesterday trying to connect, but untill the driver is installed to make the computer "see" the NanoVNA in DFU mode, then you simply can't proceed.

Hope it helps.

Another picture for you as it tells a thousand words.

Regards, James.

You can all thank AJ3DI Jim, my benefactor, for introducing me to this gadget called Nano NVA.
It forced me to take another look at many concepts: resistance, reactance, impedance, PHASE, and of course, how useful (or bewildering) a Smith Chart can be.

Of course, at my PhilMont Mobile Radio club presentation (over an hour) it was recorded, and although Jim missed the first couple of (very essential) slides, the talk can be viewed by anyone.

Each time I give this talk, I learn more about what the hurdles are. I find, as a teacher, we can "say the words and answer multiple choice exams without any REAL understanding".

My goal was to slow down enough for folks to see "resonance" and "phase" like a kid swinging on a swing and grampy (our feed line) giving the essential push to keep the current (kid) swinging.
A crude analogy, of course, for resonance in an antenna.

So have fun watching the video if you choose to spend an hour that way.
I usually prepare for many more slides than I actually show (rookie error).

Feedback is apprediated: K3euibarry at gmial.com

73
Barry

Sorry Richard, its two points not two cogs in the NanoVNA-App software to upgrade the firmware. Hopefully there's a picture attached.

BTW James THANKS for the step by step...

this will help others a lot... the shorting of VDD and BOOTI was confusing since most procedures and comments talked of a JUMPER... there was none here...

James, thanks for the input, as I stated below l was able to get the device in DFU mode after shortening the pins (not a jumper on this version)

found the device...

was able to load it

but as I stated below, the unit boots up after power-up reset to a blank white screen

the unit cannot be reached via the VNA-QT application

note please I have another unit that CAN be reached with VNA-QT

Larry also very good point about trying via the Win10 app did not work will try terratem to see and let you know