-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Measuring µ' and µ'' with nanovna-Saver #206
Comments
Can you attach the excel-sheet or the formulas to this issue? |
Hello Zarath, |
Many thanks! |
Hello Holger, |
one more comment: |
Hello Herman, I tried using nanovna-saver sweeping 50KHz to 200MHz with segments =1 for 101 points. My resulting steps are linear at 2MHz per step but I see that yours are (probably) logarithmic which is much more ideal. Could you please explain how you did this as I can not see any setting for a logarithmic sweep. I have not made a chamber and am just operating with a single turn of wire in an attempt for a quick and dirty reading whose accuracy does not need to be very good simply enough to approximately identify the material type. Perhaps you can warn me if this will not be good enough for this purpose and I will need to make a chamber even with the four mounting posts only. 73, Graeme ZL2APV |
Hi Graeme, For Holger: I hope this answer helps you Graem. |
Logarithmic segment scanning would be a possible option. So when 3 segments from 1M-100G first scan points would be from 1M to 10M, second from 10M to 100M and third from 100M to 1G. Logarithmic sweeping is imho not impemented in any current firmware. Perhaps scan point reduction can spread more evenly without increasing scan time too much. |
Hi holger, |
What I have done is swept from 50KHz to 200MHz with 20 seg and saved the .s1p followed by sweep at 2 segments again saving and finally at 1 segment. I took the values from 50KHz to 999KHz from the 20 seg file added to them the 1MHz to 9.9 MHz from the 2 seg file and finally 10MHz up from the 1 seg file. I had to drop off the last 13 readings for 101 points so only went to 174 MHz but at least the pseudo log file worked and only took a couple of minutes to create. I just need to sweep a bit higher if I want to go up to 200MHz. |
Hi Graeme, For the nerds reading this: I do not recommend this as the accuracy obtained in this way does not make sense in relation to the accuracy of the manufacturers specs of the toroid. |
Hi Holger, |
@Herman-RFguy tnx for the update. I still plan to impelent that functionality, but time... |
Great to read that Holger! We can't buy time, its precious, so if you find some i am looking forward to be your beta tester. with kind regards, |
It's build after that original dimensions in the presentation. I haven't measured the exact induction yet. Reducing the hight wouldn't be easy afterwords as I brazed the stoods. (46nH by the way) |
never mind Holger, it will work anyway. |
Hi Herman,
Many thanks for the English translation and it is a big help. Still
getting excellent results from my lashed up test facility and it has not
encouraged me to make a better version although the one Holger has built
looks similar to what I had in mind but I will probably see how 35mm
spacers will work as I have a set I made a couple of years ago. I keep a
selection of N and BNC parts so will have no problem in building a
mating connector. I will use knurled nuts on the top of the pillars
which have 3mm threads projecting.
73, Graeme
…On 20/08/20 9:09 pm, Herman-RFguy wrote:
Hi Holger,
I translated my presentation into english and edited the formula work
in Word, making it much more readable compared to my handwriting -:)
I attach it hereby.
do you plan to implement this nice feature when you fint the time for it?
With kind regards,
Herman.
µ meting met nanoVNA-V4-E.pptx
<https://github.com/NanoVNA-Saver/nanovna-saver/files/5101923/meting.met.nanoVNA-V4-E.pptx>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#206 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGSFBVI7GU5BUHIODJAYH3SBTR4ZANCNFSM4OMDN4QQ>.
|
Hi Greame, 73, |
Thanks for your contribution Igor-M. Concerning the math: I gave the derivation just to explain the background of the calculation. |
Thanks Igor-M for your interesting work. It is always good to see another approach. I will be staying with what I have as it works so well for me and is repeatable but I accept that I did need to make the chamber which was not too difficult and only took around an hour to make. I do have to solder and unsolder the centre wire to put the toroid on and off but it is something that I don't do very often so its not really a problem. I massage the .s1p file so that I can directly import it into Libre Office spreadsheet and the graph is directly displayed using a near copy of Herman's sheet. 73, Graeme ZL2APV |
@ Herman and Graeme and Holger - your hardware is definitely better than my 2 turns of wire, sure!! PS: I would put a few mm thick quality isolator (like teflon or something like that) on the bottom of the chamber such the toroid does not sit on the copper directly.. |
Here is the link to the paper PS: this is a T50-6 (yellow Amidon powder toroid) measured with my 2 turns.. |
@ Herman - out of curiosity I've put my above s1p (T50-6 with 2 turns, 1-30MHz, 801 points) data into your excel table. I've added the "Turns Number" to the calculation (.. nn in the L column). |
Hello Igor, With kind regards, |
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. |
Hi Zarath, it still has your interest? |
This sounds like a great addition indeed. We already have a chart that can plot Z in real and imaginary parts (Charts/RI.py). Maybe adding a derived variant of that with some additions to the drop-down menu to set core dimensions, number of windings, and adjusting the calculation in getImYPosition() and getReYPosition() could be a quick fix? Looks doable to me but I'm afraid that I don't have time to make it happen soon. Cheers, |
Another thing though, considering the measurement itself: VNA accuracy is best when
Measuring a large inductor (or a small one at high frequencies) gets you quite a bit away from the 50 ohm. Might be worth an experiment to make a new box with a connector on both ends of this central rod and using a S21 measurement. This puts the inductor in series with the measurement path and will cause a large attenuation for a large impedance, making the measurement much more accurate. NanoVNA-Saver already implements the calculation into Z-series so that may give you a nice start on the calculations. Cheers again, |
Ok, this got stuck in my head so I gave it a go (code available on my fork). I've added a graph based on the existing real-imaginary graph. The settings for the core parameters are in the graph menu (right click on the graph and you'll find them). I don't have a nice test fixture but I did a quick test on some unknown quality small ferrite torroids I had laying around 8mm OD, 4mm ID, 3mm height. Example setup (small core around a wire soldered to an SMA connector. Sweep 10M-1G in 3 segments. RI plots already supported a log frequency scale. Looks like it works, I'm not really happy though with how the core properties are set. Might be nice to have a single, more flexible dialog window where you can specify the dimensions in different styles depending on your core type and setup. Maybe even with a list to select from some standard core dimensions. Anyway, I don't have the nice test setup or good reference cores here so it would be great if someone can test this code already. Cheers, |
Hi Roel, |
oops, i thought i would find a Windows executable as I am used to, but it is a Pyton source code. |
Hi Herman, Ah, that's to bad. I'm not sure how that works. I've only got a Linux machine here... I see though that @zarath has added a script to have Github run the build process for releases. I've kicked that off so hopefully there will appear some usable version for you on my fork. Well, it seems to have done something at least. At the bottom of the page linked below there are some outputs. https://github.com/rjordans/nanovna-saver/actions/runs/4151729912 Cheers, |
Thanks a lot so far Roel. w. regards, |
Hi Roel, |
Great to hear Herman! Good to know that this produces usable results. I've added a brief description on how to use this feature in the toplevel README.md document (also visible on the main Github page). Hopefully that's enough for people to understand the basic usage. 73 de PA3RJ, Roel |
I think so Roel. |
Hi Roel, |
Hi Herman, Is this bug something that this new code triggers or is it something else? I see that there is another issue #589 that there is a problem in general with the continuous sweep not stopping. You might be running into that? Cheers, |
@Herman-RFguy this build https://github.com/rjordans/nanovna-saver/actions/runs/4157198674 should fix your freezing problem hopefully |
Thanks a lot Roel! |
I did not notice your previous question. |
Hi Roel, |
Hi Herman, That's strange. I didn't touch any parts related to the mu calculation for fixing the freezing bug and can see no change in the behavior here either. Cheers, |
Hi Roel, what is desirable now? with kind regards, |
Hi, where one may download the version with u' and u'' for testing? I can see rjordans' build above, but it cannot be downloaded.. |
Hi Igor, |
Hello Roel, The autoscaling of u' and u'' Can you also plot in the same display the quotient u''/u' as this represents the loss tangent of the core material and gives very useful information on selecting the frequency where to use the core material for what purpose. Thanks again for your contribution for this topic. |
Hi Herman, I haven't had much time to look into this but maybe something to note on your point 2: we already have a S11 Q plot that should basically show u'/u''. Maybe that's enough for you to work with already? Implementing the common scaling for u' and u'' looks like it will be a bit more involved than what I was hoping for. I like the idea but it will take some time before I'll be able to look into that. Cheers, |
Hi Roel, I saw your qrl activities, very interesting. |
Dear members,
This is the first time i contribute an idea to this community.
I developed a measurement method to determine the complex µ ( µ' and µ'' ) of a toroid using the nano vna.
after a calibration sequence the S11 is saved in a .s1p file and than the physical dimensions of the measured toroid are added to the excel sheet i made.
I plot the numerical results from the excel sheet with the use of a plot program i found on the WWW.( see pic.)
The measurement chamber can be easily constructed with double clad PCB, or some copper plate, the round wall is not obligatory as tests learned, using 4 spacers yields identical results. More mechanical details can be given in a separate document.
For saver:
The physical dimensions of the toroid have to be input, the s11 data is obtained directly from the vna.
After ending the calculations the µ' and µ'' are known and can be graphically shown in the plot window of saver.
The frequency axis is preferred logarithmic and the Y axis as well, auto ranging as µ can be 10 for a powder iron core
and >1000 for other types.
I have done all the math and i am happy to share this with the community to add a very nice function.
The AL value can be derived easily and it is used very often for calculating the number of turns for a self inductance.
A plotted result for a T94-2 toroid is added to show what can be expected.
µ'' tells a lot of the losses and thus enables choices to be made for the intended use and frequency.
I wait for any help how i have to to share this math info .
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: