开云体育

On Fri, Jan 24, 2020 at 07:24 PM, Ken Liao, AA6KL wrote:

" ..Thank you for helping me test out the firmware. I was using Ubuntu and didn't try it out at Windows..."
====================================================================================

No problem Ken. It would be nice to have a lab full of beta testers like Microsoft does but I guess you'll have to settle for us instead. If there is a useable platform for connecting to the NanoVNA-H4, one of the boards members is probably running it.

I eventually gave up trying to use the touchscreen and went to navigating the UI using the jog-switch. Even so, after doing a touchscreen corner to corner calibration and touchscreen test, registration and sensitivity using a stylus was not useable.

After, the firmware update, USB communication was toast even after I cycled power on the NanoVNA-H4 a few times. I was hoping to be able to perform a "clearconfig 1234" after updating but could never link to the NanoVNA-H4 via a serial connection. Loading hugen's firmware put things back in order.

I don't know how wide spread the greater than 1 GHz center frequency issue is. None of this group's member's have reported it not being a problem, while those that have responded are experiencing the same lock-up issue I have observed. hugen has left feedback that he is investigating the issue, but this being Chinese New Year he deserves to spend time with friends and family and hopefully hit the ground running afterwards.

My system is Windows 10 x64, i7, 12Gb.
regards,
- Herb

Ok it looks like I need to do more work on the cal kit parameters. Previously the software only took S parameter files for cal kit definitions, and I've only added a "fine tune" UI which does length extension the configured S parameters (and adds parasitics for the load standard).

The hardware hasn't changed since the December revision (V2_2), which is the revision they are using for production. The next hardware revision will be an experimental one, with changes like an amplifier on channel 0 and port 2 ecal features.

Here is one sample from production:
Note that the enclosure is still not finalized and for the first few weeks the VNA will be sold without an enclosure at reduced price I've heard. There are still some fit issues related to the connectors that need to be fixed and enclosure manufacturing will take some time as well.

Ken,I think you meant to say in the last paragraph that the MCU can NEVER be bricked as you will always be able to get back into dfu mode.?
... Larry



On Fri, 24 Jan 2020 at 10:24 PM, Ken Liao, AA6KL<kuohsing@...> wrote: Herb,

Thank you for helping me test out the firmware.? I was using Ubuntu and didn't try it out at Windows.? I will be out of reach of my lab computer for the following two days.? So it will take a few day to have the new formware fixed.

For the DFU format issue, I was using the dfu-tool to convert from bin to dfu format, and tested it with dfu-util.? Apparently, the generated format is not recognized by ST Micro's DfuSe Demo.? I need to find a better tool to do the conversion at Ubuntu.

The touchscreen calibration needs to be done through Configuration->Touch Calibration with jog switch after the firmware update.? I can? make it use the default one after each firmware update, instead of reading from Flash configuation.

I saw the USB serial issue too.? But once I unplug the USB cable, turn off and turn on the device, then plug in USB cable, the USB serial works.? I will verify if this is same for Windows.? In ChibiOS_18, the gcc compilation is quite aggressive and may cause race condition.? In Ubuntu, if I disable the LTO (Link Time Optimization) flag in gcc, the USB would work.? Making compile option -O0 (no optimization) also works, but the firmware size is 190KB!? Another potential USB issue is the device USB handshake with host by pulling down USB_DP pin.? This requires the R48 connected between USB_DP(PA12) and PA8, which is not polulated at this moment yet.? I will do more experiment to fix the USB serial issue.

Roger raised an interesting question about how to burn formware via USB with malfuntion USB serial. When pressing the job switch at powering on, the BOOT0 pin is connected to VDD, and MCU enters the DFU mode.? The DFU firmware is inside the ROM and cannot be modified.? This way, ST Micro can ensure that its MCU will be bricked (totally dead and un-recoverable) by bad flash content.

For the center frequency issue, I will wait for Hugen's fix and merge his code.

Ken

Herb,

Thank you for helping me test out the firmware. I was using Ubuntu and didn't try it out at Windows. I will be out of reach of my lab computer for the following two days. So it will take a few day to have the new formware fixed.

For the DFU format issue, I was using the dfu-tool to convert from bin to dfu format, and tested it with dfu-util. Apparently, the generated format is not recognized by ST Micro's DfuSe Demo. I need to find a better tool to do the conversion at Ubuntu.

The touchscreen calibration needs to be done through Configuration->Touch Calibration with jog switch after the firmware update. I can make it use the default one after each firmware update, instead of reading from Flash configuation.

I saw the USB serial issue too. But once I unplug the USB cable, turn off and turn on the device, then plug in USB cable, the USB serial works. I will verify if this is same for Windows. In ChibiOS_18, the gcc compilation is quite aggressive and may cause race condition. In Ubuntu, if I disable the LTO (Link Time Optimization) flag in gcc, the USB would work. Making compile option -O0 (no optimization) also works, but the firmware size is 190KB! Another potential USB issue is the device USB handshake with host by pulling down USB_DP pin. This requires the R48 connected between USB_DP(PA12) and PA8, which is not polulated at this moment yet. I will do more experiment to fix the USB serial issue.

Roger raised an interesting question about how to burn formware via USB with malfuntion USB serial. When pressing the job switch at powering on, the BOOT0 pin is connected to VDD, and MCU enters the DFU mode. The DFU firmware is inside the ROM and cannot be modified. This way, ST Micro can ensure that its MCU will be bricked (totally dead and un-recoverable) by bad flash content.

For the center frequency issue, I will wait for Hugen's fix and merge his code.

Ken

at 388 US for the kit. they have been putting lot of time on the tutorial
and not selling many the way I see it..


Le ven. 24 janv. 2020 à 18:28, Roger Need via Groups.Io <sailtamarack=
[email protected]> a écrit :

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

On Fri, Jan 24, 2020 at 04:22 PM, Roger Need wrote:

How did you manage to get into DFU mode and reflash if the serial port was not recognized in Windows?
=================================================================

Hi Roger,
DFU Demo Recognizes the NanoVNA as a device in DFU mode not as a serial port. So it works even though a terminal program sees nothing attached. The actual logistics are above my pay grade, but I think that covers the gist of it.

On a side note, when you first boot the NanoVNA-H4 into DFU mode the screen goes completely dark during the process. This is different than when the 2.8" NanoVNA goes into DFU mode. Kind of freaks you out until you realize that's just the way it works; but the first time there's a "What did I do to my new -H4 moment".

- Herb

Herb,

How did you manage to get into DFU mode and reflash if the serial port was not recognized in Windows?

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