¿ªÔÆÌåÓý

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

Re: Nanovna Saver stopped working

 

On Mon, Jan 30, 2023 at 10:44 PM, Fkawee wrote:


As mentioned it used to work until ubuntu upgraded itself (with my permission
yikes) to 20.04.
When I click on the exe file I get no response.
Why do you try the "exe" on a Linux system? - just follow my advice from below - open a terminal, go to a project or development directory and do this (maybe you need to install git: "sudo apt install git").

git clone

Then enter the directory:
cd nanovna-saver

and just type
python nanovna-saver.py

Check the error messages (missing modules) and install them, e.g. these are essential:
sudo apt install python3-numpy python3-scipy

until the program starts without complaint.

To follow the development, just fetch an update with
git pull

If you want to install the tool in your path, you can create a Debian package by typing
make deb
For this you need to install python3-stdeb, the module for converting Python code and modules to a Debian package.
sudo apt install python3-stdeb

You need also an udev rule that allows user access to the USB serial port of NanoVNA and tinySA.
This is currently not part of the package - just use this one and install it into /etc/udev/rules.d:



Martin


Re: Nanovna Saver stopped working

 

Hi,

I guess its wine that has stopped working after the upgrade. Can you run
any other Windows (exe) programs on your computer? (Something like LTSpice)
Check the software center if wine is installed. If it is, and you are not
able to run any windows programs, you need to search for help on fixing
wine.

Or, you could run the python version of nanovna saver instead. Instructions
should be in the repository.


Regards,
Askild

On Mon, Jan 30, 2023 at 10:44 PM Fkawee <frankw259@...> wrote:

Thanks for the response guys.
Please forgive me, as I am a little weak using linux.
Can you elaborate more on how you got it to work?
As mentioned it used to work until ubuntu upgraded itself (with my
permission yikes) to 20.04.
When I click on the exe file I get no response.
Thanks again all.






Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

You most likely had a weird chip and firmware combo too. Take it as a
learning experience.

- know your hardware
- make backups of firmware (ideally 2x & crc)
- check if updates are compatible with your device, only flash if you¡¯re
100%sure.
- learn jtag level reflashing for the device.

As for the GD, glad my tip helped point things in the right way.


-John


Op ma 30 jan. 2023 om 20:21 schreef Al Waschka <awaschka@...>

This gave me an idea.

Does the reverse apply? If the manufacturer used STMCube, could I have
successfully loaded an old NanoVNA dfu with DfuSE-Demo which ran with
anomalies but then when I tried to load a different version the computer
would not recognize the device being plugged in when booted with jogwheel
pressed?
On Jan 30, 2023, at 1:31 PM, Ray WW0AW via groups.io <hrpch=
[email protected]> wrote:

? This is great !!! Thank you my friend, for the files with full dump of
GS-400 which is just what I needed.
You're right, I destroyed the bootloader so I cannot use either
NanoVNA-App or QTbut I already verified that I can communicate to the MCU
via STLinkso I'll go ahead and flash it keeping my fingers crossed....I'll
return with good news of success.
On Sunday, January 29, 2023 at 09:54:19 PM CST, DiSlord <
dislordlive@...> wrote:

Read better....

You use STM-Cube, so you destroy bootloader (need use NanoVNA-App or QT
for update in bootload mode)
Upload this in 0x08000000 address as before
4-inch-GD32F303CCT6-20200619 FULL.bin
















Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

On Mon, Jan 30, 2023 at 03:56 AM, PDXer wrote:

Does it need new calibration every time when different frequency range is selected?
Yes.


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

that is still an older fw .. but at least you have a working unit with a working bootloader (so your pc should find it)

dislord sure has a newer fw for it ... 17th (19th) of june 2020 is VERY old! (why 17th (and 19th in brackets)?? see version NUMBER .. there you fint the 17 ... and below that when it was compiled (2 days later it seems) ...but .. it is from 2020!! and i surely know that we have many many new versions since that year

... DISLORD?? what is newest he can throw on his unit?? 1.309?? or even newer like the 1.312??

(he sure can better answer what fw is newest from his workbench) ... that one he sent is not new but it works (to realive your unit)

and soon he wil tell you what is newest fw that matches (i bet he has a 1.312 or so if not newer)

greetz sigi dg9bfc



Am 31.01.2023 um 02:50 schrieb Ray WW0AW via groups.io:

20200617-1a9a11d
Jun 19 2020




Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

Ray WW0AW
 

20200617-1a9a11d
Jun 19 2020


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

Ray WW0AW
 

With DisLord's help I was able to unbrick it !!!!


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

GOTCHA! :-)

what fw do you now have on what unit??

dg9bfc sigi


Am 31.01.2023 um 02:38 schrieb Ray WW0AW via groups.io:

U N B R I C K E D !!!
The problem was the STM32CubeProgrammer I got is buggy,
so I switched to the older STLINK Utility and it worked like a charm.
Thank you my friend.!!!




Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

Ray WW0AW
 

U N B R I C K E D !!!
The problem was the STM32CubeProgrammer I got is buggy,
so I switched to the older STLINK Utility and it worked like a charm.
Thank you my friend.!!!


Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

There is one particular use case where no calibration is needed at all, and that is when tuning a magnetic loop or similar antenna, where the only adjustment is resonant frequency. The S11 VSWR/log mag dip will be at the same frequency regardless of calibration status.
73, Don N2VGU


File /NanoVNA Upgrade Failure.pdf uploaded #file-notice

Group Notification
 

The following files and folders have been uploaded to the Files area of the [email protected] group.

* /NanoVNA Upgrade Failure.pdf ( /g/nanovna-users/files/NanoVNA%20Upgrade%20Failure.pdf )

*By:* Al Waschka <awaschka@...>

*Description:*
This is a description of the process I went through in my initial NanoVNA acquisition including the problems I found and my (unsuccessful) attempts to correct them. I have published this in hopes that it might be helpful to someone else. If you have any idea what the actual problem(s) was(were), please let me know so I can avoid it in the future.


Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

On Mon, Jan 30, 2023 at 02:25 PM, David Rounds wrote:


Depending on your firmware version, you can save multiple sets of
calibration data.

I saved all five sets in my nano, specifically, 3 Mhz to 15 Mhz, 15 Mhz
to 30 Mhz, 3 Mhz to 30 Mhz, 143 Mhz to 149 Mhz, and 420 Mhz to 450 Mhz,?
I then load the calibration data as needed for the antenna span being
checked.

David
AK9F

On 1/30/2023 5:42 AM, PDXer wrote:
Does it need new calibration every time when different frequency range is
selected?
Or is it enough just one initial full freq. calibration?




Yeah, I think my set allows 6 or 7 setting savings, and can recall them I remember in the menu.
It seems a great idea. Putting on the tiny Open Short Load bits unto the SMA port and taking them out can be a bit of pain, if it has to be done often. But saving and recalling the calibration settings for most commonly used frequency ranges sounds solving the problem. cheers. 73.


Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

Great info & advice. Thanks.


Re: Nanovna Saver stopped working

 

Thanks for the response guys.
Please forgive me, as I am a little weak using linux.
Can you elaborate more on how you got it to work?
As mentioned it used to work until ubuntu upgraded itself (with my permission yikes) to 20.04.
When I click on the exe file I get no response.
Thanks again all.


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

The dfu tool and STMCube are interchangeable - Cube just has a lot more features (and runs on a lot more platforms). I have had zero issues using them interchangeable on my -H4 . . .

On January 30, 2023 1:21:05 PM CST, Al Waschka <awaschka@...> wrote:
This gave me an idea.

Does the reverse apply? If the manufacturer used STMCube, could I have successfully loaded an old NanoVNA dfu with DfuSE-Demo which ran with anomalies but then when I tried to load a different version the computer would not recognize the device being plugged in when booted with jogwheel pressed?
On Jan 30, 2023, at 1:31 PM, Ray WW0AW via groups.io <hrpch@...> wrote:

? This is great !!! Thank you my friend, for the files with full dump of GS-400 which is just what I needed.
You're right, I destroyed the bootloader so I cannot use either NanoVNA-App or QTbut I already verified that I can communicate to the MCU via STLinkso I'll go ahead and flash it keeping my fingers crossed....I'll return with good news of success.
On Sunday, January 29, 2023 at 09:54:19 PM CST, DiSlord <dislordlive@...> wrote:

Read better....

You use STM-Cube, so you destroy bootloader (need use NanoVNA-App or QT for update in bootload mode)
Upload this in 0x08000000 address as before
4-inch-GD32F303CCT6-20200619 FULL.bin














--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

 

This gave me an idea.

Does the reverse apply? If the manufacturer used STMCube, could I have successfully loaded an old NanoVNA dfu with DfuSE-Demo which ran with anomalies but then when I tried to load a different version the computer would not recognize the device being plugged in when booted with jogwheel pressed?

On Jan 30, 2023, at 1:31 PM, Ray WW0AW via groups.io <hrpch@...> wrote:

? This is great !!! Thank you my friend, for the files with full dump of GS-400 which is just what I needed.
You're right, I destroyed the bootloader so I cannot use either NanoVNA-App or QTbut I already verified that I can communicate to the MCU via STLinkso I'll go ahead and flash it keeping my fingers crossed....I'll return with good news of success.
On Sunday, January 29, 2023 at 09:54:19 PM CST, DiSlord <dislordlive@...> wrote:

Read better....

You use STM-Cube, so you destroy bootloader (need use NanoVNA-App or QT for update in bootload mode)
Upload this in 0x08000000 address as before
4-inch-GD32F303CCT6-20200619 FULL.bin











Re: "Bricked" after attempt to update FW #nanovna-v2 #firmware #crash #newbie #flashing

Ray WW0AW
 

This is great !!!?Thank you my friend, for the files with full dump of GS-400 which is just what I needed.
You're right, I destroyed the bootloader so I cannot use either NanoVNA-App or QTbut I already verified that I can communicate to the MCU via STLinkso I'll go ahead and flash it keeping my fingers crossed....I'll return with good news of success.

On Sunday, January 29, 2023 at 09:54:19 PM CST, DiSlord <dislordlive@...> wrote:

Read better....

You use STM-Cube, so you destroy bootloader (need use NanoVNA-App or QT for update in bootload mode)
Upload this in 0x08000000 address as before
4-inch-GD32F303CCT6-20200619 FULL.bin


Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

Brian Wilkins
 

Jim

I calibrate a coax pig tail that connects to my antenna system (50ft + UnUn
+ Wire + Counterpoise). That way, I eliminate a known good out of my
measurement by ¡°calibrating out¡± the known good. I have also worked my way
out of diagnosing the antenna system by measuring the window connection,
coax then with unun + antenna + wire. Not sure if this is best practice or
where I learned it. Just seems to make logical sense. How are others doing
it? From posts I have read, it seems people just wing it without any
logical step thru of the antenna system!

On Mon, Jan 30, 2023 at 9:14 AM Jim Lux <jimlux@...> wrote:

On 1/30/23 3:42 AM, PDXer wrote:
Does it need new calibration every time when different frequency range
is selected?
Or is it enough just one initial full freq. calibration?

That depends on the level of accuracy you want. If you do a full range
cal, and then set a narrower range for the measurement, it interpolates
from the full range cal. That may or may not be great (particularly at
the points where it changes which harmonics to use, at N*300 MHz points)

If you cal over, say, 0-900, and there's 100 points, that means there's
a calibrated point every 9 MHz. Leaving aside the "transition points
between harmonics" it's likely that the device's internal errors (what
you're calibrating out) smoothly vary in amplitude and phase between
points.

OTOH, if you are calibrating with a fixture or coax in the system (e.g.
you've got 50 ft of coax, and you're doing the cal at the end of the
coax, to measure your antenna at the feedpoint) then you potentially
have a problem -That 50 ft of coax has multiple wavelengths (and a
different number of wavelengths, depending on frequency) - and 9 MHz
between calibration points may have one or more phase wraps. Now,
linear interpolation might not work so well.

The other thing where you definitely want to recalibrate for the "range
of use" is where you want the best possible measurements. Why
interpolate if you can use real data?

For what it's worth, I cal 0-100 MHz (because it's easy) when working
with HF stuff.

And, if you're using an application (like NanoVNA-Saver, and others)
that does multiple sweeps to get more points in the range, then you can
calibrate with fine resolution over a wide range.






--
73, ko4aqf@...


Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

Depending on your firmware version, you can save multiple sets of calibration data.

I saved all five sets in my nano, specifically, 3 Mhz to 15 Mhz, 15 Mhz to 30 Mhz, 3 Mhz to 30 Mhz, 143 Mhz to 149 Mhz, and 420 Mhz to 450 Mhz,? I then load the calibration data as needed for the antenna span being checked.

David
AK9F

On 1/30/2023 5:42 AM, PDXer wrote:
Does it need new calibration every time when different frequency range is selected?
Or is it enough just one initial full freq. calibration?




Re: NanoVNA H4 OSL calibration question (newbie) #calibration #nanovna-h4

 

On 1/30/23 3:42 AM, PDXer wrote:
Does it need new calibration every time when different frequency range is selected?
Or is it enough just one initial full freq. calibration?
That depends on the level of accuracy you want. If you do a full range cal, and then set a narrower range for the measurement, it interpolates from the full range cal. That may or may not be great (particularly at the points where it changes which harmonics to use, at N*300 MHz points)

If you cal over, say, 0-900, and there's 100 points, that means there's a calibrated point every 9 MHz. Leaving aside the "transition points between harmonics" it's likely that the device's internal errors (what you're calibrating out) smoothly vary in amplitude and phase between points.

OTOH, if you are calibrating with a fixture or coax in the system (e.g. you've got 50 ft of coax, and you're doing the cal at the end of the coax, to measure your antenna at the feedpoint) then you potentially have a problem -That 50 ft of coax has multiple wavelengths (and a different number of wavelengths, depending on frequency) - and 9 MHz between calibration points may have one or more phase wraps. Now, linear interpolation might not work so well.

The other thing where you definitely want to recalibrate for the "range of use" is where you want the best possible measurements. Why interpolate if you can use real data?

For what it's worth, I cal 0-100 MHz (because it's easy) when working with HF stuff.

And, if you're using an application (like NanoVNA-Saver, and others) that does multiple sweeps to get more points in the range, then you can calibrate with fine resolution over a wide range.