New application

[todivefor]

I am not sure what is used for calibration, slot 1?

There is no in app calibration for the nanoVNA (yet). My tested models send out already corrected data. The currently loaded calibration is used.
Do we need an in app calibration? Routines are already in, since the FA-VA requires it.

I am not sure what "My tested models send out already corrected data" means?

My slot 0 is calibrated 7MHz - 29.7MHz and slots 1-7 have calibrations for individual bands. If I start my NanoVNA-H, I'm using calibration in slot 0 (7 - 29.7MHz) and it is sweeping this stimulus, so VNAmate is using this calibration. I then switch VNAmate to individual bands. I assume I am still using slot 0 calibration. If I switch NanoVNA to slot 1 - 7, then VNAmate will be using those calibrations?

I think app calibration would be nice. I am getting good results without it. If my understanding is correct?

Thank you.

[DL2RUM]

I am not sure what "My tested models send out already corrected data" means?

Some VNA models send out the measured raw data. These values are useless without a calibration.

Your understanding is nearly correct, except the app doesn't do any calibrations or corrections. It just shows what the NanoVNA delivers.

[Werner3861]

You state that your app was tested with the NanoVNA-F V2. I have the same -F that is depicted in the instructions. It appears however that the -F does not have a Bluetooth function built-in. Can you confirm that the -F ONLY connects to the app using the USB connection but not Bluetooth.
If you have tested -F with Bluetooth, what am I missing? Is there a hidden setting that needs to be activated?

[DL2RUM]

Who was talking about Bluetooth?

[Mike KB0DDC]

Good morning to everyone!
First a little back information. Ive been a ham for almost 40 years with a long break. Things such as jobs, houses, kids, moving....
My question I have a SSA-2N nano van. Does anyone know if this app will work with it? Otherwise I will just hook it up and find out.
Mike

[n1ho]

I think Werner3861 is having a problem similar to mine - VNAmate doesn't seem to see my NanoVNA-F. I have an M4 MBPro, running Sequoia 15.6, and used a USB-A - to USB-C cable to connect from the USB-A port on the NanoVNA-F to the USB-C port on the righthand side of the MBP. VNAmate shows only "Bluetooth-Incoming-Port" and "debug-console" as possible devices. My NanoVNA-F is 4.3" HW2.3 HW3.1 running BH5HNU's Firmware 1.0.5. I downloaded VNAmate from the App Store at about 1700UTC today.

I did look at all of the entries in "/dev" and couldn't find any new ones that might've come up by attaching the NanoVNA-F, even after restarting MacOS.

Ironically, if I plug in my small docking adapter that connects in my Ethernet, backup drives and my Elecraft K3, VNAmate does offer the K3's USB port as a possibility

The USB-C "port" on the NanoVNA-F is labeled "Charging Only", so it appears we're forced to use the USB-A port to talk to it somehow.

Do we need to push some buttons or select some menu items on the NanoVNA to force it to talk to our Macs? (I have done firmware updates on this device a couple of times, and I don't want to accidentally destroy its firmware by pushing the wrong buttons!)

Thanks, and 73,

Brandy, N1HO

[DL2RUM]

It seems the USB-C port in the NanoVNA is not USB-C compatible!
I have to use a USB-C to A adapter in my MBP M1. Then I use a USB-A - USB-C cable. This it will work fine, without any driver installed.

[n1ho]

I recabled, and tried with a USB-C/USB-A cable (with the 'C' end plugged into the NanoVNA) and a USB-A/USB-C adapter with the 'C' side plugged into the right-hand port on the MBP, and MacOS saw the unit (and which I granted permission to 'talk' to it). I noticed that it showed up
in /dev as cu.usbmodem48D8666532391 and tty.usbmodem48D8666532391 and VNAmate displayed it as "usbmodem48D8666532391"
as one of the possible/available devices. (VNAmate also saw the USB ports on my K3 and K4D!). I can't tell if it sniffed out the cu or the tty or both.

However, VNAmate also said "Port opened successful but no connection!" and there is a little dot just to the right of the 'Connect' button.
(I am slightly color-blind, so I can't distinguish the color). Toggling between 'Connect' and 'Disconnect' causes it to "disconnect" and then
re-attempt to connect with the same error message. Setting up all the hardware and turning the NanoVNA on as the last step exhibits the
same behaviour. It does the same thing with a USB-C/USB-C cable as well.

Hope that helps,

Brandy, N1HO

[DL2RUM]

Can you post a screen shot of the Welcome / About / Info screen of your device?
Do you have tried both NanoVNA settings?

[n1ho]

"Both" NanoVNA settings? Sorry, didn't know there were 2; can you clarify? Maybe that's what my problem is

Hopefully, this screen shot will help: