Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Re: edy555 design notes on CALIBRATION sets
Oristo, reference your inductor measurement above, Could you explain how you conducted this test? Did you recal the NanoVNA at each of your measurement ranges? Your test fixture set up isn't really a broad range test fixture. Did you lock down the position of your test clips and leads? I don't remember reading if the Nano firmware stores one single point/frequency calibration value, several over the specified frequency range or 101 points. What did your 51 ohm resistor look like over the 0.1-900 Mhz range after the calibration?
thanks, Jim, KA6TPR |
Re: Which Firmware Version?
Mike,
Did you checkout the user manuals in the "Files" section of this group? Basically there are two methods: 1. If you have the latest firmware installed then there is a new menu option that allows you to perform a screen calibration. 2. If you have the original firmware then you have to connect the NanoVNA to a computer and use a terminal program to perform the calibration. Herb |
Re: Which Firmware Version?
How does one calibrate the screen?
toggle quoted message
Show quoted text
Mike WY6K "... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..." On Wednesday, October 2, 2019, 3:06:18 PM CDT, Larry Rothman <nlroth@...> wrote:
Any time you push new F/W to the device it is good practice to re-cal the touchscreen. Now, with that said, I just updated one of my units and found the touch surface was still calibrated. So - if you see the touch is off at any time - most likely on the menu selections - do a quick cal. Regards,Larry ? ? On Wednesday, October 2, 2019, 3:56:15 p.m. GMT-4, Joe St. Clair <saintc@...> wrote:? Hmm. Can newly installed firmware detect that it has never been touch screen calibrated and automatically start in TOUCH CAL the first time? |
Re: edy555 design notes on CALIBRATION sets
That's a great point.? Testing components, especially inductors, at the intended frequency of use is great.? And the NanoVNA makes it easy - which means I might do actually do it...
toggle quoted message
Show quoted text
Mike WY6K "... somewhere in the distance, there's a tower and a light, broadcastin' the resistance, through the rain and through the night..." On Wednesday, October 2, 2019, 2:12:49 PM CDT, Oristo <ormpoa@...> wrote:
Hi Mike- This was a little unclear to me, but interesting.? Are you saying thatExactly, IMO "calibration" should reflect actual measurement configuration ? Then the data you posted was for that inductor?Yes, one that is very liable to stray pickup. The attached image shows nanoVNA display for a frequency scan, and hopefully visible is an approximating circular segment Smith plot, as reactances should be. While component RLC values at intended application wavelength[s] are obviously of interest, observing Smith plots over a wider range can reinforce credibility or reveal anomalies. Having not been otherwise informed, nanoVNA reports 50 Ohms for that 51 Ohm resistor; I can live with 2% errors... IMO, 5 stored calibrations are none too many. |
NanoVNASaver not running under Linux
John Kemker
Having a problem getting NanoVNASaver to run under Linux Mint (Tessa). Installed the requirements, ran the pip install and get this error message when I try to run it:
NanoVNASaver Traceback (most recent call last): File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 16, in <module> from . import multiarray ImportError: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/NanoVNASaver", line 11, in <module> load_entry_point('NanoVNASaver==0.1.0', 'console_scripts', 'NanoVNASaver')() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 489, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2852, in load_entry_point return ep.load() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2443, in load return self.resolve() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2449, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/local/lib/python3.7/dist-packages/NanoVNASaver/__main__.py", line 23, in <module> from .NanoVNASaver import NanoVNASaver File "/usr/local/lib/python3.7/dist-packages/NanoVNASaver/NanoVNASaver.py", line 24, in <module> import numpy as np File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in <module> from . import add_newdocs File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in <module> from numpy.lib import add_newdoc File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in <module> from .type_check import * File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in <module> import numpy.core.numeric as _nx File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 26, in <module> raise ImportError(msg) ImportError: Importing the multiarray numpy extension module failed. Most likely you are trying to import a failed build of numpy. If you're working with a numpy git repo, try `git clean -xdf` (removes all files not under version control). Otherwise reinstall numpy. Original error was: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py) Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in <module> from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in <module> import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in <module> from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in <module> import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in <module> import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 16, in <module> from . import multiarray ImportError: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/NanoVNASaver", line 11, in <module> load_entry_point('NanoVNASaver==0.1.0', 'console_scripts', 'NanoVNASaver')() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 489, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2852, in load_entry_point return ep.load() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2443, in load return self.resolve() File "/usr/local/lib/python3.7/dist-packages/pkg_resources/__init__.py", line 2449, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/local/lib/python3.7/dist-packages/NanoVNASaver/__main__.py", line 23, in <module> from .NanoVNASaver import NanoVNASaver File "/usr/local/lib/python3.7/dist-packages/NanoVNASaver/NanoVNASaver.py", line 24, in <module> import numpy as np File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in <module> from . import add_newdocs File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in <module> from numpy.lib import add_newdoc File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in <module> from .type_check import * File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in <module> import numpy.core.numeric as _nx File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 26, in <module> raise ImportError(msg) ImportError: Importing the multiarray numpy extension module failed. Most likely you are trying to import a failed build of numpy. If you're working with a numpy git repo, try `git clean -xdf` (removes all files not under version control). Otherwise reinstall numpy. Original error was: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py) Any ideas (Ignore my misspelt message earlier!)? |
Re: NanoVNA-Saver 0.1.0
Larry, thank you very much. I've found it!
toggle quoted message
Show quoted text
Roy WA0YMH On Wed, Oct 2, 2019, 7:05 PM Larry Rothman <nlroth@...> wrote:
Firmware archive in the files section |
Re: NanoVNA-Saver 0.1.0
Firmware archive in the files section
toggle quoted message
Show quoted text
On Wed, 2 Oct 2019 at 7:54 PM, Roy Appleton<twelveoclockhigh@...> wrote: Where can I find a copy of the "CLEAR_MEMORY_DFU" file? Thanks, Roy WA0YMH On Wed, Oct 2, 2019, 6:44 PM Larry Rothman <nlroth@...> wrote:
Bob,You don't need a torque wrench for this device - it's just not that |
Re: NanoVNA-Saver 0.1.0
Where can I find a copy of the "CLEAR_MEMORY_DFU" file?
toggle quoted message
Show quoted text
Thanks, Roy WA0YMH On Wed, Oct 2, 2019, 6:44 PM Larry Rothman <nlroth@...> wrote:
Bob,You don't need a torque wrench for this device - it's just not that |
Re: NanoVNA-Saver 0.1.0
Bob,You don't need a torque wrench for this device - it's just not that critical IMO.?An alternative would be the small 3d printed rings that were discussed a couple of weeks ago.?Also, take the front cover off the display and ensure that the SMA PCB mounts on that side of the board are soldered. Most aren't.?
toggle quoted message
Show quoted text
RegardsLarry On Wed, 2 Oct 2019 at 7:00 PM, Bob Albert via Groups.Io<bob91343@...> wrote: Well Herb I have no idea how to upgrade the firmware.? I do have the sharp program on my PC if that helps. Anyway I am having a blast with this amazing unit.? I can't believe it's basically as good as boat anchor units costing 100 or more times as much.? And even includes a display and cal kit! I was ready to order a different unit from a different vendor but that doesn't appear to be necessary.? I am going to shout from the rooftops about this great instrument. Sure it has its limitations but is wonderful nonetheless.? I am getting displays that, while not totally in agreement with my other gear, still look very believable.? Even the shape of the SWR vs frequency curves are similar to my fancy VNA.? And with the help of the sharp program I can print results. I am still learning about saving and recalling and such.? I have some SMA hardware on order that will simplify some of my testing.? I am still agonizing over the cost of a torque wrench; so far I haven't gotten one. Another impressive characteristic is the accuracy of the frequency.? Putting it into CW mode generates a solid, precise signal.? I wonder about the amplitude; I will see about measuring it on my SA.? Perhaps it will do as a signal generator.? It's well shielded, as I can't hear its signal with nothing connected to it. Bob On Wednesday, October 2, 2019, 03:17:32 PM PDT, hwalker <herbwalker2476@...> wrote:
Bob, If you ever decide to upgrade your firmware you may run into something similar.? My second NanoVNA arrived with only the 2 trace firmware installed.? When I tried to upgrade to the 4 trace firmware it wouldn't take correctly.? The solution was to first install CLEAR_MEMORY_DFU and then install the 4 trace DFU.? Its not always necessary, but I now use it as a matter of course to prevent artifacts left over from the previous install from causing hard to track down problems. Herb |
Re: edy555 design notes on CALIBRATION sets
Hi
toggle quoted message
Show quoted text
Yes that's great that we can now look at all these components to see just how good they are/,were. Carry on and publish your results. We will all be interested I'm sure. A On Thu, 3 Oct 2019, 00:10 alan victor, <avictor73@...> wrote:
Several years ago I investigated potentiometers with the lowest possible |
Re: NanoVNA-Saver 0.1.0
Bob Albert
I just measured about -10 dBm into 50 Ohms at both 100 MHz and 10 MHz.? Not enough to be illegal.
toggle quoted message
Show quoted text
Bob On Wednesday, October 2, 2019, 04:32:43 PM PDT, Alan Lloyd <alanthebass37@...> wrote:
Hmm. I measured 100mV PK-PK into 50 ohms at 50 kHz. My scope drops off at high frequencies (as do all). Output is, of course, a square wave. ? A On Thu, 3 Oct 2019, 00:00 Bob Albert via Groups.Io, <bob91343= [email protected]> wrote: ? Well Herb I have no idea how to upgrade the firmware.? I do have the |
Re: NanoVNA-Saver 0.1.0
Hmm. I measured 100mV PK-PK into 50 ohms at 50 kHz. My scope drops off at
high frequencies (as do all). Output is, of course, a square wave. ? A On Thu, 3 Oct 2019, 00:00 Bob Albert via Groups.Io, <bob91343= [email protected]> wrote: Well Herb I have no idea how to upgrade the firmware. I do have the |
Re: edy555 design notes on CALIBRATION sets
Several years ago I investigated potentiometers with the lowest possible reactance up through 30 MHz. I found the Allen Bradley TYPE J and specifically a 1 k ohm P/N JA1G044P102B exceptionally good.
This pot demonstrated a range of R from nearly a short circuit to 1 k which moved EXACTLY along the real axis on the Smith Chart display of my VNA; swept through 30 MHz. I was amazed of the low parasitic reactance displayed. I'll see if I can find one to sweep and display. Alan |
Re: NanoVNA-Saver 0.1.0
Bob Albert
Well Herb I have no idea how to upgrade the firmware.? I do have the sharp program on my PC if that helps.
toggle quoted message
Show quoted text
Anyway I am having a blast with this amazing unit.? I can't believe it's basically as good as boat anchor units costing 100 or more times as much.? And even includes a display and cal kit! I was ready to order a different unit from a different vendor but that doesn't appear to be necessary.? I am going to shout from the rooftops about this great instrument. Sure it has its limitations but is wonderful nonetheless.? I am getting displays that, while not totally in agreement with my other gear, still look very believable.? Even the shape of the SWR vs frequency curves are similar to my fancy VNA.? And with the help of the sharp program I can print results. I am still learning about saving and recalling and such.? I have some SMA hardware on order that will simplify some of my testing.? I am still agonizing over the cost of a torque wrench; so far I haven't gotten one. Another impressive characteristic is the accuracy of the frequency.? Putting it into CW mode generates a solid, precise signal.? I wonder about the amplitude; I will see about measuring it on my SA.? Perhaps it will do as a signal generator.? It's well shielded, as I can't hear its signal with nothing connected to it. Bob On Wednesday, October 2, 2019, 03:17:32 PM PDT, hwalker <herbwalker2476@...> wrote:
Bob, If you ever decide to upgrade your firmware you may run into something similar.? My second NanoVNA arrived with only the 2 trace firmware installed.? When I tried to upgrade to the 4 trace firmware it wouldn't take correctly.? The solution was to first install CLEAR_MEMORY_DFU and then install the 4 trace DFU.? Its not always necessary, but I now use it as a matter of course to prevent artifacts left over from the previous install from causing hard to track down problems. Herb |
Re: NanoVNA-Saver: Testers wanted
Hello Rune,
If you haven't done so already, please add my name to your list of Alpha testers if you would like. I will be testing on a Dell Laptop computer running Windows 10 and an iMac under Mojave 10.14.6. I understand that this is a chance to test for program bugs and not recommend new features. I agree. I do believe the it's time to nail down at least one foot. That way you can only run in a small circle! Thanks for all the work you've done on this incredible project. Larry |
Re: NanoVNA-Saver 0.1.0
Bob,
If you ever decide to upgrade your firmware you may run into something similar. My second NanoVNA arrived with only the 2 trace firmware installed. When I tried to upgrade to the 4 trace firmware it wouldn't take correctly. The solution was to first install CLEAR_MEMORY_DFU and then install the 4 trace DFU. Its not always necessary, but I now use it as a matter of course to prevent artifacts left over from the previous install from causing hard to track down problems. Herb |
Re: edy555 design notes on CALIBRATION sets
I made a page about this:
Basically, unbalanced bridge sensitivity is non-linear; for bridges balanced @ 50 Ohms, signal amplitude difference from 0 to 50 is the same as from 50 to 150. Signal change from 500 to 1000 Ohms is only 10% of change from 0 to 1000 Ohms, so far more sensitive near 50 Ohms, and "calibrating" with a different LOAD does not help. |
Re: Installed recent firmware - was this a big mistake?
In reality, USB does not work that way. Here are "real" supported USB speeds:
USB 1.0/Low-Speed: 1.5 Megabits per second (Mbps) USB 1.1/Full-Speed: 12 Mbps. USB 2.0/Hi-Speed: 480 Mbps. USB 3.0/SuperSpeed: 5 Gbps. USB 3.1/SuperSpeed: 10 Gbps. Setting some bps is supported for virtual COM (AKA CDC device) to chips (e.g. FTDi) at the other end which interface USB to real serial (RS-422 or 232 or whatever).. There is no such interface at the STM32 chip in nanoVNA,. Speed is determined by which USB speed gets negotiated at plugin detection time and buffer sizes implemented. |
to navigate to use esc to dismiss