开云体育

I am trying to run NanoVNA-saver on Windows 10 with the NanoVNA-H4. NanoVNA-saver correctly sees the USB port the NanoVNA-H4 is connected to; however, when I click on "Connect to NanoVNA" the program immediately locks up. I did install the 64-bit STM drivers as suggested by some.

Rick / N9ITW

On Mon, Jan 27, 2020 at 02:38 PM, <netwtek@...> wrote:

I am trying to run NanoVNA-saver on Windows 10 with the NanoVNA-H4. NanoVNA-saver correctly sees the USB port the NanoVNA-H4 is connected to; however, when I click on "Connect to NanoVNA" the program immediately locks up. I did install the 64-bit STM drivers as suggested by some.
==========================================================================
Rick,
Windows 10 already comes with the required serial port driver and you should not have needed to install any STM drivers (not the case with Windows 7 or Windows XP).

On a clean Windows installation the following should happen:

- When you connect the NanoVNA-H4 to a Windows 10 PC and power it on, you should immediately hear the usual notification sound of a USB device being connected.

- Try running NanoVNA-Sharp or NanoVNAPartner (see the groups Wiki for software links). If those programs work then your drivers are O.K. and you have a problem specifically with NanoVNA-saver.

- If NanoVNA-Sharp and NanoVNAPartner also don't work, then you either have a driver problem or possibly a bad cable connection between the H4 and your PC.

- If it turns out to be a driver problem, try going into the device control panel and deleting the STM drivers you installed and then re-booting the PC. The next time after re-booting that you connect the H4, windows should use its own drivers and you can troubleshoot from there.

- Herb

I tried all that you recommend, but still not luck. I even tried it in a different Windows 10 computer. Windows is loading their Microsoft driver for the USB, and it does show up when plugged in and turned on. I also tried to putty into it, and I just get a blank screen. I tried hitting the enter key several times, but no response back from the NanoVNA.

On Mon, Jan 27, 2020 at 05:20 PM, <netwtek@...> wrote:

" I tried all that you recommend, but still not luck. I even tried it in a different Windows 10 computer. Windows is loading their Microsoft driver for the USB, and it does show up when plugged in and turned on. I also tried to putty into it, and I just get a blank screen. I tried hitting the enter key several times, but no response back from the NanoVNA. "
===============================================================
Are you saying that the H4 screen was normal but when you connected with putty it went blank or that the putty screen is blank? Do you have an android phone or tablet that you can use? If so try the web app at . I just tried it to verify it works with the H4 and it does. If that app works then it definitely narrows it down to a windows driver problem.

- Herb

Herb

To answer your question, when I used putty, it opened up a window with a flashing curser. Hitting enter did nothing, it remained blank just as thought it could not communicate with the NanoVNA. I alos tried minicom on Linux Mint with the same result.

I tried connecting the NanoVNA on Android with an USB OTG connector using the program you suggested. When I try to connect, I get a message staying "failed to open: Error writing 1 bytes at offset 0 length=1. I am starting to wonder if I have a bad NanoVNA.

Rick

On Mon, Jan 27, 2020 at 06:43 PM, <netwtek@...> wrote:
" .. I am starting to wonder if I have a bad NanoVNA."
=============================================

Could be Rick. I tried upgrading to the release at . After upgrading to that release, I could no longer connect to the NanoVNA-H4. Simliar to what you are experiencing. I had to go back to hugen's release at .

I don't know if you've done any upgrades yet but it might be worth a shot to re-load hugen's release. It will also let you know if DFU Demo can recognize your H4 in the STM DFU mode. This mode is different than the virtual serial port mode so it may work even though the com port driver doesn't.

Good luck.

- Herb

Thank you Herb for all your help. I had not changed what originally came on it, but I did go ahead as you suggested and reinstalled from hugen's github site. No change, still no communications. I am going to sleep on it, and maybe contact Maggie on Alibaba to see how I need to proceed.

73, Rick / N9ITW

Hi all,

Same here...
Win10 shows COM PORT 7 but no communication. Driver used is generic Windows ver 10.0.17763.1
I tried to connect to PuTTY but no prompt showing up.

What is the default speed and settings for this COM port ? I used 9600/8/N/1 Xon/Xoff.

Thanks for any help.
73 Patrick

This happens to me sometimes (rather often), then I have to repeat the start until it connects.

Jos

Op 27-1-2020 om 23:38 schreef netwtek@...:

Patrick,
Since its a usb interface, the 'com port' speed is an irrelevant artifact and the connection actually runs at whatever the computer sets up the usb interface to run at max negotiated throughput.?
This has already been discussed in the forum.?
Please use TeraTerm. It works every time. The Nano will show up as a serial device though.?



On Tue, 28 Jan 2020 at 4:55 AM, tk5ep<pegloff@...> wrote: Hi all,

Same here...
Win10 shows COM PORT 7 but no communication. Driver used is generic Windows ver 10.0.17763.1
I tried to connect to PuTTY but no prompt showing up.

What is the default speed and settings for this COM port ? I used 9600/8/N/1 Xon/Xoff.

Thanks for any help.
73 Patrick

Hi

I'm wworking with Windows 10 and when I click on the link that Herb advises I get a blank screen in my browser (Mozilla FireFox), however my NanoVNA-H4 works well with the "Teraterm"? terminal softwarte, you could try that one as well.

Jos

Op 28-1-2020 om 03:22 schreef hwalker:

On Tue, Jan 28, 2020 at 03:41 AM, Jos Stevens wrote:

Hi

I'm wworking with Windows 10 and when I click on the link that Herb advises I get a blank screen in my browser (Mozilla FireFox), however my NanoVNA-H4 works well with the "Teraterm" terminal softwarte, you could try that one as well.

Jos
============================================================
Jos,
FYI, the browser link only works out of the box with the Chrome browser. Internet explorer requires a special driver, and from your response I'm guessing so does Firefox. What's really strange with Rick's H4 is that he can charge from the USB port, he can put the unit in DFU mode and load firmware from the USB port, but cannot establish comport communications via the USB port.

The above indicates the hardware is O.K. but that the serial port driver is not working. The NanoVNA-H4 uses the STM32F303CCT6 and it supports serial communications via a virtual comport (VCP). I checked to see if there was a Windows 10 driver at but the Windows 10 native STM32 VCP driver is recommended:

"The STSW-STM32102 software package contains four installation files based on the various versions of the Microsoft? operating system.
OS versions prior to Windows? 7 are compatible with the Windows? 7 installations included in the package.
Starting from Windows? 10, the STSW-STM32102 driver is no more adequate and the usage of the native inbox driver is recommended. "

I thought when Rick tried loading the x64 VCP driver from the ST web site that it might have messed up his configuration, but he tried connecting to another Windows 10 PC and also could not establish comport communications.

Very puzzling.

- Herb

On Mon, Jan 27, 2020 at 11:38 PM, <netwtek@...> wrote:

I am trying to run NanoVNA-saver on Windows 10 with the NanoVNA-H4.
NanoVNA-saver correctly sees the USB port the NanoVNA-H4 is connected to;
however, when I click on "Connect to NanoVNA" the program immediately locks
up. I did install the 64-bit STM drivers as suggested by some.

Rick / N9ITW

However, I would try what USBDeview shows, which driver is on the port I'm looking at.
read on in Post # 7284. /g/nanovna-users/message/7284

73, Gyula HA3HZ

I also tried to putty into it, and I just get a blank screen

Steps to use PuTTY with nanoVNA virtual COM port
---------------------------------------------------------------------
1) select "* Serial" on the Session panel
2) change to "COM3" or whatever COM port on the Serial Panel
other default options are OK/ignored
3) select "Implicit CR in every LF" on the Terminal panel
4) select [Open]
5) keyboard [Return] on blank screen to provoke "ch>" prompt

Gyula and Oristo

I installed USBDeview as per Gyula, and it shows ChibiOS/RTVirtualCOM port driver is active and loaded for COM3 (which is the correct COM port). I then tried PuTTY using the information from Oristo's post. PuTTY just opens up to a black screen with a green cursor in the top left hand corner. When I press enter, I get no response or prompt. Any other thoughts?

I installed USBDeview as per Gyula, and it shows ChibiOS/RTVirtualCOM port driver is active
and loaded for COM3 (which is the correct COM port).

Correct COM port, but the wrong driver.
Delete that and hope that Microsoft's USB Serial Device driver gets
loaded subsequently:
C:\WINDOWS\system32\DRIVERS\usbser.sy

I'm getting exactly the same results after trying the same configurations and tests....
I don't have another USB5 cable to try..

Will try on another computer.

I have a NanoVNA-H sw version0.4.0-3 build on nov 25

The DFU

I followed the advice to remove the drivers from USBdeview and voila !
My NanoVNA now shows up with COM11 (COM7 before) and the communication works as predicted.

Now, what other devices are not working anymore ? :-)

Thanks for the help
Patrick TK5EP

Bravo

Unfortunately, I was not as lucky as tk5ep. I deleted the driver, rebooted ,Windows found new device and assigned a different com port (just like tk5ep). Still no communications with Putty, NanoVNA-saver, OR NanoVNA for android.

I have tried two different Windows 10 computers, two different android devices (phone and table) both with an OTG cable, two different USB cables, AND minicom on Linux Mint with no response from the NanoVNA-H4.

I thought about trying to reset the NanoVNA to defaults, but from what I understand, it can only be done through a terminal connection which I cannot establish.