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
NanoVNA-MATLAB
#consolecommands
#test-jig
#matlab
#tdr
#tdr-step-response
I released MATLAB scripts, they allows to connect and read S11 and S21 data directly from NanoVNA.
You can get S11 and S21 for any freq range, save it to S2P file, make different plots, include S11, S21, phase, impedance, Smith chart and TDR. And all this can be done from MATLAB with no needs for external applications. :) In addition I added TDR Step Response plot. This is a new and very cool feature which is not available in other software. So it will be the first one :) Enjoy! Best regards! |
Re: Question on
#consolecommands
Oristo,
On my set-up you are 1 for 2: 1. Did not hang during serial read and script completed without errors in the console. 2. Display colors still don't match see attachment), but there is no edge bleeding and all relevant info is displayed correctly. Regards, Herb |
Re: Question on
#consolecommands
Oristo wrote,
"Guess what? I had been using only 2 traces. When I add the other 2, THOSE PNG TRACE COLORS DO NOT MATCH THE DISPLAY Magenta traces on nanoVNA display is green in PNG" ----------------------------------------------------------------------------------------------------------------------------------------- My battery icon is also red orange (see attachment). I also believe the NanoVNA's color mapping is not intuitive and it is a credit to programmers like QRP that they have been able to produce any workable solution at all (Maybe C# makes it easier). It seems any kind of major display change (2 to 4 trace, On screen keyboard, Version screen) throws things out of kilter and makes you re-think things. Timing on the serial transfers also requires different ways of looking at things such as your serial read routine for ensuring you actually have received a full screen. I've learned more about Python by following your scripting and trying to tweak things for my display than reading my books on the language. - Regards, Herb |
Re: NanoVNA Battery
What a great idea!
El dom., 27 oct. 2019 a las 11:06, gusagar54 via Groups.Io (<gusagar= [email protected]>) ±ð²õ³¦°ù¾±²ú¾±¨®: Thanks Chris, I?ll try to install the biggest possible one that fits well. |
Re: Question on
#consolecommands
Thanks, QRP -
For some unknown reason pixel bytes are reversed on firmware side,I FINALLY understand. RRRRRGGGGGGBBBBB gets to LCD as GGGBBBBBRRRRRGGG so what was intended red is GGGBB what was intended green is BBBRRR and intended blue becomes RRGGG So, to match LCD colors, host must also swap bytes, sigh. Herb - THIS version may match your display and not hang: |
Re: Question on
#consolecommands
1. Attachment flut_1a.png is the capture file, Wrong screen colors but no 'color fringing artifact' is visible when zoomed in.What color is your battery icon? Two text lines for CHO and CH1 at the top of your PNG match my PNG... I'm starting to believe that until I am able to upgrade to the same firmwareGuess what? I had been using only 2 traces. When I add the other 2, THOSE PNG TRACE COLORS DO NOT MATCH THE DISPLAY Magenta traces on nanoVNA display is green in PNG, which is opposite color.. Perhaps nanoVNA display has some unintuitive color matching; LCD colors are fundamentally subtractive while RGB is additive. There are only 6 unique combinations for converting RGB565 to RGB888, and the one you have comes closest on my nanoVNA. The battery icon on my nanoVNA is red-orange; what color is yours? |
Re: Owen Duffy on improvised test fixtures
#test-jig
This is a primary reason I made my VNA design with both open source
toggle quoted message
Show quoted text
hardware and software, even permitting commercial use and sales. If someone would like to continue the work or fork it, the more power to them. This is one of the big concerns I have about the NanoVNA, is that while the software is open, the hardware is not explicitly so, and there are multiple vendors with PCBs that can't be reproduced. So who knows if the current design will be reproducible if the current manufacturers stop selling it? On Sun, Oct 27, 2019 at 5:37 PM Jacon Zar <jaconzar@...> wrote:
On Sat, Oct 26, 2019 at 09:59 PM, Pierre Martel wrote:Definitely! |
Re: MATLAB Connection
#consolecommands
On Sun, Oct 27, 2019 at 03:35 AM, Nicholas Giannini wrote:
You can try NanoVNA-MATLAB project :) |
Re: Thank you
Ok. Well I got out of high school in 1963, so you must have a few years on me. I didn¡¯t think there were many Beltz¡¯s around.
toggle quoted message
Show quoted text
Yes, the nano is definitely a very neat tool. The more I explore, the more I find. This is a great group. I presently live in Arizona. Bob N7GW On Oct 27, 2019, at 4:05 PM, Bob Albert via Groups.Io <bob91343@...> wrote: |
Re: Performance of 1:1 Balun
W5DXP
Nan wrote: I am following G3TXQ method of measuring common mode impedance.Measuring the s21 of a choke is akin to measuring the s21 of a coil and to do that the coil needs to be terminated in its characteristic impedance. Steve and I had numerous email exchanges on that subject. If a coil or choke is not terminated in its characteristic impedance on Port2 of a VNA, one is measuring group delay, not signal delay. The VNA assumes a characteristic impedance of 50 ohms and Steve's following experiment proved that trying to measure s21 delay in a piece of 300 ohm twinlead produced "wildly varying s21 delays". "Cecil, I just tried that simple experiment with 9.6ft of 300 Ohm ribbon I happened to have lying around. Simply connecting it directly between Port A and Port B of the analyser produced wildly varying S21 delays with a minimum of 3.4nSec at 13.5MHz I then roughly terminated the ribbon by inserting a 270 Ohm resistor between one leg and Port B, making 320 Ohms total. The reported S21 delay then varied only a little with frequency, typically being between 10nSec and 11 nSec. 73, Steve G3TXQ" "I was inserting extra resistors Rt between the coil and Point B to change the coil termination. The one thing you can't get away from is that adding Rt makes a massive difference to the reported S21 delay even though it obviously can't add substantial physical delay." Note: Rt is the extra resistance that Steve was putting in series at Port2 to try to approximate the characteristic impedance of the coil or choke. Here's what Steve measured for your described 1:1 choke: |
Re: Thank you
Bob Albert
Interesting.? Bob Beltz was my boss in power supply engineering at ITT Industrial Products Division, Sylmar California back in the 1960s.
toggle quoted message
Show quoted text
Yeah the nanoVNA is a major breakthrough, and whoever came up with it deserves a prize.? It obsoletes giant units that cost many thousands, of which I have a couple. Bob K6DDX On Sunday, October 27, 2019, 02:32:52 PM PDT, Robert Beltz <bobbr30107@...> wrote:
Not me.? I worked at Westinghouse and Eaton Corps. In Michigan and Atlanta. Power systems engineering.? Joyfully retired now and enjoying this new toy, the nanovna. On Oct 27, 2019, at 2:15 PM, Bob Albert via Groups.Io <bob91343@...> wrote: |
Re: Performance of 1:1 Balun
Hi Rune
If you go to G3TXQ's website: and click on the hyperlink "spreadsheet" which is almost at the bottom of the page , you will get a XL file which calculates "Z" from S11 & S21 data. Take note that the file was originally created in Open Document Format and needs to be converted to XL. I got some warning messages of possible format loss during conversion to XL 2016 so frankly I am not sure if my conversion process is correct & the formula's got corrupted. I also note that calculation of Z is based on S21 data only, and the formulas are as follows: (copied from the XL sheet and I am trying to understand this!) R =100*10^(-S21mag/20)*COS(S21phase/57.29578)-100 X = -(R+100)*TAN(S21phase/57.29578) Z = SQRT(R^2+X^2) S21mag(dB) in NanoVNA Saver = |S21| - is this correct? OR is it Logarithmic Magnitude (Log Mag /dB Mag) S21phase(deg) in NanoVNA Saver = S21 phase - this should be correct Excellent software, its just me trying to learn to use it correctly! Any help is much appreciated. BR-Nan |
Re: Screen resolution on NANOVNA saver 0.1.4
Hi Rune, Alan and W5DXP are right and I learned it too after some work.
In the ¡°Display Settings¡± window, under ¡°Markers¡±, I clicked ¡® Remove¡¯ and screen size reduced to the same as the earlier versions were......Problem solved. Thanks all for replying, I only have a summary of replies each morning so only just saw your posts. This simple inexpensive device coupled with Your excellent software Rune make this a major piece of test gear for any amateur station. First Class Thank you. Wayne VK6EH |
Re: Question on
#consolecommands
Oristo,
I must have gotten out of sync with your current script. With the : "Updated Python script applies reverse gamma to compensate PNG and nanoVNA display difference, making grids more visible.." I am back to wrong screen colors again but the script runs to completion with no errors. 1. Attachment flut_1a.png is the capture file, Wrong screen colors but no 'color fringing artifact' is visible when zoomed in. 2. Attachment flut_1b.png is the capture file with prune = 8 or 10. Screen colors are different but still wrong. Visible 'color fringing artifacts' when zoomed in. 3. Attachment flut_1c.png is the capture file with ">76800H". Screen colors are different but still wrong. No visible 'color fringing artifacts' when zoomed in. I'm starting to believe that until I am able to upgrade to the same firmware version as you that correlation between your results and mine may not be possible. Regards, - Herb |
Re: Is it possible to do a display driver swap?
Ken,
Thank you for information. The touch signals are going to be a problem for me, unless it is possible to tap in to the raw signals. The display itself might work. Both ili9341 and ili9486 support multiple interfaces, so if it has more wires it doesn't necessarily mean that it only supports parallel. I could look for another display... |
Re: Owen Duffy on improvised test fixtures
#test-jig
On Sat, Oct 26, 2019 at 09:59 PM, Pierre Martel wrote:
Definitely! We had this problem on EEVBlog in FY6x00 AWG's thread, where our great contributor, Fremen67 from France, put tremendous effort to prepare our own DIY firmware for these gens, than mysteriously disappeared for over a year, without any previous signs of problems, and some weeks ago he miraculously reappeared. Should I emphasize, that he make his work in old, closed style, so any progress during his absence was/is absolutely impossible. We may only test results of his work, but don't contribute in any serious way... |
Re: Question: Is it possible to use calibration imperfections to detect the quality of calibration standards???
#calibration
Dr. David Kirkby from Kirkby Microwave Ltd
On Sun, 27 Oct 2019 at 19:15, <erik@...> wrote:
Well, the delays did not work as expected.Why should phase of S11 open and S11 short be 180 degrees apart? Are just leaving open a bit of coax, then adding a short to it? If so, the phase difference will not be 180 degrees due to the fringing capacitance of the cable. That phase difference will increase with frequency. That's well all well-engineered calibration kits have the offset delay on the short a bit longer than on the open. Dave |
Re: Thank you
Not me. I worked at Westinghouse and Eaton Corps. In Michigan and Atlanta. Power systems engineering. Joyfully retired now and enjoying this new toy, the nanovna.
toggle quoted message
Show quoted text
On Oct 27, 2019, at 2:15 PM, Bob Albert via Groups.Io <bob91343@...> wrote: |
Re: Question: Is it possible to use calibration imperfections to detect the quality of calibration standards???
#calibration
In an older post,(I now fail to find), Kurt explained it is possible to use,You may have read my interpretation (#3515) of page 3 in: ... which now states: "Providing your short and open calibration standards are well defined (like the Rosenberger kit from SDR-KITS) incl. the precise value of the load resistance (which is measured by SDR down to 0.01ohm accuracy) there is only one source for fine tuning and that is the fringe C of the load which varies from one example to another." .. and Kurt suggests tweaking that to minimize oscillations in "a S11 dB trace with e.g. 0.2dB per division (the first red trace) which is oscillating across the frequency range" I sort of confirmed that for myself, using 2m LMR-400.. |
to navigate to use esc to dismiss