开云体育

On Sat, Jan 11, 2020 at 03:47 PM, Leif M wrote:

I attached a Smith chart file with a -1690 delay, does it look good. It is
from a 36mm length of Teflon coax with open on other end. The delay seems long
at least.

Your plot should be a little tighter together. Did you calibrate the NanoVNA before attaching the cable?
The plots below are 30 cm of RG316 with an open BNC connector on the end. One up to 299 MHz. and the other up to 900 MHz. offset delay was set to -1536 ps and no calibration done in NanoVNA saver.

Roger

I'm getting a program crash when enabling Continuous Scan after loading a
calibration file on 0.2.2, Win7 SP1. Anyone else seeing this? I've posted a
new bug issue on Github.

-agc

Bob Larkin wrote:

Here is a picture when running a stylus all over the screen in a touch test

Take the four screws holding the screen bezel down, and check to see if there aren't scraps of the plastic film still stuck under there. I had that problem for a few minutes when mine arrived, until I noticed a tiny corner of the film sticking out of the bezel.

--
wes will
n9kdy

On 1/12/20 2:38 PM, Nels Nelsen wrote:

I just have this one error :
Python setup.py egg info failed with code 1 in
/temp/pip-build-xzpflql/PyQt5/

???? That might be the same error message I got when I installed the latest Nanovna-saver yesterday.? The program still starts, but I haven't tried actually connecting to the NVNA.

I don't know where the picture at groups.io went. Try

Bob

It sounds like you may have a bad touchscreen or, make sure that
There is nothing pinching the touchscreen around the front bezel.?You can remove the 4 screws on the front bezel and do a visual chaek ofnthe touch surface.?


On Sun, 12 Jan 2020 at 6:33 PM, Bob Larkin<bob@...> wrote: My nanoVNA arrived in Dec and functions just fine in RF terms. The touch screen has never been correct and the numerical input from the pad has not worked.? It is:
ch> 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 18 2019 - 16:10:54

Here is what happens.? If I do a serial controlled cal I see the following:
ch> touchcal
first touch upper left, then lower right...done
touch cal params: 3776 562 -30 192
ch> saveconfig
Config saved.
ch> touchtest
then moving the stylus vertically (y-axis) has results as expected.? But movements horizontally are in the wrong direction and they also cause movement in the y direction.? The result is that only about half of the screen is accessible in a sort-of diagonal pattern.

Yes, I did use the upper-left and lower-right corners to cal, as marked on the screen.

If I try to out-smart it and use the wrong corners, there are different, but very-wrong results.

Am I doing this right?? Has anybody else had such a problem?? I do not see indications of such on a forum search.

Thanks, Bob? W7PUA

Here is a picture when running a stylus all over the screen in a touch test

My nanoVNA arrived in Dec and functions just fine in RF terms. The touch screen has never been correct and the numerical input from the pad has not worked. It is:
ch> 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 18 2019 - 16:10:54

Here is what happens. If I do a serial controlled cal I see the following:
ch> touchcal
first touch upper left, then lower right...done
touch cal params: 3776 562 -30 192
ch> saveconfig
Config saved.
ch> touchtest
then moving the stylus vertically (y-axis) has results as expected. But movements horizontally are in the wrong direction and they also cause movement in the y direction. The result is that only about half of the screen is accessible in a sort-of diagonal pattern.

Yes, I did use the upper-left and lower-right corners to cal, as marked on the screen.

If I try to out-smart it and use the wrong corners, there are different, but very-wrong results.

Am I doing this right? Has anybody else had such a problem? I do not see indications of such on a forum search.

Thanks, Bob W7PUA

Rune,

Thanks for fixing the "Offset Delay" bug in Calibration. I checked it out with several coax cables and got good results. It also correlates with the "electrical delay" parameter in the NanoVNA hardware.

Roger

On Sat, Jan 11, 2020 at 03:47 PM, Leif M wrote:

Is S11 or CH0 impedance also available in polar plot form?
========================================================

Leif,
You may have already found this information but if not, by selecting the NanoVNA-Saver 0.2.2 "Display Settings" command button a window will pop-up and in that window there is a "Settings" button that will allow you to select for S11 (CH0) polar format to be displayed.

- Herb

When I reloaded my Linux Mint XFCE 19.2 because of screen freezing up I
installed Mint XFCE 19.3 and after a reboot it decided that I should not
have administration rights over any USB drives. So I installed Mint Mate
19.3 (yes they are all really different) and I am having a hard time
getting nanoVNA-saver ver 2.2 to work at all. Some of The problems are
where python puts the code in the directory naming structure of Linux.
Your script has gotten me very close to success. Thank you.
I just have this one error :
Python setup.py egg info failed with code 1 in
/temp/pip-build-xzpflql/PyQt5/

I am getting to dislike PyQt5 as it causes a lot of errors.

At this time I have no fix and nanoVNA-saver 2.2 will not run on any of
the above mentioned Linux distributions. But when it ran it ran circles
around and with the nanovna. So much fun.

Thanks for all of your help.
NE7LS

On Sun, Jan 12, 2020 at 01:51 PM, Joe Kirk wrote:

I have one of the white NanoVNAs but the high level menu does not have the Config option which I understand would show me the current version of firmware. How can I find out which version I have?
================================================

Joe,
Another little gem in Rune's latest NanoVNA Saver 0.2.2 release is the manage command button (see attachment) which presents you with a pop-up window showing version and other info regarding your NanoVNA. It works fine with my 0.4.3Q firmware. I haven't tried it with other firmware.

If you haven't installed or upgraded to NanoVNA Saver 0.2.2 its another reason to do so.


- Herb

If you are updating your previously installed NanoVNA-Saver in Linux, the procedure is the same with one exception. If you try to do the gitclone, it will complain that the directory is not empty. So first I moved my current install to a different directory name then followed install steps as normal. Your existing launcher/shortcut will still work as directory structure is the same. Also you can still use the previous version if necessary by changing the path. I also have added a no cache option for pip to avoid the "directory not owned by current user" error.

sudo mv nanovna-saver nanovna-saver-2.1

then

git clone
cd nanovna-saver
sudo python3.7 -m pip --no-cache-dir install .
--
Andrew Harmon - KD5RKO

I have one of the white NanoVNAs but the high level menu does not have the Config option which I understand would show me the current version of firmware. How can I find out which version I have?
TIA
Joe G3ZDF

You can get much better than 20Hz by watching S meter, when you are very close it will swing due to constructive and destructive action on the signal. Get the S meter to nearly stop swinging and you will be within 1 Hz

On Sun, Jan 12, 2020 at 12:38 PM, Roger Need wrote:

" … The latest version has fixed the (offset delay) bug. I just made a number of tests using NanoVNA saver 2.2 with different length cables and got good results by just entering an estimate for one way delay and then varying for best results while watching the Smith Chart and S11 phase delay. .

I also compared using the offset delay in the program and the equivalent electrical delay parameter in the NanoVNA hardware and got agreement there as well. The electrical delay used in the hardware parameter is the round trip delay so I divided by 2 to get the offset delay in the Saver program. "
=============================================================
Roger,
I'm sure Rune will be happy to hear those results. Kurt Poulsen had previously provided feedback to Rune that the "S21 phase delay has been fixed OK and the S21 group delay are still correct."

Kudo's to Rune for his usual excellence.

Crazy Houston and Chiefs game in progress.

- Herb

Herb,
That's great information that you shared. Thanks!

If you can't install nanovna saver, I recommend nanovnaPartner, which works under XP.
You can find the latest version of nanoVNA Partner v0.19 on my website (ha3hz.hu)

73, Gyula HA3HZ

It is likely that the nanovna-saver will work from python under XP. However, Python 3.5 and above will not work on Windows XP.
Try 3.4.4 and if you succeed in installing Qt5 then you are close to success.
There is WinPython, a portable python option for windows, but I couldn't go any further. However, there is also an integrated Qt5.
If I get the PS2 keyboard for my XP machine, I will try to continue with the installation.

73, Gyula HA3HZ

Hi Chuck,
i see you need to install a driver on windows 7 so that your computer can see nanoVNA. To do this, download and install en.stsw-stm32080.zip (DfuSe) or STSW-LINK004 (ST-Link) or en.stsw-stm32102.zip (STM32 Virtual Com Port driver). DefuSe or ST-Link is required for a firmware upgrade.
After installation, plug the nanoVNA connector into your computer's USB port. Use the USB cable (not OTG) supplied with the nanoVNA.
I don't know what the usb connector of white nanovna.
You can see in the device manager of your computer that it is present at COM & LPT.
If not, a little utility (USBDeview) will help you to remove the faulty driver.
To run nanoVNA-Saver on Windows 7, you must have the SP1 Service Pack installed and MS VC ++ multipack (2005-2017) installed, then the windows exe version of nanovna-saver will work. It starts up slower when you first start up, later it is faster.

Hope I was able to help with the solution.

73, Gyula HA3HZ