¿ªÔÆÌåÓý

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

nanovna hw v3.1 #firmware


 

Hello everyone,

a friend came by to update his nanovna. It is a black nanovna and the QR code redirect to nanovna.com which leads to this forum. So I did pick the latest hugen firmware and the update went well.

After the update, I realized the hardware version is 3.1. I cannot see the traces on smith chart anymore and the battery reading seem to be broken.

Does anyone knows which would be the appropriate firmware for the hw rev 3.1 ?

Thank you for any pointers !


 

Alezis,
Try running a Calibration if you haven't done that already.
I am not sure that will deal with all 3.4 vs 3.1 issues, but it should get traces on the screen unless the configuration settings are way out of line. (That can be fixed, too.)
Let us know what happens.
--John Gord

On Thu, Sep 10, 2020 at 07:59 PM, Alezis wrote:


Hello everyone,

a friend came by to update his nanovna. It is a black nanovna and the QR code
redirect to nanovna.com which leads to this forum. So I did pick the latest
hugen firmware and the update went well.

After the update, I realized the hardware version is 3.1. I cannot see the
traces on smith chart anymore and the battery reading seem to be broken.

Does anyone knows which would be the appropriate firmware for the hw rev 3.1 ?

Thank you for any pointers !


 

Alezis,
ALL of the 2.8 inch nanovna devices can use what-ever is currently being produced for the 'H'.
The H4, F and SAA firmware cannot be used.
Please refer to the nanovna forum Wiki for info on firmware for the devices.
The latest stable firmware from the originator of the nanovna is at

On Thursday, September 10, 2020, 10:59:06 p.m. EDT, Alezis <cldp@...> wrote:

Hello everyone,

a friend came by to update his nanovna. It is a black nanovna and the QR code redirect to nanovna.com which leads to this forum. So I did pick the latest hugen firmware and the update went well.

After the update, I realized the hardware version is 3.1. I cannot see the traces on smith chart anymore and the battery reading seem to be broken.

Does anyone knows which would be the appropriate firmware for the hw rev 3.1 ?

Thank you for any pointers !


 

Hello John,

thank you for the reply ! Much appreciated.

I did try to reset the whole unit, I did reset calibration and tried again to read some values in the smith chart and I only see the dot at the center where I whould see a line for the bandwidth that is set in the stimulus menu.

I also lost the battery level indicator, reading in the about menu show -% value. On one of OneOfEleven firmware I even lost the battery logo indicator completely !!!

SWR reading is displaying the proper trace for the bandwidth set in the stimulus menu but then again, it is quite off.

When you say it can be fixed, how can this be done ?

Thank you for the all the tips !

Alezis


 

On Fri, Sep 11, 2020 at 07:21 AM, Larry Rothman wrote:


Alezis,
ALL of the 2.8 inch nanovna devices can use what-ever is currently being
produced for the 'H'.
The H4, F and SAA firmware cannot be used.
Please refer to the nanovna forum Wiki for info on firmware for the devices.
The latest stable firmware from the originator of the nanovna is at


That is good to know all 2.8 work with the H firmware. This is what I did try and it did not work as per my initial post.

I am aware of the wiki, I went though it in the hope to find information about the hw 3.1 but I did not find anything.

The link you provided does not contain .dfu files though, I am not sure how to obtain one as I do not have the skills to compile any of the code at this point.

Thanks for the edy555 link ! I will try to find the .dfu file somehwere on his page.


 

There is a zipped file in the assets link

Sent from Rogers Yahoo Mail on Android

On Sat, 12 Sep 2020 at 2:32 am, Alezis<cldp@...> wrote: On Fri, Sep 11, 2020 at 07:21 AM, Larry Rothman wrote:


? Alezis,
ALL of the 2.8 inch nanovna devices can use what-ever is currently being
produced for the 'H'.
The H4, F and SAA firmware cannot be used.
Please refer to the nanovna forum Wiki for info on firmware for the devices.
The latest stable firmware from the originator of the nanovna is at


That is good to know all 2.8 work with the H firmware. This is what I did try and it did not work as per my initial post.

I am aware of the wiki, I went though it in the hope to find information about the hw 3.1 but I did not find anything.

The link you provided does not contain .dfu files though, I am not sure how to obtain one as I do not have the skills to compile any of the code at this point.

Thanks for the edy555 link ! I will try to find the .dfu file somehwere on his page.


 

Hi Larry,
I have NanoVNA-H v3.2 with firmware NanoVNA-Q version 0.4.4 from Nov 26 2019
I checked NanoVNA-Q site and they do not have any update so far.

I would like to update to
0.8.0-20200620 but there is no .dfu file only bin, hex and elf files.
I am used to upgrade using a dfu file for Win 7 system.

How can I upgrade without dfu file?


 

Please read the user guide I edit, it's in the files section.?
It tells you how to convert a bin file to dfu.?
The easiest way though is to install one of DiSlord's dfu files. His firmware is in the files section as well.?
Make sure you install for H and not H4.?


On Sat, 12 Sep 2020 at 9:26 AM, Corneliu via groups.io<coralenka@...> wrote: Hi Larry,
I have NanoVNA-H v3.2 with firmware NanoVNA-Q version 0.4.4 from Nov 26 2019
I checked NanoVNA-Q site and they do not have any update so far.

I would like to update to
0.8.0-20200620 but there is no .dfu file only bin, hex and elf files.
I am used to upgrade using a dfu file for Win 7 system.

How can I upgrade without dfu file?


 

On Fri, Sep 11, 2020 at 01:42 AM, John Gord wrote:


Alezis,
Try running a Calibration if you haven't done that already.
I am not sure that will deal with all 3.4 vs 3.1 issues, but it should get
traces on the screen unless the configuration settings are way out of line.
(That can be fixed, too.)
Let us know what happens.
--John Gord
John, how can this be fixed when readings are way out ?

Thanks for your reply !


 

Alezis,

See message 15041 for information on the "clearconfig 1234" command sent with a terminal program. I have never needed to do this, so I don't know what all it may affect. A search of the messages (from the web interface) for "clearconfig" should turn up further information.
A screenshot might help in showing the problem you are having.

--John Gord

On Mon, Sep 14, 2020 at 08:23 PM, Alezis wrote:


On Fri, Sep 11, 2020 at 01:42 AM, John Gord wrote:


Alezis,
Try running a Calibration if you haven't done that already.
I am not sure that will deal with all 3.4 vs 3.1 issues, but it should get
traces on the screen unless the configuration settings are way out of line.
(That can be fixed, too.)
Let us know what happens.
--John Gord
John, how can this be fixed when readings are way out ?

Thanks for your reply !


 

Hi Alezis,

because of my weekend family activities, I just got here.
Please, if the problem is still current, visit my web page where you will find an answer to the solution.
I have v3.0 hardware from NanoVNA (it may be a July 2019 production) that I have converted to be much more capable in its current state. You can read the description here:
I hope you can solve the problem after reading the above.
You can also install the latest firmware.

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***