Hi Larry,
you're right - the application still thinks at that point that the NanoVNA
is connected - despite having just received an error that it was
disconnected. It should probably just disconnect when it gets the error.
I'll put it on the list of little niggles ;-)
Thanks for the feedback!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 2 Oct 2019 at 19:10, Larry Rothman <nlroth@...> wrote: Hi Rune,There is a small bug in the serial connect routine.If I disconnect
the Nano while scanning, I get the pop-up error and that's OK.If I then
click on the Rescan button, the selected serial port disappears but the
button underneath still shows "Disconnect".I think if there is no serial
port shown, that should be reset as there is no recovery that I can see -
'Saver just hangs.
Regards,Larry
|
I saw this
Thought might be of interest to some.
72
Dom
M1KTA
|
Re: edy555 design notes on CALIBRATION sets
On Mon, Jul 29, 2019 at 11:59 AM alan victor wrote: if you desire to use the nanoVNA as a component measurement tool, like an LCR meter, conduct your measurments at say 1 MHz or even 50 kHz! OSL calibration and measurement for alligator clips, using axial lead 51 Ohm resistor LOAD 23 Ohms 7 uH @ 0.1 MHz 5.5 Ohms 6.6uH @ 1 MHz 40 Ohms 400mH @ 10-100MHz 57 Ohms 900pH @500-900MHz Actual measurements had more separation between DUT and nanoVNA than shown in image hopefully attached; it matters particularly for air-wound coils... LCR measurement <>
|
Hi Rune,There is a small bug in the serial connect routine.If I disconnect the Nano while scanning, I get the pop-up error and that's OK.If I then click on the Rescan button, the selected serial port disappears but the button underneath still shows "Disconnect".I think if there is no serial port shown, that should be reset as there is no recovery that I can see - 'Saver just hangs.
Regards,Larry
|
Re: More comparisons of NanoVNA and Keysight analyzer
On the AIM-4170D PC SW, the y=0 axis is also used for resistance and reactance on the same graph as SWR so here is what it usually looks like:
|
Hi Nick,
this looks ... interesting.
The Gtk error isn't something I have any control over - it seems to be your
Window Manager (at a guess?) or local Qt implementation that's using Gtk
for its popups. It looks like a bug, but possibly not one I can fix...
The dialog window for saving gets the following instruction in the code:
filedialog.setDefaultSuffix("cal")
This is supposed to set the default suffix to be added if no other suffix
is provided, and it does on Windows at least. ;-)
So sadly it looks a bit like Linux-specific Qt errors. (Or, of course,
that I'm using it incorrectly, and it randomly happens to work on Windows.
Both are likely! ;-)
Thanks for getting back to me on this though, it's a very interesting
problem!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 2 Oct 2019 at 18:49, Nick <g3vnc@...> wrote: Here's the console output when when I hit the load cal button...
nick@LM19-2:~$ python3.7 ./nanovna-saver/nanovna-saver.py
NanoVNASaver 0.1.0
Copyright (C) 2019 Rune B. Broberg
This program comes with ABSOLUTELY NO WARRANTY
This program is licensed under the GNU General Public License version 3
See for further details
Settings: /home/nick/.config/NanoVNASaver/NanoVNASaver.ini
Gtk-Message: 17:32:47.985: GtkDialog mapped without a transient parent.
This is discouraged.
I get the same Gtk-Message when I save a cal with or without the .cal
extension.
The cal files become visible if I give them a .cal extension. Files
without the .cal extension are not visible in the object picker even when
All Files is selected e.g. bnc_1 and bnc_2 are not visible to the object
picker because they do not have the .cal extension.
It is possible to save a cal file without the .cal extension in which case
it is hidden from the object picker.
Perhaps the save dialog should force a .cal extension e.g. by adding it
automatically to the Name field?
73
Nick
|
Here's the console output when when I hit the load cal button...
nick@LM19-2:~$ python3.7 ./nanovna-saver/nanovna-saver.py
NanoVNASaver 0.1.0
Copyright (C) 2019 Rune B. Broberg
This program comes with ABSOLUTELY NO WARRANTY
This program is licensed under the GNU General Public License version 3
See for further details
Settings: /home/nick/.config/NanoVNASaver/NanoVNASaver.ini
Gtk-Message: 17:32:47.985: GtkDialog mapped without a transient parent. This is discouraged.
I get the same Gtk-Message when I save a cal with or without the .cal extension.
The cal files become visible if I give them a .cal extension. Files without the .cal extension are not visible in the object picker even when All Files is selected e.g. bnc_1 and bnc_2 are not visible to the object picker because they do not have the .cal extension.
It is possible to save a cal file without the .cal extension in which case it is hidden from the object picker.
Perhaps the save dialog should force a .cal extension e.g. by adding it automatically to the Name field?
73
Nick
|
Hi Bryan, thanks for the feedback! The code used is the same for S11 and S21 charts of the same type, such as the return loss/gain charts - so the errors end up being the same ;-) Thanks for checking in any case! Early aim for next release is early next week. It depends how many features I try to push into it. ;-) -- Rune / 5Q5R On Wed, 2 Oct 2019 at 18:15, bryburns via Groups.Io <bryburns= [email protected]> wrote: Rune,
Thanks for the new release. Keep up the great work.
I see the same issue with S11 return loss in dB.
I do not see it in the phase plots.
--
Bryan, WA5VAH
On Wed, Oct 2, 2019 at 09:06 AM, <norbert.kohns@...> wrote:
Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after
calibration
right on the 0 dB line and on the current version somewhat below the 0 dB
line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Hello Brian, thanks for trying out the software! :-) I do not read from or save to the NanoVNA calibration locations. Currently, my recommendation is that users calibrate the NanoVNA across the full span of 50kHz-900 or 1500MHz, depending on version, with whatever attached hardware (cables, adaptors) they are going to use, and save this as calibration memory 0. This will ensure that the data transmitted to NanoVNA-Saver is at least reasonable looking, and won't fall foul of the bits of code that try to detect transmission errors. Calibration within the application itself can be saved to calibration files. Currently, the calibration set used (for those users using custom characterized sets) is not saved in the calibration file, but has to be set manually in the interface. This method allows the use of many more data points for calibrating within the application. I've used as many as 5050 (= 50 "segments") at one point. This higher resolution cannot be achieved using the NanoVNA's built in memories. I hope this explains why it's currently not possible? Thanks again for taking the time to try out my software :-) -- Rune / 5Q5R On Wed, 2 Oct 2019 at 17:22, brianbgarber via Groups.Io <brianbgarber= [email protected]> wrote: Hi Rune,
Thanks for your development efforts! I have a quick question about saving
calibration data; can you read from / save to memory locations on the
NanoVNA?
73, Brian WB8AM
|
That's actually a good point.? However, the AD4350 only goes down to 137 MHz.? So unless they have done something creative to extend that range down lower, you will need BOTH V1 and V2 if you want to include HF.
Mike WY6K
"... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..."
toggle quoted message
Show quoted text
On Wednesday, October 2, 2019, 9:20:36 AM CDT, Oristo <ormpoa@...> wrote: On Mon, Sep 30, 2019 at 12:24 PM, mike watts wrote: Or, they might be dumping inventory to get liquidity. Manufacturers may be aware that V2 is coming, at which point V1 will be a hard sell.
|
Rune,
Thanks for the new release. Keep up the great work.
I see the same issue with S11 return loss in dB.
I do not see it in the phase plots.
--
Bryan, WA5VAH
toggle quoted message
Show quoted text
On Wed, Oct 2, 2019 at 09:06 AM, <norbert.kohns@...> wrote:
Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after calibration
right on the 0 dB line and on the current version somewhat below the 0 dB
line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Hi Norbert,
thanks for the bug report! I can tell you that the data points are drawn
where they should be, but the reference lines are 10 pixels offset. Whoops!
I've fixed it on GitHub, and the fix will be in the next release as well.
Thanks again for your help!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 2 Oct 2019 at 17:06, <norbert.kohns@...> wrote: Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after calibration
right on the 0 dB line and on the current version somewhat below the 0 dB
line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Hi Bill, The .exe file should work just fine on Windows 10. First startup can take a little while, maybe 10-20 seconds, but after that it should run fine. What happens when you try to start it? -- Rune / 5Q5R On Wed, 2 Oct 2019, 17:19 bill wright via Groups.Io, <chief6226= [email protected]> wrote: Is there a trick to get the 0.1. version .exe to work. I am on a win 10.
machine. Is thisa linux .exe? the other two version unload and install and
work well w10 no.I tried to unload the zip file but do not find an .exe
fileplease adviseBill kd5yyk
On Wednesday, October 2, 2019, 10:06:42 AM CDT,
norbert.kohns@... <norbert.kohns@...> wrote:
Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after calibration
right on the 0 dB line and on the current version somewhat below the 0 dB
line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Re: How we use the Nanovna
These are nice little instruments !!Thanks for the update.
toggle quoted message
Show quoted text
On Wednesday, October 2, 2019, 11:32:52 a.m. GMT-4, Warren Allgyer <allgyer@...> wrote:
Larry
Not very much actually. It was calibrated at the 100 MHz span and then I reduced the span to 50 MHz without recalibration in order to get better resolution. At these levels I am not concerned about absolute values but more about where the null occurs.
But, to specifically answer your question, this is what it looks like when calibrated for this specific test range.
|
Re: How we use the Nanovna
Larry
Not very much actually. It was calibrated at the 100 MHz span and then I reduced the span to 50 MHz without recalibration in order to get better resolution. At these levels I am not concerned about absolute values but more about where the null occurs.
But, to specifically answer your question, this is what it looks like when calibrated for this specific test range.
|
Hi Rune,
Thanks for your development efforts! I have a quick question about saving calibration data; can you read from / save to memory locations on the NanoVNA?
73, Brian WB8AM
|
Is there a trick to get the 0.1. version .exe to work.? I am on a win 10. machine. Is thisa linux .exe?? the other two version unload and install and work well w10 no.I tried to unload the zip file but do not find an .exe fileplease adviseBill kd5yyk
toggle quoted message
Show quoted text
On Wednesday, October 2, 2019, 10:06:42 AM CDT, norbert.kohns@... <norbert.kohns@...> wrote:
Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after calibration right on the 0 dB line and on the current version somewhat below the 0 dB line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Re: Quick Tips for New Users
Hi Kurt,
Thank you, I look forward to your report.
With regards,
Bob
|
Hi Rune,
thanks for the software update and for the additional features!
One issue I recognized: S21 is with the previous version after calibration right on the 0 dB line and on the current version somewhat below the 0 dB line.
Am I doing something wrong with the new version?
Kind regards
Norbert, DG1KPN
|
Re: How we use the Nanovna
Very interesting! Thanks for sharing!
Roy
WA0YMH
toggle quoted message
Show quoted text
On Wed, Oct 2, 2019, 9:53 AM Warren Allgyer <allgyer@...> wrote: Here I am working on a circularly polarized 440 MHz antenna for satellite
ops. The first screenshot shows initial results when it was first
connected. The second trace is after tuning. To be able to see Return Loss
and the Smith Chart at the same time, in real time, was invaluable in
getting this thing corralled.
Next step: build a second one and phase them to give me a 2 bay CP
transmit antenna with 0 dBi gain. Exactly what I wanted.
WA8TOD
|
Oristo
WY6K Mike Watts
Warren Allgyer
Brian Garber
bill wright
