¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Pitfalls of measuring components with the NanoVNA #measurement

 

I know it takes a long time to write such a detailed and informative post.
It took pretty much my entire morning.

But I have to admit that my morning started around 11 AM! ;-)


Re: Portable Analyzer Options

 

You get 2 out of 3 with the NanoVNA-H4. With the latest software you get 401 points and there is an SD card storage capability. On mine you have to file the case slot to access the SD card connector but maybe Hugen is now shipping with the slot cut already.

One of the big issues is seeing the screen in bright sunlight. I prefer my RigExpert for outside work.

Roger


Portable Analyzer Options

 

I am preparing for portable operations once the weather gets warmer. I want to take along a nanovna to troubleshoot issues on the field. One important requirement is the scrolling and input control has to be buttons, not the thumbwheel switch so that left me with two options, the nanovna-F version 3.1 form Deepelec.com and the nanovna-SAA-2N which I purchased form R&L Electronics. Both are in metal cases which is an asset for filed work. I use BNC connectors so I Install adapters on each unit and use a BNC calibration kit.

I can use the command set or a computer program to configure the nanovna but I do not want to use a laptop or smartphone in the field, just a standalone unit.

Some other requirements and my observations are as follows:

- Frequency Range 1 to 30 Mhz in 100kHz steps (301 segments)

nanovna-F : 101 segments - have to use 3 RECALL settings for resolution
nanovna-SAA-2N : 201 segments - have to use 2 RECALL settings for resolution

- TDR functionality : both units support function via TRANSFORM settings

- Save and examine results
nanovna-F : STORAGE S1P and S2P
nanovna-SAA-2N : no storage

Are there any other models which have button controls, at lease 301 segments and save measurement to storage?

Thanks,

Mike N2MS


Re: Bricked NanoVNA-H

 

Look like broken LCD module (or bad connection). Blue LED flash - mean normal scan, as i see your device worked, and can send data to CPU over USB.
Problem in LCD module (or in SPI bus), try check it connection.

Check all data lines (SPI, CS, Reset), power lines. See NanoVNA scheme.


Re: Bricked NanoVNA-H

 

I've put as many DFU files that i can find looking through the files section on here, put them into a folder and trying them one by one.

Just for the fun of it and scientific experimentation.

Regards, James.


Re: Bricked NanoVNA-H

 

I must admit Richard, I thought I was going to brick this little device but up to now, I've not managed too.

But I can get very similar results to you with the white screen.

I'd keep at it until you really can't take any more Hi Hi.

Regards, James.


Re: Bricked NanoVNA-H

 

Not all will work on your device Richard from what I believe so keep trying.

I did try some recently and had the same result as you.
Flashed it manually and the white screen stayed there.

Keep trying as there are many to choose from but finding the right one for your device could take a while I would say.

The NanoVNA-App software seems to be able to make that decision for you though and selects the right one for your device.

I'm still learning myself as I've only just started to dabble with flashing the device so I'm open to the experts on here.

Kind regards, James.


Re: Bricked NanoVNA-H

 

Hi Richard, its an option when you run the NanoVNA-App software.

This latest software has it built in.

When you run the NanoVNA-App software and select the two points button at the top of the page, another window drops down where you can select one of two firmware for the device. There are three to choose from but it will only let you use two of them as it knows which device is connected to the pc.

Once your NanoVNA device is in DFU mode, you can literally press the firmware version button and the rest is automated.

You can manually flash from a folder saved to your drive any of the many DFU's written for the device if you want too.

There are plenty to choose from and can be found in the files section of the groups.

This is where i got the H4 version that i tried.

Link to many can be found here too

/g/nanovna-users/files/Firmware/All%20%28known%29%20publicly%20available%20NanoVNA%20DFU%20files%20from%20May%205,%202019%20through%20to%20Sept%2029,%202019

Hope it helps. Kind regards, James.


Re: Bricked NanoVNA-H

 

all ok found it and 1.045 in files section here...

tried both, loaded 3 times each and recycled power got the same result each time

natta! nothing on the display...

goo try


Re: Bricked NanoVNA-H

 

On Thu, Feb 25, 2021 at 10:09 AM, James Anderson wrote:


DiSlord H v1.0.39
James where did you download it from...you got a link please


Re: Pitfalls of measuring components with the NanoVNA #measurement

 

Manfred,

I know it takes a long time to write such a detailed and informative post. Thanks for posting!

Regards - Roger


Re: Pitfalls of measuring components with the NanoVNA #measurement

 

This was a fantastic read! Thanks Manfred!

I used type 43 material to wind a common mode choke for HF frequencies recently. It seems to give about 30 dB attenuation with small signal stimulus, however, I was wondering how it would behave under power.

Regards,
Gregg

--
VE6WGM


Re: Nano VNA: An Antenna Stethoscope ( pdf file latest edition de k3eu )

 

Barry Thank you for that wonderful line " 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".
I took out a lengthy period and left the Audio Engineering industry and
started teaching Electronics & Sound Engineering to Level IV. The first
book I read in preparation was Isaac Asimov's Guide to Science. I always
had in my mind... "What happens if that kid at the front asks "Yeah but
really Why???".

On Thu, 25 Feb 2021 at 17:11, Dave Daniel <kc0wjn@...> wrote:

365 MB


On 2/25/2021 10:32 AM, Bob wrote:
What is the size of the mp4 file?

--
This email has been checked for viruses by Avast antivirus software.








Re: Bricked NanoVNA-H

 

Hello Gyula and thank you for the reply and the tera term and putty info.
I¡¯ve watched a couple of videos after posting too but thank you.

I was just trying a few things out to try and resemble Richards predicament.

I was just curious as to how the smaller Nano that I have would react to me fooling around with it.

I¡¯d read somewhere that it was difficult to ¡°brick¡± it so did some experimenting.

And for what they cost, even if I did brick it, it wouldn¡¯t be the end of the world.

I¡¯m just hoping that it is firmware based and not hardware for Richard.

Very kind regards, James.

On 25 Feb 2021, at 18:11, Gyula Molnar <gyula.ha3hz@...> wrote:

?Hi James,
I think you choose the firmware versions based on your idea and meanwhile mix the firmware written for the 2.8 "and 4" (3.95 ") versions. Yet these should not be confused with each other because they use a different microprocessor. They will not work with the firmware written for the other.
For example, you are writing here: /g/nanovna-users/message/20975 -H4 you are experimenting with firmware. Do not do it.
You may not allow the other to charge immediately.
Managing terminal programs For PuTTY, the Port, Speed ??and Serial markings must be set in the Configuration. You can find their information in PC Device Manager when you connect to your device.
All three data must match for PC and PuTTY.
I assume that the driver is already on the PC, so if the connection is successful, it is advisable to type the word 'help' when the cursor is flashing, because in response you will see the possible commands.
In the wiki or files folder you will find a list of possible consol commands and what commands they accept.
You can also find more on the website of the creator of the given program.

73, Gyula HA3HZ

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





Re: Bricked NanoVNA-H

 

Hi James,
I think you choose the firmware versions based on your idea and meanwhile mix the firmware written for the 2.8 "and 4" (3.95 ") versions. Yet these should not be confused with each other because they use a different microprocessor. They will not work with the firmware written for the other.
For example, you are writing here: /g/nanovna-users/message/20975 -H4 you are experimenting with firmware. Do not do it.
You may not allow the other to charge immediately.
Managing terminal programs For PuTTY, the Port, Speed ??and Serial markings must be set in the Configuration. You can find their information in PC Device Manager when you connect to your device.
All three data must match for PC and PuTTY.
I assume that the driver is already on the PC, so if the connection is successful, it is advisable to type the word 'help' when the cursor is flashing, because in response you will see the possible commands.
In the wiki or files folder you will find a list of possible consol commands and what commands they accept.
You can also find more on the website of the creator of the given program.

73, Gyula HA3HZ

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


Re: Nano VNA: An Antenna Stethoscope ( pdf file latest edition de k3eu )

 

So it was :-)

My apologies.

Regards,
Gregg
--
VE6WGM


Re: Nano VNA: An Antenna Stethoscope ( pdf file latest edition de k3eu )

 

365 MB

On 2/25/2021 10:32 AM, Bob wrote:
What is the size of the mp4 file?
--
This email has been checked for viruses by Avast antivirus software.


Re: Nano VNA: An Antenna Stethoscope ( pdf file latest edition de k3eu )

Bob
 

What is the size of the mp4 file?

--
W7BE Bob


Re: Pitfalls of measuring components with the NanoVNA #measurement

 

Mike,

how do you characterize ferrites and powder iron (rod and toroid) for useable
frequency as inductors/choke, transformers, and wide band transformers?
As Jim pointed out, you wind a few turns on the candidate core, and measure its complex impedance over the frequency range you are interested in, and a little around.

But that's only the first step. In that measurement you can see how much inductance and how much resistance you get at any specific frequency. These will scale in proportion to the square of the number of turns. When you use many turns, you will also get strong effects from stray capacitance between all those turns, and you can see the capacitance too if you measure such an inductor.

You can then decide in which frequency range you want to use each core, depending on application. For example, if you want to build resonant circuits, lowpass filters and the like, you want to use a core only in the (low) frequency range where it provides nearly pure inductance. You can use the software to get the Q values at different frequencies. You will typically want a Q of 30 at the very least, to get low filter losses, and much higher than that in power applications. Certainly above 100, while the best you can achieve might be something like 300 to 400, using a good core in its best frequency range.

On the other hand, if you want to build a transformer, you want a core that provides a high enough impedance, and you can trade quite a bit between this impedance being provided mainly by inductance, resistance, or by a mix of them. For a broadband transformer typically you would look for a material that at the low frequency end provides most impedance by inductance, and use a number of turns that provides an impedance of at least about 3 times the load resistance. Some people prefer 5 times, perfectionists prefer 10 times. It depends on how much inductive reactance your circuit can handle. You also need to watch that the resistance associated to that inductance is low enough to cause only an acceptable amount of loss.

At the high end of your frequency range, this same core will typically provide a high, although almost purely resistive impedance. So it has very little effect on the circuit, but still you need to calculate that the loss will be low enough.

But you always have to be aware that the NanoVNA measures with very small signals. You can apply those results directly to small-signal circuits, but when you are dealing with large signals you need to do additional measurements, using a high drive level that the NanoVNA cannot provide. This is required because core materials typically are non-linear with drive level. The kind and amount of nonlinearity varies with the material, and is often poorly documented by the manufacturer. While several manufacturers do give loss graphs for their power materials, these graphs often don't extend into the frequency ranges we need.

A "PowerVNA" could be used to measure thereactance and resistance at various drive levels, to draw curves for the power behavior of a core. Lacking such an instrument, what I do is applying various drive levels from a ham transmitter, and directly measuring the rate at which the core heats up. Then I calculate the power loss from this, and use it to draw loss curves.

The result is that some materials are great at low drive levels but less good at high drive, while others tend to be mediocre in terms of loss at low drive but don't worsen much at higher drive. And all this is highly frequency-dependent.

In applications where the transformer or inductor has to carry DC in addition to your signal, it's essential to also evaluate how much flux density will be caused by this DC, and how much that will affect the core's behavior towards the signal. You need to make sure that the core can handle the DC while staying well away from saturation. That requires using a long enough core (in terms of path length), of a material that has low enough permeability. It helps if the material has a high saturation flux density, which you can get from the datasheet, or you can measure it with a power inductor tester.

When you need a core for EMI suppression, you want it to provide the highest possible impedance over the frequency range you need to suppress, and it's a bonus if this impedance is mainly resistive.

Attached are impedance measurements up to 250MHz for two large toroids with 2 turns on each: A T-200-2 powdered iron toroid, and an FT-240-61 ferrite one. You can see that the powdered iron toroid provides almost all of the impedance in the form of reactance, up to a frequency of at least 200MHz. It's high Q material. But the impedance is rather low, at 20MHz it provides only 27? or so. The bending-up of the reactance curve at VHF probably means that we are nearing the parallel resonant frequency with the stray capacitance, while the resistance bending up is due to increased core losses towards VHF.

The graph for the ferrite toroid shows such a high Q zone only up to about 15MHz, but it provides a lot more impedance, around 130? at 20MHz . Above that frequency the core starts providing a quickly increasing amount of resistance. At 250MHz essentially all of the impedance comes from resistance.

What does this mean? Well, the #2 powdered iron material is great for making high Q inductors in the HF range, and even into VHF, at somewhat lower Q. But it's a poor transformer material and would be lousy for EMI suppression over the entire range. The #61 ferrite instead can be used to make inductors in the range up to 15MHz or so, and is a good transformer material from a few MHz to the end of the measured range and beyond. In the VHF range it's also a decent EMI suppression material, and towards UHF it's excellent for EMI suppression.

That makes the question arise, how can the same material be good for EMI suppression (which requires energy absorption, that is high loss) and for transformers (which require low loss), in the same frequency range? Simple: It's a matter of number of turns versus circuit impedance. For transformer use, you wind enough turns to get an impedance that's very much higher than the circuit impedance, so the resulting loss is low despite the core providing almost a pure resistance. For EMI absorption instead you use so few turns that the choking impedance is similar to the circuit impedance. That will make the core "suck up and destroy" unwanted RF signals. It will turn them into heat.

Enough writing for now. For loss measurements at higher drive levels, see



And if you need a power inductor tester, you can copy mine:



So you can complement the NanoVNA with those tools, to more completely characterize any mystery cores you might have laying around.

Manfred


Re: Bricked NanoVNA-H

 

Can I suggest that you try and flash the latest firmware from the top of the NanoVNA-App.

Select DiSlord H v1.0.39 and it should come back to life for you.

Fingers crossed anyway.

I've flashed mine now twice with the wrong dfu and it white screened on me.

I then reflashed the device and it started working again with the screen showing.