开云体育

Ken,
I used DFU File Manager to convert your hex file to dfu format and then DFU Demo (not File Manger as I previously wrote) was able to load the converted file without error. I encountered the following problems after the upgrade was complete:

1. I could not get a good touchscreen calibration no matter how many times I tried. I had to resort to using the multi-function switch to navigate the UI.

2. The NanoVNA-H4 serial port was not recognized after the upgrade, so no CLI commands could be issued to the NanoVNA-H4.

3. The center frequency problem reported in is still present in your upgrade.

I loaded hugen's January 18th, 2020 release and touchscreen calibration worked, serialport communications was restored, the center frequency issue was still present.

I suggest users hold off on the upgrade until you look into these issues, unless they are adventurous.

Herb

Ever wonder where the idea for this "RF Demo Kit" came from??

A company called MegiQ has been selling something similar for at least 4 years with their VNA..



Roger

Those new to VNA's will find this 3 part video tutorial very informative. It starts off with the basics, then moves on to calibration and finally on how to test components. Topics like using port extenders, de-embedding, transmission lines are all covered. It is time well spent if you really want to learn about VNA's. Just turn off the music - it will drive you nuts...



Roger

"You can get as deep into the pool as you want, but the more you know, the better your measurements will be, and the better you'll know when the instrument is lying to you."
One of the best comments! You will always need to be aware of a lying instrument. The only remedy is knowledge of the instrument and measurement procedures. Get to know how port extensions work, what the effect is of an adapter in your signal path and how to measure stuff without an RF connector.
This cannot be learnt from a cookbook, only through hands-on experience.

Op 24-1-2020 om 23:00 schreef mdrandol@...:

Ken,
When I try to load your DFU file into DFU File Manager I get a "wrong format" error (see attachment). hugen's latest release loads without error.

- Herb

On Fri, Jan 24, 2020 at 12:53 PM, Oristo wrote:

Will including all three of those in /g/nanovna-users/wiki/drivers help or confuse?

Confuse (more). Windows users only need DfuSe for routine firmware updating. Keep it simple as possible.

Downloading and installing DfuSe from

It's also in a google drive "STSW_STM32080_V3.0.6.zip" in the "Firmware" folder (see msg #348 for link).
It could be here in the file section also (subject to the list owner's approval); the ST License Agreement allows redistribution, under conditions therein (see "SLA0044.txt" in the zip file).
Just a suggestion! :-)
--kv5r

There's always the Wikipedia article, and its slew of references.

(electrical)

A VNA displays frequency, amplitude (impedance, return loss, transmittance) and time (phase). You can get as deep into the pool as you want, but the more you know, the better your measurements will be, and the better you'll know when the instrument is lying to you. :)

I ported Hugen's NanoVNA-H branch F303 to ChibiOS 18.2.2. This project only works for the new 4" LCD version, NanoVNA-H4.

The project files are at


You can download the binary at


To update firmware with USB cable only, you need to enter the DFU mode via the following procedure.
- Power off NanoVNA-H4
- Press down the jog switch
- Power on
- Release jog switch

edy555 forked out ChibiOS for his NanoVNA project in 2016 when ChibiOS was in release 3. Now ChibiOS has reached release 19. However, there are some drivers missing in the latest release 19. So I am using the stable release 18.2.2.

With the new ChibiOS release, developers can easily add support of new peripherals like UART, Bluetooth, SD card file system, etc, and use the latest ChibiStudio features. Later, I will add support for other STM32F4 and STM32L4 series MCUs.

If you have the new NanoVNA-H4, please try out this firmware and let me know if you notice any difference compared with Hugen's firmware.

73
Ken, AA6KL

On Thu, Jan 23, 2020 at 07:47 PM, Gabriel Tenma White wrote:

I heard from the customer that they've finished testing half of the first
batch. I think it will become available right after the holidays, so in just
over a week.

Gabriel,

I know you have been doing a lot of prototype testing in recent weeks to get more performance.

Will the manufactured units have your latest changes in them or did you pass them a version from a few weeks ago?

Any chance of posting a a photo of what the first batch looks like?

Roger.

Hi Gabriel
Good idea including k0, k1 and k2 but yes there are more to it. The open has frequency dependent parameters normally represented by the C coefficients C0, C1, C2 and C3 which you may have included in a calibration kit file. Then there is losses to encounter for, in the open due to isolation such Teflon which has a frequency dependent loss and also with respect to delay. Same applies so to speak with the short but no so much for SMA. But if start using commercial BNC and N connector hell break loss. The load also need to have a model with at least a shunt C to the R and a serial L of some few nH or less than 1nH and a delay, because the load parasitic influence bot open and short calibration . I have been doing a lot of tuning lately on a 6GHz R&S calibration kit and did the extension port method for seeing the phase and group delay is oscillations. It not an easy task to get a dot.
Any way it is a very interesting VNAView you have developed and I fell tempted to try it out
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Gabriel Tenma White
Sendt: 24. januar 2020 17:10
Til: [email protected]
Emne: Re: [nanovna-users] First PCB pictures of the V2

I think I get what you are saying, which is that a real world lossy coax stub will have ripples in its S11 that are physical and even if measured with a perfect VNA. In that case I think what I should do is incorporate the k0,k1,k2 loss models into the port extension feature (currently it's only parameterized on length and cable Z0). Then I could (in theory) input k0,k1,k2 into the software, adjust port extension electrical length until the smith chart approaches a dot, then fine tune kit parameters to get the smallest dot. Does this sound right?

This is what the cal kit fine tuning UI looks like currently:
Are there more parameters I'm missing?

Hi Gyula -

this info from ST site:

STSW-LINK009 Active

I suppose that is
.. which appears to be for ST-Link, NOT nanoVNAs..

Installing drivers from there may provoke a problem that we trying to avoid,
namely folks trying to use DfuSe Demo, but having a driver for ST-Link installed.

I suppose that folks should be directed to
for DFU drivers, instead of

Will including all three of those in /g/nanovna-users/wiki/drivers
help or confuse?

FWIW, to test documentation, I am experimenting on a relatively virgin Windows 10 PC:
* Device Manager reports STM32 BOOTLOADER when >>NO<< matching driver is installed.
* my Python scripts (e.g. ) communicate successfully with nanoVNA by COM3 using Microsoft's USB Serial Device driver.

Downloading and installing DfuSe from
(after receiving and responding to confirmation email)
automagically installed the "STM Device in DFU Mode" driver
.. which is located at C:\Program Files (x86)\STMicroelectronics\Software\DfuSe v3.0.6\Bin\Driver\

Thanks, I am encouraged to give it a try.? I already have the hot air gun and am getting fairly good with it.? One day when I am feeling brave I may give it a shot.? I don't have anything to lose, as I can pull the thing back off if need be.
I am on a roll right now, having swapped out my daughter's tires and wheels and then repaired my antenna and cranked the tower back up and worked South Africa to check it out.? It's great to take a project off the list.
I probably should replace the power management IC on my other nano; it won't turn on while the cable is attached.? Once on, I usually can reattach the cable.? That points to the IC, and I have a few spares so that's on the list as well.
I won't get started listing all the other stuff I need to do, but this is a hobby and if I don't feel like doing it, I won't.
Bob On Friday, January 24, 2020, 01:05:22 AM PST, KV5R <kv5r@...> wrote:

On Wed, Jan 22, 2020 at 11:22 AM, Bob Albert wrote:

I just don't have the visual acuity, steady hand, and tiny soldering tool needed.

Howdy Bob,
I don't know if it would be worth the cost, but cell-phone repair techs are always fixing those tiny connectors. There's some youtube videos.
Most don't use a tiny-point iron for fine-pitch devices; they clean the pads, smear solder paste (with flux) across them, set the device in place, then hit it with the hot-air gun. The solder paste melts and surface tension pulls it apart and under the pins, all at once. If done right, no bridges. They also have a microscope!
I have your same afflictions. Last year I got a cheap imported hot-air & soldering iron rework station ($50), a USB microscope on a stand ($45), and a practice board with some SMT chips. It works! The hot air gun takes practice; smallest nozzle, very low air flow, and right temp for the paste used. The hard part is not blowing away the part... :)
73, --KV5R

Bruce, not Bob - was looking at 2 messages at the same time.....

Hi Oristo,

this info from ST site:

STSW-LINK009 Active
Save to myST

ST-LINK, ST-LINK/V2, ST-LINK/V2-1 USB driver signed for Windows7, Windows8, Windows10
Get Software
Download databrief

This USB driver (STSW-LINK009) is for ST-LINK/V2, ST-LINK/V2-1 and STLINK-V3 boards and derivatives (STM8/STM32 discovery boards, STM8/STM32 evaluation boards and STM32 Nucleo boards). It declares to the system the USB interfaces possibly provided by the ST-LINK: ST Debug, Virtual COM port and ST Bridge interfaces.

This may seem to be a dumb question. I hope not. I've been involved in electronics for over 60 years and have done a lot of component and circuit testing using a variety of test equipment items, i.e. meters, o'scopes, signal generators, etc. Never had an opportunity to use a VNA. Too darn expensive until the nanoVNA came out. Great machine. Now, how to use it.

Is there a cookbook on using the VNA to test various components such as resistors, inductors, capacitors, coils, transmission lines, etc.? I see some individual posts covering some items for specific data such as toroids, filters, etc. But, I haven't found a simple to read cookbook on how to set up to test, what data to test and look for, etc. Some of the tomes I've looked at are filled with theory but the actual testing description is minimal. I don't need to go through the theory; I just need to get and interpret the data. Particularly I need to know what to avoid during testing which would mess up the results.

Suggestions most appreciated.

BruceN / K4TQL

--
*"To invent, you need a good imagination and a pile of junk"* -- Thomas Alva Edison (1847-1931)

I think I get what you are saying, which is that a real world lossy coax stub will have ripples in its S11 that are physical and even if measured with a perfect VNA. In that case I think what I should do is incorporate the k0,k1,k2 loss models into the port extension feature (currently it's only parameterized on length and cable Z0). Then I could (in theory) input k0,k1,k2 into the software, adjust port extension electrical length until the smith chart approaches a dot, then fine tune kit parameters to get the smallest dot. Does this sound right?

This is what the cal kit fine tuning UI looks like currently:
Are there more parameters I'm missing?

Hi Norbert

I think you problem is the load as a load has influence on both the short and open calibration. It might be more reactive than my measurement on the NanoVNA supplied load.
I suggest you create a reference s1p file for you semirigid stub and load it into NanoVNA-saver as a reference trace and the observe a s11 dB trace with 0.1dB/div and see how closes it matches.
SimSmith is a nice tool for creating such a reference trace when you have figured out the k0, k1 and k2 factors for your semirigid cable. This is done for k0 as reflection the ohm per meter at DC. K1 for return loss at 0.5 and 5GHz and k2 for 5 and 10GHz as well. It just requires you know what brand your stub are for finding the Att at those frequencies.
As far as a I know you have a VNWA so please write me directly at kurt@... <mailto:kurt@...> for further hints as I also want to do some "dirty tricks" about the NanoVNA ? Then we later can enjoy to info others here.

Kind regards

Kurt



-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af Norbert Kohns
Sendt: 24. januar 2020 13:48
Til: [email protected]
Emne: Re: [nanovna-users] Full reflection runs over the perimeter of the smith chart



Hi Kurt,

thanks for your reply!

The picture shows the calibration settings, that I copied from your document "Male and female calibration of NanoVNA-H".

I used the same standards as you did except the load, which I measured precisely.



Best regards

Norbert, DG1KPN

Yes, I used a barrel adapter.

And - that is why I said:

just don't push them in too far or you'll damage the centre pin on the
BNC/TNC.

On Friday, January 24, 2020, 7:52:35 a.m. GMT-5, Clyde Spencer <cftr01b@...> wrote:

Actually the pin in a N Male connector is larger, wider, than the female
BNC. Using a N male on a BNC female will spread the BNC female center to
the point it can become intermittent for a BNC male.

On Fri, Jan 24, 2020, 7:40 AM Larry Rothman <nlroth@...> wrote:

? ...and don't forget that male N connectors fit female BNC & TNC as well -
just don't push them in too far or you'll damage the centre pin on the
BNC/TNC.

? ? On Friday, January 24, 2020, 5:58:43 a.m. GMT-5, hwalker <
herbwalker2476@...> wrote:

? On Fri, Jan 24, 2020 at 02:16 AM, Reinier Gerritsen wrote:

" BNC on 900 MHz is just so so, on a measurement device it is an absolute
no no! ''
========================================================================

Not true.? BNC connectors are rated up to 4 GHz, although most
professional test equipment? in my company's laboratory only use it to
about 1.5 GHz.? Agilent, Rhode-Schwartz, Fluke etc. all commonly use BNC
connectors on their test instruments.

Quality measurement equipment use BNC connectors manufactured by companies
such as Amphenol, Pasternak, etc.? If you are talking about a bad
experience with cheap Asian imports then you should say that and not
disparage all BNC connectors.

- Herb

Actually the pin in a N Male connector is larger, wider, than the female
BNC. Using a N male on a BNC female will spread the BNC female center to
the point it can become intermittent for a BNC male.