NanoVNA-H, NanoVNA-H4, LiteVNA64

[KF6BL]

Hi. I have both the -H and -H4 models and can find the firmware on GitHub. I was thinking of getting a LiteVNA64 and was looking for the firmware files for upgrading. Can't seem to find anything. I did see reference to Solver32 and I think one more software package, but nothing regarding the LiteVNA64 firmware.

Is there a location where one finds the firmware like on GitHub? Or possibly somewhere else? Don't want to spend money on a LiteVNA64 if I can't find a source for firmware.

One more question. Like the -H and -H4 the firmware comes in .DFU files. Will the LiteVNA64 also have .DFU files or will it be a different format?

Thanks
Brian D KF6BL

[bingo600]

LiteVNA FW is listed at the manuf. site

https://www.zeenko.tech/litevna

/Bingo

[KF6BL]

Thanks Bingo, I have been there but thought there would be a .DFU file. OK, so at least there is a location for the firmware. Thanks again.

Brian D
KF6BL

[Aldo22]

I'm recycling this thread as it's about a similar question.

I have a new NanoVNA-H v3.6_MS and I think the device is very good for this price.

I have some questions about the firmware options

1. Pre-installed is v1.2.14 from August 22
This version can write to the SD card, but not read it (afaics).
Is it possible to switch to DiSlord v1.2.20 without any problems?
Is it better to wait for a new version of hugen79? Are there any updates to be expected?

2. I have a version with the MS5351M. With hugen79 there are different firmwares for MS5351M and SI5351A, with DiSlord not. Is this a problem?

3. What is the difference between *.dfu and *.bin?
Do you update TinySA with a *.bin and NanoVNA with a *.dfu?
I also would like to update the NanoVNA with "dfu-util" on Linux.

Thanks!

[bingo600]

2. I have a version with the MS5351M. With hugen79 there are different firmwares for MS5351M and SI5351A, with DiSlord not. Is this a problem?

On Dislord , you can select MS in the config (advanced i think), remember to do a "config" save after.

I upgraded to "dislord" on my H4 without problems.

3. What is the difference between *.dfu and *.bin?
Do you update TinySA with a *.bin and NanoVNA with a *.dfu?
I also would like to update the NanoVNA with "dfu-util" on Linux.

I'm using the bin with linux dfu-util.

Remember to turn it on with the "Jog Wheel" pressed down , to boot into dfu-mode.

*** This is for a H4 , you'd want the H's

Code: [Select]

Just download the NanoVNA-H4.bin file and send it to the NanoVNA-H4
$ dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D NanoVNA-H4.bin

HoRo has a repos of the latest dislord's
https://github.com/Ho-Ro/NanoVNA-D/tree/current-bin-hex



Do you know this group , that's where the stuff happens.
https://groups.io/g/nanovna-users/topics

/Bingo

[Aldo22]

Thank you!

Remember to turn it on with the "Jog Wheel" pressed down , to boot into dfu-mode.

The installed Firmware has "Reset and Enter DFU" in the menu. I guess this works as well.

*** This is for a H4 , you'd want the H's

Code: [Select]

Just download the NanoVNA-H4.bin file and send it to the NanoVNA-H4
$ dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D NanoVNA-H4.bin


Another example says:

Code: [Select]

dfu-util -a 0 -D nanoVNA_900_ch_20190505.dfuSo I'm still wondering what is the difference between .bin and .dfu and what it has to do with the different parameter lists.

EDIT:

-s, --dfuse-address [ADDRESS][:LENGTH][:MODIFIERS]

    Specify target address for raw binary download/upload on DfuSe devices. Do not use this option for downloading DfuSe (.dfu) files.

[Aldo22]

It worked with

dfu-util -a 0 -D nanoVNA.dfu

Thank you for your support!

[bingo600]

I just "Pulled the dislord repos from git" , and compiled it for the H , and the H4
Seems like latest is 1.2.24

Code: [Select]

#define VERSION "1.2.24"

Here's the H4 build

Code: [Select]

$/nanovna-h4/Dislord/NanoVNA-D$ ls -l build/
total 3108
-rwxrwxr-x 1 bingo bingo   86508 Jul 29 16:23 H4.bin
-rw-rw-r-- 1 bingo bingo   56924 Jul 29 16:23 H4.dmp
-rwxrwxr-x 1 bingo bingo 1021796 Jul 29 16:23 H4.elf
-rw-rw-r-- 1 bingo bingo  243401 Jul 29 16:23 H4.hex
-rw-rw-r-- 1 bingo bingo 1582548 Jul 29 16:23 H4.list
-rw-rw-r-- 1 bingo bingo  274109 Jul 29 16:23 H4.map
drwxrwxr-x 2 bingo bingo    4096 Jul 29 16:23 lst
drwxrwxr-x 2 bingo bingo    4096 Jul 29 16:23 obj
$
/Bingo

[Aldo22]

I just "Pulled the dislord repos from git" , and compiled it for the H , and the H4
Seems like latest is 1.2.24

I think this is the development version (snapshot).
Latest version (stable) is 1.2.20 afaics.
It is a matter of taste.
For me, 1.2.20 brings the SD card browser that I was missing.

Thank you.

[pienari]

My Lite VNA64 is dead.
I bought it year ago and it is used only few times.
Now it wont start, nothing happens when i plug to charger.

[bingo600]

My Lite VNA64 is dead.
I bought it year ago and it is used only few times.
Now it wont start, nothing happens when i plug to charger.

Wasn't there something with deep discharge

For the 62' model
Hello xxx, there is a problem with the charging circuit of the early release LiteVNA62. When the battery is drained it cannot be reactivated and requires the removal of R98 from the PCB. We apologise for our mistake, the LiteVNA62 will charge back to normal once the R98 is removed and no new battery is required.


For the 64' model
Hello xxx, this resistor is R1 on LiteVNA64. LiteVNA62 and LiteVNA64 use different charging chips, I did not find inability to charge in my test, you can try to remove R1 first, and then charge for 1 hour in the off state.

Answ: I lifted one end of R1 to test.  That took care of the issue.  The LiteVNA64 began charging.

[pienari]

Ohh. Bad battery or bad design.
I can try to charge battery with my lab psu.

What that R1 do, can i just remove it?

With AAI analyzers i have not found any self discharge issue.

[bingo600]

You should join here
https://groups.io/g/liteVNA/topics

That's where the designers (Hugen et all)  are , and the "hardcore stuff" is discussed
https://groups.io/g/liteVNA/topic/charging_issues/88762637

AFAIK the RTC is slowly depleting the Batt ....
https://groups.io/g/liteVNA/topic/97812453

[pienari]

Thank you for all.
Now i have to make few mods to my LiteVNA64.

[Solder_Junkie]

For anyone considering purchasing a Nano VNA, the H4 version can be switched to become a TinyPFA phase frequency analyser simply by loading different firmware. It only takes a minute and equally it can be just as easily returned to operate as a VNA.

Two instruments for the price of one.

A phase frequency analyser is used to compare two oscillators, typically to set the oscillator in a counter or signal generator onto frequency, or to observe drift over a period of time. The TinyPFA works in conjunction with TimeLab software (free). The attached image shows it being used to compare different loop time settings in a home made GPS disciplined oscillator, the reference was a rubidium oscillator. It’s incredible what can be achieved using low cost instruments on a home work bench.

SJ