开云体育

THANK YOU Herb and Owen ??

Both your information helped and I'm back in business! This little unit just doesn't seem to work right. It did when I first got it, did the upgrade to the NanoVNA-H Jan 18th version and the _AA, and the unit hasn't worked right since. I was trying to reinstall the backup from the original 12262019 version that came with it, but it's corrupted, so that's what white screened me. Going to try and see if it's working properly with the 29200128 _AA installed. Haven't had much luck with this unit. I have the H4 on order from gigaparts, should be here Wednesday. Hopefully it will work properly. At least it has a 2 year warranty, lol!

The NanoVNA will boot into DFU mode if you power it up with that pin
shorted. When it is in that mode, you can use either the ST
Microelectronics tool DfuSe Demo (Windows only) or the open source
dfu-utils package (Windows, Mac, Linux) to reload the firmware. Selecting
the DFU menu option, if available, makes the NanoVNA reboot into DFU mode
ONCE.

If you then reboot it without the pin shorted (usually by turning it off,
removing the short, and turning it back on), or reboot again after you did
the menu option to boot into DFU mode, the NanoVNA will boot into its
normal firmware. From there all the usual things will work, including using
PC software such as NanoVNA-saver.

So I haven't tried this yet, but after I remove the connection, will the PC app recognize it again, or how else do you update it? Guess I should try it first..

Oh, hey, I know this one now!

From the forum wiki under "Help":
unlikely to be "bricked" - Owen Duffy
which is a link to:

where it says:

There is a pin on the board, BOOT0, that must be held high during reset to enter the on-chip bootloader. Later firmware versions also provide a menu option to enter the bootloader, but if an attempted upgrade messes up the menu, you may need to use the BOOT0 pin bridged to the adjacent VDD pin while you power cycle the nanovna.

Blog post has further instructions, and even several photos.
Very thorough.

Jerry, KE7ER

Thank you I will give it a try!

On Sun, Aug 9, 2020 at 12:45 PM, Steve Haber wrote:

so I accidentally uploaded the wrong version to my nano VNA and now when I power it on all I have is a white screen. Is there any way to flash the right version back into my nano VNA without the interface application?
==================================================
Someone recently did the same thing on the tinySA forum. This from moderator:

switch off the nanoVNA
Open the case
Connect BOOT0 with VDD pin
switch on the nanoVNA
wait 5 seconds
remove the connection
update firmware

This is how everyone updated their firmware when the NanoVNA was first released.

- Herb

so I accidentally uploaded the wrong version to my nano VNA and now when I power it on all I have is a white screen. Is there any way to flash the right version back into my nano VNA without the interface application?

On Sun, Aug 9, 2020 at 08:23 AM, Jerry Gaffke wrote:

And as someone pointed out below, avoid steering a thread away from its
original topic! More readers will notice your new topic than will ever see it
buried in a large, old thread too.

Unfortunately and speaking from experience , some police gets uptight when new and SIMILAR post is entered.

Perhaps better usage of hashtags to identify subject should be advertised.
Let's admit - majority of users are amateur operators used to rag chewing , hence wavering off the subject is pretty norm for them.

I actually keep (very accurate ) statistics ( just kidding ) how soon a subject gets hijacked...
on an average within 5 ( FIVE ) entries !

I do write up my own notes as text files whenever trying to master
something complicated. Been using vi for that since the early 80's.

Will be taking such notes as I dig through the wiki and pertinent forum posts.
So the natural path here would be to do about as DougVL suggests.
Every plagiarized tidbit in my notes will get an author, date, and URL.
Should then be moderately easy to edit it for general consumption,
post that to the group for corrections and additions.
Then place it in the wiki.

Once in the wiki, other users are welcome to hack it.
But I will consider myself the owner, and occasionally do a diff against my backup.
If I don't agree with the hacks, I'll unhack it.

We'll see if I follow through on this.
Now 8 years into finishing out this off-grid strawbale house,
the water system is not fully winter proof,
the yaks will need hay for the winter and better fences,
canyon walls are full of weeds, internet link is dodgy, tractor needs work, ...
And hey, I'm retired! It's all a hobby!

Jerry Gaffke, KE7ER near Flora OR

Ready-made compiled firmware in .dfu format for flashing, separate versions for stock (v9.0) and for sdcard modified (v9.0.1) NanoVNA-H4

I'll try to behave here, keeping threads on topic would make it easier to look for information later.
And keeping track of all this stuff is tough enough without wandering threads.

But that can be at odds with having a discussion, discussions tend to wander as related issues come up.
Two or three related issues later, and we're talking about something completely different,
with no distinct dividing line.

Those who know me from other forums may remember a time or two
when I told the thread police that we were having a discussion, and carried on.
In a forum with 7000 members, it is not always best to comply with the one member who complains.

When searching forums for a particular bit of information, I usually rely on key words in the discussion.
And if it was a discussion in which I took part, I include "KE7ER" in the key words.
That's usually the case for threads I am looking for, as those are the ones I remember most.

I doubt we will ever be able to count on posts to threads always staying on subject.
For example, the title of this thread is "Firmware choices, wiki is awfully confusing"

My yahoo email account currently has 33,000 bits of email in the inbox, over two decades worth,
no other folders. Pretty much the same system. My niece was horrified when she saw that.

Jerry, KE7ER


Rich wrote:

a) the process is hampered by folks hijacking threads. the first time that happens,
someone ought to say "stop", "post new thread", but instead, the thread goes crashing on

Doug wrote:

And as someone pointed out below, avoid steering a thread away from its
original topic! More readers will notice your new topic than will ever see it
buried in a large, old thread too.

I think a notation should be made in the Wiki as to its publication date, the model(s) it refers to and the highest version of firmware it relates to.?
It does cover examples of how to perform a number of common hamshack-related tests & measurements.?



On Sun, 9 Aug 2020 at 6:25 AM, Oristo<ormpoa@...> wrote: > Guide to the NanoVNA - Kindle Edition $2.99 @ Amazon

Is this being updated?? Should it be delisted?

I too found the Wiki complex and confusing, even back in October, 2019 when it was MUCH smaller. And I think it's amazing (and terrific) that it has grown so much. This is a very busy, helpful and informative discussion group. But there's the key - - it's a "discussion" group. Not an 'educational' one, although that is certainly a side effect.

And once you do get familiar with the information, the group and the device, there's a lot less motivation to do something about organizing the Wiki.

Something that might help you and other future users is to document for yourself what you do find that's useful, along with where you found it. Sort of like 'taking notes' in a class. It could just be in a plain text file, added to when appropriate. Then, when you're pretty well (or at least somewhat) confident, post it. And add it to the Wiki. It could be updated as you learn even more. Just keep it organized and it could be a very helpful 'roadmap' to many other future users.

And as someone pointed out below, avoid steering a thread away from its original topic! More readers will notice your new topic than will ever see it buried in a large, old thread too.

Doug, K8RFT

On 2020-08-08 20:29:-0700, Jerry Gaffke via groups.io wrote:

I can generally be successful searching for stuff here.
But reading the forum posts and wiki contents can be a challenge
if you haven't been following the discussion for a few months.
Even if you sort of know what you are doing.

Jerry, KE7ER

My impression from trying to find information and follow discussions is that
a) the process is hampered by folks hijacking threads. the first time that happens, someone ought to say "stop", "post new thread", but instead, the thread goes crashing on

b) "the thread crashing on" is just another symptom of the mad dash that I see everywhere...it doesn't matter the subject or the technology. Example: I was at a dinner last year where an engineer with a hearing problem groused about his $14K USD hearing aids. Seems that they don't work very well. I asked what his audiologist said about that. He said that he had been to 3, and all 3 didn't know the products or how to use them, but were great at extolling how great the new technology is. I see that as similar to what happened to the NanoVNAs. My impression is that there is a mad dash to upgrade and enhance at some breakneck pace, which developers are happy to accommodate because they like to, well, develop. But who actually gets all that to the users...?

c) if you are in the moment, and following all the threads...that is, if your life is wrapped up in NanoVNAs, then you can keep track of the pieces...but if you come to the party late, and someone says read the Wiki and read the forum, you are faced with a daunting task

d) I offered to help write docs and update the Wiki, early on...I asked for help and input from the developers...after all, who knows better than they what is happening? The reply was that I should just pick up a device and start using the desktop software, and then write up what I "discover"...I passed...after all, that is exactly what I was trying to avoid...so my VNAs (yup, plural) sit idly for the most part.

I used to run my own engineering company...we did a variety of applications, from some in nuclear operations, to some that ran trains in some very complicated situations (special purpose trains, run by a net work of a dozen computers). At one point, I happened to be on site when an upgrade was in progress. The train operators suggested that I might want to drive the train...literally. Did I say NO...I did NOT! (I got to blow the horn ;-) Their reasoning was that our company would be more familiar with what was /supposed/ to happen, and if something went amiss, we'd be in a better position to understand what that was.

I don't pretend to know what is under the hood of NanoVNAs...but I do have the software engineering and programming savvy to enjoin a discussion with developers.

There was another post in this thread (I think) that addressed collaboration on the Wiki. I might say collab in general. The person posting had a valid point, I opine, that folks would write something original and add it to the Wiki, rather than collab with others to get a better product. That's what my last several paragraphs addressed.

We would not be having all this discussion if there were a greater sense of collab. I encourage those who remain to develop a greater sense of teamwork, even if it means slowing down the rate of releases.



--
72/73 de Rich NE1EE
On the banks of the Piscataqua

It seems that the last Sw QT_Windows Release doesn't support Touchstone or xls measurement files export. This is a great drawback.
--
Piero Belforte

Well, who is Christopher Schwartz? Is he on this list?

My initial reaction is that it (the ebook) is a plagiarism of the information on our Wiki and should thus be didallowed.

Does anyone on this list want to own up to publishing this? Please PM me if so.

DaveD

There are available source code repositories in github with the latest H4 firmware.

Guide to the NanoVNA - Kindle Edition $2.99 @ Amazon

Is this being updated? Should it be delisted?

Hi Jerry -

There are several other tutorials in there now that should be worth investigating.
But really, it is simply overwhelming.
Perhaps we could create a guide to the user guides?
Or perhaps settle on one good beginner's guide, put it at the top of the wiki?

Those suggestions have merit. Here are some considerations:
* works here are by volunteers
- most submit their own work, rather than collaborate to make one better,
much less authoritative. (However, a recently cited "firmware for idiots" link
is to GitHub, which supports such collaborations, AKA "pull requests"..)
- external references may move or disappear at providers' whim
(e.g. Google Sites is currently forcing a migration that may disappear some)
* while I at least skim material for validity before adding Wiki links,
my perspective and VNA workflows are idiosyncratic,
so inappropriate for rating or ranking introductory guides.

I assume most of them are aimed at the nanoVNA-H and friends.

My perspective is that >>this group<< is for NanoVNA-H, NanoVNA-H4,
Hugen's first-generation NanoVNA and early clones.
At least, my references to other VNAs in Wiki
are intended to simply help distinguish among those "supported"
and others that trade on that name by edy555.
Other VNAs have (or at least should have) other support/affinity groups...

The new wealth of variants may require a reorganization of the wiki.

I can imagine NOBODY motivated to manage consolidated introductory
information for incompatible platforms which essentially share just nominal function
and partial names promulgated by a dynamic cast of characters.

Perhaps a Main Wiki page could simply identify and group supported vs unsupported VNAs,
then a second page could enumerate only most popular (by vote?) tutorial and introductory content
for supported models
a third page of alternative user guides for supported models,
another page pointing elsewhere for other VNAs and related devices,
then remaining pages (as now) for mods, application notes, etc.

Hopefully the standalone menu structure is at least somewhat similar on all of
them, but that seems doubtful.

I can only attest to menu structures for nanoVNA firmware menus mapped up to
December 2019. However, since Microsoft broke IBM's paradigm of extensively
validated backward compatibility in mid 1980s by moving fast and breaking things,
programmers often arbitrarily rearrange and rename functions, baffling existing users.
Bill Gates called that "embrace and extend"..
FWIW, sorting some nanoVNA menu interactions involved reading source code..

As Oristo mentioned, there is nothing stopping ANY forum member from
making edits to the Wiki page.

That's good and bad.
You might have somebody like me whacking at it.

FWIW, at least Larry and I have corrected wrong or unclear Wiki entries.
Groups.io Wiki includes a version comparison facility for managing changes.

Somebody who thinks the code at
is only suitable for the edy555 kit.

So far as I know, no true edy555 kit is generally available;
whether current edy555 firmware works on his original design
is unknown to me.