A little confused on the firmware versions.
Is the source code available for the nanoVNA_900_AA ? Or is that already in the hugen-modified 0.1.1 ?
What I really want is the best of all worlds for using the nanoVNA while hanging from my tower at 110 feet. Being able to measure Z at the feedpoint with large font and display of R + jX. I'm perfectly willing to tweak the code to do that, but I need the large font version as the starting point.
Thanks,
Steve, N2IC
|
Happy if somebody could answer the following:
I have FW Sept 19 2019:10.37.16. What is CAL/CORRECTION? Is it application of the selected RECALL?
Is it necessary to have CORRECTION highlighted when calibrating?
By the way: My battery-icon shows just the outline and nothing inside, is this correct for my current FW?
Thanks for any reply,
Torbjorn
|
Re: Experimental 256 point FFT Firmware
No, It is just ttrftech/NanoVNA head build. XENOMORPH is not an author.
|
Re: Trying to understand the T-Check outcome of the nanoVNA
Hi Erik One note If you are using the NanoVNA-saver and has entered the calibration kit data as a female kit (adding the delay of the Thru adaptor (2 x 62ps) for the short and open, then you only need to subtract the delay of the Thru adaptor for the s21/s12 measurements to have the right phase (0 degree) at both the two SMA male adaptors. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af erik@... Sendt: 25. september 2019 16:54 Til: [email protected]Emne: [nanovna-users] Trying to understand the T-Check outcome of the nanoVNA Using a not too good BNC Tee I performed a T-Check Attached the measurement (.s2p) and the excel file (.xlsx) in which the T-Check is calculated. Next to the T-Check calculation the excel also calculates the abs(Zin-Zout)/Z0 (the percentage absolute distance of the two impedances as another estimate of error) The frequency is denoted in MHz Do ignore anything above say 500MHz The T-Check suggests the error quickly increases to substantial levels but the abs(Zin-Zout)/Z0 suggests there is a very systematic error in my measurement where the absolute distance of the two rotating impedances grows very linear with frequency. I did calibrate using the Tee without (OSL) and with (T) the outgoing cable connected but maybe that did result into the error. What am I doing wrong?
|
Hi Rune Have a look on my answer to Erik about his T-Check experiment. There sis some issues about subtracting the delay of the thru adaptor which is missing in you calibration setup (I think ?) Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Rune Broberg Sendt: 25. september 2019 22:52 Til: [email protected]Emne: Re: [nanovna-users] NanoVNA Saver Hi Bryan, The signs on those phase plots have *really* been bothering me. It's one of the places where it really shows how much of a newbie I am at RF measurements: I have no idea what way the phase is *supposed* to go, so I might well end up flipping it ;-) I think I got it all pointing the same way in the coming version, which is in a development branch on GitHub. Maybe I'll post a screenshot and have you (or others) sanity check it before I release! Thanks for taking the time to report it! Reports like these really help make the software better. -- Rune / 5Q5R
On Wed, 25 Sep 2019 at 22:42, bryburns via Groups.Io <bryburns= <mailto: [email protected]> [email protected]> wrote: Rune, Using nanoVNA-saver0.0.11 It looks like the S21 phase in the marker box is of opposite sign to the plot of S21 phase. I think the phase in the plot is correct. -- Bryan, WA5VAH
|
Re: Trying to understand the T-Check outcome of the nanoVNA
Hi Erik Three problems. First of all you have not subtracted the delay of the Thru adaptor (2 x 62ps) when calibration s11/s22 as you remove the thru adaptor after s11 calibration and thus the calibration plane are 124ps out in the blue air. Second when measuring s21/s22 you must subtract the delay of the thru adaptor (1x62ps) from the calibration as then you have same phase at the two male SMA adaptor for the two test cables. That is why the T check is only some + - 20% and as seen for my image for 500MHz span as I throw away all points above 500MHz. Third the range above 900MHz is "stupid" to use as useless When above is done the T-Adaptor is sitting between two calibration planes where s11/s22 and s21/s12 are correct placed at the two calibration planes being identical to the measurement plane Good luck with the next steps Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af erik@... Sendt: 25. september 2019 16:54 Til: [email protected]Emne: [nanovna-users] Trying to understand the T-Check outcome of the nanoVNA Using a not too good BNC Tee I performed a T-Check Attached the measurement (.s2p) and the excel file (.xlsx) in which the T-Check is calculated. Next to the T-Check calculation the excel also calculates the abs(Zin-Zout)/Z0 (the percentage absolute distance of the two impedances as another estimate of error) The frequency is denoted in MHz Do ignore anything above say 500MHz The T-Check suggests the error quickly increases to substantial levels but the abs(Zin-Zout)/Z0 suggests there is a very systematic error in my measurement where the absolute distance of the two rotating impedances grows very linear with frequency. I did calibrate using the Tee without (OSL) and with (T) the outgoing cable connected but maybe that did result into the error. What am I doing wrong?
|
Re: Annotated nanoVNA menu diagram
Lets hope none of the other builds aren't different! That menu is updated to correct link bugs: Its associated help file has been improved but not updated to address functionality added since "original" firmware; Additional software and firmware description:
|
Rune, I really appreciate the work you¡¯re doing¡ especially the .exe files. Radios I understand, but ¡°compiling¡± and those odd prerequisites are way above my pay grade. ? Paul M0GJL
|
Great to hear, Paul! I'm certainly not intentionally doing anything to make
it more difficult to run :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 25 Sep 2019 at 23:16, <techo@...> wrote: NanoVNA-Saver runs OK on my old bog standard Acer 64 bit laptop running
Win 7 home premium. The only glitch I have is AVG has to check out a file
before letting me run the latest release for the first time. Once AVG
gives the ¡°all clear¡± Saver runs without any problem. Paul
|
NanoVNA-Saver runs OK on my old bog standard Acer 64 bit laptop running Win 7 home premium. The only glitch I have is AVG has to check out a file before letting me run the latest release for the first time. Once AVG gives the ¡°all clear¡± Saver runs without any problem. Paul
|
Hi George,
I'm not suggesting you need to upgrade to Windows 10 - as mentioned, the
app is built on and runs on Windows 7.
I don't know anything about Framework 4.0 or Framework 3.5, but a quick
look reveals that Microsoft .NET Framework 4.0 was released just under nine
and half years ago. I don't specify anything in my software to say that
it's required, but I could see why the build software might assume it is
installed on PCs in current use. ;-)
I do think it requires some version of the Microsoft VC++ redistributable
packages. But again, I couldn't say which: The build machine never had any
externally added to it that did not come automatically with Windows Update.
As to thread hi-jacking, I have no idea. I try to reply to the posts that
address me and/or my software fairly quickly, and I rarely pay that much
attention to the rest of the thread unless I really need to. I can't keep
track of all the threads I get involved with anyway ;-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 25 Sep 2019 at 23:04, George <steber@...> wrote: Rune,
You are doing fine work. Keep it up.
But I hope you can understand the frustration of not being able to run the
software on the many laptops and other computers that have not been
upgraded to Win10. We do not want to install a bloated Framework 4.0 when
it already has Framework 3.5 --- just to run one program.
If you ever get it to run on WinXP that would be a big big plus!
I'm sure a software developers life is full of headaches. Hope you hang in
there. Your work is appreciated by many here.
By the way, how did this thread get hi-jacked away from dealing with Win7
issues?
On Wed, Sep 25, 2019 at 01:12 PM, Rune Broberg wrote:
Hi George (and others),
the .exe for NanoVNA-Saver is built on Windows 7 - on a virtual machine
that's used for nothing else. It has the build tools installed, but
otherwise is just a (fully updated) clean Windows 7 install.
I'm not sure what else I can do to make it run on a clean Windows 7? I
*do* assume that people install updates - I don't think I have any way to
generate executables that will work on un-updated machines, or indeed on
Windows XP, which I've recently discovered there are still people using.
If you have any suggestions on what to do to make it more portable, let
me
know :-)
--
Rune / 5Q5R
On Wed, 25 Sep 2019 at 21:59, George <steber@...> wrote:
On Tue, Sep 24, 2019 at 11:54 PM, peter_pc2a wrote:
Hi
I have a problem to get Saver working together with Win7
The program starts, but as soon I connect the VNA the program top
working
Did try on Win7 32, 64 and different pc's, but same result
Swap HD op the pc and run Win10, it works
Any idea?
Peter
We had the same problem here... works with Win10 but not Win7. Not
sure if
this is the cause of your problem.
We found that Win7 did not have latest Framework 4.0.
Many software developers assume that we all have the latest versions.
We finally gave up trying to get it to work with Win7 on all of the
laptops here.
|
Rune,
You are doing fine work. Keep it up.
But I hope you can understand the frustration of not being able to run the software on the many laptops and other computers that have not been upgraded to Win10. We do not want to install a bloated Framework 4.0 when it already has Framework 3.5 --- just to run one program.
If you ever get it to run on WinXP that would be a big big plus!
I'm sure a software developers life is full of headaches. Hope you hang in there. Your work is appreciated by many here.
By the way, how did this thread get hi-jacked away from dealing with Win7 issues?
toggle quoted message
Show quoted text
On Wed, Sep 25, 2019 at 01:12 PM, Rune Broberg wrote:
Hi George (and others),
the .exe for NanoVNA-Saver is built on Windows 7 - on a virtual machine
that's used for nothing else. It has the build tools installed, but
otherwise is just a (fully updated) clean Windows 7 install.
I'm not sure what else I can do to make it run on a clean Windows 7? I
*do* assume that people install updates - I don't think I have any way to
generate executables that will work on un-updated machines, or indeed on
Windows XP, which I've recently discovered there are still people using.
If you have any suggestions on what to do to make it more portable, let me
know :-)
--
Rune / 5Q5R
On Wed, 25 Sep 2019 at 21:59, George <steber@...> wrote:
On Tue, Sep 24, 2019 at 11:54 PM, peter_pc2a wrote:
Hi
I have a problem to get Saver working together with Win7
The program starts, but as soon I connect the VNA the program top working
Did try on Win7 32, 64 and different pc's, but same result
Swap HD op the pc and run Win10, it works
Any idea?
Peter
We had the same problem here... works with Win10 but not Win7. Not sure if
this is the cause of your problem.
We found that Win7 did not have latest Framework 4.0.
Many software developers assume that we all have the latest versions.
We finally gave up trying to get it to work with Win7 on all of the
laptops here.
|
Hi Bryan, The signs on those phase plots have *really* been bothering me. It's one of the places where it really shows how much of a newbie I am at RF measurements: I have no idea what way the phase is *supposed* to go, so I might well end up flipping it ;-) I think I got it all pointing the same way in the coming version, which is in a development branch on GitHub. Maybe I'll post a screenshot and have you (or others) sanity check it before I release! Thanks for taking the time to report it! Reports like these really help make the software better. -- Rune / 5Q5R On Wed, 25 Sep 2019 at 22:42, bryburns via Groups.Io <bryburns= [email protected]> wrote: Rune,
Using nanoVNA-saver0.0.11
It looks like the S21 phase in the marker box is of opposite sign to the
plot of S21 phase. I think the phase in the plot is correct.
--
Bryan, WA5VAH
|
Rune,
Using nanoVNA-saver0.0.11
It looks like the S21 phase in the marker box is of opposite sign to the plot of S21 phase. I think the phase in the plot is correct.
--
Bryan, WA5VAH
|
On Wed, Sep 25, 2019 at 09:30 PM, Wolfgang Kiefer wrote: But: In my opinion a moderator has to prevent the forum users from spam. Yes, so if users are pissed off with a certain user then deal with the person who is CAUSING the complaints, and not the people complaining. This is not happening here, and we're pissed off with the management. 73 de Andy
|
Re: errors of "error" models
@Gary O'Neil Hello, Thank you very much for your kind interest on our Work! We much appreciate that. Especially, the most encouraging guess also made by you about "missing terms". Very interesting indeed! Thank you, once more. Now, regarding your questions included at: /g/nanovna-users/message/3041we would like to ask you first to tell us, please, if you tried our software, that is if you already compiled and run the FORTRAN REGION and then the MAXIMA DERDEI, to see its rich, multiple-output graphics. Sincerely, yin&pez@arg 11
|
Because I got the same warning from moderator Dave Daniel (via email), I want to hold the ball flat...
But: In my opinion a moderator has to prevent the forum users from spam.
Now my remarks to the theme NanoVNA V2:
- have you seen the EU1KY analyzer? This model has a 4.3" touch screen.
- and the extensions from KD8CEC?
(You can find both via google.)
I hope, that one day all the good ideas will be marriaged.
73, Wolfgang DH1AKF
|
Rune, Excellent... Very good, that is a very nice benefit.
Alan
|
And if I disappear from this group, you all know what has happened.
A false god with a mouse and delete key got rid me ;-)
Let that be an informative lesson if it happens.
73 de Andy
|
Hi Alan,
one of the features of NanoVNA-Saver - the prime one, really, from my point
of view - is the ability to sweep many more than 101 points. I think I've
used it up to 20200 points at one time, but I believe there are people who
have tried more ;-)
So it should be possible to get decent data, I hope.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 25 Sep 2019 at 22:02, alan victor <avictor73@...> wrote: One other note Rune. And others can comment in if I am off base. After
thinking about this a bit more, there may be an issue in obtaining GD and
what is known as differential group delay accurately particularly for
NARROW band networks. The Nanovna is currently limited to 101 data points.
No issue for wide band networks but for narrow band there may be a problem
with just 101 points to obtain a sufficiently small aperture. As a rule of
thumb, to get GD proper, the frequency step size must be a fraction of the
network band width. Taking that into consideration, 101 data points may
fall short of the desired resolution to obtain GD. Maybe not, have to run a
simulation for grins on say a crystal filter or a very high Q LC filter and
see if this is an issue. FUN!
Alan
|
cho45
Kurt Poulsen
Oristo
gin&pez@arg
Wolfgang Kiefer