Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
Re: Odd Behavior of NanoVNA-Saver
Charles,
When I get split second popups, I video the display and play back the video at a slow speed until I can stop it at the pop-up.? Did you check your syslogs for error messages? On Sun, 9 Aug 2020 at 10:21 PM, Charles Albert<cma_1956@...> wrote: After a few issues, I was able to get NanoVNA-Saver (Python) up and running on my Linux Mint 19.3 machine. Everything seems to work just fine but for one small problem... Every time I start NanoVNA-Saver and hit the connect button on the main screen, the program crashes and exits. (this happens so fast that I can't see any error messages) BUT, if I immediately relaunch the program and hit the connect button again, all is well. The software connects to the device and begins doing everything it should. Now, here comes the really odd bit... If I disconnect from the device and exit NanoVNA-Saver, and then relaunch, the same thing happens as above. If, however, I just exit NanoVNA-Saver WITHOUT DISCONNECTING from the device and then relaunch, the software will connect to the device and work just fine. This is, to me, a minor thing. I've just been shrugging my shoulders and relaunching so it will connect. Takes what? Maybe 10 seconds? It just seems strange. Take Care & 73 de KC6UFM Charles |
Re: I think I bricked my nano VNA
Steve,
Some developers recommend you do a Clearconfig 1234 (using a terminal program like putty) after a firmware update. This is followed by a touch screen calibration. Some "weird" issues have been solved this way. Maybe someone with experience on this topic can make a suggestion... Roger |
Re: Odd Behavior of NanoVNA-Saver
On 8/9/20 7:20 PM, Charles Albert wrote:
After a few issues, I was able to get NanoVNA-Saver (Python) up and running on my Linux Mint 19.3 machine. Everything seems to work just fine but for one small problem... I'm going to guess something about the drivers for the USB device - is it a serial port, I'm too lazy to go look how my nanoVNA shows up, but I do notice the software imports serial (i.e. Pyserial) You might try reinstalling the Pyserial package. There's some "pip" command that does it - I use Anaconda, so there's a conda update thing too. And there's always weirdnesses about USB serial ports - you plug it in, and it takes some amount of time before a) /dev/tty... shows up b) /dev/tty... is actually usable |
Odd Behavior of NanoVNA-Saver
After a few issues, I was able to get NanoVNA-Saver (Python) up and running on my Linux Mint 19.3 machine. Everything seems to work just fine but for one small problem...
Every time I start NanoVNA-Saver and hit the connect button on the main screen, the program crashes and exits. (this happens so fast that I can't see any error messages) BUT, if I immediately relaunch the program and hit the connect button again, all is well. The software connects to the device and begins doing everything it should. Now, here comes the really odd bit... If I disconnect from the device and exit NanoVNA-Saver, and then relaunch, the same thing happens as above. If, however, I just exit NanoVNA-Saver WITHOUT DISCONNECTING from the device and then relaunch, the software will connect to the device and work just fine. This is, to me, a minor thing. I've just been shrugging my shoulders and relaunching so it will connect. Takes what? Maybe 10 seconds? It just seems strange. Take Care & 73 de KC6UFM Charles |
Re: Firmware choices, wiki is awfully confusing
Larry,
toggle quoted message
Show quoted text
I've only looked at a few pieces. Perhaps in a week or so I'll come up with the text file mentioned here: /g/nanovna-users/message/16415 If deemed appropriate (and if I get it done), we'll post it to the wiki. I'm not saying we should significantly alter the wiki, but rather to provide a way to navigate it. The three part nanoVNA tutorial from DG8GB looks very promising, one part each for the "classic", the -H, and the -H4. I believe what he refers to as the -H2 is what most people refer to as the -H. For starting out from ground zero, HexAndFlex might be hard to beat: But then I have not looked over much more than the above two. Jerry, KE7ER On Sun, Aug 9, 2020 at 03:59 PM, Larry Rothman wrote:
|
Re: Firmware choices, wiki is awfully confusing
Hi Jerry,
What areas of the forum Wiki do you think are very good? What part(s) of the forum wiki's material don't you feel is up to par? Only a handful of members have contributed and/or edited the wiki out of a membership of close to 7000 yet ANY member can add content or upload documents to the files area.? When I ask those members that have issues with the content to feel free to add their own notes, I see nothing (for the most part) and no one has approached me to help them with adding content (I can't speak for Oristo, Herb or the other wiki contributors).? Comments? ... Larry On Sun, 9 Aug 2020 at 6:30 PM, Jerry Gaffke via groups.io<jgaffke@...> wrote: I worked as an EE for decades in digital design RF is a bit foreign at times, but I'd guess I'm better off than the typical user. Some of the material in the wiki is excellent. Much of it is not. Some of it is simply way over the top technically for most users. Telling somebody who can't figure out their nanoVNA to just check the wiki without further guidance is likely leave them feeling stupid and inadequate. Clyde wrote: It appears this person is just trying to get a copy of an article that, HEYou might include a snippet of what you are responding to. I have no idea what article that might be. I would be skeptical of any unknown person or persons being allowed toI believe the wiki is open to all forum members. The admin likely has no interest in policing the wiki. Just the view of a newbie, that has found the information presented by thisGlad to hear it's working for you. Jerry, KE7ER On Sun, Aug? 9, 2020 at 02:43 PM, Clyde Lambert wrote: I do not know who this guy is, not even sure he is a licensed ham, but as a |
Re: Firmware choices, wiki is awfully confusing
I worked as an EE for decades in digital design
RF is a bit foreign at times, but I'd guess I'm better off than the typical user. Some of the material in the wiki is excellent. Much of it is not. Some of it is simply way over the top technically for most users. Telling somebody who can't figure out their nanoVNA to just check the wiki without further guidance is likely leave them feeling stupid and inadequate. Clyde wrote: It appears this person is just trying to get a copy of an article that, HEYou might include a snippet of what you are responding to. I have no idea what article that might be. I would be skeptical of any unknown person or persons being allowed toI believe the wiki is open to all forum members. The admin likely has no interest in policing the wiki. Just the view of a newbie, that has found the information presented by thisGlad to hear it's working for you. Jerry, KE7ER On Sun, Aug 9, 2020 at 02:43 PM, Clyde Lambert wrote: I do not know who this guy is, not even sure he is a licensed ham, but as a |
Re: Firmware choices, wiki is awfully confusing
I do not know who this guy is, not even sure he is a licensed ham, but as a
newbie to VNAs myself, I found the Wiki does have a overwhelming amount of info. However, if one takes it step by step, I see absolutely no problem with it. There are several ebooks on Amazon that clearly explains, that if one can read, the NanoVNAs from a compleat explanation of VNAs to full engineering aspects and use. In fact the VNA guide on Wiki also fits that bill. If one is overwhelmed by what is presented in the group WIKI, then they need to learn how to reasurch a topic one step at a time. It appears this person is just trying to get a copy of an article that, HE HIMSELF, has written as he refers to his article on another web site. I read the reference article he referred to and found NO additional information that is not covered in the group WIKI. I would be skeptical of any unknown person or persons being allowed to change the information in the groups WIKI, without the review of such info by the group Admin. Just the view of a newbie, that has found the information presented by this group, to be educational and helpful in understanding and using the NanoVNA. Clyde Lambert KC7BJE |
Re: I think I bricked my nano VNA
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! |
Re: I think I bricked my nano VNA
The NanoVNA will boot into DFU mode if you power it up with that pin
toggle quoted message
Show quoted text
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. On Sun, Aug 9, 2020 at 4:28 PM Steve Haber <haber.steve@...> wrote:
So I haven't tried this yet, but after I remove the connection, will the |
Re: I think I bricked my nano VNA
Oh, hey, I know this one now!
toggle quoted message
Show quoted text
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 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 |
Re: I think I bricked my nano VNA
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 |
Re: Firmware choices, wiki is awfully confusing
Anne Ranch
On Sun, Aug 9, 2020 at 08:23 AM, Jerry Gaffke wrote:
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 ! |
Re: Firmware choices, wiki is awfully confusing
I do write up my own notes as text files whenever trying to master
toggle quoted message
Show quoted text
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 On Sun, Aug 9, 2020 at 05:44 AM, DougVL wrote:
Something that might help you and other future users is to document for |
to navigate to use esc to dismiss