开云体育

Hugen set 266 MHz for his 800 firmware versions.

It is a git change hash To extract such notes, goto https://github.com/hugen79/NanoVNA-H/tags click ... and copy goto

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.

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

Adding diode only connects sensor Yes. https://drive.google.com/drive/folders/1H_l_3vnXSgg6AOIngvMEsPpIvRVTG7hq

Just popped a SMT 1n4148 in D2, but with my 0.2.3 firmware I see no battery symbol on the display. Is it a case of reinstall the firmware, to enable this??

I find this tricky.. Recent Hugen releases have CONFIG -> VERSION that now shows v0.2.3-2-g8ac9166 Going to https://circleci.com/gh/ttrftech/NanoVNA, this suggests that Hugen pulled from edy555 on or

This should read "4 segments from 50 kHz to 900 MHz." -- Bryan, WA5VAH

Dear all, I have been blessed with a group of people who have helped test the last few releases of NanoVNA-Saver. I'm getting ready to send them another alpha version, but I thought I would offer

Interesting thought, but I already have done that as a test. I set threshold to 295 MHz. Of course, you have to fully recalibrate (nanoVNA and nanoVNA-Saver) once you make such a change and use

Kurt, thanks again for your explanations and pictures. Now I have to experiment for a while and build a suitable fixture and see what the resuts are. I don't want to overdo it too much, primarily I

This smells like you should reduce threshold /g/nanovna-users/message/4155

Hi Bryan, I know it's the easy way out to claim that it's the other guy's fault, but I really don't treat 0.3.0 any differently than I did 0.2.3. The fact that it's at a specific frequency might point

The other menu change will be 2 less traces to enable/disable.One of the storage locations was cut due to the size of the larger fonts.Hugen found there was some overlap and corruption of the data

Rune, I have a little more information on the data error issues when nanoVNA-Saver 0.1.3 interfaces to the edy555 - 0.3.0 firmware. I get a consistent error when running 3 scans from 50 kHz to 900

The main difference that I found in Google Drive Oct 18 AA firmware is now only four (0-3) SAVE and RESTORE configurations, sigh... Other that maybe order of some items, are there other menu changes?

Thanks for your very quick reply. That sorted it. Paul, G0VKT.

And to complete the comparison two more measurements. The directivity of the bridge (red line) and the dynamic range of port 2 (CH1) (green line) of the nanoVNA and the home build VNA Measured by