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
Early app for the NanoVNA
|
Currently NanoVNA has 4 calibration slots.
How about limit sweep count up to 4? *User must calibrate done every 1/4 bandwidth then save 0 to 3 calibration slot. *nanovna-saver loads every 1/4 bandwidth calibration slots prior to sweeps every 1/4 bandwidth. It would be more static(?) results we get - Just I my 2 cent |
|
The reason for having in-app calibration rather than using the calibration
toggle quoted message
Show quoted text
on the device is to avoid these problems. The in-app calibration supports pretty much however many calibration points you're willing to wait for, and it works by frequency, so you can change your span and still get reasonable results. I'm not a big fan of limiting users in what they do, so I'm certainly not keen on implementing a limit on sweep count. But if it can be shown that accuracy suffers with some settings, it might be prudent to add a warning. Thanks for your input! -- Rune / 5Q5R On Wed, 4 Sep 2019 at 09:19, RFy <gpdxdveil@...> wrote:
[Edited Message Follows] |
Right-clicking on the icon revealed the path, which, interestingly, is not visible if I do a search for python items on my c: drive.Windows filesystems have an attribute for hiding content, which some malware exploits. Yes weird, AKA "security by obscurity". Here are procedures to "unhide" from file Explorer: |
|
Gentlemen, many thanks for your help.
Python is now successfully installed and I can launch Rune's python code. The issue was that Python wasn't on the path (as several suggested). Fixed by checking the appropriate box when installing Python 3.7.4. I'm looking forward to playing with Rune's script when I return home. Best, - Jeff, k6jca |
|
Hi Rune --
Yes, I had done a sweep before the "short" calibration, but not the other two. It would be really nice if one could save a calibration to a file, so that he could recall the file on later invocations of nanovnasaver instad of having to recalibrate for similar runs every invocation. 73 -- Harry, W5PNY |
|
I agree on saving calibrations! The current development branch now has full
toggle quoted message
Show quoted text
SOLT(I) calibration, and I'll try to get saving/loading in before releasing 0.0.5 -- Rune On Wed, 4 Sep 2019 at 18:29, Harry McGavran Jr <w5pny@...> wrote:
Hi Rune -- |
|
The newly published 0.0.5 now allows saving/loading calibrations; and
2-port 1-path calibration as well. It still assumes perfect standards - I'll work on those further in future releases. It has a slightly different layout to allow more information from markers, and a mouse-controlled marker as well (only controllable on the logmag displays though). I look forward to hearing your feedback. -- Rune / 5Q5R On Wed, 4 Sep 2019 at 17:33, Rune Broberg via Groups.Io <mihtjel= [email protected]> wrote: I agree on saving calibrations! The current development branch now has full |
|
Wim
On Wed, Sep 4, 2019 at 08:58 PM, Rune Broberg wrote:
Just tried .05, and it worked for excellent for me. Tried a calibration with 10 sweeps and the mouse marker. One thing I noticed is that the calibration slot in the NanoVNA is still used when taking the calibration sweeps with your software. In my case this was really noticeable because I calibrated a small bandwidth before, and this was clearly visible when doing the load calibration sweep. I tried to "reset" the calibration on the NanoVNA and in your software, but this had no effect, the dip in the load sweep remained where it was calibrated before. I am unsure if this can have a negative effect on the accuracy of the calibration in your software. When I swept a load afterwards, I could not see any immediate negative effect. One suggestion for improvement of your app could be averaging to reduce noise (by repeating the same frequency sweep a definable number of times and averaging each point of the different sweeps) |
|
Rune,
So far release 0.0.5 is running well on my laptop. I reloaded some s1p files of S21 sweeps that I previously performed on some filters, and with your new marker readout capability was able to verify the -3dB frequency points and associated bandwidth for my bandpass filters. Outstanding work! I don't know what your day job is but you definitely have talent has a programmer. |
|
It's quite likely that the executable wouldn't run on 32 bit. It is built
toggle quoted message
Show quoted text
using 64 bit python, because that's what I run on this machine. I suggest using the master version in that case, or optionally that someone might be kind enough to generate 32 bit executables if requested on this list. With regard to the calibration from the device, I would expect that as long as the output from the NanoVNA is stable, it should not make a difference to the quality whether it is calibrated or not, as long as the app is calibrated correctly. I see good reason in what you said about averaging. Maybe even some code to sort out the occasional outliers that show up. I'll put it on the TODO list. And Herb, thank you very much for your kind comments. Programming is part of my line of work, but this is the first project of this scale I've done in Python, and it is the first time I've had to do all these RF calculations. There is a certain joy to working out these equations, getting them programmed in, and suddenly seeing a very recognizable value or trace popping up on the screen. I hope you enjoy the app, -- Rune / 5Q5R On Wed, 4 Sep 2019 at 23:04, Wim <wim_huyghe@...> wrote:
Just tried the executable from your release folder, I cannot run this on |
|
I too have tried to execute the .exe file from the .zip window, I am running Windows 10 64bit version and get a dialog box that I say to run anyway, but only get a brief "flash" window on my screen and then it disappears with no trace. I have not installed python etc. but I don't think I need anything else to run the .exe file. Any idea what is happening? Bob
|
|
Hi Rune,
I have downloaded your release 0.0.5 and am checking it out. Some comments: 1. At first I thought the Mouse Cursor was broken -- I was clicking in the S11 Smith Chart plot and I wasn't seeing its marker. Then I discovered accidentally that its marker would appear if I instead clicked in the S11 Return Loss plot. Any chance to get this marker to appear no matter which plot we first click our mouse in? 2. Also, in the version I downloaded this morning from the master (not release) folder (a version without the verbose Mouse cursor and dots for Markers in lieu of triangles), I could move the mouse cursor in the S11 Smith Chart plot. I cannot do this now -- I have to go to the S11 Return Loss plot to move it. 3. Reference Plot color -- works fine, but I notice that the color displayed in the "color button" is a very grayed-out version of the color I select. Not sure why it's grayed-out, as the color of the actual reference plot is fine. 4. The only way I seem to be able to get Markers 1 and 2 to appear on the screen is if I first type a frequency into their boxes, and then the markers appear (which might be your intention). But I know that the frequency I type isn't the actual frequency that the marker is pointing to (which I can read by ovelaying the mouse cursor on top of either Marker 1 or 2). For example, for Marker 2 I had typed in 500000000 (i.e. 500 MHz). But the actual frequency of the sample is 506.936 MHz. Would be nice if the displayed frequency were the actual frequency. 5. Being able to transfer the mouse cursor's frequency into either Marker 1 or Marker 2 would be a nice feature. 6. Would be nice to step the mouse cursor (and/or the markers) with the keyboard arrow keys for "fine tuning". 7. Heartily agree with adding averaging. 8. A word of caution regarding adding C0 (and C1, C2, C3) for the open calibration standard. As has been mentioned in other threads, there might be a 50 femtofarad value already hard-coded into the NanoVNA software as C0. Adding an external C0 parameter, without being able to zero out the existing C0, will defeat the purpose of adding the new C0 value. (If this is an issue, I would suggest contacting Hugen -- he might be able to confirm the existance of this hard-coded value. If it an existing compensation already exists, there might be some way to cancel out its effect -- maybe by adding to it a negative (!!!) 50 femtofarad value?). 9. It would be nice if the release version appeared someplace in the app. And finally...excellent job! - Jeff, k6jca |
|
Hi Bob,
toggle quoted message
Show quoted text
the app launches a console window first, in which any error messages should appear. If you double-click to launch, that's probably the brief flash you're seeing. You could try opening a command prompt in windows, moving to the directory where you unzipped the file, and running it from there. This should show you any errors. By the way, I assume you did unzip all the files? I haven't yet managed to make a version that doesn't require a whole plethora of different files, all included in the .zip -- Rune / 5Q5R On Thu, 5 Sep 2019 at 01:14, Bob Shaw <ve3suy@...> wrote:
I too have tried to execute the .exe file from the .zip window, I am |
|
Hi Jeff,
toggle quoted message
Show quoted text
thanks for the shopping list :D I'll respond to each: 1) In the LogMag charts, each X-coordinate has a well-defined frequency. In the Smith charts, I would have to find the closest point of the trace (or reference?) and set the frequency to that. That code is more complex, and thus I haven't done it yet. It's on the list though! 2) I think that might have been a glitch - I haven't had any code in the Smith chart for moving cursors. 3) The colour is a little grayed out because it's mostly transparent. The reference sweep is drawn on top of the measured sweep, but in a (more) transparent colour, in order not to completely blot out the sweep. With sufficiently many points, it starts to look solid. When picking a colour you can choose the "alpha" value to set transparency. 4) I'll make a display of the actual measured frequency for the cursors - great point. 5) I'll think about a nice way to make an interface for storing the mouse marker frequency into the other markers - or optionally moving the other markers using the mouse. 6) Stepping would be a great feature, I agree. 7) Averaging will probably arrive at some point. It shouldn't be too hard for pure averaging. But sweeps will get slow. 8) Good point on the double compensation - I will check the firmware. 9) I fully agree, we need an about button, and probably the version in the window title. :-) Thanks for all your feedback, and your praise in the other email! -- Rune / 5Q5R On Thu, 5 Sep 2019 at 02:38, Jeff Anderson <jca1955@...> wrote:
Hi Rune, |
Oristo
to navigate to use esc to dismiss