开云体育

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

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

the tape pushes along the edge of the display, I tried but not good.

On Tue, Jan 28, 2020 at 04:54 AM, Gyula Molnar wrote:

Touchscreen rework – insert 4 pcs plastic washer.
===============================================

Gyula,
Kudo's! That is a much cleaner solution than the extra tape on the Russian forum. I will submit an issue report to hugen with your proposed solution.

- Herb

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

Touchscreen rework – insert 4 pcs plastic washer.

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:

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

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@...:

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

Minor fix for typing above:
The "error: si5351_init failed" message occurred while charging the battery from the USB port on the computer after trying to turn on the device when it was turned off.
Solution: When charging the battery, I do not turn on the device while charging turn on the device and there will be no such error message.

I probably need to look for a menu switch error later on. See 5.

Gyula

On 1/27/20 8:02 PM, N8AUM via Groups.Io wrote:

Hello group!
I am a little confused now regarding what a typical DC resistance should be for a 50 ohm load that the specs say DC to whatever. At DC shouldn't it be very close to 50 ohms? A measurement of 68 ohms at DC is 36% high ? What am I missing here ?

???? Yes, it should measure 50 ohms.? Your load appears to be defective.

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

Hello group!
I am a little confused now regarding what a typical DC resistance should be for a 50 ohm load that the specs say DC to whatever. At DC shouldn't it be very close to 50 ohms? A measurement of 68 ohms at DC is 36% high ? What am I missing here ?

Vidas

On Mon, 27 Jan 2020 at 21:42, <pgc1682@...> wrote:

Not understand S= Z= Y= values in WVNA, (selectable for in arbitrary
open/short/load), this labels S, Y, Z not same all calibrator files
supplied with WVNA.

73, Lajos

IIRC, the standards can be defined as S-parameters, or an inpedance (Z) or
admittance (Y). Although they are all equivalent, it is easier to calculate
the impedance inductor. But for capacitor, it’s easier to work as an
admittance. It is purely a matter of

I believe that you are using an N calibration kit. You can pretty much
ignore the loss of that at 1.3 GHz.

In the case of an ideal short, S=-1, Z=0, and Y is infinity. You can either
them whatever way suites you best.

Dave

--

Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom

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

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 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

Hi Rudi
It is a 22cm R316 test cable I used 500MHz as that is a range with good performance of the NanoVNA, although it also works with 900MHz. During the process the star stop frequencies changes and I just manually restore these before an new run.
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af reuterr@...
Sendt: 27. januar 2020 18:41
Til: [email protected]
Emne: Re: [nanovna-users] characteristic impedance

On Mon, Jan 27, 2020 at 04:32 PM, Kurt Poulsen wrote:

Remember to set a frequency span e.g. 0.05 to 500Mhz then calibrate
and save to e.g. location 0. Then follow the steps described in the
right side I see you missed that

Hello Kurt,
Sorry, I can not make it to work.

Can you please tell me, what is the length of your coax cable and what type.
I guess that your dip was at 500 MHz, right? But then a span of just 500 MHz is strange for me.
It looks like, that I have a misunderstanding, but where?

The program nanoVNA Partner behaves strange, if you do not make it right on the first try.
I need to close it and restart after each try.

73, Rudi DL5FA

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.