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
Search
NanoVNA Saver
hwalker,
Where do you find NanoVNA Saver 0.0.10a.exe ? I went here: and see 0.0.10 but not 0.0.10a. Would love to have the whole screen fit in my 1366X768 screen. Rune, Thank you so much for fitting the whole screen into a 1366x768 screen. That will really make the NanoVNA Saver software so much easier to use. Thanks, Steve_WB8GRS |
Hi Kurt,
toggle quoted message
Show quoted text
thank you for trying out the app! I'll certainly consider a way to lock the markers out of mouse control. I'm looking into zooming/scaling of the plots, but I don't have a great solution figured out yet. I hope you enjoy using the software :-) -- Rune / 5Q5R On Sat, 21 Sep 2019 at 11:58, Kurt Poulsen <kurt@...> wrote:
Hi Rune |
Hi Jim,
toggle quoted message
Show quoted text
I've studied the file, and it seems the same values were used for the different calibration standards (OSL as well as I&T). In a fit of poor design philosophy, I initially elected *not* to let the buttons in the calibration screen run the sweep for you, but to expect the user to do this manually for each standard before pressing the respective button. It's become blatantly clear that this is completely unintuitive, and I'll be looking at changing it - but for now, when you want to use in-app calibration, make sure that you run a sweep for each standard, and after each, press the relevant button in the calibration window. That's currently the only way to get a valid in-app calibration. I'll make a better interface for it, but it probably won't be for a couple of releases (ie. not this coming week ;-) -- Rune / 5Q5R On Sat, 21 Sep 2019 at 22:33, <jimcking@...> wrote:
Hi Rune, |
Hi Logan,
toggle quoted message
Show quoted text
thank you for the suggestion. Implementing "bold" probably wouldn't be a big problem. I have previously implemented "scaling" for high def monitors on advice of other users, which should allow operating system scaling to work without major problems, at least for Windows. I make no promises, but you might have a look at this in the meantime? Also, thank you very much for suggesting that I'm getting close to positive integer major version territory - at times, I still feel very far off ;-) -- Rune / 5Q5R On Sat, 21 Sep 2019 at 23:09, kz6oscar <lrahnz@...> wrote:
Rune, |
Hi Herb,
toggle quoted message
Show quoted text
thank you for the feedback and the suggestion. It's good to hear that it's starting to fit on 1366x768! I have received other comments indicating that being able to store "comments" about sweeps was a desired feature, and I'll definitely look at adding it. The charts should all have some room at the top for a header as well. :-) -- Rune On Sat, 21 Sep 2019 at 23:19, hwalker <herbwalker2476@...> wrote:
Rune, |
Hi Maurizio,
toggle quoted message
Show quoted text
thank you very much! Exactly the kind of thing I was looking for. It seems my current implementation in the development version isn't far off from what Keysight do; though I do need to set up the IIF/IIR for continuous/live sweeping. -- Rune / 5Q5R On Sat, 21 Sep 2019 at 23:48, Maurizio IZ1MDJ <redifon500@...> wrote:
Hi , I found some info about the smoothing and average on Keysight network |
Hi Steve,
toggle quoted message
Show quoted text
as I see Herb has informed you already, there's currently no executables for the 10a-version, which is my development branch. "a" at the end generally indicates that it's between releases - I've started doing this just to keep track of what app I'm myself running when checking for bugs ;-) If you do wish to run the latest, greatest (and most unstable!) version, the readme contains very superficial instructions. It requires having Python 3.7 and git installed, and knowing how to use it is a good idea. For most users, at the rate I'm currently managing to make releases, I recommend waiting for the .exe. These features should be out in a proper release within the next 48 hours. :-) -- Rune / 5Q5R On Sun, 22 Sep 2019 at 00:55, WB8GRS <ssedgwick@...> wrote:
hwalker, |
Hi Rune
toggle quoted message
Show quoted text
Absolutely an enjoyment to use. Keep up the good work Have not yet tried the calibration, will do. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]> P? vegne af Rune Broberg Sendt: 22. september 2019 09:26 Til: [email protected] Emne: Re: [nanovna-users] NanoVNA Saver Hi Kurt, thank you for trying out the app! I'll certainly consider a way to lock the markers out of mouse control. I'm looking into zooming/scaling of the plots, but I don't have a great solution figured out yet. I hope you enjoy using the software :-) -- Rune / 5Q5R On Sat, 21 Sep 2019 at 11:58, Kurt Poulsen <kurt@...> wrote:
Hi Rune |
Hi Rune , I get the last version , and I will test the average function as son as possible.
Many thanks for the very good application . Next week I wil measure a notch FM filter using the nanoVNA using nanosaver , and also an hp8752B . I will compare the measures and post the graphics. Best regards Maurizio IZ1MDJ |
I've been happily using the NanoVNA and various versions of "Saver" for a lot of projects lately, but some were just motivated by curiosity about the device.
Unfortunately I have no other analyzer to compare to. In any case here are some sweeps from earlier tests that might be useful for reference or amusement. In most cases, they were done with my very early attempts at full bandwidth calibration. - The fm filter is a commercial product from the rtl-sdr.com people. - The LW filter is a homebrewed design I use to augment VLF beacon hunting. - The multiband dipole is my 20ft high 80/40 meter trap dipole that has been augmented with parallel dipoles for 15 and 10. The feedline has a toroid common mode filer. - The 6 meter antenna is an attic mounted dipole with a toroid common mode filter. I've also used happily used the device and "saver" to design and build a 6 meter "squalo", but forgot to save the files from the latest testing run. I'm currently working on a 400-700 mhz indor LPA design and plan to try to use the device for relative pattern and gain testing. Earlier tests with several types of 500-900mhz 1/4 wave mag-mount antennas and TV rabbit ears showed useful relative gain results at 2-3 wavelength spacings. 73, AE0GL fm_bandstop.s2p
fm_bandstop.s2p
LW-lpf.s2p
LW-lpf.s2p
multiband-dipole.s1p
multiband-dipole.s1p
6meters.s1p
6meters.s1p
|
On Sun, Sep 22, 2019 at 06:09 AM, Mario Vano wrote:
CORRECTION: (I mistyped) - The multi-band dipole is my 20ft high 40/20 meter trap dipole that has been augmented with parallel dipoles for 15 and 10. The feedline has a toroid common mode filter.
|
For those waiting for new binaries: I just published 0.0.11 :-)
toggle quoted message
Show quoted text
This release brings averaging as a new feature: Press "Sweep settings" to select between running a single sweep (of optionally multiple segments), a continuous (live) sweeping of the range, or to average several sweeps from the NanoVNA. You can configure how many averages to make, and optionally, how many of the sample points to discard, based on which deviate the most from the rest, and are least likely to contribute signal. Also added is a new Resistance/Reactance chart, which shows both the R and X component of R+jX. This brings the challenge of showing two traces for the same data - added is therefore the option of picking a secondary colour for sweeps under "Display settings". There are further improvements to UI sizing, meaning the interface now fits - tightly - on a 1366x768 screen, at least on Windows. A few quality of live improvements made it in: Press escape in any of the pop out windows to close them instantly. The calibration window now shows more clearly when the source of calibration data is loading from a file, and also the number of points loaded. A few crash bugs were fixed. I look forward to hearing feedback from all of you! -- Rune / 5Q5R On Sun, 22 Sep 2019 at 17:14, Mario Vano <mvano@...> wrote:
On Sun, Sep 22, 2019 at 06:09 AM, Mario Vano wrote: |
Hi Rune,
Thank you for this great software for the nanovna. I appreciate the 3 different markers which are available and you readout a lot of good information in the boxes to the left of the graphs. Would it be possible to put the S11 phase in that box in the lower right corner? I don't see a way to readout the actual phase angle except by looking at the S11 phase plot. Am I missing an easy place to get the S11 phase at a particular frequency? Thanks. -- Bryan, WA5VAH |
Hi Bryan,
this sounds easy to implement. I'll put it in the next version. :-) -- Rune / 5Q5R On Sun, 22 Sep 2019 at 23:45, bryburns via Groups.Io <bryburns= [email protected]> wrote: Hi Rune, |
Hello Rune,
toggle quoted message
Show quoted text
Again thank you for your perseverance with the nanoVNA PC Software you are bringing us all! It is very much appreciated. However I have a question regarding Calibration using your software, I presume that before I set about doing a Calibration in nanoVNA-Saver, and reset it, I should also do a reset of the VNA Hardware itself? Or is this taken care of by nanoVNA-Saver? As I still see the "0" come up alongside the "C" in the left hand sidebar. 73's Pete ZL2iK -----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Rune Broberg Sent: Monday, 23 September 2019 07:37 To: [email protected] Subject: Re: [nanovna-users] NanoVNA Saver For those waiting for new binaries: I just published 0.0.11 :-) This release brings averaging as a new feature: Press "Sweep settings" to select between running a single sweep (of optionally multiple segments), a continuous (live) sweeping of the range, or to average several sweeps from the NanoVNA. You can configure how many averages to make, and optionally, how many of the sample points to discard, based on which deviate the most from the rest, and are least likely to contribute signal. Also added is a new Resistance/Reactance chart, which shows both the R and X component of R+jX. This brings the challenge of showing two traces for the same data - added is therefore the option of picking a secondary colour for sweeps under "Display settings". There are further improvements to UI sizing, meaning the interface now fits - tightly - on a 1366x768 screen, at least on Windows. A few quality of live improvements made it in: Press escape in any of the pop out windows to close them instantly. The calibration window now shows more clearly when the source of calibration data is loading from a file, and also the number of points loaded. A few crash bugs were fixed. I look forward to hearing feedback from all of you! -- Rune / 5Q5R On Sun, 22 Sep 2019 at 17:14, Mario Vano <mvano@...> wrote: On Sun, Sep 22, 2019 at 06:09 AM, Mario Vano wrote: |
Hi Rune,
I have made a large number of routine impedance measurements using your V0.0.10 exe binary under Windows 10 Pro 64b. I have not encountered any stability problems and in general think it works wonderfully well - thank you! One part of the GUI that I didn't understand intuitively the first few times I used it was the purpose of the "Segments" box. I changed it and nothing seemed to happen. I of course noticed immediately that it is a multiplier for the number of steps in the sweep once I changed it and then happened to do a calibration which shows the number of steps in the sweep. I decided I would like to make a suggestion that I hope is worthy of consideration. It occurred to me that it would be obvious to the user that the segments setting increases the sweep frequency resolution if the number of Hz per step could be shown. Additionally I think the provision of the "Hz/Step" information would be useful in some situations. For example when sweeping a network with narrow high Q responses the user may wish to select a segments setting that provides a sufficiently small step size to ensure a narrow peak or null is not missed without increasing the sweep time any more than necessary. A second advantage for providing the "Hz/Step" data is that it would provide immediate indication of how a change of the segments setting changes the sweep resolution. This feedback would make the setting more user intuitive I think. Considering that the number of segments would never exceed two digits and the number of Hz per step would never exceed 7 digits there might be room to fit the two boxes on the existing segments line within the GUI. If for example the "Segments" label were abbreviated to "Segs." with a two digit box then possibly there would be room for another label something like "Hz/Step" followed by a 7 (or 9 if 2 comma delimiters) digit box on the same line. Just might be one of many possible ways to implement it without impacting the existing GUI layout very much. Thanks again for your great contribution - "NanoVNA-Saver" really enhances the usefulness of my nanoVNA for what I intend to use it for! Enjoy! Tom VA7TA |
Hi Pete,
toggle quoted message
Show quoted text
you don't need to reset the NanoVNA calibration - it probably even works better if you don't, in that the data received from the NanoVNA will not be rejected as mangled during data transmission if it "looks like" real data. ;-) -- Rune / 5Q5R On Mon, 23 Sep 2019 at 03:19, Peter Mulhare <peter@...> wrote:
Hello Rune, |
to navigate to use esc to dismiss