Re: Is there an Android app for the NanoVNA - WebUSB
I added Web-Client launch instructions in the Wiki /g/nanovna-users/wiki/HomeFWIW, Web-Client works with STMicroelectronics' driver on Windows 8.1 64-bit Home and Chrome browser thru a USB 2.0 port to nanoVNA with original firmware. For Android devices that work with powered USB 2.0 hubs, this might help:
|
Re: Windows 7 USB Driver problem - not working
Hi Nigel,
I would like a simpler approach to repair.
The nanoVNA saver also works under Windows 7. A prerequisite for this is that you have SP1 and Ms VC ++ installed.
You can then start nanovna-saver-0.0.12.exe from Windows.
If you want to access the nanovna saver by installing Python, make sure to check the PATH path when installing Python - and install it in the Program Files folder (not in the Users /.../../../ folder) ). Then install the required pyqt5, numpy, pyserial from the Windows command line using pip3 install .... You can verify the installation by calling the Python 3.7 Module Docs server on your browser page.
I unpacked the contents of the nanovnasaver master downloaded from github into the C: root directory. You can start the program with nanovna-saver.py.
If not missed something, it should work. I hope it works for you.
Gyula
|
Hi David
Can you please post a link to where you got it from,
Thanks Dave 2E0DMB
toggle quoted message
Show quoted text
On 1 Oct 2019 11:46 am, "David J Taylor via Groups.Io" <gm8arv@...> wrote:
My NanoVNA-F arrived today and I'm looking forward to playing with it.?
It's
slightly smaller than a Google Pixel 3 phone (which isn't the biggest
model), although somewhat thicker of course.
UK buyers might like to know that it escaped duty, tax, collection fee
etc.
Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv
|
My NanoVNA-F arrived today Since NanoVNA-F has its own group, GitHub and videos, while this group is already quit busy, [with too many messages lacking clear context and/or generous with redundant content] please consider further discussion NanoVNA-F only there: /g/nanovna-f
|
Re: Windows 7 USB Driver problem - not working
You're welcome Nigel - I look forward to seeing what's gone wrong this time
;-)
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Tue, 1 Oct 2019 at 11:19, Nigel <zs6rn@...> wrote: Hi Rune :-)
Thanks for speedy response.
Once log file obtained it will be a pleasure to send to you for analysis -
THANK YOU!
Also thanks to YOU for developing NanoVNA-Saver - your efforts are MUCH
appreciated.
Very best regards
Nigel R
|
My NanoVNA-F arrived today and I'm looking forward to playing with it. It's slightly smaller than a Google Pixel 3 phone (which isn't the biggest model), although somewhat thicker of course.
UK buyers might like to know that it escaped duty, tax, collection fee etc.
Cheers,
David
--
SatSignal Software - Quality software for you
Web:
Email: david-taylor@...
Twitter: @gm8arv
|
Re: Windows 7 USB Driver problem - not working
Checking the Windows device driver properties shows nanovna to be using ChibOS/RT Virtual Com port and Windows recognizes device being attached / removed. You could replace that driver with this: Virtual COM port operation to nanoVNA can be confirmed using .e.g putty.exe I don't bother with a .msi installer; the standalone .exe works fine. Try sending `help` from putty: /g/nanovna-users/wiki/shellcommandsNanovna-Saver uses pyqt5, which can be separately tested: `python -m serial.tools.list_ports` COM3 1 ports found NanoVNA USB driver is STMicroelectronics Virtual COM Port 8/2/2013 1.4.0.0
|
Re: Another modified nanoVNA software
@neb70gsm
I would like to test the new software. especially the TDR function is very welkome.
Plse send to on1bes(at)scarlet.be
tnkx on1bes
|
Re: Is there an Android app for the NanoVNA?
Larry, if only I could but thank you for the suggestion.
73 Bob GM4CID
|
Did we by chance read the fine print..
For remote regions, we will charge your extra shipping costs. Usually it cost about 35USD-50USD. We will contact you after your payment. Thanks for your understanding.
It will be interesting to see just how remote you are. Not to mention the part about Duties and Taxes.
I am interested to hear how this works out. I am too much of a skeptic to hope to get something
at less than half the going price. Usually doesn't work out for me.
toggle quoted message
Show quoted text
On 9/30/2019 1:17 PM, W5DXP wrote:
I couldn't resist. I ordered this one if for nothing else, for spare parts. What will things be like a year from now?
|
Re: Windows 7 USB Driver problem - not working
Hi Rune :-)
Thanks for speedy response.
Once log file obtained it will be a pleasure to send to you for analysis - THANK YOU!
Also thanks to YOU for developing NanoVNA-Saver - your efforts are MUCH appreciated.
Very best regards
Nigel R
|
Re: Windows 7 USB Driver problem - not working
Hi Nigel,
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
toggle quoted message
Show quoted text
On Tue, 1 Oct 2019 at 09:57, Nigel <zs6rn@...> wrote: 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
|
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.
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: Odd Crash on NanoVNA-Saver v0.0.12
Hi Steve,
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
toggle quoted message
Show quoted text
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.
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
|
Just set it to daily summary and get one email per day
|
I'm a newbie too, can I get a copy. Thanks in advance. Doug, KI6DS
|
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
|
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.
|
Oristo
Gyula Molnar
David J Taylor