¿ªÔÆÌåÓý

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

Re: DIY loads

James R. Chastain
 

Thanks. Just what I wanted.

On Wednesday, September 18, 2019, 10:41:26 PM EDT, w0lwa <trberger@...> wrote:

Rod

Have a look at

and start reading on page 24 of




On 9/18/19 9:35 PM, James R. Chastain via Groups.Io wrote:
Any problems making your own calibration loads? 50 ohm non inductive resistor and a shorted connector or am I missing something?
KD0XX (Rod)



--
=============================================
Thomas R. Berger? ? ? Emeritus Professor
53 Kendal Drive? ? ? Mathematics Department
Oberlin, OH 44074? ? Colby College
K1TRB? ? ? ? ? ? ? ? Waterville, ME 04901
=============================================


Re: NanoVNA Saver - bug report?

 

Hi Nick,
please try putting the full path to the file in the field, not just the
file name. It may be a matter of which folder the software sees as its
working folder (generally controlled by your OS).

I liked the firmware message as well, but I haven't found a nice place to
put it, and several people were having problems running out of screen real
estate - so for now, it's no longer shown. I'd love to have it back, though.

--
Rune / 5Q5R

On Thu, 19 Sep 2019 at 21:03, Nick <g3vnc@...> wrote:

Hi Rune

thank you so much for this application which I have been using to good
effect this past week with the nanoVNA.

I think there may be a problem with saving and loading calibrations.

Yesterday I did a calibration which I called full_sweep. The full_sweep
file was saved to the nanovna-saver directory, and I could shutdown
nanovna-saver, restart it, and load the calibration.

Today it will not load. I get this

2019-09-19 19:49:53,703 - NanoVNASaver.Calibration - ERROR - Failed
loading calibration data: [Errno 2] No such file or directory: 'full_sweep'
Traceback (most recent call last):
File "/home/nick/nanovna-saver/NanoVNASaver/Calibration.py", line
430, in loadCalibration
file = open(filename, "r")
FileNotFoundError: [Errno 2] No such file or directory: 'full_sweep'

The file is still present. Is this a problem with directory paths?

73
Nick
G3VNC

PS: I used to like the build date message from the firmware when you
first connected to the device!

On 18/09/2019 21:36, Rune Broberg wrote:
I just released 0.0.10:




Re: Firmware summary

 

I agree and was going to put forth the same request as Rudi just did:

On Thu, Sep 19, 2019 at 02:39 PM, <reuterr@...> wrote:

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

Then you could look up what version is actual flashed.
Due to an ever-increasing number of NanoVNA firmware developers providing binaries on this forum (I think it's up to 5 now) and building different variations and/or experimental versions, I (and others) have a request to make of those same developers:

Please use the NanoVNA's boot-up central message field to provide at least the developer's forum name along with their version number (or date) and possibly included options.

All Nano F/W versions I download are archived and labeled with the developer name, date, F range and any other options along with any sub-version numbers if updates come out.
It could be automated through the make file for convenience.

How do the developers (you know who you are) feel about this?

73
Larry


Re: NanoVNA Saver - bug report?

 

Hi Rune

thank you so much for this application which I have been using to good effect this past week with the nanoVNA.

I think there may be a problem with saving and loading calibrations.

Yesterday I did a calibration which I called full_sweep. The full_sweep file was saved to the nanovna-saver directory, and I could shutdown nanovna-saver, restart it, and load the calibration.

Today it will not load. I get this

2019-09-19 19:49:53,703 - NanoVNASaver.Calibration - ERROR - Failed loading calibration data: [Errno 2] No such file or directory: 'full_sweep'
Traceback (most recent call last):
File "/home/nick/nanovna-saver/NanoVNASaver/Calibration.py", line 430, in loadCalibration
file = open(filename, "r")
FileNotFoundError: [Errno 2] No such file or directory: 'full_sweep'

The file is still present. Is this a problem with directory paths?

73
Nick
G3VNC

PS: I used to like the build date message from the firmware when you first connected to the device!

On 18/09/2019 21:36, Rune Broberg wrote:
I just released 0.0.10:


Re: Firmware summary

 

Hello Erik,
Thank you for adding your extension to the Hugen nanoVNA version 0.1.1.

It would be nice to fill out in the "version window" the version number,
e.g.: 0.1.1 + scan, 1500MHz

Then you could look up what version is actual flashed.

I am working mainly with MacOS.
In case you use the program "dfu-util" on Linux or MacOS for flashing, the USB vendor ID is 0000 in your .dfu file, and you cannot flash.
Error message: dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)

In this case I have to transfer your .dfu file to Windows, use DfuFileMgr.exe to convert your file to .hex,
and convert it back to format .dfu with entering the USB vendor ID: DF11.
Then copy it back to MacOS and use dfu-util for flashing.

Therefore it would be also nice to add the USB vendor ID : DF11 to your .dfu file.

73, Rudi DL5FA


Re: nanoVNA Output Voltage

 

Some clarification from my earlier measurement.

The Measurement output from CH0 ranges from -13 dBm at 55 kHz to -36 dBm at 900 MHz..... a more than 23 dB variance.

Beginning at the first increment above 300 MHz the Measurement output switches from fundamental to 3rd harmonic. So, for example, when measuring at 330 MHz the 330 MHz Measurement output being used will be at -19 dBm the there will also be a much higher power fundamental signal output at 110 MHz at -9 dBm. The Nanovna ignores this fundamental frequency by virtue of its heterodyne mixing but users should be aware of its presence when performing S21 measurements of preamps and the like. These relatively high power fundamental frequencies can easily overload amplifiers and distort measurement results.

Another example: The Measurement output at 900 MHz is way down at -36 dBm but the 300 MHz fundamental that is generating that measurement frequency is also present at a whopping -9 dBm, nearly 30 dB higher! User beware!

Warren Allgyer


Re: NanoVNA LNA S21 & S11

 

Hi hwalker.Very thanks for answering my post & i read before your procedure. So the S11 isn't interesting in the LNA Performance.
Regards.


Re: nanoVNA Output Voltage

 

The output power of the SI5351 is automatic set depending the requested sweep frequency, 2mA below 300MHz, 8mA above 300MHz
Similar for a manually set fixed output frequency using the freq command

You can manually control the power through console by issuing

power [0-3]

The power is in small steps controlling the SI5351 current into the output attenuator
0->2mA
1->4mA
2->6mA
3->8mA

Issuing
power -1
sets the nanoVNA again in automatic power mode

If you report output power please indicate at which power setting the output is generated.


Re: nanoVNA Output Voltage

 

Hi, Andy,

we had the same idea, I measured the output and the frequency accuracy on the weekend. It is very bad if there are 5 kHz difference, e.g. on LF...the band is < 2kHz wide.
I have set the measurement results under Photos, Output to frequency.

Measuring equipment Advantest R3131 with Rubidium-10MHz reference.

73 Joe


Re: A bit off topic, but Nano VNA related.

 

Why not try the following console commands through a script:

pause (the scanning - still generates output)

now loop the following via a data driven stream...
freq 1000000
(wait)
freq 1000005

I don't know how fast these commands can be sent - talk to Rune (nanovna-saver author)

73
Larry


A bit off topic, but Nano VNA related.

Andy G0FTD
 

I just checked my NanaoVNA output and frequency accuracy, utterly superb.

Good enough to generate WSPR signals, or simple FSK/CW QRSS signals.

The latter are normally send with a 5Hz shift, with a dot length of 6 seconds.

Is there a simple way to use the VNA to generate such signals via USB ?

73 de Andy


Re: nanoVNA Output Voltage

Andy G0FTD
 

I just measure 100mv peak into 50R at 50Khz to 50Mhz (-10dbm)
At 70Mhz it was 70mv (convenient to remember).
I was amazed at how accurate the out put frequency was according to my GPS calibrated freq counter too.

73 de Andy


Re: nanoVNA Output Voltage

 

I think the -10 dBm number is based on conversion of the unterminated voltage. My unit puts out -17 dBm at 100 MHz and -19 dBm at 900 MHz when properly terminated in a 50 ohm load. This level is consistent with other Si5351 devices I own.

One of those devices is the RFzero board which is a GPS referenced, Arduino based synthesizer. It comes with some very nice beacon software that allows it to run WSPR up to 1.5 GHz using harmonics of the Si5351. I have mine operating on 23 cm and get good WSPR decodes using the fifth harmonic.

Warren Allgyer
WA8TOD


Re: NanoVNA Saver 0.0.9 screen size and saving screen questions

 

Hi Rune:

Keep up the great work - you're an indispensable asset!

You might try thinking a little bit laterally. Other similar python programs I use (like the qspectrum sdr data analyzer) split the window into two sections; one contains the graphs - it scales within limits to track screen size but doesn't scroll, and the second is a sidebar which contains all data and settings and scrolls as desired - with less essential things at the bottom.

I think some of the QT screen designer programs generate platform adaptation code that helps with these problems.

In any case, thanks for working on this problem. I know it's hard to keep a balance at this stage of development between getting the core functionality stable and making the program pretty!

M


Re: Electrical Delay_Port Extension

 

Hi hwalker
Ok with your commercial kit, if I am guessing right you do not have the cal kit data ?
The HP male load I have a couple of these and are far from impressed. I have also a BNC special made cal kit characterized against a Rosenberger professional kit with full documentation so I have a made a couple of BNC kit like on the photo with calibration plane data. However if used as ideal kit the calibration is super but of course not at the calibration plane.
The male adaptors are special made as quick insert which I do not think is in the trade so lucky me ?
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af hwalker
Sendt: 19. september 2019 14:02
Til: [email protected]
Emne: Re: [nanovna-users] Electrical Delay_Port Extension

Kurt,
Thanks for the comments. I am fortunate to have a commercial BNC VSWR kit that came with OSL standards plus various mismatches. I picked it up from an engineer's estate sell and was able to verify the kit's performance up to 1 GHz using a HP8753C VNA. The kit is my gold standard against which I verified my everyday use home made BNC OSL. The home made BNC OSL (see attached photo) pretty much follow your construction suggestions, except the 50 ohm load is an HP11593A (picked up two at the same estate sell). I was told the commercial VSWR kit was manufactured by Berkeley labs but have not been able to verify that info.


Re: NanoVNA Saver 0.0.9 screen size and saving screen questions

 

That looks the business allright :)

On Thu, Sep 19, 2019 at 02:25 PM, Rune Broberg wrote:


Jeffrey,
I've worked slightly more on the ideas you presented, and just pushed an
update that makes it *nearly* fit on a 768 pixel screen. It does actually
fit, I believe, if you hide the task bar. I think that's as good as it's
going to get for today :-)

It should probably fit with font size 7, I think anyway. :-)

--
Rune / 5Q5R

On Thu, 19 Sep 2019 at 07:07, Jeffrey Vandenbroucke <jeffrey@...>
wrote:

CollapsibleBox(QtWidgets.QWidget) would be handy - you can "hide" controls
you don't need then.

For myself, I patched the charts to be 300px in height max. Ditched the
s11_control_box and s21_control_box (and the setText statements); as I can
read that with markers. Font size set to 7; and removed the about box. Now
it fits snug inside my (small) display.




Re: NanoVNA Saver 0.0.9 screen size and saving screen questions

 

Jeffrey,
I've worked slightly more on the ideas you presented, and just pushed an
update that makes it *nearly* fit on a 768 pixel screen. It does actually
fit, I believe, if you hide the task bar. I think that's as good as it's
going to get for today :-)

It should probably fit with font size 7, I think anyway. :-)

--
Rune / 5Q5R

On Thu, 19 Sep 2019 at 07:07, Jeffrey Vandenbroucke <jeffrey@...>
wrote:

CollapsibleBox(QtWidgets.QWidget) would be handy - you can "hide" controls
you don't need then.

For myself, I patched the charts to be 300px in height max. Ditched the
s11_control_box and s21_control_box (and the setText statements); as I can
read that with markers. Font size set to 7; and removed the about box. Now
it fits snug inside my (small) display.




Re: NanoVNA LNA S21 & S11

 

Said,
I posted this procedure earlier that I used to check the gain of a RF preamp. The device under test was a Mini-Circuits preamp with a handwritten note saying, "27 dB gain, 1-1000 MHz".

Test procedure used:
1. Turn the amplifier on to allow it to warm up and also to guard against turn on transients damaging the nanoVNA during testing.
2. Turn on the nanoVNA, set the display to CH1/LOGMAG only, 10 dB per DIV, reference position at 4 divisions to be able to see 27 dB gain.
3. Connect a 20 dB attenuator to CH1 and a 6 dB attenuator to CH0 to closely match the expected 27 dB gain of the preamp.
4. Connect attenuators together using a cable. The nanoVNA should be displaying a 26 dB loss over the frequency range. If not your attenuators are not flat
5. Change to the calibrate menu and select "reset" and then perform a "through" calibration. The new reference should be 0 dB at 4 divisions.
6. Connect the output of the 6 dB attenuator to the input of the amplifier and output of the amplifier to the 20 dB attenuator.
7. Read the amplifier gain in dB directly off the nanoVNA using the marker display.

The above only checks the S21 performance of the preamp. That was all I was interested in at the time.


Re: Electrical Delay_Port Extension

 

Kurt,
Thanks for the comments. I am fortunate to have a commercial BNC VSWR kit that came with OSL standards plus various mismatches. I picked it up from an engineer's estate sell and was able to verify the kit's performance up to 1 GHz using a HP8753C VNA. The kit is my gold standard against which I verified my everyday use home made BNC OSL. The home made BNC OSL (see attached photo) pretty much follow your construction suggestions, except the 50 ohm load is an HP11593A (picked up two at the same estate sell). I was told the commercial VSWR kit was manufactured by Berkeley labs but have not been able to verify that info.


Re: NanoVNA LNA S21 & S11

 

Very thanks for quick answer qrp.ddc. I made the 2nd manipulation with 20db connected to ch0 & ch1 and turned the Orange & blue traces & have had the S21 & S11.I think i was wrong.
The amplifiers are 20-24db 2m band.
I made a calibration with the 2 Attenuatos connected to have a zero instead of 40db.
Very thanks for infos & 73s dr qrp.ddc