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: How does VNA get the phase angle of S11
You have the test signal from the SI5351 send to the bridge but also to the "reference" mixer, in the reference mixer it is mixed with the output of the Local Oscillator (LO) which also comes from the SI5351.
The unbalance of the bridge goes to the "reflection" mixer where it is mixed with the same LO. The LO is at 5kHz offset from the test signal so the output of both mixers is a IF signal at 5kHz. Both IF's are then read into the controller using the ADC and in a DSP algorithm in the controller the IF's are going to DSP mixers where they are mixed with two 5kHz signals 90 degrees apart (I/Q mixer) to create a DC signal. The DC signals (I and Q) are the real and imaginary part of the complex downconverted reference and reflection input to the HW mixers. As you do not know the actual angle of amplitude of the test signal the complex test signal is divided by the complex reference signal to eliminate the phase and amplitude uncertainty. The outcome of this division is the unbalance of the bridge scaled relative to the reference signal, both in magnitude and angle. Attached a small pdf that contains the block diagram of a VNA using the same mechanism |
Is my Nanovna broken?
I cannot get this to work on startup using nanosaver and I get in the logfile ...
2019-10-03 07:33:37,745 - NanoVNASaver - INFO - Startup... 2019-10-03 07:33:37,829 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-03 07:33:37,869 - NanoVNASaver.NanoVNASaver - INFO - Found NanoVNA (0483 5740) on port /dev/ttyACM0 2019-10-03 07:33:37,869 - NanoVNASaver.NanoVNASaver - DEBUG - Building user interface 2019-10-03 07:33:37,973 - NanoVNASaver.NanoVNASaver - DEBUG - Finished building interface 2019-10-03 07:33:51,682 - NanoVNASaver.NanoVNASaver - INFO - Opening serial port /dev/ttyACM0 2019-10-03 07:33:52,100 - NanoVNASaver.NanoVNASaver - INFO - info Kernel: 4.0.0 Compiler: GCC 5.4.1 20160919 Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices Board: NanoVNA Build time: Aug 2 2019 - 16:40:01 ch> 2019-10-03 07:33:52,265 - NanoVNASaver.NanoVNASaver - INFO - Read starting frequency 100000 and end frequency 150000 2019-10-03 07:33:52,265 - NanoVNASaver.NanoVNASaver - DEBUG - Starting initial sweep 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - INFO - Initializing SweepWorker 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - INFO - 1000 sweeps 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - DEBUG - Parsed sweep range as 100000 to 150000 2019-10-03 07:33:52,266 - NanoVNASaver.SweepWorker - DEBUG - Sweep segment no 0 2019-10-03 07:33:52,267 - NanoVNASaver.SweepWorker - DEBUG - Setting sweep range to 100000 to 100000 2019-10-03 07:33:52,568 - NanoVNASaver.SweepWorker - DEBUG - Reading frequencies 2019-10-03 07:33:52,784 - NanoVNASaver.SweepWorker - DEBUG - Reading data 0 2019-10-03 07:33:52,994 - NanoVNASaver.SweepWorker - DEBUG - Read 101 values 2019-10-03 07:33:52,995 - NanoVNASaver.SweepWorker - WARNING - Got a non-float data value: 2147483647.147483647 2147483647.147483647 (2147483647.147483647) 2019-10-03 07:33:52,995 - NanoVNASaver.SweepWorker - DEBUG - Re-reading data 0 repeats until 2019-10-03 07:34:06,245 - NanoVNASaver.SweepWorker - CRITICAL - Tried and failed to read data 0 20 times. Giving up. 2019-10-03 07:34:06,245 - NanoVNASaver.SweepWorker - DEBUG - Sweep segment no 1 2019-10-03 07:34:06,251 - NanoVNASaver.SweepWorker - DEBUG - Stopping sweeping as signalled 2019-10-03 07:34:06,258 - NanoVNASaver.SweepWorker - DEBUG - Resetting NanoVNA sweep to full range: 100000 to 150000 2019-10-03 07:34:06,260 - NanoVNASaver.SweepWorker - DEBUG - Sending "finished" signal Anyone? No RF squirted into it, default as delivered. Cannot see more than one trace. |
Re: Installed recent firmware - was this a big mistake?
From: Oristo
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 (eg. 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. ==================================== Here, I experienced that a USB 5 GHz Wi-Fi dongle was substantially slowed in speed by having a USB mouse plugged into the same hub. So some USB appears to "work that way". Cheers, David -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
Re: errors of "error" models
Hello gin&pez
toggle quoted message
Show quoted text
I installed maxima and ran the visualizer, it worked OK giving the expected figures. I have also taken a look at the fortran code, and I am not done yet, it is difficult to read as it is written in strict fortran 77 using the 6 character variable names. Such short variable names makes it difficult (for about 20% of the names) to understand the intent of the variable or function. You may consider using longer variable names as 32 character variables names are supported in watcom fortran 2.0 (not sure for 1.9) and 31 character variable names in the fortran 90 standard and gnu fortran. You may also consider indenting the loops and conditionals to ease reading. Regards Jose On Wed, Oct 2, 2019 at 1:47 PM yza <yzaVNA@...> wrote:
26 : Correction of Maxima Version and "Unpacked" DERDEI Code |
Re: Which Firmware Version?
I did not get that from the user guide.? But your explanation works for me.? I have not connected with a terminal program yet...
toggle quoted message
Show quoted text
Thank!Mike WY6K On Wednesday, October 2, 2019, 09:29:27 PM CDT, hwalker <herbwalker2476@...> wrote:
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: 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 |
to navigate to use esc to dismiss