开云体育

Hello everyone.

I would like to know where can we find a changelog related to the firmware released.

Also, what would be the difference between nanovna_800 vs nanovna_900 firmware?

Thanks in advanced,

Luís CT2FZI

Oh btw, does anyone have a screenshot of the AA version? I would like to have a look if its useful, as in buying a second unit just for field work powered by a USB power bank ;)

Cheers!

Luis CT2FZI

The 800MHz firmware works better at higher temperatures. But what does that mean in practice, what are the FW differences?

Cheers!

The si5351 manual shows that the internal VCO operates at a maximum of 900MHz and a 4-divide-frequency output with a maximum frequency of 225MHz. In order to output a frequency of 300MHz, the internal VCO needs to be overclocked to 1200MHz. Not every si5351 can be stably overclocked to 1200MHz. As the temperature increases, the internal VCO operating limit frequency of the si5351 will decrease. If you notice a significant spike(>0dB) in your nanoVNA at 300 MHz or 900 MHz, I recommend that you use the 800MHz firmware.

Thank you!

Hello,

I thank you Hugen for your reply. Now its clear, and over 800MHz I don't have any interest so I played safe and already flashed the 800MHz version.

Where can one find the FW change log? (Maybe I find some reasons to skip upgrade and wait for the next one)

Where can one find the FW change log?

I find this tricky..
Recent Hugen releases have CONFIG -> VERSION
that now shows v0.2.3-2-g8ac9166

Going to ,
this suggests that Hugen pulled from edy555 on or after #111
.. but it is unclear to me which of those (if any)
e.g. reduced configuration storage from from five to four (SAVE 0-3)

It may be after #115 added negative value support for SCALE->ELECTRICAL DELAY

* does v0.2.3-2-g8ac9166 implement 12kHz IF?
* will shell 'offset' command still work?
* will disabling inline function promote even more touch screen bugs?
(e.g. testing ELECTRICAL DELAY)
* will disabled items (e.g. 'dump') remain in shell 'help' output, like 'test'?

Hugen told me the g8ac9166 part is the build number (version?) and I assume you can peruse the changes in his git repo that relate to that specific number.
Also, this is his build release notes from 3 days ago:
1. not synchronized to save flash, this may use the last version of inline optimization, and the screen speed will be significantly
slower after disabling the function inline;
2. Fixed the problem that the AA version clear_flash is not properly emptied;
3. After recompiling, you can connect to the cho45 web interface normally, but I don't

On Monday, October 21, 2019, 2:57:15 p.m. GMT-4, Oristo <ormpoa@...> wrote:

> Where can one find the FW change log?

I find this tricky..
Recent Hugen releases have CONFIG -> VERSION
that now shows v0.2.3-2-g8ac9166

Going to ,
this suggests that Hugen pulled from edy555 on or after #111
.. but it is unclear to me which of those (if any)
e.g. reduced configuration storage from from five to four (SAVE 0-3)

It may be after #115? added negative value support for SCALE->ELECTRICAL DELAY

* does v0.2.3-2-g8ac9166 implement 12kHz IF?
* will shell 'offset' command still work?
* will disabling inline function promote even more touch screen bugs?
? (e.g. testing ELECTRICAL DELAY)
* will disabled items (e.g. 'dump') remain in shell 'help' output, like 'test'?

g8ac9166 part is the build number

It is a git change hash

this is his build release notes

To extract such notes,
goto
click ... and copy
goto
paste

screen speed will be significantly slower

which means that higher priority activities
which do not successfully save and restore context
(e.g. run out of space) will more likely provoke errors.
(computing)

On Mon, Aug 5, 2019 at 07:07 AM, <hugen@...> wrote:

Not every si5351 can be stably overclocked to 1200MHz. As the temperature
increases, the internal VCO operating limit frequency of the si5351 will
decrease. If you notice a significant spike(>0dB) in your nanoVNA at 300 MHz
or 900 MHz, I recommend that you use the 800MHz firmware.

You can check your hardware with this firmware: /g/nanovna-users/message/5445

It includes latest changes from @edy555, @hugen79, @qrp73 repositories and performs si5351 PLL check. If you see red PLL icon near battery icon, it means that your si5351 works unstable.

Also, this firmware supports @cho45 NanoVNA WebApp and has no freezes and errors. :)

I have a Hugen nanoVNA with the gen111.taobao.com firmware.
I use it for HF measurements and have been happy with the performance.
I have been waiting for the firmware revisions to settle down before I upgrade.
This looks like a mature version.
Should I be aware of any issues when upgrading to this version?

Thanks to all for the effort.

Mike N2MS

Hi,
Is it possible to have the source code of this firmware version?
Regards

Of course - it's under the GPL, so the source code must remain open :-)

--
Rune / 5Q5R

On Tue, Oct 22, 2019 at 03:42 PM, n2msqrp wrote:

This looks like a mature version.

A new version is never a mature version. Old bugs may have been killed but new (buggy?) features and behaviour will have been introduced.
It may be powerful and feature-rich, but it's not mature.

Raymond

On Tue, Oct 22, 2019 at 04:16 PM, Raymond Domp Frank wrote:

A new version is never a mature version. Old bugs may have been killed but new
(buggy?) features and behaviour will have been introduced.
It may be powerful and feature-rich, but it's not mature.

That doesn't mean that I'm not longing for a bit of time to try this version out!

Raymond

Well, it is a rainy day so I tried to do the upgrade.

I went to the [email protected] | Wiki Main Menu and under Firmware and under "Easy windows firmware update" downloaded the "How to write firmware (Windows GUI)" document.

To make it easier I printed out the document. Since I have a DFU file I skipped the first two pages on the DFU File Manager.

I already downloaded DfuSe Demo.

I had DIP IC socket pins with the correct 2.54mm spacing so I shorted two pins together and inserted the shunt into the two rightmost pins P1 VDD and BOOT0.

I switched on the unit and got the white screen and removed the pins.

I switched down the unit and powered up to verify gen111.taobao.com was still working.

I switched down the unit into inserted the pin shunt into P1 and powered up into the white screen boot mode.

I connected the unit to my laptop and started DfuSe Demo. It did not recognize the device so I started Device Manager. It showed the ST driver with an error. I ran update driver and searched for a driver wpdate (This is a Windows 10 laptop).

It found and installed the ST driver and DfuSe Demo found the DFU Device.

Be sure to read the directions at the bottom of page 4. The first step is to save the existing DFU file with the Upload Action Choose and Load options. I saved the existing file and labeled it gen111

I did the upgrade with the NanoVNA-0.3.0m.dfu file. I selected Choose and after a couple of messages the bottom bar turned green and ended with "Target 00: Verify successful" I left the DFU mode. My unit did not automatically reboot so I switched the unit off and on.

The screen came on. I selected the CONFIG and VERSION touchscreen buttons and it shows Version 0.3.0m

Success!

Since I only have one screen on this laptop I usually print upgrade instruction and read them a couple of times before starting. I usually print two pages per sheet to save paper:-) The document is next to my laptop while upgrading and I add notes as I upgrade.

I will continue playing with this great little VNA. I use NanoVNA SERVER and will try NAnoVNASHARP and the NanoVNA WebApp.

Mike N2MS

Hi,
Sorry but wherre can i download this particular version?
regards

Sorry but wherre can i download this particular version?

Much of this Topic is about:
/g/nanovna-users/message/5445

QRP releases firmware here:

thank's

A couple of questions.
How can I tell which version of firmware I have?
My NanoVna works fine as far as I can see.
Also works ok with the latest version of nanonva-saver.
I am mainly interested in HF. What advantages would I get by upgrading firmware?
Don m5aky

I had similar issue with ST Driver error (also win 10) but device manager could not find update.I found this arduino site had a file download which worked: