¿ªÔÆÌåÓý

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

NanoVNA application by OneOfEleven #applications


 

What is the max frequency set? I cannot do 2000MHz (v0157, H4 108fw).
Also the BW - sometimes it takes over what has been set in H4, once it overwrites the H4, not sure I understand it how it should work.


 

On Mon, Aug 3, 2020 at 09:23 PM, igor-m wrote:


What is the max frequency set? I cannot do 2000MHz (v0157, H4 108fw).
ok, I can set for example 1500MHz or 2000MHz but it disconnects the H4 from serial, it also offers to save the .bmp file when clicking on Scan.


 

On Mon, Aug 3, 2020 at 08:23 PM, igor-m wrote:
What is the max frequency set? I cannot do 2000MHz (v0157, H4 108fw).
Also the BW - sometimes it takes over what has been set in H4, once it
overwrites the H4, not sure I understand it how it should work.
Do you mean the "bandwidth" settings Igor ?

If so, that is not the scan frequency, that is the baseband bandwidth, which can be set to 10Hz to 4000Hz .. NOT MHz

The baseband bandwidth is the bandwidth seen by the VNA at each scan spot frequency as it scans across the scan range. The higher the baseband bandwidth the faster the VNA scans, so low bandwidth settings make the VNA scan very slowly.


 

Do you mean the "bandwidth" settings Igor ?
Nope, I talk stop frequency.
Setting for example 1500MHz or 2000MHz disconnects the H4 from serial, it also offers to "save the .bmp" when clicking on Scan.

Bandwidth is a different issue..


 

The maximum that the software will do is just over 4.1GHz (unsigned 2^32), not sure what's going wrong for you.

Can you maybe show me the comms window output, see what it's actually sending to the VNA ?


 

After entering a new frequency in Start or Stop fields and pressing the Enter it disconnects from the H4.


 

Try the latest Igor, let me know if it's still wrong.

v.0.1.59


 

v0159 does not disconnect the serial.
Editing the Start/Stop fields changes the actual scanning range only after pressing Enter.
The Enter stops scanning - thus you have to start the scan again by pressing Scan (aka Sweep).


 

It ought to be working, not sure what might be wrong yet.

This is on my little VNA-H.

Not very good up at 2.7GHz but it's doing it.


 

On Tue, Aug 4, 2020 at 02:36 PM, igor-m wrote:
v0159 does not disconnect the serial.
Editing the Start/Stop fields changes the actual scanning range only after
pressing Enter.
The Enter stops scanning - thus you have to start the scan again by pressing
Scan (aka Sweep).
Yes I know, I was having problems in the early days with previous/current scans coming in and changing the scan range at the same time, so I made it stop the scan whilst your editing the scan range - at least for now.

But it's always been like that, though pressing enter is new.


 

On Tue, Aug 4, 2020 at 06:39 AM, OneOfEleven wrote:


Not very good up at 2.7GHz but it's doing it.
To get an impression of the usability it is useful to look at the phase of an open S11 i.s.o the magnitude of the noise
Often at higher frequencies the magnitude is determined by various harmonic products created inside the SA612
As soon as the phase loses correlation while there still seems to be magnitude you know you are in trouble

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


 

On Tue, Aug 4, 2020 at 03:39 PM, OneOfEleven wrote:


It ought to be working, not sure what might be wrong yet.

This is on my little VNA-H.

Not very good up at 2.7GHz but it's doing it.
This freshly calibrated (OSL) with stock coax and load. Latest fw from github.
Your little VNA-H looks good, imho..


 

On Tue, Aug 4, 2020 at 06:39 AM, OneOfEleven wrote:

It ought to be working, not sure what might be wrong yet.
This is on my little VNA-H.
Not very good up at 2.7GHz but it's doing it.
=========================================
Working very nicely on my H4 with DiSlord v1.0.11 and your v0.1.59 (see attachment).

- Herb


 

And my H4 calibrated with stock coaxes and loads, and with 0db -3db and -23db (3+20) attenuators.
FW - ~latest github source.


 

I've finished off the firmware upload code but I canonly test on my little NanoVNA-H (STM32F072 MCU), I can't test on the H4, so proceed with caution.

If you try it and it fails then do let me know, and also make sure you have an ST-Link of some sorts to hand to recover your VNA.


 

And try not to upload a .HEX file - for now.

Stay with .DFU or .BIN files - for now.


 

OneOfEleven.
Error in FW by DiSlord.
It looks Ok with your FW.
73.


 

On Tue, Aug 4, 2020 at 11:36 AM, OneOfEleven wrote:


And try not to upload a .HEX file - for now.

Stay with .DFU or .BIN files - for now.
87189 bytes loaded OK from G:\Github\forkNanoVNA\nanoVNA-H4 v1.0.12 beta.dfu
Invalid number of DFU elements [2]


 

Could have your DFU file DiSlord to use and fix the problem with ?

It's not a bug, just a small limit I have placed on the DFU file format, I can modify to allow more DFU types.

What did you use to compile to the DFU file with I wonder ?


 

I use DfuSe v3.0.6 from STM