开云体育

Thanks from a newbie
________________________________
From: [email protected] <[email protected]> on behalf of Gareth Evans via groups.io <headstone255@...>
Sent: Thursday, March 6, 2025 2:29 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Apologies if flogging a dead horse! CAL Correction?

It's your calibration!

O - Open; S - Short; L - Load (The 50 Ohm)


On Wed, Mar 5, 2025 at 09:48 PM, CLIFTON HEAD wrote:

What does OSL stand for and where or how to find it on the VNA H4 or F V2

Well NanoVNA Saver 0.6.5 used to connect to com port on Win 10 and now it does not. I start the nanovna software, turn on the NanoVNA and when
I click Rescan the software crashes off. If I turn on the NanoVNA first and then start the software I get Failed to execute nanosaver could not open Com 5. When I check Device Manager com ports I see Com port 5 and the yellow triangle. I deleted the com port and plugged the C cable from the NanoVNA-H into the pc and the com port 5 reappeared with the yellow triangle.

So I downloaded Nanosaver 0.7.3 and with NanoVNA turn on then start nanosaver 0.7.3 I get the com port 5 error. If I start nanosaver first and then turn on NanoVNA-H I click rescan and nothing happens.

The yellow triangle on the STMicroelectronics Virtual COM Port (COM 5) is causing nanosaver not to connect to pc. I have downloaded latest nanovna saver driver and when I try to update Win says I have the latest driver. I am stuck as NanoVNA saver used to work, any ideas how to remove yellow triangle from Com Port 5 I think that's my issue or I am missing something else.
Mick N3OJP

Entered 82 no % (.82) just 82 and it comes up on the screen as 82%
________________________________
From: [email protected] <[email protected]> on behalf of Geoff Peters - AB6BT via groups.io <AB6BT@...>
Sent: Wednesday, March 5, 2025 8:43 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] NanoVNA F V2 not working correctly

Just out of curiosity...for the H4 the VF is entered as a decimal as
0.82. Is the F V2 VF entered the same or is it in percent?

73,
Geoff -->AB6BT


On 3/5/2025 6:18 PM, CLIFTON HEAD via groups.io wrote:

Yes, if you mean the value. Both 82% for RG-8X. Even if the VF was off maybe 5 meters still shouldn't come up with over a 1000 m for the 16 m / 52' length.
________________________________
From: [email protected] <[email protected]> on behalf of Mark Foster via groups.io <m.foster99@...>
Sent: Wednesday, March 5, 2025 8:01 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] NanoVNA F V2 not working correctly

Did you enter the Velocity Factor (VF) of the coax the same in both units ?

Thanks, I see C1 is the 1 because I saved the cal.
________________________________
From: [email protected] <[email protected]> on behalf of Stan Dye via groups.io <standye@...>
Sent: Wednesday, March 5, 2025 5:18 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Apologies if flogging a dead horse! CAL Correction?

Clifton, the 1.2.40 firmware version is very recent, so you don't need to update. The correction item should be there in the calibration menu, but you don't need to worry about it unless for some reason you want to disable calibration. It defaults to the enabled state. Look at the very left-hand side of the screen, and if you see a capital 'C' there, at the top of a column of other letters, your calibration is enabled.

At the advice of many, I simply removed the 9:1 UNUN (Palomar Engineering) and made a "direct" connection to the rain gutter via a sheet metal screw.
Then ran one radial along the ground (I will try more radials later).
Much to my surprise, it now loads better on the 10/15/20 meter bands.
I will try it on the air today (QRP power only) to avoid setting off any fire alarms here (TU for that advice).

I realise that the information from the Nano VNA in my shack has limited value - TU.
Coax is 50 ft RG8X (decent quality) and a couple of "isolators" (RF chokes) in the shack.

de k3eui barry Philly
March 06 2025

Addendum: After posting the last message, I reviewed the video link which I
had posted regarding saving of stimulus frequency range. Then I saw that on
recall, I have to press on the number displayed in the corner of the grey
screen, which I had done unknowingly, to get the frequency range displayed.

Went back and did the same thing for the screenshot - Clicked on 8.bmp with
the guitar pick which came along with the NanoVNA. To my pleasant surprise,
the grey screen disappeared and the saved screenshot was displayed!

Jon, VU2JO.

On Thu, Mar 6, 2025 at 5:23?PM Jon via groups.io <vu2jo0@...>
wrote:

I am using a 32GB micro SD card in my NanoVNA-H v3.6. I use it mainly to
save calibration (). I did not do any
formatting, just inserted a new card and started saving calibration. So far
I have saved about 7 sets and recalled them multiple times later.

After reading your post, I tried to save a screenshot. It showed as saved.
But when I tried to recall it, the recalled screen is just a grey screen
with only the saved number (8.bmp) at one corner!

Jon, VU2JO

On Thu, Mar 6, 2025 at 4:36?PM moshe.braner via groups.io <moshe.braner=
[email protected]> wrote:

I recently bought an H4 v4.3. Was looking forward to being able to save
plots from the nanoVNA to a micro SD card. But every attempt resulted in
"fail write" message. I read that it cannot handle some big fast modern
cards. Tried an 8GB card. No Go. Tried an old 1GB card, formatted
FAT32. The nanoVNA managed to save a calibration, but screenshots

"fail".

Each failed screenshot save resulted (as seen from Windows) in a file
written by the chosen name - but with zero size. Tried a brand new 2GB
card, no go. Read somewhere advice to format the card using the official
SD-formatter program from the SD conglomerate. I have a very old version
of that on my Windows XP PC. Tried that. It formatted it FAT (not
FAT32). The nanoVNA accepted that and successfully wrote a BMP

screenshot

file. That's been my experience. YMMV.
- Moshe N1OVN

I am using a 32GB micro SD card in my NanoVNA-H v3.6. I use it mainly to
save calibration (). I did not do any
formatting, just inserted a new card and started saving calibration. So far
I have saved about 7 sets and recalled them multiple times later.

After reading your post, I tried to save a screenshot. It showed as saved.
But when I tried to recall it, the recalled screen is just a grey screen
with only the saved number (8.bmp) at one corner!

Jon, VU2JO

On Thu, Mar 6, 2025 at 4:36?PM moshe.braner via groups.io <moshe.braner=
[email protected]> wrote:

I recently bought an H4 v4.3. Was looking forward to being able to save
plots from the nanoVNA to a micro SD card. But every attempt resulted in
"fail write" message. I read that it cannot handle some big fast modern
cards. Tried an 8GB card. No Go. Tried an old 1GB card, formatted
FAT32. The nanoVNA managed to save a calibration, but screenshots "fail".
Each failed screenshot save resulted (as seen from Windows) in a file
written by the chosen name - but with zero size. Tried a brand new 2GB
card, no go. Read somewhere advice to format the card using the official
SD-formatter program from the SD conglomerate. I have a very old version
of that on my Windows XP PC. Tried that. It formatted it FAT (not
FAT32). The nanoVNA accepted that and successfully wrote a BMP screenshot
file. That's been my experience. YMMV.
- Moshe N1OVN

I recently bought an H4 v4.3. Was looking forward to being able to save plots from the nanoVNA to a micro SD card. But every attempt resulted in "fail write" message. I read that it cannot handle some big fast modern cards. Tried an 8GB card. No Go. Tried an old 1GB card, formatted FAT32. The nanoVNA managed to save a calibration, but screenshots "fail". Each failed screenshot save resulted (as seen from Windows) in a file written by the chosen name - but with zero size. Tried a brand new 2GB card, no go. Read somewhere advice to format the card using the official SD-formatter program from the SD conglomerate. I have a very old version of that on my Windows XP PC. Tried that. It formatted it FAT (not FAT32). The nanoVNA accepted that and successfully wrote a BMP screenshot file. That's been my experience. YMMV.
- Moshe N1OVN

Oops, sorry, already answered multiple times.

Must remember that when we Brits are tucked up in our beds,
you Yanks are still enjoying your evening's hobbies :-)

It's your calibration!

O - Open; S - Short; L - Load (The 50 Ohm)

As a P.S. to my last comment (below), from a search i found a reference to
yet another version of nanoVNA Saver (0.7.3). On one PC, the SV4401A would
not connect (or would crash) just as in the other versions of nanoVNA
Saver. Then i found a comment by a user, that switching to another PC
solved that problem.

So, on my 2nd Win10 laptop, the SV4401A connects to nanoVNA Saver 0.7.3 and
appears to be working correctly.
I did not go back and see if the SV4401A will connect to pre-0.7.3 on the
2nd laptop.

So please, i'd like to hear why the SV4401A is a "completely different
animal from the nanoVNA group." Thank you for any comments.
There's still the issue of the home screen on the VNA misspelling the word
"running" as "runing." If this proves the unit is a fake, i am still
within the return window on amazon.

Thanks
Orrin WN1Z


El mié, 5 mar 2025 a la(s) 8:51?p.m., Orrin Winton via groups.io
(orrin.winton@...) escribió:

I appreciate any comments.

I go to nanovna.com, it suggests:

For platforms such as Amazon or AliExpress, please buy directly through the
store provided by the link. Other advertising links on the platform may
sell bad clones.

Amazon
AURSINC <>




So i go to the Aursinc store on Amazon with that link, and the exact
AURSINC/Sysjoint SV4401A that i bought is there in the Aursinc store. The
name Sysjoint seems to go along with the name Aursinc in several places i
look on the web.


The Chelegance site mentioned above (in this thread) only mentions a
SV4401A latest firmware of 0.4.0 but my device boots up as 0.5.9.

The Chelegance wiki page, for desktop software, lists nanoVNA Saver 0.3.12,
so i downloaded that.

My SV4401A causes nanoVNA Saver versions 0.3.12, 0.5.4, and 0.6.8 to either
fail to load or crash once connected. My F-V2 can connect to all 3
versions.


Without some advice, i am not sure how to proceed. ... I wrote down the
firmware version and serial number that my SV4401A gives on boot-up.


Best 73

Orrin WN1Z




El mié, 5 mar 2025 a la(s) 7:14?p.m., PT via groups.io (paultwa00=
[email protected]) escribió:

Completely different animal from the NanoVNA group

I appreciate any comments.

I go to nanovna.com, it suggests:

For platforms such as Amazon or AliExpress, please buy directly through the
store provided by the link. Other advertising links on the platform may
sell bad clones.

Amazon
AURSINC <>




So i go to the Aursinc store on Amazon with that link, and the exact
AURSINC/Sysjoint SV4401A that i bought is there in the Aursinc store. The
name Sysjoint seems to go along with the name Aursinc in several places i
look on the web.


The Chelegance site mentioned above (in this thread) only mentions a
SV4401A latest firmware of 0.4.0 but my device boots up as 0.5.9.

The Chelegance wiki page, for desktop software, lists nanoVNA Saver 0.3.12,
so i downloaded that.

My SV4401A causes nanoVNA Saver versions 0.3.12, 0.5.4, and 0.6.8 to either
fail to load or crash once connected. My F-V2 can connect to all 3 versions.


Without some advice, i am not sure how to proceed. ... I wrote down the
firmware version and serial number that my SV4401A gives on boot-up.


Best 73

Orrin WN1Z




El mié, 5 mar 2025 a la(s) 7:14?p.m., PT via groups.io (paultwa00=
[email protected]) escribió:

Completely different animal from the NanoVNA group

Completely different animal from the NanoVNA group

Just out of curiosity...for the H4 the VF is entered as a decimal as 0.82. Is the F V2 VF entered the same or is it in percent?

73,
Geoff -->AB6BT

No, you may have gotten a clone. Try NanoVNA.com Good Luck.
________________________________
From: [email protected] <[email protected]> on behalf of Orrin Winton via groups.io <orrin.winton@...>
Sent: Wednesday, March 5, 2025 8:17 PM
To: [email protected] <[email protected]>; Orrin Winton <orrin.winton@...>
Subject: [nanovna-users] Sysjoint SV4401A nanoVNA

So i bought one of these on Amazon (SV4401A). They're $150 less on Ali
Express, but i don't entirely trust Ali Express -- i've been burned twice
by them. The last "burn" was $24 worth of fake coax. Not worth returning.

Anyway, this SV4401A is great and does what it's supposed to do. BUT there
are spelling errors on the main screen, unbelievable.

On the main screen, bottom right, there is a 'button' labelled
RUNING instead of RUNNING. There was another typo as well, but i can't find
it at the moment.

I guess that can be fixed with a firmware update.

Best 73
Orrin WN1Z

Yes, if you mean the value. Both 82% for RG-8X. Even if the VF was off maybe 5 meters still shouldn't come up with over a 1000 m for the 16 m / 52' length.
________________________________
From: [email protected] <[email protected]> on behalf of Mark Foster via groups.io <m.foster99@...>
Sent: Wednesday, March 5, 2025 8:01 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] NanoVNA F V2 not working correctly

Did you enter the Velocity Factor (VF) of the coax the same in both units ?

So i bought one of these on Amazon (SV4401A). They're $150 less on Ali
Express, but i don't entirely trust Ali Express -- i've been burned twice
by them. The last "burn" was $24 worth of fake coax. Not worth returning.

Anyway, this SV4401A is great and does what it's supposed to do. BUT there
are spelling errors on the main screen, unbelievable.

On the main screen, bottom right, there is a 'button' labelled
RUNING instead of RUNNING. There was another typo as well, but i can't find
it at the moment.

I guess that can be fixed with a firmware update.

Best 73
Orrin WN1Z

Thank you Stan
________________________________
From: [email protected] <[email protected]> on behalf of Stan Dye via groups.io <standye@...>
Sent: Wednesday, March 5, 2025 5:18 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Apologies if flogging a dead horse! CAL Correction?

Clifton, the 1.2.40 firmware version is very recent, so you don't need to update. The correction item should be there in the calibration menu, but you don't need to worry about it unless for some reason you want to disable calibration. It defaults to the enabled state. Look at the very left-hand side of the screen, and if you see a capital 'C' there, at the top of a column of other letters, your calibration is enabled.

Thank You
________________________________
From: [email protected] <[email protected]> on behalf of W0LEV via groups.io <davearea51a@...>
Sent: Wednesday, March 5, 2025 4:08 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Apologies if flogging a dead horse! CAL Correction?

O = Open termination
S = Short circuit termination
L = Non-reactive 50-ohm load termination

All applied to the source port.

You may also see "T" in an OSLT designation.

T = Through with the supplied coaxial cable between the source and sink
ports.

Dave - W?LEV

<>
Virus-free.www.avg.com
<>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Mar 5, 2025 at 9:48?PM CLIFTON HEAD via groups.io <aecret=
[email protected]> wrote:

What does OSL stand for and where or how to find it on the VNA H4 or F V2
________________________________
From: [email protected] <[email protected]> on behalf of
W0LEV via groups.io <davearea51a@...>
Sent: Wednesday, March 5, 2025 2:49 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Apologies if flogging a dead horse! CAL
Correction?

Once you complete your chosen cal., go back and check that the OSL actually
shows as an OSL should. If so, that will assure your cal has taken hold.

Dave - W?LEV

<

Virus-free.www.avg.com
<

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Mar 5, 2025 at 8:05?PM Clyde Lambert via groups.io <clyde.lambert=
[email protected]> wrote:

Please excuse my 80yr old brain, I know to include the rest of the info.
but didn't type it.
I have a NanoVNA H4 with FW version 1.2.40.
My question is;
Is 1.2.40 the latest FW or is there a newer version?
The reason for my question is the "Calibration correction" does not show
on the menu selections on my version of FW.
Thank you in advance.
Clyde KC7BJE

--

*Dave - W?LEV*


--
Dave - W?LEV

--

*Dave - W?LEV*


--
Dave - W?LEV

Did you enter the Velocity Factor (VF) of the coax the same in both units ?