By modifying the Windows NanoVNASaver.ini file, it is very easy to insert the Standards Calibrations data, kindly supplied by Kurt Poulsen.  Typos are then  automatically avoided.

However in the Linux version (I'm using MINT 20, FWIW), I have yet to find such a simple and accurate method.
Can anybody point me at the answer?
H-P

On 6/24/21 4:20 AM, Hector Pascal wrote:
>
> By modifying the Windows NanoVNASaver.ini file, it is very easy to
> insert the Standards Calibrations data, kindly supplied by Kurt
> Poulsen.  Typos are then  automatically avoided.
>
> However in the Linux version (I'm using MINT 20, FWIW), I have yet to
> find such a simple and accurate method.
> Can anybody point me at the answer?
> H-P
>

NanoVNA-saver is python, and should be the same in all versions.

On mine (running on MacOS) I get this in the terminal window where I
start it:

nanovna-saver jimlux$ python3 nanovna-saver.py
NanoVNASaver 0.3.6

Copyright (C) 2019, 2020 Rune B. Broberg
Copyright (C) 2020 NanoVNA-Saver Authors

This program comes with ABSOLUTELY NO WARRANTY
This program is licensed under the GNU General Public License version 3

See https://github.com/NanoVNA-Saver/nanovna-saver for further details.

Settings: /Users/jimlux/.config/NanoVNASaver/NanoVNASaver.ini


--

Down in .config, the ini file starts with:

[General]
CalibrationFile=/Users/jimlux/nanovna-saver/2021-04-19-1-50MHz.cal
Chart00=S21 Gain
Chart01=S11 Return Loss
Chart02=None
Chart10=None
Chart11=S11 VSWR
Chart12=None
CheckForUpdates=No
ColoredMarkerNames=true
DarkMode=false
ExpertCalibrationUser=true
FontSize=8
LineThickness=1

and on and on after that.

Many thanks Jim,  I finally found the Linux .config folder, and the .ini file can be updated in exactly the same way as in the Windows version.

The problem seemed to be that the .config file was completely hidden, until I switched to being a root user. (I have only been tinkering with Linux for the past 6 months, so I often don't know the things obvious to others - and being in my mid 70's doesn't help either!).  I switched to Linux so that I could get the correct screen scaling for my monitor.

Nanosaver now works fine with the added Cal Standards files - except that connection to the VNA is very flaky, sometimes OK, sometimes needs a reboot.  I'm still investigating this.  My Linux PC is quite old, and has a mixture of USB1 and 2 ports, and I need to be sure which ones are USB2, before checking out their hardware.  Does Linux have a handy command for helping with identification?  The VNA connects flawlessly to my newer Win 10 PC, so that should rule out a VNA USB problem, I guess?

Many thanks again,
H-P

On 6/24/21 7:27 PM, Hector Pascal wrote:
>
> Many thanks Jim,  I finally found the Linux .config folder, and the
> .ini file can be updated in exactly the same way as in the Windows
> version.
>
> The problem seemed to be that the .config file was completely hidden,
> until I switched to being a root user. (I have only been tinkering
> with Linux for the past 6 months, so I often don't know the things
> obvious to others - and being in my mid 70's doesn't help either!).  I
> switched to Linux so that I could get the correct screen scaling for
> my monitor.
>
you actually don't need to be root, but by default, directories
beginning with . don't get displayed.


> Nanosaver now works fine with the added Cal Standards files - except
> that connection to the VNA is very flaky, sometimes OK, sometimes
> needs a reboot.  I'm still investigating this.  My Linux PC is quite
> old, and has a mixture of USB1 and 2 ports, and I need to be sure
> which ones are USB2, before checking out their hardware.  Does Linux
> have a handy command for helping with identification?  The VNA
> connects flawlessly to my newer Win 10 PC, so that should rule out a
> VNA USB problem, I guess?
>
lsusb might give you some info.  But in this kind of thing "google is
your friend"

>
> Many thanks again,
> H-P
>
>

Good by,
There is too much crap on this feed so I switched to special notes only.
Next step is to unsubscribe. I am using my VNAs to measure and not to masturbate with SW and FW.
73 de OE6CCP

> Am 2021/06/25 um 04:52 schrieb Jim Lux <jim@luxfamily.com>:
>
> On 6/24/21 7:27 PM, Hector Pascal wrote:
>>
>> Many thanks Jim, I finally found the Linux .config folder, and the .ini file can be updated in exactly the same way as in the Windows version.
>>
>> The problem seemed to be that the .config file was completely hidden, until I switched to being a root user. (I have only been tinkering with Linux for the past 6 months, so I often don't know the things obvious to others - and being in my mid 70's doesn't help either!). I switched to Linux so that I could get the correct screen scaling for my monitor.
>>
> you actually don't need to be root, but by default, directories beginning with . don't get displayed.
>
>
>> Nanosaver now works fine with the added Cal Standards files - except that connection to the VNA is very flaky, sometimes OK, sometimes needs a reboot. I'm still investigating this. My Linux PC is quite old, and has a mixture of USB1 and 2 ports, and I need to be sure which ones are USB2, before checking out their hardware. Does Linux have a handy command for helping with identification? The VNA connects flawlessly to my newer Win 10 PC, so that should rule out a VNA USB problem, I guess?
>>
> lsusb might give you some info. But in this kind of thing "google is your friend"
>
>
>
>>
>> Many thanks again,
>> H-P
>>
>
>
>
>
>
>
>

Maybe start your own VNA Measurements group then?
H-P

With Linux/Unix by default filenames starting with a period are not
listed/shown but may still be accessible
as the non-root user depending on the file permissions.

Command line to show the filenames that start with a period:
# ls -a
or for details
# ls -la





On Thu, Jun 24, 2021 at 9:27 PM Hector Pascal <hector.pascal@gmail.com>
wrote:

> Many thanks Jim, I finally found the Linux .config folder, and the .ini
> file can be updated in exactly the same way as in the Windows version.
>
> The problem seemed to be that the .config file was completely hidden,
> until I switched to being a root user. (I have only been tinkering with
> Linux for the past 6 months, so I often don't know the things obvious to
> others - and being in my mid 70's doesn't help either!). I switched to
> Linux so that I could get the correct screen scaling for my monitor.
>
> Nanosaver now works fine with the added Cal Standards files - except that
> connection to the VNA is very flaky, sometimes OK, sometimes needs a
> reboot. I'm still investigating this. My Linux PC is quite old, and has a
> mixture of USB1 and 2 ports, and I need to be sure which ones are USB2,
> before checking out their hardware. Does Linux have a handy command for
> helping with identification? The VNA connects flawlessly to my newer Win
> 10 PC, so that should rule out a VNA USB problem, I guess?
>
> Many thanks again,
> H-P
>
>
>

On Thu, Jun 24, 2021 at 09:25 PM, Erich Kaltenbrunner wrote:

>
> I am using my VNAs to measure and not to masturbate with SW and FW.
> 73 de OE6CCP

Yep.  I'm pretty much the same, interested in RF, not software and computers. It's inevitable with the way technology has evolved that issues with latter two are going to dominate. The way the nanoVNA products arose and the technology evolved makes it especially rife with complexities and a playground for software/computer aficionados. I haven't checked, but I assume it's much different on the Rohde & Schwarz VNA group.

On 6/25/21 6:53 AM, Lou W7HV via groups.io wrote:
> On Thu, Jun 24, 2021 at 09:25 PM, Erich Kaltenbrunner wrote:
>
>  I am using my VNAs to measure and not to masturbate with SW and FW.
> 73 de OE6CCP
>
> Yep.  I'm pretty much the same, interested in RF, not software and
> computers. It's inevitable with the way technology has evolved that
> issues with latter two are going to dominate. The way the nanoVNA
> products arose and the technology evolved makes it especially rife
> with complexities and a playground for software/computer aficionados.
> I haven't checked, but I assume it's much different on the Rohde &
> Schwarz VNA group.
> _._,_._,_


Probably - but after all, this group (and the other similar ones for
other NanoVNAs) are the "mutual support channel", - and things like
hardware, firmware, and software mods are going to be the dominant
topic.  The R+S, Anritsu, and Keysight units have their own support
channels  - and since the hardware and software are more "locked down"
you won't see as much modification and firmware stuff.

There is *plenty* of discussion on other forums about trying to get the
"big iron" VNAs to work with Labview, Python, etc. With a lot of the
same "program X doesn't recognize my model Y on my computer running Z" 
as you see here.  I fought the libusb and GPIB interface driver battles
a few years ago and it was a whole litany of searching on various
forums, finding point solutions, and finally getting it to work, and
then saying "nobody install anything new on that computer in the lab, it
finally works with Python and Ruby, we don't want to break it"

Hi all,
In my "defence" of starting this topic, I must state that I myself have also been a hands on RF engineer for over 50 years - working the first 4 in commercial R&D, the second 20 for BBC Transmission (when they had their own REAL engineers!), and the last 17 teaching RF units at Uni. I really don't WANT to play with soft- and firm-ware, but when the system doesn't work as intended, I have to dust off my limited programming skills and dig in.  Nobody else is available locally to get things going for me!  This Group is probably the best available knowledge base for all the "low cost VNA" hardware, firmware and software.  If people want a dedicated VNA measurements group, then start one up!  There is certainly enough expertise in this group, let alone the N2PK, and the DG8SAQ ones to support it.

H-P

Dear Erich,
You do not HAVE to read all the messages in this forum, or even turn on your computer, if you wish to just set up aerials and get a sore thumb pressing the transmit switch.

Meanwhile, I must get back to Madam Palm and her five sisters (can you work that out?).

Steve L.

Im familiar with linux/unix but totally new to the VNA world so this group
is a goldmine for folks like me.

These low cost VNAs bring in new folks to the RF world and thats always
good.

Erich, please don't go!

With your incredible knowledge you could be an invaluable source of knowledge to all us w*****s here - just think, no so very long ago you were a tosser, too.