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: Windows 7 USB Driver problem - not working
Hi Nigel,
toggle quoted message
Show quoted text
I don't think NanoVNA-Saver ever outputs (from its own code) a message with the text "unable to find" anything. So it might be from a module or something. Could you start the software with "-D logfile.txt" as a command line option, and send me the log file? This should show any errors. You can send direct to mihtjel@..., or here. Thanks for trying the software :-) -- Rune / 5Q5R On Tue, 1 Oct 2019 at 09:57, Nigel <zs6rn@...> wrote:
Am enjoying the journey learning how to use the nanovna but have |
|
Windows 7 USB Driver problem - not working
Am enjoying the journey learning how to use the nanovna but have encountered a problem relating to using nanovna saver that requires guidance from those more knowledgeable than I am regarding interfacing the device to a Windows 7 notebook.
I have connected the nanonvna to the same notebook to upgrade the device firmware (Release 0.1.1 with added scan command and battery.dfu) using dfuSe_Demo_3.0.6 with no issues. Trying the 'original' P.C. application (Nanovna-Sharp) I can establish a connection of sorts (able to change Connect - Disconnect indication but that is all) if using COM3 (Com1 is the only other port shown and if selected then unable to connect/disconnect) but no data transferred so probably an anomaly. Have installed the latest Nanovna-Saver (along with Python) and after start up and GUI displayed, an error in the command / DOS window (behind the GUI) shows as "unable to find..." - am guessing that the blank between ' ' is looking for the Com port and performing a scan shows no device or port available. Checking the Windows device driver properties shows nanovna to be using ChibOS/RT Virtual Com port and Windows recognizes device being attached / removed. Booting the same notebook into Linux (Puppy) the result of a 'lsusb' shows the nanovna as connected. As an aside, I considered trying to build nanovna-saver on the Puppy system but too many dependencies and not good experience in the past with other applications (I am not really a software person). Searching for similar posts I only see Windows 10 issues and perhaps I have missed the answer to this challenge so apologies in advance. Sincerely hope is an easy fix and that biggest issue is my ignorance... an idiots 'how to' (step by step) guide is probably needed. MANY thanks for any guidance / suggestions. 73 Nigel ZS6RN |
|
Re: Installed recent firmware - was this a big mistake?
Hi Bryan & others,
I'm slightly confused at seeing both people mentioning that they see the errors on the screen of the NanoVNA (in which case my software just replicates it), as well as seeing corrupted data purely in NanoVNA-Saver. Some general remarks: NanoVNA-Saver connects to the NanoVNA via the USB emulated serial port. I specify a bitrate of 115200; but since there's no actual physical transformation to a serial signal going on, that *shouldn't* change anything. I have frequently seen data errors in the received data, the source of which I have been unable to identify. The software attempts to reject and re-read values it deems to be completely unrealistic, ie. being grossly outside the Smith chart. It prints warnings in the console when this happens. It may be that the firmware needs to be adjusted in order to cope with rapid successions of setting a sweep range and immediately asking for the data; but I don't think there's much I can do from the PC end of the equation, sadly? Thanks for letting me know, though. -- Rune / 5Q5R On Tue, 1 Oct 2019 at 04:22, bryburns via Groups.Io <bryburns= [email protected]> wrote: Here is some more information on this issue. |
|
Re: Odd Crash on NanoVNA-Saver v0.0.12
Hi Steve,
toggle quoted message
Show quoted text
could you do the following: - Start NanoVNA-Saver from a command prompt (cmd.exe), in order to preserve the crash error message, - Start it with the option "-D logfile.txt" in order to log debugging information to a log file (in this case logfile.txt, modify as needed) That should give information to help show what the problem is :-) -- Rune / 5Q5R On Tue, 1 Oct 2019 at 01:07, WB8GRS <ssedgwick@...> wrote:
Whenever I enter a start frequency of 50m, NanoVNA-Saver v0.0.12 crashes. |
|
Re: Installed recent firmware - was this a big mistake?
Here is some more information on this issue.
I am running the firmware from nanovna-firmware-0.2.2 which I downloaded from that was created by edy555. I cleared the memory using the dfu file DMR-CLEAR_MEMORY_DFU.dfu located in the files section of this user group prior to loading the 0.2.2 firmware. The nanoVNA is producing reasonably stable results by itself. When using nanoVNA-Saver never gets bad data when collecting only 1 101-point segment between the start and stop frequencies. However, it appears to get bad data frequently at the beginning of the second segment when 2 segments are used. When continuous scanning is enable, both the first segment and the second segment frequently have bad data. This is most noticeable if you are measuring a device which has some rapidly changing amplitude and phase information such as a stop band filter. I am trying to measure a US FM-Band stop band filter (stop-band is 88-108 MHz in theory) when I am observing this issue. The frequency extent of the sweep width does not seem to matter much. It is as though the frequencies being measured are not the ones that the software assumes are being measured. This seems like a problem that Rune should look at. -- Bryan, WA5VAH |
|
Re: NanoVNA-Saver 0.0.12
Rune,
There seems to be an issue with nanoVNA-Saver 0.0.12 when using some of the latest firmware (0.2.2 from edy555 for example) and trying to use multiple 101-point scans. It seems to work fine with only a single 101-point scan. I am sure you don't have time to follow every thread. Can you take a look at the thread in this user's group listed on the next line? /g/nanovna-users/topic/installed_recent_firmware/34348349?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,34348349 At first, I didn't think the issue was with nanoVNA-Saver; however, now I am wondering if it is? Let me know what you think? -- Bryan, WA5VAH |
|
Re: Installed recent firmware - was this a big mistake?
Ok. I use Teraterm to talk to the console. Putty is ok but it's a little old these days.
I've always let everything sync up automatically and when I've looked, the speed has always been 115KBs. I think if you try any faster speeds you're asking for errors. |
|
Re: Installed recent firmware - was this a big mistake?
Guilty as charged :>).
The reason I mentioned Baud rate is because the software talks to the nanoVNA through the equivalent of a serial port. And, you can use a terminal emulator to control the device, read data, etc. The terminal emulator software that I have only goes up to 921600. So maybe that is why I don't see errors when I get data from the nanoVNA at that rate. Although I don't see it on the nanoVNA screen when I use the terminal emulator software. Something else is going on. I am still looking into the issues with the new firmware and will report anything I learn. -- Bryan, WA5VAH |
|
Re: New file uploaded to [email protected]
Whoops that failed; groups.io will not serve html files.
It is instead relocated here: and added it to the Wiki as "NanoVNA Versions" /g/nanovna-users/wiki/home tersely describes and points to firmware versions that were described in and/or appended to messages. I apologize for the confusion |
|
New file uploaded to [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the [email protected] group. File: firmware.htm Uploaded By: Oristo Description: You can access this file at the URL: Cheers, |
|
Odd Crash on NanoVNA-Saver v0.0.12
Whenever I enter a start frequency of 50m, NanoVNA-Saver v0.0.12 crashes. For example, I enter a start freq of 50m and a stop freq of 200m and click "connect the NanoVNA", NanoVNA-Saver v0.0.12 crashes. In fact if I enter a start frequency of 50m or 51m, NanoVNA-Saver v0.0.12 crashes. If I enter a start freq of 49m or 52m, NanoVNA-Saver v0.0.12 does NOT crashes. Entering 50m or 51m as the start frequency does NOT cause a crash when I use NanoVNA-Saver v0.0.11
Anyone else seeing this? Thanks, Steve_WB8GRS |
|
Re: New user
Anyway, there lots of impetus from others to create separate topic areas.
toggle quoted message
Show quoted text
A On Mon, 30 Sep 2019, 23:49 Alan Lloyd, <alanthebass37@...> wrote:
Glenn |
|
Re: New user
Glenn
Yes that's a good idea. But my idea is better. A On Mon, 30 Sep 2019, 23:30 Glenn Little, <glennmaillist@...> wrote: When you download the email with you client create a folder for NanoVNA |
|
Re: Deal on ebay
Trygve Sjothun
Thanks Mike and all other comments noted. Re: tools, I have the opportunity
to learn more about radio antennas with this new tool. I have managed to calibrate it and have taken swr readings but wish to do more than that and learn in the process. On Mon 30 Sep 2019, 22:39 mike watts via Groups.Io, <wy6k= [email protected]> wrote: Trygve, I have made my notes into a "Tips for New Users" write up. You |
|
Re: New user
When you download the email with you client create a folder for NanoVNA with subfolders for each subject area as you define them.
toggle quoted message
Show quoted text
The solution is now on your computer without forcing others to think the same way that you do. Glenn On 9/30/2019 5:29 PM, Alan Lloyd wrote:
Hi David --
----------------------------------------------------------------------- Glenn Little ARRL Technical Specialist QCWA LM 28417 Amateur Callsign: WB4UIV wb4uiv@... AMSAT LM 2178 QTH: Goose Creek, SC USA (EM92xx) USSVI LM NRA LM SBE ARRL TAPR "It is not the class of license that the Amateur holds but the class of the Amateur that holds the license" |
Oristo
ljurc
to navigate to use esc to dismiss