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: NanoVNA-H v0.4.0
Hi all,
sorry to ask , but I need a translator help for "DUMP, SCANRAW, COLOR commands are not available". Please correct me, if I got it wrong: Dump is "screen dump", so a copy of the screen by a PC software. SCANRAW : reading of scan values without correction applied: Do I need this for a Software linke NanoVNA-Saver or is it an unused feature? COLOR: sounds like a manual setting of the colors ? Is it used by PC software and which? @Cornellu: Others may again correct me, but aa-Version is the name for "Antenna-Analyser", which means, that that only S11 (CH0) and 2 traces on the device are supported, but with bigger Fonts. No S22 "through" measurements possible. vy73 de Karsten, DD1KT |
Re: NanoVNA-Saver 0.2.0
Hi Herb
Yes you did, and murphy is a bloody optimist. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af hwalker Sendt: 16. november 2019 12:58 Til: [email protected] Emne: Re: [nanovna-users] NanoVNA-Saver 0.2.0 #Ferrite_Impedance Kurt Poulsen wrote, "You have a problem as you are calibrating on the output side of the test fixture. " ----------------------------------------------------------------------------------------------------------------------------- Kurt, Great explanation and much thanks for taking the time to do so. Did I mention something about "going down the rabbit hole" ¡ - Herb |
Re: NanoVNA-Saver 0.2.0
Kurt Poulsen wrote,
"You have a problem as you are calibrating on the output side of the test fixture. " ----------------------------------------------------------------------------------------------------------------------------- Kurt, Great explanation and much thanks for taking the time to do so. Did I mention something about "going down the rabbit hole" ¡ - Herb |
Re: NanoVNA-H v0.4.0
Sorry but what is?AA version display. pls ????
toggle quoted message
Show quoted text
On Friday, November 15, 2019, 08:57:50 PM GMT+2, Gyula Molnar <gyula.ha3hz@...> wrote:
New firmware from hugen: NanoVNA-H version compiled on November 15, 2019 Using the code of nanoVNA-Q of qrp73, the driving of si5351 and aic3204 is more reasonable. By judging that the si5351 locking state is more reasonable than simply setting a delay, it can effectively avoid the noise caused by the unstabilization of si5351. Unlike the compilation optimization of QRP73 and edy555, inline optimization is not disabled, and the refresh efficiency is better. Due to limited flash space DUMP, SCANRAW, COLOR commands are not available. Optimized for AA version display. |
Re: NanoVNA-Saver 0.2.0
Hi Herb
toggle quoted message
Show quoted text
You have a problem as you are calibrating on the output side of the test fixture. Then the fixture is part of you test cable going from the NanoVNA to the test jig and including also the "mystery" unknown impedance of the wire thru the testjig, mainly an inductor for low frequencies but for higher frequency you will even experience quarter wave length resonances. It will not work as you do it. You must calibrate at the input of the test jig with a female kit, first a calibration of the NanoVNA stored to C0, and the use NanoVNA-Saver and enter the calibration kit data if you have the using the delay setting for short and open and also the data for load if you got it. Then you measure you fixture without the clamp choke save it as s1p then measure the fixture with clamp choke and save it as s1p. Then you will measure far better than before well knowing you have the testjig wire thru the choke and if you has a shorter wire from input to output of the testjig then you will approach the single wite method like the manufacturers use. To take the process a step further to get material measurements without influence from parasitic element: The big problem comes how to subtract the two s1p from each other. In my case it was very easy using my VNWA software as I simply in a custom trace convert the two s1p files saved to e.g. Mem1 and Mem2 to subtractable impedances, by a simple expression like z2s(s2z(Mem2)-s2z(Mem1)). As you cannot subtract s parameter from each other the trick is to convert the measurement without the choke to and impedance s2z(Mem1) and the subtract it from the s1p with choke s2z(Mem2) and the convert the difference back to s parameter with the expression z2s. Then the custom trace is showing the true s parameter of the choke and the test fixture impedances is thus totally eliminated and the custom trace can be saved as a new s1p file for nice presentation in the NanoVNA-saver by importing the file. I think the free QUCS (Quite Universal Circuit Simulator) has facilities to do this trick as well and suggest you download it and have some fun. Take notice there are two version not compatible a German originated derived version of the original. I fancy the original. It has a lot of display features and is a fantastic piece of software. Regarding the fixture It ought to be completely closed so no field lines escape out in the blue air. Next level is how to calculate the real material parameter which involved all the math shown in the article. I added that in the custom trace also after calculation the chamber parameters in a spreadsheet and I settled for circular chambers like paint can with a fixed shorting rod mating a SMA SMA bulkhead thru adaptor in the center of the lid which then make the calibration better with the VNWA calibration kit configured a female kit, of which I have publish data to enter in the NanoVNA-saver. UPS that was a long story Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af hwalker Sendt: 16. november 2019 03:35 Til: [email protected] Emne: Re: [nanovna-users] NanoVNA-Saver 0.2.0 #Ferrite_Impedance On Fri, Nov 15, 2019 at 06:33 AM, Kurt Poulsen wrote:
" I have done a lot of such measurements in the past and eliminated the inductance of the wire thru the core. In your setup I think you get even better result by doing a SOL calibration at the end of the BNC adaptor using the Shorting wire thru the core without the core as short and place a leaded 50 ohm resistor as load and nothing for the open. The you get eliminated the "funny" impedances of the adaptors in the calibration process " ------------------------------------------------------------------------------------------------------------------------------- Kurt, The one turn loop gave me a method of sorting my ferrites by visual signature, but I could never get a good SOL calibration, per your suggestion, that extended beyond a few MHz. Since most of my unidentified ferrites are clamp-on style, I decided to "go down the rabbit hole" and try to build a fixture using some of the references you provided and material that I had on hand. Attached is a photo of the fixture I built. I tried to construct a coaxial type fixture where I could easily get access to the center conductor. I performed an OSL calibration from 1 - 500 MHz with the fixture cover in place and no ferrite installed. I made a reference plot with the fixture terminated in 50 ohms. The S11 impedance plot showed a straight 50 ohms with a slight bump at the 300 MHz band switch over point (see red trace in attached plot). I then replaced the 50 ohm load with the short standard used during calibration, installed a Fair-rite 0443164151 ferrite on the inner conductor (see attached photo), replaced the fixture cover and made a test run. The S11 impedance plot showed a rise in impedance with at least 100 ohms of impedance between ~17 MHz and 400 MHz (See black trace in attached plot) . The slight bump at 300 MHz during the reference run turned into huge outlier during the test run. I would typically remove it from my data set. The typical impedance data in the chart provided by Fair-rite does not closely match the data I obtained (see embedded chart data). I discovered that the coaxial fixture could also be used to measure the transfer impedance of an rf current probe that I had constructed from ferrites, so there was a secondary benefit to its construction. - Herb |
Re: NanoVna-Saver TDR
#tdr
Unfortunately I didn't find more easy solution which works good.
So, currently this matlab script is the only way that I know for TDR step response. If someone can help with math it will be great. |
Re: NanoVna-Saver TDR
#tdr
On Sat, Nov 16, 2019 at 10:31 AM, hwalker wrote:
This is not so easy, because it uses integrated matlab functions for S11 processing and their implementation is complicated. |
Re: NanoVna-Saver TDR
#tdr
On Fri, Nov 15, 2019 at 11:00 PM, QRP RX wrote:
" You can use complex pieces of cables with different impedance for testing it. For example: 1 meter 50 ohm + 1 meter 75 ohm + 1 meter 50 ohm + 25 ohm load. " ------------------------------------------------------------------------------------------------------- QRP, A number of people, including myself, have intentionally added mismatches along the length of the cable and made the same observation as you. I haven't tried to read your MATLAB code, I'm having enough trouble learning python and C# without adding MATLAB to the mix. Thanks for linking to your code. Hopefully someone familiar with both languages will take up the challenge and convert it to python. Rune is overworked these days and could use some contributions from the rest of us. Do you expect to translate the MATLAB code to C# and add it to your NanoVNA-Sharp MOD? - Herb |
Re: NanoVNA Noise improvements. Hugen79's NanoVNA Github Issue #14
#filtering
#noise
#improvement
#hack
#circuit
On Fri, Nov 15, 2019 at 09:34 PM, Gabriel Tenma White wrote:
" ¡ It's the absolute accuracy and confidence in the measurements that you care about, and if you look at the smith chart that hugen posted, it looks the same as the image erik posted earlier in his "chasing ghosts" thread, namely big unexplained dips in S11 above 600MHz that is unphysical when measuring a stub ¡." ------------------------------------------------------------------------------------------------- Thanks Gabriel. Its much easier for me to read the logmag plots and it takes more of a trained eye, like yours, to read the smith chart. hugen commented in the attached copy of the smith chart that reliable operation is limited to 1300 MHz, I suppose that is related to your comments as values after that become exceedingly noisy and eventually exit the circle of the smith chart (loss of directivity?). Most of my own measurements above 1 GHz are S21 through measurements. I would more than happy with 40 - 50 dB of head room above 1 GHz. When I first purchased the NanoVNA I was only expecting it to be useable to 300 MHz. All this additional measurement capability is icing on the cake for me. Regards, - Herb |
Re: NanoVna-Saver TDR
#tdr
You can use complex pieces of cables with different impedance for testing it.
For example: 1 meter 50 ohm + 1 meter 75 ohm + 1 meter 50 ohm + 25 ohm load. |
Re: NanoVna-Saver TDR
#tdr
The problem with this IFFT approach is that result looks like truth, but it is not.
If you test it on different datasets, you will find incorrect results. |
Re: NanoVna-Saver TDR
#tdr
On Fri, Nov 15, 2019 at 11:01 PM, <erik@...> wrote:
conjugate also cannot help. This is wrong approach. You're needs to interpolate S11, then use interpolation for integration step response. In such way it works ok. See my matlab script. |
Re: NanoVna-Saver TDR
#tdr
On Sat, Nov 16, 2019 at 12:41 AM, hwalker wrote:
This approach is incorrect and leads to wrong results. It will give you even worse results with signed value. I wanted to add this into NanoVNASharp MOD, but it shows incorrect results and there is no way to fix it. Because approach is incorrect. You can find correct approach in my MATLAB scripts: |
Re: SWR...Nano versus Transmitting
M Garza
Hi Ron,
Just to understand: You are disconnecting the cable from the back of the radio and connecting it to the vna? Is that correct? You are not using a different jumper or removing any of the existing items that are inline when connected to the radio, correct? If you are, that might change what you are reading. Thanks, Marco On Fri, Nov 15, 2019, 9:38 PM Ron - An Old Ham in Utah <k7uv@...> wrote: I'm using an external full-range tuner with a straight through (direct |
to navigate to use esc to dismiss