Re: New version of NanoVNA-Saver: 0.2.1
Thanks the new version, experimential port extension very good news.
Of course, loss compensation option(s) requied too. But math not easy, now next entry level is easy. Good start point to advanced math.
For simple lossless port extension only required the delay. But have many way to get this. Simplest, everything is unkown, simply try and see what happen is change the delay.
If you know port extension physical lenght and velocity factor, delay easy computable. Try it, and fine tune with small delay value change. Delay, physical lenght, and velocity factor easy compute, if you know two of them. Many instrument, manuals use different method to set delay. Many uses the delay, others use electrical lenght (millimeters) and velocity factor = 1. Others use mechanical lenght (millimeters) + true velocity factor (for example 0,66).
Another differencies, some instrument use one way delay, some use two way delay. The signal from instrumnet travel to port extension end (one way delay), now if not ideally terminated, the part of signal reflected back to instrument (two way delay).
I suggest there input, delay, velocity factor, lenght. Simple check box useful (one or two way delay). More elegant, settings for delay picoseconds, nanoseconds. To lenght in millimeters, centimeters, meters, feet, inches.
If you not know the lenght or delay, and the coaxial line terminated by complex antenne or not, many times useful the tdr lenght to delay compute. Not easy the simple delay guess on real antenna + coaxial cable. TDR help a lot.
Many times good result with antenna, but sometimes fail. If you think your line between 30 to 60 meters, and you get 49,68 meter no big problem. If you get outside, something is wrong. If you disconect the far end of cable, you will have good value. If impossible disconnect, try short the antenne.
Example, 1000.000mm lenght velocity factor 1 coax cable one way delay:
1000.000/0.299792458/1 = 3335.641 picoseconds
Example, 1000.000mm lenght velocity factor 0.700 coax cable one way delay:
1000.000/0.299792458/0.700 = 4765.200 picoseconds
0.299792458 = light speed constans
Next level the loss compensation.
|
Re: NanoVNA-Q out of memory while compiling
I tested it on arm-none-eabi-gcc (15:4.9.3+svn231177-1) 4.9.3 20150529 (prerelease)
The latest github version can fit into memory with all commands enabled, just out of the repository.
|
Re: New version of NanoVNA-Saver: 0.2.1
On Wed, Dec 4, 2019 at 03:09 PM, Kurt Poulsen wrote: Kurt and Rune, I found the same thing as Kurt. I had to multiply the delay by 10. I have connector savers on my NanoVNA. They add a delay of 52 ps. as reported by Dave Kirby in an earlier post. I had to enter -520 to get the short and open to go to the two extremes on on the Smith Chart horizontal axis. Roger
Hi Rune
The dealy to enter is by a factor of ten. E.g. if the measurement plane has to
be shifted backward to the calibration plane by 50.7ps the I must enter -507ps
and this the sign is Ok.
I used the calibration with two testcables and calibrated with the female kit
setting and left the thru adaptor positioned (I had created a calibration kit
file and used it)
Kind regards
Kurt
|
Re: NanoVNA-Q out of memory while compiling
Well, if this is only for your own personal use, I would suggest you can begin removing all the help text and associated code, incuding the info text.??
Afterall, you already know how to use the commands, right???
... Larry
On Wed, 4 Dec 2019 at 6:50 PM, Lapo Pieri<ik5nax@...> wrote: Hi,
I got this:
.....
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: build/ch.elf section `.data' will not fit in region `flash0'
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: region `flash0' overflowed by 208 bytes
collect2: error: ld returned 1 exit status
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:243: build/ch.elf] Error 1
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:7-2018-q2-6+b1) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]
How could I fix it?
Many thanks
Lapo
|
Re: NanoVNA connected to Amazon Fire tablet
There is no need to download from the Play Store.?
Go to GitHub/cho45 and download the release directly from the releases section then sideload it on the Fire tablet.?
Here's the link:.? ?
You will get updates faster from here than from Play.?
On Wed, 4 Dec 2019 at 6:03 PM, k9wkj<k9wkjham@...> wrote: find some instructions to install the Google Play Store on your Fire
then install the NanoVNA app right from the Play store
profit!!
used it on a repeater site last week again
|
Re: Software Quits Working...
That doesn't happen here.? Perhaps it's the version you are using.
Bob
toggle quoted message
Show quoted text
On Wednesday, December 4, 2019, 04:00:39 PM PST, Chuck Carpenter <w5usj@...> wrote:
...right after starting up.
I'm thinking that the VNA might need to be connected when booting the software?
The VNA white version is purchased but delivery is a week or so away.? I'd thought I might get a look at the software while waiting...8^(
|
NanoVNA-Q out of memory while compiling
Hi,
I got this:
.....
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: build/ch.elf section `.data' will not fit in region `flash0'
/usr/lib/gcc/arm-none-eabi/7.3.1/../../../arm-none-eabi/bin/ld: region `flash0' overflowed by 208 bytes
collect2: error: ld returned 1 exit status
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:243: build/ch.elf] Error 1
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (15:7-2018-q2-6+b1) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]
How could I fix it?
Many thanks
Lapo
|
I have a problem that the 5V input to the vna is shorted.? ?I cannot charge the battery.? So I tried charging the battery from a power supply and all works ok.
I opened the unit and unsoldered the connector, USB.? I tested and the connector is not shorted.
Now I find the vna no longer accepts power.? Perhaps there is a jumper inside the connector I removed.
This connector is so small I don't see how to reinstall it.
The schematic diagram of the VNA shows no USB connector that I can find so that I can manage to operate the unit.? I would not care if it uses this connector; I can put something else on, and sacrifice the communication port feature.
Can someone explain where to apply 5V so as to get the unit operational again?? There are many pins to this connector, more than I thought would be needed to function.? If I knew which pads to connect to external 5V I could do that and it would be sufficient for my needs.
Bob
toggle quoted message
Show quoted text
On Tuesday, November 26, 2019, 10:59:17 AM PST, Bob Albert via Groups.Io <bob91343@...> wrote:
Will this work?
Wholesale USB 2.0 USB-C Type C Male To Female USB A Adapter OTG Data Sync Cable | eBay
|
|
|
| $1.10 |? |
|
|
|
|? |
Wholesale USB 2.0 USB-C Type C Male To Female USB A Adapter OTG Data Syn...
USB3.1 Type-C male to USB3.0 female OTG data cable for Google Pixel C,for Nokia. With OTG Data function. 1 x USB...
|
|
|
? ? On Tuesday, November 26, 2019, 10:36:00 AM PST, vbifyz <3ym3ym@...> wrote:?
My unit has a problem with both the supplied cable and the connector itself. With the supplied USB-C cable it almost never connects to the PC, but charging is ok.
With a better quality cables it connects about 50% of the time (in both orientations), and loses connection easily if I move it around.
Answering the original question: The cable to search is "USB Type-C to USB-A 2.0 Male". Don't buy the cheapest ones. You don't need more expensive high speed 3.0 cables either.
|
Re: New version of NanoVNA-Saver: 0.2.1
Hi Rune The dealy to enter is by a factor of ten. E.g. if the measurement plane has to be shifted backward to the calibration plane by 50.7ps the I must enter -507ps and this the sign is Ok. I used the calibration with two testcables and calibrated with the female kit setting and left the thru adaptor positioned (I had created a calibration kit file and used it) 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
|
Re: NanoVNA connected to Amazon Fire tablet
find some instructions to install the Google Play Store on your Fire
then install the NanoVNA app right from the Play store
profit!!
used it on a repeater site last week again
|
Tom, the nanoVNA goes to 1500 MHz.? Just key in that frequency in the Stimulus menu.
BobK6DDX
toggle quoted message
Show quoted text
On Wednesday, December 4, 2019, 02:28:26 PM PST, Tom Martin <thomas.martin@...> wrote:
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
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
|
Roger Need
Kurt Poulsen
Tom Martin
Jim Allyn - N7JA