Re: New version of NanoVNA-Saver: 0.2.1
Hi Run I did demo the NonoVNA-saver 0.2.1 to night I the locale HAM club and in the preparation this afternoon I tested the delay function and it seem it is not doing a correct calculation and quite big difference. Will chase how much it account for and let you know if you have forgotten a 2 times phi ? I noticed a comment a shift to the end of a cable. In my opinion the calibration should be done at the end of cable and the delay only used to shift adaptor delays and the like not the large a chunk a delay Kind regards Kurt. -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Rune Broberg Sendt: 4. december 2019 12:24 Til: [email protected]; [email protected]Emne: [nanovna-users] New version of NanoVNA-Saver: 0.2.1 I have released a new version of NanoVNA-Saver, 0.2.1: <> This release is a minor update to the 0.2.0 release: New feature: Capacitance and Inductance charts These new charts display the calculated series equivalent Capacitance and Inductance against frequency. New feature: Panning and modified zooming You can now hold the middle mouse button to pan a zoomed chart, or hold shift or control to only zoom the value or frequency axis when zooming using the mouse wheel. Moving markers using the arrow keys After placing a marker on a chart by clicking with the mouse, it's now possible to move the marker immediately using the arrow keys. Experimental feature: Port extension/Offset delay The calibration window has a new experimental feature. You can set an offset delay, which I'm told is useful for compensating for cables used when measuring without doing a full calibration. The value is applied immediately when changed, and is not connected to the other calibration features. Feedback on this feature is specifically requested. Additionally, a number of bugfixes have been made, based on your feedback - Thank you! A lot of tidying has happened on the back end of the code, as well as the introduction of some automatic testing - thanks to Holger M¨¹ller and David Hunt! As ever, I look forward to hearing all your feedback and suggestions! -- Rune / 5Q5R
|
I'm in the USA, and am looking for a NanoVva to go to 1090 Mhz, as I have several 17 element 900 Mhz Yaagi's that I want to modiflt to 1090 Mhz.
So I am looking forward to any posts similar to this one.
Tom W7TJM
|
Re: New version of NanoVNA-Saver: 0.2.1
On 12/4/19 7:22 AM, Mario Vano wrote: I can't find it. What do you use for a middle mouse button on a macintosh if you have an apple two button mouse? ???? Don't know about Mac, but in Linux you would use both mouse buttons simultaneously to emulate middle mouse button.? Maybe do a web search for 'mac middle mouse button emulate'?? Or buy a different mouse?
|
Re: New version of NanoVNA-Saver: 0.2.1
Dear Rune,
thank you very much for the very fast reply -- I am very pleased -- as it is your hobby to increase the usabillity of nanovna... Thanks for all!
I made my observations with the offset feature in single sweep mode --- but it may depend on my settings:
As nansnovna-saver breaks the limits of the 101 points, my ordinary setting for nanovna-saver usage is 5 segments, 3 repetitions each segment.
And this settings result in my observed fixed "recalculations".
hopefully this helps a little further to identify the responsible part of code...
And i readjusted my calibration setting for 1 segment, 0(1) repetitions and single sweep -- but, sorry to write that, with the same results (no change in the S11-smith diagram when I entered different values in the feature "offset".
I fear, I made a simple but powerful mistake during the usage of this feature ...
|
Le 04/12/2019 ¨¤ 20:26, jakefromcf via Groups.Io a ¨¦crit?: 1) Has anyone got the windows exe running under wine? The opening screen launches the GUI OK but crashes when asked to connect. Linux (mint64bit) sees the VNA as TTY0 a symbolic link exists to com1.
2) Trying to build the Linux release but stuck when Python 3.7.4 cannot find pip, seems to be a common problem but the common answers do not resolve this.
Thank You John Knott 2E0KNJ
Hi Work fine on Debian Buster 32 and 64 bits but only after making a virtual environment and for the 32bits versions, copying somes lib by hand (no pyqt5 32 bits)
|
Hi John,
Did you follow the installation instructions here...
Linux release working fine here on Linux Mint 19.2.
73
Nick
|
1) Has anyone got the windows exe running under wine? The opening screen launches the GUI OK but crashes when asked to connect. Linux (mint64bit) sees the VNA as TTY0 a symbolic link exists to com1.
2) Trying to build the Linux release but stuck when Python 3.7.4 cannot find pip, seems to be a common problem but the common answers do not resolve this.
Thank You John Knott 2E0KNJ
|
Re: New version of NanoVNA-Saver: 0.2.1
Hartje,
a little update: If you are running a continuous sweep, the Offset Delay
will *not* be applied. Only for single sweeps of an arbitrary length.
I'll fix this in the next version, of course :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 4 Dec 2019 at 19:39, Rune Broberg <mihtjel@...> wrote: Hello Hartje,
thank you very much for your feedback!
I have used it like you describe, though usually without having set up a
calibration in NanoVNA-Saver itself. There may be an error that prevents it
from functioning as I expected - I will look at it some more. :-)
I agree that it *should* include a loss compensation, but this isn't as
easy as the mathematics for doing a phase shift ;-)
UI placement is a difficult problem. Like you say, some windows are ending
up taller than your screen. I run all my screens at 1920x1200, so I don't
tend to notice if I make the windows too large. I know that if I put
anything more in the main window, it will be too tall for those running
1366x768. All a matter of compromising.
Again, thank you for taking the time to give me feedback on this!
--
Rune / 5Q5R
On Wed, 4 Dec 2019 at 19:20, <hartje@...> wrote:
Dear Rune,
thanks for the new release 0.2.1.
I tried to test the new experimental feature additional extension of
cable length with the linux tar gz on python 3.7 (opensuse, Thumbleweed)
When I have the calibration at the port has been loaded an I connect a
short adapter (length 200 ps) I opened the calibration dialog and added the
200 ps to the special extension of the dialog.
Nothing happens, even when I closed the dialog.
What did I expect from the view of working process?
When I enter a number into the offset dialog, the last measured Smith
diagram will be redrawn with the new calculation of the just entered
extension.
So I am able to optimize the length so that the Smith diagram shows a dot
in the high impedance point. -- As I understood your description.
Let me recommend some more points:
1. I prefer this dialog to be placed in the main window, left column,
below TDR or above analysis
2. I tried to open the last nanaovna-saver versions on Windows 8.1
Surface Pro with screen pixels 1920 x1080. When entering the calibration
dialog, this dialog is larger than the screen and the low er elements are
cut off. -- Am I the only one who mentioned this issue?
3. the new offset should have a phase component (offset time) as well as
an attenuation component. You proposed to use it for "extending the
calibration plane to the end of the cable" -- yes, this will be nice. --
But real cables are lossy cables!
Thanks for this experimental feature. (together with all the other nice
features)
|
Re: New version of NanoVNA-Saver: 0.2.1
Hello Mario,
I don't know how things work on Apple - sorry. Middle mouse to drag things
is used in other apps I use, such as Autodesk Fusion 360. I don't know what
they do on Mac OS, though. Maybe there is a way to do it?
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 4 Dec 2019 at 16:22, Mario Vano <mvano@...> wrote: I can't find it. What do you use for a middle mouse button on a macintosh
if you have an apple two button mouse?
M
|
Re: New version of NanoVNA-Saver: 0.2.1
Hello Wolfgang,
thank you! I hope it's useful for you :-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 4 Dec 2019 at 13:51, Wolfgang Kiefer <woki@...> wrote: Thank you, Rune!
Now also the TDR function is correct and even delivers the impedance as
function of the distance. Great!
Wolfgang, DH1AKF
|
Re: New version of NanoVNA-Saver: 0.2.1
Hello Hartje,
thank you very much for your feedback!
I have used it like you describe, though usually without having set up a
calibration in NanoVNA-Saver itself. There may be an error that prevents it
from functioning as I expected - I will look at it some more. :-)
I agree that it *should* include a loss compensation, but this isn't as
easy as the mathematics for doing a phase shift ;-)
UI placement is a difficult problem. Like you say, some windows are ending
up taller than your screen. I run all my screens at 1920x1200, so I don't
tend to notice if I make the windows too large. I know that if I put
anything more in the main window, it will be too tall for those running
1366x768. All a matter of compromising.
Again, thank you for taking the time to give me feedback on this!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 4 Dec 2019 at 19:20, <hartje@...> wrote: Dear Rune,
thanks for the new release 0.2.1.
I tried to test the new experimental feature additional extension of cable
length with the linux tar gz on python 3.7 (opensuse, Thumbleweed)
When I have the calibration at the port has been loaded an I connect a
short adapter (length 200 ps) I opened the calibration dialog and added the
200 ps to the special extension of the dialog.
Nothing happens, even when I closed the dialog.
What did I expect from the view of working process?
When I enter a number into the offset dialog, the last measured Smith
diagram will be redrawn with the new calculation of the just entered
extension.
So I am able to optimize the length so that the Smith diagram shows a dot
in the high impedance point. -- As I understood your description.
Let me recommend some more points:
1. I prefer this dialog to be placed in the main window, left column,
below TDR or above analysis
2. I tried to open the last nanaovna-saver versions on Windows 8.1 Surface
Pro with screen pixels 1920 x1080. When entering the calibration dialog,
this dialog is larger than the screen and the low er elements are cut off.
-- Am I the only one who mentioned this issue?
3. the new offset should have a phase component (offset time) as well as
an attenuation component. You proposed to use it for "extending the
calibration plane to the end of the cable" -- yes, this will be nice. --
But real cables are lossy cables!
Thanks for this experimental feature. (together with all the other nice
features)
|
Re: New version of NanoVNA-Saver: 0.2.1
Dear Rune,
thanks for the new release 0.2.1.
I tried to test the new experimental feature additional extension of cable length with the linux tar gz on python 3.7 (opensuse, Thumbleweed)
When I have the calibration at the port has been loaded an I connect a short adapter (length 200 ps) I opened the calibration dialog and added the 200 ps to the special extension of the dialog.
Nothing happens, even when I closed the dialog.
What did I expect from the view of working process?
When I enter a number into the offset dialog, the last measured Smith diagram will be redrawn with the new calculation of the just entered extension.
So I am able to optimize the length so that the Smith diagram shows a dot in the high impedance point. -- As I understood your description.
Let me recommend some more points:
1. I prefer this dialog to be placed in the main window, left column, below TDR or above analysis
2. I tried to open the last nanaovna-saver versions on Windows 8.1 Surface Pro with screen pixels 1920 x1080. When entering the calibration dialog, this dialog is larger than the screen and the low er elements are cut off. -- Am I the only one who mentioned this issue?
3. the new offset should have a phase component (offset time) as well as an attenuation component. You proposed to use it for "extending the calibration plane to the end of the cable" -- yes, this will be nice. -- But real cables are lossy cables!
Thanks for this experimental feature. (together with all the other nice features)
|
Re: NanoVNA connected to Amazon Fire tablet
I haven't yet. However I've used it for the DVB-T dongle and other USB
connected items. So I so no reason why not save for you need a program for
Android (fire is Android) and I believe there is see wiki for the address of the google play store.
--
-----------------
I do not accept private email due to forum scraping groups.io
|
Re: NanoVNA connected to Amazon Fire tablet
|
NanoVNA connected to Amazon Fire tablet
|
On Wed, Dec 4, 2019 at 06:47 AM, Larry Rothman wrote: The H version has slight hardware mods but both versions are essentially
identical (except some clones are crap).
Slight mods include better RF shields, onboard v+ filtering, fixed USB-C
interface resistors.? Nothing spectacular. ================================================================================== The NanoVNA-H version also comes in an ABS plastic case that you would have to pay about an additional USA $10 for as an add-on to the Nano-VNA. It has the diode already installed for utilizing the battery voltage icon. The firmware is 0.2.3.2 which is already updated to extend operation to 1500 MHz The price is about the same as the Nano-VNA so value wise it is the better deal. - Herb
|
Re: New version of NanoVNA-Saver: 0.2.1
I can't find it. What do you use for a middle mouse button on a macintosh if you have an apple two button mouse?
M
|
The H version has slight hardware mods but both versions are essentially identical (except some clones are crap).
Slight mods include better RF shields, onboard v+ filtering, fixed USB-C interface resistors.? Nothing spectacular.
ALL firmware version work on ALL hardware versions.
Please read the Firmware section in the Wiki.
...Larry
toggle quoted message
Show quoted text
On Wednesday, December 4, 2019, 9:23:37 a.m. GMT-5, BruceN <k4tql@...> wrote:
Now, my question would be: "What's the difference between the nanoVNA and the nanoVNA-H?? Any difference in the
hardware or is it the firmware?
BruceN
|
Ooops, I spoke to soon. Found the info I needed in an earlier post which, although maybe not up to day by some days, will give a a start. I'll repeat the link here for those who may have missed it also. /g/nanovna-users/message/7477Also found a beginner's guide which will help, too. /g/nanovna-users/topic/64625688BruceN
|
Hi Bruce,
I've been playing/using my NanoVNA since the end of June and have at times, pushed several versions of firmware to it in the span of an hour.
As several users experieinced with programming the particular STM32F072 micro used, it is 'virtually' impossible to brick it as you don't write to the bootloader of the device.?
That said, glitches DO happen and I prepared for that by buying one of the cheap USB STLINK programming dongles mentioned in several prior posts (I got mine from aliexpress for $3 and it works fine).
As for which one to use - you need to experiment with each and find the one that suits your needs - just like with normal PC software applications.
...Larry
toggle quoted message
Show quoted text
On Wednesday, December 4, 2019, 9:20:43 a.m. GMT-5, BruceN <k4tql@...> wrote:
In addition to all the fast and furious releases, it befuddles me as to which version of whose firmware to use.
I've seen several posts about folks bricking their nanovna because they either chose the wrong firmware or
screwed up installing it.
I've read about how to properly install it so I'm not afraid of that.? But, which version to choose?? Does it depend on
what you wish to do with it?? Do some folks find the features given by one better than another?? I haven't found that
comparison as yet.? Or, maybe I missed it.? I do browse the Wiki and it's been a help.
So, my question would be, which one should I start with.
BruceN
|
Kurt Poulsen
Tom Martin
Jim Allyn - N7JA
Oristo