开云体育

Thanks John, will do.

Mike C.

I recommend using the recommendations from , and using one of the vendor links on the "Buy a NanoVNA" page.

That's what I just did , and bought H4 from R&L Electronics. (Ordered via the web on Nov 21, arrived at my home Nov 26). Very satisfactory experience.

Since you expressed a preference for Ebay/Amazon, you might wish to use the link they provide for "AURSINC" on Amazon.

Miike,
Try:

/g/NanoVNA-V2
and
/g/NanoVNAV2

--John Gord

Hi Larry,

Relatively new visitor here. If there is a "specific" user group for the SAA-2N? VNA, could you please address it here for those of us who have "that" specific unit? Thank you for any help you can give.

Mike C.

On 11/27/2021 8:51 AM, Larry Rothman wrote:

The SAA uses a binary programming protocol, not dfu, so I don't know what help files you are referring to.Please refer to docs that reference the SAA series of devices specifically and refer to the SAA user groups for info on programming the device.

<snip>

Looking for an approved vendor (=not a clone) on Ebay or Amazon. I can't wait for the ports of Long Beach and Los Angeles to make a delivery. Some of my overseas shipments are over two months past their delivery date and there is no hope in sight.

Pat

The SAA uses a binary programming protocol, not dfu, so I don't know what help files you are referring to.Please refer to docs that reference the SAA series of devices specifically and refer to the SAA user groups for info on programming the device.?
Search the forum messages for SAA and binary?
This topic has been covered a few times here.?


On Fri., 26 Nov. 2021 at 11:26 p.m., Anthony<n2ki.ham@...> wrote: So I have spent quite some time trying to get the SAA-2N to connect to my PC using a number of different help files.? None of which worked.? There are a number of missalignments to what the help files say to do and what is actually appearing.

For starters, the drivers were installed without any errors.? This was confirmed by the Device Manager display not indicating a yellow triangle. When the VNA is connected to the USB port, it shows up as being on Com 8, specifically USB Serial Device (COM8).

Second, the help file says to enter DFU mode by the following path (per flow chart) "Config" > "DFU".? That path does not exist in my unit.? My best guess is to enter "Config" > "Bootload" but I can not verify this as it is not in the help file.? Can someone confirm this?

Next, when in the bootload screen, the DfuSe v3.0.6 still does not see the VNA.? Also I will point out that there is no listing in the Device Manager saying STM Device in DFU Mode, yet the drivers installed correctly.? When I try to reinstall the drivers, Windows says the best drivers are already installed.

Next, when looking at the Version screen, there is no Version listed.? It just says Version:
Underneath Version is shows a Build Time of June 9 2021 -17:36:19

So is there a help file that I am missing? I appreciate if anyone can clarify this procedure.

Thanks!

So I have spent quite some time trying to get the SAA-2N to connect to my PC using a number of different help files. None of which worked. There are a number of missalignments to what the help files say to do and what is actually appearing.

For starters, the drivers were installed without any errors. This was confirmed by the Device Manager display not indicating a yellow triangle. When the VNA is connected to the USB port, it shows up as being on Com 8, specifically USB Serial Device (COM8).

Second, the help file says to enter DFU mode by the following path (per flow chart) "Config" > "DFU". That path does not exist in my unit. My best guess is to enter "Config" > "Bootload" but I can not verify this as it is not in the help file. Can someone confirm this?

Next, when in the bootload screen, the DfuSe v3.0.6 still does not see the VNA. Also I will point out that there is no listing in the Device Manager saying STM Device in DFU Mode, yet the drivers installed correctly. When I try to reinstall the drivers, Windows says the best drivers are already installed.

Next, when looking at the Version screen, there is no Version listed. It just says Version:
Underneath Version is shows a Build Time of June 9 2021 -17:36:19

So is there a help file that I am missing? I appreciate if anyone can clarify this procedure.

Thanks!

Hello Bruce ans all,
few days ago I has purchase a nanovna(SAA2) Version 2.2 and install nanovna-saver 3.8 and when I start it sugest to update to version 3.9...
When I try to run it I get the same error of Bruce get...
I already try following the instructions on this link (/g/nanovna-users/files/Nano%20VNA%20Saver/nanoVNA-H4%20software%20support%20under%20Ubuntu.pdf) without success...
Can somebody help me please???

Hi Gyula ...
Tryied to visit your web page .. but the language doesn't switch to english and remain in Hungarian all the times ....
Peter...

This is the place
*Sent:* Friday, November 26, 2021 at 9:13 AM
*From:* "davebb123456" <davidbrowne76@...>
*To:* [email protected]
*Subject:* Re: [nanovna-users] LIBRE VNA
Yes here you go,
Thanks Dave
[email protected]

On Fri, 26 Nov 2021, 09:02 Piero Tognolatti, <piero.tognolatti@...>
wrote:

Does a user group on LIBRE VNA exist?

Regards

Piero, I0KPT

Yes here you go,
Thanks Dave
[email protected]

On Fri, 26 Nov 2021, 09:02 Piero Tognolatti, <piero.tognolatti@...>
wrote:

Does a user group on LIBRE VNA exist?

Regards

Piero, I0KPT

Does a user group on LIBRE VNA exist?

Regards

Piero, I0KPT

Hi,
I will be brief on the answer, but you will find a lot of information in this forum in the wiki and files folders. When you log in to the forum, you will find it in the menu on the left side of the screen.
If you prefer to read and learn from the experiences of others, use the google ‘NanoVNA’ search engine or if you don’t want to search, you can also find ideas and experiences about NanoVNA on my website.

--
Gyula HA3HZ

Calibration, Compensation, DIY Parts Hacking!...... My First Post!
im new to all this so let me know if im the right page....
and i hope this helps another new user to get going faster then i did..lol..
I am a new user of the NanoVNA and in just messing around with it i knew this would be a great tool...
But i thought that if i did the standard SMA Cal, and added my so239. i knew it would be off! but for SWR i thought just go with it and add/learn more as i go along... i couldn't find the proper E delay info and how to figure it out, so being lazy i looked for Cal Kits for simple HF/VHF/UHF/CB connectors as that's all i got it for and need it to do with it.. wow the $ is biggly for those 66$. i found a set here
AS-PLS-UM - Precision calibration load set. PL-259 (UHF male) connectors


my pl259 with smaF for the cal kit isnt much different or far off im betting, so i think my DIY KIT will do just fine..

hears how i figured out a cpl different ways to compensate/DIY Hack with spare parts/a few cheep parts.... (any higher in FREQ id go better cables/connectors and such but for simple radio work i think i have my GO KIT/ Portable Test Lab) ready...
I love it"....
I need a few more connectors i don't have now, but for now i can Zero this thingy out 3 different ways.... i did a save cal in 2 different cal settings and looked at the same antenna in both, and didn't notice much difference at all on the smith and swr.. so that kinda confirms some people saying that just a connector will throw off everything.. i agree a simple connector change wont mess the simple readings but for higher freq or more in-depth readings we really need a highly calibrated piece of equipment!

so now that iv gotten this far ill feel better about trying out more detailed readings... Knowing i can make it and get it done is a good feeling..
Ironically i just found the best and bare minimum to the point on Port Extension and Electrical Delay ive seen yet, AFTER I FINISHED Getting this all together.. lol I Love It...
#317: NanoVNA Port Extension using the Electrical Delay setting


I will, (maybe not today LOL) replicate his E-delay vid and see how true my DYI CAL Kits Fair with Known Test Matching... I Think?... lol

1. The easiest, is to get a MorF/SMA to Fso239, & Male/PL259toSMA/Female and use your cal there...
2. a lil work, and 3 so230 making a cal set, and using your open as your coax connector..
3. just learn how to "Calibrate then Compensate" to get by with out so many darned connectors...

Like the Wifey calls me "Capt Over Kill" here is my "as of now cal set" and im off n running about to use this more and more as im learning how the rest of all these functions work...
"all the help i can get" is how im looking at this.. !!!
Wish me Luck..
73s
KK6DBR
Happy Thanks Giving All!

Alternatively, I present my favorite C meter. The Ballantine 520 measures capacitance from 0.01 pF to 12 uF (not a typo) in 12 ranges.
It's an oldie, but a goodie. I can wave the probes near each other on the lowest scale and watch the meter vary accordingly.
The low end capability makes it valuable to measure PCB trace capacitance.
It is basically a 1 KHz sine wave generator with a precision resistive voltage divider followed by a VTVM calibrated in capacitance
Also, the probes don't respond to C to GND; only between the probe tips, so stray C is avoided. They are simply coax with UT-141 semi-rigid with the ends center conductor exposed as tips.

Just a general thought: We are not running a metrology lab.

Sure, accuracy is worth chasing. But there is a practical limit to what
amateurs can and should expect of affordable measurement instruments.
Monday, yesterday, I was working with another PhD EE and PhD in Plasma
Physics in designing a piece of equipment for a specific purpose. The
comment was made that the latest NANOVNA - the full 3-GHz version - comes
mighty close to challenging the equivalent HP (Agilent.....Keysight)
equipment. We both have an 8753C with S-Parameter Test Sets and HP
precision cal standards. And the cost ratio: maybe 1000:1 or greater.
The NANOs are the best piece of test equipment to add to any ham shack or
professional design effort since the advent of the DMM (Digital MultiMeter).

BTW: The "OPEN" cal standard for RF systems and measurements has been and
remains the most challenging of any "standard". A short or strictly
resistive standard is relatively easy to fashion at RF and microwave
frequencies. The "OPEN" will remain a challenge for metrology labs aimed
at higher RF and microwave frequencies - even for amateurs. Frankly, the
cal standards provided with most of the NANOs compare rather
(embarrassingly) well against the HP (Agilent.....Keysight) standards to
the frequency limits of the instruments.

Dave - W?LEV

On Tue, Nov 23, 2021 at 6:37 PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Mon, Nov 22, 2021 at 07:06 PM, WB2UAQ wrote:

I agree with Roger that the reactance is very high making it tough to

measure

the min C accurately.

I think you misunderstood me. My comments about high reactance were an
answer to the question posed by Joe WB9SB. I said...

For a air variable R is very small and for a very small capacitance like

8 pF the reactance X is very high under 10 MHz. At >10 MHz. it is
1/(2*pi*8e-12*10e6) = 1,990 ohms and 19,900 ohms at 1 MHz. . So on the
Smith chart when you plot from 1 >to 10 MHz. it is just a fat dot at the
right hand side.

I did not say that the NanoVNA could not measure the minimum C of the air
variable cap. In fact the nanoVNA gives a good estimate as shown in the
screenshot/plot below. The 8 pF is close to the 8.4 pF what I measured
with my DE-5000 LCR meter.

Roger

--
*Dave - W?LEV*
*Just Let Darwin Work*

On Tue, Nov 23, 2021 at 10:37 AM, Roger Need wrote:

I did not say that the NanoVNA could not measure the minimum C of the air
variable cap. In fact the nanoVNA gives a good estimate as shown in the
screenshot/plot below. The 8 pF is close to the 8.4 pF what I measured with
my DE-5000 LCR meter.

Screenshot/graph of 8 pF capacitor was missing in last post.

Roger

On Mon, Nov 22, 2021 at 07:06 PM, WB2UAQ wrote:

I agree with Roger that the reactance is very high making it tough to measure
the min C accurately.

I think you misunderstood me. My comments about high reactance were an answer to the question posed by Joe WB9SB. I said...

For a air variable R is very small and for a very small capacitance like 8 pF the reactance X is very high under 10 MHz. At >10 MHz. it is 1/(2*pi*8e-12*10e6) = 1,990 ohms and 19,900 ohms at 1 MHz. . So on the Smith chart when you plot from 1 >to 10 MHz. it is just a fat dot at the right hand side.

I did not say that the NanoVNA could not measure the minimum C of the air variable cap. In fact the nanoVNA gives a good estimate as shown in the screenshot/plot below. The 8 pF is close to the 8.4 pF what I measured with my DE-5000 LCR meter.

Roger

It did happen to me before, try loading a calibration you have saved prior, then try to calibrate again.

Hi,
I tried to connect NanoVNA-F V2 0.3.0 to nanovna-saver on Windows 10 x64.
I have ST com/usb driver and device is on COM7.

I connected via terminal to it and talked with no issue:
ch> help
There are all commands
help: lists all the registered commands
reset: usage: reset
cwfreq: usage: cwfreq {frequency(Hz)}
saveconfig: usage: saveconfig
clearconfig: usage: clearconfig {protection key}
data: usage: data [array]
frequencies: usage: frequencies
scan: usage: scan {start(Hz)} {stop(Hz)} [points] [outmask]
sweep: usage: sweep [start(Hz)] [stop(Hz)] [points]
touchcal: usage: touchcal
touchtest: usage: touchtest
pause: usage: pause
resume: usage: resume
cal: usage: cal [load|open|short|thru|done|reset|on|off]
save: usage: save {id}
recall: usage: recall {id}
trace: usage: trace [0|1|2|3|all]
[{format}|scale|refpos|channel|off] [{value}]
marker: usage: marker [1|2|3|4] [on|off|{index}]
edelay: usage: edelay {value}
pwm: usage: pwm {0.0-1.0}
beep: usage: beep on/off
lcd: usage: lcd X Y WIDTH HEIGHT FFFF
capture: usage: capture
version: usage: Show NanoVNA version
info: usage: NanoVNA-F V2 info
SN: usage: NanoVNA-F V2 Serial Numbel
resolution: usage: LCD resolution
LCD_ID: usage: LCD ID
ch> version
0.3.0
ch>

When I open up GUI and click [connect], I either get this:
PS C:\Program Files\NanoVNA> .\nanovna-saver.exe -d
NanoVNASaver 0.3.9

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 for further details.

2021-11-23 16:11:01,761 - NanoVNASaver - INFO - Startup...
2021-11-23 16:11:01,848 - NanoVNASaver.NanoVNASaver - DEBUG - Running from
pyinstaller bundle
Settings: C:/Users/mszczuro/AppData/Roaming/NanoVNASaver/NanoVNASaver.ini
2021-11-23 16:11:02,069 - NanoVNASaver.Settings.Sweep - DEBUG -
Sweep(3600000, 30000000, 101, 1, Properties('', SweepMode.SINGLE, (3, 0),
False))
2021-11-23 16:11:02,069 - NanoVNASaver.SweepWorker - INFO - Initializing
SweepWorker
2021-11-23 16:11:02,069 - NanoVNASaver.Settings.Sweep - DEBUG -
Sweep(3600000, 30000000, 101, 1, Properties('', SweepMode.SINGLE, (3, 0),
False))
2021-11-23 16:11:02,069 - NanoVNASaver.Settings.Sweep - DEBUG -
get_index_range(0) -> (3600000, 30000000)
2021-11-23 16:11:02,069 - NanoVNASaver.SweepWorker - DEBUG - Init data
length: 101
2021-11-23 16:11:02,431 - NanoVNASaver.NanoVNASaver - DEBUG - Building user
interface
2021-11-23 16:11:02,904 - NanoVNASaver.Windows.About - INFO - Latest
version is 0.3.9"
2021-11-23 16:11:02,904 - NanoVNASaver.Windows.About - INFO - This is 0.3.9
2021-11-23 16:11:02,904 - NanoVNASaver.Windows.SweepSettings - DEBUG -
update_band(False)
2021-11-23 16:11:02,958 - NanoVNASaver.NanoVNASaver - DEBUG - New font
width: 164.000000, normal font: 164.000000, factor: 1.000000
2021-11-23 16:11:03,040 - NanoVNASaver.Hardware.Hardware - DEBUG - Found
NanoVNA USB:(0483:5740) on port COM7
2021-11-23 16:11:03,056 - NanoVNASaver.NanoVNASaver - DEBUG - Finished
building interface
2021-11-23 16:11:44,430 - NanoVNASaver.NanoVNASaver - INFO - Connection
COM7 (NanoVNA)
2021-11-23 16:11:44,535 - NanoVNASaver.Hardware.Hardware - INFO - Finding
correct VNA type...
2021-11-23 16:11:44,537 - NanoVNASaver.NanoVNASaver - ERROR - Unable to
connect to VNA: Cannot configure port, something went wrong. Original
message: PermissionError(13, 'A device attached to the system is not
functioning.', None, 31)
2021-11-23 16:11:44,537 - NanoVNASaver.Hardware.VNA - DEBUG - VNA reading
frequencies
2021-11-23 16:11:44,538 - NanoVNASaver.Hardware.VNA - DEBUG -
exec_command(frequencies)
Traceback (most recent call last):
File "NanoVNASaver\NanoVNASaver.py", line 522, in serialButtonClick
File "NanoVNASaver\NanoVNASaver.py", line 556, in connect_device
File "NanoVNASaver\Hardware\VNA.py", line 148, in readFrequencies
File "NanoVNASaver\Hardware\VNA.py", line 190, in readValues
File "NanoVNASaver\Hardware\VNA.py", line 92, in exec_command
File "NanoVNASaver\Hardware\Serial.py", line 33, in drain_serial
File "serial\serialwin32.py", line 269, in read
serial.serialutil.PortNotOpenError: *Attempting to use a port that is not
open*

and app crash,
or I get:
(...)
2021-11-23 16:16:38,398 - NanoVNASaver.NanoVNASaver - INFO - Connection
COM7 (NanoVNA)
Traceback (most recent call last):
File "NanoVNASaver\NanoVNASaver.py", line 522, in serialButtonClick
File "NanoVNASaver\NanoVNASaver.py", line 542, in connect_device
File "serial\serialutil.py", line 372, in timeout
File "serial\serialwin32.py", line 222, in _reconfigure_port
serial.serialutil.SerialException: Cannot configure port, something went
wrong. Original message: PermissionError(13, '*A device attached to the
system is not functioning*.', None, 31)

or I get:
(...)
2021-11-23 16:20:25,393 - NanoVNASaver.Hardware.Hardware - DEBUG - Found
NanoVNA USB:(0483:5740) on port COM7
2021-11-23 16:20:25,393 - NanoVNASaver.NanoVNASaver - DEBUG - Finished
building interface
2021-11-23 16:20:29,791 - NanoVNASaver.NanoVNASaver - INFO - Connection
COM7 (NanoVNA)
2021-11-23 16:20:29,791 - NanoVNASaver.NanoVNASaver - ERROR - Tried to open
COM7 (NanoVNA) and failed: could not open port 'COM7': FileNotFoundError(2,
'*The system cannot find the file specified*.', None, 2)

And I get these on random (1st and 2nd) depending on USB cable. The 3rd
message I get on the best shielded USB cable I have, so it looks like
permanent issue.

Which file could be missing? Is there a more verbose debug available?

BR,
Marcin