开云体育

Another verified kink (Item 5) added:

Members have started receiving the NanoVNA-H4 (H4) and reporting various hints and kinks (mostly the latter). I thought it would be a good idea to start a topic where users could look for this information under one topic.

Kinks:
1. Several users have reported that the opening for the USB-C connector needed to be widened. Gyula Molnar provided an example fix in message #10333.

2. There has been wide spread feedback that setting the frequency range above 1 GHz, using center frequency and span, results in the H4 locking up and requiring power cycling. The work around until hugen announces a fix is to only use start and stop frequencies to set the range above 1 GHz.

3. The H4 display sometime exhibits artifacts from the previous sweep that don't clear when the display refreshes. The 2.8" display had similar issues but it is more noticeable on the 4" display. You can force a refresh that clears the artifacts by performing a trace selection.

4. Gyula Molnar reported that the menu switch on his H4 did not initially work and of receiving a subsequent error message: "error: si5351_init failed". Both were apparently solved by fully charging the battery.

5. A Russian user posted the following, which I have verified on my H4:
The cut-out under the touch screen is narrower than required. If a menu is brought up and pressure is applied to the right side of the case, the device begins to run around the menu. You can permanently solve this issue by disassembling the case and on the non-sensory part of the display, the right edge to the silver line inclusive, stick 1 layer of extra tape to the board. I haven't verified the fix, but I have verified that if a menu is present applying pressure to right hand side of the case will cause random menu selection.

Hints:
1. The H4 enters the DFU mode differently than in the past. Use the following procedure to enter DFU on the H4.
- Power off NanoVNA-H4
- Press down the jog switch
- Power on
- Release jog switch
The screen should black out and DFU Demo should report an STM device in DFU mode. Follow normal upgrade procedure from that point.

2. The H4 maintains excellent backwards software command compatibility and works with NanoVNA-saver, NanoVNASharp and NanoVNAPartner. The screen capture command will not work, if present, in any of these programs because of the larger screen size. The necessary software change is minor and hopefully the developers will catch up soon. Until then, you can use Oristo's python capture script at after making the following modifications.

- change 320 and 240 to 320 and 480 at lines 46 and 73 Comment: pixel dimensions of NanoVNA-H4 display are 320 by 480
- change x value to: x = struct.unpack(">153600H", b) Comment: Number of half bytes has doubled
- change img value to: img = Image.frombuffer('RGBA', (480, 320), arr, 'raw', 'RGBA', 0, 1) Comment: Converted image
- change COM3 at line 11 to appropriate comport

3. The H4 firmware is NOT backwards compatible with the NanoVNA-H. Too many changes had to be made to accommodate the new Cortex-M4 MCU (F303) and the 4" display to maintain compatibility. hugen now maintains separate NanoVNA-H4 and NanoVNA-H firmwares. Do not make the mistake of installing NanoVNA-H firmware in a NanoVNA-H4.

4. The brightness menu has been substituted for the DFU menu on the H4. Users can now adjust the display brightness for best inside or outdoor viewing.

5. A new marker menu is available (courtesy of an edy555 merge). Users who would rather have the smith chart display in terms other than L/C can now do so.

6. The slightly annoying "feature", where the power LED stays on for a few moments after switching the NanoVNA-H off, seems to be gone forever on the NanoVNA-H4 (and NanoVNA-H v3.4).


Feel free to add to the items above after getting confirmation of the kink from another member, if possible. I have submitted an issue report to hugen ( ) regarding the case opening and center frequency kinks. He responded that he will look into both issues when he returns after the Chinese New Year.

- Herb

On Mon, Jan 27, 2020 at 01:59 PM, hwalker wrote: W5DXP,
Another interesting take on the 1/8 wave length cable impedance measurement. Did you predetermine the optimum frequency range or just eyeball a range for best fit of the intersection?

Herb, my NanoVNA is calibrated for 3-30 MHz. I first run the scans over that whole range to find out what intersection frequency I need to zero in on.

Approved.

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

John,
The typical dfu file is 190KB. What you're looking at is the archive with several files.?
Please go through the forum wiki or use the link that Oristo just gave you and download the dfu directly from QRP's github.?
If you're doing tv streaming, 190KB will d/l in 2 seconds or less.
Just make sure you grab the file with .dfu at the end.?
... Larry



On Mon, 27 Jan 2020 at 6:22 PM, John via Groups.Io<n0ure@...> wrote: Oristo

I have seen that many dfu files are very large. Internet in this house is used for TV streaming so I will DL over the night.
Now I will go looking for the Windows dfu flash procedures.

Later

John

Oristo

I have seen that many dfu files are very large. Internet in this house is used for TV streaming so I will DL over the night.
Now I will go looking for the Windows dfu flash procedures.

Later

John

Members have started receiving the NanoVNA-H4 (H4) and reporting various hints and kinks (mostly the latter). I thought it would be a good idea to start a topic where users could look for this information under one topic.

Kinks:
1. Several users have reported that the opening for the USB-C connector needed to be widened. Gyula Molnar provided an example fix in message #10333.

2. There has been wide spread feedback that setting the frequency range above 1 GHz, using center frequency and span, results in the H4 locking up and requiring power cycling. The work around until hugen announces a fix is to only use start and stop frequencies to set the range above 1 GHz.

3. The H4 display sometime exhibits artifacts from the previous sweep that don't clear when the display refreshes. The 2.8" display had similar issues but it is more noticeable on the 4" display. You can force a refresh that clears the artifacts by performing a trace selection.

4. Gyula Molnar reported that the menu switch on his H4 did not initially work and of receiving a subsequent error message: "error: si5351_init failed". Both were apparently solved by fully charging the battery.


Hints:
1. The H4 enters the DFU mode differently than in the past. Use the following procedure to enter DFU on the H4.
- Power off NanoVNA-H4
- Press down the jog switch
- Power on
- Release jog switch
The screen should black out and DFU Demo should report an STM device in DFU mode. Follow normal upgrade procedure from that point.

2. The H4 maintains excellent backwards software command compatibility and works with NanoVNA-saver, NanoVNASharp and NanoVNAPartner. The screen capture command will not work, if present, in any of these programs because of the larger screen size. The necessary software change is minor and hopefully the developers will catch up soon. Until then, you can use Oristo's python capture script at after making the following modifications.

- change 320 and 240 to 320 and 480 at lines 46 and 73 Comment: pixel dimensions of NanoVNA-H4 display are 320 by 480
- change x value to: x = struct.unpack(">153600H", b) Comment: Number of half bytes has doubled
- change img value to: img = Image.frombuffer('RGBA', (480, 320), arr, 'raw', 'RGBA', 0, 1) Comment: Converted image
- change COM3 at line 11 to appropriate comport

3. The H4 firmware is NOT backwards compatible with the NanoVNA-H. Too many changes had to be made to accommodate the new Cortex-M4 MCU (F303) and the 4" display to maintain compatibility. hugen now maintains separate NanoVNA-H4 and NanoVNA-H firmwares. Do not make the mistake of installing NanoVNA-H firmware in a NanoVNA-H4.

4. The brightness menu has been substituted for the DFU menu on the H4. Users can now adjust the display brightness for best inside or outdoor viewing.

5. A new marker menu is available (courtesy of an edy555 merge). Users who would rather have the smith chart display in terms other than L/C can now do so.

6. The slightly annoying "feature", where the power LED stays on for a few moments after switching the NanoVNA-H off, seems to be gone forever on the NanoVNA-H4 (and NanoVNA-H v3.4).


Feel free to add to the items above after getting confirmation of the kink from another member, if possible. I have submitted an issue report to hugen ( ) regarding the case opening and center frequency kinks. He responded that he will look into both issues when he returns after the Chinese New Year.

- Herb

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

Have you tried using the installer from python.org?

Sure, on other systems.
Python bundled with Visual Studio Community also has no such issues,
but Python has plenty of other issues even with python.org versions.

As I mentioned, that was a relatively virgin Windows 10 PC,
and Store code disappears when an account is deleted.

section 3.2 in the Using Python on Windows page, as referenced from the Microsoft Store page.

Nope, if M$ cannot be bothered to make it a hyperlink, then I am not motivated to retype their URL.

On Mon, Jan 27, 2020 at 12:12 PM, W5DXP wrote:

"The way that I measure the Z0 and VF of an unknown piece of coax is to measure and plot the impedance with the coax open-circuited overlaid with a plot of the impedance with the coax short-circuited. Since the Z0 of 1/8 wavelength of open-circuit coax is -jZ0 and the Z0 of 1/8 wavelength of short-circuit coax is +jZ0, then where the curves intersect is the Z0 of the coax. VF is calculated by dividing the physical length by the length of 1/8 wavelength in free space. I picked three pieces of coax at random, RG213, RG6, and RG62, and ran those graphs. "
==================================================
W5DXP,
Another interesting take on the 1/8 wave length cable impedance measurement. Did you predetermine the optimum frequency range or just eyeball a range for best fit of the intersection?

- Herb

Hi Kurt,

I will borrow high quality OSLT N standard. I will try on Nanovna and WVNA. I not fully understand values conversion to WVNA arbitrary settings.

This calibrator 50 ohm load not have inductance or capacitance modell. Which is the settings line for this load in WVNA?

Sort, and open have offset loss parameters and C0-C3, L0-L3 C0-C3, L0-L3 values already converted from your manual, but how to convert to wvna offset loss? Offset loss availabe dB/sqrt(GHz) or Mohm/s format. All L0-L3 parameters zero, what is the simple formula?

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

Have you tried using the installer from python.org? Microsoft notes on their store their version might not be stable. It is a bit nerfed from the full version. See section 3.2 in the Using Python on Windows page, as referenced from the Microsoft Store page.

K9YC and I have exchanged several emails regarding his recommendation to
not use open wire feeders. We had to part ways agreeing to disagree on
this bit of advice. For the newbie, his advice is good.

However, I operate a 450-foot long doublet with a lowest resonant frequency
of 950 kHz. I use open parallel wire transmission line. There isn't more
than 8-feet of coax in the entire system. I have common mode bifilar wound
chokes using the red iron powder cores (?r about 10) at both the input and
output of my (home brew) L-Network *matching* network (a.k.a., 'antenna
tuner - it does NOT "tune" the antenna!!!). I use this setup from
160-meters through 6-meters. I believe key to this solution is abandoning
the 43, 75, 31, and.... materials in winding bifilar or quadfilar CM
chokes. Instead, use the red/black cores (Material 2) for HF. The ?r of
the 'other' materials is just too high to make a good CM choke in this
manner. For the current choke, that wound with coax around and through the
torus, the higher ?r materials are quite appropriate as they are more
lossy (Rs) and, once constructed in a current choke manner, offer more
inductance (Ls) WITHOUT resonances (if properly wound) in the HF region.

Dave - W?LEV


On Mon, Jan 27, 2020 at 6:56 PM David Eckhardt via Groups.Io <davearea51a=
[email protected]> wrote:

A far more extensive treatment of all topics related to this, and many
others, which is well based in good engineering practices and faithful to
the physics of EM can be accessed at the following URL. Dig, there is a
*LOT* of good information here.



I'd suggest a complete read of all things pertaining to baluns and chokes
on this site. It's quite extensive.

Dave - W?LEV

On Mon, Jan 27, 2020 at 6:24 PM stone_ridge_road <xdavid@...

wrote:

K9YC's RFI-Ham.pdf file is an older one with a lot of good information,
but K9YC wrote the 2018Cookbook.pdf paper specifically to update the
information on common mode chokes. He no longer uses some of the
information in the earlier paper, and he now strongly recommends only
#31 for common mode chokes for any of the HF bands.

Type 31 ferrite was specifically developed by Fair-Rite to have the kind
of internal loss at HF that the other cores don't.

73,
Dave AB7E


On 1/27/2020 9:43 AM, Randall Steffens II via Groups.Io wrote:

I think Dave meant to link this document by K9YC -

. It’s the one where he compares a number of
different types (#43, #61, #73, #78, etc) and why he often prefers #31.

But

he has good things to say about #43 as well! Also #61 and #73 in some
circumstances. This document is a GREAT read!!

Randy
NC8U

--

*Dave - W?LEV*
*Just Let Darwin Work*
*Just Think*

--

*Dave - W?LEV*
*Just Let Darwin Work*
*Just Think*

Hi Gyula -

Can you download:

It works for me, except that Chrome warns against downloading it.
Warning is easily overridden and perhaps is better than needing to right-click and [Save link as..] ..?

Yes that one works okay.? Thanks!
Bob

Hi Alberto,

I set it up by measuring the voltage at the battery connection points, and noted this.
I checked the voltage displayed with nanoVNA-Saver or nanoVNAPartner. I typed the difference between the two with Terra Term at vbat_offset.
That is all.

73, Gyula

Bob -

gives me a screen of gibberish

That happens by mouse >>left-click<< on the URL
Instead, need right-click and [Save link as...]

Hi Rudi,

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.

If there is a button in the window that has no subtitles, you can delete the window with that button. Unfortunately, the author did not label this.
You can zoom in by holding down the left mouse button and dragging and releasing.
The maker made it a hobby.

That's all.

The way that I measure the Z0 and VF of an unknown piece of coax is to measure and plot the impedance with the coax open-circuited overlaid with a plot of the impedance with the coax short-circuited. Since the Z0 of 1/8 wavelength of open-circuit coax is -jZ0 and the Z0 of 1/8 wavelength of short-circuit coax is +jZ0, then where the curves intersect is the Z0 of the coax. VF is calculated by dividing the physical length by the length of 1/8 wavelength in free space. I picked three pieces of coax at random, RG213, RG6, and RG62, and ran those graphs. Here are the results:

Oops, sorry my bad, NOT


but this one: