Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Re: Common ground and 2-port measuring
Miro, the nanovna is designed to measure this way - think of the
calibration you do for a thru S21 measurement; it calibrates the error due to the cable and ground paths. For measuring the choke, there is no need to worry about this issue. Other issues are present which have a much larger effect on the resolution/accuracy of an S21 measurement - it is quite accurate for small values of Z, but gets less and less accurate as Z exceeds several k-ohms. But it is entirely sufficient to get a reasonable measure of the effectiveness of the choke, especially for the values of insertion loss and common-mode S21 attenuation. On Thu, Jul 7, 2022 at 7:23 PM Miro, N9LR via groups.io <m_kisacanin= [email protected]> wrote: Some really good suggestions, but let me highlight "my problem" here :) |
Re: Common ground and 2-port measuring
Some really good suggestions, but let me highlight "my problem" here :)
I'll only focus on measuring S21 in differential mode using 2 port setup! On the port 0 I connect shield and center conductor (as with any coaxial transmission line), on the other port I do the same. Simple connection, nothing fancy. Shield to shield, hot to hot :) Now I have internally bonded ground between shields at Port 0 and Port 1, and i ALSO have shield of the coaxial cable connecting grounds of those two ports!!! THAT DOES NOT SEEM RIGHT! Chances are that DUT (the current balun in this case) will lessen the impact of the internally bonded grounds by acting as the current balun, but what if CMRR is small - parallel ground paths will add some measuring error! I still need to take a look at the S11 concept suggested by WB2UAQ with shorted output and 1 port measurement of S11, but that still does not give me S21 in differential mode! So, how will internal ground bonding affect 2 port setup for measuring S21 in differential mode? |
Re: Common ground and 2-port measuring
I do this a little differently, for simplicity, as discussed in some of the
toggle quoted message
Show quoted text
message threads (search for CMC, and you will find lots of methods/info from discussions several months ago). For insertion loss, with a coaxial coax choke like what you described, what I care about is the loss through the center conductor when the shield is working as a return path - so I just hook it directly to the coax port 0 and 1 connectors of the nano, and display the S21 loss curve in dB. A good choke will have just a small insertion loss, typically less than .1 dB at HF frequencies. For common-mode rejection, what I care about is how much the shield attenuates the signal - so I connect the shield only to the center conductors of the port 0 and 1, and do another S21 loss curve. Then I see 20-40 dB of attenuation in a curve across 1-30MHz for my HF chokes. If I want to see the impedance, I can also change the display to show R+jX and get an estimate of the impedance, hoping for k's of ohms resistive and a small reactive part. The measurement and values are not perfect, but is easy to do. You can see a similar loss curve if you just hook the shield across port 0, and display an S11 loss curve - but displaying the impedance isn't correct in that setup, since it is the impedance of the reflection, not of the choke. On Thu, Jul 7, 2022 at 2:25 PM WB2UAQ <pschuch@...> wrote:
As you said, short the input terminals and the output terminals and |
Re: Common ground and 2-port measuring
As you said, short the input terminals and the output terminals and measure S21 between the terminals with them floating. With the phase and magnitude of S21 the common mode Z can be calculated. There are files in this discussion group that do the calculation. Save the s2p data and insert it into the spreadsheets.
For insertion loss measure S11 (return loss format) looking into the DUT with the output terminals of the DUT shorted. Half the return loss is the loss thru the DUT. |
Re: Common ground and 2-port measuring
[Siegfried said: In both cases a common ground does not hurt so i connect both grounds together]
That's what I was hoping for :) That common/internal ground (bonding) can't affect when measuring against 50ohm load (1 port measurement), but I was concerned how will that affect S21 (through loss). Any "science" beyond empirical finding that internal bonding won't hurt? A gut filling tells me that there much be more to it when I have two ground paths in parallel - one internal and one through DUT. When it comes to "how much power" - that would be great for another release - nanoVNA with legal power output (1k5W) and temperature sensor built in :) + other port that can handle these levels too! And battery to support all that! |
Re: Common ground and 2-port measuring
I measure through loss
toggle quoted message
Show quoted text
And cm surpression In both cases a common ground does not hurt so i connect both grounds together And i measure swr with the balun loaded with its nominal impedance.. 50 ohms.. Or 200 (for a 1 to 4).. Or for whatever it is made Those three tests give you a good idea how well your balun or choke works How much loss it has How good it suppresses cm current And in what frequency range you can use it... Whatelse do you need to know?? Maybe how much power it can handle.. Grin Greetz sigi dg9bfc Am 07.07.2022 22:25 schrieb "Miro, N9LR via groups.io" <m_kisacanin@...>:
|
Common ground and 2-port measuring
Found several articles and several answers/opinions on this topic :)
If I want to do 2 port measurement in a setup where the input and output of the DUT do NOT have common ground (let's say an RF transformer, or a simple current balun), how will internal common ground on nanoVNA ports affect measurements. Let's be even more specific - want to do some simple testing of an HF balun. S21 for differential mode and for the common mode suppression. Just for the sake of the argument, balun will be wound with a short (comparing to lambda) piece of coaxial cable, either wound in air or on ferrite toroid. In the CMR mode I'l short both sides of the balun, connect to "hot" ends of both nanoVNA ports, and "rely" on the grounds being connected internally - is that correct setup? In the differential mode how will that internal common ground affect measurements as it will effectively short the current that is supposed to go through the shield of the coaxial cable making the balun? So, in one case (CMRR measurement) that internal common ground helps. but in the other (differential) it does not. All would be easier if ports on nanoVNA are not bonded internally and I have an option to connect them or not :) |
Re: Traces refresh rate slows down with fw 1.0.69
#nanovna-h4
On Wed, Jul 6, 2022 at 10:26 PM, <t.rohner@...> wrote:
Hello and many thanks for the infomation. Good to hear, there is a solution that fixes the problem. The 1.0.53 is also for my Nano the latest version that worked without the mentioned issue. Recently I updated to 1.2.00, which is much more stable but also with this version I faced the same issue. The problem seems to be hardware dependent. I will look for version 1.2.02 and give it a try. Many thanks and 73 Gerd |
Re: Measuring AL value via NanoVNA
#coils
#transformer
On Wed, Jul 6, 2022 at 10:06 AM, EB4APL wrote:
Which Acrobat version are you using to open this file and othersIt opens fine on one of my old computer using Adobe Reader 11 and also with the latest version of Adobe Reader DC for Windows. Roger |
Re: Traces refresh rate slows down with fw 1.0.69
#nanovna-h4
Hello
I had the same problem you have. For me, with a H4 also, FW originally was 1.0.39. Then i updated and up until 1.0.53 the traces work at "normal" speed. (i tested this, starting from 1.0.69, it was slow like you describe it. 1.0.64 doesn't work at all on my H4, black screen) I tested clear config and restart with 1.2.00, no luck. (i reduced the sweep points to 51 and it took "only" about 20 sek for a sweep, but no useful readout connected to my DemoKit 6.5MHz BSF) Then i saw in the vna beta group, that there is a 1.2.02 version. I installed it and heureka, it sweeps even faster, than 1.0.53. I hope that helps 73 de HB9SFG |
Re: Measuring AL value via NanoVNA
#coils
#transformer
Hi Roger,
toggle quoted message
Show quoted text
Which Acrobat version are you using to open this file and others generated by the deepl translator? I have version 9 Pro Extended and it refuses to open it, saying that an updated version is needed. Checking with the Acrobat update function it says that there is not any update available. Regards, Ignacio El 06/07/2022 a las 18:10, Roger Need via groups.io escribi¨®:
On Wed, Jul 6, 2022 at 06:03 AM, F1AMM wrote:It's a pity that your pages are not in HTML; it would have allowed Chrome toUse the deepl translator. It will translate pdf files and keep them in the same format as the original. --
El software de antivirus Avast ha analizado este correo electr¨®nico en busca de virus. |
Re: Measuring AL value via NanoVNA
#coils
#transformer
I found this online (
toggle quoted message
Show quoted text
): [image: image.png] As with air wound inductors, the inductance for fixed ?r, the inductance varies as the square of the number of turns. The ? in the above equations should be the ?r of the toroid material times ?o (of free space). So the scaling between 33 turns and 21 turns would be [21 / 33]^2 or 0.401. If you measured 36 ?H with 33 turns, you should have 33 ?H x 0.401 = 13.4 ?H with 21 turns. Of course, the 33 turns is with 0.1 mm and the 21 ?H is with 0.2 mm. But with a larger core, I would expect greater inductance than the original 0.1 mm core. Bear in mind that the tolerance in ?r from unit-to-unit may be as much as 20%. This is quite normal even with toroids from the same batch from the manufacturer. Dave - W?LEV On Wed, Jul 6, 2022 at 4:29 AM F1AMM <18471@...> wrote:
Hello-- *Dave - W?LEV* *Just Let Darwin Work* --
Dave - W?LEV |
Re: Measuring AL value via NanoVNA
#coils
#transformer
On Tue, Jul 5, 2022 at 09:29 PM, F1AMM wrote:
Yes the Al will vary with frequency for ferrite toroids. The reason is that the permeability of the ferrite toroid varies with frequency and the Mix (31,43, 75) etc. has a significant effect. Powdered iron Al only varies slightly with frequency. Most of the online ferrite toroid calculators only provide good results at low frequencies. Here is an excellent online calculator for you to try >> Roger |
Re: Measuring AL value via NanoVNA
#coils
#transformer
On Wed, Jul 6, 2022 at 06:03 AM, F1AMM wrote:
Use the deepl translator. It will translate pdf files and keep them in the same format as the original. Attached is a translation to French of one of Arie Kleingeld PA3A English articles Roger Here is |
Re: nanovna-saver/displayed charts/S11 R/¦Ø & X/¦Ø (?? / Hz)
And, speaking of Smith Charts, if you haven't yet discovered SimSmith, give
toggle quoted message
Show quoted text
it a try. It's free. There is also an excellent tutorial linked from that site. Dave - W?LEV On Wed, Jul 6, 2022 at 4:04 AM F1AMM <18471@...> wrote:
Thank you Victor-- *Dave - W?LEV* *Just Let Darwin Work* --
Dave - W?LEV |
Re: Measuring AL value via NanoVNA
#coils
#transformer
F1AMM
I have a lot of bad luck with Adobe. I had a CS3 version with Acrobat 8 pro (+ license) but it refuses to work. With Adobe it's hard problems. It is therefore insoluble for me to translate your .pdf and it is a pity.
The EZNEC notice is provided, among other things, in Word (.doc). It's impeccable: I converted it into HTML and Google translated it for me into almost perfect French. At least with Google it works. |
to navigate to use esc to dismiss