¿ªÔÆÌåÓý

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

NanoVNA-Saver 0.1.3 MAC


 

Colin, which version of macOS and how did you set up the USB ports?
Tried it here with Catalina but some problem finding the device on the USB¡­

Dana VE3DS

On Oct 19, 2019, at 20:11, zl2arl <colin.larsen@...> wrote:

I've just done the MacOS install, went smoothly, all I had to do was adjust
the font size up a bit ;)

On Sun, 20 Oct 2019, 12:49 W5DXP, <w5dxp@...> wrote:

That sure does help, Rune. I was using it on my mobile system and my wifi
doesn't reach that far. It would have never occurred to me that Saver
needed the internet. Thanks very much. Do you have any idea how fast one
has to be to get that screen-capture while Saver is shutting down?
Displaying that screen for longer than one millisecond would help. :)




 

Hello Dana,

I have been running most of the recent releases of NanoVNA-Saver on my iMac under Mojave 10.14.6. I declined the upgrade to Catalina because several of my expensive software purchases would no longer work. The procedure I use is to plug the NanoVNA into my MAC, turn on the NanoVNA and then launch the Saver program V0.1.3. When the screen paints the USB port is already properly identified and I simply select "Connect to nanoVNA". It all works perfectly and has for every release of Saver that I tried starting back at about V0.0.6.

Again, this is all under Mojave, not Catalina. If you find the correct incantation for Catalina please let us all know.

Good luck,

Larry, AE5CZ


 

Hmmm, Larry, so it may be a Catalina issue as it doesn¡¯t find the usb¡­
I¡¯ll try it on Mojave and see if that works¡­thanks for the comments.
Oh by the way what version of Python are you using??

Dana Ve3DS

On Oct 20, 2019, at 13:41, Larry Goga <lgoga@...> wrote:

Hello Dana,

I have been running most of the recent releases of NanoVNA-Saver on my iMac under Mojave 10.14.6. I declined the upgrade to Catalina because several of my expensive software purchases would no longer work. The procedure I use is to plug the NanoVNA into my MAC, turn on the NanoVNA and then launch the Saver program V0.1.3. When the screen paints the USB port is already properly identified and I simply select "Connect to nanoVNA". It all works perfectly and has for every release of Saver that I tried starting back at about V0.0.6.

Again, this is all under Mojave, not Catalina. If you find the correct incantation for Catalina please let us all know.

Good luck,

Larry, AE5CZ


 

Hi Dana,

In OSX the nanoVNA is shown as "/dev/cu.usbmodem4001"
Normally rescan will automatically connect. You could try however to manually enter the string above

Eric


 

Ok, I rescan isn¡¯t finding anything, so I will try manual also

Thx
Dana

On Oct 20, 2019, at 14:22, ericm@... wrote:

Hi Dana,

In OSX the nanoVNA is shown as "/dev/cu.usbmodem4001"
Normally rescan will automatically connect. You could try however to manually enter the string above

Eric


 

I used the installation process as described on the GitHub nanovna-saver website for installation of nanovna-saver for the Mac OS. It is as follows:
Mac OS:
Homebrew
Install Homebrew From :
/usr/bin/ruby -e "$(curl -fsSL )"
Python :
brew install python
NanoVNASaver Installation
git clone
cd nanovna-saver
Change PyQt restriction in setup.py PyQt5==5.11.2 to PyQt5
Install local pip packages
python3 -m pip install .
NanoVNASaver

All of the above works for me and I believe the Python installation is v3.7.4 Hope this helps.

Larry


 

Thanks Larry - good summary

This all worked fine on my iMac under High Sierra, however something
didnt work properly under Catalina¡­still trying to trace the issue, something
to do with the serial ports¡­ I¡¯ll report back if I can figure it out.

Cheers
Dana VE3DS

On Oct 21, 2019, at 12:23, Larry Goga <lgoga@...> wrote:

I used the installation process as described on the GitHub nanovna-saver website for installation of nanovna-saver for the Mac OS. It is as follows:
Mac OS:
Homebrew
Install Homebrew From :
/usr/bin/ruby -e "$(curl -fsSL )"
Python :
brew install python
NanoVNASaver Installation
git clone
cd nanovna-saver
Change PyQt restriction in setup.py PyQt5==5.11.2 to PyQt5
Install local pip packages
python3 -m pip install .
NanoVNASaver

All of the above works for me and I believe the Python installation is v3.7.4 Hope this helps.

Larry


 

something didnt work properly under Catalina¡­still trying to trace the issue,
something to do with the serial ports
I cannot even use High Sierra because of driver (and Java) issues.
macOS has become more restrictive about 3d party kernel extensions or kexts.
"They act as drivers ¡ª if you like a Windows analogy ¡ª and give access to your Mac¡¯s hardware."

Something done on previous macOS that was inherited by Catalina update
could be at issue. Check 'Security & Privacy' under 'System Preferences'

"If a user space driver quits unexpectedly or you restart your Mac,
you might need to unplug and reattach the accessory cable to enumerate the driver. (50042397)"
"Driver extensions might not launch on-demand after installation. (51229724)
Workaround: Disable System Integrity Protection"


CH340 driver


 

Hi,

mine is working fine under Catalina 10.15. NanoVNASaver found the USB port immediately when the VNA was connected and I just clicked to connect to it.

Good Luck -- John (VK2JON)


 

Hi John -

mine is working fine under Catalina 10.15.
Great! If you would try, in Terminal:

# with nanoVNA powered off, enter:
ioreg -p IOUSB -l -w 0 | grep "USB Product Name" > without

# then power on nanoVNA and enter:
ioreg -p IOUSB -l -w 0 | grep "USB Product Name" > nano

# finally
diff nano without

# the result on my Mac shows a "ChibiOS/RT Virtual COM Port" driver used for nanoVNA

< | | "USB Product Name" = "IOUSBHostDevice"
< | | "USB Product Name" = "QUAD-CAPTURE"
< | "USB Product Name" = "Polar V800"
< "USB Product Name" = "ChibiOS/RT Virtual COM Port"
---
| "USB Product Name" = "IOUSBHostDevice"
| "USB Product Name" = "QUAD-CAPTURE"
"USB Product Name" = "Polar V800"


 

Now this is interesting John¡­. it isn¡¯t playing here on Catalina.

Glad to hear someone has it though!

73 Dana VE3DS

On Oct 21, 2019, at 20:52, John Sharpe <johsharpe@...> wrote:

Hi,

mine is working fine under Catalina 10.15. NanoVNASaver found the USB port immediately when the VNA was connected and I just clicked to connect to it.

Good Luck -- John (VK2JON)


 

macOS Catalina
Version 10.15.4

Rebooted to Recovery Mode
Disabled SIP (csrutil disable)
Restarted in "regular" mode
device shows up as /dev/cu.usbmodem4001

Used NANOVnA to scope out antenna

Rebooted to Recovery Mode
Enabled SIP (csrutil ebable)
Restarted in "regular" mode
device still shows up as /dev/cu.usbmodem4001

Moral of the story is it worked even after re-enabling SIP. Now I have to get it to work using vmWare Fusion and Windows 7. Hope this is helpful...

73 Mark KG0RMS


 

How exactly do I change the PyQT restriction? I'm computer literate, but not familiar with Python at all.
The original install instructions I found didn't have that step, so I'm wondering if that isn't my problem. Here's the error:

Processing /Users/lynn/nanovna-saver
Preparing metadata (setup.py) ... done
Collecting pyserial>=3.5
Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
Collecting PyQt5>=5.15.0
Using cached PyQt5-5.15.6.tar.gz (3.2 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error

¡Á Preparing metadata (pyproject.toml) did not run successfully.
©¦ exit code: 1
¨t©¤> [29 lines of output]
Traceback (most recent call last):
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 156, in prepare_metadata_for_build_wheel
hook = backend.prepare_metadata_for_build_wheel
AttributeError: module 'sipbuild.api' has no attribute 'prepare_metadata_for_build_wheel'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
main()
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 160, in prepare_metadata_for_build_wheel
whl_basename = backend.build_wheel(metadata_directory, config_settings)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/api.py", line 51, in build_wheel
project = AbstractProject.bootstrap('pep517')
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/abstract_project.py", line 83, in bootstrap
project.setup(pyproject, tool, tool_description)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/project.py", line 594, in setup
self.apply_user_defaults(tool)
File "project.py", line 63, in apply_user_defaults
super().apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/pyqtbuild/project.py", line 70, in apply_user_defaults
super().apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/project.py", line 241, in apply_user_defaults
self.builder.apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/pyqtbuild/builder.py", line 67, in apply_user_defaults
raise PyProjectOptionException('qmake',
sipbuild.pyproject.PyProjectOptionException
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

¡Á Encountered error while generating package metadata.
¨t©¤> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
WARNING: There was an error checking the latest version of pip.


 

Do you have sip installed in Python?

On May 23, 2022 4:46:21 PM CDT, "Lynn Mears via groups.io" <K0CLM@...> wrote:
How exactly do I change the PyQT restriction? I'm computer literate, but not familiar with Python at all.
The original install instructions I found didn't have that step, so I'm wondering if that isn't my problem. Here's the error:

Processing /Users/lynn/nanovna-saver
Preparing metadata (setup.py) ... done
Collecting pyserial>=3.5
Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
Collecting PyQt5>=5.15.0
Using cached PyQt5-5.15.6.tar.gz (3.2 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error

¡Á Preparing metadata (pyproject.toml) did not run successfully.
©¦ exit code: 1
¨t©¤> [29 lines of output]
Traceback (most recent call last):
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 156, in prepare_metadata_for_build_wheel
hook = backend.prepare_metadata_for_build_wheel
AttributeError: module 'sipbuild.api' has no attribute 'prepare_metadata_for_build_wheel'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
main()
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/opt/homebrew/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 160, in prepare_metadata_for_build_wheel
whl_basename = backend.build_wheel(metadata_directory, config_settings)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/api.py", line 51, in build_wheel
project = AbstractProject.bootstrap('pep517')
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/abstract_project.py", line 83, in bootstrap
project.setup(pyproject, tool, tool_description)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/project.py", line 594, in setup
self.apply_user_defaults(tool)
File "project.py", line 63, in apply_user_defaults
super().apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/pyqtbuild/project.py", line 70, in apply_user_defaults
super().apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/sipbuild/project.py", line 241, in apply_user_defaults
self.builder.apply_user_defaults(tool)
File "/private/var/folders/5c/_kgrrymn4hx0glzk2g84ysrh0000gn/T/pip-build-env-jodshyjo/overlay/lib/python3.9/site-packages/pyqtbuild/builder.py", line 67, in apply_user_defaults
raise PyProjectOptionException('qmake',
sipbuild.pyproject.PyProjectOptionException
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

¡Á Encountered error while generating package metadata.
¨t©¤> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
WARNING: There was an error checking the latest version of pip.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

Doesn't look like it. Will work on that
thanks!


 

I installed sip. We¡¯re you thinking that would solve the error (it did not) or is that what I use to change the PyQT restriction?

Thanks!


 

It looked like it was having a problem building related to sip, so was hoping that wou,d help.

I'm not honestly clear what you are calling a "PyQt restriction" . . . Building PyQt is often a part of the install (if not already present) and absence of subcomponents can affect it as well.

On May 23, 2022 6:50:46 PM CDT, "Lynn Mears via groups.io" <K0CLM@...> wrote:
I installed sip. We¡¯re you thinking that would solve the error (it did not) or is that what I use to change the PyQT restriction?

Thanks!




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

The install instructions said
¡° Change PyQt restriction in setup.py PyQt5==5.11.2 to PyQt5¡±

That was my original questions as to how to do that.


 

I guess I missed that message, but it appears from your build logs that that requirement does not exist in your build, since early in the log (sorry, don't have that message . . . ) it clearly shows that it is looking for a version above a certain level, and not 5.11.2 specifically . . .

On May 23, 2022 7:39:13 PM CDT, "Lynn Mears via groups.io" <K0CLM@...> wrote:
The install instructions said
¡° Change PyQt restriction in setup.py PyQt5==5.11.2 to PyQt5¡±

That was my original questions as to how to do that.




--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


 

OK, thanks!