¿ªÔÆÌåÓý

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

Re: Proper way to measure length of _Window_Line_?

 

I'm wondering if the correct way to measure the length of window line
with a NanoVNA is fundamentally different than that of measuring coax.

I'm following the method described by Arie
(/g/nanovna-users/message/26832). I have 5.175m of "JSC
1320 300 Ohm Ladder Line 300 Ohm 20 AWG / 7 Strands Bare Copper". That's
a quarter wavelength of 20.7m, or a frequency of 14.5MHz.


First things first, a FULL ELECTRICAL wavelength at 14.5MHz is 300/14.5 ~= 20.7m. A quarter wave ELECTRICAL length is 5.172m.
To find the PHYSICAL length for a quarter wave stub at 14.5MHz, MULTIPLY the ELECTRICAL length by the cable VF.
The Spec Sheet for 1320 TV Ladderline is 0.82. Therefore the PHYSICAL length required is 5.172*0.82 = 4.241m.

If you now want to prove this, you can use the NanoVNA, BUT it is best if you use a broadband matching transformer and measure the 300 Ohm ladderline in balanced mode.
If you try measuring the ladderline directly on the 50 Ohm unbalanced S11 input of the NanaVNA, you will get unreliable results as you have already discovered. Possible reasons are mentioned in other posts in this thread.

To match 50 Ohm to 300 Ohm, the impedance ratio is 300/50 = 6. The turns ratio for the transformer is the square root of the impedence ratio, sqrt(6) = 2.45.
So let us use 8 turns on the 50 Ohm Primary and (8*2.45) = 19.5 turns on the 300 Ohm Secondary.
The half turn is convenient as we end up with the primary at one end and the secondary at the other end of the ferrite core.

To make the matching transformer, use a binocular "balun" ferrite core. I have used a 14mm (9/16") long, 13.2mm wide ferrite with two 3.8mm (5/32") holes.
It is best if the primary and secondary windings are bifilar wound.
It is even better if the smaller 8 turn primary is wound in the centre of the 19.5 turn secondary.

As the power levels used here are quite low, the thickness of the wire is not critical. The main thing is that you can fit 28 "turns" of wire down each hole.
You will need about 1200-1500mm (4-5ft) of fine enamelled copper wire for a 14mm (9/16") binocular balun core.
Take your wire, fold it over, mark one leg at each end so you can identify it later and twist the legs together lightly. About 1 twist per cm, 2 twists per inch is fine.

It is difficult to describe what to do next, but what we want is to start with 5.5 turns of the secondary wire only, then 8 turns of the double bifilar wire, and finally 5.5 turns of the secondary wire only to finish up.
Unwind about 250-300mm (10"-12") of the unmarked leg so you can pass 5 full turns of the marked leg only through both holes of the ferrite and then pass it through the hole you started at to give 5.5 turns.
Now twist the unmarked leg around the marked leg to start your bifilar combined winding.
Make 8 complete turns with the twin bifilar wire and finish at the same end you started the 8 bifilar turns.
Separate the two legs and wind the marked leg ONLY through the ferrite another 5.5 times. You should finish at the same end you started with the single wire.

The "single" wire end is your 300 Ohm secondary, the bifilar 8 turn end is your 50 Ohm primary.

Mount the finished transformer on a piece of pcb or perf board. Attach a female SMA connector to the 8 turn winding and some terminals at the 300 Ohm end to attach your ladderline.
I am not being too prescriptive here. Use your imagination and your ingenuity to make a neat, relatively robust piece of test adaptor for you VNA test kit.

FINALLY, connect your SMA test lead to the transformer SMA connector and terminate the 300 Ohm terminals with a NON-INDUCTIVE 300 Ohm SMT or metal film resistor/s.
Now do a Short/Open/Load Calibration over the frequency range of interest and save to one of your Calibration memories.

You can now run your test on your ladderline. It should be relatively accurate as the Calibration Plane is at the 300 Ohm Terminals of the Transformer.

I used a similar transformer design when I was a design engineer working on early VDSL Broadband Network deployment. This used multiple carriers from 2MHz-35MHz on 100 Ohm Cat 5 cable.
I used a 10 turn primary and 14 turn secondary for the 50/100 transformer. The system was very sensitive to cable balance and the transformer worked well.

73...Bob VK2ZRE


Re: Best Firmware Update for NanoVNA V2? #nanovna

 

Charlie, I sent you details by email.

----- Original Message -----
From: "W5CDT" <charlie.texas@...>
To: [email protected]
Sent: Wednesday, February 16, 2022 5:34:34 PM
Subject: Re: [nanovna-users] Best Firmware Update for NanoVNA V2? #nanovna
That would be great. Much appreciated Danny.



Re: S21 port not working

 

On Sun, Feb 13, 2022 at 03:37 PM, Alan Brown wrote:


Trying to use log mag and not working now.
I think I overload S21 with more then 10db.
What is the fix anyone now?
I¡¯m hoping some simple right at the port
The front end of CH1 just contains some resistors and SA612 mixer. Try looking there for damage first....

Shown here >>>

Full schematic here >>

Roger


Re: Best Firmware Update for NanoVNA V2? #nanovna

 

That would be great. Much appreciated Danny.


Re: Best Firmware Update for NanoVNA V2? #nanovna

 

I also recently purchased the AURSINC SAA-2N v2.2 which I believe to be the same internally.

I loaded DiSLord's "V2 480x320 v1.1.00.bin" and had some difficulty getting the screen re-inverted but got it figured out in a few minutes.

I can't find the forum post where I downloaded it now but if you want that I can give you a link to my copy of it.

Danny

----- Original Message -----
From: "W5CDT" <charlie.texas@...>
To: [email protected]
Sent: Wednesday, February 16, 2022 12:05:12 PM
Subject: [nanovna-users] Best Firmware Update for NanoVNA V2? #nanovna
I recently purchased a NanoVNA V2 because it has the extended frequency range to
3GHz.
The firmware version is well over a year old (see attached photo) and was
wondering if there are any recommended firmware upgrade versions for the
NanoVNA V2.

Any suggestions on how to upgrade the firmware are greatly appreciated.

-Charlie



Best Firmware Update for NanoVNA V2? #nanovna

 

I recently purchased a NanoVNA V2 because it has the extended frequency range to 3GHz.
The firmware version is well over a year old (see attached photo) and was wondering if there are any recommended firmware upgrade versions for the NanoVNA V2.

Any suggestions on how to upgrade the firmware are greatly appreciated.

-Charlie


Re: S21 port not working

 

On 2/16/22 6:16 AM, Alan Brown via groups.io wrote:
I¡¯m no wiser after these posts.
S21 does not work as not able to calibrate it.
It has gone bad. Overload.
Is there a fix? I¡¯m measuring gain of a LNA as I have done many times and now the port is bad.
I don¡¯t remember breaking it but I probably did as just takes a few seconds not thinking.
I was about to order a new H4 and this one will work for things I don¡¯t need S21 port for.
What is it I¡¯d have to change is the VNA, resistor chip etc??
This is a H4? Original NanoVNA RF design, just with a bigger screen? The first thing after the CH1 input is a resistive pad (I can't remember how many dB, but something like 17-20 dB). I would have thought that's pretty robust against a momentary overload. How much did your LNA put into it? The next thing in the chain is the mixer, but that should be able to handle 0dBm without damage and probably more - it's a bipolar Gilbert cell, and the inputs drive the bases of an NPN transistor.? This isn't some delicate CMOS or MOSFET. So, did you put more than ~100mW in?? Or worse yet, hook it up to the supply voltage without a DC block (e.g. if your LNA expects a bias T or something like that) - 12V across the 56 ohm input resistor is ~200mA or 2.5W - That teeny, tiny SMT resistor won't handle that.? After that goes open, the 12V is then across the 240 ohm series resistors and ultimately the SA612 input

You could probably measure the resistors in the pad to see if one or more is cooked.

OTOH, if it's a NanoVNA2, I believe they have an RF switch as the first thing after the connector, and those are fairly sensitive to overload.


Re: S21 port not working

 

I¡¯m no wiser after these posts.
S21 does not work as not able to calibrate it.
It has gone bad. Overload.
Is there a fix? I¡¯m measuring gain of a LNA as I have done many times and now the port is bad.
I don¡¯t remember breaking it but I probably did as just takes a few seconds not thinking.
I was about to order a new H4 and this one will work for things I don¡¯t need S21 port for.
What is it I¡¯d have to change is the VNA, resistor chip etc??


Re: Proper way to measure length of _Window_Line_?

 

Has anyone wound a high common mode impedance 1:1 balun with 50 ohm coax and calibrate at the output end of the balun?

I made a balun years ago for use with GR Z bridges (GR 1606 and 916) for this purpose with good results.

I didn't wind the coax on a ferrite toroid at the time. I wound the coax on a length of PVC pipe and with a variable cap across the coax (shield to shield) I tuned it to resonance for the frequency of the test. The common mode Z is very high and higher than a ferrite-cored balun.

Obviously this would not work for a swept frequency test but should work with a broadband ferrite-cored balun.


Re: Proper way to measure cable length

 

What I wanted to say here is:

A quarterwavelength at 500 kHz = 150m electrical.
A 1/4 wave physical cable with VF=0.78 would then be 150 x 0.78 = 117m long or with a VF of 0,66:? 150 x 0.66 = 99m
So sweeping from 500 kHz up will be sufficient for coax upto 100m long or so.
For longer cables one has to start with a lower frequency.

Arie


Op 12-2-2022 om 01:47 schreef Bob Ecclestone:

(** A quarter wavelength at 500 kHz is 600m / 4 = 150m and taking into
account the VF, the electrical length will be 150/0,78 = nearly 200m,
should be enough:-) ? )


Re: Proper way to measure length of _Window_Line_?

 

I've measured windowline many times using the NANO - something I can not
easily accomplish with the HP 8753C. Be sure the NANO is not connected to
any conducting cabling, chargers, USB cables, or sitting on or near
anything conducting. At HF frequencies the NANO is small enough to not
influence measurements. However, if it is connected to anything
conducting, it is no longer "small" as a function of frequency /
wavelength.

The attachment indicates you have connected the NANO to a PC. The NANO
effectively becomes much larger at RF frequencies as its connected to: 1)
the USB cable, 2) the PC, and 3) the house wiring, and finally, 4) the
power grid. This will greatly influence correct readings of windowline.
Measurements must be made with the NANO alone.

Dave - W?LEV



On Tue, Feb 15, 2022 at 4:40 PM Kevin Zembower via groups.io <kevin=
[email protected]> wrote:

I'm wondering if the correct way to measure the length of window line
with a NanoVNA is fundamentally different than that of measuring coax.

I'm following the method described by Arie
(/g/nanovna-users/message/26832). I have 5.175m of "JSC
1320 300 Ohm Ladder Line 300 Ohm 20 AWG / 7 Strands Bare Copper". That's
a quarter wavelength of 20.7m, or a frequency of 14.5MHz.

The first step is to sweep it to determine the velocity factor. Yet,
when I sweep from 12-17MHz, I get the Smith chart attached. There's no
point when the impedance is close to zero.

Am I doing something wrong (most probable), or is measuring the length
of window line with an NanoVNA fundamentally different than measuring coax?

Thanks for your advice and suggestions.

-Kevin
KC3KZ





--
*Dave - W?LEV*
*Just Let Darwin Work*


Proper way to measure length of _Window_Line_?

 

I'm wondering if the correct way to measure the length of window line
with a NanoVNA is fundamentally different than that of measuring coax.

I'm following the method described by Arie
(/g/nanovna-users/message/26832). I have 5.175m of "JSC
1320 300 Ohm Ladder Line 300 Ohm 20 AWG / 7 Strands Bare Copper". That's
a quarter wavelength of 20.7m, or a frequency of 14.5MHz.

The first step is to sweep it to determine the velocity factor. Yet,
when I sweep from 12-17MHz, I get the Smith chart attached. There's no
point when the impedance is close to zero.

Am I doing something wrong (most probable), or is measuring the length
of window line with an NanoVNA fundamentally different than measuring coax?

Thanks for your advice and suggestions.

-Kevin
KC3KZ


Re: PC Won't Recognize Unit in DFU Mode so Can't Update Firmware

 

Hi , some time ,is it necessary to force the installation of the STM drivers as wrote on readme.txt , inside the directory of the
en.stsw-stm32102.

/ (C) COPYRIGHT 2018 STMicroelectronics
* File Name : readme.txt
* Author : MCD Application Team
* Version : V1.5.0
* Date : 02/05/2018
* Description : read me file for Virtual COM Port driver

* THE PRESENT SOFTWARE WHICH IS FOR GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS
* WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE TIME.
* AS A RESULT, STMICROELECTRONICS SHALL NOT BE HELD LIABLE FOR ANY DIRECT,
* INDIRECT OR CONSEQUENTIAL DAMAGES WITH RESPECT TO ANY CLAIMS ARISING FROM THE
* CONTENT OF SUCH SOFTWARE AND/OR THE USE MADE BY CUSTOMERS OF THE CODING
* INFORMATION CONTAINED HEREIN IN CONNECTION WITH THEIR PRODUCTS.
****/

Last version

- V1.5.0 - 02/05/2018
Supported OS


+ Windows 98SE, 2000, XP, Vista, Seven, 8.x (x86 & x64 Windows platforms)

Contents
*
+ VCP_V1.5.0_Setup_W7_x86_32bits.exe : Setup file to Copy required files for Win7 x86
+ VCP_V1.5.0_Setup_W7_x64_64bits.exe : Setup file to Copy required files for Win7 x64
+ VCP_V1.5.0_Setup_W8_x86_32bits.exe : Setup file to Copy required files for Win8 x86
+ VCP_V1.5.0_Setup_W8_x64_64bits.exe : Setup file to Copy required files for Win8 x64
+ version.txt : History of versions
+ readme.txt : This file

How to use


1- Uninstall previous versions (Start-> Settings-> Control Panel-> Add or remove programs)

2- Run your "VCP_V1.5.0_Setup_W7_x86_32bits.exe" or "VCP_V1.5.0_Setup_W7_x64_64bits.exe" or "VCP_V1.5.0_Setup_W8_x86_32bits.exe" or "VCP_V1.5.0_Setup_W8_x64_64bits.exe" depending on your machine OS

if you like to force the driver install , any time after the first install :

3- Go to Your installation directory - Example, C:\Program Files (x86)\STMicroelectronics\Software\Virtual comport driver

4- Go to Your OS version directory ([Win7] or [Win8])
+ Then :
- Double click on dpinst_x86.exe if you are running a 32-bits OS version
- Double click on dpinst_amd64.exe if you are running a 64-bits OS version
+ Follow the instructions.



**** (C) COPYRIGHT 2018 STMicroelectronics END OF FILE*
Maurizio


Re: PC Won't Recognize Unit in DFU Mode so Can't Update Firmware

 

This solution solved my issue, which was exactly the same as OP. Thank you sir!!

Tim NC0Q

On Fri, Jan 22, 2021 at 04:55 PM, Michael Brickell VE3TKI wrote:


I have 3 laptops, two running Windows 10, and one running Window 7. I was
able to install the v1.0.39 firmware for my H4 nanoVNA on the Windows 7 laptop
but not the Windows 10 ones. When I ran the DFuse v3.0.6 program I did not
see anything in the Available DFU Devices List. The problem was that the
bootloader driver did not install with the DFuse Demo v3.06 program.

I then downloaded the STM Bootloader Driver package from
, and
installed the amd64.exe driver on the Windows 10 laptops. Having done this I
found that when the nanoVNA is placed in DFU mode and connected via the USB
cable, an ¡°STM Device in DFU Mode¡± appears in the list of USB Controllers
in Device Manager.

When I run the DFuse Demo v3.0.6 program I now see ¡°STM Device in DFU
Mode¡± in the Available DFU Devices List , and the new firmware installs
properly.

Michael Brickell VE3TKI


Re: Need help with SD card problems

 

David,
The SD card routines have been tweaked to work with most TF cards in SPI mode.
Unfortunately, not all cards support that mode of operation.
Most newer cards do support SPI mode.

On Monday, February 14, 2022, 11:45:07 a.m. EST, David Rounds <groups@...> wrote:

I could not find any of my SanDisk 16gb cards that would work.
Switched to a Samsung 32gb and it worked perfectly.


Re: Need help with SD card problems

 

I could not find any of my SanDisk 16gb cards that would work.
Switched to a Samsung 32gb and it worked perfectly.


Re: S21 port not working

 

On 2/13/22 11:27 PM, Maurizio IZ1MDJ wrote:
Hi , in my opinion , calibrate the S11 port , with 20 dB of attenuation applied , make non sense .
Maurizio
Yes, I'd put the 20 dB pad on the UUT output (i.e. the CH1 port, not the CH0 port).? Then you do a calibration (with the pad in place).? Measure your UUT, add 20 dB to the S21 magnitude. You could also measure the pad separately (with a conventional SOT calibration), measure the UUT and pad, then do the arithmetic.


Re: S21 port not working

William Smith
 

I think Jim was saying two things:

1) Calibrate it normally and then measure a known device, like e a 20dB attenuator, and see if you get a sane result.

2) If measuring a (say) 20dB amplifier, put 20dB of attenuation after it, so you don¡¯t overload the input.

73, Willie N1JBJ

On Feb 14, 2022, at 2:27 AM, Maurizio IZ1MDJ <redifon500@...> wrote:

Hi , in my opinion , calibrate the S11 port , with 20 dB of attenuation applied , make non sense .
Maurizio


Re: S21 port not working

 

Hi , in my opinion , calibrate the S11 port , with 20 dB of attenuation applied , make non sense .
Maurizio


Re: S21 port not working

 

On 2/13/22 3:37 PM, Alan Brown via groups.io wrote:
Trying to use log mag and not working now.
I think I overload S21 with more then 10db.
What is the fix anyone now?
I¡¯m hoping some simple right at the port

If you check with a thru and/or a pad, do you get the right values (i.e. did you not damage anything).


You can put 20 dB attenuation at the output of your amplifier under test. Calibrate (Short, open, thru) using the pad.