开云体育

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

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...

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

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