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
History
N7PH
Gentlemen,
As the editor I would like to write an article for the Tacoma Radio Club's newsletter including the history of the development of the NANO-VNA. I would like to include the names of the designers/developers and software developers as well variations out there. I have been unable to pin down very much of this information after several hours of internet searching. Who is edy555? Who is Hugen and how is he involved? What is the involvement of Rune Broberg; software only? Any others I have not come across? Would someone on the list please pass along the history to me; I would much appreciate it. Thanks, PJH, N7PH |
Re: CAL -> RESET -> CALIBRATION clarification...
Herb and Larry thanx both,
all clear now, confirming what I thought and hoped that CAL->RESET doesn't clear the current contents of C0-C4 while "clearconfig 1234" does. Best regards and thanx again for the great work that you and many others are so generously giving to the rest of us... I hope one day to be able to contribute too. lm |
Re: THE NANOVNA - A COMMENT
Great comments!? I add my "Whale Done" to them.
toggle quoted message
Show quoted text
I haven't begun to fathom the depths of the Nano, but I thank those who poured themselves into the design and manufacturing of it. I have had and used the HP 8753 for years and now have 3 small VNAs including the Nano.? They are all helpful. Keep up the good work,? It is appreciated. Ray, W4BYG On 12/9/2019 6:22 PM, David Eckhardt wrote:
All too often we receive criticism for something we have accomplished or |
Re: errors of "error" models
I'm still trying to understand what you are publishing.
Am I correct your model as published in the white on black picture is a one port model like this and you describe how to determine the model using 3 known DUT's as in this Where you still have to solve the three equations but as I am laizy I use Maxima leading to this result: Or am I completely failing to grasp what you are trying to convey? -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files: /g/nanovna-users/files Erik, PD0EK |
Re: 30MHz and below
On Tue, Dec 10, 2019 at 06:19 AM, Howard Fidel wrote:
There is no advantage. The 101 points are across the frequency range displayed. =========================================================================== The advantage comes in how the 101 points are used. If your original configuration was for 50k -900M, then the 101 measurement points are about 8.9 MHz apart. The stored calibration points are also 8.9 MHz apart. In the 50K- 30M you only have about 4 measurement and calibration points available. If you change your configuration to 50K-30M, then the 101 measurement points are now about 297 kHz apart. You have better frequency resolution, however; you still have only 4 calibration points available and a lot of interpolation will be involved. This can result in quite inaccurate VSWR readings and demonstrates why it is important to re-calibrate when you change your frequency range. - Herb |
Re: hp limiter
On Tue, Dec 10, 2019 at 05:20 AM, <nanovnauser@...> wrote:
hi all,ive an old hp limiter from an old spectrum analyzer. Its a 5086-7282 0-1.8ghz, is it worth putting this on the input port of my nanovna as a protection,is it a goog idea or bad?,73. ============================================= The 5086-7282 is a diode limiter. Diodes are non-linear devices and can introduce uncertainties in your measurements. The input port of the NanoVNA is CH1 and placing the limiter there would protect the port from signals greater than 30 dBm (if I remember the specs for the limiter correctly). I believe 30 dBm might be higher than the NanoVNA is rated for and would give you a false sense of security. I can't recall any commercial or amateur VNA designs with a limiter on the output port (NanoVNA CH0) because of the non-linearity issue previously cited. - Herb |
Re: hp limiter
Read up on the various messages that talk about the reference plane.
toggle quoted message
Show quoted text
The limiter will limit when it is connected to the Nanovna but if you are performing antenna testing, if the Nano is floating, it becomes part of the antenna system and readings can be incorrect. On Tuesday, December 10, 2019, 9:33:19 a.m. GMT-5, nanovnauser@... <nanovnauser@...> wrote:
looking at it,as i right in thinking they provide an overlod? path to ground?,ie shunt or thru/series,ie do i need to ground the? body or will it do that via the sma conectors on it? |
Re: hp limiter
Spell checker smile of the day...... :-)
toggle quoted message
Show quoted text
This is a 10W limiter is similar to yours, so I would suspect you could use it on CH1 without issue as long as you re-calibrated with it attached. ...Larry On Tuesday, December 10, 2019, 8:20:25 a.m. GMT-5, <nanovnauser@...> wrote:
hi all,ive an old hp limitre from an old rectum paralyser,its a 5086-7282 0- 1.8ghz,is it worth putting this on the input port of my nanovna as a protection,is it a goog idea or bad?,73. |
Re: nanoVNAPartner v0.17
Thanks!
toggle quoted message
Show quoted text
The download works great. I'll be trying it out later today! On 12/9/2019 4:11 PM, neb40gsm via Groups.Io wrote:
Have you tried downloading it from this link: --
Cheers, Ed Humphries, KT4ED |
Re: CAL -> RESET -> CALIBRATION clarification...
Hi Luigi,
toggle quoted message
Show quoted text
The RESET on-screen button clears only the current calibration constants in RAM and it needs to be used any time you attempt a calibration/save sequence. It does NOT clear what is already stored/saved in flash(ROM). The console command CLEARCONFIG does that and loads defaults into flash memory at all 5 locations.? So - with that said, if you want to perform an additional calibration for 1 to 30MHz, you would set your freq range then perform:? CAL -> RESET -> CALIBRATION ->SOLT -> Save 1 through 4? OR? If you only want to use the 1 to 30MHz range most of the time, you can save to location 0 and it will load that calibration at power-on every time. You can verify that when you cycle power, memory 0 returns what you've stored there. I hope this clears up things. ...Larry On Tuesday, December 10, 2019, 3:56:07 a.m. GMT-5, Luigi Mantuano <l49mantuano@...> wrote:
Good Evening to all, as a beginner and despite having been reading ALL of these posts, I¡¯m still a little confused about the use of RESET during the initial or any subsequent calibration. Let¡¯s say I do the initial STIMULUS Start/Stop 50K-900M, then CAL -> RESET -> CALIBRATION¡ go through the OSLIT procedure¡ SAVE in C0 and double check SMITH for marker position on O, S, L¡ and all is good, yeah! Now I decide to set up a range on HF (say 2M to 30M)? so STIMULUS Start/Stop 2M-30M, next CAL and then¡¡. RESET or NOT???? Continue as above and SAVE in C1 or C2, C3 or C4¡ Two main articles on the subject, on this forum, suggest opposite instructions, hence my confusion¡? And then we have the Console command ¡°clearconfig 1234¡±, which apparently clears? "ALL Config and Calibration data from the device¡±. Ok, that¡¯s for another time. Many thank in advance, Luigi M |
Re: CAL -> RESET -> CALIBRATION clarification...
Luigi
Each time you perform a calibration the following procedure should be performed: 1. Reset current calibration state, <CAL- RESET> 2. Connect the OPEN standard to the CH0 port, <CAL - CALIBRATE OPEN> and execute. 3. Connect the SHORT standard to the CH0 port, <CAL - CALIBRATE SHORT > and execute. 4. Connect the LOAD standard to the CH0 port, <CAL - CALIBRATE LOAD> and execute. 5. Connect the LOAD standard to both the CH0 and CH1 ports, <CAL - CALIBRATE ISOLN> and execute. If there is only one load, the CH0 port can be left unconnected. 6. Connect the cables to the CH0 and CH1 ports, connect the cables with the through connectors, <CAL - CALIBRATE THRU> and execute. 7. Finish calibration and the error correction information will be computed, <CAL - CALIBRATE DONE> 8. Specify the memory cell number and save, <CAL - CALIBRATE SAVE - SAVE 0> or save to one of the other 4 memory locations if desired. Notes: 1. Saving to <SAVE 0> will make the calibration the default configuration when the NanoVNA is turned on. 2. If you save to one of the other 4 memory locations you need to use the RECALL menu option to reload the configuration. 3. If you don't perform a save then the calibration is only temporary and will be lost after power off. The former SAVE 0 configuration will be re-stored at power on. 4. If you are only performing a temporary change for through lost measurements, you do a quick normalization by skipping steps 2 - 5 and skip step 8. The normalization will only apply for the current session. Hope that helps. - Herb |
Re: New version of NanoVNA-Saver: 0.2.1
Hi Lajos
Yes I use arbitrary calibration setting. It provides the best calibration. For the NanoVNA I use different versions on the 3 I have. Latest edy555, Latest Hugen-H versin AA with nice larger alphanumeric characters and the default Hugen supplied with my cased Hugen-H. I am about to try the latest Q version I know the method for finding Zo and K factor in ZPlots. I just did the other day short/open method with success Good luck with getting calibration kit made. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af pgc1682@... Sendt: 10. december 2019 10:28 Til: [email protected] Emne: Re: [nanovna-users] New version of NanoVNA-Saver: 0.2.1 Hi Kurt, Thanks for the detailed example pdf. I will try it. I not understand some things on calibrations. Your calibrations better than my. I not have well enginered measured oslt cal set with proper data. I have oslt not only sma but no data. I use also wvna (not my). Its have calibration kit and data. But with bad condition. You use arbitrary calibration model on your wvna? Wich firmware use on your nanovna? Currently i use qrp not newest firmware. I see more nanovna. Not same result. My nanovna better. I not know why. I think hugen device both, but not sure. Much higher noise and amplitude change on harmonic change. Version 3.2 (better) version 3.3 pcb. On 3.3 not qrp firmware running. I see your final result on port extension. Good wideband result. It will be better. Rest loss exist. I not know why, oslt calibration residual or your cable slighy higher loss than database. I recommend try k parameter optimize by hand. Or try measure k parameters on well calibrated device. With zplots can do. Simple short/open sweep required and zplots calculate parameter for cable. Better if you have not 50 ohm terminators, low/high resistor method. Diy terminators possiby on sma zero leg + two 0805 resistors. 73, Lajos |
to navigate to use esc to dismiss