¿ªÔÆÌåÓý

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

Re: NanoVNA-H4

 

Hi Joe

You seems need an S21 Logmag measurement , Knowing that dynamic range of H4 on the UHF are limited to 50db you should not expect more then -45db values for the isolation measurements between the Two bands, obviously you need a 401 sweep points , and many complete 401 point calibrations for each bands (with isolation and Throught) , each calibration should be focused on the desired slice of the band under test, you need to reset the old calibration for each new calibration to be sure to avoid interpolation errors ,
Good Luck.
73's Nizar


NanoVNA-H4

 

I have a NanoVNA-H4,

I have no problems checking antenna SWR etc.

But what I want to do now is to check the performance of a "Diplexor"
You know one of these things that splits/combines a 2 meter and 440 antenna into one common output.

You know one of these.

<>
I want to measure the insertion losses for each band.? and then the amount of isolation between the bands.

Can anyone show me a video on how to do this? OR give me a step by step on how to do it?

Joe WB9SBD


a little confusion in vision between 0 and 8 on the display

 

Hi

May be not a very objective vision, it seems to mee that there is a little confusion in vision between 0 and 8 on the display, with SEESII H4 + DiSlord 1.2.40 , I prefer a simple 0 graphic display without the strike symbol , it will make the screen easier .

Thanks
73's Nizar .


Re: NanoVNA port renormalization

 

Hi PY2CSH

For me per example , I prefer set Z port 1 to 75 Ohm virtually and keep Z port 2 to 50 Ohm as it's physically , so it can be very handy option for who need it .

73's Nizar


Re: NanoVNA port renormalization

 

? ... I personally don't see the need to have different Z for the input and output of a DUT. ... ?

How about a matching network, say matching 50 to 20 ohms?


Re: NanoVNA port renormalization

 

Roger,
You are correct. There is no added matching circuitry. It's all math. The physical connections are the same for both plots.
--John

On Mon, Feb 10, 2025 at 09:18 AM, Roger Need wrote:


On Sun, Feb 9, 2025 at 11:56 PM, John Gord wrote:


Each is shown at 50 ohms and again at a higher Z that gives a better match
Maybe I am interpreting this incorrectly. Your comparison shows with PortZ =
50 and PortZ = 430. The Smith Chart marker shows almost the same input
impedance in both cases so it appears you did not use an L pad, resistor or
transformer to get 430 ohms on input and output of filter. Is my assumption
correct?

Roger


Re: NanoVNA port renormalization

 

What NanoVna are you using
________________________________
From: [email protected] <[email protected]> on behalf of Team-SIM SIM-Mode via groups.io <sim31_team@...>
Sent: Sunday, February 9, 2025 10:57 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] NanoVNA port renormalization

Hi
This is my point of view : Z--> option does not change the physically pot2 impedance , it remaine always at 50 Ohm +/- 1 ohm value, just firmware by computing way can display S11 or S21 as its at 75 ohm or 300 ohm , for example seting it at the accurate physically port2 50.45 ohm will gives more accurate S11 S21 displayed results , but if DUT does not run smoothly on physically 50 Ohm load , computing compensation will loos sens , so its rather to have the two Z port option one for port1 and second for port2 .
73s Nizar.


Re: NanoVNA port renormalization

 

For those interested there was a long (over 300 posts) discussion of how to measure ceramic filters in another group about 5 years ago.



David Platt started it off and I have attached his 50 to 330ohm circuit that he used to measure a Murata 10.7 MHz. filter. In this case you do not need the PortZ function.

I have also attached a graphic showing how Murata suggests using series resistors to get the correct input and output impedance for measurement. The PortZ function will be useful in this case.

Roger


Re: NanoVNA port renormalization

 

On Sun, Feb 9, 2025 at 11:56 PM, John Gord wrote:


Each is shown at 50 ohms and again at a higher Z that gives a better match
Maybe I am interpreting this incorrectly. Your comparison shows with PortZ = 50 and PortZ = 430. The Smith Chart marker shows almost the same input impedance in both cases so it appears you did not use an L pad, resistor or transformer to get 430 ohms on input and output of filter. Is my assumption correct?

Roger


Re: NanoVNA port renormalization

 

Rather than prioritizing new feature development for the NanoVNA, I would prefer to see some integrity/troubleshooting functions build in. Things like checking for internal shorts, component values out of whack, etc. Sort of a ¡°self-test¡± series of checks, to the degree that is possible.


Re: After firmware update my nano-vna-h is behaving bizarrely.

 

Yep...Just went through this myself. Mine was an MS version and dislord 1.2.40 defaults to SI.

Bryan, n0luf


Re: NanoVNA port renormalization

 

Second try on screenshots:


Re: NanoVNA port renormalization

 

Roger,
Here are screenshots of tests with a ceramic filter and a crystal filter at 10.7 MHz (different spans).
Each is shown at 50 ohms and again at a higher Z that gives a better match.
Also shown is the test fixture and the filters I tested. There is no matching added to the fixture, just direct connections with coax leads about 3cm long. The small headers on the test fixture are the 50 ohm and short used in calibration. Not shown in the photo is the thru jumper.
--John

On Sun, Feb 9, 2025 at 02:40 PM, Roger Need wrote:


On Sun, Feb 9, 2025 at 02:04 PM, John Gord wrote:


A crystal (or ceramic) filter response is correctly transformed by the
renormalization; I have used this feature several times.
Interesting... What was the design impedance of the filter?

I am surprised at your results because the loading greatly affects the crystal
filter characteristics. The usual way is to use a series resistance, L pad or
transformer on input and output if the crystal filter is designed for a higher
impedance and then recalculate the response from the measured results
factoring this in. Doing this is not the same as directly connecting a 50
ohms VNA and then doing a S parameter transformation (Port Z function) like
the one in the NanoVNA. I am interested in your results so please explain
the test setup and your results.

Roger


Re: Smith Chart acting up in calibration

 

As a followup on this, I see the chip specific files from Huygen, but not Dislord . . . . fwiw . . .

- Tim

On February 9, 2025 8:41:26 PM EST, Tim Dawson <tadawson@...> wrote:
At one time there were specific binaries which set that flag (but otherwise identical) Not sure if they still exist or not, since it's so easy to set.

- Tim

On February 9, 2025 8:26:04 PM EST, "Bryan Curl via groups.io" <bc3910@...> wrote:
Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: NanoVNA port renormalization

 

Hi
This is my point of view : Z--> option does not change the physically pot2 impedance , it remaine always at 50 Ohm +/- 1 ohm value, just firmware by computing way can display S11 or S21 as its at 75 ohm or 300 ohm , for example seting it at the accurate physically port2 50.45 ohm will gives more accurate S11 S21 displayed results , but if DUT does not run smoothly on physically 50 Ohm load , computing compensation will loos sens , so its rather to have the two Z port option one for port1 and second for port2 .
73s Nizar.


Re: After firmware update my nano-vna-h is behaving bizarrely.

 

If your nanovna-H is an MS version (rather than older SI version - see label on back for hardware revision number) - then you need to go into 'expert settings' and change the 'mode' to 'MS5351', then do 'save config'.
See if that is the problem.
Stan KC7XE


After firmware update my nano-vna-h is behaving bizarrely.

 

After calibrating after upgrading to new firmware NanoVNA-H.v1.2.40.dfu from dsilord, the nano vna is showing what seems to be crazy flickering SWR values even after recalibrating and trying to find any setup that needs to be repeated.

Is this a known thing? Is it indicative that my device, labelled Nano-VNA-H and running a slightly earlier DSILord 1.2.x (1.2.30 I think) should go back to 1.2.30?

Warren VA7 WPX


Re: Smith Chart acting up in calibration

 

At one time there were specific binaries which set that flag (but otherwise identical) Not sure if they still exist or not, since it's so easy to set.

- Tim

On February 9, 2025 8:26:04 PM EST, "Bryan Curl via groups.io" <bc3910@...> wrote:
Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: Smith Chart acting up in calibration

 

Absolutely....thanks Tim. Somehow I missed your post.

One thing Ill have to remember now is that a reset will revert it back to SI...even if I save the config.

Fred, Yes, the sma connectors are weak sauce. They are always my first suspect. My next one may have N type...but adapters may cost more than the nanovna. hi hi.


Re: Nanovna-h and Windows 11

 

On Sun, Feb 9, 2025 at 11:18 AM, Stan Dye wrote:


Please see the detailed steps I provided for getting the correct driver
installed in the .pdf file at the following link. This is in the files section
of this group. Let me know if it doesn't clearly explain the solution, and
I'll update it:
/g/nanovna-users/files/Miscellaneous/DFU-mode%20Driver%20for%20Win10Win11

Stan KC7XE
I have been using the STM32 Cube Programmer (latest is now 2.19).

Thanks so much for the docs and driver so I can now switch back and forth. I'm so used to the STM32 way but it's nice to be able to use the NanoVNA-App as well.