¿ªÔÆÌåÓý

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

Re: NanoVNA-Saver and the new _H4 firmware

 

On Thu, Feb 20, 2020 at 02:51 PM, Jos Stevens wrote:


Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC.
================================================================
Jos,
I just ran NanoVNA-saver cal on my -H4 using 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz (see attached) and still had no problem applying the calibration.

My computer is also a Windows 10 PC. I did run a full SOLT instead of just an SOL. Shouldn't make any difference. Hopefully, another -H4 user can run a similar calibration and help to narrow things down for you.

- Herb


Re: A Good source for Calibrated Loads in formats other than SMA - #calibration

 

Hi

I will create a document soon with all the settings required for the NanoVNA-saver both for the male and female kit based on Rosenberger parts. They will include the L and C coefficients used by NanoVNA-saver.
The male and female loads are individually measured by SDR kits with a 4 wire tester and value written on the inside label of the wooden box. The short open and thru delays are contained in the calibration kit file, a standard part of the VNWA software and thus not suppled with the delivery of the kit. These will be included with my document to support purchase from SDR-Kits of these super calibration kit.

I just need to find the time ?

Kind regards

Kurt



-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af jsternmd
Sendt: 20. februar 2020 19:53
Til: [email protected]
Emne: Re: [nanovna-users] A Good source for Calibrated Loads in formats other than SMA - #calibration



Another good source for Precision with full specification are Rosenberger (German) sold by <> www.sdr-kits.net


Re: A Good source for Calibrated Loads in formats other than SMA - #calibration

aparent1/kb1gmx
 

I ahve a set of them. They are high quality PL259 plug to SMA with good
quality SMA OSL.

The OSL tested on Agilent 8357C PNA were good past 3ghz but
not to 6. The PL adapted loads of course start to diverge around
120mhz as PL259 are not really good at UHF (they appear as a
25 to 35 ohm impedance bump). Not at all surprising as they
are NOT a constant Impedance connector.

As DC to 30 mhz (maybe a little higher) they are close as precision
as you will likely get allowing for the connector.

The following common connectors are constant impedance and
good to a minimum of 3ghz some higher:

BNC, TNC, SMA, SMB, N
Do be careful as there are 50 ohm and 75 ohm versions of most
of them (not interchangeable).

There are many others some better but not common.

The oddball is u-fl, good to very high but not a user friendly
connector due to size and fragility.

Allison
-----------------
No direct email, it goes to bit bucket due address harvesting in groups.IO


Re: #nanovna-h4 stops at boot screen #nanovna-h4

 

Hi Keen
Thank you
I did update the H4 and used is for a couple of hours. It look good.
Only in rare cases there is small straylines, e.g. just one yellow one, and it disappear very quickly. So to speak like what happens on the H version now and then.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Ken Liao, AA6KL
Sendt: 20. februar 2020 14:03
Til: [email protected]
Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen

Kurt and Herb,

I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue.



Ken


Re: NanoVNA-Saver and the new _H4 firmware

 

Herb,

Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC.

Regards,

Jos

Op 20-2-2020 om 18:51 schreef hwalker:

I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report. My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.

I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.

- Herb


Re: Android app cable not working!

 

OK, progress... sort of. but not yet quite working. The new OTG
cable installed. Result is it shows a connection available but the web
app then displays ERROR: Failed to claim interface




On Wed, Feb 19, 2020 at 5:52 PM Kayak via Groups.Io
<kayak1176@...> wrote:

Joerg, thank you maybe that is the "simple thing" preventing this?

Would this otg adapter cable suffice, do you think?

amazon.com/Cable-Matters-2-Pack-Adapter-Inches/dp/B00GM0OZ4O

On Wed, Feb 19, 2020 at 11:20 AM Joerg-ex DB2OO <exDB2OO@...> wrote:

Kayak,
it seems to me, that you place the OTG adapter at the NanoVNA and not at the smartphone. Why do you need otherwise the"...USB-A


Re: A Good source for Calibrated Loads in formats other than SMA - #calibration

 

Referring to the OP reference, they look a lot like N male to to SMA female adapters with a male SMA O/S/L screwed onto them.
So you can as well buy one N male to SMA female adapter for 3$ on eBay

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


Re: errors of "error" models

 

#107': On the Missing Terms in NanoVNA firmware - ERRATUM

Dear Erik,

Thank you very much indeed for your valuable comment,
since you forced us to recheck the related code.

No, we can not explain that, simply because we erroneously
noticed this absence.

We are terribly sorry for the inconvenience.
Please accept our apologies.

Hence, we withdrawn this proposition:


Best regards,

gin&pez@arg

:107'#


Re: A Good source for Calibrated Loads in formats other than SMA - #calibration

 

A direct link


Re: NanoVNA-Saver and the new _H4 firmware

David Fragale
 

Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z" even though I specified it be displayed and the control page actually showing it was supposed to be present/displayed ??Other than the NanoVNA being sensitive to the lay of the USB cable in the vicinity of the UUT ( which is a lot easier to counteract if you ditch the short USB jumper supplied and switch to a 3 ft. cable ( and add? ferrite shells on the ends around the uUSB connector? housings)? . That longer cable gives you the chance to actually elevate a UUT and puts your body proximity effect as far away as possible .
? DWF , KA4CNPIn a message dated 2/20/2020 12:51:40 PM Eastern Standard Time, herbwalker2476@... writes:

? I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report.? My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.

? I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.

- Herb


Re: nanovna saver display

Glen K4KV
 

Thank you Stefano!? I will try that tonight.

73

Glen K4KV

On 2/20/2020 13:54, stefano bello wrote:
Hi Glen,

IMHO it is only a problem of resetting charts.
As you have a frequency range problem:
1) Point the mouse cursor on the chart that show the wrong behaviuor.
2) right click to show the chart management menu.
3) On such menu left click Reset because the VNA Saver could have some "memory" of previous measurement
4) Then always on this menu choose Frequency axis and left click on Automatic
5) Alternatively you can choose Frequncy axis then customize the minimum and maximum frequency.
Sometime the problem is on Data Axis ( vertical ) and the chart management menu can help too.

Stefano I3VBP



Re: nanovna saver display

 

Hi Glen,

IMHO it is only a problem of resetting charts.
As you have a frequency range problem:
1) Point the mouse cursor on the chart that show the wrong behaviuor.
2) right click to show the chart management menu.
3) On such menu left click Reset because the VNA Saver could have some "memory" of previous measurement
4) Then always on this menu choose Frequency axis and left click on Automatic
5) Alternatively you can choose Frequncy axis then customize the minimum and maximum frequency.

Sometime the problem is on Data Axis ( vertical ) and the chart management menu can help too.

Stefano I3VBP


Re: A Good source for Calibrated Loads in formats other than SMA - #calibration

 

Another good source for Precision with full specification are Rosenberger (German) sold by www.sdr-kits.net


Re: #nanovna-h4 stops at boot screen #nanovna-h4

 

Ken,
I upgraded to version 1.3 and have been running various tests for about an hour without noticing any persistent stray display artifacts. Thanks for the release and I'll let you know if I experience any ver 1.3 related issues.

Another member has reported a NanoVNA-saver calibration issue after loading ver 1.3, but so far I have not been able to duplicate it with my NanoVNA-H4.

- Herb


Re: NanoVNA-Saver and the new _H4 firmware

 

I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report. My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.

I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.

- Herb


Re: errors of "error" models

 

Can you explain why they are needed given the current content of eterm_calc_er?

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


NanoVNA-Saver and the new _H4 firmware

 

Hello? Ken and Rune,
I flashed the new firmware version 1.3? of today into my NanoVNA-H4 and tried to calibrate the device in NanoVNA-Saver; Sorry I have to say that 4 times in a row NanoVNA-Saver aborted when I press "apply" after the calibration being? done , then I stopped trying. ?? ? ? ?? ? ?? ? ? ? I never have experienced this behavior when using the previous firmware.
Stand-alone the device operates normally , as far as I can see.
Kind regards,
Jos

Op 20-2-2020 om 14:02 schreef Ken Liao, AA6KL:

Kurt and Herb,

I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue.



Ken


Re: Anyone had news from Maggie King?

 

My timing was impeccable - I ordered via PayPal/email just before the start of Chinese New Year. As soon as that ended, the Corona virus threw everything in a state of confusion. I exchanged a few messages with Maggie where she informed me of the delays.

Just this morning, Sophia sent me the DHL tracking number, so I think all is well.


Re: nanovna saver display

Glen K4KV
 

I was working only on the PC.? I saw in the pdf document where they seemed to change

the sweep range to a sub-set of the main calibration range, and the graphic areas also changed

to the new sweep frequencies.? It did not work for me!

73

Glen K4KV

ps - I have used the program myVNA for a long time with the N2PK VNA.? It works like I just said:

when you change the sweep to a subset of the main cal range, the display graphics match the subset.

If one attempts to sweep outside the main cal range, the program tells you it does not like that!

On 2/20/2020 08:14, gary wrote:
Did you change the sweep on the nano or using NanoVNA-saver. I think you need to do the latter.


Re: errors of "error" models

 

#107 : On the Missing Terms in NanoVNA firmware

Hello,

Allow us, please, to propose the following modifications remarked by "//" :



Sincerely,

yin&pez@arg

REFERENCES

[I] : errors in "error" models :
[#08] : 25.09.2019 : /g/nanovna-users/message/3004
[#11] : 25.09.2019 : /g/nanovna-users/message/3049
[#11]' : 25.09.2019 : /g/nanovna-users/message/3041, by Gary O'Neil, N3GO
[#15] : 26.09.2019 : /g/nanovna-users/message/3147

[II] : error model(s) : 18.09.2019 : /g/nanovna-users/message/2553 :
REF [2] :