开云体育

how to use the NanoVNA-Saver software *Calibration settings*

/g/nanovna-users/wiki/NanoVNA-Saver_Calibration-Settings

Very nice. I hope that some folks allergic to Smith chart read this
and appreciate how it helps typical VNA tasks.

so, this firmware /g/nanovna-users/message/5445 has more bug fixes and improvements in comparison with 0.3.1 :)

Yes, firmware 0.3.0m already has fix from version 0.3.1 from @edy555. :)

Actually the bug which is fixed by @edy555 in 0.3.1 was missing from 0.3.0m. It was already fixed.

The same other bugs which currently present in 0.3.1 from @edy555 already fixed in 0.3.0m.

0.3.0m missing sine table removement from 0.3.1, but it won't affect functionality.

Ok great! Thanks. Larry.

You selected the wrong converter - just like I did.
Select I want to generate a DFU.Then, click on the S19 or hex button - not the bin.
That should do it.

Edy555's version had a few new menu items such as DFU menu, version info, and
a few more Format menu's (not available in Hugen's firmware).

OK, you may have missed that there were already two (now three) menu maps
to match firmware menu differences.
The second map already showed DFU, version and more FORMAT options.

Since my hardware came with Hugen's firmware, I would like to confirm that the
VNA shall work correctly irrespective of the firmware I load?

I communicate directly with neither edy555 nor Hugen.
IMO, Hugen releases to Google Drive have been more stable,
and I prefer his AA versions (2 trace with larger font).

My impression is that edy555 is working on his own NanoVNA (2),
which is one reason that Hugen's are now named NanoVNA-H.

QRP reports that edy555 0.3.0 firmware has bug fixes,
better noise floor and more precise measurement.
I am concerned that touch display usability may be appreciably poorer
and whether routines no longer in-lined have been vetted for reentrancy.
I suppose that it also has smaller (4 trace) font;
4 traces on touch panel is not worthwhile to me..

ok just downloaded 0.3.1 build.
I generated with the dfu file manager, the ch.bin from the build but
all i get is a 301 byte file. it processes it too quickly, so i dont think it's successful.
Hmm...

Hugen's firmware was an early Oct build - if I remember right "NanoVNA-H_20191009.dfu".

Edy555's build is 0.2.3 which I note has changed to "0.3.0-20191020.dfu". (I plan to change my firmware tonight)

Some of the differences I noted was that Edy555's version had a few new menu items such as DFU menu, version info, and a few more Format menu's (not available in Hugen's firmware). Yes many of the menu's don't make sense and I am glad its just not me! Congrats on the fantastic effort to build the menu structure which is so help for a newbie like me.

Since my hardware came with Hugen's firmware, I would like to confirm that the VNA shall work correctly irrespective of the firmware I load? (Hugen or Edy555).

Regards - Nan

Just answered my own question, then get more excitment than i bargained for :-) ...thanks guys.
0.3.1 fix ??... no Rune,didn't know 0.3.0 existed til now..

Do you have the 0.3.1 fix from edy555 in as well?

--
Rune / 5Q5R

On Mon, Oct 21, 2019 at 10:38 PM, Dean Smith wrote:

Aha September firmware with 1500 span 0.2.3 no battery symbol.

The firmware that I mention above supports 10 kHz - 1500 MHz range. The battery icon bug is fixed. And it is more fresh, it is based on 0.3.0 version from @edy555.

Aha September firmware with 1500 span 0.2.3 no battery symbol.
Uploaded October 11th firmware battery symbol appears! Yay.
Now to recalibrate...

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 set threshold to 295 MHz

Hugen set 266 MHz for his 800 firmware versions.

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)

forgot to mention, this firmware version has modded battery indicator. :)
It has white color for normal battery, yellow color for low battery and red color for critical battery voltage.

You can test this firmware. This is improved version of edy555 firmware v 0.3.0. It shows battery indicator even if diode is not installed.

Also it shows battery voltage on CONFIG => VERSION screen.

Note that firmware assumes that diode voltage drop is 500 mV, so it adds 500 mV for correction.

PS: this version has si5351 hardware check, so if you see the red PLL indicator under the battery it means that you have defective si5351 chip. Defective si5351 may works unstable above 200 MHz.

In addition, this firmware has bug fixes, better noise floor and more precise measurement.

I recommend you to cleanup settings and perform calibration after upgrade. You can perform setting and calibration cleanup with the following console command:

clearconfig 1234

I see no battery symbol on the display

May not show when powered by USB

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'?

I see no battery symbol on the display.

Adding diode only connects sensor

Is it a case of reinstall the firmware, to enable this??

Yes.