Re: gnuplot for nanoVNA Touchstone files
it probably wouldn't be a huge effort to build a Python command-line tool .. so now I must confess failing to obtain consistent results verifying NanoVNA-Saver Python prerequisites on Windows 8.1 .. and have a collection of crash reports to show for it. From ... I tried this discouraging example: #!/usr/bin/python import sys print 'Number of arguments:', len(sys.argv), 'arguments.' print 'Argument List:', str(sys.argv) --------------------------------------- C:\Users\ormpoa>py - < args.py File "<stdin>", line 5 print 'Number of arguments:', len(sys.argv), 'arguments.' ^ SyntaxError: invalid syntax .. which was fixed by surrounding print args with parens, but still.. C:\Users\ormpoa>pipenv run python nVargs.py info Number of arguments: 2 arguments. Argument List: ['nVargs.py', 'info'] info Kernel: 4.0.0 Compiler: GCC 8.2.1 20181213 (release) [gcc-8-branch revision 267074] Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices Board: NanoVNA-H Build time: Oct 9 2019 - 10:20:33
|
Re: Calibration kit from Ebay
I searched for calibration kits and perhaps SMA calibration kits. I looked carefully that the connector can be tightened without turning the inner center pin.
Example
|
Re: Firmware upgrade - Touchscreen not working
Today I got the same issue. It happens after attempt to remove air bubbles under protection film.
After all I fixed it, the root of cause is LCD protection film.
Try to unstick protection film and stick it back.
|
Can the nanoVNA act as a vector voltmeter?
Can the nanoVNA be used as a vector voltmeter? Connect two sources and measure ratio B/A and phase B-A.
|
Guidelines for SWR 1:1.5 and 1:2 in SWR graph
Is it possible to get distinguishable guidelines for SWR 1:1.5 and 1:2 on SWR graph?
That would be very helpful for visualization of SWR measurements (acceptable SWR bandwidth for example).
|
Re: gnuplot for nanoVNA Touchstone files
If you just want Touchstone files, NanoVNA-Saver was actually, as the name
implies, built to save Touchstone files. ;-) Not easily automated, though
it probably wouldn't be a huge effort to build a Python command-line tool
to do so.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Fri, 18 Oct 2019 at 20:52, Oristo <ormpoa@...> wrote: link added to application notes
/g/nanovna-users/wiki/Application-Notes nanoVNA shell commands `frequencies` and `data` naturally return columns
of numbers,
so nearly Touchstone format.
The unix utility `paste` trivializes combining text file columns,
and while it is not too tricky to store PuTTY log files,
then edit those logs into files appropriate for `paste`,
that is not easily scripted. As Dr. David noted,
"being able to generate all the PDF plots from a single unix shell script
makes the process much easier".
One challenge is that Windows seemingly lacks a native utility comparable
to Unix `paste`,
but `paste` is available e.g. by Cygwin, Windows Subsystem for Linux (WSL)
or MSYS2
WSL is an option neither for Windows 7 nor 8, and Cygwin is rather
extensive.
MSYS2 `paste.exe` may be already available e.g. if some Ruby is installed,
and appears the least invasive well-supported.
Another challenge is communicating with nanoVNA's virtual COM port from
scripts;
that works for me on Windows 8.1 so far neither from Cygwin nor cmd.exe...
Suggestions are invited; ideally, a utility is wanted that
sends command line arguments in sequence to nanoVNA,
then returns data from the final argument until nanoVNA returns "ch>".
|
Re: gnuplot for nanoVNA Touchstone files
link added to application notes
/g/nanovna-users/wiki/Application-Notes nanoVNA shell commands `frequencies` and `data` naturally return columns of numbers, so nearly Touchstone format. The unix utility `paste` trivializes combining text file columns, and while it is not too tricky to store PuTTY log files, then edit those logs into files appropriate for `paste`, that is not easily scripted. As Dr. David noted, "being able to generate all the PDF plots from a single unix shell script makes the process much easier". One challenge is that Windows seemingly lacks a native utility comparable to Unix `paste`, but `paste` is available e.g. by Cygwin, Windows Subsystem for Linux (WSL) or MSYS2 WSL is an option neither for Windows 7 nor 8, and Cygwin is rather extensive. MSYS2 `paste.exe` may be already available e.g. if some Ruby is installed, and appears the least invasive well-supported. Another challenge is communicating with nanoVNA's virtual COM port from scripts; that works for me on Windows 8.1 so far neither from Cygwin nor cmd.exe... Suggestions are invited; ideally, a utility is wanted that sends command line arguments in sequence to nanoVNA, then returns data from the final argument until nanoVNA returns "ch>".
|
Re: Owen Duffy on improvised test fixtures
#test-jig
Hi Jeff, I take a different approach to the test fixture, Mine in a copper sheet between a pair of PCB mount male connectors with alligator clips to the DUT. Since most of my work in <100 MHz, it works for me. I get a good 50 dB isolation. Mel, K6KBE On Fri, Oct 18, 2019 at 11:33 AM Jeff Anderson <jca1955@...> wrote: Bruce, I completely agree. Rune¡¯s code is available to all of us. If
there¡¯s something I¡¯d like to see added (and there are two small mods), I
look at it as an excellent reason to learn Python and make the mods myself.
- Jeff, k6jca
|
Re: Owen Duffy on improvised test fixtures
#test-jig
Bruce, I completely agree. Rune¡¯s code is available to all of us. If there¡¯s something I¡¯d like to see added (and there are two small mods), I look at it as an excellent reason to learn Python and make the mods myself.
- Jeff, k6jca
|
I agree, I look at changes I make as "WHAT IF" that way, I don't mess things up. However, when a good thing happens, I always recal.........Then save with new name. Mel, K6KBE On Fri, Oct 18, 2019 at 11:27 AM Maurizio IZ1MDJ <redifon500@...> wrote: Hi Nick , my suggestion is that the " save calibration " , save also the
state of the instruments , like all the vna i know.
If you , change some sweep parameter with the calibration applied , it's
ok to put a warning at the operator that the currently calibration may be
not valid.
Sincerely I don't understand what is the convenience to mantain sweep
setup that my be not agree with the calibration.
Of course this is my opinion.
Best Regards
Maurizio IZ1MDJ
On Fri, Oct 18, 2019 at 03:39 PM, Nick wrote:
Hi Rune
I would not expect measurements made outside of the frequency range of
the
current calibration to be "accurate".
I would not want nvna-s to change the sweep setup when a calibration is
loaded. But I might expect to be reminded.
Having loaded a calibration how about warning the user if they try to make
measurements outside the calibrated frequency range?
e.g. by flashing up an out of calibration message box, watermarking the plots
etc.
73
Nick
On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:
I agree that calibrations should save the start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever
frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?
|
Hi Nick , my suggestion is that the " save calibration " , save also the state of the instruments , like all the vna i know.
If you , change some sweep parameter with the calibration applied , it's ok to put a warning at the operator that the currently calibration may be not valid.
Sincerely I don't understand what is the convenience to mantain sweep setup that my be not agree with the calibration.
Of course this is my opinion.
Best Regards
Maurizio IZ1MDJ
toggle quoted message
Show quoted text
On Fri, Oct 18, 2019 at 03:39 PM, Nick wrote:
Hi Rune
I would not expect measurements made outside of the frequency range of the
current calibration to be "accurate".
I would not want nvna-s to change the sweep setup when a calibration is
loaded. But I might expect to be reminded.
Having loaded a calibration how about warning the user if they try to make
measurements outside the calibrated frequency range?
e.g. by flashing up an out of calibration message box, watermarking the plots
etc.
73
Nick
On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote:
I agree that calibrations should save the start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?
|
Re: Abbreviated documentation for more simplistic tasks?
An excellent idea.
Someone new to VNA's and what a complex impedance is will be overwhelmed
if told to check the wiki, all the forum posts, and read some Agilent document.
They just want to measure their antenna's SWR (they think).
Or maybe sweep a filter.
A first document should tell them that without having to first wade through a lot of new material.
We need a single document that tells how to charge it, turn it on, configure it to show SWR
and complex impedance, and then sweep across a range of frequencies.
How to measure that filter.
How to deal with the user interface, what parts of the menu structure they can ignore,
If ambitious, further sections of this document could give a primer on what a complex impedance is.
When calibration might be a good idea.
What a reference plane is.
Maybe set up a few example exercises, using a 100 pF cap and a 100 ohm resistor so the parts are likely on hand.
Keep the frequency fairly low so it's easy to reproduce.
Show them how to measure these parts in various configurations, and what results to expect.
Perhaps add a hand wound inductor to the mix.
And what happens when this stuff is put on the end of 25 feet of cheap RG79 coax.
An appendix with links into other documents with a brief description of what can be found there.
Things like transmission line theory, impedance matching, Smith charts, S parameters.
Jerry, KE7ER
|
Re: Possible Issue with ttrftech firmware (0.2.3-11) above 300 mhz
AA6KL,
Thanks for the info and tips, I was successful in clearing the config and saving the cleared config to slot 0. Re-calibrated the device, and there was still no change with the smith chart above 300 mhz.
Firmware verison 0.1.1 is fine above 300 mhz, and anything above 0.1.1 causes the issue. So i still going back on the firmware is the issue (at least on my device).
|
What is The Best calibrati¨®n for NanoVna???
Hello friends! very good day, what is the best way to make the best NanoVNA calibration since I have seen several videos of NanoVNA users that make them in different ways on YouTube and I don't know which one is the best and the most appropriate! Is there any kind of tutorial to do it ??? best regards! 73s
|
Hello Rune- Thanks for the fantastic software! I built an 11-pole 500 kHz Low Pass Chebyshev filter using AADE Filter Design software back in 2010 for use with a Softrock LF Ensemble II SDR kit. It seemed to work as expected, but with NanoVNA and NanoVNA-Saver I was finally able to do a 'proper' analysis- see the attached images. Also, thank you Hugen and edy555 for the fantastic hardware! 73, Joe F. KC8RKL <posting this a 2nd time, as the .png images originally attached showed errors in the groups.io web interface>
|
Re: Can't update firmware
As with re-calibration or after a firmware upgrade, you will first perform a Reset and then perform a calibration step by step (if you make a mistake, it will start over again).
So here too, the faulty driver must be removed first and then the new driver installed. (or use the installation wizard.)
Anyone who can ask well knows the answer already :-)
|
Re: Owen Duffy on improvised test fixtures
#test-jig
It's been my experience that those who can, do. Those who can't, criticize. I'm sure Rune would appreciate suggestions as to how to improve his software. But, at least he gave us a start. It's up to us to help develop the application.
My nickel's worth.
Bruce Nebergall / K4TQL
|
Hi Rune
I would not expect measurements made outside of the frequency range of the current calibration to be "accurate".
I would not want nvna-s to change the sweep setup when a calibration is loaded. But I might expect to be reminded.
Having loaded a calibration how about warning the user if they try to make measurements outside the calibrated frequency range?
e.g. by flashing up an out of calibration message box, watermarking the plots etc.
73
Nick
toggle quoted message
Show quoted text
On Thu, Oct 17, 2019 at 08:04 PM, Rune Broberg wrote: I agree that calibrations should save the start/stop/segments/averaging.
It's a great point. I don't know if I want to overwrite whatever frequency
span the user has set up when they load the calibration, though. It's a
matter of doing what the user expects, and I'm not sure I would expect
loading a calibration to change my sweeping setup?
|
Re: errors of "error" models
#57 : ann : [LeastVNA] ~ [NanoVNA] later today 57#
|
Re: errors of "error" models
Dr. David Kirkby from Kirkby Microwave Ltd
On Fri, 18 Oct 2019 at 11:43, yza <yzaVNA@...> wrote: #55 : just because this is research in progress : #55 Many people report work that¡¯s in progress, but report it in a way others can at least see what is the aims of the work. The title should give some indication of what the work is about, but even your title is confusing. I just did a search for ¡°amplifier work in progress¡± Here are the first two links I found. I did not read any more than the first paragraph of each, but they are at least presented in a way that others can follow. despite they are a work in progress. Here is a description for children on how to make graphs. We see a title on the graph, the x axis is the year, the y-axes is the population. I don¡¯t know at what age graphs are taught to children in the UK, but I am sure by the age of 14, children would know that you need to put labels on the axes! It is such a basic thing, yet you don¡¯t even label the axes! When I write software, even if just for my own use, I will put at least some comments in the code. Have you considered putting your work onto a webpage, that people could read and understand without clicking links? Have you considered writing it like a basic scientific report? Earlier I wrote that I would try to correct the English if you could write the work in an understandable way. That offer still stands. Dave. -- Dr. David Kirkby, Kirkby Microwave Ltd, drkirkby@... Telephone 01621-680100./ +44 1621 680100 Registered in England & Wales, company number 08914892. Registered office: Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United Kingdom
|
Oristo
YT9TP - Pedja
Gyula Molnar
gin&pez@arg