¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Re : NanoVNA-Saver Linux update procedure

 

Currently I have owner read and write permission on both /.cache and /.cache/pip but only group read and write permission on /.cache/pip.
Anyway I have NanoVNA-saver running through Nick's requirements.txt hack so will leave alone

den@den-ThinkPad-T520 ~ $ ls -dl /home/den/.cache
drwx------ 36 den den 4096 Dec 9 19:08 /home/den/.cache
den@den-ThinkPad-T520 ~ $ ls -dl /home/den/.cache/pip
drwxrwx--- 5 den den 4096 Jan 15 22:23 /home/den/.cache/pip

Thanks for the suggestion


Re: Poor Manual

 

Russian version


Re: Run a Airspy HF+ from a Samsung 10" tablet?

 

I have the above tablet and wonder if anyone has been able to run their
HF+ from one? If so, what did it take to enable it?
Ray, W4BYG
=====================================

Ray, I expect you meant to post to: /g/airspy. I don't see why it shouldn't work from /any/ Windows tablet as there are no extra drivers required.

73,
David GM8ARV
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv


Re: Can't save calibration with NanoVNA saver in NanoVNA device,

 

Hi Rune,
Thank You for the explanation.I know that and use all features of the nanoVNA Saver.The Calibration Assistant is very helpfull ! Very good software for nanoVNA users.Thank You once again.Maybe in future we can get and "Save to device" button.
Best Regards de Peter/Lz2pg


Re: #nanovna-saver Linux software issue #nanovna-saver

 

I've ran into issues too with Ubuntu 18.04.3 LTS

All of the dependencies are present. Below is the results of the install.

xx@000-OMEN-by-HP-Laptop::~/nanovna-saver$ python3.7 -m pip install .
Processing /home/mm/nanovna-saver
Collecting PyQt5 (from NanoVNASaver==0.2.2)
Using cached
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.7/tokenize.py", line 447, in open
buffer = _builtin_open(filename, 'rb')
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-build-x4up3i2u/PyQt5/setup.py'

----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-x4up3i2u/PyQt5/


I've tried creating the tmp folder and manually moving setup.py . It really didn't make much difference.

If any other information would be helpful, let me know.

73
Bob N8FAU


Run a Airspy HF+ from a Samsung 10" tablet?

 

I have the above tablet and wonder if anyone has been able to run their HF+ from one?? If so, what did it take to enable it?
Ray, W4BYG

--
They say a smart person learns from their mistakes. A
wise person learns from the mistakes of others.


Re: Poor Manual

 

... and one more
Added to the list:
/g/nanovna-users/wiki/User-Guides


Re: Poor Manual

 

... and one more:


Re: Firmwares

 

replaced firmwares_hugen


Re: Can't save calibration with NanoVNA saver in NanoVNA device,

 

Hi Peter,
just a quick note: On the NanoVNA, you calibrate the device itself, and
what it outputs on its screen, and via the USB cable. In NanoVNA-Saver,
you calibrate exclusively within the software - it relies on the
calibration on the NanoVNA itself remaining constant. This also allows
calibrating with more data points than the NanoVNA itself allows. Using the
"segments" setting, you can get many more points than the 101 of the device
itself. There is no way to save calibration to the device. Neither the
firmware, nor NanoVNA-Saver, supports this.

Since we are on the subject of calibration: NanoVNA-Saver has a calibration
assistant, and 5 manual buttons for calibration. Use the assistant. The
manual buttons take whatever is currently stored (and being displayed) by
the application, and uses that as the calibration data. It does *not* make
a separate sweep for the new standard - it assumes the user knows to do
this themselves. The latest version has a warning popup if a user tries to
use the manual buttons.

I hope you enjoy using the application :-)

--
Rune / 5Q5R

On Sat, 18 Jan 2020 at 18:58, <s_peter@...> wrote:

Hello All,
When calibrate the device (nanoVNA-H) all is 100% OK.
When I do calibrate with nanoVNA saver (several versions incl.0.2.2-1),
all is
also OK 100%, exept lhe last step - saving the calibrtion in nanoVNA-H. No
way to
save this calibration in nanoVNA-H.I can save it to the Disk only.
Seems somewhere I make mistake,,,, Where ?
The connection between the Saver and device is established and active.
The VNA-H is not prepared to get data ?
I have not found the procedure for recording in the device via NanoVNA
Saver anywhere. Many things are described how to calibrate, but this is not
exactly what it is.
Any Help will be appreciated.Thanks in advance,
Peter




Re: Can't save calibration with NanoVNA saver in NanoVNA device,

 

Hi Gyula,
Many thanks for the answer.Will see what I can do wiy saved calibrations on
the Hard disk.
Best Regards !


Re: Firmwares

 

Hugen released new firmware today for NanoVNA-H and NanoVNA-H4. Version number is 0.4.5-4.


Re: Re : NanoVNA-Saver Linux update procedure

 

The final post here

indicates that pip 19.3.1 fixed the problem on Debian Buster,
whereas it didn't for you.

Built nvna-a 0.2.2 with python 3.7.6 on Win7 x64 (mingw64) first with pip
19.2.3 then pip 19.3.1. Everything including PyQt5==5.14.1 was installed
without a hitch!

Do not know what to make of all this. Will do more tests.
Yes, Windows does not match the linux/POSIX paradigm for directory ownership;
this cache ownership bug cannot occur on Windows.

One workaround for linux user den is:
`chown den /home/den/.cache`

if /home/den/.cache does not exist, then
`mkdir /home/den/.cache`

If /home/den/.cache is already owned by someone else, then:
`sudo chown den /home/den/.cache`

Then repeat for /home/den/.cache/pip

The "fix" for pip was to disable caching, which seems dumb (to me):


Re: Can't save calibration with NanoVNA saver in NanoVNA device,

 

Hi Peter,

You can't save to your device with the nanoVNA saver.
The backup is done to your computer.
It is advisable to write detailed information in the note.

Gyula HA3HZ


Can't save calibration with NanoVNA saver in NanoVNA device,

 

Hello All,
When calibrate the device (nanoVNA-H) all is 100% OK.
When I do calibrate with nanoVNA saver (several versions incl.0.2.2-1), all is
also OK 100%, exept lhe last step - saving the calibrtion in nanoVNA-H. No way to
save this calibration in nanoVNA-H.I can save it to the Disk only.
Seems somewhere I make mistake,,,, Where ?
The connection between the Saver and device is established and active.
The VNA-H is not prepared to get data ?
I have not found the procedure for recording in the device via NanoVNA Saver anywhere. Many things are described how to calibrate, but this is not exactly what it is.
Any Help will be appreciated.Thanks in advance,
Peter


Re: Firmwares

 

Hi Herb,

Thanks for the information. There is also a contact link from where you can download it

73, Gyula


Re: Firmwares

 

On Sat, Jan 18, 2020 at 08:10 AM, Gyula Molnar wrote:

Updated firmwares.
the dates in the file names represent the latest release.
=================================
Gyula,
The updates are much appreciated. I just received my NanoVNA-H v3.4 unit and a version no. appears to have been snuck in by hugen (see attachment).

NanoVNA-saver identifies it as follows:

0.4.4-1- Dec 18 2019 NanoVNA-H version compiled on December 18, 2019
1. New scan command
2. Screenshots

Again, please note that currently this firmware version is only distributed with the NanoVNA-H v3.4.
- Herb


Re: Interpreting TDR, aka when to worry #nanovna-saver #tdr

 

measuring cable and insertion loss ala
Added to "External Links" wiki page
/g/nanovna-users/wiki/External-links#related-28RF29-links


Re: Interpreting TDR, aka when to worry #nanovna-saver #tdr

 

Thanks for the tips everyone. After sending I realize what I'm particularly interested in is measuring cable and insertion loss ala .

Given that I'm looking at seven days straight of rain (the joy of Seattle in the winter) disconnecting parts of the transmission line and testing them independently is not a near-term project :-).

I had previously seen the collective wisdom part of the wiki, some great gems in there.

Thanks,
Chris