开云体育

I export the nanovna touchstone files into simsmith where I can make
different simulations/adaptations

On Wed, May 27, 2020 at 4:28 PM warnergt via groups.io <warnergt=
[email protected]> wrote:

I used to use Touchstone many, many years ago. It was a great program.
I haven't worked with S parameters for a long time so I'm out of touch
with the currently available applications.
What current applications work like Touchstone and/or work with Touchstone
files?

I had completely forgotten about Les Besser.
He was great -- and one really smart guy.
I met him somewhere -- perhaps at one of the
microwaves courses he used to teach.

I installed nanovna-saver-0.2.2 on my Mac and it works perfectly in MacOS (I use the latest Catalina 10.15.5).
I wish I could remember exactly how I installed it.
I do know that I can invoke it from a terminal command line with: NanoVNASaver

Then, I created a simple script to run it:

##!/bin/bash
NanoVNASaver

Then, I used Apple's Automator to create what looks like and app to run that script.
Thus, NanoVNASaver looks like a regular app on my Mac. I simply double-click on the icon and it starts up.

I am a newbie to the NanoVNA H4 as well, and will defer to others that are more knowledgeable on this topic than me, but I read on another forum that RigExpert release AntScope2, an open source product () where some were using AntScope2 with their NanoVNA devices. This may or may not be an option for Mac users.

Hi Craig,

Yes, i used it today actually with a NanoVNA-H and NanoVNA-Saver on OSX
Mojave, no trouble.

It's certainly easier to use on the computer, but if you'll be hanging off
towers and prefer to read the screen directly, then the 4" screen-size
might be a better buy (or for failing eyes) :)

There is also an Android app that might make the above easier although i
haven't tried it myself yet.

But it gets the job done. Which is better is debatable, the NanoVNA is
certainly cheaper.

Hope it helps...



Cheers,

Chris.

On Wed, Jun 17, 2020 at 01:20 PM, Erik Kaashoek wrote:

The differential input resistance of the SA612 is about 3kOhm.

Ok, I thought that he wanted to measure the CH1 termination resistors network, that is why I mentioned "nanoVNA switched off of course".
Instead from what I understand he wanted a live ohmmeter measurement, whereas obviously that is not proper.

Hi Craig,

you may want to install Python on your machine now so you can try out the nanovna saver. He gets acquainted with it until the nanovna arrives. Rick included a pdf on how to install it.
You may also want to check out the forum wiki and files. Since this is a large amount of material, I suggest that whatever topic interests you read it.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Please note that the build date for 4.2.1 is incorrectly 2019, correct 2020.

--
*** If you are not part of the solution, then you are the problem. ( ) ***

On Wed, Jun 17, 2020 at 05:39 PM, <iyerak@...> wrote:

Just found this:

It looks like an acknowledged design error!

It looks that it could be resolved with the v4.2.1
Compare this

with this

changed the CH1 50Ohm network.

Additionally firmware update using 'dfu-util' works fine.

NanoVNA-saver and RigExpert Antscope2 both work fine on Catalina w/NanoVNA-H4
/ Gerry

On 18.06.20 09:44, reuterr@... wrote:

Hello Holger,
In the MacOS archive I can see libraries only, no executable.
As far as I know nanoVNA-saver is a Python3 program.
73, Rudi DL5FA

$ file nanovna-saver
nanovna-saver: Mach-O 64-bit x86_64 executable

the nanovna-saver binary in the zip archive misses the
executable flag (chmod +x nanovna-saver)

I'll fix this in future builds, if otherwise
github actions build would work.

73
Holger

Hello Holger,
The sourcecode works under MacOS Mojave 10.14.6.
73, Rudi DL5FA

Hello Holger,
In the MacOS archive I can see libraries only, no executable.
As far as I know nanoVNA-saver is a Python3 program.
73, Rudi DL5FA

Hello Rick,

On 18.06.20 09:03, Rick Commo wrote:

I have a latw 2014 Macbook Pro running Catalina. Here is my command
to start up nanovnasaver natively.

nanovnasaver='python3 ~/nanovna-saver-0.2.0/nanovna-saver.py&’

As you can see the “~/nanovna-saver-02.0” is the directory tree where
all the nanovnsaver files are put.

as I have no Mac available (at least none with a current IOS) I'm
looking for someone who can test the automated build distribution
via github actions.

Link


73
Holger

If you need good 50ohm match use a 10dB attenuator between DUT and CH1 input
Calibrate thru using the attenuator and you loose a bit of dynamic range but get very good 50ohm match.


--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

I have a latw 2014 Macbook Pro running Catalina. Here is my command to start up nanovnasaver natively.

nanovnasaver='python3 ~/nanovna-saver-0.2.0/nanovna-saver.py&’

As you can see the “~/nanovna-saver-02.0” is the directory tree where all the nanovnsaver files are put.

Attached is the PDF that I created to install it. I used the info found in the URL of the top line. You will also have some upfront work and installing to do to get to the final results that you want.

I have Parallels and could run it under Window, but my preference was to do it natively under macOS. I just ran it with the nanovna attached and all was as it should be except that see that I need to update to 0.2.2 now!

Cheers & good luck,
-rick

Just found this:

It looks like an acknowledged design error!

I've successfully used NanoVNA Saver with my MacBook Pro using VMware Fusion and Windows 10. I've not tried anything that runs on Mac OSX directly.

The MFJ 259A does some of the same basic measurements as the NanoVNA with the VNA providing far more capabilities. My only complaints are the small physical screen size and it's not easy to see in sunlight. Mark - wd9jen.

Thanks for your suggestions. I purchased two of these (one for a student), and both of them have the same response. Is this particular to the NanoVNA-H? Does anyone else experience this? I fear this is by design, rather than a defect.

I agree with Erik that it wouldn't make sense to apply a dc ohmmeter to ch1. Instead, I did as you did: I calibrated the device with a cable on ch0 but not on ch1. When it came time to do the through measurement, I connected the cable directly to ch1. Recognizing a small impedance transformation across the through (which I'll neglect), the input impedance seen at ch1 was about 43 - j5 ohms at the lower end of the band, getting progressively further away from 50 ohms towards the higher end. This is hardly acceptable, and nowhere near what you are seeing with your H4.